Joe Blount wrote: > >>> Is the acl_t intentionally designed to be opaque? >>> >> >> Yes, its meant to be opaque. >> >> The layout of the acl_t will likely change in the not too distant future. >> > > Will old versions be supported? For example, if ADM > <http://www.opensolaris.org/os/project/adm/> treats it as opaque and > archives the current format, after an upgrade (layout change), could we > write the old ACL to the new ZFS code? > > thanks, > Joe
acl_t is a purely in-core data structure, and is not appropriate for storing in an archive. Thats what interfaces such as acl_totext() are for. ADM should be archiving the ACL in a textual representation, much like tar/cpio do. The interfaces such as acl_get()/acl_set() are merely convenience functions to make it easier for getting/setting ACLs without having to know if the file system is ZFS or UFS. For example acl_get() knows how to determine if a file system supports POSIX draft ACLs or NFSv4 ACL and then uses the native acl(2) syscall to retrieve the data. -Mark _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
