> While this is true, the real answer is that libc5 should include its
> own kernel headers that are seperate from the kernel. User space
> applications should never use kernel headers anyway. If they absolutly
> _must_ include a kernel header, they should have their own copy
> instead of relying on the kernel header. (Debian already does this BTW)
having own copies of kernel header files is a very *bad* idea IMHO.
either I have to add tons of #if this_kernel_vesion etc. or I have to
change [many?] application sources if the kernel header files change
(e.g. one more entry in a structure...)
Harald
--
All SCSI disks will from now on ___ _____
be required to send an email notice 0--,| /OOOOOOO\
24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig, \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik // / \\ \
koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^