diff options
| author | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-08-20 21:44:51 +0000 |
|---|---|---|
| committer | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-08-20 21:44:51 +0000 |
| commit | a1c12c59399daab8a78cb145d1c2c0d0b0664ba9 (patch) | |
| tree | 901f2f7d99c6c4824ba39c14ada9598cfd6a80b5 /debian/mdadm.docs | |
| parent | f99acd60de30e4228dd452ce93b253e760f76719 (diff) | |
Sorry for the large commit, I have been working all day and chaotically, so
this is the reward. I am nearing a release, but it's not quite done...
changelog so far (this is for the pending 2.5.3.git2006whatever-1 release, and
includes previous "unreleased" entries).
* Tracking upstream git releases.
- now the --run switch behaves as stated in the manpage. This properly
fixes #287415
- new version-1 partitionable arrays are now named X instead of _dX (e.g.
0 instead of _d0) for device names like md_dX. I actually think this is
a bug and hope upstream will use dX (e.g. d0) instead in a future
version.
* Instead of trying to do a whole lot of magic with respect to detecting
RAID devices to start, mdadm from now on requires a valid mdadm.conf file
to be installed. It still tries to do what it can, but there are no
heuristics anymore. See /usr/share/doc/mdadm/README.upgrading-2.5.3 .
* Removed the zero-superblock warning because we require the user to sign
off the configuration file anyway.
* This also enables us to use mdadm.conf from the initial ramdisk and thus
closes: #381303.
* In case the user chooses to assemble all arrays from the initial ramdisk,
use the new homehost feature of mdadm (closes: #381057). This will start
only those arrays belonging to the local system, unless it is the first
run on a system, in which case it will start all arrays and mark them as
belonging to the local system.
* Improved the debconf control script: integrated error messages into the
frontends, and made it a bit smarter. Error messages can now be
translated, and the script checks whether the user's choice is listed in
the configuration file and only proceeds if it is, or the user chooses to
ignore that it is not.
* mkconf can now take a generate/force-generate parameter to write directly
to /etc/mdadm/mdadm.conf. A second parameter specifies an alternate
filename.
* mkconf now outputs comments for the settings it suggests.
* Removed all udev-related stuff. We must coexist with udev because there
are setups that assemble arrays without mdadm, so the device nodes must be
created by udev, if that is used.
(closes: #382263, #382450, #383688, #383891, #383806, #382480)
Staying at low urgency since these (RC) bugs only exist in unstable.
* Now installs MD modules and mdadm/mdrun into initial ramdisk regardless of
whether the hook script thinks there are devices to start. This was done
to enable recovery from the initramfs shell.
* Now uses 'MD' instead of 'RAID' consistently in all messages.
* Now rebuilds initramfs for all installed kernels.
* Now breaks the endless config loop only when the user does not see the
question (see #381284, #381007).
* Don't fail mdadm-raid when /dev is on a read-only filesystem
(closes: #382876).
* Updated debconf translations:
- French by Florentin Duneau (closes: #382389).
Diffstat (limited to 'debian/mdadm.docs')
| -rw-r--r-- | debian/mdadm.docs | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/debian/mdadm.docs b/debian/mdadm.docs index 6282b256..2a34ed24 100644 --- a/debian/mdadm.docs +++ b/debian/mdadm.docs @@ -1,6 +1,7 @@ TODO debian/README.recipes debian/README.initramfs-transition +debian/README.upgrading-2.5.3 debian/README.mdrun debian/README.checkarray debian/FAQ |