Nathan Meyers wrote:
> There was an interesting comment in a column in the current Linux
> Journal: evidently glibc 2.0 was an "experimental" release. Problem
> is... it was a widely adopted experimental release. The JDK is in good
> company: many applications were broken by the move to 2.1, which is
> slowing acceptance of RH6.
I don't understand how this happened. I would have thought that, like the
kernel, glibc would have 'stable' and 'experimental' versions. No one
should base production (release) code on 'experimental' anything.
How involved is it to fix the problems caused by the glibc 2.1 changes? Where
can I read more about the evolution of Linux threads from the 1.x kernel on? It
seems almost all the sticky Java problems on Linux relate to the thread model.
What areas do the Java-Linux porting team need help with at this point?
Anxiously awaiting a robust Linux 1.2 JDK that'll work with RH 6.x,
Terry
--
[EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
