*BSD News Article 12867


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!paladin.american.edu!news.univie.ac.at!fstgds15.tu-graz.ac.at!fstgds01.tu-graz.ac.at!not-for-mail
From: chmr@edvz.tu-graz.ac.at (Christoph Robitschko)
Newsgroups: comp.os.386bsd.questions
Subject: Re: PC keeps rebooting after install
Date: 12 Mar 1993 17:56:18 +0100
Organization: Technical University of Graz, Austria
Lines: 32
Message-ID: <1nqfbiINNndf@fstgds01.tu-graz.ac.at>
References: <1np5io$3gg@walt.ee.pdx.edu>
NNTP-Posting-Host: fstgds01.tu-graz.ac.at
X-Newsreader: TIN [version 1.1 PL7]

In article <1np5io$3gg@walt.ee.pdx.edu> rgrimes@acacia (Rodney W. Grimes) writes:
-> peter@NeoSoft.com (Peter da Silva) writes:
-> : 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.


Wrong. If you send fsck a INTR signal (^C), it will exit immediately with
an exit code reporting failure. If you send it a QUIT signal (^\), it
will finish the diskcheck and then exit with a failure status. This is
documented in the fsck(8) man page.

And *the proper way to enter singleuser mode* (TM) is to use Julian's
bootblocks and enter "-s" to the prompt. Thanks, Julian (if you can hear me) !



							Christoph