Path: utzoo!mnetor!uunet!littlei!intelisc!joel
From: joel@intelisc.UUCP (Joel Clark)
Newsgroups: comp.unix.questions
Subject: Re: csh and $SHELL variable conflicts.
Message-ID: <228@intelisc.UUCP>
Date: 4 Feb 88 01:10:54 GMT
References: <65200004@convexe> <3600007@hpiacla.HP.COM>
Reply-To: joel@intelisc.UUCP (Joel Clark)
Followup-To: comp.unix.questions
Organization: Intel Scientific Computer, Beaverton, OR
Lines: 27
Keywords: csh sh


I have ATT's Sys V/386 R3.0 V1.0 on an intel 80386 PC/AT bus type
machine.

We aquired a copy of csh through intel's Berkeley source license.
OTHERSH was set to /bin/sh before compiling it.
Shell scripts written with '#' as the first character are run by
/bin/sh EXCEPT when executed from a makefile.   make reads the
script and feeds it to the shell defined by $SHELL.

Is there a convention for shell and environment variables to define
the interactive shell and the batch shell differently?

Currently I `set shell=/bin/csh` and `setenv SHELL /bin/sh`

However in an attempt to emulate BSD job control I was investigating
`shl`  the SYS V shell layer facility and found it creates virtual
terminals running the shell defined in $SHELL.

This does note sweetly and cleanly allow me to provide our customers
with a csh environment with "job control" in a System V system.  Suggestions?

Joel Clark			            
Intel Scientific Computers		      
503-628-7732				     
joel@isc.intel.com			   
{tektronix}!ogcvax!intelisc!joel