Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12298 comp.os.386bsd.misc:3166 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!spool.mu.edu!news.clark.edu!netnews.nwnet.net!selway.umt.edu!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: Whats wrong with Linux networking ??? Date: 12 Aug 1994 14:44:22 GMT Organization: Montana State University, Bozeman Montana Lines: 49 Message-ID: <32g1s6$98b@pdq.coe.montana.edu> References: <Cu8CBr.Fx@calcite.rhyolite.com> <32bfg0$sol@ra.nrl.navy.mil> <1994Aug11.062307.29008@cs.brown.edu> <32daeg$flv@ra.nrl.navy.mil> NNTP-Posting-Host: 153.90.192.29 In article <32daeg$flv@ra.nrl.navy.mil>, Craig Metz <cmetz@sundance.itd.nrl.navy.mil> wrote: > What I really disagree with here is that many people, Vernon definitely >being the loudest, keep saying that the Linux communities shouldn't even try >to create and implement new designs because, obviously, the BSD code is far >superior to everything else. This is *far* from the truth. Vernon's statement has nothing to do with Linux or BSD. This is NOT a BSD vs. Linux issue. If I may be so bold, I'm hearing Vernon say this: "If freely usable code exists that performs the task you are trying to accomplish, use it." He could argue that the BSD folks are stupid for not using dosemu, since the code is already written, why 're-invent it'? However, he's not because none of the BSD folks will argue that point with him. :-) That the NFS server happens to be used in BSD is irrelevant to the issue. CSRG decided to not 're-invent' NFS since U.of.G. already did. They didn't follow the 'NIH' syndrom highly discussed. You can choose to 're-invent' everything, but the arguement is made that it's possible that nothing is to gain. >I strongly disagree. Even if it ends up a total >failure deserving of another rewrite or going to the BSD code, it is imperative >that people try new designs and implementations. Before or after a working version is there. My *opinion* on the matter is to build a working system FIRST, and then AFTER it is working try out new things. But, that is also market driven as well. My customers don't care that my product may be faster/better/quicker/bigger/smaller than the competitors product if it doesn't work right or doesn't exist. Make it work right first, and then try to make it better/faster. If that means taking a step back and using someone else's code in the interim, so be it. 'Nuff said. Nate -- nate@bsd.coe.montana.edu | FreeBSD core member and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-4836 | home #: (406) 586-0579 | Available for contract/otherwise work.