public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: Trying to create default ACL entries to match file ACL entries
Date: Tue, 04 Jun 2019 21:58:00 -0000	[thread overview]
Message-ID: <5CF6E997.70201@tlinx.org> (raw)
In-Reply-To: <4df43ab7-abc9-e0ae-e9c1-ace2c07da9d9@SystematicSw.ab.ca>

On 2019/06/04 14:26, Brian Inglis wrote:
> On 2019-06-04 13:59, L A Walsh wrote:
>   
>> lets see if this is more clear:
>> On 2019/06/04 12:44, Eliot Moss wrote:
>>     
>>> On 6/4/2019 3:34 PM, L A Walsh wrote:
>>>       
>>>> I am trying to create an entry for '/' (or '.' w/me sitting in '/')
>>>> where the default entries are the same as the file entries.
>>>>           ^^^^^^^
>>>> so tried doing:
>>>>    getfacl . | setfacl -d - .
>>>>         
>> Sorry, but am trying to get the 'file' entries (w/o the -d)
>> copied into the default.
>>     
>
> Not seeing -d, --default documented or supported in the code as an option flag
> under Cygwin: it is available under Debian/Ubuntu at least, and probably other
> Linux; 
Not to confuse things, but its under getfacl.

silly me, thinking setfacl might have the same flag
very confusing...
So need to getfacl to get access perms, then turn them into a form for
default acl...
Sigh...


--
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:[~2019-06-04 21:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 19:34 L A Walsh
2019-06-04 19:44 ` Eliot Moss
2019-06-04 19:59   ` L A Walsh
2019-06-04 21:26     ` Brian Inglis
2019-06-04 21:58       ` L A Walsh [this message]
2019-06-04 21:34 ` Chris Wagner
2019-06-04 22:11   ` Brian Inglis
2019-06-06 19:44   ` how do i create a trusted-installer? (was Re: Trying to create default ACL entries to match file ACL entries) L A Walsh

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=5CF6E997.70201@tlinx.org \
    --to=cygwin@tlinx.org \
    --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).