Dotsch, could you place a post about Other Platform BOINC versions on the Boinc Forums as well, so I can sticky it there?

I have made a post in the boinc forums. Thank you very much !

---

By any chance would a port to the Amiga platform be considered?

Hm, very problematic.
So far I know it is a propetary OS, so the porting is very hard. Also not shure, if there is anyone here which is famliar with this OS and wan't to port BOINC and SETI. Also I am not shure if it is worth to invest the time of porting, there are very rare systems out there...
On which hardware did it run ? - Is Amiga OS released for the the PPC CPUs ? - If not, and it would run on the 68xxx CPUs, it have not the CPU power to complete any WU within any deadline.

I believe later amigas ran on the PPC chip, but all the other considerations you and ageless mention are pretty valid. Once can hold on to hope though... thanks for the consideration.

---

Is here anyone missing a port to a not supported platform, which is not avaialable and are which should to ported for ?

I have lots of CPU horsepower to give to projects like this but my "platform of choice" -- OpenVMS on Alpha and Itanium -- still doesn't have any indicated porting activity or binaries. I just got an e-mail today from the SETI@home project wondering why I hadn't contributed any work units lately. I can't!

I can understand that the available resources (people) for porting is limited, but is the code source such that each OS + platform combination really needs to be uniquely written or customized from some other sources? If it does then that might explain the shortage of resources.

I'm not a strong 'C' programmer by any means. But if the only porting that really has to be done is to get around compiler differences I have done that before with other packages, some of them quite large.

I am willing to make a stab at an OpenVMS port of the SETI client but given all the various sources out there I'd need to be told which one(s) to start with. As I understand that BOINC is required then maybe I should start there first.

/Marty

Is here anyone missing a port to a not supported platform, which is not avaialable and are which should to ported for ?

I have lots of CPU horsepower to give to projects like this but my "platform of choice" -- OpenVMS on Alpha and Itanium -- still doesn't have any indicated porting activity or binaries. I just got an e-mail today from the SETI@home project wondering why I hadn't contributed any work units lately. I can't!

I can understand that the available resources (people) for porting is limited, but is the code source such that each OS + platform combination really needs to be uniquely written or customized from some other sources? If it does then that might explain the shortage of resources.

I'm not a strong 'C' programmer by any means. But if the only porting that really has to be done is to get around compiler differences I have done that before with other packages, some of them quite large.

I am willing to make a stab at an OpenVMS port of the SETI client but given all the various sources out there I'd need to be told which one(s) to start with. As I understand that BOINC is required then maybe I should start there first.

/Marty

This post brings up an interesting point about porting.

I wonder what the feasibility/interest would be to port Boinc and the clients to Java rather than C? After all, it's platform independant so that multiple ports would be unnecessary, except maybe in the case of optimized clients using specific instruction sets for specific cpus.

---

This post brings up an interesting point about porting.

I wonder what the feasibility/interest would be to port Boinc and the clients to Java rather than C? After all, it's platform independant so that multiple ports would be unnecessary, except maybe in the case of optimized clients using specific instruction sets for specific cpus.

I think, java would not provide any usefull performance.

---

I have lots of CPU horsepower to give to projects like this but my "platform of choice" -- OpenVMS on Alpha and Itanium -- still doesn't have any indicated porting activity or binaries. I just got an e-mail today from the SETI@home project wondering why I hadn't contributed any work units lately. I can't!

I can understand that the available resources (people) for porting is limited, but is the code source such that each OS + platform combination really needs to be uniquely written or customized from some other sources? If it does then that might explain the shortage of resources.

There was some persons, which has started porting SETI 4.x on VMS, but they had some problems, and never finished there work. - I will search around for the threads and postings of this people, and post you the links.
Also, for SETI Enhanced (V.5.x) there was not any porting activity for VMS.

The problem is, that VMS is very different to Unix, and there are less volunteers which has enought VMS knowledge to port it.
Normaly on the Unix systems, the porting is easy, but it could be, that on VMS some things would be changed in the code.

I'm not a strong 'C' programmer by any means. But if the only porting that really has to be done is to get around compiler differences I have done that before with other packages, some of them quite large.

I am willing to make a stab at an OpenVMS port of the SETI client but given all the various sources out there I'd need to be told which one(s) to start with. As I understand that BOINC is required then maybe I should start there first.

Great ! I think, there are a lot of people, which could/would use an VMS port. What do you think about to make your binaries public, if you have success ?

For compiling SETI, you need the BOINC Source, which requires libcurl, openssl and the zlib. The BOINC Client Sources are available via CVS : http://boinc.berkeley.edu/anonymous_platform.php
I recommend you to use the stable branch (BOINC 5.4.11). The BOINC Client 5.5 and 5.6 are alpha releases, which I did not recommend for normal usage.

SETI requires the BOINC Client, Libs and API and additional the fftw libs (www.fftw.org). The fftw libs speedup the processing, but SETI could work without.
There are two different Versions at SETI in the moment, the Beta Project uses the actual versions, and the main project the SETI 5.12 to 5.15 Sources.
It is very important, not to use 5.17 in the main project.
The SETI sources are available in tarballs. The tarball from 13th May 2006 are 5.13.
Please look here for further infos : http://setiathome.berkeley.edu/sah_porting.php

If you have any problems or questions with the porting, feel free to contact me via email (seti_boinc at dotsch dot de) or here in the forums.

Also, the boinc_opt mailinglist is a good point, if you have questions or problems about the porting. The list has mostly less postings, but is readen from a lot of peoples, including the SETI devs and the BOINC devs, inluding Eric Korpela and David Anderson.

---

The problem is, that VMS is very different to Unix, and there are less volunteers which has enought VMS knowledge to port it.
Normaly on the Unix systems, the porting is easy, but it could be, that on VMS some things would be changed in the code.

I was ahead of you here. I found this blog, where it says:

So far, noone has come up with a port of the new Boinc version of SETI for OpenVMS. I've looked at the code, but because of the design decisions that the Berkeley team made, unless OpenVMS Engineering comes out with a full implementation of fork(), BOINC won't port any time soon (unless some brave soul wants to convert it to pthreads).

---

The problem is, that VMS is very different to Unix, and there are less volunteers which has enought VMS knowledge to port it.
Normaly on the Unix systems, the porting is easy, but it could be, that on VMS some things would be changed in the code.

I was ahead of you here. I found this blog, where it says:

So far, noone has come up with a port of the new Boinc version of SETI for OpenVMS. I've looked at the code, but because of the design decisions that the Berkeley team made, unless OpenVMS Engineering comes out with a full implementation of fork(), BOINC won't port any time soon (unless some brave soul wants to convert it to pthreads).

So far I know, had Yuri Dario the same problem with a missing/bad fork implementation on OS/2. He has written some fixes which work for OS/2.
I think it is worth to try it on VMS, too.

---

can you please post binaries for slackware? I recently switched to linux and am not yet comfortable compiling stuff myself.

---

can you please post binaries for slackware? I recently switched to linux and am not yet comfortable compiling stuff myself.

Linux (x86) is officaly supported by BOINC and SETI.
The BOINC binaries are available at boinc.berkeley.edu/download.php. If you attach to the SETI projects, the needed binaries will downloaded automaticly.

---

I think it is time make another update of the list of the available ports :

Stefan Urbat ; http://www.lb.shuttle.de/apastron/boincDown.shtml :
- Solaris x86 (i686 and AMD64)
- Solaris SPARC BOINC client 5.4.9 and SETI App for UltraSPARC I/II and IIIi
- Linux on AMD64 (Opteron), Itanium (IA64), PPC and Power CPUs, SPARC and Alpha
- HPUX 10.20/11.0/11i (V1 and V2.) on PARISC
- HPUX 11i (V.1 and V.2) on IA64 (Itanium)
- FreeBSD i386 and Alpha
- NetBSD i386
- OpenBSD i386

FreeBSD Ports ; http://www.freebsd.org/cgi/ports.cgi?query=boinc-setiathome&stype=all
- FreeBSD, source via the FreeBSD Ports

Yuri Dario ; http://groups.yahoo.com/group/seti-warp/message/1467
- OS/2 i386

Nekochan ; http://www.nekochan.net/nekoware/index.php?path=current/
- Irix

KWSN ; http://www.zadra.org/index.php?module=Downloads
- Windows MMX/SSE/SSE2/SSE3 optimized and Linux x86 SSE/SSE2 optimized
The optimized Linux app works on older GLIBC 2.x Linuxes, too.

Alex Kan ; http://tbp.berkeley.edu/~alexkan/seti/
- MacOS X optimized for G4 and G5


The ports for AIX and TRU64 are still in work.

The most third party binaries are listed on the boinc third party site (boinc.berkeley.edu/download_other.php), too.
____________

Is here anyone missing a port to a not supported platform, which is not avaialable and are which should to ported for ?

Any chance SCO 5.0.[5,6,7] will ever be supported?

---

Any chance SCO 5.0.[5,6,7] will ever be supported?

You are the first person, which asks for SCO binaries.
How many systems do you have ?
Do do have expiriance in compiling and are you interested in port it to UnixWare ? - The sources are public, and I can assist you in compiling. Otherwise, I could try it my self. But I have no Unixware installed, so I will need some time.

So far I know, is it posible to let Solaris x86 and Linux x86 binaries run on UnixWare. - I think it would be worth to try it out, too. Because it could be get a faster success, than compiling it.

---

Any chance SCO 5.0.[5,6,7] will ever be supported?

You are the first person, which asks for SCO binaries.
How many systems do you have ?
Do do have expiriance in compiling and are you interested in port it to UnixWare ? - The sources are public, and I can assist you in compiling. Otherwise, I could try it my self. But I have no Unixware installed, so I will need some time.

So far I know, is it posible to let Solaris x86 and Linux x86 binaries run on UnixWare. - I think it would be worth to try it out, too. Because it could be get a faster success, than compiling it.

I have found some intersting documentations and howtos, to let Linux binaries run on Unixware with lxrun :
http://uw713doc.sco.com/en/LX_uw/CONTENTS.html
http://developers.sun.com/solaris/articles/lxrun
http://www.ugcs.caltech.edu/~steven/lxrun/lxrun-FAQ.html

Also there are a lot of articles, which using UnixWare binaries at Solaris x86 and vice versa. The most said, that the binaries should be dynamic linked.

---

Seti-openvms, do you have started the portings to OpenVMS ?

Telecom, have you tried to let the Linux or Solaris x86 BOINC and SETI binaries on SCO UnixWare/OpenServer ?

---

Finally I manage to install seti on my debian HAPPA.
If someone out there have a box, here is how I have installed it.

-Set you sources.list (/etc/apt/sources.list) to the follow debian ftp

deb http://ftp.de.debian.org/debian unstable main

-update
# apt-get update
-install the boinc client
# apt-get install boinc-client
-install the seti client
# apt-get install boinc-app-seti
Don’t try to install the boinc manager its broken!!!
-Edit the “remote_hosts.cfg” to allow remote manager control
(/var/lib/boinc-client /remote_hosts.cfg) add the ip of a trusted boinc manager

-->Boinc runs as a daemon and I had some problem restart it so I rebooted...

-So reboot
After the reboot access your new seti from a trusted boinc manager and attached it to the seti project.
Reboot again and your good to go!
BR,
dbmms

Thank you very much for testing and documentating !

Am I right, that debian is the only distro, which supports Linux on PARISC ?

I did knew that debian has made ports for all platforms. - I will add this in the next summary, too.

---

yes, as far that I know

I like the way 'debian' deals with network install / updates. Really easy to install once you know the name of the application and the network location of the repository (not trivial...).

BR,

Any chance SCO 5.0.[5,6,7] will ever be supported?

You are the first person, which asks for SCO binaries.
How many systems do you have ?
Do do have expiriance in compiling and are you interested in port it to UnixWare ? - The sources are public, and I can assist you in compiling. Otherwise, I could try it my self. But I have no Unixware installed, so I will need some time.

So far I know, is it posible to let Solaris x86 and Linux x86 binaries run on UnixWare. - I think it would be worth to try it out, too. Because it could be get a faster success, than compiling it.

I have found some intersting documentations and howtos, to let Linux binaries run on Unixware with lxrun :
http://uw713doc.sco.com/en/LX_uw/CONTENTS.html
http://developers.sun.com/solaris/articles/lxrun
http://www.ugcs.caltech.edu/~steven/lxrun/lxrun-FAQ.html

Also there are a lot of articles, which using UnixWare binaries at Solaris x86 and vice versa. The most said, that the binaries should be dynamic linked.

