Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12304 comp.os.386bsd.misc:3170 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!reuter.cse.ogi.edu!psgrain!rainrgnews0!pacifier!news.alpha.net!MathWorks.Com!europa.eng.gtefsd.com!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: 9 Aug 1994 16:47:12 GMT Organization: Information Technology Division, Naval Research Laboratory Lines: 24 Message-ID: <328bug$rmg@ra.nrl.navy.mil> References: <Cu107E.Mz3@curia.ucc.ie> <31trcr$9n@euterpe.owl.de> <3256t1$rbn@ra.nrl.navy.mil> <325psg$15q@euterpe.owl.de> NNTP-Posting-Host: sundance.itd.nrl.navy.mil In article <325psg$15q@euterpe.owl.de>, Martin Husemann <martin@euterpe.owl.de> wrote: >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... There have been a number of *major* bug fixes since then. >>>- 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... Smail is *very* sensitive to a proper build configuration. This is the kind of things that the canned distributions like Slackware frequently botch. I've always build Smail from the source and done my own build configuration and I have yet to encounter any problems. -Craig