From 582faeb461aa0dd01b55bf6c9b1433532fc927d3 Mon Sep 17 00:00:00 2001 From: Dimitri John Ledkov Date: Wed, 2 Aug 2017 13:41:18 +0100 Subject: modprobe.d: ship drop-in to set bonding max_bonds to 0 (#6448) This allows networkd to correctly manage bond0 using networkd, when requested by the user. Fixes #5971 #6184 --- README | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'README') diff --git a/README b/README index 5ae581e33..bf010f8ac 100644 --- a/README +++ b/README @@ -110,11 +110,10 @@ REQUIREMENTS: It's a good idea to disable the implicit creation of networking bonding devices by the kernel networking bonding module, so that the automatically created "bond0" interface doesn't conflict with any such - device created by systemd-networkd (or other tools). Please make sure - that the kernel module bonding.ko is shipped with max_bonds=0 set by - default. Ideally there would be a kernel compile-time option for this, - but there currently isn't. The next best thing is to make this change - through a modprobe.d drop-in. + device created by systemd-networkd (or other tools). Ideally there + would be a kernel compile-time option for this, but there currently + isn't. The next best thing is to make this change through a modprobe.d + drop-in. This is shipped by default, see modprobe.d/systemd.conf. Note that kernel auditing is broken when used with systemd's container code. When using systemd in conjunction with -- cgit v1.2.3-65-gdbad