> > Apparently Linus told Felix von Leitner (the author of dietlibc - a sma=
> > no nonsense glibc replacement C library) a while ago _not_ to include a=
> > linux kernel headers in userland (i.e. the C library headers in this ca=
> > This imho is obviously wrong since there are definitely a need for incl=
> > kernel headers on a linux platform.
> ??? Necessity no. Are there practical benefits yes.
> The policy of the kernel developers in general is that if your apps
> includes kernel headers and it breaks, it is a kernel problem.
> As for ioctl it is a giant mess that needs to be taken out and shot.
> And yes there are places where even the mighty glibc is in the wrong.
Just acknowledging that it is a problem doesn't solve the problem though.
The question remains how you approach the kernel headers issue at the momen=
My guess is the only way is by including the kernel headers for now and
change it one day when someone decides to clean up the mess.
Every absurdity has a champion who will defend it.
Abraham vd Merwe - 2d3D, Inc.
Device Driver Development, Outsourcing, Embedded Systems
Cell: +27 82 565 4451 Snailmail:
Tel: +27 21 761 7549 Block C, Antree Park
Fax: +27 21 761 7648 Doncaster Road
Email: firstname.lastname@example.org Kenilworth, 7700
Http: http://www.2d3d.com South Africa
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/