On Wed, Dec 29, 2021 at 7:36 PM Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > > On Wed, Dec 29, 2021 at 12:57:25PM -0500, Neal Gompa wrote: > > of the RPM database. Once the RPM database is moved, it becomes > > possible to split /var into its own subvolume and make it trivial to > > configure a full boot-to-snapshot system leveraging the technologies > > we have available to us. > > The Benefit to Fedora section alludes to this, but doesn't really spell it > out... since this seems like a pretty compelling benefit, it probably > should. Added. There's more hurdles to jump, just so no one thinks snapshots and rollbacks are showing up in Fedora 36. There's a quandary with /boot which likewise is married to /usr via the vmlinuz kernel modules. As we snapshot /usr how do we retain vmlinuz such that we can still boot those older snapshots? And then how do we do it considering Boot Loader Spec expects "boot" (or $BOOT) volume to be shared among multiple distros? Related is the "discoverable sub-volumes specification" discussion, so that we have a way of self-described assembly of systems during startup instead of having to depend on fstab, or any other database for that matter, to know how a system should boot. https://lists.freedesktop.org/archives/systemd-devel/2021-November/047059.html -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
