Making it possible to uninstall initscripts / insserv and facilities

[Martin Pitt]

Hey Felipe,

Felipe Sateler [2015-11-25 15:18 -0300]:
> > As I wrote I think this is mostly good, but I'd really restrict this
> > to running under systemd
> >
> >   unshift(@opts, '-f') unless -f '/etc/init.d/mountkernfs.sh' || ! -d '/run/systemd/systemd';
> >
> > IMHO insserv really ought to fail hard if you remove
> > /etc/init.d/mountkernfs.sh (or initscripts as a whole) and are
> > actually running sysvinit.
> 
> I agree that failing hard if you are running sysvinit would be ideal.
> However, this check would break in
> containerized or chrooted environments.

Containers should be fine, but indeed chroots would not be. So indeed,
let's not sweat that and restrict the check to
/etc/init.d/mountkernfs.sh for now.

> Unfortunately, drawing inferences from the running system is bound
> to have this sort of problems. AFAIK, d-i does not run systemd;
> would things work there when initscripts is no longer transitively
> depended upon?

I don't think we need to be worried about the d-i environment; that's
fairly static, and people won't go and randomly purge stuff there.

> Maybe instead of using only mountkernfs.sh as flag file, we could:
> 
> 1. Check existence of /lib/sysvinit/init

Ah, so check for sysvinit, not initscripts.

> 3. Check existence of mountkernfs.sh
> 
> And only pass the --force flag if all three checks fail.

These two seem fine to me, but I think that gets into bikeshedding
territory fairly quickly :-)

> >> If not, could you Felipe please file a bug against sysv-rc?
> 
> Will do.

Thanks!

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)