A news in phoronix comment that it continues the debian debate about what to do with your initialization system. For a long time there have been voices calling for renewal and to get rid of the old sysvinit. And within those voices the rivalry between those who support systemd, those who support upstart and (very, very few) those who support openrc ……… ..and are not willing to support more than one.
The discussion is fierce and is like putting together a book of several volumes (they go through the 2500 messages, and this bug was opened only 2 months ago!!!). systemd is supported by several distros that migrated successfully (Fedora, Arch, OpenSuse, etc.), but its followers regret that Debian has to maintain versions for the FreeBSD kernel, where systemd is not ported (nor does Lennart intend to port it) . What is ported to FreeBSD is OpenRC (actually port to Debian KFreeBSD was achieved), but only Gentoo and its derivatives use it (except Sabayon which uses systemd). And Upstart, has the advantage of coming from the downstream (Ubuntu and its derivatives and also Chrome OS), but it falls short compared to systemd. And if to this we add the discussion outside the Debian lists, among which is Lennart's opinion y Patrick Lauer answering (to Lennart), any flamewar is small in comparison.
It was also news in phoronix that there are already opinions within the Debian technical committee. On one side is Ian Jackson (Debian daemon maintainer) who is in favor of Upstart. He considers it for its minimalism, for being better integrated into a demon's code, for its ease of packaging, have a less arrogant community (according to him) and for being more ready to be chosen for Jessie (OpenRC is not yet). It also indicates that disadvantages such as lack of IPv6 and UDP socket activation or multiple socket activation do not require difficult structural decisions and can therefore be more easily resolved.
And on the other hand is Russ allbery who is in favor of systemd: First you think that OpenRC is the most conservative alternative and that you don't even want to bother solving bugs like the lack of integration with events at the kernel level or its dependency more on shell scripts than on declarative syntax. In terms of service management, the activation of sockets stands out (not only initialize them but do it in parallel), the integration of the status of the daemon (more complete than in upstart) and in-depth security. Also remember that Debian already uses systemd (especially logind) for certain applications like udev and gnome (whose version 3.8 is already in testing) and you already have the migration plan in mind.
And as for the question of portability, systemd fans on LWN.net they say «There is no portable software, there is only software that was ported.I mean, either the Debian carriers for kFreeBSD and Hurd make it work, or they're going to shit. And this second option weighs heavily since (according to popcon) only 0,09% of Debian users have the FreeBSD kernel installed.
Meanwhile, KWin developer Martin Gräßlin is following the discussion on Debian that I had told them about, and he loves Russ Allbery's comparison between systemd and upstart and comments on his google + account that he intends to integrate systemd to Plasma, and incidentally that any environment that uses Wayland is passed to systemd. In particular you want to use socket activation to start your KWin session.
Christian Loosli asks that KDE not have a high dependency. Martin replies that KDE has a high dependency especially on QT, but fuck it, they only want it for features that are neither in OpenRC nor in Upstart, but more importantly, because they want KDE to depend on kdbus (
your own d-bus service explorer a project that seeks to integrate d-bus to the kernel) which already depends on systemd. It also says don't worry about the initialization system because this will be independent of whether you use OpenRC or SysVInit (In fact, Gentoo uses systemd even though its init is OpenRC. So "there should be no problem with Debian"). Then it is Eric Hameleers (member of the Slackware coreteam) who complains that they want to choose technologies that are only for Linux (again the issue of portability). Martin asks you to read the post of the false myths that Lennart wrote. That he trusts Martin.
What do you think of the panorama? The next news I have to do is an article on systemd, I'm going to do it as a football game story.