Re: [RFC] Small PCI core patch

From: Greg KH (greg_at_kroah.com)
Date: 11/22/05

  • Next message: Greg KH: "[RFC] Small PCI core patch"
    Date:	Mon, 21 Nov 2005 15:01:41 -0800
    To: linux-kernel@vger.kernel.org
    
    

    On Mon, Nov 21, 2005 at 02:53:03PM -0800, Greg KH wrote:
    > Subject: PCI: fix up the exported symbols to be the proper license.

    Ok, now that I have everyone's attention, no I'm not serious about
    submitting this patch, I'm not a fool. I know the rules about existing
    kernel symbols.

    But, what if this patch really did go in? Who would be affected by
    this? Nothing that is currently in the kernel.org kernel tree, right,
    so what's the big deal?

    Oh yeah, closed source drivers that are out side of the tree, but who
    cares about them?

    Oh yeah, _very_ large companies rely on them right now, and are working
    on creating more and more closed source drivers. Why? Don't they know
    that their legal departments do not agree with this? Are they
    approaching Linux development in the same way they used to with the old
    Unix systems, i.e. fork and "add value"?

    Well, consider this a warning shot for anyone who is relying on closed
    source modules. What you are doing is trying to take from Linux and not
    give anything back.. The GPL explicitly forbids this, and Linux would
    not be good enough today for you to be using it without that protection.
    There is a reason why you are wanting to use Linux for your internal
    use, and why your customers are asking for it.

    If you, or your company is relying on closed source kernel modules, your
    days are numbered. And what are you going to do, and how are you going
    to explain things to your bosses and your customers, if possibly,
    something like this patch were to be accepted?

    Something to think about...

    thanks,

    greg k-h
    -
    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: Greg KH: "[RFC] Small PCI core patch"

    Relevant Pages

    • [PATCH]Documentation update broken web addresses.
      ... Below you will find an updated version from the original series bunching all patches into one big patch ... Kernel Developer's Guide at ... problems that need to be cleaned up and fixed within the Linux kernel ... ps/2 keybd is multiplexed through this driver ...
      (Linux-Kernel)
    • Re: [PATCH]Documentation update broken web addresses.
      ... As for the patch itself if anybody see's anything that might be fixed let me know and I'll fix it up ... Kernel Developer's Guide at ... problems that need to be cleaned up and fixed within the Linux kernel ... ps/2 keybd is multiplexed through this driver ...
      (Linux-Kernel)
    • Open letter to Linux kernel developers (was Re: Binary Drivers)
      ... I am writing as a Linux-only user of over 2 years to express my concern with the recent proposal to block out closed source modules from the kernel. ... that trying to steamroll the industry into developing open source drivers by banning closed source drivers is going to have a completely different result. ... To us this decision would mean that after Jan 1 2008 we will be out of business (at least in the Linux market). ... Developers contributing their software to Linux kernel have full right to decide if other kernel code using their work is derived or not. ...
      (Linux-Kernel)
    • Re: that old GNU/Linux argument
      ... Linux is the kernel ONLY ... By "closed source" if you mean proprietary code; ... Contrary to his unfortunate quote: Mr. Torvalds has never had aspirations to be a "god" ...
      (Fedora)
    • Re: Nobody should ever need to patch the kernel!!
      ... just look around for the most famous linux kernel patches... ... You cannot enable shfs mounts without a patch... ... programmers, what were they thinking when they programmed that part, ...
      (comp.os.linux.development.system)