this is left up to the distribution a non-chroot environment will install in /emul and you can install a chroot environment wherever you like. there are also /lib and /lib64 directoried (in the same way that sparc64 implements things) but in debian things dont seem to be done like that. in fedoracore for x86_64 you will find 32bit libraries in /lib and 64bit in /lib64. an ldd of a binary will show that the binary is using the appropriate libraries. take the same binary across from fc to a debian box, ldd it, then it will still use the proper libraries. it would seem that ldd in its glory, knows the difference. thankfully linux has been 64 bit for a long time, so alpha and sparc have taken the edge off things. Dean
I've heard that with the 64-bit kernel you can run 32- and 64-bit code mixed -- although presumably not within a single executable image. How are the shared libraries organised so that each executable gets its own kind of libraries? Wouldn't there be trouble with mname collisions and the like? -- hendrik