Path: utzoo!attcan!uunet!yale!husc6!ukma!david From: david@ms.uky.edu (David Herron -- One of the vertebrae) Newsgroups: comp.bugs.4bsd Subject: Re: bin owns stuff Message-ID: <10242@s.ms.uky.edu> Date: 14 Sep 88 17:16:38 GMT References: <26049@ucbvax.BERKELEY.EDU> <5416@zodiac.UUCP> <21791@sgi.SGI.COM> <21879@sgi.SGI.COM> <13551@mimsy.UUCP> Reply-To: david@ms.uky.edu (David Herron -- One of the vertebrae) Organization: U of Kentucky, Mathematical Sciences Lines: 19 My reason for wanting binaries owned by bin (except when necessary) (besides the convenience reasons mentioned above of not having to live as root) is so that I can do something like 'quota bin' and find out how much disk space is taken up by system programs. Or I could split them over a couple of different user-id's, one for each type. Like 'local-bin', 'usg-bin', and 'ucb-bin'. That's just one reason, the underlying reason is esthetics. If you define 'bin' to be the owner of the binaries they 'he' should own the binaries. Defining 'bin' this way gives more flexibility (after all, flexibility is one of the traditions of Unix) than defining 'root' as the owner of everything but user stuff. -- <---- David Herron -- One of the MMDF guys <---- ska: David le casse\*' {rutgers,uunet}!ukma!david, david@UKMA.BITNET <---- What does the phrase "Don't work too hard" <---- have to do with the decline of the american 'work ethic'?