Slashdot Mirror
PearPC Trying to Sue CherryOS
Varg Vikernes writes "PearPC developers are taking in donations to sue Maui X-Stream, the developers of the MAC emulator software CherryOS. There have been allegations that CherryOS is nothing more than PearPC code, which is open-source, but with a GUI attached to it. One of the PearPC developers tried to get in contact with someone from Maui X-Stream, but eventually were told to "speak with an Attorney" about the allegations. "
It might be worthwhile mentioning that CherryOS (PearPC) is not a "MAC" (sic) emulator, but rather a general PowerPC architecture and motherboard emulator. PearPC presents itself as such. However, CherryOS markets and specifically targets itself at Mac OS X. Unfortunately, Apple's Mac OS X license agreement specifically states it can only be installed on an Apple-branded computer. Aside from the PearPC issues, CherryOS is a commercial product actively encouraging its users to break Apple's Mac OS X license agreement. And yes, this license agreement is binding: that's why no one makes clones. (And no, Apple "ROMs" are no longer required. Haven't been for ages.)
Funnily enough, Maui X-Stream president Jim Kartes said:
We are building an emulator like they are that uses Mac language. PearPC uses Mac language and next thing you know, they say we are using their code. This is a totally different architecture.
This comment makes no sense. "PearPC uses Mac language" has no meaning, and is, if anything, indicative of the fact that this company does not fundamentally understand the operation of innards of their product, which isn't surprising, since they didn't create it. PearPC is essentially a PowerPC motherboard emulator, which emulates a PowerPC processor, and various necessary elements of a PowerPC motherboard. I think what Kartes is trying to claim is that because PearPC and CherryOS do the same thing, it's no surprise that they'd appear similar. This claim is absurd, because the evidence is overwhelming that CherryOS is using PearPC as the emulation engine. CherryOS is essentially a graphical wrapper for PearPC, which does nothing more than pass instructions to PearPC and execute PearPC within itself. It tries to conceal, rather poorly, that PearPC is what's running underneath. Aside from the proof of very unique shared strings and symbols above, CherryOS also shares PearPC's featureset, or lack thereof in the case of support for sound and networking, and even PearPC's specific bugs. In sum, any claim that CherryOS and PearPC would share unique strings, variable names, and symbols simply because they're both emulators is ridiculous. Also, saying "Mac language" is really irrelevant because, aside from not making sense, PearPC (and CherryOS) doesn't have anything to do with the Mac or "Mac language". It's a *PowerPC* emulator. The fact that a Mac operating system runs on it is incidental; PearPC (and CherryOS) doesn't contain or use anything that could be referred to as "Mac language".
eWeek has a general overview of the situation:
http://www.eweek.com/article2/0,1759,1775386,00.as p
Below is a comprehensive collection of evidence, which runs the gamut from CherryOS including original PearPC graphics, extremely unique strings and error messages, debug code from PearPC, the same unique MAC address as PearPC's default network adapter (of which there are approximately 184884258895036416 different combinations), shared specific functionality, including bugs, and so on, not to mention code from other GPL projects:
http://www.ht-technology.com/cherryos-pearpc/cherr yos-pearpc.html
http://www.drunkenblog.com/drunkenblog-archives/00 0501.html
http://www.drunkenblog.com/drunkenblog-archives/00 0503.html
http://www.drunkenblog.com/drunkenblog-archives/00 0504.html
http://www.drunkenblog.com/drunkenblog-archives/00 0507.html
Obligatory corny fruit joke:
There's not a valid suit there...it's like comparing apples to oranges!
Badum-chh!
I justed donated.
I'd like to see the GPL tested over this a bit more. It just adds one more opinion in future events.
That and this guy blatenly misuses GPL'd code repeatedly and then has the audacity to tell the world that he wrote it all.
Proceed with Format (Y/N)? Y
That annoys me so much I could strangle a manatee in the nude.
Do not touch -Willie
the Apple.
keanmarine.com
that's one disfunctional fruit salad...
Rise up in the cafeteria and STAB them with your plastic forks!
...take a look at this. [In Internet time it's kinda old, March 16.]
In this case, the people responsible for this are selling the product of another, not just using it for their own collection (which they would be all right with).
It would be a different situation if the RIAA were, for example, suing people who burn pirated music and sell it.
Not retroactively, the GPL has a provision that says if you violate it, it permanently terminates the license. Since they violated the license, it's terminated. They have no valid license to distribute PearPC at all now. Even if they belatedly decided to comply with the terms of the GPL. It's too late.
You say
PearPC has been a very big deal to me for a long time. What Arben and MauiX are doing is wrong. Funny thing is they had a chance to step to the plate. A commercial app based off PearPC was never out of the question. They just chose to go about it the wrong way. The community backing PearPC would have (most anyway) supported someone packaging a commercial app derived from PearPC as long as they followed the GPL it was released under. Instead this company has chosen to lie and attempt to hide the facts. It's a fight they can't win, but they are for whatever reason determined to do so.
So if you are a PearPC supporter... I would suggest lending any help you can...
and if not... then as a supporter of the GPL any help you can is needed as well.
"why don't you just slip into something more comfortable...like a coma!"
No, the problem is that I've never seen anyone here go to great lengths to rationalize and justify this type of copyright infringement. But when Slashbork posts the *AA-story-of-the-week you can browse at +5 and read the most mind-bending, self-serving "commentary" about why copyright is "evil", the *AA sucks, the artists are getting screwed and "we're sticking it to the man so fire up eMule and let's get it on". To claps and assenting nods from the peanut gallery. Time and time again.
Copyright is copyright. The GPL exists to counter the idea of copyright and gets its "teeth" as it were from it as well. If everyone is going to ask for blood when the GPL is violated somehow (by ignoring the force of the of the work's original creator copyright) then maybe everyone could also cry foul when someone tries to call infringement "fair use" because it happens to be music instead of source code.
think about it.
CherryOS is an attempt(allegedly) to make money off a gift given to society via GPL without giving credit where credit is due.
P2P mp3 downloaders are breaking the law, no doubt about that, but only when they download copyrighted works.
However, they are downloading something that is overpriced, and something for which they may have
a "right" to download. what if they own the cd? what if they own it, but they lost it or broke it? they paid for the right to listen to it.
"Trying" to sue?
Sue, or sue not. There is no try.
"MAC", in all capitals, stands for Media Access Control, and is the hardware address of your Ethernet card.
"Mac" is short for "Macintosh", which is the computer made by Apple.
Call me a stickler but I believe there is just as good a reason for this convention to be enforced as there is for the difference between "KB","Kb","kb", and "kB" to be enforced. Reply if you really need me to elaborate further.
CAn'T CompreHend SARcaSm?
We got similar advise once. One of our supposed 'distribution partners' tried to license a product of ours, under their own name.
They walked away from the deal, started selling a different product under that name, but claimed our performance numbers (this was a fire supression chemical), and even quoted our test results, for a totally dissimilar product!
One of our legal staff advised us, "It's going to be a terrible pain to sue them. Rather, continue selling your products, use the same marketing literature, and 'copy-cat' them right back. Force them to sue you, if they dare."
The PearPC community should do this to CherryOS. Create a gui, that matches CherryOS exactly.
Release it as CherryOS Plus. Even use the same name. If they have the balls to take you to court, lots of interesting things will have to be revealed in discovery.
It'll cost you the same amount in lawyer fees, but it'll cost them much more. (Easier to defend, especially in a GPL question, where discovery will reveal the code).
WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
straight from the horses mouth
the link even includes reference to the software used for the comparison.
The test was conducted using UltraCompare, a standard tool for application comparison. The test used CherryOS 1.2 and PPC 0.4 Pre as the basis for comparison. The UltraCompare test works by running through every possible process of the application. The results show the matching number of bytes and gives a consensus on whether the core architectures of the two products are the Same, Similiar or Different. As you will see from the results below, CherryOS and PearPC are radically different products.
apparently running "diff pearPC.exe cherryOS.exe" is all you need to do.
ironically, the screenshot included on the page appears to me to be more evidence that they include similarities. something that, in the binary, is even more damning.
and no, the UltraCompare site shows no evidence that it can "[run] through every process of the application"
-- i am jack's amusing sig file
No, and this is partly what is wrong with America today.
Lawsuits are not about profit. They are about redressing wrongs. If someone hoses you over, the law says that you are entitled to be restored to the state you would be in if you were not hosed.
Punitive damages go a step further and (as the name implies) punish the wrongdoer for hosing you over. I believe this is where many folks get confused and think that lawsuits are all about making money (other than for lawyers). If punitive damages were paid into the U.S. Treasury (or state equivalent), it would fix a lot of ambulance-chasing that goes on today (of course, actual damages are still payable to the plaintif - they go to redress the tort that brought the parties to court in the first place).