Slashdot Mirror


USL vs BSDI Documents

Dibyendu Majumdar writes "Dennis Ritchie has posted some court papers from the lawsuit by USL against BSDI about UNIX intellectual property. Some of the SCO claims, such as identical comments in the code, etc. also occur in the claims made by USL. Interesting read in the context of SCO vs IBM case."

13 of 178 comments (clear)

  1. Re:Ummm... by Anonymous Coward · · Score: 1, Informative

    IANAL, but is USL SOL if SCO says BFD about IBM's IP?

    Ahem..."I Am Not A Lawyer" but is USL "Shit Out of Luck" if SCO says "Big Fucking Deal" about IBM's "Intellectual Property".

    P.S. Google "acronym lookup"

  2. Not the same SCO by Anonymous Coward · · Score: 1, Informative

    I think it's time you realise that today's SCO is not the same SCO of 10 years ago.

    Today's SCO is just Caldera with a different name. That bold portion does not refer to the modern SCO.

    Please take note of this in the future.

    1. Re:Not the same SCO by Anonymous Coward · · Score: 3, Informative

      Not the same SCO, but it's pretty much the same SCO UNIX. (Meaning OpenServer/XENIX, not the UnixWare that the lawsuit revolves around.)

      BTW, Linux also has a "SCO binary emulation mode" called iBCS or (confusingly) LinuxABI.

  3. Re:So like some folks are saying... by ViVeLaMe · · Score: 2, Informative

    BSDI's product was far from "free as in beer". As of 3 years ago, BSD-OS Internet Server sold at 999$ apiece.
    On a side note, both SCO & USL are US companies, so they would love to charge 0.92 USD, not 1 Euro a glass.

    --
    i had a sig, once..
  4. Re:SCO owns C++ by Anonymous Coward · · Score: 5, Informative

    Bzzt, sorry. C++ is an ANSI standard, and ANSI have some pretty tough rules regarding standards submissions. SCO might "own" C++, but they don't own the C++ ANSI standard.

  5. Re:When will someone countersue SCO? by molarmass192 · · Score: 2, Informative

    I think it would have to be launched by the copyright owner of the code in question. The only problem is that we don't have the SCO code to examine and determine who the copyright owner is. To get the SCO code, it would most likely have to be subpoenaed and then the examiners would be faced with the NDA vs. tainting conundrum.

    --

    Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
  6. Re:SCO owns C++ by Drathos · · Score: 3, Informative

    Um.. Read the post again. It's not a MozillaZine interview, it's a MozillaQuest "interview". MozillaQuest has a long history of BS, so take everything you read there with a gigantic grain of salt.. Why hasn't SCO's claim to C++ been reported elsewhere since March 4 when this was posted?

    Personally, I think that a claim to C++ would have a much wider impact than a claim to SCO code being put into Linux, were it true. Most UNIX/Linux code is still written in C, but the primary language in the Windows world is C++. (well.. MS C++)

    --
    End of line..
  7. They might own Cfront by reynaert · · Score: 4, Informative

    He's probably talking about Cfront. Never expect a suit to know the difference between a standard and an implementation :)

    Cfront was the first C++ implementation. It worked by translating C++ code to C (in fact, it started out as a simple preprocessor), and as a result it has all kinds of problems with fancier C++ constructs, such as exceptions, STL, and inline functions. According to Mozilla's portability guidelines, the SCO and HP C++ compilers are still based on it.

  8. SCO own everything? by hobsonchoice · · Score: 2, Informative

    I think, maybe SCO don't care what happened with BSD.

    Perhaps I am totally misunderstanding their comments but I get the impression SCO seems to think they own C++ programming languages anyway.

    As to this case, SCO now allege that IBM's support for Linux is killing Unix, but not too long ago, SCO discussed Unix's feature in their SEC filings.

    Meanwhile, definitely worth checking out, there's a new S-3 filing by SCO

  9. Re:Skousen K Fred options by hobsonchoice · · Score: 2, Informative

    I'm no expert on these types of documents, so could be wrong in understanding it, but:

    I'm pretty sure that is a stock option - he has not bought any yet.

    Instead he has been granted the right to buy 45000 shares at $10.25 on 6/24/2004. As he is a brand new director, this is presumably part of his compensation package.

    If SCO stock is worth more than $10.25 when the option vests, he makes money

    If SCO stock is worth less than $10.25, the option is basically useless

    I think the same general rules would apply if SCO is bought out.

    I am not sure whether he retains the option if he leaves the company before the June 2004 date.

    Personally, I don't think he got a great deal. If I were Skousen, I would have asked for 0.001 options vesting immediately (or in months not a year).

  10. Re:Relevant Details by bovinewasteproduct · · Score: 2, Informative

    BSDI agreed to substitute a port of the University of California's in a release which became known as 4.4 BSD(Lite) for BSD/386.

    Just as a side note, BSDI WAS based on 4.4BSD-Lite. As was 386BSD (which birthed both FreeBSD and NetBSD). After the settlement, BSDI, FreeBSD and NetBSD all restarted development using 4.4BSD-Lite2 per the agreement. For FreeBSD this was the dividing line between the 1.X and 2.X series.

    With the advent of the release of 32V, people could once again distribute FreeBSD 1.X (why, I don't know!)

    BWP

  11. A different precedent from 1994? by blyon3 · · Score: 3, Informative

    In November, 1994 I was a plaintiff's expert witness in the
    case of Automated Securities Clearance(ASC) vs. Securities Application
    Applications (SAI), Inc. We (ASC) contended that SAI had misappropriated
    trade secrets by taking source code of the popular BRASS Nasdaq trading
    system and developing a competing product.

    By examining the source code of the 2 systems, I was able to find
    a very small amount (several hundred lines out of about 500,000) of
    identical code, some with identical comments, formatting, etc.
    However, in our case, we successfully argued that this small amount wasn't
    the extent of the damage, rather it was the dna fingerprint that
    proved that the original BRASS code was used as a "reference" for
    the competing product -- and that the extent of the misappropriation
    was well beyond the actual duplicate lines shown as evidence (especially
    since the identical lines were at a low-level infrastructure layer
    which we argued was necessary for anything else to work...)

    The judge agreed -- imposing an injunction on SAI, and as punitive
    damages imposing an additional injunction .... essentially putting
    SAI out of business. The case isn't 100% relevant given some pretty
    bad conduct of the SAI folks (ex-ASC employees) and the judge's finding
    that they had been "disingenuous" on the stand, but it does provide some
    precendent for small amounts of code being used to 'prove' a larger
    infringement.

    In particular, the judge found that identical comments do have value --
    representing 'trial and error', evolution, or labor that went into the
    original and that was used to advantage by the copier. This holds
    true even for copied 'dead code' that is never even executed.

    IANAL, but those interested should consult the records of the
    Superior Court of NJ, Chancery Division, Hudson County, Docket # C-28-94.

    In a strange coincidence, the lawyers for the defendant (SAI) were
    "Crummy, Del Deo, Dolan...." -- the same firm that was on the other side
    for the USL vs. BSDI case (I just noticed from Dennis Ritchie's links...)
    ~

    1. Re:A different precedent from 1994? by blyon3 · · Score: 2, Informative


      The key differences here are:

      1) The product was a set of application programs, albeit a fairly complex one, instead of an operating system with known public interfaces, include-files, etc.

      2) The company (ASC) did convince the judge that it made all reasonable efforts to protect it's trade secrets by keeping the source code under pretty tight control. In the UNIX case, large amounts of the code were available/known to the public, so it seems unclear if any trade-secret protection could be claimed.

      It would have been absolutely OK if SAI had "derived" a new product based only on it's knowledge of the functionality or public interfaces of BRASS. Instead, they actually took a copy of the source code and used parts of it in their derivation. This is what made it actionable... IMO, there's nothing wrong with reverse engineering a product... So, if Linux/BSD/whatever all use either new source code, or copies of publicly available (non-copyrighted, non-trade-secret) source code, then there shouldn't be any issue.