Date: Tue, 02 Apr 2002 21:49:51 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Dag-Erling Smorgrav <des@ofug.org> Cc: Robert Watson <rwatson@FreeBSD.org>, Marcel Moolenaar <marcel@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ia64/ia64 ia64dump.c Message-ID: <20679.1017776991@critter.freebsd.dk> In-Reply-To: Your message of "02 Apr 2002 16:47:51 %2B0200." <xzp3cyeupgo.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <xzp3cyeupgo.fsf@flood.ping.uio.no>, Dag-Erling Smorgrav writes: >Robert Watson <rwatson@FreeBSD.org> writes: >> As long as no one expects the dump format to be static, we should have no >> problem as we migrate to desDUMP. What are the features missing from our >> older dump formats that are required -- the ability to sparsely store >> chunks of address space, etc? > >That, and the ability to save a dump written by a different kernel >than the one currently running, possibly even by a different machine. >Currently, savecore(8) uses the running kernel's idea of dumplo >etc. to locate the dump. This will also rid us of savecore's >dependency on libkvm. *Currently* savecore needs nothing but the diskpartition to pull a kernel dump from any architecture in. *Previously* it behaved as you describe, and I increasingly get the suspicion that you havn't actually looked at the code I committed at all... -- 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 cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20679.1017776991>