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

[Justin B Rye]

Back from my walk in the lovely warm pouring rain...

Justin B Rye wrote:
> Michael Biebl wrote:
>> Am 29.06.19 um 15:09 schrieb Justin B Rye:
>>> [...] A file in
>>> +      <filename>/lib/modprobe.d</filename> can be overridden by one with the
>>> +      same name under <filename>/etc/modprobe.d</filename>, but the names are
>>> +      processed in alphabetical order, so
>> 
>> That sentence is a bit confusing: files with the same name are
>> overridden. period. there is no but.

Okay, coming back to it, it can't be helping that this is a useless
use of passive voice.  Swapping it around:

          [...] A file in
          <filename>/etc/modprobe.d</filename> will override one with the same
          name under <filename>/lib/modprobe.d</filename>, but the names are
          processed in alphabetical order, so [...]

This way we start off with the focus in the right place: on the
existing dummy.conf in /etc.  It's not a problem if an upstream
/lib/modprobe.d/dummy.conf turns up, *but*...
-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dummy-module-config4.diff
Type: text/x-diff
Size: 2808 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190629/d5a54920/attachment-0001.diff>