From owner-freebsd-stable Fri Apr 23 13:37: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 55D97154E2 for ; Fri, 23 Apr 1999 13:37:00 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from markab (markab [128.130.111.33]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id WAA11304; Fri, 23 Apr 1999 22:34:24 +0200 (MET DST) Date: Fri, 23 Apr 1999 22:34:23 +0200 (MET DST) From: Gerald Pfeifer To: stable@freebsd.org Cc: "David O'Brien" Subject: Re: NFSv3 seriously broken in 3.1 In-Reply-To: <19990423084016.B36610@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > but I was wrong. :-} David O'Brien has informed me that he added > recognition of "nfsv2" to am-utils in FreeBSD. Sorry for the > misinformation. Indeed I wanted to ``complain'', because I have been successfully using that option on 3.1. ;-) On Fri, 23 Apr 1999, David O'Brien wrote: > If you want to verify that the option is working for you, look for > > found compatiblity option "nfsv2": set options vers=2, proto=udp for host Yup, I found that. Why I brought this to stable and why think this is rather important is the following: We had a perfectly stable 2.2.7 system which worked fine with our Solaris 2.6 server for several months. Merely by upgrading to 3.1 and without changing the AMD configuration one bit, the setup broke! From the replies I received (also by private e-mail), I understand that NFSv3 is not considered ready yet. However, shouldn't it be *disabled* by default then for -stable resp. 3.x? Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message