Path: utzoo!yunexus!geac!drew
From: drew@geac.UUCP (Drew Sullivan)
Newsgroups: comp.bugs.4bsd
Subject: Re: bin owns stuff (was: Installing 4.3-Tahoe on a VAX)
Message-ID: <3224@geac.UUCP>
Date: 15 Sep 88 11:16:50 GMT
Article-I.D.: geac.3224
References: <26049@ucbvax.BERKELEY.EDU> <5416@zodiac.UUCP> <21791@sgi.SGI.COM> <8481@smoke.ARPA> <21879@sgi.SGI.COM>
Reply-To: drew@lethe.UUCP (Drew Sullivan)
Organization: Systems Software
Lines: 24

In article <21879@sgi.SGI.COM> vjs@rhyolite.SGI.COM (Vernon Schryver) writes:
>In article <8481@smoke.ARPA>, gwyn@smoke.ARPA (Doug Gwyn ) writes:
>> The basic idea is to avoid forcing the system administrator to act under
>> UID 0 unless absolutely necessary.  Files owned by "bin" can be updated
>> by "bin" rather than "root".
>
>Should anyone besides root be allowed to 'update' sh or crontab?

Yes, the system owner.  I for one run a different copy of sh then the stock
one.  Sh is owned by local (its my box, I can changed sh if I want to).  In
this way I can tell 6 months down the road what are local updated versions of
files vs the stock (bin) distibuted files.

Xenix has this habbit of new releases that aren't quit there yet.  Getty
is another program I had to replace because I wanted different getty programs
than the normal /etc/getty.  So I wrote a getty dispatcher that would invoke
uugetty or the normal getty based on its arguements.

Lastly with Xenix's 10 consoles, I can have myself loggin on 5 times,
uucp admin, lp admin, and local admin (owner of /etc/passwd, /u (users)).

I have found that the need to go super user is slowing disappearing.
-- 
-- Drew Sullivan <drew@lethe.uucp>   +1 416 225-1592  Toronto, Ontario, Canada