David S. Miller wrote:
>This allows people to make proprietary implementations of TCP under
>Linux. And we don't want this just as we don't want to add a way to
>allow someone to do a proprietary Linux VM.
*Sigh* and thence begin the proprietary-vs-OpenSource flame wars again.
_Any_ open protocol can be abused for proprietary stuff. It can also
be used for Something Entirely Different.
Personally, I would _love_ to have TCP as a module, just so that the
system can unload it on my poor underpowered laptop when it's not
The fact that you can abuse this ability in order to replace the
current TCP with Something Proprietary And Therefore Evil is a
no-brainer. Anybody can do exactly the same thing with my network
card driver, or the Unix-domain code, or the NFS server, or ...
So what's so damn special about the TCP stack that you need to shout
"Absolutely not" here? I don't get it.
-- Matthias Urlichs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/