[SLE] Who makes /lib/modules/xxx/modules.dep?
Does anyone know how the file /lib/modules/2.2.x/modules.dep is created? I did a `make modules modules_install' with a stock (not SuSE) 2.2.15 kernel and found that I still had an older version of that file, according to the date. I then tried deleting it and rebooting. I got a new copy of the older version. Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Paul" == Paul W Abrahams
writes:
> Does anyone know how the file /lib/modules/2.2.x/modules.dep is > created? I did a `make modules modules_install' with a stock > (not SuSE) 2.2.15 kernel and found that I still had an older > version of that file, according to the date. I then tried > deleting it and rebooting. I got a new copy of the older > version. man depmod Charles -- ===================================================== One Net to rule them all, One Net to find them, One Net to bring them all, and with Linux bind them. ===================================================== -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
erm... depmod -a I believe is the actual command to remake modules.dep
this should be done within the boot script, ie, /sbin/init.d/boot
kw
/* Keith Warno
** Developer & Sys Admin
** http://www.HaggleWare.com/
*/
----- Original Message -----
From: "Paul W. Abrahams"
PS -- if you got the old version of the modules.dep, chances are you are
still using the old kernel.
Did you download the vanilla kernel sources? SuSE installs the kernel in
/boot/ (this is how lilo.conf is set up). vanilla kernel sources build the
kernel to be places in / by default. Is you new kernel sitting in /?
If the answer to the last question is yes, you must rebuild your kernel
after changing the line in the kernel top-level makefile which reads:
#
# INSTALL_PATH specifies where to place the updated kernel and system map
# images. Uncomment if you want to place them anywhere other than root.
INSTALL_PATH=/boot
INSTALL_PATH is commented out in vanilla kernel source. Uncomment it so it
will put the kernel in /boot. or your can change lilo.conf to point to your
new kernel in / if it is there.
Regards,
kw
/* Keith Warno
** Developer & Sys Admin
** http://www.HaggleWare.com/
*/
----- Original Message -----
From: "Keith Warno"
Keith Warno wrote:
PS -- if you got the old version of the modules.dep, chances are you are still using the old kernel.
Did you download the vanilla kernel sources? SuSE installs the kernel in /boot/ (this is how lilo.conf is set up). vanilla kernel sources build the kernel to be places in / by default. Is you new kernel sitting in /?
If the answer to the last question is yes, you must rebuild your kernel after changing the line in the kernel top-level makefile which reads:
# # INSTALL_PATH specifies where to place the updated kernel and system map # images. Uncomment if you want to place them anywhere other than root.
INSTALL_PATH=/boot
INSTALL_PATH is commented out in vanilla kernel source. Uncomment it so it will put the kernel in /boot. or your can change lilo.conf to point to your new kernel in / if it is there.
INSTALL_PATH is set to /boot and has been for some time, so that's not the problem. The kernel and System.map do show up in /boot. So whatever the problem is, it's specifically connected to modules, not to the rest of the kernel. Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Keith Warno wrote:
PS -- if you got the old version of the modules.dep, chances are you are still using the old kernel.
Interesting discovery: the timestamp of the modules.dep file is the time when /etc/conf.modules was last edited, and remains that way even if modules.dep is deleted and then (implicitly on bootup initialization) recreated. No wonder I was puzzled as to where the apparently old file came from. I wonder how that timestamp gets set. Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
abrahams@valinet.com
-
cpchan@myna.com
-
keith@HaggleWare.com