From: Christoph Hellwig <hch@infradead.org>
To: Kevin Corry <corryk@us.ibm.com>
Cc: evms-devel@lists.sourceforge.net,
evms-announce@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: EVMS announcement
Date: Thu, 7 Nov 2002 20:24:38 +0000 [thread overview]
Message-ID: <20021107202438.A7960@infradead.org> (raw)
In-Reply-To: <02110516191004.07074@boiler>; from corryk@us.ibm.com on Tue, Nov 05, 2002 at 04:19:10PM -0600
On Tue, Nov 05, 2002 at 04:19:10PM -0600, Kevin Corry wrote:
> Greetings EVMS users,
>
> On behalf of the EVMS team, we would like to announce a significant change
> in direction for the Enterprise Volume Management System project.
>
> As many of you may know by now, the 2.5 kernel feature freeze has come
> and gone, and it seems clear that the EVMS kernel driver is not going
> to be included. With this in mind, we have decided to rework the EVMS
> user-space administration tools (the Engine) to work with existing
> drivers currently in the kernel, including (but not necessarily limited
> to) device mapper and MD.
Hi Kevin,
I think that's a very good move for EVMS in the long term. You will
be able to provide the users what they want (an easy to user and
integrated volume managment solution) without having the pain of
maintaining a large base of kernel-level code.
Of course there will be some hassle for you now, like adding DM plugins
for higher raid levels, etc.. But in the end I guess it will hope both
EVMS and Linux. EVMS by reducing the scope of the project without
reducing it's functionality, the Linux by having a modular and leight-weight
in kernel volume-managment solution with many eyes looking at it, using
it and improving it. I guess you will find a bunch of suboptimal things
in DM very soon and I hope you will help the kernel community in fixing
it. This of course means also that DM will hopefully get an integral part
of the kernel, not an Sistina Project like LVM1.
I (and I guess many other kernel developers interested in storage
handling) will look forward to the comments who the current kernel-level
storage managment facilities are useable by an unified userland engine
handling it, and I guess mthere will be many obvious improvement.
I'm also looking forward to IBM's opensource cluster volumemanagment
integration as competitions to Sistina's propritary addons.
I wish you all luck with your new direction and expect me and other kernel
developers in that area to help you wherever we can.
Christoph
prev parent reply other threads:[~2002-11-07 20:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 22:19 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 ` [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 [this message]
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=20021107202438.A7960@infradead.org \
--to=hch@infradead.org \
--cc=corryk@us.ibm.com \
--cc=evms-announce@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®