From: Steve Alexander <sca@refugee.engr.sgi.com>
To: Alan Cox <alan@cymru.net>
Cc: lm@gate1-neteng.engr.sgi.com (Larry McVoy),
dm@neteng.engr.sgi.com, nn@lanta.engr.sgi.com,
torvalds@cs.helsinki.fi, sparclinux-cvs@caipfs.rutgers.edu,
lmlinux@neteng.engr.sgi.com
Subject: Re: linux needs bsd networking stack
Date: Thu, 30 May 1996 11:17:21 -0700 [thread overview]
Message-ID: <199605301817.LAA13683@refugee.engr.sgi.com> (raw)
In-Reply-To: Message from alan@cymru.net of 30 May 1996 11:06:25 BST
Alan Cox <alan@cymru.net> writes:
>We can't steal it outright. 4.4BSD has abominable problems as is. The FreeBSD
>people
>have the worst of them fixed but don't have stuff like Vegas and have all the
>horrible spoofing problems caused by bad timers.
I'm not sure I understand what that means, but I'm pretty sure that Vegas is
not universally agreed to be a good idea, unless I've missed a meeting.
Just to set the record straight, there are people at SGI who don't like either
the BSD or Linux stacks ;->.
The one thing that I will say about the Linux stack is that it is evolving much
more rapidly than any of the public BSD versions are (I spent some time porting
aliases forward from one version to another for a friend, and the improvements
between versions were amazing), so at some point it will probably win on
functionality.
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steve Alexander <sca@refugee.engr.sgi.com>
To: Alan Cox <alan@cymru.net>
Cc: Larry McVoy <lm@gate1-neteng.engr.sgi.com>,
dm@neteng.engr.sgi.com, nn@lanta.engr.sgi.com,
torvalds@cs.helsinki.fi, sparclinux-cvs@caipfs.rutgers.edu,
lmlinux@neteng.engr.sgi.com
Subject: Re: linux needs bsd networking stack
Date: Thu, 30 May 1996 11:17:21 -0700 [thread overview]
Message-ID: <199605301817.LAA13683@refugee.engr.sgi.com> (raw)
Message-ID: <19960530181721.tILw7FqKemPYZm1723_hsePwvMaiJuBI8YxuDQuGZeI@z> (raw)
In-Reply-To: Message from alan@cymru.net of 30 May 1996 11:06:25 BST
Alan Cox <alan@cymru.net> writes:
>We can't steal it outright. 4.4BSD has abominable problems as is. The FreeBSD
>people
>have the worst of them fixed but don't have stuff like Vegas and have all the
>horrible spoofing problems caused by bad timers.
I'm not sure I understand what that means, but I'm pretty sure that Vegas is
not universally agreed to be a good idea, unless I've missed a meeting.
Just to set the record straight, there are people at SGI who don't like either
the BSD or Linux stacks ;->.
The one thing that I will say about the Linux stack is that it is evolving much
more rapidly than any of the public BSD versions are (I spent some time porting
aliases forward from one version to another for a friend, and the improvements
between versions were amazing), so at some point it will probably win on
functionality.
-- Steve
next reply other threads:[~1996-05-30 18:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-30 18:17 Steve Alexander [this message]
1996-05-30 18:17 ` linux needs bsd networking stack Steve Alexander
-- strict thread matches above, loose matches on Subject: below --
1996-05-30 0:36 Neal Nuckolls
1996-05-30 3:02 ` David S. Miller
1996-05-30 10:12 ` Alan Cox
1996-05-30 10:12 ` Alan Cox
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=199605301817.LAA13683@refugee.engr.sgi.com \
--to=sca@refugee.engr.sgi.com \
--cc=alan@cymru.net \
--cc=dm@neteng.engr.sgi.com \
--cc=lm@gate1-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