Bourne Shell Comments Problem

[Peter da Silva]

In article <8567 at smoke.ARPA>, gwyn at smoke.ARPA (Doug Gwyn ) writes:
> In article <375 at stiatl.UUCP> meo at stiatl.UUCP (Miles O'Neal) writes:
> >A comment indicator in column1, line 1, indicates the script is
> >a csh script instead of sh.

> Any Bourne shell that acts this way is BROKEN.
> Nearly all Bourne shell scripts I have encountered in the past
> several years start with #.

You must not have used systems with the csh available then, since csh (not
sh) uses the first character to determine whether to pass the script off onto
the bourne shell. Some might ask whether this is broken, since after all anyone
writing csh scripts has to be off their nut, but it is a fact of life. If you
have csh, check your bourne shell scripts to make sure they're csh proof.

Once upon a time a system administrator who shall not be named put # at the
front of all the bourne shell scripts on one of the Berkeley machines. It
was not a pretty sight.
-- 
Peter da Silva  `-_-'  Ferranti International Controls Corporation.
"Have you hugged  U  your wolf today?"            peter at ficc.uu.net