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: Sun, 02 Jun 2002 10:15:20 -0400
From: Tom Brown & Deb Burkey <tmbdab95 AT comcast DOT net>
Subject: newbie question: everything is executable
To: cygwin AT cygwin DOT com
Reply-to: tmbdab95 AT comcast DOT net
Message-id: <NEBBKKHDKLFPPMDMDBMKAEDNCBAA.tmbdab95@comcast.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal

Hello,
I've looked around the FAQ, guides, and web, but don't see the answer yet.
I just installed Cygwin on a Win98 box, but I've used UNIX for years.  The
guides say that chmod only lets you modify the +w attribute, and that the
mount table can determine the attributes for all files in the mounted tree.
However, every file I create in my $HOME (or below) is executable upon
creation.  E.g., if I do the following:
 $> cat > foo
 $> echo $PATH
 $> ctrl-D
and then type "foo", I get my path.  I am not doing a "source" on "foo",
just typing "foo". On any system I've used previously, text files are not
automatically executable - you can source them to exec their contents, but
to make them executable you had to give them the +x attribute.  How can I
remove the x attribute from file in my directory?  And prevent them from
creating with that attribute in the first place?

Thanks,
Tom



--
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/