From: Kevin Corry <kevcorry@us.ibm.com>
To: linux-lvm@sistina.com, Greg Freemyer <freemyer@NorcrossGroup.com>,
"Anastasios A. Papadopoulos (Tas)" <vze2sjj7@verizon.net>
Cc: EVMS <evms-devel@lists.sourceforge.net>
Subject: Re: [linux-lvm] What are they talking about?
Date: Wed May 21 16:12:02 2003 [thread overview]
Message-ID: <200305211603.39641.kevcorry@us.ibm.com> (raw)
In-Reply-To: <20030521204843.ZNFH1333.imf40bis.bellsouth.net@tiger2>
On Wednesday 21 May 2003 15:53, Greg Freemyer wrote:
> Kevin,
>
> I understand how LVM2, DM, and EVMS are architected.
>
> I still have no idea what the article is talking about.
>
> Are you saying that the referenced sources just don't understand how it all
> works and that the "industrial-strength Logical Volume Manager" they want
> is achievable via the current DM implementation in combination with
> appropriate high quality user-space tools?
Yes, that would be my opinion. DM provides all of the infrastructure that the
kernel requires. (It can be further enhanced by adding sub-modules
("targets") to provide new ways to map devices). Then it's up to the
user-space tools to figure out how to best use this infrastructure.
> That certainly agrees with what I thought and why I was so confused by the
> article.
I was quite confused by the article as well. :)
--
Kevin Corry
kevcorry@us.ibm.com
http://evms.sourceforge.net/
next prev parent reply other threads:[~2003-05-21 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 15:46 re[2]: [linux-lvm] What are they talking about? Greg Freemyer
2003-05-21 16:12 ` Kevin Corry [this message]
2003-05-21 16:24 ` Alasdair G Kergon
-- strict thread matches above, loose matches on Subject: below --
2003-05-21 14:12 Steve Pratt
2003-05-21 11:59 Greg Freemyer
2003-05-21 12:42 ` Anastasios A. Papadopoulos (Tas)
2003-05-21 14:46 ` Kevin Corry
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=200305211603.39641.kevcorry@us.ibm.com \
--to=kevcorry@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=freemyer@NorcrossGroup.com \
--cc=linux-lvm@sistina.com \
--cc=vze2sjj7@verizon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.