I strongly agree. I have been facing this problem and it was really a pain. I used the last bonding version which didn't define the ABI version, together with the associated ifenslave, but when the
I'm a bit concerned about doing some of this stuff in the 2.4 series. That compatibility stuff is there for a reason, and was set to be removed in 2.6. Perhaps we shouldn't be doing stuff this drast
[removed bonding-announce from cc:] My thinking here is that any ifenslave old enough (two years or more) to still be using the OLD ioctl values is unlikely to work with the current kernel driver, an
I think I better leave this for Amir to answer. He's our ABI expert and this needs carefull consideration, especially now that he's working on enhancing ifenslave's capabilities for the hot operation
I was specifically told by David Miller that we are not to break binary compatibility within a 2.4 release. Such things had to wait until 2.5 or later. We can not require a user to upgrade their ife
Hi ! I strongly agree. I have been facing this problem and it was really a pain. I used the last bonding version which didn't define the ABI version, together with the associated ifenslave, but when
I'm a bit concerned about doing some of this stuff in the 2.4 series. That compatibility stuff is there for a reason, and was set to be removed in 2.6. Perhaps we shouldn't be doing stuff this drast
[removed bonding-announce from cc:] My thinking here is that any ifenslave old enough (two years or more) to still be using the OLD ioctl values is unlikely to work with the current kernel driver, an
I think I better leave this for Amir to answer. He's our ABI expert and this needs carefull consideration, especially now that he's working on enhancing ifenslave's capabilities for the hot operation
I was specifically told by David Miller that we are not to break binary compatibility within a 2.4 release. Such things had to wait until 2.5 or later. We can not require a user to upgrade their ife