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."

27 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. Whaaa? by BobPaul · · Score: 3, Insightful

    I always thought it was ok as long as they provided everything necessary to build the CD on your own, IE all of the GPL code that was used and which non-GPL packages (the nVidia and ATI drivers) were used.

    If anything I would have expected this to be a violation of nVidia and ATI's copyright, distributing their drivers rather than sending people to their respective websites to download.

    1. 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.

  3. 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.
  4. 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
  5. 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
  6. 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.

  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. nvidia and ati are the problem by Anonymous Coward · · Score: 3, Insightful

    i am an idiot so here i go again.

    1) as of the new xorg there is no need for video drivers to be in the kernel.
    2) indeed the kernel people have been urging ati and nv to move their drivers out to userland.
    3) their drivers need a lot of rework to get to userland, plus they will run approx. 1% slower.
    4) neither ati nor nvidia want to lose 1% performance, let alone all the time and testing to move the code.
    5) if one moves before the other, the average gaymer, i mean laymer, oops, gamer magazine draws charts that make 1% seem like the entire frickin' page width.

    bye now.

  10. 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.
  11. Re:tainted kernel by Kortec · · Score: 3, Insightful

    The problem with this is that the "evil" closed sourced drivers, in this case, are hands-down better. The folks at nVidia actually seem to care about the Linux community, and therefore bother to keep up with our development and produce drivers that perform top-notch for us. It's more than a little odd that the thanks they recieve for their efforts, other than my video card dollars, is GPL violetions, but that's the case.

    --
    "My heart is in the work." - Andrew Carnegie
  12. Re:tainted kernel by Anonymous Coward · · Score: 3, Insightful

    "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"

    Thats bullshit as I look at it.

    That driver requires GPL'd code to be compiled. It requires GPL'd code to run. It's obviously kernel-derived and thusly it violates the GPL.

    The tainting is there to inform end users that their kernel is tainted with non-gpl'd code it's not there to decide weither or not distributing GPL'd-derived software in closed source form is legal.

  13. 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."
  14. 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."
  15. Re:All the more reason... by computerjunkie · · Score: 4, Insightful

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

  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. Re:All the more reason... by sumdumass · · Score: 3, Insightful

    it isn't that you cannot use a program, it is that you cannot use certain programs when redistributing gpl'd products. You are free to use it all you want if you don't trip anything in the gpl designed to protect free software.

    Now, i too think this is bullshit. There are alot of users out there that don't have the skills or abilities to install NVidia's or ATI's drivers and have it working corectly. Also, it seems that you cannot use them in a live cd so performance is thrown out. It doesn't matter how free software should be, this just holds it back. It is no wonder propriatary software vendors are fearful and sticking with microsoft only products. Situations like this do nothing but re-enforce all those GPL is viral statments. It is a shame that this hasn't been adressed before. Linus has glanced on the issue with before GPL kernel libraries verses others and non-GPL'd software using them. This topic should be closed at this point in life.

  19. 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?

  20. 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.

  21. Derivative work interpretation is scary by btempleton · · Score: 3, Insightful

    I must say I have always been bothered by the suggestion that writing code to a particular API (such as that of a kernel) could be considered a derivative work under copyright. If I write to the Windows API, have I careated a derivative work of Windows, to be owned by Microsoft?

    If you do static linking of some GPL code with your code, then it's not just a derivative work, you are actually including somebody else's code and must get their permission. But static linking is of course less and less common. Modules that call libraries are only bound to the libraries at runtime today. Code is written to APIs but bound at runtime.

    This is thus a "loophole" in the GPL, turning it into the LGPL in some interpretations, and to fight that, we see this interpretation that just writing code to an API, making use of the API definition found in header files, makes you a derivative work. I don't think this is a good interpretation for a free software movement to be pushing, even if it means some loopholes.

    --
    Has it been over a year since you last donated to the Electronic Frontier Foundation
    1. Re:Derivative work interpretation is scary by btempleton · · Score: 3, Insightful

      But this is, if you think about it, a pretty radical doctrine in software. Certainly if Microsoft, or anybody else who generated a header file or API, tried to claim a copyright interest in programs written to that API, the world, and most of all the free software community, would be up in arms. You should not use a doctrine you would not accept from others.

      --
      Has it been over a year since you last donated to the Electronic Frontier Foundation
  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. Re:There's more restricition in BSD by mrchaotica · · Score: 3, Insightful

    I hate these stupid semantic arguments, because nobody ever realizes that the question is not between "more restrictions" or "less restrictions," but between who is restricted.

    The GPL restricts the developer, because he's forced to contribute his code back to the community. This is done for the benefit of the end user.

    The BSD license restricts the end user, because even though the code running on his device used to be Free, the vendor could chose to close it and cut off his control of his own device at any time. This is done for the benefit of said vendor.

    The GPL and BSD licenses are both restrictive, but in different ways. There is no possible license that has zero restrictions for all.

    Now that I've made this clear, can we please stop arguing about it and move on?!

    --

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

  24. 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.
  25. 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