HEADS UP: caution required with updates using custom kernels

[O. Hartmann]

Am Sat, 25 Jun 2016 17:35:31 +0200
Tijl Coosemans <tijl at FreeBSD.org> schrieb:

> On Sat, 25 Jun 2016 18:26:45 +0300 Konstantin Belousov <kostikbel at 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?

... he can, but it is the very same as with the recent kernel.

Besides - I thought "I would have the most recent libc" in this scenario and the kernel
is out of sync? 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20160625/f5ce9585/attachment.sig>