Date: Sat, 25 Jun 2016 17:35:31 +0200 From: Tijl Coosemans <tijl@FreeBSD.org> To: Konstantin Belousov <kostikbel@gmail.com>, "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: freebsd-current@freebsd.org Subject: Re: HEADS UP: caution required with updates using custom kernels Message-ID: <20160625173531.104842ac@kalimero.tijl.coosemans.org> In-Reply-To: <20160625152645.GB38613@kib.kiev.ua> References: <20160623210751.GB7860@spindle.one-eyed-alien.net> <20160624060019.5e650ad9.ohartman@zedat.fu-berlin.de> <20160624155111.GB20770@spindle.one-eyed-alien.net> <330789230754140e38fb527973e23405@ultimatedns.net> <20160624225034.GC20770@spindle.one-eyed-alien.net> <20160625070238.GG38613@kib.kiev.ua> <20160625131806.14fa4799.ohartman@zedat.fu-berlin.de> <20160625113544.GS38613@kib.kiev.ua> <20160625171714.7e318044.ohartman@zedat.fu-berlin.de> <20160625152645.GB38613@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 25 Jun 2016 18:26:45 +0300 Konstantin Belousov <kostikbel@gmail.com> wrote: > On Sat, Jun 25, 2016 at 05:17:14PM +0200, O. Hartmann wrote: >> Is there a way to salvage the situation without relying on "customized" >> third party kernels? >> >> I usually use /bin/csh - so this might be of use. > > You need either kernel with COMPAT_FREEBSD10, or simpler, newer libc. > You could take that libc anywhere, e.g. from the ALPHA5 binaries recently > uploaded. There is no way to fix build with the combination of bits you > have at present self-hosting. Can't he boot kernel.old?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160625173531.104842ac>