Re: [PATCH] Blacklist binary-only modules lying about their license

From: Marc Boucher (marc_at_linuxant.com)
Date: 04/28/04

  • Next message: Martin Schwidefsky: "[PATCH] s390 (1/6): core s390."
    Date:	Wed, 28 Apr 2004 12:40:43 -0400
    To: Tom Sightler <ttsig@tuxyturvy.com>
    
    

    On Apr 28, 2004, at 10:03 AM, Tom Sightler wrote:

    > On Tue, 2004-04-27 at 23:28, Marc Boucher wrote:
    >> We generally prefer to focus on making stuff work for users,
    >> rather than waste time arguing about controversial GPL politics.
    >
    > Well, as one of your customers (I am a paid/licensed user of your
    > Conexant modem drivers for my Dell D800) I am completely turned off by
    > this. I use a myriad of different binary drivers on various Linux
    > systems, things like the NVidia binary driver, EMC PowerPath, VMware
    > binary module, etc. EMC PowerPath compares well to your example as it
    > consist of multiple modules and each one spits out a message. EMC
    > simply used their documentation to tell the user that these messages
    > means that the kernel can no longer be supported by the Linux
    > community,
    > however, they can be safely ignored.

    I'm sorry, but the typical user of EMC PowerPath cannot really be
    compared to the typical winmodem user.

    If the issue hadn't been a real confusing / usability problem for
    thousands of individual customers, we wouldn't have bothered with the
    workaround.

    >> I would like however to point out that part of the reason why people
    >> sometimes resort to such kludges is that some kernel maintainers have
    >> been rather reluctant to accommodate proprietary drivers which
    >> unfortunately are a necessary real-world evil
    >
    > In my opinion your actions also represent a real-world evil. As a user
    > I'm reluctant to use proprietary drivers and certainly don't expect
    > the ones
    > that I am forced to used to lie about that fact and try to pretend to
    > be GPL
    > when they are not.

    It is very common practice to simulate the perception of software to
    work around things and provide increased comfort and compatibility.
    Entire GPL projects like wine, reactos, ndiswrapper (an open-source
    clone of our DriverLoader), and even the linux kernel itself implement
    foreign APIs or many workarounds to make programs or drivers function,
    even believe that they are running in another environment. Do these
    projects "lie" and represent real-world evils by technically pretending
    / emulating results when they are in fact not the real thing?

    > After reading this I realized that I myself have probably
    > reported kernel BUG's while your drivers were loaded, not realizing
    > that my
    > kernel was really tainted because it didn't report that fact. Who
    > knows how
    > many other users may have done the same thing?

    The problem goes both ways. Non-standard, unreported and hard to detect
    kernel patches have caused numerous users to report alleged driver bugs
    to us. You wouldn't know how much time and resources these things cost
    us.

    > You seem to think that acceptance of Linux is somehow more important
    > that the
    > GPL. In my opinion it's exactly the opposite, acceptance and
    > recognition of
    > the the importance of the GPL and the rights it gives you is more
    > important
    > than the acceptance of Linux.

    Some folks are more ideological than practical, but most people use
    Linux to solve practical needs.
    The former are a lot more vocal than the silent majority.

    > If the "real-world" forces you to do something
    > that gives up those rights (loading a binary module) the kernel should
    > definitely
    > make the user aware.

    The important part here is making the user aware, which we have clearly
    done.

    Marc

    >
    > Later,
    > Tom
    >
    >

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Martin Schwidefsky: "[PATCH] s390 (1/6): core s390."

    Relevant Pages

    • Linux in a binary world... a doomsday scenario
      ... Linux in a binary world ... 2005 the kernel developers en mass decide that binary ... see their competitors ship only binary drivers, ...
      (Linux-Kernel)
    • Re: 2.6.24-rc8-mm1
      ... Uncompressing linux... ... Ok, booting kernel. ... # Device Drivers ... # SCSI support type ...
      (Linux-Kernel)
    • Re: Linux GPL and binary module exception clause?
      ... >> I have heard many people reference the fact that the although the Linux ... >> under the GPL. ... > become a derived work of the kernel? ... To date we have not even attempted to load our SNAP drivers inside the ...
      (Linux-Kernel)
    • Re: Linux GPL and binary module exception clause?
      ... Well here is the one NO, and imposing all modules are GPL is a no can do. ... > Modules are essentially dynamically linked extensions to the GPL kernel. ... > specifically for Linux, so it seems more appropriate that they would be ... > Linus are being taken out of context to somehow justify permission for the ...
      (Linux-Kernel)
    • Plextor PX-716sa DVD-burner how to make it work under SuSE 9.2?
      ... I had heard that Linux was doing ok now (the ... Unfortunately when I did a fresh install of SuSE 9.2 pro the dvd would not ... The kernel recognizes the SATA interface, it just doesn't see the drive at ... writing the drivers, so that I could get this thing moving, as I am not a ...
      (comp.os.linux.hardware)