> * Created a version for 2.4 that puts back all old compatibility
> stuff that was removed either during the propagation set or the
> cleanup set.
> * 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).
I'm going to need a ruling from you:
We understood from David that support of old ioctl definitions (i.e.
those mapped to SIOCDEVPRIVATE) needs to be removed in the 2.6
kernel. This will break compatibility with old versions of ifenslave
(at least 2 years old, but still included in recent distributions
like Red Hat 9).
If removing those private ioctls is a necessity for 2.6, then breaking
compatibility with the old ifenslave versions is inevitable, so we
might as well remove all compatibility stuff from the 2.6 bonding
module (not just the private ioctls). Of course, we'll keep ifenslave
fully compatible with all versions of bonding, so the user only needs
to upgrade the tool once.
Given the above, how do you feel about removing old backward
compatibility stuff from bonding in 2.6 ?
| Shmulik Hen Advanced Network Services |
| Israel Design Center, Jerusalem |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp. |