# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2013-06-02 01:15+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. type: definition of entity &debian;
#, no-wrap
msgid "Debian GNU/Linux"
msgstr ""

#. type: definition of entity &release;
#, no-wrap
msgid "7.0"
msgstr ""

#. type: definition of entity &releasename;
#, no-wrap
msgid "wheezy"
msgstr ""

#. type: definition of entity &oldreleasename;
#, no-wrap
msgid "squeeze"
msgstr ""

#. type: definition of entity &testingreleasename;
#, no-wrap
msgid "jessie"
msgstr ""

#. type: definition of entity &developers;
#, no-wrap
msgid "990"
msgstr ""

#. type: definition of entity &all-pkgs;
#, no-wrap
msgid "37400"
msgstr ""

#. type: definition of entity &main-pkgs;
#, no-wrap
msgid "28200"
msgstr ""

#. type: definition of entity &contrib-nonfree-pkgs;
#, no-wrap
msgid "187"
msgstr ""

#. type: definition of entity &archs;
#, no-wrap
msgid "10"
msgstr ""

#. type: definition of entity &debian-donation;
#, no-wrap
msgid "http://www.debian.org/donations"
msgstr ""

#. type: definition of entity &docdate;
#, no-wrap
msgid "2 June 2013"
msgstr ""

#. type: definition of entity &docversion;
#, no-wrap
msgid "5.0.2"
msgstr ""

#. type: <title></title>
#: debian-faq.sgml:11
msgid "The &debian; FAQ"
msgstr ""

#. type: <author></author>
#: debian-faq.sgml:12
msgid ""
"<name>Authors are listed at <qref id=\"authors\">Debian FAQ Authors</qref></"
"name>"
msgstr ""

#. type: <version></version>
#: debian-faq.sgml:13
msgid "version &docversion;, &docdate;"
msgstr ""

#. type: <abstract></abstract>
#: debian-faq.sgml:14
msgid "This document answers questions frequently asked about &debian;."
msgstr ""

#. type: <copyrightsummary></copyrightsummary>
#: debian-faq.sgml:19
msgid ""
"Copyright &copy; 1996-2013 by Software in the Public Interest, portions "
"copyright &copy; 2004, 2005, 2006 Kamaraju Kusumanchi"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:25
msgid ""
"Permission is granted to make and distribute verbatim copies of this "
"document provided the copyright notice and this permission notice are "
"preserved on all copies."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:30
msgid ""
"Permission is granted to copy and distribute modified versions of this "
"document under the conditions for verbatim copying, provided that the entire "
"resulting derived work is distributed under the terms of a permission notice "
"identical to this one."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:35
msgid ""
"Permission is granted to copy and distribute translations of this document "
"into another language, under the above conditions for modified versions, "
"except that this permission notice may be included in translations approved "
"by the Free Software Foundation instead of in the original English."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:42 basic_defs.sgml:5
msgid "Definitions and overview"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:42 basic_defs.sgml:7
msgid "What is this FAQ?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:15
msgid ""
"This document gives frequently asked questions (with their answers!) about "
"the Debian distribution (&debian; and others) and about the Debian project. "
"If applicable, pointers to other documentation will be given: we won't quote "
"large parts of external documentation in this document. You'll find out that "
"some answers assume some knowledge of Unix-like operating systems. We'll try "
"to assume as little prior knowledge as possible: answers to general "
"beginners questions will be kept simple."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:19
msgid ""
"If you can't find what you're looking for in this FAQ, be sure to check out "
"<ref id=\"debiandocs\">. If even that doesn't help, refer to <ref id="
"\"feedback\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:42 basic_defs.sgml:21
msgid "What is &debian;?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:24
msgid ""
"&debian; is a particular <em>distribution</em> of the Linux operating "
"system, and numerous packages that run on it."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:42 basic_defs.sgml:25
msgid "&debian; is:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:32
msgid ""
"<strong>full featured</strong>: Debian includes more than &all-pkgs; "
"software packages at present. Users can select which packages to install; "
"Debian provides a tool for this purpose. You can find a list and "
"descriptions of the packages currently available in Debian at any of the "
"Debian <url id=\"http://www.debian.org/distrib/ftplist\" name=\"mirror sites"
"\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:38
msgid ""
"<strong>free to use and redistribute</strong>: There is no consortium "
"membership or payment required to participate in its distribution and "
"development. All packages that are formally part of &debian; are free to "
"redistribute, usually under terms specified by the GNU General Public "
"License."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:42
msgid ""
"The Debian FTP archives also carry approximately &contrib-nonfree-pkgs; "
"software packages (in the <tt>non-free</tt> and <tt>contrib</tt> sections), "
"which are distributable under specific terms included with each package."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:45
msgid ""
"<strong>dynamic</strong>: With about &developers; volunteers constantly "
"contributing new and improved code, Debian is evolving rapidly. The FTP "
"archives are updated twice every day."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:60
msgid ""
"Most Linux users run a specific <em>distribution</em> of Linux, like "
"&debian;. However, in principle, users could obtain the Linux kernel via the "
"Internet or from elsewhere, and compile it themselves. They could then "
"obtain source code for many applications in the same way, compile the "
"programs, then install them into their systems. For complicated programs, "
"this process can be not only time-consuming but error-prone. To avoid it, "
"users often choose to obtain the operating system and the application "
"packages from one of the Linux distributors. What distinguishes the various "
"Linux distributors are the software, protocols, and practices they use for "
"packaging, installing, and tracking applications packages on users' systems, "
"combined with installation and maintenance tools, documentation, and other "
"services."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:66
msgid ""
"&debian; is the result of a volunteer effort to create a free, high-quality "
"Unix-compatible operating system, complete with a suite of applications. The "
"idea of a free Unix-like system originates from the GNU project, and many of "
"the applications that make &debian; so useful were developed by the GNU "
"project."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:74
msgid ""
"For Debian, free has the GNUish meaning (see the <url id=\"http://www.debian."
"org/social_contract#guidelines\" name=\"Debian Free Software Guidelines\">). "
"When we speak of free software, we are referring to freedom, not price. Free "
"software means that you have the freedom to distribute copies of free "
"software, that you receive source code or can get it if you want it, that "
"you can change the software or use pieces of it in new free programs; and "
"that you know you can do these things."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:78
msgid ""
"The Debian Project was created by Ian Murdock in 1993, initially under the "
"sponsorship of the Free Software Foundation's GNU project. Today, Debian's "
"developers think of it as a direct descendent of the GNU project."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:85
msgid ""
"Although &debian; itself is free software, it is a base upon which value-"
"added Linux distributions can be built. By providing a reliable, full-"
"featured base system, Debian provides Linux users with increased "
"compatibility, and allows Linux distribution creators to eliminate "
"duplication of effort and focus on the things that make their distribution "
"special. See <ref id=\"childistro\"> for more information."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:42 basic_defs.sgml:87
msgid "OK, now I know what Debian is... what is Linux?!"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:92
msgid ""
"In short, Linux is the kernel of a Unix-like operating system. It was "
"originally designed for 386 (and better) PCs; today Linux also runs on a "
"dozen of other systems. Linux is written by Linus Torvalds and many computer "
"scientists around the world."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:42 basic_defs.sgml:93
msgid "Besides its kernel, a \"Linux\" system usually has:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:95
msgid ""
"a file system that follows the Linux Filesystem Hierarchy Standard <url id="
"\"http://www.pathname.com/fhs/\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:98
msgid ""
"a wide range of Unix utilities, many of which have been developed by the GNU "
"project and the Free Software Foundation."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:104
msgid ""
"The combination of the Linux kernel, the file system, the GNU and FSF "
"utilities, and the other utilities are designed to achieve compliance with "
"the POSIX (IEEE 1003.1) standard; see <ref id=\"otherunices\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:107
msgid ""
"For more information about Linux, see <url id=\"http://www.linux.org/info/\" "
"name=\"What is Linux\"> by <url id=\"http://www.linux.org/\" name=\"Linux "
"Online\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:42 basic_defs.sgml:109
msgid "Does Debian just do GNU/Linux?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:114
msgid ""
"Currently, Debian is only available for Linux, but with Debian GNU/Hurd and "
"Debian on BSD kernels, we have started to offer non-Linux-based OSes as a "
"development, server and desktop platform, too. However, these non-linux "
"ports are not officially released yet."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:116
msgid "The oldest porting effort is Debian GNU/Hurd."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:119
msgid ""
"The Hurd is a set of servers running on top of the GNU Mach microkernel. "
"Together they build the base for the GNU operating system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:123
msgid ""
"Please see <url id=\"http://www.gnu.org/software/hurd/\"> for more "
"information about the GNU/Hurd in general, and <url id=\"http://www.debian."
"org/ports/hurd/\"> for more information about Debian GNU/Hurd."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:126
msgid ""
"A second effort is the port to a BSD kernel. People are working with both "
"the NetBSD and the FreeBSD kernels."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:129
msgid ""
"See <url id=\"http://www.debian.org/ports/#nonlinux\"> for more information "
"about these non-linux ports."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:42 basic_defs.sgml:133
msgid ""
"What is the difference between &debian; and other Linux distributions? Why "
"should I choose Debian over some other distribution?"
msgstr ""

#. type: <p><taglist>
#: debian-faq.sgml:42 basic_defs.sgml:135
msgid "These key features distinguish Debian from other Linux distributions:"
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:42 basic_defs.sgml:137
msgid "Freedom:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:146
msgid ""
"As stated in the <url id=\"http://www.debian.org/social_contract\" name="
"\"Debian Social Contract\">, Debian will remain 100% free. Debian is very "
"strict about shipping truly free software. The guidelines used to determine "
"if a work is \"free\" are provided in <url id=\"http://www.debian.org/"
"social_contract#guidelines\" name=\"The Debian Free Software\">."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:42 basic_defs.sgml:146
msgid "The Debian package maintenance system:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:156
msgid ""
"The entire system, or any individual component of it, can be upgraded in "
"place without reformatting, without losing custom configuration files, and "
"(in most cases) without rebooting the system. Most Linux distributions "
"available today have some kind of package maintenance system; the Debian "
"package maintenance system is unique and particularly robust (see <ref id="
"\"pkg_basics\">)."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:42 basic_defs.sgml:156
msgid "Open development:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:161
msgid ""
"Whereas other Linux distributions are developed by individuals, small, "
"closed groups, or commercial vendors, Debian is the only major Linux "
"distribution that is being developed cooperatively by many individuals "
"through the Internet, in the same spirit as Linux and other free software."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:170
msgid ""
"More than &developers; volunteer package maintainers are working on over "
"&all-pkgs; packages and improving &debian;. The Debian developers contribute "
"to the project not by writing new applications (in most cases), but by "
"packaging existing software according to the standards of the project, by "
"communicating bug reports to upstream developers, and by providing user "
"support. See also additional information on how to become a contributor in "
"<ref id=\"contrib\">."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:42 basic_defs.sgml:170
msgid "The Universal Operating System:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:179
msgid ""
"Debian comes with <url id=\"http://packages.debian.org/stable/\" name=\"more "
"than &all-pkgs; packages\"> and runs on <url id=\"http://www.debian.org/"
"ports/\" name=\"&archs; architectures\">. This is far more than is available "
"for any other GNU/Linux distribution. See <ref id=\"apps\"> for an overview "
"of the provided software and see <ref id=\"arches\"> for a description of "
"the supported hardware platforms."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:42 basic_defs.sgml:179
msgid "The Bug Tracking System:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:195
msgid ""
"The geographical dispersion of the Debian developers required sophisticated "
"tools and quick communication of bugs and bug-fixes to accelerate the "
"development of the system. Users are encouraged to send bugs in a formal "
"style, which are quickly accessible by WWW archives or via e-mail. See "
"additional information in this FAQ on the management of the bug log in <ref "
"id=\"buglogs\">."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:42 basic_defs.sgml:195
msgid "The Debian Policy:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:199
msgid ""
"Debian has an extensive specification of our standards of quality, the "
"Debian Policy. This document defines the qualities and standards to which we "
"hold Debian packages."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:204
msgid ""
"For additional information about this, please see our web page about <url id="
"\"http://www.debian.org/intro/why_debian\" name=\"reasons to choose Debian"
"\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:42 basic_defs.sgml:207
msgid ""
"How does the Debian project fit in or compare with the Free Software "
"Foundation's GNU project?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:213
msgid ""
"The Debian system builds on the ideals of free software first championed by "
"the <url id=\"http://www.gnu.org/\" name=\"Free Software Foundation\"> and "
"in particular by <url id=\"http://www.stallman.org/\" name=\"Richard Stallman"
"\">. FSF's powerful system development tools, utilities, and applications "
"are also a key part of the Debian system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:218
msgid ""
"The Debian Project is a separate entity from the FSF, however we communicate "
"regularly and cooperate on various projects. The FSF explicitly requested "
"that we call our system \"&debian;\", and we are happy to comply with that "
"request."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:42 basic_defs.sgml:223
msgid ""
"The FSF's long-standing objective is to develop a new operating system "
"called GNU, based on <url id=\"http://www.gnu.org/software/hurd/\" name="
"\"Hurd\">. Debian is working with FSF on this system, called <url id="
"\"http://www.debian.org/ports/hurd/\" name=\"Debian GNU/Hurd\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:42 basic_defs.sgml:226
msgid "How does one pronounce Debian and what does this word mean?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:3
msgid ""
"The project name is pronounced Deb'-ee-en, with a short e in Deb, and "
"emphasis on the first syllable. This word is a contraction of the names of "
"Debra and Ian Murdock, who founded the project. (Dictionaries seem to offer "
"some ambiguity in the pronunciation of Ian (!), but Ian prefers ee'-en.)"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:43 getting.sgml:5
msgid "Getting and installing &debian;"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:10
msgid ""
"The official document giving installation instructions is the <url id="
"\"http://www.debian.org/releases/stable/installmanual\" name=\"Debian GNU/"
"Linux Installation Guide\">. We'll give some additional notes about getting "
"and installing &debian; here."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:43 getting.sgml:12
msgid "What is the latest version of Debian?"
msgstr ""

#. type: <p><taglist>
#: debian-faq.sgml:43 getting.sgml:13
msgid "Currently there are three versions of &debian;:"
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:43 getting.sgml:14
msgid ""
"<em>release &release;, a.k.a. the `stable' distribution or &releasename;</em>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:16
msgid ""
"This is stable and well tested software, it changes if major security or "
"usability fixes are incorporated."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:43 getting.sgml:17
msgid ""
"<em>the `testing' distribution, currently called &testingreleasename;</em>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:21
msgid ""
"This is where packages that will be released as the next `stable' are "
"placed; they've had some testing in unstable but they may not be completely "
"fit for release yet. This distribution is updated more often than `stable', "
"but not more often than `unstable'."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:43 getting.sgml:22
msgid "<em>the `unstable' distribution</em>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:28
msgid ""
"This is the version currently under development; it is updated continuously. "
"You can retrieve packages from the `unstable' archive on any Debian FTP site "
"and use them to upgrade your system at any time, but you may not expect the "
"system to be as usable or as stable as before - that's why it's called "
"`<strong>unstable</strong>'!"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:32
msgid "Please see <ref id=\"dists\"> for more information."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:43 getting.sgml:34
msgid "Are there package upgrades in `stable'?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:39
msgid ""
"No new functionality is added to the stable release. Once a Debian version "
"is released and tagged `stable' it will only get security updates. That is, "
"only packages for which a security vulnerability has been found after the "
"release will be upgraded. All the security updates are served through <url "
"id=\"ftp://security.debian.org\" name=\"security.debian.org\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:47
msgid ""
"Security updates serve one purpose: to supply a fix for a security "
"vulnerability. They are not a method for sneaking additional changes into "
"the stable release without going through normal point release procedure. "
"Consequently, fixes for packages with security issues will not upgrade the "
"software. The Debian Security Team will backport the necessary fixes to the "
"version of the software distributed in `stable' instead."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:54
msgid ""
"For more information related to security support please read the <url id="
"\"http://www.debian.org/security/faq\" name=\"Security FAQ\"> or the <url id="
"\"http://www.debian.org/doc/manuals/securing-debian-howto/\" name=\"Debian "
"Security Manual\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:43 getting.sgml:56
msgid "Where/how can I get the Debian installation disks?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:60
msgid ""
"You can get the installation disks by downloading the appropriate files from "
"one of the <url id=\"http://www.debian.org/mirror/list\" name=\"Debian "
"mirrors\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:63
msgid ""
"Please refer to <url id=\"http://www.debian.org/CD\" name=\"Debian GNU/Linux "
"on CDs\"> for more information about CD (and DVD) images."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:43 getting.sgml:65
msgid "How do I install the Debian from CD-ROMs?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:71
msgid ""
"Installing Debian from CD is straightforward: configure your system for "
"booting off a CD, insert your CD, and reboot. Your system will now be "
"running the Debian Installer. See the <url id=\"http://www.debian.org/"
"releases/stable/installmanual\" name=\"Debian GNU/Linux Installation Guide"
"\"> for more information."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:43 getting.sgml:75
msgid ""
"Why does the official stable released CD-ROM contain symlinks for `frozen' "
"and `unstable'? I thought this CD contains just `stable'!"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:43 getting.sgml:77
msgid "Official Debian CD images indeed contain symlinks like:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:43 getting.sgml:82
#, no-wrap
msgid ""
" /dists/frozen -> &releasename;/\n"
" /dists/stable -> &releasename;/\n"
" /dists/testing -> &releasename;/\n"
" /dists/unstable -> &releasename;/"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:43 getting.sgml:86
msgid "so that they work when your sources.list has an entry like"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:43 getting.sgml:88
#, no-wrap
msgid " deb cdrom:[&lt;name as on cd label&gt;]/ unstable main [...]"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:43 getting.sgml:91
msgid "."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:96
msgid ""
"The fact these symlinks are present does <em>not</em> mean the image is "
"`unstable' or `testing' or anything. Read the CD label in <file>/.disk/info</"
"file> to find out which Debian version it contains. This information is also "
"present in <file>/README.txt</file> on the CD."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:99
msgid ""
"Read <url id=\"http://www.debian.org/releases/\"> to find out what the "
"current `stable' and `testing' releases are."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:43 getting.sgml:102
msgid "Can I get and install Debian directly from a remote Internet site?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:105
msgid ""
"Yes. You can boot the Debian installation system from a set of files you can "
"download from our FTP site and its mirrors."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:109
msgid ""
"You can download a small CD image file, create a bootable CD from it, "
"install the basic system from it and the rest over the network. For more "
"information please see <url id=\"http://www.debian.org/CD/netinst/\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:43 getting.sgml:113
msgid ""
"You can also download even smaller floppy disk image files, create bootable "
"diskettes from them, start the installation procedure and get the rest of "
"Debian over the network."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:43 getting.sgml:116
msgid "Are there any alternative strategies for booting the system installer?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:3
msgid ""
"Yes. Apart from CD or DVD, you can install Debian GNU/Linux by booting from "
"floppy disks, USB memory stick, directly from hard disk, or using TFTP net "
"booting. For installing on multiple computers it's possible to do fully "
"automatic installations. NB: not all methods are supported by all computer "
"architectures. Once the installer has booted, the rest of the system can be "
"downloaded over the network, or installed from local media. See the <url id="
"\"http://www.debian.org/releases/stable/installmanual\" name=\"Debian GNU/"
"Linux Installation Guide\"> for more information."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:5
msgid "Choosing a Debian distribution"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:12
msgid ""
"There are many different Debian distributions. Choosing the proper Debian "
"distribution is an important decision. This section covers some information "
"useful for users that want to make the choice best suited for their system "
"and also answers possible questions that might be arising during the "
"process. It does not deal with \"why you should choose Debian\" but rather "
"\"which distribution of Debian\"."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:14
msgid ""
"For more information on the available distributions read <ref id=\"dists\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:17
msgid "Which Debian distribution (stable/testing/unstable) is better for me?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:20
msgid ""
"The answer is a bit complicated. It really depends on what you intend to do. "
"One solution would be to ask a friend who runs Debian. But that does not "
"mean that you cannot make an independent decision. In fact, you should be "
"able to decide once you complete reading this chapter."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:25
msgid ""
"If security or stability are at all important for you: install stable. "
"period. This is the most preferred way."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:30
msgid ""
"If you are a new user installing to a desktop machine, start with stable. "
"Some of the software is quite old, but it's the least buggy environment to "
"work in. You can easily switch to the more modern unstable once you are a "
"little more confident."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:34
msgid ""
"If you are a desktop user with some experience in Linux and does not mind "
"facing the odd bug now and then, use unstable. It has all the latest and "
"greatest software, and bugs are usually fixed swiftly."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:38
msgid ""
"If you are running a server, especially one that has strong stability "
"requirements or is exposed to the Internet, install stable. This is by far "
"the strongest and safest choice."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:44
msgid ""
"The following questions (hopefully) provide more detail on these choices. "
"After reading this whole FAQ, if you still could not make a decision, stick "
"with the stable distribution."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:49
msgid ""
"You asked me to install stable, but in stable so and so hardware is not "
"detected/working. What should I do?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:53
msgid ""
"Try to search the web using a search engine and see if someone else is able "
"to get it working in stable. Most of the hardware should work fine with "
"stable. But if you have some state-of-the-art, cutting edge hardware, it "
"might not work with stable. If this is the case, you might want to install/"
"upgrade to unstable."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:58
msgid ""
"For laptops, <url id=\"http://www.linux-on-laptops.com/\"> is a very good "
"website to see if someone else is able to get it to work under Linux. The "
"website is not specific to Debian, but is nevertheless a tremendous "
"resource. I am not aware of any such website for desktops."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:68
msgid ""
"Another option would be to ask in the debian-user mailing list by sending an "
"email to debian-user@lists.debian.org . Messages can be posted to the list "
"even without subscribing. The archives can be read through <url id=\"http://"
"lists.debian.org/debian-user/\"> Information regarding subscribing to the "
"list can be found at the location of archives. You are strongly encourage to "
"post your questions on the mailing-list than on <url id=\"http://www.debian."
"org/support\" name=\"irc\">. The mailing-list messages are archived, so "
"solution to your problem can help others with the same issue."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:72
msgid ""
"Will there be different versions of packages in different distributions?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:73
msgid ""
"Yes. Unstable has the most recent (latest) versions. But the packages in "
"unstable are not well tested and might have bugs."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:76
msgid ""
"On the other hand, stable contains old versions of packages. But this "
"package is well tested and is less likely to have any bugs."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:78
msgid "The packages in testing fall between these two extremes."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:82
msgid ""
"The stable distributions really contains outdated packages. Just look at "
"Kde, Gnome, Xorg or even the kernel. They are very old. Why is it so?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:89
msgid ""
"Well, you might be correct. The age of the packages at stable depends on "
"when the last release was made. Since there is typically over 1 year between "
"releases you might find that stable contains old versions of packages. "
"However, they have been tested in and out. One can confidently say that the "
"packages do not have any known severe bugs, security holes etc., in them. "
"The packages in stable integrate seamlessly with other stable packages. "
"These characteristics are very important for production servers which have "
"to work 24 hours a day, 7 days a week."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:95
msgid ""
"On the other hand, packages in testing or unstable can have hidden bugs, "
"security holes etc., Moreover, some packages in testing and unstable might "
"not be working as intended. Usually people working on a single desktop "
"prefer having the latest and most modern set of packages. Unstable is the "
"solution for this group of people."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:99
msgid ""
"As you can see, stability and novelty are two opposing ends of the spectrum. "
"If stability is required: install stable distribution. If you want to work "
"with the latest packages, then install unstable."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:104
msgid "If I were to decide to change to another distribution, Can I do that?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:106
msgid ""
"Yes, but it is a one way process. You can go from stable --&gt; testing --"
"&gt; unstable. But the reverse direction is not \"possible\". So better be "
"sure if you are planning to install/upgrade to unstable."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:114
msgid ""
"Actually, if you are an expert and if you are willing to spend some time and "
"if you are real careful and if you know what you are doing, then it might be "
"possible to go from unstable to testing and then to stable. The installer "
"scripts are not designed to do that. So in the process, your configuration "
"files might be lost and...."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:116
msgid "Could you tell me whether to install testing or unstable?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:119
msgid ""
"This is a rather subjective issue. There is no perfect answer but only a "
"\"wise guess\" could be made while deciding between unstable and testing. My "
"personal order of preference is Stable, Unstable and Testing. The issue is "
"like this:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:125
msgid "Stable is rock solid. It does not break."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:127
msgid ""
"Testing breaks less often than Unstable. But when it breaks, it takes a long "
"time for things to get rectified. Sometimes this could be days and it could "
"be months at times."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:133
msgid ""
"Unstable changes a lot, and it can break at any point. However, fixes get "
"rectified in many occasions in a couple of days and it always has the latest "
"releases of software packaged for Debian."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:141
msgid ""
"But there are times when tracking testing would be beneficial as opposed to "
"unstable. The author such situation due to the gcc transition from gcc3 to "
"gcc4. He was trying to install the <package>labplot</package> package on a "
"machine tracking unstable and it could not be installed in unstable as some "
"of its dependencies have undergone gcc4 transition and some have not. But "
"the package in testing was installable on a testing machine as the gcc4 "
"transitioned packages had not \"trickled down\" to testing."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:147
msgid "You are talking about testing being broken. What do you mean by that?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:150
msgid ""
"Sometimes, a package might not be installable through package management "
"tools. Sometimes, a package might not be available at all, maybe it was "
"(temporarily) removed due to bugs or unmet dependencies. Sometimes, a "
"package installs but does not behave in the proper way."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:153
msgid ""
"When these things happen, the distribution is said to be broken (at least "
"for this package)."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:158
msgid ""
"Why is it that testing could be broken for months? Wont the fixes introduced "
"in unstable flow directly down into testing?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:162
msgid ""
"The bug fixes and improvements introduced in the unstable distribution "
"trickle down to testing after a certain number of days. Let's say this "
"threshold is 10 days. The packages in unstable go into testing only when "
"there are no RC-bugs reported against them. If there is a RC-bug filed "
"against a package in unstable, it will not go into testing after the 10 days."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:168
msgid ""
"The idea is that, if the package has any problems, it would be discovered by "
"people using unstable and will be fixed before it enters testing. This keeps "
"the testing in an usable state for most period of the time. Overall a "
"brilliant concept, if you ask me. But things are alwasy not so simple. "
"Consider the following situation:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:172
msgid "Imagine you are interested in package XYZ."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:174
msgid ""
"Let's assume that on June 10, the version in testing is XYZ-3.6 and in "
"unstable it is XYZ-3.7"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:176
msgid "After 10 days, XYZ-3.7 from unstable migrates into testing."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:178
msgid ""
"So on June 20, both testing and unstable have XYZ-3.7 in their repositories."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:180
msgid ""
"Let's say, The user of testing distribution sees that a new XYZ package is "
"available and updates his XYZ-3.6 to XYZ-3.7"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:183
msgid ""
"Now on June 25, someone using testing or unstable discovers an RC bug in "
"XYZ-3.7 and files it in the BTS."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:188
msgid ""
"The maintainer of XYZ fixes this bug and uploads it to unstable say on June "
"30. Here it is assumed that it takes 5 days for the maintainer to fix the "
"bug and upload the new version. The number 5 should not be taken literally. "
"It could be less or more, depending upon the severity of the RC-bug at hand."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:190
msgid ""
"This new version in unstable, XYZ-3.8 is scheduled to enter testing on July "
"10th."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:192
msgid "But on July 5th some other person, discovers another RC-bug in XYZ-3.8"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:194
msgid ""
"Let's say the maintainer of XYZ fixes this new RC-bug and uploads new "
"version of XYZ after 5 days."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:196
msgid "So on July 10, testing has XYZ-3.7 while unstable has XYZ-3.9"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:198
msgid ""
"This new version XYZ-3.9 is now rescheduled to enter testing on July 20th."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:204
msgid ""
"Now since you are running testing, and since XYZ-3.7 is buggy, you could "
"probably use XYZ only after July 20th. That is you essentially ended up with "
"a broken XYZ for about one month."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:211
msgid ""
"The situation can get much more complicated, if say, XYZ depends on 4 other "
"packages. This could in turn lead to unusable testing distribution for "
"months. The above scenario which is artificially created by me, can occur in "
"the real life. But such occurrences are rare."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:214
msgid ""
"From an administrator's point of view, Which distribution requires more "
"attention?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:222
msgid ""
"One of the main reasons many people chose Debian over other Linux "
"distributions is that it requires very little administration. People want a "
"system that just works. In general one can say that, stable requires very "
"little maintenance while testing and unstable require constant maintenance "
"from the administrator. If you are running stable, all you need to worry "
"about is, keeping track of security updates. If you are running either "
"testing or unstable it is a good idea to be aware of the new bugs discovered "
"in the installed packages, new bugfixes/features introduced etc."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:234
msgid "What happens when a new release is made?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:237
msgid ""
"This question will not help you in choosing a Debian distribution. But "
"sooner or later you will face this question."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:240
msgid ""
"The stable distribution is currently &releasename;; The next stable "
"distribution will be called as &testingreleasename;. Let's consider the "
"particular case as to what happens when &testingreleasename; is released as "
"the new stable version."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:244
msgid ""
"oldstable = &oldreleasename;; stable = &releasename;; testing = "
"&testingreleasename;; unstable = sid"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:246
msgid ""
"Unstable is always referred to as sid irrespective of whether a release is "
"made or not."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:249
msgid ""
"packages constantly migrate from sid to testing (i.e. &testingreleasename;). "
"But packages in stable (i.e. &releasename;) remain the same except for "
"security updates."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:252
msgid ""
"after sometime testing becomes frozen. But it will still be called testing. "
"At this point no new packages from unstable can migrate to testing unless "
"they include release-critical (RC) bug fixes."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:256
msgid ""
"When testing is frozen, all the new bugfixes introduced, have to be manualy "
"checked by the members of the release team. This is done to ensure that "
"there wont be any unknown severe problems in the frozen testing."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:257
msgid "RC bugs in 'frozen testing' are reduced to zero."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:260
msgid ""
"The 'frozen testing' with no rc-bugs will be released as the new stable "
"version. In our example, this new stable release will be called as "
"&testingreleasename;."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:262
msgid ""
"At this stage oldstable = &releasename;, stable = &testingreleasename;. The "
"contents of stable and 'frozen testing' are same at this point."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:263
msgid "A new testing is forked from the current unstable."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:266
msgid ""
"Packages start coming down from sid to testing and the Debian community will "
"be working towards making the next stable release."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:271
msgid ""
"I have a working Desktop/cluster with Debian installed. How do I know which "
"distribution I am running?"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:44 choosing.sgml:274
msgid ""
"In most situations it is very easy to figure this out. Take a look at the "
"<file>/etc/apt/sources.list</file> file. There will be an entry similar to "
"this:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:44 choosing.sgml:276
#, no-wrap
msgid "deb http://ftp.us.debian.org/debian/ unstable main contrib"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:279
msgid ""
"The third field ('unstable' in the above example) indicates the Debian "
"distribution the system is currently tracking."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:44 choosing.sgml:285
msgid ""
"You can also use <prgn>lsb_release</prgn> (available in the <package>lsb-"
"release</package> package). If you run this program in an unstable system "
"you will get:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:44 choosing.sgml:292
#, no-wrap
msgid ""
"$ lsb_release  -a\n"
"LSB Version:    core-2.0-noarch:core-3.0-noarch:core-3.1-noarch:core-2.0-ia32:core-3.0-ia32:core-3.1-ia32\n"
"Distributor ID: Debian\n"
"Description:    Debian GNU/Linux unstable (sid)\n"
"Release:    unstable\n"
"Codename:   sid"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:301
msgid ""
"However, this is always not that easy. Some systems might have <file>sources."
"list</file> files with multiple entries corresponding to different "
"distributions. This could happen if the administrator is tracking different "
"packages from different Debian distributions. This is frequently referred to "
"as apt-pinning. These systems might run a mixture of distributions."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:304
msgid ""
"I am currently tracking stable. Can I change to testing or unstable? If so, "
"How?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:311
msgid ""
"If you are currently running stable, then in the <file>/etc/apt/sources."
"list</file> file the third field will be either &releasename; or stable. You "
"need to change this to the distribution you want to run. If you want to run "
"testing, then change the third field of <file>/etc/apt/sources.list</file> "
"to testing. If you want to run unstable, then change the third field to "
"unstable."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:313
msgid ""
"Currently testing is called &testingreleasename;. So, if you change the "
"third field of <file>/etc/apt/sources.list</file> to &testingreleasename;, "
"then also you will be running testing. But when &testingreleasename; becomes "
"stable, you will still be tracking &testingreleasename;."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:318
msgid ""
"Unstable is always called Sid. So if you change the third field of <file>/"
"etc/apt/sources.list</file> to sid, then you will be tracking unstable."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:323
msgid ""
"Currently Debian offers security updates for testing but not for unstable, "
"as fixes in unstable are directly made to the main archive. So if you are "
"running unstable make sure that you remove the lines relating to security "
"updates in <file>/etc/apt/sources.list</file>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:327
msgid ""
"If there is a release notes document available for the distribution you are "
"upgrading to (even though it has not yet been released) it would be wise to "
"review it, as it might provide information on how you should upgrade to it."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:333
msgid ""
"Nevertheless, once you make the above changes, you can run <file>aptitude "
"update</file> and then install the packages that you want. Notice that "
"installing a package from a different distribution might automatically "
"upgrade half of your system. If you install individual packages you will end "
"up with a system running mixed distributions."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:338
msgid ""
"It might be best in some situations to just fully upgrade to the new "
"distribution running <prgn>apt-get dist-upgrade</prgn>, <prgn>aptitude safe-"
"upgrade</prgn> or <prgn>aptitude full-upgrade</prgn>. Read apt's and "
"aptitude's manual pages for more information."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:342
msgid ""
"I am currently tracking testing (&testingreleasename;). What will happen "
"when a release is made? Will I still be tracking testing or will my machine "
"be running the new stable distribution?"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:44 choosing.sgml:346
msgid ""
"It depends on the entries in the <file>/etc/apt/sources.list</file> file. If "
"you are currently tracking testing, these entries are similar to either:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:44 choosing.sgml:348
#, no-wrap
msgid "deb http://ftp.us.debian.org/debian/ testing main"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:44 choosing.sgml:352
msgid "or"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:44 choosing.sgml:354
#, no-wrap
msgid "deb http://ftp.us.debian.org/debian/ &testingreleasename; main"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:359
msgid ""
"If the third field in <file>/etc/apt/sources.list</file> is 'testing' then "
"you will be tracking testing even after a release is made. So after "
"&testingreleasename; is released, you will be running a new Debian "
"distribution which will have a different codename. Changes might not be "
"apparent at first but will be evident as soon as new packages from unstable "
"go over to the testing distribution."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:363
msgid ""
"But if the third field contains '&testingreleasename;' then you will be "
"tracking stable (since &testingreleasename; will then be the new stable "
"distribution)."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:367
msgid "I am still confused. What did you say I should install?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:367
msgid "If unsure, the best bet would be stable distribution."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:371
msgid "But what about Knoppix, Linex, Ubuntu, and others?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:373
msgid ""
"They are not Debian; they are <em>Debian based</em>. Though there are many "
"similarities and commonalities between them, there are also crucial "
"differences."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:381
msgid ""
"All these distributions have their own merits and are suited to some "
"specific set of users. For more information, read the information of <url id="
"\"http://www.debian.org/misc/children-distros\" name=\"software "
"distributions based on Debian\"> available at the Debian website."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:383
msgid ""
"I know that Knoppix/Linex/Ubuntu/... is Debian-based. So after installing it "
"on the hard disk, can I use 'apt' package tools on it?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:387
msgid ""
"These distributions are Debian based. But they are not Debian. You will be "
"still able to use apt package tools by pointing the <file>/etc/apt/sources."
"list</file> file to these distributions' repositories. But then you are not "
"running Debian, you are running a different distribution. They are not the "
"same."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:396
msgid ""
"In most situations if you stick with one distribution you should use that "
"and not mix packages from other distributions. Many common breakages arise "
"due to people running a distribution and trying to install Debian packages "
"from other distributions. The fact that they use the same formatting and "
"name (.deb) does not make them inmediately compatible."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:402
msgid ""
"For example, Knoppix is a Linux distribution designed to be booted as a live "
"CD where as Debian is designed to be installed on hard-disk. Knoppix is "
"great if you want to know whether a particular hardware works, or if you "
"want to experience how a linux system 'feels' etc., Knoppix is good for "
"demonstration purposes while Debian is designed to run 24/7. Moreover the "
"number of packages available, the number of architectures supported by "
"Debian are far more greater than that of Knoppix."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:408
msgid ""
"If you want Debian, it is best to install Debian from the get-go. Although "
"it is possible to install Debian through other distributions, such as "
"Knoppix, the procedure calls for expertise. If you are reading this FAQ, I "
"would assume that you are new to both Debian and Knoppix. In that case, save "
"yourself a lot of trouble later and install Debian right at the beginning."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:413
msgid ""
"I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. "
"What should I do?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:418
msgid ""
"You are advised not to use the Debian forums (either mailing lists or IRC) "
"for help as people might advise you thinking that you are running a Debian "
"system and the \"fixes\" they provide might not be suited to what you are "
"running. They might even worsen the problem you are facing."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:423
msgid ""
"Use the forums of the specific distribution you are using first. If you do "
"not get help or the help you get does not fix your problem you might want to "
"try asking in Debian forums, but keep the advise of the previous paragraph "
"in mind."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:44 choosing.sgml:425
msgid ""
"I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I "
"migrate?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:44 choosing.sgml:431
msgid ""
"Consider the change from a Debian-based distribution to Debian just like a "
"change from one operating system to another one. You should make a backup of "
"all your data and reinstall the operating system from scratch. You should "
"not attempt to \"upgrade\" to Debian using the package management tools as "
"you might end up with an unusable system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:3
msgid ""
"If all your user data (i.e. your <file>/home</file>) is under a separate "
"partition migrating to Debian is actually quite simple, you just have to "
"tell the installation system to mount (but not reformat) that partition when "
"reinstalling. Making backups of your data, as well as your previous system's "
"configuration (i.e. <file>/etc/</file> and, maybe, <file>/var/</file>) is "
"still encouraged."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:45 compat.sgml:7
msgid "Compatibility issues"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:45 compat.sgml:9
msgid "On what hardware architectures/systems does &debian; run?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:14
msgid ""
"&debian; includes complete source-code for all of the included programs, so "
"it should work on all systems which are supported by the Linux kernel; see "
"the <url id=\"http://en.tldp.org/FAQ/Linux-FAQ/intro.html#DOES-LINUX-RUN-ON-"
"MY-COMPUTER\" name=\"Linux FAQ\"> for details."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:45 compat.sgml:17
msgid ""
"The current &debian; release, &release;, contains a complete, binary "
"distribution for the following architectures:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:22
msgid ""
"<em>amd64</em>: this covers systems based on AMD 64bit CPUs with AMD64 "
"extension and all Intel CPUs with EM64T extension, and a common 64bit "
"userspace."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:24
msgid "<em>armel</em>: little-endian ARM machines."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:26
msgid ""
"<em>armhf</em>: an alternative to armel for ARMv7 machines with hard-float."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:31
msgid ""
"<em>i386</em>: this covers systems based on Intel and compatible processors, "
"including Intel's 386, 486, Pentium, Pentium Pro, Pentium II (both Klamath "
"and Celeron), and Pentium III, and most compatible processors by AMD, Cyrix "
"and others."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:33
msgid "<em>ia64</em>: Intel IA-64 (\"Itanium\") computers."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:36
msgid ""
"<em>mips</em>: SGI's big-endian MIPS systems, Indy and Indigo2; <em>mipsel</"
"em>: little-endian MIPS machines, Digital DECstations."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:40
msgid ""
"<em>powerpc</em>: this covers some IBM/Motorola PowerPC machines, including "
"the Apple Macintosh PowerMac models, and the CHRP and PReP open architecture "
"machines."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:42
msgid "<em>s390</em>: IBM S/390 mainframe systems."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:44
msgid ""
"<em>s390x</em>: 64-bit port for IBM System z machines intended to replace "
"s390."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:47
msgid ""
"<em>sparc</em>: this covers Sun's SPARC and most UltraSPARC systems, and "
"some of their successors in the sun4 architectures"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:57
msgid ""
"The development of binary distributions of Debian for <em>armhf</em> (for "
"ARM boards and devices with a floating-point unit), <em>arv32</em> (for "
"Atmel's 32-bit RISC architecture), <em>m32</em> (for 32-bit RISC "
"microprocessor of Renesas Technology), <em>s390x</em> (for the 64-bit "
"userland for IBM System z mainframes), and <em>sh</em> (for Hitachi SuperH "
"processors) is currently underway."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:64
msgid ""
"Support for the <em>m68k</em> architecture was dropped in the Etch (Debian "
"4.0) release, because it did not meet the criteria set by the Debian Release "
"Managers. This architecture covers Amigas and ATARIs having a Motorola 680x0 "
"processor for x>=2; with MMU. However, the port is still active and "
"available for installation even if not a part of this official stable "
"release and might be reactivated for future releases."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:70
msgid ""
"Support for the <em>hppa</em> (Hewlett-Packard's PA-RISC machines) and "
"<em>alpha</em> (Compaq/Digital's Alpha systems) were dropped in the Squeeze "
"(Debian 6.0) release for similar reasons. The <em>arm</em> was dropped too "
"in this release, as it was superseded by the <em>armel</em> arquitecture."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:73 compat.sgml:113
msgid ""
"For more information on the available ports see the <url id=\"http://www."
"debian.org/ports/\" name=\"ports pages at the website\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:78
msgid ""
"For further information on booting, partitioning your drive, enabling PCMCIA "
"(PC Card) devices and similar issues please follow the instructions given in "
"the Installation Manual, which is available from our WWW site at <url id="
"\"http://www.debian.org/releases/stable/installmanual\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:45 compat.sgml:80
msgid "What kernels does &debian; run?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:45 compat.sgml:83
msgid ""
"Debian provides a complete, binary distribution for the following operating "
"system kernels:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:89
msgid ""
"FreeBSD: provided through the <em>kfreebsd-amd64</em> and <em>kfreebsd-i386</"
"em> ports, for 64-bit PCs and 32-bit PCs respectively. These ports were "
"first released in Debian 6.0 Squeeze as a <em>technology preview</em>."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:45 compat.sgml:94
msgid "In addition to these, work is in progress on the following adaptations:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:98
msgid "<em>avr32</em>, port to Atmel's 32-bit RISC architecture,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:101
msgid ""
"<em>hurd-i386</em> a port for 32-bit PC. This port will use GNU Hurd, the "
"new operating system being put together by the GNU group,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:103
msgid "<em>sh</em>, port to Hitachi SuperH processors."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:109
msgid ""
"There were attempts to port the distribution to the NetBSD kernel, providing "
"<em>netbsd-i386</em> (for 32-bit PCs) and <em>netbsd-alpha</em> (for Alpha "
"machines) but these ports were never released and are currently abandoned."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:45 compat.sgml:116
msgid "How compatible is Debian with other distributions of Linux?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:121
msgid ""
"Debian developers communicate with other Linux distribution creators in an "
"effort to maintain binary compatibility across Linux distributions. Most "
"commercial Linux products run as well under Debian as they do on the system "
"upon which they were built."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:126
msgid ""
"&debian; adheres to the <url id=\"http://www.pathname.com/fhs/\" name="
"\"Linux Filesystem Hierarchy Standard\">. However, there is room for "
"interpretation in some of the rules within this standard, so there may be "
"slight differences between a Debian system and other Linux systems."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:137
msgid ""
"&debian; supports software developed for the <url id=\"http://www.linuxbase."
"org/\" name=\"Linux Standard Base\">. The LSB is a specification for "
"allowing the same binary package to be used on multiple distributions. The "
"Debian Etch release is Certified for LSB Release 3.1, see the <url id="
"\"https://www.linux-foundation.org/lsb-cert/productdir.php\" name=\"Linux "
"Foundation Certification webpage\">. Discussion and coordination of efforts "
"towards ensuring Debian meets the requirements of the Linux Standard Base is "
"taking place on the <url id=\"http://lists.debian.org/debian-lsb/\" name="
"\"debian-lsb mailing list\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:45 compat.sgml:140
msgid "How source code compatible is Debian with other Unix systems?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:149
msgid ""
"For most applications Linux source code is compatible with other Unix "
"systems. It supports almost everything that is available in System V Unix "
"systems and the free and commercial BSD-derived systems. However in the Unix "
"business such claim has nearly no value because there is no way to prove it. "
"In the software development area complete compatibility is required instead "
"of compatibility in \"about most\" cases. So years ago the need for "
"standards arose, and nowadays POSIX.1 (IEEE Standard 1003.1-1990) is one of "
"the major standards for source code compatibility in Unix-like operating "
"systems."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:164
msgid ""
"Linux is intended to adhere to POSIX.1, but the POSIX standards cost real "
"money and the POSIX.1 (and FIPS 151-2) certification is quite expensive; "
"this made it more difficult for the Linux developers to work on complete "
"POSIX conformance. The certification costs make it unlikely that Debian will "
"get an official conformance certification even if it completely passed the "
"validation suite. (The validation suite is now freely available, so it is "
"expected that more people will work on POSIX.1 issues.)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:176
msgid ""
"Unifix GmbH (Braunschweig, Germany) developed a Linux system that has been "
"certified to conform to FIPS 151-2 (a superset of POSIX.1). This technology "
"was available in Unifix' own distribution called Unifix Linux 2.0 and in "
"Lasermoon's Linux-FT."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:45 compat.sgml:180
msgid ""
"Can I use Debian packages (\".deb\" files) on my Red Hat/Slackware/... Linux "
"system? Can I use Red Hat packages (\".rpm\" files) on my &debian; system?"
msgstr ""

#. type: <p><taglist>
#: debian-faq.sgml:45 compat.sgml:183
msgid ""
"Different Linux distributions use different package formats and different "
"package management programs."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:45 compat.sgml:184
msgid "<strong>You probably can:</strong>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:196
msgid ""
"A program to unpack a Debian package onto a Linux host that is been built "
"from a `foreign' distribution is available, and will generally work, in the "
"sense that files will be unpacked. The converse is probably also true, that "
"is, a program to unpack a Red Hat or Slackware package on a host that is "
"based on &debian; will probably succeed in unpacking the package and placing "
"most files in their intended directories. This is largely a consequence of "
"the existence (and broad adherence to) the Linux Filesystem Hierarchy "
"Standard. The <url id=\"http://packages.debian.org/alien\" name=\"Alien\"> "
"package is used to convert between different package formats."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:45 compat.sgml:196
msgid "<strong>You probably do not want to:</strong>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:207
msgid ""
"Most package managers write administrative files when they are used to "
"unpack an archive. These administrative files are generally not "
"standardized. Therefore, the effect of unpacking a Debian package on a "
"`foreign' host will have unpredictable (certainly not useful) effects on the "
"package manager on that system. Likewise, utilities from other distributions "
"might succeed in unpacking their archives on Debian systems, but will "
"probably cause the Debian package management system to fail when the time "
"comes to upgrade or remove some packages, or even simply to report exactly "
"what packages are present on a system."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:45 compat.sgml:207
msgid "<strong>A better way:</strong>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:213
msgid ""
"The Linux File System Standard (and therefore &debian;) requires that "
"subdirectories under <tt>/usr/local/</tt> be entirely under the user's "
"discretion. Therefore, users can unpack `foreign' packages into this "
"directory, and then manage their configuration, upgrade and removal "
"individually."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:45 compat.sgml:221
msgid "How should I install a non-Debian program?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:229
msgid ""
"Files under the directory <tt>/usr/local/</tt> are not under the control of "
"the Debian package management system. Therefore, it is good practice to "
"place the source code for your program in /usr/local/src/. For example, you "
"might extract the files for a package named \"foo.tar\" into the directory "
"<tt>/usr/local/src/foo</tt>. After you compile them, place the binaries in "
"<tt>/usr/local/bin/</tt>, the libraries in <tt>/usr/local/lib/</tt>, and the "
"configuration files in <tt>/usr/local/etc/</tt>."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:45 compat.sgml:233
msgid ""
"If your programs and/or files really must be placed in some other directory, "
"you could still store them in <tt>/usr/local/</tt>, and build the "
"appropriate symbolic links from the required location to its location in "
"<tt>/usr/local/</tt>, e.g., you could make the link"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:45 compat.sgml:229
#, no-wrap
msgid "ln -s /usr/local/bin/foo /usr/bin/foo"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:240
msgid ""
"In any case, if you obtain a package whose copyright allows redistribution, "
"you should consider making a Debian package of it, and uploading it for the "
"Debian system. Guidelines for becoming a package developer are included in "
"the Debian Policy manual (see <ref id=\"debiandocs\">)."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:45 compat.sgml:242
msgid "Why can't I compile programs that require libtermcap?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:248
msgid ""
"Debian uses the <tt>terminfo</tt> database and the <tt>ncurses</tt> library "
"of terminal interface routes, rather than the <tt>termcap</tt> database and "
"the <tt>termcap</tt> library. Users who are compiling programs that require "
"some knowledge of the terminal interface should replace references to "
"<tt>libtermcap</tt> with references to <tt>libncurses</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:255
msgid ""
"To support binaries that have already been linked with the <tt>termcap</tt> "
"library, and for which you do not have the source, Debian provides a package "
"called <package>termcap-compat</package>. This provides both <tt>libtermcap."
"so.2</tt> and <tt>/etc/termcap</tt>. Install this package if the program "
"fails to run with the error message \"can't load library 'libtermcap."
"so.2'\", or complains about a missing <tt>/etc/termcap</tt> file."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:45 compat.sgml:257
msgid "Why can't I install AccelX?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:3
msgid ""
"AccelX uses the <tt>termcap</tt> library for installation. See <ref id="
"\"termcap\"> above."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:5
msgid "Software available in the Debian system"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:8
msgid ""
"What types of applications and development software are available for "
"&debian;?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:46 software.sgml:9
msgid "Like most Linux distributions, &debian; provides:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:12
msgid ""
"the major GNU applications for software development, file manipulation, and "
"text processing, including gcc, g++, make, texinfo, Emacs, the Bash shell "
"and numerous upgraded Unix utilities,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:14
msgid ""
"Perl, Python, Tcl/Tk and various related programs, modules and libraries for "
"each of them,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:15
msgid "TeX (LaTeX) and Lyx, dvips, Ghostscript,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:18
msgid ""
"the Xorg windowing system, which provides a networked graphical user "
"interface for Linux, and countless X applications including the GNOME, KDE "
"and Xfce desktop environments."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:24
msgid ""
"a full suite of networking applications, including servers for Internet "
"protocols such as HTTP (WWW), FTP, NNTP (news), SMTP and POP (mail) and DNS "
"(name servers); relational databases like PostgreSQL, MySQL; also provided "
"are web browsers including the various Mozilla products <footnote><p>These "
"have been, however, rebranded and are provided with different names due to "
"trademark issues</p></footnote>,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:28
msgid ""
"a complete set of office applications, including the OpenOffice.org "
"productivity suite, Gnumeric and other spreadsheets, WYSIWYG editors, "
"calendars."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:37
msgid ""
"More than &main-pkgs; packages, ranging from news servers and readers to "
"sound support, FAX programs, database and spreadsheet programs, image "
"processing programs, communications, net, and mail utilities, Web servers, "
"and even ham-radio programs are included in the distribution. Another "
"&contrib-nonfree-pkgs; software suites are available as Debian packages, but "
"are not formally part of Debian due to license restrictions."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:39
msgid "Who wrote all that software?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:43
msgid ""
"For each package the <em>authors</em> of the program(s) are credited in the "
"file <tt>/usr/share/doc/PACKAGE/copyright</tt>, where PACKAGE is to be "
"substituted with the package's name."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:49
msgid ""
"<em>Maintainers</em> who package this software for the &debian; system are "
"listed in the Debian control file (see <ref id=\"controlfile\">) that comes "
"with each package. The Debian changelog, in <tt>/usr/share/doc/PACKAGE/"
"changelog.Debian.gz</tt>, mentions the people who've worked on the Debian "
"packaging too."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:52
msgid ""
"How can I get a current list of programs that have been packaged for Debian?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:57
msgid ""
"A complete list is available from any of the <url id=\"http://www.debian.org/"
"distrib/ftplist\" name=\"Debian mirrors\">, in the file <tt>indices/"
"Maintainers</tt>. That file includes the package names and the names and e-"
"mails of their respective maintainers."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:61
msgid ""
"The <url id=\"http://packages.debian.org/\" name=\"WWW interface to the "
"Debian packages\"> conveniently summarizes the packages in each of about "
"thirty \"sections\" of the Debian archive."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:63
msgid "How can I install a developer's environment to build packages?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:70
msgid ""
"If you want to build packages in your Debian system you will need to have a "
"basic development environment, including a C/C++ compiler and some other "
"essential packages. In order to install this environment you just need to "
"install the <package>build-essential</package>. This package is a meta-"
"package or place-holder package which depends on the standard development "
"tools one needs to build a Debian package."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:75
msgid ""
"Some software can, however, need additional software to be rebuilt, "
"including library headers or additional tools such as <prgn>autoconf</prgn> "
"or <prgn>gettext</prgn>. Debian provides many of the tools needed to build "
"other software as Debian packages."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:46 software.sgml:83
msgid ""
"Finding which software is precisely required can be tricky, however, unless "
"you are planning on rebuilding Debian packages. This last task is rather "
"easy to do, as official packages have to include a list of the additional "
"software (besides the packages in <package>build-essential</package>) needed "
"to build the pacakge, this is known as <tt>Build-Dependencies</tt>. To "
"install all the packages needed to build a given source package and then "
"build said source package you can just run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:46 software.sgml:86
#, no-wrap
msgid ""
"# apt-get build-dep <var>foo</var>\n"
"# apt-get source --build <var>foo</var>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:92
msgid ""
"Notice that if you want to build the Linux kernels distributed by Debian you "
"will want to install also the <package>kernel-package</package> package. For "
"more information see <ref id=\"customkernel\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:94
msgid "What is missing from &debian;?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:98
msgid ""
"A list of packages which are still needed to be packaged for Debian exists, "
"the <url id=\"http://www.debian.org/devel/wnpp/\" name=\"Work-Needing and "
"Prospective Packages list\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:100
msgid ""
"For more details about adding the missing things, see <ref id=\"contrib\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:104
msgid ""
"Why do I get \"ld: cannot find -lfoo\" messages when compiling programs? Why "
"aren't there any libfoo.so files in Debian library packages?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:109
msgid ""
"Debian Policy requires that such symbolic links (to libfoo.so.x.y.z or "
"similar) are placed in separate, development packages. Those packages are "
"usually named libfoo-dev or libfooX-dev (presuming the library package is "
"named libfooX, and X is a whole number)."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:111
msgid "(How) Does Debian support Java?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:115
msgid ""
"Several <em>free</em> implementations of Java technology are available as "
"Debian packages, providing both Java Development Kits as well as Runtime "
"Environments. You can write, debug and run Java programs using Debian."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:120
msgid ""
"Running a Java applet requires a web browser with the capability to "
"recognize and execute them. Several web browsers available in Debian, such "
"as Mozilla or Konqueror, support Java plug-ins that enable running Java "
"applets within them."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:124
msgid ""
"Please refer to the <url id=\"http://www.debian.org/doc/manuals/debian-java-"
"faq/\" name=\"Debian Java FAQ\"> for more information."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:127
msgid ""
"How can I check that I am using a Debian system, and what version is it?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:133
msgid ""
"In order to make sure that your system has been installed from the real "
"Debian base disks check for the existence of <tt>/etc/debian_version</tt> "
"file, which contains a single one-line entry giving the version number of "
"the release, as defined by the package <tt>base-files</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:138
msgid ""
"The existence of the program <tt>dpkg</tt> shows that you should be able to "
"install Debian packages on your system, but as the program has been ported "
"to many other operating systems and architectures, this is no longer a "
"reliable method of determining is a system &debian;."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:46 software.sgml:143
msgid ""
"Users should be aware, however, that the Debian system consists of many "
"parts, each of which can be updated (almost) independently. Each Debian "
"\"release\" contains well defined and unchanging contents. Updates are "
"separately available. For a one-line description of the installation status "
"of package <tt>foo</tt>, use the command <tt>dpkg --list foo</tt>. To view "
"versions of all installed packages, run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:46 software.sgml:138
#, no-wrap
msgid "dpkg -l"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:46 software.sgml:145
msgid "For a more verbose description, use:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:46 software.sgml:138
#, no-wrap
msgid "dpkg --status foo"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:150
msgid "How does Debian support non-English languages?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:153
msgid ""
"&debian; is distributed with keymaps for nearly two dozen keyboards, and "
"with utilities (in the <tt>kbd</tt> package) to install, view, and modify "
"the tables."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:154
msgid "The installation prompts the user to specify the keyboard he will use."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:158
msgid ""
"Vast majority of the software we packaged supports entering non-US-ASCII "
"characters used in other Latin languages (e.g. ISO-8859-1 or ISO-8859-2), "
"and a number of programs support multi-byte languages such as Japanese or "
"Chinese."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:165
msgid ""
"Currently, support for German-, Spanish-, Finnish-, French-, Hungarian-, "
"Italian-, Japanese-, Korean-, Dutch-, Polish-, Portuguese-, Russian-, "
"Turkish-, and Chinese-language manual pages is provided through the "
"<tt>manpages-LANG</tt> packages (where LANG is the two-letter ISO country "
"code). To access an NLS manual page, the user must set the shell LC_MESSAGES "
"variable to the appropriate string."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:169
msgid ""
"For example, in the case of the Italian-language manual pages, LC_MESSAGES "
"needs to be set to 'italian'. The <prgn>man</prgn> program will then search "
"for Italian manual pages under <tt>/usr/share/man/it/</tt>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:173
msgid "Where is pine?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:177
msgid ""
"Due to its restrictive license, it's in the non-free area. Moreover, since "
"license does not even allow modified binaries to be distributed, you have to "
"compile it yourself from the source and the Debian patches."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:181
msgid ""
"The source package name is <package>pine</package>. You can use the "
"<package>pine-tracker</package> package to be notified about when you need "
"to upgrade."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:184
msgid ""
"Note that there are many replacements for both pine and pico, such as "
"<package>mutt</package> and <package>nano</package>, that are located in the "
"main section."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:186
msgid "Where is qmail/ezmlm/djbdns?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:193
msgid ""
"Dan J. Bernstein used to distribute <url id=\"http://cr.yp.to/software.html"
"\" name=\"all software he has written\"> with a restrictive license which "
"does not allow modified binaries to be distributed. In november 2007 "
"however, Bernstein said \"[...] i have decided to put all of my future and "
"[...] past software into the public domain\". See <url id=\"http://cr.yp.to/"
"distributors.html\" name=\"FAQ from distributors\"> for his distribution "
"terms."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:200
msgid ""
"As of 2008-09, <package>daemontools</package>, <package>djbdns</package> and "
"<package>ucspi-tcp</package> are shipped with Debian lenny (in main). As of "
"this writing (2008-09), <package>qmail</package> nor <package>ezmlm</"
"package> is shipped with Debian main; see <url id=\"http://bugs.debian."
"org/457318\" name=\"Bug #457318 (ITP qmail)\"> and <url id=\"http://bugs."
"debian.org/469193\" name=\"Bug #469193 (ITP ezmlm-idx)\"> for the current "
"status."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:202
msgid "As of 2008-09, <tt>publicfile</tt> was still not free software."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:204
msgid "Where is a player for Flash (SWF)?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:207
msgid ""
"Debian ships both <package>gnash</package> and <package>swfdec</package>: "
"two free SWF movie players."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:209
msgid "Where is Google Earth?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:214
msgid ""
"Google Earth is available for GNU/Linux from Google's web site, but is not "
"only not Free Software, but is completely undistributable by a third party. "
"However, <package>googleearth-package</package> (in the contrib-section) "
"might be helpful in using this software."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:216
msgid "Where is VoIP software?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:220
msgid ""
"Two main open protocols are used for Voice Over IP: SIP and H.323. Both are "
"implemented by a wide variety of software in Debian main. <package>ekiga</"
"package> is one of the popular clients."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:46 software.sgml:223
msgid ""
"I have a wireless network card which doesn't work with Linux. What should I "
"do?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:225
msgid "Buy one which does :)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:3
msgid ""
"Alternatively, use <package>ndiswrapper</package> to use a driver for "
"Windows (if you have one) on your Linux system. See the <url id=\"http://"
"wiki.debian.org/NdisWrapper\" name=\"Debian Wiki ndiswrapper page\"> for "
"more information."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:5
msgid "The Debian FTP archives"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:7
msgid "How many Debian distributions are there?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:13
msgid ""
"There are three major distributions: the \"stable\" distribution, the "
"\"testing\" distribution, and the \"unstable\" distribution. The \"testing\" "
"distribution is sometimes `frozen' (see <ref id=\"frozen\">). Next to these, "
"there is the \"oldstable\" distribution (that's just the one from before "
"\"stable\"), and the \"experimental\" distribution."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:19
msgid ""
"Experimental is used for packages which are still being developed, and with "
"a high risk of breaking your system. It's used by developers who'd like to "
"study and test bleeding edge software. Users shouldn't be using packages "
"from here, because they can be dangerous and harmful even for the most "
"experienced people."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:21
msgid "See <ref id=\"choosing\"> for help when choosing a Debian distribution."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:23
msgid "What are all those names like etch, lenny, etc.?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:30
msgid ""
"They are just \"codenames\". When a Debian distribution is in the "
"development stage, it has no version number but a codename. The purpose of "
"these codenames is to make easier the mirroring of the Debian distributions "
"(if a real directory like <tt>unstable</tt> suddenly changed its name to "
"<tt>stable</tt>, a lot of stuff would have to be needlessly downloaded "
"again)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:36
msgid ""
"Currently, <tt>stable</tt> is a symbolic link to <tt>&releasename;</tt> (i."
"e. &debian; &release;) and <tt>testing</tt> is a symbolic link to "
"<tt>&testingreleasename;</tt>. This means that <tt>&releasename;</tt> is the "
"current stable distribution and <tt>&testingreleasename;</tt> is the current "
"testing distribution."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:39
msgid ""
"<tt>unstable</tt> is a permanent symbolic link to <tt>sid</tt>, as <tt>sid</"
"tt> is always the unstable distribution (see <ref id=\"sid\">)."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:41
msgid "Which other codenames have been used in the past?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:50
msgid ""
"Other codenames that have been already used are: <tt>buzz</tt> for release "
"1.1, <tt>rex</tt> for release 1.2, <tt>bo</tt> for releases 1.3.x, <tt>hamm</"
"tt> for release 2.0, <tt>slink</tt> for release 2.1, <tt>potato</tt> for "
"release 2.2, <tt>woody</tt> for release 3.0, <tt>sarge</tt> for release 3.1, "
"<tt>etch</tt> for release 4.0, and <tt>lenny</tt> for release 5.0, and "
"<tt>squeeze</tt> for release 6.0, <tt>wheezy</tt> for release 7.0."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:52
msgid "Where do these codenames come from?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:47 ftparchives.sgml:53
msgid ""
"So far they have been characters taken from the \"Toy Story\" movies by "
"Pixar."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:54
msgid "<em>buzz</em> (Buzz Lightyear) was the spaceman,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:55
msgid "<em>rex</em> was the tyrannosaurus,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:56
msgid "<em>bo</em> (Bo Peep) was the girl who took care of the sheep,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:57
msgid "<em>hamm</em> was the piggy bank,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:58
msgid "<em>slink</em> (Slinky Dog) was the toy dog,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:59
msgid "<em>potato</em> was, of course, Mr. Potato,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:60
msgid "<em>woody</em> was the cowboy,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:61
msgid "<em>sarge</em> was the sergeant of the Green Plastic Army Men,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:62
msgid "<em>etch</em> was the toy blackboard (Etch-a-Sketch),"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:63
msgid "<em>lenny</em> was the toy binoculars,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:64
msgid "<em>squeeze</em> was the name for the three-eyed aliens,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:66
msgid ""
"<em>wheezy</em> was the name of the rubber toy penguin with a red bow tie,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:69
msgid "<em>jessie</em> was the name of the yodelling cowgirl."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:71
msgid "<em>sid</em> was the boy next door who destroyed toys."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:125
msgid "What about \"sid\"?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:131
msgid ""
"<em>sid</em> or <em>unstable</em> is the place where most of the packages "
"are initially uploaded. It will never be released directly, because packages "
"which are to be released will first have to be included in <em>testing</em>, "
"in order to be released in <em>stable</em> later on. sid contains packages "
"for both released and unreleased architectures."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:134
msgid ""
"The name \"sid\" also comes from the \"Toy Story\" animated motion picture: "
"Sid was the boy next door who destroyed toys :-)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:156
msgid ""
"<footnote><p>When the present-day sid did not exist, the FTP site "
"organization had one major flaw: there was an assumption that when an "
"architecture is created in the current unstable, it will be released when "
"that distribution becomes the new stable. For many architectures that isn't "
"the case, with the result that those directories had to be moved at release "
"time. This was impractical because the move would chew up lots of bandwidth. "
"</p><p>The archive administrators worked around this problem for several "
"years by placing binaries for unreleased architectures in a special "
"directory called \"sid\". For those architectures not yet released, the "
"first time they were released there was a link from the current stable to "
"sid, and from then on they were created inside the unstable tree as normal. "
"This layout was somewhat confusing to users. </p><p>With the advent of "
"package pools (see <ref id=\"pools\">), binary packages began to be stored "
"in a canonical location in the pool, regardless of the distribution, so "
"releasing a distribution no longer causes large bandwidth consumption on the "
"mirrors (there is, however, a lot of gradual bandwidth consumption "
"throughout the development process).</p></footnote>"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:158
msgid "What does the stable directory contain?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:162
msgid ""
"stable/main/: This directory contains the packages which formally constitute "
"the most recent release of the &debian; system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:166
msgid ""
"These packages all comply with the <url id=\"http://www.debian.org/"
"social_contract#guidelines\" name=\"Debian Free Software Guidelines\">, and "
"are all freely usable and distributable."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:170
msgid ""
"stable/non-free/: This directory contains packages distribution of which is "
"restricted in a way that requires that distributors take careful account of "
"the specified copyright requirements."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:176
msgid ""
"For example, some packages have licenses which prohibit commercial "
"distribution. Others can be redistributed but are in fact shareware and not "
"free software. The licenses of each of these packages must be studied, and "
"possibly negotiated, before the packages are included in any redistribution "
"(e.g., in a CD-ROM)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:181
msgid ""
"stable/contrib/: This directory contains packages which are DFSG-free and "
"<em>freely distributable</em> themselves, but somehow depend on a package "
"that is <em>not</em> freely distributable and thus available only in the non-"
"free section."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:185
msgid "What does the testing distribution contain?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:188
msgid ""
"Packages are installed into the `testing' directory after they have "
"undergone some degree of testing in <qref id=\"unstable\">unstable</qref>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:194
msgid ""
"They must be in sync on all architectures where they have been built and "
"mustn't have dependencies that make them uninstallable; they also have to "
"have fewer release-critical bugs than the versions currently in testing. "
"This way, we hope that `testing' is always close to being a release "
"candidate."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:198
msgid ""
"More information about the status of \"testing\" in general and the "
"individual packages is available at <url id=\"http://www.debian.org/devel/"
"testing\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:200
msgid "What about \"testing\"? How is it `frozen'?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:204
msgid ""
"When the \"testing\" distribution is mature enough, the release manager "
"starts `freezing' it. The normal propagation delays are increased to ensure "
"that as little as possible new bugs from \"unstable\" enter \"testing\"."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:210
msgid ""
"After a while, the \"testing\" distribution becomes truly `frozen'. This "
"means that all new packages that are to propagate to the \"testing\" are "
"held back, unless they include release-critical bug fixes. The \"testing\" "
"distribution can also remain in such a deep freeze during the so-called "
"`test cycles', when the release is imminent."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:216
msgid ""
"When a \"testing\" release becomes `frozen', \"unstable\" tends to partially "
"freeze as well. This is because developers are reluctant to upload radically "
"new software to unstable, in case the frozen software in testing needs minor "
"updates and to fix release critical bugs which keep testing from becoming "
"\"stable\"."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:221
msgid ""
"We keep a record of bugs in the \"testing\" distribution that can hold off a "
"package from being released, or bugs that can hold back the whole release. "
"For details, please see <url id=\"http://www.debian.org/releases/testing/\" "
"name=\"current testing release information\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:225
msgid ""
"Once that bug count lowers to maximum acceptable values, the frozen \"testing"
"\" distribution is declared \"stable\" and released with a version number."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:234
msgid ""
"The most important bug count is the \"Release Critical\" bug count, which "
"can be followed in the <url id=\"http://bugs.debian.org/release-critical/\" "
"name=\"Release-critical bug status page\">. A common release goal is <url id="
"\"http://wiki.debian.org/ReleaseGoals/NoRCBugs\" name=\"NoRCBugs\"> which "
"means that the distribution should not have any bugs of severity critical, "
"grave or serious. The full list of issues considered critical can be found "
"in the <url id=\"http://release.debian.org/testing/rc_policy.txt\" name=\"RC "
"policy document\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:238
msgid ""
"With each new release, the previous \"stable\" distribution becomes obsolete "
"and moves to the archive. For more information please see <url id=\"http://"
"www.debian.org/distrib/archive\" name=\"Debian archive\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:240
msgid "What does the unstable distribution contain?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:246
msgid ""
"The `unstable' directory contains a snapshot of the current development "
"system. Users are welcome to use and test these packages, but are warned "
"about their state of readiness. The advantage of using the unstable "
"distribution is that you are always up-to-date with the latest in GNU/Linux "
"software industry, but if it breaks: you get to keep both parts :-)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:249
msgid ""
"There are also main, contrib and non-free subdirectories in `unstable', "
"separated on the same criteria as in `stable'."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:251
msgid "What are all those directories at the Debian FTP archives?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:254
msgid ""
"The software that has been packaged for &debian; is available in one of "
"several directory trees on each Debian mirror site."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:258
msgid ""
"The <tt>dists</tt> directory is short for \"distributions\", and it is the "
"canonical way to access the currently available Debian releases (and pre-"
"releases)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:261
msgid ""
"The <tt>pool</tt> directory contains the actual packages, see <ref id=\"pools"
"\">."
msgstr ""

#. type: <p><taglist>
#: debian-faq.sgml:47 ftparchives.sgml:262
msgid "There are the following supplementary directories:"
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:47 ftparchives.sgml:263
msgid "<em>/tools/</em>:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:265
msgid ""
"DOS utilities for creating boot disks, partitioning your disk drive, "
"compressing/decompressing files, and booting Linux."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:47 ftparchives.sgml:266
msgid "<em>/doc/</em>:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:268
msgid ""
"The basic Debian documentation, such as this FAQ, the bug reporting system "
"instructions, etc."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:47 ftparchives.sgml:269
msgid "<em>/indices/</em>:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:271
msgid ""
"various indices of the site (the Maintainers file and the override files)."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:47 ftparchives.sgml:272
msgid "<em>/project/</em>:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:274
msgid "mostly developer-only materials and some miscellaneous files."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:279
msgid "What are all those directories inside <tt>dists/stable/main</tt>?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:284
msgid ""
"Within each of the major directory trees<footnote><p><tt>dists/stable/main</"
"tt>, <tt>dists/stable/contrib</tt>, <tt>dists/stable/non-free</tt>, and "
"<tt>dists/unstable/main/</tt>, etc.</p></footnote>, there are three sets of "
"subdirectories containing index files."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:290
msgid ""
"There's one set of <tt>binary-<var>something</var></tt> subdirectories which "
"contain index files for binary packages of each available computer "
"architecture, for example <tt>binary-i386</tt> for packages which execute on "
"Intel x86 PC machines or <tt>binary-sparc</tt> for packages which execute on "
"Sun SPARCStations."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:294
msgid ""
"The complete list of available architectures for each release is available "
"at <url id=\"http://www.debian.org/releases/\" name=\"the release's web page"
"\">. For the current release, please see <ref id=\"arches\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:299
msgid ""
"The index files in binary-* are called Packages(.gz, .bz2) and they include "
"a summary of each binary package that is included in that distribution. The "
"actual binary packages reside in the top level <qref id=\"pools\"><tt>pool</"
"tt> directory</qref>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:303
msgid ""
"Furthermore, there's a subdirectory called source/ which contains index "
"files for source packages included in the distribution. The index file is "
"called Sources(.gz, .bz2)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:307
msgid ""
"Last but not least, there's a set of subdirectories meant for the "
"installation system index files, they are at <tt>debian-installer/binary-"
"<var>architecture</var></tt>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:309
msgid "Where is the source code?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:314
msgid ""
"Source code is included for everything in the Debian system. Moreover, the "
"license terms of most programs in the system <em>require</em> that source "
"code be distributed along with the programs, or that an offer to provide the "
"source code accompany the programs."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:321
msgid ""
"The source code is distributed in the <tt>pool</tt> directory (see <ref id="
"\"pools\">) together with all the architecture-specific binary directories. "
"To retrieve the source code without having to be familiar with the structure "
"of the FTP archive, try a command like <tt>apt-get source mypackagename</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:325
msgid ""
"Some packages are only distributed as source code due to the restrictions in "
"their licenses. Notably, one such package is <tt>pine</tt>, see <ref id="
"\"pine\"> for more information."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:328
msgid ""
"Source code may or may not be available for packages in the \"contrib\" and "
"\"non-free\" directories, which are not formally part of the Debian system."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:330
msgid "What's in the <tt>pool</tt> directory?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:337
msgid ""
"Packages are kept in a large `pool', structured according to the name of the "
"source package. To make this manageable, the pool is subdivided by section "
"(`main', `contrib' and `non-free') and by the first letter of the source "
"package name. These directories contain several files: the binary packages "
"for each architecture, and the source packages from which the binary "
"packages were generated."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:342
msgid ""
"You can find out where each package is placed by executing a command like "
"<tt>apt-cache showsrc mypackagename</tt> and looking at the `Directory:' "
"line. For example, the <tt>apache</tt> packages are stored in <tt>pool/main/"
"a/apache/</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:352
msgid ""
"Additionally, since there are so many <tt>lib*</tt> packages, these are "
"treated specially: for instance, libpaper packages are stored in <tt>pool/"
"main/libp/libpaper/</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:362
msgid ""
"<footnote><p>Historically, packages were kept in the subdirectory of "
"<tt>dists</tt> corresponding to which distribution contained them. This "
"turned out to cause various problems, such as large bandwidth consumption on "
"mirrors when major changes were made. This was fixed with the introduction "
"of the package pool. </p><p>The <tt>dists</tt> directories are still used "
"for the index files used by programs like <tt>apt</tt>.</p></footnote>"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:364
msgid "What is \"incoming\"?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:368
msgid ""
"After a developer uploads a package, it stays for a short while in the "
"\"incoming\" directory before it is checked that it's genuine and allowed "
"into the archive."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:374
msgid ""
"Usually nobody should install things from this place. However, in some rare "
"cases of emergency, the incoming directory is available at <url id=\"http://"
"incoming.debian.org/\">. You can manually fetch packages, check the GPG "
"signature and MD5sums in the .changes and .dsc files, and then install them."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:47 ftparchives.sgml:376
msgid "How do I set up my own apt-able repository?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:3
msgid ""
"If you have built some private Debian packages which you'd like to install "
"using the standard Debian package management tools, you can set up your own "
"apt-able package archive. This is also useful if you'd like to share your "
"Debian packages while these are not distributed by the Debian project. "
"Instructions on how to do this are given in the <url id=\"http://www.debian."
"org/doc/manuals/repository-howto/repository-howto\" name=\"Debian Repository "
"HOWTO\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:5
msgid "Basics of the Debian package management system"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:9
msgid ""
"This chapter touches on some lower level internals of Debian package "
"management. If you're interested mainly in <em>usage</em> of the relevant "
"tools, skip to chapters <ref id=\"pkgtools\"> and/or <ref id=\"uptodate\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:11
msgid "What is a Debian package?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:48 pkg_basics.sgml:14
msgid ""
"Packages generally contain all of the files necessary to implement a set of "
"related commands or features. There are two types of Debian packages:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:22
msgid ""
"<em>Binary packages</em>, which contain executables, configuration files, "
"man/info pages, copyright information, and other documentation. These "
"packages are distributed in a Debian-specific archive format (see <ref id="
"\"deb-format\">); they are usually distinguished by having a '.deb' file "
"extension. Binary packages can be unpacked using the Debian utility "
"<tt>dpkg</tt> (possibly via a frontend like <prgn>aptitude</prgn>); details "
"are given in its manual page."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:31
msgid ""
"<em>Source packages</em>, which consist of a <tt>.dsc</tt> file describing "
"the source package (including the names of the following files), a <tt>.orig."
"tar.gz</tt> file that contains the original unmodified source in gzip-"
"compressed tar format and usually a <tt>.diff.gz</tt> file that contains the "
"Debian-specific changes to the original source. The utility <tt>dpkg-source</"
"tt> packs and unpacks Debian source archives; details are provided in its "
"manual page. (The program <prgn>apt-get</prgn> can get used a frontend for "
"<tt>dpkg-source</tt>.)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:45
msgid ""
"Installation of software by the package system uses \"dependencies\" which "
"are carefully designed by the package maintainers. These dependencies are "
"documented in the <tt>control</tt> file associated with each package. For "
"example, the package containing the GNU C compiler (<package>gcc</package>) "
"\"depends\" on the package <package>binutils</package> which includes the "
"linker and assembler. If a user attempts to install <package>gcc</package> "
"without having first installed <package>binutils</package>, the package "
"management system (dpkg) will send an error message that it also needs "
"<package>binutils</package>, and stop installing <package>gcc</package>. "
"(However, this facility can be overridden by the insistent user, see <manref "
"section=\"8\" name=\"dpkg\">.) See more in <ref id=\"depends\"> below."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:48 pkg_basics.sgml:46
msgid "Debian's packaging tools can be used to:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:47
msgid "manipulate and manage packages or parts of packages,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:48
msgid "administer local overrides of files in a package,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:49
msgid "aid developers in the construction of package archives, and"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:52
msgid ""
"aid users in the installation of packages which reside on a remote FTP site."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:56
msgid "What is the format of a Debian binary package?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:61
msgid ""
"A Debian \"package\", or a Debian archive file, contains the executable "
"files, libraries, and documentation associated with a particular suite of "
"program or set of related programs. Normally, a Debian archive file has a "
"filename that ends in <tt>.deb</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:67
msgid ""
"The internals of this Debian binary packages format are described in the "
"<manref section=\"5\" name=\"deb\"> manual page. This internal format is "
"subject to change (between major releases of &debian;), therefore please "
"always use <manref section=\"1\" name=\"dpkg-deb\"> if you need to do "
"lowlevel manipulations on <tt>.deb</tt> files."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:69
msgid "Why are Debian package file names so long?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:72
msgid ""
"The Debian binary package file names conform to the following convention: "
"&lt;foo&gt;_&lt;VersionNumber&gt;-&lt;DebianRevisionNumber&gt;_&lt;"
"DebianArchitecture&gt;.deb"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:48 pkg_basics.sgml:75
msgid ""
"Note that <tt>foo</tt> is supposed to be the package name. As a check, one "
"can learn the package name associated with a particular Debian archive file "
"(.deb file) in one of these ways:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:78
msgid ""
"inspect the \"Packages\" file in the directory where it was stored at a "
"Debian FTP archive site. This file contains a stanza describing each "
"package; the first field in each stanza is the formal package name."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:83
msgid ""
"use the command <tt>dpkg --info foo_VVV-RRR_AAA.deb</tt> (where VVV, RRR and "
"AAA are the version, revision and architecture of the package in question, "
"respectively). This displays, among other things, the package name "
"corresponding to the archive file being unpacked."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:89
msgid ""
"The <tt>VVV</tt> component is the version number specified by the upstream "
"developer. There are no standards in place here, so the version number may "
"have formats as different as \"19990513\" and \"1.3.8pre1\"."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:97
msgid ""
"The <tt>RRR</tt> component is the Debian revision number, and is specified "
"by the Debian developer (or an individual user if he chooses to build the "
"package himself). This number corresponds to the revision level of the "
"Debian package, thus, a new revision level usually signifies changes in the "
"Debian Makefile (<tt>debian/rules</tt>), the Debian control file (<tt>debian/"
"control</tt>), the installation or removal scripts (<tt>debian/p*</tt>), or "
"in the configuration files used with the package."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:104
msgid ""
"The <tt>AAA</tt> component identifies the processor for which the package "
"was built. This is commonly <tt>i386</tt>, which refers to chips compatible "
"to Intel's 386 or later versions. For other possibilities review Debian's "
"FTP directory structure at <ref id=\"dirtree\">. For details, see the "
"description of \"Debian architecture\" in the manual page <manref section="
"\"1\" name=\"dpkg-architecture\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:106
msgid "What is a Debian control file?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:109
msgid ""
"Specifics regarding the contents of a Debian control file are provided in "
"the Debian Policy Manual, section 5, see <ref id=\"debiandocs\">."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:48 pkg_basics.sgml:110
msgid ""
"Briefly, a sample control file is shown below for the Debian package hello:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:128
#, no-wrap
msgid ""
"Package: hello\n"
"Priority: optional\n"
"Section: devel\n"
"Installed-Size: 45\n"
"Maintainer: Adam Heath &lt;doogie@debian.org&gt;\n"
"Architecture: i386\n"
"Version: 1.3-16\n"
"Depends: libc6 (>= 2.1)\n"
"Description: The classic greeting, and a good example\n"
" The GNU hello program produces a familiar, friendly greeting.  It\n"
"\n"
" allows nonprogrammers to use a classic computer science tool which\n"
" would otherwise be unavailable to them.\n"
" .\n"
" Seriously, though: this is an example of how to do a Debian package.\n"
" It is the Debian version of the GNU Project's `hello world' program\n"
" (which is itself an example for the GNU Project)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:135
msgid ""
"The Package field gives the package name. This is the name by which the "
"package can be manipulated by the package tools, and usually similar to but "
"not necessarily the same as the first component string in the Debian archive "
"file name."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:139
msgid ""
"The Version field gives both the upstream developer's version number and (in "
"the last component) the revision level of the Debian package of this program "
"as explained in <ref id=\"pkgname\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:142
msgid ""
"The Architecture field specifies the chip for which this particular binary "
"was compiled."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:145
msgid ""
"The Depends field gives a list of packages that have to be installed in "
"order to install this package successfully."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:150
msgid ""
"The Installed-Size indicates how much disk space the installed package will "
"consume. This is intended to be used by installation front-ends in order to "
"show whether there is enough disk space available to install the program."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:153
msgid ""
"The Section line gives the \"section\" where this Debian package is stored "
"at the Debian FTP sites."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:158
msgid ""
"The Priority indicates how important is this package for installation, so "
"that semi-intelligent software like dselect or aptitude can sort the package "
"into a category of e.g. packages optionally installed. See <ref id=\"priority"
"\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:161
msgid ""
"The Maintainer field gives the e-mail address of the person who is currently "
"responsible for maintaining this package."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:163
msgid "The Description field gives a brief summary of the package's features."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:167
msgid ""
"For more information about all possible fields a package can have, please "
"see the Debian Policy Manual, section 5, \"Control files and their fields\", "
"see <ref id=\"debiandocs\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:169
msgid "What is a Debian conffile?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:175
msgid ""
"Conffiles is a list of configuration files (usually placed in <tt>/etc</tt>) "
"that the package management system will not overwrite when the package is "
"upgraded. This ensures that local values for the contents of these files "
"will be preserved, and is a critical feature enabling the in-place upgrade "
"of packages on a running system."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:48 pkg_basics.sgml:175
msgid "To determine exactly which files are preserved during an upgrade, run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:175
#, no-wrap
msgid "dpkg --status package"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:48 pkg_basics.sgml:179
msgid "And look under \"Conffiles:\"."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:182
msgid "What is a Debian preinst, postinst, prerm, and postrm script?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:186
msgid ""
"These files are executable scripts which are automatically run before or "
"after a package is installed. Along with a file named <tt>control</tt>, all "
"of these files are part of the \"control\" section of a Debian archive file."
msgstr ""

#. type: <p><taglist>
#: debian-faq.sgml:48 pkg_basics.sgml:187
msgid "The individual files are:"
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:48 pkg_basics.sgml:188
msgid "preinst"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:194
msgid ""
"This script executes before that package will be unpacked from its Debian "
"archive (\".deb\") file. Many 'preinst' scripts stop services for packages "
"which are being upgraded until their installation or upgrade is completed "
"(following the successful execution of the 'postinst' script)."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:48 pkg_basics.sgml:194
msgid "postinst"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:203
msgid ""
"This script typically completes any required configuration of the package "
"<tt>foo</tt> once <tt>foo</tt> has been unpacked from its Debian archive (\"."
"deb\") file. Often, 'postinst' scripts ask the user for input, and/or warn "
"the user that if he accepts default values, he should remember to go back "
"and re-configure that package as the situation warrants. Many 'postinst' "
"scripts then execute any commands necessary to start or restart a service "
"once a new package has been installed or upgraded."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:48 pkg_basics.sgml:203
msgid "prerm"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:208
msgid ""
"This script typically stops any daemons which are associated with a package. "
"It is executed before the removal of files associated with the package."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:48 pkg_basics.sgml:208
msgid "postrm"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:212
msgid ""
"This script typically modifies links or other files associated with <tt>foo</"
"tt>, and/or removes files created by the package. (Also see <ref id=\"virtual"
"\">.)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:222
msgid ""
"Currently all of the control files can be found in directory <tt>/var/lib/"
"dpkg/info</tt>. The files relevant to package <tt>foo</tt> begin with the "
"name \"foo\" and have file extensions of \"preinst\", \"postinst\", etc., as "
"appropriate. The file <tt>foo.list</tt> in that directory lists all of the "
"files that were installed with the package <tt>foo</tt>. (Note that the "
"location of these files is a dpkg internal; you should not rely on it.)"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:225
msgid ""
"What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, "
"<em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:48 pkg_basics.sgml:228
msgid ""
"Each Debian package is assigned a <em>priority</em> by the distribution "
"maintainers, as an aid to the package management system. The priorities are:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:230
msgid ""
"<strong>Required</strong>: packages that are necessary for the proper "
"functioning of the system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:236
msgid ""
"This includes all tools that are necessary to repair system defects. You "
"must not remove these packages or your system may become totally broken and "
"you may probably not even be able to use dpkg to put things back. Systems "
"with only the Required packages are probably unusable, but they do have "
"enough functionality to allow the sysadmin to boot and install more software."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:238
msgid ""
"<strong>Important</strong> packages should be found on any Unix-like system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:242
msgid ""
"Other packages which the system will not run well or be usable without will "
"be here. This does <em>NOT</em> include Emacs or X or TeX or any other large "
"applications. These packages only constitute the bare infrastructure."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:246
msgid ""
"<strong>Standard</strong> packages are standard on any Linux system, "
"including a reasonably small but not too limited character-mode system. "
"Tools are included to be able to browse the web (using w3m), send e-mail "
"(with mutt) and download files from FTP servers."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:253
msgid ""
"This is what will install by default if users do not select anything else. "
"It does not include many large applications, but it does include the Python "
"interpreter and some server software like OpenSSH (for remote "
"administration), Exim (for mail delivery, although it can be configured for "
"local delivery only), an identd server (pidentd) and the RPC portmapper "
"(<tt>portmap</tt>). It also includes some common generic documentation that "
"most users will find helpful."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:256
msgid ""
"<strong>Optional</strong> packages include all those that you might "
"reasonably want to install if you did not know what it was, or do not have "
"specialized requirements."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:257
msgid "This includes X, a full TeX distribution, and lots of applications."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:262
msgid ""
"<strong>Extra</strong>: packages that either conflict with others with "
"higher priorities, are only likely to be useful if you already know what "
"they are, or have specialized requirements that make them unsuitable for "
"\"Optional\"."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:269
msgid ""
"If you do a default Debian installation all the packages of priority "
"<strong>Standard</strong> or higher will be installed in your system. If you "
"select pre-defined tasks you will get lower priority packages too."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:273
msgid ""
"Additionally, some packages are marked as <strong>Essential</strong> since "
"they are absolutely necessary for the proper functioning of the system. The "
"package management tools will refuse to remove these."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:275
msgid "What is a Virtual Package?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:283
msgid ""
"A virtual package is a generic name that applies to any one of a group of "
"packages, all of which provide similar basic functionality. For example, "
"both the <tt>tin</tt> and <tt>trn</tt> programs are news readers, and should "
"therefore satisfy any dependency of a program that required a news reader on "
"a system, in order to work or to be useful. They are therefore both said to "
"provide the \"virtual package\" called <tt>news-reader</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:290
msgid ""
"Similarly, <tt>smail</tt> and <tt>sendmail</tt> both provide the "
"functionality of a mail transport agent. They are therefore said to provide "
"the virtual package, \"mail transport agent\". If either one is installed, "
"then any program depending on the installation of a <tt>mail-transport-"
"agent</tt> will be satisfied by the existence of this virtual package."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:296
msgid ""
"Debian provides a mechanism so that, if more than one package which provide "
"the same virtual package is installed on a system, then system "
"administrators can set one as the preferred package. The relevant command is "
"<tt>update-alternatives</tt>, and is described further in <ref id=\"diverse"
"\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:300
msgid ""
"What is meant by saying that a package <em>Depends</em>, <em>Recommends</"
"em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em>, <em>Breaks</"
"em> or <em>Provides</em> another package?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:48 pkg_basics.sgml:304
msgid ""
"The Debian package system has a range of package \"dependencies\" which are "
"designed to indicate (in a single flag) the level at which Program A can "
"operate independently of the existence of Program B on a given system:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:309
msgid ""
"Package A <em>depends</em> on Package B if B absolutely must be installed in "
"order to run A. In some cases, A depends not only on B, but on a version of "
"B. In this case, the version dependency is usually a lower limit, in the "
"sense that A depends on any version of B more recent than some specified "
"version."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:312
msgid ""
"Package A <em>recommends</em> Package B, if the package maintainer judges "
"that most users would not want A without also having the functionality "
"provided by B."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:314
msgid ""
"Package A <em>suggests</em> Package B if B contains files that are related "
"to (and usually enhance) the functionality of A."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:318
msgid ""
"Package A <em>conflicts</em> with Package B when A will not operate if B is "
"installed on the system. Most often, conflicts are cases where A contains "
"files which are an improvement over those in B. \"Conflicts\" are often "
"combined with \"replaces\"."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:320
msgid ""
"Package A <em>replaces</em> Package B when files installed by B are removed "
"and (in some cases) over-written by files in A."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:324
msgid ""
"Package A <em>breaks</em> Package B when both cannot packages cannot be "
"simultaneously configured in a system. The package management system will "
"refuse to install one if the other one is already installed and configured "
"in the system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:329
msgid ""
"Package A <em>provides</em> Package B when all of the files and "
"functionality of B are incorporated into A. This mechanism provides a way "
"for users with constrained disk space to get only that part of package A "
"which they really need."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:335
msgid ""
"More detailed information on the use of each these terms can be found in the "
"Debian Policy manual, section 7.2, \"Binary Dependencies\", see <ref id="
"\"debiandocs\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:337
msgid "What is meant by Pre-Depends?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:347
msgid ""
"\"Pre-Depends\" is a special dependency. In the case of most packages, "
"<tt>dpkg</tt> will unpack its archive file (i.e., its <tt>.deb</tt> file) "
"independently of whether or not the files on which it depends exist on the "
"system. Simplistically, unpacking means that <tt>dpkg</tt> will extract the "
"files from the archive file that were meant to be installed on your file "
"system, and put them in place. If those packages <em>depend</em> on the "
"existence of some other packages on your system, <tt>dpkg</tt> will refuse "
"to complete the installation (by executing its \"configure\" action) until "
"the other packages are installed."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:356
msgid ""
"However, for some packages, <tt>dpkg</tt> will refuse even to unpack them "
"until certain dependencies are resolved. Such packages are said to \"Pre-"
"depend\" on the presence of some other packages. The Debian project provided "
"this mechanism to support the safe upgrading of systems from <tt>a.out</tt> "
"format to <tt>ELF</tt> format, where the <em>order</em> in which packages "
"were unpacked was critical. There are other large upgrade situations where "
"this method is useful, e.g. the packages with the required priority and "
"their LibC dependency."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:359
msgid ""
"As before, more detailed information about this can be found in the Policy "
"manual."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:362
msgid ""
"What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, "
"<em>purge</em> and <em>hold</em> in the package status?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:366
msgid ""
"These \"want\" flags tell what the user wanted to do with a package (as "
"indicated either by the user's actions in the \"Select\" section of "
"<tt>dselect</tt>, or by the user's direct invocations of <tt>dpkg</tt>)."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:48 pkg_basics.sgml:367
msgid "Their meanings are:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:368
msgid "unknown - the user has never indicated whether he wants the package"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:369
msgid "install - the user wants the package installed or upgraded"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:371
msgid ""
"remove - the user wants the package removed, but does not want to remove any "
"existing configuration files."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:373
msgid ""
"purge - the user wants the package to be removed completely, including its "
"configuration files."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:376
msgid ""
"hold - the user wants this package not to be processed, i.e., he wants to "
"keep the current version with the current status whatever that is."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:380
msgid "How do I put a package on hold?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:383
msgid ""
"There are three ways of holding back packages, with dpkg, aptitude or with "
"dselect."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:48 pkg_basics.sgml:383
msgid "With dpkg, you have to export the list of package selections, with:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:383
#, no-wrap
msgid "dpkg --get-selections \\* > selections.txt"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:48 pkg_basics.sgml:386
msgid ""
"Then edit the resulting file <file>selections.txt</file>, change the line "
"containing the package you wish to hold, e.g. <package>libc6</package>, from "
"this:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:383
#, no-wrap
msgid "libc6                                           install"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:48 pkg_basics.sgml:388
msgid "to this:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:383
#, no-wrap
msgid "libc6                                           hold"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:48 pkg_basics.sgml:390
msgid "Save the file, and reload it into dpkg database with:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:383
#, no-wrap
msgid "dpkg --set-selections < selections.txt"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:48 pkg_basics.sgml:393
msgid "With aptitude, you can hold a package using"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:393
#, no-wrap
msgid "aptitude hold package_name"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:48 pkg_basics.sgml:395
msgid "and remove the hold with"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:393
#, no-wrap
msgid "aptitude unhold package_name"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:403
msgid ""
"With dselect, you have to enter the [S]elect screen, find the package you "
"wish to hold in its present state, and press the `=' key (or `H'). The "
"changes will go live immediately after you exit the [S]elect screen."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:405
msgid "How do I install a source package?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:409
msgid ""
"Debian source packages can't actually be \"installed\", they are just "
"unpacked in whatever directory you want to build the binary packages they "
"produce."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:48 pkg_basics.sgml:414
msgid ""
"Source packages are distributed on most of the same mirrors where you can "
"obtain the binary packages. If you set up your APT's <manref section=\"5\" "
"name=\"sources.list\"> to include the appropriate \"deb-src\" lines, you'll "
"be able to easily download any source packages by running"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:409 pkg_basics.sgml:432
#, no-wrap
msgid "apt-get source foo"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:48 pkg_basics.sgml:421
msgid ""
"To help you in actually building the source package, Debian source package "
"provide the so-called build-dependencies mechanism. This means that the "
"source package maintainer keeps a list of other packages that are required "
"to build their package. To see how this is useful, run"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:417
#, no-wrap
msgid "apt-get build-dep foo"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:48 pkg_basics.sgml:426
msgid "before building the source."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:428
msgid "How do I build binary packages from a source package?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:432
msgid ""
"The preferred way to do this is by using various wrapper tools. We'll show "
"how it's done using the <tt>devscripts</tt> tools. Install this package if "
"you haven't done so already."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:48 pkg_basics.sgml:433
msgid "Now, first get the source package:"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:48 pkg_basics.sgml:437
msgid "and change to the source tree:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:432
#, no-wrap
msgid "cd foo-*"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:48 pkg_basics.sgml:441
msgid "Then install needed build-dependencies (if any):"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:432
#, no-wrap
msgid "sudo apt-get build-dep foo"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:48 pkg_basics.sgml:446
msgid ""
"Then create a dedicated version of your own build (so that you won't get "
"confused later when Debian itself releases a new version)"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:432
#, no-wrap
msgid "dch -l local 'Blah blah blah'"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:48 pkg_basics.sgml:450
msgid "And finally build your package"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:432
#, no-wrap
msgid "debuild -us -uc"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:48 pkg_basics.sgml:455
msgid ""
"If everything worked out fine, you should now be able to install your "
"package by running"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:432
#, no-wrap
msgid "sudo dpkg -i ../*.deb"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:459
msgid ""
"If you prefer to do things manually, and don't want to use <tt>devscripts</"
"tt>, follow this procedure:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:48 pkg_basics.sgml:465
msgid ""
"You will need all of foo_*.dsc, foo_*.tar.gz and foo_*.diff.gz to compile "
"the source (note: there is no .diff.gz for some packages that are native to "
"Debian)."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:48 pkg_basics.sgml:467
msgid ""
"Once you have them (<ref id=\"sourcepkgs\">), if you have the <package>dpkg-"
"dev</package> package installed, the following command:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:465
#, no-wrap
msgid "dpkg-source -x foo_version-revision.dsc"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:48 pkg_basics.sgml:471
msgid "will extract the package into a directory called <tt>foo-version</tt>."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:48 pkg_basics.sgml:472
msgid ""
"If you want just to compile the package, you may cd into <tt>foo-version</"
"tt> directory and issue the command"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:471
#, no-wrap
msgid "dpkg-buildpackage -rfakeroot -b"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:48 pkg_basics.sgml:475
msgid ""
"to build the package (note that this also requires the <package>fakeroot</"
"package> package), and then"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:48 pkg_basics.sgml:471
#, no-wrap
msgid "dpkg -i ../foo_version-revision_arch.deb"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:48 pkg_basics.sgml:479
msgid "to install the newly-built package(s)."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:48 pkg_basics.sgml:481
msgid "How do I create Debian packages myself?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:3
msgid ""
"For a more detailed description on this, read the New Maintainers' Guide, "
"available in the <package>maint-guide</package> package, or at <url id="
"\"http://www.debian.org/doc/devel-manuals#maint-guide\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:5
msgid "The Debian package management tools"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:8
msgid "What programs does Debian provide for managing its packages?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:14
msgid ""
"There are multiple tools that are used to manage Debian packages, from "
"graphic or text-based interfaces to the low level tools used to install "
"packages. All the available tools rely on the lower level tools to properly "
"work and are presented here in decreasing complexity level."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:19
msgid ""
"It is important to understand that the higher level package management tools "
"such as <prgn>aptitude</prgn> or <prgn>dselect</prgn> rely on <prgn>apt</"
"prgn> which, itself, relies on <prgn>dpkg</prgn> to manage the packages in "
"the system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:30
msgid ""
"See <url id=\"http://www.debian.org/doc/manuals/debian-reference/ch02.en.html"
"\" name=\"Chapter 2. Debian package management\"> of the <url id=\"http://"
"www.debian.org/doc/manuals/debian-reference/\" name=\"Debian reference\"> "
"for more information about the Debian package management utilities. This "
"document is available in various languages and formats, see <url id=\"http://"
"www.debian.org/doc/user-manuals#quick-reference\" name=\"the Debian "
"Reference entry on the DDP Users' Manuals overview\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:32
msgid "dpkg"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:49 pkgtools.sgml:34
msgid ""
"This is the main package management program. <prgn>dpkg</prgn> can be "
"invoked with many options. Some common uses are:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:35
msgid "Find out all the options: <tt>dpkg --help</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:37
msgid ""
"Print out the control file (and other information) for a specified package: "
"<tt>dpkg --info foo_VVV-RRR.deb</tt>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:39
msgid ""
"Install a package (including unpacking and configuring) onto the file system "
"of the hard disk: <tt>dpkg --install foo_VVV-RRR.deb</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:46
msgid ""
"Unpack (but do not configure) a Debian archive into the file system of the "
"hard disk: <tt>dpkg --unpack foo_VVV-RRR.deb</tt>. Note that this operation "
"does <em>not</em> necessarily leave the package in a usable state; some "
"files may need further customization to run properly. This command removes "
"any already-installed version of the program and runs the preinst (see <ref "
"id=\"maintscripts\">) script associated with the package."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:53
msgid ""
"Configure a package that already has been unpacked: <tt>dpkg --configure "
"foo</tt>. Among other things, this action runs the postinst (see <ref id="
"\"maintscripts\">) script associated with the package. It also updates the "
"files listed in the <tt>conffiles</tt> for this package. Notice that the "
"'configure' operation takes as its argument a package name (e.g., foo), "
"<em>not</em> the name of a Debian archive file (e.g., foo_VVV-RRR.deb)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:56
msgid ""
"Extract a single file named \"blurf\" (or a group of files named \"blurf*\" "
"from a Debian archive: <tt>dpkg --fsys-tarfile foo_VVV-RRR.deb | tar -xf - "
"blurf*</tt>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:58
msgid ""
"Remove a package (but not its configuration files): <tt>dpkg --remove foo</"
"tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:60
msgid ""
"Remove a package (including its configuration files): <tt>dpkg --purge foo</"
"tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:63
msgid ""
"List the installation status of packages containing the string (or regular "
"expression) \"foo*\": <tt>dpkg --list 'foo*'</tt>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:67
msgid "APT"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:80
msgid ""
"APT is the <em>Advanced Package Tool</em> and provides the <prgn>apt-get</"
"prgn> program. <prgn>apt-get</prgn> provides a simple way to retrieve and "
"install packages from multiple sources using the command line. Unlike "
"<prgn>dpkg</prgn>, <prgn>apt-get</prgn> does not understand .deb files, it "
"works with the packages proper name and can only install .deb archives from "
"a source specified in <file>/etc/apt/sources.list</file>. <prgn>apt-get</"
"prgn> will call <prgn>dpkg</prgn> directly after downloading the .deb "
"archives<footnote><p>Notice that there are ports that make this tool "
"available with other package management systems, like Red Hat package "
"manager, also known as <prgn>rpm</prgn></p></footnote> from the configured "
"sources."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:49 pkgtools.sgml:82
msgid "Some common ways to use <prgn>apt-get</prgn> are:"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:83
msgid "To update the list of package known by your system, you can run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:83 debian-faq.sgml:50 uptodate.sgml:78
#, no-wrap
msgid "apt-get update"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:49 pkgtools.sgml:86
msgid "(you should execute this regularly to update your package lists)"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:88
msgid ""
"To upgrade all the packages on your system (without installing extra "
"packages or removing packages), run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:83
#, no-wrap
msgid "apt-get upgrade"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:91
msgid "To install the <var>foo</var> package and all its dependencies, run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:83
#, no-wrap
msgid "apt-get install foo"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:94
msgid "To remove the foo package from your system, run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:83
#, no-wrap
msgid "apt-get remove foo"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:98
msgid ""
"To remove the foo package and its configuration files from your system, run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:83
#, no-wrap
msgid "apt-get --purge remove foo"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:102
msgid ""
"To upgrade all the packages on your system, and, if needed for a package "
"upgrade, installing extra packages or removing packages, run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:83 debian-faq.sgml:50 uptodate.sgml:78
#, no-wrap
msgid "apt-get dist-upgrade"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:49 pkgtools.sgml:109
msgid ""
"(The command <tt>upgrade</tt> keeps a package at its installed obsolete "
"version if upgrading would need an extra package to be installed, for a new "
"dependency to be satisfied. The <tt>dist-upgrade</tt> command is less "
"conservative.)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:114
msgid ""
"Note that you must be logged in as root to perform any commands that modify "
"the system packages."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:118
msgid ""
"Note that <prgn>apt-get</prgn> now installs recommended packages as default "
"and is the preferred program for package management from console to perform "
"system installation and major system upgrades for its robustness."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:49 pkgtools.sgml:124
msgid ""
"The apt tool suite also includes the <prgn>apt-cache</prgn> tool to query "
"the package lists. You can use it to find packages providing specific "
"functionality through simple text or regular expression queries and through "
"queries of dependencies in the package management system. Some common ways "
"to use <prgn>apt-cache</prgn> are:"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:125
msgid "To find packages whose description contain <var>word</var>:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:125
#, no-wrap
msgid "apt-cache search <var>word</var>"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:128
msgid "To print the detailed information of a package:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:125
#, no-wrap
msgid "apt-cache show <var>package</var>"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:131
msgid "To print the packages a given package depends on:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:125
#, no-wrap
msgid "apt-cache depends <var>package</var>"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:136
msgid ""
"To print detailed information of the versions available for a package and "
"the packages that reverse-depends on it:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:125
#, no-wrap
msgid "apt-cache showpkg <var>package</var>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:147
msgid ""
"For more information, install the <package>apt</package> package and read "
"<manref section=\"8\" name=\"apt-get\">, <manref section=\"5\" name="
"\"sources.list\"> and install the <package>apt-doc</package> package and "
"read <file>/usr/share/doc/apt-doc/guide.html/index.html</file>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:149 debian-faq.sgml:50 uptodate.sgml:36
#: uptodate.sgml:103
msgid "aptitude"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:155
msgid ""
"<prgn>aptitude</prgn> is a package manager for &debian; systems that "
"provides a frontend to the apt package management infrastructure. "
"<prgn>aptitude</prgn> is a text-based interface using the curses library, it "
"can be used to perform management tasks in a fast and easy way."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:49 pkgtools.sgml:159
msgid ""
"<prgn>aptitude</prgn> provides the functionality of <prgn>dselect</prgn> and "
"<prgn>apt-get</prgn>, as well as many additional features not found in "
"either program:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:161
msgid "<prgn>aptitude</prgn> offers easy access to all versions of a package."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:165
msgid ""
"<prgn>aptitude</prgn> makes it easy to keep track of obsolete software by "
"listing it under \"Obsolete and Locally Created Packages\"."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:170
msgid ""
"<prgn>aptitude</prgn> includes a fairly powerful system for searching "
"particular packages and limiting the package display. Users familiar with "
"<prgn>mutt</prgn> will pick up quickly, as <prgn>mutt</prgn> was the "
"inspiration for the expression syntax."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:173
msgid ""
"<prgn>aptitude</prgn> can be used to install the predefined tasks available. "
"For more information see <ref id=\"tasksel\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:179
msgid ""
"<prgn>aptitude</prgn> in full screen mode has <prgn>su</prgn> functionality "
"embedded and can be run by a normal user. It will call <prgn>su</prgn> (and "
"ask for the root password, if any) when you really need administrative "
"privileges"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:187
msgid ""
"You can use <prgn>aptitude</prgn> through a visual interface (simply run "
"<tt>aptitude</tt>) or directly from the command line. The command line "
"syntax used is very similar to the one used in <prgn>apt-get</prgn>. For "
"example, to install the <var>foo</var> package, you can run <tt>aptitude "
"install <var>foo</var></tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:190
msgid ""
"Note that <prgn>aptitude</prgn> is the preferred program for daily package "
"management from console."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:194
msgid ""
"For more informations, read the manual page <manref section=\"8\" name="
"\"aptitude\"> and install the <package>aptitude-doc</package> package."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:196
msgid "synaptic"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:209
msgid ""
"<prgn>synaptic</prgn> is a graphical package manager. It enables you to "
"install, upgrade and remove software packages in a user friendly way. Next "
"to all features offered by aptitude, it also has a feature for editing the "
"list of used repositories, and supports browsing all available documentation "
"related to a package. See the <url id=\"http://www.nongnu.org/synaptic/\" "
"name=\"Synaptic Website\"> for more information."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:211
msgid "tasksel"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:218
msgid ""
"When you want to perform a specific task it might be difficult to find the "
"appropiate suite of packages that fill your need. The Debian developers have "
"defined <tt>tasks</tt>, a task is a collection of several individual Debian "
"packages all related to a specific activity. Tasks can be installed through "
"the <prgn>tasksel</prgn> program or through <prgn>aptitude</prgn>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:228
msgid ""
"The Debian installer will typically install automaticaly the task associated "
"with a standard system and a desktop environment. The specific desktop "
"environment installed will depend on the CD/DVD media used, most commonly it "
"will be the GNOME desktop (<tt>gnome-desktop</tt> task). Also, depending on "
"your selections throughout the installation process, tasks might be "
"automatically installed in your system. For example, if you selected a "
"language, the task associated with it will be installed automatically too "
"and if you are running in a laptop system the installer recognises the "
"<tt>laptop</tt> task will be installed too."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:230
msgid "Other package management tools"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:232
msgid "dselect"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:240
msgid ""
"This program is a menu-driven interface to the Debian package management "
"system. For woody and earlier releases, this was the main package management "
"interface for for first-time installations, but currently users are "
"encouraged to use <prgn>aptitude</prgn> instead. Some users might feel more "
"comfortable using <prgn>aptitude</prgn> and it is also recommended over "
"<prgn>dselect</prgn> for large-scale upgrades. For more information on "
"<prgn>aptitude</prgn> please see <ref id=\"aptitude\">."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:49 pkgtools.sgml:241
msgid "<prgn>dselect</prgn> can:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:245
msgid ""
"guide the user as he/she chooses among packages to install or remove, "
"ensuring that no packages are installed that conflict with one another, and "
"that all packages required to make each package work properly are installed;"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:247
msgid ""
"warn the user about inconsistencies or incompatibilities in their selections;"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:248
msgid "determine the order in which the packages must be installed;"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:249
msgid "automatically perform the installation or removal; and"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:252
msgid ""
"guide the user through whatever configuration process are required for each "
"package."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:259
msgid ""
"<prgn>dselect</prgn> begins by presenting the user with a menu of 7 items, "
"each of which is a specific action. The user can select one of the actions "
"by using the arrow keys to move the highlighter bar, then pressing the "
"<em>&lt;enter&gt;</em> key to select the highlighted action."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:266
msgid ""
"What the user sees next depends on the action he selected. If he selects any "
"option but <tt>Access</tt> or <tt>Select</tt>, then <prgn>dselect</prgn> "
"will simply proceed to execute the specified action: e.g., if the user "
"selected the action <tt>Remove</tt>, then dselect would proceed to remove "
"all of the files selected for removal when the user last chose the "
"<tt>Select</tt> action."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:271
msgid ""
"Both the <tt>Access</tt> menu item and the <tt>Select</tt> menu item lead to "
"additional menus. In both cases, the menus are presented as split screens; "
"the top screen gives a scrollable list of choices, while the bottom screen "
"gives a brief explanation (\"info\") for each choice."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:274
msgid ""
"Extensive on-line help is available, use the '?' key to get to a help screen "
"at any time."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:49 pkgtools.sgml:280
msgid ""
"The order in which the actions are presented in the first <prgn>dselect</"
"prgn> menu represents the order in which a user would normally choose "
"<prgn>dselect</prgn> to install packages. However, a user can pick any of "
"the main menu choices as often as needed (including not at all, depending on "
"what one wants to do)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:287
msgid ""
"Begin by choosing an <strong>Access Method</strong>. This is the method by "
"which the user plans on accessing Debian packages; e.g., some users have "
"Debian packages available on CD-ROM, while others plan to fetch them using "
"anonymous FTP. The selected \"Access Method\" is stored after <prgn>dselect</"
"prgn> exits, so if it does not change, then this option need not be invoked "
"again."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:293
msgid ""
"Then <strong>Update</strong> the list of available packages. To do this, "
"<prgn>dselect</prgn> reads the file \"Packages.gz\" which should be included "
"in the top level of the directory where the Debian packages to be installed "
"are stored. (But if it is not there, <prgn>dselect</prgn> will offer to make "
"it for you.)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:299
msgid ""
"<strong>Select</strong> specific packages for installation on his system. "
"After choosing this menu item, the user is first presented with a full "
"screen of help (unless the `--expert' command line option was used). Once "
"the user exits the Help screen, he sees the split-screen menu for choosing "
"packages to install (or remove)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:304
msgid ""
"The top part of the screen is a relatively narrow window into the list of "
"Debian's &all-pkgs; packages; the bottom part of the screen contains "
"description of the package or group of packages which are highlighted above."
msgstr ""

#. type: <p><taglist>
#: debian-faq.sgml:49 pkgtools.sgml:307
msgid ""
"One can specify which packages should be operated on by highlighting a "
"package name or the label for a group of packages. After that, you can "
"select packages:"
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:49 pkgtools.sgml:309
msgid "to be installed:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:310
msgid "This is accomplished by pressing the `+' key."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:49 pkgtools.sgml:311
msgid "to be deleted:"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:49 pkgtools.sgml:312
msgid "Packages can be deleted two ways:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:317
msgid ""
"removed: this removes most of the files associated with the package, but "
"preserves the files listed as configuration files (see <ref id=\"conffile"
"\">) and package configuration information. This is done by pressing the `-' "
"key."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:319
msgid ""
"purged: this removes <em>every</em> file that is part of the package. This "
"is done by pressing the `_' key."
msgstr ""

#. type: </list></p>
#: debian-faq.sgml:49 pkgtools.sgml:323
msgid ""
"Note that it's not possible to remove \"All Packages\". If you try that, "
"your system will instead be reduced to the initial installed base packages."
msgstr ""

#. type: <tag></tag>
#: debian-faq.sgml:49 pkgtools.sgml:324
msgid "to be put \"on hold\""
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:330
msgid ""
"This is done by pressing `=', and it effectively tells <prgn>dselect</prgn> "
"not to upgrade a package even if the version currently installed on your "
"system is not as recent as the version that is available in the Debian "
"repository you are using (this was specified when you set the <strong>Access "
"Method</strong>, and acquired when you used <strong>Update</strong>)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:334
msgid ""
"Just like you can put a package on hold, you can reverse such setting by "
"pressing `:'. That tells <prgn>dselect</prgn> that the package(s) may be "
"upgraded if a newer version is available. This is the default setting."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:345
msgid ""
"You can select a different order in which the packages are presented, by "
"using the `o' key to cycle between various options for sorting the packages. "
"The default order is to present packages by Priority; within each priority, "
"packages are presented in order of the directory (a.k.a. section) of the "
"archive in which they are stored. Given this sort order, some packages in "
"section A (say) may be presented first, followed by some packages in section "
"B, followed by more packages (of lower priority) in section A."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:350
msgid ""
"You can also expand meanings of the labels at the top of the screen, by "
"using the `v' (verbose) key. This action pushes much of the text that "
"formerly fit onto the display off to the right. To see it, press the right "
"arrow; to scroll back to the left, press the left arrow."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:359
msgid ""
"If you select a package for installation or removal, e.g., <package>foo.deb</"
"package>, and that package depends on (or recommends) another package, e.g., "
"<package>blurf.deb</package>, then <prgn>dselect</prgn> will place the you "
"in a sub-screen of the main selection screen. There you can choose among the "
"related packages, accepting the suggested actions (to install or not), or "
"rejecting them. To do the latter, press Shift-D; to return to the former, "
"press Shift-U. In any case, you can save your selections and return to the "
"main selection screen by pressing Shift-Q."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:365
msgid ""
"Users returning to the main menu can then select the \"Install\" menu item "
"to unpack and configure the selected packages. Alternatively, users wishing "
"to remove files can choose the \"Remove\" menu item. At any point, users can "
"choose \"Quit\" to exit dselect; users' selections are preserved by "
"<prgn>dselect</prgn>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:369
msgid "dpkg-deb"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:49 pkgtools.sgml:371
msgid ""
"This program manipulates Debian archive(<tt>.deb</tt>) files. Some common "
"uses are:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:372
msgid "Find out all the options: <tt>dpkg-deb --help</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:374
msgid ""
"Determine what files are contained in a Debian archive file: <tt>dpkg-deb --"
"contents foo_VVV-RRR.deb</tt>)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:380
msgid ""
"Extract the files contained in a named Debian archive into a user specified "
"directory: <tt>dpkg-deb --extract foo_VVV-RRR.deb tmp</tt> extracts each of "
"the files in <tt>foo_VVV-RRR.deb</tt> into the directory <tt>tmp/</tt>. This "
"is convenient for examining the contents of a package in a localized "
"directory, without installing the package into the root file system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:383
msgid ""
"Extract the control information files from a package: <tt>dpkg-deb --control "
"foo_VVV-RRR.deb tmp</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:389
msgid ""
"Note that any packages that were merely unpacked using <tt>dpkg-deb --"
"extract</tt> will be incorrectly installed, you should use <tt>dpkg --"
"install</tt> instead."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:392
msgid ""
"More information is given in the manual page <manref section=\"1\" name="
"\"dpkg-deb\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:394
msgid "dpkg-split"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:400
msgid ""
"This program splits large package into smaller files (e.g., for writing onto "
"a set of floppy disks), and can also be used to merge a set of split files "
"back into a single file. It can only be used on a Debian system (i.e. a "
"system containing the <package>dpkg</package> package), since it calls the "
"program <tt>dpkg-deb</tt> to parse the debian package file into its "
"component records."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:49 pkgtools.sgml:401
msgid "For example, to split a big .deb file into N parts,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:404
msgid ""
"Execute the command <tt>dpkg-split --split foo.deb</tt>. This will produce N "
"files each of approximately 460 KBytes long in the current directory."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:405
msgid "Copy those N files to floppy disks."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:407
msgid ""
"Copy the contents of the floppy disks onto the hard disk of your choice on "
"the other machine."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:409
msgid ""
"Join those part-files together using <tt>dpkg-split --join \"foo*\"</tt>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:416
msgid ""
"Debian claims to be able to update a running program; how is this "
"accomplished?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:419
msgid ""
"The kernel (file system) in &debian; systems supports replacing files even "
"while they're being used."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:425
msgid ""
"We also provide a program called <prgn>start-stop-daemon</prgn> which is "
"used to start daemons at boot time or to stop daemons when the runlevel is "
"changed (e.g., from multi-user to single-user or to halt). The same program "
"is used by installation scripts when a new package containing a daemon is "
"installed, to stop running daemons, and restart them as necessary."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:428
msgid "How can I tell what packages are already installed on a Debian system?"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:429
msgid ""
"To learn the status of all the packages installed on a Debian system, "
"execute the command"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:428
#, no-wrap
msgid "dpkg --list"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:49 pkgtools.sgml:436
msgid ""
"This prints out a one-line summary for each package, giving a 2-letter "
"status symbol (explained in the header), the package name, the version which "
"is <em>installed</em>, and a brief description."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:437
msgid ""
"To learn the status of packages whose names match the string any pattern "
"beginning with \"foo\" by executing the command:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:436
#, no-wrap
msgid "dpkg --list 'foo*'"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:441
msgid ""
"To get a more verbose report for a particular package, execute the command:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:440
#, no-wrap
msgid "dpkg --status packagename"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:446
msgid "How to display the files of a package installed?"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:447
msgid ""
"To list all the files provided by the installed package <tt>foo</tt> execute "
"the command"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:446
#, no-wrap
msgid "dpkg --listfiles foo"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:452
msgid ""
"Note that the files created by the installation scripts aren't displayed."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:455
msgid "How can I find out what package produced a particular file?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:49 pkgtools.sgml:458
msgid ""
"To identify the package that produced the file named <tt>foo</tt> execute "
"either:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:459
msgid "<tt>dpkg --search filename</tt>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:465
msgid ""
"This searches for <tt>filename</tt> in installed packages. (This is "
"(currently) equivalent to searching all of the files having the file "
"extension of <tt>.list</tt> in the directory <tt>/var/lib/dpkg/info/</tt>, "
"and adjusting the output to print the names of all the packages containing "
"it, and diversions.)"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:49 pkgtools.sgml:466
msgid "A faster alternative to this is the <prgn>dlocate</prgn> tool."
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:49 pkgtools.sgml:459
#, no-wrap
msgid "dlocate -S  filename"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:469
msgid "<tt>zgrep foo Contents-ARCH.gz</tt>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:478
msgid ""
"This searches for files which contain the substring <tt>foo</tt> in their "
"full path names. The files <tt>Contents-ARCH.gz</tt> (where ARCH represents "
"the wanted architecture) reside in the major package directories (main, non-"
"free, contrib) at a Debian FTP site (i.e. under <tt>/debian/dists/"
"&releasename;</tt>). A <tt>Contents</tt> file refers only to the packages in "
"the subdirectory tree where it resides. Therefore, a user might have to "
"search more than one <tt>Contents</tt> files to find the package containing "
"the file <tt>foo</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:482
msgid ""
"This method has the advantage over <tt>dpkg --search</tt> in that it will "
"find files in packages that are not currently installed on your system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:483
msgid "<tt>apt-file search <var>foo</var></tt>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:491
msgid ""
"If you install the <package>apt-file</package>, similar to the above, it "
"searches files which contain the substring or regular expression <tt>foo</"
"tt> in their full path names. The advantage over the sample above is that "
"there is no need to retrieve the <tt>Contents-ARCH.gz</tt> files as it will "
"do this automatically for all the sources defined in <file>/etc/apt/sources."
"list</file> when you run (as root) <tt>apt-file update</tt>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:49 pkgtools.sgml:497
msgid ""
"Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make "
"sure old unused library-packages get purged?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:504
msgid ""
"Some packages are split in program (`foo') and data (`foo-data') (or in "
"`foo' and `foo-doc'). This is true for many games, multimedia applications "
"and dictionaries in Debian and has been introduced since some users might "
"want to access the raw data without installing the program or because the "
"program can be run without the data itself, making it optional."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:49 pkgtools.sgml:511
msgid ""
"Similar situations occur when dealing with libraries: generally these get "
"installed since packages containing applications depend on them. When the "
"application-package is purged, the library-package might stay on the system. "
"Or: when the application-package no longer depends upon e.g. libdb4.2, but "
"upon libdb4.3, the libdb4.2 package might stay when the application-package "
"is upgraded."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:3
msgid ""
"In these cases, `foo-data' doesn't depend on `foo', so when you remove the "
"`foo' package it will not get automatically removed by most package "
"management tools. The same holds true for the library packages. This is "
"necessary to avoid circular dependencies. If you use <prgn>aptitude</prgn> "
"(see <ref id=\"aptitude\">) as your package management tool it will, "
"however, track automatically installed packages and remove them when no "
"packages remain that need them in your system."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:50 uptodate.sgml:5
msgid "Keeping your Debian system up-to-date"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:11
msgid ""
"A Debian goal is to provide a consistent upgrade path and a secure upgrade "
"process. We always do our best to make upgrading to new releases a smooth "
"procedure. In case there's some important note to add to the upgrade "
"process, the packages will alert the user, and often provide a solution to a "
"possible problem."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:18
msgid ""
"You should also read the Release Notes document that describes the details "
"of specific upgrades. It is available on the Debian website at <url id="
"\"http://www.debian.org/releases/stable/releasenotes\"> and is also shipped "
"on the Debian CDs, DVDs and Blu-Ray discs"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:50 uptodate.sgml:20
msgid "How can I keep my Debian system current?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:28
msgid ""
"One could simply execute an anonymous ftp call to a Debian archive, then "
"peruse the directories until one finds the desired file, and then fetch it, "
"and finally install it using <tt>dpkg</tt>. Note that <tt>dpkg</tt> will "
"install upgrade files in place, even on a running system. Sometimes, a "
"revised package will require the installation of a newly revised version of "
"another package, in which case the installation will fail until/unless the "
"other package is installed."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:34
msgid ""
"Many people find this approach much too time-consuming, since Debian evolves "
"so quickly -- typically, a dozen or more new packages are uploaded every "
"week. This number is larger just before a new major release. To deal with "
"this avalanche, many people prefer to use a more automated method. Several "
"different packages are available for this purpose:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:42
msgid ""
"APT is an advanced interface to the Debian packaging system. It features "
"complete installation ordering, multiple source capability and several other "
"unique features, see the User's Guide in <tt>/usr/share/doc/apt-doc/guide."
"html/index.html</tt> (you will have to install the <tt>apt-doc</tt> package)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:46
msgid ""
"<prgn>aptitude</prgn> is the recommended package manager for &debian; "
"systems. It is a text-based interface to APT using the curses library, and "
"can be used to perform management tasks in a fast and easy way."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:50 uptodate.sgml:51
msgid ""
"Before you can use <prgn>aptitude</prgn>, you'll have to edit the <tt>/etc/"
"apt/sources.list</tt> file to set it up. If you wish to upgrade to the "
"latest stable version of Debian, you'll probably want to use a source like "
"this one:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:50 uptodate.sgml:46
#, no-wrap
msgid "http://ftp.us.debian.org/debian stable main contrib non-free"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:57
msgid ""
"You can replace ftp.us.debian.org with the name of a faster Debian mirror "
"near you. See the mirror list at <url id=\"http://www.debian.org/mirror/list"
"\"> for more information."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:60
msgid ""
"More details on this can be found in the <manref section=\"8\" name="
"\"sources.list\"> manual page."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:50 uptodate.sgml:60
msgid "To update your system, run"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:50 uptodate.sgml:60 uptodate.sgml:109
#, no-wrap
msgid "aptitude update"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:50 uptodate.sgml:62 uptodate.sgml:80 uptodate.sgml:112
msgid "followed by"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:50 uptodate.sgml:60 uptodate.sgml:109
#, no-wrap
msgid "aptitude dist-upgrade"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:50 uptodate.sgml:68
msgid ""
"Answer any questions that might come up, and your system will be upgraded. "
"See also <ref id=\"aptitude\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:50 uptodate.sgml:70
msgid "apt-get, dselect and apt-cdrom"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:74
msgid ""
"<prgn>apt-get</prgn> is an APT-based command-line tool for handling "
"packages, and the APT dselect method is an interface to APT through "
"<prgn>dselect</prgn>. Both of these provide a simple, safe way to install "
"and upgrade packages."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:78
msgid ""
"To use <prgn>apt-get</prgn>, install the <package>apt</package> package, and "
"edit the <tt>/etc/apt/sources.list</tt> file to set it up, just as for <ref "
"id=\"aptitude-upgrade\">."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:50 uptodate.sgml:78
msgid "Then run"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:50 uptodate.sgml:86
msgid ""
"Answer any questions that might come up, and your system will be upgraded. "
"See also the <manref section=\"8\" name=\"apt-get\"> manual page, as well as "
"<ref id=\"apt-get\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:91
msgid ""
"To use APT with <prgn>dselect</prgn>, choose the APT access method in "
"dselect's method selection screen (option 0) and then specify the sources "
"that should be used. The configuration file is <file>/etc/apt/sources.list</"
"file>. See also <ref id=\"dselect\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:95
msgid ""
"If you want to use CDs to install packages, you can use <prgn>apt-cdrom</"
"prgn>. For details, please see the Release Notes, section \"Setting up for "
"an upgrade from a local mirror\"."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:101
msgid ""
"Please note that when you get and install the packages, you'll still have "
"them kept in your /var directory hierarchy. To keep your partition from "
"overflowing, remember to delete extra files using <tt>apt-get clean</tt> and "
"<tt>apt-get autoclean</tt>, or to move them someplace else (hint: use "
"<package>apt-move</package>)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:109
msgid ""
"<prgn>aptitude</prgn> is a text-based interface to the Debian package "
"system. It allows the user to view the list of packages and to perform "
"package management tasks such as installing, upgrading, and removing "
"packages (see <ref id=\"aptitude\">). Actions may be performed from a visual "
"interface or from the command-line."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:50 uptodate.sgml:110
msgid ""
"In command line, the actions are similar to that of APT, so to upgrade your "
"system run"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:123
msgid ""
"Note that <prgn>aptitude</prgn> is not the recommended tool for doing "
"upgrades from one &debian; release to another. For upgrades between releases "
"you should read the <url id=\"http://www.debian.org/releases/stable/"
"releasenotes\" name=\"Release Notes\">. This document describes in detail "
"the recommended steps for upgrades from previous releases as well as known "
"issues you should consider before upgrading."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:126
msgid ""
"For details, see the manual page <manref section=\"8\" name=\"aptitude\">, "
"and the file <file>/usr/share/aptitude/README</file>"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:50 uptodate.sgml:128
msgid "mirror"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:132
msgid ""
"This Perl script, and its (optional) manager program called <prgn>mirror-"
"master</prgn>, can be used to fetch user-specified parts of a directory tree "
"from a specified host <em>via</em> anonymous FTP."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:139
msgid ""
"<prgn>mirror</prgn> is particularly useful for downloading large volumes of "
"software. After the first time files have been downloaded from a site, a "
"file called <tt>.mirrorinfo</tt> is stored on the local host. Changes to the "
"remote file system are tracked automatically by <prgn>mirror</prgn>, which "
"compares this file to a similar file on the remote system and downloads only "
"changed files."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:149
msgid ""
"The <prgn>mirror</prgn> program is generally useful for updating local "
"copies of remote directory trees. The files fetched need not be Debian "
"files. (Since <prgn>mirror</prgn> is a Perl script, it can also run on non-"
"Unix systems.) Though the <prgn>mirror</prgn> program provides mechanisms "
"for excluding files names of which match user-specified strings, this "
"program is most useful when the objective is to download whole directory "
"trees, rather than selected packages."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:50 uptodate.sgml:151
msgid "dpkg-mountable"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:156
msgid ""
"dpkg-mountable adds an access method called `mountable' to dselect's list, "
"which allows you to install from any file system specified in /etc/fstab. "
"For example, the archive could be a normal hard disk partition or an NFS "
"server, which it will automatically mount and umount for you if necessary."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:162
msgid ""
"It also has some extra features not found in the standard dselect methods, "
"such as provision for a local file tree (either parallel to the main "
"distribution or totally separate), and only getting packages which are "
"required, rather than the time-consuming recursive directory scan, as well "
"as logging of all dpkg actions in the install method."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:50 uptodate.sgml:165
msgid "Must I go into single user mode in order to upgrade a package?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:169
msgid ""
"No. Packages can be upgraded in place, even in running systems. Debian has a "
"<tt>start-stop-daemon</tt> program that is invoked to stop, then restart "
"running process if necessary during a package upgrade."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:50 uptodate.sgml:172
msgid "Do I have to keep all those .deb archive files on my disk?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:176
msgid ""
"No. If you have downloaded the files to your disk then after you have "
"installed the packages, you can remove them from your system, e.g. by "
"running <tt>aptitude clean</tt>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:50 uptodate.sgml:180
msgid ""
"How can I keep a log of the packages I added to the system? I'd like to know "
"when which package upgrades and removals have occured!"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:50 uptodate.sgml:184
msgid ""
"Passing the <tt>--log</tt>-option to <prgn>dpkg</prgn> makes <prgn>dpkg</"
"prgn> log status change updates and actions. It logs both the <prgn>dpkg</"
"prgn>-invokation (e.g."
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:50 uptodate.sgml:186
#, no-wrap
msgid "2005-12-30 18:10:33 install hello 1.3.18 2.1.1-4"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:50 uptodate.sgml:190
msgid ") and the results (e.g."
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:50 uptodate.sgml:192
#, no-wrap
msgid "2005-12-30 18:10:35 status installed hello 2.1.1-4"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:50 uptodate.sgml:197
msgid ""
") If you'd like to log all your <prgn>dpkg</prgn> invokations (even those "
"done using frontends like <prgn>aptitude</prgn>), you could add"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:50 uptodate.sgml:199
#, no-wrap
msgid "log /var/log/dpkg.log"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:50 uptodate.sgml:205
msgid ""
"to your <file>/etc/dpkg/dpkg.cfg</file>. Be sure the created logfile gets "
"rotated periodically. If you're using <prgn>logrotate</prgn>, this can be "
"achieved by creating a file <file>/etc/logrotate.d/dpkg</file> with contents"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:50 uptodate.sgml:210
#, no-wrap
msgid ""
"/var/log/dpkg {\n"
"  missingok\n"
"  notifempty\n"
"}"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:215
msgid ""
"More details on <prgn>dpkg</prgn> logging can be found in the <manref "
"section=\"1\" name=\"dpkg\"> manual page."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:219
msgid ""
"<prgn>aptitude</prgn> logs the package installations, removals, and upgrades "
"that it intends to perform to <file>/var/log/aptitude</file>. Note that the "
"<em>results</em> of those actions are not recorded in this file!"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:222
msgid ""
"Another way to record your actions is to run your package management session "
"within the <manref section=\"1\" name=\"script\"> program."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:50 uptodate.sgml:224
msgid "Can I automatically update the system?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:228
msgid ""
"Yes. You can use <prgn>cron-apt</prgn>, this tool updates the system at "
"regular interval by using a cron job. By default it just updates the package "
"list and download new packages without installing."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:232
msgid ""
"Note: Automatic upgrade of packages is <strong>NOT</strong> recommended in "
"<em>testing</em> or <em>unstable</em> systems as this might bring unexpected "
"behaviour and remove packages without notice."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:50 uptodate.sgml:235
msgid "I have several machines how can I download the updates only one time?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:238
msgid ""
"If you have more than one Debian machine on your network, it is useful to "
"use <prgn>apt-proxy</prgn> to keep all of your Debian systems up-to-date."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:244
msgid ""
"<prgn>apt-proxy</prgn> reduces the bandwidth requirements of Debian mirrors "
"by restricting the frequency of Packages, Releases and Sources file updates "
"from the back end and only doing a single fetch for any file, independently "
"of the actual request it from the proxy. <prgn>apt-proxy</prgn> "
"automatically builds a Debian HTTP mirror based on requests which pass "
"through the proxy."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:50 uptodate.sgml:247
msgid ""
"For more details, see the apt-proxy homepage at <url id=\"http://apt-proxy."
"sourceforge.net/\">"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:51 kernel.sgml:3
msgid ""
"Of course, you can get the same benefit if you are already using a standard "
"caching proxy and all your systems are configured to use it."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:51 kernel.sgml:5
msgid "Debian and the kernel"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:51 kernel.sgml:8
msgid ""
"Can I install and compile a kernel without some Debian-specific tweaking?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:51 kernel.sgml:10
msgid "Yes."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:51 kernel.sgml:19
msgid ""
"There's only one common catch: the Debian C libraries are built with the "
"most recent <em>stable</em> releases of the <strong>kernel</strong> headers. "
"If you happen to need to compile a program with kernel headers newer than "
"the ones from the stable branch, then you should either upgrade the package "
"containing the headers (<package>libc6-dev</package>), or use the new "
"headers from an unpacked tree of the newer kernel. That is, if the kernel "
"sources are in <file>/usr/src/linux</file>, then you should add <tt>-I/usr/"
"src/linux/include/</tt> to your command line when compiling."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:51 kernel.sgml:22
msgid "What tools does Debian provide to build custom kernels?"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:51 kernel.sgml:26
msgid ""
"Users who wish to (or must) build a custom kernel are encouraged to download "
"the package <package>kernel-package</package>. This package contains the "
"script to build the kernel package, and provides the capability to create a "
"Debian <package>linux-image-<var>version</var></package> package just by "
"running the command"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:51 kernel.sgml:22
#, no-wrap
msgid "make-kpkg --initrd kernel_image"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:51 kernel.sgml:29
msgid ""
"in the top-level kernel source directory. Help is available by executing the "
"command"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:51 kernel.sgml:22
#, no-wrap
msgid "make-kpkg --help"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:51 kernel.sgml:33
msgid "and through the manual page <manref section=\"1\" name=\"make-kpkg\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:51 kernel.sgml:39
msgid ""
"Users must separately download the source code for the most recent kernel "
"(or the kernel of their choice) from their favorite Linux archive site, "
"unless a <package>linux-source-<var>version</var></package> package is "
"available (where <var>version</var> stands for the kernel version)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:51 kernel.sgml:42
msgid ""
"Detailed instructions for using the <package>kernel-package</package> "
"package are given in the file <file>/usr/share/doc/kernel-package/README.gz</"
"file>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:51 kernel.sgml:44
msgid "How can I make a custom boot floppy?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:51 kernel.sgml:53
msgid ""
"This task is greatly aided by the Debian package <package>boot-floppies</"
"package>, normally found in the <tt>admin</tt> section of the Debian FTP "
"archive. Shell scripts in this package produce boot floppies in the "
"<tt>SYSLINUX</tt> format. These are <tt>MS-DOS</tt> formatted floppies whose "
"master boot records have been altered so that they boot Linux directly (or "
"whatever other operating system has been defined in the <file>syslinux.cfg</"
"file> file on the floppy). Other scripts in this package produce emergency "
"root disks and can even reproduce the base disks."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:51 kernel.sgml:57
msgid ""
"You will find more information about this in the <file>/usr/share/doc/boot-"
"floppies/README</file> file after installing the <package>boot-floppies</"
"package> package."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:51 kernel.sgml:60
msgid "What special provisions does Debian provide to deal with modules?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:51 kernel.sgml:70
msgid ""
"Debian's <package>modconf</package> package provides a shell script (<file>/"
"usr/sbin/modconf</file>) which can be used to customize the configuration of "
"modules. This script presents a menu-based interface, prompting the user for "
"particulars on the loadable device drivers in his system. The responses are "
"used to customize the file <file>/etc/modules.conf</file> (which lists "
"aliases, and other arguments that must be used in conjunction with various "
"modules) through files in <file>/etc/modutils/</file>, and <file>/etc/"
"modules</file> (which lists the modules that must be loaded at boot time)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:51 kernel.sgml:75
msgid ""
"Like the (new) <file>Configure.help</file> files that are now available to "
"support the construction of custom kernels, the <package>modconf</package> "
"package comes with a series of help files (in <file>/usr/lib/modules_help/</"
"file>) which provide detailed information on appropriate arguments for each "
"of the modules."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:51 kernel.sgml:78
msgid "Can I safely de-install an old kernel package, and if so, how?"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:51 kernel.sgml:83
msgid ""
"Yes. The <prgn>linux-image-<var>NNN</var>.prerm</prgn> script checks to see "
"whether the kernel you are currently running is the same as the kernel you "
"are trying to de-install. Therefore you can remove unwanted kernel image "
"packages using this command:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:51 kernel.sgml:78
#, no-wrap
msgid "dpkg --purge linux-image-<var>NNN</var>"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:52 customizing.sgml:3
msgid ""
"(replace <var>NNN</var> with your kernel version and revision number, of "
"course)"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:5
msgid "Customizing your installation of &debian;"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:8
msgid "How can I ensure that all programs use the same paper size?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:12
msgid ""
"Install the <package>libpaper1</package> package, and it will ask you for a "
"system-wide default paper size. This setting will be kept in the file <tt>/"
"etc/papersize</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:16
msgid ""
"Users can override the paper size setting using the <tt>PAPERSIZE</tt> "
"environment variable. For details, see the manual page <manref section=\"5\" "
"name=\"papersize\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:19
msgid ""
"How can I provide access to hardware peripherals, without compromising "
"security?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:24
msgid ""
"Many device files in the <tt>/dev</tt> directory belong to some predefined "
"groups. For example, <tt>/dev/fd0</tt> belongs to the <tt>floppy</tt> group, "
"and <tt>/dev/dsp</tt> belongs to the <tt>audio</tt> group."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:52 customizing.sgml:25
msgid ""
"If you want a certain user to have access to one of these devices, just add "
"the user to the group the device belongs to, i.e. do:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:52 customizing.sgml:24
#, no-wrap
msgid "adduser user group"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:52 customizing.sgml:29
msgid "This way you won't have to change the file permissions on the device."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:33
msgid ""
"If you do this from within a user's shell or a GUI environment you have to "
"logout and login again to become an effective member of that group. To check "
"which groups you belong to run <tt>groups</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:38
msgid ""
"Notice that, since the introduction of <tt>udev</tt> if you change the "
"permissions of a hardware peripheral they might be be adjusted for some "
"devices when the system starts, if this happens to the hardware peripherals "
"you are instered in you will have to adjust the rules at <tt>/etc/udev</tt>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:40
msgid "How do I load a console font on startup the Debian way?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:43
msgid ""
"The <package>kbd</package> and <package>console-tools</package> packages "
"support this, edit <tt>/etc/kbd/config</tt> or <tt>/etc/console-tools/"
"config</tt> files."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:46
msgid "How can I configure an X11 program's application defaults?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:52
msgid ""
"Debian's X programs will install their application resource data in the <tt>/"
"etc/X11/app-defaults/</tt> directory. If you want to customize X "
"applications globally, put your customizations in those files. They are "
"marked as configuration files, so their contents will be preserved during "
"upgrades."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:55
msgid ""
"Every distribution seems to have a different boot-up method. Tell me about "
"Debian's."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:67
msgid ""
"Like all Unices, Debian boots up by executing the program <tt>init</tt>. The "
"configuration file for <tt>init</tt> (which is <tt>/etc/inittab</tt>) "
"specifies that the first script to be executed should be <tt>/etc/init.d/"
"rcS</tt>. This script runs all of the scripts in <tt>/etc/rcS.d/</tt> by "
"sourcing or forking subprocess depending on their file extension to perform "
"initialization such as to check and to mount file systems, to load modules, "
"to start the network services, to set the clock, and to perform other "
"initialization. Then, for compatibility, it runs the files (except those "
"with a `.'in the filename) in <tt>/etc/rc.boot/</tt> too. Any scripts in the "
"latter directory are usually reserved for system administrator use, and "
"using them in packages is deprecated."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:52 customizing.sgml:71
msgid ""
"After completing the boot process, <tt>init</tt> executes all start scripts "
"in a directory specified by the default runlevel (this runlevel is given by "
"the entry for <tt>id</tt> in <tt>/etc/inittab</tt>). Like most System V "
"compatible Unices, Linux has 7 runlevels:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:72
msgid "0 (halt the system),"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:73
msgid "1 (single-user mode),"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:74
msgid "2 through 5 (various multi-user modes), and"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:76
msgid "6 (reboot the system)."
msgstr ""

#. type: </list></p>
#: debian-faq.sgml:52 customizing.sgml:81
msgid ""
"Debian systems come with id=2, which indicates that the default runlevel "
"will be '2' when the multi-user state is entered, and the scripts in <tt>/"
"etc/rc2.d/</tt> will be run."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:92
msgid ""
"In fact, the scripts in any of the directories, <tt>/etc/rcN.d/</tt> are "
"just symbolic links back to scripts in <tt>/etc/init.d/</tt>. However, the "
"<em>names</em> of the files in each of the <tt>/etc/rcN.d/</tt> directories "
"are selected to indicate the <em>way</em> the scripts in <tt>/etc/init.d/</"
"tt> will be run. Specifically, before entering any runlevel, all the scripts "
"beginning with 'K' are run; these scripts kill services. Then all the "
"scripts beginning with 'S' are run; these scripts start services. The two-"
"digit number following the 'K' or 'S' indicates the order in which the "
"script is run. Lower numbered scripts are executed first."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:98
msgid ""
"This approach works because the scripts in <tt>/etc/init.d/</tt> all take an "
"argument which can be either `start', `stop', `reload', `restart' or `force-"
"reload' and will then do the task indicated by the argument. These scripts "
"can be used even after a system has been booted, to control various "
"processes."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:52 customizing.sgml:98
msgid "For example, with the argument `reload' the command"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:52 customizing.sgml:98
#, no-wrap
msgid "/etc/init.d/sendmail reload"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:52 customizing.sgml:104
msgid ""
"sends the sendmail daemon a signal to reread its configuration file. (BTW, "
"Debian supplies <prgn>invoke-rc.d</prgn> as a wrapper for invoking the "
"scripts in <tt>/etc/init.d/</tt>.)"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:108
msgid ""
"It looks as if Debian does not use <tt>rc.local</tt> to customize the boot "
"process; what facilities are provided?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:52 customizing.sgml:111
msgid ""
"Suppose a system needs to execute script <tt>foo</tt> on start-up, or on "
"entry to a particular (System V) runlevel. Then the system administrator "
"should:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:112
msgid "Enter the script <tt>foo</tt> into the directory <tt>/etc/init.d/</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:115
msgid ""
"Run the Debian command <tt>update-rc.d</tt> with appropriate arguments, to "
"specify which runlevels should start the service, and which runlevels should "
"stop the service."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:120
msgid ""
"Consider rebooting the system to check that the service starts correctly "
"(assuming that you've asked for it to be started in the default runlevel). "
"Otherwise, manually start it by running `<tt>/etc/init.d/foo start</tt>'."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:135
msgid ""
"One might, for example, cause the script <tt>foo</tt> to execute at boot-up, "
"by putting it in <tt>/etc/init.d/</tt> and running <tt>update-rc.d foo "
"defaults 19</tt>. The argument `<tt>defaults</tt>' refers to the default "
"runlevels, which means (at least in absence of any LSB comment block to the "
"contrary) to start the service in runlevels 2 through 5, and to stop the "
"service in runlevels 0, 1 and 6. (Any LSB Default-Start and Default-Stop "
"directives in <tt>foo</tt> take precedence when using the sysv-rc version of "
"update-rc.d, but are ignored by the current (v0.8.10) file-rc version of "
"update-rc.d.) The argument `<tt>19</tt>' ensures that <tt>foo</tt> is called "
"after all scripts whose number is less than 19 have completed, and before "
"all scripts whose number is 20 or greater."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:138
msgid ""
"How does the package management system deal with packages that contain "
"configuration files for other packages?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:145
msgid ""
"Some users wish to create, for example, a new server by installing a group "
"of Debian packages and a locally generated package consisting of "
"configuration files. This is not generally a good idea, because <prgn>dpkg</"
"prgn> will not know about those configuration files if they are in a "
"different package, and may write conflicting configurations when one of the "
"initial \"group\" of packages is upgraded."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:152
msgid ""
"Instead, create a local package that modifies the configuration files of the "
"\"group\" of Debian packages of interest. Then <prgn>dpkg</prgn> and the "
"rest of the package management system will see that the files have been "
"modified by the local \"sysadmin\" and will not try to overwrite them when "
"those packages are upgraded."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:155
msgid ""
"How do I override a file installed by a package, so that a different version "
"can be used instead?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:159
msgid ""
"Suppose a sysadmin or local user wishes to use a program \"login-local\" "
"rather than the program \"login\" provided by the Debian <package>login</"
"package> package."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:52 customizing.sgml:160
msgid "Do <strong>not</strong>:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:162
msgid "Overwrite <tt>/bin/login</tt> with <tt>login-local</tt>."
msgstr ""

#. type: </list></p>
#: debian-faq.sgml:52 customizing.sgml:167
msgid ""
"The package management system will not know about this change, and will "
"simply overwrite your custom <tt>/bin/login</tt> whenever <tt>login</tt> (or "
"any package that provides <tt>/bin/login</tt>) is installed or updated."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:52 customizing.sgml:168
msgid "Rather, do"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:52 customizing.sgml:169
msgid "Execute:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:52 customizing.sgml:169
#, no-wrap
msgid "dpkg-divert --divert /bin/login.debian /bin/login"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:52 customizing.sgml:173
msgid ""
"in order to cause all future installations of the Debian <package>login</"
"package> package to write the file <tt>/bin/login</tt> to <tt>/bin/login."
"debian</tt> instead."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:52 customizing.sgml:174
msgid "Then execute:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:52 customizing.sgml:169
#, no-wrap
msgid "cp login-local /bin/login"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:52 customizing.sgml:177
msgid "to move your own locally-built program into place."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:182
msgid ""
"Run <tt>dpkg-divert --list</tt> to see which diversions are currently active "
"on your system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:184
msgid ""
"Details are given in the manual page <manref section=\"8\" name=\"dpkg-divert"
"\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:188
msgid ""
"How can I have my locally-built package included in the list of available "
"packages that the package management system knows about?"
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:52 customizing.sgml:190
msgid "Execute the command:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:52 customizing.sgml:192
#, no-wrap
msgid "dpkg-scanpackages BIN_DIR OVERRIDE_FILE [PATHPREFIX] > my_Packages"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:52 customizing.sgml:194
msgid "where:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:197
msgid ""
"BIN-DIR is a directory where Debian archive files (which usually have an "
"extension of \".deb\") are stored."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:201
msgid ""
"OVERRIDE_FILE is a file that is edited by the distribution maintainers and "
"is usually stored on a Debian FTP archive at <tt>indices/override.main.gz</"
"tt> for the Debian packages in the \"main\" distribution. You can ignore "
"this for local packages."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:203
msgid ""
"PATHPREFIX is an <em>optional</em> string that can be prepended to the "
"<tt>my_Packages</tt> file being produced."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:52 customizing.sgml:209
msgid ""
"Once you have built the file <tt>my_Packages</tt>, tell the package "
"management system about it by using the command:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:52 customizing.sgml:211
#, no-wrap
msgid "dpkg --merge-avail my_Packages"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:216
msgid ""
"If you are using APT, you can add the local repository to your <manref "
"section=\"5\" name=\"sources.list\"> file, too."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:52 customizing.sgml:220
msgid ""
"Some users like mawk, others like gawk; some like vim, others like elvis; "
"some like trn, others like tin; how does Debian support diversity?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:226
msgid ""
"There are several cases where two packages provide two different versions of "
"a program, both of which provide the same core functionality. Users might "
"prefer one over another out of habit, or because the user interface of one "
"package is somehow more pleasing than the interface of another. Other users "
"on the same system might make a different choice."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:231
msgid ""
"Debian uses a \"virtual\" package system to allow system administrators to "
"choose (or let users choose) their favorite tools when there are two or more "
"that provide the same basic functionality, yet satisfy package dependency "
"requirements without specifying a particular package."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:241
msgid ""
"For example, there might exist two different versions of newsreaders on a "
"system. The news server package might 'recommend' that there exist <em>some</"
"em> news reader on the system, but the choice of <tt>tin</tt> or <tt>trn</"
"tt> is left up to the individual user. This is satisfied by having both the "
"<package>tin</package> and <package>trn</package> packages provide the "
"virtual package <package>news-reader</package>. <em>Which</em> program is "
"invoked is determined by a link pointing from a file with the virtual "
"package name <tt>/etc/alternatives/news-reader</tt> to the selected file, e."
"g., <tt>/usr/bin/trn</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:247
msgid ""
"A single link is insufficient to support full use of an alternate program; "
"normally, manual pages, and possibly other supporting files must be selected "
"as well. The Perl script <tt>update-alternatives</tt> provides a way of "
"ensuring that all the files associated with a specified package are selected "
"as a system default."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:52 customizing.sgml:247
msgid "For example, to check what executables provide `x-window-manager', run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:52 customizing.sgml:247
#, no-wrap
msgid "update-alternatives --display x-window-manager"
msgstr ""

#. type: </example><example>
#: debian-faq.sgml:52 customizing.sgml:249
msgid "If you want to change it, run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:52 customizing.sgml:247
#, no-wrap
msgid "update-alternatives --config x-window-manager"
msgstr ""

#. type: </example></p>
#: debian-faq.sgml:52 customizing.sgml:254
msgid ""
"And follow the instructions on the screen (basically, press the number next "
"to the entry you'd like better)."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:52 customizing.sgml:257
msgid ""
"If a package doesn't register itself as a window manager for some reason "
"(file a bug if it's in error), or if you use a window manager from /usr/"
"local directory, the selections on screen won't contain your preferred "
"entry. You can update the link through command line options, like this:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:52 customizing.sgml:254
#, no-wrap
msgid ""
"update-alternatives --install /usr/bin/x-window-manager \\\n"
"  x-window-manager /usr/local/bin/wmaker-cvs 50"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:52 customizing.sgml:267
msgid ""
"The first argument to `--install' option is the symlink that points to /etc/"
"alternatives/NAME, where NAME is the second argument. The third argument is "
"the program to which /etc/alternatives/NAME should point to, and the fourth "
"argument is the priority (larger value means the alternative will more "
"probably get picked automatically)."
msgstr ""

#. type: <p><example>
#: debian-faq.sgml:52 customizing.sgml:267
msgid "To remove an alternative you added, simply run:"
msgstr ""

#. type: <example></example>
#: debian-faq.sgml:52 customizing.sgml:267
#, no-wrap
msgid "update-alternatives --remove x-window-manager /usr/local/bin/wmaker-cvs"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:5
msgid "Getting support for &debian;"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:8
msgid "What other documentation exists on and for a Debian system?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:10
msgid ""
"Installation instructions for the current release: see <url id=\"http://www."
"debian.org/releases/stable/installmanual\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:14
msgid ""
"The Debian GNU/Linux reference covers many aspects of system administration "
"through shell-command examples. Basic tutorials, tips, and other information "
"are provided for many different topics ranging from system administration to "
"programming."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:16
msgid ""
"Get it from the <package>debian-reference</package> package, or at <url id="
"\"http://www.debian.org/doc/user-manuals#quick-reference\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:22
msgid ""
"The Debian Policy manual documents the policy requirements for the "
"distribution, i.e. the structure and contents of the Debian archive, several "
"design issues of the operating system etc. It also includes the technical "
"requirements that each package must satisfy to be included in the "
"distribution, and documents the basic technical aspects of Debian binary and "
"source packages."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:24
msgid ""
"Get it from the <package>debian-policy</package> package, or at <url id="
"\"http://www.debian.org/doc/devel-manuals#policy\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:28
msgid ""
"Documentation developed by the Debian Documentation Project. It is available "
"at <url id=\"http://www.debian.org/doc/\"> and includes user guides, "
"administration guides and security guides for the Debian GNU/Linux operating "
"system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:30
msgid ""
"Documentation on installed Debian packages: Most packages have files that "
"are unpacked into <tt>/usr/share/doc/PACKAGE</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:34
msgid ""
"Documentation on the Linux project: The Debian package <package>doc-linux</"
"package> installs all of the most recent versions of the HOWTOs and mini-"
"HOWTOs from the <url id=\"http://www.tldp.org/\" name=\"Linux Documentation "
"Project\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:39
msgid ""
"Unix-style `man' pages: Most commands have manual pages written in the style "
"of the original Unix 'man' files. For instance, to see the manual page for "
"the command `ls', execute <tt>man ls</tt>. Execute <tt>man man</tt> for more "
"information on finding and viewing manual pages."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:53 support.sgml:41
msgid ""
"New Debian users should note that the 'man' pages of many general system "
"commands are not available until they install these packages:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:44
msgid ""
"<tt>man-db</tt>, which contains the <tt>man</tt> program itself, and other "
"programs for manipulating the manual pages."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:46
msgid ""
"<tt>manpages</tt>, which contains the system manual pages. (see <ref id="
"\"nonenglish\">)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:51
msgid ""
"GNU-style `info' pages: User documentation for many commands, particularly "
"GNU tools, is available not in `man' pages, but in `info' files which can be "
"read by the GNU tool <tt>info</tt>, by running <tt>M-x info</tt> within GNU "
"Emacs, or with some other Info page viewer."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:56
msgid ""
"Its main advantage over the original `man' pages are that it is a hypertext "
"system. It does <em>not</em> require the WWW, however; <tt>info</tt> can be "
"run from a plain text console. It was designed by Richard Stallman and "
"preceded the WWW."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:62
msgid ""
"Note that you may access a lot of documentation on your system by using a "
"WWW browser, through `dwww', `dhelp' or `doccentral' commands, found in "
"respective packages, or by using `yelp'."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:65
msgid "Are there any on-line resources for discussing Debian?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:70
msgid ""
"Yes. In fact, the main method of support Debian provides to our users is by "
"the way of e-mail. We'll give some details on that, and mention some other "
"useful resources. Even more resources are listed at the <url id=\"http://www."
"debian.org/support\" name=\"Debian Support webpage\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:72
msgid "Mailing lists"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:75
msgid ""
"There are a lot of <url id=\"http://www.debian.org/MailingLists/\" name="
"\"Debian-related mailing lists\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:79
msgid ""
"On a system with the <package>doc-debian</package> package installed there "
"is a complete list of mailing lists in <file>/usr/share/doc/debian/mailing-"
"lists.txt</file>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:90
msgid ""
"Debian mailing lists are named following the pattern debian-<var>list-"
"subject</var>. Examples are debian-announce, debian-user, debian-news. To "
"subscribe to any list debian-<var>list-subject</var>, send mail to debian-"
"<var>list-subject</var>-request@lists.debian.org with the word \"subscribe\" "
"in the Subject: header. Be sure to remember to add <em>-request</em> to the "
"e-mail address when using this method to subscribe or unsubscribe. Otherwise "
"your e-mail will go to the list itself, which could be embarrassing or "
"annoying, depending on your point of view."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:96
msgid ""
"You can subscribe to mailing lists using the <url id=\"http://www.debian.org/"
"MailingLists/subscribe\" name=\"WWW form\">. You can also un-subscribe using "
"a <url id=\"http://www.debian.org/MailingLists/unsubscribe\" name=\"WWW form"
"\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:99
msgid ""
"The list manager's e-mail address is <email>listmaster@lists.debian.org</"
"email>, in case you have any trouble."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:108
msgid ""
"The mailing lists are public forums. All e-mails sent to the lists are also "
"copied to the public archive, for anybody (even non-subscribers) to browse "
"or search. Please make sure you never send any confidential or unlicensed "
"material to the lists. This includes things like e-mail addresses. Of "
"particular note is the fact that spammers have been known to abuse e-mail "
"addresses posted to our mailing lists. See the <url id=\"http://www.debian."
"org/MailingLists/#disclaimer\" name=\"Mailing Lists Privacy policy\"> for "
"more information."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:111
msgid ""
"Archives of the Debian mailing lists are available via WWW at <url id="
"\"http://lists.debian.org/\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:114
msgid "What is the code of conduct for the mailing lists?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:53 support.sgml:116
msgid "When using the Debian mailing lists, please follow these rules:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:118
msgid ""
"Do not send spam. See the <url id=\"http://www.debian.org/MailingLists/#ads"
"\" name=\"Debian mailing list advertising policy\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:121
msgid ""
"Do not flame; it is not polite. The people developing Debian are all "
"volunteers, donating their time, energy and money in an attempt to bring the "
"Debian project together."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:123
msgid ""
"Do not use foul language; besides, some people receive the lists via packet "
"radio, where swearing is illegal."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:126
msgid ""
"Make sure that you are using the proper list. <em>Never</em> post your (un)"
"subscription requests to the mailing list itself<footnote><p>Use the debian-"
"<var>list-subject</var>-REQUEST@lists.debian.org address for that.</p></"
"footnote>"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:128
msgid "See section <ref id=\"bugreport\"> for notes on reporting bugs."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:132
msgid "Web forums"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:137
msgid ""
"<url id=\"http://debianhelp.org/\" name=\"debianHELP\"> and <url id=\"http://"
"forums.debian.net/\" name=\"Debian User Forums\"> are web forums on which "
"you can submit questions about Debian and have them answered by other users. "
"(These are not officially part of the Debian project.)"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:139
msgid "Wiki"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:143
msgid ""
"Solutions to common problems, howto's, guides, tips and other documentation "
"can be found at the constantly changing <url id=\"http://wiki.debian.org/\" "
"name=\"Debian Wiki\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:145
msgid "Maintainers"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:149
msgid ""
"Users can address questions to individual package maintainers using e-mail. "
"To reach a maintainer of a package called xyz, send e-mail to "
"<em>xyz@packages.debian.org</em>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:151
msgid "Usenet newsgroups"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:158
msgid ""
"Users should post non-Debian-specific questions to one of the Linux USENET "
"groups, which are named comp.os.linux.* or linux.*. There are several lists "
"of Linux Usenet newsgroups and other related resources on the WWW, e.g. on "
"the <url id=\"http://www.linux.org/docs/usenet.html\" name=\"Linux Online\"> "
"and <url id=\"http://www.linuxjournal.com/helpdesk.php\" name=\"LinuxJournal"
"\"> sites."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:161
msgid "Is there a quick way to search for information on &debian;?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:53 support.sgml:164
msgid ""
"There is a variety of search engines that serve documentation related to "
"Debian:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:166
msgid "<url id=\"http://search.debian.org/\" name=\"Debian WWW search site\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:169
msgid ""
"<url id=\"http://groups.google.com/\" name=\"Google Groups\">: a search "
"engine for newsgroups."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:176
msgid ""
"For example, to find out what experiences people have had with finding "
"drivers for Promise controllers under Debian, try searching on the phrase "
"<tt>Promise Linux driver</tt>. This will show you all the postings that "
"contain these strings, i.e. those where people discussed these topics. If "
"you add <tt>Debian</tt> to those search strings, you'll also get the "
"postings specifically related to Debian."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:181
msgid ""
"Any of the common web spidering engines, such as <url id=\"http://www."
"altavista.com/\" name=\"AltaVista\"> or <url id=\"http://www.google.com/\" "
"name=\"Google\">, as long as you use the right search terms."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:185
msgid ""
"For example, searching on the string \"cgi-perl\" gives a more detailed "
"explanation of this package than the brief description field in its control "
"file."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:189
msgid "Are there logs of known bugs?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:193
msgid ""
"Reports on unsolved (and closed) issues are publicly available: Debian "
"promissed to do so by stating \"We will not hide problems\" in the <url id="
"\"http://www.debian.org/social_contract\" name=\"Debian Social Contract\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:197
msgid ""
"The &debian; distribution has a bug tracking system (BTS) which files "
"details of bugs reported by users and developers. Each bug is given a "
"number, and is kept on file. Once it has been dealt with, it is marked as "
"such."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:200
msgid ""
"Copies of this information are available at <url id=\"http://www.debian.org/"
"Bugs/\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:204
msgid ""
"A mail server provides access to the bug tracking system database via e-"
"mail. In order to get the instructions, send an e-mail to request@bugs."
"debian.org with \"help\" in the body."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:53 support.sgml:206
msgid "How do I report a bug in Debian?"
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:53 support.sgml:209
msgid ""
"If you have found a bug in Debian, please read the instructions for "
"reporting a bug in Debian. These instructions can be obtained in one of "
"several ways:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:211
msgid ""
"From the WWW. A copy of the instructions is shown at <url id=\"http://www."
"debian.org/Bugs/Reporting\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:214
msgid ""
"On any Debian system with the <package>doc-debian</package> package "
"installed. The instructions are in the file <file>/usr/share/doc/debian/bug-"
"reporting.txt</file>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:217
msgid ""
"By anonymous FTP. Debian mirror sites contain the instructions in the file "
"<tt>doc/bug-reporting.txt</tt>."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:227
msgid ""
"You can use the package <package>reportbug</package> that will guide you "
"through the reporting process and mail the message to the proper address, "
"with some extra details about your system added automatically. It will also "
"show you a list of bugs already reported to the package you are reporting "
"against in case your bug has been reported previously, so that you can add "
"additional information to the existing bug report."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:3
msgid ""
"Expect to get an automatic acknowledgement of your bug report. It will also "
"be automatically given a bug tracking number, entered into the bug log and "
"forwarded to the debian-bugs-dist mailing list."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:54 contrib.sgml:5
msgid "Contributing to the Debian Project"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:11
msgid ""
"<url id=\"&debian-donation;\" name=\"Donations\"> of time (to develop new "
"packages, maintain existing packages, or provide user support), resources "
"(to mirror the FTP and WWW archives), and money (to pay for new testbeds as "
"well as hardware for the archives) can help the project."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:54 contrib.sgml:13
msgid "How can I become a Debian software developer?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:18
msgid ""
"The development of Debian is open to all, and new users with the right "
"skills and/or the willingness to learn are needed to maintain existing "
"packages which have been \"orphaned\" by their previous maintainers, to "
"develop new packages, and to provide user support."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:22
msgid ""
"The description of becoming a Debian developer can be found at the <url id="
"\"http://www.debian.org/devel/join/newmaint\" name=\"New Member's Corner\"> "
"at the Debian web site."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:54 contrib.sgml:25
msgid "How can I contribute resources to the Debian project?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:31
msgid ""
"Since the project aims to make a substantial body of software rapidly and "
"easily accessible throughout the globe, mirrors are urgently needed. It is "
"desirable but not absolutely necessary to mirror all of the archive. Please "
"visit the <url id=\"http://www.debian.org/mirror/size\" name=\"Debian mirror "
"size\"> page for information on the disk space requirements."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:35
msgid ""
"Most of the mirroring is accomplished entirely automatically by scripts, "
"without any interaction. However, the occasional glitch or system change "
"occurs which requires human intervention."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:40
msgid ""
"If you have a high-speed connection to the Internet, the resources to mirror "
"all or part of the distribution, and are willing to take the time (or find "
"someone) who can provide regular maintenance of the system, then please "
"contact <email>debian-admin@lists.debian.org</email>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:54 contrib.sgml:43
msgid "How can I contribute financially to the Debian project?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:46
msgid ""
"One can make individual donations to one of two organizations that are "
"critical to the development of the Debian project."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:54 contrib.sgml:48
msgid "Software in the Public Interest"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:52
msgid ""
"Software in the Public Interest (SPI) is an IRS 501(c)(3) non-profit "
"organization, formed when FSF withdrew their sponsorship of Debian. The "
"purpose of the organization is to develop and distribute free software."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:60
msgid ""
"Our goals are very much like those of FSF, and we encourage programmers to "
"use the GNU General Public License on their programs. However, we have a "
"slightly different focus in that we are building and distributing a Linux "
"system that diverges in many technical details from the GNU system as "
"originally planned by FSF. We still communicate with FSF, and we cooperate "
"in sending them changes to GNU software and in asking our users to donate to "
"FSF and the GNU project."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:62
msgid "SPI can be reached at: <url id=\"http://www.spi-inc.org/\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:54 contrib.sgml:64
msgid "Free Software Foundation"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:74
msgid ""
"At this time there is no formal connection between Debian and the Free "
"Software Foundation. However, the Free Software Foundation is responsible "
"for some of the most important software components in Debian, including the "
"GNU C compiler, GNU Emacs, and much of the C run-time library that is used "
"by all programs on the system. FSF pioneered much of what free software is "
"today: they wrote the General Public License that is used on much of the "
"Debian software, and they invented the \"GNU\" project to create an entirely "
"free Unix system. Debian should be considered a descendent of the GNU system."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:55 redist.sgml:3
msgid "FSF can be reached at: <url id=\"http://www.fsf.org/\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:55 redist.sgml:5
msgid "Redistributing &debian; in a commercial product"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:55 redist.sgml:7
msgid "Can I make and sell Debian CDs?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:55 redist.sgml:14
msgid ""
"Go ahead. You do not need permission to distribute anything we have "
"<em>released</em>, so that you can master your CD as soon as the beta-test "
"ends. You do not have to pay us anything. Of course, all CD manufacturers "
"must honor the licenses of the programs in Debian. For example, many of the "
"programs are licensed under the GPL, which requires you to distribute their "
"source code."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:55 redist.sgml:18
msgid ""
"Also, we will publish a list of CD manufacturers who donate money, software, "
"and time to the Debian project, and we will encourage users to buy from "
"manufacturers who donate, so it is good advertising to make donations."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:55 redist.sgml:20
msgid "Can Debian be packaged with non-free software?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:55 redist.sgml:24
msgid ""
"Yes. While all the main components of Debian are free software, we provide a "
"non-free directory for programs that are not freely redistributable."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:55 redist.sgml:33
msgid ""
"CD manufacturers <em>may</em> be able to distribute the programs we have "
"placed in that directory, depending on the license terms or their private "
"arrangements with the authors of those software packages. CD manufacturers "
"can also distribute the non-free software they get from other sources on the "
"same CD. This is nothing new: free and commercial software are distributed "
"on the same CD by many manufacturers now. Of course we still encourage "
"software authors to release the programs they write as free software."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:55 redist.sgml:37
msgid ""
"I am making a special Linux distribution for a \"vertical market\". Can I "
"use &debian; for the guts of a Linux system and add my own applications on "
"top of it?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:55 redist.sgml:43
msgid ""
"Yes. Debian-derived distributions are being created both in close "
"cooperation with the Debian project itself and by external parties. One can "
"use the <url id=\"http://cdd.alioth.debian.org/\" name=\"Custom Debian "
"Distributions\"> framework to work together with Debian; <url id=\"http://"
"www.skolelinux.org/\" name=\"Skolelinux\"> is one such project."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:55 redist.sgml:48
msgid ""
"There are several other Debian-derived distributions already on the market, "
"such as Progeny Debian, Linspire, Knoppix and Ubuntu, that are targeted at a "
"different kind of audience than the original &debian; is, but use most of "
"our components in their product."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:55 redist.sgml:53
msgid ""
"Debian also provides a mechanism to allow developers and system "
"administrators to install local versions of selected files in such a way "
"that they will not be overwritten when other packages are upgraded. This is "
"discussed further in the question on <ref id=\"divert\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:55 redist.sgml:56
msgid ""
"Can I put my commercial program in a Debian \"package\" so that it installs "
"effortlessly on any Debian system?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:3
msgid ""
"Go right ahead. The package tool is free software; the packages may or may "
"not be free software, it can install them all."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:56 nexttime.sgml:7
msgid "Changes expected in the next major release of Debian"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:56 nexttime.sgml:9
msgid "Extended support for non-English users"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:12
msgid ""
"Debian already has very good support for non-English users, see <ref id="
"\"nonenglish\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:17
msgid ""
"We hope to find people who will provide support for even more languages, and "
"translate. Some programs already support internationalization, so we need "
"message catalogs translators. Many programs still remain to be properly "
"internationalized."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:20
msgid ""
"The GNU Translation Project <url id=\"ftp://ftp.gnu.org/pub/gnu/ABOUT-NLS\"> "
"works on internationalizing the GNU programs."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:56 nexttime.sgml:21
msgid ""
"Specifically for Debian lenny, we're working on things like the following:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:25
msgid ""
"I18n support in all debconf-using packages: Packages using the Debian "
"configuration management must allow for translation of all messages "
"displayed to the user during package configuration."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:27
msgid ""
"I18n support for package descriptions: Update package management frontends "
"to use the translated descriptions of packages."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:29
msgid ""
"UTF-8 debian/changelog and debian/control. This way, e.g. names of people "
"from asian countries can get typeset the right way in changelogs."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:56 nexttime.sgml:35
msgid "Faster booting: Dependency based boot sequence"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:42
msgid ""
"Work is being done on <url id=\"http://wiki.debian.org/LSBInitScripts/"
"DependencyBasedBoot\" name=\"converting the Debian boot sequence\"> to use "
"dynamic and dependency based ordering instead of hardcoded sequence numbers. "
"Once that's finished, Debian systems will boot much faster."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:56 nexttime.sgml:44
msgid "Improvements in the Debian Installer"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:47
msgid ""
"Lots of work has been done on the Debian Installer, resulting in major "
"improvements. We'll mention just two of them here."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:52
msgid ""
"Starting the installer from Microsoft Windows: It is now possible to start "
"the installer directly from Microsoft Windows without the need to change "
"BIOS settings. Upon insertion of a CD-ROM, DVD-ROM or USB stick, an autorun "
"program will be started, offering a step-by-step process to start the Debian "
"Installer."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:56
msgid ""
"The debian-installer now includes experimental support for installing Debian "
"on systems with Serial ATA RAID."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:56 nexttime.sgml:58
msgid "More architectures"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:56 nexttime.sgml:66
msgid ""
"Complete Debian system on other architectures such as <url id=\"http://wiki."
"debian.org/ArmEabiPort\" name=\"ARM EABI\"> (referred to as \"armel\") (next "
"to the old \"arm\") will likely get supported with lenny. Support for <url "
"id=\"http://wiki.debian.org/SHPort\" name=\"SuperH\"> is expected soon. "
"Notice that even though some architectures are dropped for a given the "
"release there still might be a way to install and upgrade using the latest "
"<tt>sid</tt>."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:56 nexttime.sgml:68
msgid "More kernels"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:3
msgid ""
"In addition to Debian GNU/Hurd, Debian is being ported also to BSD kernels, "
"namely to <url id=\"http://www.debian.org/ports/kfreebsd-gnu/\" name="
"\"FreeBSD\">. This port runs on both AMD64 (\"kfreebsd-amd64\") and "
"traditional Intel (\"kfreebsd-i386\")."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:57 faqinfo.sgml:5
msgid "General information about the FAQ"
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:57 faqinfo.sgml:7
msgid "Authors"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:13
msgid ""
"The first edition of this FAQ was made and maintained by J.H.M. Dassen (Ray) "
"and Chuck Stickelman. Authors of the rewritten &debian; FAQ are Susan G. "
"Kleinmann and Sven Rudolph. After them, the FAQ was maintained by Santiago "
"Vila and, later, by Josip Rodin. The current maintainer is Javier Fernandez-"
"Sanguino."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:57 faqinfo.sgml:14
msgid "Parts of the information came from:"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:15
msgid ""
"The Debian-1.1 release announcement, by <url id=\"http://www.perens.com/\" "
"name=\"Bruce Perens\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:16
msgid ""
"The Linux FAQ, by <url id=\"http://www.chiark.greenend.org.uk/~ijackson/\" "
"name=\"Ian Jackson\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:17
msgid ""
"<url id=\"http://lists.debian.org/\" name=\"Debian Mailing Lists Archives\">,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:19
msgid ""
"the dpkg programmers' manual and the Debian Policy manual (see <ref id="
"\"debiandocs\">)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:20
msgid "many developers, volunteers, and beta testers, and"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:21
msgid "the flaky memories of its authors. :-)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:23
msgid ""
"Kamaraju Kusumanchi's <url id=\"http://people.cornell.edu/pages/kk288/"
"debian_choosing_distribution.html\" name=\"Choosing a Debian distribution FAQ"
"\">, who graciously made it GPL so I could include it as a new chapter (see "
"<ref id=\"choosing\">)"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:28
msgid ""
"The authors would like to thank all those who helped make this document "
"possible."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:31
msgid ""
"All warranties are disclaimed. All trademarks are property of their "
"respective trademark owners."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:57 faqinfo.sgml:33
msgid "Feedback"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:39
msgid ""
"Comments and additions to this document are always welcome. Please send e-"
"mail to <email>doc-debian@packages.debian.org</email>, or submit a wishlist "
"bug report against the <package><url id=\"http://bugs.debian.org/debian-faq"
"\" name=\"debian-faq\"></package> package."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:57 faqinfo.sgml:41
msgid "Availability"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:44
msgid ""
"The latest version of this document can be viewed on the Debian WWW pages at "
"<url id=\"http://www.debian.org/doc/FAQ/\">."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:48
msgid ""
"It is also available for download in plain text, HTML, PostScript and PDF "
"formats at <url id=\"http://www.debian.org/doc/user-manuals#faq\">. Also, "
"there are several translations there."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:52
msgid ""
"This document is available in the <package>debian-faq</package> package. "
"Translations are available in <package>debian-faq-de</package>, "
"<package>debian-faq-fr</package> and other packages."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:57
msgid ""
"The original SGML files used to create this document are also available in "
"<package>debian-faq</package>'s source package, or in SVN at: <tt>svn://svn."
"debian.org/svn/ddp/manuals/trunk/debian-faq</tt> and <url id=\"http://svn."
"debian.org/viewsvn/ddp/manuals/trunk/debian-faq/\">."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:57 faqinfo.sgml:59
msgid "Document format"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:57 faqinfo.sgml:64
msgid ""
"This document was written using the DebianDoc SGML DTD (rewritten from "
"LinuxDoc SGML). DebianDoc SGML systems enables us to create files in a "
"variety of formats from one source, e.g. this document can be viewed as "
"HTML, plain text, TeX DVI, PostScript, PDF, or GNU info."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:58
msgid ""
"Conversion utilities for DebianDoc SGML are available in Debian package "
"<package>debiandoc-sgml</package>."
msgstr ""

#. type: definition of entity &release;
#, no-wrap
msgid "6.0"
msgstr ""

#. type: definition of entity &oldreleasename;
#, no-wrap
msgid "lenny"
msgstr ""

#. type: definition of entity &developers;
#, no-wrap
msgid "880"
msgstr ""

#. type: definition of entity &all-pkgs;
#, no-wrap
msgid "29000"
msgstr ""

#. type: definition of entity &archs;
#, no-wrap
msgid "9"
msgstr ""

#. type: definition of entity &docdate;
#, no-wrap
msgid "17 March 2012"
msgstr ""

#. type: definition of entity &docversion;
#, no-wrap
msgid "5.0.1"
msgstr ""

#. type: <copyrightsummary></copyrightsummary>
#: debian-faq.sgml:19
msgid ""
"Copyright &copy; 1996-2005 by Software in the Public Interest, portions "
"copyright &copy; 2004, 2005, 2006 Kamaraju Kusumanchi"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:66
msgid ""
"Support for the <em>hppa</em> (Hewlett-Packard's PA-RISC machines) and "
"<em>alpha</em> (Compaq/Digital's Alpha systems) were dropped in the Squeeze "
"(Debian 6.0) release for similar reasons. The <em>arm</em> was dropped too "
"in this release, as it was superceded by the <em>armel</em> arquitecture."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:92
msgid ""
"In addittion to these, work is in progress of a <em>hurd-i386</em> port for "
"32-bit PC. This port will use GNU Hurd, the new operating system being put "
"together by the GNU group."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:53
msgid ""
"Other codenames that have been already used are: <tt>buzz</tt> for release "
"1.1, <tt>rex</tt> for release 1.2, <tt>bo</tt> for releases 1.3.x, <tt>hamm</"
"tt> for release 2.0, <tt>slink</tt> for release 2.1, <tt>potato</tt> for "
"release 2.2, <tt>woody</tt> for release 3.0, <tt>sarge</tt> for release 3.1, "
"<tt>etch</tt> for release 4.0, and <tt>lenny</tt> for release 5.0, and "
"<tt>squeeze</tt> for release 6.0."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:66
msgid "<em>lenny</em> was the toy binoculars."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:67
msgid "<em>squeeze</em> was the name for the three-eyed aliens."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:71
msgid ""
"<em>wheezy</em> was the name of the rubber toy penguin with a red bow tie."
msgstr ""

#. type: definition of entity &docdate;
#, no-wrap
msgid "16 May 2011"
msgstr ""

#. type: definition of entity &docversion;
#, no-wrap
msgid "4.0.5"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:28
msgid "<em>alpha</em>: Compaq/Digital's Alpha systems."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:30
msgid "<em>sparc</em>: this covers Sun's SPARC and most UltraSPARC systems."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:33
msgid ""
"<em>powerpc</em>: this covers some IBM/Motorola PowerPC machines, including "
"CHRP, PowerMac and PReP machines."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:35
msgid "<em>arm</em>: ARM and StrongARM machines."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:40
msgid ""
"<em>hppa</em>: Hewlett-Packard's PA-RISC machines (712, C3000, L2000, A500)."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:48
msgid ""
"The development of binary distributions of Debian for Sparc64 (UltraSPARC "
"native) architectures is currently underway."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:55
msgid ""
"Support for the <em>m68k</em> architecture was dropped in this release, "
"because it did not meet the criteria set by the Debian Release Managers. "
"This architecture covers Amigas and ATARIs having a Motorola 680x0 processor "
"for x>=2; with MMU. However, the port is still active and available for "
"installation even if not a part of this official stable release and might be "
"reactivated for future releases."
msgstr ""

#. type: <heading></heading>
#: debian-faq.sgml:45 compat.sgml:212
msgid "Why do my old XFree 2.1 Motif applications crash?"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:45 compat.sgml:216
msgid ""
"You need to install the <package>motifnls</package> package, which provides "
"the XFree-2.1 configuration files needed to allow Motif applications "
"compiled under XFree-2.1 to run under XFree-3.1."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:46 software.sgml:3
msgid ""
"Without these files, some Motif applications compiled on other machines "
"(such as Netscape) may crash when attempting to copy or paste from or to a "
"text field, and may also exhibit other problems."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:3
msgid ""
"Alternatively, use <package>ndiswrapper</package> to use a driver for "
"Windows (if you have one) on your Linux system. See the <url id=\"http://"
"wiki.debian.org/NdisWrapper\" name=\"Debian Wiki ndiswapper page\"> for more "
"information."
msgstr ""

#. type: <p><list>
#: debian-faq.sgml:47 ftparchives.sgml:56
msgid ""
"So far they have been characters taken from the movie \"Toy Story\" by Pixar."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:61
msgid "<em>slink</em> (Slinky Dog (R)) was the toy dog,"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:62
msgid "<em>potato</em> was, of course, Mr. Potato (R),"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:65
msgid "<em>etch</em> was the toy blackboard (Etch-a-Sketch (R)),"
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:47 ftparchives.sgml:71
msgid ""
"<em>Wheezy</em> was the name of the rubber toy penguin with a red bow tie."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:53 support.sgml:108
msgid ""
"The mailing lists are public forums. All e-mails sent to the lists are also "
"copied to the public archive, for anybody (even non-subscribers) to browse "
"or search. Please make sure you never send any confidential or unlicensed "
"material to the lists. This includes things like e-mail addresses. Of "
"particular note is the fact that spammers have been known to abuse e-mail "
"addresses posted to our mailing lists. See the <url id=\"http://www.debian."
"org/MailingLists/index.en.html#disclaimer\" name=\"Mailing Lists Privacy "
"policy\"> for more information."
msgstr ""

#. type: <p></p>
#: debian-faq.sgml:54 contrib.sgml:22
msgid ""
"The description of becoming a Debian developer can be found at the <url id="
"\"http://www.debian.org/devel/join/newmaint\" name=\"New Maintainer's Corner"
"\"> at the Debian web site."
msgstr ""
