Package: insserv Version: 1.14.0-2 Severity: normal
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). Furthermore, I can't see why insserv makes this decision: its complete LSB dependencies are as follows: # Required-Start: $local_fs $remote_fs # Required-Stop: $local_fs $remote_fs # Should-Start: xfs $named slapd hal # Should-Stop: xfs $named slapd hal The components of *_fs are not present in rc2 ; I don't have anything from the Should-Start installed (ie. none of the packages with the scripts listed directly, nor any of the components of $named). What is going on? Does the insserv sequence algorithm have a special case for xdm? [1] http://www.debian-administration.org/articles/620 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.34.1-core2-i (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages insserv depends on: ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib insserv recommends no packages. Versions of packages insserv suggests: pn bootchart <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
