From owner-freebsd-stable Fri Apr 23 19:50:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7A4DC14D68 for ; Fri, 23 Apr 1999 19:50:20 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id TAA45824; Fri, 23 Apr 1999 19:47:45 -0700 (PDT) (envelope-from obrien) Message-ID: <19990423194745.A42940@nuxi.com> Date: Fri, 23 Apr 1999 19:47:45 -0700 From: "David O'Brien" To: Gerald Pfeifer , stable@FreeBSD.ORG Subject: Re: NFSv3 seriously broken in 3.1 Reply-To: obrien@NUXI.com References: <19990423084016.B36610@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Gerald Pfeifer on Fri, Apr 23, 1999 at 10:34:23PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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! Can you describe the breakage? You weren't specifying "nfsv2" in the maps you were using in 2.2.7? If the list truly feels that v2/UDP should be the default rather than v3/UDP, I'll glady change it for -STABLE (but not -CURRENT). I want 3.2 to be the most stable OS we can muster up. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message