User Tools

Site Tools



This noncommercial distribution started in 1993 and continues to be a popular distribution, with many volunteer developers around the world contributing to the project. Debian is a huge distribution that takes some time to install. After you install the base Debian system, you can install and upgrade Debian packages easily with a package installer called apt-get (where apt stands for the Advanced Packaging Tool). Debian is available free of charge from . Debian is the basis for several other recent distributions, including Knoppix, MEPIS, and Ubuntu. At this writing, the most recent release of Debian is Debian 9, code-named Stretch.

Snippet from Wikipedia: Debian

Debian (), also known as Debian GNU/Linux, is a Linux distribution composed of free and open-source software, developed by the community-supported Debian Project, which was established by Ian Murdock on August 16, 1993. The first version of Debian (0.01) was released on September 15, 1993, and its first stable version (1.1) was released on June 17, 1996. The Debian Stable branch is the most popular edition for personal computers and servers. Debian is also the basis for many other distributions, most notably Ubuntu.

Debian is one of the oldest operating systems based on the Linux kernel. The project is coordinated over the Internet by a team of volunteers guided by the Debian Project Leader and three foundational documents: the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. New distributions are updated continually, and the next candidate is released after a time-based freeze.

Since its founding, Debian has been developed openly and distributed freely according to the principles of the GNU Project. Because of this, the Free Software Foundation sponsored the project from November 1994 to November 1995. When the sponsorship ended, the Debian Project formed the nonprofit organization Software in the Public Interest to continue financially supporting development.



Debian (

) is an operating system composed of free software mostly carrying the GNU General Public License.<ref>

</ref> The operating system is developed by an internet collaboration of volunteers aligned with The Debian Project.

Debian systems can use either the Linux kernel (known as the Debian GNU/Linux distribution), the FreeBSD kernel (known as the Debian GNU/kFreeBSD distribution) or, more recently, the GNU Hurd kernel (more precisely, the GNU Mach microkernel and its servers; known as the Debian GNU/Hurd distribution).<ref name=“About Debian”>


Debian GNU/Linux is one of the most popular Linux distributions for personal and Internet server machines.<ref>




</ref> Debian is seen as a solid Linux, and as a consequence has been used as a base for other Linux distributions; DistroWatch lists 144 active Debian derivatives.<ref>Based on Debian, status active Distrowatch</ref><ref>Debian Derivatives Debian wiki</ref> Debian has been forked many times, but is not affiliated with its derivatives.

The vital role the Debian project plays in free software is demonstrated by its advancement of development and security patches relating to its strong participation in CVE compatibility efforts.<ref>



/Linux installation program language selection]]

/Linux console login and welcome message]]

to view Debian package details]]

The Debian project released a new kernel as of Wheezy's release date: the Debian GNU/kFreeBSD kernel. Debian now supports two kernels, Linux and kFreeBSD, and offers other kernels as development works (GNU Hurd and NetBSD). This project's new kernel has recently come out of preview but still lacks the amount of software available as on Debian's Linux. The kernel is offered for Intel/AMD 32-bit and 64-bit architecture machines.<ref>

</ref> Wheezy is officially supported on ten machine architectures and also brought support for two new architectures: s390x and armhf.

Debian is still primarily known as a Linux distribution with access to online repositories hosting over 37,500 software packages.<ref>

</ref> Debian officially hosts free software on its repositories but also allows non-free software to be installed. Debian includes popular programs such as LibreOffice,<ref>

</ref> Iceweasel (a rebranding of Firefox), Evolution mail, CD/DVD writing programs, music and video players, image viewers and editors, and PDF viewers. The cost of developing all the packages included in Debian 5.0 lenny (323 million lines of code) using the COCOMO model, has been estimated to be about US$ 8 billion.<ref>

</ref> Ohloh estimates that the codebase (68 million lines of code) using the same model, would cost about US$ 1.2 billion to develop.<ref>


Debian offers 10 DVD and 69 CD images for download and installation, but using just the first optical iso image of any of its downloadable sets is sufficient. Debian requires the first installable image, but uses online repositories for additional software. Debian's basic installation requires only the first CD or DVD of its release in order to have a working desktop experience. The Wheezy release offers to install a variety of default Desktops from its DVD boot menu (GNOME, KDE, Xfce, and LXDE) and allows visually-impaired people to use its installer. The new feature in Debian's latest installer of Wheezy for the visually-impaired supports a mode which is textual but performs audio output for each stage of installation. Debian offers different network installation methods for expert users. A minimal install of Debian is available via the 'netinstall' CD, whereby Debian is installed with just a base and later additional software can be downloaded from the internet.<ref>


Debian's new form of installation-from-USB has been supported since its sixth edition. Debian supports this capability inside its first iso-file of any of its install media sets (whether CD or DVD) and does not require the help of 'extraction tools' such as unetbootin. This new feature is called Hybrid iso in which an .iso file is dumped to USB. Debian is one of the few Linux distributions offering this feature with its install iso media, and other distributions are starting to adopt alike.

Other notable new features in Debian's latest release include: Multiarch, which allows 32-bit Linux software to run on 64-bit operating system installs;<ref>

</ref> improved multimedia support, reducing reliance on third-party repositories; compiled packages with hardened security flags; AppArmor, which can protect a system against unknown vulnerabilities; and systemd, which shipped as a technology preview.

Debian's install-media is distributed via downloadable CD/DVD images from its mirrored sites,<ref>

</ref> BitTorrent, jigdo and from optional retailers.<ref>


Desktop environments

Debian offers stable and testing CD images specifically built for GNOME (the default), KDE Plasma Workspaces, Xfce and LXDE.<ref>

</ref> Less common window managers such as Enlightenment, Openbox, Fluxbox, GNUstep, IceWM, Window Maker and others can also be installed.

It was previously suggested that the default desktop environment of version 7.0 “Wheezy” may be switched to Xfce, because GNOME 3 might not fit on the first CD of the set.<ref>

</ref> The Debian Installer team announced that the first CD includes GNOME thanks to their efforts to minimize the amount of disc space GNOME takes up.<ref>


</ref> In November 2013 it was announced that the desktop environment of version 8.0 “Jessie” would change to Xfce. Demand for Xfce will be evaluated and the default environment may switch back to GNOME again just before Jessie is frozen.<ref>;a=commitdiff;h=dfca406eb694e0ac00ea04b12fc912237e01c9b5</ref><ref></ref>

MATE and Cinnamon are not available in the official Debian package repositories.


Debian Pure Blend is a subset of Debian that is configured to support a particular target group out-of-the-box.<ref name=“debian-blends”>


Debian Blend is a Debian-based distribution having an explicit goal of improving Debian as a whole. Consequently, all extras offered by Blends will either become part of Debian, or are temporary workarounds to solve a need of the target group which cannot yet be solved within Debian.<ref name=“debian-blends” />

Debian Live

Debian also releases live install images for CDs, DVDs and USB thumb drives, for the i386 and amd64 architectures, and with a choice of desktop environments. These Debian Live images allow the user to boot from a removable media and run Debian without affecting the contents of their computer. This may be useful for a prospective new user trying out Debian and testing its compatibility with their system, or for an experienced user wishing to do maintenance work on a system (Debian, other GNU/Linux, Windows, etc.) without booting it. These live images also offer the option to install Debian on the user's computer.<ref>


Personalized Debian Live images can be built with the live-build tool,<ref>

</ref> in which images are generated for CD/DVD/USB drives and for netboot purposes. Live-magic is another tool used for personalizing Debian Live images, along with the assistance of a graphical interface.

{{anchor|EMBEDDED}}Embedded systems

Recent releases of Debian support an increasing number of ARM-based NAS devices. The cheap NSLU2 was supported by Debian 4.0 and 5.0<ref>

</ref> and can be upgraded to Debian 6.0 although there are problems with a 6.0 clean install.<ref>

</ref> Debian 5.0 added support for the Buffalo Kurobox Pro,<ref name=“”>

</ref> and Debian 6.0 for the SheevaPlug.<ref name=“ReferenceA”>


Other NAS devices supported by Debian, but perhaps not so widely used by home users, include GLAN Tank<ref>The GLAN Tank is a Japanese NAS device, described on Japanese Wikipedia GLAN Tank

</ref> and Thecus N2100 as of Debian 4.0,<ref>

</ref> QNAP Turbo Station (TS-109, TS-209, TS-409) and HP mv2120 as of Debian 5.0,<ref name=“”/> and QNAP Turbo NAS TS-11x, TS-21x and TS-41x, OpenRD, Lanner EM7210 and Intel SS4000-e as of Debian 6.0.<ref name=“ReferenceA”/>


Package management

Debian's official standard for administering packages on its system is the apt toolset. Though for many years apt-get has been the defacto tool for administering packages on Debian, suggestions point to aptitude as better for interactive use as aptitude supports better search on package metadata.<ref>


The dpkg database

dpkg is the storage information center of installed packages and provides no configuration for accessing online repositories. The dpkg database is located at /var/lib/dpkg/available and contains the list of “installed” software on the current system.

The dpkg command

The dpkg command tool is used for the dpkg database without capability of accessing online repositories.<ref>

</ref> The command can work with local .deb package files as well as information from the dpkg database.

APT tools for online repositories

An APT tool allows administration of an installed Debian system for retrieving and resolving package dependencies from online repositories. APT tools share dependency information(/etc/apt configuration files) and downloaded cache .deb files(/var/cache/apt/archives). APT tools depend on verifying what is installed in the dpkg database in order to determine missing packages for requested installs.

  • aptitude is a command tool and offers a TUI interface. This command's support is self-contained for full features of APT administration
  • apt-get and apt-cache are command tools of the standard APT-class toolset apt package. The package is called “apt” and supplies the command “apt-cache” as well as “apt-get”. “apt-get” installs and removes packages. “apt-cache” is used for searching packages and displaying package information.


