public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] LVM reimplementation ready for beta testing
Date: Fri, 1 Feb 2002 10:03:03 +0100	[thread overview]
Message-ID: <20020201100303.A14415@sistina.com> (raw)
In-Reply-To: <20020130202254.A7364@fib011235813.fsnet.co.uk> <20020131010119.GB858@ufies.org> <20020131134533.A10295@sistina.com> <20020131134225.B32321@havoc.gtf.org>
In-Reply-To: <20020131134225.B32321@havoc.gtf.org>; from garzik@havoc.gtf.org on Thu, Jan 31, 2002 at 01:42:25PM -0500

On Thu, Jan 31, 2002 at 01:42:25PM -0500, Jeff Garzik wrote:
> On Thu, Jan 31, 2002 at 01:45:33PM +0100, Heinz J . Mauelshagen wrote:
> > LVM2 and the device-mapper are GPL/LGPL.
> 
> Could you clarify the meaning of "GPL/LGPL"?  Are certain parts GPL and
> other parts LGPL?  If so, which parts?

The LVM2 sofware no longer uses a particular driver which is just
usable for its own purpose.
It rather accesses a different, so-called 'device-mapper' driver, which
implements a generic volume management service for the Linux kernel by
supporting arbitray mappings of address ranges to underlying block devices.
Because this is a generic service rather than an application within the kernel,
it is open to be used by multiple LVM implementations (for eg. EVMS could be
ported to use it :-)

The device-mapper driver is under the GPL and our Beta1 release dated Wednesday,
which included the LVM2 tools as well, supports 2.4 kernels. We are aiming to
get it integrated into the stock kernel and are implementing the necessary
changes (bio interface) for 2.5 now.
We released a device-mapper library (implements a generic API for the
device-mapper) which is under the LGPL with it.

The LVM2 tools have a library with routines to for eg. access the
device-mapper library, deal with LVM metadata (VGDA), support different
metadata formats and offer configuration file support which is under the
LGPL as well.
The tools themselves (vgcreate, lvcreate, ...) are under the GPL.

IOW:

GPL				LGPL
-----------------------------   ------------------------------
LVM2 tools			LVM2 library
device-mapper driver		device-mapper library

> 
> 	jeff
> 
> 

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-02-01  9:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 20:22 [ANNOUNCE] LVM reimplementation ready for beta testing Joe Thornber
2002-01-30 21:54 ` [lvm-devel] " Andreas Dilger
2002-01-30 22:03   ` Jim McDonald
2002-01-30 23:09   ` Joe Thornber
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 [this message]
2002-02-04 22:16         ` Bill Davidsen
2002-02-05 10:18           ` Heinz J . Mauelshagen
2002-01-31  1:53 ` Daniel Phillips
  -- strict thread matches above, loose matches on Subject: below --
2002-01-31 19:52 [linux-lvm] Re: [lvm-devel] " Steve Pratt
2002-01-31 12:52 ` Joe Thornber
2002-02-01  9:55   ` [Evms-devel] " Arjan van de Ven
2002-01-31 13:09     ` Joe Thornber
2002-02-01 10:12       ` Arjan van de Ven
2002-01-31 13:35         ` Joe Thornber
2002-02-01 14:44         ` Alan Cox

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=20020201100303.A14415@sistina.com \
    --to=mauelshagen@sistina.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