Re: MFC of socket/protocol reference improvements

On Sun, 11 Jun 2006, Robert Watson wrote:

(1) Normally, RELENG_* has significant constraints on changes to the kernel
APIs used by loadable modules -- especially for device drivers. In the
past, we've not made a lot of changes to the protocol switch interface,
and historically it hasn't been a run-time extensible interface. Andre
has recent made changes to allow IP protocols to be loaded at runtime,
such as IP divert, and these will be affected, however. Do we consider
modules programmed against these interfaces to be "breakable" -- i.e., the
require a recompile and or changes in the RELENG_6 branch?

From a policy standpoint, breaking modules in a -STABLE branch is
forbidden since it causes pain for 3rd party developers. Exceptions can be made for changes that provide more benefit than damage caused by breaking the ABI.

Usually the question revolves around, "Does anyone actually distribute modules that use that interface?" :-)

--
Doug White | FreeBSD: The Power to Serve
dwhite@xxxxxxxxxxxxx | www.FreeBSD.org
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages