Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!rutgers!husc6!harvard!adelie!morgoth!dmb
From: dmb@morgoth.UUCP (David M. Brown)
Newsgroups: net.unix
Subject: Re: Looking through other users' (unprotected) files
Message-ID: <169@morgoth.UUCP>
Date: Thu, 23-Oct-86 14:56:18 EDT
Article-I.D.: morgoth.169
Posted: Thu Oct 23 14:56:18 1986
Date-Received: Fri, 24-Oct-86 08:14:50 EDT
References: <1246@kitty.UUCP> <141@rayssd.UUCP> <2433@phri.UUCP> <2046@saber.UUCP> <3561@mit-eddie.MIT.EDU>
Organization: Goldberg-Zoino and Assoc., Newton, MA
Lines: 24
Summary: Chmod sets PERMISSIONS

[]

It occurs to me that whenever you have a shared resource (ie, disk
space), you have entered the domain of politics.  There are several
ways to deal with this.  One is anarchy (anyone may do whatever s/he
is able to do).  In a system in which there are no controls, it is
impossible to totally prevent this mode of politics from occurring.
My favorite way of dealing with political situations is to use the
concepts of etiquette and convention.  An example of etiquette is
'using only what you need.'  An example of convention is 'it is
permissible to read files for which you have read permission.'

Essentially, it is all wrapped up in the word "permission."  By
setting the appropriate _read_ _permission_ on your files and
directories, you are giving me _permission_ to read them.  Novices
will learn.

dmb@morgoth

Dave Brown
GZA
(617) 969-0050

#include '/usr/local/disclaimer'