public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Houder" <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-3
Date: Tue, 14 Apr 2015 16:32:00 -0000	[thread overview]
Message-ID: <e9ab557069048406daec796d781a60f5.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <20150414154527.GN7343@calimero.vinschen.de>

> On Apr 14 17:26, Houder wrote:
>> >        Everyone:(Rc,S,RA)
>> >
>> > The only reason I can think of is that the parent dir has default
>> > permissions which imply the mask value already.  So, what does
>> > `icacls . | cat' in this directory print?
>>
>> %% icacls . | cat
>> . NULL SID:(DENY)(Rc,S,REA,X,DC)
>>   Seven\Test:(F)
>>   Seven\None:(RX)
>>   Everyone:(RX)
>>   NULL SID:(OI)(CI)(IO)(DENY)(Rc,S,REA,X,DC)
>
> As I thought.  There's a mask value already in there which influences
> how the default permissions are inherited.  You created this dir with
> Cygwin 2.0 already, right?  Remove the masks with

You created this dir with Cygwin 2.0 already, right? Correct! I did not
occur to me to start all over again ...

>   $ setfacl -d m:,d:m: .
>
> and try again.
>
>>   CREATOR OWNER:(OI)(CI)(IO)(F)
>>   CREATOR GROUP:(OI)(CI)(IO)(RX)
>>   Everyone:(OI)(CI)(IO)(RX)
>
> This *should* work now.  I fear you have to remove the masks from
> all files and dirs created by Cygwin 2.0.  Sorry, but that's what
> testing is for ;}

No problem at all ...

Btw, I will only report back on this in case you are INcorrect above.

Henri


--
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

  reply	other threads:[~2015-04-14 16:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 16:10 Houder
2015-04-14  8:58 ` Corinna Vinschen
2015-04-14 14:18   ` Houder
2015-04-14 14:50     ` Corinna Vinschen
2015-04-14 15:01       ` Houder
2015-04-14 15:12         ` Corinna Vinschen
2015-04-14 15:26           ` Houder
2015-04-14 15:45             ` Corinna Vinschen
2015-04-14 16:32               ` Houder [this message]
2015-04-14 18:21                 ` Corinna Vinschen
2015-04-14 18:38                   ` Houder
2015-04-15  7:13                     ` Corinna Vinschen
2015-04-15  7:46                       ` Houder
2015-04-15  9:04                         ` Corinna Vinschen
2015-04-14 14:27   ` Achim Gratz
2015-04-14 14:52     ` Corinna Vinschen
2015-04-14 15:35       ` Achim Gratz
2015-04-14 15:53         ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2015-04-12 19:23 Corinna Vinschen
2015-04-12 21:19 ` Bryan Berns
2015-04-13  7:17   ` Corinna Vinschen
2015-04-13  7:32     ` Corinna Vinschen
2015-04-13 11:13     ` Bryan Berns

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=e9ab557069048406daec796d781a60f5.squirrel@webmail.xs4all.nl \
    --to=houder@xs4all.nl \
    --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).