Ricardo M. Correia wrote:
> 
> On Qui, 2008-02-07 at 12:48 -0800, Matthew Ahrens wrote:
>> First, note that the problem is quite constrained:
>>
>> There are a fixed number of attribute names (for any given software version) 
>> since these are interpreted system attributes. Therefore the attribute names 
>> can be a small number, rather than a string -- ie, we have an enum that 
>> defines the attributes.  We (ie, OpenSolaris) can control the allocation of 
>> new enum values in this namespace.
> 
> Since we are on the subject of redesigning attributes, have you 
> considered providing a lighter-weight extended attribute mechanism to 
> userspace applications

The ZAP would probably be sufficient to store lighter-weight user extended 
attributes (directly in the ZAP, not to point to other files like the current 
Solaris extended attributes do).  The method I proposed for system attributes 
is not applicable, since user attributes would almost certainly be string -> 
string mappings.

--matt

Reply via email to