On Oct 23, 2016, at 10:49, Monty Montgomery xiphmont@gmail.com wrote:
We've already decided that updates cannot be done safely without at least one reboot, so let's not bother with requests to remove that.
That may be an intentional design decision, but as a result I've simply stopped installing updates.
Yes, the kernel has traditionally required a reboot, as have power failures and hardware upgrades. But it seems odd that a reboot is required for, eg, a GIMP update. (or is that not the case? It has seemed like everything coming in through Software Update requires reboots these days. That is my impression, and the impression of many others, and it may be incorrect.)
It's correct, Monty, any and all updates are handled during a reboot (actually 2). The package manager doesn't have an idea of "This program could simply be restarted, this library isn't currently in use, this package would definitely require a reboot" so it goes with what is guaranteed to work: reboot for everything. It's the safer, though far more annoying, route.
Personally I installed the tracer plugin and just do "dnf update", even on my rawhide system.
Definitely in favor of taking the system from "full desktop" transitioning to "minimal upgrade environment" and then executing the reboot after the upgrade is down. Rather than our current: full desk environment, reboot, minimal upgrade, reboot, full desktop environment.
Hell, not even Windows usually requires two reboots for upgrades.