From owner-freebsd-current Mon Apr 22 15:03:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA17336 for current-outgoing; Mon, 22 Apr 1996 15:03:13 -0700 (PDT) Received: from xi.dorm.umd.edu (root@xi.dorm.umd.edu [129.2.152.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA17328 for ; Mon, 22 Apr 1996 15:03:11 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by xi.dorm.umd.edu (8.7.5/8.6.12) with SMTP id SAA05494; Mon, 22 Apr 1996 18:02:57 -0400 (EDT) Date: Mon, 22 Apr 1996 18:02:56 -0400 (EDT) From: Sujal Patel X-Sender: smpatel@xi.dorm.umd.edu To: "Marc G. Fournier" cc: current@freebsd.org Subject: Re: request for a new "feature" as regards DDB In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, Marc G. Fournier wrote: > I happened to be off of vt0 when it died, with no way to > switch to vt0 and see what ddb was showing, and since I had to > cold boot the machine as a result, couldn't even get a core dump :( > > So...any way of having an auto-switch to vt0 if the system > crashes with DDB enabled? While we're talking about DDB, can't we have it timeout in 30s if you don't hit a key (and then generate a core dump). What about making DDB a LKM also? Whenever I find myself using DDB, I know that the system is going to panic, not everyone needs DDB loaded at all times (and rebuilding kernels is such a pain). Sujal