From: "Linda A. Walsh" <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: suse cp copies 'acls' and extended attrs....
Date: Wed, 13 Jul 2011 07:59:37 -0700 [thread overview]
Message-ID: <4E1DB2D9.4060900@tlinx.org> (raw)
I'm not sure if it is in mainline cp (would tend to guess it is likely),
but the default
cp -a mode will copy all file attributes now, as well, by default. (You
can turn it off, but
the default for -a(rchive) mode is to copy everything...)...
So you can use 'cp' now to copy xfs files around and not lose
capabilities, acls or other ext_attrs,
as well as rsync....
Just an FYI from someone who just found out recently -- it may be old
news...if so, sorry,
first I heard of it!
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2011-07-13 14:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E1DB2D9.4060900@tlinx.org \
--to=xfs@tlinx.org \
--cc=xfs@oss.sgi.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 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.