From: Jeff Mcadams <jeffm@iglou.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: John Kodis <kodis@mail630.gsfc.nasa.gov>,
"Richard B. Johnson" <root@chaos.analogic.com>,
linux-kernel@vger.kernel.org, bug-bash@gnu.org
Subject: Re: binfmt_script and ^M
Date: Mon, 5 Mar 2001 10:59:43 -0500 [thread overview]
Message-ID: <20010305105943.A25964@iglou.com> (raw)
In-Reply-To: <20010305095512.A30787@tux.gsfc.nasa.gov> <Pine.LNX.4.21.0103051224450.5591-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.21.0103051224450.5591-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Mon, Mar 05, 2001 at 12:25:13PM -0300
Also sprach Rik van Riel
>On Mon, 5 Mar 2001, John Kodis wrote:
>> On Mon, Mar 05, 2001 at 08:40:22AM -0500, Richard B. Johnson wrote:
>> > Somebody must have missed the boat entirely. Unix does not, never
>> > has, and never will end a text line with '\r'.
>> Unix does not, never has, and never will end a text line with ' ' (a
>> space character) or with \t (a tab character). Yet if I begin a
>> shell script with '#!/bin/sh ' or '#!/bin/sh\t', the training white
>> space is striped and /bin/sh gets exec'd. Since \r has no special
>> significance to Unix, I'd expect it to be treated the same as any
>> other whitespace character -- it should be striped, and /bin/sh
>> should get exec'd.
>Makes sense, IMHO...
That only makes sense if:
#!/bin/shasdf\n
would also exec /bin/sh.
" " and \t are whitespace, \r is not whitespace.
--
Jeff McAdams Email: jeffm@iglou.com
Head Network Administrator Voice: (502) 966-3848
IgLou Internet Services (800) 436-4456
next prev parent reply other threads:[~2001-03-05 16:01 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 13:03 binfmt_script and ^M Ivo Timmermans
2001-02-27 13:44 ` Alan Cox
2001-02-27 13:47 ` Ivo Timmermans
2001-02-27 13:54 ` Alan Cox
2001-02-27 14:36 ` Rogier Wolff
2001-02-28 20:10 ` Erik Hensema
2001-03-01 12:04 ` Pavel Machek
2001-03-05 13:20 ` Jan Nieuwenhuizen
2001-03-05 13:37 ` Andreas Schwab
2001-03-05 13:40 ` Richard B. Johnson
2001-03-05 14:55 ` John Kodis
2001-03-05 15:25 ` Rik van Riel
2001-03-05 15:59 ` Jeff Mcadams [this message]
2001-03-05 16:18 ` Paul Flinders
2001-03-05 17:12 ` Andreas Schwab
2001-03-05 19:54 ` Paul Flinders
2001-03-05 20:09 ` Paul Flinders
2001-03-06 10:41 ` Andreas Schwab
2001-03-06 12:33 ` Paul Flinders
2001-03-06 14:45 ` Laramie Leavitt
2001-03-06 15:12 ` Sean Hunter
2001-03-06 15:37 ` David Weinehall
2001-03-06 21:10 ` Thorsten Glaser Geuer
[not found] ` <20010308130145.O20737@dev.sportingbet.com>
2001-03-09 16:52 ` Thorsten Glaser Geuer
2001-03-06 15:53 ` James A. Sutherland
2001-03-07 8:29 ` Ondrej Sury
2001-03-06 16:59 ` Xavier Bestel
2001-03-06 18:17 ` binfmt_script and ^M (historical note) Don Dugger
2001-03-05 18:58 ` binfmt_script and ^M Pozsar Balazs
2001-03-05 20:39 ` Robert Read
2001-03-05 21:05 ` Pozsar Balazs
2001-03-05 22:34 ` Robert Read
2001-03-06 15:14 ` Jeff Coy
2001-03-06 18:15 ` Peter Samuelson
2001-03-06 18:36 ` Jeff Coy
2001-03-06 20:26 ` John Kodis
2001-03-06 20:43 ` Andreas Schwab
2001-03-06 2:18 ` Richard B. Johnson
2001-03-05 15:50 ` Richard B. Johnson
2001-03-05 16:53 ` H. Peter Anvin
2001-03-05 21:48 ` Dr. Kelsey Hudson
2001-03-06 18:19 ` Peter Samuelson
2001-03-06 21:04 ` Dr. Kelsey Hudson
2001-03-05 14:56 ` [PATCH]: print missing interpreter name [Was: Re: binfmt_script and ^M] Jan Nieuwenhuizen
2001-03-05 15:59 ` Richard B. Johnson
2001-03-05 20:18 ` [PATCH #3]: " Jan Nieuwenhuizen
2001-03-05 16:37 ` binfmt_script and ^M Erik Hensema
2001-03-05 22:13 ` Pavel Machek
2001-02-27 13:42 Heusden, Folkert van
2001-02-27 13:38 ` Ivo Timmermans
2001-02-27 19:20 ` Jamie Lokier
2001-02-27 19:59 ` Don Dugger
2001-02-27 21:35 ` Rogier Wolff
2001-02-27 14:01 ` Bruce Harada
2001-02-27 13:53 Heusden, Folkert van
2001-02-27 14:26 ` Alistair Riddell
2001-02-27 23:22 ` David
2001-02-28 14:07 ` Jamie Lokier
2001-02-28 22:23 ` H. Peter Anvin
2001-03-05 19:14 Jesse Pollard
2001-03-06 20:54 ` Thorsten Glaser Geuer
2001-03-05 21:15 Andries.Brouwer
2001-03-06 13:55 Jesse Pollard
2001-03-06 14:54 ` Andreas Schwab
2001-03-06 15:56 Jesse Pollard
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=20010305105943.A25964@iglou.com \
--to=jeffm@iglou.com \
--cc=bug-bash@gnu.org \
--cc=kodis@mail630.gsfc.nasa.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=root@chaos.analogic.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;
as well as URLs for NNTP newsgroup(s).