From owner-freebsd-hackers Thu Oct 17 22:23:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA25648 for hackers-outgoing; Thu, 17 Oct 1996 22:23:55 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA25641 for ; Thu, 17 Oct 1996 22:23:52 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id FAA01100; Fri, 18 Oct 1996 05:23:45 GMT Date: Fri, 18 Oct 1996 14:23:45 +0900 (JST) From: Michael Hancock To: Kent Vander Velden cc: hackers@FreeBSD.org Subject: Re: new filesystem In-Reply-To: <9610180215.AA12203@spiff.cc.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 17 Oct 1996, Kent Vander Velden wrote: > "The Design and Implementation of the 4.4 BSD OS" talks about using > the nullfs as a starting place for a new filesystem or a layer but I am > not completely certain that this is the best choice in this case. > Perhaps the extra information could be handled at the vnode level > instead of the inode level... You should read ftp://ftp.cs.ucla.edu/pub/ficus/ucla_csd_910056.ps. This is the design that 4.4BSD is based upon. If the link is wrong look around for John Heidemann's paper on stackable vnodes. Regards, Mike Hancock