From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon, 24 Feb 2003 12:18:49 -0500
From: William Josephson <jkw@eecs.harvard.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] (no subject)
Message-ID: <20030224171849.GB37539@mero.morphisms.net>
References: <3ac8898cbd443116eeeb152a9d5ac1e6@snellwilcox.com> <20030224100637.A1582@broadq.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030224100637.A1582@broadq.com>
User-Agent: Mutt/1.4i
Topicbox-Message-UUID: 7090c3a8-eacb-11e9-9e20-41e7f4b1d025

On Mon, Feb 24, 2003 at 10:06:37AM -0600, Wayne Walker wrote:
> If you plan on wirting a "unix-ish" file system, I think the SysV /
> Coherent  fs was fairly simple (as simple as inode/superblock/indirect
> block fs's go).  I've not looked at the actual linux or *BSD code for
> that, though.

If you're actually looking for an on-disk filesystem,
kfs or FreeBSD's FFS are probably good places to start.
I have read-only FFS+buffer cache for plan 9 lying
around here somewhere which I suppose I should finish;
it already serves its purpose for doing physical backup
a la Russ's "trimfat" for FAT filesystems, though.

But I suspect you are looking for a Plan 9 filesystem, so
something like ramfs, webfs, or nntpfs might be better
places to start.  Lib9p is also worth poking at, IMO.