Date: Mon, 1 Apr 2002 19:01:07 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: Dag-Erling Smorgrav <des@ofug.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sys kerneldump.h Message-ID: <20020402030107.GA315@dhcp01.pn.xcllnt.net> In-Reply-To: <xzpy9g7bjy6.fsf@flood.ping.uio.no> References: <5634.1017668341@critter.freebsd.dk> <xzpy9g7bjy6.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 01, 2002 at 03:57:21PM +0200, Dag-Erling Smorgrav wrote: > > > Savecore dumps the header in ascii in the .info file, and I find it > > unlikely that people will do things like "grep dump /dev/ad0s1b" so > > I decided that a binary format was OK for on-disk use. > > A binary format makes future extensions more difficult. As it is, > your dump header already needs modification (or extension) to cope > with the sparc64 platform which has discontiguous physical memory, > while my proposed text format already handled that case. I've been thinking about this as well. And the first thing that came to mind was to use the ELF format. I don't know if it's feasible or beneficial, but it's a thought I find interesting enough to have it mature for a while. Having a machine independent dump header seems to give the greatest flexibility. Especially the size of the dump header should be the same if you want to work backwards from the end of the device. Savecore does not have any MD code, and I rather like it. Whether the on disk format is text or binary mostly depends on whether you want to be immune to endianness. Other than that there's no big difference. Just my $0.02 -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net 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?20020402030107.GA315>