public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn <core@enodev.com>
To: Christoph Hellwig <hch@infradead.org>, Shawn <core@enodev.com>,
	Michael Clark <michael@metaparadigm.com>,
	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:47:30 -0500	[thread overview]
Message-ID: <20021014164730.B28737@q.mn.rr.com> (raw)
In-Reply-To: <20021014172137.D19897@infradead.org>; from hch@infradead.org on Mon, Oct 14, 2002 at 05:21:37PM +0100

On 10/14, Christoph Hellwig said something like:
> On Mon, Oct 14, 2002 at 09:20:48AM -0500, Shawn wrote:
> > Having said all that, given that your premises are true regarding the
> > code design problems you have with EVMS, you have a valid point about
> > including it in mainline. The question is, is this good enough to ignore
> > having a logical device management system?!?
> 
> It is not good enough to ignore it.  It is good enough to postpone
> integration for 2.7.

I just wish logical volume management in general had not been so
abandoned in mainline in the first place. I'm not saying Linus unfairly
excluded patches, and I'm not saying patches weren't available. I'm just
saying the dynamics of Linus and the maintainers did not allow for a
healthy LVM in mainline, resulting in decay.

If LVM1's destiny was to die during 2.5, then I wish there would have
been a replacement ready during 2.5's lifecycle. Otherwise, keep
creaking along with what's there, and fix it.

The larger question of volume management should have been addressed
before this whole mess happened. It really was, but LVM1 maintenance was
somewhat abandoned in favor of device mapper, and now it's broken, and
the holy wars are upon us again because many are in fear of losing
functionality important to them (at least the ubiquitous nature of the
functonality), and there is panic.

> Now that Al has sorted out lots of the block device mess in 2.5
> I will work together with whoever is interested in it (i.e. the EVMS
> folks) to integrate proper higher-level volume-management into
> the kernel once the next unstable series opens.

I look forward to it. In spite of my personal goals on this, I do
appreciate your pickiness.

> Coing up with lots of code just before feature freeze is just not the way
> infrastructure work is done Linux.

I just wish there were less veto-esque ways to handle EVMS in *-stable.

--
Shawn Leas
core@enodev.com

I put my air conditioner in backwards.  It got cold outside.
The weatherman on TV was confused.  "It was supposed to be hot
today."
						-- Stephen Wright

  parent reply	other threads:[~2002-10-14 21:42 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12 17:14 Linux v2.5.42 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
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=20021014164730.B28737@q.mn.rr.com \
    --to=core@enodev.com \
    --cc=evms-devel@lists.sourceforge.net \
    --cc=hch@infradead.org \
    --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