From owner-freebsd-current@freebsd.org Wed May 24 10:42:24 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E058DD7BEA3 for ; Wed, 24 May 2017 10:42:24 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47D3D1D01 for ; Wed, 24 May 2017 10:42:23 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([87.138.105.249]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MTCDO-1dLcyZ1spy-00S7NH for ; Wed, 24 May 2017 12:42:21 +0200 Date: Wed, 24 May 2017 12:42:19 +0200 From: "Hartmann, O." To: FreeBSD CURRENT Subject: ino64: desastrous update - recommendations not working!!! Message-ID: <20170524124219.3410c416@hermann> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:U6Sdhg80INiD1O3g2vUXfBWhKzJBC1omyl5g4ym6KmNfWyxbcM2 tjQw4CwZUSq7k10GGDElPYDXAVAt3uLecZ6ILJaVK/XLVGUJM/HheWWqscQ3gKpYTNPJLlD X8uZhZ6VJBeXZg9R9CH7hsGz5X848uibm25BF90zXkg6M6u86j7GFpEMnwTDslJmk8oUOkV YC7ZhhcFdddqc/AF1OqKw== X-UI-Out-Filterresults: notjunk:1;V01:K0:03y3akd+Y9Y=:r9ZEYZZMWoc9wfS6109+Zh SQSzfyvDcSY4mgrgX6zmc4M2JnlVJ6GnttI7OVLT7BWUz3AuEdoWFbu+lNXrmLyinBT8TFqFn ANvu2AO5iYVKm5FR7N8riZe6TYiw26zOH0l9HP2pRPoNXX+tDRqxsxwPoLhMgIom38zIJkh6a jkYAHlXRy+DZQOr/idN9vAKtE657LNMO9i41sid3c7ZRwiTqw+M1RVr97+l7Xm5rPydVH1g+3 k+iUg9WtJQ7prUa0CtzUXmQNIfBh5hQaq4rXcwT1Y7ZMlfcJ0UwMfZFN4Zukhm2VjIqyhoyfV yqkLfcSA3eJoIsQAAAjexz0X/irReJIrSE/Bb6DGRBu0gDYQpuHdtrXhunqaLZpBX431qOIJk YW5VtuK4kbYUsspjXR+6A7fk5XXAYU6E3ix2TFhERgR2jbafHyjpuM2y5f5tB86CGLpiT7S2Z rH8KHSMHZk+Ka6rJRf2+oTknBLjYXceLVtqrhlWT7+pg5D3IkLD+shWVZxSZEtBDe4/oP2Ybm OHh91a3t1V6chrSZW62LuqsiHlwpm4uGbBGpuNPPRwfqsqU/6ig8AQI3EXBw/SNDi/W6Nj4zT SWUIoq3wTq+e/6RmB3mTBIDQ8RFHtWnh+Iuz2/A1Le/VVnNuH2M0jLxTHA7q9FeSt+uRR1pIz DxUq7CwICAx0lVJ3i+JS3ruTsnEa4LPlxcrKDKY0KNJUDjnu+nC8u9IyAT67B2D4CT2MTpvAe RmXGfktTVK8xgguBk3HvqTD8Chnilfh8AC4HNqDrTLT1WIME24q/0Oc74E8Nm7t5DMtdkA2C/ mc6L4+TImd4EjK1khh4b1JWDxoLacqou/qv3vjK95i+y//yyM2l5VnXEk3XsoeyvvK4CIxjRw JGEte6hLHho6tzsy6qYw== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 24 May 2017 10:42:25 -0000 On almost every CURRENT that has been updated according to UPDATING entry 2017-05-23 regarding ino64, the recommended update process ends up in a desaster or, if the old environemnt/kernel is intact, itr doesn't work. Procedure: make -jX buildworld buildkernel [successful] make installkernel [successful] reboot Booting single user mode as recommended withnthe newly installed kernel BUMMER! When it comes to the point to type in the full path of /bin/sh, /bin/sh immediately fails with SIGNAL 12 In this case, I can boot without problems the old kernel and the system works again. But, depending on the entry revision from which I started the 22nd, or 23rd of May ino64-deal, there is a more harsh failure! According to the above recommendation of updating, BUMMER! doesn't occur at that point and the shell /bin/sh starts as expected. Performing mergemaster -Fp also performs well without any questions or installations so far, but then make installworld BUMMER! again and this time with fatal consequences! The installation fails in libexec/rtld-elf or something like that in the source/object tree after copying libexec/ld-elf.so.1. I see /libexec/ld-elf.so.1 successfully copied with the security copy marked with appendix .old being of a conclusive date and time. The installworld bails out, leaves the tree in a mixture of old and new binaries and now, thanks, the whole system ist wrecked. When trying to reboot such a half-ready installation in single user mode, I can't even get an shell enymore. How can I fix this emergency case with the tools aboard? Since there is no compiler or build infrastructure any more on the USB bootimage, I can not simply installworld and installkernel - the boot image is useless - on this list I had such a discussion in March. For short: I have the intact and complete /usr/obj tree and I think it would be a great deal to be able to simply boot via USB memstick and perform installworld with propper settings of DESTDIR= and sibblings. Yes, now what is to do ... :-( Help appreciated and thanks in advance for those reading so far. O