Slashdot Mirror


Kororaa Accused of Violating GPL

AlanS2002 writes "The Kororaa Project, a pre-configured binary install method for Gentoo Linux which bundles nVidia's and ATI binary drivers in its Kororaa Xgl Live CD , has put its Live CD on hold after being accused of violating the GPL. The issue appears to be the distribution of the Linux Kernel and nVidia's/ATI binary drivers together. When the binary drivers are built the GPL'ed code is included in the binary result, which is a violation."

25 of 843 comments (clear)

  1. Yep. by Anonymous Coward · · Score: 4, Insightful

    This is one example of why the GPL is a terrible license. People are trying to add useful things to the Linux kernel so more people use it and your license is restricting it. Use a BSD style license if you want to distribute your code open source.

  2. What? by tomstdenis · · Score: 4, Insightful

    The drivers aren't GPL though and they don't include GPL code. They merely are compatible with GPL code. This is like saying my source files are GPLed because GCC can parse them. Or this webpage is MPLed because Mozilla can read it, etc...

    Just because the kernel can load your module doesn't mean your modules is GPLed. The way I understand the GPL is anything you derive from GPL code must be open source and what not. The drivers are proprietary and just happen to be compatible with GPL code.

    --
    Someday, I'll have a real sig.
  3. Aggregation is not linking! by Morgaine · · Score: 5, Insightful

    Aggregation of components is not the same think as linking, the FSF is totally clear about that. So both the GPL code and the binary code can be present together on the same medium, not linked.

    It's only when the CD is booted and the drivers loaded that a runtime image containing the binary modules linked with the kernel is created, and not before.

    Distributing an aggregation is perfectly legit, according to the guidelines for GPL v2. (Dunno about v3).

    --
    "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
    1. Re:Aggregation is not linking! by ebooher · · Score: 4, Informative
      Perhaps, but the binary module is compiled by linking against the kernel headers, and it includes shim code which may (or may not) be derived from the kernel. This would mean that the compiled binary module (which he is distributing) could therefore be derived from the kernel, and thus would need to be distributed under the terms of the GPL.

      According to information that the originator of Kororaa received from NVidia while investigating this matter, this is not true.

      The NVIDIA kernel module consists of two pieces: a binary-only portion and a kernel interface layer (aka the "shim"). The binary-only portion is not Linux-specific (the same code is used on Windows, Solaris, etc), and does not include any Linux kernel header files when it is built. The shim is provided in source code form with the driver package, and this is the piece that is compiled for your version and configuration of the Linux kernel. The shim is the only piece that references Linux kernel data structures or macros, and only does so to the extent that is needed to provide the functionality of a modern graphics driver. After the shim is compiled, it is linked with the binary-only portion, to produce the final NVIDIA kernel module.

      NVidia states that the binary is the same binary they use in all Systems. Be they Linux, BSD, Windows, or Bob's Unknown Mini-OS. The "shim" is the glue code they write that is OS specific that makes calls into the binary.

      --
      "Genius may shine aloof and alone, like a star, but goodness is social, and it takes two men and God to make a Brother."
  4. Re:All the more reason... by Poppler · · Score: 5, Insightful

    I thought [the GPL] was supposed to make things simpler, not have all of these caveats and 'gotchas'.

    You are confused. The GPL is designed to keep software big-F Free. The "caveats and 'gotchas'" are very much the point.

    --
    What's the ugliest part of your body? Some say your nose, some say your toes, but I think it's your mind. -Zappa
  5. It all depends by robla · · Score: 4, Insightful

    ...on who sent the email as to whether or not this is truly a significant event. While the person emailing may have a point (IANAL, so I dunno, the devil is in the messy details), it's a little melodramatic to make a big fuss out of this unless the person making the complaint is a copyright holder in the kernel and is issuing a cease and desist.

  6. Re:tainted kernel by tomstdenis · · Score: 4, Informative

    It only taints the kernel if you load the module. The kernel itself [the bzImage] is entirely based on GPL code.

    So don't autoload the drivers and the kernel will not load with a tainted status. /me shakes head...

    Tom

    --
    Someday, I'll have a real sig.
  7. Oh no!!! by Duncan3 · · Score: 4, Insightful

    Someone made Linux easy to install...

    KILL KILL KILL!!! STOP THEM!!!

    Seriously, they put linkable drivers on a CD... That's 100% OK.

    Stop trying to stop Linux you Microsoft plant, nice try tho.

    --
    - Adam L. Beberg - The Cosm Project - http://www.mithral.com/
  8. I spit by fishbowl · · Score: 4, Insightful

    There really isn't any fun, having to take a distro that leaves you with an 80x25 console, or a 640x480 X desktop (and I feel lucky sometimes to have EITHER of these work correctly), and from there, find and download drivers for NV or ATI, and build and boot a kernel that works with what was otherwise a working live system.

    This is really not a reasonable thing to expect from a user, not even from a user like me who has been running linux since 0.99pl1.

    --
    -fb Everything not expressly forbidden is now mandatory.
  9. What a prick by linvir · · Score: 5, Insightful
    Sounds like the sort of guy who sends a letter to have the local skatepark closed down when he notices that its disabled access is lacking.

    The most infuriating thing is how he goes for the puppy angle with this bullshit:

    this distribution goes against the open source spirit of linux
    The 'open source spirit of Linux' is that Open Source is supposed to enable people to stop worrying about this licensing crap. If nVidia and ATI aren't complaining, there shouldn't be an issue on our side.

    And for the most part there isn't. Which is why it's even more sad that he's actually caving to this:

    As such, the Live CD has been put on hold, until I can sort this out. If I cannot sort this out I will be forced to cease work on the Xgl Live CD.
    My overall opinion is that this Koraraa guy ought to grow a pair and wait to see what the non-basement-dwelling grownups have to say about his distro's licensing.
  10. Why not wait to see if this is an issue? by khasim · · Score: 4, Interesting

    Before you go on about how evil the GPL is, why not wait until there is some clarification on the issue.

    So far, an un-identified person sent an email to someone distributing a Live CD making certain claims.

    As far as I can see, no one has said whether that person has any code of his/her own in that Linux distribution. Nor has anyone who would be able to say one way or the other been quoted.

    Personally, I'd wait until Linus or ATI said that this was wrong before going off on how evil the GPL is.

  11. One man's "useful" is another man's "treacherous. by Kadin2048 · · Score: 5, Insightful

    Saying they're trying to add "useful things" to the kernel is a bit of a judgement call. You might think that adding proprietary drivers is useful, but a lot of people would disagree.

    The GPL is designed to prohibit this for a reason, and it's not because the FSF people enjoy making people's lives difficult, it's to keep Linux and the kernel from becoming dependent on proprietary binary lumps. If you want to taint your kernel by adding proprietary modules, more power to you, but you can't redistribute the result. Every user has to add the tainted bits in themselves.

    If every distro could just use the nvidia binary drivers, maybe the people working on the free "nv" driver just wouldn't bother. And then one day nvidia decides (because they suddenly become evil / get bought by Microsoft / whatever) to pull the rug out and cease development of the drivers. A few well-placed cancelled projects could set an operating system years behind the competition.

    The GPL attempts to ensure that a basic Linux system is at least functional without proprietary add-ons, so that it can't become the hostage of someone who controls a lump of code that everyone has gotten used to depending on.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  12. You've got the dependency graph wrong by Morgaine · · Score: 5, Informative

    The nVidia "shim" is licensed under the GPL and is copyright nVidia --- this means that it's perfectly legal to compile the shim against the GPL kernel. At the same time, nVidia is free to do whatever they want with the shim, and its license is immaterial to them at that point because they hold its copyright. The GPL has no say over what else the copyright owner can do with kernel-linked code, the only thing that's mandatory is that it's GPL'd, and it is. For example, it's very common for copyright holders to dual-license their own GPL'd code for commercial and highly proprietary use.

    Well, what nVidia chose to do in this case is to link the shim with their binary driver, and they're perfectly entitled to do that, by their copyright. Furthermore, since the shim and the binary driver are separate components from the kernel, they can certainly be shipped on the same CD as GPL components, as long as the binary code is not linked to the kernel. And it's not.

    So you see, by virtue of being the copyright holders of the shim and GPL'ing it, nVidia easily comply with the requirements of the GPL but aren't constrained in what else they do with it.

    If the binary module were linked against the kernel then you'd be right, but it's not. At no point in time did the binary module even get a sniff of the kernel, and it's shipped without knowing anything about it, nor viceversa.

    Yes, the dependency is contrived, but that's how the GPL forced them to rearrange their code dependency graph in order to stay on the good side of the GPL's guidelines.

    --
    "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
  13. No other options. by Kadin2048 · · Score: 4, Insightful

    all those suckers that bought NVidia or ATI video hardware

    Just out of curiosity, who are the non-suckers? The people who bought video hardware from ... who, exactly?

    3Dlabs doesn't make GPUs anymore, 3dfx got bought by NVidia, and XGI is gone. That leaves ATI, NVidia, Matrox, and Intel making GPUs. Does Matrox or Intel release source code to their drivers? (Is Matrox even still in the consumer graphics card business?) Who else is there? ATI and NVidia basically have the market for aftermarket cards cornered, to the best of my knowledge, and in both cases their drivers are closed-source. There really aren't any other options for most people.

    Personally I'd say go with NVidia, because they seem markedly less evil and their binary drivers seem to suck less, but that doesn't mean I'm happy about it.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  14. Re:All the more reason... by computerjunkie · · Score: 4, Insightful

    Have you ever read a standard EULA? The GPL is simple by comparison.

  15. Re:Whaaa? by mrsbrisby · · Score: 4, Insightful

    No, that's blatently wrong. OpenWRT includes the closed source BroadComm network driver

    If OpenWRT is distributing a Linux kernel with closed-source software linked into it, then yes, they are violating the GPL.

    and RedHat Enterprise includes lots of Redhat only software that isn't GPL.

    As far as I know, RHEL doesn't allow their trademark to be redistributed. That's a very different thing.

    Now, if you created your own custom kernel in order to make the binary drivers work, but then didn't include the source code for that, I would agree with you. But they didn't modify the kernel at all. They just compiled kernel modules.

    But the kernel modules are based on the Linux kernel. They use hidden magical interfaces. They don't necessarily make the modules GPL (says Linus), but that doesn't mean the resulting linked modules can be redistributed.

    If the drivers themselves were "Derived works" then that would prohibit distribution. However, that would also prevent people from using them at all and require ATI and nVidia open sourced the drivers. This is not the case, though. The drivers contain a GPL kernel interface and a binary only driver. The kernel interface that the ATI and nVidia drivers use is the derived work, and is opensource. You can get it in the respective packages from ATI and nVidia's websites.

    You're confused. The GPL isn't a usage-license, it's a redistribution license. You're free to download ATI or NVidia's copyrighted work (as they say- that's their distribution) and compile and link them into your kernel. You cannot redistribute your binary modules, or your built kernel with them, because you cannot satisfy the requirement of the GPL that says you need to be able to provide source code for those things.

  16. Re:tainted kernel by idonthack · · Score: 4, Insightful
    just remove the evil binary-only drivers and all is well.
    Except XGL is Kororaa's main feature (in fact, the only reason for the LiveCD), and that won't run without those drivers. If they take the drivers out they might as well just not do it.
    --
    Why is it that when you believe something it's an opinion, but when I believe something it's a manifesto?
  17. Re:All the more reason... by Tet · · Score: 5, Insightful
    This hurts Linux adoption big time.

    Thus speaks the voice of one who sees widespread adoption of Linux as a goal. Others see the creation of a free operating system as the goal instead. The two aren't mutually exclusive, but nor do they go hand in hand. I would rather see Linux remain a niche OS than sacrifice my principles to chase market share. Of course, I'd like to see Linux gain widespread adoption as well. But if it came to a choice between the two, I'll stick with what I believe to be right.

    --
    "The invisible and the non-existent look very much alike." -- Delos B. McKown
  18. A counter-argument by xenocide2 · · Score: 4, Informative

    Does anyone besides open source zealots care about open drivers? I think so. Perhaps if Nvidia and ATi had open sourced their drivers, Xgl wouldn't have taken so long to exist (Xgl requires a certain level of driver support, and aiglx even more so). I'm pretty sure you'd have liked this just as much 4 years ago, when I first saw people talking about things like openGL accellerated gtk widgets, and otherwise imagining how to use 3d to its best. But 4 years ago, you were writing off a large group of people by doing that.

    Furthermore, installing drivers for your ethernet, cd drive, etc is very simple on linux, because the drivers are open source and in kernel. Attempting to maintain a glue between the kernel and your driver is painful and prone to failure; unlike in tree drivers, when someone else breaks code you depended on, you have to fix it, not them. Recall that nvidia's nforce2 boards are better supported in the kernel than by nVidia itself! With no documents to support them in their efforts, even. I hear they even now recommend the reverse engineered driver over their own, but don't distribute or improve, oddly. If nvidia's drivers were GPL'd, installing them would be as simple as installing anything else.

    It's pretty naive to think that their IP is so valuable that the source code would disclose it any more than the underlying binary code does. Their IP is already in jeopardy by distributing the software. One of the many reasons I suspect they have no intention of participating in OSS is that there's a number of speed over quality decisions written into it that would be exposed, perhaps even application specific optimizations. While this could be neat to have optimized drivers on a per game basis, this is never disclosed to the public (and when revealed sparks not applause but public humiliation). Furthermore, it means that optimizations are done on their terms, not the public's. Any application specific optimizations are given only to a specific application, with no cross over improvement in other applications, or the ability to make the change. If NVIDIA really wanted to share their drivers with the public and gain all the benefits often touted, they'd stop pointing at other people's IP they own and begin to change it. They haven't, and they won't. What nefarious secrets lie within? Perhaps just a case of "this stuff is really hard, and we don't do it very well?"

    Just a thought -- if you dislike the open source spirit as embodied by the GPL, why not do something productive about it, like make a liveCD based on BSD running Xgl. There's nvidia drivers for BSD too, ya know. And for all the talk about pressuring vendors to open their code, they have no qualms about giving it away reguardless with no expectation of anything in return. Linux needs to focus on being Linux, not beating Redmond.

    The good news is that I suspect the person who wrote to Kororaa doesn't actually have any basis for the claim. While nvidia's legality has been on shady grounds, the message published doesn't provide any insightful evidence in either direction. Anyone seriously familiar with the kernel and binary objects should be familiar with the recurring arguments and whatnot. It's clear to me that if the drivers themselves were in violation, nvidia would have been sued some time ago.

    --
    I Browse at +4 Flamebait

    Open Source Sysadmin

  19. Re:tainted kernel by swillden · · Score: 4, Informative

    So don't autoload the drivers and the kernel will not load with a tainted status.

    That doesn't make any difference.

    Copyright law prohibits the creation of derived works without permission, and the GPL does not grant that permission unless you distribute source. So the question boils down to "Are the binary-only modules derivative works under the law?".

    The answer is: yes and no. The modules come from ATI and NVidia in two parts: a binary-only part that contains all of the interesting code, and some "glue code" that is distributed in source. Both parts have liberal redistribution permissions, which makes the GPL happy, so the big issue is source.

    The argument is that the core, binary-only components of their drivers are not derived works of Linux, since they contain no Linux code (not even any headers) and I think they even claim that the same binaries are used on other platforms and wasn't developed specifically for Linux, at least in the beginning. The glue code that they distribute that wraps the binary-only component is clearly a derived work of Linux, but they distribute the source to that.

    When a user compiles the glue code and links it with the binary-only component to produce a kernel module, the result is a derived work of the GPL'd Linux kernel. Note that I didn't say "and loads it into a running kernel". That's not really relevant. Technically, it's somewhat unclear whether the GPL gives users the right to create otherwise unauthorized derived works, but the general interpretation (including by the FSF) is that people can do whatever they like, and it's only when they start distributing that the question of whether or not the GPL has granted them permission becomes important.

    When someone takes that same compiled glue plus binary module and distributes them, they're distributing a derived work of Linux, without complying with the terms of the GPL, and therefore without permission to distribute under copyright law.

    I think it's quite clear that Kororaa cannot do this without infringing Linux copyrights. The only way they can justify it is if they can argue that the binary kernel modules (glue + core binaries) are not, under the law, derived works of Linux. That seems like a tough one, but IANAL, so maybe it's possible.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  20. Re:One man's "useful" is another man's "treacherou by Alef · · Score: 5, Insightful
    If you want to taint your kernel by adding proprietary modules, more power to you, but you can't redistribute the result. Every user has to add the tainted bits in themselves.

    What if I distribute the kernel with instructions on how to add add proprietary module? Would that be OK?
    What if I then distrubute the kernel with a helper script that downloads the modules when the user runs it?
    What if these modules would reside on the same CD as the kernel, and the script simply copies them from a specific directory instead of copying them from a server?
    What if I also include a helper script that automatically installs the modules when the user runs it?
    And what if this script is a boot script?

    But, oh wait, that sounds an awful lot like what kororaa does already...? Where did I cross the line?

  21. Re:There's more restricition in BSD by Ded+Bob · · Score: 4, Insightful

    After all, it's the BSD licence that restricts me from seeing the Nokia OS source code.

    No. It is the Nokia license that restricts you. The BSD license does not contain the restriction.

  22. Re:It wouldn't be Linux anymore. by mrchaotica · · Score: 4, Insightful
    From a hardware vendor's perspective, stable binary interfaces are nirvana.

    It means that they can write their drivers to a stable interface and not have to worry about every single recompile of the kernel invalidating their work, which in turn means that they have lower support cost.
    That entire argument is bullshit.

    What would really be nirvana would be for an entire community of willing volunteers to write their driver for free, which could happen if the vendor would just release some damn specs! Then the support cost wouldn't just be lower, it would be zero because the community would be supporting itself!

    Besides, "trade secrets" are not necessary for a hardware company to succeed anyway. Look at all the hardware that does have Free drivers: CPUs, mass storage devices, sound cards, network cards, etc. Those don't have any "trade secrets" that prevent drivers from being written, and there is absolutely no reason for video cards (and wireless chips) to be any different!
    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  23. burninating some karma... by Penguin+Follower · · Score: 4, Insightful

    OK, I've got karma to burn.

    I just happen to enjoy playing Doom3 and UT 2004. What card other than an ATI or Nvidia is going to pull that off and has open source drivers?

    You're using open source drivers, but then you go and (censored) it up by using a closed source game.

    Actually, I use Nvidia's binary driver. :P

    I was just waiting for one of you open source utopians to express the "closed source games are evil" opinion. Let's face it, while there have been some good open source games released, 99% of the games in the world are closed source, and some of them I have deemed are worth my time and money spent. The game industry wouldn't truly exist without the profit motive, and in general they see the need to keep things closed to ensure that.

    Games don't need to be closed source to make money. That's what you're probably thinking at the moment. The only system that would work that I can think of is if a source CD was included in the same box as the binary CD. Obviously, you couldn't post the source on a publicly accessible server, for people who can would download the source and compile the game - never giving the company one dollar.

    Things to keep in mind:

    • A business is a profiteering venture (we're not talking non-profit here).
    • It is in the business's best interest to protect any proprietary technology. Since we all hate software patents (and dislike copyright), the only protection left is closed source.
  24. A Shame, Either Way You Look At It by larzluv · · Score: 4, Insightful
    The following GPL FAQ items I believe are relevant:

    http://www.gnu.org/licenses/gpl-faq.html#MoneyGuzz lerInc
    http://www.gnu.org/licenses/gpl-faq.html#GPLAndPlu gins
    http://www.gnu.org/licenses/gpl-faq.html#GPLAndNon freeOnSameMachine
    http://www.gnu.org/licenses/gpl-faq.html#MereAggre gation
    http://www.gnu.org/licenses/gpl-faq.html#LinkingWi thGPL
    http://www.gnu.org/licenses/gpl-faq.html#GPLModule License
    http://www.gnu.org/licenses/gpl-faq.html#GPLPlugin sInNF

    I think this item is also insightful:

    http://www.tux.org/lkml/#s1-19

    which mentions:
    http://www.atnf.csiro.au/people/rgooch/linux/docs/ licensing.txt

    TECHNICALLY, seems the GPL prohibits what Kororaa is doing with their Live CD. HOWEVER, seems Linus would side with them. HOWEVER HOWEVER, this would have to be legally debated, in other words, "defended". There's no explicit legal protection, and to get a judgment call would require money, lawyers, and being tangled in a lawsuit.

    All of which would be silly and embarrassing both inside, and outside, of The Community.

    I, personally, am very much in favor of "completely free (as in speech)" software. Mr. Stallman may be a "stickler", but I find him heroically inflexible. The world needs MORE Mr. Stallmans who actually and honestly stand tall, stand proud for what they believe in. And I'm not kissing ass here: I share his vision, but am far weaker in my convictions.

    The pragmatist in me thinks that the Linux kernel's license should be changed to the LGPL. (http://www.gnu.org/copyleft/lesser.html) I know full well, however, that this would be a huge step backward for Freedom. (Anybody saying otherwise is either [1.a] simply not intelligent enough to understand, or [1.b] hasn't bothered to consider the implications, [2] has ulterior motives, and/or [3] has a personal vendetta against RMS due to personality conflict. "Consider the messenger...")

    But PRACTICALLY, it would enable real headway on the driver/support front. I think ATI and nVidia (and every other closed-source **DRIVER** maker) is quite daft. But they have their "reasons", even if we neither know, nor understand them.

    It's laudable to DREAM of a world where all software is Free, both as in Speech AND as in Beer. Bur for now, and for the foreseeable future, we all live and work in the Real World. Unless we're friendly and play nice with the other children, most proprietary companies, especially hardware creators, may very well choose to take their balls and go home. (To those who cry, "GOOD RIDDANCE!", I ask for you to tell us all of the open-source-hardware, with accompanying open-source drivers, to replace their wares with!) Free and Open (Source) Software makes its virtues self-evident. We need not be antagonistic.

    The truth of the matter is that the hardware we want open-sourced drivers for the most is made by companies comfortably at the top of their game. They sell PLENTY of hardware to not need to worry/care about The Community one iota. They ha

    --
    "To err is human, to totally fsck things up requires an election." - L.W. Hale