Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ski.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!gymble!lll-crg!dual!ptsfa!ski!jmm
From: jmm@ski.UUCP (Joel M. Miller)
Newsgroups: net.unix,net.unix-wizards
Subject: "#! /bin/sh" vs ":"
Message-ID: <183@ski.UUCP>
Date: Sat, 27-Apr-85 01:55:46 EDT
Article-I.D.: ski.183
Posted: Sat Apr 27 01:55:46 1985
Date-Received: Mon, 29-Apr-85 06:24:10 EDT
Reply-To: jmm@ski.UUCP (Joel M. Miller)
Organization: Smith-Kettlewell Institute, S.F., CA.
Lines: 23
Xref: linus net.unix:3745 net.unix-wizards:10131

There are at least 2 ways of indicating to csh that a Shell script
should be interpreted by sh: begin the file with:

	#! /bin/sh

or with any character other than "#", such as:

	:

These two ways are not equivalent, but I can't characterize the
difference.  The first sometimes causes commands in the script
to fail with the error message "restricted", and produces a funny
command line in ps -f:

	file file

These are cured by ":".

But what's really happening here?
-- 
Joel M Miller; Smith-Kettlewell Institute of Visual Sciences
2232 Webster St; San Francisco CA 94115; 415/561-1703
dual!ptsfa!ski!jmm    OR    {ucbvax,dual,sun}!twg!ski!jmm