X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,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:50:58 +0000 (UTC) Lines: 11 Message-ID: References: <31b7d2791003101403t5ac23548m27dbc1e591ef1417 AT mail DOT gmail DOT com> <31b7d2791003101430x182fa852w2e7737b1a3617f81 AT mail DOT gmail DOT com> <4B982163 DOT 8030906 AT redhat 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 Eric Blake redhat.com> writes: > Yes, this is on purpose. Use of a drive letter says that you DON'T want > POSIX path processing, therefore, you are also giving up ACL processing. > Moral of the story - don't expect drive letters to do what you want. > Use POSIX paths. Thanks, Eric. I just wanted to be sure this wasn't a bug. -- 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