Date: Wed, 24 May 2017 08:40:17 -0600 From: Alan Somers <asomers@freebsd.org> To: "Hartmann, O." <ohartmann@walstatt.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: ino64: desastrous update - recommendations not working!!! Message-ID: <CAOtMX2gQBu-sEtToUTsoLZG-BuiapnqzwcLhz8W_5HAvX%2BJ0jg@mail.gmail.com> In-Reply-To: <20170524124219.3410c416@hermann> References: <20170524124219.3410c416@hermann>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2gQBu-sEtToUTsoLZG-BuiapnqzwcLhz8W_5HAvX%2BJ0jg>