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

Fuck you SCO

[Leroy_Brown242]

Stop being bitches.

Re:Fuck you SCO

[Leroy_Brown242]

No Problem.
any time.

Re:someone make a list of SCO threats

[mrpuffypants]

Hang on, I was planning to do this just after I'm done compiling a list of Windows security flaws

Dare me.

[Mariner77]

Booo! I'll cold blood murder that son of a b*tch if he dares to touch Darwin inside my Mac.

Re:We get it already, SCO

[IM6100]

The Goreans may have known more than we give them credit for. Possibly a recount, if it included things like the military absentee ballots, would have gone even further against them.

There certainly has been no recount, formal or informal, would have given algore the electoral votes.