[Michael Biebl] > I don't think there is anything to fix here specifically in udev and > is sort-of expected behaviour.
Actually, udev can fix this by adding a stop symlink in rc1.d and start symlinks in rc2.d to rc5.d. Then sysv-rc will know that udev was stopped in rc1.d and start it again in rc2.d. sysv-rc will also know that udev was already started in rcS.d and not start it again in rc2.d during boot. :) To summarize, create something like this: /etc/rcS.d/S03udev /etc/rc1.d/K03udev /etc/rc2.d/S03udev /etc/rc3.d/S03udev /etc/rc4.d/S03udev /etc/rc5.d/S03udev No need to stop it in runlevels 0 and 6, as there is no way to return from them (they turn off or reboot the machine). This should be done by all services starting daemons in rcS.d/. :) But most of them should really move out of rcS.d and start in rc2.d to rc5.d instead hdparm is one such example. hdparm is not required to be running to get a working single user login shell. :) -- 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
