[OpenAFS-devel] DRAFT: New sysname standard

[Derek Atkins]

No, it doesn't.  

First, @sys is purely a client issue, so there really isn't a
compatibility issue in the first place.  Second, this is only a
concern for _new ports_ for which transarc doesn't even have support
(otherwise it would already be in OpenAFS).

The only "interoperability" issue per-se would be that links using
@kern wont be accessible from non-openafs clients.

-derek

Ted McCabe <ted@MIT.EDU> writes:

> At 3:49 PM -0400 4/25/01, Derek Atkins wrote:
> >Considering that @sys is a client matter, and we're talking about new
> >client ports of OpenAFS...  Why can't we make other @foo variables
> >that solve the other problems?  Then we could have an @value for the
> >user-space and an @value for the kernel-space naming....  Then we
> >could use something like:
> 
> This ignores any concerns of inter-operability with Transarc's 
> clients, which is currently a significant issue.
> 
>     --Ted

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available