From owner-freebsd-current Wed Dec 4 11:26:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA17228 for current-outgoing; Wed, 4 Dec 1996 11:26:41 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA17223 for ; Wed, 4 Dec 1996 11:26:39 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA11255; Wed, 4 Dec 1996 12:26:32 -0700 (MST) Date: Wed, 4 Dec 1996 12:26:32 -0700 (MST) Message-Id: <199612041926.MAA11255@rocky.mt.sri.com> From: Nate Williams To: Doug Rabson Cc: michael butler , current@freebsd.org Subject: Re: nfs v2 In-Reply-To: References: <199612041538.CAA01116@asstdc.scgt.oz.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Doug Rabson writes: > On Thu, 5 Dec 1996, michael butler wrote: > > > 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, > > Any chance of a kernel backtrace for the panic? FWIW, I just tried mounting a 2.1.6.1 FS onto a 2.2 box and have no problems. Unfortunately, I can't easiily mount a 2.1.6.1 FS from a -current machine since my -current box is also my 2.1.6.1 box (my laptop has two disks). Nate