kernel presentation at ILUG on Sat.

[Dave Hull]

On Mon, 5 May 2003, Charles Steinkuehler wrote:

> This sort of depends on what you're using System.map for.  The most 
> important thing is correctly generating the modules.dep file with depmod.
> 
> Most disto's typically run depmod at startup, and depmod gets it's 
> symbol information from the running kernel by default (via /proc/ksyms), 
> so using the proper System.map file would only be important for running 
> depmod the first time, just after you built a new kernel but before you 
> boot it for the first time.
> 
> If you're running other tools that require access to the kernel symbols 
> through something other than the /proc/ksyms interface, you may need to 
> copy your System.map file somewhere.
> 
> A "make modules_install install" typically works for me, which on RH 
> copies the System.map file to /boot, and even with the default kernel 
> install script will make an initial modules.dep file.
> 
> On my RH box, an rc script then keeps the /boot/System.map symlink 
> pointed to the currently running kernel at every reboot, so no manual 
> installation is necessary.

Charles, this is great information. I'll admit it's been months since I've 
bothered with compiling a kernel, but the System.map question is one I've had 
for a while now, but never bothered to research in depth as my systems 
continued to work just fine.

Where did you grep all of this wonderful information from? Have you been 
reading kernel sources as insomnia treatment?

-- 
Dave Hull
http://insipid.com

Be independent.  Insult a rich relative today.