Slashdot Mirror


SCO Invokes DMCA, Names Headers, Novell Steps In

Sparky writes "We've already heard that SCO have invoked the DMCA via 'letters sent to select Fortune 1000 Linux end users.' The specifics come via a copy of the letter reprinted at LWN.net - they've decided that they own the copyright to about 65 header files contained in Linux - largely errno.h, signal.h and ioctl.h." balloonpup also notes "CNet News has reported that SCO has reported a fourth quarter loss of $1.6 million, owing mostly to hefty legal fees in its war against Linux. SCO said they would have reported $7.4 million in earnings, if not for the $9 million payout to their lawyers. Way to go, SCO!" Many readers also point out a Groklaw article indicating Novell has registered for the copyrights on multiple versions of Unix with the U.S. Copyright Office, so that "both the SCO Group and Novell have registered for UNIX System V copyrights for the same code."

9 of 770 comments (clear)

  1. Even better news from SCO SEC filing by zzabur · · Score: 5, Informative
    Revenue from SCOsource licenses is expected to be minimal in the first quarter as the Company finalizes license agreements with vendors and continues to implement its intellectual property license initiative...

    ...Operating expenses relating to the Company's UNIX business are anticipated to remain flat during fiscal 2004. Expenses associated with SCOsource initiatives are expected to increase in fiscal 2004 as the Company pursues and expands the scope of its legal strategy to enforce and protect its UNIX intellectual property...

    If the above information is correct, SCO revenue in Q1/2004 will be around 15 M$ and net loss could be >5-10 M$. It seems they don't get more money soon, they will be out of business before summer.

    --
    Auferre trucidare rapere falsis nominibus imperium, atque ubi solitudinem faciunt, pacem appellant.
  2. I listened to the call by El_Smack · · Score: 5, Informative

    After seeing the number posted on /., I dialed it up and listened. I have to say that, even though I know what they are doing is messed up, they put some very posive spin on thier situation, albiet that is the purpose of this conference call.
    One of the first questions in the Q and A period was "If I pay the $699, do I have rights to use the source and continue to run Linux?" Darl very neatly sidestepped half the question and answered "Yes, you can continue to run the binary (emphasis mine) within the agreement."

    From that, I take it that if you pay, you can run the kernel, but they won't say you can play with it.

    --


    There are 01 kinds of cars in the world. The General Lee, and everything else.
  3. Re:clue me in.... by Anonymous Coward · · Score: 5, Informative

    SCO is a member of the Open Group and participated in the development of those standards. The FTC has sued Rambus for doing the same thing with JEDEC DRAM standards-- you can't participate in standards development if you're later going to claim ownership of the technologies involved!

  4. Re:clue me in.... by Anonymous Coward · · Score: 5, Informative

    Heres the freebsd version of errno.h.

    #define EPERM 1 /* Operation not permitted */
    #define ENOENT 2 /* No such file or directory */
    #define ESRCH 3 /* No such process */
    #define EINTR 4 /* Interrupted system call */
    #define EIO 5 /* Input/output error */
    #define ENXIO 6 /* Device not configured */
    #define E2BIG 7 /* Argument list too long */

  5. errno.h and signal.h are from POSIX by minkwe · · Score: 5, Informative

    http://www.opengroup.org/onlinepubs/007904975/base defs/errno.h.html#tag_13_10

    Do these guys have any brains at all?

    --
    "Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
  6. Re:Is it enough to change the comments at the top? by Edward+Scissorhands · · Score: 5, Informative

    NO. You cannot slap another license or copyright header on BSD code. I do not know how this rumour got started, but the BSD license is very clear. You must retain the BSD copyright notice in the source code, and, in the case of binary redistribution, you must have the software display the BSD license. If you read the copyright information for MS Windows, for example, either on the Windows installation CD, or, IIRC, at the bottom of the EULA flashed during installation, the BSD copyright notice is there.

    If a Linux kernel programmer took some header files from FreeBSD or 4.4BSD, for example, but removed the BSD copyright notice, that is a violation of the BSD license terms. HOWEVER, that does not mean that SCO was wronged. The only party that could sue for violation of the BSD license is, of course, the Regents of the University of California. AFAIK, but IANAL.

  7. Re:checking out insider holdings by Anonymous Coward · · Score: 5, Informative

    Note: this is to the replies, not to the parent.

    I have a little reality check for you people who think SCO is gonna get shit for this little pump and dump:

    -Our esteemed Commander and Cheif pumped and dumped his little oil company and sold all his shares 2 days before it went bankrupt. The appropriate investigative organizations where politely told to bug off.

    -The above's best friend and cheif campain supporter via donations was the CEO of Enron. Need I say more?

    -Worldcom went bankrupt over executive fraud and now has a cushy contract in Iraq.

    -Microsoft pretty much got let off the hook as soon as someone they "donated" money to got the presidency.

    -Our Vice President is busy riding a gigantic $100,000 a month retirement golden parachute from his company, Halburton, with strangely enough is getting the most, best, and highest paying government contracts.

    What makes you guys think that ANYTHING bad will happen to SCO because of what they are doing? Wake up.

    This is all of course assuming memory serves me correctly.

  8. actual link by gumbi+west · · Score: 5, Informative

    The parent link is not correct. But This is

  9. Re:clue me in.... by gonar · · Score: 5, Informative

    if you read page 33 (section 2.4) and later of the POSIX 1996 standard, all those comment strings are direct quotes from the description in the standard.

    examples:
    (p33):
    [E2BIG] Arg list too long
    The sum of the number of bytes used by....
    (p36):
    [EPERM] Operation not permitted
    An attempt was made to...

    --
    The difference between Theory and Practice is greater in Practice than in Theory.