Hi,
+# Don't run modutils.sh if systemd is installed
+if [ $first_time -eq 1 ]&& [ ! -e /bin/systemctl ]; then
/etc/init.d/modutils.sh || true
fi
I just came across this and was wondering what the situation is with
respect to systemd's module loading. Is there actually a mechanism in
place for populating systemd's /etc/modules-load.d folder?
The "module_autoload_xx" directives populate /etc/modutils but not
/etc/modules-load.d. As far as I can tell this means that one still
needs to include the old modutils.sh script to autoload modules (via
modutils-initscripts package). With this patch, you need to boot the
system twice in order for the kernel modules to be auto-loaded (because
update-modules does not reload modutils.sh immediately after adding the
modules).
Are we in a transition period where module-autoload is not yet
implemented via the systemd method but update-modules doesn't quite play
ball properly with that, or is there already a mechanism for populating
modules-load.d that I haven't found yet? (Other than doing it by hand).
Thanks,
Kelvin.
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
