William Harrington wrote: > On Dec 16, 2013, at 5:17 PM, John Burrell wrote: > >> When I try and update the dynamic linker, /usr/lib/ld-2.18.so in my case, >> >> >> I get the message 'Text file busy' >> >> and when I then access the chroot window I get a seg fault. > > You aren't clear, > > /usr/lib being your host system that you updated glibc, or the system that > you are using via chroot. It helps to be clear in all that you do.
...Also, it is *not* possible to replace either /lib/ld-linux.so.2 or
/lib64/ld-linux-x86-64.so.2 (...and yes, I use those paths intentionally,
since those are the ABI standard) on a running system unless you replace both
it and /lib{,64}/libc.so.6 from the same process. (And you really want to
"replace" them with an unlink() and copy, or copy to a temp file and
unlink()/link(), sequence.)
ld-linux and libc are not compatible across versions, so trying to exec()
anything while those two files are coming from different glibc versions is
pretty dangerous.
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
