I put the following in "40_custom" and then ran update-grub:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "freebsd" {
set root=(hd0,8)
chainloader +1
boot
}
On rebooting, I selected the 'freebsd' entry in the grub menu.
The result was the message "error: no loaded kernel".
Perhaps I have to specify the FreeBSD loader as a kernel, or address
the root partition more like the way one does it in legacy GRUB?
On Sat, Sep 26, 2009 at 10:33 AM, Slug71 <email address hidden> wrote:
> This will boot FreeBSD. Add to grub.cfg
>
> menuentry "freebsd" {
> set root=(hd0,x)
> chainloader +1
> boot
> }
>
> --
> FreeBSD not detected by os-prober
> https://bugs.launchpad.net/bugs/432254
> You received this bug notification because you are a direct subscriber
> of the bug.
>
I put the following in "40_custom" and then ran update-grub:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "freebsd" {
set root=(hd0,8)
chainloader +1
boot
}
On rebooting, I selected the 'freebsd' entry in the grub menu.
The result was the message "error: no loaded kernel".
My fstab entry for BSD's root partition is
##bsd partition(s)
## bsd: /dev/ad0s2a
/dev/sda8 /mnt/bsdroot ufs ro,ufstype=ufs2 0 0
and that works well.
Perhaps I have to specify the FreeBSD loader as a kernel, or address
the root partition more like the way one does it in legacy GRUB?
On Sat, Sep 26, 2009 at 10:33 AM, Slug71 <email address hidden> wrote: /bugs.launchpad .net/bugs/ 432254
> This will boot FreeBSD. Add to grub.cfg
>
> menuentry "freebsd" {
> set root=(hd0,x)
> chainloader +1
> boot
> }
>
> --
> FreeBSD not detected by os-prober
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>