From: Jim McDonald <Jim@mcdee.net>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: linux-lvm@sistina.com, linux-kernel@vger.kernel.org,
lvm-devel@sistina.com
Subject: [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementation ready for beta testing
Date: Wed Jan 30 16:05:02 2002 [thread overview]
Message-ID: <1012428221.1750.253.camel@lapcat> (raw)
In-Reply-To: <20020130145408.I763@lynx.adilger.int>
On Wed, 2002-01-30 at 21:54, Andreas Dilger wrote:
> On Jan 30, 2002 20:22 +0000, Joe Thornber wrote:
> > Sistina is pleased to announce that the LVM2 software is ready for
> > beta testing.
> >
> > This is a complete reimplementation of the existing LVM system, both
> > driver and userland tools.
>
> What is the current and future licensing of the LVM2 code? Given the
> GFS events, I think people will be hesitant to accept an all-Sistina
> reimplementation of LVM.
Also, does/where does this fit in with EVMS?
Cheers,
Jim.
--
Jim McDonald - Jim@mcdee.net
WARNING: multiple messages have this Message-ID (diff)
From: Jim McDonald <Jim@mcdee.net>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: linux-lvm@sistina.com, linux-kernel@vger.kernel.org,
lvm-devel@sistina.com
Subject: Re: [lvm-devel] [ANNOUNCE] LVM reimplementation ready for beta testing
Date: 30 Jan 2002 22:03:40 +0000 [thread overview]
Message-ID: <1012428221.1750.253.camel@lapcat> (raw)
In-Reply-To: <20020130145408.I763@lynx.adilger.int>
In-Reply-To: <20020130202254.A7364@fib011235813.fsnet.co.uk> <20020130145408.I763@lynx.adilger.int>
On Wed, 2002-01-30 at 21:54, Andreas Dilger wrote:
> On Jan 30, 2002 20:22 +0000, Joe Thornber wrote:
> > Sistina is pleased to announce that the LVM2 software is ready for
> > beta testing.
> >
> > This is a complete reimplementation of the existing LVM system, both
> > driver and userland tools.
>
> What is the current and future licensing of the LVM2 code? Given the
> GFS events, I think people will be hesitant to accept an all-Sistina
> reimplementation of LVM.
Also, does/where does this fit in with EVMS?
Cheers,
Jim.
--
Jim McDonald - Jim@mcdee.net
next prev parent reply other threads:[~2002-01-30 16:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 14:23 [linux-lvm] [ANNOUNCE] LVM reimplementation ready for beta testing Joe Thornber
2002-01-30 20:22 ` Joe Thornber
2002-01-30 15:54 ` [linux-lvm] Re: [lvm-devel] " Andreas Dilger
2002-01-30 21:54 ` Andreas Dilger
2002-01-30 16:05 ` Jim McDonald [this message]
2002-01-30 22:03 ` Jim McDonald
2002-01-30 18:15 ` [linux-lvm] " Lars Kellogg-Stedman
2002-01-31 3:00 ` [linux-lvm] Re: [lvm-devel] " Joe Thornber
2002-01-30 16:37 ` James Hawtin
2002-01-31 5:31 ` Heinz J . Mauelshagen
2002-01-30 23:09 ` Joe Thornber
2002-01-31 3:08 ` [linux-lvm] " Joe Thornber
2002-01-30 19:48 ` [linux-lvm] " Daniel Phillips
2002-01-31 1:53 ` Daniel Phillips
2002-01-31 6:30 ` [linux-lvm] " Heinz J . Mauelshagen
2002-01-31 1:01 ` christophe barbé
2002-01-31 12:45 ` Heinz J . Mauelshagen
2002-01-31 18:42 ` Jeff Garzik
2002-02-01 9:03 ` Heinz J . Mauelshagen
2002-02-04 22:16 ` Bill Davidsen
2002-02-05 10:18 ` Heinz J . Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2002-01-31 13:54 [linux-lvm] Re: [lvm-devel] " Steve Pratt
2002-01-31 19:52 ` Steve Pratt
2002-01-31 12:52 ` Joe Thornber
2002-02-01 3:47 ` 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=1012428221.1750.253.camel@lapcat \
--to=jim@mcdee.net \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.com \
--cc=lvm-devel@sistina.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 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.