Hello
Having successfully compiled a custom 2.4.19 kernel
for ide raid support (and stripping out all modules etc), I created a set of
boot-floppies from the bf2.4 set.
On mounting rescue.bin, I dropped the new kernel
in, ran rdev.sh etc, edited install.sh, making VERSION=2.4.19 .
Installation runs perfectly, and correctly creates
vmlinux-2.4.19 etc under /boot, but when the system reboots, I receive a
"can't open /lib/modules/2.4.19/modules.dep" error.
The reason is simple - the 2.4.19 folder
doesn't exist. Instead, I have a 2.4.18-bf2.4 folder.
It seems that perhaps I've missed changing a
VERSION variable somewhere, to instruct the installer to automatically
create a correct 2.4.19 folder under /lib/modules/ , rather than the
default 2.4.18-bf2.4.
Am I trying to do something (i.e. use a later
kernel) that the boot-floppies can't / weren't intended to do?
Regards, David
|