Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/3/85; site ukma.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!cbosgd!ukma!sean
From: sean@ukma.UUCP (Sean Casey)
Newsgroups: net.unix
Subject: Re: inconsistency on read/execute permissions for shell procedures
Message-ID: <1965@ukma.UUCP>
Date: Thu, 18-Jul-85 01:51:13 EDT
Article-I.D.: ukma.1965
Posted: Thu Jul 18 01:51:13 1985
Date-Received: Sat, 20-Jul-85 08:22:23 EDT
References: <761@wanginst.UUCP> <1945@ukma.UUCP> <6503@boring.UUCP>
Reply-To: sean@ukma.UUCP (Sean Casey)
Distribution: net
Organization: The White Tower @ The Univ. of KY
Lines: 21

In article <6503@boring.UUCP> guido@mcvax.UUCP (Guido van Rossum) writes:
>In article <1945@ukma.UUCP> sean@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@ukma.UUCP   or
-  Department of Mathematics			{cbosgd,anlams,hasmed}!ukma!sean
-  University of Kentucky		ARPA:	ukma!sean@ANL-MCS.ARPA