From owner-freebsd-bugs Wed Oct 9 12:20: 4 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F8CB37B401 for ; Wed, 9 Oct 2002 12:20:03 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5945E43E42 for ; Wed, 9 Oct 2002 12:20:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id g99JK3Co077970 for ; Wed, 9 Oct 2002 12:20:03 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id g99JK3vg077969; Wed, 9 Oct 2002 12:20:03 -0700 (PDT) Date: Wed, 9 Oct 2002 12:20:03 -0700 (PDT) Message-Id: <200210091920.g99JK3vg077969@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Giorgos Keramidas Subject: Re: bin/43865: unterminated string in rc.conf leaves system unuseable / disk readonly Reply-To: Giorgos Keramidas Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/43865; it has been noted by GNATS. From: Giorgos Keramidas To: Walter Kenaston Cc: bug-followup@freebsd.org Subject: Re: bin/43865: unterminated string in rc.conf leaves system unuseable / disk readonly Date: Wed, 9 Oct 2002 18:21:13 +0300 On 2002-10-09 07:58, Walter Kenaston wrote: > An error in hand-editting /etc/rc.conf - a missing quote character, > in this case - caused the OS to be in an unuseable state after > reboot. (The most this ought to cause is an erorr message and an > unprocessed configuration keyword.) Any ideas how this can be done? This isn't a bug report, but a description of something that is already known and documented. In fact, the documentation includes workarounds for the cases when the administrator has caused something like this to happen by being careless enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message