If you reboot without being connected to the network, AFS will not start.
To start it manually (after you are on the net) type:
sudo /Library/StartupItems/OpenAFS/OpenAFS
If you get an error that AFS can't open /Network/afs, then edit the file /var/db/openafs/etc/cacheinfo. Change '/Network/afs' to just '/afs' and restart afs manually.
The MIPP web pages are here:
/afs/fnal.gov/files/expwww/ppd/physical_experiments/e907/html
Your home directory is here:
/afs/fnal.gov/files/home/room?/user_name
where ? is 1, 2, or 3.
To have write access you need to authenticate EITHER with AFS or Kerberos.
Your AFS password is the same as the old unix password that you used for Fermilab before they forced you to get Kerberos.
If your username at Fermilab is not the same as your local username, then instead type klog your_fnl_user_name.
On MacOSX, you could also run the Kerberos application (open /System/Library/CoreServices/Kerberos.app). This does the same thing as kinit.
If your username at Fermilab is not the same as your local username, then instead type kinit your_fnl_user_name.
If you decide to use AFS authentication (instead of Kerberos), to change your AFS password do ONE of the following:
For MacOSX you can just type kpasswd. Note that this should execute /Library/OpenAFS/Tools/bin/kpasswd
Also note that the unix user (uid) and group (gid) id's of the remote AFS file system do not necessarily match those defined on your local system, so when you do a directory listing you will see numbers instead of user and group names. The authentication process (AFS or Kerberos) identifies you to the AFS system and let's you edit files in the AFS space.
The unix command id will display your uid and gid on the local machine.