From:	ld AT netrix DOT com (Long Doan)
Subject:	Re: what did I miss? #!.... doesn't work in bash
1 Nov 1996 07:20:51 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<327A08AE.2655.cygnus.gnu-win32@netrix.com>
References:	<Pine DOT LNX DOT 3 DOT 91 DOT 961030122503 DOT 3502I-100000 AT webnet DOT wn DOT com> <199610311912 DOT LAA04347 AT cygnus DOT com>
Mime-Version:	1.0
X-Mailer:	Mozilla 3.01b1 (X11; I; SunOS 5.4 sun4m)
Original-To:	David Jeffers <jeffers AT redrose DOT net>
Original-Cc:	"Bret A. Schuhmacher" <bas AT wn DOT com>, gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Still, the bang line must be interpreted in the other cases, like:
#!/usr/local/bin/perl, #!/bin/csh, or #!/usr/local/bin/tk. In these
cases, the first line is the only one that bash (or other shells) should
understand. In fact, bash will choke on (usable) scripts running under
those shells.

Long.


David Jeffers wrote:
> 
> >>>>> "Bret" == Bret A Schuhmacher <bas AT wn DOT com> writes:
> 
>     The bang "#!/usr/sh" line isn't really necessary for shell
>     scripts using Cygnus bash. I remember reading about a
>     "magic cookie" but all my scripts work with it or without it
>     on Win 95. NT Perl uses a BAT file to build an executable
>     so again it isn't necessary.
> 
>     For instance:
> 
>     #!/bin/sh                           <---not necessary?
> 
>     awk ' { print $1 } '
> 
> 
>     works fine since awk is in my PATH.
> 
>     I think the "#!/bin/sh" line in Cygnus simply means
>     "this is an executable" since I don't even have to
>     chmod +x after I write the scripts like I do in Linux...
[...]
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -