linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.42
Date: Sat, 12 Oct 2002 04:40:36 -0700	[thread overview]
Message-ID: <20021012114036.GB22536@pegasys.ws> (raw)
In-Reply-To: <1034423197.14382.2.camel@irongate.swansea.linux.org.uk>

On Sat, Oct 12, 2002 at 12:46:37PM +0100, Alan Cox wrote:
> On Sat, 2002-10-12 at 12:11, jw schultz wrote:
> > 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.
> 
> LVM2 supports LVM1 volumes. I don't know where you got the idea
> otherwise. 

Good.  I'm very glad to be wrong.  Then all we need care
about is project maturity and design.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

  reply	other threads:[~2002-10-12 11:34 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 [this message]
2002-10-12 17:47     ` Jon Portnoy
2002-10-12 18:10     ` Rik van Riel
2002-10-13 11:58     ` venom
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=20021012114036.GB22536@pegasys.ws \
    --to=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).