Execute "ls /lib/modules" and see what you have. When you issue the mkbootdisk command, the kernel version has to match one of the entries in that directory.
BTW...if you're planning on using /dev/fd0, anyhow, you can omit the "--device /dev/fd0" parameter. On Tue, 2 Jul 2002, Hahnel William J wrote: > Hello, > > I'm trying to create a boot disk for my 2.4.17-0.16 kernel but I'm not > having any luck. The command being used is: > > mkbootdisk --device /dev/fd0 2.4.17-0.16 > > I'm getting the message that there is no space left on the diskette. This > makes sense since I looked at my /boot and found the following as the file > sizes: > > [root /boot]# ls -l initrd-2.4.17-0.16.img > -rw-r--r-- 1 root root 440211 Feb 14 08:58 > initrd-2.4.17-0.16.img > [root /boot]# ls -l vmlinuz-2.4.17-0.16 > -rw-r--r-- 1 root root 1032679 Feb 10 13:40 vmlinuz-2.4.17-0.16 > > Anyone have a solution they would care to share?? > > Thanks, > > Bill Hahnel > _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
