2007/12/3, Bruce Dubbs <[EMAIL PROTECTED]>: > Alexander E. Patrakov wrote: > > > Just a data point: I was able to upgrade glibc "live" on LFS LiveCD > > 6.2-5 from 2.3.6 to 2.7 by building it in /dev/shm "by the book" and > > installing it with the following commands: > > > > make install_root=/dev/shm/glibc-install > > cd /dev/shm/glibc-install > > tar -cpf - . | tar -C / -xUpvf - > > That is very interesting. I'm curious though why a simple > > cp -af . / > > doesn't work. My understanding is that a file is maintained in memory > while in use, even if the file system overwrites what is on the disk.
I will test it and post the result. As far as I can predict, this will work for this upgrade (because there are no overwritten libraries, only overwritten symlinks), but may fail for the case of "2.5 -> 2.5 + branch_update", because both contain /lib/libc-2.5.so. > It only deletes the file completely when the last process using the file > releases the file or terminates. > > This also leads to the question about what happens to /sbin/init. I > would think that even with an in place update of glibc, the old > libraries would still be used ( linux-gate.so.1, libc.so.6, and > /lib/ld-linux.so.2). Correct, but there is a way for init to re-execute itself and release these libraries: "init u". -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
