mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: "David S. Miller" <davem@redhat.com>
Cc: "Matt D. Robinson" <yakker@alacritech.com>,
	"La Monte H.P. Yarroll" <piggy@em.cig.mot.com>,
	linux-kernel@vger.kernel.org, sctp-developers-list@cig.mot.com
Subject: Re: [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table
Date: Wed, 6 Jun 2001 17:51:24 -0600	[thread overview]
Message-ID: <200106062351.f56NpOs20522@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <15134.48456.5360.764458@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> <3B1EBB13.34721ED9@alacritech.com> <15134.48456.5360.764458@pizda.ninka.net>

David S. Miller writes:
> 
> Matt D. Robinson writes:
>  > > 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.
>  > 
>  > And if as Joe User I don't want Linux TCP, but Joe's TCP, they can't
>  > do that (in a supportable way)?  Are you saying Linux is, "do it my
>  > way, or it's the highway"?

Pardon my cynicism, but this reads more like "I'm an ACME Inc. and I
want to sell a proprietary TCP stack for Linux, please change Linux to
make this possible/easy". I doubt there are many Joe Users out there
who want to replace their TCP stack. I bet they would be much happier
to see patches go in which improve the performance of the generic
kernel.

But I'm sure there are plenty of ACME Inc.'s out there who would love
to sell a replacement TCP stack. And suck users down a proprietary
solution path. But I don't see why the Linux community should help the
ACME's of this world. And Linux is doing very nicely in the corporate
world, so we needn't to lose any sleep over what our current policies
do for our acceptance levels.

If it bothers you that Linux caters more the the users and less to the
vendors, then use another OS. We don't mind. The door is over there.
Please don't slam it on your way out.

> If Joe's TCP is opensource, they are more than welcome to publish
> such changes.

Yep. And then we can all benefit.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  reply	other threads:[~2001-06-06 23:58 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 ` La Monte H.P. Yarroll
2001-06-06 22:07   ` La Monte H.P. Yarroll
2001-06-07 19:11     ` Matthias Urlichs
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 [this message]
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=200106062351.f56NpOs20522@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggy@em.cig.mot.com \
    --cc=sctp-developers-list@cig.mot.com \
    --cc=yakker@alacritech.com \
    /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

all inboxes | Powered by JetHome®