I use PCLinuxOS as my primary Linux OS. They are a bit conservative to adapt new updates until they are sure of stability because of rolling nature. KDE is still at 5 there. Heard about Neon and wanted to try KDE 6. I find that they have adopted Windows style approach to updates where we need to reboot to apply the updates and we cannot do anything on the system while the updates are processing. Recently managed to install Fedora because I heard that their EFI is secured or something and can survive clobbering by Windows updates in a dual boot setup. But they also seem to have gone with offline updates.

Are offline updates necessary due to them using SystemD or is the Linux world in general moving in this direction?

  • f00f/eris@startrek.websiteEnglish
    12·
    6 months ago

    It’s not systemd’s fault, though systemd most often implements offline updates. The arguments for and against offline updates have nothing to do with systemd.

    A lot of Linux distros, and graphical package managers like Discover and GNOME Software, are moving in that direction, under the argument that updating while online can cause disruptions to running software, in the worst case including the package manager itself (which can brick the system if it occurs in the middle of a critical update), and updates can’t be applied until the affected program (or the system, in case of critical components like the kernel) restarts anyway. Fedora Magazine explains the reasoning here: https://fedoramagazine.org/offline-updates-and-fedora-35/

    In my personal experience though, I have never had an issue enabling automatic online updates on Debian Stable, and have had computers stay online for several months without any noticeable issues beyond Firefox restarting, so the risk is there but it’s pretty minor.

    • Max-P@lemmy.max-p.meEnglish
      6·
      6 months ago

      And also with the atomic/immutable distros, the switch is practically instant, so it’s not even like it forces you to watch a spinning circle for 20 minutes when you turn off your computer. You reboot and the apps all start clean with the right library versions.

      It’s rare but I’ve seen software trash itself because the newly spawned process talks a different protocol and it can lead to either crashes or off behavior that leads to a crash eventually. Or it tries to read a file mid update. Kernel updates can make it so when you plug in a USB stick, nothing happens because the driver’s gone. Firefox as you mentionned. Chromium will tolerate it mostly but it can get very weird over time.

      The risk is non-zero, so when you target end users that don’t want to have to troubleshoot, it’s safer to just do offline updates. Especially with Flatpaks now, you get those updated online and really it’s only system components you don’t care to delay updates taking effect

      If you’re new to Linux and everyone told you you can just update and no reboot, and you run into weird Firefox glitches, it just looks bad.

  • u/lukmly013 💾 (lemmy.sdf.org)@lemmy.sdf.orgEnglish
    2·
    6 months ago

    It does sound like a good idea.

    Mid-update you can end up with broken dependencies and thus not fully working system. There may also be a problem with how programs update their config files.
    This is especially true with big updates which is why Arch and Manjaro recommended to update from plain TTY during the Plasma 6 upgrade. Reboot, do not login, switch to TTY, stop the graphical login manager, just then proceed with upgrade.
    A bit too much to ask for from regular users. Especially since it relies on them reading update announcements before each update.

    Personally, I always close most stuff during updates. I even had terminal emulator itself die during update on Linux Mint.