From: Paul Jackson <pj@sgi.com>
To: Hansjoerg Lipp <hjlipp@web.de>
Cc: linux-kernel@vger.kernel.org, hjlipp@web.de
Subject: Re: [PATCH] Linux 2.6: shebang handling in fs/binfmt_script.c
Date: Sun, 22 Feb 2004 02:09:11 -0800 [thread overview]
Message-ID: <20040222020911.2c8ea5c6.pj@sgi.com> (raw)
In-Reply-To: <20040216133418.GA4399@hobbes>
In addition to the incompatible changes you note:
1) "#! cmd x y" to pass single arg "x y" with embedded space broken
2) Use of '\' char changed
3) Handling of long line changed
doesn't this also
4) risk breaking shells that look to argv[2] for the name of the
shell script file for error messages? This argument
has moved out to argv[argc-1], for some value of argc.
I'll wager you have to make a better case for this than simply:
As I'm really missing this feature in Linux and changing this
would not break any (unless ...
before the above incompatibilities in a critical piece of code are
overcome with the compelling need to change these details.
Perhaps you can handle any such special argument specification by
wrapping the user level command, as in:
Instead of:
#!/usr/bin/awk -F \t -f
... my awk code ...
rather do:
#!myawk
... my awk code ...
where myawk is a compiled program that essentially does
/usr/bin/awk -F '\t' -f argv[2]
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-02-22 10:07 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 [this message]
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
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=20040222020911.2c8ea5c6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox