Hello,
I appreciated the sentiments in this thread as I had problems with Mandrake 9.1 and the boot floppy routine; I could never get one to actually boot. I learned somewhere to put one of my useless "boot floppies" into the drive and as root enter "lilo -vb /dev/fd0" . This copies your presently working lilo.conf setup to the floppy and at least it will give you the lilo screen and boot from your hard drive in the event that you lose your lilo (say by installing windows updates on another partition
--and having MicroSoft wipe your master boot record and lilo).
May 18 2004--I am updating this post with a warning. When I originally posted above ,I was of the opinion that what I described above allowed me to boot either from the floppy or from the hard drive presuming my system was healthy and functioning. Since then, I have reason to believe that Linux wants to remember one boot sector only. So if one used a floppy as above to boot, one may subsequently find that a hard drive boot becomes not possible and to change back, one would have to use said floppy to boot into Linux and then change back to a hard drive boot by typing (as root):
" lilo -b /dev/hda"
which would then add the line "boot=/dev/hda" to the /etc/linux.conf file and on the next boot attempt you would be able to boot once again from the hard drive. I am sorry if this is confusing and am trying to report clearly my experience. Any guru input is of course welcomed.
May 18 2004 --additional update
OK. Since the last update (today), I have experimented further and before describing the fix that I have been seeking allow me to supply some context. I have just learned to use the download/update tools and have sucessfully did the official security updates for Mandrake 9.1 including the rather long (65 MB) KDEbase update. I believe that these just overwrite the allready installed version and do not add that much to your installation in terms of size. But, they may very well have improved the functiionality of some of the tools I have tried to use in the past, e.g., "format a floppy".
Having said that, I fomratted a floppy with no trouble this time (ext2) and then went to a console command line and as root entered:
"mkbootdisk --device /dev/fd0 2.4.21-0.11mdk"
(the last is the only required argument and is the version # of my kernel found in /boot)
and lo and behold, it actually created a standalone bootable floppy complete with an installer: Here are the files it creates on the floppy
boot.msg* initrd.img* ldlinux.sys* syslinux.cfg* vmlinuz
The installler is the ldlinux.sys and was missing from the installation prompted boot disk that I made and tried to use without results. The total size in bytes is 1.388832 Mbytes and by this one can see that if the kernel is much larger, the whole won't fit on a floppy unless some heroic measures are taken to create a larger capacity floppy.
So there it is as it works for me. I hope that the information posted here justifies the bandwidth used as far as helping some other newbie like me.
robertn[B]