Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!decwrl!sun!guy
From: guy@sun.uucp (Guy Harris)
Newsgroups: net.unix
Subject: Re: inconsistency on read/execute permissions for shell procedures
Message-ID: <2407@sun.uucp>
Date: Wed, 10-Jul-85 21:37:49 EDT
Article-I.D.: sun.2407
Posted: Wed Jul 10 21:37:49 1985
Date-Received: Fri, 12-Jul-85 04:49:03 EDT
References: <761@wanginst.UUCP> <1945@ukma.UUCP>
Distribution: net
Organization: Sun Microsystems, Inc.
Lines: 12

> On BSD systems, the kernel can understand that a file is a shell file
> and start a shell to interpret it.  It seems that the shell must me able
> to read the file to be able to execute it.  I really do not understand why
> this is so, since a simple solution would be to have the kernel hand the
> shell the file on standard input if --x access is permitted.

Unfortunately, this would mean that a shell script couldn't act as a filter;
one of the major improvements that the Bourne shell offered over the V6
shell was that it didn't redirect the standard input of all the programs run
in a shell script to the script, so that you could run a script as a filter.

	Guy Harris