CHOST i386-pc-linux-gnu doesn't work. _why_?
25 Oct 2005 11:23:52 UTC
Topic 190059
(moderation:
Is there a special reason _why_ a client with that CHOST doesn't work? Note that if you use a non-optimized gentoo stage3 install, this is the CHOST you will have, no matter the actual CPU you use.
Apart from that, is there a special reason that CPUs below i686 can't run einstein@home?
Note that I'd also have a few sparc-linux boxes idling around that could be put to good use. But what I gather from earlier forum posts you seem not too interested in gaining a wider hardware-base. Most posts concerning these things came over rather arrogant I'll have to say. Which makes me question whether I really want to donate my cycles to you ...
CHOST i386-pc-linux-gnu doesn't work. _why_?
)
The eye,
That K6 rig you have will need 4 days to process an Einstein workunit, if it were running only Einstein, and if it crunched 24 hours/day, which I would guess is the reason that you haven't set it to work on Einstein. A 333MHz P2 will take even longer, maybe a week of 24/7 crunching. So the oldest, slowest i696s are marginal. IMO, a weaker CPU simply wouldn't be capable of processing a WU within the 14-day deadline.
Someone else will have to answer the other questions that you raise, my one attempt at running Linux (Mandrake 7, if I remember correctly) was an abortion, so I didn't delve more deeply into Linux.
Respects,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK