Am Donnerstag 08 Oktober 2009 schrieb Dr. Werner Fink: > On Wed, Oct 07, 2009 at 03:29:20PM +0200, Petter Reinholdtsen wrote: > > One feature that might be good to have, is to be able to start > > gdm/kdm/xdm/wdm/etc as soon as possible during boot, and everything > > else after these scripts have started. Is it possible to get insserv > > to generate such sequence? > > > > I would like to specify to inssert to give priority to kdm, and > > everything not needed to start kdm should get a sequence number after > > kdm. > > > > How hard would it be to implement in insserv? The list of priority > > facilities would have to be fetched from a configuration file, or > > perhaps from the init.d scripts themselves (like X-Interactive). > > > > I guess I would end up with something like this in rc2.d/: > > > > S01rsyslog > > S02acpid > > S02dbus > > S03hal > > S04network-manager > > S05kdm > > S06... the rest ... > > > > A similar feature would be nice for startpar, to get kdm started > > earlier during boot. > > On openSuSE we use for xdm (also used for kdm and gdm) and syslog > further scripts called earlysyslog and earlyxdm. Those scripts And these scripts have an higher importance for startpar, "early" is an hardcoded prefix - and startpar will prefer the subtree reaching them. This works fairly well.
Greetings, Stephan _______________________________________________ initscripts-ng-devel mailing list initscripts-ng-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/initscripts-ng-devel
