Slashdot videos: Now with more Slashdot!

View

Discuss

Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

eldavojohn writes "On message boards, Linus Torvalds was explaining why NDISWrapper is not eligible to be released under the GPL even though the project claims to be. Linus remarked, "Ndiswrapper itself is *not* compatible with the GPL. Trying to claim that ndiswrapper somehow itself is GPL'd even though it then loads modules that aren't is stupid and pointless. Clearly it just re-exports those GPLONLY functions to code that is *not* GPL'd." This all sprung up with someone restricted NDISWrapper's access to GPL-only symbols thereby breaking the utility. Linus merely replied that "If it loads non-GPL modules, it shouldn't be able to use GPLONLY symbols." As you may know, NDISWrapper implements Windows kernel API and then loads Windows binaries for a number of devices and runs them natively to avoid the cost and complication of emulation."Link to Original Source

Nobody loves ndiswrapper, but, people are using it because they need drivers for their networking cards - in particular, wireless cards. Really, the GPL is about ensuring the source is available, and in the case of a ndiswrapper, it is. Saying that because one piece of software talks to a closed system somehow filters up and makes the rest of the system closed or in violation of the GPL is silly. If that were the case, then, every time you surfed, you would be violating the GPL, becuase FireFox makes connections to the millions of closed systems that happen to be web sites.

License issues, legal issues, sadly these aren't just things you can wish away for the sake of compatibility.

I could argue your various 'lack of' statements and such with obvious facts and personal experience from using multiple different operating systems. But... I think you made the validity of your view pretty obvious when you called something both 3rd place and the least popular in the world at the same time. "If your not first your last!"

Uninformed bias? How's this for uninformed bias: I have Linux installed on 4 different computers, and Windows on 2 of them. I have personally needed to use ndiswrapper to get a wifi card working on one of the Linux installs. Oh, and I read the FA, which makes it rather clear to me that this is not a legal/licensing question, it is an "I'm being a pedantic troublemaker" question. A question I am intimately familiar with as I spend a lot of time playing the role myself.
Flamebait? Perhaps, I'm a rather

Sure, Linus said that ndiswrapper shouldn't be able to use GPL-only symbols. (And I disagree with him on that.) So far so good.

However, he also said that ndiswrapper is perfectly fine and isn't a license violation, and that he's okay with ndiswrapper asking for the symbols to be exported more freely.

"Quite frankly, my position on this has always been that the GPLv2explicitly covers _derived_ works only, and that very obviously a Windowsdriver isn't a derived work of the kernel. So as far as I'm concerned,ndiswrapper may be distasteful froma technical and support angle, but notagainst the license.

So I'm personally perfectly happy to say that we should revert that commit0aa5bd52d0c49ca56d24584c646e6544ccbb3dc9, but what I've wanted to hearfrom the very beginning was simply to get a list of symbols that currentlyclash, and hear from the people who maintain the symbols whether theyreally meant for that commit to be valid. "