From owner-freebsd-current@FreeBSD.ORG Tue Jun 28 13:38:11 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A6F91065675; Tue, 28 Jun 2011 13:38:11 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 962EC8FC14; Tue, 28 Jun 2011 13:38:10 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap0EACHZCU6DaFvO/2dsb2JhbABShEmjb7h7kTKBK4N5gQwEkhCQPQ X-IronPort-AV: E=Sophos;i="4.65,437,1304308800"; d="scan'208";a="129237045" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 28 Jun 2011 09:38:00 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 26AB1B3F20; Tue, 28 Jun 2011 09:38:00 -0400 (EDT) Date: Tue, 28 Jun 2011 09:38:00 -0400 (EDT) From: Rick Macklem To: Grzegorz Bernacki Message-ID: <40143899.5952.1309268280142.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4E0996AB.9000802@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Cc: rmacklem@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: NFS/BOOTP problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2011 13:38:11 -0000 Grzegorz Bernacki wrote: > Hi, > > After rebasing to new -current I experienced problem with mounting > root > via NFS. I was getting error: "Mounting from nfs: failed with error 2: > unknown file system.". I use BOOTP and NFSv3 (option NFSCLIENT). It > seems that bootp set fs type to 'nfs' and recently NFSv3 was renamed > to > 'oldnfs'. Patch below fixes the problem. Do you think it is proper > solution? Could it be fixed some other better way? > If you wish to use the old NFS client as the root fs, you can add a line like: vfs.root.mountfrom="oldnfs:" in the boot/loader.conf file on the root fs in the NFS server to have the same effect as your patch. (This is mentioned in the message in UPDATING.) However, it would be nice if you used the new NFS client instead, by building the kernel with "option NFSCL" so that it uses the new NFS client. (The new NFS client does NFSv3 in what I believe to be a completely compatible way as the old one.) If you tried the new NFS client and it didn't work for you, I would like to hear what the problem was, so it can be resolved. (The intent was to leave the old NFS client in the system so that it could be used as a fallback when the new one didn't work correctly for some situation.) If others feel that having a system that will boot via the old NFS client without needing to add the line to loader.conf is important, then doing your patch would be appropriate. I didn't do what your patch does, since I was hoping folks would use the new client instead and only force use of the old one when it was really necessary. rick [patch snipped for brevity]