Looks like Brian proposed
something similar in the commit-list:
I'm thinking that with 3.6, as we may be
supporting 2.4 and 2.6 kernels,
without knowing which ahead of time, we may want to include 2.4 and 2.6
capable modutils as insmod.2.4 and insmod.2.6, for example.
At boot time, in the initrd, we determine the kernel type, and create a
link to the appropriate one:
if [ 2.6 kernel ];
ln -s insmod.2.6 insmod
fi
And off we go!
without knowing which ahead of time, we may want to include 2.4 and 2.6
capable modutils as insmod.2.4 and insmod.2.6, for example.
At boot time, in the initrd, we determine the kernel type, and create a
link to the appropriate one:
if [ 2.6 kernel ];
ln -s insmod.2.6 insmod
fi
And off we go!
If my method works, it'll be
simplier since 2.6 kernel capable insmod would look for 2.4 kernel capable
insmod.old, so no need to code around it, just include the 2.4 kernel capable
insmod as insmod.old.
Testing right
now...
Cheers,
Bernard
From: [EMAIL PROTECTED] on behalf of Bernard Li
Sent: Sun 08/01/2006 21:45
To: sisuite-devel@lists.sourceforge.net
Subject: [Sisuite-devel] modutils
It appears that modutils is no longer
being used. We either use module-init-tools or busybox:
[initrd.rul]
MODULE_UTILS=module-init-tools
ifeq ($(ARCH),ppc64)
MODULE_UTILS=busybox
endif
ifeq ($(ARCH),ppc64-iSeries)
MODULE_UTILS=busybox
endif
ifeq ($(ARCH),ppc64)
MODULE_UTILS=busybox
endif
ifeq ($(ARCH),ppc64-iSeries)
MODULE_UTILS=busybox
endif
I ran into an issue using
UseYourOwnKernel with branch/3.6.x on RHEL3 which uses 2.4 kernel. I got
the following error message:
Kernel requires old insmod, but
couldn't run insmod.old: No such file or directory
I propose that we compile modutil's
insmod as insmod.old.
I'd like to check this into stable
branch if possible (since this is a bugfix of sorts) - of course I'll do as much
testing as I can.
Thanks,
Bernard
