[OpenAFS] Knfs doesn't work on an AFS/NFS translator under OpenAFS

[Renata Maria Dart]

Hi,  we do still have AFS for the NeXT, but somewhere along the
line it started behaving in a very flaky way (I don't have the
details on this anymore) and since it was no longer a supported 
platform at Transarc, there was no recourse.  NeXT users decided
it was more reliable to go with the translator. 

Thanks for all of your inputs, and thanks to the OpenAFS guys for
opening a bug report on this issue.

-Renata

>Date: Tue, 20 May 2003 17:10:53 -0700
>From: Russ Allbery <rra@stanford.edu>
>Subject: Re: [OpenAFS] Knfs doesn't work on an AFS/NFS translator under OpenAFS
>To: Derek Atkins <warlord@MIT.EDU>
>Cc: Renata Maria Dart <renata@SLAC.Stanford.EDU>, openafs-info@openafs.org
>MIME-version: 1.0
>Content-transfer-encoding: 7BIT
>User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Portable Code, 
sparc-sun-solaris2.6)
>
>Derek Atkins <warlord@MIT.EDU> writes:
>> Renata Maria Dart <renata@SLAC.Stanford.EDU> writes:
>
>>> We also have a handful of ancient NeXTs which use it (I know, I'm not
>>> likely to get much sympathy there).
>
>> Ok, so "legacy"..  Well, tell your NeXT users to get machines that are
>> less than 10 years old....  ;)
>
>Don't you have AFS for NeXT?  When we had NeXT systems in the main campus,
>we just ran AFS on them natively.
>
>-- 
>Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

 Renata Dart                         | renata@SLAC.Stanford.edu  
 Stanford Linear Accelerator Center  |    
 2575 Sand Hill Road, MS 97          | (650) 926-2848 (office)
 Stanford, California   94025        | (650) 926-3329 (fax)