Date: 24 Jul 1996 07:02:56 -0500 From: Zach Heilig <zach@blizzard.gaffaneys.com> To: "Michael L. VanLoon -- HeadCandy.com" <michaelv@HeadCandy.com> Cc: "Amir Y. Rosenblatt" <amir@neuron.net>, freebsd-current@freebsd.org Subject: Re: A new twist on the reboot problems Message-ID: <87afwpc0zz.fsf@freebsd.gaffaneys.com> In-Reply-To: "Michael L. VanLoon -- HeadCandy.com"'s message of Wed, 24 Jul 1996 00:04:49 -0700 References: <199607240704.AAA11312@MindBender.HeadCandy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Michael L. VanLoon -- HeadCandy.com" <michaelv@HeadCandy.com> writes: > Incidentally, if you want to be *sure* you capture all panic output, > you might consider putting a comconsole into your kernel and hooking a > serial terminal with scrollback and/or logging (old PC running kermit > works fine) up to be the console. Then, no matter what gets written, > or not written, before the machine freaks out, and before fsck > "cleans" everything, you have it all logged on a separate machine. Speaking of re-routing the console, I noticed this option is called COMconsole (caps for emphasis). Is there anyway to re-route the console to a parallel port? I don't get many console messages (I'm the only one who uses it), so routing them to a printer wouldn't be a bad idea. (Though I'd have to come up with a second parallel port, I don't want to use my laser for console messages... but that's an entirely different problem) -- Zach Heilig (zach@blizzard.gaffaneys.com) | ALL unsolicited commercial email Support bacteria -- it's the | is unwelcome. I avoid dealing only culture some people have! | with companies that email ads.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87afwpc0zz.fsf>