#bsod

christophs@diaspora.glasswings.com

There is no mystery over who wrote the Blue Screen of Death, despite what some may want you to believe - The Old New Thing

Somehow, there is a claim of a 30-year mystery surrounding Microsoft’s Blue Screen of Death. The argument goes that there are three conflicting sources of authorship: Steve Ballmer, John Vert, and me.

But really, there is no conflict. There are three different blue-colored screens, and each has a different author.

#bsod #windows

https://devblogs.microsoft.com/oldnewthing/20240730-00/?p=110062

gander22h@diasp.org

Airlines, banks, health care have operations disrupted in global IT outage

A global tech outage was disrupting operations in multiple industries on Friday, with airlines halting flights, some broadcasters off-air and everything from banking to health care hit by system problems.

According to an alert sent by global cybersecurity firm Crowdstrike to its clients and reviewed by Reuters, the company's Falcon Sensor software is causing Microsoft Windows to crash and display a blue screen, known informally as the "blue screen of death."

#CrowdStrike #Microsoft #Windows #BSOD but not #Linux #Mac or #BSD

danie10@squeet.me

New systemd update will bring Windows’ infamous Blue Screen of Death to Linux – Roll on Memes!

A Windows Bluse Screen of Death (BSOD) saying there is a technical error
Windows’ infamous “Blue Screen of Death” is a bit of a punchline. People have made a hobby of spotting them out in the wild, and in some circles, they remain a byword for the supposed flakiness and instability of PCs. To this day, networked PCs in macOS are represented by beige CRT monitors displaying a BSOD.

But the BSOD is supposed to be a diagnostic tool, an informational screen that technicians can use to begin homing in on the problem that caused the crash in the first place; that old Windows’ BSOD error codes were often so broad and vague as to be useless doesn’t make the idea a bad one. Today, version 255 of the Linux systemd project honours that original intent by adding a systemd-bsod component that generates a full-screen display of some error messages when a Linux system crashes.

On the plus side it does often happen that a specific error gets a bit burying in lots of streaming text output in the CLI (or in a log file), so from that perspective this may better highlight an actual issue. For new users it may help bring a lot of focus.

I strongly suspect though for the many users that have mastered log files, and that don’t like Windows at all, this may grate a bit. Then many also love to hate systemd itself, and this will add some fuel to those flames too.

That all said though, change is also never popular, and in most cases, if it also proves useful, it will be accepted after a while. I’m sure we’re going to see many new Linux memes now about the BSOD.

See https://arstechnica.com/gadgets/2023/12/linux-distros-are-about-to-get-a-killer-windows-feature-the-blue-screen-of-death/
#Blog, #BSOD, #linux, #technology