From: Jim Meyering <jim@meyering.net>
To: selinux@tycho.nsa.gov
Subject: cp: --preserve={context,xattr,acl}
Date: Fri, 18 Aug 2006 20:03:02 +0200 [thread overview]
Message-ID: <87veop2a7d.fsf@rho.meyering.net> (raw)
Currently, upstream cp can selectively preserve a few different attributes.
>From the documentation:
`-p'
`--preserve[=ATTRIBUTE_LIST]'
Preserve the specified attributes of the original files. If
specified, the ATTRIBUTE_LIST must be a comma-separated list of
one or more of the following strings:
`mode' ...
`ownership'
`timestamps'
`links'
`all'
Using `--preserve' with no ATTRIBUTE_LIST is equivalent to
`--preserve=mode,ownership,timestamps'.
In the absence of this option, each destination file is created
with the permissions of the corresponding source file, minus the
bits set in the umask and minus the set-user-ID and set-group-ID
bits. *Note File permissions::.
The SELinux patches add "context" to the list.
and upstream treats ACLs like "mode".
However, with XATTR support, I may well add two more: "xattr" and "acl".
But then there'd be overlap between --preserve=xattr and --preserve=context,
Since I presume the latter subsumes the former. Right?
So if both were specified on a selinux-enabled system,
would there be any point in doing anything XATTR-specific?
What do you think?
Jim
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2006-08-18 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 18:03 Jim Meyering [this message]
2006-08-18 18:30 ` cp: --preserve={context,xattr,acl} James Antill
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=87veop2a7d.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.