Darren and Dermot, Attached is the mostly reverted DTD file.
I had to change <partition> to look like this: <!ELEMENT partition (partition*, slice*, size?)> instead of <!ELEMENT partition (slice*, size?)> Does that work for you? -Drew On 1/25/11 6:51 AM, Darren Kenny wrote:
I tend to agree with Dermot here, specifically for the case where we want do to something like: <partition action="use_existing_solaris2"/> If we differentiate between logical and primary in the schema, then the above wouldn't work as expected where the Solaris2 partition is a logical partition. Also, the 5-36 notion is also how fdisk itself interprets things with its -W and -F arguments, so we would also be deviating from that "standard" in Solaris. (Okay, there aren't numbers, but it's done by position in the output/input of fdisk here). Thanks, Darren. On 25/01/2011 13:38, Dermot McCluskey wrote:Drew, I'm a bit concerned that such a big change is coming in at the end of our discussion. As I understand it, the way this is meant to work is that the partition name is used to identify whether a partition is logical or primary, ie 1-4 = primary; 5-36 = logical. And there can only be one extended partition per disk, so it is always possible to determine which extended partition the logical partitions belong to. Admittedly, it might appear a bit neater if the logical partitions were sub-elements of the extended partition in the schema, but even so, it should definitely be possible to specify legitimate layouts with the existing DTD. Are there any specific use-cases that cannot be accommodated by the current schema? - Dermot btw, why would you need a part_type attrib on extended_partition? What values could it possibly have other than "15"?
binijaEG7s6et.bin
Description: application/applefile
target.dtd
Description: Binary data
_______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
