Changes between Version 29 and Version 30 of CPUShare


Ignore:
Timestamp:
08/13/2008 12:11:59 PM (16 years ago)
Author:
Sam Hocevar
Comment:

remove links to Debian packages

Legend:

Unmodified
Added
Removed
Modified

  • CPUShare

    v29 v30  
    1313First of all, you need to make sure your kernel was built with '''`CONFIG_SECCOMP=y`'''. This option is activated by default on the upstream kernel. Unfortunately, it used to be deactivated on official Debian kernels, so you may wish to upgrade or build your own kernel. Without this option, it is not possible to run untrusted bytecode securely and CPUShare will refuse to start.
    1414
    15 If you are using Debian unstable, install CPUShare directly:
     15If you are using Debian unstable or Ubuntu, install CPUShare directly:
    1616{{{
    1717% aptitude install cpushare
    1818}}}
    1919
    20 If you are using Ubuntu or another version of Debian, just download one of the following packages:
    21  * [/files/CPUShare/cpushare_0.47-3_i386.deb cpushare_0.47-3_i386.deb] (32-bit platforms)
    22  * [/files/CPUShare/cpushare_0.47-3_amd64.deb cpushare_0.47-3_amd64.deb] (64-bit platforms)
    23  * [/files/CPUShare/cpushare_0.47-3.dsc cpushare_0.47-3.dsc] (source package)
    2420Then download our [/files/CPUShare/libcaca-sell.cpu sell order] and put it in `/etc/cpushare/`. If your machine has several CPUs, you can place several copies of the same file in `/etc/cpushare/`, just make sure their names end in `.cpu`. Finally, start the CPUShare daemons:
    2521{{{