linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: dm-devel@redhat.com, linux-lvm@redhat.com
Subject: [linux-lvm] New LVM2/device-mapper development tarballs
Date: Thu, 10 Nov 2005 15:52:47 +0000	[thread overview]
Message-ID: <20051110155247.GH26394@agk.surrey.redhat.com> (raw)

I have just created new tarballs from CVS for testing
purposes:

  ftp://sources.redhat.com/pub/dm/device-mapper.1.02.00.tgz
  ftp://sources.redhat.com/pub/lvm2/LVM2.2.02.00.tgz

There are some significant extensions to libdevmapper and 
the code that activates logical volumes has been rewritten
to prepare for kernel patches to fix snapshot activation.
The new code will also make it possible to support more
complex device hierarchies in the future, such as snapshots 
of mirrors.

So far I've done some basic testing, but I expect there
are still plenty more bugs to be found: If you find any,
please report them to one of these lists!

(Note that you'll need to install the new device-mapper package
before the new LVM2 one.)

Alasdair
-- 
agk@redhat.com

                 reply	other threads:[~2005-11-10 15:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20051110155247.GH26394@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).