From: Samuel Flory <sflory@rackable.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: Mike Fedyk <mfedyk@matchmail.com>,
Stan Bubrouski <stan@ccs.neu.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: is it possible to have a kernel module with a BSD license?!
Date: Fri, 26 Dec 2003 12:14:21 -0800 [thread overview]
Message-ID: <3FEC969D.4080502@rackable.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0312241510150.7586@dlang.diginsite.com>
David Lang wrote:
> the question comes back to looking if it's derived from the linux kernel.
>
> if it is then it must be GPL (GPL doesn't allow anything else)
>
> if it isn't then it can be becouse the GPL is compatable with BSD code.
> (it becomes GPL for purposes of the kernel, but is also available for
> other uses under the BSD license)
>
> however the big question as always remains 'is this derived from the
> kernel code'
Well it's obviously derived if any of the following is true:
1)You are using any linux you borrowed from gpl sources.
2)The module uses a lot internal kernel hooks.
Linus claims that is it's derived if:
1)It only supports linux. (He's got a point.)
2)It was originally written for linux. (I'd disagree, but IANAL)
Certainly you'd have a leg to stand on if:
1)The module was really cross platform. (Extra points for it working on
*BSD, or the like 1st.)
2)The linux headers are clearly marked gpl.
3)Every accessing internal linux kernel functions was in the linux headers.
4)Everything in the module was gpl, or bsd. (Less to do things being
derived than with if you can legally use the result.)
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-12-26 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 15:17 is it possible to have a kernel module with a BSD license?! Bruce Ferrell
2003-12-24 16:10 ` Arjan van de Ven
2003-12-24 22:11 ` Mike Fedyk
2003-12-24 23:12 ` Samuel Flory
2003-12-25 8:33 ` Arjan van de Ven
2003-12-24 22:01 ` Stan Bubrouski
2003-12-24 22:10 ` Mike Fedyk
2003-12-24 23:34 ` David Lang
2003-12-26 20:14 ` Samuel Flory [this message]
2003-12-27 14:51 ` Helge Hafting
2003-12-28 15:27 ` Ryan Anderson
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=3FEC969D.4080502@rackable.com \
--to=sflory@rackable.com \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=stan@ccs.neu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox