linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: venom@sns.it
To: jw schultz <jw@pegasys.ws>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.42
Date: Sun, 13 Oct 2002 13:58:58 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.43.0210131354020.9392-100000@cibs9.sns.it> (raw)
In-Reply-To: <20021012111140.GA22536@pegasys.ws>

On Sat, 12 Oct 2002, jw schultz wrote:

> Date: Sat, 12 Oct 2002 04:11:40 -0700
> From: jw schultz <jw@pegasys.ws>
> To: Kernel Mailing List <linux-kernel@vger.kernel.org>
> Subject: Re: Linux v2.5.42
>
>
> I'll add my $0.02US which (according to exchange rates) is
> worth more though almost worthless.
>
> Hate to say it but in this comparison LVM2 looses.  Primary
> reason: Backward compatibility.  People are going to need to
> be able to switch between kernels.
>
> So far everything indicates that LVM2 is not compatible with
> LVM.  That LVM2 and LVM(1) can coexist-exist is irrelevant if
> 2.5 hasn't got a working LVM(1).  And that would leave us
> with having to do backup+restore around the upgrade.

that is I think the real issue for people like me. One day I will have to
upgrade my servers to kernel 2.6, and all of them are on LVM1. I need to
be able to upgrade them. with EVMS I can do so, but after I will have
other problems because of operator, now used to LVM command line (that is
the same they are using on other Unices), will also have to learn another
command line. If I am not wrong, the LVM1 like command line is going to
disappear from EVMS, and that will be a problem for many users.
EVMS is powerfull but somehow too complex for many.
So my 2 eurocents are for EVMS with "also" a LVM1 like command line.

Luigi



  parent reply	other threads:[~2002-10-13 11:53 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12  4:59 Linux v2.5.42 Linus Torvalds
2002-10-12  5:53 ` Adrian Bunk
2002-10-12  7:23 ` Adrian Bunk
2002-10-12  7:52 ` Andres Salomon
2002-10-12  9:23   ` David S. Miller
2002-10-12  9:11 ` Adrian Bunk
2002-10-12  9:24 ` Adrian Bunk
2002-10-12  9:41   ` Sam Ravnborg
2002-10-12 10:21     ` Adrian Bunk
2002-10-12  9:50 ` Matthias Andree
2002-10-12 11:11   ` jw schultz
2002-10-12 11:29     ` Andres Salomon
2002-10-12 11:46     ` Alan Cox
2002-10-12 11:40       ` jw schultz
2002-10-12 17:47     ` Jon Portnoy
2002-10-12 18:10     ` Rik van Riel
2002-10-13 11:58     ` venom [this message]
2002-10-13 12:52       ` Michael Clark
2002-10-12 12:37 ` Ed Tomlinson
2002-10-12 13:32 ` Christoph Hellwig
2002-10-12 19:39   ` Andres Salomon
2002-10-12 13:43 ` Christoph Hellwig
2002-10-13 17:10   ` Dipankar Sarma
2002-10-14 10:01 ` Joe Thornber
2002-10-14 19:21   ` Christoph Hellwig
2002-10-14 19:32     ` Alexander Viro
2002-10-14 22:28     ` Joe Thornber
2002-10-12 17:14 Mark Peloquin
2002-10-12 19:34 ` Alan Cox
2002-10-12 19:37   ` jbradford
2002-10-13 23:55     ` Rob Landley
2002-10-13 12:41 ` [Evms-devel] " Michael Clark
2002-10-13 13:49   ` Christoph Hellwig
2002-10-13 15:16     ` Michael Clark
2002-10-13 15:35       ` Christoph Hellwig
2002-10-13 16:11         ` Brian Jackson
2002-10-13 16:26           ` Arjan van de Ven
2002-10-13 17:06             ` Brian Jackson
2002-10-13 19:58               ` Mark Hahn
2002-10-13 19:57                 ` Rik van Riel
2002-10-13 20:26                   ` Sean Neakums
2002-10-24 11:45                   ` Alexander Kellett
2002-10-13 19:59                 ` Andrew Morton
2002-10-13 20:24                 ` Bernd Eckenfels
2002-10-14 15:11                   ` Christoph Hellwig
2002-10-14 22:27                     ` Bernd Eckenfels
2002-10-13 17:46           ` Robert Love
2002-10-13 18:34             ` Brian Jackson
2002-10-14 14:45           ` Christoph Hellwig
2002-10-13 13:41 ` Christoph Hellwig
2002-10-12 20:20 Dieter Nützel
2002-10-12 22:19 ` Hans Reiser
2002-10-14 17:37 Ben Rafanello
2002-10-15  2:47 Paul McKenney
2002-10-15 17:43 Mark Peloquin

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.0210131354020.9392-100000@cibs9.sns.it \
    --to=venom@sns.it \
    --cc=jw@pegasys.ws \
    --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;
as well as URLs for NNTP newsgroup(s).