Re: GPLONLY kernel symbols???

M. R. Brown (mrbrown@0xd6.org)
Thu, 18 Oct 2001 08:32:44 -0500


--7cm2iqirTL37Ot+N
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* pierre@lineo.com <pierre@lineo.com> on Wed, Oct 17, 2001:

>=20
> I can make a kernel driver that compiles statically
> and also uses a non-GPL library, even in the form of
> a binary .o file, and the "tainted" mechanism as it
> is today will miss it entirely.
>=20

Statically into the kernel? I don't think so. First off, if your "static"
code isn't GPL'd you can't distribute the resultant kernel since you've
violated the GPL. The tainted mechanism was designed for proprietary
and/or binary-only modules without a supported license. The case you
mention above can't even exist (at least, not in any publically-accessible
code).

M. R.

--7cm2iqirTL37Ot+N
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)

iD8DBQE7ztn8aK6pP/GNw0URAr4nAJ9D4KptBKPSiUFNDjbKbqR7OaiN5QCeOfoW
tpj7QKxQGq/qtb+sepGAfzE=
=zbyq
-----END PGP SIGNATURE-----

--7cm2iqirTL37Ot+N--
-
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/