From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: #! incompatible -- binfmt_script.c broken?
Date: 9 Dec 2002 11:23:03 -0800 [thread overview]
Message-ID: <at2qin$fgn$1@cesium.transmeta.com> (raw)
In-Reply-To: 20021209182605.GA22747@atrey.karlin.mff.cuni.cz
Followup to: <20021209182605.GA22747@atrey.karlin.mff.cuni.cz>
By author: Pavel Machek <pavel@ucw.cz>
In newsgroup: linux.dev.kernel
>
> Hi!
>
> > > Why can't we simply have /bin/bash_that_splits_args_itself
> >
> > We could, but it would in practice mean doing an extra exec() for each
> > executable. This seems undesirable.
>
> Only for executables that need argument spliting... For such scripts I
> guess we can get handle the overhead.
>
We probably can, but a better question is really: what are the
semantics that users expect? Given that Unices are by and large
inconsistent, we should pick the behaviour that makes sense to the
most people. I suspect that most people would expect whitespace
partition.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-12-09 19:15 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
2002-12-09 18:19 ` H. Peter Anvin
2002-12-09 18:26 ` Pavel Machek
2002-12-09 19:23 ` H. Peter Anvin [this message]
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='at2qin$fgn$1@cesium.transmeta.com' \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.