Linus Torvalds vs. systemd developers

This is better than reality TV:

"Key, I'm f*cking tired of the fact that you don't fix problems in the code *you* write, so that the kernel then has to work around the problems you cause.

Greg - just for your information, I will *not* be merging any code from Kay into the kernel until this constant pattern is fixed."

Love it, better than Eastenders.

http://twitter.com/lusis/status/450701265782456320

:o)

+1 Linus

You rock!!

http://igurublog.wordpress.com/2014/04/03/tso-and-linus-and-...

Seems the behavior is systemic across all RH maintained projects...

Well, this has certainly been the attitude from systemd developers from all that I have seen about it. They constantly dismiss criticism rather than answering it. They do this by claiming that the criticism is emotionally motivated without ever addressing any of the points of criticism. This has always been the attitude of Poettering about all his projects. His attitude is somewhat reminiscent of Joerg Schilling. We see that cdrtools has been forked or worked around to avoid the problems such an attitude brings with it. In the end it's quite possible that systemd won't end up the defacto standard init system, at least not in its current state, with the attitude of the developers.

Quoting: http://twitter.com/lusis/status/450701265782456320

Yes :)

Slackware's April 1st ChangeLog :o)

http://www.linuxquestions.org/questions/attachment.php?attac...

kikinovak, that page wants a login. I did a quick web search to see if it was on a different site, but didn't find it.

The only thing I know about systemd is that it destroyed my Arch rolling system, and I've never used Arch again.

@tuxchick: Here's a copy of the screenshot on my server:

http://www.microlinux.fr/download/changelog.jpg

The more i read into thing the more i suspect that Systemd and the rest of the changes that are coming out of RH are focused on one thing and one thing only, the quick spin up of VM instances in a environment like the Amazon cloud service.

Sadly RH packs an inordinate amount of weight in the glue area between user facing and kernel.

Speaking strictly as a user, I can honestly say this dust-up has finally made it clear to me the problems inherent in moving to Systemd. Hopefully, Debian will take their sweet time in switching, or forgo the switch entirely.

And as for putting another distribution on my laptop that relies on Systemd, well, it can wait.

Linus is awesome:)

> Speaking strictly as a user, I can honestly say this dust-up has finally made it clear to me the problems inherent in moving to Systemd. Hopefully, Debian will take their sweet time in switching, or forgo the switch entirely.

Speaking has someone who has various objections to systemd (or at least, to anointing systemd as the default init system for Linux, as there apparently are/would be some very good use-cases for it, too), it's not clear to me that this fracas points out the basic problems with sysdemd.

Rather, this incident "merely" points out the regressive attitudes of the systemd developers (though of course, the two phenomena arguably are strongly connected).

But such developments are hardly unique to the systemd devs. It seems to be a malaise common to many FOSS projects these days, as exemplified (for example) by KDE and Gnome, Canonical (Unity, Mir, Amazon lens, etc), and some others. People seem to be confusing "I can do this, and it would be so cool -- maybe even useful" with "this is a great idea, and a good direction for the design philosophy to follow."

We get to watch the sausage-making. It will all sort out, as it always does.

@tuxchick : my brother once went to visit a sausage factory in Austria, back in the 80s. He's never once eaten sausage since that day. :o)

Making yer own sausage is even easier than learning Linux. Last time we (friends/family) did it, we put up 600lbs in a day.