From: Brian Candler <B.Candler@pobox.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: attr vs. getfattr
Date: Fri, 8 Jun 2012 09:43:06 +0100 [thread overview]
Message-ID: <20120608084306.GC44864@nsrc.org> (raw)
In-Reply-To: <alpine.DEB.2.01.1206071959230.5568@trent.utfs.org>
On Thu, Jun 07, 2012 at 08:01:06PM -0700, Christian Kujau wrote:
> On Thu, 7 Jun 2012 at 21:54, Eric Sandeen wrote:
> > > I.e. "nothing" is printed. I understand there's "attr" specifically for
> > > XFS filesystems and at least it displays that there *is* an attribute
> > > stored, but it cannot get its value:
> >
> > By default it's looking at the user namespace. You want to look at security (or all) with -m:
>
> Aaargh! Namespaces...yes, of course. Thanks for reminding me and sorry for
> the noise.
I was recently bitten by this too, and I consider it a bug in the manpage.
-d, --dump
Dump the values of all extended attributes associated with path‐
name.
I'd say it's not unreasondable to read this and think that -d dumps *all*
extended attributes, because that's what it says.
Only if you read later do you find:
-m pattern, --match=pattern
Only include attributes with names matching the regular expression
pattern. The default value for pattern is "^user\\." ...
Regards,
Brian.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-06-08 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 12:26 attr vs. getfattr Christian Kujau
2012-06-08 2:54 ` Eric Sandeen
2012-06-08 3:01 ` Christian Kujau
2012-06-08 8:43 ` Brian Candler [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=20120608084306.GC44864@nsrc.org \
--to=b.candler@pobox.com \
--cc=lists@nerdbynature.de \
--cc=sandeen@sandeen.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox