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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=F+gMm4iRAOIFEHwv
	GQdb4BdhzSj/f/FdsCuKdY4spidmAMKJRZudJxJ2CO7L+tF1LKoGCf6XIINYgtjJ
	1Ztj0WPaPf8St0pFvGD0NUEkBn1kEblCYwtw0yMt5ki8aeALN74tF1scZqPGl/O4
	/S8q91UvL6KLuXrWRcuijmCrlHc=
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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=wpNd//jJFm4rZal+y7gB+x
	XQDis=; b=xUMMRw2Edp7/Ieyqx5LrVmOAZbO9OBBfmZQ6TQsIcS1ubrdrG/pQUK
	Itn87LMeIwEyDblhiSith9wMIDakaDbCBpk0oxbjjHNVx8XH1n039qsi+1uwAsWR
	OHilC71AxXlHVEcm5VnqbuqTOx7nxJJi0voRDOi1xiBu7UAhOyHME=
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=4.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2 spammy=H*UA:Bat!, H*x:Bat!, H*F:D*yandex.ru, H*x:Home
X-HELO: smtp.ht-systems.ru
Date: Wed, 10 Feb 2016 21:21:34 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <1677082297.20160210212134@yandex.ru>
To: xnor <xnoreq AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: Issues with ACL settings after updating to the latest cygwin.dll
In-Reply-To: <emdc328b81-98cd-4ffa-b33c-c768c6a218cc@gaming>
References: <486885659 DOT 20160210050721 AT yandex DOT ru> <emdc328b81-98cd-4ffa-b33c-c768c6a218cc AT gaming>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, xnor!


>>It was always the case.
>>Permissions are NOT REQUIRED to be ordered in a specific way, but 
>>Explorer is
>>only capable of editing them in the only one way.
>>Means, Explorer is deficient. Explorer. Not Windows. Windows is 
>>perfectly
>>capable of handling the Cygwin ACL in the intended way.
> No, it really wasn't.

> The ACLs were fine until the change in the new Cygwin version. Now there 
> are 12 ACL entries, all non inherited / inheritance is broken, for each 
> file...

That's normal POSIX behavior.
If you want Windows behavior, mount your outside-Cygwin FS with noacl flag.


-- 
With best regards,
Andrey Repin
Wednesday, February 10, 2016 21:20:45

Sorry for my terrible english...


--
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