Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site hocda.UUCP
Path: utzoo!watmath!clyde!burl!hou3c!hocda!grt
From: grt@hocda.UUCP (G.TOMASEVICH)
Newsgroups: net.unix-wizards
Subject: Assorted bins and libs, why?
Message-ID: <415@hocda.UUCP>
Date: Mon, 23-Apr-84 13:52:28 EST
Article-I.D.: hocda.415
Posted: Mon Apr 23 13:52:28 1984
Date-Received: Tue, 24-Apr-84 07:42:57 EST
Organization: AT&T Bell Labs, Holmdel, NJ
Lines: 14

In reference to existence of /bin, /usr/bin, etc., I can see conflicting
considerations:
One wants to have publicly available user written commands without an
extremely long PATH.  We have /bin, /usr/bin, and /usr/jerq/bin, plus any
private bin that a user has.  The directories /usr/bin and /usr/lib have
general write permission, but not /bin or /lib.  It just occurred to me
that this is a security hole.  Maybe everything that comes with /usr/bin
and /usr/lib should be moved into /bin and /lib, assuming a large root
filesystem.  Then we have the path problem someone mentioned.
On the other hand, if there are many commands in one directory, then it
could have more than ten blocks, which causes searching to be slow when
the indirectly addressed part of the directory must be searched.
This all assumes filesystem size is not an issue.
	George Tomasevich, AT&T Bell Laboratories