Subject: Re: mysterious bash problem
From: [email-masked] ($Bill Luebkert)

19 Jan 1998 16:15:51 -0800
Message-ID: <[email-masked]>
References: <[email-masked]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Earnie Boyd <[email-masked]>
Cc: [email-masked], [email-masked]

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:[email-masked]
-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".