From:	fjh AT cs DOT mu DOT OZ DOT AU (Fergus Henderson)
Subject:	Re: mysterious bash problem
16 Jan 1998 21:29:41 -0800 :
Message-ID:	<19980115121237.41005.cygnus.gnu-win32@mundook.cs.mu.OZ.AU>
References:	<19980113142530 DOT 20840 DOT qmail AT hotmail DOT com>
Mime-Version:	1.0
To:	Earnie Boyd <earnie_boyd AT hotmail DOT com>
Cc:	Ulrich DOT Lauther AT mchp DOT siemens DOT de, gnu-win32 AT cygnus DOT com

On 13-Jan-1998, Earnie Boyd <earnie_boyd AT hotmail DOT com> wrote:
> 
> Ulrich Lauther <ulrich DOT lauther AT mchp DOT siemens DOT de> writes:
> >
> >Let foo be a valid shell script (starting with a ":" in the first line,
> >BTW):
> 
> To execute a script the first non-blank line must begin with
> 
> #! /bin/sh
> 
> where /bin/sh is the path and shell you want to execute.

I think you're missing some history.  Using `:' in the first line to
identify a Bourne shell script (as opposed to `#', for a C-shell script)
actually predates the `#!' convention.

If gnu-win32 doesn't support execution of shell scripts starting with
`:', then this is a bug in gnu-win32.  It works fine with other Unix
systems, including Linux.

In any case, the form of the error message

> >bash.exe: ./foo: (null)

is clearly a bug.

-- 
Fergus Henderson <fjh AT cs DOT mu DOT oz DOT au>   |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>   |  of excellence is a lethal habit"
PGP: finger fjh AT 128 DOT 250 DOT 37 DOT 3         |     -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -