From: Disconnect <lkml@sigkill.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Controversy over dynamic linking -- how to end the panic
Date: Thu, 21 Jun 2001 15:22:28 -0400 [thread overview]
Message-ID: <20010621152226.E13649@sigkill.net> (raw)
In-Reply-To: <E15D9u7-0001xo-00@the-village.bc.nu>
On Thu, 21 Jun 2001, Alan Cox did have cause to say:
> An application is clearly not a derivative work in the general case, and they
> are linked with glibc which is LGPL and gives the users the choice and right
> to run non-free apps.
IANAL, and this may be a dumb question, but what about LGPLing the driver
abstraction layer and/or headers? (Presuming of course there -is- a driver
abstraction layer that would work for 99% of the drivers.) That leaves
the kernel safe (since LGPL says link whatever under whichever license,
GPL is valid for kernel core) and -specifically- allows any license you
like for HW/SW vendors who want to make modules.
---
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1 [www.ebb.org/ungeek]
GIT/CC/CM/AT d--(-)@ s+:-- a-->? C++++$ ULBS*++++$ P- L+++>+++++
E--- W+++ N+@ o+>$ K? w--->+++++ O- M V-- PS+() PE Y+@ PGP++() t
5--- X-- R tv+@ b++++>$ DI++++ D++(+++) G++ e* h(-)* r++ y++
------END GEEK CODE BLOCK------
next reply other threads:[~2001-06-21 19:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 19:22 Disconnect [this message]
2001-06-21 19:24 ` Controversy over dynamic linking -- how to end the panic Alan Cox
-- 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 21:43 Timur Tabi
2001-06-21 19:25 Jesse Pollard
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: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-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=20010621152226.E13649@sigkill.net \
--to=lkml@sigkill.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.