Help Debian, by testing it and reporting bugs.
This pages lists some modificationd 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 depends on what situation you can recover your-self ?FootNote(How much time you can spend fixing a bug ; How often you want to backup, to recover potential data loss). Each class of testers is very useful for Debian, since each different level test a different level of maturity of the Debian release.
?TableOfContents(2)
. Remember : ["Xen"], ["OpenVz"], [:QEMU:Qemu]... are your friends to run multiple system on a single machine.
No risk
This class is suitable to any user, running Debian on production machine.
Runs DebianStable.
Use/test any software from DebianStable and report bugs & problems.
- (BTW, also submit documentation improvements : rephrase text, undocumented aspects, etc...).
Use ["KDE"] or ["Xfce"] desktops (you can install many and choose one when you login).
Enable ["SELinux"]?FootNote(No SELinux is not considered harmful, but in some situation, but the default policy could prevent some program from working, and modifying ) in "enforcing=0" mode, then report errors.
- Test Debian-Live CDs on various machines.
- Test installing Debian on any machine you can.
Intel Core2 / AMD64 users : install Debian/i386 with both [wiki:linux-image-2.6-686 -686] and [wiki:linux-image-2.6-amd64 -amd64] kernels flavors.
Medium risk
This class is suitable for Desktop/Laptop of advanced users.
Runs DebianStable.
Install ["StableProposedUpdates"] on your test machine.
Set dash as your /bin/sh
- Enable ["SELinux"] in "enforcing=1" mode, switch to "enforcing=0" in case of problems.
- Use [:DebianIPv6:IPv6].
- Intel Core2 / AMD64 users : install Debian/amd64 distribution.
High risk
Advanced users should have a machine like this for development/test machine
Probably runs ["DebianTesting"].
Enable Dependency-based init systems ["LSBInitScripts"] (insserv).
Set dash as your /bin/sh
- Enable ["SELinux"].
Optionally, you can do some AptPinning of specific unstable's packages.
Very-high risk
Debian Developers should have a test machine like this (typically in a [:SystemVirtualization:Virtual machine]).
Probably runs DebianUnstable
Have a ["DebianUnstable"] for development/test machine.
Enable Dependency-based init systems ["LSBInitScripts"] (insserv).
Set dash as your [:BourneShell:/bin/sh].
- Enable ["SELinux"].
see other entries from the ["LennyReleaseGoals"].
One can test selected packages from [:DebianExperimental:Experimental] (see ["AptPinning"]).
- like KDE4.1
Debian Developers
Hey, the class above this one is for you