On Wed, Dec 25, 2002 at 08:55:02AM -0500, Robert P. J. Day wrote:
as it stands, the only modules supplied by red hat's
current initrd.img are for ext3 and jbd, so it's easy
enough to build those into a new kernel and not have
to mess with initrd any more. is this a fair
observation?
Only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Javier Gostling wrote:
|
| Only in ide drive systems. If your root FS is on a SCSI drive, initrd
| also loads the SCSI controller's driver.
You can safely compile SCSI drivers into the kernel as well in order to
completely do away w/ the initrd.
On Thu, 26 Dec 2002, Javier Gostling wrote:
On Wed, Dec 25, 2002 at 08:55:02AM -0500, Robert P. J. Day wrote:
as it stands, the only modules supplied by red hat's
current initrd.img are for ext3 and jbd, so it's easy
enough to build those into a new kernel and not have
to mess with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert P. J. Day wrote:
| ah, so the initrd.img file is built at installation time
| based on HW detection, is it? of course, that makes sense.
| that suggests that any more digging into that topic would
| probably be more appropriate on the
On Thu, 26 Dec 2002 10:30:14 -0500 (EST), Robert P. J. Day
[EMAIL PROTECTED] wrote:
Only in ide drive systems. If your root FS is on a SCSI drive, initrd
also loads the SCSI controller's driver.
ah, so the initrd.img file is built at installation time
based on HW detection, is it? of course,
On Thu, 26 Dec 2002, Rick Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert P. J. Day wrote:
| ah, so the initrd.img file is built at installation time
| based on HW detection, is it? of course, that makes sense.
| that suggests that any more digging into that topic
for the longest time, when i was teaching students how to
rebuild a kernel, i would explain the purpose of the file
/boot/initrd.img, but suggest that they could avoid having
to deal with one by just compiling the necessary modules
into the kernel and be done with it once and for all, and
not
