All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: Erik Mouw <erik@harddisk-recovery.com>
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 09:11:48 -0400	[thread overview]
Message-ID: <4540B414.7040406@compro.net> (raw)
In-Reply-To: <20061026121041.GB12420@harddisk-recovery.com>

Erik Mouw wrote:
> 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
> 

Any Holy IP I might have would be GPL. It's just I know of some that isn't and I
can't understand why it isn't. I'm not looking for legal advise. Just opinions.

Some code is added directly to the kernel source tree. A user land library is
written to access the changes. It is not GPL or LGPL. Simple scenario. No? I
thought so at least.

With all the complex and detailed (way over my head) discussions of the GPL-V2
vs. V3 that the list has had recently, I don't understand how something so
simple as this scenario would require legal advise to know if it were OK or not.



Thanks anyway
Mark

  reply	other threads:[~2006-10-26 13:11 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
2006-10-26 13:11       ` Mark Hounschell [this message]
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=4540B414.7040406@compro.net \
    --to=markh@compro.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dmarkh@cfl.rr.com \
    --cc=erik@harddisk-recovery.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 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.