It should be noted that a reboot should be done so your systems starts with the new packages/libraries.
Updating doesn't mean you are automatically running the new installed files. Some people mistake an upgrade for a fully updated kernel/services running in memory. Some you can get away with by restarting the services.
If you happen to be on a zypper package manager run zypper ps -s, it will list packages that have been installed but are pending a restart, moreso it notes things running on deleted files.
True, true. But there's miles and miles of difference between "You should reboot at your earliest convenience, but it's ultimately optional" and "Microsoft's computer is rebooting NOW -- better hope you weren't planning on doing anything important in the next 30 minutes."
(Oh yeah, and about that '30 minutes' part -- On Linux, you reboot to apply updates that are already installed. The update reboot doesn't take any longer than any normal reboot. On Windows, for some dumbass reason, the update has to be installed during the reboot, which can make the mandatory reboot take much, much longer than a normal boot.)
The trick on Windows is to set your networks as Metered connections, it then let's you know there are updates but won't downloaf/apply them till you ask it to.
It sucks though because you have to unoause one drive a lot to sync files.
For some reason Fedora does the same shit when you update from the Software app. Gnome version, perhaps KDE is different. And I really don’t understand why, as dnf update does the thing as it should be.
Same on OpenSUSE. Seems CLI update is normal way, the GNOME software updater seems to handle it slightly different, and you get a checkbox If you shutdown that says "install pending updates"
On the KDE version you just get a permanent notification in the tray reminding you that you should reboot. It can so it automatically though if you choose so in the Discover app.
But will it install those updates during the reboot? Or will it update just to apply the updates?
As the Gnome version (non-mutable, meaning not Silverblue) does not update a thing, even a browser. It updates during the reboot, by rebooting into some special state, akin to macOS (and perhaps Windows, haven’t been using one for decades) then it reboots again.
Since the latest update of Fedora (50? I lost the count at this point) it does the reboot even when you ask to shutdown the computer after updates.
I haven’t checked whether dnf update updates things right away (like browser), mostly because that’s a shared family computer, which I don’t touch most of the time. And I try to use it as I use macOS (as a normie would use), just to check out whether it’s a viable system yet. (It mostly is, but there are weird bugs that’s easy to resolve only when you’re knowledgeable of Linux.)
But it does not do the extra reboot and install updates thing. That’s why I’m puzzled why is it there in the first place?
As the Gnome version (non-mutable, meaning not Silverblue) does not update a thing, even a browser. It updates during the reboot, by rebooting into some special state, akin to macOS (and perhaps Windows, haven’t been using one for decades) then it reboots again.
Since the latest update of Fedora (50? I lost the count at this point) it does the reboot even when you ask to shutdown the computer after updates.
What the fuck?
My interest in ever using Fedora has now decreased even further. What are they trying to do, copy the shitty Windows update method exactly? No other Linux distro I've ever tried has done shit like that.
Hey, but in general Fedora is very good and I can recommend it. This annoying update behaviour bears some meaning for some reason, so I can tolerate that.
It’s not that the system forces you to update. It’s you who is in control. Most times updates take minutes, with version upgrades taking like half an hour (twice a year).
It should be noted that a reboot should be done so your systems starts with the new packages/libraries.
Updating doesn't mean you are automatically running the new installed files. Some people mistake an upgrade for a fully updated kernel/services running in memory. Some you can get away with by restarting the services.
If you happen to be on a zypper package manager run zypper ps -s, it will list packages that have been installed but are pending a restart, moreso it notes things running on deleted files.
Maybe there is a similar command for apt
True, true. But there's miles and miles of difference between "You should reboot at your earliest convenience, but it's ultimately optional" and "Microsoft's computer is rebooting NOW -- better hope you weren't planning on doing anything important in the next 30 minutes."
(Oh yeah, and about that '30 minutes' part -- On Linux, you reboot to apply updates that are already installed. The update reboot doesn't take any longer than any normal reboot. On Windows, for some dumbass reason, the update has to be installed during the reboot, which can make the mandatory reboot take much, much longer than a normal boot.)
The trick on Windows is to set your networks as Metered connections, it then let's you know there are updates but won't downloaf/apply them till you ask it to.
It sucks though because you have to unoause one drive a lot to sync files.
For some reason Fedora does the same shit when you update from the Software app. Gnome version, perhaps KDE is different. And I really don’t understand why, as
dnf updatedoes the thing as it should be.Same on OpenSUSE. Seems CLI update is normal way, the GNOME software updater seems to handle it slightly different, and you get a checkbox If you shutdown that says "install pending updates"
Yes, it’s exactly like this.
On the KDE version you just get a permanent notification in the tray reminding you that you should reboot. It can so it automatically though if you choose so in the Discover app.
But will it install those updates during the reboot? Or will it update just to apply the updates?
As the Gnome version (non-mutable, meaning not Silverblue) does not update a thing, even a browser. It updates during the reboot, by rebooting into some special state, akin to macOS (and perhaps Windows, haven’t been using one for decades) then it reboots again.
Since the latest update of Fedora (50? I lost the count at this point) it does the reboot even when you ask to shutdown the computer after updates.
I haven’t checked whether
dnf updateupdates things right away (like browser), mostly because that’s a shared family computer, which I don’t touch most of the time. And I try to use it as I use macOS (as a normie would use), just to check out whether it’s a viable system yet. (It mostly is, but there are weird bugs that’s easy to resolve only when you’re knowledgeable of Linux.)But it does not do the extra reboot and install updates thing. That’s why I’m puzzled why is it there in the first place?
What the fuck?
My interest in ever using Fedora has now decreased even further. What are they trying to do, copy the shitty Windows update method exactly? No other Linux distro I've ever tried has done shit like that.
Hey, but in general Fedora is very good and I can recommend it. This annoying update behaviour bears some meaning for some reason, so I can tolerate that.
It’s not that the system forces you to update. It’s you who is in control. Most times updates take minutes, with version upgrades taking like half an hour (twice a year).
Oh yeah, no, that's the same on KDE, I thought you were just referring to the automatic reboot thing, my bad.
Also don't know if it works differently with dnf, since it never bothered me that much
Debianite distros have /var/run/reboot-required. It doesn't tell you which packages, though, just if you should reboot.