>> So here is what I did in the meantime:
>> * Created a version for 2.4 that puts back all old compatibility stuff
>> that was removed either during the propagation set or the cleanup
>> * Created a version for 2.6 that puts back just the compatibility
>> stuff that was removed in the propagation set (BOND_SETHWADDR, since
>> we got a complaint from a RH9 user).
>> * Removed the mention of the multicast param from the read-me.
>> * Raised the ABI version to 2 so the new ifenslave keeps propagating
>> IP settings to slaves for older drivers, and doesn't do that for new
>> ones that contain Willy Tarreau's panic fix.
>I like this.
Same here, but I'd like to have a list somewhere of what each
of the ABI versions is for and how they're supposed to behave. It's
starting to look like we're going to be adding these on a semi-regular
basis, so we need to keep track of what each one does and why.
I also don't have any major heartburn about leaving the OLD
thingies in 2.4. I'd like to remove them, but part of my reason for
wanting to nuke them was to keep 2.4 and 2.6 identical, but we're not
doing that, so it's not as big a concern.
-Jay Vosburgh, IBM Linux Technology Center, fubar@xxxxxxxxxx