linux-kernel - Re: Shebang - why are parameters not splitted on whitespace?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fbdd0e50812060402q6aaaed6q6bb345c50ed68b07@mail.gmail.com>
Date:	Sat, 6 Dec 2008 13:02:14 +0100
From:	Geralt <usr.gentoo@...glemail.com>
To:	Valdis.Kletnieks@...edu,
	"Américo Wang" <xiyou.wangcong@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Shebang - why are parameters not splitted on whitespace?

On Sat, Dec 6, 2008 at 6:41 AM,  <Valdis.Kletnieks@...edu> wrote:
> On Sat, 06 Dec 2008 01:04:52 GMT, Américo Wang said:
>> On Wed, Dec 3, 2008 at 5:29 PM, Geralt <usr.gentoo@...glemail.com> wrote:
>> > Hello,
>> >
>> > I should have anticipated this objection :-). I'm aware that this is
>> > not consistent among Unix operating systems (you can find more about
>> > it here [1]), but I was specifically refering to linux in this case
>> > and why it handles the shebang arguments as one big string and not as
>> > single arguments for the application.
>>
>> I can't think out any strong reasons, maybe only becasue Linux developers
>> prefer that approach.
>
> And of course, "whitespace" is a somewhat fungible concept.  'man bash'
> and read about $IFS.
>
So you're saying that you can't do that because you don't know where
to split the parameters, right? But would it be that bad to state a
rule what "whitespace" is in the shebang line?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/