lkml.org 
[lkml]   [2003]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Linux iSCSI Initiator, OpenSource (fwd) (Re: Gauntlet Set NOW!)
Andre Hedrick wrote:
>
> ..
> Again all I want to know is where the threshold of fair usage lays.

Yes, it needs to be clarified.

> This posting made by Linus to the gnu.misc.discuss newsgroup (Message-ID
> "4b0rbb$5iu@klaava.helsinki.fi") on December 17, 1995 where he
> basically gave his permission for the EXPORT_SYMBOL
> vs. EXPORT_SYMBOL_GPL system hereby proprietary modules that call only
> EXPORT_SYMBOL symbols are allowed:
>
> http://groups.google.com/groups?as_umsgid=4b0rbb%245iu%40klaava.helsinki.fi

I wasn't aware of that posting until Adam pointed it out. It seems
to be a sensible and easily understandable position.

> Until there is some type of agreement ratified by all of us, this is a
> safe position for setting and holding a precedence. If any one of the
> copyright holders in the kernel wishes to formally object, please do so
> now.

Yup. Now is their chance. Is everyone OK with treating the contents
of header files in the same was as EXPORT_SYMBOL()? ie: LGPL?

Really, I don't see any alternative. Even things like the semaphore
down() function are inlined. Linus's 1995 intentions are infeasible
unless we also treat that part of the kernel API which is implemented
in headers as being exported.

It might make sense to be more selective, by putting #ifdef GPL around
some portions. If anyone cares, and can be bothered. If any inlined
function is complex enough to justify that then it's too damn big and
should be zoomed into a .c file anyway.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

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