On Thursday, January 03, 2008 12:04, Jay Vosburgh wrote:
>> 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 bond
Jari Takkala <[EMAIL PROTECTED]> wrote:
>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
On Wednesday, January 02, 2008 16:56, Randy Dunlap wrote:
> You could (should) make be unsigned int and then use
> module_param(ifnum, uint, 0); and then ...
>
> then this block is mostly useless since ifnum cannot be < 0.
> And how could it ever be > INT_MAX (when ifnum was an int)?
>
> If is
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
Jari Takkala <[EMAIL PROTECTED]> wrote:
>Allow the user to specify an initial interface number when loading the bonding
>driver. This is useful when loading multiple instances of the bonding driver
>and you want to control the interface number assignment. For example, if the
>user wishes to cre
On Wed, 2 Jan 2008 16:20:48 -0500 Jari Takkala wrote:
> Allow the user to specify an initial interface number when loading the
> bonding driver. This is useful when loading multiple instances of the bonding
> driver and you want to control the interface number assignment. For example,
> if the
