Date: 12 Mar 2002 22:07:38 +0100 From: Dag-Erling Smorgrav <des@ofug.org> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: arch@FreeBSD.ORG, peter@FreeBSD.ORG, jake@FreeBSD.ORG Subject: Re: dumpsys() rewrite Message-ID: <xzphenltrz9.fsf@flood.ping.uio.no> In-Reply-To: <14701.1015966841@critter.freebsd.dk> References: <14701.1015966841@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp <phk@critter.freebsd.dk> writes: > `) Device driver or proxy for it register their ability to do dumps > with the kernel, informing the kernel about the number of bytes > they have room for (and the sector size of the media ?). Umm, no - it's simpler to just have a driver-provided helper for disk_dumpcheck(), rather than a system for registering dump-capable devices. BTW, this reminds me that the device should "know" that it's the current dump device, so it can clear dumpdev if it disappears (e.g. you 'camcontrol stop' the disk and remove it from the enclosure...) > > c) the on-disk format will be as follows: > Make it XML while we're at it ? All it costs in the kernel is > a bit more text in the printfs. It's not hierarchical, and therefore won't benefit from being expressed in XML. It'll just add unnecessary complexity to savecore(1). DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzphenltrz9.fsf>