That makes perfect sense, why know what caused the crash right away when you can manually check logs… fail.
Comment on New systemd update will bring Windows’ infamous Blue Screen of Death to Linux
nobleshift@lemmy.world 11 months ago
[deleted]
random65837@lemmy.world 11 months ago
nobleshift@lemmy.world 11 months ago
[deleted]random65837@lemmy.world 11 months 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? LOL! “Stay in your lane” LOL!
leo@lemmy.linuxuserspace.show 11 months ago
Why’s that?
nobleshift@lemmy.world 11 months ago
leo@lemmy.linuxuserspace.show 11 months 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.