From owner-freebsd-fs@FreeBSD.ORG Wed Oct 12 09:00:27 2005 Return-Path: X-Original-To: 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 D070616A420 for ; Wed, 12 Oct 2005 09:00:27 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45E5743D5D for ; Wed, 12 Oct 2005 09:00:21 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring [10.0.0.2]) by itchy.rabson.org (8.13.3/8.13.3) with ESMTP id j9C8xtkr037480; Wed, 12 Oct 2005 09:59:55 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-fs@freebsd.org, cel@citi.umich.edu Date: Wed, 12 Oct 2005 09:59:53 +0100 User-Agent: KMail/1.8.2 References: <4342F29D.1080302@citi.umich.edu> In-Reply-To: <4342F29D.1080302@citi.umich.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510120959.54281.dfr@nlsystems.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (itchy.rabson.org [80.177.232.242]); Wed, 12 Oct 2005 09:59:56 +0100 (BST) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on itchy.rabson.org X-Virus-Scanned: ClamAV 0.83/1128/Tue Oct 11 02:30:06 2005 on itchy.rabson.org X-Virus-Status: Clean Cc: Ivan Synyeokov Subject: Re: nfs4 on FreeBSD 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: Wed, 12 Oct 2005 09:00:28 -0000 On Tuesday 04 October 2005 22:22, Chuck Lever wrote: > Ivan Synyeokov wrote: > > Hi, > > I'm playing with nfs4 under FreeBSD and I wonder is there any > > particular plans to improve its support and have fully functional > > nfs4 client and server in base or maybe ports? > > > > I've found that Rick's (ftp://ftp.cis.uoguelph.ca/pub/nfsv4/) work > > is quite stable (I mean server part) on FreeBSD 6.0 Beta5, but > > client is only available for OpenBSD. Rick, do you plan to port > > your client to FreeBSD also? > > On the other hand, lack of delegation and locking state features > > from native FreeBSD6 client, prevent me from putting nfs4 in > > production. So, I kindly regard if anybody clear the situation, and > > in any case I could provide some testing. > > hi ivan- > > i'm beginning to look at the FreeBSD NFS client to think about how to > finish the nascent NFSv4 and RPCGSS implementation. it's a slow > start though. I have a working userland RPCSEC_GSS implementation which follows the Solaris api for gss-specific extensions to the RPC api (e.g. rpc_gcc_get_mechanisms(), rpc_gss_set_svc_name(), rpc_gss_getcred() etc.). I also have a working GSSAPI redirector which allows the use of multiple GSSAPI mechanisms, such as SPKEY which is required by the spec. It even includes an almost complete set of manpages culled from the RFC.