Torvalds is claiming that NDISwrapper -- a loader like firmware-loading, or BIOS-updating drivers should be tainted as non-GPL because it loads some non-GPL material.
Tovalds deftly skipped over answering the issue of all the firmware-loading and updating drivers that are permitted to be called "GPL" even though the firmware they load is not.
There is a major difference here. NDISwrapper loads code that runs in kernel space. Firmware loading loads firmware to a device which runs it separately. A bug being caused by buggy firmware in a peripheral can be handled. A bug being caused by a binary blob in kernel space can have potentially disasterous effects.
See the difference and why module tainting is a good idea? There's no point in debugging a kernel that has random binary blobs since there's no way of telling what they do.
Not at all. Nearly all binary blobs are for x86. This makes it impossible for me to recompile the code to use my devices on powerpc, arm, mips, sh, etc.
So you can prove beyond reasonable doubt that Global Warming is the result of mandkinds 3% CO2?
I can't prove the opposite, but this page is worth a read to counter the propaganda and fud spread by politicians.
This is what it sounds like, when doves cry... Actually one of the very few songs Prince has made that is good. Now he's worth millions and millions, and is getting greedier by the day.
Uh, no. One core for Nortons user-interface and all that crap, one core for the scanning service and one core for your virus (which hardly uses cpu) and Real Work (TM)
I'll tell you another useful bit about SMP. Back in the days when I had two Pentium II (or III?) cpus, I was suckered into clicking a link that got FF and IE to completely freak out and use 101% cpu resources. Fortunately for me this didn't bring my box into a grinding halt like "everybody elses", because they only ran on one of the cores;-)
The same way yours got modded "Redundant" (wtf?!). Anyone care to wager a bet on what my mod will be? I'd say flamebait/troll is a bit over the edge... Overrated perhaps?
Ok, so I'll write a worm that patches the MD5 hash while in transit to Microsoft, big deal. Or I'll just patch the app that calculates the MD5 sum. Or just simply make it skip the check altogether (One simple jmp is required...)
Any P2P patch that requires communicating with microsoft is moot, since the "victim machine" (you) cannot be trusted since it is infected.
While he might not be "correct", you're not much better. You are following the RIAA/MPAA school of thought where a pirate copy equals loss of a sale. If the Taiwan Group case, this is atleast (partly) true. But with casual piracy, that line of thinking just doesn't hold water. There is no guarantee that a teenager downloading Vista Ultimate would've bought it instead of continuing to use the OEM XP that came with his PC.
Copying money differs from copying software/music/movies in that you can (theoretically) use the copied money as "legal" tender. A pirate copy isn't in any way the same as money.
Actually, looking at the incredible amount of "flamebait" and "troll" moderations on posts critical of American Football, it is both obvious that not only does a lot of slashdotters see american football, but they're stupid as hell too.
Padding allows the players to do more than their Rugby counterparts. I've heard this argument a thousand times, but the truth is that if the players have padding, they will play harder to compensate. If you give your rugby players padding, will they play the same way or will they play harder? It's a different focus on playing. American football and Rugby are different sports, even if they are closely related.
Player injuries are also reduced from 157.7 to 16 injuries per 1000h played. On the upside, you're about twice as likely to die from the injuries in american football as in rugby. I still mean that american football is rugby for wee little girlies.
Slashdot Mirror
Yes, but we're talking a combined attack here. If someone found a flaw in the browser allowing bypassing the certificate check, you're pwned.
Then an attacker could try to use a combined attack, using a flaw in the browser combined with DNS poisoning.
Your BIOS guards against that attack vector if you use BIOS-calls to write to the harddrive. Not very likely, and very easy to circumvent...
It doesn't oxidize, for one ;)
So does Home and Away! *shudder*
They cut out a fair bit because they simply can't see the tumor... Cutting a safety margin comes on top of that again.
Does it matter? The "From: " header does not need to be forged. The "Reply-To: " header OTOH...
There's atleast one in the White House. The only difference is that he has more resources. "Shock and Awe" sounds like terror to me.
A four-digit sid makes you me^10 in geekyness ;)
You're the one that grabbed my nick! I'd been registered a lot earlier here if the nick wasn't taken and I didn't bother inventing something! :-P
Denying that you're a geek with a 5-digit slashdot ID doesn't really work out you know ;)
There is a major difference here. NDISwrapper loads code that runs in kernel space. Firmware loading loads firmware to a device which runs it separately. A bug being caused by buggy firmware in a peripheral can be handled. A bug being caused by a binary blob in kernel space can have potentially disasterous effects.
See the difference and why module tainting is a good idea? There's no point in debugging a kernel that has random binary blobs since there's no way of telling what they do.
Not at all. Nearly all binary blobs are for x86. This makes it impossible for me to recompile the code to use my devices on powerpc, arm, mips, sh, etc.
Yeah, good luck on asking the 1000+ people that have copyright on the kernel...
So you can prove beyond reasonable doubt that Global Warming is the result of mandkinds 3% CO2? I can't prove the opposite, but this page is worth a read to counter the propaganda and fud spread by politicians.
No, because that'd be the SP's first SP, which is just as unreliable as the first...
This is what it sounds like, when doves cry... Actually one of the very few songs Prince has made that is good. Now he's worth millions and millions, and is getting greedier by the day.
Uh, no. One core for Nortons user-interface and all that crap, one core for the scanning service and one core for your virus (which hardly uses cpu) and Real Work (TM)
I'll tell you another useful bit about SMP. Back in the days when I had two Pentium II (or III?) cpus, I was suckered into clicking a link that got FF and IE to completely freak out and use 101% cpu resources. Fortunately for me this didn't bring my box into a grinding halt like "everybody elses", because they only ran on one of the cores ;-)
The same way yours got modded "Redundant" (wtf?!).
Anyone care to wager a bet on what my mod will be? I'd say flamebait/troll is a bit over the edge... Overrated perhaps?
Ok, so I'll write a worm that patches the MD5 hash while in transit to Microsoft, big deal. Or I'll just patch the app that calculates the MD5 sum. Or just simply make it skip the check altogether (One simple jmp is required...)
Any P2P patch that requires communicating with microsoft is moot, since the "victim machine" (you) cannot be trusted since it is infected.
While he might not be "correct", you're not much better. You are following the RIAA/MPAA school of thought where a pirate copy equals loss of a sale. If the Taiwan Group case, this is atleast (partly) true. But with casual piracy, that line of thinking just doesn't hold water. There is no guarantee that a teenager downloading Vista Ultimate would've bought it instead of continuing to use the OEM XP that came with his PC.
Copying money differs from copying software/music/movies in that you can (theoretically) use the copied money as "legal" tender. A pirate copy isn't in any way the same as money.
Even reddit can link to a reliable source...
Actually, looking at the incredible amount of "flamebait" and "troll" moderations on posts critical of American Football, it is both obvious that not only does a lot of slashdotters see american football, but they're stupid as hell too.
Player injuries are also reduced from 157.7 to 16 injuries per 1000h played. On the upside, you're about twice as likely to die from the injuries in american football as in rugby. I still mean that american football is rugby for wee little girlies.