From: "Matthew O'Keefe" <okeefe@borg.umn.edu>
To: linux-lvm@sistina.com
Cc: Matthew O'Keefe <okeefe@brule.borg.umn.edu>
Subject: Re: [linux-lvm] Working together
Date: Sat, 19 May 2001 11:37:54 -0500 [thread overview]
Message-ID: <20010519113754.A14371@brule.borg> (raw)
In-Reply-To: <OF97CFF081.B6DCBCCA-ON85256A50.004CE72A@raleigh.ibm.com>
On Fri, May 18, 2001 at 09:01:49AM -0500, Mark Peloquin wrote:
> Hello everyone,
>
>
> > Why should Linux LVM join the EVMS project ?
>
> The EVMS project can offer some immediate solutions to current Linux LVM
> issues.
>
> - EVMS supports in-kernel reading/writing of metadata
>
> - EVMS supports in-kernel discovery of volume groups and volumes
>
Hi,
does the EVMS code work in production today? If not, then saying
it "can offer some immediate solutions to current Linux LVM issues"
is inaccurate. That said, its great to see another alternative
LVM appearing on the horizon for Linux.
Matt O'Keefe
Sistina Software, Inc.
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
next prev parent reply other threads:[~2001-05-19 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 14:01 [linux-lvm] Working together Mark Peloquin
2001-05-18 16:27 ` Heinz J. Mauelshagen
2001-05-20 5:44 ` Tracy R Reed
2001-05-21 14:58 ` Heinz J. Mauelshagen
2001-05-19 16:37 ` Matthew O'Keefe [this message]
2001-05-23 9:51 ` Heinz J. Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2001-05-19 19:54 Mark Peloquin
2001-05-21 18:42 Ben Rafanello
2001-05-23 15:33 Mark Peloquin
2001-05-23 20:48 ` Heinz J. Mauelshagen
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=20010519113754.A14371@brule.borg \
--to=okeefe@borg.umn.edu \
--cc=linux-lvm@sistina.com \
--cc=okeefe@brule.borg.umn.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 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.