On 2017-02-26 22:36, Anton Aylward wrote:
On 26/02/17 02:22 PM, Carlos E. R. wrote:
You can have snapshots, yes, but not the rollback feature on boot. The ability to boot an older snapshot, then make it the current one. "/" must be a single partition.
I think that's an ambiguous wording. What do you mean by "/" in that?
It needs to control /boot, /var, /usr, /lib, /bin, /sbin... Dunno /tmp. Some parts are not included, like /var/log, databases, and such. But the rpm database is reverted, I think. I don't know if there is a list of the volumes that btrfs snapshots needs to control. All data directories can be separated, like /home, /srv...
If you are saying that the root FS needs to have /boot then yes I agree. After all the binaries in /boot correspond to the, for example, kernel modules in /lib/modules.
Exactly.
But I'll insist that purely data parts of the tree that aren't involved in the boot sequence, such as /home, and the stuff used by Apache under /srv, and the stuff that isn't used until the system is up and running and applications are needed such as /local and quite probably /usr/share, and many others that aren't needed until someone logs in are exempt.
All /usr must be controlled by the snapshot-rollback mechanism. Data yes, can be outside. Better, should be outside. the /local directory, i don't know, I haven't thought it out. /etc is included.
I'm not being absolutist in "data is data and code is code and never the twain shall meet". After all,, there's a lot of 'data' needed to get the system up, things in /etc, the 'data' such as systemd's units. One reason to have /usr as part of the boot & RootFS -- but not things in /usr/share like the man pages, obviously!
All that comes in rpms needs be included, because it can be reverted.
BTDT. Please don't tell me I can't do what I've been doing successfully for a while.
-- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))