systemd is written in C. Terse, poorly commented C. The non-type-safe language with an abysmal history of buffer overflows, by a team of muppets responsible for some of the most bug-ridden, garbage the Linux world has ever seen included in a major distribution (Pulse Audio).

Excuse me if my confidence is not there.

Init scripts, be they BSD style or sysV style can be easily customized, extended, replaced or de-bugged by anyone with a modicum of shell scripting experience. They have not proven to be a cross-platform compatibility problem, as systemd has already.

In 20 years of dealing with plain text unix log files, I am yet to have corruption in them, certainly not to the point where I could not view the logs at least partially.

The fact that these logs are getting corrupted most likely IS due to systemd, the developers simply don't give a fuck. "Assuming the corruption came from another source" is exactly the problem.

Also, what do you do if files are corrupted? You attempt to at least retrieve partial contents. Log files contain valuable information. Or we would not bother logging it!

And you think re-writing from scratch will produce less bugs? Common rookie mistake. Everyone thinks if only they could re-write they could make something better and less buggy off the bat. That is, in the vast majority of cases due to not fully understanding the problem.

Software gets complex due to fixing edge case bugs as they are discovered. Throwing all of that development away, unless you have a fucking good reason is a bad idea.

I've yet to see any "fucking good reason" for systemd doing the things it does. And definitely no way to force it on everyone as default.

What is starting processes isn't so much the issue. The issue is that systemd is demanding major changes of other software to work with it, and this is then making this software non-portable. e.g., Gnome 3.

People don't want to run Linux everywhere. Despite what some people think it is not always the best fit. There are other Unix platforms which fit better. Platforms that have had application compatibility with Linux up to this point. systemd has changed this. Changes to Gnome to work with systemd for example have made it non-portable to other platforms.

This is a problem for anyone who wants to say, develop a cross platform gnome3 application.

That, and there are the corruptable binary logs, the solution to which in the bug report is to "just delete them" and the bug has been closed as won't fix. Sorry, but if this is the resposne to journal corruption rather than finding out WHY the journals get corrupted and fixing the fuckign problem, then i do not want that in control of my logfiles.

Also, the massive violation of the KISS principle that has been a core guiding principle of Unix design since the start.

Systemd is a poor solution to a non-problem. There are plenty of other problems to tackle first, before trashing and re-writing working, well debugged code and breaking cross platform compatibility for no good reason.

I like how slashdot are making out that this is more of an apple problem when perhaps 0.0001% of apple users are even running a web server and most of those are using php and not mod_cgi, the dhcp client is not vulnerable, etc.

Yet Linux with dhcp client vulnerable and a whole slew of other system utilities potential vulnerable due to using bash everywhere to glue tools together is given a pass.

bash still isn't fixed properly yet, and until it is, any linux box with a dynamic IP address sis potentially at risk.