Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12172 comp.os.386bsd.misc:3084 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!news.cac.psu.edu!news.pop.psu.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: 8 Aug 1994 12:02:41 GMT Organization: Information Technology Division, Naval Research Laboratory Lines: 40 Message-ID: <3256t1$rbn@ra.nrl.navy.mil> References: <Cu107E.Mz3@curia.ucc.ie> <31trcr$9n@euterpe.owl.de> NNTP-Posting-Host: sundance.itd.nrl.navy.mil In article <31trcr$9n@euterpe.owl.de>, Martin Husemann <martin@euterpe.owl.de> wrote: >In <Cu107E.Mz3@curia.ucc.ie> dave@odyssey.ucc.ie writes: > >>OK, I keep hearing reference to how Linux networking is not as good >>as FreeBSD and so forth > >We had a Linux-1.0 system connected to the Internet. When? >- Dynamic routing (routed) did not work and was disabled. routed is inherently broken for routing. Gated works on Linux fine, however. >- Changing static routes sometimes brought the system to some obscure > state needing a reboot. Never *ever* seen this happen, even in the very early days. >- Smail wouldn't work in daemon mode but had to be started by inetd > (and the retry scheduling by a cron job) Your Smail configuration was wrong then. Always worked fine for me. >- sometimes the system won't let you telnet or ftp in (this affects the > smtp port as well, but due to higher timeouts doesn't matter): telnet > says: "Connected to ....." and nothing happens. After some minutes > you would get a prompt, if the timeout hadn't disconnected you. This > happens nondeterministic but regular. Again, I've used Linux and its networking from the early days (and on some crazy configurations), and I've never seen anything like this. >- NFS was *slooow* No arguing this one. Linux's NFS is still in need of serious work. -Craig