All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Newall <davidn@davidnewall.com>
To: Valery Reznic <valery_reznic@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: execve for script don't return ENOEXEC, bug ?
Date: Sat, 20 Mar 2010 20:11:56 +1030	[thread overview]
Message-ID: <4BA49864.7080503@davidnewall.com> (raw)
In-Reply-To: <687582.96058.qm@web110305.mail.gq1.yahoo.com>

Valery Reznic wrote:
> [valery@localhost ~]$ cat a.sh 
> #!/bin/sh
> echo "It's a.sh"
> [valery@localhost ~]$ cat b.sh 
> #! ./a.sh
> echo "It's b.sh"
> [valery@localhost ~]$ 
> [valery@localhost ~]$ strace -f -e execve setarch i386 ./b.sh 
> execve("/usr/bin/setarch", ["setarch", "i386", "./b.sh"], [/* 40 vars */]) = 0
> execve("./b.sh", ["./b.sh"], [/* 40 vars */]) = 0
> It's a.sh
>   

That is the correct output for a script which is being interpreted by 
a.sh, when a.sh prints "It's a.sh" using /bin/sh as its interpreter.  
Remember, you didn't ask /bin/sh to interpret b.sh, you asked a.sh to do 
it, and a.sh is a simple echo statement, not an interpreter.  There is 
no error here.

  reply	other threads:[~2010-03-20  9:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 10:56 execve for script don't return ENOEXEC, bug ? Valery Reznic
2010-03-19 21:07 ` Andrew Morton
2010-03-20  0:37   ` David Newall
2010-03-20  6:42     ` Valery Reznic
2010-03-20  9:41       ` David Newall [this message]
2010-03-20 12:56         ` Valery Reznic
2010-03-20 17:57           ` David Newall
2010-03-21  8:33             ` Valery Reznic
     [not found]               ` <876436.86374.qm-3jHsvP0p17FeqboJWQvT7/u2YVrzzGjVVpNB7YpNyf8@public.gmane.org>
2010-03-21 19:16                 ` Johannes Stezenbach
2010-03-21 19:16                   ` Johannes Stezenbach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BA49864.7080503@davidnewall.com \
    --to=davidn@davidnewall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=valery_reznic@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.