HEADS UP: caution required with updates using custom kernels

O. Hartmann ohartman at zedat.fu-berlin.de
Sat Jun 25 11:18:05 UTC 2016


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?
-------------- 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/64fbc66c/attachment.sig>


More information about the freebsd-current mailing list