From owner-freebsd-questions  Mon Jul  7 19:15:55 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA22092
          for questions-outgoing; Mon, 7 Jul 1997 19:15:55 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA22087
          for <freebsd-questions@FreeBSD.ORG>; Mon, 7 Jul 1997 19:15:52 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id TAA03145;
	Mon, 7 Jul 1997 19:17:21 -0700 (PDT)
Message-Id: <199707080217.TAA03145@implode.root.com>
To: David Lowe <dlowe@sirius.com>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Logging kernel panics 
In-reply-to: Your message of "Mon, 07 Jul 1997 15:54:23 PDT."
             <Pine.NXT.3.95q.970707152905.13964A-100000@ds9> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 07 Jul 1997 19:17:21 -0700
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Is there some fairly reliable way of storing panic messages, short of
>logging all console output via a serial port?  We already have a serial
>console, but the darned thing doesn't have any logging at all.

   Try building your bootblocks with the "BOOT_FORCE_COMCONSOLE" option, and
then re-installing them with disklabel -B <disk>. This will cause all console
output to go to the serial port.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project