Submitted 29-Jun-00 by Bob Puff@NLE:
> I was getting a ton of "conf.modules is more recent than ..."
> messages. I found someone's suggestion of simply changing the
> date/time on the referenced file, and it went away. But why was this
> check done? It filled my logs with TONS of these messages.
This check is done everytime there is a need to load a module or check
to see if a module needs to be loaded. Whoever suggested changing the
date of the file was simply wrong. The correct ssolution is to run
"/sbin/depmod -a" to properly update the modules.dep.
HTH
--
_
_|_|_
( ) * Anton Graham
/v\ / <[EMAIL PROTECTED]>
/( )X
(m_m) GPG ID: 18F78541
Penguin Powered!
