From: Alasdair G Kergon <agk@uk.sistina.com>
To: dm-devel@sistina.com
Cc: Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [dm-devel] [RFC] device-mapper v4 ioctl interface implementation
Date: Sun, 6 Jul 2003 01:39:48 +0100 [thread overview]
Message-ID: <20030706013948.A19057@uk.sistina.com> (raw)
In-Reply-To: <20030701145812.GA1596@fib011235813.fsnet.co.uk>; from thornber@sistina.com on Tue, Jul 01, 2003 at 03:58:12PM +0100
On Tue, Jul 01, 2003 at 03:58:12PM +0100, Joe Thornber wrote:
> Following on from the header file for the v4 ioctl interface that I
> posted a couple of weeks ago, here is the first cut at the
> implementation (3 patches posted as a follow up to this mail). I hope
> the v1 interface can be retired before 2.6. Tools are not yet
> available to drive this, but should be later this week.
Updated device-mapper tools (dmsetup + libdevmapper) are now
available for testing at:
ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-testing-new-version4-interface.tgz
This tarball also includes the complete device-mapper patches
for 2.4.20 and 2.4.21, also available outside the tarball at:
ftp://ftp.sistina.com/pub/LVM2/device-mapper/patches/combined*
Updated LVM2 tools to work alongside the above are at:
ftp://ftp.sistina.com/pub/LVM2/tools/LVM2.0-testing.tgz
If the new tools detect the old version 1 driver, they try to
fall back and use the version 1 API, so you shouldn't
need to keep two sets of tools around if you're regularly
swapping kernels. [But this hasn't been thoroughly tested.]
Alasdair
--
agk@uk.sistina.com
prev parent reply other threads:[~2003-07-06 0:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 14:58 Joe Thornber
2003-07-01 15:01 ` [RFC 1/3] dm: fix memory leak Joe Thornber
2003-07-01 15:01 ` [RFC 2/3] dm: avoid event race Joe Thornber
2003-07-01 15:02 ` [RFC 3/3] dm: v4 ioctl interface Joe Thornber
2003-07-01 20:05 ` Kevin Corry
2003-07-02 8:59 ` Joe Thornber
2003-07-02 10:59 ` [dm-devel] " Joe Thornber
2003-07-02 10:59 ` Joe Thornber
2003-07-02 10:59 ` Joe Thornber
2003-07-02 11:00 ` Joe Thornber
2003-07-02 11:00 ` Joe Thornber
2003-07-02 14:17 ` Kevin Corry
2003-07-02 14:15 ` Kevin Corry
2003-07-06 0:39 ` Alasdair G Kergon [this message]
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=20030706013948.A19057@uk.sistina.com \
--to=agk@uk.sistina.com \
--cc=dm-devel@sistina.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®