From owner-freebsd-current@FreeBSD.ORG Wed Nov 26 18:39:23 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E69B16A4CE for ; Wed, 26 Nov 2003 18:39:23 -0800 (PST) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DD0943FA3 for ; Wed, 26 Nov 2003 18:39:22 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.12.10/8.12.9) with ESMTP id hAR2dL7P024950 for ; Wed, 26 Nov 2003 21:39:22 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: Date: Wed, 26 Nov 2003 21:39:20 -0500 To: current@FreeBSD.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Change install-order? (upgrade from static to dynamic root) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Nov 2003 02:39:23 -0000 I just installed 5.1-release on a sparc64, and then cvsup'ed to the latest snapshot of -current. Since that update is such a large jump in time, I was going from a system which had no /rescue or /libexec to one which builds everything dynamically. This gets one into a mess in the middle of installworld, where suddenly almost everything dies with messages like: "ELF interpreter /libexec/ld-elf.so.1 not found" I know others have run into this problem, but there seems to be nothing in UPDATING to warn people about it. Or at least, I didn't see anything in /usr/src/UPDATING under sparc64. Instead of warning people, I was wondering if there would be any downside to having installworld always install /rescue first (since that should not depend on anything else), and install /libexec before installing executables. - - - - I did recover from that mess by taking advantage of tips given in previous threads on this situation. I used the rescue binary in to give me a few key commands, doing something like: cd /usr/obj/usr/src/rescue/rescue ./rescue mkdir /usr/tempbin ./rescue ln rescue /usr/tempbin/cp ./rescue ln rescue /usr/tempbin/cat ./rescue ln rescue /usr/tempbin/ldconfig ./rescue ln rescue /usr/tempbin/ln ...etc... PATH=/usr/tempbin cd /usr/obj/usr/src/libexec/rtld-elf cp -p * /libexec ldconfig -m /lib cd /usr/obj/usr/src/usr.bin/xinstall cp -p xinstall /usr/bin/install I may have missed a few steps there, but I think that got me far enough along that I could 'make install's in /usr/src/lib and /usr/src/libexec. Once I was confident that I had enough working parts installed, I went back and repeated the 'make installworld'. Seems to have worked out OK. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu