From: Petter Reinholdtsen
Script ordering is vital for this to work. And how are the scripts -ordered? By numbers! +ordered? By numbers 01-99!
And the numbers are picked using skills, knowledge and negotiation. Getting it right is often hard.
The current Debian default is wrong. The stop sequence should by -default be the reverse of the start sequence. It isn't. +default be the reverse of the start sequence. It isn't. The default +uses '20' for both.
Reordering is hard and sometimes requires cooperation between maintainers of all packages involved. @@ -228,7 +229,7 @@ Two options are available with the insserv package:
Incorrect dependencies give the wrong but predictable and stable (as in the same all the time) boot and shutdown order.
+Every insserv upload are checked using test suite to make sure the +generated boot sequence is correct, and that previously detected bugs +do not show up again.
+It is possible to enable concurrent booting, running boot scripts in parallel (CONCURRENCY=startpar in /etc/default/rcS)
@@ -385,6 +390,8 @@ facility, then that daemon has been started.All of these represent points in time during boot and shutdown. +Virtual facilities are defined in /etc/insserv.conf and +/etc/insserv.conf.d/
A sysadmin can provide overrides in +/etc/insserv/overrides/scriptname if the script settings are +wrong. The insserv package provides overrides in +/usr/share/insserv/overrides/ for packages currently missing +headers.
Release goal for Debian Lenny.
-
76% of packages got LSB headers
+
76% of packages got LSB headers.
Unsolved in BTS: ~85
Without BTS reports: ~150
Last package will be fixed 2008-06-13 at the current rate.