Path: utzoo!utstat!helios.physics.utoronto.ca!ists!yunexus!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!pacbell.com!pacbell!att!mcdchg!tellab5!richsun!beirne
From: beirne@richsun.reuter.com (Michael G. Beirne)
Newsgroups: news.software.b
Subject: Re: cnews on a 3B1 with ksh
Message-ID: <903@richsun.UUCP>
Date: 24 May 90 21:22:23 GMT
References: <1990May22.212714.6570@bagend.uucp> <2254@crdos1.crd.ge.COM>
Sender: news@richsun.UUCP
Organization: Rich Inc., Oakbrook,IL
Lines: 27

In article <2254@crdos1.crd.ge.COM> davidsen@crdos1.crd.ge.com (bill davidsen) writes:
>In article <1990May22.212714.6570@bagend.uucp> jan@bagend.uucp (Jan Isley) writes:
>
>| Given that all of the cnews files begin with '#! /bin/sh', why
>| do the processes blindly run off and do their /bin/ksh thing?  If you
>| are going to tell me to RTFM about why #! /bin/sh does not work on the
>| 3B1, please include the page number you found it on, okay?  I missed it.

	"A word beginning with a # causes that word and all following
	charactersup to a new-line to be ignored."
		page 2 "sh" man page in comments paragraph.

Now from the csh manual page:

     If the file is a text file,  and the  first line begins 
     with #!, the next word is taken to be the pathname of a
     shell  (or  command)  to  interpret  that script. 

So from this we see that "#! /bin/sh" is a csh feature and NOT a sh or ksh
feature. Furthermore this may be a operating system feature also, depending
on what exec does when it runs a text file.

Larry Walls scripts do a ": use /bin/sh" if "#! /bin/sh " doesn't work.
Your mileage may vary.

Michael G. Beirne
beirne@richp1.UUCP or beirne@richsun.cpg.trs.reuter.com