change design little.

Today I'm thinking about partition.

design.txt

@@ -100,6 +100,9 @@ row 4 | quit	    	      			 previous  next    |
     * initrd generating
     * boot (grub/elilo/yaboot) installing
 
+    Operation partition is very complicated. If I first record partition information in xml, then operate partitions based on data in xml, that will be difficult. For, first I have to record changes, some partitions may be untouched, some may be deleted, some may be changed a flag. If users operate partition list many times, how shall I do. Shall I record the action or the result? If action, order is critical. If result, I have to deduce actions. I do not like complexity. So I decided to let user use extern command like fdisk/parted directly.
+    Ok, I know there's a side effect that partition will destroy data on disk. To minimize that, I will let partition operating be the last steps.
+
 4. Hello Modules
 
    Nothing is particularly hard if you divide it into small jobs.

xml/install_ng.xml

@@ -34,7 +34,8 @@
 	  </choice>
 	</attribute>
 	<attribute name="id"/>
-	<attribute name="size"/>
+	<attribute name="start"/>
+	<attribute name="end"/>
       </element>
     </oneOrMore>
   </define>