Linuzoid,

I would like to see a comment from someone about why - apparently - the building of the initrd image might take a long time in some cases and get done quickly in other cases.
That is if it is really the creation of the initrd that is delaying things of course ...... 
I "think" it is the creation of the initrd, I remember posts about old machine where that phase took more than half an hour, I remember also (from other posts) that sometimes the initrd size were at least double than the usual 5 or 6 MB ...
What's the initrd ? It is small filesystem, containing approx. 200 files: basic command, basic libs, basic drivers needed to start the the kernel and including at least the drivers to correctly mount a root filesystems (therefore hw drivers and filesystem modules, like ext3, ext4 ...). The format of initrd is a cpio archive, gzip compressed, if you want to check the initrd content this command should do:
zcat /boot/initrd.img | cpio -itvalternatively the following will provide the complete listing and additionally the code of the
init script:
lsinitrd /boot/initrd.imgOn system with less powerful CPU the compression may take longer ...
From another point of view, the included modules depends from the detected hardware and from modules specified in /etc/modprobe* ... I guess there is a some variable depending on the running system ...
Does explain such long times ?

... probably not completely ...