I just finished installing the boinc framework here, and got the following:

2005-05-26 14:16:54 [---] Insufficient work; requesting more
2005-05-26 14:16:54 [SETI@home] Requesting 17278 seconds of work
2005-05-26 14:16:54 [SETI@home] Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-05-26 14:16:54 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2005-05-26 14:16:54 [SETI@home] Message from server: platform 'i386-portbld-freebsd4.11' not found
2005-05-26 14:16:54 [SETI@home] Project prefs: no separate prefs for home; using your defaults
2005-05-26 14:16:54 [SETI@home] No work from project
2005-05-26 14:16:54 [SETI@home] No work from project
2005-05-26 14:16:54 [SETI@home] Deferring communication with project for 1 days, 0 hours, 0 minutes, and 0 seconds

At this point, I have no idea if I'm not assigned work from the project because of the "platform not found" message, because I have a 2nd computer (windows-based) with assigned work, or because the project is somewhat down.

(am using précompiled binaries for FreeBSD, straight from the ftp.freebsd.org ports collection)

---

2005-05-26 14:16:54 [SETI@home] Message from server: platform 'i386-portbld-freebsd4.11' not found
that means BOINC does not know what seti cruncher to use.

you need 3 things total:
a precompiled BOINC client
a precompiled seti client
app_info.xml

see:
http://boinc.berkeley.edu/anonymous_platform.php

you need 3 things total:
a precompiled BOINC client
a precompiled seti client
app_info.xml

I have a precompiled BOINC client, a precompiled seti client, and the app_info.xml is correct.

The problem is that the FreeBSD-compiled clients apparently reports themselves correctly instead of reporting as "anonymous". I have changed the platform name in the main xml file, but the client doesn't use that value, it fills that value from precompiled version.

So, I can't use the FreeBSD port, I need to compile it on my own.

:(

---

you need 3 things total:
a precompiled BOINC client
a precompiled seti client
app_info.xml

I have a precompiled BOINC client, a precompiled seti client, and the app_info.xml is correct.

The problem is that the FreeBSD-compiled clients apparently reports themselves correctly instead of reporting as "anonymous". I have changed the platform name in the main xml file, but the client doesn't use that value, it fills that value from precompiled version.

So, I can't use the FreeBSD port, I need to compile it on my own.

:(

i couldn't tell from the tgz how BSD sets up boinc for you, but the seti client and app_info.xml with the proper executable references should be in the projects/setiathome.berkeley.edu/ subdirectory of your boinc dir. if that is correct, boinc will not try to download a new seti client.

what BOINC does is look for app_info.xml in the proper directory. if it doesn't find it, it asks the seti servers for a seti client that matches the boinc compile. if it doesnt exist on the seti servers you get the message above.
if boinc does find app_info.xml and either it is incorrect or the seti client is bad, it spits out different error messages.

the boinc source would have had to be specially edited to ignore app_info.xml and there is no reason why any BSD user would have done this. if its in ports, somebody verified that it works.

you need 3 things total:
a precompiled BOINC client
a precompiled seti client
app_info.xml

I have a precompiled BOINC client, a precompiled seti client, and the app_info.xml is correct.

The problem is that the FreeBSD-compiled clients apparently reports themselves correctly instead of reporting as "anonymous". I have changed the platform name in the main xml file, but the client doesn't use that value, it fills that value from precompiled version.

So, I can't use the FreeBSD port, I need to compile it on my own.

:(

i couldn't tell from the tgz how BSD sets up boinc for you, but the seti client and app_info.xml with the proper executable references should be in the projects/setiathome.berkeley.edu/ subdirectory of your boinc dir. if that is correct, boinc will not try to download a new seti client.

what BOINC does is look for app_info.xml in the proper directory. if it doesn't find it, it asks the seti servers for a seti client that matches the boinc compile. if it doesnt exist on the seti servers you get the message above.
if boinc does find app_info.xml and either it is incorrect or the seti client is bad, it spits out different error messages.

the boinc source would have had to be specially edited to ignore app_info.xml and there is no reason why any BSD user would have done this. if its in ports, somebody verified that it works.

I had the same problem. The app_info.xml was there and the executable also. It is important in which Directory you start Your boinc_client! On my system (Freebsd7) the files where found in /var/db/boinc/...
so You have to cd to /var/db/boinc/ and run there, then it finds the client and runs with "anonymous"

MfG Lars