On Thu, 14 Jun 2001 18:13:09 -0600,
"D. Stimits" <stimits@xxxxxxxxxx> wrote:
>Keith Owens wrote:
>> On Thu, 14 Jun 2001 14:06:19 -0600,
>> "D. Stimits" <stimits@xxxxxxxxxx> wrote:
>> >Interesting that it is not there. Wouldn't modprobe be normal on
>> >mkinitrd?
>>
>> Only on a full blown install ramdisk. End users with initrd are
>> assumed to be using a tuned list of modules. mkinitrd inserts explicit
>> insmod commands in linuxrc, based on the modules you specify during
>> mkinitrd. modprobe is only useful when you do not know ahead of time
>> which modules you will be using.
>
>So I have to wonder then why this install based mkinitrd.xfs is asking
>for modprobe? Is that a bug in the mkinitrd.xfs that it attempts to use
>modprobe?
As I said in a previous mail, you compiled the kernel for automatic
module loading (kmod). It is kmod inside the kernel that is invoking
modprobe, looking for the module to do scsi_hostadaptor. That has
nothing to do with mkinitrd.
|