All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Cattelan <cattelan@thebarn.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com, petr.pisar@atlas.cz
Subject: Re: Portability of libattr
Date: Fri, 11 Apr 2008 10:01:27 -0500	[thread overview]
Message-ID: <47FF7D47.40007@thebarn.com> (raw)
In-Reply-To: <20080409185445.GA30834@infradead.org>

Christoph Hellwig wrote:
> On Wed, Apr 09, 2008 at 08:41:08PM +0200, petr.pisar@atlas.cz wrote:
>   
>> Hello,
>>
>> I'm adding support for extended atributes into few applications.
>> Unfortunatetally API for EA manipulation is not standartized and every
>> operating system uses its own solution. I thought libattr from attr package
>> could help me. However attr seems running on Linux (and maybe IRIX) only.
>>
>> Therefore I've decided to use libc functions from every system directly. I've
>> succesfully ported my code to Linux, IRIX and Darwin (Max OS X). Their AE
>> syscalls are very similar. However FreeBSD API is more different. Because I'm
>> extending more applications I need to share the code.
>>
>> So, my qustions are: should I write my own library or should I extend libattr.
>> As I can understand libattr code it's designed to port IRIX application on
>> Linux. Am I right? Or are you going support more OS's in libattr? Or exists
>> here some similar library providing unified interface fro more systems?
>>     
>
> Note: I'm not the maintainer of libattr, so I'm not the one to decide.
>
> I think adding more systems is an excellent idea as it's a bit of a
> porting layer already.  Russell will have to add FreeBSD support anyway
> once he ports xfsdump to FreeBSD :)
>
>   
nod.

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?

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.

I would be really cool if we got FreeBSD support into libattr.

-Russell

  reply	other threads:[~2008-04-11 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 18:41 Portability of libattr petr.pisar
2008-04-09 18:54 ` Christoph Hellwig
2008-04-11 15:01   ` Russell Cattelan [this message]
2008-04-11 16:40     ` petr.pisar
2008-04-11 19:47       ` nscott

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=47FF7D47.40007@thebarn.com \
    --to=cattelan@thebarn.com \
    --cc=hch@infradead.org \
    --cc=petr.pisar@atlas.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.