Re: incorrect taint of ndiswrapper

Giridhar Pemmasani
2006-10-23T11:35:24Z

--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> However by then it has already dynamically linked with explicit GPLONLY
> symbols so it cannot then load a binary windows driver but should unload
> itself or refuse to load anything but the GPL ndis drivers (of which
> afaik only one exists), and even then they expect an environment
> incompatible with the Linux kernel.

So the idea of tainting is to _prevent_ any binary code being loaded into
kernel, even if kernel is marked as having binary code loaded, which I
thought was the purpose of tainting (so that people not interested in dealing
with binary code know they don't have/want to)? If that is the goal, how do
you know this scheme of adding names to module loader in kernel guarantees
that (now or in future)?

Thanks,
Giri

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around