Mark Shellenbaum writes: > > Isn't the same true of the "SETTABLE" attribute? It's listed as > > failing with EPERM on all attempts, and in the SUNWattr_rw section, > > just like OPAQUE. > > > > The SETTABLE attribute was removed with > > Rescind SETTABLE Attribute [PSARC/2007/444 Self Review]
Oh ... duh. > > Currently, it looks like the SUNWattr_ro items are all things that can > > be determined at mount time (FSID and MDEV), and thus the fact that > > these can't be changed is without consequence. But where does the > > OPAQUE flag come from? How does it ever get set in the first place, > > if it's a read-only attribute? > > > > OPAQUE is a BSD specific attribute, which is used as part of unionfs. Got it; thanks. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
