Slashdot Mirror


OSI vs SCO

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

551 comments

  1. Wow by gazbo · · Score: 5, Funny

    OSI is ISO backwards. Conspiracy.

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

      When I first read the headline, I thought of the ISO OSI network model. Then I clicked on the link to find out it's about Open Source Initiative, not Open Systems Interconnect.

    2. Re:Wow by stonebeat.org · · Score: 5, Funny

      no it is just backward compliance :)

    3. Re:Wow by Muad · · Score: 1

      Someone still hasa sense of humor.... hey SCO: Sue me!

      --
      --- "I didn't think anyone would understand it" -Prof. Bob Muller
    4. Re:Wow by hazem · · Score: 1

      Maybe the editors think they'll get more people reading the articles if they make the headings cryptic enough?

    5. Re:Wow by crizh · · Score: 1

      This whole thread will be backwards.

      1. SCO are suing IBM for breach of contract in allowing SCO trade secrets to influence the development of Linux.

      2 SCO are spreading FUD letters around the business community alleging that the Linux Kernel Source contains some of the Bell Labs code that SCO currently owns the copyright to. SCO have withdrawn their versions of Linux on the grounds that now that they know that the Kernel contains stolen code, that they own, to continue to distribute it under the GPL would give all of us an irrevocable licence to use/modify/distribute that code.

      3. 1 and 2 are not related.

      --
      Trust The Computer, The Computer is your friend.
    6. Re:Wow by crizh · · Score: 3, Informative

      Now that I've made that clear.

      1. Read the Position Paper. SCO haven't a leg to stand on in the IBM case.

      2. Prove it. I cannot understand why Linus, Alan Cox, et al haven't filed some sort of libel suit against SCO. If they'd called me a thief in public like that you can bet I'd be having my lawyer call them straight away and suggest that they retract their accusations or have their arses sued off.

      As to SCO withdrawing their versions of Linux, if they did that to avoid being trapped by the GPL then they should have taken the source of the FTP site before they sent out the letters.

      I'm tempted to email Darl and officially accept the terms of the GPL pertaining to the copy of kernel-source-2.4.19.SuSE-152.nosrc.rpm that SCO distributed to me the day after they sent those letters out.

      By pulling their Distro they have plainly stated that they know how the GPL works and how it would prejudice their position. By failing to stop distributing they have given away any code they claim had been stolen.

      Even so they should still reveal what they claim has been stolen from the Bell Labs code. It should be noted that this code is copyrighted, NOT a trade secret, and has nothing to do with the IBM case and SCO has no excuse for not revealing the proof.

      --
      Trust The Computer, The Computer is your friend.
    7. Re:Wow by Your+Anus · · Score: 1

      Actually, I don't see how SCO can *NOT* distribute the source code. Is it not their obligation under the GPL to fulfil any request for the source at least three years after distribution? I guess they could always point back at another source repository.

      I like the point that the Position Paper makes that the allegations SCO makes are so baseless that OSI thinks the State of Utah should review the matter for possible sactions against SCO. Isn't there also a US law about slandering your competitors in public? The Waltham Act?

      --

      In the USA, we like stuff watered down, like beer, television, and freedom.
    8. Re:Wow by crizh · · Score: 1

      I think their position is that the licence that they originally received the source under, and that everyone else distributes under, is not valid as it contains 'infringing' code. Whoever put that code in the kernel had no right to do so and it therefore isn't covered by the GPL. SCO is the only entity with a right to introduce Bell Labs code into the Linux Kernel and that is why they have stopped distributing it.

      --
      Trust The Computer, The Computer is your friend.
    9. Re:Wow by Citizen+of+Earth · · Score: 1

      I cannot understand why Linus, Alan Cox, et al haven't filed some sort of libel suit against SCO.

      Libel!? How about corporate fraud.

  2. Wait a minute... by Anonymous Coward · · Score: 1, Funny



    Someone actually used AIX?!

    1. Re:Wait a minute... by anarxia · · Score: 1, Funny

      No, IBM always bundled Windows with their mainframes.

    2. Re:Wait a minute... by lucifuge31337 · · Score: 0

      Another idiot. Mainframes don't run AIX.

      --
      Do not fold, spindle or mutilate.
    3. Re:Wait a minute... by BJH · · Score: 1, Flamebait

      I know you're being sarcastic, and I think your parent is an ignorant fool too, but as it happens, IBM doesn't bundle AIX with its mainframes either.

    4. Re:Wait a minute... by FutureShoks · · Score: 1

      I rest my case ;)

      --
      ___FutureShoks___
    5. Re:Wait a minute... by t-wata · · Score: 1

      Yes,number of AIX users are much more than UnixWare user(s).

    6. Re:Wait a minute... by Rick.C · · Score: 1
      That was a +n Funny. Please mod accordingly.

      Actually, IBM mainframes ship with an HMC (Hardware Maintenance Console) which is an IBM 300PL PC with a DVD-RAM drive. It runs OS/2.

      Go figure.
      --
      You were 80% angel, 10% demon. The rest was hard to explain. - Over The Rhine
      "Math in a song is good."-Linford
    7. Re:Wait a minute... by mr_z_beeblebrox · · Score: 1

      Someone actually used AIX?!

      Doesn't everyone?!?
      I have a 33 MhZ RS6000 (with 16MB of memory) running DNS on my home network. Ok, I know it's not mainstream but it's just so cool!

    8. Re:Wait a minute... by Anonymous Coward · · Score: 0

      Yeah, I've got an Apple IIc that acts a network gateway and mail server.

      Oh, thats A/UX, not AIX. My mistake.

    9. Re:Wait a minute... by mastropiero · · Score: 1

      Hell, we got one here at work serving as a slave named server and has the longest uptime in the server room (after the redhat mail server, of course :))

    10. Re:Wait a minute... by jedidiah · · Score: 1

      Your pomposity is nice and all but it all flies in the face of the fact that Unixen other than AIX (Solaris) have a bigger part of the market.

      So, it's quite possible to have been out of school for quite awhile and never have seen an AIX deployment.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    11. Re:Wait a minute... by Doobian+Coedifier · · Score: 1

      Well...my school (I work for computing dept.) uses AIX 4.x on a majority of our systems...including our email, web publishing, and research clusters, which are all RS/6000's. They're remarkably stable:

      09:47AM up 591 days, 4:31, 23 users, load average: 0.29, 0.23, 0.20

      But in the end, what's the point of replying to AC's. Oh well. The stability of these machines leaves me with nothing better to do.

    12. Re:Wait a minute... by Anonymous Coward · · Score: 0

      Exactly the truth. This is the same kind of dipshit person who thinks Sun Solaris is true enterprise computing. Ignorant remarks like "OpenVMS has been dead for ten years" is very likely to come out of these fools mouths. I guess that's why banks all around the world are running OpenVMS and the US government has a contract with HP (formerly Compaq) to continue OpenVMS support for the next seven years at the very least. Idiot CS jockies.

    13. Re:Wait a minute... by NighthawkFoo · · Score: 1

      Since OS/2 is end-of-lifed, I wonder if they'll transition it to Linux in the future?

      --
      "I disapprove of what you say, but I will defend to the death your right to say it."
      - Evelyn Beatrice Hall
    14. Re:Wait a minute... by Anonymous Coward · · Score: 0

      Yeah. The grandparent of this post probably thinks BSD is dead, along with this silly Linux fad.

    15. Re:Wait a minute... by Rick.C · · Score: 2, Interesting
      Since IBM owns OS/2, its EOL as an external product does not necessarily affect its status as an internal tool.

      Look at PL/S, a PL/I derrivative that IBM has used internally since the early '70s. It generates compact systems-level code (like C can) and supports in-line assembler instructions for when a high-level language just doesn't cut it. Mention that you know PL/I and you'll get laughed outta Dodge, but if you've ever seen a PL/S listing, you'll understand why they still use it. All their mainframe code is written in PL/S, so it'll be around for a long time.

      Similarly, IBM has a lot of code and a lot of trained programmers invested in OS/2. They're not going to throw that away without a compelling business reason. "But Linux is cool!" is compelling, but it's not a business reason.

      I used to work for a subsidiary of Fujitsu. They made a box that competed with IBM's 3705 and 3745 communications controllers back in the day. Their programmers knew that architecture inside out, so they wrote -all- of their code in 3705 assembler and Fujitsu even produced a proprietary 3705-based microprocessor chip for internal use.

      Never underestimate the value of a code base.
      --
      You were 80% angel, 10% demon. The rest was hard to explain. - Over The Rhine
      "Math in a song is good."-Linford
    16. Re:Wait a minute... by Anonymous Coward · · Score: 0

      Moron -- you're the idiot. IBM M/F could certainly run AIX under VM. Why don't you take that tiny little genital wart between your ears and shove it back into your asshole where it belongs.

    17. Re:Wait a minute... by Anonymous Coward · · Score: 0

      the HMC for the rs6000 regatta class unix machines use linux on the HMC. I'd bet that the mainframes will follow.

    18. Re:Wait a minute... by Gsus411 · · Score: 1

      Nah.... A/UX only runs on 68k Macs, not early Apples. I forget what processors the Apples used offhand......

    19. Re:Wait a minute... by Lee+Cremeans · · Score: 1

      The original Apples (I, II, II+, IIc, IIe, IIc+) were 8-bit machines running processors out of the 6502 family. The IIgs was actually 16-bit internally (it kept the 8-bit Apple II slots) and used the 65C816 CPU, which had a 6502 compatibility mode.

      -lee

  3. GPL the best bet by deanj · · Score: 4, Interesting

    The best bet for this whole thing is that SCO did their own Linux and released it. Since they did it under GPL, the cat's out of the bag. ...At least from this point on...or rather, the point they released it on. They've pulled their Linux since then.

    Question is, can they sue for release of software BEFORE they released the now GPL-ed SCO code in their Linux distro?

    1. Re:GPL the best bet by sparkes · · Score: 3, Interesting

      couple of points.

      1). Did Caldera own the code in question when they where in the distro market?

      2). I don't think the licence on a linux distro is a boilerplate thing. I am not sure that a SCO distribution with a GPL kernel containing the code would sanction the use of said code unless their copyright was on the kernel code in question.

      The kernel is released under a boiler plate licence with a Linus copyright and contains code with other copyright messages also covered by the GPL.

      Unless SCO modified the kernel and added their licence to the code above the Linus one (making the kernel in thier release a fork of the linux code) would just bundling the code with other software in a distribution authorise the re-licensing of their code?

      sparkes

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

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

    3. Re:GPL the best bet by dirk · · Score: 1

      Yes, they can sue for anything before they released their GPLed version of Linux (and possibly afterward if the court finds that they did not have knowledge they were distributing their IP in the kernel, which would invalidate the GPL release). Just because they later released it under another license does not validate the unauthorized use of their IP in earlier instances (if their IP was actually used). Also, it would not authorize the use of their IP unless it is a direct descendent from their distro. The only way to leagally use the code (again, if the courts don't invalidate their GPL release of it) is to take it directly from their distro. Technically speaking, you couldn't take the same code from an earlier distro by someone else, because they did not have the rights to release it under the GPL at that time. Of course proving you got it from a distro that was not theirs will be hard if not impossible (unless your release predates their release). And, of course, IANAL.

      --

      "Information wants to be expensive" - Stewart Brand, the same guy who said "Information wants to be free"
    4. Re:GPL the best bet by pe1rxq · · Score: 2, Insightful

      It doesn't matter whose copyright was on it, even who wrote it...
      They distributed the code under the gpl allowing everybody to see it and thus they have no legal base at all with respect to trade secrets.
      In other words: It can't be a secret if you are telling everybody who wants to listen about it.

      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    5. Re:GPL the best bet by paitre · · Score: 2, Interesting

      Considering that SCO/Caldera is still distributing the SRPMS for OpenServer 3.1.1. Now, considering that SCO is claiming damages in pre-IBM "involvement" as well as post-IBM "involvement" in kernel development, they're pretty much pooched.

      Basically, since SCO/Caldera now owns that code, and they are still distributing it, they are doing so with the full knowledge and understanding that they are bound by the GPL. Pretty much, they're fucked. They may very well be -right- (although I think it more likely that Linux kernel code made its way into Unixware), but they're hosed by the GPL (as they would if it were BSD licensed):)

    6. Re:GPL the best bet by Zocalo · · Score: 5, Interesting
      SCO did their own Linux and released it. Since they did it under GPL, the cat's out of the bag.

      Nope. This is wrong, and keeps cropping up again and again here and elsewhere. *Caldera* did their own Linux and released it under the GPL. SCO (the original) produced and sold commercial UNIX under several names. Caldera then bought SCO (again the original) and it's IP, and still under the name Caldera helped to start the United Linux directive. Up until this point, under the leadership of Ransom Love, Caldera "got it".

      It would then appear that Ransom Love left and the lawyers took control, which is the point where they "lost it". Caldera became the current SCO, and the dubious comments about UNIX vs Linux started to fly around. The comments then became more legally inclined, finally culminating in the suit against IBM.

      I'd guess that SCO started to come up with the prospects of the lawsuits after Ransom Love's departure. As they built up their "evidence" (which has yet to be publically documented in a satisfactory manner), the comments grew in the level of vitriol and FUD content. Presumably this increase was as the lawyers became more confident they could pull off their intended plan. Whether that plan is simply to be bought out, or they actually believe they can successfully sue IBM is a matter for speculation. As far as I can tell, all we can say about SCO's current plan is that it seems to be:

      1. Piss off pretty much the entire *NIX community with threat of lawsuit.
      2. ???
      3. Profit!!!
      What step 2. is, remains to be seen, and I really hope it doesn't lead to 3.

      On an unrelated note, what I want to read at this point is a frank positional summary by Ransom Love who is becoming somewhat conspicuous by his "absense" through all this mess.

      --
      UNIX? They're not even circumcised! Savages!
    7. Re:GPL the best bet by Planesdragon · · Score: 4, Insightful

      They distributed the code under the gpl allowing everybody to see it and thus they have no legal base at all with respect to trade secrets.

      Their argument for this claim will be "we didn't distribute it; we had no knowledge." Denying them this would do two things.

      1: Hackers can now put words in the mouth of corporations. (See? MSDN got hacked and folk downloaded GPL'd Windows, so now it's all free!)

      2: Every piece of "FUD" about the GPL will be proven--it IS a viral license, that can irrevocably infect your code without your express wishes.

    8. Re:GPL the best bet by DASHSL0T · · Score: 4, Interesting

      3. Already seems to be working. MS and someone else (even if for dubious reasons) are now licensing from SCO.

      Also, their stock went up 40% (!) yesterday on the MS news. It also was about double from when the lawsuit silliness started *before* yesterday. So SCO stockholders are making money, that's for sure. At least if they bought at a low. Even if they didn't, they have dramatically reduced their losses. The next best thing to making money is to lose less money. :)

      As for the GPL, I really do not think it holds water if somebody misappropriates your code, inserts it somewhere in linux and you unknowingly release it. But, IANAL. If the GPL does stand up and is declared valid in such a case, you can expect large companies to avoid it like the plague. They will not want have to vett every line of code they distribute under the GPL against every line of code in their proprietary portfolio to make sure somebody, somewhere, didn't insert stolen code.

      Please note, I am not saying SCO's claim is valid and anybody took/used anything inappropriately. I am just saying that I don't think the "GPL defense" will stand up in court, and *even if it does* that may have worse long-range effects anyway. A lose-lose. :(

      --
      Freedom Is Universal
      Linux-Universe
    9. Re:GPL the best bet by Penguin+Follower · · Score: 5, Insightful

      2: Every piece of "FUD" about the GPL will be proven--it IS a viral license, that can irrevocably infect your code without your express wishes.

      Actually, in this case it doesn't matter what open license it is. If the license used was the BSD license, SCO would still be losing their "intellectual property" because the source would still be there for everyone to see. Thus, we need not worry about the "viral FUD" if the above point is brought to attention.

    10. Re:GPL the best bet by Anonymous Coward · · Score: 3, Interesting

      It doesn't matter whose copyright was on it, even who wrote it...

      Yes it does. It matters a very great deal, in fact.

      Someone else cannot licence your Intellectual Property without your consent. If there was any code that was stolen from SCO and placed in the Linux kernel with someone elses Copyright on it, that code would not legally be under the GPL. Only the Copyright holder can decide that.

      This is the same as if you purchase a television at a garage sale, but the cops come around and tell you that the television is stolen. You have no rights to own that television as the seller never had any right to sell it to you. Same deal here.

      Now the general argument around here (And also now from ESR) is that SCO distributed the Linux kernel under the terms of the GPL, and even if they were unaware that their code was contained in the kernel they are constrained by the terms of the GPL. It would seem to me that at best that is going to be a huge legal grey area, and at worst it plays directly into the hands of companies such as Microsoft, who have been saying all along that the GPL can "steal" your IP from under you. That would just prove them dead right, wouldn't it?

      I personally believe that the worst part about all of this so far is the stuning display of ignorance that surrounds the GPL.

    11. Re:GPL the best bet by Glock27 · · Score: 1
      What step 2. is, remains to be seen, and I really hope it doesn't lead to 3.

      I guess you haven't seen SCO's stock chart lately...

      Of course, it may come down like a lead balloon any time now... ;-)

      --
      Galileo: "The Earth revolves around the Sun!"
      Score: -1 100% Flamebait
    12. Re:GPL the best bet by pe1rxq · · Score: 1

      In case of your first point it wouldn't be SCO distributing the code willingly...

      As for your second point, yes the GPL is viral, but it is only dangerous if you don't read it before distributing source code under its terms in which case you are simply an idiot.
      And as a poster above already mentioned it doesn't matter as it is about trade secrets being distributed openly....

      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    13. Re:GPL the best bet by Penguin+Follower · · Score: 1

      If the GPL does stand up and is declared valid in such a case, you can expect large companies to avoid it like the plague. They will not want have to vett every line of code they distribute under the GPL against every line of code in their proprietary portfolio to make sure somebody, somewhere, didn't insert stolen code.

      While companies may very well avoid the GPL like the plague as you put it, those companies might as well blacklist every other open source license as well. BSD, LGPL, etc... if you release any source under any of those licenses and it was your trade secret/intellectual property -- you lose it (as many other posters have noted in their replies).

      On a side note: The GPL has been called "viral", but I don't see how it is worse than the BSD license when you consider the following:

      1. OK, Company XYZ unknowingly releases code under GPL. Well, now all their competitors can look at the code, but then have to write their own implementation using that knowlege (i.e. can't copy word for word) or they fall into the trap of using GPL code in their product.

      2. Or, another possibility: Company XYZ unknowingly releases code under the BSD license. Now, not only can their competitors look at the code and understand how it works, but they don't even have to rewrite it because of the way the BSD license works... at least that is my understanding of the BSD license at the moment.

      Thus, I would see the BSD scenario as even worse, because your competitor now HAS your code/product (basically) straight from you! DOH!

    14. Re:GPL the best bet by TheRaven64 · · Score: 1
      This depends exactly what the form of the IP they are claiming is. If it is a copyright violation, then you are correct, however if it is a patent violation then it is not quite so clear cut. If some GPL code contains patented algorithms (see XviD for an example) then the code is free, but can not be run without a license. In this case an implicit license could be granted to anyone running the exact version distributed by the owner of the patent, but not to those who use derived works (this can be done simply by not persuing claims against those individuals).

      On the other hand, I don't think that this is what they are claiming, so this isn't actually relevant.

      --
      I am TheRaven on Soylent News
    15. Re:GPL the best bet by Planesdragon · · Score: 1

      Thus, we need not worry about the "viral FUD" if the above point is brought to attention.

      Actually, by your logic, we ALL would need to worry about it. Does copyleft trump copyright? If so, expect a much harder road for Linux. (Personally, I think it doesn't, but IANAL.)

    16. Re:GPL the best bet by pe1rxq · · Score: 1

      If you had read my entire post instead of just this one quoted line you would have seen that I was saying exactly the same thing.... namely SCO distributed code they claim is theirs under the gpl.
      (In your analogy they sold you a tv (stolen or not) and then go calling the cops on you for being in possession of 'their' tv.)

      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    17. Re:GPL the best bet by Anonymous Coward · · Score: 0

      they would however need to credit their competitor, IIRC

    18. Re:GPL the best bet by Zocalo · · Score: 1
      I purposefully sidestepped the GPL legal issues because IANAL as well. There a few clauses that deal with the issue of restricted license code being released under the GPL, for instance #7 which essentially states if there is a license conflict you "may not distribute the Program at all". This is referring to the GPL'd version, so this is why SCO has had to stop distributing Linux, but does not have to stop selling its commercial product.

      On the general subject of the GPL though, I hope no one is going to be dumb enough to get a judge to rule that SCO distributed it's IP under the GPL and therefore lost *any* of its rights to that IP. If that happens it's going to be hyped as a validation of all of Microsoft's FUD about the "viral nature" of the GPL and a bad day for open source code in general.

      As you say, this is about alledged misappropriation of code and incorporation of that code into another product. The license of the receiving product, in this case the GPL, should be irrelevent in any legal proceedings. I don't see that this is any different from one closed source license package ripping of the code from another closed source package in that respect. If anything though, because the code is now, and always will be publically available (as opposed to being in the public domain) the potential for damages paid to SCO if successful in it's efforts will probably be greater, but hey, IANAL.

      --
      UNIX? They're not even circumcised! Savages!
    19. Re:GPL the best bet by Anonymous Coward · · Score: 0

      Your post never claimed any such thing! You say:

      They distributed the code under the gpl allowing everybody to see it and thus they have no legal base at all with respect to trade secrets.
      In other words: It can't be a secret if you are telling everybody who wants to listen about it.


      Essentially you are arguing that as SCO distributed Linux that their code (which may or may not be in the Linux kernel) is automatically under the GPL, wether SCO knew it was their code or not.

      Your argument only works if you accept that SCO have lost all rights to any code in the Linux kernel, wether they put it there or not. As I said, that is a load of rubbish. Only SCO can put their code under the GPL. Simply redistributing that code in good faith is highly unlikely to bind them to the terms of the GPL.

    20. Re:GPL the best bet by sphealey · · Score: 2, Insightful
      Now the general argument around here (And also now from ESR) is that SCO distributed the Linux kernel under the terms of the GPL, and even if they were unaware that their code was contained in the kernel they are constrained by the terms of the GPL. It would seem to me that at best that is going to be a huge legal grey area, and at worst it plays directly into the hands of companies such as Microsoft, who have been saying all along that the GPL can "steal" your IP from under you. That would just prove them dead right, wouldn't it?
      Well, to me it would prove that the managers of an organization which released corporate property under a license they did not fully understand were incompetent, and liable to a shareholder/stakeholder suit for breach of fiduciary duty. To the best of my knowledge "we didn't understand" and "we did not realize the implications" are not permissible defenses in commercial contract law. Joe Homeowner can stand in front of the judge and claim that he was taken unfair advantage of by parties with greater knowledge/power, but a commercial entity is presumed capable of understanding its actions.

      The GPL is what it is. Call it "viral" if you like, call it "ideological", just don't call it late for dinner. Any organization considering releasing code under the GPL is free to have their legal counsel analyze it. Their legal counsel is free to do some research to determine what the possible implications of the GPL are. If the organization and/or its counsel fail to do their homework, I don't see how that can be interpreted as a failure of the license.

      sPh

    21. Re:GPL the best bet by denisdekat · · Score: 5, Interesting

      I am not a legal expert, but if you are proven to be negligent about any business data, last I checked, you are at fault really. For example. If I listed all of my customers on my website, I could not sue an ex-employee for using my customer list to do sales, since I make it public and available to all.
      I do not see how SCO could claim proprietary information on something they released under GPL.
      However, this country seems so corrupt anything is possible.

    22. Re:GPL the best bet by Anonymous Coward · · Score: 0

      I am a lawyer, an I think we should get together, because IalsoORAL...

    23. Re:GPL the best bet by Anonymous Coward · · Score: 0

      Perhaps.

      My argument is that people are currently running around and claiming that this is pretty much a cut and dried case, and SCO has lost already. "There is no SCO code in Linux. Even if there was, SCO distributed Linux, so the code in question is under the GPL. QED" is the basic argument. Even ESR is using it now.

      It isn't going to be as simple as that. This is a huge legal grey area here people. There are very few legal cases with this weird sort of "loopback" effect we see with SCO & Linux. It isn't as clear as people would like it to be.

      On top of that, it would still play straight into the hands of Microsoft and their "Viral GPL which steals all your IP and eats your babies" FUD. If the argument is a defence of Linux then it is a very valid offence against Linux, too! If you thought hardware support in Linux was a little patchy now, just you wait until after that argument is accepted in a court of law! Drivers will be pulled from websites faster than you can type rm -rf *.

      Either way, people need to be sensible about this. SCO may or may not have a claim to code which is in the Linux kernel. SCO may or may not have licenced that code when they distributed Linux. It certainly is not a simple case of "loosers weepers" though.

    24. Re:GPL the best bet by hendridm · · Score: 1

      > As for the GPL, I really do not think it holds water if somebody misappropriates your code, inserts it somewhere in linux and you unknowingly release it.

      Yeah, I didn't know the weed was in the glove compartmant officer. I borrowed this car from a friend.

      :)

    25. Re:GPL the best bet by deanj · · Score: 2, Interesting

      I think SCO stop distributing Linux as soon as they realized they wouldn't be able to go after other companies using their IP, when they were giving their IP away.

      re: the GPL and IP thing. They're doing just that. There was a story about it on /. a couple of days ago. Who *cares* if Microsoft tries to use their FUD about all this? They're going to do it no matter what happens anyway. They're doing whatever they can to make sure that Linux gets a good ol' screwdriver right in the chest, and they're trying to help twist it.

      Bottom line: The lawyers (or whoever) that are in charge of IP at SCO screwed up, and they screwed up big time. They never should have released the code under GPL if they wanted to protect it later on down the line.

      Going back and trying to reassert what ever rights they think they have isn't going to work. This is like putting code out in the public domain and then trying to turn around and stop everyone from using it. Too late. Too bad.

    26. Re:GPL the best bet by Anonymous Coward · · Score: 0, Insightful

      2: Every piece of "FUD" about the GPL will be proven--it IS a viral license, that can irrevocably infect your code without your express wishes.

      It is no more viral than any commercial NDA'd source license. The viral nature of their source license is the whole basis of SCO's case. If the GPL is a virus, then MS' "shared source" and SCO's Unix license are the bubonic plague.

    27. Re:GPL the best bet by pe1rxq · · Score: 1

      I am not arguing that all of SCO's code is under the gpl...
      SCO is claiming that the linux kernel contains their trade secrets. They distributed this code including the alledged trade secrets themselves.
      Just redistributing it in good faith is no protection since you have to agree to the GPL in order to be allowed to redistribute it. (Until you agree to the terms of the GPL the source falls under normal copyright and you can't distribute it without written permission blah, blah blah)
      So they should have read the GPL... and one of the things stated in the gpl is that you give the recipient the right to redistribute it again.
      If they distributed it in good faith without knowing that any of their trade secrets are in and that all recipients were allowed to use them they obviously didn't read the GPL and weren't allowed to distribute it in the first place.

      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    28. Re:GPL the best bet by st0rmcold · · Score: 2, Interesting


      IMHO, I think SCO is at fault, "not knowing" is no excuse in court, they distributed Caldera, if they wanted to distrubute code without knowing whats in it, hence giving it a blind license, they can't claim that they didn't know. It was their responsibility to look at the code in Caldera to make sure that everything in there belonged there, before they license it with GPL and give it away. If they would of been doing that, the copied code would have been spotted right away and it would of been solved then, but they have been distributing this OS for quite some time, and now claim that they didn't do quality control, it's not anyone elses fault.

      They don't belong in the OS industry if they can't even manage their own releases, and/or know what it even does.

      --
      Posting useless rant since 2003.
    29. Re:GPL the best bet by theLOUDroom · · Score: 2, Insightful
      Their argument for this claim will be "we didn't distribute it; we had no knowledge." Denying them this would do two things.
      1: Hackers can now put words in the mouth of corporations. (See? MSDN got hacked and folk downloaded GPL'd Windows, so now it's all free!)
      2: Every piece of "FUD" about the GPL will be proven--it IS a viral license, that can irrevocably infect your code without your express wishes.


      1. They did distribute it, they're a member of UnitedLinux fer chrissakes.
      2. That they continued to release the code under the GPL, after they filed this lawsuit.
      3. 1 & 2 Combined means, that they knowingly distributed the code under the GPL, therefore agreeing to its terms.
      --
      Life is too short to proofread.
    30. Re:GPL the best bet by Anonymous Coward · · Score: 0

      Then what the heck are you claiming? You seem to want it both ways; you say that the SCO code is not under the GPL and then try to argue that SCO is S.O.L because they distributed code under the terms of the GPL. Which is it?!

      My entire point is that just because SCO distributed the Linux kernel it does not automatically follow that the code they claim is in the kernel is also legally under the GPL. It is a legal grey area, and never been tested.

      Maybe you could clarify your position a little. Do you believe that any SCO code in the kernel is under the GPL or not? Thats a simple Yes or No question for you.

    31. Re:GPL the best bet by Anonymous Coward · · Score: 0

      I have a copy of UnitedLinux from SCO when they were called SCO which I was given by an SCO representative at LinuxExpoUK2002 in London. It was a beta of unitedLinux disk1.

      Plainly printed on it is SCO. not caldera.

      - Of course there is no way i'd go anywhere near a linux or unix from SCO now and so the UnitedLinux disk they gave me is doomed to be a coaster for the rest of its natural life.

      Cheers for the coaster anyway SCO, shame you seemed so nice and friendly at the expo. Who knew that not a year later you'd be trying to hold us at gunpoint.

    32. Re:GPL the best bet by TFloore · · Score: 5, Insightful
      1: Hackers can now put words in the mouth of corporations. (See? MSDN got hacked and folk downloaded GPL'd Windows, so now it's all free!)

      Of course not. Only when a corporation purposely distributes code does this become an issue. They may not knowingly distribute it, but they purposely distribute. There's a lawyer term that relates here, due diligence, that basically means that a corpoartion has a duty to their stockholders to make sure they aren't doing something stupid by a purposeful action, such as releasing trade secrets under an open license. If SCO really did purposely publicly license trade secrets under an open license, even unknowingly, there may actually be grounds for a shareholder lawsuit against SCO for not being properly cautious about such a public licensing. Note that this would be a bad thing for Open Source in general, as most companies don't have the resources to properly examine, what, 5 million lines of source code for the software in a normal linux distribution. And therefore the proper "safe" response may be to not use linux, even internally.

      2: Every piece of "FUD" about the GPL will be proven--it IS a viral license, that can irrevocably infect your code without your express wishes.

      Yes, the GPL is viral. It is meant to be viral. Stallman did that on purpose. No, it cannot infect your code without your wishes. But it can without your informed intent, if you are not properly careful of what you are doing. Again, due dilegence.

      Actually, assuming SCO has a valid case in this lawsuit, I don't really see a problem with both viewpoints on this...

      If IBM really did release SCO IP in kernel patches, then IBM is liable for violating a NDA, and there should be consequences for that.

      However, at the point that SCO (or Caldera after they bought SCO) released that IP in their own linux distribution, liability for other users/distributors stops.

      That (assumed) window between IBM releasing SCO IP, and Caldera (as SCO owner) releasing that same IP under an open license, makes for some interesting possibilities for legal rulings for other distributors.

      Oh, and I like your sigline, but really... Cadbury creme eggs *are* heavenly.
      --
      This is my sig. There are many like it but this one is... Oops. Frank, I've got your sig again! Where's mine?
    33. Re:GPL the best bet by ecki · · Score: 4, Informative

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

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

    34. Re:GPL the best bet by pe1rxq · · Score: 2, Insightful

      Yes, Any SCO source code in linux kernels distributed by SCO is under the gpl.

      As explained earlier if they didn't agree with ALL the terms of the GPL they couldn't have distributed it.
      And since they did it is no longer a trade secret and everybody can use the intellectual property in it.

      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    35. Re:GPL the best bet by Planesdragon · · Score: 3, Insightful

      "not knowing" is no excuse in court

      IANAL(RU), but I was taught (by lawyers) that intent is as improtant as action.

      The way I see it, if SCO's code is in fact in Linux, then "Us" would have to prove that it's common practice to examine all of the source code for an OSS distribution (it isn't), that SCO didn't do so (which they obviously didn't), and, probably, that they continued to distribute Linux with their code after knowing that it was "theirs."

      They don't belong in the OS industry if they can't even manage their own releases, and/or know what it even does.

      OSS is built on trust and re-use. If we (that is, folks who use any OSS at all) had to examine every bit of source code, then OSS would grind to a gut-wrenching hault. At best, we'd have locked-down distrubtions with a small fraction of the software that they have now.

    36. Re:GPL the best bet by Anonymous Coward · · Score: 0

      Yes, Any SCO source code in linux kernels distributed by SCO is under the gpl.

      At least you now have a clear position, even if I believe you are jumping the gun, making you guilty of the very thing I am arguing to you.

      Why did you earlier state that you did not believe that the SCO code was not under the GPL though?

      if they didn't agree with ALL the terms of the GPL they couldn't have distributed it

      Yes that is true, and my argument still stands; this is a legal grey area where their IP may or may not now fall under the GPL even though they unknowingly distributed it. If SCO were to claim that they did not agree to the GPL in full then that is a seperate action that Linus and the other copyright holders must undertake against SCO for infringment.

      And since they did it is no longer a trade secret and everybody can use the intellectual property in it.

      Which only follows if it is established that the SCO code is now under the GPL. Which as I argue, it may not be.

    37. Re:GPL the best bet by sigsegv · · Score: 1
      2. ???

      To quote for an old(ish) cartoon...

      2. Then a miracle occurs

      -sig

    38. Re:GPL the best bet by joak · · Score: 1

      A company that publishes its own trade secrets is pretty much hosed regardless of the license, isn't it? They're required to make reasonable efforts to keep them confidential, which presumably doesn't include selling them publicly. I don't think the "we didn't know about it" argument would hold up--if they want to keep it secret, it's the company's responsibility to know about it.

    39. Re:GPL the best bet by Anonymous Coward · · Score: 0

      I hold in my hands a 3-CD set entitled "SCO Linux Server". That's right, they released GPLed code under the name of SCO. Yes, they were bought by Caldera and continue to operate our of the Lindon Utah based Caldera offices, but they have released Linux code under the name of SCO. However, I do not konw if this release includes some of the Unix code in question. It most likely does not.

    40. Re:GPL the best bet by grahamm · · Score: 1

      The only way that the GPL can be 'viral' and cause an IP owner to lose control of the IP is if they (not anyone else) release under GPL code containing their IP. So unless MicoSoft intend to release any software under GPL they are immune from what they call the 'viral' nature of the GPL.

    41. Re:GPL the best bet by st0rmcold · · Score: 4, Insightful


      No, you are completly missing the point, don't know how it's very simple.

      SCO is a distributor, it's not the user's fault, nor will he ever be held liable to using a product that was legitimatly licensed software given to him.

      SCO IS LICENSING THEIR GODAMN OS!, you're damn right that everyone that licenses through the GPL SHOULD KNOW EXACTLY WHAT's IN IT! this has nothing to do with joe blow linux user, this has to do with distributors who create and release this stuff, sometimes for a profit, sometimes for not, it's their responisbility. Total bullshit that a company can claim they didn't know what the fuck they were licensing.

      Every godamn linux distributor should be inspecting their releases, if they waive that right, they also waive the right to sue for infrigement, if something in that release happened to be one of their trade secrets. This is not the case if someone else does it, if I take SCO's code and implement it, I am at fault, and redhat can't be held liable for my contribution, only I can be held liable. But if SCO dosen't check their own stuff, they just download source and give it out as GPL, that's their problem, cuz they actually own the IP, so they are giving their consent by waiving the right to look at it, even if it was taken from under their nose.

      I'm not condoning this action, but I am saying if your own IP, you need to always look carefully at your releases to make sure you don't go releasing it to the public, cuz after that it's too late, and you shouldn't be able to claim damages.

      That's the risk you take by owning IP and contributing to open source, it could be SCO employees that put the code in, no one really knows, but since SCO gave it out themselves, it's their fault, regardless of who actually put it in the OS.

      This is not a hit on the open source model, because it's clearly a grab at cash, linux will survive in the splendor it is, exactly because of the copyleft, and the fact that if you assign it GPL, you are giving it away, wether the fuck you know what in it or not!

      --
      Posting useless rant since 2003.
    42. Re:GPL the best bet by dh003i · · Score: 2, Informative

      Actually, no. The GPL does not state that corps caught with GPL'ed code in their proprietary software have to GPL their entire program. They have to EITHER GPL their entire program, or REMOVE all of the GPL'ed code from their proprietary program. Their choice.

    43. Re:GPL the best bet by pe1rxq · · Score: 1

      Why did you earlier state that you did not believe that the SCO code was not under the GPL though?


      I never did...
      Look at my original post:


      It doesn't matter whose copyright was on it, even who wrote it...
      They distributed the code under the gpl allowing everybody to see it and thus they have no legal base at all with respect to trade secrets.
      In other words: It can't be a secret if you are telling everybody who wants to listen about it.


      It does not say that SCO has no rights to the code. It just says that they licensed it to others under the gpl (they might still own part of it and can distribute it under other licenses as they see fit). And thus that if there were any trade secrets in it they are spread to the world themself.


      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    44. Re:GPL the best bet by cens0r · · Score: 1

      So you think all the people who distribute Linux do a line by line audit of the source code before every release?

      --
      Jack Valenti and Orrin Hatch will be first up against the wall when the revolution comes.
    45. Re:GPL the best bet by Anonymous Coward · · Score: 0

      I never did...

      I am not arguing that all of SCO's code is under the gpl...

      Best call in Mulder and Scully!

    46. Re:GPL the best bet by spitzak · · Score: 1
      I agree that they can claim the GPL release was a "mistake". However they must now actively act like it was a "mistake" and try to fix it. This means they must immediately release complete information about where the infringement is so all users of the GPL'd code can "fix" it. The longer they don't do this, the stronger the GPL release case gets.

      As for the FUD about the GPL, the results are identical no matter *what* license they released their Linux under. It would be the same if they used BSD or they put it in the public domian, or even if they signed a NDA with somebody for it and later realized that person should not have access to the code.

    47. Re:GPL the best bet by Planesdragon · · Score: 2, Insightful

      SCO is a distributor, it's not the user's fault

      I didn't say it was the user's fault.

      What I said was, SCO either is making a spurious claim (yay for everyone except them), carrying out a 'GIF switch' with the wrong law (yay for everyone except them), or going to court to stop the distribution of their code which they didn't know about, which could suck.

      If they go to court, and their claims of fact are found to be true, and no procedural faults stop them (i.e. "you distributed your code for 5 minutes after your CPO knew about it"), OSS winds itself up in quite a pickle.

      * If the unwittingly-added code is found to be properly GPL'd, OSS is "viral" and disgruntled employees can wreack havoc with any proprietary software that they want.

      * If the unwittingly-added code is removed from the GPL, OSS companies have the hassle of removing all of the effected modules from their systems.

      This has the potential to be rather thorny, and FSF zealotry won't help the matter much.

      That's the risk you take by owning IP and contributing to open source, it could be SCO employees that put the code in, no one really knows, but since SCO gave it out themselves, it's their fault, regardless of who actually put it in the OS.

      If SCO knew that the code was theirs and continued to GPL it, then those GPL's are viable and ironclad. If they made all necessary steps after learning that their code was in Linux, and they didn't put it there, then the status of the "GPL'd" code is in doubt.

      This is a murky situation, requiring lawyers and judges and a jury or three. (IANAL, of course--but if you didn't know that already, you're probably delusional.)

    48. Re:GPL the best bet by chasm!killer · · Score: 1

      I don't think so.

      If an officer of Microsoft Corporation was authorized by the board to distribute the souce code to Windows and was acting in his capacity as an officer of the company when he did in fact hack MSDN and put GPL licenses and the Windows souce code up there, I would say that in fact it would be free. I think any US court would agree, too. It would be odd for him to do it that way instead of just instructing the webmaster to add the page in his normal work schedule, but perhaps that's because Bill wanted to REALLY SUPRISE everyone! Or he just wanted to prove he could still hack MSDN.

      And as far as the viral nature of GPL: it is a viral license to that extent and it was intended to be so. It does not allow any code you have explicitly released to be withdrawn. I don't believe I have signed any contracts that gave me rights like that in the last 40 years. And I don't think any corporate lawyer should let his clients sign a contract to use software that did not include such a prohibition. Do you think Walmart would install cash registers with the posibility that they would be liable for copyright violation any time SCO, or whoever, wanted to change the license?

      --
      -- Ancient (IBM 1620 and Atari 400) Programmer
    49. Re:GPL the best bet by jedidiah · · Score: 1

      At the very least this demonstrates that SCO failed to release a product without a meaningful code review.

      Either they knew of this problem 3 months ago when they were still distributing the infringing product, or they managed to "magically" find out about this problem in the last 3 months.

      At the very least, they're contradicting their own filing against IBM.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    50. Re:GPL the best bet by mark_lybarger · · Score: 1

      Do you think Walmart would install cash registers with the posibility that they would be liable for copyright violation any time SCO, or whoever, wanted to change the license?

      would anybody create gif images without having a license? nah, i wouldn't think so...

    51. Re:GPL the best bet by jedidiah · · Score: 2, Insightful

      OSS practices really have nothing to do with this.

      This is a commercial software company. The development practices of such companies are what is relevant here. Did they exercise the standard of care in their industry? Did they exercise the standard of care that they are claiming in their filing against IBM?

      If it weren't for their claim against IBM, which includes an affirmative claim about the quality of their own development process, I would say that SCO stood a better chance of claiming reasonable ignorance.

      IBM could also provide a parade of OS developers to claim that code review is infact a common standard of care in OS development.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    52. Re:GPL the best bet by st0rmcold · · Score: 4, Insightful


      It's as if I give you an old table I found in my basement, and you find a gold bar in one of the legs. Can I sue you to get it back because I didn't know that it was there? No, because it's yours and myfault for not inspecting the table beforehand to ensure I was only giving away the table. You came over, and I gave you the table, end of discussion.

      Exact same concept here, SCO is responsible, intent is irrelevant here, because it's not even criminal, it's civil. Someone else "might" have put some code belonging to SCO in the linux kernel, Caldera knowingly kept licensing linux for years, without even knowing what's in the kernel, like I said earlier, waving the right to claim that it's not their fault, wether they meant to do it or not, it's negligence, and they shouldn't be rewarded.

      They want money for damages ages after the actually offense happened (I'm assuming it did in this case) and they don't want to take any blame for purposly continuing to contribute to it.

      What I am saying here is that they are clearly at foul, and this is most likely pointing to a case of money hungry conglomerates. I mean, you can defend them all you want, but if you want to look at it in a logical sense, they were stupid, and gave away their own shit, copyright dosen't excuse stupidity, nor should the courts.

      --
      Posting useless rant since 2003.
    53. Re:GPL the best bet by jedidiah · · Score: 1

      You're ignoring SCO's other claims in this matter.

      They have made affirmative claims to the court that they employ a superior and more highly organized development process relative to Linux.

      Now, they are in a situation that requires the court to believe that SCO acted reasonably while not bothering to examine a software product that was going to be stamped with the SCO name.

      SCO really can't have it both ways. A savvy judge will realize this.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    54. Re:GPL the best bet by drinkypoo · · Score: 1
      As for the GPL, I really do not think it holds water if somebody misappropriates your code, inserts it somewhere in linux and you unknowingly release it.

      While this is just more meaningless speculation (even a lawyer can't answer this question for you because it can only be decided in court) it seems that this quite easily would make that code GPL. If you release someone else's code with GPL, that doesn't make that code GPL, because you didn't own the copyright to begin with. However, if it's your code, and you release it under the GPL, then... you released it. The burden is on you to know what you're releasing.

      While this probably WILL scare companies away from FoOSS for no particular reason, this is only really a problem with very large codebases. You don't generally release a product as GPL unless that is really your intent. When SCO acquired Caldera (for some reason I had thought it was the other way around... Maybe I was just lost) they began distributing Linux. That's a fact. It was their code, and by distributing it under the GPL, they created a GPL-licensed fork of their code. (Assuming, of course, that any of their code was actually in there, which has not been proven.) They might have the right to sue whoever put it in there for their losses between the time it was inserted into the linux kernel, and the time they started distributing it themselves, that makes sense anyway.

      Of course, since the code allegedly deals with features which SCO Unix does not even have, you could argue that their losses total $0, and 0 multiplied by anything is still 0, so it doesn't really matter what the time period is. That probably won't wash though; The question becomes, if Linux stole customers from SCO because it had features derived from SCO-owned code, how many customers did it steal? I think the only Linux feature that has ever really stolen customers from SCO (As opposed to "stealing" them from other FoOSS OSes) is iBCS' SCO compatibility, which doesn't contain SCO code, though it does require use of the SCO libraries, which requires a SCO license... Which SCO gave out for free to people for quite some time.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    55. Re:GPL the best bet by jedidiah · · Score: 1

      If they are in a position to lose intellectual property by failing to do so: YES.

      Now, this doesn't necessarily need to be the WHOLE kernel. Certain obvious things can be left out (like the bttv module) in order for due dilligence to occour.

      However, people/companies have a responsibility to look after their own best interests in order to avoid future trouble. A company like SCO should at the very least review those parts of the kernel that are more likely to include SCO property.

      This is just the CYA argument.

      There is also the issue of taking responsibility for the code you're releasing as well as being able to service it. This of course demands some non-trivial familiarity with the Linux kernel.

      IOW, if you are presenting yourself as some sort of RedHat you damn well better be familiar enough with the kernel to know if it's been contaminated. That's really the only reason to pay for a commercially branded version of Linux.

      Any IT grade commercial Linux distributor should be a reasonably effective Sun wannabe.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    56. Re:GPL the best bet by jedidiah · · Score: 1

      No patent claims have been made as of yet.

      Also, if SCO does attempt to make a patent claim. The result will be much like a mosquito running into a tractor trailer.

      IBM is the tractor trailer of patents.

      SCO is a mosquito at best (in any area one would care to contemplate).

      --
      A Pirate and a Puritan look the same on a balance sheet.
    57. Re:GPL the best bet by jedidiah · · Score: 1

      That certainly will be consolation for them when they are standing in line at the unemployment office.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    58. Re:GPL the best bet by chasm!killer · · Score: 1

      Ah so!

      Honorable Mark may have a really good point there (I don't have a license or GIF on my web site, but I bet I'm in the minority there, one way or the other ....).

      --
      -- Ancient (IBM 1620 and Atari 400) Programmer
    59. Re:GPL the best bet by HiThere · · Score: 1

      But Caldera is the same company. They merely changed their name after they acquired SCO. So the company that is now SCO issued their own Linux.

      OTOH, since nobody knows just what is being challenged, it could be that nothing included with their Linux version is covered. We don't, and by their intention can't, know. They won't tell us. (Yeah, SCO sent out threatening letters, but that doesn't prove anything about what the court filing is... and within a week MS has purchased a license, which doesn't prove anything except that MS can't be sued for whatever it is the license covers.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    60. Re:GPL the best bet by Planesdragon · · Score: 1

      It's as if I give you an old table I found in my basement, and you find a gold bar in one of the legs. Can I sue you to get it back because I didn't know that it was there? No, because it's yours and myfault for not inspecting the table beforehand to ensure I was only giving away the table. You came over, and I gave you the table, end of discussion.

      Let's say that you're a mover, and Bob is the guy I'm selling the table to. You come in to move the table, steal a gold bar, and put it into the table. LATER, I sell the table to Bob--and shortly after (say, while it's still in your truck) I discover that you put the gold bar there, and I immediatly come to get it back.

      Do I get it? I have no idea--but my sense of ethics says that I should, as I knew about the bar, it was my bar, and it was transmitted to you without my knowledge, or your knowledge, by the fraud of another.

      Move away from physical goods, throw in copyleft, and I suspect the darn thing just gets more complex.

    61. Re:GPL the best bet by Anonymous Coward · · Score: 0

      MS has purchased a license, which doesn't prove anything except that MS can't be sued for whatever it is the license covers.)

      Doesn't prove that at all. It could just be that SCO is out of money, and Microsoft is essentially paying them to allow the lawsuit to continue, without creating the possibly dangerous corporate connection to SCO that a buyout would provide.

    62. Re:GPL the best bet by rifter · · Score: 1

      Trade Secrets are not trade secrets if they are revealed. BUt if the revealer is breaking a contract, they are still liable for their actions. Your NDA example is also misleading. The NDA does not apply if it is broken? That would render them useless. The whole point of an NDA is that it provides remedies if it is broken. Therefore it certainly still applies.

    63. Re:GPL the best bet by fredrik70 · · Score: 1

      Question is though, wouldn't SCO have to put their copyright comment on the pieces that were theirs in the kernel? if they're not there and one can prove that it is their code, I'm not too sure the GPL stands.

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    64. Re:GPL the best bet by cens0r · · Score: 1

      the only problem I have with this is that it's so hard to do. Not only do you have to be very familiar with the linux kernal, you also have to be familiar with the other source (in this case the SCO code). The biggest down side I see is that once you've found this person(s), they can no longer really be used to develop code for you because they're knowledge of both systems could easily lead to contamination.

      Also, assuming IBM did in fact break the NDA, why would SCO be pouring over any source that IBM contributed. I wouldn't find it odd if they assumed that IBM was following the terms of the NDA and didn't audit that code closely.

      --
      Jack Valenti and Orrin Hatch will be first up against the wall when the revolution comes.
    65. Re:GPL the best bet by GlassHeart · · Score: 1
      It's as if I give you an old table I found in my basement, and you find a gold bar in one of the legs. Can I sue you to get it back because I didn't know that it was there? No, because it's yours and myfault for not inspecting the table beforehand to ensure I was only giving away the table.

      Possibly. Let's modify the analogy to suit the case a little better.

      Let's say the table has a secret compartment, just like a large base of code like a Linux distribution is nearly impossible to inspect thoroughly. Let's say another person stole your bar of gold from your safe, and hid it in the table that you gave me.

      What do you think now? Should you suffer the loss of that gold bar?

    66. Re:GPL the best bet by Anonymous Coward · · Score: 0

      They should. It's their problem if they don't.

    67. Re:GPL the best bet by st0rmcold · · Score: 1


      In a personal case, this might hold up, but if you sell tables for a living and people put gold bars in all your tables, and you don't inspect them, then yes, you suffer the loss. You're putting your quality control stamp on the table saying it's legit and ready to go, you can't take that back afterwards, it's your fault for not inspecting what you sell.

      If the table comes out clean from inspection after the production line, and then (movers) stick something in it onthe shipment process, then it's different, but if right off the production line, then yes it's yuor fault. Joe blow should lose his gold bar, because it was in the table all along, and he didn't take a look at it before giving it away. The case you say would be someone putting something in it during the moving process and that's anot story, cuz the owner has no way of knowing, there was a third party. This is directly SCO approving code and giving it out under a license, I think it's 100% their fault. If they wanted to milk this cow they had to do it long time ago.

      --
      Posting useless rant since 2003.
    68. Re:GPL the best bet by kalimar · · Score: 2, Interesting
      Again, point missed.

      If they are indeed going to court to stop the distribution of code which they did not intend to distribute, but still did, then you know what, they lose. They are a vendor. If they don't know what is in their product, they are idiots. If they didn't take the time to find out what was in their product, they're careless.

      * If the unwittingly-added code is found to be properly GPL'd, OSS is "viral" and disgruntled employees can wreack havoc with any proprietary software that they want.


      Bad example. The actions of disgruntled employees are a separate issue. If it was a disgruntled employee that released proprietary information, there are a barrage of different issues at stake (like when was this purported employee released, why did it take so long to find this problem, etc). At the end of a case of disgruntled employee doing something, they have every right to retract the leaked information. I'm not sure if it can still be considered a trade secret, but it is most definitely still under whatever copyright the employer wants it to be. But we're not talking about the "what if's" of a disgruntled employee. We're talking about a company that should've known it's code was in there, could've known earlier if the code was in there, but did nothing about it until it realized that it was a rodent and about to be exterminated.

      The main thing that needs to be considered is:
      Caldera released a product under a license. Since, we can assume that code review was done (see above about not knowing what is your product and being an idiot), we can also assume that the product passed said review and was authorized to be released with the appropriate licenses. As a result, said proprietary information was approved to be released under GPL and thus made non-proprietary. End of story.

      Regardless of whether or not SCO knew the code was theirs. If they did, then this lawsuit is thrown out and SCO punished for being gits and wasting the courts time. If they didn't know, then this lawsuit is thrown out and SCO punished for being idiots and wasting the courts time.

      As for your last point, such is life. If it is found that proprietary code was released thus exposing trade secrets, I would think that several things would have to happen:
      1. The date of the release would need to be determined
      2. All new code created after that release date would need to be examined
      3. Changes would have to be made


      However, given the information in the linked position paper from the Open Source Initiative, I am sure that SCO is toast. But now it's up to a court to decide how serious a case of cranio-rectal inversion SCO has.
    69. Re:GPL the best bet by foolip · · Score: 1
      They have to EITHER GPL their entire program, or REMOVE all of the GPL'ed code from their proprietary program. Their choice.

      ... If a corporation has code which they recieved under the GPL in a product of theirs which they distribute and someone found out, then they'd be in a bit of trouble. What would happen is that since the corporation is distributing under a non-GPL license, their rights to the GPLd code automatically becomes null and void, and they can chose, as you say to either comply completely with the GPL, or remove the code in question.

      Recall however that the same code can be distributed under many different licenses if the copyright holders want to, so me licensing a few hundred lines of my (no one elses!) code to you under the GPL doesn't mean that I can't use that code in my proprietary software product. So if SCO's code has gotten into the kernel and they accidently redistribute it (which I understand isn't the case, but let's pretend) the only legal effect would be that that precise code is now under the GPL. But if someone has taken SCO's code unlicensed (don't say steal) and put it into the kernel, then that person is not the copyright holder of that code, and could not place it under the GPL in the first place. As a consequence, the GPL for that code is again null and void, and it would have to be removed from the kernel.

      If software patents are involved... well I don't know. Just recall that the GPL requires any patents on code to be licensed to all third parties for any use at no royalty-fee, so if SCO has distributed GPLd code for which they hold patents and don't allow this, then once again the license becomes void, and removing the affected code should be the solution.

      Don't trust my word for it though, I don't really know what sort of claims SCO are making (can't be bothered to read all these articles), so the situation may be somewhat different

    70. Re:GPL the best bet by schon · · Score: 1

      "we didn't distribute it; we had no knowledge."

      At one time, this may have been a valid concern, but if you look closely, they're still distributing it

      So they'd be pretty damn hard pressed to convince someone that they are immune from the GPL.

      Every piece of "FUD" about the GPL will be proven--it IS a viral license, that can irrevocably infect your code without your express wishes.

      No, it wouldn't. They are still distributing it, so by definition they are aware of the code. Nothing is being "taken" from them - they're giving it away themselves.

    71. Re:GPL the best bet by Anonymous Coward · · Score: 0

      I like the GPL, but please note that BSD or any other free-software license would have the same result in this case
      Not from a practical point, because without the GPL the source code to proof it would not be open, so we would have to deal with trade secrets and NDAs to establish it.

    72. Re:GPL the best bet by dh003i · · Score: 1

      so me licensing a few hundred lines of my (no one elses!) code to you under the GPL doesn't mean that I can't use that code in my proprietary software product

      This is true, but it only applies to you -- the developer of those particular lines of code. You, the developer, license your specific code in as many different ways as you want. However, once it's released as part of a larger program under the GPL, that is there permanently. You can still license it in parallel under a EULA, but there's also an identical version licensed under the GPL. Public-domain type licenses are one-way: you can't take something out of what is effectively the public domain. Once you license code under the GPL, you can't then prevent others from distributing that code under the GPL.

    73. Re:GPL the best bet by MonopolyNews · · Score: 2

      my impression is that a court will be sympathetic to the argument you give above. That's why Boies et al. had them stop shipping Linux. HOWEVER. They have promised to idemnify their own customers. IE. they have given their own customers permission to continue to use Linux, released under GPL. That means they they ARE willingly putting their IP under a GPL license and that is that! Their clients can redistribute it. They cannot claim it's secret. AND furthermore: they are distributing linux to their customers illegally unless their IP is also under the GPL (since they are talking about blocks of code within GPLed modules!) On the other hand they have Boied so you can continue to worry if you are so inclined.

      --

      Slashdot Journal on Monopoly News
    74. Re:GPL the best bet by MonopolyNews · · Score: 1

      as I posted above, I think you are right. However, SCO is promising their own customers indemnity... that code is still distributed under the GPL, so their IP is under the GPL. They would have to not only stop selling Linux, but to RECALL their distros (or patch them).

      --

      Slashdot Journal on Monopoly News
    75. Re:GPL the best bet by schon · · Score: 1

      if it is a patent violation

      First, if it was a patent violation, someone at SCO would have said so - so far, all they've alleged is copyright (Darl McBride - "we have found instances where the code was copied verbatim") and some nebulous "IP" infringement (which amounts to "look and feel".)

      Second, even if this did turn out to be about patents, SCO still has no legal leg to stand on, as Section 7 of the GPL clearly covers this.

    76. Re:GPL the best bet by dvdeug · · Score: 1

      Actually, no. The GPL does not state that corps caught with GPL'ed code in their proprietary software have to GPL their entire program. They have to EITHER GPL their entire program, or REMOVE all of the GPL'ed code from their proprietary program. Their choice.

      No. By doing so, they've committed copyright infringement. They can either make a deal with the owner of the infringed code, or go to court. They cannot unilaterly fix it.

    77. Re:GPL the best bet by dvdeug · · Score: 2

      "Us" would have to prove that it's common practice to examine all of the source code for an OSS distribution (it isn't)

      It is common pratice to have some idea what you're sending out. Speaking as a Debian developer, there are people who argue and practice that a developer should read every new line in every update, including Branden, our X developer. (I've done it, but mainly because I'm small fry.) To be completely ignorant of what you are sending out is ill-advised.

    78. Re:GPL the best bet by watzinaneihm · · Score: 1

      Maybe it is working for SCO. But for Microsoft it seems like negative to neutral publicity.The google news starts with a story of MS playing hardball (on the frontpage that too) and then about the OSI "tearing down SCO claims " article (linked from /.)

      --
      .ACMD setaloiv siht gnidaeR
    79. Re:GPL the best bet by dh003i · · Score: 1
      Actually, no. The GPL does not state that corps caught with GPL'ed code in their proprietary software have to GPL their entire program. They have to EITHER GPL their entire program, or REMOVE all of the GPL'ed code from their proprietary program. Their choice.

      No. By doing so, they've committed copyright infringement. They can either make a deal with the owner of the infringed code, or go to court. They cannot unilaterly fix it.

      Actually, within the GPL, there are clauses verifying what I say. Even if what you say were true, they could still remove the GPL'ed code from their code all-together -- they do *not* have to GPL their code.
    80. Re:GPL the best bet by MonopolyNews · · Score: 1

      a better version of this point is: SCO has promised to indemnify their users of linux. They have not recalled those copied. So in that act they ARE distributing their IP under the GPL (assuming generously that it's really there).

      --

      Slashdot Journal on Monopoly News
    81. Re:GPL the best bet by MonopolyNews · · Score: 1

      forget this nonsense about a viral GPL, it's not! Don't forget, it's GPLed code that's accused of being infected... the virus in this metaphorical case would be SCO's proprietary IP!

      --

      Slashdot Journal on Monopoly News
    82. Re:GPL the best bet by dvdeug · · Score: 1

      Actually, within the GPL, there are clauses verifying what I say.

      There are? Which ones? The only clause that comes close is #4:

      4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

      which says nothing about the subject, except that their license is terminated.

      Even if what you say were true, they could still remove the GPL'ed code from their code all-together -- they do *not* have to GPL their code.

      They might. A court might rule that they have to GPL their code, or the copyright holder might insist on it, with going to court having negative enough results that they are effectively compelled to do so.

    83. Re:GPL the best bet by GryMor · · Score: 1

      That only saves them from further infringement, it doesn't fix the infringement they have allready committed. In the case of derivative works, it is not unheard of for unauthorized derivative works to be turned over to the original copyright holders as part of the remedy of a copyright infringement suit (it's not normally what happens, but it has happened).

      --
      Realities just a bunch of bits.
    84. Re:GPL the best bet by styrotech · · Score: 1

      It is common pratice to have some idea what you're sending out. Speaking as a Debian developer, there are people who argue and practice that a developer should read every new line in every update, including Branden, our X developer. (I've done it, but mainly because I'm small fry.) To be completely ignorant of what you are sending out is ill-advised.

      That is true, but that claim your parent poster refuted went further than that. Does Debian (ie it's maintainers) cross check that incoming code against other code bases to see if it was 'stolen'. No of course not, they just check it for correctness.

      Not to defend SCO (may they rot in hell), but claiming they should've known would only apply if they added the code not a third party that isn't allowed to. I think SCO's case is without merit, but I don't think a court would uphold the unwitting GPL redistribution snag against them.

    85. Re:GPL the best bet by DASHSL0T · · Score: 1

      >> The GPL does not state that corps caught with GPL'ed code in their proprietary software have to GPL their entire program. They have to EITHER GPL their entire program, or REMOVE all of the GPL'ed code from their proprietary program. Their choice.

      But that is the reverse of what we have here. It isn't SCO with GPL code in proprietary software. it is GPL code with unauthorized (possibly) propietary software IN IT.

      I don't think that you can enforce GPL on the holder of said proprietary code and say "sorry, you have no claims because you didn't catch the fact that somebody was screwing you over during your code review".

      --
      Freedom Is Universal
      Linux-Universe
    86. Re:GPL the best bet by jedidiah · · Score: 1

      When you're protecting the crown jewels, losing one or two competent developers may not be such a bad trade off.

      While such a person would no long be able to be directly connected with the development of either kernel, such people could be used as a safe conduit for knowledge transfer. SCO could enhance Linux with "safe" binary kernel modules. SCO could also enhance SCO by stealing pure ideas from Linux.

      This is how the first PC BIOS was originally reverse engineered.

      Actually the more I think about it, the more sense it makes for such a team to be in place inside ANY organization that works with their own commercial OS as well as Linux.

      HELL, it may turn out that such an organization already exists inside of IBM and they're just waiting fire broadsides at SCO.

      Let us not forget that IBM also has all of the relevant source and they can perform their own in depth analysis.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    87. Re:GPL the best bet by dh003i · · Score: 2, Interesting

      Um, actually, no. There is no proprietary code in the Linux kernel or any other GPL'ed software. That's a bogus bullshit claim. If there was any validity to that claim, SCO would have published the offending lines of code. They haven't, so obviously they are full of shit.

      If a proprietary entity releases some of their software with unique GPL'ed code in it, then they're obligated to either release the entire thing under the GPL, stop offering the package, or remove the GPL'ed code. For lines of code long enough to be clearly copy&pasted or of clearly enough similarity to be directly modified GPL'ed code, they knew damn well what they were doing. The GPL license is not hidden -- it is made very clear on every piece of software that comes with it. There is no such thing as "proprietary developers accidentally using GPL'ed code". That's bullshit.

      No auditing is necessary for proprietary entities, if they follow simple procedures. For every piece of code they use that isn't theirs, they need to document where it came from and the license it was covered under. If they don't, that's their own fault, and it's too damn bad for them.

    88. Re:GPL the best bet by gandy909 · · Score: 1

      I think if something covered by an NDA is already disclosed by someone else to everyone then there is no longer a purpose for the NDA and it is relatively meaningless.

      --

      (Stolen sig) Remember: it's a "Microsoft virus", not an "email virus", a "Microsoft worm", not a "computer worm
    89. Re:GPL the best bet by MrResistor · · Score: 2, Insightful

      The way I see it, if SCO's code is in fact in Linux, then "Us" would have to prove that it's common practice to examine all of the source code for an OSS distribution (it isn't), that SCO didn't do so (which they obviously didn't), and, probably, that they continued to distribute Linux with their code after knowing that it was "theirs."

      SCO continued to distribute Linux even after filing the suit against IBM. Does that count as knowingly distributing their IP under the GPL? I think it does.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    90. Re:GPL the best bet by uniplex · · Score: 1

      Unknowingly or unintentionally distributing gpl'd code with a commercial license is one thing.. but sco _intentionally_ distributed a linux kernel and it's source code under the gpl. So really all I can say is that if infact sco's IP was in those sources, then by-golly hats off to sco for their contribution to linux and the open source movement.

    91. Re:GPL the best bet by bwt · · Score: 1


      SCO's intent was to licence Caldera Linux under the GPL to paying customers. What is your point?

      If they claim to not have understand the implications of what they were agreeing to, the law will basically turn a cold shoulder. Hell, even when the other side chooses the contract and you don't read it you are still accountable if you agree. If you were the side that chose it, you will lose every time.

    92. Re:GPL the best bet by DASHSL0T · · Score: 1

      >> Um, actually, no. There is no proprietary code in the Linux kernel or any other GPL'ed software. That's a bogus bullshit claim.

      Surely you jest. Nobody, anywhere, at any time, has swiped a single line of code from his employer and placed it in his GPL project? EVER??? That's a pretty broad and indefensible claim to be making.

      >>If there was any validity to that claim, SCO would have published the offending lines of code. They haven't, so obviously they are full of shit.

      Well yes, if they wanted to quickly get the code removed. However, if in reality they don't give a rat's butt about the code and instead they want to milk the situation for cash, they wouldn't and would take the offender to court. It's a scumbag move but it doesn't invalidate their claim. If their claim is invalid, the court will decide.

      >>If a proprietary entity releases some of their software with unique GPL'ed code in it, then they're obligated to either release the entire thing under the GPL, stop offering the package, or remove the GPL'ed code. For lines of code long enough to be clearly copy&pasted or of clearly enough similarity to be directly modified GPL'ed code, they knew damn well what they were doing. The GPL license is not hidden -- it is made very clear on every piece of software that comes with it. There is no such thing as "proprietary developers accidentally using GPL'ed code". That's bullshit.

      Once again, this is backwards. Additionally, even given the situation you outlined, there is no way an employer knows that developer John Smith didn't swipe code from a GPL product to meet his deadline and not tell anyone about it. Are they going to cross-check their code against the entire portfolio of open source software?

      Now when John Smith works for Microsoft and does that in Windows, do you think a court is going to declare XP is now GPLed? No, MS will simply have to remove the code and maybe pay damages. But this is still backwards. It isn't GPLed code in a proprietary product. It is ALLEGEDLY proprietary code in a GPL product.

      >>No auditing is necessary for proprietary entities, if they follow simple procedures. For every piece of code they use that isn't theirs, they need to document where it came from and the license it was covered under. If they don't, that's their own fault, and it's too damn bad for them.

      Sigh. You still have it backwards. SCO does it have it documented anyway. It came from (example) Kernel developer X. Now, who is liable? Kernel Developer X is. SCO certainly isn't going to be told by a court "oh, tough shit, now all your intellectual property is GPLed because of the actions of Kernel Developer X without your knowledge".

      --
      Freedom Is Universal
      Linux-Universe
    93. Re:GPL the best bet by bwt · · Score: 1

      No, "it's a mistake" doesn't cut it. Unless the code they distributed is, was, and stays licenced by the GPL they have mistkenly committed for-profit copyright infringement against every valid GPL contributor to the linux kernel.

      It's completely odd that they would claim their own infringement would be a harmless "mistake", while simultaneously asking for $1G for a similar mistake.

      Even if the worst case is true and IBM knowingly attempted to incorporate SCO code into the linux code, SCO stood by and continued to distribute and profit from the very code they claim is infringing while simultaneuously telling the customers who paid for that it was not only non-infringing but explicitly allowed to copy and modify the code.

    94. Re:GPL the best bet by Anonymous Coward · · Score: 0

      Me thinks you don't understand what is meant by the GPL being viral.

    95. Re:GPL the best bet by MonopolyNews · · Score: 1

      I do understand what it attempts to mean. It's a poor metaphor. Wait until it's resolved in court before beeing too glib.

      --

      Slashdot Journal on Monopoly News
    96. Re:GPL the best bet by nathanh · · Score: 1
      The GPL does not state that corps caught with GPL'ed code in their proprietary software have to GPL their entire program.

      Correct. The GPL states that if you accept the licensing agreement stated in the GPL then you are obligated to GPL the entire derivative work.

      They have to EITHER GPL their entire program, or REMOVE all of the GPL'ed code from their proprietary program.

      Very close. The reality is that they either GPL their entire program (aka, standard license) or negotiate something else with the owner of the GPLd code. This negotiation might result in removal of the code, it might involve money, it might involve fisticuffs and a lawsuit.

      The GPL is, afterall, a license. The terms of the license are "you may use this software for any purpose, profit or non-profit, but if you do anything that would infringe on copyright then you must GPL your product". But this only applies if you agree to the license. If you don't agree to the license then you are simply guilty of copyright infringement, same as any pirate.

    97. Re:GPL the best bet by Anonymous Coward · · Score: 0

      Does Debian (ie it's maintainers) cross check that incoming code against other code bases to see if it was 'stolen'. No of course not, they just check it for correctness.

      Indeed, SCO probably maintained a "Chinese Wall" between it's Linux and UNIX groups, which would make it pretty much impossible for developers to check Linux for UNIX source code.

      (Except in the context of a legal review. Such as the one preceeding this lawsuit.)

    98. Re:GPL the best bet by Art+Tatum · · Score: 1
      As they built up their "evidence" (which has yet to be publically documented in a satisfactory manner)

      Yep. My suspicion is that they're taking so long because they need the time to find some plausible things in the Linux kernel and integrate them into their own codebase. After that, who's going to be able to prove that it wasn't in there a long time ago?

      And why did they change their story, anyway? As far as I can tell, they started out with a charge that IBM simply used trade secrets. Now it's copyright? Hmmmm...

      On an unrelated note, what I want to read at this point is a frank positional summary by Ransom Love who is becoming somewhat conspicuous by his "absense" through all this mess.

      He's about the only one who isn't getting involved. With Microsoft and OSI jumping in on this, it's shaping up to look like the Battle of the Five Armies. Now we just need to hear from the Regents and resurrect USL for old times sake. Heck, maybe the RIAA and MPAA could even find a way to stick their oar in. One big happy quarreling family...

    99. Re:GPL the best bet by Anonymous Coward · · Score: 0

      But whether we call the entity SCO or Caldera, distribution continued until last week.

      I think that the most interesting point is that there was a period of a month or two (ending last week) during which a single legal entity (SCO) distrbuted linux (for a fee) while having strong suspicions that what they were distributing source code to which they were the rightful owners of the copyright. Under the terms in which they were distrbuting this source code, they were granting others the right to view, modify, and redistribute for free that source code, and to pass those rights along to others.

      It's just hard to get around it. Even if they hadn't been giving it away before the lawsuit, it is hard to see how they weren't giving it away after the lawsuit.

    100. Re:GPL the best bet by dh003i · · Score: 1

      Surely you jest. Nobody, anywhere, at any time, has swiped a single line of code from his employer and placed it in his GPL project? EVER??? That's a pretty broad and indefensible claim to be making.

      Single lines of code are almost always generic and cannot be claimed by anyone. Surely, somewhere in his body of work, Michael Crichton wrote, "I don't think so". That does not mean that when I write that, I am plaguarizing Crichton.

      It is much more likely that SCO is stealing code from GPL'ed products than vica-versa. After all, GPL'ed programs are open for everyone to see -- no-one's had a problem so far. However, SCO's code is proprietary and closed-source, so they could be stealing tons of code from GPL'ed and BSD'ed programs.

      if in reality they don't give a rat's butt about the code and instead they want to milk the situation for cash, they wouldn't and would take the offender to court. It's a scumbag move but it doesn't invalidate their claim. If their claim is invalid, the court will decide.

      Since their entire claim is bullshit anyways, this is moot. See the OSS' response to the lawsuite. In short, SCO's lawsuite asserts things that are misleading and down-right false, to such an extent as to be punishable under criminal law. Due to the broad falsity of their statements, they could also be civilally liable for defamation and slander.

      However, SCO gains nothing by not specifying which lines of code are in violation. Even if any of their claims were true, they could not claim right to extra damages from said defendants when they could have prevented those damages by telling the defendants which lines of code were offending, thus allowing the defendants to remove them.

      Additionally, even given the situation you outlined, there is no way an employer knows that developer John Smith didn't swipe code from a GPL product to meet his deadline and not tell anyone about it. Are they going to cross-check their code against the entire portfolio of open source software?

      Corporations have the rights of persons (a fact which is absurd). Thus, they should collectively have those same responsibilities. They shouldn't get to both eliminate individual responsibility and the overal corporate responsibility by playing a finger-pointing game. Companies are responsible for the actions of their employees on their watch. They're the one who hired them, thus made appropriate character judgements. If those in their company commit such unscrupulous actions, and they further it by marketing those products without checking, that's their responsibility.

      What your proposing gives a back-door to every corporation for any violatation of any license what-so-ever, by claiming the bullshit line that "they didn't know" and "an employee snuck in the code".

      Now when John Smith works for Microsoft and does that in Windows, do you think a court is going to declare XP is now GPLed? No, MS will simply have to remove the code and maybe pay damages. But this is still backwards. It isn't GPLed code in a proprietary product. It is ALLEGEDLY proprietary code in a GPL product.

      Nothing in the GPL says MS has to GPL windows if they "accidentally do such". (I state again, that there is NO accidental violation of the GPL...the individual who put in the code knew damn well what they were doing, and the company is ultimately responsible for hiring and trusting that individual). In any event, the GPL simply states that if you fail to abide by it, you no longer have the additional rights granted by it. Those additional rights cover the GPL'ed code. Meaning, you no longer have the right to distribute the GPL'ed code. You can still distribute your own code under whatever license you want, but not that GPL'ed code. So, you can either remove the GPL'ed code, stop distributing the entire program, or distribute it all under the GPL (actually, you technically can't distribute the original GPL'ed code anymore, unless granted the right to do so by a negotiation with the o

    101. Re:GPL the best bet by firewood · · Score: 1
      A court might rule that they have to GPL their code, or the copyright holder might insist on it, with going to court having negative enough results that they are effectively compelled to do so.

      Also likely (but IANAL) is that the court will just assess monetary damages for copyright infringement, maybe even treble damages. Let's see... GPL requires you to give away the source for free, to first approximation, for anyone to recompile;

      and 3 times 0 is 0 ...

    102. Re:GPL the best bet by Wolfrider · · Score: 1

      > their stock went up 40% (!) yesterday on the MS news. It also was about double from when the lawsuit silliness started *before* yesterday. So SCO stockholders are making money, that's for sure.

      --Just goes to show you, there are plenty of IDIOTS on Wall Street. Think about it for a second - every headline that I've seen leads me to the conclusion that SCO is Bad Business.

      --If their stock went up 40%, that's insane. The market overall is in such a slump, people must be grasping at straws. Look for it to fall - I'd guess to under $10 a share within two weeks, but that's just a Wild-Ass Guess.

      --SCO deserves to fail - and fall HARD.

      --
      .
      == WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??
    103. Re:GPL the best bet by NoOneInParticular · · Score: 1

      I think you should be more explicit in step 2.

    104. Re:GPL the best bet by rifter · · Score: 1

      Yes, but that is not exactly what is going on in this case. What we have is an allegation that code was given under NDA to someone who subsequently broke that NDA by releasing it under the GPL. We do also have the curious case such that the accuser (SCO) will only allow us to know what code they are talking about with an NDA, in which case what you are saying certainly applies, though I think part of the reason they are using NDA at this stage is that they are still formulating their strategy (and hunting for infringing code) and don't want to help IBM any more than they have to (or get too much guff from the peanut gallery; which they know they will certainly get anyway).

      In reference to the first NDA, however, it is very important. The whole point of the NDA was if IBM did what SCO claims they have done SCo would be able to sue them. It was supposed to stop disclosure in the first place, but if it has not, it is meant to provide legal remedies.

    105. Re:GPL the best bet by kubrick · · Score: 1

      Their argument for this claim will be "we didn't distribute it; we had no knowledge."

      I'm sure they must have had their lawyers check the GPL over pretty carefully at times; this is something that will work against their claim that they had "no knowledge" of the effects of distributing their IP under the license.

      There's a bit of a difference between hacking a website and a company willingly and knowingly distributing software for years, isn't there?

      What's that about "without your express wishes"? They released the source code -- if it contains their trade secrets, whoever was at fault originally was let off the hook at that point. If they didn't want to do that, they should have considered their position more carefully before trying to cash in on the Linux hype.

      --
      deus does not exist but if he does
    106. Re:GPL the best bet by dvdeug · · Score: 1

      and 3 times 0 is 0 ...

      The same principle applies to the stuff that Microsoft gives away for free. Go ahead, distribute it and see what they sue you for.

    107. Re:GPL the best bet by studerby · · Score: 1
      Do I get it?

      The law is pretty clear, yes, the owner is entitled to recover stolen goods. In fact, in many cases an owner is entitled to recover stolen goods even if they've been resold honestly several times in the meantime. This comes up sometimes in the art world, with valuable works surfacing and returning to their original owners. For example, a couple of years ago, a stolen Wyeth painting came up at auction; it was seized and returned to Sears, the parent company of the gallery from which it was stolen. It had apprecieted from 30k to 500k in that time.

      I'm not a lawyer and there are probably some exceptional cases; in particular, the line between "looting" and archeology (particularly when the archelogists are from another country/culture) seems to be moving around in the last 20 years or so, although this seems to mostly be handled at the diplomatic level...

      --

      .sig generation error:468(3)

    108. Re:GPL the best bet by studerby · · Score: 1
      intent is irrelevant here

      Intent is (almost) everything with licenses.

      Licenses are a sub-species of contracts; contracts are a formulation of a "meeting of the minds", i.e. an agreement between 2 or more parties. You can't have an agreement without intent.

      That said, there are some exceptions, and there are some rules for digging out what the "intent" is behind a license or contract, and there are some principles for resolving ambiguity. For example, when there is an ambiguity in a contract between a very resource-rich entity and a resource-poor entity, the reasonable interpretation most favorable to the resource-poor entity is favored; the theory is that the rich/big/sophistacted entity more likely new what they were doing...

      There are probably also some laws/rules about "intent" in a corporation. If SCO/Caldera had policies about keeping the Unix code out of Linux and enforced them on any developers they employed, but some "disgruntled" employee made significant efforts to break the rules (e.g. checked them in under an alias to an external project), then there was no "intent"; if they didn't have rules and told their Linux developers "just get it done", then they either had "intent" or were negligent with their property, and they lose.

      For the case where some other developer took "their" code and put it in Linux, it's more complicated, I think. The "negligence" argument above is plausible; it'll definitely get a hearing in court. However, it's not clear to me that they had a duty to monitor Linux for "stolen" code coming in from the outside, I wouldn't be shocked if the courts distinguish re-distribution of the code from maintenance of the code, with redistributers not having as much responsibility for the content.

      By analogy, if I accidentally buy a stolen computer in a lot of used PCs, the original owner can sue and get the machine back, but he can't sue me for any damages or costs because I accidentally ended up with his PC (unless I damaged it after I had notice that it wasn't legally mine). I don't have a positive duty to check that the PCs aren't stolen. However, if I sell that stolen PC in true good faith, the original owner in theory can't successfully sue me for anything (although I could be dragged into proceedings as a witness, and could be sued with the claim I knew or should have known the PC was stolen).

      Extending my analogy a bit though, if I sell that stolen PC and the buyer loses posession of it to the original owner because it was stolen goods, then legally it wasn't mine to sell to the final buyer and he can sue me to recover his money.

      This analogy leads me to wonder if:

      • assuming that "illegal" "Unix" code is found in Linux
      • assuming SCO/Caldera distributed that code
      • then users/buyers of SCO/Caldera linux could sue SCO
      The theory is that SCO represented the product as a "legal" one and their customers who built businesses around that representation of their product would be hurt by that mis-representation. They in turn could sue their "suppliers" though...
      --

      .sig generation error:468(3)

  4. Re:Rocketman, as interpreted by William Shatner by Anonymous Coward · · Score: 1, Funny

    Could you please troll in an open format such as Ogg?

    Real for Linux sucks balls.

  5. Saw this on Google News a while back by lingqi · · Score: 4, Insightful
    and I really like the title of this one: OSI Tears Apart SCO's Claims

    Anyway - on a related note: this is why IBM will not buy SCO. As much as people daydream that IBM is "on our side" and all that, there seem to be all too many who conveniently forgets that IBM is in it for the money, not because they have some kind of conviction that OSI is morally good, or something - it's only good because it's making them money.

    Buying SCO, even if it temporarily puts this behind them, makes OSI completely unworkable by IBM - beacuse this would set a precedence of sketchy IP companies suddenly realizing that IBM will actually pay CASH for bullshit patents and stuff. As much cash as IBM have, they can't be buying every bullshit patent touting company out there - at least not doing so while making a buck.

    so, if SCO fucks linux over, IBM will just find another route to makey money, and if linux stands, IBM will continue to stand my its side. Regardless, though - don't expect IBM to chump out the change for SCO, though i do think they will push a few lawyers for the good cause, because getting a few lawyers and bust SCO's bs out of the water and keep linux standing will, in the end, mean the best bottom line for its business.

    look at the world with an economic eye, guys.

    --

    My life in the land of the rising sun.

    1. Re:Saw this on Google News a while back by crumley · · Score: 1

      Yeah, this was on slashdot a while ago too.

      --
      Preventive War is like committing suicide for fear of death. - Otto Von Bismarck
    2. Re:Saw this on Google News a while back by Anonymous Coward · · Score: 1, Insightful

      so, if SCO fucks linux over, IBM will just find another route to makey money

      IBM has woven Linux so deep into their business plan that it would be vewry difficult for them to just find something else to supplant it.
      They've publicly said that Linux will become their core OS.
    3. Re:Saw this on Google News a while back by fw3 · · Score: 4, Interesting
      As much as people daydream that IBM is "on our side ... not because they have some kind of conviction that OSI is morally good

      Err well making money is arguably morally good.

      SCO is far less trying to fsck over linux than IBM, yes they've made noises toward the Distributions, but a primary thrust of their suit is to revoke IBM's Unix license. Even a very small likelihood of that happening will grab the attention of people running AIX.

      Naturally we expect IBM to address this with the court and if the court considers it likely they will prevail, then IBM will be allowed to continue shipping AIX.

      The reasons I think SCO loses this case, amplifying OSI's discussion:

      • AIX as a kernel is the Mach microkernel, (derived from BSD not SysV) and among unixes it's the one which outwardly seems to have the most rewriting. The same kernel and hardware have been the basis of os/400 for half a decade.
      • AIX as an OS mostly uses bsd-flavored commands (and only adopted sysV-style init as Linux's SysV-style became the lingua-franca)
      • IBM is supporting thier Unix clients by building linux compatibility on top of the (far more solid) AIX kernel. This means middleware. Does anyone doubt that IBM has done a GPL-free interface? No way do I believe they'd risk opening AIX source by directly incorporating GPL.
      Basing AIX on Mach didn't come cheap. For instance AIX took longer than it's competitors to get 64-bit clean for the same reasons that the Hurd (also Mach-based) just got set-back a year, the 32bit limitations are in the microkernel, not the bolted-on subsystems. One thing they bought with that investment, however was a very strong position in the event that SYS-V's inheritors ever wanted to raise this particular ruckus.

      Personally I'm hoping SCO gets tapped for IBM's legal fees when they inevitably lose this case. The only winners I can see are SCO's lawyers, and perhaps to a lesser degree microsoft and Sun.

      --
      Linux is Linux, if One need clarify their dist: <Dist>/GNU Linux
      bsds are of course just BSD
    4. Re:Saw this on Google News a while back by Zathrus · · Score: 1

      They've publicly said that Linux will become their core OS.

      Who is "they"?

      One product manager said that, and he's nothing but a lacky. AIX is going nowhere (as much as I would like it to go into the toilet) and isn't going to be replaced by Linux in the short term. Nor are the various mainframe OS's. Linux is going to be an option for IBM as long as they feel it's viable, but that's it -- an option. And if IBM decides that Linux is too fraught with peril you'll see them pull back from it over a number of years and start pushing their own solutions again or maybe even a BSD solution (doubtful).

      I think the OP is correct, and he stated it very succintly. It may be that IBM will decide that the cheaper route is to buy SCO out, but even $100M is a lot of lawyers' fees. And IBM may want to make a statement -- it all depends on cost. Ideology is not going to enter into it, and anyone thinking differently hasn't figured out the real world yet.

    5. Re:Saw this on Google News a while back by CaptainZapp · · Score: 1
      SCO is far less trying to fsck over linux than IBM, yes they've made noises toward the Distributions, but a primary thrust of their suit is to revoke IBM's Unix license.

      I would have bought that up to the point when Microsoft started to "license" 20 year old computer technology of which there's no chance in hell that it ever gets incorporated into their products.

      At least that's my take.

      --
      ich bin der musikant

      mit taschenrechner in der hand

      kraftwerk

    6. Re:Saw this on Google News a while back by evilviper · · Score: 1
      beacuse this would set a precedence of sketchy IP companies suddenly realizing that IBM will actually pay CASH for bullshit patents and stuff. As much cash as IBM have, they can't be buying every bullshit patent touting company out there - at least not doing so while making a buck.

      Obviously, you've never heard of frivolous lawsuits...

      Always, companies will settle lawsuits for the "hassle" ammount... In other words, it's cheaper to settle a lawsuit for $1,000, than to defend your case, even if you are guaranteed to win. As poor of a precident as it sets, they continue to look out for themselves in the short-term, rather than looking at the whole industry, and what effect it will have in the long-term.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    7. Re:Saw this on Google News a while back by chez69 · · Score: 1

      A few corrections:

      - AIX is not based on mach
      - OS/400 was ported to PowerPC, but it certainly not the same kernel as AIX.

      --
      PHP is the solution of choice for relaying mysql errors to web users.
    8. Re:Saw this on Google News a while back by ePhil_One · · Score: 1
      As poor of a precident as it sets, they continue to look out for themselves in the short-term, rather than looking at the whole industry, and what effect it will have in the long-term

      I don't think "Take one for the team" works in the corporate environment. If you spend $250,000 to risk setting a precedent and succeed, you're a quarter million down on the competition. IF you pay $100,000 to make that go away for sure, and there's a chance they go sue your competitor next, you're only down $100,000 on the competition and theres a chance they'll have to make the same deal or worse. Now, if the industry chooses to band together against a common cause (for a mutual defense fund of sorts), that a different matter.

      Personally, I think IBM will 1) string it out as long as possible with their staff lawyers. 2) Give up the Unix label if forced, because its of questionable value in their new "Linux compatible" world

      --
      You are in a maze of twisted little posts, all alike.
    9. Re:Saw this on Google News a while back by Anonymous Coward · · Score: 0

      I don't think anyone (in their right mind) is suggesting that Linux replace any of the mainframe OSes, but to say that IBM will simply pull back if Linux becomes "fraught with perils", is also a bit naive. They've spent $1 biliion dollars on it so far. I don't remember where I read the article, but it had mentioned something like 7500 people at IBM working on Linux projects.

    10. Re:Saw this on Google News a while back by greed · · Score: 2, Interesting
      AIX as a kernel is the Mach microkernel,

      I know that AIX (along with every other OS at IBM) was to be hosted under Mach back in the mid-90s, but every system house except OS/2 abandoned that project. And OS/2... well, we know about what happened there. This was all part of the much-hyped and little-designed Workplace project.

      AIX does have a rather unusual kernel for UNIX; it has quite a lot of dynamic configuration and device management, and it has had it for a very long time--back when it was still standard practice to reboot a Sun to make a config change, you almost never needed to reboot an RS/6000. AIX has, by Sun and Linux standards, an unusual shared object system as well. But it worked back when everyone was saying, "always build static on Solaris" (ca. 1993). That it hasn't changed much (prior to AIX 5.2) kind of hurts C++, but oh well.

      And I can't find any trace of Mach on IBM's marketing pages for AIX; companies who use Mach seem to be quite happy to add it to the list of features they're marketing.

    11. Re:Saw this on Google News a while back by raju1kabir · · Score: 1
      Err well making money is arguably morally good.

      That's an argument I'd be fascinated to see you make.

      Making money is as morally ambiguous as wearing a blue shirt or having an apple for breakfast. It's how you make it, what you do with it, what impact all that has on others, and what you understand about that impact that determines the morality.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    12. Re:Saw this on Google News a while back by Malcontent · · Score: 1

      "Err well making money is arguably morally good."

      Sez who?

      Jesus continually preached against the evils of greed and accumulation of wealth.

      Budha preached poverty and chastity.

      Mohammed didn't mind accumulation of wealth nearly as much as Jesus did.

      Anton Levay (the founder of satanism) was all for getting rich as you can.

      The only moral framework which actually encourages making money is satanism.

      --

      War is necrophilia.

    13. Re:Saw this on Google News a while back by Malcontent · · Score: 1

      "Making money is as morally ambiguous as wearing a blue shirt or having an apple for breakfast. "

      From the bible.

      "It is harder for a rich man to get into heaven then for a camel to go through the eye of a needle."

      "Love of money is the root of all evil."

      Jesus preached more then once that making money (at least in excess of what you need to live) was actually immoral.

      So did budha BTW.

      --

      War is necrophilia.

    14. Re:Saw this on Google News a while back by Anonymous Coward · · Score: 0

      Ack, but IBM put quite a bit of efford and thus money (loads of Marketing) in Linux and a couple of managers within IBM will have their heads on a block when it comes to Linux business failing.

      They kind of put a face on the last 1 to 2 years: 'we are Linux'. That's a costly marketing position.
      Some bucks to win the case will be good for the balance at the end of the year ;-) (speaking economically :P)

      So, my guess is that they will not give up easily.

    15. Re:Saw this on Google News a while back by steveg · · Score: 1

      Are you equating 'religion' with 'moral framework'?

      Thye might (arguably) be related, but they're certainly not synonymous.

      --
      Ignorance killed the cat. Curiosity was framed.
    16. Re:Saw this on Google News a while back by rifter · · Score: 1

      I don't think anyone (in their right mind) is suggesting that Linux replace any of the mainframe OSes

      Apparently IBM and the NYSE are...

    17. Re:Saw this on Google News a while back by Malcontent · · Score: 1

      " Are you equating 'religion' with 'moral framework'?"

      No.

      It's just that the people I mentioned have been the most influencial moral thinkers in all of history. There have been many great moral thinkers in the past few thousand years and I can't think of that many who advocated the accumulation of wealth as a moral or spritual goal.
      I pointed out that the founder of the church of satan is one of them. I am sure there have been others.

      Perhaps you can make a list for me, I really can't think of too many.

      --

      War is necrophilia.

    18. Re:Saw this on Google News a while back by evilviper · · Score: 1
      IF you pay $100,000 to make that go away for sure, and there's a chance they go sue your competitor next, you're only down $100,000 on the competition and theres a chance they'll have to make the same deal or worse.

      Indeed, BUT, this is the kind of thing that doesn't just go away. There's quite a chance this could bite them in the ass years later. Quite possibly, someone else will make very similar claims in the future, and when that happens a few times, they end up paying far more than the $250,000 they could have put up the first time.

      In the narrow picture, the $100,000 is a good deal... In the big picture, spending the $250,000 is the best way to go.

      That's why I used the example of companies always settling for a set ammount despite the validity of the claims... Sure, prosecuting several of the claims would be more expensive right away, but if you don't, you'll be spending may times more over time on many many more frivolous lawsuit settlements, because it's easy money.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    19. Re:Saw this on Google News a while back by fw3 · · Score: 1
      Hmm, I agree there's remarkably little data on this found in google ... here's what I'm (reasonably) certain of

      Aix is a microkernel design, At the time I started using it ('93 / aix 3.1) this was 'common knowlege' and the basis was Mach. I beleive that's with extensive IBM mods. Yes I also remember the time when 'Workplace shell' was going to sit on a microkernel under aix, os/2 ... That was also the days of IBM's SAA :-).

      You may also remember that the (ca) '96 timeframe was when IBM was offering it's microkernel investment to competitors. I (still) beleive that this was on the basis that they had migrated os/400 off of it's mini-platform onto RISC and DEC and HP were looking at the same problem with a need to move VMS and MPE respectively onto their RISC platforms.

      I know for a fact that the AIX VM has the same design (benefits and limitations) that Hurd has been dealing with in their Mach underpinning. IT's an approach to the VM which to my knowlege is unique to Mach/osf1.

      I'll offer the following assertions that AIX is based on Mach.

      AIX/ESA, runs native on S/370 and S/390 mainframes, based on OSF/1. AIX [rs/6k] was to have been base for OSF/1 until Mach was chosen instead. I hope this subsection is converging : ref

      The Mach microkernel technology developed at Carnegie Mellon University serves as the basis for IBM's microkernel work. On the Mach base IBM is experimenting with new ways of implementing low-end environments, developing stand-alone file servers, integrating multiple operating system personalities on a single computer, ... For instance, the low-end AIX implementation on Mach currently runs as a dominant personality and supports an environment for running DOS programs as a secondary personality. ref

      MACH isn't a UNIX system either but is the basis for interesting UNIX kernel dev elopments. The DEC UNIX kernel is build on MACH (as well as the GNU Hurd, NextSt ep/OpenStep, Apple's forthcoming Rhapsody and IBM's OS/2 for the RS/6000). ref

      IBM's own AIX operating system is based on a different Unix kernel, called the Mach kernel, which was created at Carnegie Mellon University in Pittsburgh, but many of the layers of Unix functions that ride on top of this kernel are apparen tly based on Unix System V ref

      See also e2[microkernel]

      --
      Linux is Linux, if One need clarify their dist: <Dist>/GNU Linux
      bsds are of course just BSD
  6. Re:As an attorney... by DigiShaman · · Score: 2, Insightful

    Can we get some legal certified toilet paper? Cause now days, you need an attorney just to wipe your own ass. To bad the slashdot crowd can't just pool togeather some money to kick SCO out of existance. I can dream can't I?

    --
    Life is not for the lazy.
  7. OSI Papers notwithstanding... by BJZQ8 · · Score: 5, Funny

    OSI Papers notwithstanding, all it takes is a tipply judge to cause a lot of headaches for everyone from RedHat to Yellow Dog. In any case, Microsoft wins. Their line...go with the smart, non-litigated choice...Windows XP. Now with Software Assurance!

    1. Re:OSI Papers notwithstanding... by Anonymous Coward · · Score: 1, Funny

      non litigated you say?

      wasnt there a big ass criminal trial a year ago?

    2. Re:OSI Papers notwithstanding... by gandy909 · · Score: 1

      "...non litigated..."?

      You are referring to a not only litigated, but convicted, monopolist....

      --

      (Stolen sig) Remember: it's a "Microsoft virus", not an "email virus", a "Microsoft worm", not a "computer worm
    3. Re:OSI Papers notwithstanding... by BJZQ8 · · Score: 2

      I mean non-litigated in the sense that, so far, there has been no serious lawsuit yet against Microsoft that would threaten the users themselves, or the very survival of the distributions they use. Microsoft is large enough and has enough legions of lawyers that they could prevent such a thing by sheer mass alone, even if they had infringed 100 patents. Microsoft can and will spin this as "go with the big one", while "little" companies like RedHat and SCO fight amongst themselves. If SCO (Caldera, whatever) had a brain in their head they would join with the Linux vendors to present a "United" front against MS. But they are ultimately looking for shareholder value, so this really makes sense in the short term.

    4. Re:OSI Papers notwithstanding... by ch-chuck · · Score: 1

      Well, XP was a nice dream for about 1.5 yrs for me - recently it's turned to crap reinstalling every couple of weeks. Wasted 1.5 hrs on it this morning instead of doing something productive and lowering my TCO. Maybe it's the disk drive going flaky, but it bsod'd with a stop code about a month ago, "unmountable disk" - which I was able to mount with Linux ntfs fs module in ro mode w/ no problem and could at least save the data that running the msft 'recovery' process wouldn't touch. After a complete reinstall, recently it started getting a different stop code, hard error on c:\windows\system32\ntdll.dll. But this time it could log onto the disk doing a 'recovery' setup, did chkdsk which found a few errors and rebooted ok. Then it did it again last night - exact same bsod, ntdll.dll. This morning I waited thru the cd loading a recovery setup /again/, chkdsk found no problem, chkdsk /p did, rebooted but still craps out. SO, my XP is getting reinstalled AGAIN (3rd strike) onto a different disk, a SCSI UW160 I surplused from work, this time. Same system runs Win98 (bletch, for my 3D glasses, games and older stuff only) and of course Linux with Q3A just fine.

      --
      try { do() || do_not(); } catch (JediException err) { yoda(err); }
    5. Re:OSI Papers notwithstanding... by Anonymous Coward · · Score: 0

      heres an idea - why dont u BUY a disk instead of workin on crappy second hand stuff.
      Blaming the operating system for your faulty goods gets us nowhere.
      loads of folks have XP running extremely well without ever seeing a problem.

    6. Re:OSI Papers notwithstanding... by Waffle+Iron · · Score: 1
      Their line...go with the smart, non-litigated choice...Windows XP. Now with Software Assurance!

      In BSA audited enterprise, vendor litigates YOU!

    7. Re:OSI Papers notwithstanding... by jedidiah · · Score: 1

      A shame that.

      MY OS doesn't have those sorts of problems with OLD disk drives.

      Perhaps someday YOUR OS will be less of a JOKE.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    8. Re:OSI Papers notwithstanding... by Anonymous Coward · · Score: 0

      > wasnt there a big ass criminal trial a year ago?

      Very yesterday's news; 'what have you done for/to me lately?' is the rallying question of managers everywhere.

  8. So... by Noryungi · · Score: 5, Insightful
    Frankly, I am getting sick and tired of this whole SCO hoopla. The facts of the case can be summed up as follows:

    • SCO is dying (and no, this is not a joke).
    • Even if Linux was to suffer from this ridiculous law suit, there is always [Free|Net|Open]BSD, systems that certainly do not include any code from SCO (otherwise, they would be named).


    So, not matter what happens, open source will survive. GNU/Linux may suffer, but not other systems.

    The SCO law suit will probably go down in history in the same category as the stupid congressmen that bad-mouth the GPL. Namely, the trashcan.
    --
    The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
    1. Re:So... by femto · · Score: 2, Funny
      > Even if Linux was to suffer from this ridiculous law suit, there is always [Free|Net|Open]BSD

      And if all else fails, there is always the HURD... :-) (seriously!)

    2. Re:So... by Greger47 · · Score: 5, Insightful


      Even if Linux was to suffer from this ridiculous law suit, there is always [Free|Net|Open]BSD, systems that certainly do not include any code from SCO (otherwise, they would be named).

      I'm picking your comment at random from all the theres-no-problem-we-still-have-*BSD touters out there.

      There is NOTHING, I repeat NOTHING that prevents this mess from happening to the *BSDs aswell. Some oh-so-secret IP from random-ligitator-company may just as easily end up in any project with an open development model.

      Yes, the *BSDs where clensed in the beginning of the 90ies from the old AT&T sorucecode license ghost, but this deal is about supposedly *new* IP developed by SCO.

    3. Re:So... by Anonymous Coward · · Score: 1, Insightful
      Um... the majority of the code in a "Linux" distribution is the GNU portion of GNU/Linux. And Linux, the kernel, is GPL-d.

      I believe, judging from SCO posting some inflammatory comments, from their perspective, by Stallman and Perens on their web site, that this is another orchestrated attack on the GPL. When MS tried that before, it didn't work for them. So now, SCO is doing it for them, from all the evidence we can see. They are trying to make people believe that GPL equals piracy and lack of respect for copyright. (Of course, GPL is based on copyright, being a license on top of copyright, from which it derives its power, but they don't realize that).

      In short, saying who cares because BSD is available is missing the big picture. Of course they want only BSD. They can steal it and it won't make them play nice and give anything back, the way the GPL does. Instead, they can use the free work of others and them make it proprietary, which is their craving.

    4. Re:So... by Noryungi · · Score: 1
      Hmmmm.

      I think you answered your own rebuttal when you wrote:

      Yes, the *BSDs where cle[a]nsed in the beginning of the 90ies from the old AT&T so[ur]cecode license ghost, but this deal is about supposedly *new* IP developed by SCO.

      Specifically, SCO is suing IBM because IBM supposedly integrated SCO Intellectual Property (IP) to the Linux kernel.

      Since IBM has not -- AFAIK -- collaborated with [Free|Net|Open]BSD, and has not supplied any specific help to these groups, it follows logically that, whatever IP was "stolen" from SCO, it was not, repeat NOT integrated into the different kernels of the *BSDs.

      This is, of course, assuming that SCO actually has some serious proof on its side -- which is pure conjecture at this stage of the law suit.

      So, allow me to sum up:

      • SCO is suing IBM, allegedly because big blue stole some sort of "secret recipe" from SCO to integrate it into Linux.
      • IBM -- again, AFAIK -- never collaborated with the BSDs, and the BSDs are therfore immune to the law suit


      Given these two points, I am afraid the thesis of my previous post still stands.

      Som people have said: well, yes, but if Linux is gone, what will happen to the BSDs? They will become proprietary!

      The simple answer is to say that the BSDs will continue to exist, simply because it's easy to download the last "free" (BSD-licensed) version and to start all over again. And if the worst happens, I am sure there will be people who will do just that.

      Besides, there are already two foundations (the FreeBSD Foundation and the NetBSD Foundation) doing just that: making sure that these Oses stay "free".

      Just like there is nothing to prevent anyone and their grand mother from creating their own Linux distribution, there is nothing to prevent you from creating your own branch of BSD.

      Actualy, this is exactly what happened rather recently, since OpenBSD is an offshoot/fork of NetBSD. Not to mention things like WarBSD, Darwin, and several others...

      Several years ago, I bought the "Unix Haters Handbook". No matter what you think of the central idea of the book (Unix is Evil), there was a sentence that I vaguely remember, in the NFS chapter: "NFS triumphed because it was free, not because it was technically superior". The same thing is -- IMHO -- true for Linux and the BSDs.

      So, please, don't panic. Linux is here to stay, no matter how much FUD SCO is spewing.
      --
      The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
    5. Re:So... by jilles · · Score: 1

      If people bothered to read the paper, they'd know that the OSI claims that BSD and SCO do share the same legacy of source code (i.e. they both evolved from Bell Unix). In fact SCO chose to settle a legal argument with the BSD people about code infringement because it became very clear that it was actually sco infringing on BSD (alledgedly they copied thousands of bsd licensed source files and stripped them from copyright and license) rather than the other way around.

      --

      Jilles
    6. Re:So... by Ugmo · · Score: 1

      Even if Linux was to suffer from this ridiculous law suit, there is always [Free|Net|Open]BSD, systems that certainly do not include any code from SCO (otherwise, they would be named).

      I don't want to put down BSD. It is great and all and I am glad it exists. Diversity and variety is strength.

      I also do not believe in the idae that this is a 12 year old plot by Microsoft, meaning MS spun off Xenix and SCO many years ago just so they could do this now muwhaahaahaa. I think MS is just taking advantage of something that came up. I do think they bought the license to lend credibility to SCO's claims and help keep them in business long enough to stretch this FUD campaign out as long as possible.

      Having said those two things, if Linux went under and all developement switched to BSD licenses, nothing would make MS happier. They would just rape all the code that Open Source people developed, make slight changes to the file format s and protocols so they do not work with BSD systems and sell your own code back to you at 85% profit margins.

      Linux and the GPL is the real thorn in MS's side. They would like to see it's adoption stopped or slowed and SCO is just one way to do it.

    7. Re:So... by DickBreath · · Score: 1

      He has a real point.

      A new <random-litigator-company> can sue anyone over <supposedly-new-IP> that has been misappropriated into BSD. This alleged act occured recently and is unconnected with any IP claims of the old Unix code.

      Now do this...

      s/BSD/<other-open-source-project>/g

      --

      I'll see your senator, and I'll raise you two judges.
    8. Re:So... by cHiphead · · Score: 1

      if i remember (in)correctly in proper /. fashion, previous lawsuit(s?) against BSD got raped in the eye b/c berkeley wrote huge portions of the code that SCO now holds in its hand. some sort of 'you dont sue us we wont sue you, motherf__kers' deal.

      --

      This is my sig. There are many like it, but this one is mine.
    9. Re:So... by DickBreath · · Score: 2, Insightful

      But new will sue users of The HURD because it (allegedly) misappropriates . Of course Microsoft will take out a healty license from .

      This is a real insight. Any open source project is vulnerable to this kind of Microsoft sponsored lawsuit.

      This will (hopefully) of course get thrown out in court, after moving in Lawyer-Time (opposite of Internet-Time).

      In the meantime, there is lots of FUD flying around about how dangerous it is to use <open-source-project>

      In the meantime, the lawyers of <random-litigator-company> are getting paid, and are happy. Bills get paid, legal fight continues. Eventually it is thrown out. The lawyers are merely employees who then move on to do work for new <random-litigator-company>, which sells a license to Microsoft.

      do while( 1 ) { lather(); rinse(); }

      --

      I'll see your senator, and I'll raise you two judges.
    10. Re:So... by zenyu · · Score: 1

      The lawyers are merely employees who then move on to do work for new

      IANAL obviously, but aren't there criminal sanctions for helping someone with a frivalous lawsuit? I would think 20 minutes with google would tell a lawyer SCO doesn't have much to stand on. If there aren't criminal sanctions available to a judge dealing with this type of lawyer, can they not at least disbar the lawyers with direct involvement in the case?

      Any lawyers, judges out there?

    11. Re:So... by Anonymous Coward · · Score: 0

      >SCO is dying (and no, this is not a joke).
      >
      >Even if Linux was to suffer from this ridiculous law suit, there is always [Free|Net|Open]BSD, systems that certainly do not include any code from SCO (otherwise, they would be named).

      You're not too far off. SCO might be checking to see if they include any enhancements or what not from the BSD distros. There was a case like this back when AT&T still had control over Unix and tried to sue BSD, but it went back on them and they got sued by BSD.

      Alot of the code and software still used today was developed on BSD unix.

    12. Re:So... by Anonymous Coward · · Score: 0

      While that's true, it's very unlikely that someone like Theo is going to be sued for the revenue from his t-shirt sales. At most, he'd get a letter in the mail, he'd fix the code, and everyone would get on with life.

      In order to have a big legal IP shitstorm, you need some deep pockets. Someone like IBM, or the University of California (original BSD lawsuit).

    13. Re:So... by LMCBoy · · Score: 1

      GNU/Linux may suffer, but not other systems.

      This could lead to the rise of the GNU/Hurd, the Second Coming of GNU!

      (actually, I don't think GNU/Linux has anything to worry about)

      --
      Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
    14. Re:So... by Anonymous Coward · · Score: 0

      SCO is dying (and no, this is not a joke).

      Seems amusing to me.

    15. Re:So... by Greger47 · · Score: 2, Insightful


      Let's say Linux never existed and the *BSDs ruled the opensource world.

      Let's say Big Blue goes out shopping for a nice alternative to M$ Windows.

      Let's say random-company-about-to-go-down-the-drain figures it's time to make a quick buck.

      Thus any project can end up in this exact mess . All open source projects become easy targets for lowlife IP scum as soon as someone with big money starts investing in them.

      1. It's easy to check any code for random IP/patent collisions with your own portfolio.
      2. If you are to lazy to look, you can silently plant some infinging code.
    16. Re:So... by Greger47 · · Score: 1

      Correction:

      All open source projects become goldmines...

    17. Re:So... by Arandir · · Score: 1

      They can steal it and it won't make them play nice and give anything back, the way the GPL does.

      I hear this all the time, but there's a big problem with it. Why do "they" need the GPL out of the way before they can steal BSD code? Why don't they just steal it NOW? Why even bother trying to kill GPL software?

      After all Sun's fortunes came from "stealing" BSD, but they never once bothered trying to stick a knife in GPL. Apple made the biggest comeback in history by "stealing" BSD, but they didn't try to murder GPL. In fact, in all of history, only Microsoft and SCO/Caldera have ever devoted any appreciable amount of energy trying to discredit the GPL.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    18. Re:So... by DickBreath · · Score: 1

      aren't there criminal sanctions for helping someone with a frivalous lawsuit?

      I'm sure there are.

      Just like there are many laws related to pr0n.

      So just how did you say you defined frivolus lawsuit again? Anything that makes you get hard? But what makes you get hard is decidedly not what makes me get hard. Is it pr0n or is it fine art?

      One man's frivolus lawsuit is.... oh, nevermind. :-)

      --

      I'll see your senator, and I'll raise you two judges.
  9. Dupe. by Anonymous Coward · · Score: 0

    I thought we already talked about this.

  10. a good explanation from.... by smd4985 · · Score: 5, Interesting

    open-source advocate Bruce Perens:

    http://news.com.com/2010-1071_3-1007758.html?tag =f d_nc_1

    He doesn't outright say it be he is almost implying that certain monied interests (M$?) could be indirectly funding the whole SCO effort to spread FUD about Linux.

    --
    smd4985
    1. Re:a good explanation from.... by SerpentMage · · Score: 1

      I really do wonder about this. Why all of the sudden this interest? Remember that a certain company does own some of SCO.

      Also is it not interesting that somebody decides to buy a license just now? Yes it could be to save their hide later down the road. Oddly also lately the Open Source topic by them happened to not exist. They just talked about their new product launches, etc. It seemed odd to me...

      Maybe this is just conspiracy thinking, but I do think there is more to this than meets the eye. The question though is who is involved....

      --

      "You can't make a race horse of a pig"
      "No," said Samuel, "but you can make very fast pig"
    2. Re:a good explanation from.... by Anonymous Coward · · Score: 2, Insightful

      You're the religious zealot. The only thing giving I"P" value is current I"P" law. The perceived value of I"P" as a result of that law cannot be used as an argument for I"P" - that would be circular logic beloved of religions everywhere.

      Anyway, SCO have only alleged that Linux contains their I"P". I wouldn't beleive them, myself. If anything, it's far more likely SCO UnixWare contains Linux I"P" (GPL is not anti-I"P" (though I am), it depends on strong copyright law).

      It is a non-sequitur to say "go to Cuba if you don't like IP". The renaissance happened without I"P". The very idea of I"P" is antithetical to fields like Mathematics and Science. America prospered by ignoring European I"P" laws in the 19th century. Strengthening I"P" laws, in fact, seems to lead to cultural stagnation.

    3. Re:a good explanation from.... by Eunuchswear · · Score: 1
      Remember that a certain company does own some of SCO.
      Oh how coy. Which company might this be, Microsoft? The company that sold it's share in SCO in January 2000?.

      Not that has anything to do with this lawsuit, that is being brought by Caldera, or "Caldera D/B/A The SCO Group".

      --
      Watch this Heartland Institute video
    4. Re:a good explanation from.... by mav[LAG] · · Score: 1

      True although this seems pretty clear:

      Microsoft hardly needs an SCO source license. Its license payment to SCO is simply a good-looking way to pass along a bribe, coupled with an announcement designed to further intimidate Linux users.

      --
      --- Hot Shot City is particularly good.
    5. Re:a good explanation from.... by jgerman · · Score: 1

      MOD PARENT UP! A well written and insightful reply.

      --
      I'm the big fish in the big pond bitch.
    6. Re:a good explanation from.... by bobKali · · Score: 1

      Hate to feed ya, but the "burn in hell like the thieving dog that it is" comment made me laugh out loud....

      First off I thought that the lawsuit was over trade secrets, not IP (or does IP now encompass trade secrets as well as copyrights and trademarks and patents and bears! oh my!) Seems to me that the IP moniker has become so broad that it's not worth using anymore because points made that would be apropriate for one form of IP are not apropriate for another form (a prime example would be the necessity to defend or lose trademarks which does not apply, AFAIK, to patents.)

      Next, I think that of the problems that Cuba and North Korea have, respecting IP claims are pretty far down on that list.

      And the problem with equating the 'theft' of non-physical items with the theft of physical items has been illustraded time and time again ad nausiam.... No matter what anyone else does with it, you still have your use of it. It's still wrong, and criminal, and should be. But it is not theft, nor is it piracy. It is infringement of whatever state-granted privilege is being infringed upon.

    7. Re:a good explanation from.... by gotan · · Score: 1

      Your comment lost contact with reality by the end of "If it was your IP being stolen [...]".

      The linked text explains in detail that SCO's IP-claims are invalid, and that no IP that SCO can claim ownership to was stolen. Maybe you should read the text.

      Mentioning "axis-of-evil" countries and resurrecting language from the cold war doesn't contribute any credibility to your comment.

      Since the "If Linux does contain SCO IP" condition evaluates to false the rest of your post is invalid as well.

      --
      "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
    8. Re:a good explanation from.... by Anonymous Coward · · Score: 0

      Fuck you. That was a blatant troll.

    9. Re:a good explanation from.... by Anonymous Coward · · Score: 0

      Hi. The premise of the linked text is that SCO UNIXWare does not have the enterprise scalability features of Linux. This is provably false, and therefore the linked text is worthless.

      In other words, you have been trolled.

    10. Re:a good explanation from.... by Anonymous Coward · · Score: 0

      The nice thing about imaginary Intellectual 'Property' is that it can be exchanged for equally imaginary US Dollar bills.

      The "perceived value" of these US "Dollars" can then be traded for substantial value like food or labor. In fact, all of capitalist society is based on the the ridiclous idea that these little green pieces of paper have some real value.

      One would have to be a real capitalist zealot to buy into the "collective delusuion" that dollar bills are anything more than a legal farse based in an near religous circular logic.

      However, the more enlightend of us have only a couple options but to participate in the trade of dollar bills. Moving to Cuba is one of them.

    11. Re:a good explanation from.... by Tony-A · · Score: 2, Informative

      This is not a matter of religous zealotry, it a matter of plain theft!

      But whose theft?
      "The exact terms of final settlement, and much of the judicial record, were sealed at Novell's insistence."

      "The University of California then threatened to countersue over license violations by AT&T and USL. It seems that from as far back as before 1985, the historical Bell Labs codebase had been incorporating large amounts of software from the BSD sources. The University's cause of action lay in the fact that AT&T, USL and Novell had routinely violated the terms of the BSD license by removing license attributions and copyrights."

      Methinks it gets very interesting if that stuff gets unsealed.

    12. Re:a good explanation from.... by phliar · · Score: 1
      stolen ...property ... burn in hell like the theiving [sic] dog that it is ... plain criminal ... ... plain theft!
      Bullshit!

      Just because you'd like it to be so doesn't make it so. Repeat after me: this is copyright violation. Not theft. Words mean things. "Theft," "thieving" [I'm fixing your atrocious spelling], "property" -- all these words have specific meanings. Copyright violation is a civil matter, not criminal. Since copyright is by definition and by law of a limited duration, it cannot be called "property" -- ownership is by definition for all time. (We won't even talk about your underhanded implications about "the underlying problem"... have you stopped beating your wife and kids yet?)

      You wouldn't happen to be a SCO or Micros**t employee, would you?

      --
      Unlimited growth == Cancer.
    13. Re:a good explanation from.... by SerpentMage · · Score: 1

      Ok thanks for clearing up my misunderstanding. The reason I was coy is because I wonder. I do not want to say MS because I am not exactly sure. Everything just puzzles me a bit and this has me wondering. Most things have an ulterior motive and I am trying to figure out what this one is.

      --

      "You can't make a race horse of a pig"
      "No," said Samuel, "but you can make very fast pig"
  11. The numbers prove it.. by Aliencow · · Score: 1

    BS...err SCO is dying !

    1. Re:The numbers prove it.. by Destoo · · Score: 1

      SCO is already dead and was reanimated by MS to spread FUD, according to Bruce Perens at news.. So it's necromancy.

      As you can see in the graphic of Historical and technical background, you'll notice there is no death date for BSD!

      Take that, you BSD trolls!

      (counterpoint: when something is not dead, it's in the process of dying, which is what the trolls have been saying.)

      --
      Nouvelles de jeux et technologies en français. TC
  12. Position Paper still needs work... by Anonymous Coward · · Score: 1, Interesting

    I've been reviewing this document since ESR first published it on the web several weeks ago. I'm glad to see he's updating it, and the chart is a great improvement.

    There are still some rough edges, though. For instance, directly below the AIX label on the chart the text says "AIX and Solaris are not included..."

    It's a wonderful overview of the UNIX world, but it also underscores complacency among UNIX hackers for AT&T's license. I'm not sure the judge in the SCO v/s IBM case will look kindly on the "everybody did it so it was okay" attitude toward sharing code. Isn't that just the thing SCO is talking about?

    1. Re:Position Paper still needs work... by rifter · · Score: 1

      It's a wonderful overview of the UNIX world, but it also underscores complacency among UNIX hackers for AT&T's license. I'm not sure the judge in the SCO v/s IBM case will look kindly on the "everybody did it so it was okay" attitude toward sharing code. Isn't that just the thing SCO is talking about?

      I think you are forgetting that "everyone" includes AT&T and SCO. Apparently at least AT&T was shown to have appropriated BSD code into its products. So it might well be a pot and kettle case...

  13. My favorite quote... by HotNeedleOfInquiry · · Score: 5, Insightful

    SCO's complaint is factually defective in that it implies claims about SCO's business and technical capabilities that are untrue. It is, indeed, very cleverly crafted to deceive a reader without intimate knowledge of the technology and history of Unix; it gives false impressions by both the suppression of relevant facts, the ambiguous suggestion of falsehoods, and in a few instances by outright lying.

    --
    "Eve of Destruction", it's not just for old hippies anymore...
    1. Re:My favorite quote... by Sherloqq · · Score: 2, Funny

      Heh, mine were:

      SCO's complaint is factually defective in that it implies claims about SCO's business and technical capabilities that are untrue. It is, indeed, very cleverly crafted to deceive a reader without intimate knowledge of the technology and history of Unix; it gives false impressions by both the suppression of relevant facts, the ambiguous suggestion of falsehoods, and in a few instances by outright lying.

      Ouch. 'Dem are some strong words!

      Their strength has been in franchise operations including McDonalds, Burger King, and Pizza Hut, which involve lots of parallel small deployments with no individual site requiring enterprise technology. [...] SCO's claim to own the scalability techniques certainly cannot be supported from the feature list of its own SCO OpenServer

      So, SCO Unix is the equivalent of a McDonalds' hamburger? Mmmmm... tasty... Would you like a SCO media kit with that?

      Examination of SCO's 10Ks reveals that, even were we to assume that every dime of their revenue came from the enterprise market, their 2002 share could not have exceeded 3.1% [5] This is at the level of statistical noise.

      Bur-r-r-r-rned!!!

      During the USL/Novell vs. BSD court case, it was determined that only three files out of eighteen thousand in the distribution were found to be the licit property of Novell and removed. I wonder how many will be found in Linux. ...SCO made the "ancient Unix" Version 7 source code available for free[13], which rather disposes of the theory that the original Unix code had any residual IP value in the marketplace of today. They belatedly terminated this offering on May 19th 2003, apparently realizing how badly it damaged their trade-secret claims.

      Uhh... can you say "too late now"?

      I think I've had enough already.

      --
      Have EVDO, will travel.
  14. Confused by Sheetrock · · Score: 3, Interesting

    I'm reading in the paper where ESR uses a graphic to illustrate the relationship between the various Unixes/workalikes, and I'm a bit confused -- why is Linux way off to the side disconnected from everything else when a largish part is composed of BSD tools and another largish part is derived from Unix?

    --

    Try not. Do or do not, there is no try.
    -- Dr. Spock, stardate 2822-3.




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

      In short, the answer can be found in the acronym:

      G.N.U.

      GNU is Not Unix :)

      In full, read up on the Free Software Foundation site as to when and why Richard Stallman developed the GNU utilities and how Linus Torvalds was around at the right time to supply the missing piece to the system. i.e. the Linux kernel.

    2. Re:Confused by pix · · Score: 2, Informative

      Ah...but this is the point. Nothing in GNU/Linux is derived from Unix. Many things work in a similar fashion (by design), but they were coded from scratch

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

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

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

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

      --

      Someday, you're going to die. Get over it.
    4. Re:Confused by Tet · · Score: 2, Informative
      why is Linux way off to the side disconnected from everything else when a largish part is composed of BSD tools and another largish part is derived from Unix?

      Not true. Linux is almost completely written from scratch. There are a few ported BSD drivers, but the core OS is a completely new work that shares no code with "genuine" Unix. Of course, Linux distributions included BSD derived code, but the suit here regards the kernel, not userland, and the kernel wasn't derived from anything...

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
    5. Re:Confused by Anonymous Coward · · Score: 0

      why is Linux way off to the side disconnected from everything else when a largish part is composed of BSD tools and another largish part is derived from Unix?

      Bite your tounge. If Linux does have code in it derived from Unix, SCO wins.

      Linux is off to the side with no connecting lines since the chart shows Unix heritage as derived from the original AT&T source code. Even BSD Unix started with a draft of AT&T code which was used as a starting point which eventualy morphed into something very different.

      Linux, the kernel, ideally should have nothing in common with AT&T based code. Most Linux utilities are actually GNU, not BSD derived. The BSD stuff that is in there today no longer has a connection with the AT&T code.

    6. Re:Confused by DoctorPepper · · Score: 1

      I think he's trying to imply that Linux is not a derivative of UNIX, but is a separately developed, Unix-like operating system. The other *nix versions have lines joining them together because they are derivatives of UNIX.

      --

      No matter where you go... there you are.
    7. Re:Confused by realdpk · · Score: 1

      That we know of. Now don't get me wrong, I'm not on SCO's side here, at all. They haven't given us any evidence, so I think /. (and others) should ignore 'em until they do, to stop the FUD spread.

      However, there's really no way for us to know if code wasn't copied from some commercial source into GNU or Linux kernel source. We can say that the "official" statement is that GNU and Linux will not incorporate code that it knows to be "stolen" (and by We I guess I mean FSF and Linus respectively) and that offending code will be removed if proof is presented. The community doesn't have its own lawyers and coders with access to all available commercial source worldwide searching the code.

      That all said though, I'll go back to my first point. SCO's lawsuit needs to stop getting press, unless /. et al are cool with spreading Linux FUD.

    8. Re:Confused by drinkypoo · · Score: 1
      Defining Linux is notoriously tricky

      I thought we covered this already. "Linux" is a kernel, "RedHat Linux" for example is a "Linux Distribution" but more importantly it is a complete "Operating System" since it provides the facility necessary to run programs using the Linux kernel. (Just having a copy of the Kernel itself will not accomplish this. You can write a small enough kernel to floppy and load it, but then you can't start a process. You COULD use kernel-level autoconfiguration and some patches to make Linux come up from a kernel and start performing some network task like Masquerading, perhaps...)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:Confused by jedidiah · · Score: 1

      On the other hand, the development process and releases for Free Software are all out in the open. Interested and non-biased third parties can trace the lineage of any Free Software project.

      This is generally not available for commercial software.

      How can you validate SCO claims? How can you trust any information they might provide?

      Commercial source code is more of a "trade secret" than a copyrighted work in the current scheme.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    10. Re:Confused by geekee · · Score: 1

      Yes. This is why this opinion paper is irrelevant. It claims Linux is independent of all other flavors of Unix without providing any evidence. SCO claims something different. We just have to wait for SCO's day in court.

      --
      Vote for Pedro
    11. Re:Confused by Dion · · Score: 1

      disconnected from everything else when a largish part is composed of BSD tools

      Because:

      1. We are talking about Linux the kernel, not tools.
      2. When talking about a linux distribution the tools are from GNU, NOT BSD.

      Linux is in no way derived from Unix, it is however modeled on Unix.

      --
      -- To dream a dream is grand, but to live it is divine. -- Leto ][
    12. Re:Confused by realdpk · · Score: 1

      It could conceivably be provable - have an independant 3rd party compile the code in question and compare it to existing UnixWare installs. If the binaries match (which they ought to, I'd think, barring major weirdness) then you know the code was once there. Or, you're at least reasonably certain.

  15. seen this before by daveatwork · · Score: 2, Interesting

    Yeah, i saw this ages ago (well, a few days anyhoo). I found it fairly interesting, until i looked outside and was mesmorised by the grass growing!

    Honest, I do think this is an interesting case, purely from one view point. The claims SCO have raised are valid, but since the legal submission they gave to the court is 'open source', ie everyone can read it, the amount of evidence piling up against SCO is astonishing. The interesting point is how on earth SCO feel their gonna get out of this. I can't wait for it to hit the courts....

  16. More Conspiracy ... by barfomar · · Score: 3, Interesting

    With Microsoft is now licensing Unix from SCO,they're probably planning on using SCO as a FUD lever (or worse) against Linux The result could be a bidding war between IBM and Redmond to control SCO. IBM could buy out the sickly company to euthanize it. SCO sold their soul in hopes somebody would bid it up to take them out of their misery.

    1. Re:More Conspiracy ... by stanmann · · Score: 2, Informative

      IBM doesn't want SCO. Less hassle to win this suit and crush SCO. Especially since buying SCO would suggest that the suit has any merit. IBM makes money on Linux, or they wouldn't be selling it. IBM is an ancient giant. They have survived the various computer revolutions, and have an enterprise attitude. IBM isn't going away, and has always been the Corporate and Government trend setter. Despite mistakes like MCA and the OS/2 fork, they have endured, and will likely continue to evolve, adapt and overcome.

      --
      Food not Bombs is a nice platitude but it breaks down when you notice that the Bombees are usually well fed
    2. Re:More Conspiracy ... by Anonymous Coward · · Score: 0

      considering the timing M$ got themselves into this matter, I can't stop thinking this has been a well planned FUD/smear campaign against OpenSource conducted by M$ from the beginning. sco's mcbride said he talked with several "experts" to determine if IBM's code (or Linux code, whatever) is infringing their IP. I won't be surprised if these "experts" are from Redmond. I can see Steve Ballmer and his clan soon be saying to government & other big clients that Linux is "illegally pirated OS" and therefore they should stay away from opensource ... until the trial is over. maybe M$ will support SCO suing every linux distributors until longhorn is ready to ship.

    3. Re:More Conspiracy ... by Anonymous Coward · · Score: 0

      i think ibm will not buy sco on this one - at least not before the suit is over. it's a matter of public image first - they would give merit to the case and portray themselves as thieves if they took the easy way out. even being ibm (and huge and resilient wrt to computer market fluctuations such as sco dying and all) an accusation of theft does not sit well unresolved on their public image. plus they need to erase this 'we can revoke your aix license any time we feel like' idea once and for all.

  17. what would Nelson say? by stonebeat.org · · Score: 1

    ha ha! Offcourse he would say "haha" whether is SCO or ISO :)

    1. Re:what would Nelson say? by Anonymous Coward · · Score: 0

      Please, $CO and GNU/O$I.

  18. If you don't read anything else, read this... by HotNeedleOfInquiry · · Score: 4, Interesting
    One is that, despite misleading claims implied on SCO's web pages by phrases like "exclusive licensing", SCO does not own or control the Unix trademark. As we have previously observed, that trademark -- and the privilege of suing IBM for relief on a trademark-violation theory -- belongs to The Open Group.

    Furthermore, SCO is barred by the terms of the GNU General Public License from making copyright or patent-infringement claims on any technology shipped in conjunction with the Linux kernel that SCO/Caldera itself has been selling for the last eight years. Therefore, SCO may accuse IBM of misappropriating SCO-owned software to improve the Linux kernel only if that software does not actually ship with the Linux kernel it is alleged to be improving!

    Finally, SCO is barred from making trade-secret claims on the contents of the Linux kernel, not merely by the fact that the kernel source is generally available, but by the fact that SCO has made the sources of its Linux kernel available for download from SCO's own website!

    --
    "Eve of Destruction", it's not just for old hippies anymore...
    1. Re:If you don't read anything else, read this... by PhilHibbs · · Score: 4, Interesting
      Furthermore, SCO is barred by the terms of the GNU General Public License from making copyright or patent-infringement claims...
      I'm not sure I like where that line might lead. By that logic, if someone decides to mirror a Linux distro on their servers as a public service, not knowing that it contains code that has been stolen from them, they lose all redress. If I were a large organisation offering free mirroring space, such as, say, The University of Manchester (I got that from gnu.org's list of mirrors), I might think twice about continuing to do so. It gives credence to what I previously disregarded as Microsoft's FUD about the 'viral' GPL.
    2. Re:If you don't read anything else, read this... by be-fan · · Score: 1

      That's not anywhere in the same league. If your company is shipping a product, and doesn't know if there are copyright violations in the code, that's a huge problem. If the police find cocaine in the cupcakes I'm selling to children, the "I didn't know it was there!" excuse isn't a very good one.

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:If you don't read anything else, read this... by PhilHibbs · · Score: 1

      I agree, but it's still fantastic ammunition for Microsoft to use in scaring companies, universities, and governments away from the GPL.

    4. Re:If you don't read anything else, read this... by drnlm · · Score: 3, Insightful
      But SCO did not merely mirror the kernel, they actively distributed it - buy selling distrubitions, by posting security patches on their ftp-server and by sending security advisories to their clients advising them to download the code.

      Nobody claims that the University of Manchester is the distibuter of the gnu tools they mirror, they claim that the FSF is. SCO's case is very different and not helped by the fact that they only pulled their distributions some time after filing suit against IBM.

      Furthermore, the fact that they were making threatening noises towards other distributions, while still actively distributing their own, makes it very hard for them to argue that they had not previously been aware of the possibility that they were distriuting the claimed infringing code under GPL. Especially as this point has been trotted out in every slashdot discussion on the subject.

    5. Re:If you don't read anything else, read this... by realdpk · · Score: 1

      SCO distributed the allegedly "infringing" code themselves. That's what he means.

    6. Re:If you don't read anything else, read this... by PhilHibbs · · Score: 1
      But SCO did not merely mirror the kernel, they actively distributed it -
      Yes I know, but inferences can easily be drawn, extrapolations made, and FUD spread from tiny acorns like this.

      How about another analogy - Lets say a big agribusiness like Monsanto owns the rights to some GM plant or other, and they also own a subsidiary that makes energy bars. The subsidiary buys a load of glucose that is made from ripped-off Monsanto seeds, and sells it in their energy bars. Have Monsanto now lost their IP? I don't think so. Bring in the GPL, and this intuitive no-brainer comes in danger of being a big loser for big business. That's bad for GPL adoption, even if the arguement has been twisted to fit an agenda.
    7. Re:If you don't read anything else, read this... by bobKali · · Score: 1

      That's probably the most coherant analogy adressing the GPL argument that I've heard so far.

      But this still sounds a lot like using "we didn't know we were infringing" to prevent the loss of trade secrets. Is this a defense only available to the owner of said secrets? I think it's interresting that the only recepient of a related lawsuit (so far) is IBM, the supposed infringer.

    8. Re:If you don't read anything else, read this... by spitzak · · Score: 1

      I think "we didn't know we were infringing" is a legitimate defense. However they must actively do actions to "fix" this "mistake". In this case it means SCO must immediately release sufficient information so that everybody can remove the infringing code from the Linux distributions.

    9. Re:If you don't read anything else, read this... by jedidiah · · Score: 1

      To be kind, your "analogy" stretches the truth a bit.

      a) There is no "subsidiary" involved here. SCO/Caldera one small unified company. It's not some monster like Monsanto.

      b) No one is claiming that SCO would lose rights to ALL of it's code. It only loses rights to those bits that it has given away already.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    10. Re:If you don't read anything else, read this... by Anonymous Coward · · Score: 0

      Microsoft's Shared Source program has exactly the same restriction in it. Only, if you put your IP in their program, THEY OWN IT.

    11. Re:If you don't read anything else, read this... by Anonymous Coward · · Score: 0

      I am not trying to argue with your comment, just pointing out that your writing style is overly synthetic, which is common among people with low self esteem!

      Have you realized that you are a fucking dork yet? Really, read through past comments you've made. You are a fucking loser who attempts to talk down to people without any real agenda or personal foundation. You are probably 46 years old, fat, bloated, with a receding hairline and play role-playing games. I might be wrong, but I doubt it.

    12. Re:If you don't read anything else, read this... by schon · · Score: 1

      By that logic, if someone decides to mirror a Linux distro on their servers as a public service, not knowing that it contains code that has been stolen from them, they lose all redress.

      No, it doesn't. Here's a better way of putting it:

      if someone decides to mirror a linux distro on their servers as a public service, not knowing that it contains code that has been stolen from them, then they find out about it, and continue distributing it , then they lose all redress.

    13. Re:If you don't read anything else, read this... by Trogre · · Score: 1

      GPL is not the virus.
      GPL is the cure.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    14. Re:If you don't read anything else, read this... by Anonymous Coward · · Score: 0
      By that logic, if someone decides to mirror a Linux distro on their servers as a public service, not knowing that it contains code that has been stolen from them, they lose all redress.

      I disagree. Mirroring a website is no different than functioning as an ISP. The mirror has no control over the content. They are simply providing a charitable service for the originating site. By your logic, if I were to donate to the Free Software Foundation, I would lose my intellectual property rights if the FSF were to violate them.

      The SCO case is different since SCO sold a Linux distribution and actively participated in Linux development. SCO even helped develop the 'enterprise' features that IBM allegedly introduced.

    15. Re:If you don't read anything else, read this... by PhilHibbs · · Score: 1
      GPL is not the virus.
      GPL is the cure.
      Gosh, that helps so much, it's all clear now!
  19. Re:As an attorney... by gunne · · Score: 1

    Good troll there, mr. anonymous...
    Now go play somewhere else.

  20. An overblown paper by Anonymous Coward · · Score: 0, Troll

    IBM neither requested nor required SCO's permission to call their AIX offering a Unix.

    Big whoop. Yet another pointless, posturing remark from a paper of dubious value.

    If you have a knowledge of Unix history, read the paper with a critical eye, and do a little research, its not hard to find errors, omissions, overstatements, and what appear to be some dubious legal claims.

    I think that the Linux community is going to be very disappointed if it is relying upon this paper for its views.

    1. Re:An overblown paper by dmayle · · Score: 1

      This kind of reminds me of the whole ArtX Ars Technica thing awhile back... Is there anyway to verify that this AC didn't post from SCO? (Sorry if this is a troll)

    2. Re:An overblown paper by finkployd · · Score: 1

      If you have a knowledge of Unix history, read the paper with a critical eye, and do a little research, its not hard to find errors, omissions, overstatements, and what appear to be some dubious legal claims.

      But much too hard for you to post these supposed errors. Go ahead. Show us how smart you are.

      Finkployd

    3. Re:An overblown paper by Eunuchswear · · Score: 2, Interesting
      But much too hard for you to post these supposed errors. Go ahead. Show us how smart you are.
      Much more polite to point out the errors to ESR, gives him a chance to fix them.

      The current version (1.7 as I write) is more accurate than the earlier ones (I think 1.2 was the first I saw).

      Originaly it had statements like (from memory, can't find the CVS copy online):

      blah, blah, blah, ... enterprise features: JFS, LVM, SMP, NUMA, hotswap, ... SCO Unix has none of these
      The current version says
      We can therefore state that of the component technologies for enterprise scaling, the Bell Labs codebase includes a journaling file system (in the form of the VxFS Veritas journaling file system) and LVM (in the form of VxVM). But SMP only entered the line in 1995 with UnixWare 2. PCI hot-swapping came in only in 1998 with Unixware 7.
      So now he admits that UnixWare (the code that IBM had access to via Project Monterey) has all but one of the features in his checklist. (It has NUMA as well, but it takes a while to fix those position papers).
      --
      Watch this Heartland Institute video
  21. Re:Legal issues by Anonymous Coward · · Score: 0

    How could you hope not to be considered a troll? Unless you are an attorney working on the case, you've seen the same court documents and press statements as the rest of us have. SCO has not demonstrated their claim. SCO acknowledges that IBM has a unrevokable, perpetual license to the SCO UNIX sources. You can show all of the case law you like, but you still have to have evidence.

    I suggest that we all just wait and see what happens, because, for all of our comments on slashdot, it's what the judge hears from the two sides in the case that will really determine the outcome.

  22. I just read the whole thing by techstar25 · · Score: 1


    If you only read one position paper all year . . .

    Seriously, this should be required reading for all slashdot visitors. It had a lot of great info. If you read the paper, you'd realize that SCO doesn't have a chance in hell (which is kind of what we thought anyway).

    1. Re:I just read the whole thing by Eunuchswear · · Score: 1

      And don't forget to point out the errors you find to ESR. He does fix them. Slowly.

      --
      Watch this Heartland Institute video
  23. Definition of "derived" is the key by OmniGeek · · Score: 5, Insightful

    I believe the key is what "derived" means in the context of that graphic. Yes, Linux uses UNIX design concepts and structures, but that's true of all the OSes in the graphic; to that extent, they're all related. Solid lines indicate direct inheritance of code. The off-to-the-side bit reflects the fact that Linus' original project was built from scratch and didn't use code from the other family members.

    WRT the use of BSD tools, I suspect this was a judgement call in producing a readable graphic describing major influences. Show all interactions and the page is an unreadable mess, (possibly resembling the profile of a gnu?).

    --

    "My strength is as the strength of ten men, for I am wired to the eyeballs on espresso."
  24. counter sue sco by Anonymous Coward · · Score: 1, Insightful

    can we counter sue these motherfuckers for messing with us for no reason, knowingly trying to fuck up an important part of the industry?

    This is BS .. fuck.

  25. ESR just couldn't resist... by spakka · · Score: 3, Insightful

    [4] We use the term "hacker" in its correct and original sense here, as an enthusiast or artist of computer programming.

    'Hacker' is pejorative for many concerned with law enforcement, who do not care about ESR's 'hacker/cracker' agenda. Why not just call them 'contributors' or 'authors'? I don't see references to 'Micro$oft' or even 'Unices' in the document.

    1. Re:ESR just couldn't resist... by Anonymous Coward · · Score: 0

      Indeed. Words mean what the majority of people who say or hear the word think it means. 'Hacker' has a bad connotation now to most people, deal with it. No dictionary, jargon file, or rabid advocate will change that.

      This applies to that whole GNU/Linux sillyness too.

    2. Re:ESR just couldn't resist... by gosand · · Score: 4, Insightful
      'Hacker' is pejorative for many concerned with law enforcement, who do not care about ESR's 'hacker/cracker' agenda. Why not just call them 'contributors' or 'authors'?

      Because they are hackers. Why did he use that term? Well, he did write the book on it, so to speak.

      I am really saddened at the weak constitutions of most people today, even in the tech community. Everyone has a "why not conform?" attitude. What ever happened to actually having beliefs in something and standing up for it? Everyone derides ESR and RMS because they stick by what they believe in. Even if you don't agree with them, why do you feel that they need to change their stance? Why does everyone need to have the same opinion on things?

      Even though I haven't seen it yet, I have seen this quote from the Matrix Reloaded:
      Lock: Not everyone has the same beliefs as you do.
      Morpheus: My beliefs do not require them to.

      ESR, RMS, and others HAVE beliefs in things - what do you believe in?

      --

      My beliefs do not require that you agree with them.

    3. Re:ESR just couldn't resist... by Anonymous Coward · · Score: 0

      It's how people use the word that will ultimately gives it its meaning. OSI try to bring back the original sense by using it that way. We should all do the same to help them bring back its real meaning.
      Wether it is the right moment to fight that battle is another story...

    4. Re:ESR just couldn't resist... by jgerman · · Score: 1
      'Hacker' is a word that's been around long before law enforcement abused it, by people who don't care about law enforcements agenda.


      Their called hackers because it's a term of respect and has been before ESR, before the media perverted it, and likely before you came on the scene. Else you would know the history of the word.

      --
      I'm the big fish in the big pond bitch.
    5. Re:ESR just couldn't resist... by brlewis · · Score: 1

      Before its meaning got distorted, the majority of people who said or heard "hacker" thought it meant something more like what ESR says. By your reasoning, no bad press, law enforcement, etc. would have changed that. But you're wrong. Word meanings change. They can change back. Deal with it.

    6. Re:ESR just couldn't resist... by spakka · · Score: 1

      I am aware that the popular usage of 'hacker' differs from its technical, historical usage. This bothers me about as much as people talking about pencil 'lead' instead of 'graphite-clay composite'.

    7. Re:ESR just couldn't resist... by jgerman · · Score: 1

      If it didn't bother you then you wouldn't have complained about it.

      --
      I'm the big fish in the big pond bitch.
    8. Re:ESR just couldn't resist... by Shimbo · · Score: 1

      I am really saddened at the weak constitutions of most people today, even in the tech community. Everyone has a "why not conform?" attitude. What ever happened to actually having beliefs in something and standing up for it? Everyone derides ESR and RMS because they stick by what they believe in.

      At some point you have to accept that natural languages change; writers of dictionaries realise this and eventually accept common usage.

      The Jargon File defines exactly that - Jargon, of which one dictionary definition is "Speech or writing having unusual or pretentious vocabulary".

      Insisting on the meaning of a word stay fixed is, sooner or later just another windmill-jousting exercise. To coin a phrase, "language wants to be free".

    9. Re:ESR just couldn't resist... by spakka · · Score: 1

      If it didn't bother you then you wouldn't have complained about it.

      I didn't. I just doubted whether it was helpful to shoehorn the debate into this legal submission. You were the one getting all emotional and defensive about it.

    10. Re:ESR just couldn't resist... by Xabraxas · · Score: 1

      Yeah well hackers still use the term hacker because it's what they're used to and its meaning is now intrinsic to the word, so deal with it. In my world I don't hear the word "hacker" used in a negative sense.

      --
      Time makes more converts than reason
    11. Re:ESR just couldn't resist... by raju1kabir · · Score: 1
      Before its meaning got distorted, the majority of people who said or heard "hacker" thought it meant something more like what ESR says. By your reasoning, no bad press, law enforcement, etc. would have changed that. But you're wrong. Word meanings change. They can change back. Deal with it.

      The other possibility is that spakka believes in Ordination Linguistics, a school of thought that holds that every morpheme combination has an ultimate meaning consequent to the basic structures of organic matter and the physical universe, and that the observed meanings are slowly converging toward this predetermined state. When this happens, thousands of years from now, language will stop evolving and communication will be a zero-friction exercise. Perhaps he believes that "hacker" meaning "computer criminal" is what they call an "early complete", meaning a word that has achieved convergence with its universal meaning ahead of the bulk of the lexicon.

      Okay, I just made all that up. But it's either that, or he was trained by the French language board, the group that has determined that French as of circa 1990 is the archetypical perfect language and no new words shall be allowed to enter, despite the fact that French evolved over the centuries through the absorbtion of words from other language groups.

      --
      "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
    12. Re:ESR just couldn't resist... by Black+Copter+Control · · Score: 1
      'Hacker' is pejorative for many concerned with law enforcement, who do not care about ESR's 'hacker/cracker' agenda. Why not just call them 'contributors' or 'authors'? I don't see references to 'Micro$oft' or even 'Unices' in the document.

      Language is a very context-sensitive space. "garbage collection", for example means entirely different things in the context of sanitation engineering than it does in the context of computer engineering. "My partner" can mean very different things depending on whether it is meant to be in a buisness context or a romantic context. Evem phrases such as "nice buns", or "fuck the dog" can have very different meanings depending on context.

      None of the meanings is intrinsicly 'wrong'. They simply require the proper context to be unambiguous.+

      If you create the proper context for a word, you can use it in any one of it's common meanings. By creating a context for the use of the word 'hacker', the OSI paper was simple being accurate in it's use of language.

      --
      OS Software is like love: The best way to make it grow is to give it away.
    13. Re:ESR just couldn't resist... by gosand · · Score: 1
      The Jargon File defines exactly that - Jargon, of which one dictionary definition is "Speech or writing having unusual or pretentious vocabulary". Insisting on the meaning of a word stay fixed is, sooner or later just another windmill-jousting exercise. To coin a phrase, "language wants to be free".

      Odd that you would, in a way, demean the jargon file because of the word "jargon", give a standard dictionary definition of "jargon", then argue that the meaning of words need to be able to change!

      Believe me, I understand the importance of language - I am married to a woman who got her masters in French linguistics. I get lessons all the time on the Latin origin of words, how words have changed over time, etc etc. While it is OK to accept the change of words, it is also OK to fight to retain the meaning of some words. You can argue that people misuse their/there/they're or your/you're all the time, and that's OK because you can figure out what they mean. But I will continue to cringe every time I see it because it is quite simply wrong.

      I think there is a difference between a word naturally progressing or evolving (like the word fax) as opposed to something that changes because of misuse. (hacker being one of those) Allowing the media and/or corporations to force the evolution of our language is a terrible thing to let happen. They are able to coin phrases and ramrod them down our throats until we have no choice but to accept them. "Intellectual Property" springs to mind.

      Just because the President of the United States mispronounces nuclear doesn't make it right.

      --

      My beliefs do not require that you agree with them.

    14. Re:ESR just couldn't resist... by Anonymous Coward · · Score: 0

      "the majority of people who said or heard "hacker" thought it meant something more like what ESR says"

      That's not true. The majority of people thought it meant "a bad golfer" or a "someone with poor workmanship".

      The idea of a Hacker being someone good with computers was mainly local to MIT. In the mass media, a "Computer Hacker" has always been associated with breaking into computer systems, and the ESR definition never had broad currency.

    15. Re:ESR just couldn't resist... by the+Atomic+Rabbit · · Score: 1
      Because they are hackers. Why did he use that term? Well, he did write the book on it, so to speak.

      Actually, he didn't write the book; he stole it.

    16. Re:ESR just couldn't resist... by Anonymous Coward · · Score: 0

      What do I believe?

      I believe that using the word 'programmer' would have been more effective at convincing the audience of the argument.

      The people who have weighed in on the use of hackers have neglected the intended audience. The slashdot crowd is not the intended audience for this document. This document was written (though disclaimed as such) as a friend of the court brief.

      Imagine the judge asks, "Who let hackers write unix? Isn't that dangerous?"

      Then you reply, "Judge, your an idiot. Don't you know about...(diatribe on term hackers)"

      The article could maintain correctness without engaging in pedantry.

      Actually, the article didn't engage in pedantry as far as the intended audience is concerned. We all know this to be true, but the judge doesn't.

      As far as the judge knows, bad people who steal computing access and resources are the same people who worked on Linux. These "stealing people" are associated with IBM and the case at hand is about stealing intellectual property. This is not an association we want to be formed in the mind of the judge. It doesn't matter what we all think of the inconsequential hacker/cracker debate.

      It matters what the judge decides on the case at hand.

      Later,
      LurkerAgain

    17. Re:ESR just couldn't resist... by Anonymous Coward · · Score: 0

      [b]Well, he did write the book on it, so to speak.[/b]

      Naw, he just took credit for others work.

      [b]Why does everyone need to have the same opinion on things?[/b]

      Hey, I'm cool with that. Now tell ESR and RMS to stop trying to ram their opinion down my throat.

      [b]ESR, RMS, and others HAVE beliefs in things - what do you believe in?b]

      Capitalism.

    18. Re:ESR just couldn't resist... by Anonymous Coward · · Score: 0

      What ever happened to actually having beliefs in something and standing up for it?

      The USA happened to Iraq, and now everyone is too scared of becoming an enemy combatant. Conformity is safer.

  26. SCO is crazy by Andy+Dodd · · Score: 4, Insightful

    When suing someone else in the corporate world, you must be very careful of one thing:

    Make sure they can't countersue you on something else.

    If IBM were smart, they'd go looking through their patents and technology and countersue SCO into the stone age.

    Chances are EXTREMELY good that a company as large as IBM has something to fire back at SCO. Patents are as useful for defending oneself against extortion as they are for extorting money from people in the corporate world. (Many companies file patents solely for defensive purposes - If someone goes after them for patent infringement, they hope that they can strike back with their own patent infringement claim.)

    --
    retrorocket.o not found, launch anyway?
    1. Re:SCO is crazy by dsplat · · Score: 1

      There's one problem with IBM countersuing right now. If they do sue SCO into bankruptcy, someone else will end up with the IP rights that SCO is suing over. This whole thing could come up again. Assuming that we are correct and that IBM is extremely likely to win this case, it is in their interest to get it decided in their favor. Then it doesn't matter much what happens to SCO.

      --
      The net will not be what we demand, but what we make it. Build it well.
    2. Re:SCO is crazy by UnknowingFool · · Score: 1

      Countersuing is a good idea. Since it doesn't seem that SCO learned anything from the BSD fiasco, they may have done the same thing again.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    3. Re:SCO is crazy by drinkypoo · · Score: 1
      Chances are EXTREMELY good that a company as large as IBM has something to fire back at SCO.

      It's not the size, it's what you do with it :) IBM has a load of patents because they spend a LOT of money on R&D and subsequently patenting their ideas. Nearly every ground-breaking advance in computer technology lately has either come right out of IBM or is based on something that came out of IBM.

      As far as I understand, however, most of those patents are in the hardware realm.

      IBM is one of the largest patent-holders around, and they continue to get new patents very rapidly, being one of the leading patent-producers.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  27. lawyers read slashdot? by Anonymous Coward · · Score: 1, Insightful

    I wonder if lawyers (hopefully the ones on our side) search/read thru slashdot and other places similar for ideas. I hope they do. Amongst all of the crap there are some half way decent ideas, facts, and angles.

  28. Microsoft linkage by moehoward · · Score: 5, Interesting

    Considering the history of SCO in the mid-late 80s, you have to wonder how closely MS and SCO remained linked at the executive levels. Gates really liked UNIX and MS had their hands in the mix in that time frame. Gates is technical and understands why Unix/Linux is powerful and he actually liked working with it. SCO took over all the MS aspects of their initiative (sort of) back in the 80s/early 90s.

    I suspect that their is more here than meets the eye in terms of collusion between MS and SCO. I could see MS picking up SCO if they can damage Linux in the process.

    To spell it out, here is what I'm suggesting (IMHO): I suspect MS and SCO execs are acquaintences. I suspect that MS execs tugged on the SCO execs to make some troubles for Linux (starting with the IBM thing whenever). I suspect that they have a big bag of such issues with which to harass Linux vendors. I suspect that MS will enter the Linux/Unix arena in the next 3 to 5 years, possibly through an aquisition of SCO.

    Question: Was SCO part of the anti-trust suits and related suits against MS? If so to what degree?

    --
    "If you want to improve, be content to be thought foolish and stupid." - Epictetus
    1. Re:Microsoft linkage by Eunuchswear · · Score: 1
      Question: Was SCO part of the anti-trust suits and related suits against MS? If so to what degree?
      Yeah SCO was. It sued Microsoft and won. Twice.

      Original SCO complaing to the European commission about Microsoft holding them to a license that ATT signed giving Microsoft a little bit of every SVR3.2 or later system for ever and ever. And SCO won. (Gota love that Microsoft way of papering over a defeat).

      Caldera, now known as "Caldera D/B/A The SCO Group" sued Microsoft over anti-commercial suppression of DR-DOS. (That Caldera had bought just to get a bit of the action).

      So, you're right. SCO was heavily involved in the various Microsoft anti-trust suits, as one of the more successful anti-Microsoft entities.

      Oh dear, more paranoia turns out to be dubious.

      --
      Watch this Heartland Institute video
    2. Re:Microsoft linkage by moehoward · · Score: 5, Funny

      I agree with your paranoia comments. I'd mod me down if I could.

      I'd still look for connections down the road. MS sure capitulated to SCO mighty fast. But, don't discount Gates' respect for Unix/Linux either.

      But after doing a painfully difficult 1 minute search on Google, I'd say SCO is looking more and more like a Rambus. The lawyers are calling the shots. I see their gripes with MS.

      I'll start working on an Illuminati and Free Masons angle. That will be much more diffiulct to call paranoia because we all know they run the world anyway.

      --
      "If you want to improve, be content to be thought foolish and stupid." - Epictetus
    3. Re:Microsoft linkage by G27+Radio · · Score: 2, Interesting

      I suspect that their is more here than meets the eye in terms of collusion between MS and SCO. I could see MS picking up SCO if they can damage Linux in the process.

      It's interesting that in the month leading up to this I've seen a couple quotes from Microsoft representatives stating that they would be creating a version of their OS that doesn't require the Windows GUI. This is a big step towards Windows becoming more like Unix. Perhaps this is related somehow?

      It would make sense that the best way for Windows to compete with Linux is to become more like Linux. At least in the areas where Linux is clobbering MS. It's just the timing that makes me wonder if these things are related.

    4. Re:Microsoft linkage by Anonymous Coward · · Score: 0

      I doubt Gates has much respect for Unix. His non-micro background was more with the DEC mainframe stuff, and like most 'framers he probably sees Unix as the hacked-together kludge that it is.

      It's an open secret that MS used UNIX internally well into the 90s, but none of that experience made it into Windows NT. In fact Gates hired one of the most notorious UNIX haters out there, Dave Cutler, as NT's architect.

      The MS line going way back is that "Unix is old and obsolete and going away". Like most borg-thought, this no doubt comes directly from Gates.

    5. Re:Microsoft linkage by moehoward · · Score: 1

      The MS "line" is not necessarily what Gates thinks. Harken back to the Xenix days. For you youngsters out there, yes, MS sold and supported Xenix and Xenix tools for years. SCO picked it all up as MS exited that realm. And don't forget some of the command line and file system features "stolen" from Unix in the dawning days of DOS.

      As soon as it becomes advantageous for MS to be in *nix again, they will be all over it from angles you can only dream of. The MS strategy is simple: Long-term Profit. Don't confuse marketing-droid speak with the mindset of Mr. Gates and Mr. Ballmer.

      Step 1: Profit.
      Step 2: Profit.
      Step 3: Profit.

      MS is in business to make money, not to make wet dreams for technologists.

      --
      "If you want to improve, be content to be thought foolish and stupid." - Epictetus
    6. Re:Microsoft linkage by Anonymous Coward · · Score: 0

      Yeah, Microsoft got involved in UNIX -- decided it was political clusterfuck and not a very good technical platform for their ambitions, so they dropped it and rolled their own.

      As for the "line" -- Microsoft sells an authentic UNIX98-certified subsystem for NT called SFU/Interix. And by "sell", I mean "bury in obscurity while pushing Win32 and NET as a UNIX migration target". Meanwhile they lose tons of business to Linux.

      It would be advantagous for them to push Microsoft UNIX, aka Interix, *right now*. But they don't.

  29. More likely IBM fucks SCO over by Anonymous Coward · · Score: 0
    If, as you say, IBM is making money off OSS (and they probably are), IBM should rip SCO open and fuck 'em with a telephone pole - an old telephone pole with lots of splinters. Just to set an example.

    Thus, no company will attack OSS IP in the future, and the M$ proxy server SCO has an all-too-appropriate permanent BSOD.

    We can only hope.

  30. Re:As an attorney... by KingRamsis · · Score: 2, Funny

    I beg to differ as a corporate lawyer specialized in IP laws I think you mom sucks real hard.

    now mr.trollboy go play somewhere else.

  31. Man I just read that whole thing... by xMonkey · · Score: 0, Offtopic


    PWND!

  32. Interactive UNIX by thomasa · · Score: 0, Offtopic

    I spend $1500 on a unlimited user UNIX
    called Interactive UNIX. It was marketed
    by Sun at the time. It was a true SVR3.2
    running on Intel. This was in 1994.

  33. They only need to muddy the waters by ewg · · Score: 2, Interesting

    Win, lose, or draw, SCO can hurt Linux merely by muddying the waters.

    --
    org.slashdot.post.SignatureNotFoundException: ewg
  34. GNU's Not Unix. by mfh · · Score: 0, Troll

    BSD tools are BSD tools, and Linux tools are GNU tools.

    http://www.gnu.org

    Why do you think Stallman and his ankle-biters are so adamant about calling it GNU/Linux? Cause they're all BSD fans?

    --
    The dangers of knowledge trigger emotional distress in human beings.
  35. Wonder what Ray Noorda thinks of all this? by Anonymous Coward · · Score: 3, Insightful
    "In 1994, a group of Novell alumni formed Caldera Systems International with the backing of Novell's founder, Ray Noorda. Caldera was intended to be a Linux distributor, aiming at the business and enterprise market."

    Interesting how Caldera held the torch as it were for DRDOS (which IMHO was the TRUE and technically superior DOS for the PC, insofar that it really WAS better than MSDOS (aka "Messy DOS"), it derived directly from from Digital Research whereas MSDOS was the bastardization of Digital Research's CPM and further mangled by Bill Gates et al.) and DRDOS was MSDOS' direct and main competitor back in the day. Also interesting is the fact that Ray Noorda was involved in the formation of Caldera. It's no secret that there was no love lost between Mr. Norda and Bill Gates - especially from Ray Noorda's side.

    With the way that SCO/Caldera has appeared to have become Microsoft's bitch, Mr. Noorda must be choking on his biscuits right about now.

    1. Re:Wonder what Ray Noorda thinks of all this? by twos · · Score: 1
      MSDOS was the bastardization of Digital Research's CPM

      More correctly:

      Excerpted from The Unusual History of MS-DOS

      The "Microsoft Disk Operating System" or MS-DOS was based on QDOS, the "Quick and Dirty Operating System" written by Tim Paterson of Seattle Computer Products, for their prototype Intel 8086 based computer.

      QDOS was based on Gary Kildall's CP/M, Paterson had bought a CP/M manual and used it as the basis to write his operating system in six weeks, QDOS was different enough from CP/M to be considered legal.

      Microsoft bought the rights to QDOS for $50,000, keeping the IBM deal a secret from Seattle Computer Products.

      --
      Phear The Phat Penguin
    2. Re:Wonder what Ray Noorda thinks of all this? by SN74S181 · · Score: 1

      Ray Noorda bought DR-DOS as a holding to enable him to sue Microsoft. He is known as a spiteful man and there were other early issues where he was 'stabbed in the back' by Microsoft.

      DR-DOS has no particular lineage to CP/M and to say that it is 'the one true DOS' and MS-DOS is a bastardization of history. Further, it came late on the market after MS-DOS had been established as the dominant OS on it's hardware platform. If you want to look at the Digital Research product that does have the CP/M heritage and that failed in the market, it's CP/M-86, which was marketed as an alternative OS for the IBM PC (along with Xenix, by the way...) as an alternative, but failed. Wait awhile and maybe I'll sell you my boxed CP/M-86 set, which I'm considering hawking on eBay. But please, oh please, don't blather on about something you appear to know nothing about.

      The biggest similarity between 'Noorda/DR-DOS' and 'SCO/UNIX codebase' is that SCO's ownership of the UNIX codebase enables the suit they are engaging in, just like Caldera's ownership of the DR-DOS codebase enabled their legal hijinx. The humorous thing about it all is the chorus of 'Gooooo Noorda!' that was heard in the DR-DOS vs. Microsoft case and the rank hypocrasy of the side the same pundits are taking now.

    3. Re:Wonder what Ray Noorda thinks of all this? by ebh · · Score: 1

      The about.com article was an interesting capsule summary, I found the comma-splices disturbing.

    4. Re:Wonder what Ray Noorda thinks of all this? by jedidiah · · Score: 1

      The DR-DOS cause of action Microsoft was a well publicized historical fact the details of which were published in the tech magazines of the day.

      Attempting to equate this to the empty claims that SCO has made against IBM is simply assinine.

      Better a hypocrite than a moron.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    5. Re:Wonder what Ray Noorda thinks of all this? by SN74S181 · · Score: 1

      I am addressing the issue that the 'wronged party' in the DR-DOS case was not Ray Noorda by any stretch of the imagination. In fact, he got a hell of a deal, he purchased DR-DOS at firesale prices, in part because Microsoft had turned the product into something near worthless. He bought it primarily as a vehicle to sue Microsoft. He was NOT the wronged party.

      Similarly, the 'wronged party' in the Caldera/SCO case is somewhere in the distant past. The value to SCO in their holding of rights to the UNIX source is primarily in it's utility for suing IBM.

    6. Re:Wonder what Ray Noorda thinks of all this? by Anonymous Coward · · Score: 0

      The issue with the Windows Beta and DR-DOS wasn't really the main thrust of the case.

      Caldera/SCO was suing on restraint-of-trade issues having to to with Microsoft's OEM contracts.

    7. Re:Wonder what Ray Noorda thinks of all this? by jedidiah · · Score: 1

      It doesn't matter that Ray wasn't the wronged party. The fact remains that THERE WAS A WRONGED PARTY. It was a genuine wrong. It was a just action to persue the matter. It wasn't merely barratry.

      SCO has yet to demonstrate that any real wrong has occured. Until that occurs, no one has any reason to assume that they are not currently commiting barratry.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    8. Re:Wonder what Ray Noorda thinks of all this? by Anonymous Coward · · Score: 0

      Then how do you explain the fact that Gary Kildall found quite a bit of his CP/M code in MS/PCDOS (see "twos" post above) and as a result, both IBM and MS paid him out a rather substantial amount of money with the proviso being that all 3 parties keep quiet about it for a certain number of years?

    9. Re:Wonder what Ray Noorda thinks of all this? by ShadowDrake · · Score: 1

      >DR-DOS has no particular lineage to CP/M

      CP/M begat CP/M-86 (and CP/M-68k). CP/M-86 begat DR-DOS.

      If you fire up a DR-DOS system, you'll see something like "Copyright 1976-1998". The 1976 is when CP/M was beginning.

      --
      It's just like a fascist dictatorship, without the punctual rail service!
  36. ISC Interactive Unix by Anonymous Coward · · Score: 0

    To add to the list of x86 UNIX's, there is ISC Interactive UNIX which SunSoft bought. If I remember my history correctly, they used portions of that to help with drivers for Intel Solaris.

  37. Quasi dupe by Anonymous Coward · · Score: 0

    This was covered (not very well) yesterday: link

  38. Re:My experiences with Linux by Lumpy · · Score: 1, Troll


    I felt that I was up to the job to convert the entire server pool to the Linux technology. I had several years experience programming VB, C#, ASP, and .NET Framework at the kernel level.


    so linux is a failure because you were horribly underskilled for the job?

    does that mean that Ford is at fault for all the bad drivers on the road?

    I know that you are just a troll, but some of the newbies here will read you and actually believe your tripe.

    Linux = success if you have skilled and capable people behind it... Windows expierience = nothing in the Linux world as you need REAL TCP/IP skills REAL Netowrk skills and REAL computer skills. something that no MS certification delivers or shows.

    you failed because you assumed and did not have the skills to do the job (and after reading it I strongly suspect any project management skills you have..)

    --
    Do not look at laser with remaining good eye.
  39. MS cannot buy SCO by codepunk · · Score: 1

    Think about it, MS cannot possibly buy SCO else the wrath of a new anti-trust suit.

    --


    Got Code?
    1. Re:MS cannot buy SCO by Anonymous Coward · · Score: 0

      Yeah, and they were sooooo hurt by the last one...

  40. Re:My experiences with Linux by KingRamsis · · Score: 1

    earth calling Lumpy...earth calling Lumpy

    it's a troll come back home :-)

  41. more a legal than technical issue Re:If you don't by Anonymous Coward · · Score: 0

    Furthermore, SCO is barred by the terms of the GNU General Public License from making copyright or patent-infringement claims on any technology shipped in conjunction with the Linux kernel that SCO/Caldera itself has been selling for the last eight years.

    And wouldn't Microsoft like having the legality of the GPL being questioned, lengthily, in court.

    They may not expect to win, but as a way to hurt enterprise sales, rendering the entire licensing structure legally ambiguous for a year or two would certainly be worthwhile.

    The GPL has never been tested in court, after all, and that's already something of a concern about it for enterprise level customers. Making that a huge dominant issue and giving those legislators who go 'ack! communism!' a kick at it makes it a PR war, and a PR war is where having deeper pockets is really useful.

  42. SCO - Too bad they ruined the name by zoid.com · · Score: 3, Interesting

    This lawsuit is what SCO will be known for. It's really too bad because before Caldera got ahold of SCO it was one of the true Unix hack shacks.

    1. Re:SCO - Too bad they ruined the name by valisk · · Score: 1
      I couldn't agree more, in fact to see just how shoddy they have made SCO look almost brings me to tears, I still remember looking forward to recieving the regular Skunkware disks and playing with the new tools they contained, its one of the main reasons I insist in calling this company Caldera, despite the pretense Sco is dead.
      What we have now is a rerun of Invasion of the Bodysnatchers in corporate form.

      --

      Economic Left/Right: -0.62
      Social Libertarian/Authoritarian: -3.69
    2. Re:SCO - Too bad they ruined the name by drinkypoo · · Score: 1

      SCO stopped being useful long before Caldera. Basically ever since Linux kernel 1.1. The only interesting IP they've had since Xenix was Unixware which they didn't even write. For that matter, they didn't write Xenix, either. SCO Unix has long been known for being slow and incompatible.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  43. Re:Confused = Where is MINIX ? by Anonymous Coward · · Score: 0

    Go ahead ... mod me down, but I was there, when Gilmore was over at Evans Hall (Cal, Berk) fixing AT&T Un*x bugs and a participant on the MINIX list when Linus posted his announcement...

    Yeah, I was the original postmaster at {sun.pacbell,uunet,pyramid, amdahl}!hoptoad and also have a copy of the letter Gilmore received from AT&T stating none of their code was in the GNU code...

    Of course, John didn't get into Linux until he realized it could be used as a front end iron box, years later.

    So.... what about MINIX and this letter gnu@ ?

  44. Most important by selfsealingstembolt · · Score: 3, Interesting

    The best part is at the end of the document:
    A judgment in favor of SCO could do serious damage to the open-source community. SCO's implication of wider claims could turn Linux into an intellectual-property minefield, with potential users and allies perpetually wary of being mugged by previously unasserted IP claims, and ever-more-outlandish theories of entitlement being propounded by parties with only the most tenuous relationship to anyone who ever wrote actual program code. On behalf of the community that wrote most of today's Unix code, and whose claims to have done so were tacitly recognized by the impairment of AT&T's rights under the 1993 settlement, we protest that to allow this outcome would be a very grave injustice. We wrote our Unix and Linux code as a gift and an expression of art, to be enjoyed by our peers and used by others for all licit purposes both non-profit and for-profit. We did not write it to have it appropriated by men so dishonorable that after making profit from our gift for eight years they could turn around and insult our competence.

    And here's the really important message:
    Damage to the open-source community would matter, because we are both today's principal source of innovation in software and the guardians and maintainers of the open Internet. Our autonomy is everyone's bulwark against government and corporate control of the digital media that are increasingly central in political, commercial, and personal communications. Our creative energy is what perpetually renews and finds ever more exciting uses for computers and networks. The vigor of our culture today will translate into more possibilities for everyone tomorrow.

    I think that is a nice roundup of every geek's feelings towards the tendencies found in politics, business and laws nowadays.

    --
    Keep open minded - but not that open your brain falls out...
  45. Throwing The Book by retendo · · Score: 1

    Wow. Thank you Eric. Thank you for throwing the history book at them.

    Much needed, much deserived.

  46. Confused? by Andre+Breton · · Score: 2, Interesting
    You are confused by that? Bah, that diagram is for sissies. This is much better and way more confuzzling:

    www.levenez.com/unix/

    No, seriously, check it out. Best *nix genealogical tree I know of.

    1. Re:Confused? by gsfprez · · Score: 1

      Hmm... apparently, this diagram seems to be a big fav our best friend...

      Darl McBride, CEO of The SCO group,
      presenting the Unix History in Caldera GeoFORUM Las Vegas. -- august 26, 2002.

      halfway down the page

      http://www.levenez.com/wall/

      apparently, he was blissfully unaware that people were stealing from him the whole time, what a shame!
      (/sarcasm)...

      --
      guns kill people like spoons make Rosie O'Donnell fat.
  47. Confusing line by Stonent1 · · Score: 1

    ...but XENIX was SCO's original Unix, while UnixWare was what it picked up in the Caldera acquisition...

    IIRC SCO was making UnixWare long before Caldera acquired them. So this statement is a bit confusing.

    1. Re:Confusing line by NullProg · · Score: 1

      Even more confusing:


      In the late 1970's Microsoft licensed UNIX source code from AT&T which at the time was not licensing the name UNIX. Therefore Microsoft created the name Xenix. Microsoft did not sell Xenix to end-users but instead licensed the software to software OEMs such as Intel, Tandy, Altos and SCO who then provided a finished version of their own Xenix to the end-users or other customers.

      SCO introduced its first version of Xenix named SCO Xenix System V for the Intel 8086 and 8088 in 1983. Today SCO Xenix is one of the more commonly used and found versions of Xenix.


      Enjoy,

      --
      It's just the normal noises in here.
    2. Re:Confusing line by Quixotic+Raindrop · · Score: 1

      Actually, no, I don't think that's right. XENIX was SCOs original Unix, and Unixware didn't appear until about 1992. Originally, UnixWare was a product of AT&T, I think. It was sold, along with the rest of AT&T's Unix stuff to Novell. SCO acquired it from Novell in 1995.

      --
      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. (Einstein)
    3. Re:Confusing line by ebh · · Score: 1

      [From hazy memory:]

      USL (not AT&T) and Novell created a joint venture called Univel to productize the heretofore OEM-only Unix System V source base into a shrink-wrapped binary (UnixWare) installable on Intel boxes.

      When Novell acquired USL, Univel ceased to exist.

      All this happened because Ray Noorda thought that NetWare, UnixWare and WordPerfect (itself the ultimate buy-high-sell-low deal) would comprise enough of a vertical market to topple Microsoft.

      Sorry Ray, it didn't work, but at least you lost a lot of money and destroyed a lot of jobs.

  48. Sco, Caldera, WTF by Old+Wolf · · Score: 1

    I read in today's paper that the action against IBM is actually being taken by "SCO Group", a completely independent entity to SCO (the Santa Cruz Organization). It said that "SCO Group" used to be Caldera (of Caldera Linux fame), and Caldera bought UnixWare off SCO previously.

    However I haven't seen this distinction mentioned on Slashdot (it seems to be a pretty big one..), can anyone confirm?

    1. Re:Sco, Caldera, WTF by Eunuchswear · · Score: 1
      Yes, this is exactlty right.

      SCO != The SCO Group

      The SCO Group == Caldera

      So when people start muttering "but Microsoft own SCO don't they" (ignoring the fact that Microsoft sold it's 12.3% share in January 2000) they're talking about the wrong SCO.

      --
      Watch this Heartland Institute video
    2. Re:Sco, Caldera, WTF by demon · · Score: 3, Informative

      Yeah, Caldera bought the SCO name, rights to the original AT&T/Bell Labs UNIX codebase, and the UNIXWare and OpenServer products from SCO a few years back. What was SCO took on the name Tarantella - the name of the DOS/Windows to Unix crossover product that the former SCO also sold. Caldera later renamed itself to 'The SCO Group', and has been selling Linux, UNIXWare and OpenServer product lines - until just recently.

      --

      Sam: "That was needlessly cryptic."
      Max: "I'd be peeing my pants if I wore any!"
  49. Stolen code found by Anonymous Coward · · Score: 1, Funny
    After weeks of investigation, I have found several occurances of stolen code in Linux kernel. Here is one example:

    in AIX:
    if (a == NULL)
    {
    b = 1;
    }
    and in Linux:
    if (x == NULL)
    {
    y = 1;
    }
    The names of the variables were changed, but that didn't fool my eagle's eye.
    1. Re:Stolen code found by Anonymous Coward · · Score: 0

      You missed a few things:

      #include <stdio.h>

      and a function common to almost the entire codebase that's common to both SCO and Linux:

      int main()

  50. SCO used the wrong group by linuxislandsucks · · Score: 2, Funny

    maybe they should have started with OSI so they could get their facts right!

    --
    Don't Tread on OpenSource
  51. Agent Smith is really Morpheus by Anonymous Coward · · Score: 0

    And Trinity is really Neo's sister! (gack!)

  52. Unix history by Anonymous Coward · · Score: 0

    You that havent reed it, do read it.. not for the SCO clames, but for the Unix history..

  53. It takes time. by mfh · · Score: 5, Insightful

    If IBM had the legal grounds to base a countersuit on one (or more... probably more) of their numerous patents, it would take a very, very long time to prepare these things in an airtight way, not like what SCO has done with their haphazard and amateurish nonsense.

    One thing's for certain; no matter what hapens, IBM will make sure their rebuttals and countersuits are extremely well supported and factually correct, probably with the help of many, many highly paid expert witnesses.

    I'm expecting them to try to prove a point in court, to legitimize their new business model, and to open up future revenue streams for cooperation (they need to clear EVERYONE of this nonsense, or else an entire industry [the one they created by embracing Linux] might disappear).

    It would do better for their bottom line in the long run to prove their business model is sound, and to legally fuck their competition (i.e., SCO) than just outright buying SCO; it would then look like they are covering something up.

    --
    The dangers of knowledge trigger emotional distress in human beings.
    1. Re:It takes time. by dillon_rinker · · Score: 1

      PRECISELY. Their goal in this fight should be to destroy SCO and its leadershop. They win so overwhelmingly that the executives of of SCO are open to shareholder lawsuits. Executives considering legal action against Linux should fear the loss of both their corporate profits and their personal fortunes. In short, there should be a massive, disproportional, and overwhelming response. Cry havoc, and let slip the dogs of law!

    2. Re:It takes time. by curious.corn · · Score: 1

      Funny, when I was a newb people explained me IBM used to be a big & bad dinosaur. Now the bazaar is hugging round the cathedral's walls, sheltering under it's aisles. Looks good for now... but be cautious, the prelate's benevolent eye could turn to Inquisition.

      --
      Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
  54. Great paper by little_blaine · · Score: 5, Interesting

    This paper is a gem. It provides a good history of unix and unix-like OSs, and in my mind it establishes that SCO has no claim to the UNIX trademark. SCO willfully misrepresents itself as a much bigger player in the enterprise market than it actually is, for the purpose of claiming bigger damages. My favorite quote:

    Examination of SCO's 10Ks reveals that, even were we to assume that every dime of their revenue came from the enterprise market, their 2002 share could not have exceeded 3.1% [5] This is at the level of statistical noise.

    1. Re:Great paper by Eunuchswear · · Score: 1
      and in my mind it establishes that SCO has no claim to the UNIX trademark.
      You need ESR to tell you this? Novell gave the UNIX trademark the the Open Group when it sold the source code to SCO.

      What ESR forgets is that all the UNIX based enterprise systems (except those clever buggers at SUN) were licensed from Caldera (as the successor to SCO, as the successor to Novell, as the sucessor to AT&T), so even though Caldera didn't sell many enterprise systems they got a few pennies from everything sold. It's the value of those licenses they're afraid of losing.

      It may not be more than 3.1% of the market, but it's the only money they have. Just you try prying a grain of rice from the hands of a starving man.

      --
      Watch this Heartland Institute video
    2. Re:Great paper by Quixotic+Raindrop · · Score: 1

      Novell gave the UNIX trademark the the Open Group when it sold the source code to SCO.

      Actually, the Open Group (then X/Open) received the trademark in 1993. SCO bought the AT&T source from Novell in 1995.

      There have been several posts from people who are upset with what they say is revisionist history from ESR. However, in at least one place on SCO's History page, they revise history to be the first commercial disributor of a web browser (IXI Mosaic). I have a dated invoice from Netscape Corporation for Navigator Gold which predates this offering. Revisionist, indeed.

      --
      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. (Einstein)
  55. Microsoft Stand by KoolDude · · Score: 1


    Scene One. Linus is watching 'Matrix Reloaded' in his room. Santa the ant is slowly moving towards Linus. Billy happens to be spyin on Linus.

    [Billy]: Dude, where you goin ?

    [Santa]: To bite Linus.

    [Billy]: Well, eat this grain, and make sure you bite hard

    --
    getSexySig(); /* returns sexy signature */
  56. Theorists all of them by el_frostie · · Score: 1
    "He has been since 1997 one of the leading theorists and (both in his individual capacity and as the president of OSI) one of the principal spokespersons/ambassadors for the open-source community."
    Ha! I knew it. All those open-source-folks are just a bunch of theorists.
    --
    One good reason why computers can do more work than people is that they never have to stop and answer the phone.
  57. Petition by thoolihan · · Score: 1
    --
    http://unmoldable.com W:"No one of consequence" I:"I must know" W:"Get used to disappointment"
    1. Re:Petition by dbreeze · · Score: 1

      2300+ in the first 12 hours...not too bad! (I'm 2295!)
      Somebody mod the parent up and get this thing some views!

      --
      When the king heard the words of the Book of the Law he tore his robes.2Kings22:11
  58. Mainframes don't run AIX by Epeeist · · Score: 2, Interesting

    Not any more they don't. They run Linux under VM.

    However, you used to be able to get AIX for S/390. It was hugely expensive and didn't really catch on.

  59. Not true... by Anonymous Coward · · Score: 1

    BSD is protected by res judicata. In other words, this has already been litigated when Novell sued Berkeley and they won.

  60. IBM will not buy SCO. You're right. by Anonymous Coward · · Score: 1, Interesting

    Last night I watched on one of the cable news channels, Larry Ellison and Scott McNealy sitting side by side discussing the newest "partnership" between Oracle and Sun Microsystems. In effect they are about to all-but-legally merge the two companies into one. I predict that they will ultimately actually do the formal merger soon. They *have* to, in order to survive against MS in the future. Ellison can buy SCO with his pocket change, and I predict he will. This is the dark horse that hardly anyone has yet mentioned here on Slashdot. Look for IBM to blow the chance at "owning" Unix, because of their attittude of conservative "not caving in to demands of terrorrists", and no doubt SCO is terrorizing the *nix world right now, but Ellison is enuff of a cowboy to pull off such a gamble.

  61. Re:more a legal than technical issue Re:If you don by earthforce_1 · · Score: 2, Interesting

    >The GPL has never been tested in court, after all, and that's already
    > something of a concern about it for enterprise level customers.

    Then maybe it is finally time for the GPL to have its day in court and do or die. And this looks like an excellent test case.

    --
    My rights don't need management.
  62. Teeth by johnos · · Score: 1

    "for use by enterprise customers, it(Linux) must be re-designed ...This ...is not...possible ...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."
    Too bad one can't be held in contempt of court for blatant and aggravated stupidity. This reminds me of the Nazi dentist in the Kurt Vonnegut novel who proved Jesus was Aryan and not Jewish through careful examination of His teeth in medieval paintings.

  63. Way to go for stupid choice of quote by Anonymous Coward · · Score: 5, Interesting

    "SCO has never owned the UNIX trademark. IBM neither requested nor required SCO's permission to call their AIX offering a Unix. That decision lies not with the accidental owner of the historical Bell Labs source code, but with the Open Group."

    Well, this is quite true, but it's a trivial offhand swipe at SCO that has nothing to do with the court case. SCO are claiming breach of contract and copyright infringement, not trademark infringement.

    The OSI position paper is actually pretty good, and almost any sentence picked at random would probably have been more relevant than that one.

    How about:

    SCO alleges (Paragraph 57): "When SCO acquired the UNIX assets from Novell in 1995, it acquired rights in and to all (1) underlying, original UNIX software code developed by AT&T Bell Laboratories."

    SCO neglects to mention that those rights had been substantially impaired before its acquisition of the ancestral Bell Labs source code. [...] ten years ago at a time when Linux was in its infancy, the courts already found the contributions of other parties to what is now UnixWare to be so great, and Novell's proprietary entitlement in the code so small, that Novell's lawyers had to settle for a minor, face-saving gesture from the University of California or walk away with nothing at all.

    Or:

    SCO's claim to own the scalability techniques certainly cannot be supported from the feature list of its own SCO OpenServer, a genetic Unix. The latest version advertises SMP up to only 4 processors (a level which SCO's complaint dismisses as inadequate), no LVM, no NUMA, and no hot-swapping. That is, SCO is alleging that IBM misappropriated from SCO technologies which do not appear in SCO's own product.

    1. Re:Way to go for stupid choice of quote by Anonymous Coward · · Score: 0

      SCO's claim to own the scalability techniques certainly cannot be supported from the feature list of its own SCO OpenServer

      OpenServer is a legacy product. The lawsuit is about UNIXWare. So this quote really just amounts to baseless FUD.

    2. Re:Way to go for stupid choice of quote by Anonymous Coward · · Score: 0

      I'll just take it that you're one of those dumb 'home experts' with no experience in the real corporate world.

  64. Interesting reading by BennyTheBall · · Score: 5, Interesting
    In case you haven't come across it yet...This article by Bruce Perens makes a good reading.
    The title kind'a get you thinking... "The Fear War on Linux". It seems pretty clear that the only one who might benefit from this is Microsoft. Really fitting for their strategy of FUDing Linux out of existence. Is this just a convenient turn of events for the Redmond guys, or a truly Machiavellian charade orchestrated by them since day one?

    Btw, could someone explain these clearly out-of-context quotes?

    1. Re:Interesting reading by Anonymous Coward · · Score: 0

      "t seems pretty clear that the only one who might benefit from this is Microsof"

      I would have thought that Sun's recent push on X86 Solaris would be a bigger beneficiary.

      Intel's price point and virtual servers are the drivers behind Linux adoption. The GPL is almost irrelevent.

  65. Re:As an attorney... by Anonymous Coward · · Score: 0

    Well what do you know, I am also a lawyer, and I think Slashdot should append a long legal disclaimer after each post just in case anyone got offended by the post. Othervise the poster doesn't have a legal leg to stand on.

  66. except for those little state lawsuits by SuperBanana · · Score: 1
    Their line...go with the smart, non-litigated choice...Windows XP

    Which would be a lie, since they're still getting sued by at least two states, MA being one of them...I think VA is the other state?

    1. Re:except for those little state lawsuits by BJZQ8 · · Score: 1

      Do you think anything will come of these lawsuits, other than the previous slaps on the wrist that MS has gotten?

  67. Re:As an attorney... by Anonymous Coward · · Score: 0
    I used to be a lawyer, until I included IANAL in a post here on Slashdot, thinking it meant "if anyone needs a lawyer."

    They disbarred me for that. Alas.

  68. ESR is just as bad, if not worse by swordgeek · · Score: 3, Insightful

    This is getting tiresome.

    SCO has made a big gamble here, they're incurring the wrath of much of the Unix community (and ALL of the Linux community), and they might end up destroying what's left of their IP and credibility.

    BUT...they're putting their money where their mouth is. They're taking this to court, and winning or losing based on a court ruling.

    Eric Raymond, on the other hand, is providing a 'rebuttal' to their case which is at LEAST as revisionist and self serving as SCO's, but he's not risking anything. Instead he's sitting back, making smarmy comments, feeling superior, and further convincing the Linux community that Open Source is a holy and sacred beast, which must take over the world.

    In other words, his evangelism is just as galling as SCO's corporatism, but without the clout behind it.

    It's time for ESR and all the rest (Theo de Radt, creator/manager of a fabulous OS and general asshole, Linux coders who don't believe in documentation, etc. etc.) to get off of their evangelical horses and start working for the best results, rather than a vision or mission.

    --

    "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    1. Re:ESR is just as bad, if not worse by mofochickamo · · Score: 2, Interesting
      Eric Raymond, on the other hand, is providing a 'rebuttal' to their case which is at LEAST as revisionist and self serving as SCO's, but he's not risking anything. Instead he's sitting back, making smarmy comments, feeling superior, and further convincing the Linux community that Open Source is a holy and sacred beast, which must take over the world. In other words, his evangelism is just as galling as SCO's corporatism, but without the clout behind it.

      Hi swordgeek,

      I read the first half of the article and skimmed the second half. I saw points taken from SCO's complaint and Raymond discrediting them. He is obviously biased toward free software but that doesn't take anything away from the points he makes.

      You said that Raymond is not risking anything by writing this rebuttal, and I agree with you. However, he is not the one who started this fight. He would not have written this article was it not for SCO filing the lawsuit.

      Finally, if you respond to this post will you explain to me why you think that Raymond's rebuttal doesn't have clout?

      Ciao.

      --
      Honk if you're horny.
    2. Re:ESR is just as bad, if not worse by Anonymous Coward · · Score: 0

      1) Raymond is fairly obviously trying to sell his services to IBM as a trial consultant. (See planted "ESR is great, IBM should hire him" press release at The Inquirer and elsewhere.)

      So to he is a little more than a disinterested party or "open source advocate".

      2) ESR has clout, that's a fact. People will be repeating some of the rife inaccuracies in this paper for years to come.

      Now, someone should explain to the rest of us exactly *why* he has any clout. From here, his writings seem deeply flawed and self-serving, and he doesn't have the "code cred" that other open source types have.

    3. Re:ESR is just as bad, if not worse by swordgeek · · Score: 1

      Two points.

      Several of ESR's points are...specious. I can't access the article right now so I can't dig into them point-by-point, but his interpretation of the facts is rather skewed in places.

      Secondly, you state: " he is not the one who started this fight." Seeing as how this was a "fight" between SCO and IBM, he's certainly the only person who inserted himself into it. After all, the lawsuit wasn't against him.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    4. Re:ESR is just as bad, if not worse by Archie+Steel · · Score: 1

      However, as I understand it, IBM is looking into getting him as an expert witness in the case. As someone who has been around UNIX and free/open source software for a long while, it's only natural that he should take a strong stance on this. As it stands, his rebuttal seems to be rock-solid. I have yet to read a convincing counter-rebuttal...

      --

      Reminder: find a new sig
    5. Re:ESR is just as bad, if not worse by shades66 · · Score: 1

      If SCO think that they have the ultimate WEB platform running on their UNIX servers then why do they run their web page under linux!... For those who can't reach their mouse button to click this here is what it says...

      The site www.sco.com is running Apache/1.3.14 (Unix) mod_ssl/2.7.1 OpenSSL/0.9.6 PHP/4.0.3pl1 on Linux.

      --
      ---- There are 10 types of people in the world. Those that understand binary and those that don't
  69. Re:As an attorney... by Anonymous Coward · · Score: 0

    It was probably for the best. You'll at least make it through the first part of the revolution alive, although the second part is going to be a wildcard for anyone.

  70. We have to defend our turf NOW !!! by Delifisek · · Score: 0

    I think this is most successful F.U.D attack against GNU/Linux. We have to defend our turf. Fight back, force SCO to show us copied code. And fix and finish these F.U.D attack at ASAP. Otherwise it will more destructive and MindCrarft test report or any biased journalists or M$ management PR works.

    --
    [My english is better than most other people's Turkish, so please point out mistakes politely. Thank you.]
  71. Something was "added to" Linux they say by mnmn · · Score: 4, Insightful


    The SCO spokesman said something was added to Linux by vendors that was proprietary code. That sounds like the kernel is out of the picture, in which case, we cant say their aim is on "Linux" no matter what the intention. So it could be something like YaST or even some fancy scripting. How hard can it be to replace something thats not the kernel in a distro? And this wouldnt affect the other distros either.

    Theyre really kicking up dust in the face of Linux and not clarifying why. Everyone has been blindly mounting defence for Linux without even knowing what code came from UNIX by IBM at all. By the time they 'reveal' their little blame, all this wall of defence would have strengthened the case for Linux being really free.. and we needed a phreak losing case like this to give a reminder to the community not to use tainted code anywhere in the distros at all. No other Operating System grew up with so much licensing issues in mind; and Linux is bulletproof now. It is precisely this reason why Linux took the lead over BSD.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
  72. SCO's Motivation by ljfrench · · Score: 1

    After reading Eric's paper, it seems to me the smoke and mirrors SCO is putting up could only come from one of two motives:

    A) Create an image that SCO owns the rights to all of Unix/Linux, hoping they'll make a bundle by either licensing those rights or getting bought by an outside party (like M$)

    B) Disrupt the Linux community in the hopes that some outside interested party will help fund their initiative, so the interested third party can sell more of their own operating system (M$?)

    Kudos to Eric and OSI for creating this position statement. It should be a help to IBM, and if not, at least it calms the fears of those enterprises running Linux.

    1. Re:SCO's Motivation by Russ+Nelson · · Score: 1

      Thanks!
      -russ

      --
      Don't piss off The Angry Economist
  73. Why Microsoft REALLY licensed SCO's Unix by cschmidt · · Score: 1

    This article in Australian IT (props go to Google News!) suggests that the real reason SCO is suing (and sending out nasty letters to Linux vendors and customers) is to slow the adoption of Linux in the enterprise. From the article:

    Any IT manager whose team runs Linux could find a fast-talking lawyer at their door - hardly an event to enhance a career.

    Until the dust settles, you'd be a mug to take on Linux while writs and threats are flying around the globe.

    Perhaps that is one of the key objectives of this saga.

    Microsoft, by licensing SCO's Unix offering, lend legitimacy to their lawsuit and in so doing make IT managers think twice about deploying a Linux solution.

    --

    Who am I to blow against the wind? -- Paul Simon
  74. Good troll. by jotaeleemeese · · Score: 1

    Congrats.

    --
    IANAL but write like a drunk one.
    1. Re:Good troll. by Anonymous Coward · · Score: 0

      Thank you! I was being serious, though. :-)

  75. What if... by Anonymous Coward · · Score: 0
    Can anyone tell me what would happen if M$ bought the SCO IP?

    Would they be able to, or would the monopoly commission stop this? Can they stop an IP sale, or just a company buyout sale?

    Why would microsoft license the IP? For me there are 2 possible reasons...

    a) Cover their arses from already using the IP (which means at least THEY know what code SCO is complaining about (consipiracy smells like shit here), or

    b) To finance SCO, they don't care about the actual code...

    I don't believe that SCO should be bought out by IBM, unless they want the IP. If they wanted the IP, they would want it for making money, hence that they do not want to buy SCO means, to me, that they don't want/need the IP.

    Now, M$ is another story...

  76. "one of your own" by Anonymous Coward · · Score: 0

    GNU/Linux is rotten to the core. Some might even say dying.

    Caldera, the Linux company now called SCO suing IBM over IBM's work with GNU/Linux. Previously, Calderia's CEO called the GPL, a core idea of GNU/Linux poison.
    TurboLinux, SuSE, VA Linux all lost millions of investor dollars chasing GNU/Linux.

    Something IS wrong when a company that files for a 57 million dollar IPO to be a Linux company files a lawsuit over the very same techology 3 years later.

    1. Re:"one of your own" by Anonymous Coward · · Score: 0

      we do not care about your companies or your money. ours is the future.

  77. MISTAKE ! by Anonymous Coward · · Score: 0
    The line;

    'Bell Labs Unix


    Bell Labs sold several variants of this system over a period of years. The initial development line ended with Version 7. The business-oriented line ended with System V release 4 in 1998. The original genetic Unix. A trademark Unix, and proprietary.'

    That should be 1988.

    1. Re:MISTAKE ! by Anonymous Coward · · Score: 0

      Another one: 'AIX and Solaris are not shown on this chart. Both derive from System V.' AIX does show in the chart.

  78. defenders of the open internet by efflux · · Score: 1
    I can't help but read the following line from the position paper personally:

    Damage to the open-source community would matter, because we are both today's principal source of innovation in software and the guardians and maintainers of the open Internet.

    I wonder if the next generation of hackers will be able to do the same. I don't mean this as an attack against the *ability* of the up-and-coming...but I don't know if the neophites will be able to stand against a market if that market is openly hostile towards them. Will I (or others entering the field) ever have a chance at becoming "an old hand" that has been critical to the development of the market? Will we ever have the chance to be so initimately involved that we can protect "the open internet"? Or will these gods and legends eventually pass on, leaving the kindom to a weakened progeny--weakened because they did have the experience of building what they defend--who are left to the mercy of corporate marauders?

    I am both inspired and disheartened, and am left to consider my place in computer science more than ever.

    --
    Do I contradict myself? Very well, then I contradict myself, I am large, I contain multitudes. -- Walt Whitman
  79. ESR, as always, is full of shit by delmoi · · Score: 2, Insightful

    SCO's complaint cannot be understood without reference to a seismic shift now occurring in the software industry. The root of the shift lies in the approximate doubling of hardware capacity every eighteen months which has been the trend since the mid-1970s. This means that the typical complexity of software designed to fully utilize state-of-the-art hardware also doubles every eighteen months, escalating the difficulties of software engineering to previously unimagined levels.

    This is so much bullshit, you don't need to write twice as much code to do twice as much work. If anything, it makes programming easier because you can use a lot more pre-made code in libraries without worrying about performance. I think it's hilarious that he goes on and on about his own philosophy and theories and states them as pure facts while also talking about the specifics of the SCO case. It weakens his whole argument, really.

    and look at this:
    Examination of SCO's 10Ks reveals that, even were we to assume that every dime of their revenue came from the enterprise market, their 2002 share could not have exceeded 3.1% [5] This is at the level of statistical noise.

    Statistical noise? Yeah, if you were taking a survey with a standard sample size (~1200 samples), but not if you're looking at all the data (such as comparing revenue). ESR is simply showing is poor education here.

    --

    ReadThe ReflectionEngine, a cyberpunk style n
    1. Re:ESR, as always, is full of shit by that+_evil+_gleek · · Score: 1

      It's a qualified statement. He's not talking about any old software, but "software designed to fully utilize state-of-the-art hardware". Meaning using the hardware to 100% of its capabilities.... This ties in with enterprise computing later...
      Seriously, look at any new release of a software product, it will probably claim to now support a new hardware tech. A 486 was better than a 386, but the percent to which it was depended on whether you recompiled the software to reap all the benefits. Ditto with 486 to 586...ditto with everything really... (Of course I can only recompile the software to take advantage, because someone else did that work in the compiler to make it that easy.) Thats just processors, now include any and all harddrives, graphics cards, 3d accelerators, modems, networks adapters, etc, support all their feautures and get 100% of the performance they provide from all of them, and get it right without bugs or security holes.... Perhaps, he was too succint.

      Anyway, typically new hardware means some improvement to old software, but the /qouted/ improvement when running with software the supports the new tech.

      Also, he's talking about Unix, which is OS which is what provides the OSI to the libraries in the first place. I think maybe you missed it because you were grinding that "use some library" axe that app developers like to grind....

  80. Fight The FUD by belove · · Score: 2, Interesting

    One thing that might help would be to contact your local paper. I've just written to the editor of the business section for mine, offering him a few helpful links and my help if he wants it.

    Help spread anti-FUD.

  81. I bought an Old English dictionary. YOU OWE ME $$! by crovira · · Score: 1

    That's about the level of the argument here.

    I hope that the court DOESN'T just throw this out of court but fines SCO into oblivion as a warning to other IP vultures (and saves IBM the time and expense of counter-suing.)

    --
    MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
  82. Wow by Anonymous Coward · · Score: 0

    I'm impressed. This paper uses the word "meretricious"!

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

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

    Disclaimer: I work for VERITAS Software Corporation.

    1. Re:Major Nitpick by Anonymous Coward · · Score: 0

      Somewhere I heard that Veritas is a spinoff of AT&T, and the original filesystem work was done there. Wrong?

    2. Re:Major Nitpick by mikeee · · Score: 1

      Yes, wrong. Veritas started as a vendor of fault-tolerant UNIX boxen, and eventually converted to a software-only strategy when it became clear that building hardware was not a value-add.

  84. Skewed Logic by nanojath · · Score: 1
    Garbage. I do not have the historical knowledge or experience with software development to know whether your claim that this paper is at LEAST as revisionist and self serving as SCO's, but I don't need it to know that your assertion that SCO suing is equivalent to putting their money where their mouth is is specious.


    Your statement that SCO risks destroying what's left of their IP and credibility tacitly recognizes that the value of their assets was diminished prior to this lawsuit - which makes the gamble you admire them so much for seem a lot less daring. The actions of SCO are being widely seen as a last-ditch effort to sell out a failing business model. Sounds a lot more like putting your mouth where your money isn't.


    If SCO's claims are substantially false then this lawsuit is about significantly more than them taking a gamble and winning or losing. It is about business participants in the open source software community abusing the court systems out of self-interest. Actions of this nature are a significant threat to the viability of open source development, and that is a considerable burden to add when you consider that businesses with a vested interest in maintaining a monopolistic interest in proprietary software development (not to name any names) invest significantly in spreading disinformation about open source, including in lobbying efforts to sway the decisions of our legislators.


    Eric Raymond and his co-authors, meanwhile, are expressing an opinion and making it public. You are not obligated to read or believe it. It does not put a burden on the court system or require any business to divert money that could be spent on creating value in the economy on defending against litigation.


    Every community has its zealots. Clearly you have philosophical differences with Eric Raymond. So, if you want to make a point, demonstrate specific points in this paper and show using verifiable evidence that they are false or misleading. Contribute to the dialog. Otherwise you're just being contrary.


    One last thing - your final comment seems to imply that it is poissible for any endeavor to acheive the best results, without containing a component of vision or mission. I think this is false, and it is particularly false in the world of cooperative, distributed efforts.

    --

    It Is the Nature of Information to Transgress Artificial Boundaries

    1. Re:Skewed Logic by mark_lybarger · · Score: 1

      come on now. the OP presents some valid arguments and you twist it and the OP into a neo-nazi?

      first off, the claim of destroying what's left of SCO's ip was purely speculation. it may have been a percieved diminished value by the OP, but certainly SCO still feels they can squeeze something out of whatever they hold.

      next: "you admire them so much for "... the OP never uses the word admire and I don't get that the OP admires SCO's or their actions. i merely come away from reading the OP feeling that the OP feels that SCO has shown more balls than ESR regarding these IP issues.

      regarding that soon to be famous last comment. i gather that the OP merely feels that OS projects could stand to put aside a little theoretical BS regarding IP property and what the current definition of FREE is today. and get to work fixing and building the systems they preach about.

      i neither agree nor disagree with the OP, i just think the OP presented some valid points and you countered with some extensive assumptions about the post.

    2. Re:Skewed Logic by swordgeek · · Score: 1

      I love seeing people who disagree with me coherently and intelligently. :-)

      "If SCO's claims are substantially false then this lawsuit is about significantly more than them taking a gamble and winning or losing. It is about business participants in the open source software community abusing the court systems out of self-interest. Actions of this nature are a significant threat to the viability of open source development, and that is a considerable burden to add when you consider that businesses with a vested interest in maintaining a monopolistic interest in proprietary software development (not to name any names) invest significantly in spreading disinformation about open source, including in lobbying efforts to sway the decisions of our legislators."

      I disagree with this.

      The 'who owns Unix' question has been hanging around for ages--MUCH too long--and it's time to put an end to it. The SCO lawsuit is likely to clearly define what is SCO's property, what isn't theirs, and what the open source community can or cannot legally use. This is, in my opinion, a Good Thing.

      Furthermore, if SCO's claims are substantially or entirely false, the court has the right to hit them with punitive measures, which would also tend to further open up the Unix source code for public development. This would hurt SCO far too much for them to recover easily, if at all.

      Ultimately you just don't take on a company like IBM in court unless you see a fair chance of winning, and you don't count on a fair chance of winning unless you have some legal high-ground to stand on. If SCO knew that they were full of shit from the get-go, they would have attacked small companies who couldn't afford to go to court--not IBM. (Divine Inc. is a perfect example of this.)

      "Eric Raymond and his co-authors, meanwhile, are expressing an opinion and making it public."

      If this was all they were doing, it would be fine. However Eric is actually stating his opinion in a way that implies it to be fact, and is doing so as an informal ambassador of the open source community. It's quite difficult for him to speak exclusively as an interested individual, and he makes no attempt here to do so.

      "One last thing - your final comment seems to imply that it is poissible for any endeavor to acheive the best results, without containing a component of vision or mission. I think this is false, and it is particularly false in the world of cooperative, distributed efforts."

      Hmm. This isn't quite the context I intended the statement in. Likely I wasn't being clear.

      What I meant is that an exclusive vision/mission which limits the approaches to a problem is damaging. If the problem is "how do I implement 'X'?" and the vision is "all solutions and tools used must abide by our particular license!" then you've just limited (a) the tools you can use, and (b) the ways you can solve the problem.

      Put another way, Open Source is a philosophical vision, but not always a practial one. Mistaking it for a development scheme is a mistake. (The same can be said for proprietary code--sometimes it's the best solution, but not always.) The take home message is use the best tool for the job.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  85. delmoi, also, apparently is full of shit by Quixotic+Raindrop · · Score: 3, Interesting

    This is so much bullshit, you don't need to write twice as much code to do twice as much work.

    It was not said that you need to code twice as much; rather, that complexity doubles. This is demonstrably true.

    Statistical noise? Yeah, if you were taking a survey with a standard sample size (~1200 samples) Actually, 3.1% is > 2 standard deviations from the mean regardless of sample size. It's noise, plain and simple.

    --
    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. (Einstein)
  86. WoW is WoW backwards - but theres still IP by jefu · · Score: 1, Funny
    IP is PI backwards.

    So we know (for a change) how the IP story ends :
    ...95141.3
    But now I'm confused about how that story starts. Any clues?

    1. Re:WoW is WoW backwards - but theres still IP by mark_lybarger · · Score: 1

      unfortunately there is no beginning. or perhaps it was just rebooted 5 or 6 times? who knows. just waiting for nov.

    2. Re:WoW is WoW backwards - but theres still IP by fredrik70 · · Score: 1

      We're working on it. Don't hold your breath though! ;-)

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    3. Re:WoW is WoW backwards - but theres still IP by blinkylights · · Score: 1

      Huh.

      I think you may have just proved that Al Gore does not exist.

  87. Issue isnt the Unix trademark.. by nurb432 · · Score: 1

    The issue SCO is suing for ( unless i totally mised the boat here ) is patent rights over code components, NOT the trademarked name 'unix'...

    In that case i agree.. the name does belong to the opengroup.. and has for a long time..

    But the code? ... i dont belive they had rights to that.

    --
    ---- Booth was a patriot ----
    1. Re:Issue isnt the Unix trademark.. by clarkc3 · · Score: 1
      But the code? ... i dont belive they had rights to that

      aquired the rights to it from Novell in 1995

    2. Re:Issue isnt the Unix trademark.. by monkeypuzzle · · Score: 1

      they == OSI?

    3. Re:Issue isnt the Unix trademark.. by Anonymous Coward · · Score: 0

      Yeah, but legal matters are often very much about correct terminology usage. If a judge doesn't understand what "Unix" is and who owns what and where it came from he could very well be taken in by SCO's dog and pony show.

      That said, the OSI statement could stand to have some of the flag waving cut out. It also had some dodging and glossing that should have been re-written to plainly illustrate areas where SCO might actually have a case. Judges deal with weasel-wording all day and can be quick to toss anything they think is jerking them around -- particularly when it's not something they are obligated to read or acknowledge.

  88. SCO - Microsoft Connection by voideng · · Score: 1

    There seems to be a lack of acknowlegement about SCO and Microsoft being in bed for the last 20 years or so. http://www.computerhope.com/unix/xenix.htm

  89. Linux will not be affected by this by master_p · · Score: 1

    IANAL, but I can't see how Linux is going to be affected. If the current code contains SCO proprietary stuff, then the Linux hackers should remove it and provide their own implementation. It's IBM that's gonna suffer.

  90. sale of property an "accident"? by tim_maroney · · Score: 1

    SCO has never owned the UNIX trademark. IBM neither requested nor required SCO's permission to call their AIX offering a Unix. That decision lies not with the accidental owner of the historical Bell Labs source code, but with the Open Group.... There is a body of code and associated intellectual property (IP), originating in Bell Labs, which SCO purchased from Novell in 1995.

    So, which is it, Eric? Does SCO own the Unix intellectual property as an "accident," or did they buy it?

    This contradiction is understandable: he is saying that no one can truly own intellectual property, and that selling IP is null and void on a moral and ethical level. The fact that SCO owns the Unix source as a result of sale is simply a historical "accident."

    There's some truth to that on the level of abstract justice. Coca-Cola could have bought Unix as easily as SCO did. Nerither of them wrote it in the first place, and neither of them has an abstract moral claim to it. Similarly. it's arbitrary that, say, Paul McCartney is currently the owner of the Buddy Holly catalog.

    But that is the nature of property -- that it can be bought and sold, with reference primarily to the financial transaction, and with only limited concern about whether the new owner is in some moral sense the rightful owner. The reason we allow intellectual property in this society is so that people will be incented to create more of it, since IP becomes a thing of value the creator can then sell to someone who did not create it.

    We've decided as a society that the incentive to create that is involved in limited monopoly outweighs the potential social benefits of unlimited access to all IP. Dismissing the transactions that placed Unix in the hands of SCO is dismissing the nature of property, and instead treating Unix as an ideal which is rightly the property of everyone. However, if Bell Labs couldn't have sold Unix, they most likely never would have developed it in the first place.

    As if to underscore the point that he is protesting the fact that anyone owns Unix, that it was developed as property and sold as property, Raymond goes on to indulge in irrelevant bragging about the ease of obtaining the supposedly confidential sources:

    The contents of the historical Bell Labs codebase is well known; through most of its history, AT&T/USL/Novell tacitly ignored source license violations for non-commercial purposes, and many senior Unix programmers still possess bootleg copies of that source code. (The authors of this document could lay hands on one without difficulty.)

    This I think is near the heart of the free Unix controversy. The Unix community was accustomed for years to living outside the law. Bell Labs charged an unreasonable amount for source code access, but Unix and its client applications were written in such a way that one really needed source code to use it effectively, so bootlegging source became the regular practice. This led to a habit of disregard for intellectual property, and even a feeling that this disregard was somehow virtuous. And of course, people who feel this way would hardly coinsider it a problem to pilfer Unix sources to help create Linux. Unfortunately this subculture of software piracy is incompatible with the right of the owners to control their property.

    This unresolved conflict is now coming to a head. I think any reasonable person can see which side the courts are likely to come down on. My hope is that IBM will settle by buying Unix into the public domain or otherwise freeing the source, but if that's not what happens, then SCO may very well succeed in enforcing its property rights, "accidental" as they may be.

    1. Re:sale of property an "accident"? by iapetus · · Score: 1

      From WordNet:

      accidental
      adj 1: associated by chance and not an integral part; "poetry is something to which words are the accidental, not by any means the essential form"- Frederick W. Robertson; "they had to decide whether his misconduct was adventitious or the result of a flaw in his character"
      [syn: adventitious]
      --
      ++ Say to Elrond "Hello.".
      Elrond says "No.". Elrond gives you some lunch.
    2. Re:sale of property an "accident"? by tim_maroney · · Score: 1

      Exactly, and ownership is integral to property. Calling SCO's ownership of Unix source an accident is like disparaging my ownership of my car as accicental. It's no accicdent -- the car was made to be sold, I bought it, and I have all property rights pertaining to it because of that sale.

    3. Re:sale of property an "accident"? by iapetus · · Score: 2, Informative

      But you're still missing the point. He's not debating that SCO own the Bell Labs source: that's a record of historical fact. As the document makes quite clear, the Open Group owns the Unix trademark. So whether or not SCO own the Bell Labs makes no difference: IBM need the permission of the Open Group, not SCO, to call AIX a Unix. SCO's ownership of the source (not the trademark) is entirely accidental to this.

      In the same way, I'm not denying that you own your car. However, in any discussion of whether I own my car, your ownership of yours is accidental.

      Nobody is saying that anything is 'an accident'. You're still working to another definition of the word 'accidental'.

      --
      ++ Say to Elrond "Hello.".
      Elrond says "No.". Elrond gives you some lunch.
    4. Re:sale of property an "accident"? by ehetzner · · Score: 1

      Wow, you just turned one out-of-context quotation into eight paragraphs of bullshit. Perhaps you a student, of, oh, say, rhetoric?

      What Raymond has said here has absolutely nothing to do with what you're talking about. Nothing at all. Go read the article before you post again.

      (In case you don't want to read the article: he is discussing the difference between ownership of the UNIX trademark & ownership of Bell Labs code base. Now, I don't think this was the best quotation possible from the article, but still.)

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

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

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

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

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

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

      frob.

      --
      //TODO: Think of witty sig statement
    6. Re:sale of property an "accident"? by ESR · · Score: 1

      Don't put words in my mouth. I do not claim that
      nobody can own intellectual property, either in this paper or elsewhere. You think there is a contradiction only because, as others have pointed out, you don't understand what "accidental" means in a legal context.

      I have taken the excellent suggestion of substituting the word "adventitious".

      --
      >>esr>>
    7. Re:sale of property an "accident"? by tim_maroney · · Score: 1

      The naming issue is not what the lawsuit is about. The lawsuit is about the pilfering of source code.

      I'm using the definition of "accidental" that was intended, so far as I know, which is to say, "incidental." I am disagreeing with that and observing that legal ownership is anything but incidental, in a society that has decided that intellectual property can be bought and sold. It is key.

    8. Re:sale of property an "accident"? by tim_maroney · · Score: 1

      "Adventitious" is just as much an attempt to downplay the significance of SCO's ownership of the Unix source code as its synonym "accidental" was.

      How about substituting the word "legal" instead?

    9. Re:sale of property an "accident"? by i+am+lose+cannon!! · · Score: 1

      Your sig is trippy. It's like your intials, but, WHOAH, they are encapsulated by the arrows.
      WHOA MAN.
      Is this a reference to the object oriented paradigm? Enquiring minds want to know.

  91. Re:My favorite quote... (summed up nicely) by jez_f · · Score: 1
    SCO is alleging that IBM misappropriated from SCO technologies which do not appear in SCO's own product.
    Can't say it much more clearly than that.
  92. Re:As an attorney... by siskbc · · Score: 2, Interesting
    I'm done some pretty extensive legal research on this case, and SCO has a damn strong case.

    I'll assume two things here: 1) You're not a troll, and 2) you've read the OSI paper that was the article. Both are probably wrong, but hey.

    So if you have some serious research, I'm sure we'd love to see it. Particularly if some of it invalidates claims in the OSI paper, which are pretty strong.

    --

    -Looking for a job as a materials chemist or multivariat

  93. Some corrections about the histroy of x86 UNIX by pcause · · Score: 3, Informative

    UNIX systems that are built under licenses that SCO inherited are the dominant UNIX variants. These include Solaris and AIX and HP-UX. All have licenses from Bell Labs/AT&T that protected AT&T's intellectual property, which SCO now owns.

    SCO and Intel UNIX: OSI has it wrong and so does SCO. SCO did port Xenix to the 8086 and 286. Intel/AT&T paid to have Interactve Systems port UNIX 5.2.2 to the 286 and 5.3 to the 386. SCO used the Interactive port for the basis of the later products. Interactive built a packaged UNIX based on V.3 which was eventually bought by Sun which used this as the base of Solaris for Intel.

    IBM hired Locus Computing to port UNIX to the PS/2. They used a V.2.2 variant and did not use the same code base that was used for the RISC AIX, which was developed by Interactive for IBM.

    The OSF ported the MACH kernel and UNIX layer but still used a variety of the Bell commands. I think the kernel was Bell license free, but I can not remember the exact terms. I know you needed an AT&T 5.2 level license, but I think this was because OSF still used the commands, libs, etc from Bell.

    In a way, SCO is correct, in that the Intel ports of the various UNIX'es all derive from some version of Bell Labs UNIX which the vendors had access to via an AT&T license.

    1. Re:Some corrections about the histroy of x86 UNIX by Quixotic+Raindrop · · Score: 1

      Except Minix, which was derived from Unix V 7, the source to which was freely given up by SCO a number of years ago.

      Since by every account I have ever come across, Linux was Linus' attempt to make a Minix clone, there can't be any residual IP claim by SCO for Linux.

      --
      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. (Einstein)
  94. These guys have a patent on everything! by theLOUDroom · · Score: 1

    It would be pretty funny if their included some of their patents like this:
    US Patent #5,965,809, "Method of Bra Size Determination by Direct Measurement of the Breast
    Maybe just to point out the silliness of the whole case.

    --
    Life is too short to proofread.
  95. A question to ponder... by mark-t · · Score: 1

    If SCO thought Linux was so sucky before IBM got involved with it, why did SCO start creating distros in the first place?

  96. Here's a point you can verify. ESR's a liar. by Anonymous Coward · · Score: 0

    Where's-my-next-grandstand-ESR says, "Picking a fight with IBM isn't smart. Picking a fight with me isn't smart either. Picking a fight with both of us is mind-bogglingly stupid, especially when the facts ain't on your side."

    Speaking of mind-bogglingly stupid, the public record begs a moment in the spotlight.

    In 1998 Eric Raymond was generally fond of telling us all how "open source" was "his term", namely a USP&TO service/certification mark which he owned and that he was going to sue anyone in general (and me in particular) who used it without his approval. That was about the time that he declared that Linux, published under the GPL, conformed to his newborn "open source" license, and therefore was not so much "free software" published as it was under the GPL, but was "open source" because, well, it conformed to the nascent "open source initiative" license, even though Linux was first published eight years before Raymond decided that "open source" was a better term, for purposes of marketing free software, than the term "free software" was. Well, Linux had been described since its genesis in 1990 as free software but Raymond decided that Linux was better described as open source and contrived his open source license to fit the occasion. Historians refer to such slight of hand, on a nice day, as revisionist.

    In fact, there had been no USP&TO acceptance of the term "open source", but only an application, from February of '98, for the term as a certification mark. That was Raymond's first lie, that it had been accepted as a "service mark". And the applicant was not Raymond, but rather a corporation, Software in the Public Interest. That was his second lie.
    http://tess2.uspto.gov/bin/showfield?f=doc&s tate=9 v08f1.4.25

    Go here and read what the SPI corporation had to say about Raymond and his antics of misrepresentation at the time. They were not happy with what he was trying to do.
    http://www.spi-inc.org/news/1998/19981124

    Forward to 2003. Same Eric Raymond, different year, same misrepresentation. Visit the Open Source Inititative web site and note that it displays what it calls the OSI Certification mark, and that this logo has a TM in it, which is an clear assertion that it the OSI Certification mark is a US registered trademark. Take a look...
    http://opensource.org/docs/certification_ mark.php

    Hmmm. Now, go back to the USP&TO web site and note that, again, there is NO trademark, as Raymond & his OSI web site assert, but only an abandoned application.
    http://tess2.uspto.gov/bin/showfield ?f=doc&state=9 v08f1.5.1

    Better that such typical and often-occuring misrepresentations of the legal status of these terms by Raymond & his OSI are exposed now rather than in a courtroom where Raymond, along with IBM and its legal defense would be blown sky high (as in obliterated) by Ray Noorda's lawyers. It would be a damn shame if the judge were so put off by a demonstration of Raymond's hard-earned style of hyperbole and self aggrandizement that the judge were to decide that IBM itself had no real defense except Raymond's self-serving version of history and that IBM actually was in the wrong here.

    If the IBM defense is in the right on this one but if it introduces a self-proclaimed "UNIX historian" who prefers his own "facts" which are shown to be misrepresentations of easily documentable facts, then IBM itself and any truth of its defense will tragically be subverted by Raymond's time-worn antics. IBM wants to win this one but the last thing it wants to do is to put someone on the stand who regularly shows himself to be hell bent on exposing himself as someone who prefers his own, self-aggrandizing, cooked "facts" to the ones that any 9-year-old can document with an internet browser.

  97. Yes, we certainly do use AIX. by Nick+Driver · · Score: 3, Interesting

    Once again postings like this prove that Slashdot is full of CS graduates and home "experts" who wouldn't know true corporate computing environments if they slapped them in the face. Of course people use AIX.

    Yes, we certainly do use AIX, and it is a fine, reliable, stable and high-performance *nix.

    telnet (CWX1)

    CWX1 (AIX 4.2.1) Unauthorized use/access is prohibited.
    login: root
    root's Password:
    Last unsuccessful login: Wed May 14 13:25:58 2003 on /dev/pts/0 from netmgt1
    Last login: Thu May 15 09:28:00 2003 on /dev/pts/0 from netmgt3

    Determining terminal type, please wait...
    Terminal recognized as vt220 (DEC VT220)
    TERM=vt220

    / >#uname -a
    AIX cwx1 2 4 00054848A100
    / >#uptime
    10:41AM up 337 days, 12:13, 4 users, load average: 0.19, 0.22, 0.54
    / >#

    Yes, it's an older, outdated version of AIX, but does its job and runs too reliably to risk dorking with upgrading it. Besides, it's on a private internal network only (hence being able to telnet in as root), and runs an older version of Oracle that's quite happy on this platform. And furthermore, it's long since paid for itself over and over again.

    1. Re:Yes, we certainly do use AIX. by mark_lybarger · · Score: 1

      And furthermore, it's long since paid for itself over and over again.

      how exactly does an OS pay for itself? i've got to get me one of these AIX os's...

    2. Re:Yes, we certainly do use AIX. by Nick+Driver · · Score: 2, Informative

      how exactly does an OS pay for itself? i've got to get me one of these AIX os's...

      This system as a whole, including the Oracle database and the apps which use that database, are parts of a revenue-generating organization. That organization could not operate as successfully without that system, and before it was purchased 7 years ago, our operation was done solely by manual accounting procedures. The financial benefits (expense reduction plus additional revenue) realized above and over the old manual process during that 7 year period are at least twice what that the system cost to purchase and maintain over that amount of time... so the system has made our operation more efficient and profitable.

    3. Re:Yes, we certainly do use AIX. by Anonymous Coward · · Score: 0

      I see a couple of issues here...

      1) You're allowing Telnet connections - sending username/passwords (and everything else) in the clear
      2) You're able to login as root directly. Also not good practice (especially if you're using an insecure protocol). Someone running a port sniffer has only to grab this one password and they own the box.

      Now, I realize you say its on an internal network only which somewhat mitigates risk but how secure is that network, really?

    4. Re:Yes, we certainly do use AIX. by infinite9 · · Score: 1

      Yes, we certainly do use AIX, and it is a fine, reliable, stable and high-performance *nix.


      Hey smarty-pants, try this one:

      #include"stdio.h"

      int main() {

      int x,y,z;

      x=1;

      y=0;

      z=x/y;

      printf("z=%d\n",z);

      }

      Care to guess what you get when you run it? HP and Sun give you Floating Point Exception and dump the core. Which is correct. AIX gives you... 15. I guess not all zeros are in fact zero. Technically, IBM is probably right since dividing by zero is undefined. But you'd think they would at least make a minor attempt to make the developer's life easier. I haven't tried this in about two years, but I bet it still works.

      --
      Disconnect your television. Do your own research. Draw your own conclusions. They're probably lying. Don't be a sheep.
  98. How about being a bit more specific by maynard · · Score: 1
    Yes that is true, and my argument still stands; this is a legal grey area where their IP may or may not now fall under the GPL even though they unknowingly distributed it. If SCO were to claim that they did not agree to the GPL in full then that is a seperate action that Linus and the other copyright holders must undertake against SCO for infringment.
    Since prior to the acquisition of SCO by Caldera, SCO never contributed to the Linux kernel or released any code under the GPL (that I am aware of), why not limit the discussion thusly:

    - Any code or file released by Caldera and accepted by Linus into the kernel tree with the copyright notice "Copyright Caldera Corporation, All rights reserved. This file is released under the General Public License..."

    Is deemed released on purpose, retains its license under the GPL, and cannot be used ex-post-facto for tort under copyright or breach of contract law.

    Do you agree with that statement?

    --Maynard
    1. Re:How about being a bit more specific by Anonymous Coward · · Score: 0

      Do you agree with that statement?

      Yes, absolutly. That is a clear intent to distribute the code contained within the file under the terms of the GPL.

      But that is nothing to do with the claims by SCO that IBM appropriated code from Project Monterray into Linux. SCO claim that the code came from IBM, not from Caldera, and that SCO never licenced the code to IBM for this purpose.

      In fact I am now confused. Are you asserting that because Caldera released code under the terms of the GPL that SCO now has no claim? I'm sure you're not, or at least I hope you're not. Because that would be a silly argument.

  99. Let's get our facts straight by Anonymous Coward · · Score: 1, Interesting
    The odd jump between UnixWare 2 qnd UnixWare 7 reflects the fact that it was an SCO product designed to merge OpenServer 5 with UnixWare 2 (5 + 2 = 7) after SCO bought the AT&T codebase.

    And Bill Gates is the devil because...

    Nice try, but guess what? Unixware and OpenServer are still two separate products.

    For the most part, though, this seems to have some good points. I'd love to see the reaction from SCO. It's farily obvious from SCO's original presentation (from which this document quotes) was not fully reviewed by enough mind power backed by technical experience. For example,

    Virtually none of these software developers and hobbyists had access to enterprise-scale equipment and testing facilities for Linux development. - SCO

    Not true at all, including the hardware IBM, Compaq, etc., made available, not to mention the equipment Caldera generously made available themselves to developers. Oops. Too bad they got rid of the folks who could have reminded them of this...

  100. Arrgh... by nebaz · · Score: 1

    Let me get this straight. SCO is suing IBM about AIX and OSI is involved. The GPL should be ok though. Too many TLA's. I'm so confused.

    --
    Rhymes that keep their secrets will unfold behind the clouds.There upon the rainbow is the answer to a neverending story
  101. OSI is ESR by Anonymous Coward · · Score: 0

    this is just another note from Eric S. Raymond. I don't think one individual filing multiple briefs and writing letters "on behalf" of multiple groups does anything to help linux's case. I'm not trying to cast aspersions on him personally, but his role has primarily been as an evangelist and hobbiest. His writing is entertaining and often makes good points, but isn't particularly professional (sounding) and right now, the courts are seeing a small group of software pirates and music bucaneers in league with elements of the rogue mega-corporation, IBM attempting to squash the clean cut, small town Mormon business that invented computing as we know it.

  102. Re:A question to ponder... by The+Analog+Kid · · Score: 1

    Probably as a vector to put Unix code into Linux, and someone might see these modifications, think that they are good and contribute them to the kernel or where ever it is found in. Then wait a long time, people wouldn't realize that the code came from Caldera. Then when they became SCO, it would put blame on IBM for the code and say they put it in.

  103. Parent isn't a troll. by Anonymous Coward · · Score: 0

    He's pointing out a gross error the grandparent made.

    1. Re:Parent isn't a troll. by Anonymous Coward · · Score: 0

      What? He forgot to wear Depends?

  104. Perhaps it's a typo by petecarlson · · Score: 1

    I scaned the parents in the thread and didn't see this mentioned. If it was, mod this down.
    About 3/4th of the way down, I got a little confused by this statement: "It is a matter of record [23] that IBM's approach to LVM was rejected by Linus Torvalds in favor of a different approach. Accordingly, even if we were to stipulate that IBM has access to SCO's JFS[emp. mine] technology, any attempted misappropriation came to naught!"

    I think he ment to say SCO's LVM. Has he filed this brief yet and if not can someone contact him to have this corrected?

  105. Re:My experiences with the Troll by Anonymous Coward · · Score: 0
    Too many buzzwords + not enough intelligence + several made-up "facts" = one big fat troll

    I started to refute this, but then I deleted all my text. I'm not gonna waste more bandwidth on a troll, the likes of which should be in the next Harry Potter movie.

  106. Ask Slashdot: Why Does Eric S. Raymond Suck? by Anonymous Coward · · Score: 0

    (1) Reference to self in third person

    The principal author of this position paper (Raymond) has been a Unix developer since 1982, is a technical specialist in systems programming technologies related to those at issue,

    (2) Delusions of grandeur

    and is a historian whose writings on the open-source community and Unix ([TNHD], [CATB], [TAOUP]) are widely considered authoritative both within the community and outside it. He has been since 1997 one of the leading theorists and (both in his individual capacity and as the president of OSI) one of the principal spokespersons/ambassadors for the open-source community

    (3) Endless citing of own pretentious bullshit

    [TNHD] The New Hacker's Dictionary. Third Edition. Eric S. Raymond. Copyright © 1996. ISBN 0-262-68092-0. MIT Press. 547pp.. HTML at the Jargon File Resource Page. .

    [CATB] The Cathedral and the Bazaar. Second Edition. Eric S. Raymond. Copyright © 1999. ISBN 0-596-00131-2. O'Reilly & Associates. 240pp.. How and why the Linux development model works. HTML here .

    [TAOUP] The Art of Unix Programming. Second Edition. Eric S. Raymond. Copyright © 2003. ISBN 0-13-142901-9. Addison-Wesley. 240pp. Work in progress, to be published August 2003. HTML of the draft is here .

    1. Re:Ask Slashdot: Why Does Eric S. Raymond Suck? by RevSmiley · · Score: 2, Insightful

      Hr may or may not suck but at least he puts his name on comments.

      --
      As you can see I don't care about my karma.
    2. Re:Ask Slashdot: Why Does Eric S. Raymond Suck? by Anonymous Coward · · Score: 0

      Yeah, OK "RevSmiley".

  107. Perhaps stolen IP was how NOT to ... by Anonymous Coward · · Score: 0

    Someone I know was once sued because, having seen how one product didn't work well, they took a completely different approach that worked much better. The stolen IP was the knowledge of how NOT to do something!

    So, perhaps SCO's case is that IBM discovered that the SCO's code and development model were completely useless and then improperly switched to backing Linux. At least the total inadequacy of SCO's codebase is something that would be much, much harder to refute.

  108. hypothetical totally irrelevant by maynard · · Score: 2, Insightful
    My argument is that people are currently running around and claiming that this is pretty much a cut and dried case, and SCO has lost already. "There is no SCO code in Linux. Even if there was, SCO distributed Linux, so the code in question is under the GPL. QED" is the basic argument. Even ESR is using it now.
    Wow. I just finished reading the entire paper and I didn't read into it anything of the sort. He most certainly did NOT say that because Caldera released Caldera Network Desktop and Caldera OpenLinux that whatever SCO codebase may or may not be in the Linux Kernel is somehow covered under the GPL. You're mixing up the timeline of ownership such that it obfuscates Caldera's direct contributions to the Linux kernel as part of their business plan.

    Let's review some basic UNIX history:

    - early '80s: SCO bought the rights to Unix V. 7 from AT&T and developed XENIX (one of many x86 UNIX derivatives), with Microsoft as a partner.

    - Across the '80s many other developers developed UNIX on Intel, as well as UNIX on other chip platforms such as 68K. This includes Sun, SGI, HP, Sequent, IBM, etc etc etc.

    - The trademark for "UNIX" was sold to X/Open in the early '90s. X/Open then renamed themselves "The Open Group". They still own the trademark.

    - In '91 Linus released the first Linux Kernel to the hacking community. He wrote this on his own and is a derivative of nothing other than his own work.

    - In '93 Novel purchased USL (AT&T)s stake in the UNIX codebase.

    - In '94 Berkeley and AT&T/USL settled an ongoing copyright infringement lawsuit over the rights to those portions of the BSD codebase which contained original AT&T Version 7 code. A few files in BSD were removed, rewritten, and then BSD was rereleased as BSD-4.4Lite. (This had nothing to do with Linux).

    - By '95 Caldera was actively contributing source code to the Linux Kernel, along with dual CPU hardware, to further community development of a product line they were actively engaged in selling. All of this code was released under the GPL with full knowledge and intent of management as part of their business plan.

    - in '95 Novel purchased the rights to the original UNIX codebase from USL

    - By '96, when Kernel 2.0 was released, Linux had basic support for SMP in the kernel.

    - In '98 Novel sold the UNIX codebase to SCO (previously SCO had only a source license from AT&T). SCO, IBM, and others began Project Monterey to unify an single UNIX source tree among many hardware vendors.

    - In '99 - 2000: Kernel 2.2 was released which included many new SMP features. By this time independent of project Monterey Linux developers were coding in beta their own journaled filesystems, Logical Volume support, clustering failover, and very early NUMA support.

    - 2001: SCO split into Tarantella (a web services company) and the original SCO name w/ original AT&T UNIX tree. Along with this was the original SCO Openserver codebase and UNIXWARE. Linux had by that time far surpassed UNIXWARE in SMP scaling, along with most other enterprise features, and all of this had happened before IBM invested in Linux and dumped project Monterey.

    Thus, one sees from the history of Linux development, all relevant "enterprise" features were developed independent of IBM and the project Monterey codetree. The assertion that "SCO released code which accidentally made it into the kernel tree" and "loosers weepers" is completely irrelevant to the facts at hand. None of that happened, thus the hypothetical doesn't matter.

    ESR makes all of this perfectly clear in his position paper.

    Cheers,
    --Maynard
    1. Re:hypothetical totally irrelevant by Anonymous Coward · · Score: 0
      I'm not even talking about Caldera. I couldn't in fact care about Caldera.

      The argument goes thus:

      • IBM copies SCO code into Linux kernel
      • SCO takes Linux kernel and distributed it without knowledge of their own IP which has been copied into the kernel by IBM
      • Because SCO distributed the Linux kernel, any code they have a claim to in the kernel is under the GPL and SCO are out of luck becuase they distributed it themselves

      What the hell does Caldera have to do with it?
    2. Re:hypothetical totally irrelevant by Anonymous Coward · · Score: 0

      I just finished reading the entire paper and I didn't read into it anything of the sort.

      Oh I forgot. ESR has not said this in the position paper but did use this argument in the CNet editorial.

      I still don't know how Caldera got brought into this argument!

  109. Please take a stats course by Anonymous Coward · · Score: 0

    Probably a troll, but I'll bite. Your statements are so far off that it's hard to tear them apart, which is probably what makes it so fun as a troll.

    Why don't I just stick to the most obvious problem:

    * Standard deviation is a function of sample size, making everything you've said completely false.

    1. Re:Please take a stats course by Quixotic+Raindrop · · Score: 1

      Actually, the size of the standard deviation is dependent on sample size. The percentage is not: "[...] a normal distribution will always have approximately 68% of the scores between the scores at +1Sx and -1Sx. This is because, mathematically, 68% of the area under the normal curve falls between +1Sx and -1Sx." (Basic Statistics for the Behavioral Sciences, Heiman, Gary, 1992)

      The first standard deviation accounts for 34% of the scores above (or below) the mean. The second standard deviation accounts for ~48% of the scores above (or below) the mean. This places something that consists of 3.1% within the third standard deviation away from the mean. This is true regardless of what you are measuring or what the sample size is.

      --
      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. (Einstein)
  110. Who benefits? by Anonymous Coward · · Score: 0

    Microsoft, of course. If this FUD prevents a few people from switching to Linux, it would certainly make Microsoft happy. Well worth paying a few license fees. Or even funding a lawsuit by someone like SCO.

    But they wouldn't do anything like that, would they?

  111. Little details do matter... by bovinewasteproduct · · Score: 1

    Come on ESR, you could have atleast made sure that your timeline was correct!

    Even if he messed up the fact that FreeBSD has to different parents depending the version (FreeBSD 1.X is from 386BSD and FreeBSD > 2.0 is from 4.4BSD-Lite Release 2), 4.4BSD-Lite (FreeBSD is not from 4.4BSD, which was AT&T licensed) was release prior to 1993 (I think 90-91). The beginnings of 386BSD and Linux are both at about the same time.

    Little details do matter...:)

    BWP

  112. yeah by Anonymous Coward · · Score: 0

    what he said......

  113. Don't like the GPL? Don't rip-off GPL-ed code. by phliar · · Score: 4, Insightful
    It really is as simple as that. If you don't believe in the goals of the Gnu project, don't incorporate GPL-ed code into yours! No one is forcing you to even use GPL-ed code.

    All this stuff about "irrevocably infect your code without your express wishes" is just FUD. Whining about "programmer took some 'free' code to incorporate into our precious corporate product" is just whining -- no one else is responsible for your clueless employees. "GPL" is not a synonym for "public domain."

    SCO distributing a Linux distribution doesn't necessarily affect the case since they can reasonably claim they didn't look through all the billions and billions of lines of code in the kernel. But I'm not a lawyer, and my unfounded speculations are just that. Don't read this paragraph.

    --
    Unlimited growth == Cancer.
    1. Re:Don't like the GPL? Don't rip-off GPL-ed code. by fredrik70 · · Score: 2, Insightful

      actually, the linux kernel isn't *that* big, believe it's around 3 MLOC nowadays (anyone got an exact figure?). whereas I can appreciate SCO not checking all 3rd party apps that comes with their dist, but rather relying on MD5 checksums, I would imagine it's not an impossible task to check the source for code that shouldn't be there. You would only have to check the total once, and after that you only would have to check the *changes* made to the kernel.

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    2. Re:Don't like the GPL? Don't rip-off GPL-ed code. by phliar · · Score: 1
      actually, the linux kernel isn't *that* big,...

      not checking all 3rd party apps that comes with their dist, but rather relying on MD5 checksums

      Hey! I said don't read that paragraph!

      I don't see how you can use MD5 sums of packages to identify "code that shouldn't be there" -- the whole point of MD5 is that a small change in the file will cause a large change in its signature.

      I think it's reasonable that SCO wasn't checking -- they could claim in good faith they didn't think their trusted partner would behave so heinously. But that's all academic, of course... until we see this "actual evidence of SCO IP in Linux!" it's all bullshit anyway.

      --
      Unlimited growth == Cancer.
    3. Re:Don't like the GPL? Don't rip-off GPL-ed code. by fredrik70 · · Score: 1

      Ah sorry, was a bit unclear. didn't mean you check for dodgy code with MD5, but rather just make sure that all 3rd party stuff got the identical checksum as their respective maker says, just making sure you don't get an dodgy (trojans etc, etc) build. Basically you put your trust in the 3rd party that everything is in order as long as the checksum is ok. This would IMHO mean that if any 3rd party stuff is tainted with code that shouldn't be there then it's *that* 3rd party that's responisble - not the distribution maker itself. SCO said for some time that the tainted code was *not* in the kernel itself - seems like they backed away from that now...
      Anyway, I'm not sure if I can agree with you about not checking the kernel at least, but then again, I might be wrong - never tried to set myself into such a big project as the linux kernel myself, so I assume I'm talking about things slightly out of my league! ;-)

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
  114. Bible re. making money by brlewis · · Score: 1

    The verses you quoted (Luke 18:24 and 1 Timothy 6:10) teach that the love of money makes it difficult for people to prioritize spiritually, not that making money is immoral.

    1. Re:Bible re. making money by Malcontent · · Score: 1

      Why would somebody accumulate more money then they need if they didn't love it.

      Jesus preached that you should live a simple and humble life. He preached that you should spend your life helping others not making yourself richer.

      Budha also preached poverty.

      Mohammed didn't seem to mind wealth as much but he too preached a life of service to others.

      The satanist religion on the other hand advocates the accumulation of wealth (and power) as a moral goal.

      --

      War is necrophilia.

    2. Re:Bible re. making money by brlewis · · Score: 1

      I haven't really studied what the Bible says re. accumulating more wealth than you need. But "making money" doesn't imply accumulating more than you need.

    3. Re:Bible re. making money by Malcontent · · Score: 1

      " But "making money" doesn't imply accumulating more than you need."

      Yes sure if you want to nit pick. Ask anybody how much money they want though and you'll get a number much bigger then what they "need".

      Capitalism encourages greed, gluttonny, pride, lust, sloth and the rest of the seven deadly sins.

      think about it. Usury is a sin, what would capitalism be without lending and interest?

      capitalims is anti-christian and pro satanist. there is no was to get around that fact.

      --

      War is necrophilia.

  115. The Evil Beast Controls all by keepr · · Score: 0, Troll

    SCO is a souless puppet whoose strings are being manipulated by the heartless tyrant known as MicroSoft. They deserve the full fury of the opensource community that will be unleashed upon them in the next few months.

    --
    Slashdot taught me how to use the preview button!
    1. Re:The Evil Beast Controls all by VidarBox · · Score: 1

      Its simply a question of timing. Microsoft knows it can't win SCO's lawsuit against IBM/Linux but it serves as a bigger threat than SCO did as a delay-engine. If it can tie things up in litegation, its succeeded. I find it humorous this happened not long after/before Ellison was quoted as saying Microsoft was on its last leg.

    2. Re:The Evil Beast Controls all by john.penfold · · Score: 1

      I once heard that McDonalds is really a Microsoft sub-concious mind controlling centre. They place what is called 'food poison' into Chicken McNuggets which in turn makes you delude yourself into trusting Microsoft. All paranoid delusions aside, isn't SCO being sued for using unix code segments in their linux flavour...

  116. Read it! by tryfan · · Score: 2, Interesting

    I really hope that a lot of people actually READS the paper. It's excellently clear, and very well written.
    If the case goes to court (which it should) and IBM wins (which it will), then a lot of FUD about Linux and IP actually will be out of the way.

  117. ESR's Errors by llywrch · · Score: 2, Insightful

    > There have been several posts from people who are upset with what they say is revisionist history from ESR.

    There are numerous places in this paper where ESR gets his facts wrong, & not a few typos (e.g. the genealogical chart he provides for UNIX post-v.7 out _does_ show the lineage of AIX). And he can't help but add a section or two about his pet theory about how wonderful Open Source is.

    HOWEVER, there are far less errors in ESR's history of UNIX than in the SCO Group's. The biases in their narrative distort the facts; ESR's bias does not. If the two or three sections where he waxes prophetic about Open Source are removed, the basic facts of the relationship between SCO UNIX, IBM & Linux remain.

    I only hope that people bring these errors to ESR's attention, & that he proves his assertion of the superiority of Open Source by making the nescessary bug fixes. (Or someone else will prove it by forking his white paper, with the necessary improvements. ;-)

    Geoff

    --
    I think I see a trend here. Maybe for them it really would be easier to muzzle the entire internet than to produce p
  118. US va USA by Anonymous Coward · · Score: 0


    From the OSI position paper:

    The required attribution is "UNIX is a registered trademark of The Open Group in the United States and other countries".

    Is it United States or United States of America? Do "required attributions" require correct country names or will any abbreviation do?

  119. Re:As an attorney... by Anonymous Coward · · Score: 1, Informative

    Well fancy that! I ALSO happen to be an attorney and I have done extensive research on this case as well. It looks to me like SCO hasn't a legal leg to stand on since none of the code they claim is in Linux actually existed before 2002. (I've also signed the NDA to see what it is that they are claiming they "have on Linux". That's why I'm posting AC. Seth is a cocksucker.) SCO will be laughed out of court on day one as soon as they make their "revelation".

  120. Re:more a legal than technical issue Re:If you don by LMCBoy · · Score: 1

    The GPL has never been tested in court, after all, and that's already something of a concern about it for enterprise level customers.

    The shrink-wrap EULA has also never been tested in court, IIRC. Does that make MS software "something of a concern" for enterprise level customers?

    Besides, it isn't clear to me what exactly about the GPL must be tested in court to mollify enterprise customers. If they are simply using GPL software, then the GPL doesn't even do anything. For pure users, GPL==freeware. The GPL restrictions come into play only if one chooses to redistribute GPL'd software. If you do not accept the terms of the GPL, then the software reverts to standard copyright law, under which you have no rights to redistribute it. I really don't see how one could invalidate the GPL without necessarily invalidating all software licenses at the same time (IANAL).

    --
    Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
  121. Re:A question to ponder... by Anonymous Coward · · Score: 0

    SCO didn't. Caldera did. Then Caldera bought SCO UnixWare, OpenServer, Services and Support, and a few other odds and ends. Then *new management* came in, took over Caldera and the "Old SCO" and replaced it with what we have now.

    This is not the same company as Caldera; this is not he same company as SCO. It is a new entity with completely different leadership which has entirely different purposes from either previous company. It just happens to have the same name as one of the previous companies.

  122. Ransom by Anonymous Coward · · Score: 0

    I bet some people would be happy to go back to the days of Ransom Love... I dare say the fights over THAT Caldera seem relatively tame compared to what the entirely new leadership at SCO are doing.

  123. Seems to me.. by magnwa · · Score: 1

    It seems to me that this entire position paper will get thrown out as it is talking about SCO OpenServer. SCO's suit contends that the infractions occurred with UnixWare.

    J

  124. Re:My experiences with Linux by raju1kabir · · Score: 2, Interesting
    The main reason that open source software, and Linux in particular, is failing

    It's not failing. It's gaining marketshare. It's winning people contracts in larger and larger organizations for larger and larger installations.

    the newest version of Linux, version 9.0

    There's no such thing.

    I felt that I was up to the job to convert the entire server pool to the Linux technology. I had several years experience programming VB, C#, ASP, and .NET Framework at the kernel level.

    Put another way... I felt that I was up to the job to perform a heart-and-lung transplant. I had several experiences applying band-aids to minor scrapes and recommending chicken soup to people with the sniffles.

    Furthermore, he found out that the 'x' in Linux was a tribute to the former Communist philosopher, Carl Marx, whose name also ends in 'x'.

    You got the wrong memo. It's in honor of Richard Nixon, who also (unlike Karl) has an 'i', an 'n', and an 'x' in the same name.

    Needless to say, I will not be recommending Linux to any of my Fortune 500 clients.

    Ought to be easy, as you clearly don't have any.

    --
    "Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
  125. "Everybody" meant "everybody and AT&T".... by Anonymous Coward · · Score: 0

    "everybody did it so it was okay" wouldn't wash, execpt that AT&T played along -- probably to maximize overall market acceptance and garner "free" programming contibutions from the user community. Good plan for AT&T, or bad, we don't have the boardroom insight of the time to say. But, when the owner of a trade secret doesn't protect it, actively, positively, and without fail, the secret is out and lost forever. That is the law.

  126. You're a liar ... by Anonymous Coward · · Score: 0

    ... as well as an attorney.

    How about citing some of your 'extensive legal research'? I'm not going to believe that it exists until you do.

    SCO has not disclosed their primary evidence in the case. Without access to this evidence, you have no basis to form the opinion that they have a 'damn strong case'.

  127. MS funding SCO. by Anonymous Coward · · Score: 0

    I believe the main reason why MS is "licensing" from SCO is to give it additional funding in the proxy fight against Linux, IBM, etc.

  128. Silly question... by leshert · · Score: 1

    So, what exactly does OSI's ownership of the UNIX trademark mean, if honoring the trademark is more "in the breach than in the fact"? Has OSI failed to enforce its interest in the trademark sufficiently for it to be weakened and unenforceable?

    The reason I'm asking is that, should SCO prevail, could OSI get ugly and demand that SCO stop using OSI's trademark in their marketing materials?

    1. Re:Silly question... by demon · · Score: 1

      OSI doesn't own the UNIX trademark. The Open Group does, and have for some time. They purchased the rights to the UNIX trademark from either USL or Novell (I can't remember which off the top of my head, I think it says in the paper), and have held licensing rights to the name since.

      Could The Open Group revoke SCO's rights to the UNIX trademark? I don't really know - I suppose they could, being the trademark holders. Don't know if The Open Group will care enough about it to make it worth their time to do so though.

      --

      Sam: "That was needlessly cryptic."
      Max: "I'd be peeing my pants if I wore any!"
  129. Leave it to ESR by blair1q · · Score: 0, Troll

    After he became famous by stealing the Jargon File and publishing it for his own benefit, he's moved on to writing fluffy, irrelevant, legally moot junk in an attempt to deprive SCO of any of its legal rights to the intellectual property it owns.

    1. Re:Leave it to ESR by ctid · · Score: 1
      After he became famous by stealing the Jargon File and publishing it for his own benefit, he's moved on to writing fluffy, irrelevant, legally moot junk in an attempt to deprive SCO of any of its legal rights to the intellectual property it owns.


      Seriously, you should try to read the article. You have to at least try to understand the issues, otherwise you're just humiliating yourself.

      --
      Reality is defined by the maddest person in the room
    2. Re:Leave it to ESR by Anonymous Coward · · Score: 0

      How do idiots like you get a posting bonus? Sheer volume of seperate unique /. login id'es?

    3. Re:Leave it to ESR by talks_to_birds · · Score: 1
      shoo, Micro$oft pimp...

      t_t_b

      --
      I'm on PJ's "enemies" list! Are you?
    4. Re:Leave it to ESR by blair1q · · Score: 1

      I did read the article. Twice. I didn't see a legal argument in there. Just a thief, whining that he won't be able to profit from stolen property any more.

    5. Re:Leave it to ESR by blair1q · · Score: 1

      Microsoft pimp?

      Microsoft just paid SCO for a UNIX license so it wouldn't have to worry about being accused of stealing any more.

      Microsoft has lawyers that crap all over the Department of Justice. They wouldn't pay for a license from a two-bit, nearly bankrupt holding company if they didn't think they had to.

      ESR is playing the Jean Valjean part, appealing to emotion to contravene the law. But he's not stealing a loaf of bread to feed his family, he's stealing $millions in IP to keep his business in the black. He's hardly the symbol of pathos Victor Hugo gave us.

  130. Re:As an attorney... by Anonymous Coward · · Score: 0

    "I'm done...."



    Nice grammer, attorney-boy. If you had done even one-half of 1% of the research that you're claiming to have done, then you'd realize that SCO hasn't got a single legal leg to stand on.

  131. Caldera bought SCO... by maynard · · Score: 1

    ...But retained the SCO name for marketing purposes. --M

    1. Re:Caldera bought SCO... by drinkypoo · · Score: 1

      Good to have confirmation. It's pretty much a toss-up whether to use the SCO or the Caldera name; SCO is known for "too little too late" and Caldera is known as the "sue microsoft company" -- which makes Microsoft's support at this time ironic as hell. I guess that was just Ransom, though.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  132. Re:As an attorney... by Anonymous Coward · · Score: 0

    No. It means your IANAL retentive

  133. 'cus it's The American Way! by Anonymous Coward · · Score: 0

    > Everyone derides ESR and RMS because they stick by what they believe in. Even if you don't agree with them, why do you feel that they need to change their stance?

    "Bash unto others", is pretty much the motto of humanity.

    A sense of superiority is the goal for most, and how better to achive power than to "win" by aimless bashing of anything that matters not to you directly. Think of it as "eliminating the competition" in the game of life.

    > "Not everyone has the same beliefs as you do."

    Indeed, and those without "my" beliefs should probably be, in order of preference...

    o Killed.

    o Condemmed by "God", so others might serve my purpose in feeling rightous enough to do the actuall killing/bashing.

    o Bashed until they vanish from my world experience, without a trace.

    o Denied until they are clearly "in their place", like in a box under someone else's bridge.

    It stinks, but that's life in today's world. Get used to it.

  134. A little marketing wouldn't hurt by Angst+Badger · · Score: 1

    While having little legal bearing, it would be nice to have an executive-summary-style comparison of the featuresets of Linux vs. SCO's offerings. Not having worked with SCO's products, I'm not in a position to do this alone (I've administered various Linux distros, Solaris, and AIX), but if some sysadmins with SCO experience would like to put some thought into this, I'll help do the writeup and the suit-friendly presentation. Contact me at eodell@sfront.com if you're interested.

    --
    Proud member of the Weirdo-American community.
  135. Re:As an attorney... by Anonymous Coward · · Score: 1, Funny

    As an attorney interested in legla matters related to the software industry, I am followwing this case closely as well, and my legal opinion is of the contrary. After careful ponderance of the evidence presented so far by both sides, it seems that the judge is leaning heavily in favor of granting all further rights to nVidia. This will leave the OSI in a lurch as it has pending preprocessed propietary patents in proper due to come up with SGI in 2004. This will leave the GNU scrambling to find new sources for OT... SCO had better purchase PanIP, a far more experienced enterprise class litigator, or shut up shop.

  136. Re:My experiences with Linux by RazorJ_2000 · · Score: 0, Troll

    "HAHAHAHHAHA!!!!"



    If you're a consultant, then you're easily the stupidest person that I've ever seen.

    "...NET Framework at the kernel level."



    HAHAHAHAAAAA!!!!
    --
    pi=sigma{n:0-infinity}[(1/16)^n][(4/(8n+1))-(2/(8n +4))-(1/ (8n+5))-(1/(8n+6))]
  137. Sue SCO for slander and libel by Black+Copter+Control · · Score: 4, Interesting
    We might actually have a legal precedent as the first class-action libel suit.

    Reading thru the OSI document, it became clear to me that the SCO suit and surrounding PR are an attempt to do to Linux what the USL/BSD suit did to BSD a decade ago -- that is stall it's adoption in a cloud of legal FUD.

    For those who are not aware, back in the early '90s Unix Systems Lab (the inheritor, at that time, of the bell labs IP in Unix) sued the BSD people over their attempt to split off the BSD code from the Bell Labs IP. At that time, they had realized that the BSD code base had very little code that had actually sourced with AT&T and decided that it was time to excise what was left of the AT&T code and go their own non-proprietary way. USL was indignant at this abandonment of fealty and attempted to sue the BSD group back into compliance.

    As the OSI paper succinctly puts it: "The suit was settled after AT&T's request for an injunction blocking distribution of BSD was denied in terms that made it clear the judge thought BSD likely to win its defense." -- (and after Berkeley's threat to counter sue AT&T over their own violations of the BSD copyright and license).

    Many people, however, credit the current popularity of Linux -- at least in part -- to the legal cloud that the AT&T suit placed over the BSD codebase -- at about the same time that Linus released the early (and relatively primitive) versions of the Linux kernel with the GNU utility codebase.It is believed that a number of people decided that it was easier -- legally speaking -- to throw their lot in with the clearly IP-intact Linux than to risk getting caught by the BSD license debacle.

    As a result, Linux is now the dominant Unix-variant OS OS, and the various BSDs -- which started with a much more stable and mature codebase are now holding a relatively niche market space.

    SCO's suit along with their rather bombastic and (as shown by the OSI document) seriously misleading and unfounded PR claims seem intended to create precisely the same kind of 'chilling environment' around Linux. The fact that Linux is just about to get into a serious head-on fight with Microsoft for control of both the server market and the desktop market may be either coincidental or part of a conspiracy.

    Although SCO's legal filings have a limited immunity to claims of slander and libel, to the extent to which they have repeated those claims in press releases, public statements, and letters, they are not. Those public and semi-public statements appear to be a large part of SCO's 'legal' campaign, and open them to some serious libel claims.

    I honestly believe that it would be appropriate for the Linux community to seriously look at suing SCO over the insulting, degrading and clearly untruthful statements that they've made about us. The intent of those statements is to degrade the image and financial value of the work of the Linux community, and if they're allowed to stand, they may succeed in doing so to a greater degree than they already have.

    --
    OS Software is like love: The best way to make it grow is to give it away.
    1. Re:Sue SCO for slander and libel by 1seconddelay · · Score: 1

      I agree with you but the problem is funding. If IBM really wanted to shake it up they should invite the open source community leaders to the party in utah! Quite simply sco manages to paint all linux users as pirates and thieves. I believe however that we are on the right side of things and that linux will emerge stronger and more free. A libel lawsuit would be cool as @@#% though.

  138. Microsoft blood money should be put in escrow by Anonymous Coward · · Score: 0

    The Money that Microsoft recently gave to SCO should be put into an escrow account so when RedHat, SuSe, and others sue SCO for damages arising out of SCO's frivalous case, they would have something to be compensated with.

  139. WAIT A MINUTE DUDE !(Yes, we certainly do use AIX) by Anonymous Coward · · Score: 1, Funny

    Did you just teleneted in as root??

    Its not only your OS that is outdated :)

  140. the out of context quotes: by Anonymous Coward · · Score: 0

    Richard Stallman

    "Linux is a copy of UNIX. There is very little new stuff in Linux."
    Linux kernel forum

    "I consider the law prohibiting the sharing of copies with your friend the moral equivalent of Jim Crow. It does not deserve respect."
    Richard Stallman, Free as in Freedom, Richard Stallman's Crusade for Free Software: O'Reilly (2002) at p. 72

    "The whole GNU project is really one big hack. It's one big act of subversive playful cleverness..."
    Richard Stallman, Revolution OS (DVD)

    Bruce Perens

    "This is becoming a tradition. I go there and break the law every year in the name of free speech."
    Bruce Perens, explaining his plan to demonstrate how to modify DVD technology to attendees of an Open Source convention.

    "We have to remember that Linux is a follow-on to UNIX. It's not just a UNIX clone. It's actually a UNIX successor."
    Bruce Perens, mpulse magazine, December 2001.

    CONTEXT FOR THE ABOVE:

    Stallman is often full of hyperbole and not to be taken literally when he comments on his competition. You might as well quote Bill Gates on Linux. Humans deride the competition.

    Perens is as American as Washington, Jefferson, and those other long haired radical revolutionaries that believed in FREEDOM enough to disobey tyrannical laws bought by the rich to oppress the majority.

    Is that context enough?

  141. SCO is not DDoS'd by Anonymous Coward · · Score: 0

    I didn't expect to be able to read those misquotes off their site, after hearing that they'd been DDoS'd some days ago.

    But not so, their site isn't lagged at all.

  142. Play the "insult" card too hard? by Anonymous Coward · · Score: 0

    Is it just me or does ESR play the "insult" card too often? It would seem to me to be better stated that "SCO saw benefit to using the contributions of the community and now attacks that same community by which SCO profited."

    Insult doesn't mean much. Insult is not a legal issue. Who contributed and who profited is more meaningful.

    Later,
    LurkerMan

  143. when open became popular... by Anonymous Coward · · Score: 0

    From the OSI paper:
    "The most skilled programmers flocked to the new mode."

    This is pretty questionable. The most skilled programmers were probably well-established, well-paid, and mostly restricted and cautious about contributing to open projects while employed at closed companies.

  144. No recurring fees to SCO/Caldera for UNIX source by Anonymous Coward · · Score: 0

    Not at all. I seem to remember that AT&T sold UNIX System III and V licenses back in the '80s for about $40,000 per license. This included the rights to the source code, modifications, the "UNIX" name, and the right to distriubute a commercial product based upon this tree. None of the commercial UNIX vendors such as Sun, SGI, IBM, HP, et all pay a recurring fee for use of the original UNIX source tree.

  145. There's an issue with that paper. by nenolod · · Score: 1

    Linux was derived from MINIX. That is all.

  146. Could be that SCO believes IBM's Monteray PR speil by Lew+Pitcher · · Score: 2, Interesting

    It appears that SCO's claims about Linux scalability, etc, may have been as a result of some IBM PR in 2000.

    A vunet article from June 2000 quotes Miles Barel, IBM's program director for AIX and Monterey, as saying that scalability, volume and systems management features present in IBM's Unix operating system, AIX, are still missing from Linux.

    Of course, an IBM'er would (at that moment in time) push AIX over the (then) hobby project called Linux. But, it seems that it is this comment that's sparked SCO's much delayed attack.

    --

    "values of beta will give rise to dom!"

  147. OPEN SOURCE BOICOT by Anonymous Coward · · Score: 0

    Apache, Sendmail, Squid, Samba, Cdrtools, OpenOffice, Gnome, Kde, gcc, Mozilla ... This programs are open source and SCO can use it. If SCO hate opensource, why can use it? I think that all the open source programers must put a clausule in his programs to boicot SCO. In the other hand, www.sco.com use Apache+Linux... ( http://uptime.netcraft.com/up/graph/?host=www.sco. com )

  148. No they haven't by RevSmiley · · Score: 1

    "This document, originally proposed as a draft brief of amicus curiae, has been endorsed as an OSI position paper by OSI's Board of Directors. The Board has concluded on advice of counsel that OSI cannot seek amicus status in advance of pleadings. The option to seek amicus status at a future time remains open."

    --
    As you can see I don't care about my karma.
  149. Irony, anyone? by Anonymous Coward · · Score: 0

    What is today *BSD played a large role in eroding the intellectual property that wound up in the hands of SCO (the net2 stuff being just the most obvious and highest-profile). So the jokes about RedHat FreeBSD are funny, but not in the way people seem to think. If SCO thought there was a dime to be squeezed out of *BSD I'd bet they'd be gunning for them too.

    This might be an interesting case, I don't forsee any big winners, but the loser could be the GPL, if things go a certain way it could be open season in terms of enforcing the license or (more likely) citing it to remove contributed code from large projects (like linux) retroactively (that is, invalidating a GPL-ed release of something would virally invalidate all derived versions).

  150. The most interesting point I've found on this by dacarr · · Score: 2, Interesting

    The thing that I'm seeing in this whole affair between SCO's FUD and ESR's OSI writeup is oddly ironic: it won't be a battle between open source developers and Micros~1 that becomes the pivotal point for Linux, it will more likely be this issue that we're all reading about.

    --
    This sig no verb.
  151. Interesting by cshark · · Score: 0

    I see they've added pretty diagrams since last I checked. Nice. This is top quality material.

    --

    This signature has Super Cow Powers

  152. Sales contact number on sco site. by generic · · Score: 1

    The sales number on their website is 1-888-GO-LINUX, shouldn't it be 1-888-KO-LINUX?

    I think they are confused.

    --
    Microsoft aggravates my tourettes syndrome.
  153. I wonder if SCO knows (or cares) how much damage t by tonyl · · Score: 2, Insightful

    Disclaimer: I'm a log time SCO reseller/consultant and although I do more and more Linux, a lot of my business is still SCO. Which probably makes me prejudiced.

    When Microsoft was under assault by the Justice Dept., they whined that any harsh punishment would have drastic effects on our economy. I think this suit has equally undesirable consequences.

    Chances are that this will all blow over with little or nothing changing. Either they'll lose, or they'll win but won't be so greedy as to kill of the golden goose. Let's hope so, anyway.

    But suppose they are as rapacious and unprincipled as Microsoft? Suppose they actually have a case, and actually win, and start demanding outrageous royalties and compensation for previous sales?

    That could destroy Linux. Destroying Linux makes Microsoft stronger and only hastens SCO's own already progressing downward spiral. No doubt it would affect FreeBSD also because of FUD if nothing else. While it might not directly affect Sun and Apple, making Microsoft stronger doesn't help.

    My wife and I talked about this today. Without a strong base of Unix/Linux customers, you can stick a large fork in me. It's been my life for 20 years. I am NOT going to start doing Microsoft crapola now; I'm too old, too tired, and I dislike their stuff too much.

    OK, putting me out of business doesn't kill the economy. But how many others will be similarly displaced and disenfranchised?

    Can anyone guesstimate what the economic consequences of the Worst Case Scenario might be?

    --
    -- Tony Lawrence
  154. Good Logic by nanojath · · Score: 1
    These amplifications clarified your comments a lot for me... This particular case is fascinating to me as a person who is interested in the various Open Source models, but lacks the technical credentials, background and knowledge to speak to the many of the deeper issues. So I appreciate the input of people with more knowledge, but it can be difficult to judge authority.


    Others called me on spinning more into your comments than was fair (guilty) - good rhetorical technique, not always the best way of getting to facts. I think it is very interesting, though, to ponder the vision versus elbow grease factor, if you will. I often look at the world of Open Source development as a sort of model anarchy, still my favorite idealistic model for self-governance. I think there is a need for visionaries and advocates, but what you say is true - there's a fine line between principles and dogma, and the latter usually ends up restricting your options.


    Whether the actions of these two representatives (SCO and Eric Raymond) can really be meaningfully compared, you are making me lean to the belief that ultimately this lawsuit can be a good thing if it clarifies ownership of Unix (after reading that paper I have no idea what that really means).

    --

    It Is the Nature of Information to Transgress Artificial Boundaries

  155. Re:A question to ponder... by shades66 · · Score: 1

    And by looking at this page at SCO this got quote a lot of awards from their distribution of Linux. Can you imagine their awards page from now on... (I am guessing it won't be changing for a while!)...

    I do wonder what any of their larger customers using SCO's linux distribution are thinking right now! If SCO do give up on linux they are going to annoy a lot of their clients...

    Mark.

    PS. Thought this was funny still being on SCO's Partner page...

    IBM offers the industry's most comprehensive lineup of solutions for Linux®. IBM's efforts to advance Linux stretch back to 1998 and signify an unrivaled show of support via technology, skills, services, and corporate focus. With the industry's largest portfolio of hardware, software and services for Linux, IBM support continues to expand, allowing more companies to leverage Linux to grow their e-businesses.

    --
    ---- There are 10 types of people in the world. Those that understand binary and those that don't
  156. Whoops! by jcr · · Score: 2, Informative

    The paper says:

    However, The Open Group's strict construction of the term ÒUnixÓ is more honored in the breach than the observance.

    This is a pretty common misuse of Shakespeare's line from Hamlet. Most people take it to mean that the thing in question is mostly ignored, but what Hamlet meant when he said it was that the tradition in question was a bad one, and that it was more honorable to breach than to observe it.

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  157. How much do you think MS paid for the SCO license? by Ryan+C. · · Score: 1

    $1?
    $0.01?
    -$1,000,000?

    Seriously, I'm sure MS paid nothing or got some kick-back to accept the license. It's a common market strategy (e.g. Rambus) to "sell" licenses for undisclosed terms to major players to make your claim seem stronger. Seems to have worked again, SCO stock is way up on the news.

    -Ryan C.

    --
    -Ryan C.
  158. Is UNIX a Trademark? by PetoskeyGuy · · Score: 2, Insightful

    I was wondering if "UNIX" was still a trademark. In all the days I've been around computers I've heard them described as PC, Mac or unix system. PC has always been Wintel or compatible. Unix systems could mean Irix, Linux, *BSD, Solaris but mainly mean your going to be using "ls" instead of "dir" to do your dirty work. This article mentions a few ways a trademark can be lost and lists some nice examples.

    • if buyers understand that the mark refers only to the type of goods sold, and not to its source, then it makes no difference what efforts the owner used, because the mark has become generic.
    • if consumers use that company's mark to identify a certain product type, because the mark is shorter and easier to pronounce than the product's generic name
    • when a particular brand achieves such a high market share that the brand becomes the category.

    I think that most computer people would agree that unix is pretty generic by now. I don't know if this is directly related to the lawsuit or not. What do you think?

  159. Mistakes in ESR's paper by graham_m · · Score: 1

    I was going to point out some of the mistakes in ESR's paper but I really can't be bothered now. Can someone get the Unix timeline fixed please!

  160. Re:How much do you think MS paid for the SCO licen by shades66 · · Score: 1

    I am guessing that from the announcement on the 19th that the payment was "Active Directory Services" or whatever it is called. See www.sco.com and look at the last few news items!

    --
    ---- There are 10 types of people in the world. Those that understand binary and those that don't
  161. All your Linux are belong to- aw, screw it. by franksbiyatch · · Score: 1
    Here's something to [allegedly] amuse you.


    Sure, not all the facts are right, but that never held back Fox News or The New York Times. Enjoy.


    Taken shamelessly from http://www.ridiculopathy.com/news_detail.php?id=82 6


    LINDON, UTAH- In a webcast on Tuesday, representatives from SCO Group [aka Caldera Systems] expressed sincere thanks to the tireless core of Linux developers who have, for more than a decade, so generously donated their efforts to advance the usefulness of their intellectual property.

    "Guys, we can't say enough how much we really appreciate how much you've done with our patented product," said CEO Darl McBride. "You've really taken our little server OS to the next level. Thanks guys, really. You'll all be getting 'letters of appreciation' very soon."

    Sure enough, a few days later several thousand hard core Linux developers and users opened their snail mail to find official-looking invitations to a party at a California Federal courthouse.

    "8:30am - ?" read the invite. The "?," explained McBride, stands for crazy fun.

    As the current owners of the original Bell Labs Unix code and trademarks, SCO ceased Unix development years ago in favor of a more efficient business model: full-time litigation.

    "When we gave up on it, Linux was just a third-rate toy server with no applications or commercial services. Look at it today: professional grade server software and a quickly maturing desktop environment, a real crown jewel in our IP stable. We really have to take our red hats off to those guys. Get it? Red Hat. Ell Oh Ell."

    Slashdot was all a' buzz on Tuesday with speculation about what specifically SCO would do to thank them. A few hours later, though, a leaked memo resolved the issue. The company plans to say thanks by giving the Linux community an opportunity to pay huge royalties and, in some cases, give up rights to their work.

    "Linux users, our users, are just about the most gracious people on the planet," said McBride. "We can't help but love them."


    On Monday Microsoft decided to license the Unix name and technology from SCO, not because they actually needed it but, as CEO Steve Ballmer put it, "mostly as a corporate high-five for a job well done."

    Linux developers were naturally surprised to hear that portions of the supposedly open [free as in speech, free as in beer] operating system actually belong to someone. As it turns out, when bits of SCO's OpenServer Shared Libraries somehow ended up in the kernel source code, Linux became the property of SCO/Caldera.

    SCO executives say there is no reason to worry, though. "Open" Source software is in no danger.

    Some were confused by the statement, arguing that the quotes around the word "Open" had not always been there. SCO's legal team, however, insists that they have.

    In a related story, McBride recently settled a land dispute with the owner of his former home. After abandoning the place in the early 1990's he reportedly moved back in last month while the current owner was on vacation. Happily for McBride, the two bedroom ranch was now a three bedroom split-level with a pool.

    "I simply love what you've done to the place," McBride said through his attorney. "Now get the hell out."

    Over the next few months, SCO/Caldera plan to collaborate with other organizations like the RIAA and the Girl Scouts to create new and innovative licensing schemes. Look for details on FreshMeat very soon.

    In the meantime, Linux users are lining up to buy back software they helped develop.

    "It kinda sucks that Linux is proprietary now," wrote Slashdot poster AnonymousCoward. "But I'm glad they appreciate all our hard work. They seem like really nice guys." (Score: -1 Insightful)


    Some Linux fans have expressed interest in switching to BSD or another free Unix derivative. Others, however may opt to dump their decade-long dot matrix printer emulation project in favor of more time spent in a place developers like to call "outside" conversing with strange, fleshy avatars known as "people."

  162. That's it! by Anonymous Coward · · Score: 0

    I've always used windoze because frankly, I've been to lazy to learn Linux. But the level of their greed has plain pissed me off. Linux it is.

  163. VERY private network. by Nick+Driver · · Score: 1

    Now, I realize you say its on an internal network only which somewhat mitigates risk but how secure is that network, really?

    Obviously you didn't believe me when I said it's on a private network did you?. There are only six devices on this private network segment -- the server itself and five workstations, it is NOT routeable *anywhere* else, or even connected to any other network device period. You have to be physically present in the computer room, where I am right now, and under my personal supervision to telnet to this AIX box.

  164. Ancient Unix Source by dberger · · Score: 1

    Seems that while SCO has stopped serving the bits, planetmirror still has this stuff laying about:

    The click-through license:

    and the files that live behind it (accessible without accepting the license, no less)

    5th Edition UNIX
    6th Edition UNIX
    7th Edition UNIX
    Mini UNIX
    UNIX System III
    UNIX 32V

  165. Eyes Rolling by Anonymous Coward · · Score: 0

    No one actually admits to being a lawyer. Doesn't matter, no one's advice here should be taken too seriously. You folks must think a lot of yourselves and your precious reputations to always be announcing that you are not lawyers. At least make me laugh and switch to "IAMANAL" or simply "Type A". Dumb asses.

  166. screw them! by sboss · · Score: 1

    pardon this post! it is far from PC (politically correct).

    Screw Them! They are a sinking ship that wants to grab a hold of something solid. They file the lawsuit, become a PITA (pain in the ass) and IBM will buy them to shut them up and make the go away. IBM stick to your guns, and not pay them a dime. Actually counter sue for harassment and legal fees. Even if you dont get the harassment lawsuit (which you should not care about) get your legal fees back. And put those bastards out of business. Screw Them!

    --
    Scott
    janitor
    sdn website family
    email: scott at sboss dot net
  167. Rob Landley is a therorist !? by Anonymous Coward · · Score: 0

    "He has been since 1997 one of the leading
    therorists..."
    ^^^^^^^^^^

    http://www.opensource.org/sco-vs-ibm.html#id2790 29 0

    I knew Unix folks were Hackers,
    but now they convinced me
    they are therorists!

  168. Default aix SIGFPE by Anonymous Coward · · Score: 0

    infinite9:

    On AIX, if you want to receive SIGFPE, then enable it. The call is fp_enable().

    Other options include examining a status flag in the Floating-Point Status and Control registers (FPSCR), using fp_divbyzero().

    See:
    http://www.unet.univie.ac.at/aix/aixprggd/ genprogc /floating-point_except.htm

  169. Just how dumb are you? by Anonymous Coward · · Score: 0

    Anti-ESR zealots are ALMOST as bad as the anti-RMS ones... (but as you demonstrated, the anti-ESR guys are obviously much more stupid)

  170. Mindless ESR bashing ... by Anonymous Coward · · Score: 0

    ... makes you sound like an idiot, so shut the fuck up

  171. ESR trolling.... by Anonymous Coward · · Score: 0

    ...makes you sound like an idiot. Please shut the fuck up.

  172. Re:How much do you think MS paid for the SCO licen by no_code_charlie · · Score: 1

    "According to today's Seattle Post-Intelligencer, some observers say the "deal could impede Linux. .... The agreement ... will put between $10 million and $20 million into the hands of The SCO Group, of Lindon, Utah, said a source close to the deal." http://www.washingtonpost.com/wp-dyn/articles/A145 17-2003May20.html?nav=hptoc_tn

  173. seems? by waspleg · · Score: 1

    we like to start wars for the economic benefit of those in power

    if that is not corruption what is?

  174. What can you do with $30? by Anonymous Coward · · Score: 0

    I found this interesting fact by looking at Caldera's insider trading in the last 2 years.

    On February 21, 2003, 6 Directors of Caldera International (SCOX) purchased between 26,923 and 33,462 shares of Caldera stock each.

    Of course none of them were familiar with this case or with M$ofts pending license.... right?

  175. How about YOU Shut The Fuck Up by Anonymous Coward · · Score: 0

    Yeah, really! How about YOU Shut The Fuck Up instead? The man has a fucking RIGHT to question the message and the messager. What part of that don't you fucking understand? Go back to reading your comic books and popping your zits.

  176. How about YOU Shut The Fuck Up ! by Anonymous Coward · · Score: 0

    Yeah, really! How about YOU Shut The Fuck Up instead? The man has a fucking RIGHT to question the message and the messager. What part of that don't you fucking understand? Go clean your fucking closet why don't you?

  177. The quotes explained by smiff · · Score: 1
    Richard Stallman

    "Linux is a copy of UNIX. There is very little new stuff in Linux." Linux kernel forum

    Stallman didn't say that. He quoted Larry McVoy who said that.

    "I consider the law prohibiting the sharing of copies with your friend the moral equivalent of Jim Crow. It does not deserve respect." Richard Stallman, Free as in Freedom, Richard Stallman's Crusade for Free Software: O'Reilly (2002) at p. 72

    That quote was taken completely out of context. What Stallman actually said was:

    "I'm looking beyond what the existing laws are to what they should be...I'm not trying to draft legislation. I'm thinking about what should the law do? I consider the law prohibiting the sharing of copies with your friend the moral equivalent of Jim Crow. It does not deserve respect."

    In the interest of brevity, even that's not in complete context. Stallman is basically saying if you were to thinking about what the law should be, and someone proposed the current copyright law, the current law would not merit much thought.

    The final Stallman quote,

    "The whole GNU project is really one big hack. It's one big act of subversive playful cleverness..." Richard Stallman, Revolution OS (DVD)

    sounds like meaningless babble. I don't know what the heck that's supposed to mean. Maybe if SCO put it in context it would make more sense.

    Bruce Perens

    "This is becoming a tradition. I go there and break the law every year in the name of free speech." Bruce Perens, explaining his plan to demonstrate how to modify DVD technology to attendees of an Open Source convention.

    In a show of civil disobedience, Bruce was planning to circumvent the region controls on a DVD player. He was planning to get arrested so he could put the DMCA on trial. His employer, Hewlett Packard, was afraid that they could be held liable for his demonstration, so they asked him not to do it. In the end, Perens cancelled the demonstration since it would defeat his whole purpose of HP was sued.

    "We have to remember that Linux is a follow-on to UNIX. It's not just a UNIX clone. It's actually a UNIX successor." Bruce Perens, mpulse magazine, December 2001.

    From the magazine interview:

    What does the open source mean to development of devices within the mobile Internet?

    We have to remember that Linux is a follow-on to UNIX. It's not just a UNIX clone. It's actually a UNIX successor. UNIX was invented by the phone company and it was very streaming-oriented. No one used the word 'streaming' in 1970, but if you look at the way UNIX works, it's all pipes and filters, and that's streaming.

    It's a very good operating system for telecom, and branches out to streaming media and sending video, etcetera, where these things will happen over third generation wireless. Linux fits there very well.

    So Perens was referring to the original AT&T UNIX and its stream-oriented foundation. What SCO fails to mention is that they do not have a claim against Linux based on the original AT&T code base. As Eric Raymond pointed out so well in the position paper, AT&T attempted to enforce their intellectual property rights, but ended up settling out of court by paying the defendant's legal fees.

  178. ESR: Trademark Maven? Bwaaaaa Haaaa Haaaaa by Anonymous Coward · · Score: 0

    Eric Raymond is the LAST person on the planet whom I would want to rely on to explain trademarks to me. He's the idiot who lied about owning the Open Source certification mark (dead-abandoned) and who asserts that Open Source Certified is a trademark (dead-abandoned).

  179. Of Fucking Course by Anonymous Coward · · Score: 0

    Hell, Yes, Raymond puts his name on his bullshit. And that is the point here, not that there's anything wrong with an anonymous comment. If you don't like the rules here at Slashdot go somewhere else. If you can't get used to this feature of Slashdot in all these years you need psycho-therapy.

  180. My grandchild's homework by Anonymous Coward · · Score: 0

    My 8-year-old granddaughter's homework today contains hard to spell words like SEPARATE and teaches that it is incorrect grammar to use an apostrophe and the letter s as the plural form of any word. Now, you were speaking about idiots?

  181. Feel Free to show us all by Anonymous Coward · · Score: 0

    Feel Free to show us all any indication at all why exactly it is that you consider yourself to be a genius....

  182. Re:My experiences with Linux by Anonymous Coward · · Score: 0

    This is one of the most stupid comments I've read
    in slashdot. Seems so faked. But, perhaps -real- stupidity supports MS sales.

  183. ugly second-cousin by PlainBlack · · Score: 1

    Every old UNIX hand knows that SCO has always been the ugly second-cousin of real unix environments like DEC Unix, AIX, HPUX, and Solaris. No real unix administrator would ever *choose* to use SCO if s/he had the choice.

    And I can honestly say that after having administered all of the OS's mentioned above, Linux is vastly more innovative than any of them these days. Sure all of them have thier cool utilities, but feature-for-feature Linux wins hands down.

  184. A nice niche for Apple by antAllan · · Score: 1
    the various BSDs ... are now holding a relatively niche market space.

    That niche including the largest number of installed copies of a genetic-Unix desktop OS than of all other desktop Unix variants combined (including Linux)... ?

    Of course, Mac OS X Server isn't doing quite as well... (yet).

  185. "My stack is bigger than yours" by Andy+Dodd · · Score: 1

    A lot of patents are filed for the simple reason of increasing the patent count of a company for threat/marketing purposes.

    It also depends on who invented it - Some inventors are given special treatment because they're so valuable to the company, even though they might be a bit eccentric.

    Back when my dad was in IP for a major company, some of them would rate patents on a scale of 1 to 5. 1 was "really important, use our best lawyers to draft and file", 4 was essentially "get some wino off the street to draft it up and file it", 5 was "patently stupid".

    Most 5s were thrown away, but said company had a few Nobel Prize winners that had some REALLY crazy ideas patented because Lucent wanted to treat them well, and also so they could say, "Person Y works for us and has filed N patents"

    --
    retrorocket.o not found, launch anyway?
  186. Ransom Love is someone's name? by Anonymous Coward · · Score: 0

    ...wow, I thought Mike Huntz was bad.

  187. Um by delmoi · · Score: 1

    We are not talking about test scores, or any other continuous data, but rather we are trying to determine the composition of the set. There is no reason to assume that it will fall into any kind of normal Gaussian distribution pattern.

    If we determine the makeup by testing every element rather then by taking a sample, there is no margin of error. The only thing ESR could have meant by his 'statistical noise' comment is that SCO's market share was equivalent to zero. But this is clearly false. It also doesn't take price into account.

    --

    ReadThe ReflectionEngine, a cyberpunk style n
  188. So what? by delmoi · · Score: 1

    It was not said that you need to code twice as much; rather, that complexity doubles. This is demonstrably true.

    Well, there are two kinds of complexity. Strictly speaking, we are talking about O(n) running time. In that case O(2n) = O(n) anyway, so if you 'double' the complexity, it stays the same.

    If you're talking about 'conceptual' complexity, like how many conditionals, etc, then that would in fact be related to code length. And like I said, faster computers let you write less code, not more.

    --

    ReadThe ReflectionEngine, a cyberpunk style n
  189. Well, what does he mean exactly? by delmoi · · Score: 1

    Well, I suppose you have a point when it comes to underlying tech, like an OS. Obviously an OS that supports SMP, lots of threading, protected mem, NUMA, transparent clustering, and all sorts of crazy goodness is going to take longer to write then DOS. But at the same time, that's really more of an issue of supporting hardware *features* then it is a result of hardware speed. You could have all of that with a 386 if it supported those things. Now of course, having those features requires transistors, the number of which also goes up with Moore's law. But I don't really think the feature set is doubling every 18 months :P

    He also seems to be claming that the open source model is the only one that works. Microsoft, SUN and other small companies seem to have been able to keep up.

    --

    ReadThe ReflectionEngine, a cyberpunk style n