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=MegpRUWuQyUbS3rW dcgFImAmPQlzapS3+1ZtyqQz/ARDbj2k/luSXEUxhwyMum1v9f/AdPZgrdtlhhPy Y+LhUyJeetmKVGP73Qc9q0/GMV8vNAkbXxUZMg8NHTjJxCK53mbZS+Lim03foBot z0f3EqTPDa2jzx2NOSilMw1SI2k= 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=9ESuMNYRAE8y3p+qAfA0Bv Fdyq0=; b=YhT55xgEXJLNhcPyf595N/Lbu1lM8l7Ugi/ZUcS6og17eYRd4n7GbL inDhYYnHuE5u66VfG56Z55b5BrMFoEuNgsDKbzHBOfptm8PnYot9EhpnqQQkggRy SlsOr1R4ZI8ZlXtwrJDL+6fM6NrYm3u7JL0iOO8OKiiEXzsO13+rw= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=-0.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=english, H*F:D*yandex.ru, H*RU:192.168.1.10, H*r:ip*192.168.1.10 X-HELO: forward103j.mail.yandex.net Authentication-Results: smtp3p.mail.yandex.net; dkim=pass header.i=@yandex.ru Date: Fri, 27 Apr 2018 11:54:40 +0300 From: Andrey Repin Reply-To: cygwin AT cygwin DOT com Message-ID: <1823587349.20180427115440@yandex.ru> To: Ulli Horlacher , cygwin AT cygwin DOT com Subject: Re: umask problem: wrong permissions for new files In-Reply-To: <20180426143827.GA27620@rus.uni-stuttgart.de> References: <20180420100357 DOT GA21217 AT rus DOT uni-stuttgart DOT de> <6cd38c2e-2271-aaee-3263-babf905325c1 AT SystematicSw DOT ab DOT ca> <20180426143827 DOT GA27620 AT rus DOT uni-stuttgart DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Greetings, Ulli Horlacher! > On Fri 2018-04-20 (07:25), Brian Inglis wrote: >> Cygwin supports Windows ACLs as POSIX ACLs, which are also supported by >> Linux. Use setfacl to set similar default ACLs (DACLs) on a Linux >> directory, rerun your test there, and you should see similar results. > (How) can I completly remove ACLs from the cygwin files and directories? You CAN, yes. However, you will lose any way to access the files, as explained below. > The standard UNIX permissions are sufficent for my needs and much easier > to handle :-} "Standard POSIX" permissions are insufficient even for most basic operations. They survive only because removing them would cause even more harm, than letting them sit around. >> *Never* remove DACLs from any Windows directory which will *ever* be used >> with any non-Cygwin Windows program: /undefined behaviour/ will result. > Uuups... thanks for the warning! -- With best regards, Andrey Repin Friday, April 27, 2018 11:52:38 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