In article <[EMAIL PROTECTED]>, Arnd Bergmann <[EMAIL PROTECTED]> wrote: >Possible -- sure, but not useful except as an option for the initial >bootstrap that might not fully work with /lib64. >I've followed both SuSE and Red Hat making that mistake with their early >s390x distributions. They both now have the problem that they changed >to /lib64 installations, which makes it really hard to create 64 bit >packages that work in the old _and_ new distributions.
/lib64 ?! We're arguing for a month if adding a new top-level directory called /run is a good idea and they just add a very very ugly /lib64 ? What's wrong with /lib/ for 64 bits libs and /lib/32/ for the 32 bit legacy stuff (note the slash). Ofcourse, they'll get the rpath thing wrong and commercial applications are going to insist on /lib64, shiver. Mike.
