Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Alan Cox <alan@cymru.net>
To: nn@lanta.engr.sgi.com (Neal Nuckolls)
Cc: dm@neteng.engr.sgi.com, lmlinux@neteng.engr.sgi.com,
	sparclinux-cvs@caipfs.rutgers.edu, alan@cymru.net,
	torvalds@cs.helsinki.fi
Subject: Re: linux needs bsd networking stack
Date: Thu, 30 May 1996 11:12:12 +0100 (BST)	[thread overview]
Message-ID: <199605301012.LAA24835@snowcrash.cymru.net> (raw)
In-Reply-To: <199605300036.RAA09665@lanta.engr.sgi.com> from "Neal Nuckolls" at May 29, 96 05:36:19 pm

> Whether the linux kernel networking implementation is better or
> worse than the BSD code isn't my point. The fact that it's not
> clearly superior, only very different, from the standard is.

Chuckle. The BSD stack doesn't even match the RFC's [ie THE STANDARD]

> work in this area I can readily grab many free BSD-based protocol
> pieceparts off the net. New routing protocols, ATM signalling, TCP
> conjestion improvements, realtime protocol stacks, etc. are all

Let me see: Routing protocols is userspace. ATM signalling we have (going in
2.1), Vegas we have in the pre 2.1 stuff. realtime - if you mean low latency
then take a look at unet.

> Actually, for the startups that I mentioned - those interested in
> shipping a commercial product - there is no choice, it's FreeBSD,
> because it comes without the GPL kiss of death.

So "We should change it for the startups" was message 1. "The startups wont
use it was message two". Do you have bullet holes in your shoes by any
chance ?

> I think that basing any improvements on a 4.4BSD-based linux stack
> would result in something more usable.  Also, as a side effect, it
> would encourage more talented networking people to participate and
> isn't this what freeware is all about?

We can't use the 4.4BSD stack so that issue is moot. Free software is also about high
technical quality. If I wanted to get paid lots of money for hacking kernels I'd go
and work for mirkosoft

WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@cymru.net>
To: Neal Nuckolls <nn@lanta.engr.sgi.com>
Cc: dm@neteng.engr.sgi.com, lmlinux@neteng.engr.sgi.com,
	sparclinux-cvs@caipfs.rutgers.edu, alan@cymru.net,
	torvalds@cs.helsinki.fi
Subject: Re: linux needs bsd networking stack
Date: Thu, 30 May 1996 11:12:12 +0100 (BST)	[thread overview]
Message-ID: <199605301012.LAA24835@snowcrash.cymru.net> (raw)
Message-ID: <19960530101212.3PxLS0q6stcP2ppM85RSEqEDXveAI86PGKQ13ek9ZCA@z> (raw)
In-Reply-To: <199605300036.RAA09665@lanta.engr.sgi.com> from "Neal Nuckolls" at May 29, 96 05:36:19 pm

> Whether the linux kernel networking implementation is better or
> worse than the BSD code isn't my point. The fact that it's not
> clearly superior, only very different, from the standard is.

Chuckle. The BSD stack doesn't even match the RFC's [ie THE STANDARD]

> work in this area I can readily grab many free BSD-based protocol
> pieceparts off the net. New routing protocols, ATM signalling, TCP
> conjestion improvements, realtime protocol stacks, etc. are all

Let me see: Routing protocols is userspace. ATM signalling we have (going in
2.1), Vegas we have in the pre 2.1 stuff. realtime - if you mean low latency
then take a look at unet.

> Actually, for the startups that I mentioned - those interested in
> shipping a commercial product - there is no choice, it's FreeBSD,
> because it comes without the GPL kiss of death.

So "We should change it for the startups" was message 1. "The startups wont
use it was message two". Do you have bullet holes in your shoes by any
chance ?

> I think that basing any improvements on a 4.4BSD-based linux stack
> would result in something more usable.  Also, as a side effect, it
> would encourage more talented networking people to participate and
> isn't this what freeware is all about?

We can't use the 4.4BSD stack so that issue is moot. Free software is also about high
technical quality. If I wanted to get paid lots of money for hacking kernels I'd go
and work for mirkosoft

  parent reply	other threads:[~1996-05-30 10:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-30  0:36 linux needs bsd networking stack Neal Nuckolls
1996-05-30  3:02 ` David S. Miller
1996-05-30 10:12 ` Alan Cox [this message]
1996-05-30 10:12   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
1996-05-30 18:17 Steve Alexander
1996-05-30 18:17 ` Steve Alexander
1996-05-29 23:04 Larry McVoy
1996-05-30 10:06 ` Alan Cox
1996-05-30 10:06   ` Alan Cox
1996-05-29 21:59 Neal Nuckolls
1996-05-29 22:50 ` David S. Miller
1996-05-30  9:46   ` Alan Cox
1996-05-30  9:46     ` Alan Cox
1996-05-30  5:21 ` Linus Torvalds
1996-05-30  9:43 ` Alan Cox
1996-05-30  9:43   ` Alan Cox

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=199605301012.LAA24835@snowcrash.cymru.net \
    --to=alan@cymru.net \
    --cc=dm@neteng.engr.sgi.com \
    --cc=lmlinux@neteng.engr.sgi.com \
    --cc=nn@lanta.engr.sgi.com \
    --cc=sparclinux-cvs@caipfs.rutgers.edu \
    --cc=torvalds@cs.helsinki.fi \
    /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