Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!magnesium.club.cc.cmu.edu!news.sei.cmu.edu!bb3.andrew.cmu.edu!andrew.cmu.edu!aw2t+ From: "Alex R.N. Wetmore" <aw2t+@andrew.cmu.edu> Newsgroups: comp.os.386bsd.bugs Subject: Re: NetBSD 0.9 boot single-user with mount rw Date: Wed, 6 Oct 1993 23:32:32 -0400 Organization: Junior, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA Lines: 25 Message-ID: <gggsrEW00WBM8GcHYY@andrew.cmu.edu> NNTP-Posting-Host: po5.andrew.cmu.edu In-Reply-To: <tmcCEI6uw.9nJ@netcom.com> Excerpts from netnews.comp.os.386bsd.bugs: 7-Oct-93 NetBSD 0.9 boot single-user.. by Thomas M. Crockett@netco > Anyway, I had this problem while in X with thekeyboard freezing after > awhile. Reading thru the bsd news groups I saw mention of a "fix' that > seemed to fit my situation. This consisted of turning the vga getty > off in /etc/ttys. And you know, it seemed to work! So well in fact > that I forgot to undo the fix before exiting X. And then soemthing had > died because there was no terminal to return to... OK, boot single > user (-s) which then of course brings up the root partition in > read-only mode! Wonderful, except that what I need to fix is /etc/ttys 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. 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. happy hacking! alex