From: Hansjoerg Lipp <hjlipp@web.de>
To: Paul Jackson <pj@sgi.com>
Cc: aebr@win.tue.nl, jamie@shareable.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Linux 2.6: shebang handling in fs/binfmt_script.c
Date: Thu, 26 Feb 2004 00:13:08 +0100 [thread overview]
Message-ID: <20040225231308.GA7744@hobbes> (raw)
In-Reply-To: <20040223172942.5a18528a.pj@sgi.com>
On Mon, Feb 23, 2004 at 05:29:42PM -0800, Paul Jackson wrote:
> > I don't see any reason, why one should stick to the limits of some other
> > operating systems, when it's not necessary.
>
> If I make it a habit to write portable code, then over the years, I
> cause fewer problems for myself and others. More things "just work".
> I've got scripts that I use that are 10 or 20 years old, and have been
> used on all manner of evironments that could not have been anticipated
> when the script was first written.
Yes, it's true, that this is often sensible. But I also think, that
sometimes we must get rid of old restrictions, that don't make much
sense.
The patch does not prevent you from writing portable scripts, but it
allows us to write scripts, that can't be written without this change
(or you need some work around like wrappers or an interpreter parsing
the shebang line on its own).
And because you could see this patch as a step towards other operating
systems to reduce the chaos the web pages mentioned in this thread
show[1], this patch might even make scripts written for other operating
systems work under Linux. So, there are not only disadvantages with
regard to portability.
Regards,
Hansjoerg Lipp
[1] http://www.in-ulm.de/~mascheck/various/shebang/
http://homepages.cwi.nl/~aeb/std/hashexclam-1.html
next prev parent reply other threads:[~2004-02-25 23:24 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 [this message]
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=20040225231308.GA7744@hobbes \
--to=hjlipp@web.de \
--cc=aebr@win.tue.nl \
--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