…and of course, this news is getting mixed reactions from the Linux nerds…
Back when I used Windows, I remember the BSOD’s being about as useful to me as someone pointing in opposite directions saying “he/she/they went that way.” So long as the new Linux blue screens provide info that’s actually useful in diagnosing the problem(s), I see no issues with this. [shrugs]
Do they have to be blue though? We all have collective PTSD from getting Windows BSODs.
Yeah, I totally get that, I have really bad memories myself.
If it’s an ncurses/similar interface that enables keyboard navigation through dmesg/journalctl, and provides info that allows us to properly diagnose it, I can see this being useful.
But yeah, I’ll admit that simply saying “BSOD’s are coming to Linux” without additional info about the implementation does bring feelings of dread in me.
Yep. I agree. And it looks like anything that makes it to
LOG_EMERGwill be shown on the screen as well as a QR code to look things up with. Seems like it’ll be pretty useful, honestly.
deleted by creator
Why’s that?
deleted by creator
That makes perfect sense, why know what caused the crash right away when you can manually check logs… fail.
Lots of assumptions in that reply bro. And why would you care how another man runs his boxen? I bet you also have a problem with what beer one drinks. Stay in your lane.
- I hope it’s not blue for heavens sake
- I hope it’s actually useful because Windows bsod is not at all.
- Systemd adding yet more stuff to it’s repertoire which I don’t think anyone asked for.
deleted by creator
As long as it can be the same colour as the terminal there’s literally no reason to Frank out and write sensationalized headlines. Even if it was hard coded blue it’s not from windows. The name is obviously a reference but isn’t going to have m$ code or somehow make the kernel worse. It also requires a log level config so any existing os install likely won’t be affected unless you do it yourself.
