Removing conflicts of init system

Felipe Sateler fsateler at debian.org
Sat Dec 22 12:30:38 GMT 2018


On Fri, Dec 21, 2018, 19:19 Lorenz <lorenzo.ru.g at gmail.com wrote:

> Josh Triplett <josh at joshtriplett.org> ha scritto:
> > sysvinit works similarly, with /lib/sysvinit/init
> This was in Jessie, but I don't see any /lib/sysvinit/init in Stretch nor
> in Sid,
> it's /sbin/init now, am I wrong?
>

You are correct. The sysvinit package (which provided the fallback) was
dropped:

  * Drop transitional sysvinit package. It has served its purpose for the
    wheezy → jessie transition and keeping it around for longer only
    leads to confusion as it doesn't setup /etc/inittab which is necessary
    to boot with SysV. This functionality has moved into sysvinit-core,
    which should be used instead in such a case. (Closes: #781766)


There is nothing blocking its reintroduction, though, if care is taken to
make sysvinit functional after installing it.

Saludos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20181222/29eb5dbc/attachment.html>


More information about the Pkg-systemd-maintainers mailing list