From df190f2bca650ba2ec94051d02d2f3bfc56130da Mon Sep 17 00:00:00 2001 From: lizhi-rocky Date: Fri, 16 Jul 2010 17:39:58 +0800 Subject: [PATCH] change design little. Today I'm thinking about partition. --- design.txt | 3 +++ xml/install_ng.xml | 3 ++- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/design.txt b/design.txt index 69b67f4..e3ffe02 100644 --- a/design.txt +++ b/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. diff --git a/xml/install_ng.xml b/xml/install_ng.xml index 1cc1eb1..d02a7be 100644 --- a/xml/install_ng.xml +++ b/xml/install_ng.xml @@ -34,7 +34,8 @@ - + +