• mrgoosmoos@lemmy.ca
      link
      fedilink
      English
      arrow-up
      9
      ·
      8 days ago

      one of the reasons I’m moving away. pisses me off so much at work, I don’t even want it at home

  • Squiddork@lemmy.world
    link
    fedilink
    arrow-up
    31
    arrow-down
    1
    ·
    edit-2
    9 days ago

    Managed to wreck my NVMe drive with an unsafe shutdown on linux the other week, gave it a few hours for the self check, booted back into the distro and has been running fine ever since.

    Pretty sure windows would’ve just set the computer on fire at this point.

    • LordAmplifier@pawb.social
      link
      fedilink
      English
      arrow-up
      6
      ·
      8 days ago

      That’s weak. I always pull on the power cord until the plug comes out. That shuts it down in a second flat.

      • Avid Amoeba@lemmy.ca
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        8 days ago

        I was talking about a laptop with non-removable battery of course! I turn off my desktop via Zigbee remote hooked to Home Assistant which flips a Zigbee power switch that the AC power cord is hooked up to. Even faster death than going under the desk and unplugging the power cord. Even just unplugging itself takes time.

    • Quik@infosec.pub
      link
      fedilink
      arrow-up
      3
      ·
      7 days ago

      This is so fucking annoying. Whenever you try to run something not clearly meant for the desktop, there is like a 80/20 chance that you can completely forget suspend…

    • ragas@lemmy.ml
      link
      fedilink
      arrow-up
      7
      ·
      9 days ago

      “&&” will only run shutdown if the update runs correctly.

      I do “;” to definitely run the shutdown after the update process exits. (Don’t want to keep the system running if nothing is happening any more.)

      • Successful_Try543@feddit.org
        link
        fedilink
        arrow-up
        5
        ·
        8 days ago

        I do “;” to definitely run the shutdown after the update process exits.

        If you’re able to successfully boot the machine afterwards is not your concern?

        • ragas@lemmy.ml
          link
          fedilink
          arrow-up
          3
          ·
          8 days ago

          I don’t know about arch but my system usually boots fine after an upgrade. (Gentoo here)

              • Successful_Try543@feddit.org
                link
                fedilink
                arrow-up
                1
                ·
                8 days ago

                No. It will boot the previous kernel, but the user experience will be at least suboptimal if some packages have already been removed during the upgrade, but the upgrade stopped at some point because a downloaded package was corrupt, leaving lots of dependent packages unconfigured. In case networking doesn’t work, it’s also inconvenient to manually download the affected package on another machine and transfer it with a usb stick onto the computer to restart the upgrade.

    • baltakatei@sopuli.xyz
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      9 days ago

      Assuming you enter your password upon running sudo, isn’t there the risk of sudo’s privilege timing out if pacman takes too long to complete? I believe I tried something similar, intending to run a one-liner I could start then walk away from. However, I ended up returning to see the system not rebooted hours later.

      Or is yes somehow supposed to take care of this? Sorry, newish Debian user here who hasn’t ventured outside the distribution much.

      • Successful_Try543@feddit.org
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        9 days ago

        Yes, in this command one liner, the system should not power off when the update took too long.

        Or is yes somehow supposed to take care of this?

        No, yes is simply answering all questions asked during the update procedure (start upgrade, replace config files, restart services) with “yes”.

        • somerandomperson@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          9 days ago

          There’s no timeout for sudo. When permitted, a process runs as root and then closes.

          Also, the system will still shutdown when update fails because pipes do not care if previous commands exit with a nonzero code, unless pipefail is set.

          Edit: i’m blind.

      • Matriks404@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        edit-2
        8 days ago

        The command after && runs only if the previous command returns non-error exit status (0), if pacman returns error the latter command won’t be executed.

        Additionally there’s probably a configuration option for sudo for it to not time out, but it doesn’t matter since you can just use systemctl reboot as a normal user to reboot your system (at least on Debian). If that’s too long I recommend to add this to your .bashrc (if you use Bash): alias reb='systemctl reboot' or something similar.

        • Ziglin (it/they)@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          8 days ago

          Maybe this is just a yay thing but I think if sudo priveleges run out while downloading the files it prompts you for your password again before performing the changes. That would lead to it either trying to use the yes output or getting stuck in the password prompt, only failing in the prior.

          This entire problem could be solved by just running it as the root user.

  • AlsaValderaan@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    9
    ·
    8 days ago

    On my work PC I disabled automatic restarts and I’ll just hibernate it for weeks at a time, keeping my work stuff open. Convenient, and I can install updates when I choose to.

    • vithigar@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      7 days ago

      It’s much less risky than it used to be. Journaling filesystems reduce the risk of filesystem corruption to near zero and are fairly ubiquitous now on non-removable media.

  • Endymion_Mallorn@kbin.melroy.org
    link
    fedilink
    arrow-up
    8
    arrow-down
    2
    ·
    9 days ago

    Y’all don’t delete WSUS, block all of the M$ IPs at both your HOSTS file and your router, and stop all update processes?

    Do you even know how Windows works?

    • Onomatopoeia@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      16
      ·
      9 days ago

      Yea, it has a robust rollback system, which is part of why it takes so long now.

      But… I only do updates a couple times a year to minimize the headache on my personal machines.

      My work machines it’s not my problem, but I reboot them at night a couple times a week, just in case.

    • tyler@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      9 days ago

      Compared to Mac? Mac’s is so much better? The number of times windows has fucked me over by updating on a restart.

      • Aurenkin@sh.itjust.works
        link
        fedilink
        arrow-up
        2
        ·
        9 days ago

        Fair enough. My experience on Mac has been pretty bad compared to Windows but to be honest there could be recency bias there. I use Mac every day for work and don’t use Windows very often but at least Windows has never suddenly closed all my apps because it decided it was time to update.

        • LwL@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          8 days ago

          I think you got lucky then, windows is known to do exactly that. Well, these days it at least gives you a warning that it will do it in 15 minutes or so.

        • tyler@programming.dev
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          8 days ago

          That is crazy because that’s literally what windows is known for haha. My wife’s gaming computer has restarted probably six times just this year without her wanting to just to install updates.

          What I’m guessing is happening is that your work has MDM enabled on your device and forces the updates through. That’s exactly what happened with the Mac work computers I’ve had while my home Mac laptops have never done that.

          • Aurenkin@sh.itjust.works
            link
            fedilink
            arrow-up
            1
            ·
            8 days ago

            Yeah it sounds like I’m just out of touch with the modern Windows usage experience by the sound of it. It really sucks that it’s gotten so bad, I would be so pissed off if that happened when I was playing a game or something.