From: Hansjoerg Lipp <hjlipp@web.de>
To: Paul Jackson <pj@sgi.com>
Cc: jamie@shareable.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Linux 2.6: shebang handling in fs/binfmt_script.c
Date: Tue, 24 Feb 2004 01:13:13 +0100 [thread overview]
Message-ID: <20040224001313.GA6426@hobbes> (raw)
In-Reply-To: <20040223140027.5c035157.pj@sgi.com>
On Mon, Feb 23, 2004 at 02:00:27PM -0800, Paul Jackson wrote:
> Hansjoerg wrote:
> > I still don't understand your argument... If there is a shell having
> > those problems, nobody would use something like
>
> I will acknowledge that while one _could_ code a shell so that your
> proposed change would break it, it would be a stupid, silly and ugly
> way to code a shell.
>
> That is, one _could_ code a shell to say:
>
> 1) If argv[1] starts with a '-', consume and handle as an option
> (or possibly as a space separated list of options).
> 2) Presume the next argument, if any, is a shell script file.
There is no problem with such a shell if you use scripts beginning with
#!/some/shell
or
#!/some/shell -some_arg
if some_arg does not contain whitespace characters. In both cases,
argv will be the same as it is with the current code.
/some/script param1 param2
will become
/some/shell /some/script param1 param2
or
/some/shell -some_arg /some/script param1 param2
as it has been before.
There is a problem with a shebang line like
#!/some/shell -x -y
_but_ this was most probably an error, before. (Unless this shell
accepts _one_ parameter "-x -y" containing a space.)
So, I really can't see any problem with such a shell...
Regards,
Hansjoerg Lipp
next prev parent reply other threads:[~2004-02-24 1:26 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 [this message]
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
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=20040224001313.GA6426@hobbes \
--to=hjlipp@web.de \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox