From: kumon@flab.fujitsu.co.jp
To: Rick Hohensee <humbubba@smarty.smart.net>
Cc: linux-kernel@vger.kernel.org
Cc: kumon@flab.fujitsu.co.jp
Subject: Re: Controversy over dynamic linking -- how to end the panic
Date: Fri, 22 Jun 2001 13:05:08 +0900 [thread overview]
Message-ID: <200106220405.NAA09904@asami.proc.flab.fujitsu.co.jp> (raw)
In-Reply-To: <200106220305.XAA15554@smarty.smart.net>
In-Reply-To: <200106220305.XAA15554@smarty.smart.net>
Rick Hohensee writes:
> Richard Stallman is the creator of the license. It's his greatest work.
> Linus is in no way priviledged as to interpretation of it, other than
> tolerance on the part of the parties that own the copyright to the
> license.
So, GPL FAQ on FSF web-site <http://www.fsf.org/copyleft/gpl-faq.html>
is worth reading. It represents their thought.
* If a library is released under the GPL (not the LGPL), does that
mean that any program which uses it has to be under the GPL?
<http://www.fsf.org/copyleft/gpl-faq.html#IfLibraryIsGPL>
* Why are some GNU libraries released under the ordinary GPL rather
than the Lesser GPL?
<http://www.fsf.org/copyleft/gpl-faq.html#WhySomeGPLAndNotLGPL>
* I am writing free software that uses non-free libraries. What legal
issues come up if I use the GPL?
<http://www.fsf.org/copyleft/gpl-faq.html#TOCWritingFSWithNFLibs>
--
Computer Systems Laboratory, Fujitsu Labs.
kumon@flab.fujitsu.co.jp
next prev parent reply other threads:[~2001-06-22 4:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 3:05 Rick Hohensee
2001-06-22 4:05 ` kumon [this message]
2001-06-23 22:29 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2001-06-21 21:43 Timur Tabi
2001-06-21 19:25 Jesse Pollard
2001-06-21 19:22 Disconnect
2001-06-21 19:24 ` Alan Cox
2001-06-21 18:14 Eric S. Raymond
2001-06-21 18:30 ` Alan Cox
2001-06-21 19:17 ` Eric S. Raymond
2001-06-21 19:51 ` Andrew Pimlott
2001-06-21 20:13 ` Eric S. Raymond
2001-06-21 20:46 ` Andrew Pimlott
2001-06-21 21:02 ` Timur Tabi
2001-06-21 21:05 ` Andrew Pimlott
2001-06-21 21:17 ` Timur Tabi
2001-06-21 20:17 ` David S. Miller
2001-06-21 20:29 ` Timur Tabi
2001-06-21 18:39 ` Jeff Golds
2001-06-21 18:51 ` Jeff Mahoney
2001-06-21 20:02 ` Steve Brueggeman
2001-06-21 18:46 ` Timur Tabi
2001-06-21 19:03 ` Timur Tabi
2001-06-21 19:53 ` Erik Mouw
2001-06-21 19:04 ` Mike Harrold
2001-06-21 19:14 ` Alan Cox
2001-06-21 20:12 ` Marco Colombo
2001-06-21 21:14 ` Alan Cox
2001-06-21 20:31 ` Timur Tabi
2001-06-21 19:08 ` Timur Tabi
2001-06-21 19:17 ` Alexander Viro
2001-06-21 20:01 ` Wei Weng
2001-06-21 19:06 ` Alan Cox
2001-06-21 19:34 ` Jonathan Lundell
2001-06-21 20:17 ` D. Stimits
2001-06-22 11:32 ` Rob Landley
2001-06-21 20:34 ` Craig Milo Rogers
2001-06-22 1:29 ` Andrea Arcangeli
2001-06-22 10:44 ` David Woodhouse
2001-06-23 20:11 ` Fabrice Gautier
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=200106220405.NAA09904@asami.proc.flab.fujitsu.co.jp \
--to=kumon@flab.fujitsu.co.jp \
--cc=humbubba@smarty.smart.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®