Christopher Faylor wrote:
However, here is one of the times I repeated that I
don't want to do this over the internet:
[...]
Fixing this problem will be difficult. Dealing with
race conditions like this always is difficult.
Indeed, as an embedded software designer I know this
first hand.
I don't
Larry Hall wrote:
Chris has already answered that question earlier in
the discussion. He needs physical access to the
machine to resolve this problem. Remote access isn't
enough.
Forgive my ignorance, but I read the archives back to
1 jan 2004 but found no explanation why remote access
doesn't
On Tue, 1 Feb 2005, Joris van der Sande wrote:
Larry Hall wrote:
Chris has already answered that question earlier in
the discussion. He needs physical access to the
machine to resolve this problem. Remote access isn't
enough.
Forgive my ignorance, but I read the archives back to
1
On Tue, Feb 01, 2005 at 11:01:11PM +0100, Joris van der Sande wrote:
Larry Hall wrote:
Chris has already answered that question earlier in the discussion. He
needs physical access to the machine to resolve this problem. Remote
access isn't enough.
Forgive my ignorance, but I read the archives
The hyperthreading problem reproduces perfectly on my
Hush ATX 2.8 GHz P4 (www.hush-pc.com): building my
application fails consistent (within 1 minute) with
hyperthreading enabled.
Since my machine is on-line 24/7, would it help if I
gave Christopher (or another motivated developer) remote
At 07:45 PM 1/30/2005, you wrote:
The hyperthreading problem reproduces perfectly on my Hush ATX 2.8 GHz P4
(www.hush-pc.com): building my application fails consistent (within 1 minute)
with hyperthreading enabled.
Since my machine is on-line 24/7, would it help if I gave Christopher (or
6 matches
Mail list logo