From owner-freebsd-fs@FreeBSD.ORG  Tue Jan  6 13:35:56 2004
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 B6F6B16A4CE
	for <freebsd-fs@freebsd.org>; Tue,  6 Jan 2004 13:35:56 -0800 (PST)
Received: from citi.umich.edu (citi.umich.edu [141.211.133.111])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8288743D46
	for <freebsd-fs@freebsd.org>; Tue,  6 Jan 2004 13:35:55 -0800 (PST)
	(envelope-from rees@citi.umich.edu)
Received: from citi.umich.edu (dumaguete.citi.umich.edu [141.211.133.51])
	by citi.umich.edu (Postfix) with ESMTP
	id 8F0572091E; Tue,  6 Jan 2004 16:35:54 -0500 (EST)
To: Tillman Hodgson <tillman@seekingfire.com>
From: Jim Rees <rees@umich.edu>
In-Reply-To: Tillman Hodgson, Tue, 06 Jan 2004 15:13:36 CST
Date: Tue, 06 Jan 2004 16:35:54 -0500
Sender: rees@citi.umich.edu
Message-Id: <20040106213554.8F0572091E@citi.umich.edu>
cc: freebsd-fs@freebsd.org
Subject: Re: Request: summary of NFSv4 status available anywhere? 
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
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, 06 Jan 2004 21:35:56 -0000

I'm sorry we haven't been better about sharing our plans.

We have no current plans to do a server.  Sorry.

We are holding back new code pending the release of FreeBSD 5.2, which will
be the first to incorporate our client.  After that we'll be working on gss,
and hope to test a client with kerberos and maybe lipkey at Connectathon in
late Feb.  Look for it to show up in the FreeBSD source tree shortly after
that.

Right now I'm working on some small cleanups.  I want to have the v3 and v4
clients both use the same rpc, so that v3 will get the benefits of rpcsec.
I want to fix the layering violations and backward references that currently
make it impossible to have completely separate v3 and v4 client modules.

There is still plenty of work to do before the client is fully functional.
You can use it, but as it is now you don't get many of the benefits of v4.
That will come later.