Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site plus5.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!lll-crg!dual!qantel!ihnp4!mgnetp!we53!busch!wucs!wuphys!plus5!hokey
From: hokey@plus5.UUCP (Hokey)
Newsgroups: net.unix
Subject: Re: Re: Failure to execute 'csh'-commands from 'make'
Message-ID: <831@plus5.UUCP>
Date: Sun, 11-Aug-85 00:32:09 EDT
Article-I.D.: plus5.831
Posted: Sun Aug 11 00:32:09 1985
Date-Received: Wed, 14-Aug-85 21:45:21 EDT
References: <291@oce-rd1.UUCP> <5433@fortune.UUCP> <824@plus5.UUCP> <275@kitty.UUCP>
Reply-To: hokey@plus5.UUCP (Hokey)
Organization: Plus Five Computer Services, St. Louis, MO
Lines: 24

In article <275@kitty.UUCP> peter@kitty.UUCP (Peter DaSilva) writes:
>> [ihnp4!plus5!hokey]
>> In article <5433@fortune.UUCP> olson@fortune.UUCP (Dave olson) writes:
>> >If you have one of the 'augmented' versions of make, S3, S5, (not sure
>> >how many others...) try setting 'SHELL=/bin/csh'.
>> 
>> This will, of course, render any bourne shell scripts inoperable, as *all*
>> shell scripts will be executed by csh.
>
>This is pure bs. If your login shell is csh, SHELL=/bin/csh. Csh knows about
>bourne shell scripts (that begin with anything but a #, or with #!/bin/sh),
>and calls the bourne shell to execute them.

Peter DaSilva, it has been a very long week.  

The only reason I am not calling you a Liar is because I do not know about S3.

Sounds to me like you are talking about a 4BSD system.  I based my statements
on S5.

I hereby apologize for this outburst.
-- 
Hokey           ..ihnp4!plus5!hokey
		  314-725-9492