Chewy7324@discuss.tchncs.de
on 07 Dec 2023 03:13
nextcollapse
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@pawb.social
on 07 Dec 2023 23:35
collapse
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).
autotldr@lemmings.world
on 07 Dec 2023 03:15
nextcollapse
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!
mateomaui@reddthat.com
on 07 Dec 2023 03:20
nextcollapse
EonNShadow@pawb.social
on 07 Dec 2023 05:57
collapse
The thought of someone’s Linux install failing catastrophically, displaying a “MSoS”, then the user switching back to the is MS OS because of it is funny to me.
Thorned_Rose@kbin.social
on 07 Dec 2023 07:42
nextcollapse
Back about two decades when I was using Windows and it was till easily customisable, I changed the bsod colour to red for funsies. Windows being Windows crashed and went to my red screen of death - my ex's cousin saw it and thought it was something really really bad, "Wow, a red screen, never seen that before. Must be even worse than blue". No mate, I just customise the shit out of anything I touch 😅
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.
that’s the goal, they also gonna implement the QR code, but not like the crappy of QR code on windows(that send you to a suppirt page with a dozen of possible sulution, where nothing work), the qr code is going translate to the kernel panic message, i liked, i can scan the qr code and search the error on my cell
rotopenguin@infosec.pub
on 07 Dec 2023 03:55
nextcollapse
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)
Infiltrated_ad8271@kbin.social
on 07 Dec 2023 05:53
nextcollapse
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@kbin.social
on 07 Dec 2023 06:29
nextcollapse
Use case is not having enough RAM?
lemmyvore@feddit.nl
on 07 Dec 2023 09:49
nextcollapse
Um, you really need to read the entire phrase and not pick out only what you want from it. 😃
Swap can make a system slower to OOM kill, since it provides another, slower source of memory to thrash on in out of memory situations
It means that if you try to use it as a source of memory, when you run out of actual RAM it will make your system almost completely unresponsive due to disk thrash, instead of allowing the kernel to just kill the process that’s eating your RAM. So you’ll just end up hard-booting system.
wmassingham@lemmy.world
on 08 Dec 2023 13:59
collapse
Yes, and that’s a good thing if you don’t want it to start killing processes. You have that extra time/space to deal with the out-of-memory condition yourself.
Or you can ignore that condition and continue using the system in a degraded state, with swap as “disk RAM”.
Like I said, the system will be almost completely unresponsive due to disk access being several orders of magnitude lower than RAM and allocation thrashing… you won’t be able to do much, the mouse, keyboard and display will react extremely slowly. There may be situations where you’d prefer this to an OOM kill, for example if you’re running a test or experiment where you’d rather have it finish even if it takes a very long time rather than lose the data. But if you’re a regular desktop user or server admin you’ll probably just reboot.
bdonvr@thelemmy.club
on 07 Dec 2023 20:01
collapse
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.
Infiltrated_ad8271@kbin.social
on 08 Dec 2023 05:42
collapse
Yep. 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@infosec.pub
on 07 Dec 2023 06:35
collapse
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.
Infiltrated_ad8271@kbin.social
on 08 Dec 2023 06:08
collapse
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?
Holzkohlen@feddit.de
on 07 Dec 2023 06:12
nextcollapse
At least make it pink or smth
wmassingham@lemmy.world
on 07 Dec 2023 14:03
nextcollapse
PSoD is already used by VMware ESXi. And Windows Insider builds, I think.
Maybe green?
ABeeinSpace@lemmy.world
on 07 Dec 2023 14:18
nextcollapse
Green is Windows Insider builds
mateomaui@reddthat.com
on 07 Dec 2023 19:06
nextcollapse
PSoD
Piss Screen of Death?
edit: oh nvm, I mistakenly thought this was in reply to the suggestion for dark yellow.
uriel238@lemmy.blahaj.zone
on 08 Dec 2023 00:20
collapse
Maybe a customizable setting? Black screen with red border and a looping kittens video?
AgnosticMammal@lemmy.zip
on 07 Dec 2023 14:26
nextcollapse
Maybe it can be the “brown screen of death”. To indicate that it shit itself.
NeoNachtwaechter@lemmy.world
on 07 Dec 2023 08:18
nextcollapse
Is it April 1st already?
NeoNachtwaechter@lemmy.world
on 07 Dec 2023 08:20
nextcollapse
I want it with Elon’s face in the backgrund, so that I can throw some darts at it!
avidamoeba@lemmy.ca
on 07 Dec 2023 08:36
nextcollapse
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.
MonkderZweite@feddit.ch
on 07 Dec 2023 16:07
collapse
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.
MonkderZweite@feddit.ch
on 07 Dec 2023 19:22
collapse
They use Systemd, so there.
Krafting@lemmy.world
on 07 Dec 2023 08:48
nextcollapse
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)
Yeah, Linux should have taken the guru meditation from the Amiga! (I know VirtualBox already copied it mind you)
palordrolap@kbin.social
on 07 Dec 2023 10:27
collapse
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.
Diplomjodler@feddit.de
on 07 Dec 2023 12:13
nextcollapse
Phantastic! Can we have ads in the task bar next?
KseniyaK@lemmy.ca
on 07 Dec 2023 17:43
nextcollapse
I 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@lemmy.blahaj.zone
on 08 Dec 2023 07:26
collapse
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
SeeJayEmm@lemmy.procrastinati.org
on 08 Dec 2023 14:16
collapse
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.
threaded - newest
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).
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!
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.
Mauve Screen of Suffering
Tosca Screen of Wailing
Crimson Screen of Grief
That almost sounds soothing.
Lilac of Log Level 1
I’m giving you bonus points for the alliteration.
The thought of someone’s Linux install failing catastrophically, displaying a “MSoS”, then the user switching back to the is MS OS because of it is funny to me.
Back about two decades when I was using Windows and it was till easily customisable, I changed the bsod colour to red for funsies. Windows being Windows crashed and went to my red screen of death - my ex's cousin saw it and thought it was something really really bad, "Wow, a red screen, never seen that before. Must be even worse than blue". No mate, I just customise the shit out of anything I touch 😅
Fuchsia Screen of Disappointment
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.
No, there is a random crash every six hours now to increase familiarity.
Unfortunately this only affects boot messages, not normal system operation, for that you still get core dumps and kernel panics / oops
A BSOD that gave you a clue about why it happened would be a welcome change.
that’s the goal, they also gonna implement the QR code, but not like the crappy of QR code on windows(that send you to a suppirt page with a dozen of possible sulution, where nothing work), the qr code is going translate to the kernel panic message, i liked, i can scan the qr code and search the error on my cell
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)
So, with btrfs on ssd, is there any use case for a swap partition?
Use case is not having enough RAM?
Swap is not “disk RAM”.
https://en.m.wikipedia.org/wiki/Virtual_memory
What would you describe it as? With virtual memory it pretty much functions that way, no?
chrisdown.name/2018/01/…/in-defence-of-swap.html
I’m not sure what that post is meant to show, if swap isn’t “disk RAM”. That post even concludes:
Um, you really need to read the entire phrase and not pick out only what you want from it. 😃
It means that if you try to use it as a source of memory, when you run out of actual RAM it will make your system almost completely unresponsive due to disk thrash, instead of allowing the kernel to just kill the process that’s eating your RAM. So you’ll just end up hard-booting system.
Yes, and that’s a good thing if you don’t want it to start killing processes. You have that extra time/space to deal with the out-of-memory condition yourself.
Or you can ignore that condition and continue using the system in a degraded state, with swap as “disk RAM”.
Like I said, the system will be almost completely unresponsive due to disk access being several orders of magnitude lower than RAM and allocation thrashing… you won’t be able to do much, the mouse, keyboard and display will react extremely slowly. There may be situations where you’d prefer this to an OOM kill, for example if you’re running a test or experiment where you’d rather have it finish even if it takes a very long time rather than lose the data. But if you’re a regular desktop user or server admin you’ll probably just reboot.
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.
Yep. 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.
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?
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
Piss Screen of Death?
edit: oh nvm, I mistakenly thought this was in reply to the suggestion for dark yellow.
Maybe a customizable setting? Black screen with red border and a looping kittens video?
Dark yellow?
Maybe it can be the “brown screen of death”. To indicate that it shit itself.
Is it April 1st already?
I want it with Elon’s face in the backgrund, so that I can throw some darts at it!
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.
They use Systemd, so there.
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)
Yeah, Linux should have taken the guru meditation from the Amiga! (I know VirtualBox already copied it mind you)
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
/procpseudo-file", or a sub-sub-sub-command of one of the manysystemd*commands which ultimately does the same thing.Phantastic! Can we have ads in the task bar next?
I 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.
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.
Came here to say this. Let them toggle the logs or the QR code.
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.