From: Steve Herber <herber@thing.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] BOINC
Date: Tue, 24 Jan 2006 00:40:03 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0601232352500.26741@thing.com> (raw)
In-Reply-To: <200509190258.24101.cryos@gentoo.org>
Marcus:
Boinc on my amd64 system has been crunching away for the past few months,
once I converted over from the setiathome Classic system. Your ebuilds
have been great. Thanks!
I see that you also maintaining the setiathome ebuild. The package builds
and runs and for that I also thank you.
Do you know if anyone has figured out why the amd64 performance is so
low and if there is a plan to improve it? In my move from Classic to
Boinc my two amd xp systems keep crunching away. I am tempted to turn
off my amd64 version because the performance is so embarrassingly slow.
I hope there is some good news in that area.
Thank you for all your work!
Steve Herber herber@thing.com work: 206-221-7262
Security Engineer, UW Medicine, IT Services home: 425-454-2399
On Mon, 19 Sep 2005, Marcus D. Hanwell wrote:
> On Monday 19 September 2005 00:30, Neil Stone wrote:
>> Does anyone on this list use BOINC on AMD64 systems ??
>>
>> I am trying to use is but getting a mesage about my platform not being
>> supported...
>>
>> Ideas anyone ?
>>
> I am using it, and maintaining it... It is pretty fragile right now, and I
> think I know how to improve it once I get time to sit down with the ebuilds
> and take a look. You want to emerge boinc, then attach to a project. It will
> cry about no platform, then stop it. Then emerge setiathome-4.18 (I think)
> and start boinc after that is done.
>
> You should be crunching away, it works here but I am open to feedback. I will
> be adding some updated ebuilds to automate this more - it is a bug. If you
> emerge setiathome first then when you attach to setiathome it deletes the
> binary client you just built and complains there isn't one! The latest
> snapshots unfortunately do not build here either.
>
> I am a little busy right now, but I will get to it. If you come up with any
> solutions/suggestions then please post them here or to bugzilla.
>
> Thanks,
>
> Marcus
> --
> Gentoo Linux Developer
> Scientific Applications | AMD64 | KDE | net-proxy
>
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-01-24 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 23:30 [gentoo-amd64] BOINC Neil Stone
2005-09-19 1:40 ` Taka John Brunkhorst
2005-09-19 1:58 ` Marcus D. Hanwell
2006-01-24 8:40 ` Steve Herber [this message]
2005-09-19 18:59 ` Vincent ETIENNE
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 20:01 [gentoo-amd64] boinc Dieter Ries
2006-08-01 21:19 ` Steve Herber
2006-08-02 8:19 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0601232352500.26741@thing.com \
--to=herber@thing.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox