From: venom@sns.it
To: Matthias Andree <matthias.andree@gmx.de>
Cc: linux-kernel@vger.kernel.org,
Dave Jones <davej@codemonkey.org.uk>,
Alexander Viro <viro@math.psu.edu>,
Joe Thornber <joe@fib011235813.fsnet.co.uk>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] Remove LVM from 2.5 (resend)
Date: Wed, 2 Oct 2002 01:25:58 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.43.0210020124240.16927-100000@cibs9.sns.it> (raw)
In-Reply-To: <20021001191249.GJ15537@merlin.emma.line.org>
EVMS is powerfull, but actually has a so ugly command line...
fortunatelly EVMS architecture command line could be exchanged...
On Tue, 1 Oct 2002, Matthias Andree wrote:
> Date: Tue, 1 Oct 2002 21:12:49 +0200
> From: Matthias Andree <matthias.andree@gmx.de>
> To: linux-kernel@vger.kernel.org
> Cc: Dave Jones <davej@codemonkey.org.uk>, venom@sns.it,
> Alexander Viro <viro@math.psu.edu>,
> Joe Thornber <joe@fib011235813.fsnet.co.uk>,
> Linus Torvalds <torvalds@transmeta.com>
> Subject: Re: [PATCH] Remove LVM from 2.5 (resend)
>
> On Tue, 01 Oct 2002, Dave Jones wrote:
>
> > On Tue, Oct 01, 2002 at 04:52:44PM +0200, venom@sns.it wrote:
> > > A Logical Volume Manager is needed on Unix servers, and so it is needed
> > > also on Linux.
> > > If this LVM is obsoleted, then when will LVM2 be merged?
> > > really we cannot have a 2.6 or 3.0 tree without a Volume Manager, it would
> > > be a big fault.
> >
> > No-one suggested 2.6.0 shipping without /something/, but having a dead
> > LVM1 in _2.5_ doesn't help anyone. We've gone 6 months with it being in
> > a broken/uncompilable state, going another month without it isn't a big
> > deal. Getting something in before halloween is however a goal the
> > Sistina folks should be aiming for.
>
> How about EVMS kernel-space merge instead?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-10-01 23:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 14:06 [PATCH] Remove LVM from 2.5 (resend) Joe Thornber
2002-10-01 14:15 ` Alexander Viro
2002-10-01 14:52 ` venom
2002-10-01 15:48 ` Dave Jones
2002-10-01 16:06 ` Jens Axboe
2002-10-01 16:35 ` Joe Thornber
2002-10-01 16:41 ` Jens Axboe
2002-10-01 23:19 ` venom
2002-10-01 18:42 ` Lars Marowsky-Bree
2002-10-02 1:00 ` Alan Cox
2002-10-02 4:24 ` Theodore Ts'o
2002-10-02 13:34 ` Alan Cox
2002-10-02 14:54 ` Lars Marowsky-Bree
2002-10-02 17:09 ` Alan Cox
2002-10-02 22:29 ` Lars Marowsky-Bree
2002-10-02 22:46 ` Alan Cox
2002-10-02 23:14 ` Andreas Dilger
2002-10-02 23:22 ` Alexander Viro
2002-10-03 5:50 ` Michael Clark
2002-10-03 12:38 ` Alan Cox
2002-10-03 14:09 ` Michael Clark
2002-10-03 15:07 ` Shawn
2002-10-03 15:22 ` Michael Clark
2002-10-06 5:05 ` GrandMasterLee
2002-10-01 19:12 ` Matthias Andree
2002-10-01 23:25 ` venom [this message]
2002-10-01 17:09 ` Status of InterMezzo in 2.5 Andreas Dilger
2002-10-01 14:40 ` [PATCH] Remove LVM from 2.5 (resend) Jens Axboe
2002-10-01 14:54 ` Joe Thornber
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=Pine.LNX.4.43.0210020124240.16927-100000@cibs9.sns.it \
--to=venom@sns.it \
--cc=davej@codemonkey.org.uk \
--cc=joe@fib011235813.fsnet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).