Re: /usr/bin/env behaviour?

["Malcolm Herbert" <mjch%mjch.net@localhost>]

On Sun, 9 Nov 2008 03:28:09 +0100, "Rhialto" <rhialto%falu.nl@localhost> said:
> On Sun 09 Nov 2008 at 11:03:20 +1100, Malcolm Herbert wrote:
> > Thinking about it, it may not even be env's fault if /bin/sh (or
> > whatever is responsible for parsing the #! line) is giving env a badly
> > tokenised set of arguments ...
> 
> Here you're closest. It is the execve() system call that parses the line
> and decides to invoke env. Unfortunately it allows only a single
> argument.

argh ... that kind of scuppers my plan somewhat ... :(


-- 
Malcolm Herbert                                This brain intentionally
mjch%mjch.net@localhost                                                left 
blank