Date: Thu, 24 Apr 2008 11:55:45 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Brooks Davis <brooks@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc/defaults rc.conf Message-ID: <20080424115327.V22132@fledge.watson.org> In-Reply-To: <200804232240.m3NMexsf070598@repoman.freebsd.org> References: <200804232240.m3NMexsf070598@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Apr 2008, Brooks Davis wrote: > brooks 2008-04-23 22:40:59 UTC > > FreeBSD src repository > > Modified files: > etc/defaults rc.conf > Log: > Revert rev 1.332 and keep ddb scripts off by default for now. Minidumps > are more flexable and much text-dump like output can be produced from > them so there's a good argument they are a better default. I think a contrast is being set up here that isn't quite the case: DDB scripts work fine with minidumps *and* textdumps, so the choice is not "DDB scripts or minidumps", it's "textdumps or minidumps". Someone(tm) needs to add support to ddb(8) to extract the DDB textdump buffer from a minidump, in which case you might well want a crash-time script that captures, say, witness output data, and then saves it in the minidump to be extracted after reboot. I'm fine with the default remaining minidumps, but think we should make sure to think of the various elements of my recent DDB work (output capture, scripting, and textdumps) as separable and reusable. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080424115327.V22132>