From owner-freebsd-questions@FreeBSD.ORG Wed Dec 1 00:35:41 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 4E77D16A4CE for ; Wed, 1 Dec 2004 00:35:41 +0000 (GMT) Received: from lakermmtao06.cox.net (lakermmtao06.cox.net [68.230.240.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF74043D41 for ; Wed, 1 Dec 2004 00:35:40 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.24]) by lakermmtao06.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041201003539.QZJN4767.lakermmtao06.cox.net@dolphin.local.net>; Tue, 30 Nov 2004 19:35:39 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id iB10ZbcC096546; Tue, 30 Nov 2004 18:35:37 -0600 (CST) (envelope-from conrads@cox.net) Date: Tue, 30 Nov 2004 18:35:32 -0600 From: "Conrad J. Sabatier" To: "David Kelly" Message-ID: <20041130183532.05a1960a@dolphin.local.net> In-Reply-To: <4105.207.111.173.106.1101855843.squirrel@webmail.dogbark.com> References: <41ACF2BD.9000706@earthlink.net> <4105.207.111.173.106.1101855843.squirrel@webmail.dogbark.com> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: mikegoe@earthlink.net cc: questions@freebsd.org Subject: Re: Help with rc.conf error, read-only file system 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: Wed, 01 Dec 2004 00:35:41 -0000 On Tue, 30 Nov 2004 17:04:03 -0600 (CST), "David Kelly" wrote: > > I've been away from FreeBSD for a while and I just loaded 5.3 and > > inavertently made an error in rc.conf. Now when I boot up the file > > system is read-only and I haven't been able to edit rc.conf to > > correct the simple mistake. Any help would be appreciated. Once you reach the single-user shell prompt, do this: mount -u / (changes root filesystem from read-only to read/write) mount -a (attempts to mount any other filesystems in /etc/fstab) If any filesystem fails to mount, run "fsck -y" on it, then try mounting it again. > "mount -a" to attempt mounting all filesystems. Use "fsck -y" on the > ones mount refuses to do. These days "background fsck" usually applies > automatically meanwhile one gets to use the filesystems instantly. Not in single-user mode it doesn't. > Just for fun you can type "mount" by itself at any time to list > mounted filesystems and some interesting properties such as R/W and > softupdates. > > Manually you could remount root with "mount /" to make it R/W. Then > "mount/usr" so as to have vi, which will complain (but still function) > about/var not being mounted and therefore no backup copy for crash > recovery. > > Use "exit" to resume multiuser boot out of single user. > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > -- Conrad J. Sabatier -- "In Unix veritas"