The gdebi tool and other front-ends
  • gdebi is an APT which can be used in command-line and on the GUI. gdebi combines the functionality of the dpkg tool and APT package resolving with online repositories. The local .deb file in the GUI environment's file manager can be associated to be opened with gdebi providing a graphical experience of installing packages via double clicking. gdebi can also install a local .deb file via the command line alike the dpkg command, but with access to online repositories. If gdebi is requested to install a local .deb file that requires to install a dependency, it then searches the repositories as defined in the common APT configuration folder (/etc/apt) and performs to resolving and downloading missing packages.

There are various front-ends for APT, both graphical and command-line based. Graphical applications include Software Center, Synaptic and Apper.



The Debian Project offers three distributions, each with different characteristics. The distributions include packages which comply with the Debian Free Software Guidelines (DFSG), which are included inside the main repositories.<ref name=“distributions”>

</ref> Debian also officially supports the optional backports repository for the stable distribution.<ref>



When in need of updated versions of software, it is possible to use Debian testing instead of stable as it usually contains more modern, though slightly less stable packages. Another alternative is to use Debian backports, which are “recompiled packages from testing (mostly) and unstable (in a few cases only, e.g. security updates), so they will run without new libraries (wherever it is possible) on a stable Debian distribution”.<ref>


Official repositories are the following:

  • stable, currently aliased wheezy, is the current release that has stable and well-tested software. Stable is made by freezing testing for a few months where bugs are fixed to make the distribution as stable as possible; then the resulting system is released as stable. It is updated only if major security or usability fixes are incorporated. After Debian 6.0, new releases will be made every two years.<ref name=“two-year-cycle”/> Stable's CDs and DVDs can be found in the Debian website.<ref name=“distributions” />
  • backports: This repository provides more recent versions than stable for some software. It is mainly intended for users of stable who need a newer version of a particular package.
  • testing, currently aliased jessie, is what the next major release will be and is currently being tested. The packages included in this distribution have had some testing in unstable but they may not be completely fit for release yet. It contains more modern packages than stable but older than unstable. This distribution is updated continually until it enters the “frozen” state. Security updates for testing distribution are provided by Debian testing security team. Testing's CDs and DVDs can be found on the Debian website.<ref name=“distributions” />
  • unstable, permanently aliased sid, repository contains packages currently under development; it is updated continually. This repository is designed for Debian developers who participate in a project and need the latest libraries available, or for those who like to “live on the edge”, so it will not be as stable as the other distributions. There are no official CDs/DVDs because it is rapidly changing and the project does not support it, although CD and DVD images of sid are built quarterly by aptosid. Additionally, the other two distributions can be upgraded to unstable.<ref name=“distributions” />

: Depreciating repositories in Debian:

  • oldstable, presently aliased squeeze, is the prior stable release. It is supported until 1 year after a new stable is released. Debian recommends to update to the new stable once it has been released.<ref>


  • snapshot: The snapshot repositories provide older versions of other repositories. They may be used to install a specific older version of some software.

: Other repository in Debian:

  • experimental: is meant to be a temporary staging area of highly experimental software for developers. Even though it's documented as a 'distribution' branch from Debian's documentation, many dependency packages that fulfill experimental software are commonly resolved with the unstable branch. This branch of experimental software is not as documented as the other branches as it shouldn't even be referenced by advanced users.<ref>


Non-free and Unofficial repositories

The Debian Free Software Guidelines (DFSG) defines its distinctive meaning of the word “free” as in “free and open source software” (FOSS), although it is not endorsed by the Free Software Foundation or GNU foundation; reason being Debian's servers includes and supports a proprietary repository and documentation that recommends non-free software.<ref>


</ref> In accordance with its guidelines, a relatively small number of packages are excluded from the distributions' main repositories and included inside the non-free and contrib repositories. These two repositories are not officially part of Debian GNU/Linux. The Debian project offers its distribution without non-free repositories but can be adopted manually after initial setup.

  • non-free: repositories include packages which do not comply with the DFSG (this does not usually include legally questionable packages, like libdvdcss).<ref name=“distributions” />
  • contrib: repositories include packages which do comply with the DFSG, but may fail other requirements. For instance, they may depend on packages which are in non-free or requires such for building them.<ref name=“distributions” />



:These repositories are not part of the Debian Project, they are maintained by third party organizations. They contain packages that are either more modern than the ones found in stable or include packages that are not included in the Debian Project for a variety of reasons such as: e.g. possible patent infringement, binary-only/no sources, or special licenses that are too restrictive. Their use requires precise configuration of the priority of the repositories to be merged; otherwise these packages may not integrate correctly into the system, and may cause problems upgrading or conflicts between packages from different sources. The Debian Project discourages the use of these repositories as they are not part of the project.

Hardware support

Hardware requirements

Debian has no hardware requirements beyond those of the Linux kernel and the GNU tool-sets (gcc, coreutils, bash, etc.). Therefore, any architecture or platform to which these packages have been ported, and for which a Debian port exists, can run Debian.<ref name=“hreqs2”>


Linux, and therefore Debian, supports the use of multiple processors in a system (symmetric multiprocessing). This does not inhibit support for single-processor systems.<ref name=“hreqs2” />

Debian's recommended system requirements differ depending on the level of installation, which corresponds to increased numbers of installed components:<ref name=“hreqs1”>


| Install desktop | RAM minimum<ref name=“hreqs1” /> | RAM recommended<ref name=“hreqs1” /> | Hard drive space used<ref name=“hreqs1” />
No 64&nbsp;MB 256&nbsp;MB 1&nbsp;GB
Yes 128&nbsp;MB 512&nbsp;MB 5&nbsp;GB

A 1&nbsp;GHz processor is the minimum recommended for desktop systems.<ref name=“hreqs1” />

The real minimum memory requirements are much less than the numbers listed in this table. Depending on the architecture, it is possible to install Debian with as little as 20&nbsp;MB of RAM for s390, or 48&nbsp;MB of RAM for i386 and AMD64. Similarly, disk space requirements, which depend on the packages to be installed, can also be reduced by manually selecting the packages needed.<ref name=“hreqs1” />

It is possible to run graphical user interfaces on older or low-end systems, but the installation of window managers instead of desktop environments is recommended, as desktop environments are more resource-intensive.<ref name=“hreqs1” />

Depending on the nature of the server, RAM and disk space requirements can vary widely.<ref name=“hreqs1” />

Architecture ports


–> Most software packages in the official Debian repositories are compiled for an abundance of available and older instruction sets.

Stable ports

As of the current stable release, the official ports are:<ref>


Unstable ports

In the current official unstable distribution there are following ports:

Unofficial ports

Unofficial ports are also available as part of the unstable distribution at

  • alpha

    : DEC Alpha architecture

  • hppa

    : HP PA-RISC architecture

  • m68k

    : Motorola 68k architecture on Amiga, Atari, Macintosh and various embedded VME systems

  • powerpcspe

    : PowerPCSPE architecture (binary-incompatible variant of the PowerPC)

  • ppc64

    : PowerPC64 architecture supporting 64-bit PowerPC CPUs with VMX

  • sh4

    : Hitachi SuperH architecture

  • sparc64

    : Sun SPARC architecture with 64-bit userland

  • x32

    : 32-bit userland for modern amd64 processors, incompatible with i386



port was the second official one in Debian, and has been part of five stable Debian releases. Due to its failure to meet the release criteria, it was dropped before the release of etch but is in current status of being revived. The


(OABI,<ref name=“”/> &lt;armv4t),




ports were dropped before the release of squeeze.


Debian is known for its serious manifesto social contract and policies.<ref name=socialcontract>Debian Social Contract</ref> Debian's policies and team efforts focus on collaborative software development and testing processes and dedicates lengthy development time between unstable and stable release cycles. As a result of its strictly guarded policies, a new distribution release for Debian tends to occur every one to two years.<ref name=“debfaq-def”>

</ref> The strategy policies used by the Debian project for minimizing software bugs, albeit with longer release cycles, has allowed it to remain one of the most stable and secure Linux distributions.



The Debian Project is a volunteer organization with three foundational documents:

  • The Debian Social Contract defines a set of basic principles by which the project and its developers conduct affairs.<ref name=“socialcontract”/>
  • The Debian Free Software Guidelines define the criteria for “free software” and thus what software is permissible in the distribution, as referenced in the Social Contract. These guidelines have also been adopted as the basis of the Open Source Definition. Although it can be considered a separate document for all practical purposes, it formally is part of the Social Contract.<ref name=“socialcontract” />
  • The Debian Constitution describes the organizational structure for formal decision-making within the Project, and enumerates the powers and responsibilities of the Debian Project Leader, the Debian Project Secretary, and the Debian Developers generally.<ref name=“constitution”>


Debian is developed by over three thousand volunteers.<ref name=“free kernel”>

</ref> Each of them sustains some niche in the project, be it package maintenance, software documentation, maintaining the project infrastructure, quality assurance, or release coordination. Package maintainers have jurisdiction over their own packages, although packages are increasingly co-maintained. Other tasks are usually handled by the domain of smaller, more collaborative groups of developers.

Debian is supported by donations through several nonprofit organizations around the world. Most important of these is Software in the Public Interest,<ref name=“releases”>

</ref> the owner of the Debian trademark and umbrella organization for various other community free software projects.<ref>


The project maintains official mailing lists and conferences for communication and coordination between developers.<ref>

</ref> For issues with single packages or domains, a public bug tracking system is used by developers and end-users. Informally, Internet Relay Chat channels (primarily on the OFTC and freenode networks) are used for communication among developers and users also.

Together, the Developers may make binding general decisions by way of a General Resolution or election. All voting is conducted by Cloneproof Schwartz Sequential Dropping, a Condorcet method of voting. A Project Leader is elected once per year by a vote of the Developers; in April 2010, Stefano Zacchiroli was voted into this position, succeeding Steve McIntyre. The Debian Project Leader has several special powers, but they are far from absolute and rarely used. Under a General Resolution, the Developers may, among other things, recall the leader, reverse a decision by him or his delegates, and amend the constitution and other foundational documents.

The Leader sometimes delegates authority to other developers in order for them to perform specialized tasks. Generally this means that a leader delegates someone to start a new group for a new task, and gradually a team gets formed that carries on doing the work and regularly expands or reduces their ranks as they think is best and as the circumstances allow.

A role in Debian with a similar importance to the Project Leader's is that of a Release Manager. Release Managers set goals for the next release, supervise the processes, and make the final decision as to when to release.<ref name=“releasemanagers”>



Project leaders

The Debian Project Leader (DPL) is the public face of the project and defines the current direction of the project.<ref>What does a Debian Project Leader do</ref> The project has had the following leaders:<ref>


A supplemental position, Debian Second in Charge (2IC), was created by Anthony Towns. Steve McIntyre held the position between April 2006 and April 2007. From April 2009 to April 2010 this position was held by Luk Claes. Stefano Zacchiroli abandoned this unofficial position when elected in April 2010.<ref>

Stefano Zacchiroli |date =2010-03-12 |publisher =Debian |quote=I do not believe in the utility of a DPL board, so I will not have one; nor I will have a second in charge (2IC).}}</ref>

Release managers

  • Brian C. White (1997–1999)
  • Richard Braakman (1999–2000)
  • Anthony Towns (2000–2004)
  • Steve Langasek, Andreas Barth and Colin Watson (2004–2007)
  • Andreas Barth and Luk Claes (2007–2008)
  • Luk Claes and Marc Brockschmidt (2008–2009)
  • Luk Claes and Adeodato Simó (2009–2010)
  • Adam D. Barratt and Neil McGovern (2010–2013)<ref>


  • Adam D. Barratt and Niels Thykier (2013–present)<ref>

    team changes, auto-rm and arch status}}</ref>

Note that this list includes the active release managers; it does not include the release assistants (first introduced in 2003) and the retiring managers (“release wizards”).<ref name=“releasemanagers” />

Developer recruitment, motivation, and resignation

The Debian project has a steady influx of applicants wishing to become developers. These applicants must undergo an elaborate vetting process which establishes their identity, motivation, understanding of the project's goals (embodied in the Social Contract), and technical competence.<ref>


Debian Developers join the Project for a number of reasons; some that have been cited in the past include:<ref>


  • A desire to contribute back to the free-software community (practically all applicants are users of free software)
  • A desire to see some specific software task accomplished (some view the Debian user community as a valuable testing or proving ground for new software)
  • A desire to make, or keep, free software competitive with proprietary alternatives
  • A desire to work closely with people who share some of their aptitudes, interests, and goals (there is a very strong sense of community within the Debian project which some applicants do not experience in their paid jobs)
  • A simple enjoyment of the iterative process of software development and maintenance

Debian Developers may resign their positions at any time by orphaning the packages they were responsible for and sending a notice to the developers and the keyring maintainer (so that their upload authorization can be revoked).

Development procedures

Software packages in development are either uploaded to the project distribution named unstable (also known as sid), or to the experimental repository. Software packages uploaded to unstable are normally versions stable enough to be released by the original upstream developer, but with the added Debian-specific packaging and other modifications introduced by Debian developers. These additions may be new and untested. Software not ready yet for the unstable distribution is typically placed in the experimental repository.<ref name=“ftparchive”>


After a version of a software package has remained in unstable for a certain length of time (depending on the urgency of the software's changes), that package is automatically migrated to the testing distribution. The package's migration to testing occurs only if no serious (release-critical) bugs in the package are reported and if other software needed for package functionality qualifies for inclusion in testing.<ref name=“ftparchive” />

Since updates to Debian software packages between official releases do not contain new features, some choose to use the testing and unstable distributions for their newer packages. However, these distributions are less tested than stable, and unstable does not receive timely security updates. In particular, incautious upgrades to working unstable packages can sometimes seriously break software functionality.<ref name=“securityfaq”>

</ref> Since September 9, 2005<ref>

</ref> the testing distribution's security updates have been provided by the testing security team.<ref>


After the packages in testing have matured and the goals for the next release are met, the testing distribution becomes the next stable release. The timing of the release is decided by the Release Managers, and in the past the exact date was rarely announced earlier than a couple of weeks beforehand.<ref name=“Simó”>


Package maintenance

File:Debian package cycle.svg

Each Debian software package has a maintainer who keeps track of releases by the “upstream” authors of the software and ensures that the package is compliant with Debian Policy, coheres with the rest of the distribution, and meets the standards of quality of Debian. In relations with users and other developers, the maintainer uses the bug tracking system to follow up on bug reports and fix bugs. Typically, there is only one maintainer for a single package, but, increasingly, small teams of developers “co-maintain” larger and more complex packages and groups of packages.<ref>


Periodically, a package maintainer makes a release of a package by uploading it to the “incoming” directory of the Debian package archive (or an “upload queue” which periodically batch-transmits packages to the incoming directory). Package uploads are automatically processed to ensure that they are well-formed (all the requisite files are in place) and that the package is digitally signed by a Debian developer using OpenPGP-compatible software. All Debian developers have individual cryptographic key pairs.<ref>

</ref> Packages are signed to be able to reject uploads from hostile outsiders to the project, and to permit accountability in the event that a package contains a serious bug, a violation of policy, or malicious code.

If the package in incoming is found to be validly signed and well-formed, it is installed into the archive into an area called the “pool” and distributed every day to hundreds of mirrors worldwide. Initially, all package uploads accepted into the archive are only available in the “unstable” suite of packages, which contains the most up-to-date version of each package.

However, new code is also untried code, and those packages are only distributed with clear disclaimers. For packages to become candidates for the next “stable” release of the Debian distribution, they first need to be included in the “testing” suite. For a package to be included in testing:<ref>



  • It must have been in unstable for the appropriate length of time (the exact duration depends on the “urgency” of the upload)
  • It must not have a greater number of “release-critical” bugs filed against it than the current version in testing. Release-critical bugs are those bugs which are considered serious enough that they make the package unsuitable for release.
  • It must be compiled for all release architectures the package claims to support (e.g.: the i386-specific package gmod can be included in “testing”)
  • All of its dependencies must either be satisfiable by packages already in testing, or be satisfiable by the group of packages which are going to be installed at the same time.
  • The operation of installing the package into testing must not break any packages currently in testing.

Thus, a release-critical bug in a package on which many packages depend, such as a shared library, may prevent many packages from entering the testing area, because that library is considered deficient.

Periodically, the Release Manager publishes guidelines to the developers in order to ready the release, and in accordance with them eventually decides to make a release. This occurs when all important software is reasonably up-to-date in the release-candidate suite for all architectures for which a release is planned, and when any other goals set by the Release Manager have been met. At that time, all packages in the release-candidate suite (“testing”) become part of the released suite (“stable”).

It is possible for a package, particularly an old, stable, and seldom-updated one, to belong to more than one suite at the same time. The suites are simply collections of pointers into the package “pool” mentioned above.

Debian Security Announcement (DSA)

The Debian Project, being free software, handles security policy through public disclosure rather than through security through obscurity. Many advisories are coordinated with other free software vendors (Debian is a member of vendor-sec) and are published the same day a vulnerability is made public. Debian has a security audit team that reviews the archive looking for new or unfixed security bugs. Debian also participates in security standardization efforts: the Debian security advisories are compatible with the Common Vulnerabilities and Exposures (CVE) dictionary, and Debian is represented in the Board of the Open Vulnerability and Assessment Language (OVAL) project.<ref>


The Debian Project offers extensive documentation and tools to harden a Debian installation both manually and automatically.<ref>

</ref> SELinux (Security-Enhanced Linux) packages are installed by default though not enabled.<ref name=lennynew>

</ref> Debian provides an optional hardening wrapper but does not compile their packages by default using gcc features such as PIE and buffer overflow protection to harden their software, unlike Ubuntu, Fedora and Hardened Gentoo among others.<ref>

</ref> These extra features greatly increase security at a performance cost of 1% in 32-bit and 0.01% in 64-bit.<ref>


It is a release goal for Debian 7.0 (wheezy) “to update as many packages as possible to use security hardening build flags via dpkg-buildflags. These flags enable various protections against security issues such as stack smashing, predictable locations of values in memory, etc.”<ref name=“Debian_Release_Goal”>Release Goal Security Hardening Build Flags</ref>




, the latest stable release is version 7, code name wheezy. When a new version is released, the prior stable version becomes oldstable.

, this is version 6.0, code name squeeze.

In addition, a stable release gets minor updates (called point releases). The numbering scheme for the point releases up to Debian 4.0 was to include the letter r (for release) after the main version number (e.g. 4.0) and then the number of the point release; for example, the latest point release of version 4.0 (etch) as of 8 December 2010 is 4.0r9.<ref>

</ref> From Debian 5.0 (lenny), the numbering scheme of point releases has been changed and conforms to the GNU version numbering standard; so, for example, the first point release of Debian 5.0 was 5.0.1 (instead of 5.0r1).<ref>

</ref> The numbering scheme was once again changed for the first Debian 7 update, with the latter being assigned version 7.1.<ref>


Security updates

The Debian security team releases security updates for the latest stable major release, and for the prior stable release for one year.<ref name=“securityfaq” /> Version 4.0 etch was released on 8 April 2007, and the security team supported version 3.1 Sarge until 21 March 2008. For most uses it is strongly recommended to run a system which receives security updates. The testing distribution also receives security updates, but not in as timely a manner as stable.<ref>


Time-based development schedule

For Debian 6.0 (squeeze) a new policy of time-based development freezes on a two-year cycle was announced. Time-based freezes are intended to allow the Debian Project to blend the predictability of time based releases with its policy of feature based releases. The new freeze policy aims to provide better predictability of releases for users of the Debian distribution, and to allow Debian developers to do better long-term planning. Debian developers expect that a two-year release cycle will give more time for disruptive changes, reducing inconveniences caused for users. Having predictable freezes was expected to reduce overall freeze time. The squeeze cycle was intended to be especially short to “get into the new cycle”.<ref name=“two-year-cycle”>

</ref> However this short freeze cycle for squeeze was abandoned.<ref name=“two-year-cycle-2”>


Debian release code names

The code names of Debian releases are names of characters from the film Toy Story. The unstable, development distribution is permanently nicknamed sid, after the emotionally unstable next-door neighbor boy who regularly destroyed toys.<ref name=“ftparchive” /> The current release wheezy is named after the rubber toy penguin in Toy Story 2.<ref name=“wheezy-codename-devel-announcement”>

</ref> The release after wheezy will be named jessie, after the cowgirl in Toy Story 2 and Toy Story 3.<ref name=“jessie-codename-devel-announcement”>



Debian has made twelve major stable releases (TBA stands for to be announced):<ref name=“releases” />

Version Code&nbsp;name Release date Ports Packages Supported until Notes


1 474




, ELF transition, Linux&nbsp;2.0<ref name=“releases” />



1 848



1 974



2 ≈&nbsp;1,500

glibc transition, new architecture:


<ref name=“releases” />


4 ≈&nbsp;2,250


, new architectures:




<ref name=“releases” />


6 ≈&nbsp;3,900

New architectures:




<ref name=“22rel”>



11 ≈&nbsp;8,500

New architectures:










<ref name=“releases” />


11 ≈&nbsp;15,400

<ref name=“securityfaq” />

Modular installer, semi-official




11 ≈&nbsp;18,000

}}<ref name=“”>


New architecture:


, dropped architecture:


.<ref name=“40rel”>

</ref> Graphical installer, udev transition, modular X.Org transition. Final update 4.0r9 was released 2010-05-22.<ref>






<ref name=“Simó”/>}}

12 ≈&nbsp;23,000<ref name=“lenny released” />



New architecture/binary ABI:



</ref> SPARC 32-bit hardware support dropped.<ref>

</ref> Full Eee PC support.<ref>

</ref> Final update 5.0.10 was released 2012-03-10.<ref>


<ref name=“squeezenotes”>




<ref name=“squeeze released” />


≈&nbsp;29,000<ref name=“squeeze released” />

New architectures/kernels:




, dropped architectures:




, OABI<ref name=“”></ref>


.<ref name=“squeeze released”/> eglibc instead of glibc.<ref>

</ref> Dependency-based boot sequence, which allows for parallel init script processing.<ref>

</ref> Remove old libraries such as GTK&nbsp;1.<ref>

</ref> Default Linux kernel purged of non-free firmware.<ref name=“free kernel”/>

<ref name=“wheezynotes”>


wheezy<ref name=“wheezy-codename-devel-announcement”/>

<ref name=“”>



≈&nbsp;37,000<ref name=“”/>

New architectures:



Debian Wiki | |date=2012-08-20}}</ref>



</ref> Remove old libraries such as Qt&nbsp;3.<ref>

</ref> Introduce multiarch support.<ref>


<ref name=“jessie-codename-devel-announcement”/>

jessie<ref name=“jessie-codename-devel-announcement”/> TBA TBA TBA



9 architectures with Linux kernel + 2 architectures with kernel of FreeBSD<ref name=“squeeze released” /> :

11 architectures with Linux kernel + 2 architectures with kernel of FreeBSD

Due to an incident involving a CD vendor who made an unofficial and broken release labeled 1.0, an official 1.0 release was never made.<ref name=“releases” />


Debian was first announced on 16 August 1993 by Ian Murdock, who initially called the system “the Debian Linux Release”.<ref>


</ref> The word “Debian” was formed as a combination of the first name of his then-girlfriend Debra Lynn and his own first name.<ref>

</ref> Prior to Debian's release, the Softlanding Linux System (SLS) had been the first Linux distribution compiled from various software packages, and was a popular basis for other distributions in 1993-1994.<ref name=“grassroots”>

</ref> The perceived poor maintenance and prevalence of bugs in SLS motivated Murdock to launch a new distribution.<ref>


In 1993 Murdock also released the Debian Manifesto, outlining his view for the new operating system.<ref>

</ref> In it he called for the creation of a distribution to be maintained in an open manner, in the spirit of Linux and GNU.

The Debian Project grew slowly at first and released the first 0.9x versions in 1994 and 1995. During this time it was sponsored by the Free Software Foundation's GNU Project.<ref>

</ref> The first ports to other, non-i386 architectures began in 1995, and the first 1.x version of Debian was released in 1996.

In 1996, Bruce Perens replaced Ian Murdock as the project leader. Perens decided to create a social contract for Debian to guarantee the future freedom of the system's contents. He created a first draft, and edited suggestions from a month-long discussion on the Debian mailing lists into the Debian Social Contract and the Debian Free Software Guidelines, defining fundamental commitments for the development of the distribution. He also initiated the creation of the legal umbrella organization, Software in the Public Interest.<ref name=“releases” /> Perens developed the project from 40 to 200 developers. He broke apart the “base system”, the core packages of Debian, which had been maintained by Murdock alone, and distributed them to many maintainers. He led the conversion of the project from a.out to ELF. He created the BusyBox program to make it possible to run a Debian installer on a single floppy, and wrote a new installer. Perens was also responsible for many policy and design elements of Debian that persist to this day. Perens left the project in 1998.


The Project elected new leaders and made two more 2.x releases, each including more ports and packages. The Advanced Packaging Tool was deployed during this time and the first port to a non-Linux kernel, Debian GNU/Hurd, was started. The first Linux distributions based on Debian, namely Libranet, Corel Linux and Stormix's Storm Linux, were started in 1999.<ref name=“releases” /> The 2.2 release in 2000 was dedicated to Joel Klecker, a developer who died of Duchenne muscular dystrophy.<ref name=“espy”>


In late 2000, the project made major changes to archive and release management, reorganizing software archive processes with new “package pools” and creating a testing distribution as an ongoing, relatively stable staging area for the next release. In the same year, developers began holding an annual conference called DebConf with talks and workshops for developers and technical users.<ref name=“releases” />

In July 2002, the Project released version 3.0, codenamed woody, a stable release which would see relatively few updates until the following release.<ref name=“releases” />


The 3.1 sarge release was made in June 2005. There were many major changes in this release, mostly due to the long time it took to freeze and release the distribution. Not only did this release update over 73% of the software shipped in the prior version, but it also included much more software than prior releases, almost doubling in size with over 9,000 new packages.<ref name=sargenew>

</ref> A new installer replaced the aging boot-floppies installer with a modular design. This allowed advanced installations (with RAID, XFS and LVM support) including hardware detection, making installations easier for novice users. The installation system also boasted full internationalization support as the software was translated into almost forty languages. An installation manual and comprehensive release notes were released in ten and fifteen different languages respectively. This release included the efforts of the Debian-Edu/Skolelinux, Debian-Med and Debian-Accessibility sub-projects which raised the number of packages that were educational, had a medical affiliation, and ones made for people with disabilities.<ref name=“releases” />

In 2006, as a result of a much-publicized dispute, Mozilla software was rebranded in Debian, with Firefox becoming Iceweasel, Thunderbird becoming Icedove, along with other Mozilla programs. The Mozilla Corporation stated that Debian may not use the Firefox trademark if it distributes Firefox with modifications which have not been approved by the Mozilla Corporation. Two prominent reasons that Debian modifies the Firefox software are to change the artwork and to provide security patches. Debian Free Software Guidelines consider Mozilla's artwork non-free. Debian provides long term support for older versions of Firefox in the stable release, where Mozilla preferred that old versions not be supported but has since included Legacy versions of programs. These software programs developed largely by the Mozilla Corporation were rebranded despite having only minor differences in the source code.<ref>


Debian 4.0 (etch) was released April 8, 2007 for the same number of architectures as in sarge. It included the AMD64 port but dropped support for m68k. The m68k port was, however, still available in the unstable distribution. There were approximately 18,200 binary packages maintained by more than 1,030 Debian developers.<ref name=“releases” />

Debian 5.0 (lenny) was released February 14, 2009 after 22 months of development. It includes more than 25,000 software packages. Support was added for Marvell's Orion platform and for netbooks such as the Asus Eee PC, but support was dropped for 32-bit SPARC machines.<ref name=“lenny released”>

</ref> The release was dedicated to Thiemo Seufer, an active developer and member of the community who died in a car accident on December 26, 2008.<ref name=“thiemo”>


On September 5, 2010, Debian officially acquired the backports service, which provides more recent versions of some software for the stable release of Debian.<ref name=“DBP”>


Debian 6.0 (squeeze) was released February 6, 2011 after 24 months of development. For the first time, Debian GNU/kFreeBSD was introduced with this version as a technology preview.<ref name=“squeeze released”>


Debian 7.0 (wheezy) was released May 4, 2013 after 26 months of development. This release attempted to allow more architectures to be supported.<ref name=“wheezy released”>



Debian won the 2007 poll on Server Distribution of the Year by<ref>


Both the Debian distribution and their website have won various awards from different organizations. Debian was awarded the 2004 Readers' Choice Award for Favorite Linux Distribution by the Linux Journal.<ref>

</ref> A total of fifteen other awards have been awarded throughout Debian's lifetime including Best Linux Distribution.<ref>


Debian has also received negative assessments. In May 2008, a Debian Developer revealed his discovery that changes made in 2006 to the random number generator in the version of the OpenSSL package distributed with Debian and other Debian-based distributions such as Ubuntu or Knoppix, made a variety of security keys vulnerable to a random number generator attack.<ref>


</ref> The security weakness was caused by changes made to the OpenSSL code by another Debian Developer in response to memory debugger warnings.<ref>

</ref> The security hole was soon patched by Debian and others, but the complete resolution procedure was cumbersome for users because it involved regenerating all affected keys, and it drew criticism to Debian's practice of making Debian-specific changes to software.

Richard Stallman and the Free Software Foundation (FSF) have criticized the Debian Project for providing the non-free repository, rather than excluding this type of software entirely,<ref name=“fsf”>

</ref> an opinion also echoed by some in Debian including the then-Project Leader Wichert Akkerman.<ref>

</ref> The internal dissent in the Debian Project regarding the non-free section has persisted, but the last time it came to a vote in 2006, a large majority decided to keep it.<ref name=“nonfreeremovalvote”>


During the release cycles of Woody and Sarge, the Debian Project drew considerable criticism from the free software community because of the long time between stable releases.

See also


Further reading

debian.txt · Last modified: 2020/03/12 18:40 (external edit)