[113] in DCNS Development
Re: Directory protections in AFS
daemon@ATHENA.MIT.EDU (Tom Coppeto)
Tue Sep 24 10:23:04 1991
To: nschmidt@Athena.mit.edu
Cc: developers@Athena.mit.edu
In-Reply-To: Your message of Tue, 24 Sep 91 09:06:33 -0400.
Date: Tue, 24 Sep 91 10:22:07 BST
From: Tom Coppeto <tom@Athena.mit.edu>
Since NFS uses the unix file system protection scheme, it is your
umask that dictates the default protection for new files and
directories. The concept of the umask does not exist under AFS, so
protections are inherited. Since the default umask is currently 77, we
can expect people to lose in a similar way as you have.
I'm not sure how the permit command fits into this since it is the
default behavior that has changed. I would assume there is no problem
if everyone realizes they have to do something to protect their files.
Unfortunately it is an education process.
This education process concerning the file protection scheme was
discussed a bit at the conversion meetings. In addition to the lack of
a umask, you have the inability to protect one file in a public
directory, and the incomplete information given by ls (as well as the
change of incantation to modify protections).
My understanding is that this education process, as one of the reasons
the conversion was delayed until next year, was to be addressed in
this time frame. I'm sure everyone is psyched to get these conversion
meetings going again.
- Tom
