Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Jun 2016 17:17:14 +0200
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        freebsd-current@freebsd.org
Subject:   Re: HEADS UP: caution required with updates using custom kernels
Message-ID:  <20160625171714.7e318044.ohartman@zedat.fu-berlin.de>
In-Reply-To: <20160625113544.GS38613@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>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
Am Sat, 25 Jun 2016 14:35:44 +0300
Konstantin Belousov <kostikbel@gmail.com> schrieb:

> On Sat, Jun 25, 2016 at 01:18:06PM +0200, O. Hartmann wrote:
> > Am Sat, 25 Jun 2016 10:02:38 +0300
> > Konstantin Belousov <kostikbel@gmail.com> schrieb:
> >   
> > > On Fri, Jun 24, 2016 at 10:50:34PM +0000, Brooks Davis wrote:  
> > > > pipe(2) had an unnecessarily odd calling convention (ignoring the
> > > > argument the user thought they were passing and returning the two file
> > > > descriptors via the two return registers).  This required machine
> > > > dependent assembly for every target and special handling in tracing
> > > > tools (ktrace, dtrace, etc).  On 64-bit platforms, pipe(2)'s
> > > > implementation is the only reason the two-register return model needs to
> > > > exist at all (on 32-bit platforms it allows off_t to be returned from
> > > > lseek).    
> > > getpid() is another instance.
> > > _______________________________________________
> > > freebsd-current@freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"  
> > 
> > That all is a nice explanation, but how to recover from a broken system, on which the
> > order of installation wasn't performed the right way?  
> 
> Copy the libc.so.7 binary from the build area to /lib manually, e.g. using
> rescue shell.
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

I did so, but there is no effect.

Whenever I try to build a kernel/world, I receive this from the shell:

root@localhost: [src] make update
*** Signal 12

Stop.
make: stopped in /usr/src
.ERROR_TARGET='update'
.ERROR_META_FILE=''
.MAKE.LEVEL='0'
MAKEFILE=''
.MAKE.MODE='normal'
.CURDIR='/usr/src'
.MAKE='make'
.OBJDIR='/usr/obj/usr/src'
.TARGETS='update'
DESTDIR=''
LD_LIBRARY_PATH=''
MACHINE='amd64'
MACHINE_ARCH='amd64'
MAKEOBJDIRPREFIX='/usr/obj'
MAKESYSPATH='/usr/src/share/mk'
MAKE_VERSION='20160606'
PATH='/sbin:/bin:/usr/sbin:/usr/bin'
SRCTOP='/usr/src'
OBJTOP='/usr/obj/usr/src'

These two machines in question are victims "of the early adopter" - the warning came way
too late! At work, I did the same update - but I did an installworld prior to the usual
installkernel - and everything seems so far to work, even without COMAPT_FREEBSD10 in the
kernel.

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.


Thank you in advance for help, kind regards,

Oliver

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXbqB6AAoJEOgBcD7A/5N8azQH/3Lf3ldgGX1dgobLnzgQsorQ
sW/Lyb7Ae3WjoFmIwzsAD1JpWBwBNJ/E4DAHIurMDcQh2BjXKvlHzHoMhmYbwko5
eQIUkKCyVCdt0J0bkRilV3SVnToFFXxdSGlweCXvxc9ISd3fIDGvT3rBEbmKGRY8
PsKU8C4/l1epH9eqEue4YMaTEUcggfiIcErVbGLsbhreTnSVFLcqxe7GtYDcwrXF
uP9XhrQFheeCd46zJPFgQkgi2ydvPtvetKW0OSZCNxWui3Yyz3b5sf9SylF/nrM+
v+OGjnSweBI8oB4Qg2HpcMKBfjL71Qm/XZbHIB8jOU78YPeGdk0hwLv2N0JegaQ=
=oBCy
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160625171714.7e318044.ohartman>