On Thu, 26 Oct 2000, Timothy Shimmin wrote:
> It seems that your EA API assumes EA lists, whereas
> in XFS we seem to base it on EA sets.
> That is, in your API the ordering of attributes is significant;
> hence the ATR_APPEND, ATR_PREPEND and an ATR_SET definition which
> mentions the handling of multiple instances of the same name.
> In XFS there doesn't seem to be an explicit concept of ordering,
> and I thought that only one attribute name could exist for
> a particular file system object (well actually 2 - possibly
> a User space version and a Root space version) -
> is this not the case, Curtis ?
I'm not Curtis and don't know about XFS but I will try to answer your
question anyway. (-;
If XFS doesn't order the EAs that's fine. - However for FSs which do order
them the API has to provide the interface. - If the underlying FS chooses
to ignore ordering that is not a problem. - After all, the EAs will at a
low level be handled by each FS so they can choose to do what they want
concerning ordering (at least that would be my understanding of it).
> 3.
> How do you remove an attribute or multiple attributes ?
> Do you do a SET with a null value in <new> ?
You read in all EAs (ATR_GETALL), delete the ones you want to get
rid of and then you replace all of them (ATR_REPLACE). Easy. And it works
for just one, for seeral or even for all EAs at once.
Regards,
Anton
--
Anton Altaparmakov Phone: +44-(0)1223-333541 (lab)
Christ's College eMail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
Cambridge CB2 3BU WWW: http://www-stu.christs.cam.ac.uk/~aia21/
United Kingdom ICQ: 8561279
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
