public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Marco Atzeri <marco.atzeri@gmail.com>, cygwin@cygwin.com
Subject: Re: Installer cannot write to Cygwin's /usr/local/etc
Date: Sun, 16 Feb 2014 09:09:00 -0000	[thread overview]
Message-ID: <343221677.20140216125720@yandex.ru> (raw)
In-Reply-To: <53007ADE.1050309@gmail.com>

Greetings, Marco Atzeri!

>>> However you can check the Windows ACL with
>>
>>> $ cd /usr/local
>>
>>> /usr/local
>>> $ getfacl bin
>>
>> I would say, if you want to see _windows_ permissions, you need to use cacls.
>> gerfacl only show POSIX approximation of windows permissions.
>>
>>

> correct.

> Curious however
>   NOTE: Cacls is now deprecated, please use Icacls.

> but the two provide a slight different outputs:

I have no access to my Win7 box right now (I've somehow managed to lock my
account while experimenting with `net user' command in the light of new Cygwin
functionality, and being swamped by ongoing work load decided to postpone
investigation... though it is probably worth a warning...)
What icacls says about "X" meaning? (That seems to be the only difference?)

(BTW, you can specify multiple objects for [i]cacls to inspect at once.)

>    $ Icacls etc
> etc GE-MATZERI-EU\0356EU:(F)
>      BUILTIN\Administrators:(RX)
>      Everyone:(RX)
>      CREATOR OWNER:(OI)(CI)(IO)(F)
>      CREATOR GROUP:(OI)(CI)(IO)(RX)
>      Everyone:(OI)(CI)(IO)(RX)

>   $ Icacls bin
> bin GE-MATZERI-EU\0356EU:(F)
>      BUILTIN\Administrators:(RX)
>      Everyone:(RX)
>      CREATOR OWNER:(OI)(CI)(IO)(F)
>      CREATOR GROUP:(OI)(CI)(IO)(RX)
>      Everyone:(OI)(CI)(IO)(RX)


> $ cacls etc
> E:\cygwin\usr\local\etc GE-MATZERI-EU\0356EU:F
>                          BUILTIN\Administrators:R
>                          Everyone:R
>                          CREATOR OWNER:(OI)(CI)(IO)F
>                          CREATOR GROUP:(OI)(CI)(IO)R
>                          Everyone:(OI)(CI)(IO)R


> $ cacls bin
> E:\cygwin\usr\local\bin GE-MATZERI-EU\0356EU:F
>                          BUILTIN\Administrators:R
>                          Everyone:R
>                          CREATOR OWNER:(OI)(CI)(IO)F
>                          CREATOR GROUP:(OI)(CI)(IO)R
>                          Everyone:(OI)(CI)(IO)R


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 16.02.2014, <12:50>

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

  reply	other threads:[~2014-02-16  9:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-16  2:35 Gerry Reno
2014-02-16  4:51 ` Andrey Repin
2014-02-16  5:40   ` Gerry Reno
2014-02-16  6:17     ` Andrey Repin
2014-02-16  8:46       ` Marco Atzeri
2014-02-16 17:09       ` Christopher Faylor
2014-02-16  7:35 ` Marco Atzeri
2014-02-16  7:35   ` Andrey Repin
2014-02-16  9:05     ` Marco Atzeri
2014-02-16  9:09       ` Andrey Repin [this message]
2014-02-16 10:31         ` Marco Atzeri
2014-02-16 17:39   ` Gerry Reno
2014-02-16 18:25     ` Gerry Reno

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=343221677.20140216125720@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.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).