Re: misc/38425 (savecore confused if getbootfile(3) fails)

[yamt%mwd.biglobe.ne.jp@localhost (YAMAMOTO Takashi)]

The following reply was made to PR misc/38425; it has been noted by GNATS.

From: yamt%mwd.biglobe.ne.jp@localhost (YAMAMOTO Takashi)
To: tls%rek.tjls.com@localhost
Cc: dogcow%babymeat.com@localhost, gnats-bugs%NetBSD.org@localhost, 
misc-bug-people%netbsd.org@localhost,
        gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, 
simonb%NetBSD.org@localhost
Subject: Re: misc/38425 (savecore confused if getbootfile(3) fails)
Date: Sun, 14 Jun 2009 22:03:52 +0000 (UTC)

 hi,
 
 > On Sun, Jun 14, 2009 at 06:50:17AM -0700, Tom Spindler wrote:
 >> I don't know about any of you, but savecore completely fails to work
 >> for me after 1.78 savecore.c; in particular, failing to set the
 >> booted kernel causes check_space to die a painful death:
 > 
 > I'll poke at it some more.  This works in our local tree -- maybe I
 > missed a change when integrating it back into NetBSD.
 > 
 > It is absolutely, positively *not* the right solution to cause any
 > of these utilities to try to know the kernel name.  Any operation
 > they have any business doing can be done via /dev/ksyms -- the
 > question is where I missed one or more references to the kernel name
 > that were exposed beyond libkvm, which correctly defaults to use
 > /dev/ksyms if some other kernel name is not rammed down its throat.
 > 
 > Thor
 
 talking about the right solution, savecore should not use /dev/ksyms
 or info from the live kernel at all.  we should store necessary info
 in the dump itself.  (as freebsd does?)
 
 YAMAMOTO Takashi