Xref: utzoo news.software.b:4839 unix-pc.general:5526
Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!pikes!aspen.craycos.com!sphere!ruck
From: ruck@sphere.UUCP (John R Ruckstuhl Jr)
Newsgroups: news.software.b,unix-pc.general
Subject: Re: cnews on a 3B1 with ksh
Message-ID: <286@sphere.UUCP>
Date: 25 May 90 18:57:33 GMT
References: <1990May22.212714.6570@bagend.uucp> <1990May23.190938.16011@shibaya.lonestar.org>
Followup-To: news.software.b,unix-pc.general
Organization: Private; Colorado Springs, CO
Lines: 20

In article <1990May23.190938.16011@shibaya.lonestar.org>, afc@shibaya.lonestar.org (Augustine Cano) writes:
> Some programs that use Larry Wall's Configure script test for this and
> tell you that "#! /bin/sh" doesn't work.  Apparently, what works is
> ": use /bin/sh".  I suppose one solution would be to replace all "#!..."
> with ": use ..."

With all due respect to Mr Wall, when I last used "Configure" on an AT&T
3B1, it informed me (correctly) that "#! /bin/sh" didn't work, but
misled me by saying that ": use /bin/sh" did work.  (This Configure was
bundled with rn patchlevel ?40?)

Isn't it easy to test?  Invoke a script like
    : use /bin/sh	# or whatever you think *might* work
    ps
from whatever shells you hope will respect that first line, and examine
output.  This is how I proved to myself that ": use /bin/sh" doesn't 
work with the Korn Shell I use on the 3B1.
-- 
John R Ruckstuhl, Jr	UUCP: sphere!ruck (or hplabs!hp-lsd!sphere!ruck)
			DOMAIN: ruck%sphere@hp-lsd.cos.hp.com