From owner-freebsd-arch Sat Mar 30 11:29: 5 2002 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id C65B637B41A for ; Sat, 30 Mar 2002 11:29:02 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2UJSZe7035317; Sat, 30 Mar 2002 20:28:39 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: arch@freebsd.org Subject: Re: Rewamping kernel dumps... In-Reply-To: Your message of "30 Mar 2002 20:25:10 +0100." Date: Sat, 30 Mar 2002 20:28:35 +0100 Message-ID: <35316.1017516515@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: >Poul-Henning Kamp writes: >> Here is what I plan to do to the kernel dumping code. >> [...] > >Sounds good. > >> I understand that various people have some ideas about the layout of >> the dump on the sequential media, this is an area I will not be involved >> in, and I suggest people interested hash this out somehow. > >I uphold my earlier suggestion of a block of metadata formatted as >text. I would probably have stuck it all into tar(1) format from the beginning of the partition. One file for the msgbuf, one file for a ram snapshot etc etc. But as I said, I'm not writing that bit. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message