Path: utzoo!yunexus!ists!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!samsung!cs.utexas.edu!rutgers!cmcl2!panix!jsb
From: jsb@panix.UUCP (J. S. B'ach)
Newsgroups: comp.sys.next
Subject: Re: kernel corruption on 330Mb hd???
Message-ID: <534@panix.UUCP>
Date: 17 Nov 89 13:49:50 GMT
Article-I.D.: panix.534
References: <17504@kuhub.cc.ukans.edu> <12609@cit-vax.Caltech.Edu>
Reply-To: jsb@panix.UUCP (J. S. B'ach)
Organization: Panix, NYC
Lines: 14

In article <12609@cit-vax.Caltech.Edu> madler@tybalt.caltech.edu.UUCP (Mark Adler) writes:
)
)Yep, I've seen just that happen a few times to some NeXT's here.  It seems
)to be contagious since it happens to a few machines connected over ethernet
)at the same time (but not all of them?).  It's never happened (fingers crossed)
)to my standalone NeXT (no net connection).  I have no suggestions.
Well it happened to mine.  And I was booting from the optical drive.  The fix was
to resore from the hard drive.  NeXT is aware of the bug and asked to be sent
copies of the corrupt kernel to help them debug.
-- 
	rutgers!cmcl2!panix!jsb  	 or (more reliably) uunet!actnyc!jsb
"There aren't enough men around.  Every time there's a plane accident, it's 100 men
 dead or it's a troop transport, and I literally think, 'Why couldn't some women
 have been on that flight?'" - Helen Gurley Brown