On 4 Mar 2024, at 15:57, Peter Kjellerstedt via lists.openembedded.org <[email protected]> wrote: > +modulesloaddir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', > '${nonarch_libdir}', '${sysconfdir}', d)}/modules-load.d" > +modprobedir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', > '${nonarch_base_libdir}', '${sysconfdir}', d)}/modprobe.d”
Feels like this should be fixed by changing either eudev or systemd-udev (presumably that’s the two recipes which are at blame here) so that they use the same path, as module config files changing location depending on whether systemd is enabled is terrible, especially when you have systems which built both systemd and sysv and expect to be able to build different images with different init systems from the same distro. Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196642): https://lists.openembedded.org/g/openembedded-core/message/196642 Mute This Topic: https://lists.openembedded.org/mt/104724883/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
