X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 	tests=AWL,BAYES_00,SARE_SUB_ENC_UTF8,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Francis Litterio <flitterio AT gmail DOT com>
Subject: Re: setfacl fails to replace ACLs when given a pathname starting with  =?utf-8?b?CWE=?= drive letter
Date: Wed, 10 Mar 2010 22:42:41 +0000 (UTC)
Lines: 42
Message-ID: <loom.20100310T233552-556@post.gmane.org>
References: <loom DOT 20100310T223730-987 AT post DOT gmane DOT org> <31b7d2791003101403t5ac23548m27dbc1e591ef1417 AT mail DOT gmail DOT com>  	<loom DOT 20100310T231120-570 AT post DOT gmane DOT org> <31b7d2791003101430x182fa852w2e7737b1a3617f81 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: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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. <jrdepriest <at> gmail.com> 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.

> It also specifically mentions this:
> "POSIX operating systems (such as Linux) do not have the concept of
> drive letters. Instead, all absolute paths begin with a slash (instead
> of a drive letter such as "c:") and all file systems appear as
> subdirectories (for example, you might buy a new disk and make it be
> the /disk2 directory)."

Yes, but I'm not sure how that's relevant to the behavior of setfacl when given
a pathname starting with a drive letter.

> By the way, when you said "updating to the latest release" do you mean
> you upgraded a 1.5 installation to 1.7.1 or a 1.7.1 to some newer
> version of 1.7.1?

No, not that old.  I was upgrading from an installation I had done about 8
months ago.

This gets stranger.  Watch this:

  $ /bin/ls -l /cygdrive/c/temp/xyz
  -rwx------+ 1 littef Domain Users 6714 Mar  1 15:07 /cygdrive/c/temp/xyz
  $ /bin/ls -l c:/temp/xyz
  -rw-r--r-- 1 littef Domain Users 6714 Mar  1 15:07 c:/temp/xyz

Notice the '+' indicating additional ACLs on the file when a UNIX pathname is
used, but the '+' is missing when a drive-letter is used.  This also did not
used to happen.  It is as if the presence of drive letters is suppressing
awareness of ACLs within the Cygwin layer.

Anyone know if this was this done on purpose?
--
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