From: Jochen Hein <jochen@jochen.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 <-> 2.6 compatibility
Date: Sun, 26 Oct 2003 19:18:48 +0100 [thread overview]
Message-ID: <87fzhfsvzr.fsf@echidna.jochen.org> (raw)
In-Reply-To: Pine.LNX.4.58.0310261844580.8636@trider-g7.ext.fabbione.net
Fabio Massimo Di Nitto <fabbione@fabbione.net> writes:
> On Sun, 26 Oct 2003, Jochen Hein wrote:
>
>> Matthias Andree <matthias.andree@gmx.de> writes:
>>
>> > As 2.6 starts stabilizing, PLEASE try to synch up major components of
>> > 2.6 and 2.4 so that the same user space can be used for either version.
>> > It's fine with modutils and stuff, but when it comes to LVM, these 2.4
>> > and 2.6 versions are a problem.
>>
>> Debian SID contains lvm10, lvm2 and lvm-common, which can be installed
>> together and work for both kernels. Backport to woody was simple.
>
> this is true in terms of userland utils but you still need to perform a
> transition of kernels. 2.4 -> 2.4 + devicemapper patch -> 2.6.
No, I just did install 2.6 on my formerly 2.4-vanilla system!
> Until now i
> couldn't find a way to jump directly from 2.4 to 2.6 and converting from
> lvm1 to lvm2 at the same time.
lvm-common contains a program that decides what
iop-version/lvm-version/dm-version is running and calls the right
userland. So you have e.g.:
/sbin/vgchange: link to lvmiopversion. That decides to call
/lib/lvm-10/vgchange or /lib/lvm-2/vgchange depending on the kernel
stuff. Very helpful for me.
Jochen
--
#include <~/.signature>: permission denied
next prev parent reply other threads:[~2003-10-26 18:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 19:09 Linux 2.6.0-test9 Linus Torvalds
2003-10-25 19:52 ` Marcelo Tosatti
2003-10-25 20:14 ` viro
2003-10-25 22:35 ` Linus Torvalds
2003-10-25 23:45 ` Jose Luis Domingo Lopez
2003-10-26 0:22 ` 2.6.0-test9: selinux compile error with "make O=..." Adrian Bunk
2003-10-26 9:49 ` Sam Ravnborg
2003-10-27 13:40 ` Stephen Smalley
2003-10-27 18:42 ` Sam Ravnborg
2003-10-28 15:10 ` Stephen Smalley
2003-10-26 12:05 ` Linux 2.6.0-test9 Patrik Wallstrom
2003-10-27 18:21 ` Patrik Wallstrom
2003-10-27 22:51 ` bill davidsen
2003-10-28 2:12 ` Jeff Garzik
2003-10-28 4:52 ` Bill Davidsen
2003-10-26 15:05 ` Linux 2.4 <-> 2.6 compatibility (was: Linux 2.6.0-test9) Matthias Andree
2003-10-26 15:18 ` Linux 2.4 <-> 2.6 compatibility Måns Rullgård
2003-10-27 2:51 ` Matthias Andree
2003-10-26 16:06 ` Jochen Hein
2003-10-26 17:47 ` Fabio Massimo Di Nitto
2003-10-26 18:18 ` Jochen Hein [this message]
2003-10-27 16:02 ` Linux 2.6.0-test9 (compile stats) John Cherry
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=87fzhfsvzr.fsf@echidna.jochen.org \
--to=jochen@jochen.org \
--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