The /g/ [retarded] mentality

>doesn't like systemd
I bet you don't drink tap water or get your kids vaccinated either

>>56296863
Not op but I really don't get this tap water meme. I probably drank from tap water less than 10 times in my life. I've never been to a place where people drank from tap water. Everybody either use filters or buy 5galon containers of mineral water.

Just what sort of water do you guys have up there in the US?

>>56296975
Clean water

>>56296809
>likes plain config files
>doesn't like systemd
Have fun with your initscripts boilerplate.

>>56296975

I always drink tap water. What shithole country do you live that you need bottle/filtered water?

>>56296975
3rd world country?

File: 1472043043483.jpg (115KB, 744x960px) Image search: [Google]

115KB, 744x960px

>>56296809
Systemd comes from Red Hat. Red Hat, in the Linux world, is the company with the largest ties to the US government and the various state security organizations around the world--including NSA. The US government (DoD) is Red Hat's number one customer. Red Hat also happens to be Lennart Poettering's employer.

The Linux kernel, I believe, is clean. As long as Linus lives, you're not going to subvert the kernel. Let's just assume that is true for the sake of argument. If you can't get into the kernel, what is your next option? You need something low level (PID 1?), ubiquitous, and vast in scope and complexity.

This describes systemd perfectly. It was almost like it was designed to touch as much of a Linux system as possible. It has hooks into some many different subsystems and APIs that it's almost impossible to build a modern distro with current software without pulling in systemd as a dependency. This happened almost overnight, and I think there are malicious forces at work here.

We must remember Heart Bleed. Heart Bleed appeared to be an innocent mistake, and it was a tiny typo in one line of a C program. If it's possible to do that much damage with a tiny little error, imagine when you have an attack surface as wide as systemd, written in a language like C that is almost designed to produce security holes when not written absolutely perfectly--and humans are not absolutely perfect programmers.

Systemd is dangerous. It's too big to be audited as quickly as its developed. It's complexity adds as much attack surface to a Linux system as the kernel itself. We can't get away from these facts. Shitfighting about init systems is a waste of our time. Sytemd is horrible because of where it comes from and how complex it is. Backdoors will be hidden in it.

>>56296863
Holy projection batman!

>>56297007
>>56297051
>>56297076
I live in Brazil. I think that even if the water you get is "clean" you should use filters. Pipes and faucets get dirty or rust overtime, while most filters are "self cleaning" and/or are easy to disassembly if you want to clean them.

>>56297081
Linux is full of Red Hat devs tho and it's not like Linus reviews all commits. He just trusts his maintainers.

nice ( you ) generation script

>>56296809
99% of neo /g/ doesn't even know what you're talking about
it's pointless

This is a nightmare

http://suckless.org/sucks/systemd

Especially implementations like nspawn, DNS, networking in PID1

If you look at this init from a distance you can begin to even see how it can be a deliberate effort to damage the security of the operating system

Systemd's push into critical parts of the OS is alarming.

Systemd is very much trying to make itself an irremovable part of modern GNU/Linux with its development style of absorbing other OS elements. As it becomes more bloated it will continue to become harder to audit and control what is running on one's machine.
In the end, all the distros that adopted this will be dealing with volatile high velocity corporate code running critical parts of their OS.

The FSF should say something before it's too late.

File: runit.png (22KB, 644x364px) Image search: [Google]

22KB, 644x364px

>>56297030
>Have fun with your 2 line shell scripts
FTFY, pic related