Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12103 comp.os.386bsd.misc:3050
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!math.ohio-state.edu!jussieu.fr!centre.univ-orleans.fr!univ-lyon1.fr!swidir.switch.ch!scsing.switch.ch!news.dfn.de!urmel.informatik.rwth-aachen.de!news.rhrz.uni-bonn.de!mpifr-bonn.mpg.de!uniol!news.fh-lippe.de!euterpe.owl.de!not-for-mail
From: martin@euterpe.owl.de (Martin Husemann)
Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc
Subject: Re: Whats wrong with Linux networking ???
Date: 5 Aug 1994 19:03:23 +0200
Organization: The Other Site - Martin's Museum of Muses
Lines: 29
Message-ID: <31trcr$9n@euterpe.owl.de>
References: <Cu107E.Mz3@curia.ucc.ie>
NNTP-Posting-Host: localhost.owl.de
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-Newsreader: NN version 6.5.0 #2 (NOV)
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.
- Dynamic routing (routed) did not work and was disabled.
- Changing static routes sometimes brought the system to some obscure
state needing a reboot.
- Smail wouldn't work in daemon mode but had to be started by inetd
(and the retry scheduling by a cron job)
- 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.
- NFS was *slooow*
There may have been other obscurities, which I've forgotten.
Martin
--
UNIX - An operating system similar to OS-9, but with less functionality
and special features designed to soak up excess memory, disk space and
CPU time on large, expensive computers.
-- OS-9 Glossary