Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>)
Newsgroups: net.unix
Subject: Re: inconsistency on read/execute permissions for shell procedures
Message-ID: <52@brl-tgr.ARPA>
Date: Sun, 21-Jul-85 01:13:12 EDT
Article-I.D.: brl-tgr.52
Posted: Sun Jul 21 01:13:12 1985
Date-Received: Mon, 22-Jul-85 04:19:48 EDT
References: <761@wanginst.UUCP> <1945@ukma.UUCP> <6503@boring.UUCP> <1965@ukma.UUCP>
Distribution: net
Organization: Ballistic Research Lab
Lines: 6

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

?? The shell will open the file specified as an argument, or if that
is omitted, it will take commands from FD # 0 (standard input).
How would opening a file on e.g. FD # 3 do any good?