3 ms·
> Anything that involves system services This is not true. NixOS, as one example, is able to figure out which services (including system) need to be restarted.
by zamalek 4y ago
> Anything that involves system services
This is not true. NixOS, as one example, is able to figure out which services (including system) need to be restarted.
> god forbid the kernel
This is not true either. Live kernel updates are possible (but are usually a paid addition, e.g. https://ubuntu.com/security/livepatch https://ubuntu.com/security/livepatch).
- lockhouse 4y agoIn the case of an update involving a shared library you would still have to close and restart every single program that links against it though, right? Which if we’re talking about something like glibc you might as well just reboot.
- zamalek 4y agoIf you wanted the change to take effect then, yes, you would need to restart those apps. Because of the way that NixOS deals with dependencies, the old versions would still be around for running apps to use and carry on. It might actually be a useful tool for NixOS: finding out which processes have a specific version of a module loaded, so that the user can be warned to restart those processes. If the user wants to restart processes they can, if they want to just reboot they can also. Simply because it's "simpler" to do one, doesn't mean it's the correct universal choice in all circumstances. My wife, for example, leaves way to much crap open and leaves her laptop suspended - a restart is a serious issue for her.
- commoner 4y agoI've never had to reboot Linux after a glibc update if I didn't care whether the new version was being used. In general, glibc updates are not important enough to interrupt what I'm doing to reboot my device and I'll just shut down or reboot my device the next time I normally do.