text stringlengths 7 369 |
|---|
[2163.26 --> 2163.92] I like using it |
[2163.92 --> 2165.34] because it's just, |
[2166.48 --> 2167.72] I think it's how |
[2167.72 --> 2168.42] I'm going to use |
[2168.42 --> 2169.10] Linux now |
[2169.10 --> 2170.72] for the future |
[2170.72 --> 2172.08] when I'm not |
[2172.08 --> 2173.46] deploying a desktop |
[2173.46 --> 2173.88] system. |
[2173.98 --> 2174.56] And I'm not even |
[2174.56 --> 2175.92] convinced it may |
[2175.92 --> 2176.76] actually ultimately |
[2176.76 --> 2177.38] end up using it |
[2177.38 --> 2178.24] for a desktop system |
[2178.24 --> 2179.12] as well. |
[2179.46 --> 2180.22] Especially like a |
[2180.22 --> 2180.76] system here in the |
[2180.76 --> 2181.52] studio that's pretty |
[2181.52 --> 2182.04] static. |
[2183.00 --> 2183.32] I think the |
[2183.32 --> 2184.22] counterpoint to that |
[2184.22 --> 2185.86] is what Red Hat, |
[2185.98 --> 2186.46] for example, |
[2186.46 --> 2187.26] I know it well, |
[2187.34 --> 2188.00] are doing with |
[2188.00 --> 2189.36] the Red Hat |
[2189.36 --> 2190.74] Core OS operating |
[2190.74 --> 2191.34] system at the |
[2191.34 --> 2191.50] minute, |
[2191.64 --> 2192.56] Fedora Core OS |
[2192.56 --> 2192.96] if you want to |
[2192.96 --> 2193.48] try out the |
[2193.48 --> 2194.84] upstream version. |
[2195.52 --> 2196.22] Everything is |
[2196.22 --> 2197.78] configured declaratively |
[2197.78 --> 2198.86] up front, |
[2199.04 --> 2199.22] right? |
[2199.28 --> 2199.94] So you say, |
[2200.06 --> 2200.74] I want this |
[2200.74 --> 2201.60] NIC to have |
[2201.60 --> 2202.46] this IP address. |
[2202.94 --> 2203.74] I want these |
[2203.74 --> 2204.96] storage disks to |
[2204.96 --> 2205.88] be configured to |
[2205.88 --> 2206.56] this mount point, |
[2206.64 --> 2207.24] that kind of thing. |
[2208.08 --> 2209.04] That's all done |
[2209.04 --> 2209.56] through an |
[2209.56 --> 2210.26] ignition config |
[2210.26 --> 2210.66] file. |
[2210.90 --> 2211.90] You supply that |
[2211.90 --> 2212.70] to the VM |
[2212.70 --> 2213.52] or to the |
[2213.52 --> 2215.44] machine when it |
[2215.44 --> 2216.00] boots up, |
[2216.00 --> 2217.10] and it then |
[2217.10 --> 2218.32] configures itself |
[2218.32 --> 2219.52] based on that |
[2219.52 --> 2221.04] instantiation kind |
[2221.04 --> 2222.10] of request. |
[2223.06 --> 2224.00] And it seems to |
[2224.00 --> 2224.72] me like NICS is |
[2224.72 --> 2225.60] operating in a |
[2225.60 --> 2226.46] similar space where |
[2226.46 --> 2227.44] the operating system |
[2227.44 --> 2228.16] is almost like |
[2228.16 --> 2229.78] read only and |
[2229.78 --> 2230.44] everything is kind |
[2230.44 --> 2231.42] of given to it. |
[2231.50 --> 2232.12] It's like this |
[2232.12 --> 2233.90] blank canvas onto |
[2233.90 --> 2234.70] which everything gets |
[2234.70 --> 2236.08] painted straight |
[2236.08 --> 2236.42] away. |
[2237.06 --> 2237.84] NICS OS itself |
[2237.84 --> 2238.70] managed to make |
[2238.70 --> 2239.76] base arch feel |
[2239.76 --> 2240.08] bloated. |
[2240.20 --> 2240.78] It's really |
[2240.78 --> 2241.12] nothing. |
[2241.26 --> 2241.86] There's not a lot |
[2241.86 --> 2242.72] going on there. |
[2242.72 --> 2245.56] So what happens |
[2245.56 --> 2246.22] when you need to |
[2246.22 --> 2247.70] do a rollback, |
[2247.94 --> 2248.60] for example, |
[2248.60 --> 2249.34] with my home |
[2249.34 --> 2250.08] assistant VM |
[2250.08 --> 2251.34] running on top |
[2251.34 --> 2251.92] of Proxmox, |
[2252.16 --> 2253.42] if an upgrade |
[2253.42 --> 2254.16] goes sideways, |
[2254.72 --> 2256.06] all I do is |
[2256.06 --> 2257.02] roll back a |
[2257.02 --> 2257.82] specific snapshot |
[2257.82 --> 2258.96] which on the |
[2258.96 --> 2259.82] ZFS backend |
[2259.82 --> 2260.64] storage that |
[2260.64 --> 2261.70] Proxmox uses |
[2261.70 --> 2263.48] is simple. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.