Linked by Tony Steidler-Dennison on Wed 30th Jul 2008 18:54 UTC
Thread beginning with comment 325086
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-11-21
#5 Change your OS
#6 Change your hardware
#10 is the only interesting one and it isn't explained at all.
From /etc/init.d/rc on Debian SID
# Specify method used to enable concurrent init.d scripts.
# Valid options are 'none', 'shell' and 'startpar'. To enable the
# concurrent boot option, the init.d script order must allow for
# concurrency. This is not the case with the default boot sequence in
# Debian as of 2008-01-20. Before enabling concurrency, one need to
# check the sequence values of all boot scripts, and make sure only
# scripts that can be started in parallel have the same sequence
# number, and that a scripts dependencies have a earlier sequence
# number. See the insserv package for a away to reorder the boot
# automatically to allow this.
CONCURRENCY=none
INNSERV configuration is at /etc/insserv.conf
/usr/share/doc/insserv/README.Debian which explains the whole thing:
To test dependency based reordering of the boot sequence, install the
package, enable parallel booting, and run update-bootsystems-insserv
to make a backup of the boot sequence and reorder the boot scripts.
Be careful to verify the boot sequence before rebooting, as an
incorrect boot sequence can render the system completely unbootable.
In short:
# Enable parallel booting
echo CONCURRENCY=shell >> /etc/default/rcS
# Update boot sequence
update-bootsystem-insserv
# At this point, I recommend examining the order in /etc/rcS.d/ and
# /etc/rc2.d/ carefully, to verify that the configuration actually
# will boot. Update /etc/insserv/overrides/ or
# /usr/share/insserv/overrides/ with better dependency information
# if the boot order is incorrect, and run insserv -v to update the
# boot order.
# Ready to reboot
shutdown -r now
The next boot should then start services in parallel, as early as
possible during the boot process based on the dependency information
provided.
To monitor the boot sequence, the bootchart project is a good choice.
Debian packages are available in etch and sid. The project itself is
available from http://www.bootchart.org/.
Background info on alternative boot systems in Debian is available from
http://alioth.debian.org/docman/view.php/30730/38/debconf2-initscri....
In a nutshell, if you're not interested in getting down into the weeds I wouldn't fix what isn't broken.