Here's our particular take on /afs/@cell (/afs/iastate.edu).

We have the standard @sys-forest nonsense (if I had it to do over
I'd probably put these 1 level down).  Then we have the following
other top levels (we borrowed MIT's "locker" nomenclature):

     academic   - lockers for courses
                  (e.g., /afs/iastate.edu/academic/design/arch403)
     common     - as per transarc
     group      - lockers for groups
                  (e.g., /afs/iastate.edu/group/careerserv)
     info       - lockers for the web server (smart move to name
                  this genericly instead of "gopher" way back when :)
     private    - we allow people to bring in their own disks and
                  attach them to certain of our AFS servers, they
                  all live below here)
     project    - lockers for projects we are working on internally
     public     - lockers of general public interest
                  (e.g., /afs/iastate.edu/public/tcltk)
     rental     - we allow people to rent space on our disks for
                  whatever reason they are willing to pay for,
                  those go here
     restore    - usually empty, if we need to restore a volume
                  for somebody it goes here for a while for them
                  to copy out what they need
     service    - as per transarc
     software   - the @sys forest again
     system     - in ye olden days when disks cost $10K/GB
                  most of our client machines AFS-mounted /usr
                  those /usr trees live down here
     users      - the great unwashed


The most likely place for religious arguments is how to do your
homedirs.  We put ours as:

      /afs/iastate.edu/users/NN/MM/username

where MM and NN are the low 5 bits, and the next 5 bits of the UID
which gives us roughly 32 entries at each directory level.
For example:

# hesinfo janeane passwd
janeane:*:5755:101:,,,,:/home/janeane:/bin/tcsh

# hesinfo janeane filsys
AFS /afs/iastate.edu/users/19/27/janeane w /home/janeane

                  users
                 /     \
               00..19..31
                  /  \
                 /    \
               00..27..31
                  /| \
                 / |  \
                   |
                janeane

We used to have a dir of symlinks:

    /afs/iastate.edu/usr/<username>

but when you have 40,000 of those everytime anybody used one
the system fell to its knees, so it's gone.

As you may have noticed/wondered above we use the HESIOD naming
system (an extenstion of DNS) so we don't have to resort to
stuff like:
   /afs/iastate.edu/user/j/a/janeane
which would be non-optimal (we we investigated our choices
we found the idstribution very much skewed -- lost of empty
2-letter combos, while others like /m/a/ and /j/o/ had
many hundreds in them.

Our users can just say:

    cd ~janeane

and "magic happens" courtesy of Hesiod.

John
-- 
John Hascall                         (__)   Shut up, be happy.
Software Engineer,            ,------(oo)    The conveniences you demanded
Acropolis Project Manager,   / |Moo U|\/      are now mandatory.
ISU Computation Center      *  ||----||        -- Jello Biafra

Reply via email to