Hi, On Mon, Sep 5, 2011 at 7:50 PM, Adrian Chadd <adr...@freebsd.org> wrote: > That's not what the COMPAT_* hooks are for. > > They're for backwards compatibility of normal userland binaries, not > binaries which use a FreeBSD-specific kernel ABI. > What do you define as "normal" and where do you draw the line ?
>From my point of view, I should be able to run a FreeBSD 9.0 kernel (when released) on top of a FreeBSD 5 userland without such issues. That's what backward compatibility is. _Every_ piece of the ABI exposed by the kernel[0] should be kept compatible, even funky behavior userland might ends up relying on. However, if as you say, you (the committers folks) willingly break the exposed ABI, well, sorry, but that can no longer be called "backward compatible"... That said, this has turned out of context. Now, to come back to my original issue, how am I supposed to track down cross-release issue ? swap storage ? [sic...] Regards, - Arnaud [0]: ... with very few exception, such are security issue when there is no other choices available. _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
