I tried to make my system boot as fast as possible too, and the two really important improvements where :

1) MOD_AUTOLOAD = no and put all needed modules in MODULES in /etc/rc.conf

2) tune mkinitcpio.conf to specify only needed modules and remove all unneeded HOOKS (including udev and autodetect)

If you don't need autodetect but want to keep udev, I think it should also speedup boot. If you want to keep udev and autodetect, I don't think you can do better.

Colin Pitrat (Bull Services Telco)
Bull,  Architect of an Open World (TM)
Tél : +33 (0)  1 30 80 72 93
www.bull.com


-------- Message original --------
De: Dimitrios Apostolou <[EMAIL PROTECTED]>
Pour: General Discusson about Arch Linux <[email protected]>
> Date: 23/07/2007 1:37:55 PM +0200
Objet: [arch] How fast could boot Arch?

My primary complaint for the long boot time is udev... It takes 20 seconds on my 800MHz system, even if I disable MOD_AUTOLOAD. But I guess this is not arch specific, I have seen similar times on other distros as well and even minutes of wait time on older systems. I suppose it has to do with the "including the kitchen-sink" default kernel, which causes udev_settle to wait for too many triggered events. So one solution would be to compile a custom kernel, with only the necessary modules enabled. Any other ideas on improving udev?

Dimitris

_______________________________________________
arch mailing list
[email protected]
http://archlinux.org/mailman/listinfo/arch

begin:vcard
fn:Colin Pitrat
n:Pitrat;Colin
org:Bull;Telco
adr:;;rue Jean Jaures;Les Clayes sous Bois;;78340;France
email;internet:[EMAIL PROTECTED]
tel;work:+33 1 30 80 72 93
x-mozilla-html:FALSE
url:http://www.bull.com
version:2.1
end:vcard

_______________________________________________
arch mailing list
[email protected]
http://archlinux.org/mailman/listinfo/arch

Reply via email to