[Petter Reinholdtsen] > I notice you tried a few things with reordering. I've tested insserv > recently myself, and discovered my accident that it will do a very > poor job if it claim to find loops in the dependency graph.
And there is such loop in the dependency graph today. I investigated it this evening, and believe I found the problem in init.d/keymap.sh. By editing /etc/init.d/keymap.sh and /usr/share/insserv/overrides/keymap.sh, and removing '$syslog' from the LSB header, I believe insserv should be able to to a better job reordering the boot sequence. To detect the loop, I looked for upward-pointing arrays in the graph displayed when running /usr/share/insserv/check-initd-order -g > bootorder.dotty dotty bootorder.dotty After identifying the loop, I had a look at the scripts involved and discovered that keymap.sh was expected to run early, but depended on syslog which starts very late (in runlevel 2, actually). The dependency bug is reported as #386338. JFYI. Friendly, -- Petter Reinholdtsen _______________________________________________ initscripts-ng-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/initscripts-ng-devel
