Can the current diffs be posted somewhere so people who have executed a
non-commercial source license with Sun can try to help with the port?
I see nothing in the Source license I signed (even though it says version
1.1.x at the top, but they sent me 1.2 sources) to keep the
platform-dependent di
I realize this is off-topic and off-list, but I have tried
twice to email Rob Schoening privately and both times the
email bounced. And the fact is I'm rather desparate.
I saw Rob's post regarding Java on the BeOS and it renewed
my hopes. Is there any Java port for the BeOS? I don't care
what ver
"Seth M. Landsman" wrote:
>
> > 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 :). Inste
> Sean> We still don't have anything to work with though, or even
> Sean> acknoledgement that someone who is dealing with the situation has seen
> Sean> my request yet.
>
> We've seen it, it's just no that easy to create a short (or medium sized)
> example that shows the problem.
>
>The diffs we have are publicly available when we have a port done.
>All of the 1.1.x diffs had been posted.
Unfortunately, Sun didn't give me the option of obtaining the 1.1.x sources.
>
>As to 1.2 (Java 2) there are different licensing rules that we are under
>at the moment.
I'll take your
On Mon, 01 Feb 1999 15:15:40 -0800, Rob Schoening wrote:
>
>> 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 fi
Out of curiosity, how is this policy (of not being able to release any
source code) affected, if at all, by the new Java license, if and when it
applies to the platform? Can source code be distributed in patch form
(as it normally is anyhow) before the finished product passes the JCK,
under the ne
> 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
On Mon, 1 Feb 1999, Seth M. Landsman wrote:
> > 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
> Sean Kellner writes:
Sean> 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
> 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
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 hack
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
13 matches
Mail list logo
