inconsistency on read/execute permissions for shell procedures

[Sean Casey]

In article <6503 at boring.UUCP> guido at mcvax.UUCP (Guido van Rossum) writes:
>In article <1945 at ukma.UUCP> sean at ukma.UUCP (Sean Casey) writes:

>>        ... since a simple solution would be to have the kernel hand the
>>shell the file on standard input if --x access is permitted.  ...
>
>Simple: the shell's standard input is also the shell file's standard input,
>and with your proposed solution the shell script wouldn't be able to read
>interesting user data from its standard input, wouldn't be usable as a filter,
>etc.  So the contents of the shell file has to be presented to the shell
>without closing or dupping the standard input.

Ok, that makes sense.  How about handing the shell an open file descriptor
with the shell script opened for reading?

Sean
-- 

-  Sean Casey				UUCP:	sean at ukma.UUCP   or
-  Department of Mathematics			{cbosgd,anlams,hasmed}!ukma!sean
-  University of Kentucky		ARPA:	ukma!sean at ANL-MCS.ARPA