On Wed, Sep 22, 2010 at 6:14 PM, Lennart Sorensen <lsore...@csclub.uwaterloo.ca> wrote:
> Wouldn't that be a bug in the BIOS? Don't go writing to a drive you > don't know what contains. It could be something other tahn fat16 after > all (what if it was a linux kernel with a bootheader on it and not a > filesystem at all?) > > Sounds like the BIOS needs fixing badly. Nothing wrong with making > grub more robust against corrupt filesystems, but it doesn't actually > fix the bug in the BIOS. Well, I think I didn't state the problem clearly enough: The bios doesn't write to the disk, it just changes the value on the fly when the bootloader is reading the bpb through a bios method. The workaroud also doesn't change the disk, it only reads the necessary information from a region the bios doesn't mess up on the fly... _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
