Microsoft, Novell, and "Clone Product" Lawsuits
El_Oscuro writes "The MS/Novell deal specifically excludes patent protection for "clone products." In the agreement, a clone product is broadly defined as "a product (or major component thereof) of a Party that has the same or substantially the same features and functionality as a then-existing product (or major component thereof) of the other Party ... and that has the same or substantially the same user interface, or implements all or substantially all of the Application Programming Interfaces of the Prior Product." The text of the clone product definition subsections is very cumbersome to read, but it specifically mentions OpenOffice, Wine, and OpenXchange by name without asserting that they are necessarily clone products."
Novell open source users are not protected from Microsoft's vaporware patent lawsuits.
Functionality is the key. Linux products are dependable and do not crash so they are functionally different than any MS product.
Profanity - The sign of a small mind trying to express itself.
Windows was a clone product. (MAC/X-Windows)
Microsoft Exchange is a clone (sendmail)
DOS (CPM)
Microsoft does not invent, only "embrace, extend, extinguish".
I am the unwilling control for my Origin.
The section is vague at best. Hundreds of open source projects have "the same or substantially the same features and functionality as a then-existing product (or major component thereof) of [Microsoft] and that (a) has the same or substantially the same user interface, or (b) implements all or substantially all of the Application Programming Interfaces of the Prior Product."
Samba could be viewed as a clone product, but so could gedit (clone of notepad). Firefox might be a clone of Internet Explorer 7. What about totem? Looks an awful lot like Windows Media Player, at least the older versions. Nautilus behaves a lot like Windows Explorer, huh?
This section is stupid and ridiculous and is likely to get struck down by the first courtroom judge that looks at this thing as being too vaguely worded.
IANAL and this is not legal advice.
My blog
The more details come to light... the more I'm wondering what Novell got out of this deal.
I patent the numbers 0 and 1
A penny per usage
(patents for the numbers 2, letters F and U still pending)
Sounds like a good enough set of reasons to not support Suse Linux any more. Ubuntu anyone?
...Open Source isn't the only answer -- but it's almost always a better value than the alternatives...
Doesn't matter to me though, Xenomai wins in every way and it is not encumbered by any existing patents.
--jeffk++
ipv6 is my vpn
the word they're looking for is not "clone" but "competition". This is, therefore, a Very Special agreement indeed:
"We will not sue you for patent infringement as long as your products are not similar to ours."
My turnips listen for the soft cry of your love
IMHO the whole point of the effort on Microsoft's part was to thin the money-making distro herd.
1. Create the perception that there is an approved Linux distro. This is a requirement for bureacracy-bound businesses that have to check with Legal/PHB's before "purchasing" a Linux distro.
2. What better way to waste Novell's resources than create documents that protect nothing? It's a poorly run organization and this agreement is an excellent example of _exactly_ how poorly it is run. I'm sure there are great people that work at Novell, they just don't get to make strategic decisions. Novell is slowly circling the drain and Microsoft needs the perception of competition and cooperation to keep legislators pushing their agenda. http://finance.yahoo.com/q/ks?s=NOVL
3. One of Microsoft's goals is to capture Linux revenue. This, more than anything else will keep OSS at bay.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
I'm soft of totally confused looking for any relevance to anything here. Microsoft gave Novell $40M, and agreed not to sue Novell's customers, unless Novell's customers were using Novell's product (the wording of the exceptions seem to exclude anything that could possibly be in a distribution).
My question is, "What difference does the agreement make?"
M$ could possibly sue Novel, et.al., before the agreement was signed. Now, M$ is out $40M, and still could possibly sue Novel, et. al. The possibility of M$ winning such a lawsuit remains as remote as it was before. It appears that the $40M was simply the cost of a publicity stunt. Wouldn't another fake grassroots campaign have been more effective?
Aah, change is good. -- Rafiki
Yeah, but it ain't easy. -- Simba
X probably exercises a lot of memory, so have you ever tried to install a memory checker such as memtest86, reboot with it, and run it all night? It might catch memory errors that don't often show up under regular use. I don't know about the i810 driver, but if you experience problems when you do the exact same action (e.g. playing a 3-d game or something) then you might want to spend the energy to complain at your distribution maker that game Y always crashes or has weird stripes in 800x600 resolution with your kernel version and video card etc.
I'm as big a Linux fanboi as the next, but I would never claim that you're doing something wrong. That kind of behaviour (lockups and crashes) is simply unacceptable, I think everyone agrees. When you say X.org is still in its infancy I guess you refer to the version 7 split into modular system; do you mean you never had such lockups under a previous version? That might also be an important data point to tell in your bugreport.
As you said, you submit bug reports where possible: great. For other readers I'd just reiterate: don't expect anyone helping you out if you never send in a short formal bugreport with the details you (at your technical level) deem important. The authors of the software (X.org in this case) may have never tested it out in your exact configuration; PC hardware is very diverse. Complain to your distribution makers: they'll assess it and pass it on upstream (possibly after a long time; if you want instant results, hire somebody to solve it).
Try to see it from the X.org programmers' perspectives (no, I'm not one of them, I'm guessing here): if you receive a lot of similar, readable, not too ranty, detailed bug reports then maybe (if you have time) you can track and fix the issues. But you are not going to trawl general forums (like slashdot) to see if somebody complains "it doesn't work".
To be, or not to be: isn't that quite logical, Slashdot Beta?