speeding up boot even more? (rebuild mkinitrd)

[Bill Davidsen]

Tom Horsley wrote:
> On Mon, 04 May 2009 23:44:49 -0400
> Will Woods wrote:
> 
>> Nope. mkinitrd is pretty smart - if you don't have mdraid/dmraid/LVM
>> volumes, it doesn't bother putting the modules / setup code in the
>> initrd. 
> 
> Then why do I get all the messages before udev up around the time
> initrd is running about "no raids found" and such?
> 
>> In short: don't bother, it won't change anything. But if you must.. 
>> kv=$(uname -r); mkinitrd --stuff -v -f /boot/initrd-$kv.img $kv 
> 
> Yea, I finally realized I could find the code running mkinitrd
> in the postinstall script for the kernel package and dug out much
> the same thing. Weirdly, I get an initrd image that is almost
> twice as big when I omit lots of stuff :-).
> 
As Will said "Nope. mkinitrd is pretty smart" and he meant it. ;-)

-- 
Bill Davidsen <davidsen at tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot