If I can put /usr on a different subvolume which will include /usr/bin, /usr/sbin, /usr/lib, and /usr/lib64, then I should be able to put /etc on a separate subvolume and anaconda should be enhanced to permit it.
That gets really messy though, because /etc/fstab is what contains the partition configuration...
When I realized how well this worked and how easy it was to do, I wanted to do the same thing for /etc becuase I change a lot of stuff in it such as /etc/libvirt definitions.
Right, the tricky thing with /etc is that it is a mix of OS defaults and your custom state. That's why the OSTree model introduces /usr/etc which holds defaults; so at any point, you can do "ostree admin config-diff" and get a diff of just your changes to /etc. You can then just back this up.
The reason OSTree needs /usr/etc is to implement upgrades - it ensures your changes propagate forwards.
OK, is putting /usr on a different btrfs subvol a bug or a feature?
I'd say it's an option. You can snapshot /usr and that's OK but it does lead to questions about /etc and the other major directories: /boot and /var. Basically if you use snapshots of /usr you get to keep both pieces (literally! ;) )
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
