zlacker

Same with systemd.

>>BadBad+(OP)
Except for all those who've accidentally blown their legs off with it, of course.

Just ask the guy who bricked his motherboard due to a systemd bug where his firmware wasn't write protected and got destroyed by a 'rm -rf' command. lol

>>its_ma+nq1
No software is perfect. Not sysvinit (and it's bash scripts from different vendors), nor systemd. Errors happen. At least for me systemd is a net positive.

>>BadBad+2w1
> No software is perfect

Especially when it's a giant blob of buggy C code written by a known hack who has multiple decades' worth of history of foisting shit code upon a less than enthused public.

> At least for me systemd is a net positive

For the moment. Just wait until it finds a way to fuck you. It's plotting and scheming behind your back to do so as we speak.

Systemd for some reason seems to uniquely be the epicenter of giant facepalm bugs like LEAVING THE SYSTEM FIRMWARE VULNERABLE TO AN RM -RF COMMAND, a situation which causes alarm to none of the systemd crowd. They just shrug if off. "What's the big deal? I don't get it," they say.

I used to see the same mentality from Microsoft people back in the day. "Why would you use Linux? I don't get it. Windows is fine."

It's because you lack standards. You're completely used to being surrounded by software and hardware that is Fucking Garbage. Everything is like that in your world. You're happier than a pig in shit, oblivious.

>>its_ma+YD1
> Systemd for some reason seems to uniquely be the epicenter of giant facepalm bugs like LEAVING THE SYSTEM FIRMWARE VULNERABLE TO AN RM -RF COMMAND

I am very sorry to inform you but efivarfs is something coming from the Linux kernel. Being able to rm -rf it is squarely something that is entirely on the kernel implementation, WHICH THE AUTHOR OF EFIVARFS EVEN ADMITS[0]

[0]: https://lwn.net/Articles/978640/

>>NekkoD+mX4
Thanks for the correction. Yes, I have my bone to pick with the Linux kernel too on many different fronts.

#facepalm