3 ms·
In contrast, here is a thread about Debian, after much deliberation, unanimously choosing to break kernel ABI compatibility with VMware. They didn't want to inc
by cpeterso 15y ago
In contrast, here is a thread about Debian, after much deliberation, unanimously choosing to break kernel ABI compatibility with VMware. They didn't want to increase the ABI number during a "freeze", even though they broke the ABI.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607368 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607368
- danudey 15y agoWhile I disagree, in the end, about breaking user applications, I can appreciate their situation. They have an upstream kernel from which they get bugfixes and patches, but which has no guarantees of stability. Any guarantees that the Debian team decides to make are their own responsibility, and could result in them maintaining multiple patches just to fix ever-more-diverging upstream releases.
- lambda 15y agoThat's the difference between the user-space interface, and the kernel ABI. The Linux kernel ABI has no compatibility guarantees. If you are linking to the kernel, you are considered to be part of the kernel, and thus you are expected to keep abreast of any ABI changes (preferably by getting your module into the kernel tree, so that anyone changing the ABI can fix your code too). The Debian kernel team tries to do a reasonable job of tracking kernel ABI compatibility changes, and updating the number when the ABI does change, to avoid having to recompile and reinstall everything for every patch to the stable tree. In this case, they decided that the ABI change was only intended for a single, in-tree module (KVM), and that they didn't have to increment the ABI number for a change that shouldn't affect anything else. This is really just an example of the Linux kernel developers' two approaches to compatibility. For the kernel ABI, they make no guarantees whatsoever about compatibility. For the user space interface, they are supposed to never, ever change the interface in ways that will break existing programs, though there are sometimes disagreements about what precisely constitutes this interface and what is outside the bounds of it.
- namdnay 15y agoSlightly off-topic, but often when reading these mailing lists I find some developers to be rather unhelpful, if not downright nasty. Take this example. Now I realise this isn't a company-client relationship we're looking at, but am I alone in thinking a bit more diplomacy wouldn't have gone amiss?