mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Timur Tabi <ttabi@interactivesi.com>
To: Linux Kernel Mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Controversy over dynamic linking -- how to end the panic
Date: Thu, 21 Jun 2001 16:43:11 -0500	[thread overview]
Message-ID: <aiLYb.A.GGG.xpmM7@dinero.interactivesi.com> (raw)

** Reply to message from Andrew Pimlott <andrew@pimlott.ne.mediaone.net> on
Thu, 21 Jun 2001 17:30:06 -0400


> I'm not sure whether you are right or wrong--but such a conclusion
> would be grossly unfair.  I think a strong case would be made that
> existing practice wrt Linux is independent of existing practice wrt
> GNU, and that everyone involved knows that Linus's GPL is not the
> FSF's GPL.  And I think that the FSF (and their lawyers) would
> advance this claim vigorously.

Well, that's a can of worms we DON'T want to open.  What's to stop Microsoft
from claiming their own interpretaion of the GPL?  The whole point behind the
GPL (and any license) is that it cannot be vaguely interpreted by various
individuals and companies.

> (Besides, it's really in nobody's best interest to take the GPL
> before a judge, so I think that rough consensus and community
> dynamics will continue to drive the interpretation of the GPL.)

Well, what if one company create a Linux application and used the "Linus GPL"
instead of the "FSF GPL" to defend its practices?  I think there's some
situation going on right now about an company that released a non-GPL Linux
media player (or something like that) that links in someone else's GPL code.

Besides, isn't the "Linus GPL" somewhere between the "FSF GPL" and the LGPL?


-- 
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com


-- 
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com


             reply	other threads:[~2001-06-21 21:43 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 21:43 Timur Tabi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-22  3:05 Rick Hohensee
2001-06-22  4:05 ` kumon
2001-06-23 22:29 ` Scott Wood
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=aiLYb.A.GGG.xpmM7@dinero.interactivesi.com \
    --to=ttabi@interactivesi.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 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®