Date: Mon, 23 May 2005 15:04:56 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Jon Passki <cykyc@yahoo.com> Cc: stable@freebsd.org Subject: Re: Recent 5.4-p1 upgrade issue (lib/libc.so.5) Message-ID: <20050523220455.GA49814@xor.obsecurity.org> In-Reply-To: <20050523215740.89642.qmail@web50309.mail.yahoo.com> References: <20050523184430.GC96054@xor.obsecurity.org> <20050523215740.89642.qmail@web50309.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Mon, May 23, 2005 at 02:57:40PM -0700, Jon Passki wrote:
>
> --- Kris Kennaway <kris@obsecurity.org> wrote:
>
> > On Mon, May 23, 2005 at 10:24:15AM -0700, Jon Passki wrote:
>
> > > 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.
>
> Ah, makes sense now, but let me regurgitate:
> According to src/Makefile.inc1, installword sets up INSTALLTMP with
> some nifty files, along with the files previously in the obj tree
> setup by phases such as bootstrap-tools. Since these are defined
> later on in the path before the user's ${PATH}, one doesn't shoot
> one's foot off when updating the binaries, correct?
Well, it does that too, but it also installs libc itself in a safe way
using install(1).
Kris
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)
iD8DBQFCklOHWry0BWjoQKURAjdMAKDEUynWDqIT+L91zhLPzZFpKzMSRgCfTOQN
LLuGaelMEtN+HSAu4NEx8a4=
=OeYw
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050523220455.GA49814>