Post a Comment
I noticed, yesterday, that readahead was not in the default install for my Fedora 8 machines. Looking at the boot charts, it looks like 8 and 9 do not use it. Anyone have info on the rationale? It was always a bit of a hack. But my understanding was that it *did* help.
Arch Linux Boot Performance:
http://fopref.meinungsverstaerker.de/div/bootchart1.png
http://fopref.meinungsverstaerker.de/div/bootchart2.png
;-)
I tried ArchLinux about two months ago and the boot time was slower than in most distros because loading udev uevents took almost a minute to finish. I checked the ArchLinux forums and it appears that a lot of users have experienced the same issue, especially those whose computer is a bit old.
shrug,
udev has nothing to do with Arch boot problems.
udev events is causing problems.
You can disable udev events but this will cause boot problems once in a while.
Safer option is to try udev/module-init-tools/initscripts from Arch testing repository.
You need to know what are you doing and you need to remember that these packages are from testing.
The above should speed up default Arch boot time. On system tweaked already this will not have much of impact on boot time.
on HP laptop with SATA 5400RPM/1GB RAM I am getting 21-23s with Arch/KDE and custom kernel 2.6.24-zen4.
Of course faster disk better timing. Of course booting to cli would be much faster.
In general kernel and linux software tend to slow down but distros put extra glue to slow things down even more.
Bootchart _is_ in the fedora repo, so "yum install bootchart" is just enough to have it installed.
At a quick inspection, I did not find in the Ubuntu review which version they installed. If it was the LiveCD, they should make a comparison with the Fedora one because the default services list is very diverse.








