All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Hansjoerg Lipp <hjlipp@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Linux 2.6: shebang handling in fs/binfmt_script.c
Date: Mon, 23 Feb 2004 14:24:51 -0800	[thread overview]
Message-ID: <20040223142451.1432ef52.pj@sgi.com> (raw)
In-Reply-To: <20040223201340.GA13914@hobbes>

Hansjoerg wrote:
> #!/bin/zsh -v -x
> ...
> this should be "evidence" enough(?)

This testing was done on a system with your patch applied, right?
Because on a stock kernel, the various shells are of course
confused by the "-v -x" argv[1].

I will grant that ksh, bash, ash, tcsh and zsh are likely ok
(willing to see > 1 option before the script file name.)

An alternative way to test the same thing, that works even on
a stock kernel:

  $ echo 'echo "$*"' > ./d
  $ ash -e -e ./d 1 2 3
  $ tcsh -v -v ./d 1 2 3
  $ zsh -e -e ./d 1 2 3
  $ ksh -e -e ./d 1 2 3
  $ bash -e -e ./d 1 2 3

The thing being tested: will a shell handle > 1 option before a script
file name.  Each shell invocation of the "./d" script should echo the
script file arguments "1 2 3".

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@sgi.com> 1.650.933.1373

  reply	other threads:[~2004-02-23 22:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 13:34 [PATCH] Linux 2.6: shebang handling in fs/binfmt_script.c Hansjoerg Lipp
2004-02-22 10:09 ` Paul Jackson
2004-02-22 15:54   ` Hansjoerg Lipp
2004-02-22 20:53     ` Paul Jackson
2004-02-22 22:57       ` Jamie Lokier
2004-02-23  5:44         ` Paul Jackson
2004-02-23 14:22           ` Jamie Lokier
2004-02-23 17:34             ` Andries Brouwer
2004-02-23 20:13               ` Paul Jackson
2004-02-23 21:46               ` Paul Jackson
2004-02-24  1:13                 ` Hansjoerg Lipp
2004-02-24  1:29                   ` Paul Jackson
2004-02-25 23:13                     ` Hansjoerg Lipp
2004-02-23 20:12             ` Paul Jackson
2004-02-23 20:16               ` Jamie Lokier
2004-02-23 22:08                 ` Paul Jackson
2004-02-23 20:25           ` Hansjoerg Lipp
2004-02-23 22:00             ` Paul Jackson
2004-02-23 23:59               ` Jamie Lokier
2004-02-24  0:13               ` Hansjoerg Lipp
2004-02-24  1:32                 ` Paul Jackson
2004-02-25 23:14                   ` Hansjoerg Lipp
2004-02-25 23:24                     ` Paul Jackson
2004-02-23 20:13       ` Hansjoerg Lipp
2004-02-23 22:24         ` Paul Jackson [this message]
2004-02-24  0:21           ` Hansjoerg Lipp
2004-02-23  5:49     ` Paul Jackson
2004-02-23  5:50     ` Paul Jackson
2004-02-23  5:42 ` Paul Jackson
2004-02-23 20:24   ` Hansjoerg Lipp
2004-02-23 21:55     ` Paul Jackson

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=20040223142451.1432ef52.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=hjlipp@web.de \
    --cc=linux-kernel@vger.kernel.org \
    /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.