From 1ec7ddaa62e53173b4e1d2982f2bc0a3c8993fa7 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 20 Dec 2008 11:18:45 +0100 Subject: Updating cd includes. --- includes/lenny | 1 - includes/lenny/common/doc/00-INDEX | 22 + .../lenny/common/doc/FAQ/debian-faq.en.html.tar.gz | Bin 0 -> 118489 bytes includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz | Bin 0 -> 327083 bytes includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz | Bin 0 -> 119684 bytes includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz | Bin 0 -> 59678 bytes .../common/doc/FAQ/html/ch-basic_defs.en.html | 610 +++++ .../lenny/common/doc/FAQ/html/ch-basic_defs.html | 1 + .../lenny/common/doc/FAQ/html/ch-choosing.en.html | 961 +++++++ .../lenny/common/doc/FAQ/html/ch-choosing.html | 1 + .../lenny/common/doc/FAQ/html/ch-compat.en.html | 554 +++++ includes/lenny/common/doc/FAQ/html/ch-compat.html | 1 + .../common/doc/FAQ/html/ch-contributing.en.html | 370 +++ .../lenny/common/doc/FAQ/html/ch-contributing.html | 1 + .../common/doc/FAQ/html/ch-customizing.en.html | 716 ++++++ .../lenny/common/doc/FAQ/html/ch-customizing.html | 1 + .../lenny/common/doc/FAQ/html/ch-faqinfo.en.html | 407 +++ includes/lenny/common/doc/FAQ/html/ch-faqinfo.html | 1 + .../common/doc/FAQ/html/ch-ftparchives.en.html | 756 ++++++ .../lenny/common/doc/FAQ/html/ch-ftparchives.html | 1 + .../lenny/common/doc/FAQ/html/ch-getting.en.html | 451 ++++ includes/lenny/common/doc/FAQ/html/ch-getting.html | 1 + .../lenny/common/doc/FAQ/html/ch-kernel.en.html | 389 +++ includes/lenny/common/doc/FAQ/html/ch-kernel.html | 1 + .../lenny/common/doc/FAQ/html/ch-nexttime.en.html | 377 +++ .../lenny/common/doc/FAQ/html/ch-nexttime.html | 1 + .../common/doc/FAQ/html/ch-pkg_basics.en.html | 1123 +++++++++ .../lenny/common/doc/FAQ/html/ch-pkg_basics.html | 1 + .../lenny/common/doc/FAQ/html/ch-pkgtools.en.html | 1199 +++++++++ .../lenny/common/doc/FAQ/html/ch-pkgtools.html | 1 + .../lenny/common/doc/FAQ/html/ch-redistrib.en.html | 340 +++ .../lenny/common/doc/FAQ/html/ch-redistrib.html | 1 + .../lenny/common/doc/FAQ/html/ch-software.en.html | 639 +++++ .../lenny/common/doc/FAQ/html/ch-software.html | 1 + .../lenny/common/doc/FAQ/html/ch-support.en.html | 679 +++++ includes/lenny/common/doc/FAQ/html/ch-support.html | 1 + .../lenny/common/doc/FAQ/html/ch-uptodate.en.html | 636 +++++ .../lenny/common/doc/FAQ/html/ch-uptodate.html | 1 + .../lenny/common/doc/FAQ/html/footnotes.en.html | 294 +++ includes/lenny/common/doc/FAQ/html/footnotes.html | 1 + includes/lenny/common/doc/FAQ/html/index.en.html | 522 ++++ includes/lenny/common/doc/FAQ/html/index.html | 1 + includes/lenny/common/doc/bug-log-access.txt | 55 + includes/lenny/common/doc/bug-log-mailserver.txt | 140 ++ .../lenny/common/doc/bug-mailserver-refcard.txt | 81 + includes/lenny/common/doc/bug-maint-info.txt | 409 +++ .../lenny/common/doc/bug-maint-mailcontrol.txt | 390 +++ includes/lenny/common/doc/bug-reporting.txt | 362 +++ includes/lenny/common/doc/constitution.txt | 600 +++++ includes/lenny/common/doc/debian-manifesto | 135 + includes/lenny/common/doc/mailing-lists.txt | 1266 ++++++++++ includes/lenny/common/doc/social-contract.txt | 118 + includes/lenny/common/doc/source-unpack.txt | 33 + includes/lenny/install/README.html | 253 ++ includes/lenny/install/README.mirrors.html | 2622 ++++++++++++++++++++ includes/lenny/install/README.mirrors.txt | 658 +++++ includes/lenny/install/README.txt | 143 ++ includes/lenny/install/autorun.inf | 2 + includes/lenny/install/css/debinstall-print.css | 69 + includes/lenny/install/css/debinstall.css | 294 +++ includes/lenny/install/pics/blue-lowerleft.png | Bin 0 -> 294 bytes includes/lenny/install/pics/blue-lowerright.png | Bin 0 -> 266 bytes includes/lenny/install/pics/blue-upperleft.png | Bin 0 -> 280 bytes includes/lenny/install/pics/blue-upperright.png | Bin 0 -> 290 bytes includes/lenny/install/pics/debian-61.png | Bin 0 -> 8033 bytes includes/lenny/install/pics/debian.jpg | Bin 0 -> 8442 bytes includes/lenny/install/pics/dot_bw.gif | Bin 0 -> 43 bytes includes/lenny/install/pics/gradient.png | Bin 0 -> 254 bytes includes/lenny/install/pics/logo-50.jpg | Bin 0 -> 3986 bytes includes/lenny/install/pics/openlogo-nd-50.png | Bin 0 -> 1429 bytes includes/lenny/install/pics/red-lowerleft.png | Bin 0 -> 353 bytes includes/lenny/install/pics/red-lowerright.png | Bin 0 -> 299 bytes includes/lenny/install/pics/red-upperleft.png | Bin 0 -> 321 bytes includes/lenny/install/pics/red-upperright.png | Bin 0 -> 344 bytes includes/lenny/install/tools/README | 13 + includes/lenny/install/tools/diskio.zip | Bin 0 -> 10290 bytes includes/lenny/install/tools/fips20.zip | Bin 0 -> 162110 bytes includes/lenny/install/tools/gzip124.exe | Bin 0 -> 119146 bytes includes/lenny/install/tools/lodlin16.zip | Bin 0 -> 135562 bytes includes/lenny/install/tools/md5sum-w32.zip | Bin 0 -> 70352 bytes includes/lenny/install/tools/rawrite1.zip | Bin 0 -> 11157 bytes includes/lenny/install/tools/rawrite2.zip | Bin 0 -> 15655 bytes includes/lenny/install/tools/rwwrtwin.zip | Bin 0 -> 261448 bytes .../lenny/install/tools/src/md5sum-w32_1.1.dsc | 25 + .../lenny/install/tools/src/md5sum-w32_1.1.tar.gz | Bin 0 -> 7617 bytes includes/lenny/install/tools/unz512x3.exe | Bin 0 -> 236134 bytes 86 files changed, 18731 insertions(+), 1 deletion(-) delete mode 120000 includes/lenny create mode 100644 includes/lenny/common/doc/00-INDEX create mode 100644 includes/lenny/common/doc/FAQ/debian-faq.en.html.tar.gz create mode 100644 includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz create mode 100644 includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz create mode 100644 includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz create mode 100644 includes/lenny/common/doc/FAQ/html/ch-basic_defs.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-basic_defs.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-choosing.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-choosing.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-compat.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-compat.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-contributing.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-contributing.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-customizing.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-customizing.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-faqinfo.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-faqinfo.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-ftparchives.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-ftparchives.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-getting.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-getting.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-kernel.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-kernel.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-nexttime.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-nexttime.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-pkg_basics.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-pkg_basics.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-pkgtools.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-pkgtools.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-redistrib.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-redistrib.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-software.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-software.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-support.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-support.html create mode 100644 includes/lenny/common/doc/FAQ/html/ch-uptodate.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/ch-uptodate.html create mode 100644 includes/lenny/common/doc/FAQ/html/footnotes.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/footnotes.html create mode 100644 includes/lenny/common/doc/FAQ/html/index.en.html create mode 120000 includes/lenny/common/doc/FAQ/html/index.html create mode 100644 includes/lenny/common/doc/bug-log-access.txt create mode 100644 includes/lenny/common/doc/bug-log-mailserver.txt create mode 100644 includes/lenny/common/doc/bug-mailserver-refcard.txt create mode 100644 includes/lenny/common/doc/bug-maint-info.txt create mode 100644 includes/lenny/common/doc/bug-maint-mailcontrol.txt create mode 100644 includes/lenny/common/doc/bug-reporting.txt create mode 100644 includes/lenny/common/doc/constitution.txt create mode 100644 includes/lenny/common/doc/debian-manifesto create mode 100644 includes/lenny/common/doc/mailing-lists.txt create mode 100644 includes/lenny/common/doc/social-contract.txt create mode 100644 includes/lenny/common/doc/source-unpack.txt create mode 100644 includes/lenny/install/README.html create mode 100644 includes/lenny/install/README.mirrors.html create mode 100644 includes/lenny/install/README.mirrors.txt create mode 100644 includes/lenny/install/README.txt create mode 100644 includes/lenny/install/autorun.inf create mode 100644 includes/lenny/install/css/debinstall-print.css create mode 100644 includes/lenny/install/css/debinstall.css create mode 100644 includes/lenny/install/pics/blue-lowerleft.png create mode 100644 includes/lenny/install/pics/blue-lowerright.png create mode 100644 includes/lenny/install/pics/blue-upperleft.png create mode 100644 includes/lenny/install/pics/blue-upperright.png create mode 100644 includes/lenny/install/pics/debian-61.png create mode 100644 includes/lenny/install/pics/debian.jpg create mode 100644 includes/lenny/install/pics/dot_bw.gif create mode 100644 includes/lenny/install/pics/gradient.png create mode 100644 includes/lenny/install/pics/logo-50.jpg create mode 100644 includes/lenny/install/pics/openlogo-nd-50.png create mode 100644 includes/lenny/install/pics/red-lowerleft.png create mode 100644 includes/lenny/install/pics/red-lowerright.png create mode 100644 includes/lenny/install/pics/red-upperleft.png create mode 100644 includes/lenny/install/pics/red-upperright.png create mode 100644 includes/lenny/install/tools/README create mode 100644 includes/lenny/install/tools/diskio.zip create mode 100644 includes/lenny/install/tools/fips20.zip create mode 100644 includes/lenny/install/tools/gzip124.exe create mode 100644 includes/lenny/install/tools/lodlin16.zip create mode 100644 includes/lenny/install/tools/md5sum-w32.zip create mode 100644 includes/lenny/install/tools/rawrite1.zip create mode 100644 includes/lenny/install/tools/rawrite2.zip create mode 100644 includes/lenny/install/tools/rwwrtwin.zip create mode 100644 includes/lenny/install/tools/src/md5sum-w32_1.1.dsc create mode 100644 includes/lenny/install/tools/src/md5sum-w32_1.1.tar.gz create mode 100644 includes/lenny/install/tools/unz512x3.exe (limited to 'includes/lenny') diff --git a/includes/lenny b/includes/lenny deleted file mode 120000 index 9a63c961d..000000000 --- a/includes/lenny +++ /dev/null @@ -1 +0,0 @@ -sid \ No newline at end of file diff --git a/includes/lenny/common/doc/00-INDEX b/includes/lenny/common/doc/00-INDEX new file mode 100644 index 000000000..041eacaa5 --- /dev/null +++ b/includes/lenny/common/doc/00-INDEX @@ -0,0 +1,22 @@ +What's in /debian/doc? + +--- General Documentation +FAQ/ Debian FAQ List in html, postscript, and plain text +constitution.txt Debian Constitution +debian-manifesto How it all started... +mailing-lists.txt How to subscribe to the Debian mailing lists +social-contract.txt Debian Social Contract and Free Software Guidelines +source-unpack.txt How to unpack a Debian source package +debian-keyring.tar.gz PGP keys of all the developers. + + +--- The Bug Tracking System for users +bug-reporting.txt How to report a bug in Debian +bug-log-mailserver.txt Introduction to the bug system request server +bug-log-access.txt Accessing bug reports in the tracking system +bug-mailserver-refcard.txt Mail server's reference card + + +--- Debian Developer's Information +bug-maint-info.txt Developer's information re the bug system +bug-maint-mailcontrol.txt Introduction to the bug control mailserver diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.html.tar.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.html.tar.gz new file mode 100644 index 000000000..abee0f971 Binary files /dev/null and b/includes/lenny/common/doc/FAQ/debian-faq.en.html.tar.gz differ diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz new file mode 100644 index 000000000..3b428a113 Binary files /dev/null and b/includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz differ diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz new file mode 100644 index 000000000..0ff09491e Binary files /dev/null and b/includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz differ diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz new file mode 100644 index 000000000..aeaaa4122 Binary files /dev/null and b/includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz differ diff --git a/includes/lenny/common/doc/FAQ/html/ch-basic_defs.en.html b/includes/lenny/common/doc/FAQ/html/ch-basic_defs.en.html new file mode 100644 index 000000000..cc5565314 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-basic_defs.en.html @@ -0,0 +1,610 @@ + + + + + + + + +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 ] +[ 16 ] +[ 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 12.1. If even that doesn't help, refer to Feedback, Section 16.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. +

+ +

+Debian GNU/Linux is: +

+ + + + +

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

+ +

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

+ +

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

+ +

+For more information about Linux, see What is Linux by Linux Online. +

+ +
+ +

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

+
+
+
+
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 1060 volunteer package maintainers are working on over 18200 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 13.1. +

+
+
+
+
The Universal Operating System:
+
+

+Debian comes with more than +18200 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 5.1 for an overview +of the provided software and see On what +hardware architectures/systems does Debian GNU/Linux run?, Section 4.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 +12.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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-basic_defs.html b/includes/lenny/common/doc/FAQ/html/ch-basic_defs.html new file mode 120000 index 000000000..6bee626aa --- /dev/null +++ b/includes/lenny/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/includes/lenny/common/doc/FAQ/html/ch-choosing.en.html b/includes/lenny/common/doc/FAQ/html/ch-choosing.en.html new file mode 100644 index 000000000..e0403cc09 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-choosing.en.html @@ -0,0 +1,961 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Choosing a Debian distribution + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 3 - Choosing a Debian distribution +

+ +
+ +

+There are many different Debian distributions. Choosing the proper Debian +distribution is an important decission. This section covers some information +useful for users that want to make the choice best suited for their system and +also answers possible questions that might be arising during the process. It +does not deal with "why you should choose Debian" but rather +"which distribution of Debian". +

+ +

+For more information on the available distributions read How many Debian distributions are there?, +Section 6.1. +

+ +
+ +

3.1 Which Debian distribution (stable/testing/unstable) is better for me?

+ +

+The answer is a bit complicated. It really depends on what you intend to do. +One solution would be to ask a friend who runs Debian. But that does not mean +that you cannot make an independent decision. In fact, you should be able to +decide once you complete reading this chapter. +

+ + + + + +

+The following questions (hopefully) provide more detail on these choices. +After reading this whole FAQ, if you still could not make a decision, stick +with the stable distribution. +

+ +
+ +

3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?

+ +

+Try to search the web using a search engine and see if someone else is able to +get it working in stable. Most of the hardware should work fine with stable. +But if you have some state-of-the-art, cutting edge hardware, it might not work +with stable. If this is the case, you might want to install/upgrade to +unstable. +

+ +

+For laptops, http://www.linux-on-laptops.com/ +is a very good website to see if someone else is able to get it to work under +Linux. The website is not specific to Debian, but is nevertheless a tremendous +resource. I am not aware of any such website for desktops. +

+ +

+Another option would be to ask in the debian-user mailing list by sending an +email to debian-user@lists.debian.org . Messages can be posted to the list +even without subscribing. The archives can be read through http://lists.debian.org/debian-user/ +Information regarding subscribing to the list can be found at the location of +archives. You are strongly encourage to post your questions on the +mailing-list than on irc. The mailing-list messages +are archived, so solution to your problem can help others with the same issue. +

+ +
+ +

3.1.2 Will there be different different versions of packages in different distributions?

+ +

+Yes. Unstable has the most recent (latest) versions. But the packages in +unstable are not well tested and might have bugs. +

+ +

+On the other hand, stable contains old versions of packages. But this package +is well tested and is less likely to have any bugs. +

+ +

+The packages in testing fall between these two extremes. +

+ +
+ +

3.1.3 The stable distributions really contains outdated packages. Just look at Kde, Gnome, Xorg or even the kernel. They are very old. Why is it so?

+ +

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

+ +

+On the other hand, packages in testing or unstable can have hidden bugs, +security holes etc., Moreover, some packages in testing and unstable might not +be working as intended. Usually people working on a single desktop prefer +having the latest and most modern set of packages. Unstable is the solution +for this group of people. +

+ +

+As you can see, stability and novelty are two opposing ends of the spectrum. +If stability is required: install stable distribution. If you want to work +with the latest packages, then install unstable. +

+ +
+ +

3.1.4 If I were to decide to change to another distribution, Can I do that?

+ +

+Yes, but it is a one way process. You can go from stable --> testing --> +unstable. But the reverse direction is not "possible". So better be +sure if you are planning to install/upgrade to unstable. +

+ +

+Actually, if you are an expert and if you are willing to spend some time and if +you are real careful and if you know what you are doing, then it might be +possible to go from unstable to testing and then to stable. The installer +scripts are not designed to do that. So in the process, your configuration +files might be lost and.... +

+ +
+ +

3.1.5 Could you tell me whether to install testing or unstable?

+ +

+This is a rather subjective issue. There is no perfect answer but only a +"wise guess" could be made while deciding between unstable and +testing. My personal order of preference is Stable, Unstable and Testing. The +issue is like this: +

+ + + + +

+But there are times when tracking testing would be beneficial as opposed to +unstable. The author such situation due to the gcc transition from gcc3 to +gcc4. He was trying to install the labplot package on a machine +tracking unstable and it could not be installed in unstable as some of its +dependencies have undergone gcc4 transition and some have not. But the package +in testing was installable on a testing machine as the gcc4 transitioned +packages had not "trickled down" to testing. +

+ +
+ +

3.1.6 You are talking about testing being broken. What do you mean by that?

+ +

+Sometimes, a package might not be installable through package management tools. +Sometimes, a package might not be available at all, maybe it was (temporarily) +removed due to bugs or unmet dependencies. Sometimes, a package installs but +does not behave in the proper way. +

+ +

+When these things happen, the distribution is said to be broken (at least for +this package). +

+ +
+ +

3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?

+ +

+The bug fixes and improvements introduced in the unstable distribution trickle +down to testing after a certain number of days. Let's say this threshold is 10 +days. The packages in unstable go into testing only when there are no RC-bugs +reported against them. If there is a RC-bug filed against a package in +unstable, it will not go into testing after the 10 days. +

+ +

+The idea is that, if the package has any problems, it would be discovered by +people using unstable and will be fixed before it enters testing. This keeps +the testing in an usable state for most period of the time. Overall a +brilliant concept, if you ask me. But things are alwasy not so simple. +Consider the following situation: +

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

+The situation can get much more complicated, if say, XYZ depends on 4 other +packages. This could in turn lead to unusable testing distribution for months. +The above scenario which is artificially created by me, can occur in the real +life. But such occurrences are rare. +

+ +
+ +

3.1.8 From an administrator's point of view, Which distribution requires more attention?

+ +

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

+ +
+ +

3.1.9 What happens when a new release is made?

+ +

+This question will not help you in choosing a Debian distribution. But sooner +or later you will face this question. +

+ +

+The stable distribution is currently etch; The next stable distribution will be +called as lenny. Let's consider the particular case as to what happens when +lenny is released as the new stable version. +

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

3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?

+ +

+In most situations it is very easy to figure this out. Take a look at the +/etc/apt/sources.list file. There will be an entry similar to +this: +

+ +
+     deb http://ftp.us.debian.org/debian/ unstable main contrib
+
+ +

+The third field ('unstable' in the above example) indicates the Debian +distribution the system is currently tracking. +

+ +

+You can also use lsb_release (available in the +lsb-release package). If you run this program in an unstable +system you will get: +

+ +
+     $ lsb_release  -a
+     LSB Version:    core-2.0-noarch:core-3.0-noarch:core-3.1-noarch:core-2.0-ia32:core-3.0-ia32:core-3.1-ia32
+     Distributor ID: Debian
+     Description:    Debian GNU/Linux unstable (sid)
+     Release:    unstable
+     Codename:   sid
+
+ +

+However, this is always not that easy. Some systems might have +sources.list files with multiple entries corresponding to +different distributions. This could happen if the administrator is tracking +different packages from different Debian distributions. This is frequently +referred to as apt-pinning. These systems might run a mixture of +distributions. +

+ +
+ +

3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?

+ +

+If you are currently running stable, then in the +/etc/apt/sources.list file the third field will be either etch or +stable. You need to change this to the distribution you want to run. If you +want to run testing, then change the third field of +/etc/apt/sources.list to testing. If you want to run unstable, +then change the third field to unstable. +

+ +

+Currently testing is called lenny. So, if you change the third field of +/etc/apt/sources.list to lenny, then also you will be running +testing. But when lenny becomes stable, you will still be tracking lenny. +

+ +

+Unstable is always called Sid. So if you change the third field of +/etc/apt/sources.list to sid, then you will be tracking unstable. +

+ +

+Currently Debian offers security updates for testing but not for unstable, as +fixes in unstable are directly made to the main archive. So if you are running +unstable make sure that you remove the lines relating to security updates in +/etc/apt/sources.list. +

+ +

+If there is a release notes document available for the distribution you are +upgrading to (even though it has not yet been released) it would be wise to +review it, as it might provide information on how you should upgrade to it. +

+ +

+Nevertheless, once you make the above changes, you can run aptitude +update and then install the packages that you want. Notice that +installing a package from a different distribution might automatically upgrade +half of your system. If you install individual packages you will end up with a +system running mixed distributions. +

+ +

+It might be best in some situations to just fully upgrade to the new +distribution running apt-get dist-upgrade, aptitude +safe-upgrade or aptitude full-upgrade. Read apt's and +aptitude's manual pages for more information. +

+ +
+ +

3.1.12 I am currently tracking testing (lenny). What will happen when a release is made? Will I still be tracking testing or will my machine be running the new stable distribution?

+ +

+It depends on the entries in the /etc/apt/sources.list file. If +you are currently tracking testing, these entries are similar to either: +

+ +
+     deb http://ftp.us.debian.org/debian/ testing main
+
+ +

+or +

+ +
+     deb http://ftp.us.debian.org/debian/ lenny main
+
+ +

+If the third field in /etc/apt/sources.list is 'testing' then you +will be tracking testing even after a release is made. So after lenny is +released, you will be running a new Debian distribution which will have a +different codename. Changes might not be apparent at first but will be evident +as soon as new packages from unstable go over to the testing distribution. +

+ +

+But if the third field contains 'lenny' then you will be tracking stable (since +lenny will then be the new stable distribution). +

+ +
+ +

3.1.13 I am still confused. What did you say I should install?

+ +

+If unsure, the best bet would be stable distribution. +

+ +
+ +

3.2 But what about Knoppix, Linex, Ubuntu, and others?

+ +

+They are not Debian; they are Debian based. Though there are many +similarities and commonalities between them, there are also crucial +differences. +

+ +

+All these distributions have their own merits and are suited to some specific +set of users. For more information, read the information of software distributions based +on Debian available at the Debian website. +

+ +
+ +

3.2.1 I know that Knoppix/Linex/Ubuntu/... is Debian-based. So after installing it on the hard disk, can I use 'apt' package tools on it?

+ +

+These distributions are Debian based. But they are not Debian. You will be +still able to use apt package tools by pointing the +/etc/apt/sources.list file to these distributions' repositories. +But then you are not running Debian, you are running a different distribution. +They are not the same. +

+ +

+In most situations if you stick with one distribution you should use that and +not mix packages from other distributions. Many common breakages arise due to +people running a distribution and trying to install Debian packages from other +distributions. The fact that they use the same formatting and name (.deb) does +not make them inmediately compatible. +

+ +

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

+ +

+If you want Debian, it is best to install Debian from the get-go. Although it +is possible to install Debian through other distributions, such as Knoppix, the +procedure calls for expertise. If you are reading this FAQ, I would assume +that you are new to both Debian and Knoppix. In that case, save yourself a lot +of trouble later and install Debian right at the beginning. +

+ +
+ +

3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?

+ +

+You are advised not to use the Debian forums (either mailing lists or IRC) for +help as people might advise you thinking that you are running a Debian system +and the "fixes" they provide might not be suited to what you are +running. They might even worsen the problem you are facing. +

+ +

+Use the forums of the specific distribution you are using first. If you do not +get help or the help you get does not fix your problem you might want to try +asking in Debian forums, but keep the advise of the previous paragraph in mind. +

+ +
+ +

3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?

+ +

+Consider the change from a Debian-based distribution to Debian just like a +change from one operating system to another one. You should make a backup of +all your date and reinstall the operating system from scratch. You should not +attempt to "upgrade" to Debian using the package management tools as +you might end up with an unusable system. +

+ +

+If all your user data (i.e. your /home) is under a separate +partition migrating to Debian is actually quite simple, you just have to tell +the installation system to mount (but not reformat) that partition when +reinstalling. Making backups of your data, as well as your previous system's +configuration (i.e. /etc/ and, maybe, /var/) is +still encouraged. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-choosing.html b/includes/lenny/common/doc/FAQ/html/ch-choosing.html new file mode 120000 index 000000000..5b6a7051a --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-choosing.html @@ -0,0 +1 @@ +ch-choosing.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-compat.en.html b/includes/lenny/common/doc/FAQ/html/ch-compat.en.html new file mode 100644 index 000000000..375bff45d --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-compat.en.html @@ -0,0 +1,554 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Compatibility issues + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

4.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, 4.0, contains a complete, binary +distribution for the following architectures: +

+ +

+i386: this covers systems based on Intel and compatible processors, +including Intel's 386, 486, Pentium, Pentium Pro, Pentium II (both Klamath and +Celeron), and Pentium III, and most compatible processors by AMD, Cyrix and +others. +

+ +

+amd64: this covers systems based on AMD 64bit CPUs with AMD64 +extension and all Intel CPUs with EM64T extension, and a common 64bit +userspace. +

+ +

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

+ +

+Support for the m68k architecture was dropped in this release, because +it did not meet the criteria set by the Debian Release Managers. This +architecture covers Amigas and ATARIs having a Motorola 680x0 processor for +x>=2; with MMU. However, the port is still active and available for +installation even if not a part of this official stable release and might be +reactivated for future releases. +

+ +

+For more information on the available ports see the ports pages at the website. +

+ +

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

+ +
+ +

4.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. The Debian Etch release is Certified for LSB Release 3.1, see +the Linux +Foundation Certification webpage. Discussion and coordination of +efforts towards ensuring Debian meets the requirements of the Linux Standard +Base is taking place on the debian-lsb mailing list. +

+ +
+ +

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

+ +
+ +

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

+
+
+ +
+ +

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

+ +
+ +

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

+ +
+ +

4.7 Why can't I install AccelX?

+ +

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

+ +
+ +

4.8 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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-compat.html b/includes/lenny/common/doc/FAQ/html/ch-compat.html new file mode 120000 index 000000000..069644986 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-compat.html @@ -0,0 +1 @@ +ch-compat.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-contributing.en.html b/includes/lenny/common/doc/FAQ/html/ch-contributing.en.html new file mode 100644 index 000000000..db2d6e329 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-contributing.en.html @@ -0,0 +1,370 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 13 - 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. +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
+ +

13.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 as originally planned by +FSF. We still communicate with FSF, and we cooperate in sending them changes +to GNU software and in asking our users to donate to FSF and the GNU project. +

+ +

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

+ +
+ +

13.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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-contributing.html b/includes/lenny/common/doc/FAQ/html/ch-contributing.html new file mode 120000 index 000000000..4185524fd --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-contributing.html @@ -0,0 +1 @@ +ch-contributing.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-customizing.en.html b/includes/lenny/common/doc/FAQ/html/ch-customizing.en.html new file mode 100644 index 000000000..94671123b --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-customizing.en.html @@ -0,0 +1,716 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

+If you do this from within a user's shell or a GUI environment you have to +logout and login again to become an effective member of that group. To check +which groups you belong to run groups. +

+ +

+Notice that, since the introduction of udev if you change the +permissions of a hardware peripheral they might be be adjusted for some devices +when the system starts, if this happens to the hardware peripherals you are +instered in you will have to adjust the rules at /etc/udev. +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ + + + +

+One might, for example, cause the script foo to execute at +boot-up, by putting it in /etc/init.d/ and running +update-rc.d foo defaults 19. The argument `defaults' +refers to the default runlevels, which means (at least in absence of any LSB +comment block to the contrary) to start the service in runlevels 2 through 5, +and to stop the service in runlevels 0, 1 and 6. (Any LSB Default-Start and +Default-Stop directives in foo take precedence when using the +sysv-rc version of update-rc.d, but are ignored by the current (v0.8.10) +file-rc version of update-rc.d.) The argument `19' ensures that +foo is called after all scripts whose number is less than 19 have +completed, and before all scripts whose number is 20 or greater. +

+ +
+ +

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

+ +
+ +

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

+ + + +

+Run dpkg-divert --list to see which diversions are currently +active on your system. +

+ +

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

+ +
+ +

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

+ +
+ +

11.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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-customizing.html b/includes/lenny/common/doc/FAQ/html/ch-customizing.html new file mode 120000 index 000000000..1cfdfaae7 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-customizing.html @@ -0,0 +1 @@ +ch-customizing.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-faqinfo.en.html b/includes/lenny/common/doc/FAQ/html/ch-faqinfo.en.html new file mode 100644 index 000000000..9edac2076 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-faqinfo.en.html @@ -0,0 +1,407 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

16.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 debian-faq package. +

+ +
+ +

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

+ +

+This document is available in the debian-faq package. +Translations are available in debian-faq-de, +debian-faq-fr and other packages. +

+ +

+The original SGML files used to create this document are also available in +debian-faq's source package, or in SVN at: +svn://svn.debian.org/svn/ddp/manuals/trunk/debian-faq and http://svn.debian.org/viewsvn/ddp/manuals/trunk/debian-faq/. +

+ +
+ +

16.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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-faqinfo.html b/includes/lenny/common/doc/FAQ/html/ch-faqinfo.html new file mode 120000 index 000000000..0f759b493 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-faqinfo.html @@ -0,0 +1 @@ +ch-faqinfo.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-ftparchives.en.html b/includes/lenny/common/doc/FAQ/html/ch-ftparchives.en.html new file mode 100644 index 000000000..0efd28ab9 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-ftparchives.en.html @@ -0,0 +1,756 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

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

+ +
+ +

6.1 How many Debian distributions are there?

+ +

+There are three major 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 +6.5.1). Next to these, there is the "oldstable" distribution +(that's just the one from before "stable"), and the +"experimental" distribution. +

+ +

+Experimental is used for packages which are still being developed, and with a +high risk of breaking your system. It's used by developers who'd like to study +and test bleeding edge software. Users shouldn't be using packages from here, +because they can be dangerous and harmful even for the most experienced people. +

+ +

+See Choosing a Debian distribution, Chapter 3 +for help when choosing a Debian distribution. +

+ +
+ +

6.2 What are all those names like etch, lenny, 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 etch (i.e. +Debian GNU/Linux 4.0) and testing is a symbolic link to +lenny. This means that etch is the current stable +distribution and lenny 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 6.3). +

