public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: Kevin Corry <corryk@us.ibm.com>, evms-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Evms-announce] EVMS announcement
Date: Wed, 6 Nov 2002 01:16:07 +0100	[thread overview]
Message-ID: <20021106001607.GJ27832@marowsky-bree.de> (raw)
In-Reply-To: <02110516191004.07074@boiler>

On 2002-11-05T16:19:10,
   Kevin Corry <corryk@us.ibm.com> said:

Kevin,

this must have been a very painful decision. I publically applaud you for
making it.

The great benefit from EVMS is the unified toolset for the administrator. It
is impressive that you are willing to rework this on top of a "Not Invented
Here" framework. I'm not sure whether my ego would have allowed the same
decision ;-)

The Device-Mapper seems to appeal more to the kernel community (and I'll agree
it is quite impressively neat code), and the EVMS management aspect appeals to
users. I hope that merging these will appeal to all. (It certainly does to
me).

I'm most certainly looking forward to seeing the clustering support comeing
;-)

Now, an interesting question is whether the md modules etc will simply be
continued to be used or whether they'll make use of the DM engine too? Can
they be made "plugins" to DM or the EVMS framework? Or even, could EVMS (in
theory) parse the meta-data from a legacy md device and just setup a DM
mapping for it? That would appeal to me quite a bit. I really need to start
reading up on it...


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
Principal Squirrel 
SuSE Labs - Research & Development, SuSE Linux AG
  
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
  -- Capt. Edward A. Murphy            -- Louis Pasteur

  parent reply	other threads:[~2002-11-06  0:09 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     ` [Evms-devel] " Kevin Corry
2002-11-06  1:45       ` 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 ` Lars Marowsky-Bree [this message]
2002-11-06 13:55   ` [Evms-announce] " 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=20021106001607.GJ27832@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=corryk@us.ibm.com \
    --cc=evms-devel@lists.sourceforge.net \
    --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