> It seems to work fine on my system :). One thing I noticed in the startup
> sequence is that with your kernel from a couple weeks ago when it looked
> for core dumps, it would say something like
> savecore: cannot find device 100/114
> followed by what looks like a log entry with the same message. With this
> kernel, it changes the numbers to 72/64. What exactly are those for, and
> are they important? What device are they looking for?

They're the same thing as the proc mismatch. savecore has to go
groveling in the kernel to figure out which device would have gotten a
savecore file. If the kernel in /netbsd is not the running one, then
it'll get nonsense numbers, and generate message like the ones you see.

Take care,

Bill