On Mon, May 23, 2005 at 02:57:40PM -0700, Jon Passki wrote:
>
> --- Kris Kennaway <[EMAIL PROTECTED]> 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
pgpg7x07WVfXS.pgp
Description: PGP signature
