>
>We (ir.stanford.edu) are thinking about changing the way we layout
>home directories in AFS and would like to get some feedback on what
>methods other people are using. Since most of our users are still in NFS
>(due mainly to political reasons) we had a simple scheme of:
We (iastate.edu) have both AFS and NFS. For AFS, we use
/afs/isu/users/[0-31]/[0-31]/[username]
That is for users' lockers. We have other lockers for softwares,
rental, ... etc. We use DECAthena's attach scheme to create all the
necessary links as needed so that we don't need to mung the password
file. Of course, we also use hesiod, kerberos, and moira for
authentication and informations on those lockers.
>
>Other options I've thought of include hashing on the uid, doing some sort
>of modulo arithmetic on the uid, or treating the uid as a hex number and
>using them to create the subdirectories. The problem with this method is
>if your UID changes then so does your directory name (unless you have some
>huge directory full of symlinks which defeats the whole purpose if you use
>this directory in a password file). These approaches also make it harder
>to find someone's home directory (although ~user works fine if you have
>the full password file on your system).
>
>We could eventually have about 20,000 directories in AFS/DFS if we migrate
>all our users into AFS.
>
>For now I'm going to write a perl script to mung through the password file
>and try various algorithms to see which one seems like the best.
>
>thanks, Roland
>
_____
Phi H. Truong "Hmmmmmmmmm....... "
[EMAIL PROTECTED] ISU Computation Center
Systems Analyst 237 Durham Center ph: (515) 294 - 1420
