[OpenAFS-devel] RE: OpenAFS: conventions for new @sys? (rs_aix43 s390_linux22)

[Broughton, Travis V]

This is something I've always wanted to see - something like a
user-extensible table of "@" macros.  I would like to be able to have an
"@cell" macro for organizations that have multiple cells with some amount of
uniformity among them (/afs/@cell/common/etc, for example).  Also, in some
cases an "@user" macro might be useful -- imagine how much simpler home
directory mappings might be (assuming, of course, a flat homedir structure
and not a heirarchical one like a lot of sites use) -- every new user could
be created with a home directory of /afs/@cell/homes/@user.  I can think of
a few others but these should suffice to demonstrate that this functionality
is not completely without merit.  Unfortunately this functionality would
only work within a specific set of OpenAFS cache managers -- you'd lose
interoperability with the previous generation's client, as well as with the
commercially-supported one.

-tvb

-----Original Message-----
From: owner-info-afs@transarc.com [mailto:owner-info-afs@transarc.com]On
Behalf Of Nathan Neulinger
Sent: Friday, November 03, 2000 6:58 PM
To: Russ Allbery
Cc: info-afs@transarc.com; openafs-devel@central.org
Subject: Re: OpenAFS: conventions for new @sys? (rs_aix43 s390_linux22)


Russ Allbery wrote:
> 
> Johan Danielsson <joda@pdc.kth.se> writes:
> > Russ Allbery <rra@stanford.edu> writes:
> 
> >> I *would* like to see @sys names chosen on more criteria than just what
> >> version of AFS client is associated with that system
> 
> > The problem with this is that it would require longer sysnames, and that
> > will more likely break the 32 (or 31, i can never remember) volume name
> > limit.
> 
> I don't see why.  Among the officially supported Transarc AFS clients, the
> only one that currently needs to be split for the purposes of most
> applications is rs_aix42 (into rs_aix42 and rs_aix43).
> 
> --
> Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

How bout a much more capable facility than @sys... Extend that concept
into what the old apollo workstations had - dynamic symlinks. Why not
make that part of AFS. i.e. support more than just @sys.

For example, alot of sites would probably find '@acsys' to be useful to
do the autoconf determined sys type. 

I dunno exactly, but it seems like making a more general purpose
mechanism would be very useful.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
CIS - Systems Programming                Fax: (573) 341-4216