From: "David Schwartz" <davids@webmaster.com>
To: "David S. Miller" <davem@redhat.com>, "Yoav Weiss" <ml-lkml@unpatched.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: The disappearing sys_call_table export.
Date: Tue, 6 May 2003 12:45:40 -0700
Message-ID: <MDEHLPKNGKAHNMBLJOLKCEGACMAA.davids@webmaster.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <1052212504.983.16.camel@rth.ninka.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1043
Lines: 25


> On Tue, 2003-05-06 at 01:45, Yoav Weiss wrote:
> > In fact, in linux which is opensource, you can probably write a script
> > that extracts any unexported symbol from the source code, find a path to
> > it from some exported symbol, and automagically create a module that
> > re-exports this symbol for your legacy driver to use.

> You might have a derivative work after obtaining access to a
> non-exported interface.  If this is correct, binary-only modules
> can't do this and therefore they must stick to exported interfaces.

	Obviously you don't have much experience getting around licenses. ;)

	You GPL the part that does the dirty work. Then your closed-source module
only uses exported interfaces and the boundary between GPL and closed-source
code is a clear license boundary.

	DS


-
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/