On Fri, 2014-09-12 at 10:46 -0400, Stephen Gallagher wrote: > == Proposed Improvements == > > We could significantly improve this situation by allowing the system > to drop directly from the interactive system into the updater > environment without doing a full reboot or relaunching the kernel. > > Lennart, would it be possible to set up a special systemd target for > performing updates that would essentially stop all processes except > for systemd and then apply the updates? > > In an ideal world, it would then also be possible after update is > completed to restore operation to the standard boot targets of systemd > so that the system comes back up without having to perform a total > reboot. The exceptional case would of course be that in which either > the kernel, libc or systemd[1] needed to be updated, in which case a > reboot could be performed. > > In this scenario, we can reduce the number of encrypted disk > challenges to at most a single one, and that only if absolutely > minimal plumbing packages saw an update. > > I'd very much like to hear from the plumbers on this matter.
Yeah, I almost never use the reboot & install method. 90% of the packages being installed/updated seem foolish to need a reboot to update. I typically do a yum update manually and then if I notice glibc/kernel/systemd or other big packages do a reboot. All my systems have disk encryption since some of our projects could potentially include people's private information. The latest way of updating is just plain annoying for an unknown gain. I would *love* if it was improved. -- Nathanael -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
