Bug#573762: shouldn't include mdadm into initramfs at all if INITRDSTAT='none'

[martin f krafft]

also sprach Marc Haber <mh+debian-bugs at zugschlus.de> [2010.03.13.1935 +0100]:
> Why is mdadm included in an initrd for a system that doesn't use
> any RAID in the first place?

Because it made more sense this way. Adding RAID to initramfs is
hardly expensive or requires a lot of space, and if you accidentally
set INITRDSTART=none, you'll be glad.

> Please think about implementing an automatic or manual option that
> prevents mdadm from going into the initramfs.

mdadm will eventually switch to using an event-based, incremental
assembly algorithm (see the experimental branch). Then, mdadm will
always be in the initramfs anyway.

You always have the option to compile your own kernel, override the
initramfs hook script, or send patches that do what you want in
a way that keeps mdadm as generic and flexible as possible.

-- 
 .''`.   martin f. krafft <madduck at d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20100314/cf7f8bf0/attachment.pgp>