X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A06AB2E.5030907@gmail.com> Date: Sun, 10 May 2009 11:23:42 +0100 From: Darren Syzling User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.7 ACLs References: <49F9A90B DOT 30807 AT gmail DOT com> <20090504092036 DOT GE21324 AT calimero DOT vinschen DOT de> In-Reply-To: <20090504092036.GE21324@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 Corinna Vinschen wrote: > Cygwin is a POSIX environment. The ACLs are set according to POSIX > rules, not according to Win32 rules. > > Thanks I'm not criticising Cywin's ACL behaviour just looking for guidance on anyone who has used 1.7 with existing Windows applications. In my case I wish to use the cygwin toolset but operate within the context of the Windows OS/Tools which clearly rely on Windows based ACLs and trying to find a reasonable workable approach to the problem. I'll read the mount table section you supplied and the other sections on cygwin's ACL behaviour. Darren -- 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/