Making it possible to uninstall initscripts / insserv and facilities

[Felipe Sateler]

On 24 November 2015 at 18:28, Michael Biebl <biebl at debian.org> wrote:
> Am 24.11.2015 um 22:25 schrieb Petter Reinholdtsen:
>> [Felipe Sateler]
>>> That would potentially leave initscripts with wrong ordering, thus
>>> breaking a boot back to sysvinit (via syvinit package).
>>
>> My guess is that this would not happen if the initscripts package is
>> installed before trying to boot using sysvinit, which I suspect is a
>> requirement.  The initscripts postinst script calls update-rc.d which
>> would call insserv to fix the ordering.  Is my guess wrong?
>
> Afaiu, Felipe's point was, that initscripts could be installed, but
> systemd the active PID 1.
> So switching to sysvinit as active init would not necessarily re-trigger
> a insserv run.

Exactly, and the added --force would mask a bug somewhere in the init scripts.


> What check did you have in mind here? Testing for a (conf)file shipped
> by the initscripts package?

Right. Either that or shelling out to dpkg-query, but testing for
/etc/init.d/mountkernfs.sh (the most depended upon service) would be
good as well.

-- 

Saludos,
Felipe Sateler