Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:2887 comp.os.linux.misc:20508 Newsgroups: comp.os.386bsd.misc,comp.os.linux.misc Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!rex!ben From: ben@rex.uokhsc.edu (Benjamin Z. Goldsteen) Subject: Re: I hope this wont ignite a major flame war, but Ive got to know! Message-ID: <CtMnq1.C8@rex.uokhsc.edu> Date: Thu, 28 Jul 1994 01:49:12 GMT Reply-To: benjamin-goldsteen@uokhsc.edu References: <30drlt$7tc@news.u.washington.edu> <Ct5qpn.G6E@murdoch.acc.Virginia.EDU><9407221206.29@rmkhome.com> <DHOLLAND.94Jul25171448@scws33.harvard.edu> <CtKBJ5.77B@rex.uokhsc.edu> <3163r7$440@quagga.ru.ac.za> Organization: Health Sciences Center, University of Oklahoma Lines: 20 csgr@cs.ru.ac.za (Geoff Rehmet) writes: >In <CtKBJ5.77B@rex.uokhsc.edu> ben@rex.uokhsc.edu (Benjamin Z. Goldsteen) writes: >>Linux is about the only UNIX-alike that doesn't base their TCP/IP code >>on BSD's. >I guess you don't consider SYSV to be a UNIX-alike OS ;-) Unless I am mistaken, SVR4's networking consists of the Berkeley TCP/IP code with STREAMS on top (with sockets emulated on STREAMS). There were a few other attempts at TCP/IP, but they weren't too successful... [I believe Peter de Silvia will back me up on this] Actually, though, I think the fact that Linux doesn't base their TCP/IP code on BSD is a good thing for TCP/IP. Rewriting something from scratch based on the standards documents is a good way to find bugs and imprecision. -- Benjamin Z. Goldsteen