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?

  • cygnus@lemmy.caOP
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    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.

    • slembcke@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      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.

    • LeFantome@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      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.

    • Tobias Hunger@programming.dev
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      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.