On Thu, 18 Nov 1999, Richard Adams wrote:
> 1) depmod used an old System.map,! Why is that,? possably because
> when the new kernel was compiled you forgot to copy
> /usr/src/linux/System.map to its final resting place, normaly that
> would be /boot, or even "/" depending on which distro one has, and
> what one has defined in /etc/lilo.conf
>
> Solution to (1) is copy /usr/src/linux/System.map to the place
> defined in /etc/lilo.conf.
depmod only uses System.map when it's explicitly requested to. Normally it
uses /proc/ksyms. AFAIK, lilo.conf has no settings related to System.map,
and the file is really only useful for debugging kernel panics, oopses,
and the like. (That's actually really useful when it's needed.)
The old modules are usually the culpret... CONFIG_MODVERSIONS may also do
it.
I've seen this before, but never seen any associated problems with it.
--
Tom Rothamel - http://onegeek.org/~tom/ ------------ Lilug Veep - Using Linux
"Are we just machines? With veins instead of wiring, brains
instead of of CPUs, and life insurance instead of warranties?"
- Torg, "Sluggy Freelance"
