Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 16 Oct 2002 05:31:24 -0400
From:	David T-G <davidtg-bug-fileutils AT justpickone DOT org>
To:	FileUtils bugs <bug-fileutils AT gnu DOT org>
Cc:	Andrei Cernea <acernea AT cedara DOT com>,
	"CygWin Users' List" <cygwin AT cygwin DOT com>
Subject:	Re: chmod
Message-ID:	<20021016093124.GH84133@justpickone.org>
Reply-To:	"CygWin Users' List" <cygwin AT cygwin DOT com>,
	Andrei Cernea <acernea AT cedara DOT com>
References:	<880E371DA312D6119BFD00B0D02090C4496CA1 AT dinobot>
Mime-Version:	1.0
In-Reply-To:	<880E371DA312D6119BFD00B0D02090C4496CA1@dinobot>
User-Agent:	Mutt/1.4i

--pLlCf/bEWtYPubJE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Andrei --

=2E..and then Andrei Cernea said...
%=20
% Hi!
%=20
% I am using Cygwin 2.05. I am emailing you because of this:
%=20
% =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
% > chmod --help
=2E..
%=20
% Report bugs to <bug-fileutils AT gnu DOT org>.
% =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
%=20
% I noticed that in order for a file to have x rights on windows it needs to
% have executable extension. That is, if I have a script file with no
[snip]

Well, yes and no...  If it has a .exe or .com or .bat extension, then
it's considered obvious that it should be executable and so the x bit is
set for you.  As I understand it, if you want to be able to run a shell
script without having to use

  bash /path/to/script

then you'll need to set the x bit.  IIRC there's a way to tell Windows
and the Cygwin DLL to recognize .sh extensions, just like it already
recognizes the other three, and then naming your shell scripts
appropriately will make them executable.  Note that I don't think that
this is the same as typical file extensions, but I could be wrong.  Then
you could tie .pl to perl and who knows what else, too.  Perhaps all
that's necessary to have the system honor the shebang line is the x bit;
it's been a while since I was an active cygwin reader.

The bottom line is that you should direct your question to the cygwin
mailing list, where I've sent a copy of this message (Hi, all! Long time,
no see :-) and to which I've directed followups.  Yes, the reporting
address is the bug-fileutils mailing list, but this isn't a bug but
instead a peculiarity of the cygwin environment.


HTH & HAND

:-D
--=20
David T-G                      * There is too much animal courage in=20
(play) davidtg AT justpickone DOT org * society and not sufficient moral courage.
(work) davidtgwork AT justpickone DOT org  -- Mary Baker Eddy, "Science and Health"
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!




--pLlCf/bEWtYPubJE
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE9rTHsGb7uCXufRwARAlZIAKClwciOfWY0QBxWnlDLvjlIfVCDPACfdnfJ
JPcbYkJAlvFFTmsp6P+EvkY=
=ckJC
-----END PGP SIGNATURE-----

--pLlCf/bEWtYPubJE--

- Raw text -