Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Feb 2015 11:29:51 +0200
From:      Beeblebrox <zaphod@berentweb.com>
To:        Rick Macklem <rmacklem@uoguelph.ca>
Cc:        freebsd-net@freebsd.org
Subject:   Re: NFS and diskless: some questions re nfs_diskless.c
Message-ID:  <20150216112951.0b4ff5cd@rsbsd.rsb>
In-Reply-To: <424747461.3929611.1424048192500.JavaMail.root@uoguelph.ca>
References:  <20150215174056.34912959@rsbsd.rsb> <424747461.3929611.1424048192500.JavaMail.root@uoguelph.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi again, Rick.

> If you are using a pxeboot built with this code, I don't know why you
> would still get NFSv2 instead of NFSv3. (Check the line for "/" in
> the diskless root's /etc/fstab <and> try adding the "nfsv3" option.

* I added nfsv3 to the client fstab as advised, but get same result (V2). T=
ested separately with Grub AND FreeBSD's pxeboot file.

* The probable reason is that my kernel has everything thrown in, but not B=
OOTP_NFSV3:
{ NFSCL, NFS_ROOT, KRPC, BOOTP, BOOTP_NFSROOT } (NFSD NFSLOCKD get loaded a=
s modules). This is based on a prior discussion on the lists, one which in =
retrospect I seem to have mis-understood (http://freebsd.1045724.n5.nabble.=
com/PXE-boot-using-Grub-bootloader-fails-at-mountroot-no-PXE-devs-td5924518=
.html#a5925420)

In that discussion, while trying to use Grub as my pxeboot, I thought the s=
olution was "build your kernel with BOOTP, BOOTP_NFSROOT"; whereas the more=
 elegant solution was perhaps to find a way to "fill in the structure nfsv3=
_diskless" in grub.cfg or elsewhere. So I think I'll try to fix this by you=
r suggestion of:
> I think if you build a kernel with "options NFS_ROOT" (but not the
> others), a boot loader can fill in the environment variables and have
> them used, just like pxeboot does.

Unless, above solution conflicts with my other objective, which is to "over=
ride the root fs"
> you can set this environment variable (look at bootpc_init()
> if you are using the BOOTP + BOOTP_NFSROOT
You mean using vfs.root.mountfrom I assume? But please clarify: Do you mean=
 I can "override the root fs" if only I'm using BOOTP and not when using NF=
S_ROOT?

Thanks and Regards.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150216112951.0b4ff5cd>