From a3db1035f47bfe43a1d74762c0e709a923d4e7ac Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 27 Apr 2024 05:14:06 +0200 Subject: Correcting filename of TODO. Signed-off-by: Daniel Baumann --- debian/TODO | 29 ----------------------------- debian/mdadm.TODO | 29 +++++++++++++++++++++++++++++ 2 files changed, 29 insertions(+), 29 deletions(-) delete mode 100644 debian/TODO create mode 100644 debian/mdadm.TODO diff --git a/debian/TODO b/debian/TODO deleted file mode 100644 index eb3299e..0000000 --- a/debian/TODO +++ /dev/null @@ -1,29 +0,0 @@ -debian mdadm TODO list -====================== - -- 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/. -- 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 - determine that the configuration is okay. A conservative approach would be - beneficial to the user. Not sure if it's worth the effort though. -- one nice^W important thing would be to check device names and UUIDs at least. - -- verify operation without udev - - udev removed before mdadm installed - - udev removed after mdadm installed - -- 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 - -- manage DAEMON_OPTIONS with debconf diff --git a/debian/mdadm.TODO b/debian/mdadm.TODO new file mode 100644 index 0000000..eb3299e --- /dev/null +++ b/debian/mdadm.TODO @@ -0,0 +1,29 @@ +debian mdadm TODO list +====================== + +- 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/. +- 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 + determine that the configuration is okay. A conservative approach would be + beneficial to the user. Not sure if it's worth the effort though. +- one nice^W important thing would be to check device names and UUIDs at least. + +- verify operation without udev + - udev removed before mdadm installed + - udev removed after mdadm installed + +- 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 + +- manage DAEMON_OPTIONS with debconf -- cgit v1.2.3