HEADS UP: caution required with updates using custom kernels
Konstantin Belousov
kostikbel at gmail.com
Sat Jun 25 11:35:51 UTC 2016
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 at 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 at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe at 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.
More information about the freebsd-current
mailing list