From owner-freebsd-questions@FreeBSD.ORG Fri Oct 15 20:31:15 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E1CA16A4CE for ; Fri, 15 Oct 2004 20:31:15 +0000 (GMT) Received: from amcuxfw801.amc.af.mil (amcuxns801.amc.af.mil [131.9.254.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1113C43D45 for ; Fri, 15 Oct 2004 20:31:12 +0000 (GMT) (envelope-from david.hauan@fairchild.af.mil) Received: from amc.af.mil ([131.9.19.246]) by fw1.amc.af.mil with ESMTP id i9FKV9aS003325 for ; Fri, 15 Oct 2004 15:31:09 -0500 (CDT) Received: from ([131.9.25.136]) by amcotav802.amc.af.mil with ESMTP id KP-BXW35.20605825; Fri, 15 Oct 2004 13:16:13 -0500 Received: from amcw2ms517.amc.ds.af.mil ([131.9.19.74]) by AMCW2BH506.amc.ds.af.mil with Microsoft SMTPSVC(5.0.2195.6713); Fri, 15 Oct 2004 13:15:47 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 15 Oct 2004 13:15:47 -0500 Message-ID: <59FD5336D1B1FA40AF6DDD241D8DBAC6E01EF2@amcw2ms517.amc.ds.af.mil> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How to recover from setting boot_single=""? Thread-Index: AcSy4JMj3Vy2OM52RlSKxTCIZyNTdgAAhF2w From: "Hauan, David" To: "David Kurtz" , X-OriginalArrivalTime: 15 Oct 2004 18:15:47.0680 (UTC) FILETIME=[FE95CE00:01C4B2E2] Subject: RE: How to recover from setting boot_single=""? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2004 20:31:15 -0000 > -----Original Message----- > From: David Kurtz [mailto:davidkurtz@mac.com]=20 > Sent: Friday, October 15, 2004 10:58 AM > To: freebsd-questions@freebsd.org > Subject: How to recover from setting boot_single=3D""? >=20 >=20 > Short story: I placed a single line, >=20 > boot_single=3D"" >=20 > into the previously empty file /boot/loader.conf and now my=20 > machine boots with an extremely limited read-only volume. >=20 > How do I get my old boot behavior back? try cntrl+d that show bring you up to multi user mode with read/write slices. >=20 >=20 > Long story: I was muddling through updating the kernel and=20 > world for the first time, going from FreeBSD 5.1 =3D> 5.2.=20 > Following instructions in /usr/src/UPDATING I made backups,=20 > made buildworld, etc. until it got to the point where it says=20 > reboot in single user. >=20 > Never having done that, I tried first by "reboot"ing, but for=20 > some reason my USB keyboard doesn't get power until further=20 > on in the boot cycle, so I couldn't just "press 4." I looked=20 > through the docs and found instruction saying that I should=20 > set boot_single. I'm guessing I should have set it to=20 > something other than "", which is just copied from=20 > /boot/defaults/loader.conf. >=20 > So, a couple more questions: what is this limited read-only=20 > mode exactly? Where are my files (e.g. /usr is empty)? What=20 > should I have done? Is it possible to back out? >=20 > It's a personal sandbox, and everything I need is already=20 > safely backed up; if I need to just blast the whole system=20 > with a CD install, I can do that. But I am curious to know if=20 > it's possible to u-turn in this cul-de-sac. Apparently, I=20 > know just enough to get myself into trouble, but not enough=20 > to get out. _______________________________________________ > freebsd-questions@freebsd.org mailing list=20 > http://lists.freebsd.org/mailman/listinfo/free> bsd-questions >=20 > To unsubscribe, send any mail to=20 > "freebsd-questions-unsubscribe@freebsd.org" >=20