reupload because i mixed up sigterm and sigkill like a dumb fuck

        • RustyNova@lemmy.world
          1·
          1 month ago

          In those cases there’s an easy solution.

          Step 1: sigh

          Step 2: press the power button 5 or 10 seconds while contemplating why you decided to do a quick restart instead of keeping the session and do something actually productive

          • KubeRoot@discuss.tchncs.deEnglish
            1·
            1 month ago

            I recommend starting with SysRq+E before that, there’s a chance it gets whatever the shutdown was waiting for. And if that fails… REISUB my beloved.

  • Wispy2891@lemmy.world
    0·
    1 month ago

    Reverse meme when it’s time to install the updates.

    Windows in that case is “I MUST REBOOT IMMEDIATELY PREPARE TO LOSE ALL UNSAVED DATA IN 3. 2. 1…”

    • Buddahriffic@lemmy.world
      0·
      1 month ago

      When I switched to win 10, I actually gave them more money to get the pro version for access to the group policy editor so I could control updates and never have to deal with my PC telling me it’s time to restart on its own. Because I was stupid.

      When it came time to switch to Win 11, I did the much more sensible thing and installed Fedora instead. I started with cinnamon and even though I ended up disliking it also, it was still way better than the windows experience.

  • empireOfLove2@lemmy.dbzer0.comOPEnglish
    0·
    1 month ago

    also yes i know shutdown typically uses sigterm and waits nicely, but it doesn’t take 45 seconds for no damn reason like windows

    also sigkill is funnier

    • Valmond@lemmy.dbzer0.com
      1·
      1 month ago

      Windows: the shutdown mechanism cannot execute correctly because this process is still running:

      ShutDownProcess

  • starman2112@sh.itjust.works
    01·
    1 month ago

    It’s not a request, it’s a warning. The machine will be without power soon, and it’s up to the machine whether it wants to prepare for that or not