From owner-freebsd-i386@FreeBSD.ORG Thu Nov 4 16:50:34 2004 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA90116A4CE for ; Thu, 4 Nov 2004 16:50:34 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7686E43D46 for ; Thu, 4 Nov 2004 16:50:34 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id iA4GoYeV021549 for ; Thu, 4 Nov 2004 16:50:34 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA4GoYNi021548; Thu, 4 Nov 2004 16:50:34 GMT (envelope-from gnats) Date: Thu, 4 Nov 2004 16:50:34 GMT Message-Id: <200411041650.iA4GoYNi021548@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Ceri Davies Subject: Re: i386/61443: FreeBSD 5.2-RELEASE installation stops at /stand/sysinstall X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Ceri Davies List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 16:50:34 -0000 The following reply was made to PR i386/61443; it has been noted by GNATS. From: Ceri Davies To: FreeBSD Gnats Submit Cc: Subject: Re: i386/61443: FreeBSD 5.2-RELEASE installation stops at /stand/sysinstall Date: Thu, 4 Nov 2004 16:45:01 +0000 Adding to audit trail: On Thu, Nov 04, 2004 at 05:37:51PM +0100, Eivind Olsen wrote: Ceri Davies wrote: >Synopsis: FreeBSD 5.2-RELEASE installation stops at /stand/sysinstall > >State-Changed-From-To: open->feedback >State-Changed-By: ceri >State-Changed-When: Wed Nov 3 21:57:06 GMT 2004 >State-Changed-Why: >Is this reproducible with a 5.3-RC ? > >http://www.freebsd.org/cgi/query-pr.cgi?pr=61443 I have now tested this on the same computer and I don't see the problem anymore (testing with 5.3-RC2 now), so something seems to have been fixed since 5.2-RELEASE. :) -- Regards / Hilsen Eivind Olsen