| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: attr vs. getfattr |
| From: | Christian Kujau <lists@xxxxxxxxxxxxxxx> |
| Date: | Thu, 7 Jun 2012 20:01:06 -0700 (PDT) |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <4FD16983.5090901@xxxxxxxxxxx> |
| References: | <alpine.DEB.2.01.1206070508580.5568@xxxxxxxxxxxxxx> <4FD16983.5090901@xxxxxxxxxxx> |
| User-agent: | Alpine 2.01 (DEB 1266 2009-07-14) |
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. > A lot of manpage reading and intuition-following and namespace-remembering. > ;) Will do! C. -- BOFH excuse #79: Look, buddy: Windows 3.1 IS A General Protection Fault. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: attr vs. getfattr, Eric Sandeen |
|---|---|
| Next by Date: | [PATCH 0/9] xfs: discontiguous directory buffer support, Dave Chinner |
| Previous by Thread: | Re: attr vs. getfattr, Eric Sandeen |
| Next by Thread: | Re: attr vs. getfattr, Brian Candler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |