On Sun, 2008-01-27 at 09:53 +0100, Robert Millan wrote: > I just committed a check in grub-probe that attempts to read and verify files > using GRUB filesystems and compares them with output from your system. E.g. > if you do: grub-probe -t fs /full/path/to/file it will compare and verify it > using fs/ufs.c.
A few problems. grub-mkdevicemap generates an incomplete file containing only a very long list of (hd0), (hd1) ... (hd35) with no matching device names. I edited the file by hand to this: (hd0) /dev/ad0 (hd1) /dev/ad1 # grub-probe / grub-probe: error: cannot find a device for /. # grub-probe -t fs /kernel grub-probe: error: cannot find a device for /kernel. It seems that grub2 doesn't detect the existing devices including (fd0) on a *BSD system, though it works great on linux. Oh, and I have a FAT32 fs mounted on /c and grub-probe still gives me the same error, so it seems device related rather than fs related. I still have some ideas to try on the different BSD's to see if they all act the same. BTW, gcc on NetBSD *does* support -fstack-protector :o/ _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel