Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!ncar!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!brunix!cs.brown.edu!Mark_Weaver
From: Mark_Weaver@brown.edu
Subject: Re: NetBSD 0.9 boot single-user with mount rw
In-Reply-To: "Alex R.N. Wetmore"'s message of Wed, 6 Oct 1993 23:32:32 -0400
Message-ID: <MARK_WEAVER.93Oct7003620@tonto-slip9.cis.brown.edu>
Sender: news@cs.brown.edu
Organization: Brown University Department of Computer Science
References: <gggsrEW00WBM8GcHYY@andrew.cmu.edu>
Date: Thu, 7 Oct 1993 04:36:20 GMT
Lines: 28
In article <gggsrEW00WBM8GcHYY@andrew.cmu.edu> "Alex R.N. Wetmore" <aw2t+@andrew.cmu.edu> writes:
> As for X loosing the keyboard, I have only seen this when /etc/daily
> gets run, which sends a sighup to syslog, which resets the keyboard mode
> on the console, killing the X keyboard mode. I have just stopped
> leaving X running all the time (ie over night), which worked for me.
> Sounds like you might be seeing something else though.
You can solve the sighup problem by keeping /dev/console open by
by something other than just syslogd. Running xconsole should do this,
for instance. It will be fixed in XFree86 2.0, when it comes out.
> As for single user mode, after bringing it up, run fsck on the main
> partition (fsck /dev/wd0a) and if there aren't any errors do a mount -u
> /dev/wd0a /, which will mount the partition read-write. If the fsck
> doesn't work okay reboot the machine and do it again.
A nice easy way that does it for me is to do:
umount -a
mount -a
Which is essentially what the /etc/rc does after the fsck anyway.
Mark
--
--------------------------------------------------------------------
Email: Mark_Weaver@brown.edu | Brown University
PGP Key: finger mhw@cs.brown.edu | Dept of Computer Science