From owner-freebsd-afs@FreeBSD.ORG  Sun Oct  3 17:51:54 2004
Return-Path: <owner-freebsd-afs@FreeBSD.ORG>
Delivered-To: freebsd-afs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 23B2C16A4CE
	for <freebsd-afs@freebsd.org>; Sun,  3 Oct 2004 17:51:54 +0000 (GMT)
Received: from s1.stradamotorsports.com (ip30.gte215.dsl-acs2.sea.iinet.com
	[209.20.215.30])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7080943D48
	for <freebsd-afs@freebsd.org>; Sun,  3 Oct 2004 17:51:53 +0000 (GMT)
	(envelope-from jcw@highperformance.net)
Received: from [192.168.1.16] ([192.168.1.16])i93Hpp8m039384;
	Sun, 3 Oct 2004 10:51:51 -0700 (PDT)
	(envelope-from jcw@highperformance.net)
Date: Sun, 03 Oct 2004 10:51:50 -0700
From: "Jason C. Wells" <jcw@highperformance.net>
To: port-freebsd@openafs.org, freebsd-afs@freebsd.org
Message-ID: <298988599E2F2A499C14658C@[192.168.1.16]>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Status: No, hits=0.0 required=4.0
	tests=none
	version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
Subject: Re-energizing FreeBSD Efforts
X-BeenThere: freebsd-afs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: The Andrew File System and FreeBSD <freebsd-afs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-afs>,
	<mailto:freebsd-afs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-afs>
List-Post: <mailto:freebsd-afs@freebsd.org>
List-Help: <mailto:freebsd-afs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-afs>,
	<mailto:freebsd-afs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Oct 2004 17:51:54 -0000

I was hoping that I could get the FreeBSD client working correctly.  It 
seems to be part way there, but certainly not ready for anything more than 
experimental use.

Is anyone out there willing to write code for the FreeBSD port of OpenAFS 
on the client side?

I certainly don't have the skill to get software working that results in a 
system hang with no error reporting at all.  I am willing to do lots of 
compiling, testing, and reporting.  If there is no one out there who 
understands the internals and will write code, then all I would be doing is 
populating the mailing list archives with unanswered messages.

If I can't generate some interest, I have heard that I can fall back on 
Arla.  I would prefer to get OpenAFS up to speed.

Thanks,
Jason C. Wells