From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <198ff93d3223123a0e103cbcc4755bc4@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] everything is a directory
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 17 Aug 2007 09:24:26 -0400
In-Reply-To: <13426df10708170600u40bd2dcat14f02aa7c192fb0e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: ab7a8948-ead2-11e9-9d60-3106f5b1d025

hey, how do you grep for stuff in extended attributes?

- erik


> On 8/17/07, Douglas A. Gwyn <DAGwyn@null.net> wrote:
>> What do you mean by "extended attributes"?
>> I haven't noticed them on the Unix systems I use.
>>
> maybe I'm missing the question, but on my linux:
> 
> man -k extended | grep attrib | wc
>     21     183    1417
> libattr             (rpm) - Dynamic library for extended attribute support
> fgetxattr [getxattr] (2)  - retrieve an extended attribute value
> flistxattr [listxattr] (2)  - list extended attribute names
> (etc. It's a lot like read but, as usual, it needs  a new set of
> system calls ... 5 of them.
> And ls can't show them,  but ... we have getfattr/setfattr
>        The output format of getfattr -d is as follows:
>                1:  # file: somedir/
>                2:  user.name0="value0"
>                3:  user.name1="value1"
>                4:  user.name2="value2"
>                5:  ...
> 
> 
> it's everywhere. But it was too hard to put in in some normal way, so
> it went in from the side.
> 
> ron