reg@vaxine.UUCP (03/15/84)
<this line intentionally left non-blank>
There has been an excessive amount of discussion recently about making
sure that shell scripts are "automatically" executed by the correct shell. Along
with this has gone a lot of chastising of the #! construct (which, as an aside,
I happen to think is a nice feature and not at all inconsistent with the
407/410/413 magic number stuff exec(2) already did). If you are *really* upset
with using #! or are worried that it won't work on every system, here is what
you do:
exec /bin/my-own-personal-shell-and-the-hell-with-everyone-else <<EOF
<my shell file goes here>
EOF
I believe you will find the "exec" intrinsic in both the Bourne shell and the C
shell. (I don't know (nor care, but that is beside the point) about the Korn
shell.)
Can we change the topic, now that we have beaten this dead horse into
sub-atomic particles?
Rick Genter
Automatix Inc.
linus!vaxine!reglcc.bob@UCLA-LOCUS.ARPA (03/19/84)
From: Bob English <lcc.bob@UCLA-LOCUS.ARPA> Of course, you remembered to quote your shell file so that the proper program will be passed to your-own-personal-shell, and did so in a way that all shells will recognize. Didn't you? --bob--