Jump to content

Debian: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
→‎Releases: Updated "as of". 4.0r9 is the last 4.0 release.
→‎Time-based development schedule: Trimmed some historical details.
Line 336: Line 336:


==== Time-based development schedule ====
==== 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">{{cite web |url = http://www.debian.org/News/2009/20090729 |title = Debian decides to adopt time-based release freezes |publisher = Debian |accessdate = 2009-09-12 |date = 2009-07-29}}</ref> However this short freeze cycle for squeeze was abandoned.<ref name="two-year-cycle-2">{{cite web |url = http://www.debian.org/News/2009/20090730 |title = Debian GNU/Linux 6.0 "Squeeze" release goals |publisher = Debian |accessdate = 2009-12-01 |date = 2009-07-30}}</ref>
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. 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">{{cite web |url = http://www.debian.org/News/2009/20090729 |title = Debian decides to adopt time-based release freezes |publisher = Debian |accessdate = 2009-09-12 |date = 2009-07-29}}</ref> However this short freeze cycle for squeeze was abandoned.<ref name="two-year-cycle-2">{{cite web |url = http://www.debian.org/News/2009/20090730 |title = Debian GNU/Linux 6.0 "Squeeze" release goals |publisher = Debian |accessdate = 2009-12-01 |date = 2009-07-30}}</ref>


==== Debian release code names ====
==== Debian release code names ====

Revision as of 02:52, 5 June 2014

Debian
Debian 7.0 (Wheezy) with GNOME 3
DeveloperDebian Project
OS familyUnix-like
Working stateCurrent
Source modelOpen-source
Initial releaseAugust 16, 1993; 31 years ago (1993-08-16)
Latest release11.5 (Bullseye)[1] (September 10, 2022; 23 months ago (2022-09-10)) [±]
Repository
Available in73 languages[2]
Update methodAPT (several front-ends available)
Package managerdpkg
PlatformsIA-32, x86-64, PowerPC, SPARC, ARM, MIPS, S390
Kernel typeMonolithic: Linux, kFreeBSD (unstable: Micro: Hurd)
UserlandGNU
Default
user interface		GNOME
LicenseFree software (mainly GPL).[3] Proprietary software in a separate (non-default) repository.[4]
Official websitewww.debian.org

Debian (/ˈdɛbiən/) is an operating system composed of Free Software mostly carrying the GNU General Public License.[5] The operating system is developed by an Internet collaboration of volunteers aligned with The Debian Project.

Debian GNU/Linux is one of the most popular Linux distributions for personal computers and network servers.[6][7][8][9] Debian has been used as a base for other Linux distributions; as of 2014, DistroWatch lists 138 active Debian derivatives.[10][11] Debian has been forked many times but is not affiliated with its derivatives.

In addition to releasing security updates, the Debian project is committed to providing accurate information about security issues. Debian Security Advisories are CVE-Compatible.[12]

Features

Text version of the Debian Installer
Graphical version of the Debian Installer (available since Etch)
Debian GNU/Linux console login and welcome message

Debian 6.0 introduced a new kernel: the Debian GNU/kFreeBSD kernel. Debian now supports two kernels, Linux and kFreeBSD, and offers other kernels under development (GNU Hurd and NetBSD). This project's new kernel is released as a technology preview and still lacks the amount of software available as on Debian's Linux.[13] The kernel is offered for Intel/AMD 32-bit and 64-bit architecture machines.[14] The current stable release, code-named Wheezy, is officially supported on eleven architectures and also brought support for two new architectures: s390x and armhf.

Debian is still primarily a Linux distribution with access to online repositories hosting over 37,500 software packages.[15] Debian officially hosts free software on its repositories but also allows non-free software to be installed. Debian includes popular programs such as LibreOffice,[16] 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.[17] Ohloh estimates that the codebase (68 million lines of code) using the same model, would cost about US$ 1.2 billion to develop.[18]

Debian offers DVD and CD images for installation that can be downloaded using BitTorrent, with jigdo and bought from retailers.[19] The sets are made up of several disks (the amd64 port consists of 10 DVDs or 69 CDs),[20] but using just the first iso image of any of its downloadable sets is sufficient;[21] the installer can retrieve software not contained in the first iso image from online repositories. Installation images are hybrid on some architectures and can be used to create a bootable USB stick.[22] The Wheezy release offers to install a variety of default Desktops from its DVD boot menu (GNOME, KDE, Xfce, and LXDE) and includes aids for visually-impaired people. 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.[23] Debian offers different network installation methods. 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. Another option is to boot the installer from the network.[24]

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;[25] UEFI support for amd64;[26] 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.[27]

Desktop environments

Debian KDE desktop

Debian offers stable and testing CD images specifically built for GNOME (the default), KDE Plasma Workspaces, Xfce and LXDE.[28] Less common window managers such as Enlightenment, Openbox, Fluxbox, IceWM, Window Maker and others are also available.[29]

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.[30] 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.[31][32] 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.[33][34] Debian makes images of its install disk 1 available with Xfce as the included environment.[35]

As of March 2014, MATE is available in the testing and unstable repositories,[36] while Cinnamon is only available in the unstable repository.[37]

Blends

A Debian Pure Blend is a subset of Debian that is configured out-of-the-box for users with particular skills and interests.[38]

A 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.[39]

Debian Live

Debian also releases live install images for CDs, DVDs and USB thumb drives, for IA-32 and x86-64 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. A full install of Debian to the computer's hard drive can be initiated from the live image environment.[40]

Personalized Debian Live images can be built with the live-build tool,[41] in which images are generated for CD/DVD/USB drives and for network booting purposes. Live-magic is another tool used for personalizing Debian Live images, along with the assistance of a graphical interface.

Debian version 5.0 "Lenny" was the first official Live CD release.[42]

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[43] and can be upgraded to Debian 6.0 although there are problems with a 6.0 clean install.[44] Debian 5.0 added support for the Buffalo Kurobox Pro,[45] and Debian 6.0 for the SheevaPlug.[46]

Other NAS devices supported by Debian, but perhaps not so widely used by home users, include GLAN Tank and Thecus N2100 as of Debian 4.0,[47] QNAP Turbo Station (TS-109, TS-209, TS-409) and HP mv2120 as of Debian 5.0,[45] and QNAP Turbo NAS TS-11x, TS-21x and TS-41x, OpenRD, Lanner EM7210 and Intel SS4000-e as of Debian 6.0.[46]

Packages

Debian package
The GNOME icon for deb files
Filename extension
.deb
Internet media type
application/x-deb
Developed byDebian
Type of formatPackage management system
Container forSoftware package
Extended fromar archive

Package management

Package management operations can be performed with different tools available on Debian, from the lowest level command dpkg to graphical front-ends like synaptic. The official standard for administering packages on a Debian system is the apt toolset.[48]

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.[49] The command can work with local .deb package files as well as information from the dpkg database.

APT tools for online repositories
Using Aptitude to view Debian package details
Package installed with Aptitude.

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. The program comes with enhancements such as better search on package metadata. 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. "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 tool 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.

Repositories

A Debian 4.0 "Etch" Box Cover[50]

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.[51] Debian also officially supports the optional backports repository for the stable distribution.[52]

Official

When in need of updated versions of software, it is possible to use Debian testing instead of stable as it usually contains more up to date, 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".[53]

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.[54] Stable's CDs and DVDs can be found in the Debian website.[51]
  • 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, contains software being tested for inclusion in the next major release. The packages included in this distribution have had some testing in unstable but they may not be completely fit for release yet. It contains newer 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.[51]
  • 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 run bleeding-edge software, so it will not be as stable as the other distributions. Debian does not support official sid installation CDs/DVDs because the repository is rapidly changing, although CD and DVD images of sid are built quarterly by aptosid. Additionally, the other distributions can be set to draw software from unstable the next time the system is upgraded.[51]

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.[55]
  • 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 is 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 should not even be referenced by advanced users.[56]

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.[57][58] 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).[51]
  • 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.[51]
Third-party repositories

These repositories are not part of the Debian Project, they are maintained by third party organizations. They contain packages that are either more up to date 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.[59]

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.[60]

Linux, and therefore Debian, supports the use of multiple processors in a system (symmetric multiprocessing). This does not inhibit support for single-processor systems.[60]

Debian's recommended system requirements differ depending on the level of installation, which corresponds to increased numbers of installed components:[61]

Install desktop RAM minimum[61] RAM recommended[61] Hard drive space used[61]
No 64 MB 256 MB 1 GB
Yes 128 MB 512 MB 5 GB

A 1 GHz processor is the minimum recommended for desktop systems.[61]

The real minimum memory requirements depend on the architecture and may be much less than the numbers listed in this table. It is possible to install Debian with as little as 20 MB of RAM for s390, or 60 MB of RAM for x86-64.[61] The installer will run in low memory mode and it is recommended to create a swap partition.[62] Similarly, disk space requirements, which depend on the packages to be installed, can also be reduced by manually selecting the packages needed.[61]

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.[61] Requirements for individual software vary widely and must be considered as well as those of the base operating environment.[61]

Architecture ports

HP 9000 C110 PA-RISC workstation booting Debian GNU/Linux

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 (wheezy), the official ports are:[63]

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 http://www.debian-ports.org:

  • 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 x86-64 processors, incompatible with IA-32

The m68k 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 arm (OABI,[66] <armv4t), alpha and hppa ports were dropped before the release of squeeze.

Policies

Debian is known for its manifesto,[67] social contract,[7][67][68] and policies.[69] Debian's policies and team efforts focus on collaborative software development and testing processes[70] 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. 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.

Organization

Diagram of the organizational structure of the project

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.[71]
  • 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.[71]
  • 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.[72]

Debian is developed by over three thousand volunteers.[73] There are many ways a volunteer can contribute to the project without being a Debian Developer.[74]

Debian is supported by donations through several nonprofit organizations around the world. The largest supporter is Software in the Public Interest,[75] the owner of the Debian trademark, manager of the monetary donations[76] and umbrella organization for various other community free software projects.[77]

The project maintains official mailing lists and conferences for communication and coordination between developers.[78] For issues with single packages and other tasks,[79] a public bug tracking system is used by developers and end-users. Internet Relay Chat channels (primarily on the OFTC and freenode networks) are also used for communication among developers[51] and to provide real time help.[80]

Together, the Developers may make binding general decisions by way of a General Resolution or election.[72] All voting is conducted by Cloneproof Schwartz Sequential Dropping, a Condorcet method of voting.[81] A Project Leader is elected once per year by a vote of the Developers;[72] in April 2010, Stefano Zacchiroli was voted into this position, succeeding Steve McIntyre. The Debian Project Leader has several special powers, but they are not absolute. 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.[72]

The Leader sometimes delegates authority to other developers in order for them to perform specialized tasks. Delegates make decisions as they think is best, taking into account technical criteria and consensus.[72]

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.[82][83]

Project leaders

The Debian Project Leader (DPL) is the public face of the project and defines the current direction of the project.[84] The project has had the following leaders:[85]

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.[87]

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)[88]
  • Adam D. Barratt and Niels Thykier (2013–present)[89]

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").[82]

Developer recruitment, motivation, and resignation

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

Debian Developers join the Project for a number of reasons; some that have been cited in the past include:[92]

  • 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). Alternatively, when necessary, existing developers can be expelled.[72]

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.[93]

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".[93]

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.[94] Since September 9, 2005[95] the "testing" distribution's security updates have been provided by the "testing" security team.[96]

When "testing" is deemed mature enough and the number of remaining bugs is acceptable, the "testing" distribution becomes the next stable release.[56] 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.[97]

Package maintenance

Flowchart of the life cycle of a Debian package

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.[98]

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.[99] Developers are responsible for any package they upload even if the packaging was prepared by another contributor.[100]

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" distribution, which contains the most up-to-date version of each package.[51]

For packages to become candidates for the next "stable" release of the Debian distribution, they first need to be included in the "testing" distribution. For a package to be included in "testing":[101][102]

  • It must have been in "unstable" for the appropriate length of time (the exact duration depends on the urgency of the changes)
  • 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 new version of a shared library on which many packages depend may prevent those packages from entering "testing", because the updated library must meet the requirements too.

Periodically, the release team publishes guidelines to the developers in order to ready the release. A new release occurs when all important software is reasonably up-to-date in the release-candidate distribution, and when any other significant issues are solved. At that time, all packages in the "testing" distribution become the new "stable" distribution.[51]

A version of a package can belong to more than one distribution, usually "testing" and "unstable". It is possible for a package to keep the same version between stable releases and be part of "oldstable", "stable", "testing" and "unstable" at the same time.[103] Each distribution, also called suite, can be seen as a collection of pointers into the package "pool" mentioned above.[51]

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 and are published the same day a vulnerability is made public.[104] Debian has a security audit team that focuses on packages in the stable release looking for new or unfixed security bugs.[105] The Debian security advisories are compatible with the Common Vulnerabilities and Exposures (CVE) dictionary.[106]

The Debian Project offers documentation and tools to harden a Debian installation both manually and automatically.[107] SELinux (Security-Enhanced Linux) packages are installed by default though not enabled.[108] Debian provides an optional hardening wrapper and does not compile their packages by default using gcc features such as PIE and buffer overflow protection to harden their software, unlike Ubuntu,[109] Fedora and Hardened Gentoo among others, but tries to build as many packages as possible with hardening flags.[27] These extra features increase security at a performance cost of 1% in IA-32 and 0.01% in x86-64.[110]

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.[111][112] The security weakness was caused by changes made to the OpenSSL code by another Debian Developer in response to memory debugger warnings.[113] 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,[114] and it drew criticism to Debian's practice of making Debian-specific changes to software.

History

Releases

As of June 2014, the 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) is 4.0r9.[115] From Debian 5.0 (lenny), the numbering scheme of point releases has been changed and conforms to the GNU version numbering standard;[116] so, for example, the first point release of Debian 5.0 was 5.0.1 (instead of 5.0r1).[117] The numbering scheme was once again changed for the first Debian 7 update, with the latter being assigned version 7.1.[118]

Security updates

The Debian security team releases security updates for the latest stable major release, and for the prior stable release for one year.[94] 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.[119]

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. 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".[54] However this short freeze cycle for squeeze was abandoned.[120]

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.[93] The current release wheezy is named after the rubber toy penguin in Toy Story 2.[121] The release after wheezy will be named jessie, after the cowgirl in Toy Story 2 and Toy Story 3.[122]

Timeline

Debian has made twelve major stable releases (TBA stands for to be announced):[75]

Version Code name Release date Ports Packages Supported until Notes
Old version, no longer maintained: 1.1 buzz 17 June 1996 1 474 Old version, no longer maintained: September 1996[123] dpkg, ELF transition, Linux 2.0[75]
Old version, no longer maintained: 1.2 rex 12 December 1996 1 848 Old version, no longer maintained: 1996[citation needed] -
Old version, no longer maintained: 1.3 bo 5 June 1997 1 974 Old version, no longer maintained: 1997[citation needed] -
Old version, no longer maintained: 2.0 hamm 24 July 1998 2 ≈ 1,500 Old version, no longer maintained: 1998 glibc transition, new architecture: m68k[75]
Old version, no longer maintained: 2.1 slink 9 March 1999 4 ≈ 2,250 Old version, no longer maintained: December 2000 APT, new architectures: alpha, sparc[75]
Old version, no longer maintained: 2.2 potato 15 August 2000 6 ≈ 3,900 Old version, no longer maintained: April 2003 New architectures: arm, powerpc[124]
Old version, no longer maintained: 3.0 woody 19 July 2002 11 ≈ 8,500 Old version, no longer maintained: August 2006 New architectures: hppa, ia64, mips, mipsel, s390[75]
Old version, no longer maintained: 3.1 sarge 6 June 2005 11 ≈ 15,400 Old version, no longer maintained: April 2008[94] Modular installer, semi-official amd64 support.
Old version, no longer maintained: 4.0 etch 8 April 2007 11 ≈ 18,000 Old version, no longer maintained: 15 February 2010[125] New architecture: amd64, dropped architecture: m68k.[126] Graphical installer, udev transition, modular X.Org transition. Final update 4.0r9 was released 2010-05-22.[127]
Old version, no longer maintained: 5.0[128] lenny[129] 15 February 2009[97] 12 ≈ 23,000[130] Old version, no longer maintained: 6 February 2012[131] New architecture/binary ABI: armel.[132] SPARC 32-bit hardware support dropped.[133] Full Eee PC support.[134] Final update 5.0.10 was released 2012-03-10.[135]
Older version, yet still maintained: 6.0[136] squeeze[137] 6 February 2011[138] 9+2[A] ≈ 29,000[138] Older version, yet still maintained: Standard: 31 May 2014 LTS: February 2016[139] New architectures/kernels: kfreebsd-i386 and kfreebsd-amd64. Dropped architectures: alpha, hppa, and OABI arm.[66][138] Moved to eglibc instead of glibc.[140] Dependency-based boot sequence, which allows for parallel init script processing.[141] Removed old libraries such as GTK 1.[142] Default Linux kernel purged of non-free firmware.[73]
Current stable version: 7[143] wheezy[121] 4 May 2013[144] 11+2[B] ≈ 37,000[144] Current stable version: TBA New architectures: armhf­[145] and s390x.[146] Removed old libraries such as Qt 3.[147] Introduced multiarch support.[148]
Future release: 8[122] jessie[122] TBA TBA TBA Future release: TBA We will freeze "Jessie" at 23:59 UTC on the 5th of November 2014; TBA
Legend:
Old version
Older version, still maintained
Latest version
Latest preview version
Future release
A 9 architectures with Linux kernel + 2 architectures with kernel of FreeBSD[138]
B 11 architectures with Linux kernel + 2 architectures with kernel of FreeBSD

Unable to compile EasyTimeline input:

EasyTimeline 1.90


Timeline generation failed: More than 10 errors found
Line 143: from:10/06/2023 till:05/06/2014

- Plotdata attribute 'from' invalid.

 Date '10/06/2023' not within range as specified by command Period.



Line 144: at:10/06/2023 shift:(0,10) text:"Bookworm 12"

- Plotdata attribute 'at' invalid.

 Date '10/06/2023' not within range as specified by command Period.



Line 145: at:10/06/2023 align:right text:".0"

- Plotdata attribute 'at' invalid.

 Date '10/06/2023' not within range as specified by command Period.



Line 148: from:10/06/2023 till:05/06/2014

- Plotdata attribute 'from' invalid.

 Date '10/06/2023' not within range as specified by command Period.



Line 153: from:14/08/2021 till:05/06/2014

- Plotdata attribute 'from' invalid.

 Date '14/08/2021' not within range as specified by command Period.



Line 154: at:14/08/2021 shift:(0,10) text:"Bullseye 11"

- Plotdata attribute 'at' invalid.

 Date '14/08/2021' not within range as specified by command Period.



Line 155: at:14/08/2021 align:right text:".0"

- Plotdata attribute 'at' invalid.

 Date '14/08/2021' not within range as specified by command Period.



Line 158: from:09/10/2021 till:18/12/2021

- Plotdata attribute 'till' invalid.

 Date '18/12/2021' not within range as specified by command Period.



Line 161: from:18/12/2021 till:26/03/2022

- Plotdata attribute 'till' invalid.

 Date '26/03/2022' not within range as specified by command Period.



Line 164: from:26/03/2022 till:09/07/2022

- Plotdata attribute 'till' invalid.

 Date '09/07/2022' not within range as specified by command Period.



Line 167: from:09/07/2022 till:10/09/2022

- Plotdata attribute 'till' invalid.

 Date '10/09/2022' not within range as specified by command Period.



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.[75]

1993–1998

Debian was first announced on 16 August 1993 by Ian Murdock, who initially called the system "the Debian Linux Release".[149][150] The word "Debian" was formed as a combination of the first name of his then-girlfriend Debra Lynn and his own first name.[151] 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.[152] The perceived poor maintenance and prevalence of bugs in SLS motivated Murdock to launch a new distribution.[153]

In 1993 Murdock also released the Debian Manifesto, outlining his view for the new operating system.[154] 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.[155] The first ports to other, non-IA-32 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.[75] 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.

1999–2004

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.[75] The 2.2 release in 2000 was dedicated to Joel Klecker, a developer who died of Duchenne muscular dystrophy.[156]

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.[75]

In July 2002, the Project released version 3.0, codenamed woody, a stable release which would see relatively few updates until the following release.[75]

2005–present

Debian 4.0 "Etch" (2007)

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.[157] 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.[75]

In 2006, as a result of a much-publicized dispute, Mozilla software was rebranded in Debian, with Firefox becoming Iceweasel and Thunderbird becoming Icedove. 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.[158]

Debian 4.0 (etch) was released April 8, 2007 for the same number of architectures as in sarge. It included the x86-64 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.[75]

Debian 6.0 "Squeeze" (2011)

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.[130] 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.[159]

On September 5, 2010, Debian officially acquired the backports service, which provides more recent versions of some software for the stable release of Debian.[160]

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.[138]

Debian 7.0 (wheezy) was released May 4, 2013 after 26 months of development. This release attempted to allow more architectures to be supported.[161]

Reception

Debian won the 2007 poll on Server Distribution of the Year by LinuxQuestions.org.[162]

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.[163] A total of fifteen other awards have been awarded throughout Debian's lifetime including Best Linux Distribution.[164]

Debian has also received negative assessments. 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,[165] an opinion also echoed by some in Debian including the then-Project Leader Wichert Akkerman.[166] 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.[167]

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

References

  1. ^ "Updated Debian 11: 11.5 released". Debian News. Debian. September 10, 2022. Retrieved September 10, 2022.
  2. ^ "Debian Installer 7.0 RC3 release". Debian. May 2, 2013. Retrieved May 2, 2013.
  3. ^ "License information". Debian. Retrieved February 28, 2009.
  4. ^ "Debian - Packages". Debian. See non-free repository
  5. ^ "What Does Free Mean? or What do you mean by Free Software?". official Debian site. Debian. Retrieved December 1, 2009.
  6. ^ Katherine Noyes (January 11, 2012). "Debian Linux Named Most Popular Distro for Web Servers". PC World. Retrieved February 14, 2013.
  7. ^ a b Joe Brockmeier (February 7, 2011). "Why Debian matters more than ever". Network World. Retrieved May 30, 2014.
  8. ^ Steven J. Vaughan-Nichols (December 16, 2009). "The Five Distros That Changed Linux". Linux Magazine. Retrieved February 14, 2013.
  9. ^ "Usage Statistics and Market Share of Linux for Websites, October 2012". W3Techs.com. Retrieved October 13, 2012.
  10. ^ "Based on Debian, status active". Distrowatch. Retrieved May 25, 2014.
  11. ^ "Debian Derivatives". Debian Wiki.
  12. ^ "Debian and CVE compatibility". Debian. Retrieved April 16, 2013.
  13. ^ "Debian GNU/kFreeBSD". Debian. April 30, 2014. Retrieved May 26, 2014.
  14. ^ "Release Notes for Debian 7.0 (wheezy), 64-bit PC". Debian. Retrieved June 10, 2013.
  15. ^ "Debian". Debian. Retrieved May 11, 2013.
  16. ^ "Debian Moves to LibreOffice". Debian. Retrieved March 5, 2012.
  17. ^ "Measuring Lenny: the size of Debian 5.0" (PDF). libresoft. Retrieved May 25, 2014.
  18. ^ "Debian GNU/Linux". Ohloh.net. Retrieved July 3, 2013.
  19. ^ "Debian on CDs". Debian. May 10, 2014. Retrieved May 27, 2014.
  20. ^ "Downloading Debian CD images with jigdo". Debian. May 10, 2014. Retrieved May 26, 2014.
  21. ^ "Downloading Debian CD/DVD images via HTTP/FTP". Debian. May 17, 2014. Retrieved May 26, 2014.
  22. ^ "4.3. Preparing Files for USB Memory Stick Booting". Debian. Retrieved May 27, 2014.
  23. ^ "5.2. Accessibility". Debian. Retrieved May 26, 2014.
  24. ^ "Installing Debian GNU/Linux via the Internet". Debian. Retrieved December 11, 2008.
  25. ^ "Multiarch, The Case For Multiarch". Debian Wiki. Retrieved June 11, 2013.
  26. ^ Katherine Noyes (May 7, 2013). "Five things to like About Debian 7.0 'Wheezy'". PC World. Retrieved May 27, 2014.
  27. ^ a b "Chapter 2. What's new in Debian 7.0". Debian. Retrieved May 27, 2014.
  28. ^ "Debian GNU/Linux 4.0 released". Debian. April 8, 2008. Retrieved October 31, 2008.
  29. ^ "Virtual Package: x-window-manager". Debian. Retrieved May 27, 2014.
  30. ^ Michael Larabel (August 8, 2012). "Debian Now Defaults To Xfce Desktop". Phoronix Media. Retrieved August 27, 2012.
  31. ^ "Debian Installer 7.0 Beta3 release". Debian.
  32. ^ "Re: CD1 without a network mirror isn't sufficient to install a full desktop environment". Debian.
  33. ^ "Git - tasksel/tasksel.git/commitdiff". Debian. November 3, 2013. Retrieved March 25, 2014.
  34. ^ "Debian 8.0 "Jessie" Ditches GNOME and Adopts Xfce". News.softpedia.com. Retrieved March 25, 2014.
  35. ^ "Debian Linux 7.0 Wheezy: Hands on". For the CD images, it is useful to know that Debian supports a number of different desktops, including Gnome, KDE, Xfce and LXDE, and there is a different "disk 1" image for each of these desktops.
  36. ^ "Debian - Package Search Results - mate-desktop". Debian. Retrieved March 25, 2014.
  37. ^ "Debian - Package Search Results - cinnamon". Debian. Retrieved March 25, 2014.
  38. ^ "Chapter 2. What are Debian Pure Blends?". Debian. June 19, 2013. Retrieved May 27, 2014.
  39. ^ "Debian Pure Blends". Debian Wiki. May 2, 2013. Retrieved December 7, 2013.
  40. ^ "Live install images". Debian. October 27, 2013. Retrieved December 7, 2013.
  41. ^ "DebianLive/ live-build: Debian Wiki". Debian. Retrieved August 15, 2011.
  42. ^ "Debian Live Lenny Beta1". Debian.
  43. ^ "Upgrading your Slug LG #161". Linuxgazette.net. Retrieved July 27, 2011.
  44. ^ "Installing Debian on NSLU2". Cyrius.com. February 24, 2011. Retrieved July 27, 2011.
  45. ^ a b "Chapter 2. What's new in Debian GNU/Linux 5.0". Debian. Retrieved July 27, 2011.
  46. ^ a b "Chapter 2. What's new in Debian GNU/Linux 6.0". Debian. Retrieved July 27, 2011.
  47. ^ "What's new in Debian GNU/Linux 4.0". Release Notes for Debian GNU/Linux 4.0 ("etch"), ARM. Debian. August 16, 2007. Retrieved July 27, 2011.
  48. ^ "Chapter 2. Debian package management". Debian Reference. Debian. December 3, 2013. Retrieved May 29, 2014.
  49. ^ "Debian Wiki dpkg". Debian Wiki. Retrieved December 10, 2008.
  50. ^ "Artwork for Debian CDs". Debian. Retrieved January 11, 2009.
  51. ^ a b c d e f g h i j "Chapter 4. Resources for Debian Developers". Debian. Retrieved October 31, 2008.
  52. ^ "Backports service becoming official". Debian.
  53. ^ "Debian Backports". Debian. Retrieved August 19, 2012.
  54. ^ a b "Debian decides to adopt time-based release freezes". Debian. July 29, 2009. Retrieved September 12, 2009.
  55. ^ "Chapter 3 - Choosing a Debian distribution". Debian. Retrieved June 3, 2013.
  56. ^ a b "Chapter 6 - The Debian FTP archives". Debian. Retrieved June 3, 2013.
  57. ^ "Explaining Why We Don't Endorse Other Systems". www.gnu.org. Retrieved April 14, 2013.
  58. ^ "About Debian: It's all free?". Debian. Retrieved April 14, 2013.
  59. ^ "MultimediaCodecs". Debian Wiki. February 20, 2014. Retrieved May 29, 2014.
  60. ^ a b "2.1. Supported Hardware Chapter 2. System Requirements". Debian. Retrieved November 2, 2008.
  61. ^ a b c d e f g h i "3.4. Meeting Minimum Hardware Requirements". Debian. 2013. Retrieved May 30, 2014.
  62. ^ "6.3. Using Individual Components". Debian. 2013. Retrieved May 30, 2014.
  63. ^ "Debian Ports". Debian. Retrieved May 28, 2014.
  64. ^ "Debian Wiki: armhf – Arm Hard Float Port". Debian Wiki.
  65. ^ "Supported Hardware". Debian. Retrieved October 11, 2008.
  66. ^ a b "ArmEabiPort". Debian Wiki.
  67. ^ a b Scott Gilbertson (August 13, 2013). "No distro diva drama here: Penguinista favourite Debian turns 20". The Register. Retrieved May 30, 2014.
  68. ^ Ryan Paul (December 30, 2008). "Why Ubuntu users should care about Debian". Ars Technica. Retrieved May 30, 2014.
  69. ^ Joe Brockmeier (May 19, 2009). "Trademarks: Open Source Friendly (TM)". PC World. Retrieved May 30, 2014.
  70. ^ "The Debian GNU/Linux FAQ: Definitions and overview". Debian. Retrieved May 12, 2008.
  71. ^ a b "Debian Social Contract". Debian. Retrieved June 17, 2013.
  72. ^ a b c d e f "Constitution for the Debian Project (v1.4)". Debian. December 8, 2013. Retrieved February 25, 2014.
  73. ^ a b "Debian 6.0 "Squeeze" to be released with completely free Linux Kernel". Debian. Retrieved December 15, 2010.
  74. ^ "How can you help Debian?". Debian. April 30, 2014. Retrieved June 3, 2014.
  75. ^ a b c d e f g h i j k l m "A Brief History of Debian: Debian Releases". Debian. Retrieved October 31, 2008.
  76. ^ "Donations to Software in the Public Interest". Debian. May 10, 2014. Retrieved June 3, 2014.
  77. ^ "SPI Projects: Welcome to SPI (archived)". www.spi-inc.org. Archived from the original on March 16, 2010. Retrieved May 12, 2008.
  78. ^ "The Debian GNU/Linux FAQ: Getting support for Debian GNU/Linux". Debian. Retrieved May 12, 2008.
  79. ^ "Debian bug tracking system pseudo-packages". Debian. December 8, 2013. Retrieved June 3, 2014.
  80. ^ "Support". Debian. April 30, 2014. Retrieved June 3, 2014.
  81. ^ "Debian Voting Information". Debian. February 18, 2014. Retrieved June 3, 2014.
  82. ^ a b "The Debian organization web page". Debian. Retrieved November 1, 2008.
  83. ^ O'Mahony, Siobhan; Ferraro, Fabrizio (April 2008). "The Emergence of Governance in an Open Source Community" (PDF). ualberta.ca. Archived from the original (PDF) on May 29, 2008. Retrieved November 1, 2008.
  84. ^ "Debian Project Leader". Debian.
  85. ^ "A Brief History of Debian Chapter 2: Leadership". Debian. Retrieved November 1, 2008.
  86. ^ Devotee (April 13, 2013). "Results for Debian Project Leader 2013 Election". Debian.
  87. ^ "DPL Platform – Stefano Zacchiroli". Debian. March 12, 2010. section 2.2.3 No DPL board. 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).
  88. ^ "Bits from the (chilly) release team". Debian.
  89. ^ "Release sprint results – team changes, auto-rm and arch status". Debian.
  90. ^ "Debian New Member - Statistics". Debian. Retrieved June 3, 2014.
  91. ^ "Debian New Maintainers". Debian. Retrieved October 31, 2008.
  92. ^ "How You Can Join". Debian. Retrieved October 31, 2008.
  93. ^ a b c "The Debian GNU/Linux FAQ Chapter 6: The Debian FTP archives". Debian. Retrieved May 24, 2007.
  94. ^ a b c "Debian security FAQ". Debian. February 28, 2007. Retrieved October 21, 2008.
  95. ^ Hess, Joey (September 5, 2005). "announcing the beginning of security support for testing". debian-devel-announce (Mailing list). Debian. Retrieved April 20, 2007. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  96. ^ "Debian testing security team". Debian. Retrieved October 31, 2008.
  97. ^ a b Simó, Adeodato (February 1, 2009). "Release update: deep freeze, planned dates, and remaining bugs". debian-devel-announce@lists.debian.org (Mailing list). Debian. Retrieved February 7, 2009. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  98. ^ "General Resolution: Endorse the concept of Debian Maintainers". Debian. Retrieved December 13, 2008.
  99. ^ "Debian Developer's Reference". Debian. Retrieved October 9, 2010.
  100. ^ "DebianMentorsFaq". Debian Wiki. May 21, 2014. Retrieved June 4, 2014.
  101. ^ "Debian Developer Reference". Debian. Retrieved October 31, 2008.
  102. ^ "Debian "testing" distribution". Debian. Retrieved November 24, 2008.
  103. ^ "Debian -- Package Search Results -- dict-bouvier". Debian. Retrieved June 4, 2014.
  104. ^ "Security Information". Debian. Retrieved December 13, 2008.
  105. ^ "Debian Security Audit Project". Debian. March 15, 2014. Retrieved June 4, 2014.
  106. ^ "Organizations Participating". CVE. April 16, 2014. Retrieved June 5, 2014.
  107. ^ "Securing Debian Manual". Debian. Retrieved December 13, 2008.
  108. ^ "Chapter 2. What's new in Debian GNU/Linux 5.0". Debian. Retrieved February 18, 2009.
  109. ^ "Ubuntu Wiki CompilerFlags". Ubuntu. Retrieved January 31, 2011.
  110. ^ "Debian Secure by Default". Debian: Secure by Default Project. Retrieved January 31, 2011.
  111. ^ "DSA-1571-1 openssl: predictable random number generator". Debian. Retrieved October 31, 2008.
  112. ^ "CVE-2008-0166 (under review)". mitre.org. Retrieved October 31, 2008.
  113. ^ "Debian OpenSSL Security Flaw". cryptogon.com. May 26, 2008. Retrieved October 31, 2008.
  114. ^ "When Private Keys are Public: Results from the 2008 Debian OpenSSL Vulnerability" (PDF). UCSD CSE. 2009.
  115. ^ "Release". Debian. May 22, 2010. Retrieved June 5, 2014.
  116. ^ "GNU Coding Standards: Releases". GNU Project. May 13, 2014. Retrieved May 25, 2014. You should identify each release with a pair of version numbers, a major version and a minor. We have no objection to using more than two numbers, but it is very unlikely that you really need them.
  117. ^ Brockschmidt, Marc (February 15, 2009). "Debian squeeze waiting for development". debian-devel-announce (Mailing list). Debian. Retrieved February 15, 2009. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  118. ^ "Debian wiki on DebianWheezy". Debian Wiki. Retrieved December 17, 2013.
  119. ^ "Debian testing security team". Debian. Retrieved October 31, 2008.
  120. ^ "Debian GNU/Linux 6.0 "Squeeze" release goals". Debian. July 30, 2009. Retrieved December 1, 2009.
  121. ^ a b "Release Update: freeze guidelines, transitions, BSP, rc bug fixes". debian-devel-announce (Mailing list). Debian. September 3, 2010. Retrieved September 3, 2010. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  122. ^ a b c "Bits from the nippy Release Team". debian-devel-announce (Mailing list). Debian. July 27, 2012. Retrieved July 27, 2012. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  123. ^ "date of file packages". DebianTemplate:Inconsistent citations{{cite web}}: CS1 maint: postscript (link)
  124. ^ Schulze, Martin (August 15, 2000). "Debian GNU/Linux 2.2, the "Joel 'Espy' Klecker" release". debian-announce (Mailing list). Debian. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  125. ^ "Debian Wiki: Debian Releases > Debian Etch". Debian. Retrieved February 16, 2010.
  126. ^ Schmehl, Alexander (April 8, 2007). "Debian GNU/Linux 4.0 released". debian-announce (Mailing list). Debian. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  127. ^ "Debian -- News -- Debian GNU/Linux 4.0 updated". Debian. Retrieved March 12, 2012.
  128. ^ Brockschmidt, Marc (March 2, 2008). "Release Update: Release numbering, goals, armel architecture, BSPs". debian-announce (Mailing list). Debian. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  129. ^ Langasek, Steve (November 16, 2006). "testing d-i Release Candidate 1 and more release adjustments". debian-devel-announce (Mailing list). Debian. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  130. ^ a b "Debian GNU/Linux 5.0 released". Debian. February 14, 2009. Retrieved February 15, 2009.
  131. ^ Muehlenhoff, Moritz (December 6, 2011). "[SECURITY] [DSA 2360-1] Two month advance notification for upcoming end-of-life for Debian oldstable". debian-security-announce (Mailing list). Debian. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  132. ^ Brockschmidt, Marc (June 2, 2008). "Release Update: arch status, major transitions finished, freeze coming up". debian-devel-announce (Mailing list). Debian. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  133. ^ Smakov, Jurij (July 18, 2007). "Retiring the sparc32 port". debian-devel-announce (Mailing list). Debian. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  134. ^ Armstrong, Ben (August 3, 2008). "Bits from the Debian Eee PC team, summer 2008". debian-devel-announce (Mailing list). Debian. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  135. ^ "Debian -- News -- Updated Debian 5.0: 5.0.10 released". Debian. March 10, 2012. Retrieved March 12, 2012.
  136. ^ "Debian GNU/Linux 6.0: Release Notes". Debian.
  137. ^ Claes, Luk (September 1, 2008). "Release Update: freeze guidelines, testing, BSP, rc bug fixes". debian-devel-announce (Mailing list). Debian. Retrieved October 31, 2008. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  138. ^ a b c d e "Debian 6.0 "Squeeze" released". Debian. February 6, 2011. Retrieved February 6, 2011.
  139. ^ Muehlenhoff, Moritz (April 16, 2014). "[SECURITY] [DSA 2907-1] Announcement of long term support for Debian oldstable". debian-security-announce (Mailing list). Debian. Retrieved April 16, 2014. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  140. ^ "Aurelien's weblog: Debian is switching to EGLIBC". Aurélien Jarno. Retrieved May 21, 2009.
  141. ^ "LSBInitScripts/DependencyBasedBoot". Debian Wiki. Retrieved July 27, 2011.
  142. ^ "ReleaseGoals/RemoveOldLibs". Debian Wiki. Retrieved July 27, 2011.
  143. ^ "Debian GNU/Linux 7.0: Release Notes". Debian. Retrieved May 4, 2013.
  144. ^ a b "Debian 7.0 Wheezy released". Debian. Retrieved May 5, 2013.
  145. ^ "ArmHardFloatPort – Debian Wiki". Debian Wiki. August 20, 2012.
  146. ^ "Bit from the Release Team: armhf and s390x". Debian. June 7, 2012. Retrieved June 14, 2011.
  147. ^ "Ana's blog » Blog Archive » post and pre-release fun". Ekaia.org. February 7, 2011. Retrieved July 27, 2011.
  148. ^ "Debian 7 Wheezy to introduce multiarch support". Debian. Retrieved July 27, 2011.
  149. ^ "A Brief History of Debian: Introduction: What is the Debian Project?". Debian. Retrieved May 12, 2008.
  150. ^ Ian A Murdock (August 16, 1993). "New release under development; suggestions requested". Newsgroup: comp.os.linux.development. CBusDD.MIK@unix.portal.com. Retrieved June 13, 2012.
  151. ^ Nixon, Robin (2010). Ubuntu: Up and Running. O'Reilly Media. p. 3. ISBN 978-0-596-80484-8.
  152. ^ Hillesley, Richard (November 2, 2007). "Debian and the grass roots of Linux". Retrieved May 25, 2014.
  153. ^ Murdock, Ian A (August 16, 1993). "NNTP Subject: New release under development; suggestions requested". Newsgroup: comp.oslinux.development. CBusDD.MIK@unix.portal.com. Retrieved August 17, 2007.
  154. ^ "Appendix A: The Debian Manifesto". Debian. Retrieved August 13, 2008.
  155. ^ "What is the Debian Project?". A Brief History of Debian. Debian. Retrieved July 27, 2011.
  156. ^ "Debian GNU/Linux 2.2, the "Joel 'Espy' Klecker" release, is officially released". Debian. August 15, 2000. Retrieved July 27, 2011.
  157. ^ "Chapter 2 - What's new in Debian GNU/Linux 3.1". Debian. Retrieved August 5, 2010.
  158. ^ Hoover, Lisa (October 10, 2006). "Behind the Debian and Mozilla dispute over use of Firefox". linux.com. Retrieved February 9, 2009.
  159. ^ "Appendix C. Lenny dedicated to Thiemo Seufer". Debian. February 14, 2009. Retrieved May 25, 2014.
  160. ^ "Debian -- News -- Backports service becoming official". Debian. Retrieved September 13, 2010.
  161. ^ "Debian 7.0 "Wheezy" released". Debian. May 4, 2013. Retrieved May 5, 2013.
  162. ^ "2007 LinuxQuestions.org Members Choice Awards". LinuxQuestions.org. Retrieved November 2, 2008.
  163. ^ "2004 Readers' Choice Awards". linuxjournal.com. November 1, 2004. Retrieved November 2, 2008.
  164. ^ "Awards". Debian. Retrieved November 2, 2008.
  165. ^ "Explaining Why We Don't Endorse Other Systems". Free Software Foundation. Retrieved September 28, 2009.
  166. ^ "Moving contrib and non-free [out] of master.debian.org". debian-devel (Mailing list). Debian. June 21, 1999. {{cite mailing list}}: |first= missing |last= (help); Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  167. ^ "General Resolution: Status of the non-free section". Debian. Retrieved September 28, 2009.

Further reading

Template:MATE Template:Xfce Template:LXDE

Template:Link FA

Retrieved from "https://en.wikipedia.org/w/index.php?title=Debian&oldid=611620149"