Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA7186 ; Mon, 18 Jan 93 10:49:40 EST
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!spool.mu.edu!agate!doc.ic.ac.uk!uknet!cf-cm!myrddin.isl.cf.ac.uk!paul
From: paul@isl.cf.ac.uk (Paul)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD INIT Problem?
Message-ID: <1993Jan19.105717.24056@cm.cf.ac.uk>
Date: 19 Jan 93 10:57:15 GMT
References: <C12nrG.19p@crucible.demon.co.uk>
Sender: news@cm.cf.ac.uk (Network News System)
Organization: Intelligent Systems Lab, ELSYM, Universiity of Wales, College of
Cardiff.
Lines: 18
This looks like the bug caused by the dodgy 2nd hard disk patch. I'm
not sure why using the original init would help though.
Back out patch 21 (and 38 which depends on it) and try again. You may
have to use fsck initially to get the filesystem cleaned up but after
that it should be ok.
Init still isn't halting properly, it continues running rc (hence the
"Starting network" message) even though fsck found an error.
Don't worry about fsck clearing errors and then rebooting, this is
normal. However, it should only reboot once. The continuous cycle
problem should go away when you back out the above patch.
--
Paul Richards, University of Wales, College Cardiff
JANET:paul@uk.ac.cf.isl Internet:paul@isl.cf.ac.uk
UUCP: paul@cf-isl.UUCP or ...!uunet!mcsun!uknet!cf!isl!paul