-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 11 March 2004 04:33, Ivan Teliatnikov wrote: > The initrd is typically used for temporarily booting the hardware into a > state, that the real kernel vmlinuz can than take over and continue the > booting. For example - you can't read the kernel off the scsi hard disk > until you have a scsi driver loaded in the kernel. > > My /etc/grub.conf points to non-existing image. Is this correct? > > title Red Hat Linux (2.4.20-30.7.legacy) > root (hd0,0) > kernel /vmlinuz-2.4.20-30.7.legacy ro root=/dev/hda9 > initrd /initrd-2.4.20-30.7.legacy.img > > I can manually create this image running command > mkinitrd /initrd-2.4.20-30.7.legacy.img 2.4.20-30.7.legacy Making of the initrd is part of the kernel %post script. If, for some reason, you're using a 3rd party module in your current kernel, that initrd thinks is required, then you should have gotten a message about the %post script failing. In all the tests I did, I use rpm manually or with yum, and the initrd.img was created. Can anybody else duplicate this failure using apt? - -- Jesse Keating RHCE (http://geek.j2solutions.net) Fedora Legacy Team (http://www.fedoralegacy.org) GPG Public Key (http://geek.j2solutions.net/jkeating.j2solutions.pub) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAUITK4v2HLvE71NURArPOAJ9sKxL5ykvDCyOVVWica4dlCtWCCACfYApq OTOJx8JF0y5QB6CzM4n7p1o= =hwZY -----END PGP SIGNATURE-----
