Translation(s): none

(!) ?Discussion

New call for test

Help Debian, by testing it and reporting bugs.

This page lists some modifications that you can make to your own (test) machine, in order to test some features (and report bugs!).

The four class of testers (risk) are equally useful to Debian. Classes depend on what situation you can recover yourself 1. Each class of testers is very useful to Debian, since each different level tests a different level of maturity of the Debian release.

. {i} Remember : ?Xen, OpenVz, UML, ?vserver:,Qemu... are your friends to run multiple systems on a single machine.

No risk

This class is suitable to any user, running Debian on production machine(s). Noobies, "man reportbug", and "aptitude show apt-listbugs".

Medium risk

This class is suitable for Desktop/Laptop advanced users.

High risk

Advanced users may have a machine like this for development/test.

Very-high risk

Debian Developers likely have a test machine like this (typically in a Virtual machine).

DD Development System

Some system-wide features that are long-term goals should be enabled on development systems.

  1. Risk = How much time you can spend fixing a bug ; How often you want to backup, to recover potential data loss (1)

  2. No SELinux is not considered harmful, but in some situations the default policy could prevent programs from working. Understanding that a problem is due to SELinux isn't always obvious [For those who don't check /var/log/syslog (2)

  3. users of Debian/i386 can switch from linux-image-2.6-amd64 to linux-image-2.6-686 kernels, in case of problems. (3)