From: Cort Dougan <cort@fsmlabs.com>
To: Craig Milo Rogers <rogers@ISI.EDU>
Cc: Larry McVoy <lm@bitmover.com>,
Rik van Riel <riel@conectiva.com.br>,
Timur Tabi <ttabi@interactivesi.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] Module Licensing?
Date: Wed, 31 Oct 2001 14:42:44 -0700 [thread overview]
Message-ID: <20011031144244.R607@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <20011031092228.J1506@work.bitmover.com> <4986.1004558101@ISI.EDU>
In-Reply-To: <4986.1004558101@ISI.EDU>; from rogers@ISI.EDU on Wed, Oct 31, 2001 at 11:55:01AM -0800
The GPL 2.0 uses language that makes it pretty clear that it was meant to
describe the source code, not the object module. It uses "source code" to
refer to what is licensed under the GPL several times.
The GPL has been a great source for nebulous debates without much in the
way of solid ground to stand on. It's not remarkable that it has a history
in academia.
Too bad those who drafted the GPL were not (competent) lawyers, either.
} Your compiled object module might be a derived work, hence its
} distribution would be restricted by the terms of the GPL version 2.
} Your source code file would not be a derived work (under certain
} currently widely-held assumptions about interface copyrights), and
} hence could be distributed without restriction by the GPL.
}
} Usual disclaimer: I am not a lawyer.
}
} Craig Milo Rogers
} -
} To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
} the body of a message to majordomo@vger.kernel.org
} More majordomo info at http://vger.kernel.org/majordomo-info.html
} Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-10-31 21:46 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 3:46 Module Licensing? Kevin D. Wooten
2001-10-30 4:08 ` Ben Greear
2001-10-30 4:58 ` TimO
2001-10-30 5:10 ` Ben Greear
2001-10-30 7:24 ` Kevin D. Wooten
2001-10-30 17:27 ` Timur Tabi
2001-10-30 23:10 ` Alan Cox
2001-10-31 0:13 ` Timur Tabi
2001-10-31 0:25 ` Alan Cox
2001-10-31 16:53 ` Timur Tabi
2001-10-31 17:10 ` Rik van Riel
2001-10-31 17:22 ` Larry McVoy
2001-10-31 17:27 ` Rik van Riel
2001-10-31 18:34 ` Larry McVoy
2001-10-31 18:44 ` Rik van Riel
2001-10-31 18:53 ` Andreas Dilger
2001-10-31 20:08 ` Craig Milo Rogers
2001-10-31 17:32 ` dean gaudet
2001-10-31 19:55 ` [OT] " Craig Milo Rogers
2001-10-31 21:42 ` Cort Dougan [this message]
2001-10-31 23:47 ` Jamie Lokier
2001-10-31 23:54 ` Larry McVoy
2001-11-01 0:10 ` Jamie Lokier
2001-11-01 0:43 ` Alan Cox
2001-11-01 23:52 ` n0ano
2001-10-31 17:29 ` Timur Tabi
2001-10-31 17:37 ` Rik van Riel
2001-10-31 18:31 ` LLX
2001-11-08 0:36 ` drizzt.dourden
2001-11-08 12:41 ` Alan Cox
2001-11-08 13:19 ` Drizzt Do'Urden
2001-11-08 14:53 ` Module Licensing? (thinking a little more) Drizzt Do'Urden
2001-11-08 15:56 ` Doug McNaught
2001-11-08 17:00 ` Drizzt Do'Urden
2001-11-08 17:18 ` Russell King
2001-11-08 17:47 ` Drizzt Do'Urden
2001-11-09 7:50 ` Stefan Smietanowski
2001-11-10 18:09 ` QuoteMstr - Danny Colascione
2001-11-08 17:29 ` Doug McNaught
2001-11-08 19:28 ` drizzt.dourden
2001-10-31 20:15 ` Module Licensing? Craig Milo Rogers
2001-10-31 19:49 ` Craig Milo Rogers
2001-11-04 3:37 ` Albert D. Cahalan
2001-10-31 17:11 ` Alan Cox
2001-11-05 4:40 ` [file interface] " Roger Larsson
2001-10-30 9:22 ` Alan Cox
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=20011031144244.R607@ftsoj.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=riel@conectiva.com.br \
--cc=rogers@ISI.EDU \
--cc=ttabi@interactivesi.com \
/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