Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12712 comp.os.386bsd.misc:3414
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!hookup!yeshua.marcam.com!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!EU.net!Germany.EU.net!netmbx.de!zib-berlin.de!irz401!uriah!not-for-mail
From: j@uriah.sax.de (J Wunsch)
Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc
Subject: Re: Whats wrong with Linux networking ???
Date: 17 Aug 1994 18:36:05 +0200
Organization: Private U**X site; member IN e.V.
Lines: 22
Message-ID: <32te9lINN6ab@bonnie.sax.de>
References: <RSANDERS.94Aug9003813@hrothgar.mindspring.com> <1994Aug13.012953.5809@cs.brown.edu> <32jp2u$bpb@Starbase.NeoSoft.COM> <32ll52$n7d@quagga.ru.ac.za> <1994Aug15.034939.20997@cs.brown.edu>
NNTP-Posting-Host: bonnie.sax.de
mhw@cs.brown.edu (Mark Weaver) writes:
>disk activity. I always get significant disk activity from compiling,
>even though my /tmp is a ramdisk.
>On Linux, while doing the same thing, there is hardly any disk
>activity at all. I always think something's wrong when compiling
>under Linux because I don't hear the characteristic disk chattering
>that I associate with compiling.
Are you sure your temp files go via the ramdisk? I've used to compile
with ``-pipe'' set, and i notice the same effect as you with Linux
even when making World for XFree86 etc. Some infrequently blinking of
the SCSI LED indicates that a new source file is being read/ object
file written, but nothing to hear like the usual `machine gun sound'.
(This is with FreeBSD > 1.0.2)
--
cheers, J"org work: joerg_wunsch@tcd-dresden.de
private: joerg_wunsch@uriah.sax.de
Steinbach's Guideline for Systems Programming:
Never test for an error condition you don't know how to handle.