+ +
+ +

6.2.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, woody for release 3.0, +sarge for release 3.1, and etch for release 4.0. +

+ +
+ +

6.2.2 Where do these codenames come from?

+ +

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

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

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

+ +

+[2] +

+ +
+ +

6.4 What does the stable directory contain?

+ + + + +
+ +

6.5 What does the testing distribution 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. +

+ +
+ +

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

+ +
+ +

6.6 What does the unstable distribution 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'. +

+ +
+ +

6.7 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 6.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 this FAQ, the bug reporting system +instructions, etc. +

+
+
+
+
/indices/:
+
+

+various indices of the site (the Maintainers file and the override files). +

+
+
+
+
/project/:
+
+

+mostly developer-only materials and some miscellaneous files. +

+
+
+ +
+ +

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

+ +

+Within each of the major directory trees[3], 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 4.1. +

+ +

+The index files in binary-* are called Packages(.gz, .bz2) and they include a +summary of each binary package that is included in that distribution. The +actual binary packages reside in the top level 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, .bz2). +

+ +

+Last but not least, there's a set of subdirectories meant for the installation +system index files, they are at +debian-installer/binary-architecture. +

+ +
+ +

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

+ +
+ +

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

+ +

+[4] +

+ +
+ +

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

+ +
+ +

6.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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-ftparchives.html b/includes/lenny/common/doc/FAQ/html/ch-ftparchives.html new file mode 120000 index 000000000..cdad69f63 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-ftparchives.html @@ -0,0 +1 @@ +ch-ftparchives.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-getting.en.html b/includes/lenny/common/doc/FAQ/html/ch-getting.en.html new file mode 100644 index 000000000..16d506c41 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-getting.en.html @@ -0,0 +1,451 @@ + + + + + + + + +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 ] +[ 16 ] +[ 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 4.0, a.k.a. the `stable' distribution or etch
+
+

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

+
+
+
+
the `testing' distribution, currently called lenny
+
+

+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?, Section 6.1 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. +

+ +

+Please refer to Debian GNU/Linux on +CDs for more information about CD (and DVD) images. +

+ +
+ +

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

+ +

+Installing Debian from CD is straightforward: configure your system for booting +off a CD, insert your CD, and reboot. Your system will now be running the +Debian Installer. See the Debian GNU/Linux +Installation Guide for more information. +

+ +
+ +

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 -> etch/
+      /dists/stable -> etch/
+      /dists/testing -> etch/
+      /dists/unstable -> etch/
+
+ +

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

+ +
+ +

2.7 Are there any alternative strategies for booting the system installer?

+ +

+Yes. Apart from CD or DVD, you can install Debian GNU/Linux by booting from +floppy disks, USB memory stick, directly from hard disk, or using TFTP net +booting. For installing on multiple computers it's possible to do fully +automatic installations. NB: not all methods are supported by all computer +architectures. Once the installer has booted, the rest of the system can be +downloaded over the network, or installed from local media. See the Debian GNU/Linux +Installation Guide for more information. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-getting.html b/includes/lenny/common/doc/FAQ/html/ch-getting.html new file mode 120000 index 000000000..568d808b9 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-getting.html @@ -0,0 +1 @@ +ch-getting.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-kernel.en.html b/includes/lenny/common/doc/FAQ/html/ch-kernel.en.html new file mode 100644 index 000000000..58781c998 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-kernel.en.html @@ -0,0 +1,389 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

10.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 +linux-image-version package just by running the command +

+ +
+     make-kpkg --initrd 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 +linux-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. +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

+Yes. The linux-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 linux-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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-kernel.html b/includes/lenny/common/doc/FAQ/html/ch-kernel.html new file mode 120000 index 000000000..125039fb4 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-kernel.html @@ -0,0 +1 @@ +ch-kernel.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-nexttime.en.html b/includes/lenny/common/doc/FAQ/html/ch-nexttime.en.html new file mode 100644 index 000000000..cd6c875e5 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-nexttime.en.html @@ -0,0 +1,377 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

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

+ +
+ +

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

+ +

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

+ +

+Specifically for Debian lenny, we're working on things like the following: +

+ + + + +
+ +

15.2 Faster booting: Dependency based boot sequence

+ +

+Work is being done on converting the +Debian boot sequence to use dynamic and dependency based ordering +instead of hardcoded sequence numbers. Once that's finished, Debian systems +will boot much faster. +

+ +
+ +

15.3 Improvements in the Debian Installer

+ +

+Lots of work has been done on the Debian Installer, resulting in major +improvements. We'll mention just two of them here. +

+ +

+Starting the installer from Microsoft Windows: It is now possible to start the +installer directly from Microsoft Windows without the need to change BIOS +settings. Upon insertion of a CD-ROM, DVD-ROM or USB stick, an autorun program +will be started, offering a step-by-step process to start the Debian Installer. +

+ +

+The debian-installer now includes experimental support for installing Debian on +systems with Serial ATA RAID. +

+ +
+ +

15.4 More architectures

+ +

+Complete Debian system on other architectures such as ARM EABI (referred to as +"armel") (next to the old "arm") will likely get supported +with lenny. Support for SuperH is expected soon. +Notice that even though some architectures are dropped for a given the release +there still might be a way to install and upgrade using the latest +sid. +

+ +
+ +

15.5 More kernels

+ +

+In addition to Debian GNU/Hurd, Debian is being ported also to BSD kernels, +namely to FreeBSD. This port +runs on both AMD64 ("kfreebsd-amd64") and traditional Intel +("kfreebsd-i386"). +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-nexttime.html b/includes/lenny/common/doc/FAQ/html/ch-nexttime.html new file mode 120000 index 000000000..da23d4849 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-nexttime.html @@ -0,0 +1 @@ +ch-nexttime.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-pkg_basics.en.html b/includes/lenny/common/doc/FAQ/html/ch-pkg_basics.en.html new file mode 100644 index 000000000..72799b217 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-pkg_basics.en.html @@ -0,0 +1,1123 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

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

+ +
+ +

+This chapter touches on some lower level internals of Debian package +management. If you're interested mainly in usage of the relevant +tools, skip to chapters The Debian package +management tools, Chapter 8 and/or Keeping +your Debian system up-to-date, Chapter 9. +

+ +
+ +

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

+ +

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

+ + + + + +
+ +

7.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) if you need to do lowlevel manipulations on +.deb files. +

+ +
+ +

7.3 Why are Debian package file names so long?

+ +

+The Debian binary package file names conform to the following convention: +<foo>_<VersionNumber>-<DebianRevisionNumber>_<DebianArchitecture>.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. +

+ +

+The AAA component identifies the processor for which the package +was built. This is commonly i386, which refers to chips +compatible to Intel's 386 or later versions. For other possibilities review +Debian's FTP directory structure at What are all those directories at the +Debian FTP archives?, Section 6.7. For details, see the description of +"Debian architecture" in the manual page +dpkg-architecture(1). +

+ +
+ +

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

+ +

+The Priority indicates how important is this package for installation, so that +semi-intelligent software like dselect or aptitude can sort the package into a +category of e.g. packages optionally installed. See What is an Essential, Required, +Important, Standard, Optional, or Extra +package?, Section 7.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". +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ + + + + + +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

+The preferred way to do this is by using various wrapper tools. We'll show how +it's done using the devscripts tools. Install this package if you +haven't done so already. +

+ +

+Now, first get the source package: +

+ +
+     apt-get source foo
+
+ +

+and change to the source tree: +

+ +
+     cd foo-*
+
+ +

+Then install needed build-dependencies (if any): +

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

+Then create a dedicated version of your own build (so that you won't get +confused later when Debian itself releases a new version) +

+ +
+     dch -l local 'Blah blah blah'
+
+ +

+And finally build your package +

+ +
+     debuild -us -uc
+
+ +

+If everything worked out fine, you should now be able to install your package +by running +

+ +
+     sudo dpkg -i ../*.deb
+
+ +

+If you prefer to do things manually, and don't want to use +devscripts, follow this procedure: +

+ +

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

+ +
+ +

7.15 How do I create Debian packages myself?

+ +

+For a 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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-pkg_basics.html b/includes/lenny/common/doc/FAQ/html/ch-pkg_basics.html new file mode 120000 index 000000000..98c97fece --- /dev/null +++ b/includes/lenny/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/includes/lenny/common/doc/FAQ/html/ch-pkgtools.en.html b/includes/lenny/common/doc/FAQ/html/ch-pkgtools.en.html new file mode 100644 index 000000000..391e6560f --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-pkgtools.en.html @@ -0,0 +1,1199 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

8.1.1 dpkg

+ +

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

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

8.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[5] 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. +

+ +
+ +

8.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 preferred program for package management +from console both for package installations and package or system upgrades. +

+ +

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

+ +
+ +

8.1.4 synaptic

+ +

+synaptic is a graphical package manager. It enables you to +install, upgrade and remove software packages in a user friendly way. Next to +all features offered by aptitude, it also has a feature for editing the list of +used repositories, and supports browsing all available documentation related to +a package. See the Synaptic +Website for more information. +

+ +
+ +

8.1.5 tasksel

+ +

+When you want to perform a specific task it might be difficult to find the +appropiate suite of packages that fill your need. The Debian developers have +defined tasks, a task is a collection of several individual Debian +packages all related to a specific activity. Tasks can be installed through +the tasksel program or through aptitude. +

+ +

+The Debian installer will typically install automaticaly the task associated +with a standard system and a desktop environment. The specific desktop +environment installed will depend on the CD/DVD media used, most commonly it +will be the GNOME desktop (gnome-desktop task). Also, depending +on your selections throughout the installation process, tasks might be +automatically installed in your system. For example, if you selected a +language, the task associated with it will be installed automatically too and +if you are running in a laptop system the installer recognises the +laptop task will be installed too. +

+ +
+ +

8.1.6 Other package management tools

+ +
+ +

8.1.6.1 dselect

+ +

+This program is a menu-driven interface to the Debian package management +system. For woody and earlier releases, this was the main package management +interface for for first-time installations, but currently users are encouraged +to use aptitude instead. Some users might feel more comfortable +using aptitude and it is also recommended over +dselect for large-scale upgrades. For more information on +aptitude please see aptitude, Section +8.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). +

+ + + + + +
+ +

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

+ +
+ +

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

+ + + + + +
+ +

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

+ +
+ +

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

8.4 How to display the files of a package installed?

+ +

+To list all the files provided by the installed package foo +execute the command +

+ +
+     dpkg --listfiles foo
+
+ +

+Note that the files created by the installation scripts aren't displayed. +

+ +
+ +

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

+ +

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

+ + + + +
+ +

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

+ +

+Some packages are split in program (`foo') and data (`foo-data') (or in `foo' +and `foo-doc'). This is true for many games, multimedia applications and +dictionaries in Debian and has been introduced since some users might want to +access the raw data without installing the program or because the program can +be run without the data itself, making it optional. +

+ +

+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 8.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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-pkgtools.html b/includes/lenny/common/doc/FAQ/html/ch-pkgtools.html new file mode 120000 index 000000000..6c9eeed19 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-pkgtools.html @@ -0,0 +1 @@ +ch-pkgtools.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-redistrib.en.html b/includes/lenny/common/doc/FAQ/html/ch-redistrib.en.html new file mode 100644 index 000000000..77bbf561b --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-redistrib.en.html @@ -0,0 +1,340 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

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

+ +
+ +

14.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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-redistrib.html b/includes/lenny/common/doc/FAQ/html/ch-redistrib.html new file mode 120000 index 000000000..f1826236b --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-redistrib.html @@ -0,0 +1 @@ +ch-redistrib.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-software.en.html b/includes/lenny/common/doc/FAQ/html/ch-software.en.html new file mode 100644 index 000000000..2c2d7458e --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-software.en.html @@ -0,0 +1,639 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

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

+ +
+ +

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

+ +

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

+ + + + + + + +

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

+ +
+ +

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

+ +
+ +

5.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 +thirty "sections" of the Debian archive. +

+ +
+ +

5.4 How can I install a developer's environment to build packages?

+ +

+If you want to build packages in your Debian system you will need to have a +basic development environment, including a C/C++ compiler and some other +essential packages. In order to install this environment you just need to +install the build-essential. This package is a meta-package or +place-holder package which depends on the standard development tools one needs +to build a Debian package. +

+ +

+Some software can, however, need additional software to be rebuilt, including +library headers or additional tools such as autoconf or +gettext. Debian provides many of the tools needed to build other +software as Debian packages. +

+ +

+Finding which software is precisely required can be tricky, however, unless you +are planning on rebuilding Debian packages. This last task is rather easy to +do, as official packages have to include a list of the additional software +(besides the packages in build-essential) needed to build the +pacakge, this is known as Build-Dependencies. To install all the +packages needed to build a given source package and then build said source +package you can just run: +

+ +
+     # apt-get build-dep foo
+     # apt-get source --build foo
+
+ +

+Notice that if you want to build the Linux kernels distributed by Debian you +will want to install also the kernel-package package. For more +information see What tools does +Debian provide to build custom kernels?, Section 10.2. +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

5.7 (How) Does Debian support Java?

+ +

+Several free implementations of Java technology are available as +Debian packages, providing both Java Development Kits as well as Runtime +Environments. You can write, debug and run Java programs using Debian. +

+ +

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

+ +

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

+ +
+ +

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

5.9 How does Debian support non-English languages?

+ + + + +
+ +

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

+ +
+ +

5.11 Where is qmail/ezmlm/djbdns?

+ +

+Dan J. Bernstein used to distribute all software he has written +with a restrictive license which does not allow modified binaries to be +distributed. In november 2007 however, Bernstein said "[...] i have +decided to put all of my future and [...] past software into the public +domain". See FAQ from +distributors for his distribution terms. +

+ +

+As of 2008-04, daemontools, djbdns and +ucspi-tcp are shipped with Debian lenny (in main). As of this +writing (2008-04), qmail is not yet packaged for Debian main; see +Bug #457318 (ITP +qmail) for the current status. +

+ +

+As of 2008-04, publicfile and ezmlm were still not +free software. For ezmlm, there's the ezmlm-src +package in the non-free area. +

+ +
+ +

5.12 Where is a player for Flash (SWF)?

+ +

+Debian ships both gnash and swfdec: two free SWF +movie players. +

+ +
+ +

5.13 Where is Google Earth?

+ +

+Google Earth is available for GNU/Linux from Google's web site, but is not only +not Free Software, but is completely undistributable by a third party. +However, googleearth-package (in the contrib-section) might be +helpful in using this software. +

+ +
+ +

5.14 Where is VoIP software?

+ +

+Two main open protocols are used for Voice Over IP: SIP and H.323. Both are +implemented by a wide variety of software in Debian main. ekiga +is one of the popular clients. +

+ +
+ +

5.15 I have a wireless network card which doesn't work with Linux. What should I do?

+ +

+Buy one which does :) +

+ +

+Alternatively, use ndiswrapper to use a driver for Windows (if you +have one) on your Linux system. See the Debian Wiki ndiswapper +page for more information. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-software.html b/includes/lenny/common/doc/FAQ/html/ch-software.html new file mode 120000 index 000000000..f75c0ab2c --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-software.html @@ -0,0 +1 @@ +ch-software.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-support.en.html b/includes/lenny/common/doc/FAQ/html/ch-support.en.html new file mode 100644 index 000000000..5036cb539 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-support.en.html @@ -0,0 +1,679 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

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

+ +
+ +

12.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, or by using `yelp'. +

+ +
+ +

12.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. We'll give some details on that, and mention some other +useful resources. Even more resources are listed at the Debian Support webpage. +

+ +
+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ + + + + + +
+ +

12.2.2 Web forums

+ +

+debianHELP and Debian User Forums are web forums +on which you can submit questions about Debian and have them answered by other +users. (These are not officially part of the Debian project.) +

+ +
+ +

12.2.3 Wiki

+ +

+Solutions to common problems, howto's, guides, tips and other documentation can +be found at the constantly changing Debian Wiki. +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ + + + +
+ +

12.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. Once it has been dealt with, it is marked as such. +

+ +

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

+ +
+ +

12.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 add additional information to the +existing bug report. +

+ +

+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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-support.html b/includes/lenny/common/doc/FAQ/html/ch-support.html new file mode 120000 index 000000000..978d556ab --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-support.html @@ -0,0 +1 @@ +ch-support.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/ch-uptodate.en.html b/includes/lenny/common/doc/FAQ/html/ch-uptodate.en.html new file mode 100644 index 000000000..33cc9f08e --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-uptodate.en.html @@ -0,0 +1,636 @@ + + + + + + + + +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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +
Chapter 9 - 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. +

+ +
+ +

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

+ +
+ +

9.1.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://ftp.us.debian.org/debian stable main contrib non-free
+
+ +

+You can replace ftp.us.debian.org with the name of a faster Debian mirror near +you. See the mirror list at http://www.debian.org/mirror/list +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 8.1.3. +

+ +
+ +

9.1.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 9.1.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 8.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 8.1.6.1. +

+ +

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

+ +
+ +

9.1.3 aptitude

+ +

+aptitude is a text-based interface to the Debian package system. +It allows the user to view the list of packages and to perform package +management tasks such as installing, upgrading, and removing packages (see aptitude, Section 8.1.3). Actions +may be performed from a visual interface or from the command-line. +

+ +

+In command line, the actions are similar to that of APT, so to upgrade your +system run +

+ +
+     aptitude update
+
+ +

+followed by +

+ +
+     aptitude dist-upgrade
+
+ +

+To upgrade from a preview release, aptitude is the tool +recommended. Read the Release Notes at http://www.debian.org/releases/stable/releasenotes. +

+ +

+For details, see the manual page aptitude(8), and the file +/usr/share/aptitude/README +

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

+No. If you have downloaded the files to your disk then after you have +installed the packages, you can remove them from your system, e.g. by running +aptitude clean. +

+ +
+ +

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

+ +
+ +

9.5 Can I automatically update the system?

+ +

+Yes. You can use cron-apt, this tool updates the system at +regular interval by using a cron job. By default it just updates the package +list and download new packages without installing. +

+ +

+Note: Automatic upgrade of packages is NOT recommended in +testing or unstable systems as this might bring unexpected +behaviour and remove packages without notice. +

+ +
+ +

9.6 I have several machines how can I download the updates only one time?

+ +

+If you have more than one Debian machine on your network, it is useful to use +apt-proxy to keep all of your Debian systems up-to-date. +

+ +

+apt-proxy reduces the bandwidth requirements of Debian mirrors by +restricting the frequency of Packages, Releases and Sources file updates from +the back end and only doing a single fetch for any file, independently of the +actual request it from the proxy. apt-proxy automatically builds +a Debian HTTP mirror based on requests which pass through the proxy. +

+ +

+For more details, see the apt-proxy homepage at http://apt-proxy.sourceforge.net/ +

+ +

+Of course, you can get the same benefit if you are already using a standard +caching proxy and all your systems are configured to use it. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/ch-uptodate.html b/includes/lenny/common/doc/FAQ/html/ch-uptodate.html new file mode 120000 index 000000000..37f685277 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-uptodate.html @@ -0,0 +1 @@ +ch-uptodate.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/footnotes.en.html b/includes/lenny/common/doc/FAQ/html/footnotes.en.html new file mode 100644 index 000000000..881269fa1 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/footnotes.en.html @@ -0,0 +1,294 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Footnotes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +

+The Debian GNU/Linux FAQ +
Footnotes

+ +

1

+ +

+These have been, however, rebranded and are provided with different names due +to trademark issues +

+ +

2

+ +

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

+ +

3

+ +

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

+ +

4

+ +

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

+ +

5

+ +

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

+ +

6

+ +

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

+ +

7

+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/footnotes.html b/includes/lenny/common/doc/FAQ/html/footnotes.html new file mode 120000 index 000000000..c18fdfb77 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/footnotes.html @@ -0,0 +1 @@ +footnotes.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/FAQ/html/index.en.html b/includes/lenny/common/doc/FAQ/html/index.en.html new file mode 100644 index 000000000..c7115e0d1 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/index.en.html @@ -0,0 +1,522 @@ + + + + + + + + +The Debian GNU/Linux FAQ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ 16 ] +[ 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, portions copyright © 2004, 2005, 2006 Kamaraju Kusumanchi +

+ +

+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 ] +[ 16 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 4.0.3, 6 August 2008
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/lenny/common/doc/FAQ/html/index.html b/includes/lenny/common/doc/FAQ/html/index.html new file mode 120000 index 000000000..0e8542211 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/index.html @@ -0,0 +1 @@ +index.en.html \ No newline at end of file diff --git a/includes/lenny/common/doc/bug-log-access.txt b/includes/lenny/common/doc/bug-log-access.txt new file mode 100644 index 000000000..c8fa75f57 --- /dev/null +++ b/includes/lenny/common/doc/bug-log-access.txt @@ -0,0 +1,55 @@ +Methods of accessing the bug tracking system logs + +Accessing active bug reports + + Each message received at or sent by the bug processing system is + logged and made available in a number of ways. + + The primary access method is to use the web pages. See the forms on + the main BTS page at http://bugs.debian.org/ + + There is a mailserver which can send bug reports as plain text on + request. To use it send the word help as the sole contents of an email + to request@bugs.debian.org (the Subject of the message is ignored), or + read the instructions on the World Wide Web or in the file + bug-log-mailserver.txt. + +Accessing archived bug reports + + Each closed bug report is archived 28 days after the last message + relating to it is received and filed. This means that it is no longer + possible to access it or change anything about it using the control + and service bots. However, the reports are still accessible for + viewing. + + You can search the bug report archive using the WWW forms at + http://bugs.debian.org/, simply select the "archived bugs" option. + + Note that it doesn't contain the oldest closed bug reports, only those + after #40000, approximately. + +Accessing the raw bug data + + If you need to get hold of the raw data used by the bug tracking + system, you can mirror it using rsync from bugs-mirror.debian.org. The + relevant modules are bts-spool-db (for the active bug spool), + bts-spool-archive (for bugs that have been closed for a while and thus + archived), and bts-spool-index (for the bug index files). + + At the time of writing, the active spool is about 2.5GB and the + archived spool is about 10GB. If you only need a sample for testing + purposes, please consider downloading only part of the active spool + rather than the whole thing. + + Please do not rely on *.status files in the bug spools, as they are + obsolete, for compatibility purposes only, and will be removed at some + point in the future. Use the *.summary files instead. + _________________________________________________________________ + + Debian BTS administrators + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/lenny/common/doc/bug-log-mailserver.txt b/includes/lenny/common/doc/bug-log-mailserver.txt new file mode 100644 index 000000000..447a059f7 --- /dev/null +++ b/includes/lenny/common/doc/bug-log-mailserver.txt @@ -0,0 +1,140 @@ +Introduction to the bug system request server + + There is a mailserver which can send the bug reports and indices as + plain text on request. + + To use it you send a mail message to request@bugs.debian.org. The + Subject of the message is ignored, except for generating the Subject + of the reply. + + The body you send should be a series of commands, one per line. You'll + receive a reply which looks like a transcript of your message being + interpreted, with a response to each command. No notifications are + sent to anyone for the commands listed here and the mail isn't logged + anywhere publicly available. + + Any text on a line starting with a hash sign # is ignored; the server + will stop processing when it finds a line with a control terminator ( + quit, thank you, or two hyphens are common examples). It will also + stop if it encounters too many unrecognised or badly-formatted + commands. If no commands are successfully handled it will send the + help text for the server. + +Commands available + + send bugnumber + send-detail bugnumber + Requests the transcript for the bug report in question. + send-detail sends all of the "boring" messages in the + transcript as well, such as the various auto-acks. + + index [full] + index-summary by-package + index-summary by-number + Request the full index (with full details, and including done + and forwarded reports), or the summary sorted by package or by + number, respectively. + + index-maint + Requests the index page giving the list of maintainers with + bugs (open and recently-closed) in the tracking system. + + index maint maintainer + Requests the index pages of bugs in the system for the + maintainer maintainer. The search term is an exact match. The + bug index will be sent in a separate message. + + index-packages + Requests the index page giving the list of packages with bugs + (open and recently-closed) in the tracking system. + + index packages package + Requests the index pages of bugs in the system for the package + package. The search term is an exact match. The bug index will + be sent in a separate message. + + send-unmatched [this|0] + send-unmatched last|-1 + send-unmatched old|-2 + Requests logs of messages not matched to a particular bug + report, for this week, last week and the week before. (Each + week ends on a Wednesday.) + + getinfo filename + Request a file containing information about package(s) and or + maintainer(s) - the files available are: + + maintainers + The unified list of packages' maintainers, as used by the + tracking system. This is derived from information in the + Packages files, override files and pseudo-packages files. + + override.distribution + override.distribution.non-free + override.distribution.contrib + override.experimental + Information about the priorities and sections of packages + and overriding values for the maintainers. This + information is used by the process which generates the + Packages files in the FTP archive. Information is + available for each of the main distribution trees + available, by their codewords. + + pseudo-packages.description + pseudo-packages.maintainers + List of descriptions and maintainers respectively for + pseudo-packages. + + refcard + Requests that the mailservers' reference card be sent in plain + ASCII. + + help + Requests that this help document be sent by email in plain + ASCII. + + quit + stop + thank + thanks + thankyou + thank you + -- + Stops processing at this point of the message. After this you + may include any text you like, and it will be ignored. You can + use this to include longer comments than are suitable for #, + for example for the benefit of human readers of your message + (reading it via the tracking system logs or due to a CC or + BCC). + + #... + One-line comment. The # must be at the start of the line. + + debug level + Sets the debugging level to level, which should be a + nonnegative integer. 0 is no debugging; 1 is usually + sufficient. The debugging output appears in the transcript. It + is not likely to be useful to general users of the bug system. + + There is a reference card for the mailservers, available via the WWW, + in bug-mailserver-refcard.txt or by email using the refcard command + (see above). + + If you wish to manipulate bug reports you should use the + control@bugs.debian.org address, which understands a superset of the + commands listed above. This is described in another document, + available on the WWW, in the file bug-maint-mailcontrol.txt, or by + sending help to control@bugs. + + In case you are reading this as a plain text file or via email: an + HTML version is available via the bug system main contents page + http://www.debian.org/Bugs/. + _________________________________________________________________ + + Debian BTS administrators + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/lenny/common/doc/bug-mailserver-refcard.txt b/includes/lenny/common/doc/bug-mailserver-refcard.txt new file mode 100644 index 000000000..04a075b9c --- /dev/null +++ b/includes/lenny/common/doc/bug-mailserver-refcard.txt @@ -0,0 +1,81 @@ +Mail servers' reference card + + Full documentation of the mail servers is available on the WWW, in the + files bug-log-mailserver.txt and bug-maint-mailcontrol.txt or by + sending the word help to each mailserver. + +Synopsis of commands available at request@bugs.debian.org + + * send bugnumber + * send-detail bugnumber + * index [full] + * index-summary by-package + * index-summary by-number + * index-maint + * index maint maintainer + * index-packages + * index packages package + * send-unmatched [this|0] + * send-unmatched last|-1 + * send-unmatched old|-2 + * getinfo filename (ftp.debian.org/debian/doc/*) + * help + * refcard + * quit|stop|thank...|--... + * #... (comment) + * debug level + +Synopsis of extra commands available at control@bugs.debian.org + + * reassign bugnumber package [ version ] + * severity bugnumber severity + * reopen bugnumber [ originator-address | = | ! ] + * found bugnumber [ version ] + * notfound bugnumber version + * submitter bugnumber originator-address | ! + * forwarded bugnumber address + * notforwarded bugnumber + * owner bugnumber address | ! + * noowner bugnumber + * retitle bugnumber new-title + * clone bugnumber NewID [ new IDs ... ] + * merge bugnumber bugnumber ... + * unmerge bugnumber + * forcemerge bugnumber bugnumber ... + * tag bugnumber [ + | - | = ] tag [ tag ... ] + * block bugnumber by bug ... + * unblock bugnumber by bug ... + * close bugnumber [ fixed-version ] (deprecated -- you must + separately tell originator why, see "Closing bug reports" instead) + + reopen with = or no originator address leaves the originator as the + original submitter; ! sets it to you, the person doing the reopen. + + Severities are critical, grave, serious, important, normal, minor, and + wishlist. + + Tags currently include patch, wontfix, moreinfo, unreproducible, help, + pending, fixed, security, upstream, confirmed, fixed-upstream, + fixed-in-experimental, d-i, ipv6, lfs, l10n, potato, woody, sarge, + sarge-ignore, etch, etch-ignore, sid, and experimental. + +Synopsis of bug submission and followup addresses + + * nnn[ -submit | ] + * nnn-maintonly + * nnn-quiet + * nnn-forwarded + * nnn-request + * nnn-submitter + * nnn-done + * nnn-close + * nnn-subscribe + _________________________________________________________________ + + Debian BTS administrators + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/lenny/common/doc/bug-maint-info.txt b/includes/lenny/common/doc/bug-maint-info.txt new file mode 100644 index 000000000..e8b0206a2 --- /dev/null +++ b/includes/lenny/common/doc/bug-maint-info.txt @@ -0,0 +1,409 @@ +Developers' information regarding the bug processing system + + Initially, a bug report is submitted by a user as an ordinary mail + message to submit@bugs.debian.org. This will then be given a number, + acknowledged to the user, and forwarded to debian-bugs-dist. If the + submitter included a Package line listing a package with a known + maintainer the maintainer will get a copy too. + + The Subject line will have Bug#nnn: added, and the Reply-To will be + set to include both the submitter of the report and + nnn@bugs.debian.org. + _________________________________________________________________ + + * Closing bug reports + * Followup messages + * Severity levels + * Tags for bug reports + * Recording that you have passed on a bug report + * Changing bug ownership + * Incorrectly listed package maintainers + * Reopening, reassigning and manipulating bugs + * Subscribing to bugs + * More-or-less obsolete subject-scanning feature + * Obsolete X-Debian-PR: quiet feature + _________________________________________________________________ + +Closing bug reports + + Debian bug reports should be closed when the problem is fixed. + Problems in packages can only be considered fixed once a package that + includes the bug fix enters the Debian archive. + + Normally, the only people that should close a bug report are the + submitter of the bug and the maintainer(s) of the package against + which the bug is filed. There are exceptions to this rule, for + example, the bugs filed against unknown packages or certain generic + pseudo-packages. When in doubt, don't close bugs, first ask for advice + on the debian-devel mailing list. + + Bug reports should be closed by sending email to + nnn-done@bugs.debian.org. The message body needs to contain an + explanation of how the bug was fixed. + + With the emails received from the bug tracking system, all you need to + do to close the bug is to make a Reply in your mail reader program and + edit the To field to say nnn-done@bugs.debian.org instead of + nnn@bugs.debian.org (nnn-close is provided as an alias for nnn-done). + + Where applicable, please supply a Version line in the pseudo-header of + your message when closing a bug, so that the bug tracking system knows + which releases of the package contain the fix. + + The person closing the bug, the person who submitted it and the + debian-bugs-closed mailing list will each get a notification about the + change in status of the report. The submitter and the mailing list + will also receive the contents of the message sent to nnn-done. + +Followup messages + + The bug tracking system will include the submitter's address and the + bug address (nnn@bugs.debian.org) in the Reply-To header after + forwarding the bug report. Please note that these are two distinct + addresses. + + If a developer wishes to reply to a bug report they should simply + reply to the message, respecting the Reply-To header. This will not + close the bug. + + The bug tracking system will receive the message at + nnn@bugs.debian.org, pass it on to the package maintainer, file the + reply with the rest of the logs for that bug report and forward it to + debian-bugs-dist. + + Sending a message to nnn-submitter@bugs.debian.org will explicitly + email the submitter of the bug and place a copy in the Bug tracking + system. The message will not be sent to package maintainer. + + If you wish to send a followup message which is not appropriate for + debian-bugs-dist you can do so by sending it to + nnn-quiet@bugs.debian.org or nnn-maintonly@bugs.debian.org. Mail to + nnn-quiet@bugs.debian.org is filed in the Bug Tracking System but is + not delivered to any individuals or mailing lists. Mail to + nnn-maintonly@bugs.debian.org is filed in the Bug Tracking System and + is delivered only to the maintainer of the package in question. + + Do not use the "reply to all recipients" or "followup" feature of your + mailer unless you intend to edit down the recipients substantially. In + particular, see that you don't send followup messages to + submit@bugs.debian.org. + + For more information about headers to suppress ACK messages and how to + send carbon copies using the Bug Tracking System, see the instructions + for reporting bugs. + +Severity levels + + The bug system records a severity level with each bug report. This is + set to normal by default, but can be overridden either by supplying a + Severity line in the pseudo-header when the bug is submitted (see the + instructions for reporting bugs), or by using the severity command + with the control request server. + + The severity levels are: + + critical + makes unrelated software on the system (or the whole system) + break, or causes serious data loss, or introduces a security + hole on systems where you install the package. + + grave + makes the package in question unusable or mostly so, or causes + data loss, or introduces a security hole allowing access to the + accounts of users who use the package. + + serious + is a severe violation of Debian policy (roughly, it violates a + "must" or "required" directive), or, in the package + maintainer's or release manager's opinion, makes the package + unsuitable for release. + + important + a bug which has a major effect on the usability of a package, + without rendering it completely unusable to everyone. + + normal + the default value, applicable to most bugs. + + minor + a problem which doesn't affect the package's usefulness, and is + presumably trivial to fix. + + wishlist + for any feature request, and also for any bugs that are very + difficult to fix due to major design considerations. + + Certain severities are considered release-critical, meaning the bug + will have an impact on releasing the package with the stable release + of Debian. Currently, these are critical, grave and serious. For + complete and canonical rules on what issues merit these severities, + see the list of Release-Critical Issues for Lenny. + +Tags for bug reports + + Each bug can have zero or more of a set of given tags. These tags are + displayed in the list of bugs when you look at a package's page, and + when you look at the full bug log. + + Tags can be set by supplying a Tags line in the pseudo-header when the + bug is submitted (see the instructions for reporting bugs), or by + using the tags command with the control request server. Separate + multiple tags with commas, spaces, or both. + + The current bug tags are: + + patch + A patch or some other easy procedure for fixing the bug is + included in the bug logs. If there's a patch, but it doesn't + resolve the bug adequately or causes some other problems, this + tag should not be used. + + wontfix + This bug won't be fixed. Possibly because this is a choice + between two arbitrary ways of doing things and the maintainer + and submitter prefer different ways of doing things, possibly + because changing the behaviour will cause other, worse, + problems for others, or possibly for other reasons. + + moreinfo + This bug can't be addressed until more information is provided + by the submitter. The bug will be closed if the submitter + doesn't provide more information in a reasonable (few months) + timeframe. This is for bugs like "It doesn't work". What + doesn't work? + + unreproducible + This bug can't be reproduced on the maintainer's system. + Assistance from third parties is needed in diagnosing the cause + of the problem. + + help + The maintainer is requesting help with dealing with this bug. + + pending + A solution to this bug has been found and an upload will be + made soon. + + fixed + This bug is fixed or worked around (by a non-maintainer upload, + for example), but there's still an issue that needs to be + resolved. This tag replaces the old "fixed" severity. + + security + This bug describes a security problem in a package (e.g., bad + permissions allowing access to data that shouldn't be + accessible; buffer overruns allowing people to control a system + in ways they shouldn't be able to; denial of service attacks + that should be fixed, etc). Most security bugs should also be + set at critical or grave severity. + + upstream + This bug applies to the upstream part of the package. + + confirmed + The maintainer has looked at, understands, and basically agrees + with the bug, but has yet to fix it. (Use of this tag is + optional; it is intended mostly for maintainers who need to + manage large numbers of open bugs.) + + fixed-upstream + The bug has been fixed by the upstream maintainer, but not yet + in the package (for whatever reason: perhaps it is too + complicated to backport the change or too minor to be worth + bothering). + + fixed-in-experimental + The bug has been fixed in the package of the experimental + distribution, but not yet in the unstable distribution. + + d-i + This bug is relevant to the development of debian-installer. It + is expected that this will be used when the bug affects + installer development but is not filed against a package that + forms a direct part of the installer itself. + + ipv6 + This bug affects support for Internet Protocol version 6. + + lfs + This bug affects support for large files (over 2 gigabytes). + + l10n + This bug is relevant to the localisation of the package. + + potato + This bug particularly applies to the potato release of Debian. + + woody + This bug particularly applies to the woody distribution. + + sarge + This bug should not be archived until it is fixed in sarge. + + sarge-ignore + This release-critical bug is to be ignored for the purposes of + releasing sarge. This tag should only be used by the release + manager; do not set it yourself without explicit authorization + from them. + + etch + This bug should not be archived until it is fixed in etch. + + etch-ignore + This release-critical bug is to be ignored for the purposes of + releasing etch. This tag should only be used by the release + manager; do not set it yourself without explicit authorization + from them. + + lenny + This bug should not be archived until it is fixed in lenny. + + lenny-ignore + This release-critical bug is to be ignored for the purposes of + releasing lenny. This tag should only be used by the release + manager(s); do not set it yourself without explicit + authorization from them. + + sid + This bug should not be archived until it is fixed in sid. + + experimental + This bug should not be archived until it is fixed in + experimental. + + The meanings of the latter 8 tags have changed recently; the ignore + tags ignore the bug for the purpose of a testing propagation. The + release tags, which used to only indicate which bugs affected a + specific release, now indicate when a bug can be archived, and are + otherwise ignored by the BTS. However, they may be utilized by other + tools like the testing propagation scripts. + +Recording that you have passed on a bug report + + When a developer forwards a bug report to the developer of the + upstream source package from which the Debian package is derived, they + should note this in the bug tracking system as follows: + + Make sure that the To field of your message to the author has only the + author(s) address(es) in it; put the person who reported the bug, + nnn-forwarded@bugs.debian.org and nnn@bugs.debian.org in the CC field. + + Ask the author to preserve the CC to nnn-forwarded@bugs.debian.org + when they reply, so that the bug tracking system will file their reply + with the original report. These messages are only filed and are not + sent on; to send a message as normal, send them to nnn@bugs.debian.org + as well. + + When the bug tracking system gets a message at nnn-forwarded it will + mark the relevant bug as having been forwarded to the address(es) in + the To field of the message it gets, if the bug is not already marked + as forwarded. + + You can also manipulate the "forwarded to" information by sending + messages to control@bugs.debian.org. + +Changing bug ownership + + In cases where the person responsible for fixing a bug is not the + assigned maintainer for the associated package (for example, when the + package is maintained by a team), it may be useful to record this fact + in the bug tracking system. To help with this, each bug may optionally + have an owner. + + The owner can be set by supplying an Owner line in the pseudo-header + when the bug is submitted (see the instructions for reporting bugs), + or by using the owner and noowner commands with the control request + server. + +Incorrectly listed package maintainers + + If the maintainer of a package is listed incorrectly, this is usually + because the maintainer has changed recently, and the new maintainer + hasn't yet uploaded a new version of the package with a changed + Maintainer control file field. This will be fixed when the package is + uploaded; alternatively, the archive maintainers can override the + maintainer record of a package manually, for example if a rebuild and + reupload of the package is not expected to be needed soon. Contact + override-change@debian.org for changes to the override file. + +Reopening, reassigning and manipulating bugs + + It is possible to reassign bug reports to other packages, to reopen + erroneously-closed ones, to modify the information saying to where, if + anywhere, a bug report has been forwarded, to change the severities + and titles of reports, to set the ownership of bugs, to merge and + unmerge bug reports, and to record the versions of packages in which + bugs were found and in which they were fixed. This is done by sending + mail to control@bugs.debian.org. + + The format of these messages is described in another document + available on the World Wide Web or in the file + bug-maint-mailcontrol.txt. A plain text version can also be obtained + by mailing the word help to the server at the address above. + +Subscribing to bugs + + The bug tracking system also allows bug submitters, developers and + other interested third parties to subscribe to individual bugs. This + feature can be used by those wishing to keep an eye on a bug, without + having to subscribe to a package through the PTS. All messages that + are received at nnn@bugs.debian.org, are sent to subscribers. + + Subscribing to a bug can be done by sending an email to + nnn-subscribe@bugs.debian.org. The subject and body of the email are + ignored by the BTS. Once this message is processed, users are sent a + confirmation message that they will need to reply to before they are + sent the messages relating to that bug. + + It is also possible to unsubscribe from a bug. Unsubscribing can be + done by sending an email to nnn-unsubscribe@bugs.debian.org. The + subject and body of the email are again ignored by the BTS. Users will + be sent a confirmation message which they must reply to if they wish + to be unsubscribed from the bug. + + By default, the address subscribed is the one found in the From + header. If you wish to subscribe another address to a bug, you will + need to encode the address to be subscribed into the subscription + message. This takes the form of: + nnn-subscribe-localpart=example.com@bugs.debian.org. That example + would send localpart@example.com a subscription message for bug nnn. + The @ sign must be encoded by changing it to an = sign. Similarly, an + unsubscription takes the form + nnn-unsubscribe-localpart=example.com@bugs.debian.org. In both cases, + the subject and body of the email will be forwarded to the email + address within the request for confirmation. + +More-or-less obsolete subject-scanning feature + + Messages that arrive at submit or bugs whose Subject starts Bug#nnn + will be treated as having been sent to nnn@bugs.debian.org. This is + both for backwards compatibility with mail forwarded from the old + addresses, and to catch followup mail sent to submit by mistake (for + example, by using reply to all recipients). + + A similar scheme operates for maintonly, done, quiet and forwarded, + which treat mail arriving with a Subject tag as having been sent to + the corresponding nnn-whatever@bugs.debian.org address. + + Messages arriving at plain forwarded and done -- ie, with no bug + report number in the address -- and without a bug number in the + Subject will be filed under "junk" and kept for a few weeks, but + otherwise ignored. + +Obsolete X-Debian-PR: quiet feature + + It used to be possible to prevent the bug tracking system from + forwarding anywhere messages it received at debian-bugs, by putting an + X-Debian-PR: quiet line in the actual mail header. + + This header line is now ignored. Instead, send your message to quiet + or nnn-quiet (or maintonly or nnn-maintonly). + _________________________________________________________________ + + Debian BTS administrators + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/lenny/common/doc/bug-maint-mailcontrol.txt b/includes/lenny/common/doc/bug-maint-mailcontrol.txt new file mode 100644 index 000000000..a0b7c9ec1 --- /dev/null +++ b/includes/lenny/common/doc/bug-maint-mailcontrol.txt @@ -0,0 +1,390 @@ +Introduction to the bug control and manipulation mailserver + + Just as request@bugs.debian.org allows the retrieval of bug data and + documentation by email, control@bugs.debian.org allows bug reports to + be manipulated in various ways. + + The control server works just like the request server, except that it + has some additional commands; in fact, it's the same program. The two + addresses are only separated to avoid users making mistakes and + causing problems while merely trying to request information. + + Since the commands specific to the control server actually change the + status of a bug, a notification about processing the commands is sent + to the maintainer of the package(s) the changed bugs are assigned to. + Additionally the mail to the server and the resulting changes are + logged in the bug report and thereby available in the WWW pages. + + Please see the introduction to the request server available on the + World Wide Web, in the file bug-log-mailserver.txt, or by sending help + to either mailserver, for details of the basics of operating the + mailservers and the common commands available when mailing either + address. + + The reference card for the mailservers is available via the WWW, in + bug-mailserver-refcard.txt or by email using the refcard command. + +Commands available at the control mailserver + + General Versioning Duplicates Misc. + + reassign + severity + tag + retitle + submitter + + found | notfound + fixed | notfixed + reopen + + merge | unmerge + forcemerge + clone + + thanks + # + forwarded | notforwarded + owner | noowner + block | unblock + archive | unarchive + + reassign bugnumber package [ version ] + Records that bug #bugnumber is a bug in package. This can be + used to set the package if the user forgot the pseudo-header, + or to change an earlier assignment. No notifications are sent + to anyone (other than the usual information in the processing + transcript). + + If you supply a version, the bug tracking system will note that + the bug affects that version of the newly-assigned package. + + You can assign a bug to two packages at once by separating the + package names with a comma. However, you should only do this if + the bug can be fixed by a change to either package. If this is + not the case, you should clone the bug and reassign the clone + to the other package. + + reopen bugnumber [ originator-address | = | ! ] + Reopens #bugnumber if it is closed. + + By default, or if you specify =, the original submitter is + still as the originator of the report, so that they will get + the ack when it is closed again. + + If you supply an originator-address the originator will be set + to the address you supply. If you wish to become the new + originator of the reopened report you can use the ! shorthand + or specify your own email address. + + It is usually a good idea to tell the person who is about to be + recorded as the originator that you're reopening the report, so + that they will know to expect the ack which they'll get when it + is closed again. + + If the bug is not closed then reopen won't do anything, not + even change the originator. To change the originator of an open + bug report, use the submitter command; note that this will + inform the original submitter of the change. + + If the bug was recorded as being closed in a particular version + of a package but recurred in a later version, it is better to + use the found command instead. + + found bugnumber [ version ] + Record that #bugnumber has been encountered in the given + version of the package to which it is assigned. + + The bug tracking system uses this information, in conjunction + with fixed versions recorded when closing bugs, to display + lists of bugs open in various versions of each package. It + considers a bug to be open when it has no fixed version, or + when it has been found more recently than it has been fixed. + + If no version is given, then the list of fixed versions for the + bug is cleared. This is identical to the behaviour of reopen. + + This command will only cause a bug to be marked as not done if + no version is specified, or if the version being marked found + is equal to the version which was last marked fixed. (If you + are certain that you want the bug marked as not done, use + reopen in conjunction with found.) + + This command was introduced in preference to reopen because it + was difficult to add a version to that command's syntax without + suffering ambiguity. + + notfound bugnumber version + Remove the record that #bugnumber was encountered in the given + version of the package to which it is assigned. + + This differs from closing the bug at that version in that the + bug is not listed as fixed in that version either; no + information about that version will be known. It is intended + for fixing mistakes in the record of when a bug was found. + + fixed bugnumber version + Indicate that bug #bugnumber was fixed in the given version of + the package to which it is assigned. + + This does not cause the bug to be marked as closed, it merely + adds another version in which the bug was fixed. Use the + bugnumber-done address to close a bug and mark it fixed in a + particular version. + + notfixed bugnumber version + Remove the record that bug #bugnumber has been fixed in the + given version. + + This command is equivalent to found followed by notfound (the + found removes the fixed at a particular version, and notfound + removes the found.) + + submitter bugnumber originator-address | ! + Changes the originator of #bugnumber to originator-address. + + If you wish to become the new originator of the report you can + use the ! shorthand or specify your own email address. + + While the reopen command changes the originator of other bugs + merged with the one being reopened, submitter does not affect + merged bugs. + + forwarded bugnumber address + Notes that bugnumber has been forwarded to the upstream + maintainer at address. This does not actually forward the + report. This can be used to change an existing incorrect + forwarded-to address, or to record a new one for a bug that + wasn't previously noted as having been forwarded. + + notforwarded bugnumber + Forgets any idea that bugnumber has been forwarded to any + upstream maintainer. If the bug was not recorded as having been + forwarded then this will do nothing. + + retitle bugnumber new-title + Changes the title of a bug report to that specified (the + default is the Subject mail header from the original report). + + Unlike most of the other bug-manipulation commands when used on + one of a set of merged reports this will change the title of + only the individual bug requested, and not all those with which + it is merged. + + severity bugnumber severity + Set the severity level for bug report #bugnumber to severity. + No notification is sent to the user who reported the bug. + + Severities are critical, grave, serious, important, normal, + minor, and wishlist. + + For their meanings please consult the general developers' + documentation for the bug system. + + clone bugnumber NewID [ new IDs ... ] + The clone control command allows you to duplicate a bug report. + It is useful in the case where a single report actually + indicates that multiple distinct bugs have occurred. "New IDs" + are negative numbers, separated by spaces, which may be used in + subsequent control commands to refer to the newly duplicated + bugs. A new report is generated for each new ID. + + Example usage: + + clone 12345 -1 -2 + reassign -1 foo + retitle -1 foo: foo sucks + reassign -2 bar + retitle -2 bar: bar sucks when used with foo + severity -2 wishlist + clone 123456 -3 + reassign -3 foo + retitle -3 foo: foo sucks + merge -1 -3 + + merge bugnumber bugnumber ... + Merges two or more bug reports. When reports are merged + opening, closing, marking or unmarking as forwarded and + reassigning any of the bugs to a new package will have an + identical effect on all of the merged reports. + + Before bugs can be merged they must be in exactly the same + state: either all open or all closed, with the same + forwarded-to upstream author address or all not marked as + forwarded, all assigned to the same package or package(s) (an + exact string comparison is done on the package to which the bug + is assigned), and all of the same severity. If they don't start + out in the same state you should use reassign, reopen and so + forth to make sure that they are before using merge. Titles are + not required to match, and will not be affected by the merge. + Tags are not required to match, either, they will be joined. + + If any of the bugs listed in a merge command is already merged + with another bug then all the reports merged with any of the + ones listed will all be merged together. Merger is like + equality: it is reflexive, transitive and symmetric. + + Merging reports causes a note to appear on each report's logs; + on the WWW pages this is includes links to the other bugs. + + Merged reports are all expired simultaneously, and only when + all of the reports each separately meet the criteria for + expiry. + + forcemerge bugnumber bugnumber ... + Forcibly merges two or more bug reports. The first bug listed + is the master bug, and its settings (the settings which must be + equal in a normal merge) are assigned to the bugs listed next. + To avoid typos erroneously merging bugs, bugs must be in the + same package. See the text above for a description of what + merging means. + + Note that this makes it possible to close bugs by merging; you + are responsible for notifying submitters with an appropriate + close message if you do this. + + unmerge bugnumber + Disconnects a bug report from any other reports with which it + may have been merged. If the report listed is merged with + several others then they are all left merged with each other; + only their associations with the bug explicitly named are + removed. + + If many bug reports are merged and you wish to split them into + two separate groups of merged reports you must unmerge each + report in one of the new groups separately and then merge them + into the required new group. + + You can only unmerge one report with each unmerge command; if + you want to disconnect more than one bug simply include several + unmerge commands in your message. + + tags bugnumber [ + | - | = ] tag [ tag ... ] + Sets tags for the bug report #bugnumber. No notification is + sent to the user who reported the bug. Setting the action to + + means to add each given tag, - means to remove each given tag, + and = means to ignore the current tags and set them afresh to + the list provided. The default action is adding. + + Example usage: + + # same as 'tags 123456 + patch' + tags 123456 patch + + # same as 'tags 123456 + help security' + tags 123456 help security + + # add 'fixed' and 'pending' tags + tags 123456 + fixed pending + + # remove 'unreproducible' tag + tags 123456 - unreproducible + + # set tags to exactly 'moreinfo' and 'unreproducible' + tags 123456 = moreinfo unreproducible + + Available tags currently include patch, wontfix, moreinfo, + unreproducible, help, pending, fixed, fixed-in-experimental, + fixed-upstream, security, upstream, confirmed, d-i, ipv6, lfs, + l10n, potato, woody, sarge, sarge-ignore, etch, etch-ignore, + sid, and experimental. + + For their meanings please consult the general developers' + documentation for the bug system. + + block bugnumber by bug ... + Note that the fix for the first bug is blocked by the other + listed bugs. + + unblock bugnumber by bug ... + Note that the fix for the first bug is no longer blocked by the + other listed bugs. + + close bugnumber [ fixed-version ] (deprecated) + Close bug report #bugnumber. + + A notification is sent to the user who reported the bug, but + (in contrast to mailing bugnumber-done@bugs.debian.org) the + text of the mail which caused the bug to be closed is not + included in that notification. The maintainer who closes a + report needs to ensure, probably by sending a separate message, + that the user who reported the bug knows why it is being + closed. The use of this command is therefore deprecated. See + the developer's information about how to close a bug properly. + + If you supply a fixed-version, the bug tracking system will + note that the bug was fixed in that version of the package. + + package [ packagename ... ] + Limits the following commands so that they will only apply to + bugs filed against the listed packages. You can list one or + more packages. If you don't list any packages, the following + commands will apply to all bugs. You're encouraged to use this + as a safety feature in case you accidentally use the wrong bug + numbers. + + Example usage: + + package foo + reassign 123456 bar 1.0-1 + + package bar + retitle 123456 bar: bar sucks + severity 123456 normal + + package + severity 234567 wishlist + + owner bugnumber address | ! + Sets address to be the "owner" of #bugnumber. The owner of a + bug claims responsibility for fixing it. This is useful to + share out work in cases where a package has a team of + maintainers. + + If you wish to become the owner of the bug yourself, you can + use the ! shorthand or specify your own email address. + + noowner bugnumber + Forgets any idea that the bug has an owner other than the usual + maintainer. If the bug had no owner recorded then this will do + nothing. + + archive bugnumber + Archives a bug that had been archived at some point in the past + but is currently not archived if the bug fulfills the + requirements for archival, ignoring time. + + unarchive bugnumber + Unarchives a bug that was previously archived. Unarchival + should generally be coupled with reopen and found/fixed as + appropriate. Bugs that have been unarchived can be archived + using archive assuming the non-time based archival requirements + are met. + + #... + One-line comment. The # must be at the start of the line. The + text of comments will be included in the acknowledgement sent + to the sender and to affected maintainers, so you can use this + to document the reasons for your commands. + + quit + stop + thank + thanks + thankyou + thank you + -- + On a line by itself, in any case, possibly followed by + whitespace, tells the control server to stop processing the + message; the remainder of the message can include explanations, + signatures or anything else, none of it will be detected by the + control server. + _________________________________________________________________ + + Debian BTS administrators + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/lenny/common/doc/bug-reporting.txt b/includes/lenny/common/doc/bug-reporting.txt new file mode 100644 index 000000000..974eb2085 --- /dev/null +++ b/includes/lenny/common/doc/bug-reporting.txt @@ -0,0 +1,362 @@ +How to report a bug in Debian using reportbug + + We strongly recommend that you report bugs in Debian using the + reportbug program. To install and start it, simply run: + + aptitude install reportbug; reportbug + + It will guide you through the bug reporting process step by step. + + If you have questions that the interactive prompts of reportbug do not + resolve, you can refer to the rest of the documentation below or ask + the Debian user mailing list. + +How to report a bug in Debian using email (and advanced usage of reportbug) + +Important things to note before sending your bug report + +What package does your bug report belong to? + + You need to know what package your bug report should be filed against. + See this example for information on how to find this information. (You + will use this information to see if your bug report has been filed + already.) + + If you are unable to determine which package your bug report should be + filed against, please send e-mail to the Debian user mailing list + asking for advice. + + If your problem doesn't relate just to one package but some general + Debian service, there are several pseudo-packages or even mailing + lists that you can use to relay your message to us instead. + +Has your bug report been filed already? + + You should check to see if your bug report has already been filed + before submitting it. You can see which bugs have been filed in a + specific package using the package option of the bug search form. If + there is an existing bug report #, you should submit your + comments by sending e-mail to @bugs.debian.org instead of + reporting a new bug. + +Send multiple reports for multiple bugs + + Please don't report multiple unrelated bugs -- especially ones in + different packages -- in a single bug report. + +Don't file bugs upstream + + If you file a bug in Debian, don't send a copy to the upstream + software maintainers yourself, as it is possible that the bug exists + only in Debian. If necessary, the maintainer of the package will + forward the bug upstream. + +Sending the bug report via e-mail + + You can report bugs in Debian by sending an e-mail to + submit@bugs.debian.org with a special format described below. + reportbug (see above) will properly format the e-mails for you; please + use it! + +Headers + + Like any e-mail you should include a clear, descriptive Subject line + in your main mail header. The subject you give will be used as the + initial bug title in the tracking system, so please try to make it + informative! + + If you'd like to send a copy of your bug report to additional + recipients (such as mailing lists), you shouldn't use the usual e-mail + headers, but a different method, described below. + +Pseudo-headers + + The first part of the bug report are the pseudo-headers which contain + information about what package and version your bug report applies to. + The first line of the message body has to include a pseudo-header. It + should say: +Package: + + Replace with the name of the package which has the bug. + + The second line of the message should say: +Version: + + Replace with the version of the package. Please don't + include any text here other than the version itself, as the bug + tracking system relies on this field to work out which releases are + affected by the bug. + + You need to supply a correct Package line in the pseudo-header in + order for the bug tracking system to deliver the message to the + package's maintainer. See this example for information on how to find + this information. + + For other valid pseudo-headers, see Additional pseudo-headers + +The body of the report + + Please include in your report: + * The exact and complete text of any error messages printed or + logged. This is very important! + * Exactly what you typed or did to demonstrate the problem. + * A description of the incorrect behavior: exactly what behavior you + were expecting, and what you observed. A transcript of an example + session is a good way of showing this. + * A suggested fix, or even a patch, if you have one. + * Details of the configuration of the program with the problem. + Include the complete text of its configuration files. + * The versions of any packages on which the buggy package depends. + * What kernel version you're using (type uname -a), your shared C + library (type ls -l /lib/libc.so.6 or dpkg -s libc6 | grep + ^Version), and any other details about your Debian system, if it + seems appropriate. For example, if you had a problem with a Perl + script, you would want to provide the version of the `perl' binary + (type perl -v or dpkg -s perl | grep ^Version:). + * Appropriate details of the hardware in your system. If you're + reporting a problem with a device driver please list all the + hardware in your system, as problems are often caused by IRQ and + I/O address conflicts. + * If you have reportbug installed the output of reportbug -q + --template -T none -s none -S normal -b --list-cc none -q + will also be useful, as it contains the output of + maintainer specific scripts and version information. + + Include any detail that seems relevant -- you are in very little + danger of making your report too long by including too much + information. If they are small, please include in your report any + files you were using to reproduce the problem. (If they are large, + consider making them available on a publicly available website if + possible.) + + For more advice on how to help the developers solve your problem, + please read How to Report Bugs Effectively. + +An Example Bug Report + + A bug report with header and pseudo-header looks something like this: + To: submit@bugs.debian.org + From: diligent@testing.linux.org + Subject: Hello says `goodbye' + + Package: hello + Version: 1.3-16 + + When I invoke `hello' without arguments from an ordinary shell + prompt it prints `goodbye', rather than the expected `hello, world'. + Here is a transcript: + + $ hello + goodbye + $ /usr/bin/hello + goodbye + $ + + I suggest that the output string, in hello.c, be corrected. + + I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13 + and libc6 2.1.3-10. + +Sending copies of bug reports to other addresses + + Sometimes it is necessary to send a copy of a bug report to somewhere + else besides debian-bugs-dist and the package maintainer, which is + where they are normally sent. + + You could do this by CC'ing your bug report to the other address(es), + but then the other copies would not have the bug report number put in + the Reply-To field and the Subject line. When the recipients reply + they will probably preserve the submit@bugs.debian.org entry in the + header and have their message filed as a new bug report. This leads to + many duplicated reports. + + The right way to do this is to use the X-Debbugs-CC header. Add a line + like this to your message's mail header: + X-Debbugs-CC: other-list@cosmic.edu + + This will cause the bug tracking system to send a copy of your report + to the address(es) in the X-Debbugs-CC line as well as to + debian-bugs-dist. + + Avoid sending such copies to the addresses of other bug reports, as + they will be caught by the checks that prevent mail loops. There is + relatively little point in using X-Debbugs-CC for this anyway, as the + bug number added by that mechanism will just be replaced by a new one; + use an ordinary CC header instead. + + This feature can often be combined usefully with mailing quiet -- see + below. + +Additional Pseudoheaders + +Severity levels + + If a report is of a particularly serious bug, or is merely a feature + request, you can set the severity level of the bug as you report it. + This is not required however, and the package maintainer will assign + an appropriate severity level to your report even if you do not (or + pick the wrong severity). + + To assign a severity level, put a line like this one in the + pseudo-header: +Severity: + + Replace with one of the available severity levels, as + described in the advanced documentation. + +Assigning tags + + You can set tags on a bug as you are reporting it. For example, if you + are including a patch with your bug report, you may wish to set the + patch tag. This is not required, however, and the developers will set + tags on your report as and when it is appropriate. + + To set tags, put a line like this one in the pseudo-header: +Tags: + + Replace with one or more of the available tags, as described in + the advanced documentation. Separate multiple tags with commas, + spaces, or both. +User: +Usertags: + + Replace with one or more usertags. Separate multiple tags + with commas, spaces, or both. If you specify a , that user's + tags will be set. Otherwise, the e-mail address of the sender will be + used as the username. +Forwarded: foo@example.com + + will mark the newly submitted bug as forwarded to foo@example.com. See + Recording that you have passed on a bug report in the developers' + documentation for details. +Owner: foo@example.com + + will indicate that foo@example.com is now responsible for fixing this + bug. See Changing bug ownership in the developers' documentation for + details. +Source: foopackage + + the equivalent of Package: for bugs present in the source package of + foopackage; for most bugs in most packages you don't want to use this + option. + + Finally, if your MUA doesn't allow you to edit the headers, you can + set the various X-Debbugs- headers in the pseudo-headers. + +Additional information + +Different submission addresses (minor or mass bug reports) + + If a bug report is minor, for example, a documentation typo or a + trivial build problem, please adjust the severity appropriately and + send it to maintonly@bugs.debian.org instead of + submit@bugs.debian.org. maintonly will forward the report to the + package maintainer only, it won't forward it to the BTS mailing lists. + + If you're submitting many reports at once, you should definitely use + maintonly@bugs.debian.org so that you don't cause too much redundant + traffic on the BTS mailing lists. Before submitting many similar bugs + you may also want to post a summary on debian-bugs-dist. + + If wish to report a bug to the bug tracking system that's already been + sent to the maintainer, you can use quiet@bugs.debian.org. Bugs sent + to quiet@bugs.debian.org will not be forwarded anywhere, only filed. + + When you use different submission addresses, the bug tracking system + will set the Reply-To of any forwarded message so that the replies + will by default be processed in the same way as the original report. + That means that, for example, replies to maintonly will go to + nnn-maintonly@bugs.debian.org instead of nnn@bugs.debian.org, unless + of course one overrides this manually. + +Acknowledgements + + Normally, the bug tracking system will return an acknowledgement to + you by e-mail when you report a new bug or submit additional + information to an existing bug. If you want to suppress this + acknowledgement, include an X-Debbugs-No-Ack header in your e-mail + (the contents of this header do not matter; however, it must be in the + mail header and not in the pseudo-header with the Package field). If + you report a new bug with this header, you will need to check the web + interface yourself to find the bug number. + + Note that this header will not suppress acknowledgements from the + control@bugs.debian.org mailserver, since those acknowledgements may + contain error messages which should be read and acted upon. + +Bug reports against unknown packages + + If the bug tracking system doesn't know who the maintainer of the + relevant package is it will forward the report to debian-bugs-dist + even if maintonly was used. + + When sending to maintonly@bugs.debian.org or + nnn-maintonly@bugs.debian.org you should make sure that the bug report + is assigned to the right package, by putting a correct Package at the + top of an original submission of a report, or by using the + control@bugs.debian.org service to (re)assign the report + appropriately. + +Using dpkg to find the package and version for the report + + When using reportbug to report a bug in a command, say grep, the + following will automatically select the right package and let you + write the report right away: reportbug --file $(which grep) + + You can also find out which package installed it by using dpkg + --search. You can find out which version of a package you have + installed by using dpkg --list or dpkg --status. + + For example: +$ which apt-get +/usr/bin/apt-get +$ type apt-get +apt-get is /usr/bin/apt-get +$ dpkg --search /usr/bin/apt-get +apt: /usr/bin/apt-get +$ dpkg --list apt +Desired=Unknown/Install/Remove/Purge/Hold +| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed +|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) +||/ Name Version Description ++++-==============-==============-============================================ +ii apt 0.3.19 Advanced front-end for dpkg +$ dpkg --status apt +Package: apt +Status: install ok installed +Priority: standard +Section: base +Installed-Size: 1391 +Maintainer: APT Development Team +Version: 0.3.19 +Replaces: deity, libapt-pkg-doc (<< 0.3.7), libapt-pkg-dev (<< 0.3.7) +Provides: libapt-pkg2.7 +Depends: libapt-pkg2.7, libc6 (>= 2.1.2), libstdc++2.10 +Suggests: dpkg-dev +Conflicts: deity +Description: Advanced front-end for dpkg + This is Debian's next generation front-end for the dpkg package manager. + It provides the apt-get utility and APT dselect method that provides a + simpler, safer way to install and upgrade packages. + . + APT features complete installation ordering, multiple source capability + and several other unique features, see the Users Guide in + /usr/doc/apt/guide.text.gz + +Other useful commands and packages + + The querybts tool, available from the same package as reportbug, + provides a convenient text-based interface to the bug tracking system. + + Emacs users can also use the debian-bug command provided by the + debian-el package. When called with M-x debian-bug, it will ask for + all necessary information in a similar way to reportbug. + _________________________________________________________________ + + Debian BTS administrators + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/lenny/common/doc/constitution.txt b/includes/lenny/common/doc/constitution.txt new file mode 100644 index 000000000..96ed0c700 --- /dev/null +++ b/includes/lenny/common/doc/constitution.txt @@ -0,0 +1,600 @@ + Historical version of the Constitution for the Debian Project (v1.2) + + Version 1.2 ratified on October 29th, 2003. Supersedes Version 1.1 + ratified on June 21st, 2003, which itself supersedes Version 1.0 + ratified on December 2nd, 1998. Superseded by version 1.3, ratified on + September 24th, 2006. That was superceded by the current version, 1.4 + ratified on October 7th, 2007. + +1. Introduction + + The Debian Project is an association of individuals who have made + common cause to create a free operating system. + + This document describes the organisational structure for formal + decision-making in the Project. It does not describe the goals of the + Project or how it achieves them, or contain any policies except those + directly related to the decision-making process. + +2. Decision-making bodies and individuals + + Each decision in the Project is made by one or more of the following: + 1. The Developers, by way of General Resolution or an election; + 2. The Project Leader; + 3. The Technical Committee and/or its Chairman; + 4. The individual Developer working on a particular task; + 5. Delegates appointed by the Project Leader for specific tasks; + 6. The Project Secretary. + + Most of the remainder of this document will outline the powers of these + bodies, their composition and appointment, and the procedure for their + decision-making. The powers of a person or body may be subject to + review and/or limitation by others; in this case the reviewing body or + person's entry will state this. In the list above, a person or body is + usually listed before any people or bodies whose decisions they can + overrule or who they (help) appoint - but not everyone listed earlier + can overrule everyone listed later. + + 2.1. General rules + + 1. Nothing in this constitution imposes an obligation on anyone to do + work for the Project. A person who does not want to do a task which + has been delegated or assigned to them does not need to do it. + However, they must not actively work against these rules and + decisions properly made under them. + 2. A person may hold several posts, except that the Project Leader, + Project Secretary and the Chairman of the Technical Committee must + be distinct, and that the Leader cannot appoint themselves as their + own Delegate. + 3. A person may leave the Project or resign from a particular post + they hold, at any time, by stating so publicly. + +3. Individual Developers + + 3.1. Powers + + An individual Developer may + 1. make any technical or nontechnical decision with regard to their + own work; + 2. propose or sponsor draft General Resolutions; + 3. propose themselves as a Project Leader candidate in elections; + 4. vote on General Resolutions and in Leadership elections. + + 3.2. Composition and appointment + + 1. Developers are volunteers who agree to further the aims of the + Project insofar as they participate in it, and who maintain + package(s) for the Project or do other work which the Project + Leader's Delegate(s) consider worthwhile. + 2. The Project Leader's Delegate(s) may choose not to admit new + Developers, or expel existing Developers. If the Developers feel + that the Delegates are abusing their authority they can of course + override the decision by way of General Resolution - see §4.1(3), + §4.2. + + 3.3. Procedure + + Developers may make these decisions as they see fit. + +4. The Developers by way of General Resolution or election + + 4.1. Powers + + Together, the Developers may: + 1. Appoint or recall the Project Leader. + 2. Amend this constitution, provided they agree with a 3:1 majority. + 3. Override any decision by the Project Leader or a Delegate. + 4. Override any decision by the Technical Committee, provided they + agree with a 2:1 majority. + 5. Issue, supersede and withdraw nontechnical policy documents and + statements. + These include documents describing the goals of the project, its + relationship with other free software entities, and nontechnical + policies such as the free software licence terms that Debian + software must meet. + They may also include position statements about issues of the day. + 1. A Foundation Document is a document or statement regarded as + critical to the Project's mission and purposes. + 2. The Foundation Documents are the works entitled "Debian Social + Contract" and "Debian Free Software Guidelines". + 3. A Foundation Document requires a 3:1 majority for its + supersession. New Foundation Documents are issued and existing + ones withdrawn by amending the list of Foundation Documents in + this constitution. + 6. Together with the Project Leader and SPI, make decisions about + property held in trust for purposes related to Debian. (See §9.1.) + + 4.2. Procedure + + 1. The Developers follow the Standard Resolution Procedure, below. A + resolution or amendment is introduced if proposed by any Developer + and sponsored by at least K other Developers, or if proposed by the + Project Leader or the Technical Committee. + 2. Delaying a decision by the Project Leader or their Delegate: + 1. If the Project Leader or their Delegate, or the Technical + Committee, has made a decision, then Developers can override + them by passing a resolution to do so; see §4.1(3). + 2. If such a resolution is sponsored by at least 2K Developers, + or if it is proposed by the Technical Committee, the + resolution puts the decision immediately on hold (provided + that resolution itself says so). + 3. If the original decision was to change a discussion period or + a voting period, or the resolution is to override the + Technical Committee, then only K Developers need to sponsor + the resolution to be able to put the decision immediately on + hold. + 4. If the decision is put on hold, an immediate vote is held to + determine whether the decision will stand until the full vote + on the decision is made or whether the implementation of the + original decision will be delayed until then. There is no + quorum for this immediate procedural vote. + 5. If the Project Leader (or the Delegate) withdraws the original + decision, the vote becomes moot, and is no longer conducted. + 3. Votes are taken by the Project Secretary. Votes, tallies, and + results are not revealed during the voting period; after the vote + the Project Secretary lists all the votes cast. The voting period + is 2 weeks, but may be varied by up to 1 week by the Project + Leader. + 4. The minimum discussion period is 2 weeks, but may be varied by up + to 1 week by the Project Leader. The Project Leader has a casting + vote. There is a quorum of 3Q. + 5. Proposals, sponsors, amendments, calls for votes and other formal + actions are made by announcement on a publicly-readable electronic + mailing list designated by the Project Leader's Delegate(s); any + Developer may post there. + 6. Votes are cast by email in a manner suitable to the Secretary. The + Secretary determines for each poll whether voters can change their + votes. + 7. Q is half of the square root of the number of current Developers. K + is Q or 5, whichever is the smaller. Q and K need not be integers + and are not rounded. + +5. Project Leader + + 5.1. Powers + + The Project Leader may: + 1. Appoint Delegates or delegate decisions to the Technical Committee. + The Leader may define an area of ongoing responsibility or a + specific decision and hand it over to another Developer or to the + Technical Committee. + Once a particular decision has been delegated and made the Project + Leader may not withdraw that delegation; however, they may withdraw + an ongoing delegation of particular area of responsibility. + 2. Lend authority to other Developers. + The Project Leader may make statements of support for points of + view or for other members of the project, when asked or otherwise; + these statements have force if and only if the Leader would be + empowered to make the decision in question. + 3. Make any decision which requires urgent action. + This does not apply to decisions which have only become gradually + urgent through lack of relevant action, unless there is a fixed + deadline. + 4. Make any decision for whom noone else has responsibility. + 5. Propose draft General Resolutions and amendments. + 6. Together with the Technical Committee, appoint new members to the + Committee. (See §6.2.) + 7. Use a casting vote when Developers vote. + The Project Leader also has a normal vote in such ballots. + 8. Vary the discussion period for Developers' votes (as above). + 9. Lead discussions amongst Developers. + The Project Leader should attempt to participate in discussions + amongst the Developers in a helpful way which seeks to bring the + discussion to bear on the key issues at hand. The Project Leader + should not use the Leadership position to promote their own + personal views. + 10. Together with SPI, make decisions affecting property held in trust + for purposes related to Debian. (See §9.1.) + + 5.2. Appointment + + 1. The Project Leader is elected by the Developers. + 2. The election begins nine weeks before the leadership post becomes + vacant, or (if it is too late already) immediately. + 3. For the following three weeks any Developer may nominate themselves + as a candidate Project Leader. + 4. For three weeks after that no more candidates may be nominated; + candidates should use this time for campaigning (to make their + identities and positions known). If there are no candidates at the + end of the nomination period then the nomination period is extended + for three further weeks, repeatedly if necessary. + 5. The next three weeks are the polling period during which Developers + may cast their votes. Votes in leadership elections are kept + secret, even after the election is finished. + 6. The options on the ballot will be those candidates who have + nominated themselves and have not yet withdrawn, plus None Of The + Above. If None Of The Above wins the election then the election + procedure is repeated, many times if necessary. + 7. The decision will be made using the method specified in section + §A.6 of the Standard Resolution Procedure. The quorum is the same + as for a General Resolution (§4.2) and the default option is "None + Of The Above". + 8. The Project Leader serves for one year from their election. + + 5.3. Procedure + + The Project Leader should attempt to make decisions which are + consistent with the consensus of the opinions of the Developers. + + Where practical the Project Leader should informally solicit the views + of the Developers. + + The Project Leader should avoid overemphasizing their own point of view + when making decisions in their capacity as Leader. + +6. Technical committee + + 6.1. Powers + + The Technical Committee may: + 1. Decide on any matter of technical policy. + This includes the contents of the technical policy manuals, + developers' reference materials, example packages and the behaviour + of non-experimental package building tools. (In each case the usual + maintainer of the relevant software or documentation makes + decisions initially, however; see 6.3(5).) + 2. Decide any technical matter where Developers' jurisdictions + overlap. + In cases where Developers need to implement compatible technical + policies or stances (for example, if they disagree about the + priorities of conflicting packages, or about ownership of a command + name, or about which package is responsible for a bug that both + maintainers agree is a bug, or about who should be the maintainer + for a package) the technical committee may decide the matter. + 3. Make a decision when asked to do so. + Any person or body may delegate a decision of their own to the + Technical Committee, or seek advice from it. + 4. Overrule a Developer (requires a 3:1 majority). + The Technical Committee may ask a Developer to take a particular + technical course of action even if the Developer does not wish to; + this requires a 3:1 majority. For example, the Committee may + determine that a complaint made by the submitter of a bug is + justified and that the submitter's proposed solution should be + implemented. + 5. Offer advice. + The Technical Committee may make formal announcements about its + views on any matter. Individual members may of course make informal + statements about their views and about the likely views of the + committee. + 6. Together with the Project Leader, appoint new members to itself or + remove existing members. (See §6.2.) + 7. Appoint the Chairman of the Technical Committee. + The Chairman is elected by the Committee from its members. All + members of the committee are automatically nominated; the committee + votes starting one week before the post will become vacant (or + immediately, if it is already too late). The members may vote by + public acclamation for any fellow committee member, including + themselves; there is no default option. The vote finishes when all + the members have voted, or when the voting period has ended. The + result is determined using the method specified in section A.6 of + the Standard Resolution Procedure. + 8. The Chairman can stand in for the Leader, together with the + Secretary + As detailed in §7.1(2), the Chairman of the Technical Committee and + the Project Secretary may together stand in for the Leader if there + is no Leader. + + 6.2. Composition + + 1. The Technical Committee consists of up to 8 Developers, and should + usually have at least 4 members. + 2. When there are fewer than 8 members the Technical Committee may + recommend new member(s) to the Project Leader, who may choose + (individually) to appoint them or not. + 3. When there are 5 members or fewer the Technical Committee may + appoint new member(s) until the number of members reaches 6. + 4. When there have been 5 members or fewer for at least one week the + Project Leader may appoint new member(s) until the number of + members reaches 6, at intervals of at least one week per + appointment. + 5. If the Technical Committee and the Project Leader agree they may + remove or replace an existing member of the Technical Committee. + + 6.3. Procedure + + 1. The Technical Committee uses the Standard Resolution Procedure. + A draft resolution or amendment may be proposed by any member of + the Technical Committee. There is no minimum discussion period; the + voting period lasts for up to one week, or until the outcome is no + longer in doubt. Members may change their votes. There is a quorum + of two. + 2. Details regarding voting + The Chairman has a casting vote. When the Technical Committee votes + whether to override a Developer who also happens to be a member of + the Committee, that member may not vote (unless they are the + Chairman, in which case they may use only their casting vote). + 3. Public discussion and decision-making. + Discussion, draft resolutions and amendments, and votes by members + of the committee, are made public on the Technical Committee public + discussion list. There is no separate secretary for the Committee. + 4. Confidentiality of appointments. + The Technical Committee may hold confidential discussions via + private email or a private mailing list or other means to discuss + appointments to the Committee. However, votes on appointments must + be public. + 5. No detailed design work. + The Technical Committee does not engage in design of new proposals + and policies. Such design work should be carried out by individuals + privately or together and discussed in ordinary technical policy + and design forums. + The Technical Committee restricts itself to choosing from or + adopting compromises between solutions and decisions which have + been proposed and reasonably thoroughly discussed elsewhere. + Individual members of the technical committee may of course + participate on their own behalf in any aspect of design and policy + work. + 6. Technical Committee makes decisions only as last resort. + The Technical Committee does not make a technical decision until + efforts to resolve it via consensus have been tried and failed, + unless it has been asked to make a decision by the person or body + who would normally be responsible for it. + +7. The Project Secretary + + 7.1. Powers + + The Secretary: + 1. Takes votes amongst the Developers, and determines the number and + identity of Developers, whenever this is required by the + constitution. + 2. Can stand in for the Leader, together with the Chairman of the + Technical Committee. + If there is no Project Leader then the Chairman of the Technical + Committee and the Project Secretary may by joint agreement make + decisions if they consider it imperative to do so. + 3. Adjudicates any disputes about interpretation of the constitution. + 4. May delegate part or all of their authority to someone else, or + withdraw such a delegation at any time. + + 7.2. Appointment + + The Project Secretary is appointed by the Project Leader and the + current Project Secretary. + + If the Project Leader and the current Project Secretary cannot agree on + a new appointment they must ask the board of SPI (see §9.1.) to appoint + a Secretary. + + If there is no Project Secretary or the current Secretary is + unavailable and has not delegated authority for a decision then the + decision may be made or delegated by the Chairman of the Technical + Committee, as Acting Secretary. + + The Project Secretary's term of office is 1 year, at which point they + or another Secretary must be (re)appointed. + + 7.3. Procedure + + The Project Secretary should make decisions which are fair and + reasonable, and preferably consistent with the consensus of the + Developers. + + When acting together to stand in for an absent Project Leader the + Chairman of the Technical Committee and the Project Secretary should + make decisions only when absolutely necessary and only when consistent + with the consensus of the Developers. + +8. The Project Leader's Delegates + + 8.1. Powers + + The Project Leader's Delegates: + 1. have powers delegated to them by the Project Leader; + 2. may make certain decisions which the Leader may not make directly, + including approving or expelling Developers or designating people + as Developers who do not maintain packages. This is to avoid + concentration of power, particularly over membership as a + Developer, in the hands of the Project Leader. + + 8.2. Appointment + + The Delegates are appointed by the Project Leader and may be replaced + by the Leader at the Leader's discretion. The Project Leader may not + make the position as a Delegate conditional on particular decisions by + the Delegate, nor may they override a decision made by a Delegate once + made. + + 8.3. Procedure + + Delegates may make decisions as they see fit, but should attempt to + implement good technical decisions and/or follow consensus opinion. + +9. Software in the Public Interest + + SPI and Debian are separate organisations who share some goals. Debian + is grateful for the legal support framework offered by SPI. Debian's + Developers are currently members of SPI by virtue of their status as + Developers. + + 9.1. Authority + + 1. SPI has no authority regarding Debian's technical or nontechnical + decisions, except that no decision by Debian with respect to any + property held by SPI shall require SPI to act outside its legal + authority, and that Debian's constitution may occasionally use SPI + as a decision body of last resort. + 2. Debian claims no authority over SPI other than that over the use of + certain of SPI's property, as described below, though Debian + Developers may be granted authority within SPI by SPI's rules. + 3. Debian Developers are not agents or employees of SPI, or of each + other or of persons in authority in the Debian Project. A person + acting as a Developer does so as an individual, on their own + behalf. + + 9.2. Management of property for purposes related to Debian + + Since Debian has no authority to hold money or property, any donations + for the Debian Project must be made to SPI, which manages such affairs. + + SPI have made the following undertakings: + 1. SPI will hold money, trademarks and other tangible and intangible + property and manage other affairs for purposes related to Debian. + 2. Such property will be accounted for separately and held in trust + for those purposes, decided on by Debian and SPI according to this + section. + 3. SPI will not dispose of or use property held in trust for Debian + without approval from Debian, which may be granted by the Project + Leader or by General Resolution of the Developers. + 4. SPI will consider using or disposing of property held in trust for + Debian when asked to do so by the Project Leader. + 5. SPI will use or dispose of property held in trust for Debian when + asked to do so by a General Resolution of the Developers, provided + that this is compatible with SPI's legal authority. + 6. SPI will notify the Developers by electronic mail to a Debian + Project mailing list when it uses or disposes of property held in + trust for Debian. + +A. Standard Resolution Procedure + + These rules apply to communal decision-making by committees and + plebiscites, where stated above. + + A.1. Proposal + + The formal procedure begins when a draft resolution is proposed and + sponsored, as required. + + A.1. Discussion and Amendment + + 1. Following the proposal, the resolution may be discussed. Amendments + may be made formal by being proposed and sponsored according to the + requirements for a new resolution, or directly by the proposer of + the original resolution. + 2. A formal amendment may be accepted by the resolution's proposer, in + which case the formal resolution draft is immediately changed to + match. + 3. If a formal amendment is not accepted, or one of the sponsors of + the resolution does not agree with the acceptance by the proposer + of a formal amendment, the amendment remains as an amendment and + will be voted on. + 4. If an amendment accepted by the original proposer is not to the + liking of others, they may propose another amendment to reverse the + earlier change (again, they must meet the requirements for proposer + and sponsor(s).) + 5. The proposer of a resolution may suggest changes to the wordings of + amendments; these take effect if the proposer of the amendment + agrees and none of the sponsors object. In this case the changed + amendments will be voted on instead of the originals. + 6. The proposer of a resolution may make changes to correct minor + errors (for example, typographical errors or inconsistencies) or + changes which do not alter the meaning, providing noone objects + within 24 hours. In this case the minimum discussion period is not + restarted. + + A.2. Calling for a vote + + 1. The proposer or a sponsor of a motion or an amendment may call for + a vote, providing that the minimum discussion period (if any) has + elapsed. + 2. The proposer or any sponsor of a resolution may call for a vote on + that resolution and all related amendments. + 3. The person who calls for a vote states what they believe the + wordings of the resolution and any relevant amendments are, and + consequently what form the ballot should take. However, the final + decision on the form of ballot(s) is the Secretary's - see 7.1(1), + 7.1(3) and A.3(4). + 4. The minimum discussion period is counted from the time the last + formal amendment was accepted, or since the whole resolution was + proposed if no amendments have been proposed and accepted. + + A.3. Voting procedure + + 1. Each resolution and its related amendments is voted on in a single + ballot that includes an option for the original resolution, each + amendment, and the default option (where applicable). + 2. The default option must not have any supermajority requirements. + Options which do not have an explicit supermajority requirement + have a 1:1 majority requirement. + 3. The votes are counted according to the rules in A.6. The default + option is "Further Discussion", unless specified otherwise. + 4. In cases of doubt the Project Secretary shall decide on matters of + procedure. + + A.4. Withdrawing resolutions or unaccepted amendments + + The proposer of a resolution or unaccepted amendment may withdraw it. + In this case new proposers may come forward keep it alive, in which + case the first person to do so becomes the new proposer and any others + become sponsors if they aren't sponsors already. + + A sponsor of a resolution or amendment (unless it has been accepted) + may withdraw. + + If the withdrawal of the proposer and/or sponsors means that a + resolution has no proposer or not enough sponsors it will not be voted + on unless this is rectified before the resolution expires. + + A.5. Expiry + + If a proposed resolution has not been discussed, amended, voted on or + otherwise dealt with for 4 weeks the secretary may issue a statement + that the issue is being withdrawn. If none of the sponsors of any of + the proposals object within a week, the issue is withdrawn. + + The secretary may also include suggestions on how to proceed, if + appropriate. + + A.6. Vote Counting + + 1. Each voter's ballot ranks the options being voted on. Not all + options need be ranked. Ranked options are considered preferred to + all unranked options. Voters may rank options equally. Unranked + options are considered to be ranked equally with one another. + Details of how ballots may be filled out will be included in the + Call For Votes. + 2. If the ballot has a quorum requirement R any options other than the + default option which do not receive at least R votes ranking that + option above the default option are dropped from consideration. + 3. Any (non-default) option which does not defeat the default option + by its required majority ratio is dropped from consideration. + 1. Given two options A and B, V(A,B) is the number of voters who + prefer option A over option B. + 2. An option A defeats the default option D by a majority ratio + N, if V(A,D) is strictly greater than N * V(D,A). + 3. If a supermajority of S:1 is required for A, its majority + ratio is S; otherwise, its majority ratio is 1. + 4. From the list of undropped options, we generate a list of pairwise + defeats. + 1. An option A defeats an option B, if V(A,B) is strictly greater + than V(B,A). + 5. From the list of [undropped] pairwise defeats, we generate a set of + transitive defeats. + 1. An option A transitively defeats an option C if A defeats C or + if there is some other option B where A defeats B AND B + transitively defeats C. + 6. We construct the Schwartz set from the set of transitive defeats. + 1. An option A is in the Schwartz set if for all options B, + either A transitively defeats B, or B does not transitively + defeat A. + 7. If there are defeats between options in the Schwartz set, we drop + the weakest such defeats from the list of pairwise defeats, and + return to step 5. + 1. A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) is less + than V(B,Y). Also, (A,X) is weaker than (B,Y) if V(A,X) is + equal to V(B,Y) and V(X,A) is greater than V(Y,B). + 2. A weakest defeat is a defeat that has no other defeat weaker + than it. There may be more than one such defeat. + 8. If there are no defeats within the Schwartz set, then the winner is + chosen from the options in the Schwartz set. If there is only one + such option, it is the winner. If there are multiple options, the + elector with the casting vote chooses which of those options wins. + + Note: Options which the voters rank above the default option are + options they find acceptable. Options ranked below the default options + are options they find unacceptable. + + When the Standard Resolution Procedure is to be used, the text which + refers to it must specify what is sufficient to have a draft resolution + proposed and/or sponsored, what the minimum discussion period is, and + what the voting period is. It must also specify any supermajority + and/or the quorum (and default option) to be used. + +B. Use of language and typography + + The present indicative ("is", for example) means that the statement is + a rule in this constitution. "ay" or "can" indicates that the person or + body has discretion. "Should" means that it would be considered a good + thing if the sentence were obeyed, but it is not binding. Text marked + as a citation, such as this, is rationale and does not form part of the + constitution. It may be used only to aid interpretation in cases of + doubt. diff --git a/includes/lenny/common/doc/debian-manifesto b/includes/lenny/common/doc/debian-manifesto new file mode 100644 index 000000000..9322c934f --- /dev/null +++ b/includes/lenny/common/doc/debian-manifesto @@ -0,0 +1,135 @@ +Please note that this document is provided in order to document +Debian's history. While the general ideas still apply some details +changed. + + +******************** +Appendix +The Debian Manifesto +******************** + + + The Debian Linux Manifesto + + Written by Ian A. Murdock + Revised 01/06/94 + + +What is Debian Linux? +===================== + +Debian Linux is a brand-new kind of Linux distribution. Rather than +being developed by one isolated individual or group, as other +distributions of Linux have been developed in the past, Debian is being +developed openly in the spirit of Linux and GNU. The primary purpose +of the Debian project is to finally create a distribution that lives up +to the Linux name. Debian is being carefully and conscientiously put +together and will be maintained and supported with similar care. + +It is also an attempt to create a non-commercial distribution that will +be able to effectively compete in the commercial market. It will +eventually be distributed by The Free Software Foundation on CD-ROM, +and The Debian Linux Association will offer the distribution on floppy +disk and tape along with printed manuals, technical support and other +end-user essentials. All of the above will be available at little more +than cost, and the excess will be put toward further development of +free software for all users. Such distribution is essential to the +success of the Linux operating system in the commercial market, and it +must be done by organizations in a position to successfully advance and +advocate free software without the pressure of profits or returns. + + +Why is Debian being constructed? +================================ + +Distributions are essential to the future of Linux. Essentially, they +eliminate the need for the user to locate, download, compile, install +and integrate a fairly large number of essential tools to assemble a +working Linux system. Instead, the burden of system construction is +placed on the distribution creator, whose work can be shared with +thousands of other users. Almost all users of Linux will get their +first taste of it through a distribution, and most users will continue +to use a distribution for the sake of convenience even after they are +familiar with the operating system. Thus, distributions play a very +important role indeed. + +Despite their obvious importance, distributions have attracted little +attention from developers. There is a simple reason for this: they are +neither easy nor glamorous to construct and require a great deal of +ongoing effort from the creator to keep the distribution bug-free and +up-to-date. It is one thing to put together a system from scratch; it +is quite another to ensure that the system is easy for others to +install, is installable and usable under a wide variety of hardware +configurations, contains software that others will find useful, and is +updated when the components themselves are improved. + +Many distributions have started out as fairly good systems, but as time +passes attention to maintaining the distribution becomes a secondary +concern. A case-in-point is the Softlanding Linux System (better known +as SLS). It is quite possibly the most bug-ridden and badly maintained +Linux distribution available; unfortunately, it is also quite possibly +the most popular. It is, without question, the distribution that +attracts the most attention from the many commercial "distributors" of +Linux that have surfaced to capitalize on the growing popularity of the +operating system. + +This is a bad combination indeed, as most people who obtain Linux from +these "distributors" receive a bug-ridden and badly maintained Linux +distribution. As if this wasn't bad enough, these "distributors" have +a disturbing tendency to misleadingly advertise non-functional or +extremely unstable "features" of their product. Combine this with the +fact that the buyers will, of course, expect the product to live up to +its advertisement and the fact that many may believe it to be a +commercial operating system (there is also a tendency not to mention +that Linux is free nor that it is distributed under the GNU General +Public License). To top it all off, these "distributors" are actually +making enough money from their effort to justify buying larger +advertisements in more magazines; it is the classic example of +unacceptable behavior being rewarded by those who simply do not know +any better. Clearly something needs to be done to remedy the +situation. + + +How will Debian attempt to put an end to these problems? +======================================================== + +The Debian design process is open to ensure that the system is of the +highest quality and that it reflects the needs of the user community. +By involving others with a wide range of abilities and backgrounds, +Debian is able to be developed in a modular fashion. Its components +are of high quality because those with expertise in a certain area are +given the opportunity to construct or maintain the individual +components of Debian involving that area. Involving others also +ensures that valuable suggestions for improvement can be incorporated +into the distribution during its development; thus, a distribution is +created based on the needs and wants of the users rather than the needs +and wants of the constructor. It is very difficult for one individual +or small group to anticipate these needs and wants in advance without +direct input from others. + +Debian Linux will also be distributed on physical media by the Free +Software Foundation and the Debian Linux Association. This provides +Debian to users without access to the Internet or FTP and additionally +makes products and services such as printed manuals and technical +support available to all users of the system. In this way, Debian may +be used by many more individuals and organizations than is otherwise +possible, the focus will be on providing a first-class product and not +on profits or returns, and the margin from the products and services +provided may be used to improve the software itself for all users +whether they paid to obtain it or not. + +The Free Software Foundation plays an extremely important role in the +future of Debian. By the simple fact that they will be distributing +it, a message is sent to the world that Linux is not a commercial +product and that it never should be, but that this does not mean that +Linux will never be able to compete commercially. For those of you who +disagree, I challenge you to rationalize the success of GNU Emacs and +GCC, which are not commercial software but which have had quite an +impact on the commercial market regardless of that fact. + +The time has come to concentrate on the future of Linux rather than on +the destructive goal of enriching oneself at the expense of the entire +Linux community and its future. The development and distribution of +Debian may not be the answer to the problems that I have outlined in +the Manifesto, but I hope that it will at least attract enough +attention to these problems to allow them to be solved. diff --git a/includes/lenny/common/doc/mailing-lists.txt b/includes/lenny/common/doc/mailing-lists.txt new file mode 100644 index 000000000..84010d8df --- /dev/null +++ b/includes/lenny/common/doc/mailing-lists.txt @@ -0,0 +1,1266 @@ + Introduction to the Debian mailing lists + ======================================== + + Debian GNU/Linux is developed through distributed development all + around the world. Therefore, email is the preferred way to discuss + various items. Much of the conversation between Debian developers + and users is managed through several mailing lists. + + There are many world-open mailing lists, meaning anyone can read + everything that is posted, and participate in the discussions. Everyone is + encouraged to help development of Debian and to spread the word of free + software. There are also a few lists which are only open to official Debian + developers; please don't interpret this as closed development, it sometimes + doesn't make much sense discussing internal topics with non-developers. + + All original Debian mailing lists run on a special server, using an + automatic mail processing software called SmartList. This server is called + lists.debian.org. All submission, subscription and unsubscription messages + have to be sent to a particular address at this host. + + The language used on all lists is English, unless stated otherwise. + There are some user lists for other languages available. + +Subscription / Unsubscription +----------------------------- + + Anyone is able to subscribe/unsubscribe on their own to any mailing list, + presuming the subscription policy for a particular list is `open'. + + The requests for subscription or unsubscription can be sent to a special + control address, which is slightly different from the list address. + Subscription or unsubscription messages should NOT be sent to the address + of the mailing list itself. + + To subscribe or unsubscribe from a mailing list, please send mail to + + -REQUEST@lists.debian.org + + with the word `subscribe' or `unsubscribe' as subject. + + Please remember the -REQUEST part of the address. + + As part of the subscription process, the list software will send you an + email to which you must reply in order to finish subscribing. This is a + security measure to keep people from subscribing others to the lists without + their permission. + + If you need to contact a human listmaster, direct your mail to + listmaster@lists.debian.org . To find out who is responsible for the + lists, take a look at http://www.debian.org/intro/organization + +User lists + + There are several user based mailing lists where developers and + users can get in contact to discuss and solve problems. + + debian-announce@lists.debian.org + + Description : Important announcements + Moderated : yes + Subscription: open + + debian-chinese-big5@lists.debian.org + + Description : debian-user in Chinese [Big5] + Language : Chinese + Moderated : subscribers + Subscription: open + + debian-chinese-gb@lists.debian.org + + Description : debian-user in Chinese [GB] + Language : Chinese + Moderated : subscribers + Subscription: open + + debian-edu-announce@lists.debian.org + + Description : Announcements for the debian-edu archive + Moderated : yes + Subscription: open + + debian-enterprise@lists.debian.org + + Description : Debian for the enterprise + Moderated : no + Subscription: open + + debian-esperanto@lists.debian.org + + Description : debian-user in Esperanto + Language : Esperanto + Moderated : no + Subscription: open + + debian-firewall@lists.debian.org + + Description : Running a firewall on Debian + Moderated : no + Subscription: open + + debian-infrastructure-announce@lists.debian.org + + Description : Infrastructure announcements + Moderated : signed + Subscription: open + + debian-isp@lists.debian.org + + Description : Debian at Internet Service Providers + Moderated : no + Subscription: open + + debian-italian@lists.debian.org + + Description : debian-user in Italian + Language : Italian + Moderated : no + Subscription: open + + debian-japanese@lists.debian.org + + Description : debian-user in Japanese + Language : English/Japanese + Moderated : no + Subscription: open + + debian-kde@lists.debian.org + + Description : KDE in Debian + Moderated : no + Subscription: open + + debian-laptop@lists.debian.org + + Description : Debian on mobile computers + Moderated : no + Subscription: open + + debian-news-french@lists.debian.org + + Description : French Debian News, weekly and otherwise + Language : French + Moderated : yes + Subscription: open + + debian-news-german@lists.debian.org + + Description : German Debian News, weekly and otherwise + Language : German + Moderated : yes + Subscription: open + + debian-news-italian@lists.debian.org + + Description : Italian Debian News, weekly and otherwise + Language : Italian + Moderated : yes + Subscription: open + + debian-news-portuguese@lists.debian.org + + Description : Portuguese Debian News, weekly and otherwise + Language : Portuguese + Moderated : yes + Subscription: open + + debian-news-spanish@lists.debian.org + + Description : Spanish Debian News, weekly and otherwise + Language : Spanish + Moderated : yes + Subscription: open + + debian-news@lists.debian.org + + Description : Debian News, weekly and otherwise + Moderated : yes + Subscription: open + + debian-photo@lists.debian.org + + Description : Using Debian for photography + Moderated : no + Subscription: open + + debian-russian@lists.debian.org + + Description : debian-user in Russian + Language : Russian + Moderated : no + Subscription: open + + debian-security-announce@lists.debian.org + + Description : Security announcements + Moderated : yes + Subscription: open + + debian-security@lists.debian.org + + Description : Security in Debian + Moderated : no + Subscription: open + + debian-testing-security-announce@lists.debian.org + + Description : Security announcements for testing + Moderated : yes + Subscription: open + + debian-user-catalan@lists.debian.org + + Description : debian-user in Catalan + Language : Catalan + Moderated : no + Subscription: open + + debian-user-danish@lists.debian.org + + Description : debian-user in Danish + Language : Danish + Moderated : no + Subscription: open + + debian-user-french@lists.debian.org + + Description : debian-user in French + Language : French + Moderated : no + Subscription: open + + debian-user-german@lists.debian.org + + Description : debian-user in German + Language : German + Moderated : no + Subscription: open + + debian-user-hungarian + + Description : debian-user in Hungarian + Language : Hungarian + Subscription: http://lists.linux.hu/mailman/listinfo/debian + + debian-user-icelandic@lists.debian.org + + Description : debian-user in Icelandic + Moderated : no + Subscription: open + + debian-user-indonesian@lists.debian.org + + Description : debian-user in Indonesian + Language : Indonesian + Moderated : no + Subscription: open + + debian-user-polish@lists.debian.org + + Description : debian-user in Polish + Language : Polish + Moderated : no + Subscription: open + + debian-user-portuguese@lists.debian.org + + Description : debian-user in Portuguese + Language : Portuguese (both European and Brazilian, and other dialects are welcome) + Moderated : no + Subscription: open + + debian-user-spanish@lists.debian.org + + Description : debian-user in Spanish + Language : Spanish + Moderated : no + Subscription: open + + debian-user-swedish@lists.debian.org + + Description : debian-user in Swedish + Language : Swedish + Moderated : no + Subscription: open + + debian-user-turkish@lists.debian.org + + Description : debian-user in Turkish + Language : Turkish + Moderated : no + Subscription: open + + debian-user-ukrainian@lists.debian.org + + Description : debian-user in Ukrainian + Language : Ukrainian + Moderated : no + Subscription: open + + debian-user-vietnamese@lists.debian.org + + Description : debian-user in Vietnamese + Language : Vietnamese + Moderated : no + Subscription: open + + debian-user@lists.debian.org + + Description : Help and discussion among users of Debian + Digest : debian-user-digest@lists.debian.org + Moderated : no + Subscription: open + + debian-volatile-announce@lists.debian.org + + Description : Announcements for the debian-volatile archive + Moderated : yes + Subscription: open + + debian-volatile@lists.debian.org + + Description : Using the debian-volatile archive + Moderated : no + Subscription: open + +Development lists + + There are several lists on which developers and experienced + users discuss more technical issues. In addition, there are some + announcement lists to help experienced users keep track of + development. + + debian-accessibility@lists.debian.org + + Description : Making Debian more accessible to people with disabilities + Moderated : no + Subscription: open + + debian-apache@lists.debian.org + + Description : Maintaining the Debian Apache (web server) and related packages + Moderated : no + Subscription: open + + debian-beowulf@lists.debian.org + + Description : Debian on Beowulf clusters + Moderated : no + Subscription: open + + debian-boot@lists.debian.org + + Description : Developing the installation system + Moderated : no + Subscription: open + + debian-cd@lists.debian.org + + Description : Creating Debian CD Images + Moderated : no + Subscription: open + + debian-ctte-private@lists.debian.org + + Description : Debian Technical Committee private list [dead list] + Moderated : yes + Subscription: Debian Technical Committee only + + debian-ctte@lists.debian.org + + Description : Debian Technical Committee + Moderated : subscribers + Subscription: open + + debian-custom@lists.debian.org + + Description : Developing common infrastructure for custom Debian distributions + Moderated : no + Subscription: open + + debian-dak@lists.debian.org + + Description : Debian Archive Kit / Buildd list + Moderated : no + Subscription: open + + debian-ddtp@lists.debian.org + + Description : DDTP coordination + Moderated : no + Subscription: open + + debian-debbugs-cvs@lists.debian.org + + Description : debbugs CVS commits + Moderated : yes + Subscription: open + + debian-debbugs@lists.debian.org + + Description : debbugs, the Debian bug tracking system + Moderated : no + Subscription: open + + debian-desktop@lists.debian.org + + Description : Debian Desktop project + Moderated : no + Subscription: open + + debian-devel-announce@lists.debian.org + + Description : Announcements for developers + Moderated : signed + Subscription: open + + debian-devel-austrian + + Description : Development discussions among Austrians + Language : (mostly) German + Subscription: https://www.gibraltar.at/mailman/listinfo/debian-at + + debian-devel-french@lists.debian.org + + Description : Development discussions in French + Language : French + Moderated : no + Subscription: open + + debian-devel-games@lists.debian.org + + Description : Development of games in Debian + Moderated : no + Subscription: open + + debian-devel-italian@lists.debian.org + + Description : Development discussions in Italian + Language : Italian + Moderated : no + Subscription: open + + debian-devel-portuguese@lists.debian.org + + Description : Development discussions in Portuguese + Language : Portuguese + Moderated : no + Subscription: open + + debian-devel-spanish@lists.debian.org + + Description : Development discussions in Spanish + Language : Spanish + Moderated : no + Subscription: open + + debian-devel@lists.debian.org + + Description : Development of Debian + Digest : debian-devel-digest@lists.debian.org + Moderated : no + Subscription: open + + debian-doc@lists.debian.org + + Description : Writing documentation for Debian + Moderated : no + Subscription: open + + debian-dpkg-bugs@lists.debian.org + + Description : dpkg bug reports + Moderated : no + Subscription: open + + debian-dpkg-cvs@lists.debian.org + + Description : dpkg CVS commits + Moderated : yes + Subscription: open + + debian-dpkg@lists.debian.org + + Description : Development of dpkg + Moderated : no + Subscription: open + + debian-edu-french@lists.debian.org + + Description : Discussion between French educational Debian-based projects + Moderated : no + Subscription: open + + debian-edu@lists.debian.org + + Description : Making Debian desirable for education purposes + Moderated : no + Subscription: open + + debian-emacsen@lists.debian.org + + Description : Maintaining Emacsen + Moderated : no + Subscription: open + + debian-email@lists.debian.org + + Description : Generic "grab-bag" list for Debian-related communication + Moderated : no + Subscription: developers only + + debian-embedded@lists.debian.org + + Description : Debian on embedded systems + Moderated : no + Subscription: open + + debian-flash@lists.debian.org + + Description : development and use of flash technologies on Debian + Moderated : no + Subscription: open + + debian-gcc@lists.debian.org + + Description : Debian GCC Maintainers + Moderated : no + Subscription: open + + debian-glibc@lists.debian.org + + Description : Maintaining GNU C Library packages + Moderated : no + Subscription: open + + debian-gtk-gnome@lists.debian.org + + Description : Packages using GTK+ and/or GNOME + Moderated : no + Subscription: open + + debian-hams@lists.debian.org + + Description : Development of HAM Radio under Debian + Moderated : no + Subscription: open + + debian-handheld@lists.debian.org + + Description : Debian on handheld computers + Moderated : no + Subscription: open + + debian-haskell@lists.debian.org + + Description : Haskell packages and maintenance + Moderated : no + Subscription: open + + debian-ipv6@lists.debian.org + + Description : IPv6 Maintenance + Moderated : no + Subscription: open + + debian-java@lists.debian.org + + Description : Java Maintenance + Moderated : no + Subscription: open + + debian-jr@lists.debian.org + + Description : Making Debian desirable for children + Moderated : no + Subscription: open + + debian-kernel-maint@lists.debian.org + + Description : Debian kernel development and discussion + Moderated : no + Subscription: open + + debian-kernel@lists.debian.org + + Description : Kernel packages in Debian + Moderated : no + Subscription: open + + debian-knoppix@lists.debian.org + + Description : Development of the Knoppix Live CD/DVD + Moderated : no + Subscription: open + + debian-lex@lists.debian.org + + Description : Making Debian desirable for lawyers + Moderated : no + Subscription: open + + debian-lint-maint@lists.debian.org + + Description : Maintenance of Debian `lint' tools like lintian or linda + Moderated : no + Subscription: open + + debian-live@lists.debian.org + + Description : Discussion and maintenance of the Debian Live systems + Moderated : no + Subscription: open + + debian-lsb@lists.debian.org + + Description : Debian and the Linux Standard Base + Moderated : no + Subscription: open + + debian-med@lists.debian.org + + Description : Making Debian desirable for doctors + Moderated : no + Subscription: open + + debian-mentors@lists.debian.org + + Description : Helping newbie developers + Moderated : no + Subscription: open + + debian-multimedia@lists.debian.org + + Description : Multimedia support and applications + Moderated : no + Subscription: open + + debian-ocaml-maint@lists.debian.org + + Description : ocaml package maintenance and development + Moderated : no + Subscription: open + + debian-openoffice@lists.debian.org + + Description : OpenOffice packages maintenance + Moderated : no + Subscription: open + + debian-perl@lists.debian.org + + Description : Perl packages maintenance + Moderated : no + Subscription: open + + debian-policy@lists.debian.org + + Description : Creating and editing Debian Policy + Moderated : no + Subscription: open + + debian-printing@lists.debian.org + + Description : Debian Printing Infrastructure + Moderated : no + Subscription: open + + debian-private@lists.debian.org + + Description : Private discussions among developers + Moderated : no + Subscription: developers only + + debian-python@lists.debian.org + + Description : Python packages maintenance + Moderated : no + Subscription: open + + debian-qa-packages@lists.debian.org + + Description : Orphaned packages maintained by the QA group + Moderated : no + Subscription: open + + debian-qa@lists.debian.org + + Description : Quality Assurance + Moderated : no + Subscription: open + + debian-qt-kde@lists.debian.org + + Description : Packages using Qt and/or KDE + Moderated : no + Subscription: open + + debian-release@lists.debian.org + + Description : Coordinating Debian releases + Moderated : no + Subscription: open + + debian-ruby@lists.debian.org + + Description : Ruby packages maintenance + Moderated : no + Subscription: open + + debian-science@lists.debian.org + + Description : using debian for science and related research + Moderated : no + Subscription: open + + debian-security-tracker@lists.debian.org + + Description : Discussion about the Debian Security Tracker + Moderated : no + Subscription: open + + debian-sgml@lists.debian.org + + Description : Debian and SGML + Moderated : no + Subscription: open + + debian-ssh@lists.debian.org + + Description : SSH packages maintenance + Moderated : no + Subscription: open + + debian-testing@lists.debian.org + + Description : Testing for the next release + Moderated : no + Subscription: open + + debian-tex-maint@lists.debian.org + + Description : Coordination of the maintenance of TeX packages in Debian + Moderated : no + Subscription: open + + debian-toolchain@lists.debian.org + + Description : Compilers, assemblers etc. + Moderated : no + Subscription: open + + debian-webapps@lists.debian.org + + Description : Web applications packaging + Moderated : no + Subscription: open + + debian-wnpp@lists.debian.org + + Description : Work-Needing and Prospective Packages + Moderated : no + Subscription: open + + debian-www-cvs@lists.debian.org + + Description : Web pages CVS commits + Moderated : yes + Subscription: open + + debian-www@lists.debian.org + + Description : Web pages design and maintenance + Moderated : no + Subscription: open + + debian-x@lists.debian.org + + Description : Debian XFree86 packaging + Moderated : no + Subscription: open + + deity@lists.debian.org + + Description : APT packages maintenance + Moderated : no + Subscription: open + +Internationalization and Translations + + These lists cover issues like localization, translation and support for + users that don't speak English. + + debian-i18n@lists.debian.org + + Description : Debian Internationalization + Moderated : no + Subscription: open + + debian-l10n-arabic@lists.debian.org + + Description : Arabic Localization + Language : Arabic + Moderated : no + Subscription: open + + debian-l10n-basque@lists.debian.org + + Description : Basque localization + Language : Basque + Moderated : no + Subscription: open + + debian-l10n-catalan@lists.debian.org + + Description : Catalan Localization + Language : Catalan + Moderated : no + Subscription: open + + debian-l10n-czech@lists.debian.org + + Description : Czech Localization + Moderated : no + Subscription: open + + debian-l10n-danish@lists.debian.org + + Description : Danish Localization + Language : Danish + Moderated : no + Subscription: open + + debian-l10n-dutch@lists.debian.org + + Description : Dutch Localization + Language : Dutch + Moderated : no + Subscription: open + + debian-l10n-english@lists.debian.org + + Description : English Localization + Language : English + Moderated : no + Subscription: open + + debian-l10n-esperanto@lists.debian.org + + Description : Esperanto Localization + Language : Esperanto + Moderated : no + Subscription: open + + debian-l10n-finnish@lists.debian.org + + Description : Finnish Localization + Language : Finnish + Moderated : no + Subscription: open + + debian-l10n-french@lists.debian.org + + Description : French Localization + Language : French + Moderated : no + Subscription: open + + debian-l10n-galician@lists.debian.org + + Description : Galician Localization + Language : Galician + Moderated : no + Subscription: open + + debian-l10n-german@lists.debian.org + + Description : German Localization + Language : German + Moderated : no + Subscription: open + + debian-l10n-greek@lists.debian.org + + Description : Greek Localization + Language : Greek + Moderated : no + Subscription: open + + debian-l10n-hungarian@lists.debian.org + + Description : Hungarian Localization + Language : Hungarian + Moderated : no + Subscription: open + + debian-l10n-italian@lists.debian.org + + Description : Italian Localization + Language : Italian + Moderated : no + Subscription: open + + debian-l10n-kannada@lists.debian.org + + Description : Kannada Localization + Language : Kannada + Moderated : no + Subscription: open + + debian-l10n-korean@lists.debian.org + + Description : Korean Localization + Moderated : no + Subscription: open + + debian-l10n-malayalam@lists.debian.org + + Description : Malayalam Localization + Language : Malayalam + Moderated : no + Subscription: open + + debian-l10n-persian@lists.debian.org + + Description : Persian/Farsi Localization + Language : Persian + Moderated : no + Subscription: open + + debian-l10n-polish@lists.debian.org + + Description : Polish Localization + Language : Polish + Moderated : no + Subscription: open + + debian-l10n-portuguese@lists.debian.org + + Description : Portuguese Localization + Language : Portuguese + Moderated : no + Subscription: open + + debian-l10n-romanian@lists.debian.org + + Description : Romanian Localization + Language : Romanian + Moderated : no + Subscription: open + + debian-l10n-russian@lists.debian.org + + Description : Russian Localization + Language : Russian + Moderated : no + Subscription: open + + debian-l10n-spanish@lists.debian.org + + Description : Spanish Localization + Language : Spanish + Moderated : no + Subscription: open + + debian-l10n-swedish@lists.debian.org + + Description : Swedish Localization + Moderated : no + Subscription: open + + debian-l10n-turkish@lists.debian.org + + Description : Turkish Localization + Language : Turkish + Moderated : no + Subscription: open + +Ports to non-i386 Linux architectures and to non-Linux kernels + + Debian GNU/Linux is ported to several other types of computers, and there + are also efforts to create Debian systems on kernels other than Linux. + + debian-68k@lists.debian.org + + Description : Debian port to m68k + Moderated : no + Subscription: open + + debian-alpha@lists.debian.org + + Description : Debian port to Alpha + Moderated : no + Subscription: open + + debian-amd64@lists.debian.org + + Description : Debian port to AMD64 + Moderated : no + Subscription: open + + debian-arm@lists.debian.org + + Description : Debian port to ARM + Moderated : no + Subscription: open + + debian-bsd@lists.debian.org + + Description : Debian port to BSD + Moderated : no + Subscription: open + + debian-hppa@lists.debian.org + + Description : Debian port to HPPA + Moderated : no + Subscription: open + + debian-hurd@lists.debian.org + + Description : Debian port to Hurd + Moderated : no + Subscription: open + + debian-ia64@lists.debian.org + + Description : Debian port to Intel IA-64 + Moderated : no + Subscription: open + + debian-mips@lists.debian.org + + Description : Debian port to MIPS + Moderated : no + Subscription: open + + debian-powerpc@lists.debian.org + + Description : Debian port to PowerPC + Moderated : no + Subscription: open + + debian-s390@lists.debian.org + + Description : Debian port to IBM S/390 + Moderated : no + Subscription: open + + debian-sparc@lists.debian.org + + Description : Debian port to SPARC + Moderated : no + Subscription: open + + debian-superh@lists.debian.org + + Description : Debian port to SuperH + Moderated : no + Subscription: open + + debian-win32@lists.debian.org + + Description : Debian port to Win32 + Moderated : no + Subscription: open + +The Bug Tracking System + + The Debian bug tracking system is open to the public, and it produces + a lot of email. Some of this might be of interest to developers or even + users, so it is distributed through these (high-volume) mailing lists. + + debian-bugs-closed@lists.debian.org + + Description : Debian BTS, closed bugs + Moderated : yes + Subscription: open + + debian-bugs-dist@lists.debian.org + + Description : Debian BTS, received bugs + Moderated : yes + Subscription: open + + debian-bugs-forwarded@lists.debian.org + + Description : Debian BTS, forwarded bugs + Moderated : yes + Subscription: open + + debian-bugs-rc@lists.debian.org + + Description : Debian BTS, release-critical bugs + Moderated : yes + Subscription: open + +Miscellaneous Debian lists + + There are several mailing lists which discuss topics that are + not directly related to developing or using Debian, and there + are some that don't necessarily have a clear distinction + between developers and users in the intended audience. + + debian-admin@lists.debian.org + + Description : Internal list for Debian Project machine admins + Moderated : no + Subscription: closed + + debian-changes@lists.debian.org + + Description : Stable packages' upgrade announcements + Digest : debian-changes-digest@lists.debian.org + Moderated : yes + Subscription: open + + debian-consultants@lists.debian.org + + Description : Debian consultants, paid support + Moderated : no + Subscription: open + + debian-curiosa@lists.debian.org + + Description : All the funny stuff regarding Debian + Moderated : no + Subscription: open + + debian-devel-changes@lists.debian.org + + Description : Unstable packages' upgrade announcements + Moderated : yes + Subscription: open + + debian-events-eu@lists.debian.org + + Description : Events with Debian affiliation in Europe + Moderated : no + Subscription: open + + debian-events-na@lists.debian.org + + Description : Events with Debian affiliation in North America + Moderated : no + Subscription: open + + debian-events-nl@lists.debian.org + + Description : Events with Debian affiliation in the Netherlands + Moderated : no + Subscription: open + + debian-jobs@lists.debian.org + + Description : Job postings for members of the Debian community + Moderated : yes + Subscription: open + + debian-legal@lists.debian.org + + Description : Copyright, licensing and patent issues + Moderated : no + Subscription: open + + debian-mirrors-announce@lists.debian.org + + Description : News and announcements regarding FTP archive mirrors + Moderated : signed + Subscription: open + + debian-mirrors@lists.debian.org + + Description : Discussions about the Debian mirror network + Moderated : no + Subscription: open + + debian-newmaint@lists.debian.org + + Description : Debian New Maintainer process discussion + Moderated : no + Subscription: open + + debian-project@lists.debian.org + + Description : Discussions about non-technical issues in the project + Moderated : no + Subscription: open + + debian-publicity@lists.debian.org + + Description : Making Debian famous + Moderated : no + Subscription: open + + debian-testing-changes@lists.debian.org + + Description : Testing packages' upgrade announcements + Moderated : yes + Subscription: open + + debian-vote@lists.debian.org + + Description : Voting announcements and discussion + Moderated : no + Subscription: open + + debian-women@lists.debian.org + + Description : Discussion and collaboration involving women in Debian + Moderated : no + Subscription: open + + whitelist@lists.debian.org + + Description : Generic whitelist + Moderated : yes + Subscription: open + +Lists hosted for other projects + + Our list server provides mailing list facilities for other free + projects as well. + + other-cdwrite@lists.debian.org + + Description : cdwrite + Moderated : no + Subscription: open + + other-sart@lists.debian.org + + Description : Discussions and announcements about SART + Moderated : no + Subscription: open + + +Debian mailing list advertising policy +-------------------------------------- + + This policy is intended to fight mailing-list "spamming". + + The Debian mailing lists accept commercial advertising for payment. The fee + for advertisments is a donation of USD 1000 or more to "Software in the + Public Interest" (SPI). One donation per advertisement, please. If you + prefer to pay in arrears, simply post your advertisement to the list, and + the list operator will bill you USD 1999. The list operator will donate + this amount, minus the expense of collecting it, to SPI. Please note that + the lists are distributed automatically -- messages are generally not read + or checked in any way before they are distributed. + + The act of posting an advertisement indicates your willingness to + * accept responsibility for the fee, + * indemnify the list operator against any legal claims from you or + others in connection with your advertisement, and + * pay any legal and business expenses incurred in collecting late payment. + Our liability to you is limited to a good-faith effort to deliver your + message. + + Reduced rates and/or waiver of fee are available for Debian-related + advertisements. You must consult the list operator in advance of posting for + any reduction or fee waiver. + +-- +Online HTML version of this document is available at + http://www.debian.org/MailingLists/subscribe diff --git a/includes/lenny/common/doc/social-contract.txt b/includes/lenny/common/doc/social-contract.txt new file mode 100644 index 000000000..63591f8f4 --- /dev/null +++ b/includes/lenny/common/doc/social-contract.txt @@ -0,0 +1,118 @@ + Version 1.0 ratified on July 5, 1997. Superseded by Version 1.1, + ratified on April 26, 2004. + + Debian, the producers of the Debian GNU/Linux system, have created the + Debian Social Contract. The Debian Free Software Guidelines (DFSG) part + of the contract, initially designed as a set of commitments that we + agree to abide by, has been adopted by the free software community as + the basis of the Open Source Definition. + __________________________________________________________________ + +"Social Contract" with the Free Software Community + + 1. Debian Will Remain 100% Free Software + We promise to keep the Debian GNU/Linux Distribution entirely free + software. As there are many definitions of free software, we + include the guidelines we use to determine if software is "free" + below. We will support our users who develop and run non-free + software on Debian, but we will never make the system depend on an + item of non-free software. + 2. We Will Give Back to the Free Software Community + When we write new components of the Debian system, we will license + them as free software. We will make the best system we can, so that + free software will be widely distributed and used. We will feed + back bug-fixes, improvements, user requests, etc. to the "upstream" + authors of software included in our system. + 3. We Won't Hide Problems + We will keep our entire bug-report database open for public view at + all times. Reports that users file on-line will immediately become + visible to others. + 4. Our Priorities are Our Users and Free Software + We will be guided by the needs of our users and the free-software + community. We will place their interests first in our priorities. + We will support the needs of our users for operation in many + different kinds of computing environment. We won't object to + commercial software that is intended to run on Debian systems, and + we'll allow others to create value-added distributions containing + both Debian and commercial software, without any fee from us. To + support these goals, we will provide an integrated system of + high-quality, 100% free software, with no legal restrictions that + would prevent these kinds of use. + 5. Programs That Don't Meet Our Free-Software Standards + We acknowledge that some of our users require the use of programs + that don't conform to the Debian Free Software Guidelines. We have + created "contrib" and "non-free" areas in our FTP archive for this + software. The software in these directories is not part of the + Debian system, although it has been configured for use with Debian. + We encourage CD manufacturers to read the licenses of software + packages in these directories and determine if they can distribute + that software on their CDs. Thus, although non-free software isn't + a part of Debian, we support its use, and we provide infrastructure + (such as our bug-tracking system and mailing lists) for non-free + software packages. + __________________________________________________________________ + +The Debian Free Software Guidelines (DFSG) + + 1. Free Redistribution + The license of a Debian component may not restrict any party from + selling or giving away the software as a component of an aggregate + software distribution containing programs from several different + sources. The license may not require a royalty or other fee for + such sale. + 2. Source Code + The program must include source code, and must allow distribution + in source code as well as compiled form. + 3. Derived Works + The license must allow modifications and derived works, and must + allow them to be distributed under the same terms as the license of + the original software. + 4. Integrity of The Author's Source Code + The license may restrict source-code from being distributed in + modified form _only_ if the license allows the distribution of + "patch files" with the source code for the purpose of modifying the + program at build time. The license must explicitly permit + distribution of software built from modified source code. The + license may require derived works to carry a different name or + version number from the original software. (This is a compromise. + The Debian group encourages all authors not to restrict any files, + source or binary, from being modified.) + 5. No Discrimination Against Persons or Groups + The license must not discriminate against any person or group of + persons. + 6. No Discrimination Against Fields of Endeavor + The license must not restrict anyone from making use of the program + in a specific field of endeavor. For example, it may not restrict + the program from being used in a business, or from being used for + genetic research. + 7. Distribution of License + The rights attached to the program must apply to all to whom the + program is redistributed without the need for execution of an + additional license by those parties. + 8. License Must Not Be Specific to Debian + The rights attached to the program must not depend on the program's + being part of a Debian system. If the program is extracted from + Debian and used or distributed without Debian but otherwise within + the terms of the program's license, all parties to whom the program + is redistributed should have the same rights as those that are + granted in conjunction with the Debian system. + 9. License Must Not Contaminate Other Software + The license must not place restrictions on other software that is + distributed along with the licensed software. For example, the + license must not insist that all other programs distributed on the + same medium must be free software. + 10. Example Licenses + The "GPL", "BSD", and "Artistic" licenses are examples of licenses + that we consider "free". + + The concept of stating our "social contract with the free software + community" was suggested by Ean Schuessler. This document was drafted + by Bruce Perens, refined by the other Debian developers during a + month-long e-mail conference in June 1997, and then accepted as the + publicly stated policy of the Debian Project. + + Bruce Perens later removed the Debian-specific references from the + Debian Free Software Guidelines to create "The Open Source Definition". + + Other organizations may derive from and build on this document. Please + give credit to the Debian project if you do. diff --git a/includes/lenny/common/doc/source-unpack.txt b/includes/lenny/common/doc/source-unpack.txt new file mode 100644 index 000000000..151b7337d --- /dev/null +++ b/includes/lenny/common/doc/source-unpack.txt @@ -0,0 +1,33 @@ + HOW TO UNPACK A DEBIAN SOURCE PACKAGE + +There are two kinds of Debian source packages: old ones and new ones. + +A. Old ones look like this: + hello-1.3-4.tar.gz + hello-1.3-4.diff.gz + You unpack them by untarring the .tar.gz. There is NO need to apply + the diff. + +B. New ones look like this: + hello_1.3-11.dsc + hello_1.3-11.diff.gz + hello_1.3-11.orig.tar.gz - note the `.orig' part + Here you MUST use dpkg-source or apply the diff manually - see below. + + If you have `dpkg-source' you should put the files in the same + directory and type `dpkg-source -x .dsc'. + + If you do not you can extract the Debian source as follows: + 1. untar P_V.orig.tar.gz. + 2. rename the resulting P-V.orig directory to P-V. If some other + directory results, rename *it* to P-V. + 3. mkdir P-V/debian. + 4. apply the diff with patch -p0. + 5. do `chmod +x P-V/debian/rules' + (where P is the package name and V the version.) + +C. There are some packages where the Debian source is the upstream + source. In this case there will be no .diff.gz and you can just use + the .tar.gz. If a .dsc is provided you can use `dpkg-source -x'. + + -- Ian Jackson Sat, 31 Aug 1996 diff --git a/includes/lenny/install/README.html b/includes/lenny/install/README.html new file mode 100644 index 000000000..1717250a1 --- /dev/null +++ b/includes/lenny/install/README.html @@ -0,0 +1,253 @@ + + + + + + + Debian GNU/Linux -- The Universal Operating System + + + + + + + + + + + + + + + + + + + + + +
+ + +

+ Introduction +

+ +

An operating system is the set of basic programs and + utilities that make your computer run. At the core of an + operating system is the kernel. The kernel is the most + fundamental program on the computer, which does all the basic + housekeeping and lets you start other programs. Debian is + kernel independent. It currently uses the Linux kernel but work is in + progress to provide Debian for other kernels, using the Hurd. Most + of the basic operating system tools come from the GNU project; hence the name + GNU/Linux.

+ +

Debian is available for various kinds of computers + (“architectures”), like “IBM-compatible” PCs (i386), + Compaq's Alpha, Sun's Sparc, Motorola/IBM's + PowerPC, and (Strong)ARM processors. Check the + ports page for more + information.

+ +

Read more...

+ +

+ About This Disc +

+ +

This disc is labeled + Debian GNU/Linux testing "Lenny" - Official RC i386 BC Binary-1 20081104-23:45 + . + It contains programs ("binaries") for `i386' computers.

+

This disc is a business card image. It contains only the + installer and will download the base system and the remaining packages from + the network.

+

The Release Notes for "lenny" are available on the + Debian web + site.

+ +

+ Installing +

+ +

Because Debian is a complete Operating System, the + installation procedure may seem a bit unusual. You can install + Debian GNU/Linux either alongside your current OS, or as + the only OS on your computer.

+

An Installation Guide for this disc is available from + the + Debian web site.

+

Programs and other files that are needed for the installation can be + found on this disc under + /tools/ + and /install/floppy/ +

+ +

For the impatient ones: you can start the installation program easily by + booting off this disc. Note that not all (esp. older) systems support + this.

+ +

You can also examine the /install/ + directory; you might be able to start the installation system directly + from there.

+ + +

+ Last-Minute Notes +

+ +
    +
  • You should keep in mind that this is an unofficial disc of the Debian + system. This means that all sorts of bugs may be present anywhere in the + system. Please report any bugs you find to the person that gave you this + disc, not Debian.
    • + +
+ +

+ Installing software using Apt +

+ +

After installing or upgrading, Debian's packaging system can + use CDs, DVDs, local collections, or networked servers (FTP, + HTTP) to automatically install software from (.deb + packages). This is done preferably with the ‘apt’ and + ‘aptitude’ programs.

+ +

You can install packages from the commandline using + apt-get. For example, if you want to install the + packages ‘commprog’ and ‘maxgame’, you can give the + command:

+ +

+ apt-get install commprog maxgame +

+ +

Note that you don't have to enter the complete path, or the + ‘.deb’ extension. ‘Apt’ will figure this out + itself.

+ +

Or use aptitude for a full screen interactive selection of + available Debian packages.

+ +

+ CD/DVD Manufacturers +

+ +

You are completely free to manufacture and re-distribute CDs/DVDs of the + Debian GNU/Linux Operating System, like this one. There is no charge from + us (but of course donations are always welcome).

+ +

For all needed information and contact addresses, please + refer to:

+ +

+ http://www.debian.org/CD/ +

+ +

+ More Information +

+ + +

There is much more information present on this disc. Besides + the already mentioned installation and upgrading procedures, + this is the most interesting:

+ + + + +

Also on the Internet are many resources. To name a few:

+ + + + +
+

+ See the Debian contact page + for information on contacting us.

+
+
+ + diff --git a/includes/lenny/install/README.mirrors.html b/includes/lenny/install/README.mirrors.html new file mode 100644 index 000000000..051830587 --- /dev/null +++ b/includes/lenny/install/README.mirrors.html @@ -0,0 +1,2622 @@ + + + + Debian worldwide mirror sites + + + +

Debian worldwide mirror sites

+

Debian is distributed (mirrored) on hundreds of servers on the Internet. +Using a nearby server will probably speed up your download, and also +reduce the load on our central servers and on the Internet as a whole. + +

Debian mirrors can be primary and secondary. The definitions are as follows: + +

+ A primary mirror site has good bandwidth, is available 24 hours a day, + and has an easy to remember name of the form ftp.<country>.debian.org. +
+ They are all automatically updated whenever there are updates to + the Debian archive. + +
+
+ A secondary mirror site may have restrictions on what they mirror (due to + space restrictions). Just because a site is secondary doesn't necessarily + mean it'll be any slower or less up to date than a primary site. + +
+

Use the site closest to you for the fastest downloads possible whether it is + +a primary or secondary site. The program + +netselect can be used to +determine the site with the least latency; use a download program such as + + +wget or + +rsync for determining the site with the most throughput. +Note that geographic proximity often isn't the most important factor for +determining which machine will serve you best. + +

The authoritative copy of the following list can always be found at: + http://www.debian.org/mirror/list.
+If you know of any mirrors that are missing from this list, +please have the site maintainer fill out the form at: + http://www.debian.org/mirror/submit.
+Everything else you want to know about Debian mirrors: + http://www.debian.org/mirror/.
+ +

Primary Debian mirror sites

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CountrySiteArchitectures
Austriaftp.at.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Australiaftp.au.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Belgiumftp.be.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Bulgariaftp.bg.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Brazilftp.br.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Canadaftp.ca.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Switzerlandftp.ch.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Chileftp.cl.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Czech Republicftp.cz.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Germanyftp.de.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Germanyftp2.de.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Denmarkftp.dk.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Estoniaftp.ee.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Spainftp.es.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Finlandftp.fi.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Franceftp.fr.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Franceftp2.fr.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Great Britainftp.uk.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Greeceftp.gr.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Hong Kongftp.hk.debian.org/debian/alpha amd64 arm armel i386 ia64 powerpc sparc
Croatiaftp.hr.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Hungaryftp.hu.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Irelandftp.ie.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Icelandftp.is.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Italyftp.it.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Japanftp.jp.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Japanftp2.jp.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Koreaftp.kr.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Mexicoftp.mx.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Netherlandsftp.nl.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Norwayftp.no.debian.org/debian/amd64 i386 ia64 powerpc sparc
New Zealandftp.nz.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Polandftp.pl.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Portugalftp.pt.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Romaniaftp.ro.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Russiaftp.ru.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Swedenftp.se.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Sloveniaftp.si.debian.org/debian/alpha amd64 i386 ia64 m68k powerpc sparc
Slovakiaftp.sk.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Turkeyftp.tr.debian.org/debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Taiwanftp.tw.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
United Statesftp.us.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
+

Secondary mirrors of the Debian archive

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Host nameFTPHTTPArchitectures
AR Argentina
debian.logiclinux.com/debian/amd64 i386
ftp.ccc.uba.ar/pub/linux/debian/debian//pub/linux/debian/debian/amd64 i386
debian.torredehanoi.org/debian//debian/alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
AT Austria
ftp.at.debian.org
(debian.sil.at)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
gd.tuwien.ac.at/opsys/linux/debian//opsys/linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.mur.at/debian//debian/amd64 i386 ia64
ftp.tu-graz.ac.at/mirror/debian//mirror/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.univie.ac.at/systems/linux/debian/debian//systems/linux/debian/debian/i386
debian.inode.at/debian//debian/alpha amd64 arm armel i386 powerpc sparc
esda.wu-wien.ac.at/pub/debian/amd64 i386 powerpc
debian.lagis.at/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
AU Australia
ftp.au.debian.org
(mirror.linux.org.au)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.aarnet.edu.au/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.monash.edu.au/pub/linux/debian//pub/linux/debian/amd64 i386
ftp.uwa.edu.au/debian//debian/amd64 i386
mirror.eftel.com/debian//debian/amd64 i386
mirror.pacific.net.au/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.iinet.net.au/debian/debian//debian/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.optus.net/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.cse.unsw.edu.au/debian//debian/amd64 i386 ia64 powerpc
mirror.3fl.net.au/pub/debian//debian/amd64 i386
ftp.netspace.net.au/pub/debian//pub/debian/alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
BE Belgium
ftp.be.debian.org
(ftp.belnet.be)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.kulnet.kuleuven.ac.be/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.easynet.be/debian//ftp/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.debian.skynet.be/debian//ftp/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.be.gbxs.net/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
BG Bulgaria
ftp.bg.debian.org
(debian.spnet.net)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.ludost.net/debian//debian/i386
ftp.uni-sofia.bg/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.telecoms.bg/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.mnet.bg/debian//debian/i386
debian.networx-bg.com/debian//debian/amd64 i386
BR Brazil
ftp.br.debian.org
(debian.c3sl.ufpr.br)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.das.ufsc.br/pub/debian/amd64 i386
download.unesp.br/linux/debian/alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
sft.if.usp.br/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
linorg.usp.br/debian//debian/i386
linux.iq.usp.br/debian/amd64 i386
ftp.pucpr.br/debian/amd64 hurd-i386 i386
debian.las.ic.unicamp.br/debian//debian/amd64 i386 powerpc sparc
debian.pop-sc.rnp.br/debian/amd64 i386
BY Belarus
linux.org.by/debian//debian/amd64 i386
ftp.mgts.by/debian//debian/amd64 i386
CA Canada
ftp.ca.debian.org/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.yorku.ca/debian/amd64 i386
ftp3.nrc.ca/debian//debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
gulus.usherbrooke.ca/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.cpsc.ucalgary.ca/mirror/debian.org/debian//mirror/debian.org/debian/amd64 i386
mirror.peer1.net/debian/alpha amd64 arm armel i386 mips mipsel powerpc sparc
debian.mirror.rafal.ca/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.savoirfairelinux.net/debian//debian/amd64 i386 powerpc
debian.mirror.iweb.ca/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.publicns.net/pub/debian//pub/debian/amd64 armel i386
mirror.csclub.uwaterloo.ca/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
CH Switzerland
ftp.ch.debian.org
(debian.ethz.ch)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.switch.ch/mirror/debian//ftp/mirror/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.csg.uzh.ch/debian/amd64 i386
CL Chile
ftp.cl.debian.org
(debian.ciencias.uchile.cl)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.ubiobio.cl/debian/amd64 i386 powerpc
debian.utalca.cl/debian/amd64 i386
mirror.debian.cl/debian/amd64 i386
mirror.debianchile.cl/debian/amd64 i386
CN China
mirrors.geekbone.org/debian//debian/alpha amd64 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.cn99.com/debian//debian/amd64 i386
www.anheng.com.cn/debian//debian/alpha amd64 arm hppa hurd-i386 i386 ia64 mips mipsel powerpc s390 sparc
CZ Czech Republic
ftp.cz.debian.org
(ftp.debian.cz)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.sh.cvut.cz/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.zcu.cz/mirrors/debian//mirrors/debian/amd64 i386
debian.mirror.web4u.cz//amd64 i386
ftp.cvut.cz/debian//debian/amd64 i386 ia64
debian.ignum.cz/debian//debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
DE Germany
ftp.de.debian.org
(debian.inf.tu-dresden.de)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp2.de.debian.org
(ftp.rfc822.org)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.tu-clausthal.de/pub/linux/debian/amd64 arm armel i386 ia64 m68k mips powerpc sparc
debian.uni-duisburg-essen.de/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.freenet.de/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.informatik.rwth-aachen.de/pub/Linux/debian//ftp/pub/Linux/debian/alpha amd64 i386 powerpc sparc
ftp-stud.fht-esslingen.de/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.stw-bonn.de/debian//debian/amd64 i386
ftp.fu-berlin.de/pub/unix/linux/mirrors/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.tu-bs.de/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.uni-koeln.de/debian//debian/alpha amd64 i386 powerpc sparc
ftp.mpi-sb.mpg.de/pub/linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.tiscali.de/pub/debian/debian//pub/debian/debian/amd64 arm armel hurd-i386 i386 ia64
ftp.tu-chemnitz.de/pub/linux/debian/debian//pub/linux/debian/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.uni-kl.de/debian//debian/amd64 i386 ia64 powerpc sparc
ftp.uni-bayreuth.de/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.informatik.hu-berlin.de/pub/Linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp5.gwdg.de/pub/linux/debian/debian//pub/linux/debian/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.hosteurope.de/pub/linux/debian//pub/linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.informatik.uni-frankfurt.de/pub/Mirrors/debian.org/debian//debian/amd64 i386 ia64 powerpc
debian.netcologne.de/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
artfiles.org/debian//debian/amd64 i386
debian.intergenia.de/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.cruisix.net/debian//debian/amd64 i386 powerpc
ftp.rrzn.uni-hannover.de/debian/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.charite.de/debian/i386
ftp.plusline.de/pub/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
sinclair.farm.ftbfs.de/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.halifax.rwth-aachen.de/debian//debian/amd64 i386
DK Denmark
ftp.dk.debian.org
(mirrors.dotsrc.org)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.dkuug.dk/pub/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.here.dk/debian//debian/amd64 i386 ia64 mips powerpc
debian.uni-c.dk/debian/alpha amd64 i386 ia64 powerpc
mirrors.telianet.dk/debian//debian/amd64 i386 powerpc sparc
debianmirror.wwi.dk/debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
EE Estonia
ftp.ee.debian.org
(ftp.aso.ee)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ES Spain
ftp.es.debian.org
(ulises.hostalia.com)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.rediris.es/debian//debian/alpha amd64 i386 ia64 powerpc sparc
ftp.cica.es/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.caliu.cat/debian//debian/amd64 i386 ia64 powerpc
ftp.gva.es/mirror/debian//mirror/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.gul.uc3m.es/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.um.es/mirror/debian/i386
jane.uab.cat/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.udc.es/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.grn.cat/debian//debian/amd64 i386 ia64 powerpc
debian.com.es/debian//debian/alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
FI Finland
ftp.fi.debian.org
(trumpetti.atm.tut.fi)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.funet.fi/pub/linux/mirrors/debian//pub/linux/mirrors/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.jyu.fi/debian//debian/alpha amd64 hurd-i386 i386 powerpc sparc
ftp.seclan.com/debian//debian/amd64 i386 powerpc
FR France
ftp.fr.debian.org
(debian.proxad.net)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp2.fr.debian.org
(ftp.oleane.net)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.iut-bm.univ-fcomte.fr/debian//debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.eudil.fr/debian//debian/alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.proxad.net/mirrors/ftp.debian.org/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.lip6.fr/pub/linux/distributions/debian//pub/linux/distributions/debian/amd64 i386
debian.ens-cachan.fr/debian//ftp/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.u-picardie.fr/mirror/debian//mirror/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.mirrors.easynet.fr/debian//alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.u-strasbg.fr/debian//debian/alpha amd64 hurd-i386 i386 ia64 m68k powerpc sparc
debian.cict.fr/debian//debian/amd64 arm armel hurd-i386 i386
mir1.ovh.net/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mir2.ovh.net/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.nerim.net/debian//debian/i386
ftp.crihan.fr/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.mines.inpl-nancy.fr/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.debian.ikoula.com/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
webb.ens-cachan.fr/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirrors.ircam.fr/pub/debian//pub/debian/alpha amd64 hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc
debian.mirror.inra.fr/debian//debian/amd64 arm armel i386 ia64 powerpc sparc
debian.med.univ-tours.fr/debian//debian/alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.univ-pau.fr/pub/mirrors/debian//linux/mirrors/debian/amd64 i386
ftp.univ-nantes.fr/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirrors.compuscene.org/debian/amd64 i386
debian.revolsys.fr/debian//debian/amd64 i386
debian.univ-reims.fr/debian//debian/amd64 i386
GB Great Britain
ftp.uk.debian.org
(debian.hands.com)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.man.ac.uk/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
www.mirrorservice.org/sites/ftp.debian.org/debian//sites/ftp.debian.org/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.ticklers.org/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.virginmedia.com/mirrors/ftp.debian.org/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.positive-internet.com/debian//debian/amd64 hppa i386 ia64 powerpc sparc
the.earth.li/debian//debian/amd64 hurd-i386 i386
ukdebian.mirror.anlx.net/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.ox.ac.uk/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.zetnet.co.uk/debian//debian/amd64 i386 mipsel
GE Georgia
ftp.ifg.gtu.ge/debian/amd64 i386
GR Greece
ftp.gr.debian.org
(ftp.ntua.gr)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.otenet.gr/pub/linux/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.duth.gr/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.softnet.tuc.gr/pub/linux/debian//ftp/linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.cc.uoc.gr/mirrors/linux/debian//mirrors/linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
HK Hong Kong
ftp.hk.debian.org/debian//debian/alpha amd64 arm armel i386 ia64 powerpc sparc
www.zentek-international.com/mirrors/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
HR Croatia
ftp.hr.debian.org
(debian.carnet.hr)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.irb.hr/debian//debian/alpha amd64 arm armel hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.carnet.hr/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.iskon.hr/debian//debian/amd64 hurd-i386 i386 ia64 s390
HU Hungary
ftp.hu.debian.org
(ftp.fsn.hu)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.kfki.hu/pub/linux/debian//linux/debian/alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.bme.hu/OS/Linux/dist/debian//OS/Linux/dist/debian/amd64 hurd-i386 i386 ia64
debian.mirrors.crysys.hu/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.sth.sze.hu/debian//amd64 i386 ia64
ID Indonesia
kebo.vlsm.org/debian//debian/amd64 hurd-i386 i386 powerpc
debian.indika.net.id/debian/i386
IE Ireland
ftp.ie.debian.org
(debian.heanet.ie)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.esat.net/pub/linux/debian//pub/linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
IL Israel
debian.co.il/debian/i386
mirror.isoc.org.il/pub/debian/amd64 i386
IN India
ftp.iitm.ac.in/debian//debian/amd64 i386
IS Iceland
ftp.is.debian.org
(ftp.rhnet.is)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
IT Italy
ftp.it.debian.org
(ftp.bofh.it)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
giano.com.dist.unige.it/debian//debian/amd64 arm armel i386
ftp.bononia.it/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
freedom.dicea.unifi.it/pub/linux/debian//ftp/pub/linux/debian/amd64 hurd-i386 i386
ftp.eutelia.it/pub/Debian_Mirror/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mi.mirror.garr.it/mirrors/debian//mirrors/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.fastweb.it/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.unina.it/pub/linux/distributions/debian//pub/linux/distributions/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.fastbull.org/debian//debian/amd64 i386 powerpc
debian.dynamica.it/debian//debian/amd64 hurd-i386 i386 ia64 powerpc
mirror.units.it/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
JP Japan
ftp2.jp.debian.org
(ftp.debian.or.jp)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.jp.debian.org
(dennou-q.gfd-dennou.org, dennou-k.gfd-dennou.org, dennou-h.gfd-dennou.org, debian.topstudio.co.jp, www.oyu-net.jp, hanzubon.jp, ftp.nara.wide.ad.jp, ftp2.jp.debian.org)		/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.nara.wide.ad.jp/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ring.asahi-net.or.jp/pub/linux/debian/debian//archives/linux/debian/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.dti.ad.jp/pub/Linux/debian//pub/Linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
dennou-k.gfd-dennou.org/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
dennou-q.gfd-dennou.org/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
sb.itc.u-tokyo.ac.jp/DEBIAN//DEBIAN/amd64 hurd-i386 i386 powerpc
ftp.riken.jp/Linux/debian/debian//Linux/debian/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.shimpinomori.net/debian/amd64 i386 powerpc
www.ring.gr.jp/pub/linux/debian/debian//archives/linux/debian/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.jaist.ac.jp/pub/Linux/Debian//pub/Linux/Debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
www.cohsoft.com/debian/amd64 hurd-i386 i386 powerpc
dennou-h.gfd-dennou.org/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
KR Korea
ftp.kr.debian.org
(ftp.kaist.ac.kr)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.daum.net/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
LT Lithuania
ameba.sc-uni.ktu.lt/debian//debian/amd64 i386
debian.balt.net/debian//debian/amd64 arm armel i386 sparc
LV Latvia
koyanet.lv/debian//debian/amd64 i386
MT Malta
debian.eng.um.edu.mt/debian/amd64 i386
MX Mexico
ftp.mx.debian.org
(debian.unam.mx)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mmc.igeofcu.unam.mx/debian/amd64 hurd-i386 i386 ia64
NC New Caledonia
debian.nautile.nc/debian//debian/amd64 arm i386
NI Nicaragua
debian.uni.edu.ni/debian/amd64 hurd-i386 i386
NL Netherlands
ftp.nl.debian.org
(ftp.snt.utwente.nl)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.nluug.nl/pub/os/Linux/distr/debian//pub/os/Linux/distr/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.surfnet.nl/pub/os/Linux/distr/debian//os/Linux/distr/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.debian.nl/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.tiscali.nl/pub/mirrors/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
NO Norway
ftp.no.debian.org
(ftp.uninett.no)		/debian//debian/amd64 i386 ia64 powerpc sparc
NZ New Zealand
ftp.nz.debian.org
(ftp.citylink.co.nz)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.ihug.co.nz/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
PF French Polynesia
repository.linux.pf/debian//debian/amd64 i386
PL Poland
ftp.pl.debian.org
(ftp.task.gda.pl)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.icm.edu.pl/pub/Linux/debian//pub/Linux/debian/alpha amd64 hurd-i386 i386 sparc
ftp.man.szczecin.pl/pub/Linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.vectranet.pl/debian//debian/amd64 i386
ftp.pwr.wroc.pl/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.man.poznan.pl/pub/linux/debian/debian//pub/linux/debian/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
piotrkosoft.net/pub/mirrors/debian//pub/mirrors/debian/amd64 i386
PT Portugal
ftp.pt.debian.org
(ftp.uevora.pt)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.eq.uc.pt/pub/software/Linux/debian//software/Linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.ua.pt/debian//debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.linux.pt/pub/mirrors/debian//pub/mirrors/debian/amd64 hurd-i386 i386
ftp.telepac.pt/pub/debian/amd64 i386 sparc
mirrors.nfsi.pt/pub/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
neacm.fe.up.pt/pub/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
cesium.di.uminho.pt/pub/debian//pub/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.netvisao.pt/debian//alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.dcc.fc.up.pt/debian/amd64 i386 ia64 powerpc
mirror.sim.ul.pt/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
RO Romania
ftp.ro.debian.org
(ftp.iasi.roedu.net)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.lug.ro/debian//debian/amd64 i386 powerpc
ftp.mikesnet.ro/debian//debian/amd64 i386 mips mipsel
RU Russia
ftp.ru.debian.org
(ftp.chg.ru)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.nsu.ru/debian//debian/amd64 i386
ftp.psn.ru/debian//debian/alpha amd64 hurd-i386 i386
ftp.corbina.net/debian/amd64 i386 ia64
ftp.mipt.ru/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.yandex.ru/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.debian.chuvsu.ru/debian//debian/amd64 i386
SE Sweden
ftp.se.debian.org
(ftp.acc.umu.se)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.sunet.se/pub/Linux/distributions/debian//pub/Linux/distributions/debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.port80.se/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.ds.karen.hj.se/pub/os/linux/debian//pub/os/linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.lth.se/debian//debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.df.lth.se/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
kalle.csb.ki.se/debian/amd64 arm i386
SG Singapore
mirror.nus.edu.sg/pub/Debian//Debian/amd64 i386
SI Slovenia
ftp.si.debian.org
(ftp.camtp.uni-mb.si)		/debian//debian/alpha amd64 i386 ia64 m68k powerpc sparc
ftp.arnes.si/packages/debian//pub/packages/debian/amd64 hurd-i386 i386
debian.prunk.si/debian//debian/amd64 i386
SK Slovakia
ftp.sk.debian.org
(ftp.tuke.sk)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.ynet.sk/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.debian.sk/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.antik.sk/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
SV El Salvador
debian.ues.edu.sv/debian//debian/amd64 i386 ia64
TH Thailand
ftp.coe.psu.ac.th/debian//debian/i386
ftp.thaios.net/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.debianclub.org/debian//debian/amd64 i386
TR Turkey
ftp.tr.debian.org
(debian.ankara.edu.tr)		/debian//debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.linux.org.tr/debian//debian/amd64 i386
godel.cs.bilgi.edu.tr/debian//debian/hurd-i386 i386
debian.eso-es.net/debian/amd64 i386 ia64 sparc
debian.comu.edu.tr/debian//debian/amd64 i386 ia64 powerpc sparc
ftp.metu.edu.tr/debian//debian/ALL alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
TW Taiwan
ftp.tw.debian.org
(debian.linux.org.tw)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.csie.ntu.edu.tw/pub/debian//debian/amd64 hurd-i386 i386
ftp.twaren.net/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
opensource.nchc.org.tw/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.isu.edu.tw/debian//debian/alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.nctu.edu.tw/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.nttu.edu.tw/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.csie.nctu.edu.tw/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.ncnu.edu.tw/Linux/Debian/debian//Linux/Debian/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.cse.yzu.edu.tw/pub/Linux/debian/debian//pub/Linux/debian/debian/alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
UA Ukraine
debian.osdn.org.ua/pub/Debian/debian//debian/i386
debian.org.ua/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.3logic.net/debian/amd64 i386
mirror.mirohost.net/debian//debian/amd64 i386
ftp2.debian.org.ua/debian//debian/amd64 i386
US United States
ftp.us.debian.org
(ftp.egr.msu.edu, mirrors.kernel.org, debian.osuosl.org, debian.lcs.mit.edu)		/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.gtlib.gatech.edu/pub/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.egr.msu.edu/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
distro.ibiblio.org/pub/linux/distributions/debian//debian/amd64 i386 ia64
ftp-mirror.internap.com/pub/debian//pub/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.cerias.purdue.edu/pub/os/debian//pub/os/debian/amd64 hurd-i386 i386 ia64 powerpc sparc
mirror.cs.wisc.edu/pub/mirrors/linux/debian//pub/mirrors/linux/debian/amd64 i386
ftp.uwsg.indiana.edu/linux/debian//linux/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
natasha.stmarytx.edu/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.ndlug.nd.edu/debian//mirrors/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.uchicago.edu/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
carroll.aset.psu.edu/pub/linux/distributions/debian//pub/linux/distributions/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
gladiator.real-time.com/linux/debian/alpha amd64 i386 powerpc sparc
mirrors.kernel.org/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirrors.xmission.com/debian//debian/amd64 hurd-i386 i386 powerpc sparc
ftp.lug.udel.edu/pub/debian//pub/debian/amd64 hurd-i386 i386 powerpc sparc
debian.lcs.mit.edu/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
linux.csua.berkeley.edu/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.silug.org/pub/debian//pub/debian/alpha amd64 arm armel hppa i386 mips mipsel powerpc sparc
debian.secsup.org/pub/linux/debian//alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.osuosl.org/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.anl.gov/pub/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
sluglug.ucsc.edu/debian/amd64 hurd-i386 i386 powerpc sparc
mirrors.geeks.org/debian//debian/amd64 i386
mirrors.usc.edu/pub/linux/distributions/debian//pub/linux/distributions/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.mirrors.pair.com//alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
lug.mtu.edu/debian//debian/alpha amd64 hppa i386 mips mipsel powerpc sparc
debian.mirrors.tds.net/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.cites.uiuc.edu/pub/debian//pub/debian/amd64 hurd-i386 i386 ia64 powerpc sparc
mirrors.tummy.com/debian//debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.mirror.frontiernet.net/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
cudlug.cudenver.edu/debian//debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
bigmirror.crossbowproject.net/pub/debian/alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.cc.columbia.edu/pub/linux/debian/debian//pub/linux/debian/debian/amd64 i386 powerpc
ftp.grokthis.net/mirrors/debian/amd64 i386
mirrors.xenir.com/debian/amd64 arm armel i386 powerpc
debian.mirrors.easynews.com/linux/debian/amd64 i386
debian.ams.sunysb.edu/debian/alpha amd64 arm armel hppa hurd-i386 ia64 m68k mips mipsel powerpc s390 sparc
mirrors.acm.jhu.edu/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.uga.edu/debian//debian/i386
mirror.steadfast.net/debian/amd64 i386
ftp.utexas.edu/pub/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
mirror.fdcservers.net/debian//debian/amd64 i386
mirror.rit.edu/debian//debian/alpha amd64 arm armel i386 powerpc sparc
debian.corenetworks.net/debian/amd64 i386
mirror.its.uidaho.edu/debian//pub/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.cs.binghamton.edu/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
UZ Uzbekistan
debian.snet.uz/debian/amd64 i386
debian.stream.uz/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
VE Venezuela
debian.unesr.edu.ve/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.ula.ve/debian//debian/alpha amd64 i386 ia64 powerpc sparc
ZA South Africa
ftp.sun.ac.za/debian//ftp/debian/amd64 i386
debian.mirror.ac.za/debian//debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.is.co.za/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
+
+ + + +
Last modified: Sun Nov 2 19:52:19 2008Number of sites listed: 417
+ + diff --git a/includes/lenny/install/README.mirrors.txt b/includes/lenny/install/README.mirrors.txt new file mode 100644 index 000000000..eba36b791 --- /dev/null +++ b/includes/lenny/install/README.mirrors.txt @@ -0,0 +1,658 @@ + Debian worldwide mirror sites + ----------------------------- + +Debian is distributed (mirrored) on hundreds of servers on the Internet. +Using a nearby server will probably speed up your download, and also +reduce the load on our central servers and on the Internet as a whole. + +Debian mirrors can be primary and secondary. The definitions are as follows: + + A primary mirror site has good bandwidth, is available 24 hours a day, + and has an easy to remember name of the form ftp..debian.org. + They are all automatically updated whenever there are updates to + the Debian archive. + + A secondary mirror site may have restrictions on what they mirror (due to + space restrictions). Just because a site is secondary doesn't necessarily + mean it'll be any slower or less up to date than a primary site. + +Use the site closest to you for the fastest downloads possible whether it is +a primary or secondary site. The program `netselect' can be used to +determine the site with the least latency; use a download program such as +`wget' or `rsync' for determining the site with the most throughput. +Note that geographic proximity often isn't the most important factor for +determining which machine will serve you best. + +The authoritative copy of the following list can always be found at: + http://www.debian.org/mirror/list +If you know of any mirrors that are missing from this list, +please have the site maintainer fill out the form at: + http://www.debian.org/mirror/submit +Everything else you want to know about Debian mirrors: + http://www.debian.org/mirror/ + + + Primary Debian mirror sites + --------------------------- + + Country Site Debian archive Architectures + --------------------------------------------------------------------------- + Austria ftp.at.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Australia ftp.au.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Belgium ftp.be.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Bulgaria ftp.bg.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Brazil ftp.br.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Canada ftp.ca.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Switzerland ftp.ch.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Chile ftp.cl.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Czech Republic ftp.cz.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Germany ftp.de.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Germany ftp2.de.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Denmark ftp.dk.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Estonia ftp.ee.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Spain ftp.es.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Finland ftp.fi.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + France ftp.fr.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + France ftp2.fr.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Great Britain ftp.uk.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Greece ftp.gr.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Hong Kong ftp.hk.debian.org /debian/ alpha amd64 arm armel i386 ia64 powerpc sparc + Croatia ftp.hr.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Hungary ftp.hu.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Ireland ftp.ie.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Iceland ftp.is.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Italy ftp.it.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Japan ftp.jp.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Japan ftp2.jp.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Korea ftp.kr.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Mexico ftp.mx.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Netherlands ftp.nl.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Norway ftp.no.debian.org /debian/ amd64 i386 ia64 powerpc sparc + New Zealand ftp.nz.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Poland ftp.pl.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Portugal ftp.pt.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Romania ftp.ro.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Russia ftp.ru.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Sweden ftp.se.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Slovenia ftp.si.debian.org /debian/ alpha amd64 i386 ia64 m68k powerpc sparc + Slovakia ftp.sk.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Turkey ftp.tr.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + Taiwan ftp.tw.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + United States ftp.us.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + + + Secondary mirrors of the Debian archive + --------------------------------------- + +HOST NAME FTP HTTP ARCHITECTURES +--------- --- ---- ------------- + +AR Argentina +------------ +debian.logiclinux.com /debian/ amd64 i386 +ftp.ccc.uba.ar /pub/linux/debian/debian/ /pub/linux/debian/debian/ amd64 i386 +debian.torredehanoi.org /debian/ /debian/ alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc + +AT Austria +---------- +ftp.at.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.sil.at) +gd.tuwien.ac.at /opsys/linux/debian/ /opsys/linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.mur.at /debian/ /debian/ amd64 i386 ia64 +ftp.tu-graz.ac.at /mirror/debian/ /mirror/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.univie.ac.at /systems/linux/debian/debian/ /systems/linux/debian/debian/ i386 +debian.inode.at /debian/ /debian/ alpha amd64 arm armel i386 powerpc sparc +esda.wu-wien.ac.at /pub/debian/ amd64 i386 powerpc +debian.lagis.at /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +AU Australia +------------ +ftp.au.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (mirror.linux.org.au) +mirror.aarnet.edu.au /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.monash.edu.au /pub/linux/debian/ /pub/linux/debian/ amd64 i386 +ftp.uwa.edu.au /debian/ /debian/ amd64 i386 +mirror.eftel.com /debian/ /debian/ amd64 i386 +mirror.pacific.net.au /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.iinet.net.au /debian/debian/ /debian/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.optus.net /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.cse.unsw.edu.au /debian/ /debian/ amd64 i386 ia64 powerpc +mirror.3fl.net.au /pub/debian/ /debian/ amd64 i386 +ftp.netspace.net.au /pub/debian/ /pub/debian/ alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc + +BE Belgium +---------- +ftp.be.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.belnet.be) +ftp.kulnet.kuleuven.ac.be /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.easynet.be /debian/ /ftp/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.debian.skynet.be /debian/ /ftp/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.be.gbxs.net /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +BG Bulgaria +----------- +ftp.bg.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.spnet.net) +debian.ludost.net /debian/ /debian/ i386 +ftp.uni-sofia.bg /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.telecoms.bg /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.mnet.bg /debian/ /debian/ i386 +debian.networx-bg.com /debian/ /debian/ amd64 i386 + +BR Brazil +--------- +ftp.br.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.c3sl.ufpr.br) +debian.das.ufsc.br /pub/debian/ amd64 i386 +download.unesp.br /linux/debian/ alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc +sft.if.usp.br /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +linorg.usp.br /debian/ /debian/ i386 +linux.iq.usp.br /debian/ amd64 i386 +ftp.pucpr.br /debian/ amd64 hurd-i386 i386 +debian.las.ic.unicamp.br /debian/ /debian/ amd64 i386 powerpc sparc +debian.pop-sc.rnp.br /debian/ amd64 i386 + +BY Belarus +---------- +linux.org.by /debian/ /debian/ amd64 i386 +ftp.mgts.by /debian/ /debian/ amd64 i386 + +CA Canada +--------- +ftp.ca.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.yorku.ca /debian/ amd64 i386 +ftp3.nrc.ca /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +gulus.usherbrooke.ca /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.cpsc.ucalgary.ca /mirror/debian.org/debian/ /mirror/debian.org/debian/ amd64 i386 +mirror.peer1.net /debian/ alpha amd64 arm armel i386 mips mipsel powerpc sparc +debian.mirror.rafal.ca /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.savoirfairelinux.net /debian/ /debian/ amd64 i386 powerpc +debian.mirror.iweb.ca /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.publicns.net /pub/debian/ /pub/debian/ amd64 armel i386 +mirror.csclub.uwaterloo.ca /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +CH Switzerland +-------------- +ftp.ch.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.ethz.ch) +mirror.switch.ch /mirror/debian/ /ftp/mirror/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.csg.uzh.ch /debian/ amd64 i386 + +CL Chile +-------- +ftp.cl.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.ciencias.uchile.cl) +debian.ubiobio.cl /debian/ amd64 i386 powerpc +debian.utalca.cl /debian/ amd64 i386 +mirror.debian.cl /debian/ amd64 i386 +mirror.debianchile.cl /debian/ amd64 i386 + +CN China +-------- +mirrors.geekbone.org /debian/ /debian/ alpha amd64 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.cn99.com /debian/ /debian/ amd64 i386 +www.anheng.com.cn /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 mips mipsel powerpc s390 sparc + +CZ Czech Republic +----------------- +ftp.cz.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.debian.cz) +debian.sh.cvut.cz /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.zcu.cz /mirrors/debian/ /mirrors/debian/ amd64 i386 +debian.mirror.web4u.cz / / amd64 i386 +ftp.cvut.cz /debian/ /debian/ amd64 i386 ia64 +debian.ignum.cz /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +DE Germany +---------- +ftp.de.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.inf.tu-dresden.de) +ftp2.de.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.rfc822.org) +ftp.tu-clausthal.de /pub/linux/debian/ amd64 arm armel i386 ia64 m68k mips powerpc sparc +debian.uni-duisburg-essen.de /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.freenet.de /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.informatik.rwth-aachen.de /pub/Linux/debian/ /ftp/pub/Linux/debian/ alpha amd64 i386 powerpc sparc +ftp-stud.fht-esslingen.de /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.stw-bonn.de /debian/ /debian/ amd64 i386 +ftp.fu-berlin.de /pub/unix/linux/mirrors/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.tu-bs.de /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.uni-koeln.de /debian/ /debian/ alpha amd64 i386 powerpc sparc +ftp.mpi-sb.mpg.de /pub/linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.tiscali.de /pub/debian/debian/ /pub/debian/debian/ amd64 arm armel hurd-i386 i386 ia64 +ftp.tu-chemnitz.de /pub/linux/debian/debian/ /pub/linux/debian/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.uni-kl.de /debian/ /debian/ amd64 i386 ia64 powerpc sparc +ftp.uni-bayreuth.de /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.informatik.hu-berlin.de /pub/Linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp5.gwdg.de /pub/linux/debian/debian/ /pub/linux/debian/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.hosteurope.de /pub/linux/debian/ /pub/linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.informatik.uni-frankfurt.de /pub/Mirrors/debian.org/debian/ /debian/ amd64 i386 ia64 powerpc +debian.netcologne.de /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +artfiles.org /debian/ /debian/ amd64 i386 +debian.intergenia.de /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.cruisix.net /debian/ /debian/ amd64 i386 powerpc +ftp.rrzn.uni-hannover.de /debian/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.charite.de /debian/ i386 +ftp.plusline.de /pub/debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +sinclair.farm.ftbfs.de /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.halifax.rwth-aachen.de /debian/ /debian/ amd64 i386 + +DK Denmark +---------- +ftp.dk.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (mirrors.dotsrc.org) +ftp.dkuug.dk /pub/debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.here.dk /debian/ /debian/ amd64 i386 ia64 mips powerpc +debian.uni-c.dk /debian/ alpha amd64 i386 ia64 powerpc +mirrors.telianet.dk /debian/ /debian/ amd64 i386 powerpc sparc +debianmirror.wwi.dk /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +EE Estonia +---------- +ftp.ee.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.aso.ee) + +ES Spain +-------- +ftp.es.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ulises.hostalia.com) +ftp.rediris.es /debian/ /debian/ alpha amd64 i386 ia64 powerpc sparc +ftp.cica.es /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.caliu.cat /debian/ /debian/ amd64 i386 ia64 powerpc +ftp.gva.es /mirror/debian/ /mirror/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.gul.uc3m.es /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.um.es /mirror/debian/ i386 +jane.uab.cat /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.udc.es /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.grn.cat /debian/ /debian/ amd64 i386 ia64 powerpc +debian.com.es /debian/ /debian/ alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc + +FI Finland +---------- +ftp.fi.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (trumpetti.atm.tut.fi) +ftp.funet.fi /pub/linux/mirrors/debian/ /pub/linux/mirrors/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.jyu.fi /debian/ /debian/ alpha amd64 hurd-i386 i386 powerpc sparc +ftp.seclan.com /debian/ /debian/ amd64 i386 powerpc + +FR France +--------- +ftp.fr.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.proxad.net) +ftp2.fr.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.oleane.net) +ftp.iut-bm.univ-fcomte.fr /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.eudil.fr /debian/ /debian/ alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.proxad.net /mirrors/ftp.debian.org/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.lip6.fr /pub/linux/distributions/debian//pub/linux/distributions/debian/amd64 i386 +debian.ens-cachan.fr /debian/ /ftp/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.u-picardie.fr /mirror/debian/ /mirror/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.mirrors.easynet.fr /debian/ / alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.u-strasbg.fr /debian/ /debian/ alpha amd64 hurd-i386 i386 ia64 m68k powerpc sparc +debian.cict.fr /debian/ /debian/ amd64 arm armel hurd-i386 i386 +mir1.ovh.net /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mir2.ovh.net /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.nerim.net /debian/ /debian/ i386 +ftp.crihan.fr /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.mines.inpl-nancy.fr /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.debian.ikoula.com /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +webb.ens-cachan.fr /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirrors.ircam.fr /pub/debian/ /pub/debian/ alpha amd64 hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc +debian.mirror.inra.fr /debian/ /debian/ amd64 arm armel i386 ia64 powerpc sparc +debian.med.univ-tours.fr /debian/ /debian/ alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.univ-pau.fr /pub/mirrors/debian/ /linux/mirrors/debian/ amd64 i386 +ftp.univ-nantes.fr /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirrors.compuscene.org /debian/ amd64 i386 +debian.revolsys.fr /debian/ /debian/ amd64 i386 +debian.univ-reims.fr /debian/ /debian/ amd64 i386 + +GB Great Britain +---------------- +ftp.uk.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.hands.com) +debian.man.ac.uk /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +www.mirrorservice.org /sites/ftp.debian.org/debian/ /sites/ftp.debian.org/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.ticklers.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.virginmedia.com /mirrors/ftp.debian.org / alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.positive-internet.com /debian/ /debian/ amd64 hppa i386 ia64 powerpc sparc +the.earth.li /debian/ /debian/ amd64 hurd-i386 i386 +ukdebian.mirror.anlx.net /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.ox.ac.uk /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.zetnet.co.uk /debian/ /debian/ amd64 i386 mipsel + +GE Georgia +---------- +ftp.ifg.gtu.ge /debian/ amd64 i386 + +GR Greece +--------- +ftp.gr.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.ntua.gr) +debian.otenet.gr /pub/linux/debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.duth.gr /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.softnet.tuc.gr /pub/linux/debian/ /ftp/linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.cc.uoc.gr /mirrors/linux/debian/ /mirrors/linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +HK Hong Kong +------------ +ftp.hk.debian.org /debian/ /debian/ alpha amd64 arm armel i386 ia64 powerpc sparc +www.zentek-international.com /mirrors/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +HR Croatia +---------- +ftp.hr.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.carnet.hr) +ftp.irb.hr /debian/ /debian/ alpha amd64 arm armel hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.carnet.hr /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.iskon.hr /debian/ /debian/ amd64 hurd-i386 i386 ia64 s390 + +HU Hungary +---------- +ftp.hu.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.fsn.hu) +ftp.kfki.hu /pub/linux/debian/ /linux/debian/ alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.bme.hu /OS/Linux/dist/debian/ /OS/Linux/dist/debian/ amd64 hurd-i386 i386 ia64 +debian.mirrors.crysys.hu /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.sth.sze.hu /debian/ / amd64 i386 ia64 + +ID Indonesia +------------ +kebo.vlsm.org /debian/ /debian/ amd64 hurd-i386 i386 powerpc +debian.indika.net.id /debian/ i386 + +IE Ireland +---------- +ftp.ie.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.heanet.ie) +ftp.esat.net /pub/linux/debian/ /pub/linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +IL Israel +--------- +debian.co.il /debian/ i386 +mirror.isoc.org.il /pub/debian/ amd64 i386 + +IN India +-------- +ftp.iitm.ac.in /debian/ /debian/ amd64 i386 + +IS Iceland +---------- +ftp.is.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.rhnet.is) + +IT Italy +-------- +ftp.it.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.bofh.it) +giano.com.dist.unige.it /debian/ /debian/ amd64 arm armel i386 +ftp.bononia.it /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +freedom.dicea.unifi.it /pub/linux/debian/ /ftp/pub/linux/debian/ amd64 hurd-i386 i386 +ftp.eutelia.it /pub/Debian_Mirror/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mi.mirror.garr.it /mirrors/debian/ /mirrors/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.fastweb.it /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.unina.it /pub/linux/distributions/debian//pub/linux/distributions/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.fastbull.org /debian/ /debian/ amd64 i386 powerpc +debian.dynamica.it /debian/ /debian/ amd64 hurd-i386 i386 ia64 powerpc +mirror.units.it /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +JP Japan +-------- +ftp2.jp.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.debian.or.jp) +ftp.jp.debian.org /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (dennou-q.gfd-dennou.org, dennou-k.gfd-dennou.org, dennou-h.gfd-dennou.org, debian.topstudio.co.jp, www.oyu-net.jp, hanzubon.jp, ftp.nara.wide.ad.jp, ftp2.jp.debian.org) +ftp.nara.wide.ad.jp /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ring.asahi-net.or.jp /pub/linux/debian/debian/ /archives/linux/debian/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.dti.ad.jp /pub/Linux/debian/ /pub/Linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +dennou-k.gfd-dennou.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +dennou-q.gfd-dennou.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +sb.itc.u-tokyo.ac.jp /DEBIAN/ /DEBIAN/ amd64 hurd-i386 i386 powerpc +ftp.riken.jp /Linux/debian/debian/ /Linux/debian/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.shimpinomori.net /debian/ amd64 i386 powerpc +www.ring.gr.jp /pub/linux/debian/debian/ /archives/linux/debian/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.jaist.ac.jp /pub/Linux/Debian/ /pub/Linux/Debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +www.cohsoft.com /debian/ amd64 hurd-i386 i386 powerpc +dennou-h.gfd-dennou.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +KR Korea +-------- +ftp.kr.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.kaist.ac.kr) +ftp.daum.net /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +LT Lithuania +------------ +ameba.sc-uni.ktu.lt /debian/ /debian/ amd64 i386 +debian.balt.net /debian/ /debian/ amd64 arm armel i386 sparc + +LV Latvia +--------- +koyanet.lv /debian/ /debian/ amd64 i386 + +MT Malta +-------- +debian.eng.um.edu.mt /debian/ amd64 i386 + +MX Mexico +--------- +ftp.mx.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.unam.mx) +mmc.igeofcu.unam.mx /debian/ amd64 hurd-i386 i386 ia64 + +NC New Caledonia +---------------- +debian.nautile.nc /debian/ /debian/ amd64 arm i386 + +NI Nicaragua +------------ +debian.uni.edu.ni /debian/ amd64 hurd-i386 i386 + +NL Netherlands +-------------- +ftp.nl.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.snt.utwente.nl) +ftp.nluug.nl /pub/os/Linux/distr/debian/ /pub/os/Linux/distr/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.surfnet.nl /pub/os/Linux/distr/debian/ /os/Linux/distr/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.debian.nl /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.tiscali.nl /pub/mirrors/debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +NO Norway +--------- +ftp.no.debian.org /debian/ /debian/ amd64 i386 ia64 powerpc sparc + (ftp.uninett.no) + +NZ New Zealand +-------------- +ftp.nz.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.citylink.co.nz) +debian.ihug.co.nz /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +PF French Polynesia +------------------- +repository.linux.pf /debian/ /debian/ amd64 i386 + +PL Poland +--------- +ftp.pl.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.task.gda.pl) +ftp.icm.edu.pl /pub/Linux/debian/ /pub/Linux/debian/ alpha amd64 hurd-i386 i386 sparc +ftp.man.szczecin.pl /pub/Linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.vectranet.pl /debian/ /debian/ amd64 i386 +ftp.pwr.wroc.pl /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.man.poznan.pl /pub/linux/debian/debian/ /pub/linux/debian/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +piotrkosoft.net /pub/mirrors/debian/ /pub/mirrors/debian/ amd64 i386 + +PT Portugal +----------- +ftp.pt.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.uevora.pt) +ftp.eq.uc.pt /pub/software/Linux/debian/ /software/Linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.ua.pt /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.linux.pt /pub/mirrors/debian/ /pub/mirrors/debian/ amd64 hurd-i386 i386 +ftp.telepac.pt /pub/debian/ amd64 i386 sparc +mirrors.nfsi.pt /pub/debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +neacm.fe.up.pt /pub/debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +cesium.di.uminho.pt /pub/debian/ /pub/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.netvisao.pt /debian/ / alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.dcc.fc.up.pt /debian/ amd64 i386 ia64 powerpc +mirror.sim.ul.pt /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +RO Romania +---------- +ftp.ro.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.iasi.roedu.net) +ftp.lug.ro /debian/ /debian/ amd64 i386 powerpc +ftp.mikesnet.ro /debian/ /debian/ amd64 i386 mips mipsel + +RU Russia +--------- +ftp.ru.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.chg.ru) +debian.nsu.ru /debian/ /debian/ amd64 i386 +ftp.psn.ru /debian/ /debian/ alpha amd64 hurd-i386 i386 +ftp.corbina.net /debian/ amd64 i386 ia64 +ftp.mipt.ru /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.yandex.ru /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.debian.chuvsu.ru /debian/ /debian/ amd64 i386 + +SE Sweden +--------- +ftp.se.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.acc.umu.se) +ftp.sunet.se /pub/Linux/distributions/debian//pub/Linux/distributions/debian/alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.port80.se /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.ds.karen.hj.se /pub/os/linux/debian/ /pub/os/linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.lth.se /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.df.lth.se /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +kalle.csb.ki.se /debian/ amd64 arm i386 + +SG Singapore +------------ +mirror.nus.edu.sg /pub/Debian/ /Debian/ amd64 i386 + +SI Slovenia +----------- +ftp.si.debian.org /debian/ /debian/ alpha amd64 i386 ia64 m68k powerpc sparc + (ftp.camtp.uni-mb.si) +ftp.arnes.si /packages/debian/ /pub/packages/debian/ amd64 hurd-i386 i386 +debian.prunk.si /debian/ /debian/ amd64 i386 + +SK Slovakia +----------- +ftp.sk.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.tuke.sk) +mirror.ynet.sk /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.debian.sk /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.antik.sk /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +SV El Salvador +-------------- +debian.ues.edu.sv /debian/ /debian/ amd64 i386 ia64 + +TH Thailand +----------- +ftp.coe.psu.ac.th /debian/ /debian/ i386 +ftp.thaios.net /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.debianclub.org /debian/ /debian/ amd64 i386 + +TR Turkey +--------- +ftp.tr.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.ankara.edu.tr) +ftp.linux.org.tr /debian/ /debian/ amd64 i386 +godel.cs.bilgi.edu.tr /debian/ /debian/ hurd-i386 i386 +debian.eso-es.net /debian/ amd64 i386 ia64 sparc +debian.comu.edu.tr /debian/ /debian/ amd64 i386 ia64 powerpc sparc +ftp.metu.edu.tr /debian/ /debian/ ALL alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +TW Taiwan +--------- +ftp.tw.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (debian.linux.org.tw) +debian.csie.ntu.edu.tw /pub/debian/ /debian/ amd64 hurd-i386 i386 +ftp.twaren.net /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +opensource.nchc.org.tw /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.isu.edu.tw /debian/ /debian/ alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.nctu.edu.tw /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.nttu.edu.tw /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.csie.nctu.edu.tw /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.ncnu.edu.tw /Linux/Debian/debian/ /Linux/Debian/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.cse.yzu.edu.tw /pub/Linux/debian/debian/ /pub/Linux/debian/debian/ alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc + +UA Ukraine +---------- +debian.osdn.org.ua /pub/Debian/debian/ /debian/ i386 +debian.org.ua /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.3logic.net /debian/ amd64 i386 +mirror.mirohost.net /debian/ /debian/ amd64 i386 +ftp2.debian.org.ua /debian/ /debian/ amd64 i386 + +US United States +---------------- +ftp.us.debian.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + (ftp.egr.msu.edu, mirrors.kernel.org, debian.osuosl.org, debian.lcs.mit.edu) +ftp.gtlib.gatech.edu /pub/debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.egr.msu.edu /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +distro.ibiblio.org /pub/linux/distributions/debian//debian/ amd64 i386 ia64 +ftp-mirror.internap.com /pub/debian/ /pub/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.cerias.purdue.edu /pub/os/debian/ /pub/os/debian/ amd64 hurd-i386 i386 ia64 powerpc sparc +mirror.cs.wisc.edu /pub/mirrors/linux/debian/ /pub/mirrors/linux/debian/ amd64 i386 +ftp.uwsg.indiana.edu /linux/debian/ /linux/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +natasha.stmarytx.edu /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.ndlug.nd.edu /debian/ /mirrors/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.uchicago.edu /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +carroll.aset.psu.edu /pub/linux/distributions/debian//pub/linux/distributions/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +gladiator.real-time.com /linux/debian/ alpha amd64 i386 powerpc sparc +mirrors.kernel.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirrors.xmission.com /debian/ /debian/ amd64 hurd-i386 i386 powerpc sparc +ftp.lug.udel.edu /pub/debian/ /pub/debian/ amd64 hurd-i386 i386 powerpc sparc +debian.lcs.mit.edu /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +linux.csua.berkeley.edu /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.silug.org /pub/debian/ /pub/debian/ alpha amd64 arm armel hppa i386 mips mipsel powerpc sparc +debian.secsup.org /pub/linux/debian/ / alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.osuosl.org /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.anl.gov /pub/debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +sluglug.ucsc.edu /debian/ amd64 hurd-i386 i386 powerpc sparc +mirrors.geeks.org /debian/ /debian/ amd64 i386 +mirrors.usc.edu /pub/linux/distributions/debian//pub/linux/distributions/debian/alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.mirrors.pair.com / / alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +lug.mtu.edu /debian/ /debian/ alpha amd64 hppa i386 mips mipsel powerpc sparc +debian.mirrors.tds.net /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.cites.uiuc.edu /pub/debian/ /pub/debian/ amd64 hurd-i386 i386 ia64 powerpc sparc +mirrors.tummy.com /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.mirror.frontiernet.net /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +cudlug.cudenver.edu /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +bigmirror.crossbowproject.net /pub/debian/ alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.cc.columbia.edu /pub/linux/debian/debian/ /pub/linux/debian/debian/ amd64 i386 powerpc +ftp.grokthis.net /mirrors/debian/ amd64 i386 +mirrors.xenir.com /debian/ amd64 arm armel i386 powerpc +debian.mirrors.easynews.com /linux/debian/ amd64 i386 +debian.ams.sunysb.edu /debian/ alpha amd64 arm armel hppa hurd-i386 ia64 m68k mips mipsel powerpc s390 sparc +mirrors.acm.jhu.edu /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.uga.edu /debian/ /debian/ i386 +mirror.steadfast.net /debian/ amd64 i386 +ftp.utexas.edu /pub/debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +mirror.fdcservers.net /debian/ /debian/ amd64 i386 +mirror.rit.edu /debian/ /debian/ alpha amd64 arm armel i386 powerpc sparc +debian.corenetworks.net /debian/ amd64 i386 +mirror.its.uidaho.edu /debian/ /pub/debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +debian.cs.binghamton.edu /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +UZ Uzbekistan +------------- +debian.snet.uz /debian/ amd64 i386 +debian.stream.uz /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +VE Venezuela +------------ +debian.unesr.edu.ve /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.ula.ve /debian/ /debian/ alpha amd64 i386 ia64 powerpc sparc + +ZA South Africa +--------------- +ftp.sun.ac.za /debian/ /ftp/debian/ amd64 i386 +debian.mirror.ac.za /debian/ /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc +ftp.is.co.za /debian/ alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc + +------------------------------------------------------------------------------- +Last modified: Sun Nov 2 19:52:19 2008 Number of sites listed: 417 diff --git a/includes/lenny/install/README.txt b/includes/lenny/install/README.txt new file mode 100644 index 000000000..64ca8c81b --- /dev/null +++ b/includes/lenny/install/README.txt @@ -0,0 +1,143 @@ + + Debian GNU/Linux testing "Lenny" - Official RC i386 BC Binary-1 + 20081104-23:45 + + (HTML version in README.html) + + Welcome to the exciting world of + Debian GNU/Linux + + This disc contains the installer for the Debian GNU/Linux + distribution. Debian is a very extensive collection of software. But + it is more. It is a complete Operating System (OS) for your computer. + And it is free (as in "freedom"). + + CONTENTS: + * Introduction + * About This Disc + * Installing + * Last-Minute Notes + * Installing software using Apt + * CD/DVD Manufacturers + * More Information + * Browse This Disc + +Introduction +============ + + An operating system is the set of basic programs and utilities that + make your computer run. At the core of an operating system is the + kernel. The kernel is the most fundamental program on the computer, + which does all the basic housekeeping and lets you start other + programs. Debian is kernel independent. It currently uses the Linux + kernel but work is in progress to provide Debian for other kernels, + using the Hurd. Most of the basic operating system tools come from the + GNU project; hence the name GNU/Linux. + + Debian is available for various kinds of computers ("architectures"), + like "IBM-compatible" PCs (i386), Compaq's Alpha, Sun's Sparc, + Motorola/IBM's PowerPC, and (Strong)ARM processors. Check the ports + page for more information. + + Read more at: + + http://www.debian.org/intro/about + +About This Disc +=============== + + This disc is labeled + + Debian GNU/Linux testing "Lenny" - Official RC i386 BC Binary-1 + 20081104-23:45 + + It contains programs ("binaries") for `i386' computers. + + This disc is a business card image. It contains only the installer and + will download the base system and the remaining packages from the + network. + + The Release Notes for "lenny" are available on the Debian web site. + +Installing +========== + + Because Debian is a complete Operating System, the installation + procedure may seem a bit unusual. You can install Debian GNU/Linux + either alongside your current OS, or as the only OS on your computer. + + An Installation Guide for this disc is available from the Debian web + site. + + Programs and other files that are needed for the installation can be + found on this disc under /tools/ and /install/floppy/ + + For the impatient ones: you can start the installation program easily + by booting off this disc. Note that not all (esp. older) systems + support this. + + You can also examine the /install/ directory; you might be able to + start the installation system directly from there. + +Last-Minute Notes +================= + + * You should keep in mind that this is an unofficial disc of the + Debian system. This means that all sorts of bugs may be present + anywhere in the system. Please report any bugs you find to the + person that gave you this disc, not Debian. + +Installing software using Apt +============================= + + After installing or upgrading, Debian's packaging system can use CDs, + DVDs, local collections, or networked servers (FTP, HTTP) to + automatically install software from (.deb packages). This is done + preferably with the `apt' and `aptitude' programs. + + You can install packages from the commandline using apt-get. For + example, if you want to install the packages `commprog' and `maxgame', + you can give the command: + + apt-get install commprog maxgame + + Note that you don't have to enter the complete path, or the `.deb' + extension. `Apt' will figure this out itself. + + Or use aptitude for a full screen interactive selection of available + Debian packages. + +CD/DVD Manufacturers +==================== + + You are completely free to manufacture and re-distribute CDs/DVDs of + the Debian GNU/Linux Operating System, like this one. There is no + charge from us (but of course donations are always welcome). + + For all needed information and contact addresses, please refer to: + + http://www.debian.org/CD/ + +More Information +================ + + There is much more information present on this disc. Besides the + already mentioned installation and upgrading procedures, this is the + most interesting: + * /doc/FAQ Debian FAQ + * /doc/constitution.txt The Debian Constitution + * /doc/debian-manifesto The Debian Manifesto + * /doc/social-contract.txt Debian's Social Contract + * /doc/bug-reporting.txt Bug reporting instructions + + Also on the Internet are many resources. To name a few: + * http://www.debian.org/ The Debian homepage + * http://www.debian.org/doc/ Debian Documentation + * http://www.debian.org/support/ Debian User Support + * http://www.tldp.org/ The Linux Documentation Project + * http://www.linux.org/ General Linux homepage + + + + See the Debian contact page (http://www.debian.org/contact) for + information on contacting us. diff --git a/includes/lenny/install/autorun.inf b/includes/lenny/install/autorun.inf new file mode 100644 index 000000000..70f471d8f --- /dev/null +++ b/includes/lenny/install/autorun.inf @@ -0,0 +1,2 @@ +[autorun] +open=setup.exe diff --git a/includes/lenny/install/css/debinstall-print.css b/includes/lenny/install/css/debinstall-print.css new file mode 100644 index 000000000..6e141d258 --- /dev/null +++ b/includes/lenny/install/css/debinstall-print.css @@ -0,0 +1,69 @@ +/* + +Debian Installation Medium print media CSS +to be used in conjuction the all media CSS file +Created by: Kalle Söderman + +*/ + +body { + margin: 0 1em 0 70px; + font: normal 10pt sans-serif; + color:black; + background-image:none; +} +.alt { + display:none; + } +.section { + display:none; + } +#logo { + z-index: 0; + } +h1 { + z-index:100; + } +em { + color: #666; + } +code { + background-color: transparent; + border:0; + } +tt a { + font-family: monospace; + background-color: transparent; + border:0; + } +.toc li { + border-bottom: 0.5pt dotted black; + } +#outer ul { + line-height:1.2em; + } +#intro { + border-bottom: 1pt solid black + } +#breadcrumbs { + font-weight:bold; + border-bottom: 1pt solid black; + } +#fineprint, #breadcrumbs { + background: transparent; + } +#fineprint { + color:black; + border-top:1px solid black; + } +#fineprint p { + line-height:1.5em; + } +p a:link { + background-image: url('../pics/dot_bw.gif'); + background-repeat:repeat-x; + background-position:bottom left; + } +a:link, a:visited, a:link:visited { + color:black; + } \ No newline at end of file diff --git a/includes/lenny/install/css/debinstall.css b/includes/lenny/install/css/debinstall.css new file mode 100644 index 000000000..cdbeb2b15 --- /dev/null +++ b/includes/lenny/install/css/debinstall.css @@ -0,0 +1,294 @@ +/* + +Debian Installation Medium CSS +Created by: Kalle Söderman + +*/ + + + + +html { + height:100%; + } +body { + margin: 0px 10px 0 70px; + font: normal 16px sans-serif; + background-color: white; + background-image:url('../pics/gradient.png'); + background-position: top left; + background-repeat: repeat-x; + color:black; +} + +/* --------------- Main Divs --------------- */ + +#header { + margin:0; + padding:0; +} +#upperheader { + margin:0; + padding:0; +} +#logo { + position:absolute; + top:0; + left:0; +} +#intro { + border-bottom:1px solid #c70036; +} +#mirrors #intro { + margin:0; + padding:0; +} +#intro #splash { + margin-top:70px; + margin-bottom: 0px; + text-align:center; +} +#debian-img { + margin-top:10px; + clear:both; + display:block; +} + +#intro p,.intro { + margin-bottom: 0.75em; + padding:0; + line-height:1.2em; + text-align: left; + font-size:118%; +} +.alt { + float:right; +} +.toc { + font-size: 0.73em; + list-style:none; + margin: 0 0 1em 0; + line-height:1.5em; +} +#mirrors .toc { + border-top: 1px solid #d3d6df; +} +.toc li { + border-bottom: 1px solid #d3d6df; + padding:3px 3px 3px 3px; +} +#maincol { + clear:both; +} +.clr { + border-top:1px solid black; +} +#footer { + margin:0; + + clear:both; +} + +#maincol ul, #mailheader { + text-indent:0; + list-style-position:outside; + margin:0.5em 0 1em 0; + padding:0; +} +ul { + list-style-position:outside; + margin:0.5em 0 1em 0; + + padding:0; +} +ul ul, ul ul ul, ul ul ul ul { + padding-left:1em; +} + +#breadcrumbs { + font-size:0.68em; + margin:0 0 0 0; + padding:0.25em; + background-color: #f2f3f7; + border-bottom: 1px solid #e2e3e7; + text-transform:lowercase; +} +.hidecss { + display:none; +} +#fineprint { + font-size:0.68em; + color: #333; + margin:2em 0 0 0; + padding:0.25em; + background-color: #f2f3f7; + border-top: 1px solid #e2e3e7; + text-transform:lowercase; +} +#fineprint p { + margin:0; + line-height:1em; +} +.nonvisual { + display:none; +} +.clear {clear:both} +#clear { + clear:both; +} + +/* --------------- Images --------------- */ + +img {border:0;} + + + +/* --------------- Typography --------------- */ +#intro h1 { + margin:0; + line-height:0.8em; +} +dd { + margin: 0 0 1em 1em; +} +.section { + font-family:monospace; + font-size: 0.9em; + position:absolute; + top: 0px; + left:70px; + text-transform: uppercase; + letter-spacing: 0.08em; + background-color: #c70036; + line-height: 20px; + color:white; + padding: 0 5px 0 5px; + margin:0; +} +.section em { + font-style:normal; + color:white; +} +strong { + font-weight:bold; +} + +p { + margin: 0.1em 0 0.4em 0; + line-height:1.5em; +} +em { + color: #666; +} + +h1, h2, h3, h4, h5, h6 { + font-weight: normal; +} +h1 { + font-size: 218%; margin:0.5em 0 0.5em 0; +} +h2 { + font-size: 164%; margin: 1em 0 0.25em 0; +} +h3 { + font-size: 145%; +} +h4 { + font-size: 118%; +} +blockquote { + margin: 0; +} +hr { + background-color:#cdcdcd; + height:1px; + border:0; + display:none; +} +pre { + font-family: monospace; + font-size: 0.73em; + line-height:1.5em; +} + +th { + text-align:left; +} +blockquote { + margin-left: 1em; + font-size:0.73em; +} +code { + background-color: #f2f3f7; + border: 1px solid #e2e3e7; + padding: 0 0.25em 0 0.25em; + text-decoration:none; +} + +tt a { + background-color: #fffede; + border: 1px solid #eae9cb; + padding: 0 0.25em 0 0.25em; + text-decoration:none; +} +tt a:hover { + background-color:transparent; + border-color:transparent; +} + +dt { + font-weight:bold; + margin:0; +} +dd { + margin-left:1em; +} +#mirrors h1 { + margin-top:70px; + padding: 0.25em 0 0 0; + border-top: 1px solid #c70036; +} +#mirrors pre { + font-size:0.75em; +} +#mirrors td, #mirrors th { + font-size:0.73em; + padding-right:1em; +} +#mirrors code { + background:transparent; + border:none; +} +/*--------------- Small Type Group -------------*/ + +.small, #footer,#news, #security,.planet #sidebar, .planet .date, .wikitoc, .wiki #sidebar, .wiki #pageinfo.info, .wiki #spotlight { + font-size:0.73em; +} + + + +/* --------------------- Links ---------------------- */ + +a:link { + color: #0035c7; + text-decoration:none; +} + +a:link:hover { + text-decoration: underline; + color: #2e00c7; +} +a:visited { + text-decoration:none; + color: #0035c7; +} +a:visited:hover { + text-decoration:underline; +} +a:link:active { + color: #c70036; + background-color:transparent; +} + + + diff --git a/includes/lenny/install/pics/blue-lowerleft.png b/includes/lenny/install/pics/blue-lowerleft.png new file mode 100644 index 000000000..2a2245e45 Binary files /dev/null and b/includes/lenny/install/pics/blue-lowerleft.png differ diff --git a/includes/lenny/install/pics/blue-lowerright.png b/includes/lenny/install/pics/blue-lowerright.png new file mode 100644 index 000000000..7e6627145 Binary files /dev/null and b/includes/lenny/install/pics/blue-lowerright.png differ diff --git a/includes/lenny/install/pics/blue-upperleft.png b/includes/lenny/install/pics/blue-upperleft.png new file mode 100644 index 000000000..a58d0ecb1 Binary files /dev/null and b/includes/lenny/install/pics/blue-upperleft.png differ diff --git a/includes/lenny/install/pics/blue-upperright.png b/includes/lenny/install/pics/blue-upperright.png new file mode 100644 index 000000000..2f368493a Binary files /dev/null and b/includes/lenny/install/pics/blue-upperright.png differ diff --git a/includes/lenny/install/pics/debian-61.png b/includes/lenny/install/pics/debian-61.png new file mode 100644 index 000000000..1aca3e663 Binary files /dev/null and b/includes/lenny/install/pics/debian-61.png differ diff --git a/includes/lenny/install/pics/debian.jpg b/includes/lenny/install/pics/debian.jpg new file mode 100644 index 000000000..db62d7a03 Binary files /dev/null and b/includes/lenny/install/pics/debian.jpg differ diff --git a/includes/lenny/install/pics/dot_bw.gif b/includes/lenny/install/pics/dot_bw.gif new file mode 100644 index 000000000..87a807675 Binary files /dev/null and b/includes/lenny/install/pics/dot_bw.gif differ diff --git a/includes/lenny/install/pics/gradient.png b/includes/lenny/install/pics/gradient.png new file mode 100644 index 000000000..33009daf8 Binary files /dev/null and b/includes/lenny/install/pics/gradient.png differ diff --git a/includes/lenny/install/pics/logo-50.jpg b/includes/lenny/install/pics/logo-50.jpg new file mode 100644 index 000000000..542f0a498 Binary files /dev/null and b/includes/lenny/install/pics/logo-50.jpg differ diff --git a/includes/lenny/install/pics/openlogo-nd-50.png b/includes/lenny/install/pics/openlogo-nd-50.png new file mode 100644 index 000000000..3d7e47199 Binary files /dev/null and b/includes/lenny/install/pics/openlogo-nd-50.png differ diff --git a/includes/lenny/install/pics/red-lowerleft.png b/includes/lenny/install/pics/red-lowerleft.png new file mode 100644 index 000000000..caca9c543 Binary files /dev/null and b/includes/lenny/install/pics/red-lowerleft.png differ diff --git a/includes/lenny/install/pics/red-lowerright.png b/includes/lenny/install/pics/red-lowerright.png new file mode 100644 index 000000000..c27056c59 Binary files /dev/null and b/includes/lenny/install/pics/red-lowerright.png differ diff --git a/includes/lenny/install/pics/red-upperleft.png b/includes/lenny/install/pics/red-upperleft.png new file mode 100644 index 000000000..c1e3301cc Binary files /dev/null and b/includes/lenny/install/pics/red-upperleft.png differ diff --git a/includes/lenny/install/pics/red-upperright.png b/includes/lenny/install/pics/red-upperright.png new file mode 100644 index 000000000..54d17cafd Binary files /dev/null and b/includes/lenny/install/pics/red-upperright.png differ diff --git a/includes/lenny/install/tools/README b/includes/lenny/install/tools/README new file mode 100644 index 000000000..bc56f934f --- /dev/null +++ b/includes/lenny/install/tools/README @@ -0,0 +1,13 @@ +/debian/tools contains MS-DOS tools for installing and booting Linux. + +fips20.zip Non-destructively split harddisk partitions (works with FAT32) +gzip124.exe gzip for DOS +lodlin16.zip load Linux kernel from DOS +rawrite1.zip rawrite version 1.3 (rawrite 2.0 is much faster, but +rawrite2.zip rawrite version 2.0 it locks up on some machines.) +unz512x3.exe Info-ZIP's free UnZipper for DOS +rwwrtwin.zip Win32 version of rawrite runs on Windows 95, NT, 98, 2000, + ME, XP and probably later versions. +diskio.zip Under 95, 98 & ME you need diskio.dll. It must be in + the same directory as rwwrtwin.exe. (uncompressed) +md5sum-w32.zip Win32 version of md5sum diff --git a/includes/lenny/install/tools/diskio.zip b/includes/lenny/install/tools/diskio.zip new file mode 100644 index 000000000..b30fa96c3 Binary files /dev/null and b/includes/lenny/install/tools/diskio.zip differ diff --git a/includes/lenny/install/tools/fips20.zip b/includes/lenny/install/tools/fips20.zip new file mode 100644 index 000000000..c4a64b6d8 Binary files /dev/null and b/includes/lenny/install/tools/fips20.zip differ diff --git a/includes/lenny/install/tools/gzip124.exe b/includes/lenny/install/tools/gzip124.exe new file mode 100644 index 000000000..1a8d1373e Binary files /dev/null and b/includes/lenny/install/tools/gzip124.exe differ diff --git a/includes/lenny/install/tools/lodlin16.zip b/includes/lenny/install/tools/lodlin16.zip new file mode 100644 index 000000000..b86310a1f Binary files /dev/null and b/includes/lenny/install/tools/lodlin16.zip differ diff --git a/includes/lenny/install/tools/md5sum-w32.zip b/includes/lenny/install/tools/md5sum-w32.zip new file mode 100644 index 000000000..982202bb7 Binary files /dev/null and b/includes/lenny/install/tools/md5sum-w32.zip differ diff --git a/includes/lenny/install/tools/rawrite1.zip b/includes/lenny/install/tools/rawrite1.zip new file mode 100644 index 000000000..abdc229a8 Binary files /dev/null and b/includes/lenny/install/tools/rawrite1.zip differ diff --git a/includes/lenny/install/tools/rawrite2.zip b/includes/lenny/install/tools/rawrite2.zip new file mode 100644 index 000000000..aa3388504 Binary files /dev/null and b/includes/lenny/install/tools/rawrite2.zip differ diff --git a/includes/lenny/install/tools/rwwrtwin.zip b/includes/lenny/install/tools/rwwrtwin.zip new file mode 100644 index 000000000..2c3fd1156 Binary files /dev/null and b/includes/lenny/install/tools/rwwrtwin.zip differ diff --git a/includes/lenny/install/tools/src/md5sum-w32_1.1.dsc b/includes/lenny/install/tools/src/md5sum-w32_1.1.dsc new file mode 100644 index 000000000..44393f8bd --- /dev/null +++ b/includes/lenny/install/tools/src/md5sum-w32_1.1.dsc @@ -0,0 +1,25 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA1 + +Format: 1.0 +Source: md5sum-w32 +Version: 1.1 +Binary: md5sum-w32 +Maintainer: Bas Zoetekouw +Architecture: any +Standards-Version: 3.5.2 +Build-Depends: debhelper (>> 3.0.0), mingw32, zip +Files: + b5741a5c7e027ee1e9242163c5eb711b 7617 md5sum-w32_1.1.tar.gz + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.0.7 (GNU/Linux) + +iQEXAwUBPXo9/Z6S+2TcVAFTFAKpcwP/bDWljR/VQxCFtjg4epqZczN5MRWHQ0Qc +qjRw5F0of0V0jELCVClRGl68VBX96o3tJSGvhCkXqT3UXQYd1vsiakHQotcEib3V +r07De88Bzxm9NE43AR/98TU+9niIkrOmkbxGJQXU3puKMXd/WpCw4XgNOYT6A1hg +7ugByZ32x9ID/RtIpCehPvrqCVn8J1v2dTam3m3obGt6yESg+2PcxzEeIVwN3jb3 +AwkLTKi7VyelSmMWPdJUxsMZvGmBFyjjNqwZeMYPnuGS60sHxREHA/heDsM1hIbS +7PZ9hcPXw588Y79ItGFZY4Rfdc0cJQSTkPvt2z5gAk1Eeii5kzCC25nZ +=aPY9 +-----END PGP SIGNATURE----- diff --git a/includes/lenny/install/tools/src/md5sum-w32_1.1.tar.gz b/includes/lenny/install/tools/src/md5sum-w32_1.1.tar.gz new file mode 100644 index 000000000..bf42ec880 Binary files /dev/null and b/includes/lenny/install/tools/src/md5sum-w32_1.1.tar.gz differ diff --git a/includes/lenny/install/tools/unz512x3.exe b/includes/lenny/install/tools/unz512x3.exe new file mode 100644 index 000000000..e8b36c833 Binary files /dev/null and b/includes/lenny/install/tools/unz512x3.exe differ -- cgit v1.2.3