Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!altos!megadon!clp
From: tag@mtunf.ATT.COM (Tom Gillespie)
Newsgroups: comp.unix
Subject: Re: Shell scripts starting with "#"
Summary: not in AT&T System V
Message-ID: <2225@megadon.UUCP>
Date: 17 Oct 90 18:30:29 GMT
References: <3695@zorba.Tynan.COM> <2136@megadon.UUCP>
Sender: clp@megadon.UUCP
Organization: AT&T BL Middletown/Lincroft NJ USA
Lines: 29
Approved: clp@megadon.UUCP

In AT&T System V Release 3 for 3B2, neither

#!/bin/sh

nor

: use /bin/sh

will force Bourne shell execution; Korn shell Version 11/16/88 simply ignores
either one. (csh does not exist for 3B2 as far as I know).

For 6386, which does have csh,

: use /bin/sh

works reliably; again, Korn shell (same version) ignores it.

My favorite workaround:

(alias) >/dev/null 2>&1 && exec /bin/sh $0 $@

since 'alias' is a built-in command in ksh.  This is the test that Larry Wall's
metaconfig builds in to the Configure script to warn ksh users that Bourne
shell should probably be used instead.


Tom Gillespie
tag@mtunf.att.com
(201) 576-2338