From owner-freebsd-fs@FreeBSD.ORG Tue Nov 2 18:16:36 2010 Return-Path: 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 645781065670 for ; Tue, 2 Nov 2010 18:16:36 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B1D968FC1B for ; Tue, 2 Nov 2010 18:16:35 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA17406; Tue, 02 Nov 2010 20:16:30 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4CD0557D.1070901@icyb.net.ua> Date: Tue, 02 Nov 2010 20:16:29 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.11) Gecko/20101021 Lightning/1.0b2 Thunderbird/3.1.5 MIME-Version: 1.0 To: Chad David References: <4CD04E21.7010907@acns.ab.ca> In-Reply-To: <4CD04E21.7010907@acns.ab.ca> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: fs@freebsd.org Subject: Re: Skeleton Filesystem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2010 18:16:36 -0000 on 02/11/2010 19:45 Chad David said the following: > > 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. That sounds terribly useful for different uses, please share it! I myself took a shot at this although in much more primitive from [avgfs :-)]. Thanks! -- Andriy Gapon