From owner-freebsd-stable@FreeBSD.ORG Mon May 23 17:24:17 2005 Return-Path: X-Original-To: freebsd-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 1D71916A41C for ; Mon, 23 May 2005 17:24:17 +0000 (GMT) (envelope-from cykyc@yahoo.com) Received: from web50303.mail.yahoo.com (web50303.mail.yahoo.com [206.190.38.57]) by mx1.FreeBSD.org (Postfix) with SMTP id B47DF43D49 for ; Mon, 23 May 2005 17:24:16 +0000 (GMT) (envelope-from cykyc@yahoo.com) Received: (qmail 57042 invoked by uid 60001); 23 May 2005 17:24:16 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=5R8QukhAgFwrYkfAFjVW6LlUvWkIFd+Ko8Rwgt+MlONpwfu9DY7asckgq0R2FdbZhLJow3Qvv8KTCv8CmNP8RXKHBn9JWzhx4yF3pYm59IKwEJvCMIswKV9cNf24eCx/lIdNCLnBSJLYki6VKxXDhpx1w/eea/T5IOwDWhhwqTo= ; Message-ID: <20050523172415.57039.qmail@web50303.mail.yahoo.com> Received: from [65.173.207.2] by web50303.mail.yahoo.com via HTTP; Mon, 23 May 2005 10:24:15 PDT Date: Mon, 23 May 2005 10:24:15 -0700 (PDT) From: Jon Passki To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: 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 17:24:17 -0000 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? TIA, Jon PGP Fingerprint: 1BB0 A946 927B 93C3 ED6A 0466 6692 6C2C 84BE 4122 "Should any political party attempt to abolish social security, unemployment insurance, and eliminate labor laws and farm programs, you would not hear of that party again in our political history. There is a tiny splinter group, of course, that believes you can do these things. Among them are [...] a few other Texas oil millionaires, and an occasional politician or business man from other areas. Their number is negligible and they are stupid." [1] -- Dwight D. Eisenhower, Former President of the USA (Republican), Nov. 8, 1954 [1] http://www.eisenhowermemorial.org/presidential-papers/first-term/documents/1147.cfm __________________________________ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail