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

[andreimpopescu at gmail.com]

Control: tags -1 moreinfo

On Mi, 26 iun 19, 20:23:59, Baptiste BEAUPLAT wrote:
> Package: release-notes
> 
> Dear maintainers,
> 
> Systemd, in buster, will ship the file /lib/modprobe.d/systemd.conf,
> which contains the following:
> 
>     options bonding max_bonds=0
> 
>     # Do the same for dummy0.
> 
>     options dummy numdummies=0
> 
> This breaks any configuration that an administrator could have added to
> /etc/modprobe.d regarding the dummy and bonding modules.

Would you have background information on why this is done?
What would be the impact on local configuration (networking unusable, 
degraded, etc.)?
 
> For instance, a file in /etc/modprobe.d/dummy.conf containing:
> 
>     options dummy numdummies=1
> 
> Will result in the following being executed by modprobe:
> 
>     insmod /lib/modules/4.19.0-5-amd64/kernel/drivers/net/dummy.ko
> numdummies=1 numdummies=0
> 
> And the original configuration will be overridden.
> 
> 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?

> I thinks this should be documented in the release notes as admins would
> need to be aware of that.


Thanks,
Andrei - not a Release Notes Maintainer, just anticipating what 
information might be necessary to write a useful entry.
-- 
http://wiki.debian.org/FAQsFromDebianUser
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190626/b319d13e/attachment.sig>