Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!hal!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery)
Newsgroups: news.groups
Subject: Re: System administration
Message-ID: <1989Nov24.012944.26274@NCoast.ORG>
Date: 24 Nov 89 01:29:44 GMT
References: <1730@l.cc.purdue.edu>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery)
Followup-To: news.groups
Organization: North Coast Public Access UN*X, Cleveland, OH
Lines: 23

As quoted from <1730@l.cc.purdue.edu> by cik@l.cc.purdue.edu (Herman Rubin):
+---------------
| The system OWNER has the right to do this.  A system administrator has an 
| important function to perform, namely, to make the system work well for the
| USERS.  As administrator, s/he has no business making rules for his convenience
| if they degrade the system in the eyes of the owner and/or users.
| -- 
+---------------

(1) Often, the system administrator *is* the owner.
(2) When s/he is *not* the owner, s/he is selected *by* the owner in order to
    manage the system for the owner.  In that case, the sysadmin is bound by
    what the users want only insofar as the owner wishes it to be that way; and
    in any disagreement between the owner's wishes and the users' wishes as
    moderated by the sysadmin, the owner's wishes are final.

++Brandon
-- 
Brandon S. Allbery    allbery@NCoast.ORG, BALLBERY (MCI Mail), ALLBERY (Delphi)
uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu bsa@telotech.uucp
*(comp.sources.misc mail to comp-sources-misc[-request]@backbone.site, please)*
*Third party vote-collection service: send mail to allbery@uunet.uu.net (ONLY)*
expnet.all: Experiments in *net management and organization.  Mail me for info.