Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!howland.reston.ans.net!cs.utexas.edu!news.tamu.edu!mbreed
From: mbreed@cs.tamu.edu (Michael B. Reed)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Booting into Single User Mode
Date: 27 Jun 1996 14:07:42 GMT
Organization: Texas A&M Department of Computer Engineering, College Station, TX
Lines: 23
Message-ID: <4qu4je$bf6@news.tamu.edu>
References: <DtM9Az.Equ@caprica.com> <4qt6lg$dkd@symiserver2.symantec.com>
NNTP-Posting-Host: photon.cs.tamu.edu
In <DtM9Az.Equ@caprica.com>, ktaira@caprica.com (Kenneth Taira) writes:
> After a
>number of attempts to use Control-C to force system into Single-usr mode,
Better yet, boot with the -s flag. If I'm not mistaken, there should be
a page for boot in section 8 of the man pages. This should contain a list
of boot flags...it's been a while since I've read it, though.
In addition to having to manually mount /usr, as described by some of the
other posts, you'll need to change the root partition to read/write mode,
as it's mounted as read-only at this point. I believe the appropriate
form of mount in this case is:
mount -u -w /
Check mount(8) for details. If you don't do this, vipw won't be able to
write the updated /etc/passwd and the database files.
--
-Brad Reed mbreed@tamu.edu http://www.cs.tamu.edu/people/mbreed/
TAMU Prisoner, August 31, 1992 - December 20, 1996