SCO Hints at *BSD Lawsuits Next Year, And More

shystershep writes "Apparently attacking one Unix-like OS isn't enough. According to Darl McBride, SCO has plans to target BSD. "The more yarn you pull out the more you see," according to McBride. They're a little preoccupied with the IBM litigation right now, though, so "we probably won't file any suits against BSD until sometime in the first half of next year." Hmmm. I can't imagine why SCO executives feel that they need to hire bodyguards." How to get at the *BSDs? vireo writes "In this Newsforge story, we learn that Boies, Schiller & Flexner will directly attack the 1994 AT&T/BSD settlement." Read on below for another handful of updates on the giant SCO lawsuit frenzy.

osullish writes "The Financial Times reports that SCO is indicating it will sue an as-yet un-named Linux-using corporation within the next 90 days. Also mentioned in the article is possible action against Novell, which recently purchased Ximian and SUSE Linux."

Iaitos points to this rather stiffly-worded notice from Novell (on their site) regarding the non-compete agreement SCO claims would taint Novell's acquisition of SUSE:

PROVO, Utah Nov. 18, 2003: Novell has seen the November 18 InfoWorld article in which SCO CEO Darl McBride refers to a supposed non-compete agreement between Novell and SCO. Mr. McBride's characterization of the agreements between Novell and SCO is inaccurate. There is no non-compete provision in those contracts, and the pending acquisition of SUSE LINUX does not violate any agreement between Novell and SCO.

Novell has received no formal communication from SCO on this particular issue. Novell understands its rights under the contracts very well, and will respond in due course should SCO choose to formally pursue this issue."

slavitos points to a ZDNet article covering the same ground, writing: "A characteristic SCO twist in the story: "McBride added that lawsuits likely will be preceded and possibly prevented by communications offering businesses an opportunity to get right with SCO. "We'll be communicating with users what our expectations are," he said.". Oh, that's helpful, Darl - and no, we didn't really expect you to be any more specific."

If your lips aren't yet too tired, ansak writes "PJ has done it again -- okay, "co-ordinated it" would be the better phrase. The transcript of SCOG's conference call is now available (and in danger of being slashdotted without slashdot's help, even!).
#include <std.thanks.to.volunteers.h>"

Another legal theory being thrown about is that SCO's lawsuit (the one against IBM, that is) all leads back to Sequent. Petrol writes "The Inquirer has a story about SCO's action against IBM. 'Sources close to the action describe a trail of code that might well be the target of SCO's ire against IBM and the Linux community.'"

Comments

Apple?

[mgs1000]

So does this include OS X? That should be an interesting fight.

Its over the dinosaur is dead

[Crashmarik]

Its just going to take alittle while for the peabrain (Mcbride, boies et al) to get the message.

SCO's stock has gone from a high of 21 to 14 today, its no longer reacting to the press releases. Even Forbes is now referring to the canopy group as shakedown artists. McBride and company are increasingly running out of people who will buy their story or invest in their stock.

The last time sco had a teleconference they managed a 50 percent bump in share price. This time they got a 1.5 percent bump. This is despite the fact that they have now widened their suit to include contractual control over Novell and BSD.

The big worry will be what happens when sco does give up the ghost. Theres alot of people that depend on the software to run their businesses. They had nothing to do with the lawsuit and will be hurt when the message does at last get to the brain of the beast.

BSD Code Settlement

[rstultz]

Wasn't that case settled because of the fact that AT&T had copied a bunch of BSD code, and the realization had been made that both had screwed up and the easiest course of action was to say "From this day forth..." both were legal? that's always been my understanding of that settlement.

If SCO attacks it, don't they also open themselves back up to claims against AT&T (which SCO would now have to defend) of stealing code from BSD and putting it into their codebase (UNIX, SVWhatever)?

My question would be, can they really open up that can of worms again? And if they do, don't they open themselves up to accusations of IP infringement? Would they have to then clean up the UNIX codebase to remove any infringement that the settlement allowed?

Ryan Stultz

Re:We get it already, SCO

[Zeinfeld]

I'm also starting to hope that Boies will share the cell...

I find it very strange that Boies has reached this superstar status on the back of what is by any measure a lacklustre litigation record.

Boies first came to prominence in the Microsoft case. Athough the case was initially 'won' it was overturned on appeal. This has been Boies best result so far.

In the Florida recount case Boies lost what should have been a slam dunk case, demanding that the state perform a recount required by the election laws. Boies lost in this case because he was outmaneuvered by the Republican party lawyers who ran rings arround him.

Boies next took the Napster case, in this case he was successful in gaining a temporary stay of an injunction against Napster. But we later find this was only because one of the Appeals court judges was anxious that Napster survive long enough for the appeals court to be able to make a really important rulling in the copyright area...

I cannot think of a better council for SCO in this particular case. The court will require SCO to reveal the exact code fragments it claims are subject to copyright claims sooner rather than later. At this point the SCO case will quickly unravel since the fragments in question will be rewritten.

There are absolutely no grounds for supressing the specifics of the SCO claim. The whole point of the copyright bargain is disclosure in return for a limited term monoploy on exploitation.

Re:We get it already, SCO

[jazzsupe]

I would not write off Boies nor take him lightly. He came to prominence well before the Microsoft case. Previously he was the star litigator for, arguably, the most respected and venerated law firm in the U.S.: Cravath, Swaine & Moore. For quite a while he has been considered one of the top 3, or so, litigators in the U.S. The Microsoft case simply brought him attention from the non-legal community.

When Boies left the Cravath partnership, it was somewhat of a scandal in the legal community. No one walks away from a Cravath partnership (so goes conventional wisdom) -- the average annual salary for Cravath partners is somewhere in the neighborhood of $2.0 million.

IBM has long been one of Cravath's largest and most loyal clients -- in fact, I noticed that Cravath is representing IBM in the SCO matter. I can't help but wonder if one of the main reasons Boies agreed to represent SCO is to go head-to-head with his former parters at Cravath. It wouldn't surprise me if that is his main motivating factor. Boies does not need the money or any more notches in his belt.

The fact that Boies lost a couple prominent cases speaks more to his willingness to take on tough cases with unpredictable outcomes that he finds interesting or challenging.

But do not write off Boies or dismiss him. Don't get me wrong -- I hope he loses the SCO case big time. But he is to be feared.