From: Pavel Machek <pavel@ucw.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: #! incompatible -- binfmt_script.c broken?
Date: Fri, 6 Dec 2002 10:02:34 +0100 [thread overview]
Message-ID: <20021206090234.GA1940@zaurus> (raw)
In-Reply-To: <aslmtl_im_1@cesium.transmeta.com>
Hi!
> > And because of I was not able to find anything in POSIX which would say
> > that we should do split on spaces (not that I found that we should not),
> > I vote for leaving current behavior in Linux, and fixing perl manpage
> > (and eventually FreeBSD, if anyone is interested) instead.
> >
>
> Classic catch-22: POSIX won't standardize it because of lack of
> consistency between UNIX implementations, although everyone pretty
> much agrees it would be a desirable feature to add to the standard.
Why can't we simply have /bin/bash_that_splits_args_itself
?
Pavel
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2002-12-08 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 19:22 [PATCH] Re: #! incompatible -- binfmt_script.c broken? Petr Vandrovec
2002-12-04 20:00 ` H. Peter Anvin
2002-12-05 2:41 ` Miles Bader
[not found] ` <aslmtl_im_1@cesium.transmeta.com>
2002-12-06 9:02 ` Pavel Machek [this message]
2002-12-09 18:19 ` H. Peter Anvin
2002-12-09 18:26 ` Pavel Machek
2002-12-09 19:23 ` H. Peter Anvin
2002-12-09 21:49 ` Pavel Machek
2002-12-10 0:40 ` Alan Cox
2002-12-10 0:28 ` H. Peter Anvin
2002-12-10 1:11 ` Alan Cox
2002-12-10 0:36 ` H. Peter Anvin
[not found] <20021204170701.16075.58972.Mailman@lists.us.dell.com>
2002-12-04 18:52 ` mbm
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=20021206090234.GA1940@zaurus \
--to=pavel@ucw.cz \
--cc=hpa@zytor.com \
--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