Bug#272034: initrd-tools: if no /etc/mdadm/mdadm.conf exists then mdrun should be called instead of mdadm

[maximilian attems <debian@sternwelten.at>]

hello Mario,

can you enlight me on belows bug report concerning
the mdadm support in initrd-tools.

On Thu, 16 Sep 2004, Mike Fedyk wrote:

> Package: initrd-tools
> Version: 0.1.71
> Severity: normal
> 
> This has the problem that if persistent superblocks are configured but not
> used on some drives it can start a raid array where not wanted, but it will
> avoid having to regenerate your initrd image just because you changed the
> structure of your array.
> 
> The problem can be avoided just like the mdadm package does it (desc in
> subject), so it isn't too hard to work around.
> 
> -- System Information:
> Debian Release: 3.1
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.7-1-386
> Locale: LANG=C, LC_CTYPE=C
> 
> Versions of packages initrd-tools depends on:
> ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
> ii  cpio                          2.5-1.1    GNU cpio -- a program to manage ar
> ii  cramfsprogs                   1.1-6      Tools for CramFs (Compressed ROM F
> ii  dash                          0.5.1-3    The Debian Almquist Shell
> ii  util-linux                    2.12-3     Miscellaneous system utilities
> 
> -- no debconf information

is that still the case?
i see no mdrun call in /etc/init.d/mdadm
am i looking at the wrong place?

thanks for your explanations.
--
maks