From owner-freebsd-current@FreeBSD.ORG Fri Sep 26 12:07:17 2003 Return-Path: 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 53C0716A4B3 for ; Fri, 26 Sep 2003 12:07:17 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B54644039 for ; Fri, 26 Sep 2003 12:06:54 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h8QJ6iLG079578; Fri, 26 Sep 2003 21:06:49 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: Jonathan Fosburgh From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 26 Sep 2003 14:03:28 CDT." <200309261403.28676.syjef@mdanderson.org> Date: Fri, 26 Sep 2003 21:06:44 +0200 Message-ID: <79577.1064603204@critter.freebsd.dk> cc: current@freebsd.org Subject: Re: cannot boot -s X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 26 Sep 2003 19:07:17 -0000 In message <200309261403.28676.syjef@mdanderson.org>, Jonathan Fosburgh writes: >On Friday 26 September 2003 01:13 pm, Cameron Murdoch wrote: >> I have the same here from this morning's -current but I also see this on >> boot up: >> >> *snip* >> mounting root from ufs:/dev/ad0s2a >> pid 87 (fsck_ufs), uid 0: exited on signal 8 >> pid 88 (fsck_ufs), uid 0: exited on signal 8 >> > >I noticed the same thing when I did not try to boot into single-user mode. Try to pull in the commit I just did to syscons, I looks like I messed something up somewhere :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.