Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
User Journal

Journal Snags's Journal: Problems with SCO IP License for Linux

Here is a list of problems I have with the SCO IP License for Linux (SIPLL). I'll update this as I get angrier.
  1. It's vaporware. There are lots of press releases and documents about the license, but no actual description of what you're buying. I.e. what are the terms? What do you have to agree to? The only way to buy it is to call SCO at 800-726-8649. Hey, SCO, if you want me to even consider buying a license, post the EULA! I'm not gonna shell out money when I can't see what I'm buying.
  2. It's leeching. There have been *many* hours of effort put into Linux other than what SCO claims. Why do they get the money?
  3. It's against the GPL. SCO themselves have distributed Linux after they were well aware that their (claimed) IP was included in the kernel. If they weren't willing to distribute it under those terms, they shouldn't have.
  4. The SIPLL requires activation. Huh? Does this mean that there's going to be some extra software installed on my computer that won't function without calling SCO? I thought a license is a legal agreement, i.e. information.
  5. It's extortion. The only purpose for buying a license is to keep SCO from suing you. But there's no proof that they'll even win. It's just the threat of the lawsuit that they're using to try to sell the licenses.
  6. It's binary-only. Need to recompile the kernel? Tough. You're only allowed to use their IP in binary form.
  7. No modifications allowed. Under their license, you can't modify the Linux kernel. Need something custom? Here's their advice:

    Consider migrating from an in house customized version of Linux to a shrink wrap, off the shelf version of Linux or to an alternative operating system. If you are unable to migrate, consider outsourcing the development of the customized Linux distribution.

    So basically, you should hire someone who's willing to violate SCO IP to do the work. Doesn't that constitute contributory infringement?

    Technically, they can only restrict you from modifying their part. However, they won't identify what that is, so you basically have to assume that any modifications you make might violate SCO IP and aren't legal.

  8. It applies to embedded systems. I might not even know that the device I've bought contains Linux. And I'm supposed to pay them $32? Their claimed IP seems more applicable to large scale systems than small embedded ones, so I doubt that it's even included in the small kernels used in these systems.
  9. It costs $500 to have an SSH server. This I don't understand. So long as I'm just running a desktop machine, it's $199. But as soon as I have some kind of server process running, like sshd, it's a server and costs $699. That's a lot of money to just be running a program that SCO had nothing to do with (and doesn't claim otherwise).
  10. Distributing Linux is not allowed. Yep, you heard it. Red Hat is violating SCO IP. Not only that, but SCO isn't going to offer any license to cure this. Of course, this is SCO's best source of revenue, being as "they have no real products" (unproven quote going around the net). So I doubt SCO will do anything to shut down this free revenue stream.

That's all I have time to write down now. Leave comments if you think I should add things to the list. -- Snags

This discussion has been archived. No new comments can be posted.

Problems with SCO IP License for Linux

Comments Filter:

Ya'll hear about the geometer who went to the beach to catch some rays and became a tangent ?

Working...