diff options
author | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-08-30 15:50:00 +0000 |
---|---|---|
committer | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-08-30 15:50:00 +0000 |
commit | 07113759a42105a28848a1392343bdfaac8eab62 (patch) | |
tree | fded5f1992bbfead7e4293a602343c28d4306cc9 /debian/mdadm.templates | |
parent | d4749533999d76ea700d65b23123580120cf1f62 (diff) |
* 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).
Diffstat (limited to 'debian/mdadm.templates')
-rw-r--r-- | debian/mdadm.templates | 13 |
1 files changed, 11 insertions, 2 deletions
diff --git a/debian/mdadm.templates b/debian/mdadm.templates index d7d69313..50f0efa6 100644 --- a/debian/mdadm.templates +++ b/debian/mdadm.templates @@ -18,8 +18,11 @@ _Description: 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 @@ _Description: Proceed with starting arrays not listed in mdadm.conf? . 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 |