Check out man mkinitrd. seems like I have always just given it the kernel version and the imgfile name needed.
I guess the real question is do you really need an initrd? Unless you need something like scsi drivers that you compiled as modules that need to be availible before the file systems are availible you should not need one. If unsure, comment out the line in lilo that refers to it, run lilo again and reboot. Bret On Sat, at 22:50, Brandon Robert Dorman wrote: > Hey guys, > > Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing > my lilo.conf, ran /sbin/lilo and got this: > Added linux > fatal: open /boot/initrd-2.4.17: no such file or directory. Sure > enough, a ls of /boot shows: > > ls /boot > > boot.b kernel.h module-info-2.4.7-10 vmlinuz > chain.b kernel.h-2.4.7 os2_d.b > vmlinuz-2.4.17 > grub message System.map > vmlinuz-2.4.7-10 > initrd-2.4.7-10.img module-info System.map-2.4.7-10 > > No initrd. Where can i copy it from? This is my first time compiling a > kernel after about 2.5 years working off and on with linux, i followed > the howtos but am stumped here. Thanks. > > -Brandon > [EMAIL PROTECTED] > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
