From owner-freebsd-alpha  Thu Jun  8 11: 2:21 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 2DD1237B608
	for <alpha@FreeBSD.ORG>; Thu,  8 Jun 2000 11:02:14 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
	by feral.com (8.9.3/8.9.3) with ESMTP id LAA19568;
	Thu, 8 Jun 2000 11:02:10 -0700
Date: Thu, 8 Jun 2000 11:01:44 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: alpha@FreeBSD.ORG
Subject: Re: nullfs broken on alpha?
In-Reply-To: <14655.55017.616832.725282@grasshopper.cs.duke.edu>
Message-ID: <Pine.BSF.4.05.10006081101271.15951-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


Grump. I thought was from 1997. I guess nobody's been enterprising.


On Thu, 8 Jun 2000, Andrew Gallatin wrote:

> 
> Matthew Jacob writes:
>  > 
>  > I was building in a nullfs mounted on top of an NFS directory when this
>  > happened. Sigh, not much info to go on.... Anyone seen anything similar?
>  > 
>  > 
> 
> >From the i386 LINT:
> 
> # NB: The NULL, PORTAL, UMAP and UNION filesystems are known to be
> # buggy, and WILL panic your system if you attempt to do anything with
> # them.  They are included here as an incentive for some enterprising
> # soul to sit down and fix them.
> 
> 
> Drew
> 



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