decoration decoration

When you want to know more...
For layout only
Site Map
About Groklaw
Legal Research
ApplevSamsung p.2
Cast: Lawyers
Comes v. MS
Gordon v MS
IV v. Google
Legal Docs
MS Litigations
News Picks
Novell v. MS
Novell-MS Deal
OOXML Appeals
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v Novell
Sean Daly
Software Patents
Switch to Linux
Unix Books
Your contributions keep Groklaw going.
To donate to Groklaw 2.0:

Groklaw Gear

Click here to send an email to the editor of this weblog.

Contact PJ

Click here to email PJ. You won't find me on Facebook Donate Paypal

User Functions



Don't have an account yet? Sign up as a New User

No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.

What's New

No new stories

COMMENTS last 48 hrs
No new comments


hosted by ibiblio

On servers donated to ibiblio by AMD.

Now They Are Starting to Look at the GPL?
Wednesday, June 11 2003 @ 12:34 PM EDT

According to this article in Electronic Commerce Times, "Will SCO's Suit Chill the Penguin?" SCO is just now starting to look at the GPL.

From comments in the article, I'd say they still don't get it:

Did SCO Know?

However, Stowell said, when the company discovered that its source code had been incorporated into Red Hat Linux, it stopped distributing its own version of Linux and ended any further Linux development. This move, he noted, showed that SCO was acting according to a GPL clause that could shore up its case.

"After the preamble, it says the code has to be contributed knowingly in order to be considered part of the GPL license," he explained.

Like the difference between "dead" and "almost dead," everything hangs on one word. Stowell maintains that because SCO never knowingly contributed proprietary Unix code to Linux, and ceased distributing GPL'ed code when it discovered the error, the company is off the hook.

These guys are so funny. They didn't know that they were releasing a GPL product until last month? Puh-lease.

I earlier presented some evidence that they certainly knew years ago in a post on May 19.

