On Mon, Aug 07, 2006 at 01:19:27PM -0700, Frans Meulenbroeks wrote:
> When installing modules it is possible that they are
> not registered properly.
>
> postinst does a depmod -A and update-modules
[...]
Yeah, that doesn't make any sense. The -A is to stop depmod
regenerating the modules list in the case where nothing has happened,
such as you just rebooted. So in the init script you want -A, but
when installing a package that contains a module you alrady know that
the module list has changed and want to force the update.
> As far as I can see the following files are affected:
The following is the one used by module packages and so is the main
one that should be updated:
> ./classes/module.bbclass
The following is an initscript, so it shouldn't be updated:
> ./packages/modutils/files/modutils.sh
These ones are running it after installing a new kernel. I guess it
makes no difference?
> ./classes/kernel.bbclass
> ./packages/linux/mnci-ramses_2.4.21-rmk2-pxa1.bb
Not sure what these ones are doing, both like like the old modules
stuff which I've long since forgotten about - debian says
update-modules is obsolete.
> ./packages/modutils/files/mnci/modutils.sh
> ./packages/update-modules/update-modules-1.0/update-modules
I think the best thing would be to update ./classes/module.bbclass
and perhaps ./classes/kernel.bbclass only and leave everything else
alone. That should fix the issue you described without too much risk
of breaking anything.
> PS: I assume this will also affect lines like:
> ${HOST_PREFIX}depmod-${KERNEL_MAJOR_VERSION} in kernel.bbclass
I don't see any reason why that would be effected?
--
Jamie Lenehan <[EMAIL PROTECTED]>
_______________________________________________
Oe mailing list
[email protected]
https://www.handhelds.org/mailman/listinfo/oe
