Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 May 2005 11:44:30 -0700
From:      Kris Kennaway <kris@obsecurity.org>
To:        Jon Passki <cykyc@yahoo.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Recent 5.4-p1 upgrade issue (lib/libc.so.5)
Message-ID:  <20050523184430.GC96054@xor.obsecurity.org>
In-Reply-To: <20050523172415.57039.qmail@web50303.mail.yahoo.com>
References:  <20050523172415.57039.qmail@web50303.mail.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--E13BgyNx05feLLmH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 23, 2005 at 10:24:15AM -0700, Jon Passki wrote:
> Hello,
>=20
> 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 :)
>=20
> 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.
>=20
> 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.=20
> 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.
>=20
> 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

--E13BgyNx05feLLmH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFCkiSNWry0BWjoQKURAiRYAKC4JJsfP+d0tKDNnrJdnQyVYfYK9wCeKlE1
OPGWdFpUt9bPMDACCi+Cs1c=
=e51X
-----END PGP SIGNATURE-----

--E13BgyNx05feLLmH--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050523184430.GC96054>