xfs
[Top] [All Lists]

Re: Portability of libattr

To: xfs@xxxxxxxxxxx
Subject: Re: Portability of libattr
From: petr.pisar@xxxxxxxx
Date: Fri, 11 Apr 2008 18:40:45 +0200
In-reply-to: <47FF7D47.40007@xxxxxxxxxxx>
Mail-followup-to: xfs@xxxxxxxxxxx
References: <20080409184103.GD20142@xxxxxxxxxxxxxxxxxxxxxx> <20080409185445.GA30834@xxxxxxxxxxxxx> <47FF7D47.40007@xxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.16 (2007-06-09)
On Fri, Apr 11, 2008 at 10:01:27AM -0500, Russell Cattelan wrote:
> I have not looked closely at the FreeBSD EA stuff so I don't know how
> different things are. I can't imagine they are that far off?
>
Unfortunatelly, I have no FreeBSD machine available now, but as I found in its
manual pages, they have splitted the names space and the rest of the EA name.
The namespaces are enumerated. So you can't just call
getxattr("user.mime_type', ...). Also they support reading EA from any
arbitrarry offset like Darwin. (Linux reads from first byte always). FreeBSD
API is little more rich.

> I thought the libattr code does compile on IRIX. There was an effort at one
> point to only have one usespace code base that worked on both linux and
> irix.
>
Great. Could you tell me which of these two APIs are the standard interface?
I'm a little confused about all the Linux code in libattr (like syscall
numbers) because glibc-2.6.1 has already syscall wrappers. So If added support
for Darwin of FreeBSD into libattr, which level should I implement?
attr_get(3) or getxattr(2/3) which is still parto of libattr? In other words:
Should I implement IRIX-styled API or the Linux-styled one?

-- Petr

Attachment: pgpWi2jQSJJQp.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>