I thought I would never have to see BSOD after switching to linux, but here we go…
[ tbh, I love that errors are presented much better, just that the name doesn’t bring back much good memories.
Finally, my life is complete. We have achieved feature parity with Windows.
Seriously, the BSOD QR-code is a great way to have a more inclusive system. Hardened geeks can still sift through the boot log to find problems and newbies can just get help online. Win-win.
I hope it supports themes. I’d like to make my BSOD look like the classic Windows 9x BSOD.
The systemd-bsod will also display a QR code for getting more information on the error causing the boot failure.
That’s pretty neat. Nowadays with the proliferation of smartphones that’s an easy way to move straight to troubleshooting the issue
This is the best summary I could come up with:
Systemd 255 even is introducing systemd-bsod as a “Blue Screen of Death” for displaying important error messages during boot failure, systemd-vmspawn as a new tool to spawn virtual machines, and other new features.
It’s not an off-timed April Fool’s prank or anything, there is finally a systemd-bsod service for “Blue Screen of Death” full-screen error messages on Linux…
-
Systemd’s bootctl will now show whether the system was booted from a Unified Kernel Image (UKI).
-
systemctl will now automatically soft-reboot into a new root file-system if found under /run/nextroot/ when a reboot operation is invoked.
-
A new option “SurveFinalKillSignal” has been added to skip the final SIGTERM/SIGKILL spree on shutdown in order to survive soft-reboot operation.
-
A new “ConditionSecurity=measured-uki” option for only running when the system has been booted via a measured Unified Kernel Image (UKI).
The original article contains 520 words, the summary contains 139 words. Saved 73%. I’m a bot and I’m open source!
