From: Christoph Hellwig <hch@caldera.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM and SPL
Date: Fri, 31 Aug 2001 14:59:03 +0200 [thread overview]
Message-ID: <20010831145903.A13324@caldera.de> (raw)
In-Reply-To: <20010831084053.A24948@otto.plogic.internal>; from rlatham@plogic.com on Fri, Aug 31, 2001 at 08:40:53AM -0400
On Fri, Aug 31, 2001 at 08:40:53AM -0400, Rob Latham wrote:
> sistina this week switched the license for the GFS tools from the GPL
> to the SPL
>
> http://www.sistina.com/Sistina%20Public%20License%201.0.pdf
>
> I'm worried now that Sistina will switch the license for LVM.
> However, considering there was almost a fork of the project (mostly)
> because of something as "simple" as mailing list policy, i guess
> openLVM would pop up again pretty quickly in that case... Is it
> concievable that the kernel patches will stay GPL'ed but a more
> restrictive license applied to the userspace tools ?
Even if just the userspace tools would switch to something even more
restrictive than GPL I'd go for OpenLVM. Just my 2 (Euro-)Cents.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-08-31 12:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rlatham@plogic.com>
2001-08-31 12:40 ` [linux-lvm] LVM and SPL Rob Latham
2001-08-31 12:59 ` Christoph Hellwig [this message]
2001-08-31 14:26 ` Jeff Layton
2001-08-31 18:11 ` Michael J. Declerck
2001-08-31 13:07 Chemolli Francesco (USI)
-- strict thread matches above, loose matches on Subject: below --
2001-08-31 15:06 Chemolli Francesco (USI)
2001-08-31 18:29 ` Jeff Layton
2001-08-31 19:02 ` Michael J. Declerck
2001-08-31 19:15 ` Jeff Layton
2001-09-03 8:42 Chemolli Francesco (USI)
2001-09-04 7:33 ` Luca Berra
2001-09-04 5:54 Gonyou, Austin
2001-09-04 10:41 ` Jeff Layton
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=20010831145903.A13324@caldera.de \
--to=hch@caldera.de \
--cc=linux-lvm@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.