<snip>
In fact, what it happens is that if the floppy is removed, it doesn't start, but it does if he uses the grub menu. On investigation, it seems that grub modifies (clears) the "active" or "bootable" flag from partitions (his normal boot disk is disk is /dev/hdh). That behavior seems to be controlled by the "makeactive" line in "/boot/grub/menu.lst".
Can that line be commented out safely? Is it proper for Yast to activate it, when the user requests "boot floppy", because he doesn't want to modify his normal boot sequence? Opinions?
Not sure about the boot floppy but on my system, I do not have that flag in my menu.lst. I'm sure that my partition setup is different and I do not use a bootfloppy. I thought that the M$ partition should be active and setup the PC to boot from a floppy in BIOS. Then the only info needed on the floppy is the info for the Linux partitions. That way when the PC boots, it will find the boot record on the floppy and try to boot from it, bypassing the bootstrap on the HDD. -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."