Niall,
Is there a file that defines all the supported GUIDs?
/usr/include/sys/efi_partition.h seems to have at least the Solaris
value you are defaulting to.
My preference would be to either require the user to enter the guid
hex string, but refer them to a local file that defines all the supported
values (in which case I call the attrib "guid", not "guid_type"?
or switch to using meaning names, but have a list of the supported
values hard-coded in the DTD, eg:
<!ATTLIST gpt_slice gpt_partition_type (solaris|esp|....) "solaris">
plus a comment that explains that these values are mapped to GUIDs
internally.
- Dermot
On 02/04/11 09:59, Niall Power wrote:
Hi Guys,
Following on from the discussion we had yesterday about factoring in GPT slices
into the schema I just want to throw this in so that it doesn't slip through
the cracks.
Here's a first stab at defining a gpt_slice element within the target DTD
schema:
<!ELEMENT disk ((disk_name|disk_prop|disk_keyword|iscsi), partition*, slice*,
gpt_slice*)>
<!ELEMENT gpt_slice (size?)>
<!ATTLIST gpt_slice name CDATA #REQUIRED>
<!ATTLIST gpt_slice action (create|delete|preserve) "create">
<!ATTLIST gpt_slice guid_type CDATA "6A898CC3-1DD2-11B2-99A6-080020736631">
The guid_type value is not very user friendly, so we may wish to consider a more convenient
shorthand notation for key types;
eg. "solaris" or "esp" which matches the EFI system partition:
<!ATTLIST gpt_slice guid_type CDATA "solaris">
For explanation of guid_type, see:
http://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
