As a full time desktop Linux user since 1999 (the actual year of the Linux desktop, I swear) I wish all you Windows folks the best of luck on the next clean install 👍

…and Happy 30th Birthday “New Technology” File System!

    • herrvogel@lemmy.world
      link
      fedilink
      English
      arrow-up
      30
      arrow-down
      2
      ·
      edit-2
      1 year ago

      Many Linux package managers themselves tell you you should reboot your system after updates, especially if the update has touched system packages. You can definitely run into problems that will leave you scratching your head if you don’t.

    • pacoboyd@lemm.ee
      link
      fedilink
      English
      arrow-up
      28
      arrow-down
      1
      ·
      1 year ago

      *nix systems are not immune to needing reboots after updates. I work as an escalation engineer for an IT support firm and our support teams that do *nix updates without reboots have DEFINATELY been the cause of some hard to find issues. We’ll often review environment changes first thing during an engagement only to fix the issue to find that it was from some update change 3 months ago where the team never rebooted to validate the new config was good. Not gonna argue that in general its more stable and usually requires less reboots, but its certainly not the answer to every Windows pitfall.

      • havokdj@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        2
        ·
        1 year ago

        The only time you truly need to reboot is when you update your kernel.

        The solution to this problem is live-patching. Not really a game changer with consumer electronics because they don’t have to use ECC, but with servers that can take upwards of 10 minutes to reboot, it is a game changer.

        • UnsafePantomime@lemmy.world
          link
          fedilink
          English
          arrow-up
          6
          ·
          1 year ago

          We have an Ubuntu machine at work with an NVIDIA GPU we use for CUDA. Every time CUDA has an update, CUDA throws obtuse errors until reboot.

          To say only kernel updates require reboot is naive.

          • havokdj@lemmy.world
            link
            fedilink
            English
            arrow-up
            4
            ·
            1 year ago

            Damn yeah I didn’t think of that either. Alright, scratch what I said. The point still stands that you very rarely need to update outside of scenarios containing very critical processes such as these, those of which depend on what work you do with it.

            It’s been a long slow night and morning and I was half awake when I said that. Hell I’m still half awake now, just disregard anything I’ve said.

        • rambaroo@lemmy.world
          link
          fedilink
          English
          arrow-up
          6
          ·
          1 year ago

          This isn’t true, I had to reboot debian the other day to take an update to dbus which is not part of the kernel.

      • bremen15@feddit.de
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        9
        ·
        1 year ago

        Seems to be sloppy engineering. We ran a huge multi site operation on Linux and did not need to.