I'll recap for the benefit of other list readers.
Using depmod from modules-1.3.69c I found that forcing the version with
'depmod -a 1.3.75' would create a modules.dep file in /lib/modules/1.3.75
but the dependencies within that file would be for the currently running
kernel version, at that time 1.3.72.
Ok, I think I understand what's going on, but I'm not sure if others will
get it or if it's what you really intended.
I never noticed before that specifying paths in conf.modules would cause
all of depmod's built in paths to be discarded. Hence the new
conf.modules "keep" option!
RTFM flamers: I'm sure I was lazy and didn't read something I should have. ;-)
Anyway, I had paths in conf.modules from before depmod knew about some of
the new 1.3.* directories. This caused depmod to not only discard it's
builtins but disgard the forced version paths that were gathered by the
config_read() function in config.c.
So, for anyone trying to use the forced version feature of depmod-1.3.69c
along with custom paths in /etc/conf.modules, be sure to add "keep" to the
top of the file.
Bjorn, was the disgard of forced version paths intentional here?
___
William E. Roadcap mailto://roadcapw@cfw.com
TITUS Software ftp://titus.cfw.com/pub
Waynesboro, Va (USA) http://www.cfw.com/~roadcapw