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

[onlyLinuxLuvUBack]

Michael , I give you these for free.....

Have a print on demand store, stock:

1)
###############
Systemd-the-tshirt

- Phoronix.com
###############

2)
###############
Systemd-the-coffee-cup

- Phoronix.com
###############

3)
###############
Systemd-the-baseball-cap

- Phoronix.com
###############


4)
###############
Systemd-the-toilet-paper( print on each sheet)

- Phoronix.com
###############

[Danny3]

Yet another proof that Microsoft destroys everything it touches!
But I wonder, Lennart couldn't really find another employer than Microsoft or Microsoft really has thrown a lot of money in his direction that he could not refuse?
I really hope that one day someone forks systemd and remove the bad parts.

[tobias]

But I really, really cannot understand why it's part of systemd when it has nothing to do with it. You don't even need to have systemd installed for it to work (I mean, it's obvious, the system isn't even "up" at that point during boot).

The systemd devs wrote it. So why not put it into the repo at hand? :-)

It also forwards information to systemd for the boot time measurements and such.

[sophisticles]

Couldn't it be black by default? Why the need to copy Windows?

Because a Black Screen of Death is also a Windows "thing":

https://en.wikipedia.org/wiki/Black_screen_of_death

[F.Ultra]

SO MANY features get rolled into this project. New keywords for service files even when there already existed a whole bagful. Honestly, almost no-one knows how to correctly write a systemd service file that does exactly what is wanted. There are 5 methods to do the same thing, but they differ slightly in behavior in some edge case, and it usually takes a discussion thread of like 5 experienced systemd users and several days of brainstorming to achieve a "final" consensus how some non-trivial service file should be written. WTF?

I managed pretty well to live with cron and shell scripts under sysV. With systemd i can only hope google brings me to the right discussion thread for the type of service i need...

Give us one example of something that can be done in 5 different methods but differ only slightly in behaviour.

Couldn't it be black by default? Why the need to copy Windows?

It's quite clear that they copied the blue from the BSOD just for the lolz.

I like systemd-boot a lot because of its simplicity (and how bug ridden GRUB is in comparison).

But I really, really cannot understand why it's part of systemd when it has nothing to do with it. You don't even need to have systemd installed for it to work (I mean, it's obvious, the system isn't even "up" at that point during boot).

That's the problem here.

Just call it "simple boot manager" and make it completely separate project and that's it.

That is because there are two systemd:s, one is the init system and the other is a project to create a unified plumbing system for Linux, part of that unification is to name every tool systemd-xx so that they are more easier found without having to google for "what was the boot manager from the systemd project called now again".

I have no problem with systemd in general, but I do have a problem specifically with systemd-resolved. It's utter garbage. I always experience unexplained network slowdowns on distros that use it by default (Fedora and Ubuntu based distros) which don't happen on distros that don't use it by default. Also you have this issue that is still open after 4 years: https://github.com/systemd/systemd/issues/13432 . I've seen others also complain that it has broken behaviour with public Wi-Fi and VPNs.

It's only a resolver, it cannot cause slowdowns of your network traffic.

[sophisticles]

Yet another proof that Microsoft destroys everything it touches!

That's why they have a Market Cap of 2.75 trillion dollars:

https://www.google.com/search?q=microsoft+market+cap+rate

[sophisticles]

[WARNING: very satirical and cynical comment ahead - don't bother to reply!]

"Oh look!!! they've created the BSOD for Linux (30 years later)!!! How wonderful!!! Now we can all spend Christmas looking into a blue screen - trying not to cry - while asking ourselfs why it happened with a sense of nostalgia!!!"

Yes, what else could we ask for xmas but a BSOD??? Lots of BSOD!!! Yes!!! We all love when our computers crash!!! Bring on BSODs!!!

You know what's the next best thing?
We can all now go on to the front of MS' HQ and say to everyone that goes in: "You know what my Linux OS now produces??? BSOD's!!!"

(you'll have to ignore those that will say that's a terribly rare thing on windows these days and that BSOD are mostly a thing of the past, thou....)

Happy xmas everyone

ahahahahahahhaha

Pro tip, if you want the cynicism and satire to land do not tell your audience that is what it is and especially do not preface the bit with the disclaimer.

Other than that, great job on that commentary, I'm sure it really made people think.

[sophisticles]

Linux, admittedly does a very good job of it, tries to be a jack of all trades

Do you know what the complete saying is?

Jack of all trades, master of none.

[user1]

It's only a resolver, it cannot cause slowdowns of your network traffic.

Sorry, I meant slowdowns with website loading. Sometimes the whole website takes ages to load. Other times, if certain websites load quickly, some of their elements still take ages to load. And it's related to the Github issue in my previous comment. When the slowdown happens, I see the "Using degraded feature set" message in logs.

[cj.wijtmans]

but they do try to solve the standardization problems inherent to Linux as a whole.

a program is not a standard. dumbest argument i ever heard.