diff options
| author | Daniel Baumann <daniel@debian.org> | 2008-12-20 11:18:45 +0100 |
|---|---|---|
| committer | Daniel Baumann <daniel@debian.org> | 2011-03-09 19:05:40 +0100 |
| commit | 1ec7ddaa62e53173b4e1d2982f2bc0a3c8993fa7 (patch) | |
| tree | 0c7974e616b2637fc0d30efa0ac2dd3f0a4ee842 /includes | |
| parent | d391837f66a5722d17d49e785cd9528b1696e92c (diff) | |
| download | live-build-1ec7ddaa62e53173b4e1d2982f2bc0a3c8993fa7.zip live-build-1ec7ddaa62e53173b4e1d2982f2bc0a3c8993fa7.tar.gz | |
Updating cd includes.
Diffstat (limited to 'includes')
193 files changed, 34733 insertions, 10434 deletions
diff --git a/includes/etch b/includes/etch deleted file mode 120000 index 9a63c96..0000000 --- a/includes/etch +++ /dev/null @@ -1 +0,0 @@ -sid
\ No newline at end of file diff --git a/includes/sid/common/doc/00-INDEX b/includes/etch/common/doc/00-INDEX index 041eaca..041eaca 100644 --- a/includes/sid/common/doc/00-INDEX +++ b/includes/etch/common/doc/00-INDEX diff --git a/includes/etch/common/doc/FAQ/debian-faq.en.html.tar.gz b/includes/etch/common/doc/FAQ/debian-faq.en.html.tar.gz Binary files differnew file mode 100644 index 0000000..abee0f9 --- /dev/null +++ b/includes/etch/common/doc/FAQ/debian-faq.en.html.tar.gz diff --git a/includes/etch/common/doc/FAQ/debian-faq.en.pdf.gz b/includes/etch/common/doc/FAQ/debian-faq.en.pdf.gz Binary files differnew file mode 100644 index 0000000..3b428a1 --- /dev/null +++ b/includes/etch/common/doc/FAQ/debian-faq.en.pdf.gz diff --git a/includes/etch/common/doc/FAQ/debian-faq.en.ps.gz b/includes/etch/common/doc/FAQ/debian-faq.en.ps.gz Binary files differnew file mode 100644 index 0000000..0ff0949 --- /dev/null +++ b/includes/etch/common/doc/FAQ/debian-faq.en.ps.gz diff --git a/includes/etch/common/doc/FAQ/debian-faq.en.txt.gz b/includes/etch/common/doc/FAQ/debian-faq.en.txt.gz Binary files differnew file mode 100644 index 0000000..aeaaa41 --- /dev/null +++ b/includes/etch/common/doc/FAQ/debian-faq.en.txt.gz diff --git a/includes/etch/common/doc/FAQ/html/ch-basic_defs.en.html b/includes/etch/common/doc/FAQ/html/ch-basic_defs.en.html new file mode 100644 index 0000000..cc55653 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-basic_defs.en.html @@ -0,0 +1,610 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Definitions and overview</title> + +<link href="index.en.html" rel="start"> +<link href="index.en.html" rel="prev"> +<link href="ch-getting.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-basic_defs"></a></p> +<hr> + +<p> +[ <a href="index.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ 1 ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-getting.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 1 - Definitions and overview +</h1> + +<hr> + +<h2><a name="s-whatisfaq"></a>1.1 What is this FAQ?</h2> + +<p> +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. +</p> + +<p> +If you can't find what you're looking for in this FAQ, be sure to check out <a +href="ch-support.en.html#s-debiandocs">What other documentation exists on and +for a Debian system?, Section 12.1</a>. If even that doesn't help, refer to <a +href="ch-faqinfo.en.html#s-feedback">Feedback, Section 16.2</a>. +</p> + +<hr> + +<h2><a name="s-whatisdebian"></a>1.2 What is Debian GNU/Linux?</h2> + +<p> +Debian GNU/Linux is a particular <em>distribution</em> of the Linux operating +system, and numerous packages that run on it. +</p> + +<p> +Debian GNU/Linux is: +</p> +<ul> +<li> +<p> +<strong>full featured</strong>: Debian includes more than 18200 software +packages at present. Users can select which packages to install; Debian +provides a tool for this purpose. You can find a list and descriptions of the +packages currently available in Debian at any of the Debian <code><a +href="http://www.debian.org/distrib/ftplist">mirror sites</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>free to use and redistribute</strong>: There is no consortium +membership or payment required to participate in its distribution and +development. All packages that are formally part of Debian GNU/Linux are free +to redistribute, usually under terms specified by the GNU General Public +License. +</p> + +<p> +The Debian FTP archives also carry approximately 560 software packages (in the +<samp>non-free</samp> and <samp>contrib</samp> sections), which are +distributable under specific terms included with each package. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>dynamic</strong>: With about 1060 volunteers constantly contributing +new and improved code, Debian is evolving rapidly. The FTP archives are +updated twice every day. +</p> +</li> +</ul> + +<p> +Most Linux users run a specific <em>distribution</em> 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. +</p> + +<p> +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. +</p> + +<p> +For Debian, free has the GNUish meaning (see the <code><a +href="http://www.debian.org/social_contract#guidelines">Debian Free Software +Guidelines</a></code>). 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. +</p> + +<p> +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. +</p> + +<p> +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 <a +href="ch-redistrib.en.html#s-childistro">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</a> for more information. +</p> + +<hr> + +<h2><a name="s-linux"></a>1.3 OK, now I know what Debian is... what is Linux?!</h2> + +<p> +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. +</p> + +<p> +Besides its kernel, a "Linux" system usually has: +</p> +<ul> +<li> +<p> +a file system that follows the Linux Filesystem Hierarchy Standard <code><a +href="http://www.pathname.com/fhs/">http://www.pathname.com/fhs/</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +a wide range of Unix utilities, many of which have been developed by the GNU +project and the Free Software Foundation. +</p> +</li> +</ul> + +<p> +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 <a href="ch-compat.en.html#s-otherunices">How +source code compatible is Debian with other Unix systems?, Section 4.3</a>. +</p> + +<p> +For more information about Linux, see <code><a +href="http://www.linux.org/info/">What is Linux</a></code> by <code><a +href="http://www.linux.org/">Linux Online</a></code>. +</p> + +<hr> + +<h2><a name="s-non-linux"></a>1.4 Does Debian just do GNU/Linux?</h2> + +<p> +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. +</p> + +<p> +The oldest porting effort is Debian GNU/Hurd. +</p> + +<p> +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. +</p> + +<p> +Please see <code><a +href="http://www.gnu.org/software/hurd/">http://www.gnu.org/software/hurd/</a></code> +for more information about the GNU/Hurd in general, and <code><a +href="http://www.debian.org/ports/hurd/">http://www.debian.org/ports/hurd/</a></code> +for more information about Debian GNU/Hurd. +</p> + +<p> +A second effort is the port to a BSD kernel. People are working with both the +NetBSD and the FreeBSD kernels. +</p> + +<p> +See <code><a +href="http://www.debian.org/ports/#nonlinux">http://www.debian.org/ports/#nonlinux</a></code> +for more information about these non-linux ports. +</p> + +<hr> + +<h2><a name="s-difference"></a>1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?</h2> + +<p> +These key features distinguish Debian from other Linux distributions: +</p> +<dl> +<dt>Freedom:</dt> +<dd> +<p> +As stated in the <code><a href="http://www.debian.org/social_contract">Debian +Social Contract</a></code>, 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 <code><a +href="http://www.debian.org/social_contract#guidelines">The Debian Free +Software</a></code>. +</p> +</dd> +</dl> +<dl> +<dt>The Debian package maintenance system:</dt> +<dd> +<p> +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 <a +href="ch-pkg_basics.en.html">Basics of the Debian package management system, +Chapter 7</a>). +</p> +</dd> +</dl> +<dl> +<dt>Open development:</dt> +<dd> +<p> +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. +</p> + +<p> +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 <a +href="ch-contributing.en.html#s-contrib">How can I become a Debian software +developer?, Section 13.1</a>. +</p> +</dd> +</dl> +<dl> +<dt>The Universal Operating System:</dt> +<dd> +<p> +Debian comes with <code><a href="http://packages.debian.org/stable/">more than +18200 packages</a></code> and runs on <code><a +href="http://www.debian.org/ports/">11 architectures</a></code>. This is far +more than is available for any other GNU/Linux distribution. See <a +href="ch-software.en.html#s-apps">What types of applications and development +software are available for Debian GNU/Linux?, Section 5.1</a> for an overview +of the provided software and see <a href="ch-compat.en.html#s-arches">On what +hardware architectures/systems does Debian GNU/Linux run?, Section 4.1</a> for +a description of the supported hardware platforms. +</p> +</dd> +</dl> +<dl> +<dt>The Bug Tracking System:</dt> +<dd> +<p> +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 <a +href="ch-support.en.html#s-buglogs">Are there logs of known bugs?, Section +12.4</a>. +</p> +</dd> +</dl> +<dl> +<dt>The Debian Policy:</dt> +<dd> +<p> +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. +</p> +</dd> +</dl> + +<p> +For additional information about this, please see our web page about <code><a +href="http://www.debian.org/intro/why_debian">reasons to choose +Debian</a></code>. +</p> + +<hr> + +<h2><a name="s-gnu"></a>1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?</h2> + +<p> +The Debian system builds on the ideals of free software first championed by the +<code><a href="http://www.gnu.org/">Free Software Foundation</a></code> and in +particular by <code><a href="http://www.stallman.org/">Richard +Stallman</a></code>. FSF's powerful system development tools, utilities, and +applications are also a key part of the Debian system. +</p> + +<p> +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. +</p> + +<p> +The FSF's long-standing objective is to develop a new operating system called +GNU, based on <code><a +href="http://www.gnu.org/software/hurd/">Hurd</a></code>. Debian is working +with FSF on this system, called <code><a +href="http://www.debian.org/ports/hurd/">Debian GNU/Hurd</a></code>. +</p> + +<hr> + +<h2><a name="s-pronunciation"></a>1.7 How does one pronounce Debian and what does this word mean?</h2> + +<p> +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.) +</p> + +<hr> + +<p> +[ <a href="index.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ 1 ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-getting.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-basic_defs.html b/includes/etch/common/doc/FAQ/html/ch-basic_defs.html index 6bee626..6bee626 120000 --- a/includes/sid/common/doc/FAQ/html/ch-basic_defs.html +++ b/includes/etch/common/doc/FAQ/html/ch-basic_defs.html diff --git a/includes/etch/common/doc/FAQ/html/ch-choosing.en.html b/includes/etch/common/doc/FAQ/html/ch-choosing.en.html new file mode 100644 index 0000000..e0403cc --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-choosing.en.html @@ -0,0 +1,961 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Choosing a Debian distribution</title> + +<link href="index.en.html" rel="start"> +<link href="ch-getting.en.html" rel="prev"> +<link href="ch-compat.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-choosing"></a></p> +<hr> + +<p> +[ <a href="ch-getting.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ 3 ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-compat.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 3 - Choosing a Debian distribution +</h1> + +<hr> + +<p> +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". +</p> + +<p> +For more information on the available distributions read <a +href="ch-ftparchives.en.html#s-dists">How many Debian distributions are there?, +Section 6.1</a>. +</p> + +<hr> + +<h2><a name="s3.1"></a>3.1 Which Debian distribution (stable/testing/unstable) is better for me?</h2> + +<p> +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. +</p> +<ul> +<li> +<p> +If security or stability are at all important for you: install stable. period. +This is the most preferred way. +</p> +</li> +</ul> +<ul> +<li> +<p> +If you are a new user installing to a desktop machine, start with stable. Some +of the software is quite old, but it's the least buggy environment to work in. +You can easily switch to the more modern unstable once you are a little more +confident. +</p> +</li> +</ul> +<ul> +<li> +<p> +If you are a desktop user with some experience in Linux and does not mind +facing the odd bug now and then, use unstable. It has all the latest and +greatest software, and bugs are usually fixed swiftly. +</p> +</li> +</ul> +<ul> +<li> +<p> +If you are running a server, especially one that has strong stability +requirements or is exposed to the Internet, install stable. This is by far the +strongest and safest choice. +</p> +</li> +</ul> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.1.1"></a>3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?</h3> + +<p> +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. +</p> + +<p> +For laptops, <code><a +href="http://www.linux-on-laptops.com/">http://www.linux-on-laptops.com/</a></code> +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. +</p> + +<p> +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 <code><a +href="http://lists.debian.org/debian-user/">http://lists.debian.org/debian-user/</a></code> +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 <code><a +href="http://www.debian.org/support">irc</a></code>. The mailing-list messages +are archived, so solution to your problem can help others with the same issue. +</p> + +<hr> + +<h3><a name="s3.1.2"></a>3.1.2 Will there be different different versions of packages in different distributions?</h3> + +<p> +Yes. Unstable has the most recent (latest) versions. But the packages in +unstable are not well tested and might have bugs. +</p> + +<p> +On the other hand, stable contains old versions of packages. But this package +is well tested and is less likely to have any bugs. +</p> + +<p> +The packages in testing fall between these two extremes. +</p> + +<hr> + +<h3><a name="s3.1.3"></a>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?</h3> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.1.4"></a>3.1.4 If I were to decide to change to another distribution, Can I do that?</h3> + +<p> +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. +</p> + +<p> +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.... +</p> + +<hr> + +<h3><a name="s3.1.5"></a>3.1.5 Could you tell me whether to install testing or unstable?</h3> + +<p> +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: +</p> +<ul> +<li> +<p> +Stable is rock solid. It does not break. +</p> +</li> +</ul> +<ul> +<li> +<p> +Testing breaks less often than Unstable. But when it breaks, it takes a long +time for things to get rectified. Sometimes this could be days and it could be +months at times. +</p> +</li> +</ul> +<ul> +<li> +<p> +Unstable changes a lot, and it can break at any point. However, fixes get +rectified in many occasions in a couple of days and it always has the latest +releases of software packaged for Debian. +</p> +</li> +</ul> + +<p> +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 <code>labplot</code> 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. +</p> + +<hr> + +<h3><a name="s3.1.6"></a>3.1.6 You are talking about testing being broken. What do you mean by that?</h3> + +<p> +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. +</p> + +<p> +When these things happen, the distribution is said to be broken (at least for +this package). +</p> + +<hr> + +<h3><a name="s3.1.7"></a>3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?</h3> + +<p> +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. +</p> + +<p> +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: +</p> +<ul> +<li> +<p> +Imagine you are interested in package XYZ. +</p> +</li> +</ul> +<ul> +<li> +<p> +Let's assume that on June 10, the version in testing is XYZ-3.6 and in unstable +it is XYZ-3.7 +</p> +</li> +</ul> +<ul> +<li> +<p> +After 10 days, XYZ-3.7 from unstable migrates into testing. +</p> +</li> +</ul> +<ul> +<li> +<p> +So on June 20, both testing and unstable have XYZ-3.7 in their repositories. +</p> +</li> +</ul> +<ul> +<li> +<p> +Let's say, The user of testing distribution sees that a new XYZ package is +available and updates his XYZ-3.6 to XYZ-3.7 +</p> +</li> +</ul> +<ul> +<li> +<p> +Now on June 25, someone using testing or unstable discovers an RC bug in +XYZ-3.7 and files it in the BTS. +</p> +</li> +</ul> +<ul> +<li> +<p> +The maintainer of XYZ fixes this bug and uploads it to unstable say on June 30. +Here it is assumed that it takes 5 days for the maintainer to fix the bug and +upload the new version. The number 5 should not be taken literally. It could +be less or more, depending upon the severity of the RC-bug at hand. +</p> +</li> +</ul> +<ul> +<li> +<p> +This new version in unstable, XYZ-3.8 is scheduled to enter testing on July +10th. +</p> +</li> +</ul> +<ul> +<li> +<p> +But on July 5th some other person, discovers another RC-bug in XYZ-3.8 +</p> +</li> +</ul> +<ul> +<li> +<p> +Let's say the maintainer of XYZ fixes this new RC-bug and uploads new version +of XYZ after 5 days. +</p> +</li> +</ul> +<ul> +<li> +<p> +So on July 10, testing has XYZ-3.7 while unstable has XYZ-3.9 +</p> +</li> +</ul> +<ul> +<li> +<p> +This new version XYZ-3.9 is now rescheduled to enter testing on July 20th. +</p> +</li> +</ul> +<ul> +<li> +<p> +Now since you are running testing, and since XYZ-3.7 is buggy, you could +probably use XYZ only after July 20th. That is you essentially ended up with a +broken XYZ for about one month. +</p> +</li> +</ul> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.1.8"></a>3.1.8 From an administrator's point of view, Which distribution requires more attention?</h3> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.1.9"></a>3.1.9 What happens when a new release is made?</h3> + +<p> +This question will not help you in choosing a Debian distribution. But sooner +or later you will face this question. +</p> + +<p> +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. +</p> +<ul> +<li> +<p> +oldstable = sarge; stable = etch; testing = lenny; unstable = sid +</p> +</li> +</ul> +<ul> +<li> +<p> +Unstable is always referred to as sid irrespective of whether a release is made +or not. +</p> +</li> +</ul> +<ul> +<li> +<p> +packages constantly migrate from sid to testing (i.e. lenny). But packages in +stable (i.e. etch) remain the same except for security updates. +</p> +</li> +</ul> +<ul> +<li> +<p> +after sometime testing becomes frozen. But it will still be called testing. +At this point no new packages from unstable can migrate to testing unless they +include release-critical (RC) bug fixes. +</p> +</li> +</ul> +<ul> +<li> +<p> +When testing is frozen, all the new bugfixes introduced, have to be manualy +checked by the members of the release team. This is done to ensure that there +wont be any unknown severe problems in the frozen testing. +</p> +</li> +</ul> +<ul> +<li> +<p> +RC bugs in 'frozen testing' are reduced to zero. +</p> +</li> +</ul> +<ul> +<li> +<p> +The 'frozen testing' with no rc-bugs will be released as the new stable +version. In our example, this new stable release will be called as lenny. +</p> +</li> +</ul> +<ul> +<li> +<p> +At this stage oldstable = etch, stable = lenny. The contents of stable and +'frozen testing' are same at this point. +</p> +</li> +</ul> +<ul> +<li> +<p> +A new testing is forked from the current stable. +</p> +</li> +</ul> +<ul> +<li> +<p> +Packages start coming down from sid to testing and the Debian community will be +working towards making the next stable release. +</p> +</li> +</ul> + +<hr> + +<h3><a name="s3.1.10"></a>3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?</h3> + +<p> +In most situations it is very easy to figure this out. Take a look at the +<code>/etc/apt/sources.list</code> file. There will be an entry similar to +this: +</p> + +<pre> + deb http://ftp.us.debian.org/debian/ unstable main contrib +</pre> + +<p> +The third field ('unstable' in the above example) indicates the Debian +distribution the system is currently tracking. +</p> + +<p> +You can also use <code>lsb_release</code> (available in the +<code>lsb-release</code> package). If you run this program in an unstable +system you will get: +</p> + +<pre> + $ 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 +</pre> + +<p> +However, this is always not that easy. Some systems might have +<code>sources.list</code> 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. +</p> + +<hr> + +<h3><a name="s3.1.11"></a>3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?</h3> + +<p> +If you are currently running stable, then in the +<code>/etc/apt/sources.list</code> 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 +<code>/etc/apt/sources.list</code> to testing. If you want to run unstable, +then change the third field to unstable. +</p> + +<p> +Currently testing is called lenny. So, if you change the third field of +<code>/etc/apt/sources.list</code> to lenny, then also you will be running +testing. But when lenny becomes stable, you will still be tracking lenny. +</p> + +<p> +Unstable is always called Sid. So if you change the third field of +<code>/etc/apt/sources.list</code> to sid, then you will be tracking unstable. +</p> + +<p> +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 +<code>/etc/apt/sources.list</code>. +</p> + +<p> +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. +</p> + +<p> +Nevertheless, once you make the above changes, you can run <code>aptitude +update</code> 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. +</p> + +<p> +It might be best in some situations to just fully upgrade to the new +distribution running <code>apt-get dist-upgrade</code>, <code>aptitude +safe-upgrade</code> or <code>aptitude full-upgrade</code>. Read apt's and +aptitude's manual pages for more information. +</p> + +<hr> + +<h3><a name="s3.1.12"></a>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?</h3> + +<p> +It depends on the entries in the <code>/etc/apt/sources.list</code> file. If +you are currently tracking testing, these entries are similar to either: +</p> + +<pre> + deb http://ftp.us.debian.org/debian/ testing main +</pre> + +<p> +or +</p> + +<pre> + deb http://ftp.us.debian.org/debian/ lenny main +</pre> + +<p> +If the third field in <code>/etc/apt/sources.list</code> 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. +</p> + +<p> +But if the third field contains 'lenny' then you will be tracking stable (since +lenny will then be the new stable distribution). +</p> + +<hr> + +<h3><a name="s3.1.13"></a>3.1.13 I am still confused. What did you say I should install?</h3> + +<p> +If unsure, the best bet would be stable distribution. +</p> + +<hr> + +<h2><a name="s3.2"></a>3.2 But what about Knoppix, Linex, Ubuntu, and others?</h2> + +<p> +They are not Debian; they are <em>Debian based</em>. Though there are many +similarities and commonalities between them, there are also crucial +differences. +</p> + +<p> +All these distributions have their own merits and are suited to some specific +set of users. For more information, read the information of <code><a +href="http://www.debian.org/misc/children-distros">software distributions based +on Debian</a></code> available at the Debian website. +</p> + +<hr> + +<h3><a name="s3.2.1"></a>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?</h3> + +<p> +These distributions are Debian based. But they are not Debian. You will be +still able to use apt package tools by pointing the +<code>/etc/apt/sources.list</code> file to these distributions' repositories. +But then you are not running Debian, you are running a different distribution. +They are not the same. +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.2.2"></a>3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?</h3> + +<p> +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. +</p> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.2.3"></a>3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?</h3> + +<p> +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. +</p> + +<p> +If all your user data (i.e. your <code>/home</code>) 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. <code>/etc/</code> and, maybe, <code>/var/</code>) is +still encouraged. +</p> + +<hr> + +<p> +[ <a href="ch-getting.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ 3 ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-compat.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/etch/common/doc/FAQ/html/ch-choosing.html b/includes/etch/common/doc/FAQ/html/ch-choosing.html new file mode 120000 index 0000000..5b6a705 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-choosing.html @@ -0,0 +1 @@ +ch-choosing.en.html
\ No newline at end of file diff --git a/includes/etch/common/doc/FAQ/html/ch-compat.en.html b/includes/etch/common/doc/FAQ/html/ch-compat.en.html new file mode 100644 index 0000000..375bff4 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-compat.en.html @@ -0,0 +1,554 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Compatibility issues</title> + +<link href="index.en.html" rel="start"> +<link href="ch-choosing.en.html" rel="prev"> +<link href="ch-software.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-compat"></a></p> +<hr> + +<p> +[ <a href="ch-choosing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ 4 ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-software.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 4 - Compatibility issues +</h1> + +<hr> + +<h2><a name="s-arches"></a>4.1 On what hardware architectures/systems does Debian GNU/Linux run?</h2> + +<p> +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 <code><a +href="http://en.tldp.org/FAQ/Linux-FAQ/intro.html#DOES-LINUX-RUN-ON-MY-COMPUTER">Linux +FAQ</a></code> for details. +</p> + +<p> +The current Debian GNU/Linux release, 4.0, contains a complete, binary +distribution for the following architectures: +</p> + +<p> +<em>i386</em>: this covers systems based on Intel and compatible processors, +including Intel's 386, 486, Pentium, Pentium Pro, Pentium II (both Klamath and +Celeron), and Pentium III, and most compatible processors by AMD, Cyrix and +others. +</p> + +<p> +<em>amd64</em>: this covers systems based on AMD 64bit CPUs with AMD64 +extension and all Intel CPUs with EM64T extension, and a common 64bit +userspace. +</p> + +<p> +<em>alpha</em>: Compaq/Digital's Alpha systems. +</p> + +<p> +<em>sparc</em>: this covers Sun's SPARC and most UltraSPARC systems. +</p> + +<p> +<em>powerpc</em>: this covers some IBM/Motorola PowerPC machines, including +CHRP, PowerMac and PReP machines. +</p> + +<p> +<em>arm</em>: ARM and StrongARM machines. +</p> + +<p> +<em>mips</em>: SGI's big-endian MIPS systems, Indy and Indigo2; +<em>mipsel</em>: little-endian MIPS machines, Digital DECstations. +</p> + +<p> +<em>hppa</em>: Hewlett-Packard's PA-RISC machines (712, C3000, L2000, A500). +</p> + +<p> +<em>ia64</em>: Intel IA-64 ("Itanium") computers. +</p> + +<p> +<em>s390</em>: IBM S/390 mainframe systems. +</p> + +<p> +The development of binary distributions of Debian for Sparc64 (UltraSPARC +native) architectures is currently underway. +</p> + +<p> +Support for the <em>m68k</em> architecture was dropped in this release, because +it did not meet the criteria set by the Debian Release Managers. This +architecture covers Amigas and ATARIs having a Motorola 680x0 processor for +x>=2; with MMU. However, the port is still active and available for +installation even if not a part of this official stable release and might be +reactivated for future releases. +</p> + +<p> +For more information on the available ports see the <code><a +href="http://www.debian.org/ports/">ports pages at the website</a></code>. +</p> + +<p> +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 <code><a +href="http://www.debian.org/releases/stable/installmanual">http://www.debian.org/releases/stable/installmanual</a></code>. +</p> + +<hr> + +<h2><a name="s-otherdistribs"></a>4.2 How compatible is Debian with other distributions of Linux?</h2> + +<p> +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. +</p> + +<p> +Debian GNU/Linux adheres to the <code><a +href="http://www.pathname.com/fhs/">Linux Filesystem Hierarchy +Standard</a></code>. 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. +</p> + +<p> +Debian GNU/Linux supports software developed for the <code><a +href="http://www.linuxbase.org/">Linux Standard Base</a></code>. 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 <code><a +href="https://www.linux-foundation.org/lsb-cert/productdir.php">Linux +Foundation Certification webpage</a></code>. Discussion and coordination of +efforts towards ensuring Debian meets the requirements of the Linux Standard +Base is taking place on the <code><a +href="http://lists.debian.org/debian-lsb/">debian-lsb mailing list</a></code>. +</p> + +<hr> + +<h2><a name="s-otherunices"></a>4.3 How source code compatible is Debian with other Unix systems?</h2> + +<p> +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. +</p> + +<p> +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.) +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-otherpackages"></a>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?</h2> + +<p> +Different Linux distributions use different package formats and different +package management programs. +</p> +<dl> +<dt><strong>You probably can:</strong></dt> +<dd> +<p> +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 <code><a href="http://packages.debian.org/alien">Alien</a></code> package +is used to convert between different package formats. +</p> +</dd> +</dl> +<dl> +<dt><strong>You probably do not want to:</strong></dt> +<dd> +<p> +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. +</p> +</dd> +</dl> +<dl> +<dt><strong>A better way:</strong></dt> +<dd> +<p> +The Linux File System Standard (and therefore Debian GNU/Linux) requires that +subdirectories under <samp>/usr/local/</samp> 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. +</p> +</dd> +</dl> + +<hr> + +<h2><a name="s-non-debian-programs"></a>4.5 How should I install a non-Debian program?</h2> + +<p> +Files under the directory <samp>/usr/local/</samp> 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 +<samp>/usr/local/src/foo</samp>. After you compile them, place the binaries in +<samp>/usr/local/bin/</samp>, the libraries in <samp>/usr/local/lib/</samp>, +and the configuration files in <samp>/usr/local/etc/</samp>. +</p> + +<p> +If your programs and/or files really must be placed in some other directory, +you could still store them in <samp>/usr/local/</samp>, and build the +appropriate symbolic links from the required location to its location in +<samp>/usr/local/</samp>, e.g., you could make the link +</p> + +<pre> + ln -s /usr/local/bin/foo /usr/bin/foo +</pre> + +<p> +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 <a href="ch-support.en.html#s-debiandocs">What other +documentation exists on and for a Debian system?, Section 12.1</a>). +</p> + +<hr> + +<h2><a name="s-termcap"></a>4.6 Why can't I compile programs that require libtermcap?</h2> + +<p> +Debian uses the <samp>terminfo</samp> database and the <samp>ncurses</samp> +library of terminal interface routes, rather than the <samp>termcap</samp> +database and the <samp>termcap</samp> library. Users who are compiling +programs that require some knowledge of the terminal interface should replace +references to <samp>libtermcap</samp> with references to +<samp>libncurses</samp>. +</p> + +<p> +To support binaries that have already been linked with the <samp>termcap</samp> +library, and for which you do not have the source, Debian provides a package +called <code>termcap-compat</code>. This provides both +<samp>libtermcap.so.2</samp> and <samp>/etc/termcap</samp>. 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 +<samp>/etc/termcap</samp> file. +</p> + +<hr> + +<h2><a name="s-accelx"></a>4.7 Why can't I install AccelX?</h2> + +<p> +AccelX uses the <samp>termcap</samp> library for installation. See <a +href="#s-termcap">Why can't I compile programs that require libtermcap?, +Section 4.6</a> above. +</p> + +<hr> + +<h2><a name="s-motifnls"></a>4.8 Why do my old XFree 2.1 Motif applications crash?</h2> + +<p> +You need to install the <code>motifnls</code> 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. +</p> + +<p> +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. +</p> + +<hr> + +<p> +[ <a href="ch-choosing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ 4 ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-software.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-compat.html b/includes/etch/common/doc/FAQ/html/ch-compat.html index 0696449..0696449 120000 --- a/includes/sid/common/doc/FAQ/html/ch-compat.html +++ b/includes/etch/common/doc/FAQ/html/ch-compat.html diff --git a/includes/etch/common/doc/FAQ/html/ch-contributing.en.html b/includes/etch/common/doc/FAQ/html/ch-contributing.en.html new file mode 100644 index 0000000..db2d6e3 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-contributing.en.html @@ -0,0 +1,370 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Contributing to the Debian Project</title> + +<link href="index.en.html" rel="start"> +<link href="ch-support.en.html" rel="prev"> +<link href="ch-redistrib.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-contributing"></a></p> +<hr> + +<p> +[ <a href="ch-support.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ 13 ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-redistrib.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 13 - Contributing to the Debian Project +</h1> + +<hr> + +<p> +<code><a href="http://www.debian.org/donations">Donations</a></code> 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. +</p> + +<hr> + +<h2><a name="s-contrib"></a>13.1 How can I become a Debian software developer?</h2> + +<p> +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. +</p> + +<p> +The description of becoming a Debian developer can be found at the <code><a +href="http://www.debian.org/devel/join/newmaint">New Maintainer's +Corner</a></code> at the Debian web site. +</p> + +<hr> + +<h2><a name="s-contribresources"></a>13.2 How can I contribute resources to the Debian project?</h2> + +<p> +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 <code><a href="http://www.debian.org/mirror/size">Debian mirror +size</a></code> page for information on the disk space requirements. +</p> + +<p> +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. +</p> + +<p> +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 +<code><a +href="mailto:debian-admin@lists.debian.org">debian-admin@lists.debian.org</a></code>. +</p> + +<hr> + +<h2><a name="s-supportingorganizations"></a>13.3 How can I contribute financially to the Debian project?</h2> + +<p> +One can make individual donations to one of two organizations that are critical +to the development of the Debian project. +</p> + +<hr> + +<h3><a name="s-SPI"></a>13.3.1 Software in the Public Interest</h3> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +SPI can be reached at: <code><a +href="http://www.spi-inc.org/">http://www.spi-inc.org/</a></code>. +</p> + +<hr> + +<h3><a name="s-FSF"></a>13.3.2 Free Software Foundation</h3> + +<p> +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. +</p> + +<p> +FSF can be reached at: <code><a +href="http://www.fsf.org/">http://www.fsf.org/</a></code>. +</p> + +<hr> + +<p> +[ <a href="ch-support.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ 13 ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-redistrib.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-contributing.html b/includes/etch/common/doc/FAQ/html/ch-contributing.html index 4185524..4185524 120000 --- a/includes/sid/common/doc/FAQ/html/ch-contributing.html +++ b/includes/etch/common/doc/FAQ/html/ch-contributing.html diff --git a/includes/etch/common/doc/FAQ/html/ch-customizing.en.html b/includes/etch/common/doc/FAQ/html/ch-customizing.en.html new file mode 100644 index 0000000..9467112 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-customizing.en.html @@ -0,0 +1,716 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Customizing your installation of Debian GNU/Linux</title> + +<link href="index.en.html" rel="start"> +<link href="ch-kernel.en.html" rel="prev"> +<link href="ch-support.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-customizing"></a></p> +<hr> + +<p> +[ <a href="ch-kernel.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ 11 ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-support.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 11 - Customizing your installation of Debian GNU/Linux +</h1> + +<hr> + +<h2><a name="s-papersize"></a>11.1 How can I ensure that all programs use the same paper size?</h2> + +<p> +Install the <code>libpaper1</code> package, and it will ask you for a +system-wide default paper size. This setting will be kept in the file +<samp>/etc/papersize</samp>. +</p> + +<p> +Users can override the paper size setting using the <samp>PAPERSIZE</samp> +environment variable. For details, see the manual page +<code>papersize(5)</code>. +</p> + +<hr> + +<h2><a name="s-hardwareaccess"></a>11.2 How can I provide access to hardware peripherals, without compromising security?</h2> + +<p> +Many device files in the <samp>/dev</samp> directory belong to some predefined +groups. For example, <samp>/dev/fd0</samp> belongs to the <samp>floppy</samp> +group, and <samp>/dev/dsp</samp> belongs to the <samp>audio</samp> group. +</p> + +<p> +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: +</p> + +<pre> + adduser user group +</pre> + +<p> +This way you won't have to change the file permissions on the device. +</p> + +<p> +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 <samp>groups</samp>. +</p> + +<p> +Notice that, since the introduction of <samp>udev</samp> 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 <samp>/etc/udev</samp>. +</p> + +<hr> + +<h2><a name="s-consolefont"></a>11.3 How do I load a console font on startup the Debian way?</h2> + +<p> +The <code>kbd</code> and <code>console-tools</code> packages support this, edit +<samp>/etc/kbd/config</samp> or <samp>/etc/console-tools/config</samp> files. +</p> + +<hr> + +<h2><a name="s-appdefaults"></a>11.4 How can I configure an X11 program's application defaults?</h2> + +<p> +Debian's X programs will install their application resource data in the +<samp>/etc/X11/app-defaults/</samp> 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. +</p> + +<hr> + +<h2><a name="s-booting"></a>11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's.</h2> + +<p> +Like all Unices, Debian boots up by executing the program <samp>init</samp>. +The configuration file for <samp>init</samp> (which is +<samp>/etc/inittab</samp>) specifies that the first script to be executed +should be <samp>/etc/init.d/rcS</samp>. This script runs all of the scripts in +<samp>/etc/rcS.d/</samp> 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 <samp>/etc/rc.boot/</samp> too. +Any scripts in the latter directory are usually reserved for system +administrator use, and using them in packages is deprecated. +</p> + +<p> +After completing the boot process, <samp>init</samp> executes all start scripts +in a directory specified by the default runlevel (this runlevel is given by the +entry for <samp>id</samp> in <samp>/etc/inittab</samp>). Like most System V +compatible Unices, Linux has 7 runlevels: +</p> +<ul> +<li> +<p> +0 (halt the system), +</p> +</li> +</ul> +<ul> +<li> +<p> +1 (single-user mode), +</p> +</li> +</ul> +<ul> +<li> +<p> +2 through 5 (various multi-user modes), and +</p> +</li> +</ul> +<ul> +<li> +<p> +6 (reboot the system). +</p> +</li> +</ul> + +<p> +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 +<samp>/etc/rc2.d/</samp> will be run. +</p> + +<p> +In fact, the scripts in any of the directories, <samp>/etc/rcN.d/</samp> are +just symbolic links back to scripts in <samp>/etc/init.d/</samp>. However, the +<em>names</em> of the files in each of the <samp>/etc/rcN.d/</samp> directories +are selected to indicate the <em>way</em> the scripts in +<samp>/etc/init.d/</samp> 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. +</p> + +<p> +This approach works because the scripts in <samp>/etc/init.d/</samp> 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. +</p> + +<p> +For example, with the argument `reload' the command +</p> + +<pre> + /etc/init.d/sendmail reload +</pre> + +<p> +sends the sendmail daemon a signal to reread its configuration file. (BTW, +Debian supplies <code>invoke-rc.d</code> as a wrapper for invoking the scripts +in <samp>/etc/init.d/</samp>.) +</p> + +<hr> + +<h2><a name="s-custombootscripts"></a>11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?</h2> + +<p> +Suppose a system needs to execute script <samp>foo</samp> on start-up, or on +entry to a particular (System V) runlevel. Then the system administrator +should: +</p> +<ul> +<li> +<p> +Enter the script <samp>foo</samp> into the directory <samp>/etc/init.d/</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Run the Debian command <samp>update-rc.d</samp> with appropriate arguments, to +specify which runlevels should start the service, and which runlevels should +stop the service. +</p> +</li> +</ul> +<ul> +<li> +<p> +Consider rebooting the system to check that the service starts correctly +(assuming that you've asked for it to be started in the default runlevel). +Otherwise, manually start it by running `<samp>/etc/init.d/foo start</samp>'. +</p> +</li> +</ul> + +<p> +One might, for example, cause the script <samp>foo</samp> to execute at +boot-up, by putting it in <samp>/etc/init.d/</samp> and running +<samp>update-rc.d foo defaults 19</samp>. The argument `<samp>defaults</samp>' +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 <samp>foo</samp> 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 `<samp>19</samp>' ensures that +<samp>foo</samp> is called after all scripts whose number is less than 19 have +completed, and before all scripts whose number is 20 or greater. +</p> + +<hr> + +<h2><a name="s-interconffiles"></a>11.7 How does the package management system deal with packages that contain configuration files for other packages?</h2> + +<p> +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 <code>dpkg</code> 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. +</p> + +<p> +Instead, create a local package that modifies the configuration files of the +"group" of Debian packages of interest. Then <code>dpkg</code> 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. +</p> + +<hr> + +<h2><a name="s-divert"></a>11.8 How do I override a file installed by a package, so that a different version can be used instead?</h2> + +<p> +Suppose a sysadmin or local user wishes to use a program +"login-local" rather than the program "login" provided by +the Debian <code>login</code> package. +</p> + +<p> +Do <strong>not</strong>: +</p> +<ul> +<li> +<p> +Overwrite <samp>/bin/login</samp> with <samp>login-local</samp>. +</p> +</li> +</ul> + +<p> +The package management system will not know about this change, and will simply +overwrite your custom <samp>/bin/login</samp> whenever <samp>login</samp> (or +any package that provides <samp>/bin/login</samp>) is installed or updated. +</p> + +<p> +Rather, do +</p> +<ul> +<li> +<p> +Execute: +</p> + +<pre> + dpkg-divert --divert /bin/login.debian /bin/login +</pre> + +<p> +in order to cause all future installations of the Debian <code>login</code> +package to write the file <samp>/bin/login</samp> to +<samp>/bin/login.debian</samp> instead. +</p> +</li> +</ul> +<ul> +<li> +<p> +Then execute: +</p> + +<pre> + cp login-local /bin/login +</pre> + +<p> +to move your own locally-built program into place. +</p> +</li> +</ul> + +<p> +Run <samp>dpkg-divert --list</samp> to see which diversions are currently +active on your system. +</p> + +<p> +Details are given in the manual page <code>dpkg-divert(8)</code>. +</p> + +<hr> + +<h2><a name="s-localpackages"></a>11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?</h2> + +<p> +Execute the command: +</p> + +<pre> + dpkg-scanpackages BIN_DIR OVERRIDE_FILE [PATHPREFIX] > my_Packages +</pre> + +<p> +where: +</p> +<ul> +<li> +<p> +BIN-DIR is a directory where Debian archive files (which usually have an +extension of ".deb") are stored. +</p> +</li> +</ul> +<ul> +<li> +<p> +OVERRIDE_FILE is a file that is edited by the distribution maintainers and is +usually stored on a Debian FTP archive at <samp>indices/override.main.gz</samp> +for the Debian packages in the "main" distribution. You can ignore +this for local packages. +</p> +</li> +</ul> +<ul> +<li> +<p> +PATHPREFIX is an <em>optional</em> string that can be prepended to the +<samp>my_Packages</samp> file being produced. +</p> +</li> +</ul> + +<p> +Once you have built the file <samp>my_Packages</samp>, tell the package +management system about it by using the command: +</p> + +<pre> + dpkg --merge-avail my_Packages +</pre> + +<p> +If you are using APT, you can add the local repository to your +<code>sources.list(5)</code> file, too. +</p> + +<hr> + +<h2><a name="s-diverse"></a>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?</h2> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +For example, there might exist two different versions of newsreaders on a +system. The news server package might 'recommend' that there exist +<em>some</em> news reader on the system, but the choice of <samp>tin</samp> or +<samp>trn</samp> is left up to the individual user. This is satisfied by +having both the <code>tin</code> and <code>trn</code> packages provide the +virtual package <code>news-reader</code>. <em>Which</em> program is invoked is +determined by a link pointing from a file with the virtual package name +<samp>/etc/alternatives/news-reader</samp> to the selected file, e.g., +<samp>/usr/bin/trn</samp>. +</p> + +<p> +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 <samp>update-alternatives</samp> provides a way of +ensuring that all the files associated with a specified package are selected as +a system default. +</p> + +<p> +For example, to check what executables provide `x-window-manager', run: +</p> + +<pre> + update-alternatives --display x-window-manager +</pre> + +<p> +If you want to change it, run: +</p> + +<pre> + update-alternatives --config x-window-manager +</pre> + +<p> +And follow the instructions on the screen (basically, press the number next to +the entry you'd like better). +</p> + +<p> +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: +</p> + +<pre> + update-alternatives --install /usr/bin/x-window-manager \ + x-window-manager /usr/local/bin/wmaker-cvs 50 +</pre> + +<p> +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). +</p> + +<p> +To remove an alternative you added, simply run: +</p> + +<pre> + update-alternatives --remove x-window-manager /usr/local/bin/wmaker-cvs +</pre> + +<hr> + +<p> +[ <a href="ch-kernel.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ 11 ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-support.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-customizing.html b/includes/etch/common/doc/FAQ/html/ch-customizing.html index 1cfdfaa..1cfdfaa 120000 --- a/includes/sid/common/doc/FAQ/html/ch-customizing.html +++ b/includes/etch/common/doc/FAQ/html/ch-customizing.html diff --git a/includes/etch/common/doc/FAQ/html/ch-faqinfo.en.html b/includes/etch/common/doc/FAQ/html/ch-faqinfo.en.html new file mode 100644 index 0000000..9edac20 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-faqinfo.en.html @@ -0,0 +1,407 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - General information about the FAQ</title> + +<link href="index.en.html" rel="start"> +<link href="ch-nexttime.en.html" rel="prev"> +<link href="index.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-faqinfo"></a></p> +<hr> + +<p> +[ <a href="ch-nexttime.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ 16 ] +[ <a href="index.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 16 - General information about the FAQ +</h1> + +<hr> + +<h2><a name="s-authors"></a>16.1 Authors</h2> + +<p> +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. +</p> + +<p> +Parts of the information came from: +</p> +<ul> +<li> +<p> +The Debian-1.1 release announcement, by <code><a +href="http://www.perens.com/">Bruce Perens</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +The Linux FAQ, by <code><a +href="http://www.chiark.greenend.org.uk/~ijackson/">Ian Jackson</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code><a href="http://lists.debian.org/">Debian Mailing Lists +Archives</a></code>, +</p> +</li> +</ul> +<ul> +<li> +<p> +the dpkg programmers' manual and the Debian Policy manual (see <a +href="ch-support.en.html#s-debiandocs">What other documentation exists on and +for a Debian system?, Section 12.1</a>) +</p> +</li> +</ul> +<ul> +<li> +<p> +many developers, volunteers, and beta testers, and +</p> +</li> +</ul> +<ul> +<li> +<p> +the flaky memories of its authors. :-) +</p> +</li> +</ul> +<ul> +<li> +<p> +Kamaraju Kusumanchi's <code><a +href="http://people.cornell.edu/pages/kk288/debian_choosing_distribution.html">Choosing +a Debian distribution FAQ</a></code>, who graciously made it GPL so I could +include it as a new chapter (see <a href="ch-choosing.en.html">Choosing a +Debian distribution, Chapter 3</a>) +</p> +</li> +</ul> + +<p> +The authors would like to thank all those who helped make this document +possible. +</p> + +<p> +All warranties are disclaimed. All trademarks are property of their respective +trademark owners. +</p> + +<hr> + +<h2><a name="s-feedback"></a>16.2 Feedback</h2> + +<p> +Comments and additions to this document are always welcome. Please send e-mail +to <code><a +href="mailto:doc-debian@packages.debian.org">doc-debian@packages.debian.org</a></code>, +or submit a wishlist bug report against the <code><code><a +href="http://bugs.debian.org/debian-faq">debian-faq</a></code></code> package. +</p> + +<hr> + +<h2><a name="s-latest"></a>16.3 Availability</h2> + +<p> +The latest version of this document can be viewed on the Debian WWW pages at +<code><a +href="http://www.debian.org/doc/FAQ/">http://www.debian.org/doc/FAQ/</a></code>. +</p> + +<p> +It is also available for download in plain text, HTML, PostScript and PDF +formats at <code><a +href="http://www.debian.org/doc/user-manuals#faq">http://www.debian.org/doc/user-manuals#faq</a></code>. +Also, there are several translations there. +</p> + +<p> +This document is available in the <code>debian-faq</code> package. +Translations are available in <code>debian-faq-de</code>, +<code>debian-faq-fr</code> and other packages. +</p> + +<p> +The original SGML files used to create this document are also available in +<code>debian-faq</code>'s source package, or in SVN at: +<samp>svn://svn.debian.org/svn/ddp/manuals/trunk/debian-faq</samp> and <code><a +href="http://svn.debian.org/viewsvn/ddp/manuals/trunk/debian-faq/">http://svn.debian.org/viewsvn/ddp/manuals/trunk/debian-faq/</a></code>. +</p> + +<hr> + +<h2><a name="s-docformat"></a>16.4 Document format</h2> + +<p> +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. +</p> + +<p> +Conversion utilities for DebianDoc SGML are available in Debian package +<code>debiandoc-sgml</code>. +</p> + +<hr> + +<p> +[ <a href="ch-nexttime.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ 16 ] +[ <a href="index.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-faqinfo.html b/includes/etch/common/doc/FAQ/html/ch-faqinfo.html index 0f759b4..0f759b4 120000 --- a/includes/sid/common/doc/FAQ/html/ch-faqinfo.html +++ b/includes/etch/common/doc/FAQ/html/ch-faqinfo.html diff --git a/includes/etch/common/doc/FAQ/html/ch-ftparchives.en.html b/includes/etch/common/doc/FAQ/html/ch-ftparchives.en.html new file mode 100644 index 0000000..0efd28a --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-ftparchives.en.html @@ -0,0 +1,756 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - The Debian FTP archives</title> + +<link href="index.en.html" rel="start"> +<link href="ch-software.en.html" rel="prev"> +<link href="ch-pkg_basics.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-ftparchives"></a></p> +<hr> + +<p> +[ <a href="ch-software.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ 6 ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-pkg_basics.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 6 - The Debian FTP archives +</h1> + +<hr> + +<h2><a name="s-dists"></a>6.1 How many Debian distributions are there?</h2> + +<p> +There are three major distributions: the "stable" distribution, the +"testing" distribution, and the "unstable" distribution. +The "testing" distribution is sometimes `frozen' (see <a +href="#s-frozen">What about "testing"? How is it `frozen'?, Section +6.5.1</a>). Next to these, there is the "oldstable" distribution +(that's just the one from before "stable"), and the +"experimental" distribution. +</p> + +<p> +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. +</p> + +<p> +See <a href="ch-choosing.en.html">Choosing a Debian distribution, Chapter 3</a> +for help when choosing a Debian distribution. +</p> + +<hr> + +<h2><a name="s-codenames"></a>6.2 What are all those names like etch, lenny, etc.?</h2> + +<p> +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 <samp>unstable</samp> suddenly changed its name to +<samp>stable</samp>, a lot of stuff would have to be needlessly downloaded +again). +</p> + +<p> +Currently, <samp>stable</samp> is a symbolic link to <samp>etch</samp> (i.e. +Debian GNU/Linux 4.0) and <samp>testing</samp> is a symbolic link to +<samp>lenny</samp>. This means that <samp>etch</samp> is the current stable +distribution and <samp>lenny</samp> is the current testing distribution. +</p> + +<p> +<samp>unstable</samp> is a permanent symbolic link to <samp>sid</samp>, as +<samp>sid</samp> is always the unstable distribution (see <a href="#s-sid">What +about "sid"?, Section 6.3</a>). +</p> + +<hr> + +<h3><a name="s-oldcodenames"></a>6.2.1 Which other codenames have been used in the past?</h3> + +<p> +Other codenames that have been already used are: <samp>buzz</samp> for release +1.1, <samp>rex</samp> for release 1.2, <samp>bo</samp> for releases 1.3.x, +<samp>hamm</samp> for release 2.0, <samp>slink</samp> for release 2.1, +<samp>potato</samp> for release 2.2, <samp>woody</samp> for release 3.0, +<samp>sarge</samp> for release 3.1, and <samp>etch</samp> for release 4.0. +</p> + +<hr> + +<h3><a name="s-sourceforcodenames"></a>6.2.2 Where do these codenames come from?</h3> + +<p> +So far they have been characters taken from the movie "Toy Story" by +Pixar. +</p> +<ul> +<li> +<p> +<em>buzz</em> (Buzz Lightyear) was the spaceman, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>rex</em> was the tyrannosaurus, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>bo</em> (Bo Peep) was the girl who took care of the sheep, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>hamm</em> was the piggy bank, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>slink</em> (Slinky Dog (R)) was the toy dog, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>potato</em> was, of course, Mr. Potato (R), +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>woody</em> was the cowboy, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>sarge</em> was the sergeant of the Green Plastic Army Men, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>etch</em> was the toy blackboard (Etch-a-Sketch (R)), +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>lenny</em> was the binoculars. +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>sid</em> was the boy next door who destroyed toys. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-sid"></a>6.3 What about "sid"?</h2> + +<p> +<em>sid</em> or <em>unstable</em> is the place where most of the packages are +initially uploaded. It will never be released directly, because packages which +are to be released will first have to be included in <em>testing</em>, in order +to be released in <em>stable</em> later on. sid contains packages for both +released and unreleased architectures. +</p> + +<p> +The name "sid" also comes from the "Toy Story" animated +motion picture: Sid was the boy next door who destroyed toys :-) +</p> + +<p> +[<a href="footnotes.en.html#f2" name="fr2">2</a>] +</p> + +<hr> + +<h2><a name="s-stable"></a>6.4 What does the stable directory contain?</h2> +<ul> +<li> +<p> +stable/main/: This directory contains the packages which formally constitute +the most recent release of the Debian GNU/Linux system. +</p> + +<p> +These packages all comply with the <code><a +href="http://www.debian.org/social_contract#guidelines">Debian Free Software +Guidelines</a></code>, and are all freely usable and distributable. +</p> +</li> +</ul> +<ul> +<li> +<p> +stable/non-free/: This directory contains packages distribution of which is +restricted in a way that requires that distributors take careful account of the +specified copyright requirements. +</p> + +<p> +For example, some packages have licenses which prohibit commercial +distribution. Others can be redistributed but are in fact shareware and not +free software. The licenses of each of these packages must be studied, and +possibly negotiated, before the packages are included in any redistribution +(e.g., in a CD-ROM). +</p> +</li> +</ul> +<ul> +<li> +<p> +stable/contrib/: This directory contains packages which are DFSG-free and +<em>freely distributable</em> themselves, but somehow depend on a package that +is <em>not</em> freely distributable and thus available only in the non-free +section. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-testing"></a>6.5 What does the testing distribution contain?</h2> + +<p> +Packages are installed into the `testing' directory after they have undergone +some degree of testing in <a href="#s-unstable">unstable</a>. +</p> + +<p> +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. +</p> + +<p> +More information about the status of "testing" in general and the +individual packages is available at <code><a +href="http://www.debian.org/devel/testing">http://www.debian.org/devel/testing</a></code>. +</p> + +<hr> + +<h3><a name="s-frozen"></a>6.5.1 What about "testing"? How is it `frozen'?</h3> + +<p> +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". +</p> + +<p> +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. +</p> + +<p> +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 <code><a +href="http://www.debian.org/releases/testing/">current testing release +information</a></code>. +</p> + +<p> +Once that bug count lowers to maximum acceptable values, the frozen +"testing" distribution is declared "stable" and released +with a version number. +</p> + +<p> +With each new release, the previous "stable" distribution becomes +obsolete and moves to the archive. For more information please see <code><a +href="http://www.debian.org/distrib/archive">Debian archive</a></code>. +</p> + +<hr> + +<h2><a name="s-unstable"></a>6.6 What does the unstable distribution contain?</h2> + +<p> +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 :-) +</p> + +<p> +There are also main, contrib and non-free subdirectories in `unstable', +separated on the same criteria as in `stable'. +</p> + +<hr> + +<h2><a name="s-dirtree"></a>6.7 What are all those directories at the Debian FTP archives?</h2> + +<p> +The software that has been packaged for Debian GNU/Linux is available in one of +several directory trees on each Debian mirror site. +</p> + +<p> +The <samp>dists</samp> directory is short for "distributions", and it +is the canonical way to access the currently available Debian releases (and +pre-releases). +</p> + +<p> +The <samp>pool</samp> directory contains the actual packages, see <a +href="#s-pools">What's in the <samp>pool</samp> directory?, Section 6.10</a>. +</p> + +<p> +There are the following supplementary directories: +</p> +<dl> +<dt><em>/tools/</em>:</dt> +<dd> +<p> +DOS utilities for creating boot disks, partitioning your disk drive, +compressing/decompressing files, and booting Linux. +</p> +</dd> +</dl> +<dl> +<dt><em>/doc/</em>:</dt> +<dd> +<p> +The basic Debian documentation, such as this FAQ, the bug reporting system +instructions, etc. +</p> +</dd> +</dl> +<dl> +<dt><em>/indices/</em>:</dt> +<dd> +<p> +various indices of the site (the Maintainers file and the override files). +</p> +</dd> +</dl> +<dl> +<dt><em>/project/</em>:</dt> +<dd> +<p> +mostly developer-only materials and some miscellaneous files. +</p> +</dd> +</dl> + +<hr> + +<h2><a name="s-archsections"></a>6.8 What are all those directories inside <samp>dists/stable/main</samp>?</h2> + +<p> +Within each of the major directory trees[<a href="footnotes.en.html#f3" +name="fr3">3</a>], there are three sets of subdirectories containing index +files. +</p> + +<p> +There's one set of <samp>binary-<var>something</var></samp> subdirectories +which contain index files for binary packages of each available computer +architecture, for example <samp>binary-i386</samp> for packages which execute +on Intel x86 PC machines or <samp>binary-sparc</samp> for packages which +execute on Sun SPARCStations. +</p> + +<p> +The complete list of available architectures for each release is available at +<code><a href="http://www.debian.org/releases/">the release's web +page</a></code>. For the current release, please see <a +href="ch-compat.en.html#s-arches">On what hardware architectures/systems does +Debian GNU/Linux run?, Section 4.1</a>. +</p> + +<p> +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 <a +href="#s-pools"><samp>pool</samp> directory</a>. +</p> + +<p> +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). +</p> + +<p> +Last but not least, there's a set of subdirectories meant for the installation +system index files, they are at +<samp>debian-installer/binary-<var>architecture</var></samp>. +</p> + +<hr> + +<h2><a name="s-source"></a>6.9 Where is the source code?</h2> + +<p> +Source code is included for everything in the Debian system. Moreover, the +license terms of most programs in the system <em>require</em> that source code +be distributed along with the programs, or that an offer to provide the source +code accompany the programs. +</p> + +<p> +The source code is distributed in the <samp>pool</samp> directory (see <a +href="#s-pools">What's in the <samp>pool</samp> directory?, Section 6.10</a>) +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 <samp>apt-get source mypackagename</samp>. +</p> + +<p> +Some packages are only distributed as source code due to the restrictions in +their licenses. Notably, one such package is <samp>pine</samp>, see <a +href="ch-software.en.html#s-pine">Where is pine?, Section 5.10</a> for more +information. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-pools"></a>6.10 What's in the <samp>pool</samp> directory?</h2> + +<p> +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. +</p> + +<p> +You can find out where each package is placed by executing a command like +<samp>apt-cache showsrc mypackagename</samp> and looking at the `Directory:' +line. For example, the <samp>apache</samp> packages are stored in +<samp>pool/main/a/apache/</samp>. +</p> + +<p> +Additionally, since there are so many <samp>lib*</samp> packages, these are +treated specially: for instance, libpaper packages are stored in +<samp>pool/main/libp/libpaper/</samp>. +</p> + +<p> +[<a href="footnotes.en.html#f4" name="fr4">4</a>] +</p> + +<hr> + +<h2><a name="s-incoming"></a>6.11 What is "incoming"?</h2> + +<p> +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. +</p> + +<p> +Usually nobody should install things from this place. However, in some rare +cases of emergency, the incoming directory is available at <code><a +href="http://incoming.debian.org/">http://incoming.debian.org/</a></code>. You +can manually fetch packages, check the GPG signature and MD5sums in the +.changes and .dsc files, and then install them. +</p> + +<hr> + +<h2><a name="s-ownrepository"></a>6.12 How do I set up my own apt-able repository?</h2> + +<p> +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 <code><a +href="http://www.debian.org/doc/manuals/repository-howto/repository-howto">Debian +Repository HOWTO</a></code>. +</p> + +<hr> + +<p> +[ <a href="ch-software.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ 6 ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-pkg_basics.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-ftparchives.html b/includes/etch/common/doc/FAQ/html/ch-ftparchives.html index cdad69f..cdad69f 120000 --- a/includes/sid/common/doc/FAQ/html/ch-ftparchives.html +++ b/includes/etch/common/doc/FAQ/html/ch-ftparchives.html diff --git a/includes/etch/common/doc/FAQ/html/ch-getting.en.html b/includes/etch/common/doc/FAQ/html/ch-getting.en.html new file mode 100644 index 0000000..16d506c --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-getting.en.html @@ -0,0 +1,451 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Getting and installing Debian GNU/Linux</title> + +<link href="index.en.html" rel="start"> +<link href="ch-basic_defs.en.html" rel="prev"> +<link href="ch-choosing.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-getting"></a></p> +<hr> + +<p> +[ <a href="ch-basic_defs.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ 2 ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-choosing.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 2 - Getting and installing Debian GNU/Linux +</h1> + +<hr> + +<p> +The official document giving installation instructions is the <code><a +href="http://www.debian.org/releases/stable/installmanual">Debian GNU/Linux +Installation Guide</a></code>. We'll give some additional notes about getting +and installing Debian GNU/Linux here. +</p> + +<hr> + +<h2><a name="s-version"></a>2.1 What is the latest version of Debian?</h2> + +<p> +Currently there are three versions of Debian GNU/Linux: +</p> +<dl> +<dt><em>release 4.0, a.k.a. the `stable' distribution or etch</em></dt> +<dd> +<p> +This is stable and well tested software, it changes if major security or +usability fixes are incorporated. +</p> +</dd> +</dl> +<dl> +<dt><em>the `testing' distribution, currently called lenny</em></dt> +<dd> +<p> +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'. +</p> +</dd> +</dl> +<dl> +<dt><em>the `unstable' distribution</em></dt> +<dd> +<p> +This is the version currently under development; it is updated continuously. +You can retrieve packages from the `unstable' archive on any Debian FTP site +and use them to upgrade your system at any time, but you may not expect the +system to be as usable or as stable as before - that's why it's called +`<strong>unstable</strong>'! +</p> +</dd> +</dl> + +<p> +Please see <a href="ch-ftparchives.en.html#s-dists">How many Debian +distributions are there?, Section 6.1</a> for more information. +</p> + +<hr> + +<h2><a name="s-updatestable"></a>2.2 Are there package upgrades in `stable'?</h2> + +<p> +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 <code><a +href="ftp://security.debian.org">security.debian.org</a></code>. +</p> + +<p> +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. +</p> + +<p> +For more information related to security support please read the <code><a +href="http://www.debian.org/security/faq">Security FAQ</a></code> or the +<code><a href="http://www.debian.org/doc/manuals/securing-debian-howto/">Debian +Security Manual</a></code>. +</p> + +<hr> + +<h2><a name="s-boot-floppies"></a>2.3 Where/how can I get the Debian installation disks?</h2> + +<p> +You can get the installation disks by downloading the appropriate files from +one of the <code><a href="http://www.debian.org/mirror/list">Debian +mirrors</a></code>. +</p> + +<p> +Please refer to <code><a href="http://www.debian.org/CD">Debian GNU/Linux on +CDs</a></code> for more information about CD (and DVD) images. +</p> + +<hr> + +<h2><a name="s-cdrom"></a>2.4 How do I install the Debian from CD-ROMs?</h2> + +<p> +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 <code><a +href="http://www.debian.org/releases/stable/installmanual">Debian GNU/Linux +Installation Guide</a></code> for more information. +</p> + +<hr> + +<h2><a name="s-cdimage-symlinks"></a>2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!</h2> + +<p> +Official Debian CD images indeed contain symlinks like: +</p> + +<pre> + /dists/frozen -> etch/ + /dists/stable -> etch/ + /dists/testing -> etch/ + /dists/unstable -> etch/ +</pre> + +<p> +so that they work when your sources.list has an entry like +</p> + +<pre> + deb cdrom:[<name as on cd label>]/ unstable main [...] +</pre> + +<p> +. +</p> + +<p> +The fact these symlinks are present does <em>not</em> mean the image is +`unstable' or `testing' or anything. Read the CD label in +<code>/.disk/info</code> to find out which Debian version it contains. This +information is also present in <code>/README.txt</code> on the CD. +</p> + +<p> +Read <code><a +href="http://www.debian.org/releases/">http://www.debian.org/releases/</a></code> +to find out what the current `stable' and `testing' releases are. +</p> + +<hr> + +<h2><a name="s-remoteinstall"></a>2.6 Can I get and install Debian directly from a remote Internet site?</h2> + +<p> +Yes. You can boot the Debian installation system from a set of files you can +download from our FTP site and its mirrors. +</p> + +<p> +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 <code><a +href="http://www.debian.org/CD/netinst/">http://www.debian.org/CD/netinst/</a></code>. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-alternativebootinstaller"></a>2.7 Are there any alternative strategies for booting the system installer?</h2> + +<p> +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 <code><a +href="http://www.debian.org/releases/stable/installmanual">Debian GNU/Linux +Installation Guide</a></code> for more information. +</p> + +<hr> + +<p> +[ <a href="ch-basic_defs.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ 2 ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-choosing.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-getting.html b/includes/etch/common/doc/FAQ/html/ch-getting.html index 568d808..568d808 120000 --- a/includes/sid/common/doc/FAQ/html/ch-getting.html +++ b/includes/etch/common/doc/FAQ/html/ch-getting.html diff --git a/includes/etch/common/doc/FAQ/html/ch-kernel.en.html b/includes/etch/common/doc/FAQ/html/ch-kernel.en.html new file mode 100644 index 0000000..58781c9 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-kernel.en.html @@ -0,0 +1,389 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Debian and the kernel</title> + +<link href="index.en.html" rel="start"> +<link href="ch-uptodate.en.html" rel="prev"> +<link href="ch-customizing.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-kernel"></a></p> +<hr> + +<p> +[ <a href="ch-uptodate.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ 10 ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-customizing.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 10 - Debian and the kernel +</h1> + +<hr> + +<h2><a name="s-non-debian-kernel"></a>10.1 Can I install and compile a kernel without some Debian-specific tweaking?</h2> + +<p> +Yes. +</p> + +<p> +There's only one common catch: the Debian C libraries are built with the most +recent <em>stable</em> releases of the <strong>kernel</strong> headers. If you +happen to need to compile a program with kernel headers newer than the ones +from the stable branch, then you should either upgrade the package containing +the headers (<code>libc6-dev</code>), or use the new headers from an unpacked +tree of the newer kernel. That is, if the kernel sources are in +<code>/usr/src/linux</code>, then you should add +<samp>-I/usr/src/linux/include/</samp> to your command line when compiling. +</p> + +<hr> + +<h2><a name="s-customkernel"></a>10.2 What tools does Debian provide to build custom kernels?</h2> + +<p> +Users who wish to (or must) build a custom kernel are encouraged to download +the package <code>kernel-package</code>. This package contains the script to +build the kernel package, and provides the capability to create a Debian +<code>linux-image-<var>version</var></code> package just by running the command +</p> + +<pre> + make-kpkg --initrd kernel_image +</pre> + +<p> +in the top-level kernel source directory. Help is available by executing the +command +</p> + +<pre> + make-kpkg --help +</pre> + +<p> +and through the manual page <code>make-kpkg(1)</code>. +</p> + +<p> +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 +<code>linux-source-<var>version</var></code> package is available (where +<var>version</var> stands for the kernel version). +</p> + +<p> +Detailed instructions for using the <code>kernel-package</code> package are +given in the file <code>/usr/share/doc/kernel-package/README.gz</code>. +</p> + +<hr> + +<h2><a name="s-custombootdisk"></a>10.3 How can I make a custom boot floppy?</h2> + +<p> +This task is greatly aided by the Debian package <code>boot-floppies</code>, +normally found in the <samp>admin</samp> section of the Debian FTP archive. +Shell scripts in this package produce boot floppies in the +<samp>SYSLINUX</samp> format. These are <samp>MS-DOS</samp> 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 +<code>syslinux.cfg</code> file on the floppy). Other scripts in this package +produce emergency root disks and can even reproduce the base disks. +</p> + +<p> +You will find more information about this in the +<code>/usr/share/doc/boot-floppies/README</code> file after installing the +<code>boot-floppies</code> package. +</p> + +<hr> + +<h2><a name="s-modules"></a>10.4 What special provisions does Debian provide to deal with modules?</h2> + +<p> +Debian's <code>modconf</code> package provides a shell script +(<code>/usr/sbin/modconf</code>) 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 +<code>/etc/modules.conf</code> (which lists aliases, and other arguments that +must be used in conjunction with various modules) through files in +<code>/etc/modutils/</code>, and <code>/etc/modules</code> (which lists the +modules that must be loaded at boot time). +</p> + +<p> +Like the (new) <code>Configure.help</code> files that are now available to +support the construction of custom kernels, the <code>modconf</code> package +comes with a series of help files (in <code>/usr/lib/modules_help/</code>) +which provide detailed information on appropriate arguments for each of the +modules. +</p> + +<hr> + +<h2><a name="s-removeoldkernel"></a>10.5 Can I safely de-install an old kernel package, and if so, how?</h2> + +<p> +Yes. The <code>linux-image-<var>NNN</var>.prerm</code> 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: +</p> + +<pre> + dpkg --purge linux-image-<var>NNN</var> +</pre> + +<p> +(replace <var>NNN</var> with your kernel version and revision number, of +course) +</p> + +<hr> + +<p> +[ <a href="ch-uptodate.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ 10 ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-customizing.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-kernel.html b/includes/etch/common/doc/FAQ/html/ch-kernel.html index 125039f..125039f 120000 --- a/includes/sid/common/doc/FAQ/html/ch-kernel.html +++ b/includes/etch/common/doc/FAQ/html/ch-kernel.html diff --git a/includes/etch/common/doc/FAQ/html/ch-nexttime.en.html b/includes/etch/common/doc/FAQ/html/ch-nexttime.en.html new file mode 100644 index 0000000..cd6c875 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-nexttime.en.html @@ -0,0 +1,377 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Changes expected in the next major release of Debian</title> + +<link href="index.en.html" rel="start"> +<link href="ch-redistrib.en.html" rel="prev"> +<link href="ch-faqinfo.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-nexttime"></a></p> +<hr> + +<p> +[ <a href="ch-redistrib.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ 15 ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-faqinfo.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 15 - Changes expected in the next major release of Debian +</h1> + +<hr> + +<h2><a name="s-i18n"></a>15.1 Extended support for non-English users</h2> + +<p> +Debian already has very good support for non-English users, see <a +href="ch-software.en.html#s-nonenglish">How does Debian support non-English +languages?, Section 5.9</a>. +</p> + +<p> +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. +</p> + +<p> +The GNU Translation Project <code><a +href="ftp://ftp.gnu.org/pub/gnu/ABOUT-NLS">ftp://ftp.gnu.org/pub/gnu/ABOUT-NLS</a></code> +works on internationalizing the GNU programs. +</p> + +<p> +Specifically for Debian lenny, we're working on things like the following: +</p> +<ul> +<li> +<p> +I18n support in all debconf-using packages: Packages using the Debian +configuration management must allow for translation of all messages displayed +to the user during package configuration. +</p> +</li> +</ul> +<ul> +<li> +<p> +I18n support for package descriptions: Update package management frontends to +use the translated descriptions of packages. +</p> +</li> +</ul> +<ul> +<li> +<p> +UTF-8 debian/changelog and debian/control. This way, e.g. names of people +from asian countries can get typeset the right way in changelogs. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-dependencybasedboot"></a>15.2 Faster booting: Dependency based boot sequence</h2> + +<p> +Work is being done on <code><a +href="http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot">converting the +Debian boot sequence</a></code> to use dynamic and dependency based ordering +instead of hardcoded sequence numbers. Once that's finished, Debian systems +will boot much faster. +</p> + +<hr> + +<h2><a name="s-di"></a>15.3 Improvements in the Debian Installer</h2> + +<p> +Lots of work has been done on the Debian Installer, resulting in major +improvements. We'll mention just two of them here. +</p> + +<p> +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. +</p> + +<p> +The debian-installer now includes experimental support for installing Debian on +systems with Serial ATA RAID. +</p> + +<hr> + +<h2><a name="s-morearches"></a>15.4 More architectures</h2> + +<p> +Complete Debian system on other architectures such as <code><a +href="http://wiki.debian.org/ArmEabiPort">ARM EABI</a></code> (referred to as +"armel") (next to the old "arm") will likely get supported +with lenny. Support for <code><a +href="http://wiki.debian.org/SHPort">SuperH</a></code> 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 +<samp>sid</samp>. +</p> + +<hr> + +<h2><a name="s-morekernels"></a>15.5 More kernels</h2> + +<p> +In addition to Debian GNU/Hurd, Debian is being ported also to BSD kernels, +namely to <code><a +href="http://www.debian.org/ports/kfreebsd-gnu/">FreeBSD</a></code>. This port +runs on both AMD64 ("kfreebsd-amd64") and traditional Intel +("kfreebsd-i386"). +</p> + +<hr> + +<p> +[ <a href="ch-redistrib.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ 15 ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-faqinfo.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-nexttime.html b/includes/etch/common/doc/FAQ/html/ch-nexttime.html index da23d48..da23d48 120000 --- a/includes/sid/common/doc/FAQ/html/ch-nexttime.html +++ b/includes/etch/common/doc/FAQ/html/ch-nexttime.html diff --git a/includes/etch/common/doc/FAQ/html/ch-pkg_basics.en.html b/includes/etch/common/doc/FAQ/html/ch-pkg_basics.en.html new file mode 100644 index 0000000..72799b2 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-pkg_basics.en.html @@ -0,0 +1,1123 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Basics of the Debian package management system</title> + +<link href="index.en.html" rel="start"> +<link href="ch-ftparchives.en.html" rel="prev"> +<link href="ch-pkgtools.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-pkg_basics"></a></p> +<hr> + +<p> +[ <a href="ch-ftparchives.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ 7 ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-pkgtools.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 7 - Basics of the Debian package management system +</h1> + +<hr> + +<p> +This chapter touches on some lower level internals of Debian package +management. If you're interested mainly in <em>usage</em> of the relevant +tools, skip to chapters <a href="ch-pkgtools.en.html">The Debian package +management tools, Chapter 8</a> and/or <a href="ch-uptodate.en.html">Keeping +your Debian system up-to-date, Chapter 9</a>. +</p> + +<hr> + +<h2><a name="s-package"></a>7.1 What is a Debian package?</h2> + +<p> +Packages generally contain all of the files necessary to implement a set of +related commands or features. There are two types of Debian packages: +</p> +<ul> +<li> +<p> +<em>Binary packages</em>, which contain executables, configuration files, +man/info pages, copyright information, and other documentation. These packages +are distributed in a Debian-specific archive format (see <a +href="#s-deb-format">What is the format of a Debian binary package?, Section +7.2</a>); they are usually distinguished by having a '.deb' file extension. +Binary packages can be unpacked using the Debian utility <samp>dpkg</samp> +(possibly via a frontend like <code>aptitude</code>); details are given in its +manual page. +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>Source packages</em>, which consist of a <samp>.dsc</samp> file describing +the source package (including the names of the following files), a +<samp>.orig.tar.gz</samp> file that contains the original unmodified source in +gzip-compressed tar format and usually a <samp>.diff.gz</samp> file that +contains the Debian-specific changes to the original source. The utility +<samp>dpkg-source</samp> packs and unpacks Debian source archives; details are +provided in its manual page. (The program <code>apt-get</code> can get used a +frontend for <samp>dpkg-source</samp>.) +</p> +</li> +</ul> + +<p> +Installation of software by the package system uses "dependencies" +which are carefully designed by the package maintainers. These dependencies +are documented in the <samp>control</samp> file associated with each package. +For example, the package containing the GNU C compiler (<code>gcc</code>) +"depends" on the package <code>binutils</code> which includes the +linker and assembler. If a user attempts to install <code>gcc</code> without +having first installed <code>binutils</code>, the package management system +(dpkg) will send an error message that it also needs <code>binutils</code>, and +stop installing <code>gcc</code>. (However, this facility can be overridden by +the insistent user, see <code>dpkg(8)</code>.) See more in <a +href="#s-depends">What is meant by saying that a package <em>Depends</em>, +<em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> +or <em>Provides</em> another package?, Section 7.9</a> below. +</p> + +<p> +Debian's packaging tools can be used to: +</p> +<ul> +<li> +<p> +manipulate and manage packages or parts of packages, +</p> +</li> +</ul> +<ul> +<li> +<p> +administer local overrides of files in a package, +</p> +</li> +</ul> +<ul> +<li> +<p> +aid developers in the construction of package archives, and +</p> +</li> +</ul> +<ul> +<li> +<p> +aid users in the installation of packages which reside on a remote FTP site. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-deb-format"></a>7.2 What is the format of a Debian binary package?</h2> + +<p> +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 <samp>.deb</samp>. +</p> + +<p> +The internals of this Debian binary packages format are described in the +<code>deb(5)</code> manual page. This internal format is subject to change +(between major releases of Debian GNU/Linux), therefore please always use +<code>dpkg-deb(1)</code> if you need to do lowlevel manipulations on +<samp>.deb</samp> files. +</p> + +<hr> + +<h2><a name="s-pkgname"></a>7.3 Why are Debian package file names so long?</h2> + +<p> +The Debian binary package file names conform to the following convention: +<foo>_<VersionNumber>-<DebianRevisionNumber>_<DebianArchitecture>.deb +</p> + +<p> +Note that <samp>foo</samp> 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: +</p> +<ul> +<li> +<p> +inspect the "Packages" file in the directory where it was stored at a +Debian FTP archive site. This file contains a stanza describing each package; +the first field in each stanza is the formal package name. +</p> +</li> +</ul> +<ul> +<li> +<p> +use the command <samp>dpkg --info foo_VVV-RRR_AAA.deb</samp> (where VVV, RRR +and AAA are the version, revision and architecture of the package in question, +respectively). This displays, among other things, the package name +corresponding to the archive file being unpacked. +</p> +</li> +</ul> + +<p> +The <samp>VVV</samp> 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". +</p> + +<p> +The <samp>RRR</samp> 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 (<samp>debian/rules</samp>), the Debian control file +(<samp>debian/control</samp>), the installation or removal scripts +(<samp>debian/p*</samp>), or in the configuration files used with the package. +</p> + +<p> +The <samp>AAA</samp> component identifies the processor for which the package +was built. This is commonly <samp>i386</samp>, which refers to chips +compatible to Intel's 386 or later versions. For other possibilities review +Debian's FTP directory structure at <a +href="ch-ftparchives.en.html#s-dirtree">What are all those directories at the +Debian FTP archives?, Section 6.7</a>. For details, see the description of +"Debian architecture" in the manual page +<code>dpkg-architecture(1)</code>. +</p> + +<hr> + +<h2><a name="s-controlfile"></a>7.4 What is a Debian control file?</h2> + +<p> +Specifics regarding the contents of a Debian control file are provided in the +Debian Policy Manual, section 5, see <a +href="ch-support.en.html#s-debiandocs">What other documentation exists on and +for a Debian system?, Section 12.1</a>. +</p> + +<p> +Briefly, a sample control file is shown below for the Debian package hello: +</p> + +<pre> + 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). +</pre> + +<p> +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. +</p> + +<p> +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 <a href="#s-pkgname">Why are Debian package file names so long?, +Section 7.3</a>. +</p> + +<p> +The Architecture field specifies the chip for which this particular binary was +compiled. +</p> + +<p> +The Depends field gives a list of packages that have to be installed in order +to install this package successfully. +</p> + +<p> +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. +</p> + +<p> +The Section line gives the "section" where this Debian package is +stored at the Debian FTP sites. +</p> + +<p> +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 <a +href="#s-priority">What is an <em>Essential</em>, <em>Required</em>, +<em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> +package?, Section 7.7</a>. +</p> + +<p> +The Maintainer field gives the e-mail address of the person who is currently +responsible for maintaining this package. +</p> + +<p> +The Description field gives a brief summary of the package's features. +</p> + +<p> +For more information about all possible fields a package can have, please see +the Debian Policy Manual, section 5., "Control files and their +fields". +</p> + +<hr> + +<h2><a name="s-conffile"></a>7.5 What is a Debian conffile?</h2> + +<p> +Conffiles is a list of configuration files (usually placed in +<samp>/etc</samp>) 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. +</p> + +<p> +To determine exactly which files are preserved during an upgrade, run: +</p> + +<pre> + dpkg --status package +</pre> + +<p> +And look under "Conffiles:". +</p> + +<hr> + +<h2><a name="s-maintscripts"></a>7.6 What is a Debian preinst, postinst, prerm, and postrm script?</h2> + +<p> +These files are executable scripts which are automatically run before or after +a package is installed. Along with a file named <samp>control</samp>, all of +these files are part of the "control" section of a Debian archive +file. +</p> + +<p> +The individual files are: +</p> +<dl> +<dt>preinst</dt> +<dd> +<p> +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). +</p> +</dd> +</dl> +<dl> +<dt>postinst</dt> +<dd> +<p> +This script typically completes any required configuration of the package +<samp>foo</samp> once <samp>foo</samp> 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. +</p> +</dd> +</dl> +<dl> +<dt>prerm</dt> +<dd> +<p> +This script typically stops any daemons which are associated with a package. +It is executed before the removal of files associated with the package. +</p> +</dd> +</dl> +<dl> +<dt>postrm</dt> +<dd> +<p> +This script typically modifies links or other files associated with +<samp>foo</samp>, and/or removes files created by the package. (Also see <a +href="#s-virtual">What is a Virtual Package?, Section 7.8</a>.) +</p> +</dd> +</dl> + +<p> +Currently all of the control files can be found in directory +<samp>/var/lib/dpkg/info</samp>. The files relevant to package +<samp>foo</samp> begin with the name "foo" and have file extensions +of "preinst", "postinst", etc., as appropriate. The file +<samp>foo.list</samp> in that directory lists all of the files that were +installed with the package <samp>foo</samp>. (Note that the location of these +files is a dpkg internal; you should not rely on it.) +</p> + +<hr> + +<h2><a name="s-priority"></a>7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?</h2> + +<p> +Each Debian package is assigned a <em>priority</em> by the distribution +maintainers, as an aid to the package management system. The priorities are: +</p> +<ul> +<li> +<p> +<strong>Required</strong>: packages that are necessary for the proper +functioning of the system. +</p> + +<p> +This includes all tools that are necessary to repair system defects. You must +not remove these packages or your system may become totally broken and you may +probably not even be able to use dpkg to put things back. Systems with only +the Required packages are probably unusable, but they do have enough +functionality to allow the sysadmin to boot and install more software. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>Important</strong> packages should be found on any Unix-like system. +</p> + +<p> +Other packages which the system will not run well or be usable without will be +here. This does <em>NOT</em> include Emacs or X or TeX or any other large +applications. These packages only constitute the bare infrastructure. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>Standard</strong> packages are standard on any Linux system, including +a reasonably small but not too limited character-mode system. Tools are +included to be able to browse the web (using w3m), send e-mail (with mutt) and +download files from FTP servers. +</p> + +<p> +This is what will install by default if users do not select anything else. It +does not include many large applications, but it does include the Python +interpreter and some server software like OpenSSH (for remote administration), +Exim (for mail delivery, although it can be configured for local delivery +only), an identd server (pidentd) and the RPC portmapper +(<samp>portmap</samp>). It also includes some common generic documentation +that most users will find helpful. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>Optional</strong> packages include all those that you might reasonably +want to install if you did not know what it was, or do not have specialized +requirements. +</p> + +<p> +This includes X, a full TeX distribution, and lots of applications. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>Extra</strong>: packages that either conflict with others with higher +priorities, are only likely to be useful if you already know what they are, or +have specialized requirements that make them unsuitable for +"Optional". +</p> +</li> +</ul> + +<p> +If you do a default Debian installation all the packages of priority +<strong>Standard</strong> or higher will be installed in your system. If you +select pre-defined tasks you will get lower priority packages too. +</p> + +<p> +Additionally, some packages are marked as <strong>Essential</strong> since they +are absolutely necessary for the proper functioning of the system. The package +management tools will refuse to remove these. +</p> + +<hr> + +<h2><a name="s-virtual"></a>7.8 What is a Virtual Package?</h2> + +<p> +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 <samp>tin</samp> and <samp>trn</samp> 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 <samp>news-reader</samp>. +</p> + +<p> +Similarly, <samp>smail</samp> and <samp>sendmail</samp> 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 +<samp>mail-transport-agent</samp> will be satisfied by the existence of this +virtual package. +</p> + +<p> +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 +<samp>update-alternatives</samp>, and is described further in <a +href="ch-customizing.en.html#s-diverse">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</a>. +</p> + +<hr> + +<h2><a name="s-depends"></a>7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?</h2> + +<p> +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: +</p> +<ul> +<li> +<p> +Package A <em>depends</em> on Package B if B absolutely must be installed in +order to run A. In some cases, A depends not only on B, but on a version of B. +In this case, the version dependency is usually a lower limit, in the sense +that A depends on any version of B more recent than some specified version. +</p> +</li> +</ul> +<ul> +<li> +<p> +Package A <em>recommends</em> Package B, if the package maintainer judges that +most users would not want A without also having the functionality provided by +B. +</p> +</li> +</ul> +<ul> +<li> +<p> +Package A <em>suggests</em> Package B if B contains files that are related to +(and usually enhance) the functionality of A. +</p> +</li> +</ul> +<ul> +<li> +<p> +Package A <em>conflicts</em> with Package B when A will not operate if B is +installed on the system. Most often, conflicts are cases where A contains +files which are an improvement over those in B. "Conflicts" are +often combined with "replaces". +</p> +</li> +</ul> +<ul> +<li> +<p> +Package A <em>replaces</em> Package B when files installed by B are removed and +(in some cases) over-written by files in A. +</p> +</li> +</ul> +<ul> +<li> +<p> +Package A <em>provides</em> Package B when all of the files and functionality +of B are incorporated into A. This mechanism provides a way for users with +constrained disk space to get only that part of package A which they really +need. +</p> +</li> +</ul> + +<p> +More detailed information on the use of each these terms can be found in the +Policy manual. +</p> + +<hr> + +<h2><a name="s-pre-depends"></a>7.10 What is meant by Pre-Depends?</h2> + +<p> +"Pre-Depends" is a special dependency. In the case of most packages, +<samp>dpkg</samp> will unpack its archive file (i.e., its <samp>.deb</samp> +file) independently of whether or not the files on which it depends exist on +the system. Simplistically, unpacking means that <samp>dpkg</samp> will +extract the files from the archive file that were meant to be installed on your +file system, and put them in place. If those packages <em>depend</em> on the +existence of some other packages on your system, <samp>dpkg</samp> will refuse +to complete the installation (by executing its "configure" action) +until the other packages are installed. +</p> + +<p> +However, for some packages, <samp>dpkg</samp> 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 +<samp>a.out</samp> format to <samp>ELF</samp> format, where the <em>order</em> +in which packages were unpacked was critical. There are other large upgrade +situations where this method is useful, e.g. the packages with the required +priority and their LibC dependency. +</p> + +<p> +As before, more detailed information about this can be found in the Policy +manual. +</p> + +<hr> + +<h2><a name="s-pkgstatus"></a>7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?</h2> + +<p> +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 +<samp>dselect</samp>, or by the user's direct invocations of +<samp>dpkg</samp>). +</p> + +<p> +Their meanings are: +</p> +<ul> +<li> +<p> +unknown - the user has never indicated whether he wants the package +</p> +</li> +</ul> +<ul> +<li> +<p> +install - the user wants the package installed or upgraded +</p> +</li> +</ul> +<ul> +<li> +<p> +remove - the user wants the package removed, but does not want to remove any +existing configuration files. +</p> +</li> +</ul> +<ul> +<li> +<p> +purge - the user wants the package to be removed completely, including its +configuration files. +</p> +</li> +</ul> +<ul> +<li> +<p> +hold - the user wants this package not to be processed, i.e., he wants to keep +the current version with the current status whatever that is. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-puttingonhold"></a>7.12 How do I put a package on hold?</h2> + +<p> +There are three ways of holding back packages, with dpkg, aptitude or with +dselect. +</p> + +<p> +With dpkg, you have to export the list of package selections, with: +</p> + +<pre> + dpkg --get-selections \* > selections.txt +</pre> + +<p> +Then edit the resulting file <code>selections.txt</code>, change the line +containing the package you wish to hold, e.g. <code>libc6</code>, from this: +</p> + +<pre> + libc6 install +</pre> + +<p> +to this: +</p> + +<pre> + libc6 hold +</pre> + +<p> +Save the file, and reload it into dpkg database with: +</p> + +<pre> + dpkg --set-selections < selections.txt +</pre> + +<p> +With aptitude, you can hold a package using +</p> + +<pre> + aptitude hold package_name +</pre> + +<p> +and remove the hold with +</p> + +<pre> + aptitude unhold package_name +</pre> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-sourcepkgs"></a>7.13 How do I install a source package?</h2> + +<p> +Debian source packages can't actually be "installed", they are just +unpacked in whatever directory you want to build the binary packages they +produce. +</p> + +<p> +Source packages are distributed on most of the same mirrors where you can +obtain the binary packages. If you set up your APT's +<code>sources.list(5)</code> to include the appropriate "deb-src" +lines, you'll be able to easily download any source packages by running +</p> + +<pre> + apt-get source foo +</pre> + +<p> +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 +</p> + +<pre> + apt-get build-dep foo +</pre> + +<p> +before building the source. +</p> + +<hr> + +<h2><a name="s-sourcebuild"></a>7.14 How do I build binary packages from a source package?</h2> + +<p> +The preferred way to do this is by using various wrapper tools. We'll show how +it's done using the <samp>devscripts</samp> tools. Install this package if you +haven't done so already. +</p> + +<p> +Now, first get the source package: +</p> + +<pre> + apt-get source foo +</pre> + +<p> +and change to the source tree: +</p> + +<pre> + cd foo-* +</pre> + +<p> +Then install needed build-dependencies (if any): +</p> + +<pre> + sudo apt-get build-dep foo +</pre> + +<p> +Then create a dedicated version of your own build (so that you won't get +confused later when Debian itself releases a new version) +</p> + +<pre> + dch -l local 'Blah blah blah' +</pre> + +<p> +And finally build your package +</p> + +<pre> + debuild -us -uc +</pre> + +<p> +If everything worked out fine, you should now be able to install your package +by running +</p> + +<pre> + sudo dpkg -i ../*.deb +</pre> + +<p> +If you prefer to do things manually, and don't want to use +<samp>devscripts</samp>, follow this procedure: +</p> + +<p> +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). +</p> + +<p> +Once you have them (<a href="#s-sourcepkgs">How do I install a source package?, +Section 7.13</a>), if you have the <code>dpkg-dev</code> package installed, the +following command: +</p> + +<pre> + dpkg-source -x foo_version-revision.dsc +</pre> + +<p> +will extract the package into a directory called <samp>foo-version</samp>. +</p> + +<p> +If you want just to compile the package, you may cd into +<samp>foo-version</samp> directory and issue the command +</p> + +<pre> + dpkg-buildpackage -rfakeroot -b +</pre> + +<p> +to build the package (note that this also requires the <code>fakeroot</code> +package), and then +</p> + +<pre> + dpkg -i ../foo_version-revision_arch.deb +</pre> + +<p> +to install the newly-built package(s). +</p> + +<hr> + +<h2><a name="s-creatingdebs"></a>7.15 How do I create Debian packages myself?</h2> + +<p> +For a more detailed description on this, read the New Maintainers' Guide, +available in the <code>maint-guide</code> package, or at <code><a +href="http://www.debian.org/doc/devel-manuals#maint-guide">http://www.debian.org/doc/devel-manuals#maint-guide</a></code>. +</p> + +<hr> + +<p> +[ <a href="ch-ftparchives.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ 7 ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-pkgtools.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-pkg_basics.html b/includes/etch/common/doc/FAQ/html/ch-pkg_basics.html index 98c97fe..98c97fe 120000 --- a/includes/sid/common/doc/FAQ/html/ch-pkg_basics.html +++ b/includes/etch/common/doc/FAQ/html/ch-pkg_basics.html diff --git a/includes/etch/common/doc/FAQ/html/ch-pkgtools.en.html b/includes/etch/common/doc/FAQ/html/ch-pkgtools.en.html new file mode 100644 index 0000000..391e656 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-pkgtools.en.html @@ -0,0 +1,1199 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - The Debian package management tools</title> + +<link href="index.en.html" rel="start"> +<link href="ch-pkg_basics.en.html" rel="prev"> +<link href="ch-uptodate.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-pkgtools"></a></p> +<hr> + +<p> +[ <a href="ch-pkg_basics.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ 8 ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-uptodate.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 8 - The Debian package management tools +</h1> + +<hr> + +<h2><a name="s-pkgprogs"></a>8.1 What programs does Debian provide for managing its packages?</h2> + +<p> +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. +</p> + +<p> +It is important to understand that the higher level package management tools +such as <code>aptitude</code> or <code>dselect</code> rely on <code>apt</code> +which, itself, relies on <code>dpkg</code> to manage the packages in the +system. +</p> + +<p> +See the <code><a href="http://www.debian.org/doc/manuals/apt-howto/">APT +HOWTO</a></code> for more information about the Debian package management +utilities. This document is available in various languages and formats, see +<code><a href="http://www.debian.org/doc/user-manuals#apt-howto">the APT HOWTO +entry on the DDP Users' Manuals overview</a></code>. +</p> + +<hr> + +<h3><a name="s-dpkg"></a>8.1.1 dpkg</h3> + +<p> +This is the main package management program. <code>dpkg</code> can be invoked +with many options. Some common uses are: +</p> +<ul> +<li> +<p> +Find out all the options: <samp>dpkg --help</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Print out the control file (and other information) for a specified package: +<samp>dpkg --info foo_VVV-RRR.deb</samp> +</p> +</li> +</ul> +<ul> +<li> +<p> +Install a package (including unpacking and configuring) onto the file system of +the hard disk: <samp>dpkg --install foo_VVV-RRR.deb</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Unpack (but do not configure) a Debian archive into the file system of the hard +disk: <samp>dpkg --unpack foo_VVV-RRR.deb</samp>. Note that this operation +does <em>not</em> necessarily leave the package in a usable state; some files +may need further customization to run properly. This command removes any +already-installed version of the program and runs the preinst (see <a +href="ch-pkg_basics.en.html#s-maintscripts">What is a Debian preinst, postinst, +prerm, and postrm script?, Section 7.6</a>) script associated with the package. +</p> +</li> +</ul> +<ul> +<li> +<p> +Configure a package that already has been unpacked: <samp>dpkg --configure +foo</samp>. Among other things, this action runs the postinst (see <a +href="ch-pkg_basics.en.html#s-maintscripts">What is a Debian preinst, postinst, +prerm, and postrm script?, Section 7.6</a>) script associated with the package. +It also updates the files listed in the <samp>conffiles</samp> for this +package. Notice that the 'configure' operation takes as its argument a package +name (e.g., foo), <em>not</em> the name of a Debian archive file (e.g., +foo_VVV-RRR.deb). +</p> +</li> +</ul> +<ul> +<li> +<p> +Extract a single file named "blurf" (or a group of files named +"blurf*" from a Debian archive: <samp>dpkg --fsys-tarfile +foo_VVV-RRR.deb | tar -xf - blurf*</samp> +</p> +</li> +</ul> +<ul> +<li> +<p> +Remove a package (but not its configuration files): <samp>dpkg --remove +foo</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Remove a package (including its configuration files): <samp>dpkg --purge +foo</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +List the installation status of packages containing the string (or regular +expression) "foo*": <samp>dpkg --list 'foo*'</samp>. +</p> +</li> +</ul> + +<hr> + +<h3><a name="s-apt-get"></a>8.1.2 APT</h3> + +<p> +APT is the <em>Advanced Package Tool</em> and provides the <code>apt-get</code> +program. <code>apt-get</code> provides a simple way to retrieve and install +packages from multiple sources using the command line. Unlike +<code>dpkg</code>, <code>apt-get</code> does not understand .deb files, it +works with the packages proper name and can only install .deb archives from a +source specified in <code>/etc/apt/sources.list</code>. <code>apt-get</code> +will call <code>dpkg</code> directly after downloading the .deb archives[<a +href="footnotes.en.html#f5" name="fr5">5</a>] from the configured sources. +</p> + +<p> +Some common ways to use <code>apt-get</code> are: +</p> +<ul> +<li> +<p> +To update the list of package known by your system, you can run: +</p> + +<pre> + apt-get update +</pre> + +<p> +(you should execute this regularly to update your package lists) +</p> +</li> +</ul> +<ul> +<li> +<p> +To upgrade all the packages on your system (without installing extra packages +or removing packages), run: +</p> + +<pre> + apt-get upgrade +</pre> +</li> +</ul> +<ul> +<li> +<p> +To install the <var>foo</var> package and all its dependencies, run: +</p> + +<pre> + apt-get install foo +</pre> +</li> +</ul> +<ul> +<li> +<p> +To remove the foo package from your system, run: +</p> + +<pre> + apt-get remove foo +</pre> +</li> +</ul> +<ul> +<li> +<p> +To remove the foo package and its configuration files from your system, run: +</p> + +<pre> + apt-get --purge remove foo +</pre> +</li> +</ul> +<ul> +<li> +<p> +To upgrade all the packages on your system, and, if needed for a package +upgrade, installing extra packages or removing packages, run: +</p> + +<pre> + apt-get dist-upgrade +</pre> + +<p> +(The command <samp>upgrade</samp> keeps a package at its installed obsolete +version if upgrading would need an extra package to be installed, for a new +dependency to be satisfied. The <samp>dist-upgrade</samp> command is less +conservative.) +</p> +</li> +</ul> + +<p> +Note that you must be logged in as root to perform any commands that modify the +system packages. +</p> + +<p> +The apt tool suite also includes the <code>apt-cache</code> 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 <code>apt-cache</code> are: +</p> +<ul> +<li> +<p> +To find packages whose description contain <var>word</var>: +</p> + +<pre> + apt-cache search <var>word</var> +</pre> +</li> +</ul> +<ul> +<li> +<p> +To print the detailed information of a package: +</p> + +<pre> + apt-cache show <var>package</var> +</pre> +</li> +</ul> +<ul> +<li> +<p> +To print the packages a given package depends on: +</p> + +<pre> + apt-cache depends <var>package</var> +</pre> +</li> +</ul> +<ul> +<li> +<p> +To print detailed information of the versions available for a package and the +packages that reverse-depends on it: +</p> + +<pre> + apt-cache showpkg <var>package</var> +</pre> +</li> +</ul> + +<p> +For more information, install the <code>apt</code> package and read +<code>apt-get(8)</code>, <code>sources.list(5)</code> and install the +<code>apt-doc</code> package and read +<code>/usr/share/doc/apt-doc/guide.html/index.html</code>. +</p> + +<hr> + +<h3><a name="s-aptitude"></a>8.1.3 aptitude</h3> + +<p> +<code>aptitude</code> is a package manager for Debian GNU/Linux systems that +provides a frontend to the apt package management infrastructure. +<code>aptitude</code> is a text-based interface using the curses library, it +can be used to perform management tasks in a fast and easy way. +</p> + +<p> +<code>aptitude</code> provides the functionality of <code>dselect</code> and +<code>apt-get</code>, as well as many additional features not found in either +program: +</p> +<ul> +<li> +<p> +<code>aptitude</code> offers access to all versions of a package. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> logs all its actions in <code>/var/log/aptitude</code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> makes it easy to keep track of obsolete software by +listing it under "Obsolete and Locally Created Packages". +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> includes a fairly powerful system for searching +particular packages and limiting the package display. Users familiar with +<code>mutt</code> will pick up quickly, as <code>mutt</code> was the +inspiration for the expression syntax. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> tracks which packages have been installed due to +dependencies and removes them automatically when the packages that needed them +are removed from the system. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> can automatically install <em>Recommended:</em> +packages[<a href="footnotes.en.html#f6" name="fr6">6</a>]. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> can be used to install the predefined tasks available. +For more information see <a href="#s-tasksel">tasksel, Section 8.1.5</a>. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> in full screen mode has <code>su</code> functionality +embedded and can be run by a normal user. It will call <code>su</code> (and +ask for the root password, if any) when you really need administrative +privileges +</p> +</li> +</ul> + +<p> +You can use <code>aptitude</code> through a visual interface (simply run +<samp>aptitude</samp>) or directly from the command line. The command line +syntax used is very similar to the one used in <code>apt-get</code>. For +example, to install the <var>foo</var> package, you can run <samp>aptitude +install <var>foo</var></samp>. +</p> + +<p> +Note that <code>aptitude</code> is the preferred program for package management +from console both for package installations and package or system upgrades. +</p> + +<p> +For more informations, read the manual page <code>aptitude(8)</code> and +install the <code>aptitude-doc</code> package. +</p> + +<hr> + +<h3><a name="s-synaptic"></a>8.1.4 synaptic</h3> + +<p> +<code>synaptic</code> 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 <code><a href="http://www.nongnu.org/synaptic/">Synaptic +Website</a></code> for more information. +</p> + +<hr> + +<h3><a name="s-tasksel"></a>8.1.5 tasksel</h3> + +<p> +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 <samp>tasks</samp>, a task is a collection of several individual Debian +packages all related to a specific activity. Tasks can be installed through +the <code>tasksel</code> program or through <code>aptitude</code>. +</p> + +<p> +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 (<samp>gnome-desktop</samp> 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 +<samp>laptop</samp> task will be installed too. +</p> + +<hr> + +<h3><a name="s-dpkg-extra"></a>8.1.6 Other package management tools</h3> + +<hr> + +<h4><a name="s-dselect"></a>8.1.6.1 dselect</h4> + +<p> +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 <code>aptitude</code> instead. Some users might feel more comfortable +using <code>aptitude</code> and it is also recommended over +<code>dselect</code> for large-scale upgrades. For more information on +<code>aptitude</code> please see <a href="#s-aptitude">aptitude, Section +8.1.3</a>. +</p> + +<p> +<code>dselect</code> can: +</p> +<ul> +<li> +<p> +guide the user as he/she chooses among packages to install or remove, ensuring +that no packages are installed that conflict with one another, and that all +packages required to make each package work properly are installed; +</p> +</li> +</ul> +<ul> +<li> +<p> +warn the user about inconsistencies or incompatibilities in their selections; +</p> +</li> +</ul> +<ul> +<li> +<p> +determine the order in which the packages must be installed; +</p> +</li> +</ul> +<ul> +<li> +<p> +automatically perform the installation or removal; and +</p> +</li> +</ul> +<ul> +<li> +<p> +guide the user through whatever configuration process are required for each +package. +</p> +</li> +</ul> + +<p> +<code>dselect</code> begins by presenting the user with a menu of 7 items, each +of which is a specific action. The user can select one of the actions by using +the arrow keys to move the highlighter bar, then pressing the +<em><enter></em> key to select the highlighted action. +</p> + +<p> +What the user sees next depends on the action he selected. If he selects any +option but <samp>Access</samp> or <samp>Select</samp>, then +<code>dselect</code> will simply proceed to execute the specified action: e.g., +if the user selected the action <samp>Remove</samp>, then dselect would proceed +to remove all of the files selected for removal when the user last chose the +<samp>Select</samp> action. +</p> + +<p> +Both the <samp>Access</samp> menu item and the <samp>Select</samp> 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. +</p> + +<p> +Extensive on-line help is available, use the '?' key to get to a help screen +at any time. +</p> + +<p> +The order in which the actions are presented in the first <code>dselect</code> +menu represents the order in which a user would normally choose +<code>dselect</code> 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). +</p> +<ul> +<li> +<p> +Begin by choosing an <strong>Access Method</strong>. This is the method by +which the user plans on accessing Debian packages; e.g., some users have Debian +packages available on CD-ROM, while others plan to fetch them using anonymous +FTP. The selected "Access Method" is stored after +<code>dselect</code> exits, so if it does not change, then this option need not +be invoked again. +</p> +</li> +</ul> +<ul> +<li> +<p> +Then <strong>Update</strong> the list of available packages. To do this, +<code>dselect</code> reads the file "Packages.gz" which should be +included in the top level of the directory where the Debian packages to be +installed are stored. (But if it is not there, <code>dselect</code> will offer +to make it for you.) +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>Select</strong> specific packages for installation on his system. +After choosing this menu item, the user is first presented with a full screen +of help (unless the `--expert' command line option was used). Once the user +exits the Help screen, he sees the split-screen menu for choosing packages to +install (or remove). +</p> + +<p> +The top part of the screen is a relatively narrow window into the list of +Debian's 18200 packages; the bottom part of the screen contains description of +the package or group of packages which are highlighted above. +</p> + +<p> +One can specify which packages should be operated on by highlighting a package +name or the label for a group of packages. After that, you can select +packages: +</p> +<dl> +<dt>to be installed:</dt> +<dd> +<p> +This is accomplished by pressing the `+' key. +</p> +</dd> +</dl> +<dl> +<dt>to be deleted:</dt> +<dd> +<p> +Packages can be deleted two ways: +</p> +<ul> +<li> +<p> +removed: this removes most of the files associated with the package, but +preserves the files listed as configuration files (see <a +href="ch-pkg_basics.en.html#s-conffile">What is a Debian conffile?, Section +7.5</a>) and package configuration information. This is done by pressing the +`-' key. +</p> +</li> +</ul> +<ul> +<li> +<p> +purged: this removes <em>every</em> file that is part of the package. This is +done by pressing the `_' key. +</p> +</li> +</ul> + +<p> +Note that it's not possible to remove "All Packages". If you try +that, your system will instead be reduced to the initial installed base +packages. +</p> +</dd> +</dl> +<dl> +<dt>to be put "on hold"</dt> +<dd> +<p> +This is done by pressing `=', and it effectively tells <code>dselect</code> not +to upgrade a package even if the version currently installed on your system is +not as recent as the version that is available in the Debian repository you are +using (this was specified when you set the <strong>Access Method</strong>, and +acquired when you used <strong>Update</strong>). +</p> + +<p> +Just like you can put a package on hold, you can reverse such setting by +pressing `:'. That tells <code>dselect</code> that the package(s) may be +upgraded if a newer version is available. This is the default setting. +</p> +</dd> +</dl> + +<p> +You can select a different order in which the packages are presented, by using +the `o' key to cycle between various options for sorting the packages. The +default order is to present packages by Priority; within each priority, +packages are presented in order of the directory (a.k.a. section) of the +archive in which they are stored. Given this sort order, some packages in +section A (say) may be presented first, followed by some packages in section B, +followed by more packages (of lower priority) in section A. +</p> + +<p> +You can also expand meanings of the labels at the top of the screen, by using +the `v' (verbose) key. This action pushes much of the text that formerly fit +onto the display off to the right. To see it, press the right arrow; to scroll +back to the left, press the left arrow. +</p> + +<p> +If you select a package for installation or removal, e.g., +<code>foo.deb</code>, and that package depends on (or recommends) another +package, e.g., <code>blurf.deb</code>, then <code>dselect</code> will place the +you in a sub-screen of the main selection screen. There you can choose among +the related packages, accepting the suggested actions (to install or not), or +rejecting them. To do the latter, press Shift-D; to return to the former, +press Shift-U. In any case, you can save your selections and return to the +main selection screen by pressing Shift-Q. +</p> +</li> +</ul> +<ul> +<li> +<p> +Users returning to the main menu can then select the "Install" menu +item to unpack and configure the selected packages. Alternatively, users +wishing to remove files can choose the "Remove" menu item. At any +point, users can choose "Quit" to exit dselect; users' selections are +preserved by <code>dselect</code>. +</p> +</li> +</ul> + +<hr> + +<h4><a name="s-dpkg-deb"></a>8.1.6.2 dpkg-deb</h4> + +<p> +This program manipulates Debian archive(<samp>.deb</samp>) files. Some common +uses are: +</p> +<ul> +<li> +<p> +Find out all the options: <samp>dpkg-deb --help</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Determine what files are contained in a Debian archive file: <samp>dpkg-deb +--contents foo_VVV-RRR.deb</samp>) +</p> +</li> +</ul> +<ul> +<li> +<p> +Extract the files contained in a named Debian archive into a user specified +directory: <samp>dpkg-deb --extract foo_VVV-RRR.deb tmp</samp> extracts each of +the files in <samp>foo_VVV-RRR.deb</samp> into the directory <samp>tmp/</samp>. +This is convenient for examining the contents of a package in a localized +directory, without installing the package into the root file system. +</p> +</li> +</ul> +<ul> +<li> +<p> +Extract the control information files from a package: <samp>dpkg-deb --control +foo_VVV-RRR.deb tmp</samp>. +</p> +</li> +</ul> + +<p> +Note that any packages that were merely unpacked using <samp>dpkg-deb +--extract</samp> will be incorrectly installed, you should use <samp>dpkg +--install</samp> instead. +</p> + +<p> +More information is given in the manual page <code>dpkg-deb(1)</code>. +</p> + +<hr> + +<h4><a name="s-dpkg-split"></a>8.1.6.3 dpkg-split</h4> + +<p> +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 <code>dpkg</code> package), since it calls the program +<samp>dpkg-deb</samp> to parse the debian package file into its component +records. +</p> + +<p> +For example, to split a big .deb file into N parts, +</p> +<ul> +<li> +<p> +Execute the command <samp>dpkg-split --split foo.deb</samp>. This will produce +N files each of approximately 460 KBytes long in the current directory. +</p> +</li> +</ul> +<ul> +<li> +<p> +Copy those N files to floppy disks. +</p> +</li> +</ul> +<ul> +<li> +<p> +Copy the contents of the floppy disks onto the hard disk of your choice on the +other machine. +</p> +</li> +</ul> +<ul> +<li> +<p> +Join those part-files together using <samp>dpkg-split --join +"foo*"</samp>. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-updaterunning"></a>8.2 Debian claims to be able to update a running program; how is this accomplished?</h2> + +<p> +The kernel (file system) in Debian GNU/Linux systems supports replacing files +even while they're being used. +</p> + +<p> +We also provide a program called <code>start-stop-daemon</code> 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. +</p> + +<hr> + +<h2><a name="s-whatpackages"></a>8.3 How can I tell what packages are already installed on a Debian system?</h2> + +<p> +To learn the status of all the packages installed on a Debian system, execute +the command +</p> + +<pre> + dpkg --list +</pre> + +<p> +This prints out a one-line summary for each package, giving a 2-letter status +symbol (explained in the header), the package name, the version which is +<em>installed</em>, and a brief description. +</p> + +<p> +To learn the status of packages whose names match the string any pattern +beginning with "foo" by executing the command: +</p> + +<pre> + dpkg --list 'foo*' +</pre> + +<p> +To get a more verbose report for a particular package, execute the command: +</p> + +<pre> + dpkg --status packagename +</pre> + +<hr> + +<h2><a name="s-listfiles"></a>8.4 How to display the files of a package installed?</h2> + +<p> +To list all the files provided by the installed package <samp>foo</samp> +execute the command +</p> + +<pre> + dpkg --listfiles foo +</pre> + +<p> +Note that the files created by the installation scripts aren't displayed. +</p> + +<hr> + +<h2><a name="s-filesearch"></a>8.5 How can I find out what package produced a particular file?</h2> + +<p> +To identify the package that produced the file named <samp>foo</samp> execute +either: +</p> +<ul> +<li> +<p> +<samp>dpkg --search filename</samp> +</p> + +<p> +This searches for <samp>filename</samp> in installed packages. (This is +(currently) equivalent to searching all of the files having the file extension +of <samp>.list</samp> in the directory <samp>/var/lib/dpkg/info/</samp>, and +adjusting the output to print the names of all the packages containing it, and +diversions.) +</p> + +<p> +A faster alternative to this is the <code>dlocate</code> tool. +</p> + +<pre> + dlocate -S filename +</pre> +</li> +</ul> +<ul> +<li> +<p> +<samp>zgrep foo Contents-ARCH.gz</samp> +</p> + +<p> +This searches for files which contain the substring <samp>foo</samp> in their +full path names. The files <samp>Contents-ARCH.gz</samp> (where ARCH +represents the wanted architecture) reside in the major package directories +(main, non-free, contrib) at a Debian FTP site (i.e. under +<samp>/debian/dists/etch</samp>). A <samp>Contents</samp> file refers only to +the packages in the subdirectory tree where it resides. Therefore, a user +might have to search more than one <samp>Contents</samp> files to find the +package containing the file <samp>foo</samp>. +</p> + +<p> +This method has the advantage over <samp>dpkg --search</samp> in that it will +find files in packages that are not currently installed on your system. +</p> +</li> +</ul> +<ul> +<li> +<p> +<samp>apt-file search <var>foo</var></samp> +</p> + +<p> +If you install the <code>apt-file</code>, similar to the above, it searches +files which contain the substring or regular expression <samp>foo</samp> in +their full path names. The advantage over the sample above is that there is no +need to retrieve the <samp>Contents-ARCH.gz</samp> files as it will do this +automatically for all the sources defined in <code>/etc/apt/sources.list</code> +when you run (as root) <samp>apt-file update</samp>. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-datapackages"></a>8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?</h2> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +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 <code>aptitude</code> (see <a +href="#s-aptitude">aptitude, Section 8.1.3</a>) 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. +</p> + +<hr> + +<p> +[ <a href="ch-pkg_basics.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ 8 ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-uptodate.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-pkgtools.html b/includes/etch/common/doc/FAQ/html/ch-pkgtools.html index 6c9eeed..6c9eeed 120000 --- a/includes/sid/common/doc/FAQ/html/ch-pkgtools.html +++ b/includes/etch/common/doc/FAQ/html/ch-pkgtools.html diff --git a/includes/etch/common/doc/FAQ/html/ch-redistrib.en.html b/includes/etch/common/doc/FAQ/html/ch-redistrib.en.html new file mode 100644 index 0000000..77bbf56 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-redistrib.en.html @@ -0,0 +1,340 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Redistributing Debian GNU/Linux in a commercial product</title> + +<link href="index.en.html" rel="start"> +<link href="ch-contributing.en.html" rel="prev"> +<link href="ch-nexttime.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-redistrib"></a></p> +<hr> + +<p> +[ <a href="ch-contributing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ 14 ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-nexttime.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 14 - Redistributing Debian GNU/Linux in a commercial product +</h1> + +<hr> + +<h2><a name="s-sellcds"></a>14.1 Can I make and sell Debian CDs?</h2> + +<p> +Go ahead. You do not need permission to distribute anything we have +<em>released</em>, so that you can master your CD as soon as the beta-test +ends. You do not have to pay us anything. Of course, all CD manufacturers +must honor the licenses of the programs in Debian. For example, many of the +programs are licensed under the GPL, which requires you to distribute their +source code. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-packagednonfree"></a>14.2 Can Debian be packaged with non-free software?</h2> + +<p> +Yes. While all the main components of Debian are free software, we provide a +non-free directory for programs that are not freely redistributable. +</p> + +<p> +CD manufacturers <em>may</em> be able to distribute the programs we have placed +in that directory, depending on the license terms or their private arrangements +with the authors of those software packages. CD manufacturers can also +distribute the non-free software they get from other sources on the same CD. +This is nothing new: free and commercial software are distributed on the same +CD by many manufacturers now. Of course we still encourage software authors to +release the programs they write as free software. +</p> + +<hr> + +<h2><a name="s-childistro"></a>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?</h2> + +<p> +Yes. Debian-derived distributions are being created both in close cooperation +with the Debian project itself and by external parties. One can use the +<code><a href="http://cdd.alioth.debian.org/">Custom Debian +Distributions</a></code> framework to work together with Debian; <code><a +href="http://www.skolelinux.org/">Skolelinux</a></code> is one such project. +</p> + +<p> +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. +</p> + +<p> +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 <a href="ch-customizing.en.html#s-divert">How do I override a file +installed by a package, so that a different version can be used instead?, +Section 11.8</a>. +</p> + +<hr> + +<h2><a name="s-commercialdebs"></a>14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?</h2> + +<p> +Go right ahead. The package tool is free software; the packages may or may not +be free software, it can install them all. +</p> + +<hr> + +<p> +[ <a href="ch-contributing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ 14 ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-nexttime.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-redistrib.html b/includes/etch/common/doc/FAQ/html/ch-redistrib.html index f182623..f182623 120000 --- a/includes/sid/common/doc/FAQ/html/ch-redistrib.html +++ b/includes/etch/common/doc/FAQ/html/ch-redistrib.html diff --git a/includes/etch/common/doc/FAQ/html/ch-software.en.html b/includes/etch/common/doc/FAQ/html/ch-software.en.html new file mode 100644 index 0000000..2c2d745 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-software.en.html @@ -0,0 +1,639 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Software available in the Debian system</title> + +<link href="index.en.html" rel="start"> +<link href="ch-compat.en.html" rel="prev"> +<link href="ch-ftparchives.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-software"></a></p> +<hr> + +<p> +[ <a href="ch-compat.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ 5 ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-ftparchives.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 5 - Software available in the Debian system +</h1> + +<hr> + +<h2><a name="s-apps"></a>5.1 What types of applications and development software are available for Debian GNU/Linux?</h2> + +<p> +Like most Linux distributions, Debian GNU/Linux provides: +</p> +<ul> +<li> +<p> +the major GNU applications for software development, file manipulation, and +text processing, including gcc, g++, make, texinfo, Emacs, the Bash shell and +numerous upgraded Unix utilities, +</p> +</li> +</ul> +<ul> +<li> +<p> +Perl, Python, Tcl/Tk and various related programs, modules and libraries for +each of them, +</p> +</li> +</ul> +<ul> +<li> +<p> +TeX (LaTeX) and Lyx, dvips, Ghostscript, +</p> +</li> +</ul> +<ul> +<li> +<p> +the Xorg windowing system, which provides a networked graphical user interface +for Linux, and countless X applications including the GNOME, KDE and Xfce +desktop environments. +</p> +</li> +</ul> +<ul> +<li> +<p> +a full suite of networking applications, including servers for Internet +protocols such as HTTP (WWW), FTP, NNTP (news), SMTP and POP (mail) and DNS +(name servers); relational databases like PostgreSQL, MySQL; also provided are +web browsers including the various Mozilla products [<a +href="footnotes.en.html#f1" name="fr1">1</a>], +</p> +</li> +</ul> +<ul> +<li> +<p> +a complete set of office applications, including the OpenOffice.org +productivity suite, Gnumeric and other spreadsheets, WYSIWYG editors, +calendars. +</p> +</li> +</ul> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-softwareauthors"></a>5.2 Who wrote all that software?</h2> + +<p> +For each package the <em>authors</em> of the program(s) are credited in the +file <samp>/usr/share/doc/PACKAGE/copyright</samp>, where PACKAGE is to be +substituted with the package's name. +</p> + +<p> +<em>Maintainers</em> who package this software for the Debian GNU/Linux system +are listed in the Debian control file (see <a +href="ch-pkg_basics.en.html#s-controlfile">What is a Debian control file?, +Section 7.4</a>) that comes with each package. The Debian changelog, in +<samp>/usr/share/doc/PACKAGE/changelog.Debian.gz</samp>, mentions the people +who've worked on the Debian packaging too. +</p> + +<hr> + +<h2><a name="s-pkglist"></a>5.3 How can I get a current list of programs that have been packaged for Debian?</h2> + +<p> +A complete list is available from any of the <code><a +href="http://www.debian.org/distrib/ftplist">Debian mirrors</a></code>, in the +file <samp>indices/Maintainers</samp>. That file includes the package names +and the names and e-mails of their respective maintainers. +</p> + +<p> +The <code><a href="http://packages.debian.org/">WWW interface to the Debian +packages</a></code> conveniently summarizes the packages in each of about +thirty "sections" of the Debian archive. +</p> + +<hr> + +<h2><a name="s-buildenv"></a>5.4 How can I install a developer's environment to build packages?</h2> + +<p> +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 <code>build-essential</code>. This package is a meta-package or +place-holder package which depends on the standard development tools one needs +to build a Debian package. +</p> + +<p> +Some software can, however, need additional software to be rebuilt, including +library headers or additional tools such as <code>autoconf</code> or +<code>gettext</code>. Debian provides many of the tools needed to build other +software as Debian packages. +</p> + +<p> +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 <code>build-essential</code>) needed to build the +pacakge, this is known as <samp>Build-Dependencies</samp>. To install all the +packages needed to build a given source package and then build said source +package you can just run: +</p> + +<pre> + # apt-get build-dep <var>foo</var> + # apt-get source --build <var>foo</var> +</pre> + +<p> +Notice that if you want to build the Linux kernels distributed by Debian you +will want to install also the <code>kernel-package</code> package. For more +information see <a href="ch-kernel.en.html#s-customkernel">What tools does +Debian provide to build custom kernels?, Section 10.2</a>. +</p> + +<hr> + +<h2><a name="s-missing"></a>5.5 What is missing from Debian GNU/Linux?</h2> + +<p> +A list of packages which are still needed to be packaged for Debian exists, the +<code><a href="http://www.debian.org/devel/wnpp/">Work-Needing and Prospective +Packages list</a></code>. +</p> + +<p> +For more details about adding the missing things, see <a +href="ch-contributing.en.html#s-contrib">How can I become a Debian software +developer?, Section 13.1</a>. +</p> + +<hr> + +<h2><a name="s-no-devs"></a>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?</h2> + +<p> +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). +</p> + +<hr> + +<h2><a name="s-java"></a>5.7 (How) Does Debian support Java?</h2> + +<p> +Several <em>free</em> implementations of Java technology are available as +Debian packages, providing both Java Development Kits as well as Runtime +Environments. You can write, debug and run Java programs using Debian. +</p> + +<p> +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. +</p> + +<p> +Please refer to the <code><a +href="http://www.debian.org/doc/manuals/debian-java-faq/">Debian Java +FAQ</a></code> for more information. +</p> + +<hr> + +<h2><a name="s-isitdebian"></a>5.8 How can I check that I am using a Debian system, and what version is it?</h2> + +<p> +In order to make sure that your system has been installed from the real Debian +base disks check for the existence of <samp>/etc/debian_version</samp> file, +which contains a single one-line entry giving the version number of the +release, as defined by the package <samp>base-files</samp>. +</p> + +<p> +The existence of the program <samp>dpkg</samp> 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. +</p> + +<p> +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 <samp>foo</samp>, use the command <samp>dpkg --list foo</samp>. To +view versions of all installed packages, run: +</p> + +<pre> + dpkg -l +</pre> + +<p> +For a more verbose description, use: +</p> + +<pre> + dpkg --status foo +</pre> + +<hr> + +<h2><a name="s-nonenglish"></a>5.9 How does Debian support non-English languages?</h2> +<ul> +<li> +<p> +Debian GNU/Linux is distributed with keymaps for nearly two dozen keyboards, +and with utilities (in the <samp>kbd</samp> package) to install, view, and +modify the tables. +</p> + +<p> +The installation prompts the user to specify the keyboard he will use. +</p> +</li> +</ul> +<ul> +<li> +<p> +Vast majority of the software we packaged supports entering non-US-ASCII +characters used in other Latin languages (e.g. ISO-8859-1 or ISO-8859-2), and +a number of programs support multi-byte languages such as Japanese or Chinese. +</p> +</li> +</ul> +<ul> +<li> +<p> +Currently, support for German-, Spanish-, Finnish-, French-, Hungarian-, +Italian-, Japanese-, Korean-, Dutch-, Polish-, Portuguese-, Russian-, Turkish-, +and Chinese-language manual pages is provided through the +<samp>manpages-LANG</samp> packages (where LANG is the two-letter ISO country +code). To access an NLS manual page, the user must set the shell LC_MESSAGES +variable to the appropriate string. +</p> + +<p> +For example, in the case of the Italian-language manual pages, LC_MESSAGES +needs to be set to 'italian'. The <code>man</code> program will then search +for Italian manual pages under <samp>/usr/share/man/it/</samp>. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-pine"></a>5.10 Where is pine?</h2> + +<p> +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. +</p> + +<p> +The source package name is <code>pine</code>. You can use the +<code>pine-tracker</code> package to be notified about when you need to +upgrade. +</p> + +<p> +Note that there are many replacements for both pine and pico, such as +<code>mutt</code> and <code>nano</code>, that are located in the main section. +</p> + +<hr> + +<h2><a name="s-qmail"></a>5.11 Where is qmail/ezmlm/djbdns?</h2> + +<p> +Dan J. Bernstein used to distribute <code><a +href="http://cr.yp.to/software.html">all software he has written</a></code> +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 <code><a href="http://cr.yp.to/distributors.html">FAQ from +distributors</a></code> for his distribution terms. +</p> + +<p> +As of 2008-04, <code>daemontools</code>, <code>djbdns</code> and +<code>ucspi-tcp</code> are shipped with Debian lenny (in main). As of this +writing (2008-04), <code>qmail</code> is not yet packaged for Debian main; see +<code><a href="http://bugs.debian.org/457318">Bug #457318 (ITP +qmail)</a></code> for the current status. +</p> + +<p> +As of 2008-04, <samp>publicfile</samp> and <samp>ezmlm</samp> were still not +free software. For <samp>ezmlm</samp>, there's the <code>ezmlm-src</code> +package in the non-free area. +</p> + +<hr> + +<h2><a name="s-flash"></a>5.12 Where is a player for Flash (SWF)?</h2> + +<p> +Debian ships both <code>gnash</code> and <code>swfdec</code>: two free SWF +movie players. +</p> + +<hr> + +<h2><a name="s-googleearth"></a>5.13 Where is Google Earth?</h2> + +<p> +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, <code>googleearth-package</code> (in the contrib-section) might be +helpful in using this software. +</p> + +<hr> + +<h2><a name="s-voip"></a>5.14 Where is VoIP software?</h2> + +<p> +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. <code>ekiga</code> +is one of the popular clients. +</p> + +<hr> + +<h2><a name="s-nonfreewireless"></a>5.15 I have a wireless network card which doesn't work with Linux. What should I do?</h2> + +<p> +Buy one which does :) +</p> + +<p> +Alternatively, use <code>ndiswrapper</code> to use a driver for Windows (if you +have one) on your Linux system. See the <code><a +href="http://wiki.debian.org/NdisWrapper">Debian Wiki ndiswapper +page</a></code> for more information. +</p> + +<hr> + +<p> +[ <a href="ch-compat.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ 5 ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-ftparchives.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-software.html b/includes/etch/common/doc/FAQ/html/ch-software.html index f75c0ab..f75c0ab 120000 --- a/includes/sid/common/doc/FAQ/html/ch-software.html +++ b/includes/etch/common/doc/FAQ/html/ch-software.html diff --git a/includes/etch/common/doc/FAQ/html/ch-support.en.html b/includes/etch/common/doc/FAQ/html/ch-support.en.html new file mode 100644 index 0000000..5036cb5 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-support.en.html @@ -0,0 +1,679 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Getting support for Debian GNU/Linux</title> + +<link href="index.en.html" rel="start"> +<link href="ch-customizing.en.html" rel="prev"> +<link href="ch-contributing.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-support"></a></p> +<hr> + +<p> +[ <a href="ch-customizing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ 12 ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-contributing.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 12 - Getting support for Debian GNU/Linux +</h1> + +<hr> + +<h2><a name="s-debiandocs"></a>12.1 What other documentation exists on and for a Debian system?</h2> +<ul> +<li> +<p> +Installation instructions for the current release: see <code><a +href="http://www.debian.org/releases/stable/installmanual">http://www.debian.org/releases/stable/installmanual</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +The Debian GNU/Linux reference covers many aspects of system administration +through shell-command examples. Basic tutorials, tips, and other information +are provided for many different topics ranging from system administration to +programming. +</p> + +<p> +Get it from the <code>debian-reference</code> package, or at <code><a +href="http://www.debian.org/doc/user-manuals#quick-reference">http://www.debian.org/doc/user-manuals#quick-reference</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +The Debian Policy manual documents the policy requirements for the +distribution, i.e. the structure and contents of the Debian archive, several +design issues of the operating system etc. It also includes the technical +requirements that each package must satisfy to be included in the distribution, +and documents the basic technical aspects of Debian binary and source packages. +</p> + +<p> +Get it from the <code>debian-policy</code> package, or at <code><a +href="http://www.debian.org/doc/devel-manuals#policy">http://www.debian.org/doc/devel-manuals#policy</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Documentation developed by the Debian Documentation Project. It is available +at <code><a +href="http://www.debian.org/doc/">http://www.debian.org/doc/</a></code> and +includes user guides, administration guides and security guides for the Debian +GNU/Linux operating system. +</p> +</li> +</ul> +<ul> +<li> +<p> +Documentation on installed Debian packages: Most packages have files that are +unpacked into <samp>/usr/share/doc/PACKAGE</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Documentation on the Linux project: The Debian package <code>doc-linux</code> +installs all of the most recent versions of the HOWTOs and mini-HOWTOs from the +<code><a href="http://www.tldp.org/">Linux Documentation Project</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Unix-style `man' pages: Most commands have manual pages written in the style of +the original Unix 'man' files. For instance, to see the manual page for the +command `ls', execute <samp>man ls</samp>. Execute <samp>man man</samp> for +more information on finding and viewing manual pages. +</p> + +<p> +New Debian users should note that the 'man' pages of many general system +commands are not available until they install these packages: +</p> +<ul> +<li> +<p> +<samp>man-db</samp>, which contains the <samp>man</samp> program itself, and +other programs for manipulating the manual pages. +</p> +</li> +</ul> +<ul> +<li> +<p> +<samp>manpages</samp>, which contains the system manual pages. (see <a +href="ch-software.en.html#s-nonenglish">How does Debian support non-English +languages?, Section 5.9</a>). +</p> +</li> +</ul> +</li> +</ul> +<ul> +<li> +<p> +GNU-style `info' pages: User documentation for many commands, particularly GNU +tools, is available not in `man' pages, but in `info' files which can be read +by the GNU tool <samp>info</samp>, by running <samp>M-x info</samp> within GNU +Emacs, or with some other Info page viewer. +</p> + +<p> +Its main advantage over the original `man' pages are that it is a hypertext +system. It does <em>not</em> require the WWW, however; <samp>info</samp> can +be run from a plain text console. It was designed by Richard Stallman and +preceded the WWW. +</p> +</li> +</ul> + +<p> +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'. +</p> + +<hr> + +<h2><a name="s-onlineresources"></a>12.2 Are there any on-line resources for discussing Debian?</h2> + +<p> +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 <code><a +href="http://www.debian.org/support">Debian Support webpage</a></code>. +</p> + +<hr> + +<h3><a name="s12.2.1"></a>12.2.1 Mailing lists</h3> + +<p> +There are a lot of <code><a +href="http://www.debian.org/MailingLists/">Debian-related mailing +lists</a></code>. +</p> + +<p> +On a system with the <code>doc-debian</code> package installed there is a +complete list of mailing lists in +<code>/usr/share/doc/debian/mailing-lists.txt</code>. +</p> + +<p> +Debian mailing lists are named following the pattern +debian-<var>list-subject</var>. Examples are debian-announce, debian-user, +debian-news. To subscribe to any list debian-<var>list-subject</var>, send +mail to debian-<var>list-subject</var>-request@lists.debian.org with the word +"subscribe" in the Subject: header. Be sure to remember to add +<em>-request</em> to the e-mail address when using this method to subscribe or +unsubscribe. Otherwise your e-mail will go to the list itself, which could be +embarrassing or annoying, depending on your point of view. +</p> + +<p> +You can subscribe to mailing lists using the <code><a +href="http://www.debian.org/MailingLists/subscribe">WWW form</a></code>. You +can also un-subscribe using a <code><a +href="http://www.debian.org/MailingLists/unsubscribe">WWW form</a></code>. +</p> + +<p> +The list manager's e-mail address is <code><a +href="mailto:listmaster@lists.debian.org">listmaster@lists.debian.org</a></code>, +in case you have any trouble. +</p> + +<p> +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 <code><a +href="http://www.debian.org/MailingLists/index.en.html#disclaimer">Mailing +Lists Privacy policy</a></code> for more information. +</p> + +<p> +Archives of the Debian mailing lists are available via WWW at <code><a +href="http://lists.debian.org/">http://lists.debian.org/</a></code>. +</p> + +<hr> + +<h4><a name="s-mailinglistconduct"></a>12.2.1.1 What is the code of conduct for the mailing lists?</h4> + +<p> +When using the Debian mailing lists, please follow these rules: +</p> +<ul> +<li> +<p> +Do not send spam. See the <code><a +href="http://www.debian.org/MailingLists/#ads">Debian mailing list advertising +policy</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Do not flame; it is not polite. The people developing Debian are all +volunteers, donating their time, energy and money in an attempt to bring the +Debian project together. +</p> +</li> +</ul> +<ul> +<li> +<p> +Do not use foul language; besides, some people receive the lists via packet +radio, where swearing is illegal. +</p> +</li> +</ul> +<ul> +<li> +<p> +Make sure that you are using the proper list. <em>Never</em> post your +(un)subscription requests to the mailing list itself[<a +href="footnotes.en.html#f7" name="fr7">7</a>] +</p> +</li> +</ul> +<ul> +<li> +<p> +See section <a href="#s-bugreport">How do I report a bug in Debian?, Section +12.5</a> for notes on reporting bugs. +</p> +</li> +</ul> + +<hr> + +<h3><a name="s12.2.2"></a>12.2.2 Web forums</h3> + +<p> +<code><a href="http://debianhelp.org/">debianHELP</a></code> and <code><a +href="http://forums.debian.net/">Debian User Forums</a></code> 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.) +</p> + +<hr> + +<h3><a name="s12.2.3"></a>12.2.3 Wiki</h3> + +<p> +Solutions to common problems, howto's, guides, tips and other documentation can +be found at the constantly changing <code><a +href="http://wiki.debian.org/">Debian Wiki</a></code>. +</p> + +<hr> + +<h3><a name="s12.2.4"></a>12.2.4 Maintainers</h3> + +<p> +Users can address questions to individual package maintainers using e-mail. To +reach a maintainer of a package called xyz, send e-mail to +<em>xyz@packages.debian.org</em>. +</p> + +<hr> + +<h3><a name="s12.2.5"></a>12.2.5 Usenet newsgroups</h3> + +<p> +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 +<code><a href="http://www.linux.org/docs/usenet.html">Linux Online</a></code> +and <code><a +href="http://www.linuxjournal.com/helpdesk.php">LinuxJournal</a></code> sites. +</p> + +<hr> + +<h2><a name="s-searchtools"></a>12.3 Is there a quick way to search for information on Debian GNU/Linux?</h2> + +<p> +There is a variety of search engines that serve documentation related to +Debian: +</p> +<ul> +<li> +<p> +<code><a href="http://search.debian.org/">Debian WWW search site</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code><a href="http://groups.google.com/">Google Groups</a></code>: a search +engine for newsgroups. +</p> + +<p> +For example, to find out what experiences people have had with finding drivers +for Promise controllers under Debian, try searching on the phrase <samp>Promise +Linux driver</samp>. This will show you all the postings that contain these +strings, i.e. those where people discussed these topics. If you add +<samp>Debian</samp> to those search strings, you'll also get the postings +specifically related to Debian. +</p> +</li> +</ul> +<ul> +<li> +<p> +Any of the common web spidering engines, such as <code><a +href="http://www.altavista.com/">AltaVista</a></code> or <code><a +href="http://www.google.com/">Google</a></code>, as long as you use the right +search terms. +</p> + +<p> +For example, searching on the string "cgi-perl" gives a more detailed +explanation of this package than the brief description field in its control +file. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-buglogs"></a>12.4 Are there logs of known bugs?</h2> + +<p> +Reports on unsolved (and closed) issues are publicly available: Debian +promissed to do so by stating "We will not hide problems" in the +<code><a href="http://www.debian.org/social_contract">Debian Social +Contract</a></code>. +</p> + +<p> +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. +</p> + +<p> +Copies of this information are available at <code><a +href="http://www.debian.org/Bugs/">http://www.debian.org/Bugs/</a></code>. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-bugreport"></a>12.5 How do I report a bug in Debian?</h2> + +<p> +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: +</p> +<ul> +<li> +<p> +From the WWW. A copy of the instructions is shown at <code><a +href="http://www.debian.org/Bugs/Reporting">http://www.debian.org/Bugs/Reporting</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +On any Debian system with the <code>doc-debian</code> package installed. The +instructions are in the file +<code>/usr/share/doc/debian/bug-reporting.txt</code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +By anonymous FTP. Debian mirror sites contain the instructions in the file +<samp>doc/bug-reporting.txt</samp>. +</p> +</li> +</ul> + +<p> +You can use the package <code>reportbug</code> 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. +</p> + +<p> +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. +</p> + +<hr> + +<p> +[ <a href="ch-customizing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ 12 ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-contributing.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-support.html b/includes/etch/common/doc/FAQ/html/ch-support.html index 978d556..978d556 120000 --- a/includes/sid/common/doc/FAQ/html/ch-support.html +++ b/includes/etch/common/doc/FAQ/html/ch-support.html diff --git a/includes/etch/common/doc/FAQ/html/ch-uptodate.en.html b/includes/etch/common/doc/FAQ/html/ch-uptodate.en.html new file mode 100644 index 0000000..33cc9f0 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/ch-uptodate.en.html @@ -0,0 +1,636 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Keeping your Debian system up-to-date</title> + +<link href="index.en.html" rel="start"> +<link href="ch-pkgtools.en.html" rel="prev"> +<link href="ch-kernel.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-uptodate"></a></p> +<hr> + +<p> +[ <a href="ch-pkgtools.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ 9 ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-kernel.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 9 - Keeping your Debian system up-to-date +</h1> + +<hr> + +<p> +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. +</p> + +<p> +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 +<code><a +href="http://www.debian.org/releases/stable/releasenotes">http://www.debian.org/releases/stable/releasenotes</a></code>. +</p> + +<hr> + +<h2><a name="s-howtocurrent"></a>9.1 How can I keep my Debian system current?</h2> + +<p> +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 <samp>dpkg</samp>. Note that <samp>dpkg</samp> 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. +</p> + +<p> +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: +</p> + +<hr> + +<h3><a name="s-aptitude-upgrade"></a>9.1.1 aptitude</h3> + +<p> +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 +<samp>/usr/share/doc/apt-doc/guide.html/index.html</samp> (you will have to +install the <samp>apt-doc</samp> package). +</p> + +<p> +<code>aptitude</code> 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. +</p> + +<p> +Before you can use <code>aptitude</code>, you'll have to edit the +<samp>/etc/apt/sources.list</samp> 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: +</p> + +<pre> + http://ftp.us.debian.org/debian stable main contrib non-free +</pre> + +<p> +You can replace ftp.us.debian.org with the name of a faster Debian mirror near +you. See the mirror list at <code><a +href="http://www.debian.org/mirror/list">http://www.debian.org/mirror/list</a></code> +for more information. +</p> + +<p> +More details on this can be found in the <code>sources.list(8)</code> manual +page. +</p> + +<p> +To update your system, run +</p> + +<pre> + aptitude update +</pre> + +<p> +followed by +</p> + +<pre> + aptitude dist-upgrade +</pre> + +<p> +Answer any questions that might come up, and your system will be upgraded. See +also <a href="ch-pkgtools.en.html#s-aptitude">aptitude, Section 8.1.3</a>. +</p> + +<hr> + +<h3><a name="s-apt"></a>9.1.2 apt-get, dselect and apt-cdrom</h3> + +<p> +<code>apt-get</code> is an APT-based command-line tool for handling packages, +and the APT dselect method is an interface to APT through <code>dselect</code>. +Both of these provide a simple, safe way to install and upgrade packages. +</p> + +<p> +To use <code>apt-get</code>, install the <code>apt</code> package, and edit the +<samp>/etc/apt/sources.list</samp> file to set it up, just as for <a +href="#s-aptitude-upgrade">aptitude, Section 9.1.1</a>. +</p> + +<p> +Then run +</p> + +<pre> + apt-get update +</pre> + +<p> +followed by +</p> + +<pre> + apt-get dist-upgrade +</pre> + +<p> +Answer any questions that might come up, and your system will be upgraded. See +also the <code>apt-get(8)</code> manual page, as well as <a +href="ch-pkgtools.en.html#s-apt-get">APT, Section 8.1.2</a>. +</p> + +<p> +To use APT with <code>dselect</code>, 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 <code>/etc/apt/sources.list</code>. See also +<a href="ch-pkgtools.en.html#s-dselect">dselect, Section 8.1.6.1</a>. +</p> + +<p> +If you want to use CDs to install packages, you can use <code>apt-cdrom</code>. +For details, please see the Release Notes, section "Setting up for an +upgrade from a local mirror". +</p> + +<p> +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 <samp>apt-get clean</samp> +and <samp>apt-get autoclean</samp>, or to move them someplace else (hint: use +<code>apt-move</code>). +</p> + +<hr> + +<h3><a name="s-update_aptitude"></a>9.1.3 aptitude</h3> + +<p> +<code>aptitude</code> 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 <a +href="ch-pkgtools.en.html#s-aptitude">aptitude, Section 8.1.3</a>). Actions +may be performed from a visual interface or from the command-line. +</p> + +<p> +In command line, the actions are similar to that of APT, so to upgrade your +system run +</p> + +<pre> + aptitude update +</pre> + +<p> +followed by +</p> + +<pre> + aptitude dist-upgrade +</pre> + +<p> +To upgrade from a preview release, <code>aptitude</code> is the tool +recommended. Read the Release Notes at <code><a +href="http://www.debian.org/releases/stable/releasenotes">http://www.debian.org/releases/stable/releasenotes</a></code>. +</p> + +<p> +For details, see the manual page <code>aptitude(8)</code>, and the file +<code>/usr/share/aptitude/README</code> +</p> + +<hr> + +<h3><a name="s-mirror"></a>9.1.4 mirror</h3> + +<p> +This Perl script, and its (optional) manager program called +<code>mirror-master</code>, can be used to fetch user-specified parts of a +directory tree from a specified host <em>via</em> anonymous FTP. +</p> + +<p> +<code>mirror</code> is particularly useful for downloading large volumes of +software. After the first time files have been downloaded from a site, a file +called <samp>.mirrorinfo</samp> is stored on the local host. Changes to the +remote file system are tracked automatically by <code>mirror</code>, which +compares this file to a similar file on the remote system and downloads only +changed files. +</p> + +<p> +The <code>mirror</code> program is generally useful for updating local copies +of remote directory trees. The files fetched need not be Debian files. (Since +<code>mirror</code> is a Perl script, it can also run on non-Unix systems.) +Though the <code>mirror</code> 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. +</p> + +<hr> + +<h3><a name="s-dpkg-mountable"></a>9.1.5 dpkg-mountable</h3> + +<p> +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. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-upgradesingle"></a>9.2 Must I go into single user mode in order to upgrade a package?</h2> + +<p> +No. Packages can be upgraded in place, even in running systems. Debian has a +<samp>start-stop-daemon</samp> program that is invoked to stop, then restart +running process if necessary during a package upgrade. +</p> + +<hr> + +<h2><a name="s-savedebs"></a>9.3 Do I have to keep all those .deb archive files on my disk?</h2> + +<p> +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 +<samp>aptitude clean</samp>. +</p> + +<hr> + +<h2><a name="s-keepingalog"></a>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!</h2> + +<p> +Passing the <samp>--log</samp>-option to <code>dpkg</code> makes +<code>dpkg</code> log status change updates and actions. It logs both the +<code>dpkg</code>-invokation (e.g. +</p> + +<pre> + 2005-12-30 18:10:33 install hello 1.3.18 2.1.1-4 +</pre> + +<p> +) and the results (e.g. +</p> + +<pre> + 2005-12-30 18:10:35 status installed hello 2.1.1-4 +</pre> + +<p> +) If you'd like to log all your <code>dpkg</code> invokations (even those done +using frontends like <code>aptitude</code>), you could add +</p> + +<pre> + log /var/log/dpkg.log +</pre> + +<p> +to your <code>/etc/dpkg/dpkg.cfg</code>. Be sure the created logfile gets +rotated periodically. If you're using <code>logrotate</code>, this can be +achieved by creating a file <code>/etc/logrotate.d/dpkg</code> with contents +</p> + +<pre> + /var/log/dpkg { + missingok + notifempty + } +</pre> + +<p> +More details on <code>dpkg</code> logging can be found in the +<code>dpkg(1)</code> manual page. +</p> + +<p> +<code>aptitude</code> logs the package installations, removals, and upgrades +that it intends to perform to <code>/var/log/aptitude</code>. Note that the +<em>results</em> of those actions are not recorded in this file! +</p> + +<p> +Another way to record your actions is to run your package management session +within the <code>script(1)</code> program. +</p> + +<hr> + +<h2><a name="s-autoupdate"></a>9.5 Can I automatically update the system?</h2> + +<p> +Yes. You can use <code>cron-apt</code>, 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. +</p> + +<p> +Note: Automatic upgrade of packages is <strong>NOT</strong> recommended in +<em>testing</em> or <em>unstable</em> systems as this might bring unexpected +behaviour and remove packages without notice. +</p> + +<hr> + +<h2><a name="s-aptproxy"></a>9.6 I have several machines how can I download the updates only one time?</h2> + +<p> +If you have more than one Debian machine on your network, it is useful to use +<code>apt-proxy</code> to keep all of your Debian systems up-to-date. +</p> + +<p> +<code>apt-proxy</code> 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. <code>apt-proxy</code> automatically builds +a Debian HTTP mirror based on requests which pass through the proxy. +</p> + +<p> +For more details, see the apt-proxy homepage at <code><a +href="http://apt-proxy.sourceforge.net/">http://apt-proxy.sourceforge.net/</a></code> +</p> + +<p> +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. +</p> + +<hr> + +<p> +[ <a href="ch-pkgtools.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ 9 ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-kernel.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/ch-uptodate.html b/includes/etch/common/doc/FAQ/html/ch-uptodate.html index 37f6852..37f6852 120000 --- a/includes/sid/common/doc/FAQ/html/ch-uptodate.html +++ b/includes/etch/common/doc/FAQ/html/ch-uptodate.html diff --git a/includes/etch/common/doc/FAQ/html/footnotes.en.html b/includes/etch/common/doc/FAQ/html/footnotes.en.html new file mode 100644 index 0000000..881269f --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/footnotes.en.html @@ -0,0 +1,294 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Footnotes</title> + +<link href="index.en.html" rel="start"> +<link href=".en.html" rel="prev"> +<link href=".en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Footnotes</h1> + +<h2><a href="ch-software.en.html#fr1" name="f1">1</a></h2> + +<p> +These have been, however, rebranded and are provided with different names due +to trademark issues +</p> + +<h2><a href="ch-ftparchives.en.html#fr2" name="f2">2</a></h2> + +<p> +When the present-day sid did not exist, the FTP site organization had one major +flaw: there was an assumption that when an architecture is created in the +current unstable, it will be released when that distribution becomes the new +stable. For many architectures that isn't the case, with the result that those +directories had to be moved at release time. This was impractical because the +move would chew up lots of bandwidth. +</p> + +<p> +The archive administrators worked around this problem for several years by +placing binaries for unreleased architectures in a special directory called +"sid". For those architectures not yet released, the first time they +were released there was a link from the current stable to sid, and from then on +they were created inside the unstable tree as normal. This layout was somewhat +confusing to users. +</p> + +<p> +With the advent of package pools (see <a href="#s-pools">What's in the +<samp>pool</samp> directory?, Section 6.10</a>), binary packages began to be +stored in a canonical location in the pool, regardless of the distribution, so +releasing a distribution no longer causes large bandwidth consumption on the +mirrors (there is, however, a lot of gradual bandwidth consumption throughout +the development process). +</p> + +<h2><a href="ch-ftparchives.en.html#fr3" name="f3">3</a></h2> + +<p> +<samp>dists/stable/main</samp>, <samp>dists/stable/contrib</samp>, +<samp>dists/stable/non-free</samp>, and <samp>dists/unstable/main/</samp>, etc. +</p> + +<h2><a href="ch-ftparchives.en.html#fr4" name="f4">4</a></h2> + +<p> +Historically, packages were kept in the subdirectory of <samp>dists</samp> +corresponding to which distribution contained them. This turned out to cause +various problems, such as large bandwidth consumption on mirrors when major +changes were made. This was fixed with the introduction of the package pool. +</p> + +<p> +The <samp>dists</samp> directories are still used for the index files used by +programs like <samp>apt</samp>. +</p> + +<h2><a href="ch-pkgtools.en.html#fr5" name="f5">5</a></h2> + +<p> +Notice that there are ports that make this tool available with other package +management systems, like Red Hat package manager, also known as +<code>rpm</code> +</p> + +<h2><a href="ch-pkgtools.en.html#fr6" name="f6">6</a></h2> + +<p> +Although this can also lead to systems with more packages installed than they +actually need to work. +</p> + +<h2><a href="ch-support.en.html#fr7" name="f7">7</a></h2> + +<p> +Use the debian-<var>list-subject</var>-REQUEST@lists.debian.org address for +that. +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/footnotes.html b/includes/etch/common/doc/FAQ/html/footnotes.html index c18fdfb..c18fdfb 120000 --- a/includes/sid/common/doc/FAQ/html/footnotes.html +++ b/includes/etch/common/doc/FAQ/html/footnotes.html diff --git a/includes/etch/common/doc/FAQ/html/index.en.html b/includes/etch/common/doc/FAQ/html/index.en.html new file mode 100644 index 0000000..c7115e0 --- /dev/null +++ b/includes/etch/common/doc/FAQ/html/index.en.html @@ -0,0 +1,522 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ</title> + +<link href="index.en.html" rel="start"> +<link href="ch-faqinfo.en.html" rel="prev"> +<link href="ch-basic_defs.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="index"></a></p> +<hr> + +<p> +[ <a href="ch-faqinfo.en.html">previous</a> ] +[ <a href="#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-basic_defs.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br></h1> + +<hr> + +<h2><a name="abstract"></a>Abstract</h2> + +<p> +This document answers questions frequently asked about Debian GNU/Linux. +</p> + +<hr> + +<h2><a name="copyright"></a>Copyright Notice</h2> + +<p> +Copyright © 1996-2005 by Software in the Public Interest, portions copyright © 2004, 2005, 2006 Kamaraju Kusumanchi +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="contents"></a>Contents</h2> + +<ul> +<li><a href="ch-basic_defs.en.html">1 Definitions and overview</a> + <ul> + <li><a href="ch-basic_defs.en.html#s-whatisfaq">1.1 What is this FAQ?</a></li> + <li><a href="ch-basic_defs.en.html#s-whatisdebian">1.2 What is Debian GNU/Linux?</a></li> + <li><a href="ch-basic_defs.en.html#s-linux">1.3 OK, now I know what Debian is... what is Linux?!</a></li> + <li><a href="ch-basic_defs.en.html#s-non-linux">1.4 Does Debian just do GNU/Linux?</a></li> + <li><a href="ch-basic_defs.en.html#s-difference">1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?</a></li> + <li><a href="ch-basic_defs.en.html#s-gnu">1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?</a></li> + <li><a href="ch-basic_defs.en.html#s-pronunciation">1.7 How does one pronounce Debian and what does this word mean?</a> + </ul></li> +<li><a href="ch-getting.en.html">2 Getting and installing Debian GNU/Linux</a> + <ul> + <li><a href="ch-getting.en.html#s-version">2.1 What is the latest version of Debian?</a></li> + <li><a href="ch-getting.en.html#s-updatestable">2.2 Are there package upgrades in `stable'?</a></li> + <li><a href="ch-getting.en.html#s-boot-floppies">2.3 Where/how can I get the Debian installation disks?</a></li> + <li><a href="ch-getting.en.html#s-cdrom">2.4 How do I install the Debian from CD-ROMs?</a></li> + <li><a href="ch-getting.en.html#s-cdimage-symlinks">2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!</a></li> + <li><a href="ch-getting.en.html#s-remoteinstall">2.6 Can I get and install Debian directly from a remote Internet site?</a></li> + <li><a href="ch-getting.en.html#s-alternativebootinstaller">2.7 Are there any alternative strategies for booting the system installer?</a> + </ul></li> +<li><a href="ch-choosing.en.html">3 Choosing a Debian distribution</a> + <ul> + <li><a href="ch-choosing.en.html#s3.1">3.1 Which Debian distribution (stable/testing/unstable) is better for me?</a> + <ul> + <li><a href="ch-choosing.en.html#s3.1.1">3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?</a></li> + <li><a href="ch-choosing.en.html#s3.1.2">3.1.2 Will there be different different versions of packages in different distributions?</a></li> + <li><a href="ch-choosing.en.html#s3.1.3">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?</a></li> + <li><a href="ch-choosing.en.html#s3.1.4">3.1.4 If I were to decide to change to another distribution, Can I do that?</a></li> + <li><a href="ch-choosing.en.html#s3.1.5">3.1.5 Could you tell me whether to install testing or unstable?</a></li> + <li><a href="ch-choosing.en.html#s3.1.6">3.1.6 You are talking about testing being broken. What do you mean by that?</a></li> + <li><a href="ch-choosing.en.html#s3.1.7">3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?</a></li> + <li><a href="ch-choosing.en.html#s3.1.8">3.1.8 From an administrator's point of view, Which distribution requires more attention?</a></li> + <li><a href="ch-choosing.en.html#s3.1.9">3.1.9 What happens when a new release is made?</a></li> + <li><a href="ch-choosing.en.html#s3.1.10">3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?</a></li> + <li><a href="ch-choosing.en.html#s3.1.11">3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?</a></li> + <li><a href="ch-choosing.en.html#s3.1.12">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?</a></li> + <li><a href="ch-choosing.en.html#s3.1.13">3.1.13 I am still confused. What did you say I should install?</a> + </ul></li> + <li><a href="ch-choosing.en.html#s3.2">3.2 But what about Knoppix, Linex, Ubuntu, and others?</a> + <ul> + <li><a href="ch-choosing.en.html#s3.2.1">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?</a></li> + <li><a href="ch-choosing.en.html#s3.2.2">3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?</a></li> + <li><a href="ch-choosing.en.html#s3.2.3">3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?</a> + </ul></li> + </ul></li> +<li><a href="ch-compat.en.html">4 Compatibility issues</a> + <ul> + <li><a href="ch-compat.en.html#s-arches">4.1 On what hardware architectures/systems does Debian GNU/Linux run?</a></li> + <li><a href="ch-compat.en.html#s-otherdistribs">4.2 How compatible is Debian with other distributions of Linux?</a></li> + <li><a href="ch-compat.en.html#s-otherunices">4.3 How source code compatible is Debian with other Unix systems?</a></li> + <li><a href="ch-compat.en.html#s-otherpackages">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?</a></li> + <li><a href="ch-compat.en.html#s-non-debian-programs">4.5 How should I install a non-Debian program?</a></li> + <li><a href="ch-compat.en.html#s-termcap">4.6 Why can't I compile programs that require libtermcap?</a></li> + <li><a href="ch-compat.en.html#s-accelx">4.7 Why can't I install AccelX?</a></li> + <li><a href="ch-compat.en.html#s-motifnls">4.8 Why do my old XFree 2.1 Motif applications crash?</a> + </ul></li> +<li><a href="ch-software.en.html">5 Software available in the Debian system</a> + <ul> + <li><a href="ch-software.en.html#s-apps">5.1 What types of applications and development software are available for Debian GNU/Linux?</a></li> + <li><a href="ch-software.en.html#s-softwareauthors">5.2 Who wrote all that software?</a></li> + <li><a href="ch-software.en.html#s-pkglist">5.3 How can I get a current list of programs that have been packaged for Debian?</a></li> + <li><a href="ch-software.en.html#s-buildenv">5.4 How can I install a developer's environment to build packages?</a></li> + <li><a href="ch-software.en.html#s-missing">5.5 What is missing from Debian GNU/Linux?</a></li> + <li><a href="ch-software.en.html#s-no-devs">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?</a></li> + <li><a href="ch-software.en.html#s-java">5.7 (How) Does Debian support Java?</a></li> + <li><a href="ch-software.en.html#s-isitdebian">5.8 How can I check that I am using a Debian system, and what version is it?</a></li> + <li><a href="ch-software.en.html#s-nonenglish">5.9 How does Debian support non-English languages?</a></li> + <li><a href="ch-software.en.html#s-pine">5.10 Where is pine?</a></li> + <li><a href="ch-software.en.html#s-qmail">5.11 Where is qmail/ezmlm/djbdns?</a></li> + <li><a href="ch-software.en.html#s-flash">5.12 Where is a player for Flash (SWF)?</a></li> + <li><a href="ch-software.en.html#s-googleearth">5.13 Where is Google Earth?</a></li> + <li><a href="ch-software.en.html#s-voip">5.14 Where is VoIP software?</a></li> + <li><a href="ch-software.en.html#s-nonfreewireless">5.15 I have a wireless network card which doesn't work with Linux. What should I do?</a> + </ul></li> +<li><a href="ch-ftparchives.en.html">6 The Debian FTP archives</a> + <ul> + <li><a href="ch-ftparchives.en.html#s-dists">6.1 How many Debian distributions are there?</a></li> + <li><a href="ch-ftparchives.en.html#s-codenames">6.2 What are all those names like etch, lenny, etc.?</a> + <ul> + <li><a href="ch-ftparchives.en.html#s-oldcodenames">6.2.1 Which other codenames have been used in the past?</a></li> + <li><a href="ch-ftparchives.en.html#s-sourceforcodenames">6.2.2 Where do these codenames come from?</a> + </ul></li> + <li><a href="ch-ftparchives.en.html#s-sid">6.3 What about "sid"?</a></li> + <li><a href="ch-ftparchives.en.html#s-stable">6.4 What does the stable directory contain?</a></li> + <li><a href="ch-ftparchives.en.html#s-testing">6.5 What does the testing distribution contain?</a> + <ul> + <li><a href="ch-ftparchives.en.html#s-frozen">6.5.1 What about "testing"? How is it `frozen'?</a> + </ul></li> + <li><a href="ch-ftparchives.en.html#s-unstable">6.6 What does the unstable distribution contain?</a></li> + <li><a href="ch-ftparchives.en.html#s-dirtree">6.7 What are all those directories at the Debian FTP archives?</a></li> + <li><a href="ch-ftparchives.en.html#s-archsections">6.8 What are all those directories inside <samp>dists/stable/main</samp>?</a></li> + <li><a href="ch-ftparchives.en.html#s-source">6.9 Where is the source code?</a></li> + <li><a href="ch-ftparchives.en.html#s-pools">6.10 What's in the <samp>pool</samp> directory?</a></li> + <li><a href="ch-ftparchives.en.html#s-incoming">6.11 What is "incoming"?</a></li> + <li><a href="ch-ftparchives.en.html#s-ownrepository">6.12 How do I set up my own apt-able repository?</a> + </ul></li> +<li><a href="ch-pkg_basics.en.html">7 Basics of the Debian package management system</a> + <ul> + <li><a href="ch-pkg_basics.en.html#s-package">7.1 What is a Debian package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-deb-format">7.2 What is the format of a Debian binary package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-pkgname">7.3 Why are Debian package file names so long?</a></li> + <li><a href="ch-pkg_basics.en.html#s-controlfile">7.4 What is a Debian control file?</a></li> + <li><a href="ch-pkg_basics.en.html#s-conffile">7.5 What is a Debian conffile?</a></li> + <li><a href="ch-pkg_basics.en.html#s-maintscripts">7.6 What is a Debian preinst, postinst, prerm, and postrm script?</a></li> + <li><a href="ch-pkg_basics.en.html#s-priority">7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-virtual">7.8 What is a Virtual Package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-depends">7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-pre-depends">7.10 What is meant by Pre-Depends?</a></li> + <li><a href="ch-pkg_basics.en.html#s-pkgstatus">7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?</a></li> + <li><a href="ch-pkg_basics.en.html#s-puttingonhold">7.12 How do I put a package on hold?</a></li> + <li><a href="ch-pkg_basics.en.html#s-sourcepkgs">7.13 How do I install a source package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-sourcebuild">7.14 How do I build binary packages from a source package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-creatingdebs">7.15 How do I create Debian packages myself?</a> + </ul></li> +<li><a href="ch-pkgtools.en.html">8 The Debian package management tools</a> + <ul> + <li><a href="ch-pkgtools.en.html#s-pkgprogs">8.1 What programs does Debian provide for managing its packages?</a> + <ul> + <li><a href="ch-pkgtools.en.html#s-dpkg">8.1.1 dpkg</a></li> + <li><a href="ch-pkgtools.en.html#s-apt-get">8.1.2 APT</a></li> + <li><a href="ch-pkgtools.en.html#s-aptitude">8.1.3 aptitude</a></li> + <li><a href="ch-pkgtools.en.html#s-synaptic">8.1.4 synaptic</a></li> + <li><a href="ch-pkgtools.en.html#s-tasksel">8.1.5 tasksel</a></li> + <li><a href="ch-pkgtools.en.html#s-dpkg-extra">8.1.6 Other package management tools</a> + </ul></li> + <li><a href="ch-pkgtools.en.html#s-updaterunning">8.2 Debian claims to be able to update a running program; how is this accomplished?</a></li> + <li><a href="ch-pkgtools.en.html#s-whatpackages">8.3 How can I tell what packages are already installed on a Debian system?</a></li> + <li><a href="ch-pkgtools.en.html#s-listfiles">8.4 How to display the files of a package installed?</a></li> + <li><a href="ch-pkgtools.en.html#s-filesearch">8.5 How can I find out what package produced a particular file?</a></li> + <li><a href="ch-pkgtools.en.html#s-datapackages">8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?</a> + </ul></li> +<li><a href="ch-uptodate.en.html">9 Keeping your Debian system up-to-date</a> + <ul> + <li><a href="ch-uptodate.en.html#s-howtocurrent">9.1 How can I keep my Debian system current?</a> + <ul> + <li><a href="ch-uptodate.en.html#s-aptitude-upgrade">9.1.1 aptitude</a></li> + <li><a href="ch-uptodate.en.html#s-apt">9.1.2 apt-get, dselect and apt-cdrom</a></li> + <li><a href="ch-uptodate.en.html#s-update_aptitude">9.1.3 aptitude</a></li> + <li><a href="ch-uptodate.en.html#s-mirror">9.1.4 mirror</a></li> + <li><a href="ch-uptodate.en.html#s-dpkg-mountable">9.1.5 dpkg-mountable</a> + </ul></li> + <li><a href="ch-uptodate.en.html#s-upgradesingle">9.2 Must I go into single user mode in order to upgrade a package?</a></li> + <li><a href="ch-uptodate.en.html#s-savedebs">9.3 Do I have to keep all those .deb archive files on my disk?</a></li> + <li><a href="ch-uptodate.en.html#s-keepingalog">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!</a></li> + <li><a href="ch-uptodate.en.html#s-autoupdate">9.5 Can I automatically update the system?</a></li> + <li><a href="ch-uptodate.en.html#s-aptproxy">9.6 I have several machines how can I download the updates only one time?</a> + </ul></li> +<li><a href="ch-kernel.en.html">10 Debian and the kernel</a> + <ul> + <li><a href="ch-kernel.en.html#s-non-debian-kernel">10.1 Can I install and compile a kernel without some Debian-specific tweaking?</a></li> + <li><a href="ch-kernel.en.html#s-customkernel">10.2 What tools does Debian provide to build custom kernels?</a></li> + <li><a href="ch-kernel.en.html#s-custombootdisk">10.3 How can I make a custom boot floppy?</a></li> + <li><a href="ch-kernel.en.html#s-modules">10.4 What special provisions does Debian provide to deal with modules?</a></li> + <li><a href="ch-kernel.en.html#s-removeoldkernel">10.5 Can I safely de-install an old kernel package, and if so, how?</a> + </ul></li> +<li><a href="ch-customizing.en.html">11 Customizing your installation of Debian GNU/Linux</a> + <ul> + <li><a href="ch-customizing.en.html#s-papersize">11.1 How can I ensure that all programs use the same paper size?</a></li> + <li><a href="ch-customizing.en.html#s-hardwareaccess">11.2 How can I provide access to hardware peripherals, without compromising security?</a></li> + <li><a href="ch-customizing.en.html#s-consolefont">11.3 How do I load a console font on startup the Debian way?</a></li> + <li><a href="ch-customizing.en.html#s-appdefaults">11.4 How can I configure an X11 program's application defaults?</a></li> + <li><a href="ch-customizing.en.html#s-booting">11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's.</a></li> + <li><a href="ch-customizing.en.html#s-custombootscripts">11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?</a></li> + <li><a href="ch-customizing.en.html#s-interconffiles">11.7 How does the package management system deal with packages that contain configuration files for other packages?</a></li> + <li><a href="ch-customizing.en.html#s-divert">11.8 How do I override a file installed by a package, so that a different version can be used instead?</a></li> + <li><a href="ch-customizing.en.html#s-localpackages">11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?</a></li> + <li><a href="ch-customizing.en.html#s-diverse">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?</a> + </ul></li> +<li><a href="ch-support.en.html">12 Getting support for Debian GNU/Linux</a> + <ul> + <li><a href="ch-support.en.html#s-debiandocs">12.1 What other documentation exists on and for a Debian system?</a></li> + <li><a href="ch-support.en.html#s-onlineresources">12.2 Are there any on-line resources for discussing Debian?</a> + <ul> + <li><a href="ch-support.en.html#s12.2.1">12.2.1 Mailing lists</a></li> + <li><a href="ch-support.en.html#s12.2.2">12.2.2 Web forums</a></li> + <li><a href="ch-support.en.html#s12.2.3">12.2.3 Wiki</a></li> + <li><a href="ch-support.en.html#s12.2.4">12.2.4 Maintainers</a></li> + <li><a href="ch-support.en.html#s12.2.5">12.2.5 Usenet newsgroups</a> + </ul></li> + <li><a href="ch-support.en.html#s-searchtools">12.3 Is there a quick way to search for information on Debian GNU/Linux?</a></li> + <li><a href="ch-support.en.html#s-buglogs">12.4 Are there logs of known bugs?</a></li> + <li><a href="ch-support.en.html#s-bugreport">12.5 How do I report a bug in Debian?</a> + </ul></li> +<li><a href="ch-contributing.en.html">13 Contributing to the Debian Project</a> + <ul> + <li><a href="ch-contributing.en.html#s-contrib">13.1 How can I become a Debian software developer?</a></li> + <li><a href="ch-contributing.en.html#s-contribresources">13.2 How can I contribute resources to the Debian project?</a></li> + <li><a href="ch-contributing.en.html#s-supportingorganizations">13.3 How can I contribute financially to the Debian project?</a> + <ul> + <li><a href="ch-contributing.en.html#s-SPI">13.3.1 Software in the Public Interest</a></li> + <li><a href="ch-contributing.en.html#s-FSF">13.3.2 Free Software Foundation</a> + </ul></li> + </ul></li> +<li><a href="ch-redistrib.en.html">14 Redistributing Debian GNU/Linux in a commercial product</a> + <ul> + <li><a href="ch-redistrib.en.html#s-sellcds">14.1 Can I make and sell Debian CDs?</a></li> + <li><a href="ch-redistrib.en.html#s-packagednonfree">14.2 Can Debian be packaged with non-free software?</a></li> + <li><a href="ch-redistrib.en.html#s-childistro">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?</a></li> + <li><a href="ch-redistrib.en.html#s-commercialdebs">14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?</a> + </ul></li> +<li><a href="ch-nexttime.en.html">15 Changes expected in the next major release of Debian</a> + <ul> + <li><a href="ch-nexttime.en.html#s-i18n">15.1 Extended support for non-English users</a></li> + <li><a href="ch-nexttime.en.html#s-dependencybasedboot">15.2 Faster booting: Dependency based boot sequence</a></li> + <li><a href="ch-nexttime.en.html#s-di">15.3 Improvements in the Debian Installer</a></li> + <li><a href="ch-nexttime.en.html#s-morearches">15.4 More architectures</a></li> + <li><a href="ch-nexttime.en.html#s-morekernels">15.5 More kernels</a> + </ul></li> +<li><a href="ch-faqinfo.en.html">16 General information about the FAQ</a> + <ul> + <li><a href="ch-faqinfo.en.html#s-authors">16.1 Authors</a></li> + <li><a href="ch-faqinfo.en.html#s-feedback">16.2 Feedback</a></li> + <li><a href="ch-faqinfo.en.html#s-latest">16.3 Availability</a></li> + <li><a href="ch-faqinfo.en.html#s-docformat">16.4 Document format</a></li> + </ul></li> +</ul> + +<hr> + +<p> +[ <a href="ch-faqinfo.en.html">previous</a> ] +[ <a href="#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-basic_defs.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + diff --git a/includes/sid/common/doc/FAQ/html/index.html b/includes/etch/common/doc/FAQ/html/index.html index 0e85422..0e85422 120000 --- a/includes/sid/common/doc/FAQ/html/index.html +++ b/includes/etch/common/doc/FAQ/html/index.html diff --git a/includes/sid/common/doc/bug-log-access.txt b/includes/etch/common/doc/bug-log-access.txt index c8fa75f..c8fa75f 100644 --- a/includes/sid/common/doc/bug-log-access.txt +++ b/includes/etch/common/doc/bug-log-access.txt diff --git a/includes/sid/common/doc/bug-log-mailserver.txt b/includes/etch/common/doc/bug-log-mailserver.txt index aa28efc..447a059 100644 --- a/includes/sid/common/doc/bug-log-mailserver.txt +++ b/includes/etch/common/doc/bug-log-mailserver.txt @@ -14,18 +14,18 @@ Introduction to the bug system request server 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 starting with quit, stop, - thank or two hyphens (to avoid parsing a signature). 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. + 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 + send-detail sends all of the "boring" messages in the transcript as well, such as the various auto-acks. index [full] @@ -95,8 +95,11 @@ Commands available quit stop - thank... - --... + 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 #, diff --git a/includes/sid/common/doc/bug-mailserver-refcard.txt b/includes/etch/common/doc/bug-mailserver-refcard.txt index b3ce545..04a075b 100644 --- a/includes/sid/common/doc/bug-mailserver-refcard.txt +++ b/includes/etch/common/doc/bug-mailserver-refcard.txt @@ -45,7 +45,7 @@ Synopsis of extra commands available at control@bugs.debian.org * tag bugnumber [ + | - | = ] tag [ tag ... ] * block bugnumber by bug ... * unblock bugnumber by bug ... - * close bugnumber [ fixed-version ] (deprecated - you must + * 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 diff --git a/includes/sid/common/doc/bug-maint-info.txt b/includes/etch/common/doc/bug-maint-info.txt index de36df0..e8b0206 100644 --- a/includes/sid/common/doc/bug-maint-info.txt +++ b/includes/etch/common/doc/bug-maint-info.txt @@ -83,7 +83,7 @@ Followup messages 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 + 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. @@ -115,7 +115,8 @@ Severity levels serious is a severe violation of Debian policy (roughly, it violates a "must" or "required" directive), or, in the package - maintainer's opinion, makes the package unsuitable for release. + 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, @@ -136,7 +137,7 @@ Severity levels 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 Etch. + see the list of Release-Critical Issues for Lenny. Tags for bug reports @@ -254,6 +255,15 @@ Tags for bug reports 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. @@ -261,10 +271,12 @@ Tags for bug reports This bug should not be archived until it is fixed in experimental. - The meanings of the latter 6 tags have changed recently; the ignore + 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 indicate which bugs affected a specific - release now indicate when a bug can be archived. + 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 @@ -287,7 +299,7 @@ Recording that you have passed on a bug report 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 + You can also manipulate the "forwarded to" information by sending messages to control@bugs.debian.org. Changing bug ownership @@ -335,7 +347,7 @@ Subscribing to bugs 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@debian.org, are sent to subscribers. + 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 @@ -373,9 +385,10 @@ More-or-less obsolete subject-scanning feature 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. + 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 diff --git a/includes/sid/common/doc/bug-maint-mailcontrol.txt b/includes/etch/common/doc/bug-maint-mailcontrol.txt index 52f8474..a0b7c9e 100644 --- a/includes/sid/common/doc/bug-maint-mailcontrol.txt +++ b/includes/etch/common/doc/bug-maint-mailcontrol.txt @@ -1,9 +1,8 @@ Introduction to the bug control and manipulation mailserver - In addition to the mailserver on request@bugs.debian.org which allows - the retrieval of bug data and documentation by email, there is another - server on control@bugs.debian.org which also allows bug reports to be - manipulated in various ways. + 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 @@ -27,6 +26,29 @@ Introduction to the bug control and manipulation mailserver 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, @@ -37,6 +59,12 @@ Commands available at the control mailserver 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. @@ -163,16 +191,16 @@ Commands available at the control mailserver 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 + 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 @@ -240,20 +268,20 @@ Commands available at the control mailserver Example usage: - # same as 'tags 123456 + patch' - tags 123456 patch + # same as 'tags 123456 + patch' + tags 123456 patch - # same as 'tags 123456 + help security' - tags 123456 help security + # same as 'tags 123456 + help security' + tags 123456 help security - # add 'fixed' and 'pending' tags - tags 123456 + fixed pending + # add 'fixed' and 'pending' tags + tags 123456 + fixed pending - # remove 'unreproducible' tag - tags 123456 - unreproducible + # remove 'unreproducible' tag + tags 123456 - unreproducible - # set tags to exactly 'moreinfo' and 'unreproducible' - tags 123456 = moreinfo 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, @@ -297,15 +325,15 @@ Commands available at the control mailserver Example usage: - package foo - reassign 123456 bar 1.0-1 + package foo + reassign 123456 bar 1.0-1 - package bar - retitle 123456 bar: bar sucks - severity 123456 normal + package bar + retitle 123456 bar: bar sucks + severity 123456 normal - package - severity 234567 wishlist + package + severity 234567 wishlist owner bugnumber address | ! Sets address to be the "owner" of #bugnumber. The owner of a @@ -321,6 +349,18 @@ Commands available at the control mailserver 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 diff --git a/includes/sid/common/doc/bug-reporting.txt b/includes/etch/common/doc/bug-reporting.txt index 8ea79c5..974eb20 100644 --- a/includes/sid/common/doc/bug-reporting.txt +++ b/includes/etch/common/doc/bug-reporting.txt @@ -1,58 +1,88 @@ -How to report a bug in Debian +How to report a bug in Debian using reportbug -Important things to note before sending + We strongly recommend that you report bugs in Debian using the + reportbug program. To install and start it, simply run: - Please don't report multiple unrelated bugs -- especially ones in - different packages -- in a single bug report. It makes our lives much - easier if you send separate reports. + 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 - You should check if your bug report has already been filed by someone - else before submitting it. Lists of currently outstanding bugs are - available on the World Wide Web and elsewhere -- see other documents - for details. You can submit your comments to an existing bug report - #<number> by sending e-mail to <number>@bugs.debian.org +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 you can't seem to determine which package contains the problem, - 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. - 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. +Has your bug report been filed already? -Sending the bug report using an automatic bug report tool + 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 #<number>, you should submit your + comments by sending e-mail to <number>@bugs.debian.org instead of + reporting a new bug. - The reportbug program can ease filing bugs by guiding you through the - bug reporting process step by step. The querybts tool, available from - the same package as reportbug, provides a convenient text-based - interface to the bug tracking system. +Send multiple reports for multiple bugs - 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. + 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 - Send e-mail to submit@bugs.debian.org, as described below. + 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 - Of course, 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! + 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! - You need to put a pseudo-header at the start of the body of the - message. That means that the first line of the message body should - say: -Package: <something> + 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: <packagename> - Replace <something> with the name of the package which has the bug. + Replace <packagename> with the name of the package which has the bug. The second line of the message should say: -Version: <something> +Version: <packageversion> - Replace <something> with the version of the package. Please don't + Replace <packageversion> 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. @@ -62,16 +92,17 @@ Version: <something> package's maintainer. See this example for information on how to find this information. - The pseudo-header fields should start at the very start of their - lines. + 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 behaviour: exactly what behaviour - you were expecting, and what you observed. A transcript of an - example session is a good way of showing this. + * 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. @@ -86,19 +117,24 @@ Version: <something> 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 + <package> 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 (uuencoding them if they may - contain odd characters etc.). + 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. -Example +An Example Bug Report - A bug report, with mail header, looks something like this: + 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' @@ -151,19 +187,22 @@ Sending copies of bug reports to other addresses 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 that, you can set the severity level of the bug as you report - it. This is not required, however, and the developers will assign an - appropriate severity level to your report if you do not. + 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: <severity> Replace <severity> with one of the available severity levels, as - described in the developers' documentation. + described in the advanced documentation. Assigning tags @@ -176,7 +215,7 @@ Assigning tags Tags: <tags> Replace <tags> with one or more of the available tags, as described in - the developers' documentation. Separate multiple tags with commas, + the advanced documentation. Separate multiple tags with commas, spaces, or both. User: <username> Usertags: <usertags> @@ -185,9 +224,6 @@ Usertags: <usertags> with commas, spaces, or both. If you specify a <username>, that user's tags will be set. Otherwise, the e-mail address of the sender will be used as the username. - -Other pseudo headers (primarily of interest to package maintainers) - Forwarded: foo@example.com will mark the newly submitted bug as forwarded to foo@example.com. See @@ -207,29 +243,31 @@ Source: foopackage 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 instead of submit@bugs. maintonly will - forward the report to the package maintainer only, it won't forward it - to the BTS mailing lists. + 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 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. + 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. Bugs sent to - quiet@bugs will not be forwarded anywhere, only filed. + 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 instead of nnn@bugs, unless of course one overrides - this manually. + nnn-maintonly@bugs.debian.org instead of nnn@bugs.debian.org, unless + of course one overrides this manually. Acknowledgements @@ -243,27 +281,31 @@ Acknowledgements interface yourself to find the bug number. Note that this header will not suppress acknowledgements from the - control@bugs mailserver, since those acknowledgements may contain - error messages which should be read and acted upon. + 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'll forward the report to debian-bugs-dist even - if maintonly was used. + relevant package is it will forward the report to debian-bugs-dist + even if maintonly was used. - When sending to maintonly@bugs or nnn-maintonly@bugs 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 service to (re)assign the report - appropriately first if it isn't correct already. + 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 - If you are reporting a bug in a command, you can 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. + 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 @@ -300,6 +342,15 @@ Description: Advanced front-end for dpkg 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 <owner@bugs.debian.org> diff --git a/includes/sid/common/doc/constitution.txt b/includes/etch/common/doc/constitution.txt index 70eca90..96ed0c7 100644 --- a/includes/sid/common/doc/constitution.txt +++ b/includes/etch/common/doc/constitution.txt @@ -1,10 +1,10 @@ + Historical version of the Constitution for the Debian Project (v1.2) - Historical version of the Constitution for the Debian Project (v1.2) - - Version 1.2 ratified on October 29^th, 2003. Supersedes Version 1.1 - ratified on June 21^st, 2003, which itself supersedes Version 1.0 - ratified on December 2^nd, 1998. Superseded by version 1.3, ratified - on September 24^th, 2006. + 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 @@ -26,26 +26,26 @@ 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 + 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 + 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. + 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. @@ -95,12 +95,12 @@ 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". + 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. + 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.) @@ -108,8 +108,8 @@ 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. + 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 @@ -128,9 +128,8 @@ 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. + 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 @@ -146,24 +145,22 @@ 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. + 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. + 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. + 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; @@ -194,16 +191,16 @@ 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. + 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. + 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 @@ -222,8 +219,8 @@ 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. + The Project Leader should avoid overemphasizing their own point of view + when making decisions in their capacity as Leader. 6. Technical committee @@ -232,19 +229,18 @@ 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).) + 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. + 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. @@ -257,26 +253,26 @@ 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. + 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. + 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. + 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 @@ -298,20 +294,19 @@ 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. + 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). + 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. + 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 @@ -319,9 +314,9 @@ 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. + 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. @@ -356,9 +351,9 @@ 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 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 @@ -418,8 +413,8 @@ 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 + 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 @@ -429,8 +424,7 @@ 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. + 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 @@ -462,23 +456,23 @@ A. Standard Resolution Procedure 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. + 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 or a resolution may suggest changes to the wordings - of amendments; these take effect if the proposer of the amendment + 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 @@ -548,10 +542,9 @@ A. Standard Resolution Procedure 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. + 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 @@ -562,12 +555,12 @@ A. Standard Resolution Procedure 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 + 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, @@ -576,33 +569,32 @@ A. Standard Resolution Procedure 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). + 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. + 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. + 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. `May' 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. + 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/sid/common/doc/debian-manifesto b/includes/etch/common/doc/debian-manifesto index 9322c93..9322c93 100644 --- a/includes/sid/common/doc/debian-manifesto +++ b/includes/etch/common/doc/debian-manifesto diff --git a/includes/etch/common/doc/mailing-lists.txt b/includes/etch/common/doc/mailing-lists.txt new file mode 100644 index 0000000..84010d8 --- /dev/null +++ b/includes/etch/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 + + <listname>-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/sid/common/doc/social-contract.txt b/includes/etch/common/doc/social-contract.txt index e0ddb27..63591f8 100644 --- a/includes/sid/common/doc/social-contract.txt +++ b/includes/etch/common/doc/social-contract.txt @@ -1,13 +1,12 @@ - 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. - _________________________________________________________________ + 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 @@ -20,14 +19,14 @@ 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. + 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. + 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. @@ -44,14 +43,14 @@ 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. - _________________________________________________________________ + 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) @@ -66,13 +65,13 @@ The Debian Free Software Guidelines (DFSG) 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. + 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 + "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. @@ -82,21 +81,21 @@ The Debian Free Software Guidelines (DFSG) 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. + 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. + 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 @@ -113,8 +112,7 @@ The Debian Free Software Guidelines (DFSG) 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". + 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/sid/common/doc/source-unpack.txt b/includes/etch/common/doc/source-unpack.txt index 151b733..151b733 100644 --- a/includes/sid/common/doc/source-unpack.txt +++ b/includes/etch/common/doc/source-unpack.txt diff --git a/includes/sid/install/README.html b/includes/etch/install/README.html index 549a748..297d43b 100644 --- a/includes/sid/install/README.html +++ b/includes/etch/install/README.html @@ -1,3 +1,5 @@ + + <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html lang="en"> <head> @@ -21,31 +23,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - <div align=right> (<a href="README.txt">Text version</a>) </div> @@ -59,12 +36,6 @@ </table> - - - - - - <table bgcolor="#DF0451" border="0" cellpadding="0" cellspacing="0" width="100%" summary=""> <tr> @@ -77,7 +48,7 @@ <table align="center" border="0" cellpadding="2" cellspacing="0"> <tr><td bgcolor="#000084"> <div align="center"><font color="#FFFFFF" face="helvetica,arial"><B> - DEBIAN_NAME DEBIAN_DATE + Debian GNU/Linux 4.0 r5 "Etch" - Official i386 BC Binary-1 20081024-15:52 </B></font></div> </td></tr> </table> @@ -123,78 +94,41 @@ vspace="0" alt="" width="15" height="16"> <font face="Arial,Helvetica"> - <P><B><A href="http://www.debian.org/">Debian home page</A></B></P> - <br> <P> - - - - - - - - - - <A href="#intro">Intro</A> <P> - - - <A href="#thisdisc">About This Disc</A> <P> - - - <A href="#install">Installing</A> <P> - - - - <A href="#lastmin">Last-Minute Notes</A> <P> - - - - - <A href="#apt">Using CDs/DVDs with apt</A> <P> - - - - - <A href="#cdmanuf">CD/DVD Manufacturers</A> <P> - - - - <A href="#other">More Information</A> <P> - <P> <A href=".">Browse This Disc</A></P> <P> @@ -202,15 +136,10 @@ vspace="0" alt="" width="15" height="16"> </P> - </font> - - - - </td> <td bgcolor="#BBDDFF"> </td> <td> </td> @@ -229,14 +158,10 @@ Debian GNU/Linux! <P><H2><A name="intro"> Intro - - - - </H2> </a> <p> -This is one disc in a set containing the the +This is one disc in a set containing the <a href="http://www.debian.org/">Debian GNU/Linux</a> distribution. Debian is a very extensive collection of software. But it is more. It is a complete @@ -265,109 +190,69 @@ Compaq's <i>Alpha</i>, Sun's <i>Sparc</i>, Motorola/IBM's <i>PowerPC</i>, and <i>(Strong)ARM</i> processors. Check the <A href="http://www.debian.org/ports">ports</A> page - - - for more information. <P> - - - - - <A href="http://www.debian.org/intro/about">Read more...</A> - - - - - <P><HR><P><H2><A name="thisdisc"> - About This Disc - - - - </H2> </a> <p> This disc is labeled <P> <tt> - DEBIAN_NAME DEBIAN_DATE + Debian GNU/Linux 4.0 r5 "Etch" - Official i386 BC Binary-1 20081024-15:52 </tt> <P> - which means that this disc is number 1 of a set of 1 discs. - -It contains programs ("binaries") for `DEBIAN_ARCHITECTURE' computers. - - - - - +The packages on this disc contain programs ("binaries") for 'ARCH' computers. <P> -The programs on the Binary discs are ordered by popularity. The Binary-1 disc +The packages on the Binary discs are ordered by popularity. The Binary-1 disc contains the most popular programs and the installation tools; it is possible -to install and run Debian with only the Binary-1 disc. The other discs, up to -Binary-1, contain mostly special-interest programs. -<p> - +to install and run Debian with only the Binary-1 disc. +It is unlikely that you will need all of the 1 discs in the set. The +higher the number in the set, the less likely it is that you will use any of +the packages on that disc; higher-number images contain mostly special-interest +programs. +<P> The Release Notes for "etch" are available on the <A href="http://www.debian.org/releases/etch/releasenotes">Debian web site</A>. - - - - - - - - - - - <P><HR><P><H2><A name="install"> - Installing - - - - </H2> </a> <p> - Because Debian is a complete Operating System, the installation procedure may seem a bit unusual. You can install Debian GNU/Linux either <i>alongside</i> your current OS, or as the <i>only</i> OS on your computer. - <P> An <b>Installation Guide</b> for this disc is available from <A href="http://www.debian.org/releases/etch/installmanual">the Debian web site</a>. <P> Programs and other files that are needed for the installation can be found on this disc under - DEBIAN_TOOLS - - + <P> + <tt> + <A href="tools/">/tools/</a> + </tt> + and + <tt> + <A href="install/floppy/">/install/floppy/</a> + </tt> <P> 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. <P> - - You can examine the <P> <tt> @@ -378,102 +263,55 @@ Installing from there. - - - - - - - - - - - <P><HR><P><H2><A name="lastmin"> - Last-Minute Notes - - - - </H2> </a> <p> <UL> - - - - - - - - <LI>This is an official release of the Debian system. Please report any bugs you find in the Debian Bug Tracking System; details at <A HREF="http://bugs.debian.org/">bugs.debian.org</A>. <LI>If you're reporting bugs against this disc or the installation system, please also mention the version of this disc; this can be -found in the file <a href="/.disk/info">/.disk/info</a>. - +found in the file <a href="./.disk/info">/.disk/info</a>. <br> </LI> </UL> - - - - - - <P><HR><P><H2><A name="apt"> - Using Apt - - - - </H2> </a> <p> After installing or upgrading, Debian's packaging system can use CDs, DVDs, local collections, or networked servers (FTP, HTTP) to automatically install software from (<tt>.deb</tt> <i>packages</i>). This is done - preferably with the `apt' and `aptitude' programs. + preferably with the 'apt' and 'aptitude' programs. <P> You can install packages from the commandline using - <tt>apt-get</tt>. For example, if you want to install the packages - `commprog' and `maxgame', you can give the command + <tt>aptitude</tt>. For example, if you want to install the packages + 'commprog' and 'maxgame', you can give the command <P> <tt> - apt-get install commprog maxgame + aptitude install commprog maxgame </tt> <P> Note that you don't have to enter the complete path, or the - `<tt>.deb</tt>' extension. `Apt' will figure this out itself. + '<tt>.deb</tt>' extension. 'Apt' will figure this out itself. <P> Or use aptitude for a full screen interactive selection of available Debian packages. - - - - - - <P><HR><P><H2><A name="cdmanuf"> - CD/DVD Manufacturers - - - - </H2> </a> <p> @@ -489,23 +327,12 @@ For all needed information and contact addresses, please refer to <a href="http://www.debian.org/CD/">http://www.debian.org/CD/</a> </tt> - - - - - <P><HR><P><H2><A name="other"> - More Information - - - - </H2> </a> <p> - There is much more information present on this disc. Besides the already mentioned installation and upgrading procedures, this is the most interesting: <P> @@ -513,59 +340,32 @@ interesting: <P> <UL> <LI> - - - - <A href="doc/FAQ/">Debian FAQ</a> </LI> <LI> - - - - <A href="doc/constitution.txt">The Debian Constitution</a> </LI> <LI> - - - - <A href="doc/debian-manifesto">The Debian Manifesto</a> </LI> <LI> - - - - <A href="doc/social-contract.txt">Debian's Social Contract</a> </LI> <LI> - - - - <A href="doc/bug-reporting.txt">Bug reporting instructions</a> </LI> </UL> - - - - - - - <P> Also on the Internet are many resources. To name a few: <P> @@ -573,46 +373,26 @@ Also on the Internet are many resources. To name a few: <UL> <LI> - - - - <A href="http://www.debian.org/">The Debian homepage</a> </LI> <LI> - - - - <A href="http://www.debian.org/doc/">Debian Documentation</a> </LI> <LI> - - - - <A href="http://www.debian.org/support">Debian User Support</a> </LI> <LI> - - - - <A href="http://www.tldp.org/">The Linux Documentation Project</a> </LI> <LI> - - - - <A href="http://www.linux.org/">General Linux homepage</a> </LI> @@ -622,28 +402,14 @@ Also on the Internet are many resources. To name a few: <DIV align="center"> - - - - - <HR> - <SMALL>See the Debian <A href="http://www.debian.org/contact">contact page</A> - - - for information on contacting us. </SMALL><P> -<SMALL> - -Last Modified: Sat Mar 20 12:30:45 EST 2004 - -<br></SMALL> </DIV> </td> diff --git a/includes/etch/install/README.mirrors.html b/includes/etch/install/README.mirrors.html new file mode 100644 index 0000000..728fb73 --- /dev/null +++ b/includes/etch/install/README.mirrors.html @@ -0,0 +1,2616 @@ +<html> + +<head> + <title>Debian worldwide mirror sites</title> +</head> + +<body> +<h1 align="center">Debian worldwide mirror sites</h1> +<p>Debian is distributed (<em>mirrored</em>) 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. + +<p>Debian mirrors can be primary and secondary. The definitions are as follows: + + <blockquote> + A <strong>primary mirror</strong> site has good bandwidth, is available 24 hours a day, + and has an easy to remember name of the form ftp.<country>.debian.org. + <br> + They are all automatically updated whenever there are updates to + the Debian archive. + + </blockquote> + <blockquote> + A <strong>secondary mirror</strong> 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. + + </blockquote> +<p>Use the site closest to you for the fastest downloads possible whether it is + +a primary or secondary site. The program +<a href="http://packages.debian.org/stable/net/netselect"> +<em>netselect</em></a> can be used to +determine the site with the least latency; use a download program such as + +<a href="http://packages.debian.org/stable/web/wget"> +<em>wget</em></a> or +<a href="http://packages.debian.org/stable/net/rsync"> +<em>rsync</em></a> 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. + +<p>The authoritative copy of the following list can always be found at: +<a href="http://www.debian.org/mirror/list"> http://www.debian.org/mirror/list</a>.<br> +If you know of any mirrors that are missing from this list, +please have the site maintainer fill out the form at: +<a href="http://www.debian.org/mirror/submit"> http://www.debian.org/mirror/submit</a>.<br> +Everything else you want to know about Debian mirrors: +<a href="http://www.debian.org/mirror/"> http://www.debian.org/mirror/</a>.<br> + +<h2 align="center">Primary Debian mirror sites</h2> + +<table border="0" align="center"> +<tr> + <th>Country</th> + <th>Site</th> + <th>Architectures</th> +</tr> +<tr> + <td>Austria</td> + <td><a href="http://ftp.at.debian.org/debian/">ftp.at.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Australia</td> + <td><a href="http://ftp.au.debian.org/debian/">ftp.au.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Belgium</td> + <td><a href="http://ftp.be.debian.org/debian/">ftp.be.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Bulgaria</td> + <td><a href="http://ftp.bg.debian.org/debian/">ftp.bg.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Brazil</td> + <td><a href="http://ftp.br.debian.org/debian/">ftp.br.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Canada</td> + <td><a href="http://ftp.ca.debian.org/debian/">ftp.ca.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Switzerland</td> + <td><a href="http://ftp.ch.debian.org/debian/">ftp.ch.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Chile</td> + <td><a href="http://ftp.cl.debian.org/debian/">ftp.cl.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Czech Republic</td> + <td><a href="http://ftp.cz.debian.org/debian/">ftp.cz.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Germany</td> + <td><a href="http://ftp.de.debian.org/debian/">ftp.de.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Germany</td> + <td><a href="http://ftp2.de.debian.org/debian/">ftp2.de.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Denmark</td> + <td><a href="http://ftp.dk.debian.org/debian/">ftp.dk.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Estonia</td> + <td><a href="http://ftp.ee.debian.org/debian/">ftp.ee.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Spain</td> + <td><a href="http://ftp.es.debian.org/debian/">ftp.es.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Finland</td> + <td><a href="http://ftp.fi.debian.org/debian/">ftp.fi.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>France</td> + <td><a href="http://ftp.fr.debian.org/debian/">ftp.fr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>France</td> + <td><a href="http://ftp2.fr.debian.org/debian/">ftp2.fr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Great Britain</td> + <td><a href="http://ftp.uk.debian.org/debian/">ftp.uk.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Greece</td> + <td><a href="http://ftp.gr.debian.org/debian/">ftp.gr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Hong Kong</td> + <td><a href="http://ftp.hk.debian.org/debian/">ftp.hk.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> + <td>Croatia</td> + <td><a href="http://ftp.hr.debian.org/debian/">ftp.hr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Hungary</td> + <td><a href="http://ftp.hu.debian.org/debian/">ftp.hu.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Ireland</td> + <td><a href="http://ftp.ie.debian.org/debian/">ftp.ie.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Iceland</td> + <td><a href="http://ftp.is.debian.org/debian/">ftp.is.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Italy</td> + <td><a href="http://ftp.it.debian.org/debian/">ftp.it.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Japan</td> + <td><a href="http://ftp.jp.debian.org/debian/">ftp.jp.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Japan</td> + <td><a href="http://ftp2.jp.debian.org/debian/">ftp2.jp.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Korea</td> + <td><a href="http://ftp.kr.debian.org/debian/">ftp.kr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Mexico</td> + <td><a href="http://ftp.mx.debian.org/debian/">ftp.mx.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Netherlands</td> + <td><a href="http://ftp.nl.debian.org/debian/">ftp.nl.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Norway</td> + <td><a href="http://ftp.no.debian.org/debian/">ftp.no.debian.org/debian/</a></td> + <td><small><small>amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> + <td>New Zealand</td> + <td><a href="http://ftp.nz.debian.org/debian/">ftp.nz.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Poland</td> + <td><a href="http://ftp.pl.debian.org/debian/">ftp.pl.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Portugal</td> + <td><a href="http://ftp.pt.debian.org/debian/">ftp.pt.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Romania</td> + <td><a href="http://ftp.ro.debian.org/debian/">ftp.ro.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Russia</td> + <td><a href="http://ftp.ru.debian.org/debian/">ftp.ru.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Sweden</td> + <td><a href="http://ftp.se.debian.org/debian/">ftp.se.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Slovenia</td> + <td><a href="http://ftp.si.debian.org/debian/">ftp.si.debian.org/debian/</a></td> + <td><small><small>alpha amd64 i386 ia64 m68k powerpc sparc</small></small></td> +</tr> +<tr> + <td>Slovakia</td> + <td><a href="http://ftp.sk.debian.org/debian/">ftp.sk.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Turkey</td> + <td><a href="http://ftp.tr.debian.org/debian/">ftp.tr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Taiwan</td> + <td><a href="http://ftp.tw.debian.org/debian/">ftp.tw.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>United States</td> + <td><a href="http://ftp.us.debian.org/debian/">ftp.us.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +</table> +<h2 align="center">Secondary mirrors of the Debian archive</h2> + +<table border="0" align="center"> +<tr> + <th>Host name</th> + <th>FTP</th> + <th>HTTP</th> + <th>Architectures</th> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>AR Argentina</strong></big></td></tr> + +<tr> +<td valign=top>debian.logiclinux.com</td> +<td></td> +<td valign=top><a href="http://debian.logiclinux.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ccc.uba.ar</td> +<td valign=top><a href="ftp://ftp.ccc.uba.ar/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.ccc.uba.ar/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.torredehanoi.org</td> +<td valign=top><a href="ftp://debian.torredehanoi.org/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.torredehanoi.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>AT Austria</strong></big></td></tr> + +<tr> +<td valign=top>ftp.at.debian.org<br> (debian.sil.at)</td> +<td valign=top><a href="ftp://ftp.at.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.at.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>gd.tuwien.ac.at</td> +<td valign=top><a href="ftp://gd.tuwien.ac.at/opsys/linux/debian/">/opsys/linux/debian/</a></td> +<td valign=top><a href="http://gd.tuwien.ac.at/opsys/linux/debian/">/opsys/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mur.at</td> +<td valign=top><a href="ftp://debian.mur.at/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mur.at/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>ftp.tu-graz.ac.at</td> +<td valign=top><a href="ftp://ftp.tu-graz.ac.at/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><a href="http://ftp.tu-graz.ac.at/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.univie.ac.at</td> +<td valign=top><a href="ftp://ftp.univie.ac.at/systems/linux/debian/debian/">/systems/linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.univie.ac.at/systems/linux/debian/debian/">/systems/linux/debian/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.inode.at</td> +<td valign=top><a href="ftp://debian.inode.at/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.inode.at/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>esda.wu-wien.ac.at</td> +<td valign=top><a href="ftp://esda.wu-wien.ac.at/pub/debian/">/pub/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.lagis.at</td> +<td valign=top><a href="ftp://debian.lagis.at/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.lagis.at/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>AU Australia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.au.debian.org<br> (mirror.linux.org.au)</td> +<td valign=top><a href="ftp://ftp.au.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.au.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.aarnet.edu.au</td> +<td valign=top><a href="ftp://mirror.aarnet.edu.au/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.aarnet.edu.au/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.monash.edu.au</td> +<td valign=top><a href="ftp://ftp.monash.edu.au/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://ftp.monash.edu.au/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uwa.edu.au</td> +<td valign=top><a href="ftp://ftp.uwa.edu.au/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uwa.edu.au/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.eftel.com</td> +<td valign=top><a href="ftp://mirror.eftel.com/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.eftel.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.pacific.net.au</td> +<td valign=top><a href="ftp://mirror.pacific.net.au/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.pacific.net.au/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.iinet.net.au</td> +<td valign=top><a href="ftp://ftp.iinet.net.au/debian/debian/">/debian/debian/</a></td> +<td valign=top><a href="http://ftp.iinet.net.au/debian/debian/">/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.optus.net</td> +<td valign=top><a href="ftp://mirror.optus.net/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.optus.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.cse.unsw.edu.au</td> +<td valign=top><a href="ftp://mirror.cse.unsw.edu.au/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.cse.unsw.edu.au/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.3fl.net.au</td> +<td valign=top><a href="ftp://mirror.3fl.net.au/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://mirror.3fl.net.au/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.netspace.net.au</td> +<td valign=top><a href="ftp://ftp.netspace.net.au/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.netspace.net.au/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>BE Belgium</strong></big></td></tr> + +<tr> +<td valign=top>ftp.be.debian.org<br> (ftp.belnet.be)</td> +<td valign=top><a href="ftp://ftp.be.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.be.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.kulnet.kuleuven.ac.be</td> +<td valign=top><a href="ftp://ftp.kulnet.kuleuven.ac.be/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.kulnet.kuleuven.ac.be/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.easynet.be</td> +<td valign=top><a href="ftp://ftp.easynet.be/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.easynet.be/ftp/debian/">/ftp/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debian.skynet.be</td> +<td valign=top><a href="ftp://ftp.debian.skynet.be/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.debian.skynet.be/ftp/debian/">/ftp/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.be.gbxs.net</td> +<td valign=top><a href="ftp://mirror.be.gbxs.net/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.be.gbxs.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>BG Bulgaria</strong></big></td></tr> + +<tr> +<td valign=top>ftp.bg.debian.org<br> (debian.spnet.net)</td> +<td valign=top><a href="ftp://ftp.bg.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.bg.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.ludost.net</td> +<td valign=top><a href="ftp://debian.ludost.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ludost.net/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uni-sofia.bg</td> +<td valign=top><a href="ftp://ftp.uni-sofia.bg/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uni-sofia.bg/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.telecoms.bg</td> +<td valign=top><a href="ftp://debian.telecoms.bg/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.telecoms.bg/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mnet.bg</td> +<td valign=top><a href="ftp://debian.mnet.bg/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mnet.bg/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.networx-bg.com</td> +<td valign=top><a href="ftp://debian.networx-bg.com/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.networx-bg.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>BR Brazil</strong></big></td></tr> + +<tr> +<td valign=top>ftp.br.debian.org<br> (debian.c3sl.ufpr.br)</td> +<td valign=top><a href="ftp://ftp.br.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.br.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.das.ufsc.br</td> +<td valign=top><a href="ftp://debian.das.ufsc.br/pub/debian/">/pub/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>download.unesp.br</td> +<td></td> +<td valign=top><a href="http://download.unesp.br/linux/debian/">/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>sft.if.usp.br</td> +<td></td> +<td valign=top><a href="http://sft.if.usp.br/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>linorg.usp.br</td> +<td valign=top><a href="ftp://linorg.usp.br/debian/">/debian/</a></td> +<td valign=top><a href="http://linorg.usp.br/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>linux.iq.usp.br</td> +<td></td> +<td valign=top><a href="http://linux.iq.usp.br/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.pucpr.br</td> +<td valign=top><a href="ftp://ftp.pucpr.br/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.las.ic.unicamp.br</td> +<td valign=top><a href="ftp://debian.las.ic.unicamp.br/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.las.ic.unicamp.br/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.pop-sc.rnp.br</td> +<td></td> +<td valign=top><a href="http://debian.pop-sc.rnp.br/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>BY Belarus</strong></big></td></tr> + +<tr> +<td valign=top>linux.org.by</td> +<td valign=top><a href="ftp://linux.org.by/debian/">/debian/</a></td> +<td valign=top><a href="http://linux.org.by/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.mgts.by</td> +<td valign=top><a href="ftp://ftp.mgts.by/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.mgts.by/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>CA Canada</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ca.debian.org</td> +<td valign=top><a href="ftp://ftp.ca.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ca.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.yorku.ca</td> +<td></td> +<td valign=top><a href="http://debian.yorku.ca/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp3.nrc.ca</td> +<td valign=top><a href="ftp://ftp3.nrc.ca/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp3.nrc.ca/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>gulus.usherbrooke.ca</td> +<td valign=top><a href="ftp://gulus.usherbrooke.ca/debian/">/debian/</a></td> +<td valign=top><a href="http://gulus.usherbrooke.ca/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.cpsc.ucalgary.ca</td> +<td valign=top><a href="ftp://mirror.cpsc.ucalgary.ca/mirror/debian.org/debian/">/mirror/debian.org/debian/</a></td> +<td valign=top><a href="http://mirror.cpsc.ucalgary.ca/mirror/debian.org/debian/">/mirror/debian.org/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.peer1.net</td> +<td></td> +<td valign=top><a href="http://mirror.peer1.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel i386 mips mipsel powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.rafal.ca</td> +<td valign=top><a href="ftp://debian.mirror.rafal.ca/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirror.rafal.ca/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.savoirfairelinux.net</td> +<td valign=top><a href="ftp://debian.savoirfairelinux.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.savoirfairelinux.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.iweb.ca</td> +<td valign=top><a href="ftp://debian.mirror.iweb.ca/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirror.iweb.ca/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.publicns.net</td> +<td valign=top><a href="ftp://mirror.publicns.net/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://mirror.publicns.net/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>amd64 armel i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.csclub.uwaterloo.ca</td> +<td valign=top><a href="ftp://mirror.csclub.uwaterloo.ca/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.csclub.uwaterloo.ca/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>CH Switzerland</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ch.debian.org<br> (debian.ethz.ch)</td> +<td valign=top><a href="ftp://ftp.ch.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ch.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.switch.ch</td> +<td valign=top><a href="ftp://mirror.switch.ch/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><a href="http://mirror.switch.ch/ftp/mirror/debian/">/ftp/mirror/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.csg.uzh.ch</td> +<td></td> +<td valign=top><a href="http://debian.csg.uzh.ch/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>CL Chile</strong></big></td></tr> + +<tr> +<td valign=top>ftp.cl.debian.org<br> (debian.ciencias.uchile.cl)</td> +<td valign=top><a href="ftp://ftp.cl.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.cl.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.ubiobio.cl</td> +<td></td> +<td valign=top><a href="http://debian.ubiobio.cl/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.utalca.cl</td> +<td></td> +<td valign=top><a href="http://debian.utalca.cl/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.debian.cl</td> +<td></td> +<td valign=top><a href="http://mirror.debian.cl/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.debianchile.cl</td> +<td></td> +<td valign=top><a href="http://mirror.debianchile.cl/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>CN China</strong></big></td></tr> + +<tr> +<td valign=top>mirrors.geekbone.org</td> +<td valign=top><a href="ftp://mirrors.geekbone.org/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.geekbone.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.cn99.com</td> +<td valign=top><a href="ftp://debian.cn99.com/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.cn99.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>www.anheng.com.cn</td> +<td valign=top><a href="ftp://www.anheng.com.cn/debian/">/debian/</a></td> +<td valign=top><a href="http://www.anheng.com.cn/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>CZ Czech Republic</strong></big></td></tr> + +<tr> +<td valign=top>ftp.cz.debian.org<br> (ftp.debian.cz)</td> +<td valign=top><a href="ftp://ftp.cz.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.cz.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.sh.cvut.cz</td> +<td valign=top><a href="ftp://debian.sh.cvut.cz/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.sh.cvut.cz/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.zcu.cz</td> +<td valign=top><a href="ftp://ftp.zcu.cz/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><a href="http://ftp.zcu.cz/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.web4u.cz</td> +<td valign=top><a href="ftp://debian.mirror.web4u.cz/">/</a></td> +<td valign=top><a href="http://debian.mirror.web4u.cz/">/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.cvut.cz</td> +<td valign=top><a href="ftp://ftp.cvut.cz/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.cvut.cz/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>debian.ignum.cz</td> +<td valign=top><a href="ftp://debian.ignum.cz/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ignum.cz/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>DE Germany</strong></big></td></tr> + +<tr> +<td valign=top>ftp.de.debian.org<br> (debian.inf.tu-dresden.de)</td> +<td valign=top><a href="ftp://ftp.de.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.de.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp2.de.debian.org<br> (ftp.rfc822.org)</td> +<td valign=top><a href="ftp://ftp2.de.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp2.de.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.tu-clausthal.de</td> +<td valign=top><a href="ftp://ftp.tu-clausthal.de/pub/linux/debian/">/pub/linux/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 arm armel i386 ia64 m68k mips powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.uni-duisburg-essen.de</td> +<td valign=top><a href="ftp://debian.uni-duisburg-essen.de/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.uni-duisburg-essen.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.freenet.de</td> +<td valign=top><a href="ftp://ftp.freenet.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.freenet.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.informatik.rwth-aachen.de</td> +<td valign=top><a href="ftp://ftp.informatik.rwth-aachen.de/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td valign=top><a href="http://ftp.informatik.rwth-aachen.de/ftp/pub/Linux/debian/">/ftp/pub/Linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp-stud.fht-esslingen.de</td> +<td valign=top><a href="ftp://ftp-stud.fht-esslingen.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp-stud.fht-esslingen.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.stw-bonn.de</td> +<td valign=top><a href="ftp://ftp.stw-bonn.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.stw-bonn.de/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.fu-berlin.de</td> +<td valign=top><a href="ftp://ftp.fu-berlin.de/pub/unix/linux/mirrors/debian/">/pub/unix/linux/mirrors/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.tu-bs.de</td> +<td valign=top><a href="ftp://debian.tu-bs.de/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.tu-bs.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uni-koeln.de</td> +<td valign=top><a href="ftp://ftp.uni-koeln.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uni-koeln.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.mpi-sb.mpg.de</td> +<td valign=top><a href="ftp://ftp.mpi-sb.mpg.de/pub/linux/debian/">/pub/linux/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.tiscali.de</td> +<td valign=top><a href="ftp://ftp.tiscali.de/pub/debian/debian/">/pub/debian/debian/</a></td> +<td valign=top><a href="http://ftp.tiscali.de/pub/debian/debian/">/pub/debian/debian/</a></td> +<td valign=top><small><small>amd64 arm armel hurd-i386 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>ftp.tu-chemnitz.de</td> +<td valign=top><a href="ftp://ftp.tu-chemnitz.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.tu-chemnitz.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uni-kl.de</td> +<td valign=top><a href="ftp://ftp.uni-kl.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uni-kl.de/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uni-bayreuth.de</td> +<td valign=top><a href="ftp://ftp.uni-bayreuth.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uni-bayreuth.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.informatik.hu-berlin.de</td> +<td valign=top><a href="ftp://ftp.informatik.hu-berlin.de/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp5.gwdg.de</td> +<td valign=top><a href="ftp://ftp5.gwdg.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp5.gwdg.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.hosteurope.de</td> +<td valign=top><a href="ftp://ftp.hosteurope.de/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://ftp.hosteurope.de/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.informatik.uni-frankfurt.de</td> +<td valign=top><a href="ftp://ftp.informatik.uni-frankfurt.de/pub/Mirrors/debian.org/debian/">/pub/Mirrors/debian.org/debian/</a></td> +<td valign=top><a href="http://ftp.informatik.uni-frankfurt.de/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.netcologne.de</td> +<td valign=top><a href="ftp://debian.netcologne.de/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.netcologne.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>artfiles.org</td> +<td valign=top><a href="ftp://artfiles.org/debian/">/debian/</a></td> +<td valign=top><a href="http://artfiles.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.intergenia.de</td> +<td></td> +<td valign=top><a href="http://debian.intergenia.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.cruisix.net</td> +<td valign=top><a href="ftp://debian.cruisix.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.cruisix.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.rrzn.uni-hannover.de</td> +<td valign=top><a href="ftp://ftp.rrzn.uni-hannover.de/debian/debian/">/debian/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.charite.de</td> +<td></td> +<td valign=top><a href="http://debian.charite.de/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.plusline.de</td> +<td valign=top><a href="ftp://ftp.plusline.de/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.plusline.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>sinclair.farm.ftbfs.de</td> +<td></td> +<td valign=top><a href="http://sinclair.farm.ftbfs.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.halifax.rwth-aachen.de</td> +<td valign=top><a href="ftp://ftp.halifax.rwth-aachen.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.halifax.rwth-aachen.de/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>DK Denmark</strong></big></td></tr> + +<tr> +<td valign=top>ftp.dk.debian.org<br> (mirrors.dotsrc.org)</td> +<td valign=top><a href="ftp://ftp.dk.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.dk.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.dkuug.dk</td> +<td valign=top><a href="ftp://ftp.dkuug.dk/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.dkuug.dk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.here.dk</td> +<td valign=top><a href="ftp://mirror.here.dk/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.here.dk/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 mips powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.uni-c.dk</td> +<td></td> +<td valign=top><a href="http://debian.uni-c.dk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.telianet.dk</td> +<td valign=top><a href="ftp://mirrors.telianet.dk/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.telianet.dk/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debianmirror.wwi.dk</td> +<td></td> +<td valign=top><a href="http://debianmirror.wwi.dk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>EE Estonia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ee.debian.org<br> (ftp.aso.ee)</td> +<td valign=top><a href="ftp://ftp.ee.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ee.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>ES Spain</strong></big></td></tr> + +<tr> +<td valign=top>ftp.es.debian.org<br> (ulises.hostalia.com)</td> +<td valign=top><a href="ftp://ftp.es.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.es.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.rediris.es</td> +<td valign=top><a href="ftp://ftp.rediris.es/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.rediris.es/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.cica.es</td> +<td valign=top><a href="ftp://ftp.cica.es/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.cica.es/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.caliu.cat</td> +<td valign=top><a href="ftp://ftp.caliu.cat/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.caliu.cat/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.gva.es</td> +<td valign=top><a href="ftp://ftp.gva.es/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><a href="http://ftp.gva.es/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.gul.uc3m.es</td> +<td valign=top><a href="ftp://ftp.gul.uc3m.es/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.gul.uc3m.es/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.um.es</td> +<td valign=top><a href="ftp://ftp.um.es/mirror/debian/">/mirror/debian/</a></td> +<td></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>jane.uab.cat</td> +<td valign=top><a href="ftp://jane.uab.cat/debian/">/debian/</a></td> +<td valign=top><a href="http://jane.uab.cat/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.udc.es</td> +<td valign=top><a href="ftp://ftp.udc.es/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.udc.es/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.grn.cat</td> +<td valign=top><a href="ftp://debian.grn.cat/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.grn.cat/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.com.es</td> +<td valign=top><a href="ftp://debian.com.es/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.com.es/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>FI Finland</strong></big></td></tr> + +<tr> +<td valign=top>ftp.fi.debian.org<br> (trumpetti.atm.tut.fi)</td> +<td valign=top><a href="ftp://ftp.fi.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.fi.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.funet.fi</td> +<td valign=top><a href="ftp://ftp.funet.fi/pub/linux/mirrors/debian/">/pub/linux/mirrors/debian/</a></td> +<td valign=top><a href="http://ftp.funet.fi/pub/linux/mirrors/debian/">/pub/linux/mirrors/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.jyu.fi</td> +<td valign=top><a href="ftp://ftp.jyu.fi/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.jyu.fi/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 hurd-i386 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.seclan.com</td> +<td valign=top><a href="ftp://ftp.seclan.com/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.seclan.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>FR France</strong></big></td></tr> + +<tr> +<td valign=top>ftp.fr.debian.org<br> (debian.proxad.net)</td> +<td valign=top><a href="ftp://ftp.fr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.fr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp2.fr.debian.org<br> (ftp.oleane.net)</td> +<td valign=top><a href="ftp://ftp2.fr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp2.fr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.iut-bm.univ-fcomte.fr</td> +<td valign=top><a href="ftp://ftp.iut-bm.univ-fcomte.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.iut-bm.univ-fcomte.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.eudil.fr</td> +<td valign=top><a href="ftp://ftp.eudil.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.eudil.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.proxad.net</td> +<td valign=top><a href="ftp://ftp.proxad.net/mirrors/ftp.debian.org/">/mirrors/ftp.debian.org/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.lip6.fr</td> +<td valign=top><a href="ftp://ftp.lip6.fr/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><a href="http://ftp.lip6.fr/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.ens-cachan.fr</td> +<td valign=top><a href="ftp://debian.ens-cachan.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ens-cachan.fr/ftp/debian/">/ftp/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.u-picardie.fr</td> +<td valign=top><a href="ftp://ftp.u-picardie.fr/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><a href="http://ftp.u-picardie.fr/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirrors.easynet.fr</td> +<td valign=top><a href="ftp://debian.mirrors.easynet.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirrors.easynet.fr/">/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.u-strasbg.fr</td> +<td valign=top><a href="ftp://ftp.u-strasbg.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.u-strasbg.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 hurd-i386 i386 ia64 m68k powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.cict.fr</td> +<td valign=top><a href="ftp://debian.cict.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.cict.fr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm armel hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>mir1.ovh.net</td> +<td valign=top><a href="ftp://mir1.ovh.net/debian/">/debian/</a></td> +<td valign=top><a href="http://mir1.ovh.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mir2.ovh.net</td> +<td></td> +<td valign=top><a href="http://mir2.ovh.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.nerim.net</td> +<td valign=top><a href="ftp://ftp.nerim.net/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.nerim.net/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.crihan.fr</td> +<td valign=top><a href="ftp://ftp.crihan.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.crihan.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mines.inpl-nancy.fr</td> +<td valign=top><a href="ftp://debian.mines.inpl-nancy.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mines.inpl-nancy.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debian.ikoula.com</td> +<td valign=top><a href="ftp://ftp.debian.ikoula.com/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>webb.ens-cachan.fr</td> +<td valign=top><a href="ftp://webb.ens-cachan.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://webb.ens-cachan.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.ircam.fr</td> +<td valign=top><a href="ftp://mirrors.ircam.fr/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://mirrors.ircam.fr/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.inra.fr</td> +<td valign=top><a href="ftp://debian.mirror.inra.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirror.inra.fr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm armel i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.med.univ-tours.fr</td> +<td valign=top><a href="ftp://debian.med.univ-tours.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.med.univ-tours.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.univ-pau.fr</td> +<td valign=top><a href="ftp://ftp.univ-pau.fr/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><a href="http://ftp.univ-pau.fr/linux/mirrors/debian/">/linux/mirrors/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.univ-nantes.fr</td> +<td valign=top><a href="ftp://ftp.univ-nantes.fr/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.compuscene.org</td> +<td></td> +<td valign=top><a href="http://mirrors.compuscene.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.revolsys.fr</td> +<td valign=top><a href="ftp://debian.revolsys.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.revolsys.fr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.univ-reims.fr</td> +<td valign=top><a href="ftp://debian.univ-reims.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.univ-reims.fr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>GB Great Britain</strong></big></td></tr> + +<tr> +<td valign=top>ftp.uk.debian.org<br> (debian.hands.com)</td> +<td valign=top><a href="ftp://ftp.uk.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uk.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.man.ac.uk</td> +<td></td> +<td valign=top><a href="http://debian.man.ac.uk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>www.mirrorservice.org</td> +<td valign=top><a href="ftp://www.mirrorservice.org/sites/ftp.debian.org/debian/">/sites/ftp.debian.org/debian/</a></td> +<td valign=top><a href="http://www.mirrorservice.org/sites/ftp.debian.org/debian/">/sites/ftp.debian.org/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ticklers.org</td> +<td valign=top><a href="ftp://ftp.ticklers.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ticklers.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.virginmedia.com</td> +<td valign=top><a href="ftp://debian.virginmedia.com/mirrors/ftp.debian.org">/mirrors/ftp.debian.org</a></td> +<td valign=top><a href="http://debian.virginmedia.com/">/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.positive-internet.com</td> +<td valign=top><a href="ftp://mirror.positive-internet.com/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.positive-internet.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hppa i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>the.earth.li</td> +<td valign=top><a href="ftp://the.earth.li/debian/">/debian/</a></td> +<td valign=top><a href="http://the.earth.li/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>ukdebian.mirror.anlx.net</td> +<td valign=top><a href="ftp://ukdebian.mirror.anlx.net/debian/">/debian/</a></td> +<td valign=top><a href="http://ukdebian.mirror.anlx.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.ox.ac.uk</td> +<td valign=top><a href="ftp://mirror.ox.ac.uk/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.ox.ac.uk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.zetnet.co.uk</td> +<td valign=top><a href="ftp://debian.zetnet.co.uk/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.zetnet.co.uk/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 mipsel</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>GE Georgia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ifg.gtu.ge</td> +<td valign=top><a href="ftp://ftp.ifg.gtu.ge/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>GR Greece</strong></big></td></tr> + +<tr> +<td valign=top>ftp.gr.debian.org<br> (ftp.ntua.gr)</td> +<td valign=top><a href="ftp://ftp.gr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.gr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.otenet.gr</td> +<td valign=top><a href="ftp://debian.otenet.gr/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://debian.otenet.gr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.duth.gr</td> +<td valign=top><a href="ftp://ftp.duth.gr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.duth.gr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.softnet.tuc.gr</td> +<td valign=top><a href="ftp://ftp.softnet.tuc.gr/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://ftp.softnet.tuc.gr/ftp/linux/debian/">/ftp/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.cc.uoc.gr</td> +<td valign=top><a href="ftp://ftp.cc.uoc.gr/mirrors/linux/debian/">/mirrors/linux/debian/</a></td> +<td valign=top><a href="http://ftp.cc.uoc.gr/mirrors/linux/debian/">/mirrors/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>HK Hong Kong</strong></big></td></tr> + +<tr> +<td valign=top>ftp.hk.debian.org</td> +<td valign=top><a href="ftp://ftp.hk.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.hk.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>www.zentek-international.com</td> +<td></td> +<td valign=top><a href="http://www.zentek-international.com/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>HR Croatia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.hr.debian.org<br> (debian.carnet.hr)</td> +<td valign=top><a href="ftp://ftp.hr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.hr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.irb.hr</td> +<td valign=top><a href="ftp://ftp.irb.hr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.irb.hr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.carnet.hr</td> +<td valign=top><a href="ftp://ftp.carnet.hr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.carnet.hr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.iskon.hr</td> +<td valign=top><a href="ftp://debian.iskon.hr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.iskon.hr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64 s390</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>HU Hungary</strong></big></td></tr> + +<tr> +<td valign=top>ftp.hu.debian.org<br> (ftp.fsn.hu)</td> +<td valign=top><a href="ftp://ftp.hu.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.hu.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.kfki.hu</td> +<td valign=top><a href="ftp://ftp.kfki.hu/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://ftp.kfki.hu/linux/debian/">/linux/debian/</a></td> +<td valign=top><small><small>alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.bme.hu</td> +<td valign=top><a href="ftp://ftp.bme.hu/OS/Linux/dist/debian/">/OS/Linux/dist/debian/</a></td> +<td valign=top><a href="http://ftp.bme.hu/OS/Linux/dist/debian/">/OS/Linux/dist/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirrors.crysys.hu</td> +<td valign=top><a href="ftp://debian.mirrors.crysys.hu/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirrors.crysys.hu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.sth.sze.hu</td> +<td valign=top><a href="ftp://debian.sth.sze.hu/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.sth.sze.hu/">/</a></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>ID Indonesia</strong></big></td></tr> + +<tr> +<td valign=top>kebo.vlsm.org</td> +<td valign=top><a href="ftp://kebo.vlsm.org/debian/">/debian/</a></td> +<td valign=top><a href="http://kebo.vlsm.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.indika.net.id</td> +<td></td> +<td valign=top><a href="http://debian.indika.net.id/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>IE Ireland</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ie.debian.org<br> (debian.heanet.ie)</td> +<td valign=top><a href="ftp://ftp.ie.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ie.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.esat.net</td> +<td valign=top><a href="ftp://ftp.esat.net/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://ftp.esat.net/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>IL Israel</strong></big></td></tr> + +<tr> +<td valign=top>debian.co.il</td> +<td></td> +<td valign=top><a href="http://debian.co.il/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.isoc.org.il</td> +<td></td> +<td valign=top><a href="http://mirror.isoc.org.il/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>IN India</strong></big></td></tr> + +<tr> +<td valign=top>ftp.iitm.ac.in</td> +<td valign=top><a href="ftp://ftp.iitm.ac.in/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.iitm.ac.in/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>IS Iceland</strong></big></td></tr> + +<tr> +<td valign=top>ftp.is.debian.org<br> (ftp.rhnet.is)</td> +<td valign=top><a href="ftp://ftp.is.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.is.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>IT Italy</strong></big></td></tr> + +<tr> +<td valign=top>ftp.it.debian.org<br> (ftp.bofh.it)</td> +<td valign=top><a href="ftp://ftp.it.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.it.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>giano.com.dist.unige.it</td> +<td valign=top><a href="ftp://giano.com.dist.unige.it/debian/">/debian/</a></td> +<td valign=top><a href="http://giano.com.dist.unige.it/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm armel i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.bononia.it</td> +<td valign=top><a href="ftp://ftp.bononia.it/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.bononia.it/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>freedom.dicea.unifi.it</td> +<td valign=top><a href="ftp://freedom.dicea.unifi.it/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://freedom.dicea.unifi.it/ftp/pub/linux/debian/">/ftp/pub/linux/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.eutelia.it</td> +<td valign=top><a href="ftp://ftp.eutelia.it/pub/Debian_Mirror/">/pub/Debian_Mirror/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mi.mirror.garr.it</td> +<td valign=top><a href="ftp://mi.mirror.garr.it/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><a href="http://mi.mirror.garr.it/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.fastweb.it</td> +<td valign=top><a href="ftp://debian.fastweb.it/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.fastweb.it/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.unina.it</td> +<td valign=top><a href="ftp://ftp.unina.it/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><a href="http://ftp.unina.it/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.dynamica.it</td> +<td valign=top><a href="ftp://debian.dynamica.it/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.dynamica.it/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.units.it</td> +<td></td> +<td valign=top><a href="http://mirror.units.it/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>JP Japan</strong></big></td></tr> + +<tr> +<td valign=top>ftp2.jp.debian.org<br> (ftp.debian.or.jp)</td> +<td valign=top><a href="ftp://ftp2.jp.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp2.jp.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.jp.debian.org<br> (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)</td> +<td></td> +<td valign=top><a href="http://ftp.jp.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.nara.wide.ad.jp</td> +<td valign=top><a href="ftp://ftp.nara.wide.ad.jp/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.nara.wide.ad.jp/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ring.asahi-net.or.jp</td> +<td valign=top><a href="ftp://ring.asahi-net.or.jp/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://ring.asahi-net.or.jp/archives/linux/debian/debian/">/archives/linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.dti.ad.jp</td> +<td valign=top><a href="ftp://ftp.dti.ad.jp/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td valign=top><a href="http://ftp.dti.ad.jp/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>dennou-k.gfd-dennou.org</td> +<td valign=top><a href="ftp://dennou-k.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><a href="http://dennou-k.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>dennou-q.gfd-dennou.org</td> +<td valign=top><a href="ftp://dennou-q.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><a href="http://dennou-q.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>sb.itc.u-tokyo.ac.jp</td> +<td valign=top><a href="ftp://sb.itc.u-tokyo.ac.jp/DEBIAN/">/DEBIAN/</a></td> +<td valign=top><a href="http://sb.itc.u-tokyo.ac.jp/DEBIAN/">/DEBIAN/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.riken.jp</td> +<td valign=top><a href="ftp://ftp.riken.jp/Linux/debian/debian/">/Linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.riken.jp/Linux/debian/debian/">/Linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.shimpinomori.net</td> +<td></td> +<td valign=top><a href="http://debian.shimpinomori.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>www.ring.gr.jp</td> +<td valign=top><a href="ftp://www.ring.gr.jp/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://www.ring.gr.jp/archives/linux/debian/debian/">/archives/linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.jaist.ac.jp</td> +<td valign=top><a href="ftp://ftp.jaist.ac.jp/pub/Linux/Debian/">/pub/Linux/Debian/</a></td> +<td valign=top><a href="http://ftp.jaist.ac.jp/pub/Linux/Debian/">/pub/Linux/Debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>www.cohsoft.com</td> +<td></td> +<td valign=top><a href="http://www.cohsoft.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>dennou-h.gfd-dennou.org</td> +<td valign=top><a href="ftp://dennou-h.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><a href="http://dennou-h.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>KR Korea</strong></big></td></tr> + +<tr> +<td valign=top>ftp.kr.debian.org<br> (ftp.kaist.ac.kr)</td> +<td valign=top><a href="ftp://ftp.kr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.kr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.daum.net</td> +<td valign=top><a href="ftp://ftp.daum.net/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.daum.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>LT Lithuania</strong></big></td></tr> + +<tr> +<td valign=top>ameba.sc-uni.ktu.lt</td> +<td valign=top><a href="ftp://ameba.sc-uni.ktu.lt/debian/">/debian/</a></td> +<td valign=top><a href="http://ameba.sc-uni.ktu.lt/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.balt.net</td> +<td valign=top><a href="ftp://debian.balt.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.balt.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm armel i386 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>LV Latvia</strong></big></td></tr> + +<tr> +<td valign=top>koyanet.lv</td> +<td valign=top><a href="ftp://koyanet.lv/debian/">/debian/</a></td> +<td valign=top><a href="http://koyanet.lv/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>MT Malta</strong></big></td></tr> + +<tr> +<td valign=top>debian.eng.um.edu.mt</td> +<td></td> +<td valign=top><a href="http://debian.eng.um.edu.mt/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>MX Mexico</strong></big></td></tr> + +<tr> +<td valign=top>ftp.mx.debian.org<br> (debian.unam.mx)</td> +<td valign=top><a href="ftp://ftp.mx.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.mx.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mmc.igeofcu.unam.mx</td> +<td></td> +<td valign=top><a href="http://mmc.igeofcu.unam.mx/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>NC New Caledonia</strong></big></td></tr> + +<tr> +<td valign=top>debian.nautile.nc</td> +<td valign=top><a href="ftp://debian.nautile.nc/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.nautile.nc/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>NI Nicaragua</strong></big></td></tr> + +<tr> +<td valign=top>debian.uni.edu.ni</td> +<td></td> +<td valign=top><a href="http://debian.uni.edu.ni/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>NL Netherlands</strong></big></td></tr> + +<tr> +<td valign=top>ftp.nl.debian.org<br> (ftp.snt.utwente.nl)</td> +<td valign=top><a href="ftp://ftp.nl.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.nl.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.nluug.nl</td> +<td valign=top><a href="ftp://ftp.nluug.nl/pub/os/Linux/distr/debian/">/pub/os/Linux/distr/debian/</a></td> +<td valign=top><a href="http://ftp.nluug.nl/pub/os/Linux/distr/debian/">/pub/os/Linux/distr/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.surfnet.nl</td> +<td valign=top><a href="ftp://ftp.surfnet.nl/pub/os/Linux/distr/debian/">/pub/os/Linux/distr/debian/</a></td> +<td valign=top><a href="http://ftp.surfnet.nl/os/Linux/distr/debian/">/os/Linux/distr/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debian.nl</td> +<td valign=top><a href="ftp://ftp.debian.nl/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.debian.nl/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.tiscali.nl</td> +<td valign=top><a href="ftp://ftp.tiscali.nl/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><a href="http://ftp.tiscali.nl/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>NO Norway</strong></big></td></tr> + +<tr> +<td valign=top>ftp.no.debian.org<br> (ftp.uninett.no)</td> +<td valign=top><a href="ftp://ftp.no.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.no.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>NZ New Zealand</strong></big></td></tr> + +<tr> +<td valign=top>ftp.nz.debian.org<br> (ftp.citylink.co.nz)</td> +<td valign=top><a href="ftp://ftp.nz.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.nz.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.ihug.co.nz</td> +<td valign=top><a href="ftp://debian.ihug.co.nz/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ihug.co.nz/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>PF French Polynesia</strong></big></td></tr> + +<tr> +<td valign=top>repository.linux.pf</td> +<td valign=top><a href="ftp://repository.linux.pf/debian/">/debian/</a></td> +<td valign=top><a href="http://repository.linux.pf/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>PL Poland</strong></big></td></tr> + +<tr> +<td valign=top>ftp.pl.debian.org<br> (ftp.task.gda.pl)</td> +<td valign=top><a href="ftp://ftp.pl.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.pl.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.icm.edu.pl</td> +<td valign=top><a href="ftp://ftp.icm.edu.pl/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td valign=top><a href="http://ftp.icm.edu.pl/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 armel hurd-i386 i386 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.man.szczecin.pl</td> +<td valign=top><a href="ftp://ftp.man.szczecin.pl/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.vectranet.pl</td> +<td valign=top><a href="ftp://ftp.vectranet.pl/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.vectranet.pl/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.pwr.wroc.pl</td> +<td valign=top><a href="ftp://ftp.pwr.wroc.pl/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.pwr.wroc.pl/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.man.poznan.pl</td> +<td valign=top><a href="ftp://ftp.man.poznan.pl/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.man.poznan.pl/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>piotrkosoft.net</td> +<td valign=top><a href="ftp://piotrkosoft.net/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><a href="http://piotrkosoft.net/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>PT Portugal</strong></big></td></tr> + +<tr> +<td valign=top>ftp.pt.debian.org<br> (ftp.uevora.pt)</td> +<td valign=top><a href="ftp://ftp.pt.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.pt.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.eq.uc.pt</td> +<td valign=top><a href="ftp://ftp.eq.uc.pt/pub/software/Linux/debian/">/pub/software/Linux/debian/</a></td> +<td valign=top><a href="http://ftp.eq.uc.pt/software/Linux/debian/">/software/Linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.ua.pt</td> +<td valign=top><a href="ftp://debian.ua.pt/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ua.pt/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.linux.pt</td> +<td valign=top><a href="ftp://ftp.linux.pt/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><a href="http://ftp.linux.pt/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.telepac.pt</td> +<td valign=top><a href="ftp://ftp.telepac.pt/pub/debian/">/pub/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.nfsi.pt</td> +<td valign=top><a href="ftp://mirrors.nfsi.pt/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://mirrors.nfsi.pt/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>neacm.fe.up.pt</td> +<td valign=top><a href="ftp://neacm.fe.up.pt/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://neacm.fe.up.pt/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>cesium.di.uminho.pt</td> +<td valign=top><a href="ftp://cesium.di.uminho.pt/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://cesium.di.uminho.pt/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.netvisao.pt</td> +<td valign=top><a href="ftp://debian.netvisao.pt/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.netvisao.pt/">/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.dcc.fc.up.pt</td> +<td></td> +<td valign=top><a href="http://debian.dcc.fc.up.pt/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.sim.ul.pt</td> +<td valign=top><a href="ftp://mirror.sim.ul.pt/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.sim.ul.pt/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>RO Romania</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ro.debian.org<br> (ftp.iasi.roedu.net)</td> +<td valign=top><a href="ftp://ftp.ro.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ro.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.lug.ro</td> +<td valign=top><a href="ftp://ftp.lug.ro/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.lug.ro/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.mikesnet.ro</td> +<td valign=top><a href="ftp://ftp.mikesnet.ro/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.mikesnet.ro/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 mips mipsel</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>RU Russia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ru.debian.org<br> (ftp.chg.ru)</td> +<td valign=top><a href="ftp://ftp.ru.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ru.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.nsu.ru</td> +<td valign=top><a href="ftp://debian.nsu.ru/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.nsu.ru/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.psn.ru</td> +<td valign=top><a href="ftp://ftp.psn.ru/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.psn.ru/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.corbina.net</td> +<td valign=top><a href="ftp://ftp.corbina.net/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>ftp.mipt.ru</td> +<td valign=top><a href="ftp://ftp.mipt.ru/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.yandex.ru</td> +<td valign=top><a href="ftp://mirror.yandex.ru/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.yandex.ru/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debian.chuvsu.ru</td> +<td valign=top><a href="ftp://ftp.debian.chuvsu.ru/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.debian.chuvsu.ru/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>SE Sweden</strong></big></td></tr> + +<tr> +<td valign=top>ftp.se.debian.org<br> (ftp.acc.umu.se)</td> +<td valign=top><a href="ftp://ftp.se.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.se.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.sunet.se</td> +<td valign=top><a href="ftp://ftp.sunet.se/pub/Linux/distributions/debian/">/pub/Linux/distributions/debian/</a></td> +<td valign=top><a href="http://ftp.sunet.se/pub/Linux/distributions/debian/">/pub/Linux/distributions/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.port80.se</td> +<td valign=top><a href="ftp://ftp.port80.se/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.port80.se/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ds.karen.hj.se</td> +<td valign=top><a href="ftp://ftp.ds.karen.hj.se/pub/os/linux/debian/">/pub/os/linux/debian/</a></td> +<td valign=top><a href="http://ftp.ds.karen.hj.se/pub/os/linux/debian/">/pub/os/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.lth.se</td> +<td valign=top><a href="ftp://debian.lth.se/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.lth.se/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.df.lth.se</td> +<td valign=top><a href="ftp://ftp.df.lth.se/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>kalle.csb.ki.se</td> +<td></td> +<td valign=top><a href="http://kalle.csb.ki.se/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>SG Singapore</strong></big></td></tr> + +<tr> +<td valign=top>mirror.nus.edu.sg</td> +<td valign=top><a href="ftp://mirror.nus.edu.sg/pub/Debian/">/pub/Debian/</a></td> +<td valign=top><a href="http://mirror.nus.edu.sg/Debian/">/Debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>SI Slovenia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.si.debian.org<br> (ftp.camtp.uni-mb.si)</td> +<td valign=top><a href="ftp://ftp.si.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.si.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 ia64 m68k powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.arnes.si</td> +<td valign=top><a href="ftp://ftp.arnes.si/packages/debian/">/packages/debian/</a></td> +<td valign=top><a href="http://ftp.arnes.si/pub/packages/debian/">/pub/packages/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.prunk.si</td> +<td valign=top><a href="ftp://debian.prunk.si/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.prunk.si/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>SK Slovakia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.sk.debian.org<br> (ftp.tuke.sk)</td> +<td valign=top><a href="ftp://ftp.sk.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.sk.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.ynet.sk</td> +<td></td> +<td valign=top><a href="http://mirror.ynet.sk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debian.sk</td> +<td valign=top><a href="ftp://ftp.debian.sk/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.debian.sk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.antik.sk</td> +<td valign=top><a href="ftp://ftp.antik.sk/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.antik.sk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>SV El Salvador</strong></big></td></tr> + +<tr> +<td valign=top>debian.ues.edu.sv</td> +<td valign=top><a href="ftp://debian.ues.edu.sv/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ues.edu.sv/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>TH Thailand</strong></big></td></tr> + +<tr> +<td valign=top>ftp.coe.psu.ac.th</td> +<td valign=top><a href="ftp://ftp.coe.psu.ac.th/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.coe.psu.ac.th/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.thaios.net</td> +<td></td> +<td valign=top><a href="http://ftp.thaios.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debianclub.org</td> +<td valign=top><a href="ftp://ftp.debianclub.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.debianclub.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>TR Turkey</strong></big></td></tr> + +<tr> +<td valign=top>ftp.tr.debian.org<br> (debian.ankara.edu.tr)</td> +<td valign=top><a href="ftp://ftp.tr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.tr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.linux.org.tr</td> +<td valign=top><a href="ftp://ftp.linux.org.tr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.linux.org.tr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>godel.cs.bilgi.edu.tr</td> +<td valign=top><a href="ftp://godel.cs.bilgi.edu.tr/debian/">/debian/</a></td> +<td valign=top><a href="http://godel.cs.bilgi.edu.tr/debian/">/debian/</a></td> +<td valign=top><small><small>hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.eso-es.net</td> +<td></td> +<td valign=top><a href="http://debian.eso-es.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.comu.edu.tr</td> +<td valign=top><a href="ftp://debian.comu.edu.tr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.comu.edu.tr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.metu.edu.tr</td> +<td valign=top><a href="ftp://ftp.metu.edu.tr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.metu.edu.tr/debian/">/debian/</a></td> +<td valign=top><small><small>ALL alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>TW Taiwan</strong></big></td></tr> + +<tr> +<td valign=top>ftp.tw.debian.org<br> (debian.linux.org.tw)</td> +<td valign=top><a href="ftp://ftp.tw.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.tw.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.csie.ntu.edu.tw</td> +<td valign=top><a href="ftp://debian.csie.ntu.edu.tw/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://debian.csie.ntu.edu.tw/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.twaren.net</td> +<td valign=top><a href="ftp://ftp.twaren.net/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.twaren.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>opensource.nchc.org.tw</td> +<td valign=top><a href="ftp://opensource.nchc.org.tw/debian/">/debian/</a></td> +<td valign=top><a href="http://opensource.nchc.org.tw/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.isu.edu.tw</td> +<td valign=top><a href="ftp://ftp.isu.edu.tw/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.isu.edu.tw/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.nctu.edu.tw</td> +<td valign=top><a href="ftp://debian.nctu.edu.tw/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.nctu.edu.tw/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.nttu.edu.tw</td> +<td valign=top><a href="ftp://mirror.nttu.edu.tw/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.nttu.edu.tw/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.csie.nctu.edu.tw</td> +<td valign=top><a href="ftp://debian.csie.nctu.edu.tw/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.csie.nctu.edu.tw/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ncnu.edu.tw</td> +<td valign=top><a href="ftp://ftp.ncnu.edu.tw/Linux/Debian/debian/">/Linux/Debian/debian/</a></td> +<td valign=top><a href="http://ftp.ncnu.edu.tw/Linux/Debian/debian/">/Linux/Debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.cse.yzu.edu.tw</td> +<td valign=top><a href="ftp://ftp.cse.yzu.edu.tw/pub/Linux/debian/debian/">/pub/Linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.cse.yzu.edu.tw/pub/Linux/debian/debian/">/pub/Linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>UA Ukraine</strong></big></td></tr> + +<tr> +<td valign=top>debian.osdn.org.ua</td> +<td valign=top><a href="ftp://debian.osdn.org.ua/pub/Debian/debian/">/pub/Debian/debian/</a></td> +<td valign=top><a href="http://debian.osdn.org.ua/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.org.ua</td> +<td valign=top><a href="ftp://debian.org.ua/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.org.ua/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.3logic.net</td> +<td valign=top><a href="ftp://ftp.3logic.net/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.mirohost.net</td> +<td valign=top><a href="ftp://mirror.mirohost.net/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.mirohost.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp2.debian.org.ua</td> +<td valign=top><a href="ftp://ftp2.debian.org.ua/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp2.debian.org.ua/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>US United States</strong></big></td></tr> + +<tr> +<td valign=top>ftp.us.debian.org<br> (ftp.egr.msu.edu, mirrors.kernel.org, debian.osuosl.org, debian.lcs.mit.edu)</td> +<td valign=top><a href="ftp://ftp.us.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.us.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.gtlib.gatech.edu</td> +<td valign=top><a href="ftp://ftp.gtlib.gatech.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.gtlib.gatech.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.egr.msu.edu</td> +<td valign=top><a href="ftp://ftp.egr.msu.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.egr.msu.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>distro.ibiblio.org</td> +<td valign=top><a href="ftp://distro.ibiblio.org/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><a href="http://distro.ibiblio.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>ftp-mirror.internap.com</td> +<td valign=top><a href="ftp://ftp-mirror.internap.com/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp-mirror.internap.com/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.cerias.purdue.edu</td> +<td valign=top><a href="ftp://ftp.cerias.purdue.edu/pub/os/debian/">/pub/os/debian/</a></td> +<td valign=top><a href="http://ftp.cerias.purdue.edu/pub/os/debian/">/pub/os/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.cs.wisc.edu</td> +<td valign=top><a href="ftp://mirror.cs.wisc.edu/pub/mirrors/linux/debian/">/pub/mirrors/linux/debian/</a></td> +<td valign=top><a href="http://mirror.cs.wisc.edu/pub/mirrors/linux/debian/">/pub/mirrors/linux/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uwsg.indiana.edu</td> +<td valign=top><a href="ftp://ftp.uwsg.indiana.edu/linux/debian/">/linux/debian/</a></td> +<td valign=top><a href="http://ftp.uwsg.indiana.edu/linux/debian/">/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>natasha.stmarytx.edu</td> +<td valign=top><a href="ftp://natasha.stmarytx.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://natasha.stmarytx.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ndlug.nd.edu</td> +<td valign=top><a href="ftp://ftp.ndlug.nd.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ndlug.nd.edu/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.uchicago.edu</td> +<td valign=top><a href="ftp://debian.uchicago.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.uchicago.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>carroll.aset.psu.edu</td> +<td valign=top><a href="ftp://carroll.aset.psu.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><a href="http://carroll.aset.psu.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>gladiator.real-time.com</td> +<td valign=top><a href="ftp://gladiator.real-time.com/linux/debian/">/linux/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.kernel.org</td> +<td valign=top><a href="ftp://mirrors.kernel.org/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.kernel.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.xmission.com</td> +<td valign=top><a href="ftp://mirrors.xmission.com/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.xmission.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.lug.udel.edu</td> +<td valign=top><a href="ftp://ftp.lug.udel.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.lug.udel.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.lcs.mit.edu</td> +<td valign=top><a href="ftp://debian.lcs.mit.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.lcs.mit.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>linux.csua.berkeley.edu</td> +<td></td> +<td valign=top><a href="http://linux.csua.berkeley.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.silug.org</td> +<td valign=top><a href="ftp://ftp.silug.org/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.silug.org/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 mips mipsel powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.secsup.org</td> +<td valign=top><a href="ftp://debian.secsup.org/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://debian.secsup.org/">/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.osuosl.org</td> +<td valign=top><a href="ftp://debian.osuosl.org/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.osuosl.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.anl.gov</td> +<td valign=top><a href="ftp://mirror.anl.gov/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://mirror.anl.gov/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>sluglug.ucsc.edu</td> +<td></td> +<td valign=top><a href="http://sluglug.ucsc.edu/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.geeks.org</td> +<td valign=top><a href="ftp://mirrors.geeks.org/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.geeks.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.usc.edu</td> +<td valign=top><a href="ftp://mirrors.usc.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><a href="http://mirrors.usc.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirrors.pair.com</td> +<td valign=top><a href="ftp://debian.mirrors.pair.com/">/</a></td> +<td valign=top><a href="http://debian.mirrors.pair.com/">/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>lug.mtu.edu</td> +<td valign=top><a href="ftp://lug.mtu.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://lug.mtu.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 hppa i386 mips mipsel powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirrors.tds.net</td> +<td valign=top><a href="ftp://debian.mirrors.tds.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirrors.tds.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.cites.uiuc.edu</td> +<td valign=top><a href="ftp://debian.cites.uiuc.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://debian.cites.uiuc.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.tummy.com</td> +<td valign=top><a href="ftp://mirrors.tummy.com/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.tummy.com/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.frontiernet.net</td> +<td valign=top><a href="ftp://debian.mirror.frontiernet.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirror.frontiernet.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>cudlug.cudenver.edu</td> +<td valign=top><a href="ftp://cudlug.cudenver.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://cudlug.cudenver.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>bigmirror.crossbowproject.net</td> +<td valign=top><a href="ftp://bigmirror.crossbowproject.net/pub/debian/">/pub/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.cc.columbia.edu</td> +<td valign=top><a href="ftp://mirror.cc.columbia.edu/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://mirror.cc.columbia.edu/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.grokthis.net</td> +<td valign=top><a href="ftp://ftp.grokthis.net/mirrors/debian/">/mirrors/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.xenir.com</td> +<td></td> +<td valign=top><a href="http://mirrors.xenir.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm armel i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirrors.easynews.com</td> +<td></td> +<td valign=top><a href="http://debian.mirrors.easynews.com/linux/debian/">/linux/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.ams.sunysb.edu</td> +<td></td> +<td valign=top><a href="http://debian.ams.sunysb.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.acm.jhu.edu</td> +<td></td> +<td valign=top><a href="http://mirrors.acm.jhu.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uga.edu</td> +<td valign=top><a href="ftp://ftp.uga.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uga.edu/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.steadfast.net</td> +<td></td> +<td valign=top><a href="http://mirror.steadfast.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.utexas.edu</td> +<td valign=top><a href="ftp://ftp.utexas.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.utexas.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.fdcservers.net</td> +<td valign=top><a href="ftp://mirror.fdcservers.net/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.fdcservers.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.rit.edu</td> +<td valign=top><a href="ftp://mirror.rit.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.rit.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.corenetworks.net</td> +<td></td> +<td valign=top><a href="http://debian.corenetworks.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.its.uidaho.edu</td> +<td valign=top><a href="ftp://mirror.its.uidaho.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.its.uidaho.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.cs.binghamton.edu</td> +<td valign=top><a href="ftp://debian.cs.binghamton.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.cs.binghamton.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>UZ Uzbekistan</strong></big></td></tr> + +<tr> +<td valign=top>debian.snet.uz</td> +<td></td> +<td valign=top><a href="http://debian.snet.uz/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.stream.uz</td> +<td valign=top><a href="ftp://debian.stream.uz/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.stream.uz/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>VE Venezuela</strong></big></td></tr> + +<tr> +<td valign=top>debian.unesr.edu.ve</td> +<td></td> +<td valign=top><a href="http://debian.unesr.edu.ve/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ula.ve</td> +<td valign=top><a href="ftp://ftp.ula.ve/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ula.ve/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>ZA South Africa</strong></big></td></tr> + +<tr> +<td valign=top>ftp.sun.ac.za</td> +<td valign=top><a href="ftp://ftp.sun.ac.za/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.sun.ac.za/ftp/debian/">/ftp/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.ac.za</td> +<td valign=top><a href="ftp://debian.mirror.ac.za/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirror.ac.za/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.is.co.za</td> +<td valign=top><a href="ftp://ftp.is.co.za/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +</table> +<hr> +<table border="0" width="100%"><tr> + <td align="left"><small>Last modified: Tue Oct 14 07:52:17 2008</small></td> + <td align="right"><small>Number of sites listed: 417</small></td> +</tr></table> +</body> +</html> diff --git a/includes/etch/install/README.mirrors.txt b/includes/etch/install/README.mirrors.txt new file mode 100644 index 0000000..671f955 --- /dev/null +++ b/includes/etch/install/README.mirrors.txt @@ -0,0 +1,657 @@ + 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 + --------------------------- + + 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.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 armel 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: Tue Oct 14 07:52:17 2008 Number of sites listed: 417 diff --git a/includes/sid/install/README.txt b/includes/etch/install/README.txt index db1c7b2..dc1ddbd 100644 --- a/includes/sid/install/README.txt +++ b/includes/etch/install/README.txt @@ -1,8 +1,8 @@ (HTML version in README.html)
- DEBIAN_NAME
- DEBIAN_DATE
+ Debian GNU/Linux 4.0 r5 "Etch" - Official i386 BC Binary-1
+ 20081024-15:52
@@ -23,7 +23,7 @@ Intro
=====
- This is one disc in a set containing the the Debian GNU/Linux
+ This is one disc in a set containing 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").
@@ -52,17 +52,20 @@ About This Disc This disc is labeled
- DEBIAN_NAME
- DEBIAN_DATE
+ Debian GNU/Linux 4.0 r5 "Etch" - Official i386 BC Binary-1
+ 20081024-15:52
- which means that this disc is number 1 of a set of 1 discs. It
- contains programs ("binaries") for `DEBIAN_ARCHITECTURE' computers.
+ which means that this disc is number 1 of a set of 1 discs. The
+ packages on this disc contain programs ("binaries") for 'ARCH'
+ computers.
- The programs on the Binary discs are ordered by popularity. The
+ The packages on the Binary discs are ordered by popularity. The
Binary-1 disc contains the most popular programs and the installation
tools; it is possible to install and run Debian with only the Binary-1
- disc. The other discs, up to Binary-1, contain mostly
- special-interest programs.
+ disc. It is unlikely that you will need all of the 1 discs in
+ the set. The higher the number in the set, the less likely it is that
+ you will use any of the packages on that disc; higher-number images
+ contain mostly special-interest programs.
The Release Notes for "etch" are available on the Debian web site.
@@ -80,7 +83,7 @@ Installing Programs and other files that are needed for the installation can be
found on this disc under
- DEBIAN_TOOLS
+ /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
@@ -112,16 +115,16 @@ 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.
+ 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 install packages from the commandline using aptitude. For
+ example, if you want to install the packages 'commprog' and 'maxgame',
you can give the command
- apt-get install commprog maxgame
+ aptitude install commprog maxgame
- Note that you don't have to enter the complete path, or the `.deb'
- extension. `Apt' will figure this out itself.
+ 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.
@@ -165,8 +168,6 @@ More Information See the Debian contact page (http://www.debian.org/contact) for
information on contacting us.
- Last Modified: Sat Mar 20 12:30:45 EST 2004
-
References
1. http://bugs.debian.org/
diff --git a/includes/sid/install/autorun.bat b/includes/etch/install/autorun.bat index 4718afe..4718afe 100644 --- a/includes/sid/install/autorun.bat +++ b/includes/etch/install/autorun.bat diff --git a/includes/sid/install/autorun.inf b/includes/etch/install/autorun.inf index 1b28f75..1b28f75 100644 --- a/includes/sid/install/autorun.inf +++ b/includes/etch/install/autorun.inf diff --git a/includes/sid/install/pics/blue-lowerleft.png b/includes/etch/install/pics/blue-lowerleft.png Binary files differindex 2a2245e..2a2245e 100644 --- a/includes/sid/install/pics/blue-lowerleft.png +++ b/includes/etch/install/pics/blue-lowerleft.png diff --git a/includes/sid/install/pics/blue-lowerright.png b/includes/etch/install/pics/blue-lowerright.png Binary files differindex 7e66271..7e66271 100644 --- a/includes/sid/install/pics/blue-lowerright.png +++ b/includes/etch/install/pics/blue-lowerright.png diff --git a/includes/sid/install/pics/blue-upperleft.png b/includes/etch/install/pics/blue-upperleft.png Binary files differindex a58d0ec..a58d0ec 100644 --- a/includes/sid/install/pics/blue-upperleft.png +++ b/includes/etch/install/pics/blue-upperleft.png diff --git a/includes/sid/install/pics/blue-upperright.png b/includes/etch/install/pics/blue-upperright.png Binary files differindex 2f36849..2f36849 100644 --- a/includes/sid/install/pics/blue-upperright.png +++ b/includes/etch/install/pics/blue-upperright.png diff --git a/includes/sid/install/pics/debian.jpg b/includes/etch/install/pics/debian.jpg Binary files differindex db62d7a..db62d7a 100644 --- a/includes/sid/install/pics/debian.jpg +++ b/includes/etch/install/pics/debian.jpg diff --git a/includes/sid/install/pics/logo-50.jpg b/includes/etch/install/pics/logo-50.jpg Binary files differindex 542f0a4..542f0a4 100644 --- a/includes/sid/install/pics/logo-50.jpg +++ b/includes/etch/install/pics/logo-50.jpg diff --git a/includes/sid/install/pics/red-lowerleft.png b/includes/etch/install/pics/red-lowerleft.png Binary files differindex caca9c5..caca9c5 100644 --- a/includes/sid/install/pics/red-lowerleft.png +++ b/includes/etch/install/pics/red-lowerleft.png diff --git a/includes/sid/install/pics/red-lowerright.png b/includes/etch/install/pics/red-lowerright.png Binary files differindex c27056c..c27056c 100644 --- a/includes/sid/install/pics/red-lowerright.png +++ b/includes/etch/install/pics/red-lowerright.png diff --git a/includes/sid/install/pics/red-upperleft.png b/includes/etch/install/pics/red-upperleft.png Binary files differindex c1e3301..c1e3301 100644 --- a/includes/sid/install/pics/red-upperleft.png +++ b/includes/etch/install/pics/red-upperleft.png diff --git a/includes/sid/install/pics/red-upperright.png b/includes/etch/install/pics/red-upperright.png Binary files differindex 54d17ca..54d17ca 100644 --- a/includes/sid/install/pics/red-upperright.png +++ b/includes/etch/install/pics/red-upperright.png diff --git a/includes/sid/install/tools/README b/includes/etch/install/tools/README index bc56f93..bc56f93 100644 --- a/includes/sid/install/tools/README +++ b/includes/etch/install/tools/README diff --git a/includes/sid/install/tools/diskio.zip b/includes/etch/install/tools/diskio.zip Binary files differindex b30fa96..b30fa96 100644 --- a/includes/sid/install/tools/diskio.zip +++ b/includes/etch/install/tools/diskio.zip diff --git a/includes/sid/install/tools/fips20.zip b/includes/etch/install/tools/fips20.zip Binary files differindex c4a64b6..c4a64b6 100644 --- a/includes/sid/install/tools/fips20.zip +++ b/includes/etch/install/tools/fips20.zip diff --git a/includes/sid/install/tools/gzip124.exe b/includes/etch/install/tools/gzip124.exe Binary files differindex 1a8d137..1a8d137 100644 --- a/includes/sid/install/tools/gzip124.exe +++ b/includes/etch/install/tools/gzip124.exe diff --git a/includes/sid/install/tools/lodlin16.zip b/includes/etch/install/tools/lodlin16.zip Binary files differindex 50ad313..da30b2d 100644 --- a/includes/sid/install/tools/lodlin16.zip +++ b/includes/etch/install/tools/lodlin16.zip diff --git a/includes/sid/install/tools/md5sum-w32.zip b/includes/etch/install/tools/md5sum-w32.zip Binary files differindex 982202b..982202b 100644 --- a/includes/sid/install/tools/md5sum-w32.zip +++ b/includes/etch/install/tools/md5sum-w32.zip diff --git a/includes/sid/install/tools/rawrite1.zip b/includes/etch/install/tools/rawrite1.zip Binary files differindex abdc229..abdc229 100644 --- a/includes/sid/install/tools/rawrite1.zip +++ b/includes/etch/install/tools/rawrite1.zip diff --git a/includes/sid/install/tools/rawrite2.zip b/includes/etch/install/tools/rawrite2.zip Binary files differindex aa33885..aa33885 100644 --- a/includes/sid/install/tools/rawrite2.zip +++ b/includes/etch/install/tools/rawrite2.zip diff --git a/includes/sid/install/tools/rwwrtwin.zip b/includes/etch/install/tools/rwwrtwin.zip Binary files differindex 2c3fd11..2c3fd11 100644 --- a/includes/sid/install/tools/rwwrtwin.zip +++ b/includes/etch/install/tools/rwwrtwin.zip diff --git a/includes/sid/install/tools/src/md5sum-w32_1.1.dsc b/includes/etch/install/tools/src/md5sum-w32_1.1.dsc index 44393f8..44393f8 100644 --- a/includes/sid/install/tools/src/md5sum-w32_1.1.dsc +++ b/includes/etch/install/tools/src/md5sum-w32_1.1.dsc diff --git a/includes/sid/install/tools/src/md5sum-w32_1.1.tar.gz b/includes/etch/install/tools/src/md5sum-w32_1.1.tar.gz Binary files differindex bf42ec8..bf42ec8 100644 --- a/includes/sid/install/tools/src/md5sum-w32_1.1.tar.gz +++ b/includes/etch/install/tools/src/md5sum-w32_1.1.tar.gz diff --git a/includes/sid/install/tools/unz512x3.exe b/includes/etch/install/tools/unz512x3.exe Binary files differindex e8b36c8..e8b36c8 100644 --- a/includes/sid/install/tools/unz512x3.exe +++ b/includes/etch/install/tools/unz512x3.exe diff --git a/includes/lenny b/includes/lenny deleted file mode 120000 index 9a63c96..0000000 --- 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 0000000..041eaca --- /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 Binary files differnew file mode 100644 index 0000000..abee0f9 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/debian-faq.en.html.tar.gz diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz Binary files differnew file mode 100644 index 0000000..3b428a1 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz Binary files differnew file mode 100644 index 0000000..0ff0949 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz Binary files differnew file mode 100644 index 0000000..aeaaa41 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz 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 0000000..cc55653 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-basic_defs.en.html @@ -0,0 +1,610 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Definitions and overview</title> + +<link href="index.en.html" rel="start"> +<link href="index.en.html" rel="prev"> +<link href="ch-getting.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-basic_defs"></a></p> +<hr> + +<p> +[ <a href="index.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ 1 ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-getting.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 1 - Definitions and overview +</h1> + +<hr> + +<h2><a name="s-whatisfaq"></a>1.1 What is this FAQ?</h2> + +<p> +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. +</p> + +<p> +If you can't find what you're looking for in this FAQ, be sure to check out <a +href="ch-support.en.html#s-debiandocs">What other documentation exists on and +for a Debian system?, Section 12.1</a>. If even that doesn't help, refer to <a +href="ch-faqinfo.en.html#s-feedback">Feedback, Section 16.2</a>. +</p> + +<hr> + +<h2><a name="s-whatisdebian"></a>1.2 What is Debian GNU/Linux?</h2> + +<p> +Debian GNU/Linux is a particular <em>distribution</em> of the Linux operating +system, and numerous packages that run on it. +</p> + +<p> +Debian GNU/Linux is: +</p> +<ul> +<li> +<p> +<strong>full featured</strong>: Debian includes more than 18200 software +packages at present. Users can select which packages to install; Debian +provides a tool for this purpose. You can find a list and descriptions of the +packages currently available in Debian at any of the Debian <code><a +href="http://www.debian.org/distrib/ftplist">mirror sites</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>free to use and redistribute</strong>: There is no consortium +membership or payment required to participate in its distribution and +development. All packages that are formally part of Debian GNU/Linux are free +to redistribute, usually under terms specified by the GNU General Public +License. +</p> + +<p> +The Debian FTP archives also carry approximately 560 software packages (in the +<samp>non-free</samp> and <samp>contrib</samp> sections), which are +distributable under specific terms included with each package. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>dynamic</strong>: With about 1060 volunteers constantly contributing +new and improved code, Debian is evolving rapidly. The FTP archives are +updated twice every day. +</p> +</li> +</ul> + +<p> +Most Linux users run a specific <em>distribution</em> 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. +</p> + +<p> +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. +</p> + +<p> +For Debian, free has the GNUish meaning (see the <code><a +href="http://www.debian.org/social_contract#guidelines">Debian Free Software +Guidelines</a></code>). 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. +</p> + +<p> +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. +</p> + +<p> +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 <a +href="ch-redistrib.en.html#s-childistro">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</a> for more information. +</p> + +<hr> + +<h2><a name="s-linux"></a>1.3 OK, now I know what Debian is... what is Linux?!</h2> + +<p> +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. +</p> + +<p> +Besides its kernel, a "Linux" system usually has: +</p> +<ul> +<li> +<p> +a file system that follows the Linux Filesystem Hierarchy Standard <code><a +href="http://www.pathname.com/fhs/">http://www.pathname.com/fhs/</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +a wide range of Unix utilities, many of which have been developed by the GNU +project and the Free Software Foundation. +</p> +</li> +</ul> + +<p> +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 <a href="ch-compat.en.html#s-otherunices">How +source code compatible is Debian with other Unix systems?, Section 4.3</a>. +</p> + +<p> +For more information about Linux, see <code><a +href="http://www.linux.org/info/">What is Linux</a></code> by <code><a +href="http://www.linux.org/">Linux Online</a></code>. +</p> + +<hr> + +<h2><a name="s-non-linux"></a>1.4 Does Debian just do GNU/Linux?</h2> + +<p> +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. +</p> + +<p> +The oldest porting effort is Debian GNU/Hurd. +</p> + +<p> +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. +</p> + +<p> +Please see <code><a +href="http://www.gnu.org/software/hurd/">http://www.gnu.org/software/hurd/</a></code> +for more information about the GNU/Hurd in general, and <code><a +href="http://www.debian.org/ports/hurd/">http://www.debian.org/ports/hurd/</a></code> +for more information about Debian GNU/Hurd. +</p> + +<p> +A second effort is the port to a BSD kernel. People are working with both the +NetBSD and the FreeBSD kernels. +</p> + +<p> +See <code><a +href="http://www.debian.org/ports/#nonlinux">http://www.debian.org/ports/#nonlinux</a></code> +for more information about these non-linux ports. +</p> + +<hr> + +<h2><a name="s-difference"></a>1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?</h2> + +<p> +These key features distinguish Debian from other Linux distributions: +</p> +<dl> +<dt>Freedom:</dt> +<dd> +<p> +As stated in the <code><a href="http://www.debian.org/social_contract">Debian +Social Contract</a></code>, 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 <code><a +href="http://www.debian.org/social_contract#guidelines">The Debian Free +Software</a></code>. +</p> +</dd> +</dl> +<dl> +<dt>The Debian package maintenance system:</dt> +<dd> +<p> +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 <a +href="ch-pkg_basics.en.html">Basics of the Debian package management system, +Chapter 7</a>). +</p> +</dd> +</dl> +<dl> +<dt>Open development:</dt> +<dd> +<p> +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. +</p> + +<p> +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 <a +href="ch-contributing.en.html#s-contrib">How can I become a Debian software +developer?, Section 13.1</a>. +</p> +</dd> +</dl> +<dl> +<dt>The Universal Operating System:</dt> +<dd> +<p> +Debian comes with <code><a href="http://packages.debian.org/stable/">more than +18200 packages</a></code> and runs on <code><a +href="http://www.debian.org/ports/">11 architectures</a></code>. This is far +more than is available for any other GNU/Linux distribution. See <a +href="ch-software.en.html#s-apps">What types of applications and development +software are available for Debian GNU/Linux?, Section 5.1</a> for an overview +of the provided software and see <a href="ch-compat.en.html#s-arches">On what +hardware architectures/systems does Debian GNU/Linux run?, Section 4.1</a> for +a description of the supported hardware platforms. +</p> +</dd> +</dl> +<dl> +<dt>The Bug Tracking System:</dt> +<dd> +<p> +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 <a +href="ch-support.en.html#s-buglogs">Are there logs of known bugs?, Section +12.4</a>. +</p> +</dd> +</dl> +<dl> +<dt>The Debian Policy:</dt> +<dd> +<p> +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. +</p> +</dd> +</dl> + +<p> +For additional information about this, please see our web page about <code><a +href="http://www.debian.org/intro/why_debian">reasons to choose +Debian</a></code>. +</p> + +<hr> + +<h2><a name="s-gnu"></a>1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?</h2> + +<p> +The Debian system builds on the ideals of free software first championed by the +<code><a href="http://www.gnu.org/">Free Software Foundation</a></code> and in +particular by <code><a href="http://www.stallman.org/">Richard +Stallman</a></code>. FSF's powerful system development tools, utilities, and +applications are also a key part of the Debian system. +</p> + +<p> +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. +</p> + +<p> +The FSF's long-standing objective is to develop a new operating system called +GNU, based on <code><a +href="http://www.gnu.org/software/hurd/">Hurd</a></code>. Debian is working +with FSF on this system, called <code><a +href="http://www.debian.org/ports/hurd/">Debian GNU/Hurd</a></code>. +</p> + +<hr> + +<h2><a name="s-pronunciation"></a>1.7 How does one pronounce Debian and what does this word mean?</h2> + +<p> +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.) +</p> + +<hr> + +<p> +[ <a href="index.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ 1 ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-getting.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..6bee626 --- /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 0000000..e0403cc --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-choosing.en.html @@ -0,0 +1,961 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Choosing a Debian distribution</title> + +<link href="index.en.html" rel="start"> +<link href="ch-getting.en.html" rel="prev"> +<link href="ch-compat.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-choosing"></a></p> +<hr> + +<p> +[ <a href="ch-getting.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ 3 ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-compat.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 3 - Choosing a Debian distribution +</h1> + +<hr> + +<p> +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". +</p> + +<p> +For more information on the available distributions read <a +href="ch-ftparchives.en.html#s-dists">How many Debian distributions are there?, +Section 6.1</a>. +</p> + +<hr> + +<h2><a name="s3.1"></a>3.1 Which Debian distribution (stable/testing/unstable) is better for me?</h2> + +<p> +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. +</p> +<ul> +<li> +<p> +If security or stability are at all important for you: install stable. period. +This is the most preferred way. +</p> +</li> +</ul> +<ul> +<li> +<p> +If you are a new user installing to a desktop machine, start with stable. Some +of the software is quite old, but it's the least buggy environment to work in. +You can easily switch to the more modern unstable once you are a little more +confident. +</p> +</li> +</ul> +<ul> +<li> +<p> +If you are a desktop user with some experience in Linux and does not mind +facing the odd bug now and then, use unstable. It has all the latest and +greatest software, and bugs are usually fixed swiftly. +</p> +</li> +</ul> +<ul> +<li> +<p> +If you are running a server, especially one that has strong stability +requirements or is exposed to the Internet, install stable. This is by far the +strongest and safest choice. +</p> +</li> +</ul> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.1.1"></a>3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?</h3> + +<p> +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. +</p> + +<p> +For laptops, <code><a +href="http://www.linux-on-laptops.com/">http://www.linux-on-laptops.com/</a></code> +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. +</p> + +<p> +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 <code><a +href="http://lists.debian.org/debian-user/">http://lists.debian.org/debian-user/</a></code> +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 <code><a +href="http://www.debian.org/support">irc</a></code>. The mailing-list messages +are archived, so solution to your problem can help others with the same issue. +</p> + +<hr> + +<h3><a name="s3.1.2"></a>3.1.2 Will there be different different versions of packages in different distributions?</h3> + +<p> +Yes. Unstable has the most recent (latest) versions. But the packages in +unstable are not well tested and might have bugs. +</p> + +<p> +On the other hand, stable contains old versions of packages. But this package +is well tested and is less likely to have any bugs. +</p> + +<p> +The packages in testing fall between these two extremes. +</p> + +<hr> + +<h3><a name="s3.1.3"></a>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?</h3> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.1.4"></a>3.1.4 If I were to decide to change to another distribution, Can I do that?</h3> + +<p> +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. +</p> + +<p> +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.... +</p> + +<hr> + +<h3><a name="s3.1.5"></a>3.1.5 Could you tell me whether to install testing or unstable?</h3> + +<p> +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: +</p> +<ul> +<li> +<p> +Stable is rock solid. It does not break. +</p> +</li> +</ul> +<ul> +<li> +<p> +Testing breaks less often than Unstable. But when it breaks, it takes a long +time for things to get rectified. Sometimes this could be days and it could be +months at times. +</p> +</li> +</ul> +<ul> +<li> +<p> +Unstable changes a lot, and it can break at any point. However, fixes get +rectified in many occasions in a couple of days and it always has the latest +releases of software packaged for Debian. +</p> +</li> +</ul> + +<p> +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 <code>labplot</code> 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. +</p> + +<hr> + +<h3><a name="s3.1.6"></a>3.1.6 You are talking about testing being broken. What do you mean by that?</h3> + +<p> +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. +</p> + +<p> +When these things happen, the distribution is said to be broken (at least for +this package). +</p> + +<hr> + +<h3><a name="s3.1.7"></a>3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?</h3> + +<p> +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. +</p> + +<p> +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: +</p> +<ul> +<li> +<p> +Imagine you are interested in package XYZ. +</p> +</li> +</ul> +<ul> +<li> +<p> +Let's assume that on June 10, the version in testing is XYZ-3.6 and in unstable +it is XYZ-3.7 +</p> +</li> +</ul> +<ul> +<li> +<p> +After 10 days, XYZ-3.7 from unstable migrates into testing. +</p> +</li> +</ul> +<ul> +<li> +<p> +So on June 20, both testing and unstable have XYZ-3.7 in their repositories. +</p> +</li> +</ul> +<ul> +<li> +<p> +Let's say, The user of testing distribution sees that a new XYZ package is +available and updates his XYZ-3.6 to XYZ-3.7 +</p> +</li> +</ul> +<ul> +<li> +<p> +Now on June 25, someone using testing or unstable discovers an RC bug in +XYZ-3.7 and files it in the BTS. +</p> +</li> +</ul> +<ul> +<li> +<p> +The maintainer of XYZ fixes this bug and uploads it to unstable say on June 30. +Here it is assumed that it takes 5 days for the maintainer to fix the bug and +upload the new version. The number 5 should not be taken literally. It could +be less or more, depending upon the severity of the RC-bug at hand. +</p> +</li> +</ul> +<ul> +<li> +<p> +This new version in unstable, XYZ-3.8 is scheduled to enter testing on July +10th. +</p> +</li> +</ul> +<ul> +<li> +<p> +But on July 5th some other person, discovers another RC-bug in XYZ-3.8 +</p> +</li> +</ul> +<ul> +<li> +<p> +Let's say the maintainer of XYZ fixes this new RC-bug and uploads new version +of XYZ after 5 days. +</p> +</li> +</ul> +<ul> +<li> +<p> +So on July 10, testing has XYZ-3.7 while unstable has XYZ-3.9 +</p> +</li> +</ul> +<ul> +<li> +<p> +This new version XYZ-3.9 is now rescheduled to enter testing on July 20th. +</p> +</li> +</ul> +<ul> +<li> +<p> +Now since you are running testing, and since XYZ-3.7 is buggy, you could +probably use XYZ only after July 20th. That is you essentially ended up with a +broken XYZ for about one month. +</p> +</li> +</ul> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.1.8"></a>3.1.8 From an administrator's point of view, Which distribution requires more attention?</h3> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.1.9"></a>3.1.9 What happens when a new release is made?</h3> + +<p> +This question will not help you in choosing a Debian distribution. But sooner +or later you will face this question. +</p> + +<p> +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. +</p> +<ul> +<li> +<p> +oldstable = sarge; stable = etch; testing = lenny; unstable = sid +</p> +</li> +</ul> +<ul> +<li> +<p> +Unstable is always referred to as sid irrespective of whether a release is made +or not. +</p> +</li> +</ul> +<ul> +<li> +<p> +packages constantly migrate from sid to testing (i.e. lenny). But packages in +stable (i.e. etch) remain the same except for security updates. +</p> +</li> +</ul> +<ul> +<li> +<p> +after sometime testing becomes frozen. But it will still be called testing. +At this point no new packages from unstable can migrate to testing unless they +include release-critical (RC) bug fixes. +</p> +</li> +</ul> +<ul> +<li> +<p> +When testing is frozen, all the new bugfixes introduced, have to be manualy +checked by the members of the release team. This is done to ensure that there +wont be any unknown severe problems in the frozen testing. +</p> +</li> +</ul> +<ul> +<li> +<p> +RC bugs in 'frozen testing' are reduced to zero. +</p> +</li> +</ul> +<ul> +<li> +<p> +The 'frozen testing' with no rc-bugs will be released as the new stable +version. In our example, this new stable release will be called as lenny. +</p> +</li> +</ul> +<ul> +<li> +<p> +At this stage oldstable = etch, stable = lenny. The contents of stable and +'frozen testing' are same at this point. +</p> +</li> +</ul> +<ul> +<li> +<p> +A new testing is forked from the current stable. +</p> +</li> +</ul> +<ul> +<li> +<p> +Packages start coming down from sid to testing and the Debian community will be +working towards making the next stable release. +</p> +</li> +</ul> + +<hr> + +<h3><a name="s3.1.10"></a>3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?</h3> + +<p> +In most situations it is very easy to figure this out. Take a look at the +<code>/etc/apt/sources.list</code> file. There will be an entry similar to +this: +</p> + +<pre> + deb http://ftp.us.debian.org/debian/ unstable main contrib +</pre> + +<p> +The third field ('unstable' in the above example) indicates the Debian +distribution the system is currently tracking. +</p> + +<p> +You can also use <code>lsb_release</code> (available in the +<code>lsb-release</code> package). If you run this program in an unstable +system you will get: +</p> + +<pre> + $ 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 +</pre> + +<p> +However, this is always not that easy. Some systems might have +<code>sources.list</code> 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. +</p> + +<hr> + +<h3><a name="s3.1.11"></a>3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?</h3> + +<p> +If you are currently running stable, then in the +<code>/etc/apt/sources.list</code> 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 +<code>/etc/apt/sources.list</code> to testing. If you want to run unstable, +then change the third field to unstable. +</p> + +<p> +Currently testing is called lenny. So, if you change the third field of +<code>/etc/apt/sources.list</code> to lenny, then also you will be running +testing. But when lenny becomes stable, you will still be tracking lenny. +</p> + +<p> +Unstable is always called Sid. So if you change the third field of +<code>/etc/apt/sources.list</code> to sid, then you will be tracking unstable. +</p> + +<p> +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 +<code>/etc/apt/sources.list</code>. +</p> + +<p> +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. +</p> + +<p> +Nevertheless, once you make the above changes, you can run <code>aptitude +update</code> 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. +</p> + +<p> +It might be best in some situations to just fully upgrade to the new +distribution running <code>apt-get dist-upgrade</code>, <code>aptitude +safe-upgrade</code> or <code>aptitude full-upgrade</code>. Read apt's and +aptitude's manual pages for more information. +</p> + +<hr> + +<h3><a name="s3.1.12"></a>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?</h3> + +<p> +It depends on the entries in the <code>/etc/apt/sources.list</code> file. If +you are currently tracking testing, these entries are similar to either: +</p> + +<pre> + deb http://ftp.us.debian.org/debian/ testing main +</pre> + +<p> +or +</p> + +<pre> + deb http://ftp.us.debian.org/debian/ lenny main +</pre> + +<p> +If the third field in <code>/etc/apt/sources.list</code> 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. +</p> + +<p> +But if the third field contains 'lenny' then you will be tracking stable (since +lenny will then be the new stable distribution). +</p> + +<hr> + +<h3><a name="s3.1.13"></a>3.1.13 I am still confused. What did you say I should install?</h3> + +<p> +If unsure, the best bet would be stable distribution. +</p> + +<hr> + +<h2><a name="s3.2"></a>3.2 But what about Knoppix, Linex, Ubuntu, and others?</h2> + +<p> +They are not Debian; they are <em>Debian based</em>. Though there are many +similarities and commonalities between them, there are also crucial +differences. +</p> + +<p> +All these distributions have their own merits and are suited to some specific +set of users. For more information, read the information of <code><a +href="http://www.debian.org/misc/children-distros">software distributions based +on Debian</a></code> available at the Debian website. +</p> + +<hr> + +<h3><a name="s3.2.1"></a>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?</h3> + +<p> +These distributions are Debian based. But they are not Debian. You will be +still able to use apt package tools by pointing the +<code>/etc/apt/sources.list</code> file to these distributions' repositories. +But then you are not running Debian, you are running a different distribution. +They are not the same. +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.2.2"></a>3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?</h3> + +<p> +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. +</p> + +<p> +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. +</p> + +<hr> + +<h3><a name="s3.2.3"></a>3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?</h3> + +<p> +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. +</p> + +<p> +If all your user data (i.e. your <code>/home</code>) 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. <code>/etc/</code> and, maybe, <code>/var/</code>) is +still encouraged. +</p> + +<hr> + +<p> +[ <a href="ch-getting.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ 3 ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-compat.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..5b6a705 --- /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 0000000..375bff4 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-compat.en.html @@ -0,0 +1,554 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Compatibility issues</title> + +<link href="index.en.html" rel="start"> +<link href="ch-choosing.en.html" rel="prev"> +<link href="ch-software.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-compat"></a></p> +<hr> + +<p> +[ <a href="ch-choosing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ 4 ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-software.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 4 - Compatibility issues +</h1> + +<hr> + +<h2><a name="s-arches"></a>4.1 On what hardware architectures/systems does Debian GNU/Linux run?</h2> + +<p> +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 <code><a +href="http://en.tldp.org/FAQ/Linux-FAQ/intro.html#DOES-LINUX-RUN-ON-MY-COMPUTER">Linux +FAQ</a></code> for details. +</p> + +<p> +The current Debian GNU/Linux release, 4.0, contains a complete, binary +distribution for the following architectures: +</p> + +<p> +<em>i386</em>: this covers systems based on Intel and compatible processors, +including Intel's 386, 486, Pentium, Pentium Pro, Pentium II (both Klamath and +Celeron), and Pentium III, and most compatible processors by AMD, Cyrix and +others. +</p> + +<p> +<em>amd64</em>: this covers systems based on AMD 64bit CPUs with AMD64 +extension and all Intel CPUs with EM64T extension, and a common 64bit +userspace. +</p> + +<p> +<em>alpha</em>: Compaq/Digital's Alpha systems. +</p> + +<p> +<em>sparc</em>: this covers Sun's SPARC and most UltraSPARC systems. +</p> + +<p> +<em>powerpc</em>: this covers some IBM/Motorola PowerPC machines, including +CHRP, PowerMac and PReP machines. +</p> + +<p> +<em>arm</em>: ARM and StrongARM machines. +</p> + +<p> +<em>mips</em>: SGI's big-endian MIPS systems, Indy and Indigo2; +<em>mipsel</em>: little-endian MIPS machines, Digital DECstations. +</p> + +<p> +<em>hppa</em>: Hewlett-Packard's PA-RISC machines (712, C3000, L2000, A500). +</p> + +<p> +<em>ia64</em>: Intel IA-64 ("Itanium") computers. +</p> + +<p> +<em>s390</em>: IBM S/390 mainframe systems. +</p> + +<p> +The development of binary distributions of Debian for Sparc64 (UltraSPARC +native) architectures is currently underway. +</p> + +<p> +Support for the <em>m68k</em> architecture was dropped in this release, because +it did not meet the criteria set by the Debian Release Managers. This +architecture covers Amigas and ATARIs having a Motorola 680x0 processor for +x>=2; with MMU. However, the port is still active and available for +installation even if not a part of this official stable release and might be +reactivated for future releases. +</p> + +<p> +For more information on the available ports see the <code><a +href="http://www.debian.org/ports/">ports pages at the website</a></code>. +</p> + +<p> +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 <code><a +href="http://www.debian.org/releases/stable/installmanual">http://www.debian.org/releases/stable/installmanual</a></code>. +</p> + +<hr> + +<h2><a name="s-otherdistribs"></a>4.2 How compatible is Debian with other distributions of Linux?</h2> + +<p> +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. +</p> + +<p> +Debian GNU/Linux adheres to the <code><a +href="http://www.pathname.com/fhs/">Linux Filesystem Hierarchy +Standard</a></code>. 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. +</p> + +<p> +Debian GNU/Linux supports software developed for the <code><a +href="http://www.linuxbase.org/">Linux Standard Base</a></code>. 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 <code><a +href="https://www.linux-foundation.org/lsb-cert/productdir.php">Linux +Foundation Certification webpage</a></code>. Discussion and coordination of +efforts towards ensuring Debian meets the requirements of the Linux Standard +Base is taking place on the <code><a +href="http://lists.debian.org/debian-lsb/">debian-lsb mailing list</a></code>. +</p> + +<hr> + +<h2><a name="s-otherunices"></a>4.3 How source code compatible is Debian with other Unix systems?</h2> + +<p> +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. +</p> + +<p> +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.) +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-otherpackages"></a>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?</h2> + +<p> +Different Linux distributions use different package formats and different +package management programs. +</p> +<dl> +<dt><strong>You probably can:</strong></dt> +<dd> +<p> +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 <code><a href="http://packages.debian.org/alien">Alien</a></code> package +is used to convert between different package formats. +</p> +</dd> +</dl> +<dl> +<dt><strong>You probably do not want to:</strong></dt> +<dd> +<p> +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. +</p> +</dd> +</dl> +<dl> +<dt><strong>A better way:</strong></dt> +<dd> +<p> +The Linux File System Standard (and therefore Debian GNU/Linux) requires that +subdirectories under <samp>/usr/local/</samp> 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. +</p> +</dd> +</dl> + +<hr> + +<h2><a name="s-non-debian-programs"></a>4.5 How should I install a non-Debian program?</h2> + +<p> +Files under the directory <samp>/usr/local/</samp> 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 +<samp>/usr/local/src/foo</samp>. After you compile them, place the binaries in +<samp>/usr/local/bin/</samp>, the libraries in <samp>/usr/local/lib/</samp>, +and the configuration files in <samp>/usr/local/etc/</samp>. +</p> + +<p> +If your programs and/or files really must be placed in some other directory, +you could still store them in <samp>/usr/local/</samp>, and build the +appropriate symbolic links from the required location to its location in +<samp>/usr/local/</samp>, e.g., you could make the link +</p> + +<pre> + ln -s /usr/local/bin/foo /usr/bin/foo +</pre> + +<p> +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 <a href="ch-support.en.html#s-debiandocs">What other +documentation exists on and for a Debian system?, Section 12.1</a>). +</p> + +<hr> + +<h2><a name="s-termcap"></a>4.6 Why can't I compile programs that require libtermcap?</h2> + +<p> +Debian uses the <samp>terminfo</samp> database and the <samp>ncurses</samp> +library of terminal interface routes, rather than the <samp>termcap</samp> +database and the <samp>termcap</samp> library. Users who are compiling +programs that require some knowledge of the terminal interface should replace +references to <samp>libtermcap</samp> with references to +<samp>libncurses</samp>. +</p> + +<p> +To support binaries that have already been linked with the <samp>termcap</samp> +library, and for which you do not have the source, Debian provides a package +called <code>termcap-compat</code>. This provides both +<samp>libtermcap.so.2</samp> and <samp>/etc/termcap</samp>. 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 +<samp>/etc/termcap</samp> file. +</p> + +<hr> + +<h2><a name="s-accelx"></a>4.7 Why can't I install AccelX?</h2> + +<p> +AccelX uses the <samp>termcap</samp> library for installation. See <a +href="#s-termcap">Why can't I compile programs that require libtermcap?, +Section 4.6</a> above. +</p> + +<hr> + +<h2><a name="s-motifnls"></a>4.8 Why do my old XFree 2.1 Motif applications crash?</h2> + +<p> +You need to install the <code>motifnls</code> 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. +</p> + +<p> +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. +</p> + +<hr> + +<p> +[ <a href="ch-choosing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ 4 ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-software.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..0696449 --- /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 0000000..db2d6e3 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-contributing.en.html @@ -0,0 +1,370 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Contributing to the Debian Project</title> + +<link href="index.en.html" rel="start"> +<link href="ch-support.en.html" rel="prev"> +<link href="ch-redistrib.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-contributing"></a></p> +<hr> + +<p> +[ <a href="ch-support.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ 13 ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-redistrib.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 13 - Contributing to the Debian Project +</h1> + +<hr> + +<p> +<code><a href="http://www.debian.org/donations">Donations</a></code> 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. +</p> + +<hr> + +<h2><a name="s-contrib"></a>13.1 How can I become a Debian software developer?</h2> + +<p> +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. +</p> + +<p> +The description of becoming a Debian developer can be found at the <code><a +href="http://www.debian.org/devel/join/newmaint">New Maintainer's +Corner</a></code> at the Debian web site. +</p> + +<hr> + +<h2><a name="s-contribresources"></a>13.2 How can I contribute resources to the Debian project?</h2> + +<p> +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 <code><a href="http://www.debian.org/mirror/size">Debian mirror +size</a></code> page for information on the disk space requirements. +</p> + +<p> +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. +</p> + +<p> +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 +<code><a +href="mailto:debian-admin@lists.debian.org">debian-admin@lists.debian.org</a></code>. +</p> + +<hr> + +<h2><a name="s-supportingorganizations"></a>13.3 How can I contribute financially to the Debian project?</h2> + +<p> +One can make individual donations to one of two organizations that are critical +to the development of the Debian project. +</p> + +<hr> + +<h3><a name="s-SPI"></a>13.3.1 Software in the Public Interest</h3> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +SPI can be reached at: <code><a +href="http://www.spi-inc.org/">http://www.spi-inc.org/</a></code>. +</p> + +<hr> + +<h3><a name="s-FSF"></a>13.3.2 Free Software Foundation</h3> + +<p> +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. +</p> + +<p> +FSF can be reached at: <code><a +href="http://www.fsf.org/">http://www.fsf.org/</a></code>. +</p> + +<hr> + +<p> +[ <a href="ch-support.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ 13 ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-redistrib.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..4185524 --- /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 0000000..9467112 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-customizing.en.html @@ -0,0 +1,716 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Customizing your installation of Debian GNU/Linux</title> + +<link href="index.en.html" rel="start"> +<link href="ch-kernel.en.html" rel="prev"> +<link href="ch-support.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-customizing"></a></p> +<hr> + +<p> +[ <a href="ch-kernel.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ 11 ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-support.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 11 - Customizing your installation of Debian GNU/Linux +</h1> + +<hr> + +<h2><a name="s-papersize"></a>11.1 How can I ensure that all programs use the same paper size?</h2> + +<p> +Install the <code>libpaper1</code> package, and it will ask you for a +system-wide default paper size. This setting will be kept in the file +<samp>/etc/papersize</samp>. +</p> + +<p> +Users can override the paper size setting using the <samp>PAPERSIZE</samp> +environment variable. For details, see the manual page +<code>papersize(5)</code>. +</p> + +<hr> + +<h2><a name="s-hardwareaccess"></a>11.2 How can I provide access to hardware peripherals, without compromising security?</h2> + +<p> +Many device files in the <samp>/dev</samp> directory belong to some predefined +groups. For example, <samp>/dev/fd0</samp> belongs to the <samp>floppy</samp> +group, and <samp>/dev/dsp</samp> belongs to the <samp>audio</samp> group. +</p> + +<p> +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: +</p> + +<pre> + adduser user group +</pre> + +<p> +This way you won't have to change the file permissions on the device. +</p> + +<p> +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 <samp>groups</samp>. +</p> + +<p> +Notice that, since the introduction of <samp>udev</samp> 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 <samp>/etc/udev</samp>. +</p> + +<hr> + +<h2><a name="s-consolefont"></a>11.3 How do I load a console font on startup the Debian way?</h2> + +<p> +The <code>kbd</code> and <code>console-tools</code> packages support this, edit +<samp>/etc/kbd/config</samp> or <samp>/etc/console-tools/config</samp> files. +</p> + +<hr> + +<h2><a name="s-appdefaults"></a>11.4 How can I configure an X11 program's application defaults?</h2> + +<p> +Debian's X programs will install their application resource data in the +<samp>/etc/X11/app-defaults/</samp> 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. +</p> + +<hr> + +<h2><a name="s-booting"></a>11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's.</h2> + +<p> +Like all Unices, Debian boots up by executing the program <samp>init</samp>. +The configuration file for <samp>init</samp> (which is +<samp>/etc/inittab</samp>) specifies that the first script to be executed +should be <samp>/etc/init.d/rcS</samp>. This script runs all of the scripts in +<samp>/etc/rcS.d/</samp> 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 <samp>/etc/rc.boot/</samp> too. +Any scripts in the latter directory are usually reserved for system +administrator use, and using them in packages is deprecated. +</p> + +<p> +After completing the boot process, <samp>init</samp> executes all start scripts +in a directory specified by the default runlevel (this runlevel is given by the +entry for <samp>id</samp> in <samp>/etc/inittab</samp>). Like most System V +compatible Unices, Linux has 7 runlevels: +</p> +<ul> +<li> +<p> +0 (halt the system), +</p> +</li> +</ul> +<ul> +<li> +<p> +1 (single-user mode), +</p> +</li> +</ul> +<ul> +<li> +<p> +2 through 5 (various multi-user modes), and +</p> +</li> +</ul> +<ul> +<li> +<p> +6 (reboot the system). +</p> +</li> +</ul> + +<p> +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 +<samp>/etc/rc2.d/</samp> will be run. +</p> + +<p> +In fact, the scripts in any of the directories, <samp>/etc/rcN.d/</samp> are +just symbolic links back to scripts in <samp>/etc/init.d/</samp>. However, the +<em>names</em> of the files in each of the <samp>/etc/rcN.d/</samp> directories +are selected to indicate the <em>way</em> the scripts in +<samp>/etc/init.d/</samp> 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. +</p> + +<p> +This approach works because the scripts in <samp>/etc/init.d/</samp> 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. +</p> + +<p> +For example, with the argument `reload' the command +</p> + +<pre> + /etc/init.d/sendmail reload +</pre> + +<p> +sends the sendmail daemon a signal to reread its configuration file. (BTW, +Debian supplies <code>invoke-rc.d</code> as a wrapper for invoking the scripts +in <samp>/etc/init.d/</samp>.) +</p> + +<hr> + +<h2><a name="s-custombootscripts"></a>11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?</h2> + +<p> +Suppose a system needs to execute script <samp>foo</samp> on start-up, or on +entry to a particular (System V) runlevel. Then the system administrator +should: +</p> +<ul> +<li> +<p> +Enter the script <samp>foo</samp> into the directory <samp>/etc/init.d/</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Run the Debian command <samp>update-rc.d</samp> with appropriate arguments, to +specify which runlevels should start the service, and which runlevels should +stop the service. +</p> +</li> +</ul> +<ul> +<li> +<p> +Consider rebooting the system to check that the service starts correctly +(assuming that you've asked for it to be started in the default runlevel). +Otherwise, manually start it by running `<samp>/etc/init.d/foo start</samp>'. +</p> +</li> +</ul> + +<p> +One might, for example, cause the script <samp>foo</samp> to execute at +boot-up, by putting it in <samp>/etc/init.d/</samp> and running +<samp>update-rc.d foo defaults 19</samp>. The argument `<samp>defaults</samp>' +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 <samp>foo</samp> 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 `<samp>19</samp>' ensures that +<samp>foo</samp> is called after all scripts whose number is less than 19 have +completed, and before all scripts whose number is 20 or greater. +</p> + +<hr> + +<h2><a name="s-interconffiles"></a>11.7 How does the package management system deal with packages that contain configuration files for other packages?</h2> + +<p> +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 <code>dpkg</code> 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. +</p> + +<p> +Instead, create a local package that modifies the configuration files of the +"group" of Debian packages of interest. Then <code>dpkg</code> 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. +</p> + +<hr> + +<h2><a name="s-divert"></a>11.8 How do I override a file installed by a package, so that a different version can be used instead?</h2> + +<p> +Suppose a sysadmin or local user wishes to use a program +"login-local" rather than the program "login" provided by +the Debian <code>login</code> package. +</p> + +<p> +Do <strong>not</strong>: +</p> +<ul> +<li> +<p> +Overwrite <samp>/bin/login</samp> with <samp>login-local</samp>. +</p> +</li> +</ul> + +<p> +The package management system will not know about this change, and will simply +overwrite your custom <samp>/bin/login</samp> whenever <samp>login</samp> (or +any package that provides <samp>/bin/login</samp>) is installed or updated. +</p> + +<p> +Rather, do +</p> +<ul> +<li> +<p> +Execute: +</p> + +<pre> + dpkg-divert --divert /bin/login.debian /bin/login +</pre> + +<p> +in order to cause all future installations of the Debian <code>login</code> +package to write the file <samp>/bin/login</samp> to +<samp>/bin/login.debian</samp> instead. +</p> +</li> +</ul> +<ul> +<li> +<p> +Then execute: +</p> + +<pre> + cp login-local /bin/login +</pre> + +<p> +to move your own locally-built program into place. +</p> +</li> +</ul> + +<p> +Run <samp>dpkg-divert --list</samp> to see which diversions are currently +active on your system. +</p> + +<p> +Details are given in the manual page <code>dpkg-divert(8)</code>. +</p> + +<hr> + +<h2><a name="s-localpackages"></a>11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?</h2> + +<p> +Execute the command: +</p> + +<pre> + dpkg-scanpackages BIN_DIR OVERRIDE_FILE [PATHPREFIX] > my_Packages +</pre> + +<p> +where: +</p> +<ul> +<li> +<p> +BIN-DIR is a directory where Debian archive files (which usually have an +extension of ".deb") are stored. +</p> +</li> +</ul> +<ul> +<li> +<p> +OVERRIDE_FILE is a file that is edited by the distribution maintainers and is +usually stored on a Debian FTP archive at <samp>indices/override.main.gz</samp> +for the Debian packages in the "main" distribution. You can ignore +this for local packages. +</p> +</li> +</ul> +<ul> +<li> +<p> +PATHPREFIX is an <em>optional</em> string that can be prepended to the +<samp>my_Packages</samp> file being produced. +</p> +</li> +</ul> + +<p> +Once you have built the file <samp>my_Packages</samp>, tell the package +management system about it by using the command: +</p> + +<pre> + dpkg --merge-avail my_Packages +</pre> + +<p> +If you are using APT, you can add the local repository to your +<code>sources.list(5)</code> file, too. +</p> + +<hr> + +<h2><a name="s-diverse"></a>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?</h2> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +For example, there might exist two different versions of newsreaders on a +system. The news server package might 'recommend' that there exist +<em>some</em> news reader on the system, but the choice of <samp>tin</samp> or +<samp>trn</samp> is left up to the individual user. This is satisfied by +having both the <code>tin</code> and <code>trn</code> packages provide the +virtual package <code>news-reader</code>. <em>Which</em> program is invoked is +determined by a link pointing from a file with the virtual package name +<samp>/etc/alternatives/news-reader</samp> to the selected file, e.g., +<samp>/usr/bin/trn</samp>. +</p> + +<p> +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 <samp>update-alternatives</samp> provides a way of +ensuring that all the files associated with a specified package are selected as +a system default. +</p> + +<p> +For example, to check what executables provide `x-window-manager', run: +</p> + +<pre> + update-alternatives --display x-window-manager +</pre> + +<p> +If you want to change it, run: +</p> + +<pre> + update-alternatives --config x-window-manager +</pre> + +<p> +And follow the instructions on the screen (basically, press the number next to +the entry you'd like better). +</p> + +<p> +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: +</p> + +<pre> + update-alternatives --install /usr/bin/x-window-manager \ + x-window-manager /usr/local/bin/wmaker-cvs 50 +</pre> + +<p> +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). +</p> + +<p> +To remove an alternative you added, simply run: +</p> + +<pre> + update-alternatives --remove x-window-manager /usr/local/bin/wmaker-cvs +</pre> + +<hr> + +<p> +[ <a href="ch-kernel.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ 11 ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-support.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..1cfdfaa --- /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 0000000..9edac20 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-faqinfo.en.html @@ -0,0 +1,407 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - General information about the FAQ</title> + +<link href="index.en.html" rel="start"> +<link href="ch-nexttime.en.html" rel="prev"> +<link href="index.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-faqinfo"></a></p> +<hr> + +<p> +[ <a href="ch-nexttime.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ 16 ] +[ <a href="index.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 16 - General information about the FAQ +</h1> + +<hr> + +<h2><a name="s-authors"></a>16.1 Authors</h2> + +<p> +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. +</p> + +<p> +Parts of the information came from: +</p> +<ul> +<li> +<p> +The Debian-1.1 release announcement, by <code><a +href="http://www.perens.com/">Bruce Perens</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +The Linux FAQ, by <code><a +href="http://www.chiark.greenend.org.uk/~ijackson/">Ian Jackson</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code><a href="http://lists.debian.org/">Debian Mailing Lists +Archives</a></code>, +</p> +</li> +</ul> +<ul> +<li> +<p> +the dpkg programmers' manual and the Debian Policy manual (see <a +href="ch-support.en.html#s-debiandocs">What other documentation exists on and +for a Debian system?, Section 12.1</a>) +</p> +</li> +</ul> +<ul> +<li> +<p> +many developers, volunteers, and beta testers, and +</p> +</li> +</ul> +<ul> +<li> +<p> +the flaky memories of its authors. :-) +</p> +</li> +</ul> +<ul> +<li> +<p> +Kamaraju Kusumanchi's <code><a +href="http://people.cornell.edu/pages/kk288/debian_choosing_distribution.html">Choosing +a Debian distribution FAQ</a></code>, who graciously made it GPL so I could +include it as a new chapter (see <a href="ch-choosing.en.html">Choosing a +Debian distribution, Chapter 3</a>) +</p> +</li> +</ul> + +<p> +The authors would like to thank all those who helped make this document +possible. +</p> + +<p> +All warranties are disclaimed. All trademarks are property of their respective +trademark owners. +</p> + +<hr> + +<h2><a name="s-feedback"></a>16.2 Feedback</h2> + +<p> +Comments and additions to this document are always welcome. Please send e-mail +to <code><a +href="mailto:doc-debian@packages.debian.org">doc-debian@packages.debian.org</a></code>, +or submit a wishlist bug report against the <code><code><a +href="http://bugs.debian.org/debian-faq">debian-faq</a></code></code> package. +</p> + +<hr> + +<h2><a name="s-latest"></a>16.3 Availability</h2> + +<p> +The latest version of this document can be viewed on the Debian WWW pages at +<code><a +href="http://www.debian.org/doc/FAQ/">http://www.debian.org/doc/FAQ/</a></code>. +</p> + +<p> +It is also available for download in plain text, HTML, PostScript and PDF +formats at <code><a +href="http://www.debian.org/doc/user-manuals#faq">http://www.debian.org/doc/user-manuals#faq</a></code>. +Also, there are several translations there. +</p> + +<p> +This document is available in the <code>debian-faq</code> package. +Translations are available in <code>debian-faq-de</code>, +<code>debian-faq-fr</code> and other packages. +</p> + +<p> +The original SGML files used to create this document are also available in +<code>debian-faq</code>'s source package, or in SVN at: +<samp>svn://svn.debian.org/svn/ddp/manuals/trunk/debian-faq</samp> and <code><a +href="http://svn.debian.org/viewsvn/ddp/manuals/trunk/debian-faq/">http://svn.debian.org/viewsvn/ddp/manuals/trunk/debian-faq/</a></code>. +</p> + +<hr> + +<h2><a name="s-docformat"></a>16.4 Document format</h2> + +<p> +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. +</p> + +<p> +Conversion utilities for DebianDoc SGML are available in Debian package +<code>debiandoc-sgml</code>. +</p> + +<hr> + +<p> +[ <a href="ch-nexttime.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ 16 ] +[ <a href="index.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..0f759b4 --- /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 0000000..0efd28a --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-ftparchives.en.html @@ -0,0 +1,756 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - The Debian FTP archives</title> + +<link href="index.en.html" rel="start"> +<link href="ch-software.en.html" rel="prev"> +<link href="ch-pkg_basics.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-ftparchives"></a></p> +<hr> + +<p> +[ <a href="ch-software.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ 6 ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-pkg_basics.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 6 - The Debian FTP archives +</h1> + +<hr> + +<h2><a name="s-dists"></a>6.1 How many Debian distributions are there?</h2> + +<p> +There are three major distributions: the "stable" distribution, the +"testing" distribution, and the "unstable" distribution. +The "testing" distribution is sometimes `frozen' (see <a +href="#s-frozen">What about "testing"? How is it `frozen'?, Section +6.5.1</a>). Next to these, there is the "oldstable" distribution +(that's just the one from before "stable"), and the +"experimental" distribution. +</p> + +<p> +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. +</p> + +<p> +See <a href="ch-choosing.en.html">Choosing a Debian distribution, Chapter 3</a> +for help when choosing a Debian distribution. +</p> + +<hr> + +<h2><a name="s-codenames"></a>6.2 What are all those names like etch, lenny, etc.?</h2> + +<p> +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 <samp>unstable</samp> suddenly changed its name to +<samp>stable</samp>, a lot of stuff would have to be needlessly downloaded +again). +</p> + +<p> +Currently, <samp>stable</samp> is a symbolic link to <samp>etch</samp> (i.e. +Debian GNU/Linux 4.0) and <samp>testing</samp> is a symbolic link to +<samp>lenny</samp>. This means that <samp>etch</samp> is the current stable +distribution and <samp>lenny</samp> is the current testing distribution. +</p> + +<p> +<samp>unstable</samp> is a permanent symbolic link to <samp>sid</samp>, as +<samp>sid</samp> is always the unstable distribution (see <a href="#s-sid">What +about "sid"?, Section 6.3</a>). +</p> + +<hr> + +<h3><a name="s-oldcodenames"></a>6.2.1 Which other codenames have been used in the past?</h3> + +<p> +Other codenames that have been already used are: <samp>buzz</samp> for release +1.1, <samp>rex</samp> for release 1.2, <samp>bo</samp> for releases 1.3.x, +<samp>hamm</samp> for release 2.0, <samp>slink</samp> for release 2.1, +<samp>potato</samp> for release 2.2, <samp>woody</samp> for release 3.0, +<samp>sarge</samp> for release 3.1, and <samp>etch</samp> for release 4.0. +</p> + +<hr> + +<h3><a name="s-sourceforcodenames"></a>6.2.2 Where do these codenames come from?</h3> + +<p> +So far they have been characters taken from the movie "Toy Story" by +Pixar. +</p> +<ul> +<li> +<p> +<em>buzz</em> (Buzz Lightyear) was the spaceman, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>rex</em> was the tyrannosaurus, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>bo</em> (Bo Peep) was the girl who took care of the sheep, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>hamm</em> was the piggy bank, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>slink</em> (Slinky Dog (R)) was the toy dog, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>potato</em> was, of course, Mr. Potato (R), +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>woody</em> was the cowboy, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>sarge</em> was the sergeant of the Green Plastic Army Men, +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>etch</em> was the toy blackboard (Etch-a-Sketch (R)), +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>lenny</em> was the binoculars. +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>sid</em> was the boy next door who destroyed toys. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-sid"></a>6.3 What about "sid"?</h2> + +<p> +<em>sid</em> or <em>unstable</em> is the place where most of the packages are +initially uploaded. It will never be released directly, because packages which +are to be released will first have to be included in <em>testing</em>, in order +to be released in <em>stable</em> later on. sid contains packages for both +released and unreleased architectures. +</p> + +<p> +The name "sid" also comes from the "Toy Story" animated +motion picture: Sid was the boy next door who destroyed toys :-) +</p> + +<p> +[<a href="footnotes.en.html#f2" name="fr2">2</a>] +</p> + +<hr> + +<h2><a name="s-stable"></a>6.4 What does the stable directory contain?</h2> +<ul> +<li> +<p> +stable/main/: This directory contains the packages which formally constitute +the most recent release of the Debian GNU/Linux system. +</p> + +<p> +These packages all comply with the <code><a +href="http://www.debian.org/social_contract#guidelines">Debian Free Software +Guidelines</a></code>, and are all freely usable and distributable. +</p> +</li> +</ul> +<ul> +<li> +<p> +stable/non-free/: This directory contains packages distribution of which is +restricted in a way that requires that distributors take careful account of the +specified copyright requirements. +</p> + +<p> +For example, some packages have licenses which prohibit commercial +distribution. Others can be redistributed but are in fact shareware and not +free software. The licenses of each of these packages must be studied, and +possibly negotiated, before the packages are included in any redistribution +(e.g., in a CD-ROM). +</p> +</li> +</ul> +<ul> +<li> +<p> +stable/contrib/: This directory contains packages which are DFSG-free and +<em>freely distributable</em> themselves, but somehow depend on a package that +is <em>not</em> freely distributable and thus available only in the non-free +section. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-testing"></a>6.5 What does the testing distribution contain?</h2> + +<p> +Packages are installed into the `testing' directory after they have undergone +some degree of testing in <a href="#s-unstable">unstable</a>. +</p> + +<p> +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. +</p> + +<p> +More information about the status of "testing" in general and the +individual packages is available at <code><a +href="http://www.debian.org/devel/testing">http://www.debian.org/devel/testing</a></code>. +</p> + +<hr> + +<h3><a name="s-frozen"></a>6.5.1 What about "testing"? How is it `frozen'?</h3> + +<p> +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". +</p> + +<p> +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. +</p> + +<p> +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 <code><a +href="http://www.debian.org/releases/testing/">current testing release +information</a></code>. +</p> + +<p> +Once that bug count lowers to maximum acceptable values, the frozen +"testing" distribution is declared "stable" and released +with a version number. +</p> + +<p> +With each new release, the previous "stable" distribution becomes +obsolete and moves to the archive. For more information please see <code><a +href="http://www.debian.org/distrib/archive">Debian archive</a></code>. +</p> + +<hr> + +<h2><a name="s-unstable"></a>6.6 What does the unstable distribution contain?</h2> + +<p> +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 :-) +</p> + +<p> +There are also main, contrib and non-free subdirectories in `unstable', +separated on the same criteria as in `stable'. +</p> + +<hr> + +<h2><a name="s-dirtree"></a>6.7 What are all those directories at the Debian FTP archives?</h2> + +<p> +The software that has been packaged for Debian GNU/Linux is available in one of +several directory trees on each Debian mirror site. +</p> + +<p> +The <samp>dists</samp> directory is short for "distributions", and it +is the canonical way to access the currently available Debian releases (and +pre-releases). +</p> + +<p> +The <samp>pool</samp> directory contains the actual packages, see <a +href="#s-pools">What's in the <samp>pool</samp> directory?, Section 6.10</a>. +</p> + +<p> +There are the following supplementary directories: +</p> +<dl> +<dt><em>/tools/</em>:</dt> +<dd> +<p> +DOS utilities for creating boot disks, partitioning your disk drive, +compressing/decompressing files, and booting Linux. +</p> +</dd> +</dl> +<dl> +<dt><em>/doc/</em>:</dt> +<dd> +<p> +The basic Debian documentation, such as this FAQ, the bug reporting system +instructions, etc. +</p> +</dd> +</dl> +<dl> +<dt><em>/indices/</em>:</dt> +<dd> +<p> +various indices of the site (the Maintainers file and the override files). +</p> +</dd> +</dl> +<dl> +<dt><em>/project/</em>:</dt> +<dd> +<p> +mostly developer-only materials and some miscellaneous files. +</p> +</dd> +</dl> + +<hr> + +<h2><a name="s-archsections"></a>6.8 What are all those directories inside <samp>dists/stable/main</samp>?</h2> + +<p> +Within each of the major directory trees[<a href="footnotes.en.html#f3" +name="fr3">3</a>], there are three sets of subdirectories containing index +files. +</p> + +<p> +There's one set of <samp>binary-<var>something</var></samp> subdirectories +which contain index files for binary packages of each available computer +architecture, for example <samp>binary-i386</samp> for packages which execute +on Intel x86 PC machines or <samp>binary-sparc</samp> for packages which +execute on Sun SPARCStations. +</p> + +<p> +The complete list of available architectures for each release is available at +<code><a href="http://www.debian.org/releases/">the release's web +page</a></code>. For the current release, please see <a +href="ch-compat.en.html#s-arches">On what hardware architectures/systems does +Debian GNU/Linux run?, Section 4.1</a>. +</p> + +<p> +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 <a +href="#s-pools"><samp>pool</samp> directory</a>. +</p> + +<p> +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). +</p> + +<p> +Last but not least, there's a set of subdirectories meant for the installation +system index files, they are at +<samp>debian-installer/binary-<var>architecture</var></samp>. +</p> + +<hr> + +<h2><a name="s-source"></a>6.9 Where is the source code?</h2> + +<p> +Source code is included for everything in the Debian system. Moreover, the +license terms of most programs in the system <em>require</em> that source code +be distributed along with the programs, or that an offer to provide the source +code accompany the programs. +</p> + +<p> +The source code is distributed in the <samp>pool</samp> directory (see <a +href="#s-pools">What's in the <samp>pool</samp> directory?, Section 6.10</a>) +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 <samp>apt-get source mypackagename</samp>. +</p> + +<p> +Some packages are only distributed as source code due to the restrictions in +their licenses. Notably, one such package is <samp>pine</samp>, see <a +href="ch-software.en.html#s-pine">Where is pine?, Section 5.10</a> for more +information. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-pools"></a>6.10 What's in the <samp>pool</samp> directory?</h2> + +<p> +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. +</p> + +<p> +You can find out where each package is placed by executing a command like +<samp>apt-cache showsrc mypackagename</samp> and looking at the `Directory:' +line. For example, the <samp>apache</samp> packages are stored in +<samp>pool/main/a/apache/</samp>. +</p> + +<p> +Additionally, since there are so many <samp>lib*</samp> packages, these are +treated specially: for instance, libpaper packages are stored in +<samp>pool/main/libp/libpaper/</samp>. +</p> + +<p> +[<a href="footnotes.en.html#f4" name="fr4">4</a>] +</p> + +<hr> + +<h2><a name="s-incoming"></a>6.11 What is "incoming"?</h2> + +<p> +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. +</p> + +<p> +Usually nobody should install things from this place. However, in some rare +cases of emergency, the incoming directory is available at <code><a +href="http://incoming.debian.org/">http://incoming.debian.org/</a></code>. You +can manually fetch packages, check the GPG signature and MD5sums in the +.changes and .dsc files, and then install them. +</p> + +<hr> + +<h2><a name="s-ownrepository"></a>6.12 How do I set up my own apt-able repository?</h2> + +<p> +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 <code><a +href="http://www.debian.org/doc/manuals/repository-howto/repository-howto">Debian +Repository HOWTO</a></code>. +</p> + +<hr> + +<p> +[ <a href="ch-software.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ 6 ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-pkg_basics.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..cdad69f --- /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 0000000..16d506c --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-getting.en.html @@ -0,0 +1,451 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Getting and installing Debian GNU/Linux</title> + +<link href="index.en.html" rel="start"> +<link href="ch-basic_defs.en.html" rel="prev"> +<link href="ch-choosing.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-getting"></a></p> +<hr> + +<p> +[ <a href="ch-basic_defs.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ 2 ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-choosing.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 2 - Getting and installing Debian GNU/Linux +</h1> + +<hr> + +<p> +The official document giving installation instructions is the <code><a +href="http://www.debian.org/releases/stable/installmanual">Debian GNU/Linux +Installation Guide</a></code>. We'll give some additional notes about getting +and installing Debian GNU/Linux here. +</p> + +<hr> + +<h2><a name="s-version"></a>2.1 What is the latest version of Debian?</h2> + +<p> +Currently there are three versions of Debian GNU/Linux: +</p> +<dl> +<dt><em>release 4.0, a.k.a. the `stable' distribution or etch</em></dt> +<dd> +<p> +This is stable and well tested software, it changes if major security or +usability fixes are incorporated. +</p> +</dd> +</dl> +<dl> +<dt><em>the `testing' distribution, currently called lenny</em></dt> +<dd> +<p> +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'. +</p> +</dd> +</dl> +<dl> +<dt><em>the `unstable' distribution</em></dt> +<dd> +<p> +This is the version currently under development; it is updated continuously. +You can retrieve packages from the `unstable' archive on any Debian FTP site +and use them to upgrade your system at any time, but you may not expect the +system to be as usable or as stable as before - that's why it's called +`<strong>unstable</strong>'! +</p> +</dd> +</dl> + +<p> +Please see <a href="ch-ftparchives.en.html#s-dists">How many Debian +distributions are there?, Section 6.1</a> for more information. +</p> + +<hr> + +<h2><a name="s-updatestable"></a>2.2 Are there package upgrades in `stable'?</h2> + +<p> +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 <code><a +href="ftp://security.debian.org">security.debian.org</a></code>. +</p> + +<p> +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. +</p> + +<p> +For more information related to security support please read the <code><a +href="http://www.debian.org/security/faq">Security FAQ</a></code> or the +<code><a href="http://www.debian.org/doc/manuals/securing-debian-howto/">Debian +Security Manual</a></code>. +</p> + +<hr> + +<h2><a name="s-boot-floppies"></a>2.3 Where/how can I get the Debian installation disks?</h2> + +<p> +You can get the installation disks by downloading the appropriate files from +one of the <code><a href="http://www.debian.org/mirror/list">Debian +mirrors</a></code>. +</p> + +<p> +Please refer to <code><a href="http://www.debian.org/CD">Debian GNU/Linux on +CDs</a></code> for more information about CD (and DVD) images. +</p> + +<hr> + +<h2><a name="s-cdrom"></a>2.4 How do I install the Debian from CD-ROMs?</h2> + +<p> +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 <code><a +href="http://www.debian.org/releases/stable/installmanual">Debian GNU/Linux +Installation Guide</a></code> for more information. +</p> + +<hr> + +<h2><a name="s-cdimage-symlinks"></a>2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!</h2> + +<p> +Official Debian CD images indeed contain symlinks like: +</p> + +<pre> + /dists/frozen -> etch/ + /dists/stable -> etch/ + /dists/testing -> etch/ + /dists/unstable -> etch/ +</pre> + +<p> +so that they work when your sources.list has an entry like +</p> + +<pre> + deb cdrom:[<name as on cd label>]/ unstable main [...] +</pre> + +<p> +. +</p> + +<p> +The fact these symlinks are present does <em>not</em> mean the image is +`unstable' or `testing' or anything. Read the CD label in +<code>/.disk/info</code> to find out which Debian version it contains. This +information is also present in <code>/README.txt</code> on the CD. +</p> + +<p> +Read <code><a +href="http://www.debian.org/releases/">http://www.debian.org/releases/</a></code> +to find out what the current `stable' and `testing' releases are. +</p> + +<hr> + +<h2><a name="s-remoteinstall"></a>2.6 Can I get and install Debian directly from a remote Internet site?</h2> + +<p> +Yes. You can boot the Debian installation system from a set of files you can +download from our FTP site and its mirrors. +</p> + +<p> +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 <code><a +href="http://www.debian.org/CD/netinst/">http://www.debian.org/CD/netinst/</a></code>. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-alternativebootinstaller"></a>2.7 Are there any alternative strategies for booting the system installer?</h2> + +<p> +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 <code><a +href="http://www.debian.org/releases/stable/installmanual">Debian GNU/Linux +Installation Guide</a></code> for more information. +</p> + +<hr> + +<p> +[ <a href="ch-basic_defs.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ 2 ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-choosing.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..568d808 --- /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 0000000..58781c9 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-kernel.en.html @@ -0,0 +1,389 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Debian and the kernel</title> + +<link href="index.en.html" rel="start"> +<link href="ch-uptodate.en.html" rel="prev"> +<link href="ch-customizing.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-kernel"></a></p> +<hr> + +<p> +[ <a href="ch-uptodate.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ 10 ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-customizing.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 10 - Debian and the kernel +</h1> + +<hr> + +<h2><a name="s-non-debian-kernel"></a>10.1 Can I install and compile a kernel without some Debian-specific tweaking?</h2> + +<p> +Yes. +</p> + +<p> +There's only one common catch: the Debian C libraries are built with the most +recent <em>stable</em> releases of the <strong>kernel</strong> headers. If you +happen to need to compile a program with kernel headers newer than the ones +from the stable branch, then you should either upgrade the package containing +the headers (<code>libc6-dev</code>), or use the new headers from an unpacked +tree of the newer kernel. That is, if the kernel sources are in +<code>/usr/src/linux</code>, then you should add +<samp>-I/usr/src/linux/include/</samp> to your command line when compiling. +</p> + +<hr> + +<h2><a name="s-customkernel"></a>10.2 What tools does Debian provide to build custom kernels?</h2> + +<p> +Users who wish to (or must) build a custom kernel are encouraged to download +the package <code>kernel-package</code>. This package contains the script to +build the kernel package, and provides the capability to create a Debian +<code>linux-image-<var>version</var></code> package just by running the command +</p> + +<pre> + make-kpkg --initrd kernel_image +</pre> + +<p> +in the top-level kernel source directory. Help is available by executing the +command +</p> + +<pre> + make-kpkg --help +</pre> + +<p> +and through the manual page <code>make-kpkg(1)</code>. +</p> + +<p> +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 +<code>linux-source-<var>version</var></code> package is available (where +<var>version</var> stands for the kernel version). +</p> + +<p> +Detailed instructions for using the <code>kernel-package</code> package are +given in the file <code>/usr/share/doc/kernel-package/README.gz</code>. +</p> + +<hr> + +<h2><a name="s-custombootdisk"></a>10.3 How can I make a custom boot floppy?</h2> + +<p> +This task is greatly aided by the Debian package <code>boot-floppies</code>, +normally found in the <samp>admin</samp> section of the Debian FTP archive. +Shell scripts in this package produce boot floppies in the +<samp>SYSLINUX</samp> format. These are <samp>MS-DOS</samp> 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 +<code>syslinux.cfg</code> file on the floppy). Other scripts in this package +produce emergency root disks and can even reproduce the base disks. +</p> + +<p> +You will find more information about this in the +<code>/usr/share/doc/boot-floppies/README</code> file after installing the +<code>boot-floppies</code> package. +</p> + +<hr> + +<h2><a name="s-modules"></a>10.4 What special provisions does Debian provide to deal with modules?</h2> + +<p> +Debian's <code>modconf</code> package provides a shell script +(<code>/usr/sbin/modconf</code>) 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 +<code>/etc/modules.conf</code> (which lists aliases, and other arguments that +must be used in conjunction with various modules) through files in +<code>/etc/modutils/</code>, and <code>/etc/modules</code> (which lists the +modules that must be loaded at boot time). +</p> + +<p> +Like the (new) <code>Configure.help</code> files that are now available to +support the construction of custom kernels, the <code>modconf</code> package +comes with a series of help files (in <code>/usr/lib/modules_help/</code>) +which provide detailed information on appropriate arguments for each of the +modules. +</p> + +<hr> + +<h2><a name="s-removeoldkernel"></a>10.5 Can I safely de-install an old kernel package, and if so, how?</h2> + +<p> +Yes. The <code>linux-image-<var>NNN</var>.prerm</code> 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: +</p> + +<pre> + dpkg --purge linux-image-<var>NNN</var> +</pre> + +<p> +(replace <var>NNN</var> with your kernel version and revision number, of +course) +</p> + +<hr> + +<p> +[ <a href="ch-uptodate.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ 10 ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-customizing.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..125039f --- /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 0000000..cd6c875 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-nexttime.en.html @@ -0,0 +1,377 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Changes expected in the next major release of Debian</title> + +<link href="index.en.html" rel="start"> +<link href="ch-redistrib.en.html" rel="prev"> +<link href="ch-faqinfo.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-nexttime"></a></p> +<hr> + +<p> +[ <a href="ch-redistrib.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ 15 ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-faqinfo.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 15 - Changes expected in the next major release of Debian +</h1> + +<hr> + +<h2><a name="s-i18n"></a>15.1 Extended support for non-English users</h2> + +<p> +Debian already has very good support for non-English users, see <a +href="ch-software.en.html#s-nonenglish">How does Debian support non-English +languages?, Section 5.9</a>. +</p> + +<p> +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. +</p> + +<p> +The GNU Translation Project <code><a +href="ftp://ftp.gnu.org/pub/gnu/ABOUT-NLS">ftp://ftp.gnu.org/pub/gnu/ABOUT-NLS</a></code> +works on internationalizing the GNU programs. +</p> + +<p> +Specifically for Debian lenny, we're working on things like the following: +</p> +<ul> +<li> +<p> +I18n support in all debconf-using packages: Packages using the Debian +configuration management must allow for translation of all messages displayed +to the user during package configuration. +</p> +</li> +</ul> +<ul> +<li> +<p> +I18n support for package descriptions: Update package management frontends to +use the translated descriptions of packages. +</p> +</li> +</ul> +<ul> +<li> +<p> +UTF-8 debian/changelog and debian/control. This way, e.g. names of people +from asian countries can get typeset the right way in changelogs. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-dependencybasedboot"></a>15.2 Faster booting: Dependency based boot sequence</h2> + +<p> +Work is being done on <code><a +href="http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot">converting the +Debian boot sequence</a></code> to use dynamic and dependency based ordering +instead of hardcoded sequence numbers. Once that's finished, Debian systems +will boot much faster. +</p> + +<hr> + +<h2><a name="s-di"></a>15.3 Improvements in the Debian Installer</h2> + +<p> +Lots of work has been done on the Debian Installer, resulting in major +improvements. We'll mention just two of them here. +</p> + +<p> +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. +</p> + +<p> +The debian-installer now includes experimental support for installing Debian on +systems with Serial ATA RAID. +</p> + +<hr> + +<h2><a name="s-morearches"></a>15.4 More architectures</h2> + +<p> +Complete Debian system on other architectures such as <code><a +href="http://wiki.debian.org/ArmEabiPort">ARM EABI</a></code> (referred to as +"armel") (next to the old "arm") will likely get supported +with lenny. Support for <code><a +href="http://wiki.debian.org/SHPort">SuperH</a></code> 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 +<samp>sid</samp>. +</p> + +<hr> + +<h2><a name="s-morekernels"></a>15.5 More kernels</h2> + +<p> +In addition to Debian GNU/Hurd, Debian is being ported also to BSD kernels, +namely to <code><a +href="http://www.debian.org/ports/kfreebsd-gnu/">FreeBSD</a></code>. This port +runs on both AMD64 ("kfreebsd-amd64") and traditional Intel +("kfreebsd-i386"). +</p> + +<hr> + +<p> +[ <a href="ch-redistrib.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ 15 ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-faqinfo.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..da23d48 --- /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 0000000..72799b2 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-pkg_basics.en.html @@ -0,0 +1,1123 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Basics of the Debian package management system</title> + +<link href="index.en.html" rel="start"> +<link href="ch-ftparchives.en.html" rel="prev"> +<link href="ch-pkgtools.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-pkg_basics"></a></p> +<hr> + +<p> +[ <a href="ch-ftparchives.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ 7 ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-pkgtools.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 7 - Basics of the Debian package management system +</h1> + +<hr> + +<p> +This chapter touches on some lower level internals of Debian package +management. If you're interested mainly in <em>usage</em> of the relevant +tools, skip to chapters <a href="ch-pkgtools.en.html">The Debian package +management tools, Chapter 8</a> and/or <a href="ch-uptodate.en.html">Keeping +your Debian system up-to-date, Chapter 9</a>. +</p> + +<hr> + +<h2><a name="s-package"></a>7.1 What is a Debian package?</h2> + +<p> +Packages generally contain all of the files necessary to implement a set of +related commands or features. There are two types of Debian packages: +</p> +<ul> +<li> +<p> +<em>Binary packages</em>, which contain executables, configuration files, +man/info pages, copyright information, and other documentation. These packages +are distributed in a Debian-specific archive format (see <a +href="#s-deb-format">What is the format of a Debian binary package?, Section +7.2</a>); they are usually distinguished by having a '.deb' file extension. +Binary packages can be unpacked using the Debian utility <samp>dpkg</samp> +(possibly via a frontend like <code>aptitude</code>); details are given in its +manual page. +</p> +</li> +</ul> +<ul> +<li> +<p> +<em>Source packages</em>, which consist of a <samp>.dsc</samp> file describing +the source package (including the names of the following files), a +<samp>.orig.tar.gz</samp> file that contains the original unmodified source in +gzip-compressed tar format and usually a <samp>.diff.gz</samp> file that +contains the Debian-specific changes to the original source. The utility +<samp>dpkg-source</samp> packs and unpacks Debian source archives; details are +provided in its manual page. (The program <code>apt-get</code> can get used a +frontend for <samp>dpkg-source</samp>.) +</p> +</li> +</ul> + +<p> +Installation of software by the package system uses "dependencies" +which are carefully designed by the package maintainers. These dependencies +are documented in the <samp>control</samp> file associated with each package. +For example, the package containing the GNU C compiler (<code>gcc</code>) +"depends" on the package <code>binutils</code> which includes the +linker and assembler. If a user attempts to install <code>gcc</code> without +having first installed <code>binutils</code>, the package management system +(dpkg) will send an error message that it also needs <code>binutils</code>, and +stop installing <code>gcc</code>. (However, this facility can be overridden by +the insistent user, see <code>dpkg(8)</code>.) See more in <a +href="#s-depends">What is meant by saying that a package <em>Depends</em>, +<em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> +or <em>Provides</em> another package?, Section 7.9</a> below. +</p> + +<p> +Debian's packaging tools can be used to: +</p> +<ul> +<li> +<p> +manipulate and manage packages or parts of packages, +</p> +</li> +</ul> +<ul> +<li> +<p> +administer local overrides of files in a package, +</p> +</li> +</ul> +<ul> +<li> +<p> +aid developers in the construction of package archives, and +</p> +</li> +</ul> +<ul> +<li> +<p> +aid users in the installation of packages which reside on a remote FTP site. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-deb-format"></a>7.2 What is the format of a Debian binary package?</h2> + +<p> +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 <samp>.deb</samp>. +</p> + +<p> +The internals of this Debian binary packages format are described in the +<code>deb(5)</code> manual page. This internal format is subject to change +(between major releases of Debian GNU/Linux), therefore please always use +<code>dpkg-deb(1)</code> if you need to do lowlevel manipulations on +<samp>.deb</samp> files. +</p> + +<hr> + +<h2><a name="s-pkgname"></a>7.3 Why are Debian package file names so long?</h2> + +<p> +The Debian binary package file names conform to the following convention: +<foo>_<VersionNumber>-<DebianRevisionNumber>_<DebianArchitecture>.deb +</p> + +<p> +Note that <samp>foo</samp> 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: +</p> +<ul> +<li> +<p> +inspect the "Packages" file in the directory where it was stored at a +Debian FTP archive site. This file contains a stanza describing each package; +the first field in each stanza is the formal package name. +</p> +</li> +</ul> +<ul> +<li> +<p> +use the command <samp>dpkg --info foo_VVV-RRR_AAA.deb</samp> (where VVV, RRR +and AAA are the version, revision and architecture of the package in question, +respectively). This displays, among other things, the package name +corresponding to the archive file being unpacked. +</p> +</li> +</ul> + +<p> +The <samp>VVV</samp> 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". +</p> + +<p> +The <samp>RRR</samp> 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 (<samp>debian/rules</samp>), the Debian control file +(<samp>debian/control</samp>), the installation or removal scripts +(<samp>debian/p*</samp>), or in the configuration files used with the package. +</p> + +<p> +The <samp>AAA</samp> component identifies the processor for which the package +was built. This is commonly <samp>i386</samp>, which refers to chips +compatible to Intel's 386 or later versions. For other possibilities review +Debian's FTP directory structure at <a +href="ch-ftparchives.en.html#s-dirtree">What are all those directories at the +Debian FTP archives?, Section 6.7</a>. For details, see the description of +"Debian architecture" in the manual page +<code>dpkg-architecture(1)</code>. +</p> + +<hr> + +<h2><a name="s-controlfile"></a>7.4 What is a Debian control file?</h2> + +<p> +Specifics regarding the contents of a Debian control file are provided in the +Debian Policy Manual, section 5, see <a +href="ch-support.en.html#s-debiandocs">What other documentation exists on and +for a Debian system?, Section 12.1</a>. +</p> + +<p> +Briefly, a sample control file is shown below for the Debian package hello: +</p> + +<pre> + 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). +</pre> + +<p> +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. +</p> + +<p> +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 <a href="#s-pkgname">Why are Debian package file names so long?, +Section 7.3</a>. +</p> + +<p> +The Architecture field specifies the chip for which this particular binary was +compiled. +</p> + +<p> +The Depends field gives a list of packages that have to be installed in order +to install this package successfully. +</p> + +<p> +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. +</p> + +<p> +The Section line gives the "section" where this Debian package is +stored at the Debian FTP sites. +</p> + +<p> +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 <a +href="#s-priority">What is an <em>Essential</em>, <em>Required</em>, +<em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> +package?, Section 7.7</a>. +</p> + +<p> +The Maintainer field gives the e-mail address of the person who is currently +responsible for maintaining this package. +</p> + +<p> +The Description field gives a brief summary of the package's features. +</p> + +<p> +For more information about all possible fields a package can have, please see +the Debian Policy Manual, section 5., "Control files and their +fields". +</p> + +<hr> + +<h2><a name="s-conffile"></a>7.5 What is a Debian conffile?</h2> + +<p> +Conffiles is a list of configuration files (usually placed in +<samp>/etc</samp>) 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. +</p> + +<p> +To determine exactly which files are preserved during an upgrade, run: +</p> + +<pre> + dpkg --status package +</pre> + +<p> +And look under "Conffiles:". +</p> + +<hr> + +<h2><a name="s-maintscripts"></a>7.6 What is a Debian preinst, postinst, prerm, and postrm script?</h2> + +<p> +These files are executable scripts which are automatically run before or after +a package is installed. Along with a file named <samp>control</samp>, all of +these files are part of the "control" section of a Debian archive +file. +</p> + +<p> +The individual files are: +</p> +<dl> +<dt>preinst</dt> +<dd> +<p> +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). +</p> +</dd> +</dl> +<dl> +<dt>postinst</dt> +<dd> +<p> +This script typically completes any required configuration of the package +<samp>foo</samp> once <samp>foo</samp> 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. +</p> +</dd> +</dl> +<dl> +<dt>prerm</dt> +<dd> +<p> +This script typically stops any daemons which are associated with a package. +It is executed before the removal of files associated with the package. +</p> +</dd> +</dl> +<dl> +<dt>postrm</dt> +<dd> +<p> +This script typically modifies links or other files associated with +<samp>foo</samp>, and/or removes files created by the package. (Also see <a +href="#s-virtual">What is a Virtual Package?, Section 7.8</a>.) +</p> +</dd> +</dl> + +<p> +Currently all of the control files can be found in directory +<samp>/var/lib/dpkg/info</samp>. The files relevant to package +<samp>foo</samp> begin with the name "foo" and have file extensions +of "preinst", "postinst", etc., as appropriate. The file +<samp>foo.list</samp> in that directory lists all of the files that were +installed with the package <samp>foo</samp>. (Note that the location of these +files is a dpkg internal; you should not rely on it.) +</p> + +<hr> + +<h2><a name="s-priority"></a>7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?</h2> + +<p> +Each Debian package is assigned a <em>priority</em> by the distribution +maintainers, as an aid to the package management system. The priorities are: +</p> +<ul> +<li> +<p> +<strong>Required</strong>: packages that are necessary for the proper +functioning of the system. +</p> + +<p> +This includes all tools that are necessary to repair system defects. You must +not remove these packages or your system may become totally broken and you may +probably not even be able to use dpkg to put things back. Systems with only +the Required packages are probably unusable, but they do have enough +functionality to allow the sysadmin to boot and install more software. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>Important</strong> packages should be found on any Unix-like system. +</p> + +<p> +Other packages which the system will not run well or be usable without will be +here. This does <em>NOT</em> include Emacs or X or TeX or any other large +applications. These packages only constitute the bare infrastructure. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>Standard</strong> packages are standard on any Linux system, including +a reasonably small but not too limited character-mode system. Tools are +included to be able to browse the web (using w3m), send e-mail (with mutt) and +download files from FTP servers. +</p> + +<p> +This is what will install by default if users do not select anything else. It +does not include many large applications, but it does include the Python +interpreter and some server software like OpenSSH (for remote administration), +Exim (for mail delivery, although it can be configured for local delivery +only), an identd server (pidentd) and the RPC portmapper +(<samp>portmap</samp>). It also includes some common generic documentation +that most users will find helpful. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>Optional</strong> packages include all those that you might reasonably +want to install if you did not know what it was, or do not have specialized +requirements. +</p> + +<p> +This includes X, a full TeX distribution, and lots of applications. +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>Extra</strong>: packages that either conflict with others with higher +priorities, are only likely to be useful if you already know what they are, or +have specialized requirements that make them unsuitable for +"Optional". +</p> +</li> +</ul> + +<p> +If you do a default Debian installation all the packages of priority +<strong>Standard</strong> or higher will be installed in your system. If you +select pre-defined tasks you will get lower priority packages too. +</p> + +<p> +Additionally, some packages are marked as <strong>Essential</strong> since they +are absolutely necessary for the proper functioning of the system. The package +management tools will refuse to remove these. +</p> + +<hr> + +<h2><a name="s-virtual"></a>7.8 What is a Virtual Package?</h2> + +<p> +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 <samp>tin</samp> and <samp>trn</samp> 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 <samp>news-reader</samp>. +</p> + +<p> +Similarly, <samp>smail</samp> and <samp>sendmail</samp> 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 +<samp>mail-transport-agent</samp> will be satisfied by the existence of this +virtual package. +</p> + +<p> +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 +<samp>update-alternatives</samp>, and is described further in <a +href="ch-customizing.en.html#s-diverse">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</a>. +</p> + +<hr> + +<h2><a name="s-depends"></a>7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?</h2> + +<p> +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: +</p> +<ul> +<li> +<p> +Package A <em>depends</em> on Package B if B absolutely must be installed in +order to run A. In some cases, A depends not only on B, but on a version of B. +In this case, the version dependency is usually a lower limit, in the sense +that A depends on any version of B more recent than some specified version. +</p> +</li> +</ul> +<ul> +<li> +<p> +Package A <em>recommends</em> Package B, if the package maintainer judges that +most users would not want A without also having the functionality provided by +B. +</p> +</li> +</ul> +<ul> +<li> +<p> +Package A <em>suggests</em> Package B if B contains files that are related to +(and usually enhance) the functionality of A. +</p> +</li> +</ul> +<ul> +<li> +<p> +Package A <em>conflicts</em> with Package B when A will not operate if B is +installed on the system. Most often, conflicts are cases where A contains +files which are an improvement over those in B. "Conflicts" are +often combined with "replaces". +</p> +</li> +</ul> +<ul> +<li> +<p> +Package A <em>replaces</em> Package B when files installed by B are removed and +(in some cases) over-written by files in A. +</p> +</li> +</ul> +<ul> +<li> +<p> +Package A <em>provides</em> Package B when all of the files and functionality +of B are incorporated into A. This mechanism provides a way for users with +constrained disk space to get only that part of package A which they really +need. +</p> +</li> +</ul> + +<p> +More detailed information on the use of each these terms can be found in the +Policy manual. +</p> + +<hr> + +<h2><a name="s-pre-depends"></a>7.10 What is meant by Pre-Depends?</h2> + +<p> +"Pre-Depends" is a special dependency. In the case of most packages, +<samp>dpkg</samp> will unpack its archive file (i.e., its <samp>.deb</samp> +file) independently of whether or not the files on which it depends exist on +the system. Simplistically, unpacking means that <samp>dpkg</samp> will +extract the files from the archive file that were meant to be installed on your +file system, and put them in place. If those packages <em>depend</em> on the +existence of some other packages on your system, <samp>dpkg</samp> will refuse +to complete the installation (by executing its "configure" action) +until the other packages are installed. +</p> + +<p> +However, for some packages, <samp>dpkg</samp> 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 +<samp>a.out</samp> format to <samp>ELF</samp> format, where the <em>order</em> +in which packages were unpacked was critical. There are other large upgrade +situations where this method is useful, e.g. the packages with the required +priority and their LibC dependency. +</p> + +<p> +As before, more detailed information about this can be found in the Policy +manual. +</p> + +<hr> + +<h2><a name="s-pkgstatus"></a>7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?</h2> + +<p> +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 +<samp>dselect</samp>, or by the user's direct invocations of +<samp>dpkg</samp>). +</p> + +<p> +Their meanings are: +</p> +<ul> +<li> +<p> +unknown - the user has never indicated whether he wants the package +</p> +</li> +</ul> +<ul> +<li> +<p> +install - the user wants the package installed or upgraded +</p> +</li> +</ul> +<ul> +<li> +<p> +remove - the user wants the package removed, but does not want to remove any +existing configuration files. +</p> +</li> +</ul> +<ul> +<li> +<p> +purge - the user wants the package to be removed completely, including its +configuration files. +</p> +</li> +</ul> +<ul> +<li> +<p> +hold - the user wants this package not to be processed, i.e., he wants to keep +the current version with the current status whatever that is. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-puttingonhold"></a>7.12 How do I put a package on hold?</h2> + +<p> +There are three ways of holding back packages, with dpkg, aptitude or with +dselect. +</p> + +<p> +With dpkg, you have to export the list of package selections, with: +</p> + +<pre> + dpkg --get-selections \* > selections.txt +</pre> + +<p> +Then edit the resulting file <code>selections.txt</code>, change the line +containing the package you wish to hold, e.g. <code>libc6</code>, from this: +</p> + +<pre> + libc6 install +</pre> + +<p> +to this: +</p> + +<pre> + libc6 hold +</pre> + +<p> +Save the file, and reload it into dpkg database with: +</p> + +<pre> + dpkg --set-selections < selections.txt +</pre> + +<p> +With aptitude, you can hold a package using +</p> + +<pre> + aptitude hold package_name +</pre> + +<p> +and remove the hold with +</p> + +<pre> + aptitude unhold package_name +</pre> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-sourcepkgs"></a>7.13 How do I install a source package?</h2> + +<p> +Debian source packages can't actually be "installed", they are just +unpacked in whatever directory you want to build the binary packages they +produce. +</p> + +<p> +Source packages are distributed on most of the same mirrors where you can +obtain the binary packages. If you set up your APT's +<code>sources.list(5)</code> to include the appropriate "deb-src" +lines, you'll be able to easily download any source packages by running +</p> + +<pre> + apt-get source foo +</pre> + +<p> +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 +</p> + +<pre> + apt-get build-dep foo +</pre> + +<p> +before building the source. +</p> + +<hr> + +<h2><a name="s-sourcebuild"></a>7.14 How do I build binary packages from a source package?</h2> + +<p> +The preferred way to do this is by using various wrapper tools. We'll show how +it's done using the <samp>devscripts</samp> tools. Install this package if you +haven't done so already. +</p> + +<p> +Now, first get the source package: +</p> + +<pre> + apt-get source foo +</pre> + +<p> +and change to the source tree: +</p> + +<pre> + cd foo-* +</pre> + +<p> +Then install needed build-dependencies (if any): +</p> + +<pre> + sudo apt-get build-dep foo +</pre> + +<p> +Then create a dedicated version of your own build (so that you won't get +confused later when Debian itself releases a new version) +</p> + +<pre> + dch -l local 'Blah blah blah' +</pre> + +<p> +And finally build your package +</p> + +<pre> + debuild -us -uc +</pre> + +<p> +If everything worked out fine, you should now be able to install your package +by running +</p> + +<pre> + sudo dpkg -i ../*.deb +</pre> + +<p> +If you prefer to do things manually, and don't want to use +<samp>devscripts</samp>, follow this procedure: +</p> + +<p> +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). +</p> + +<p> +Once you have them (<a href="#s-sourcepkgs">How do I install a source package?, +Section 7.13</a>), if you have the <code>dpkg-dev</code> package installed, the +following command: +</p> + +<pre> + dpkg-source -x foo_version-revision.dsc +</pre> + +<p> +will extract the package into a directory called <samp>foo-version</samp>. +</p> + +<p> +If you want just to compile the package, you may cd into +<samp>foo-version</samp> directory and issue the command +</p> + +<pre> + dpkg-buildpackage -rfakeroot -b +</pre> + +<p> +to build the package (note that this also requires the <code>fakeroot</code> +package), and then +</p> + +<pre> + dpkg -i ../foo_version-revision_arch.deb +</pre> + +<p> +to install the newly-built package(s). +</p> + +<hr> + +<h2><a name="s-creatingdebs"></a>7.15 How do I create Debian packages myself?</h2> + +<p> +For a more detailed description on this, read the New Maintainers' Guide, +available in the <code>maint-guide</code> package, or at <code><a +href="http://www.debian.org/doc/devel-manuals#maint-guide">http://www.debian.org/doc/devel-manuals#maint-guide</a></code>. +</p> + +<hr> + +<p> +[ <a href="ch-ftparchives.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ 7 ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-pkgtools.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..98c97fe --- /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 0000000..391e656 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-pkgtools.en.html @@ -0,0 +1,1199 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - The Debian package management tools</title> + +<link href="index.en.html" rel="start"> +<link href="ch-pkg_basics.en.html" rel="prev"> +<link href="ch-uptodate.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-pkgtools"></a></p> +<hr> + +<p> +[ <a href="ch-pkg_basics.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ 8 ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-uptodate.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 8 - The Debian package management tools +</h1> + +<hr> + +<h2><a name="s-pkgprogs"></a>8.1 What programs does Debian provide for managing its packages?</h2> + +<p> +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. +</p> + +<p> +It is important to understand that the higher level package management tools +such as <code>aptitude</code> or <code>dselect</code> rely on <code>apt</code> +which, itself, relies on <code>dpkg</code> to manage the packages in the +system. +</p> + +<p> +See the <code><a href="http://www.debian.org/doc/manuals/apt-howto/">APT +HOWTO</a></code> for more information about the Debian package management +utilities. This document is available in various languages and formats, see +<code><a href="http://www.debian.org/doc/user-manuals#apt-howto">the APT HOWTO +entry on the DDP Users' Manuals overview</a></code>. +</p> + +<hr> + +<h3><a name="s-dpkg"></a>8.1.1 dpkg</h3> + +<p> +This is the main package management program. <code>dpkg</code> can be invoked +with many options. Some common uses are: +</p> +<ul> +<li> +<p> +Find out all the options: <samp>dpkg --help</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Print out the control file (and other information) for a specified package: +<samp>dpkg --info foo_VVV-RRR.deb</samp> +</p> +</li> +</ul> +<ul> +<li> +<p> +Install a package (including unpacking and configuring) onto the file system of +the hard disk: <samp>dpkg --install foo_VVV-RRR.deb</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Unpack (but do not configure) a Debian archive into the file system of the hard +disk: <samp>dpkg --unpack foo_VVV-RRR.deb</samp>. Note that this operation +does <em>not</em> necessarily leave the package in a usable state; some files +may need further customization to run properly. This command removes any +already-installed version of the program and runs the preinst (see <a +href="ch-pkg_basics.en.html#s-maintscripts">What is a Debian preinst, postinst, +prerm, and postrm script?, Section 7.6</a>) script associated with the package. +</p> +</li> +</ul> +<ul> +<li> +<p> +Configure a package that already has been unpacked: <samp>dpkg --configure +foo</samp>. Among other things, this action runs the postinst (see <a +href="ch-pkg_basics.en.html#s-maintscripts">What is a Debian preinst, postinst, +prerm, and postrm script?, Section 7.6</a>) script associated with the package. +It also updates the files listed in the <samp>conffiles</samp> for this +package. Notice that the 'configure' operation takes as its argument a package +name (e.g., foo), <em>not</em> the name of a Debian archive file (e.g., +foo_VVV-RRR.deb). +</p> +</li> +</ul> +<ul> +<li> +<p> +Extract a single file named "blurf" (or a group of files named +"blurf*" from a Debian archive: <samp>dpkg --fsys-tarfile +foo_VVV-RRR.deb | tar -xf - blurf*</samp> +</p> +</li> +</ul> +<ul> +<li> +<p> +Remove a package (but not its configuration files): <samp>dpkg --remove +foo</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Remove a package (including its configuration files): <samp>dpkg --purge +foo</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +List the installation status of packages containing the string (or regular +expression) "foo*": <samp>dpkg --list 'foo*'</samp>. +</p> +</li> +</ul> + +<hr> + +<h3><a name="s-apt-get"></a>8.1.2 APT</h3> + +<p> +APT is the <em>Advanced Package Tool</em> and provides the <code>apt-get</code> +program. <code>apt-get</code> provides a simple way to retrieve and install +packages from multiple sources using the command line. Unlike +<code>dpkg</code>, <code>apt-get</code> does not understand .deb files, it +works with the packages proper name and can only install .deb archives from a +source specified in <code>/etc/apt/sources.list</code>. <code>apt-get</code> +will call <code>dpkg</code> directly after downloading the .deb archives[<a +href="footnotes.en.html#f5" name="fr5">5</a>] from the configured sources. +</p> + +<p> +Some common ways to use <code>apt-get</code> are: +</p> +<ul> +<li> +<p> +To update the list of package known by your system, you can run: +</p> + +<pre> + apt-get update +</pre> + +<p> +(you should execute this regularly to update your package lists) +</p> +</li> +</ul> +<ul> +<li> +<p> +To upgrade all the packages on your system (without installing extra packages +or removing packages), run: +</p> + +<pre> + apt-get upgrade +</pre> +</li> +</ul> +<ul> +<li> +<p> +To install the <var>foo</var> package and all its dependencies, run: +</p> + +<pre> + apt-get install foo +</pre> +</li> +</ul> +<ul> +<li> +<p> +To remove the foo package from your system, run: +</p> + +<pre> + apt-get remove foo +</pre> +</li> +</ul> +<ul> +<li> +<p> +To remove the foo package and its configuration files from your system, run: +</p> + +<pre> + apt-get --purge remove foo +</pre> +</li> +</ul> +<ul> +<li> +<p> +To upgrade all the packages on your system, and, if needed for a package +upgrade, installing extra packages or removing packages, run: +</p> + +<pre> + apt-get dist-upgrade +</pre> + +<p> +(The command <samp>upgrade</samp> keeps a package at its installed obsolete +version if upgrading would need an extra package to be installed, for a new +dependency to be satisfied. The <samp>dist-upgrade</samp> command is less +conservative.) +</p> +</li> +</ul> + +<p> +Note that you must be logged in as root to perform any commands that modify the +system packages. +</p> + +<p> +The apt tool suite also includes the <code>apt-cache</code> 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 <code>apt-cache</code> are: +</p> +<ul> +<li> +<p> +To find packages whose description contain <var>word</var>: +</p> + +<pre> + apt-cache search <var>word</var> +</pre> +</li> +</ul> +<ul> +<li> +<p> +To print the detailed information of a package: +</p> + +<pre> + apt-cache show <var>package</var> +</pre> +</li> +</ul> +<ul> +<li> +<p> +To print the packages a given package depends on: +</p> + +<pre> + apt-cache depends <var>package</var> +</pre> +</li> +</ul> +<ul> +<li> +<p> +To print detailed information of the versions available for a package and the +packages that reverse-depends on it: +</p> + +<pre> + apt-cache showpkg <var>package</var> +</pre> +</li> +</ul> + +<p> +For more information, install the <code>apt</code> package and read +<code>apt-get(8)</code>, <code>sources.list(5)</code> and install the +<code>apt-doc</code> package and read +<code>/usr/share/doc/apt-doc/guide.html/index.html</code>. +</p> + +<hr> + +<h3><a name="s-aptitude"></a>8.1.3 aptitude</h3> + +<p> +<code>aptitude</code> is a package manager for Debian GNU/Linux systems that +provides a frontend to the apt package management infrastructure. +<code>aptitude</code> is a text-based interface using the curses library, it +can be used to perform management tasks in a fast and easy way. +</p> + +<p> +<code>aptitude</code> provides the functionality of <code>dselect</code> and +<code>apt-get</code>, as well as many additional features not found in either +program: +</p> +<ul> +<li> +<p> +<code>aptitude</code> offers access to all versions of a package. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> logs all its actions in <code>/var/log/aptitude</code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> makes it easy to keep track of obsolete software by +listing it under "Obsolete and Locally Created Packages". +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> includes a fairly powerful system for searching +particular packages and limiting the package display. Users familiar with +<code>mutt</code> will pick up quickly, as <code>mutt</code> was the +inspiration for the expression syntax. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> tracks which packages have been installed due to +dependencies and removes them automatically when the packages that needed them +are removed from the system. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> can automatically install <em>Recommended:</em> +packages[<a href="footnotes.en.html#f6" name="fr6">6</a>]. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> can be used to install the predefined tasks available. +For more information see <a href="#s-tasksel">tasksel, Section 8.1.5</a>. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code>aptitude</code> in full screen mode has <code>su</code> functionality +embedded and can be run by a normal user. It will call <code>su</code> (and +ask for the root password, if any) when you really need administrative +privileges +</p> +</li> +</ul> + +<p> +You can use <code>aptitude</code> through a visual interface (simply run +<samp>aptitude</samp>) or directly from the command line. The command line +syntax used is very similar to the one used in <code>apt-get</code>. For +example, to install the <var>foo</var> package, you can run <samp>aptitude +install <var>foo</var></samp>. +</p> + +<p> +Note that <code>aptitude</code> is the preferred program for package management +from console both for package installations and package or system upgrades. +</p> + +<p> +For more informations, read the manual page <code>aptitude(8)</code> and +install the <code>aptitude-doc</code> package. +</p> + +<hr> + +<h3><a name="s-synaptic"></a>8.1.4 synaptic</h3> + +<p> +<code>synaptic</code> 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 <code><a href="http://www.nongnu.org/synaptic/">Synaptic +Website</a></code> for more information. +</p> + +<hr> + +<h3><a name="s-tasksel"></a>8.1.5 tasksel</h3> + +<p> +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 <samp>tasks</samp>, a task is a collection of several individual Debian +packages all related to a specific activity. Tasks can be installed through +the <code>tasksel</code> program or through <code>aptitude</code>. +</p> + +<p> +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 (<samp>gnome-desktop</samp> 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 +<samp>laptop</samp> task will be installed too. +</p> + +<hr> + +<h3><a name="s-dpkg-extra"></a>8.1.6 Other package management tools</h3> + +<hr> + +<h4><a name="s-dselect"></a>8.1.6.1 dselect</h4> + +<p> +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 <code>aptitude</code> instead. Some users might feel more comfortable +using <code>aptitude</code> and it is also recommended over +<code>dselect</code> for large-scale upgrades. For more information on +<code>aptitude</code> please see <a href="#s-aptitude">aptitude, Section +8.1.3</a>. +</p> + +<p> +<code>dselect</code> can: +</p> +<ul> +<li> +<p> +guide the user as he/she chooses among packages to install or remove, ensuring +that no packages are installed that conflict with one another, and that all +packages required to make each package work properly are installed; +</p> +</li> +</ul> +<ul> +<li> +<p> +warn the user about inconsistencies or incompatibilities in their selections; +</p> +</li> +</ul> +<ul> +<li> +<p> +determine the order in which the packages must be installed; +</p> +</li> +</ul> +<ul> +<li> +<p> +automatically perform the installation or removal; and +</p> +</li> +</ul> +<ul> +<li> +<p> +guide the user through whatever configuration process are required for each +package. +</p> +</li> +</ul> + +<p> +<code>dselect</code> begins by presenting the user with a menu of 7 items, each +of which is a specific action. The user can select one of the actions by using +the arrow keys to move the highlighter bar, then pressing the +<em><enter></em> key to select the highlighted action. +</p> + +<p> +What the user sees next depends on the action he selected. If he selects any +option but <samp>Access</samp> or <samp>Select</samp>, then +<code>dselect</code> will simply proceed to execute the specified action: e.g., +if the user selected the action <samp>Remove</samp>, then dselect would proceed +to remove all of the files selected for removal when the user last chose the +<samp>Select</samp> action. +</p> + +<p> +Both the <samp>Access</samp> menu item and the <samp>Select</samp> 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. +</p> + +<p> +Extensive on-line help is available, use the '?' key to get to a help screen +at any time. +</p> + +<p> +The order in which the actions are presented in the first <code>dselect</code> +menu represents the order in which a user would normally choose +<code>dselect</code> 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). +</p> +<ul> +<li> +<p> +Begin by choosing an <strong>Access Method</strong>. This is the method by +which the user plans on accessing Debian packages; e.g., some users have Debian +packages available on CD-ROM, while others plan to fetch them using anonymous +FTP. The selected "Access Method" is stored after +<code>dselect</code> exits, so if it does not change, then this option need not +be invoked again. +</p> +</li> +</ul> +<ul> +<li> +<p> +Then <strong>Update</strong> the list of available packages. To do this, +<code>dselect</code> reads the file "Packages.gz" which should be +included in the top level of the directory where the Debian packages to be +installed are stored. (But if it is not there, <code>dselect</code> will offer +to make it for you.) +</p> +</li> +</ul> +<ul> +<li> +<p> +<strong>Select</strong> specific packages for installation on his system. +After choosing this menu item, the user is first presented with a full screen +of help (unless the `--expert' command line option was used). Once the user +exits the Help screen, he sees the split-screen menu for choosing packages to +install (or remove). +</p> + +<p> +The top part of the screen is a relatively narrow window into the list of +Debian's 18200 packages; the bottom part of the screen contains description of +the package or group of packages which are highlighted above. +</p> + +<p> +One can specify which packages should be operated on by highlighting a package +name or the label for a group of packages. After that, you can select +packages: +</p> +<dl> +<dt>to be installed:</dt> +<dd> +<p> +This is accomplished by pressing the `+' key. +</p> +</dd> +</dl> +<dl> +<dt>to be deleted:</dt> +<dd> +<p> +Packages can be deleted two ways: +</p> +<ul> +<li> +<p> +removed: this removes most of the files associated with the package, but +preserves the files listed as configuration files (see <a +href="ch-pkg_basics.en.html#s-conffile">What is a Debian conffile?, Section +7.5</a>) and package configuration information. This is done by pressing the +`-' key. +</p> +</li> +</ul> +<ul> +<li> +<p> +purged: this removes <em>every</em> file that is part of the package. This is +done by pressing the `_' key. +</p> +</li> +</ul> + +<p> +Note that it's not possible to remove "All Packages". If you try +that, your system will instead be reduced to the initial installed base +packages. +</p> +</dd> +</dl> +<dl> +<dt>to be put "on hold"</dt> +<dd> +<p> +This is done by pressing `=', and it effectively tells <code>dselect</code> not +to upgrade a package even if the version currently installed on your system is +not as recent as the version that is available in the Debian repository you are +using (this was specified when you set the <strong>Access Method</strong>, and +acquired when you used <strong>Update</strong>). +</p> + +<p> +Just like you can put a package on hold, you can reverse such setting by +pressing `:'. That tells <code>dselect</code> that the package(s) may be +upgraded if a newer version is available. This is the default setting. +</p> +</dd> +</dl> + +<p> +You can select a different order in which the packages are presented, by using +the `o' key to cycle between various options for sorting the packages. The +default order is to present packages by Priority; within each priority, +packages are presented in order of the directory (a.k.a. section) of the +archive in which they are stored. Given this sort order, some packages in +section A (say) may be presented first, followed by some packages in section B, +followed by more packages (of lower priority) in section A. +</p> + +<p> +You can also expand meanings of the labels at the top of the screen, by using +the `v' (verbose) key. This action pushes much of the text that formerly fit +onto the display off to the right. To see it, press the right arrow; to scroll +back to the left, press the left arrow. +</p> + +<p> +If you select a package for installation or removal, e.g., +<code>foo.deb</code>, and that package depends on (or recommends) another +package, e.g., <code>blurf.deb</code>, then <code>dselect</code> will place the +you in a sub-screen of the main selection screen. There you can choose among +the related packages, accepting the suggested actions (to install or not), or +rejecting them. To do the latter, press Shift-D; to return to the former, +press Shift-U. In any case, you can save your selections and return to the +main selection screen by pressing Shift-Q. +</p> +</li> +</ul> +<ul> +<li> +<p> +Users returning to the main menu can then select the "Install" menu +item to unpack and configure the selected packages. Alternatively, users +wishing to remove files can choose the "Remove" menu item. At any +point, users can choose "Quit" to exit dselect; users' selections are +preserved by <code>dselect</code>. +</p> +</li> +</ul> + +<hr> + +<h4><a name="s-dpkg-deb"></a>8.1.6.2 dpkg-deb</h4> + +<p> +This program manipulates Debian archive(<samp>.deb</samp>) files. Some common +uses are: +</p> +<ul> +<li> +<p> +Find out all the options: <samp>dpkg-deb --help</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Determine what files are contained in a Debian archive file: <samp>dpkg-deb +--contents foo_VVV-RRR.deb</samp>) +</p> +</li> +</ul> +<ul> +<li> +<p> +Extract the files contained in a named Debian archive into a user specified +directory: <samp>dpkg-deb --extract foo_VVV-RRR.deb tmp</samp> extracts each of +the files in <samp>foo_VVV-RRR.deb</samp> into the directory <samp>tmp/</samp>. +This is convenient for examining the contents of a package in a localized +directory, without installing the package into the root file system. +</p> +</li> +</ul> +<ul> +<li> +<p> +Extract the control information files from a package: <samp>dpkg-deb --control +foo_VVV-RRR.deb tmp</samp>. +</p> +</li> +</ul> + +<p> +Note that any packages that were merely unpacked using <samp>dpkg-deb +--extract</samp> will be incorrectly installed, you should use <samp>dpkg +--install</samp> instead. +</p> + +<p> +More information is given in the manual page <code>dpkg-deb(1)</code>. +</p> + +<hr> + +<h4><a name="s-dpkg-split"></a>8.1.6.3 dpkg-split</h4> + +<p> +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 <code>dpkg</code> package), since it calls the program +<samp>dpkg-deb</samp> to parse the debian package file into its component +records. +</p> + +<p> +For example, to split a big .deb file into N parts, +</p> +<ul> +<li> +<p> +Execute the command <samp>dpkg-split --split foo.deb</samp>. This will produce +N files each of approximately 460 KBytes long in the current directory. +</p> +</li> +</ul> +<ul> +<li> +<p> +Copy those N files to floppy disks. +</p> +</li> +</ul> +<ul> +<li> +<p> +Copy the contents of the floppy disks onto the hard disk of your choice on the +other machine. +</p> +</li> +</ul> +<ul> +<li> +<p> +Join those part-files together using <samp>dpkg-split --join +"foo*"</samp>. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-updaterunning"></a>8.2 Debian claims to be able to update a running program; how is this accomplished?</h2> + +<p> +The kernel (file system) in Debian GNU/Linux systems supports replacing files +even while they're being used. +</p> + +<p> +We also provide a program called <code>start-stop-daemon</code> 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. +</p> + +<hr> + +<h2><a name="s-whatpackages"></a>8.3 How can I tell what packages are already installed on a Debian system?</h2> + +<p> +To learn the status of all the packages installed on a Debian system, execute +the command +</p> + +<pre> + dpkg --list +</pre> + +<p> +This prints out a one-line summary for each package, giving a 2-letter status +symbol (explained in the header), the package name, the version which is +<em>installed</em>, and a brief description. +</p> + +<p> +To learn the status of packages whose names match the string any pattern +beginning with "foo" by executing the command: +</p> + +<pre> + dpkg --list 'foo*' +</pre> + +<p> +To get a more verbose report for a particular package, execute the command: +</p> + +<pre> + dpkg --status packagename +</pre> + +<hr> + +<h2><a name="s-listfiles"></a>8.4 How to display the files of a package installed?</h2> + +<p> +To list all the files provided by the installed package <samp>foo</samp> +execute the command +</p> + +<pre> + dpkg --listfiles foo +</pre> + +<p> +Note that the files created by the installation scripts aren't displayed. +</p> + +<hr> + +<h2><a name="s-filesearch"></a>8.5 How can I find out what package produced a particular file?</h2> + +<p> +To identify the package that produced the file named <samp>foo</samp> execute +either: +</p> +<ul> +<li> +<p> +<samp>dpkg --search filename</samp> +</p> + +<p> +This searches for <samp>filename</samp> in installed packages. (This is +(currently) equivalent to searching all of the files having the file extension +of <samp>.list</samp> in the directory <samp>/var/lib/dpkg/info/</samp>, and +adjusting the output to print the names of all the packages containing it, and +diversions.) +</p> + +<p> +A faster alternative to this is the <code>dlocate</code> tool. +</p> + +<pre> + dlocate -S filename +</pre> +</li> +</ul> +<ul> +<li> +<p> +<samp>zgrep foo Contents-ARCH.gz</samp> +</p> + +<p> +This searches for files which contain the substring <samp>foo</samp> in their +full path names. The files <samp>Contents-ARCH.gz</samp> (where ARCH +represents the wanted architecture) reside in the major package directories +(main, non-free, contrib) at a Debian FTP site (i.e. under +<samp>/debian/dists/etch</samp>). A <samp>Contents</samp> file refers only to +the packages in the subdirectory tree where it resides. Therefore, a user +might have to search more than one <samp>Contents</samp> files to find the +package containing the file <samp>foo</samp>. +</p> + +<p> +This method has the advantage over <samp>dpkg --search</samp> in that it will +find files in packages that are not currently installed on your system. +</p> +</li> +</ul> +<ul> +<li> +<p> +<samp>apt-file search <var>foo</var></samp> +</p> + +<p> +If you install the <code>apt-file</code>, similar to the above, it searches +files which contain the substring or regular expression <samp>foo</samp> in +their full path names. The advantage over the sample above is that there is no +need to retrieve the <samp>Contents-ARCH.gz</samp> files as it will do this +automatically for all the sources defined in <code>/etc/apt/sources.list</code> +when you run (as root) <samp>apt-file update</samp>. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-datapackages"></a>8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?</h2> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +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 <code>aptitude</code> (see <a +href="#s-aptitude">aptitude, Section 8.1.3</a>) 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. +</p> + +<hr> + +<p> +[ <a href="ch-pkg_basics.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ 8 ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-uptodate.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..6c9eeed --- /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 0000000..77bbf56 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-redistrib.en.html @@ -0,0 +1,340 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Redistributing Debian GNU/Linux in a commercial product</title> + +<link href="index.en.html" rel="start"> +<link href="ch-contributing.en.html" rel="prev"> +<link href="ch-nexttime.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-redistrib"></a></p> +<hr> + +<p> +[ <a href="ch-contributing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ 14 ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-nexttime.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 14 - Redistributing Debian GNU/Linux in a commercial product +</h1> + +<hr> + +<h2><a name="s-sellcds"></a>14.1 Can I make and sell Debian CDs?</h2> + +<p> +Go ahead. You do not need permission to distribute anything we have +<em>released</em>, so that you can master your CD as soon as the beta-test +ends. You do not have to pay us anything. Of course, all CD manufacturers +must honor the licenses of the programs in Debian. For example, many of the +programs are licensed under the GPL, which requires you to distribute their +source code. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-packagednonfree"></a>14.2 Can Debian be packaged with non-free software?</h2> + +<p> +Yes. While all the main components of Debian are free software, we provide a +non-free directory for programs that are not freely redistributable. +</p> + +<p> +CD manufacturers <em>may</em> be able to distribute the programs we have placed +in that directory, depending on the license terms or their private arrangements +with the authors of those software packages. CD manufacturers can also +distribute the non-free software they get from other sources on the same CD. +This is nothing new: free and commercial software are distributed on the same +CD by many manufacturers now. Of course we still encourage software authors to +release the programs they write as free software. +</p> + +<hr> + +<h2><a name="s-childistro"></a>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?</h2> + +<p> +Yes. Debian-derived distributions are being created both in close cooperation +with the Debian project itself and by external parties. One can use the +<code><a href="http://cdd.alioth.debian.org/">Custom Debian +Distributions</a></code> framework to work together with Debian; <code><a +href="http://www.skolelinux.org/">Skolelinux</a></code> is one such project. +</p> + +<p> +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. +</p> + +<p> +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 <a href="ch-customizing.en.html#s-divert">How do I override a file +installed by a package, so that a different version can be used instead?, +Section 11.8</a>. +</p> + +<hr> + +<h2><a name="s-commercialdebs"></a>14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?</h2> + +<p> +Go right ahead. The package tool is free software; the packages may or may not +be free software, it can install them all. +</p> + +<hr> + +<p> +[ <a href="ch-contributing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ 14 ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-nexttime.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..f182623 --- /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 0000000..2c2d745 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-software.en.html @@ -0,0 +1,639 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Software available in the Debian system</title> + +<link href="index.en.html" rel="start"> +<link href="ch-compat.en.html" rel="prev"> +<link href="ch-ftparchives.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-software"></a></p> +<hr> + +<p> +[ <a href="ch-compat.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ 5 ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-ftparchives.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 5 - Software available in the Debian system +</h1> + +<hr> + +<h2><a name="s-apps"></a>5.1 What types of applications and development software are available for Debian GNU/Linux?</h2> + +<p> +Like most Linux distributions, Debian GNU/Linux provides: +</p> +<ul> +<li> +<p> +the major GNU applications for software development, file manipulation, and +text processing, including gcc, g++, make, texinfo, Emacs, the Bash shell and +numerous upgraded Unix utilities, +</p> +</li> +</ul> +<ul> +<li> +<p> +Perl, Python, Tcl/Tk and various related programs, modules and libraries for +each of them, +</p> +</li> +</ul> +<ul> +<li> +<p> +TeX (LaTeX) and Lyx, dvips, Ghostscript, +</p> +</li> +</ul> +<ul> +<li> +<p> +the Xorg windowing system, which provides a networked graphical user interface +for Linux, and countless X applications including the GNOME, KDE and Xfce +desktop environments. +</p> +</li> +</ul> +<ul> +<li> +<p> +a full suite of networking applications, including servers for Internet +protocols such as HTTP (WWW), FTP, NNTP (news), SMTP and POP (mail) and DNS +(name servers); relational databases like PostgreSQL, MySQL; also provided are +web browsers including the various Mozilla products [<a +href="footnotes.en.html#f1" name="fr1">1</a>], +</p> +</li> +</ul> +<ul> +<li> +<p> +a complete set of office applications, including the OpenOffice.org +productivity suite, Gnumeric and other spreadsheets, WYSIWYG editors, +calendars. +</p> +</li> +</ul> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-softwareauthors"></a>5.2 Who wrote all that software?</h2> + +<p> +For each package the <em>authors</em> of the program(s) are credited in the +file <samp>/usr/share/doc/PACKAGE/copyright</samp>, where PACKAGE is to be +substituted with the package's name. +</p> + +<p> +<em>Maintainers</em> who package this software for the Debian GNU/Linux system +are listed in the Debian control file (see <a +href="ch-pkg_basics.en.html#s-controlfile">What is a Debian control file?, +Section 7.4</a>) that comes with each package. The Debian changelog, in +<samp>/usr/share/doc/PACKAGE/changelog.Debian.gz</samp>, mentions the people +who've worked on the Debian packaging too. +</p> + +<hr> + +<h2><a name="s-pkglist"></a>5.3 How can I get a current list of programs that have been packaged for Debian?</h2> + +<p> +A complete list is available from any of the <code><a +href="http://www.debian.org/distrib/ftplist">Debian mirrors</a></code>, in the +file <samp>indices/Maintainers</samp>. That file includes the package names +and the names and e-mails of their respective maintainers. +</p> + +<p> +The <code><a href="http://packages.debian.org/">WWW interface to the Debian +packages</a></code> conveniently summarizes the packages in each of about +thirty "sections" of the Debian archive. +</p> + +<hr> + +<h2><a name="s-buildenv"></a>5.4 How can I install a developer's environment to build packages?</h2> + +<p> +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 <code>build-essential</code>. This package is a meta-package or +place-holder package which depends on the standard development tools one needs +to build a Debian package. +</p> + +<p> +Some software can, however, need additional software to be rebuilt, including +library headers or additional tools such as <code>autoconf</code> or +<code>gettext</code>. Debian provides many of the tools needed to build other +software as Debian packages. +</p> + +<p> +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 <code>build-essential</code>) needed to build the +pacakge, this is known as <samp>Build-Dependencies</samp>. To install all the +packages needed to build a given source package and then build said source +package you can just run: +</p> + +<pre> + # apt-get build-dep <var>foo</var> + # apt-get source --build <var>foo</var> +</pre> + +<p> +Notice that if you want to build the Linux kernels distributed by Debian you +will want to install also the <code>kernel-package</code> package. For more +information see <a href="ch-kernel.en.html#s-customkernel">What tools does +Debian provide to build custom kernels?, Section 10.2</a>. +</p> + +<hr> + +<h2><a name="s-missing"></a>5.5 What is missing from Debian GNU/Linux?</h2> + +<p> +A list of packages which are still needed to be packaged for Debian exists, the +<code><a href="http://www.debian.org/devel/wnpp/">Work-Needing and Prospective +Packages list</a></code>. +</p> + +<p> +For more details about adding the missing things, see <a +href="ch-contributing.en.html#s-contrib">How can I become a Debian software +developer?, Section 13.1</a>. +</p> + +<hr> + +<h2><a name="s-no-devs"></a>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?</h2> + +<p> +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). +</p> + +<hr> + +<h2><a name="s-java"></a>5.7 (How) Does Debian support Java?</h2> + +<p> +Several <em>free</em> implementations of Java technology are available as +Debian packages, providing both Java Development Kits as well as Runtime +Environments. You can write, debug and run Java programs using Debian. +</p> + +<p> +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. +</p> + +<p> +Please refer to the <code><a +href="http://www.debian.org/doc/manuals/debian-java-faq/">Debian Java +FAQ</a></code> for more information. +</p> + +<hr> + +<h2><a name="s-isitdebian"></a>5.8 How can I check that I am using a Debian system, and what version is it?</h2> + +<p> +In order to make sure that your system has been installed from the real Debian +base disks check for the existence of <samp>/etc/debian_version</samp> file, +which contains a single one-line entry giving the version number of the +release, as defined by the package <samp>base-files</samp>. +</p> + +<p> +The existence of the program <samp>dpkg</samp> 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. +</p> + +<p> +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 <samp>foo</samp>, use the command <samp>dpkg --list foo</samp>. To +view versions of all installed packages, run: +</p> + +<pre> + dpkg -l +</pre> + +<p> +For a more verbose description, use: +</p> + +<pre> + dpkg --status foo +</pre> + +<hr> + +<h2><a name="s-nonenglish"></a>5.9 How does Debian support non-English languages?</h2> +<ul> +<li> +<p> +Debian GNU/Linux is distributed with keymaps for nearly two dozen keyboards, +and with utilities (in the <samp>kbd</samp> package) to install, view, and +modify the tables. +</p> + +<p> +The installation prompts the user to specify the keyboard he will use. +</p> +</li> +</ul> +<ul> +<li> +<p> +Vast majority of the software we packaged supports entering non-US-ASCII +characters used in other Latin languages (e.g. ISO-8859-1 or ISO-8859-2), and +a number of programs support multi-byte languages such as Japanese or Chinese. +</p> +</li> +</ul> +<ul> +<li> +<p> +Currently, support for German-, Spanish-, Finnish-, French-, Hungarian-, +Italian-, Japanese-, Korean-, Dutch-, Polish-, Portuguese-, Russian-, Turkish-, +and Chinese-language manual pages is provided through the +<samp>manpages-LANG</samp> packages (where LANG is the two-letter ISO country +code). To access an NLS manual page, the user must set the shell LC_MESSAGES +variable to the appropriate string. +</p> + +<p> +For example, in the case of the Italian-language manual pages, LC_MESSAGES +needs to be set to 'italian'. The <code>man</code> program will then search +for Italian manual pages under <samp>/usr/share/man/it/</samp>. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-pine"></a>5.10 Where is pine?</h2> + +<p> +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. +</p> + +<p> +The source package name is <code>pine</code>. You can use the +<code>pine-tracker</code> package to be notified about when you need to +upgrade. +</p> + +<p> +Note that there are many replacements for both pine and pico, such as +<code>mutt</code> and <code>nano</code>, that are located in the main section. +</p> + +<hr> + +<h2><a name="s-qmail"></a>5.11 Where is qmail/ezmlm/djbdns?</h2> + +<p> +Dan J. Bernstein used to distribute <code><a +href="http://cr.yp.to/software.html">all software he has written</a></code> +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 <code><a href="http://cr.yp.to/distributors.html">FAQ from +distributors</a></code> for his distribution terms. +</p> + +<p> +As of 2008-04, <code>daemontools</code>, <code>djbdns</code> and +<code>ucspi-tcp</code> are shipped with Debian lenny (in main). As of this +writing (2008-04), <code>qmail</code> is not yet packaged for Debian main; see +<code><a href="http://bugs.debian.org/457318">Bug #457318 (ITP +qmail)</a></code> for the current status. +</p> + +<p> +As of 2008-04, <samp>publicfile</samp> and <samp>ezmlm</samp> were still not +free software. For <samp>ezmlm</samp>, there's the <code>ezmlm-src</code> +package in the non-free area. +</p> + +<hr> + +<h2><a name="s-flash"></a>5.12 Where is a player for Flash (SWF)?</h2> + +<p> +Debian ships both <code>gnash</code> and <code>swfdec</code>: two free SWF +movie players. +</p> + +<hr> + +<h2><a name="s-googleearth"></a>5.13 Where is Google Earth?</h2> + +<p> +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, <code>googleearth-package</code> (in the contrib-section) might be +helpful in using this software. +</p> + +<hr> + +<h2><a name="s-voip"></a>5.14 Where is VoIP software?</h2> + +<p> +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. <code>ekiga</code> +is one of the popular clients. +</p> + +<hr> + +<h2><a name="s-nonfreewireless"></a>5.15 I have a wireless network card which doesn't work with Linux. What should I do?</h2> + +<p> +Buy one which does :) +</p> + +<p> +Alternatively, use <code>ndiswrapper</code> to use a driver for Windows (if you +have one) on your Linux system. See the <code><a +href="http://wiki.debian.org/NdisWrapper">Debian Wiki ndiswapper +page</a></code> for more information. +</p> + +<hr> + +<p> +[ <a href="ch-compat.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ 5 ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-ftparchives.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..f75c0ab --- /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 0000000..5036cb5 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-support.en.html @@ -0,0 +1,679 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Getting support for Debian GNU/Linux</title> + +<link href="index.en.html" rel="start"> +<link href="ch-customizing.en.html" rel="prev"> +<link href="ch-contributing.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-support"></a></p> +<hr> + +<p> +[ <a href="ch-customizing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ 12 ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-contributing.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 12 - Getting support for Debian GNU/Linux +</h1> + +<hr> + +<h2><a name="s-debiandocs"></a>12.1 What other documentation exists on and for a Debian system?</h2> +<ul> +<li> +<p> +Installation instructions for the current release: see <code><a +href="http://www.debian.org/releases/stable/installmanual">http://www.debian.org/releases/stable/installmanual</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +The Debian GNU/Linux reference covers many aspects of system administration +through shell-command examples. Basic tutorials, tips, and other information +are provided for many different topics ranging from system administration to +programming. +</p> + +<p> +Get it from the <code>debian-reference</code> package, or at <code><a +href="http://www.debian.org/doc/user-manuals#quick-reference">http://www.debian.org/doc/user-manuals#quick-reference</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +The Debian Policy manual documents the policy requirements for the +distribution, i.e. the structure and contents of the Debian archive, several +design issues of the operating system etc. It also includes the technical +requirements that each package must satisfy to be included in the distribution, +and documents the basic technical aspects of Debian binary and source packages. +</p> + +<p> +Get it from the <code>debian-policy</code> package, or at <code><a +href="http://www.debian.org/doc/devel-manuals#policy">http://www.debian.org/doc/devel-manuals#policy</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Documentation developed by the Debian Documentation Project. It is available +at <code><a +href="http://www.debian.org/doc/">http://www.debian.org/doc/</a></code> and +includes user guides, administration guides and security guides for the Debian +GNU/Linux operating system. +</p> +</li> +</ul> +<ul> +<li> +<p> +Documentation on installed Debian packages: Most packages have files that are +unpacked into <samp>/usr/share/doc/PACKAGE</samp>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Documentation on the Linux project: The Debian package <code>doc-linux</code> +installs all of the most recent versions of the HOWTOs and mini-HOWTOs from the +<code><a href="http://www.tldp.org/">Linux Documentation Project</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Unix-style `man' pages: Most commands have manual pages written in the style of +the original Unix 'man' files. For instance, to see the manual page for the +command `ls', execute <samp>man ls</samp>. Execute <samp>man man</samp> for +more information on finding and viewing manual pages. +</p> + +<p> +New Debian users should note that the 'man' pages of many general system +commands are not available until they install these packages: +</p> +<ul> +<li> +<p> +<samp>man-db</samp>, which contains the <samp>man</samp> program itself, and +other programs for manipulating the manual pages. +</p> +</li> +</ul> +<ul> +<li> +<p> +<samp>manpages</samp>, which contains the system manual pages. (see <a +href="ch-software.en.html#s-nonenglish">How does Debian support non-English +languages?, Section 5.9</a>). +</p> +</li> +</ul> +</li> +</ul> +<ul> +<li> +<p> +GNU-style `info' pages: User documentation for many commands, particularly GNU +tools, is available not in `man' pages, but in `info' files which can be read +by the GNU tool <samp>info</samp>, by running <samp>M-x info</samp> within GNU +Emacs, or with some other Info page viewer. +</p> + +<p> +Its main advantage over the original `man' pages are that it is a hypertext +system. It does <em>not</em> require the WWW, however; <samp>info</samp> can +be run from a plain text console. It was designed by Richard Stallman and +preceded the WWW. +</p> +</li> +</ul> + +<p> +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'. +</p> + +<hr> + +<h2><a name="s-onlineresources"></a>12.2 Are there any on-line resources for discussing Debian?</h2> + +<p> +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 <code><a +href="http://www.debian.org/support">Debian Support webpage</a></code>. +</p> + +<hr> + +<h3><a name="s12.2.1"></a>12.2.1 Mailing lists</h3> + +<p> +There are a lot of <code><a +href="http://www.debian.org/MailingLists/">Debian-related mailing +lists</a></code>. +</p> + +<p> +On a system with the <code>doc-debian</code> package installed there is a +complete list of mailing lists in +<code>/usr/share/doc/debian/mailing-lists.txt</code>. +</p> + +<p> +Debian mailing lists are named following the pattern +debian-<var>list-subject</var>. Examples are debian-announce, debian-user, +debian-news. To subscribe to any list debian-<var>list-subject</var>, send +mail to debian-<var>list-subject</var>-request@lists.debian.org with the word +"subscribe" in the Subject: header. Be sure to remember to add +<em>-request</em> to the e-mail address when using this method to subscribe or +unsubscribe. Otherwise your e-mail will go to the list itself, which could be +embarrassing or annoying, depending on your point of view. +</p> + +<p> +You can subscribe to mailing lists using the <code><a +href="http://www.debian.org/MailingLists/subscribe">WWW form</a></code>. You +can also un-subscribe using a <code><a +href="http://www.debian.org/MailingLists/unsubscribe">WWW form</a></code>. +</p> + +<p> +The list manager's e-mail address is <code><a +href="mailto:listmaster@lists.debian.org">listmaster@lists.debian.org</a></code>, +in case you have any trouble. +</p> + +<p> +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 <code><a +href="http://www.debian.org/MailingLists/index.en.html#disclaimer">Mailing +Lists Privacy policy</a></code> for more information. +</p> + +<p> +Archives of the Debian mailing lists are available via WWW at <code><a +href="http://lists.debian.org/">http://lists.debian.org/</a></code>. +</p> + +<hr> + +<h4><a name="s-mailinglistconduct"></a>12.2.1.1 What is the code of conduct for the mailing lists?</h4> + +<p> +When using the Debian mailing lists, please follow these rules: +</p> +<ul> +<li> +<p> +Do not send spam. See the <code><a +href="http://www.debian.org/MailingLists/#ads">Debian mailing list advertising +policy</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +Do not flame; it is not polite. The people developing Debian are all +volunteers, donating their time, energy and money in an attempt to bring the +Debian project together. +</p> +</li> +</ul> +<ul> +<li> +<p> +Do not use foul language; besides, some people receive the lists via packet +radio, where swearing is illegal. +</p> +</li> +</ul> +<ul> +<li> +<p> +Make sure that you are using the proper list. <em>Never</em> post your +(un)subscription requests to the mailing list itself[<a +href="footnotes.en.html#f7" name="fr7">7</a>] +</p> +</li> +</ul> +<ul> +<li> +<p> +See section <a href="#s-bugreport">How do I report a bug in Debian?, Section +12.5</a> for notes on reporting bugs. +</p> +</li> +</ul> + +<hr> + +<h3><a name="s12.2.2"></a>12.2.2 Web forums</h3> + +<p> +<code><a href="http://debianhelp.org/">debianHELP</a></code> and <code><a +href="http://forums.debian.net/">Debian User Forums</a></code> 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.) +</p> + +<hr> + +<h3><a name="s12.2.3"></a>12.2.3 Wiki</h3> + +<p> +Solutions to common problems, howto's, guides, tips and other documentation can +be found at the constantly changing <code><a +href="http://wiki.debian.org/">Debian Wiki</a></code>. +</p> + +<hr> + +<h3><a name="s12.2.4"></a>12.2.4 Maintainers</h3> + +<p> +Users can address questions to individual package maintainers using e-mail. To +reach a maintainer of a package called xyz, send e-mail to +<em>xyz@packages.debian.org</em>. +</p> + +<hr> + +<h3><a name="s12.2.5"></a>12.2.5 Usenet newsgroups</h3> + +<p> +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 +<code><a href="http://www.linux.org/docs/usenet.html">Linux Online</a></code> +and <code><a +href="http://www.linuxjournal.com/helpdesk.php">LinuxJournal</a></code> sites. +</p> + +<hr> + +<h2><a name="s-searchtools"></a>12.3 Is there a quick way to search for information on Debian GNU/Linux?</h2> + +<p> +There is a variety of search engines that serve documentation related to +Debian: +</p> +<ul> +<li> +<p> +<code><a href="http://search.debian.org/">Debian WWW search site</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +<code><a href="http://groups.google.com/">Google Groups</a></code>: a search +engine for newsgroups. +</p> + +<p> +For example, to find out what experiences people have had with finding drivers +for Promise controllers under Debian, try searching on the phrase <samp>Promise +Linux driver</samp>. This will show you all the postings that contain these +strings, i.e. those where people discussed these topics. If you add +<samp>Debian</samp> to those search strings, you'll also get the postings +specifically related to Debian. +</p> +</li> +</ul> +<ul> +<li> +<p> +Any of the common web spidering engines, such as <code><a +href="http://www.altavista.com/">AltaVista</a></code> or <code><a +href="http://www.google.com/">Google</a></code>, as long as you use the right +search terms. +</p> + +<p> +For example, searching on the string "cgi-perl" gives a more detailed +explanation of this package than the brief description field in its control +file. +</p> +</li> +</ul> + +<hr> + +<h2><a name="s-buglogs"></a>12.4 Are there logs of known bugs?</h2> + +<p> +Reports on unsolved (and closed) issues are publicly available: Debian +promissed to do so by stating "We will not hide problems" in the +<code><a href="http://www.debian.org/social_contract">Debian Social +Contract</a></code>. +</p> + +<p> +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. +</p> + +<p> +Copies of this information are available at <code><a +href="http://www.debian.org/Bugs/">http://www.debian.org/Bugs/</a></code>. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-bugreport"></a>12.5 How do I report a bug in Debian?</h2> + +<p> +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: +</p> +<ul> +<li> +<p> +From the WWW. A copy of the instructions is shown at <code><a +href="http://www.debian.org/Bugs/Reporting">http://www.debian.org/Bugs/Reporting</a></code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +On any Debian system with the <code>doc-debian</code> package installed. The +instructions are in the file +<code>/usr/share/doc/debian/bug-reporting.txt</code>. +</p> +</li> +</ul> +<ul> +<li> +<p> +By anonymous FTP. Debian mirror sites contain the instructions in the file +<samp>doc/bug-reporting.txt</samp>. +</p> +</li> +</ul> + +<p> +You can use the package <code>reportbug</code> 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. +</p> + +<p> +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. +</p> + +<hr> + +<p> +[ <a href="ch-customizing.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ 12 ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-contributing.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..978d556 --- /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 0000000..33cc9f0 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/ch-uptodate.en.html @@ -0,0 +1,636 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Keeping your Debian system up-to-date</title> + +<link href="index.en.html" rel="start"> +<link href="ch-pkgtools.en.html" rel="prev"> +<link href="ch-kernel.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="ch-uptodate"></a></p> +<hr> + +<p> +[ <a href="ch-pkgtools.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ 9 ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-kernel.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Chapter 9 - Keeping your Debian system up-to-date +</h1> + +<hr> + +<p> +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. +</p> + +<p> +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 +<code><a +href="http://www.debian.org/releases/stable/releasenotes">http://www.debian.org/releases/stable/releasenotes</a></code>. +</p> + +<hr> + +<h2><a name="s-howtocurrent"></a>9.1 How can I keep my Debian system current?</h2> + +<p> +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 <samp>dpkg</samp>. Note that <samp>dpkg</samp> 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. +</p> + +<p> +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: +</p> + +<hr> + +<h3><a name="s-aptitude-upgrade"></a>9.1.1 aptitude</h3> + +<p> +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 +<samp>/usr/share/doc/apt-doc/guide.html/index.html</samp> (you will have to +install the <samp>apt-doc</samp> package). +</p> + +<p> +<code>aptitude</code> 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. +</p> + +<p> +Before you can use <code>aptitude</code>, you'll have to edit the +<samp>/etc/apt/sources.list</samp> 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: +</p> + +<pre> + http://ftp.us.debian.org/debian stable main contrib non-free +</pre> + +<p> +You can replace ftp.us.debian.org with the name of a faster Debian mirror near +you. See the mirror list at <code><a +href="http://www.debian.org/mirror/list">http://www.debian.org/mirror/list</a></code> +for more information. +</p> + +<p> +More details on this can be found in the <code>sources.list(8)</code> manual +page. +</p> + +<p> +To update your system, run +</p> + +<pre> + aptitude update +</pre> + +<p> +followed by +</p> + +<pre> + aptitude dist-upgrade +</pre> + +<p> +Answer any questions that might come up, and your system will be upgraded. See +also <a href="ch-pkgtools.en.html#s-aptitude">aptitude, Section 8.1.3</a>. +</p> + +<hr> + +<h3><a name="s-apt"></a>9.1.2 apt-get, dselect and apt-cdrom</h3> + +<p> +<code>apt-get</code> is an APT-based command-line tool for handling packages, +and the APT dselect method is an interface to APT through <code>dselect</code>. +Both of these provide a simple, safe way to install and upgrade packages. +</p> + +<p> +To use <code>apt-get</code>, install the <code>apt</code> package, and edit the +<samp>/etc/apt/sources.list</samp> file to set it up, just as for <a +href="#s-aptitude-upgrade">aptitude, Section 9.1.1</a>. +</p> + +<p> +Then run +</p> + +<pre> + apt-get update +</pre> + +<p> +followed by +</p> + +<pre> + apt-get dist-upgrade +</pre> + +<p> +Answer any questions that might come up, and your system will be upgraded. See +also the <code>apt-get(8)</code> manual page, as well as <a +href="ch-pkgtools.en.html#s-apt-get">APT, Section 8.1.2</a>. +</p> + +<p> +To use APT with <code>dselect</code>, 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 <code>/etc/apt/sources.list</code>. See also +<a href="ch-pkgtools.en.html#s-dselect">dselect, Section 8.1.6.1</a>. +</p> + +<p> +If you want to use CDs to install packages, you can use <code>apt-cdrom</code>. +For details, please see the Release Notes, section "Setting up for an +upgrade from a local mirror". +</p> + +<p> +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 <samp>apt-get clean</samp> +and <samp>apt-get autoclean</samp>, or to move them someplace else (hint: use +<code>apt-move</code>). +</p> + +<hr> + +<h3><a name="s-update_aptitude"></a>9.1.3 aptitude</h3> + +<p> +<code>aptitude</code> 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 <a +href="ch-pkgtools.en.html#s-aptitude">aptitude, Section 8.1.3</a>). Actions +may be performed from a visual interface or from the command-line. +</p> + +<p> +In command line, the actions are similar to that of APT, so to upgrade your +system run +</p> + +<pre> + aptitude update +</pre> + +<p> +followed by +</p> + +<pre> + aptitude dist-upgrade +</pre> + +<p> +To upgrade from a preview release, <code>aptitude</code> is the tool +recommended. Read the Release Notes at <code><a +href="http://www.debian.org/releases/stable/releasenotes">http://www.debian.org/releases/stable/releasenotes</a></code>. +</p> + +<p> +For details, see the manual page <code>aptitude(8)</code>, and the file +<code>/usr/share/aptitude/README</code> +</p> + +<hr> + +<h3><a name="s-mirror"></a>9.1.4 mirror</h3> + +<p> +This Perl script, and its (optional) manager program called +<code>mirror-master</code>, can be used to fetch user-specified parts of a +directory tree from a specified host <em>via</em> anonymous FTP. +</p> + +<p> +<code>mirror</code> is particularly useful for downloading large volumes of +software. After the first time files have been downloaded from a site, a file +called <samp>.mirrorinfo</samp> is stored on the local host. Changes to the +remote file system are tracked automatically by <code>mirror</code>, which +compares this file to a similar file on the remote system and downloads only +changed files. +</p> + +<p> +The <code>mirror</code> program is generally useful for updating local copies +of remote directory trees. The files fetched need not be Debian files. (Since +<code>mirror</code> is a Perl script, it can also run on non-Unix systems.) +Though the <code>mirror</code> 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. +</p> + +<hr> + +<h3><a name="s-dpkg-mountable"></a>9.1.5 dpkg-mountable</h3> + +<p> +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. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="s-upgradesingle"></a>9.2 Must I go into single user mode in order to upgrade a package?</h2> + +<p> +No. Packages can be upgraded in place, even in running systems. Debian has a +<samp>start-stop-daemon</samp> program that is invoked to stop, then restart +running process if necessary during a package upgrade. +</p> + +<hr> + +<h2><a name="s-savedebs"></a>9.3 Do I have to keep all those .deb archive files on my disk?</h2> + +<p> +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 +<samp>aptitude clean</samp>. +</p> + +<hr> + +<h2><a name="s-keepingalog"></a>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!</h2> + +<p> +Passing the <samp>--log</samp>-option to <code>dpkg</code> makes +<code>dpkg</code> log status change updates and actions. It logs both the +<code>dpkg</code>-invokation (e.g. +</p> + +<pre> + 2005-12-30 18:10:33 install hello 1.3.18 2.1.1-4 +</pre> + +<p> +) and the results (e.g. +</p> + +<pre> + 2005-12-30 18:10:35 status installed hello 2.1.1-4 +</pre> + +<p> +) If you'd like to log all your <code>dpkg</code> invokations (even those done +using frontends like <code>aptitude</code>), you could add +</p> + +<pre> + log /var/log/dpkg.log +</pre> + +<p> +to your <code>/etc/dpkg/dpkg.cfg</code>. Be sure the created logfile gets +rotated periodically. If you're using <code>logrotate</code>, this can be +achieved by creating a file <code>/etc/logrotate.d/dpkg</code> with contents +</p> + +<pre> + /var/log/dpkg { + missingok + notifempty + } +</pre> + +<p> +More details on <code>dpkg</code> logging can be found in the +<code>dpkg(1)</code> manual page. +</p> + +<p> +<code>aptitude</code> logs the package installations, removals, and upgrades +that it intends to perform to <code>/var/log/aptitude</code>. Note that the +<em>results</em> of those actions are not recorded in this file! +</p> + +<p> +Another way to record your actions is to run your package management session +within the <code>script(1)</code> program. +</p> + +<hr> + +<h2><a name="s-autoupdate"></a>9.5 Can I automatically update the system?</h2> + +<p> +Yes. You can use <code>cron-apt</code>, 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. +</p> + +<p> +Note: Automatic upgrade of packages is <strong>NOT</strong> recommended in +<em>testing</em> or <em>unstable</em> systems as this might bring unexpected +behaviour and remove packages without notice. +</p> + +<hr> + +<h2><a name="s-aptproxy"></a>9.6 I have several machines how can I download the updates only one time?</h2> + +<p> +If you have more than one Debian machine on your network, it is useful to use +<code>apt-proxy</code> to keep all of your Debian systems up-to-date. +</p> + +<p> +<code>apt-proxy</code> 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. <code>apt-proxy</code> automatically builds +a Debian HTTP mirror based on requests which pass through the proxy. +</p> + +<p> +For more details, see the apt-proxy homepage at <code><a +href="http://apt-proxy.sourceforge.net/">http://apt-proxy.sourceforge.net/</a></code> +</p> + +<p> +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. +</p> + +<hr> + +<p> +[ <a href="ch-pkgtools.en.html">previous</a> ] +[ <a href="index.en.html#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ 9 ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-kernel.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..37f6852 --- /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 0000000..881269f --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/footnotes.en.html @@ -0,0 +1,294 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ - Footnotes</title> + +<link href="index.en.html" rel="start"> +<link href=".en.html" rel="prev"> +<link href=".en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br>Footnotes</h1> + +<h2><a href="ch-software.en.html#fr1" name="f1">1</a></h2> + +<p> +These have been, however, rebranded and are provided with different names due +to trademark issues +</p> + +<h2><a href="ch-ftparchives.en.html#fr2" name="f2">2</a></h2> + +<p> +When the present-day sid did not exist, the FTP site organization had one major +flaw: there was an assumption that when an architecture is created in the +current unstable, it will be released when that distribution becomes the new +stable. For many architectures that isn't the case, with the result that those +directories had to be moved at release time. This was impractical because the +move would chew up lots of bandwidth. +</p> + +<p> +The archive administrators worked around this problem for several years by +placing binaries for unreleased architectures in a special directory called +"sid". For those architectures not yet released, the first time they +were released there was a link from the current stable to sid, and from then on +they were created inside the unstable tree as normal. This layout was somewhat +confusing to users. +</p> + +<p> +With the advent of package pools (see <a href="#s-pools">What's in the +<samp>pool</samp> directory?, Section 6.10</a>), binary packages began to be +stored in a canonical location in the pool, regardless of the distribution, so +releasing a distribution no longer causes large bandwidth consumption on the +mirrors (there is, however, a lot of gradual bandwidth consumption throughout +the development process). +</p> + +<h2><a href="ch-ftparchives.en.html#fr3" name="f3">3</a></h2> + +<p> +<samp>dists/stable/main</samp>, <samp>dists/stable/contrib</samp>, +<samp>dists/stable/non-free</samp>, and <samp>dists/unstable/main/</samp>, etc. +</p> + +<h2><a href="ch-ftparchives.en.html#fr4" name="f4">4</a></h2> + +<p> +Historically, packages were kept in the subdirectory of <samp>dists</samp> +corresponding to which distribution contained them. This turned out to cause +various problems, such as large bandwidth consumption on mirrors when major +changes were made. This was fixed with the introduction of the package pool. +</p> + +<p> +The <samp>dists</samp> directories are still used for the index files used by +programs like <samp>apt</samp>. +</p> + +<h2><a href="ch-pkgtools.en.html#fr5" name="f5">5</a></h2> + +<p> +Notice that there are ports that make this tool available with other package +management systems, like Red Hat package manager, also known as +<code>rpm</code> +</p> + +<h2><a href="ch-pkgtools.en.html#fr6" name="f6">6</a></h2> + +<p> +Although this can also lead to systems with more packages installed than they +actually need to work. +</p> + +<h2><a href="ch-support.en.html#fr7" name="f7">7</a></h2> + +<p> +Use the debian-<var>list-subject</var>-REQUEST@lists.debian.org address for +that. +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..c18fdfb --- /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 0000000..c7115e0 --- /dev/null +++ b/includes/lenny/common/doc/FAQ/html/index.en.html @@ -0,0 +1,522 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> + +<html> + +<head> + +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> + +<title>The Debian GNU/Linux FAQ</title> + +<link href="index.en.html" rel="start"> +<link href="ch-faqinfo.en.html" rel="prev"> +<link href="ch-basic_defs.en.html" rel="next"> +<link href="index.en.html#contents" rel="contents"> +<link href="index.en.html#copyright" rel="copyright"> +<link href="ch-basic_defs.en.html" rel="chapter" title="1 Definitions and overview"> +<link href="ch-getting.en.html" rel="chapter" title="2 Getting and installing Debian GNU/Linux"> +<link href="ch-choosing.en.html" rel="chapter" title="3 Choosing a Debian distribution"> +<link href="ch-compat.en.html" rel="chapter" title="4 Compatibility issues"> +<link href="ch-software.en.html" rel="chapter" title="5 Software available in the Debian system"> +<link href="ch-ftparchives.en.html" rel="chapter" title="6 The Debian FTP archives"> +<link href="ch-pkg_basics.en.html" rel="chapter" title="7 Basics of the Debian package management system"> +<link href="ch-pkgtools.en.html" rel="chapter" title="8 The Debian package management tools"> +<link href="ch-uptodate.en.html" rel="chapter" title="9 Keeping your Debian system up-to-date"> +<link href="ch-kernel.en.html" rel="chapter" title="10 Debian and the kernel"> +<link href="ch-customizing.en.html" rel="chapter" title="11 Customizing your installation of Debian GNU/Linux"> +<link href="ch-support.en.html" rel="chapter" title="12 Getting support for Debian GNU/Linux"> +<link href="ch-contributing.en.html" rel="chapter" title="13 Contributing to the Debian Project"> +<link href="ch-redistrib.en.html" rel="chapter" title="14 Redistributing Debian GNU/Linux in a commercial product"> +<link href="ch-nexttime.en.html" rel="chapter" title="15 Changes expected in the next major release of Debian"> +<link href="ch-faqinfo.en.html" rel="chapter" title="16 General information about the FAQ"> +<link href="ch-basic_defs.en.html#s-whatisfaq" rel="section" title="1.1 What is this FAQ?"> +<link href="ch-basic_defs.en.html#s-whatisdebian" rel="section" title="1.2 What is Debian GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-linux" rel="section" title="1.3 OK, now I know what Debian is... what is Linux?!"> +<link href="ch-basic_defs.en.html#s-non-linux" rel="section" title="1.4 Does Debian just do GNU/Linux?"> +<link href="ch-basic_defs.en.html#s-difference" rel="section" title="1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?"> +<link href="ch-basic_defs.en.html#s-gnu" rel="section" title="1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?"> +<link href="ch-basic_defs.en.html#s-pronunciation" rel="section" title="1.7 How does one pronounce Debian and what does this word mean?"> +<link href="ch-getting.en.html#s-version" rel="section" title="2.1 What is the latest version of Debian?"> +<link href="ch-getting.en.html#s-updatestable" rel="section" title="2.2 Are there package upgrades in `stable'?"> +<link href="ch-getting.en.html#s-boot-floppies" rel="section" title="2.3 Where/how can I get the Debian installation disks?"> +<link href="ch-getting.en.html#s-cdrom" rel="section" title="2.4 How do I install the Debian from CD-ROMs?"> +<link href="ch-getting.en.html#s-cdimage-symlinks" rel="section" title="2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!"> +<link href="ch-getting.en.html#s-remoteinstall" rel="section" title="2.6 Can I get and install Debian directly from a remote Internet site?"> +<link href="ch-getting.en.html#s-alternativebootinstaller" rel="section" title="2.7 Are there any alternative strategies for booting the system installer?"> +<link href="ch-choosing.en.html#s3.1" rel="section" title="3.1 Which Debian distribution (stable/testing/unstable) is better for me?"> +<link href="ch-choosing.en.html#s3.2" rel="section" title="3.2 But what about Knoppix, Linex, Ubuntu, and others?"> +<link href="ch-compat.en.html#s-arches" rel="section" title="4.1 On what hardware architectures/systems does Debian GNU/Linux run?"> +<link href="ch-compat.en.html#s-otherdistribs" rel="section" title="4.2 How compatible is Debian with other distributions of Linux?"> +<link href="ch-compat.en.html#s-otherunices" rel="section" title="4.3 How source code compatible is Debian with other Unix systems?"> +<link href="ch-compat.en.html#s-otherpackages" rel="section" title="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?"> +<link href="ch-compat.en.html#s-non-debian-programs" rel="section" title="4.5 How should I install a non-Debian program?"> +<link href="ch-compat.en.html#s-termcap" rel="section" title="4.6 Why can't I compile programs that require libtermcap?"> +<link href="ch-compat.en.html#s-accelx" rel="section" title="4.7 Why can't I install AccelX?"> +<link href="ch-compat.en.html#s-motifnls" rel="section" title="4.8 Why do my old XFree 2.1 Motif applications crash?"> +<link href="ch-software.en.html#s-apps" rel="section" title="5.1 What types of applications and development software are available for Debian GNU/Linux?"> +<link href="ch-software.en.html#s-softwareauthors" rel="section" title="5.2 Who wrote all that software?"> +<link href="ch-software.en.html#s-pkglist" rel="section" title="5.3 How can I get a current list of programs that have been packaged for Debian?"> +<link href="ch-software.en.html#s-buildenv" rel="section" title="5.4 How can I install a developer's environment to build packages?"> +<link href="ch-software.en.html#s-missing" rel="section" title="5.5 What is missing from Debian GNU/Linux?"> +<link href="ch-software.en.html#s-no-devs" rel="section" title="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?"> +<link href="ch-software.en.html#s-java" rel="section" title="5.7 (How) Does Debian support Java?"> +<link href="ch-software.en.html#s-isitdebian" rel="section" title="5.8 How can I check that I am using a Debian system, and what version is it?"> +<link href="ch-software.en.html#s-nonenglish" rel="section" title="5.9 How does Debian support non-English languages?"> +<link href="ch-software.en.html#s-pine" rel="section" title="5.10 Where is pine?"> +<link href="ch-software.en.html#s-qmail" rel="section" title="5.11 Where is qmail/ezmlm/djbdns?"> +<link href="ch-software.en.html#s-flash" rel="section" title="5.12 Where is a player for Flash (SWF)?"> +<link href="ch-software.en.html#s-googleearth" rel="section" title="5.13 Where is Google Earth?"> +<link href="ch-software.en.html#s-voip" rel="section" title="5.14 Where is VoIP software?"> +<link href="ch-software.en.html#s-nonfreewireless" rel="section" title="5.15 I have a wireless network card which doesn't work with Linux. What should I do?"> +<link href="ch-ftparchives.en.html#s-dists" rel="section" title="6.1 How many Debian distributions are there?"> +<link href="ch-ftparchives.en.html#s-codenames" rel="section" title="6.2 What are all those names like etch, lenny, etc.?"> +<link href="ch-ftparchives.en.html#s-sid" rel="section" title="6.3 What about "sid"?"> +<link href="ch-ftparchives.en.html#s-stable" rel="section" title="6.4 What does the stable directory contain?"> +<link href="ch-ftparchives.en.html#s-testing" rel="section" title="6.5 What does the testing distribution contain?"> +<link href="ch-ftparchives.en.html#s-unstable" rel="section" title="6.6 What does the unstable distribution contain?"> +<link href="ch-ftparchives.en.html#s-dirtree" rel="section" title="6.7 What are all those directories at the Debian FTP archives?"> +<link href="ch-ftparchives.en.html#s-archsections" rel="section" title="6.8 What are all those directories inside <samp>dists/stable/main</samp>?"> +<link href="ch-ftparchives.en.html#s-source" rel="section" title="6.9 Where is the source code?"> +<link href="ch-ftparchives.en.html#s-pools" rel="section" title="6.10 What's in the <samp>pool</samp> directory?"> +<link href="ch-ftparchives.en.html#s-incoming" rel="section" title="6.11 What is "incoming"?"> +<link href="ch-ftparchives.en.html#s-ownrepository" rel="section" title="6.12 How do I set up my own apt-able repository?"> +<link href="ch-pkg_basics.en.html#s-package" rel="section" title="7.1 What is a Debian package?"> +<link href="ch-pkg_basics.en.html#s-deb-format" rel="section" title="7.2 What is the format of a Debian binary package?"> +<link href="ch-pkg_basics.en.html#s-pkgname" rel="section" title="7.3 Why are Debian package file names so long?"> +<link href="ch-pkg_basics.en.html#s-controlfile" rel="section" title="7.4 What is a Debian control file?"> +<link href="ch-pkg_basics.en.html#s-conffile" rel="section" title="7.5 What is a Debian conffile?"> +<link href="ch-pkg_basics.en.html#s-maintscripts" rel="section" title="7.6 What is a Debian preinst, postinst, prerm, and postrm script?"> +<link href="ch-pkg_basics.en.html#s-priority" rel="section" title="7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?"> +<link href="ch-pkg_basics.en.html#s-virtual" rel="section" title="7.8 What is a Virtual Package?"> +<link href="ch-pkg_basics.en.html#s-depends" rel="section" title="7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?"> +<link href="ch-pkg_basics.en.html#s-pre-depends" rel="section" title="7.10 What is meant by Pre-Depends?"> +<link href="ch-pkg_basics.en.html#s-pkgstatus" rel="section" title="7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?"> +<link href="ch-pkg_basics.en.html#s-puttingonhold" rel="section" title="7.12 How do I put a package on hold?"> +<link href="ch-pkg_basics.en.html#s-sourcepkgs" rel="section" title="7.13 How do I install a source package?"> +<link href="ch-pkg_basics.en.html#s-sourcebuild" rel="section" title="7.14 How do I build binary packages from a source package?"> +<link href="ch-pkg_basics.en.html#s-creatingdebs" rel="section" title="7.15 How do I create Debian packages myself?"> +<link href="ch-pkgtools.en.html#s-pkgprogs" rel="section" title="8.1 What programs does Debian provide for managing its packages?"> +<link href="ch-pkgtools.en.html#s-updaterunning" rel="section" title="8.2 Debian claims to be able to update a running program; how is this accomplished?"> +<link href="ch-pkgtools.en.html#s-whatpackages" rel="section" title="8.3 How can I tell what packages are already installed on a Debian system?"> +<link href="ch-pkgtools.en.html#s-listfiles" rel="section" title="8.4 How to display the files of a package installed?"> +<link href="ch-pkgtools.en.html#s-filesearch" rel="section" title="8.5 How can I find out what package produced a particular file?"> +<link href="ch-pkgtools.en.html#s-datapackages" rel="section" title="8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?"> +<link href="ch-uptodate.en.html#s-howtocurrent" rel="section" title="9.1 How can I keep my Debian system current?"> +<link href="ch-uptodate.en.html#s-upgradesingle" rel="section" title="9.2 Must I go into single user mode in order to upgrade a package?"> +<link href="ch-uptodate.en.html#s-savedebs" rel="section" title="9.3 Do I have to keep all those .deb archive files on my disk?"> +<link href="ch-uptodate.en.html#s-keepingalog" rel="section" title="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!"> +<link href="ch-uptodate.en.html#s-autoupdate" rel="section" title="9.5 Can I automatically update the system?"> +<link href="ch-uptodate.en.html#s-aptproxy" rel="section" title="9.6 I have several machines how can I download the updates only one time?"> +<link href="ch-kernel.en.html#s-non-debian-kernel" rel="section" title="10.1 Can I install and compile a kernel without some Debian-specific tweaking?"> +<link href="ch-kernel.en.html#s-customkernel" rel="section" title="10.2 What tools does Debian provide to build custom kernels?"> +<link href="ch-kernel.en.html#s-custombootdisk" rel="section" title="10.3 How can I make a custom boot floppy?"> +<link href="ch-kernel.en.html#s-modules" rel="section" title="10.4 What special provisions does Debian provide to deal with modules?"> +<link href="ch-kernel.en.html#s-removeoldkernel" rel="section" title="10.5 Can I safely de-install an old kernel package, and if so, how?"> +<link href="ch-customizing.en.html#s-papersize" rel="section" title="11.1 How can I ensure that all programs use the same paper size?"> +<link href="ch-customizing.en.html#s-hardwareaccess" rel="section" title="11.2 How can I provide access to hardware peripherals, without compromising security?"> +<link href="ch-customizing.en.html#s-consolefont" rel="section" title="11.3 How do I load a console font on startup the Debian way?"> +<link href="ch-customizing.en.html#s-appdefaults" rel="section" title="11.4 How can I configure an X11 program's application defaults?"> +<link href="ch-customizing.en.html#s-booting" rel="section" title="11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's."> +<link href="ch-customizing.en.html#s-custombootscripts" rel="section" title="11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?"> +<link href="ch-customizing.en.html#s-interconffiles" rel="section" title="11.7 How does the package management system deal with packages that contain configuration files for other packages?"> +<link href="ch-customizing.en.html#s-divert" rel="section" title="11.8 How do I override a file installed by a package, so that a different version can be used instead?"> +<link href="ch-customizing.en.html#s-localpackages" rel="section" title="11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?"> +<link href="ch-customizing.en.html#s-diverse" rel="section" title="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?"> +<link href="ch-support.en.html#s-debiandocs" rel="section" title="12.1 What other documentation exists on and for a Debian system?"> +<link href="ch-support.en.html#s-onlineresources" rel="section" title="12.2 Are there any on-line resources for discussing Debian?"> +<link href="ch-support.en.html#s-searchtools" rel="section" title="12.3 Is there a quick way to search for information on Debian GNU/Linux?"> +<link href="ch-support.en.html#s-buglogs" rel="section" title="12.4 Are there logs of known bugs?"> +<link href="ch-support.en.html#s-bugreport" rel="section" title="12.5 How do I report a bug in Debian?"> +<link href="ch-contributing.en.html#s-contrib" rel="section" title="13.1 How can I become a Debian software developer?"> +<link href="ch-contributing.en.html#s-contribresources" rel="section" title="13.2 How can I contribute resources to the Debian project?"> +<link href="ch-contributing.en.html#s-supportingorganizations" rel="section" title="13.3 How can I contribute financially to the Debian project?"> +<link href="ch-redistrib.en.html#s-sellcds" rel="section" title="14.1 Can I make and sell Debian CDs?"> +<link href="ch-redistrib.en.html#s-packagednonfree" rel="section" title="14.2 Can Debian be packaged with non-free software?"> +<link href="ch-redistrib.en.html#s-childistro" rel="section" title="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?"> +<link href="ch-redistrib.en.html#s-commercialdebs" rel="section" title="14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?"> +<link href="ch-nexttime.en.html#s-i18n" rel="section" title="15.1 Extended support for non-English users"> +<link href="ch-nexttime.en.html#s-dependencybasedboot" rel="section" title="15.2 Faster booting: Dependency based boot sequence"> +<link href="ch-nexttime.en.html#s-di" rel="section" title="15.3 Improvements in the Debian Installer"> +<link href="ch-nexttime.en.html#s-morearches" rel="section" title="15.4 More architectures"> +<link href="ch-nexttime.en.html#s-morekernels" rel="section" title="15.5 More kernels"> +<link href="ch-faqinfo.en.html#s-authors" rel="section" title="16.1 Authors"> +<link href="ch-faqinfo.en.html#s-feedback" rel="section" title="16.2 Feedback"> +<link href="ch-faqinfo.en.html#s-latest" rel="section" title="16.3 Availability"> +<link href="ch-faqinfo.en.html#s-docformat" rel="section" title="16.4 Document format"> +<link href="ch-choosing.en.html#s3.1.1" rel="subsection" title="3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?"> +<link href="ch-choosing.en.html#s3.1.2" rel="subsection" title="3.1.2 Will there be different different versions of packages in different distributions?"> +<link href="ch-choosing.en.html#s3.1.3" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.4" rel="subsection" title="3.1.4 If I were to decide to change to another distribution, Can I do that?"> +<link href="ch-choosing.en.html#s3.1.5" rel="subsection" title="3.1.5 Could you tell me whether to install testing or unstable?"> +<link href="ch-choosing.en.html#s3.1.6" rel="subsection" title="3.1.6 You are talking about testing being broken. What do you mean by that?"> +<link href="ch-choosing.en.html#s3.1.7" rel="subsection" title="3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?"> +<link href="ch-choosing.en.html#s3.1.8" rel="subsection" title="3.1.8 From an administrator's point of view, Which distribution requires more attention?"> +<link href="ch-choosing.en.html#s3.1.9" rel="subsection" title="3.1.9 What happens when a new release is made?"> +<link href="ch-choosing.en.html#s3.1.10" rel="subsection" title="3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?"> +<link href="ch-choosing.en.html#s3.1.11" rel="subsection" title="3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?"> +<link href="ch-choosing.en.html#s3.1.12" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.1.13" rel="subsection" title="3.1.13 I am still confused. What did you say I should install?"> +<link href="ch-choosing.en.html#s3.2.1" rel="subsection" title="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?"> +<link href="ch-choosing.en.html#s3.2.2" rel="subsection" title="3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?"> +<link href="ch-choosing.en.html#s3.2.3" rel="subsection" title="3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?"> +<link href="ch-ftparchives.en.html#s-oldcodenames" rel="subsection" title="6.2.1 Which other codenames have been used in the past?"> +<link href="ch-ftparchives.en.html#s-sourceforcodenames" rel="subsection" title="6.2.2 Where do these codenames come from?"> +<link href="ch-ftparchives.en.html#s-frozen" rel="subsection" title="6.5.1 What about "testing"? How is it `frozen'?"> +<link href="ch-pkgtools.en.html#s-dpkg" rel="subsection" title="8.1.1 dpkg"> +<link href="ch-pkgtools.en.html#s-apt-get" rel="subsection" title="8.1.2 APT"> +<link href="ch-pkgtools.en.html#s-aptitude" rel="subsection" title="8.1.3 aptitude"> +<link href="ch-pkgtools.en.html#s-synaptic" rel="subsection" title="8.1.4 synaptic"> +<link href="ch-pkgtools.en.html#s-tasksel" rel="subsection" title="8.1.5 tasksel"> +<link href="ch-pkgtools.en.html#s-dpkg-extra" rel="subsection" title="8.1.6 Other package management tools"> +<link href="ch-pkgtools.en.html#s-dselect" rel="subsection" title="8.1.6.1 dselect"> +<link href="ch-pkgtools.en.html#s-dpkg-deb" rel="subsection" title="8.1.6.2 dpkg-deb"> +<link href="ch-pkgtools.en.html#s-dpkg-split" rel="subsection" title="8.1.6.3 dpkg-split"> +<link href="ch-uptodate.en.html#s-aptitude-upgrade" rel="subsection" title="9.1.1 aptitude"> +<link href="ch-uptodate.en.html#s-apt" rel="subsection" title="9.1.2 apt-get, dselect and apt-cdrom"> +<link href="ch-uptodate.en.html#s-update_aptitude" rel="subsection" title="9.1.3 aptitude"> +<link href="ch-uptodate.en.html#s-mirror" rel="subsection" title="9.1.4 mirror"> +<link href="ch-uptodate.en.html#s-dpkg-mountable" rel="subsection" title="9.1.5 dpkg-mountable"> +<link href="ch-support.en.html#s12.2.1" rel="subsection" title="12.2.1 Mailing lists"> +<link href="ch-support.en.html#s-mailinglistconduct" rel="subsection" title="12.2.1.1 What is the code of conduct for the mailing lists?"> +<link href="ch-support.en.html#s12.2.2" rel="subsection" title="12.2.2 Web forums"> +<link href="ch-support.en.html#s12.2.3" rel="subsection" title="12.2.3 Wiki"> +<link href="ch-support.en.html#s12.2.4" rel="subsection" title="12.2.4 Maintainers"> +<link href="ch-support.en.html#s12.2.5" rel="subsection" title="12.2.5 Usenet newsgroups"> +<link href="ch-contributing.en.html#s-SPI" rel="subsection" title="13.3.1 Software in the Public Interest"> +<link href="ch-contributing.en.html#s-FSF" rel="subsection" title="13.3.2 Free Software Foundation"> + +</head> + +<body> + +<p><a name="index"></a></p> +<hr> + +<p> +[ <a href="ch-faqinfo.en.html">previous</a> ] +[ <a href="#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-basic_defs.en.html">next</a> ] +</p> + +<hr> + +<h1> +The Debian GNU/Linux FAQ +<br></h1> + +<hr> + +<h2><a name="abstract"></a>Abstract</h2> + +<p> +This document answers questions frequently asked about Debian GNU/Linux. +</p> + +<hr> + +<h2><a name="copyright"></a>Copyright Notice</h2> + +<p> +Copyright © 1996-2005 by Software in the Public Interest, portions copyright © 2004, 2005, 2006 Kamaraju Kusumanchi +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +<hr> + +<h2><a name="contents"></a>Contents</h2> + +<ul> +<li><a href="ch-basic_defs.en.html">1 Definitions and overview</a> + <ul> + <li><a href="ch-basic_defs.en.html#s-whatisfaq">1.1 What is this FAQ?</a></li> + <li><a href="ch-basic_defs.en.html#s-whatisdebian">1.2 What is Debian GNU/Linux?</a></li> + <li><a href="ch-basic_defs.en.html#s-linux">1.3 OK, now I know what Debian is... what is Linux?!</a></li> + <li><a href="ch-basic_defs.en.html#s-non-linux">1.4 Does Debian just do GNU/Linux?</a></li> + <li><a href="ch-basic_defs.en.html#s-difference">1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?</a></li> + <li><a href="ch-basic_defs.en.html#s-gnu">1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?</a></li> + <li><a href="ch-basic_defs.en.html#s-pronunciation">1.7 How does one pronounce Debian and what does this word mean?</a> + </ul></li> +<li><a href="ch-getting.en.html">2 Getting and installing Debian GNU/Linux</a> + <ul> + <li><a href="ch-getting.en.html#s-version">2.1 What is the latest version of Debian?</a></li> + <li><a href="ch-getting.en.html#s-updatestable">2.2 Are there package upgrades in `stable'?</a></li> + <li><a href="ch-getting.en.html#s-boot-floppies">2.3 Where/how can I get the Debian installation disks?</a></li> + <li><a href="ch-getting.en.html#s-cdrom">2.4 How do I install the Debian from CD-ROMs?</a></li> + <li><a href="ch-getting.en.html#s-cdimage-symlinks">2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!</a></li> + <li><a href="ch-getting.en.html#s-remoteinstall">2.6 Can I get and install Debian directly from a remote Internet site?</a></li> + <li><a href="ch-getting.en.html#s-alternativebootinstaller">2.7 Are there any alternative strategies for booting the system installer?</a> + </ul></li> +<li><a href="ch-choosing.en.html">3 Choosing a Debian distribution</a> + <ul> + <li><a href="ch-choosing.en.html#s3.1">3.1 Which Debian distribution (stable/testing/unstable) is better for me?</a> + <ul> + <li><a href="ch-choosing.en.html#s3.1.1">3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?</a></li> + <li><a href="ch-choosing.en.html#s3.1.2">3.1.2 Will there be different different versions of packages in different distributions?</a></li> + <li><a href="ch-choosing.en.html#s3.1.3">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?</a></li> + <li><a href="ch-choosing.en.html#s3.1.4">3.1.4 If I were to decide to change to another distribution, Can I do that?</a></li> + <li><a href="ch-choosing.en.html#s3.1.5">3.1.5 Could you tell me whether to install testing or unstable?</a></li> + <li><a href="ch-choosing.en.html#s3.1.6">3.1.6 You are talking about testing being broken. What do you mean by that?</a></li> + <li><a href="ch-choosing.en.html#s3.1.7">3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?</a></li> + <li><a href="ch-choosing.en.html#s3.1.8">3.1.8 From an administrator's point of view, Which distribution requires more attention?</a></li> + <li><a href="ch-choosing.en.html#s3.1.9">3.1.9 What happens when a new release is made?</a></li> + <li><a href="ch-choosing.en.html#s3.1.10">3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?</a></li> + <li><a href="ch-choosing.en.html#s3.1.11">3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?</a></li> + <li><a href="ch-choosing.en.html#s3.1.12">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?</a></li> + <li><a href="ch-choosing.en.html#s3.1.13">3.1.13 I am still confused. What did you say I should install?</a> + </ul></li> + <li><a href="ch-choosing.en.html#s3.2">3.2 But what about Knoppix, Linex, Ubuntu, and others?</a> + <ul> + <li><a href="ch-choosing.en.html#s3.2.1">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?</a></li> + <li><a href="ch-choosing.en.html#s3.2.2">3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?</a></li> + <li><a href="ch-choosing.en.html#s3.2.3">3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?</a> + </ul></li> + </ul></li> +<li><a href="ch-compat.en.html">4 Compatibility issues</a> + <ul> + <li><a href="ch-compat.en.html#s-arches">4.1 On what hardware architectures/systems does Debian GNU/Linux run?</a></li> + <li><a href="ch-compat.en.html#s-otherdistribs">4.2 How compatible is Debian with other distributions of Linux?</a></li> + <li><a href="ch-compat.en.html#s-otherunices">4.3 How source code compatible is Debian with other Unix systems?</a></li> + <li><a href="ch-compat.en.html#s-otherpackages">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?</a></li> + <li><a href="ch-compat.en.html#s-non-debian-programs">4.5 How should I install a non-Debian program?</a></li> + <li><a href="ch-compat.en.html#s-termcap">4.6 Why can't I compile programs that require libtermcap?</a></li> + <li><a href="ch-compat.en.html#s-accelx">4.7 Why can't I install AccelX?</a></li> + <li><a href="ch-compat.en.html#s-motifnls">4.8 Why do my old XFree 2.1 Motif applications crash?</a> + </ul></li> +<li><a href="ch-software.en.html">5 Software available in the Debian system</a> + <ul> + <li><a href="ch-software.en.html#s-apps">5.1 What types of applications and development software are available for Debian GNU/Linux?</a></li> + <li><a href="ch-software.en.html#s-softwareauthors">5.2 Who wrote all that software?</a></li> + <li><a href="ch-software.en.html#s-pkglist">5.3 How can I get a current list of programs that have been packaged for Debian?</a></li> + <li><a href="ch-software.en.html#s-buildenv">5.4 How can I install a developer's environment to build packages?</a></li> + <li><a href="ch-software.en.html#s-missing">5.5 What is missing from Debian GNU/Linux?</a></li> + <li><a href="ch-software.en.html#s-no-devs">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?</a></li> + <li><a href="ch-software.en.html#s-java">5.7 (How) Does Debian support Java?</a></li> + <li><a href="ch-software.en.html#s-isitdebian">5.8 How can I check that I am using a Debian system, and what version is it?</a></li> + <li><a href="ch-software.en.html#s-nonenglish">5.9 How does Debian support non-English languages?</a></li> + <li><a href="ch-software.en.html#s-pine">5.10 Where is pine?</a></li> + <li><a href="ch-software.en.html#s-qmail">5.11 Where is qmail/ezmlm/djbdns?</a></li> + <li><a href="ch-software.en.html#s-flash">5.12 Where is a player for Flash (SWF)?</a></li> + <li><a href="ch-software.en.html#s-googleearth">5.13 Where is Google Earth?</a></li> + <li><a href="ch-software.en.html#s-voip">5.14 Where is VoIP software?</a></li> + <li><a href="ch-software.en.html#s-nonfreewireless">5.15 I have a wireless network card which doesn't work with Linux. What should I do?</a> + </ul></li> +<li><a href="ch-ftparchives.en.html">6 The Debian FTP archives</a> + <ul> + <li><a href="ch-ftparchives.en.html#s-dists">6.1 How many Debian distributions are there?</a></li> + <li><a href="ch-ftparchives.en.html#s-codenames">6.2 What are all those names like etch, lenny, etc.?</a> + <ul> + <li><a href="ch-ftparchives.en.html#s-oldcodenames">6.2.1 Which other codenames have been used in the past?</a></li> + <li><a href="ch-ftparchives.en.html#s-sourceforcodenames">6.2.2 Where do these codenames come from?</a> + </ul></li> + <li><a href="ch-ftparchives.en.html#s-sid">6.3 What about "sid"?</a></li> + <li><a href="ch-ftparchives.en.html#s-stable">6.4 What does the stable directory contain?</a></li> + <li><a href="ch-ftparchives.en.html#s-testing">6.5 What does the testing distribution contain?</a> + <ul> + <li><a href="ch-ftparchives.en.html#s-frozen">6.5.1 What about "testing"? How is it `frozen'?</a> + </ul></li> + <li><a href="ch-ftparchives.en.html#s-unstable">6.6 What does the unstable distribution contain?</a></li> + <li><a href="ch-ftparchives.en.html#s-dirtree">6.7 What are all those directories at the Debian FTP archives?</a></li> + <li><a href="ch-ftparchives.en.html#s-archsections">6.8 What are all those directories inside <samp>dists/stable/main</samp>?</a></li> + <li><a href="ch-ftparchives.en.html#s-source">6.9 Where is the source code?</a></li> + <li><a href="ch-ftparchives.en.html#s-pools">6.10 What's in the <samp>pool</samp> directory?</a></li> + <li><a href="ch-ftparchives.en.html#s-incoming">6.11 What is "incoming"?</a></li> + <li><a href="ch-ftparchives.en.html#s-ownrepository">6.12 How do I set up my own apt-able repository?</a> + </ul></li> +<li><a href="ch-pkg_basics.en.html">7 Basics of the Debian package management system</a> + <ul> + <li><a href="ch-pkg_basics.en.html#s-package">7.1 What is a Debian package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-deb-format">7.2 What is the format of a Debian binary package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-pkgname">7.3 Why are Debian package file names so long?</a></li> + <li><a href="ch-pkg_basics.en.html#s-controlfile">7.4 What is a Debian control file?</a></li> + <li><a href="ch-pkg_basics.en.html#s-conffile">7.5 What is a Debian conffile?</a></li> + <li><a href="ch-pkg_basics.en.html#s-maintscripts">7.6 What is a Debian preinst, postinst, prerm, and postrm script?</a></li> + <li><a href="ch-pkg_basics.en.html#s-priority">7.7 What is an <em>Essential</em>, <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-virtual">7.8 What is a Virtual Package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-depends">7.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-pre-depends">7.10 What is meant by Pre-Depends?</a></li> + <li><a href="ch-pkg_basics.en.html#s-pkgstatus">7.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em>, <em>purge</em> and <em>hold</em> in the package status?</a></li> + <li><a href="ch-pkg_basics.en.html#s-puttingonhold">7.12 How do I put a package on hold?</a></li> + <li><a href="ch-pkg_basics.en.html#s-sourcepkgs">7.13 How do I install a source package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-sourcebuild">7.14 How do I build binary packages from a source package?</a></li> + <li><a href="ch-pkg_basics.en.html#s-creatingdebs">7.15 How do I create Debian packages myself?</a> + </ul></li> +<li><a href="ch-pkgtools.en.html">8 The Debian package management tools</a> + <ul> + <li><a href="ch-pkgtools.en.html#s-pkgprogs">8.1 What programs does Debian provide for managing its packages?</a> + <ul> + <li><a href="ch-pkgtools.en.html#s-dpkg">8.1.1 dpkg</a></li> + <li><a href="ch-pkgtools.en.html#s-apt-get">8.1.2 APT</a></li> + <li><a href="ch-pkgtools.en.html#s-aptitude">8.1.3 aptitude</a></li> + <li><a href="ch-pkgtools.en.html#s-synaptic">8.1.4 synaptic</a></li> + <li><a href="ch-pkgtools.en.html#s-tasksel">8.1.5 tasksel</a></li> + <li><a href="ch-pkgtools.en.html#s-dpkg-extra">8.1.6 Other package management tools</a> + </ul></li> + <li><a href="ch-pkgtools.en.html#s-updaterunning">8.2 Debian claims to be able to update a running program; how is this accomplished?</a></li> + <li><a href="ch-pkgtools.en.html#s-whatpackages">8.3 How can I tell what packages are already installed on a Debian system?</a></li> + <li><a href="ch-pkgtools.en.html#s-listfiles">8.4 How to display the files of a package installed?</a></li> + <li><a href="ch-pkgtools.en.html#s-filesearch">8.5 How can I find out what package produced a particular file?</a></li> + <li><a href="ch-pkgtools.en.html#s-datapackages">8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?</a> + </ul></li> +<li><a href="ch-uptodate.en.html">9 Keeping your Debian system up-to-date</a> + <ul> + <li><a href="ch-uptodate.en.html#s-howtocurrent">9.1 How can I keep my Debian system current?</a> + <ul> + <li><a href="ch-uptodate.en.html#s-aptitude-upgrade">9.1.1 aptitude</a></li> + <li><a href="ch-uptodate.en.html#s-apt">9.1.2 apt-get, dselect and apt-cdrom</a></li> + <li><a href="ch-uptodate.en.html#s-update_aptitude">9.1.3 aptitude</a></li> + <li><a href="ch-uptodate.en.html#s-mirror">9.1.4 mirror</a></li> + <li><a href="ch-uptodate.en.html#s-dpkg-mountable">9.1.5 dpkg-mountable</a> + </ul></li> + <li><a href="ch-uptodate.en.html#s-upgradesingle">9.2 Must I go into single user mode in order to upgrade a package?</a></li> + <li><a href="ch-uptodate.en.html#s-savedebs">9.3 Do I have to keep all those .deb archive files on my disk?</a></li> + <li><a href="ch-uptodate.en.html#s-keepingalog">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!</a></li> + <li><a href="ch-uptodate.en.html#s-autoupdate">9.5 Can I automatically update the system?</a></li> + <li><a href="ch-uptodate.en.html#s-aptproxy">9.6 I have several machines how can I download the updates only one time?</a> + </ul></li> +<li><a href="ch-kernel.en.html">10 Debian and the kernel</a> + <ul> + <li><a href="ch-kernel.en.html#s-non-debian-kernel">10.1 Can I install and compile a kernel without some Debian-specific tweaking?</a></li> + <li><a href="ch-kernel.en.html#s-customkernel">10.2 What tools does Debian provide to build custom kernels?</a></li> + <li><a href="ch-kernel.en.html#s-custombootdisk">10.3 How can I make a custom boot floppy?</a></li> + <li><a href="ch-kernel.en.html#s-modules">10.4 What special provisions does Debian provide to deal with modules?</a></li> + <li><a href="ch-kernel.en.html#s-removeoldkernel">10.5 Can I safely de-install an old kernel package, and if so, how?</a> + </ul></li> +<li><a href="ch-customizing.en.html">11 Customizing your installation of Debian GNU/Linux</a> + <ul> + <li><a href="ch-customizing.en.html#s-papersize">11.1 How can I ensure that all programs use the same paper size?</a></li> + <li><a href="ch-customizing.en.html#s-hardwareaccess">11.2 How can I provide access to hardware peripherals, without compromising security?</a></li> + <li><a href="ch-customizing.en.html#s-consolefont">11.3 How do I load a console font on startup the Debian way?</a></li> + <li><a href="ch-customizing.en.html#s-appdefaults">11.4 How can I configure an X11 program's application defaults?</a></li> + <li><a href="ch-customizing.en.html#s-booting">11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's.</a></li> + <li><a href="ch-customizing.en.html#s-custombootscripts">11.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?</a></li> + <li><a href="ch-customizing.en.html#s-interconffiles">11.7 How does the package management system deal with packages that contain configuration files for other packages?</a></li> + <li><a href="ch-customizing.en.html#s-divert">11.8 How do I override a file installed by a package, so that a different version can be used instead?</a></li> + <li><a href="ch-customizing.en.html#s-localpackages">11.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?</a></li> + <li><a href="ch-customizing.en.html#s-diverse">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?</a> + </ul></li> +<li><a href="ch-support.en.html">12 Getting support for Debian GNU/Linux</a> + <ul> + <li><a href="ch-support.en.html#s-debiandocs">12.1 What other documentation exists on and for a Debian system?</a></li> + <li><a href="ch-support.en.html#s-onlineresources">12.2 Are there any on-line resources for discussing Debian?</a> + <ul> + <li><a href="ch-support.en.html#s12.2.1">12.2.1 Mailing lists</a></li> + <li><a href="ch-support.en.html#s12.2.2">12.2.2 Web forums</a></li> + <li><a href="ch-support.en.html#s12.2.3">12.2.3 Wiki</a></li> + <li><a href="ch-support.en.html#s12.2.4">12.2.4 Maintainers</a></li> + <li><a href="ch-support.en.html#s12.2.5">12.2.5 Usenet newsgroups</a> + </ul></li> + <li><a href="ch-support.en.html#s-searchtools">12.3 Is there a quick way to search for information on Debian GNU/Linux?</a></li> + <li><a href="ch-support.en.html#s-buglogs">12.4 Are there logs of known bugs?</a></li> + <li><a href="ch-support.en.html#s-bugreport">12.5 How do I report a bug in Debian?</a> + </ul></li> +<li><a href="ch-contributing.en.html">13 Contributing to the Debian Project</a> + <ul> + <li><a href="ch-contributing.en.html#s-contrib">13.1 How can I become a Debian software developer?</a></li> + <li><a href="ch-contributing.en.html#s-contribresources">13.2 How can I contribute resources to the Debian project?</a></li> + <li><a href="ch-contributing.en.html#s-supportingorganizations">13.3 How can I contribute financially to the Debian project?</a> + <ul> + <li><a href="ch-contributing.en.html#s-SPI">13.3.1 Software in the Public Interest</a></li> + <li><a href="ch-contributing.en.html#s-FSF">13.3.2 Free Software Foundation</a> + </ul></li> + </ul></li> +<li><a href="ch-redistrib.en.html">14 Redistributing Debian GNU/Linux in a commercial product</a> + <ul> + <li><a href="ch-redistrib.en.html#s-sellcds">14.1 Can I make and sell Debian CDs?</a></li> + <li><a href="ch-redistrib.en.html#s-packagednonfree">14.2 Can Debian be packaged with non-free software?</a></li> + <li><a href="ch-redistrib.en.html#s-childistro">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?</a></li> + <li><a href="ch-redistrib.en.html#s-commercialdebs">14.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?</a> + </ul></li> +<li><a href="ch-nexttime.en.html">15 Changes expected in the next major release of Debian</a> + <ul> + <li><a href="ch-nexttime.en.html#s-i18n">15.1 Extended support for non-English users</a></li> + <li><a href="ch-nexttime.en.html#s-dependencybasedboot">15.2 Faster booting: Dependency based boot sequence</a></li> + <li><a href="ch-nexttime.en.html#s-di">15.3 Improvements in the Debian Installer</a></li> + <li><a href="ch-nexttime.en.html#s-morearches">15.4 More architectures</a></li> + <li><a href="ch-nexttime.en.html#s-morekernels">15.5 More kernels</a> + </ul></li> +<li><a href="ch-faqinfo.en.html">16 General information about the FAQ</a> + <ul> + <li><a href="ch-faqinfo.en.html#s-authors">16.1 Authors</a></li> + <li><a href="ch-faqinfo.en.html#s-feedback">16.2 Feedback</a></li> + <li><a href="ch-faqinfo.en.html#s-latest">16.3 Availability</a></li> + <li><a href="ch-faqinfo.en.html#s-docformat">16.4 Document format</a></li> + </ul></li> +</ul> + +<hr> + +<p> +[ <a href="ch-faqinfo.en.html">previous</a> ] +[ <a href="#contents">Contents</a> ] +[ <a href="ch-basic_defs.en.html">1</a> ] +[ <a href="ch-getting.en.html">2</a> ] +[ <a href="ch-choosing.en.html">3</a> ] +[ <a href="ch-compat.en.html">4</a> ] +[ <a href="ch-software.en.html">5</a> ] +[ <a href="ch-ftparchives.en.html">6</a> ] +[ <a href="ch-pkg_basics.en.html">7</a> ] +[ <a href="ch-pkgtools.en.html">8</a> ] +[ <a href="ch-uptodate.en.html">9</a> ] +[ <a href="ch-kernel.en.html">10</a> ] +[ <a href="ch-customizing.en.html">11</a> ] +[ <a href="ch-support.en.html">12</a> ] +[ <a href="ch-contributing.en.html">13</a> ] +[ <a href="ch-redistrib.en.html">14</a> ] +[ <a href="ch-nexttime.en.html">15</a> ] +[ <a href="ch-faqinfo.en.html">16</a> ] +[ <a href="ch-basic_defs.en.html">next</a> ] +</p> + +<hr> + +<p> +The Debian GNU/Linux FAQ +</p> + +<address> +version 4.0.3, 6 August 2008<br> +<br> +Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> +<br> +</address> +<hr> + +</body> + +</html> + 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 0000000..0e85422 --- /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 0000000..c8fa75f --- /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 <owner@bugs.debian.org> + + 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 0000000..447a059 --- /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 <owner@bugs.debian.org> + + 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 0000000..04a075b --- /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 <owner@bugs.debian.org> + + 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 0000000..e8b0206 --- /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 <owner@bugs.debian.org> + + 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 0000000..a0b7c9e --- /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 <owner@bugs.debian.org> + + 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 0000000..974eb20 --- /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 #<number>, you should submit your + comments by sending e-mail to <number>@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: <packagename> + + Replace <packagename> with the name of the package which has the bug. + + The second line of the message should say: +Version: <packageversion> + + Replace <packageversion> 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 + <package> 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: <severity> + + Replace <severity> 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: <tags> + + Replace <tags> with one or more of the available tags, as described in + the advanced documentation. Separate multiple tags with commas, + spaces, or both. +User: <username> +Usertags: <usertags> + + Replace <usertags> with one or more usertags. Separate multiple tags + with commas, spaces, or both. If you specify a <username>, 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 <deity@lists.debian.org> +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 <owner@bugs.debian.org> + + 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 0000000..96ed0c7 --- /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 0000000..9322c93 --- /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 0000000..84010d8 --- /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 + + <listname>-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 0000000..63591f8 --- /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 0000000..151b733 --- /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 <whatever>.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 <ijackson@gnu.ai.mit.edu> Sat, 31 Aug 1996 diff --git a/includes/lenny/install/README.html b/includes/lenny/install/README.html new file mode 100644 index 0000000..1717250 --- /dev/null +++ b/includes/lenny/install/README.html @@ -0,0 +1,253 @@ + + +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> + <title>Debian GNU/Linux -- The Universal Operating System</title> + <meta name="Description" content="Debian GNU/Linux is a free distribution of the GNU/Linux operating system. It is maintained and updated through the work of many users who volunteer their time and effort." /> + <meta name="Keywords" content="debian, GNU, linux, unix, open source, free, DFSG" /> + <meta name="Language" content="English" /> + <meta name="Author" content="J.A. Bezemer, debian-boot@lists.debian.org" /> + <link rev="made" href="mailto:debian-boot@lists.debian.org" /> + <link href="css/debinstall.css" rel="stylesheet" type="text/css" /> + <link href="css/debinstall-print.css" media="print" rel="stylesheet" type="text/css" /> +</head> +<body id="readme"> + + <!-- The HTML and TEXT file are NOT the actual source code. --> + <!-- For that, see http://svn.debian.org/wsvn/debian-cd --> + + + + + + + + <div id="header"> + <div id="upperheader"> + <div id="logo"> + <a href="http://www.debian.org/" title="www.debian.org"><img + src="pics/openlogo-nd-50.png" width="70" height="120" + alt="www.debian.org" /></a> + </div><!-- end logo --> + <p class="section"><em>Installer</em></p> + </div><!-- end upperheader --> + <!--UdmComment--> + + + <div id="intro"> + <div id="splash"> + <h1> + Welcome to the exciting world of + <span id="debian-img"><img + src="pics/debian-61.png" alt="Debian GNU/Linux" + height="94" width="211" /></span></h1> + + <p>This disc contains the installer for the + <a href="http://www.debian.org/">Debian GNU/Linux</a> 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 <a href= + "http://www.debian.org/intro/free">free</a> (as in + “freedom”).</p> + </div> + </div> + + <p id="breadcrumbs"> + <span class="alt">(<a href= "README.txt">Text version</a>)</span> + Debian GNU/Linux testing "Lenny" - Official RC i386 BC Binary-1 20081104-23:45 + </p> + </div><!-- end header --> + + <div id="outer"> + <ul class="toc"> + <li><a href="#introduction">Introduction</a></li> + <li><a href="#thisdisc">About This Disc</a></li> + <li><a href="#install">Installing</a></li> + <li><a href="#lastmin">Last-Minute Notes</a></li> + <li><a href="#apt">Installing software using Apt</a></li> + <li><a href="#cdmanuf">CD/DVD Manufacturers</a></li> + <li><a href="#other">More Information</a></li> + <li><a href=".">Browse This Disc</a></li> + </ul> + + <h2 id="introduction"> + Introduction + </h2> + + <p>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 <a href= + "http://www.linux.org/">Linux</a> kernel but work is in + progress to provide Debian for other kernels, using <a href= + "http://www.gnu.org/software/hurd/hurd.html">the Hurd</a>. Most + of the basic operating system tools come from the <a href= + "http://www.gnu.org/">GNU project</a>; hence the name + GNU/Linux.</p> + + <p>Debian is available for various kinds of computers + (“architectures”), like “IBM-compatible” PCs (<em>i386</em>), + Compaq's <em>Alpha</em>, Sun's <em>Sparc</em>, Motorola/IBM's + <em>PowerPC</em>, and <em>(Strong)ARM</em> processors. Check the + <a href="http://www.debian.org/ports">ports</a> page for more + information.</p> + + <p><a href="http://www.debian.org/intro/about">Read more...</a></p> + + <h2 id="thisdisc"> + About This Disc + </h2> + + <p>This disc is labeled + <small><strong>Debian GNU/Linux testing "Lenny" - Official RC i386 BC Binary-1 20081104-23:45</strong></small> + . + It contains programs ("binaries") for `i386' computers.</p> + <p>This disc is a <em>business card</em> image. It contains only the + installer and will download the base system and the remaining packages from + the network.</p> + <p>The Release Notes for "lenny" are available on the + <a href="http://www.debian.org/releases/lenny/releasenotes">Debian web + site</a>.</p> + + <h2 id="install"> + Installing + </h2> + + <p>Because Debian is a complete Operating System, the + installation procedure may seem a bit unusual. You can install + Debian GNU/Linux either <em>alongside</em> your current OS, or as + the <em>only</em> OS on your computer.</p> + <p>An <b>Installation Guide</b> for this disc is available from + <a href="http://www.debian.org/releases/lenny/installmanual">the + Debian web site</a>.</p> + <p>Programs and other files that are needed for the installation can be + found on this disc under + <tt><a href="tools/">/tools/</a></tt> + and <tt><a href="install/floppy/">/install/floppy/</a></tt> + </p> + + <p>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.</p> + + <p>You can also examine the <tt><a href="install/">/install/</a></tt> + directory; you might be able to start the installation system directly + from there.</p> + + + <h2 id="lastmin"> + Last-Minute Notes + </h2> + + <ul> + <li>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.</li> + + </ul> + + <h2 id="apt"> + Installing software using Apt + </h2> + + <p>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 + <em>packages</em>). This is done preferably with the ‘apt’ and + ‘aptitude’ programs.</p> + + <p>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:</p> + + <p> + <code>apt-get install commprog maxgame</code> + </p> + + <p>Note that you don't have to enter the complete path, or the + ‘.deb’ extension. ‘Apt’ will figure this out + itself.</p> + + <p>Or use aptitude for a full screen interactive selection of + available Debian packages.</p> + + <h2 id="cdmanuf"> + CD/DVD Manufacturers + </h2> + + <p>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).</p> + + <p>For all needed information and contact addresses, please + refer to:</p> + + <p> + <a href="http://www.debian.org/CD/">http://www.debian.org/CD/</a> + </p> + + <h2 id="other"> + More Information + </h2> + + + <p>There is much more information present on this disc. Besides + the already mentioned installation and upgrading procedures, + this is the most interesting:</p> + + <ul> + <li> + <a href="doc/FAQ/">Debian FAQ</a> + </li> + <li> + <a href="doc/constitution.txt">The Debian Constitution</a> + </li> + <li> + <a href="doc/debian-manifesto">The Debian Manifesto</a> + </li> + <li> + <a href="doc/social-contract.txt">Debian's Social Contract</a> + </li> + <li> + <a href="doc/bug-reporting.txt">Bug reporting instructions</a> + </li> + </ul> + + + <p>Also on the Internet are many resources. To name a few:</p> + + <ul> + <li> + <a href="http://www.debian.org/">The Debian homepage</a> + </li> + <li> + <a href="http://www.debian.org/doc/">Debian Documentation</a> + </li> + <li> + <a href="http://www.debian.org/support">Debian User Support</a> + </li> + <li> + <a href="http://www.tldp.org/">The Linux Documentation Project</a> + </li> + <li> + <a href="http://www.linux.org/">General Linux homepage</a> + </li> + </ul> + + + <div id="fineprint"> + <p> + See the Debian <a href= + "http://www.debian.org/contact">contact page</a> + for information on contacting us.</p> + </div> + </div> +</body> +</html> diff --git a/includes/lenny/install/README.mirrors.html b/includes/lenny/install/README.mirrors.html new file mode 100644 index 0000000..0518305 --- /dev/null +++ b/includes/lenny/install/README.mirrors.html @@ -0,0 +1,2622 @@ +<html> + +<head> + <title>Debian worldwide mirror sites</title> +</head> + +<body> +<h1 align="center">Debian worldwide mirror sites</h1> +<p>Debian is distributed (<em>mirrored</em>) 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. + +<p>Debian mirrors can be primary and secondary. The definitions are as follows: + + <blockquote> + A <strong>primary mirror</strong> site has good bandwidth, is available 24 hours a day, + and has an easy to remember name of the form ftp.<country>.debian.org. + <br> + They are all automatically updated whenever there are updates to + the Debian archive. + + </blockquote> + <blockquote> + A <strong>secondary mirror</strong> 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. + + </blockquote> +<p>Use the site closest to you for the fastest downloads possible whether it is + +a primary or secondary site. The program +<a href="http://packages.debian.org/stable/net/netselect"> +<em>netselect</em></a> can be used to +determine the site with the least latency; use a download program such as + +<a href="http://packages.debian.org/stable/web/wget"> +<em>wget</em></a> or +<a href="http://packages.debian.org/stable/net/rsync"> +<em>rsync</em></a> 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. + +<p>The authoritative copy of the following list can always be found at: +<a href="http://www.debian.org/mirror/list"> http://www.debian.org/mirror/list</a>.<br> +If you know of any mirrors that are missing from this list, +please have the site maintainer fill out the form at: +<a href="http://www.debian.org/mirror/submit"> http://www.debian.org/mirror/submit</a>.<br> +Everything else you want to know about Debian mirrors: +<a href="http://www.debian.org/mirror/"> http://www.debian.org/mirror/</a>.<br> + +<h2 align="center">Primary Debian mirror sites</h2> + +<table border="0" align="center"> +<tr> + <th>Country</th> + <th>Site</th> + <th>Architectures</th> +</tr> +<tr> + <td>Austria</td> + <td><a href="http://ftp.at.debian.org/debian/">ftp.at.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Australia</td> + <td><a href="http://ftp.au.debian.org/debian/">ftp.au.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Belgium</td> + <td><a href="http://ftp.be.debian.org/debian/">ftp.be.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Bulgaria</td> + <td><a href="http://ftp.bg.debian.org/debian/">ftp.bg.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Brazil</td> + <td><a href="http://ftp.br.debian.org/debian/">ftp.br.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Canada</td> + <td><a href="http://ftp.ca.debian.org/debian/">ftp.ca.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Switzerland</td> + <td><a href="http://ftp.ch.debian.org/debian/">ftp.ch.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Chile</td> + <td><a href="http://ftp.cl.debian.org/debian/">ftp.cl.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Czech Republic</td> + <td><a href="http://ftp.cz.debian.org/debian/">ftp.cz.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Germany</td> + <td><a href="http://ftp.de.debian.org/debian/">ftp.de.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Germany</td> + <td><a href="http://ftp2.de.debian.org/debian/">ftp2.de.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Denmark</td> + <td><a href="http://ftp.dk.debian.org/debian/">ftp.dk.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Estonia</td> + <td><a href="http://ftp.ee.debian.org/debian/">ftp.ee.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Spain</td> + <td><a href="http://ftp.es.debian.org/debian/">ftp.es.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Finland</td> + <td><a href="http://ftp.fi.debian.org/debian/">ftp.fi.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>France</td> + <td><a href="http://ftp.fr.debian.org/debian/">ftp.fr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>France</td> + <td><a href="http://ftp2.fr.debian.org/debian/">ftp2.fr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Great Britain</td> + <td><a href="http://ftp.uk.debian.org/debian/">ftp.uk.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Greece</td> + <td><a href="http://ftp.gr.debian.org/debian/">ftp.gr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Hong Kong</td> + <td><a href="http://ftp.hk.debian.org/debian/">ftp.hk.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> + <td>Croatia</td> + <td><a href="http://ftp.hr.debian.org/debian/">ftp.hr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Hungary</td> + <td><a href="http://ftp.hu.debian.org/debian/">ftp.hu.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Ireland</td> + <td><a href="http://ftp.ie.debian.org/debian/">ftp.ie.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Iceland</td> + <td><a href="http://ftp.is.debian.org/debian/">ftp.is.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Italy</td> + <td><a href="http://ftp.it.debian.org/debian/">ftp.it.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Japan</td> + <td><a href="http://ftp.jp.debian.org/debian/">ftp.jp.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Japan</td> + <td><a href="http://ftp2.jp.debian.org/debian/">ftp2.jp.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Korea</td> + <td><a href="http://ftp.kr.debian.org/debian/">ftp.kr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Mexico</td> + <td><a href="http://ftp.mx.debian.org/debian/">ftp.mx.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Netherlands</td> + <td><a href="http://ftp.nl.debian.org/debian/">ftp.nl.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Norway</td> + <td><a href="http://ftp.no.debian.org/debian/">ftp.no.debian.org/debian/</a></td> + <td><small><small>amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> + <td>New Zealand</td> + <td><a href="http://ftp.nz.debian.org/debian/">ftp.nz.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Poland</td> + <td><a href="http://ftp.pl.debian.org/debian/">ftp.pl.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Portugal</td> + <td><a href="http://ftp.pt.debian.org/debian/">ftp.pt.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Romania</td> + <td><a href="http://ftp.ro.debian.org/debian/">ftp.ro.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Russia</td> + <td><a href="http://ftp.ru.debian.org/debian/">ftp.ru.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Sweden</td> + <td><a href="http://ftp.se.debian.org/debian/">ftp.se.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Slovenia</td> + <td><a href="http://ftp.si.debian.org/debian/">ftp.si.debian.org/debian/</a></td> + <td><small><small>alpha amd64 i386 ia64 m68k powerpc sparc</small></small></td> +</tr> +<tr> + <td>Slovakia</td> + <td><a href="http://ftp.sk.debian.org/debian/">ftp.sk.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Turkey</td> + <td><a href="http://ftp.tr.debian.org/debian/">ftp.tr.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>Taiwan</td> + <td><a href="http://ftp.tw.debian.org/debian/">ftp.tw.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> + <td>United States</td> + <td><a href="http://ftp.us.debian.org/debian/">ftp.us.debian.org/debian/</a></td> + <td><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +</table> +<h2 align="center">Secondary mirrors of the Debian archive</h2> + +<table border="0" align="center"> +<tr> + <th>Host name</th> + <th>FTP</th> + <th>HTTP</th> + <th>Architectures</th> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>AR Argentina</strong></big></td></tr> + +<tr> +<td valign=top>debian.logiclinux.com</td> +<td></td> +<td valign=top><a href="http://debian.logiclinux.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ccc.uba.ar</td> +<td valign=top><a href="ftp://ftp.ccc.uba.ar/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.ccc.uba.ar/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.torredehanoi.org</td> +<td valign=top><a href="ftp://debian.torredehanoi.org/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.torredehanoi.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>AT Austria</strong></big></td></tr> + +<tr> +<td valign=top>ftp.at.debian.org<br> (debian.sil.at)</td> +<td valign=top><a href="ftp://ftp.at.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.at.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>gd.tuwien.ac.at</td> +<td valign=top><a href="ftp://gd.tuwien.ac.at/opsys/linux/debian/">/opsys/linux/debian/</a></td> +<td valign=top><a href="http://gd.tuwien.ac.at/opsys/linux/debian/">/opsys/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mur.at</td> +<td valign=top><a href="ftp://debian.mur.at/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mur.at/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>ftp.tu-graz.ac.at</td> +<td valign=top><a href="ftp://ftp.tu-graz.ac.at/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><a href="http://ftp.tu-graz.ac.at/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.univie.ac.at</td> +<td valign=top><a href="ftp://ftp.univie.ac.at/systems/linux/debian/debian/">/systems/linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.univie.ac.at/systems/linux/debian/debian/">/systems/linux/debian/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.inode.at</td> +<td valign=top><a href="ftp://debian.inode.at/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.inode.at/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>esda.wu-wien.ac.at</td> +<td valign=top><a href="ftp://esda.wu-wien.ac.at/pub/debian/">/pub/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.lagis.at</td> +<td valign=top><a href="ftp://debian.lagis.at/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.lagis.at/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>AU Australia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.au.debian.org<br> (mirror.linux.org.au)</td> +<td valign=top><a href="ftp://ftp.au.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.au.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.aarnet.edu.au</td> +<td valign=top><a href="ftp://mirror.aarnet.edu.au/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.aarnet.edu.au/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.monash.edu.au</td> +<td valign=top><a href="ftp://ftp.monash.edu.au/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://ftp.monash.edu.au/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uwa.edu.au</td> +<td valign=top><a href="ftp://ftp.uwa.edu.au/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uwa.edu.au/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.eftel.com</td> +<td valign=top><a href="ftp://mirror.eftel.com/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.eftel.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.pacific.net.au</td> +<td valign=top><a href="ftp://mirror.pacific.net.au/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.pacific.net.au/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.iinet.net.au</td> +<td valign=top><a href="ftp://ftp.iinet.net.au/debian/debian/">/debian/debian/</a></td> +<td valign=top><a href="http://ftp.iinet.net.au/debian/debian/">/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.optus.net</td> +<td valign=top><a href="ftp://mirror.optus.net/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.optus.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.cse.unsw.edu.au</td> +<td valign=top><a href="ftp://mirror.cse.unsw.edu.au/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.cse.unsw.edu.au/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.3fl.net.au</td> +<td valign=top><a href="ftp://mirror.3fl.net.au/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://mirror.3fl.net.au/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.netspace.net.au</td> +<td valign=top><a href="ftp://ftp.netspace.net.au/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.netspace.net.au/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>BE Belgium</strong></big></td></tr> + +<tr> +<td valign=top>ftp.be.debian.org<br> (ftp.belnet.be)</td> +<td valign=top><a href="ftp://ftp.be.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.be.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.kulnet.kuleuven.ac.be</td> +<td valign=top><a href="ftp://ftp.kulnet.kuleuven.ac.be/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.kulnet.kuleuven.ac.be/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.easynet.be</td> +<td valign=top><a href="ftp://ftp.easynet.be/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.easynet.be/ftp/debian/">/ftp/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debian.skynet.be</td> +<td valign=top><a href="ftp://ftp.debian.skynet.be/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.debian.skynet.be/ftp/debian/">/ftp/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.be.gbxs.net</td> +<td valign=top><a href="ftp://mirror.be.gbxs.net/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.be.gbxs.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>BG Bulgaria</strong></big></td></tr> + +<tr> +<td valign=top>ftp.bg.debian.org<br> (debian.spnet.net)</td> +<td valign=top><a href="ftp://ftp.bg.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.bg.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.ludost.net</td> +<td valign=top><a href="ftp://debian.ludost.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ludost.net/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uni-sofia.bg</td> +<td valign=top><a href="ftp://ftp.uni-sofia.bg/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uni-sofia.bg/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.telecoms.bg</td> +<td valign=top><a href="ftp://debian.telecoms.bg/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.telecoms.bg/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mnet.bg</td> +<td valign=top><a href="ftp://debian.mnet.bg/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mnet.bg/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.networx-bg.com</td> +<td valign=top><a href="ftp://debian.networx-bg.com/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.networx-bg.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>BR Brazil</strong></big></td></tr> + +<tr> +<td valign=top>ftp.br.debian.org<br> (debian.c3sl.ufpr.br)</td> +<td valign=top><a href="ftp://ftp.br.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.br.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.das.ufsc.br</td> +<td valign=top><a href="ftp://debian.das.ufsc.br/pub/debian/">/pub/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>download.unesp.br</td> +<td></td> +<td valign=top><a href="http://download.unesp.br/linux/debian/">/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>sft.if.usp.br</td> +<td></td> +<td valign=top><a href="http://sft.if.usp.br/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>linorg.usp.br</td> +<td valign=top><a href="ftp://linorg.usp.br/debian/">/debian/</a></td> +<td valign=top><a href="http://linorg.usp.br/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>linux.iq.usp.br</td> +<td></td> +<td valign=top><a href="http://linux.iq.usp.br/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.pucpr.br</td> +<td valign=top><a href="ftp://ftp.pucpr.br/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.las.ic.unicamp.br</td> +<td valign=top><a href="ftp://debian.las.ic.unicamp.br/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.las.ic.unicamp.br/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.pop-sc.rnp.br</td> +<td></td> +<td valign=top><a href="http://debian.pop-sc.rnp.br/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>BY Belarus</strong></big></td></tr> + +<tr> +<td valign=top>linux.org.by</td> +<td valign=top><a href="ftp://linux.org.by/debian/">/debian/</a></td> +<td valign=top><a href="http://linux.org.by/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.mgts.by</td> +<td valign=top><a href="ftp://ftp.mgts.by/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.mgts.by/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>CA Canada</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ca.debian.org</td> +<td valign=top><a href="ftp://ftp.ca.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ca.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.yorku.ca</td> +<td></td> +<td valign=top><a href="http://debian.yorku.ca/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp3.nrc.ca</td> +<td valign=top><a href="ftp://ftp3.nrc.ca/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp3.nrc.ca/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>gulus.usherbrooke.ca</td> +<td valign=top><a href="ftp://gulus.usherbrooke.ca/debian/">/debian/</a></td> +<td valign=top><a href="http://gulus.usherbrooke.ca/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.cpsc.ucalgary.ca</td> +<td valign=top><a href="ftp://mirror.cpsc.ucalgary.ca/mirror/debian.org/debian/">/mirror/debian.org/debian/</a></td> +<td valign=top><a href="http://mirror.cpsc.ucalgary.ca/mirror/debian.org/debian/">/mirror/debian.org/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.peer1.net</td> +<td></td> +<td valign=top><a href="http://mirror.peer1.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel i386 mips mipsel powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.rafal.ca</td> +<td valign=top><a href="ftp://debian.mirror.rafal.ca/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirror.rafal.ca/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.savoirfairelinux.net</td> +<td valign=top><a href="ftp://debian.savoirfairelinux.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.savoirfairelinux.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.iweb.ca</td> +<td valign=top><a href="ftp://debian.mirror.iweb.ca/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirror.iweb.ca/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.publicns.net</td> +<td valign=top><a href="ftp://mirror.publicns.net/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://mirror.publicns.net/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>amd64 armel i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.csclub.uwaterloo.ca</td> +<td valign=top><a href="ftp://mirror.csclub.uwaterloo.ca/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.csclub.uwaterloo.ca/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>CH Switzerland</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ch.debian.org<br> (debian.ethz.ch)</td> +<td valign=top><a href="ftp://ftp.ch.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ch.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.switch.ch</td> +<td valign=top><a href="ftp://mirror.switch.ch/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><a href="http://mirror.switch.ch/ftp/mirror/debian/">/ftp/mirror/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.csg.uzh.ch</td> +<td></td> +<td valign=top><a href="http://debian.csg.uzh.ch/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>CL Chile</strong></big></td></tr> + +<tr> +<td valign=top>ftp.cl.debian.org<br> (debian.ciencias.uchile.cl)</td> +<td valign=top><a href="ftp://ftp.cl.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.cl.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.ubiobio.cl</td> +<td></td> +<td valign=top><a href="http://debian.ubiobio.cl/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.utalca.cl</td> +<td></td> +<td valign=top><a href="http://debian.utalca.cl/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.debian.cl</td> +<td></td> +<td valign=top><a href="http://mirror.debian.cl/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.debianchile.cl</td> +<td></td> +<td valign=top><a href="http://mirror.debianchile.cl/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>CN China</strong></big></td></tr> + +<tr> +<td valign=top>mirrors.geekbone.org</td> +<td valign=top><a href="ftp://mirrors.geekbone.org/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.geekbone.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.cn99.com</td> +<td valign=top><a href="ftp://debian.cn99.com/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.cn99.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>www.anheng.com.cn</td> +<td valign=top><a href="ftp://www.anheng.com.cn/debian/">/debian/</a></td> +<td valign=top><a href="http://www.anheng.com.cn/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>CZ Czech Republic</strong></big></td></tr> + +<tr> +<td valign=top>ftp.cz.debian.org<br> (ftp.debian.cz)</td> +<td valign=top><a href="ftp://ftp.cz.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.cz.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.sh.cvut.cz</td> +<td valign=top><a href="ftp://debian.sh.cvut.cz/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.sh.cvut.cz/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.zcu.cz</td> +<td valign=top><a href="ftp://ftp.zcu.cz/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><a href="http://ftp.zcu.cz/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.web4u.cz</td> +<td valign=top><a href="ftp://debian.mirror.web4u.cz/">/</a></td> +<td valign=top><a href="http://debian.mirror.web4u.cz/">/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.cvut.cz</td> +<td valign=top><a href="ftp://ftp.cvut.cz/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.cvut.cz/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>debian.ignum.cz</td> +<td valign=top><a href="ftp://debian.ignum.cz/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ignum.cz/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>DE Germany</strong></big></td></tr> + +<tr> +<td valign=top>ftp.de.debian.org<br> (debian.inf.tu-dresden.de)</td> +<td valign=top><a href="ftp://ftp.de.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.de.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp2.de.debian.org<br> (ftp.rfc822.org)</td> +<td valign=top><a href="ftp://ftp2.de.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp2.de.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.tu-clausthal.de</td> +<td valign=top><a href="ftp://ftp.tu-clausthal.de/pub/linux/debian/">/pub/linux/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 arm armel i386 ia64 m68k mips powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.uni-duisburg-essen.de</td> +<td valign=top><a href="ftp://debian.uni-duisburg-essen.de/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.uni-duisburg-essen.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.freenet.de</td> +<td valign=top><a href="ftp://ftp.freenet.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.freenet.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.informatik.rwth-aachen.de</td> +<td valign=top><a href="ftp://ftp.informatik.rwth-aachen.de/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td valign=top><a href="http://ftp.informatik.rwth-aachen.de/ftp/pub/Linux/debian/">/ftp/pub/Linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp-stud.fht-esslingen.de</td> +<td valign=top><a href="ftp://ftp-stud.fht-esslingen.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp-stud.fht-esslingen.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.stw-bonn.de</td> +<td valign=top><a href="ftp://ftp.stw-bonn.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.stw-bonn.de/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.fu-berlin.de</td> +<td valign=top><a href="ftp://ftp.fu-berlin.de/pub/unix/linux/mirrors/debian/">/pub/unix/linux/mirrors/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.tu-bs.de</td> +<td valign=top><a href="ftp://debian.tu-bs.de/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.tu-bs.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uni-koeln.de</td> +<td valign=top><a href="ftp://ftp.uni-koeln.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uni-koeln.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.mpi-sb.mpg.de</td> +<td valign=top><a href="ftp://ftp.mpi-sb.mpg.de/pub/linux/debian/">/pub/linux/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.tiscali.de</td> +<td valign=top><a href="ftp://ftp.tiscali.de/pub/debian/debian/">/pub/debian/debian/</a></td> +<td valign=top><a href="http://ftp.tiscali.de/pub/debian/debian/">/pub/debian/debian/</a></td> +<td valign=top><small><small>amd64 arm armel hurd-i386 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>ftp.tu-chemnitz.de</td> +<td valign=top><a href="ftp://ftp.tu-chemnitz.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.tu-chemnitz.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uni-kl.de</td> +<td valign=top><a href="ftp://ftp.uni-kl.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uni-kl.de/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uni-bayreuth.de</td> +<td valign=top><a href="ftp://ftp.uni-bayreuth.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uni-bayreuth.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.informatik.hu-berlin.de</td> +<td valign=top><a href="ftp://ftp.informatik.hu-berlin.de/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp5.gwdg.de</td> +<td valign=top><a href="ftp://ftp5.gwdg.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp5.gwdg.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.hosteurope.de</td> +<td valign=top><a href="ftp://ftp.hosteurope.de/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://ftp.hosteurope.de/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.informatik.uni-frankfurt.de</td> +<td valign=top><a href="ftp://ftp.informatik.uni-frankfurt.de/pub/Mirrors/debian.org/debian/">/pub/Mirrors/debian.org/debian/</a></td> +<td valign=top><a href="http://ftp.informatik.uni-frankfurt.de/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.netcologne.de</td> +<td valign=top><a href="ftp://debian.netcologne.de/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.netcologne.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>artfiles.org</td> +<td valign=top><a href="ftp://artfiles.org/debian/">/debian/</a></td> +<td valign=top><a href="http://artfiles.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.intergenia.de</td> +<td></td> +<td valign=top><a href="http://debian.intergenia.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.cruisix.net</td> +<td valign=top><a href="ftp://debian.cruisix.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.cruisix.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.rrzn.uni-hannover.de</td> +<td valign=top><a href="ftp://ftp.rrzn.uni-hannover.de/debian/debian/">/debian/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.charite.de</td> +<td></td> +<td valign=top><a href="http://debian.charite.de/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.plusline.de</td> +<td valign=top><a href="ftp://ftp.plusline.de/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.plusline.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>sinclair.farm.ftbfs.de</td> +<td></td> +<td valign=top><a href="http://sinclair.farm.ftbfs.de/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.halifax.rwth-aachen.de</td> +<td valign=top><a href="ftp://ftp.halifax.rwth-aachen.de/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.halifax.rwth-aachen.de/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>DK Denmark</strong></big></td></tr> + +<tr> +<td valign=top>ftp.dk.debian.org<br> (mirrors.dotsrc.org)</td> +<td valign=top><a href="ftp://ftp.dk.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.dk.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.dkuug.dk</td> +<td valign=top><a href="ftp://ftp.dkuug.dk/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.dkuug.dk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.here.dk</td> +<td valign=top><a href="ftp://mirror.here.dk/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.here.dk/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 mips powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.uni-c.dk</td> +<td></td> +<td valign=top><a href="http://debian.uni-c.dk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.telianet.dk</td> +<td valign=top><a href="ftp://mirrors.telianet.dk/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.telianet.dk/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debianmirror.wwi.dk</td> +<td></td> +<td valign=top><a href="http://debianmirror.wwi.dk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>EE Estonia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ee.debian.org<br> (ftp.aso.ee)</td> +<td valign=top><a href="ftp://ftp.ee.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ee.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>ES Spain</strong></big></td></tr> + +<tr> +<td valign=top>ftp.es.debian.org<br> (ulises.hostalia.com)</td> +<td valign=top><a href="ftp://ftp.es.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.es.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.rediris.es</td> +<td valign=top><a href="ftp://ftp.rediris.es/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.rediris.es/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.cica.es</td> +<td valign=top><a href="ftp://ftp.cica.es/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.cica.es/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.caliu.cat</td> +<td valign=top><a href="ftp://ftp.caliu.cat/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.caliu.cat/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.gva.es</td> +<td valign=top><a href="ftp://ftp.gva.es/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><a href="http://ftp.gva.es/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.gul.uc3m.es</td> +<td valign=top><a href="ftp://ftp.gul.uc3m.es/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.gul.uc3m.es/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.um.es</td> +<td valign=top><a href="ftp://ftp.um.es/mirror/debian/">/mirror/debian/</a></td> +<td></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>jane.uab.cat</td> +<td valign=top><a href="ftp://jane.uab.cat/debian/">/debian/</a></td> +<td valign=top><a href="http://jane.uab.cat/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.udc.es</td> +<td valign=top><a href="ftp://ftp.udc.es/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.udc.es/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.grn.cat</td> +<td valign=top><a href="ftp://debian.grn.cat/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.grn.cat/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.com.es</td> +<td valign=top><a href="ftp://debian.com.es/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.com.es/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>FI Finland</strong></big></td></tr> + +<tr> +<td valign=top>ftp.fi.debian.org<br> (trumpetti.atm.tut.fi)</td> +<td valign=top><a href="ftp://ftp.fi.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.fi.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.funet.fi</td> +<td valign=top><a href="ftp://ftp.funet.fi/pub/linux/mirrors/debian/">/pub/linux/mirrors/debian/</a></td> +<td valign=top><a href="http://ftp.funet.fi/pub/linux/mirrors/debian/">/pub/linux/mirrors/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.jyu.fi</td> +<td valign=top><a href="ftp://ftp.jyu.fi/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.jyu.fi/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 hurd-i386 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.seclan.com</td> +<td valign=top><a href="ftp://ftp.seclan.com/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.seclan.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>FR France</strong></big></td></tr> + +<tr> +<td valign=top>ftp.fr.debian.org<br> (debian.proxad.net)</td> +<td valign=top><a href="ftp://ftp.fr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.fr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp2.fr.debian.org<br> (ftp.oleane.net)</td> +<td valign=top><a href="ftp://ftp2.fr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp2.fr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.iut-bm.univ-fcomte.fr</td> +<td valign=top><a href="ftp://ftp.iut-bm.univ-fcomte.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.iut-bm.univ-fcomte.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.eudil.fr</td> +<td valign=top><a href="ftp://ftp.eudil.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.eudil.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.proxad.net</td> +<td valign=top><a href="ftp://ftp.proxad.net/mirrors/ftp.debian.org/">/mirrors/ftp.debian.org/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.lip6.fr</td> +<td valign=top><a href="ftp://ftp.lip6.fr/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><a href="http://ftp.lip6.fr/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.ens-cachan.fr</td> +<td valign=top><a href="ftp://debian.ens-cachan.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ens-cachan.fr/ftp/debian/">/ftp/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.u-picardie.fr</td> +<td valign=top><a href="ftp://ftp.u-picardie.fr/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><a href="http://ftp.u-picardie.fr/mirror/debian/">/mirror/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirrors.easynet.fr</td> +<td valign=top><a href="ftp://debian.mirrors.easynet.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirrors.easynet.fr/">/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.u-strasbg.fr</td> +<td valign=top><a href="ftp://ftp.u-strasbg.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.u-strasbg.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 hurd-i386 i386 ia64 m68k powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.cict.fr</td> +<td valign=top><a href="ftp://debian.cict.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.cict.fr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm armel hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>mir1.ovh.net</td> +<td valign=top><a href="ftp://mir1.ovh.net/debian/">/debian/</a></td> +<td valign=top><a href="http://mir1.ovh.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mir2.ovh.net</td> +<td></td> +<td valign=top><a href="http://mir2.ovh.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.nerim.net</td> +<td valign=top><a href="ftp://ftp.nerim.net/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.nerim.net/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.crihan.fr</td> +<td valign=top><a href="ftp://ftp.crihan.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.crihan.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mines.inpl-nancy.fr</td> +<td valign=top><a href="ftp://debian.mines.inpl-nancy.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mines.inpl-nancy.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debian.ikoula.com</td> +<td valign=top><a href="ftp://ftp.debian.ikoula.com/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>webb.ens-cachan.fr</td> +<td valign=top><a href="ftp://webb.ens-cachan.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://webb.ens-cachan.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.ircam.fr</td> +<td valign=top><a href="ftp://mirrors.ircam.fr/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://mirrors.ircam.fr/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.inra.fr</td> +<td valign=top><a href="ftp://debian.mirror.inra.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirror.inra.fr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm armel i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.med.univ-tours.fr</td> +<td valign=top><a href="ftp://debian.med.univ-tours.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.med.univ-tours.fr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.univ-pau.fr</td> +<td valign=top><a href="ftp://ftp.univ-pau.fr/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><a href="http://ftp.univ-pau.fr/linux/mirrors/debian/">/linux/mirrors/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.univ-nantes.fr</td> +<td valign=top><a href="ftp://ftp.univ-nantes.fr/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.compuscene.org</td> +<td></td> +<td valign=top><a href="http://mirrors.compuscene.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.revolsys.fr</td> +<td valign=top><a href="ftp://debian.revolsys.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.revolsys.fr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.univ-reims.fr</td> +<td valign=top><a href="ftp://debian.univ-reims.fr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.univ-reims.fr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>GB Great Britain</strong></big></td></tr> + +<tr> +<td valign=top>ftp.uk.debian.org<br> (debian.hands.com)</td> +<td valign=top><a href="ftp://ftp.uk.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uk.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.man.ac.uk</td> +<td></td> +<td valign=top><a href="http://debian.man.ac.uk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>www.mirrorservice.org</td> +<td valign=top><a href="ftp://www.mirrorservice.org/sites/ftp.debian.org/debian/">/sites/ftp.debian.org/debian/</a></td> +<td valign=top><a href="http://www.mirrorservice.org/sites/ftp.debian.org/debian/">/sites/ftp.debian.org/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ticklers.org</td> +<td valign=top><a href="ftp://ftp.ticklers.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ticklers.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.virginmedia.com</td> +<td valign=top><a href="ftp://debian.virginmedia.com/mirrors/ftp.debian.org">/mirrors/ftp.debian.org</a></td> +<td valign=top><a href="http://debian.virginmedia.com/">/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.positive-internet.com</td> +<td valign=top><a href="ftp://mirror.positive-internet.com/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.positive-internet.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hppa i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>the.earth.li</td> +<td valign=top><a href="ftp://the.earth.li/debian/">/debian/</a></td> +<td valign=top><a href="http://the.earth.li/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>ukdebian.mirror.anlx.net</td> +<td valign=top><a href="ftp://ukdebian.mirror.anlx.net/debian/">/debian/</a></td> +<td valign=top><a href="http://ukdebian.mirror.anlx.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.ox.ac.uk</td> +<td valign=top><a href="ftp://mirror.ox.ac.uk/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.ox.ac.uk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.zetnet.co.uk</td> +<td valign=top><a href="ftp://debian.zetnet.co.uk/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.zetnet.co.uk/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 mipsel</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>GE Georgia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ifg.gtu.ge</td> +<td valign=top><a href="ftp://ftp.ifg.gtu.ge/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>GR Greece</strong></big></td></tr> + +<tr> +<td valign=top>ftp.gr.debian.org<br> (ftp.ntua.gr)</td> +<td valign=top><a href="ftp://ftp.gr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.gr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.otenet.gr</td> +<td valign=top><a href="ftp://debian.otenet.gr/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://debian.otenet.gr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.duth.gr</td> +<td valign=top><a href="ftp://ftp.duth.gr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.duth.gr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.softnet.tuc.gr</td> +<td valign=top><a href="ftp://ftp.softnet.tuc.gr/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://ftp.softnet.tuc.gr/ftp/linux/debian/">/ftp/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.cc.uoc.gr</td> +<td valign=top><a href="ftp://ftp.cc.uoc.gr/mirrors/linux/debian/">/mirrors/linux/debian/</a></td> +<td valign=top><a href="http://ftp.cc.uoc.gr/mirrors/linux/debian/">/mirrors/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>HK Hong Kong</strong></big></td></tr> + +<tr> +<td valign=top>ftp.hk.debian.org</td> +<td valign=top><a href="ftp://ftp.hk.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.hk.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>www.zentek-international.com</td> +<td></td> +<td valign=top><a href="http://www.zentek-international.com/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>HR Croatia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.hr.debian.org<br> (debian.carnet.hr)</td> +<td valign=top><a href="ftp://ftp.hr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.hr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.irb.hr</td> +<td valign=top><a href="ftp://ftp.irb.hr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.irb.hr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.carnet.hr</td> +<td valign=top><a href="ftp://ftp.carnet.hr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.carnet.hr/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.iskon.hr</td> +<td valign=top><a href="ftp://debian.iskon.hr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.iskon.hr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64 s390</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>HU Hungary</strong></big></td></tr> + +<tr> +<td valign=top>ftp.hu.debian.org<br> (ftp.fsn.hu)</td> +<td valign=top><a href="ftp://ftp.hu.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.hu.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.kfki.hu</td> +<td valign=top><a href="ftp://ftp.kfki.hu/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://ftp.kfki.hu/linux/debian/">/linux/debian/</a></td> +<td valign=top><small><small>alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.bme.hu</td> +<td valign=top><a href="ftp://ftp.bme.hu/OS/Linux/dist/debian/">/OS/Linux/dist/debian/</a></td> +<td valign=top><a href="http://ftp.bme.hu/OS/Linux/dist/debian/">/OS/Linux/dist/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirrors.crysys.hu</td> +<td valign=top><a href="ftp://debian.mirrors.crysys.hu/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirrors.crysys.hu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.sth.sze.hu</td> +<td valign=top><a href="ftp://debian.sth.sze.hu/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.sth.sze.hu/">/</a></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>ID Indonesia</strong></big></td></tr> + +<tr> +<td valign=top>kebo.vlsm.org</td> +<td valign=top><a href="ftp://kebo.vlsm.org/debian/">/debian/</a></td> +<td valign=top><a href="http://kebo.vlsm.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.indika.net.id</td> +<td></td> +<td valign=top><a href="http://debian.indika.net.id/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>IE Ireland</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ie.debian.org<br> (debian.heanet.ie)</td> +<td valign=top><a href="ftp://ftp.ie.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ie.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.esat.net</td> +<td valign=top><a href="ftp://ftp.esat.net/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://ftp.esat.net/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>IL Israel</strong></big></td></tr> + +<tr> +<td valign=top>debian.co.il</td> +<td></td> +<td valign=top><a href="http://debian.co.il/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.isoc.org.il</td> +<td></td> +<td valign=top><a href="http://mirror.isoc.org.il/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>IN India</strong></big></td></tr> + +<tr> +<td valign=top>ftp.iitm.ac.in</td> +<td valign=top><a href="ftp://ftp.iitm.ac.in/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.iitm.ac.in/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>IS Iceland</strong></big></td></tr> + +<tr> +<td valign=top>ftp.is.debian.org<br> (ftp.rhnet.is)</td> +<td valign=top><a href="ftp://ftp.is.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.is.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>IT Italy</strong></big></td></tr> + +<tr> +<td valign=top>ftp.it.debian.org<br> (ftp.bofh.it)</td> +<td valign=top><a href="ftp://ftp.it.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.it.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>giano.com.dist.unige.it</td> +<td valign=top><a href="ftp://giano.com.dist.unige.it/debian/">/debian/</a></td> +<td valign=top><a href="http://giano.com.dist.unige.it/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm armel i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.bononia.it</td> +<td valign=top><a href="ftp://ftp.bononia.it/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.bononia.it/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>freedom.dicea.unifi.it</td> +<td valign=top><a href="ftp://freedom.dicea.unifi.it/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://freedom.dicea.unifi.it/ftp/pub/linux/debian/">/ftp/pub/linux/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.eutelia.it</td> +<td valign=top><a href="ftp://ftp.eutelia.it/pub/Debian_Mirror/">/pub/Debian_Mirror/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mi.mirror.garr.it</td> +<td valign=top><a href="ftp://mi.mirror.garr.it/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><a href="http://mi.mirror.garr.it/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.fastweb.it</td> +<td valign=top><a href="ftp://debian.fastweb.it/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.fastweb.it/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.unina.it</td> +<td valign=top><a href="ftp://ftp.unina.it/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><a href="http://ftp.unina.it/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.fastbull.org</td> +<td valign=top><a href="ftp://debian.fastbull.org/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.fastbull.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.dynamica.it</td> +<td valign=top><a href="ftp://debian.dynamica.it/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.dynamica.it/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.units.it</td> +<td></td> +<td valign=top><a href="http://mirror.units.it/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>JP Japan</strong></big></td></tr> + +<tr> +<td valign=top>ftp2.jp.debian.org<br> (ftp.debian.or.jp)</td> +<td valign=top><a href="ftp://ftp2.jp.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp2.jp.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.jp.debian.org<br> (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)</td> +<td></td> +<td valign=top><a href="http://ftp.jp.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.nara.wide.ad.jp</td> +<td valign=top><a href="ftp://ftp.nara.wide.ad.jp/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.nara.wide.ad.jp/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ring.asahi-net.or.jp</td> +<td valign=top><a href="ftp://ring.asahi-net.or.jp/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://ring.asahi-net.or.jp/archives/linux/debian/debian/">/archives/linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.dti.ad.jp</td> +<td valign=top><a href="ftp://ftp.dti.ad.jp/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td valign=top><a href="http://ftp.dti.ad.jp/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>dennou-k.gfd-dennou.org</td> +<td valign=top><a href="ftp://dennou-k.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><a href="http://dennou-k.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>dennou-q.gfd-dennou.org</td> +<td valign=top><a href="ftp://dennou-q.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><a href="http://dennou-q.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>sb.itc.u-tokyo.ac.jp</td> +<td valign=top><a href="ftp://sb.itc.u-tokyo.ac.jp/DEBIAN/">/DEBIAN/</a></td> +<td valign=top><a href="http://sb.itc.u-tokyo.ac.jp/DEBIAN/">/DEBIAN/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.riken.jp</td> +<td valign=top><a href="ftp://ftp.riken.jp/Linux/debian/debian/">/Linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.riken.jp/Linux/debian/debian/">/Linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.shimpinomori.net</td> +<td></td> +<td valign=top><a href="http://debian.shimpinomori.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>www.ring.gr.jp</td> +<td valign=top><a href="ftp://www.ring.gr.jp/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://www.ring.gr.jp/archives/linux/debian/debian/">/archives/linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.jaist.ac.jp</td> +<td valign=top><a href="ftp://ftp.jaist.ac.jp/pub/Linux/Debian/">/pub/Linux/Debian/</a></td> +<td valign=top><a href="http://ftp.jaist.ac.jp/pub/Linux/Debian/">/pub/Linux/Debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>www.cohsoft.com</td> +<td></td> +<td valign=top><a href="http://www.cohsoft.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>dennou-h.gfd-dennou.org</td> +<td valign=top><a href="ftp://dennou-h.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><a href="http://dennou-h.gfd-dennou.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>KR Korea</strong></big></td></tr> + +<tr> +<td valign=top>ftp.kr.debian.org<br> (ftp.kaist.ac.kr)</td> +<td valign=top><a href="ftp://ftp.kr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.kr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.daum.net</td> +<td valign=top><a href="ftp://ftp.daum.net/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.daum.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>LT Lithuania</strong></big></td></tr> + +<tr> +<td valign=top>ameba.sc-uni.ktu.lt</td> +<td valign=top><a href="ftp://ameba.sc-uni.ktu.lt/debian/">/debian/</a></td> +<td valign=top><a href="http://ameba.sc-uni.ktu.lt/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.balt.net</td> +<td valign=top><a href="ftp://debian.balt.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.balt.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm armel i386 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>LV Latvia</strong></big></td></tr> + +<tr> +<td valign=top>koyanet.lv</td> +<td valign=top><a href="ftp://koyanet.lv/debian/">/debian/</a></td> +<td valign=top><a href="http://koyanet.lv/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>MT Malta</strong></big></td></tr> + +<tr> +<td valign=top>debian.eng.um.edu.mt</td> +<td></td> +<td valign=top><a href="http://debian.eng.um.edu.mt/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>MX Mexico</strong></big></td></tr> + +<tr> +<td valign=top>ftp.mx.debian.org<br> (debian.unam.mx)</td> +<td valign=top><a href="ftp://ftp.mx.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.mx.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mmc.igeofcu.unam.mx</td> +<td></td> +<td valign=top><a href="http://mmc.igeofcu.unam.mx/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>NC New Caledonia</strong></big></td></tr> + +<tr> +<td valign=top>debian.nautile.nc</td> +<td valign=top><a href="ftp://debian.nautile.nc/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.nautile.nc/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>NI Nicaragua</strong></big></td></tr> + +<tr> +<td valign=top>debian.uni.edu.ni</td> +<td></td> +<td valign=top><a href="http://debian.uni.edu.ni/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>NL Netherlands</strong></big></td></tr> + +<tr> +<td valign=top>ftp.nl.debian.org<br> (ftp.snt.utwente.nl)</td> +<td valign=top><a href="ftp://ftp.nl.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.nl.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.nluug.nl</td> +<td valign=top><a href="ftp://ftp.nluug.nl/pub/os/Linux/distr/debian/">/pub/os/Linux/distr/debian/</a></td> +<td valign=top><a href="http://ftp.nluug.nl/pub/os/Linux/distr/debian/">/pub/os/Linux/distr/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.surfnet.nl</td> +<td valign=top><a href="ftp://ftp.surfnet.nl/pub/os/Linux/distr/debian/">/pub/os/Linux/distr/debian/</a></td> +<td valign=top><a href="http://ftp.surfnet.nl/os/Linux/distr/debian/">/os/Linux/distr/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debian.nl</td> +<td valign=top><a href="ftp://ftp.debian.nl/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.debian.nl/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.tiscali.nl</td> +<td valign=top><a href="ftp://ftp.tiscali.nl/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><a href="http://ftp.tiscali.nl/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>NO Norway</strong></big></td></tr> + +<tr> +<td valign=top>ftp.no.debian.org<br> (ftp.uninett.no)</td> +<td valign=top><a href="ftp://ftp.no.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.no.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>NZ New Zealand</strong></big></td></tr> + +<tr> +<td valign=top>ftp.nz.debian.org<br> (ftp.citylink.co.nz)</td> +<td valign=top><a href="ftp://ftp.nz.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.nz.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.ihug.co.nz</td> +<td valign=top><a href="ftp://debian.ihug.co.nz/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ihug.co.nz/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>PF French Polynesia</strong></big></td></tr> + +<tr> +<td valign=top>repository.linux.pf</td> +<td valign=top><a href="ftp://repository.linux.pf/debian/">/debian/</a></td> +<td valign=top><a href="http://repository.linux.pf/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>PL Poland</strong></big></td></tr> + +<tr> +<td valign=top>ftp.pl.debian.org<br> (ftp.task.gda.pl)</td> +<td valign=top><a href="ftp://ftp.pl.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.pl.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.icm.edu.pl</td> +<td valign=top><a href="ftp://ftp.icm.edu.pl/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td valign=top><a href="http://ftp.icm.edu.pl/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 hurd-i386 i386 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.man.szczecin.pl</td> +<td valign=top><a href="ftp://ftp.man.szczecin.pl/pub/Linux/debian/">/pub/Linux/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.vectranet.pl</td> +<td valign=top><a href="ftp://ftp.vectranet.pl/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.vectranet.pl/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.pwr.wroc.pl</td> +<td valign=top><a href="ftp://ftp.pwr.wroc.pl/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.pwr.wroc.pl/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.man.poznan.pl</td> +<td valign=top><a href="ftp://ftp.man.poznan.pl/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.man.poznan.pl/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>piotrkosoft.net</td> +<td valign=top><a href="ftp://piotrkosoft.net/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><a href="http://piotrkosoft.net/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>PT Portugal</strong></big></td></tr> + +<tr> +<td valign=top>ftp.pt.debian.org<br> (ftp.uevora.pt)</td> +<td valign=top><a href="ftp://ftp.pt.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.pt.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.eq.uc.pt</td> +<td valign=top><a href="ftp://ftp.eq.uc.pt/pub/software/Linux/debian/">/pub/software/Linux/debian/</a></td> +<td valign=top><a href="http://ftp.eq.uc.pt/software/Linux/debian/">/software/Linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.ua.pt</td> +<td valign=top><a href="ftp://debian.ua.pt/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ua.pt/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.linux.pt</td> +<td valign=top><a href="ftp://ftp.linux.pt/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><a href="http://ftp.linux.pt/pub/mirrors/debian/">/pub/mirrors/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.telepac.pt</td> +<td valign=top><a href="ftp://ftp.telepac.pt/pub/debian/">/pub/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.nfsi.pt</td> +<td valign=top><a href="ftp://mirrors.nfsi.pt/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://mirrors.nfsi.pt/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>neacm.fe.up.pt</td> +<td valign=top><a href="ftp://neacm.fe.up.pt/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://neacm.fe.up.pt/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>cesium.di.uminho.pt</td> +<td valign=top><a href="ftp://cesium.di.uminho.pt/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://cesium.di.uminho.pt/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.netvisao.pt</td> +<td valign=top><a href="ftp://debian.netvisao.pt/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.netvisao.pt/">/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.dcc.fc.up.pt</td> +<td></td> +<td valign=top><a href="http://debian.dcc.fc.up.pt/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.sim.ul.pt</td> +<td valign=top><a href="ftp://mirror.sim.ul.pt/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.sim.ul.pt/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>RO Romania</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ro.debian.org<br> (ftp.iasi.roedu.net)</td> +<td valign=top><a href="ftp://ftp.ro.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ro.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.lug.ro</td> +<td valign=top><a href="ftp://ftp.lug.ro/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.lug.ro/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.mikesnet.ro</td> +<td valign=top><a href="ftp://ftp.mikesnet.ro/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.mikesnet.ro/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 mips mipsel</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>RU Russia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.ru.debian.org<br> (ftp.chg.ru)</td> +<td valign=top><a href="ftp://ftp.ru.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ru.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.nsu.ru</td> +<td valign=top><a href="ftp://debian.nsu.ru/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.nsu.ru/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.psn.ru</td> +<td valign=top><a href="ftp://ftp.psn.ru/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.psn.ru/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.corbina.net</td> +<td valign=top><a href="ftp://ftp.corbina.net/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>ftp.mipt.ru</td> +<td valign=top><a href="ftp://ftp.mipt.ru/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.yandex.ru</td> +<td valign=top><a href="ftp://mirror.yandex.ru/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.yandex.ru/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debian.chuvsu.ru</td> +<td valign=top><a href="ftp://ftp.debian.chuvsu.ru/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.debian.chuvsu.ru/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>SE Sweden</strong></big></td></tr> + +<tr> +<td valign=top>ftp.se.debian.org<br> (ftp.acc.umu.se)</td> +<td valign=top><a href="ftp://ftp.se.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.se.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.sunet.se</td> +<td valign=top><a href="ftp://ftp.sunet.se/pub/Linux/distributions/debian/">/pub/Linux/distributions/debian/</a></td> +<td valign=top><a href="http://ftp.sunet.se/pub/Linux/distributions/debian/">/pub/Linux/distributions/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.port80.se</td> +<td valign=top><a href="ftp://ftp.port80.se/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.port80.se/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ds.karen.hj.se</td> +<td valign=top><a href="ftp://ftp.ds.karen.hj.se/pub/os/linux/debian/">/pub/os/linux/debian/</a></td> +<td valign=top><a href="http://ftp.ds.karen.hj.se/pub/os/linux/debian/">/pub/os/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.lth.se</td> +<td valign=top><a href="ftp://debian.lth.se/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.lth.se/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.df.lth.se</td> +<td valign=top><a href="ftp://ftp.df.lth.se/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>kalle.csb.ki.se</td> +<td></td> +<td valign=top><a href="http://kalle.csb.ki.se/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>SG Singapore</strong></big></td></tr> + +<tr> +<td valign=top>mirror.nus.edu.sg</td> +<td valign=top><a href="ftp://mirror.nus.edu.sg/pub/Debian/">/pub/Debian/</a></td> +<td valign=top><a href="http://mirror.nus.edu.sg/Debian/">/Debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>SI Slovenia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.si.debian.org<br> (ftp.camtp.uni-mb.si)</td> +<td valign=top><a href="ftp://ftp.si.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.si.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 ia64 m68k powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.arnes.si</td> +<td valign=top><a href="ftp://ftp.arnes.si/packages/debian/">/packages/debian/</a></td> +<td valign=top><a href="http://ftp.arnes.si/pub/packages/debian/">/pub/packages/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.prunk.si</td> +<td valign=top><a href="ftp://debian.prunk.si/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.prunk.si/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>SK Slovakia</strong></big></td></tr> + +<tr> +<td valign=top>ftp.sk.debian.org<br> (ftp.tuke.sk)</td> +<td valign=top><a href="ftp://ftp.sk.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.sk.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.ynet.sk</td> +<td></td> +<td valign=top><a href="http://mirror.ynet.sk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debian.sk</td> +<td valign=top><a href="ftp://ftp.debian.sk/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.debian.sk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.antik.sk</td> +<td valign=top><a href="ftp://ftp.antik.sk/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.antik.sk/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>SV El Salvador</strong></big></td></tr> + +<tr> +<td valign=top>debian.ues.edu.sv</td> +<td valign=top><a href="ftp://debian.ues.edu.sv/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.ues.edu.sv/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>TH Thailand</strong></big></td></tr> + +<tr> +<td valign=top>ftp.coe.psu.ac.th</td> +<td valign=top><a href="ftp://ftp.coe.psu.ac.th/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.coe.psu.ac.th/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.thaios.net</td> +<td></td> +<td valign=top><a href="http://ftp.thaios.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.debianclub.org</td> +<td valign=top><a href="ftp://ftp.debianclub.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.debianclub.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>TR Turkey</strong></big></td></tr> + +<tr> +<td valign=top>ftp.tr.debian.org<br> (debian.ankara.edu.tr)</td> +<td valign=top><a href="ftp://ftp.tr.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.tr.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.linux.org.tr</td> +<td valign=top><a href="ftp://ftp.linux.org.tr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.linux.org.tr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>godel.cs.bilgi.edu.tr</td> +<td valign=top><a href="ftp://godel.cs.bilgi.edu.tr/debian/">/debian/</a></td> +<td valign=top><a href="http://godel.cs.bilgi.edu.tr/debian/">/debian/</a></td> +<td valign=top><small><small>hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.eso-es.net</td> +<td></td> +<td valign=top><a href="http://debian.eso-es.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.comu.edu.tr</td> +<td valign=top><a href="ftp://debian.comu.edu.tr/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.comu.edu.tr/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.metu.edu.tr</td> +<td valign=top><a href="ftp://ftp.metu.edu.tr/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.metu.edu.tr/debian/">/debian/</a></td> +<td valign=top><small><small>ALL alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>TW Taiwan</strong></big></td></tr> + +<tr> +<td valign=top>ftp.tw.debian.org<br> (debian.linux.org.tw)</td> +<td valign=top><a href="ftp://ftp.tw.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.tw.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.csie.ntu.edu.tw</td> +<td valign=top><a href="ftp://debian.csie.ntu.edu.tw/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://debian.csie.ntu.edu.tw/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.twaren.net</td> +<td valign=top><a href="ftp://ftp.twaren.net/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.twaren.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>opensource.nchc.org.tw</td> +<td valign=top><a href="ftp://opensource.nchc.org.tw/debian/">/debian/</a></td> +<td valign=top><a href="http://opensource.nchc.org.tw/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.isu.edu.tw</td> +<td valign=top><a href="ftp://ftp.isu.edu.tw/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.isu.edu.tw/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.nctu.edu.tw</td> +<td valign=top><a href="ftp://debian.nctu.edu.tw/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.nctu.edu.tw/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.nttu.edu.tw</td> +<td valign=top><a href="ftp://mirror.nttu.edu.tw/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.nttu.edu.tw/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.csie.nctu.edu.tw</td> +<td valign=top><a href="ftp://debian.csie.nctu.edu.tw/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.csie.nctu.edu.tw/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ncnu.edu.tw</td> +<td valign=top><a href="ftp://ftp.ncnu.edu.tw/Linux/Debian/debian/">/Linux/Debian/debian/</a></td> +<td valign=top><a href="http://ftp.ncnu.edu.tw/Linux/Debian/debian/">/Linux/Debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.cse.yzu.edu.tw</td> +<td valign=top><a href="ftp://ftp.cse.yzu.edu.tw/pub/Linux/debian/debian/">/pub/Linux/debian/debian/</a></td> +<td valign=top><a href="http://ftp.cse.yzu.edu.tw/pub/Linux/debian/debian/">/pub/Linux/debian/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>UA Ukraine</strong></big></td></tr> + +<tr> +<td valign=top>debian.osdn.org.ua</td> +<td valign=top><a href="ftp://debian.osdn.org.ua/pub/Debian/debian/">/pub/Debian/debian/</a></td> +<td valign=top><a href="http://debian.osdn.org.ua/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.org.ua</td> +<td valign=top><a href="ftp://debian.org.ua/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.org.ua/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.3logic.net</td> +<td valign=top><a href="ftp://ftp.3logic.net/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.mirohost.net</td> +<td valign=top><a href="ftp://mirror.mirohost.net/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.mirohost.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp2.debian.org.ua</td> +<td valign=top><a href="ftp://ftp2.debian.org.ua/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp2.debian.org.ua/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>US United States</strong></big></td></tr> + +<tr> +<td valign=top>ftp.us.debian.org<br> (ftp.egr.msu.edu, mirrors.kernel.org, debian.osuosl.org, debian.lcs.mit.edu)</td> +<td valign=top><a href="ftp://ftp.us.debian.org/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.us.debian.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.gtlib.gatech.edu</td> +<td valign=top><a href="ftp://ftp.gtlib.gatech.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.gtlib.gatech.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.egr.msu.edu</td> +<td valign=top><a href="ftp://ftp.egr.msu.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.egr.msu.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>distro.ibiblio.org</td> +<td valign=top><a href="ftp://distro.ibiblio.org/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><a href="http://distro.ibiblio.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386 ia64</small></small></td> +</tr> +<tr> +<td valign=top>ftp-mirror.internap.com</td> +<td valign=top><a href="ftp://ftp-mirror.internap.com/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp-mirror.internap.com/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.cerias.purdue.edu</td> +<td valign=top><a href="ftp://ftp.cerias.purdue.edu/pub/os/debian/">/pub/os/debian/</a></td> +<td valign=top><a href="http://ftp.cerias.purdue.edu/pub/os/debian/">/pub/os/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.cs.wisc.edu</td> +<td valign=top><a href="ftp://mirror.cs.wisc.edu/pub/mirrors/linux/debian/">/pub/mirrors/linux/debian/</a></td> +<td valign=top><a href="http://mirror.cs.wisc.edu/pub/mirrors/linux/debian/">/pub/mirrors/linux/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uwsg.indiana.edu</td> +<td valign=top><a href="ftp://ftp.uwsg.indiana.edu/linux/debian/">/linux/debian/</a></td> +<td valign=top><a href="http://ftp.uwsg.indiana.edu/linux/debian/">/linux/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>natasha.stmarytx.edu</td> +<td valign=top><a href="ftp://natasha.stmarytx.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://natasha.stmarytx.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ndlug.nd.edu</td> +<td valign=top><a href="ftp://ftp.ndlug.nd.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ndlug.nd.edu/mirrors/debian/">/mirrors/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.uchicago.edu</td> +<td valign=top><a href="ftp://debian.uchicago.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.uchicago.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>carroll.aset.psu.edu</td> +<td valign=top><a href="ftp://carroll.aset.psu.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><a href="http://carroll.aset.psu.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>gladiator.real-time.com</td> +<td valign=top><a href="ftp://gladiator.real-time.com/linux/debian/">/linux/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.kernel.org</td> +<td valign=top><a href="ftp://mirrors.kernel.org/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.kernel.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.xmission.com</td> +<td valign=top><a href="ftp://mirrors.xmission.com/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.xmission.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.lug.udel.edu</td> +<td valign=top><a href="ftp://ftp.lug.udel.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.lug.udel.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.lcs.mit.edu</td> +<td valign=top><a href="ftp://debian.lcs.mit.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.lcs.mit.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>linux.csua.berkeley.edu</td> +<td></td> +<td valign=top><a href="http://linux.csua.berkeley.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.silug.org</td> +<td valign=top><a href="ftp://ftp.silug.org/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.silug.org/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa i386 mips mipsel powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.secsup.org</td> +<td valign=top><a href="ftp://debian.secsup.org/pub/linux/debian/">/pub/linux/debian/</a></td> +<td valign=top><a href="http://debian.secsup.org/">/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.osuosl.org</td> +<td valign=top><a href="ftp://debian.osuosl.org/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.osuosl.org/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.anl.gov</td> +<td valign=top><a href="ftp://mirror.anl.gov/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://mirror.anl.gov/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>sluglug.ucsc.edu</td> +<td></td> +<td valign=top><a href="http://sluglug.ucsc.edu/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.geeks.org</td> +<td valign=top><a href="ftp://mirrors.geeks.org/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.geeks.org/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.usc.edu</td> +<td valign=top><a href="ftp://mirrors.usc.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><a href="http://mirrors.usc.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirrors.pair.com</td> +<td valign=top><a href="ftp://debian.mirrors.pair.com/">/</a></td> +<td valign=top><a href="http://debian.mirrors.pair.com/">/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>lug.mtu.edu</td> +<td valign=top><a href="ftp://lug.mtu.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://lug.mtu.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 hppa i386 mips mipsel powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirrors.tds.net</td> +<td valign=top><a href="ftp://debian.mirrors.tds.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirrors.tds.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.cites.uiuc.edu</td> +<td valign=top><a href="ftp://debian.cites.uiuc.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://debian.cites.uiuc.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>amd64 hurd-i386 i386 ia64 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.tummy.com</td> +<td valign=top><a href="ftp://mirrors.tummy.com/debian/">/debian/</a></td> +<td valign=top><a href="http://mirrors.tummy.com/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.frontiernet.net</td> +<td valign=top><a href="ftp://debian.mirror.frontiernet.net/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirror.frontiernet.net/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>cudlug.cudenver.edu</td> +<td valign=top><a href="ftp://cudlug.cudenver.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://cudlug.cudenver.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>bigmirror.crossbowproject.net</td> +<td valign=top><a href="ftp://bigmirror.crossbowproject.net/pub/debian/">/pub/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha arm armel hppa i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.cc.columbia.edu</td> +<td valign=top><a href="ftp://mirror.cc.columbia.edu/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><a href="http://mirror.cc.columbia.edu/pub/linux/debian/debian/">/pub/linux/debian/debian/</a></td> +<td valign=top><small><small>amd64 i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.grokthis.net</td> +<td valign=top><a href="ftp://ftp.grokthis.net/mirrors/debian/">/mirrors/debian/</a></td> +<td></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.xenir.com</td> +<td></td> +<td valign=top><a href="http://mirrors.xenir.com/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 arm armel i386 powerpc</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirrors.easynews.com</td> +<td></td> +<td valign=top><a href="http://debian.mirrors.easynews.com/linux/debian/">/linux/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.ams.sunysb.edu</td> +<td></td> +<td valign=top><a href="http://debian.ams.sunysb.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirrors.acm.jhu.edu</td> +<td></td> +<td valign=top><a href="http://mirrors.acm.jhu.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.uga.edu</td> +<td valign=top><a href="ftp://ftp.uga.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.uga.edu/debian/">/debian/</a></td> +<td valign=top><small><small>i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.steadfast.net</td> +<td></td> +<td valign=top><a href="http://mirror.steadfast.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>ftp.utexas.edu</td> +<td valign=top><a href="ftp://ftp.utexas.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><a href="http://ftp.utexas.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>mirror.fdcservers.net</td> +<td valign=top><a href="ftp://mirror.fdcservers.net/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.fdcservers.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.rit.edu</td> +<td valign=top><a href="ftp://mirror.rit.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.rit.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel i386 powerpc sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.corenetworks.net</td> +<td></td> +<td valign=top><a href="http://debian.corenetworks.net/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>mirror.its.uidaho.edu</td> +<td valign=top><a href="ftp://mirror.its.uidaho.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://mirror.its.uidaho.edu/pub/debian/">/pub/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>debian.cs.binghamton.edu</td> +<td valign=top><a href="ftp://debian.cs.binghamton.edu/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.cs.binghamton.edu/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>UZ Uzbekistan</strong></big></td></tr> + +<tr> +<td valign=top>debian.snet.uz</td> +<td></td> +<td valign=top><a href="http://debian.snet.uz/debian/">/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.stream.uz</td> +<td valign=top><a href="ftp://debian.stream.uz/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.stream.uz/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>VE Venezuela</strong></big></td></tr> + +<tr> +<td valign=top>debian.unesr.edu.ve</td> +<td></td> +<td valign=top><a href="http://debian.unesr.edu.ve/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.ula.ve</td> +<td valign=top><a href="ftp://ftp.ula.ve/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.ula.ve/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 i386 ia64 powerpc sparc</small></small></td> +</tr> + +<tr><td colspan=4><hr size=1></td></tr> +<tr><td colspan=4><big><strong>ZA South Africa</strong></big></td></tr> + +<tr> +<td valign=top>ftp.sun.ac.za</td> +<td valign=top><a href="ftp://ftp.sun.ac.za/debian/">/debian/</a></td> +<td valign=top><a href="http://ftp.sun.ac.za/ftp/debian/">/ftp/debian/</a></td> +<td valign=top><small><small>amd64 i386</small></small></td> +</tr> +<tr> +<td valign=top>debian.mirror.ac.za</td> +<td valign=top><a href="ftp://debian.mirror.ac.za/debian/">/debian/</a></td> +<td valign=top><a href="http://debian.mirror.ac.za/debian/">/debian/</a></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +<tr> +<td valign=top>ftp.is.co.za</td> +<td valign=top><a href="ftp://ftp.is.co.za/debian/">/debian/</a></td> +<td></td> +<td valign=top><small><small>alpha amd64 arm armel hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</small></small></td> +</tr> +</table> +<hr> +<table border="0" width="100%"><tr> + <td align="left"><small>Last modified: Sun Nov 2 19:52:19 2008</small></td> + <td align="right"><small>Number of sites listed: 417</small></td> +</tr></table> +</body> +</html> diff --git a/includes/lenny/install/README.mirrors.txt b/includes/lenny/install/README.mirrors.txt new file mode 100644 index 0000000..eba36b7 --- /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.<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 + --------------------------- + + 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 0000000..64ca8c8 --- /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 0000000..70f471d --- /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 0000000..6e141d2 --- /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 0000000..cdbeb2b --- /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 Binary files differnew file mode 100644 index 0000000..2a2245e --- /dev/null +++ b/includes/lenny/install/pics/blue-lowerleft.png diff --git a/includes/lenny/install/pics/blue-lowerright.png b/includes/lenny/install/pics/blue-lowerright.png Binary files differnew file mode 100644 index 0000000..7e66271 --- /dev/null +++ b/includes/lenny/install/pics/blue-lowerright.png diff --git a/includes/lenny/install/pics/blue-upperleft.png b/includes/lenny/install/pics/blue-upperleft.png Binary files differnew file mode 100644 index 0000000..a58d0ec --- /dev/null +++ b/includes/lenny/install/pics/blue-upperleft.png diff --git a/includes/lenny/install/pics/blue-upperright.png b/includes/lenny/install/pics/blue-upperright.png Binary files differnew file mode 100644 index 0000000..2f36849 --- /dev/null +++ b/includes/lenny/install/pics/blue-upperright.png diff --git a/includes/lenny/install/pics/debian-61.png b/includes/lenny/install/pics/debian-61.png Binary files differnew file mode 100644 index 0000000..1aca3e6 --- /dev/null +++ b/includes/lenny/install/pics/debian-61.png diff --git a/includes/lenny/install/pics/debian.jpg b/includes/lenny/install/pics/debian.jpg Binary files differnew file mode 100644 index 0000000..db62d7a --- /dev/null +++ b/includes/lenny/install/pics/debian.jpg diff --git a/includes/lenny/install/pics/dot_bw.gif b/includes/lenny/install/pics/dot_bw.gif Binary files differnew file mode 100644 index 0000000..87a8076 --- /dev/null +++ b/includes/lenny/install/pics/dot_bw.gif diff --git a/includes/lenny/install/pics/gradient.png b/includes/lenny/install/pics/gradient.png Binary files differnew file mode 100644 index 0000000..33009da --- /dev/null +++ b/includes/lenny/install/pics/gradient.png diff --git a/includes/lenny/install/pics/logo-50.jpg b/includes/lenny/install/pics/logo-50.jpg Binary files differnew file mode 100644 index 0000000..542f0a4 --- /dev/null +++ b/includes/lenny/install/pics/logo-50.jpg diff --git a/includes/lenny/install/pics/openlogo-nd-50.png b/includes/lenny/install/pics/openlogo-nd-50.png Binary files differnew file mode 100644 index 0000000..3d7e471 --- /dev/null +++ b/includes/lenny/install/pics/openlogo-nd-50.png diff --git a/includes/lenny/install/pics/red-lowerleft.png b/includes/lenny/install/pics/red-lowerleft.png Binary files differnew file mode 100644 index 0000000..caca9c5 --- /dev/null +++ b/includes/lenny/install/pics/red-lowerleft.png diff --git a/includes/lenny/install/pics/red-lowerright.png b/includes/lenny/install/pics/red-lowerright.png Binary files differnew file mode 100644 index 0000000..c27056c --- /dev/null +++ b/includes/lenny/install/pics/red-lowerright.png diff --git a/includes/lenny/install/pics/red-upperleft.png b/includes/lenny/install/pics/red-upperleft.png Binary files differnew file mode 100644 index 0000000..c1e3301 --- /dev/null +++ b/includes/lenny/install/pics/red-upperleft.png diff --git a/includes/lenny/install/pics/red-upperright.png b/includes/lenny/install/pics/red-upperright.png Binary files differnew file mode 100644 index 0000000..54d17ca --- /dev/null +++ b/includes/lenny/install/pics/red-upperright.png diff --git a/includes/lenny/install/tools/README b/includes/lenny/install/tools/README new file mode 100644 index 0000000..bc56f93 --- /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 Binary files differnew file mode 100644 index 0000000..b30fa96 --- /dev/null +++ b/includes/lenny/install/tools/diskio.zip diff --git a/includes/lenny/install/tools/fips20.zip b/includes/lenny/install/tools/fips20.zip Binary files differnew file mode 100644 index 0000000..c4a64b6 --- /dev/null +++ b/includes/lenny/install/tools/fips20.zip diff --git a/includes/lenny/install/tools/gzip124.exe b/includes/lenny/install/tools/gzip124.exe Binary files differnew file mode 100644 index 0000000..1a8d137 --- /dev/null +++ b/includes/lenny/install/tools/gzip124.exe diff --git a/includes/lenny/install/tools/lodlin16.zip b/includes/lenny/install/tools/lodlin16.zip Binary files differnew file mode 100644 index 0000000..b86310a --- /dev/null +++ b/includes/lenny/install/tools/lodlin16.zip diff --git a/includes/lenny/install/tools/md5sum-w32.zip b/includes/lenny/install/tools/md5sum-w32.zip Binary files differnew file mode 100644 index 0000000..982202b --- /dev/null +++ b/includes/lenny/install/tools/md5sum-w32.zip diff --git a/includes/lenny/install/tools/rawrite1.zip b/includes/lenny/install/tools/rawrite1.zip Binary files differnew file mode 100644 index 0000000..abdc229 --- /dev/null +++ b/includes/lenny/install/tools/rawrite1.zip diff --git a/includes/lenny/install/tools/rawrite2.zip b/includes/lenny/install/tools/rawrite2.zip Binary files differnew file mode 100644 index 0000000..aa33885 --- /dev/null +++ b/includes/lenny/install/tools/rawrite2.zip diff --git a/includes/lenny/install/tools/rwwrtwin.zip b/includes/lenny/install/tools/rwwrtwin.zip Binary files differnew file mode 100644 index 0000000..2c3fd11 --- /dev/null +++ b/includes/lenny/install/tools/rwwrtwin.zip 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 0000000..44393f8 --- /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 <bas@debian.org> +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 Binary files differnew file mode 100644 index 0000000..bf42ec8 --- /dev/null +++ b/includes/lenny/install/tools/src/md5sum-w32_1.1.tar.gz diff --git a/includes/lenny/install/tools/unz512x3.exe b/includes/lenny/install/tools/unz512x3.exe Binary files differnew file mode 100644 index 0000000..e8b36c8 --- /dev/null +++ b/includes/lenny/install/tools/unz512x3.exe diff --git a/includes/sid b/includes/sid new file mode 120000 index 0000000..fb5b653 --- /dev/null +++ b/includes/sid @@ -0,0 +1 @@ +lenny
\ No newline at end of file diff --git a/includes/sid/common/doc/FAQ/debian-faq.en.html.tar.gz b/includes/sid/common/doc/FAQ/debian-faq.en.html.tar.gz Binary files differdeleted file mode 100644 index 4deda61..0000000 --- a/includes/sid/common/doc/FAQ/debian-faq.en.html.tar.gz +++ /dev/null diff --git a/includes/sid/common/doc/FAQ/debian-faq.en.pdf.gz b/includes/sid/common/doc/FAQ/debian-faq.en.pdf.gz Binary files differdeleted file mode 100644 index 265fe0f..0000000 --- a/includes/sid/common/doc/FAQ/debian-faq.en.pdf.gz +++ /dev/null diff --git a/includes/sid/common/doc/FAQ/debian-faq.en.ps.gz b/includes/sid/common/doc/FAQ/debian-faq.en.ps.gz Binary files differdeleted file mode 100644 index da90480..0000000 --- a/includes/sid/common/doc/FAQ/debian-faq.en.ps.gz +++ /dev/null diff --git a/includes/sid/common/doc/FAQ/debian-faq.en.txt.gz b/includes/sid/common/doc/FAQ/debian-faq.en.txt.gz Binary files differdeleted file mode 100644 index 0543b2b..0000000 --- a/includes/sid/common/doc/FAQ/debian-faq.en.txt.gz +++ /dev/null diff --git a/includes/sid/common/doc/FAQ/html/ch-basic_defs.en.html b/includes/sid/common/doc/FAQ/html/ch-basic_defs.en.html deleted file mode 100644 index aac1358..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-basic_defs.en.html +++ /dev/null @@ -1,431 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Definitions and overview</title> - -</head> - -<body> - -<p><a name="ch-basic_defs"></a></p> -<hr> - -<p> -[ <a href="index.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ 1 ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-getting.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 1 - Definitions and overview -</h1> - -<hr> - -<h2><a name="s-whatisfaq"></a>1.1 What is this FAQ?</h2> - -<p> -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. -</p> - -<p> -If you can't find what you're looking for in this FAQ, be sure to check out <a -href="ch-support.en.html#s-debiandocs">What other documentation exists on and -for a Debian system?, Section 11.1</a>. If even that doesn't help, refer to <a -href="ch-faqinfo.en.html#s-feedback">Feedback, Section 15.2</a>. -</p> - -<hr> - -<h2><a name="s-whatisdebian"></a>1.2 What is Debian GNU/Linux?</h2> - -<p> -Debian GNU/Linux is a particular <em>distribution</em> of the Linux operating -system, and numerous packages that run on it. -</p> - -<p> -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. -</p> - -<p> -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. -</p> - -<p> -For Debian, free has the GNUish meaning (see the <code><a -href="http://www.debian.org/social_contract#guidelines">Debian Free Software -Guidelines</a></code>). 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. -</p> - -<p> -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. -</p> - -<p> -Debian GNU/Linux is: -</p> -<ul> -<li> -<p> -<strong>full featured</strong>: Debian includes more than 18347 software -packages at present. Users can select which packages to install; Debian -provides a tool for this purpose. You can find a list and descriptions of the -packages currently available in Debian at any of the Debian <code><a -href="http://www.debian.org/distrib/ftplist">mirror sites</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -<strong>free to use and redistribute</strong>: There is no consortium -membership or payment required to participate in its distribution and -development. All packages that are formally part of Debian GNU/Linux are free -to redistribute, usually under terms specified by the GNU General Public -License. -</p> - -<p> -The Debian FTP archives also carry approximately 444 software packages (in the -<samp>non-free</samp> and <samp>contrib</samp> sections), which are -distributable under specific terms included with each package. -</p> -</li> -</ul> -<ul> -<li> -<p> -<strong>dynamic</strong>: With about 1950 volunteers constantly contributing -new and improved code, Debian is evolving rapidly. New releases are planned to -be made every several months, and the FTP archives are updated daily. -</p> -</li> -</ul> - -<p> -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 <a -href="ch-redistrib.en.html#s-childistro">I am making a special Linux -distribution for a "vertical market". Can I use Debian GNU/Linux for -the guts of a Linux system and add my own applications on top of it?, Section -13.3</a> for more information. -</p> - -<hr> - -<h2><a name="s-linux"></a>1.3 OK, now I know what Debian is... what is Linux?!</h2> - -<p> -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. -</p> - -<p> -Besides its kernel, a "Linux" system usually has: -</p> -<ul> -<li> -<p> -a file system that follows the Linux Filesystem Hierarchy Standard <code><a -href="http://www.pathname.com/fhs/">http://www.pathname.com/fhs/</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -a wide range of Unix utilities, many of which have been developed by the GNU -project and the Free Software Foundation. -</p> -</li> -</ul> - -<p> -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 <a href="ch-compat.en.html#s-otherunices">How -source code compatible is Debian with other Unix systems?, Section 3.3</a>. -</p> - -<p> -For more information about Linux, see Michael K. Johnson's <code><a -href="ftp://ibiblio.org/pub/Linux/docs/HOWTO/INFO-SHEET">Linux Information -Sheet</a></code> and <code><a -href="ftp://ibiblio.org/pub/Linux/docs/HOWTO/META-FAQ">Meta-FAQ</a></code>. -</p> - -<hr> - -<h2><a name="s-non-linux"></a>1.4 Does Debian just do GNU/Linux?</h2> - -<p> -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. -</p> - -<p> -The oldest porting effort is Debian GNU/Hurd. -</p> - -<p> -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. -</p> - -<p> -Please see <code><a -href="http://www.gnu.org/software/hurd/">http://www.gnu.org/software/hurd/</a></code> -for more information about the GNU/Hurd in general, and <code><a -href="http://www.debian.org/ports/hurd/">http://www.debian.org/ports/hurd/</a></code> -for more information about Debian GNU/Hurd. -</p> - -<p> -A second effort is the port to a BSD kernel. People are working with both the -NetBSD and the FreeBSD kernels. -</p> - -<p> -See <code><a -href="http://www.debian.org/ports/#nonlinux">http://www.debian.org/ports/#nonlinux</a></code> -for more information about these non-linux ports. -</p> - -<hr> - -<h2><a name="s-difference"></a>1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?</h2> - -<p> -These key features distinguish Debian from other Linux distributions: -</p> -<dl> -<dt>Freedom:</dt> -<dd> -<p> -As stated in the <code><a href="http://www.debian.org/social_contract">Debian -Social Contract</a></code>, 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 <code><a -href="http://www.debian.org/social_contract#guidelines">The Debian Free -Software</a></code>. -</p> -</dd> -</dl> -<dl> -<dt>The Debian package maintenance system:</dt> -<dd> -<p> -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 <a -href="ch-pkg_basics.en.html">Basics of the Debian package management system, -Chapter 6</a>). -</p> -</dd> -</dl> -<dl> -<dt>Open development:</dt> -<dd> -<p> -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. -</p> - -<p> -More than 1950 volunteer package maintainers are working on over 18347 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 <a -href="ch-contributing.en.html#s-contrib">How can I become a Debian software -developer?, Section 12.1</a>. -</p> -</dd> -</dl> -<dl> -<dt>The Universal Operating System:</dt> -<dd> -<p> -Debian comes with <code><a href="http://packages.debian.org/stable/">more than -18347 packages</a></code> and runs on <code><a -href="http://www.debian.org/ports/">10 architectures</a></code>. This is far -more than is available for any other GNU/Linux distribution. See <a -href="ch-software.en.html#s-apps">What types of applications and development -software are available for Debian GNU/Linux?, Section 4.1</a> for an overview -of the provided software and see <a href="ch-compat.en.html#s-arches">On what -hardware architectures/systems does Debian GNU/Linux run?, Section 3.1</a> for -a description of the supported hardware platforms. -</p> -</dd> -</dl> -<dl> -<dt>The Bug Tracking System:</dt> -<dd> -<p> -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 <a -href="ch-support.en.html#s-buglogs">Are there logs of known bugs?, Section -11.4</a>. -</p> -</dd> -</dl> -<dl> -<dt>The Debian Policy:</dt> -<dd> -<p> -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. -</p> -</dd> -</dl> - -<p> -For additional information about this, please see our web page about <code><a -href="http://www.debian.org/intro/why_debian">reasons to choose -Debian</a></code>. -</p> - -<hr> - -<h2><a name="s-gnu"></a>1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?</h2> - -<p> -The Debian system builds on the ideals of free software first championed by the -<code><a href="http://www.gnu.org/">Free Software Foundation</a></code> and in -particular by <code><a href="http://www.stallman.org/">Richard -Stallman</a></code>. FSF's powerful system development tools, utilities, and -applications are also a key part of the Debian system. -</p> - -<p> -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. -</p> - -<p> -The FSF's long-standing objective is to develop a new operating system called -GNU, based on <code><a -href="http://www.gnu.org/software/hurd/">Hurd</a></code>. Debian is working -with FSF on this system, called <code><a -href="http://www.debian.org/ports/hurd/">Debian GNU/Hurd</a></code>. -</p> - -<hr> - -<h2><a name="s-pronunciation"></a>1.7 How does one pronounce Debian and what does this word mean?</h2> - -<p> -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.) -</p> - -<hr> - -<p> -[ <a href="index.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ 1 ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-getting.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-compat.en.html b/includes/sid/common/doc/FAQ/html/ch-compat.en.html deleted file mode 100644 index 4e92270..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-compat.en.html +++ /dev/null @@ -1,386 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Compatibility issues</title> - -</head> - -<body> - -<p><a name="ch-compat"></a></p> -<hr> - -<p> -[ <a href="ch-getting.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ 3 ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-software.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 3 - Compatibility issues -</h1> - -<hr> - -<h2><a name="s-arches"></a>3.1 On what hardware architectures/systems does Debian GNU/Linux run?</h2> - -<p> -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 <code><a -href="http://en.tldp.org/FAQ/Linux-FAQ/intro.html#DOES-LINUX-RUN-ON-MY-COMPUTER">Linux -FAQ</a></code> for details. -</p> - -<p> -The current Debian GNU/Linux release, 4.0, contains a complete, binary -distribution for the following architectures: -</p> - -<p> -<em>i386</em>: this covers PCs based on Intel and compatible processors, -including Intel's 386, 486, Pentium, Pentium Pro, Pentium II (both Klamath and -Celeron), and Pentium III, and most compatible processors by AMD, Cyrix and -others. -</p> - -<p> -<em>m68k</em>: this covers Amigas and ATARIs having a Motorola 680x0 processor -for x>=2; with MMU. -</p> - -<p> -<em>alpha</em>: Compaq/Digital's Alpha systems. -</p> - -<p> -<em>sparc</em>: this covers Sun's SPARC and most UltraSPARC systems. -</p> - -<p> -<em>powerpc</em>: this covers some IBM/Motorola PowerPC machines, including -CHRP, PowerMac and PReP machines. -</p> - -<p> -<em>arm</em>: ARM and StrongARM machines. -</p> - -<p> -<em>mips</em>: SGI's big-endian MIPS systems, Indy and Indigo2; -<em>mipsel</em>: little-endian MIPS machines, Digital DECstations. -</p> - -<p> -<em>hppa</em>: Hewlett-Packard's PA-RISC machines (712, C3000, L2000, A500). -</p> - -<p> -<em>ia64</em>: Intel IA-64 ("Itanium") computers. -</p> - -<p> -<em>s390</em>: IBM S/390 mainframe systems. -</p> - -<p> -The development of binary distributions of Debian for Sparc64 (UltraSPARC -native) architectures is currently underway. -</p> - -<p> -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 <code><a -href="http://www.debian.org/releases/stable/installmanual">http://www.debian.org/releases/stable/installmanual</a></code>. -</p> - -<hr> - -<h2><a name="s-otherdistribs"></a>3.2 How compatible is Debian with other distributions of Linux?</h2> - -<p> -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. -</p> - -<p> -Debian GNU/Linux adheres to the <code><a -href="http://www.pathname.com/fhs/">Linux Filesystem Hierarchy -Standard</a></code>. 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. -</p> - -<p> -Debian GNU/Linux supports software developed for the <code><a -href="http://www.linuxbase.org/">Linux Standard Base</a></code>. The LSB is a -specification for allowing the same binary package to be used on multiple -distributions. Packages for the Debian Etch release must not conflict with -requirements of the LSB, v1.3. As of this writing, Debian GNU/Linux is not -formally LSB-certified. However, some Debian derived distributions are. -Discussion and coordination of efforts towards ensuring Debian meets the -requirements of the Linux Standard Base is taking place on the <code><a -href="http://lists.debian.org/debian-lsb/">debian-lsb mailing list</a></code>. -</p> - -<hr> - -<h2><a name="s-otherunices"></a>3.3 How source code compatible is Debian with other Unix systems?</h2> - -<p> -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. -</p> - -<p> -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.) -</p> - -<p> -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. -</p> - -<hr> - -<h2><a name="s-otherpackages"></a>3.4 Can I use Debian packages (".deb" files) on my Red Hat/Slackware/... Linux system? Can I use Red Hat packages (".rpm" files) on my Debian GNU/Linux system?</h2> - -<p> -Different Linux distributions use different package formats and different -package management programs. -</p> -<dl> -<dt><strong>You probably can:</strong></dt> -<dd> -<p> -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 <code><a href="http://packages.debian.org/alien">Alien</a></code> package -is used to convert between different package formats. -</p> -</dd> -</dl> -<dl> -<dt><strong>You probably do not want to:</strong></dt> -<dd> -<p> -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. -</p> -</dd> -</dl> -<dl> -<dt><strong>A better way:</strong></dt> -<dd> -<p> -The Linux File System Standard (and therefore Debian GNU/Linux) requires that -subdirectories under <samp>/usr/local/</samp> 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. -</p> -</dd> -</dl> - -<hr> - -<h2><a name="s-libc5"></a>3.5 Is Debian able to run my old libc5 programs?</h2> - -<p> -Yes. Just install the required <code>libc5</code> libraries, from the -<samp>oldlibs</samp> section (containing old packages included for -compatibility with older applications). -</p> - -<hr> - -<h2><a name="s-libc5-compile"></a>3.6 Can Debian be used to compile libc5 programs?</h2> - -<p> -Yes. Install <code>libc5-altdev</code> and <code>altgcc</code> packages (from -the <samp>oldlibs</samp> section). You can find the appropriate libc5-compiled -<code>gcc</code> and <code>g++</code> in directory -<samp>/usr/i486-linuxlibc1/bin</samp>. Put them in your $PATH variable to get -<code>make</code> and other programs to execute these first. -</p> - -<p> -Be aware that libc5 environment isn't fully supported by our other packages -anymore. -</p> - -<hr> - -<h2><a name="s-non-debian-programs"></a>3.7 How should I install a non-Debian program?</h2> - -<p> -Files under the directory <samp>/usr/local/</samp> 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 -<samp>/usr/local/src/foo</samp>. After you compile them, place the binaries in -<samp>/usr/local/bin/</samp>, the libraries in <samp>/usr/local/lib/</samp>, -and the configuration files in <samp>/usr/local/etc/</samp>. -</p> - -<p> -If your programs and/or files really must be placed in some other directory, -you could still store them in <samp>/usr/local/</samp>, and build the -appropriate symbolic links from the required location to its location in -<samp>/usr/local/</samp>, e.g., you could make the link -</p> - -<pre> - ln -s /usr/local/bin/foo /usr/bin/foo -</pre> - -<p> -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 <a href="ch-support.en.html#s-debiandocs">What other -documentation exists on and for a Debian system?, Section 11.1</a>). -</p> - -<hr> - -<h2><a name="s-termcap"></a>3.8 Why can't I compile programs that require libtermcap?</h2> - -<p> -Debian uses the <samp>terminfo</samp> database and the <samp>ncurses</samp> -library of terminal interface routes, rather than the <samp>termcap</samp> -database and the <samp>termcap</samp> library. Users who are compiling -programs that require some knowledge of the terminal interface should replace -references to <samp>libtermcap</samp> with references to -<samp>libncurses</samp>. -</p> - -<p> -To support binaries that have already been linked with the <samp>termcap</samp> -library, and for which you do not have the source, Debian provides a package -called <code>termcap-compat</code>. This provides both -<samp>libtermcap.so.2</samp> and <samp>/etc/termcap</samp>. 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 -<samp>/etc/termcap</samp> file. -</p> - -<hr> - -<h2><a name="s-accelx"></a>3.9 Why can't I install AccelX?</h2> - -<p> -AccelX uses the <samp>termcap</samp> library for installation. See <a -href="#s-termcap">Why can't I compile programs that require libtermcap?, -Section 3.8</a> above. -</p> - -<hr> - -<h2><a name="s-motifnls"></a>3.10 Why do my old XFree 2.1 Motif applications crash?</h2> - -<p> -You need to install the <code>motifnls</code> 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. -</p> - -<p> -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. -</p> - -<hr> - -<p> -[ <a href="ch-getting.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ 3 ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-software.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-contributing.en.html b/includes/sid/common/doc/FAQ/html/ch-contributing.en.html deleted file mode 100644 index ae790ba..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-contributing.en.html +++ /dev/null @@ -1,191 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Contributing to the Debian Project</title> - -</head> - -<body> - -<p><a name="ch-contributing"></a></p> -<hr> - -<p> -[ <a href="ch-support.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ 12 ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-redistrib.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 12 - Contributing to the Debian Project -</h1> - -<hr> - -<p> -<code><a href="http://www.debian.org/donations">Donations</a></code> 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. -</p> - -<hr> - -<h2><a name="s-contrib"></a>12.1 How can I become a Debian software developer?</h2> - -<p> -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. -</p> - -<p> -The description of becoming a Debian developer can be found at the <code><a -href="http://www.debian.org/devel/join/newmaint">New Maintainer's -Corner</a></code> at the Debian web site. -</p> - -<hr> - -<h2><a name="s-contribresources"></a>12.2 How can I contribute resources to the Debian project?</h2> - -<p> -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 <code><a href="http://www.debian.org/mirror/size">Debian mirror -size</a></code> page for information on the disk space requirements. -</p> - -<p> -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. -</p> - -<p> -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 -<code><a -href="mailto:debian-admin@lists.debian.org">debian-admin@lists.debian.org</a></code>. -</p> - -<hr> - -<h2><a name="s-supportingorganizations"></a>12.3 How can I contribute financially to the Debian project?</h2> - -<p> -One can make individual donations to one of two organizations that are critical -to the development of the Debian project. -</p> - -<hr> - -<h3><a name="s-SPI"></a>12.3.1 Software in the Public Interest</h3> - -<p> -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. -</p> - -<p> -Our goals are very much like those of FSF, and we encourage programmers to use -the GNU General Public License on their programs. However, we have a slightly -different focus in that we are building and distributing a Linux system that -diverges in many technical details from the GNU system planned by FSF. We -still communicate with FSF, and we cooperate in sending them changes to GNU -software and in asking our users to donate to FSF and the GNU project. -</p> - -<p> -SPI can be reached at: <code><a -href="http://www.spi-inc.org/">http://www.spi-inc.org/</a></code>. -</p> - -<hr> - -<h3><a name="s-FSF"></a>12.3.2 Free Software Foundation</h3> - -<p> -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. -</p> - -<p> -FSF can be reached at: <code><a -href="http://www.fsf.org/">http://www.fsf.org/</a></code>. -</p> - -<hr> - -<p> -[ <a href="ch-support.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ 12 ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-redistrib.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-customizing.en.html b/includes/sid/common/doc/FAQ/html/ch-customizing.en.html deleted file mode 100644 index 0185e6c..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-customizing.en.html +++ /dev/null @@ -1,522 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Customizing your installation of Debian GNU/Linux</title> - -</head> - -<body> - -<p><a name="ch-customizing"></a></p> -<hr> - -<p> -[ <a href="ch-kernel.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ 10 ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-support.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 10 - Customizing your installation of Debian GNU/Linux -</h1> - -<hr> - -<h2><a name="s-papersize"></a>10.1 How can I ensure that all programs use the same paper size?</h2> - -<p> -Install the <code>libpaper1</code> package, and it will ask you for a -system-wide default paper size. This setting will be kept in the file -<samp>/etc/papersize</samp>. -</p> - -<p> -Users can override the paper size setting using the <samp>PAPERSIZE</samp> -environment variable. For details, see the manual page -<code>papersize(5)</code>. -</p> - -<hr> - -<h2><a name="s-hardwareaccess"></a>10.2 How can I provide access to hardware peripherals, without compromising security?</h2> - -<p> -Many device files in the <samp>/dev</samp> directory belong to some predefined -groups. For example, <samp>/dev/fd0</samp> belongs to the <samp>floppy</samp> -group, and <samp>/dev/dsp</samp> belongs to the <samp>audio</samp> group. -</p> - -<p> -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: -</p> - -<pre> - adduser user group -</pre> - -<p> -This way you won't have to change the file permissions on the device. -</p> - -<hr> - -<h2><a name="s-consolefont"></a>10.3 How do I load a console font on startup the Debian way?</h2> - -<p> -The <code>kbd</code> and <code>console-tools</code> packages support this, edit -<samp>/etc/kbd/config</samp> or <samp>/etc/console-tools/config</samp> files. -</p> - -<hr> - -<h2><a name="s-appdefaults"></a>10.4 How can I configure an X11 program's application defaults?</h2> - -<p> -Debian's X programs will install their application resource data in the -<samp>/etc/X11/app-defaults/</samp> 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. -</p> - -<hr> - -<h2><a name="s-booting"></a>10.5 Every distribution seems to have a different boot-up method. Tell me about Debian's.</h2> - -<p> -Like all Unices, Debian boots up by executing the program <samp>init</samp>. -The configuration file for <samp>init</samp> (which is -<samp>/etc/inittab</samp>) specifies that the first script to be executed -should be <samp>/etc/init.d/rcS</samp>. This script runs all of the scripts in -<samp>/etc/rcS.d/</samp> 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 <samp>/etc/rc.boot/</samp> too. -Any scripts in the latter directory are usually reserved for system -administrator use, and using them in packages is deprecated. -</p> - -<p> -After completing the boot process, <samp>init</samp> executes all start scripts -in a directory specified by the default runlevel (this runlevel is given by the -entry for <samp>id</samp> in <samp>/etc/inittab</samp>). Like most System V -compatible Unices, Linux has 7 runlevels: -</p> -<ul> -<li> -<p> -0 (halt the system), -</p> -</li> -</ul> -<ul> -<li> -<p> -1 (single-user mode), -</p> -</li> -</ul> -<ul> -<li> -<p> -2 through 5 (various multi-user modes), and -</p> -</li> -</ul> -<ul> -<li> -<p> -6 (reboot the system). -</p> -</li> -</ul> - -<p> -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 -<samp>/etc/rc2.d/</samp> will be run. -</p> - -<p> -In fact, the scripts in any of the directories, <samp>/etc/rcN.d/</samp> are -just symbolic links back to scripts in <samp>/etc/init.d/</samp>. However, the -<em>names</em> of the files in each of the <samp>/etc/rcN.d/</samp> directories -are selected to indicate the <em>way</em> the scripts in -<samp>/etc/init.d/</samp> 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. -</p> - -<p> -This approach works because the scripts in <samp>/etc/init.d/</samp> 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. -</p> - -<p> -For example, with the argument `reload' the command -</p> - -<pre> - /etc/init.d/sendmail reload -</pre> - -<p> -sends the sendmail daemon a signal to reread its configuration file. (BTW, -Debian supplies <code>invoke-rc.d</code> as a wrapper for invoking the scripts -in <samp>/etc/init.d/</samp>.) -</p> - -<hr> - -<h2><a name="s-custombootscripts"></a>10.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?</h2> - -<p> -Suppose a system needs to execute script <samp>foo</samp> on start-up, or on -entry to a particular (System V) runlevel. Then the system administrator -should: -</p> -<ul> -<li> -<p> -Enter the script <samp>foo</samp> into the directory <samp>/etc/init.d/</samp>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Run the Debian command <samp>update-rc.d</samp> with appropriate arguments, to -set up links between the (command-line-specified) directories rc?.d and -<samp>/etc/init.d/foo</samp>. Here, '?' is a number from 0 through 6 and -corresponds to each of the System V runlevels. -</p> -</li> -</ul> -<ul> -<li> -<p> -Reboot the system. -</p> -</li> -</ul> - -<p> -The command <samp>update-rc.d</samp> will set up links between files in the -directories rc?.d and the script in <samp>/etc/init.d/</samp>. Each link will -begin with a 'S' or a 'K', followed by a number, followed by the name of the -script. Scripts beginning with 'S' in <samp>/etc/rcN.d/</samp> are executed -when runlevel <samp>N</samp> is entered. Scripts beginning with a 'K' are -executed when leaving runlevel <samp>N</samp>. -</p> - -<p> -One might, for example, cause the script <samp>foo</samp> to execute at -boot-up, by putting it in <samp>/etc/init.d/</samp> and installing the links -with <samp>update-rc.d foo defaults 19</samp>. The argument 'defaults' refers -to the default runlevels, which are 2 through 5. The argument '19' ensures -that <samp>foo</samp> is called before any scripts containing numbers 20 or -larger. -</p> - -<hr> - -<h2><a name="s-interconffiles"></a>10.7 How does the package management system deal with packages that contain configuration files for other packages?</h2> - -<p> -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 <code>dpkg</code> 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. -</p> - -<p> -Instead, create a local package that modifies the configuration files of the -"group" of Debian packages of interest. Then <code>dpkg</code> 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. -</p> - -<hr> - -<h2><a name="s-divert"></a>10.8 How do I override a file installed by a package, so that a different version can be used instead?</h2> - -<p> -Suppose a sysadmin or local user wishes to use a program -"login-local" rather than the program "login" provided by -the Debian <code>login</code> package. -</p> - -<p> -Do <strong>not</strong>: -</p> -<ul> -<li> -<p> -Overwrite <samp>/bin/login</samp> with <samp>login-local</samp>. -</p> -</li> -</ul> - -<p> -The package management system will not know about this change, and will simply -overwrite your custom <samp>/bin/login</samp> whenever <samp>login</samp> (or -any package that provides <samp>/bin/login</samp>) is installed or updated. -</p> - -<p> -Rather, do -</p> -<ul> -<li> -<p> -Execute: -</p> - -<pre> - dpkg-divert --divert /bin/login.debian /bin/login -</pre> - -<p> -in order to cause all future installations of the Debian <code>login</code> -package to write the file <samp>/bin/login</samp> to -<samp>/bin/login.debian</samp> instead. -</p> -</li> -</ul> -<ul> -<li> -<p> -Then execute: -</p> - -<pre> - cp login-local /bin/login -</pre> - -<p> -to move your own locally-built program into place. -</p> -</li> -</ul> - -<p> -Details are given in the manual page <code>dpkg-divert(8)</code>. -</p> - -<hr> - -<h2><a name="s-localpackages"></a>10.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?</h2> - -<p> -Execute the command: -</p> - -<pre> - dpkg-scanpackages BIN_DIR OVERRIDE_FILE [PATHPREFIX] > my_Packages -</pre> - -<p> -where: -</p> -<ul> -<li> -<p> -BIN-DIR is a directory where Debian archive files (which usually have an -extension of ".deb") are stored. -</p> -</li> -</ul> -<ul> -<li> -<p> -OVERRIDE_FILE is a file that is edited by the distribution maintainers and is -usually stored on a Debian FTP archive at <samp>indices/override.main.gz</samp> -for the Debian packages in the "main" distribution. You can ignore -this for local packages. -</p> -</li> -</ul> -<ul> -<li> -<p> -PATHPREFIX is an <em>optional</em> string that can be prepended to the -<samp>my_Packages</samp> file being produced. -</p> -</li> -</ul> - -<p> -Once you have built the file <samp>my_Packages</samp>, tell the package -management system about it by using the command: -</p> - -<pre> - dpkg --merge-avail my_Packages -</pre> - -<p> -If you are using APT, you can add the local repository to your -<code>sources.list(5)</code> file, too. -</p> - -<hr> - -<h2><a name="s-diverse"></a>10.10 Some users like mawk, others like gawk; some like vim, others like elvis; some like trn, others like tin; how does Debian support diversity?</h2> - -<p> -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. -</p> - -<p> -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. -</p> - -<p> -For example, there might exist two different versions of newsreaders on a -system. The news server package might 'recommend' that there exist -<em>some</em> news reader on the system, but the choice of <samp>tin</samp> or -<samp>trn</samp> is left up to the individual user. This is satisfied by -having both the <code>tin</code> and <code>trn</code> packages provide the -virtual package <code>news-reader</code>. <em>Which</em> program is invoked is -determined by a link pointing from a file with the virtual package name -<samp>/etc/alternatives/news-reader</samp> to the selected file, e.g., -<samp>/usr/bin/trn</samp>. -</p> - -<p> -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 <samp>update-alternatives</samp> provides a way of -ensuring that all the files associated with a specified package are selected as -a system default. -</p> - -<p> -For example, to check what executables provide `x-window-manager', run: -</p> - -<pre> - update-alternatives --display x-window-manager -</pre> - -<p> -If you want to change it, run: -</p> - -<pre> - update-alternatives --config x-window-manager -</pre> - -<p> -And follow the instructions on the screen (basically, press the number next to -the entry you'd like better). -</p> - -<p> -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: -</p> - -<pre> - update-alternatives --install /usr/bin/x-window-manager \ - x-window-manager /usr/local/bin/wmaker-cvs 50 -</pre> - -<p> -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). -</p> - -<p> -To remove an alternative you added, simply run: -</p> - -<pre> - update-alternatives --remove x-window-manager /usr/local/bin/wmaker-cvs -</pre> - -<hr> - -<p> -[ <a href="ch-kernel.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ 10 ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-support.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-faqinfo.en.html b/includes/sid/common/doc/FAQ/html/ch-faqinfo.en.html deleted file mode 100644 index 1d4f43b..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-faqinfo.en.html +++ /dev/null @@ -1,210 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - General information about the FAQ</title> - -</head> - -<body> - -<p><a name="ch-faqinfo"></a></p> -<hr> - -<p> -[ <a href="ch-nexttime.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ 15 ] -[ <a href="index.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 15 - General information about the FAQ -</h1> - -<hr> - -<h2><a name="s-authors"></a>15.1 Authors</h2> - -<p> -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. -</p> - -<p> -Parts of the information came from: -</p> -<ul> -<li> -<p> -The Debian-1.1 release announcement, by <code><a -href="http://www.perens.com/">Bruce Perens</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -The Linux FAQ, by <code><a -href="http://www.chiark.greenend.org.uk/~ijackson/">Ian Jackson</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -<code><a href="http://lists.debian.org/">Debian Mailing Lists -Archives</a></code>, -</p> -</li> -</ul> -<ul> -<li> -<p> -the dpkg programmers' manual and the Debian Policy manual (see <a -href="ch-support.en.html#s-debiandocs">What other documentation exists on and -for a Debian system?, Section 11.1</a>) -</p> -</li> -</ul> -<ul> -<li> -<p> -many developers, volunteers, and beta testers, and -</p> -</li> -</ul> -<ul> -<li> -<p> -the flaky memories of its authors. :-) -</p> -</li> -</ul> - -<p> -The authors would like to thank all those who helped make this document -possible. -</p> - -<p> -All warranties are disclaimed. All trademarks are property of their respective -trademark owners. -</p> - -<hr> - -<h2><a name="s-feedback"></a>15.2 Feedback</h2> - -<p> -Comments and additions to this document are always welcome. Please send e-mail -to <code><a -href="mailto:doc-debian@packages.debian.org">doc-debian@packages.debian.org</a></code>, -or submit a wishlist bug report against the <code><code><a -href="http://bugs.debian.org/doc-debian">doc-debian</a></code></code> package. -</p> - -<hr> - -<h2><a name="s-latest"></a>15.3 Availability</h2> - -<p> -The latest version of this document can be viewed on the Debian WWW pages at -<code><a -href="http://www.debian.org/doc/FAQ/">http://www.debian.org/doc/FAQ/</a></code>. -</p> - -<p> -It is also available for download in plain text, HTML, PostScript and PDF -formats at <code><a -href="http://www.debian.org/doc/user-manuals#faq">http://www.debian.org/doc/user-manuals#faq</a></code>. -Also, there are several translations there. -</p> - -<p> -The original SGML files used to create this document are also available in -<code>doc-debian</code>'s source package, or in CVS at: -<samp>:pserver:anonymous@cvs.debian.org:/cvs/debian-doc/ddp/manuals.sgml/faq</samp> -</p> - -<hr> - -<h2><a name="s-docformat"></a>15.4 Document format</h2> - -<p> -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. -</p> - -<p> -Conversion utilities for DebianDoc SGML are available in Debian package -<code>debiandoc-sgml</code>. -</p> - -<hr> - -<p> -[ <a href="ch-nexttime.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ 15 ] -[ <a href="index.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-ftparchives.en.html b/includes/sid/common/doc/FAQ/html/ch-ftparchives.en.html deleted file mode 100644 index 6560f14..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-ftparchives.en.html +++ /dev/null @@ -1,575 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - The Debian FTP archives</title> - -</head> - -<body> - -<p><a name="ch-ftparchives"></a></p> -<hr> - -<p> -[ <a href="ch-software.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ 5 ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-pkg_basics.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 5 - The Debian FTP archives -</h1> - -<hr> - -<h2><a name="s-dirtree"></a>5.1 What are all those directories at the Debian FTP archives?</h2> - -<p> -The software that has been packaged for Debian GNU/Linux is available in one of -several directory trees on each Debian mirror site. -</p> - -<p> -The <samp>dists</samp> directory is short for "distributions", and it -is the canonical way to access the currently available Debian releases (and -pre-releases). -</p> - -<p> -The <samp>pool</samp> directory contains the actual packages, see <a -href="#s-pools">What's in the <samp>pool</samp> directory?, Section 5.10</a>. -</p> - -<p> -There are the following supplementary directories: -</p> -<dl> -<dt><em>/tools/</em>:</dt> -<dd> -<p> -DOS utilities for creating boot disks, partitioning your disk drive, -compressing/decompressing files, and booting Linux. -</p> -</dd> -</dl> -<dl> -<dt><em>/doc/</em>:</dt> -<dd> -<p> -The basic Debian documentation, such as the FAQ, the bug reporting system -instructions, etc. -</p> -</dd> -</dl> -<dl> -<dt><em>/indices/</em>:</dt> -<dd> -<p> -The Maintainers file and the override files. -</p> -</dd> -</dl> -<dl> -<dt><em>/project/</em>:</dt> -<dd> -<p> -mostly developer-only materials, such as: -</p> -<dl> -<dt><em>project/experimental/</em>:</dt> -<dd> -<p> -This directory contains packages and tools which are still being developed, and -are still in the alpha testing stage. Users shouldn't be using packages from -here, because they can be dangerous and harmful even for the most experienced -people. -</p> -</dd> -</dl> -</dd> -</dl> - -<hr> - -<h2><a name="s-dists"></a>5.2 How many Debian distributions are there in the <samp>dists</samp> directory?</h2> - -<p> -There are three distributions, the "stable" distribution, the -"testing" distribution, and the "unstable" distribution. -The "testing" distribution is sometimes `frozen' (see <a -href="#s-frozen">What about "testing"? How is it `frozen'?, Section -5.6.1</a>). -</p> - -<hr> - -<h2><a name="s-codenames"></a>5.3 What are all those names like slink, potato, etc.?</h2> - -<p> -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 <samp>unstable</samp> suddenly changed its name to -<samp>stable</samp>, a lot of stuff would have to be needlessly downloaded -again). -</p> - -<p> -Currently, <samp>stable</samp> is a symbolic link to <samp>etch</samp> (i.e. -Debian GNU/Linux 4.0) and <samp>testing</samp> is a symbolic link to -<samp>lenny</samp>. This means that <samp>etch</samp> is the current stable -distribution and <samp>lenny</samp> is the current testing distribution. -</p> - -<p> -<samp>unstable</samp> is a permanent symbolic link to <samp>sid</samp>, as -<samp>sid</samp> is always the unstable distribution (see <a href="#s-sid">What -about "sid"?, Section 5.4</a>). -</p> - -<hr> - -<h3><a name="s-oldcodenames"></a>5.3.1 Which other codenames have been used in the past?</h3> - -<p> -Other codenames that have been already used are: <samp>buzz</samp> for release -1.1, <samp>rex</samp> for release 1.2, <samp>bo</samp> for releases 1.3.x, -<samp>hamm</samp> for release 2.0, <samp>slink</samp> for release 2.1, -<samp>potato</samp> for release 2.2, <samp>woody</samp> for release 3.0 and -<samp>sarge</samp> for release 3.1. -</p> - -<hr> - -<h3><a name="s-sourceforcodenames"></a>5.3.2 Where do these codenames come from?</h3> - -<p> -So far they have been characters taken from the movie "Toy Story" by -Pixar. -</p> -<ul> -<li> -<p> -<em>buzz</em> (Buzz Lightyear) was the spaceman, -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>rex</em> was the tyrannosaurus, -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>bo</em> (Bo Peep) was the girl who took care of the sheep, -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>hamm</em> was the piggy bank, -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>slink</em> (Slinky Dog (R)) was the toy dog, -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>potato</em> was, of course, Mr. Potato (R), -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>woody</em> was the cowboy, -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>sarge</em> was the sergeant of the Green Plastic Army Men, -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>etch</em> was the toy blackboard (Etch-a-Sketch (R)), -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>lenny</em> was the binoculars. -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>sid</em> was the boy next door who destroyed toys. -</p> -</li> -</ul> - -<hr> - -<h2><a name="s-sid"></a>5.4 What about "sid"?</h2> - -<p> -<em>sid</em> or <em>unstable</em> is the place where most of the packages are -initially uploaded. It will never be released directly, because packages which -are to be released will first have to be included in <em>testing</em>, in order -to be released in <em>stable</em> later on. sid contains packages for both -released and unreleased architectures. -</p> - -<p> -The name "sid" also comes from the "Toy Story" animated -motion picture: Sid was the boy next door who destroyed toys :-) -</p> - -<p> -[<a href="footnotes.en.html#f1" name="fr1">1</a>] -</p> - -<hr> - -<h2><a name="s-stable"></a>5.5 What does the stable directory contain?</h2> -<ul> -<li> -<p> -stable/main/: This directory contains the packages which formally constitute -the most recent release of the Debian GNU/Linux system. -</p> - -<p> -These packages all comply with the <code><a -href="http://www.debian.org/social_contract#guidelines">Debian Free Software -Guidelines</a></code>, and are all freely usable and distributable. -</p> -</li> -</ul> -<ul> -<li> -<p> -stable/non-free/: This directory contains packages distribution of which is -restricted in a way that requires that distributors take careful account of the -specified copyright requirements. -</p> - -<p> -For example, some packages have licenses which prohibit commercial -distribution. Others can be redistributed but are in fact shareware and not -freeware. The licenses of each of these packages must be studied, and possibly -negotiated, before the packages are included in any redistribution (e.g., in a -CD-ROM). -</p> -</li> -</ul> -<ul> -<li> -<p> -stable/contrib/: This directory contains packages which are DFSG-free and -<em>freely distributable</em> themselves, but somehow depend on a package that -is <em>not</em> freely distributable and thus available only in the non-free -section. -</p> -</li> -</ul> - -<hr> - -<h2><a name="s-testing"></a>5.6 What does the testing directory contain?</h2> - -<p> -Packages are installed into the `testing' directory after they have undergone -some degree of testing in <a href="#s-unstable">unstable</a>. -</p> - -<p> -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. -</p> - -<p> -More information about the status of "testing" in general and the -individual packages is available at <code><a -href="http://www.debian.org/devel/testing">http://www.debian.org/devel/testing</a></code> -</p> - -<hr> - -<h3><a name="s-frozen"></a>5.6.1 What about "testing"? How is it `frozen'?</h3> - -<p> -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". -</p> - -<p> -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. -</p> - -<p> -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 <code><a -href="http://www.debian.org/releases/testing/">current testing release -information</a></code>. -</p> - -<p> -Once that bug count lowers to maximum acceptable values, the frozen -"testing" distribution is declared "stable" and released -with a version number. -</p> - -<p> -With each new release, the previous "stable" distribution becomes -obsolete and moves to the archive. For more information please see <code><a -href="http://www.debian.org/distrib/archive">Debian archive</a></code>. -</p> - -<hr> - -<h2><a name="s-unstable"></a>5.7 What does the unstable directory contain?</h2> - -<p> -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 :-) -</p> - -<p> -There are also main, contrib and non-free subdirectories in `unstable', -separated on the same criteria as in `stable'. -</p> - -<hr> - -<h2><a name="s-archsections"></a>5.8 What are all those directories inside <samp>dists/stable/main</samp>?</h2> - -<p> -Within each of the major directory trees[<a href="footnotes.en.html#f2" -name="fr2">2</a>], there are three sets of subdirectories containing index -files. -</p> - -<p> -There's one set of <samp>binary-<var>something</var></samp> subdirectories -which contain index files for binary packages of each available computer -architecture, for example <samp>binary-i386</samp> for packages which execute -on Intel x86 PC machines or <samp>binary-sparc</samp> for packages which -execute on Sun SPARCStations. -</p> - -<p> -The complete list of available architectures for each release is available at -<code><a href="http://www.debian.org/releases/">the release's web -page</a></code>. For the current release, please see <a -href="ch-compat.en.html#s-arches">On what hardware architectures/systems does -Debian GNU/Linux run?, Section 3.1</a>. -</p> - -<p> -The index files in binary-* are called Packages(.gz) and they include a summary -of each binary package that is included in that distribution. The actual -binary packages (for <em>woody</em> and subsequent releases) reside in the top -level <a href="#s-pools"><samp>pool</samp> directory</a>. -</p> - -<p> -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). -</p> - -<p> -Last but not least, there's a set of subdirectories meant for the installation -system index files. In the <em>woody</em> release, these are named -<samp>disks-<var>architecture</var></samp>; in <em>sarge</em>, they are at -<samp>debian-installer/binary-<var>architecture</var></samp>. -</p> - -<hr> - -<h2><a name="s-source"></a>5.9 Where is the source code?</h2> - -<p> -Source code is included for everything in the Debian system. Moreover, the -license terms of most programs in the system <em>require</em> that source code -be distributed along with the programs, or that an offer to provide the source -code accompany the programs. -</p> - -<p> -The source code is distributed in the <samp>pool</samp> directory (see <a -href="#s-pools">What's in the <samp>pool</samp> directory?, Section 5.10</a>) -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 <samp>apt-get source mypackagename</samp>. -</p> - -<p> -Some packages are only distributed as source code due to the restrictions in -their licenses. Notably, one such package is <samp>pine</samp>, see <a -href="ch-software.en.html#s-pine">Where is pine?, Section 4.10</a> for more -information. -</p> - -<p> -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. -</p> - -<hr> - -<h2><a name="s-pools"></a>5.10 What's in the <samp>pool</samp> directory?</h2> - -<p> -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. -</p> - -<p> -You can find out where each package is placed by executing a command like -<samp>apt-cache showsrc mypackagename</samp> and looking at the `Directory:' -line. For example, the <samp>apache</samp> packages are stored in -<samp>pool/main/a/apache/</samp>. -</p> - -<p> -Additionally, since there are so many <samp>lib*</samp> packages, these are -treated specially: for instance, libpaper packages are stored in -<samp>pool/main/libp/libpaper/</samp>. -</p> - -<p> -[<a href="footnotes.en.html#f3" name="fr3">3</a>] -</p> - -<hr> - -<h2><a name="s-incoming"></a>5.11 What is "incoming"?</h2> - -<p> -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. -</p> - -<p> -Usually nobody should install things from this place. However, in some rare -cases of emergency, the incoming directory is available at <code><a -href="http://incoming.debian.org/">http://incoming.debian.org/</a></code>. You -can manually fetch packages, check the GPG signature and MD5sums in the -.changes and .dsc files, and then install them. -</p> - -<hr> - -<h2><a name="s-ownrepository"></a>5.12 How do I set up my own apt-able repository?</h2> - -<p> -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 <code><a -href="http://www.debian.org/doc/manuals/repository-howto/repository-howto">Debian -Repository HOWTO</a></code>. -</p> - -<hr> - -<p> -[ <a href="ch-software.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ 5 ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-pkg_basics.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-getting.en.html b/includes/sid/common/doc/FAQ/html/ch-getting.en.html deleted file mode 100644 index fe19d08..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-getting.en.html +++ /dev/null @@ -1,374 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Getting and installing Debian GNU/Linux</title> - -</head> - -<body> - -<p><a name="ch-getting"></a></p> -<hr> - -<p> -[ <a href="ch-basic_defs.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ 2 ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-compat.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 2 - Getting and installing Debian GNU/Linux -</h1> - -<hr> - -<p> -The official document giving installation instructions is the <code><a -href="http://www.debian.org/releases/stable/installmanual">Debian GNU/Linux -Installation Guide</a></code>. We'll give some additional notes about getting -and installing Debian GNU/Linux here. -</p> - -<hr> - -<h2><a name="s-version"></a>2.1 What is the latest version of Debian?</h2> - -<p> -Currently there are three versions of Debian GNU/Linux: -</p> -<dl> -<dt><em>release 4.0, a.k.a. the `stable' distribution</em></dt> -<dd> -<p> -This is stable and well tested software, it changes if major security or -usability fixes are incorporated. -</p> -</dd> -</dl> -<dl> -<dt><em>the `testing' distribution</em></dt> -<dd> -<p> -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'. -</p> -</dd> -</dl> -<dl> -<dt><em>the `unstable' distribution</em></dt> -<dd> -<p> -This is the version currently under development; it is updated continuously. -You can retrieve packages from the `unstable' archive on any Debian FTP site -and use them to upgrade your system at any time, but you may not expect the -system to be as usable or as stable as before - that's why it's called -`<strong>unstable</strong>'! -</p> -</dd> -</dl> - -<p> -Please see <a href="ch-ftparchives.en.html#s-dists">How many Debian -distributions are there in the <samp>dists</samp> directory?, Section 5.2</a> -for more information. -</p> - -<hr> - -<h2><a name="s-updatestable"></a>2.2 Are there package upgrades in `stable'?</h2> - -<p> -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 <code><a -href="ftp://security.debian.org">security.debian.org</a></code>. -</p> - -<p> -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. -</p> - -<p> -For more information related to security support please read the <code><a -href="http://www.debian.org/security/faq">Security FAQ</a></code> or the -<code><a href="http://www.debian.org/doc/manuals/securing-debian-howto/">Debian -Security Manual</a></code>. -</p> - -<hr> - -<h2><a name="s-boot-floppies"></a>2.3 Where/how can I get the Debian installation disks?</h2> - -<p> -You can get the installation disks by downloading the appropriate files from -one of the <code><a href="http://www.debian.org/mirror/list">Debian -mirrors</a></code>. -</p> - -<p> -The installation system files are separated in subdirectories of -<code>dists/stable/main</code> directory, and the names of these subdirectories -correspond to your architecture like this: <samp>disks-<var>arch</var></samp> -(<var>arch</var> is "i386", "sparc", etc, check the site -for an exact list). In each of these architecture subdirectories there can be -several directories, each for a version of the installation system, and the -currently used one is in the `current' directory (that's a symbolic link). -</p> - -<p> -See the <code>README.txt</code> file in that directory for further -instructions. -</p> - -<hr> - -<h2><a name="s-cdrom"></a>2.4 How do I install the Debian from CD-ROMs?</h2> - -<p> -Linux supports the ISO 9660 (CD-ROM) file system with Rock Ridge extensions -(formerly known as "High Sierra"). Several <code><a -href="http://www.debian.org/CD/vendors/">vendors</a></code> provide Debian -GNU/Linux in this format. -</p> - -<p> -Warning: When installing from CD-ROM, it is usually not a good idea to choose -dselect's <samp>cdrom</samp> access method. This method is usually very slow. -The <samp>mountable</samp> and <samp>apt</samp> methods, for example, are much -better for installing from CD-ROM (see <a -href="ch-uptodate.en.html#s-dpkg-mountable">dpkg-mountable, Section 8.2.5</a> -and <a href="ch-uptodate.en.html#s-apt">apt-get, dselect and apt-cdrom, Section -8.2.2</a>). -</p> - -<hr> - -<h2><a name="s-cdimage-symlinks"></a>2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!</h2> - -<p> -Official Debian CD images indeed contain symlinks like: -</p> - -<pre> - /dists/frozen -> sarge/ - /dists/stable -> sarge/ - /dists/testing -> sarge/ - /dists/unstable -> sarge/ -</pre> - -<p> -so that they work when your sources.list has an entry like -</p> - -<pre> - deb cdrom:[<name as on cd label>]/ unstable main [...] -</pre> - -<p> -. -</p> - -<p> -The fact these symlinks are present does <em>not</em> mean the image is -`unstable' or `testing' or anything. Read the CD label in -<code>/.disk/info</code> to find out which Debian version it contains. This -information is also present in <code>/README.txt</code> on the CD. -</p> - -<p> -Read <code><a -href="http://www.debian.org/releases/">http://www.debian.org/releases/</a></code> -to find out what the current `stable' and `testing' releases are. -</p> - -<hr> - -<h2><a name="s-cdimages"></a>2.6 I have my own CD-writer, are there CD images available somewhere?</h2> - -<p> -Yes. To make it easier for CD vendors to provide high quality disks, we -provide the <code><a href="http://cdimage.debian.org/">Official CD -images</a></code>. -</p> - -<hr> - -<h2><a name="s-floppy"></a>2.7 Can I install it from a pile of floppy disks?</h2> - -<p> -First of all, a warning: whole Debian GNU/Linux is way too large to be -installed from media as small as a standard 1.44MB floppy disk - you may not -find installing from floppies a very pleasant experience. -</p> - -<p> -Copy the Debian packages onto formatted floppy disks. Either a DOS, the native -Linux "ext2", or the "minix" format will do; one just has -to use a mount command appropriate to the floppy being used. -</p> - -<p> -Using floppy disks has these complications: -</p> -<ul> -<li> -<p> -Short MS-DOS file names: If you are trying to place Debian package files onto -MS-DOS formatted disks, you will find that their names are generally too long, -and do not conform to the MS-DOS 8.3 filename limitation. To overcome this, -you would have to use VFAT formatted disks, since VFAT supports longer file -names. -</p> -</li> -</ul> -<ul> -<li> -<p> -Large file sizes: Some packages are larger than 1.44 MBytes, and will not fit -onto a single floppy disk. To solve this problem, use the dpkg-split tool (see -<a href="ch-pkgtools.en.html#s-dpkg-split">dpkg-split, Section 7.1.5.2</a>), -available in the <samp>tools</samp> directory on <code><a -href="http://www.debian.org/mirror/list">Debian mirrors</a></code>. -</p> -</li> -</ul> - -<p> -You must have support in the kernel for floppy disks in order to read and write -to floppy disk; most kernels come with floppy drive support included in them. -</p> - -<p> -To mount a floppy disk under the mount point <samp>/floppy</samp> (a directory -which should have been created during installation), use: -</p> -<ul> -<li> -<pre> - mount -t msdos /dev/fd0 /floppy/ -</pre> - -<p> -if the floppy disk is in drive A: and has an MS-DOS file system, -</p> -</li> -</ul> -<ul> -<li> -<pre> - mount -t msdos /dev/fd1 /floppy/ -</pre> - -<p> -if the floppy disk is in drive B: and has an MS-DOS file system, -</p> -</li> -</ul> -<ul> -<li> -<pre> - mount -t ext2 /dev/fd0 /floppy/ -</pre> - -<p> -if the floppy disk is in drive A: and has an ext2 (i.e., a normal Linux) file -system. -</p> -</li> -</ul> - -<hr> - -<h2><a name="s-remoteinstall"></a>2.8 Can I get and install Debian directly from a remote Internet site?</h2> - -<p> -Yes. You can boot the Debian installation system from a set of files you can -download from our FTP site and its mirrors. -</p> - -<p> -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 <code><a -href="http://www.debian.org/CD/netinst/">http://www.debian.org/CD/netinst/</a></code>. -</p> - -<p> -You can also download even smaller floppy disk image files, create bootable -diskettes from them, start the installation procedure and get the rest of -Debian over the network. For more information, please see <code><a -href="http://www.debian.org/distrib/floppyinst">http://www.debian.org/distrib/floppyinst</a></code>. -</p> - -<hr> - -<p> -[ <a href="ch-basic_defs.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ 2 ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-compat.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-kernel.en.html b/includes/sid/common/doc/FAQ/html/ch-kernel.en.html deleted file mode 100644 index 28e150f..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-kernel.en.html +++ /dev/null @@ -1,315 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Debian and the kernel</title> - -</head> - -<body> - -<p><a name="ch-kernel"></a></p> -<hr> - -<p> -[ <a href="ch-uptodate.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ 9 ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-customizing.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 9 - Debian and the kernel -</h1> - -<hr> - -<h2><a name="s-non-debian-kernel"></a>9.1 Can I install and compile a kernel without some Debian-specific tweaking?</h2> - -<p> -Yes. -</p> - -<p> -There's only one common catch: the Debian C libraries are built with the most -recent <em>stable</em> releases of the <strong>kernel</strong> headers. If you -happen to need to compile a program with kernel headers newer than the ones -from the stable branch, then you should either upgrade the package containing -the headers (<code>libc6-dev</code>), or use the new headers from an unpacked -tree of the newer kernel. That is, if the kernel sources are in -<code>/usr/src/linux</code>, then you should add -<samp>-I/usr/src/linux/include/</samp> to your command line when compiling. -</p> - -<hr> - -<h2><a name="s-customkernel"></a>9.2 What tools does Debian provide to build custom kernels?</h2> - -<p> -Users who wish to (or must) build a custom kernel are encouraged to download -the package <code>kernel-package</code>. This package contains the script to -build the kernel package, and provides the capability to create a Debian -<code>kernel-image-<var>version</var></code> package just by running the -command -</p> - -<pre> - make-kpkg kernel_image -</pre> - -<p> -in the top-level kernel source directory. Help is available by executing the -command -</p> - -<pre> - make-kpkg --help -</pre> - -<p> -and through the manual page <code>make-kpkg(1)</code>. -</p> - -<p> -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 -<code>kernel-source-<var>version</var></code> package is available (where -<var>version</var> stands for the kernel version). -</p> - -<p> -Detailed instructions for using the <code>kernel-package</code> package are -given in the file <code>/usr/share/doc/kernel-package/README.gz</code>. -Briefly, one should: -</p> -<ul> -<li> -<p> -Unpack the kernel sources, and <samp>cd</samp> to the newly created directory. -</p> -</li> -</ul> -<ul> -<li> -<p> -Modify the kernel configuration using one of these commands: -</p> -<ul> -<li> -<p> -<samp>make config</samp> (for a text-based interface). -</p> -</li> -</ul> -<ul> -<li> -<p> -<samp>make menuconfig</samp> (for an ncurses-based menu driven interface). -Note that to use this option, the <code>libncurses5-dev</code> package must be -installed. -</p> -</li> -</ul> -<ul> -<li> -<p> -<samp>make xconfig</samp> (for an X11 interface). Using this option requires -that relevant X and Tcl/Tk packages be installed. -</p> -</li> -</ul> - -<p> -Any of the above steps generates a new <samp>.config</samp> in the top-level -kernel source directory. -</p> -</li> -</ul> -<ul> -<li> -<p> -Execute the command: <samp>make-kpkg -rev Custom.<var>N</var> -kernel_image</samp>, where <var>N</var> is a revision number assigned by the -user. The new Debian archive thus formed would have revision -Custom.<var>N</var>, e.g. <code>kernel-image-2.2.14_Custom.1_i386.deb</code> -for the Linux kernel 2.2.14 on i386. -</p> -</li> -</ul> -<ul> -<li> -<p> -Install the package created. -</p> -<ul> -<li> -<p> -Run <samp>dpkg --install -../kernel-image-<var>VVV</var>_Custom.<var>N</var>_i386.deb</samp> to install -the kernel itself. The installation script will: -</p> -<ul> -<li> -<p> -run the boot loader (grub, LILO or some other) if needed, -</p> -</li> -</ul> -<ul> -<li> -<p> -install the custom kernel in -<code>/boot/vmlinuz_<var>VVV</var>-Custom.<var>N</var></code>, and set up -appropriate symbolic links to the most recent kernel version. -</p> -</li> -</ul> -<ul> -<li> -<p> -prompt the user to make a boot floppy. This boot floppy will contain the raw -kernel only. See <a href="#s-custombootdisk">How can I make a custom boot -floppy?, Section 9.3</a>. -</p> -</li> -</ul> -</li> -</ul> -<ul> -<li> -<p> -To employ secondary boot loaders such as <code>loadlin</code>, copy this image -to other locations (e.g. to an <samp>MS-DOS</samp> partition). -</p> -</li> -</ul> -</li> -</ul> - -<hr> - -<h2><a name="s-custombootdisk"></a>9.3 How can I make a custom boot floppy?</h2> - -<p> -This task is greatly aided by the Debian package <code>boot-floppies</code>, -normally found in the <samp>admin</samp> section of the Debian FTP archive. -Shell scripts in this package produce boot floppies in the -<samp>SYSLINUX</samp> format. These are <samp>MS-DOS</samp> 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 -<code>syslinux.cfg</code> file on the floppy). Other scripts in this package -produce emergency root disks and can even reproduce the base disks. -</p> - -<p> -You will find more information about this in the -<code>/usr/share/doc/boot-floppies/README</code> file after installing the -<code>boot-floppies</code> package. -</p> - -<hr> - -<h2><a name="s-modules"></a>9.4 What special provisions does Debian provide to deal with modules?</h2> - -<p> -Debian's <code>modconf</code> package provides a shell script -(<code>/usr/sbin/modconf</code>) 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 -<code>/etc/modules.conf</code> (which lists aliases, and other arguments that -must be used in conjunction with various modules) through files in -<code>/etc/modutils/</code>, and <code>/etc/modules</code> (which lists the -modules that must be loaded at boot time). -</p> - -<p> -Like the (new) <code>Configure.help</code> files that are now available to -support the construction of custom kernels, the <code>modconf</code> package -comes with a series of help files (in <code>/usr/lib/modules_help/</code>) -which provide detailed information on appropriate arguments for each of the -modules. -</p> - -<hr> - -<h2><a name="s-removeoldkernel"></a>9.5 Can I safely de-install an old kernel package, and if so, how?</h2> - -<p> -Yes. The <code>kernel-image-<var>NNN</var>.prerm</code> 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: -</p> - -<pre> - dpkg --purge --force-remove-essential kernel-image-<var>NNN</var> -</pre> - -<p> -(replace <var>NNN</var> with your kernel version and revision number, of -course) -</p> - -<hr> - -<p> -[ <a href="ch-uptodate.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ 9 ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-customizing.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-nexttime.en.html b/includes/sid/common/doc/FAQ/html/ch-nexttime.en.html deleted file mode 100644 index 2df0e3f..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-nexttime.en.html +++ /dev/null @@ -1,147 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Changes expected in the next major release of Debian</title> - -</head> - -<body> - -<p><a name="ch-nexttime"></a></p> -<hr> - -<p> -[ <a href="ch-redistrib.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ 14 ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-faqinfo.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 14 - Changes expected in the next major release of Debian -</h1> - -<hr> - -<h2><a name="s-security"></a>14.1 Increased security</h2> - -<p> -Debian contains support for shadow passwords since release 1.3. In addition, -the Linux library of Pluggable Authentication Modules (a.k.a. <code><a -href="http://www.kernel.org/pub/linux/libs/pam/">libpam</a></code>;) that -allows sysadmins to choose authorization modes on an application-specific basis -is available, and initially set to authenticate via shadow password. -</p> - -<p> -Including full support for additional security enhancements for mandatory -access control mechanisms such as SElinux, RSBAC and buffer overflow protection -like Exec-shield or PaX is still in progress. -</p> - -<hr> - -<h2><a name="s-i18n"></a>14.2 Extended support for non-English users</h2> - -<p> -Debian already has very good support for non-English users, see <a -href="ch-software.en.html#s-nonenglish">How does Debian support non-English -languages?, Section 4.8</a>. -</p> - -<p> -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. -</p> - -<p> -The GNU Translation Project <code><a -href="ftp://ftp.gnu.org/pub/gnu/ABOUT-NLS">ftp://ftp.gnu.org/pub/gnu/ABOUT-NLS</a></code> -works on internationalizing the GNU programs. -</p> - -<hr> - -<h2><a name="s-morearches"></a>14.3 More architectures</h2> - -<p> -Complete Debian system on other architectures such as AMD64 or 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 <samp>sid</samp>. -</p> - -<hr> - -<h2><a name="s-morekernels"></a>14.4 More kernels</h2> - -<p> -In addition to Debian GNU/Hurd, Debian is being ported also to BSD kernels, -namely to <code><a href="http://www.debian.org/ports/netbsd">NetBSD</a></code>. -</p> - -<hr> - -<p> -[ <a href="ch-redistrib.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ 14 ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-faqinfo.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-pkg_basics.en.html b/includes/sid/common/doc/FAQ/html/ch-pkg_basics.en.html deleted file mode 100644 index a26e8ee..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-pkg_basics.en.html +++ /dev/null @@ -1,863 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Basics of the Debian package management system</title> - -</head> - -<body> - -<p><a name="ch-pkg_basics"></a></p> -<hr> - -<p> -[ <a href="ch-ftparchives.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ 6 ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-pkgtools.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 6 - Basics of the Debian package management system -</h1> - -<hr> - -<h2><a name="s-package"></a>6.1 What is a Debian package?</h2> - -<p> -Packages generally contain all of the files necessary to implement a set of -related commands or features. There are two types of Debian packages: -</p> -<ul> -<li> -<p> -<em>Binary packages</em>, which contain executables, configuration files, -man/info pages, copyright information, and other documentation. These packages -are distributed in a Debian-specific archive format (see <a -href="#s-deb-format">What is the format of a Debian binary package?, Section -6.2</a>); they are usually distinguished by having a '.deb' file extension. -Binary packages can be unpacked using the Debian utility <samp>dpkg</samp>; -details are given in its manual page. -</p> -</li> -</ul> -<ul> -<li> -<p> -<em>Source packages</em>, which consist of a <samp>.dsc</samp> file describing -the source package (including the names of the following files), a -<samp>.orig.tar.gz</samp> file that contains the original unmodified source in -gzip-compressed tar format and usually a <samp>.diff.gz</samp> file that -contains the Debian-specific changes to the original source. The utility -<samp>dpkg-source</samp> packs and unpacks Debian source archives; details are -provided in its manual page. -</p> -</li> -</ul> - -<p> -Installation of software by the package system uses "dependencies" -which are carefully designed by the package maintainers. These dependencies -are documented in the <samp>control</samp> file associated with each package. -For example, the package containing the GNU C compiler (<code>gcc</code>) -"depends" on the package <code>binutils</code> which includes the -linker and assembler. If a user attempts to install <code>gcc</code> without -having first installed <code>binutils</code>, the package management system -(dpkg) will send an error message that it also needs <code>binutils</code>, and -stop installing <code>gcc</code>. (However, this facility can be overridden by -the insistent user, see <code>dpkg(8)</code>.) See more in <a -href="#s-depends">What is meant by saying that a package <em>Depends</em>, -<em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> -or <em>Provides</em> another package?, Section 6.9</a> below. -</p> - -<p> -Debian's packaging tools can be used to: -</p> -<ul> -<li> -<p> -manipulate and manage packages or parts of packages, -</p> -</li> -</ul> -<ul> -<li> -<p> -aid the user in the break-up of packages that must be transmitted through a -limited-size medium such as floppy disks, -</p> -</li> -</ul> -<ul> -<li> -<p> -aid developers in the construction of package archives, and -</p> -</li> -</ul> -<ul> -<li> -<p> -aid users in the installation of packages which reside on a remote FTP site. -</p> -</li> -</ul> - -<hr> - -<h2><a name="s-deb-format"></a>6.2 What is the format of a Debian binary package?</h2> - -<p> -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 <samp>.deb</samp>. -</p> - -<p> -The internals of this Debian binary packages format are described in the -<code>deb(5)</code> manual page. This internal format is subject to change -(between major releases of Debian GNU/Linux), therefore please always use -<code>dpkg-deb(1)</code> for manipulating <samp>.deb</samp> files. -</p> - -<hr> - -<h2><a name="s-pkgname"></a>6.3 Why are Debian package file names so long?</h2> - -<p> -The Debian binary package file names conform to the following convention: -<foo>_<VersionNumber>-<DebianRevisionNumber>.deb -</p> - -<p> -Note that <samp>foo</samp> 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: -</p> -<ul> -<li> -<p> -inspect the "Packages" file in the directory where it was stored at a -Debian FTP archive site. This file contains a stanza describing each package; -the first field in each stanza is the formal package name. -</p> -</li> -</ul> -<ul> -<li> -<p> -use the command <samp>dpkg --info foo_VVV-RRR.deb</samp> (where VVV and RRR are -the version and revision of the package in question, respectively). This -displays, among other things, the package name corresponding to the archive -file being unpacked. -</p> -</li> -</ul> - -<p> -The <samp>VVV</samp> 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". -</p> - -<p> -The <samp>RRR</samp> 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 (<samp>debian/rules</samp>), the Debian control file -(<samp>debian/control</samp>), the installation or removal scripts -(<samp>debian/p*</samp>), or in the configuration files used with the package. -</p> - -<hr> - -<h2><a name="s-controlfile"></a>6.4 What is a Debian control file?</h2> - -<p> -Specifics regarding the contents of a Debian control file are provided in the -Debian Policy Manual, section 5, see <a -href="ch-support.en.html#s-debiandocs">What other documentation exists on and -for a Debian system?, Section 11.1</a>. -</p> - -<p> -Briefly, a sample control file is shown below for the Debian package hello: -</p> - -<pre> - 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). -</pre> - -<p> -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. -</p> - -<p> -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 <a href="#s-pkgname">Why are Debian package file names so long?, -Section 6.3</a>. -</p> - -<p> -The Architecture field specifies the chip for which this particular binary was -compiled. -</p> - -<p> -The Depends field gives a list of packages that have to be installed in order -to install this package successfully. -</p> - -<p> -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. -</p> - -<p> -The Section line gives the "section" where this Debian package is -stored at the Debian FTP sites. This is the name of a subdirectory (within one -of the main directories, see <a href="ch-ftparchives.en.html#s-dirtree">What -are all those directories at the Debian FTP archives?, Section 5.1</a>) where -the package is stored. -</p> - -<p> -The Priority indicates how important is this package for installation, so that -semi-intelligent software like dselect or console-apt can sort the package into -a category of e.g. packages optionally installed. See <a -href="#s-priority">What is an <em>Essential</em> <em>Required</em>, -<em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> -package?, Section 6.7</a>. -</p> - -<p> -The Maintainer field gives the e-mail address of the person who is currently -responsible for maintaining this package. -</p> - -<p> -The Description field gives a brief summary of the package's features. -</p> - -<p> -For more information about all possible fields a package can have, please see -the Debian Policy Manual, section 5., "Control files and their -fields". -</p> - -<hr> - -<h2><a name="s-conffile"></a>6.5 What is a Debian conffile?</h2> - -<p> -Conffiles is a list of configuration files (usually placed in -<samp>/etc</samp>) 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. -</p> - -<p> -To determine exactly which files are preserved during an upgrade, run: -</p> - -<pre> - dpkg --status package -</pre> - -<p> -And look under "Conffiles:". -</p> - -<hr> - -<h2><a name="s-maintscripts"></a>6.6 What is a Debian preinst, postinst, prerm, and postrm script?</h2> - -<p> -These files are executable scripts which are automatically run before or after -a package is installed. Along with a file named <samp>control</samp>, all of -these files are part of the "control" section of a Debian archive -file. -</p> - -<p> -The individual files are: -</p> -<dl> -<dt>preinst</dt> -<dd> -<p> -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). -</p> -</dd> -</dl> -<dl> -<dt>postinst</dt> -<dd> -<p> -This script typically completes any required configuration of the package -<samp>foo</samp> once <samp>foo</samp> 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. -</p> -</dd> -</dl> -<dl> -<dt>prerm</dt> -<dd> -<p> -This script typically stops any daemons which are associated with a package. -It is executed before the removal of files associated with the package. -</p> -</dd> -</dl> -<dl> -<dt>postrm</dt> -<dd> -<p> -This script typically modifies links or other files associated with -<samp>foo</samp>, and/or removes files created by the package. (Also see <a -href="#s-virtual">What is a Virtual Package?, Section 6.8</a>.) -</p> -</dd> -</dl> - -<p> -Currently all of the control files can be found in directory -<samp>/var/lib/dpkg/info</samp>. The files relevant to package -<samp>foo</samp> begin with the name "foo" and have file extensions -of "preinst", "postinst", etc., as appropriate. The file -<samp>foo.list</samp> in that directory lists all of the files that were -installed with the package <samp>foo</samp>. (Note that the location of these -files is a dpkg internal; you should not rely on it.) -</p> - -<hr> - -<h2><a name="s-priority"></a>6.7 What is an <em>Essential</em> <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?</h2> - -<p> -Each Debian package is assigned a <em>priority</em> by the distribution -maintainers, as an aid to the package management system. The priorities are: -</p> -<ul> -<li> -<p> -<strong>Required</strong>: packages that are necessary for the proper -functioning of the system. -</p> - -<p> -This includes all tools that are necessary to repair system defects. You must -not remove these packages or your system may become totally broken and you may -probably not even be able to use dpkg to put things back. Systems with only -the Required packages are probably unusable, but they do have enough -functionality to allow the sysadmin to boot and install more software. -</p> -</li> -</ul> -<ul> -<li> -<p> -<strong>Important</strong> packages should be found on any Unix-like system. -</p> - -<p> -Other packages which the system will not run well or be usable without will be -here. This does <em>NOT</em> include Emacs or X11 or TeX or any other large -applications. These packages only constitute the bare infrastructure. -</p> -</li> -</ul> -<ul> -<li> -<p> -<strong>Standard</strong> packages are standard on any Linux system, including -a reasonably small but not too limited character-mode system. Tools are -included to be able to browse the web (using w3m), send e-mail (with mutt) and -download files from FTP servers. -</p> - -<p> -This is what will install by default if users do not select anything else. It -does not include many large applications, but it does include the Python -interpreter and some server software like OpenSSH (for remote administration), -Exim (for mail delivery, although it can be configured for local delivery -only), an identd server (pidentd) and the RPC portmapper -(<samp>portmap</samp>). It also includes some common generic documentation -that most users will find helpful. -</p> -</li> -</ul> -<ul> -<li> -<p> -<strong>Optional</strong> packages include all those that you might reasonably -want to install if you did not know what it was, or do not have specialized -requirements. -</p> - -<p> -This includes X11, a full TeX distribution, and lots of applications. -</p> -</li> -</ul> -<ul> -<li> -<p> -<strong>Extra</strong>: packages that either conflict with others with higher -priorities, are only likely to be useful if you already know what they are, or -have specialized requirements that make them unsuitable for -"Optional". -</p> -</li> -</ul> - -<p> -If you do a default Debian installation all the packages of priority -<strong>Standard</strong> or higher will be installed in your system. If you -select pre-defined tasks you will get lower priority packages too. -</p> - -<p> -Additionally, some packages are marked as <strong>Essential</strong> since they -are absolutely necessary for the proper functioning of the system. The package -management tools will refuse to remove these. -</p> - -<hr> - -<h2><a name="s-virtual"></a>6.8 What is a Virtual Package?</h2> - -<p> -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 <samp>tin</samp> and <samp>trn</samp> 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 <samp>news-reader</samp>. -</p> - -<p> -Similarly, <samp>smail</samp> and <samp>sendmail</samp> 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 -<samp>mail-transport-agent</samp> will be satisfied by the existence of this -virtual package. -</p> - -<p> -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 -<samp>update-alternatives</samp>, and is described further in <a -href="ch-customizing.en.html#s-diverse">Some users like mawk, others like gawk; -some like vim, others like elvis; some like trn, others like tin; how does -Debian support diversity?, Section 10.10</a>. -</p> - -<hr> - -<h2><a name="s-depends"></a>6.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?</h2> - -<p> -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: -</p> -<ul> -<li> -<p> -Package A <em>depends</em> on Package B if B absolutely must be installed in -order to run A. In some cases, A depends not only on B, but on a version of B. -In this case, the version dependency is usually a lower limit, in the sense -that A depends on any version of B more recent than some specified version. -</p> -</li> -</ul> -<ul> -<li> -<p> -Package A <em>recommends</em> Package B, if the package maintainer judges that -most users would not want A without also having the functionality provided by -B. -</p> -</li> -</ul> -<ul> -<li> -<p> -Package A <em>suggests</em> Package B if B contains files that are related to -(and usually enhance) the functionality of A. -</p> -</li> -</ul> -<ul> -<li> -<p> -Package A <em>conflicts</em> with Package B when A will not operate if B is -installed on the system. Most often, conflicts are cases where A contains -files which are an improvement over those in B. "Conflicts" are -often combined with "replaces". -</p> -</li> -</ul> -<ul> -<li> -<p> -Package A <em>replaces</em> Package B when files installed by B are removed and -(in some cases) over-written by files in A. -</p> -</li> -</ul> -<ul> -<li> -<p> -Package A <em>provides</em> Package B when all of the files and functionality -of B are incorporated into A. This mechanism provides a way for users with -constrained disk space to get only that part of package A which they really -need. -</p> -</li> -</ul> - -<p> -More detailed information on the use of each these terms can be found in the -Policy manual. -</p> - -<hr> - -<h2><a name="s-pre-depends"></a>6.10 What is meant by Pre-Depends?</h2> - -<p> -"Pre-Depends" is a special dependency. In the case of most packages, -<samp>dpkg</samp> will unpack its archive file (i.e., its <samp>.deb</samp> -file) independently of whether or not the files on which it depends exist on -the system. Simplistically, unpacking means that <samp>dpkg</samp> will -extract the files from the archive file that were meant to be installed on your -file system, and put them in place. If those packages <em>depend</em> on the -existence of some other packages on your system, <samp>dpkg</samp> will refuse -to complete the installation (by executing its "configure" action) -until the other packages are installed. -</p> - -<p> -However, for some packages, <samp>dpkg</samp> 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 -<samp>a.out</samp> format to <samp>ELF</samp> format, where the <em>order</em> -in which packages were unpacked was critical. There are other large upgrade -situations where this method is useful, e.g. the packages with the required -priority and their LibC dependency. -</p> - -<p> -As before, more detailed information about this can be found in the Policy -manual. -</p> - -<hr> - -<h2><a name="s-pkgstatus"></a>6.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em> <em>purge</em> and <em>hold</em> in the package status?</h2> - -<p> -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 -<samp>dselect</samp>, or by the user's direct invocations of -<samp>dpkg</samp>). -</p> - -<p> -Their meanings are: -</p> -<ul> -<li> -<p> -unknown - the user has never indicated whether he wants the package -</p> -</li> -</ul> -<ul> -<li> -<p> -install - the user wants the package installed or upgraded -</p> -</li> -</ul> -<ul> -<li> -<p> -remove - the user wants the package removed, but does not want to remove any -existing configuration files. -</p> -</li> -</ul> -<ul> -<li> -<p> -purge - the user wants the package to be removed completely, including its -configuration files. -</p> -</li> -</ul> -<ul> -<li> -<p> -hold - the user wants this package not to be processed, i.e., he wants to keep -the current version with the current status whatever that is. -</p> -</li> -</ul> - -<hr> - -<h2><a name="s-puttingonhold"></a>6.12 How do I put a package on hold?</h2> - -<p> -There are three ways of holding back packages, with dpkg, aptitude or with -dselect. -</p> - -<p> -With dpkg, you just have to export the list of package selections, with: -</p> - -<pre> - dpkg --get-selections \* > selections.txt -</pre> - -<p> -Then edit the resulting file <code>selections.txt</code>, change the line -containing the package you wish to hold, e.g. <code>libc6</code>, from this: -</p> - -<pre> - libc6 install -</pre> - -<p> -to this: -</p> - -<pre> - libc6 hold -</pre> - -<p> -Save the file, and reload it into dpkg database with: -</p> - -<pre> - dpkg --set-selections < selections.txt -</pre> - -<p> -With aptitude, you can hold a package using -</p> - -<pre> - aptitude hold package_name -</pre> - -<p> -and remove the hold with -</p> - -<pre> - aptitude unhold package_name -</pre> - -<p> -With dselect, you just have to enter the [S]elect screen, find the package you -wish to hold in its present state, and press the `=' key (or `H'). The changes -will go live immediately after you exit the [S]elect screen. -</p> - -<hr> - -<h2><a name="s-sourcepkgs"></a>6.13 How do I install a source package?</h2> - -<p> -Debian source packages can't actually be "installed", they are just -unpacked in whatever directory you want to build the binary packages they -produce. -</p> - -<p> -Source packages are distributed on most of the same mirrors where you can -obtain the binary packages. If you set up your APT's -<code>sources.list(5)</code> to include the appropriate "deb-src" -lines, you'll be able to easily download any source packages by running -</p> - -<pre> - apt-get source foo -</pre> - -<p> -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 -</p> - -<pre> - apt-get build-dep foo -</pre> - -<p> -before building the source. -</p> - -<hr> - -<h2><a name="s-sourcebuild"></a>6.14 How do I build binary packages from a source package?</h2> - -<p> -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). -</p> - -<p> -Once you have them (<a href="#s-sourcepkgs">How do I install a source package?, -Section 6.13</a>), if you have the <code>dpkg-dev</code> package installed, the -following command: -</p> - -<pre> - dpkg-source -x foo_version-revision.dsc -</pre> - -<p> -will extract the package into a directory called <samp>foo-version</samp>. -</p> - -<p> -If you want just to compile the package, you may cd into -<samp>foo-version</samp> directory and issue the command -</p> - -<pre> - dpkg-buildpackage -rfakeroot -b -</pre> - -<p> -to build the package (note that this also requires the <code>fakeroot</code> -package), and then -</p> - -<pre> - dpkg -i ../foo_version-revision_arch.deb -</pre> - -<p> -to install the newly-built package(s). -</p> - -<hr> - -<h2><a name="s-creatingdebs"></a>6.15 How do I create Debian packages myself?</h2> - -<p> -For more detailed description on this, read the New Maintainers' Guide, -available in the <code>maint-guide</code> package, or at <code><a -href="http://www.debian.org/doc/devel-manuals#maint-guide">http://www.debian.org/doc/devel-manuals#maint-guide</a></code>. -</p> - -<hr> - -<p> -[ <a href="ch-ftparchives.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ 6 ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-pkgtools.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-pkgtools.en.html b/includes/sid/common/doc/FAQ/html/ch-pkgtools.en.html deleted file mode 100644 index 2183ae9..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-pkgtools.en.html +++ /dev/null @@ -1,936 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - The Debian package management tools</title> - -</head> - -<body> - -<p><a name="ch-pkgtools"></a></p> -<hr> - -<p> -[ <a href="ch-pkg_basics.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ 7 ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-uptodate.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 7 - The Debian package management tools -</h1> - -<hr> - -<h2><a name="s-pkgprogs"></a>7.1 What programs does Debian provide for managing its packages?</h2> - -<p> -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. -</p> - -<p> -It is important to understand that the higher level package management tools -such as <code>aptitude</code> or <code>dselect</code> rely on <code>apt</code> -which, itself, relies on <code>dpkg</code> to manage the packages in the -system. -</p> - -<p> -See the <code><a href="http://www.debian.org/doc/manuals/apt-howto/">APT -HOWTO</a></code> for more information about the Debian package management -utilities. This document is available in various languages and formats, see -<code><a href="http://www.debian.org/doc/user-manuals#apt-howto">the APT HOWTO -entry on the DDP Users' Manuals overview</a></code>. -</p> - -<hr> - -<h3><a name="s-dpkg"></a>7.1.1 dpkg</h3> - -<p> -This is the main package management program. <code>dpkg</code> can be invoked -with many options. Some common uses are: -</p> -<ul> -<li> -<p> -Find out all the options: <samp>dpkg --help</samp>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Print out the control file (and other information) for a specified package: -<samp>dpkg --info foo_VVV-RRR.deb</samp> -</p> -</li> -</ul> -<ul> -<li> -<p> -Install a package (including unpacking and configuring) onto the file system of -the hard disk: <samp>dpkg --install foo_VVV-RRR.deb</samp>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Unpack (but do not configure) a Debian archive into the file system of the hard -disk: <samp>dpkg --unpack foo_VVV-RRR.deb</samp>. Note that this operation -does <em>not</em> necessarily leave the package in a usable state; some files -may need further customization to run properly. This command removes any -already-installed version of the program and runs the preinst (see <a -href="ch-pkg_basics.en.html#s-maintscripts">What is a Debian preinst, postinst, -prerm, and postrm script?, Section 6.6</a>) script associated with the package. -</p> -</li> -</ul> -<ul> -<li> -<p> -Configure a package that already has been unpacked: <samp>dpkg --configure -foo</samp>. Among other things, this action runs the postinst (see <a -href="ch-pkg_basics.en.html#s-maintscripts">What is a Debian preinst, postinst, -prerm, and postrm script?, Section 6.6</a>) script associated with the package. -It also updates the files listed in the <samp>conffiles</samp> for this -package. Notice that the 'configure' operation takes as its argument a package -name (e.g., foo), <em>not</em> the name of a Debian archive file (e.g., -foo_VVV-RRR.deb). -</p> -</li> -</ul> -<ul> -<li> -<p> -Extract a single file named "blurf" (or a group of files named -"blurf*" from a Debian archive: <samp>dpkg --fsys-tarfile -foo_VVV-RRR.deb | tar -xf - blurf*</samp> -</p> -</li> -</ul> -<ul> -<li> -<p> -Remove a package (but not its configuration files): <samp>dpkg --remove -foo</samp>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Remove a package (including its configuration files): <samp>dpkg --purge -foo</samp>. -</p> -</li> -</ul> -<ul> -<li> -<p> -List the installation status of packages containing the string (or regular -expression) "foo*": <samp>dpkg --list 'foo*'</samp>. -</p> -</li> -</ul> - -<hr> - -<h3><a name="s-apt-get"></a>7.1.2 APT</h3> - -<p> -APT is the <em>Advanced Package Tool</em> and provides the <code>apt-get</code> -program. <code>apt-get</code> provides a simple way to retrieve and install -packages from multiple sources using the command line. Unlike -<code>dpkg</code>, <code>apt-get</code> does not understand .deb files, it -works with the packages proper name and can only install .deb archives from a -source specified in <code>/etc/apt/sources.list</code>. <code>apt-get</code> -will call <code>dpkg</code> directly after downloading the .deb archives[<a -href="footnotes.en.html#f4" name="fr4">4</a>] from the configured sources. -</p> - -<p> -Some common ways to use <code>apt-get</code> are: -</p> -<ul> -<li> -<p> -To update the list of package known by your system, you can run: -</p> - -<pre> - apt-get update -</pre> - -<p> -(you should execute this regularly to update your package lists) -</p> -</li> -</ul> -<ul> -<li> -<p> -To upgrade all the packages on your system, run: -</p> - -<pre> - apt-get upgrade -</pre> -</li> -</ul> -<ul> -<li> -<p> -To install the <var>foo</var> package and all its dependencies, run: -</p> - -<pre> - apt-get install foo -</pre> -</li> -</ul> -<ul> -<li> -<p> -To remove the foo package from your system, run: -</p> - -<pre> - apt-get remove foo -</pre> -</li> -</ul> -<ul> -<li> -<p> -To remove the foo package and its configuration files from your system, run: -</p> - -<pre> - apt-get --purge remove foo -</pre> -</li> -</ul> -<ul> -<li> -<p> -To upgrade all the packages on your system to a new Debian GNU/Linux release, -run: -</p> - -<pre> - apt-get dist-upgrade -</pre> -</li> -</ul> - -<p> -Note that you must be logged in as root to perform any commands that modify the -system packages. -</p> - -<p> -The apt tool suite also includes the <code>apt-cache</code> 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 <code>apt-cache</code> are: -</p> -<ul> -<li> -<p> -To find packages whose description contain <var>word</var>: -</p> - -<pre> - apt-cache search <var>word</var> -</pre> -</li> -</ul> -<ul> -<li> -<p> -To print the detailed information of a package: -</p> - -<pre> - apt-cache show <var>package</var> -</pre> -</li> -</ul> -<ul> -<li> -<p> -To print the packages a given package depends on: -</p> - -<pre> - apt-cache depends <var>package</var> -</pre> -</li> -</ul> -<ul> -<li> -<p> -To print detailed information of the versions available for a package and the -packages that reverse-depends on it: -</p> - -<pre> - apt-cache showpkg <var>package</var> -</pre> -</li> -</ul> - -<p> -For more information, install the <code>apt</code> package and read -<code>apt-get(8)</code>, <code>sources.list(5)</code> and install the -<code>apt-doc</code> package and read -<code>/usr/share/doc/apt-doc/guide.html/index.html</code>. -</p> - -<hr> - -<h3><a name="s-aptitude"></a>7.1.3 aptitude</h3> - -<p> -<code>aptitude</code> is a package manager for Debian GNU/Linux systems that -provides a frontend to the apt package management infrastructure. -<code>aptitude</code> is a text-based interface using the curses library, it -can be used to perform management tasks in a fast and easy way. -</p> - -<p> -<code>aptitude</code> provides the functionality of <code>dselect</code> and -<code>apt-get</code>, as well as many additional features not found in either -program: -</p> -<ul> -<li> -<p> -<code>aptitude</code> offers access to all versions of a package. -</p> -</li> -</ul> -<ul> -<li> -<p> -<code>aptitude</code> logs all its actions in <code>/var/log/aptitude</code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -<code>aptitude</code> makes it easy to keep track of obsolete software by -listing it under "Obsolete and Locally Created Packages". -</p> -</li> -</ul> -<ul> -<li> -<p> -<code>aptitude</code> includes a fairly powerful system for searching -particular packages and limiting the package display. Users familiar with -<code>mutt</code> will pick up quickly, as <code>mutt</code> was the -inspiration for the expression syntax. -</p> -</li> -</ul> -<ul> -<li> -<p> -<code>aptitude</code> tracks which packages have been installed due to -dependencies and removes them automatically when the packages that needed them -are removed from the system. -</p> -</li> -</ul> -<ul> -<li> -<p> -<code>aptitude</code> can automatically install <em>Recommended:</em> -packages[<a href="footnotes.en.html#f5" name="fr5">5</a>]. -</p> -</li> -</ul> -<ul> -<li> -<p> -<code>aptitude</code> in full screen mode has <code>su</code> functionality -embedded and can be run by a normal user. It will call <code>su</code> (and -ask for the root password, if any) when you really need administrative -privileges -</p> -</li> -</ul> - -<p> -You can use <code>aptitude</code> through a visual interface (simply run -<samp>aptitude</samp>) or directly from the command line. The command line -syntax used is very similar to the one used in <code>apt-get</code>. For -example, to install the <var>foo</var> package, you can run <samp>aptitude -install <var>foo</var></samp>. -</p> - -<p> -Note that <code>aptitude</code> is the recommended program by Debian to install -a package and/or to upgrade your system. -</p> - -<p> -For more informations, read the manual page <code>aptitude(8)</code> and -install the <code>aptitude-doc-en</code> package. -</p> - -<hr> - -<h3><a name="s-dselect"></a>7.1.4 dselect</h3> - -<p> -This program is a menu-driven interface to the Debian package management -system. It is particularly useful for first-time installations. Some users -might feel more comfortable using <code>aptitude</code> which is also -recommended over <code>dselect</code> for large-scale upgrades. For more -information on <code>aptitude</code> please see <a href="#s-aptitude">aptitude, -Section 7.1.3</a>. -</p> - -<p> -<code>dselect</code> can: -</p> -<ul> -<li> -<p> -guide the user as he/she chooses among packages to install or remove, ensuring -that no packages are installed that conflict with one another, and that all -packages required to make each package work properly are installed; -</p> -</li> -</ul> -<ul> -<li> -<p> -warn the user about inconsistencies or incompatibilities in their selections; -</p> -</li> -</ul> -<ul> -<li> -<p> -determine the order in which the packages must be installed; -</p> -</li> -</ul> -<ul> -<li> -<p> -automatically perform the installation or removal; and -</p> -</li> -</ul> -<ul> -<li> -<p> -guide the user through whatever configuration process are required for each -package. -</p> -</li> -</ul> - -<p> -<code>dselect</code> begins by presenting the user with a menu of 7 items, each -of which is a specific action. The user can select one of the actions by using -the arrow keys to move the highlighter bar, then pressing the -<em><enter></em> key to select the highlighted action. -</p> - -<p> -What the user sees next depends on the action he selected. If he selects any -option but <samp>Access</samp> or <samp>Select</samp>, then -<code>dselect</code> will simply proceed to execute the specified action: e.g., -if the user selected the action <samp>Remove</samp>, then dselect would proceed -to remove all of the files selected for removal when the user last chose the -<samp>Select</samp> action. -</p> - -<p> -Both the <samp>Access</samp> menu item and the <samp>Select</samp> 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. -</p> - -<p> -Extensive on-line help is available, use the '?' key to get to a help screen -at any time. -</p> - -<p> -The order in which the actions are presented in the first <code>dselect</code> -menu represents the order in which a user would normally choose -<code>dselect</code> 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). -</p> -<ul> -<li> -<p> -Begin by choosing an <strong>Access Method</strong>. This is the method by -which the user plans on accessing Debian packages; e.g., some users have Debian -packages available on CD-ROM, while others plan to fetch them using anonymous -FTP. The selected "Access Method" is stored after -<code>dselect</code> exits, so if it does not change, then this option need not -be invoked again. -</p> -</li> -</ul> -<ul> -<li> -<p> -Then <strong>Update</strong> the list of available packages. To do this, -<code>dselect</code> reads the file "Packages.gz" which should be -included in the top level of the directory where the Debian packages to be -installed are stored. (But if it is not there, <code>dselect</code> will offer -to make it for you.) -</p> -</li> -</ul> -<ul> -<li> -<p> -<strong>Select</strong> specific packages for installation on his system. -After choosing this menu item, the user is first presented with a full screen -of help (unless the `--expert' command line option was used). Once the user -exits the Help screen, he sees the split-screen menu for choosing packages to -install (or remove). -</p> - -<p> -The top part of the screen is a relatively narrow window into the list of -Debian's 18347 packages; the bottom part of the screen contains description of -the package or group of packages which are highlighted above. -</p> - -<p> -One can specify which packages should be operated on by highlighting a package -name or the label for a group of packages. After that, you can select -packages: -</p> -<dl> -<dt>to be installed:</dt> -<dd> -<p> -This is accomplished by pressing the `+' key. -</p> -</dd> -</dl> -<dl> -<dt>to be deleted:</dt> -<dd> -<p> -Packages can be deleted two ways: -</p> -<ul> -<li> -<p> -removed: this removes most of the files associated with the package, but -preserves the files listed as configuration files (see <a -href="ch-pkg_basics.en.html#s-conffile">What is a Debian conffile?, Section -6.5</a>) and package configuration information. This is done by pressing the -`-' key. -</p> -</li> -</ul> -<ul> -<li> -<p> -purged: this removes <em>every</em> file that is part of the package. This is -done by pressing the `_' key. -</p> -</li> -</ul> - -<p> -Note that it's not possible to remove "All Packages". If you try -that, your system will instead be reduced to the initial installed base -packages. -</p> -</dd> -</dl> -<dl> -<dt>to be put "on hold"</dt> -<dd> -<p> -This is done by pressing `=', and it effectively tells <code>dselect</code> not -to upgrade a package even if the version currently installed on your system is -not as recent as the version that is available in the Debian repository you are -using (this was specified when you set the <strong>Access Method</strong>, and -acquired when you used <strong>Update</strong>). -</p> - -<p> -Just like you can put a package on hold, you can reverse such setting by -pressing `:'. That tells <code>dselect</code> that the package(s) may be -upgraded if a newer version is available. This is the default setting. -</p> -</dd> -</dl> - -<p> -You can select a different order in which the packages are presented, by using -the `o' key to cycle between various options for sorting the packages. The -default order is to present packages by Priority; within each priority, -packages are presented in order of the directory (a.k.a. section) of the -archive in which they are stored. Given this sort order, some packages in -section A (say) may be presented first, followed by some packages in section B, -followed by more packages (of lower priority) in section A. -</p> - -<p> -You can also expand meanings of the labels at the top of the screen, by using -the `v' (verbose) key. This action pushes much of the text that formerly fit -onto the display off to the right. To see it, press the right arrow; to scroll -back to the left, press the left arrow. -</p> - -<p> -If you select a package for installation or removal, e.g., -<code>foo.deb</code>, and that package depends on (or recommends) another -package, e.g., <code>blurf.deb</code>, then <code>dselect</code> will place the -you in a sub-screen of the main selection screen. There you can choose among -the related packages, accepting the suggested actions (to install or not), or -rejecting them. To do the latter, press Shift-D; to return to the former, -press Shift-U. In any case, you can save your selections and return to the -main selection screen by pressing Shift-Q. -</p> -</li> -</ul> -<ul> -<li> -<p> -Users returning to the main menu can then select the "Install" menu -item to unpack and configure the selected packages. Alternatively, users -wishing to remove files can choose the "Remove" menu item. At any -point, users can choose "Quit" to exit dselect; users' selections are -preserved by <code>dselect</code>. -</p> -</li> -</ul> - -<hr> - -<h3><a name="s-dpkg-extra"></a>7.1.5 Other package management tools</h3> - -<hr> - -<h4><a name="s-dpkg-deb"></a>7.1.5.1 dpkg-deb</h4> - -<p> -This program manipulates Debian archive(<samp>.deb</samp>) files. Some common -uses are: -</p> -<ul> -<li> -<p> -Find out all the options: <samp>dpkg-deb --help</samp>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Determine what files are contained in a Debian archive file: <samp>dpkg-deb ---contents foo_VVV-RRR.deb</samp>) -</p> -</li> -</ul> -<ul> -<li> -<p> -Extract the files contained in a named Debian archive into a user specified -directory: <samp>dpkg-deb --extract foo_VVV-RRR.deb tmp</samp> extracts each of -the files in <samp>foo_VVV-RRR.deb</samp> into the directory <samp>tmp/</samp>. -This is convenient for examining the contents of a package in a localized -directory, without installing the package into the root file system. -</p> -</li> -</ul> - -<p> -Note that any packages that were merely unpacked using <samp>dpkg-deb ---extract</samp> will be incorrectly installed, you should use <samp>dpkg ---install</samp> instead. -</p> - -<p> -More information is given in the manual page <code>dpkg-deb(1)</code>. -</p> - -<hr> - -<h4><a name="s-dpkg-split"></a>7.1.5.2 dpkg-split</h4> - -<p> -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 <code>dpkg</code> package), since it calls the program -<samp>dpkg-deb</samp> to parse the debian package file into its component -records. -</p> - -<p> -For example, to split a big .deb file into N parts, -</p> -<ul> -<li> -<p> -Execute the command <samp>dpkg-split --split foo.deb</samp>. This will produce -N files each of approximately 460 KBytes long in the current directory. -</p> -</li> -</ul> -<ul> -<li> -<p> -Copy those N files to floppy disks. -</p> -</li> -</ul> -<ul> -<li> -<p> -Copy the contents of the floppy disks onto the hard disk of your choice on the -other machine. -</p> -</li> -</ul> -<ul> -<li> -<p> -Join those part-files together using <samp>dpkg-split --join -"foo*"</samp>. -</p> -</li> -</ul> - -<hr> - -<h2><a name="s-updaterunning"></a>7.2 Debian claims to be able to update a running program; how is this accomplished?</h2> - -<p> -The kernel (file system) in Debian GNU/Linux systems supports replacing files -even while they're being used. -</p> - -<p> -We also provide a program called <code>start-stop-daemon</code> which is used -to start daemons at boot time or to stop daemons when the kernel runlevel is -changed (e.g., from multi-user to single-user or to halt). The same program is -used by installation scripts when a new package containing a daemon is -installed, to stop running daemons, and restart them as necessary. -</p> - -<hr> - -<h2><a name="s-whatpackages"></a>7.3 How can I tell what packages are already installed on a Debian system?</h2> - -<p> -To learn the status of all the packages installed on a Debian system, execute -the command -</p> - -<pre> - dpkg --list -</pre> - -<p> -This prints out a one-line summary for each package, giving a 2-letter status -symbol (explained in the header), the package name, the version which is -<em>installed</em>, and a brief description. -</p> - -<p> -To learn the status of packages whose names match the string any pattern -beginning with "foo" by executing the command: -</p> - -<pre> - dpkg --list 'foo*' -</pre> - -<p> -To get a more verbose report for a particular package, execute the command: -</p> - -<pre> - dpkg --status packagename -</pre> - -<hr> - -<h2><a name="s-filesearch"></a>7.4 How can I find out what package produced a particular file?</h2> - -<p> -To identify the package that produced the file named <samp>foo</samp> execute -either: -</p> -<ul> -<li> -<p> -<samp>dpkg --search filename</samp> -</p> - -<p> -This searches for <samp>filename</samp> in installed packages. (This is -(currently) equivalent to searching all of the files having the file extension -of <samp>.list</samp> in the directory <samp>/var/lib/dpkg/info/</samp>, and -adjusting the output to print the names of all the packages containing it, and -diversions.) -</p> - -<p> -A faster alternative to this is the <code>dlocate</code> tool. -</p> -</li> -</ul> -<ul> -<li> -<p> -<samp>zgrep foo Contents-ARCH.gz</samp> -</p> - -<p> -This searches for files which contain the substring <samp>foo</samp> in their -full path names. The files <samp>Contents-ARCH.gz</samp> (where ARCH -represents the wanted architecture) reside in the major package directories -(main, non-free, contrib) at a Debian FTP site (i.e. under -<samp>/debian/dists/etch</samp>). A <samp>Contents</samp> file refers only to -the packages in the subdirectory tree where it resides. Therefore, a user -might have to search more than one <samp>Contents</samp> files to find the -package containing the file <samp>foo</samp>. -</p> - -<p> -This method has the advantage over <samp>dpkg --search</samp> in that it will -find files in packages that are not currently installed on your system. -</p> -</li> -</ul> -<ul> -<li> -<p> -<samp>apt-file search <var>foo</var></samp> -</p> - -<p> -Similar to the above, it searches files which contain the substring or regular -expression <samp>foo</samp> in their full path names. The advantage over the -sample above is that there is no need to retrieve the -<samp>Contents-ARCH.gz</samp> files as it will do this automatically for all -the sources defined in <code>/etc/apt/sources.list</code> when you run (as -root) <samp>apt-file update</samp>. -</p> -</li> -</ul> - -<hr> - -<h2><a name="s-datapackages"></a>7.5 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?</h2> - -<p> -Some packages that are split in program (`foo') and data (`foo-data'). This is -true for many games, multimedia applications and dictionaries in Debian and has -been introduced since some users might want to access the raw data without -installing the program or because the program can be run without the data -itself, making it optional. -</p> - -<p> -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. -</p> - -<p> -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 <code>aptitude</code> (see <a -href="#s-aptitude">aptitude, Section 7.1.3</a>) 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. -</p> - -<hr> - -<p> -[ <a href="ch-pkg_basics.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ 7 ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-uptodate.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-redistrib.en.html b/includes/sid/common/doc/FAQ/html/ch-redistrib.en.html deleted file mode 100644 index 8242553..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-redistrib.en.html +++ /dev/null @@ -1,170 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Redistributing Debian GNU/Linux in a commercial product</title> - -</head> - -<body> - -<p><a name="ch-redistrib"></a></p> -<hr> - -<p> -[ <a href="ch-contributing.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ 13 ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-nexttime.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 13 - Redistributing Debian GNU/Linux in a commercial product -</h1> - -<hr> - -<h2><a name="s-sellcds"></a>13.1 Can I make and sell Debian CDs?</h2> - -<p> -Go ahead. You do not need permission to distribute anything we have -<em>released</em>, so that you can master your CD as soon as the beta-test -ends. You do not have to pay us anything. Of course, all CD manufacturers -must honor the licenses of the programs in Debian. For example, many of the -programs are licensed under the GPL, which requires you to distribute their -source code. -</p> - -<p> -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. -</p> - -<hr> - -<h2><a name="s-packagednonfree"></a>13.2 Can Debian be packaged with non-free software?</h2> - -<p> -Yes. While all the main components of Debian are free software, we provide a -non-free directory for programs that are not freely redistributable. -</p> - -<p> -CD manufacturers <em>may</em> be able to distribute the programs we have placed -in that directory, depending on the license terms or their private arrangements -with the authors of those software packages. CD manufacturers can also -distribute the non-free software they get from other sources on the same CD. -This is nothing new: free and commercial software are distributed on the same -CD by many manufacturers now. Of course we still encourage software authors to -release the programs they write as free software. -</p> - -<hr> - -<h2><a name="s-childistro"></a>13.3 I am making a special Linux distribution for a "vertical market". Can I use Debian GNU/Linux for the guts of a Linux system and add my own applications on top of it?</h2> - -<p> -Yes. Debian-derived distributions are being created both in close cooperation -with the Debian project itself and by external parties. One can use the -<code><a href="http://cdd.alioth.debian.org/">Custom Debian -Distributions</a></code> framework to work together with Debian; <code><a -href="http://www.skolelinux.org/">Skolelinux</a></code> is one such project. -</p> - -<p> -One person is building a "Linux for Hams" distribution, with -specialized programs for Radio Amateurs. He is starting with Debian as the -"base system", and adding programs to control the transmitter, track -satellites, etc. All of the programs he adds are packaged with the Debian -packaging system so that his users will be able to upgrade easily when he -releases subsequent CDs. -</p> - -<p> -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. -</p> - -<p> -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 <a href="ch-customizing.en.html#s-divert">How do I override a file -installed by a package, so that a different version can be used instead?, -Section 10.8</a>. -</p> - -<hr> - -<h2><a name="s-commercialdebs"></a>13.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?</h2> - -<p> -Go right ahead. The package tool is free software; the packages may or may not -be free software, it can install them all. -</p> - -<hr> - -<p> -[ <a href="ch-contributing.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ 13 ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-nexttime.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-software.en.html b/includes/sid/common/doc/FAQ/html/ch-software.en.html deleted file mode 100644 index afb823b..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-software.en.html +++ /dev/null @@ -1,401 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Software available in the Debian system</title> - -</head> - -<body> - -<p><a name="ch-software"></a></p> -<hr> - -<p> -[ <a href="ch-compat.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ 4 ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-ftparchives.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 4 - Software available in the Debian system -</h1> - -<hr> - -<h2><a name="s-apps"></a>4.1 What types of applications and development software are available for Debian GNU/Linux?</h2> - -<p> -Like most Linux distributions, Debian GNU/Linux provides: -</p> -<ul> -<li> -<p> -the major GNU applications for software development, file manipulation, and -text processing, including gcc, g++, make, texinfo, Emacs, the Bash shell and -numerous upgraded Unix utilities, -</p> -</li> -</ul> -<ul> -<li> -<p> -Perl, Python, Tcl/Tk and various related programs, modules and libraries for -each of them, -</p> -</li> -</ul> -<ul> -<li> -<p> -TeX (LaTeX) and Lyx, dvips, Ghostscript, -</p> -</li> -</ul> -<ul> -<li> -<p> -the X Window System, which provides a networked graphical user interface for -Linux, and countless X applications including GNOME and KDE as well as the GIMP -GNU Image Manipulation Program, -</p> -</li> -</ul> -<ul> -<li> -<p> -a full suite of networking applications, including servers for Internet -protocols such as HTTP (WWW), FTP, NNTP (news), SMTP and POP (mail) and name -server; relational databases like PostgreSQL, MySQL; also provided are web -browsers including the various Mozilla producs, -</p> -</li> -</ul> -<ul> -<li> -<p> -a complete set of office applications, including the OpenOffice.org -productivity suite, Gnumeric and other spreadsheets, WYSIWYG editors, -calendars. -</p> -</li> -</ul> - -<p> -More than 18138 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 444 software -suites are available as Debian packages, but are not formally part of Debian -due to license restrictions. -</p> - -<hr> - -<h2><a name="s-softwareauthors"></a>4.2 Who wrote all that software?</h2> - -<p> -For each package the <em>authors</em> of the program(s) are credited in the -file <samp>/usr/share/doc/PACKAGE/copyright</samp>, where PACKAGE is to be -substituted with the package's name. -</p> - -<p> -<em>Maintainers</em> who package this software for the Debian GNU/Linux system -are listed in the Debian control file (see <a -href="ch-pkg_basics.en.html#s-controlfile">What is a Debian control file?, -Section 6.4</a>) that comes with each package. The Debian changelog, in -<samp>/usr/share/doc/PACKAGE/changelog.Debian.gz</samp>, mentions the people -who've worked on the Debian packaging too. -</p> - -<hr> - -<h2><a name="s-pkglist"></a>4.3 How can I get a current list of programs that have been packaged for Debian?</h2> - -<p> -A complete list is available from any of the <code><a -href="http://www.debian.org/distrib/ftplist">Debian mirrors</a></code>, in the -file <samp>indices/Maintainers</samp>. That file includes the package names -and the names and e-mails of their respective maintainers. -</p> - -<p> -The <code><a href="http://packages.debian.org/">WWW interface to the Debian -packages</a></code> conveniently summarizes the packages in each of about -twenty "sections" of the Debian archive. -</p> - -<hr> - -<h2><a name="s-missing"></a>4.4 What is missing from Debian GNU/Linux?</h2> - -<p> -A list of packages which are still needed to be packaged for Debian exists, the -<code><a href="http://www.debian.org/devel/wnpp/">Work-Needing and Prospective -Packages list</a></code>. -</p> - -<p> -For more details about adding the missing things, see <a -href="ch-contributing.en.html#s-contrib">How can I become a Debian software -developer?, Section 12.1</a>. -</p> - -<hr> - -<h2><a name="s-no-devs"></a>4.5 Why do I get "ld: cannot find -lfoo" messages when compiling programs? Why aren't there any libfoo.so files in Debian library packages?</h2> - -<p> -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). -</p> - -<hr> - -<h2><a name="s-java"></a>4.6 (How) Does Debian support Java?</h2> - -<p> -Several <em>free</em> implementations of Java technology are available as -Debian packages, providing both Java Development Kits as well as Runtime -Environments. You can write, debug and run Java programs using Debian. -</p> - -<p> -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. -</p> - -<p> -Please refer to the <code><a -href="http://www.debian.org/doc/manuals/debian-java-faq/">Debian Java -FAQ</a></code> for more information. -</p> - -<hr> - -<h2><a name="s-isitdebian"></a>4.7 How can I check that I am using a Debian system, and what version is it?</h2> - -<p> -In order to make sure that your system has been installed from the real Debian -base disks check for the existence of <samp>/etc/debian_version</samp> file, -which contains a single one-line entry giving the version number of the -release, as defined by the package <samp>base-files</samp>. -</p> - -<p> -The existence of the program <samp>dpkg</samp> 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. -</p> - -<p> -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 <samp>foo</samp>, use the command <samp>dpkg --list foo</samp>. To -view versions of all installed packages, run: -</p> - -<pre> - dpkg -l -</pre> - -<p> -For a more verbose description, use: -</p> - -<pre> - dpkg --status foo -</pre> - -<hr> - -<h2><a name="s-nonenglish"></a>4.8 How does Debian support non-English languages?</h2> -<ul> -<li> -<p> -Debian GNU/Linux is distributed with keymaps for nearly two dozen keyboards, -and with utilities (in the <samp>kbd</samp> package) to install, view, and -modify the tables. -</p> - -<p> -The installation prompts the user to specify the keyboard he will use. -</p> -</li> -</ul> -<ul> -<li> -<p> -Vast majority of the software we packaged supports entering non-US-ASCII -characters used in other Latin languages (e.g. ISO-8859-1 or ISO-8859-2), and -a number of programs support multi-byte languages such as Japanese or Chinese. -</p> -</li> -</ul> -<ul> -<li> -<p> -Currently, support for German-, Spanish-, Finnish-, French-, Hungarian-, -Italian-, Japanese-, Korean- and Polish-language manual pages is provided -through the <samp>manpages-LANG</samp> packages (where LANG is the two-letter -ISO country code). To access an NLS manual page, the user must set the shell -LC_MESSAGES variable to the appropriate string. -</p> - -<p> -For example, in the case of the Italian-language manual pages, LC_MESSAGES -needs to be set to 'italian'. The <code>man</code> program will then search -for Italian manual pages under <samp>/usr/share/man/it/</samp>. -</p> -</li> -</ul> - -<hr> - -<h2><a name="s-usexports"></a>4.9 What about the US export regulation limitations?</h2> - -<p> -US laws placed restrictions on the export of defense articles, which includes -some types of cryptographic software. PGP and ssh, among others, fall into -this category. For the <em>sarge</em> release packages in this archive were -moved to the main archive (or to <em>non-free</em>, if applicable) due to the -US relaxing its regulations on the export of cryptography. -</p> - -<p> -To prevent anyone from taking unnecessary legal risks, certain Debian GNU/Linux -packages were only available from a non-US site <code><a -href="ftp://non-US.debian.org/debian-non-US/">ftp://non-US.debian.org/debian-non-US/</a></code>, -with numerous mirror sites all of which are also outside of the US, see -<code><a -href="ftp://non-US.debian.org/debian-non-US/README.non-US">ftp://non-US.debian.org/debian-non-US/README.non-US</a></code> -for a full list. These sites still exist (for the benefit of users of -<em>woody</em>) but its contents are no longer supported and are considered -obsolete. Please remove any mentions to non-US from your sources in your -<code>/etc/apt/sources.list</code> configuration file. -</p> - -<hr> - -<h2><a name="s-pine"></a>4.10 Where is pine?</h2> - -<p> -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. -</p> - -<p> -The source package name is <code>pine</code>. You can use the -<code>pine-tracker</code> package to be notified about when you need to -upgrade. -</p> - -<p> -Note that there are many replacements for both pine and pico, such as -<code>mutt</code> and <code>nano</code>, that are located in the main section. -</p> - -<hr> - -<h2><a name="s-qmail"></a>4.11 Where is qmail/ezmlm/djbdns?</h2> - -<p> -Dan J. Bernstein distributes <code><a href="http://cr.yp.to/software.html">all -software he has written</a></code> with a restrictive license, consequently, -it's in the non-free area. Since the license he uses does not allow modified -binaries to be distributed, you have to compile it yourself from the source and -the Debian patches to obtain a binary package you can install in your Debian -GNU/Linux system. -</p> - -<p> -The source package names are <code>qmail-src</code>, <code>ezmlm-src</code> and -<code>djbdns-installer</code>, respectively. -</p> - -<p> -For <code>qmail</code> you need to install <code>qmail-src</code> first and -then run <code>build-qmail</code> to build the Debian package. You also need -to do install the <code>ucspi-tcp-src</code> package to get ucspi-tcp, which -<code>qmail</code> depends on. -</p> - -<p> -Dan J. Bernstein maintains a <code><a -href="http://cr.yp.to/distributors.html">FAQ from distributors</a></code> page -if you are interested in reading his reasons (one of which is <code><a -href="http://cr.yp.to/compatibility.html">Cross-platform -compatibility</a></code>) -</p> - -<hr> - -<p> -[ <a href="ch-compat.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ 4 ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-ftparchives.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-support.en.html b/includes/sid/common/doc/FAQ/html/ch-support.en.html deleted file mode 100644 index f910fe7..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-support.en.html +++ /dev/null @@ -1,525 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Getting support for Debian GNU/Linux</title> - -</head> - -<body> - -<p><a name="ch-support"></a></p> -<hr> - -<p> -[ <a href="ch-customizing.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ 11 ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-contributing.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 11 - Getting support for Debian GNU/Linux -</h1> - -<hr> - -<h2><a name="s-debiandocs"></a>11.1 What other documentation exists on and for a Debian system?</h2> -<ul> -<li> -<p> -Installation instructions for the current release: see <code><a -href="http://www.debian.org/releases/stable/installmanual">http://www.debian.org/releases/stable/installmanual</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -The Debian GNU/Linux reference covers many aspects of system administration -through shell-command examples. Basic tutorials, tips, and other information -are provided for many different topics ranging from system administration to -programming. -</p> - -<p> -Get it from the <code>debian-reference</code> package, or at <code><a -href="http://www.debian.org/doc/user-manuals#quick-reference">http://www.debian.org/doc/user-manuals#quick-reference</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Policy manual documents the policy requirements for the distribution, i.e. the -structure and contents of the Debian archive, several design issues of the -operating system etc. It also includes the technical requirements that each -package must satisfy to be included in the distribution, and documents the -basic technical aspects of Debian binary and source packages. -</p> - -<p> -Get it from the <code>debian-policy</code> package, or at <code><a -href="http://www.debian.org/doc/devel-manuals#policy">http://www.debian.org/doc/devel-manuals#policy</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Documentation developed by the Debian Documentation Project. It is available -at <code><a -href="http://www.debian.org/doc/">http://www.debian.org/doc/</a></code> and -includes user guides, administration guides and security guides for the Debian -GNU/Linux operating system. -</p> -</li> -</ul> -<ul> -<li> -<p> -Documentation on installed Debian packages: Most packages have files that are -unpacked into <samp>/usr/share/doc/PACKAGE</samp>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Documentation on the Linux project: The Debian package <code>doc-linux</code> -installs all of the most recent versions of the HOWTOs and mini-HOWTOs from the -<code><a href="http://www.tldp.org/">Linux Documentation Project</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Unix-style `man' pages: Most commands have manual pages written in the style of -the original Unix 'man' files. They are referenced by the section of the 'man' -directory where they reside: e.g., foo(3) refers to a manual page which resides -in /usr/share/man/man3/, and it can be called by executing the command: -<samp>man 3 foo</samp>, or just <samp>man foo</samp> if section 3 is the first -one containing a page on <samp>foo</samp>. -</p> - -<p> -One can learn which directory of <samp>/usr/share/man/</samp> contains a -certain manual page by executing <samp>man -w foo</samp>. -</p> - -<p> -New Debian users should note that the 'man' pages of many general system -commands are not available until they install these packages: -</p> -<ul> -<li> -<p> -<samp>man-db</samp>, which contains the <samp>man</samp> program itself, and -other programs for manipulating the manual pages. -</p> -</li> -</ul> -<ul> -<li> -<p> -<samp>manpages</samp>, which contains the system manual pages. (see <a -href="ch-software.en.html#s-nonenglish">How does Debian support non-English -languages?, Section 4.8</a>). -</p> -</li> -</ul> -</li> -</ul> -<ul> -<li> -<p> -GNU-style `info' pages: User documentation for many commands, particularly GNU -tools, is available not in `man' pages, but in `info' files which can be read -by the GNU tool <samp>info</samp>, by running <samp>M-x info</samp> within GNU -Emacs, or with some other Info page viewer. -</p> - -<p> -Its main advantage over the original `man' pages are that it is a hypertext -system. It does <em>not</em> require the WWW, however; <samp>info</samp> can -be run from a plain text console. It was designed by Richard Stallman and -preceded the WWW. -</p> -</li> -</ul> - -<p> -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. -</p> - -<hr> - -<h2><a name="s-onlineresources"></a>11.2 Are there any on-line resources for discussing Debian?</h2> - -<p> -Yes. In fact, the main method of support Debian provides to our users is by -the way of e-mail. -</p> - -<hr> - -<h3><a name="s11.2.1"></a>11.2.1 Mailing lists</h3> - -<p> -There are a lot of <code><a -href="http://www.debian.org/MailingLists/">Debian-related mailing -lists</a></code>. -</p> - -<p> -On a system with the <code>doc-debian</code> package installed there is a -complete list of mailing lists in -<code>/usr/share/doc/debian/mailing-lists.txt</code>. -</p> - -<p> -Debian mailing lists are named following the pattern -debian-<var>list-subject</var>. Examples are debian-announce, debian-user, -debian-news. To subscribe to any list debian-<var>list-subject</var>, send -mail to debian-<var>list-subject</var>-request@lists.debian.org with the word -"subscribe" in the Subject: header. Be sure to remember to add -<em>-request</em> to the e-mail address when using this method to subscribe or -unsubscribe. Otherwise your e-mail will go to the list itself, which could be -embarrassing or annoying, depending on your point of view. -</p> - -<p> -If you have a forms-capable World Wide Web browser, you can subscribe to -mailing lists using the <code><a -href="http://www.debian.org/MailingLists/subscribe">WWW form</a></code>. You -can also un-subscribe using a <code><a -href="http://www.debian.org/MailingLists/unsubscribe">WWW form</a></code>. -</p> - -<p> -The list manager's e-mail address is <code><a -href="mailto:listmaster@lists.debian.org">listmaster@lists.debian.org</a></code>, -in case you have any trouble. -</p> - -<p> -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 <code><a -href="http://www.debian.org/MailingLists/index.en.html#disclaimer">Mailing -Lists Privacy policy</a></code> for more information. -</p> - -<p> -Archives of the Debian mailing lists are available via WWW at <code><a -href="http://lists.debian.org/">http://lists.debian.org/</a></code>. -</p> - -<hr> - -<h4><a name="s-mailinglistconduct"></a>11.2.1.1 What is the code of conduct for the mailing lists?</h4> - -<p> -When using the Debian mailing lists, please follow these rules: -</p> -<ul> -<li> -<p> -Do not send spam. See the <code><a -href="http://www.debian.org/MailingLists/#ads">Debian mailing list advertising -policy</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Do not flame; it is not polite. The people developing Debian are all -volunteers, donating their time, energy and money in an attempt to bring the -Debian project together. -</p> -</li> -</ul> -<ul> -<li> -<p> -Do not use foul language; besides, some people receive the lists via packet -radio, where swearing is illegal. -</p> -</li> -</ul> -<ul> -<li> -<p> -Make sure that you are using the proper list. <em>Never</em> post your -(un)subscription requests to the mailing list itself[<a -href="footnotes.en.html#f6" name="fr6">6</a>] -</p> -</li> -</ul> -<ul> -<li> -<p> -See section <a href="#s-bugreport">How do I report a bug in Debian?, Section -11.5</a> for notes on reporting bugs. -</p> -</li> -</ul> - -<hr> - -<h3><a name="s11.2.2"></a>11.2.2 Maintainers</h3> - -<p> -Users can address questions to individual package maintainers using e-mail. To -reach a maintainer of a package called xyz, send e-mail to -<em>xyz@packages.debian.org</em>. -</p> - -<hr> - -<h3><a name="s11.2.3"></a>11.2.3 Usenet newsgroups</h3> - -<p> -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 -<code><a href="http://www.linux.org/docs/usenet.html">Linux Online</a></code> -and <code><a -href="http://www.linuxjournal.com/helpdesk.php">LinuxJournal</a></code> sites. -</p> - -<hr> - -<h2><a name="s-searchtools"></a>11.3 Is there a quick way to search for information on Debian GNU/Linux?</h2> - -<p> -There is a variety of search engines that serve documentation related to -Debian: -</p> -<ul> -<li> -<p> -<code><a href="http://search.debian.org/">Debian WWW search site</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -<code><a href="http://groups.google.com/">Google Groups</a></code>: a search -engine for newsgroups. -</p> - -<p> -For example, to find out what experiences people have had with finding drivers -for Promise controllers under Debian, try searching on the phrase <samp>Promise -Linux driver</samp>. This will show you all the postings that contain these -strings, i.e. those where people discussed these topics. If you add -<samp>Debian</samp> to those search strings, you'll also get the postings -specifically related to Debian. -</p> -</li> -</ul> -<ul> -<li> -<p> -Any of the common web spidering engines, such as <code><a -href="http://www.altavista.com/">AltaVista</a></code> or <code><a -href="http://www.google.com/">Google</a></code>, as long as you use the right -search terms. -</p> - -<p> -For example, searching on the string "cgi-perl" gives a more detailed -explanation of this package than the brief description field in its control -file. -</p> -</li> -</ul> - -<hr> - -<h2><a name="s-buglogs"></a>11.4 Are there logs of known bugs?</h2> - -<p> -Reports on unsolved (and closed) issues are publicly available: Debian -promissed to do so by stating "We will not hide problems" in the -<code><a href="http://www.debian.org/social_contract">Debian Social -Contract</a></code>. -</p> - -<p> -The Debian GNU/Linux distribution has a bug tracking system (BTS) which files -details of bugs reported by users and developers. Each bug is given a number, -and is kept on file until it is marked as having been dealt with. -</p> - -<p> -Copies of this information are available at <code><a -href="http://www.debian.org/Bugs/">http://www.debian.org/Bugs/</a></code>. -</p> - -<p> -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. -</p> - -<hr> - -<h2><a name="s-bugreport"></a>11.5 How do I report a bug in Debian?</h2> - -<p> -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: -</p> -<ul> -<li> -<p> -By anonymous FTP. Debian mirror sites contain the instructions in the file -<samp>doc/bug-reporting.txt</samp>. -</p> -</li> -</ul> -<ul> -<li> -<p> -From the WWW. A copy of the instructions is shown at <code><a -href="http://www.debian.org/Bugs/Reporting">http://www.debian.org/Bugs/Reporting</a></code>. -</p> -</li> -</ul> -<ul> -<li> -<p> -On any Debian system with the <code>doc-debian</code> package installed. The -instructions are in the file -<code>/usr/share/doc/debian/bug-reporting.txt</code>. -</p> -</li> -</ul> - -<p> -You can use the package <code>reportbug</code> that will guide you through the -reporting process and mail the message to the proper address, with some extra -details about your system added automatically. It will also show you a list of -bugs already reported to the package you are reporting against in case your bug -has been reported previously, so that you can additional information to the -existing bug report. -</p> - -<p> -If you want to mail the report with an e-mail program, send a message to -<code><a -href="mailto:submit@bugs.debian.org">submit@bugs.debian.org</a></code>. The -message's first line must be similar to -</p> - -<pre> - Package: package-name -</pre> - -<p> -(replace <var>package-name</var> with the name of the package). The next line -should relate the package version number in a similar way: -</p> - -<pre> - Version: version-number -</pre> - -<p> -The version number for any package installed on your system can be obtained -using the command line -</p> - -<pre> - dpkg -s <var>package-name</var> -</pre> - -<p> -This section is referred to as the pseudo-header. The rest of the message -should contain the description of the bug (please make it moderately detailed), -the Debian release you are using, and versions of other relevant packages. The -Debian release number will be displayed by the command -</p> - -<pre> - cat /etc/debian_version -</pre> - -<p> -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. -</p> - -<hr> - -<p> -[ <a href="ch-customizing.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ 11 ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-contributing.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/ch-uptodate.en.html b/includes/sid/common/doc/FAQ/html/ch-uptodate.en.html deleted file mode 100644 index 180431b..0000000 --- a/includes/sid/common/doc/FAQ/html/ch-uptodate.en.html +++ /dev/null @@ -1,479 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Keeping your Debian system up-to-date</title> - -</head> - -<body> - -<p><a name="ch-uptodate"></a></p> -<hr> - -<p> -[ <a href="ch-pkgtools.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ 8 ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-kernel.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Chapter 8 - Keeping your Debian system up-to-date -</h1> - -<hr> - -<p> -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. -</p> - -<p> -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 -<code><a -href="http://www.debian.org/releases/stable/releasenotes">http://www.debian.org/releases/stable/releasenotes</a></code>. -</p> - -<hr> - -<h2><a name="s-libc5to6upgrade"></a>8.1 How can I upgrade my Debian 1.3.1 (or earlier) distribution, based on libc5, to 2.0 (or later), based on libc6?</h2> - -<p> -There are several ways to upgrade: -</p> -<ul> -<li> -<p> -Using a simple shell script called <samp>autoup.sh</samp> which upgrades the -most important packages. After <samp>autoup.sh</samp> has done his job, you -may use dselect to install the remaining packages <em>en masse</em>. This is -probably the recommended method, but not the only one. -</p> - -<p> -Currently, the latest release of <samp>autoup.sh</samp> may be found on the -following locations: -</p> -<ul> -<li> -<p> -<code><a -href="http://www.debian.org/releases/2.0/autoup/">http://www.debian.org/releases/2.0/autoup/</a></code> -</p> -</li> -</ul> -<ul> -<li> -<p> -<code><a -href="http://www.taz.net.au/autoup/">http://www.taz.net.au/autoup/</a></code> -</p> -</li> -</ul> -<ul> -<li> -<p> -<code><a -href="http://debian.vicnet.net.au/autoup/">http://debian.vicnet.net.au/autoup/</a></code> -</p> -</li> -</ul> -</li> -</ul> -<ul> -<li> -<p> -Following closely the <code><a -href="http://debian.vicnet.net.au/autoup/HOWTO/libc5-libc6-Mini-HOWTO.html">Debian -libc5 to libc6 Mini-HOWTO</a></code> and upgrade the most important packages by -hand. <samp>autoup.sh</samp> is based on this Mini-HOWTO, so this method -should work more or less like using <samp>autoup.sh</samp>. -</p> -</li> -</ul> -<ul> -<li> -<p> -Using a libc5-based <samp>apt</samp>. APT stands for Advanced Package Tool, -and it might replace dselect some day. Currently, it works just as a -command-line interface, or as a dselect access method. You will find a libc5 -version in the <samp>dists/slink/main/upgrade-older-i386</samp> directory at -the Debian archives. -</p> -</li> -</ul> -<ul> -<li> -<p> -Using just dselect, without upgrading any package by hand first. It is highly -recommended that you do NOT use this method if you can avoid it, because -dselect alone currently does not install packages in the optimal order. APT -works much better and it is safer. -</p> -</li> -</ul> - -<hr> - -<h2><a name="s-howtocurrent"></a>8.2 How can I keep my Debian system current?</h2> - -<p> -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 <samp>dpkg</samp>. Note that <samp>dpkg</samp> 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. -</p> - -<p> -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: -</p> - -<hr> - -<h3><a name="s-aptitude-upgrade"></a>8.2.1 aptitude</h3> - -<p> -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 -<samp>/usr/share/doc/apt-doc/guide.html/index.html</samp> (you will have to -install the <samp>apt-doc</samp> package). -</p> - -<p> -<code>aptitude</code> 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. -</p> - -<p> -Before you can use <code>aptitude</code>, you'll have to edit the -<samp>/etc/apt/sources.list</samp> 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: -</p> - -<pre> - http://http.us.debian.org/debian stable main contrib non-free -</pre> - -<p> -You can replace http.us.debian.org with the name of a faster Debian mirror near -you. See the mirror list at <code><a -href="http://www.debian.org/misc/README.mirrors">http://www.debian.org/misc/README.mirrors</a></code> -for more information. -</p> - -<p> -More details on this can be found in the <code>sources.list(8)</code> manual -page. -</p> - -<p> -To update your system, run -</p> - -<pre> - aptitude update -</pre> - -<p> -followed by -</p> - -<pre> - aptitude dist-upgrade -</pre> - -<p> -Answer any questions that might come up, and your system will be upgraded. See -also <a href="ch-pkgtools.en.html#s-aptitude">aptitude, Section 7.1.3</a>. -</p> - -<hr> - -<h3><a name="s-apt"></a>8.2.2 apt-get, dselect and apt-cdrom</h3> - -<p> -<code>apt-get</code> is an APT-based command-line tool for handling packages, -and the APT dselect method is an interface to APT through <code>dselect</code>. -Both of these provide a simple, safe way to install and upgrade packages. -</p> - -<p> -To use <code>apt-get</code>, install the <code>apt</code> package, and edit the -<samp>/etc/apt/sources.list</samp> file to set it up, just as for <a -href="#s-aptitude-upgrade">aptitude, Section 8.2.1</a>. -</p> - -<p> -Then run -</p> - -<pre> - apt-get update -</pre> - -<p> -followed by -</p> - -<pre> - apt-get dist-upgrade -</pre> - -<p> -Answer any questions that might come up, and your system will be upgraded. See -also the <code>apt-get(8)</code> manual page, as well as <a -href="ch-pkgtools.en.html#s-apt-get">APT, Section 7.1.2</a>. -</p> - -<p> -To use APT with <code>dselect</code>, 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 <code>/etc/apt/sources.list</code>. See also -<a href="ch-pkgtools.en.html#s-dselect">dselect, Section 7.1.4</a>. -</p> - -<p> -If you want to use CDs to install packages, you can use <code>apt-cdrom</code>. -For details, please see the Release Notes, section "Setting up for an -upgrade from a local mirror". -</p> - -<p> -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 <samp>apt-get clean</samp> -and <samp>apt-get autoclean</samp>, or to move them someplace else (hint: use -<code>apt-move</code>). -</p> - -<hr> - -<h3><a name="s-dpkg-ftp"></a>8.2.3 dpkg-ftp</h3> - -<p> -This is an older access method for <code>dselect</code>. It can be invoked -from within <code>dselect</code>, thereby allowing a user the ability to -download files and install them directly in one step. To do this, select the -<samp>ftp</samp> access method in <code>dselect</code> (option 0) and specify -the remote host name and directory. <code>dpkg-ftp</code> will then -automatically download the files that are selected (either in this session of -<code>dselect</code> or earlier ones). -</p> - -<p> -Note that, unlike the <code>mirror</code> program, <code>dpkg-ftp</code> does -not grab everything at a mirror site. Rather, it downloads only those files -which you have selected (when first starting up <code>dpkg-ftp</code>), and -which need to be updated. -</p> - -<p> -<code>dpkg-ftp</code> is somewhat obsolete. You should use the APT access -method with ftp:// URLs in <code>sources.list</code> instead. -</p> - -<hr> - -<h3><a name="s-mirror"></a>8.2.4 mirror</h3> - -<p> -This Perl script, and its (optional) manager program called -<code>mirror-master</code>, can be used to fetch user-specified parts of a -directory tree from a specified host <em>via</em> anonymous FTP. -</p> - -<p> -<code>mirror</code> is particularly useful for downloading large volumes of -software. After the first time files have been downloaded from a site, a file -called <samp>.mirrorinfo</samp> is stored on the local host. Changes to the -remote file system are tracked automatically by <code>mirror</code>, which -compares this file to a similar file on the remote system and downloads only -changed files. -</p> - -<p> -The <code>mirror</code> program is generally useful for updating local copies -of remote directory trees. The files fetched need not be Debian files. (Since -<code>mirror</code> is a Perl script, it can also run on non-Unix systems.) -Though the <code>mirror</code> 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. -</p> - -<hr> - -<h3><a name="s-dpkg-mountable"></a>8.2.5 dpkg-mountable</h3> - -<p> -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. -</p> - -<p> -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. -</p> - -<hr> - -<h2><a name="s-upgradesingle"></a>8.3 Must I go into single user mode in order to upgrade a package?</h2> - -<p> -No. Packages can be upgraded in place, even in running systems. Debian has a -<samp>start-stop-daemon</samp> program that is invoked to stop, then restart -running process if necessary during a package upgrade. -</p> - -<hr> - -<h2><a name="s-savedebs"></a>8.4 Do I have to keep all those .deb archive files on my disk?</h2> - -<p> -No. If you have downloaded the files to your disk (which is not absolutely -necessary, see above for the description of dpkg-ftp), then after you have -installed the packages, you can remove them from your system. -</p> - -<hr> - -<h2><a name="s-keepingalog"></a>8.5 How can I keep a log of the packages I added to the system? I'd like to know when which package upgrades and removals have occured!</h2> - -<p> -Passing the <samp>--log</samp>-option to <code>dpkg</code> makes -<code>dpkg</code> log status change updates and actions. It logs both the -<code>dpkg</code>-invokation (e.g. -</p> - -<pre> - 2005-12-30 18:10:33 install hello 1.3.18 2.1.1-4 -</pre> - -<p> -) and the results (e.g. -</p> - -<pre> - 2005-12-30 18:10:35 status installed hello 2.1.1-4 -</pre> - -<p> -) If you'd like to log all your <code>dpkg</code> invokations (even those done -using frontends like <code>aptitude</code>), you could add -</p> - -<pre> - log /var/log/dpkg.log -</pre> - -<p> -to your <code>/etc/dpkg/dpkg.cfg</code>. Be sure the created logfile gets -rotated periodically. If you're using <code>logrotate</code>, this can be -achieved by creating a file <code>/etc/logrotate.d/dpkg</code> with contents -</p> - -<pre> - /var/log/dpkg { - missingok - notifempty - } -</pre> - -<p> -More details on <code>dpkg</code> logging can be found in the -<code>dpkg(1)</code> manual page. -</p> - -<p> -<code>aptitude</code> logs the package installations, removals, and upgrades -that it intends to perform to <code>/var/log/aptitude</code>. Note that the -<em>results</em> of those actions are not recorded in this file! -</p> - -<p> -Another way to record your actions is to run your package management session -within the <code>script(1)</code> program. -</p> - -<hr> - -<p> -[ <a href="ch-pkgtools.en.html">previous</a> ] -[ <a href="index.en.html#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ 8 ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-kernel.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/footnotes.en.html b/includes/sid/common/doc/FAQ/html/footnotes.en.html deleted file mode 100644 index 37d57bb..0000000 --- a/includes/sid/common/doc/FAQ/html/footnotes.en.html +++ /dev/null @@ -1,112 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ - Footnotes</title> - -</head> - -<body> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br>Footnotes</h1> - -<h2><a href="ch-ftparchives.en.html#fr1" name="f1">1</a></h2> - -<p> -When the present-day sid did not exist, the FTP site organization had one major -flaw: there was an assumption that when an architecture is created in the -current unstable, it will be released when that distribution becomes the new -stable. For many architectures that isn't the case, with the result that those -directories had to be moved at release time. This was impractical because the -move would chew up lots of bandwidth. -</p> - -<p> -The archive administrators worked around this problem for several years by -placing binaries for unreleased architectures in a special directory called -"sid". For those architectures not yet released, the first time they -were released there was a link from the current stable to sid, and from then on -they were created inside the unstable tree as normal. This layout was somewhat -confusing to users. -</p> - -<p> -With the advent of package pools (see <a href="#s-pools">What's in the -<samp>pool</samp> directory?, Section 5.10</a>), binary packages began to be -stored in a canonical location in the pool, regardless of the distribution, so -releasing a distribution no longer causes large bandwidth consumption on the -mirrors (there is, however, a lot of gradual bandwidth consumption throughout -the development process). -</p> - -<h2><a href="ch-ftparchives.en.html#fr2" name="f2">2</a></h2> - -<p> -<samp>dists/stable/main</samp>, <samp>dists/stable/contrib</samp>, -<samp>dists/stable/non-free</samp>, and <samp>dists/unstable/main/</samp>, etc. -</p> - -<h2><a href="ch-ftparchives.en.html#fr3" name="f3">3</a></h2> - -<p> -Historically, packages were kept in the subdirectory of <samp>dists</samp> -corresponding to which distribution contained them. This turned out to cause -various problems, such as large bandwidth consumption on mirrors when major -changes were made. This was fixed with the introduction of the package pool. -</p> - -<p> -The <samp>dists</samp> directories are still used for the index files used by -programs like <samp>apt</samp>. You may also still see paths containing -<samp>dists/potato</samp> or <samp>dists/woody</samp> in the Filename header -field of some older packages. -</p> - -<h2><a href="ch-pkgtools.en.html#fr4" name="f4">4</a></h2> - -<p> -Notice that there are ports that make this tool available with other package -management systems, like Red Hat package manager, also known as -<code>rpm</code> -</p> - -<h2><a href="ch-pkgtools.en.html#fr5" name="f5">5</a></h2> - -<p> -Although this can also lead to systems with more packages installed than they -actually need to work. -</p> - -<h2><a href="ch-support.en.html#fr6" name="f6">6</a></h2> - -<p> -Use the debian-<var>list-subject</var>-REQUEST@lists.debian.org address for -that. -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/FAQ/html/index.en.html b/includes/sid/common/doc/FAQ/html/index.en.html deleted file mode 100644 index 7adba8c..0000000 --- a/includes/sid/common/doc/FAQ/html/index.en.html +++ /dev/null @@ -1,311 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> - -<html> - -<head> - -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> - -<title>The Debian GNU/Linux FAQ</title> - -</head> - -<body> - -<p><a name="index"></a></p> -<hr> - -<p> -[ <a href="ch-faqinfo.en.html">previous</a> ] -[ <a href="#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-basic_defs.en.html">next</a> ] -</p> - -<hr> - -<h1> -The Debian GNU/Linux FAQ -<br></h1> - -<hr> - -<h2><a name="abstract"></a>Abstract</h2> - -<p> -This document answers questions frequently asked about Debian GNU/Linux. -</p> - -<hr> - -<h2><a name="copyright"></a>Copyright Notice</h2> - -<p> -Copyright © 1996-2005 by Software in the Public Interest -</p> - -<p> -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. -</p> - -<p> -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. -</p> - -<p> -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. -</p> - -<hr> - -<h2><a name="contents"></a>Contents</h2> - -<ul> -<li><a href="ch-basic_defs.en.html">1 Definitions and overview</a> - <ul> - <li><a href="ch-basic_defs.en.html#s-whatisfaq">1.1 What is this FAQ?</a></li> - <li><a href="ch-basic_defs.en.html#s-whatisdebian">1.2 What is Debian GNU/Linux?</a></li> - <li><a href="ch-basic_defs.en.html#s-linux">1.3 OK, now I know what Debian is... what is Linux?!</a></li> - <li><a href="ch-basic_defs.en.html#s-non-linux">1.4 Does Debian just do GNU/Linux?</a></li> - <li><a href="ch-basic_defs.en.html#s-difference">1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?</a></li> - <li><a href="ch-basic_defs.en.html#s-gnu">1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?</a></li> - <li><a href="ch-basic_defs.en.html#s-pronunciation">1.7 How does one pronounce Debian and what does this word mean?</a> - </ul></li> -<li><a href="ch-getting.en.html">2 Getting and installing Debian GNU/Linux</a> - <ul> - <li><a href="ch-getting.en.html#s-version">2.1 What is the latest version of Debian?</a></li> - <li><a href="ch-getting.en.html#s-updatestable">2.2 Are there package upgrades in `stable'?</a></li> - <li><a href="ch-getting.en.html#s-boot-floppies">2.3 Where/how can I get the Debian installation disks?</a></li> - <li><a href="ch-getting.en.html#s-cdrom">2.4 How do I install the Debian from CD-ROMs?</a></li> - <li><a href="ch-getting.en.html#s-cdimage-symlinks">2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!</a></li> - <li><a href="ch-getting.en.html#s-cdimages">2.6 I have my own CD-writer, are there CD images available somewhere?</a></li> - <li><a href="ch-getting.en.html#s-floppy">2.7 Can I install it from a pile of floppy disks?</a></li> - <li><a href="ch-getting.en.html#s-remoteinstall">2.8 Can I get and install Debian directly from a remote Internet site?</a> - </ul></li> -<li><a href="ch-compat.en.html">3 Compatibility issues</a> - <ul> - <li><a href="ch-compat.en.html#s-arches">3.1 On what hardware architectures/systems does Debian GNU/Linux run?</a></li> - <li><a href="ch-compat.en.html#s-otherdistribs">3.2 How compatible is Debian with other distributions of Linux?</a></li> - <li><a href="ch-compat.en.html#s-otherunices">3.3 How source code compatible is Debian with other Unix systems?</a></li> - <li><a href="ch-compat.en.html#s-otherpackages">3.4 Can I use Debian packages (".deb" files) on my Red Hat/Slackware/... Linux system? Can I use Red Hat packages (".rpm" files) on my Debian GNU/Linux system?</a></li> - <li><a href="ch-compat.en.html#s-libc5">3.5 Is Debian able to run my old libc5 programs?</a></li> - <li><a href="ch-compat.en.html#s-libc5-compile">3.6 Can Debian be used to compile libc5 programs?</a></li> - <li><a href="ch-compat.en.html#s-non-debian-programs">3.7 How should I install a non-Debian program?</a></li> - <li><a href="ch-compat.en.html#s-termcap">3.8 Why can't I compile programs that require libtermcap?</a></li> - <li><a href="ch-compat.en.html#s-accelx">3.9 Why can't I install AccelX?</a></li> - <li><a href="ch-compat.en.html#s-motifnls">3.10 Why do my old XFree 2.1 Motif applications crash?</a> - </ul></li> -<li><a href="ch-software.en.html">4 Software available in the Debian system</a> - <ul> - <li><a href="ch-software.en.html#s-apps">4.1 What types of applications and development software are available for Debian GNU/Linux?</a></li> - <li><a href="ch-software.en.html#s-softwareauthors">4.2 Who wrote all that software?</a></li> - <li><a href="ch-software.en.html#s-pkglist">4.3 How can I get a current list of programs that have been packaged for Debian?</a></li> - <li><a href="ch-software.en.html#s-missing">4.4 What is missing from Debian GNU/Linux?</a></li> - <li><a href="ch-software.en.html#s-no-devs">4.5 Why do I get "ld: cannot find -lfoo" messages when compiling programs? Why aren't there any libfoo.so files in Debian library packages?</a></li> - <li><a href="ch-software.en.html#s-java">4.6 (How) Does Debian support Java?</a></li> - <li><a href="ch-software.en.html#s-isitdebian">4.7 How can I check that I am using a Debian system, and what version is it?</a></li> - <li><a href="ch-software.en.html#s-nonenglish">4.8 How does Debian support non-English languages?</a></li> - <li><a href="ch-software.en.html#s-usexports">4.9 What about the US export regulation limitations?</a></li> - <li><a href="ch-software.en.html#s-pine">4.10 Where is pine?</a></li> - <li><a href="ch-software.en.html#s-qmail">4.11 Where is qmail/ezmlm/djbdns?</a> - </ul></li> -<li><a href="ch-ftparchives.en.html">5 The Debian FTP archives</a> - <ul> - <li><a href="ch-ftparchives.en.html#s-dirtree">5.1 What are all those directories at the Debian FTP archives?</a></li> - <li><a href="ch-ftparchives.en.html#s-dists">5.2 How many Debian distributions are there in the <samp>dists</samp> directory?</a></li> - <li><a href="ch-ftparchives.en.html#s-codenames">5.3 What are all those names like slink, potato, etc.?</a> - <ul> - <li><a href="ch-ftparchives.en.html#s-oldcodenames">5.3.1 Which other codenames have been used in the past?</a></li> - <li><a href="ch-ftparchives.en.html#s-sourceforcodenames">5.3.2 Where do these codenames come from?</a> - </ul></li> - <li><a href="ch-ftparchives.en.html#s-sid">5.4 What about "sid"?</a></li> - <li><a href="ch-ftparchives.en.html#s-stable">5.5 What does the stable directory contain?</a></li> - <li><a href="ch-ftparchives.en.html#s-testing">5.6 What does the testing directory contain?</a> - <ul> - <li><a href="ch-ftparchives.en.html#s-frozen">5.6.1 What about "testing"? How is it `frozen'?</a> - </ul></li> - <li><a href="ch-ftparchives.en.html#s-unstable">5.7 What does the unstable directory contain?</a></li> - <li><a href="ch-ftparchives.en.html#s-archsections">5.8 What are all those directories inside <samp>dists/stable/main</samp>?</a></li> - <li><a href="ch-ftparchives.en.html#s-source">5.9 Where is the source code?</a></li> - <li><a href="ch-ftparchives.en.html#s-pools">5.10 What's in the <samp>pool</samp> directory?</a></li> - <li><a href="ch-ftparchives.en.html#s-incoming">5.11 What is "incoming"?</a></li> - <li><a href="ch-ftparchives.en.html#s-ownrepository">5.12 How do I set up my own apt-able repository?</a> - </ul></li> -<li><a href="ch-pkg_basics.en.html">6 Basics of the Debian package management system</a> - <ul> - <li><a href="ch-pkg_basics.en.html#s-package">6.1 What is a Debian package?</a></li> - <li><a href="ch-pkg_basics.en.html#s-deb-format">6.2 What is the format of a Debian binary package?</a></li> - <li><a href="ch-pkg_basics.en.html#s-pkgname">6.3 Why are Debian package file names so long?</a></li> - <li><a href="ch-pkg_basics.en.html#s-controlfile">6.4 What is a Debian control file?</a></li> - <li><a href="ch-pkg_basics.en.html#s-conffile">6.5 What is a Debian conffile?</a></li> - <li><a href="ch-pkg_basics.en.html#s-maintscripts">6.6 What is a Debian preinst, postinst, prerm, and postrm script?</a></li> - <li><a href="ch-pkg_basics.en.html#s-priority">6.7 What is an <em>Essential</em> <em>Required</em>, <em>Important</em>, <em>Standard</em>, <em>Optional</em>, or <em>Extra</em> package?</a></li> - <li><a href="ch-pkg_basics.en.html#s-virtual">6.8 What is a Virtual Package?</a></li> - <li><a href="ch-pkg_basics.en.html#s-depends">6.9 What is meant by saying that a package <em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, <em>Conflicts</em>, <em>Replaces</em> or <em>Provides</em> another package?</a></li> - <li><a href="ch-pkg_basics.en.html#s-pre-depends">6.10 What is meant by Pre-Depends?</a></li> - <li><a href="ch-pkg_basics.en.html#s-pkgstatus">6.11 What is meant by <em>unknown</em>, <em>install</em>, <em>remove</em> <em>purge</em> and <em>hold</em> in the package status?</a></li> - <li><a href="ch-pkg_basics.en.html#s-puttingonhold">6.12 How do I put a package on hold?</a></li> - <li><a href="ch-pkg_basics.en.html#s-sourcepkgs">6.13 How do I install a source package?</a></li> - <li><a href="ch-pkg_basics.en.html#s-sourcebuild">6.14 How do I build binary packages from a source package?</a></li> - <li><a href="ch-pkg_basics.en.html#s-creatingdebs">6.15 How do I create Debian packages myself?</a> - </ul></li> -<li><a href="ch-pkgtools.en.html">7 The Debian package management tools</a> - <ul> - <li><a href="ch-pkgtools.en.html#s-pkgprogs">7.1 What programs does Debian provide for managing its packages?</a> - <ul> - <li><a href="ch-pkgtools.en.html#s-dpkg">7.1.1 dpkg</a></li> - <li><a href="ch-pkgtools.en.html#s-apt-get">7.1.2 APT</a></li> - <li><a href="ch-pkgtools.en.html#s-aptitude">7.1.3 aptitude</a></li> - <li><a href="ch-pkgtools.en.html#s-dselect">7.1.4 dselect</a></li> - <li><a href="ch-pkgtools.en.html#s-dpkg-extra">7.1.5 Other package management tools</a> - </ul></li> - <li><a href="ch-pkgtools.en.html#s-updaterunning">7.2 Debian claims to be able to update a running program; how is this accomplished?</a></li> - <li><a href="ch-pkgtools.en.html#s-whatpackages">7.3 How can I tell what packages are already installed on a Debian system?</a></li> - <li><a href="ch-pkgtools.en.html#s-filesearch">7.4 How can I find out what package produced a particular file?</a></li> - <li><a href="ch-pkgtools.en.html#s-datapackages">7.5 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?</a> - </ul></li> -<li><a href="ch-uptodate.en.html">8 Keeping your Debian system up-to-date</a> - <ul> - <li><a href="ch-uptodate.en.html#s-libc5to6upgrade">8.1 How can I upgrade my Debian 1.3.1 (or earlier) distribution, based on libc5, to 2.0 (or later), based on libc6?</a></li> - <li><a href="ch-uptodate.en.html#s-howtocurrent">8.2 How can I keep my Debian system current?</a> - <ul> - <li><a href="ch-uptodate.en.html#s-aptitude-upgrade">8.2.1 aptitude</a></li> - <li><a href="ch-uptodate.en.html#s-apt">8.2.2 apt-get, dselect and apt-cdrom</a></li> - <li><a href="ch-uptodate.en.html#s-dpkg-ftp">8.2.3 dpkg-ftp</a></li> - <li><a href="ch-uptodate.en.html#s-mirror">8.2.4 mirror</a></li> - <li><a href="ch-uptodate.en.html#s-dpkg-mountable">8.2.5 dpkg-mountable</a> - </ul></li> - <li><a href="ch-uptodate.en.html#s-upgradesingle">8.3 Must I go into single user mode in order to upgrade a package?</a></li> - <li><a href="ch-uptodate.en.html#s-savedebs">8.4 Do I have to keep all those .deb archive files on my disk?</a></li> - <li><a href="ch-uptodate.en.html#s-keepingalog">8.5 How can I keep a log of the packages I added to the system? I'd like to know when which package upgrades and removals have occured!</a> - </ul></li> -<li><a href="ch-kernel.en.html">9 Debian and the kernel</a> - <ul> - <li><a href="ch-kernel.en.html#s-non-debian-kernel">9.1 Can I install and compile a kernel without some Debian-specific tweaking?</a></li> - <li><a href="ch-kernel.en.html#s-customkernel">9.2 What tools does Debian provide to build custom kernels?</a></li> - <li><a href="ch-kernel.en.html#s-custombootdisk">9.3 How can I make a custom boot floppy?</a></li> - <li><a href="ch-kernel.en.html#s-modules">9.4 What special provisions does Debian provide to deal with modules?</a></li> - <li><a href="ch-kernel.en.html#s-removeoldkernel">9.5 Can I safely de-install an old kernel package, and if so, how?</a> - </ul></li> -<li><a href="ch-customizing.en.html">10 Customizing your installation of Debian GNU/Linux</a> - <ul> - <li><a href="ch-customizing.en.html#s-papersize">10.1 How can I ensure that all programs use the same paper size?</a></li> - <li><a href="ch-customizing.en.html#s-hardwareaccess">10.2 How can I provide access to hardware peripherals, without compromising security?</a></li> - <li><a href="ch-customizing.en.html#s-consolefont">10.3 How do I load a console font on startup the Debian way?</a></li> - <li><a href="ch-customizing.en.html#s-appdefaults">10.4 How can I configure an X11 program's application defaults?</a></li> - <li><a href="ch-customizing.en.html#s-booting">10.5 Every distribution seems to have a different boot-up method. Tell me about Debian's.</a></li> - <li><a href="ch-customizing.en.html#s-custombootscripts">10.6 It looks as if Debian does not use <samp>rc.local</samp> to customize the boot process; what facilities are provided?</a></li> - <li><a href="ch-customizing.en.html#s-interconffiles">10.7 How does the package management system deal with packages that contain configuration files for other packages?</a></li> - <li><a href="ch-customizing.en.html#s-divert">10.8 How do I override a file installed by a package, so that a different version can be used instead?</a></li> - <li><a href="ch-customizing.en.html#s-localpackages">10.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?</a></li> - <li><a href="ch-customizing.en.html#s-diverse">10.10 Some users like mawk, others like gawk; some like vim, others like elvis; some like trn, others like tin; how does Debian support diversity?</a> - </ul></li> -<li><a href="ch-support.en.html">11 Getting support for Debian GNU/Linux</a> - <ul> - <li><a href="ch-support.en.html#s-debiandocs">11.1 What other documentation exists on and for a Debian system?</a></li> - <li><a href="ch-support.en.html#s-onlineresources">11.2 Are there any on-line resources for discussing Debian?</a> - <ul> - <li><a href="ch-support.en.html#s11.2.1">11.2.1 Mailing lists</a></li> - <li><a href="ch-support.en.html#s11.2.2">11.2.2 Maintainers</a></li> - <li><a href="ch-support.en.html#s11.2.3">11.2.3 Usenet newsgroups</a> - </ul></li> - <li><a href="ch-support.en.html#s-searchtools">11.3 Is there a quick way to search for information on Debian GNU/Linux?</a></li> - <li><a href="ch-support.en.html#s-buglogs">11.4 Are there logs of known bugs?</a></li> - <li><a href="ch-support.en.html#s-bugreport">11.5 How do I report a bug in Debian?</a> - </ul></li> -<li><a href="ch-contributing.en.html">12 Contributing to the Debian Project</a> - <ul> - <li><a href="ch-contributing.en.html#s-contrib">12.1 How can I become a Debian software developer?</a></li> - <li><a href="ch-contributing.en.html#s-contribresources">12.2 How can I contribute resources to the Debian project?</a></li> - <li><a href="ch-contributing.en.html#s-supportingorganizations">12.3 How can I contribute financially to the Debian project?</a> - <ul> - <li><a href="ch-contributing.en.html#s-SPI">12.3.1 Software in the Public Interest</a></li> - <li><a href="ch-contributing.en.html#s-FSF">12.3.2 Free Software Foundation</a> - </ul></li> - </ul></li> -<li><a href="ch-redistrib.en.html">13 Redistributing Debian GNU/Linux in a commercial product</a> - <ul> - <li><a href="ch-redistrib.en.html#s-sellcds">13.1 Can I make and sell Debian CDs?</a></li> - <li><a href="ch-redistrib.en.html#s-packagednonfree">13.2 Can Debian be packaged with non-free software?</a></li> - <li><a href="ch-redistrib.en.html#s-childistro">13.3 I am making a special Linux distribution for a "vertical market". Can I use Debian GNU/Linux for the guts of a Linux system and add my own applications on top of it?</a></li> - <li><a href="ch-redistrib.en.html#s-commercialdebs">13.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?</a> - </ul></li> -<li><a href="ch-nexttime.en.html">14 Changes expected in the next major release of Debian</a> - <ul> - <li><a href="ch-nexttime.en.html#s-security">14.1 Increased security</a></li> - <li><a href="ch-nexttime.en.html#s-i18n">14.2 Extended support for non-English users</a></li> - <li><a href="ch-nexttime.en.html#s-morearches">14.3 More architectures</a></li> - <li><a href="ch-nexttime.en.html#s-morekernels">14.4 More kernels</a> - </ul></li> -<li><a href="ch-faqinfo.en.html">15 General information about the FAQ</a> - <ul> - <li><a href="ch-faqinfo.en.html#s-authors">15.1 Authors</a></li> - <li><a href="ch-faqinfo.en.html#s-feedback">15.2 Feedback</a></li> - <li><a href="ch-faqinfo.en.html#s-latest">15.3 Availability</a></li> - <li><a href="ch-faqinfo.en.html#s-docformat">15.4 Document format</a></li> - </ul></li> -</ul> - -<hr> - -<p> -[ <a href="ch-faqinfo.en.html">previous</a> ] -[ <a href="#contents">Contents</a> ] -[ <a href="ch-basic_defs.en.html">1</a> ] -[ <a href="ch-getting.en.html">2</a> ] -[ <a href="ch-compat.en.html">3</a> ] -[ <a href="ch-software.en.html">4</a> ] -[ <a href="ch-ftparchives.en.html">5</a> ] -[ <a href="ch-pkg_basics.en.html">6</a> ] -[ <a href="ch-pkgtools.en.html">7</a> ] -[ <a href="ch-uptodate.en.html">8</a> ] -[ <a href="ch-kernel.en.html">9</a> ] -[ <a href="ch-customizing.en.html">10</a> ] -[ <a href="ch-support.en.html">11</a> ] -[ <a href="ch-contributing.en.html">12</a> ] -[ <a href="ch-redistrib.en.html">13</a> ] -[ <a href="ch-nexttime.en.html">14</a> ] -[ <a href="ch-faqinfo.en.html">15</a> ] -[ <a href="ch-basic_defs.en.html">next</a> ] -</p> - -<hr> - -<p> -The Debian GNU/Linux FAQ -</p> - -<address> -version 3.1.5, 17 January 2007<br> -<br> -Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> -<br> -</address> -<hr> - -</body> - -</html> - diff --git a/includes/sid/common/doc/mailing-lists.txt b/includes/sid/common/doc/mailing-lists.txt deleted file mode 100644 index 5d4a6ed..0000000 --- a/includes/sid/common/doc/mailing-lists.txt +++ /dev/null @@ -1,1673 +0,0 @@ - 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 - - <listname>-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 : Major news and very important changes in the project - are announced here. - Moderated : yes - Subscription: open - - debian-chinese-big5@lists.debian.org - - Description : Debian Chinese Project: Chinese localization (l10n), - documentation and web site translation, user support - etc. - - Posts may be in English or Big5-encoded Chinese. - All posts are automatically converted to GB encoding - and cross-posted to the debian-chinese-gb mailing list. - - If you would rather read and post in GB-encoded - Chinese, please subscribe to debian-chinese-gb instead. - Language : Chinese - Moderated : subscribers - Subscription: open - - debian-chinese-gb@lists.debian.org - - Description : Debian Chinese Project: Chinese localization (l10n) - issues, documentation and web site translation, user - support etc. - - Posts may be in English or GB-encoded Chinese. - All posts are automatically converted to Big5 encoding - and cross-posted to the debian-chinese-big5 mailing list. - - If you would rather read and post in Big5-encoded - Chinese, please subscribe to debian-chinese-big5 instead. - Language : Chinese - Moderated : subscribers - Subscription: open - - debian-commercial@lists.debian.org - - Description : Information about Debian related products from - software and hardware vendors is published here. - This is a moderated list, so please send your - submissions to the moderator at press@debian.org. - - Please note that posting commercial posts to any - other Debian mailing list is not permitted. - Moderated : yes - Subscription: open - - debian-esperanto@lists.debian.org - - Description : Debian users who speak Esperanto. - Language : Esperanto - Moderated : no - Subscription: open - - debian-firewall@lists.debian.org - - Description : Discussion of implementation and maintenance of - firewalls using Debian. Both basic issues and new - more exotic developments are discussed here. - Moderated : no - Subscription: open - - debian-isp@lists.debian.org - - Description : Discussion about issues and problems specific to - Internet Service Providers (ISPs for short) that - use Debian. - Moderated : no - Subscription: open - - debian-italian@lists.debian.org - - Description : Support for Debian users that speak Italian. - (High-volume mailing list.) - Language : Italian - Moderated : no - Subscription: open - - debian-japanese@lists.debian.org - - Description : Support for Debian users that speak Japanese, - Japanese localization issues, integrating - Debian JP packages into Debian etc. - - The English language is allowed, but using Japanese is - encouraged even for those who aren't native speakers. - - For native Japanese, Debian JP Project provides - several mailing lists discussing the Debian system in - Japanese, see http://www.debian.or.jp/MailingList.html - Language : English/Japanese - Moderated : no - Subscription: open - - debian-kde@lists.debian.org - - Description : Discussions related to KDE in Debian. - Those developing KDE-based packages are - encouraged to use this to discuss issues - and share their experience. - Moderated : no - Subscription: open - - debian-laptop@lists.debian.org - - Description : Installing, updating and using laptops with Debian. - Suggestions on special packaging, complaints, etc. - are welcome. - Moderated : no - Subscription: open - - debian-news-french@lists.debian.org - - Description : News about Debian for users speaking French. - Language : French - Moderated : yes - Subscription: open - - debian-news-german@lists.debian.org - - Description : News about Debian for users speaking German. - Language : German - Moderated : yes - Subscription: open - - debian-news-italian@lists.debian.org - - Description : Releases, news, internationalization efforts and - other related news about Debian for Italian-speaking users. - Language : Italian - Moderated : yes - Subscription: open - - debian-news-portuguese@lists.debian.org - - Description : Releases, news, internationalization efforts and other - related news about Debian for users speaking Portuguese. - Language : Portuguese - Moderated : yes - Subscription: open - - debian-news-spanish@lists.debian.org - - Description : Releases, news, internationalization efforts and - other related news about Debian for Spanish-speaking users. - Language : Spanish - Moderated : yes - Subscription: open - - debian-news@lists.debian.org - - Description : General news about the distribution and the project. - - The current events and news about Debian are - summarized in the Debian Weekly News, a newsletter - regularly posted on this list. - Moderated : yes - Subscription: open - - debian-russian@lists.debian.org - - Description : Support for Debian users that speak Russian, - and Russian localization issues: translating - "po" files, coordinating patches for Debian - packages to work with the Russian language. - Language : Russian - Moderated : no - Subscription: open - - debian-security-announce@lists.debian.org - - Description : The security team informs the users about security - problems by posting security advisories about - Debian packages on this list. - Moderated : yes - Subscription: open - - debian-user-catalan@lists.debian.org - - Description : Support for Debian users that speak Catalan. - Language : Catalan - Moderated : no - Subscription: open - - debian-user-danish@lists.debian.org - - Description : Support for Debian users who speak Danish. - Language : Danish - Moderated : no - Subscription: open - - debian-user-french@lists.debian.org - - Description : Support for Debian users that speak French. - (High-volume mailing list.) - Language : French - Moderated : no - Subscription: open - - debian-user-german@lists.debian.org - - Description : Support for Debian users that speak German. - (High-volume mailing list.) - Language : German - Moderated : no - Subscription: open - - debian-user-hungarian - - Description : Support for Debian users that speak Hungarian. - Language : Hungarian - Subscription: http://lists.linux.hu/mailman/listinfo/debian - - debian-user-icelandic@lists.debian.org - - Description : Support for Debian users that speak Icelandic. - Moderated : no - Subscription: open - - debian-user-indonesian@lists.debian.org - - Description : Support for Debian users who speak Indonesian. - Language : Indonesian - Moderated : no - Subscription: open - - debian-user-polish@lists.debian.org - - Description : Support for Debian users that speak Polish. - Language : Polish - Moderated : no - Subscription: open - - debian-user-portuguese@lists.debian.org - - Description : Support for Debian users who speak Portuguese. - (High-volume mailing list.) - Language : Portuguese (both European and Brazilian, and other dialects are welcome) - Moderated : no - Subscription: open - - debian-user-spanish@lists.debian.org - - Description : Support for Debian users that speak Spanish. - (High-volume mailing list.) - Language : Spanish - Moderated : no - Subscription: open - - debian-user-swedish@lists.debian.org - - Description : Support for Debian users that speak Swedish. - Language : Swedish - Moderated : no - Subscription: open - - debian-user-turkish@lists.debian.org - - Description : Support for Debian users that speak Turkish. - Language : Turkish - Moderated : no - Subscription: open - - debian-user-ukrainian@lists.debian.org - - Description : Support for Debian users who speak Ukrainian. - Language : Ukrainian - Moderated : no - Subscription: open - - debian-user-vietnamese@lists.debian.org - - Description : Support for Debian users that speak Vietnamese, and discussions on translations - Language : Vietnamese - Moderated : no - Subscription: open - - debian-user@lists.debian.org - - Description : Support for Debian users who speak English. - (High-volume mailing list.) - Digest : debian-user-digest@lists.debian.org - Moderated : no - Subscription: open - - debian-volatile-announce@lists.debian.org - - Description : Announcements relating to the debian-volatile project include new uploads and changes - Moderated : yes - Subscription: open - - debian-volatile@lists.debian.org - - Description : Discussion about 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 : User and Developer list for accessibility-related issues. - Moderated : no - Subscription: open - - debian-admin@lists.debian.org - - Description : This is our internal list used for administering the - Debian machine park. - Moderated : no - Subscription: closed - - debian-apache@lists.debian.org - - Description : Maintenance of the Apache HTTP server and related - packages in Debian: code changes, reproducing bugs, - talking to upstream etc. - - It is neither for submitting bug reports (please - use the BTS for that), nor for support requests. - Moderated : no - Subscription: open - - debian-beowulf@lists.debian.org - - Description : Discussion about Beowulf systems running Debian. - Moderated : no - Subscription: open - - debian-boot@lists.debian.org - - Description : Discussion and maintenance of the Debian - installation system. - Moderated : no - Subscription: open - - debian-cd@lists.debian.org - - Description : Creating Debian CD sets, official and unofficial. - Moderated : no - Subscription: open - - debian-ctte-private@lists.debian.org - - Description : Private communication between tech committee members. - Moderated : no - Subscription: Debian Technical Committee only - - debian-ctte@lists.debian.org - - Description : Public meeting, business and announcements of the Debian - Technical Committee - Moderated : subscribers - Subscription: open - - debian-custom@lists.debian.org - - Description : People on this list work on the challenges common to - all custom Debian distributions, ensuring that the - tools and procedures developed are shared, making - the most efficient use of our energies. - Moderated : no - Subscription: open - - debian-dak@lists.debian.org - - Description : Discussion about the Debian Archive Software, consisting of dak for the - archive and the buildd related parts wanna-build/sbuild. - Moderated : no - Subscription: open - - debian-ddtp@lists.debian.org - - Description : Discussions on the DDTP and coordination of the development process - Moderated : no - Subscription: open - - debian-debbugs-cvs@lists.debian.org - - Description : CVS commit messages when modifications are done to - debbugs - Moderated : no - Subscription: open - - debian-debbugs@lists.debian.org - - Description : Discussion and development of debbugs, the Debian - Bug Tracking System software. - Moderated : no - Subscription: open - - debian-desktop@lists.debian.org - - Description : Discussion about the Debian Desktop sub-project, - the integration of the various desktop-related - packages, bug reports, questions and patches. - Moderated : no - Subscription: open - - debian-devel-announce@lists.debian.org - - Description : Announcements of development issues like policy changes, - important release issues &c. - Moderated : signed - Subscription: open - - debian-devel-austrian - - Description : Discussion among the Debian developers in Austria. - Language : (mostly) German - Subscription: https://www.gibraltar.at/mailman/listinfo/debian-at - - debian-devel-french@lists.debian.org - - Description : This is the list used to discuss development - issues in French. - Moderated : no - Subscription: open - - debian-devel-games@lists.debian.org - - Description : Development and packaging discussion for games and game-related software in Debian. - Identification of potential new games suitable for Debian. Discussion about - infrastructure issues covering a wider range of games (e.g. multiplayer issues). - Moderated : no - Subscription: open - - debian-devel-italian@lists.debian.org - - Description : Discussion on development issues in Italian. - Moderated : no - Subscription: open - - debian-devel-portuguese@lists.debian.org - - Description : This is the list used by Portuguese developers - (or wannabes) to discuss development issues. - Moderated : no - Subscription: open - - debian-devel-spanish@lists.debian.org - - Description : This is the list used by Spanish developers - (or wannabes) to discuss issues besides - translation: provide help for new Spanish - developers, arrange key-signing meetings, arrange - work in booths on different shows, share experience - etc. - Moderated : no - Subscription: open - - debian-devel@lists.debian.org - - Description : Discussion about technical development topics. - (High-volume mailing list.) - Digest : debian-devel-digest@lists.debian.org - Moderated : no - Subscription: open - - debian-doc@lists.debian.org - - Description : Debian Documentation Project: anything related - to documentation in Debian is on topic here. - Moderated : no - Subscription: open - - debian-dpkg-bugs@lists.debian.org - - Description : Email sent by the bug tracking system regarding - the dpkg packages. - Moderated : no - Subscription: open - - debian-dpkg-cvs@lists.debian.org - - Description : The CVS commit messages from the dpkg CVS tree. - Moderated : no - Subscription: open - - debian-dpkg@lists.debian.org - - Description : Discussions and maintenance of dpkg, the basis of - the Debian packaging system. - Moderated : no - Subscription: open - - debian-edu-french@lists.debian.org - - Description : Discussions in french between all educational Debian-based projects. - This list should ease the collaboration between the projects themselves - and between Debian and those projects. - Moderated : no - Subscription: open - - debian-edu@lists.debian.org - - Description : Making Debian the best distribution in the - education landscape. - Moderated : no - Subscription: open - - debian-emacsen@lists.debian.org - - Description : Discussion of all things related to the several - Debian Emacs packages and their add-ons. - Moderated : no - Subscription: open - - debian-email@lists.debian.org - - Description : A generic "grab-bag" list for Debian related - correspondence such as contacting upstream authors - about licenses, bugs etc, or discussing the project - with others where it might be useful to have the - discussion archived somewhere. - - This list is archived internally on a Debian Project - machine, only developers have access to the archive. - Moderated : no - Subscription: developers only - - debian-embedded@lists.debian.org - - Description : Discussion about improving Debian for use with - embedded systems, including building cross-compiler - toolchains, cross-compiling packages, creating and - updating system images, using alternate libraries, - compile-time configuration of packages, etc. - Moderated : no - Subscription: open - - debian-events-eu@lists.debian.org - - Description : Discussions and organizational stuff about booths for - Debian at european exhibitions. - Moderated : no - Subscription: open - - debian-events-na@lists.debian.org - - Description : Discussions and organizational stuff about booths and - presentations for Debian at North American exhibitions. - Moderated : no - Subscription: open - - debian-events-nl@lists.debian.org - - Description : Announcements of small meetings and keysigning parties of Dutch - Debian Developers and other discussions of interest mainly for - Debian people in the Netherlands. Posts in both Dutch and English - are common. - Moderated : no - Subscription: open - - debian-flash@lists.debian.org - - Description : For discussion of issues relating to the development and use of Debian for - Flash development and viewing of Flash content. For general discussion of Flash - related free software, please visit the osflash community: http://osflash.org - Moderated : no - Subscription: open - - debian-gcc@lists.debian.org - - Description : Discussion on Debian packaging of GCC, the - GNU compiler collection: bug reports, porting - issues, any kind of questions or patches. - Moderated : no - Subscription: open - - debian-glibc@lists.debian.org - - Description : Discussion on Debian packaging of the GNU C Library, - the most important library on Debian systems. - Moderated : no - Subscription: open - - debian-gtk-gnome@lists.debian.org - - Description : Discussion and coordination among maintainers of - Debian's GTK+, GNOME and dependent or related - packages. - Moderated : no - Subscription: open - - debian-hams@lists.debian.org - - Description : Support for HAMRadio within Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-handheld@lists.debian.org - - Description : Discussion among people who run Debian on - handheld computers. - Moderated : no - Subscription: open - - debian-ipv6@lists.debian.org - - Description : Discussions on the use of Debian in an IPv6 network - and implementing IPv6 support in Debian packages. - Moderated : no - Subscription: open - - debian-java@lists.debian.org - - Description : Discussion about the packaging and use in Debian of VMs - and compilers for the Java(tm) language, and programs - written on it. - Moderated : no - Subscription: open - - debian-jr@lists.debian.org - - Description : Discussion and working on making Debian the sort - of operating system that children will want to use. - - The Debian Jr. Project web page is at - http://www.debian.org/devel/debian-jr/ - Moderated : no - Subscription: open - - debian-kernel-maint@lists.debian.org - - Description : Discussion and development of Debian kernel packaging, - for the kernel team and other developers. - Moderated : no - Subscription: open - - debian-kernel@lists.debian.org - - Description : Kernels used with Debian (Linux, Hurd, etc.), available - patches and flavors, packaging issues, bug reports, - porting issues, automated tools, and any other - questions or patches that are kernel-related. Mostly - bug reporting is done here. - Moderated : no - Subscription: open - - debian-knoppix@lists.debian.org - - Description : Development of the Debian-based live CD/DVD takes place. As it is mainly a - development list, user questions are best placed on the debian-user list. - Moderated : no - Subscription: open - - debian-lex@lists.debian.org - - Description : Discussion on developing Debian into an operating - system that is particularly well fit for the - requirements for legal offices. The goal of - Debian-Lex is a complete system for all tasks in - legal practice which is built completely on free - software. - Moderated : no - Subscription: open - - debian-lint-maint@lists.debian.org - - Description : The maintenance of Debian "lint" tools like lintian or linda - is discussed on this list. This may or may not be limited to - bug reports regarding the checks. - Moderated : no - Subscription: open - - debian-lsb@lists.debian.org - - Description : Discussion and coordination of efforts towards ensuring - Debian meets the requirements of the Linux Standard Base. - Moderated : no - Subscription: open - - debian-med@lists.debian.org - - Description : Discussion on providing a free operating system - for medical care. - - The Debian-Med Project web page is at - http://www.debian.org/devel/debian-med/ - Moderated : no - Subscription: open - - debian-mentors@lists.debian.org - - Description : Newbie Debian developers can seek help with - packaging and other developer-related issues here. - - This list is not meant for users' questions, - but for new maintainers'! - Moderated : no - Subscription: open - - debian-multimedia@lists.debian.org - - Description : Discussion about the development of applications - that produce multimedia content, handling multimedia - data, supporting multimedia hardware etc. - Moderated : no - Subscription: open - - debian-newmaint@lists.debian.org - - Description : Discussion about the Debian New Maintainer process, - application manager reports etc. - Moderated : no - Subscription: open - - debian-nonprofit@lists.debian.org - - Description : Discussions about the subproject to support - use of Debian in non-profit organizations. - Moderated : no - Subscription: open - - debian-ocaml-maint@lists.debian.org - - Description : Packaging of Objective Caml programs and libraries. - (http://pauillac.inria.fr/caml/) - Moderated : no - Subscription: open - - debian-openoffice@lists.debian.org - - Description : Coordination of the maintenance of the OpenOffice - packages in Debian. - Moderated : no - Subscription: open - - debian-perl@lists.debian.org - - Description : The list is dedicated to coordinate the work of various - perl package maintainer and to write a kind of perl - sub-policy. - Moderated : no - Subscription: open - - debian-policy@lists.debian.org - - Description : Discussion and editing of the Debian Policy Manual. - Moderated : no - Subscription: open - - debian-printing@lists.debian.org - - Description : Discussion of issues related to printing on Debian systems. This - covers all aspects of printing, from spoolers, to RIPs and printer - drivers. The list is used for coordination of development, - integration and bugfixing of printing packages between package - maintainers. User printing and printing setup questions are also - on topic. - Moderated : no - Subscription: open - - debian-private@lists.debian.org - - Description : Private discussions among developers: only for - issues that may not be discussed on public lists. - - Anything sent there should be treated as sensitive - and not to be spread to other lists; thus - cross-posting between it and an open list defeats - the purpose of this list. - - This list is archived internally on a Debian Project - machine, only developers have access to the archive. - Moderated : no - Subscription: developers only - - debian-python@lists.debian.org - - Description : Discussion of issues related to Python on Debian - systems with a stress on packaging standards. Therefore - relevant for maintainers of Python related packages. - Moderated : no - Subscription: open - - debian-qa-packages@lists.debian.org - - Description : Bug reports against orphaned packages and discussions - about fixing them. - Moderated : no - Subscription: open - - debian-qa@lists.debian.org - - Description : Quality assurance is important for a distribution. This - list addresses this quality. - Moderated : no - Subscription: open - - debian-qt-kde@lists.debian.org - - Description : Discussion and coordination among maintainers of - Debian's Qt, KDE and dependent or related packages. - Moderated : no - Subscription: open - - debian-release@lists.debian.org - - Description : Coordination of Debian releases issues such as testing migrations, transitions - and removals. - - This list should not be considered a discussion list; discussions related to - releases issues should be held on more appropriate lists such as debian-devel, - debian-legal or debian-project. - Moderated : no - Subscription: open - - debian-ruby@lists.debian.org - - Description : Discussion of issues related to Ruby on Debian systems - with a stress on packaging standards. Therefore - relevant for maintainers of Ruby related packages. - Moderated : no - Subscription: open - - debian-science@lists.debian.org - - Description : Discussion of issues relating to the use of Debian for science research, - including useful packages, particular problems faced by scientists using - Debian, how to make Debian more useful to scientists, etc. - Moderated : no - Subscription: open - - debian-security@lists.debian.org - - Description : Discussion about security issues, including - cryptographic issues, that are of interest to - all parts of the Debian community. - - Please note that this is NOT an announcement - mailing list. If you're looking for security - advisories from Debian, subscribe to - debian-security-announce instead. - Moderated : no - Subscription: open - - debian-sgml@lists.debian.org - - Description : Discussion of issues related to SGML on Debian systems - with a stress on proper integration of tools, packaging - standards and the writing of documentation for SGML - users. Therefore relevant for maintainers of SGML - related packages. - Moderated : no - Subscription: open - - debian-ssh@lists.debian.org - - Description : Maintenance of the OpenSSH packages for Debian. - It exists to facilitate coordination of ssh - maintenance (talking to upstream, reproducing bugs, - hacking on the code, etc.). - - It is *not* the place to mail bug reports - (use the BTS for that), nor support requests. - Moderated : no - Subscription: open - - debian-testing@lists.debian.org - - Description : Finding problems with the next Debian release: - testing the installation and the upgrade process. - Moderated : no - Subscription: open - - debian-tetex-maint@lists.debian.org - - Description : Coordination of the maintenance of Debian teTeX - and related packages. - - It is not meant for user support; for that, please - use debian-user or one of the general TeX mailing - lists or news groups. - Moderated : no - Subscription: open - - debian-tex-maint@lists.debian.org - - Description : Coordination of the maintenance of Debian TeX - and related packages. - - It is not meant for user support; for that, please - use debian-user or one of the general TeX mailing - lists or news groups. - Moderated : no - Subscription: open - - debian-toolchain@lists.debian.org - - Description : Discussion about the Debian toolchain: compilers, - assemblers, linkers and such. New releases for - many of these tools are coordinated here. - Moderated : no - Subscription: open - - debian-vote@lists.debian.org - - Description : Proposals, discussions and announcements related to - Official Debian Votes. - Moderated : no - Subscription: open - - debian-webapps@lists.debian.org - - Description : This list is used to coordinate the maintenance of web application packages. - Moderated : no - Subscription: open - - debian-wnpp@lists.debian.org - - Description : Orphaning and adopting packages which is done through - the `wnpp' BTS pseudo-package is recorded on this - list. Additionally, discussion about particular bugs - and the WNPP web pages is held here. - Moderated : no - Subscription: open - - debian-www-cvs@lists.debian.org - - Description : CVS commit logs for the Debian web pages in the - webwml CVS tree. - Moderated : yes - Subscription: open - - debian-www@lists.debian.org - - Description : Design, structure and translation of Debian - web pages. All important changes to the web - site are announced here as well. - Moderated : no - Subscription: open - - debian-x@lists.debian.org - - Description : Discussion about the X Window System within Debian. - This is NOT a user support list; this list is - intended for those who deal with the source code. - Moderated : no - Subscription: open - - deity@lists.debian.org - - Description : Debian GNU/Linux will get a new, friendly frontend to - its package maintenance system. Its codename is deity - (now known as APT) and its development is discussed - here. The -digest is open to everyone. - 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 : Internationalization (i18n) of the distribution is - discussed here. - Moderated : no - Subscription: open - - debian-l10n-arabic@lists.debian.org - - Description : Discussing Arabic localization issues, mainly - translating Debian docs and programs to Arabic. - Language : Arabic - Moderated : no - Subscription: open - - debian-l10n-catalan@lists.debian.org - - Description : Discussing Catalan localization issues, mainly - translating Debian docs and programs to Catalan. - Language : Catalan - Moderated : no - Subscription: open - - debian-l10n-czech@lists.debian.org - - Description : Discussion forum for the translators of - Debian-specific packages and documentation to the Czech language. - Moderated : no - Subscription: open - - debian-l10n-danish@lists.debian.org - - Description : Discussing Danish localization issues, mainly - translating Debian docs and programs to Danish. - Language : Danish - Moderated : no - Subscription: open - - debian-l10n-dutch@lists.debian.org - - Description : Discussion forum for the translators of Debian-specific - packages and documentation to the Dutch language. - Language : Dutch - Moderated : no - Subscription: open - - debian-l10n-english@lists.debian.org - - Description : Discussing English localization issues, mainly - translating Debian docs and programs to English. - Language : English - Moderated : no - Subscription: open - - debian-l10n-esperanto@lists.debian.org - - Description : Discussing Esperanto localization issues, mainly - translating Debian docs and programs to Esperanto. - Language : Esperanto - Moderated : no - Subscription: open - - debian-l10n-finnish@lists.debian.org - - Description : Discussing Finnish localization issues, mainly - translating Debian docs and programs to Finnish. - Language : Finnish - Moderated : no - Subscription: open - - debian-l10n-french@lists.debian.org - - Description : Discussion forum for the translators of Debian-specific - packages and documentation to the French language. - Language : French - Moderated : no - Subscription: open - - debian-l10n-galician@lists.debian.org - - Description : Discussing Galician localization issues, mainly translating Debian docs and - programs to Galician. - Language : Galician - Moderated : no - Subscription: open - - debian-l10n-german@lists.debian.org - - Description : Discussing German localization issues, mainly - translating Debian docs and programs to German. - Language : German - Moderated : no - Subscription: open - - debian-l10n-greek@lists.debian.org - - Description : Discussion on Greek localization issues, mainly - translating Debian docs and programs to Greek. - Language : Greek - Moderated : no - Subscription: open - - debian-l10n-hungarian@lists.debian.org - - Description : Discussing Hungarian localization issues, mainly - translating Debian docs and programs to Hungarian. - Language : Hungarian - Moderated : no - Subscription: open - - debian-l10n-italian@lists.debian.org - - Description : Italian localization efforts within Debian. - Language : Italian - Moderated : no - Subscription: open - - debian-l10n-korean@lists.debian.org - - Description : Discussion forum for the translators of Debian-specific packages and - documentation to the Korean language. - Moderated : no - Subscription: open - - debian-l10n-persian@lists.debian.org - - Description : Discussing Persian/Farsi localization issues, mainly translating - Debian docs and programs to Persian/Farsi. - Language : Persian - Moderated : no - Subscription: open - - debian-l10n-polish@lists.debian.org - - Description : Polish localization issues, mainly translating Debian - web pages, documentation and programs to Polish. - Language : Polish - Moderated : no - Subscription: open - - debian-l10n-portuguese@lists.debian.org - - Description : Portuguese localization issues such as translating - the documentation and programs. - Language : Portuguese - Moderated : no - Subscription: open - - debian-l10n-romanian@lists.debian.org - - Description : Discussing Romanian localization issues, mainly - translating Debian docs and programs to Romanian. - Language : Romanian - Moderated : no - Subscription: open - - debian-l10n-russian@lists.debian.org - - Description : Discussing Russian localization issues, mainly - translating Debian docs and programs to Russian. - Language : Russian - Moderated : no - Subscription: open - - debian-l10n-spanish@lists.debian.org - - Description : Discussing Spanish localization issues, mainly - translating Debian docs and programs to Spanish. - Language : Spanish - Moderated : no - Subscription: open - - debian-l10n-swedish@lists.debian.org - - Description : Discussion forum for translators of Debian-specific packages - and documentation for the Swedish language. - Moderated : no - Subscription: open - - debian-l10n-turkish@lists.debian.org - - Description : Discussing Turkish localization issues, mainly - translating Debian docs and website into Turkish, - improving Turkish environment support in Debian. - Language : Turkish - Moderated : no - Subscription: open - - debian-laespiral@lists.debian.org - - Description : La Espiral (http://laespiral.org/) is a project - meant to promote the use of Debian amongst the - people who speak Spanish. We work on custom - Debian internationalisation CDs, do installation - parties and new programs for Spanish users (see - http://www.debian.org/international/spanish/). - - Becoming a member of La Espiral is for people - that do not find themselves able to contribute - technically to Debian (at first), but might be a - good step towards becoming a Debian developer. - Language : Spanish - 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 : Discussions on the m68k port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-alpha@lists.debian.org - - Description : Discussion on the Alpha port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-amd64@lists.debian.org - - Description : Porting Debian to AMD x86-64 architecture. - Moderated : no - Subscription: open - - debian-arm@lists.debian.org - - Description : Discussion on the ARM (esp. Corel Netwinder) port for - Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-bsd@lists.debian.org - - Description : Porting Debian to BSD (all *BSD variants). - Moderated : no - Subscription: open - - debian-hppa@lists.debian.org - - Description : Discussions on the PA-RISC port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-hurd@lists.debian.org - - Description : Debian port of the GNU Hurd operating system. - Moderated : no - Subscription: open - - debian-ia64@lists.debian.org - - Description : Discussions on the intel IA64 (aka Itanium, Merced) - port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-mips@lists.debian.org - - Description : Discussions on the MIPS port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-powerpc@lists.debian.org - - Description : Discussion on the PowerPC port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-s390@lists.debian.org - - Description : Discussions on the IBM S/390 port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-sparc@lists.debian.org - - Description : Discussions on the SPARC port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-superh@lists.debian.org - - Description : Discussions on the SuperH port of Debian GNU/Linux. For - more information about running Linux on SH processors, - have a look at http://www.m17n.org/linux-sh/ - Moderated : no - Subscription: open - - debian-win32@lists.debian.org - - Description : Porting the Debian distribution to Win32 systems - (Debian GNU/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 : Messages that close Debian bug reports. - Moderated : no - Subscription: open - - debian-bugs-dist@lists.debian.org - - Description : All submitted bug reports as well as further information - on them are distributed here. - Moderated : no - Subscription: open - - debian-bugs-forwarded@lists.debian.org - - Description : Mails in which Debian maintainers forward bugs - to their upstream authors. - Moderated : no - Subscription: open - - debian-bugs-rc@lists.debian.org - - Description : All mail regarding release-critical bugs is - copied to this mailing list. - - See http://bugs.debian.org/release-critical/ - for more information. - Moderated : no - Subscription: open - -Miscellaneous Debian lists - - There are several mailing lists which don't - necessarily have a clear distinction in the - audience, between developers and users. - - debian-all-changes@lists.debian.org - - Description : Notices about uploaded binary-all packages for the - stable distribution. - Moderated : no - Subscription: open - - debian-alpha-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable alpha - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-arm-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable arm - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-cd-vendors@lists.debian.org - - Description : Communication among and with vendors of Debian CDs. - (Low-volume mailing list.) - Moderated : no - Subscription: open - - debian-changes@lists.debian.org - - Description : Changes to the releases are announced here. This - includes security upgrades as well as important - bugfixes. - Digest : debian-changes-digest@lists.debian.org - Moderated : yes - Subscription: open - - debian-consultants@lists.debian.org - - Description : Communication among Debian consultants. See at the bottom of the - consultants page (http://www.debian.org/consultants/#policy) for how - to add/update entries to this page. - Moderated : no - Subscription: open - - debian-curiosa@lists.debian.org - - Description : Funny thing from and with the project, funny quotes, - discussions irc communication and fortune cookies. - Some kind of (de.)alt.netdigest for Debian-related stuff. - Moderated : no - Subscription: open - - debian-devel-all-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable - distribution. (Quiz: binary-all or all binaries?) - Moderated : no - Subscription: open - - debian-devel-alpha-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable alpha - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-arm-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable arm - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable - distribution, from developers, buildds and katie, - the archive sentinel. - (High-volume mailing list.) - Moderated : no - Subscription: open - - debian-devel-hurd-i386-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable - hurd-i386 distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-i386-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable i386 - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-m68k-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable m68k - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-powerpc-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable powerpc - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-s390-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable s390 - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-sparc-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable sparc - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-hurd-i386-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable hurd-i386 - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-i386-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable i386 - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-jobs@lists.debian.org - - Description : Job postings can be published on this list in - order to make them public to members of the Debian - community. While the jobs do not necessarily have - to involve the use of Debian, it is encouraged that - they do. Jobs can be about the development of - proprietary system, but jobs involving free software - (either development or system administration) are - preferred. Please include information such as - location and remuneration if appropriate. The list - is moderated; it is also an open list - job postings - which have to be kept private should be sent to - leader@debian.org who will distribute them. - Moderated : yes - Subscription: open - - debian-legal@lists.debian.org - - Description : Discussions about legality issues such as - copyrights, patents etc. - Moderated : no - Subscription: open - - debian-m68k-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable m68k - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-mirrors-announce@lists.debian.org - - Description : Important changes to the FTP archive are announced here. - These are mainly useful to maintainers of Debian - mirrors. - Moderated : signed - Subscription: open - - debian-mirrors@lists.debian.org - - Description : Discussions relating to the Debian mirror network, - and the maintenance of mirrors. - Moderated : no - Subscription: open - - debian-powerpc-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable powerpc - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-project@lists.debian.org - - Description : Discussion about non-technical topics related - to the Debian Project. - Moderated : no - Subscription: open - - debian-publicity@lists.debian.org - - Description : Coordination of all the work related to the external - communication of Debian: drafting new announces, - collecting important information that Debian should relay - to its community, improving the infrastructure offered to - people who want to create Debian booth, etc. - Moderated : no - Subscription: open - - debian-s390-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable s390 - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-sparc-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable sparc - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-testing-changes@lists.debian.org - - Description : Changes to the "testing" distribution are announced - here. This includes various bugfixes. - Moderated : no - Subscription: open - - debian-women@lists.debian.org - - Description : Debian users and developers who wish to involve more - women in the Debian project. For discussion and - sharing of ideas as well as project collaboration. - Moderated : no - Subscription: open - - whitelist@lists.debian.org - - Description : This is a special pseudo-mailing list to which - people can subscribe to prove they are not - spammers. - - This allows one to avoid the restrictions imposed - on non-subscriber posts to other mailing lists, - in particular the mailing lists that allow posts - only from subscribers. - 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 mailing list - Moderated : no - Subscription: open - - other-sart@lists.debian.org - - Description : Discussions and announcements about SART, - a free raytracer that uses Guile extension - language and is distributed under GPL. - - The SART website is at - http://petra.zesoi.fer.hr/~silovic/sart/ - Moderated : no - Subscription: open - - other-vgui-discuss@lists.debian.org - - Description : The V C++ GUI Framework - an object-oriented GUI library - for X, Win32 and OS/2. V is licensed under the GNU - LGPL. The web page is at http://www.objectcentral.com/ . - 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/sid/install/README.mirrors.html b/includes/sid/install/README.mirrors.html deleted file mode 100644 index 24a9cdc..0000000 --- a/includes/sid/install/README.mirrors.html +++ /dev/null @@ -1,729 +0,0 @@ -<html> - -<head> - <title>Debian worldwide mirror sites</title> -</head> - -<body> -<h1 align="center">Debian worldwide mirror sites</h1> -<p>Debian is distributed (<em>mirrored</em>) 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. - -<p>Debian mirrors can be primary and secondary. The definitions are as follows: - - <blockquote> - A <strong>primary mirror</strong> site has good bandwidth, is available 24 hours a day, - and has an easy to remember name of the form ftp.<country>.debian.org. - <br> - Additionally, most of them are updated automatically after updates to the - Debian archive. The Debian archive on those sites is normally available - using both FTP and HTTP protocols. - - </blockquote> - <blockquote> - A <strong>secondary mirror</strong> 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. - - </blockquote> -<p>Use the site closest to you for the fastest downloads possible whether it is - -a primary or secondary site. The program -<a href="http://packages.debian.org/stable/net/netselect"> -<em>netselect</em></a> can be used to -determine the site with the least latency; use a download program such as - -<a href="http://packages.debian.org/stable/web/wget"> -<em>wget</em></a> or -<a href="http://packages.debian.org/stable/net/rsync"> -<em>rsync</em></a> 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. - -<p>The authoritative copy of the following list can always be found at: -<a href="http://www.debian.org/mirror/list"> http://www.debian.org/mirror/list</a>.<br> -If you know of any mirrors that are missing from this list, -please have the site maintainer fill out the form at: -<a href="http://www.debian.org/mirror/submit"> http://www.debian.org/mirror/submit</a>.<br> -Everything else you want to know about Debian mirrors: -<a href="http://www.debian.org/mirror/"> http://www.debian.org/mirror/</a>.<br> - -<h2 align="center">Primary Debian mirror sites</h2> - -<table border="0" align="center"> -<tr> - <th>Country</th> - <th>Site</th> - <th><b>Debian archive</b></th> - <th><b>Architectures</b></th> -</tr> -<tr><td colspan="5"><hr></td></tr> -<tr> - <td width="25%">Austria</td> - <td width="25%" align="center"><code>ftp.at.debian.org</code></td> - <td width="25%"><a href="http://ftp.at.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Australia</td> - <td width="25%" align="center"><code>ftp.au.debian.org</code></td> - <td width="25%"><a href="http://ftp.au.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Australia</td> - <td width="25%" align="center"><code>ftp.wa.au.debian.org</code></td> - <td width="25%"><a href="http://ftp.wa.au.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Bulgaria</td> - <td width="25%" align="center"><code>ftp.bg.debian.org</code></td> - <td width="25%"><a href="http://ftp.bg.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm i386 ia64 m68k mips mipsel powerpc sparc</td> -</tr> -<tr> - <td width="25%">Brazil</td> - <td width="25%" align="center"><code>ftp.br.debian.org</code></td> - <td width="25%"><a href="http://ftp.br.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Switzerland</td> - <td width="25%" align="center"><code>ftp.ch.debian.org</code></td> - <td width="25%"><a href="http://ftp.ch.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Chile</td> - <td width="25%" align="center"><code>ftp.cl.debian.org</code></td> - <td width="25%"><a href="http://ftp.cl.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Czech Republic</td> - <td width="25%" align="center"><code>ftp.cz.debian.org</code></td> - <td width="25%"><a href="http://ftp.cz.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Germany</td> - <td width="25%" align="center"><code>ftp.de.debian.org</code></td> - <td width="25%"><a href="http://ftp.de.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Germany</td> - <td width="25%" align="center"><code>ftp2.de.debian.org</code></td> - <td width="25%"><a href="http://ftp2.de.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Denmark</td> - <td width="25%" align="center"><code>ftp.dk.debian.org</code></td> - <td width="25%"><a href="http://ftp.dk.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Estonia</td> - <td width="25%" align="center"><code>ftp.ee.debian.org</code></td> - <td width="25%"><a href="http://ftp.ee.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Spain</td> - <td width="25%" align="center"><code>ftp.es.debian.org</code></td> - <td width="25%"><a href="http://ftp.es.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Finland</td> - <td width="25%" align="center"><code>ftp.fi.debian.org</code></td> - <td width="25%"><a href="http://ftp.fi.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">France</td> - <td width="25%" align="center"><code>ftp.fr.debian.org</code></td> - <td width="25%"><a href="http://ftp.fr.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">France</td> - <td width="25%" align="center"><code>ftp2.fr.debian.org</code></td> - <td width="25%"><a href="http://ftp2.fr.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Great Britain</td> - <td width="25%" align="center"><code>ftp.uk.debian.org</code></td> - <td width="25%"><a href="http://ftp.uk.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Hong Kong</td> - <td width="25%" align="center"><code>ftp.hk.debian.org</code></td> - <td width="25%"><a href="http://ftp.hk.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Croatia</td> - <td width="25%" align="center"><code>ftp.hr.debian.org</code></td> - <td width="25%"><a href="http://ftp.hr.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Hungary</td> - <td width="25%" align="center"><code>ftp.hu.debian.org</code></td> - <td width="25%"><a href="http://ftp.hu.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Ireland</td> - <td width="25%" align="center"><code>ftp.ie.debian.org</code></td> - <td width="25%"><a href="http://ftp.ie.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Iceland</td> - <td width="25%" align="center"><code>ftp.is.debian.org</code></td> - <td width="25%"><a href="http://ftp.is.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Italy</td> - <td width="25%" align="center"><code>ftp.it.debian.org</code></td> - <td width="25%"><a href="http://ftp.it.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Japan</td> - <td width="25%" align="center"><code>ftp.jp.debian.org</code></td> - <td width="25%"><a href="http://ftp.jp.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Japan</td> - <td width="25%" align="center"><code>ftp2.jp.debian.org</code></td> - <td width="25%"><a href="http://ftp2.jp.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Korea</td> - <td width="25%" align="center"><code>ftp.kr.debian.org</code></td> - <td width="25%"><a href="http://ftp.kr.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Mexico</td> - <td width="25%" align="center"><code>ftp.mx.debian.org</code></td> - <td width="25%"><a href="http://ftp.mx.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Netherlands</td> - <td width="25%" align="center"><code>ftp.nl.debian.org</code></td> - <td width="25%"><a href="http://ftp.nl.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Norway</td> - <td width="25%" align="center"><code>ftp.no.debian.org</code></td> - <td width="25%"><a href="http://ftp.no.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">New Zealand</td> - <td width="25%" align="center"><code>ftp.nz.debian.org</code></td> - <td width="25%"><a href="http://ftp.nz.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc</td> -</tr> -<tr> - <td width="25%">Poland</td> - <td width="25%" align="center"><code>ftp.pl.debian.org</code></td> - <td width="25%"><a href="http://ftp.pl.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Romania</td> - <td width="25%" align="center"><code>ftp.ro.debian.org</code></td> - <td width="25%"><a href="http://ftp.ro.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Russia</td> - <td width="25%" align="center"><code>ftp.ru.debian.org</code></td> - <td width="25%"><a href="http://ftp.ru.debian.org/debian/">/debian/</a></td> - <td width="25%">amd64 i386</td> -</tr> -<tr> - <td width="25%">Sweden</td> - <td width="25%" align="center"><code>ftp.se.debian.org</code></td> - <td width="25%"><a href="http://ftp.se.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Slovenia</td> - <td width="25%" align="center"><code>ftp.si.debian.org</code></td> - <td width="25%"><a href="http://ftp.si.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 i386 ia64 m68k powerpc sparc</td> -</tr> -<tr> - <td width="25%">Slovakia</td> - <td width="25%" align="center"><code>ftp.sk.debian.org</code></td> - <td width="25%"><a href="http://ftp.sk.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Turkey</td> - <td width="25%" align="center"><code>ftp.tr.debian.org</code></td> - <td width="25%"><a href="http://ftp.tr.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">Taiwan</td> - <td width="25%" align="center"><code>ftp.tw.debian.org</code></td> - <td width="25%"><a href="http://ftp.tw.debian.org/debian/">/debian/</a></td> - <td width="25%">alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc</td> -</tr> -<tr> - <td width="25%">United States</td> - <td width="25%" align="center"><code>ftp.us.debian.org</code></td> - <td width="25%"><a href="http://ftp.us.debian.org/debian/">/debian/</a></td> - <td width="25%">amd64 i386</td> -</tr> -</table> -<h2 align="center">Secondary mirrors of the Debian archive</h2> - - -<pre><small> -<strong>HOST NAME FTP HTTP ARCHITECTURES ---------- --- ---- ------------- -</strong> -<b>AR Argentina</b> ------------- -debian.logiclinux.com <a href="http://debian.logiclinux.com/debian/">/debian/</a> i386 -ftp.ccc.uba.ar <a href="ftp://ftp.ccc.uba.ar/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> <a href="http://ftp.ccc.uba.ar/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> amd64 i386 - -<b>AT Austria</b> ----------- -ftp.at.debian.org <a href="ftp://ftp.at.debian.org/debian/">/debian/</a> <a href="http://ftp.at.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -gd.tuwien.ac.at <a href="ftp://gd.tuwien.ac.at/opsys/linux/debian/">/opsys/linux/debian/</a> <a href="http://gd.tuwien.ac.at/opsys/linux/debian/">/opsys/linux/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.mur.at <a href="ftp://debian.mur.at/debian/">/debian/</a> <a href="http://debian.mur.at/debian/">/debian/</a> amd64 i386 ia64 -ftp.tu-graz.ac.at <a href="ftp://ftp.tu-graz.ac.at/mirror/debian/">/mirror/debian/</a> <a href="http://ftp.tu-graz.ac.at/mirror/debian/">/mirror/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.univie.ac.at <a href="ftp://ftp.univie.ac.at/systems/linux/debian/debian/">/systems/linux/debian/debian/</a> <a href="http://ftp.univie.ac.at/systems/linux/debian/debian/">/systems/linux/debian/debian/</a> i386 -debian.inode.at <a href="ftp://debian.inode.at/debian/">/debian/</a> <a href="http://debian.inode.at/debian/">/debian/</a> alpha amd64 arm i386 powerpc sparc - -<b>AU Australia</b> ------------- -ftp.wa.au.debian.org <a href="ftp://ftp.wa.au.debian.org/debian/">/debian/</a> <a href="http://ftp.wa.au.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.au.debian.org <a href="ftp://ftp.au.debian.org/debian/">/debian/</a> <a href="http://ftp.au.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.aarnet.edu.au <a href="ftp://mirror.aarnet.edu.au/debian/">/debian/</a> <a href="http://mirror.aarnet.edu.au/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.monash.edu.au <a href="ftp://ftp.monash.edu.au/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://ftp.monash.edu.au/pub/linux/debian/">/pub/linux/debian/</a> amd64 i386 -ftp.uwa.edu.au <a href="ftp://ftp.uwa.edu.au/debian/">/debian/</a> <a href="http://ftp.uwa.edu.au/debian/">/debian/</a> amd64 i386 -mirror.eftel.com <a href="ftp://mirror.eftel.com/debian/">/debian/</a> <a href="http://mirror.eftel.com/debian/">/debian/</a> amd64 i386 -mirror.pacific.net.au <a href="ftp://mirror.pacific.net.au/debian/">/debian/</a> <a href="http://mirror.pacific.net.au/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.iinet.net.au <a href="ftp://ftp.iinet.net.au/debian/debian/">/debian/debian/</a> <a href="http://ftp.iinet.net.au/debian/debian/">/debian/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.datafast.net.au <a href="ftp://mirror.datafast.net.au/debian/">/debian/</a> <a href="http://mirror.datafast.net.au/debian/">/debian/</a> amd64 i386 -mirror.optus.net <a href="ftp://mirror.optus.net/debian/">/debian/</a> <a href="http://mirror.optus.net/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>BE Belgium</b> ----------- -ftp.kulnet.kuleuven.ac.be <a href="ftp://ftp.kulnet.kuleuven.ac.be/debian/">/debian/</a> <a href="http://ftp.kulnet.kuleuven.ac.be/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.easynet.be <a href="ftp://ftp.easynet.be/debian/">/debian/</a> <a href="http://ftp.easynet.be/ftp/debian/">/ftp/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.belnet.be <a href="ftp://ftp.belnet.be/debian/">/debian/</a> <a href="http://ftp.belnet.be/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.debian.skynet.be <a href="ftp://ftp.debian.skynet.be/debian/">/debian/</a> <a href="http://ftp.debian.skynet.be/ftp/debian/">/ftp/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.scarlet.be <a href="ftp://ftp.scarlet.be/pub/debian/">/pub/debian/</a> <a href="http://ftp.scarlet.be/pub/debian/">/pub/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>BG Bulgaria</b> ------------ -ftp.bg.debian.org <a href="ftp://ftp.bg.debian.org/debian/">/debian/</a> <a href="http://ftp.bg.debian.org/debian/">/debian/</a> alpha amd64 arm i386 ia64 m68k mips mipsel powerpc sparc -debian.ludost.net <a href="ftp://debian.ludost.net/debian/">/debian/</a> <a href="http://debian.ludost.net/debian/">/debian/</a> i386 -ftp.uni-sofia.bg <a href="ftp://ftp.uni-sofia.bg/debian/">/debian/</a> <a href="http://ftp.uni-sofia.bg/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.telecoms.bg <a href="ftp://debian.telecoms.bg/debian/">/debian/</a> <a href="http://debian.telecoms.bg/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>BR Brazil</b> ---------- -ftp.br.debian.org <a href="ftp://ftp.br.debian.org/debian/">/debian/</a> <a href="http://ftp.br.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -sft.if.usp.br <a href="http://sft.if.usp.br/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -linorg.usp.br <a href="ftp://linorg.usp.br/debian/">/debian/</a> <a href="http://linorg.usp.br/debian/">/debian/</a> i386 -linux.iq.usp.br <a href="http://linux.iq.usp.br/debian/">/debian/</a> amd64 i386 -ftp.pucpr.br <a href="ftp://ftp.pucpr.br/debian/">/debian/</a> amd64 hurd-i386 i386 -www.las.ic.unicamp.br <a href="ftp://www.las.ic.unicamp.br/pub/debian/">/pub/debian/</a> <a href="http://www.las.ic.unicamp.br/pub/debian/">/pub/debian/</a> amd64 hurd-i386 i386 powerpc sparc -debian.pop-sc.rnp.br <a href="http://debian.pop-sc.rnp.br/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>BY Belarus</b> ----------- -linux.org.by <a href="ftp://linux.org.by/debian/">/debian/</a> <a href="http://linux.org.by/debian/">/debian/</a> amd64 i386 -ftp.mgts.by <a href="ftp://ftp.mgts.by/debian/">/debian/</a> <a href="http://ftp.mgts.by/debian/">/debian/</a> amd64 i386 - -<b>CA Canada</b> ---------- -debian.yorku.ca <a href="http://debian.yorku.ca/debian/">/debian/</a> amd64 i386 -ftp3.nrc.ca <a href="ftp://ftp3.nrc.ca/debian/">/debian/</a> <a href="http://ftp3.nrc.ca/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -gulus.usherbrooke.ca <a href="ftp://gulus.usherbrooke.ca/debian/">/debian/</a> <a href="http://gulus.usherbrooke.ca/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.cpsc.ucalgary.ca <a href="ftp://mirror.cpsc.ucalgary.ca/debian/">/debian/</a> <a href="http://mirror.cpsc.ucalgary.ca/debian/">/debian/</a> amd64 i386 -mirror.peer1.net <a href="http://mirror.peer1.net/debian/">/debian/</a> alpha amd64 arm i386 mips mipsel powerpc sparc -debian.mirror.rafal.ca <a href="ftp://debian.mirror.rafal.ca/debian/">/debian/</a> <a href="http://debian.mirror.rafal.ca/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.savoirfairelinux.net <a href="ftp://debian.savoirfairelinux.net/debian/">/debian/</a> <a href="http://debian.savoirfairelinux.net/debian/">/debian/</a> amd64 i386 powerpc -debian.mirror.iweb.ca <a href="ftp://debian.mirror.iweb.ca/debian/">/debian/</a> <a href="http://debian.mirror.iweb.ca/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>CH Switzerland</b> --------------- -ftp.ch.debian.org <a href="ftp://ftp.ch.debian.org/debian/">/debian/</a> <a href="http://ftp.ch.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.switch.ch <a href="ftp://mirror.switch.ch/mirror/debian/">/mirror/debian/</a> <a href="http://mirror.switch.ch/ftp/mirror/debian/">/ftp/mirror/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>CL Chile</b> --------- -ftp.cl.debian.org <a href="ftp://ftp.cl.debian.org/debian/">/debian/</a> <a href="http://ftp.cl.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.ubiobio.cl <a href="http://debian.ubiobio.cl/debian/">/debian/</a> amd64 i386 powerpc sparc - -<b>CN China</b> --------- -ftp.linuxforum.net <a href="ftp://ftp.linuxforum.net/debian/">/debian/</a> i386 -mirrors.geekbone.org <a href="ftp://mirrors.geekbone.org/debian/">/debian/</a> <a href="http://mirrors.geekbone.org/debian/">/debian/</a> alpha amd64 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.cn99.com <a href="ftp://debian.cn99.com/debian/">/debian/</a> <a href="http://debian.cn99.com/debian/">/debian/</a> amd64 i386 - -<b>CZ Czech Republic</b> ------------------ -ftp.cz.debian.org <a href="ftp://ftp.cz.debian.org/debian/">/debian/</a> <a href="http://ftp.cz.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.sh.cvut.cz <a href="ftp://debian.sh.cvut.cz/debian/">/debian/</a> <a href="http://debian.sh.cvut.cz/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.zcu.cz <a href="ftp://ftp.zcu.cz/mirrors/debian/">/mirrors/debian/</a> <a href="http://ftp.zcu.cz/mirrors/debian/">/mirrors/debian/</a> amd64 i386 -debian.mirror.web4u.cz <a href="ftp://debian.mirror.web4u.cz/">/</a> <a href="http://debian.mirror.web4u.cz/">/</a> amd64 i386 - -<b>DE Germany</b> ----------- -ftp.de.debian.org <a href="ftp://ftp.de.debian.org/debian/">/debian/</a> <a href="http://ftp.de.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp2.de.debian.org <a href="ftp://ftp2.de.debian.org/debian/">/debian/</a> <a href="http://ftp2.de.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.tu-clausthal.de <a href="ftp://ftp.tu-clausthal.de/pub/linux/debian/">/pub/linux/debian/</a> amd64 arm i386 ia64 m68k mips powerpc sparc -debian.uni-essen.de <a href="ftp://debian.uni-essen.de/debian/">/debian/</a> <a href="http://debian.uni-essen.de/debian/">/debian/</a> amd64 hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc -ftp.freenet.de <a href="ftp://ftp.freenet.de/pub/ftp.debian.org/debian/">/pub/ftp.debian.org/debian/</a> <a href="http://ftp.freenet.de/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -sunsite.informatik.rwth-aachen.de <a href="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/debian/">/pub/Linux/debian/</a> <a href="http://sunsite.informatik.rwth-aachen.de/ftp/pub/Linux/debian/">/ftp/pub/Linux/debian/</a> alpha amd64 i386 powerpc sparc -ftp-stud.fht-esslingen.de <a href="ftp://ftp-stud.fht-esslingen.de/debian/">/debian/</a> <a href="http://ftp-stud.fht-esslingen.de/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.stw-bonn.de <a href="ftp://ftp.stw-bonn.de/debian/">/debian/</a> <a href="http://ftp.stw-bonn.de/debian/">/debian/</a> amd64 i386 -ftp.fu-berlin.de <a href="ftp://ftp.fu-berlin.de/pub/unix/linux/mirrors/debian/">/pub/unix/linux/mirrors/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.tu-bs.de <a href="ftp://debian.tu-bs.de/debian/">/debian/</a> <a href="http://debian.tu-bs.de/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.uni-koeln.de <a href="ftp://ftp.uni-koeln.de/debian/">/debian/</a> <a href="http://ftp.uni-koeln.de/debian/">/debian/</a> alpha amd64 i386 powerpc sparc -debian.pffa.de <a href="ftp://debian.pffa.de/pub/mirrors/debian/">/pub/mirrors/debian/</a> <a href="http://debian.pffa.de/mirrors/debian/">/mirrors/debian/</a> i386 -ftp.mpi-sb.mpg.de <a href="ftp://ftp.mpi-sb.mpg.de/pub/linux/distributions/debian/debian/">/pub/linux/distributions/debian/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.tiscali.de <a href="ftp://ftp.tiscali.de/pub/debian/debian/">/pub/debian/debian/</a> <a href="http://ftp.tiscali.de/pub/debian/debian/">/pub/debian/debian/</a> amd64 arm hurd-i386 i386 ia64 -ftp.tu-chemnitz.de <a href="ftp://ftp.tu-chemnitz.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> <a href="http://ftp.tu-chemnitz.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.uni-kl.de <a href="ftp://ftp.uni-kl.de/debian/">/debian/</a> <a href="http://ftp.uni-kl.de/debian/">/debian/</a> amd64 i386 ia64 powerpc sparc -ftp.uni-bayreuth.de <a href="ftp://ftp.uni-bayreuth.de/pub/linux/Debian/debian/">/pub/linux/Debian/debian/</a> <a href="http://ftp.uni-bayreuth.de/linux/Debian/debian/">/linux/Debian/debian/</a> alpha amd64 hurd-i386 i386 ia64 -ftp.informatik.hu-berlin.de <a href="ftp://ftp.informatik.hu-berlin.de/pub/Mirrors/ftp.de.debian.org/debian/">/pub/Mirrors/ftp.de.debian.org/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.gwdg.de <a href="ftp://ftp.gwdg.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> <a href="http://ftp.gwdg.de/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> amd64 hurd-i386 i386 -ftp.hosteurope.de <a href="ftp://ftp.hosteurope.de/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://ftp.hosteurope.de/pub/linux/debian/">/pub/linux/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.netcologne.de <a href="ftp://debian.netcologne.de/debian/">/debian/</a> <a href="http://debian.netcologne.de/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -artfiles.org <a href="ftp://artfiles.org/debian/">/debian/</a> <a href="http://artfiles.org/debian/">/debian/</a> amd64 i386 -debian.intergenia.de <a href="http://debian.intergenia.de/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.swordcoast.net <a href="ftp://debian.swordcoast.net/debian/">/debian/</a> <a href="http://debian.swordcoast.net/debian/">/debian/</a> alpha amd64 arm hurd-i386 i386 ia64 m68k powerpc -debian.cruisix.net <a href="ftp://debian.cruisix.net/debian/">/debian/</a> <a href="http://debian.cruisix.net/debian/">/debian/</a> amd64 i386 powerpc -ftp.rrzn.uni-hannover.de <a href="ftp://ftp.rrzn.uni-hannover.de/debian/debian/">/debian/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian-ftp.charite.de <a href="http://debian-ftp.charite.de/debian/">/debian/</a> i386 - -<b>DK Denmark</b> ----------- -ftp.dk.debian.org <a href="ftp://ftp.dk.debian.org/debian/">/debian/</a> <a href="http://ftp.dk.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.dkuug.dk <a href="ftp://ftp.dkuug.dk/pub/debian/">/pub/debian/</a> <a href="http://ftp.dkuug.dk/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.here.dk <a href="http://mirror.here.dk/debian/">/debian/</a> amd64 i386 ia64 mips powerpc -debian.uni-c.dk <a href="http://debian.uni-c.dk/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirrors.telianet.dk <a href="ftp://mirrors.telianet.dk/debian/">/debian/</a> <a href="http://mirrors.telianet.dk/debian/">/debian/</a> amd64 i386 powerpc sparc - -<b>EE Estonia</b> ----------- -ftp.ee.debian.org <a href="ftp://ftp.ee.debian.org/debian/">/debian/</a> <a href="http://ftp.ee.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>ES Spain</b> --------- -ftp.es.debian.org <a href="ftp://ftp.es.debian.org/debian/">/debian/</a> <a href="http://ftp.es.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.rediris.es <a href="ftp://ftp.rediris.es/debian/">/debian/</a> <a href="http://ftp.rediris.es/debian/">/debian/</a> alpha amd64 i386 ia64 powerpc sparc -ftp.cica.es <a href="ftp://ftp.cica.es/debian/">/debian/</a> <a href="http://ftp.cica.es/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.caliu.info <a href="ftp://ftp.caliu.info/debian/">/debian/</a> <a href="http://ftp.caliu.info/debian/">/debian/</a> i386 ia64 m68k mips mipsel powerpc sparc -ftp.gva.es <a href="ftp://ftp.gva.es/pub/mirror/debian/">/pub/mirror/debian/</a> <a href="http://ftp.gva.es/mirror/debian/">/mirror/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.gul.uc3m.es <a href="ftp://ftp.gul.uc3m.es/debian/">/debian/</a> <a href="http://ftp.gul.uc3m.es/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.um.es <a href="ftp://ftp.um.es/mirror/debian/">/mirror/debian/</a> all -jane.uab.cat <a href="ftp://jane.uab.cat/debian/">/debian/</a> <a href="http://jane.uab.cat/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>FI Finland</b> ----------- -ftp.fi.debian.org <a href="ftp://ftp.fi.debian.org/debian/">/debian/</a> <a href="http://ftp.fi.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.funet.fi <a href="ftp://ftp.funet.fi/pub/linux/mirrors/debian/">/pub/linux/mirrors/debian/</a> <a href="http://ftp.funet.fi/pub/linux/mirrors/debian/">/pub/linux/mirrors/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.jyu.fi <a href="ftp://ftp.jyu.fi/debian/">/debian/</a> <a href="http://ftp.jyu.fi/debian/">/debian/</a> alpha amd64 hurd-i386 i386 powerpc sparc - -<b>FR France</b> ---------- -ftp.fr.debian.org <a href="ftp://ftp.fr.debian.org/debian/">/debian/</a> <a href="http://ftp.fr.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp2.fr.debian.org <a href="ftp://ftp2.fr.debian.org/debian/">/debian/</a> <a href="http://ftp2.fr.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.iut-bm.univ-fcomte.fr <a href="ftp://ftp.iut-bm.univ-fcomte.fr/debian/">/debian/</a> <a href="http://ftp.iut-bm.univ-fcomte.fr/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.proxad.net <a href="ftp://ftp.proxad.net/mirrors/ftp.debian.org/">/mirrors/ftp.debian.org/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.lip6.fr <a href="ftp://ftp.lip6.fr/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a> <a href="http://ftp.lip6.fr/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a> amd64 i386 -debian.ens-cachan.fr <a href="ftp://debian.ens-cachan.fr/debian/">/debian/</a> <a href="http://debian.ens-cachan.fr/ftp/debian/">/ftp/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.u-picardie.fr <a href="ftp://ftp.u-picardie.fr/mirror/debian/">/mirror/debian/</a> <a href="http://ftp.u-picardie.fr/mirror/debian/">/mirror/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.mirrors.easynet.fr <a href="ftp://debian.mirrors.easynet.fr/debian/">/debian/</a> <a href="http://debian.mirrors.easynet.fr/">/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.u-strasbg.fr <a href="ftp://ftp.u-strasbg.fr/debian/">/debian/</a> <a href="http://ftp.u-strasbg.fr/debian/">/debian/</a> alpha amd64 hurd-i386 i386 ia64 m68k powerpc sparc -debian.ibisc.univ-evry.fr <a href="ftp://debian.ibisc.univ-evry.fr/debian/">/debian/</a> <a href="http://debian.ibisc.univ-evry.fr/debian/">/debian/</a> amd64 i386 -mir1.ovh.net <a href="ftp://mir1.ovh.net/debian/">/debian/</a> <a href="http://mir1.ovh.net/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mir2.ovh.net <a href="http://mir2.ovh.net/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.nerim.net <a href="ftp://ftp.nerim.net/debian/">/debian/</a> <a href="http://ftp.nerim.net/debian/">/debian/</a> i386 -ftp.crihan.fr <a href="ftp://ftp.crihan.fr/debian/">/debian/</a> <a href="http://ftp.crihan.fr/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.mines.inpl-nancy.fr <a href="ftp://debian.mines.inpl-nancy.fr/debian/">/debian/</a> <a href="http://debian.mines.inpl-nancy.fr/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.debian.ikoula.com <a href="ftp://ftp.debian.ikoula.com/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -webb.ens-cachan.fr <a href="ftp://webb.ens-cachan.fr/debian/">/debian/</a> <a href="http://webb.ens-cachan.fr/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirrors.ircam.fr <a href="ftp://mirrors.ircam.fr/pub/debian/">/pub/debian/</a> <a href="http://mirrors.ircam.fr/pub/debian/">/pub/debian/</a> alpha amd64 hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc -debian.mirror.inra.fr <a href="ftp://debian.mirror.inra.fr/debian/">/debian/</a> <a href="http://debian.mirror.inra.fr/debian/">/debian/</a> amd64 arm i386 ia64 powerpc sparc - -<b>GB Great Britain</b> ----------------- -ftp.uk.debian.org <a href="ftp://ftp.uk.debian.org/debian/">/debian/</a> <a href="http://ftp.uk.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.mcc.ac.uk <a href="ftp://ftp.mcc.ac.uk/pub/linux/distributions/Debian/">/pub/linux/distributions/Debian/</a> hurd-i386 i386 sh -www.mirrorservice.org <a href="ftp://www.mirrorservice.org/sites/ftp.debian.org/debian/">/sites/ftp.debian.org/debian/</a> <a href="http://www.mirrorservice.org/sites/ftp.debian.org/debian/">/sites/ftp.debian.org/debian/</a> amd64 i386 -download.mirror.ac.uk <a href="ftp://download.mirror.ac.uk/sites/ftp.debian.org/debian/">/sites/ftp.debian.org/debian/</a> <a href="http://download.mirror.ac.uk/sites/ftp.debian.org/debian/">/sites/ftp.debian.org/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.ticklers.org <a href="ftp://ftp.ticklers.org/debian/">/debian/</a> <a href="http://ftp.ticklers.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.blueyonder.co.uk <a href="ftp://debian.blueyonder.co.uk/pub/debian/">/pub/debian/</a> <a href="http://debian.blueyonder.co.uk/">/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.positive-internet.com <a href="ftp://mirror.positive-internet.com/debian/">/debian/</a> <a href="http://mirror.positive-internet.com/debian/">/debian/</a> amd64 hppa i386 ia64 powerpc -the.earth.li <a href="ftp://the.earth.li/debian/">/debian/</a> <a href="http://the.earth.li/debian/">/debian/</a> amd64 hurd-i386 i386 -mirror.ox.ac.uk <a href="ftp://mirror.ox.ac.uk/debian/">/debian/</a> <a href="http://mirror.ox.ac.uk/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>GR Greece</b> ---------- -debian.otenet.gr <a href="ftp://debian.otenet.gr/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://debian.otenet.gr/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.ntua.gr <a href="ftp://ftp.ntua.gr/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://ftp.ntua.gr/pub/linux/debian/">/pub/linux/debian/</a> amd64 i386 sparc -ftp.duth.gr <a href="ftp://ftp.duth.gr/debian/">/debian/</a> <a href="http://ftp.duth.gr/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.softnet.tuc.gr <a href="ftp://ftp.softnet.tuc.gr/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://ftp.softnet.tuc.gr/ftp/linux/debian/">/ftp/linux/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.internet.gr <a href="ftp://debian.internet.gr/debian/">/debian/</a> <a href="http://debian.internet.gr/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>HK Hong Kong</b> ------------- -ftp.hk.debian.org <a href="ftp://ftp.hk.debian.org/debian/">/debian/</a> <a href="http://ftp.hk.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -www.zentek-international.com <a href="http://www.zentek-international.com/mirrors/debian/">/mirrors/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>HR Croatia</b> ----------- -ftp.hr.debian.org <a href="ftp://ftp.hr.debian.org/debian/">/debian/</a> <a href="http://ftp.hr.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.irb.hr <a href="ftp://ftp.irb.hr/debian/">/debian/</a> <a href="http://ftp.irb.hr/debian/">/debian/</a> amd64 arm hurd-i386 i386 ia64 powerpc sparc -ftp.carnet.hr <a href="ftp://ftp.carnet.hr/debian/">/debian/</a> <a href="http://ftp.carnet.hr/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.iskon.hr <a href="ftp://debian.iskon.hr/debian/">/debian/</a> <a href="http://debian.iskon.hr/debian/">/debian/</a> amd64 hurd-i386 i386 ia64 s390 - -<b>HU Hungary</b> ----------- -ftp.hu.debian.org <a href="ftp://ftp.hu.debian.org/debian/">/debian/</a> <a href="http://ftp.hu.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.bme.hu <a href="ftp://ftp.bme.hu/OS/Linux/dist/debian/">/OS/Linux/dist/debian/</a> <a href="http://ftp.bme.hu/OS/Linux/dist/debian/">/OS/Linux/dist/debian/</a> amd64 hurd-i386 i386 ia64 - -<b>ID Indonesia</b> ------------- -kebo.vlsm.org <a href="ftp://kebo.vlsm.org/debian/">/debian/</a> <a href="http://kebo.vlsm.org/debian/">/debian/</a> amd64 hurd-i386 i386 powerpc -debian.indika.net.id <a href="http://debian.indika.net.id/debian/">/debian/</a> i386 - -<b>IE Ireland</b> ----------- -ftp.ie.debian.org <a href="ftp://ftp.ie.debian.org/debian/">/debian/</a> <a href="http://ftp.ie.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.esat.net <a href="ftp://ftp.esat.net/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://ftp.esat.net/pub/linux/debian/">/pub/linux/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>IL Israel</b> ---------- -mirror.hamakor.org.il <a href="http://mirror.hamakor.org.il/pub/mirrors/debian/">/pub/mirrors/debian/</a> amd64 i386 -debian.co.il <a href="http://debian.co.il/debian/">/debian/</a> amd64 i386 - -<b>IS Iceland</b> ----------- -ftp.is.debian.org <a href="ftp://ftp.is.debian.org/debian/">/debian/</a> <a href="http://ftp.is.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>IT Italy</b> --------- -ftp.it.debian.org <a href="ftp://ftp.it.debian.org/debian/">/debian/</a> <a href="http://ftp.it.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.bononia.it <a href="ftp://ftp.bononia.it/debian/">/debian/</a> <a href="http://ftp.bononia.it/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -freedom.dicea.unifi.it <a href="ftp://freedom.dicea.unifi.it/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://freedom.dicea.unifi.it/ftp/pub/linux/debian/">/ftp/pub/linux/debian/</a> amd64 hurd-i386 i386 -ftp.eutelia.it <a href="ftp://ftp.eutelia.it/pub/Debian_Mirror/">/pub/Debian_Mirror/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mi.mirror.garr.it <a href="ftp://mi.mirror.garr.it/mirrors/debian/">/mirrors/debian/</a> <a href="http://mi.mirror.garr.it/mirrors/debian/">/mirrors/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.fastweb.it <a href="ftp://debian.fastweb.it/debian/">/debian/</a> <a href="http://debian.fastweb.it/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.unina.it <a href="ftp://ftp.unina.it/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a> <a href="http://ftp.unina.it/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.fastbull.org <a href="ftp://debian.fastbull.org/debian/">/debian/</a> <a href="http://debian.fastbull.org/debian/">/debian/</a> amd64 i386 powerpc sparc - -<b>JP Japan</b> --------- -ftp.jp.debian.org <a href="ftp://ftp.jp.debian.org/debian/">/debian/</a> <a href="http://ftp.jp.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp2.jp.debian.org <a href="ftp://ftp2.jp.debian.org/debian/">/debian/</a> <a href="http://ftp2.jp.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ring.asahi-net.or.jp <a href="ftp://ring.asahi-net.or.jp/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> <a href="http://ring.asahi-net.or.jp/archives/linux/debian/debian/">/archives/linux/debian/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.dti.ad.jp <a href="ftp://ftp.dti.ad.jp/pub/Linux/debian/">/pub/Linux/debian/</a> <a href="http://ftp.dti.ad.jp/pub/Linux/debian/">/pub/Linux/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -dennou-k.gfd-dennou.org <a href="ftp://dennou-k.gfd-dennou.org/library/Linux/debian/">/library/Linux/debian/</a> <a href="http://dennou-k.gfd-dennou.org/library/Linux/debian/">/library/Linux/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -dennou-q.gfd-dennou.org <a href="ftp://dennou-q.gfd-dennou.org/library/Linux/debian/">/library/Linux/debian/</a> <a href="http://dennou-q.gfd-dennou.org/library/Linux/debian/">/library/Linux/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.yz.yamagata-u.ac.jp <a href="ftp://ftp.yz.yamagata-u.ac.jp/debian/">/debian/</a> <a href="http://ftp.yz.yamagata-u.ac.jp/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -sb.itc.u-tokyo.ac.jp <a href="ftp://sb.itc.u-tokyo.ac.jp/DEBIAN/">/DEBIAN/</a> <a href="http://sb.itc.u-tokyo.ac.jp/DEBIAN/">/DEBIAN/</a> amd64 hurd-i386 i386 powerpc -ftp.riken.jp <a href="ftp://ftp.riken.jp/pub/Linux/debian/debian/">/pub/Linux/debian/debian/</a> <a href="http://ftp.riken.jp/pub/Linux/debian/debian/">/pub/Linux/debian/debian/</a> amd64 i386 -debian.shimpinomori.net <a href="http://debian.shimpinomori.net/debian/">/debian/</a> amd64 i386 powerpc -www.ring.gr.jp <a href="ftp://www.ring.gr.jp/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> <a href="http://www.ring.gr.jp/archives/linux/debian/debian/">/archives/linux/debian/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.jaist.ac.jp <a href="ftp://ftp.jaist.ac.jp/pub/Linux/Debian/">/pub/Linux/Debian/</a> <a href="http://ftp.jaist.ac.jp/pub/Linux/Debian/">/pub/Linux/Debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>KR Korea</b> --------- -ftp.kr.debian.org <a href="ftp://ftp.kr.debian.org/debian/">/debian/</a> <a href="http://ftp.kr.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>LT Lithuania</b> ------------- -ameba.sc-uni.ktu.lt <a href="ftp://ameba.sc-uni.ktu.lt/debian/">/debian/</a> <a href="http://ameba.sc-uni.ktu.lt/debian/">/debian/</a> i386 -debian.balt.net <a href="ftp://debian.balt.net/debian/">/debian/</a> <a href="http://debian.balt.net/debian/">/debian/</a> amd64 arm i386 sparc - -<b>MX Mexico</b> ---------- -ftp.mx.debian.org <a href="ftp://ftp.mx.debian.org/debian/">/debian/</a> <a href="http://ftp.mx.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mmc.igeofcu.unam.mx <a href="http://mmc.igeofcu.unam.mx/debian/">/debian/</a> amd64 hurd-i386 i386 ia64 - -<b>NI Nicaragua</b> ------------- -debian.uni.edu.ni <a href="http://debian.uni.edu.ni/debian/">/debian/</a> amd64 hurd-i386 i386 - -<b>NL Netherlands</b> --------------- -ftp.nl.debian.org <a href="ftp://ftp.nl.debian.org/debian/">/debian/</a> <a href="http://ftp.nl.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.nluug.nl <a href="ftp://ftp.nluug.nl/pub/os/Linux/distr/debian/">/pub/os/Linux/distr/debian/</a> <a href="http://ftp.nluug.nl/pub/os/Linux/distr/debian/">/pub/os/Linux/distr/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.surfnet.nl <a href="ftp://ftp.surfnet.nl/pub/os/Linux/distr/debian/">/pub/os/Linux/distr/debian/</a> <a href="http://ftp.surfnet.nl/os/Linux/distr/debian/">/os/Linux/distr/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.debian.nl <a href="ftp://ftp.debian.nl/debian/">/debian/</a> <a href="http://ftp.debian.nl/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.tiscali.nl <a href="ftp://ftp.tiscali.nl/pub/mirrors/debian/">/pub/mirrors/debian/</a> <a href="http://ftp.tiscali.nl/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.essentkabel.com <a href="ftp://debian.essentkabel.com/debian/">/debian/</a> <a href="http://debian.essentkabel.com/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.scarlet-internet.nl <a href="ftp://mirror.scarlet-internet.nl/pub/debian/">/pub/debian/</a> <a href="http://mirror.scarlet-internet.nl/pub/debian/">/pub/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>NO Norway</b> ---------- -ftp.no.debian.org <a href="ftp://ftp.no.debian.org/debian/">/debian/</a> <a href="http://ftp.no.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 powerpc s390 sparc - -<b>NZ New Zealand</b> --------------- -ftp.nz.debian.org <a href="ftp://ftp.nz.debian.org/debian/">/debian/</a> <a href="http://ftp.nz.debian.org/debian/">/debian/</a> alpha amd64 arm hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc -debian.ihug.co.nz <a href="ftp://debian.ihug.co.nz/debian/">/debian/</a> <a href="http://debian.ihug.co.nz/debian/">/debian/</a> amd64 i386 - -<b>PL Poland</b> ---------- -ftp.pl.debian.org <a href="ftp://ftp.pl.debian.org/debian/">/debian/</a> <a href="http://ftp.pl.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.icm.edu.pl <a href="ftp://ftp.icm.edu.pl/pub/Linux/debian/">/pub/Linux/debian/</a> <a href="http://ftp.icm.edu.pl/pub/Linux/debian/">/pub/Linux/debian/</a> alpha amd64 hurd-i386 i386 sparc -ftp.man.szczecin.pl <a href="ftp://ftp.man.szczecin.pl/pub/Linux/debian/">/pub/Linux/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.vectranet.pl <a href="ftp://ftp.vectranet.pl/debian/">/debian/</a> <a href="http://ftp.vectranet.pl/debian/">/debian/</a> amd64 i386 - -<b>PT Portugal</b> ------------ -ftp.uevora.pt <a href="ftp://ftp.uevora.pt/debian/">/debian/</a> <a href="http://ftp.uevora.pt/debian/">/debian/</a> amd64 i386 -ftp.eq.uc.pt <a href="ftp://ftp.eq.uc.pt/pub/software/Linux/debian/">/pub/software/Linux/debian/</a> <a href="http://ftp.eq.uc.pt/software/Linux/debian/">/software/Linux/debian/</a> amd64 i386 -debian.ua.pt <a href="ftp://debian.ua.pt/debian/">/debian/</a> <a href="http://debian.ua.pt/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.linux.pt <a href="ftp://ftp.linux.pt/pub/mirrors/debian/">/pub/mirrors/debian/</a> <a href="http://ftp.linux.pt/pub/mirrors/debian/">/pub/mirrors/debian/</a> amd64 hurd-i386 i386 -ftp.telepac.pt <a href="ftp://ftp.telepac.pt/pub/debian/">/pub/debian/</a> all - -<b>RO Romania</b> ----------- -ftp.ro.debian.org <a href="ftp://ftp.ro.debian.org/debian/">/debian/</a> <a href="http://ftp.ro.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.lug.ro <a href="ftp://ftp.lug.ro/debian/">/debian/</a> <a href="http://ftp.lug.ro/debian/">/debian/</a> amd64 i386 powerpc - -<b>RU Russia</b> ---------- -ftp.ru.debian.org <a href="ftp://ftp.ru.debian.org/debian/">/debian/</a> <a href="http://ftp.ru.debian.org/debian/">/debian/</a> amd64 i386 -debian.nsu.ru <a href="ftp://debian.nsu.ru/debian/">/debian/</a> <a href="http://debian.nsu.ru/debian/">/debian/</a> amd64 i386 -debian.udsu.ru <a href="ftp://debian.udsu.ru/debian/">/debian/</a> <a href="http://debian.udsu.ru/debian/">/debian/</a> amd64 i386 -ftp.psn.ru <a href="ftp://ftp.psn.ru/debian/">/debian/</a> <a href="http://ftp.psn.ru/debian/">/debian/</a> alpha amd64 hurd-i386 i386 -ftp.corbina.ru <a href="ftp://ftp.corbina.ru/pub/Linux/debian/">/pub/Linux/debian/</a> amd64 i386 ia64 -ftp.mipt.ru <a href="ftp://ftp.mipt.ru/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>SE Sweden</b> ---------- -ftp.se.debian.org <a href="ftp://ftp.se.debian.org/debian/">/debian/</a> <a href="http://ftp.se.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.sunet.se <a href="ftp://ftp.sunet.se/pub/os/Linux/distributions/debian/">/pub/os/Linux/distributions/debian/</a> <a href="http://ftp.sunet.se/pub/os/Linux/distributions/debian/">/pub/os/Linux/distributions/debian/</a>alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.port80.se <a href="ftp://ftp.port80.se/debian/">/debian/</a> <a href="http://ftp.port80.se/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.ds.hj.se <a href="ftp://ftp.ds.hj.se/pub/os/linux/debian/">/pub/os/linux/debian/</a> <a href="http://ftp.ds.hj.se/pub/os/linux/debian/">/pub/os/linux/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.bsnet.se <a href="ftp://debian.bsnet.se/debian/">/debian/</a> i386 - -<b>SG Singapore</b> ------------- -mirror.nus.edu.sg <a href="ftp://mirror.nus.edu.sg/pub/Debian/">/pub/Debian/</a> <a href="http://mirror.nus.edu.sg/Debian/">/Debian/</a> amd64 i386 -debian.wow-vision.com.sg <a href="ftp://debian.wow-vision.com.sg/debian/">/debian/</a> <a href="http://debian.wow-vision.com.sg/debian/">/debian/</a> amd64 i386 - -<b>SI Slovenia</b> ------------ -ftp.si.debian.org <a href="ftp://ftp.si.debian.org/debian/">/debian/</a> <a href="http://ftp.si.debian.org/debian/">/debian/</a> alpha amd64 i386 ia64 m68k powerpc sparc -ftp.arnes.si <a href="ftp://ftp.arnes.si/packages/debian/">/packages/debian/</a> amd64 hurd-i386 i386 - -<b>SK Slovakia</b> ------------ -ftp.sk.debian.org <a href="ftp://ftp.sk.debian.org/debian/">/debian/</a> <a href="http://ftp.sk.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>TH Thailand</b> ------------ -ftp.coe.psu.ac.th <a href="ftp://ftp.coe.psu.ac.th/debian/">/debian/</a> <a href="http://ftp.coe.psu.ac.th/debian/">/debian/</a> i386 -ftp.thaios.net <a href="http://ftp.thaios.net/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>TR Turkey</b> ---------- -ftp.tr.debian.org <a href="ftp://ftp.tr.debian.org/debian/">/debian/</a> <a href="http://ftp.tr.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -godel.cs.bilgi.edu.tr <a href="http://godel.cs.bilgi.edu.tr/debian/">/debian/</a> hurd-i386 i386 - -<b>TW Taiwan</b> ---------- -ftp.tw.debian.org <a href="ftp://ftp.tw.debian.org/debian/">/debian/</a> <a href="http://ftp.tw.debian.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.csie.ntu.edu.tw <a href="ftp://debian.csie.ntu.edu.tw/pub/debian/">/pub/debian/</a> <a href="http://debian.csie.ntu.edu.tw/debian/">/debian/</a> amd64 hurd-i386 i386 -linux.cdpa.nsysu.edu.tw <a href="http://linux.cdpa.nsysu.edu.tw/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -opensource.nchc.org.tw <a href="ftp://opensource.nchc.org.tw/debian/">/debian/</a> <a href="http://opensource.nchc.org.tw/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.nctu.edu.tw <a href="ftp://debian.nctu.edu.tw/debian/">/debian/</a> <a href="http://debian.nctu.edu.tw/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.nttu.edu.tw <a href="ftp://mirror.nttu.edu.tw/debian/">/debian/</a> <a href="http://mirror.nttu.edu.tw/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.csie.nctu.edu.tw <a href="ftp://debian.csie.nctu.edu.tw/debian/">/debian/</a> <a href="http://debian.csie.nctu.edu.tw/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>UA Ukraine</b> ----------- -debian.osdn.org.ua <a href="ftp://debian.osdn.org.ua/pub/Debian/debian/">/pub/Debian/debian/</a> <a href="http://debian.osdn.org.ua/debian/">/debian/</a> i386 -debian.org.ua <a href="ftp://debian.org.ua/debian/">/debian/</a> <a href="http://debian.org.ua/debian/">/debian/</a> i386 -ftp.3logic.net <a href="ftp://ftp.3logic.net/debian/">/debian/</a> i386 - -<b>US United States</b> ----------------- -ftp.us.debian.org <a href="ftp://ftp.us.debian.org/debian/">/debian/</a> <a href="http://ftp.us.debian.org/debian/">/debian/</a> amd64 i386 -ftp.debian.org <a href="ftp://ftp.debian.org/debian/">/debian/</a> <a href="http://ftp.debian.org/debian/">/debian/</a> amd64 i386 -ftp.gtlib.gatech.edu <a href="ftp://ftp.gtlib.gatech.edu/pub/debian/">/pub/debian/</a> <a href="http://ftp.gtlib.gatech.edu/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.egr.msu.edu <a href="ftp://ftp.egr.msu.edu/debian/">/debian/</a> <a href="http://ftp.egr.msu.edu/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -distro.ibiblio.org <a href="ftp://distro.ibiblio.org/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a> <a href="http://distro.ibiblio.org/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a> amd64 hurd-i386 i386 powerpc -ftp-mirror.internap.com <a href="ftp://ftp-mirror.internap.com/pub/debian/">/pub/debian/</a> <a href="http://ftp-mirror.internap.com/pub/debian/">/pub/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.cerias.purdue.edu <a href="ftp://ftp.cerias.purdue.edu/pub/os/debian/">/pub/os/debian/</a> <a href="http://ftp.cerias.purdue.edu/pub/os/debian/">/pub/os/debian/</a> amd64 i386 -ftp.cs.unm.edu <a href="ftp://ftp.cs.unm.edu/mirrors/debian/">/mirrors/debian/</a> alpha arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.cs.wisc.edu <a href="ftp://mirror.cs.wisc.edu/pub/mirrors/linux/debian/">/pub/mirrors/linux/debian/</a> <a href="http://mirror.cs.wisc.edu/pub/mirrors/linux/debian/">/pub/mirrors/linux/debian/</a> amd64 i386 -ftp.uwsg.indiana.edu <a href="ftp://ftp.uwsg.indiana.edu/linux/debian/">/linux/debian/</a> <a href="http://ftp.uwsg.indiana.edu/linux/debian/">/linux/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -natasha.stmarytx.edu <a href="ftp://natasha.stmarytx.edu/debian/">/debian/</a> <a href="http://natasha.stmarytx.edu/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.ndlug.nd.edu <a href="ftp://ftp.ndlug.nd.edu/debian/">/debian/</a> <a href="http://ftp.ndlug.nd.edu/mirrors/debian/">/mirrors/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.uchicago.edu <a href="ftp://debian.uchicago.edu/debian/">/debian/</a> <a href="http://debian.uchicago.edu/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -carroll.aset.psu.edu <a href="ftp://carroll.aset.psu.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a> <a href="http://carroll.aset.psu.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.fifi.org <a href="ftp://debian.fifi.org/pub/debian/">/pub/debian/</a> <a href="http://debian.fifi.org/debian/">/debian/</a> amd64 i386 sparc -gladiator.real-time.com <a href="ftp://gladiator.real-time.com/linux/debian/">/linux/debian/</a> alpha amd64 i386 powerpc sparc -mirrors.kernel.org <a href="ftp://mirrors.kernel.org/debian/">/debian/</a> <a href="http://mirrors.kernel.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.keystealth.org <a href="ftp://ftp.keystealth.org/debian/">/debian/</a> <a href="http://ftp.keystealth.org/debian/">/debian/</a> amd64 hurd-i386 i386 ia64 mips mipsel sparc -debian.lcs.mit.edu <a href="ftp://debian.lcs.mit.edu/debian/">/debian/</a> <a href="http://debian.lcs.mit.edu/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -linux.csua.berkeley.edu <a href="ftp://linux.csua.berkeley.edu/debian/">/debian/</a> <a href="http://linux.csua.berkeley.edu/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.secsup.org <a href="ftp://debian.secsup.org/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://debian.secsup.org/">/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -techweb.rfa.org <a href="ftp://techweb.rfa.org/debian/">/debian/</a> <a href="http://techweb.rfa.org/debian/">/debian/</a> amd64 i386 -debian.osuosl.org <a href="ftp://debian.osuosl.org/debian/">/debian/</a> <a href="http://debian.osuosl.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.anl.gov <a href="ftp://mirror.anl.gov/pub/debian/">/pub/debian/</a> <a href="http://mirror.anl.gov/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -sluglug.ucsc.edu <a href="http://sluglug.ucsc.edu/debian/">/debian/</a> amd64 hurd-i386 i386 powerpc sparc -mirrors.geeks.org <a href="ftp://mirrors.geeks.org/debian/">/debian/</a> <a href="http://mirrors.geeks.org/debian/">/debian/</a> amd64 i386 -debian.midco.net <a href="http://debian.midco.net/debian/">/debian/</a> i386 -mirrors.usc.edu <a href="ftp://mirrors.usc.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a> <a href="http://mirrors.usc.edu/pub/linux/distributions/debian/">/pub/linux/distributions/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.mirrors.pair.com <a href="ftp://debian.mirrors.pair.com/">/</a> <a href="http://debian.mirrors.pair.com/">/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -lug.mtu.edu <a href="ftp://lug.mtu.edu/debian/">/debian/</a> <a href="http://lug.mtu.edu/debian/">/debian/</a> alpha amd64 hppa i386 mips mipsel powerpc sparc -debian.mirrors.tds.net <a href="ftp://debian.mirrors.tds.net/debian/">/debian/</a> <a href="http://debian.mirrors.tds.net/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.cites.uiuc.edu <a href="ftp://debian.cites.uiuc.edu/pub/debian/">/pub/debian/</a> <a href="http://debian.cites.uiuc.edu/pub/debian/">/pub/debian/</a> amd64 hurd-i386 i386 ia64 powerpc sparc -mirrors.tummy.com <a href="ftp://mirrors.tummy.com/pub/ftp.debian.org/">/pub/ftp.debian.org/</a> <a href="http://mirrors.tummy.com/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.mirror.frontiernet.net <a href="ftp://debian.mirror.frontiernet.net/debian/">/debian/</a> <a href="http://debian.mirror.frontiernet.net/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -cudlug.cudenver.edu <a href="ftp://cudlug.cudenver.edu/debian/">/debian/</a> <a href="http://cudlug.cudenver.edu/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.tucdemonic.org <a href="http://mirror.tucdemonic.org/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -bigmirror.crossbowproject.net <a href="ftp://bigmirror.crossbowproject.net/pub/debian/">/pub/debian/</a> alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.cise.ufl.edu <a href="ftp://ftp.cise.ufl.edu/pub/mirrors/debian/">/pub/mirrors/debian/</a> amd64 i386 -mirror.cc.columbia.edu <a href="ftp://mirror.cc.columbia.edu/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> <a href="http://mirror.cc.columbia.edu/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> amd64 i386 powerpc - -<b>VE Venezuela</b> ------------- -debian.unesr.edu.ve <a href="http://debian.unesr.edu.ve/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -<b>ZA South Africa</b> ---------------- -ftp.sun.ac.za <a href="ftp://ftp.sun.ac.za/debian/">/debian/</a> <a href="http://ftp.sun.ac.za/ftp/debian/">/ftp/debian/</a> amd64 i386 -debian.mirror.ac.za <a href="ftp://debian.mirror.ac.za/debian/">/debian/</a> <a href="http://debian.mirror.ac.za/debian/">/debian/</a> alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -</small></pre><hr> -<table border="0" width="100%"><tr> - <td align="left"><small>Last modified: Thu Apr 5 07:52:11 2007</small></td> - <td align="right"><small>Number of sites listed: 301</small></td> -</tr></table> -</body> -</html> diff --git a/includes/sid/install/README.mirrors.txt b/includes/sid/install/README.mirrors.txt deleted file mode 100644 index 31bbf0d..0000000 --- a/includes/sid/install/README.mirrors.txt +++ /dev/null @@ -1,509 +0,0 @@ - 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. - Additionally, most of them are updated automatically after updates to the - Debian archive. The Debian archive on those sites is normally available - using both FTP and HTTP protocols. - - 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Australia ftp.au.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Australia ftp.wa.au.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Bulgaria ftp.bg.debian.org /debian/ alpha amd64 arm i386 ia64 m68k mips mipsel powerpc sparc - Brazil ftp.br.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Switzerland ftp.ch.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Chile ftp.cl.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Czech Republic ftp.cz.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Germany ftp.de.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Germany ftp2.de.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Denmark ftp.dk.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Estonia ftp.ee.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Spain ftp.es.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Finland ftp.fi.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - France ftp.fr.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - France ftp2.fr.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Great Britain ftp.uk.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Hong Kong ftp.hk.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Croatia ftp.hr.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Hungary ftp.hu.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Ireland ftp.ie.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Iceland ftp.is.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Italy ftp.it.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Japan ftp.jp.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Japan ftp2.jp.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Korea ftp.kr.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Mexico ftp.mx.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Netherlands ftp.nl.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Norway ftp.no.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 powerpc s390 sparc - New Zealand ftp.nz.debian.org /debian/ alpha amd64 arm hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc - Poland ftp.pl.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Romania ftp.ro.debian.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - Russia ftp.ru.debian.org /debian/ amd64 i386 - Sweden ftp.se.debian.org /debian/ alpha amd64 arm 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 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - United States ftp.us.debian.org /debian/ amd64 i386 - - - Secondary mirrors of the Debian archive - --------------------------------------- - -HOST NAME FTP HTTP ARCHITECTURES ---------- --- ---- ------------- - -AR Argentina ------------- -debian.logiclinux.com /debian/ i386 -ftp.ccc.uba.ar /pub/linux/debian/debian/ /pub/linux/debian/debian/ amd64 i386 - -AT Austria ----------- -ftp.at.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -gd.tuwien.ac.at /opsys/linux/debian/ /opsys/linux/debian/ alpha amd64 arm 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 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 i386 powerpc sparc - -AU Australia ------------- -ftp.wa.au.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.au.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.aarnet.edu.au /debian/ /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.iinet.net.au /debian/debian/ /debian/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.datafast.net.au /debian/ /debian/ amd64 i386 -mirror.optus.net /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -BE Belgium ----------- -ftp.kulnet.kuleuven.ac.be /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.easynet.be /debian/ /ftp/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.belnet.be /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.debian.skynet.be /debian/ /ftp/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.scarlet.be /pub/debian/ /pub/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -BG Bulgaria ------------ -ftp.bg.debian.org /debian/ /debian/ alpha amd64 arm i386 ia64 m68k mips mipsel powerpc sparc -debian.ludost.net /debian/ /debian/ i386 -ftp.uni-sofia.bg /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.telecoms.bg /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -BR Brazil ---------- -ftp.br.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -sft.if.usp.br /debian/ alpha amd64 arm 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 -www.las.ic.unicamp.br /pub/debian/ /pub/debian/ amd64 hurd-i386 i386 powerpc sparc -debian.pop-sc.rnp.br /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -BY Belarus ----------- -linux.org.by /debian/ /debian/ amd64 i386 -ftp.mgts.by /debian/ /debian/ amd64 i386 - -CA Canada ---------- -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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.cpsc.ucalgary.ca /debian/ /debian/ amd64 i386 -mirror.peer1.net /debian/ alpha amd64 arm i386 mips mipsel powerpc sparc -debian.mirror.rafal.ca /debian/ /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -CH Switzerland --------------- -ftp.ch.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.switch.ch /mirror/debian/ /ftp/mirror/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -CL Chile --------- -ftp.cl.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.ubiobio.cl /debian/ amd64 i386 powerpc sparc - -CN China --------- -ftp.linuxforum.net /debian/ i386 -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 - -CZ Czech Republic ------------------ -ftp.cz.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.sh.cvut.cz /debian/ /debian/ alpha amd64 arm 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 - -DE Germany ----------- -ftp.de.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp2.de.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.tu-clausthal.de /pub/linux/debian/ amd64 arm i386 ia64 m68k mips powerpc sparc -debian.uni-essen.de /debian/ /debian/ amd64 hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc -ftp.freenet.de /pub/ftp.debian.org/debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -sunsite.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 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.tu-bs.de /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.uni-koeln.de /debian/ /debian/ alpha amd64 i386 powerpc sparc -debian.pffa.de /pub/mirrors/debian/ /mirrors/debian/ i386 -ftp.mpi-sb.mpg.de /pub/linux/distributions/debian/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.tiscali.de /pub/debian/debian/ /pub/debian/debian/ amd64 arm hurd-i386 i386 ia64 -ftp.tu-chemnitz.de /pub/linux/debian/debian/ /pub/linux/debian/debian/ alpha amd64 arm 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 /pub/linux/Debian/debian/ /linux/Debian/debian/ alpha amd64 hurd-i386 i386 ia64 -ftp.informatik.hu-berlin.de /pub/Mirrors/ftp.de.debian.org/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.gwdg.de /pub/linux/debian/debian/ /pub/linux/debian/debian/ amd64 hurd-i386 i386 -ftp.hosteurope.de /pub/linux/debian/ /pub/linux/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.netcologne.de /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -artfiles.org /debian/ /debian/ amd64 i386 -debian.intergenia.de /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.swordcoast.net /debian/ /debian/ alpha amd64 arm hurd-i386 i386 ia64 m68k powerpc -debian.cruisix.net /debian/ /debian/ amd64 i386 powerpc -ftp.rrzn.uni-hannover.de /debian/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian-ftp.charite.de /debian/ i386 - -DK Denmark ----------- -ftp.dk.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.dkuug.dk /pub/debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.here.dk /debian/ amd64 i386 ia64 mips powerpc -debian.uni-c.dk /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirrors.telianet.dk /debian/ /debian/ amd64 i386 powerpc sparc - -EE Estonia ----------- -ftp.ee.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -ES Spain --------- -ftp.es.debian.org /debian/ /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.caliu.info /debian/ /debian/ i386 ia64 m68k mips mipsel powerpc sparc -ftp.gva.es /pub/mirror/debian/ /mirror/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.gul.uc3m.es /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.um.es /mirror/debian/ all -jane.uab.cat /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -FI Finland ----------- -ftp.fi.debian.org /debian/ /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.jyu.fi /debian/ /debian/ alpha amd64 hurd-i386 i386 powerpc sparc - -FR France ---------- -ftp.fr.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp2.fr.debian.org /debian/ /debian/ alpha amd64 arm 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.proxad.net /mirrors/ftp.debian.org/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.u-picardie.fr /mirror/debian/ /mirror/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.mirrors.easynet.fr /debian/ / alpha amd64 arm 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.ibisc.univ-evry.fr /debian/ /debian/ amd64 i386 -mir1.ovh.net /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mir2.ovh.net /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.mines.inpl-nancy.fr /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.debian.ikoula.com /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -webb.ens-cachan.fr /debian/ /debian/ alpha amd64 arm 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 i386 ia64 powerpc sparc - -GB Great Britain ----------------- -ftp.uk.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.mcc.ac.uk /pub/linux/distributions/Debian/ hurd-i386 i386 sh -www.mirrorservice.org /sites/ftp.debian.org/debian/ /sites/ftp.debian.org/debian/ amd64 i386 -download.mirror.ac.uk /sites/ftp.debian.org/debian/ /sites/ftp.debian.org/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.ticklers.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.blueyonder.co.uk /pub/debian/ / alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.positive-internet.com /debian/ /debian/ amd64 hppa i386 ia64 powerpc -the.earth.li /debian/ /debian/ amd64 hurd-i386 i386 -mirror.ox.ac.uk /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -GR Greece ---------- -debian.otenet.gr /pub/linux/debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.ntua.gr /pub/linux/debian/ /pub/linux/debian/ amd64 i386 sparc -ftp.duth.gr /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.softnet.tuc.gr /pub/linux/debian/ /ftp/linux/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.internet.gr /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -HK Hong Kong ------------- -ftp.hk.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -www.zentek-international.com /mirrors/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -HR Croatia ----------- -ftp.hr.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.irb.hr /debian/ /debian/ amd64 arm hurd-i386 i386 ia64 powerpc sparc -ftp.carnet.hr /debian/ /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.bme.hu /OS/Linux/dist/debian/ /OS/Linux/dist/debian/ amd64 hurd-i386 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.esat.net /pub/linux/debian/ /pub/linux/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -IL Israel ---------- -mirror.hamakor.org.il /pub/mirrors/debian/ amd64 i386 -debian.co.il /debian/ amd64 i386 - -IS Iceland ----------- -ftp.is.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -IT Italy --------- -ftp.it.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.bononia.it /debian/ /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mi.mirror.garr.it /mirrors/debian/ /mirrors/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.fastweb.it /debian/ /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.fastbull.org /debian/ /debian/ amd64 i386 powerpc sparc - -JP Japan --------- -ftp.jp.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp2.jp.debian.org /debian/ /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.dti.ad.jp /pub/Linux/debian/ /pub/Linux/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -dennou-k.gfd-dennou.org /library/Linux/debian/ /library/Linux/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -dennou-q.gfd-dennou.org /library/Linux/debian/ /library/Linux/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.yz.yamagata-u.ac.jp /debian/ /debian/ alpha amd64 arm 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 /pub/Linux/debian/debian/ /pub/Linux/debian/debian/ amd64 i386 -debian.shimpinomori.net /debian/ amd64 i386 powerpc -www.ring.gr.jp /pub/linux/debian/debian/ /archives/linux/debian/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.jaist.ac.jp /pub/Linux/Debian/ /pub/Linux/Debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -KR Korea --------- -ftp.kr.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -LT Lithuania ------------- -ameba.sc-uni.ktu.lt /debian/ /debian/ i386 -debian.balt.net /debian/ /debian/ amd64 arm i386 sparc - -MX Mexico ---------- -ftp.mx.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mmc.igeofcu.unam.mx /debian/ amd64 hurd-i386 i386 ia64 - -NI Nicaragua ------------- -debian.uni.edu.ni /debian/ amd64 hurd-i386 i386 - -NL Netherlands --------------- -ftp.nl.debian.org /debian/ /debian/ alpha amd64 arm 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 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.debian.nl /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.tiscali.nl /pub/mirrors/debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.essentkabel.com /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.scarlet-internet.nl /pub/debian/ /pub/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -NO Norway ---------- -ftp.no.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 powerpc s390 sparc - -NZ New Zealand --------------- -ftp.nz.debian.org /debian/ /debian/ alpha amd64 arm hurd-i386 i386 ia64 m68k mips mipsel powerpc sparc -debian.ihug.co.nz /debian/ /debian/ amd64 i386 - -PL Poland ---------- -ftp.pl.debian.org /debian/ /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.vectranet.pl /debian/ /debian/ amd64 i386 - -PT Portugal ------------ -ftp.uevora.pt /debian/ /debian/ amd64 i386 -ftp.eq.uc.pt /pub/software/Linux/debian/ /software/Linux/debian/ amd64 i386 -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/ all - -RO Romania ----------- -ftp.ro.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.lug.ro /debian/ /debian/ amd64 i386 powerpc - -RU Russia ---------- -ftp.ru.debian.org /debian/ /debian/ amd64 i386 -debian.nsu.ru /debian/ /debian/ amd64 i386 -debian.udsu.ru /debian/ /debian/ amd64 i386 -ftp.psn.ru /debian/ /debian/ alpha amd64 hurd-i386 i386 -ftp.corbina.ru /pub/Linux/debian/ amd64 i386 ia64 -ftp.mipt.ru /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -SE Sweden ---------- -ftp.se.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.sunet.se /pub/os/Linux/distributions/debian/ /pub/os/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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.ds.hj.se /pub/os/linux/debian/ /pub/os/linux/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.bsnet.se /debian/ i386 - -SG Singapore ------------- -mirror.nus.edu.sg /pub/Debian/ /Debian/ amd64 i386 -debian.wow-vision.com.sg /debian/ /debian/ amd64 i386 - -SI Slovenia ------------ -ftp.si.debian.org /debian/ /debian/ alpha amd64 i386 ia64 m68k powerpc sparc -ftp.arnes.si /packages/debian/ amd64 hurd-i386 i386 - -SK Slovakia ------------ -ftp.sk.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -TH Thailand ------------ -ftp.coe.psu.ac.th /debian/ /debian/ i386 -ftp.thaios.net /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -TR Turkey ---------- -ftp.tr.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -godel.cs.bilgi.edu.tr /debian/ hurd-i386 i386 - -TW Taiwan ---------- -ftp.tw.debian.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.csie.ntu.edu.tw /pub/debian/ /debian/ amd64 hurd-i386 i386 -linux.cdpa.nsysu.edu.tw /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -opensource.nchc.org.tw /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.nctu.edu.tw /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.nttu.edu.tw /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.csie.nctu.edu.tw /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -UA Ukraine ----------- -debian.osdn.org.ua /pub/Debian/debian/ /debian/ i386 -debian.org.ua /debian/ /debian/ i386 -ftp.3logic.net /debian/ i386 - -US United States ----------------- -ftp.us.debian.org /debian/ /debian/ amd64 i386 -ftp.debian.org /debian/ /debian/ amd64 i386 -ftp.gtlib.gatech.edu /pub/debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.egr.msu.edu /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -distro.ibiblio.org /pub/linux/distributions/debian/ /pub/linux/distributions/debian/ amd64 hurd-i386 i386 powerpc -ftp-mirror.internap.com /pub/debian/ /pub/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.cerias.purdue.edu /pub/os/debian/ /pub/os/debian/ amd64 i386 -ftp.cs.unm.edu /mirrors/debian/ alpha arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -natasha.stmarytx.edu /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.ndlug.nd.edu /debian/ /mirrors/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.uchicago.edu /debian/ /debian/ alpha amd64 arm 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 hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.fifi.org /pub/debian/ /debian/ amd64 i386 sparc -gladiator.real-time.com /linux/debian/ alpha amd64 i386 powerpc sparc -mirrors.kernel.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.keystealth.org /debian/ /debian/ amd64 hurd-i386 i386 ia64 mips mipsel sparc -debian.lcs.mit.edu /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -linux.csua.berkeley.edu /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.secsup.org /pub/linux/debian/ / alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -techweb.rfa.org /debian/ /debian/ amd64 i386 -debian.osuosl.org /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -mirror.anl.gov /pub/debian/ /debian/ alpha amd64 arm 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 -debian.midco.net /debian/ i386 -mirrors.usc.edu /pub/linux/distributions/debian/ /pub/linux/distributions/debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.mirrors.pair.com / / alpha amd64 arm 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 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 /pub/ftp.debian.org/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -debian.mirror.frontiernet.net /debian/ /debian/ alpha amd64 arm 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 -mirror.tucdemonic.org /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc -bigmirror.crossbowproject.net /pub/debian/ alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc -ftp.cise.ufl.edu /pub/mirrors/debian/ amd64 i386 -mirror.cc.columbia.edu /pub/linux/debian/debian/ /pub/linux/debian/debian/ amd64 i386 powerpc - -VE Venezuela ------------- -debian.unesr.edu.ve /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -ZA South Africa ---------------- -ftp.sun.ac.za /debian/ /ftp/debian/ amd64 i386 -debian.mirror.ac.za /debian/ /debian/ alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc - -------------------------------------------------------------------------------- -Last modified: Thu Apr 5 07:52:11 2007 Number of sites listed: 301 diff --git a/includes/squeeze b/includes/squeeze new file mode 120000 index 0000000..fb5b653 --- /dev/null +++ b/includes/squeeze @@ -0,0 +1 @@ +lenny
\ No newline at end of file |
