[Ian Zimmerman] > As elaborated in [1] , one of the easiest ways to speed up booting, or > at least improve the perception of speed (and isn't perception > everything? :-P ) is to start the X display manager (xdm, kdm, gdm or > whatever) early in the sequence. I just did the insserv transition > and I'd been quite curious where the xdm script would end up. I was > quite disappointed to find it again close to the end: at rc2.d/S06, > just before bootlogs (S07) and after cron, fetchmail, and mpd (S05).
Note that with parallel booting, which is the default in Squeeze, there is good in startpar to start xdm, kdm and gdm as early as possible, which will not be reflected in the static sequence numbers. > Furthermore, I can't see why insserv makes this decision: its > complete LSB dependencies are as follows: I suspect there is some reverse dependency in effect. Try to look at the dependency graph as generated by '/usr/share/insserv/check-initd-order -g' to get a better idea of the complete start ordering. > What is going on? Does the insserv sequence algorithm have a > special case for xdm? I would expect some script having X-Start-Before (reverse dependency) on xdm. There is no special handling of xdm in insserv. 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
