🚀 go-pugleaf

   Date: 9 Feb 90 23:53:27 GMT
   From: milano!peyote!galew_a@cs.utexas.edu  (Andy Galewsky)
   Organization: Capital Area Central Texas Unix Society, Austin, TX
   Sender: bug-bash-request@prep.ai.mit.edu

   I hope I'm not just being stupid (it has happened before) but - when I am
   running BASH-1.04 and I try to execute a Bourne shell script - I can't get 
   /bin/sh to execute it -- BASH tries to do it. I have tried putting #!/bin/sh
   as the first line of the shell script - but BASH continues to try to execute
   it - itself. It doesn't seem right that I have to throw away all of my old
   shell scripts in order to run BASH. This is probably not a BASH bug - but just
   a problem with my understanding of how this works.

			   Thanks 
			    Andy Galewsky
			   Clinical Resource Systems
			   peyote!sneffels!andy
			   galew_a@peyote.cactus.org


System V machines don't pay attention to #! in the first line.  Their
fault, not yours.  If the system call exec () didn't exec the file, then
bash assumes that the file is a bash script.  Not a bad assumption, and
in fact, the same assumption that /bin/sh makes.

Brian