From owner-freebsd-current@FreeBSD.ORG Fri Dec 2 11:01:15 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A25C16A41F for ; Fri, 2 Dec 2005 11:01:15 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id E69EE43D5E for ; Fri, 2 Dec 2005 11:01:13 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 02 Dec 2005 11:01:11 -0000 Received: from v208-017.vps.tuwien.ac.at (EHLO v208-017.vps.tuwien.ac.at) [128.131.208.17] by mail.gmx.net (mp035) with SMTP; 02 Dec 2005 12:01:11 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: Robert Watson In-Reply-To: <20051202103751.T83839@fledge.watson.org> References: <20051202103751.T83839@fledge.watson.org> Content-Type: text/plain Date: Fri, 02 Dec 2005 12:01:07 +0100 Message-Id: <1133521267.1085.2.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: current@FreeBSD.org Subject: Re: After crash, / comes up mounted read-only, but in multiuser; mfs /tmp? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 11:01:15 -0000 On Fri, 2005-12-02 at 10:41 +0000, Robert Watson wrote: > While testing the new DRM update (went badly :-), I crashed my system and > had to power cycle it. When it came back up, not surprisingly, the file > systems weren't clean. When I reached a login prompt, I logged in to > modify /etc/rc.conf, and to my surprise, was told that /etc/rc.conf wasn't > writable. Turns out it was because / was mounted read-only: This was reported some days ago in the thread "problems with -current" http://lists.freebsd.org/pipermail/freebsd-current/2005-November/058525.html No fix yet though.