From d80c8552b60d499dbec7fb37e09ab8fc4145ce2d Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 23 Sep 2007 10:04:22 +0200 Subject: Adding live-package 0.99.6-1. --- .../common/doc/FAQ/html/ch-basic_defs.en.html | 431 ++++++++++ templates/common/doc/FAQ/html/ch-basic_defs.html | 1 + templates/common/doc/FAQ/html/ch-compat.en.html | 386 +++++++++ templates/common/doc/FAQ/html/ch-compat.html | 1 + .../common/doc/FAQ/html/ch-contributing.en.html | 191 +++++ templates/common/doc/FAQ/html/ch-contributing.html | 1 + .../common/doc/FAQ/html/ch-customizing.en.html | 522 ++++++++++++ templates/common/doc/FAQ/html/ch-customizing.html | 1 + templates/common/doc/FAQ/html/ch-faqinfo.en.html | 210 +++++ templates/common/doc/FAQ/html/ch-faqinfo.html | 1 + .../common/doc/FAQ/html/ch-ftparchives.en.html | 567 +++++++++++++ templates/common/doc/FAQ/html/ch-ftparchives.html | 1 + templates/common/doc/FAQ/html/ch-getting.en.html | 374 ++++++++ templates/common/doc/FAQ/html/ch-getting.html | 1 + templates/common/doc/FAQ/html/ch-kernel.en.html | 311 +++++++ templates/common/doc/FAQ/html/ch-kernel.html | 1 + templates/common/doc/FAQ/html/ch-nexttime.en.html | 149 ++++ templates/common/doc/FAQ/html/ch-nexttime.html | 1 + .../common/doc/FAQ/html/ch-pkg_basics.en.html | 860 +++++++++++++++++++ templates/common/doc/FAQ/html/ch-pkg_basics.html | 1 + templates/common/doc/FAQ/html/ch-pkgtools.en.html | 936 +++++++++++++++++++++ templates/common/doc/FAQ/html/ch-pkgtools.html | 1 + templates/common/doc/FAQ/html/ch-redistrib.en.html | 170 ++++ templates/common/doc/FAQ/html/ch-redistrib.html | 1 + templates/common/doc/FAQ/html/ch-software.en.html | 410 +++++++++ templates/common/doc/FAQ/html/ch-software.html | 1 + templates/common/doc/FAQ/html/ch-support.en.html | 525 ++++++++++++ templates/common/doc/FAQ/html/ch-support.html | 1 + templates/common/doc/FAQ/html/ch-uptodate.en.html | 479 +++++++++++ templates/common/doc/FAQ/html/ch-uptodate.html | 1 + templates/common/doc/FAQ/html/footnotes.en.html | 112 +++ templates/common/doc/FAQ/html/footnotes.html | 1 + templates/common/doc/FAQ/html/index.en.html | 311 +++++++ templates/common/doc/FAQ/html/index.html | 1 + 34 files changed, 6961 insertions(+) create mode 100644 templates/common/doc/FAQ/html/ch-basic_defs.en.html create mode 120000 templates/common/doc/FAQ/html/ch-basic_defs.html create mode 100644 templates/common/doc/FAQ/html/ch-compat.en.html create mode 120000 templates/common/doc/FAQ/html/ch-compat.html create mode 100644 templates/common/doc/FAQ/html/ch-contributing.en.html create mode 120000 templates/common/doc/FAQ/html/ch-contributing.html create mode 100644 templates/common/doc/FAQ/html/ch-customizing.en.html create mode 120000 templates/common/doc/FAQ/html/ch-customizing.html create mode 100644 templates/common/doc/FAQ/html/ch-faqinfo.en.html create mode 120000 templates/common/doc/FAQ/html/ch-faqinfo.html create mode 100644 templates/common/doc/FAQ/html/ch-ftparchives.en.html create mode 120000 templates/common/doc/FAQ/html/ch-ftparchives.html create mode 100644 templates/common/doc/FAQ/html/ch-getting.en.html create mode 120000 templates/common/doc/FAQ/html/ch-getting.html create mode 100644 templates/common/doc/FAQ/html/ch-kernel.en.html create mode 120000 templates/common/doc/FAQ/html/ch-kernel.html create mode 100644 templates/common/doc/FAQ/html/ch-nexttime.en.html create mode 120000 templates/common/doc/FAQ/html/ch-nexttime.html create mode 100644 templates/common/doc/FAQ/html/ch-pkg_basics.en.html create mode 120000 templates/common/doc/FAQ/html/ch-pkg_basics.html create mode 100644 templates/common/doc/FAQ/html/ch-pkgtools.en.html create mode 120000 templates/common/doc/FAQ/html/ch-pkgtools.html create mode 100644 templates/common/doc/FAQ/html/ch-redistrib.en.html create mode 120000 templates/common/doc/FAQ/html/ch-redistrib.html create mode 100644 templates/common/doc/FAQ/html/ch-software.en.html create mode 120000 templates/common/doc/FAQ/html/ch-software.html create mode 100644 templates/common/doc/FAQ/html/ch-support.en.html create mode 120000 templates/common/doc/FAQ/html/ch-support.html create mode 100644 templates/common/doc/FAQ/html/ch-uptodate.en.html create mode 120000 templates/common/doc/FAQ/html/ch-uptodate.html create mode 100644 templates/common/doc/FAQ/html/footnotes.en.html create mode 120000 templates/common/doc/FAQ/html/footnotes.html create mode 100644 templates/common/doc/FAQ/html/index.en.html create mode 120000 templates/common/doc/FAQ/html/index.html (limited to 'templates/common/doc/FAQ/html') diff --git a/templates/common/doc/FAQ/html/ch-basic_defs.en.html b/templates/common/doc/FAQ/html/ch-basic_defs.en.html new file mode 100644 index 000000000..74257067e --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-basic_defs.en.html @@ -0,0 +1,431 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Definitions and overview + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 1 - Definitions and overview +

+ +
+ +

1.1 What is this FAQ?

+ +

+This document gives frequently asked questions (with their answers!) about the +Debian distribution (Debian GNU/Linux 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. +

+ +

+If you can't find what you're looking for in this FAQ, be sure to check out What other documentation exists on and +for a Debian system?, Section 11.1. If even that doesn't help, refer to Feedback, Section 15.2. +

+ +
+ +

1.2 What is Debian GNU/Linux?

+ +

+Debian GNU/Linux is a particular distribution of the Linux operating +system, and numerous packages that run on it. +

+ +

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

+ +

+Debian GNU/Linux 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 GNU/Linux so useful were +developed by the GNU project. +

+ +

+For Debian, free has the GNUish meaning (see the 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. +

+ +

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

+ +

+Debian GNU/Linux is: +

+ + + + +

+Although Debian GNU/Linux 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 I am making a special Linux +distribution for a "vertical market". Can I use Debian GNU/Linux for +the guts of a Linux system and add my own applications on top of it?, Section +13.3 for more information. +

+ +
+ +

1.3 OK, now I know what Debian is... what is Linux?!

+ +

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

+ +

+Besides its kernel, a "Linux" system usually has: +

+ + + +

+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 How +source code compatible is Debian with other Unix systems?, Section 3.3. +

+ +

+For more information about Linux, see Michael K. Johnson's Linux Information +Sheet and Meta-FAQ. +

+ +
+ +

1.4 Does Debian just do GNU/Linux?

+ +

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

+ +

+The oldest porting effort is Debian GNU/Hurd. +

+ +

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

+ +

+Please see http://www.gnu.org/software/hurd/ +for more information about the GNU/Hurd in general, and http://www.debian.org/ports/hurd/ +for more information about Debian GNU/Hurd. +

+ +

+A second effort is the port to a BSD kernel. People are working with both the +NetBSD and the FreeBSD kernels. +

+ +

+See http://www.debian.org/ports/#nonlinux +for more information about these non-linux ports. +

+ +
+ +

1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?

+ +

+These key features distinguish Debian from other Linux distributions: +

+
+
Freedom:
+
+

+As stated in the 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 The Debian Free +Software. +

+
+
+
+
The Debian package maintenance system:
+
+

+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 Basics of the Debian package management system, +Chapter 6). +

+
+
+
+
Open development:
+
+

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

+ +

+More than 1649 volunteer package maintainers are working on over 15400 packages +and improving Debian GNU/Linux. 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 How can I become a Debian software +developer?, Section 12.1. +

+
+
+
+
The Universal Operating System:
+
+

+Debian comes with more than +15400 packages and runs on 11 architectures. This is far +more than is available for any other GNU/Linux distribution. See What types of applications and development +software are available for Debian GNU/Linux?, Section 4.1 for an overview +of the provided software and see On what +hardware architectures/systems does Debian GNU/Linux run?, Section 3.1 for +a description of the supported hardware platforms. +

+
+
+
+
The Bug Tracking System:
+
+

+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 Are there logs of known bugs?, Section +11.4. +

+
+
+
+
The Debian Policy:
+
+

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

+
+
+ +

+For additional information about this, please see our web page about reasons to choose +Debian. +

+ +
+ +

1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?

+ +

+The Debian system builds on the ideals of free software first championed by the +Free Software Foundation and in +particular by Richard +Stallman. FSF's powerful system development tools, utilities, and +applications are also a key part of the Debian system. +

+ +

+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 GNU/Linux", and we are happy to comply +with that request. +

+ +

+The FSF's long-standing objective is to develop a new operating system called +GNU, based on Hurd. Debian is working +with FSF on this system, called Debian GNU/Hurd. +

+ +
+ +

1.7 How does one pronounce Debian and what does this word mean?

+ +

+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.) +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-basic_defs.html b/templates/common/doc/FAQ/html/ch-basic_defs.html new file mode 120000 index 000000000..6bee626aa --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-basic_defs.html @@ -0,0 +1 @@ +ch-basic_defs.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-compat.en.html b/templates/common/doc/FAQ/html/ch-compat.en.html new file mode 100644 index 000000000..24b527de7 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-compat.en.html @@ -0,0 +1,386 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Compatibility issues + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 3 - Compatibility issues +

+ +
+ +

3.1 On what hardware architectures/systems does Debian GNU/Linux run?

+ +

+Debian GNU/Linux 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 Linux +FAQ for details. +

+ +

+The current Debian GNU/Linux release, 3.1, contains a complete, binary +distribution for the following architectures: +

+ +

+i386: this covers PCs 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. +

+ +

+m68k: this covers Amigas and ATARIs having a Motorola 680x0 processor +for x>=2; with MMU. +

+ +

+alpha: Compaq/Digital's Alpha systems. +

+ +

+sparc: this covers Sun's SPARC and most UltraSPARC systems. +

+ +

+powerpc: this covers some IBM/Motorola PowerPC machines, including +CHRP, PowerMac and PReP machines. +

+ +

+arm: ARM and StrongARM machines. +

+ +

+mips: SGI's big-endian MIPS systems, Indy and Indigo2; +mipsel: little-endian MIPS machines, Digital DECstations. +

+ +

+hppa: Hewlett-Packard's PA-RISC machines (712, C3000, L2000, A500). +

+ +

+ia64: Intel IA-64 ("Itanium") computers. +

+ +

+s390: IBM S/390 mainframe systems. +

+ +

+The development of binary distributions of Debian for Sparc64 (UltraSPARC +native) architectures is currently underway. +

+ +

+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 http://www.debian.org/releases/stable/installmanual. +

+ +
+ +

3.2 How compatible is Debian with other distributions of Linux?

+ +

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

+ +

+Debian GNU/Linux adheres to the 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. +

+ +

+Debian GNU/Linux supports software developed for the Linux Standard Base. The LSB is a +specification for allowing the same binary package to be used on multiple +distributions. Packages for the Debian Etch release must not conflict with +requirements of the LSB, v1.3. As of this writing, Debian GNU/Linux is not +formally LSB-certified. However, some Debian derived distributions are. +Discussion and coordination of efforts towards ensuring Debian meets the +requirements of the Linux Standard Base is taking place on the debian-lsb mailing list. +

+ +
+ +

3.3 How source code compatible is Debian with other Unix systems?

+ +

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

+ +

+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.) +

+ +

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

+ +
+ +

3.4 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 GNU/Linux system?

+ +

+Different Linux distributions use different package formats and different +package management programs. +

+
+
You probably can:
+
+

+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 GNU/Linux 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 Alien package +is used to convert between different package formats. +

+
+
+
+
You probably do not want to:
+
+

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

+
+
+
+
A better way:
+
+

+The Linux File System Standard (and therefore Debian GNU/Linux) requires that +subdirectories under /usr/local/ 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. +

+
+
+ +
+ +

3.5 Is Debian able to run my old libc5 programs?

+ +

+Yes. Just install the required libc5 libraries, from the +oldlibs section (containing old packages included for +compatibility with older applications). +

+ +
+ +

3.6 Can Debian be used to compile libc5 programs?

+ +

+Yes. Install libc5-altdev and altgcc packages (from +the oldlibs section). You can find the appropriate libc5-compiled +gcc and g++ in directory +/usr/i486-linuxlibc1/bin. Put them in your $PATH variable to get +make and other programs to execute these first. +

+ +

+Be aware that libc5 environment isn't fully supported by our other packages +anymore. +

+ +
+ +

3.7 How should I install a non-Debian program?

+ +

+Files under the directory /usr/local/ 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 +/usr/local/src/foo. After you compile them, place the binaries in +/usr/local/bin/, the libraries in /usr/local/lib/, +and the configuration files in /usr/local/etc/. +

+ +

+If your programs and/or files really must be placed in some other directory, +you could still store them in /usr/local/, and build the +appropriate symbolic links from the required location to its location in +/usr/local/, e.g., you could make the link +

+ +
+     ln -s /usr/local/bin/foo /usr/bin/foo
+
+ +

+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 What other +documentation exists on and for a Debian system?, Section 11.1). +

+ +
+ +

3.8 Why can't I compile programs that require libtermcap?

+ +

+Debian uses the terminfo database and the ncurses +library of terminal interface routes, rather than the termcap +database and the termcap library. Users who are compiling +programs that require some knowledge of the terminal interface should replace +references to libtermcap with references to +libncurses. +

+ +

+To support binaries that have already been linked with the termcap +library, and for which you do not have the source, Debian provides a package +called termcap-compat. This provides both +libtermcap.so.2 and /etc/termcap. 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 +/etc/termcap file. +

+ +
+ +

3.9 Why can't I install AccelX?

+ +

+AccelX uses the termcap library for installation. See Why can't I compile programs that require libtermcap?, +Section 3.8 above. +

+ +
+ +

3.10 Why do my old XFree 2.1 Motif applications crash?

+ +

+You need to install the motifnls 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. +

+ +

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

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-compat.html b/templates/common/doc/FAQ/html/ch-compat.html new file mode 120000 index 000000000..069644986 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-compat.html @@ -0,0 +1 @@ +ch-compat.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-contributing.en.html b/templates/common/doc/FAQ/html/ch-contributing.en.html new file mode 100644 index 000000000..9ed5a5633 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-contributing.en.html @@ -0,0 +1,191 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Contributing to the Debian Project + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 12 - Contributing to the Debian Project +

+ +
+ +

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

+ +
+ +

12.1 How can I become a Debian software developer?

+ +

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

+ +

+The description of becoming a Debian developer can be found at the New Maintainer's +Corner at the Debian web site. +

+ +
+ +

12.2 How can I contribute resources to the Debian project?

+ +

+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 Debian mirror +size page for information on the disk space requirements. +

+ +

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

+ +

+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 +debian-admin@lists.debian.org. +

+ +
+ +

12.3 How can I contribute financially to the Debian project?

+ +

+One can make individual donations to one of two organizations that are critical +to the development of the Debian project. +

+ +
+ +

12.3.1 Software in the Public Interest

+ +

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

+ +

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

+ +

+SPI can be reached at: http://www.spi-inc.org/. +

+ +
+ +

12.3.2 Free Software Foundation

+ +

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

+ +

+FSF can be reached at: http://www.fsf.org/. +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-contributing.html b/templates/common/doc/FAQ/html/ch-contributing.html new file mode 120000 index 000000000..4185524fd --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-contributing.html @@ -0,0 +1 @@ +ch-contributing.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-customizing.en.html b/templates/common/doc/FAQ/html/ch-customizing.en.html new file mode 100644 index 000000000..fb8988858 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-customizing.en.html @@ -0,0 +1,522 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Customizing your installation of Debian GNU/Linux + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 10 - Customizing your installation of Debian GNU/Linux +

+ +
+ +

10.1 How can I ensure that all programs use the same paper size?

+ +

+Install the libpaper1 package, and it will ask you for a +system-wide default paper size. This setting will be kept in the file +/etc/papersize. +

+ +

+Users can override the paper size setting using the PAPERSIZE +environment variable. For details, see the manual page +papersize(5). +

+ +
+ +

10.2 How can I provide access to hardware peripherals, without compromising security?

+ +

+Many device files in the /dev directory belong to some predefined +groups. For example, /dev/fd0 belongs to the floppy +group, and /dev/dsp belongs to the audio group. +

+ +

+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: +

+ +
+     adduser user group
+
+ +

+This way you won't have to change the file permissions on the device. +

+ +
+ +

10.3 How do I load a console font on startup the Debian way?

+ +

+The kbd and console-tools packages support this, edit +/etc/kbd/config or /etc/console-tools/config files. +

+ +
+ +

10.4 How can I configure an X11 program's application defaults?

+ +

+Debian's X programs will install their application resource data in the +/etc/X11/app-defaults/ 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. +

+ +
+ +

10.5 Every distribution seems to have a different boot-up method. Tell me about Debian's.

+ +

+Like all Unices, Debian boots up by executing the program init. +The configuration file for init (which is +/etc/inittab) specifies that the first script to be executed +should be /etc/init.d/rcS. This script runs all of the scripts in +/etc/rcS.d/ 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 /etc/rc.boot/ too. +Any scripts in the latter directory are usually reserved for system +administrator use, and using them in packages is deprecated. +

+ +

+After completing the boot process, init executes all start scripts +in a directory specified by the default runlevel (this runlevel is given by the +entry for id in /etc/inittab). Like most System V +compatible Unices, Linux has 7 runlevels: +

+ + + + + +

+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 +/etc/rc2.d/ will be run. +

+ +

+In fact, the scripts in any of the directories, /etc/rcN.d/ are +just symbolic links back to scripts in /etc/init.d/. However, the +names of the files in each of the /etc/rcN.d/ directories +are selected to indicate the way the scripts in +/etc/init.d/ 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. +

+ +

+This approach works because the scripts in /etc/init.d/ 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. +

+ +

