• corsicanguppy
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 hours ago

    No. Its because windows read-locks everything.

    In Linux we have post-install scripts to ensure relevant stuff gets restarted as long as it was installed properly. (The improperly installed shit can go fuck itself)

    The only time you need to reboot is when you’ve upgraded your kernel without kstuff/ksplice or you’ve glanced at dbus a little sideways.

    • auzy@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 hours ago

      sigh

      Post-Install scripts don’t fix 100% of the issue and dynamic lazy linking is a real thing.

      The read-only thing really isn’t the main issue here, and everyone including windows has a way to do post installation stuff, and has a service manager

      As an example, a few years ago my system kept erroring due to a gstreamer update. Reboot fixed it (I only remember it because the bug reports were only recently closed).

      Probably because apps had half loaded old versions, and were lazy linking new versions.

      Furthermore, without doing this, self-recovery is difficult. Because if you update something today, and reboot a week later and your system doesn’t boot, you have no idea what caused it. You’d have to keep rolling back. If you do it on reboot, you can snapshot, update, and if system fails, then rollback automatically after losing nothing.

      There’s lots of good reasons