RE: modules.conf newer than

[Patrick Nelson <pnelson neatech com>]

Thanks.

ABrady wrote:
------------------
Any time you do something that make a change in modules.conf, it changes the
date. The system sees that the date is newer than the modules.dep file for
that kernel and issues a warning. The warning is nothing to worry about
usually. But, it could be an indication that someone has been monkeying wiht
the modules that are being loaded.

The changes can be caused by things like adding hardware, removing hardware,
configuring sound, etc, plus anything in which you manually edit the file.

Fixing it is fine. Whether or not it _should_ have had a newer date is
something you might need to be concerned about. But, I've personally never
had anybody toying with the file that I wasn't aware of. Actually, I'm the
only one who ever does outside of kudzu. Kudzu can make changes, but you'll
know about those when you boot (asks to add/remove hardware configuration).

----- Original Message -----
From: Patrick Nelson <pnelson neatech com>
To: RedHat List (E-mail) <redhat-list redhat com>
Sent: Friday, August 31, 2001 7:36 PM
Subject: modules.conf newer than


> I keep getting the message:
>
> Note:  /etc/modules.conf is more recent than
> /lib/modules/2.4.2-2/modules.dep
>
> So I did a depmod and this seems to have made it go away.  I don't
> understand what this means and so I must ask what causes that error
(besides
> the obvious) and did I do the right thing in fixing it?
>



_______________________________________________
Redhat-list mailing list
Redhat-list redhat com
https://listman.redhat.com/mailman/listinfo/redhat-list