Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!LNIC1.HPRC.UH.EDU!wescott
From: wescott@LNIC1.HPRC.UH.EDU (Andrew M. Wescott)
Newsgroups: comp.sys.apollo
Subject: Re: su
Message-ID: <8906291414.AA04731@lnic1.hprc.uh.edu>
Date: 29 Jun 89 14:14:18 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 17

So what is wrong with having to belong to group "wheel" in
order to su root?  I miss the point entirely.  Let the sysadm
add whoever to wheel from edrgy, give them the password, and
be done with it.  

There is one interesting hitch though...

Say I am logged on to an Apollo console as myself, and then I
decide to su root.  Well now I can do things like run edrgy,
kill processes, and the like.  But guess what I can't do?
I can't EDIT files owned by root.staff.none with -rwxr-xr-x
protection.  Now here's the real clincher:  When I dial up 
from home and decide to su root, I am able to edit these\
same files with no problem.  That confuses me.

Andrew Wescott
University of Houston