Apparently, there’ll be a sysdemd update which gives some (most) Linux users a BSOD in the event of a boot failure. Based on this article, it would actually be useful, so I wouldn’t mind it, though I’m unlikely to ever experience it.
The only reason is to break Linux users minds.
P.S. Thanks, i HATE it.
1 Like
As long as you can disable it if not it’s a bug not a feature.
It is already shipped with
Name : systemd
Version : 255-1
man systemd-bsod.service
SYSTEMD-BSOD.SERVICE(8) systemd-bsod SYSTEMD-BSOD.SERVICE(8)
NAME
systemd-bsod.service, systemd-bsod - Displays boot-time emergency log message in full screen.
SYNOPSIS
systemd-bsod.service
systemd-bsod [OPTIONS...]
DESCRIPTION
systemd-bsod.service is used to display a blue screen which contains a message relating to a boot failure, inclu
ding a QR code which can be scanned to get helpful information about the failure.
OPTIONS
The following options are understood by systemd-bsod:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
-c, --continuous
When specified, systemd-bsod waits continuously for changes in the journal if it doesn't find any emergency messages on the initial attempt.
Added in version 255.
EXIT STATUS
On success (displaying the journal message successfully), 0 is returned, a non-zero failure code otherwise.
SEE ALSO
systemd(1)
systemd 255
$ systemctl status systemd-bsod.service
○ systemd-bsod.service - Displays emergency message in full screen.
Loaded: loaded (/usr/lib/systemd/system/systemd-bsod.service; static)
Active: inactive (dead) since Fri 2023-12-08 20:41:50 CET; 13min ago
Duration: 430ms
Docs: man:systemd-bsod.service(8)
Main PID: 202 (code=killed, signal=TERM)
CPU: 9ms
Dec 08 20:41:50 archlinux systemd[1]: Stopping Displays emergency message in full screen....
Dec 08 20:41:50 archlinux systemd[1]: systemd-bsod.service: Deactivated successfully.
Dec 08 20:41:50 archlinux systemd[1]: Stopped Displays emergency message in full screen..
1 Like
Good point.
Oh, wow. 
Loaded: loaded (/usr/lib/systemd/system/systemd-bsod.service; static)
static …
means you only can mask it…
2 Likes
Well now I finally understand systemd haters… 
Yeah, pour all you hate over BSOD but what is actually objectively wrong with showing
2 Likes
As I said:
Unless you’re referring to keybreak and bitterhalt.
i found this funny
“Users will no longer need to trundle around countless forums and articles. With the BSOD system in place, their troubleshooting will be more in line with what many are already used to.”
No sure what planet writer live on !
forums will now just get tile of thread " HELP " + screenshot of blue screen + with message
" how to fix this "
1 Like
system give you the D . . . an excellent implementation of a bad idea . . . why did this take over everywhere?
We don’t need systemd journal anymore! How cool is that 
