Slashdot Mirror


IBM Denies Charges of Unix Theft

ahooton writes "C|net is reporting that SCO has filed a lawsuit accusing IBM of theft of it's Unix intellectual property. SCO alleges this occurred because IBM released portions of the Unix system, owned by SCO, in to Linux." While the suit is nothing new, IBM's retort is. IBM asserts it is innocent of any charges of wrongdoing. Additionally, IBM is accusing SCO of trying to stifle Linux development through the use of the courts.

400 comments

  1. Re:deja vu? by Anonymous Coward · · Score: 0

    no that was the "evil bit" story

  2. REAL Purpose by kkirk007 · · Score: 5, Insightful

    I know it's been said before, but...
    SCO's real purpose behind this lawsuit is not to get money, but to publicize itself in hopes of finding a larger company to buy them.
    SCO's business hasn't been so great lately, and...they're just a little desperate at this point.

    1. Re:REAL Purpose by Anonymous Coward · · Score: 3, Insightful

      I think the bottom of the CNET page explains your point best

      Related Quotes [stock quotes]

      Intl Bus. Machine
      85.89

      Caldera Intl
      3.69

    2. Re:REAL Purpose by BrokenHalo · · Score: 4, Insightful
      SCO's business hasn't been so great lately

      Maybe it would be if they put the same effort into producing a worthwhile actual product that they waste on fishing trips in the courts.

    3. Re:REAL Purpose by 0x0d0a · · Score: 4, Informative

      Doesn't really mean anything. You could have a company with each share not valued as much but with many shares issued, or with few shares but each share valued highly.

      Market capitalization is much more useful:

      IBM:
      Market Capitalization $147.9B

      Caldera International:
      Market Capitalization $40.2M

      (Yahoo Quotes)

    4. Re:REAL Purpose by Anonymous Coward · · Score: 2, Funny

      Nah, this whole thing is an evil plot by IBM to get grassroots mindshare: they actually paid SCO to launch an idiotic lawsuit where Big Blue gets to be the knight in shining armour, defending the holy cause of Open Source and all that.

      Now where did I put my tin foil hat? [Actually I think the parent was pretty much right and to the point but I couldn't help myself, what with the hangover...]

    5. Re:REAL Purpose by cenonce · · Score: 3, Funny

      SCO's real purpose behind this lawsuit is not to get money, but to publicize itself in hopes of finding a larger company to buy them.

      So, in other words, it is in fact to get more money!

      -A

    6. Re:REAL Purpose by Anonymous Coward · · Score: 0

      I went to the recent linux conference in Toronto and SCO had a booth, and even seemed like a real company. I was not fooled however, but I did kind of linger to hopefully witness some flames over SCO sucking so much. Alas, nothing.

      BTW, the conference was pretty empty. Cough, SARS, cough cough.

    7. Re:REAL Purpose by theyman · · Score: 1

      I agree that market cap is more useful for this kind of comparison. However, the point still is made; perhaps even more starkly.:)

      --
      Well, well, well; three holes in the ground...
    8. Re:REAL Purpose by mpsmps · · Score: 4, Insightful

      It would be suicide for IBM to buy them. If they did, every failing tech company would see how SCO made millions out of nothing, and their boards would insist on suing IBM for patent infringement in hope of getting bought out. IBM has to show that companies will regret bringing patent lawsuits against them.

    9. Re:REAL Purpose by martyn+s · · Score: 2, Insightful

      Well, yes, much more starkly. Just as another example:

      Microsoft: 25.94
      Amazon: 28.88

      Stock price usually has nothing to do with it.

    10. Re:REAL Purpose by Anonymous Coward · · Score: 0

      The REAL purpose has nothing to do with SCO.
      Microsoft/Bill has paid SCO to slow the adoption of Linux in the business server market by casting FUD on the legality of Linux.
      SCO is irrelavent as a business. Their patents make them useful as a tool against business Linux.

      Have you guys seen this?

      services for Unix

    11. Re:REAL Purpose by Tipton51 · · Score: 1

      So, if IBM buys out SCO, do they also purchase this lawsuit?
      Can they then extend the lawsuit against SUN, HP, et. al.?

    12. Re:REAL Purpose by catalina · · Score: 1

      Maybe it would be if they put the same effort into producing a worthwhile actual product that they waste on fishing trips in the courts.

      Well, I've only known one lawyer who could write decent code.......

    13. Re:REAL Purpose by Spunk · · Score: 1

      Correct.

      However, when the price is exceptionally low (say under $5) that is often a bad sign.

    14. Re:REAL Purpose by Kazoo+the+Clown · · Score: 1

      Seems to me, SCO is trying to make themselves look more attractive to Microsoft.

    15. Re:REAL Purpose by Anonymous Coward · · Score: 0

      Ohh they are goinf to get $$$ all Rigth Behind a Closed door in a basement room of 1 Microsoft Drive in Redmond.
      Sneaky Bill and Steve Very Sneaky

    16. Re:REAL Purpose by cshark · · Score: 1

      I propose that we all chip in a couple (between $2 and $5) dollars and buy sco. We as a community can afford it. And then, we would be done with this. Who knows how long this will continue if we don't?

      --

      This signature has Super Cow Powers

  3. Microsoft will be next. by Omni+Magnus · · Score: 2, Funny

    I am just waiting for Microsoft to be sued for stealing other people's code.

    1. Re:Microsoft will be next. by Anonymous Coward · · Score: 1, Interesting

      Been there, done that. Just see the stac suit against Microsoft for misappropriating their drive compression code, among others...

    2. Re:Microsoft will be next. by Anonymous Coward · · Score: 0

      Yeah, like that anti trust movie

    3. Re:Microsoft will be next. by Anonymous Coward · · Score: 1, Interesting

      Stac was actually a software patent, you know, the thing slashbots rave against endlessly.

      A better example would be QuickTime code that ended up in Windows media which lead to a large public settlement.

    4. Re:Microsoft will be next. by Anonymous Coward · · Score: 0

      Speaking of theft, maybe then we'll sue people distributing GPLed libraries.

    5. Re:Microsoft will be next. by argent · · Score: 1

      Pity that OpenBSD took out the acknowledgement clause in their license, or they'd be able to go after Microsoft for not advertising that Windows Services for UNIX uses software developed by the Regents of the University of California.

      Of course the fact that Microsoft's also shipping the "evil, viral" GCC in that same package should be bigger news. :)

    6. Re:Microsoft will be next. by Anonymous Coward · · Score: 0

      while on the toic of fishing trips why not go after MS for using AT&T devel methods and practices, (not necessarily code) MS did do Xenix, MS did have a license with AT&T.

    7. Re:Microsoft will be next. by BigDish · · Score: 1

      As of windows 2000 at least, the readme files on the CD did include that aknoledgement.

    8. Re:Microsoft will be next. by Anonymous Coward · · Score: 0

      Too late... They even lost in court... Never even slowed them down.

  4. Released or reimplemented? by Max+Romantschuk · · Score: 4, Insightful

    SCO alleges this occurred because IBM released portions of the Unix system, owned by SCO, in to Linux.

    I've understood that they've reimplemented some technology in Linux, but have they really just taken the existing pieces and put them into Linux? I doubt it.

    Would someone care to shed some light on the subject?

    --
    .: Max Romantschuk :: http://max.romantschuk.fi/
    1. Re:Released or reimplemented? by tankdilla · · Score: 2, Interesting

      I guess SCO considers those existing pieces to be trade secrets.

      --

      -Look lively. LOOK LIVELY!!! --Mr. Shmallow

    2. Re:Released or reimplemented? by inaeldi · · Score: 1

      *pats you on the head and gives you a cookie*

    3. Re:Released or reimplemented? by Anonymous Coward · · Score: 5, Informative

      While IBM has incorporated some of their code into Linux, none if it has been from SCO.

      IBM's operating system, AIX, has some code from SysV, for which SCO owns rights, but the code they've ported to Linux (such as JFS) are property of IBM.

      SCO is probably trying to muddy the issues - because AIX contains both code that has been shared with Linux and code that SCO owns rights to.

      However, considering that SCO has never specifically pointed out what parts of IBM's contributions to Linux supposedly violate their agreements, they have zero credibility.

    4. Re:Released or reimplemented? by Citizen+of+Earth · · Score: 2, Informative

      SCO accuses IBM of giving away SCO property that SCO never had in the first place. See ESR.

    5. Re:Released or reimplemented? by RatFink100 · · Score: 0

      I believe that they are alleging patent infringment i.e. not that they directly copied code, but they used techniques covered by SCOs patents.

      Of course if you want to play the patents game, IBM own one heck of a large set of patents...

    6. Re:Released or reimplemented? by Anonymous Coward · · Score: 1

      Eric Raymond gives an excellent in-depth analysis of the suit in opensource.org

      Some counter points:

      1) SCO claims ownership of code that was decided to be created by FreeBSD. There was a court decision in the 90s where SCO had to admit that it copied more of FreeBSD's code than FreeBSD copied from it. SCO initiated the lawsuit, and both sides settled. Since then FreeBSD has removed all the questionable code.

      2) SCO claims theft of code in instances where its own employees contributed to the Linux kernel when it was known as Caldera.

      3) SCO claims that Linux would have never reached certain milestones without IBM's help, but the milestones they claim didn't come from IBM's involvement with Linux.

      4) SCO claims theft of features that SCO doesn't have capability. For example, SCO cannot be run on more than 4 processors today, but as of 2000, Linux can run up to 32 processors. Yet SCO claims that this was stolen from them.

      5) SCO misrepresents IBM's role as a major and key factor in Linux development, but in truth IBM came late to the game in late 90s. By then Linux had acquired many features and capabilties that made it a great OS (Some of these SCO doesn't have). Even if IBM stole all the code that they contributed to the Linux kernel, estimates are that this is about 0.4% of the current kernel.

    7. Re:Released or reimplemented? by 0x0d0a · · Score: 1

      They haven't even listed a *technology* that they didn't like being reimplemented. They're just complaining that Linux couldn't possibly scale to enterprise-class use so quickly without stealing their code. It's a pretty inane lawsuit.

    8. Re:Released or reimplemented? by David+Gould · · Score: 1


      I believe that they are alleging patent infringment

      Maybe your information sources are more accurate than CNet's, but the article very definitely says "trade secrets", and doesn't once mention "patents", which are almost the exact opposite type of IP.

      --
      David Gould
      main(i){putchar(340056100>>(i-1)*5&31|!!(i<6)<< 6)&&main(++i);}
    9. Re:Released or reimplemented? by mark-t · · Score: 2
      So if they are trade secrets, then SCO must prove that they were misappropriated. It is not against the law for one person to independantly discover what happens to be another person's trade secret.

      The only protection you can have from that is a patent, and SCO isn't claiming patent rights.

    10. Re:Released or reimplemented? by 4of12 · · Score: 2, Funny

      Absolutely.

      SCO has a much stronger case than most people realize. The proceedings will take IBM and the rest of the open source community completely by storm.

      To wit, when their lawyers reveal specific lines of code from the linux kernel that are absolutely identical to what is in the SCO code base, a jaw-dropping silence will overtake the courtroom.

      Your honor, may it please the bench to observe Exhibit A:

      for(;;) {
      and there will be some additional fearsome evidence where loop variable names were changed from i to j.

      It's little wonder that the lawyers from IBM are so nervous.

      --
      "Provided by the management for your protection."
    11. Re:Released or reimplemented? by michael_cain · · Score: 1
      SCO has also alleged that some of their copyrighted code has been directly incorporated into the Linux source. Direct copying is almost certainly grounds for SCO to collect money, once SCO establishes that the code is indeed theirs. I can easily imagine that there are places where both SCO and Linux have incorporated code under a BSD-like license, which would make it look identical but would not involve any violation of SCO copyright.

      Of course, no one else is going to see SCO's code until at least the discovery phase of a lawsuit gets under way, so it'll be a while before we have any public facts about this.

    12. Re:Released or reimplemented? by Anonymous Coward · · Score: 0

      So is somebody with good credibility, who is a good persuader, going to testify? This would need to be someone who speaks the language of the judge and jury. Someone who wears a nice shirt, and shaves, and does not come across as a blathering radical. No matter how good ESR's points are, he needs someone to make them, and back them up in a very clearly reasoned manner, in a way that the jury and judge not only understands, but agrees with.

  5. Re:WHY? by Anonymous Coward · · Score: 0, Troll

    Just like Apple and BSD..

  6. What I hope this means by OverlordQ · · Score: 4, Insightful

    What I hope this means, is that IBM will once and for-all put an end to this SCO FUD. Who knows the true reason behind SCO's logic, but whatever it is, we dont need it ;)

    --
    Your hair look like poop, Bob! - Wanker.
    1. Re:What I hope this means by arvindn · · Score: 4, Interesting
      What I hope this means, is that IBM will once and for-all put an end to this SCO FUD.

      There's exactly one way IBM can do that: buy SCO. Sco/Caldera's logic is simple: they are a dying company, and they know it. So they want to make it as nasty as possible. If this gets to court, SCO doesn't have a whit of a chance (which is why they didn't go after the little fish first, BTW.) However, it might be the end of SCO, but it will be very costly in terms of PR for IBM as well. SCO's hope is that IBM will find buying SCO to be the easier way out. That's the best case scenario for them.

      BUT. That would put an end to SCO FUD, but MS FUD will start right thereafter. (See, we've been saying it all along, linux is incapable of innovation, sco was going to prove that in court, but big baddie IBM was afraid of them and bought them out.) So its a lose-lose situation.

    2. Re:What I hope this means by mkldev · · Score: 1
      Nope. There are two ways, IBM could simply pull out a stack of patents and says, "Oh, by the way, you're in violation of them." At that point, SCO either shuts up or IBM's lawyers just bury them like a full latrine.

      --
      120 character sigs suck. Make it 250.
    3. Re:What I hope this means by gad_zuki! · · Score: 3, Interesting

      >BUT. That would put an end to SCO FUD, but MS FUD will start right thereafter.

      Sadly, the MS FUD has already started. In the wonderfully written "Code Red for Open Source" article at Cnet which is fair and balanced (in that Fox News kind of way) Balmer is quoted as saying something to the effect, "See, you dont know who's writing your OSS software." I'm sure that little quote doesn't sit too well with IT managers debating adopting OSS. Certainly, MS's list of crimes is volumes long, but the fear of being sued because the product your using was written by 'shady individuals' as Balmer seems to be suggesting can have a real chilling effect.

      Yeah, it is a lose-lose situation depending on how people interpret what is going on. I think its fairly obvious there's a strong attempt at getting a buy-out here which makes their moral position regarding the supposed theft of IP a bit suspect. I hope others see it this way.

      Its like me going up to the guy who broke into my house and stole my stereo and telling him, "Okay, we'll leave the cops out of this if you take over my payments and buy out my equity. I can't afford this place anymore and I dont want to go bankrupt."

      What really gets me, and I'm not even a linux advocate (i use it when I need a free server), is that SCO is trashing Linux's reputation left and right in its attempt to get bought out. I'm surprised there aren't names, addresses, and phone numbers of the SCO people listed here for harassment a la spam king style.

      A little civil disobedience goes a long way.

    4. Re:What I hope this means by jbolden · · Score: 4, Interesting

      They would still have to go to court. SCO does not intend to survive the lawsuit. The real issue IMHO is whether SCO execs have actually crossed the line into fraud considering how untrue some of the statement in the original were.

      IANAL but it sure sounds like lying under oath to me.

    5. Re:What I hope this means by nathanh · · Score: 3, Funny
      Balmer is quoted as saying something to the effect, "See, you dont know who's writing your OSS software."

      And who is writing Microsoft's software *cough*stacker*cough*? I think Ballmer should stop throwing stones.

    6. Re:What I hope this means by Empty+Sands · · Score: 1

      Of course the reverse holds when IBM eventually either "kick SCO's ass" or "buy them out as its cheaper."

      We can turn around and say: "you can never go wrong buying IBM." If it was just Redhat and Sco, I think things would be a little nasty.

    7. Re:What I hope this means by gillbates · · Score: 2, Interesting
      but the fear of being sued because the product your using was written by 'shady individuals' as Balmer seems to be suggesting can have a real chilling effect.

      I think that the BSA has a much greater chilling effect than OSS. IIRC, no one has ever been sued for using OSS, but Microsoft has already filed lawsuits against schools and other government entities. Open source advocates would do well to remind people of the number of times Microsoft has sued its own customers. Granted, with OSS you might not have a corporation to support your software, but neither will you risk the liability of being sued.

      --
      The society for a thought-free internet welcomes you.
    8. Re:What I hope this means by geoff+lane · · Score: 2, Informative

      Given the turnover within MS, nobody knows who is writing Windows code either!

    9. Re:What I hope this means by mj01nir · · Score: 3, Interesting

      Certainly, MS's list of crimes is volumes long, but the fear of being sued because the product your using was written by 'shady individuals' as Balmer seems to be suggesting can have a real chilling effect.

      As chilling as this?:

      SQL Server developers, "particularly those Microsoft customers who relied on Microsoft's assurances, failed to investigate them thoroughly, and knowingly continued to provide material steps in an Infringing Combination. These infringers, if any, may face treble damages for the entire three and one-half years the case was tied up in the courts. Microsoft is not a law firm. Relying on its advice should not constitute acting in good faith; which is the required defense to treble damages for failure to investigate and honor patents once on notice of their existence."

      Microsoft is hardly lily-white when it comes to providing their customers with unencumbered products. IT decision makers need to know this.

      --
      the no .sig .sig
    10. Re:What I hope this means by jpetts · · Score: 2, Funny

      In the wonderfully written "Code Red for Open Source" article at Cnet

      I honestly interpreted this as meaning that somebody had ported the worm!!!

      --
      Call me old fashioned, but I like a dump to be as memorable as it is devastating - Bender
    11. Re:What I hope this means by dsavitsk · · Score: 3, Informative
      IANAL but it sure sounds like lying under oath to me.

      Under Federal Rule of Civil Procedure 11, if the case is being presented for any improper purpose, such as to harass or to cause unnecessary delay or needless increase in the cost of litigation, SCO can be sanctioned. At this stage, however, no oath has been administered.

    12. Re:What I hope this means by poot_rootbeer · · Score: 1

      [letting this go to court] might be the end of SCO, but it will be very costly in terms of PR for IBM as well.

      How so? Maybe my sense of perspective is skewed from reading too much Slashdot, but it seems like IBM is widely respected and SCO widely reviled in the Linux community as well as the IT community at large.

    13. Re:What I hope this means by jbolden · · Score: 1

      Nice reference they even go further in your link
      the allegations and other factual contentions have evidentiary support or, if specifically so identified, are likely to have evidentiary support after a reasonable opportunity for further investigation or discovery; and

      I think SCO clearly falls beneath this standard. Of course the real question is whether the execs and lawyers can be santioned not just SCO itself since SCO doesn't aim to survive.

    14. Re:What I hope this means by Anonymous Coward · · Score: 0

      And who is writing Microsoft's software *cough*stacker*cough*? I think Ballmer should stop throwing stones.

      That's fine.. If Ballmer is going to throw stones in a glass house, he best get a coorperate surgeon ready, because the house may-well just fall in on him, and cut him up REAL bad... I dont have any sympathy for spineless people out there...He best-well be prepared to live with lots of scars on top of the ones he ALREADY has for WORKING for Micro$oft.

    15. Re:What I hope this means by Anonymous Coward · · Score: 0

      stupid USB keyboard keeps doubling whatever I say :/
      sorry for the typos, coorperate/corperate

    16. Re:What I hope this means by Anonymous Coward · · Score: 0

      corporate :-)

    17. Re:What I hope this means by 0x0d0a · · Score: 1

      IBM has for decades been respected for producing good but expensive products, most of the time. They also tend to take care of their customers reasonably well.

      SCO has a long, rich tradition of being made fun of for their Unix distribution, which, to be blunt, sucked badly.

    18. Re:What I hope this means by iabervon · · Score: 1

      The sensible thing for IBM to do would be to mainly ignore the thing. It's not like they don't have lawyers on staff who are quite capable of beating SCO in their spare time in this case. And IBM does best if SCO either drops the charges or loses the suit, because it proves that Linux is free of the legal mess that UNIX became. This is good for IBM, because they support Linux. Of course, they could buy SCO and get the rights, but the rights are either worthless or bad PR or both.

      If things get out of hand, they could hasten the process by countersuing, but it hasn't gotten to that stage quite yet.

    19. Re:What I hope this means by Anonymous Coward · · Score: 0

      Ahem! *cough*SQL*cough*

    20. Re:What I hope this means by Anonymous Coward · · Score: 0

      something to the effect, "See, you dont know who's writing your OSS software."

      Isn't that funny, don't they contract others to do their programming? I thought a while back there was a big panic over something like this.

      Besides, how dose microsoft know who is writing their software? It seems some shaddy individuals there are puting in lots of exploits and bugs.

  7. If its stolen its stolen! by Anonymous Coward · · Score: 0

    Well, i understand that almost everything that says anything against open source is deemed evil!
    But we'l finally know wat the truth is. CO Group Chief Executive Darl McBride has said that they have strong evidence. If so we'l know it soon.
    But in anycase, since when did stealing become a crime? hello! Microsoft ? Rings a bell??

  8. In other news... by HornyBastard77 · · Score: 0
    ...the RIAA members deny charges of being greedy pigs.

    ...Microsoft denies everything.

    ...I deny being a karma whore.

    Seriously, how is this news? Did anyone expect anything else?

    1. Re:In other news... by Anonymous Coward · · Score: 0

      Did anyone expect anything else?

      yes, yes I did. and I am saddened at not finding anything else. :( [sniff]

  9. I know that there isn't SCO code in Linux because by DanThe1Man · · Score: 5, Funny

    ....LINUX DOSN'T SUCK!!

  10. Well, if there is one GOOD thing I can say... by Tokerat · · Score: 4, Interesting


    ...it's "At Least SCO went after the big guys first."

    There is no RIAA-suing-college-kids style lawsuit here. They went right after someone who could afford to defend themselves, instead of trashing say, SuSe and RedHat.

    On the other hand, it's IBM, who probably even has a patent on human life for christ sakes. Therefore I doubt we'll be seeing much more of SCO, especially if this suit doesn't hold water.

    --
    CAn'T CompreHend SARcaSm?
    1. Re:Well, if there is one GOOD thing I can say... by deadsaijinx* · · Score: 1, Interesting

      i have already pronounced SCO legally dead. of course, there's no such thing as bad publicity, or so they say. I think this kind of publicity is just plain awful. it leaves a vile taste in my mouth, ok, not really,whatever. and i think RHAT can defend itself plenty well ok ? the symbol is RHAT, try the research option to find out more about their finances.

      --
      YOU SUCK BALLS!
    2. Re:Well, if there is one GOOD thing I can say... by yaphadam097 · · Score: 1

      Perhaps they didn't go after SuSE because they are partners along with TurboLinux in the United Linux thingy... and they all want Redhat to join in the worst kind of way. Seriously, IBM represents a big market share in the proprietary Unix space, and that is what SCO is gunning for. If they can get IBM in trouble for contributing to a technology from which they also benefit (Linux) then that is just a bonus.

    3. Re:Well, if there is one GOOD thing I can say... by Anonymous Coward · · Score: 0

      > Perhaps they didn't go after SuSE because they are partners along with TurboLinux in the United Linux thingy [unitedlinux.com].

      Nope. SCO plans to go after SuSE as well (!?!?!?!?!?!!!!?????). More proof of SCO upper management braindeath.

    4. Re:Well, if there is one GOOD thing I can say... by Guppy06 · · Score: 4, Insightful

      "There is no RIAA-suing-college-kids style lawsuit here."

      That's because the RIAA is looking to use fear tactics to shut down competing media delivery forms. SCO is just in it for the money, and it's over at IBM.

    5. Re:Well, if there is one GOOD thing I can say... by Tokerat · · Score: 2, Interesting


      IANAL, but if SCO has established a precident against a small Linux vendor, couldn't they have gone to IBM and said "Look, we have proof and a precident against you. We'll take a check, thanks."?

      --
      CAn'T CompreHend SARcaSm?
    6. Re:Well, if there is one GOOD thing I can say... by Anonymous Coward · · Score: 3, Interesting

      Actually, it's because IBM sells systems with AIX, parts of which are most definitely licensed from SCO. Basically, SCO figured they could hold the threat of withdrawing the Unix license for AIX over IBM's head to force them to roll over (or buy out SCO).

      Either way, SCO is scum.

    7. Re:Well, if there is one GOOD thing I can say... by Anonymous Coward · · Score: 0

      upper management braindeath

      Surely thats redundent? ITYM "upper management."

    8. Re:Well, if there is one GOOD thing I can say... by Anonymous Coward · · Score: 0

      Your sig sucks. Don't invent new words. We have big problems with the existing ones already. Thank you! -God

    9. Re:Well, if there is one GOOD thing I can say... by Knightmare · · Score: 1

      Ok, there is one important flaw in your statement. I don't believe a P2P network like the ones that the RIAA is attacking can be called a "competing media delivery form," unless to you that means "wide open intellectual property theft network." While I will never argue that there are important and good uses for P2P. Kazaa, Gnutella, etc... are mainly used for piracy. And before you say how do you know, thats just not true. Logon to one of said networks and in the case of GNUTella take a look at the queries that come across to you (be sure to ignore the child porn and illegal software requests and the rest will be mp3 traffic). In the case of Kazaa, retrieve a users file list and poke around. I see lots of mp3's waiting to be plucked, but very little information waiting to be freed.

      I don't argue that there needs to be a better way to distribute the music, but change of a distribution method so engrained in our society takes a little time. Hell I am not that old but I still remember going down to the record/cd shop and getting advise from somebody working there on what I should pick up this week based on the stuff I had purchased previously. Going from that to a cold dead CRT that shows you neatly aligned search results with no bias or flair is a bit of culture shock that quite a few are not ready to welcome.

    10. Re:Well, if there is one GOOD thing I can say... by anno1602 · · Score: 1

      They went right after someone who could afford to defend themselves, instead of trashing say, SuSe and RedHat.

      SCO said that after they're done with IBM, they'll sue SuSE and Redhat (German).

    11. Re:Well, if there is one GOOD thing I can say... by salesgeek · · Score: 1

      ...it's "At Least SCO went after the big guys first."

      Because they could only afford one shot at the jackpot. They'll loose just like the guy that comes in, plunks down the entire $100 he's got on the blackjack table hoping to come away with $200. Most of the time they guy's not smart enought to suck down a few comp drinks to take the edge off the impending loss.

      --
      -- $G
    12. Re:Well, if there is one GOOD thing I can say... by no_code_charlie · · Score: 1

      SCO is suing on a contract to which IBM was a party Redhat, etc. were not parties, thus cannot be sued. IBM was/is the *only* target available to SCO. SCO's is essentially claiming breach of nondisclosure/confidentially clauses, possibly misappropriation of trade secret (i.e., unauthorized dissemination). SCO's suit poses no real problem for linux/gnu in general. Any public apprehension to the contrary is merely a FUD effect. Here's the thing about trade secrets: Once they become generally known they cease to be protectable trade secrets. (It is fundamental that trade secret information must be secret.) This principal even applies to widespread disseminations of trade secret information where the dissemination was, in of itself, unlawful. (Although, were unlawful dissemination is not widespread, outcome may be different.)

    13. Re:Well, if there is one GOOD thing I can say... by Anonymous+DWord · · Score: 1

      SCO said that after they're done with IBM, they'll sue SuSE and Redhat

      I love reading that. It's funny every time. Like when the JW's come to your door, and say "The meek shall inherit the Earth," and you laugh demonically and growl "Yeah, what's left of it!"

      --
      "If he thinks he can hide and run from the United States and our allies, he's sorely mistaken." Bush on bin Laden
    14. Re:Well, if there is one GOOD thing I can say... by whitehat · · Score: 1

      To quote the Mash theme song: "Suicide is painless!"

  11. Code Red for Open Source? by Anonymous Coward · · Score: 5, Interesting
    Here's another CNET article about the suit. It makes it clear that SCO is trying to make pure FUD:
    McBride refused to detail which specific code had been copied but said there were several instances--"some of them go back several years, and others are recent"--and said the copying was "not minor." SCO, however, won't publish what it's found.

    "We feel very good about the evidence that is going to show up in court. We will be happy to show the evidence we have at the appropriate time in a court setting," McBride said. "The Linux community would have me publish it now, (so they can have it) laundered by the time we can get to a court hearing. That's not the way we're going to go."

    Next he'll tell us there's weapons of mass destruction in the Linux code and the fact we can't find them just shows how diabolically clever the people who hid them were. Send the UN inspectors!
    1. Re:Code Red for Open Source? by SiliconJesus101 · · Score: 3, Insightful
      "We feel very good about the evidence that is going to show up in court. We will be happy to show the evidence we have at the appropriate time in a court setting," McBride said. "The Linux community would have me publish it now, (so they can have it) laundered by the time we can get to a court hearing. That's not the way we're going to go."

      Unbelievable!! So this guy doesn't even want the issue resolved??? I guess it's true that they are simply trolling for dollars in the form of a quick settlement or buyout.

      As far as I understand it, don't the attorneys on both sides have to share the information they have regarding the lawsuit??

      --

      "The strong will do what they want, the weak will do what they must."
      -Thucydides

    2. Re:Code Red for Open Source? by Anonymous Coward · · Score: 5, Insightful

      This allegation really underscores a primary issue of closed source software - it's not out for public review, and hence, it would be VERY difficult to validate these claims. For all we know, SCO's code is a rip-off of Linux or some prior open-source code that Linux was a beneficiary of. SCO never published their source and there's nothing outside of SCO (or maybe IBM, if there was some kind of agreement) to validate the claims. The trouble is, we can trust neither of those parties to present untainted copies of the relevant code as both could have altered timestamps or copied in code. There's also the fact that some processes in software can just really be done in one optimum way.

      This is a good reason software should not be considered "published", hence copyrightable, unless the source code exists in some human-readable means in some organization outside of the "software publisher" (who truly publishes nothing), a place the courts could seriously look at as proof of the existance.

      A way that might serve as a valid stopgap would be the generation of an MD5 hash of each source file and submitting that to some trusted agency (Library of congress?) for another digital signature and timestamp to be added, proving the date of creation to some legal standard so that these allegations could be backed with proof. We'd know the plaintext was validly signed by the LOC and that it existed at the time alleged to.

    3. Re:Code Red for Open Source? by Anonymous Coward · · Score: 0

      Actually, between the lines, he's saying that those lines of code aren't even essential to Linux, because they could easily be "laundered"...

    4. Re:Code Red for Open Source? by fr0dicus · · Score: 2, Interesting

      Surely they're alleging that IBM must have had access to this source somehow? Whatever the hell they are talking about will be mirrored throughout the world on the Linux side. As far as the code they're claiming they did first, I assume they'll have to prove it with dated documentation, which is pretty difficult to prove/disprove either way. Unless they've got some magical ace up their sleeve I can't see anyone but IBM winning. I always hated SCO anyway.

    5. Re:Code Red for Open Source? by Goonie · · Score: 2, Insightful
      "The Linux community would have me publish it now, (so they can have it) laundered by the time we can get to a court hearing. That's not the way we're going to go."

      Is he arguing the "linux community" is somehow going to make millions of copies of older versions of the kernel source on the various squillions of CD-ROM's out there disppear so SCO can't prove its case? Or is he worried that any piece of code allegedly pinched from UnixWare can have its functionality duplicated so quickly that the arguments about Linux the bicycle are disproven? Either way, it's entirely ludicrous.

      --

      Any sufficiently advanced technology is indistinguishable from a rigged demo
      --Andy Finkel (J. Klass?)
    6. Re:Code Red for Open Source? by Anonymous Coward · · Score: 0

      One comment: you have available distributed binary, but that faked code will bot compile to it. So your arguments are weak.

    7. Re:Code Red for Open Source? by dknj · · Score: 1

      Looks like a rerun of the AT&T lawsuit that threatened BSD. Time for the masses to move to the next worthy operating system

      -dk

    8. Re:Code Red for Open Source? by jdavidb · · Score: 1

      Send the UN inspectors!

      You know full well that's not the way to handle the problem! :)

    9. Re:Code Red for Open Source? by Azureflare · · Score: 1
      Or...The judge could just throw the case out as completely idiotic and have done with it. If you can prove something without evidence in the courts, then what else is the courts but a great debating society?

      IMHO, this case has no place in the legal system, and SCO should be ruled in contempt of court if/when they get there. They have no facts. They have hearsay. They have no case. It'd be like me saying "OOOOH IBM has my propietary code look! they used it and they better pay up, chop chop! No, I can't show it to you! just pay! All your base are belong to us!!!!"

      You get the idea. This is complete lunacy.

    10. Re:Code Red for Open Source? by ebyrob · · Score: 1

      Na, just limit copyright protection to the exact bit-pattern of the binaries released. That way seriously hacked versions or versions derived from the source (however it is aquired) are protected in no way whatsoever by copyright.

      Copyright only protects the "fixed media". It isn't our fault software companies don't bother fixing anything.

  12. serious question by Anonymous Coward · · Score: 1, Interesting

    does having once been a system v developer, with full access to the code, taint you from being a linux kernel developer?

    1. Re:serious question by Anonymous Coward · · Score: 0

      Huh Huh. You said 'taint'.

    2. Re:serious question by Anonymous Coward · · Score: 1, Funny

      Huh Huh. You said 'taint'.

      i can see it now, linus up on stage:

      "Once I added code"
      "Then I deleted code"
      "This tainted code you give me"
      ...

    3. Re:serious question by Unordained · · Score: 1

      depends on the contracts signed. any NDA's? any "what you write is ours forever" clauses? any "you may -not- go and rewrite this from scratch elsewhere, thanks to your exceptional memory" clauses?

      no? then no. have at it. give us a better kernel.

    4. Re:serious question by Anonymous Coward · · Score: 1, Interesting

      No, but you have to make sure you don't implement anything too similar to what you saw.

      First of all, the Linux kernel is not a special case in any way. Whatever restrictions might apply to what you can work on would apply to all proprietary as well as open source systems, whether you do it as a volunteer or as paid work for an employer.

      The clean room approach taken by many corporations is a "just in case we get sued" precaution, so if they do get sued, they don't have to go through the code to prove that none of the developers have "used stuff" from other projects.

      Think about it - if working on a certain type of product tainted you from ever working on similar products again, that would be ridiculous. Developers could never be hired to work on something similar to anything they've done before. Your CV would basically be a list of things you are no longer allowed to do.

      Note that YMMV if you've signed any NDAs beyond your employment contract. Then again, an NDA that says that you're never allowed to work on any other operating system ever again might not even hold up in court.

    5. Re:serious question by Black+Copter+Control · · Score: 1
      depends on the contracts signed. any NDA's?

      It's not the NDAs that taint you, it's having had access to the (proprietary) closed source code. If, subsequent to that, you post something into the Linux kernel that looks suspiciously like something in the Source code you (might have) had access to, then the owner of that source code might be able to sue everybody and their dog for breaching copyright. Even if it turns out to have been a false alarm, we're still talking $50K and 2.5 years of stagnation later.

      Far easier to say "oh, you've had access to SYSV(AIX, MS, etc.) kernel source code?? Sorry -- go contribute to GAIM, or something.

      It's not even that we don't trust you to produce only untainted code -- it's that people don't want to risk having to run a court case every 1-2 years just to prove that they didn't steal the proprietary code.

      --
      OS Software is like love: The best way to make it grow is to give it away.
    6. Re:serious question by senrik · · Score: 1

      ~does having once been a system v developer, with full access to the code, taint you from being a linux kernel developer?

      I would think it depend on your agreement with ATT. I've had several employment contracts that stated that any think that I created while working for company 'X' belonged to that company. Usually it means both the binaries and the source. Frequently it is also backed by a non-compete agreement.

      On the other hand, I can also see a way around it, where if you recreate it based on your memory (not your notes or etc.) on what it does, then it is would technically not be a violation of anything, particularly if you do it after the non-compete agreement period.

      --
      "the difference between myself and a madman is that I am not mad" -Salvadore Dali
  13. Linux: IBM's true universal adapter by Thaidog · · Score: 5, Interesting

    The good thing is that right now you can run linux on IBM's zSeries, AS/400, RISC6000,... all the way down to a PDA. It's no joke to say that there is alot of money about to be made... That's the real reasonb for this suit...

    --

    ||| I still can't believe Parkay's not butter.

  14. Re:I know that there isn't SCO code in Linux becau by Anonymous Coward · · Score: 0

    But its spellchukkker sure does.

  15. Unix code copied into Linux alleged by Anonymous Coward · · Score: 0

    In fact, SCO alleges that "Lines from Unix's source code have been copied into the heart of Linux, sometimes exactly and sometimes in a modified form designed to disguise their origin". Link

    1. Re:Unix code copied into Linux alleged by Tokerat · · Score: 4, Funny


      ...McBride then stated "Clearly you can see places where IBM's source code adds two numbers together, in some instances the same two numers our software would be adding durring the same process. This is clearly infringment." McBride was scheduled to answer more questions after the laughter died down, but was apparently then unavailible for comment.

      --
      CAn'T CompreHend SARcaSm?
    2. Re:Unix code copied into Linux alleged by FluxCapacitator · · Score: 0, Offtopic

      for (int i = 0; i n; i++) {
      :
      :
      }

      My god ... let's sue those bastards!

    3. Re:Unix code copied into Linux alleged by Flarelocke · · Score: 2, Interesting

      It sounds like they're going to suggest that someone in IBM leaked SCO's source code to a Linux developer and that developer submitted it to the kernel. That would explain why they're not releasing the portions of code in question -- in case that developer wipes all the evidence of having had the leaked code.

      The evidence wouldn't be on lkml because it would have been private emails. Neither would it be in the various historical linux versions.

    4. Re:Unix code copied into Linux alleged by Anonymous Coward · · Score: 1, Insightful

      What, you mean that they'll go back in time and stop themselves posting the patchs to the LKM? McBride is a fucking loony if he thinks anyone is taking this seriously.

    5. Re:Unix code copied into Linux alleged by Tokerat · · Score: 1

      Wouldn't that
      • Break the kernel in some way
      • Have already tipped off any developers to cover their stolen IP from SCO? I mean really, I don't think if some guy stole SCO code and put it in Linux that he's sitting there right now going "Gee, I wonder if that's MY code they mean!"
      Also, I thought I read somewhere that SCO claims the code is not within the kernel?
      --
      CAn'T CompreHend SARcaSm?
    6. Re:Unix code copied into Linux alleged by justsomebody · · Score: 1

      yep, you just wait for all

      "{"
      and
      "}"

      lines.

      That's a fool proof case they have

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
  16. More News... by KoolDude · · Score: 4, Insightful


    Here is another CNet article on what SCO Group Chief Executive Darl McBride thinks on this issue. From the article,

    "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview

    Interesting... eh? :)

    --
    getSexySig(); /* returns sexy signature */
    1. Re:More News... by Ami+Ganguli · · Score: 4, Insightful

      Yeah, I thought that was interesting too. Given the limited availability of SCO code, I can think of two explanations that are much more likely:

      • both SCO and Linux developers studied the BSD code
      • the SCO code was (perhaps accidentally) stolen from Linux

      Anyway, if I had discovered that my proprietary software product contained GPL code, I'd discretely try to replace my code, since I'd have much more to lose from legal action. If somebody can prove that SCO stole GPL code, it might be possible to force them to GPL their entire kernel.

      --
      It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
    2. Re:More News... by ZeroConcept · · Score: 1

      As long as they don't present evidence to back up that statement they have zero credibility.

    3. Re:More News... by geekoid · · Score: 1

      I found line by line code in UnixWare that matches the linux kernel...those thieving bastards. No I will not show you what it is.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    4. Re:More News... by ultrabot · · Score: 2, Insightful

      "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview

      What's also interesting, is that since SCO has shipped Linux kernel, they are accepting that it is ok. So if this hypothetical code exists, they gave it away.

      I also wish to enclose the obligatory "fuck off and die, SCO", now that we are on the topic.

      --
      Save your wrists today - switch to Dvorak
    5. Re:More News... by SN74S181 · · Score: 2, Insightful

      The theory is that SCO shipped Linux kernel with the infracting code in it, so now they magically can't own that code, even though they weren't the party that put the infracting code in. But if they were unaware at the time that the infracting code was in it, it's ludicrous to claim they suddenly have surrendered portions of their code base.

      People really need to be careful regarding logical handwaving tricks like that. There are PHBs out there who might actually believe your theories; they'll pitch ALL GPL code out of their shops and set up quarentines if that is the case. It certainly doesn't make the case for a business friendly Open Source process.

      Do you seriously think Programmer G at Company D can slip a little code from Company E into a GPL product that Company E also contributes to and Company E is going to surrender their code base to the FSF?

      If so, stand over there so the rest of us can snicker at you.

    6. Re:More News... by jbolden · · Score: 1

      Your analogy doesn't work. You would have to have:

      Programmer G at Company D slips some FSF/GPLed code into Company G's product X and thus D has liability to the FSF for a license violation.

      And the answer there is yes. They might just have to pay the FSF some money but D is responsible for G's actions

    7. Re:More News... by boots@work · · Score: 2, Interesting

      Let's further assume that Company E released the product to User X under the GPL, before realizing that it included code they didn't mean to release.

      There are really two issues here: is company D's behaviour tortious? And is X still allowed to use the product under the GPL?

      Clearly, D is in trouble, and they had better make damn sure they educate and control their programmers better in future. Their problems are not really particular to the GPL. D would have a similar problem if a programmer copied in a proprietary library without arranging appropriate licensing.

      However, G has granted a licence to use the program to X. The onus is on G to make sure they are not releasing things they don't want to release. I don't really see any grounds for G to revoke X's licence, and in particular saying "we didn't mean to licence that" is pretty lame. So whatever happens to D, everybody else in the world can happily get a copy of the code and use it.

      Obviously the sensible thing for D to do to avoid this is to clearly educate their programmers, and to put up walls between people working on incompatibly licensed code. I don't work for IBM, but I understand that they've done both these things: people are briefed on the consequences fo the GPL, and people working on Linux are not allowed to see the AIX source code (etc.) This is not a complete protection, but it should be pretty close.

      Would D be liable if one of their programmers had done a bad thing despite clear and repeated instructions not to do so? I'm not sure, but I would expect it to count in their favour in court.

      I understand that this is one of the reasons why HP and IBM are *not* going to release their own Linux distributions: they don't want to take the legal risk of licensing all that code without having time to review it. (Other reasons include not wanting the bad PR of squishing other distributions...)

      In any case, SCO publishing all this FUD without identifying the particular sections which are supposed to infringe is ridiculous. Even if they don't want to release their code, publishing the name of the program (or subsystem) that is supposed to infringe would allow a quick determination.

    8. Re:More News... by Hellkitten · · Score: 2, Interesting

      But if they were unaware at the time that the infracting code was in it, it's ludicrous to claim they suddenly have surrendered portions of their code base.

      But afaik they still ship it. To be taken seriously they would have to stop distributing the kernel, or make one where all the parts (they think) they have claims on are removed. (Which would make it easy to just do a diff against a real kernel, see what the alleged infringements are, and then laugh in SCO's face.) When they keep distributing code under GPL after they have discovered somone else put their code in it they would have to stop distributing it, by continuing to give away code that they know contains their code they are surrendering it

      --
      - We are the slashdot. Resistance is futile. Prepare to be moderated -
    9. Re:More News... by black+mariah · · Score: 1

      They might just have to pay the FSF some money but D is responsible for G's actions

      Okay, let's analyze this for a second. Company D breaks the GPL. Assuming that they are called on it, admit that they accidentally violated the terms, and settle out of court for a small yet signifigant sum, who gets the money? The FSF? The software's copyright holder? I don't know if this question has ever been raised before, but it's one that I think needs an answer pretty quickly.

      My money's on copyright holder, BTW.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    10. Re:More News... by nathanh · · Score: 3, Insightful

      "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview

      Interesting... eh? :)

      Not just interesting. It's bloody hilarious! The reasonable conclusion is not that Linux has appropriated SCO code, but rather that SCO has appropriated Linux code. This means McBride is about to demonstrate - in a court of law - that SCO violated the GPL. What a maroon!

    11. Re:More News... by geschild · · Score: 5, Interesting

      Now there's a defence worth contemplating: it's far easier to prove beyond a reasonable doubt that certain code existed in Linux at some point in time than it is to prove the same for a closed pieces of software. This works both ways: the closed source owners can show it was in an open source repository but will they be able to prove it was in their repository before that?

      There's an oportunity for a countersuit based on breaking the GPL in there somewhere...

      --
      Karma? What's that again?
    12. Re:More News... by Anonymous Coward · · Score: 0

      Indeed. It's a nice theory that is generally put forward by people who don't understand the GPL. Yes, SCO disrtributed the Linux kernel, and thus this "infringing" code has been distributed by the Copyright owner under the terms of the GPL.

      So far the theory holds.

      However, SCO are the Copyright holders, so they can retract their licencing. They can un-GPL their code and force it to be removed from the kernel.

      It doesn't really matter much either way though, as I don't believe that any of SCO's code is in the kernel. I also do not believe that McBride is in a stable mental condition, come to think of it.

      Oh by the way, just because you release something under the GPL you do not automatically assign ownership to the FSF. The FSF request that you do, but it is a seperate process and few people do it.

    13. Re:More News... by proj_2501 · · Score: 1

      This is why the FSF wants to be the copyright holder on GPLed software.

    14. Re:More News... by m94mni · · Score: 1

      it might be possible to force them to GPL their entire kernel.

      ... or not distribute it at all
      ... or remove the offending code

      Let's not get too excited.

    15. Re:More News... by Vengeance · · Score: 1

      Heh...

      Examples of line-by-line matching:

      if(0 == i) {
      i++;
      }

      And

      while((c = fread(in) != null) {
      elements[counter++] = c;
      }

      Imagine the nerve!

      What really gets me is this: SCO is as much as admitting that all they have to do is announce what is duplicated, and the open source community will clean it up quickly. So what they're actually doing, by their logic, is harming THEMSELVES by not quickly forcing code changes.

      The REAL issue here of course is IBM's AIX product, and the licensing for it that expires in a couple of months. SCO isn't hoping to win this lawsuit, they're hoping to be either acquired or simply paid off by IBM.

      --
      It was a joke! When you give me that look it was a joke.
    16. Re:More News... by Anonymous Coward · · Score: 0

      In all likelihood, the major legal consequence of having unintentionally shipped their own proprietary code in a GPL'ed project that they distributed would be that users of that code would be held harmless. The act would immunize other distributors from lawsuits over the violation. This theory is relevant to this lawsuit. Basically, if IBM violated SCO's patent license and SCO then distributed the code, any other company (besides IBM and SCO) can make a very convincing argument that if SCO redistributed it without realizing that it contained their intellectual property, how is any third party supposed to know? I picture any sane judge deciding that the other open source developers and distributors have no financial liability and ordering them to remove the infringing code within some limited timeframe.

    17. Re:More News... by jbolden · · Score: 1

      It would be the copyright holder. On your original post you had specified the FSF. The FSF holds the copyright on quite a few of the GPLed apps.

      Where there is a real problem is on apps like KDE where the projects did not do a good job of establishing rights. KDE board might be found not to have standing to persue a lawsuit on many violations.

    18. Re:More News... by Sloppy · · Score: 1
      Just look at the publishing dates. The Linux source code was published n years ago. The SCO code was published in The Mysterious Future. Ergo, Linux was first. ;-)

      That seems like an absurd argument, but it actually fits in perfectly with the intent and purpose of copyright law. Unpublished works do not "promote the progress of the arts and sciences" so why would society grant them copyright? SCO's source code should be thought of as a trade secret, rather than a copyrighted work.

      Credit to this insightful AC (no, it's not me) for revealing the philosophical flaw inherent in unpublished works having copyright protection.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    19. Re:More News... by spells · · Score: 1

      If somebody can prove that SCO stole GPL code, it might be possible to force them to GPL their entire kernel.

      Great more ammunition for MS viral license crap.

    20. Re:More News... by J.+J.+Ramsey · · Score: 1
      "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview Interesting... eh? :)

      What's really interesting is that SCO has not alleged anything of the sort in its legal motions, only in the media. That suggests a couple devious possibilities:

      • McBride is telling something that is technically true, but misleading. For example, the code in question could have been contributed by SCO itself as part of its own efforts with Linux, or code that both SCO and Linux got from classic examples in the K&R C manual. This sort of spin is far easier to do in an interview than in a courtroom where the defense can point out the distortion.
      • McBride could simply be lying, which is also easier outside a courtroom than within.

    21. Re:More News... by no_code_charlie · · Score: 1

      "They can un-GPL their code and force it to be removed from the kernel." Is this true? I sure hope not. Else, the whole GPL thing is a dud. If GPL is revocable then M$ could offer someone like, say, Alan Cox $25 mil or so to retract the GPL on all his stuff and then linuc would be screwed. (Trust me, M$ has $25 mil to spare.)

    22. Re:More News... by jedidiah · · Score: 1

      ...as if Microsoft would tolerate someone pilfering their source code...

      --
      A Pirate and a Puritan look the same on a balance sheet.
    23. Re:More News... by jedidiah · · Score: 1

      You can NOT "un-gpl" code. Once it's been released thusly, it's permanently out of your control.

      This is a good point. So SCO themselves have unwittingly released "their property" to the public at large and continue to do so.

      The fact that SCO continues to distribute an "unclean" kernel should terminate all proprietary rights they have over the kernel. This should should also be grounds for summary dismissal of their case.

      It is also good evidence of barratry and should be used to justify legal sanctions against SCO.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    24. Re:More News... by Anonymous Coward · · Score: 0

      Or... Maybe they both took from BSD.

  17. UNIX license buyouts ? by mj01nir · · Score: 4, Interesting

    From a different CNet article about the lawsuit:

    "HP did a complete buyout of Unix licensing from SCO," HP spokesman Brian Garabedian said. "We have a perpetual license rather than per copy license for HP-UX...We don't believe we have any exposure to the SCO lawsuit."

    Sun, too, bought out its Unix license, said John Loiacono, vice president of Sun's operating platforms group.

    "We bought our Unix license out....We are unencumbered for all things," including Sun's version of Linux, he said.

    And then in the linked article:

    IBM did make one argument defending its use of Unix intellectual property, saying it has the "irrevocable, fully paid-up and perpetual right to use the 'proprietary software' that it is alleged to have misappropriated or misused."

    It sounds like IBM believes that they have "bought out" its license as well. So ...:

    1) Did SCO mislead IBM (and possibly HP, Sun, etc) with these license buyouts?
    2) Is SCO trying to make everyone forget about the license buyouts?
    3) Does SCO consider the buyouts invalid for some reason?

    The whole thing is just weird. SCO is done. Even if they win, no one will ever trust them again. They could produce an OS that whipped any commercial or OSS implementation, but no one would buy it. Had they attacked a smaller, but significant target first (Sun?) they might have had a chance at getting bought out. But with IBM, I don't think they will bother, they'll just crush SCO. They have unfathomable resources. IBM could even afford to lose the case. Sun couldn't.

    --
    the no .sig .sig
    1. Re:UNIX license buyouts ? by EinarH · · Score: 1
      Infoworld have a article on this case.

      Particularly interesting are IBM's positions regarding SCO's claims of ownership over Unix. For example, IBM disputes SCO's claims that Unix was originally developed by AT&T's Bell Laboratories; AT&T used to license Unix to other companies; AT&T licensed Unix to IBM; all commercial Unix flavors in use today are based on SCO's System V Unix technology; SCO owns the rights in and to all underlying, original Unix software code developed by AT&T Bell Laboratories; SCO is the authorized successor in interest to and the owner of all the contractual rights arising from the AT&T Unix agreements.

      IBM also outright denies that its AIX flavor of Unix is a modification of SCO's licensed Unix.

      If the case boils down to who owns UNIX and different flavours off it then I guess this case could drag out for years with endless lawsuits.
      Since SCO can't afford that, and IBM can; SCO will probably go Chapter 11.

      --

      Melius mori in libertate quam vivere in servitute.

    2. Re:UNIX license buyouts ? by greed · · Score: 2, Funny
      IBM also outright denies that its AIX flavor of Unix is a modification of SCO's licensed Unix.

      This one is easy to prove; any non-AIX UNIX administrator will happily proclaim that AIX bears no relation to Solaris. "ODM? What's an ODM? Why doesn't this machine work the way I want! Arrrrgh!"

  18. Feh. by BJH · · Score: 5, Insightful


    Has anyone else seen the comments McBride has been making lately? Here's some choice quotes from news.com.com.com.com's unbiased and uninflammatory article, "Code Red for open source?":

    "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview.

    Please note that he has refused to release examples of this.

    In addition, he said, "We're finding code that looks likes it's been obfuscated to make it look like it wasn't UnixWare code--but it was."

    Please note that he has also refused to release examples of this, too.

    "The Linux community would have me publish it now, (so they can have it) laundered by the time we can get to a court hearing. That's not the way we're going to go."

    Yeah, that's a great excuse to not actually give any evidence of the accusations you're making - tell people that 'the Linux community' will try and sanitize every existing copy of the source code to all the versions of the kernel containing this supposed SCO source - which, he says, has been in the kernel for 'several years'! Perhaps he missed the bit where his lawyers briefed him on the GPL and how it lets anybody have a copy of the source code - including SCO itself! Is he really suggesting that SCO lacks the ability to keep a copy of all currently extant versions of the Linux kernel to use as evidence? F'chrissakes, the md5 checksums of Linus's kernels are public knowledge - if anybody tried to 'sanitize' a particular version, it'd be ridiculously easy to prove that it'd been changed since its original release.

    "This is not about 10 lines of code, it's about 20 years of extremely valuable intellectual property we're trying to protect...Am I supposed to lie down and not say anything about it?" McBride said. "There's a certain point here where you stand up for what's right and let the chips fall where they will."

    Gotta love that last line... McBride wouldn't know "what's right" if it came up and bit his ass.

    I can't even begin to express my disgust for a company that insults, intimidates and sues the very people who have made it possible for SCO to distribute their own version of Linux. Crawl away and disappear, McBride - you're a liar and you know it.

    1. Re:Feh. by Anonymous Coward · · Score: 2, Insightful

      The Linux community would have me publish it now, (so they can have it) laundered by the time we can get to a court hearing. That's not the way we're going to go.

      This is such a bonehead statement, I blinked twice when I read it. After all, Linux being open source, every revision of the source code is readily available. You could not simply "launder" this away unless you somehow manage to destroy every source code distribution of linux in existence that has ever been burned onto a CD, backed up onto tape, etc etc.

      If the allegations have any basis, SCO has no reason not to disclose the details.

    2. Re:Feh. by Gojira+Shipi-Taro · · Score: 2, Funny

      McBride is also my last name. Every time I read a post that puts it in such a negative light, I resolve to kick this particular McBride once more in the Jimmy with steel toed work boots.

      I really hate having my name dragged through the mud by an ethics-devoid fuckwit.

      --
      "Oh my God. This is terrible. This is the end of my Presidency. I'm fucked."; ~ Donald J. Trump
    3. Re:Feh. by Anonymous Coward · · Score: 0

      What, you mean Gojira Shipi-Taro is an alias?!

    4. Re:Feh. by geekoid · · Score: 1

      Hey, my name is Jimmy, you insensitive clod.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    5. Re:Feh. by Gojira+Shipi-Taro · · Score: 1

      OMG, not with a silent second "y" I hope? because that's how what I said was meant to be spelled, and I hate being an insensitive clod...

      --
      "Oh my God. This is terrible. This is the end of my Presidency. I'm fucked."; ~ Donald J. Trump
    6. Re:Feh. by black+mariah · · Score: 1

      "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview."

      There's only so many ways to do things. How many lines are matching? Five? Ten? Fifty? How many are techniques that are standard programming tools? Give us some evidence.

      In addition, he said, "We're finding code that looks likes it's been obfuscated to make it look like it wasn't UnixWare code--but it was."

      Obfuscated the code? What in the name of flying baby shit does that mean? If the code isn't the same, THEN IT ISN'T THE SAME. You can't change something and HAVE IT REMAIN THE SAME, DIPSHIT. And again, what code? There are only a few ways to do things in C. Only so many ways to access serial ports, just a few ways to handle errors... again, what's your evidence?

      "The Linux community would have me publish it now, (so they can have it) laundered by the time we can get to a court hearing. That's not the way we're going to go."

      And in one sentence... SCO signs it's death warrant. This could have gone a lot differently, you know? They could have presented a list of places, WITH SOURCE CODE, where they believe IBM released code illegally. They could have then told the OSS community that they were immune from this and that they only wanted to go after companies that had violated their intellectual property rights. If they'd done that, everyone here would probably support them. As it is, SCO looks like a bunch of dumbass bullies that are too stupid to understand they're a 5' tall 90lb weakling going after the football team's linebacker. The fight will be short, painful, and end up with SCO hanging by it's underwear from the flagpole.

      "This is not about 10 lines of code, it's about 20 years of extremely valuable intellectual property we're trying to protect...Am I supposed to lie down and not say anything about it?"

      No, but you're expected to show some proof of violations. If anyone here thought they found violations of the GPL, they'd be racing to publish their findings. By keeping their supposed findings secret, SCO is doing nothing but digging their own grave.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    7. Re:Feh. by jbolden · · Score: 1

      The statements in the original filing were boneheaded and untrue. There is no basis at all for these claims. I don't know why /.ers can't accept that SCO has no case at all, nothing resembeling a case. They are simply hoping that the costs of fighting the lawsuit lead to a buyout.

    8. Re:Feh. by Anonymous Coward · · Score: 0

      "This is not about 10 lines of code, it's about 20 years of extremely valuable intellectual property we're trying to protect..."

      So they found 10 lines of code that looks similar... Considering projects with multimillion lines of code, I don't think that is very surprising. It's only copyrighted if it is a copy. If it was created from scratch and ends up the same or similar by chance, then that's what its just coincidental.

      If they can't _prove_ that the code was copied from theirs, it's not a copyright violation.

    9. Re:Feh. by Anonymous Coward · · Score: 1, Funny
      UnixWare:
      for(int j=0;j<h;j++,h--)

      Linux:
      int j=0;for(;j<h;h--,j++)

      Dur, 'dees SCO guys could be onta somfink!!!1!1
    10. Re:Feh. by mark_lybarger · · Score: 1

      Obfuscated the code? What in the name of flying baby shit does that mean?

      well, it's where you take someone's code and change the variable names and format and whatever else you can so that it doesn't look like the original code and it's really hard to even tell it's the original code. but in reality, the alrogithm is the same, and the final person didn't code it, they merely obfuscated someone elses code.

      java has this "feature" where you can very easily reverse engineer you .class files to get the .java files (from pseudy binary back to source). as a result, there have sprung up code obfucsation tools where if i'm a library provider, i can run my library through an obfuscation process. this makes it so that if anyone converts my class files back to java files, they won't be able to read it worth a shit. the obfuscation algorithm is kept propriatarty, the .java to .class compilation process and reversal process is public knowledge (part of the java specification IIRC).

    11. Re:Feh. by fredrik70 · · Score: 1

      Thing is though, maybe they take linux code and add it to their source tree? Since noone outside SCO have access to this code they might be able to add these into current and previous release of their source. Yeah, not a completely trivial task but doable. Hopefully there will be a whistleblower in that case...

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    12. Re:Feh. by lamename · · Score: 1

      How does McBride get "about 20 years of extremely valuable intellectual property we're trying to protect"...? SCO bought UnixWare from Novell less 7 years ago, and they have been losing money ever since.

      I'm sure there is no way Linux could advance without the incredible expertise of SCO. Those idiots at places like IBM, HP, Sun, SGI, NASA, MIT, etc never could have done it without them.

    13. Re:Feh. by curtisk · · Score: 1
      java has this "feature" where you can very easily reverse engineer you.class files to get the.java files (from pseudy binary back to source). as a result, there have sprung up code obfucsation tools where if i'm a library provider

      .NET also has this problem, if you use their devtools theres a ildasm provided by Microsoft when used with some other apps, pretty much get you the original source! Kinda scary if you're a commercial developer...you'd have to buy any of the growing array of .NET obfuscators, some of which are NOT cheap by any means

      --

      Sehr geehrter Toilettenbenutzer!

    14. Re:Feh. by Anonymous Coward · · Score: 0

      No, but you're expected to show some proof of violations. If anyone here thought they found violations of the GPL, they'd be racing to publish their findings. By keeping their supposed findings secret, SCO is doing nothing but digging their own grave.


      And you are doing nothing but displaying your ignorance of federal rules of civil procedure and how the discovery process should be used in order to win a civil suit.

      I've got an idea, next time you post something, have an actual point instead of flailing an innane premise out into the vast intellectual chasm that this forum has evolved into.

    15. Re:Feh. by mark_lybarger · · Score: 1

      most major commercial developers don't seem to worry too much about obfuscation. i haven't wasted my time, but i've heard that weblogic.jar can be easily re-sourced.

      it's... really... hard... to... avoid... commenting... on... .NET... must... get away...

    16. Re:Feh. by spells · · Score: 1

      Dotfuscator comes with Visual Studio 2003.

    17. Re:Feh. by curtisk · · Score: 1
      yeah, thats right ,heh

      I remembered reading that the other day, but it totally slipped my mind when I'd posted original, and I'm still on Dev Studio 2002

      --

      Sehr geehrter Toilettenbenutzer!

    18. Re:Feh. by jedidiah · · Score: 1

      What SCO is doing MAY be consistent with federal rules of civil procedure. HOWEVER, there is a large body of potential litigants that have an interest in persuing corrective action. SCO is acting in bad faith by explicitly preventing those other third parties from absolving themselves of liability.

      Judges aren't immune to bias. Juries certainly aren't.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    19. Re:Feh. by Anonymous Coward · · Score: 0

      Modify the GPL to exclude SCO and make it retroactive. That'll teach them.

  19. what i'd really like..... by Lord_Dweomer · · Score: 3, Funny
    Does ANYBODY else wish that we could get some amusing graphical depiction of all the patent/legal nonsense thats been going on lately? I can think of a few different visualizations.....such as a small nest of black ants (SCO) being attacked by a massive bird-killing colony of army ants (IBMs legal team). I would be extremely grateful for any such graphical representations of these kinds of things.

    --
    Buy Steampunk Clothing Online!
    1. Re:what i'd really like..... by Anonymous Coward · · Score: 0

      I'm thinking more along the lines of Mohammed Saeed al-Sahaf as SCO's PR spokesman.

  20. Any evidence yet? by FFtrDale · · Score: 5, Insightful

    Last I heard, IBM was asking SCO to state specifically what code they were alleging that IBM had used, and IBM had gotten no answer. Today's story still has IBM describing SCO's allegations as "unsupported." If the nice folks at SCO can't back up their claims, are they just betting that the effect of the news stories on their business ("no bad publicity") will be greater than the losses they'll take for filing a frivolous lawsuit? What am I missing here?

    --
    Think, write, think, edit, think...then post.
    1. Re:Any evidence yet? by Anonymous Coward · · Score: 1, Insightful

      Well if I was a SCO executive with a heap of stock options that I had no doubt voted to pay myself, i'd be looking into getting the old SCO stock price up before I did the sell thing.

      "Hmmm, if we sue IBM for a HEAP of cash, then even if we don't win the stack of cash, there are likely to be enough prospectors who think we might that they'll start buying up our currently 'cheap-as-chips' shares and I can sell mine off and get off this sinking ship."

    2. Re:Any evidence yet? by 3.5+stripes · · Score: 0

      I spent a half hour reading through their press release/lawsuit, and this is what I got from it.

      Sco owns unix, IBM, sun, SGI bought licences for unix. These licences specifically forbid giving away trade secrets. Many of the functions of high end unix ; smp, high availability code, etc, took many developers much time and money to develop. SInce SCO owns unix, they own these enhancements.

      When IBM started contributing to linux, they stated many times that they were providing the kernel hackers with the resources (experienced developers who worked on many commercial high end unixes, etc) that IBM had.

      SCO says that this is a violation of their licences.

      I'm no lawyer, I'll wait to see what the court says.

      --


      He tried to kill me with a forklift!
    3. Re:Any evidence yet? by arkanes · · Score: 1
      You're accuratly stating SCOs position, although they go farther and say it's not just trade secrets or expertise, but actual lines of code that're in the linux kernel.

      There's also been a number of excellent rebuttals - for example, SCO's ownership of UNIX is quite limited, and the UNIX that they own actually doesn't have many of the features they're claiming are unique.

      The lawsuit boils down to the fact that Linux got to good too fast, and that means IBM used AIX code in it.

    4. Re:Any evidence yet? by jedidiah · · Score: 1

      I think that it is far more accurate to state that the copy of Unix that SCO owns contains NONE of the features they're claiming ownership of.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  21. This is great! by evronm · · Score: 2, Funny

    You had to figure SCO's real motive was to get IBM to buy them in order to avoid the lawsuit.

    I was really hoping that, rather than do this, IBM would sue SCO into oblivion. It's quite gratifying to see it actually happen.

    Woo hoo!

  22. IBM better be careful by phaetonic · · Score: 2, Funny

    If SCO brings in RIAA, half the lawsuit will have "copyright infringement violation" in it and the lawsuit will go in the quadrillions.

    1. Re:IBM better be careful by Anonymous Coward · · Score: 0

      yea, cause the RIAA has a lot to do with this matter...........

  23. And might as well add... by zurab · · Score: 4, Informative

    That there is the SCO reply saying that they have hired consultants and found major code duplications between UnixWare and Linux, although they will not release the information about what parts of code they are talking about that has been duplicated. Article also quotes SCO's Darl McBride:

    "We feel very good about the evidence that is going to show up in court. We will be happy to show the evidence we have at the appropriate time in a court setting."

    I hope they are bluffing, or IBM will just buy SCO out and be done with it.

    1. Re:And might as well add... by mark-t · · Score: 1
      Of course SCO is bluffing. If they weren't, they would've showed their hand by now (to extend the poker metaphor).

      My bet is that they won't even have a shred of evidence to support that premise that IBM ever contributed the code supposedly derived from SCO's IP. I'd even go so far as to say I'll bet that the questionable code was in there before IBM got involved with Linux.

      SCO is, as far as I can see, labelling Linux developers and pretty much all open source developers as a bunch of incompetents, incapable of building anything better than the "software equivalent of a bicycle". This sort of attitude is not only blatantly insulting to anyone who has ever contributed to an open source project, but almost certainly crosses the threshold of opinion versus slander.

  24. Re:I know that there isn't SCO code in Linux becau by dicka_j · · Score: 1

    hahah, I love how this was modded as redundant

    Like: "As if it needs to be said" :P

  25. Re:I know that there isn't SCO code in Linux becau by Anonymous Coward · · Score: 0

    .... Only linux users do ....

    .
    .
    .
    .
    .

    .
    .
    .
    .
    :)
    Posted as anonymous for an obvious reason.

  26. Who's copying who?? by bninja_penguin · · Score: 2, Interesting

    We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code
    And where's the proof SCO (or some programmer there) didn't use the GPLed code of Linux, and shove it into their own sorry excuse of an OS??? According to the GPL, they can do this all day long as long as they release their changes back. But who's to say, some young, enterprising programmer at SCO didn't get stuck with some piece of SCO kernel code he could not get working right, so he 'borrowed' some Linux code lines, tweaked them into place, and hoped no one would find out. You'd better be DAMN sure this isn't the case, McBride, or you'll lose your 20 years of IP crap by violating the GPL!! Wouldn't that just take the cake!! Think about that while you feel the icy water lap around your ankles as your ship slowly glides to a watery death.

    --
    For those who describe their systems as 'boxen', do you order multiple 'boxen' of corn flakes also?
  27. Who stole from who? by FullCircle · · Score: 2, Interesting

    With SCO being closed source, who is to say that SCO didn't steal Linux code and then claim the opposite?

    How do you defend against ANY closed source project doing the same?

    It would be a very scary tactic that could kill OSS.

    --
    If tyranny and oppression come to this land, it will be in the guise of fighting a foreign enemy. - James Madison
    1. Re:Who stole from who? by geekoid · · Score: 1

      Simple, SCO is saying they wrote it and own, fine lets see proof you code was out before Linux.
      The accusor should bear burdon of proof.

      If they can not do that, then I fail to see how they can prove there accusations, short of a confession from a kernel programmer.

      Dear SCO,
      For 10,000,000 I will be your snitch^H^H^H^H^H^H Expert witness.

      Yes, 10,000,000 is my sell out price, Whats yours?

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:Who stole from who? by mkldev · · Score: 3, Funny
      Dear geekoid,

      We agree to your price of 10 million Lira (about $584). Please send us your contact information so we can buy you out.

      Sincerely,
      Darl McBride
      CEO, SCO Group

      --
      120 character sigs suck. Make it 250.
    3. Re:Who stole from who? by Anonymous Coward · · Score: 0

      JFTR 10 million Lira are worth about $10.

    4. Re:Who stole from who? by Anonymous Coward · · Score: 0

      Should be "Who stole from whom?"

    5. Re:Who stole from who? by Anonymous Coward · · Score: 0

      JFTR Lira don't exist anymore.

    6. Re:Who stole from who? by Anonymous Coward · · Score: 0

      JFTR Lira don't exist anymore.

      Wrong - Turkey is not in the EU let alone Euro, and its currency (Lira) still exists.

      xe.com Universal Currency Converter ® Results
      Live mid-market rates as of 2003.05.02 10:24:12 GMT.

      10,000,000.00 TRL Turkey Liras
      = 6.4526537 USD United States Dollars

      HTH

    7. Re:Who stole from who? by Anonymous Coward · · Score: 0

      "Lira" used to refer to the Italian currency by default. If someone is talking about the Lira from Egypt, Lebanon, Libya, Syria or Turkey, they usually prefix it with the countries name. If someone says "Dollar", most people would take that to mean the American Dollar as oppossed to the Canadian Dollar or Austrailian Dollar.

  28. What about the GPL? by Anonymous Coward · · Score: 2, Informative

    Maybe those Unix license buyouts will protect Sun and HP against SCO's lawyers, but if their versions of Linux can't be redistributed freely then the GPL require that Sun and HP not distribute them at all.

  29. I agree by moogla · · Score: 1

    What's with the mods? There isn't really much to say about this other than... what did you expect IBM to do... Get all walked over like a doormat?

    --
    Black holes are where the Matrix raised SIGFPE
  30. IBM and Linux Shall Pay! by f0rt0r · · Score: 5, Funny

    I found the code that matches up exactly, the top five matches are ( drum roll )

    5) for ( int x=0;x lt 10;x++)
    4) while ( x lt 10 ) {
    3) #include stdio.h
    2) #include math.h
    1) int main( String args[] )

    Number 1) shows up in every .cpp file! Linux developers will pay for this blatant violation of SCO's IP rights!

    Note: for some reason the board wigged out with greater than and less than signes, so I had to leave those out. lt = less than

    --
    I can't afford a sig!
    1. Re:IBM and Linux Shall Pay! by localghost · · Score: 4, Funny

      None of those show up in my C++ code.

      for 5, I use "for (int x=0;x<10;x++)" (I removed spaces)
      for 4, I use "while (x<10)" (spaces again)
      for 3, I use "#include <stdio.h>" (yours will produce an error)
      for 2, I use "#include <math.h>" (again, error)
      for 1, I use "int main(int argc, char *argv[])" (I've never seen the syntax you used)

      Oh, and to make the < sign, you need to escape it with "&lt;".

    2. Re:IBM and Linux Shall Pay! by arvindn · · Score: 1

      '<' and '>' obviouly won't show up as such because they start and end html tags. Type "<" to put a '<' sign in your post.

    3. Re:IBM and Linux Shall Pay! by evilpenguin · · Score: 2, Informative

      Let me clue you in. The "<", ">", and "&" signs all have significance in HTML. Comments on /. are HTML. You must use "entities" for these characters.

      Here are the substitutions:

      &lt; equals <
      &gt; equals >
      &amp; equals &

      Use those next time and reach comment nirvana!

      Otherwise, I like your post very much. Very funny.

    4. Re:IBM and Linux Shall Pay! by Anonymous Coward · · Score: 0

      He tried:

      5) for ( int x=0;x lt 10;x++)

      Oh well, better a try than nothing at all.

    5. Re:IBM and Linux Shall Pay! by jpt.d · · Score: 2, Funny

      a google search for int main( String args[] ) brings up som ejava code... Sacrafice his children to Molech for his sins!

      --
      What we see depends on mainly what we look for. -- John Lubbock Now search for that bug slave!
    6. Re:IBM and Linux Shall Pay! by Anonymous Coward · · Score: 0

      - Oh, and to make the "" sign, you need to escape it with "& lt ;".

      No, I think he meant the leet operator.
      x lt 10 = x more leet than 10
      This turned up in the ANSI C specs in 1998,
      apparently after their website got defaced
      by some hardcore kiddies.

    7. Re:IBM and Linux Shall Pay! by Anonymous Coward · · Score: 0

      for 3, I use "#include "
      for 2, I use "#include <cmath>" ...oh well...

    8. Re:IBM and Linux Shall Pay! by zonix · · Score: 2, Insightful
      None of those show up in my C++ code.

      BTW, isn't the kernel written in C?

      --
      What would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
    9. Re:IBM and Linux Shall Pay! by elodan · · Score: 1
      1) int main( String args[] )
      Wow, those SCO guys are really clever - they've found a way to put Java code into the kernel!
    10. Re:IBM and Linux Shall Pay! by sludg-o · · Score: 1

      Note: for some reason the board wigged out with greater than and less than signes, so I had to leave those out. lt = less than

      Try using &lt; for < and &gt; for >.

      Yes, yes, offtopic...

    11. Re:IBM and Linux Shall Pay! by CoolVibe · · Score: 1

      Or they *shudder* used STL code in the kernel....

    12. Re:IBM and Linux Shall Pay! by Tyler+Durden · · Score: 1

      Indeed it is written in C. That would mean 5 would have to be rewritten to...

      int x;
      for( x=0; x10; x++ )

      --
      Happy people make bad consumers.
    13. Re:IBM and Linux Shall Pay! by justsomebody · · Score: 1

      sorry to bother but kernel is written in c not c++, so every .cpp file could hardly be a case

      #include stdio.h
      well that's a win-win situation

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    14. Re:IBM and Linux Shall Pay! by justsomebody · · Score: 1

      #include

      god damn this modern times and copy-paste without thinking

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    15. Re:IBM and Linux Shall Pay! by justsomebody · · Score: 1

      heh, just fsck html for eating characters :-)

      #include <stdio.h>

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
  31. Ideas by rf0 · · Score: 1

    I would think that mnay people have the same idea and as long as it isn't pateneted then people can share. I mean if you look at high end machines there are a number of things that are shared such as cross node memory. Now you don't seem the trying to sue each other do you?

    Rus

  32. Possible community response? by Viv · · Score: 5, Interesting

    Out of curiousity, has anyone ever considered the possibility of a group of people individually filing a claim in small claims court against a company that is doing something they don't like?

    In this case, for example, what if we could mobilize a few thousand people who use Linux professionally to sue SCO for slander? Professionals who use Linux are risking their reputation on it; SCO saying that Linux uses stolen code reflects badly on the professional. If what SCO is saying is untrue, that's slander and is in fact causing damages, yes?

    Now, here's the trick -- if 5000 professionals who are effected by this in the USA were to file claims in small claims court of say, $1000, then SCO would have to simultaneously defend 5000 cases, or risk losing $5 million in damages.

    What kind of effect do you think that would have on a company of SCO's size? Catastrophic, I'd think. And what's nice is that since they're impuning our professional judgment without providing any truth, we should have a cause of action.

    If this is doable, this could be a serious way for a large community such as the free software community to show extreme displeasure with companies that do stuff like this, and for it to really count.

    Any lawyers or anyone with professional knowledge out there that can comment?

    1. Re:Possible community response? by geekoid · · Score: 4, Funny

      what are you, a christian scientist?

      yes, that WAS funny, and if you don't understand it, don't mod it.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:Possible community response? by thadeusPawlickiROX · · Score: 1

      Now that's what I'd call a real /. effect!

      --
      take off every sig for great justice
    3. Re:Possible community response? by SN74S181 · · Score: 1

      I think he's a scientologist.

      And whomever organizes this little 'small claims court' racket better be ready for some close scrutiny. Filing lawsuits purely as a form of harassment is frowned on by judges.

      It's a moot point, though. No IT Professional with the credentials to actually be a player in that sort of legal case is fool enough to risk said credentials on such a sophmoric stunt.

    4. Re:Possible community response? by joonasl · · Score: 3, Insightful

      How truly uniquely American response to basically everything: "Let's sue!!". :)

      --
      "There is a terrorist behind every bush"
    5. Re:Possible community response? by Anonymous Coward · · Score: 0

      the judge will say "this is a textbook class action" and all will be merged. I'm not sure it's slander though; it's more like libel, and unfortunately it calls the question so it will be tossed out. you fail it.

    6. Re:Possible community response? by CausticWindow · · Score: 1

      Filing lawsuits purely as a form of harassment is frowned on by judges

      If this was true, then why are all these lame ass lawsuits popping up in the news from the US, all the time? I understand that most of them are settled out of court, but why is this if the defendants could be sure of winning?

      I think a country as litigous as yours, could really need a good public defense system like we have here. Top lawyers defend you, whatever the case, for just a small fee, affordable for all.

      --
      How small a thought it takes to fill a whole life
    7. Re:Possible community response? by Rick.C · · Score: 1
      If this was true, then why are all these lame ass lawsuits popping up in the news from the US, all the time?

      You have to be able to keep a straight face as you say, "Yes, yer Honor, dems da ones what pilfered me Unix code."

      If you crack even the slightest smile, your case is lost. That's why lawyers get paid the big bucks - they have no sense of humor. None. People who try to argue their own cases are dumb. Only trained legal professionals can handle this type of situation without laughing.
      --
      You were 80% angel, 10% demon. The rest was hard to explain. - Over The Rhine
      "Math in a song is good."-Linford
    8. Re:Possible community response? by poot_rootbeer · · Score: 1

      if 5000 professionals who are effected by this in the USA were to file claims in small claims court of say, $1000, then SCO would have to simultaneously defend 5000 cases, or risk losing $5 million in damages.

      (IANAL, but...)

      It can't cost them that much to file 5000 motions for summary dismissal. Especially since they'll ask for recovery of legal expenses too.

    9. Re:Possible community response? by esampson · · Score: 1

      There are three things that are required for slander that SCO fails to meet.

      1) They have to know the statement is false. Ok, maybe they do actually meet this, but it's damn hard to prove.

      2) The statement has to be issued with the intent of causing harm to the party suing. IBM could sue them, not you. Saying someone is a criminal isn't slanderous to the friends of the person, even though it could reflect badly on them.

      3) It has to be said. If it's in print it's libel (thanks, Spiderman).

      As always, I, ANAL. Offer void in continental US, Alaska and Hawaii. Your mileage may vary.

    10. Re:Possible community response? by no_code_charlie · · Score: 1

      Would cost at least $500,000. Those pigs likely don't have it to spare.

    11. Re:Possible community response? by 0x0d0a · · Score: 1

      I'm pretty sure you'd have to countersue for that.

    12. Re:Possible community response? by 0x0d0a · · Score: 1

      You could say that SCO is intending to harm the Linux community.

      Also, if some enterprising hacker broke into SCO and forwarded internal memos as leaked memos, I imagine that might work as proof.

  33. Cheap trik. by shankariyer · · Score: 3, Informative

    This is the most cheapest way to try to earn money. SCO can't stand up to themselves to come up with good product, so they found the most ugliest route to get money. Kudos SCO !

    Ok - so you've unix' IP, so what ? What have you done with it. Hybernate and wait for unix to hatch by itself and pour money on you. Come on...

    SCO's real purpose is not prove Linux' authenticity, its just a cheap trick to earn money( if they're going to get a dime ). Besides, I hope folks in M$ should be very happy tonight, laughing and feel as if they've got something for their bait...

    Time will tell as who is the real beneficiary is... FUD over Linux at this point - I won't say is bad, because we don't know as how it spins out but it certainly will be a bump in this superfast drive.

    1. Re:Cheap trik. by SN74S181 · · Score: 2, Insightful

      Ok - so you've unix' IP, so what ? What have you done with it. Hybernate and wait for unix to hatch by itself and pour money on you. Come on...

      Sounds like exactly what Ray Noorda did with the DR-DOS code base. He bought it solely as a vehicle to sue Microsoft. But that was against Microsoft, so a whole lot of you guys were cheering him on.

    2. Re:Cheap trik. by vegetablespork · · Score: 1
      A couple of differences:
      • Microsoft was caught red-handed by an independent programmer using the encrypted AARD code to intentionally break Windows 3.1 under DR-DOS, a competing product.
      • The Caldera/Microsoft case was not an intellectual property dispute.
      • Caldera didn't buy up intellectual property and wait for the use of it to gain critical mass to follow it with a lawsuit.
      SCO is persuing one last desperate attempt to avoid their own demise, and perhaps even cash in. The problem for them is that even if they win, the intellectual property they claim is in the kernel can be expurgated, a non-infringing version produced (if indeed the current version is infringing, which I doubt), and they still have nothing to sell.
      --

      Call (206) 338-5780 COLLECT for information about a genuine BA, BS, MA, MS, MBA, or Ph.D.

  34. No by 0x0d0a · · Score: 2, Interesting

    No, because IBM has an SCO license. It's not illegal for another Linux vendor to sell Linux. It *is* a violation of contract for IBM (however unlikely) to use code from their licensed Unix and put it into Linux and attempt to GPL it.

  35. won't come up for 2 years by Anonymous Coward · · Score: 0

    Article says that there won't be a free slot in court for 2 years. SCO will be dead by then.

  36. Another quality dupe.. by Stormie · · Score: 1, Informative

    Another quality dupe from Slashdot's crack editorial staff. Quick! Cut'n'paste those 5-rated comments! Score some cheap karma!

    1. Re:Another quality dupe.. by Anonymous Coward · · Score: 0

      Not to mention all those Information Ministry/1,2,3... Profit/ $, $$, Priceless jokes.

  37. Re:I know that there isn't SCO code in Linux becau by Anonymous Coward · · Score: 0

    Yeah, but your spelling does ;-P

  38. ObSimpsons by Spruce+Moose · · Score: 0, Offtopic

    At the Kwik-E-Mart, Bart plays backseat driver as Laura plays ``Death Row''. Upon reaching the Conservative Judge, the Insanity Plea fails to work, so Bart suggests a Change of Venue. Unfortunately, it changed to the Texas electric chair. ``If I'd hit the Remorse button one more time I would'a made it.''

  39. Yeah! by rsilvergun · · Score: 2, Insightful

    IBM's gonna defend Linux. This was the only thing I was worried about, that IBM would cut a deal with SCO and leave linux users out in the cold. Now that IBM's going to defend itself (and by extention linux) SCO is pretty much done for. I'm really looking forward to that company going bankrupt after what they said about Redhat and Suse.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  40. Just posted to LKML by rf0 · · Score: 4, Interesting

    "As somone who walked for SCO (or rather Caldera how it was called at that
    time) I can tell you this is utter crap. There were very people actually
    doing Linux kernel work then (and when the German office was closed down
    all those left the company) and we really had better things to do then
    trying to retrofit UnixWare code into the linux kenrel. Especially given
    that the kernel internals are so different that you'd need a big glue
    layer to actually make it work and you can guess how that would be
    ripped apart in a usual lkml review :)

    It might be more interesting to look for stolen Linux code in Unixware,
    I'd suggest with the support for a very well known Linux fileystem in
    the Linux compat addon product for UnixWare.."

    Could be intresting :)

    Rus

    1. Re:Just posted to LKML by ces · · Score: 1

      It might be more interesting to look for stolen Linux code in Unixware,
      I'd suggest with the support for a very well known Linux fileystem in
      the Linux compat addon product for UnixWare.."
      Could be intresting :)


      I wonder if IBM has standing to be able to sue SCO for violating the GPL.

      --
      Happy Fun Ball is for external use only.
  41. McBride went on to say by geekoid · · Score: 1, Funny

    Linux has white space, our IP has white space, clearly they stole it. QED.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    1. Re:McBride went on to say by inode_buddha · · Score: 1

      Furthermore, both support the George Foreman USB i-Grill, with suspiciously similar driver routines.

      --
      C|N>K
  42. Coincidence by SnuSnu · · Score: 1

    There are bound to be sections of code that coincide slightly in such a large project. It's hardly proof of plagiarism.

    1. Re:Coincidence by Anonymous Coward · · Score: 0

      There is bound to be similar code especially in the platform specific parts.

      There are only so many ways to setup an i386 for paging. There are only so many ways page tables can be built. There are only so many ways to disable A20....

      If that is the code they are thinking about they made a grave mistake. IBM's lawyers won't let that hold up in court.

  43. It's a marketing ploy by n_jed · · Score: 1, Insightful
    An attempt to get all the linux advocates on its side...

    IBM is accusing SCO of trying to stifle Linux development through the use of the courts

  44. Isn't SCO's logic great? by Papillon3111 · · Score: 2, Redundant

    Taken from paragraph 82 of the lawsuit filed by SCO against IBM.

    Prior to IBM's involvement, Linux was the software equivalent of a bicycle. UNIX was the software equivalent of a luxury car. To make Linux of necessary quality for use by enterprise customers, it must be re-designed so that Linux also becomes the software equivalent of a luxury car. This re-design is not technologically feasible or even possible at the enterprise level without (1) a high degree of design coordination, (2) access to expensive and sophisticated design and testing equipment; (3) access to UNIX code, methods and concepts; (4) UNIX architectural experience; and (5) a very significant financial investment.

    Somebody please explain to me how software is like a car/bicycle.

    Further into the lawsuit you'll notice SCO isn't actually suing IBM for releasing their source but because they are losing business. With A-holes like McBride I can't imagine why. I just wish they'd hurry up and die.

    1. Re:Isn't SCO's logic great? by The_dev0 · · Score: 0

      Well, if code is anything like my car, you gotta warm it up for half an hour before you can compile, then when it does get going it craps out while you swear and pull your hair out in clumps. My so-called code is like that, anyway...

      --
      Never fight naked, unless you're in prison...
  45. Correction by Papillon3111 · · Score: 2

    paragraph 84
    not 82

  46. IBM by incom · · Score: 1

    Wow, under all those lawyers, and Fancy suits, there's typical slashdot geek in there.

    --
    True genius is grasping a situation like a peice of fruit, and peircing it just right so that it drains dry.
  47. Finally... by Anonymous Coward · · Score: 1, Funny

    ...we can enjoy to see someone ripped off by an army of lawyers.

  48. Sell out price... by Anonymous Coward · · Score: 0

    Hell, I haven't gone shopping in a month. I'd sell out for $45 + travel expenses.

    SCO, are you hearing this? Reply here!

    - Anonymous Coward

  49. Rowboat vs. Bizmarck by Akardam · · Score: 4, Funny

    McBride's taking a dingy up against the battleship that is IBM. Can he honestly think that SCO won't be reduced to so much virtual matchwood? I'm just waiting for the moment when he's staring down IBM's big guns, and goes "Eep!".

    Wait for it...

    1. Re:Rowboat vs. Bizmarck by Gulik · · Score: 1

      Can he honestly think that SCO won't be reduced to so much virtual matchwood?

      As several people on /. and elsewhere have speculated, this may well be a bid by SCO for IBM to buy them out, which would be a cheaper solution for IBM than going to court.

      What I'm hoping will happen is that, while it would likely be monetarily cheaper to just buy SCO, IBM decides to go to court anyway in order to really settle the issue, and thereby make Linux less susceptible to the next wave of FUD (which Balmer has already started with the ``you don't know where Open Source code comes from'' routine).

      Since IBM has committed a chunk of their business to Linux, making sure Linux remains a viable solution in the eyes of IT managers may well be worth the extra money it would take to try the case against SCO.

    2. Re:Rowboat vs. Bizmarck by jedidiah · · Score: 1

      However, this sort of activity would fall under the heading: "negotiating with terrorists". If they allow SCO to profit from this action, they invite others to do the same. OTOH, IBM has extra money to drag this through the courts slowly and painfully. They may even be able to force SCO to spend an amount equal to it's entire market cap on this case.

      IBM may even be able to pull off some sort of barratry charge against SCO, get a large judgement, and then execute on the corpse.

      The idea should be to make SCO execs paupers while gaining control of all SCO assets.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    3. Re:Rowboat vs. Bizmarck by Anonymous Coward · · Score: 0

      Ah, but survival isn't part of SCO's plan.

      A dingy can actually do substantial damage to a battleship, if the people on board are crazy and suicidal enough. Remember the USS Cole?

    4. Re:Rowboat vs. Bizmarck by Gabrill · · Score: 1

      I seriously doubt IBM will have to bring it's 16 inchers to bear on the silly rowboat. It'll probably be more like the rowboat trying to ram the Bizmark in the screws and finding out what a terrible decision THAT was.

      --
      Always going forward, 'cause we can't find reverse.
  50. SCO, why not try for look and feel ? by Humunculus · · Score: 2, Funny

    This what Apple did of Microsoft... Now lets see, take a sys V UNIX and linux console and place them side by side. Now type: uname touch SCO ls cat SCO > /dev/null rm SCO mmm, works the same... If it quacks like a duck, it must be a duck ! I think they could win this hands down ! Now if I give up programming and take up corporate copyright law, I think I will be rich.. Rob. "For Every Pleasure There's a Tax"

    --
    The Man
  51. Comments from an ex-Calder employee` by ssimpson · · Score: 4, Insightful

    I like Christoph Hellwig's (ex-Caldera employee) comments on the Linux Kernel Mailing List 02 May 2003 06:44, in part:

    "It might be more interesting to look for stolen Linux code in Unixware, I'd suggest with the support for a very well known Linux fileystem in the Linux compat addon product for UnixWare.."

    Let's hope the FSF sue SCO for infringement of the GPL. For a billion dollars. I'm sure IBM lawyers would lend a helping hand! ;)

    --
    "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
    1. Re:Comments from an ex-Calder employee` by jrumney · · Score: 2, Informative

      The FSF can't sue SCO, they don't hold copyright over any of the code in the Linux kernel (if FSF held copyright over Linux, RMS would probably want distributions to just call themselves GNU, not GNU/Linux).

    2. Re:Comments from an ex-Calder employee` by Anonymous Coward · · Score: 0

      Last time I checked, the FSF did not own the rights to Linux, so they'd have a hard time suing SCO over it.

      I wish to God that people around here would take the time to read and understand the damn GPL (While we're at it, the LGPL, BSD, MIT and Artistic licences, too). What is even worse is that you've been moded up for getting it wrong!

    3. Re:Comments from an ex-Calder employee` by theLOUDroom · · Score: 1

      The FSF can't sue SCO, they don't hold copyright over any of the code in the Linux kernel (if FSF held copyright over Linux, RMS would probably want distributions to just call themselves GNU, not GNU/Linux).

      I think you can sue someone for violating the GPL even if you don't own the copyright. You might not be able to win damages, but you could probably have the terms of the GPL enforced. I think this has already happened, but I can't remember the case. It was considered an important test of the GPL.

      --
      Life is too short to proofread.
    4. Re:Comments from an ex-Calder employee` by jrumney · · Score: 1

      On what basis would you sue someone over code which you hold no rights over? How would you know they don't have a separate license with the copyright holder that allows them to do what they're doing?

  52. PLUG/SCO interview results? by Kaz+Riprock · · Score: 1


    What ever happened at the PLUG April meeting where we were told they would be interviewing SCO with our questions that were submitted?

    Anybody have any idea what happened at the meeting or have a transcript from the questioning?

    Their mailing list doesn't seem to have much mention of it.

    --
    Mordor...a magical, mythical land where women are more rare than dragons--but where every man would rather find a dragon
  53. Barratry by shepd · · Score: 5, Informative

    I'm pretty sure any lawyer that helped you with this would be charged with barratry, or for vexatious litigation.

    I'm not sure if individuals can be charged with something similar. You'd have to look it up. :)

    Note that the charges you are laying can still have some merit, but doing them in an attempt to subdue the defence isn't legal.

    --
    If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
    1. Re:Barratry by Anonymous Coward · · Score: 0

      What? Is the US legal system really that bad? So that when a company sues another for the purpose of forcing that other company to buy them out, it goes to court, but if the programmers who are really hurt by a companys actions want to sue, it would be illegal?

      Not only "most money wins", but even "companies can sue without reason, individuals cannot sue companies even with good reason"?

      Is this really true?

    2. Re:Barratry by awol · · Score: 2, Informative

      Nope. These cases would only be vexatious if the claims were groundless. The class action thing in the US is designed to make the prosecution of the N legitimate claims less onerous on both the plaintiff and the defendent. But everyone wronged is entitled to runa claim for damages.

      --
      "The first thing to do when you find yourself in a hole is stop digging."
  54. So, what if SCO is right? by akorvemaker · · Score: 5, Interesting

    Just curious. It seems that all the comments revolve around how SCO is stupid and wrong and greedy and dumb and soon to be extinct.

    What if they're not. What if they do have a genuine grievance. I'm not trying to be a troll or flamebait, just honestly curious. What impact would this have on GNU/Linux? Would people honor SCO's claims if they're proven right?

    1. Re:So, what if SCO is right? by Anonymous Coward · · Score: 0

      Would people honor SCO's claims if they're proven right?

      Ah, this being /., people would just say "so what if there IS SCO code in Linux, it's completely obvious algorithms anyway and SCO should never have been given a patent for it by the b0rked US patent system, so we're justified in copying it".
      It would help the level of self-righteous anger if Microsoft could somehow be shown to be "assisting" SCO - for example, if, say, a SCO employee once bought a second-hand car off a Microsoft employee, that's OBVIOUSLY part of the great Microsoft plot to destroy Linux..
      Linux is perfect and has no flaws whatsoever, didn't you know that?

    2. Re:So, what if SCO is right? by Anonymous Coward · · Score: 1, Informative

      First of all, if SCO's claims are in some way valid, it's primarily IBM's problem.

      More importantly, IBM's contributions are somewhat peripheral, so in the worst case, it would involve minor cleanups of the infringing portions. It would not affect functionality significantly.

      As a past example, the things omitted from 4.4 BSD-Lite compared to the 4.4 BSD that actually requires source licenses were entirely insignificant, and haven't prevented the *BSDs from being fully functional.

      The settlement wasn't actually honored by everybody - DEC was never sued for continuing to distribute net2...

    3. Re:So, what if SCO is right? by argent · · Score: 1

      It's USL versus CSRG all over again.

      If SCO is right, then you better hope there's a smoking gun in the SCO kernel like CSRG found in USL's source base.

      It could well be that the code in question came from California, not New England. There's BSD code in SCO, there's BSD code in Linux, hell there's BSD code in NT. It's like the 95% [1] of DNA that all mammals have in common...

      Otherwise... well, you know, there's other code bases and other logos. The Platypus is pretty cute.

    4. Re:So, what if SCO is right? by mark-t · · Score: 1
      "so what if there IS SCO code in Linux, it's completely obvious algorithms anyway and SCO should never have been given a patent for it by the b0rked US patent system, so we're justified in copying it"

      This is not SCO's allegation. SCO is saying that the open source community misappropriated trade secrets from SCO. If the issue were about patents, SCO would be *required* to be immediately forthcoming on the issue because patents are supposed to be public knowledge.

    5. Re:So, what if SCO is right? by 0x0d0a · · Score: 1

      Well, let's see. First, SCO would probably be villified even more, and people with technical knowledge would demonstrate the minimality of whatever was taken.

      Second, IBM would probably be blamed. "Oh, IBM was being stupid and got burned." The OSS community would distance themselves, as would RH and Suse (which are *not* liable, regardless of what McBride spouts in interviews).

      Third, IBM would probably appeal (since IBM can't afford to lose the SCO license). So it'd drag on and on, almost certainly until after SCO goes under. If they were forced to, they'd honor the agreement. No one else would have to honor everything.

      Fourth, Microsoft would probably use it as FUD material for a few years.

      Fifth, SCO/Caldera employees would be reviled at conventions for a while.

      In sum, it pretty much wouldn't have much of an impact on the Linux community.

    6. Re:So, what if SCO is right? by cyberformer · · Score: 1

      This is one reason why IBM has to fight this in court. If it buys SCO, many people (myself included) will assume that SCO actually had a case.

  55. Microsoft owns a share of SCO by SystematicPsycho · · Score: 0, Troll

    didn't you know? I wonder if M$ has some driving force behind in all of this?

    --
    Analytic & algebraic topology of locally Euclidean meterization of infinitely differentiable Riemmanian manifold
  56. Re:I know that there isn't SCO code in Linux becau by jtdubs · · Score: 1

    That point, I believe, is up for debate...

  57. Some hints? by Anonymous Coward · · Score: 1, Informative
    http://www.eweek.com/article2/0,3959,841419,00.asp

    McBride also addressed the controversy surrounding SCO's plans to make users pay for some Unix software they're running, unlicensed, on Linux. SCO announced this week a Unix library licensing program that will let companies pay $149 per server processor to use those Unix libraries.

    ... so they're libraries?

    and nobody could have guessed this next paragraph:

    While claiming that it is hard to estimate how many people are technically in breach of its licensing terms, McBride said it's "very widespread and would generate a revenue stream in the millions of dollars. We know who they are." But he stressed that this is a "friendly move" by the company, which would be flexible in determining what customers who had been using the software in an unlicensed way for some time would be charged.

    1. Re:Some hints? by mark-t · · Score: 1
      "We know who they are"

      What are they claiming to know? The identities of every single Linux user? Excuse me while I pick my lungs up off the floor from laughing too hard.

  58. Is SCO busy stealing Linux code RIGHT NOW? by Anonymous Coward · · Score: 1, Interesting
    Could the reason they're holding back showing the so-called similarities between their Unix code and the existing Linux code is that there aren't any? And they say they'll show the similarities in court because by the time they get to court, they expect to have put something together pasting snippets of Linux code into something they'll then claim has been in the (closed) Unix codebase all along?

    Maybe IBM should move the court to order that SCO file their "evidence" under seal with the court right now.

  59. examples by jbolden · · Score: 0, Redundant

    "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview.

    Please note that he has refused to release examples of this.


    OK I'll provide some examples
    1) #include
    2) #define __DEBUG
    3) ptr=*x->next :-)

  60. ... doesn't suck by Craig+Ringer · · Score: 1

    *shudder*

    You think OpenServer is bad... try OpenServer running Microsoft Xenix binaries using its compatability layer? Our Accts and bookings system doesn't read TERMCAP, and was written before Terminfo existed. Sheer hell.

  61. I'm wondering. SCO please answer this. by jelle · · Score: 1

    I'd like to ask SCO this question:

    SCO, please tell me.

    So you claim you need (3) and (4) to make Linux '?-bicycle-?', as you say, of the same quality as UNIX '?-luxury car-?'.

    Then how was UNIX created before (3) and (4) were available?

    Ever heard of the chicken and egg problem? How do you get access to UNIX source code, methods and concepts when you're beginning to write and define it? How can you have architectural experience with something that you're still building and haven't built before? If you have any answers to those questions, then those same answers can be applied to how Linux could be made into 'the equivalent of a luxury car' without (3) and (4).

    And for the rest, (1) and (2), and (5) are irrelevant for the way Open Source works and you, IBM, we, and the judge all know it.

    --
    --- Hindsight is 20/20, but walking backwards is not the answer.
    1. Re:I'm wondering. SCO please answer this. by CoolVibe · · Score: 1

      I'm really happy driving my tank, thank you... :)

  62. Ubersoft by Kj0n · · Score: 1

    For more information, check out this Ubersoft thread.

  63. ad at the top of /. page by xorbe · · Score: 2, Funny

    Buy SCO OpenServer 5.0.7: Want the latest greatest...
    SCO Unix and Linux help
    SCO OpenServer: Find the best deal!...

  64. Trust Slashdot... by MjDascombe · · Score: 1, Redundant
    To put a pro-linux spin on this. I mean, there are no new links in this article that in any way add anything pro-linux to a very old story, and yet they still manage to make it sound as though linux (as usual) is perfect and always in the right

    When are slashdot going to grow up, escape their linux-centric origins, and start being a fair,unbiased newssource again?

    1. Re:Trust Slashdot... by Anonymous Coward · · Score: 0

      Linux is not perfect nor always in the right.

      However, in this case, SCO's claims are just too ridiculous to be credible.

      I don't particularly like Linux, but I know enough about the facts to make it obvious to me that this case is absolutely ridiculous.

    2. Re:Trust Slashdot... by d^2b · · Score: 1
      When are slashdot going to grow up, escape their linux-centric origins, and start being a fair,unbiased newssource again?
      1. Escape their linux-centric origins like Caldera you mean? C'mon, it smells bad enough around here already.
      2. On behalf of slashdotters everywhere, I strongly resent the implication that at any point in the past slashdot was a fair, unbiased newssource.
    3. Re:Trust Slashdot... by acerbix · · Score: 1

      ... the very day Fox News starts being a fair unbiased newssource (again(?) )...

    4. Re:Trust Slashdot... by Anonymous Coward · · Score: 0

      Word is, slashdot was never an unbiased news source.

  65. Very confusing! by minkwe · · Score: 4, Interesting
    "We're finding...cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code," McBride said in an interview.

    "In an e-mail discussion that took place 24 and 25 April, SCO-Caldera Senior Vice President Chris Sontag told MozillaQuest Magazine that there is SCO-owned code in Red Hat and SuSE Linux distributions. He also told MozillaQuest Magazine that the tainted code is not in the Linux kernel that Linus [Torvalds] and others have helped develop. We're talking about what's on the periphery of the Linux kernel.

    --
    "Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
    1. Re:Very confusing! by poulbailey · · Score: 1

      You're quoting MozillaQuest here. MozillaQuest! Do you have a better source?

    2. Re:Very confusing! by ultrabot · · Score: 1

      We're talking about what's on the periphery of the Linux kernel.

      It would be interesting to know what parts in the periphery boost linux enough to get it from "bicycle" status to a full fledged enterprise unix. sysvinit? tuxracer? Nah, neither of them is by IBM...

      --
      Save your wrists today - switch to Dvorak
  66. If MS wants a fight ... by Taco+Cowboy · · Score: 0, Offtopic



    .... then MS will get a fight it can't forget


    Take for example, the name "Command Prompt" which may be counted as one of the "trade secret of unix"


    This time MS has to face not only IBM, but also The Regents of The University of California which happen to be the rightful owners of *BSD.


    If MS wanna fights the world, then the world will fight back.


    It's that simple.







    --
    Muchas Gracias, Señor Edward Snowden !
    1. Re:If MS wants a fight ... by Anonymous Coward · · Score: 0

      Bwhu? The name "Command Prompt" might be a trade secret? What. The. Fuck?

      Also, what the fuck does BSD have to do with it? W're talking about SysV. Go take your meds, you fucking retard.

    2. Re:If MS wants a fight ... by Anonymous Coward · · Score: 0

      What's with the whitespace?
      Retard.

  67. GNU/LinOS by AYEq · · Score: 3, Interesting

    It is times like this when I wish that Stallman et. al and linus didn't mess with *NIX. Really it seems that if you touch *NIX at all you are just waiting for a court battle.

    Of course then "GNU's not Unix" wouldn't have such a ironic twist :)

    ps. I love linux,bsd and really only use *NIX based systems, but it is really hard to find an organization that hasn't been sued over it's history with unix.

  68. Good thing they pick on someone their own size by Anonymous Coward · · Score: 0

    Or actually 3000 times bigger, in terms of market capitalization.

  69. Has anybody actually read IBMs filing ? by Anonymous Coward · · Score: 0

    Does anybody have a link ?

    Anonymous Coward

  70. Then make it a "lose-lose-lose" situation for all by Taco+Cowboy · · Score: 1, Insightful


    Sadly, the MS FUD has already started. In the wonderfully written "Code Red for Open Source" article at Cnet which is fair and balanced (in that Fox News kind of way) Balmer is quoted as saying something to the effect, "See, you dont know who's writing your OSS software."



    If MS wants to make it a "lose-lose" situation for the IBM-Linux alliance, then we can make it a "lose-lose-lose" situation where NOBODY came out a winner.

    Steve Ballmer may thinks he owns the world, but he ain't, at least not yet.

    Believe it or not, MS still depend on the world for its own survival, Mr. Ballmer may think otherwise, but if MS crosses the line, the world will shuns MS like a plague.

    No one is an island in this world, MS is no exception. If MS really wants a fight, then lets make it one that MS wins nothing but financial ruins.

    MS is already suffering from utter Moral Bankrupcy, and from there it's a very short trip to Financial Bankrupcy.

    IBM has learnt the bitter lesson back in the 80's, mebbe it's MS turn this time around.







    --
    Muchas Gracias, Señor Edward Snowden !
  71. IBM's Open Source Guidelines by scottme · · Score: 5, Informative
    IBM has a comprehensive and stricly-enforced internal set of guidelines that any employee who works on OSS projects, whether on IBM's time or on his/her own time, must read, understand, and certify compliance with. It's a condition of employment, even. And there's an approval process that must be used (and I quote):
    whenever an IBM group wants to:
    • start or join an OSS project with the intention of contributing code to the project and/or maintaining the code base;
    • include third party OSS with an IBM product or service;
    • ship some or all of an IBM product in source code form under an open source license;
    • publish the source code for a reference implementation.


    IANAL, but it seems to me that there must be a defensive line against the SCO suit in the mere fact that it has promulgated that policy. Of course the existence of the policy is no guarantee that it is going to be adhered to 100%, but in the (unlikely) event that SCO is able to establish that some illegal copying of their material did take place, the corporation can hold its hands up and ask what more it could have done to prevent it.
  72. This is terrible! by Andy+Tanenbaum · · Score: 1, Funny

    How cowardly of SCO to go after the little guys. I say we show our support by starting up a modest (but sincere) IBM defense fund. I'm willing to put in 5-10 dollars.

  73. yeah.. for real.. by Anonymous Coward · · Score: 0

    i hate to flame.. but this is ridiculous..

    this is probably the 4th article i read regarding this stupid lawsuit.. not much is going to happen/change anytime soon (that's how wonderfully quick the judicial process here is).. so PLEASE.. for the love of us and all.. let's post some other cool shit for the time being..

    and yes.. the evil bit run-on was cute ;-)

  74. It really is very sad for Caldera by valisk · · Score: 3, Interesting
    Once a producer of a reasonable Linux, which with a little polishing could have been a contender, buy out a crippled and dying Unix House and procede to give themselves a blood transfusion from the probably dead Sco, then they put on his clothes and begin talking, what they think is Unix talk.
    I'll sue your ass etc.
    Make claims about source code, which as itself is unpatentable (are 'Caldera' suggesting they own the 'do while' loop?, due it's reusability and the fact that there are only so many ways to do things, and that any programmers will probably come up with the same thing from time to time on a totally independant basis.

    Caldera's claim that their source has somehow ended up in the Kernel of various companies is debatable particularly the comments about 'obfuscated code' which is a way of saying that the code in question bares no resemablance to their code at all, other than it was written using the same programming language and perfoms a similar function.

    It really is all about the money, Caldera had no involvement in the original creation of the Intellectual property and have no moral right to lecture the world on how sad it is when such property is debased, dressing up as Sco and pretending to be Sco won't change anything here.
    I've no doubt the original angle was for a buyout but now we've got to the point where it is abundantly clear that IBM have no intention at all of buying them the game is up, and so Caldera/Sco will become a shell of a company file for Chap 11 and fire all it's staff, hire a few lawyers instead and float along with whatever cash they have left until they sink, then somebody will buy the Unix IP at a firesale price, hopefully they will cast it into the public domain lest it corrupt any other mortals.

    --

    Economic Left/Right: -0.62
    Social Libertarian/Authoritarian: -3.69
  75. OT but... by curious.corn · · Score: 1

    ... there's a question haunting my mind; the Caldera logo. Is it a red C stamped upon a blue globe, or is it a Mickey Mouse blue silhouette dawning from the east? Either way, it's quite revealing ;-)

    --
    Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
  76. Re:Then make it a "lose-lose-lose" situation for a by dalamcd · · Score: 0, Flamebait
    No one is an island in this world, MS is no exception. If MS really wants a fight, then lets make it one that MS wins nothing but financial ruins.

    Yes, let's. While we're at it, let's cure cancer and bring about world peace, as well. Also, we can put that whole 'intelligent life elsewhere in the universe' thing to rest, one way or the other. Are you ready, my brothers? Let us be off!

    We can figure out the details later, right?

    dalamcd

    --
    moer liek CELtroid prime!!@1!
  77. what if.... by jbloggs · · Score: 0

    Typical of the slashdot crowd, no one seems to think there is any possibility that SCO could be right. I wouldn't say the probability is 0. SCO I'm sure sees the outcry this is causing and knows it'll be their doom if they're totally full of shit, so what if they really are telling the truth?

    1. Re:what if.... by Anonymous Coward · · Score: 0

      No because months before hand Love(CEO) was mentioning on how he bought Unix in the hopes of milking it.

      Later before the press release Love stated that he owned suid's, bash, c, sysV,etc and were looking into using his new purchase as a way to make more money.

      He then hired David Bios. 6 months later all off the suden he comes out and claims for years that IBM was stealing their code.

      Ya right. It was all planned beforehand. You can tell by the evidence. Also sco's market cap was only around 17million before the lawsuit and now they are at close to 40! At the same time the board bought shares of SCO stock at $.85 a share! What a bunch of greedy bastards.

      What will happen if they win is that sco's revenue will jump by over %1000 and stock price will go through the roof making all these guys rich multimillionaires.

      This is the plan.

    2. Re:what if.... by jedidiah · · Score: 1

      That might be because SCO has already commited several blatant and obvious lies already. Linux was not as weak (pre-IBM) as SCO is now making it out to be and THEY were the ones that started SMP development on Linux.

      IBM came late to the party and EVERYONE with something resembling a clue knows this.

      Then there is the fact that some of the features that SCO is complaining about DON'T EXIST IN ANY SCO PRODUCT.

      SCO is claiming property rights on things that they've neither created nor bought.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  78. Seriously by CausticWindow · · Score: 1, Troll

    How can you even begin to pretend that there is something remotely just about the judicial system in the US?

    Seen from a foreigners perspective, the only purpose of this system is for corporations to harass their customers and to extort each other.

    As for criminal law, there seems to be a common perception that the more money you've got, the more likely you are to get off. And when people are shipped off to jail, most americans seem to enjoy making ass-raping jokes, like that should be a mandatory part of any criminal punishment. It makes your capital punishment look like mercy.

    And don't get me started on bizarre laws and amendments, protecting certain corporations or industries. It can be quite amusing to compare the latest laws passed by your congress with the enlightening figures over at www.opensecrets.org.

    Your country most be one of the most openly corrupt, by western standards. Your legal system looks like a complete sham, but all you seem to do about it is pass lame jokes like "too bad you're short on cash!" and "hope he likes it up the batty!".

    --
    How small a thought it takes to fill a whole life
    1. Re:Seriously by Anonymous Coward · · Score: 0

      please hold up an alternative judicial system for comparison

  79. Seriously, though... let IBM know it's appreciated by ron_ivi · · Score: 1
    If we're buying something (servers, services, AIX, whatever) from IBM, let them know that we appreciate their efforts&contribution, and that that helped influence the decision.


    That should get IBM's sales guys to become Linux advocates too!

  80. Re:Then make it a "lose-lose-lose" situation for a by Anonymous Coward · · Score: 0

    Sharks don't get cancer. Incredibly cancer-resistant mutant mice have been created.

    The simplest way to get intelligent life elsewhere in the universe is for some humans to get off this planet, permanently. It would only take a hundred years or so to get to the next start system - with CURRENT technology.

  81. Share and enjoy by OpCode42 · · Score: 2, Funny

    Yeah, share and enjoy, we dont need your lawsuits!

    Share and Enjoy
    Share and Enjoy
    Boot up your box
    With our communist ploy
    To run your machine
    Free from emipres mean
    And when it breaks down
    And starts to complain
    About panics on boot
    Segfaults in your games
    There's no disk space free
    Missing initrd
    There's a memory leak
    CPU usage peaks
    And the docs are just
    Full of weird techie speak
    And you've got to stop, for the good of your health!
    We'll tell you, 'Learn C and fix it yourself'.

    1. Re:Share and enjoy by no_code_charlie · · Score: 1

      You need a line about when it tries to have sex with your cat.

  82. IN SOVIET RUSSIA by noogle · · Score: 0

    Unix steals IBM!

    --

    I'm smarter than the average bear.

  83. Re:Ballmer Misquoted by Surak · · Score: 4, Informative

    Ballmer actually said: "customers will never really know who stands behind this product."

    The intent is similar, but it's a subtler shade of meaning here.

    Of course, people pay Red Hat and IBM and other companies money to stand behind the code. And you DO know who wrote the code anyways. Their names are all over it.

  84. Thanks to Minix by Anonymous Coward · · Score: 0

    I'm not worried. Who needs the feature creep of Unix anyway ;-)

  85. This is a rair time, I hope the Little Guy Looses. by jellomizer · · Score: 1

    Most of the time it is the Big Corporation that is hitting on the little guy. But it seems like SCO is a mouse tring to eat the cat. If I were IBM I would just let them suck away all their money in legal fees and let them go bankrupt. There is no great loss in loosing SCO anyways. There is still Linux and if you want a Unix there are the BSDs. If I were SCO I would go well our Unix platform is dead perhaps we should change our focus on something else.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  86. Am I Missing Something??? by p.rican · · Score: 1

    As I see it, the source code for the linux kernel/GNU linux software has been available since day one. Is there anyone out there that could vouch for the SCO claim that there is reimplemented/borrowed/misappropriated code in the kernel/GNU software. If there is, why is this just becoming an issue now? In my eyes, that question does give credibility to the theory that SCO is just "fishing" for a buy-out. Either way, I hope BIG BLUE and the open source/Free Software Community bitch-slaps SCO in and out of court. I've been using GNU/Linux since 1996 and find it impossible to believe that someone (SCO) could make a blatantly idiotic claim that GNU/Linux could not be where it is today w/o someone giving OSS developers enterprise level code. That is just a HUGE slap in the face to anyone who has been doing work on GNU/Linux software. Whenever I've needed help with any problems I've had with Linux, there's ALWAYS been someone willing to offer first class/knowledgeable help......Yup, even on /. Cheers to the programmers/developers and testers that have given me such a wonderful operating system!

    --

    /. --"Demented and sad....but social" -Judd Nelson

    1. Re:Am I Missing Something??? by usotsuki · · Score: 1

      Rather than SCO getting bought out by IBM, I hope IBM puts them out of their misery entirely.

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
  87. GPL the whole thing is not the only option by dmaxwell · · Score: 3, Interesting

    The GPL is not some Evil Overlord's World Destroying Superweapon. GPL violation is copyright violation. Even if there is some language in the GPL concerning penalties for violation, it is up to a judge to set the penalty. The judge has more options than "make them GPL the whole thing". He could restrain distribution altogether. The violator could be made to pay for an alternative license to the code he's using. He could even be made to pay damages and to reimplement the code in question. Like any copyright violation, the Court will want to put an end to it. There's more than one way for them to do it.

    Incidentally, discretely replacing such code may not necessarily work. A whistleblower could whip out a tainted code tree. Your developers might screw up and leave debugging symbols in old binaries. It would not be hard to prove in court that a sanitized code tree did not create a binary in dispute. The court may well see a code tree as business records to which the rules of evidence apply. "So Mr. Project Co-Ordinator, where is the source code that produced the exhibit in question?"

    Yeah, getting the GPL stuff out your code tree would be a good idea. There's no ironclad way to prove it was never there.

    1. Re:GPL the whole thing is not the only option by Anonymous Coward · · Score: 0
      GPL violation is copyright violation.

      Is there any precident that shows that the GPL is in fact either a legally binding contract or a copyright? While it is generally honored as such, it seems that rests entirely on the good faith of the software publisher.

      What would happen to the validity of the GPL were it to be scrutinized in a court of law and found to be legally invalid?

    2. Re:GPL the whole thing is not the only option by theLOUDroom · · Score: 1

      GPL violation is copyright violation.

      No, GPL violation would be breech of contract. It is true though, that someone could argue that they had never accepted the terms of the GPL. In this case they could be charged with copyright violation, but I'm not sure a judge is going to believe that someone distributing GPL'ed code had refused to accept the license. That makes it more complicated that a simple copyright violation.

      Take this example:
      Say I wrote some nice code to do reed-solomon encoding. You write me and email requesting a copy of the code. I send you and email with the code attached, saying that if you use it, you're agreeing to the terms of a license that's also attached.

      I think in this case it would be pretty easy to get a judge to rule, that by using the code, you had accepted the terms of the license. If a judge ruled that you had accepted the license, then you would be subject to whatever penalties that the license provides for violation when you break it. If it would work out better for you get out of the license and be charged with copyright violation, I'm not so sure a judge would allow it. Expecially, since, if you did accept the contract, it might be possible to have the contract enforced AND to sue you for copyright violation.

      --
      Life is too short to proofread.
    3. Re:GPL the whole thing is not the only option by no_code_charlie · · Score: 1

      GPL violation is copyright violation. OK, but who has the right to enforce the copyright (i.e., sue for infringement)? In general, *not* the FSF. Only the person who "authored" the infringed code would have standing to sue. What's more, that person would first have to obtain registration for his copyright from the Copyright Office as a jurisdictional prerequisite to bringing suit. MOST GPL's software developers never get around to doing this.

    4. Re:GPL the whole thing is not the only option by jedidiah · · Score: 1

      A copyright is valid from the date of creation. All you have to do is prove somehow that you created the work on or before a certain date. Publishing your work will more than suffice for this purpose.

      There are various entities that have been publishing the Linux source for quite a number of years.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    5. Re:GPL the whole thing is not the only option by no_code_charlie · · Score: 1

      - GPL violation is copyright violation. -- No, GPL violation would be breech of contract. Ah, but the breach of [the GPL] contract results in automatic termination of the license to use the GPL'd work, thus rendering the 'breacher's' use infringing. (Of course only the owner of the GPL's work would have standing to sue for infringement, and only after having secured a registration certificate for the work.)

    6. Re:GPL the whole thing is not the only option by no_code_charlie · · Score: 1

      You may have missed the point. Here it is again: 1) NO COURT has any power, authority or juridiction to entertain an action for copyright infringement with respect to a work for which a certificate of registration of copyright has not been issued by the U.S. Copyright Office. Any such action must be dimsmissed ASAP. 2) ONLY the copyright holder (i.e., the author of the work or his assignee), and in some cases, *exclusive* licensees, have standing to bring an action for copyright infringement. An action brought by anyone else must be dismissed ASAP.

    7. Re:GPL the whole thing is not the only option by no_code_charlie · · Score: 1

      What would happen to the validity of the GPL were it to be scrutinized in a court of law and found to be legally invalid? ------- Depends on what you mean by "invalid." If it were to be deemd "void" then no one would have the right to use the software that they had been relying on the gpl for the source of their right to use. Thus, unless they had some independent right to use it, their use would be infringing of the author's/owner's copyright.

    8. Re:GPL the whole thing is not the only option by jedidiah · · Score: 1

      The copyright term is 14 years too...

      --
      A Pirate and a Puritan look the same on a balance sheet.
  88. Just have to wait by Ded+Bob · · Score: 1

    I am not saying that Linux has or has not received code from SCO. I would not know. I just do not think people are remembering that it has happened in the past with copyright-stripping.

    In that case, I can see it as a misunderstanding of the BSD license. SCO code would be a lot harder to misappropriate.

    1. Re:Just have to wait by jedidiah · · Score: 1

      If what SCO is claiming to be true really is true, the violation would had to have occured BEFORE ibm got involved with Linux. That's the fatal problem with their claims.

      If this really happened, then IBM is the wrong party to sue.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:Just have to wait by Ded+Bob · · Score: 1

      If this really happened, then IBM is the wrong party to sue.

      When would IBM ever be the right party to sue? :)

    3. Re:Just have to wait by jedidiah · · Score: 1

      Yes, this really is like some stupid schmuck playing chicken with an 18-wheeler.

      IBM is ~3000 times larger than SCO.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  89. Learn to spell "its". by Anonymous Coward · · Score: 0

    Save the world from illiteracy.

  90. It's not about who wrote the code... by Dr.+Evil · · Score: 1

    ...it's about who holds the patents.

    If successful, this would be the most staggering example of innovation being stifled by the patent system. The complete abandonment of open source software for fear of patent violations.

  91. I think it's the way they're pushing the case... by TheConfusedOne · · Score: 1

    In the case of Linux they're claiming that IBM polluted the code with the SCO-gained IP. That being the case it's hard to sue Red Hat or another distro first (not to mention they're in the United Linux group) as their case hinges on proving the IBM point.

    So, they might as well shoot high right from the get go.

    Anyway this is all just a giant cry of: "Buy me NOW!!!! PLEASE!!!!"

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
  92. Re:MS Fud a long term failure. by delcielo · · Score: 1

    The reason I don't get quite as worked up about the MS Fud regarding Linux is that it's a short-term strategy at best.

    Part of that is for the well-worn reason that "Linux is not a company."

    Part of it is because today's techies and coders are tomorrow's pointy-haired bosses and project managers. Alienating us now is a strategy that will backfire bigtime down the road.

    --
    Hot Damn! It's the Soggy Bottom Boys!
  93. Open source patent licenses? by Anonymous Coward · · Score: 1, Insightful

    I doubt that open source would be completely abandoned. It would be a serious blow to the momentum of open source. And it would be a very long time before businesses would trust open source again.

    This issue is going to fuel the calls for open source patent licensing. I've seen it suggested several times before right here on Slashdot. Basically, a patent holder would license software patents for use in open source software. They could be used commercially in exchange for cross-licensing of other patents on on the same terms. It would effectively immunize open source projects against patent infringement suits. The first company to sue a big open source project over a patent would risk a countersuit on the patents of several different patent holders. As soon as they sue, they've violated the terms of the license, which requires open source cross-licensing.

  94. libc by realnowhereman · · Score: 1

    They've said that there is no infringing code in the kernel. They've said they want to arrange a payment schedule for those using Unix libraries. Does anyone else think that they might well be going after glibc?

    Have IBM done any work in glibc? If memory serves the new super-duper threads implementation had some IBM help.

    --
    Carpe Daemon
    1. Re:libc by arkanes · · Score: 1

      Apparently the GCC maintainer is employed by SCO... glibc sounds like a pretty good candidate.

    2. Re:libc by jcast · · Score: 1

      Except that gcc and glibc are completely separate animals.

      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
  95. SCO has poisoned their own well by dsplat · · Score: 2, Interesting

    There is little chance that they can win this. IANAL, so I can't speak to the question of whether their claims have a chance in court. I could argue the point of whether they make sense, but I don't want to get involved in that.

    However, IBM has the resources and the motivation to fight this. SCO's market cap is a whole lot less than IBM's investment in, and presumably revenue from, open source software. From a business perspective, it would make sense for IBM to buy SCO and release the patents to the open source community. If winning this fight would cost them more, they can do that. If winning it costs less, they can fight it and effectively disarm SCO.

    I think within a short time what we are going to see is that open source software will effectively become very safe from lawsuits. The day is coming when it will be a safe bet to use open source because you will know that it has already survived these attacks.

    --
    The net will not be what we demand, but what we make it. Build it well.
  96. Has SCO Said Where the Code Is? by Greyfox · · Score: 1
    SCO has the source to Linux, so have they pointed out any specific code that they claim is theirs? If they don't put up, I expect them to be in for a legal bitch-slapping.

    Speaking of which, didn't we have some questions for them to answer? Maybe they're too busy with their thriving business... more likely the crickets are just too loud there for them to concentrate.

    How about an slashdot community hostile takeover and subsequent firing with extreme prejudice of employees and dismantling of the company? Lets apply the /. effect to the real world!

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    1. Re:Has SCO Said Where the Code Is? by mark-t · · Score: 1
      SCO has the source to Linux, so have they pointed out any specific code that they claim is theirs?
      No.
      If they don't put up, I expect them to be in for a legal bitch-slapping.
      I agree. I expect a plethora of people wanting to be first in line for that.
      Speaking of which, didn't we have some questions for them to answer?
      Yes. I've been wondering the same thing.
      Maybe they're too busy with their thriving business... more likely the crickets are just too loud there for them to concentrate.
      Eloquently put. The writing is on the wall for SCO unless they cough up their so-called "evidence" PDQ.
      How about an slashdot community hostile takeover and subsequent firing with extreme prejudice of employees and dismantling of the company? Lets apply the /. effect to the real world!
      Nope... SCO seems to be doing a fine job of shredding themselves to pieces all by themselves. Why bother?
  97. judas by moojin · · Score: 2

    jesus had his judas and now so does the open source community. the big question is, will the betrayal of SCO through the lawsuit be the catalyst for something big for open source? you must admit sco has unified the open source community against it, much in the same way microsoft had in the years before. only if we could use this unity to further our cause.

    --
    Why did I lurk so long before registering for a Slashdot account? I could have had a Slashdot ID of less than 100000.
  98. patent by Anonymous Coward · · Score: 0

    Why even attempt to set these mindless drones straight? These brainwashed hordes wouldn't be able to tell you the difference between a patent, trade secret, trademark, copyright.

    Its all evil.

    Except of course for the IP that their employers own that allowed for the funding to pay their salaries. Or of course, the IP that the slashdot advertisers own.

  99. Re:I disagree by tomhudson · · Score: 1
    The tone in much of the main-line media was that IBM would probably buy out SCO. That IBM has, in essence, said "go fuck yourself" to SCO is news, and as such deserves to be reported.

    It's also a good thing for both the linux community, and open source as a whole. Lighten up, dudes - if IBM had just bribed^H^H^H^H^H^Hbought out SCO, we wouldn't have a chance to resolve/test some issues (GPL, etc.) in the courts.

  100. Balmer by Anonymous Coward · · Score: 0

    Balmer is quoted as saying something to the effect, "See, you dont know who's writing your OSS software."

    When you're forced to live in their world, you *do* know who it writing your code, and is unfortunate, as time and experience have proven the case.

  101. Code Audit by skroz · · Score: 1

    Since SCO has thusfar been unwilling or unable to produce evidence of or even point to any instances of stolen code, has anyone at RedHat, IBM, or anyone else performed a code audit in an attempt to locate any code fragments that might belong to SCO? It seems to me that this would be a prudent thing to do.

    --
    -- Minds are like parachutes... they work best when open.
    1. Re:Code Audit by geekee · · Score: 1

      Actually SCO claims their code has been copied verbatim and used in Linux. See here.

      --
      Vote for Pedro
  102. Re:I know that there isn't SCO code in Linux becau by CoolVibe · · Score: 1
    Well, there is some caldera code in the Linux kernel...

    I did some grepping:

    coolvibe@azazel linux $ grep -nri Caldera *
    CREDITS:2416:E: sp@caldera.de
    CREDITS:2418:S: Caldera (Deutschland) GmbH
    Documentation/Configure.help:28517:# LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
    Documentation/networking/tlan.txt:1:(C) 1997-1998 Caldera, Inc.
    Documentation/smp.tex:27:The author wishes to thank Caldera Inc. ( http://www.caldera.com )
    Documentation/sound/CMI8338:56: b. Caldera OpenLinux 2.2
    arch/x86_64/kernel/smpboot.c:13: * Original development of Linux SMP code supported by Caldera.
    arch/i386/kernel/smpboot.c:12: * Original development of Linux SMP code supported by Caldera.
    drivers/net/slip.c:41: * from Jim Freeman's <jfree@caldera.com>
    drivers/net/tlan.c:8: * (C) 1997-1998 Caldera, Inc.
    drivers/net/tlan.h:10: * (C) 1997-1998 Caldera, Inc.

    [a lot snipped because the /. lameness filter started complaining]

    Some of the original work on Linux SMP was done by them. Of course they put that in (donated the code) themselves, so there's nothing to cry "Wolf" over anyway...

  103. You must be Mr. Rip Van Winkle or something... by Anonymous Coward · · Score: 0

    What if they do have a genuine grievance. I'm not trying to be a troll or flamebait, just honestly curious. What impact would this have on GNU/Linux? Would people honor SCO's claims if they're proven right?

    [sarcasm mode on, truth mode on]
    Since when in the past 100 years (or longer) in this country, did having a valid and genuine grievence actually really mean anything in court anymore?
    [sarcasm mode off, truth mode still on]

  104. advice to IBM by 10am-bedtime · · Score: 1
    initially i was going to say, "just ignore the noise".

    but, let's be creative here... you're IBM, you're a big multinational company w/ relatively good social standing (we can forgive the wwii profiteering if you handle the next few years correctly), you're involved in hardware, software, services, etc., the money flux through your accounting department keeps people employed and communication flowing between different world cultures, you have the nads to support the people who do the work. ok, fine.

    because you are in such a position of power, and transnational in the extreme, you might as well take on the mantle of "world leader" and DTRT for everyone: buy this little company for peanuts and put its management to work undoing all the petty fecal material it and its ilk have been spewing. develop a "ministry of transparency" whose primary task is to reflect upon FUD ("hey we're experts") and educate people on how to recognize the techniques. nothing is more persuasive (not to mention entertaining) than a reformed FUD-monger -- it would be like those shows where "magicians reveal their secrets".

    why is this preferable to the world leader? that's for you to figure out; i'm just giving implementation advice here. :-)

  105. bleh by Anonymous Coward · · Score: 0

    I've said it once, i'll say it again.

    1) SCO as a company isn't worth that much..

    2) All us Open-Source advocates could probably all chip in a few bucks and BUY SCO ourselves. Then we could legitimately opensource thier IP and put an end to this bullshit.

    phaeton

  106. IBM holds patent no. 42 by totallygeek · · Score: 2, Funny
    It is the patent to the secret of life, the universe, and everything.

  107. enlighten me by wildcard023 · · Score: 1


    Maybe I'm way off here, but here's the way I see it. IP ownership falls under either:


    1) a Patient

    2) a Trademark

    3) a Copyright


    Obviously #2 is right out. This has nothing to do with trademarks.


    If this is a patient issue, hasn't the 17 year limit expired already? This would mean that the code must have been written in the ~1986 region.


    Now according to: this, AIX was first written it 1986. So patients are right out because of the expiry dates.


    So that leaves copyrights. Copyrights protect (sorry RMS) specific works, not the ideas they are based on. I would be amazed if the code from the 1986 version of System V Unix copy be cut and pasted into the Linux kernel directly. I haven't seen the SysV codebase, but that's just silly.


    So tell me where I'm wrong. Where does SCO say it has a leg to stand on?


    --

    Mike

    --
    -- Mike wildcard@illuminatus.org
    1. Re:enlighten me by penguinlust · · Score: 1

      I have seen pretty much every System V source base up to about 1994. I would seriously doubt there is a single line of code cut and pased into the Linux kernel sources. With so many lines of code there will be many that are the same. They will of course mostly consist of "contihue;", "break;", "}", "{", and other such stuff. There will also probably be a few such as "for (i=0' i What I suspect is that SCO is claiming such code as the JFS, which I beleive was create in whole by IBM" is part of the UNIX code and under SCO license. If this is it then it should be interesting to see what the courts think about this. I have seen other licenses that have been interpreted as including all other pieces ever used with it.

    2. Re:enlighten me by Anonymous Coward · · Score: 0

      The 14 year limitation on copyright has expired already, also.

    3. Re:enlighten me by David+Gould · · Score: 1

      There's (at least) one other type of IP separate from the ones you listed: "trade secrets". If reading the actual article is too much trouble, try reading the headline:
      IBM has denied SCO Group's allegations that it misappropriated Unix trade secrets, but Big Blue isn't giving hints about what its eventual strategy will be for battling the lawsuit.
      Now, I only play the part of a lawyer on Slashdot, but as I understand it, a trade secret is sort of "the opposite" of a patent: instead of publishing the information openly but having a monopoly on the right to use it (even if someone else "really does" develop the same thing independently), you keep it secret, figuring that others can't copy what they don't know, but this is only good as long as the secret stays secret. You're protected against having it stolen ("misappropriated") through, e.g., corporate espionage, NDA violation, etc., but once it gets out in the open legitimately (e.g., if someone else develops it independently, or you carelessly disclose it to someone not under NDA), all bets are off.
      --
      David Gould
      main(i){putchar(340056100>>(i-1)*5&31|!!(i<6)<< 6)&&main(++i);}
  108. The argument by totallygeek · · Score: 1
    Oh, I always thought the fight was because it was supposed to be GNU/SCO....

  109. Question by t0ny · · Score: 1
    I have a question. Since they are claiming that the Linux kernel contains some of their Unix code, does that mean that Linus is responsible for putting it there, and SCO is suing IBM because they ,unlike most companies which use Linux, have money?

    I guess they could also sue Oracle, but it seems Oracle's continued cash flow depends upon suing Microsoft, but that would basically be the vulture eating the jackal. I dont know why redundant bottom-feeding strikes me as funny.

    Perhaps SCO is also hoping IBM will continue the trend of buying out companies that file lawsuits against them...

    --

    Manipulate the moderator system! Mod someone as "overrated" today.

  110. 10 lines of code? by mark-t · · Score: 1
    Okay, if SCO can give it a number like this, it's pretty clear they have a very specific example of what they are allegating.

    Does SCO have proof that IBM was the source of these lines of code?

    More generally, do they even have proof that these lines of code were added after IBM started being directly involved in Linux?

    Thanks to version control, we can determine exactly which lines were added, who added them, and exactly *when* they were added. So it would seem that such evidence should be trivial to obtain for either side.

    I think it's time for SCO to either put up, or shut up on this issue. They allegate that the open source community is too incompetent to have made Linux as powerful as it is without misappropriating SCO's IP? I defy them to prove it!

    This whole issue makes me so flippin' mad, I can hardly type.

    Crap. I need a drink.

  111. I don't understand by pclminion · · Score: 1

    Why doesn't IBM just do us a favor, buy SCO, dissolve it, and end the whole problem?

    1. Re:I don't understand by mark-t · · Score: 1
      To do that would be an implicit admission of guilt to the Linux community.

      I'm betting that SCO doesn't actually have a single shred of proof that IBM inserted the code in question into Linux. In fact, I'm betting that the code that they question was already part of the Linux kernel before IBM began its involvement with Linux. This is trivial to prove one way or the other, so the fact that SCO is being so hush-hush about the details only lends further discredit to their claim.

      The allegation that SCO is making, that the open source community is too incompetent to make enterprise-grade software without resorting to theft is at its best slanderous, and if SCO is unwilling to provide any evidence of their allegation, I fail to see why they should even be given the time of day, let alone be bailed out of financial trouble by buying them.

    2. Re:I don't understand by SuiteSisterMary · · Score: 1

      I don't think it would be an admission of guilt; it would be a wonderful example of creative problem solving.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
  112. Banned 4 Life by tmuller · · Score: 1

    Never again will I use or attempt to think of using a SCO product ever again....

  113. Re:Ballmer Misquoted by tigheig · · Score: 2, Insightful

    Ballmer actually said: customers will never really know who stands behind this product.

    The EULA's that I've seen for most commercial software products (including Microsoft's) clearly state that they're not guaranteed to do anything, and are not guaranteed to not harm your system or you. It seems quite clear that the difference in this area between commercial OS/software releases and Open Source is that, with Open Source you never know who will stand behind the product, and with commercial software you will know that nobody stands behind the product.

    At least with the former I have a chance that someone, somewhere will stand behind their product.

  114. The Code in question by senrik · · Score: 1

    I think the code SCO is claiming relates to the following Characters:

    `1234567890-=qwertyuiop[]\asdfghjkl;;'zxcvbnm,./ ~! @#$%^&*()_+QWERTYUIOP[]\ASDFGHJKL;'ZXCVBNM,./

    So therefore all linux source code, in fact belongs to SCO. So Pay up.

    In fact, just by typing you now owe SCO $$$..

    --
    "the difference between myself and a madman is that I am not mad" -Salvadore Dali
    1. Re:The Code in question by iggymanz · · Score: 1

      I think there could be some prior art for some of those; I remember seeing at least half of the characters in Cambell's alphabet soup when I was a kid.

  115. Re:More News...Splunge by Anonymous Coward · · Score: 0

    That's 2 month old FUD here is something more current.
    Senior Vice President Chris Sontag told MozillaQuest Magazine
    "We're not talking about the Linux kernel that Linus and others have helped develop. We're talking about what's on the periphery of the Linux kernel"

    Speaking sides both mouth out of.

  116. Re:I steal from the RIAA why not steal from unix by 0x0d0a · · Score: 1

    Because the RIAA has the rights to good music, and SCO the rights to grotty, bad code.

  117. North Korea and SCO by meclamar · · Score: 1

    Does any of this remind anyone of the situation with North Korea? One rogue nation (translation: company) lashing out at everyone trying to solve its problems...

  118. The problem is that it's worked before by 0x0d0a · · Score: 1

    The problem is that ever since Caldera won the DR-DOS suit against MS, and made $150M or so, it's had the idea that the way to make money is to sue OS developers rather than to actually produce a good product.

    And actually, they *used* to be useful -- siphoning money off MS is fine by me any day of the week. Attacking Linux development by trying to run off with the money that IBM is putting into Linux (and giving half to lawyers instead of software engineers) is less attractive, however.

  119. $40.2M? for Caldera? by theonetruekeebler · · Score: 3, Funny
    That's lunch money for IBM!

    Buy the company, declare all its IP community property, fire every single employee, burn their buildings, loot their coffers, trample their crops and sew their fields with salt.

    --
    This is not my sandwich.
    1. Re:$40.2M? for Caldera? by 7dragon · · Score: 1

      The word is SOW not sew.

      You makin' a fuckin jacket out of salt?

    2. Re:$40.2M? for Caldera? by theonetruekeebler · · Score: 1
      Yeah. I feel like an idiot making that mistake, on account of I use both those words really often.

      Also, you misspelled either fuckin' or fucking.

      --
      This is not my sandwich.
  120. How significant can this be? by 0x0d0a · · Score: 1

    I can't even figure out *what* could possibly be copied. This isn't a web browser. It's a kernel. You can't just swipe the scheduler from a completely different kernel and drop it into place. It'd be far harder than just writing the thing yourself.

  121. Long term by 0x0d0a · · Score: 1

    The problem is that's obviously what Caldera *wants* to have happen. IBM wants to, as a long term policy, discourage dying companies from suing them for any IP they might be able to work with.

    Intel has similar rules -- they have crosslicensing agreements, and flat fees of up to something like $100K for patents rights, but always fight IP issues other than that. As a result, you have to be a real idiot to go after Intel on IP grounds, because they *will* fight tooth and nail, and they have a lot of resources to pour into said fight. If IBM and Intel didn't maintain such policies, everyone would see them as cash-bloated companies and try to swipe a piece of the pie.

    1. Re:Long term by theonetruekeebler · · Score: 1
      Okay, so run up Caldera's legal bills into the millions, let public and investor opinion drive their stock value into the pennies, then buy them out and destroy them all utterly.

      Wal-Mart aggressively defends itself against every single profiteering lawsuit filed against it. They are the single most sued entity in the U.S., apart from the U.S. itself. There are seminars on suing Wal-Mart.

      --
      This is not my sandwich.
  122. BullShit! by 3seas · · Score: 1

    "IBM said it's seeking a jury trial for the case, but Ferrell said a court date for trial likely won't come for about two years."

    And some claim by IBM that SCO is trying to hold up and cause delays in teh development commuinty of linux.....

    IBM has NO say over what the linux development community does or doesn't do!

    IBM seems to be doing nothing more here than effort at helping to hang a threat over the Linux development community for the next two years.

    Do we all really need to be reminded of all the effort to bust MS and where years and years of that has gotten anyone expecting justice?

    IBM does not own the linux kernel nor do they have authority over the developers of GNU/Linux.

    Perhaps what needs to be done is a review over any source code IBM has contributed to the GNU/Linux source base.

    1. Re:BullShit! by jcast · · Score: 1

      Calm down, take a deep breath, and try again, please.

      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
  123. Caldera by princeofweasels · · Score: 1

    I wonder what the possibilty that this so called stolen intellectual property was put in by Caldera. If so would they sue themselves? Maybe before they did that they'd just buy themselves out....

  124. SCO by Anonymous Coward · · Score: 0

    SCO Used to own Unix(tm).
    Bell Labs made a better one
    Berkly Systems care of UC Berkly makes a even better one. what's the problem here?

  125. Never Pay Ransom by Anonymous Coward · · Score: 0

    No, they can't buy SCO. That would invite every dying dot-com to sue IBM in the hopes of getting bought out.

  126. Re:Microsoft will be next. BEEN THERE DONE THAT by Anonymous Coward · · Score: 0

    A few years back a small company had the rights to the name 'internet explorer'. A legal battle began for the brand, and the small company lost due to insufficient funds to continue the legal battle. MS offered 50k to buy it out.

    If you are going in a legal battle against MS, either you 'are' a lawyer and have nothing better to do with your time, or have deep pockets to finance a loooooooong trial with years of legal fees. By the time the trial ends, you product is obsolete.

  127. Mod parent up! by mark-t · · Score: 1

    Short, sweet, to the point, and so utterly and profoundly true.

  128. Biggest problem with that... by Anonymous Coward · · Score: 0

    Patenting is expensive. People might want to code for free but probably not to pay for it.

  129. GPL is enforced all the time... by Anonymous Coward · · Score: 0

    http://www.gnu.org/philosophy/enforcing-gpl.html

  130. better still... by sacrilicious · · Score: 1
    Doesn't really mean anything. You could have a company with each share not valued as much but with many shares issued, or with few shares but each share valued highly. Market capitalization is much more useful

    It's possible to have a big market cap on a low margin business, so it might be even better to know net revenue. But really the story of a publicly held company is better divined from things like how saturated its chosen markets are, what its competition is, how easily it can absorb risks when diversifying, and whether it holds a degree of monopoly (monopolies can be though of in degrees by quantifying the cost of barriers to entry).

    (This might be offtopic but) I find it interesting to note the differences between assessing a public and a private company. Consider a privately held mom-and-pop deli that never expands, and makes enough money on a sustained basis to pay its employees, cover the cost of a decent lifestyle for the owners, and allow them to put away money for retirement and their kids' college. In the world of private companies this is a success. But in the world of public companies, this is a failure; there's no ever-growing profit to be distributed across the pool of stockholders. Whereas in a public company, a massive layoff can be considered a great boon and send stock prices up... but is an abysmal failure in the mom-and-pop scenario.

    --
    - First they ignore you, then they laugh at you, then ???, then profit.
  131. Why they can't do that. by mindstrm · · Score: 1

    If you purchase controlling interest in a company, the board still cannot DESTROY the company, and any shareholder value that went along with it. They have a DUTY to the shareholders to maximize shareholder value.

    That's why public companies often don't "do the right thing" and why you don't just buy one up and close it down... becuase the shareholders will SUE you for destroying their product.

    Remember, even if IBM buys a controlling interested in SCO, that doesn't make it the outright owner. Control and ownership are two different things.

    1. Re:Why they can't do that. by jcast · · Score: 1

      Which is why they have to spend the $40.2M to buy the whole thing. Either that, or defend against any shareholder lawsuits. I mean, sure, they may be in the wrong there, but they can drain the other shareholders dry if they want to.

      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
  132. Lawsuit DOS by Anonymous Coward · · Score: 0

    What would be really cool is if Lunix devs were to each sue SCO *individually* from their respective local courts. That would be really, really cool.

  133. SCO Marketing by Anonymous Coward · · Score: 0

    This is just SCO marketing looking for publicity. Just got spammed by one of their commercial spammers ... looks like a marketing ploy.