From: Erik Mouw <erik@harddisk-recovery.com>
To: Mark Hounschell <markh@compro.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
dmarkh@cfl.rr.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Another kernel releated GPL ?
Date: Thu, 26 Oct 2006 14:10:41 +0200 [thread overview]
Message-ID: <20061026121041.GB12420@harddisk-recovery.com> (raw)
In-Reply-To: <45409BFA.8000507@compro.net>
On Thu, Oct 26, 2006 at 07:28:58AM -0400, Mark Hounschell wrote:
> Alan Cox wrote:
> > Ask your lawyer. It depends on the legal definition of "derivative
> > work", which isn't something a kernel developer can really answer.
> >
>
> I'm sure every lawyer will have his own opinion. In the end won't it come down
> to the intent of the kernel developer? Surly the definition of "derivative work"
> has to be, or has been already, defined by someone other than a lawyer or court
> that knows nothing of "kernel development"?
"Derivative work" is defined by copyright law, not by some random
kernel hackers. You should really consult a lawyer.
If legal advise is too expensive, then your Most Holy IP apparently
isn't worth that much and you'd rather release it under GPL.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2006-10-26 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 9:45 Another kernel releated GPL ? Mark Hounschell
2006-10-26 11:12 ` Alan Cox
2006-10-26 11:28 ` Mark Hounschell
2006-10-26 11:48 ` Alan Cox
2006-10-26 11:54 ` Pekka Enberg
2006-10-26 12:10 ` Erik Mouw [this message]
2006-10-26 13:11 ` Mark Hounschell
2006-10-26 14:21 ` Alan Cox
2006-10-26 15:02 ` Mark Hounschell
2006-10-26 16:17 ` Alan Cox
2006-10-26 16:24 ` Vadim Lobanov
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=20061026121041.GB12420@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dmarkh@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/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