From owner-freebsd-fs@FreeBSD.ORG Mon Oct 18 10:48:22 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7ADC16A4CE for ; Mon, 18 Oct 2004 10:48:22 +0000 (GMT) Received: from mail.eecs.harvard.edu (bowser.eecs.harvard.edu [140.247.60.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C7A443D41 for ; Mon, 18 Oct 2004 10:48:22 +0000 (GMT) (envelope-from ellard@eecs.harvard.edu) Received: from localhost (localhost.eecs.harvard.edu [127.0.0.1]) by mail.eecs.harvard.edu (Postfix) with ESMTP id B332254C690; Mon, 18 Oct 2004 06:48:21 -0400 (EDT) Received: from mail.eecs.harvard.edu ([127.0.0.1]) by localhost (bowser.eecs.harvard.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33178-10; Mon, 18 Oct 2004 06:48:21 -0400 (EDT) Received: by mail.eecs.harvard.edu (Postfix, from userid 465) id 81A2B54C6A4; Mon, 18 Oct 2004 06:48:21 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.eecs.harvard.edu (Postfix) with ESMTP id 7F14854C6A3; Mon, 18 Oct 2004 06:48:21 -0400 (EDT) Date: Mon, 18 Oct 2004 06:48:21 -0400 (EDT) From: Daniel Ellard To: Daniel Gustafsson In-Reply-To: <200410180814.i9I8ET70015904@space.se> Message-ID: <20041018064004.U32814@bowser.eecs.harvard.edu> References: <200410180814.i9I8ET70015904@space.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at eecs.harvard.edu cc: freebsd-fs@freebsd.org Subject: Re: Extracting FFS from FreeBSD X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 10:48:23 -0000 On Mon, 18 Oct 2004, Daniel Gustafsson wrote: > I am working in a project which is in need of a stand-alone file system and > I am interested in extracting FFS from BSD and modyfi it to a stand-alone > module. I have some questions before I begin: I also have some questions before you begin :-) They all follow from your last question. Do you really need FFS or will something simpler do the job? What functionality do you need to support? (Has anyone done this before?) My suspicion is that if all you need is a simple user-level file system, then you can find something already written that will do most or all of what you want -- unless you need something special. If you can't find anything, it's probably faster to write a simplistic file system on your own than to dis-tangle FFS from the rest of the kernel. -Dan