env bug ?

[William Park]

On Tue, Mar 08, 2005 at 04:11:15PM -0500, Andrej Marjan wrote:
> Grant Cullen wrote:
> 
> >I tried it and got the same result, but when I put perl instead of 
> >echo foo.  It worked.  I am assuming that the command not found is 
> >echo (an internal shell command) and therefore not in the path.
> >Grant Cullen
> >JADALL Consulting Ltd.
> >grant.cullen-yMeuRWKn1UT3fQ9qLvQP4Q at public.gmane.org
> >416-706-4447
> 
> 
> amarjan at gondolin:~$ cat ./z
> #!/usr/bin/env perl foo
> amarjan at gondolin:~$ ./z
> /usr/bin/env: perl foo: No such file or directory
> 
> Doesn't work any better than echo, with the Debian 2.6.10 kernel. ;)

I'm getting same result for all shells (Bash, Ksh, Zsh, Ash) on my
system.  Who's responsible for interpreting #! line?  Kernel or shell?

-- 
William Park <opengeometry-FFYn/CNdgSA at public.gmane.org>, Toronto, Canada
Slackware Linux -- because it works.
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml