Debian Reference

Peter Kitson

ISBN : -

Order a printed copy of this book from Amazon--UNAVAILABLE--


Cover Design - Debian Reference
 

For your free electronic copy of this book please verify the numbers below. 

(We need to do this to make sure you're a person and not a malicious script)

Numbers

 




Sample Chapter From Debian Reference
     Copyright © Osamu Aoki



1.5 Basics of the Debian distributions

Debian maintains three different distributions simultaneously. These are:

stable — Most useful for a production server since it is only updated with security fixes. See ‘The stable distribution’ on page 6.

testing—The preferred distribution for a workstation since it contains recent releases of desktop software which have received a bit of testing. See ‘The testing distribution’ on page 7.

unstable — Cutting edge. The choice of Debian developers. See ‘The unstable distribution’ on page 7.

When packages in unstable have no release-critical (RC) bugs filed against them after the first week or so, they are automatically promoted to testing.

Debian distributions also have code names as described in ‘Debian distribution codenames’ on page 8. Before Woody was released in August 2002, the three distributions were, respectively, Potato, Woody, and Sid. After Woody was released the three distributions were, respectively, Woody, Sarge, and Sid. When Sarge is released, the stable and unstable distributions will be Sarge and Sid; a new testing distribution will then be created (initially as a copy of stable) and given a new code name.

Subscribe to the low-volume mailing list debian-devel-announce@lists.debian.org for important announcements about Debian. See ‘The Debian archives’ on page 5.

If you want to use versions of packages that are more current than the versions that were released with the distribution you are using, then you can either upgrade to a later distribution as described in ‘Upgrading a distribution to stable, testing, or unstable’ on page 73, or you can upgrade only selected packages. If the package can’t be upgraded easily then you may want to backport it as described in ‘Port a package to the stable system’ on page 90. Tracking the testing distribution can have the side effect of delaying the installation of packages containing security fixes. Such packages are uploaded to unstable and migrate to testing only after a delay.

If you mix distributions, e.g., testing with stable or unstable with stable, you will eventually pull in core packages such as libc6 from testing or unstable and there is no guarantee that these will not contain bugs. You have been warned.

Running the testing or unstable distribution increases your risk of hitting serious bugs.

This risk can be managed by deploying a multibooting scheme with a more stable Debian distribution or by deploying the nice trick of using chroot as described in ‘chroot’ on page 125. The latter will enable running different Debian distributions simultaneously on different consoles.

After an explanation of the fundamentals of the Debian distribution in ‘Debian fundamentals’ on the next page, you will be given some basic information to help you live happily with the latest software, taking advantage of the testing and unstable distributions of Debian. The impatient should proceed immediately to ‘Debian survival commands’ on page 83. Happy upgrading!