Subject: Re: Kernel image in filesystem, netstat(1)
To: None <tech-kern@netbsd.org>
From: Jukka Salmi <j+nbsd@2005.salmi.ch>
List: tech-kern
Date: 06/16/2005 02:24:33
Nino Dehne --> tech-kern (2005-06-16 01:56:33 +0200):
> Hi,
> 
> I am currently mildly baffled as to why netstat(1) for example needs
> an image of the running kernel in the filesystem. I figured that, since
> the kernel is loaded to memory anyway, it wouldn't need a separate
> image on disk.
> 
> The puzzling thing for me is that netstat even fails with a gzipped
> kernel image.
> 
> This led me to think that there might be some option that I stripped
> while being overly minimalistic in creating the kernel config (3.0_BETA
> with Peter Postma's altq.diff for netbsd-3 BTW).
> 
> The config I currently use is as follows. It is the bare minimum that
> suits my needs to run a WRAP embedded board successfully.
> 
> The system is run from an embedded filesystem image which currently
> contains a link from /netbsd to mnt/netbsd. The kernel is booted off
> of a compact flash image which gets mounted on /mnt, thus completing
> the circle. I would rather not have to 1) mount the CF card at all
> 2) keep the kernel uncompressed.
> 
> Is there a way to remove the dependency on an uncompressed image of
> the running kernel duplicated in the filesystem?

See ksyms(4).


HTH, Jukka

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~