From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: ls shows different permissions for the same file
Date: Thu, 13 Sep 2012 00:41:00 -0000 [thread overview]
Message-ID: <505122CC.3060306@cygwin.com> (raw)
In-Reply-To: <AB5C244567184949B9C73F32BBC4703704DD72DC@BL2PRD0410MB373.namprd04.prod.outlook.com>
On 9/12/2012 2:57 PM, Boemker, Tim wrote:
> Larry,
>
> Do you mean that, with a POSIX path, I get ACL-based permissions, but
> with Windows paths, I get just user-group-other permissions?
Not quite. The POSIX path will give you the correct mapping of Windows
ACLs into ugo plus any additional ACLS that don't map will show up with
the '+' indicator. With Windows paths, you get simple, hard-coded, ugo,
without any indication of further ACLs, if they exist.
> That sounds reasonable, but shouldn't they agree as far as they overlap?
> In the following example, for example, shouldn't they agree whether foo is
> writable by Domain Users?
No because with Windows paths Cygwin doesn't look at Windows ACLs. It
just reports a default set of ugo permissions.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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
next prev parent reply other threads:[~2012-09-13 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 19:05 Boemker, Tim
2012-09-13 0:41 ` Larry Hall (Cygwin) [this message]
2012-09-13 14:30 ` Boemker, Tim
2012-09-13 23:57 ` Larry Hall (Cygwin)
-- strict thread matches above, loose matches on Subject: below --
2012-09-12 12:47 Boemker, Tim
2012-09-12 17:40 ` Larry Hall (Cygwin)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=505122CC.3060306@cygwin.com \
--to=reply-to-list-only-lh@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).