On Tue, May 06, 2003 at 10:07:14PM -0700, David S. Miller wrote:
> For example, I just changed the values of a few SADB_EALG_* values in
> pfkeyv2.h. Now ipsec-tools is effectively broken. Oops, when will
> the copy in ipsec-tools get updated?
You just broke the userland ABI which must not happen. at all. That's
why userland having older headers is fine.
Wrong, the ABI in the 2.5.x IPSEC stuff is not cast in
stone yet.
What about if I extend stuff without breaking the ABI?
How do apps get at the new features?
That's why we want the glibc-kernheader package. Or even better
a package of headers that can be used by the kernel and userland,
but this would require people to properly sort out kernel header
functionality like internal structures and prototypes/inlines from
the actual ABI-relevant contents. The networking headers currently
are very bad on this.
Yes, this is one way to deal with it.
Actually, if you look, things like include/linux/xfrm.h are excellent
examples of userland compatible kernel headers :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/