From owner-freebsd-alpha  Tue Jul 27 12:50:53 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 7EF1014DD6
	for <alpha@FreeBSD.ORG>; Tue, 27 Jul 1999 12:50:47 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
	by feral.com (8.8.7/8.8.7) with ESMTP id MAA23444;
	Tue, 27 Jul 1999 12:50:35 -0700
Date: Tue, 27 Jul 1999 12:50:28 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Mike Smith <mike@smith.net.au>
Cc: alpha@FreeBSD.ORG
Subject: Re: NFS broken on Noname 
In-Reply-To: <199907271940.MAA00719@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9907271249330.31508-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


> > > 
> > 
> > And just NFS stopped working... that's very strange indeed.... Well, I'll
> > if I can't dust off the UDB...
> 
> The box was running 3.2, on which NFS works fine.  I upgraded to a snap 
> from the 5th of this month, as which time it stopped.  I can't be a lot 
> more precise than that, I'm afraid, and playing binary-search with 
> kernels would be painful in the extreme.

How about a tigher definition of 'not working'? What symptoms? Is the rest
of network stuff fine? Did the rc files get upgraded correctly?




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message