Someone else will correct me if I have not really understood this
correctly. As I understand it, the issue is that the kernel header
files are pretty volatile but that the overwhelming majority of
applications written deal with pretty 'standard' kernel functions.
The header files were 'breaking' the compile for application compiled
against the newer header when 'extensions' had been added to existing
functions.
So the header files were severing two groups of people with
significantly different needs: The kernel hacker group, needing the
header files that exactly correspond to the kernel in use and the
applications people that want (and need) a 'stable target'. The
'solution' then, as I understand it, is to periodically choose a
specific set of kernel header files as representative of the series.
--
best,
-bill
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
from a 1996 Micro$loth ad campaign:
The less you know about computers the more you want Micro$oft!
See! They do get some things right!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
