Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <3B79574B.4040107@ece.gatech.edu>
Date: Tue, 14 Aug 2001 12:52:27 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
CC: cygwin-developers AT cygwin DOT com
Subject: Re: readonly, NTFS, and file metadata
References: <3B783E6E DOT 2546DF0 AT ece DOT gatech DOT edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Earnie Boyd wrote:


 > But, this only solves it for NTFS with ntsec set.  What about FAT?  I
 > think that it is wrong of automake maintainers to be so narrow minded.
 > I plan to join that discussion.

I finally got a response on *why* the distdir was chmod'ed '-R a-w' 
It's because the test is to see if a distribution (of the package you're 
automaking) will operate correctly if the sources are on a read-only 
medium.  Thus, preserve time stamps, but make sure EVERYTHING is read-only.

I'm not sure how this would interact on FAT drivers, or NTFS/nontsec. 
Its probable that 'cp -p' would just do its job and return without 
error, and automake would be none the wiser.  Maybe that's what cp -p 
should do -- just ignore the ENOACCESS that the SetFileTime() function 
returns?

One person on the automake list suggested:

 > Maybe I'm missing something, but my manual page for cp reads
 >
 >        -p, --preserve
 >               preserve file attributes if possible
 >
 > Doesn't `if possible' means cp should not complain is it does?

BTW, with NTFS/ntsec (Aug 11 snapshot), I can

mv foo bar

successfully, even if foo is -r--r--r-- (I own foo).

--Chuck