Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!haven!ncifcrf!nlm-mcs!adm!smoke!gwyn
From: gwyn@smoke.ARPA (Doug Gwyn )
Newsgroups: comp.bugs.4bsd
Subject: Re: bin owns stuff (was: Installing 4.3-Tahoe on a VAX)
Message-ID: <8481@smoke.ARPA>
Date: 13 Sep 88 13:34:22 GMT
References: <26049@ucbvax.BERKELEY.EDU> <5416@zodiac.UUCP> <21791@sgi.SGI.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 6

In article <21791@sgi.SGI.COM> vjs@rhyolite.SGI.COM (Vernon Schryver) writes:
>Is there some risk with making root own everything?

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".