Hi, I've compiled a kernel from scratch from kernel.org.
I was able to get it to load correctly. However, I couldn't create a
boot disk (using bzdisk) that could fit on a single floppy. (and in
fact make bzImage
gave me that warning as well).
Now I tried to choose the minimum of options, but it still ended up
overflowing the floppy disk. Why is this? The bzimage I created looks
to be 1 mb.
However, there are additional files
How are those files that are usually on a boot floppy created?
(initrd.img, etc) Do they reside as files somewhere?
Does mkbootdisk work for creating boot disks for custom kernels? I'm
used to typing
mkbootdisk --device /dev/fd0 2.4.2-2
but obviously for a new kernel it would be different. If this command
is appropriate here, what switches or options would you use. What does
the kernel number in the command above do? Where does the "2.4.2-2"
tell mkbootdisk to look? If I named my boot bzimage "kernel.good" ,
would that be the appropriate value to insert here?
Finally, I'm wondering if a boot floppy for a custom kernel is really
necessary. If I have the boot floppy for the distribution's kernel and
I don't erase that kernel, why would a person need a special floppy
for a particular kernel? Thoughts?
Robert Nagle, Austin, Texas