ok, so there are two options :
a) put the kernel header file in the glibc
b) put the kernel header file in the application
for stuff like linux/mroute.h a) might not be very usefull, as only
mroute.h uses it (anything else).
what to do with stuff like isdn or smbfs :
the interface has different versions, so your application needs to
use the same version than the kernel does.
currently they include some kernel header files, and then they will work
fine, but only with that kernel (or kernels with the same interface).
if these applications may not use kernel header files, it will be a lot of
work to make the applications generic and compatible with all kernel versions.
andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu