On Wed, Feb 23, 2011 at 11:24 AM, Ljubomir Ljubojevic <office at plnet.rs> wrote: > > This is not just a simple "find a library" task, sometimes you need to > find out what *exact* version of the called library *must* be used to > keep compatibility (in case of hidden dependency without published > matching SRPMS) with RHEL. IMHO, the binary, when invoked on the system one is trying to clone, presents all necessary information for the interested reader to digest. At this moment, apparently, the only interested reader of said binary is the load routine :( Whether it is a jump to 'panic' or a return jump to invoke a library routine, it is available for the interested reader of the binary. This process worked in a tightly clustered group of 31 processors where the object of the invocation could be in the memory of the CPU (or need to be loaded) or it could be in the memory of a PPU (or need to be loaded), of which there were 30. Of course, there was a prologue section for each callable routine which identified it and its version number among other things and that may or may not exist in RHEL, I dunno.