[115] in DCNS Development
Major problem with AFS
daemon@ATHENA.MIT.EDU (Mark Rosenstein)
Tue Sep 24 12:21:46 1991
Date: Tue, 24 Sep 91 12:20:36 -0400
From: Mark Rosenstein <mar@MIT.EDU>
To: reidmp@Athena.mit.edu
Cc: nschmidt@Athena.mit.edu, carla@Athena.mit.edu, dot@Athena.mit.edu,
In-Reply-To: Reid M. Pinchback's message of Tue, 24 Sep 91 10:50:02 EDT <9109241450.AA05125@e40-302-4.MIT.EDU>
I just figured out what has been bothering me about these discussions.
I approach file protection wanting everything to be open and world
readable. I have one directory called private for the few exceptions.
When I create new directories, I want them to be readable. Both NFS
and AFS handle this case fine.
Naomi, on the other hand, wants most things to be private. She has a
few exceptions, but most files should not be readable and newly
created directories should not be readable. This would work fine with
both NFS and AFS if everything were private. But when you want a
couple of exceptions, you have to make your top level directory
readable so that people can get to the subdirectories which are
public. And if the top level is readable, then AFS enheritance of
permissions does not do the right thing.
It sounds like we need a flag per user that says whether the default
case should be readable or private--and of course, that is what the
umask is.
-Mark
