Avid Amoeba ( @avidamoeba@lemmy.ca ) 69•7 months agoI 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.
MonkderZweite ( @MonkderZweite@feddit.ch ) 6•7 months agoIsn’t this the default behavior of all(?) modern *nix init? Maybe not SysV, i don’t know.
Avid Amoeba ( @avidamoeba@lemmy.ca ) 3•7 months agoIs it? I’ve been on Debian/Ubuntu since 2005 and I’ve never seen anything on-screen whenever I’ve gotten a kernel oops.
MonkderZweite ( @MonkderZweite@feddit.ch ) 5•7 months agoThey use Systemd, so there.
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.
KiranWells ( @KiranWells@pawb.social ) 3•7 months agoActually 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).
-
Holzkohlen ( @Holzkohlen@feddit.de ) 25•7 months agoAt least make it pink or smth
AgnosticMammal ( @AgnosticMammal@lemmy.zip ) 2•7 months agoDark yellow?
KseniyaK ( @KseniyaK@lemmy.ca ) 22•7 months agoI hope this isn’t going to be the default. I know, the average granny might prefer to have a BSOD with a QR code, but I think a lot of the people who are more tech-savvy, like me, would prefer to see log messages when booting because then you could see which service failed and why or why it’s all of a sudden taking so long to boot. That’s also why I choose not to have a splash screen when booting.
Anyways, this BSOD thing doesn’t apply to me because I use Gentoo with OpenRC.
itslilith ( @itslilith@lemmy.blahaj.zone ) 6•7 months agoI’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
𝓢𝓮𝓮𝓙𝓪𝔂𝓔𝓶𝓶 ( @SeeJayEmm@lemmy.procrastinati.org ) 6•7 months agoJust let me hit ESC and see the panic.
pl_woah ( @pl_woah@lemmy.ml ) 1•7 months agoCame here to say this. Let them toggle the logs or the QR code.
Infiltrated_ad8271 ( @Infiltrated_ad8271@kbin.social ) 15•7 months ago- Hibernation into swap files backed by Btrfs are now supported.
So, with btrfs on ssd, is there any use case for a swap partition?
falsem ( @falsem@kbin.social ) 17•7 months agoUse case is not having enough RAM?
lemmyvore ( @lemmyvore@feddit.nl ) English5•7 months agoSwap is not “disk RAM”.
falsem ( @falsem@kbin.social ) 11•7 months agohttps://en.m.wikipedia.org/wiki/Virtual_memory
What would you describe it as? With virtual memory it pretty much functions that way, no?
bdonvr ( @bdonvr@thelemmy.club ) 2•7 months agoI 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.
Infiltrated_ad8271 ( @Infiltrated_ad8271@kbin.social ) 1•7 months agoYep. In fact my comment seemed so clear to me that I assumed it was some kind of joke, but looking at the votes, maybe swapfiles aren’t as well known as I thought.
rotopenguin ( @rotopenguin@infosec.pub ) English5•7 months agoDo 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.
Infiltrated_ad8271 ( @Infiltrated_ad8271@kbin.social ) 1•7 months agoI’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?
rotopenguin ( @rotopenguin@infosec.pub ) English13•7 months agoI 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)
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!
-
setVeryLoud(true); ( @isVeryLoud@lemmy.ca ) 4•7 months agoGood 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.
Diplomjodler ( @Diplomjodler@feddit.de ) 4•7 months agoPhantastic! Can we have ads in the task bar next?