Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
From: "Kris Thielemans" <kris.thielemans@csc.mrc.ac.uk>
To: "CygWin Users' List" <cygwin@cygwin.com>,
   "Andrei Cernea" <acernea@cedara.com>
Subject: RE: chmod
Date: Wed, 16 Oct 2002 11:38:27 +0100
Message-ID: <NBBBKKHEOHOEPNCALMIGKEAKDIAA.kris.thielemans@ic.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <20021016093124.GH84133@justpickone.org>

Hi Andrei,

we see only part of your problem here. However, if you're asking on how to
make cygwin recognise that a shell script is executable, you should put
#! /bin/sh
as first line in the script. No chmod necessary (This is a FAQ actually).
(I don't know if chmod would work/is necessary with the ntsec feature
enabled. Hopefully someone else can clarify this and put it in the
FAQ/User's guide)

Kris Thielemans
(kris.thielemans <at> ic.ac.uk)
Imaging Research Solutions Ltd
Cyclotron Building
Hammersmith Hospital
Du Cane Road
London W12 ONN, United Kingdom

web site address: http://www.irsl.org/~kris
>
> Andrei --
>
> ...and then Andrei Cernea said...
> %
> % Hi!
> %
> % I am using Cygwin 2.05. I am emailing you because of this:
> %
> % ============================================
> % > chmod --help
> ...
> %
> % Report bugs to <bug-fileutils@gnu.org>.
> % ============================================
> %
> % 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
> --
> David T-G                      * There is too much animal courage in
> (play) davidtg@justpickone.org * society and not sufficient moral courage.
> (work) davidtgwork@justpickone.org  -- Mary Baker Eddy, "Science
> and Health"
> http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf
> Qrprapl Npg!
>
>
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/