Re: binfmt_script
Aron Griffis (agriffis@css.tayloru.edu)
Tue, 16 Jun 1998 10:33:42 -0400
Quoting Jeff Voskamp (jeff@bifrost.voskamp.waterloo.on.ca):
> >There appears to be a restriction on scripts that allows only a single
> >parameter to the interpreter in the #! line. For example:
> >
> > #!/bin/csh -fb <-- fine
> > #!/bin/csh -f -b <-- not allowed
> >
> >Is there a reason for this restriction?
> >
> >-Aron
>
> Given a file
>
> Foo
> ---
> #!<interpreter> <options>
>
> the kernel changes the command line
>
> Foo <args>
>
> to
>
> <interpreter <options> Foo <args>
>
> Once you know that all should be clear.
>
> Hint: the -f option in csh takes the next "word" as the name of the file
> to run. The first verstion gives "csh -fb blah args" while the second
> gives "csh -f -b blah args" and csh tries to run the script "-b".
>
> As far as I know all unices (?) do it this way.
I think that you are wrong. From csh(1) on Solaris:
-f Fast start. Read neither the .cshrc file, nor the
.login file (if a login shell) upon startup.
>From tcsh(1) on Linux:
-f The shell ignores ~/.tcshrc, and thus starts faster.
At the command line:
kribi:~$ tcsh -f -b
> echo hi
hi
Thanks for the response.
-Aron
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu