Forgot your password?
typodupeerror

Comment Re:(e)stop the madness (Score 1) 607

It is very clear that the minute SCO reveals that information that the code will be yanked and replaced by non infringing code, most likely within hours, days at the outside. This limits the damages that SCO can claim, since it is very clear that the infringement is not only not willful, it is involuntary. The only reason why the infringement is continuing is because SCO refuses to release that information.

Don't you see, the reason SCO is not identifying the infringing code is to prove to the court later that the Linux stewards don't know where this, or any other potentially infringing code, is in their own kernel, that the open-source model is not protective of IP because the people managing the kernel can't tell when code comes in that it is infringing, and it could be happening hourly. In SCOs eyes (actually not SCO, they are just the stalking horse here, period.) the argument that the code is open source, and is there for all to see, can be attacked by saying that the Linux maintainers are requiring a burdensom, affirmative obligation on the part of everyone out there with software IP to constantly analyze the Linux kernel, looking for improper use of their code. Make no mistake about it, this is an attack (not the entire war, just one tactic in a larger strategy) on the GPL by one company. In a legal system with integrity, this case could never succeed, and the company sponsoring this would finally get their just anti-trust due. But I think we all have to be congnizant of the fact that after November 2000 that, at the top, which is where this will wind up, the fix is in, and if the FSF and IBM aren't on top of their game, this could turn out very badly.

Slashdot Top Deals

What good is a ticket to the good life, if you can't find the entrance?

Working...