This bug was fixed in the package mdadm - 2.6.7-3ubuntu5
---------------
mdadm (2.6.7-3ubuntu5) intrepid; urgency=low
* Fixes for LP: #268580
- debian/mdadm-udeb.dirs: add lib/partman for the check script
- debian/mdadm.config: don't initialize BOOT_DEGRADED to false
- debian/rules: install the check script, put the boot_degraded debconf
question in the mdadm-udeb
- debian/mdadm.templates, debian/mdadm-udeb.templates: move the
boot_degraded question to the udeb
- debian/po/POTFILES.in: add the new mdadm-udeb.templates
- debian/install-rc: install the check script, copied from partman-target
- check.d/_numbers, check.d/root_on_raid: new script to check if / or
/boot is on an md device and if so, prompt for BOOT_DEGRADED in the
installer
- debian/mdadm.config: initialize BOOT_DEGRADED to ""
-- Dustin Kirkland <[EMAIL PROTECTED]> Sat, 13 Sep 2008 11:09:09
-0400
** Changed in: mdadm (Ubuntu)
Status: In Progress => Fix Released
--
Prompt for BOOT_DEGRADED=true|false in the installer
https://bugs.launchpad.net/bugs/268580
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
