From owner-freebsd-current@FreeBSD.ORG  Fri Jul  9 13:50:17 2004
Return-Path: <owner-freebsd-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 4C2C016A4CF; Fri,  9 Jul 2004 13:50:17 +0000 (GMT)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E800743D48; Fri,  9 Jul 2004 13:50:16 +0000 (GMT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu
	[152.3.145.30])
	by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i69DoGWg009761
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 9 Jul 2004 09:50:16 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i69DoBQV022090;
	Fri, 9 Jul 2004 09:50:11 -0400 (EDT)
	(envelope-from gallatin)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16622.41619.355522.170000@grasshopper.cs.duke.edu>
Date: Fri, 9 Jul 2004 09:50:11 -0400 (EDT)
To: Robert Watson <rwatson@FreeBSD.org>
In-Reply-To: <Pine.NEB.3.96L.1040709005644.60816F-100000@fledge.watson.org>
References: <Pine.NEB.3.96L.1040709005644.60816F-100000@fledge.watson.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
cc: current@FreeBSD.org
Subject: Re: ethercons updated for -CURRENT
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jul 2004 13:50:17 -0000


Robert Watson writes:
 > having console I/O on the wire isn't such a big deal).  The other major
 > limitation is that it relies on the network stack functioning, so can't be
 > used for very early boot stuff, debugging, etc.  Despite these

How far into a crash does it work?  Eg, will it print the panic
string?  How about a DDB_TRACE? 

Thanks,

Drew