[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 10/22/2014 11:39 AM, Raphael Hertzog wrote:
> You can't create a trigger monitoring /etc/inittab because it's not
> packaged:
> $ 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.

Isn't that just a hack to work around deficits in sysvinit? If sysvinit
was to support inittab snippets in {/lib,/etc}/inittab.d (or the a bit
more verbose /etc/sysvinit/inittab.d), this should just work as with
other init systems.


Reply to: