From: Warren Toomey <wkt@cs.adfa.edu.au>
Message-Id: <200004180010.KAA42226@henry.cs.adfa.edu.au>
Subject: Re: Early file system layouts
In-Reply-To: <200004172217.IAA38973@minnie.cs.adfa.edu.au> from "norman@nose.cs.utoronto.ca" at "Apr 16, 2000  2:43:14 pm"
To: 
Date: Tue, 18 Apr 2000 10:10:41 +1000 (EST)
Cc: pups@minnie.cs.adfa.edu.au
Reply-To: wkt@cs.adfa.edu.au
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups@minnie.cs.adfa.edu.au
Precedence: bulk

In article by norman@nose.cs.utoronto.ca:
> - Second Edition sh(I) (dated 3/15/72):
> 	If the first argument is the name of an executable file,
> 	it is invoked; otherwise the string "/bin/" is prepended
> 	to the argument.  (In this way the standard commands,
> 	which reside in "/bin", are found.)  If the "/bin" file
> 	exists, but is not executable, it is used by the shell
> 	as a command file.
> Notice the odd detail that non-executable files in /bin (early on)
> or /usr/bin (later) get special treatment.  Does this mean that
> shell scripts that weren't in /usr/bin had to be invoked explicitly
> via `sh script' instead of just `script'?

Can't tell, we don't have the source code. In the Nsys kernel (dated
just before the 4th Edition), files must have the execute bit on or
they can't be exec(2)d.

	Warren