From owner-freebsd-current@freebsd.org Thu May 25 07:52:35 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 BDEFAD814A7 for ; Thu, 25 May 2017 07:52:35 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 39FE614F4; Thu, 25 May 2017 07:52:34 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.179.134.189]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MWPOI-1dSlGt49IQ-00XfY7; Thu, 25 May 2017 09:52:26 +0200 Date: Thu, 25 May 2017 09:52:20 +0200 From: "O. Hartmann" To: Alan Somers Cc: "Hartmann, O." , FreeBSD CURRENT Subject: Re: ino64: desastrous update - recommendations not working!!! Message-ID: <20170525095220.18f84a56@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170524124219.3410c416@hermann> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/+KmNLfd1k.wJdfhJPldtzvc"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:Gf+WA22yaHI9w1+do6fCT0o2QLyJVNHljVNKUH2M8UA4OQPBJtY gD0BK+Jrj7dbWvZNn2xZW4WGLec2x9Y6x5cmh761osn625zzvl6XQ8qbjE5NfioR+++OVsY cbzw981OV0MMAXjy2JlAqWASowUMjtCi+2bhNMYy3/TBf3gdpMPBU3RhEADsUWmlEIc9RC9 Hk4PMXH+5DwhWMh34Zg1w== X-UI-Out-Filterresults: notjunk:1;V01:K0:hRsnMUCeCl0=:tAiGOY8k5/WunHSS6g0E/3 4vDQ/kNoaJLdoSorOQWvb57kkaQ10H6YUtayyI22SMcTcfEC7Z02eWJ1keLz+P2Ql8wGBrtGb 7R2fgtUsUylz62wGjl6ooGq2N9QCknuim530SJ3S+QqwAl+8z/RKXCUSqFb9+YzVkHUQxU6sI 0imDPC5CvgZ4rXGurjVJrfExhK5ep0PwffzkZs9GIXwHZiZahlZtUxjA54VZu6DgwUn7gpSSl wtOTV+xsgGl1gyTth0FL8Q54HVnuFfGYuRz9x6T4ZENuuyugODsUu7XcGuB7jC+4DgbxhBj6t vAJapF0FlHp+fqnqPt0QXP3oSky/qx4shJXD7TT8OI3JYQkxrObCCZoqdktxvUUtp58GAhxSz l7rtdU+7nXa2/P0QeFTFlFTuZ1QRRtBp/6IwOz4ZtQBE1F4hU7xFSN4pyBT06cMHHQyiooR/s iAZv8R2Tphvpu5z44Mngz6ajUUZWRZrSHt303Q36km1hRgZa0dSEH+44QEVolclc8IpeJ5H/U WzROoOdPju9f2dg1AKfgPhpSorkdSVaUm9IdT+uKT6TyObHGFMWZIJl+6jaORNE0q0oF8xxXL n95o69mdY5AWGq6x4QnrqhpVubJ/Egnc9Xg3h1W49IehT4vQBlqkanssPj8mSn/ltUIeVGkZw cJyR+NfLwkhQBqN3QHYbqY3ctRxhIcdnH8YFurteSvb+7iwAHrFAArk8LzVaaNWPX6r8UhBiQ Nf9ftpEWciPpy/fM1zRTBrA9pPBZv1B/enILPNEyyvzm9ay3Ltq5/Pmajog= 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: Thu, 25 May 2017 07:52:35 -0000 --Sig_/+KmNLfd1k.wJdfhJPldtzvc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Wed, 24 May 2017 08:40:17 -0600 Alan Somers schrieb: > On Wed, May 24, 2017 at 4:42 AM, Hartmann, O. wr= ote: > > 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 =20 >=20 > Did you use a custom kernel config file without COMPAT_FREEBSD11? > _______________________________________________ YES :-( First, I wasn't aware of the fact since it hasn't been mentioned in UPDATIN= G, secondly, after I've read it many times, I realised too late that I had COMPAT_FREEBS= D10 instead of COMPAT_FREEBSD11 defined ... after a very stressful day mistake after mista= ke ... Now, after recompiling a proper kernel, on working systems which do have th= e "old" world but the "new" kernel the SIGSYS for /bin/sh vanished and the procedure of u= pdating went as expected. On boxes, where I had a terrible mixture of both world and no proper kernel= , I recompiled the kernel stuff on a working and compatible system and copied /boot/kernel= to the wrecked system and proceeded as recommended. That made things working again. --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/+KmNLfd1k.wJdfhJPldtzvc Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWSaNNAAKCRDS528fyFhY lCEqAf4ns5bgGAzInzz2VGYNS35Qwzuz/yv3RApy+odwBd+HsiLsTjsW8v1Xw+Ip SRmbWS1Uqho1PbFUNDZIqvhXTOArAf9OvaPDqdanbVfol0VDPTMp5pLDzvf1XX+0 NUyR6il8al3uJgNv1rbqu3xQPQmlrJ2AtKwSOeT9/PcwF8vlctzH =NVqf -----END PGP SIGNATURE----- --Sig_/+KmNLfd1k.wJdfhJPldtzvc--