[systemd-devel] How to get rid of this ordering cycle?

Michael Biebl mbiebl at gmail.com
Thu Aug 14 09:38:03 PDT 2014

2014-08-14 17:04 GMT+02:00 Zbigniew Jędrzejewski-Szmek <zbyszek at in.waw.pl>:
> On Thu, Aug 14, 2014 at 02:31:00PM +0100, Simon McVittie wrote:
>> On 14/08/14 13:27, Vlad Orlov wrote:
>> > # Provides:          mintsystem
>> > # Required-Start:    $local_fs $syslog $remote_fs dbus
>> > # Required-Stop:     $local_fs $syslog $remote_fs
>> > # Default-Start:     S
>> > # Default-Stop:
>> > ### END INIT INFO
>> As Lennart said, this is Debian-(and-its-derivatives)-specific: upstream
>> systemd does not support sysvinit services during early boot, i.e. rcS.
>> In Debian, support for sysvinit scripts in rcS was patched back in to
>> avoid breaking existing software, because it's unlikely that all of the
>> packages listed in
>> <http://codesearch.debian.net/search?q=Default-Start%3A\s*S> will get a
>> native systemd unit any time soon. Most of them probably doesn't
>> actually need to run in rcS - nvi? seriously? - but if fixing them all
>> was on the critical path for adopting systemd, we'd probably still be
>> using sysvinit for years to come.
> Actually, most of them probably don't need to run at all:

Yeah, this is correct. Those init scripts are only necessary if you
actually still use sysvinit as PID 1.

See http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/systemd.links

Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

More information about the systemd-devel mailing list