RE: [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table

["George Bonser" <george@gator.com>]

> Ben Greear writes:
>  > a modular TCP stack might be a really
>  > good option for making $$ though support fees...  If there is a
>  > need to keep certain (proprietary) code out of the kernel, let
>  > lawyers & public pressure do it, not overly broad technical
> restrictions.
>
> There is a legal restriction, basically "Linus and the copyright
> holders of the networking say no."
>
> Later,
> David S. Miller
> davem@redhat.com

There is, of course, one basic problem with that argument. While you can say
(and probably rightly so) that such a change would not be included in Linus'
kernel, I think anyone is allowed to post a patch that might make it
possible to add protocols as modules. If anyone chooses to use it is each
individual's decision but you could not prevent ACME from creating a patch
that allows protocol modules as long as they distributed the patch. Also,  I
know that you are allowed to distribute proprietary modules in binary form
but are there any restrictions on what function these modules can perform?
I don't remember seeing any such restrictions.

In short, while you can refuse to accept such patches or support any
problems arising from their use, I would think that ACME has the right to
patch the kernel to make such a thing possible if they want to and there is
nothing (as far as I know) that anyone can do about it as long as they make
those patches public.  So, ACME can say that to use ACME Super FooWare you
will need the ACME Super FooKernel with our FooModule that is distributed in
binary format. If you want to build the FooKernel, here is the patch but the
module is still binary.