X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 10 Mar 2010 17:47:15 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: setfacl fails to replace ACLs when given a pathname starting with a drive letter Message-ID: <20100310224715.GA24166@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <31b7d2791003101403t5ac23548m27dbc1e591ef1417@mail.gmail.com> <31b7d2791003101430x182fa852w2e7737b1a3617f81@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Wed, Mar 10, 2010 at 10:42:41PM +0000, Francis Litterio wrote: >DePriest, Jason R. writes: >> According to http://cygwin.com/cygwin-ug-net/using.html#using-pathnames, >> Cygwin supports both Win32 and POSIX file paths and they are >> translated internally on-the-fly as needed. > >Indeed. Cygwin has allowed pathnames to start with drive letters for as long as >I can remember. You might want to look at the release announcement for Cygwin 1.7.1. http://cygwin.com/cygwin-ug-net/ov-new1.7.html Specifically, the part that says: - Incoming DOS paths are always handled case-insensitive and get no POSIX permission, as if they are mounted with noacl,posix=0 mount flags. seems relevant. cgf -- 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