+For example, with the argument `reload' the command +

+ +
+     /etc/init.d/sendmail reload
+
+ +

+sends the sendmail daemon a signal to reread its configuration file. (BTW, +Debian supplies invoke-rc.d as a wrapper for invoking the scripts +in /etc/init.d/.) +

+ +
+ +

10.6 It looks as if Debian does not use rc.local to customize the boot process; what facilities are provided?

+ +

+Suppose a system needs to execute script foo on start-up, or on +entry to a particular (System V) runlevel. Then the system administrator +should: +

+ + + + +

+The command update-rc.d will set up links between files in the +directories rc?.d and the script in /etc/init.d/. Each link will +begin with a 'S' or a 'K', followed by a number, followed by the name of the +script. Scripts beginning with 'S' in /etc/rcN.d/ are executed +when runlevel N is entered. Scripts beginning with a 'K' are +executed when leaving runlevel N. +

+ +

+One might, for example, cause the script foo to execute at +boot-up, by putting it in /etc/init.d/ and installing the links +with update-rc.d foo defaults 19. The argument 'defaults' refers +to the default runlevels, which are 2 through 5. The argument '19' ensures +that foo is called before any scripts containing numbers 20 or +larger. +

+ +
+ +

10.7 How does the package management system deal with packages that contain configuration files for other packages?

+ +

+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 dpkg 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. +

+ +

+Instead, create a local package that modifies the configuration files of the +"group" of Debian packages of interest. Then dpkg 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. +

+ +
+ +

10.8 How do I override a file installed by a package, so that a different version can be used instead?

+ +

+Suppose a sysadmin or local user wishes to use a program +"login-local" rather than the program "login" provided by +the Debian login package. +

+ +

+Do not: +

+ + +

+The package management system will not know about this change, and will simply +overwrite your custom /bin/login whenever login (or +any package that provides /bin/login) is installed or updated. +

+ +

+Rather, do +

+ + + +

+Details are given in the manual page dpkg-divert(8). +

+ +
+ +

10.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?

+ +

+Execute the command: +

+ +
+     dpkg-scanpackages BIN_DIR OVERRIDE_FILE [PATHPREFIX] > my_Packages
+
+ +

+where: +

+ + + + +

+Once you have built the file my_Packages, tell the package +management system about it by using the command: +

+ +
+     dpkg --merge-avail my_Packages
+
+ +

+If you are using APT, you can add the local repository to your +sources.list(5) file, too. +

+ +
+ +

10.10 Some users like mawk, others like gawk; some like vim, others like elvis; some like trn, others like tin; how does Debian support diversity?

+ +

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

+ +

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

+ +

+For example, there might exist two different versions of newsreaders on a +system. The news server package might 'recommend' that there exist +some news reader on the system, but the choice of tin or +trn is left up to the individual user. This is satisfied by +having both the tin and trn packages provide the +virtual package news-reader. Which program is invoked is +determined by a link pointing from a file with the virtual package name +/etc/alternatives/news-reader to the selected file, e.g., +/usr/bin/trn. +

+ +

+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 update-alternatives provides a way of +ensuring that all the files associated with a specified package are selected as +a system default. +

+ +

+For example, to check what executables provide `x-window-manager', run: +

+ +
+     update-alternatives --display x-window-manager
+
+ +

+If you want to change it, run: +

+ +
+     update-alternatives --config x-window-manager
+
+ +

+And follow the instructions on the screen (basically, press the number next to +the entry you'd like better). +

+ +

+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: +

+ +
+     update-alternatives --install /usr/bin/x-window-manager \
+       x-window-manager /usr/local/bin/wmaker-cvs 50
+
+ +

+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). +

+ +

+To remove an alternative you added, simply run: +

+ +
+     update-alternatives --remove x-window-manager /usr/local/bin/wmaker-cvs
+
+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-customizing.html b/templates/common/doc/FAQ/html/ch-customizing.html new file mode 120000 index 000000000..1cfdfaae7 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-customizing.html @@ -0,0 +1 @@ +ch-customizing.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-faqinfo.en.html b/templates/common/doc/FAQ/html/ch-faqinfo.en.html new file mode 100644 index 000000000..6fdb982a7 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-faqinfo.en.html @@ -0,0 +1,210 @@ + + + + + + + + +The Debian GNU/Linux FAQ - General information about the FAQ + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 15 - General information about the FAQ +

+ +
+ +

15.1 Authors

+ +

+The first edition of this FAQ was made and maintained by J.H.M. Dassen (Ray) +and Chuck Stickelman. Authors of the rewritten Debian GNU/Linux 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. +

+ +

+Parts of the information came from: +

+ + + + + + + +

+The authors would like to thank all those who helped make this document +possible. +

+ +

+All warranties are disclaimed. All trademarks are property of their respective +trademark owners. +

+ +
+ +

15.2 Feedback

+ +

+Comments and additions to this document are always welcome. Please send e-mail +to doc-debian@packages.debian.org, +or submit a wishlist bug report against the doc-debian package. +

+ +
+ +

15.3 Availability

+ +

+The latest version of this document can be viewed on the Debian WWW pages at +http://www.debian.org/doc/FAQ/. +

+ +

+It is also available for download in plain text, HTML, PostScript and PDF +formats at http://www.debian.org/doc/user-manuals#faq. +Also, there are several translations there. +

+ +

+The original SGML files used to create this document are also available in +doc-debian's source package, or in CVS at: +:pserver:anonymous@cvs.debian.org:/cvs/debian-doc/ddp/manuals.sgml/faq +

+ +
+ +

15.4 Document format

+ +

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

+ +

+Conversion utilities for DebianDoc SGML are available in Debian package +debiandoc-sgml. +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-faqinfo.html b/templates/common/doc/FAQ/html/ch-faqinfo.html new file mode 120000 index 000000000..0f759b493 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-faqinfo.html @@ -0,0 +1 @@ +ch-faqinfo.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-ftparchives.en.html b/templates/common/doc/FAQ/html/ch-ftparchives.en.html new file mode 100644 index 000000000..013350708 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-ftparchives.en.html @@ -0,0 +1,567 @@ + + + + + + + + +The Debian GNU/Linux FAQ - The Debian FTP archives + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 5 - The Debian FTP archives +

+ +
+ +

5.1 What are all those directories at the Debian FTP archives?

+ +

+The software that has been packaged for Debian GNU/Linux is available in one of +several directory trees on each Debian mirror site. +

+ +

+The dists directory is short for "distributions", and it +is the canonical way to access the currently available Debian releases (and +pre-releases). +

+ +

+The pool directory contains the actual packages, see What's in the pool directory?, Section 5.10. +

+ +

+There are the following supplementary directories: +

+
+
/tools/:
+
+

+DOS utilities for creating boot disks, partitioning your disk drive, +compressing/decompressing files, and booting Linux. +

+
+
+
+
/doc/:
+
+

+The basic Debian documentation, such as the FAQ, the bug reporting system +instructions, etc. +

+
+
+
+
/indices/:
+
+

+The Maintainers file and the override files. +

+
+
+
+
/project/:
+
+

+mostly developer-only materials, such as: +

+
+
project/experimental/:
+
+

+This directory contains packages and tools which are still being developed, and +are still in the alpha testing stage. Users shouldn't be using packages from +here, because they can be dangerous and harmful even for the most experienced +people. +

+
+
+
+
+ +
+ +

5.2 How many Debian distributions are there in the dists directory?

+ +

+There are three distributions, the "stable" distribution, the +"testing" distribution, and the "unstable" distribution. +The "testing" distribution is sometimes `frozen' (see What about "testing"? How is it `frozen'?, Section +5.6.1). +

+ +
+ +

5.3 What are all those names like slink, potato, etc.?

+ +

+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 unstable suddenly changed its name to +stable, a lot of stuff would have to be needlessly downloaded +again). +

+ +

+Currently, stable is a symbolic link to sarge (i.e. +Debian GNU/Linux 3.1) and testing is a symbolic link to +etch. This means that sarge is the current stable +distribution and etch is the current testing distribution. +

+ +

+unstable is a permanent symbolic link to sid, as +sid is always the unstable distribution (see What +about "sid"?, Section 5.4). +

+ +
+ +

5.3.1 Which other codenames have been used in the past?

+ +

+Other codenames that have been already used are: buzz for release +1.1, rex for release 1.2, bo for releases 1.3.x, +hamm for release 2.0, slink for release 2.1, +potato for release 2.2 and woody for release 3.0. +

+ +
+ +

5.3.2 Where do these codenames come from?

+ +

+So far they have been characters taken from the movie "Toy Story" by +Pixar. +

+ + + + + + + + + + + +
+ +

5.4 What about "sid"?

+ +

+sid or unstable 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 testing, in order +to be released in stable later on. sid contains packages for both +released and unreleased architectures. +

+ +

+The name "sid" also comes from the "Toy Story" animated +motion picture: Sid was the boy next door who destroyed toys :-) +

+ +

+[1] +

+ +
+ +

5.5 What does the stable directory contain?

+ + + + +
+ +

5.6 What does the testing directory contain?

+ +

+Packages are installed into the `testing' directory after they have undergone +some degree of testing in unstable. +

+ +

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

+ +

+More information about the status of "testing" in general and the +individual packages is available at http://www.debian.org/devel/testing +

+ +
+ +

5.6.1 What about "testing"? How is it `frozen'?

+ +

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

+ +

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

+ +

+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 current testing release +information. +

