Language Selection

English French German Italian Portuguese Spanish

Legal Setback Raises Questions Of SCO's Survival

Filed under
OS

Unix vendor SCO Group's intellectual property lawsuit against IBM has been widely seen as a go-for-broke strategy. Now it looks more like just a plan to go broke.

Utah District Court Magistrate Judge Brooke Wells in late June dismissed 182 of the 201 claims IBM sought to have thrown out of the case; 112 claims remain. The legal action dates back to March 2003, when SCO charged that IBM's contributions to the Linux open source operating system contained lines of code that it had purloined from SCO's Unix software.

Judge Wells said the dismissed claims lacked the specificity needed to hold up in court. SCO, in most instances, failed to identify which lines of code IBM is alleged to have taken improperly.

One analyst says the ruling means that commercial Linux users can breathe easier. A SCO spokesman said there has been "no change" in the policy outlined in McBride's screed. But given last week's ruling, odds are that SCO won't be around long enough to chase down any more Linux users.

Full Story.

SCO's Survival

I've been reading Groklaw 2-3 times a week for last couple of years, and following the IBM v SCOG and Novell v SCOG cases with varying degrees of attention.

Pamela Jones (the founder/head of Groklaw) has been right all along.

Of the 112 claims that remain in the IBM v SCOG, a few are easily shown as spurious, and the remainder will likely be shown as prior art--if, indeed, SCOG survives long enough to actually pursue them the court. Pamela and Groklaw's crack gang of researchers have already been doing vast amounts of homework on the prior art. Whether it's short run, or long run, SCOG is toast.

The one thing I've always admired about Groklaw is their unflagging effort to print source documents--it's not just a bunch of pundits pontificating--you get to read the source material (when it can be obtained), and you can draw your own conclusions. Very much in the Open Source spirit.

It has also brought home why I would never, never, never become a lawyer Smile.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

more of today's howtos

Leftovers: OSS and Sharing

Microsoft Begs, Bugs, and Bug Doors

  • Don't install our buggy Windows 10 Creators Update, begs Microsoft
    Microsoft has urged non-tech-savvy people – or anyone who just wants a stable computer – to not download and install this year's biggest revision to Windows by hand. And that's because it may well bork your machine. It's been two weeks since Microsoft made its Creators Update available, and we were previously warned it will be a trickle-out rather than a massive rollout. Now, Redmond has urged users to stop manually fetching and installing the code, and instead wait for it to be automatically offered to your computer when it's ready.
  • Microsoft Word flaw took so long to fix that hackers used it to send fraud software to millions of computers
    A flaw in Microsoft Word took the tech giant so long to fix that hackers were able to use it to send fraud software to millions of computers, it has been revealed. The security flaw, officially known as CVE-2017-0199, could allow a hacker to seize control of a personal computer with little trace, and was fixed on April 11 in Microsoft's regular monthly security update - nine months after it was discovered.

FOSS Licensing (and Lack Thereof)

  • Portugal to harmonise usability of govt portals
    All of the code, information and tools are made available for reuse.
  • JRC: ‘Releasing code without a licence hinders reuse’
    Projects that publish source code without a licence weaken the reusability of their code, warns Stefano Gentile, a copyright and trademark specialist working for the European Commission’s Joint Research Centre (JRC). Currently just 20 % of all projects published on GitHub, one of the most popular source code sharing platforms, have selected a licence for their work - down from about 60% in 2008, Gentile said, quoting numbers published in 2015 by GitHub.
  • React to React
    The Additional Grant of Patent Rights is a patent license grant that includes certain termination criteria. These termination criteria are not entirely unprecedented when you look at the history of patent license provisions in OSI-approved licenses, but they are certainly broader than the termination criteria [or the equivalent] in several familiar modern licenses (the Apache License 2.0, EPL, MPL 2.0, and GPLv3).
  • BetConstruct declares the source code for its front-end as open source
    The project is distributed under MIT license.