X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Francis Litterio Subject: Re: setfacl fails to replace ACLs when given a pathname starting with a drive letter Date: Wed, 10 Mar 2010 22:16:07 +0000 (UTC) Lines: 21 Message-ID: References: <31b7d2791003101403t5ac23548m27dbc1e591ef1417 AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) 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 DePriest, Jason R. gmail.com> writes: > On Wed, Mar 10, 2010 at 3:43 PM, Francis Litterio wrote: > > I notice that setfacl does not change the ACLs of a file when given a > > pathname starting with a drive letter (e.g., c:/temp/zzz), but it will work > > when given a UNIX-style pathname (e.g., /cygdrive/c/temp/zzz). Example > > below. Is this a known problem? > > I'm pretty sure it is more of a feature than a problem. > > The path of c:/temp/zzz doesn't have any meaning in POSIX. I suppose > we're lucky Cygwin supports that format for *any* actions. But it used to work. I noticed this after updating to the latest release. If the drive-letter form of the pathname is not acceptable to the tool, it should complain, but (like most Cygwin utilities) it probably doesn't care about the syntax of the pathname, as long as open(2) accepts it. -- Fran -- 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