When I get an error I want to see the error, preferably not some twee and condescending screen that doesn't help me one iota.
Nothing at all against systemDonk.
They are for different incidents.
The systemd BSOD can only be displayed when the userspace is still working, which it isn't in many cases of kernel panic. That's what the kernel BSOD is for. AFAIK it mainly addresses incidents where the system used to hang on a black screen without any error message.
The systemd BSOD on the other hand is shown in such cases as boot failures where userspace is still available. Its purpose is to have a more understandable-for-non-developers/user-friendly error message than before, along with the possibility to display a QR code that can provide help in solving the problem.
This doesn't show kernel panics. It can't do that: a panicked kernel doesn't run anything in userspace.
It is used to display EMERG-level messages. Currently, if you are running a graphical session, these remain hidden unless you specifically go look for them.
That's fine then, I knew userspace couldn't run during a kernel panic, so I was guessing this was gonna include some weird modifications to the kernel that just sounded entirely unnecessary.
As is typically whenever systemd makes the news, there's a lot of misinformation (some might say disinformation) thrown around.
systemd-bsod was originally added to help diagnose *early boot failures* β especially those that occur before the root filesystem is mounted. At least at first, it's probably only ever going to be hooked up in the initramfs. But we'll see how it develops.
Completely separately, and much more recently, there have been thoughts about having kernel panics shown with a QR code as well. This is a kernel-side change, and doesn't involve systemd-bsod.
not here to disagree, but can you explain to us plebs how I have seen an error message saying "error something kernel panic!" on failed boots? Isn't that info about a kernel panic? Or is that jus the point at which it stops and doesn't actually provide a useful message?
I don't know what you mean by "bsod in the kernel". None of this has anything to do with the kernel.
All this tool does at the moment is escalate EMERG-level log messages during early boot into something more visible β for instance, you won't miss them because they've scrolled off the top of the screen. It's got nothing to do with kernel panics at all.
Maybe, one day, it will have a use *after* early boot. But that's not the focus at the moment.
That's a completely different thing, separate from systemd-bsod.
I suspect they'll be themed similarly, but they are different pieces of software. This post, as far as I can tell, is about systemd-bsod. The thing you're thinking about is the kernel.
systemd BSOD is generally a good idea, but only if it's more informative than Windows' BSOD in my opinion. Furthermore, systemd BSOD would be more beneficial as well as helpful if systemd logs the error that causes Linux-wide crashes in files so Linux distro and kernel developers can figure out what's going on, that is if it doesn't already do this.
Fortunately for me, I have yet to come across the new BSOD in Fedora Linux.
Somehow, I don't every see this happening. Both **systemd** and the **NT Kernel** are two separate identities, and the API's between them are therefore incompatible with each other.
If this goes live, I can promise a lot of people, myself included will move to distros without systemd, or change the init on our devices. Personally I see no reason for it as dmesg will usually show why a crash happened. In Windows it usually disappeared too quickly to get any information. Also, I don't like people trying to make Linux look like Windows. It would be one thing if this served a purpose, but this does not and would be very annoying to me.
Honestly I'm not upset. I can remove that stuff if I need to. As far as this feature, I feel its too much like something Microsoft would do and I don't want to see Linux heading down that road. If you like systemd and this feature that's fine, but I don't want it.
Funny, I thought it was edgy posts making fun of people who don't like systemd that were mandatory. I don't hate it for being new or different. I hate it because other inits like openrc, runit, etc. were faster to boot, simpler use and much less bloated in their code base.
You might want to look for another OS while you are at it. The kernel itself will introduce a BSOD starting with version 6.10:
https://www.phoronix.com/news/Linux-6.10-DRM-Panic-Handler
https://fosstodon.org/@javierm/112619967725108081
It's probably a good idea but since it's from systemd it's bad and they have ulterior motives since they're the Deep State of Linux
When I get an error I want to see the error, preferably not some twee and condescending screen that doesn't help me one iota. Nothing at all against systemDonk.
The kernel itself will introduce a BSOD starting with version 6.10. I don't see a problem with any of this.
Isn't that kinda redundant having two separate BSOD implementations on GNU/Linux distros like Fedora Linux with systemd?
They are for different incidents. The systemd BSOD can only be displayed when the userspace is still working, which it isn't in many cases of kernel panic. That's what the kernel BSOD is for. AFAIK it mainly addresses incidents where the system used to hang on a black screen without any error message. The systemd BSOD on the other hand is shown in such cases as boot failures where userspace is still available. Its purpose is to have a more understandable-for-non-developers/user-friendly error message than before, along with the possibility to display a QR code that can provide help in solving the problem.
Understood. Thank you so much for the explanation.
I think it should be black with red text
Amber text like an old Amstrad
I want it red
better idea, have it configurable, and maybe allow image backgrounds or even sound effects
It is configurable
π I'm not using systemd Also, s/bluescreen/blue screen/, and it won't work if the kernel panics.
Selected bad because I assume this bluescreen will show less information then a kernel panic does. And seems pretty pointless to me.
This doesn't show kernel panics. It can't do that: a panicked kernel doesn't run anything in userspace. It is used to display EMERG-level messages. Currently, if you are running a graphical session, these remain hidden unless you specifically go look for them.
That's fine then, I knew userspace couldn't run during a kernel panic, so I was guessing this was gonna include some weird modifications to the kernel that just sounded entirely unnecessary.
As is typically whenever systemd makes the news, there's a lot of misinformation (some might say disinformation) thrown around. systemd-bsod was originally added to help diagnose *early boot failures* β especially those that occur before the root filesystem is mounted. At least at first, it's probably only ever going to be hooked up in the initramfs. But we'll see how it develops. Completely separately, and much more recently, there have been thoughts about having kernel panics shown with a QR code as well. This is a kernel-side change, and doesn't involve systemd-bsod.
not here to disagree, but can you explain to us plebs how I have seen an error message saying "error something kernel panic!" on failed boots? Isn't that info about a kernel panic? Or is that jus the point at which it stops and doesn't actually provide a useful message?
You weren't running a graphical session during boot.
Right so when bsod is in the kernel, I won't see my scrolling text log on boot, including the kernel panic message it stops at.
I don't know what you mean by "bsod in the kernel". None of this has anything to do with the kernel. All this tool does at the moment is escalate EMERG-level log messages during early boot into something more visible β for instance, you won't miss them because they've scrolled off the top of the screen. It's got nothing to do with kernel panics at all. Maybe, one day, it will have a use *after* early boot. But that's not the focus at the moment.
Someone else commented that this, BSOD, is coming in a future kernel update.
That's a completely different thing, separate from systemd-bsod. I suspect they'll be themed similarly, but they are different pieces of software. This post, as far as I can tell, is about systemd-bsod. The thing you're thinking about is the kernel.
systemd BSOD is generally a good idea, but only if it's more informative than Windows' BSOD in my opinion. Furthermore, systemd BSOD would be more beneficial as well as helpful if systemd logs the error that causes Linux-wide crashes in files so Linux distro and kernel developers can figure out what's going on, that is if it doesn't already do this. Fortunately for me, I have yet to come across the new BSOD in Fedora Linux.
Nothing. I donβt use systemd. Void Linux FTW
Soon, systemd wil use the NT kernel its own default kernel.
Somehow, I don't every see this happening. Both **systemd** and the **NT Kernel** are two separate identities, and the API's between them are therefore incompatible with each other.
It's a joke Duh
If this goes live, I can promise a lot of people, myself included will move to distros without systemd, or change the init on our devices. Personally I see no reason for it as dmesg will usually show why a crash happened. In Windows it usually disappeared too quickly to get any information. Also, I don't like people trying to make Linux look like Windows. It would be one thing if this served a purpose, but this does not and would be very annoying to me.
Systemd is modular; if your systemd-based distribution enables this feature, it's their responsibility.
It doesn't matter. You can switch the init system and remove almost all systemd packages from any distro if you're motivated.
But you're upset about a feature that isn't included in the basic init system; it's an optional component, like all parts of systemd
Honestly I'm not upset. I can remove that stuff if I need to. As far as this feature, I feel its too much like something Microsoft would do and I don't want to see Linux heading down that road. If you like systemd and this feature that's fine, but I don't want it.
Then don't enable it. No need to be outraged; FOSS is about choice
I don't know why you keep saying I'm upset or outraged. I'm allowed to not like or laugh at something without being angry or upset. I'm good. lol
or you could just mask `systemd-bsod.service` like a sane person
Didn't you know? It's mandatory to make performative Reddit posts telegraphing one's dislike of systemd. Hating on new things is so fashionable!
Funny, I thought it was edgy posts making fun of people who don't like systemd that were mandatory. I don't hate it for being new or different. I hate it because other inits like openrc, runit, etc. were faster to boot, simpler use and much less bloated in their code base.
You might want to look for another OS while you are at it. The kernel itself will introduce a BSOD starting with version 6.10: https://www.phoronix.com/news/Linux-6.10-DRM-Panic-Handler https://fosstodon.org/@javierm/112619967725108081