On Thu, Aug 21, 2014 at 9:20 AM, Joel Rees <joel.r...@gmail.com> wrote:
> [...]
> I'd show you how I chained openbsd, but the partition in question is
> not mounted and I'm not logged in on an admin group user right now.
This is for booting openbsd from the grub installed by debian Linux. I
don't know how applicable it will be to kFreebsd.
>From /etc/grub.d/40_custom on the first drive in my box,
--------------------------------------------------
menuentry "chain openbsd on 0" {
set root=(hd0,3)
chainloader +1
}
--------------------------------------------------
The top line is just the label for the grub boot menu. Make it
something you understand.
The second line is telling grub that the drive it is going to find the
boot-up code on is partition 3 (3rd BIOS level partition on drive 0
(first drive in the boot order).
The third line is the chain command, to pass the boot off to the boot
record in partition 3. "+1" means read it from block 1 on the
partition.
The grub manual entries promise information they don't give, so you
have to find the docs by searching the web for things like "grub
chain" and hoping what you find is up-to-date and meaningful. You'll
want to be careful not to confuse docs for version 1 with docs for
version 2, as well.
And it occurs to me now that you may have better success ignoring this
and letting kFreebsd install the grub for booting. But then you'll
probably have to boot kFreebsd to update grub when any Linux kernel is
updated.
(BTW, chaining didn't work for me as recently as six months ago, IIRC.)
--
Joel Rees
Be careful where you see conspiracy.
Look first in your own heart.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/CAAr43iPUCtk7rvcgpnOEZGuJZ=bejj06ule1rkpbakbffmg...@mail.gmail.com
