| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <413FEEF1743111439393FB76D0221E4809790A30@leopard.zoo.q9networks.com> Date: Thu, 3 Jan 2008 10:23:08 -0500 From: "Jari Takkala" <Jari.Takkala@...com> To: "Jay Vosburgh" <fubar@...ibm.com> Cc: <netdev@...r.kernel.org> Subject: RE: [PATCH 2.6.23.12] net/bonding: option to specify initial bond interface number On Wednesday, January 02, 2008 17:24, Jay Vosburgh wrote: > What advantage does this have over: > > # echo +bond5 > /sys/class/net/bonding_masters > > which will create a new bonding master for the already-loaded driver? > The advantage is that you can load multiple instances of the bonding driver and control the name of the bond interface that will be created. Normally the bond interface name would take the next available number. In our startup scripts we need to be able to ensure that the interface name is consistent across reboots. Sometimes bond1 may be brought up before bond0 and it may have different options (requiring a different instance of the bonding driver). I understand that the startup scripts could be modified to account for this, however we also have an IOS like interface to an embedded system where the user can create new bond interfaces and specify the interface number, they may create interfaces out of order and this feature enables them to accomplish that. Jari -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists