>>> (And you really want to "replace" them with an unlink() and copy, or copy >>> to a temp file and unlink()/link(), sequence.) >> >> So the sequence I should follow is: >> >> -rwxr-xr-x 1 root root 156051 Dec 11 08:40 ld-2.18.so >> lrwxrwxrwx 1 root root 10 Dec 11 08:40 ld-linux-x86-64.so.2 -> ld-2.18.so >> >> 1) delete ld-linux-x86-64.so.2 >> 2) update ld-2.18.so > >No. You need to unlink *this* file, since it's mapped into several other >processes on the system. But this file's name is inconsistent across systems; >the symlink name is consistent, which is why I use it. > >Of course, you also need to restart every process that's using these files >after you replace them. > >It would be *far, far, FAR* safer, and much less error prone, to simply not >run any process that's mapping in any of the files you're replacing when you >replace the files. Yes, that means you can't do it from inside chroot, or >alternately you have to be running the binaries and libs from /tools. But if >you do it this way you won't have any of the problems you're having.
Thanks for that - I'm clearly out of my depth here, but learning fast by my mistakes. Before I decide how best to proceed with is, would you tell me please how the distros update the file ld-2.18.so and the symlink ld-linux-x86-64.so.2, without crashing the system. They don't appear to use a /tools dir so do they tar the files into the directories? Thanks jb. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
