Date: Thu, 25 May 2017 09:52:20 +0200 From: "O. Hartmann" <ohartmann@walstatt.org> To: Alan Somers <asomers@freebsd.org> Cc: "Hartmann, O." <ohartmann@walstatt.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: ino64: desastrous update - recommendations not working!!! Message-ID: <20170525095220.18f84a56@thor.intern.walstatt.dynvpn.de> In-Reply-To: <CAOtMX2gQBu-sEtToUTsoLZG-BuiapnqzwcLhz8W_5HAvX%2BJ0jg@mail.gmail.com> References: <20170524124219.3410c416@hermann> <CAOtMX2gQBu-sEtToUTsoLZG-BuiapnqzwcLhz8W_5HAvX%2BJ0jg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Am Wed, 24 May 2017 08:40:17 -0600 Alan Somers <asomers@freebsd.org> schrieb: > On Wed, May 24, 2017 at 4:42 AM, Hartmann, O. <ohartmann@walstatt.org> wrote: > > 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 > > 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 UPDATING, secondly, after I've read it many times, I realised too late that I had COMPAT_FREEBSD10 instead of COMPAT_FREEBSD11 defined ... after a very stressful day mistake after mistake ... Now, after recompiling a proper kernel, on working systems which do have the "old" world but the "new" kernel the SIGSYS for /bin/sh vanished and the procedure of updating 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. -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWSaNNAAKCRDS528fyFhY lCEqAf4ns5bgGAzInzz2VGYNS35Qwzuz/yv3RApy+odwBd+HsiLsTjsW8v1Xw+Ip SRmbWS1Uqho1PbFUNDZIqvhXTOArAf9OvaPDqdanbVfol0VDPTMp5pLDzvf1XX+0 NUyR6il8al3uJgNv1rbqu3xQPQmlrJ2AtKwSOeT9/PcwF8vlctzH =NVqf -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170525095220.18f84a56>