Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sun-barr!olivea!mintaka.lcs.mit.edu!ogicse!flop.ENGR.ORST.EDU!gaia.ucs.orst.edu!gecko.oes.orst.edu!matt From: matt@gecko.oes.orst.edu (Matt Curfman) Newsgroups: comp.os.386bsd.questions Subject: Re: 386BSD & MUDs Keywords: Muds, argh!!! Message-ID: <1ndkjfINNf1v@gaia.ucs.orst.edu> Date: 7 Mar 93 20:06:07 GMT References: <1993Mar7.055922.7770@wam.umd.edu> <6502@krafla.rhi.hi.is> Organization: Oregon State University, Corvallis OR USA Lines: 32 NNTP-Posting-Host: gecko.oes.orst.edu In article <6502@krafla.rhi.hi.is> adamd@rhi.hi.is (Adam David) writes: >publius@wam.umd.edu (Inigo Montoya) writes: > [deleted] > >With patchkit 0.2.1 the system is stable enough to compile on, but random >crashes do still occur - it does not make any difference whether the code >being compiled is simple or complicated, large or small, few files or many. >It is truly random, and even happens immediately after a "normal" (?) >shutdown-startup sequence (or after half an hour of intensive compiling). > >Expect this to stabilise somewhat when the FS buffer cache gets fixed. > [deleted] > >Adam David (adam@veda.is) What are some people exercising to cause these crashes that others aren't? I run the patchkit 0.2.1 kernal on a 486-66 UMC chipset, 400 meg IDE drives, and have ALWAYS been able to compile the kernal and /usr/src completely without problems. _IM_NOT_SAYING_YOU_DID_SOMETHING, I more curious what I'm not doing- don't want to break anything on my system to obtain these 'features'. Curious George, -mc _____________________________________________________________________________ Matt Curfman Almanac Information Archivist matt@gecko.oes.orst.edu Oregon State University Extension