[lkml]   [2001]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: binfmt_script and ^M
    On Mon, 5 Mar 2001, Robert Read wrote:
    > On Mon, Mar 05, 2001 at 07:58:52PM +0100, Pozsar Balazs wrote:
    > >
    > > And what does POSIX say about "#!/bin/sh\r" ?
    > > In other words: should the kernel look for the interpreter between the !
    > > and the newline, or [the first space or newline] or the first whitespace?
    > >
    > > IMHO, the first whitespace. Which means that "#!/bin/sh\r" should invoke
    > > /bin/sh. (though it is junk).
    > The line terminator, '\n', is what terminates the interpreter. White
    > space (in this case, only ' ' and '\t') is used to seperate the
    > arguments to the interpreter.

    The last little tiny thing that bothers me: why? Why only ' ' and '\t' _in
    this case_? As someone mentioned, even isspace() returns whitespace.

    A possible answer (that i can think of), is that those ar the whitespaces,
    which are in IFS (as said previously), taking out us from kernel-space
    into userspace. But imho we shouldn't define another set whitespace for
    this case, can't we just use what isspace() says?

    (okay, I'm not for this '\r' thingy, I just want to see the reasons.)

    Balazs Pozsar.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:29    [W:0.021 / U:71.400 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site