From: Valdis.Kletnieks@vt.edu
To: root@chaos.analogic.com
Cc: Andreas Schwab <schwab@suse.de>,
Mark Grosberg <mark@nolab.conman.org>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFD] Combined fork-exec syscall.
Date: Mon, 28 Apr 2003 10:38:14 -0400 [thread overview]
Message-ID: <200304281438.h3SEcFdA003667@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 28 Apr 2003 10:16:21 EDT." <Pine.LNX.4.53.0304281001200.16752@chaos>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On Mon, 28 Apr 2003 10:16:21 EDT, "Richard B. Johnson" said:
> Read the bash documentation `man bash`. The first argument becomes
> $0 (the process name), the second becomes $1, etc. Please don't
> just keep assuming that I don't know what I'm talking about.
>
> $ sh -c 'ignore echo a b c'
> Works fine.
[~]2 /bin/bash -c ignore echo a b c
echo: line 1: ignore: command not found
[~]2 /bin/bash -c 'ignore echo a b c'
/bin/bash: line 1: ignore: command not found
Obviously, tokenization makes a difference here. ;)
So let's try forcing $0 to /bin/bash rather than 'ignore'...
[~]2 sh -c '/bin/bash echo a b c'
echo: /bin/echo: cannot execute binary file
Correct, but unexpected results..
[~]2 sh -c /bin/echo echo a b c
[~]2 sh -c '/bin/echo a b c'
a b c
Again, tokenization matters - try working out what the value of argc is
for the exec of /bin/bash for each of these cases...
Dick, do you have an 'ignore' in your $PATH?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-04-28 14:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 0:57 [RFD] Combined fork-exec syscall Mark Grosberg
2003-04-28 0:59 ` Larry McVoy
2003-04-28 1:16 ` Mark Grosberg
2003-04-28 1:36 ` Måns Rullgård
2003-04-28 1:45 ` Mark Grosberg
2003-04-28 1:49 ` dean gaudet
2003-04-28 1:59 ` Mark Grosberg
2003-04-28 2:27 ` Miles Bader
2003-04-28 19:07 ` dean gaudet
2003-05-01 13:14 ` Jakob Oestergaard
2003-04-28 1:17 ` Davide Libenzi
2003-04-28 1:28 ` Mark Grosberg
2003-04-29 2:01 ` Rafael Costa dos Santos
2003-04-28 1:41 ` Ulrich Drepper
2003-04-28 1:49 ` Mark Grosberg
2003-04-28 2:19 ` Ulrich Drepper
2003-04-28 6:59 ` Kai Henningsen
2003-04-28 1:35 ` dean gaudet
2003-04-28 1:43 ` Mark Grosberg
2003-04-28 3:44 ` Mark Mielke
2003-04-28 5:16 ` Jamie Lokier
2003-04-28 2:38 ` Davide Libenzi
2003-04-28 2:09 ` Richard B. Johnson
2003-04-28 2:12 ` Mark Grosberg
2003-04-28 2:42 ` Werner Almesberger
2003-04-28 6:35 ` Mark Grosberg
2003-04-29 2:47 ` Rafael Santos
2003-04-28 3:20 ` Werner Almesberger
2003-04-28 13:00 ` Richard B. Johnson
2003-04-28 13:22 ` Andreas Schwab
2003-04-28 13:57 ` Richard B. Johnson
2003-04-28 13:57 ` Andreas Schwab
2003-04-28 14:16 ` Richard B. Johnson
2003-04-28 14:38 ` Valdis.Kletnieks [this message]
2003-04-28 14:56 ` Richard B. Johnson
2003-04-28 14:42 ` Andreas Schwab
2003-04-28 16:36 ` Mark Grosberg
2003-04-28 17:19 ` Davide Libenzi
2003-04-28 18:28 ` Craig Ruff
2003-05-06 2:48 ` Miles Bader
2003-04-29 18:50 ` Timothy Miller
2003-04-28 2:32 ` Werner Almesberger
2003-04-28 7:40 ` Mirar
2003-04-28 12:45 ` Matthias Andree
2003-04-29 1:05 ` Rafael Costa dos Santos
2003-04-28 1:19 ` Mark Grosberg
2003-04-29 1:29 ` Rafael Costa dos Santos
2003-04-28 3:03 Davide Libenzi
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=200304281438.h3SEcFdA003667@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@nolab.conman.org \
--cc=root@chaos.analogic.com \
--cc=schwab@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).