Slashdot Mirror
SCO Gives Notice To 6,000 Unix Licensees
inode_buddha writes "This article describes SCO's recent letters to its UNIX licensees, asking them to certify that they '...are not using Unix code in Linux.' It also notes another set of letters '...outlining additional evidence of copyright infringement to a subset of 1,500 global Linux users that SCO first contacted in May about copyright infringement.' There's also a decent breakdown of the company's balance sheet and some quotes from company officials. I hope to see one of those 'other' letters; could anyone post it? SCO better have asbestos underwear." Ask and receive: idiotnot adds "Here's the article from the Sydney Morning Herald. Here is a PDF Copy of the letter." "Yours truly"?
.After almost 2 weeks of no SCO stories, I was begining to delevop a bit of a nervous tic!
Now, if you'll excuse me, I have backups to corrupt.
By sending out these clearly fraudulent legal notices-- which at best claim copyright over something which is uncopyrightable, and at worst is an attempt by a third party to claim that it is illegal for people to use the materials owned by the BSD regents under the BSD license in the manner in which the BSD regents intended the BSD license to be used-- has SCO opened itself up to legal action?
SCO has in the past managed to sidestep most allegations of fraud by being horrendously vague. They said that they were owned money but never sent any invoices, sidestepping mail fraud. They tried to present things as if you needed an SCO license to use linux, but if you tried to talk to talk to them, they were actually selling UnixWare licenses and not in the process actually distributing linux to you, sidestepping GPL violations. However, this is entirely non-vague. It seems to me that SCO has stepped over some sort of line here and this is actionable.
I know that the law does not seem to have many consequences for people who send out bad takedown notices, but surely there must be something preventing company A from finding lists of competitor B's customers and sending them takedown notices for using some portion of competitor B's product that company A does not, in fact, own.
At the least, can this be added to the lanham act/ restraint of trade/ libel or whatever countersuits that Redhat and IBM have going? What are the options from here, and what will actually happen?
...and i've been putting unix code into linux. Do they expect people to admit it?
This SCO notification is brought to you by the letters 'U' and 'O' and the numbers '6' and '0'.
try { do() || do_not(); } catch (JediException err) { yoda(err); }
This has to be some pathetic cry for help. Later, we'll look back and think "If we'd said something or done something, perhaps it didn't have to happen that way." Then we'll remember that it was Darl and SCO, and shrug.
One line blog. I hear that they're called Twitters now.
Yes I skimmed the story, and I was pleasantly surprised to see an advert for IBMs linux solutions halfway down the main body of the text. That's intelligent ad placement at it's best :)
Please don't! Rewarding these criminals will set a bad example for everyone else. You are right. They are wrong. Sit it out. Make them pay in the end. That's the only way to deal with their kind.
(aka "We don't negotiate with terrorists")
Ironic that at least two Caldera employees have, with Caldera's blessing, contributed code to Linux. End of case, you can all go home now.
Perhaps Linus should send a similar letter to SCOX and the same addressees, requiring them to guarantee that none of their SCOX or derivative code includes any contributions from the Linux codebase?
Got time? Spend some of it coding or testing
This is really getting loony--but I just realized that time is up. It's already been about a month since SCO was told to produce some REAL goods. It's obviously some sort of diversionary move, but a really crazy one. I'm straining my brain to understand it, but all I can think is that they want to claim this is how they are "protecting" their IP rather than performing normal due diligence. I bet the judge is not going to be amused. Can you say "contempt of court"?
Remember the NORMAL non-SCO behavior is to say what the disputed IP actually is--but in that case the problem--if there is any real problem--would have been fixed LONG ago. Want to take any bets if there's any code in the 2.6 Linux kernel that has ANY relation at all to anything from SCO?
In related news, SCO admits they paid $9 million to the lawyers last year--but also claims they managed to clear $5 million net. Which number do you trust more? I say the 5 is just more FUDging.
Freedom = (Meaningful - Coerced) Choice != (Speech | Beer^2), and sad sock puppets' bad mods avail them naught.
Your imagination is not my problem. I no more need to certify to you that I am not using your intellectual property than that I am not using alien UFO technology in our corporate restrooms. A assertion must stand on its own merit, and any response to that assertion must necessarily be based upon that merit.
Having established that point, I think I have found a use for your assertions in our corporate restrooms.
who are those slashdot people? they swept over like Mongol-Tartars.
From the letter:
Neither you nor your contractors or employees with access to the Software Products have contributed any software code based on the Software Products for use in Linux or any other UNIX-based software product.
I'm still waiting to actually see the evidence that SCO claims is in the Linux source code.Apparently SCO is waiting to see the evidence as well. Why else would they keep asking everyone else to see if there is any?
The Better Business Bureau is a paper tiger - just because a company is listed as "satisfactory" with them does not mean the company is not a wretched hive of scum and villany.
The BBB used to be feared and respected - threatening a company with "I'll report you to the BBB" caused great gnashing of teeth and usually got things fixed quickly.
But little by little, companies realised that they could target the BBB with lawsuits for definition^Wdefamation of character. They realised that they could join the BBB, and thus slowly subvert its goals toward their own ends.
Little by little the BBB became flooded with reports, and little by little the BBB began to pursue only the most egregious examples of behavior - ignoring little things to concentrate on "what really matters".
Little by little, the response to "I'll report you to the BBB" became <voice name="butthead">" Yawn Yeah, whatever, go 'way, you suck"</voice>
True, if you find a company listed as "unsatisfactory" by the BBB you should run as though the very demons of hell pursued thee, but assuming that a clean bill of health from the BBB means that a company is clean is a very WRONG leap of faith.
(For fun, you can go through the above with the following replacements and it will be equally valid:
s/BBB/MAPS/g
or
s/businesses/posters/g && s/BBB/moderators/g
)
www.eFax.com are spammers
How exactly are the licensees supposed to certify that they're NOT using UNIX code in Linux, if SCO is unwilling to identify said code??? I mean, a kernel changes a lot depending upon what has been compiled in... how do I know if I'm using it or not?
Can somebody mod SCO -1 TROLL?
Saw this on the Yahoo board:
"From The Wall Street Journal, 1/5/2004, page B1, by Lee Gomes:"
"As for Linux, when will the courts halt the lies of has-been software maker SCO (with $13 million in funding from Microsoft and Sun -- together at last!) as it tries to make the preposterous claim that it, and not the world, owns the free operating system?"
Not even the business press is taking them seriously any more.
Belief is the currency of delusion.
SCO
If you: license our technology
Then: you are first in line when we roll out our sue-the-world plan.
Whack-A-Burger
If you: buy one of our burger value meals
Then: the fry cook gets one free whack at you with a 2-by-4 on your way out of the restaurant
Ben Dover Bowling Lanes
If you: rent one of our lanes for an hour
Then: the ex-convict who works behind the counter demonstrates who is your daddy when you bend over to pick up your bowling shoes
No, actually the quoted text in your post says "containing our copyrighted application binary interface code". They haven't proved that the versions you mention do contain such code and until they have, any such speculation remains just that.
Resistance is futile. Reactance buggers it up.
I read the PDF of the letter.
This letter assumes the guilt of all its licencees until proven otherwise. SCO is demanding corporate HR documents (non-disclosure) for each employee who might come in contact with their software stating that they will follow the licence and letter provisions to the T. The letter also seems to suggest that users of SCO software must swear under threat of legal action never to use Linux, and never to develop GPL software. Unbelievable.
If there was any doubt before, there is none now. This letter can't possibly be seen as anything but insulting, even by historically staunch SCO supporters. I've never seen such arrogance. I feel like I'm reading Hitchhikers' Guide to the Galaxy.
DIE SCO. I can't wait to read that SCO has finally died, and that its officials and officers are being brought up on criminal charges. What a bunch of fucking crooks.
Has it been actually verified that these letters were really sent? Since this scam began, scox has told numerous lies of this nature. Here are a few examples of scox's outright lies (from a yahoo poster):
,"'To clarify, the individuals reviewing the code had been involved with MIT labs in the past, but are not currently at MIT."
Lie: We've gone in, we've done a deep dive into Linux, we've compared the source code of Linux with UNIX every which way but Tuesday
Truth: Experts have shown that SCO used a simple, primitive text search based on a few keywords.
Lie: SCO's expert witnesses are "MIT Mathematicians".
Truth: Among various backpedaling statements, Paul Hatch, a SCO spokesman, wrote in a statement to The Tech
Lie: SCO received the D&T Fast 500 recognition because of the strong UNIX market, IP enforcement and the Web services strategy
Truth: SCO made the list because of revenue growth due exclusively to the Tarantula acquisition.
Lie: The IP protection legal team is on pure contingency
Truth: The legal team is billing at a 2/3 discounted rate with the possibility of contingent commissions
Lie: Boies was compensated $1.6M for a contingent event
Truth: The engagement agreement specifically excludes heritage UNIX OEM license deals; Boies is being compensated 20% of the $8MM Microsoft license deal, which is a follow-on extension of the first deal, a UNIX license deal not eligible as a contingent event.
Lie: Invoices will be mailed to Linux users by October 15, 2003
Truth: No invoices were ever mailed.
Lie: We will show rock solid evidence at SCOForum in Las Vegas
Truth: SCO was quickly shown to not have any ownership of the SCOForum evidence
Lie: The Berkeley Packet Filter code in Linux is "obfuscated" SCO code.
Truth: Jay Schulist, who never had access to SCO code, implemented it from scratch.
Lie: SCO's 2002 UNIX source release was "non-commercial" and excludes 32-bit code
Truth: "The text of the letter, sent January 23, 2002, by Bill Broderick, Director of Licensing Services for Caldera [now SCO], in fact makes no mention of "non-commercial use" restrictions, does not include the words "non-commercial use" anywhere and specifically mentions "32-bit 32V Unix" as well as the 16-bit versions."
Lie: We have been off meeting for the last several months with large corporate Linux end users. The pipeline is very healthy there.
Truth: The pipeline is empty. All inquiries have been to assess SCO's claims and liability exposure.
Lie: We have done additional signups for Linux end-user licenses. We have a number of folks that are in the evaluation process, and we definitely have a lot of interest in what's going on there.
Truth: During the earnings conference, SCO admitted that not a single Linux end-user license has been sold. Follow-on guidance comments warn that no such sales are expected in Q1.
Lie: Our claims are not trivial.
Truth: Based on evidence provided to date, SCO's claims are extremely trivial, debunked in a matter of hours
Lie: claims that SCO has are both broad and deep.
Truth: SCO's has made a breach of contract claim and a copyright infringement claim; all evidence presented to date has shown each of these claims to be trivial and unfounded
Lie: These claims touch not, just not IBM, but other vendors as well.
Truth: Exhaustive code reviews by other SYSV licensees, including HP and SGI, have shown that the only Linux/SysV overlap concerns a small amount of public domain code.
Lie: (To the Utah Judge on 12/5) SCO will make a copyright claim in two days, but no longer than a week
Truth: Many weeks later and a copyright claim has not yet been made.
Lie: During the recent road tour, Blake Stowell indicated that core operations were profitable in Q3.
Truth: Core operations lost $3.8MM in Q3-03.
Lie: Sco will audit AIX users.
Truth: It never happend.
Lie: Sco will revoke IBM rights to use, support, or distribute AIX.
Truth: Those rights can not be revoked by scox.
If some "licensee" really feels that they ought to respond to the letter, but doesn't want to do a cpu-by-cpu certification, there are standard stalling tactics that they can use to keep SCO from calling them non-compliant until IBM kills SCO.
For example, the day before the deadline, send a letter explaining there are exigent circumstances, and asking for a 90-day extension of the deadline.
Repeat until SCO says no, then send a "please accept under separate cover" letter, referring to a document that seems to have gotten lost in the mail. Buy more time by "searcing" for the lost document.
When SCO demands a new copy of the document be prepared and sent, send an open envelope, and marvel at the bad luck that the contents of the envelope have been lost.
So on and so forth.
All you have to do is stall until SCO is killed by the big guys.