I have successfull tested to let Linux binaries running on SCO UnixWare. SETI runs without any los of performance. So you can install the LKP packages and use the Linux binaries for crunching on SCO UnixWare.
Please look at this thread for a detailed installation describtion : http://setiathome.berkeley.edu/forum_thread.php?id=35426

---

It is time again to make another update of the list of the available ports :

Stefan Urbat ; http://www.lb.shuttle.de/apastron/boincDown.shtml :
- Solaris x86 (i686 and AMD64)
- Solaris SPARC BOINC client 5.4.9 and SETI App for UltraSPARC I/II and IIIi
- Linux on AMD64 (Opteron), Itanium (IA64), PPC and Power CPUs, SPARC and Alpha
- HPUX 10.20/11.0/11i (V1 and V2.) on PARISC
- HPUX 11i (V.1 and V.2) on IA64 (Itanium)
- FreeBSD i386 and Alpha
- NetBSD i386
- OpenBSD i386

FreeBSD Ports ; http://www.freebsd.org/cgi/ports.cgi?query=boinc-setiathome&stype=all
- FreeBSD, source via the FreeBSD Ports

Yuri Dario ; http://groups.yahoo.com/group/seti-warp/message/1467
- OS/2 i386

Nekochan ; http://www.nekochan.net/nekoware/index.php?path=current/
- Irix

KWSN ; http://www.zadra.org/index.php?module=Downloads
- Windows MMX/SSE/SSE2/SSE3 optimized and Linux x86 SSE/SSE2 optimized
The optimized Linux app works on older GLIBC 2.x Linuxes, too.

Alex Kan ; http://tbp.berkeley.edu/~alexkan/seti/
- MacOS X optimized for G4 and G5

Debian Linux Ports for all platforms which are supported
- BOINC Client : http://packages.debian.org/boinc-client
- BOINC manager : http://packages.debian.org/boinc-manager
- SETI application : http://packages.debian.org/boinc-app-seti

SCO UnixWare and SCO OpenServer : http://setiathome.berkeley.edu/forum_thread.php?id=35426


The ports for AIX, TRU64 and OpenBSD on AMD64 are in work.

The most third party binaries are listed on the boinc third party site (boinc.berkeley.edu/download_other.php), too.

---

An time to make another update...

Stefan Urbat ; http://www.lb.shuttle.de/apastron/boincDown.shtml :
- Solaris x86 (i686 and AMD64)
- Solaris SPARC BOINC client 5.4.9 and SETI App for UltraSPARC I/II and IIIi
- Linux on AMD64 (Opteron), Itanium (IA64), PPC and Power CPUs, SPARC and Alpha
- HPUX 10.20/11.0/11i (V1 and V2.) on PARISC
- HPUX 11i (V.1 and V.2) on IA64 (Itanium)
- FreeBSD i386 and Alpha
- NetBSD i386
- OpenBSD i386

FreeBSD Ports ; http://www.freebsd.org/cgi/ports.cgi?query=boinc-setiathome&stype=all
- FreeBSD, source via the FreeBSD Ports

Yuri Dario ; http://groups.yahoo.com/group/seti-warp/message/1467
- OS/2 i386

Nekochan ; http://www.nekochan.net/nekoware/index.php?path=current/
- Irix

KWSN ; http://www.zadra.org/index.php?module=Downloads
- Windows MMX/SSE/SSE2/SSE3 optimized and Linux x86 SSE/SSE2 optimized
The optimized Linux app works on older GLIBC 2.x Linuxes, too.

Alex Kan ; http://tbp.berkeley.edu/~alexkan/seti/
- MacOS X optimized for G4 and G5

Debian Linux Ports for all platforms which are supported
- BOINC Client : http://packages.debian.org/boinc-client
- BOINC manager : http://packages.debian.org/boinc-manager
- SETI application : http://packages.debian.org/boinc-app-seti

SCO UnixWare and SCO OpenServer : http://setiathome.berkeley.edu/forum_thread.php?id=35426

SETI@SummoneR.mikrocomp.hu ; http://www.mikrocomp.hu/seti
- OpenBSD on AMD64 (Opteron)

The ports for AIX and TRU64 are still in work.

The most third party binaries are listed on the boinc third party site (boinc.berkeley.edu/download_other.php), too.

---