From: Jose Luis Domingo Lopez <linux-kernel@24x7linux.com>
To: linux-kernel@vger.kernel.org
Subject: Re: evms or lvm?
Date: Sat, 23 Aug 2003 12:18:31 +0200 [thread overview]
Message-ID: <20030823101831.GA2857@localhost> (raw)
In-Reply-To: <3F47347F.7070103@mscc.huji.ac.il>
On Saturday, 23 August 2003, at 12:31:43 +0300,
Voicu Liviu wrote:
> I'm planing to move to 2.6x kernels and I don't know what should I use,
> lvm or evms, any 1 could help me to decide?
> I've heard that evms will not continue with 2.6, is it true?
> Best regards
>
2.6.0 will have many changes with respect to LVM and EVMS. LVM is
updated to newer version 2 (LVM2), based on DM (Device Mapper), sort of
a simplified in-kernel LVM that just handles discovering the drives.
Updated userspace utilities (LVM2) are already available to drive this.
On the other part, EVMS was completely redesigned. Former EVMS
implementation was duplicating too much code, and in general it was
regarded as a bad implementation on a very good idea, so the people at
IBM in charge on EVMS development took what it look to everyone as a
very clever move, and for 2.6.x they implemented EVMS on top of DM. User
space utilities for EVMS are (from the user's point of view) the same as
before, but now the inner details are different: no reimplementation of
software RAID, no reimplementation of LVM, etc.
Have a look at both projects websites to get more accurate and detailled
information about them:
http://evms.sourceforge.net/
http://www.sistina.com/products_lvm.htm
Regards,
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.6.0-test3-mm2)
next prev parent reply other threads:[~2003-08-23 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 9:31 evms or lvm? Voicu Liviu
2003-08-23 10:18 ` Jose Luis Domingo Lopez [this message]
2003-08-23 13:47 ` Wakko Warner
2003-08-23 14:16 ` Wichert Akkerman
2003-08-23 15:24 ` Voicu Liviu
2003-08-23 21:27 ` Jose Luis Domingo Lopez
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=20030823101831.GA2857@localhost \
--to=linux-kernel@24x7linux.com \
--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;
as well as URLs for NNTP newsgroup(s).