←back to thread

Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” bricking UEFI

(git.kernel.org)
279 points the_why_of_y | 1 comments | 22 Feb 16 18:08 UTC | HN request time: 0.288s | source
Show context
chris_wot ◴[22 Feb 16 19:43 UTC] No.11153650[source]▶
Ok, so I was wrong when I said Lennart Pottering's original response was "pretty appalling".

Unlikely he saw it, but my apologies nonetheless.

replies(1): >>11154059 #
coldpie ◴[22 Feb 16 20:33 UTC] No.11154059[source]▶
Poettering gets shit on a lot. While his software does often have problems, he is really well-intentioned and working on really hard things that really do need fixing. New software simply has bugs and problems, and while the transition period can be rough, I think things will be really improved when we break through to the other side.
replies(2): >>11154409 #>>11154953 #
cyphar ◴[22 Feb 16 22:44 UTC] No.11154953[source]▶
People don't hate systemd because it has bugs. People hate it because it's clear that it thinks it owns your system and that its manifest destiny is to contain all software that exists.
replies(2): >>11156088 #>>11156347 #
cbd1984 ◴[23 Feb 16 03:43 UTC] No.11156347[source]▶
No, they hate it because they think hating it is a good way to troll people.

It isn't honest hatred, it's just dancing around making ugly faces, like a six-year-old.

replies(1): >>11156842 #
chris_wot ◴[23 Feb 16 05:36 UTC] No.11156842[source]▶
I really like systemd, but I think that's not accurate. People have well thought through reasons for disliking systemd
replies(1): >>11158988 #
coldpie ◴[23 Feb 16 14:30 UTC] No.11158988[source]▶
However, "it's clear that it thinks it owns your system and that its manifest destiny is to contain all software that exists" is not one of those well-thought-through reasons :P
replies(2): >>11161593 #>>11165381 #
1. cyphar ◴[24 Feb 16 08:47 UTC] No.11165381[source]▶
What is the reason that systemd has to include a bootloader (bootctl -- which was gummiboot)? Why does it include a container engine (nspawn)? Why does it think that it should control all logging on your system (the whole journalctl monstrosity)?

Yes, it might've been hyperbole, but the fact that systemd has so much code inside it which has nothing to do with "being an init system" just begs the question "why?".