[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2


On Wed, 22 Oct 2014, Thibaut Paumard wrote:
> Le 22/10/2014 11:20, Gerrit Pape a écrit :
> > severity 766187 grave
> > quit
> > 
> > [...]
> > When switching to sysvinit, the /etc/inittab file is created, but
> > doesn't include the lines enabling the runit supervision.  After reboot
> > runit supervision will not be enabled, although the package is
> > installed.  This would be a grave bug as other packages depend on this
> > assumption.
> > 
> > Any idea on how to fix this?
> I think a trigger would work:
> /usr/share/doc/dpkg-dev/triggers.txt.gz

You can't create a trigger monitoring /etc/inittab because it's not
$ LANG=C dpkg -S /etc/inittab
dpkg-query: no path found matching pattern /etc/inittab

And you can't use it on another file provided by sysvinit-core because
you have no guarantee that the file trigger will be executed after
the execution of the postinst of sysvinit-core.

Triggers could be part of the solution that said, you could
use a named triggers that is activated by sysvinit-core's postinst
after the installation of the inittab.

Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Reply to: