Language Selection

English French German Italian Portuguese Spanish

SCO Unveils Latest Product Upgrade: IBM Lawsuit 4.0

Filed under
Humor

The SCO Group, everybody's favorite lawsuit-factory-disguised-as-a-software-vendor, today unveiled version 4.0 of its flagship litigation product, SCO v. IBM.

"Our top-of-the-line product now boasts new arguments, new evidence, new discovery demands, and new counter-counter-counter-motions designed to provide additional value to our customers and shareholders," said SCO's Assistant Vice Director Media Relations Specialist Third Class.

According to a four-color glossy brochure distributed by SCO, the cornerstone of IBM Lawsuit Amended Complaint 4.0 is the argument that GPL-licensed code should be seized under eminent domain laws to provide greater economic development.

"All of this valuable code is being squandered by the draconian anti-corporate, anti-American, pro-pinko-Commie GPL license that the Free Software Foundation has rammed down everybody's throats," says the brochure. "But thanks to the recent decision by the Supreme Court, the tyranny of the GPL can -- and must -- be stopped through the eminent domain process."

SCO proposes that all of the open source code held by the FSF, IBM, and Novell should be "liberated" and turned over to SCO. In its Complaint 4.0, SCO argues that "this move will provide huge public benefits by increasing tax revenue, creating jobs, protecting national security, fighting terrorism, and boosting economic development efforts nationwide."

In addition, SCO's upgraded litigation product (all 512 pages) includes the following new-and-improved contentions:

  • The GPL establishes an illegal monopoly

  • The GPL promotes slavery
  • Free software represents illegal campaign contributions
  • Open Source harms the environment
  • GPL undermines national security and aids terrorists
  • Open Source development violates child labor laws
  • The Linux mascot is degrading to penguins

Punchline.

More in Tux Machines

Programming: Go, Bugs and LLVM

  • 3 ways to copy files in Go
    This article will show you how to copy a file in the Go programming language. Although there are more than three ways to copy a file in Go, this article will present the three most common ways: using the io.Copy() function call from the Go library; reading the input file all at once and writing it to another file; and copying the file in small chunks using a buffer.
  • The life cycle of a software bug
    During the process of testing, bugs are reported to the development team. Quality assurance testers describe the bug in as much detail as possible, reporting on their system state, the processes they were undertaking, and how the bug manifested itself. Despite this, some bugs are never confirmed; they may be reported in testing but can never be reproduced in a controlled environment. In such cases they may not be resolved but are instead closed. It can be difficult to confirm a computer bug due to the wide array of platforms in use and the many different types of user behavior. Some bugs only occur intermittently or under very specific situations, and others may occur seemingly at random. Many people use and interact with open source software, and many bugs and issues may be non-repeatable or may not be adequately described. Still, because every user and developer also plays the role of quality assurance tester, at least in part, there is a good chance that bugs will be revealed.
  • LLVM's OpenMP Offloads Liboffload Into Oblivion
    The liboffload library has been dropped from LLVM's OpenMP repository. Liboffload is/was the Intel runtime library for offloading and geared for supporting the Xeon Phi co-processors. But liboffload within LLVM hasn't been receiving updates, it wasn't properly integrated within the LLVM build system, and unfortunately Xeon Phi co-processors appear to be discontinued. The liboffload library has also confused some with LLVM's libomptarget library for OpenMP support that is in much better shape.

Games and Wine (Staging) Leftovers

Free Software: Kiwi TCMS 4.2, PeerTube in the News

  • Kiwi TCMS: Kiwi TCMS 4.2
    We're happy to announce Kiwi TCMS and tcms-api version 4.2! This is a security, bug-fix and enhancement update which upgrades to the latest Django version under Python 3.6. We've pushed new kiwitcms/kiwi:latest docker image to Docker Hub and updated the demo instance at https://demo.kiwitcms.org! This version also includes GDPR related changes which affect our project. Read below for the details.
  • PeerTube: An Open Source YouTube Alternative To Beat Censorship
    When it’s about watching videos online, YouTube is the first thing that comes to our minds. But the popular video sharing platform is often subjected to censorship in many countries. There are many countries including China and North Korea that ban YouTube from time to time. Leave the others, recently, even YouTube ended up blocking many legitimate Channels as a collateral damage of its copyright crackdown. Ultimately, the content creators are the ones who get affected due to all of this blocking.
  • PeerTube: A ‘Censorship’ Resistent YouTube Alternative

    YouTube is a great video platform that has a lot to offer to both consumers and creators. At least, those who play by the rules. For creators, there is a major drawback though, one that put a spotlight on the alternative 'free-libre' software PeerTube this week.

OpenBSD chief de Raadt says no easy fix for new Intel CPU bug

Recompiling is unlikely to be a catch-all solution for a recently unveiled Intel CPU vulnerability known as TLBleed, the details of which were leaked on Friday, the head of the OpenBSD project Theo de Raadt says. The details of TLBleed, which gets its name from the fact that the flaw targets the translation lookaside buffer, a CPU cache, were leaked to the British tech site, The Register; the side-channel vulnerability can be theoretically exploited to extract encryption keys and private information from programs. Read more