Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Tue, 9 Oct 2001 13:22:50 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: "chmod a+x filename" shows no effect on W2K
Message-ID: <20011009132250.A25208@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3BC322CA DOT 37D62AB0 AT cportcorp DOT com> <3BC342AA DOT 11064 DOT EE176 AT localhost> <20011009125641 DOT B24952 AT redhat DOT com> <3BC330AD DOT 22A45E36 AT cportcorp DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3BC330AD.22A45E36@cportcorp.com>
User-Agent: Mutt/1.3.21i

On Tue, Oct 09, 2001 at 01:15:25PM -0400, Peter Buckley wrote:
>Feel free to suspect cockpit errors :-)
>
>But all I can say is that chmod didn't work, and then I made zero
>changes, and while I was sending emails to the list, chmod started
>working again.  The only possible change I made to my system was
>opening or closing IIRC an unrelated windows application.  Maybe that
>was it?

Who knows?  As I mentioned, since you are the only person experiencing
the problem, I don't think that is helpful to prematurely warn people
about the situation.

As an analogy, if I had a Honda Civic with a dead battery in my driveway,
it would not be appropriate for me to drive to the Honda dealership and
inform potential Honda buyers that "Hondas have a battery problem".

It could be that there was a battery problem with Hondas but the mere fact
that the battery was dead does not provide enough supporting evidence to
allow me to make this generalization.

Similarly, telling people that chmod doesn't always work because that seemed
to be what was happening in your case is not really helpful unless you've
some statistics indicating that this is not just a problem specific to you,
your system, your network, etc.

cgf

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