Changes between Version 28 and Version 29 of CPUShare


Ignore:
Timestamp:
08/13/2008 11:07:58 AM (16 years ago)
Author:
Sam Hocevar
Comment:

remove mention of Debian bug

Legend:

Unmodified
Added
Removed
Modified

  • CPUShare

    v28 v29  
    1111== Getting started ==
    1212
    13 First 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 is deactivated on official Debian kernels (you can voice your opinion on [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474648 bug report #474648] if you want to use CPUShare). Without this option, it is not possible to run untrusted bytecode securely and CPUShare will refuse to start.
     13First 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
    1515If you are using Debian unstable, install CPUShare directly: