From owner-freebsd-stable@FreeBSD.ORG Mon May 23 21:57:41 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D402516A41C for ; Mon, 23 May 2005 21:57:41 +0000 (GMT) (envelope-from cykyc@yahoo.com) Received: from web50309.mail.yahoo.com (web50309.mail.yahoo.com [206.190.38.242]) by mx1.FreeBSD.org (Postfix) with SMTP id 727F843D1F for ; Mon, 23 May 2005 21:57:41 +0000 (GMT) (envelope-from cykyc@yahoo.com) Received: (qmail 89644 invoked by uid 60001); 23 May 2005 21:57:40 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=RwBH7Mzc3v+TfDQOm+f7ju3m6VJIdVanLf/s9v7NJ3q6RuzCd5N/mQeLTi9jm0GqMJt4Jg11r2U3/T7b49R0qhlyJpxRuT7nRTRwwIZkVnikplbb0/4EAoLEIwSJxack4RUVzjZRrrI9KhjWvfyzs7EZuSm2woFo/HINTYI3HuU= ; Message-ID: <20050523215740.89642.qmail@web50309.mail.yahoo.com> Received: from [65.173.207.2] by web50309.mail.yahoo.com via HTTP; Mon, 23 May 2005 14:57:40 PDT Date: Mon, 23 May 2005 14:57:40 -0700 (PDT) From: Jon Passki To: stable@freebsd.org In-Reply-To: <20050523184430.GC96054@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: Recent 5.4-p1 upgrade issue (lib/libc.so.5) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cykyc@yahoo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2005 21:57:42 -0000 --- Kris Kennaway 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? In my circumstance, I don't have an obj tree on the dest. host, but I do have /rescue. I could extract that on a first run and then perform the later extractions with the updated tar (or just do it all if /rescue/tar works anyway). Does this seem decent? Is there a more elegant way? Thanks for the heads up, Kris! Jon __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/