From owner-freebsd-current  Mon Sep 11 00:44:28 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id AAA12453
          for current-outgoing; Mon, 11 Sep 1995 00:44:28 -0700
Received: (from dyson@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id AAA12443
          ; Mon, 11 Sep 1995 00:44:27 -0700
From: John Dyson <dyson>
Message-Id: <199509110744.AAA12443@freefall.freebsd.org>
Subject: Re: Is nullfs broken in -current?
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Mon, 11 Sep 1995 00:44:26 -0700 (PDT)
Cc: current@freefall.FreeBSD.org
In-Reply-To: <199509110722.AAA01160@time.cdrom.com> from "Jordan K. Hubbard" at Sep 11, 95 00:22:14 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 827       
Sender: current-owner@FreeBSD.org
Precedence: bulk

> 
> I just attempted to use it to loop "/usr/src" and "/usr/obj" mounts on
> my system (^&*$@%!! broken make macros!) and every time I compile
> anything substantive from /usr/src I now get a divide by zero and
> panic.  I could go into more detail here and will if this isn't
> immediately reproducible by those interested in nullfs.  Last person
> I saw in that code was...  David?
> 
> 					Jordan
> 
All of the layered filesystem stuff is slated to be fixed for 2.2.  I am
too busy right now to even look at it right now because of that irritating
Sig-11 problem.   The VFS layering needs work (and even in the original
4.4Lite stuff was "not good".)  The getpage/putpage stuff is the first
step in the fixes.  (Other things include proper NFS locking -- right now
NFS doesn't VOP_LOCK at all!!!)

John
dyson@freebsd.org