> >
> In fact, when you have compartments defined with exclusive bits, the initial
> compartment section
> do not relates anymore to initial compartments by default for a clearance,
> but to the fact you
> have exclusive bits sets in your compartments.
I'm not sure what's being expressed here. In the sample encodings,
compartment bit 4 has no corresponding word (name) associated with it
and is therefore reserved for future expansion.
See label_encodings.multi for an example of reserving 190-239.
This should be explained in Compartmented Mode Workstation Labeling:
Encodings Format
http://docs.sun.com/app/docs/doc/819-0874
initial compartments are specified for classifications. When
that classification is specified, the label automatically includes
the compartment viz: specifying sandbox in the example yealds
the label "sandbox playground" (playground being the word corresponding
to bit 0)
> I must admit the precise relation between those initial-that-are-not-initial
> compartments and the
> exclusive bits is still not perfectly clear on my side, but I suspect it is
> related to the max number
> of bits on which you have used them (4 in your example, from 0 to 3).
Again, I'm not sure what's being expressed here other than what I
said about reserved for future expansion compartment bits. The
sample encodings defines words associated with bits 0-3 and reserves
bit 4.
>
> I hope someone else could cdevelop this a bit more, as up to know I did not
> find real detailed
> doc about this specific point...
In addition to label_encodings(4), see
http://docs.sun.com/app/docs/doc/819-0873
Gary..
