Linus says, "Trying to claim that ndiswrapper somehow itself is GPL'd even though it then loads modules that aren't is stupid and pointless."
I wrote a program and made it entirely proprietary. I compiled it and ran it on my Linux system. The kernel loaded it right up. What's the difference? The way pointers to entry points are managed? Irrelevant. The state of a "privileged" bit on the processor? A mere conceit with no legal significance. Whether it's a "kernel module" or "user code", it's all a blob of x86 instructions that the kernel loads and hands execution over to from time to time. Quod erat demonstrandum.
... redirect to the culprit if they're misused. I own my own domain, and the MX points to a service provider that supports unlimited forwarding addresses as well as default forwarding (if I want it). I use a unique address for each business I deal with, and if they misuse it, I can block, drop, or redirect mail to that address.
If I was dealing with AmeriTrade, e.g., I'd give them "ameritrade.com@mydomain.tld". I'd automatically get mail to that address w/o having to set up anything else. BUT, if I start getting spammed at that address, I can drop all mail to that address, or configure it to automatically forward to, e.g., abuse@ameritrade.com.
Slashdot Mirror
Looks like a few 3d pairs have been posted to NASA's site and picked up here. Hope some more, wider views come out soon.
Linus says, "Trying to claim that ndiswrapper somehow itself is GPL'd even though it then loads modules that aren't is stupid and pointless."
I wrote a program and made it entirely proprietary. I compiled it and ran it on my Linux system. The kernel loaded it right up. What's the difference? The way pointers to entry points are managed? Irrelevant. The state of a "privileged" bit on the processor? A mere conceit with no legal significance. Whether it's a "kernel module" or "user code", it's all a blob of x86 instructions that the kernel loads and hands execution over to from time to time. Quod erat demonstrandum.
... redirect to the culprit if they're misused. I own my own domain, and the MX points to a service provider that supports unlimited forwarding addresses as well as default forwarding (if I want it). I use a unique address for each business I deal with, and if they misuse it, I can block, drop, or redirect mail to that address.
If I was dealing with AmeriTrade, e.g., I'd give them "ameritrade.com@mydomain.tld". I'd automatically get mail to that address w/o having to set up anything else. BUT, if I start getting spammed at that address, I can drop all mail to that address, or configure it to automatically forward to, e.g., abuse@ameritrade.com.
Works like a charm