summaryrefslogtreecommitdiff
path: root/debian/mdadm.templates
diff options
context:
space:
mode:
authorMichael Tokarev <mjt@tls.msk.ru>2014-10-04 18:19:11 +0400
committerMichael Tokarev <mjt@tls.msk.ru>2014-10-04 20:32:00 +0400
commitffb0e126255a6a074519ee458b5d26d6ba40dca1 (patch)
treee743bebc862349a7476e70c4e3f5980c0f596cc6 /debian/mdadm.templates
parent47db9cc7c7c53ddc81f03803575e39f605f99633 (diff)
removed AUTOSTART variable from /etc/default/mdadm
Diffstat (limited to 'debian/mdadm.templates')
-rw-r--r--debian/mdadm.templates11
1 files changed, 0 insertions, 11 deletions
diff --git a/debian/mdadm.templates b/debian/mdadm.templates
index 4ff10362..ddf63c76 100644
--- a/debian/mdadm.templates
+++ b/debian/mdadm.templates
@@ -68,17 +68,6 @@ _Description: Start arrays not listed in mdadm.conf?
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
-Default: true
-_Description: Do you want to start MD arrays automatically?
- Once the base system has booted, mdadm can start all MD arrays
- (RAIDs) specified in /etc/mdadm/mdadm.conf which have not yet been
- started. This is recommended unless multiple device (MD) support is
- compiled into the kernel and all partitions are marked as belonging
- to MD arrays, with type 0xfd (as those and only those will be started
- automatically by the kernel).
-
Template: mdadm/autocheck
Type: boolean
Default: true