On 6/26/19 11:04 PM, Michael Biebl wrote: > Am 26.06.19 um 21:39 schrieb andreimpopescu@gmail.com: >> >> On Mi, 26 iun 19, 20:23:59, Baptiste BEAUPLAT wrote: > >>> The only way to force modprobe to use local configuration is to rename >>> the /etc/modprobe.d/dummy.conf file to /etc/modprobe.d/systemd.conf. >> >> Is this documented anywhere else? > > According to the docs in man 5 modules-load.d it should be sufficient to > name the local config so that is sorted after systemd.conf. > > I've opened the bug #931137 [1] directly against kmod. Following the prompt reply from the maintainer, it would appear that it's the only way to go. This is what I'm going to apply to fix the actual issue on my systems. I'll let you decided if this new override from systemd to dummy and bonding modules should be mentioned in the release notes. I would advocate for it since unaware sysadmins (like me) could easly break their network configuration because of that. Best, [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931137 -- Baptiste BEAUPLAT - lyknode
Attachment:
signature.asc
Description: OpenPGP digital signature