A machine that uses an LS-120 SuperFloppy as its only floppy drive encounters a problem writing a boot disk as anaconda is hardcoded to use /dev/fd0 in that part of the script. Since the LS-120 is an ATA drive it is mounted via the /dev/hdX devices. For the unprepared this is interpreted as a freeze when in actuality it is just a VERY long pause until the file system creation fails out and the user can select "Skip ..." Obviously, this is not a good thing as without a boot floppy, an unsuccessful install/upgrade will leave a machine in a ... shall we say, interesting state.
Please verify Brock.
Suggestion: If an LS-120 drive is detected and no floppy drive is detected, the user should be prompted to insert a >1.44MB floppy< for bootdisk (NOT LS-120 disk), and LILO is put on with the proper BIOS and CHS parameters (disk=/dev/hda\n bios=0x80\n cylinders=...\n heads=...\n sectors=...). BTW: I once put an old distro (6.1, I think) an an LS-120 disk by itself. Freaky, huh?
reassigning these to dale for further review ...
I have verified that if your only floppy is a LS-120 you are not able to create a bootdisk.
I can't make a boot floppy work in our ls120 at all. I've done: drive=/dev/hdd bios=0x00 heads=2 cylinders=80 sectors=18 I've tried w/ and w/o the geometry, w/ and w/o linear. In all cases, lilo stops after lil.
mkbootdisk 1.3 uses syslinux rather then lilo, and seems to work fine