[Update: You'll notice that the Electronic Commerce Times article shows the following correction:

*Editor's Correction Note: In the original version of this article, we incorrectly stated, "A few years ago, when SCO was called Caldera, it purchased the ownership and rights to Unix from AT&T, including the pertinent licenses." In fact, the original SCO company purchased the Unix ownership and rights from Novell before being acquired by Caldera (which then adopted the SCO name for the combined company). Previously, Novell had bought Unix Systems Laboratories (USL) from AT&T, gaining the Unix rights for itself. Also, we initially reported, "According to GPL licensing terms, if any GPL'ed code is included in a release, the entire release immediately becomes covered under the GPL." In fact, if GPL'ed code is included in a release, the distributor has two options: to actively make the rest of the code in the release available under the GPL, or to cease distribution of the GPL'ed portion of code. - See more at:

Because this issue is so vital, I'll repeat some of the info here:


Now, as to SCO's public claim that if it released its Linux distribution under the GPL, it did so inadvertently and that if it happened it must have been by an employee who didn't have authorization, I invite you to take a trip back in SCO history.

Here is the SCO page where they list the GPL-licensed elements in their products. Notice that OpenLinux is listed as being released as GPL. This is still listed as of today that way.

You might find their list of press releases from 2000 interesting, just from their titles. Remember that SCO is their now-name; in 2000 they were Caldera. Interestingly, some of the ones that would appear to be most damaging to their claim can't be accessed by Wayback Archive, because of SCO's robot.txt file. For example, one press release on the list is "SCO and Industry Leaders Establish Free Standards Group -- Group Drives Linux Standardization Effort to Support Next Generation of Products and Services in the Linux Market" - May 10, 2000. That press release is listed on Wayback as being here.

Another one you can't get to is "SCO Unveils Linux Strategy -- Linux Products, Services, and Investments Become Pivotal Part of SCO's Server-Based Network Computing Strategy" - February 2, 2000". That is listed as being here, but I can't access it, though Wayback has no trouble accessing any press release listed on the 2000 page that clearly has no relationship to the case. (Note: another try May 23, 2003 worked, or at least resolved to a press release.)

Even on documents that are still available on SCO's site, the GPL is not only mentioned, it is explained and posted. For example, in their OpenLinux Install Documentation, the introduction is titled, Where did Linux come from? and it helpfully explains the GPL thus [Note it's no longer available at 2.3/gsg/introduce.html#914552, where it was in 2003, no doubt due to the name change by SCO as a result of its bankruptcy and subsequent sale of assets; however you can confirm its wording in part here and Wayback has the entire support document here, which I've used now above. The OpenLinux for developers manual is here]:

Linux was started in the early 1990s as a small research project by a Finnish college student named Linus Torvalds. Soon after Linus started his project, hundreds of others began to participate in its development via the Internet. A cooperative venture grew in which thousands of people were working together to create a new operating system. The inclusion of the GNU utilities from the Free Software Foundation (see and the release of Linux under the Gnu General Public License (GPL) furthered the spread of this work. The GPL provides that the source code to the software is released with the product and that no one can restrict access to it. Software licensed under the GPL license is sometimes referred to as Open Source software. With this type of software, anyone can examine and extend the source code, but all such work must be released for public use. Other licenses provide for inclusion of source code with its associated software, but to date the GPL is the most common Open Source license.
It then adds:
Programs that run on Linux don't have to be licensed under the GPL or any other Open Source license. Thousands of commercial applications that you can run on Linux (such as Corel WordPerfect 8 or Oracle 8 Server) use commercial licenses; they are not "GPLed", and do not include source code, thus they cannot be freely distributed. The Linux product you have purchased is built upon the work of thousands of individuals, then assembled and packaged by Caldera Systems, Inc. More complete histories of Linux and the free software and Open Source development communities are available in many of the online and printed resources named at the end of this chapter.
In "About the GNU Tools section in the same guidebook, it says:
The GNU toolchain is a set of compilers and development tools that are the foundation of the Linux development environment and are also supported on many other platforms. These and other handy development tools are available at the website. Built versions of many of these tools are included on the Caldera OpenLinux Workstation, either in the main development system or on the 'contrib' CD.

All source code for GNU tools is available; anyone can download, build, and use them for free. You can also download the current "Top of Tree" and make modifications to the tools that are needed. If you fix a bug or add a significant feature, you should contribute it back to the community, although this is not required if you do not distribute your altered software. If you distribute such work, you are actually required to distribute your source and contribute it back to the owner of the original software. See for more information about participating in this work; always consult with your own legal authorities about your specific rights and obligations for any work you are doing.Several different license types can be used for code that is contributed to the Open Source community. See for an overview of the terms and restrictions of the different licenses.

Note that you are not required to provide the source for an application that is created using the GNU toolchain. You must, however, carefully check the license type of all libraries that are used in the code: libraries that are covered by a GPL can only be used in free software; libraries that are covered by an LGPL can be used in free or proprietary software. The web page provides more information about the terms of the different licenses; when in doubt, consult your legal experts.

Say, that's good advice. How likely is it that they didn't do so themselves, or that they had no knowledge that under the GPL, if you release a product built on it that the whole is released as GPL also? Slim? Or None?

In their guide for developers, they clearly state that Linux is "a UNIX-like operating system" and that Linux and GNU tools are released under the GPL:

The Linux operating system and the GNU toolchain are released under the GNU General Public License (GPL). The GPL provides that the source code to the software must be made available and that no one can restrict access to it. With this type of software, anyone can examine and extend the source code, but all such work must be released for public use. Other licenses provide for the inclusion of source code with its associated software, but GPL is the most common Open Source License.

1.2. What is OpenLinux?

OpenLinux is Caldera's self-hosted source code Linux distribution that conforms to commercial software release procedures. OpenLinux is based on the most current stable open source technologies, but subjected to rigorous testing procedures similar to those used for proprietary operating systems.

On this page, they list SCO contributions to the Community, as they call it. And if you follow the links, you find one page that says they were releasing under the GPL:
Aim Benchmarks --
SCO is making Suites VII and IX of the AIM benchmarks available under the GPL. The Suites are now available to the community via download. The project will also be available on SourceForge soon.
They even say on another page that they made contributions of code to the Linux kernel. Here's a screenshot:

If so, it wouldn't be a surprise if some code in the kernel might look like Unix code owned by SCO. [Note the reference to SMP.] On a page describing "The Linux Support Team" they say that Caldera Open Linux distribution is based on LST Distribution, and that it is distributed under the GPL. They have whole pages devoted to the GPL, in which they accurately explain how it works. For example, here it says:

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.
And on another page, they say:
Printed below is the GNU General Public License (the GPL or copyleft), under which Linux is licensed. It is reproduced here to clear up some of the confusion about Linux's copyright status--Linux is not shareware, and it is not in the public domain. The bulk of the Linux kernel is copyright 1993 by Linus Torvalds, and other software and parts of the kernel are copyrighted by their authors. Thus, Linux is copyrighted, however, you may redistribute it under the terms of the GPL printed below.
Intriguingly, on this page of the Installation Guide, which explains Linux and gives some of its history, it says that Linux is a "UNIX operating system clone", with no AT&T code in it:
What makes Linux so different is that it is a free implementation of UNIX. It was and still is developed cooperatively by a group of volunteers, primarily on the Internet, who exchange code, report bugs, and fix problems in an open-ended environment. Anyone is welcome to join the Linux development effort. All it takes is interest in hacking a free UNIX clone, and some programming know-how. The book in your hands is your tour guide. . . . Linux is a free version of UNIX developed primarily by Linus Torvalds at the University of Helsinki in Finland, with the help of many UNIX programmers and wizards across the Internet. Anyone with enough know-how and gumption can develop and change the system. The Linux kernel uses no code from AT&T or any other proprietary source, and much of the software available for Linux was developed by the GNU project of the Free Software Foundation in Cambridge, Massachusetts, U.S.A. However, programmers from all over the world have contributed to the growing pool of Linux software.
See also SCO's OpenLinux Documentation page.) For any who are confused, this page explains who is who at SCO:
Note: Until 2001, the Santa Cruz Operation (SCO), a UNIX company, and Caldera International (CALD), a Linux company, were two different companies. In 2001, Caldera acquired SCO. Then in 2002 Caldera changed its business name to the SCO Group. However, the corporate name remains Caldera International. Many people still think of the SCO Group's Linux operations as Caldera. In order to make sure that readers would know and realize throughout the article that what is now the SCO Group is also the company once called Caldera, the SCO Group is often referred to as SCO-Caldera in this article.


Now They Are Starting to Look at the GPL? | 0 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
No user comments.
Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )