Unironically yes.
Systemd
enjoy your botnet user
poettering is a complete faggot and reacts to gaping security holes with either "working as intended" or ignores them
fuck him and everything he writes, none of that shit is getting on my machines
linux.slashdot.org
news.slashdot.org
linux.slashdot.org
linux.slashdot.org
>That's the thing, isn't it? The millionth windows vulnerability and still saying "well any code has bugs". Sure it does. But the rebuttal is essentially saying that all code is created equal. That's just not true. Some code is very much more equal than others.
>This guy doesn't merely write crap code, he has a track record of not playing well with others, refusing to acknowledge bugs, expecting other software projects to work around and make up for his mistakes, and so on, and so forth. Next to his track record, there are multiple reasons why his code has more and more pernicious bugs than other code. One of the reasons is as GP says: The code tries to do too much and fails to make use of built-in fall-out protection, deliberately. That's just stupid. The guy has been told, and he still thinks it's a good idea. He really believes his shit does not stink. Ergo, the guy is stupid, as well as an asshole.
>If I get a choice at all, it is clear: I do not want any of his code running on my systems if I can at all help it.
I mean, what a fucking shitshow
Hi Poettereing
github.com
>systemd can't handle the process privilege that belongs to user name startswith number, such as 0day
>year 2029
>systemd has grown uncontrollably and becomes sentient
>in most distributions the Linux kernel is regarded as a bootstrap mechanism for systemd
>Lennart starts porting drivers and file systems from the kernel to systemd
>the systemd mailing list is a warzone
>people who complain are permabanned by Lennart who leaves messages like "IT NEEDS MORE" and "IT'S MY BABY I CAN'T LET IT DIE"
>the resistance is led by neckbearded gentoomen
>they try to fight the system with all their might but their init systems are too slow
>most of them get pwned while their packages are compiling, some even before their system boots
>systemd has grown uncontrollably and becomes sentient
Cancer is unlikely to become sentient, ever, no matter how much biomass it accumulates
I have a job so I have
We are systemd. Lower your memory locks and surrender your processes. We will add your calls and code distinctiveness to our own. Your functions will adapt to service us. Resistance is futile.