From owner-freebsd-questions@FreeBSD.ORG Tue Nov 30 23:04:04 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 B725116A4CE for ; Tue, 30 Nov 2004 23:04:04 +0000 (GMT) Received: from lex.sublimemail.com (lex.sublimemail.com [66.45.27.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E69C43D45 for ; Tue, 30 Nov 2004 23:04:04 +0000 (GMT) (envelope-from dkelly@hiwaay.net) Received: from dogbark.net (localhost [127.0.0.1]) by lex.sublimemail.com (Postfix) with SMTP id CB0B318CF3B; Tue, 30 Nov 2004 17:04:03 -0600 (CST) Received: from 207.111.173.106 (SquirrelMail authenticated user n4hhe) by webmail.dogbark.com with HTTP; Tue, 30 Nov 2004 17:04:03 -0600 (CST) Message-ID: <4105.207.111.173.106.1101855843.squirrel@webmail.dogbark.com> Date: Tue, 30 Nov 2004 17:04:03 -0600 (CST) From: "David Kelly" To: In-Reply-To: <41ACF2BD.9000706@earthlink.net> References: <41ACF2BD.9000706@earthlink.net> X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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: Tue, 30 Nov 2004 23:04:04 -0000 > 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. "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. 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.