From owner-freebsd-hackers  Tue Jan 14 14:00:16 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id OAA10929
          for hackers-outgoing; Tue, 14 Jan 1997 14:00:16 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA10923
          for <hackers@FreeBSD.ORG>; Tue, 14 Jan 1997 14:00:14 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id NAA06796; Tue, 14 Jan 1997 13:59:49 -0800 (PST)
To: "Greg Rowe" <greg@uswest.net>
cc: hackers@FreeBSD.ORG
Subject: Re: 2.2 BETA Upgrade Problem 
In-reply-to: Your message of "Tue, 14 Jan 1997 09:43:31 CST."
             <9701140943.ZM17966@nevis.oss.uswest.net> 
Date: Tue, 14 Jan 1997 13:59:49 -0800
Message-ID: <6793.853279189@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> The problem seems to only exist (at least here) when the NFS mounted
> filesystem resides on a 2.1.5 or a 2.1.6 system. If the filesystem
> is on a 2.2 system, the Upgrade via NFS works perfectly. Jordan, I
> have systems I can test with if you need me to try anything.

Ye gods, what a mess.  The strange thing is, I mount 2.1.6 filesystems
from my 3.0 box all the time and it works great.  This is very puzzling!

					Jordan