Nathan Scott <nathans@xxxxxxx> writes:
> hi there Andreas,
> On Sun, Jun 02, 2002 at 06:34:29PM +0200, Andreas Jaeger wrote:
>> I'm one of the glibc developers and we considered adding support for
>> the *xattr syscalls to glibc.
>> Ulrich Drepper mentioned:
>> > - the various *xattr syscalls which were introduced in the 2.5 kernel
>> > might need libc support. I guess they do. But somebody should contact
>> > whoever wrote the code and ask them about the API which should be
>> > provided.
>> Can you tell me a bit more about the API?
> The best source of info is probably the man pages - they are part
> of the "attr" source package, and are also online at:
>> Is it stable?
> Yes, the interfaces are essentially unchanged since their initial
> inclusion in 2.5.3. Marcelo has told us this will be included in
>> Should we define it in glibc?
> I think so, yes. There is a libattr.so which also exports the system
> calls, so provided the two can coexist that would be great.
We would add those interfaces to libc.so.
It would help then if you would send any API changes also to the
libc-alpha@xxxxxxxxxxxxxxxxxx list (we might not notice them
>> Which constants/flags should be added?
> The attr package installs the header /usr/include/attr/xattr.h which
> defines all the interesting macros, etc.
>> Do you have some more documentation for the interface?
> The attr package contains several man pages (in addition to the system
> call interfaces), and AndreasG's web site also contains extra docs on
> extended attributes -- http://acl.bestbits.at/.
>> Is it used in other OSes and which header files define all the stuff?
> There are extended attributes interfaces on other OSes, but there's no
> standardisation in this area, and no two interfaces are really alike.
>> Some questions: What's the meaning of the size parameter? What can be
>> given for flags? What does getxattr return?
> These last few questions are answered in the syscall man pages.
thanks a lot! I'll look soon in more detail into this,
SuSE Labs aj@xxxxxxx