From: Christoph Hellwig <hch@infradead.org>
To: Michael Clark <michael@metaparadigm.com>
Cc: Mark Peloquin <markpeloquin@hotmail.com>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com,
evms-devel@lists.sourceforge.net
Subject: Re: [Evms-devel] Re: Linux v2.5.42
Date: Mon, 14 Oct 2002 16:15:45 +0100 [thread overview]
Message-ID: <20021014161545.B17683@infradead.org> (raw)
In-Reply-To: <3DA99CEC.8040208@metaparadigm.com>; from michael@metaparadigm.com on Mon, Oct 14, 2002 at 12:18:52AM +0800
On Mon, Oct 14, 2002 at 12:18:52AM +0800, Michael Clark wrote:
> one you decides. At the end of the day it is just another 'driver'
> and I don't think it's fair to place a higher benchmark of quality
> on EVMS than all the other drivers in the kernel
If you followed lkml you'll see that I even explain authors of
very small drivers how to fit the kernel standards. The situation
with those is a little different as they are not a framework and
don't add new APIs. Thus it's only a correctness and style issues.
EVMS on the other hand is not only a lot of code but also a framework,
i.e. it folows certain design principles. And I fundamentally
disagree with some of those.
> Some of us have large arrays and SANs where the absence a volume
> manager is a big thing.
Not having EVMS ~= not having a volume manager. I don't want
to have to manage my storage farms without a volume manager either,
but that doesn't have to mean that I like the EVMS design.
next prev parent reply other threads:[~2002-10-14 15:10 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
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-14 4:55 ` [Evms-devel] " Andreas Dilger
2002-10-13 17:46 ` Robert Love
2002-10-13 18:34 ` Brian Jackson
2002-10-14 4:23 ` [Evms-devel] " Andreas Dilger
2002-10-14 16:08 ` Christoph Hellwig
2002-10-14 14:45 ` Christoph Hellwig
2002-10-13 16:18 ` [Evms-devel] " Michael Clark
2002-10-13 17:10 ` Alexander Viro
2002-10-13 17:41 ` Michael Clark
2002-10-14 4:43 ` Andreas Dilger
2002-10-14 16:16 ` Christoph Hellwig
2002-10-14 15:21 ` Christoph Hellwig
2002-10-14 14:42 ` Shawn
2002-10-14 15:15 ` Christoph Hellwig [this message]
2002-10-14 14:20 ` Shawn
2002-10-14 16:15 ` Rik van Riel
2002-10-14 21:34 ` Shawn
2002-10-14 16:21 ` Christoph Hellwig
2002-10-14 16:38 ` Jeff Garzik
2002-10-14 21:47 ` Shawn
2002-10-15 7:42 ` Heinz J . Mauelshagen
2002-10-14 21:48 ` Oliver Neukum
2002-10-14 21:55 ` Shawn
2002-10-14 22:35 ` Oliver Neukum
2002-10-14 22:53 ` Shawn
2002-10-14 23:04 ` Oliver Neukum
2002-10-14 23:16 ` Alexander Viro
2002-10-14 23:30 ` Oliver Neukum
2002-10-15 0:10 ` Andrew Clausen
2002-10-14 22:57 ` Alexander Viro
2002-10-13 13:41 ` Christoph Hellwig
2002-10-14 23:57 [Evms-devel] " Mark Peloquin
2002-10-15 14:51 Steve Pratt
2002-10-15 21:18 ` Andrew Clausen
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=20021014161545.B17683@infradead.org \
--to=hch@infradead.org \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=markpeloquin@hotmail.com \
--cc=michael@metaparadigm.com \
--cc=torvalds@transmeta.com \
/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
Powered by JetHome