Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Message-ID: <3B7A8D81.102F7115@yahoo.com>
Date: Wed, 15 Aug 2001 08:56:01 -0600
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: CD List <Cygwin-Developers AT Cygwin DOT Com>
MIME-Version: 1.0
To: CD List <Cygwin-Developers AT Cygwin DOT Com>
Subject: Re: Automake 1.4l released
References: <3B79D55F DOT 9010300 AT ece DOT gatech DOT edu> <CAEGKOHJKAAFPKOCLHDIMEKKCGAA DOT tim DOT van DOT holder AT pandora DOT be> <20010815130538 DOT T17709 AT cygbert DOT vinschen DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Corinna Vinschen wrote:
> 
> The problem is only raised when using NTFS security to get POSIX
> compliant file attributes (that's called `ntsec' in Cygwin). It's
> no problem on FAT, FAT32 or even on NTFS if `ntsec' isn't used.
> 

Hmm...  I tested yesterday and I'm not using ntsec and have no
/etc/passwd or /etc/group file.  I still get the permission denied with
  touch /tmp/tmptouch
  chmod a-w /tmp/tmptouch
  touch /tmp/tmptouch
command sequence. `uname -a' gives
  CYGWIN_NT-4.0 DU211344 1.3.2(0.39/3/2) 2001-05-20 23:28 i686 unknown

> 
> I have changed `utime(s)' in the current developers version of Cygwin
> a few minutes ago. On NT/W2K it opens the file now claiming only
> FILE_WRITE_ATTRIBUTES instead of GENERIC_WRITE as desired access.
> That works for a simple reason. Even if the owner has no write
> access to the file's data, (s)he always has write access to the
> file's attributes, extended attributes and security descriptors
> (which altogether are the sum of the file's metadata).
> 

I'll try to test this soon.

> However, that doesn't change the need for automake to care for
> Cygwin versions prior to 1.3.3, apparently.
> 

Yep.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com