Dermot,
I updated the DTD to cover all of your comments. I wanted to address
the two specific questions you pointed out, however:
On 1/21/11 10:46 AM, Dermot McCluskey wrote:
Drew,
Also, I have heard people mention before that we should version our
DTDs. And that XML manifests should specify which DTD version(s)
that follow. Do we know how this is achieved?
I don't have a clue on this one. Does anybody else know?
Question:
Is it ever possible that we would want to specify either
noswap="true" or nodump="true" but not specify any
<zpool>s? If so, then we should change "zpool+" (1 or more)
to "zpool*" (0 or more) below, so that this would be legal:
<logical no_swap="true"/>
I'm ok with changing it to zpool* if everybody is as well.
new DTD things to Note:
- The in_zpool and in_vdev attributes have moved out of disk_name and up
to disk. This is because disk_name is an optional sub-element of disk,
like disk_name, disk_prop and disk_keyword.
- In writing the API for target manipulation and validation, I came to
realize that we need an <extended_partition> sub-element in addition to
<partition> and <slice> sub-elements to disk. All of the attributes
remain the same for extended_partition as partition with the exception
of part_type defaults to "15" instead of "191".
Also, <partition> objects can have slice*, size? as children, while
<extended_partition> can have partition*, size? as children.
Please let me know if you see anything else.
Thanks!
-Drew
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
