Hi,

On Thu, 23 Jun 2016 21:07:51 +0000
Brooks Davis <bro...@freebsd.org> wrote:

> Kernel config minimalists and those running aarch64 and riscv systems
> will want to head this UPDATING message.
> 
> In practice, if you're fairly up to date, doing installworld before
> installkernel will also work (I've tested that case from ALPHA4), but
> is always somewhat risky.
> 
there is another scenario in which you will use a word starting with an
f followed by three letters. I did a normal update, compiled a custom
kernel but did not re-compile my own application. As the application is
required for the start of the machine, I was left with a system which
could not be used. So, downgrading it, recompile the kernel with the
compatibility option, compile the program and then it should work again
is the way.

Erich

> -- Brooks
> 
> ----- Forwarded message from Brooks Davis <bro...@freebsd.org> -----
> 
> Date: Thu, 23 Jun 2016 21:02:05 +0000 (UTC)
> From: Brooks Davis <bro...@freebsd.org>
> To: src-committ...@freebsd.org, svn-src-...@freebsd.org,
>       svn-src-h...@freebsd.org
> Subject: svn commit: r302152 - head
> 
> Author: brooks
> Date: Thu Jun 23 21:02:05 2016
> New Revision: 302152
> URL: https://svnweb.freebsd.org/changeset/base/302152
> 
> Log:
>   Add an UPDATING entry for the pipe() -> pipe2() transition.
>   
>   Approved by:        re (gjb)
>   Sponsored by:       DARPA, AFRL
> 
> Modified:
>   head/UPDATING
> 
> Modified: head/UPDATING
> ==============================================================================
> --- head/UPDATING     Thu Jun 23 20:59:13 2016        (r302151)
> +++ head/UPDATING     Thu Jun 23 21:02:05 2016        (r302152)
> @@ -31,6 +31,14 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 11
>       disable the most expensive debugging functionality run
>       "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
>  
> +20160622:
> +     The the libc stub for the pipe(2) system call has been
> replaced with
> +     a wrapper which calls the pipe2(2) system call and the
> pipe(2) is now
> +     only implemented by the kernels which include "options
> +     FREEBSD10_COMPAT" in their config file (this is the default).

Shouldn't it read 'COMPAT_FREEBSD10'?

Erich
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to