*BSD News Article 12853


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!europa.eng.gtefsd.com!emory!ogicse!usenet.ee.pdx.edu!acacia!rgrimes
From: rgrimes@acacia (Rodney W. Grimes)
Newsgroups: comp.os.386bsd.questions
Subject: Re: PC keeps rebooting after install
Message-ID: <1np5io$3gg@walt.ee.pdx.edu>
Date: 12 Mar 93 05:03:20 GMT
Article-I.D.: walt.1np5io$3gg
References: <C3r7MJ.734@sugar.neosoft.com>
Organization: Portland State University
Lines: 31
NNTP-Posting-Host: acacia.cs.pdx.edu

peter@NeoSoft.com (Peter da Silva) writes:
: In article <1993Mar11.010233.29306@netcom.com> pascal@netcom.com (Richard Childers) writes:
: > mycroft@hal.gnu.ai.mit.edu (Charles Hannum) writes:
: > >When fsck corrects an error on booting, a certain infamous bug in init
: > >will cause the boot sequence to continue even as it's trying to reboot.
: 
: > Can't this be worked around with an explicit "sync ; sync ; sync ; halt" ?
: 
: An even simpler solution, which is handy in other cases, is put a loop like
: this at the start of /etc/rc:
: 
: 	for i in 10 9 8 7 6 5 4 3 2 1
: 	do
: 		echo -n "   ^MDisk check in $i seconds..."
: 		sleep 1
: 	done
: 
: That gives you a nice safe place to ^C into single-user mode anyway.

The proper way to force the system to enter single user mode is to type ^C
during the fsck, this causes fsck to exit with a bad status.  This is
documeted some place in th FM, I just can't remeber where.  It well not
cause fsck to stop what it is doing, it well complete the fsck and then
no matter if it succeded or not it returns with a status code of 12,
which the /etc/rc script interpets for us.

: -- 
: Peter da Silva.  <peter@sugar.neosoft.com>.
:  `-_-'   Oletko halannut suttasi tdnddn?
:   'U`    
: Tarjoilija, tdmd ateria eldd vield.