Darren Steven wrote:
>
> Sean Kellner wrote:
>
> > The status report lists that the current holdup is in a threading
> > issue. So is there any way to create a new piece of source that would
> > display the problem without any restrictions from Sun? This would allow
> > quite a few kernel hackers to go over it and at least see if the bug is
> > in linuxthreads or in the code, and probably fix it. There are a few of
> > us here who would love to help out and get this thing out the door, and
> > this seems like the only way we can.
> >
> > --
> > Sean Kellner
> > [EMAIL PROTECTED]
>
> Once again - the Open Source development model shows why it works...Many
> minds with a want/need to fix, and a fresh look (to paraphrase what a well
> known person once said "The solution is always obvoius to someone")
> --
>
> Darren Steven
> [EMAIL PROTECTED]
Exactly. We have a few people here who love to dig into the kernel and
muck with stuff, and then a few of us who are really good with Java, and
a few who have plenty of experience with concurrent programming on
multiple platforms. And then some are even great at all three.
We still don't have anything to work with though, or even
acknoledgement that someone who is dealing with the situation has seen
my request yet. If this was a truly open source project, we'd have
already gotten to the code and fixed it by now :). Instead, we have to
wait for someone to give us some code to work with, prefereably without
having anything proprietary to Sun so we can all chip in.
--
Sean Kellner
[EMAIL PROTECTED]
