DIFFERENCES between UNIX ANSWERS and NFS/UFS ANSWERS
There are many crucial distinctions between different filesystems. Most
lockers, including almost all users, generally operate under AFS. Some
lockers, mainly course lockers for Course VI, still operate under NFS. There is
also UFS (Unix File System), which governs the local directories on all
workstations, such as /tmp and /usr/tmp.
IMPORTANT: If you are using an NFS locker, such as bitbucket, or a UFS
directory, you should consult the "NFS/UFS ANSWERS" menu. There are
topics, such as setting file permissions, which are handled differently
than they normally would be under AFS. Questions which are specific to
AFS in the UNIX ANSWERS menu, and for which the data might differ under
NFS, are indicated in the title for the answer itself.
In order to tell if a locker is on AFS or NFS, type the following command
at the athena% prompt:
hesinfo lockername filsys
where "lockername" is the name of the locker (such as "matlab",
"bitbucket", or your username.) The response will be something like this:
AFS /afs/athena.mit.edu/user/j/o/joeuser w /mit/joeuser
^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The first three letters will indicate if the locker is on AFS or NFS. The
locker's home directory will also be indicated after that. If it begins
with "/afs/athena.mit.edu/...", that is also a sure sign it is on AFS.
If you are still noe sure which filesystem you are using, one simple way
of telling is by typing the command:
fs la
at the athena% prompt. Under AFS, this will list the permissions for the
current directory. In all other filesystems, it will return an error such
as this:
fs: Invalid argument; it is possible that . is not in AFS.
If you receive this error, you are most likely operating in an NFS locker
or a UFS directory. In this case, the answer you are looking for may be
in the NFS/UFS menu.
|
