Slashdot Mirror


Why Consider Linux Kernel Patent Risks?

chromatic writes "After the hoopla about OSRM's study of patent risks in the Linux kernel, I talked to Dan Ravicher, the patent attorney and free software afficionado who conducted the study. Contrary to my initial reaction, I've come to believe that the study is actually very valuable. Linux and Patent Risks on the O'Reilly Network explains why."

58 of 226 comments (clear)

  1. So.... by evan_th · · Score: 3, Insightful

    If somebody decides to sue Linux for copyright infringement, who defends it?

    1. Re:So.... by Kenja · · Score: 5, Funny
      "If somebody decides to sue Linux for copyright infringement, who defends it?"

      SCO? I thought they owned Linux.

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    2. Re:So.... by irokitt · · Score: 2, Insightful

      One would assume the FSF is in a position to help. If by Linux you mean individual distros, some of the larger ones are probably capable of beating off most attacks (that is, ones that aren't bankrolled by people like Microsoft).

      And don't forget that the free software community has a history of helping groups that fall under legal trouble (the aftermath of SCO is making free software users more aware of legal risks). So passing the hat around would also be an option. The worst cas is that Microsoft could simultaneously sue free software groups in different countries, over a multitude of different patents. That sort of attack would be very difficult to beat off.

      --
      If my answers frighten you, stop asking scary questions.
    3. Re:So.... by sloanster · · Score: 5, Insightful

      If somebody decides to sue Linux for copyright infringement, who defends it?

      I think you are a little confused, perhaps... When you say someone will "sue linux", exactly who do you mean is being sued? Novell? Linus Torvalds? IBM? Red Hat?

      Once you apply a bit of clear thinking, and decide who is being sued, the answer to your question will follow naturally.

    4. Re:So.... by InternationalCow · · Score: 2, Interesting

      I find this a very intriguing question although you might want to phrase it differently: whom to sue if a patent is infringed upon by the Linux kernel? In the cooperative development environment that is Linux, no-one really *owns* the kernel if I understand the GPL correctly. I think that is what has the microsofts of this world so worried - no single entity to attack and subdue. I would be most interested to see what a patent lawyer would come up with. I note that this issue is not mentioned in the article. Anyone?

      --
      ----- One learns to itch where one can scratch.
    5. Re:So.... by spacefrog · · Score: 4, Informative
      • If somebody decides to sue Linux for copyright infringement, who defends it?
      IBM, Apparently.
    6. Re:So.... by Bruce+Perens · · Score: 3, Insightful
      You can sue anyone. Indeed, lawsuits are generally brought against a list of defendants and "John Does 1 through 1000", so that more defendants can be added later. So, suing all known kernel mailing list subscribers would not be impossible.

      Bruce

    7. Re:So.... by killjoe · · Score: 2, Insightful

      If they sue you then you switch to BSD and they have wasted all their money. More people they sue the more money they have wasted.

      BTW in the history of the world nobody has ever been sued for actually using a product that infringes on a patent. NEVER EVER.

      You need to take a course or two in risk management. Getting paranoid about extrememly unlikely scenarios and changing your business practices to avoid unlikely events is just a "BadIdea"

      --
      evil is as evil does
    8. Re:So.... by Bruce+Perens · · Score: 3, Informative

      Well, in the U.S. it isn't necessary to figure out who is responsible for the infringement before you decide who to sue, because the patent title says that use is one of the infringing acts you can sue for. This is why there is even a question that users can be sued, we would just love to have a court rule that they can't be.Bruce

  2. Has anyone audited non-free OS's for patents? by ron_ivi · · Score: 5, Insightful
    I would still like to know if anyone's audited the source code for any of the proprietary OS's for patent violations.

    Seems Linux will be one of the safest kernels from a (patent point of view) to run, since it has had the most companies scouring it's source code looking for infringements.

    1. Re:Has anyone audited non-free OS's for patents? by Anonymous Coward · · Score: 2, Insightful
      So what happens if you buy a proprietary OS that infringes on someone's patent. I can think of a few possibilities.
      1. If your license also includes indemnification or insurance, your vendor might pay you (but AFAIK, noone actually does this, do they).
      2. Your vendor might be prohibitied from selling their OS, leaving you out in the cold. (at list with Linux you could hire people to code around the infringing parts)
      3. You get sued and have to license the patent.
      Sounds like you're better off with Linux that proprietary.
    2. Re:Has anyone audited non-free OS's for patents? by maximilln · · Score: 3, Funny

      Just like for viruses there's value to having diverse operating systems incase one of your systems gets shut down due to not only Viruses, but also IP-laws, vendors stopping support, etc.

      So lawyers are viruses?

      I'm not surprised...

      --
      +++ATHZ 99:5:80
    3. Re:Has anyone audited non-free OS's for patents? by static0verdrive · · Score: 2, Insightful

      I agree whole-heartedly. I have said the same thing in different words before; all these companies are worried about the validity of linux, but should they be a hell of a lot MORE worried about these closed-source, proprietary bastards that, if caught with pants down, could sink your whole ship of a business? It seems to me open source implies "NOTHING TO HIDE" in blaring, obvious letters.

      Now that we know M$ is attempting to undermine linux by training themselves rather than spewing FUD, ... oh, wait; there's no where for that argument to go because linux developers just keep spewing better software.

      --
      ========
      77 77 77 2e 6d 65 6c 76 69 6e 73 2e 63 6f 6d
    4. Re:Has anyone audited non-free OS's for patents? by Bruce+Perens · · Score: 2, Informative
      Because of the way patent law works, if you don't intend to license every patent you find, and that's insane because most of them are not inventions, it is best not to look.

      Bruce

    5. Re:Has anyone audited non-free OS's for patents? by Bruce+Perens · · Score: 4, Insightful
      Yet it seems customers (perhaps Daimler/Chrysler, since they're now sensitive to the issue), would start demanding that proprietary software they buy gets audited for IP rights.

      They could demand this, but what they would get would be indemnification or insurance. Their motivation is to reduce their legal risk, so either of these would be acceptable.

      You really can never complete a patent search. Because of the vagueness of patent claims, it is difficult to say conclusively that a patent can't be asserted against a particular body of code.

      Bruce

    6. Re:Has anyone audited non-free OS's for patents? by Bruce+Perens · · Score: 3, Informative
      In Microsoft's case, we know that they have offered to indemnify their customers regarding patent risk in their software. So, even if MS has something to hide, the customer is theoretically off of the hook. In practice, the customer is potentially in the position of having to sue Microsoft in order to get them to make good on their indemnity. Even the Federal Government doesn't have much luck at suing MS, so the customer can only hope that MS pays without a fight.

      Most other companies could not offer to pay their own indemnities, and many of them believe this is covered by their liability insurance when that may actually not be the case.

      So, I think it still turns out that code that is open for all to view is better.Bruce

    7. Re:Has anyone audited non-free OS's for patents? by Bruce+Perens · · Score: 2, Informative
      But, because of the open nature of the code, any infringements that do exist in the code would probably be moot, because the patent holders have not shown due diligence in protecting their patents

      You are talking about the Doctrine of Laches. Look it up on the web. Generally it takes a 6-year delay of prosecution, although it has been won for less and lost for more. It's not easy to win a laches case. You can lose your shirt while doing so.

      Bruce

  3. implied patent license by bollow+(a)+NoLockIn · · Score: 2, Interesting
    From the article

    Ravicher discovered that open-source-friendly companies (including IBM and HP) hold about 100 of those patents. Again, the likelihood that such a company would bring suit against someone using or distributing Linux is small, especially since those companies often distribute Linux themselves. (Legally, a company probably could, but it goes against the spirit of open source.)

    The assertion "legally, a company probably could" in the above statement is false. Even though it's primarily a copyright license, the GPL contains an implied patent license.

    --
    Under construction: swpat politics overview article
    1. Re:implied patent license by chromatic · · Score: 2, Insightful

      I think you're confusing the notion of having a valid case versus actually bringing a case. You don't have to have a good chance of winning to file a suit. You just have to be stupid, arrogant, or really unfriendly.

    2. Re:implied patent license by d_jedi · · Score: 3, Insightful

      It's only a patent license for those who *distribute* the GPLed software. Linux is still vulnerable to patents owned by any company that does not release a distribution (and AFAIK, IBM does not.. but it would be stupid for them to try to enforce their patents, given their investment in Linux).

      --
      I am the maverick of Slashdot
    3. Re:implied patent license by killmenow · · Score: 4, Informative

      Also, thanks to Groklaw, I learned about this thing called Promissory Estoppel that would pretty much stop them from bringing a patent suit at this point.

    4. Re:implied patent license by Bruce+Perens · · Score: 4, Informative
      To a great extent IBM has avoided distributing GPL software directly. We think this is because they don't like the patent terms of the GPL.

      Bruce

    5. Re:implied patent license by GoofyBoy · · Score: 2, Informative

      Huh?

      http://www10.software.ibm.com/developerworks/ope ns ource/linux390/linux-2.6.5-s390-06-april2004.shtml

      Click on the "Download" button and you have to agree to the GPL code.

      Section 7 on patents is there too.

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    6. Re:implied patent license by Richard_at_work · · Score: 2, Interesting

      This is an interesting one. Reading section 7 of the GPL on gnu.org seems to indicate that having a patent issue on the code DOES NOT excuse you from the obligations under the GPL (namely distribution of source code). Indeed, what it does indicate is that you STILL have to fulfil the source obligations under the GPL to those who you distribute it to (and the permission propagates down the chain).

      But reading it carefully, it seems to indicate that you are not giving a carte blanche license TO THAT CODE. The 'implied patent license' only applies to those YOU HAVE DISTRIBUTED TO (and on down the chain). This means that the linux kernel IBM has for download may be free from patent issues, but the copy on kernel.org and in redhats distribution may not be. I dont think that was an intention of this paragraph but after running it past a friendly lawyer (hey, dont hear that often do you? :) ) who agrees with me, it might be something that needs looking at.

      Also, another problem with the GPL is that it attempts to 'trump' any rulings by the legal courts. Paragraph 7 extends itself outside of patent issues and INCLUDES COURT JUDGEMENTS when it says that they do not excuse you from complying with the license. Personally, I think a court ruling that I cannot distribute the code (for example, my offices and actions are frozen by the court during a federal investigation) would superceed the lowly GPL in that case (indeed, as carrying out the obligation would land me in contempt of court and potentially with a criminal record for such).

      Just some food for thought.

  4. Don't tell Darl by antikarma · · Score: 5, Funny

    "The 283 patents that the kernel could infringe have all gone unchallenged so far."
    In other words- Sco doesn't know about them yet.

  5. Linus and patents by blogtim · · Score: 5, Informative
    Linux founder and leader Linus Torvalds has taken that approach. "Finding patent infringement has always been a responsibility of the patent holders," he said in a 2003 interview. "It is a fact that I do not encourage engineers to look up patent information
    Actually, I read an article in Wired maybe a year ago quoting Torvalds as saying that he personally avoids looking at patents because willful violation leads to triple damages. Better just to close your eyes and do whatever...
    --
    Visit Tim's Journal, yes?
    1. Re:Linus and patents by Bruce+Perens · · Score: 4, Informative
      Imagine if my lawyer does some research and finds out that my technology potentially violates several patents. And then I tell him, don't tell me, I want to be protected.

      This would be covered under attorney-client privilege. Neither you nor your attorney can be made to testify about what your attorney told you. However, what I tell you as a consultant rather than an attorney is not similarly protected. I have indeed told some customers that they should not see my findings because my findings were not favorable for a court case they were considering. What they didn't see, they would not have to testify about. They agreed, thanked me for being so careful regarding their interest, and happily paid me for a report I never delivered!

      In this case, if you know you are infringing, the amount of damages you may have to pay goes up by more than three times. That's how the law works. It sure isn't OSRM's fault.

      Bruce

    2. Re:Linus and patents by iabervon · · Score: 2, Insightful

      I wouldn't be surprised if someone actually challenged the triple damages law on the basis that it makes it undesireable for inventors to look at patents, and therefore that the system violates the patent office's constitutional mandate. Of course, it would probably not be argued in front of the present Supreme Court, since they didn't seem to go for a similar argument in Eldred v. Ashcroft.

  6. It's a MAD World!!! by grunt107 · · Score: 5, Insightful

    With the gloom of the patent infringement reports, the one bright spot is the Patent machines of IBM (and HP). It is doubtful that other major patent holders (MS) do not violate any of IBM/HP (and vice versa), so the threat of mutually assure destruction is the only seeming deterrent.

    Who are the commies in this scenario?

    1. Re:It's a MAD World!!! by misleb · · Score: 2, Funny

      Commies? The Linux advocates, of course :-)

      -matthew.

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    2. Re:It's a MAD World!!! by Bruce+Perens · · Score: 3, Informative
      It does not help that IBM, HP, and MS violate each others patents, because they are already cross-licensed with each other.

      They can't enforce their patents against each other except in unusual cases. MS contract with HP allows MS to enforce against HP in regard to specific free software, as we learned in the infamous memo, but that memo is all that we know of the MS-HP cross license. We do not know of any similar carve-out that would allow HP to enforce against Microsoft.

      Bruce

  7. But, if they do find someone to attack by Trizor · · Score: 2, Interesting

    If the point is negledgable they could get a compotent opinion form a patent lawyer that says they think the patent is bogus. Then they are an unknowing offender and only have to pay royalties. There are no royalties with OSS. Problem solved. But then again, they can't even find a target. Linux isn't one face, its many, unassociated, different corporations and organizations. Sue this!

    1. Re:But, if they do find someone to attack by chromatic · · Score: 2, Insightful

      Did you read the article? Your post is full of inaccuracies.

      Defending against a patent lawsuit is expensive and time-consuming. Sure, the courts throw out around half of all contested patents, but that means they uphold around half of all contested patents.

      Unwitting infringement does not mean that the patent is bogus, it means that you can show reasonably well that you did not know that you reinvented something someone else had patented.

      Where did you come up with the idea that patent damages include royalties?

      Where did you come up with the idea that because you can't sue everyone associated with Linux you can't sue anyone? That's completely false.

  8. Re:Linus. by Anonymous Coward · · Score: 3, Funny

    You mean the mean, pissed off, angry horde of IBM, lawyers that the companies would likely offer to Linus in order to save their own business model?

    IBM lawyers vs. MS lawyers

    THUNDERDOME!

  9. Re:Linus. by MarsDefenseMinister · · Score: 4, Informative

    Linus owns the trademark to the kernel, but not the copyright, except for the portions he wrote himself. As far as I know, Linux does not require copyright assignment as a condition for code inclusion.

    Copyright != Patent != Trademark.

    --
    No weapon in the arsenals of the world is so formidable as the will and moral courage of free men.-Ronald Reagan
  10. Re:Software Patents vs. Free Speech by OwnedByTwoCats · · Score: 4, Informative

    It seems to me that an individual with ordinary skill in the art of developing software, coming up with a patented solution to a problem, poses as much a problem for the owner of a patent as it does for the individual developer.

    One of the requirements for granting a patent is that it describe an invention or process that is nonobvious to one skilled in the art...

  11. Re:Linus. by Anonymous Coward · · Score: 4, Funny
    Two claimants enter, one claimant leaves!

  12. Re:Linus. by October_30th · · Score: 2, Funny
    angry horde of IBM

    What makes you think that the IBM lawyers would be angry?

    I think they'd be more like borgs. Resistance is futile.

    --
    The owls are not what they seem
  13. Big F'in Blue by Hanna's+Goblin+Toys · · Score: 2, Interesting
    Worse yet, though a project may have pedigreed and documented prior art that could easily convince a court to overturn a patent, the cost of such an action is out of reach for most developers -- and many companies.


    The flipside to this is that frivolous, non-innovative patents can be attacked without an infringment case - out of the blue - as restraint of trade, provided you have the cash to do so. If someone were to patent something obvious, let's say ordering a list of files by date, anyone can file a restraint of trade suit agianst the patent holder.

    Linux's new backer, Big Blue, does have the lawyer army required to attack frivolous patents. The patent war may mean the true end of non-business-backed Linux. It also may mean the doom of companies that are senselessly patenting other people's inventions, and future security for Linux.
  14. Re:Would it be illegal? by ron_ivi · · Score: 4, Informative
    " First you would have to have the source code. I suppose it could be de-compiled? I don't know how that works. Are there laws against that?"

    Even proprietary vendors make their source code available to important customers "to conduct security reviews of the products" - why shouldn't they do the same for Intellectual Property Rights?

    Furthermore, you could have third-party auditing companies provide that service in the same way they audit other confidential information such as company finances.

  15. Re:Software Patents vs. Free Speech by maximilln · · Score: 4, Funny

    so AFAIK software patents have the possibility of stopping the business end of linux, but can't fundamentally be a threat to its existence?

    The fact that Linux users continue to use Linux, which is obviously an illegal rip off of proprietary systems, is analogous to those 12 year olds who continue to trade mp3s even after we explicitly told them that doing so was a felony. We will continue to implement hardware based DRM, we will deny a license for anything but the MS boot block, and we will continue to increase funding for the anti-piracy arm of the FBI so that we can raise multinational efforts to hunt down and prosecute, to the fullest extent of the law, anyone who continues to write this so-called "open source" software. We will use any and all available means, including invocation of the PATRIOT Act, to ensure that these hardened criminals do the maximum possible time behind bars as an example to our youth. We are continuing to lobby Congress for "three strikes and you're out" laws which make repeated "open source" violations a mandatory felony. The distribution of such "open source" code is also considered a felony. Distributing 1 kb of hardened binary code, based on open source, has a mandatory minimum of 5 years in prison and distributing more than 30 g of "open source" source code carries a mandatory minimum of 10 years in prison with up to a $50,000 fine.

    With your help, and the help of other concerned citizens like yourself, we will eradicate "open source" houses from our neighborhoods. We will hunt down "open source" dealers. We will prevent our children from using "open source" code. We have already implemented measures to make the distribution of "open source" code with 500 meters of a school an automatic felony, no matter what amount or who the distribution is to.

    'Nuff said...

    --
    +++ATHZ 99:5:80
  16. Uh... by sjvn · · Score: 2, Insightful

    >I would still like to know if anyone's audited the source code for any of the proprietary OS's for patent violations.

    If they could be publicly audited for patent violations they'd be open-source, yes?

    Steven

  17. The law is loaded. by Skiron · · Score: 2, Insightful

    Patents are given out willy-nilly as we know from 'M$ 3000 patents' a year pledge.

    Then to find a programmer 'unwittingly' coded something similar that treads on the patents' toes, it is beyond the financial means of the coder to say 'Hey, I done that 5 years ago!' in a court of law.

    The law is an ass.

  18. Re:Would it be illegal? by chromatic · · Score: 2, Informative

    One problem with the U. S. Patent system is that looking for patent violations in your source code makes you liable for charges of willful infringement. I'd be surprised if any companies actually did this.

  19. High risk for any company suing... by bani · · Score: 3, Insightful

    the rewards of 'enforcing' a patent against the linux kernel would have to outweigh the risks of being a permanent pariah.

    given the fact that so many patents are revoked upon challenge, the fact that many patents are trivially circumvented via minor changes, and the fact that attacking one company over a 'patent infringement' in kernel code is in effect attacking millions of end users worldwide, the risk is extremely high and the rewards extremely low.

    to me it seems rather unlikely any company would attempt this, unless they have nothing to lose (eg SCO).

  20. Re:patents free for private use ? by Meowing · · Score: 4, Informative
    Yes, private use and research often qualify for royalty-free use of a patent, but beware that these exemptions are very narrow. More information here.

    Also, the international treaties covering patents are still evolving (there's a bunch of 'em -- not just WIPO but PLT, PCT, TRIPS and more I'm sure I'm forgetting), so it's still necessary to check out the local laws.

  21. Re:Uh... by pandrijeczko · · Score: 2, Funny

    I see Mr Ballmer's joined us again this evening...

    --
    Gentoo Linux - another day, another USE flag.
  22. An observation based on the SCO stupidity... by pandrijeczko · · Score: 2, Interesting
    Correct me if I am wrong but all the SCO vs Linux stuff has now died away.

    The Linux kernel can mount devices formatted under a whole heap of filesystems including System V, UNIXWare and other UNIX-type partitions. Presumably, since SCO holds the UNIX name, SCO also holds the patents to some of these filesystems.

    So why didn't SCO carry out legal action based on patent infringement within the Linux kernel for building in that filesystem support?

    Isn't this exactly the same type of attack we would expect from Microsoft for FAT, NTFS & Joliet support in the kernel?

    Couldn't this be a sign that attacking Linux on patents might therefore simply not be worth it based on the money & time that would be involved?

    Any comments?

    --
    Gentoo Linux - another day, another USE flag.
    1. Re:An observation based on the SCO stupidity... by flossie · · Score: 4, Insightful
      Couldn't this be a sign that attacking Linux on patents might therefore simply not be worth it based on the money & time that would be involved?

      Unfortunately, I think it is more likely that this is a sign that companies like Microsoft don't want to attack the competition with patents until they have succeeded in getting US-style patent law in force around the world.

      At the moment, it is very difficult to convince politicians how harmful software patents can be because most of the damage is theoretical. If Microsoft were to start suffocating Linux with patent threats prematurely, it would be much harder for them to get software patents introduced in Europe and Asia, thus reducing the effectiveness of their eventual attack.

    2. Re:An observation based on the SCO stupidity... by 13Echo · · Score: 2, Interesting

      "The Open Group" holds the UNIX name, not SCO. SCO owns some UNIX code (System V) but does not own the UNIX name.

      SCO could potentially have patents on some of their filesystem stuff, just as Microsoft has patents on certain parts of FAT. FAT's patent was granted in 1996, but there are at least three instances of prior art that have come up that seriously put the patent into question. Before Microsoft's recent attempts, they have never demanded any license over the use of FAT. On the other hand, it's very simple to exclude support for any filesystem from a built Linux kernel (and thus from the source). It's not really something that I think that most people have to worry about. If it becomes an issue, then it can be removed... It's a shame, really, because people will need a common filesystem between Windows and other operating systems. It doesn't matter too much though, because people are making stuff like EXT2/3 support drivers for Windows anyway. It might make Linux migration more difficult for some, but it's just something we'll have to accept.

  23. This is the most important quote from the article by Anonymous Coward · · Score: 2, Insightful

    Though many developers prefer to ignore patents, the current laws (at least in the U.S.) provide minimal legal defense for unwitting infringements. Worse yet, though a project may have pedigreed and documented prior art that could easily convince a court to overturn a patent, the cost of such an action is out of reach for most developers -- and many companies.

    Microsoft knows this. It is why they are filing 10 patents a day (reported on Slashdot before - you look it up). They have, rather correctly in my opinion, identified a profound weakness in the system and are hell-bent to use it to crush the opposition.

    They don't care whether the new patents they file are legal or ethical, all they care about is a premise to drag competitors into court and bleed them so dry that they are no longer a threat. Most of the patents they are filing may eventually be struck down in court either because they are trivial or because of prior art; it doesn't matter. They know it doesn't matter! In the end, all that matters is that they become the only company allowed to write any new software.

  24. Maybe less dangerous than we think... by earthforce_1 · · Score: 4, Insightful

    The more patent heavy corporations that have vested interest in FOSS, the better. This way, if a FOSS unfriendly company decides to launch a patent attack that would be damaging to the bottom line of FOSS friendly companies (IBM, HP, Novell) then it is all the more likely that the attacker will be found in violation of somebody else's patents. We have a MAD (Mutually Assured Destruction) scenario, and the attacker will be forced to back down. Aside from a FOSS patent fund, the best defence is to have as many patent heavy corporate friends with a vested interest in the success of FOSS as possible.

    --
    My rights don't need management.
    1. Re:Maybe less dangerous than we think... by killjoe · · Score: 2, Interesting

      This is the wrong way to look at it IMHO. We need to plan for what WE are going to do WHEN ms starts suing people.

      We need to organize now so we can start boycotting MS products and services, protesting at MS locations, programming our servers to reject traffic from MS, and fighting their FUD with counter FUD (yes FUD we have to fight fire with fire), filing countersuits or what have you.

      Plans need to be made, people need to get organized. Would a daily protest in redmond work? Would countersuits by individuals and small companies work? Would the press publish articles that critize MS? Can we really organize a boycott of MS hardware, software and services on a wide scale? Where do we discuss these and other strategies?

      I don't think we can presume all these large companies are going to come to the aid of OSS. They might (so far they have) but you have to plan for the eventuality that they won't.

      What are YOU going to do when MS starts their war for real? That's the question.

      --
      evil is as evil does
  25. Re:Linus. by Dogtanian · · Score: 2, Informative

    As far a I know, MySQL is also offered with GPL licensing.

    It is offered under GPL *and* non-GPL licenses. Which was *exactly* the reason I used it as an example.

    (Before I go on, bear in mind that IANAL). MySQL AB own the copyright to MySQL (AFAIK); thus they can release it under the GPL. All changes made to the GPL-licensed version are thus also GPL, and, unless all the authors of the new code get together with MySQL AB and come to an agreement, the branch of the GPL licensed version is GPL-only.

    However, MySQL AB retain the right to the original version they wrote (and all branches that exclusively include their code, I'd guess); thus they can offer it under a non-GPL license.

    Now, re: Linux. Let's assume that Linus doesn't own copyright on anything he didn't write. Unless all the authors (i.e. copyright owners) of a particular branch of the kernel agree, that kernel can only be released under the GPL. However, if, someday in the future, Linus received all the copyrights, he would have the copyright for the whole kernel and thus the right to offer Linux under a non-GPL license.

    This won't happen, of course- too many people own the copyrights- but if Linus had insisted from the start that he (or someone) was assigned the copyright to all the code in the kernel, then, even if that code had previously been GPLed, that person would have the right to offer a non-GPL version of Linux.

    This would not prevent use of the GPL license, but it *would* allow people to obtain Linux without the GPL.

    This is all academic, obviously. It won't happen, because too many people own the Linux kernel now to get together and agree to let this happen.

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  26. linux == can of worms == MAD by mabhatter654 · · Score: 2, Insightful
    Linux doesn't look because it provides him with some protection...without willing intent concequences are less. Also, at the time linux was written, Software patents were not valid in Europe..so again he wasn't breaking ANY laws where he lived.


    The other reason for not looking is that he wouldn't learn anything anyway. Most software patents [except for IBMs] are so vague that viewing the patent would only cause you troble...because most don't have ACTUAL implementaion...just "works-like-this". What ever implementations they DO have are locked up n copyright where nobody could ever see. That leaves many options for different intrepetations...look how many mousetraps are patented [versus 1 mouse catching device] Also, patents are invalid if the idea was published ANYWHERE prior to being patented.


    That last one is where MAD comes in. I'd bet a great many things were in Linux and OSS LONG before they were patented...too many to count. Remember, OSS is published INSTANTLY! Type your idea up and post a working model on sourceforge and it can't legally be patented...ever! Any upstart company trying to sic the patent lawyers on Linus would end up with all of OSS brought into court to start invalidating patents...and OSS goes Way back before software patents were even Legal! No company in their ritht mind [SCO excluded!] would open that can of worms... After the first 100 or so invalid software patents, the Judges would declare them all void and tell the PTO to stop creating junk! That would ruin the whole little game.

    1. Re:linux == can of worms == MAD by Doomdark · · Score: 2, Interesting
      Also, patents are invalid if the idea was published ANYWHERE prior to being patented.

      Nope. In US there's the 1 year time period after publishing during which one can file patent applications; obviously as long as applicant published the invention (built something that implements the invention).

      There really should be a Slashdot Patent FAQ; this same claim has been refuted a number of times.

      For purposes of Open Sourcing things this doesn't have much effect, except that the author can both Open Source something AND patent couple of "inventions" contained therein... :-)

      --
      I like paying taxes. With them I buy civilization -- Oliver Wendell Holmes
  27. Re:Linus. by Dogtanian · · Score: 2, Insightful

    When the FSF was having one of its funny turns and was proposing changes to the GPL that Linus was unhappy with, he stripped the "or at your option any later version" phrase from the licence

    Whoah... I never knew that. I remember noting that clause at one point and thinking it seemed pretty risky. I also remember thinking that, if I'd been working on something I intended GPLing at the time, I'd probably want to omit it (or replace it with "or at *my* option any later version"; but that creates problems with the chain of responsibility, since which version applies to other people's GPLed changes?).

    It appears that great minds think alike. Or, more likely, it didn't take a genius to figure out the problem with that clause; essentially "do I trust the FSF that much?".

    BTW, you said pretty much what I said; the only way to license the kernel on a non-GPL basis is to get *every* contributor to agree, which won't happen.

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  28. Why proprietary software is better... by russotto · · Score: 3, Interesting

    ...for the patent issue: Open Source's usual strength is its weakness here. Since anyone can look at the source, anyone -- including hostile IP companies -- can fairly easily find infringing code. With a proprietary OS, the patent-holder first has to reverse-engineer the code to find the infringement. Which isn't so easy.

    As for the claim above that no one has sued an end user: nonsense, of course. SCO has, for one. And one company was even successfully sued for a program which did not embody or use a patented process or device, but simply wrote one bit of data that, when inserted into another device, would cause it to execute the patented process in a manner violating the license granted to the manufacturer of the second device.