[Pkg-sysvinit-devel] Bug#537394: initscripts: /etc/rcS.d/S46mountnfs-bootclean.sh accidently delete vde2 pid files and mgmt files in /var/run/vde2/

[Petter Reinholdtsen]

[Alan Guo]
> I've install insserv and current /usr/share/insserv/check-initd-order is
>  blueice2:~# /usr/share/insserv/check-initd-order
> error: LSB header missing in /etc/rcS.d/S20libdevmapper1.02

This show at least that no scripts have a boot sequence in conflict
with their dependencies, which is good.

> insserv: dryrun, not creating .depend.boot, .depend.start, and
> .depend.stop

This indicated that the boot sequence have been ordered using
dependencies earlier or is currenty in effect (if not, a lot more
changes would have been proposed).  As far as I could tell, the boot
sequence is mostly OK on your machine.  I am a bit surprised, as I
would expect more changes compared to the list you sent earlier about
the content in /etc/rcS.d/.  Can you send the output from 'ls
/etc/rcS.d' now?

> I've ever install upstart, and uninstall it several days later, I
> think, maybe when I install upstart, symbol links in /etc/rc*.d is
> modified, but when I uninstall it, boot sequence have not been
> restored.

As far as I know, upstart do not change the boot sequence.  insserv
change the boot sequence.  Anyway, since a few weeks ago, dependency
based boot sequencing using insserv is the default in Debian/unstable,
so perhaps it is a good way forward for you to enable it too?

To do this, the obsolete libdevmapper1.02 script should be removed (I
suspect its package is removed but not purged), and 'dpkg-reconfigure
insserv' called to enable insserv if it isn't enabled already.

Happy hacking,
--
Petter Reinholdtsen