From: Andreas Gruenbacher <agruen@suse.de>
To: Timothy Shimmin <tes@sgi.com>
Cc: linux-xfs@oss.sgi.com, Gerald Bringhurst <gbringhurst@novell.com>,
Brandon Philips <bphilips@suse.de>
Subject: Re: acl and attr: Fix path walking code
Date: Sat, 10 Nov 2007 22:36:52 +0100 [thread overview]
Message-ID: <200711102236.53298.agruen@suse.de> (raw)
In-Reply-To: <47340ECC.4000205@sgi.com>
On Friday 09 November 2007 08:39:56 Timothy Shimmin wrote:
> You mention -L/-P is like chown.
> However, -P for getattr isn't about not walking symlinks
> to directories,
> it's about skipping symlinks altogether, right?
Hmm, -L and -P define which files and directories are visited, and -h defines
whether we are looking at symlinks or the files they point to. The two
concepts are orthogonal. -P is not about skipping symlinks, only about not
recursing into them.
You can do this (as root), for example:
$ ln -s dead link
$ setfattr -h -n trusted.name -v value link
$ getfattr -h -m- -d -P link
# file: link
trusted.name="value"
With "getfattr -R -P -h" you get a physical dump of all attributes ("a real,
complete dump"), while with "getfattr -R -L" you get a logical dump that
treats all symlinks as the files they point to. I somewhat doubt that -L
with -h has real value.
Thanks,
Andreas
prev parent reply other threads:[~2007-11-10 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 17:58 acl and attr: Fix path walking code Andreas Gruenbacher
2007-11-09 5:41 ` Timothy Shimmin
2007-11-10 20:52 ` Andreas Gruenbacher
2007-11-14 5:08 ` Timothy Shimmin
2007-11-20 5:11 ` Timothy Shimmin
2007-11-23 12:24 ` Andreas Gruenbacher
2007-11-09 7:39 ` Timothy Shimmin
2007-11-10 21:36 ` Andreas Gruenbacher [this message]
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=200711102236.53298.agruen@suse.de \
--to=agruen@suse.de \
--cc=bphilips@suse.de \
--cc=gbringhurst@novell.com \
--cc=linux-xfs@oss.sgi.com \
--cc=tes@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox