From owner-freebsd-net@FreeBSD.ORG Mon Feb 16 09:30:03 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9AB68D67 for ; Mon, 16 Feb 2015 09:30:03 +0000 (UTC) Received: from mail-la0-f42.google.com (mail-la0-f42.google.com [209.85.215.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1CF3CA2B for ; Mon, 16 Feb 2015 09:30:02 +0000 (UTC) Received: by labgd6 with SMTP id gd6so27189653lab.7 for ; Mon, 16 Feb 2015 01:29:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berentweb.com; s=google; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=XxwqgNGoj6EJ5IbCQLy9yRpnuPzqIHSRPniApccy4nc=; b=CLXk0Ybh3WYrpgJ7Lv4w4cYrFSGfFZaaDSNCT9gcmxmLvzpwBYLdOAEMvbg7KpRTmM G8MpzJ6Tplfejkm+0Kr6N4swwgMfAmMT68xEYgNYF01BmWoo9s2ZrLt0cEz1DEe8Z8Ey BoglU6Dj52gEqutIw8RxJY66VvmgwecBx3V98= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=XxwqgNGoj6EJ5IbCQLy9yRpnuPzqIHSRPniApccy4nc=; b=gwAxxMGPG9s2zVsFIxTz0RPEcKy8mPk3TmKoWnqgTw6YgDhgPclFokISCSbdtNlGyl Y6Ldi5OnG3ItxucFJEHd41ypVRp4mLgSRaFof2Gniw14NN+DozhU04z0EYk6OnCdLiMe cjEqiiE9l5OUUQt3t2bwC4ZSjqy7TGTr1Q1J43S5i0Lnf5k0mVZpszoScbVQcXbel5Fh d0+OtcnjALW8szsXHtZ/xDd6iF4N123RTaspmYqE7ocMmu763o3vMaflcY2vtgxk03mh 4tvwGd2W2I2glRBr7/HrBDRiNm5g3Rq4zbuGGnPsvD0YLZPVFO5A9iVDkUd/siM2fKrb PRHQ== X-Gm-Message-State: ALoCoQksYe8a8RiYf3e+Ln35lE7qm8zuiIDY/cf6DIOkf2KSEkJNnmeZkEImCU5ivdc/qOzsExqw X-Received: by 10.152.10.98 with SMTP id h2mr14072480lab.18.1424078995076; Mon, 16 Feb 2015 01:29:55 -0800 (PST) Received: from rsbsd.rsb ([31.200.16.157]) by mx.google.com with ESMTPSA id ud4sm1181854lac.28.2015.02.16.01.29.53 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Feb 2015 01:29:54 -0800 (PST) Date: Mon, 16 Feb 2015 11:29:51 +0200 From: Beeblebrox To: Rick Macklem 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> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2015 09:30:03 -0000 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 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.