Download CPUShare Now: cpushare-0.49.tar.bz2
The CPUShare client software is licensed under the GNU LGPL version 2.1 and is not covered by any pending or issued patent as far as I know.
Windows and OSX users interested in selling their CPU resources should download the CPUShareLiveCD from their own CPUShare accounts after creating a sell order.
There are available packages for Gentoo and Debian. Other distributions should follow.
All other Linux users can simply unpack the tarball and follow the instructions in the README. If you install python-twisted in your preferred distributions all needed dependencies should be picked up and resolved automatically. The Linux Kernel must also be compiled with CONFIG_SECCOMP=y.
| Linux | The CPUShare client currently only runs on top of the 2.6 Linux Kernel. Kernel version >= 2.6.12 is required because the CPUShare client software depends on the seccomp kernel feature that has been merged into 2.6.12. If you don't have Linux installed on your systems, you can run the CPUShareLiveCD and run it with some virtualization solution. |
| i686, x86_64 and ppc64 | The supported CPU architectures on the sell side are: i686 (not older than the Athlon for AMD and not older than the Pentium Pro for Intel), x86_64 (Opteron and EM64T) and ppc64 (G5). ppc32 should work too. You can quickly check if your CPU resources can be already sold by running the command `uname -m`. Porting to ia64 (64bit) and all other architectures will be easy if there's demand. The buyer can simultanously buy all different architectures without noticing the difference (except for the performance). The buyer is free to run in any Linux architecture that supports python and that can compile gcc successfully. |
| GCC and Binutils | The bytecode that will run remotely is normally written in C (but it can be written in asm or in any other language) and it requires gcc and its tool chain (ld/gas) to be compiled. The seccomp-loader is also written in C. Any recent version will work fine. If the buyers want to compute not just in their native architectures, but in all architectures supported by CPUShare, they can create a cross compilation environment with the cross-compiler.sh script inside the tarball. |
| Python | For maximum security against buffer overflows and to speedup the development, most of the CPUShare client software is written in python. This also provides flexibility to quickly write new buy clients. Performance is not an issue, network will be the bottleneck, and all CPU intensive computations runs on the bare hardware and not on top of the python virtual machine. Python Version >= 2.3.3 is required but version >= 2.4 is recommended. |
| ZopeInterface | Only if your distribution doesn't ship with a Twisted package and in turn if you're planning to install it by hand, you will have to install the Zope Interfaces first (Version >= 3.0.1 is required). |
| pyOpenSSL | All communications with the CPUShare servers will be encrypted with OpenSSL. Version >= 0.6 is required. All distributions should provide this package, however if you're installing it by hand you can consider using the CPUShare pyOpenSSL that contains additional features not included in the mainline package (that seems not actively maintained). |
| Twisted | Twisted is needed for the asynchronous networking communications of the CPUShare protocol. Version >= 1.3.0 is required but version >= 2.0.1 is recommended. |
This web page contains forward looking statements that
involve risks and uncertainties that could cause actual results to differ materially
from the forward-looking statements. The forward-looking statements should be considered
in light of these risks and uncertainties.