On 12/9/19 8:49 AM, John Mellor wrote:
On 2019-12-09 12:08 a.m., Ed Greshko wrote:
On 2019-12-09 12:31, Eddie G. O'Connor Jr. wrote:
Ok.....so I'm just gonna ask, because I've noticed something. There was a time I could update my machine (Lenovo ThinkPad T-430 / T-420 laptops.) that wouldn't take long and I'd be able to continue to use my machines for hours until I was ready to either reboot, shutdown, etc. Is it me?...or has recently Fedora started to behave like Windows?....in the fact that now when I do updates?....I HAVE to reboot my machine!!!???? I thought the whole premise of moving away from having to reboot for each and every update, patch, and fix was one of the major reasons some people LEFT Windows to BEGIN WITH!? Is this going to be the "norm"?.....is it because Microsoft has integrated themselves within the Open Source community that now.....the community is starting to behave like WINDOWS!?.....because if so?...I may have to start looking for another distro. The days of me having to reboot just because the SYSTEM wants me to?......SHOULD have ended with the cessation of my usage ofI assume GNOME is your desktop, yes?
Microsoft Windows.
Why not just update from the command line? "dnf update". Then you can decide if you'd like to reboot.
Eddie, I agree fully. 99% of the updates do not require a reboot. The only exception that I can think of is a breaking API change, and those should not exist in a given release. Indeed, Ubuntu explicitly guarantees that a breaking change will not happen until the next release, and they use a backport repo section in order to stop breaking changes from happening.
I have had a Firefox issue after update twice in the past, and I assume that would be because Mozilla broke their API between versions, but that's about it. However, most packages follow semantic versioning rules, and a breaking API change always requires a major version number shift. Its almost trivial for the updater to check for a major version shift in a package that is running, and flag that a reboot is required only in that situation. And even then, unless its the kernel, it should require a user logout/login instead of a reboot.
The bogus Gnome requirement to reboot is IMHO based upon faulty thinking, and needs to be corrected.
--
John Mellor, Build/Release Engineer
KDE does not impose any reboot requirements. My problem has
always been not getting any good advice on when a reboot is
required. One thing I always reboot for, is a kernel
update. Especially if I am having issues with the current kernel
(taking too long to load a Web page after clicking on a link in an
e-mail client, for example). But for anything else, I'm just
guessing.
I'm likely going to be passing
$ sudo dnf needs-restarting
more often for awhile, just to see what turns up.
Temlakos
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
