From owner-freebsd-afs@FreeBSD.ORG Mon Jan 21 10:42:05 2008 Return-Path: Delivered-To: freebsd-afs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F73916A417 for ; Mon, 21 Jan 2008 10:42:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6870913C45A for ; Mon, 21 Jan 2008 10:42:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E151846DFA; Mon, 21 Jan 2008 05:42:04 -0500 (EST) Date: Mon, 21 Jan 2008 10:42:04 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" In-Reply-To: Message-ID: <20080121103924.H73025@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-afs@freebsd.org, jcw@highperformance.net Subject: Re: AFS in FreeBSD ... X-BeenThere: freebsd-afs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: The Andrew File System and FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2008 10:42:05 -0000 On Mon, 21 Jan 2008, Marc G. Fournier wrote: > As Robert has stated in the thread I started last week, he's willing to lend > a hand with getting the kenrel module *as part of* the kernel, but what does > it take to get it to that point? > > I just downloaded Jason's initial port attempt, but it is almost a year old: > > > > Has anyone looked at the work he's done so far? Ignoring the client side > for now, Jason, what would it take to get your work to the point where > Robert could inject it into the core FreeBSD system, as opposed to an 'add > on'? What would be involved in getting 1.5.x working? I'm not sure there's a benefit to importing the OpenAFS server into the FreeBSD src tree, given that it's already well-maintained and fairly functional as a port. The main area of potential benefit is, in fact, the Arla client, which would then be able to track FreeBSD VFS changes, and offers a relatively static interface to the userland components that could continue to live in the port. After chatting with a few of the OpenAFS folks, the current concensus is that the OpenAFS client kernel parts are a lot more involved than the Arla ones, as much of the cache manager is implemented there, whereas with Arla it's just a user file system interface and so a lot less complex. So I think the short-term plan, if the Arla folks are willing and we can get a functional Arla module sync'd to 8-CURRENT, would be to get nnpfs into FreeBSD's src/sys. Robert N M Watson Computer Laboratory University of Cambridge