Hi Akintayo ...
>1. There is a symlik called module_info in the boot directory
>that points to a file of the same stem e.g. module_info-2.0.36.
>The file seems to contain information about which mods to load.
>How do I create one of these for my new kernel?
Looking for this answer myself as well. As far as I know, however, the file
is in no way vital to system operation. It is used by rh's "kernel
configuration" tool, accessible from the X-Windows control-panel, and, AFAIK
again, *only* by that. It lists the commandline parameters the modules can
take...
>2. in the /lib/modules directory there 'was' a link called
>preffered to the directory of the kernel version I was using.
[ snip ]
>As it currently stands my system will not load the modules for
>my zip, which automounts in my fstab, what steps do I have to
>take to rectify this situation.
[ snip ]
>I use RH5.2, with the patches including 2.0.36-7 <prior to
>the upgrade>
The preferred symlink seems to exist because of redhat's naming of kernel's,
eg. for my redhat 5.1 system, vmlinuz-2.0.34-0.6 in stead of a regular
vmlinuz-2.0.34. The /etc/rc.d/rc.sysinit script checks for these things.
However, the version from the redhat 5.1 distro seemed to contain a bug:
based on some circumstances involving whether or not the currently used
kernel had such a -x.x postfix appened, the "preffered" symlink is created,
but later on in the script it did something like:
if symlink preffered exists then
depmod -a preffered
else
depmod -a preffered
Deleting the "preffered" in the else-branch solved the problems I was
experiencing with modules after upgrading my kernel. Maybe RH 5.2 still has
this same "feature"? (search for depmod -a in rc.sysinit).
Hope this helps...
Rene
