2009/8/21 Petter Reinholdtsen <span dir="ltr"><<a href="mailto:pere@hungry.com" target="_blank">pere@hungry.com</a>></span><div class="im"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[Alan Guo]<br>
<div>> I've install insserv and current /usr/share/insserv/check-initd-order is<br>
> blueice2:~# /usr/share/insserv/check-initd-order<br>
> error: LSB header missing in /etc/rcS.d/S20libdevmapper1.02<br>
<br>
</div>This show at least that no scripts have a boot sequence in conflict<br>
with their dependencies, which is good.<br>
<div><br>
> insserv: dryrun, not creating .depend.boot, .depend.start, and<br>
> .depend.stop<br>
<br>
</div>This indicated that the boot sequence have been ordered using<br>
dependencies earlier or is currenty in effect (if not, a lot more<br>
changes would have been proposed). As far as I could tell, the boot<br>
sequence is mostly OK on your machine. I am a bit surprised, as I<br>
would expect more changes compared to the list you sent earlier about<br>
the content in /etc/rcS.d/. Can you send the output from 'ls<br>
/etc/rcS.d' now?</blockquote><div> </div></div><div>In you previous mail, you told me to run '/usr/share/insserv/check-initd-order' and 'insserv -vn', so i installed insserv. when installing insserv, boot orders was changed to current status.</div>
<div><br></div><div>my current ' ls /etc/rcS.d' is </div><div>lrwxrwxrwx 1 root root 27 2008-09-07 K20console-screen.sh -> ../init.d/console-screen.sh<br>-rw-r--r-- 1 root root 783 2007-12-23 README<br>
lrwxrwxrwx 1 root root 21 08-20 23:30 S01hostname.sh -> ../init.d/hostname.sh<br>lrwxrwxrwx 1 root root 24 08-20 23:30 S01mountkernfs.sh -> ../init.d/mountkernfs.sh<br>lrwxrwxrwx 1 root root 14 08-20 23:30 S02udev -> ../init.d/udev<br>
lrwxrwxrwx 1 root root 26 08-20 23:30 S03mountdevsubfs.sh -> ../init.d/mountdevsubfs.sh<br>lrwxrwxrwx 1 root root 21 08-20 23:30 S03pcmciautils -> ../init.d/pcmciautils<br>lrwxrwxrwx 1 root root 16 08-20 23:30 S03procps -> ../init.d/procps<br>
lrwxrwxrwx 1 root root 18 08-20 23:30 S04bootlogd -> ../init.d/bootlogd<br>lrwxrwxrwx 1 root root 25 08-20 23:30 S04hwclockfirst.sh -> ../init.d/hwclockfirst.sh<br>lrwxrwxrwx 1 root root 14 08-20 23:30 S04lvm2 -> ../init.d/lvm2<br>
lrwxrwxrwx 1 root root 19 08-20 23:30 S05keymap.sh -> ../init.d/keymap.sh<br>lrwxrwxrwx 1 root root 24 08-20 23:30 S06keyboard-setup -> ../init.d/keyboard-setup<br>lrwxrwxrwx 1 root root 22 08-20 23:30 S07checkroot.sh -> ../init.d/checkroot.sh<br>
lrwxrwxrwx 1 root root 20 08-20 23:30 S08hwclock.sh -> ../init.d/hwclock.sh<br>lrwxrwxrwx 1 root root 24 08-20 23:30 S08ifupdown-clean -> ../init.d/ifupdown-clean<br>lrwxrwxrwx 1 root root 27 08-20 23:30 S08module-init-tools -> ../init.d/module-init-tools<br>
lrwxrwxrwx 1 root root 17 08-20 23:30 S08mtab.sh -> ../init.d/mtab.sh<br>lrwxrwxrwx 1 root root 19 08-20 23:30 S08udev-mtab -> ../init.d/udev-mtab<br>lrwxrwxrwx 1 root root 20 08-20 23:30 S09checkfs.sh -> ../init.d/checkfs.sh<br>
lrwxrwxrwx 1 root root 21 08-20 23:30 S10mountall.sh -> ../init.d/mountall.sh<br>lrwxrwxrwx 1 root root 24 08-20 23:30 S10selinux-basics -> ../init.d/selinux-basics<br>lrwxrwxrwx 1 root root 31 08-20 23:30 S11mountall-bootclean.sh -> ../init.d/mountall-bootclean.sh<br>
lrwxrwxrwx 1 root root 26 08-20 23:30 S12mountoverflowtmp -> ../init.d/mountoverflowtmp<br>lrwxrwxrwx 1 root root 19 08-20 23:30 S13dns-clean -> ../init.d/dns-clean<br>lrwxrwxrwx 1 root root 18 08-20 23:30 S13ebtables -> ../init.d/ebtables<br>
lrwxrwxrwx 1 root root 25 08-20 23:30 S13policycoreutils -> ../init.d/policycoreutils<br>lrwxrwxrwx 1 root root 19 08-20 23:30 S13policykit -> ../init.d/policykit<br>lrwxrwxrwx 1 root root 18 08-20 23:30 S13pppd-dns -> ../init.d/pppd-dns<br>
lrwxrwxrwx 1 root root 20 08-20 23:30 S13resolvconf -> ../init.d/resolvconf<br>lrwxrwxrwx 1 root root 17 08-20 23:30 S13urandom -> ../init.d/urandom<br>lrwxrwxrwx 1 root root 20 08-20 23:30 S13x11-common -> ../init.d/x11-common<br>
lrwxrwxrwx 1 root root 18 08-20 23:30 S14ifupdown -> ../init.d/ifupdown<br>lrwxrwxrwx 1 root root 20 08-20 23:30 S15networking -> ../init.d/networking<br>lrwxrwxrwx 1 root root 21 08-20 23:30 S16mountnfs.sh -> ../init.d/mountnfs.sh<br>
lrwxrwxrwx 1 root root 31 08-20 23:30 S17mountnfs-bootclean.sh -> ../init.d/mountnfs-bootclean.sh<br>lrwxrwxrwx 1 root root 23 08-20 23:30 S18console-setup -> ../init.d/console-setup<br>lrwxrwxrwx 1 root root 20 08-20 23:30 S19alsa-utils -> ../init.d/alsa-utils<br>
lrwxrwxrwx 1 root root 21 08-20 23:30 S19bootmisc.sh -> ../init.d/bootmisc.sh<br>lrwxrwxrwx 1 root root 14 08-20 23:30 S19fuse -> ../init.d/fuse<br>lrwxrwxrwx 1 root root 26 08-20 23:30 S19libdevmapper1.02 -> ../init.d/libdevmapper1.02<br>
lrwxrwxrwx 1 root root 20 08-20 23:30 S19lm-sensors -> ../init.d/lm-sensors<br>lrwxrwxrwx 1 root root 24 08-20 23:30 S19screen-cleanup -> ../init.d/screen-cleanup<br>lrwxrwxrwx 1 root root 14 08-20 23:30 S19sudo -> ../init.d/sudo<br>
lrwxrwxrwx 1 root root 30 08-20 23:30 S20stop-bootlogd-single -> ../init.d/stop-bootlogd-single<br><br></div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<div><br>
> I've ever install upstart, and uninstall it several days later, I<br>
> think, maybe when I install upstart, symbol links in /etc/rc*.d is<br>
> modified, but when I uninstall it, boot sequence have not been<br>
> restored.<br>
<br>
</div>As far as I know, upstart do not change the boot sequence. insserv<br>
change the boot sequence. Anyway, since a few weeks ago, dependency<br>
based boot sequencing using insserv is the default in Debian/unstable,<br> so perhaps it is a good way forward for you to enable it too?</blockquote><div> </div></div><div> for I installed upstart and other related package long long ago, and then I remove them, I cannot remember clearly </div>
<div> which package I installed, which package change the boot sequence. </div><div><br></div><div>I'm using insserv now, It looks like fine. </div><div class="im"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
To do this, the obsolete libdevmapper1.02 script should be removed (I<br>
suspect its package is removed but not purged), and 'dpkg-reconfigure<br>
insserv' called to enable insserv if it isn't enabled already.<br>
</blockquote><div> </div></div><div> libdevmapper1.02 belongs to package libdevmapper1.02, I found no package depend on it, so I removed it. currently </div><div>/usr/share/insserv/check-initd-order gives no complain.</div>
<div><br></div><div>Thank you very much </div><div><br></div><div>-- <br></div><div><div class="h5">Alan Guo<br><a href="http://bluestone.cublog.cn" target="_blank">http://bluestone.cublog.cn</a></div></div><br>