On Fri, 29 Feb 2008, Pavel Roskin wrote:
quoted text
> > 
> > I'm not seeing why ndiswrapper should be treated separately.
> 
> It is already treated separately, and has been for a long time.

No, I mean "separately from the thing it loads".

It loads non-GPL code, it is non-GPL.

quoted text
> > If it loads non-GPL modules, it shouldn't be able to use GPLONLY symbols.
> 
> This is not the original intention of GPLONLY.  GPLONLY exists to prevent
> loading of modules that are proprietary, but can be considered to be Linux
> derivatives due to their use of Linux specific API.

Exactly. And ndiswrapper loads proprietary modules.

You're not following the argument. There was a reason ndiswrapper was 
marked for tainting. 

			Linus
--
unsubscribe notice
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/