Re: module license taints kernel.
- From: Bob Tennent <BobT@xxxxxxxxxxxxx>
- Date: 20 Nov 2007 17:14:26 GMT
On Tue, 20 Nov 2007 08:49:27 -0800 (PST), David Schwartz wrote:
On Nov 19, 12:21 pm, Bob Tennent <B...@xxxxxxxxxxxxx> wrote:
So if I take a copyrighted work, apply rot13 to it, the result can be
freely distributed? I rather doubt it.
The fact that you applied rot13 to it has no legal consequence
whatsoever. It's still, for legal purposes, the original work. You can
do anything with it you could do with the original work.
But one cannot distribute or modify a copyrighted work except as
licensed by the copyright holder; so that would apply to a non-creative
modification as well.
In any case, linking with a non-GPLed module isn't like this. The
linking may be non-creative and automatic, but the module itself isn't.
We're not getting anywhere. All I can say is: tell it to the judge.
Bob T.
.
- Follow-Ups:
- Re: module license taints kernel.
- From: David Schwartz
- Re: module license taints kernel.
- References:
- module license taints kernel.
- From: guru
- Re: module license taints kernel.
- From: Bob Tennent
- Re: module license taints kernel.
- From: Chris Friesen
- Re: module license taints kernel.
- From: Bob Tennent
- Re: module license taints kernel.
- From: David Schwartz
- Re: module license taints kernel.
- From: Bob Tennent
- Re: module license taints kernel.
- From: David Schwartz
- Re: module license taints kernel.
- From: Bob Tennent
- Re: module license taints kernel.
- From: David Schwartz
- Re: module license taints kernel.
- From: Bob Tennent
- Re: module license taints kernel.
- From: David Schwartz
- module license taints kernel.
- Prev by Date: Re: lseek/write
- Next by Date: Re: shell command wrapper
- Previous by thread: Re: module license taints kernel.
- Next by thread: Re: module license taints kernel.
- Index(es):