Slashdot Mirror


Why Does SCO Focus On A Minix-to-Linux Link?

ansak writes "In the latest scoop from Groklaw, Groklaw user talks_to_birds pointed out an error in SCO's version of the famous Levenez Unix Timeline. The important error is the green dotted line which shows Minix to be a derivative of Unix. If this were accepted, and if Linux was shown to be a derivative of Minix, then SCO's lawsuits would be more likely to have merit. As it turned out, even MS called Samizdat unhelpful, but at least now there may be a plausible reason why someone would try to make the link between Minix and Linux in the first place."

13 of 227 comments (clear)

  1. Long live geeks by Anonymous Coward · · Score: 5, Insightful

    One can't help but feel a warm fuzzy sense of nostalgia looking back over the history of Unix, even if a fair number of us geeks here are younger than Unix (er, UNICS) itself.

    UNICS was released nearly 40 years ago...and it's legacy still lives on. It'll take more than the likes of SCO (and a dotted green line) to tear down the Open-Source community. Long live geeks.

    1. Re:Long live geeks by Further82 · · Score: 5, Insightful

      Unix itself is not open source, its more like a specification for an OS, but there are plenty of unix OS's that are not open source and plenty that dont fall under SCO's attack plan. So even if SCO did manage to win it would not destroy UNIX or the open source community (freeBSD comes to mind as a unix OS thats open source and SCO is not targeting, yet...)

    2. Re:Long live geeks by RealSurreal · · Score: 4, Insightful

      Personally I get a warm feeling every time the geeks at Groklaw find another piece of evidence that sticks it to SCO. They're alpha geeks. All hail PJ!

  2. It doen't matter. by theglassishalf · · Score: 4, Insightful

    This enitre issue is moot. SCO distributed copies of linux under the GPL. Thus, if they owned the code, they GPLed it. End of story. It's silly to talk about it. They have already released their copyright. That is the final, and only important issue.

    Arrg!

    -Daniel

    1. Re:It doen't matter. by russotto · · Score: 4, Insightful

      That would only hold if they were aware of the supposed violation at the time they distributed the GPLed code in the first place. They claim that they weren't, and that once they were, contractural obligations prevented them from ceasing to distribute the code. (hard to swallow, but it's a story)

  3. Re:It does matter. by Pharmboy · · Score: 4, Insightful

    They have already released their copyright.

    They can't release what they don't own. Since it appears that Novell owns the copyrights, SCO may be elligible for a lawsuit for unlawful disclosure of copyrighted material to the public. This is yet another can of worms, and we would have to hope that since Novell just bought SuSe (with the help of IBM) that this would not cause other problems with code SCO contributed before it became evil.

    --
    Tequila: It's not just for breakfast anymore!
  4. The Diagram Is Not Measuring Source Dependancy by femto · · Score: 4, Insightful
    From the notes accompanying the diagram:
    Note 1 : an arrow indicates an inheritance like a compatibility, it is not only a matter of source code.

    Emphasis is not mine.

    Thus is, an arrow does not imply that Linux's source code is derived from Minix. It only implies that, in some way, the functionality may be compatible with Minix. Source code is not the only criteria for an arrow.

  5. Minux had no unix code by Billly+Gates · · Score: 4, Insightful

    Try suing the BSD distros instead?

    I read in the Linux journal a few years ago that Minux was formed because AT&T wanted to charge $30,000 per cpu for sysV!

    Talk about extortion!

    Minux was formed as a result but was never updated when Bell labs lowered the price and allowed other people to make versions of Unix like Sun and SGI.

    Unless I am wrong?

    Minix became outdated after Unix went down in price and instead became used in the academia environment to teach students how an OS works. It never really was finished and the internet really did not exist like today without a WWW. Mainly just a few newsgroup and a tiny number of FTP sites which made working on Minix difficult.

    BSD on the other hand has plenty of more merit.

    It is a direction descendant of SysIII with some bits of SysV unixware code added in.

    All the offending code has been removed today but FreeBSD 1.x and early builds of NetBSD had the Unix in it. THis is why FreeBSD compatiblity only goes back to 2.x and not the 1.x series based on NET/2.

    They are a descendant of SysIII from the late 70's since this was used for early BSD development.

    Since the deal was sealed we dont really know what happened or what the terms were with the current BSD's. IBM wants to find out.

    Someone please feel free to correct me if I am wrong since I may be ingorant in this subject area. I want to know.

  6. Remember it's pump and dump by EmbeddedJanitor · · Score: 4, Insightful

    The whole point is not to make legal sense but to keep enough bafflement in there to confuse the "investors" and keep them hoping that there is still some reason why SCO stock should not be printed on toilet paper.

    --
    Engineering is the art of compromise.
  7. Too late. by mcc · · Score: 4, Insightful

    They may not have been aware of the violation at the time they initially distributed the GPLed code. In that case they get to hide behind this "doctrine of mutual mistake" or whatever it's called.

    However, they certainly were aware of the violation at the time they filed their lawsuit against IBM. And they knowingly and consciously continued to distribute Linux as a product for some time, and from their website for at least eight months, after this. Any protections they might have potentially had they simply threw away by doing this.

  8. anything prior to 1991 by kardar · · Score: 4, Insightful

    Anything prior to 1991 is not Linux, actually.

    I guess it really depends on what you call a Unix timeline, and what you call SCO intellectual property. Of course it wasn't their intellectual property at the time, but it is now since they changed the contracts on everyone. IBM didn't think that they could change the contracts, and see what happened.

    They sued Daimler Chrysler for not giving them the serial numbers of processors that used to run UNICOS 1.0 or something similar (UNICOS 1.0 apparently always shipped with source)- for Cray supercomputers that vary in processing power from approximately 0.25 gigaflops to 1 gigaflop. No one keeps museum pieces that old around, there is no point in doing so, especially when the point of having those computers in the first place was for their supercomputing abilities.

    It's not a Unix timeline if they use it like that; they are basically saying that "Linux" has its "roots" in stuff prior to 1991, but that "SCO Linux", whatever that is supposed to mean, is anything from 1991 forward.

    The whole point is this: whatever it is that SCO are doing, they are doing things that will more than likely fail. Expecting an organization to keep records of a multi-million dollar supercomputer from the mid-eighties that has approximately 1/60th the floating-point processing power of a single-processor G5 at 2.0 Ghz and the equivalent of 64 megs of ram is a little bit on the funny side, I seriously doubt that any organization would have the floor space to keep a computer like that around just for the sake of licensing purposes. How many of us wrote legal documents to Microsoft cancelling our EULAs when we stopped using Windows 3.0, or say, for instance, how many universities wrote documents to Sun Microsystems every time they retired an IPX or a Sparcstation 1+ or perhaps something even older than that? It's just so you can say "We are suing this prominent company for something that, when you look more closely at it, is never going to fly, but we realize that most people won't look at it that closely or understand it that thoroughly, so it will, in the end, have the desired effect.

    Anything prior to approximately 1991 is not Linux, so again, it's not relevant.

    It does explain what \\\\{_hybrid-source_\\\\}, is though, - \\\\{_hybrid-source_\\\\} would be Linux (post-1991).

    Anything prior to that is not Linux, so it's not \\\\{_hybrid-source_\\\\}.

    SCO is basically saying that because they distributed Linux at some point under the GPL, and because the GPL is not valid in their opinion, that because they contributed to it, and because they hold some sort of UNIX rights, that they own Linux. That's really what they are saying, it has nothing to do with Minix, that's just a coincidence.

    Of course, they won't get away with it. They know that, the lawyers know that, we know that. The real question is WHY are they doing it? That's the question. The answer to that question is known by those who need to know.

  9. Minux Linux SCO by bayerwerke · · Score: 4, Insightful

    SCO simply doesn't understand the difference between a timeline and a family tree.

  10. Re:Long live FreeBSD by ross.w · · Score: 4, Insightful

    Also remember that Microsoft and Adti have no problem with *BSD because the licence lets them use the code in commercial software without contributing anything. It's GPL software they have a problem with, not Linux per se. Ken Brown practically said as much himself.

    THerefore I think they realise that to go after *BSD is to kill the goose that's laid them plenty of golden eggs.

    --
    If my call is important, why am I talking to a recording?