From: Alasdair G Kergon <agk@redhat.com>
To: linux-lvm@redhat.com, dm-devel@redhat.com
Subject: [linux-lvm] LVM2 release 2.02.03 / device-mapper 1.02.04
Date: Fri, 14 Apr 2006 22:43:57 +0100 [thread overview]
Message-ID: <20060414214357.GE4521@agk.surrey.redhat.com> (raw)
Some bug fixes and minor enhancements. (See the WHATS_NEW files.)
ftp://sources.redhat.com/pub/dm/device-mapper.1.02.04.tgz
ftp://sources.redhat.com/pub/lvm2/LVM2.2.02.03.tgz
The tools should cope better now if faced with multiple distinct
VGs with the same name. 'pvs -P /dev/whatever -o+vg_uuid' output
should be reliable, and vgrename accepts a VG uuid as first
argument.
And libdevmapper has support again for older 2.6 kernels that
can't handle mapped device referencing by device number.
Alasdair
--
agk@redhat.com
next reply other threads:[~2006-04-14 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 21:43 Alasdair G Kergon [this message]
2006-04-17 23:28 ` [linux-lvm] LVM2 release 2.02.03 / device-mapper 1.02.04 Alexey Shinkin
2006-04-19 16:23 ` Alasdair G Kergon
2006-04-20 20:25 ` Simone Gotti
2006-04-21 14:25 ` Eric Edgar
2006-04-21 14:45 ` Old Fart
2006-04-21 14:53 ` Alasdair G Kergon
2006-04-21 15:13 ` Simone Gotti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060414214357.GE4521@agk.surrey.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).