X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Tue, 29 Jul 2008 11:19:27 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Problems with file permissions and cp when running on Vista
Message-ID:	<20080729091927.GB29930@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4889B696 DOT 70304 AT teamwpc DOT co DOT uk> <4889ECCB DOT 2030805 AT cygwin DOT com> <488DA96E DOT 5060101 AT teamwpc DOT co DOT uk> <488E0CE9 DOT 80708 AT cygwin DOT com> <488ECB92 DOT 7040901 AT teamwpc DOT co DOT uk>
MIME-Version:	1.0
In-Reply-To:	<488ECB92.7040901@teamwpc.co.uk>
User-Agent:	Mutt/1.5.16 (2007-06-09)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Jul 29 08:49, Tom Quarendon wrote:
> Two issues as I see it.
> Firstly, cygwin doesn't appear to pick up that I have write access to the 
> file README.txt. The getacl output below doesn't list Authenticated Users. 
> I can't use vi to modify the file, but I can read the file using cat and so 
> on.

You can use vi.  You just have to write back with w!


Corinna

> Secondly, cp takes a source file that I can read and copies it to a target 
> file that I subsequently can't read. This seems inconsistent. Clearly 
> cygwin is taking notice of the access control list as well as the posix 
> permissions when doing something like cat, as the README.txt file has no 

Cygwin doesn't care, actually.  When you open a file, either it works
or it doesn't.  vim checks the permission bits to show the [readonly]
text in the status line and marks it as readonly.  That doesn't mean
you can't write it if the Windows permissons allow it.

> posix permissions, but I can cat it. However cp doesn't copy that access 
> control list information so the target file only gets a copy of the posix 
> permissions.

cp only copies POSIX permissions.  This is consistent with POSIX
semantics which states that when copying a file the POSIX ACL isn't
copied as well.  Having file permissions set for "authenticated users"
but not for the actual owner is Win32 semantics.  There's no 1:1
translation.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -