On Wed, Mar 10, 2010 at 10:42:41PM +, 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
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 wan
On 03/10/2010 03:42 PM, Francis Litterio wrote:
> 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
>
DePriest, Jason R. 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 l
> 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
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., /c
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 t
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?
--
Fran
$ /bin/ls -l zzz
-rw-r--r--+ 1 littef
8 matches
Mail list logo