r151 - mdadm/trunk/debian

[madduck at users.alioth.debian.org]

Author: madduck
Date: 2006-08-30 15:50:00 +0000 (Wed, 30 Aug 2006)
New Revision: 151

Modified:
   mdadm/trunk/debian/changelog
   mdadm/trunk/debian/mdadm.templates
Log:
   * Added a note to alert people that the warning about arrays not listed in
     the configuration file is only relevant if the arrays are needed to be
     brought up by mdadm from initramfs during boot (closes: #385017).


Modified: mdadm/trunk/debian/changelog
===================================================================
--- mdadm/trunk/debian/changelog	2006-08-30 14:43:36 UTC (rev 150)
+++ mdadm/trunk/debian/changelog	2006-08-30 15:50:00 UTC (rev 151)
@@ -2,10 +2,13 @@
 
   * Do not override the superblock default version in mdadm.conf to prevent
     creation of superblocks that the kernel can't handle (closes: #384614).
+  * Added a note to alert people that the warning about arrays not listed in
+    the configuration file is only relevant if the arrays are needed to be
+    brought up by mdadm from initramfs during boot (closes: #385017).
   * Updated debconf translations:
     - Czech by Miroslav Kure (closes: #384754).
 
- -- martin f. krafft <madduck at debian.org>  Wed, 30 Aug 2006 16:42:09 +0200
+ -- martin f. krafft <madduck at debian.org>  Wed, 30 Aug 2006 17:41:13 +0200
 
 mdadm (2.5.3.git200608202239-2) unstable; urgency=low
 

Modified: mdadm/trunk/debian/mdadm.templates
===================================================================
--- mdadm/trunk/debian/mdadm.templates	2006-08-30 14:43:36 UTC (rev 150)
+++ mdadm/trunk/debian/mdadm.templates	2006-08-30 15:50:00 UTC (rev 151)
@@ -18,8 +18,11 @@
  If you know exactly which arrays are needed to bring up the root filesystem,
  and you want to postpone starting all other arrays to a later point in the
  boot sequence, enter the arrays to start here. Alternatively, enter 'all' to
- simply start all available arrays. If you do not need or want to start any
- arrays for the root filesystem, leave the answer blank (or enter 'none').
+ simply start all available arrays.
+ .
+ If you do not need or want to start any arrays for the root filesystem, leave
+ the answer blank (or enter 'none'). This may be the case if you are using
+ kernel autostart or do not need any arrays to boot.
 
 Template: mdadm/initrdstart_msg_errexist
 Type: text
@@ -51,6 +54,12 @@
  .
  Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend
  to continue.
+ .
+ This warning is only relevant if you need arrays to be started from the
+ initial ramdisk to be able to boot. If you use kernel autostarting, or do not
+ need any arrays to be started as early as the initial ramdisk is loaded, you
+ can simply continue. Alternatively, choose not to continue and enter 'none'
+ when prompted which arrays to start from the initial ramdisk.
 
 Template: mdadm/autostart
 Type: boolean