2009/8/21 Petter Reinholdtsen <[email protected]> > [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?
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. my current ' ls /etc/rcS.d' is lrwxrwxrwx 1 root root 27 2008-09-07 K20console-screen.sh -> ../init.d/console-screen.sh -rw-r--r-- 1 root root 783 2007-12-23 README lrwxrwxrwx 1 root root 21 08-20 23:30 S01hostname.sh -> ../init.d/hostname.sh lrwxrwxrwx 1 root root 24 08-20 23:30 S01mountkernfs.sh -> ../init.d/mountkernfs.sh lrwxrwxrwx 1 root root 14 08-20 23:30 S02udev -> ../init.d/udev lrwxrwxrwx 1 root root 26 08-20 23:30 S03mountdevsubfs.sh -> ../init.d/mountdevsubfs.sh lrwxrwxrwx 1 root root 21 08-20 23:30 S03pcmciautils -> ../init.d/pcmciautils lrwxrwxrwx 1 root root 16 08-20 23:30 S03procps -> ../init.d/procps lrwxrwxrwx 1 root root 18 08-20 23:30 S04bootlogd -> ../init.d/bootlogd lrwxrwxrwx 1 root root 25 08-20 23:30 S04hwclockfirst.sh -> ../init.d/hwclockfirst.sh lrwxrwxrwx 1 root root 14 08-20 23:30 S04lvm2 -> ../init.d/lvm2 lrwxrwxrwx 1 root root 19 08-20 23:30 S05keymap.sh -> ../init.d/keymap.sh lrwxrwxrwx 1 root root 24 08-20 23:30 S06keyboard-setup -> ../init.d/keyboard-setup lrwxrwxrwx 1 root root 22 08-20 23:30 S07checkroot.sh -> ../init.d/checkroot.sh lrwxrwxrwx 1 root root 20 08-20 23:30 S08hwclock.sh -> ../init.d/hwclock.sh lrwxrwxrwx 1 root root 24 08-20 23:30 S08ifupdown-clean -> ../init.d/ifupdown-clean lrwxrwxrwx 1 root root 27 08-20 23:30 S08module-init-tools -> ../init.d/module-init-tools lrwxrwxrwx 1 root root 17 08-20 23:30 S08mtab.sh -> ../init.d/mtab.sh lrwxrwxrwx 1 root root 19 08-20 23:30 S08udev-mtab -> ../init.d/udev-mtab lrwxrwxrwx 1 root root 20 08-20 23:30 S09checkfs.sh -> ../init.d/checkfs.sh lrwxrwxrwx 1 root root 21 08-20 23:30 S10mountall.sh -> ../init.d/mountall.sh lrwxrwxrwx 1 root root 24 08-20 23:30 S10selinux-basics -> ../init.d/selinux-basics lrwxrwxrwx 1 root root 31 08-20 23:30 S11mountall-bootclean.sh -> ../init.d/mountall-bootclean.sh lrwxrwxrwx 1 root root 26 08-20 23:30 S12mountoverflowtmp -> ../init.d/mountoverflowtmp lrwxrwxrwx 1 root root 19 08-20 23:30 S13dns-clean -> ../init.d/dns-clean lrwxrwxrwx 1 root root 18 08-20 23:30 S13ebtables -> ../init.d/ebtables lrwxrwxrwx 1 root root 25 08-20 23:30 S13policycoreutils -> ../init.d/policycoreutils lrwxrwxrwx 1 root root 19 08-20 23:30 S13policykit -> ../init.d/policykit lrwxrwxrwx 1 root root 18 08-20 23:30 S13pppd-dns -> ../init.d/pppd-dns lrwxrwxrwx 1 root root 20 08-20 23:30 S13resolvconf -> ../init.d/resolvconf lrwxrwxrwx 1 root root 17 08-20 23:30 S13urandom -> ../init.d/urandom lrwxrwxrwx 1 root root 20 08-20 23:30 S13x11-common -> ../init.d/x11-common lrwxrwxrwx 1 root root 18 08-20 23:30 S14ifupdown -> ../init.d/ifupdown lrwxrwxrwx 1 root root 20 08-20 23:30 S15networking -> ../init.d/networking lrwxrwxrwx 1 root root 21 08-20 23:30 S16mountnfs.sh -> ../init.d/mountnfs.sh lrwxrwxrwx 1 root root 31 08-20 23:30 S17mountnfs-bootclean.sh -> ../init.d/mountnfs-bootclean.sh lrwxrwxrwx 1 root root 23 08-20 23:30 S18console-setup -> ../init.d/console-setup lrwxrwxrwx 1 root root 20 08-20 23:30 S19alsa-utils -> ../init.d/alsa-utils lrwxrwxrwx 1 root root 21 08-20 23:30 S19bootmisc.sh -> ../init.d/bootmisc.sh lrwxrwxrwx 1 root root 14 08-20 23:30 S19fuse -> ../init.d/fuse lrwxrwxrwx 1 root root 26 08-20 23:30 S19libdevmapper1.02 -> ../init.d/libdevmapper1.02 lrwxrwxrwx 1 root root 20 08-20 23:30 S19lm-sensors -> ../init.d/lm-sensors lrwxrwxrwx 1 root root 24 08-20 23:30 S19screen-cleanup -> ../init.d/screen-cleanup lrwxrwxrwx 1 root root 14 08-20 23:30 S19sudo -> ../init.d/sudo lrwxrwxrwx 1 root root 30 08-20 23:30 S20stop-bootlogd-single -> ../init.d/stop-bootlogd-single > > > > 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? for I installed upstart and other related package long long ago, and then I remove them, I cannot remember clearly which package I installed, which package change the boot sequence. I'm using insserv now, It looks like fine. 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. > libdevmapper1.02 belongs to package libdevmapper1.02, I found no package depend on it, so I removed it. currently /usr/share/insserv/check-initd-order gives no complain. Thank you very much -- Alan Guo http://bluestone.cublog.cn
_______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
