Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-science
Lists: gentoo-science: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-science@g.o
From: "Marcus D. Hanwell" <cryos@g.o>
Subject: New Boinc based SETI@home client
Date: Mon, 22 Aug 2005 19:46:41 +0100

I added the new Boinc based SETI@home client to the tree on Sunday. I would 
really appreciate some testing from the people on this list if any of you 
have the time. It is quite different to the old client, which is now 

I think it is mostly working and Boinc downloads the client for x86 machines. 
The remaining issue I seem to have is that when running /etc/init.d/boinc 
attach it deletes the custom downloaded client and tries to download its own. 
On amd64 this breaks it as they don't provide one. Emerging setiathome-4.18 
again and then restarting boinc fixes this, with a 24 hour delay in 
communication with the scheduling server!

So I think the attach function needs a little more magic in it to deal with 
this, or possibly a patch to the boinc function that attaches to new projects 
to allow it to recognise our custom client. Any ideas you guys might have on 
this problem would be appreciated, as well as feedback on how well the new 
packages work.

The old versions of setiathome will be masked shortly as the download URLs are 
no longer valid, and I don't believe that the project works with the old 
client anymore (anyone confirm this?).


Gentoo Linux Developer
Scientific Applications | AMD64 | KDE | net-proxy
pgpM5hgGubTmv.pgp (PGP signature)
Lists: gentoo-science: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
lapack transition
Next by thread:
Previous by date:
Re: Re: Scientific herd leadership
Next by date:

Updated May 31, 2012

Summary: Archive of the gentoo-science mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.