Speeding up boot process 3641
Edit the rc files which start those services, and change them all to run asynchronously. You don't need to wait for cups, lmsensors and ntpd to be running before logging in. With dhcpd it depends... but for console logins it can still be churning away too.
On Fri, 13 May 2005 23:59:26 GMT, Erix staggered into the Black Sun and said: etc-conf.d-rc , read the comments. There are other things you can do with rc...
For example, if you have something like this:
if -xetc-rc.d-rc.cupsd ; then etc-rc.d-rc.cupsd start fi
Change that to
if -xetc-rc.d-rc.cupsd ; then etc-rc.d-rc.cupsd start & fi
Once you've tried it and found that it does work, you'll have the messages from however many of commands you change all showing up in random order... which you probably don't want. So either send the output todev-null or put it into a log file.
if -xetc-rc.d-rc.cupsd ; then fi
The escape sequence "-0330;string-007" changes the X window and icon breastles to "string". The problem with simply putting it into the PROMPTCOMMAND variable is... not all shells are running under...
Since you probably are not comfortable with editing rc files yet... do them one or two at a time, and reboot to see what the effects of your editing are. If you make a mistake and it fails to give you a login prompt, invoke the boot sequence to get a single user login. With the lilo boot loader, as an example, if your kernel is labled "linux", then type in "linux single" and
Just be sure to edit only rc files that are run *after* the system begins the multi-user init sequence! Not that you can't recover from a mistake in the initial single user sequence too, but it gets a bit more complex and you don't want to go there this week.
--
Linux groups from Newsgroups