Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!jsq
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.unix
Subject: Re: Shell standardization (for c.std.unix)
Message-ID: <17400@cs.utexas.edu>
Date: 23 Jan 91 23:57:04 GMT
References: <17011@cs.utexas.edu> <17065@cs.utexas.edu> <17155@cs.utexas.edu>
Sender: jsq@cs.utexas.edu
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 16
Approved: jsq@cs.utexas.edu (Moderator, John S. Quarterman)
X-Submissions: std-unix@uunet.uu.net

Submitted-by: gwyn@smoke.brl.mil (Doug Gwyn)

In article <17155@cs.utexas.edu> jack@cwi.nl (Jack Jansen) writes:
>I don't see any problem in the shell reading the first line and
>checking it for #!/bin/sh.

Shells that have done this (e.g. some csh implementations on UNIX System V)
have definitely caused problems.  For example, Most of my shell scripts
start with #!/usr/5bin/sh to ensure System V semantics on BSD systems;
however, on a genuine UNIX System V system I was expecting the script to
be interpreted by /bin/sh (even if executed by csh).  We discovered that
some overly-"helpful" implementations of csh on System V, however, went
ahead and tried to find /usr/5bin/sh, which of course made the execution
fail.

Volume-Number: Volume 22, Number 80