Bug#931130: Document that local configuration for dummy and bonding modules are getting overwritten by systemd

Justin B Rye justin.byam.rye at gmail.com
Thu Jun 27 00:37:01 BST 2019


Michael Biebl wrote:
> Am 26.06.19 um 21:39 schrieb andreimpopescu at 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.

Okay, so here's a first rough idea of what the release-notes might
say.  It would make sense to put the new section after the existing
one on deprecating old-style interface names.  Something like:


 _Module configuration for bonding and dummy interfaces_

 Administrators who are using channel bonding and/or dummy interfaces
 (for instance to configure a machine as a router), and who have set
 up module parameters in a file under /etc/modprobe.d, may need to
 change the name of the local configuration file used, to avoid these
 parameters being ignored after the upgrade to buster.

 In buster, udev ships a file /lib/modprobe.d/systemd.conf designed to
 make it easier to configure such interfaces using systemd-networkd.[?]
 This contains the lines

	options bonding max_bonds=0
	options dummy numdummies=0

 A file in /lib/modprobe.d can be overridden by one with the same name
 under /etc/modprobe.d, but the names are processed in alphabetical
 order, so /lib/modprobe.d/systemd.conf follows and overrides (for
 instance) /etc/modprobe.d/dummy.conf. Make sure that any local
 configuration file has a name that sorts after "systemd.conf", such
 as "/etc/modprobe.d/zz-local.conf".


-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package



More information about the Pkg-systemd-maintainers mailing list