diff options
| author | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-11-15 17:53:09 +0000 |
|---|---|---|
| committer | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-11-15 17:53:09 +0000 |
| commit | 3806ec05e15904a2adbfb65b35eb7c6f03923d41 (patch) | |
| tree | 32935bf2093a08fd54f7afffdc5ef8c2ddf086bf /debian/TODO | |
| parent | 3da53d7de2be68e260ec6511df2e6ea94d463fa2 (diff) | |
more todo items
Diffstat (limited to 'debian/TODO')
| -rw-r--r-- | debian/TODO | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/debian/TODO b/debian/TODO index b5967a1d..34833468 100644 --- a/debian/TODO +++ b/debian/TODO @@ -1,13 +1,14 @@ debian mdadm TODO list ====================== -- check whether mdadm.conf and system are consistent during initramfs creation - and fail otherwise (#381303). - version-1 is a nightmare. E.g. on partitionable arrays, with / on /dev/md_d0p3, mdadm -Es ignores /dev/md_d0 and just uses the name, so /dev/md/<arrayname>. - figure out something about device names. +- (better) udev integration +- check whether mdadm.conf and system are consistent during initramfs creation + and fail otherwise (#381303). - 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 @@ -21,6 +22,7 @@ debian mdadm TODO list - more granular handling of init.d starts/stops, don't force all arrays to be started. +- let user specify when to start/stop which array (#398310). - also only stop those array we started; this can be easily done with sentinels in $STATEDIR |