Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3981EF79.D641E288@cygnus.com> Date: Fri, 28 Jul 2000 22:39:21 +0200 From: Corinna Vinschen Reply-To: cygwin X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: de, en MIME-Version: 1.0 To: Matthew Smith CC: Cygwin Subject: Re: sh problem References: <001b01bff8ca$f3dfdcc0$3c5350d8 AT guinness> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Matthew Smith wrote: > > I'm having some problems with sh under windows 2k. It seems if I try > writing a script that references ".", as in: > > #!/bin/sh > > # access some other shell script > ./myscript.sh > > This will fail under windows 2k, but works fine under NT 4. Is this a known > problem? There's no difference between NT and W2K which might explain that. Are you sure that you have identical settings? For example if you are using ntsec on W2K while not on NT that could be a reason. When not using ntsec, the file is identified as executable by it's magic number `#!'. When ntsec is on, it is executable only if the executable bit is set in it's security descriptor. Just a hint, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT sources DOT redhat DOT com Red Hat, Inc. mailto:vinschen AT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com