linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Andreas Dilger <adilger@clusterfs.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Lars Marowsky-Bree <lmb@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove LVM from 2.5 (resend)
Date: Thu, 03 Oct 2002 13:50:05 +0800	[thread overview]
Message-ID: <3D9BDA8D.5080700@metaparadigm.com> (raw)
In-Reply-To: Pine.GSO.4.21.0210021922200.13480-100000@weyl.math.psu.edu

On 10/03/02 07:22, Alexander Viro wrote:
> 
> On Wed, 2 Oct 2002, Andreas Dilger wrote:
> 
> 
>>On Oct 02, 2002  23:46 +0100, Alan Cox wrote:
>>
>>>Absolutely - taking the core EVMS(say the core code and the bits to do
>>>LVM1) and polishing them up to be good clean citizens without code
>>>duplication and other weirdness would be a superb start for EVMS as a
>>>merge candidate. The rest can follow a piece at a time once the core is
>>>right if EVMS is the right path
>>
>>I actually see EVMS as the "VFS for disk devices".  It is a very good
>>way to at allow dynamic disk device allocation, and could relatively
>>easily be modified to use all of the "legacy" disk major devices and
>>export only real partitions (one per minor).
>>
>>You could have thousands of disks and partitions without the current
>>limitations on major/minor device mapping.
>>
>>This was one of the things that Linus was pushing for when 2.5 started.
> 
> 
> ... and you don't need EVMS for that.

But EVMS would be an excellent substitute in the mean time.

Better to having something excellent now than something perfect but
too late.

The EVMS guys have done a great job of cleanly integrating with 2.5,
the single additional interface they needed to add to genhd.c is
testament to their consideration of these issues.

IBM seem to have done a great job creating the most extensive and
complete logical volume manager for Linux (including a suite of end
user tools much more extensive than LVM). They have also shown the
commitment to keep it current and cleary are way further ahead than
any other contender. It would be horrible if not getting the nod from
the right friends deprived users of a *complete* logical volume manager
in 2.5 anytime soon.

Peace, love and Linux ;)

~mc


  reply	other threads:[~2002-10-03  5:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 14:06 [PATCH] Remove LVM from 2.5 (resend) Joe Thornber
2002-10-01 14:15 ` Alexander Viro
2002-10-01 14:52   ` venom
2002-10-01 15:48     ` Dave Jones
2002-10-01 16:06       ` Jens Axboe
2002-10-01 16:35         ` Joe Thornber
2002-10-01 16:41           ` Jens Axboe
2002-10-01 23:19             ` venom
2002-10-01 18:42       ` Lars Marowsky-Bree
2002-10-02  1:00         ` Alan Cox
2002-10-02  4:24           ` Theodore Ts'o
2002-10-02 13:34             ` Alan Cox
2002-10-02 14:54               ` Lars Marowsky-Bree
2002-10-02 17:09                 ` Alan Cox
2002-10-02 22:29                   ` Lars Marowsky-Bree
2002-10-02 22:46                     ` Alan Cox
2002-10-02 23:14                       ` Andreas Dilger
2002-10-02 23:22                         ` Alexander Viro
2002-10-03  5:50                           ` Michael Clark [this message]
2002-10-03 12:38                             ` Alan Cox
2002-10-03 14:09                               ` Michael Clark
2002-10-03 15:07                                 ` Shawn
2002-10-03 15:22                                   ` Michael Clark
2002-10-06  5:05                                     ` GrandMasterLee
2002-10-01 19:12       ` Matthias Andree
2002-10-01 23:25         ` venom
2002-10-01 17:09   ` Status of InterMezzo in 2.5 Andreas Dilger
2002-10-01 14:40 ` [PATCH] Remove LVM from 2.5 (resend) Jens Axboe
2002-10-01 14:54   ` Joe Thornber

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=3D9BDA8D.5080700@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=adilger@clusterfs.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@suse.de \
    --cc=viro@math.psu.edu \
    /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).