mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Boucher <marc@linuxant.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: rusty@rustcorp.com.au,
	tconnors+linuxkernel1083378452@astro.swin.edu.au,
	linux-kernel@vger.kernel.org, riel@redhat.com,
	mbligh@aracnet.com, Sean Estabrooks <seanlkml@rogers.com>,
	nico@cam.org
Subject: Re: [PATCH] clarify message and give support contact for non-GPL modules
Date: Sat, 1 May 2004 19:28:03 -0400	[thread overview]
Message-ID: <3114F1F7-9BC7-11D8-B83D-000A95BCAC26@linuxant.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0405011541330.18014@ppc970.osdl.org>


Linus,

As  previously mentioned, I have offered many patches and a lot of 
source to the community throughout the last 15 years. Either personally 
or via Linuxant, under various licenses (including the GPL) depending 
on the constraints imposed by each situation, and continue doing so. In 
the workaround case, we should have admittedly sent a patch earlier 
instead of putting in the \0 and I sincerely apologized for that.

The modules in question are not binary-only, but mixed source/binary. 
With the submitted patch, we are also offering to take as much support 
burden off the community by clarifying the messages to explicitly 
direct users to where they should go for help when using third-party 
modules.

With all due respect, your claims that we are offering nothing / not 
giving back are not factual and you should not take position based on 
either incorrect information or a very narrow / alarmist interpretation 
of what we are doing.

Regards
Marc

On May 1, 2004, at 6:48 PM, Linus Torvalds wrote:
>
> On Sat, 1 May 2004, Marc Boucher wrote:
>>
>> I think that your wording is problematic, because:
>
> No.
>
> You seem to believe that you can get something for nothing.
>
> Wrong.
>
> You offer nothing to the open-source community, you get nothing back. 
> That
> means very much that people don't support what you're doing, and you
> should realize that as far as the rest of the kernel is concerned, you
> ARE tainting it.
>
> The GPL is about a symbiotic relationship, where people help each 
> other.
> In contrast, a binary module is a parasite - giving nothing back to the
> community.
>
> So live with that fact. Don't try to make it look like anything else.
>
> 		Linus
>


  reply	other threads:[~2004-05-01 23:28 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <009701c42edf$25e47390$ca41cb3f@amer.cisco.com>
2004-04-30 19:19 ` [PATCH] Blacklist binary-only modules lying about their license Linus Torvalds
2004-04-30 19:37   ` Hua Zhong
2004-04-30 22:47     ` Allowing only "-g" compiled modules! (was: [PATCH] Blacklist binary-only modules lying about their license) Jan-Benedict Glaw
2004-04-30 20:11   ` [PATCH] Blacklist binary-only modules lying about their license Marc Boucher
2004-04-30 20:26     ` Linus Torvalds
2004-04-30 20:39       ` Marc Boucher
2004-04-30 20:44         ` Linus Torvalds
2004-04-30 20:53           ` Marc Boucher
2004-04-30 21:05             ` Linus Torvalds
2004-04-30 21:10             ` Timothy Miller
2004-04-30 20:46         ` Sean Estabrooks
2004-04-30 20:34     ` Stefan Smietanowski
2004-04-30 20:47     ` A compromise that could have been reached. " Timothy Miller
2004-04-30 21:07       ` Marc Boucher
2004-04-30 21:16         ` Rik van Riel
2004-04-30 21:38         ` Timothy Miller
2004-04-30 22:05           ` Marc Boucher
2004-05-01  2:36           ` Tim Connors
2004-05-01  0:40     ` Jorge Bernal
2004-05-01  5:07     ` Martin J. Bligh
2004-05-01 19:12       ` Marc Boucher
2004-05-01 19:27         ` Davide Libenzi
2004-05-01 19:32         ` Zwane Mwaikambo
2004-05-01 19:33         ` Sean Estabrooks
2004-05-01 22:14           ` Randy.Dunlap
2004-05-01 19:47         ` Nicolas Pitre
2004-05-01 20:53           ` [PATCH] clarify message and give support contact for non-GPL modules Marc Boucher
2004-05-01 21:34             ` Sean Estabrooks
2004-05-01 21:48               ` Marc Boucher
2004-05-01 21:53                 ` Sean Estabrooks
2004-05-01 22:22                 ` Sean Estabrooks
2004-05-01 22:53                   ` Marc Boucher
2004-05-01 23:10                     ` viro
2004-05-02  7:04                       ` Xavier Bestel
2004-05-04 17:06                       ` Timothy Miller
2004-05-01 22:48                 ` Linus Torvalds
2004-05-01 23:28                   ` Marc Boucher [this message]
2004-05-02  0:22                     ` Linus Torvalds
2004-05-02  1:02                       ` Marc Boucher
2004-05-02 12:43                         ` Sean Estabrooks
2004-05-02 13:05                           ` Paul Rolland
2004-05-02 15:35                             ` Marc Boucher
2004-05-02 15:45                               ` Sean Estabrooks
2004-05-04 17:09                     ` Timothy Miller
2004-05-01 20:47         ` [PATCH] Blacklist binary-only modules lying about their license Martin J. Bligh
2004-05-01 20:58           ` Marc Boucher
2004-05-03  0:04         ` Horst von Brand
     [not found] ` <40929F5B.9090603@techsource.com>
2004-04-30 18:58   ` Hua Zhong
2004-04-30 20:14   ` Bartlomiej Zolnierkiewicz

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=3114F1F7-9BC7-11D8-B83D-000A95BCAC26@linuxant.com \
    --to=marc@linuxant.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=nico@cam.org \
    --cc=riel@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=seanlkml@rogers.com \
    --cc=tconnors+linuxkernel1083378452@astro.swin.edu.au \
    --cc=torvalds@osdl.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®