From owner-freebsd-hackers  Sat Apr 29 04:57:22 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id EAA23220
          for hackers-outgoing; Sat, 29 Apr 1995 04:57:22 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA23211
          for <hackers@FreeBSD.org>; Sat, 29 Apr 1995 04:57:03 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA22170; Sat, 29 Apr 1995 21:53:26 +1000
Date: Sat, 29 Apr 1995 21:53:26 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199504291153.VAA22170@godzilla.zeta.org.au>
To: jkh@time.cdrom.com, paul@isl.cf.ac.uk
Subject: Re: What I'd *really like* for 2.0.5
Cc: hackers@FreeBSD.org, nate@trout.sri.MT.net, phk@ref.tfs.com
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>> How are we going to get debugging info back from users?
>> 
>> Currently we can ask them to send the output of dmesg to see what's happening
>,
>> telling them to boot -c and *copy down the values* is a lousy argument in
>> my book.

>Yoo hoo!  Paul!  Are you listening!

>Repeat after me:

>	boot -v
>	dmesg

This fails if the boot panics of if there is no writable filesystem for
placing the output from dmesg.

Bruce