From owner-freebsd-hackers Thu Jul 29 13:12:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2FC2714F98 for ; Thu, 29 Jul 1999 13:12:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA78387; Thu, 29 Jul 1999 13:12:06 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 13:12:06 -0700 (PDT) From: Matthew Dillon Message-Id: <199907292012.NAA78387@apollo.backplane.com> To: Brian Reichert Cc: hackers@FreeBSD.ORG Subject: Re: state of NFSv3 under 3.2-RELEASE References: <19990729154043.K10828@numachi.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I've lost track of things: : :- are there a set of patches for 3.2-RELEASE that stabilize the NFS issues? : :- if not, should I drop back to 3.1-RELEASE, or grab a more current : snapshot? This is for a production environment. : :I appreciate the feedback... : :-- :Brian 'you Bastard' Reichert reichert@numachi.com :37 Crystal Ave. #303 Daytime number: (781) 899-7484 x704 Your best bet, if you are tracking the 3.x releases, is to stick to FreeBSD-stable (i.e. the latest 3.x tree). 3.1 is hopelessly broken. I would not even consider going back to it. There are items fixed in CURRENT that cannot be fixed in STABLE, mostly related to esoteric mmap() issues that you will probably never encounter, and heavy-use issues that you will also probably not encounter with a typical server installation. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message