Changes between Initial Version and Version 1 of Lockers

02/23/12 11:18:29 (9 years ago)



  • Lockers

    v1 v1  
     1Athena imposes a filesystem-independent layer of indirection on file 
     2storage called "lockers".  Because most Athena lockers currently live 
     3in AFS, lockers may seem a little inconvenient and pointless, but the 
     4concept may come in handy if Athena ever moves to a different 
     7Operationally, a locker is represented by a Hesiod entry with type 
     8"filsys".  The value of the filsys record is a string which usually 
     9looks like "AFS <pathname> <mode> <mountpoint> <pref>", where AFS is 
     10the filesystem type, <pathname> is the AFS path of the locker, <mode> 
     11determines whether tokens are desirable or required for the locker, 
     12<mountpoint> determines where the locker should appear on the local 
     13workstation, and <pref> is used to order filsys entries when there is 
     14more than one.  If the filesystem type is something other than AFS, 
     15different fields may be present. 
     17Users can make lockers visible on an Athena workstation using the 
     18setuid "attach" program.  The "add" alias from the standard Athena 
     19dotfiles attaches a locker and places the appropriate binary and 
     20manual directories in the user's PATH and MANPATH. 
     22A loose convention, documented in the lockers(7) man page, governs how 
     23software lockers should be organized.  Not all lockers are for 
     24software; in particular, user home directories are also lockers, and 
     25generally do not contain any software. 
     27Some platforms (Solaris and IRIX at the time of this writing) refer to 
     28lockers for most of their operating system and Athena software.  The 
     29mountpoints for these lockers are /os for operating system software 
     30and /srvd for Athena software.  On these machines, a third locker 
     31mounted on /install contains material used during installs and