From owner-freebsd-current  Sat Oct 25 19:11:18 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA09218
          for current-outgoing; Sat, 25 Oct 1997 19:11:18 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA09210
          for <current@FreeBSD.ORG>; Sat, 25 Oct 1997 19:11:04 -0700 (PDT)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA20062; Sat, 25 Oct 1997 19:10:55 -0700 (PDT)
To: Brian Somers <brian@awfulhak.org>
cc: Alex <garbanzo@hooked.net>, current <current@FreeBSD.ORG>
Subject: Re: out of swap space causes hang 
In-reply-to: Your message of "Sun, 26 Oct 1997 02:04:42 -0000."
             <199710260204.CAA09303@awfulhak.demon.co.uk> 
Date: Sat, 25 Oct 1997 19:10:55 -0700
Message-ID: <20058.877831855@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> This is annoying if you do actually crash.  Is there any reason why 
> ddb can't reset the screen & keyboard ?  I suspect (although I know 
> next to nothing abouth this) that putting the screen & keyboard into 
> a know state is an ``art'' that depends on knowing what specific 
> hardware is there :-(

You got it.  It's not easy at all (and was first discussed, oh, I'd say
at least 3 years ago :).

					Jordan