How to handle lack of updated kernel headers

[Pieter Hollants]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Seeing that Mariusz Mazur definitely won't be able to provide his
linux-libc-headers any longer (see
http://lists.pld-linux.org/mailman/pipermail/llh-announce/2006-March/000002.html),
what exactly are the options to use more recent 2.6.x kernel versions
effectively?

If I'm correct, I could of course continue using the last released
2.6.12 headers, but then I would be unable to use any new kernel
features since that release.

All the information on the Net says that there is the need for
"sanitized" kernel headers exported to user-space. But seeing that
uclibc comes with some own headers, what's the deal with the headers fed
to uclibc itself? What happens if I feed it with 2.6.15's include/ dir,
for example? fix-headers.sh runs over it, I guess, but would the result
really be "bad" headers for user-space?

- --
Pieter "Fate" Hollants <pieter at hollants.com>
(a current GnuPG key is available at www.hollants.com/gnupg.txt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEGDZFa8/cc5b1WpwRAsv6AJ9SJwCP+/vdwa+XKpXwlwPTxMtdNgCgk6/W
syAvbfKFd5McHIGQuYxzK0E=
=15vw
-----END PGP SIGNATURE-----