linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: venom@sns.it
To: Paul Jakma <paul@clubi.ie>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	Joe Thornber <thornber@sistina.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Device-mapper submission for 2.4
Date: Wed, 10 Dec 2003 17:54:08 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.43.0312101753040.24122-100000@cibs9.sns.it> (raw)
In-Reply-To: <Pine.LNX.4.56.0312101547590.1218@fogarty.jakma.org>


DM is back compatible with LVM1, tested and runs well.

Of course LVM1 has problems, but should we consider the DM case as mutch the
same as XFS?

Luigi

On Wed, 10 Dec 2003, Paul Jakma wrote:

> Date: Wed, 10 Dec 2003 15:55:53 +0000 (GMT)
> From: Paul Jakma <paul@clubi.ie>
> To: Martin J. Bligh <mbligh@aracnet.com>
> Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
>      Joe Thornber <thornber@sistina.com>, linux-kernel@vger.kernel.org
> Subject: Re: Device-mapper submission for 2.4
>
> On Tue, 9 Dec 2003, Martin J. Bligh wrote:
>
> > Some form of backward compatibility from 2.6 would seem a much more
> > sensible thing to fight for. Foisting forward comaptibility on an
> > older release seems like a bad road to go down.
>
> I dont really care, but some kind of (long-term, ie lifetime of
> either 2.4 or 2.6) compatibility is needed.
>
> LVM1 kernel support was recently removed from 2.6.0, so it would have
> to be added back in.
>
> One argument for adding forward compatibility in 2.4 is that it will
> /force/ people to move to DM before going to 2.6, which might be a
> good thing as, AIUI, LVM1 has problems.
>
> Its a choice between:
>
> - 2.6 backwards compatibility, adding back in LVM1 support, LVM1
> users will then quite possibly continue to use the problematical LVM1
> interfaces even after migrating to 2.6.
>
> - 2.4 forwards compatibility, add DM support - which appears (IMVU)
> to drop in cleanly alongside MD - and hence 2.6 can remain 'clean'.
>
> I dont know, but it would be nice to have /something/ and to have it
> in stock kernel rather than /hope/ to have upstreams include the
> required backward or forward compatibility.
>
> > M.
>
> regards,
> --
> Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
> 	warning: do not ever send email to spam@dishone.st
> Fortune:
> But it does move!
> 		-- Galileo Galilei
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


  reply	other threads:[~2003-12-10 16:54 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
2003-12-10  2:44                 ` Martin J. Bligh
2003-12-10 15:55                   ` Paul Jakma
2003-12-10 16:54                     ` venom [this message]
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
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=Pine.LNX.4.43.0312101753040.24122-100000@cibs9.sns.it \
    --to=venom@sns.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=mbligh@aracnet.com \
    --cc=paul@clubi.ie \
    --cc=thornber@sistina.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).