From owner-freebsd-current  Wed Dec  4 07:40:37 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA16376
          for current-outgoing; Wed, 4 Dec 1996 07:40:37 -0800 (PST)
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA16328
          for <current@freebsd.org>; Wed, 4 Dec 1996 07:40:23 -0800 (PST)
Received: (from imb@localhost)
          by asstdc.scgt.oz.au (8.7.6/BSD4.4) id CAA01116
          Thu, 5 Dec 1996 02:38:49 +1100 (EST)
From: michael butler <imb@scgt.oz.au>
Message-Id: <199612041538.CAA01116@asstdc.scgt.oz.au>
Subject: Re: nfs v2
In-Reply-To: <Pine.BSF.3.95.961203161400.22942D-100000@minnow.render.com> from Doug Rabson at "Dec 3, 96 04:15:33 pm"
To: dfr@render.com (Doug Rabson)
Date: Thu, 5 Dec 1996 02:38:48 +1100 (EST)
Cc: current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Doug Rabson writes:

> > Is it possible to switch back to nfs-v2 in current ?
> > Have problems with v3 from DEC-alpha to Freebsd.
 
> I don't know how you would do it without hacking the kernel and/or mountd.
> Have a look at the options for mount on the DEC-alpha.
 
> What problems do you have with NFSv3 in current?  If I know what the
> problems are then I have a chance of fixing them.

As another data point .. with a December 4th kernel I cannot mount a 2.1.6.1
file-system and access it without a panic on the -current system. A kernel
from November 21st works just fine,

	michael