Slashdot Mirror
SCO Claims Kernel Contains UnixWare Code
ergo98 writes "SCO has increased the intensity of the lawsuit with IBM by claiming to hold indisputable proof that copyrighted UnixWare code found its way into Linux, violating the rules of both camps. Whether this is true or not remains to be seen: SCO refuses to divulge the code in question, however they promise to reveal it in court shortly."
Exactly, the fact they aren't prepared to even present a single example of this makes me very suspicious. It would be magnitudes easier for SCO devels to steal code from the Linux kernel (even unintentionally) than for the Linux kernel to steal code from SCO. Anyhow, as some have already mentioned, who's to say that the code lines in question weren't already in the public domain prior to them even being in SCO? I'm doubling-down on IBM if they want to play a chicken-and-the-egg fight in this suit.
Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
No, because they've specifically stated they're not referring to official (kernel.org) kernel code.
IANAL
My understanding of this is, since they are playing games by not telling anyone what the specific violation is, they are losing their rights to claim past damages (unless they can prove the party they are suing knew of the violation). The usual way a copyright or trade secret violation is handled is by contacting the violating party and asking for the matter to be corrected. If the violating party does correct the problem in a timely manner, courts will generally treat past violations as innocent violations, and awards would not be more than the profits involved. But SCO hasn't done this. Instead they are refusing to saw what the violation is. They are only referring to "Linux" and it isn't even clear if they mean the kernel, some driver, or userland code. There's nothing any party can do to remove any violating code until they know what it is.
now we need to go OSS in diesel cars
rmadmin asks:
Can someone spread some light on how they'd prove how old their code is?
In this day and age, there's no such thing as proof. There are ways (both low and high tech) to falsify almost any piece of evidence. Thankfully, the court system is already set up to handle this.
From what I understand, in most trials there are issues of fact (he did this to them at this time) and issue of law (and because of that he should be convicted of this charge). Early in the process, SCO is supposed to file documents asserting (among other things) the facts as they understand them. IBM is supposed to reply with (among other things) the facts as they understand them, including pointing out where the agree (eg. IBM stipulates that the plaintiff is, in fact, called the Santa Cruz Organization, Inc), and where they disagree (eg. IBM at no point transmitted any part of foo.c to persons outside the company).
If they disagree on significant factual issues (and don't settle, and IBM doesn't eat SCO to make the headache go away), then the case will eventually end up in a trial by jury. The jury's main job is to listen to both sides evidence regarding the facts of the case, and decide whose evidence is more convincing.
If there's no dispute on the facts, juries can be dispensed with, and a judge can just decide how the law applies. You get fun things like Summary Judgements as in the Grokster case if everyone's on the same page as far as facts go.
If SCO produces a falsified source document from 1998 with GPL code pasted in, IBM can rebut with a witness from IBM showing that in 1998 they received a different document, including the SCO (Novell?) branded CD and the matching checksums from the printed and dated documentation. They could also add a witness from a third company showing that in 1998 they received a different document too. I don't think a jury will have a hard time deciding relative merits of such evidence.
Disclaimer: I am not a lawyer, the above should not be considered to be legal advice. Some states may permit Judges to determine issues of fact and not require a Jury for that under some circumstances.
----
Open mind, insert foot.
I believe you are talking about this SCO letter and this parody.
- SCO doesn't claim in its' filing that there is any SCO IP in the linux kernel, contrary to what McBride says
- SCO does claim in its' filing that certain compatability libraries that allow UnixWare binaries to run under linux are their IP.
- None of the current distros has a copy of any of these libraries.
- McBride should read his own companys' suit before giving interviews, but then he would be open to charges of "pump and dump" vis his SCO stock (not that ignorance is a defence, but
...)
This whole thing is so fucked up that it can only be a stock-market scam.Folk... don't click the AC's link to google... it isn't really a link to google, but some stupid 'click this link and make me a bunch of points in some stupid game' link.
Troll.
man 1 ls, man 1 cc ,man 1 find
and then you'll know.
Maybe i've been trolled, but maybe i've helped a newbie.
The Numbers refer to the original MAN PAGES books 1 to 8. Try Xman on any ***X machine.
... whenever a text is transmitted, variation occurs. This is because human beings are careless, fallible, and occasiona
Their entire suit may be based on header files in Linux which conform to SYSVR4 specifications. To an untrained reviewer, this may indeed look like infringement.
Fortunately, there's plenty of legal precedence about header files, conforming to specifications, etc. which should make short work of this claim.
Anyway, down to business...
SCO customers in New York! would you like to move away from a sinking ship and regain control of your systems? Looking to develop a Linux strategy? We can help.
If i is an unsigned byte variable, it'll always be in the range [0..255], so i < 256 will always be true, so the loop will go on and on forever.
(Until you get to the end, and the monkey starts throwing barrels at you.)
I suffer from attention surplus disorder.
to qoute: Given the loose nature of linux coding, I'm not surprised at all that someone with access to SCO code would contribute it to Linux.
I dont think you know a damn thing about "Linux" coding. what you seem confused about is weather a program is "Linux", the answer is NO. the only thing that is and has been "Linux" is the Kernel. And if you know that i would like you to explain to me how its "loose" in nature ? their is only ONE person who can "officially" approve code for use in "THE" kernel, and thats Linus. You can code a module, or even modify the hell out of the kernel, but thats not "Linux", "Linux" can only be found from one place: kernel.org, everything else is a modifyied version of it, and therefor the individual vendors are responsible for it. (hence redhat has an issue if a redhat kernel has SCO code in it, whereas the vanilla kernel wont.)
and i would challenge you to find ANY OS who only has one guy in charge of approving code/patches to the kernel.
"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
They already know this, but that isn't what the law suit is about. The law suit is about $1 billion that SCO claims this alleged offense has cost them. Honestly I doubt they care if the code is there by this point. Taking the code out will only cause some one to write a replacement relatively quickly, and net SCO nothing.
Slackware, what else when it must be secure, stable, and easy?
But JFS was written independantly of the code IBM licensed from SCO, so that can't be it. I agree they have no clue what they're targeting.
Wu-Tang Name: Half-Cut Skeleton Get your own Wu-Na
Actually, Caldera has approximately tripled since announcing this lawsuit. The one day loss was a blip. That being said, the only reason it's gone up is that otherwise, the company had no prospects at all. This at least is a shot in the dark.
"The question of whether a computer can think is no more interesting than that of whether a submarine can swim" -EWD
Try a medium or small brokerage firm that has their own trading desk.
The rules for shorting SCOX are that you have to
if some GPL code makes its way its something else... its is GPLed
This isnt true. If GPL code is incorporated into proprietary code, then it is a GPL licence violation (providing 'derived work' holds true). Licence violations mean you can seek redress, either by settling privately with the violator, or by getting a judge to rule in your favour. Redress could consist of damages and the violator excising the GPL code from his app, and/or even relicensing of the derived work under GPL.
But it is by no means automatic. What happens when GPL licence is violated is for the 2 parties to settle between themselves or, if they can not come to an amicable settlement, a judge to decide.
I use Friend/Foe + mod-point modifiers as a karma/reputation system.
...Microsoft is already making code obfuscation a natural part of their development process. Most likely they are going to release their code open source at some point in the future, after they've obfuscated it to death.
r l= /library/en-us/dnnetcomp/html/netcfobfuscation.asp
See...
http://msdn.microsoft.com/library/default.asp?u
+2 more cents.
Actually, if they really plan on going to court, they're going to have to reveal their evidence to IBM long before it actually makes it to the courtroom.
See, there's this little thing called "discovery", where both parties in a court action are entitled to request any information from the other party even slightly pertinent to the case. And the other side must comply unless they can get a judge to agree that it's not relevant.