From: Matthias Urlichs <smurf@noris.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table
Date: Thu, 7 Jun 2001 21:11:38 +0200 [thread overview]
Message-ID: <p0510030bb74580aabb4a@[10.2.6.42]> (raw)
In-Reply-To: <15134.43914.98253.998655@pizda.ninka.net>
In-Reply-To: <200106051659.LAA20094@em.cig.mot.com> <3B1E5CC1.553B4EF1@alacritech.com> <15134.42714.3365.32233@theor.em.cig.mot.com> <15134.43914.98253.998655@pizda.ninka.net>
Ahem...
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
needed.
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
next prev parent reply other threads:[~2001-06-07 19:16 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B1E5CC1.553B4EF1@alacritech.com>
2001-06-05 16:59 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table La Monte H.P. Yarroll
2001-06-06 22:07 ` La Monte H.P. Yarroll
2001-06-07 19:11 ` Matthias Urlichs [this message]
2001-06-11 18:26 ` [PATCH] sockreg2.4.5-06 " La Monte H.P. Yarroll
2001-06-13 16:25 ` David S. Miller
2001-06-06 22:15 ` [PATCH] sockreg2.4.5-05 " David S. Miller
2001-06-06 22:36 ` Alexander Viro
2001-06-06 22:42 ` Richard Gooch
2001-06-06 22:52 ` David S. Miller
2001-06-06 23:21 ` Matt D. Robinson
2001-06-06 23:51 ` Richard Gooch
2001-06-07 0:51 ` David S. Miller
2001-06-07 5:37 ` George Bonser
2001-06-07 5:50 ` David S. Miller
2001-06-07 6:00 ` George Bonser
2001-06-07 15:18 ` watermodem
2001-06-07 15:51 ` Mike Galbraith
2001-06-09 22:09 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregistertable watermodem
2001-06-09 23:15 ` Alexander Viro
2001-06-10 2:59 ` Horst von Brand
2001-06-10 4:38 ` Mike Galbraith
2001-06-07 1:22 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table Ben Greear
2001-06-07 5:16 ` Matt D. Robinson
2001-06-07 18:03 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister Alan Cox
2001-06-07 5:46 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table David S. Miller
2001-06-07 6:20 ` Richard Gooch
2001-06-07 6:47 ` Matt D. Robinson
2001-06-07 18:10 ` Alan Cox
2001-06-08 1:31 ` David S. Miller
2001-06-06 23:31 ` David S. Miller
2001-06-06 23:43 ` David S. Miller
2001-06-07 10:03 ` Henning P. Schmiedehausen
2001-06-07 10:50 ` Daniel Phillips
2001-06-07 17:52 ` Alan Cox
2001-06-08 8:29 ` Henning P. Schmiedehausen
2001-06-08 16:42 ` Alan Cox
2001-06-08 22:54 ` Albert D. Cahalan
2001-06-08 23:46 ` David Woodhouse
2001-06-11 8:45 ` Henning P. Schmiedehausen
2001-06-11 9:43 ` Helge Hafting
2001-06-11 16:17 ` Alan Cox
2001-06-11 18:31 ` Jacob Luna Lundberg
2001-06-11 18:48 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister Alan Cox
2001-06-11 20:34 ` Jacob Luna Lundberg
2001-06-12 7:08 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregistertable Helge Hafting
2001-06-07 10:05 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table Russell King
2001-06-07 15:27 ` Keith Owens
2001-06-07 17:01 ` David Woodhouse
2001-06-07 11:25 ` David S. Miller
2001-06-07 11:25 ` David S. Miller
2001-06-07 0:14 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='p0510030bb74580aabb4a@[10.2.6.42]' \
--to=smurf@noris.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).