Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1909 ; Tue, 23 Feb 93 15:03:34 EST Newsgroups: comp.os.386bsd.questions Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!nate From: nate@cs.montana.edu (Nate Williams) Subject: Re: Unstable system? Message-ID: <1993Feb22.053302.9970@coe.montana.edu> Sender: usenet@coe.montana.edu (USENET News System) Organization: Dept. of Computer Science, MSU, Bozeman Mt 59717 References: <6385@krafla.rhi.hi.is> Date: Mon, 22 Feb 1993 05:33:02 GMT Lines: 24 In article <6385@krafla.rhi.hi.is> adamd@rhi.hi.is (Adam David) writes: >Is there any inherent reason why this combination of hardware / software >crashes easily? > >Hardware: 33MHz cx486DLC + 387 (AMI BIOS) with 16 MB RAM 70ns. > all bios shadows disabled, (probably) no waitstate RAM. > (adaptec 1542B) SCSI hard disks and wd8003 ethernet, Boca io2x4 > parallel / serial portsū. > waitstate enabled on the ethernet bios. >System: standard 386bsd distribution (bin01, src01, etc01) with no patches. > swapfile enabled on /dev/as0b (doesn't seem to make any difference). The no patches installed is a real big reason, especially since you have 16MB. I'm suprised you've been able to use it at all. Get the patch-kit from agate, apply the patches, and I think you'll be a lot happier. Nate -- osynw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, home #: (406) 586-0579 | I don't think they'll catch on - Don H.