HowTo: Speed up ubuntu boot process - the way you can feel it.

[yaaarrrgg]

also, here's a one line hack that worked good for me on breezy ... run startup scripts in parallel, merely by changing the startup script: /etc/init.d/rc

Changing the line:

startup $i start

to the following:

startup $i start &

from:
http://www.debian-administration.org/articles/199
http://www.hoeg.org/blog/2005/07/27/...ooting-debian/

[joergenlie]

Quote:
Originally Posted by IdolizingStewie
I followed this How-To a couple days ago and, like an idiot, failed to note the specific changes I was making. I finally got around to rebooting today and when the computer starts back up it gives me an internal error "Failed to initialize HAL." Can anyone tell me which services I need for HAL and maybe what runlevels they need to be on? I suspect this is why I can no longer mount my external HDD which, while not vital, is extremely annoying since it has all my music.

Enable hotplug at runlevel S and try again.

My hotplug runlevel is aat S, still I get "failed to initialize HAL" ?

Jørgen

[i3dmaster]

I used this and I now can't get my network to boot at startup.
I don't mind it too much, except I have to remember to manually boot the network interface.
When i get home i will go over the things I turned off and post it around here.
If i'm not too mistakened I only turned things off like the howto. However i'm not too assured of it. I remember going over the things and starting them one by one booting and reebooting, and going over it over and over. Nothing worked and i gave up on it.

Only now to remember about it.

If you laptop wouldn't bootup, then one way to fix it is just like the other guy here to use the liveCD. Please refer to the thread. Also, in order to learn a bit more not just fixing, a better place to look at what the hell was wrong is the system log. Go to /var/log dir and look at message, bootlog, dmesg, faillog, kern.log files, etc... for the timeline closest to the accident time and see if there is anything indicating what went wrong during the last boot.

[i3dmaster]

Quote:
Originally Posted by IdolizingStewie
I followed this How-To a couple days ago and, like an idiot, failed to note the specific changes I was making. I finally got around to rebooting today and when the computer starts back up it gives me an internal error "Failed to initialize HAL." Can anyone tell me which services I need for HAL and maybe what runlevels they need to be on? I suspect this is why I can no longer mount my external HDD which, while not vital, is extremely annoying since it has all my music.

Enable hotplug at runlevel S and try again.

My hotplug runlevel is aat S, still I get "failed to initialize HAL" ?

Jørgen

that's actually your dbus system. Check that out.

[gilchris]

I want to translate this HowTo into Korean.

already finished translation.

I want to upload this translated Howto on Korean Ubuntu users group(http://ubuntu.or.kr) if you don't mind this translation is uploaded.

[sailor420]

also, here's a one line hack that worked good for me on breezy ... run startup scripts in parallel, merely by changing the startup script: /etc/init.d/rc

Changing the line:

startup $i start

to the following:

startup $i start &

from:
http://www.debian-administration.org/articles/199
http://www.hoeg.org/blog/2005/07/27/...ooting-debian/

Nice. That knocked a few seconds off my boot time, beyond all the tweaking here. I don't think much anything else other than InitNG (which isn't working for me) is gonna get my boot time below 1 minute though--damn slow laptop hard drive.

[i3dmaster]

Nice. That knocked a few seconds off my boot time, beyond all the tweaking here. I don't think much anything else other than InitNG (which isn't working for me) is gonna get my boot time below 1 minute though--damn slow laptop hard drive.

That's acutally a pretty good point!

[Sokraates]

also, here's a one line hack that worked good for me on breezy ... run startup scripts in parallel, merely by changing the startup script: /etc/init.d/rc

Changing the line:

startup $i start

to the following:

startup $i start &

from:
http://www.debian-administration.org/articles/199
http://www.hoeg.org/blog/2005/07/27/...ooting-debian/

Great idea. The only annoyance is, that CLI appears for about a second or two before KDM starts.

Not even a minor prob, simply cosmetics, but does anyone have an idea, how runlevels could be tweaked to avoid this?

[ashrack]

What was the original setting for "readahead"?

[brainkilla]

@i3dmaster
You, Sir, are a genius. Very good how-to. I used to use rcconf and recently I've discovered BUM, which does more or less the same but within a GUI. But I could not get rid of that damn raid sh*t starting and LVM and crap... this is a life saver, booting is now shorter for like 10 sec or more... thanx!