I tried to upgrade the kernel to the current version (2.6.4-1) and after reboot the system is still looking for modules in the /lib/modules/2.6.3 directory which no longer exists.
The "depmod" command returns with "WARNING: Couldn't open directory /lib/modules/2.6.3: No such file or directory FATAL: Could not open /lib/modules/2.6.3/modules.dep.temp for writing: No such file or directory"
What is the magic command to point the system into the right place?
You didn't run lilo after your upgrade.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
That seamed to do it!
This seems to happen alot! Is there any way that a post_install on the kernel pkg could detect whether lilo is being used and run this? Just a thought.
Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?
i don't think so but using a .install file to echo in a warning after install it woulod cut down on this error a wee bit.
a script may not be able to account for unusual lilo setups
I am not your friend