Messages in this thread | | | Date | Mon, 05 Mar 2001 16:18:22 +0000 | From | Paul Flinders <> | Subject | Re: binfmt_script and ^M |
| |
Jeff Mcadams wrote:
> 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.
POSIX disagrees with you (accd to the manual page)
$ man isspace .... isspace() checks for white-space characters. In the "C" and "POSIX" locales, these are: space, form-feed ('\f'), newline ('\n'), carriage return ('\r'), horizontal tab ('\t'), and vertical tab ('\v').
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |