systemd

Lennart Poettering
PulseAudio, systemd, Avahi
works for redhat
long term contributor of the GNOME project and GNOME Foundation member
key developer of kdbus

debian switched yesterday to systemd

>>15
Hell no.

LinuxFr.org : Systemd use a lot of Linux only technologies (cgroups, udev, fanotify, timerfd, signalfd, etc). Do you really think the Linux API has been taking the role of the POSIX API and the other systems are irrelevant ?
Lennart : Yes, I don't think BSD is really too relevant anymore, and I think that this implied requirement for compatibility with those systems when somebody hacks software for the free desktop or ecosystem is a burden, and holds us back for little benefit.

I can't find the quote, but he's also stated that he doesn't care about POSIX or cross-platform design, as opposed to answering ``yes'' when someone else asked the question. Which is, frankly a good thing. Given systemd's problems (see e.g. http://ewontfix.com/14/ and http://ewontfix.com/15/ ) I would sooner switch to FreeBSD than let it on my system, and Lennart, Gnome, and the rest of the RedHat bunch ignoring FreeBSD means they won't fuck it up.

Pulse is okay once you rip out consolekit and associated baggage (I don't have to write clean_up_pulse.sh scripts anymore that blindly rm magic files), but I wish OSS was still a viable solution.

>>16
Is it possible to write a shitty not-as-featured version that is still compatible with it, though?

>>17
There would be nothing to gain from doing so (I, a user, would still be shafted out of my init system), and it would send a message to daemon developers that ``Yeah, even the *BSDs are fine with systemd, so go ahead and bind your programs as tightly as you like to that API!'' I don't want to compromise with sytemd at all. I don't think the OpenSSH folks are going to merrily bake systemd-specific code into sshd, but I don't want to give them any more incentive to than what RedHat is already undoubtedly offering.