Unless it has changed recently, the system I just installed last month
actually looks for it in /usr/src/linux, not /boot. It still complains
during boot even though I actually have one there, presumably it is looking
before filesystems are mounted.
Ugh, then it's a duet between /sbin/module-update and /sbin/rc. Looking in /usr/src/linux is just plain wrong. If for any reason I build a kernel, but don't install it, then it's not just looking for data from an unmounted filesystem (/boot or /usr) but it's also looking for the *wrong* System.map. I'm going to file a bug on this. I can imagine cases where this might leave a system hosed.
dcm
