Slashdot Mirror


SCO Taking Linux Discussion To Japan

levin writes "EETimes is carrying a new story about our good friend Darl McBride, CEO of SCO. His latest escapades include a trip to Japan in response to the CE Linux Forum initiative undertaken by several big-name Japanese tech firms such as Sony and Toshiba. He's putting his famous tainted code dog-and-pony show on parade, trying to influence some of the major CELF founders."

106 of 463 comments (clear)

  1. Too Bad... by JoeLinux · · Score: 4, Funny

    ....I guess that means he'll have to accept his AssHat Award by proxy.

    1. Re:Too Bad... by PD · · Score: 2, Informative

      Invented on fark.com. They are trying to get the word into common usage, and I think they succeeded. I even heard it on TV.

    2. Re:Too Bad... by Trigun · · Score: 5, Informative

      It probably was popularized by Clint Eastwood in 'The Outlaw Josey Wales' when he said, "I'll kick you so hard, you'll be wearing your ass for a hat".

      Although, UrbanDictionary.com says:

      5 definitions found.

      asshat

      One who has their head up their ass. Thus wearing their ass as a hat. Asshat

      asshat

      One who enters into a new environment without taking the time to learn any of the social rules of the place. Then they promptly make pretty much every social gaff you can imagine this side of shitting on the dinner table.

      You know, a moron.

      Scrappy Doo is one of the few existing examples of an animated asshat.

      asshat

      a person who has no common sense or just plain stupid.

      Some of the people on notPopular.com are asshats.

      asshat

      exclamation said when being woken up for the third time by your drunken roomates

      i hope this asshat likes the taste of concrete

      asshat

      1. A hat worn by a drunken fool, or ass.

      2. A foolish person, as one who would wear an asshat.

      1. At the party, Jon made a fool of himself when he donned his asshat, the lampshade.

      2. By bothering everyone at work, that asshat has made a real fool of himself.

      Hope this helps...

    3. Re:Too Bad... by Megane · · Score: 2, Informative
      Ano gaijin wa aho desu ka?

      Iie, oshiri boushi to iimasu ne.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    4. Re:Too Bad... by gcalvin · · Score: 5, Insightful

      The EETimes article makes several mentions of SCO's "Unix patents", as if patent infringement were at the core of this controversy. I was under the impression from the other articles I've read that the issues were 1) breach of contract (with respect to IBM) and 2) copyright infringement (with respect to everyone else, including the 1500 recipients of letters from SCO). This is the first mention I've heard of patents. Is it really about patents, or is Charles J. Murray (the article's author) deserving of an AssHat Award too?

    5. Re:Too Bad... by rworne · · Score: 4, Funny

      Ano gaijin wa aho desu ka?
      Iie, oshiri boushi to iimasu ne.


      I commend your use of keigo but it isn't totally warranted in this case.

      Ano yatsu aho ka?
      (Said to friend)

      Chigau, ketsu-boushi da.
      (oshiri is polite form like "bottom" or "butt". Ketsu is more vulgar, closer to the meaning "ass". I've never heard Japanese refer to the sphincter as ohshiri-no-ana, only as ketsu-no-ana, anaru, or komon)

      If you are wondering where I picked most of this up, you get to learn a lot in Akihabara watching some kids teach Sega's Seaman to talk in Japanese.
      --
      I tried every decent and legal way I could think of to resolve the issue w/the business before I rented the chicken suit
  2. Does anyone out there still use SCO Unix? by ACK!! · · Score: 4, Interesting

    For what?

    I remember we use to use this EMC datamovers on the controller server that was hooked up to the things. Besides that, I knew of only one other company that used them.

    --
    ACK /ak/ interj. 2. [from the comic strip "Bloom County"] An exclamation of surprised disgust, esp. i
    1. Re:Does anyone out there still use SCO Unix? by carpe_noctem · · Score: 5, Funny

      Yeah, I use SCO as my server platform, and WinXP for my desktop. I'm a /. rebel, baby!

      --
      "Quoting famous computer scientists out of context is the root of all evil (or at least most of it) in programming." - K
    2. Re:Does anyone out there still use SCO Unix? by Surak · · Score: 4, Informative

      FilePro. We use it for a FilePro database that runs our entire accounting operations. I dunno why. Maybe I should mention to them that FilePro runs on Linux now. (duh).

    3. Re:Does anyone out there still use SCO Unix? by Jeremy+Erwin · · Score: 5, Funny

      Just finished converting my home's systems from Debian to OpenServer. Cost me a bundle, but I figure it's important to support organizations that defend IP rights.

    4. Re:Does anyone out there still use SCO Unix? by cdrudge · · Score: 2, Informative

      Yes. Over 700 servers mainly on OpenServer 5.0.5 and 5.0.6.

    5. Re:Does anyone out there still use SCO Unix? by Xerithane · · Score: 3, Funny

      FilePro. We use it for a FilePro database that runs our entire accounting operations. I dunno why. Maybe I should mention to them that FilePro runs on Linux now. (duh).

      Wow, I thought we were the only bass-ackwards organization that did that. We're trying to migrate away from FilePro, as it's retarded in ways that makes the short-bus riding childrens parents cringe in horror and shock.

      We regularly get to make SCO jokes, though. Still not any form of consolation for having to have programs actually run on that shit.

      --
      Dacels Jewelers can't be trusted.
    6. Re:Does anyone out there still use SCO Unix? by sheddd · · Score: 4, Funny

      Our point of sale system is running on SCO. Replacing it this winter woohoo :)

      With a M$ system :(

      I do like to bash Microsoft but sometimes their products make sense.

    7. Re:Does anyone out there still use SCO Unix? by packethead · · Score: 5, Informative

      Apprently some still do. A lot of bricks and mortar type companies run their manufacturing systems on Openserver. They are generally low-tech firms to begin with and have no plans to budget for any upgrades, nor should they - for what they do.

      Now. Any company that requires, HA/failover/performance, etc. Needs to *not* be running OpenServer. Netconfig requires a re-link and reboot anytime you breathe on it. THe package manager is this thing called 'custom', which is anything but customizable. SMP? Gigabit Ethernet? Journalized filesystem? I think not! Maybe the Military can use it, considering that Colonel Panic and Major Re-install are part of the core functionality.

      UnixWare is better, but it ain't Solaris.

      --
      .sig
    8. Re:Does anyone out there still use SCO Unix? by shadowbearer · · Score: 3, Interesting

      The Ace Hardware down the street still uses SCO OpenServer Release 5 for their POS systems. I was talking to the owner last week and he showed me their new POS they are phasing in....running Windows XP. He didn't have very kind words for SCO tech support.

      SB

      --
      It's old. The more humans I meet, the more I like my cats. At least they are honest.
    9. Re:Does anyone out there still use SCO Unix? by WeaponOfChoice · · Score: 2, Funny

      Nothing funny about that, I'm in exactly the same boat. For some reason management has the idea that a system that lasts for 15 years without upgrades is a *GOOD* thing...

      --


      It's not that I'm Anti-American - I'm Pro-Freedom
    10. Re:Does anyone out there still use SCO Unix? by Badanov · · Score: 2, Funny

      HEY!! I rode the short bus in high school!

      --
      Dawn of the Dead
    11. Re:Does anyone out there still use SCO Unix? by drinkypoo · · Score: 4, Insightful
      Lots of people still use SCO Xenix, let alone Unix, for things like point of sale and proprietary management systems such as for delivery tracking. Probably the biggest company doing the latter, ADAQ, was purchased by Mobile Information Systems which has a Sun/Solaris package to do the same thing, with GUI tracking of GPS-enabled trucks and so on, so they have probably transitioned just about everyone off the old package, and there's probably like two people supporting the old users, and no one issuing fixes.

      The thing is that these mom and pop operations dropped a few grand on a 386, a five user Xenix license, and this software package and as long as it works, they'll keep using it. Not to mention it's a minicomputer, they just get to use dumb terminals which are available at garage sales and whatnot, rather than having to have PCs. The package does everything, including financials and such, so why use something else? When the hardware fails and they find out they can't run 386 Xenix on modern hardware and they need a SCO license, then they decide they might as well buy a used Sparc or something, and that's the time to transition. However I do recall assisting one customer on transitioning to SCO Unix on a Pentium 2 instead of going to the other product. Poor bastard.

      However the point remains that if it ain't broke, why screw with it? If you're trying to make any kind of customizations, then you would like a much better OS, especially something better-supported. If you're just using something for a turnkey system, then you want something with low overhead and high stability, and while SCO Unix doesn't really fit the bill there in either category, good old SCO Xenix was amazing. Unix on a 286 in 1mb of ram, installed in 20mb of disk is nothing to sneeze at. Of course there are older examples of Unix on even lesser hardware, and there's always Minix but hell, it's almost as restricted as Xenix :P

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  3. What is a "Central Module"? by Dr.+Smeegee · · Score: 5, Insightful

    "I saw what appeared to be a word-for-word copy of about every third line of code in the central module of the Linux kernel," said Enderle of Giga Information Group, who viewed the alleged code violations two weeks ago. "The lines of code contained typos, misspellings and even copyright disclaimers. It appeared to constitute a violation of the license."

    Where can I get me one of these central modules?
    1. Re:What is a "Central Module"? by Anonymous Coward · · Score: 5, Insightful

      Every third line of code?

      Every third line of code???

      So, we're to believe that a lazy programmer, rather than go to the trouble of writing the whole thing himself, designed and wrote 2/3ds of it and went to the trouble of inserting stolen code in the gaps? With enough precision to get a working kernel?

      Wait... is every third line a }?

    2. Re:What is a "Central Module"? by spacefrog · · Score: 2, Funny

      Why do you think they call it a monolithic kernel?

      Sorry, couldn't resist. I'll go back to my corner now.

    3. Re:What is a "Central Module"? by .com+b4+.storm · · Score: 2, Funny

      $ modprobe central

      There ya go :)

      --
      "Wow, you're like some kind of superhero able to ward off happiness and success at every turn."
      -- Ryan Stiles
    4. Re:What is a "Central Module"? by ChangeOnInstall · · Score: 3, Funny

      said Enderle of Giga Information Group..."The lines of code contained typos, misspellings..."

      You sure? It compiles fine for me.

      --
      What has *science* done?!? -- Dr. Weird (ATHF)
    5. Re:What is a "Central Module"? by Fly · · Score: 5, Funny

      I think he meant "typos" like src, dest, byte, sprinf, and char. I mean, some of those aren't even words, dude.

      --
      end of line
    6. Re:What is a "Central Module"? by Fly · · Score: 4, Funny

      sprintf even, sorry for the typo

      --
      end of line
  4. More icing on the Cake... by jdh-22 · · Score: 5, Insightful

    Why do we keep posting articles that we know are only to impose FUD on the Linux/Open source community?

    --
    Every Super Villan uses Linux.
    1. Re:More icing on the Cake... by missing000 · · Score: 5, Insightful

      Why do we keep posting articles that we know are only to impose FUD on the Linux/Open source community?

      Because it is very useful to have an informed community for the media to talk to.

      You have to remember that the SCO fight is not only in court, but also largly in the court of public opinion.

      If a user is contacted by the press, it is incredibly advantageous for them to be well informed of the allegations as well as the actions of the parties making them.

      Even if we win in court, which I for one assume we will, the damage to linux adoption could be enormous if we come off as unknowledgeable and ill-prepared.

      If, on the other hand, linux users are seen as well prepared and educated, we could even stand to make gains in the business community.

      This SCO stuff is anything but trivial.

    2. Re:More icing on the Cake... by Gaetano · · Score: 3, Insightful

      I think its important to be well informed about these things so that we can fight it. Most slashdoters know the score but people reading the articles that slashdot links to, such as this one, may not know the score. Those people may be managers and have questions so perhaps they come to their sysadmin, a slashdoter, and since he is well informed he can fight the FUD.

      Otherwise there is a vaccume created by the FUD and we don't want it to be filled with yet more FUD, so we have to fill it with the trueth.

    3. Re:More icing on the Cake... by Delirium+Tremens · · Score: 3, Funny

      FUD means "search the FUcking web, Dude".
      Oh wait, wrong one.

    4. Re:More icing on the Cake... by GoofyBoy · · Score: 4, Insightful

      >If, on the other hand, linux users are seen as well prepared and educated, we could even stand to make gains in the business community.

      Actually, thats what Programming/OS/CPU wars start. One group thinks they know more/their facts are "more" right.

      To an outsider, you risk the chance to look like a shallow individual who seems to take delight in arguing petty details.

      Just wait until the facts of SCO case are fully public.

      Note:this is an article about a trip the CEO made to Japan. Is there really anything new here?

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    5. Re:More icing on the Cake... by stephenry · · Score: 2, Insightful

      Eventually this mess will come to pass. Two things are certain: Linux cannot be disinvented, it exists -today- as a viable alternative for everything from embedded systems to mainframes; secondly, no one can claim ownership over it. What this means is that even though, in the worst case, the SCO suit may be successful in FUDing Linux in the short term, once this is discredited, Linux will still exist. Not only that, but it is improving exponentially. Whether companies switch to it, over their current proprietry OS, today or tomorrow, it will happen; and their is nothing SCO, or anyone else for that matter can do about it.

    6. Re:More icing on the Cake... by missing000 · · Score: 2, Insightful

      >If, on the other hand, linux users are seen as well prepared and educated, we could even stand to make gains in the business community.

      Actually, thats what Programming/OS/CPU wars start. One group thinks they know more/their facts are "more" right.

      How's that again? I don't think a positive public image has ever been started by a Programming/OS/CPU war. Becoming a good advocate for your cause can hardly be a bad thing.

      To an outsider, you risk the chance to look like a shallow individual who seems to take delight in arguing petty details.

      Nope. All I was saying is you need to know what to say if you become involved. That's all. I hear uninformed people give opinions on things they know nothing about all the time. All I'm advocating here is a little better signal to noise ratio.

      Note:this is an article about a trip the CEO made to Japan. Is there really anything new here?

      Well, if you had read the article, you would know it has little to do with a trip to Japan, and a lot to do with scare tactics to try and dissuade electronics manufacturers from using linux.
      In my book, that that type of behavior is occurring is something valuable to know.

    7. Re:More icing on the Cake... by Tony-A · · Score: 2, Insightful

      It's also important to be able to aim someone at Slashdot so they can pick up on what is current without having to search the archives.
      Old story rolls off the front page.
      New story rolls onto the front page.
      While there's a storm in progress the storm tracking stays up. If there's nothing new to be said, then simply reiterate the old.

    8. Re:More icing on the Cake... by shadowbearer · · Score: 2, Interesting

      Mod parent+ up.

      It's very important that Slashdot stays on top of this, so that people in the IT world who *are* following it know that we are very, very seriously concerned about what is going on (and seriously pissed off).

      This cannot be a fly by night sort of thing. It has to be, and will be, fought to the death. SCO's death. Hopefully any other companies out there who consider these sort of public FUD tactics will have second thoughts after this is all over. (I'm NOT mentioning any names, they know who they are)

      The power of the linux community is not in it's lawyer division, nor even in it's programming expertise; it's in the huge number of users who believe that Open Source Software can and does work. If that sounds religious, so be it (and you can kiss my shiny metal ass, Enderle)

      SB

      --
      It's old. The more humans I meet, the more I like my cats. At least they are honest.
    9. Re:More icing on the Cake... by Bored+Huge+Krill · · Score: 2, Interesting
      when you say most people who see the code, to whom are you referring? Maybe I missed it, but as I recall only two people have seen the code, namely Laura Didio and Rob Enderle (apologies if I got the spellings wrong). Those two get quoted over and over again, to give the apparent impression that lots of people are examining the code. They aren't. There's only the two people.

      More to the point, the comparison in question raises some genuine concerns, and looks very much like showmanship rather than a balanced analysis. Like:

      1. Neither of the two analysts are experts in the field.

      2. The two analysts were shown limited and carefully chosen code segments, selected by SCO - see also #1. It isn't difficult to present a compelling case to a non-expert based on selections of a few hundred lines of code from a code base of that size.

      3. SCO hasn't demonstrated the provenance of the code in question. Merely showing similarity doesn't help.

      4. The accounts of the analysts themselves raise questions. All of the "lines of code" referred to with similarities such as "copyright messages", "typos" and "misspellings" doesn't sound like lines of code, rather comments. Something kind of funny here. Not to mention, and this is very important, whose copyright message? If there is a matching copyright message in the SCO code base and the Linux kernel, and the code is proprietary, it seems inconceivable that it would have been checked into the kernel tree without anybody noticing.

      5. Oh, yes. Which kernel tree is this supposed to be in?

      6. Why hasn't SCO told us answers to any of these already? #5 is a particularly important one, btw

      I could go on. There's many more questions here. The point being, repeated quotes from two analysts under the circumstances is hardly conclusive. I guess we'll all find out eventually.

    10. Re:More icing on the Cake... by Ian+Lance+Taylor · · Score: 2, Informative

      I saw the code, and I didn't say that their claims aren't FUD. I said it wasn't clear, and that the one piece of allegedly copied code they showed me proved little. See my writeup at the Linux Journal or on my own server.

    11. Re:More icing on the Cake... by fireman+sam · · Score: 2, Funny

      >(I'm NOT mentioning any names, they know who they are)

      Why not, don't you know tip 3 of the karma whoring for dummies:

      3. if you mention Microsoft if a post you automagically get a +2.

      If you write it with a $. ie Micro$oft you can even get more.

      Micro$oft can also be written simply as M$.

      --
      it is only after a long journey that you know the strength of the horse.
  5. where next after Japan by Tumbleweed · · Score: 2, Funny

    I think he should take his show on over to Iraq - you don't wanna let them violators get a foodhold there!

  6. The Headline Makes it seem like..... by Dr+Reducto · · Score: 3, Insightful

    The headline makes it seem like they are trying to get as many countries to discredit SCO's claims, before they get there.

  7. Here... sign this. by tbase · · Score: 4, Interesting

    "McBride, who is fluent in Japanese, will visit with several founding members to show them code samples in which the Linux open-source operating system allegedly violates SCO's Unix patents, said an SCO spokesman."

    I wonder if he's dumb enough to think they'll sign a non-disclosure?

    --

    666-607: 6th floor apartment of the beast
  8. Explanation by JoeLinux · · Score: 2, Informative

    It's a term borrowed from fark.com meaning someone who is acting stupid/idiotic/moronic/ass-holish.

  9. We are done with SCO. by bazik · · Score: 5, Funny

    We had two Compaq Proliant servers at work, running SCO Unix. We reinstalled them with Linux three weeks ago and sent back all SCO CD's, handbooks etc. to SCO with a little note that we dont want to use Software from a Company which can't write good code and sues those who can.

    Curious why we didn't receive a response yet ;)

    --


    --
    One by one the penguins steal my sanity...
  10. Re:Just a general question by quantaman · · Score: 2, Informative

    Why is it that articles that mention SCO vs Linux always call Linux" "Linux," but the articles that don't seem to remember to call Linux "GNU/Linux?"

    Is this a coincidence? It's been done what seems like 30 times in the last couple months.

    Linux is just the kernal, GNU/Linux is the entire OS which includes both the kernal and all the GNU tools and stuff. SCO is only talking about the kernal so in that case they are right in just saying Linux.

    --
    I stole this Sig
  11. This leaves one big question... by Krapangor · · Score: 5, Insightful
    ...why does nobody stop these ridiculus claims of SCO ?
    It can be done as it has been already proven in Germany.
    Nobody can make false accusations without giving proof. Any Linux distributer or the EFF or other interest groups can sue them. And if one does this SCO would to have to show the code or STFU.
    It also raises the question why IBM doesn't do this.

    The only sensible explanation for this strange behavior seems to me that SCO has some (perhaps weak) point and such a countersuit would fail. It seems to me that some of the players in this game have much more knowledge then they admit openly.

    --
    Owner of a Mensa membership card.
    1. Re:This leaves one big question... by Anonymous Coward · · Score: 3, Insightful

      IBM wants a court decision saying that Linux is untainted by SCO or AT&T code, so they don't want to do anything that will cause SCO to collapse like a house of cards *before* they get that judgement. Afterwards....

    2. Re:This leaves one big question... by lakmiseiru · · Score: 2, Insightful
      My best guess, aside from your explanation, is that letting SCO dig themselves deeper is satisfying for a few reasons:

      • Emotionally satisfying
      • Source of amusement for *nix community
      • When/if something happens to "stop these ridiculous claims of SCO," the more evidence against them and the more anti-SCO feeling present, the more likely action will be taken
      In short, by waiting we allow SCO to alienate more groups and increase the chances of a decisive victory, legal or otherwise. If various groups were to force SCO's hand now, the actions taken might not have such a lasting impact, and (even more troublesome) might be viewed with doubt by the rest of the world. Waiting for more evidence (as you said) or a decreased public opinion serve the same purpose: waiting to act helps us, not them. Of course, if (don't take this wrong, now, it's an "if") the case has a few holes, waiting could help them... but somehow I doubt it. The evidence seems to be too strong.
      --

      Access denied: Not enough clue for requested operation.
    3. Re:This leaves one big question... by ajs · · Score: 2, Interesting

      The courts will do that in the US. As soon as this hits a court-room there are one of two outcomes I expect: 1) it gets thrown out on the basis that SCO has spent so much time trying this case in the court of public opinion that a court decision would be a meaningless adjunct to SCO PR 2) SCO is made to shut up for the duration of the case. I think 2 is far more likey, but SCO's in for a nasty bit of bonking on the head for their behavior.

      Judges don't tend to be fond of those who would use their courts for PR purposes.

    4. Re:This leaves one big question... by Zathrus · · Score: 5, Informative

      Because you'd be a damn fool to do so.

      As it stands, SCO will have to prove that IBM broke its trade secret agreement, which is going to be a damned difficult thing for SCO to do. They're alleging copyright infringement as well but, and this is important, have yet to file a claim in court about any infringement whatsoever. Until they do so what exactly are you going to sue them for? Libel? Good bloody luck. You'd then be on the wrong side of the table -- you'd have to prove that their claims are false without ever seeing any of their documentation. Enjoy! You'll lose that case in a millionth of the amount of time the SCO/IBM case will take. If you even make it to day 2 in court I'll be amazed.

      Here's the deal though -- since SCO is bringing the case against IBM they will have to disclose ALL relevant information on the case to IBM. And presumably to the public, unless they somehow get the record sealed (and SCO does not have the political might that AT&T had in the AT&T/Berkeley case). The claimant is not allowed to spring surprises on the defendant in the US court system -- the defendant, being presumed innocent, is privy to all the claims being brought against them as well as all evidence to support those claims. The same is not true in reverse -- IBM can bring out evidence to counter SCO without SCO's lawyers having ever seen it before (this, however, is generally considered bad form and frowned upon not only by the other lawyer, but also the judge -- judges don't like having their time wasted and any such evidence should be shared with the claimant in order to avoid having the case go to trial in the first place).

      IBM may bring a countersuit against SCO, but in order to do so they'd have to show some substantive damages to their business model... not a very easy thing to do, particularly when you're the size that IBM is. It also complicates matters, and if IBM thinks they have a solid case they may not feel the need to bring a countersuit... easier just to shut them down quickly rather than turn an already long and complicated case into an even longer and more complicated case. Countersuits seem to be used most often when neither side has a particularly strong case.

      It seems to me that some of the players in this game have much more knowledge then they admit openly.

      Welcome to reality.

    5. Re:This leaves one big question... by prgrmr · · Score: 2, Interesting

      ...why does nobody stop these ridiculus claims of SCO ? It can be done as it has been already proven in Germany. Nobody can make false accusations without giving proof. Any Linux distributer or the EFF or other interest groups can sue them. And if one does this SCO would to have to show the code or STFU. It also raises the question why IBM doesn't do this.

      Several reasons:

      - it costs money to sue. Without a reasonable expectation of a return of that money in the form of an award for damaages, it's a poor risk.

      - is the code from Sequent subject to SCO licensing and IP owership with regard to their contract with IBM for license rights to Unix?

      - what of the GPL? This is clearly the biggest question for the Linux community, and much less so for IBM

      - Who really has a horse in this race? Marketing considerations aside, what risk does Suse, RedHat, Mandrake, et al have in the SCO vs. IBM suit? Until they are sued by SCO--and it will come in some shape or form regardless of the SCO vs. IBM outcome, unless IBM just buys them--what do they have to worry about that they can do something about?

    6. Re:This leaves one big question... by Twanfox · · Score: 2, Informative
      I know this is a stupid nit to pick, but...

      Until they do so what exactly are you going to sue them for? Libel?

      If SCO is going overseas and telling by word of mouth, it's slander. If they print it in book, or magazine or paper or something, it's libel. A newspaper reporting news on what someone else said isn't exactally libel, as the newspaper isn't saying it, but repeating what's spoken.

    7. Re:This leaves one big question... by ccarr.com · · Score: 3, Informative

      the defendant, being presumed innocent, is privy to all the claims being brought against them as well as all evidence to support those claims.

      You mean presumed "not liable". This is a civel case, not a criminal case.

      The same is not true in reverse -- IBM can bring out evidence to counter SCO without SCO's lawyers having ever seen it before...

      No. In a civil case, the discovery rules allow either party to examine the other's records.

      --
      I don't know half of you half as well as I should like, and I like less than half of you half as well as you deserve. BB
    8. Re:This leaves one big question... by jreilly · · Score: 2, Interesting

      It would be damned hard to prove libel in the US. But what about the UK. If I recall correctly, the libel laws in the UK are such that the burden of proof is on the defendent. If SCO has a business prescence in the UK, and someone were to sue them there, they'd be forced to either accept a guilty verdict, or make their "proof" public. win-win for the linux community

      --

      Freedom's just another word for nothing left to lose
  12. Japanese fluency by Fratz · · Score: 2, Interesting

    "McBride, who is fluent in Japanese, will visit with several founding members to show them code samples in which the Linux open-source operating system allegedly violates SCO's Unix patents, said an SCO spokesman."

    Something tells me that he won't need to use his Japanese much to understand their response. Laughter transcends language, after all.

    --
    -- Fratz, human
  13. In a related story by AtariAmarok · · Score: 5, Funny

    (AP) In a related story, SCO took its fight against Linux to Antarctica. Little is known of the results, except that there are rumors of significant reductions in the penguin population."

    --
    Don't blame Durga. I voted for Centauri.
  14. Evidence of someone else's common code? by Fly · · Score: 5, Interesting
    "I saw what appeared to be a word-for-word copy of about every third line of code in the central module of the Linux kernel," said Enderle of Giga Information Group, who viewed the alleged code violations two weeks ago. "The lines of code contained typos, misspellings and even copyright disclaimers. It appeared to constitute a violation of the license."
    Whose copyright?!? Surely, if is a GNU copyright notice, then SCO shouldn't be claiming the code. If it is a SCO copyright notice, then GNU/Linux should have noticed it already. If it is another BSD or other copyright, then what the heck is SCO trying to pull?
    --
    end of line
    1. Re:Evidence of someone else's common code? by NecroPuppy · · Score: 3, Insightful

      Right, but follow me here.

      If there is something in SCO code that has a copyright notice, it has to be either a SCO copyright notice or someone else's copyright notice. (For the purposes of this, anything that SCO has rights to will be a considered to be an SCO notice.)

      If it is an SCO notice, then it should be very easy to find in the Linux source. Then we know what it is.

      Alternately, it is someone else's copyright notice. And if the copyright notices match, then it is code that was put into both SCO's and Linux's codebase. If it were a GPL copyright notice, then SCO is guilty of bringing code into their codebase without releasing it. I can't really believe they would be that stupid.

      Therefor, the notice must be for something that SCO thinks they have rights to. Whether this is AT&T or Novell derived stuff or something else, we don't know yet.

      The project then becomes thus:

      1) Identify all copyright notices in the Linux codebase.
      2) Eliminate all code sections with GPL notices, as that can't be in the SCO codebase (again, unless they are really stupid).
      3) Tabulate all remaining entries, and determine when and how they entered Linux. If necessary and possible, contact the contributors.
      4) Post the results, send links to the world.

      and, 5) Profit from the fact that SCO is driven into the dirt.

      --
      I like you, Stuart. You're not like everyone else, here, at Slashdot.
  15. What they're saying: by Jonsey · · Score: 3, Funny

    With ... regretted appologies to Yatta!(c)(tm) (r)(dog)

    Nippon-Sue-Sue SCO-wonderful Easy-Rider-Salad-The-Mall! We didn't win so Sue! Sue! Sue! Sue!

    Now where are the guys in underwear jumping around talking about how life is good as long as they have leaves and that the economy will recover?

    Related Link: Google for Yatta. Trust me.

    --
    I assert that my comment is only my opinion, not that of any employer, past, present or future.
  16. Divinyls... by Anonymous Coward · · Score: 4, Funny

    When I think about SCO I touch my CELF

  17. Just more evidence. by cornice · · Score: 5, Insightful

    This is just more evidence that SCO has no intent other than to harm Linux. There seems to be nothing to gain, for SCO anyway, from this escapade in Japan.

    If this were an attempted murder, the victim would be Linux. The weapon would be SCO and the detective would now be visiting everyone with a motive. Hmmm who could that be?

  18. You are doomed now .. they know who you are ... by TheViffer · · Score: 4, Insightful

    "The 1,500 companies who received letters from SCO [about potential infringements] should be worried, big time," said Rob Enderle, a research fellow for the Giga Information Group (Santa Clara, Calif.). Based on what he saw, Enderle said, "The evidence appears to be very compelling."

    Prepare for the leter with very compelling information.

    Ahh lets cut the crap right now.

    All SCO would need to do is publish one example of where Linux has there source code here to slashdot and it would probably sway 50% of the /. viewers in a second (and if you mention WMD or politics here, you should get modded down to obliteration)

    I would very much like to see one of these 1500 letters and this very compelling information.

    --
    -- Knowing too much can get you killed, but knowing who knows too much can make you rich.
    1. Re:You are doomed now .. they know who you are ... by Anonymous Coward · · Score: 5, Interesting

      "The 1,500 companies who received letters from SCO [about potential infringements] should be worried, big time," said Rob Enderle, a research fellow for the Giga Information Group (Santa Clara, Calif.). Based on what he saw, Enderle said, "The evidence appears to be very compelling."

      Ohh.. Rob Enderle a previous IBM employee whose research and client list includes "Anticipating changes in Microsoft products and organizational direction" and "Microsoft". Sound like someone I'd trust to comment on SCO vs IBM? Yeah...

    2. Re:You are doomed now .. they know who you are ... by Ian+Lance+Taylor · · Score: 2, Informative

      I would very much like to see one of these 1500 letters and this very compelling information.

      I can't help you with the compelling information, but SCO posted a copy of the letter on their web site for a while. I think they've taken it down since, but you can still see it here.

  19. Re:Lame Duck by DrWho520 · · Score: 2, Funny

    I didn't think Japanese companies gave lame ducks much consideration...besides what kind of sauce to cook them with.

    --
    The cancel button is your friend. Do not hesitate to use it.
  20. sorry, charlie by SweetAndSourJesus · · Score: 3, Informative

    Asshat was around long before fark.com.

    An interesting etymology of asshat.

    --

    --
    the strongest word is still the word "free"
  21. Darl must be suicidal by Andy+Dodd · · Score: 5, Funny

    Isn't it enough to piss off one 800 pound gorilla?

    Now he goes poking another eight of them with a stick.

    --
    retrorocket.o not found, launch anyway?
  22. SCO just filed amendments to bylaws to indemnify by walterbyrd · · Score: 4, Interesting

    top execs.

    Something I read on yahoo message board.
    ----
    Specifically quoted from their FORM 8-A/A SEC filing. Last sentence of page 3 in the Bylaws section:

    "The Bylaws also provide that the Company will indemnify officers and directors against losses that they may incur in investigations and legal proceedings resulting from their services to the Company,"

    So as far as I can tell the Company could care less whether or not what they did was legal or ethical.

  23. What the hell. by Mmm+coffee · · Score: 2, Insightful

    What the hell, I got karma to burn. You know, I really want to kick that guys ass. Doesn't even really have to be a full out fight, just give me one shot. Just one little shot and I'll knock him out, easy.

    SCO has lawyers. Linux has a bunch of geeks with thousands of hours of experience with the bloodiest video games on earth.

    -1 Offtopic.

  24. UNIX Patents by Bigby · · Score: 5, Informative

    "In the past three months, SCO Group, a small software company that owns Unix patents, claimed it had found chunks of its Unix code in Linux."

    I thought it was already concluded that SCO doesn't even claim to own UNIX patents. They just claim that they own the copyrights. The Novell escapade brought all of that out. EE Times needs to get their story right.

  25. Easy way to fix this.. by AlbanySux · · Score: 4, Interesting

    IBM has the code to both SCO and Linux, why don't they find out the offending chunks and release a patch to romove them. The Linux community can then rewrite these peices of code and the problem goes away.

    Unless ofcourse IBM thinks that would be an admission of guilt and therefore screw them.

  26. They Own C++ Too!!! by jobsagoodun · · Score: 5, Interesting

    In this zdnet article (who else!) from 2002, Darly Baby says:
    "And C++ programming languages, we own those, have licensed them out multiple times, obviously"
    Watch yer arse Stroustrup! Darls coming to get you!

    1. Re:They Own C++ Too!!! by the-build-chicken · · Score: 4, Funny

      wow, there must just be some insane hash being passed round at SCO headquaters. I wanna get me a half a bag of SCO special, sounds like it kicks ass.

  27. Strange trip to Japan by walterbyrd · · Score: 5, Interesting

    I got this post from the yahoo message boards, the guy has a good point:
    -----
    by: martin_lvnv (41/M/Las Vegas) 07/07/03 04:44 pm
    Msg: 18108 of 18112

    Has anyone considered how strange it is that Darl is going to Japan to talk to the CE Linux Forum? CE stands for consumer electronics: i.e. very small embedded systems running out of ROM most of the time without a hard drive on a small cheap processor.

    SCOs published claims both from press releases, news reports and their own complaint are about IBM putting "enterprise" technology into Linux: NUMA, JFS, RCU, SMP etc. None of these things apply in the least to embedded systems running out of ROM on a consumer electronic device. Whats up with that?

    My only guess is that SCOs arrogance knows no bounds and they think anything using a computer chip, even a toaster, has to infringe on SCOs IP.

    http://www.celinuxforum.org/PressRelease/pr02.ht m

  28. Uniformed article by El · · Score: 2, Funny
    SCO Group, a small software company that owns Unix patents


    Uh, what Unix patents would those be?

    --

    "Freedom means freedom for everybody" -- Dick Cheney

  29. Where do you get this shit? by poptones · · Score: 3, Informative
    In the early years of the 20th century, "dog and pony show" was a derisive name for a small circus or carnival. These small-town carnivals, not large or fancy enough to offer elephants and tigers, had to make do with more modest acts, such as dancing dogs and prancing ponies, to draw crowds. By the time of World War I, "dog and pony show" was being used as a metaphor for a big show with very little substance.

    Many "mom and pop and kids" circuses that toured small towns could not afford the expense of maintaining large animals such as camels and elephants, or dangerous and also expensive ones such as lions and tigers. Often, their only menagerie was a few dogs and a pony. The majority of their entertainment consisted of clowning, acrobatics and juggling, with a few acts that involved the dogs and pony. The larger, more sophisticated and better equipped circuses came to refer to these little guys as "dog and pony shows."

    I'm sure there was the occasional carnie who would put on "special" shows for select clients, but so far as I know beastiality has long been illegal in many US states and, therefore, the practice you describe, performed in the US, would present a very real risk of imprisonment to all participants - hence the legends about "pony shows" down in ye olde Tijuana.

  30. Japan Impression by Shadow+Wrought · · Score: 5, Interesting
    I somehow doubt that McBrides Dog and Pony show is going to have much of an impact on the CERF companies. These folks didn't just draw Linux out of a hat, they have been studying it for months now. Not only that but their lawyers have already looked at all sorts of fine print about this and concluded that the companies are OK.

    I worked on an IP case as a paralegal once that involved the Japenese Patent and Copyright office. It is an amazingly complex system over there and I doubt that SCO would be able to do anything to them even it wanted to. Even if they tried to get a UTC injunction against the importation of the Linux embedded goods, they would still be limited to getting the infringing pieces removed. While I am not a developer, it certainly seems from what I have read that replacing the offending code would not be terribly onerous.

    In the end, however, I can see potentially large blows coming to either the Linux community or SCO depending on how the companies respond to the presentation.

    --
    If brevity is the soul of wit, then how does one explain Twitter?
    1. Re:Japan Impression by Mostly+a+lurker · · Score: 2, Insightful

      If there were anything even remotely real about SCO's allegations, then this would be extremely significant in Japan. It is not to do with the legal position. The business climate in Japan is totally different to that in the US. In Japan, ethics and probity are critical. If SCO could provide convincing evidence that their trade secrets had been infringed in Linux, Japanese organisations would take a big financial hit to avoid using it. However, they will look at any claims with a fine toothcomb before accepting them. Actually, the impact of McBride's visit will be an excellent indication of whether we have anything at all to worry about.

  31. Re:Copyright Question by judmarc · · Score: 2, Interesting

    IAAL, but despite the fact that I've worked on copyright and patent litigations, I'm no expert. With that disclaimer, a couple of words about what little I do know:

    1. SCO's suit, at least so far, isn't a copyright case, it's a contract breach claim against IBM.

    2. In a contract suit there is a doctrine called "mitigation of damages," which says you can't get damages from the other party for harm you could reasonably have avoided. I'd take this to mean that SCO can't get damages for any use of its code that occurred after the point where IBM could have stopped using it if it had been notified by SCO.

    3. Like everyone else, I'm very puzzled by SCO's failure to specify the offending code, and its lame excuses for that failure. OTOH, David Boies is a *very* good attorney, and if this is as lame a case as SCO's management is making it appear, I can't understand why he's still representing them. So the upshot is, as someone said in a response above, we'll just have to stay tuned (for a couple of years? arrgghh) and wait for this thing to play out.

  32. Not really offtopic, I'll tell you why. by ebbomega · · Score: 2, Insightful

    (Why must Mods automatically assume that something is offtopic. If anything bad it's flamebait, but I hardly see that it is)

    This seems to be central behind this debate. What is SCO claiming is infringing? Some seem to say that it's claiming that the Linux kernel has IP source code in it. If this is the case, then no, it's Linux that's infringing and NOT GNU/Linux. If it's GNU/Linux that's infringing, then I think they also have to accuse Berkeley of the same thing, as the GNU operating system is designed on the same general theory as BSD (A UNIX-like operating system). As I recall, all BSD ever got in trouble for was naming their OS UNIX. GNU's already got that area covered pretty easily, wouldn't you say?

    Now, if there's a specific COMPONENT of GNU/Linux that infringes (which would be a bit difficult to pinpoint... X11? Bash? What?) Then they should stop mentioning Linux in its entirety and shouldn't come after it so much as they should go after the project developers or the FSF. Not to mention the GNU/HURD developers.

    The most plausible case that SCO seems to have is over the Linux kernel, honestly. In which case it has nothing to do with GNU except that the GNU/Linux system is distributed with the infringing kernel. However, that's something that SCO should take up with Linus et al instead of the distros themselves.

    More FUD, more FUD, more FUD.

    --
    Karma: Non-Heinous
  33. f@!k the NDA I signed: many lines of code are same by binaryfeed · · Score: 4, Funny
    I signed the NDA and looked at the code in question with a SCO representative.

    Every few lines there was a line that was exactly the same as code in the Linux kernel source tree.

    These lines contained one and only one character: '\n'

  34. Re:We are moths attracted to the flame ... by canajin56 · · Score: 2, Funny
    --
    ASCII stupid question, get a stupid ANSI
  35. thanks... by lauterm · · Score: 2, Funny

    Thanks for the fix. The twitches were really starting to get bad.

  36. Every third line of code... by PickaBooga · · Score: 5, Insightful

    I am getting sick of reading this inane and insane quote:
    "I saw what appeared to be a word-for-word copy of about every third line of code in the central module of the Linux kernel," said Enderle of Giga Information Group
    How the hell do you copy every third line, without copying the other two? It would be like making a knock-off of Harry Potter and the Order of the Phoenix where I copied every third line, and I got the other two lines from the public domain Moby Dick.

    Don't even get me started on the meaningless phrase "central module of the Linux kernel".

    It would be much more believable if he just said the whole damn thing was copied. I guess he thinks it sounds more "technical" than saying 33% was copied, because he can show off that he knows "code" is made up of "lines".

    Why doesn't he just say every third byte was copied from the Evil Master Control Program, and then scoot off on his little Tron light-cycle?

    I am getting sick of hearing that quote from that jackhole of the universe.
  37. Mr. Yodaiken anyone? by i_really_dont_care · · Score: 3, Interesting

    "It shows how entrenched Linux has become," said Victor Yodaiken, CEO of FSMLabs Inc. (Socorro, N.M.), a maker of real-time software for Linux.

    Aah... yes. Last time I checked, FSMLabs was trying to undermine the GPL by offering kernel patches which use FSMLabs proprietary patented technology. The situation has become better due to massive intervention of the FSF since then, but is still somewhat uncertain.

    It's scary that this is a time where even the foe of our foe is not necessarily our friend.

  38. Standing by Beryllium+Sphere(tm) · · Score: 2, Interesting

    My non-lawyer understanding is that US courts can be really unwelcoming if you're not directly affected. A judge might say "Has SCO sued you? Sent a cease-and-desist? Have they even mentioned you by name? No? Then mind your own business".

    US courts are also Very Expensive. Anyone who jumped in now would be doing IBM's work for them, and paying kerjillions of dollars to do so.

    What IBM gains by waiting is that every time an SCO executive opens his mouth, IBM's lawyers have one more thing to cross-examine him about.

  39. Microsoft Puppet? by Ogerman · · Score: 4, Insightful

    Somebody correct me if I'm wrong, but it seems as though SCO has absolutely no interest in consumer electronics and embedded devices. (And yet Microsoft certainly does.) So why would SCO waste time specifically targeting an upstart organization aiming to promote Linux for consumer electronics? It's not a threat to their marketshare. Seems fishy, albeit unprovable at this stage. Granted, they may only be making as much fuss as possible.

    1. Re:Microsoft Puppet? by Imperator · · Score: 2, Interesting

      This is one of those cases where it's obvious what's going on, but the party that buys the lawyers and the PR firm prevents the truth from being proven in court. (Look at OJ Simpson's first trial for another example of this.) It's obvious to us that MS "bought a license" from SCO as a way to funnel money to a dying company, in exchange for which it would launch a massive FUD campaign against Linux. MS looks clean but the damage is done. SCO execs make some money. The SEC has been squeezed of funds so it won't ever bring the case to trial.

      --

      Gates' Law: Every 18 months, the speed of software halves.
  40. Where Darl got his Japanese. by ashitaka · · Score: 4, Informative

    From his bio:

    From 1988 to 1996, he worked at networking leader Novell where he was responsible for growing Novell Japan's growth to more than $100 million in revenue.

    I was in Japan from 1986 to 1996. Novell went absolutely nowhere during that time. Microsoft took over the networking market. I ended up dealing only with Novell U.S. as Novell Japan was absolutely hopeless to work with. Now that I think about it, I seem to recall meeting Darl at a gaijin get-together. Just another expat executive lording over the locals.

    If he knows more Japanese than "o-kane dase" I'll be amazed.

    --
    If you don't want to repeat the past, stop living in it.
  41. We already know what it is by autopr0n · · Score: 3, Informative

    Supposedly its the RCU (Read, Copy, Update) code that speeds up threading on super-highend systems. It came from Sequent which was later purchaced by IBM. The AT&T contract signed by sequent didn't have the add-on that IBM had, which said that IBM 'owned' all the software they developed. In other words, all the UNIX stuff developed by sequent before it was purchaced by IBM SCO has a rights on.

    The problem is what Sequent did was come up with the system and patent it, publishing the system in a patent, which applied to any multithreaded OS. In other words, they developed something and stuck it into their unix system, not the other way around.

    Anyway, this is only one part of the story...

    --
    autopr0n is like, down and stuff.
    1. Re:We already know what it is by Ian+Lance+Taylor · · Score: 3, Informative

      No, SCO is alleging that RCU, as well as other code, was contributed by IBM to Linux in violation of IBM's Unix licensing agreement. SCO does not claim that that code was copied from Unix to Linux, because that code was never in Unix; it was only in IBM's version, AIX.

      There is different code which SCO alleges was copied directly from Unix to Linux.

  42. IBM and the ant by kalel666 · · Score: 2, Funny

    This whole saga reminds me of an old joke, which I'll update to make more relevant.

    One day there was an elephant named IBM walking through the jungle, when he accidentally got a thorn stuck in his foot. He hissed in pain, and pondered his predicament, when an ant named SCO overheard him.

    After being told the problem, SCO the ant said, I'll help you out by removing the thorn on one condition; If I do it, you have to let me fuck you in the ass.

    IBM the Elephant looked around, thinking this was a joke, but eventually said, 'Sure, why not?', figuring how bad could an assfuck be from an ant. So SCO the ant walks over, pulls out the thorn, and says, alright, Pay Up!, and starts climbing IBM's leg.

    Once he's in position, SCO starts pumping like mad, fucking the elephant in the ass. Meanwhile, IBM is checking his watch, wondering when SCO will get started.

    While this is going on, a couple of monkeys, named Slashdot and Linux, are in the trees watching this whole thing in amusement. When SCO starts fucking IBM in the ass, they start howling, laughing their asses off. They laugh so hard, they knock a coconut loose, which falls and hits IBM in the head.

    Oww! screams IBM, 'That hurt!'
    Hearing this, SCO looks up and screams 'TAKE IT ALL BITCH!'

    --
    I HAVE CUBIC WISDOM THAT TRANSCENDS AND CONTRADICTS ONE DAY GODS
  43. link by Anonymous Coward · · Score: 2, Informative

    Read it here. Shave off the filename to get a list of all documents in this filing.

    [jole]

  44. And it is no secret he doesn't like linux by eddy · · Score: 3, Interesting

    At least, he works for clients who want him to say that linux sucks, which can be seen here for instance (thanks to Anon on osnews for that link)

    "Linux and other open source projects require too much customization, and doubts about the legitimacy of open source code could get users tangled up in lawsuits. Besides, many Linux supporters are a bunch of potty-mouthed malcontents. Enterprises are better off staying away from Linux and open source -- or at least thinking through the possible liabilities, argues guest columnist Rob Enderle."

    --
    Belief is the currency of delusion.
    1. Re:And it is no secret he doesn't like linux by MacOS_Rules · · Score: 3, Funny

      potty-mouthed malcontents?!?

      FUCK HIM!!! fuck him and his lousy, closed-source thesaurus! =)

      --
      If a man's character is to be abused there's nobody like a relative to do the business. -Thackeray, William
  45. What about the NDA? by bearclaw · · Score: 2, Interesting
    "I saw what appeared to be a word-for-word copy of about every third line of code in the central module of the Linux kernel," said Enderle of Giga Information Group, who viewed the alleged code violations two weeks ago. "The lines of code contained typos, misspellings and even copyright disclaimers. It appeared to constitute a violation of the license."

    How is it this person can say this without violating the NDA? Does SCO have to enforce all violations of the NDA, or just selective ones? I guess SCO could allow this person to view it without an NDA, provided they say this.

    Thoughts?

    --
    -- bearclaw
  46. Re:SCO just filed amendments to bylaws to indemnif by Farmer+Jimbo · · Score: 3, Informative

    You are talking about the SEC form 8-A12G/A from SEC's SCO page, correct?

    It's all governed by General Corporation Law, in this case indemnification is limited by section (e)

    All they're really saying is, if we didn't have seperate D&O policies for the directors and officers before, we do now. And some other stuff to try to prevent a hostile stock take over.

  47. I do not understand this???? by LWATCDR · · Score: 2, Interesting

    Didn't SCO say that the "stolen" code was Enterpise stuff that Only could come from SCO. Didn't they also claim that this code was Intel based? What the heck is this all about then. Embedded systems are not Enterpise systems. A lot of Embedded systems do not use Intel CPUS. Why do I get a feeling that Sony was laughing there butts off at this guy. Well we can hope.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  48. meh! by danro · · Score: 2, Funny

    Yeah, I use SCO as my server platform, and WinXP for my desktop. I'm a /. rebel, baby!

    If you were a true rebel, you'd be using WinXP as a server and UnixWare (or some other SCO-crap) as a desktop.
    Imagine the pain.

    --

    "First lesson," Jon said. "Stick them with the pointy end."
  49. Patents my ass... by eniu!uine · · Score: 2, Insightful

    Well, not literally.. SCO doesn't have a patent on my ass. Quote from article.

    McBride, who is fluent in Japanese, will visit with several founding members to show them code samples in which the Linux open-source operating system allegedly violates SCO's Unix patents, said an SCO spokesman.

    According to the patent search I just did, there are only three patents, one by Caldera and two by Santa Cruz Operation. While they have patented some useful things, like using a network, you would not have to view code when you're trying to see if something violates a patent. Patents are about what things do, not specifically how they are built. If you had a patent on 'a method of printing "Hello World!", I could copy almost all of your code, but change mine to printf("SCO sucks"); and it would not be patent infringement. This would be a case of copyright infringement, so the question is 'why aren't they suing for copyright infringement'... if someone was infringing on my copyrights that's probably what I would sue them for. Unless, that is, I had no case whatsoever. What they are suing for is contract violation.... there is no way anyone can say jack shit about that unless they have read the contracts. What I will say though is that it is clear SCO is claiming rights to technologies: NUMA, SMP, etc. based on the fact that they were incorporated into an operating system that was derivative of Unix. This is what they do in the press.... this completely irresponsible slander.. but what they will say in court remains to be seen.

  50. OT: Confused by fireman+sam · · Score: 2, Funny

    I was wondering, what part of OpenServer is actually open?

    Is is the code they "borrowed" from Linus?

    --
    it is only after a long journey that you know the strength of the horse.
  51. Let Him Keep Doing This Crap by Master+of+Transhuman · · Score: 2, Interesting

    It'll all be evidence against him in his "unfair restraint of trade" lawsuit that someone will no doubt bring against SCO when they lose the IBM suit...

    I predict that SCO will not be bought out and will not make big bucks suing people. I predict that THEY will be sued and brought to bankruptcy by the lawsuits within the next couple of years.

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  52. Amount of damage? And what about those patents? by hobsonchoice · · Score: 4, Interesting

    Two things

    1. According to http://www.slweekly.com/editorial/2003/city_2003-0 7-03.cfm, Caldera bought DR-DOS $400K, but got from law suit $155,000,000.

    As far as I know (I guess somebody could check) they didn't purchase the UNIX source, or value it in their SEC reports, for anything like $1bn, or $3bn, let alone $50bn... so how can they claim billions of damages, if they bought it for a few millions, and valued it of the same order?


    2. I keep seeing patents in lots of news articles about the case. My understanding is the case is about alleged contractual violations, alleged trade secret issues and alleged unfair competition etc.,

    http://www.internetwk.com/breakingNews/showArticle .jhtml?articleID=10818216
    "McBride, who is fluent in Japanese, will visit with several founding members to show them code samples in which the Linux open-source operating system allegedly violates SCO's Unix patents, said an SCO spokesman"


    http://www.wired.com/news/business/0,1367,59551,00 .html also has a SCO spokesman refering to patents

    So the obvious questions are:
    - Is the press getting it wrong?
    - If the press is indeed getting it wrong, why are they (and not just one news source) getting it wrong?

  53. MS-DOS and Calderara by Anonymous Coward · · Score: 2, Interesting

    Just want to straighten everyone out on the Caldera suit against MS several years ago. A lot of people here seem to regard that suit as part of the same pattern SCO is persuing in the current fiasco.

    In fact, Caldera's suit agains MS was far more similiar to Netscape's. MS screwed DR-DOS in the market-place with FUD, and technically by coding Windows 3.1 to break under it. Given MS-DOS's origins, it's likely that it had lots of copied code from it.

    Furthermore, Darl & Co. weren't involved in the DR-DOS suit. Ray Noorda basically took it from Novell (or off their hands) when he left to run Caldera.

    A lot of people approved of Caldera's actions at the time, because they clearly had a strong case and it was also clear that MS had strong-armed DR-DOS in the same way that eventually got them pulled into anti-trust court and declared a monopoly.

    In other words, the DR-DOS case was a very different situation with a largely different set of characters involved. Microsoft deserved what it got there.

    Linux, however, clearly doesn't deserve this shit.

  54. Re:Not gnu/linux, its Linux by Billly+Gates · · Score: 2, Informative

    RIght.

    Also Linus himself calls distributions Linux. Its his OS right? Yes it just the kernel bla bla but last time I checked only debian called itself Gnu/Linux.

    1.)People call it Linux so its Linux.
    2.)Only Debian can offer a truly "gnu" system so its the only distro that calls itself gnu/linux.

    According to the gpl you can not have any proprietary or other freeware that is not gnu in your product and release it under the GPL. Also the license does not require a product to call itself gnu/x if its released under the gpl or does it require the author to assiocate his or her product as part of "gnu". However you can not call something "gnu" if its not released properly under the GPL.

    This is why redhat Linux is linux while Debian is Debian gnu/linux.

  55. Smart Move For McBride by Anonymous Coward · · Score: 4, Insightful

    This move just proves beyond a shadow of a doubt that this whole SCO escapade is publicity stunt designed to hurt Linux.

    The only way to get fluent in Japanese is to live in Japan. If the article is true and McBride is fluent, then we can assume he has spent some time in Japan and knows something about business in Japan. This means he knows, that no matter what he tries in Japan, he will get absolutely nothing accomplished as far as suing the major Japanese players is concerned.

    What he will get, however, is many industry leading, powerful corporations agreeing with him publically.

    That is the Japanese way, maintain the "wa" (harmony.) Stay in agreement publically, while internally things are very different. McBride will use this "Public agreement" of Sony, Hitachi, Matsushita, Sharp, Phillips, Samsung, NEC, and Toshiba to cast even more FUD about linux. "Hey look, IBM may not think we have a case, but the Japanese giants unanimously agreed with everything we said."

    This move is very, very smart for McBride if he plays it right. May he fry in hell.

  56. -1 Troll by Grizzlysmit · · Score: 2, Interesting

    Can we just moderate SCO -1 Troll

    --
    in my life God comes first.... but Linux is pretty high after that :-D
    Francis Smit
  57. Comment removed by account_deleted · · Score: 2, Funny

    Comment removed based on user account deletion