Oh, you did! Thanks a lot.
BTW, want to express my greatest thanks to you for your nice job with grub2
)
I'm utterly satisfied that now it can do EVERYTHING:
1) it can boot FreeBSD kernel directly rather than via
/boot/zfsloader.
2) it can boot it from a ZFS filesystem.
3) it can do all the above with grub2 config files themselves residing on that same ZFS filesystem.
I"m saying all this because the Linux grub2 I used last wasn't able to boot the kernel directly, but would choke and reboot. Which compels to use
/boot/zfsloader, which is not nearly as good an option...
For all the above to be possible there's one requirement, though: the
bios-boot partition MUST be big enough to embed all the needed
grub2 data. At least, when I converted the existing
freebsd-boot size
64K partition to be used by grub2, it proved not big enough and the resulting bootloader escaped to rescue prompt, from which it is impossible to boot a ZFS-based system. So I made my
bios-boot partition
20M large and now it works perfectly well. I remember this recommendation since my Linux experiences with grub2.
If somebody wants to know how to create the needed
bios-boot partition:
Code:
#gpart add -t \!21686148-6449-6E6F-744E-656564454649 -s <size> -i <index> <geom>
AFAIK it need not be exactly at the beginning of your GPT disk -- which is the beauty of GPT. It doesn't need MBR/PMBR if you're using grub2 as your boot-loader.
Spent quite some time testing these things, so it'll be good for other people to know. Because grub2 is the best bootloader I know of to be used for multiboot systems (except if one's using Oracle Solaris, in which case Solaris' own grub2 version will have to be used).
So, thank you again for your great job!!!!