From: Andrey Repin <anrdaemon@yandex.ru>
To: Michael Enright <mike@kmcardiff.com>, cygwin@cygwin.com
Subject: Re: Multiple problems (probably) starting up new installation
Date: Mon, 22 Oct 2018 12:05:00 -0000 [thread overview]
Message-ID: <174350011.20181022150245@yandex.ru> (raw)
In-Reply-To: <CAOC2fq8U3u46d+oa1C4BO+rtG+0aEWCq0ZREAE_7S3XWFKe+gw@mail.gmail.com>
Greetings, Michael Enright!
>>
>> > ----rwx---+ 1 menright Mike Enright 0 Oct 21 15:02 CMakeLists.txt
>>
>> the "+" says that there's extended ACL present. So, nothing odd.
>>
> The Windows view of this set of permissions (070 plus whatever is in
> the rest of the ACL)
This is NOT "windows" view, this is Cygwin view.
For ACL, check getfacl <file>.
> seems to be that Windows programs can't do very
> much with this file.
See my previous note about setting noacl flag to increase interoperability
with native programs.
> So it's odd from that POV and I wonder if that was caused by my renaming the
> "Cygwin account".
I'm not clear on how exactly renaming was done, so can't comment.
> Using cacls I see the
> Windows username in some of the entries and I don't see the cygwin
> username in any. I know that I can get a workable ACL with chmod but I
> can see that executables built by the compiler are not executable,
> either by name from cygwin bash or by double click from Windows
> Explorer. This is the first few lines from cacls:
> $ cacls moneymaker
> C:\cygwin64\home\menright\moneymaker NULL SID:(DENY)(special access:)
> READ_CONTROL
> FILE_READ_EA
> FILE_WRITE_EA
> FILE_EXECUTE
> FILE_DELETE_CHILD
This is normal (documented) behavior for less-than-trivial permission setups.
However, without a full dump of cacls it's hard to judge correctness of the
ACL on a given file.
--
With best regards,
Andrey Repin
Monday, October 22, 2018 14:58:59
Sorry for my terrible english...
--
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:[~2018-10-22 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 22:25 Michael Enright
2018-10-21 22:50 ` Andrey Repin
2018-10-22 1:09 ` Michael Enright
2018-10-22 12:05 ` Andrey Repin [this message]
2018-10-22 14:43 ` cyg Simple
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=174350011.20181022150245@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=mike@kmcardiff.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).