From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Files created in cygwin on fileshare no longer allow "delete" in NTFS
Date: Tue, 12 Dec 2017 09:17:00 -0000 [thread overview]
Message-ID: <a60c25d5-a2f1-facb-900c-286a42324e74@cygwin.com> (raw)
In-Reply-To: <542bb7543d814f55a9f2f02fa7fc6cad@knapheide.com>
On 12/11/2017 05:19 PM, Eric Duesterhaus wrote:
>>> How can I retain NTFS "delete" rights for my users and groups on
>>> files created by Cygwin?
<snip>
> Note that there are two differences:
> 1. Delete permission are now missing.
> 2. Inheritance has been disabled and all permissions that would have
> been inherited are on the file as explicit permissions, excepting "delete"
You haven't said yet how the M drive is mounted as far as Cygwin is
concerned. Is it using Cygwin ACLs or not? It looks to me like it is.
But if that doesn't explain what you're seeing, I would recommend using the
guidelines below with any follow-up to the list so we have some baseline
information and can eliminate anything obvious.
> Problem reports: http://cygwin.com/problems.html
--
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:[~2017-12-12 3:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 0:26 Eric Duesterhaus
2017-12-12 9:17 ` Larry Hall (Cygwin) [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-11 21:29 Eric Duesterhaus
2017-12-11 22:19 ` Jürgen Wagner
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=a60c25d5-a2f1-facb-900c-286a42324e74@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).