Date: Wed, 7 May 2003 15:37:03 -0600 From: Tillman <tillman@seekingfire.com> To: freebsd-questions@freebsd.org Subject: Re: AFS Server and Client Message-ID: <20030507153703.A23403@seekingfire.com> In-Reply-To: <1052331668.6547.44.camel@jake>; from blueeskimo@gmx.net on Wed, May 07, 2003 at 02:21:08PM -0400 References: <Pine.BSF.4.44.0305061945510.30561-100000@server1.highperformance.net> <20030506222149.E19124@seekingfire.com> <1052331668.6547.44.camel@jake>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 07, 2003 at 02:21:08PM -0400, Adam wrote: > On Wed, 2003-05-07 at 00:21, Tillman wrote: > > Aside from features like volume management, failover, kerberos > > authentication, ease of client maintenance and intelligent client-side > > caching, you mean? ;-) > > > > I'd /love/ to see the OpenAFS server in the ports tree - the last > > messages on it that I've seen on various mailing lists seem to imply > > that it's Real Close Now. > > After reading up on AFS, I'd agree that there are many promising > features there. However, isn't NFS3 supposed to address some of these > shortcomings? You might be thinking about NFSv4 (v3 has been around for quite some time now). It'll definitely correct some of the problems in NFS (security and locking primarily), but like any NFS protocol it's aimed at workgroup sized networks. It'll also come at a cost: it's stateful, which is a change from traditional NFS. There's also an age difference: AFS has been around a long time, and so can be considered proven technology. Just not on FreeBSD :-) -T -- If any man thinks he slays, and if another thinks he is slain, neither knows the ways of truth. The Eternal in man cannot kill: the Eternal in man cannot die. Bhagavad Gita
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030507153703.A23403>