On May 30, 2007, at 2:19 PM, Timothy Haley - Sun Microsystem wrote: > > 2.0 OVERVIEW > > The Solaris CIFS project requires file system support for a > number of > "system" and opaque file attributes. For file systems that fully > support CIFS, the system attributes will be present on all file > system objects and the file system will need to update the > attribute(s) as a result of various file system operations such as > data written to a file. The CIFS server and application programs > will also need to be able to query/update the attributes when > needed. Additionally, the CIFS server will be using the Solaris > extended attribute model for storing a number of opaque file > attributes. ZFS will be the primary underlying file system for the > CIFS server. > > In order to accommodate the existing extended attribute aware > utilities in Solaris, the new attributes will be exposed via the > existing Solaris extended attribute model. The new attributes will > be grouped in a number of SUNWattr* files that will have multiple > attributes in a single file composed as a packed nvlist. Since all
I assume the attributes will be XDR packed. > > 4.3.1 NFSv4 Support for Optional Attributes (Potential Future Work) > > The NFSv4 protocol has an attribute model that supports extensions. > In fact, two of the new attributes (ARCHIVE and HIDDEN) are part of > the "recommended" list of attributes for a client and server and SYSTEM > implementation. The Solaris NFSv4 client and server could be > modified to support the new, optional attributes as specified by > the protocol. Spencer
