[Rik Theys] > Here's the output from the ls command: > > /etc/rc6.d/: > K01alsa-utils K01fuse K01network-manager K01postfix K03mysql-ndb > S01umountnfs.sh S16auditd > K01anacron K01irqbalance K01ntp K01rsync > K04mysql-ndb-mgm S01umountroot S16networking > K01atd K01joystick K01nvidia-glx K01saned K06hwclock.sh > S09cryptdisks-early S17wpa-ifupdown > K01bluetooth K01kdm K01nvidia-kernel K01stunnel4 README > S10lvm2 S21urandom > K01cpufrequtils K01kvm K01openbsd-inetd K01uml-utilities > S01reboot S11cryptdisks K01cron K01laptop-mode K01openvpn > K02avahi-daemon S01sendsigs S13ifupdown > K01dirmngr K01libvirt-bin K01pcscd K02mysql S01umountfs > S14rsyslog
This ordering is very strange. How did you enable dependency based boot sequencing? Was this done using the insserv or sysv-rc package scripts, or some other way? When done the normal way, all S* symlinks in rc0.d and rc6.d would be changed to K* symlinks to reflect how scripts are actually called in these runlevels. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
