> > Ah, so you have to reboot anyway, so where is the difference > between > your approach and proper offline updates then? Either way you > have to > interrupt your work to reboot the machine. One just takes a > slight bit > longer for rebooting... > > Lennart > > -- > Lennart Poettering - Red Hat, Inc. > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > In the future, hopefully once btrfs is a bit more mature, perhaps it could be considered to make a new writable snapshot subvolume of the system, and the use yum prefix to update the new subvolume. When you reboot, the new subvolume can become the new root. a) Currently running system files aren't affected. b) All upgrades are done online c) the update would merely be a switching of the root device on next reboot d) you could even roll-back by remounting the old root subvolume as the root fs. This would be similar to "boot environments" in solaris. Of course, if btrfs wasn't in use, there could be some fallback? -- Sincerely, William Brown pgp.mit.edu http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x3C0AC6DAB2F928A2
Attachment:
signature.asc
Description: This is a digitally signed message part
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
