On Wed, Nov 12, 2008 at 18:31:20 -0600,
Les Mikesell <lesmikesell(a)gmail.com> wrote:
Jesse Keating wrote:
> On Wed, 2008-11-12 at 17:41 -0600, Les Mikesell wrote:
>> No argument about the value - but it seems similar to the need for
>> the md devices at boot time. If you don't need it, why include it in
>> the install? A tool help modify initrd post-install would be nice to
>> fix things up when the boot hardware or requirements change, though.
>
> Now you've lost me.
When you install, something decides whether or not to include the md
module in the installed initrd. Shouldn't the same decision be made for
whatever handles encryption and any other services it will need at
about the same time? Hmmm, maybe that's a different choice than whether
it needs to be available, though.
mkinitrd I believe. I have had problems with yum upgrades where mkinitrd
didn't include all of the modules the new kernel was going to need, because
it was basing something on how it worked on the installed kernel.