Recent 5.4-p1 upgrade issue (lib/libc.so.5)

[Kris Kennaway]

On Mon, May 23, 2005 at 10:24:15AM -0700, Jon Passki wrote:
> Hello,
> 
> I performed an unsupported way of installing and am soliciting what
> I could do next time to prevent installation blues.  I'm not
> expecting assistance from the Project, just some love :)
> 
> I have a build host that created what I needed for the host being
> upgraded.  Once it's more polished, I'll be happy to share my
> steps, but relatively it went well.  When I attempted to update
> /lib/libc.so.5, though, I hit a bump.
> 
> I `chflags noschg /lib/libc.so.5` and then used tar to extract the
> exact file.  tar was able to unlink the file, and then choked. 
> After some unrelated errors, I was in single user mode using
> /rescue to save my rear end, which worked well enough.  Doing `ldd
> /sbin/tar` hinted why it probably choked, since tar is dynamically
> linked to /lib/libc.so.5.
> 
> Here's what gets me: I was able to do a the supported upgrade
> process in an unsupported manner (multiuser mode via ssh w/o a
> shutdown inbetween, nor going into signle user mode) w/ no issues
> on the build host.  What occurs in that process (make buildworld;
> make buildkernel; make installkernel; mergemaster -p; make
> installworld; mergemaster) where libc can be replaced (assuming it
> uses install(1), which is also linked against libc) without
> failure, but using tar causes it to fail?  Ideas?

Look at how make installworld does the replacement safely.

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050523/f3e97084/attachment.bin