+ +

+Once that bug count lowers to maximum acceptable values, the frozen +"testing" distribution is declared "stable" and released +with a version number. +

+ +

+With each new release, the previous "stable" distribution becomes +obsolete and moves to the archive. For more information please see Debian archive. +

+ +
+ +

5.7 What does the unstable directory contain?

+ +

+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 :-) +

+ +

+There are also main, contrib and non-free subdirectories in `unstable', +separated on the same criteria as in `stable'. +

+ +
+ +

5.8 What are all those directories inside dists/stable/main?

+ +

+Within each of the major directory trees[2], there are three sets of subdirectories containing index +files. +

+ +

+There's one set of binary-something subdirectories +which contain index files for binary packages of each available computer +architecture, for example binary-i386 for packages which execute +on Intel x86 PC machines or binary-sparc for packages which +execute on Sun SPARCStations. +

+ +

+The complete list of available architectures for each release is available at +the release's web +page. For the current release, please see On what hardware architectures/systems does +Debian GNU/Linux run?, Section 3.1. +

+ +

+The index files in binary-* are called Packages(.gz) and they include a summary +of each binary package that is included in that distribution. The actual +binary packages (for woody and subsequent releases) reside in the top +level pool directory. +

+ +

+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). +

+ +

+Last but not least, there's a set of subdirectories meant for the installation +system index files. In the woody release, these are named +disks-architecture; in sarge, they are at +debian-installer/binary-architecture. +

+ +
+ +

5.9 Where is the source code?

+ +

+Source code is included for everything in the Debian system. Moreover, the +license terms of most programs in the system require that source code +be distributed along with the programs, or that an offer to provide the source +code accompany the programs. +

+ +

+The source code is distributed in the pool directory (see What's in the pool directory?, Section 5.10) +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 apt-get source mypackagename. +

+ +

+Some packages are only distributed as source code due to the restrictions in +their licenses. Notably, one such package is pine, see Where is pine?, Section 4.10 for more +information. +

+ +

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

+ +
+ +

5.10 What's in the pool directory?

+ +

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

+ +

+You can find out where each package is placed by executing a command like +apt-cache showsrc mypackagename and looking at the `Directory:' +line. For example, the apache packages are stored in +pool/main/a/apache/. +

+ +

+Additionally, since there are so many lib* packages, these are +treated specially: for instance, libpaper packages are stored in +pool/main/libp/libpaper/. +

+ +

+[3] +

+ +
+ +

5.11 What is "incoming"?

+ +

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

+ +

+Usually nobody should install things from this place. However, in some rare +cases of emergency, the incoming directory is available at 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. +

+ +
+ +

5.12 How do I set up my own apt-able repository?

+ +

+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 Debian +Repository HOWTO. +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-ftparchives.html b/templates/common/doc/FAQ/html/ch-ftparchives.html new file mode 120000 index 000000000..cdad69f63 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-ftparchives.html @@ -0,0 +1 @@ +ch-ftparchives.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-getting.en.html b/templates/common/doc/FAQ/html/ch-getting.en.html new file mode 100644 index 000000000..5f608d5b0 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-getting.en.html @@ -0,0 +1,374 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Getting and installing Debian GNU/Linux + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 2 - Getting and installing Debian GNU/Linux +

+ +
+ +

+The official document giving installation instructions is the Debian GNU/Linux +Installation Guide. We'll give some additional notes about getting +and installing Debian GNU/Linux here. +

+ +
+ +

2.1 What is the latest version of Debian?

+ +

+Currently there are three versions of Debian GNU/Linux: +

+
+
release 3.1, a.k.a. the `stable' distribution
+
+

+This is stable and well tested software, it changes if major security or +usability fixes are incorporated. +

+
+
+
+
the `testing' distribution
+
+

+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'. +

+
+
+
+
the `unstable' distribution
+
+

+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 +`unstable'! +

+
+
+ +

+Please see How many Debian +distributions are there in the dists directory?, Section 5.2 +for more information. +

+ +
+ +

2.2 Are there package upgrades in `stable'?

+ +

+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 security.debian.org. +

+ +

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

+ +

+For more information related to security support please read the Security FAQ or the +Debian +Security Manual. +

+ +
+ +

2.3 Where/how can I get the Debian installation disks?

+ +

+You can get the installation disks by downloading the appropriate files from +one of the Debian +mirrors. +

+ +

+The installation system files are separated in subdirectories of +dists/stable/main directory, and the names of these subdirectories +correspond to your architecture like this: disks-arch +(arch is "i386", "sparc", etc, check the site +for an exact list). In each of these architecture subdirectories there can be +several directories, each for a version of the installation system, and the +currently used one is in the `current' directory (that's a symbolic link). +

+ +

+See the README.txt file in that directory for further +instructions. +

+ +
+ +

2.4 How do I install the Debian from CD-ROMs?

+ +

+Linux supports the ISO 9660 (CD-ROM) file system with Rock Ridge extensions +(formerly known as "High Sierra"). Several vendors provide Debian +GNU/Linux in this format. +

+ +

+Warning: When installing from CD-ROM, it is usually not a good idea to choose +dselect's cdrom access method. This method is usually very slow. +The mountable and apt methods, for example, are much +better for installing from CD-ROM (see dpkg-mountable, Section 8.2.5 +and apt-get, dselect and apt-cdrom, Section +8.2.2). +

+ +
+ +

2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!

+ +

+Official Debian CD images indeed contain symlinks like: +

+ +
+      /dists/frozen -> sarge/
+      /dists/stable -> sarge/
+      /dists/testing -> sarge/
+      /dists/unstable -> sarge/
+
+ +

+so that they work when your sources.list has an entry like +

+ +
+      deb cdrom:[<name as on cd label>]/ unstable main [...]
+
+ +

+. +

+ +

+The fact these symlinks are present does not mean the image is +`unstable' or `testing' or anything. Read the CD label in +/.disk/info to find out which Debian version it contains. This +information is also present in /README.txt on the CD. +

+ +

+Read http://www.debian.org/releases/ +to find out what the current `stable' and `testing' releases are. +

+ +
+ +

2.6 I have my own CD-writer, are there CD images available somewhere?

+ +

+Yes. To make it easier for CD vendors to provide high quality disks, we +provide the Official CD +images. +

+ +
+ +

2.7 Can I install it from a pile of floppy disks?

+ +

+First of all, a warning: whole Debian GNU/Linux is way too large to be +installed from media as small as a standard 1.44MB floppy disk - you may not +find installing from floppies a very pleasant experience. +

+ +

+Copy the Debian packages onto formatted floppy disks. Either a DOS, the native +Linux "ext2", or the "minix" format will do; one just has +to use a mount command appropriate to the floppy being used. +

+ +

+Using floppy disks has these complications: +

+ + + +

+You must have support in the kernel for floppy disks in order to read and write +to floppy disk; most kernels come with floppy drive support included in them. +

+ +

+To mount a floppy disk under the mount point /floppy (a directory +which should have been created during installation), use: +

+ + + + +
+ +

2.8 Can I get and install Debian directly from a remote Internet site?

+ +

+Yes. You can boot the Debian installation system from a set of files you can +download from our FTP site and its mirrors. +

+ +

+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 http://www.debian.org/CD/netinst/. +

+ +

+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. For more information, please see http://www.debian.org/distrib/floppyinst. +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-getting.html b/templates/common/doc/FAQ/html/ch-getting.html new file mode 120000 index 000000000..568d808b9 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-getting.html @@ -0,0 +1 @@ +ch-getting.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-kernel.en.html b/templates/common/doc/FAQ/html/ch-kernel.en.html new file mode 100644 index 000000000..5e88fad27 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-kernel.en.html @@ -0,0 +1,311 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Debian and the kernel + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 9 - Debian and the kernel +

+ +
+ +

9.1 Can I install and compile a kernel without some Debian-specific tweaking?

+ +

+Yes. +

+ +

+There's only one common catch: the Debian C libraries are built with the most +recent stable releases of the kernel 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 (libc6-dev), or use the new headers from an unpacked +tree of the newer kernel. That is, if the kernel sources are in +/usr/src/linux, then you should add +-I/usr/src/linux/include/ to your command line when compiling. +

+ +
+ +

9.2 What tools does Debian provide to build custom kernels?

+ +

+Users who wish to (or must) build a custom kernel are encouraged to download +the package kernel-package. This package contains the script to +build the kernel package, and provides the capability to create a Debian +kernel-image package just by running the command +

+ +
+     make-kpkg kernel_image
+
+ +

+in the top-level kernel source directory. Help is available by executing the +command +

+ +
+     make-kpkg --help
+
+ +

+and through the manual page make-kpkg(1). +

+ +

+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 +kernel-source-version package is available (where "version" stands +for the kernel version). +

+ +

+Detailed instructions for using the kernel-package package are +given in the file /usr/share/doc/kernel-package/README.gz. +Briefly, one should: +

+ + + + + +
+ +

9.3 How can I make a custom boot floppy?

+ +

+This task is greatly aided by the Debian package boot-floppies, +normally found in the admin section of the Debian FTP archive. +Shell scripts in this package produce boot floppies in the +SYSLINUX format. These are MS-DOS 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 syslinux.cfg file +on the floppy). Other scripts in this package produce emergency root disks and +can even reproduce the base disks. +

+ +

+You will find more information about this in the +/usr/share/doc/boot-floppies/README file after installing the +boot-floppies package. +

+ +
+ +

9.4 What special provisions does Debian provide to deal with modules?

+ +

+Debian's modconf package provides a shell script +(/usr/sbin/modconf) 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 +/etc/modules.conf (which lists aliases, and other arguments that +must be used in conjunction with various modules) through files in +/etc/modutils/, and /etc/modules (which lists the +modules that must be loaded at boot time). +

+ +

+Like the (new) Configure.help files that are now available to support the +construction of custom kernels, the modconf package comes with a series of help +files (in /usr/lib/modules_help/) which provide detailed +information on appropriate arguments for each of the modules. +

+ +
+ +

9.5 Can I safely de-install an old kernel package, and if so, how?

+ +

+Yes. The kernel-image-NNN.prerm 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: +

+ +
+     dpkg --purge --force-remove-essential kernel-image-NNN
+
+ +

+(replace "NNN" with your kernel version and revision number, of +course) +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-kernel.html b/templates/common/doc/FAQ/html/ch-kernel.html new file mode 120000 index 000000000..125039fb4 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-kernel.html @@ -0,0 +1 @@ +ch-kernel.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-nexttime.en.html b/templates/common/doc/FAQ/html/ch-nexttime.en.html new file mode 100644 index 000000000..0c1d3eca4 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-nexttime.en.html @@ -0,0 +1,149 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Changes expected in the next major release of Debian + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 14 - Changes expected in the next major release of Debian +

+ +
+ +

14.1 Increased security

+ +

+Debian contains support for shadow passwords since release 1.3. In addition, +the Linux library of Pluggable Authentication Modules (a.k.a. libpam;) that +allows sysadmins to choose authorization modes on an application-specific basis +is available, and initially set to authenticate via shadow password. +

+ +

+Including full support for advanced authentication methods such as Kerberos, as +well as additional security enhancements for mandatory access control +mechanisms such as SElinux, RSBAC and buffer overflow protection like +Exec-shield or PaX is still in progress. +

+ +
+ +

14.2 Extended support for non-English users

+ +

+Debian already has very good support for non-English users, see How does Debian support non-English +languages?, Section 4.8. +

+ +

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

+ +

+The GNU Translation Project ftp://ftp.gnu.org/pub/gnu/ABOUT-NLS +works on internationalizing the GNU programs. +

+ +
+ +

14.3 More architectures

+ +

+Complete Debian system on other architectures such as AMD64 or SuperH is +expected soon. Notice that, for AMD64 there is a development archive at +http://amd64.debian.net/ +that provides intallation images as well as binary packages for most of the +distribution. This architecture will probably be added for etch. +

+ +
+ +

14.4 More kernels

+ +

+In addition to Debian GNU/Hurd, Debian is being ported also to BSD kernels, +namely to NetBSD. +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-nexttime.html b/templates/common/doc/FAQ/html/ch-nexttime.html new file mode 120000 index 000000000..da23d4849 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-nexttime.html @@ -0,0 +1 @@ +ch-nexttime.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-pkg_basics.en.html b/templates/common/doc/FAQ/html/ch-pkg_basics.en.html new file mode 100644 index 000000000..0ebd3feb3 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-pkg_basics.en.html @@ -0,0 +1,860 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Basics of the Debian package management system + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 6 - Basics of the Debian package management system +

+ +
+ +

6.1 What is a Debian package?

+ +

+Packages generally contain all of the files necessary to implement a set of +related commands or features. There are two types of Debian packages: +

+ + + +

+Installation of software by the package system uses "dependencies" +which are carefully designed by the package maintainers. These dependencies +are documented in the control file associated with each package. +For example, the package containing the GNU C compiler (gcc) +"depends" on the package binutils which includes the +linker and assembler. If a user attempts to install gcc without +having first installed binutils, the package management system +(dpkg) will send an error message that it also needs binutils, and +stop installing gcc. (However, this facility can be overridden by +the insistent user, see dpkg(8).) See more in What is meant by saying that a package Depends, +Recommends, Suggests, Conflicts, Replaces +or Provides another package?, Section 6.9 below. +

+ +

+Debian's packaging tools can be used to: +

+ + + + + +
+ +

6.2 What is the format of a Debian binary package?

+ +

+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 .deb. +

+ +

+The internals of this Debian binary packages format are described in the +deb(5) manual page. This internal format is subject to change +(between major releases of Debian GNU/Linux), therefore please always use +dpkg-deb(1) for manipulating .deb files. +

+ +
+ +

6.3 Why are Debian package file names so long?

+ +

+The Debian binary package file names conform to the following convention: +<foo>_<VersionNumber>-<DebianRevisionNumber>.deb +

+ +

+Note that foo 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: +

+ + + +

+The VVV 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". +

+ +

+The RRR 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 (debian/rules), the Debian control file +(debian/control), the installation or removal scripts +(debian/p*), or in the configuration files used with the package. +

+ +
+ +

6.4 What is a Debian control file?

+ +

+Specifics regarding the contents of a Debian control file are provided in the +Debian Policy Manual, section 5, see What other documentation exists on and +for a Debian system?, Section 11.1. +

+ +

+Briefly, a sample control file is shown below for the Debian package hello: +

+ +
+     Package: hello
+     Priority: optional
+     Section: devel
+     Installed-Size: 45
+     Maintainer: Adam Heath <doogie@debian.org>
+     Architecture: i386
+     Version: 1.3-16
+     Depends: libc6 (>= 2.1)
+     Description: The classic greeting, and a good example
+      The GNU hello program produces a familiar, friendly greeting.  It
+      allows nonprogrammers to use a classic computer science tool which
+      would otherwise be unavailable to them.
+      .
+      Seriously, though: this is an example of how to do a Debian package.
+      It is the Debian version of the GNU Project's `hello world' program
+      (which is itself an example for the GNU Project).
+
+ +

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

+ +

+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 Why are Debian package file names so long?, +Section 6.3. +

+ +

+The Architecture field specifies the chip for which this particular binary was +compiled. +

+ +

+The Depends field gives a list of packages that have to be installed in order +to install this package successfully. +

+ +

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

+ +

+The Section line gives the "section" where this Debian package is +stored at the Debian FTP sites. This is the name of a subdirectory (within one +of the main directories, see What +are all those directories at the Debian FTP archives?, Section 5.1) where +the package is stored. +

+ +

+The Priority indicates how important is this package for installation, so that +semi-intelligent software like dselect or console-apt can sort the package into +a category of e.g. packages optionally installed. See What is an Essential Required, +Important, Standard, Optional, or Extra +package?, Section 6.7. +

+ +

+The Maintainer field gives the e-mail address of the person who is currently +responsible for maintaining this package. +

+ +

+The Description field gives a brief summary of the package's features. +

+ +

+For more information about all possible fields a package can have, please see +the Debian Policy Manual, section 5., "Control files and their +fields". +

+ +
+ +

6.5 What is a Debian conffile?

+ +

+Conffiles is a list of configuration files (usually placed in +/etc) 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. +

+ +

+To determine exactly which files are preserved during an upgrade, run: +

+ +
+     dpkg --status package
+
+ +

+And look under "Conffiles:". +

+ +
+ +

6.6 What is a Debian preinst, postinst, prerm, and postrm script?

+ +

+These files are executable scripts which are automatically run before or after +a package is installed. Along with a file named control, all of +these files are part of the "control" section of a Debian archive +file. +

+ +

+The individual files are: +

+
+
preinst
+
+

+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). +

+
+
+
+
postinst
+
+

+This script typically completes any required configuration of the package +foo once foo 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. +

+
+
+
+
prerm
+
+

+This script typically stops any daemons which are associated with a package. +It is executed before the removal of files associated with the package. +

+
+
+
+
postrm
+
+

+This script typically modifies links or other files associated with +foo, and/or removes files created by the package. (Also see What is a Virtual Package?, Section 6.8.) +

+
+
+ +

+Currently all of the control files can be found in directory +/var/lib/dpkg/info. The files relevant to package +foo begin with the name "foo" and have file extensions +of "preinst", "postinst", etc., as appropriate. The file +foo.list in that directory lists all of the files that were +installed with the package foo. (Note that the location of these +files is a dpkg internal; you should not rely on it.) +

+ +
+ +

6.7 What is an Essential Required, Important, Standard, Optional, or Extra package?

+ +

+Each Debian package is assigned a priority by the distribution +maintainers, as an aid to the package management system. The priorities are: +

+ + + + + + +

+If you do a default Debian installation all the packages of priority +Standard or higher will be installed in your system. If you +select pre-defined tasks you will get lower priority packages too. +

+ +

+Additionally, some packages are marked as Essential since they +are absolutely necessary for the proper functioning of the system. The package +management tools will refuse to remove these. +

+ +
+ +

6.8 What is a Virtual Package?

+ +

+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 tin and trn 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 news-reader. +

+ +

+Similarly, smail and sendmail 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 +mail-transport-agent will be satisfied by the existence of this +virtual package. +

+ +

+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 +update-alternatives, and is described further in Some users like mawk, others like gawk; +some like vim, others like elvis; some like trn, others like tin; how does +Debian support diversity?, Section 10.10. +

+ +
+ +

6.9 What is meant by saying that a package Depends, Recommends, Suggests, Conflicts, Replaces or Provides another package?

+ +

+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: +

+ + + + + + + +

+More detailed information on the use of each these terms can be found in the +Policy manual. +

+ +
+ +

6.10 What is meant by Pre-Depends?

+ +

+"Pre-Depends" is a special dependency. In the case of most packages, +dpkg will unpack its archive file (i.e., its .deb +file) independently of whether or not the files on which it depends exist on +the system. Simplistically, unpacking means that dpkg 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 depend on the +existence of some other packages on your system, dpkg will refuse +to complete the installation (by executing its "configure" action) +until the other packages are installed. +

+ +

+However, for some packages, dpkg 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 +a.out format to ELF format, where the order +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. +

+ +

+As before, more detailed information about this can be found in the Policy +manual. +

+ +
+ +

6.11 What is meant by unknown, install, remove purge and hold in the package status?

+ +

+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 +dselect, or by the user's direct invocations of +dpkg). +

+ +

+Their meanings are: +

+ + + + + + +
+ +

6.12 How do I put a package on hold?

+ +

+There are three ways of holding back packages, with dpkg, aptitude or with +dselect. +

+ +

+With dpkg, you just have to export the list of package selections, with: +

+ +
+     dpkg --get-selections \* > selections.txt
+
+ +

+Then edit the resulting file selections.txt, change the line +containing the package you wish to hold, e.g. libc6, from this: +

+ +
+     libc6                                           install
+
+ +

+to this: +

+ +
+     libc6                                           hold
+
+ +

+Save the file, and reload it into dpkg database with: +

+ +
+     dpkg --set-selections < selections.txt
+
+ +

+With aptitude, you can hold a package using +

+ +
+     aptitude hold package_name
+
+ +

+and remove the hold with +

+ +
+     aptitude unhold package_name
+
+ +

+With dselect, you just 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. +

+ +
+ +

6.13 How do I install a source package?

+ +

+Debian source packages can't actually be "installed", they are just +unpacked in whatever directory you want to build the binary packages they +produce. +

+ +

+Source packages are distributed on most of the same mirrors where you can +obtain the binary packages. If you set up your APT's +sources.list(5) to include the appropriate "deb-src" +lines, you'll be able to easily download any source packages by running +

+ +
+     apt-get source foo
+
+ +

+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 +

+ +
+     apt-get build-dep foo
+
+ +

+before building the source. +

+ +
+ +

6.14 How do I build binary packages from a source package?

+ +

+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). +

+ +

+Once you have them (How do I install a source package?, +Section 6.13), if you have the dpkg-dev package installed, the +following command: +

+ +
+     dpkg-source -x foo_version-revision.dsc
+
+ +

+will extract the package into a directory called foo-version. +

+ +

+If you want just to compile the package, you may cd into +foo-version directory and issue the command +

+ +
+     dpkg-buildpackage -rfakeroot -b
+
+ +

+to build the package (note that this also requires the fakeroot +package), and then +

+ +
+     dpkg -i ../foo_version-revision_arch.deb
+
+ +

+to install the newly-built package(s). +

+ +
+ +

6.15 How do I create Debian packages myself?

+ +

+For more detailed description on this, read the New Maintainers' Guide, +available in the maint-guide package, or at http://www.debian.org/doc/devel-manuals#maint-guide. +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-pkg_basics.html b/templates/common/doc/FAQ/html/ch-pkg_basics.html new file mode 120000 index 000000000..98c97fece --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-pkg_basics.html @@ -0,0 +1 @@ +ch-pkg_basics.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-pkgtools.en.html b/templates/common/doc/FAQ/html/ch-pkgtools.en.html new file mode 100644 index 000000000..114bb9fe2 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-pkgtools.en.html @@ -0,0 +1,936 @@ + + + + + + + + +The Debian GNU/Linux FAQ - The Debian package management tools + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 7 - The Debian package management tools +

+ +
+ +

7.1 What programs does Debian provide for managing its packages?

+ +

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

+ +

+It is important to understand that the higher level package management tools +such as aptitude or dselect rely on apt +which, itself, relies on dpkg to manage the packages in the +system. +

+ +

+See the APT +HOWTO for more information about the Debian package management +utilities. This document is available in various languages and formats, see +the APT HOWTO +entry on the DDP Users' Manuals overview. +

+ +
+ +

7.1.1 dpkg

+ +

+This is the main package management program. dpkg can be invoked +with many options. Some common uses are: +

+ + + + + + + + + + +
+ +

7.1.2 APT

+ +

+APT is the Advanced Package Tool and provides the apt-get +program. apt-get provides a simple way to retrieve and install +packages from multiple sources using the command line. Unlike +dpkg, apt-get does not understand .deb files, it +works with the packages proper name and can only install .deb archives from a +source specified in /etc/apt/sources.list. apt-get +will call dpkg directly after downloading the .deb archives[4] from the configured sources. +

+ +

+Some common ways to use apt-get are: +

+ + + + + + + +

+Note that you must be logged in as root to perform any commands that modify the +system packages. +

+ +

+The apt tool suite also includes the apt-cache 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 apt-cache are: +

+ + + + + +

+For more information, install the apt package and read +apt-get(8), sources.list(5) and install the +apt-doc package and read +/usr/share/doc/apt-doc/guide.html/index.html. +

+ +
+ +

7.1.3 aptitude

+ +

+aptitude is a package manager for Debian GNU/Linux systems that +provides a frontend to the apt package management infrastructure. +aptitude is a text-based interface using the curses library, it +can be used to perform management tasks in a fast and easy way. +

+ +

+aptitude provides the functionality of dselect and +apt-get, as well as many additional features not found in either +program: +

+ + + + + + + + +

+You can use aptitude through a visual interface (simply run +aptitude) or directly from the command line. The command line +syntax used is very similar to the one used in apt-get. For +example, to install the foo package, you can run aptitude +install foo. +

+ +

+Note that aptitude is the recommended program by Debian to install +a package and/or to upgrade your system. +

+ +

+For more informations, read the manual page aptitude(8) and +install the aptitude-doc-en package. +

+ +
+ +

7.1.4 dselect

+ +

+This program is a menu-driven interface to the Debian package management +system. It is particularly useful for first-time installations. Some users +might feel more comfortable using aptitude which is also +recommended over dselect for large-scale upgrades. For more +information on aptitude please see aptitude, +Section 7.1.3. +

+ +

+dselect can: +

+ + + + + + +

+dselect 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 +<enter> key to select the highlighted action. +

+ +

+What the user sees next depends on the action he selected. If he selects any +option but Access or Select, then +dselect will simply proceed to execute the specified action: e.g., +if the user selected the action Remove, then dselect would proceed +to remove all of the files selected for removal when the user last chose the +Select action. +

+ +

+Both the Access menu item and the Select 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. +

+ +

+Extensive on-line help is available, use the '?' key to get to a help screen +at any time. +

+ +

+The order in which the actions are presented in the first dselect +menu represents the order in which a user would normally choose +dselect 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). +

+ + + + + +
+ +

7.1.5 Other package management tools

+ +
+ +

7.1.5.1 dpkg-deb

+ +

+This program manipulates Debian archive(.deb) files. Some common +uses are: +

+ + + + +

+Note that any packages that were merely unpacked using dpkg-deb +--extract will be incorrectly installed, you should use dpkg +--install instead. +

+ +

+More information is given in the manual page dpkg-deb(1). +

+ +
+ +

7.1.5.2 dpkg-split

+ +

+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 dpkg package), since it calls the program +dpkg-deb to parse the debian package file into its component +records. +

+ +

+For example, to split a big .deb file into N parts, +

+ + + + + +
+ +

7.2 Debian claims to be able to update a running program; how is this accomplished?

+ +

+The kernel (file system) in Debian GNU/Linux systems supports replacing files +even while they're being used. +

+ +

+We also provide a program called start-stop-daemon which is used +to start daemons at boot time or to stop daemons when the kernel 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. +

+ +
+ +

7.3 How can I tell what packages are already installed on a Debian system?

+ +

+To learn the status of all the packages installed on a Debian system, execute +the command +

+ +
+     dpkg --list
+
+ +

+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 +installed, and a brief description. +

+ +

+To learn the status of packages whose names match the string any pattern +beginning with "foo" by executing the command: +

+ +
+     dpkg --list 'foo*'
+
+ +

+To get a more verbose report for a particular package, execute the command: +

+ +
+     dpkg --status packagename
+
+ +
+ +

7.4 How can I find out what package produced a particular file?

+ +

+To identify the package that produced the file named foo execute +either: +

+ + + + +
+ +

7.5 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?

+ +

+Some packages that are split in program (`foo') and data (`foo-data'). 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. +

+ +

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

+ +

+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 aptitude (see aptitude, Section 7.1.3) 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. +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-pkgtools.html b/templates/common/doc/FAQ/html/ch-pkgtools.html new file mode 120000 index 000000000..6c9eeed19 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-pkgtools.html @@ -0,0 +1 @@ +ch-pkgtools.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-redistrib.en.html b/templates/common/doc/FAQ/html/ch-redistrib.en.html new file mode 100644 index 000000000..f0ac5d0c8 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-redistrib.en.html @@ -0,0 +1,170 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Redistributing Debian GNU/Linux in a commercial product + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 13 - Redistributing Debian GNU/Linux in a commercial product +

+ +
+ +

13.1 Can I make and sell Debian CDs?

+ +

+Go ahead. You do not need permission to distribute anything we have +released, 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. +

+ +

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

+ +
+ +

13.2 Can Debian be packaged with non-free software?

+ +

+Yes. While all the main components of Debian are free software, we provide a +non-free directory for programs that are not freely redistributable. +

+ +

+CD manufacturers may 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. +

+ +
+ +

13.3 I am making a special Linux distribution for a "vertical market". Can I use Debian GNU/Linux for the guts of a Linux system and add my own applications on top of it?

+ +

+Yes. Debian-derived distributions are being created both in close cooperation +with the Debian project itself and by external parties. One can use the +Custom Debian +Distributions framework to work together with Debian; Skolelinux is one such project. +

+ +

+One person is building a "Linux for Hams" distribution, with +specialized programs for Radio Amateurs. He is starting with Debian as the +"base system", and adding programs to control the transmitter, track +satellites, etc. All of the programs he adds are packaged with the Debian +packaging system so that his users will be able to upgrade easily when he +releases subsequent CDs. +

+ +

+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 GNU/Linux is, but use most +of our components in their product. +

+ +

+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 How do I override a file +installed by a package, so that a different version can be used instead?, +Section 10.8. +

+ +
+ +

13.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?

+ +

+Go right ahead. The package tool is free software; the packages may or may not +be free software, it can install them all. +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-redistrib.html b/templates/common/doc/FAQ/html/ch-redistrib.html new file mode 120000 index 000000000..f1826236b --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-redistrib.html @@ -0,0 +1 @@ +ch-redistrib.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-software.en.html b/templates/common/doc/FAQ/html/ch-software.en.html new file mode 100644 index 000000000..bedb65f9e --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-software.en.html @@ -0,0 +1,410 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Software available in the Debian system + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 4 - Software available in the Debian system +

+ +
+ +

4.1 What types of applications and development software are available for Debian GNU/Linux?

+ +

+Like most Linux distributions, Debian GNU/Linux provides: +

+ + + + + + + +

+More than 15180 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 450 software +suites are available as Debian packages, but are not formally part of Debian +due to license restrictions. +

+ +
+ +

4.2 Who wrote all that software?

+ +

+For each package the authors of the program(s) are credited in the +file /usr/share/doc/PACKAGE/copyright, where PACKAGE is to be +substituted with the package's name. +

+ +

+Maintainers who package this software for the Debian GNU/Linux system +are listed in the Debian control file (see What is a Debian control file?, +Section 6.4) that comes with each package. The Debian changelog, in +/usr/share/doc/PACKAGE/changelog.Debian.gz, mentions the people +who've worked on the Debian packaging too. +

+ +
+ +

4.3 How can I get a current list of programs that have been packaged for Debian?

+ +

+A complete list is available from any of the Debian mirrors, in the +file indices/Maintainers. That file includes the package names +and the names and e-mails of their respective maintainers. +

+ +

+The WWW interface to the Debian +packages conveniently summarizes the packages in each of about +twenty "sections" of the Debian archive. +

+ +
+ +

4.4 What is missing from Debian GNU/Linux?

+ +

+A list of packages which are still needed to be packaged for Debian exists, the +Work-Needing and Prospective +Packages list. +

+ +

+For more details about adding the missing things, see How can I become a Debian software +developer?, Section 12.1. +

+ +
+ +

4.5 Why do I get "ld: cannot find -lfoo" messages when compiling programs? Why aren't there any libfoo.so files in Debian library packages?

+ +

+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). +

+ +
+ +

4.6 (How) Does Debian support Java?

+ +

+Since the official Java Development kit and Runtime Environment from Sun +Microsystems is non-free software, even undistributeable by Debian, it cannot +properly be included in Debian. If you want those installed anyway, please +refer to the java-package package in contrib. +

+ +

+However, both the JDK and several free implementations of Java +technology are available as Debian packages. You can write, debug and run Java +programs using Debian. +

+ +

+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. +Netscape Navigator, while non-free, is also available as a Debian package and +it can run Java applets. +

+ +

+Please refer to the Debian Java +FAQ for more information. +

+ +
+ +

4.7 How can I check that I am using a Debian system, and what version is it?

+ +

+In order to make sure that your system has been installed from the real Debian +base disks check for the existence of /etc/debian_version file, +which contains a single one-line entry giving the version number of the +release, as defined by the package base-files. +

+ +

+The existence of the program dpkg 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 GNU/Linux. +

+ +

+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 foo, use the command dpkg --list foo. To +view versions of all installed packages, run: +

+ +
+     dpkg -l
+
+ +

+For a more verbose description, use: +

+ +
+     dpkg --status foo
+
+ +
+ +

4.8 How does Debian support non-English languages?

+ + + + +
+ +

4.9 What about the US export regulation limitations?

+ +

+US laws placed restrictions on the export of defense articles, which includes +some types of cryptographic software. PGP and ssh, among others, fall into +this category. For the sarge release packages in this archive were +moved to the main archive (or to non-free, if applicable) due to the +US relaxing its regulations on the export of cryptography. +

+ +

+To prevent anyone from taking unnecessary legal risks, certain Debian GNU/Linux +packages were only available from a non-US site ftp://non-US.debian.org/debian-non-US/, +with numerous mirror sites all of which are also outside of the US, see +ftp://non-US.debian.org/debian-non-US/README.non-US +for a full list. These sites still exist (for the benefit of users of +woody) but its contents are no longer supported and are considered +obsolete. Please remove any mentions to non-US from your sources in your +/etc/apt/sources.list configuration file. +

+ +
+ +

4.10 Where is pine?

+ +

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

+ +

+The source package name is pine. You can use the +pine-tracker package to be notified about when you need to +upgrade. +

+ +

+Note that there are many replacements for both pine and pico, such as +mutt and nano, that are located in the main section. +

+ +
+ +

4.11 Where is qmail/ezmlm/djbdns?

+ +

+Dan J. Bernstein distributes all +software he has written with a restrictive license, consequently, +it's in the non-free area. Since the license he uses does not allow modified +binaries to be distributed, you have to compile it yourself from the source and +the Debian patches to obtain a binary package you can install in your Debian +GNU/Linux system. +

+ +

+The source package names are qmail-src, ezmlm-src and +djbdns-installer, respectively. +

+ +

+For qmail you need to install qmail-src first and +then run build-qmail to build the Debian package. You also need +to do install the ucspi-tcp-src package to get ucspi-tcp, which +qmail depends on. +

+ +

+Dan J. Bernstein maintains a FAQ from distributors page +if you are interested in reading his reasons (one of which is Cross-platform +compatibility) +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-software.html b/templates/common/doc/FAQ/html/ch-software.html new file mode 120000 index 000000000..f75c0ab2c --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-software.html @@ -0,0 +1 @@ +ch-software.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-support.en.html b/templates/common/doc/FAQ/html/ch-support.en.html new file mode 100644 index 000000000..57e21da17 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-support.en.html @@ -0,0 +1,525 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Getting support for Debian GNU/Linux + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 11 - Getting support for Debian GNU/Linux +

+ +
+ +

11.1 What other documentation exists on and for a Debian system?

+ + + + + + + + + +

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

+ +
+ +

11.2 Are there any on-line resources for discussing Debian?

+ +

+Yes. In fact, the main method of support Debian provides to our users is by +the way of e-mail. +

+ +
+ +

11.2.1 Mailing lists

+ +

+There are a lot of Debian-related mailing +lists. +

+ +

+On a system with the doc-debian package installed there is a +complete list of mailing lists in +/usr/share/doc/debian/mailing-lists.txt. +

+ +

+Debian mailing lists are named following the pattern +debian-list-subject. Examples are debian-announce, debian-user, +debian-news. To subscribe to any list debian-list-subject, send +mail to debian-list-subject-request@lists.debian.org with the word +"subscribe" in the Subject: header. Be sure to remember to add +-request 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. +

+ +

+If you have a forms-capable World Wide Web browser, you can subscribe to +mailing lists using the WWW form. You +can also un-subscribe using a WWW form. +

+ +

+The list manager's e-mail address is listmaster@lists.debian.org, +in case you have any trouble. +

+ +

+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 Mailing +Lists Privacy policy for more information. +

+ +

+Archives of the Debian mailing lists are available via WWW at http://lists.debian.org/. +

+ +
+ +

11.2.1.1 What is the code of conduct for the mailing lists?

+ +

+When using the Debian mailing lists, please follow these rules: +

+ + + + + + +
+ +

11.2.2 Maintainers

+ +

+Users can address questions to individual package maintainers using e-mail. To +reach a maintainer of a package called xyz, send e-mail to +xyz@packages.debian.org. +

+ +
+ +

11.2.3 Usenet newsgroups

+ +

+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 +Linux Online +and LinuxJournal sites. +

+ +
+ +

11.3 Is there a quick way to search for information on Debian GNU/Linux?

+ +

+There is a variety of search engines that serve documentation related to +Debian: +

+ + + + +
+ +

11.4 Are there logs of known bugs?

+ +

+Reports on unsolved (and closed) issues are publicly available: Debian +promissed to do so by stating "We will not hide problems" in the +Debian Social +Contract. +

+ +

+The Debian GNU/Linux 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 until it is marked as having been dealt with. +

+ +

+Copies of this information are available at http://www.debian.org/Bugs/. +

+ +

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

+ +
+ +

11.5 How do I report a bug in Debian?

+ +

+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: +

+ + + + +

+You can use the package reportbug 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 additional information to the +existing bug report. +

+ +

+If you want to mail the report with an e-mail program, send a message to +submit@bugs.debian.org. The +message's first line must be similar to +

+ +
+     Package: package-name
+
+ +

+(replace package-name with the name of the package). The next line +should relate the package version number in a similar way: +

+ +
+     Version: version-number
+
+ +

+The version number for any package installed on your system can be obtained +using the command line +

+ +
+     dpkg -s package-name
+
+ +

+This section is referred to as the pseudo-header. The rest of the message +should contain the description of the bug (please make it moderately detailed), +the Debian release you are using, and versions of other relevant packages. The +Debian release number will be displayed by the command +

+ +
+     cat /etc/debian_version
+
+ +

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

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-support.html b/templates/common/doc/FAQ/html/ch-support.html new file mode 120000 index 000000000..978d556ab --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-support.html @@ -0,0 +1 @@ +ch-support.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-uptodate.en.html b/templates/common/doc/FAQ/html/ch-uptodate.en.html new file mode 100644 index 000000000..b271f29f7 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-uptodate.en.html @@ -0,0 +1,479 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Keeping your Debian system up-to-date + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 8 - Keeping your Debian system up-to-date +

+ +
+ +

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

+ +

+You should also read the Release Notes document that describes the details of +specific upgrades. It is shipped on all Debian CDs and available on the WWW at +http://www.debian.org/releases/stable/releasenotes. +

+ +
+ +

8.1 How can I upgrade my Debian 1.3.1 (or earlier) distribution, based on libc5, to 2.0 (or later), based on libc6?

+ +

+There are several ways to upgrade: +

+ + + + + +
+ +

8.2 How can I keep my Debian system current?

+ +

+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 dpkg. Note that dpkg 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. +

+ +

+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: +

+ +
+ +

8.2.1 aptitude

+ +

+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 +/usr/share/doc/apt-doc/guide.html/index.html (you will have to +install the apt-doc package). +

+ +

+aptitude is the recommended package manager for Debian GNU/Linux +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. +

+ +

+Before you can use aptitude, you'll have to edit the +/etc/apt/sources.list 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: +

+ +
+     http://http.us.debian.org/debian stable main contrib non-free
+
+ +

+You can replace http.us.debian.org with the name of a faster Debian mirror near +you. See the mirror list at http://www.debian.org/misc/README.mirrors +for more information. +

+ +

+More details on this can be found in the sources.list(8) manual +page. +

+ +

+To update your system, run +

+ +
+     aptitude update
+
+ +

+followed by +

+ +
+     aptitude dist-upgrade
+
+ +

+Answer any questions that might come up, and your system will be upgraded. See +also aptitude, Section 7.1.3. +

+ +
+ +

8.2.2 apt-get, dselect and apt-cdrom

+ +

+apt-get is an APT-based command-line tool for handling packages, +and the APT dselect method is an interface to APT through dselect. +Both of these provide a simple, safe way to install and upgrade packages. +

+ +

+To use apt-get, install the apt package, and edit the +/etc/apt/sources.list file to set it up, just as for aptitude, Section 8.2.1. +

+ +

+Then run +

+ +
+     apt-get update
+
+ +

+followed by +

+ +
+     apt-get dist-upgrade
+
+ +

+Answer any questions that might come up, and your system will be upgraded. See +also the apt-get(8) manual page, as well as APT, Section 7.1.2. +

+ +

+To use APT with dselect, 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 /etc/apt/sources.list. See also +dselect, Section 7.1.4. +

+ +

+If you want to use CDs to install packages, you can use apt-cdrom. +For details, please see the Release Notes, section "Setting up for an +upgrade from a local mirror". +

+ +

+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 apt-get clean +and apt-get autoclean, or to move them someplace else (hint: use +apt-move). +

+ +
+ +

8.2.3 dpkg-ftp

+ +

+This is an older access method for dselect. It can be invoked +from within dselect, thereby allowing a user the ability to +download files and install them directly in one step. To do this, select the +ftp access method in dselect (option 0) and specify +the remote host name and directory. dpkg-ftp will then +automatically download the files that are selected (either in this session of +dselect or earlier ones). +

+ +

+Note that, unlike the mirror program, dpkg-ftp does +not grab everything at a mirror site. Rather, it downloads only those files +which you have selected (when first starting up dpkg-ftp), and +which need to be updated. +

+ +

+dpkg-ftp is somewhat obsolete. You should use the APT access +method with ftp:// URLs in sources.list instead. +

+ +
+ +

8.2.4 mirror

+ +

+This Perl script, and its (optional) manager program called +mirror-master, can be used to fetch user-specified parts of a +directory tree from a specified host via anonymous FTP. +

+ +

+mirror is particularly useful for downloading large volumes of +software. After the first time files have been downloaded from a site, a file +called .mirrorinfo is stored on the local host. Changes to the +remote file system are tracked automatically by mirror, which +compares this file to a similar file on the remote system and downloads only +changed files. +

+ +

+The mirror program is generally useful for updating local copies +of remote directory trees. The files fetched need not be Debian files. (Since +mirror is a Perl script, it can also run on non-Unix systems.) +Though the mirror 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. +

+ +
+ +

8.2.5 dpkg-mountable

+ +

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

+ +

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

+ +
+ +

8.3 Must I go into single user mode in order to upgrade a package?

+ +

+No. Packages can be upgraded in place, even in running systems. Debian has a +start-stop-daemon program that is invoked to stop, then restart +running process if necessary during a package upgrade. +

+ +
+ +

8.4 Do I have to keep all those .deb archive files on my disk?

+ +

+No. If you have downloaded the files to your disk (which is not absolutely +necessary, see above for the description of dpkg-ftp), then after you have +installed the packages, you can remove them from your system. +

+ +
+ +

8.5 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!

+ +

+Passing the --log-option to dpkg makes +dpkg log status change updates and actions. It logs both the +dpkg-invokation (e.g. +

+ +
+     2005-12-30 18:10:33 install hello 1.3.18 2.1.1-4
+
+ +

+) and the results (e.g. +

+ +
+     2005-12-30 18:10:35 status installed hello 2.1.1-4
+
+ +

+) If you'd like to log all your dpkg invokations (even those done +using frontends like aptitude), you could add +

+ +
+     log /var/log/dpkg.log
+
+ +

+to your /etc/dpkg/dpkg.cfg. Be sure the created logfile gets +rotated periodically. If you're using logrotate, this can be +achieved by creating a file /etc/logrotate.d/dpkg with contents +

+ +
+     /var/log/dpkg {
+       missingok
+       notifempty
+     }
+
+ +

+More details on dpkg logging can be found in the +dpkg(1) manual page. +

+ +

+aptitude logs the package installations, removals, and upgrades +that it intends to perform to /var/log/aptitude. Note that the +results of those actions are not recorded in this file! +

+ +

+Another way to record your actions is to run your package management session +within the script(1) program. +

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/ch-uptodate.html b/templates/common/doc/FAQ/html/ch-uptodate.html new file mode 120000 index 000000000..37f685277 --- /dev/null +++ b/templates/common/doc/FAQ/html/ch-uptodate.html @@ -0,0 +1 @@ +ch-uptodate.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/footnotes.en.html b/templates/common/doc/FAQ/html/footnotes.en.html new file mode 100644 index 000000000..0d5b7d4c5 --- /dev/null +++ b/templates/common/doc/FAQ/html/footnotes.en.html @@ -0,0 +1,112 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Footnotes + + + + + +
+ +

+The Debian GNU/Linux FAQ +
Footnotes

+ +

1

+ +

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

+ +

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

+ +

+With the advent of package pools (see What's in the +pool directory?, Section 5.10), 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). +

+ +

2

+ +

+dists/stable/main, dists/stable/contrib, +dists/stable/non-free, and dists/unstable/main/, etc. +

+ +

3

+ +

+Historically, packages were kept in the subdirectory of dists +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. +

+ +

+The dists directories are still used for the index files used by +programs like apt. You may also still see paths containing +dists/potato or dists/woody in the Filename header +field of some older packages. +

+ +

4

+ +

+Notice that there are ports that make this tool available with other package +management systems, like Red Hat package manager, also known as +rpm +

+ +

5

+ +

+Although this can also lead to systems with more packages installed than they +actually need to work. +

+ +

6

+ +

+Use the debian-list-subject-REQUEST@lists.debian.org address for +that. +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/footnotes.html b/templates/common/doc/FAQ/html/footnotes.html new file mode 120000 index 000000000..c18fdfb77 --- /dev/null +++ b/templates/common/doc/FAQ/html/footnotes.html @@ -0,0 +1 @@ +footnotes.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/index.en.html b/templates/common/doc/FAQ/html/index.en.html new file mode 100644 index 000000000..952a22550 --- /dev/null +++ b/templates/common/doc/FAQ/html/index.en.html @@ -0,0 +1,311 @@ + + + + + + + + +The Debian GNU/Linux FAQ + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+ +

Abstract

+ +

+This document answers questions frequently asked about Debian GNU/Linux. +

+ +
+ +

Copyright Notice

+ +

+Copyright © 1996-2005 by Software in the Public Interest +

+ +

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

+ +

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

+ +

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

+ +
+ +

Contents

+ + + +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/templates/common/doc/FAQ/html/index.html b/templates/common/doc/FAQ/html/index.html new file mode 120000 index 000000000..0e8542211 --- /dev/null +++ b/templates/common/doc/FAQ/html/index.html @@ -0,0 +1 @@ +index.en.html \ No newline at end of file -- cgit v1.2.3