public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Corry <kcorry@austin.rr.com>
To: Mike Diehl <mdiehl@dominion.dyndns.org>,
	evms-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Evms-devel] EVMS announcement
Date: Tue, 5 Nov 2002 18:36:02 -0600	[thread overview]
Message-ID: <02110518360200.00235@cygnus> (raw)
In-Reply-To: <20021105215100.E927E51CF@dominion.dyndns.org>

Hi Mike,

On Tuesday 05 November 2002 15:11, Mike Diehl wrote:
> Well, I'm a bit disapointed.  My experience with LVM has been nothing
> short of disasterous; EVMS looked like a very good alternative to LVM.
> Volume Management is one of the FEW things that Linux lacks that the
> "Big Boys" have.

I'm sorry you feel disappointed. But I assure you that EVMS will continue to 
provide the same experience you have come to expect. All this decision really 
means is that we will be building on a different kernel component, instead of 
providing our own. All of the EVMS tools and libraries will essentially be 
unchanged from the perspective of most users.

> The biggest thing that EVMS had going for it was it's modular design.  As I
> understand it, EVMS could even be used to manage the current MD and LVM
> drivers.  I was looking forward to partition-level encryption, etc.

And we will still maintain that modular design. In fact, we see this as 
making the design even more modular, since it won't have to be tied to a 
single kernel driver. Device mapper can be used for supporting disk 
partitions, LVM, and some other plugins. The MD driver can be used to support 
software RAID. We've even had thoughts about building on the existing loop 
driver in order to provide the partition-level encryption that you mentioned. 
And all of this from a single, unified interface.

> But never mind me.  I'm just a linux user, not a linux developer.

Actually, it *is* the users that we are most concerned with. This is why we 
are going to make such an effort to keep our tools as unchanged as possible. 
But we really do think that this is the best solution in the long term, for 
both the users and the developers.

If you continue to have any concerns about this, please let us know. We will 
do our best to address them and explain any other details about this change 
that you are unsure of.

-Kevin

  parent reply	other threads:[~2002-11-06  0:13 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 22:19 EVMS announcement Kevin Corry
2002-11-05 21:00 ` [Evms-announce] " Mike Diehl
2002-11-05 21:11   ` Mike Diehl
2002-11-05 23:53     ` Rik van Riel
2002-11-06  0:21     ` Alan Cox
2002-11-06  9:34       ` [Evms-devel] " Hendrik Visage
2002-11-06 13:55         ` Alan Cox
2002-11-06  0:36     ` Kevin Corry [this message]
2002-11-06  1:45       ` [Evms-devel] " Mike Diehl
2002-11-06  4:48         ` Alexander Viro
2002-11-06  2:54           ` Mike Diehl
2002-11-06 13:47         ` Kevin Corry
2002-11-05 23:40   ` [Evms-announce] " Andres Salomon
2002-11-05 21:29     ` Mike Diehl
2002-11-06  0:18   ` Andrew Clausen
2002-11-06 21:33     ` Matthias Andree
2002-11-07 10:37       ` Joe Thornber
2002-11-05 23:37 ` Alan Cox
2002-11-06  0:03 ` [Evms-devel] " Eff Norwood
2002-11-06  1:13   ` Rik van Riel
2002-11-06  1:41     ` Eff Norwood
2002-11-06  1:57       ` Rik van Riel
2002-11-06  2:50       ` Alexander Viro
2002-11-06  0:05 ` James H. Cloos Jr.
2002-11-06 15:21   ` Kevin Corry
2002-11-06  0:16 ` [Evms-announce] " Lars Marowsky-Bree
2002-11-06 13:55   ` Alan Cox
2002-11-06 13:59     ` Arjan van de Ven
2002-11-06 14:24       ` Jens Axboe
2002-11-06 20:46     ` H. Peter Anvin
2002-11-06 21:21       ` Alan Cox
2002-11-06 21:58         ` H. Peter Anvin
2002-11-08 18:06           ` Alan Cox
2002-11-08 19:37             ` H. Peter Anvin
2002-11-06 15:08   ` Kevin Corry
2002-11-07 20:24 ` Christoph Hellwig

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=02110518360200.00235@cygnus \
    --to=kcorry@austin.rr.com \
    --cc=evms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdiehl@dominion.dyndns.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