This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: mysterious bash problem
- To: Earnie Boyd <earnie_boyd at hotmail dot com>
- Subject: Re: mysterious bash problem
- From: "$Bill Luebkert" <dbe at wgn dot net>
- Date: Sat, 17 Jan 1998 22:49:09 -0800
- CC: Ulrich dot Lauther at mchp dot siemens dot de, gnu-win32 at cygnus dot com
- Organization: DBE Collectibles
- References: <19980114131619.11340.qmail@hotmail.com>
Earnie Boyd wrote:
>
> It might help to see foo. UNIX shell scripts must begin with #!
> /path/to/shelltoexecute.
Not true!
> If you were on UNIX you would then have to set
> the executable bit on the file properties/permissions.
Depends on how you initiate the script. True if you execute by using
the script name (eg: "foo.sh" for the script foo.sh). You could also
source the script or use it as an argument to the shell.
> The cygwin.dll
> layer tries to mimick as much of UNIX as it can. Since the file doesn't
> begin with #! you will not see the executable bit set on the permissions
> as that is how it determines if the file is executable.
>
> I have noticed that the gnu-win32 bash will try to execute the script
> even without the #! indicator. This is a bug as bash should error
> without this indicator. For more information see the bash.info file.
Correct behavior, since the shebang line is not required.
--
,-/- __ _ _ $Bill Luebkert
(_/ / ) // // DBE Collectibles
/ ) /--< o // // http://www.wgn.net/~dbe/
-/-' /___/_<_</_</_ Mailto:dbe@wgn.net
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".