Subject: Re: kdump dependency on kernel, ktrace id portability
To: Greywolf <>
From: Nathan J. Williams <>
List: tech-kern
Date: 01/09/2004 14:38:46
Greywolf <> writes:

> Thus spake Nathan J. Williams ("NJW> ") sometime Today...
> NJW> It still doesn't solve much of a problem. Having to rebuild kdump
> NJW> occasionally when you're hacking on the kernel just isn't much of a
> NJW> burden.
> It's not a huge burden, but it's sufficiently annoying to qualify as
> a hemorrhoid.  Every time I build a new kernel, to have to go and rebuild
> kdump is kind of a drag.

It's not every time you build a new kernel, just every time you build
a new kernel with new syscalls and discover subsequently that kdump
isn't displaying all the syscalls. *then* you can go rebuild kdump to
see the things you're missing. How often does that happen?

        - Nathan