From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <13426df10708170600u40bd2dcat14f02aa7c192fb0e@mail.gmail.com> Date: Fri, 17 Aug 2007 06:00:41 -0700 From: "ron minnich" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] everything is a directory In-Reply-To: <46C4E86C.CD73F5D@null.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3e1162e60708161349r56c8fd56sfdf6c560b91a3f95@mail.gmail.com> <46C4E86C.CD73F5D@null.net> Topicbox-Message-UUID: ab76835c-ead2-11e9-9d60-3106f5b1d025 On 8/17/07, Douglas A. Gwyn 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