update-modules, do we need it anymore?
Hi all,
While working on making all postinstalls run on host, I saw that we still use update-modules script. However, neither the kmod modprobe nor the busybox one read /etc/modules.conf file anymore which is created by update-modules script. Both scan /etc/modprobe.d/*.conf files.
So, does anybody know why do we still have it around? Most modern distributions declared update-modules as obsolete and /etc/modules.conf doesn't exist anymore. Am I missing something?
Thanks,
Laurentiu
Quoted 3 lines · Laurentiu Palcu
So, does anybody know why do we still have it around? Most modern distributions declared update-modules as obsolete and
/etc/modules.confdoesn't exist anymore. Am I missing something?
As you say, it's just a historical relic. It's already optional in
oe-core: you can turn it off by omitting update-modules from your DISTRO_FEATURES. I would certainly recommend that any modern distro does that.
p.
Quoted 11 lines · Laurentiu Palcu
Hi all,
While working on making all postinstalls run on host, I saw that we still use update-modules script. However, neither the kmod modprobe nor the busybox one read
/etc/modules.conffile anymore which is created by update-modules script. Both scan/etc/modprobe.d/*.conffiles.So, does anybody know why do we still have it around? Most modern distributions declared update-modules as obsolete and
/etc/modules.confdoesn't exist anymore. Am I missing something?
I've been using the autoload functionality (not heavily, but from time to time)
that is currently tied to update-modules. I did a quick scan of the alternatives
in oe-core, and didn't immediately see that the same thing is possible via kmod. Is that the case, or am I missing something as well ?
Cheers,
Bruce
Quoted 9 lines
Thanks,
Laurentiu_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Quoted 18 lines · Bruce Ashfield
On Tue, Jan 8, 2013 at 9:41 AM, Laurentiu Palcu <[email protected] <mailto:[email protected]>> wrote:
Hi all,
While working on making all postinstalls run on host, I saw that we still use update-modules script. However, neither the kmod modprobe nor the busybox one read
/etc/modules.conffile anymore which is created by update-modules script. Both scan/etc/modprobe.d/*.conffiles.So, does anybody know why do we still have it around? Most modern distributions declared update-modules as obsolete and
/etc/modules.confdoesn't exist anymore. Am I missing something?
Quoted 6 lines
I've been using the autoload functionality (not heavily, but from time to time)
that is currently tied to update-modules. I did a quick scan of the alternatives
in oe-core, and didn't immediately see that the same thing is possible via kmod. Is that the case, or am I missing something as well ?
This autoload functionality seems to be provided by /etc/init.d/modutils.sh which is explicitly called from update-modules script. However, modutils.sh resides in modutils-initscripts.bb recipe. So, I personally see not use for update-modules anymore...
Thanks,
Laurentiu
Quoted 22 lines
Cheers,
Bruce
Thanks,
Laurentiu_______________________________________________
Openembedded-core mailing list [email protected] <mailto:[email protected]>
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-coreSignature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Quoted 29 lines · Laurentiu Palcu
Quoted 10 lines · Bruce Ashfield
On Tue, Jan 8, 2013 at 9:41 AM, Laurentiu Palcu <[email protected] <mailto:[email protected]>> wrote:
Hi all,
While working on making all postinstalls run on host, I saw that we still use update-modules script. However, neither the kmod modprobe
nor
Quoted 1 line
the busybox one read
/etc/modules.conffile anymore which is createdby
Quoted 4 lines
update-modules script. Both scan
/etc/modprobe.d/*.conffiles.So, does anybody know why do we still have it around? Most modern distributions declared update-modules as obsolete and
/etc/modules.confQuoted 8 lines
doesn't exist anymore. Am I missing something?
I've been using the autoload functionality (not heavily, but from time to time)
that is currently tied to update-modules. I did a quick scan of the alternatives
in oe-core, and didn't immediately see that the same thing is possible
Quoted 7 lines
via
Quoted 1 line
kmod. Is that the case, or am I missing something as well ?
This autoload functionality seems to be provided by
/etc/init.d/modutils.shwhich is explicitly called from update-modules script. However,modutils.shresides in modutils-initscripts.bb recipe. So, I personally see not use for update-modules anymore...
I don't have any use for the rest of update-modules, so I don't disagree on that point. I'd just like to see a form of autoload support be continued if anything happens to update-modules. But since update-modules isn't mandatory, I suppose nothing drastic will happen to it regardless, but having
a modern equivalent would be nice :)
Bruce
Quoted 27 lines
Thanks,
LaurentiuQuoted 7 lines
Cheers,
Bruce
Quoted 8 lines
Thanks,
Laurentiu_______________________________________________
Openembedded-core mailing list [email protected] <mailto:[email protected]>http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 7 lines
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Quoted 7 lines · Bruce Ashfield
I don't have any use for the rest of update-modules, so I don't disagree on that point. I'd just like to see a form of autoload support be continued if anything happens to update-modules. But since update-modules isn't mandatory, I suppose nothing drastic will happen to it regardless, but having
a modern equivalent would be nice :)
Just to be clear on this. Even if update-modules is removed, modules will still be autoloaded by modutils.sh which is run in rcS.d. Also, /etc/init.d/modutils.sh can be run separately.
Thanks,
Laurentiu
Quoted 7 lines · Laurentiu Palcu
Quoted 1 line · Bruce Ashfield
I don't have any use for the rest of update-modules, so I don't disagree
on
Quoted 1 line
that point. I'd just like to see a form of autoload support be continued
if
Quoted 8 lines
Quoted 5 lines
anything happens to update-modules. But since update-modules isn't mandatory, I suppose nothing drastic will happen to it regardless, but having
a modern equivalent would be nice :)Just to be clear on this. Even if update-modules is removed, modules will still be autoloaded by
modutils.shwhich is run in rcS.d. Also,/etc/init.d/modutils.shcan be run separately.
Right, but the files that it reads are generated in kernel.bbclass, right ? If so, the generation of those files is tied to update-modules being in the DISTRO_FEATURES and available. So if update-modules is removed, we want to update the kernel.bbclass to have a different generation of the autoload config files.
Bruce
Quoted 6 lines
Thanks,
Laurentiu
Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"