From owner-freebsd-hackers Thu Feb 1 23:46:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id AB80237B4EC for ; Thu, 1 Feb 2001 23:46:18 -0800 (PST) Received: from [66.27.65.184] (we-66-27-65-184.we.mediaone.net [66.27.65.184]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id XAA23111; Thu, 1 Feb 2001 23:45:49 -0800 (PST) User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Thu, 01 Feb 2001 23:45:46 -0800 Subject: Re: capturing an early kernel dump From: Lars Eggert To: Peter Wemm , Lars Eggert Cc: Message-ID: In-Reply-To: <200102020739.f127dUW23005@mobile.wemm.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Lars Eggert wrote: >> How do I capture an early kernel dump (before rc executes and sets >> dumpdev)? > > How early? We could dump if you were prepared to hardwire in the minor and > major device numbers to get to the devsw[] vectors and manually set the > offsets. Not that early :-) I'm playing with the networking code; by that time, the disks should have been probed. Is there an "easy way" to configure a dump device after the disks are up? Thanks, Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message