this post was submitted on 13 Sep 2023
61 points (83.5% liked)

Linux

48052 readers
733 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

Even back in the Windows 3.1 or 95 days I didn't have to reboot this often - sometimes twice a day. Seems a bit excessive?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 26 points 1 year ago (4 children)

I'm using the KDE version and updates come in automatically through Discover. They almost always announce in the system tray that a reboot is required.

[–] [email protected] 62 points 1 year ago (2 children)

You also don't have to reboot when Discover says to. It's just saying that the updates won't take effect until you reboot. It could probably be worded better, for sure.

[–] [email protected] 7 points 1 year ago (1 children)

I think that installing new versions often means that particular services need to be restarted. Rather than implement logic to restart relevant services, it probably just says "fuck it, reboot".

[–] [email protected] 12 points 1 year ago

Eh, no. It only downloads the packages, then asks you to reboot and installs the new packages during the boot process. This means you get a clean system afterward in which no pre-update binaries are being run anymore. It just comes at the price that you need a full reboot for something that usually needs a session relogin at worst.

[–] [email protected] 1 points 1 year ago (2 children)

On the other hand you rather have to put a gun to the average GUI user's head to get them to reboot ever, otherwise the computer will sit there for months on end until finally they shut it down once and it can finally apply updates.

[–] [email protected] 15 points 1 year ago (1 children)

Honestly that little reboot icon in the sys tray is sort of like a loaded gun pointed at me

[–] [email protected] 2 points 1 year ago (1 children)

This is exactly my issue, Just as I can't deal with unread notifications, I can't live with a pending update icon just sitting there.

[–] [email protected] 12 points 1 year ago (1 children)

Right click the up arrow > configure icons tray > second tab > reboot notification > disabled.

[–] [email protected] 2 points 1 year ago

So you don't want to hear about the arch box I leave hot and live for two months at a time?

[–] [email protected] 13 points 1 year ago (1 children)

sigh... i hate to say it but do your updates via command line because it will actually tell you if you need a reboot. As said above, it should only be for Kernel updates, and even then it will tell you that it will switch kernels next reboot and keep running on the current one.

Most desktop applications for doing updates ask you to reboot not because its needed, but because they are being "safe" or not running with the same user rights as you are in the terminal.

[–] [email protected] 4 points 1 year ago (4 children)

Why does no other distro do that though? I've tried a bunch before and this is the first time I get that notification sitting there taunting me.

[–] [email protected] 3 points 1 year ago

Hrm. Skim ahead if you already know some of this... So say you have a running program XYZ that loads libUseful.so to do useful things. Now you run some updates and libUseful.so gets replaced with the new version. Because of how files on Unix work, the old version still exists on the disk until XYZ closes it, but any new program will load the new version. So things generally "just work" when the system is updated in place, but on the rare occasion causes weird problems. Fedora (from the GUI) chooses to run updates during reboot to prevent the rare, weird problems. If you update from the command line, it just does them in place. Kernel updates always require a reboot to apply though.

[–] [email protected] 1 points 1 year ago* (last edited 11 months ago)

[This comment has been deleted by an automated system]

[–] [email protected] 1 points 1 year ago

After applying an update you need to make sure anything using the unmatched code is replaced by the patched code. A reliable way to do that is a reboot. Actually a reboot is pretty much the only reliable way to do that.

So I am not surprised that a distribution targeting end users asks for a reboot.

[–] [email protected] 1 points 1 year ago

It has been a while since I have used Fedora but this is not unique to that distro. Arch will also tell you to reboot if the kernel, systemd, and a few other packages are updated. I rarely do it right away though.

[–] [email protected] 2 points 1 year ago

Do you have offline updates enabled in the Discover settings by any chance?