diff options
| author | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-09-16 09:22:35 +0000 |
|---|---|---|
| committer | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-09-16 09:22:35 +0000 |
| commit | ac6676d8d0148507bf7ad80d62ae8a07ac5e228d (patch) | |
| tree | 54d22a6249918f02ee639da7915ea55690e768c3 /debian/mdadm.templates | |
| parent | 2e8c870bd86788473b0f99fd7fddd6a52c62b481 (diff) | |
multiple instead of multi
Diffstat (limited to 'debian/mdadm.templates')
| -rw-r--r-- | debian/mdadm.templates | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/debian/mdadm.templates b/debian/mdadm.templates index d5afc473..1cbf68a2 100644 --- a/debian/mdadm.templates +++ b/debian/mdadm.templates @@ -67,7 +67,7 @@ Default: true _Description: Do you want to start MD arrays automatically? Once the base system has come up, mdadm can start all MD arrays (RAIDs) specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless - you have compiled multi-device (MD) support into the kernel and marked all + you have compiled multiple device (MD) support into the kernel and marked all partitions part of MD arrays with type 0xfd (as those and only those will be started automatically by the kernel), this is probably what you want. |