From owner-freebsd-fs Wed Nov 3 17:18:47 1999 Delivered-To: freebsd-fs@freebsd.org Received: from login-2.eunet.no (login-2.eunet.no [193.71.71.239]) by hub.freebsd.org (Postfix) with ESMTP id 8441A14EF4 for ; Wed, 3 Nov 1999 17:18:39 -0800 (PST) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (mbendiks@login-1.eunet.no [193.71.71.238]) by login-2.eunet.no (8.9.3/8.9.3/GN) with ESMTP id CAA35867; Thu, 4 Nov 1999 02:18:32 +0100 (CET) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id CAA81477; Thu, 4 Nov 1999 02:18:31 +0100 (CET) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Thu, 4 Nov 1999 02:18:31 +0100 (CET) From: Marius Bendiksen To: Robert Watson Cc: freebsd-fs@FreeBSD.ORG Subject: Re: stupidfs - easily extensible test file systems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I believe V9fs covers this. --- Marius Bendiksen, ScanCall AS On Thu, 28 Oct 1999, Robert Watson wrote: > > I'm in the process of hacking up a stupidfs -- i.e., a minimal file system > module that provides simplistic (i.e., stupid) implementations of all the > relevant vnops and vfsops based on in-kernel memory. The purpose of > stupidfs is to allow file system extension developers (like myself) to be > able to add new vnops and implement them in a simple file system without > having to deal initially with the issue of permenant storage in the file > stores, distributed file systems, etc. It would be a poor-man's MFS > (although perhaps more useful than MFS because it doesn't have the weight > of UFS/FFS tangled up in it, which is what has stopped me from using MFS > to do the same kind of testing), with it only really being useful for this > testing purpose. > > However, as this will take a little bit to write, I thought I'd ask if > anyone else has done this already? :-) > > Right now I pretty much have it to the point where I can see the directory > structure, create files of up to 1k, etc, etc, but there's a fair amount > more to do before it's useful. Those people working on ACLs and MACs for > POSIX.1e have needed a test framework that doesn't involve seriously > hurting themselves on the sharp edges of FFS and MFS, but that still > allows them to actually see the results in a file system. Layering would > be another option [if only it worked]. And even with layering, there are > still complications in implementation -- more complicated, than saying > "gee, let's extend the inode to have *this* structure in it" and just > having it work as it backs to nothing and isn't tangled up in the idea of > backing to something (e.g., MFS). > > Robert N M Watson > > robert@fledge.watson.org http://www.watson.org/~robert/ > PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 > TIS Labs at Network Associates, Safeport Network Services > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message