IBM Doesn't Comply With SCO's Deadline
prostoalex writes "IBM refused to settle with SCO and comply with their deadline, expiring Friday the 13th. "We've got a strong defense case, and we're going to fight it", IBM representative is quoted."
← Back to Stories (view on slashdot.org)
I hate to say this, but who actually thought IBM would give in to this undersized bully?
Someone hates these cans.
Third round!! 50 bucks on IBM!!!
On Friday the 13th a black cat was found dead at SCO underneath a broken mirror.
SCO: I bet "Friday the 13th"
IBM: I call.
SCO: Umm..*looks at cards*
IBM: *smiles*
to be continued...
When modding "Informative", please make sure it both has a source and IS actually informative.
... was later heard to comment, "Ha ha ha, they are SOOOO dead".
I'm sick of the money grubbing BS that's hovering around this case. It's clear that SCO is using the "open" in open source to try and challenge an IP issue because they know the court's never seen anything like this before. Also, the fact that M$ injects money into SCO is really suspect and deserves and out right investigation, because EVERYONE knows they [SCO] wouldn't be paying lawyer's for this FUD if they didn't have the cash.
Everyone here knows that Linux is kicking the shit out of Microsoft on the server, and they [M$]know it's not long before it starts cutting into their desktop margins.
This stuff is making me sick. It's a joke, it's friggin' "high-tech ambulance chasing".
I can't wait until they lose and I hope IBM find's something suspect in the case so that they can reveal the true evil behind all this...
I'm a bit confused here... do we want SCO to win, or do we want SCO to lose?
Ok, SCO is a bunch of scumbags, so obviously we don't want them to win.
On the other hand, if SCO loses, it will send a strong message to the world: "Stay away from anything GPL, or you'll find your proprietary code taken away from you."
I'm really not sure which outcome would be worse.
Tarsnap: Online backups for the truly paranoid
Who needs drama/soaps on tv when you have a show right here..
SCO and IBM's marriage isnt going well.
SCO says IBM is cheating with another OS.
SCO files for divorce.
SCO takes IBM's keys to the house away
IBM fights for the house.
Oh how I will tune in next week to see what happens.
It seems the Friday deadline looked good to traders, the stock price jumped... Yahoo has an article, written on Friday, about the jump.
Any bets on what happens to the stock price on Monday?...
Since I don't have the money to defend myself in court like IBM, I'd really like to comply with SCO's claims that not just linux, but a lot of other software infringes on SCO's claimed copyright. I'm just a bit puzzled as to how I might go about this.
.tgz files and post the URL here, I can download it and take care of it myself.
...
For example, I'm looking at a line of code in one of my GPL'd programs:
i += j - n;
Does this infringe on any code claimed by SCO? How would I know?
The only way I can think of is that SCO should send me a copy of their code. I can easily write a little perl script that will compare every line of my code with every line of theirs, and I can rewrite anything that seems to be infringing.
Can anyone think of another way?
Since my code is GPL'd and on my web site, SCO could do it themselves. But they are probably pretty busy, so I'd rather do it myself. Anyway, recent history shows that when they find infringing code, they don't send the programmer a nice message so the code can be changed. SCO just sues them for big bucks. I'd much rather avoid this threat, and save them time, by eliminating any infringements myself.
SCO doesn't need to send me their code. If someone at SCO would just package it up in a few
Eagerly awaiting the URL
Those who do study history are doomed to stand helplessly by while everyone else repeats it.
Linux software companies could also become SCO targets. "Do we have potential issues with Red Hat, SuSE and other commercial Linux distributors--yes, we might," Sontag said, adding that chances for negotiating with such companies appear to be slim.
Bel, the mostly sane.. "Of course I can't see anything! I'm standing on the shoulders of idiots." -- Me
Of a case involving MCA Universal, Nintendo and Donkey Kong.
It ends up Universal didn't actually OWN the rights to Donkey Kong, but bullied several companies, and sued Nintendo anyway... and ended up paying 1.8 million for the trouble.
Ryan Fenton
...of something strongly in doubt.
First off, SCO has to prove that the code in question is in fact "theirs". Considering the rather incestuous family tree that is UNIX that is not so cut and dry.
Additionally, there are allegations that SCO has been helping themselves to GPL'd code without credit or redistribution.
No, the thing we're learning here is that if you really have an IP case against Linux or another GPL project than just be right out in the open. Document the code and PROVE your case. Don't hide behind lawyers, NDA's, horribly out of context quotes and vaguely threatening letters.
And, oh yeah, it helps if you can at least stick to one story for greater than a week.
--- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
SCO can't compete with Linux. Its UnixWare OS, while a fine middle level server OS, doesn't have the the scalability, hardware support or applications that Linux has. They know it. SCO couldn't make money selling its own Linux.
So, it does what M$ could only dream of: launch a self destructive lawsuit in a last, desperate gasp of trying to save its business and destroy Linux, unleashing the greatest FUD attack witnessed yet. People are scared. M$, with its "license" pulls the strings, and watches with glee. "I told you so!" M$ will say. "You can't trust open source!"
SCO needs to be destroyed. No bought or settled with, but crushed, utterly and completely. What they have done is unethical, immoral and (hopefully) completely without legal base.
CDE open sourced! https://sourceforge.net/projects/cdesktopenv/
When is the class-action countersuit going to begin?
Directly from the article:
" The dispute between SCO and I.B.M. has not yet slowed the advance of Linux in the marketplace, according to industry executives. But the prospect that the suit may linger indefinitely can only add to the anxiety of corporate technology buyers.
"They're really concerned," noted George Weiss, an analyst at Gartner. "The significance of this case is unclear, but there's no question it has gotten the attention of people." "
SCO & MS are injecting some good ol' fashion Uncertainty & Doubt into the minds of corporate IT people considering a Linux project with IBM. Both SCO & MS have nothing to lose by bringing this case.
Win: They get some $$ and stop IBM's new Linux business strategy
Lose: They spread enough UD around to make buyers hesitate, thus still stopping IBM's Linux business.
THIS SPACE FOR RENT Call 1-800-555-CARL
> Modern OSS lack original ideas.
No it doesn't. Look at GNU Radio. You can use it to decode HDTV signals. Try finding non-free software that does the same thing. The linux kernel has VFS (Virtual Filesystem Switch) which acts as an abstraction layer allowing you to mount and use many different file systems in the same way. That's pretty original. Look at OpenBSD. It has encrypted swap space and random pids. What other OS has that? Look at apache. Before apache you couldn't have more than one website per box. Look at Gnutella, it was the first distributed p2p software ever. And the list goes on....
Correct me if im wrong but didnt SCO aquire Xenix from microsoft some time in the eighties, Xenix then becoming SCO OpenServer. I wonder if this is a reason microsoft and SCO seem to be such good chum's. Also wouldnt it be embarasing if code from what was Xenix turned up in Linux!
If IBM illegally copied code that rightfully belonged to SCO,and is large enough to warrant real copyright protections, and it made it's way into linux, then we want SCO to win against IBM, and we want SCO to do the right thing, which is let us know which code it is so the linux world at large can work to remove that code from future versions.
Furthermore, realize that we aren't obligated to remove it immediately; even if IBM copied it into, say, OS2, their customers would not be obligated to uninstall their software. SCO can claim damages, but claiming control over all of linux sure isn't going to happen.
On the other hand, if scos claims are really baseless, we want them to die, because they suck.
To date, SCO has signed new licensing deals with two companies. One is Microsoft; the other has not been identified.
Could the other one also be Microsoft? Just thinking.
The dogcow says "Moof!"
Friends, I have seen the future.
The SCO Group has three core businesses now. One is OpenServer and UnixWare, which as we all know, suck to high heaven and have never had more than 2% market share in the Unix market. They also hav-- er, had their UnitedLinux offering, but now that we have discovered just how much Darl McBride hates Linux, it's safe to say that SCO OpenLinux is history.
That leaves us with SCO's newest business: SCOsource, their gambit in the lawsuit industry. Now, every time I think about SCO and the lawsuit and the questions being raised, I am reminded of a certain Texas energy trading company that is no longer among the living. SCO can't even confirm how much Unix IP they actually own. Novell says they have the patents as a certainty and some of the copyrights as well, and SCO won't say what they actually own. Meanwhile, SCO says that SCOsource is a key business unit, allowing them to record their extortion fees as regular income, suddenly making them a "profitable" company.
Consider Enron. They inflated their revenues by trading energy that didn't exist and raping their customers for doing so. Now look at SCO. They're suing their customers, claiming infringement of IP that may not exist (they certainly won't confirm or deny the existence of it!).
You'd think investors would have learned from the Enron incident, but nope. SCOX is over $10 for the first time in its history, and McBride and his FUD-spewing lawyer-demons are just waiting for the perfect opportunity to cash out. I just pray that justice is done and that this fscked-up company will be wiped off the face of the planet.
"I am root. Bow before me." To this I say, "You are root, and you bear the sins of the world upon your shoulders."
How the hell did this teenage troll get modded up? In case anyone actually believes he has a valid point (even though he can spell neither 'hobbyist' nor 'bogus'), here is a little rebuttal.
First, OpenBSD is probably one of the LEAST innovative software projects. It has to be -- innovative means untested, which usually means insecure. Hardly appropriate for a system which strives for the ultimate in security.
Second, SCO's claims have nothing to do with originality of ideas. They have everything to do with alleged code theft. You will have that problem in any open-source project, period. If it's actually innovative, you may also run into patents, which are much more of a problem.
Third, nobody wants "innovative" software, if innovative simply means "different". This is the fundamental difference between a computer science research project and enterprise-class software (which is what Linux is quickly becoming). Rejecting compatibility, adding "cutting-edge" features, and creating a brand-new untested design are all symptoms of amateurism and are OK for college students, but not for serious use. Rejectng backwards compatibility and/or a proven design is just like saying "let's tear down New York City and rebuild it with wider streets in order to solve traffic problems." It's a rather childish suggestion.
Ok, let's play what if.
Suppose there was a meeting. There were no notes taken of this meeting. No emails or memos were ever written that it even took place.
The meeting was between Microsoft and SCO.
Microsoft promises to keep SCO afloat...doling out money to them over the next 10 to 15 years. In small chunks. First up is to buy a license from SCO...totally out in the open. Saying that they just want to be on the up and up with any code they may write in the future.
But in exchange for Microsofts funding, SCO must openly attack Linux...the only thing that Microsoft truly fears. They must attack Linux, and all the big companies that support it. They must stir up a huge shit-storm around Linux and spout off FUD like there is no tomorrow. This will put doubt in the eyes of future Linux adopters, investors and users while Microsoft gains an even larger foothold.
But remember, there are no documents ever written to this effect. No emails that can be found or memos to be brought forward. No one even knows what is going on except the people at the top. No one has actually said "Linux must die". But this is the ultimate goal.
Just a thought.
"Music is everybody's possession. It's only publishers who think that people own it." - John Lennon.
How can you say this?
Although Linux originally started as a unix clone, it was derived from Minix which in turn was based on the unix methodology. But Linux has changed, grown, if it hadn't why would people now be using it?
Open source is different for exactly the reason that its open source, anyone can look it and they are free to change it. This means that the software is continually evolving - sometimes using multiple paths, with each contributing to the overall future of the software. Who knows what Linux will look like in another 10 years? but at least it can adapt, new hardware vendors can view the source and optimise their hardware/drivers ready for Linux and if needed the kernel itself can be changed to help accomodate them.
As other people have said any software can become tainted with other proprietry code, especially when you have source licenses from many
vendors used on one of your products.
Take for example the MSQL/Timeline patent issue.
How many people would be willing to start from scratch now? look how long the hurd has taken to emerge, and even now it uses code from Linux to help it take off.
Some would say that Gnome and KDE are just Windows wannabes, but for how long? again they will evolve over time as people demand new ideas and concepts.
So it's important that open source comes out of this mess as clean as possible because if it doesn't then important contributors may be scared off and thus reduce the speed at which the current open source movement is expanding.
This is purely a knee-jerk reaction by SCO^h^h^h Caldera to take as much as possible from our community when they realised that their business model had failed.
For a company that seems to hate Linux so much it is funny to see via Netcraft that Sco's site SCO.COM is running Linux. Seemed they used to use SCO UNIX but switched to Linux according to the graphs. Yet IBM, that pushes Linux runs on AIX.
Not only are there lines of SCO's code in Linux, but also derivative products based on SCO intellectual property have been created, Sontag said. Getting all of the protected bits out, assuming SCO's claims are valid, would be a huge chore.
"Our biggest issues are with the derivative code," he said. "It would be almost impossible to separate it out."
This is the first time that SCO has essentially admitted in the open what some have been saying all along: SCO does not believe that Linux coders can ever "clean" Linux up; simply replacing "infringing" lines of code with new code is not enough becasue they are trying to claim that Linux itself is now a derivative product of SCO Unix.
The chances of this going away before SCO is utterly dead are zero. SCO has no intention of easily revealing the "matching" lines of code because they believe that they are irrelevant... as far as SCO is concerned, every line of code in Linux is infringing and it is essentially beyond repair. Since it is open-source, Linux can't license proprietary code from SCO. Ergo, the courts should essentially put an end to Linux in much the same way that they did with DeCSS code. At least, this seems to be how SCO sees it.
STOP . AMERICA . NOW
In a surprise announcement, today, SCO head Darl McBride, announced that his company had hired former Iraqi front man Tariq Aziz to handle media inquiries about SCO's legal battle with IBM. SCO's president and chief executive officer seemed very upbeat at the announcement, stating that Mr. had oodles of related experience.
Specious evidence, extravagant claims, hidden proofs, enormous odds.. Mr. Aziz has seen (or used) it all. He understands how it works, and he's shown himself able to handle even the most hostile media attention. We believe that he'll provide an excellent source of of knowledge and leadership.
When asked about the questionable morals of Mr. Aziz's former employer, Mr McBride blustered.
"This is about business -- not morals." said McBride. "Our job is to make as much money for our stockholders as possible within the bounds of the law. Mr. Aziz obeyed the decr... laws of his former country and we expect him to do the same here."
Questions about Mr. Aziz's immigration and legal status were brushed off as "a telecommuting issue". When asked about the former Iraqi functionary's whereabouts, Mr McBride only mumbled something about being "one with the source code".
Free Software: Like love, it grows best when given away.
When not anonymous, I work for IBM.
The lawyers there are PICKY.
When dealing with IP, before a project goes out the door, the lawyers go over the thing with a fine-tooth and make sure:
a) We have legal rights to what we're about to put on the market.
b) Everything we have legal right to, we've properly and appropriately protected. (Such as patented, if appropriate - it's not always.)
When buying software from 'outside', the lawyers go through the license terms to make sure it's 'appropriate', and sometimes it's a pain in the neck. Sometimes it seems it takes so long to buy a new, never-before-bought piece of software that by the time you can get it, the need is gone.
Before you can use Linux inside IBM, you need to take the online "Open Source Legal Course" (title probably abridged) and sign off that you have. The mini-course discusses the legal implications of the GPL, etc.
None of these cases is exactly like the SCO case. But the legal folks are so darned diligent about IP that I can't see anything like what SCO alledges happening inside IBM. The place just doesn't work that way.
it's just too easy to point a finger at MS each time linux is attacked in some shape or form. Sun is actually getting hit alot harder by linux's popularity than MS. Second undisclosed company licensing SCO's "technology"?? hmmm Sun Micro?
Look at SCO's P/E ratios. SCO does not have a P/E ratio, because it is NOT making any earnings. The stock is thus, no matter how low it is priced, over-valued. Would you pay 50 dollars for a dollar bill just because millions of fuckwits were also paying 50 dollars for a dollar bill?
If you want to invest in a company, SCO is not the one to invest in. Never invest in a company with a P/E ratio that's larger than the average in it's industry, and larger than it's P/E:G ratio (price/earnings to growth...it's ok if the stock has a high P/E as long as it's growing rapidly enough to accomodate that P/E).
social sciences can never use experience to verify their statemen
I think you've been too confused by the idiotic "They GPL'd their code when they sold linux", which is probably not true.
Only because they probably don't have any code inserted into Linux. But if they did, it would be under the GPL.
SCO clams that someone from inside IBM inserted their code into Linux
No, they are most definitely NOT claiming this.
They are claiming two things - first that "someone" put their code into Linux.
Second, they are claiming that IBM used "knowledge" of their OS to make Linux better.
The two issues are completely separate.
There are no allegations of code theft against IBM. Their sole complaint is "Linux hackers suck, so the only way that Linux could compete against us is if IBM helped them."
Now, if there really is SCO-owned code in Linux, SCO distributed that code knowingly. They know it's there, they know that the kernel is covered under the GPL, and they are still distributing it.
SCO is implicitly licensing their code under the GPL because they continue to distribute Linux. They must have agreed with the GPL, because nothing else grants them the right to continue distributing it.
even if they had never touched the GPL they still would have had code leakage
True, and thier actions state exactly how much any alleged code is worth to them.
The doctrine of laches says that if an injured party wants to claim damages, they must minimize the damages. Since SCO won't allow anyone to remove the alleged code (they refuse to say what the alleged code is, or where it is), then they are unable to claim injury.
By refusing to tell anyone what the alleged code is, they are effectively saying that any code that might be in the kernel is worthless to them.
In fact IBM is inherently no safer than any other stock. If you want safety, buy treasuries. The government can just print up more money if they need to pay you.
http://www.theinquirer.net/?article=10018
SCO has been sent a Cease and Desist by one of the kernel hackers. The hacker is demanding FTP logs and other records so he can determine the degree of infringement against his copyright. He is promising that he will sue unless SCO ceases their claims against other parts of the kernel.
Every contributor to the kernel can do this. I hope those scumbags get hammered for every penny they have.