Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!wupost!uunet!mcsun!uknet!bradford.ac.uk!T.D.G.Sandford From: T.D.G.Sandford@bradford.ac.uk (TDG SANDFORD) Newsgroups: comp.unix.bsd Subject: Re: [386BSD]: Infinite boot loop after applying Beta patches Message-ID: <1992Oct22.162558.14605@bradford.ac.uk> Date: 22 Oct 92 16:25:58 GMT References: <1992Oct22.024713.18413@massey.ac.nz> Organization: University of Bradford, UK Lines: 30 Originator: 90908106@muser Nntp-Posting-Host: muser In article <1992Oct22.024713.18413@massey.ac.nz> G.Eustace@massey.ac.nz (Glen Eustace) writes: >I have just applied the Beta patch kit and recompiled everything. >But something either in the kit or in what I did has broken the >system. The newly installed kernel boots, finds the hardware, does >an fsck and seems to repeatedly find an unreferenced file, I get a # >prompt, then the message Starting network and then the machine does >another hard reboot. This cycle will continue as long as I let it. > >Anyone got any clues as to what has happened ? > >I still have a copy of my original kernel so will put that back in >but I really want to get things going correctly. > >Any help appreciated. > This seems to be quite a common problem when the patchkit is installed (are you listening Terry ? :-) ), so I'll post rather than mailing a reply. You need to boot from your fixit floppy, and run fsck manually from there # fsck /dev/rwd0a Then reboot, and you should be OK. It seems to be a problem with creating a new version of init. The new (patch- kit) init also does not appear to work properly when /etc/rc terminates with a non-zero value, which is what causes the problem (I think). I hope this helps -- Thomas Sandford | t.d.g.sandford@bradford.ac.uk