• Noble Shift@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    And I will be adding it’s disablement and replacement to my pre/post install scripts …

      • Noble Shift@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        I’ve been using *nix daily since 1998 and over that time I have developed a particular way I like to set things up and run them, especially with VMs & Farms. I prefer having central reporting, so unless a box hangs on boot, having a BSOD is essentially useless to me.

        Now on a laptop I might just leave it, and of course I’ll check it out before committing to anything, but essentially it’s a feature I don’t need.

        • Leo@lemmy.linuxuserspace.showOPM
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          If the reason for the boot hang ends up in LOG_EMERG, it’ll be available to you on the “bsod” screen and show a QR code too, so not useless for you, if that’s the case. But running things the way you want is understandable.

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

      That makes perfect sense, why know what caused the crash right away when you can manually check logs… fail.

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

          Not a single assumption was made, only that you’d take something simple and make it more work. That’s not debatable, something you have to track down in logs, vs have right in front of you is more work. I’ve been running Linux as my main OS since RH8 Desktop, did you think that mattered? “Stay in your lane” LOL!