public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Rainer Blome" <rainer.blome@gmx.de>
To: cygwin@cygwin.com
Subject: Aw: Re: chmod failed: Invalid argument
Date: Thu, 28 Jan 2016 17:23:00 -0000	[thread overview]
Message-ID: <trinity-1207f321-8a47-46bf-99f9-9c2eb5b08d91-1453997213459@3capp-gmx-bs39> (raw)
In-Reply-To: <20160128144429.GC27369@calimero.vinschen.de>

> Corinna Vinschen wrote 2016-01-28 15-44:
> On Jan 28 15:24, Rainer Blome wrote:
>
> The "In-Reply-To" is still missing in your mails, so you're invariably
> breaking threading.  T'would be nice if you could make your mailer
> behave :)

This is the first time that I have a mail to reply to,
hope the threading is preserved now.
 
> > > Corinna Vinschen wrote:
> > > On Jan 28 01:27, Christopher Cobb wrote:
> > >> Or maybe chmod is broken, like it is on my machine:
> > >> $ chmod 777 x
> > >> chmod: changing permissions of âxâ: Invalid argument
> > 
> > > Can you please send the icacls output of the current directory and
> > > the icacls out for the file x?
> > 
> > Here are the icacls outputs for the test case:
> > 
> > $ umask
> > 0027
> > 
> > $ mkdir bar
> > $ cd bar
> > $ icacls .
> > . hostname\username:(I)(OI)(CI)(F)
> 
> This... doesn't look like an ACL created by Cygwin.

----
$ type mkdir
mkdir is hashed (/usr/bin/mkdir)
$ md5sum /usr/bin/mkdir
25471314acd68f352523ba17eafbb7f9 */usr/bin/mkdir
----

> If you're running Cygwin 2.4.1,

CYGWIN_NT-6.1 hostname 2.4.1(0.293/5/3) 2016-01-24 11:26 x86_64 Cygwin

> the acl should always at least contain ACEs for the
> default POSIX perms, plus a NULL ACE:
> 
> foo NULL SID:(DENY)(Rc,S)
>     VINSCHEN\corinna:(R,W,D,WDAC,WO)
>     VINSCHEN\vinschen:(R)
>     Everyone:(Rc,S,RA)

In Windows Explorer -> `bar` -> RMB -> Properties -> Security ->
Advanced, I am told that it inherits ist permissions from `base`,
the parent of `bar`. (To be precise, it inherits from its
grandparent, but I assume that the length of the ancestor chain is
not important here.)

> For directories also inheritable default perms for "CREATOR OWNER" and
> "CREATOR GROUP".  Is that really a Cygwin mkdir?!?

As far as can see, yes, see above.

> And then, what about
> this unknwon group with gid 213?  What does
> 
>   $ getent group 213
> 
> print?  Something's weird here...

getent group 213; echo $?
2

--
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:[~2016-01-28 16:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 15:43 Rainer Blome
2016-01-28 16:11 ` Corinna Vinschen
2016-01-28 17:23   ` Rainer Blome [this message]
2016-01-28 18:43     ` Corinna Vinschen
2016-01-28 20:18       ` Rainer Blome
2016-01-28 21:47         ` Corinna Vinschen
2016-01-31 22:45           ` Rainer Blome
2016-02-08 14:29             ` Corinna Vinschen
2016-02-10 10:59               ` Rainer Blome
2016-02-10 11:37                 ` Corinna Vinschen

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=trinity-1207f321-8a47-46bf-99f9-9c2eb5b08d91-1453997213459@3capp-gmx-bs39 \
    --to=rainer.blome@gmx.de \
    --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).