X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=wWWmU3DmYhgOgugYiAf2XzRdfJ6RF2teyN1f4C0WlLU83OfCWmXAJ
	2yXXnlZYZZEguNPXStNz4P6haQ8v6NLam35mEiPbo61UkRkWwUQ9Jf5JeovDEsAR
	HA/pNUHCAdFFTq1iUbQfaJzjKsTFeQPsFRzPNqzGS3AALJ+Sg/v6yg=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=KP+1GFH7BZ3l6yG6YaDNr4LkzX8=; b=QMFjpBUZ/s1xm0J+U9l/1pcPmsKI
	OpSPxbDth0NO7+IezJh0oAw+Aph2fIPGE2C/xvM2uTWHBg+uIb8kfMHT+tssCh01
	EtU1DgWsc2BdIBjBkMAZz9U4sjJM+U4ykMBVEucqX27tFrSRhsj6CkfWUUW4y6Sf
	b6QT1JuoPQMCCX0=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Tue, 10 Feb 2015 10:35:24 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: ls not in sync with chmod (weird problems with file permissions)
Message-ID:	<20150210093524.GF15989@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAO=+TS98PdSMcxRoX1RgF3kawZ-XCTE6LKzGYkFEFuCrTtB54A AT mail DOT gmail DOT com> <54D9188B DOT 4080508 AT towo DOT net> <CAO=+TS_xO_X044ZOkXUK-C1F98H6_D1PqujG9qiS_DzqMBNvhQ AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CAO=+TS_xO_X044ZOkXUK-C1F98H6_D1PqujG9qiS_DzqMBNvhQ@mail.gmail.com>
User-Agent:	Mutt/1.5.23 (2014-03-12)

--FoLtEtfbNGMjfgrs
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Feb  9 22:50, diod lightbulb wrote:
> On 9 February 2015 at 21:28, Thomas Wolff <towo AT towo DOT 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 chm=
od
> > gets changed to behave like on Linux.
> > ------
> > Thomas
>=20
> Hi Thomas,
>=20
> 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?
>=20
> 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?

Guys, I'm aware that the new ACL group/mask behaviour gives a little
trouble.  Before you turn your Windows system upside down, let's
discuss how to go forward.  See my mail at

  https://cygwin.com/ml/cygwin/2015-02/msg00197.html

and chime in so we can puzzle out the best solution for the future.
Ideally I(*) only have to implement this once ;)


Corinna


(*) Well, ideally somebody takes a heart and helps coding...


--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--FoLtEtfbNGMjfgrs
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJU2dDcAAoJEPU2Bp2uRE+gzvcQAJblH6+BVMh/7tdoffwQj9lS
LgY7ZULpow/aiyXMPcHcGNl+XY5aLWbfdYgAruQukmi7PLq0mdpb2J9EMx3x3hZA
opdHgRawBFHh0yJOyYCt5+4QNs34Lf0oMTL+w3cu4BjwMnDa/fU2in/zMmElinjH
r6PZ7etxw8bCtcmwytyZNeiM5NuVmZ9Fa9JBpBX5o3xa+unLYPl0g2dkgvRLqzU5
2rjj5NOsGgZUwoChUz4g1GhqNAhtjHkEfZdg8eeCFC3P1iNkGAt1BT1U/YIB2MAj
QkRiMpcTCv7KSqUbrCPY7bPWkTh3bqHpvCetN9cPq/5+j6NdQ9DyJKKl7aKUZxXs
aIMOhaNfPl+rwoHNTpsKALIFV21FbhhY+1inkSoGIADd2XRZrogT5/D0kBxTKVsD
1u7JUmflchwZwhvhnZYsl+v8Z+rPRfJlQcXrwiwZMQxilBEWygjwUivFcUWd/hHr
DNAVjazRGdaFNCibK8Kox/XyBhdQVg0a7by5UIYHULWGacC5jI7e8Z7a7oyRKpe4
WQFnF8fiXREShhS3YMsSXPhRQMpfzFOFucYMDHZx+vz32hTWKnivZR09qnp5GE+d
CzM6f6tpzqnQzM+LtiUlaDIRWCMCa4JS6cGgrvyaxsg9rc7as9hFW7h5dmDXsHSr
aYCRL4LSYrNVtAGAzxsm
=UHyz
-----END PGP SIGNATURE-----

--FoLtEtfbNGMjfgrs--

- Raw text -