diff options
Diffstat (limited to 'debian/NEWS')
-rw-r--r-- | debian/NEWS | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/debian/NEWS b/debian/NEWS new file mode 100644 index 00000000..b6c27b1f --- /dev/null +++ b/debian/NEWS @@ -0,0 +1,41 @@ +mdadm (2.5-1) unstable; urgency=low + + mdrun has been (finally) obsoleted, and an appropriate warning message is + written to the console if you (or a script) attempts to run it. If you + cannot live without mdrun, you can disable the warning by setting + USE_DEPRECATED_MDRUN=1 in /etc/default/mdadm. Note that mdrun will *not* be + supported. Please also see /usr/share/doc/mdadm/README.mdrun . + + -- martin f. krafft <madduck@debian.org> Tue, 30 May 2006 23:25:13 +0200 + +mdadm (2.4.1-5) unstable; urgency=low + + This version drops the automatic generation of the /etc/mdadm/mdadm.conf + file on every boot (if it was missing). This means that you need to ensure + that you have a valid configuration file. If none is present during package + configuration, mdadm *will* try to generate one, but it will only contain + information about arrays that were running at the time of package + configuration. Arrays not listed in the configuration file will *not* be + started automatically after boot (with the exception of the root partition). + + If you want to recreate your configuration file, either figure out what it + should contain from the mdadm.conf(5) manpage, or simply assemble and run + all the arrays the way you like it, then run + /usr/share/mdadm/mkconf > /etc/mdadm/mdadm.conf + + -- martin f. krafft <madduck@debian.org> Sat, 03 Jun 2006 17:45:47 +0200 + +mdadm (2.4.1-1) unstable; urgency=low + + As of version 2.3, mdadm uses /etc/mdadm.conf as its main configuration + file, and falls back to /etc/mdadm/mdadm.conf if the former is not found. + Since Debian uses /etc/mdadm/mdadm.conf as the configuration file path, this + order was reverted: Debian's mdadm reads /etc/mdadm/mdadm.conf as its main + file and falls back to /etc/mdadm.conf if the former is not found. + + An incompatible change in the reshaping of RAID 5 arrays was made in this + upstream release. If you want to reshape a RAID 5 array with a version-1 + superblock, please make sure to use mdadm 2.4.1 and at least a 2.6.17-rc2 + kernel. + + -- martin f. krafft <madduck@debian.org> Tue, 16 May 2006 13:07:49 -0500 |