Subject: Re: Changing exec's #! behavior
To: None <firstname.lastname@example.org>
From: Christos Zoulas <email@example.com>
Date: 06/13/2000 18:45:20
On Jun 13, 3:33pm, firstname.lastname@example.org (Jason R Thorpe) wrote:
-- Subject: Re: Changing exec's #! behavior
| On Tue, Jun 13, 2000 at 09:32:09PM +0000, Christos Zoulas wrote:
| > Now I suddenly cannot use an interpreter that has a space in its
| > filename. What should the kernel do next? Start parsing backslash
| Actually, you couldn't do that before, either. Try it. It will stop
| at the space (considering that the end of the interpreter name), and
| then hand the rest of the line off to the interpreter as the argument.
ok, then it might break things like
#!/bin/sh # execute the shell.
But I guess, fine I think it is more reasonable to pass the argv vector.