| To: | stimits@xxxxxxxxxx |
|---|---|
| Subject: | Re: mkinitrd, ramdisk failure? |
| From: | Keith Owens <kaos@xxxxxxxxxxxxxxxxx> |
| Date: | Fri, 15 Jun 2001 09:45:34 +1000 |
| Cc: | "XFS: linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | Your message of "Thu, 14 Jun 2001 14:06:19 CST." <3B29193B.4E1125D9@idcomm.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Thu, 14 Jun 2001 14:06:19 -0600, "D. Stimits" <stimits@xxxxxxxxxx> wrote: >Keith Owens wrote: >> is no such file or directory. Your initrd does not contain >> /sbin/modprobe, initrd normally only contains insmod to save space. > >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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: cvs [server aborted]: EOF in key in RCS file /cvs/linux-2.4-xfs/linux/fs/xfs/xfs_buf_item.h,v, Bernhard R. Erdmann |
|---|---|
| Next by Date: | do_softirq, Bernhard R. Erdmann |
| Previous by Thread: | Re: mkinitrd, ramdisk failure?, D. Stimits |
| Next by Thread: | Re: mkinitrd, ramdisk failure?, D. Stimits |
| Indexes: | [Date] [Thread] [Top] [All Lists] |