Page History

...

1. Make sure that you have a UNIX account because the directories in which you will be making files available to your collaborators will be in the UNIX AFS file system. Even if you normally work in Windows, you will need a UNIX account to access this space.
   • To obtain a UNIX account, fill out the account form and have it signed by your manager or group czar.
2. Decide which of three subdirectories is appropriate for storing your file(s):
   • /afs/slac/public/users for files related to an individual user
   • /afs/slac/public/groups for files related to a particular group
   • /afs/slac/public/software for files related to public software distributed from SLAC
3. You will need to have a subdirectory created that reflects your UNIX username, your groupname, or the name of the software unless such a subdirectory exists. If the subdirectory exists, you will have to have access privileges for this subdirectory; these can be provided by the group owner. Examples of existing subdirectories include:
   1. /afs/slac/public/users/bobcook
   2. /afs/slac/public/groups/bfactory
   3. /afs/slac/public/software/TkMail
4. If you need to have a subdirectory created, fill out an AFS space request. Specify which subdirectory (users, groups, or software), the name of the subdirectory you want to be created, and the amount of disk space you need if it is more than the default 5 MB.

   1. Note: If needed, you can add additional subdirectories under the subdirectory created by unix-admin. You will have all AFS file access privileges, except administrator privileges, for any subdirectories you choose to create. See the AFS Users' Guide for more information.

5. Copy or move your files to the appropriate subdirectory using the UNIX cp or mv commands, respectively. You may also use ftp to copy files to this space, but there is one special consideration. Your login will place you by default in your AFS home directory, and you must use the cd command to change to one of the public paths listed in point 3.
6. Notify the collaborator(s) of the name(s) and location of the file(s).

...

The subdirectory incoming has been reserved for collaborators who want to send files to SLAC users. For example, assume that Ann wants to transfer the file cheptalk.ps to SLAC user Bill.

1. Bill must have a UNIX account.
   • To obtain a UNIX account, he must fill out the account form and have it signed by his manager or group czar.
2. Ann can create a directory to contain her file and transfer her file to with these commands:
   ftp ftp.slac.stanford.edu
   Name: anonymous
   Password: ann@hep.physics.edu (the password will not display on screen)
   cd incoming
   mkdir bill
   binary (to prevent linend conversions which may damage some files.)
   put cheptalk.ps
   quit

    

3. Ann tells Bill that file cheptalk.ps is in subdirectory incoming/bill.

...