🚀 go-pugleaf

In article <SHADOW.89Aug13081959@pawl.rpi.edu> shadow@pawl.rpi.edu (Deven T. Corzine) writes:
>FALSE.  If the magic number does not match, and there is no #!
>interpreter specified, the exec call assumes /bin/sh as an
>interpreter.  The syntax errors you get are bourne shell errors, from
>the shell execve() created, NOT your current shell.

>For example, if you have a csh shell script, and are using csh,
>executing the csh script will try to interpret it with sh unless you
>begin the file with "#!/bin/csh".  Only typing "source <file>" will
>make the current shell execute the commands.

NOT TRUE :-)
If you have a csh script and you are using the csh, a comment as the
first line will give you a csh interpretation. If you do not have a
comment as the first line you will invoke /bin/sh to execute the script,
which of course will fail since the script was a csh script (unless it
is echo hello :-) I will not generalize this behavior to all UNIX shells
, but I have found many that will pass a script without a comment on the
first line to /bin/sh; otherwise the {insert a name} shell will
interpret the script.

BTW, a comment is any line that begins with a #.


--
"One, you lock the target. Two, you bait the line. Three, you slowly
spread the net. And four, you catch the man."
UUCP: ...!gatech!uflorida!sun.ufnet.ufl.edu!misterx  
Internet: misterx@sun.ufnet.ufl.edu | vishnu@pine.circa.ufl.edu