Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12213 comp.os.386bsd.misc:3105
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!spool.mu.edu!nigel.msen.com!zib-berlin.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: 8 Aug 1994 19:26:40 +0200
Organization: The Other Site - Martin's Museum of Muses
Lines: 27
Message-ID: <325psg$15q@euterpe.owl.de>
References: <Cu107E.Mz3@curia.ucc.ie> <31trcr$9n@euterpe.owl.de> <3256t1$rbn@ra.nrl.navy.mil>
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 <3256t1$rbn@ra.nrl.navy.mil> cmetz@sundance.itd.nrl.navy.mil (Craig Metz) writes:
>>We had a Linux-1.0 system connected to the Internet.
> When?
Shortly after 1.0 was available...
>>- 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.
;-}
We used slackware without any modifications. Smail was completely broken
and wouldn't do retries after SMTP timeouts. I don't see how a smail
configuration could break daemon mode (some accept(2) failed); this
looks very much like a OS failure to me...
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