@shine @sonny @pid_eins
I'll explain my concerns.
- At first, I thought that it was just an alternative to sysvinit, runit ... even though existing init systems / process managers were fine.
The freedom of choice like we all want to have.
But no! It's not just a init thing. It's about controlling the system. Note that I felt in love with the name.
- Systemd : 1 package with many functionalities (tools) controling many building block for a Linux system (part of this definition came from its website)
- No code is really bullet-proof, and a single package that has control over many parts of the system can lead to a larger attack surface and a bigger impact IMHO, No ?
- And hey, why the heck do we have to deal with binary log ?
Why not the usual plain text stream. We have to rely on systemd tool to operate on them. As a sysadmin I have to do some "witchery" operations on logs stream and it is not helpful in many cases as I want to use other tools for some direct manipulation on it.
- Speaking about choice, will we always have the choice to go for another init system if the packages in the distribution we used to work on is totally dependent on systemd ? What if this extends to the whole Linux community ?
Doesn't it sound like a kinda systemd-centric ?
Couldn't it be a bit freaky ?
Where is the good old "Free" ?
Adding to that, the "Open Source" starts to fade on some software that used to be Open, actually.
- All of that doesn't help for saying that systemd will make Linux a better OS.