From: Wichert Akkerman <wichert@wiggy.net>
To: Jose Luis Domingo Lopez <linux-kernel@24x7linux.com>,
linux-kernel@vger.kernel.org
Subject: Re: Device-mapper submission for 2.4
Date: Wed, 10 Dec 2003 10:40:51 +0100 [thread overview]
Message-ID: <20031210094051.GA14619@wiggy.net> (raw)
In-Reply-To: <3FD67005.6060606@tupshin.com>
Previously Tupshin Harper wrote:
> This is not true. LVM2 can read the LVM1 format, but it cannot
> communicate with non-dm interfaces in 2.4.x. This means that you need to
> run lvm1 on 2.4 and lvm2 on 2.6 unless you patch 2.4 with dm.
And unless my memory is failing me all distros ship tools that will
detect which interface your system has and call the right tool for you.
That was already needed for lvm1 which went through several ioctl
interfaces and continues to work fine for lvm2. Which means this
is pretty much a non-issue.
Wichert.
--
Wichert Akkerman <wichert@wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
next prev parent reply other threads:[~2003-12-10 9:40 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 11:58 Device-mapper submission for 2.4 Joe Thornber
2003-12-09 12:24 ` [Patch 1/4] fs.h: b_journal_head Joe Thornber
2003-12-09 23:46 ` Nathan Scott
2003-12-10 8:46 ` Joe Thornber
2003-12-10 12:06 ` Nathan Scott
2003-12-09 12:25 ` [Patch 2/4] dm: mempool backport Joe Thornber
2003-12-09 12:26 ` [Patch 3/4] dm: core files Joe Thornber
2003-12-09 12:26 ` [Patch 4/4] dm: ioctl interface Joe Thornber
2003-12-09 13:15 ` Device-mapper submission for 2.4 Marcelo Tosatti
2003-12-09 13:45 ` Joe Thornber
2003-12-09 14:00 ` Måns Rullgård
2003-12-09 14:10 ` Muli Ben-Yehuda
2003-12-09 14:21 ` Måns Rullgård
2003-12-09 14:16 ` Joe Thornber
2003-12-09 14:24 ` Stefan Smietanowski
2003-12-09 14:10 ` Marcelo Tosatti
2003-12-09 14:34 ` Joe Thornber
2003-12-09 21:07 ` Paul Jakma
2003-12-09 22:26 ` Joe Thornber
2003-12-09 22:48 ` Marcelo Tosatti
2003-12-09 23:46 ` Paul Jakma
2003-12-09 23:58 ` William Lee Irwin III
2003-12-10 0:15 ` Paul Jakma
2003-12-10 11:49 ` Stephan von Krawczynski
2003-12-10 23:15 ` Dave Jones
2003-12-10 0:27 ` Jose Luis Domingo Lopez
2003-12-10 0:59 ` Tupshin Harper
2003-12-10 9:40 ` Wichert Akkerman [this message]
2003-12-10 2:44 ` Martin J. Bligh
2003-12-10 15:55 ` Paul Jakma
2003-12-10 16:54 ` venom
2003-12-10 17:00 ` Paul Jakma
2003-12-10 17:14 ` venom
2003-12-10 23:40 ` Mike Fedyk
2003-12-11 19:48 ` Alasdair G Kergon
2003-12-16 19:15 ` bill davidsen
2003-12-16 19:01 ` bill davidsen
2003-12-10 8:45 ` Jens Axboe
2003-12-10 17:30 ` Paul Jakma
2003-12-10 17:44 ` Joe Thornber
2003-12-10 17:48 ` venom
2003-12-10 18:07 ` Paul Jakma
2003-12-10 19:30 ` Jens Axboe
2003-12-09 17:02 ` Bill Rugolsky Jr.
2003-12-09 22:53 ` Ciaran McCreesh
2003-12-10 3:38 ` Lincoln Dale
2003-12-10 6:12 ` Willy Tarreau
2003-12-10 6:35 ` viro
2003-12-09 17:45 ` Kevin Corry
2003-12-09 19:47 ` Paul P Komkoff Jr
2003-12-09 14:23 ` Stefan Smietanowski
2003-12-09 14:36 ` Joe Thornber
2003-12-09 19:50 ` William Lee Irwin III
2003-12-09 21:13 ` Paul Jakma
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 0:49 Carl-Daniel Hailfinger
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=20031210094051.GA14619@wiggy.net \
--to=wichert@wiggy.net \
--cc=linux-kernel@24x7linux.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