Learn about binary compatibility as it relates to the different operating environments that run on Linux on POWER. Learn about new technologies that can provide performance enhancements for a Linux on POWER apps, and follow steps to ensure binary compatibility across multiple distributions in the future.
Distribution migration and binary compatibility considerations
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
They don’t deal with any concrete examples, and shrug off glibc 2.3.2, 2.3.3 and 2.3.4 as just bugfix releases. Wrong! New features were added here too. No mention of symbol versioning. An over-emphasis on NUMA, which should not affect applications as it’s implemented at the hardware/kernel level. No discussion of C++ compatibility and no real discussion of library instability outside “Use what Red Hat tell you to use” (which is fine but not exactly a deep analysis).
Why do IBMs articles so rarely provide satisfying technical detail these days (or are sometimes totally wrong like with the Win32->Linux article)?
Nice point of view my pal!.. you know, IBM is more about the POWER name itself rather than what they can “share” or “open” with the rest of the world/market. It’s like that picture “The neverending story”… you know, gimme that “POWER” new processor!!! yeah! gimme two of’em!!!! it’s POWER!!! wow! cool! bah….
I don’t think binary compatibility will be that important in the future since the general trend is towards source based distributions e.g. Gentoo with all their pros(portability, optimized performance) and cons(compile times).