Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12099 comp.os.386bsd.misc:3048 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!europa.eng.gtefsd.com!news.umbc.edu!haven.umd.edu!cs.umd.edu!ra.nrl.navy.mil!sundance!cmetz From: cmetz@sundance.itd.nrl.navy.mil (Craig Metz) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: Whats wrong with Linux networking ??? Date: 5 Aug 1994 20:24:47 GMT Organization: Information Technology Division, Naval Research Laboratory Lines: 28 Message-ID: <31u76f$3cq@ra.nrl.navy.mil> References: <Cu107E.Mz3@curia.ucc.ie> NNTP-Posting-Host: sundance.itd.nrl.navy.mil In article <Cu107E.Mz3@curia.ucc.ie>, <dave@odyssey.ucc.ie> wrote: >OK, I keep hearing reference to how Linux networking is not as good >as FreeBSD and so forth > >usually in the form of 'Linux networking, being written from the ground up, >and as opposed to 386BSD derivatives rather cleverly using the available >and stable NET/2 code' (and of course this ignites the whole >licencing debate)... > >what I want to know is, can anyone back this up with facts ? What >exactly doesn't Linux do (or does do, but incorrectly) ? Linux doesn't just copy the Berkeley network code like basically every other UNIX-like OS on the planet except Solaris 2.4. Apparently, this is sacrilege to many people. The only reasonable complaint is that the BSD code has had about a decade to mature, while the Linux code is still very immature. If your primary goal in a UNIX is networking, you *will* find that Linux is not your best choice, FreeBSD is. The really nasty bugs seem to have been worked out, but there are a number of things left to be written (real option processing, IP multicast) and many bugs yet to be squashed. Depending on how much you rely on networking, this could be a minor annoyance or a major headache. -Craig