Hello, Ian!
> Grub will load release version 2.6, which was the latest release, but it
> will not boot latest current version of the kernel. BSD complains that the
> boot loader is too old.
I remember me fixing OpenBSD support in GRUB. It required a lot of time. I
had to install OpenBSD, learn its basics, download and compile the code. I
spent much time debugging the code. And now I'm told that the latest and
greatest version of OpenBSD doesn't work with GRUB. Now I see how
uneffective my efforts have been.
The same applies to FreeBSD. I almost expect similar problems with NetBSD
some day.
One of NetBSD guys told me that it's in his opinion not a good idea to
combine the bootloader and boot selector. I tend to agree provided that
the bootloaders _have_ to be OS-specific. But I don't think so.
The Multiboot protocol gives us the chance to avoid the nightmare of
having different bootloaders. Besides, every bootloader tends to be a poor
CLI boot selector in the same time.
In short you have 3 options:
1) Adopt the Multiboot protocol
2) Elaborate a patch for OpenBSD. It should be cleanly designed and should
maintain compatability with older version and other OS'es (notably
NetBSD) even if they refuse to put identifiers into their kernels.
3) Live in the world of separated bootloaders and bootselectors, where you
cannot choose between two kernels in a menu.
Regards,
Pavel Roskin
