(The screen normally remains white on black. The console can as well be a COM port.)
You can configure it to auto-reboot by putting a timeout value to /proc/sys/kernel/panic.
I actually scrolled up to check this was not an April fools article.
"A new component "systemd-bsod" has been added, which can show logged error messages full screen, if they have a log level of LOG_EMERG log level. This component is experimental and its public interface is subject to change."
First step is to log something with LOG_EMERG level. Then maybe make the system crash?
[0] https://github.com/systemd/systemd/issues/29478 [1] https://github.com/systemd/systemd/blob/main/test/units/test...
EDIT: just found an image, of how it looks https://0x0.st/H3qM.png
Another feature worth porting is systemd spawning around 100 processes, just like svchost.exe. /s
Years ago I had a dual boot system with bad RAM and on Windows it would regularly blue screen, on Linux it was fine. Took a long time to figure out what the actual problem was because Linux is just so rock solid.
And no, I don't use any systemd based distros on my daily drivers.
BSOD is very clearly an end user feature for folks who don’t have experience debugging kernel panics. If the QR code can generate a copy passable stack trace of the error the it could help make linux more mainstream and easier to debug for non technical folks.