public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Trying to create default ACL entries to match file ACL entries
Date: Tue, 04 Jun 2019 19:44:00 -0000	[thread overview]
Message-ID: <ab8ce19f-5c2a-63f4-1685-d3174a1db216@cs.umass.edu> (raw)
In-Reply-To: <5CF6C7A8.6090902@tlinx.org>

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.

Ooooo ... not sure _I'd_ mess what / on a Windows system!

> I noticed the example give in the manpage for copying entries:
> 
> The special filename "-" indicates reading from stdin.
>         Note that you can use this with getfacl and setfacl to copy ACLs from
>         one file to another:
> 
>             $ getfacl source_file | setfacl -f - target_file
> 
> so tried doing:
> 
>    getfacl . | setfacl -d - .

I have no problem doing:

mkdir temp
getfacl . | setfacl -f - temp
getfacl temp | setfacl -f .
getfacl / | setfacl -f .

I didn't want to try setting things on /, but
you might:

cd /
mkdir foo
getfacl foo | setfacl -f - .

But I am not sure what foo would have as its permission, i.e., whether
they are what you want.

Regards - EM

--
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 19:44 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 [this message]
2019-06-04 19:59   ` L A Walsh
2019-06-04 21:26     ` Brian Inglis
2019-06-04 21:58       ` L A Walsh
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=ab8ce19f-5c2a-63f4-1685-d3174a1db216@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --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).