[lkml]   [2002]   [Apr]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2.5.5] do export vmalloc_to_page to modules...
On Thu, Apr 04, 2002 at 04:35:33PM +0100, Tigran Aivazian wrote:
> kernel is protecting itself to make sure that "interesting" functionality

I share your same concerns, but I think "interesting" is way too much
vague to hold any legal meaning, furthmore even assuming "important"
means something (obviously not true) it's not priorly written anywhere
that "important" functionality had to be threated in a different manner.

> not necesserily "bad", i.e. it may well be necessary for Linux's survival

I don't really worry about that, important things will defend by
themself, beacuse the GPL solution will be always superior of an order
of magnitude. For istance I would never use the proprietary soltuion
despite it's temporarly better, because it would even prevent me to do
further developement. The important thing is that we never include non
GPL code in the mainline kernel and that the 99% of the code is under
the GPL licence and that it can be intermixed freely (basically only
modulo bsdcomp and a few other very exceptions in their own files with
bold letters about the BSD thing).

The only cases that can live as binary only long term are the ones
speaking with the hardware, when the hardware specs are not published
(and even that often is beaten by the GPL solution).

I think the current way of doing things is fine, I'd simply remove the
_GPL thing from kernel and modutils and then I'd return working on
technical things.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:25    [W:0.168 / U:4.624 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site