summaryrefslogtreecommitdiff
path: root/debian/TODO
diff options
context:
space:
mode:
authormadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2006-08-21 14:45:34 +0000
committermadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2006-08-21 14:45:34 +0000
commit0217504826d4ea805646a08ba0ee96fc3df80e7e (patch)
tree0a0df9771e5a3991529c3ba4f43c42e76d7e4010 /debian/TODO
parent0866367b61c4ba9f4b4e1ca2c31d9eb5cea1a41e (diff)
todo item about configuration comparison
Diffstat (limited to 'debian/TODO')
-rw-r--r--debian/TODO6
1 files changed, 6 insertions, 0 deletions
diff --git a/debian/TODO b/debian/TODO
index 23bc9405..b761947b 100644
--- a/debian/TODO
+++ b/debian/TODO
@@ -8,6 +8,12 @@ debian mdadm TODO list
/dev/md/<arrayname>.
- figure out something about device names.
+- add code to compare existing and expected configuration, after standardising
+ the files. In most cases, we'll have to answer DUNNO as to whether the
+ existing configuration file is okay, but I guess in some cases we can
+ determine that the configuration is okay. A conservative approach would be
+ beneficial to the user. Not sure if it's worth the effort though.
+
- VERIFY SARGE UPGRADE
- verify operation without udev
- udev removed before mdadm installed