Package: kmod Severity: important Dear maintainer,
While I was doing some post upgrade operation after migrating to buster,
I realized that my network configuration was failing.
Here is what I have in my /etc/network/interfaces:
auto dummy0
iface dummy0 inet static
address 192.168.64.1
netmask 24
In my /etc/modules:
dummy
And in my /etc/modprobe.d/dummy.conf:
options dummy numdummies=1
It used to work correctly with stretch but is broken with buster. The
interface doesn't show up (as in not even listed).
It appears that the problem originate from particular file from systemd
shipped with buster, /lib/modprobe.d/systemd.conf, overriding my
configuration.
Result from a modprobe -v dummy:
insmod /lib/modules/4.19.0-5-amd64/kernel/drivers/net/dummy.ko
numdummies=1 numdummies=0
Both parameters are added (the one from my local configuration and the
one from systemd).
This issue is here: A local configuration SHOULD be able to override a
system one and not the opposite.
As per the man-page, this is a known behavior:
Packages should install their configuration files in /lib/. Files in
/etc/ are reserved for the local administrator, who may use this logic
to override the
configuration files installed by vendor packages. All
configuration files are sorted by their filename in lexicographic order,
regardless of which of the directories
they reside in. If multiple files specify the same option, the
entry in the file with the lexicographically latest name will take
precedence. It is recommended to
prefix all filenames with a two-digit number and a dash, to
simplify the ordering of the files.
This is NOT a desired behavior as any update to the system configuration
directory might override local configuration (based on how the file is
named). Please change it accordingly to process system configuration (in
lexical order) and _then_ local configuration to always ensure that
local configure takes priority over the system one.
Best regards,
--
Baptiste BEAUPLAT - lyknode
signature.asc
Description: OpenPGP digital signature
