Why does /g/ hate systemd?

>>61168660
It's shit

binary logs, monolithic, tries to control your system, comes from RedHat (ehem, NSA)

>>61168660
>>61168830
autism

>>61170301
>binary logs
hurr durr, it does things differently

>monolithic
false

>tries to control your system
falser

>comes from RedHat (ehem, NSA)
falsest

If you know the differences between the init systems and the issues of the previously existing ones, and if you've listened to some talks of why the creators chose certain solutions, you'll see that systemd isn't that bad. it's currently the best init system we have

>>61170379
>Lennart doesn't work at RedHat
yeah, sure pal
>NSA never tried to compromise Linux
OK
>hurr durr, it does things differently
But why? Why binary?

>>61170436
inb4
>RedHat doesn't work together!!!
sure thing they don't

>>61170379
>Redd!t spacing
End your life

>>61170449
with NSA, fuck...

>>61170379
>currently the best init system we have

what does it have over OpenRC and runit?

https://github.com/systemd/systemd/issues/5644

This is the person responsible for writing a 100k+ LoC unautited C program that runs as root on 95% of all linux installs. If you are uneasy about all this you "don't understand linux" and "hate change".

>>61170379
The good old "it compiles to multiple binaries therefore it isn't a huge monolithic blob" fallacy

File: Screen Shot 2017-07-01 at 9.45.09 AM.png (88KB, 795x600px) Image search: [Google]

88KB, 795x600px

>>61170576
missed the image

>>61170645
What exactly is the problem here? I don't understand what you're saying.

File: Screen Shot 2017-07-01 at 10.03.56 AM.png (112KB, 779x630px) Image search: [Google]

112KB, 779x630px

>>61170826
you're not a tech illiterate right?

>>61170854
I use linux. Doesn't it mean that he wants to restrict people from removing files in the directory above? Why is this a part of systemd?

>baby pepe image
>shit, useless, vague, redundant thread

everytiem

>>61170826
he's reimplementing unix tools without understanding how they work and therefore introducing bugs. for instance, rm doesnt work on . or .. because something like rm -rf .* would recursively destroy your whole system by following ../

potterings command ignores this and running R! /foo/.* will nuke the system because it follows ..

>>61170301
What is the problem with the logs again?
You can grep and less like old logs, but now you have more info built in.
Why is this bad?
Controlling the system is the point, it makes it easier for you to control the system.
As for the NSA backdoor allegations, it is free software.
You can study it yourself to see how it works.
There is no mission statement to create backdoors, so if you find something, it can be removed.

>>61170946
The logs can corrupt easier. The assumption is that in a system crash where files get lost, the logs would be gone too.

>>61170946
there is a very big difference between having open code and being able to fix the code. At this point it's too complex and large for any one person to fix.
"NSA backdoors" are not usually added due to mallice, the majority of the time it's incompetance of which is in great abundance in the systemd ecosystem.