public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Controversy over dynamic linking -- how to end the panic
Date: Fri, 22 Jun 2001 11:44:24 +0100	[thread overview]
Message-ID: <17687.993206664@redhat.com> (raw)
In-Reply-To: <200106211814.f5LIEgK04880@snark.thyrsus.com>
In-Reply-To: <200106211814.f5LIEgK04880@snark.thyrsus.com>


esr@snark.thyrsus.com said:
>  Earlier today I was contacted by a principal at a well-known Linux
> company who was in a mild panic over recent arguments by Alan Cox and
> David Miller.  This company (not VA or Red Hat, BTW) fears that their
> customers will run from Linux if they get the idea that linking
> drivers to the kernel might force them open. 

I'm not going to join the amateur lawyers' society debate about this. But I 
will point out that I disagree with your intentions here.

Personally, I don't _want_ authors or users of binary modules to be reassured.
I want them to write open source code, or go away. And I don't think I'm 
alone in that.

I think Linus said it best...

On 7 Feb 1999, at 08:15:24 GMT, Linus Torvalds said:
> Basically, I want people to know that when they use binary-only modules,
> it's THEIR problem.  I want people to know that in their bones, and I
> want it shouted out from the rooftops.  I want people to wake up in a
> cold sweat every once in a while if they use binary-only modules. 

Large companies are now basing their design and purchasing choices on the
availability of _real_ Linux support; not just binary-only drivers. Even if 
we _are_ primarily motivated by the desire to increase the market share of 
Linux (which is something I don't concede anyway), then we still don't lose 
much by letting binary-module people continue to sweat. 

--
dwmw2



  parent reply	other threads:[~2001-06-22 10:44 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 18:14 Controversy over dynamic linking -- how to end the panic 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:17         ` David S. Miller
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: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-21 21:35   ` Controversy over dynamic linking -- how to end the panic (long) Alex Bligh - linux-kernel
2001-06-22 12:32   ` Fair Use (Was Re: Controversy over dynamic linking -- how to end the panic) Rob Landley
2001-06-22  1:29 ` Controversy over dynamic linking -- how to end the panic Andrea Arcangeli
2001-06-22 10:44 ` David Woodhouse [this message]
2001-06-23 20:11 ` Fabrice Gautier
  -- strict thread matches above, loose matches on Subject: below --
2001-06-21 19:22 Disconnect
2001-06-21 19:24 ` Alan Cox
2001-06-21 19:25 Jesse Pollard
2001-06-21 21:43 Timur Tabi
2001-06-22  3:05 Rick Hohensee
2001-06-22  4:05 ` kumon
2001-06-23 22:29 ` Scott Wood

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=17687.993206664@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=esr@snark.thyrsus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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