2y ago

systemd 255 Released With A "Blue Screen of Death" For Linux Systems

www.phoronix.com

Linux @lemmy.world

misk @sopuli.xyz

2y ago

systemd 255 Released With A "Blue Screen of Death" For Linux Systems

www.phoronix.com /news/systemd-255

56 comments

I love this! Not only for the comedic value, but throwing kernel oopses on-screen when they can't be easily captured when unprepared would be of great help in solving system problems. Unlike the cryptic messages Windows displays, Linux kernel messages are quite useful.
- Isn't this the default behavior of all(?) modern *nix init? Maybe not SysV, i don't know.
  
  Is it? I've been on Debian/Ubuntu since 2005 and I've never seen anything on-screen whenever I've gotten a kernel oops.
Some Highlights:
A new component "systemd-bsod" has been added to show logged error messages full-screen if they have a "LOG_EMERG" log level. This is intended as a tool for displaying emergency log messages full-screen on boot failures. Yes, BSOD in this case short for "Blue Screen of Death". This was worked on as part of Outreachy 2023. The systemd-bsod will also display a QR code for getting more information on the error causing the boot failure.
Hibernation into swap files backed by Btrfs are now supported.
Support for split-usr has been removed.
- Actually looking forward to the btrfs swapfile hibernation; I have tried setting it up on my machine before but the documentation was never clear on whether it would work (or why mine wasn't).
Seems like some kind of sacrilege.
- i totally understand if they named it bsod just for the meme, it's funny also they could make an option to change de color :b
  
  They could have gone with the “Red Screen of Wrath” or something.
- Agreed, bsod is precisely what I’ve been running from with Linux.
  
  Correct me if I'm wrong but isn't this basically just better error reporting? It's not like it's gonna crash more often, it will just actually show log info if something catastrophic happens.
I just wish they would use another name for it, it's linux here no need to copy windows slang! Or use another color! (I hope they'll update it to make it a customizable color)
- Fun fact: The Windows BSOD colour was as easy as adding a couple of lines to a .INI file for a long time. Then, as they tend to do, they made it more difficult, but it was still possible. Third party tools were written to do the work.
  Very recent MS Windows I have no idea about. My search-fu is failing me.
  Anyway, my point is that the "two lines in a config file" method would be nice.
  Knowing systemd though, it'll be "send some kind of message into a /proc pseudo-file", or a sub-sub-sub-command of one of the many systemd* commands which ultimately does the same thing.
- Yeah, Linux should have taken the guru meditation from the Amiga! (I know VirtualBox already copied it mind you)
At least make it pink or smth
- PSoD is already used by VMware ESXi. And Windows Insider builds, I think.
  Maybe green?
  
  Green is Windows Insider builds
  
  Maybe a customizable setting? Black screen with red border and a looping kittens video?
  
  PSoD
  Piss Screen of Death?
  edit: oh nvm, I mistakenly thought this was in reply to the suggestion for dark yellow.
- Dark yellow?
- Maybe it can be the "brown screen of death". To indicate that it shit itself.
- I'm honestly fine if this is the default for beginner distros, as long as it's easy to disable and there is still a way to get to the logs
  
  Just let me hit ESC and see the panic.
Hibernation into swap files backed by Btrfs are now supported.
So, with btrfs on ssd, is there any use case for a swap partition?
- Use case is not having enough RAM?
  
  I think what they mean is that you can just make a swap FILE instead, which you can grow and shrink as needed. No need to mess with partitioning.
  
  Swap is not "disk RAM".
- Do you mean that you don't have to find the LBA of the extents of your swap file, and put that into a kernel argument anymore?
  Cuz that is a nasty, skanky hack.
  
  I've never heard of that, it's beyond me. So it's an increased risk when tweaking the kernel? As an average home user it's all right?
I don't think it's going to do a whole lot of good when the whole KMS/DRM falls over.
(okay I haven't had that for a few months now. But i am still traumatized)
Good idea, stupid name.
Excellent for causing FUD.
No, this will not increase the amount of kernel panics you see. It just makes them more informational to the average person. Technical folks can disable it, non-technical folks won't know how to enable it, so on by default it is.
This is the best summary I could come up with:
Ahead of the holidays systemd 255 has debuted as stable and comes with systemd-bsod as a "Blue Screen of Death" service capable of displaying full-screen error messages on Linux.
This is intended as a tool for displaying emergency log messages full-screen on boot failures.
The systemd-bsod will also display a QR code for getting more information on the error causing the boot failure.
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.
The original article contains 490 words, the summary contains 123 words. Saved 75%. I'm a bot and I'm open source!
I want it with Elon's face in the backgrund, so that I can throw some darts at it!
Is it April 1st already?
Phantastic! Can we have ads in the task bar next?

56 comments