From owner-freebsd-current Fri Apr 18 09:56:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA17595 for current-outgoing; Fri, 18 Apr 1997 09:56:14 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA17560 for ; Fri, 18 Apr 1997 09:56:02 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id RAA01122; Fri, 18 Apr 1997 17:55:47 +0100 (BST) Date: Fri, 18 Apr 1997 17:55:47 +0100 (BST) From: Doug Rabson To: Nate Williams cc: current@freebsd.org Subject: Re: NFS comments In-Reply-To: <199704181640.KAA22251@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 18 Apr 1997, Nate Williams wrote: > > > I noticed Doug making some fixes in -current for some bugs, do any of > > > these also apply to 2.2.1. Also, I think I've figured out why I'm not > > > having any NFS problems on my 2.2.1 box. Does NFS default to V3 if I > > > use it in /etc/fstab file and the box supports it? My servers are > > > solaris 2.5.1 boxes, and I've not had *any* problems whatsoever beating > > > them up from FreeBSD clients. Does that ring any bells? > > > > Some of the kernel fixes are relavent to 2.2 and all the user fixes are > > relavent. I was planning to let them soak for a few days in current > > before updating the 2.2 branch. > > Great! > > > NFS will now default to V3 if not otherwise specified in /etc/fstab (with > > my latest change to mount_nfs). Before today, it would use V2 unless the > > nfsv3 option was present. > > So my NFS mounts to the Solaris boxes are using NFS V2 now then since my > box is running 2.2.1? Thats right. For 2.2.1, add 'nfsv3' to the options in /etc/fstab. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891