summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorDieter Plaetinck <dieter@plaetinck.be>2008-11-10 18:25:11 +0100
committerDieter Plaetinck <dieter@plaetinck.be>2008-11-10 18:25:11 +0100
commitce72829ec480acdbcd0d853377b895854feea80d (patch)
tree80f5ef35b24b7de9150ad51050f5ca3b516ba656 /TODO
parentc17b3379cef3d6e6dd67f2a7f74a7d51a12dd935 (diff)
todo updates
Diffstat (limited to 'TODO')
-rw-r--r--TODO20
1 files changed, 16 insertions, 4 deletions
diff --git a/TODO b/TODO
index ef0503e..45a71d6 100644
--- a/TODO
+++ b/TODO
@@ -1,19 +1,29 @@
See also the FIXME's and TODO's in the code.
-ALPHA PHASE: get it sort of reasonably working
+PRE-ALPHA PHASE: get it sort of reasonably working
+* core/interactive bug: -> configure system -> fstab (/mnt//etc/fstab) does only contain pts,shm and floppy/dvd/cdrom. not hd's? ->this breaks the boot procedure!
+
+
+
+ALPHA PHASE: get some people to test and suggest ideas, while fixing bugs
General:
* go over ALL files and check all function/executable calls are to existing
things (eg no dirty leftovers for functions that have been renamed)
* same for variables
+* go over all files and clean up
* fix to use $var_UI_TYPE where needed
* write the ui functions for asking questions etc for both cli and dialog and port all code to use it.
Specifically:
* core/interactive bug: boot space 15 -> too large should be too small
* core/interactive bug: swap space 0 -> invalid?
-* core/interactive/lib-ui: you always need to press ok before it does the action it just said it's
-doing (is it the same with previous installer?)
+* core/interactive bug: autogenerated grub menu.lst:
+ - 0) devices are /dev/hda, not sda :/
+ - 1) windows entry looks okay
+ - 0-1-3 again! (3)windows looks okay again), 0-1 use uuid's which are correct
+* core/interactive: keymap setting not kept? (note: next time check rc.conf values during configure system)
+* core/interactive: /mnt//etc/fstab -> // ?
* core/interactive: try out different installation methods
* core/base: implement as specified in README
* core/quickinst: figure out what needs to be done and do it.
@@ -45,7 +55,9 @@ support for profiles could be built in certain procedures), maybe by supplying e
arguments to the procedure or asking a few questions.
For automatic procedures, a profile could be the fundamental entitiy,
whereas for interactive procedures it could provide some other defaults.
-
+* all dialog windows are equally sized. noone cares, right?
+* we run mkinitcpio twice: one while installing kernel packages, once after
+configuring the system (mkinitcpio.conf). can we optimize this?
WORRIES FOR MAYBE NO GOOD REASON
* base procedure is mostly to serve other procedures. If we need to do much