image caption: A Microsoft Windows screen showing “Active Hours” with start time set to 12 AM and end time set to 12 AM and an error that says “Choose an end time that’s no more than 18 hours from the start time”.

    • superkret@feddit.org
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      1
      ·
      edit-2
      3 months ago

      Same goes for Linux and macOS, actually, but Linux will happily let you keep your machine vulnerable to getting hacked for months.

      Linux “reboots” every program and service it updates separately.
      So the only update that needs a reboot is one of the kernel, which doesn’t happen often.
      With Enterprise Linux, you can update the kernel without a reboot, too.

        • Kusimulkku@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          3 months ago

          That’s why Linux and software like Firefox constantly complain when you haven’t restarted after an update.

          Can’t confirm. Linux hasn’t complained and I don’t remember Firefox complaining. Maybe it doesn’t happen with the flatpak

            • Kusimulkku@lemm.ee
              link
              fedilink
              English
              arrow-up
              1
              ·
              3 months ago

              I have zypper ps -s as part of my update script so I personally notice through that when something needs to be restarted. It’s pretty rare to have to do an actual reboot. A lot of the software stores notify if you need to restart. I’ve seen it on Discover and GNOME Store (?) at least

        • expr@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          Obviously there’s a small handful of things that would require a reboot, but unlike Windows, the vast majority of programs in user space don’t require reboots on update.

          There’s also the fact that restarting Windows to update is a much slower and more disruptive experience than restarting Linux.

      • corsicanguppy@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 months ago

        the only update that needs a reboot is one of the kernel

        Okay, that’s not true. Glancing at dbus sideways will result in a reboot. But in systems free of systemd and all its entourage of shit, that’s still true.

        • Something Burger 🍔
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          dbus is 4 years older than systemd, thus proving once again that systemd haters have no idea what they’re talking about.

        • superkret@feddit.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          But in systems free of systemd and all its entourage of shit, that’s still true.

          OK my bad, I don’t run systemd.

    • Empricorn@feddit.nl
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      3
      ·
      3 months ago

      Linux will happily let you keep your machine vulnerable to getting hacked for months.

      Sad you included this misinformation in your otherwise good comment. Linux fundamentally works different and you can often update binaries as well as the kernel without rebooting.

      And even if you couldn’t, that’s 100% a user problem. Every distro I’ve ever seen makes it clear as day when you do need to restart, so this is 100% a user issue. But I guess people will also complain if their OS forces them to reboot (like this post), so… 🤷🏼‍♂️

        • barsoap@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          3 months ago

          Replacing /usr/bin/firefox doesn’t fix anything if you don’t restart Firefox itself.

          On my box updating firefox and then restarting it won’t even launch the new version because NixOS knows I’m logged in and won’t just change things in my environment. But unless there’s a kernel update yes nixos rebuild switch followed by logging out and logging in is equivalent to rebooting as it will automatically shut down and restart all system services, I think even systemd itself. Modulo some wibbles around kernel modules but those fall under kernel updates in my book.

          Contrast Ubuntu, which really likes to prompt your for reboots. The difference between a distro primarily for desktop use and one that can also do desktop because also devops want a desktop. Hey I could spin up 1000 cloud instances of my desktop with a couple of keystrokes isn’t that impressively useless :)

        • Kusimulkku@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          I don’t know what Windows needs to do to get as good of a state as Linux but you rarely need to do a full reboot as you seemingly are forced to do on Windows.

            • Kusimulkku@lemm.ee
              link
              fedilink
              English
              arrow-up
              1
              ·
              3 months ago

              It does tell me. Zypper tells it outright and you’ll get a list with zypper ps -s. But like said, it’s very rare that you need to actually reboot. Restarting apps or services suffices.

              I’m doing a lot more restarting on Linux than I ever need to do on Windows

              Don’t know what’s up with that. With Windows it nagged about rebooting constantly. Seemingly every update. Meanwhile Linux can be just fine without, some stuff you need to restart but actual reboot is much rarer.

    • azuth@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      2
      ·
      3 months ago

      ROFL

      If Microsoft really cares for more users keeping their system updated they should fix their update process.

      While some updates require a reboot on other OSes for them to take effect they don’t require work during the reboot maximizing the downtime.

      Which is on top of the work done before rebooting, on the background, unprompted, destroying system performance.

    • kautau@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      2
      ·
      3 months ago

      With windows pro you can use Group Policy to disable them completely actually, though it’s obv not a good idea

      Open Group Policy Object Editor. Navigate to Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Update. Set Configure Automatic Updates to Disabled.

    • Kusimulkku@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      3 months ago

      This is because many (most?) updates aren’t actually applied until you reboot. Same goes for Linux and macOS, actually

      Yeah no for Linux at least.

    • lightnsfw@reddthat.com
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      2
      ·
      3 months ago

      Mine doesn’t reboot on it’s own and I don’t recall ever changing any settings to prevent it other than messing with the thing OP is talking about which wouldn’t let me turn it off. I get nag screens daily after a while but it never actually restarts. Maybe one of my applications prevents it or something.

    • corsicanguppy@lemmy.ca
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      2
      ·
      edit-2
      3 months ago

      Same goes for Linux and macOS, actually

      laughs in needs-restarting -s

      It’s weird that RPMs have been restarting apps affected by library updates for decades and you still haven’t clued-in. You new?