Re: module license taints kernel.
- From: David Schwartz <davids@xxxxxxxxxxxxx>
- Date: Tue, 20 Nov 2007 08:49:27 -0800 (PST)
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.
I've already decided I can't depend on *your* characterization of
copyright law.
Then explain where you disagree with it.
I've already stated IANAL; what about you? Frankly, I'll
trust Eben Moglen, Professor of Law, Columbia Law School, who wouldn't
have allowed the statements I've quoted if the restrictions weren't
within the scope of copyright law.
You might as well ask the client's attorney if the client is innocent.
DS
.
- Follow-Ups:
- Re: module license taints kernel.
- From: Bob Tennent
- 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
- module license taints kernel.
- Prev by Date: Re: Running an application on startup in embedded linux
- Next by Date: shell command wrapper
- Previous by thread: Re: module license taints kernel.
- Next by thread: Re: module license taints kernel.
- Index(es):
Relevant Pages
|