Posts by One Norse

1) Message boards : BOINC client : BOINC Clients for other platforms (Message 6089)
Posted 18 Oct 2006 by One Norse
Post:
This is becoming a pet peeve of mine. There is no reason that anyone should be getting the 'platform 'x86_64-pc-linux-gnu' not found' error message at all. The 32 bit (i686-pc-linux-gnu) client applications run fine in an AMD 64 bit (x64_64-pc-linux-gnu) environment. I know, because until I 'upgraded' to BOINC version 5.4.9, they were running along quite nicely on my machine (Kubuntu 6.06 for AMD 64). In theory, they also run in the BSD environments, though I haven't tried it myself.

I have spent too much time reading posts on this subject, and have found multiple solutions to the problem, none of which is appealing to an average end user, including:

1)Just change 'x64_86-pc-linux-gnu' to 'i686-pc-linux-gnu' in the client state file : '/var/lib/boinc-client/client_state.xml'. (Sounded great, tried it, BOINC on my machine changes it back.)
2)Download the source and compile BOINC 'with --build=i686-pc-gnu-linux but with 64bit CFLAGS. So the client now works in 64bit mode but recognizes itself as a i686-pc-gnu-linux machine' (Great, but the average user is not enthusiastic about the learning curve involved in compiling and setting flags.)
3)Download the 32 bit apps manually, and follow all the steps necessary to get it to run as an anonymous server including generating, or copying a new app_info.xml file. (OK, but the average user wants to fuss with extra downloads, generating new configuration files, and manual updates not at all.)

None of the above solutions require a different binary for the client app. All of them seem to require some setting, or parameter be changed to get the app and run it.

All of this suggests a solution: have the core client (or the boinc manager; or the server it communicates with at the client end) read the ' x64_86-pc-linux-gnu ' platform name, check to see if a native app is available, and if not send out the app for ' i686-pc-linux-gnu ' and use it. Ditto for BSD.

Is there any reason this can't (or wont) be done?
2) Message boards : BOINC client : Dialup communications probem in Linux/Kubuntu (Message 1624)
Posted 7 Dec 2005 by One Norse
Post:
If I start boinc while my internect connection is working, I have no problems.

If I start boinc first, and then connect to the internet, boinc cannot find the server.

This is frusterating to me, since I want to use an autostart script to run boinc at startup, and manage the data transfers whenever I happen to dial in.

In order to make it work now, I first have to open a terminal, kill bionc, start the connection, then restart boinc, which is a hassle, but I suppose I could write a script to do it.

Any suggestions on how to get boinc to recognize a recently started pppd connection?






Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.