Slashdot Mirror


SCO Claims Linux Lifted ELF

fymidos writes "SCO has finally spoken. According to this linuxworld article, they claim that linux illegally uses the ELF binary format, the JFS filesystem, the init code and some more 'copyrighted Unix header and interfaces'. Finally SCO makes its move. The JFS part was expected of course, but according to the article, as far as the ELF format is concerned 'the Tool Interface Standard Committee (TISC) came up with a ELF 1.2 standard' and 'granted users a "non-exclusive, worldwide, royalty-free license" to the stuff'. Oh, and of course 'both Novell and the old SCO - as well as Microsoft, IBM and Intel - were on the committee'."

146 of 675 comments (clear)

  1. Truth Elves by mfh · · Score: 5, Funny

    Not sure what SCO has to do with Elf. Wait, nevermind. They've got truth elves, working from dusk till dawn, griding down the logic and confusing the masses with their cute looking elf outfits and fairy dust. My guess is that Santa Claus himself is somehow behind this latest SCO claim. It just seems like the more they open their traps, the lower their stock gets, so I'm all for many more of these kinds of press releases.

    --
    The dangers of knowledge trigger emotional distress in human beings.
    1. Re:Truth Elves by JPriest · · Score: 5, Funny

      SCO: "I see your Elf, and raise you a troll"

      --
      Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
    2. Re:Truth Elves by Camel+Pilot · · Score: 4, Funny

      No doubt I am sure the elf's are from MIT.

    3. Re:Truth Elves by dsbaha · · Score: 5, Funny

      Would that make SCO the "Santa Claus Operation"?

      -ds

    4. Re:Truth Elves by camkind · · Score: 4, Funny

      According to BBspot, yes

    5. Re:Truth Elves by Soruk · · Score: 2, Funny

      Makes sense, really. SCO are really showing off their elfishness.

      --
      -- Soruk
    6. Re:Truth Elves by builderbob_nz · · Score: 5, Funny

      Slight problem, the Elf killed the Troll (well the cave one at least)

      --

      Karma? Hey I just call it as I see it.
    7. Re:Truth Elves by quantaman · · Score: 3, Funny

      Would that make SCO the "Santa Claus Operation"?

      But wait, what about Linus' quote...

      "Ok, I admit it. I was just a front-man for the real fathers of Linux, the Tooth Fairy and Santa Claus."

      So SCO owns Linux after all!!

      --
      I stole this Sig
  2. More school yard fun by erick99 · · Score: 5, Insightful
    SCO, never having a straight-forward and direct claim uses bluster and a childish version of "no it ain't!" to maker their claims. For example, SCO says that TISC ...exceeded its rights... Regarding the GPL that TISC created that SCO doesn't like, SCO calls the GPL "quicksand" and claims it's invalid. I guess they figure it they declare it invalid, then it must be. It still smacks of cowardly playground bullying. There is more than enough sophomoric behavior to go around, though.

    I am not sure what this ends up meaning, legally:

    SCO also claims "substantial similarity" between the Read-Copy-Update (RCU) routine in Linux 2.6.5 and Linux patches and SCO's copyrighted work, specifically SVR4.2 MP.

    Similarity can be a slippery slope and SCO will slide as far down as need be, I suppose. And how about something that "may" be an infringement:

    It also says the journaled file system (JFS) module from later versions of AIX, which SCO believes may derive from the JFS Unix, is in Linux 2.6

    The folks at SCO probably look like adults, they are adult-sized and wear nice clothes. However, they act like elementary school kids arguing over a ball on the playground. Whoever yells loud enough, pushes hard enough, and hold their breath the longest wins.

    Cheers!

    Erick

    --
    http://www.busyweather.com/
    1. Re:More school yard fun by crimethinker · · Score: 3, Interesting
      SCO also claims "substantial similarity" between the Read-Copy-Update (RCU) routine in Linux 2.6.5 and Linux patches and SCO's copyrighted work, specifically SVR4.2 MP.

      Well, knowing what I know about SCO (only what I read here and on groklaw), I'm willing to believe that there is substantial similarity. However, I'd bet dollars to donuts that the code came from Linux (or more properly, IBM, perfectly within its rights) into SCO, and not the other way 'round.

      Their lawyers have fudged so many facts, fumbled so many easy misses, that I wouldn't doubt this for a moment. "Please stay the RHAT case, because it will be decided by the IBM case," and "please dismiss the IBM counter-claim; it will be decided by the RHAT case."

      -paul

      --
      Pistol caliber is like religion: everyone has their favourite, and theirs is the only right choice.
    2. Re:More school yard fun by at_kernel_99 · · Score: 3, Insightful
      Well, knowing what I know about SCO (only what I read here and on groklaw), I'm willing to believe that there is substantial similarity. However, I'd bet dollars to donuts that the code came from Linux (or more properly, IBM, perfectly within its rights) into SCO, and not the other way 'round.

      Your hypothesis is certainly one I wouldn't dismiss immediately, but do you know in what kind of timeframe the SVR4.2 release was made? i.e. Who is the cart and who is the horse, with respect to Linux & SCO.

    3. Re:More school yard fun by AKAImBatman · · Score: 4, Interesting

      These guys make absolutely no sense. They're flailing their arms in the air and saying "You owe us money!" Let's pick apart each claim:

      1. Sontag also says that any entities that ignore SCO's ELF copyrights are infringing."

      Hello? Copyrights are for "copy" protection. Not "patent" protection. If you invent something new and fail to patent it, I can re-implement it all I want, copyright or no.

      2. SCO also claims "substantial similarity" between the Read-Copy-Update (RCU) routine in Linux 2.6.5 and Linux patches and SCO's copyrighted work, specifically SVR4.2 MP.

      Again, do they have a patent? If they don't, then they should STFU.

      3. It thinks that Unix SMP 4.2 System V initialization (init) code was copied into Linux 2.6, that there's "substantial similarity" between the user level synchronization (ULS) routines in Linux and Unix, that its Unix System V IPC code was copied into Linux 2.4.20 and that copyrighted Unix header and interfaces were copied into Linux.

      Oooo... it's similar! Well, that just cinches it, doesn't it. It's not like anyone would ever re-implement a design they liked. I better go take the wheels off my Chevy. It's too similar to a cart and horse.

      4. It also says the journaled file system (JFS) module from later versions of AIX, which SCO believes may derive from the JFS Unix, is in Linux 2.6. - MOG

      Just to reiterate, SCO is not reading their own contracts. What IBM develops is IBMs. Plain and simple.

      These guys ought to be tried and convicted for barratry, regardless of whether their legal counsel is this stupid or not.

    4. Re:More school yard fun by EddieBurkett · · Score: 2, Interesting
      However, I'd bet dollars to donuts that the code came from Linux (or more properly, IBM, perfectly within its rights) into SCO, and not the other way 'round.


      I admit to not knowing much about the GPL, but if it does turn out that the code went from Linux -> SCO, doesn't that mean that the SCO property would be subject to the GPL (what with it being "viral" and all, right?)

      Maybe this is why they are doing all this. They've realized that their code is vulnerable, and so to protect it, they have to attack the GPL, lest they go down in flames.
      --
      The only thing I hate more than hypocrites are people who hate hypocrites.
    5. Re:More school yard fun by Anonymous Coward · · Score: 2, Insightful
      Bringing up patents is a huge red herring. SCO's original claim is that there is actual code in Linux that SCO holds copyrights too. They're not claiming that Linux developers re-implementated anything; they're claiming that Linux developers copied things. Patents don't figure into this at all. Keep in mind that a huge number of Linux developers have access to closed-source OS code which they're supposed to pretend they never saw (see: why NTFS development is so slow).

      I suspect what SCO's really hoping for is that somewhere along the line they'll say "ah hah! You have no idea where this snippet of code came from except for some line in the CREDITS file" and then magical justice fairies will award them billions in the ensuing confusion.

      But nonetheless, this really is about copyright, not patents.

    6. Re:More school yard fun by Pharmboy · · Score: 3, Insightful

      they're just learning from the bush administrations... i mean - they've called the geneva conventions "invalid" for a while now...

      I call FUD on you. He said they didn't apply to the people at GITMO, he NEVER said they were invalid. He also said the the UN is at risk of becoming irrelevent, which some would argue is a bit late. He parses his words carefully, and I wish people would quit misinterpreting them intentionally. There is plenty I disagree with Bush on, but misquoting the facts isn't benefiting anyone.

      If you are going to bash Bush, at least get the facts straight lest you lend no credibility to yourself, and all anyone could conclude is that FUD is your goal.

      --
      Tequila: It's not just for breakfast anymore!
    7. Re:More school yard fun by Simon+Brooke · · Score: 5, Insightful
      Your hypothesis is certainly one I wouldn't dismiss immediately, but do you know in what kind of timeframe the SVR4.2 release was made? i.e. Who is the cart and who is the horse, with respect to Linux & SCO.

      System V Release 4 dates from 1991, according to th copyright statement in my manuals. That makes it older than Linux, though not by much. This is irrelevant anyway because ELF is a published standard with an open license, and if it should not have been so published that is an issue between SCO and the people who licensed it, i.e. themselves.

      --
      I'm old enough to remember when discussions on Slashdot were well informed.
    8. Re:More school yard fun by AKAImBatman · · Score: 2, Insightful

      Bringing up patents is a huge red herring. SCO's original claim is that there is actual code in Linux that SCO holds copyrights too. They're not claiming that Linux developers re-implementated anything; they're claiming that Linux developers copied things.

      I understand, but that breaks down even worse in SCO's favor. The litmus test is this:

      1. Is the code EXACTLY the same?
      2. Can SCO prove beyond a shadow of a doubt that the code was explicitly copied, was disguised, did not diverge and was not re-implemented.
      3. Can SCO show a trade secret that was stolen?

      We pretty much know that #1 is false and that #2 is damn near impossible to prove. #3 is useless to them because TISC revealed the secret. They can sue TISC for that (if they have a leg to stand on), but they can't sue anyone else. Thus SCO is still performing barratry and they know it.

    9. Re:More school yard fun by Pharmboy · · Score: 2, Interesting

      I admit to not knowing much about the GPL, but if it does turn out that the code went from Linux -> SCO, doesn't that mean that the SCO property would be subject to the GPL (what with it being "viral" and all, right?)

      The GPL is very clear that if someone tries to use the GPL on software that they have no right to use the GPL on, then they can't use the GPL for it. This means, if someone GPL's someone elses code, it is considered NOT GPLed at all, and it never was, regardless of any claim. In order to license any software, you must first possess the RIGHT to do so.

      Only the legal owner of any code can choose the license his/her software is under. No one can take that away by illegally releasing it under a different license. It is no different than if I stole the source for Windows 98, then "released in under the GPL". That doesn't make it GPL because I never had the rights to do so.

      --
      Tequila: It's not just for breakfast anymore!
    10. Re:More school yard fun by tjrw · · Score: 4, Informative

      Exactly!

      Regarding RCI, no SCO don't have a patent on RCU (as I'm sure you know :-). IBM do. It was invented at Sequent, and patented by Sequent. As IBM bought Sequent in 1999, they own the patent on RCU, and can do whatever they please with it. SCO's nonsense argument about derivative works wouldn't help them even if it were correct (which it isn't). The method is not specific to Unix.

      As regards JFS, the Linux code is derived from the OS/2 version. This has been repeated time after time, but it doesn't suit SCO's story, so they keep peddling the same lies as though that somehow makes them true.

      Talk about clutching at straws!

    11. Re:More school yard fun by platypus · · Score: 4, Funny

      Well, knowing what I know about SCO (only what I read here and on groklaw)

      Dude, then you know probably more than SCO's lawyers.

    12. Re:More school yard fun by cmoss · · Score: 3, Informative

      keep in mind that they are Caldera/TSG not the old SCO that was one of the parties that released the ELF standard.

    13. Re:More school yard fun by atrizzah · · Score: 2, Insightful

      Don't be a dumbass. The UN showed itself to be irrelevant when they did nothing as Saddam made them look foolish and kicked the UN weapons inspectors out. Then they proved their irrelevance when the U.S. invaded Iraq. Regardless of how you feel about the invasion, the UN couldn't do shit to stop it.

    14. Re:More school yard fun by Anonymous Coward · · Score: 2, Funny
      If you are going to bash Bush, at least get the facts straight lest you lend no credibility to yourself, and all anyone could conclude is that FUD is your goal.

      You know, the facts never stopped Michael Moore, champion of the Left.

    15. Re:More school yard fun by drsmithy · · Score: 2, Insightful
      The UN is only irrelevant when the USA, runs willy-nilly over international law, invading/occupying foreign nations and then saying "the UN is irrelevant -- they cant do anything to stop Iraq, OR US".

      The UN has been irrelevant for a hell of a lot longer than that and for much more important reasons.

      Heck, just the fact that they let countries with non-representative governments even participate, IMHO, makes a completely joke of the whole thing.

    16. Re:More school yard fun by golgotha007 · · Score: 2, Insightful

      The UN showed itself to be irrelevant when they did nothing as Saddam made them look foolish and kicked the UN weapons inspectors out.

      The UN inspectors were not kicked out. They were told to leave by the US because the US was about to unleash holy hell on Iraq.

      Then they proved their irrelevance when the U.S. invaded Iraq.

      What was the UN to do? declare war on the US to prove they are relevant?
      The only entity making the UN irrelevant is the United States everytime they make a double standard.

      I'm an American living in Europe, so between my parents and the locals here, I get to hear both sides of the story.
      One of the biggest concerns was when the US went against the UN. That was a major mistake in the eyes of the world.

      The UN wasn't denying that there were WMD's in Iraq. All the UN wanted was more time to be absolutely sure that the supposed WMD reports about Iraq were accurate (which now we all know they weren't).

      The UN didn't make any mistakes here. Why was Bush in such a hurry? The only answer I can think of here is because election was just around the corner.

    17. Re:More school yard fun by schon · · Score: 4, Interesting

      just because something isn't patented doesn't mean it has no protection under copyright

      Umm, what? Copyrights and patents are orthogonal. They cover two completely different things.

      According to the USPTO, if something (like software) can be copyrighted, then it *cannot* be patented - although aspects of it (like an algorithm) might qualify for a patent, the code itself would not. The general rule is that patents protect ideas, copyright protects expressions or implementations.

      This is essentially what SCO is claiming with their copyright arguments, as I understand it.

      In order to determine what SCO is claiming, one must ask which day of the week it is.

      which is not to say those formats cannot be patented, just that it's not what is going on here

      Nobody is claiming that - they're claiming that the format *is not* patented, and that (by definition) you *cannot* copyright a format, so therefore SCO's claims are baseless.

      Unless they can show that the kernel's ELF loader contains code copyrighted by them, they have no case.

    18. Re:More school yard fun by afidel · · Score: 3, Insightful

      RCU comes from Dynix/ptx by Sequent which IBM bought . Sequent like IBM was an AT&T licensee, and according to published letters from AT&T to the UNIX licensee's in their UNIX newsletter AT&T claimed no controll or copyright over wholly customer written subsystems added to UNIX. Beyond that it is doubtfull that you would lose copyright controll over a substantial work just because your work integrated with another copyrighted work. Basically SCO wants to claim that ordinary copyright is super viral to the extent that they own/controll anything linking to UNIX and at the same time wish to argue that the GPL is invalid, it's crazy.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    19. Re:More school yard fun by spacecowboy420 · · Score: 2, Informative

      Just got my karma back, but I gotta do this anyway since you pushed the political bantering.

      1. moveon.org is NOT a far left-wing organization - unless you listen to bill O'reilly. Visit their website, do a logic test. Now do the same at gop.org. logical fallacy after logical fallicy to explain the accusations of the "coalition of the wild-eyed"
      2. The association between Bush and Hitler by moveon.org was made by a private citizen in media presented as an entry into a contest - not moveon.org. The contestent didn't win, and kerry nor moveon.org never endorsed the ad. They also denouced the submitted ad.
      3. Bush/Cheney did however endorse and release an ad that included the Hitler picture that was submitted in moveon.org ad - again, perpetuating the half-truths of the Bill O'Reilly's of the world.

      Fox is NOT "Fair and Balanced", diversify your news gathering instead of repeating the O'Reilly propaganda. Seriously, be a conservative all you want - good for you - just do you research, learn both sides.

      --
      ymmv
    20. Re:More school yard fun by enjo13 · · Score: 5, Informative

      Just FYI: "Substantially similiar" is a legally valid term that is suggesting that the code is a derivative work of the SCO code.

      In order to violate copyright they don't need to be identical copies. Instead they need to show that they are substantially similiar (there it is) to each other, implying that the Linux version is derived from the original SCO code. At what point something stops being a derived work is a whole different mess...

      One common example of this type of copyright dispute is in housing floorplans and architecture. Often someone will see a floorplan they like in a magazine (copyrighted), and move a few things around and have blueprints drawn from that. That's an infringement on the original copyright, because the resulting work is really just a derived form of the original.

      SCO's claims fail on a number of levels, but your 'analysis' is more or less incorrect.

      --
      Turn s60 photos into awesome videos with mScrapbook for all S60 3rd edition phones!
    21. Re:More school yard fun by Zeinfeld · · Score: 4, Insightful
      "Insightful" is more like claiming that left-wing extremists like MoveOn.org are right in connecting Bush with Hitler.

      MovOn.org never made the claim, two anti-bush ads uploaded to a weblog/competition on moveon made the comparison and they were deleted as soon as moveon were told about them. Its a bit like saying that Slashdot is pro-goatsex.

      The tenuous nature of the claim has not stopped the Bush campaign making an ad that intercuts shots of Kerry with shots of Hitler taken from the deleted contributions.

      Clearly SCO are learning nothing from the Bush administration, if you substitute Bush administration for SCO and Bin Laden for Linux what you would get is something like:

      Act One: Bin Linux initiates hostilities against SCO, SCO retaliates with massive lawsuit, then after a couple of months gets bored. Daryl McBride survives assasination attempt by a rogue pretzel.

      Act Two: SCO gets bored with Bin Linux, decides that emacs is a copy of emacs, threatens to sue unless RMS releases sauce code.

      Act Three: Despite protestations from RMS that he has already released the sauce code for emacs and the presence of code inspectors SCO applies for court injunction, RMS is thrown in jail.

      Act Four: SCO hires company run by Daryl's brother to maintain the source code, company hires a hundred fresh out of college students, then bills SCO $5,000 per day each for their services.

      Act Five: Report comes out stating that the grounds for the injuction were lies, SCO argues that the real Bin Linux threat comes from Iran.

      Fact is, if SCO was learning from the Bush administration everything they did would be a complete incompetent Cheney-up from start to finish.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    22. Re:More school yard fun by -Harlequin- · · Score: 4, Insightful

      The general rule is that patents protect ideas, copyright protects expressions or implementations.

      I know this is stupidly idealistic, but according to the patent office, ideas are explicity not patentable, only specific mechanisms/implementations. That the patent office regularly rubberstamps patents on things which are really no more than ideas is just the patent office's usual level of competance.

      You couldn't patent the idea of having a door only open for certain people, but you could patent various ways for making a door act that way. Unless we're talking about actual reality, in which case you could patent breathing, and the patent office would grant it without reading it, leaving it to the people you bill (for breathing without a license) to somehow find the mega$$$ needed to get the courts to invalidate the stupid thing.

    23. Re:More school yard fun by evilpenguin · · Score: 2, Informative

      Actually, ex post facto means "after the fact." The phrase a posteriori is the complement to a priori, which are terms from philosophy that define how a datum is knowable: Knowledge that is "a priori" is knowledge that is known without experience, whereas "a posteriori" knowledge is known only with experience.

      The most useful contrast would be between mathematics, which may be continually derived by pure thought, and physics, which requires that theories be subjected to experimentation.

      Mathematics and logic can be said to be "a priori" systems, but natural science requires validation against experience and is thus "a posteriori."

      IIRC, these phrases mean "from before" and "from after," not "after the fact," which, as I said before, is better translated to Latin as "ex post facto."

      Not that your meaning wasn't clear to me, but quickly looking over the use of these phrases in modern writing shows me that "a priori/a posteriori" are terms mostly used in logic and epistomology, wheras I see them not at all in legal dictionaries, while "ex post facto" shows up frequently in legal writing.

      I don't claim any great authority, here, however, and would be happy to be proved wrong. (Well, not happy, maybe, but I'm preapred for it ;-)

    24. Re:More school yard fun by lynx_user_abroad · · Score: 2, Informative
      If SCO took GPLed code and placed that code into their UNIX products, then distributed those products to their customers, SCO could (potentially) be forced to distribute the source code to their UNIX products that contained the GPL'ed code.

      I think "forced" is the wrong word. If a software distributor adds GPL'd code to their own and distributes the result, they either have to demonstrate they have a license, or they are infringing the copyrights of the GPL'd code author(s). That leaves them two choices, only one of which required them to offer their own code under a GPL-compatible license. The other option is to stop the infringement by no longer distributing the infringing code. The "rip it out and replace it" strategy works just as well for them as it does for anyone, presuming they actually understand how to code it.

      --

      The thing about things we don't know is we often don't know we don't know them.

  3. FreeBSD and linux compatibility? by shadow0dancer · · Score: 3, Interesting

    I'm wondering how this accusation would effect linux compatibility mode in FreeBSD.

    -SD

    1. Re:FreeBSD and linux compatibility? by arivanov · · Score: 5, Interesting

      BSD since 4.x is ELF as well (it gave up on a.out around 3.x). So the claim is valid against all BSDs and even more interesting recent Cisco IOS. Even more interesting, the SCO comment from last year that HP does not infringe comes to mind. HPUX uses ECOFF. It is the last and only commercial Unix not to use ELF.

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    2. Re:FreeBSD and linux compatibility? by senatorpjt · · Score: 4, Informative

      If this is so, then the Sony Playstation 2 would also be illegal since its binaries are in ELF format, right?

  4. Time to move to Mach-o by idiotnot · · Score: 4, Informative

    Make binary compatibility easier with Darwin, anyway.

    This affects everyone, including the BSD's. And, of course, they're full of shit, once again. ELF is not the mortar that binds the OS together. Linux started with a.out, and can probably function just fine with some other binary format.

    1. Re:Time to move to Mach-o by gr · · Score: 4, Informative

      Uh. Are you familiar with what is involved with running under a Mach framework?

      It means running, like MkLinux did, as a client process atop a Mach microkernel architecture. This is diametrically opposite to the way that the Linux kernel functions, which is largely because Linus (and many other people, myself included) thinks that microkernel architectures are a waste of resources in the real world (though they're certainly very pretty for OS research).

      This would also destroy the usefulness of all the binary packages in distribution now, which would be a major financial blow that would quite probably put all of the commercial Linux vendors out of business.

      Also, this wouldn't affect OpenBSD, since they still use a.out. (Hey, refusing to change finally paid off for Theo! Good going!)

      --
      Do you have a /. uid shorter than five digits? No? Then piss off.
    2. Re:Time to move to Mach-o by jrumney · · Score: 3, Interesting
      This affects everyone, including the BSD's.

      Best of all it affects SCO. If ELF support has to be dropped from gcc, what will they use for a compiler?

    3. Re:Time to move to Mach-o by pjrc · · Score: 5, Informative
      Obviously you don't remember the bad old days of Linux a.out. It's not about the binary applications... it's about the libraries.

      Under a.out, each library had to be assigned a memory location. Back in the old days, there was a long list of official assignments that you could download from sunsite and the other major ftp sites. There were three major problems.

      1. New libraries had to obtain an "official" memory range allocation if they were to be distributed to a wide audience. I never compiled any shared libs back then, but I'm sure someone around here must remember who was in charge of the official memory allocation list.
      2. Revisions to a library had to fit within the space they had been allocated. Add too much code, and all of a sudden your shared library may overlap a range reserved for some other library.
      3. Because liberal amounts of extra memory were allocated to each library to allow code size to grow, memory was allocated inefficiently.

      Obviously, this wasn't scalable.

    4. Re:Time to move to Mach-o by slamb · · Score: 2, Interesting
      Halfway tounge-in-cheek suggestion there. I know Linus' thoughts on microkernels. I also know that Mach sucks. Running a monolithic kernel image on top of Mach sucks even more, and there's no good reason to do it.

      My thoughts also. The microkernel crowd in general seems to agree that Mach is not a good microkernel. (L4 is much better.) And writing a monolithic kernel on top of a microkernel, rather than taking advantage of the full microkernel flexibility...I don't see the point.

      Can anyone explain to me why Apple did this with MkLinux, why NeXT did this with NeXTSTEP, and why Apple continued it with OS X? I love OS X's user interface and blend of Unix and old-school Apple stuff...but this one decision, it just seems so dumb.

    5. Re:Time to move to Mach-o by cduffy · · Score: 3, Informative

      Yes, some microkernel OSes *suck*.

      And then, some of them don't.

      See Plan 9, or QNX, or VSTa (still a toy for most purposes -- but very small and fast, and generally considered quite promising by a group of kernel developers I happen to know, a group which includes some folks who are considering building it into an OS suitable for real-life deeply embedded work).

    6. Re:Time to move to Mach-o by dolmant_php · · Score: 5, Informative

      Actually, OpenBSD moved to ELF (for many archs) in 3.4.

    7. Re:Time to move to Mach-o by idiotnot · · Score: 2, Informative

      When NeXTStep was written, single-server was fashionable. It was also a quick way to get a Unix environment, while having a system that didn't necessarily depened on Unix in a non-networked environment.

      As I said in the last post, MkLinux sprung up because Linux didn't run natively on PPC -- and Mach did. At the time, the PPC machines were fast enough that a PPC running MkLinux was performance-comparable to an x86 machine running Linux on the hardware. The project didn't last very long, however. And MkLinux, depending on who you talk to, is a lot better than AIX, which is what they'd been selling before that (yes, real AIX, not A/UX -- that only runs on m68k machines).

      Darwin isn't really mach anymore. It's mach + Free/NetBSD stuff running in the same address space, as well as oskit for the driver framework (native mach drivers are gone).

    8. Re:Time to move to Mach-o by maelstrom · · Score: 4, Funny

      Re: your sig. You fuck off.

      --
      The more you know, the less you understand.
    9. Re:Time to move to Mach-o by laird · · Score: 2, Insightful

      Yeah, I remember dealing with static linking of shared libaries, and it was a mess. Luckily, even if there's some (extremely unlikely) problem that could force us to move from ELF, there are plenty of dynamic linkers out, and we could use some other binary format comparable in functionality to ELF. I don't think that SCO could claim to have the patent on the _concept_ of dynamic linking, since it was invented long before UNIX. (Or is SCO going to try to claim ownership of Multics because it rhymes with Unix?)

      Anyway, if we can't use ELF, we would have to move to another binary format, which means that we would have to pick one new binary format, then recompile and relink of everything. That's a hassle, but it's not fatal.

    10. Re:Time to move to Mach-o by SewersOfRivendell · · Score: 2

      Your parent poster was being facetious, I suspect, but you are wrong anyway. Mach-O requires only a virtual memory system, it doesn't care what the OS architecture is. NeXTstep was always a monolithic kernel, and Mac OS X is today as well. They use Mach, but the BSD portion is fully integrated into the kernel. MkLinux did use a true microkernel architecture on top of Mach, however.

    11. Re:Time to move to Mach-o by bluGill · · Score: 2, Informative

      This was a problem with the linux implimentation of a.out, and not a.out itself. When Linux (all contributers) decided it was time to change, everyone recognized elf as the future, so they combined fixing a.out with jumping to elf.

      Freebsd stuck with a.out for several years longer, until the pain of being different exceeding the pain of changing. Other than being easier to keep in sync with the tool chain (GUN stuff) there was no read gain. (though of course elf is the standard and that is a gain in itself)

    12. Re:Time to move to Mach-o by scottgfx · · Score: 2, Funny

      Usually we brag when somthing is longer, not shorter!

      --
      It's mandatory to wash your hands before returning to the land of Dairy Queen.
  5. awww... by MachineShedFred · · Score: 5, Funny

    Man, we had so long without a SCO article that I thought I missed one about a small implosion in Utah.

    Then you had to go ruin my blissful existance...

    --
    Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
  6. Truth Elves ??? by MisanthropicProgram · · Score: 3, Funny
    It sounds more like the underpants elves ...

    Make a claim that [insert feature] was stolen by Linux

    Sue people/companies

    Hopefully Profit!

    Later on ...
    Shareholders file a class action lawsuit against SCO.... I can dream, can't I?

    1. Re:Truth Elves ??? by PierceLabs · · Score: 2, Interesting

      That's not a dream. When this all comes to light, if SCO can't actually act on any of its myriad threats, the remaining shareholders will sue the company because it will be deader than disco.

    2. Re:Truth Elves ??? by __aahlyu4518 · · Score: 4, Funny

      Disco is dead???
      Damn.. I have to get out more often...

  7. Why wasn't this brought up in 1995? by SlashChick · · Score: 5, Insightful

    From the article:

    "In 1995, the year Novell sold Unix to the Santa Cruz Operation, an industry group calling itself the Tool Interface Standard Committee (TISC) came up with a ELF 1.2 standard and to popularize it and streamline PC software development granted users a "non-exclusive, worldwide, royalty-free license" to the stuff, effectively putting it in the public domain, SCO says.

    SCOsource chief Chris Sontag, the SCO VP in charge of the company's hate-inducing IP push, claims TISC, which folded immediately after the spec was published, exceeded its rights even though both Novell and the old SCO - as well as Microsoft, IBM and Intel - were on the committee."


    So if SCO had a problem with ELF way back in 1995, why didn't they stop this back then? Obviously they had the choice to -- they clearly knew what TISC was doing. So why did it take SCO until 2003-2004 to point fingers at TISC?

    I'm sorry, but this reeks of a last-ditch money-grab by SCO...even more than it did before. The release of ELF into the public domain happened nine years ago. IMHO, SCO should not be allowed to pull this into court because their business model is hurting now. Ridiculous.

    1. Re:Why wasn't this brought up in 1995? by cmoss · · Score: 5, Interesting

      They are pulling ELF in to court because they are desperate to avoid a ruling on IBMs tenth counterclaim scheduled to be heard on Aug 4th.

      This may be a hard sell to the court since they were not a party to the original effort and they can't seem to find any of the documents transferring any rights from old SCO to Caldera/TSG.

      We'll see if it staves off the inevitable for a while longer at the aug 4th hearing. The best part is that the more deperate they act the more chance the principals will end up in jail when all of this fraud is exposed.

    2. Re:Why wasn't this brought up in 1995? by Anonymous Coward · · Score: 2, Funny
      So if SCO had a problem with ELF way back in 1995, why didn't they stop this back then?

      Because the entity currently known as SCO didn't exist at that time. Caldera wasn't founded until 1998.

      I'm in a similar situation. I just bought an old AMC Pacer, so I'm suing everybody who saw Wayne's World because DaimlerChrysler exceeded their rights when they introduced such a butt-ugly car.

    3. Re:Why wasn't this brought up in 1995? by jrumney · · Score: 4, Interesting
      "In 1995, the year Novell sold Unix to the Santa Cruz Operation, an industry group calling itself the Tool Interface Standard Committee (TISC) came up with a ELF 1.2 standard and to popularize it and streamline PC software development granted users a "non-exclusive, worldwide, royalty-free license" to the stuff, effectively putting it in the public domain, SCO says."

      So if SCO had a problem with ELF way back in 1995, why didn't they stop this back then?

      What happened with TISC in 1995 is irrelevant. As the Usenet post from 1993 shows, the ELF support in Linux does not come from any code that TISC released into the public domain in 1995 with the support of SCO. It was a clean room implementation based on documented interfaces from "SYSTEM V RELEASE 4 Programmer's Guide: >ANSI C and Programming Support Tools" (ISBN 0-13-933706-7).

      There is no copyright issue here SCO, but have fun taking the US Navy to court over it.

    4. Re:Why wasn't this brought up in 1995? by John+Hasler · · Score: 4, Informative

      > ...SCO should not be allowed to pull this into
      > court...

      They aren't. In none of their claims in any of their lawsuits do they ever accuse anyone of infringing their copyrights by putting their stuff into Linux.

      IBM, on the other hand, is close to getting a declaratory judgement that nothing in Linux infringes SCO's copyrights. In opposing IBM's motion for summary judgement on that declaratory judgement SCO has explicitly said that they are not claiming any infringement by Linux.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    5. Re:Why wasn't this brought up in 1995? by YouHaveSnail · · Score: 2, Interesting

      They aren't. In none of their claims in any of their lawsuits do they ever accuse anyone of infringing their copyrights by putting their stuff into Linux.

      According to the article, these ELF charges are part of two new documents filed in the IBM case.

      One can only conclude that this is a SCO shenanigan aimed at blocking IBM's motion for summary judgement regarding noninfringment of SCO's copyrights. IANAL, but Autozone's lawyers (and the folks over at Groklaw) seem to think that if IBM gets the declaration, SCO will instantly lose its case against Autozone (and probably DaimlerChrysler and Red Hat, too). So SCO really needs to delay that judgement as long as possible.

      On the other hand, if SCO was serious about this ELF stuff, you'd think they should have brought it up a year ago when it filed against IBM, or at some point fairly early on in discovery.

  8. Can we have some details on the JSF by ikegami · · Score: 2, Interesting

    : [i]The JFS part was expected of course[/i] Am I right when I guess JFS means Journaling File System? Why would it "of course" be mentioned by SCO? Could someone give us its history?

    1. Re:Can we have some details on the JSF by Jahf · · Score: 2, Informative

      IIRC, JFS was contributed by IBM. Go back to the IBM v. SCO mess. I would guess that some part of the JFS code (at least in SCO's mind) contains SCO licensed material.

      Remember that just because IBM wrote most of JFS, it may still contain code that had to be duplicated or rewritten to work outside of AIX. The question is whether IBM violated their agreements with SCO by redistributing or re-engineering those technologies.

      Not saying it is so, only pointing out what SCO is probably trying to say

      --
      It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
    2. Re:Can we have some details on the JSF by AlanWay · · Score: 5, Informative

      From http://oss.software.ibm.com/jfs/ in their FAQ

      Q1. What is the history of the source based use for the port of JFS for Linux.

      A1. IBM introduced its UNIX file system as the Journaled File System (JFS)
      with the initial release of AIX Version 3.1. This file system, now
      called JFS1 on AIX, has been the premier file system for AIX over the
      last 10 years and has been installed in millions of customer's AIX
      systems. In 1995, work began to enhance the file system to be more
      scalable and to support machines that had more than one
      processor. Another goal was to have a more portable file system,
      capable of running on multiple operating systems.

      Historically, the JFS1 file system is very closely tied to the memory
      manager of AIX. This design is typical of a closed-source operating
      system, or a file system supporting only one operating system.

      The new Journaled File System, on which the Linux port was based, was
      first shipped in OS/2 Warp Server for eBusiness in April, 1999, after
      several years of designing, coding, and testing. It also shipped with
      OS/2 Warp Client in October, 2000. In parallel to this effort, some
      of the JFS development team returned to the AIX Operating System
      Development Group in 1997 and started to move this new JFS source base
      to the AIX operating system. In May, 2001, a second journaled file
      system, Enhanced Journaled File System (JFS2), was made available for
      AIX 5L. In December of 1999, a snapshot of the original OS/2 JFS
      source was taken and work was begun to port JFS to Linux.

      So, the original JFS-1 was written as closed source for AIX. However, the JFS that made its way into Linux was JFS-2, which was originally written for OS/2 then ported to AIX and Linux.

      Dunno how SCO can claim code written for OS/2 :-)

    3. Re:Can we have some details on the JSF by vxvxvxvx · · Score: 3, Insightful

      well, reading what you pasted, "JFS2" sounds like something linux doesn't have, but rather is available for AIX. Of course, the JFS on linux would be the second version of JFS1 (JFS1-2?) which wasn't developed on AIX.. However, SCO's theory of "all your base are belong to us" is probably trying to claim since jfs1-2 was moved into the AIX operating system starting in 1997, that is, it code later touched AIX, all earlier versions of the code instantly became property of SCO.

      Yeah, it's a load of BS.

  9. SCO sounds more like Kim Il Jong by raistphrk · · Score: 2, Funny

    SCO has gotten into the nasty habit of claiming ownership (and inventership) to damn near every obvious computer science practice known to man. They're like the software vendor's version of Kim Il Jong of North Korea. The guy claims to have invented the Internet, the television, radar, automobiles, and any other technology the country has.

    Now, if SCO starts killing triplets...

    1. Re:SCO sounds more like Kim Il Jong by Timex · · Score: 2, Informative

      I think you meant Kim Jong-Il...

      --
      When politicians are involved, everyone loses.
    2. Re:SCO sounds more like Kim Il Jong by Elwood+P+Dowd · · Score: 4, Funny

      I'm just waiting for Darl to claim that he's written several operas.

      --

      There are no trails. There are no trees out here.
  10. Development dollars? by shogarth · · Score: 5, Insightful

    The ELF bit is a weak arguement, but what can they do? They have a medium-sized pile of money and a dead-end product line. They can litigate, piss the money away trying to outdevelop both the open-source community and Microsoft in the OS space, or give up and find a new business to try and develop. Given the source of their pot of money, it makes sense to take their shot a the IBM lottery...

    Of course, understanding their position doesn't make the decision a smart one.

    1. Re:Development dollars? by Elwood+P+Dowd · · Score: 2, Insightful

      Well, when your only remaining profitable business plan is to steal, then a moral person would say "I have no business plan, and no hope for profitability. Fire sale."

      An immoral person might go ahead and steal.

      --

      There are no trails. There are no trees out here.
    2. Re:Development dollars? by Pharmboy · · Score: 5, Insightful

      The ELF bit is a weak arguement, but what can they do? They have a medium-sized pile of money and a dead-end product line. They can litigate, piss the money away trying to outdevelop both the open-source community and Microsoft in the OS space, or give up and find a new business to try and develop. Given the source of their pot of money, it makes sense to take their shot a the IBM lottery...

      I think we must be missing something here. I understand your logic, but if you only have $5, you don't go buy a slingshot and take on a Kodiac bear, unless your goal isn't to win to begin with.

      They can't really be expecting to make money licensing Linux. They can't expect to win against the other litigants, since even they know all the other judges want to wait until the IBM case is settled before proceeding. They may not have known this before it all started, but they have to know it now. Its as if:

      1. Sue everyone
      2. ????
      3. Profit!

      And they REALLY DONT KNOW what step 2 is, so they are trying a little of everything. As hard as I look, I just can't believe that they really think they can win, so it begs the questions: What is the *real* motivation?

      Microsoft? Did you read the article about how MS was going to go after open source the other day? (the HP internal docs) I am still waiting for MS to let SCO completely self destruct, then buy their "IP" at a bargain, to hold a cloud over open source. Its like getting your buddy hooked on crack, just so you can buy his stereo cheap.

      --
      Tequila: It's not just for breakfast anymore!
  11. It's about time! by Anonymous Coward · · Score: 2, Interesting

    Ahh, that's funny, I've been been keeping an eye on SCOX on my Yahoo stock watchlist, and I did notice they've been going down the past few days. Even down 3.6% today on an otherwise up market.

    So I was expecting some "good news" from them.

  12. Oh please .... make it stop! by Goyuix · · Score: 4, Interesting

    Come on SCO - as part of my operating systems course in college we loaded ELF binaries (which we also had to create) and RAN them. They have got to be stretching a long way on that one - that is for sure. Not to mention many other OSs (such as the BSDs) can use ELF binaries....

    The JFS claims, that seems like an awful stretch as well, It does make more sense in targetting IBM though as I believe they had heavy involvement in JFS. Honestly I am not nearly as familiar with the ins and outs of it, but unless they are claiming something ridiculous like memcopy() or something...

    Which brings us to number three, 'copyrighted unix headers and interfaces' .... boy. Here comes this crap again. What on earth are they sticking in headers to copyright? #define ONE 1;??? Sounds like I might have a case myself.

    Now the interfaces, which could perhaps be interpreted as API... there is some chance that could have some fuzzy ground I imagine. But how on earth can the judge/court even take them seriously at this point?

    1. Re:Oh please .... make it stop! by DavidTC · · Score: 3, Interesting
      Um, no. I don't know if you're a troll or honestly ignorant, but that SCO isn't this SCO. The first, real, SCO participated in making the standard. Then, years later, sold their Unix licensing business (Which is all they had, Novell still owns Unix, it still gets 95% of the revenue from all licensing.), to a company called Caldera, which likes to pretend it is SCO, so much that it changed its name to 'The SCO Group', aka, 'SCOG', its stock symbol. SCO, meanwhile, changed its name to Tartatella or something.

      If SCOG thought it had purchased the ELF format from SCO, it certainly might have a case...against the old SCO. Of course, those documents have been mysteriously lost, so who knows what Caldera thought it was buying...but it certainly couldn't have actually bought ELF, regardless of how much it might have been mislead into thinking so.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  13. Not the first time... by ElForesto · · Score: 4, Insightful

    ... and not the last. Anyone remember some little company named Rambus sitting in on industry standard-setting and then running down to the patent office? This seems to be happening more and more often these days, and until we see these IP bullies get their noses bloodied in grand fashion, it's just going to keep on happening.

    --
    There is a difference between "insightful" and "inciteful" other than spelling.
    1. Re:Not the first time... by Anonymous Coward · · Score: 4, Informative

      Actually, there isn't all that much similarity except for the general money-grubbing-IP-capitalist stench.

      Rambus committed fraud by ensuring their patented technology became incorporated in the standard without revealing their patent.

      SCO committed perjury by claiming it owned copyrights on UNIX and JFS (Novell and IBM own those copyrights, respectively), and it violated the GPL by not allowing IBM to redistribute code that was licensed to them under the GPL.

      The former was a fraud committed to get real evidence, the latter is a fraudulent claim to evidence.

  14. The stock market greets this latest news... by tcopeland · · Score: 4, Informative

    ...skeptically. Which is nice.

  15. Claims on 2.6 ? It was but a gleam in Linus' eye! by redelm · · Score: 4, Interesting
    How can SCO make complaints about Linux 2.6 which didn't exist at the time they launched their suit? Are they clairvoyant?

  16. Re:Finally by Usquebaugh · · Score: 4, Funny

    This is not the end,
    It's not even the beginning of the end,
    It might, however, be the end of the beginnning.

  17. Now this gets entertaining by arivanov · · Score: 5, Interesting

    Cisco IOS post 11.2 is ELF. So is nearly every format out there except HPUX. This includes BSDs, embedded systems, so on so fourth.

    So they have just got themselves into the aiming calculations of the entire computer industry including the other big Blue, not just IBM.

    Anyway, do not see a problem even if they win this one. While I want to puke just at the thought of ECOFF, it is if IIRC (C) intel and HP and all it will take to get linux to use them will be one big rebuild and a rewrite of libdl. That is if Intel and HP do not decide to put the dl for ECOFF into the public domain.

    In, btw, this is something on which Cisco can buy them just to shut them up (if everyone agrees to go home and stop the lawsuits).

    --
    Baker's Law: Misery no longer loves company. Nowadays it insists on it
    http://www.sigsegv.cx/
    1. Re:Now this gets entertaining by southpolesammy · · Score: 4, Insightful

      this is something on which Cisco can buy them just to shut them up

      You can not, must not cave in to buy a company like this because it sets precedent for the creation of a million more just like them that will create noise and/or sue for things they don't have ownership for nor can prove there is damage being done.

      You must see this out to the end, either being the annihilation of the barratrous company or the squashing of the lawsuit by an informed judicial process. You must send a message to all other wannabes that this type of crap will not be tolerated and that doing so will result in the destruction of their companies, their reputations, and their personal viability.

      --
      Rule #1 -- Politics always trumps technology.
  18. How the stink by overshoot · · Score: 3, Insightful

    do they propose to have copyrighted a binary file format? Infringement would require that the "copied" files be "substantially similar" to the ones SCOX has copyrighted. Sounds a lot more like their usual squishy-"IP" claim: they hold the copyright on a book describing Unix utilities, so any implementation of grep violates their "IP."

    --
    Lacking <sarcasm> tags, /. substitutes moderation as "Troll."
  19. Gupta? by tigress · · Score: 4, Funny

    The charge was made by SCO VP of engineering Sandeep Gupta in a declaration that is currently under seal, but is quoted, albeit tersely, in the new filings.

    Any relation to Dr Samir Gupta?

    1. Re:Gupta? by Anonymous Coward · · Score: 2, Informative

      Probably not. As near as I can tell, "Gupta" is the Indian equivalent of the English surname "Smith"; i.e. there are millions of Guptas running around.

  20. Finally, a SCO story by Anonymous Coward · · Score: 5, Funny
    Whew!

    I was starting to have withdrawals. No SCO story in days. I didn't have my SCO fix. I thought no SCO story could only mean one thing: "SCO had figured out how to take over the world." At last, you fulfilled my deepest cravings for more SCO news and I can go on living in my beautiful world of FUD.

    Thank you slashdot. Without my SCO updates, I don't think I could go on. My life would be in even more shambles than it already is. Even my dog would not speak to me (now, as for the wife, that might be a good thing).

    Long Live SCO and FUD . Better than comics!

  21. Re:Claims on 2.6 ? It was but a gleam in Linus' ey by wambaugh · · Score: 2, Insightful

    If anyone did intentionally lift SCO code for 2.6 after the lawsuits they would have had to have been monumentally stupid, though hillariously spiteful. One would think it would be easy enough to find the authors of the suspect code and ask them before filing a lawsuit.

  22. The Complete Story of Caldera/SCOX by mst76 · · Score: 3, Informative

    The Complete Story of Caldera/SCOX, as told by Yahoo.

  23. Diagnosis and Prescription by DynaSoar · · Score: 4, Funny

    "...as far as the ELF format is concerned 'the Tool Interface Standard Committee (TISC) came up with a ELF 1.2 standard' and 'granted users a "non-exclusive, worldwide, royalty-free license" to the stuff'. Oh, and of course 'both Novell and the old SCO - as well as Microsoft, IBM and Intel - were on the committee'."

    The patient is suffering from paranoid delusions. His accustation of persecution ("theft") despite having previously personally approved of the situation represent a psychotic dissocation from reality and should be construed as a negative hallucination. As such, the patient should be provisionally diagnosed as paranoid schizophrenia, and should be admitted for stabilization and observation, lest he become dangerous to himself or others.

    Seriously, if SCO were a person acting this way towards other people in public, by now it'd be better than even money they'd have been put in hospital.

    --
    "I may be synthetic, but I'm not stupid." -- Bishop 341-B
  24. Of course they have to file something by Anonymous Coward · · Score: 5, Insightful

    Of course they have to file something--the stock's fallen below $5, and the end-of-day painters can't bring it up again.

    (Being below $5 is a bad thing(tm), because many mutual funds cannot own stocks priced that low. Also since one cannot easily sell short a stock on Nasdaq priced below $5, it dries up the pool of short-sellers to be squeezed with price manipulations)

    1. Re:Of course they have to file something by Animats · · Score: 4, Interesting
      Not only is SCOX below $5, today's intraday low, $4.44, broke through the 52-week low.

      SCO's real problem is that the lawsuits are starting to reach the point where SCO loses. AutoZone got a stay. Damlier-Chrysler has moved for summary judgement, and they have a procedural hearing tomorrow at which SCO probably won't look good. Early next month, the big one, IBM's motion for summary judgement on the copyright claims, goes before the judge.

      In the IBM case, SCO is frantically filing motions in all directions, desperately trying to stall a ruling on summary judgement or to raise issues that will convince the judge not to dismiss the copyright claims. If they lose on that one, it's the beginning of the end.

  25. SCO has no standing. by bstadil · · Score: 5, Interesting
    Current SCO is the third link in the chain. Whenever something is sold the successor in interest get's "less or equal" what the seller held.

    Since the seller sold the copyright with the explicit understanding that ELF was in the public domain, NewSCO can not claim anything.

    If someone "exceeded" their authority it's a matter for the parties involved at the time.

    --
    Help fight continental drift.
  26. ELF Info by jwkane · · Score: 5, Interesting
    1. Re:ELF Info by Amigan · · Score: 2, Informative
      What makes the claim even funnier is that SCO Openserver 5.0 was the first time that old SCO actually introduced ELF to its Operating Systems. It was the default, but you could use the a.out format if you wanted to create binaries that ran on SCO Openserver 3.x I can actually remember presentations on ELF as the future and how good it was when I attended SCO Forum in August of 1995.

      SCO Openserver 5.0 came out in 1995 and was the last Intel Unix to move to that standard.

      --
      "Software is the difference between hardware and reality"
  27. "Viral license"? by feloneous+cat · · Score: 3, Funny

    Just when I thought I had that herpes problem licked...

    --
    IANAL, but I've seen actors play them on TV
    1. Re:"Viral license"? by sharkb8 · · Score: 2, Funny

      I'd avoid licking any herpes problem, that's how it spreads.

  28. Re:SCO's business plan will be taught to MBA's by HotNeedleOfInquiry · · Score: 5, Funny

    SCO in the same breath as Edsel,
    You misspelt Enron..................^

    --
    "Eve of Destruction", it's not just for old hippies anymore...
  29. The mainstream press is buying SCO's claims by 0x0d0a · · Score: 4, Insightful

    The mainstream press is buying into SCO's claims just (AFAICT) based on the weight of how often they repeat them and the fact that they have an easy contact point, whereas there is no general "Linux" contact person.

    Take a look at today's CNN.com article, in which the reporter says:

    "The communal aspects of open source can lead to thorny legal questions, particularly when a company claims its proprietary code has seeped into a project. Because developers typically don't offer warranties, end users could be held liable for infringements."

    Wow. It's like saying that all code under the GPL is held to a legal standard that's as harsh as ... well, to give an equivalent example, if an author of a book included some infringing content, it's like holding every person that read the book liable. Eben Moglen's shot this down, it's been raked through the coals on Slashdot and Groklaw ... but because SCO does a better job of managing the press than the "Linux community, as a whole", nasty disinformation about open source is rapidly spreading around the world and seeping into end users' heads.

    Sad. And probably not fixable.

    1. Re:The mainstream press is buying SCO's claims by therealtroff · · Score: 2, Insightful

      Troll? It's the exact same mechanism. The Bush Administration never ever answers questions. They merely repeat their statements and they get reported by the mainstream media and apparently this works and most people are perfectly happy with this. Why wouldn't the same thing apply to SCO?

  30. Re:The neverending saga by Tenareth · · Score: 2, Funny

    Yes, but at least most of those B movies had a random naked woman tossed in for variety.

    --
    This sig is the express property of someone.
  31. Re:Copyright by jenkin+sear · · Score: 3, Interesting

    IANAL, but I don't belive you can copyright a format- you could patent it, but that's not what's alleged here. Note that the FAT implementation that Microsoft is waving around like a big stick is due to their patent, not a copyright claim.

    Unless the code to implement ELF is identical in Linux, I don't see anything like a case here. And if SCOX had a patent on ELF, we'd know it by now.

    --
    What a strange bird is the pelican, his beak can hold more than his belly can.
  32. ELF licence/standard by Anonymous Coward · · Score: 5, Informative

    The ELF Standard says:

    "The TIS Committee grants you a non-exclusive, worldwide, royalty-free license to use the information disclosed in this Specification to make your software TIS-compliant; no other license, express or implied, is granted or intended hereby."

    Now that's pretty damn clear indication that anyone is allowed to use this license.

    So how does SCO own this again? Oh, right, unlike IBM, Microsoft, Intel and the other members of the TIS committee, their business model is to sue! Ok, sorry, my fault.

    1. Re:ELF licence/standard by Anonymous Coward · · Score: 2, Insightful

      Anyone is allowed to use the license, not to change the license.
      I think the issue revolves around no other license, express or implied, is granted or intended hereby. I read as ELF is given to you under this license and no other licenses are implied and allowed. Which means that the release of ELF under GPL is not allowed.

      Richard Stallman would probably stomp his feet too if someone was releasing emacs under a different license.

      I think that the aim is to make GPL a non enforceable license more than collecting money.

  33. Not even close.. by schon · · Score: 4, Insightful

    Anyone remember some little company named Rambus sitting in on industry standard-setting and then running down to the patent office?

    Yeah, they're the same, except that the 'little company' didn't exist when the standard was written, don't have clear title to the format, waited *NINE YEARS* to bring it up, and doesn't have a patent, and thinks that this is a *copyright* issue.

    But yeah, except for all those differences, it's totally the same.

  34. Object formats by Anonymous Coward · · Score: 4, Informative

    Can't use ELF? No prob, we have a few others to choose from ...

    * a.out (Unix / Linux)
    * COFF (Unix / Linux)
    * XCOFF (AIX)
    * ECOFF (Mips)
    * SOM (HP)
    * Mach-O (NeXT, Mac OS X)
    * NLM
    * OMF
    * PEF (Macintosh)

    ;)

  35. Re:Claims on 2.6 ? It was but a gleam in Linus' ey by wambaugh · · Score: 3, Informative
    For those of us with fuzzy memories:

    According to http://www.dvorak.org/scotimeline/, the SCO suit was launched on March 6, 2003.

    According to http://encyclopedia.thefreedictionary.com/Timeline %20of%20Linux%20development Linux Kernel 2.4 was released on January 4, 2001 so it would follow that the code for 2.5 would be under development until the release of 2.6 on December 18, 2003.

    So it's possible that SCO code was incorporated into 2.5 at the time of the lawsuit, but if they had actually seen that happening when they filed the suit you'd think they might have mentioned it. Afterall, they would have been able to make a reasonable argument for an injunction.

  36. ELF vs a.out - Gentoo anyone? by DarkMan · · Score: 2, Interesting

    So, I'm reading the shaky claims from SCO, and I'm remembering that Linux used a.out format.

    I think that the worst case scenario is that SCO get a tempory injunction blocking the use of ELF (nevermind that no judge would actually agree that to not issue on would cause irreprable harm, given that it's 9 years old). Therefore, there is some merit in ensureing that it is possible to build a modern Linux system on a.out format binaries. Additionally, it torpeados thier claim that ELF is the 'magic pixie dust that they stole to make Linux work'.

    This sounds like a case for a source based distribution. Gentoo, being the most used source based distro sounds like a place that might be able to do that. Alas, I'm not familiar enough with Gentoo to comment - so can anyone who is give a definiative answear on whether Gentoo can be used to give a system without ELF binaries. I undertand that there will likely be a bootstrap step (I remember the a.out -> elf shift in the first place, after all).

    It's not just (not even, I should say) fear of SCO, but there is significant meaning in being able to switch executable formats - that's a lot of flexability for the future.

    So, a.out Gentoo, anyone?

  37. The Copyright Problem by sterno · · Score: 5, Insightful

    The problem we see here and throughout the SCO case is that copyright was never designed with software in mind. The nature of software licensing is such that there's frequent cases of derrived works from different sources, which is rarely the case in books.

    If you write a book, it's unlikely that somebody's going to excerpt part of your book for their own use. It's even more unlikely that the excerpt they do make will get used by somebody else in their book. This is a standard practice in software.

    Linux uses Elf. SCO claims that the committee that opened up that standard didn't have the authority to do so. Well, it's now years later, and there are countless works derived off of that original standard, and now SCO wants to undo it.

    Basically this has the effect of destroying copyright in software. How can anybody feel legally safe using any software product at any time when the history of every piece of code isn't out there for our perusal? How many times do we here of code that's out there, gets implemented countless times, and then somebody comes along and claims patent or copyright on some ancestor. The GIF patents are a perfect example of this.

    I'm aware of no good solution to this problem. Every year, more code is written like this, and more copyright issues and patent issues arise. This will lead to legal fights, and overall increase the cost of developing software exponentially over time. Keep in mind that the code were dealing with don't date back much further than 1970, so it's only going to get worse.

    --
    This sig has been temporarily disconnected or is no longer in service
    1. Re:The Copyright Problem by FyRE666 · · Score: 2, Interesting

      The problem we see here and throughout the SCO case is that copyright was never designed with software in mind. The nature of software licensing is such that there's frequent cases of derrived works from different sources, which is rarely the case in books.

      Actually I feel this is a good analogy; whoever wrote the first "Whodunnit" story (probably that dude who wrote the Bible) could claim "Murder She Wrote", "Columbo" and "Hong Kong Phoowee" are all derivative works.

      Stephen King (deceased at 54?) would be dragging Dean Koontz through the courts by his lank, greasy hair, and there'd be no Dallas ripoffs... hmm, actually this is making a compelling argument...

    2. Re:The Copyright Problem by PMuse · · Score: 3, Insightful
      The problem...is that copyright was never designed with software in mind.

      Which is why copyright in software should be abolished and patents should be used instead. (Ducks behind heat-absorbent shield.) No, really; there are some actual benefits to this.

      Patents expire. (Copyrights seem to be going on forever.)

      Modern software is far more like the interlocking gears of a machine than like the mystic gestalt of a painting.

      Copyright cares about where code came from (which is a pain). Patent only cares about what code does.

      Copyrights are automatic, but most stuff that gets invented is never patented.

      Every piece of code written before 1984 would instantly be public domain.

      --
      "We reject as false the choice between our safety and our ideals." --The American President (20.1.2009)
    3. Re:The Copyright Problem by k98sven · · Score: 4, Informative

      The nature of software licensing is such that there's frequent cases of derrived works from different sources, which is rarely the case in books.

      Not true. People use other people's code under license, and people use other people's written texts under license. There is no inherent problem here: A programmer knows when he is and is not writing original code just as well as a writer knows when he is producing original work as opposed to quoting.

      SCO claims that the committee that opened up that standard didn't have the authority to do so. Well, it's now years later, and there are countless works derived off of that original standard, and now SCO wants to undo it.

      Yes, and they can't.

      Basically this has the effect of destroying copyright in software.

      No it doesn't. SCO can claim whatever they want. It doesn't mean it'll stand up in court.

      How can anybody feel legally safe using any software product at any time when the history of every piece of code isn't out there for our perusal?

      Not difficult. As a programmer, don't use other people's code without knowing what copyright restrictions apply.

      No, you can't change those restrictions retroactively, except if a court finds it was an obvious mistake, and even then only within a reasonable timeframe. SCO has no case, yet you seem to assume they are right. One should never assume that about SCO.

      As a end-user you are not liable. You are only guilty of contributory copyright infringment if it can be proven that you knew or should have known that the software you were using contained someone else's code. How are you supposed to know that as an end-user? Especially if you're running a binary? That is just silly.

      As a software developer, for patents: Don't look at patents. If you can't afford to have a team of lawyers continously scrutinize your work for patent violations, the best option is not to look at anything you know is patented. In that way, you can always claim any infringment was unintentional, in which case you are unlikely to be forced to pay damages.
      (Given you take appropriate action when a patent owner does accuse you of infringement)

      As an end user: The same logic on contributory infringment applys.

      I agree though, patents are dangerous and will end up increasing the legal complexity and costs of developing software.

      But copyrights are not a problem in this sense.

    4. Re:The Copyright Problem by BillyBlaze · · Score: 2, Insightful
      I'm aware of no good solution to this problem.

      It's actually pretty easy - apply the idea / expression dichotomy, already clearly established in other areas of copyright law, to code. Distributing line-for-line copies of SCO's ELF implementation, which is their expression of an idea, is and should be illegal. But that's not what they're saying we did; they're saying they own the standard, they own the idea. Copyright law doesn't allow you to own an idea. Anyone who thinks otherwise needs to be educated, anyone who files suit with this misconception needs to fail spectacularly, and any law that doesn't make this crystal clear needs to be rewritten. Copyright law doesn't allow you to own an idea.

  38. Re:Claims on 2.6 ? It was but a gleam in Linus' ey by Anonymous Coward · · Score: 2, Informative

    No, you're the one who's wrong about dates. It was filed nine months before 2.6.0 came out.

    Lawsuit filed against IBM: March 2003
    Release of 2.6.0: Decemeber 2003

  39. Ha, ha! by homeobocks · · Score: 4, Funny

    People said that I was crazy for keeping all of my programs in "a.out" format . . . WHO'S CRAZY NOW?

    --
    MOUNT TAPE U1439 ON B3, NO RING
    1. Re:Ha, ha! by Rev+Saxon · · Score: 2, Funny

      you! but then again, these days who isnt?

      --
      I am that much more enlightened and proportionally disillusioned
  40. A question. by teamhasnoi · · Score: 2, Funny
    Is Darl now so sad that one may take pity on him, rather than punch him in the nose?

    I need to know, as I am conflicted.

    On one hand, a good punch in the nose may do him good.

    On the other hand, hasn't he suffered enough? Why add injury to insult?

    hmm. Perhaps punching him in the nose until he is sad is the answer...

    Decisions, decisions.

  41. Re:Itanium HP-UX uses ELF... by Admiral+Ackbar · · Score: 2, Informative

    Actually, even HP/UX 11.00 on PA-RISC uses ELF on 64 bit binaries:

    HP-UX ***** B.11.00 U 9000/800 675309372 unlimited-user license

    > file /stand/vmunix /stand/vmunix: ELF-64 executable object file - PA-RISC 2.0 (LP64)

  42. ELF, COFF, and PE by tjrw · · Score: 5, Interesting

    Oh, another little point that the article messes up, and that is somewhat amusing.
    ELF is not "similar to Microsoft DLLs", or that's badly worded. It's similar to Microsoft PE format.

    ELF is derived from COFF. It was mostly a rewrite of COFF with some bad assumptions and nn-portabilities fixed. It so happens that Microsoft's PE (PE-COFF) format is also derived from COFF and is very similar to ELF. If the format was somehow "protected" (which wouldn't be via copyright as pointed out elsewhere), then Microsoft are also guilty of copying. If SCO really own the copyrights to Unix (they don't), and if copyright applied here (it doesn't), then MS are in the same boat with everybody else. Lucky for them that SCO don't have a leg to stand on :-)

    Tim

  43. Does SCO's stupidity put them in the legal clear? by 0x0d0a · · Score: 2, Funny

    These guys ought to be tried and convicted for barratry, regardless of whether their legal counsel is this stupid or not.

    Actually, if they're stupid enough to actually think that they're right, they wouldn't be guilty of barratry.

    I look forward to a future case involving SCO with Darl trying to prove conclusively that he was too stupid to realize that his lawsuit was a load of BS.

  44. TIS, UNIX International, and ELF 1.1 by tlambert · · Score: 5, Interesting

    TIS, UNIX International, and ELF 1.1

    That's a handy reference document for SCO, the version 1.2 of the specification. Too bad it wasn't the first published version:

    Google for "pfmt11.pdf"; here is the most interesting and damning excerpt:
    -
    "Some of the major reasons for selecting this format are the public nature of the specification and the fact that the PLSIG and ABICC standardization committees can enhance its formats."
    -

    This version came out of USL and UNIX International, who are jointly credited with the creation of the ELF 1.1 standard. Even if USL could argue rights, the current SCO can't. This standard, along with the DWARF standard, TET, ETET, and the last draft of Specification 1170 (the original Single UNIX Specification) were published on the UNIX International FTP server. UNIX International was a legal agent for USL at the time of publication.

    If you want to check into anything, check into the contractual agreements between USL and UI with regard to what rights UI did or did not have. You will find that they had full rights to publish the standard on behalf of their member USL.

    In the interests of full disclosure, I was a Novell/USG ("UNIX Systems Group") employee at the time. Novell/USG was comprised of the NWU ("NetWare for UNIX"), NUC ("NetWare UNIX Client"), and the former USL. I'm one of the people who rescued the public content of the UNIX International FTP server and found it a new home at various other corporate sites when UNIX International effectively disolved in 1994. One of the documents rescued was this very document.

    -- Terry

  45. Quite funny... by WebCowboy · · Score: 4, Funny

    ...but when Winston Churchill managed to make it sound profound.

    Will there EVER really be an end though? SCO will probably lawyer themselves out of existence, but what is stopping some other greedy little twerp from pulling the same stunt with copyright claim or perhaps a software patent? (OK, I'll be fair, McBride isn't a little person)

    It seems that even very obvious or simple ideas can be patented these days, which gives the patent holder a pretty effective legal weapon. Even without patents (after all, the central argument by SCO doesn't involve patent issues) the most flimsy and ridiculous claims can be brought before court, wasting everyone's time and money.

    As long as there are lawyers without ethics or scruples (and the majority lack both) there will be no real end. Unfortunately, lawysers are quite resilient. If the bomb were ever to destroy civilisation, only cockroaches and lawyers would survive--and I'm sure one lawyer would sue another for millions and order him to exterminate the cockroaches at his expense.

  46. You forgot the most important one! by Anonymous Coward · · Score: 2, Funny

    * PE (Windows)

    Hey, it stands for "portable executable", we might as well port it...

  47. I HOPE YOU ARE WELL! by argent · · Score: 2, Funny


    From: Sandeep Gupta
    Date: Tuesday, july 20, 2004 12:53 AM
    Subject: TRANSFER

    Sandeep Gupta

    Dear Sir/Madam,

    I am fine today and how are you? I hope this letter will find you in the best of health. I am Sandeep Gupta, the VP of "Engineering", of the "Santa Cruz Operation (SCOX)", a subsidiary of the SCO Group (SCOX).

    SCOSource (SCOX) was set up by SCOsource chief Chris Sontag, to manage the excess FUD accruing from Intellectual Property Claims and its allied products as a domestic increase in the Copyright products to develop the litigation in the Linux Lawsuit producing areas. The estimated annual revenue for 1999 was $45 Billion US Dollars Ref. FMF A26 Unit 3B Paragraph "D" of the Auditor General of the Federal Republic of Nigeria Report of Nov. 1999 on estimated revenue.
    ....

    No, I can't do any more, it's too much like making fun of the mentally deficient.

  48. Some article problems by eventhorizon5 · · Score: 4, Informative

    There's some weird errors in the article, especially since it comes from a Linux magazine:

    "ELF is sorta like Microsoft's DLLs and was developed by AT&T's Unix System Labs as part of the Unix Application Binary Interface (ABI) before Unix was sold to Novell in 1993."

    ELF is not like Microsoft's DLLs. ELF is a binary executable format, and is comparable to Microsoft's PE executable format (am i correct on that?) used in their EXE files. Unix shared libraries are comparable to Windows DLLs. Also, that's the first time I've ever seen the word "sorta" in an article. hmmm....

    They also don't mention that almost every Unix OS uses the ELF format (as far as I've seen).

    "The Free Software Foundation is also the creator of the GPL, the viral license that makes Linux so provocative."

    Is this a statement from the Linuxworld author or SCO? SCO claimed the GPL was a "viral" license, but if that is coming from Linuxworld then something's wrong.

    "It also says the journaled file system (JFS) module from later versions of AIX, which SCO believes may derive from the JFS Unix, is in Linux 2.6. - MOG"

    what's "the JFS Unix"?

    Anyway, SCO is going insane and should hopefully die soon. But the author of that article needs to learn more about Linux first lol (especially since it's a Linux magazine).

    -eventhorizon

    --
    #Secret Windows Source Code, in MS C% - if (uptime >= "24 hours") then bsod() else print "Windows License Violation!"
  49. Broderick affidavit by y2imm · · Score: 2, Insightful

    In addition to its usual bullshit and bluster, SCO finds it necessary to occasionally perform a tactical release of an especially stinky pile of festering, dripping wet feces. I believe we owe this particulary pungent release to the Wednesday morning meeting where Mr Broderick's affidavit will more or less be shitcanned. A somewhat embarassing turn of events for SCO, to say the least. These guys must have huge arms from shovelling so much shit.

  50. Regardless by einhverfr · · Score: 2, Interesting

    The fact that this had to happen is scary enough.

    The torture policy from August 2001 can be found here:

    http://www.washingtonpost.com/wp-srv/nation/docu me nts/dojinterrogationmemo20020801.pdf

    --

    LedgerSMB: Open source Accounting/ERP
  51. thefreedictionary.com by Stormie · · Score: 5, Informative

    Please do not post links to thefreedictionary.com - they are a dodgy site which repackages Wikipedia content whilst stretching the GFDL as far as they possibly can.

    Look at that link you posted - you'll see a credit to Wikipedia at the bottom. Now disable javascript in your browser and refresh - ooh, the credit is gone! They insert it in with javascript rather than putting it in the body of the page to ensure that Google doesn't pick it up. Why? Because a link to Wikipedia's article would help lift Wikipedia's pagerank above that of freedictionary.com.

    Just say no, and if you want to read Wikipedia's timeline of Linux development, read the original.

  52. What a surprise, or not. by miffo.swe · · Score: 3, Interesting

    Just as the share price is slipping below they release this. I cant imagine this being a coincidence. In court they have said nothing about this at all. They have been ordered to provide proof of what specifically linux infringes on, not only the IBM stuff, and has brought nothing but "the dog ate my homework". This despite two court orders to bring forward specifications like this.

    The board is surely behind this and i suspect the SCO laywers are furious. Now they have to explain to the court why this was so damn hard to bring forward in a court with two orders hanging around their neck while it was this easy to tell the media.

    Share price up tomorrow and then as theese unfounded allegations get shot down it will fall again.

    --
    HTTP/1.1 400
  53. Demise dollars by Anonymous Coward · · Score: 5, Interesting

    What is the *real* motivation?

    I used to think that way too, before "I made $10 million bucks and all I got was this crummy t-shirt."

    Seriously. Built an early ISP. Sold it for a ton of money. Raised an additional $20 million to chase UUNET and PSI's coat-tails. Had a neutral broker in the whole deal steal the money and the company. His attorneys stalled everyone out long enough to get money to offshore banks. We all won the suits, and never saw a dime. Company was long dead by the time the court system got done.

    What I didn't understand at the time was that people like this know how to make money going down. Study what they call penny stock companies (ala bulletin board stocks/pink sheets). You can run one of these that does absolutely nothing, never files SEC documents, and make a nice income. Here's the middle item of the underwear gnomes strategy:

    1. Incorporate a dummy privately trading C corporation which you and your friends own.
    2. Use your public bulletin board company to acquire the dummy company. Claim the dummy company has some mystical super secret technology, or better yet, a patent claim against someone like Amazon.com, Priceline, Ebay, etc. When you buy it, it not only loads you and your friends up with more shares of stock (you buy it with the public company stock, and if you're smart, you do much of this w/ registered stock you can immediately dump), but it puts a bunch of press releases out about the event and gets half of the stock buying market going in a feeding frenzy buying your public stock.
    3. Dump a bunch of your newly accumulated shares. Ride the stock price down to $0.001.

    Repeat steps 1-3 over and over. Oh, when creditors come, make sure you drive the price to zero again (this makes it worthless for them to come after you and even keeps them from pushing involuntary bankruptcy which would take over your company). Claim you were an innocent investor who lost millions too. If pressed on where financial documents are, make sure you had hired some stupid kids and promoted them to CEO by promosing them multi million dollar paychecks. Have them sign all the IRS and state revenue department documents, but don't ever let them actually have control of the bank accounts. This sends the IRS and SEC after them and will stick them with tax obligations for decades. During this lying low time, acquire a few of your dummy companies and load back up on stock.

    Sound far fetched? It happens every single day. The SEC told us it could not do anything about these and could only worry about the big Worldcom sized matters because they were "underfunded and overworked." The rest of the story is that it takes financial and political clout to get the SEC to investigate. Common folks don't matter.

    So is there any wonder that the names behind SCO include power hitters from both parties and much of Utah's power base? Just another way of taking money from the lower classes...

    1. Re:Demise dollars by MikeFM · · Score: 2, Interesting

      Reminds me a lil of my talk with the FBI the other day. They said thye really couldn't do anything about an ongoing attack on our business by a competitior, although the actions are definately illegal and criminal, until the damages can be verified to be at least US$1,000,000. If we don't make it to that level of damages because we've been driven out of business first then tough luck. Great.

      On the other hand my backup plan is to go into hacking myself and steal about US$900,000 from the jerks doing this to us. As long as the FBI doesn't care I guess I might as well. Oh yeah, the local police, who have an Internet crime department, claim to be unable to deal with any crimes involving the Internet.

      Added to your story about the SEC I think my confidence in the governments ability to help me is pretty low. Nice that my tax dollars are paying to protect only big businesses.

      --
      At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
  54. RCU and Sequent by msobkow · · Score: 4, Interesting

    I was working with CBIS (Cincinnati Bell Information Systems) in the early '80s when Sequent S81 was running Dynix/ptx with SVR and BSD interface flavours.

    The technical sales reps were very hot on RCU and how it worked with NUMA to scale the system. 32 way SMP of 386's might not seem much now, but it was significant back then.

    Their plans were to have multiple OS flavours under Dynix, relying on RCU to provide scalability to AIX, SunOS/Solaris, and other operating systems that would sit on top of the monolithic ptx core.

    From day one, RCU and NUMA were marketted by Sequent as seperate products targetted at many operating systems and vendors, not as just a part of Dynix.

    I'm tired of watching SCO's insanity. The industry did not develop in a vaccuum -- there are hundreds if not thousands of us who are witness to how the systems were really developed, despite some IP vulture corp's claims otherwise.

    It's a disgrace that SCO's legal team and IP trolls haven't been arrested for fraud and locked up by now. They have no legal case, they never did, and they never will. It's time for them to be spanked and sent to sit in a jail-cell corner for 20 years each.

    --
    I do not fail; I succeed at finding out what does not work.
  55. Those million lines... by utlemming · · Score: 2, Funny

    Finally, we found those millions of lines of code. We just thought they were talking about source code and they were talking about compiled code. It all makes sense now...

    --
    The views expressed are mine own and do not express the views of my employer.
  56. Lifting ELF? by Rimbo · · Score: 2, Funny

    Is lifting elves anything like tossing dwarves?

  57. Re:Finally by kbogert · · Score: 4, Funny

    Hello, this is Darl McBride,
    I'm sorry to inform you, but this Winston Churchill quote has been acquired by SCO through a series of acquisitions and mergers. As with the linux operating system, we require that you license this quote from us for the low price of $699 a post.

    Thank you, and "History will be kind to me for I intend to write it!"

    http://www.workinghumor.com/quotes/winston_churchi ll.shtml

  58. Microsoft strategy by scoove · · Score: 2, Interesting

    I am still waiting for MS to let SCO completely self destruct, then buy their "IP" at a bargain

    I've been wondering about this as well, though really see the SCO deal as more of a trial balloon and not the actual mother of all battles for open source.

    It really doesn't seem like Microsoft's approach (remember how many billions they have and the pride that comes with the wealth and dominance). A proxy battle is more interesting as a means of testing the waters and seeing how the open source world responds. Where are they resiliant, and where are they weak? Toss pathetic little SCO and their delusionary CEO at them (much in the manner Hillary Clinton is 'endorsing' Kerry/Edwards). How often have they acquired a weak product and threw it in the competitive pool prematurely, fully knowing it wouldn't swim - only to come back in version 3 or 4 and destroy the competition (after having learned all they needed).

    In this respect, the more interesting game is the one not being played - the game of omissions, unmoved pieces, etc. Where is F/OSS weak and scrambling? You can bet Microsoft is designating many millions to carefully observing this battle - their dominance depends on it.

    Microsoft does not play to lose. They won't let SCO hit the real IP issues - rather have them throw items like ELF, JFS and header similarities that you know will fail. This is textbook Art of War.

    *scoove*

  59. If SCO declares war on the ELFs... by Black+Art · · Score: 2, Funny

    I guess that they really are Sauron.

    "One OS to rule them all and in the darkness bind them."

    --
    "Trademarks are the heraldry of the new feudalism."
  60. Smallest ELF program by truth_revealed · · Score: 2, Interesting

    You can't talk about the ELF format without mentioning this gem. You learn a lot about the format when you push it to its limits.

  61. Transaction pattern for SCO by Artifakt · · Score: 2, Informative

    SCO stock's inside trading record shows five automatic sell orders and only two regular sells in recent History (Going back to Sept. of last year). No inside trades have been reported since April 7th. There are no buys or automatic buys (0).

    Largest number of transactions (by far) and largest total value (by a smaller ratio) is Director Thomas P. Raimondi.

    Gasparro, Larry (VP), Broughton, Reginald (SR VP), and Bench, Robert K. (CFO) all appear on the list. Bench owns (or owned by the most recent record) roughly 2.4 times as much stock as the next largest investor on the list.

    Hunsaker, Jeff F. is the only person appearing on the list who is not shown with a position in the company described to explain why he is an insider, but other sources confirm he was a SR VP.

    Interestingly, Darl's name does not appear at all on the inside trading list.

    --
    Who is John Cabal?
  62. Re:Finally by Zeinfeld · · Score: 2, Informative
    Hello, this is Darl McBride, I'm sorry to inform you, but this Winston Churchill quote has been acquired by SCO through a series of acquisitions and mergers. As with the linux operating system, we require that you license this quote from us for the low price of $699 a post.

    Actually while he was an ordinary MP Churchill spent a lot of time on copyright matters. He made sure he kept the copyright on all his speeches. The BBC have to pay a substantial fee every time they use them. Its probably at leas 500 quid by now.

    --
    Looking for an Information Security student project suggestion?
    Try http://dotcrimeManifesto.com/
  63. SCO Claimed Linus shot Kennedy... by gmac63 · · Score: 2, Funny

    ...from the grassy knoll. You're point is??

    -- Lifted this SIG from Linus himself. --

    --

    INSERT INTO comment VALUE('Doh!') WHERE user='you';
  64. You've heard Winston Churchill's voice, right? by mcc · · Score: 2, Funny

    That man could read "Green Eggs and Ham" and it would sound profound.

  65. Diversion to law school... by EvanED · · Score: 2, Informative

    The burden of proof is indeed a preponderance of evidence. I don't like the description of "51%" because it isn't that meaningful to me. I prefer saying that proving something by a preponderance of evidence means showing that it is more likely than not. (Including the defense's evidence of course.) Barron's law dictionary has the quote "Evidence preponderates where it is more convincing to the trier [of fact] than the opposing evidence."

    Clear and convincing evidence is sometimes used for affirmative defenses, such as insanity. (Usually it's a preponderance of the evidence.) In these cases, the defense must show by clear and convincing evidence that the defense was met. If during deliberation the jury finds that the burden was met, and the prosecution failed to disprove the defense by a 'beyond a reasonable doubt' burden, they must acquit.

  66. Comment on misleading post(s) by Petrini · · Score: 2, Insightful

    This is, by turns, misleading and plain wrong.

    I understand, but that breaks down even worse in SCO's favor. The litmus test is this:

    1. Is the code EXACTLY the same?


    This is not the litmus test. Copyrighted material need not be copied exactly for infringement. See that part on "substantial similarity" above. While the exact breadth of copyright protection is not nailed down, it is certainly not "exact" by any stretch of the imagination or caselaw.

    2. Can SCO prove beyond a shadow of a doubt that the code was explicitly copied, was disguised, did not diverge and was not re-implemented.

    Uh, what? First, SCO only has to show that it was more likely than not copied. Reasonable doubt is only for criminal trials. Second, again, it need not be copied exactly. Third, it need not be disguised. In fact, copyright is a strict-liability statute. Intent is completely irrelevant. Even if you are influenced subconsciously, you are liable. Independent creation is a complete defense, but not realistic here, I don't think. Fourth, I don't understand what you mean by divergence and re-implementation. It sounds like similarity or derivative works. In either case, your standard of exact copying is wrong. Derivative works are entitled to the same protection as the original.

    3. Can SCO show a trade secret that was stolen?

    Trade secrets have absolutely nothing to do with copyright law.

    We pretty much know that #1 is false

    First, your #1 isn't the right test. Second, you know nothing until a jury tells you. It's a crapshoot like no other.

    and that #2 is damn near impossible to prove.

    Well, you have a strawman. You constructed an impossibly narrow and inaccurate test. Of course it's impossible to prove.

    #3 is useless to them because TISC revealed the secret. They can sue TISC for that (if they have a leg to stand on), but they can't sue anyone else.

    Again, nothing to do with copyright, which, with contract breach, is the heart of SCO's claims. I feel you might not be well-versed on these points.

    Thus SCO is still performing barratry and they know it.

    Barratry. You keep using that word. I do not think it means what you think it means.

    1 : the purchase or sale of office or preferment in church or state
    2 : an unlawful act or fraudulent breach of duty on the part of a master of a ship or of the mariners to the injury of the owner of the ship or cargo
    3 : the persistent incitement of litigation

    [from http://www.m-w.com/]

    They're not inciting litigation. They're instigating it. Furthermore, they haven't done it persistently, just one big, long case.

    IANAL, but I have taken copyright and contract law classes. I am not Just Guessing here.

  67. Odd... by xpccx · · Score: 2, Funny
    "SCO has finally spoken."

    I thought we were waiting for them to stop speaking.

  68. Re:Kernel 3.0 will be double in size by diegocgteleline.es · · Score: 2, Insightful

    Only in the changelogs. Real source don't have all those comments (nor you need them - you _have_ the changelog, the BK changelog, you can see who wrote x line in $foobar file and see the patch which changed it)

  69. Hey Darl, got some news for you! by shplorb · · Score: 2, Interesting
    Darl my man, did you know that Sony's PlayStation 2 uses the ELF format as well?

    /me stands back and waits for Sony to crush SCO like a bullant that's just bitten them.

  70. Standards can't be owned by DavidTC · · Score: 5, Insightful
    Okay, even ignoring the fact that the old SCO helped write the public domain document, this is a new level of crackheadedness even for SCO...because you can't 'own' standards like that.

    There are three ways of 'owning' a standard:

    The first is patents. For example, something about Betamax tapes were patented, and thus people had to license the standard from the owner, Sony. SCO has no patents, so can't possibly have one over ELF, so let's move on.

    The second is trademarks. For example, Firewire is trademarked by Apple. This doesn't stop anyone from making Firewire ports on their laptop, but it does stop them from calling them Firewire ports, without paying a fee. Likewise, anyone can impliment ISO-9001, but you have to get certified if you want to call yourself that. (Technically, I don't think these are trademarks, they're 'seal of approval' marks, but they're under trademark law somewhere.)

    The third is ownership of the copyright of the standards document. Quite a few standards organizations make their money this way.

    While I know SCO does not have a trademark on ELF, and I doubt they somehow have copyright on the standards document that someone else released into the public domain before they were born, the important thing to remember is that only patents can stop someone from implimenting a standard.

    I can sit here without having pay any money to Phillips for their standards documentation or their trademark and build a CD player. I can't call it a 'CD' player without getting their approval, and I'll have a hell of a time building it without looking at their documenation, but as all patents on basic CD players obviously expired already (Yeah, it's been 20 years.), I can build one, and even sell it.

    As there never were any ELF patents, there has never been anything to prevent anyone else from implimenting it, period. Even if TISC trademarked 'ELF' and sold the standards documentation, it's still perfectly legal for someone to use that document, or in fact any way of figuring out the format they want, and impliment a system that uses ELF, even if they have to call it 'HOBBIT' or something. (Remember, reverse engineering for compatiblity reasons is still legal.)

    (For everyone still paying attention, there is standard information in the format, and I can just hear everyone thinking 'what about copyright on those bytes?'. Well, no go. It's been explicitly ruled that, since copyright is only on creative works, and as information required by a standard is not 'creative', but 'factual', thus, you can't copyright it.)

    --
    If corporations are people, aren't stockholders guilty of slavery?
  71. SCO hostile takeover! by baylanger · · Score: 2, Funny
    The beginning of the end of SCO!

    As of today, how much is SCO worth on paper? Even if we all know SCO on the mid-term (I'm thinking more like ... very short-term) is worth NOTHING.

    How much money / Linux users do we need to make a hostile takeover of SCO? Once we have the control, we can shutdown SCO by using their own code... "init 5" !!!

    This comment is (C)2004 under the GNU LGPL license. SCO, feel free to re-distribute this information to your shareholder assets -- Don't forget to keep the license part of this comment, otherwise we'll sue you!
  72. The mcbride song by bani · · Score: 2, Funny

    Rollin' rollin' rollin'
    Claim your code is stolen,
    Keep them lawsuits rollin'
    mcbride!

    There's no evidence for your case
    Just lie with a straight face
    We're spreadin' our FUD far and wide

    Whine and pout, make it up
    Make it up, drag it on,
    Whine and pout, make it up
    mcbride

    Lie and shout, fud and spin,
    fud and spin, lie and shout
    Lie and shout, fud and spin,
    mcbride!