From: Jochen Hein <jochen@jochen.org>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: matthias.andree@gmx.de
Subject: Re: Linux 2.4 <-> 2.6 compatibility
Date: Sun, 26 Oct 2003 17:06:45 +0100 [thread overview]
Message-ID: <871xt0ouei.fsf@echidna.jochen.org> (raw)
In-Reply-To: <20031026150544.GJ15838@merlin.emma.line.org> (Matthias Andree's message of "Sun, 26 Oct 2003 16:05:45 +0100")
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.
Jochen
--
#include <~/.signature>: permission denied
next prev parent reply other threads:[~2003-10-26 16:15 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 [this message]
2003-10-26 17:47 ` Fabio Massimo Di Nitto
2003-10-26 18:18 ` Jochen Hein
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=871xt0ouei.fsf@echidna.jochen.org \
--to=jochen@jochen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.