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

GNOME Desktop: Flatpak and Random Wallpaper Gnome Extension

  • Flatpak in detail, part 2
    The first post in this series looked at runtimes and extensions. Here, we’ll look at how flatpak keeps the applications and runtimes on your system organized, with installations, repositories, branches, commits and deployments.
  • Flatpak – a history
    I’ve been working on Flatpak for almost 4 years now, and 1.0 is getting closer. I think it might be interesting at this point to take a retrospective look at the history of Flatpak.
  • Random Wallpaper Gnome Extension Changes Your Desktop Background With Images From Various Online Sources
    Random Wallpaper is an extension for Gnome Shell that can automatically fetch wallpapers from a multitude of online sources and set it as your desktop background. The automatic wallpaper changer comes with built-in support for downloading wallpapers from unsplash.com, desktopper.co, wallhaven.cc, as well as support for basic JSON APIs or files. The JSON support is in fact my favorite feature in Random Wallpaper. That's because thanks to it and the examples available on the Random Wallpaper GitHub Wiki, one can easily add Chromecast Images, NASA Picture of the day, Bing Picture of the day, and Google Earth View (Google Earth photos from a selection of around 1500 curated locations) as image sources.

today's howtos

KDE: QtPad, Celebrating 10 Years with KDE, GSoC 2018

  • QtPad - Modern Customizable Sticky Note App for Linux
    In this article, we'll focus on how to install and use QtPad on Ubuntu 18.04. Qtpad is a unique and highly customizable sticky note application written in Qt5 and Python3 tailored for Unix systems.
  • Celebrating 10 Years with KDE
    Of course I am using KDE software much longer. My first Linux distribution, SuSE 6.2 (the precursor to openSUSE), came with KDE 1.1.1 and was already released 19 years ago. But this post is not celebrating the years I am using KDE software. Exactly ten years ago, dear Albert committed my first contribution to KDE. A simple patch for a problem that looked obvious to fix, but waiting for someone to actually do the work. Not really understanding the consequences, it marks the start of my journey within the amazing KDE community.
  • GSoC 2018 – Coding Period (May 28th to June 18th): First Evaluation and Progress with LVM VG
    I got some problems during the last weeks of Google Summer of Code which made me deal with some challenges. One of these challenges was caused by a HD physical problem. I haven’t made a backup of some work and had to rework again in some parts of my code. As I already knew how to proceed, it was faster than the first time. I had to understand how the device loading process is made in Calamares to load a preview of the new LVM VG during its creation in Partition Page. I need to list it as a new storage device in this page and deal with the revert process. I’ve implemented some basic fixes and tried to improve it.

Open Hardware: Good for Your Brand, Good for Your Bottom Line

Chip makers are starting to catch on to the advantages of open, however. SiFive has released an entirely open RISC-V development board. Its campaign on the Crowd Supply crowd-funding website very quickly raised more than $140,000 USD. The board itself is hailed as a game-changer in the world of hardware. Developments like these will ensure that it won't be long before the hardware equivalent of LEGO's bricks will soon be as open as the designs built using them. Read more