Slashdot Mirror


OSI vs SCO

the jackol writes "As expected, the OSI's just given the SCO vs IBM case a bite with this position paper. "SCO has never owned the UNIX trademark. IBM neither requested nor required SCO's permission to call their AIX offering a Unix. That decision lies not with the accidental owner of the historical Bell Labs source code, but with the Open Group.""

5 of 551 comments (clear)

  1. Re:GPL the best bet by brlewis · · Score: 4, Informative

    I like the GPL, but please note that BSD or any other free-software license would have the same result in this case. Any license they grant to the public precludes trade secret violation, and copyright violation is limited to breach of the license.

  2. Re:Confused by Platinum+Dragon · · Score: 4, Informative

    Probably because the kernel itself has no direct relation to BSD-derived or USL-derived kernels, many of the tools are GNU (Gnu's Not Unix, remember?:) rewrites of basic Unix programs, and the BSD-derived software kind of found its way into various distributions over time since they worked just fine, thank you. I may be wrong, but I think even parts of the kernel can be traced to free BSD implementations alongside the homemade spaghetti. A hypothetical "standard" Linux installation is a mishmash of various codebases that developed outside of closed-source Unixen.

    Defining Linux is notoriously tricky, since some people primarily rely on kernel heritage, while others try to build a definition based on the collection of software considered part of the "standard" package. This is complicated by various distributions that may or may not use the same pieces of software for similar tasks. The basics may be all GNU/BSD, but once you get beyond that, things can get ugly fast.

    Someone making a chart would therefore likely either decide to stuff Linux off to one side on the justification that the kernel has no direct heritage, or draw a crapload of lines to other Unixen and codebases to really nail down every last relation.

    --

    Someday, you're going to die. Get over it.
  3. Re:GPL the best bet by ecki · · Score: 4, Informative

    There are four separate issues here: Trade secrets, NDAs, patents and copyrights. Trade secrets are nixed by revealing the source code, NDAs possibly also, copyright and patents however aren't.

    If I distribute my application in source code form, I still have all copyrights associated with it. The GPL grants others some additional rights to redistribute which they otherwise wouldn't have, even if they had the source code.

  4. Major Nitpick by Mistah+Blue · · Score: 4, Informative

    VERITAS File System (VxFS) and VERITAS Volume Manager (VxVM) are owned by VERITAS Software Corporation. They are not part of the Bell Labs code. By reading Eric's article one could infer (I did) that he was implying this code is part of the Bell Labs code.

    Disclaimer: I work for VERITAS Software Corporation.

  5. Re:sale of property an "accident"? by Frobnicator · · Score: 4, Informative
    The use of accidental is correct.

    As you pointed out, SCO/Caldera did not have any outstanding claims to the source, so they had no integral or premediated claims to the source. The authors could have said 'adventitious' instead.

    Your description of objects being bought and sold actually demonstrates how accidental or adventitious ownership works. If I bought a car, I had no previous ownership-interest in it; I'd be doing it out of legal chance, as accidental ownership -- I just bought the car because I could.

    A company or person who built the car could say that they have some interest (may or may not be ownership) in the thing, and therefore have some intrinsic reason to buy it. Their ownership would not be accidental. They bought the car because they already had something at stake in the value of the it, perhaps as a demonstration of their workmanship.

    This unresolved conflict is now coming to a head. I think any reasonable person can see which side the courts are likely to come down on. My hope is that IBM will settle by buying Unix into the public domain or otherwise freeing the source, but if that's not what happens, then SCO may very well succeed in enforcing its property rights, "accidental" as they may be.
    Actually, the fact that SCO/Caldera never obtained *ALL* the rights from *ALL* the licences is one of the main points of the article. They make this clear several times by showing different systems that were licenced and SCO has no right to, and systems that SCO released to the public both freely and under the GPL. A second is that SCO/Caldera profited for several years from the actions, including distributing infringing code under the GNU licence and contributing to the code in a public work, but are only now attempting to assert some rights against another company. A third point is that SCO/Caldera probably does not have those rights that it is trying to assert, through the earlier settlement and licence issues, mutally accepted 'theft' of code [which isn't theft if both parties were aware of it and took no official actions], and other history.

    I think that in spite of some slightly incorrect dates, omitting the free/open arguments and the GNU/Linux OS vs. the Linux kernel, and the inclusion of anecdotes like 'But that emperor has no clothes', the authors have a very clear and solid attack against several aspects of the suit

    frob.

    --
    //TODO: Think of witty sig statement