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
