mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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:14:39 +0100	[thread overview]
Message-ID: <20040225231439.GB7744@hobbes> (raw)
In-Reply-To: <20040223173246.5998e0a1.pj@sgi.com>

On Mon, Feb 23, 2004 at 05:32:46PM -0800, Paul Jackson wrote:
> > So, I really can't see any problem with such a shell...
> 
> I think we are agreeing on the technical details.
> 
> But not on the relative weight of the potential problems
> versus the value of the change you propose.

Okay. So the "result" of this discussion seems to be:

We agree, that it is not that likely that there will be a lot of
problems caused by existing scripts with a shebang line with one
argument containing spaces. But you still consider this too risky,
whereas Jamie Lokier (if I understood him right) and I think, the risk
is low enough.

The '\'-part seems to be more problematic and not that useful. So, this
part could be removed from the patch.

Andries Brouwer's web page shows me, that there are operating systems
that already split arguments, which seems to work without a lot of
problems, while you emphasize the fact, that there are more operating
systems parsing the shebang line the "old" way.

So, talking about the same facts, we still disagree, and I don't think
further discussion will change this. How should we proceed? Should we
still wait for other comments (I'd really like to know what people
think about it)? Should I ask Andrew Morton what he thinks about it,
also with regard to our discussion? Or do you still see facts, we should
talk about?

Regards,

	Hansjoerg Lipp

  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 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 [this message]
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=20040225231439.GB7744@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

all inboxes | Powered by JetHome®