В Sun, 26 Oct 2014 21:19:38 +0200
Beeblebrox <[email protected]> пишет:
>
> > > * First is, code snippet to get mount_root to use NFS V3 instead of
> > > V2. grub.cfg code should be as below, but does not work
>
> > This should be kFreeBSD....
> Still does not work with
> {set kFreeBSD.boot.nfsroot.options="nfsv3"}
> mount_root this time does not hang, but resulting mounted root is still V2
>
> * grub.cfg does not accept kFreeBSD for all parameters, and needs mixed
> syntax. Example:
> menuentry 'FreeBSD 11_amd64' {
> kfreebsd kernel/kernel
> # NOT kFreeBSD kernel/kernel
kfreebsd is not parameter, it is command. kFreeBSD. is variable name
prefix.
> set FreeBSD.acpi_load=YES
> kfreebsd_loadenv device.hints
> # NOT kFreeBSD_loadenv device.hints
> kfreebsd_module kernel/if_sis.ko
> # NOT kFreeBSD_module kernel/if_sis.ko
>
> * I disabled these 3 params:
> # set kFreeBSD.vfs.root.mountfrom="nfs:192.168.2.1:/data/amd64"
> # set kFreeBSD.vfs.root.mountfrom.options="ro"
> # set kFreeBSD.boot.nfsroot.options="nfsv3"
> And saw that FreeBSD boots normally through grub. This means that the {set
> kFreeBSD.*} settings are very likely being ignored as boot settings.
It is possible to verify that those variables are actually passed from
grub to kernel?
> The mount_root is successful because FreeBSD executes what is passed
from dhcp.
>
> Regards.
_______________________________________________
Grub-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/grub-devel
