Differences between revisions 22 and 23
Revision 22 as of 2009-03-23 20:56:10
Size: 4319
Editor: FranklinPiat
Comment: Add sidebar
Revision 23 as of 2009-03-23 21:11:17
Size: 4366
Editor: FranklinPiat
Comment: minor sidebar improvements
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
||<style="border-style:none;border:1pt solid #81BBF2"><<Include(/News, ,to="^##RECENT")>>|| ||<style="border-style:none;border:1pt solid #81BBF2"><<Include(/News,from="^##TAG_START",to="^##TAG_TOP7")>>||
Line 13: Line 13:
<<TableOfContents(2)>> ||<style="border:hidden"><<TableOfContents(2)>>||

Translation(s): none

(!) ?Discussion


New call for test

Invalid include arguments "/News,from="^##TAG_START",to="^##TAG_TOP7""!

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".

  • Use/test any software from DebianStable and report bugs & problems.

  • (BTW, also submit documentation improvements: rephrase text, undocumented aspects, etc...).
  • Enable SELinux2 in "enforcing=0" mode. Report errors.

  • Test Debian-Live CDs on various machines.
  • Install ?Kernel/Oops... in the case you ever need it! (It's installed in Lenny/Desktop by default)

  • Test installing Debian on any machine you can.
  • Intel Core2 / AMD64 users : install Debian/i386 with both -686 and -amd64 kernel flavors, but use the latter 3.

Medium risk

This class is suitable for Desktop/Laptop advanced users.

  • Same as above, plus

  • Run DebianStable, with StableProposedUpdates on your test machine (Test the pending 4.0r8 and 5.0.1).

  • Set dash as your /bin/sh (to detect bash-isms).

  • Enable SELinux in "enforcing=1" mode; switch to "enforcing=0" in case of problems.

  • Intel Core2 / AMD64 users : install Debian/amd64 distribution.

High risk

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

  • Same as above, plus

  • Enable Dependency-based init systems LSBInitScripts (Using insserv on Lenny should be fine, but removing it is very risky. see bug 475478).

  • Exceptionally, you can do some AptPinning of specific backports, testing or unstable's packages (but keep in mind that you wouldn't get security updates this way).

  • Test system running DebianTesting falls in this category too.

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)