DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=OL+dIBR
	9lOVcGnIYAnoL2X6ZSvfSUY/e66mhSVSCuhnkMYQGxR7IoCFjbuHBy0DRSASbMRH
	GUcZSRjOYBiA0xJ+Rj5VTkzsBUIugEYY1xAF4gIDeBcrQtT6jcuyQIlFOfqERcAJ
	oWigWnm/Fg13RaQIB1IdLmINssVMJC/KsatI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <54D9188B.4080508@towo.net>
References: <CAO=+TS98PdSMcxRoX1RgF3kawZ-XCTE6LKzGYkFEFuCrTtB54A@mail.gmail.com> <54D9188B.4080508@towo.net>
From: diod lightbulb <greendiod@gmail.com>
Date: Mon, 9 Feb 2015 22:50:29 +0100
Message-ID: <CAO=+TS_xO_X044ZOkXUK-C1F98H6_D1PqujG9qiS_DzqMBNvhQ@mail.gmail.com>
Subject: Re: ls not in sync with chmod (weird problems with file permissions)
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1

On 9 February 2015 at 21:28, Thomas Wolff <towo@towo.net> wrote:
> Am 09.02.2015 um 16:37 schrieb diod lightbulb:
>>
>> ...
>>
>> 1-  For pre-existing files/directories under /cygdrive/d and /cygdrive/e
>> All my file permissions that were correctly reported by ls -l as
>> rw-r--r-- became all of a sudden -rw-rwxr--+ ??? The same for
>> directories where all previously 755 dirs came back as drwxrwxr-x+
>>
>>
>> ...
>> % chmod 644 buggy
>> % stat -c " %a %u %g" buggy
>>   " buggy 674 1000 545
>>
>> Oooch, no change??? chmod used to work before today (BTW, same
>> behavior for pre-existing files: chmod has no effect).
>> ...
>
> See my mail about "group permissions". This would resolve nicely if chmod
> gets changed to behave like on Linux.
> ------
> Thomas

Hi Thomas,

Maybe so, I really didn't see the point of ACLs before, I'm just happy
with (used to?) plain POSIX. And up until now, the cygwin behavior was
OK with me. I must say (a somewhat big inconvenience but I didn't
complain) that I routinely chmod 644 all new files created by
non-cygwin apps (say new files downloaded with Mozilla). That's why I
asked earlier if there's an easy way to enforce file permissions 644
for any newly created file. Maybe through Windows but then what would
be the right corresponding Windows permissions to ensure them?

It's important for me that the files I care for are in Group Users as
my use case on this box is a Debian/Windows 7 dual-boot.  I have a
UserMapping file for drives D: and E: to try to get consistent
ownership on both. Another inconvenience right now is that the Group
given to newly created files from non-cygwin apps (again, one example
is a Mozilla downloaded file, another one is a Gimp newly created
file) seems to be None instead of Users for cygwin apps. I routinely
chgrp them. Is there a way to make sure that they belong to the Users
group from the start?

Regards,
Green

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