Re: kernel 2.6.8 pwc patches and counterpatches

From: Greg KH (greg_at_kroah.com)
Date: 08/25/04

  • Next message: Albert Cahalan: "Re: fix text reporting in O(1) proc_pid_statm()" 
    Date:	Tue, 24 Aug 2004 16:04:58 -0700
To: "Nemosoft Unv." <nemosoft@smcc.demon.nl>

    On Wed, Aug 25, 2004 at 12:58:24AM +0200, Nemosoft Unv. wrote:
    > Anyway....
    >
    > I've just about had it with the increasing
    > "we-don't-want-binary-stuff-in-Linux" attitude lately. If you rip out this
    > hook for PWC (pwc_register_decompressor), which would make it impossible to
    > load a decompressor, closed source *OR* open source (should that happen one
    > day), is going to be the last straw.

    Well, I just made a patch that did just that, and applied it to my
    trees.

    > Without this hook, PWC will work, but with limitations, just as it always
    > has. But the _user_ always had a choice of loading a closed source module
    > to get the extras. If you, kernel developers, maintainers, etc. are going
    > to take away that right from the _users_, I think you're way over head,
    > forgetting what open source is about, IMO.
    >
    > I accept that the Linux kernel is the work of Linus and the maintainers, and
    > they can do with it as they please, but I will not accept that they can put
    > arbitrary limits on the kernel's use by me, or other users.

    Think legal limits, not arbitrary.

    > Anyway, before this gets too long... I'm giving you a choice here. Either:
    >
    > * you are going to accept that there is a driver in the Linux kernel that
    > has a hook that _may_ be used to load a binary-only decompressor part into
    > the kernel, at the user's disgression. Maybe, one day, that part will be
    > open source too but I cannot guarantuee that.

    I now realize that. So I've ripped that hook out, as it's only used to
    load a binary driver, which is not allowed.

    That's the change I'm going to make.

    If you want to send me a patch to tell me to rip the whole driver out,
    fine I will, no problems, I completly understand.

    But realize that anyone can then add it back, as the work you did was
    released under the GPL :)

    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: Albert Cahalan: "Re: fix text reporting in O(1) proc_pid_statm()"

    Relevant Pages

    • Re: ksoftirqd uses 99% CPU triggered by network traffic (maybe RLT-8139 related)
      ... Patch r8139-20.patch didn't help. ... crash but without DEBUG it did crash. ... Here is a snapshot from the log file when driver is crashing: ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: r8169.c
      ... > who tries to work with the 8169 driver on the long run). ... > Btw merging a 20 megaton patch is not the way network drivers changes ... > the suggested format). ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Linux-2.6.12
      ... Just fills me with confidence about the GPL'd nature of this driver. ... * downright wrong changes to the Linux kernel that occurred in ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] iSeries virtual disk
      ... > patch for a new driver. ... Can you split them out into a separate patch? ... > better merging it into it's only caller. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Non-GPL export of invalidate_mmap_range
      ... but it's hard to see the relevance of this to your patch. ... it was NOT a derived work. ... if a the Linux kernel must be modified in order ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)