From owner-freebsd-fs@FreeBSD.ORG  Tue Nov  2 18:00:41 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E90EC106566C
	for <fs@freebsd.org>; Tue,  2 Nov 2010 18:00:41 +0000 (UTC)
	(envelope-from davidc@acns.ab.ca)
Received: from mail.acns.ab.ca (mail.acns.ab.ca [204.191.24.183])
	by mx1.freebsd.org (Postfix) with ESMTP id C96338FC1C
	for <fs@freebsd.org>; Tue,  2 Nov 2010 18:00:41 +0000 (UTC)
Received: from [192.168.2.108] (dhcp8.acns.ab.ca [192.168.2.108])
	by r2.acns.ab.ca (Postfix) with ESMTPA id 9AEA533CF5
	for <fs@freebsd.org>; Tue,  2 Nov 2010 11:45:16 -0600 (MDT)
Message-ID: <4CD04E21.7010907@acns.ab.ca>
Date: Tue, 02 Nov 2010 11:45:05 -0600
From: Chad David <davidc@acns.ab.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US;
	rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: fs@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Skeleton Filesystem
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2010 18:00:42 -0000


I'm porting our filesystem from Solaris to FreeBSD, and part of that 
effort is getting back into FreeBSD and getting familiar with VFS.

I've been writing a simple module that focuses on the VFS interfaces 
themselves, and not the underlying fileystem implementation in the hope 
of ending up with a concise but complete skeleton that can be used as a 
reference, and potentially a learning tool.

I have permission from my current employer to release this code, and am 
wondering if there is any interest from others?  If there isn't, I'll 
just focus on my port any leave you guys alone. If there is, I can make 
the code available and spend more effort on documenting the flow and logic.

What I'm hoping for is feedback from people (who are maybe not experts 
already) on what is clear and what is not.  If the code is straight 
forward, it should be useful as a starting point for others, or even 
just as a reference for the curious.

Anyway, if you are interested feel free to contact me, and I'd be happy 
to make the code available.


Thanks.

Chad