Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.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: Constant rebooting of hard drive (PLEASE HELP) Message-ID: <1993Mar17.181728.28455@coe.montana.edu> Sender: usenet@coe.montana.edu (USENET News System) Organization: CS References: <C3zK2L.7M7@veda.is> <1o5i6nINNpt@harpo.uccs.edu> Date: Wed, 17 Mar 1993 18:17:28 GMT Lines: 44 In article <1o5i6nINNpt@harpo.uccs.edu> jmward@elbert (Joel M. Ward) writes: >docs. I advise anyone else who is having the reboot problem to get a new >dist.fs from agate. Specifically, /pub/386BSD/386bsd-0.1/unofficial/ >patchkit/dist.fs.pk-0.2 Tis is the dist.fs patched up to 0.2 The biggest >problem with it is that it has the new keyboard fix in it, which will lock >up your machine tighter that a drum if it doesn't work. If you can't use >it, you have to manually copy the new kernel on (the patched kernels are >in the same spot as the patched dist.fs) I had planned to make some new bootables, but we've run into some snags, and until I get them sorted out, people will have to have a little more patience. However, these new bootables will either have a correct keyboard fix, or have patch00083 taken completely out. > > So, my machine only got the constant reboot problem after using it >for a few minutes or after a reboot. This enabled me to copy the new >kernel and init before it flipped out. For those people who have a machine >that locks up with the new keyboard fix and also have the reboot problem >from the start, they can't install 386bsd until they get some patched >dist.fs *without* the new keyboard fix Also, I don't know exactly where >the new init is (i got a uuencoded version from mycroft (don't know his >real name, but thanx!) ) The new init will be located on the new bootables, in /sbin/init. > I also don't know if i need an old copy of init to run the >patchkit. To find out what init does, do a 'man init'. For those of you don't have running systems, init is NOT required for you to run the patchkit. Fixing init allows things to work better when rebooting, shutting down, fscking the disks, etc..... Nate -- osynw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, work #: (406) 994-4836 | I don't think they'll catch on - home #: (406) 586-0579 | Don Hammerstrom