From owner-freebsd-current Thu Apr 22 3:41:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 5854A150B8 for ; Thu, 22 Apr 1999 03:41:07 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id GAA08883; Thu, 22 Apr 1999 06:37:54 -0400 (EDT) Date: Thu, 22 Apr 1999 06:37:54 -0400 (EDT) From: Daniel Eischen Message-Id: <199904221037.GAA08883@pcnet1.pcnet.com> To: andyf@speednet.com.au, mike@sentex.net Subject: Re: solid NFS patch #6 avail for -current - need testers files) Cc: current@FreeBSD.ORG, dillon@apollo.backplane.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is the only thing stopping me from upgrading our production machines > to 3.1-STABLE. > > Please, please, please backport these fixes! I have to echo these feelings. NFS, as both server and client, is working without noticeable problems for us under the old 2.2-stable. I am afraid of upgrading to 3.1-stable with the reported NFS problems, and we can't get by without NFS. Some serious consideration should be given to fix the NFS problems in 3.1 - at least to make it more reliable. Perhaps there can be well announced unstable periods of -stable for things like merging non-trivial changes from -current? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message