From owner-freebsd-current Mon Jan 4 17:30:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08292 for freebsd-current-outgoing; Mon, 4 Jan 1999 17:30:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08271 for ; Mon, 4 Jan 1999 17:30:09 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id RAA09018 for ; Mon, 4 Jan 1999 17:25:35 -0800 (PST) Date: Mon, 4 Jan 1999 17:25:34 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: How's 3.0-current as an NFS client? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Back a few months ago, there was some concern about the stability/robustness of 3.x wrt NFS. I'm about to upgrade a box that for us is semi-mission-critical, to 3.0-current, since it's running an old 3.x just peachy, but wanted to make sure that there weren't any current NFS gotcha'sthat I've missed in the mailing lists. Thanks in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message