Quote:
Originally Posted by bluesman2333
I've never bothered because my boot times are so short anyway. You can always kill the processes then use the system to see how everything works before you change filenames.
|
Hi,
I think there's something wrong in this reply:
1- Sometime you wont see effects of killing processes till next reboot.
2- If you are using the P4 (2,5GHz as you've written) and boot scripts out-of-the box your
boot time is not so fast and if it could be faster I think tuning is a good idea, don't
you?
3- With Edgy some boot scripts moved from /etc/rc2.d to /etc/rcS.d such as brltty.
Apart scripts originally lying in /etc/rc2.d it's not sufficient to rename the script,
in /etc/rcS.d, if we don't like it to start at boot time.
The reason is lots of scripts in /etc/rcS. have dependencies, it means if you don't want
this process at boot time you have to rewrite scripts not just rename them.
For instance it's not necessary to check filesystems everytime at boot so we could desire to disable the script checkfs.sh 'cause we are not interested in controlling other filesystem, apart root one, unfortunately this script has dependencies so the only way to disable it is to redesign and rewrite scripts depending on it.
I consider this procedure of rewriting but it takes a lot of time, so nevermind I'll use more often hibernation.
I can gain time with a little "trick": I remove all partions in /etc/fstab, except root and swap, so the script still remain at boot time, but it doesn't have partion to check!
I hope this could be useful,
deadlinx
----------------------------------------------------------------------------------------------
Ubuntu Edgy, flwm, Core Duo T2400 (1,83Ghz)