manuel
/
live-build
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Adding live-package 0.99-1.

This commit is contained in:
Daniel Baumann 2007-09-23 10:04:20 +02:00
commit eeaafbe5c0
131 changed files with 15149 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
AUTHORS Normal file
View File

@ -0,0 +1,9 @@
Main authors
* Daniel Baumann <daniel@debian.org>
* Marco Amadori <marco.amadori@gmail.com>
Patches (alphabetical order)
* Frederic Lehobey <Frederic.Lehobey@free.fr>
* Jason D. Clinton <me@jasonclinton.com>

339
COPYING Normal file
View File

@ -0,0 +1,339 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), 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.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License.

89
ChangeLog Normal file
View File

@ -0,0 +1,89 @@
2006-07-18 Daniel Baumann <daniel@debian.org>
* Added iso templates.
2006-07-17 Daniel Baumann <daniel@debian.org>
* Added chroot to 01-patch.sh.
* Added "--logfile".
2006-07-01 Daniel Baumann <daniel.baumann@panthera-systems.net>
* Added "--flavour".
2006-06-28 Daniel Baumann <daniel.baumann@panthera-systems.net>
* Added "--debug" and "--verbose".
2006-06-23 Daniel Baumann <daniel.baumann@panthera-systems.net>
* Rewritten manpages.
2006-06-19 Marco Amadori <marco.amadori@gmail.com>
* Added "--templates" options.
* Fixed some typos.
2006-06-15 Daniel Baumann <daniel.baumann@panthera-systems.net>
* General fixes.
2006-06-18 Marco Amadori <marco.amadori@gmail.com>
* Added "-a|--architecture" and "-p|--package-list" options.
* Reworked how lists works.
2006-06-15 Daniel Baumann <daniel.baumann@panthera-systems.net>
* General cleanup.
2006-06-14 Marco Amadori <marco.amadori@gmail.com>
* Re-added "-f|--filesystem".
2006-06-12 Marco Amadori <marco.amadori@gmail.com>
* Added "--conffile", "--preseed", "--clone", and "--rootfs" options.
2006-06-12 Daniel Baumann <daniel.baumann@panthera-systems.net>
* Added new splash.rle.
* Added memtest86+.
* Added "--distribution", and "--section" options.
* Moved /etc/default/make-live to /etc/make-live.conf.
2006-06-11 Marco Amadori <marco.amadori@gmail.com>
* Added handling of md5sums.
2006-06-09 Marco Amadori <marco.amadori@gmail.com>
* Added splashy support.
* Added ext2 rootfs support.
* Added external hook and path support.
* Swiched to getopt.
2006-06-02 Daniel Baumann <daniel.baumann@panthera-systems.net>
* Added patch from Jason D. Clinton <me@jasonclinton.com>:
- Added netboot flavour.
- Thanks to SafeDesk Solutions <http://www.safedesk.com/>.
2006-06-01 Daniel Baumann <daniel.baumann@panthera-systems.net>
* Moved syslinux inside the chroot.
2006-05-31 Daniel Baumann <daniel.baumann@panthera-systems.net>
* Added kde-*i18n and standard-i18n lists.
2006-05-28 Daniel Baumann <daniel.baumann@panthera-systems.net>
* Added patch from Frederic Lehobey <Frederic.Lehobey@free.fr>:
- Added locales to LIVE_PACKAGES.
- Added LIVE_MIRROR_KEY, LIVE_REPOSITORY, LIVE_REPOSITORY_KEY, and
LIVE_BOOTAPPEND.
2006-05-27 Daniel Baumann <daniel.baumann@panthera-systems.net>
* Initial release.

36
Makefile Normal file
View File

@ -0,0 +1,36 @@
# Makefile
all: install
install:
# Install main script
install -D -m 755 make-live.sh $(DESTDIR)/usr/sbin/make-live
install -d -m 755 $(DESTDIR)/usr/share/make-live
# Install package lists
cp -a lists $(DESTDIR)/usr/share/make-live
# Install sub scripts
cp -a scripts $(DESTDIR)/usr/share/make-live
# Install configuration templates
cp -a templates $(DESTDIR)/usr/share/make-live
# Install manpages
install -d -m 755 $(DESTDIR)/usr/share/man/man8
cp -a make-live.8 make-live.conf.8 $(DESTDIR)/usr/share/man/man8
# Install configuration file
install -D -m 644 make-live.conf $(DESTDIR)/etc/make-live.conf
uninstall:
# Remove main script
rm -rf $(DESTDIR)/usr/sbin/make-live
# Remove shared data
rm -rf $(DESTDIR)/usr/share/make-live
# Remove configuration file
rm -f $(DESTDIR)/etc/make-live.conf
reinstall: uninstall install

4
TODO-1.0 Normal file
View File

@ -0,0 +1,4 @@
logfile and output hiding
multiple other repositories
d-i/g-i
documentation

24
contrib/syslinux-splash/COPYING Normal file
View File

@ -0,0 +1,24 @@
The derivated splash for Debian Live was done by Daniel Baumann
<daniel@debian.org> from the original of Mark Riedesel. Daniels own contribution
to the derivated splash is hereby placed in the public domain.
---------------
http://dugnet.com/klown/pics/klowner_debboot.png
by Mark Riedesel, license same as open use logo
To create klowner.rle:
1. convert klowner.png klowner.bmp
2. bmptoppm < klowner.bmp | ppmtolss16 #FBFDFA=7 > klowner.rle
(FBFDFA is the color used for the inside of the "n" in Debian.)
---------------
Debian Open Use Logo License
Copyright (c) 1999 Software in the Public Interest
This logo or a modified version may be used by anyone to refer to the Debian
project, but does not indicate endorsement by the project.
Note: we would appreciate that you make the image a link to
http://www.debian.org/ if you use it on a web page.

BIN
contrib/syslinux-splash/klowner.rle Normal file
View File

Binary file not shown.

BIN
contrib/syslinux-splash/klowner_debboot.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 6.2 KiB

BIN
contrib/syslinux-splash/live.rle Normal file
View File

Binary file not shown.

BIN
contrib/syslinux-splash/live_debboot.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 101 KiB

5
debian/changelog vendored Normal file
View File

@ -0,0 +1,5 @@
live-package (0.99-1) unstable; urgency=low
* Initial release.
-- Daniel Baumann <daniel@debian.org> Mon, 17 Jul 2006 00:00:00 +0200

1
debian/compat vendored Normal file
View File

@ -0,0 +1 @@
4

14
debian/control vendored Normal file
View File

@ -0,0 +1,14 @@
Source: live-package
Section: misc
Priority: optional
Maintainer: Daniel Baumann <daniel@debian.org>
Uploaders: Marco Amadori <marco.amadori@gmail.com>
Build-Depends: debhelper (>= 4)
Standards-Version: 3.7.2
Package: live-package
Architecture: all
Depends: cdebootstrap (>= 0.3.10) | debootstrap (>= 3.3), dpkg-dev, genext2fs, mkisofs, squashfs-tools
Provides: make-live
Description: Debian Live framework
The Debian Live framework lets you automagically create live system images.

57
debian/copyright vendored Normal file
View File

@ -0,0 +1,57 @@
This package was debianized by Daniel Baumann <daniel@debian.org> on
Mon, 17 Jul 2006 00:00:00 +0200.
It was downloaded from <http://live.debian.net/>.
Copyright Holders: Daniel Baumann <daniel@debian.org>,
Marco Amadori <marco.amadori@gmail.com>.
License:
Copyright (C) 2006 Daniel Baumann <daniel@debian.org>
Copyright (C) 2006 Marco Amadori <marco.amadori@gmail.com>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
On Debian systems, the complete text of the GNU General Public License
can be found in /usr/share/common-licenses/GPL file.
License (contrib/syslinux-splash/*, templates/isolinux/splash.rle):
The derivated splash for Debian Live was done by Daniel Baumann
<daniel@debian.org> from the original of Mark Riedesel. Daniels own
contribution to the derivated splash is hereby placed in the public
domain.
---------------
http://dugnet.com/klown/pics/klowner_debboot.png
by Mark Riedesel, license same as open use logo
To create klowner.rle:
1. convert klowner.png klowner.bmp
2. bmptoppm < klowner.bmp | ppmtolss16 #FBFDFA=7 > klowner.rle
(FBFDFA is the color used for the inside of the "n" in Debian.)
---------------
Debian Open Use Logo License
Copyright (c) 1999 Software in the Public Interest
This logo or a modified version may be used by anyone to refer to the
Debian project, but does not indicate endorsement by the project.
Note: we would appreciate that you make the image a link to
http://www.debian.org/ if you use it on a web page.

1
debian/docs vendored Normal file
View File

@ -0,0 +1 @@
AUTHORS

43
debian/rules vendored Executable file
View File

@ -0,0 +1,43 @@
#!/usr/bin/make -f
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
upstream:
cd .. && svn co svn://live.debian.net/live-package || exit 0
find . -type d -name .svn -exec rm -rf {} \; || exit 0
build:
clean:
dh_testdir
dh_testroot
dh_clean
install: build
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs
# Installing package
$(MAKE) install DESTDIR=$(CURDIR)/debian/live-package
binary-arch: build install
binary-indep: build install
dh_testdir
dh_testroot
dh_installchangelogs ChangeLog
dh_installdocs
dh_install
dh_compress
dh_fixperms
dh_installdeb
dh_gencontrol
dh_md5sums
dh_builddeb
binary: binary-indep binary-arch
.PHONY: build clean binary-indep binary-arch binary install

1
lists/gnome Normal file
View File

@ -0,0 +1 @@
gnome-desktop-environment gdm-themes gnome-cups-manager gnome-themes-extras rhythmbox synaptic gnome-screensaver gdm x-window-system-core

1
lists/gnome-core Normal file
View File

@ -0,0 +1 @@
gnome-core gdm x-window-system-core

1
lists/gnome-full Normal file
View File

@ -0,0 +1 @@
gnome gdm x-window-system-core

1
lists/kde Normal file
View File

@ -0,0 +1 @@
kde kdm x-window-system-core

1
lists/kde-core Normal file
View File

@ -0,0 +1 @@
kde-core kdm x-window-system-core

1
lists/kde-core-i18n Normal file
View File

@ -0,0 +1 @@
kde-core kdm x-window-system-core kde-i18n-af kde-i18n-ar kde-i18n-az kde-i18n-bg kde-i18n-bn kde-i18n-br kde-i18n-bs kde-i18n-ca kde-i18n-cs kde-i18n-cy kde-i18n-da kde-i18n-de kde-i18n-el kde-i18n-engb kde-i18n-eo kde-i18n-es kde-i18n-et kde-i18n-eu kde-i18n-fa kde-i18n-fi kde-i18n-fr kde-i18n-fy kde-i18n-ga kde-i18n-gl kde-i18n-he kde-i18n-hi kde-i18n-hr kde-i18n-hu kde-i18n-is kde-i18n-it kde-i18n-ja kde-i18n-km kde-i18n-ko kde-i18n-lt kde-i18n-lv kde-i18n-mk kde-i18n-mn kde-i18n-ms kde-i18n-nb kde-i18n-nds kde-i18n-nl kde-i18n-nn kde-i18n-pa kde-i18n-pl kde-i18n-pt kde-i18n-ptbr kde-i18n-ro kde-i18n-ru kde-i18n-rw kde-i18n-se kde-i18n-sk kde-i18n-sl kde-i18n-sr kde-i18n-srlatin kde-i18n-ss kde-i18n-sv kde-i18n-ta kde-i18n-tg kde-i18n-tr kde-i18n-uk kde-i18n-uz kde-i18n-zhcn manpages manpages-de manpages-de-dev manpages-dev manpages-es manpages-es-extra manpages-fi manpages-fr manpages-hu manpages-it manpages-ja manpages-ja-dev manpages-ko manpages-nl manpages-pl manpages-pl-dev manpages-pt manpages-pt-dev manpages-ru manpages-tr manpages-zh

1
lists/kde-extra Normal file
View File

@ -0,0 +1 @@
kde koffice kde-extras kdm x-window-system-core

1
lists/kde-extra-i18n Normal file
View File

@ -0,0 +1 @@
kde koffice kde-extras kdm x-window-system-core kde-i18n-af kde-i18n-ar kde-i18n-az kde-i18n-bg kde-i18n-bn kde-i18n-br kde-i18n-bs kde-i18n-ca kde-i18n-cs kde-i18n-cy kde-i18n-da kde-i18n-de kde-i18n-el kde-i18n-engb kde-i18n-eo kde-i18n-es kde-i18n-et kde-i18n-eu kde-i18n-fa kde-i18n-fi kde-i18n-fr kde-i18n-fy kde-i18n-ga kde-i18n-gl kde-i18n-he kde-i18n-hi kde-i18n-hr kde-i18n-hu kde-i18n-is kde-i18n-it kde-i18n-ja kde-i18n-km kde-i18n-ko kde-i18n-lt kde-i18n-lv kde-i18n-mk kde-i18n-mn kde-i18n-ms kde-i18n-nb kde-i18n-nds kde-i18n-nl kde-i18n-nn kde-i18n-pa kde-i18n-pl kde-i18n-pt kde-i18n-ptbr kde-i18n-ro kde-i18n-ru kde-i18n-rw kde-i18n-se kde-i18n-sk kde-i18n-sl kde-i18n-sr kde-i18n-srlatin kde-i18n-ss kde-i18n-sv kde-i18n-ta kde-i18n-tg kde-i18n-tr kde-i18n-uk kde-i18n-uz kde-i18n-zhcn koffice-i18n-af koffice-i18n-bg koffice-i18n-br koffice-i18n-ca koffice-i18n-cs koffice-i18n-cy koffice-i18n-da koffice-i18n-de koffice-i18n-el koffice-i18n-engb koffice-i18n-eo koffice-i18n-es koffice-i18n-et koffice-i18n-fa koffice-i18n-fi koffice-i18n-fr koffice-i18n-he koffice-i18n-hsb koffice-i18n-hu koffice-i18n-it koffice-i18n-ja koffice-i18n-lo koffice-i18n-mt koffice-i18n-nb koffice-i18n-nl koffice-i18n-nn koffice-i18n-pl koffice-i18n-pt koffice-i18n-ptbr koffice-i18n-ru koffice-i18n-se koffice-i18n-sk koffice-i18n-sl koffice-i18n-sr koffice-i18n-sv koffice-i18n-tg koffice-i18n-th koffice-i18n-tr koffice-i18n-ven koffice-i18n-xh koffice-i18n-zhcn koffice-i18n-zhcngb2312 koffice-i18n-zhtw koffice-i18n-zhtwbig5 koffice-i18n-zu manpages manpages-de manpages-de-dev manpages-dev manpages-es manpages-es-extra manpages-fi manpages-fr manpages-hu manpages-it manpages-ja manpages-ja-dev manpages-ko manpages-nl manpages-pl manpages-pl-dev manpages-pt manpages-pt-dev manpages-ru manpages-tr manpages-zh

1
lists/kde-full Normal file
View File

@ -0,0 +1 @@
kde koffice kdm x-window-system-core

1
lists/kde-full-i18n Normal file
View File

@ -0,0 +1 @@
kde koffice kdm x-window-system-core kde-i18n-af kde-i18n-ar kde-i18n-az kde-i18n-bg kde-i18n-bn kde-i18n-br kde-i18n-bs kde-i18n-ca kde-i18n-cs kde-i18n-cy kde-i18n-da kde-i18n-de kde-i18n-el kde-i18n-engb kde-i18n-eo kde-i18n-es kde-i18n-et kde-i18n-eu kde-i18n-fa kde-i18n-fi kde-i18n-fr kde-i18n-fy kde-i18n-ga kde-i18n-gl kde-i18n-he kde-i18n-hi kde-i18n-hr kde-i18n-hu kde-i18n-is kde-i18n-it kde-i18n-ja kde-i18n-km kde-i18n-ko kde-i18n-lt kde-i18n-lv kde-i18n-mk kde-i18n-mn kde-i18n-ms kde-i18n-nb kde-i18n-nds kde-i18n-nl kde-i18n-nn kde-i18n-pa kde-i18n-pl kde-i18n-pt kde-i18n-ptbr kde-i18n-ro kde-i18n-ru kde-i18n-rw kde-i18n-se kde-i18n-sk kde-i18n-sl kde-i18n-sr kde-i18n-srlatin kde-i18n-ss kde-i18n-sv kde-i18n-ta kde-i18n-tg kde-i18n-tr kde-i18n-uk kde-i18n-uz kde-i18n-zhcn koffice-i18n-af koffice-i18n-bg koffice-i18n-br koffice-i18n-ca koffice-i18n-cs koffice-i18n-cy koffice-i18n-da koffice-i18n-de koffice-i18n-el koffice-i18n-engb koffice-i18n-eo koffice-i18n-es koffice-i18n-et koffice-i18n-fa koffice-i18n-fi koffice-i18n-fr koffice-i18n-he koffice-i18n-hsb koffice-i18n-hu koffice-i18n-it koffice-i18n-ja koffice-i18n-lo koffice-i18n-mt koffice-i18n-nb koffice-i18n-nl koffice-i18n-nn koffice-i18n-pl koffice-i18n-pt koffice-i18n-ptbr koffice-i18n-ru koffice-i18n-se koffice-i18n-sk koffice-i18n-sl koffice-i18n-sr koffice-i18n-sv koffice-i18n-tg koffice-i18n-th koffice-i18n-tr koffice-i18n-ven koffice-i18n-xh koffice-i18n-zhcn koffice-i18n-zhcngb2312 koffice-i18n-zhtw koffice-i18n-zhtwbig5 koffice-i18n-zu manpages manpages-de manpages-de-dev manpages-dev manpages-es manpages-es-extra manpages-fi manpages-fr manpages-hu manpages-it manpages-ja manpages-ja-dev manpages-ko manpages-nl manpages-pl manpages-pl-dev manpages-pt manpages-pt-dev manpages-ru manpages-tr manpages-zh

1
lists/kde-i18n Normal file
View File

@ -0,0 +1 @@
kde kdm x-window-system-core kde-i18n-af kde-i18n-ar kde-i18n-az kde-i18n-bg kde-i18n-bn kde-i18n-br kde-i18n-bs kde-i18n-ca kde-i18n-cs kde-i18n-cy kde-i18n-da kde-i18n-de kde-i18n-el kde-i18n-engb kde-i18n-eo kde-i18n-es kde-i18n-et kde-i18n-eu kde-i18n-fa kde-i18n-fi kde-i18n-fr kde-i18n-fy kde-i18n-ga kde-i18n-gl kde-i18n-he kde-i18n-hi kde-i18n-hr kde-i18n-hu kde-i18n-is kde-i18n-it kde-i18n-ja kde-i18n-km kde-i18n-ko kde-i18n-lt kde-i18n-lv kde-i18n-mk kde-i18n-mn kde-i18n-ms kde-i18n-nb kde-i18n-nds kde-i18n-nl kde-i18n-nn kde-i18n-pa kde-i18n-pl kde-i18n-pt kde-i18n-ptbr kde-i18n-ro kde-i18n-ru kde-i18n-rw kde-i18n-se kde-i18n-sk kde-i18n-sl kde-i18n-sr kde-i18n-srlatin kde-i18n-ss kde-i18n-sv kde-i18n-ta kde-i18n-tg kde-i18n-tr kde-i18n-uk kde-i18n-uz kde-i18n-zhcn manpages manpages-de manpages-de-dev manpages-dev manpages-es manpages-es-extra manpages-fi manpages-fr manpages-hu manpages-it manpages-ja manpages-ja-dev manpages-ko manpages-nl manpages-pl manpages-pl-dev manpages-pt manpages-pt-dev manpages-ru manpages-tr manpages-zh

1
lists/standard-i18n Normal file
View File

@ -0,0 +1 @@
manpages manpages-de manpages-de-dev manpages-dev manpages-es manpages-es-extra manpages-fi manpages-fr manpages-hu manpages-it manpages-ja manpages-ja-dev manpages-ko manpages-nl manpages-pl manpages-pl-dev manpages-pt manpages-pt-dev manpages-ru manpages-tr manpages-zh

1
lists/x11 Normal file
View File

@ -0,0 +1 @@
xdm x-window-system

1
lists/x11-core Normal file
View File

@ -0,0 +1 @@
xdm x-window-system-core

1
lists/xfce Normal file
View File

@ -0,0 +1 @@
xfce4 gdm x-window-system-core

188
make-live.8 Normal file
View File

@ -0,0 +1,188 @@
.TH MAKE-LIVE 8 "Jul, 27 2006" "0.99" "Debian Live framework"
.SH NAME
make-live \- An utility for building Debian Live systems.
.SH SYNOPSIS
.B make-live
.RB [\| \-a \||\| \-\-architecture
.IR ARCHITECTURE \|]
.RB [\| \-c \||\| \-\-conffile
.IR FILE \|]
.RB [\| \-\-clone
.IR DIRECTORY \|]
.RB [\| \-d \||\| \-\-distribution
.IR DISTRIBUTION \|]
.BR [\| \-\-debug \|]
.RB [\| \-f \||\| \-\-filesystem
.IR FILESYSTEM \|]
.RB [\| \-\-flavour
.IR FLAVOUR \|]
.RB [\| \-\-hook
.RI \|" COMMAND .\|.\|.\|"\|]
.RB [\| \-\-include\-image
.IR FILE \||\| DIRECTORY \|]
.RB [\| \-\-include\-rootfs
.IR FILE \||\| DIRECTORY \|]
.RB [\| \-\-linux\-image
.IR FLAVOUR \|]
.RB [\| \-\-logfile
.IR FILE \|]
.RB [\| \-p \||\| \-\-package-list
.IR FILE \|]
.RB [\| \-\-preseed
.IR FILE \|]
.RB [\| \-\-rootfs
.IR DIRECTORY \|]
.RB [\| \-s \||\| \-\-section
.RI \|" SECTION \|.\|.\|.\|"\|]
.RB [\| \-\-splashy
.RI [\| THEME \|]\|]
.RB [\| \-t \||\| \-\-type
.IR TYPE \|]
.RB [\| \-\-templates
.IR DIRECTORY \|]
.RB [\| \-\-verbose \|]
.RI [\| LIST \|]
.PP
.B make-live
.RB [\| \-h \||\| \-\-help \|]
.br
.B make-live
.RB [\| \-u \||\| \-\-usage \|]
.br
.B make-live
.RB [\| \-v \||\| \-\-version \|]
.SH DESCRIPTION
The Debian Live framework lets you automagically create live system images.
.PP
.SH OPTIONS
.TP
.BI "\-a, \-\-architecture " ARCHITECTURE
Build an image for another architecture than the autodetected one. This is
usefull for e.g. building i386 images on an amd64 machine. Instead of this flag,
the environment variable LIVE_ARCHITECTURE can be used.
.TP
.BI "\-c, \-\-conffile " FILE
Uses another configuration file in addition to the default one, if existing, in
/etc/make-live.conf. Settings in the additional configuration file do overwrite
the settings from /etc/make-live.conf. Instead of this flag, the environment
varibale LIVE_CONFFILE can be used.
.TP
.BI "\-\-clone " DIRECTORY
Clones the package selection and configuration from a given root directory. It
will output the settings to $LIVE_ROOT/preseed.cloned and $LIVE_ROOT/plist.clone
for easy reuse with \-\-preseed and \-\-package-list. Instead of this flag, the
environment variable LIVE_CLONE can be used.
.TP
.BI "\-d, \-\-distribution " DISTRIBUTION
Specifies the distribution to be used. Allowed values are all Debian
distributions (oldstable, stable, testing, unstable), although only unstable
(default) is possible for now. Instead of this flag, the environment variable
LIVE_DISTRIBUTION can be used.
.TP
.B \-\-debug
Enables debut output of make-live itself (this includes \-\-verbose too).
Instead of this environment variable, LIVE_DEBUG can be used.
.TP
.BI "\-f, \-\-filesystem " FILESYSTEM
Specifies the filesystem for the compressed image. At the moment, only squashfs
(default) and ext2 are allowed values. Instead of this flag, the environment
variable LIVE_FILESYSTEM can be used.
.TP
.BI "\-\-flavour " FLAVOUR
Specifies the bootstrap flavour. This can be either standard (default) or
minimal. Instead of this flag, the environment variable LIVE_FLAVOUR can be
used.
.TP
.\" FIXME
.BI "\-\-hook " COMMAND "\|.\|.\|.\|"
Specifies a command which will be executed at the end of the chroot setup and
before the mastering of the image. Instead of this flag, the environment
variable LIVE_HOOK can be used.
.TP
.BI "\-\-include\-image " FILE \||\| DIRECTORY
specifies a file or directory which will be copied inside the image. Can be also
set through LIVE_INCLUDE_IMAGE environment variable.
.TP
.BI "\-\-include\-rootfs " FILE \||\| DIRECTORY
specifies a file or directory which will be copied inside the root filesystem of
the image. Can be also set through the LIVE_INCLUDE_ROOTFS environment variable.
.TP
.BI "\-\-linux\-image " FLAVOUR
.TP
.BI "\-p, \-\-package-list " FILE
specifies a package list file, one package for each line. It overrides list option.
.TP
.BI "\-\-logfile " FILE
specifies the location of the logfile. It can be set through LIVE_LOGFILE,
default is \$LIVE_ROOT/make-live.log
.TP
.BI "\-\-preseed " FILE
clone the packages selection and configuration from the provided
root directory.
.TP
.BI "\-\-rootfs " DIRECTORY
skip all phases of rootfs generation and just install casper and the
kernel in the specified root directory (must be a debian).
.TP
.BI "\-s, \-\-section " SECTION "\|.\|.\|.\|"
specifies which sections are going to be availble for the package selection inside the chroot (Default: main). Can be set to every combination of "main contrib non-free", also through LIVE_SECTIONS.
.TP
.BI "\-\-splashy [\|" THEME \|]
specifies that splashy should be installed and included in initamfs, an optional
official THEME could be selected or an exernal theme could be installed, in the
second case the .tar.gz theme should be passed without extension and must be in
the current directory. Can be also set through LIVE_SPLASHY and
LIVE_SPLASHY_THEME environment variables.
.TP
.BI "\-t, \-\-type " TYPE
specifies the image type to generate. Currently, only iso and net are available.
.TP
.BI "\-\-templates " DIRECTORY
specifies a templates directory to use instead of the default one.
.TP
.B \-\-verbose
providing debug information for third-party tools.
.TP
.B \-h, \-\-help
display this help and exit.
.TP
.B \-u, \-\-usage
show usage and exit.
.TP
.B \-v, \-\-version
output version information and exit.
.SH LISTS
Every list does already include the Debian standard package selection.
.TP
.B gnome | gnome-core | gnome-full
include GNOME.
.TP
.B kde | kde-core | kde-full | kde-extra
include KDE.
.TP
.B x11 | x11-core
include X-Window-System only.
.TP
.B xfce
include Xfce.
.SH BUGS
.B make-live
works fully on amd64 and i386, partially on alpha, hppa, ia64, mips, mipsel,
powerpc, s390 and sparc. Other architectures, such as arm and m68k, as well as
non-linux ports of Debian, like hurd-i386, are currently not supported.
.SH HOMEPAGE
Debian Live project <http://live.debian.net/>
.SH SEE ALSO
.BR make-live.conf (8).
.SH AUTHOR
make-live was written by Daniel Baumann <daniel@debian.org> and Marco Amadori
<marco.amadori@gmail.com>.

90
make-live.conf Normal file
View File

@ -0,0 +1,90 @@
# /etc/default/make-live: configuration file for make-live(8)
# Where do we want to build our images?
# Default: `pwd`/live
#LIVE_ROOT="`pwd`/live"
# Which Debian mirror do we use?
# Default: http://ftp.debian.org/debian
#LIVE_MIRROR="http://ftp.debian.org/debian"
# Where is the public key of the mirror?
# Default: none
LIVE_MIRROR_KEY="http://ftp-master.debian.org/ziyi_key_2006.asc"
# Which other repository do we want to add?
# Default: none
#LIVE_REPOSITORY="http://live.debian.net/debian unstable main"
# Where is the public key of the other repository?
# Default: none
#LIVE_REPOSITORY_KEY="http://ftp-master.debian-unofficial.org/key_2006.asc"
# Which FTP proxy do we want to use inside the chroot?
# Default: none
#LIVE_FTPPROXY=""
# Which HTTP proxy do we want to use inside the chroot?
# Default: none
#LIVE_HTTPPROXY=""
# What distribution are we going to use?
# Default: unstable
#LIVE_DISTRIBUTION="unstable"
# What sections are we going to use?
# Default: main
#LIVE_SECTIONS="main contrib non-free"
# What packages do we want to install in *addition* to the flavour?
# Default: none
LIVE_PACKAGES="less locales screen sudo vim"
# What boot parameters do we want to give to the kernel?
# Default: none
#LIVE_BOOTAPPEND=""
# What IP address or hostname is assigned to the netboot server?
# Default: none
LIVE_SERVER_ADDRESS="192.168.1.1"
# Where is the chroot on the netboot server?
# Default: none
LIVE_SERVER_PATH="/srv/debian-live/chroot"
# Which filesystem should be used for the rootfs image (squashfs/ext2)?
# Default: squashfs
#LIVE_FILESYSTEM="squashfs"
# Which command should be executed in the chroot before mastering the image?
# Default: none
#LIVE_HOOK=""
# Which file or directory should be copied into the rootfs?
# Default: none
#LIVE_INCLUDE_ROOTFS=""
# Which file or directory should be copied into the image?
# Default: none
#LIVE_INCLUDE_IMAGE=""
# Which preseed file should be used for configuring packages ?
# Default: none
#LIVE_PRESEED=""
# Does splashy should be installed and configured for live system?
# Default: no
#LIVE_SPLASHY=""
#LIVE_SPLASHY_THEME=""
# Which architecture should we install for ?
# Default: auto detected
#LIVE_ARCHITECTURE=""
# Which file contains package list we would like to use for install ?
# Default: LIST option specified as last argument in command line
#LIVE_PACKAGE_LIST=""
# Which directory should be used for templates ?
# Default: "/usr/share/make-live/templates"
#LIVE_TEMPLATES=""

119
make-live.conf.8 Normal file
View File

@ -0,0 +1,119 @@
.TH MAKE-LIVE.CONF 8 "Jul, 17 2006 "0.99" "make-live configuration"
.SH NAME
make-live.conf \- make-live configuration file.
.SH DESCRIPTION
The Debian Live framework lets you automagically create live system images.
.PP
.SH ENVIRONMENT
Note that environment variables are overwritten, if they are set in the
configuration file at /etc/make-live.conf.
.TP
.B LIVE_ARCHITECTURE
specifies the build root (Default: `pwd`/live).
.TP
.B LIVE_BOOTAPPEND
specifies additional bootparameters to the kernel (Default: none).
.TP
.B LIVE_CONFFILE
specifies alternative configuration file.
.TP
.B LIVE_CLONE
.TP
.B LIVE_DISTRIBUTION
specifies which distribution will be used (Default: unstable).
.TP
.B LIVE_DEBUG
enables debug output.
.TP
.B LIVE_FILESYSTEM
specifies the filesystem to be used for the root filesystem image
(Default: squashfs).
.TP
.B LIVE_FLAVOUR
specifies the bootstrap flavour, either standard (default) or minimal.
.TP
.B LIVE_FTPPROXY
specifies your ftp_proxy you want to use inside the chroot (Default: none).
.TP
.B LIVE_HOOK
specifies a command to be executed inside the chroot before mastering the
image (Default: none).
.TP
.B LIVE_HTTPPROXY
specifies your http_proxy you want to use inside the chroot (Default: none).
.TP
.B LIVE_INCLUDE_IMAGE
specifies a file or directory which should be copied into the image
(Default: none).
.TP
.B LIVE_INCLUDE_ROOTFS
specifies a file or directory which should be copied into the to root filesystem
(Default: none).
.TP
.B LIVE_LINUX_FLAVOUR
specifies the linux-image flavour.
.TP
.B LIVE_LOGFILE
specifies the location of the logfile (Default: $LIVE_ROOT/make-live.log).
.TP
.B LIVE_MIRROR
specifies the used Debian mirror (Default: http://ftp.debian.org/debian).
.TP
.B LIVE_MIRROR_KEY
specifies the public key of the used Debian mirror (Default: none).
.TP
.B LIVE_PACKAGE_LIST
specifies a file which contains a list of packages to install, separated by
newlines, if LIVE_PACKAGE_LIST exists, default LIST option will be ignored.
.TP
.B LIVE_PACKAGES
specifies additional packages to install (Default: none).
.TP
.B LIVE_PRESEED
specifies a preseed file useful for configuring packages
(Default: none).
.TP
.B LIVE_REPOSITORY
specifies another repository used (Default: none).
.TP
.B LIVE_REPOSITORY_KEY
speficies the public key of the other repository (Default: none).
.TP
.B LIVE_SECTIONS
specifies which sections will be available (Default: main).
.TP
.B LIVE_SERVER_ADDRESS
specifies the IP address or hostname of the netboot server (Default: none).
.TP
.B LIVE_SERVER_PATH
specifies the directory of the chroot on the netboot server (Default: none).
.TP
.B LIVE_SPLASHY
specifies that splashy should be installed and initramfs patched
(Default: no).
.TP
.B LIVE_SPLASHY_THEME
if LIVE_SPLASHY exists this could be used to select a theme as the default
splashy theme, could also install external .tar.gz splashy themes specified
with file name without extension and in the current directory.
(Default: none).
.TP
.B LIVE_TEMPLATES
specifies a directory to be used for templates instead of the default one.
(Default: "/usr/share/make-live/templates")
.SH BUGS
.B make-live
works fully on amd64 and i386, partially on alpha, hppa, ia64, mips, mipsel,
powerpc, s390 and sparc. Other architectures, such as arm and m68k, as well as
non-linux ports of Debian, like hurd-i386, are currently not supported.
.SH HOMEPAGE
Debian Live project <http://live.debian.net/>
.SH AUTHOR
make-live was written by Daniel Baumann <daniel@debian.org> and Marco Amadori
<marco.amadori@gmail.com>.

283
make-live.sh Executable file
View File

@ -0,0 +1,283 @@
#!/bin/sh
# make-live - An utility for building Debian Live systems.
#
# Copyright (C) 2006 Daniel Baumann <daniel@debian.org>
# Copyright (C) 2006 Marco Amadori <marco.amadori@gmail.com>
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
set -e
PROGRAM="`basename ${0}`"
VERSION="0.99"
# Source default configuration
if [ -r /etc/make-live.conf ]
then
. /etc/make-live.conf
fi
# Source alternate configuration
if [ ! -z "${LIVE_CONFFILE}" ]
then
if [ -r "${LIVE_CONFFILE}" ]
then
. "${LIVE_CONFFILE}"
else
echo "W: could not read ${LIVE_CONFFILE}, using defaults."
fi
fi
# Source scriptlets
for SCRIPT in /usr/share/make-live/scripts/*.sh
do
. "${SCRIPT}"
done
Help ()
{
echo "make-live - An utility for building Debian Live systems."
echo
echo "Usage: ${PROGRAM} [-a ARCHITECTURE] [-c FILE] [--clone DIRECTORY] [-d DISTRIBUTION] [--debug] [-f FILESYSTEM] [--flavour FLAVOUR] [--hook \"COMMAND...\"] [--include-image FILE|DIRECTORY] [--include-rootfs FILE|DIRECTORY] [--linux-image FLAVOUR] [--logfile FILE] [-p|--package-list FILE] [--preseed FILE] [--rootfs DIRECTORY] [-s|--section \"SECTION...\"] [--splashy [THEME]] [-t|--type TYPE] [--templates DIRECTORY] [--verbose] [LIST]"
echo
echo "Values:"
echo " Architectures: alpha, amd64, arm, hppa, i386, ia64, m68k, powerpc, s390, sparc."
echo " Distributions: oldstable, stable, testing, unstable."
echo " Filesystems: ext2, squashfs, xfs."
echo " Flavours: bootable, build, minimal, standard."
echo " Linux Images: alpha-generic, alpha-smp, alpha-legacy, amd64-k8, amd64-k8-smp, em64t-p4, em64t-p4-smp, footbridge, ixp4xx, nslu2, rpc, s3c2410, parisc, parisc-smp, parisc64, parisc64-smp, 486, 686, k7, itanium, itanium-smp, mckinley, mckinley-smp, amiga, mac, r4k-ip22, r5k-ip32, sb1-bcm91250a, sb1a-bcm91480b, r5k-cobalt, r3k-kn02, r4k-kn04, powerpc, powerpc-smp, powerpc-miboot, powerpc64, s390, s390x, sparc32, sparc64, sparc64-smp."
echo " Sections: main, contrib, non-free."
echo " Types: iso, net."
echo " Lists: gnome, gnome-core, gnome-full, kde, kde-core, kde-core-i18n, kde-extra, kde-extra-i18n, kde-full, kde-full-i18n, kde-18n, standard-i18n, x11, x11-core, xfce."
echo
echo "Options:"
echo " -h, --help: display this help and exit."
echo " -u, --usage: show usage and exit."
echo " -v, --version: output version information and exit."
echo
echo "Environment:"
echo " All settings can also be done through environment variables. Please see make-live.conf(8) for more information."
echo
echo "Report bugs to Debian Live project <http://live.debian.net>."
exit 1
}
Usage ()
{
echo "make-live - An utility for building Debian Live systems."
echo
echo "Usage: ${PROGRAM} [-a ARCHITECTURE] [-c FILE] [--clone DIRECTORY] [-d DISTRIBUTION] [--debug] [-f FILESYSTEM] [--flavour FLAVOUR] [--hook "COMMAND..."] [--include-image FILE|DIRECTORY] [--include-rootfs FILE|DIRECTORY] [--linux-image FLAVOUR] [--logfile FILE] [-p|--package-list FILE] [--preseed FILE] [--rootfs DIRECTORY] [-s|--section "SECTION..."] [--splashy [THEME]] [-t|--type TYPE] [--templates DIRECTORY] [--verbose] [LIST]"
echo
echo "Try \"${PROGRAM} --help\" for more information."
exit 1
}
Version ()
{
echo "make-live, version ${VERSION}"
echo
echo "Copyright (C) 2006 Daniel Baumann <daniel@debian.org>"
echo "Copyright (C) 2006 Marco Amadori <marco.amadori@gmail.com>"
echo
echo "This program is free software; you can redistribute it and/or modify"
echo "it under the terms of the GNU General Public License as published by"
echo "the Free Software Foundation; either version 2 of the License, or"
echo "(at your option) any later version."
echo
echo "This program is distributed in the hope that it will be useful,"
echo "but WITHOUT ANY WARRANTY; without even the implied warranty of"
echo "MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the"
echo "GNU General Public License for more details."
echo
echo "Homepage: Debian Live project <http://live.debian.net/>"
exit 1
}
Main ()
{
ARGUMENTS=`getopt --shell=sh --name="${PROGRAM}" \
--options="a:c:d:f:p:s:t:huv" \
--longoptions="architecture:,conffile:,clone:,distribution:,debug,filesystem:,flavour:,hook:,include-image:,include-rootfs:,linux-image:,logfile:,package-list:,preseed:,rootfs:,section:,splashy::,type:,templates:,verbose" \
-- "${@}"`
if [ "${?}" != "0" ]
then
echo "Terminating..." >&2
exit 1
fi
eval set -- "${ARGUMENTS}"
while true
do
case "${1}" in
-a|--architecture)
LIVE_ARCHITECTURE="${2}"; shift 2
;;
-c|--conffile)
LIVE_CONFIG="${2}"; shift 2
;;
--clone)
LIVE_CLONE="${2}"; shift 2
;;
-d|--distribution)
LIVE_DISTRIBUTION="${2}"; shift 2
;;
--debug)
LIVE_DEBUG="1"
LIVE_VERBOSE="1"; shift
;;
-f|--filesystem)
LIVE_FILESYSTEM="${2}"; shift 2
;;
--flavour)
LIVE_FLAVOUR="${2}"; shift 2
;;
--hook)
LIVE_HOOK="${2}"; shift 2
;;
--include-image)
LIVE_INCLUDE_IMAGE="${2}"; shift 2
;;
--include-rootfs)
LIVE_INCLUDE_ROOTFS="${2}"; shift 2
;;
--linux-image)
LIVE_LINUX="${2}"; shift 2
;;
--logfile)
LIVE_LOGFILE="${2}"; shift 2
;;
-p|--package-list)
LIVE_PACKAGE_LIST="${2}"; shift 2
;;
--preseed)
LIVE_PRESEED="${2}"; shift 2
;;
--rootfs)
LIVE_ROOTFS="${2}"; shift 2
;;
-s|--section)
LIVE_SECTIONS="${2}"; shift 2
;;
--splashy)
LIVE_SPLASHY="1"
case "${2}" in
"")
shift 2;
;;
*)
LIVE_SPLASHY_THEME=${2} ; shift 2
;;
esac
;;
-t|--type)
LIVE_TYPE="${2}"; shift 2
;;
--templates)
LIVE_TEMPLATES="${2}"; shift 2
;;
--verbose)
LIVE_VERBOSE="1"; shift
;;
-h|--help)
Help; shift
;;
-u|--usage)
Usage; shift
;;
-v|--version)
Version; shift
;;
--)
shift; break
;;
*)
echo "Internal error!"
exit 1
;;
esac
done
LIVE_LIST="${1}"
# Enabling debug
if [ "${LIVE_DEBUG}" ]
then
set +x
fi
# Setting defaults
Defaults
# Initial checks
Init
# Bootstrap chroot
Bootstrap
# Customize chroot
Chroot
# Create type
if [ "${LIVE_TYPE}" ]
then
case ${LIVE_TYPE} in
iso)
LIVE_TYPE="Iso"
;;
net)
LIVE_TYPE="Net"
;;
*)
echo "You specified a wrong image type"
Help
;;
esac
${LIVE_TYPE}
else
Iso
fi
}
Main "${@}"

125
scripts/00-defaults.sh Normal file
View File

@ -0,0 +1,125 @@
# scripts/00-defaults.sh
Defaults ()
{
# Set architecture name
if [ -z "${LIVE_ARCHITECTURE}" ]
then
LIVE_ARCHITECTURE="`dpkg-architecture -qDEB_BUILD_ARCH`"
fi
# Set build directory
if [ -z "${LIVE_ROOT}" ]
then
LIVE_ROOT="`pwd`/live"
fi
# Set rootfs directory
if [ -d "${LIVE_ROOTFS}" ]
then
LIVE_CHROOT="${LIVE_ROOTFS}"
else
LIVE_CHROOT="${LIVE_ROOT}/chroot"
fi
# Set distribution name
if [ -z "${LIVE_DISTRIBUTION}" ]
then
LIVE_DISTRIBUTION="unstable"
fi
# Set bootstrap flavour
if [ -z "${LIVE_FLAVOUR}" ]
then
LIVE_FLAVOUR="standard"
fi
# Set linux-image flavour
if [ -z "${LIVE_LINUX}" ]
then
case "${LIVE_ARCHITECTURE}" in
alpha)
LIVE_LINUX="alpha-generic"
;;
amd64)
LIVE_LINUX="amd64-generic"
;;
arm)
echo "E: You need to specify the linux flavour."
exit 1
;;
hppa)
LIVE_LINUX="parisc"
;;
i386)
LIVE_LINUX="486"
;;
ia64)
LIVE_LINUX="itanium"
;;
m68k)
echo "E: You need to specify the linux flavour."
exit 1
;;
powerpc)
LIVE_LINUX="powerpc"
;;
s390)
LIVE_LINUX="s390"
;;
sparc)
LIVE_LINUX="sparc32"
;;
*)
echo "FIXME: Architecture not yet supported."
exit 1
;;
esac
fi
# Set logfile
if [ -z "${LIVE_LOGFILE}" ]
then
LIVE_LOGFILE="${LIVE_ROOT}/make-live.log"
fi
# Set mirror server
if [ -z "${LIVE_MIRROR}" ]
then
LIVE_MIRROR="http://ftp.debian.org/debian"
fi
# Set package list
if [ -z "${LIVE_PACKAGE_LIST}" ] && [ ! -z "${LIVE_LIST}" ]
then
LIVE_PACKAGE_LIST="/usr/share/make-live/lists/${LIVE_LIST}"
fi
# Set sections names
if [ -z "${LIVE_SECTIONS}" ]
then
LIVE_SECTIONS="main"
fi
# Set templates directory
if [ ! -z "${LIVE_TEMPLATES}" ]
then
if [ ! -d "${LIVE_TEMPLATES}" ]
then
echo "E: ${LIVE_TEMPLATES} is not a directory."
exit 1
fi
else
LIVE_TEMPLATES="/usr/share/make-live/templates"
fi
}

18
scripts/00-init.sh Normal file
View File

@ -0,0 +1,18 @@
# scripts/00-init.sh
Init ()
{
# Check if user is root
if [ "`id -u`" -ne "0" ]
then
echo "E: ${PROGRAM} requires superuser privilege."
exit 1
fi
# Check if build directory already exists
if [ -d "${LIVE_ROOT}" ] && [ ! -d "${LIVE_ROOTFS}" ]
then
echo "E: found an (unfinished) system, remove it and re-run ${PROGRAM}."
exit 1
fi
}

43
scripts/01-bootstrap.sh Normal file
View File

@ -0,0 +1,43 @@
# scripts/01-bootstrap.sh
Bootstrap ()
{
if [ -z "${LIVE_ROOTFS}" ]
then
# Create chroot directory
mkdir -p "${LIVE_CHROOT}"
if [ -z "${LIVE_VERBOSE}" ]
then
if [ -x /usr/bin/cdebootstrap ]
then
# Bootstrap with cdebootstrap
cdebootstrap --arch="${LIVE_ARCHITECTURE}" \
--flavour="${LIVE_FLAVOUR}" \
"${LIVE_DISTRIBUTION}" \
"${LIVE_CHROOT}" "${LIVE_MIRROR}"
elif [ -x /usr/sbin/debootstrap ]
then
# Bootstrap with debootstrap
debootstrap --arch="${LIVE_ARCHITECTURE}" \
"${LIVE_DISTRIBUTION}" \
"${LIVE_CHROOT}" "${LIVE_MIRROR}"
fi
else
if [ -x /usr/bin/cdebootstrap ]
then
# Bootstrap with cdebootstrap (debug)
cdebootstrap --arch="${LIVE_ARCHITECTURE}" \
--debug --flavour="${LIVE_FLAVOUR}" \
"${LIVE_DISTRIBUTION}" \
"${LIVE_CHROOT}" "${LIVE_MIRROR}"
elif [ -x /usr/sbin/debootstrap ]
then
# Bootstrap with debootstrap (debug)
debootstrap --arch="${LIVE_ARCHITECTURE}" \
--verbose "${LIVE_DISTRIBUTION}" \
"${LIVE_CHROOT}" "${LIVE_MIRROR}"
fi
fi
fi
}

169
scripts/01-chroot.sh Normal file
View File

@ -0,0 +1,169 @@
# scripts/01-chroot.sh
chroots ()
{
# Execute commands chrooted
chroot "${LIVE_CHROOT}" /usr/bin/env -i HOME="/root" \
PATH="/usr/sbin:/usr/bin:/sbin:/bin" TERM="${TERM}" \
ftp_proxy="${LIVE_FTPPROXY}" http_proxy="${LIVE_HTTPPROXY}" \
DEBIAN_PRIORITY="critical" ${1}
#DEBIAN_FRONTEND=non-interactive DEBIAN_PRIORITY=critical
# FIXME: setting DEBIAN_FRONTEND to non-interactive seems not to work.
}
Chroot ()
{
# Configure chroot
Patch_chroot apply
# Configure network
Patch_network apply
# Configure /etc/apt/sources.list
echo "deb ${LIVE_MIRROR} ${LIVE_DISTRIBUTION} ${LIVE_SECTIONS}" > \
"${LIVE_CHROOT}"/etc/apt/sources.list
chroots "apt-get update"
# Install gnupg
chroots "apt-get install --yes --force-yes gnupg wget"
# Import archive signing key
if [ ! -z "${LIVE_MIRROR_KEY}" ]
then
chroots "wget ${LIVE_MIRROR_KEY}"
chroots "apt-key add `basename ${LIVE_MIRROR_KEY}`"
chroots "rm -f `basename ${LIVE_MIRROR_KEY}`"
fi
# Add other repository
if [ ! -z "${LIVE_REPOSITORY}" ]
then
# Configure /etc/apt/sources.list
echo "deb ${LIVE_REPOSITORY}" >> \
"${LIVE_CHROOT}"/etc/apt/sources.list
# Import archive signing key
if [ ! -z "${LIVE_REPOSITORY_KEY}" ]
then
chroots "wget ${LIVE_REPOSITORY_KEY}"
chroots "apt-key add `basename ${LIVE_REPOSITORY_KEY}`"
chroots "rm -f `basename ${LIVE_REPOSITORY_KEY}`"
fi
fi
# Update indices
chroots "apt-get update"
# Configure linux-image
Patch_linuximage apply
# Install linux-image
chroots "apt-get install --yes linux-image-2.6-${LIVE_LINUX}"
chroots "apt-get install --yes --force-yes casper \
squashfs-modules-2.6-${LIVE_LINUX} \
unionfs-modules-2.6-${LIVE_LINUX}"
# Rebuild initial ramdisk
chroots "dpkg-reconfigure `basename ${LIVE_CHROOT}/var/lib/dpkg/info/linux-image-2.6.*-${LIVE_LINUX}.postinst .postinst`"
# Deconfigure linux-image
Patch_linuximage deapply
# --- Begin FIXME ---
if [ -d "${LIVE_CLONE}" ]
then
# swapping chroots
LIVE_TMP="${LIVE_CHROOT}"
LIVE_CHROOT="${LIVE_CLONE}"
# get info
chroots "apt-get install --yes debconf-utils"
chroots "debconf-get-selections" > "${LIVE_ROOT}"/preseed.cloned
chroots "dpkg --get-selections" | grep -v deinstall | cut -f1 > "${LIVE_ROOT}"/package-list.cloned
# swapping out
LIVE_CHROOT="${LIVE_TMP}"
LIVE_PRESEED="${LIVE_ROOT}"/preseed.cloned
LIVE_PACKAGE_LIST="${LIVE_ROOT}"/package-list.cloned
fi
if [ -f "${LIVE_PRESEED}" ]
then
chroots "apt-get install --yes debconf-utils"
cp ${LIVE_PRESEED} ${LIVE_CHROOT}/tmp/preseed
chroots "debconf-set-selections /tmp/preseed"
rm ${LIVE_CHROOT}/tmp/preseed
fi
if [ -z "${LIVE_ROOTFS}" ]
then
# Install packages list
if [ ! -z "${LIVE_PACKAGE_LIST}" ]
then
chroots "apt-get install --yes `cat ${LIVE_PACKAGE_LIST}`"
fi
# Install extra packages
if [ ! -z "${LIVE_PACKAGES}" ]
then
chroots "apt-get install --yes ${LIVE_PACKAGES}"
fi
fi
# Copy external path into the chroot
if [ -d "${LIVE_INCLUDE_ROOTFS}" ]
then
cd "${LIVE_INCLUDE_ROOTFS}"
find . | cpio -pumd "${LIVE_CHROOT}"/
cd "${OLDPWD}"
fi
# Execute extra command in the chroot
if [ ! -z "${LIVE_HOOK}" ]
then
chroots "${LIVE_HOOK}"
fi
# Add splashy and conditionally a theme
if [ ! -z "${LIVE_SPLASHY}" ]
then
chroots "apt-get install --yes splashy splashy-themes"
if [ ! -z "${LIVE_SPLASHY_THEME}" ]
then
# not already installed ? Then its a new theme to install!
if [ ! -d "${LIVE_CHROOT}"/etc/splashy/themes/"${LIVE_SPLASHY_THEME}" ]
then
if [ -f "${LIVE_SPLASHY_THEME}".tar.gz ]
then
cp "${LIVE_SPLASHY_THEME}".tar.gz "${LIVE_CHROOT}"/tmp/"${LIVE_SPLASHY_THEME}".tar.gz # this permits simlink to theme
chroots "splashy_config -i /tmp/${LIVE_SPLASHY_THEME}.tar.gz"
rm "${LIVE_CHROOT}"/tmp/"${LIVE_SPLASHY_THEME}".tar.gz
chroots "splashy_config -s ${LIVE_SPLASHY_THEME}"
else
echo "Specify the local splashy theme without extension, it also must be in the cwd"
fi
else
chroots "splashy_config -s ${LIVE_SPLASHY_THEME}"
fi
fi
fi
# --- End FIXME ---
# Clean apt packages cache
rm -f "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb
rm -f "${LIVE_CHROOT}"/var/cache/apt/archives/partial/*.deb
# Clean apt indices cache
rm -f "${LIVE_CHROOT}"/var/cache/apt/*pkgcache.bin
# Remove cdebootstrap packages cache
rm -rf "${LIVE_CHROOT}"/var/cache/bootstrap
# Deconfigure network
Patch_network deapply
# Deconfigure chroot
Patch_chroot deapply
}

91
scripts/01-patch.sh Normal file
View File

@ -0,0 +1,91 @@
# scripts/01-patches.sh
Patch_chroot ()
{
# Some maintainer scripts can detect if they are in a chrooted system.
# Therefore, we create the corresponding file.
case "${1}" in
apply)
# Create chroot file
echo "live" > "${LIFE_CHROOT}"/etc/debian_chroot
;;
deapply)
# Remove chroot file
rm -f "${LIVE_CHROOT}"/etc/debian_chroot
;;
esac
}
Patch_network ()
{
# Packages which are manually installed inside the chroot are installed
# from the network. Therefore, we need to be able to resolv hosts.
case "${1}" in
apply)
# Save host lookup table
if [ -f "${LIVE_CHROOT}"/etc/hosts ]
then
cp "${LIVE_CHROOT}"/etc/hosts \
"${LIVE_CHROOT}"/etc/hosts.orig
fi
# Save resolver configuration
if [ -f "${LIVE_CHROOT}"/etc/resolv.conf ]
then
cp "${LIVE_CHROOT}"/etc/resolv.conf \
"${LIVE_CHROOT}"/etc/resolv.conf.orig
fi
# Copy host lookup table
if [ -f /etc/hosts ]
then
cp /etc/hosts "${LIVE_CHROOT}"/etc/hosts
fi
# Copy resolver configuration
if [ -f /etc/resolv.conf ]
then
cp /etc/resolv.conf \
"${LIVE_CHROOT}"/etc/resolv.conf
fi
;;
deapply)
# Restore host lookup table
if [ -f "${LIVE_CHROOT}"/etc/hosts.orig ]
then
mv "${LIVE_CHROOT}"/etc/hosts.orig \
"${LIVE_CHROOT}"/etc/hosts
fi
# Restore resolver configuration
if [ -f "${LIVE_CHROOT}"/etc/resolv.conf.orig ]
then
mv "${LIVE_CHROOT}"/etc/resolv.conf.orig \
"${LIVE_CHROOT}"/etc/resolv.conf
fi
;;
esac
}
Patch_linuximage ()
{
# The linux-image package asks interactively for initial ramdisk
# creation. Therefore, we preconfigure /etc/kernel-img.conf.
case "${1}" in
apply)
# Write configuration option
echo "do_initrd = Yes" >> \
"${LIVE_CHROOT}"/etc/kernel-img.conf
;;
deapply)
# Remove configuration file
rm -f "${LIVE_CHROOT}"/etc/kernel-img.conf
;;
esac
}

145
scripts/02-image.sh Normal file
View File

@ -0,0 +1,145 @@
# scripts/02-image.sh
md5sums ()
{
# Calculating md5sums
cd "${LIVE_ROOT}"/image
find . -type f -print0 | xargs -0 md5sum > "${LIVE_ROOT}"/md5sum.txt
cd "${OLDPWD}"
if [ -d "${LIVE_INCLUDE_IMAGE}" ]
then
cd "${LIVE_INCLUDE_IMAGE}"
find . -type f -print0 | xargs -0 md5sum >> \
"${LIVE_ROOT}"/md5sum.txt
cd "${OLDPWD}"
fi
mv "${LIVE_ROOT}"/md5sum.txt "${LIVE_ROOT}"/image
}
mkisofss ()
{
if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ]
then
# Create image
if [ -z "${LIVE_VERBOSE}" ]
then
mkisofs -quiet -A "Debian Live" -p "Debian Live; http://live.debian.net/; live@lists.debian-unofficial.org" -publisher "Debian Live; http://live.debian.net/; live@lists.debian-unofficial.org" -o "${LIVE_ROOT}"/image.iso -r -J -l -V "Debian Live `date +%Y%m%d`" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table "${LIVE_ROOT}"/image ${LIVE_INCLUDE_IMAGE}
else
mkisofs -A "Debian Live" -p "Debian Live; http://live.debian.net/; live@lists.debian-unofficial.org" -publisher "Debian Live; http://live.debian.net/; live@lists.debian-unofficial.org" -o "${LIVE_ROOT}"/image.iso -r -J -l -V "Debian Live `date +%Y%m%d`" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table "${LIVE_ROOT}"/image ${LIVE_INCLUDE_IMAGE}
fi
else
echo "FIXME: Bootloader on your architecture not yet supported (Continuing in 5 seconds)."
sleep 5
if [ -z "${LIVE_VERBOSE}" ]
then
# Create image
mkisofs -quiet -o "${LIVE_ROOT}"/image.iso -r -J -l -V "Debian Live `date +%Y%m%d`" "${LIVE_ROOT}"/image ${LIVE_INCLUDE_IMAGE}
else
# Create image (debug)
mkisofs -o "${LIVE_ROOT}"/image.iso -r -J -l -V "Debian Live `date +%Y%m%d`" "${LIVE_ROOT}"/image ${LIVE_INCLUDE_IMAGE}
fi
fi
}
Linuximage ()
{
case "${1}" in
iso)
# Copy linux-image
cp "${LIVE_CHROOT}"/boot/vmlinuz-* \
"${LIVE_ROOT}"/image/isolinux/vmlinuz
cp "${LIVE_CHROOT}"/boot/initrd.img-* \
"${LIVE_ROOT}"/image/isolinux/initrd.gz
;;
net)
# Copy linux-image
cp "${LIVE_ROOT}"/chroot/boot/vmlinuz-* \
"${LIVE_ROOT}"/tftpboot/vmlinuz
cp "${LIVE_ROOT}"/chroot/boot/initrd.img-* \
"${LIVE_ROOT}"/tftpboot/initrd.gz
;;
esac
}
Memtest ()
{
if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ]
then
# Install memtest
Patch_network apply
chroots "apt-get install --yes memtest86+"
case "$1" in
iso)
# Copy memtest
cp "${LIVE_ROOT}"/chroot/boot/memtest86+.bin \
"${LIVE_ROOT}"/image/isolinux/memtest
;;
net)
# Copy memtest
cp "${LIVE_ROOT}"/chroot/boot/memtest86+.bin \
"${LIVE_ROOT}"/tftpboot/memtest
;;
esac
# Remove memtest
chroots "apt-get remove --purge --yes memtest86+"
Patch_network deapply
fi
}
Syslinux ()
{
if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ]
then
# Install syslinux
Patch_network apply
chroots "apt-get install --yes syslinux"
case "${1}" in
iso)
# Copy syslinux
mkdir -p "${LIVE_ROOT}"/image/isolinux
cp "${LIVE_CHROOT}"/usr/lib/syslinux/isolinux.bin "${LIVE_ROOT}"/image/isolinux
# Install syslinux templates
cp -a "${LIVE_TEMPLATES}"/syslinux/* \
"${LIVE_ROOT}"/image/isolinux
rm -f "${LIVE_ROOT}"/image/isolinux/pxelinux.cfg
# Configure syslinux templates
sed -i -e "s#LIVE_BOOTAPPEND#${LIVE_BOOTAPPEND}#" "${LIVE_ROOT}"/image/isolinux/isolinux.cfg
sed -i -e "s/LIVE_DATE/`date +%Y%m%d`/" "${LIVE_ROOT}"/image/isolinux/f1.txt
sed -i -e "s/LIVE_VERSION/${VERSION}/" "${LIVE_ROOT}"/image/isolinux/f10.txt
;;
net)
# Copy syslinux
mkdir -p "${LIVE_ROOT}"/tftpboot
cp "${LIVE_ROOT}"/chroot/usr/lib/syslinux/pxelinux.0 "${LIVE_ROOT}"/tftpboot
# Install syslinux templates
mkdir -p "${LIVE_ROOT}"/tftpboot/pxelinux.cfg
cp -a "${LIVE_TEMPLATES}"/syslinux/* \
"${LIVE_ROOT}"/tftpboot/pxelinux.cfg
mv "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/pxelinux.cfg "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/default
rm -f "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/isolinux.*
# Configure syslinux templates
sed -i -e "s/LIVE_SERVER_ADDRESS/${LIVE_SERVER_ADDRESS}/" -e "s#LIVE_SERVER_PATH#${LIVE_SERVER_PATH}#" -e "s#LIVE_BOOTAPPEND#${LIVE_BOOTAPPEND}#" "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/default
sed -i -e "s/LIVE_DATE/`date +%Y%m%d`/" "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/f1.txt
sed -i -e "s/LIVE_VERSION/${VERSION}/" "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/f10.txt
;;
esac
# Remove syslinux
chroots "apt-get remove --purge --yes syslinux"
Patch_network deapply
fi
}

46
scripts/02-iso.sh Normal file
View File

@ -0,0 +1,46 @@
# scripts/02-iso.sh
Iso ()
{
mkdir -p "${LIVE_ROOT}"/image/casper
if [ "${LIVE_FILESYSTEM}" = "ext2" ]
then
DU_DIM="`du -ks ${LIVE_CHROOT} | cut -f1`"
REAL_DIM="`expr ${DU_DIM} + ${DU_DIM} / 20`" # Just 5% more to be sure, need something more sophistcated here...
genext2fs --size-in-blocks=${REAL_DIM} --reserved-blocks=0 \
\--root="${LIVE_CHROOT}" \
"${LIVE_ROOT}"/image/casper/filesystem.ext2
else
if [ -f "${LIVE_ROOT}"/image/casper/filesystem.squashfs ]
then
rm "${LIVE_ROOT}"/image/casper/filesystem.squashfs
fi
if [ -z "${LIVE_VERBOSE}" ]
then
mksquashfs "${LIVE_CHROOT}" "${LIVE_ROOT}"/image/casper/filesystem.squashfs
else
mksquashfs -info "${LIVE_CHROOT}" "${LIVE_ROOT}"/image/casper/filesystem.squashfs
fi
fi
# Installing syslinux
Syslinux iso
# Installing linux-image
Linuximage iso
# Installing memtest
Memtest iso
# Installing templates
cp -a "${LIVE_TEMPLATES}"/iso/* "${LIVE_ROOT}"/image
# Calculating md5sums
md5sums
# Creating image
mkisofss
}

38
scripts/02-net.sh Normal file
View File

@ -0,0 +1,38 @@
# scripts/02-net.sh
Net ()
{
# Installing smbfs
chroots "apt-get install --yes smbfs"
if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ]
then
# Configuring initramfs for NFS
cat >> "${LIVE_ROOT}"/chroot/etc/mkinitramfs/initramfs.conf << EOF
MODULES=netboot
BOOT=nfs
EOF
fi
# Installing syslinux
Syslinux net
# Installing linux-image
Linuximage net
# Installing memtest
Memtest net
if [ -z "${LIVE_VERBOSE}" ]
then
# Creating tarball
cd "${LIVE_ROOT}" && cd .. && \
tar cfz netboot.tar.gz "${LIVE_ROOT}" && \
mv netboot.tar.gz "${LIVE_ROOT}"
else
# Creating tarball (debug)
cd "${LIVE_ROOT}" && cd .. && \
tar cfvz netboot.tar.gz "${LIVE_ROOT}" && \
mv netboot.tar.gz "${LIVE_ROOT}"
fi
}

660
templates/iso/README.html Normal file
View File

@ -0,0 +1,660 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<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">
</head>
<body text="#000000" bgcolor="#FFFFFF" link="#0000FF" vlink="#800080" alink="#FF0000">
<!-- The HTML and TEXT file are NOT the actual source code. -->
<!-- For that, see http://svn.debian.org/wsvn/debian-cd -->
<div align=right>
(<a href="README.txt">Text version</a>)
</div>
<table border="0" cellpadding="3" cellspacing="0" align="center" summary="">
<tr>
<td>
<img src="pics/logo-50.jpg" border="0" hspace="0" vspace="0" alt="" width="50" height="61">
<img src="pics/debian.jpg" border="0" hspace="0" vspace="0" alt="Debian" width="179" height="61">
</td>
</tr>
</table>
<table bgcolor="#DF0451" border="0" cellpadding="0" cellspacing="0"
width="100%" summary="">
<tr>
<td valign="top">
<img src="pics/red-upperleft.png" align="left" border="0" hspace="0"
vspace="0" alt="" width="15" height="16">
</td>
<td rowspan="2" align="center">
<table align="center" border="0" cellpadding="2" cellspacing="0">
<tr><td bgcolor="#000084">
<div align="center"><font color="#FFFFFF" face="helvetica,arial"><B>&nbsp;&nbsp;
Debian GNU/Linux testing "Etch" - Official Snapshot i386 Binary-1 CD
&nbsp;&nbsp;</B></font></div>
</td></tr>
</table>
</td>
<td valign="top">
<img src="pics/red-upperright.png" align="right" border="0" hspace="0"
vspace="0" alt="" width="16" height="16">
</td>
</tr>
<tr>
<td valign="bottom">
<img src="pics/red-lowerleft.png" align="left" border="0" hspace="0"
vspace="0" alt="" width="16" height="16">
</td>
<td valign="bottom">
<img src="pics/red-lowerright.png" align="right" border="0" hspace="0"
vspace="0" alt="" width="15" height="16">
</td>
</tr>
</table>
<table border="0" cellpadding="2" cellspacing="0" width="100%" summary="">
<tr>
<td></td>
</tr>
</table>
<table border="0" cellpadding="0" cellspacing="0" width="100%" summary="">
<tr>
<td colspan="3" valign="top" width="20%" bgcolor="#BBDDFF">
<img src="pics/blue-upperleft.png" align="left" border="0"
hspace="0" vspace="0" alt="" width="16" height="16">
<img src="pics/blue-upperright.png" align="right" border="0"
hspace="0" vspace="0" alt="" width="16" height="16">
</td>
</tr>
<tr>
<td bgcolor="#BBDDFF">&nbsp;&nbsp;</td>
<td valign="TOP" bgcolor="#BBDDFF">
<font face="Arial,Helvetica">
<P><B><A href="http://www.debian.org/">Debian home&nbsp;page</A></B></P>
&nbsp;<br>
<P>
<A href="#intro">Intro</A>
<P>
<A href="#thiscd">About This CD</A>
<P>
<A href="#install">Installing</A>
<P>
<A href="#lastmin">Last-Minute Notes</A>
<P>
<A href="#apt">Using CDs with apt</A>
<P>
<A href="#cdmanuf">CD Manufacturers</A>
<P>
<A href="#other">More Information</A>
<P>
&nbsp;<P>
<A href=".">Browse this CD-ROM</A></P>
<P>
<tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</tt>
</P>
</font>
</td>
<td bgcolor="#BBDDFF">&nbsp;&nbsp;</td>
<td>&nbsp;&nbsp;</td>
<td valign="TOP" width="80%">
<div align="center">
<big><big><B><I>
Welcome to the exciting world of
</I></B></big></big>
<br>
<big><big><big><B><I>
Debian GNU/Linux!
</I></B></big></big></big>
</div>
<P><H2><A name="intro">
Intro
</H2>
</a>
<p>
This is one of the CD-ROMs of 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 &quot;freedom&quot;).
<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>
Debian is available for various kinds of computers
(&quot;architectures&quot;), like
&quot;IBM-compatible&quot; PCs (<i>i386</i>),
Compaq's <i>Alpha</i>,
Motorola's 680x0 (<i>m68k</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="thiscd">
About This CD
</H2>
</a>
<p>
This CD-ROM is labeled
<P>
<tt>&nbsp;
Debian GNU/Linux testing "Etch" - Official Snapshot i386 Binary-1
</tt>
<P>
which means that this CD is number 1 of 1 CDs containing
programs ("binaries") for `i386' computers.
<P>
The programs on the Binary CDs are ordered by popularity. The Binary-1 CD
contains the most popular programs and the installation tools; it is possible
to install and run Debian with only the Binary-1 CD. The other CDs, up to
Binary-1, 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 CD 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 CD under
<P>
<tt>&nbsp;
<A href="tools/">/tools/</a>
</tt>
and
<tt>&nbsp;
<A href="install/floppy/">/install/floppy/</a>
</tt>
<P>
For the impatient ones:
you can start the installation program easily by booting off this CD-ROM.
Note that not all (esp. older) systems support this.
<P>
You can also
examine the
<P>
<tt>&nbsp;
<a href="install/">/install</a>
</tt>
<P>
directory; you might be able to start the installation system directly
from there.
<P><HR><P><H2><A name="lastmin">
Last-Minute Notes
</H2>
</a>
<p>
<UL>
<LI>
You should keep in mind that this is an unofficial CD of the current
development version of the Debian system. This means that all sorts of
bugs may be present anywhere in the system.
<br>&nbsp;
</LI>
</UL>
<P><HR><P><H2><A name="apt">
Using Apt
</H2>
</a>
<p>
After installing or upgrading, Debian's packaging system can use CD-ROMs,
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.
<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
<P>
<tt>&nbsp;
apt-get 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.
<P>
Or use aptitude for a full screen interactive selection of available
Debian packages.
<P><HR><P><H2><A name="cdmanuf">
CD Manufacturers
</H2>
</a>
<p>
You are completely free to manufacture and re-distribute CD-ROMs of the
Debian GNU/Linux Operating System, like this one. There is no charge from
us (but of course donations are always welcome).
<P>
For all needed information and contact addresses, please refer to
<P>
<tt>&nbsp;
<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 CD. 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>
<P>
<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>
</tr>
<tr>
<td colspan="3" valign="bottom" width="20%" bgcolor="#BBDDFF">
<img src="pics/blue-lowerleft.png" align="left" border="0"
hspace="0" vspace="0" alt="" width="17" height="16">
<img src="pics/blue-lowerright.png" align="right" border="0"
hspace="0" vspace="0" alt="" width="16" height="16">
</td>
</tr>
</table>
</body>
</html>

746
templates/iso/README.mirrors.html Normal file
View File

@ -0,0 +1,746 @@
<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.&lt;country&gt;.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&nbsp;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 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%">all</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%">all</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%">!hppa !hurd-i386 !s390</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%">all</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%">all</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%">all</td>
</tr>
<tr>
<td width="25%">Czech&nbsp;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%">all</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%">all</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%">all</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%">all</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%">all</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%">all</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%">all</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%">all</td>
</tr>
<tr>
<td width="25%">Great&nbsp;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%">all</td>
</tr>
<tr>
<td width="25%">Hong&nbsp;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%">all</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%">all</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%">all</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%">all</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%">all</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%">all</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%">all</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%">all</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%">all</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%">all</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%">!m68k</td>
</tr>
<tr>
<td width="25%">New&nbsp;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%">all</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%">all</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%">all</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%">all</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%">all</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 i386 ia64 m68k 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%">all</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%">all</td>
</tr>
<tr>
<td width="25%">United&nbsp;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%">!m68k !s390</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/download/pub/linux/debian/debian/">/download/pub/linux/debian/debian/</a> i386
debian.usla.org.ar <a href="http://debian.usla.org.ar/debian/">/debian/</a> 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 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> all
debian.mur.at <a href="ftp://debian.mur.at/debian/">/debian/</a> <a href="http://debian.mur.at/debian/">/debian/</a> 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> all
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> hurd-i386 i386
debian.inode.at <a href="ftp://debian.inode.at/debian/">/debian/</a> <a href="http://debian.inode.at/debian/">/debian/</a> alpha arm i386 m68k 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> all
ftp.au.debian.org <a href="ftp://ftp.au.debian.org/debian/">/debian/</a> <a href="http://ftp.au.debian.org/debian/">/debian/</a> all
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
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> i386
ftp.uwa.edu.au <a href="ftp://ftp.uwa.edu.au/mirrors/linux/debian/">/mirrors/linux/debian/</a> all
mirror.eftel.com <a href="ftp://mirror.eftel.com/debian/">/debian/</a> <a href="http://mirror.eftel.com/debian/">/debian/</a> 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> all
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> all
debian.goldweb.com.au <a href="http://debian.goldweb.com.au/debian/">/debian/</a> hurd-i386 i386
mirror.datafast.net.au <a href="ftp://mirror.datafast.net.au/debian/">/debian/</a> <a href="http://mirror.datafast.net.au/debian/">/debian/</a> i386
debian.ihug.com.au <a href="ftp://debian.ihug.com.au/debian/">/debian/</a> <a href="http://debian.ihug.com.au/debian/">/debian/</a> i386
debian.vicnet.net.au <a href="ftp://debian.vicnet.net.au/debian/">/debian/</a> <a href="http://debian.vicnet.net.au/debian/">/debian/</a> i386
mirror.optus.net <a href="http://mirror.optus.net/debian/">/debian/</a> all
<b>BE Belgium</b>
----------
ftp.tiscali.be <a href="ftp://ftp.tiscali.be/pub/debian/">/pub/debian/</a> <a href="http://ftp.tiscali.be/pub/debian/">/pub/debian/</a> all
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> all
ftp.easynet.be <a href="ftp://ftp.easynet.be/debian/">/debian/</a> <a href="http://ftp.easynet.be/ftp/debian/">/ftp/debian/</a> all
ftp.belnet.be <a href="ftp://ftp.belnet.be/debian/">/debian/</a> <a href="http://ftp.belnet.be/debian/">/debian/</a> all
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> all
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> all
<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> !hppa !hurd-i386 !s390
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> all
debian.telecoms.bg <a href="ftp://debian.telecoms.bg/debian/">/debian/</a> <a href="http://debian.telecoms.bg/debian/">/debian/</a> all
<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> all
sft.if.usp.br <a href="http://sft.if.usp.br/debian/">/debian/</a> i386
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> i386 m68k
ftp.pucpr.br <a href="ftp://ftp.pucpr.br/debian/">/debian/</a> <a href="http://ftp.pucpr.br/debian/">/debian/</a> 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> i386
<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> i386
ftp.mgts.by <a href="ftp://ftp.mgts.by/debian/">/debian/</a> i386
<b>CA Canada</b>
---------
mirror.direct.ca <a href="ftp://mirror.direct.ca/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://mirror.direct.ca/linux/debian/">/linux/debian/</a> i386 ia64 sparc
debian.yorku.ca <a href="http://debian.yorku.ca/debian/">/debian/</a> alpha i386
ftp3.nrc.ca <a href="ftp://ftp3.nrc.ca/debian/">/debian/</a> <a href="http://ftp3.nrc.ca/debian/">/debian/</a> i386
gulus.usherbrooke.ca <a href="ftp://gulus.usherbrooke.ca/debian/">/debian/</a> <a href="http://gulus.usherbrooke.ca/debian/">/debian/</a> all
mirror.cpsc.ucalgary.ca <a href="ftp://mirror.cpsc.ucalgary.ca/debian/">/debian/</a> <a href="http://mirror.cpsc.ucalgary.ca/debian/">/debian/</a> i386
mirror.peer1.net <a href="http://mirror.peer1.net/debian/">/debian/</a> !hppa !ia64 !s390
debian.savoirfairelinux.net <a href="ftp://debian.savoirfairelinux.net/debian/">/debian/</a> <a href="http://debian.savoirfairelinux.net/debian/">/debian/</a> all
debian.mirror.cygnal.ca <a href="ftp://debian.mirror.cygnal.ca/debian/">/debian/</a> <a href="http://debian.mirror.cygnal.ca/debian/">/debian/</a> all
<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> all
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> all
<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> all
debian.experimentos.cl <a href="ftp://debian.experimentos.cl/Debian/debian/">/Debian/debian/</a> <a href="http://debian.experimentos.cl/debian/">/debian/</a> i386
debian.ubiobio.cl <a href="http://debian.ubiobio.cl/debian/">/debian/</a> i386 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> all
debian.cn99.com <a href="ftp://debian.cn99.com/debian/">/debian/</a> <a href="http://debian.cn99.com/debian/">/debian/</a> i386
mirror.vmmatrix.net <a href="http://mirror.vmmatrix.net/debian/">/debian/</a> !alpha !hppa !m68k !mipsel !s390
<b>CO Colombia</b>
-----------
fatboy.umng.edu.co <a href="http://fatboy.umng.edu.co/debian/">/debian/</a> alpha hurd-i386 i386 ia64 sparc
debian.funlam.edu.co <a href="http://debian.funlam.edu.co/debian/">/debian/</a> i386
<b>CR Costa Rica</b>
-------------
debian.efis.ucr.ac.cr <a href="http://debian.efis.ucr.ac.cr/debian/">/debian/</a> all
<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> all
debian.sh.cvut.cz <a href="ftp://debian.sh.cvut.cz/debian/">/debian/</a> <a href="http://debian.sh.cvut.cz/debian/">/debian/</a> all
ftp.zcu.cz <a href="ftp://ftp.zcu.cz/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://ftp.zcu.cz/ftp/pub/linux/debian/">/ftp/pub/linux/debian/</a> 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> all
ftp2.de.debian.org <a href="ftp://ftp2.de.debian.org/debian/">/debian/</a> <a href="http://ftp2.de.debian.org/debian/">/debian/</a> all
ftp.tu-clausthal.de <a href="ftp://ftp.tu-clausthal.de/pub/linux/debian/">/pub/linux/debian/</a> alpha arm i386 ia64 m68k mips mipsel 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> i386
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> all
ftp.uni-erlangen.de <a href="ftp://ftp.uni-erlangen.de/pub/Linux/debian/">/pub/Linux/debian/</a> <a href="http://ftp.uni-erlangen.de/pub/Linux/debian/">/pub/Linux/debian/</a> all
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 i386 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> all
ftp.stw-bonn.de <a href="ftp://ftp.stw-bonn.de/debian/">/debian/</a> <a href="http://ftp.stw-bonn.de/debian/">/debian/</a> i386
ftp.fu-berlin.de <a href="ftp://ftp.fu-berlin.de/pub/unix/linux/mirrors/debian/">/pub/unix/linux/mirrors/debian/</a> all
debian.tu-bs.de <a href="ftp://debian.tu-bs.de/debian/">/debian/</a> <a href="http://debian.tu-bs.de/debian/">/debian/</a> all
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 i386 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> hurd-i386 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> all
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> all
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> all
ftp.uni-kl.de <a href="ftp://ftp.uni-kl.de/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://ftp.uni-kl.de/debian/">/debian/</a> i386 ia64 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> !arm
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> all
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> all
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 arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.informatik.uni-frankfurt.de <a href="ftp://ftp.informatik.uni-frankfurt.de/pub/linux/Mirror/ftp.debian.org/debian/">/pub/linux/Mirror/ftp.debian.org/debian/</a><a href="http://ftp.informatik.uni-frankfurt.de/debian/">/debian/</a> i386 ia64
debian.netcologne.de <a href="ftp://debian.netcologne.de/debian/">/debian/</a> <a href="http://debian.netcologne.de/debian/">/debian/</a> all
<b>DK Denmark</b>
----------
mirrors.dotsrc.org <a href="ftp://mirrors.dotsrc.org/debian/">/debian/</a> <a href="http://mirrors.dotsrc.org/debian/">/debian/</a> all
ftp.dkuug.dk <a href="ftp://ftp.dkuug.dk/pub/debian/">/pub/debian/</a> <a href="http://ftp.dkuug.dk/debian/">/debian/</a> all
mirror.here.dk <a href="http://mirror.here.dk/debian/">/debian/</a> !mips !mipsel
debian.uni-c.dk <a href="http://debian.uni-c.dk/debian/">/debian/</a> all
mirrors.telianet.dk <a href="ftp://mirrors.telianet.dk/debian/">/debian/</a> <a href="http://mirrors.telianet.dk/debian/">/debian/</a> hurd-i386 i386 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> all
<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> all
toxo.com.uvigo.es <a href="ftp://toxo.com.uvigo.es/debian/">/debian/</a> <a href="http://toxo.com.uvigo.es/debian/">/debian/</a> all
ftp.rediris.es <a href="ftp://ftp.rediris.es/debian/">/debian/</a> <a href="http://ftp.rediris.es/debian/">/debian/</a> alpha i386 ia64 sparc
jane.uab.es <a href="http://jane.uab.es/debian/">/debian/</a> hurd-i386 i386
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.cica.es <a href="ftp://ftp.cica.es/debian/">/debian/</a> all
ftp.dat.etsit.upm.es <a href="ftp://ftp.dat.etsit.upm.es/debian/">/debian/</a> <a href="http://ftp.dat.etsit.upm.es/debian/">/debian/</a> i386
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 arm hppa 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> all
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> all
ftp.jyu.fi <a href="ftp://ftp.jyu.fi/debian/">/debian/</a> <a href="http://ftp.jyu.fi/debian/">/debian/</a> !arm !m68k !mips !mipsel !s390
<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> all
ftp2.fr.debian.org <a href="ftp://ftp2.fr.debian.org/debian/">/debian/</a> <a href="http://ftp2.fr.debian.org/debian/">/debian/</a> all
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> all
ftp.proxad.net <a href="ftp://ftp.proxad.net/mirrors/ftp.debian.org/">/mirrors/ftp.debian.org/</a> all
ftp.minet.net <a href="ftp://ftp.minet.net/debian/">/debian/</a> all
ftp.info.iut-tlse3.fr <a href="ftp://ftp.info.iut-tlse3.fr/debian/">/debian/</a> <a href="http://ftp.info.iut-tlse3.fr/debian/">/debian/</a> i386 m68k
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> all
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> i386 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 i386
debian.mirrors.easynet.fr <a href="ftp://debian.mirrors.easynet.fr/debian/">/debian/</a> <a href="http://debian.mirrors.easynet.fr/">/</a> alpha i386 powerpc
ftp.u-strasbg.fr <a href="ftp://ftp.u-strasbg.fr/debian/">/debian/</a> <a href="http://ftp.u-strasbg.fr/debian/">/debian/</a> !arm !hppa !mips !mipsel !s390
ftp.ipv6.opentransit.net <a href="ftp://ftp.ipv6.opentransit.net/debian/">/debian/</a> <a href="http://ftp.ipv6.opentransit.net/debian/">/debian/</a> !mipsel
debian.lami.univ-evry.fr <a href="ftp://debian.lami.univ-evry.fr/debian/">/debian/</a> i386 sparc
mir1.ovh.net <a href="ftp://mir1.ovh.net/debian/">/debian/</a> <a href="http://mir1.ovh.net/debian/">/debian/</a> all
mir2.ovh.net <a href="http://mir2.ovh.net/debian/">/debian/</a> all
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> all
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 !arm !m68k
ftp.debian.ikoula.com <a href="ftp://ftp.debian.ikoula.com/debian/">/debian/</a> all
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 arm hppa 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> !arm !hppa !s390
<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> all
debian.hands.com <a href="ftp://debian.hands.com/debian/">/debian/</a> <a href="http://debian.hands.com/debian/">/debian/</a> all
ftp.demon.co.uk <a href="ftp://ftp.demon.co.uk/pub/mirrors/linux/debian/">/pub/mirrors/linux/debian/</a> all
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> 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> all
ftp.ticklers.org <a href="ftp://ftp.ticklers.org/debian/">/debian/</a> <a href="http://ftp.ticklers.org/debian/">/debian/</a> all
debian.blueyonder.co.uk <a href="ftp://debian.blueyonder.co.uk/pub/debian/">/pub/debian/</a> <a href="http://debian.blueyonder.co.uk/">/</a> all
mirror.positive-internet.com <a href="ftp://mirror.positive-internet.com/debian/">/debian/</a> <a href="http://mirror.positive-internet.com/debian/">/debian/</a> i386
the.earth.li <a href="ftp://the.earth.li/debian/">/debian/</a> <a href="http://the.earth.li/debian/">/debian/</a> 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> all
<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> all
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> i386 sparc
ftp.duth.gr <a href="ftp://ftp.duth.gr/debian/">/debian/</a> <a href="http://ftp.duth.gr/debian/">/debian/</a> all
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> all
debian.spark.net.gr <a href="http://debian.spark.net.gr/debian/">/debian/</a> i386 sparc
debian.internet.gr <a href="ftp://debian.internet.gr/debian/">/debian/</a> <a href="http://debian.internet.gr/debian/">/debian/</a> i386 ia64 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> all
sunsite.ust.hk <a href="ftp://sunsite.ust.hk/pub/debian/">/pub/debian/</a> all
www.zentek-international.com <a href="http://www.zentek-international.com/mirrors/debian/debian/">/mirrors/debian/debian/</a> all
<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> all
ftp.irb.hr <a href="ftp://ftp.irb.hr/debian/">/debian/</a> <a href="http://ftp.irb.hr/debian/">/debian/</a> arm hurd-i386 i386 ia64 sparc
ftp.carnet.hr <a href="ftp://ftp.carnet.hr/debian/">/debian/</a> <a href="http://ftp.carnet.hr/debian/">/debian/</a> all
debian.iskon.hr <a href="ftp://debian.iskon.hr/debian/">/debian/</a> <a href="http://debian.iskon.hr/debian/">/debian/</a> 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> all
ftp.index.hu <a href="ftp://ftp.index.hu/debian/">/debian/</a> i386
debian.inf.elte.hu <a href="ftp://debian.inf.elte.hu/debian/">/debian/</a> <a href="http://debian.inf.elte.hu/debian/">/debian/</a> all
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> 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> i386
debian.3wsi.net <a href="http://debian.3wsi.net/debian/">/debian/</a> i386
debian.indika.net.id <a href="http://debian.indika.net.id/debian/">/debian/</a> all
<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> all
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> all
<b>IL Israel</b>
---------
mirror.hamakor.org.il <a href="http://mirror.hamakor.org.il/pub/mirrors/debian/">/pub/mirrors/debian/</a> i386
<b>IN India</b>
--------
ftp.iitm.ac.in <a href="ftp://ftp.iitm.ac.in/debian/">/debian/</a> <a href="http://ftp.iitm.ac.in/debian/">/debian/</a> 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> all
<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> all
ftp.bononia.it <a href="ftp://ftp.bononia.it/debian/">/debian/</a> <a href="http://ftp.bononia.it/debian/">/debian/</a> all
freedom.dicea.unifi.it <a href="ftp://freedom.dicea.unifi.it/ftp/pub/linux/debian/">/ftp/pub/linux/debian/</a> <a href="http://freedom.dicea.unifi.it/ftp/pub/linux/debian/">/ftp/pub/linux/debian/</a> hurd-i386 i386
ftp.eutelia.it <a href="ftp://ftp.eutelia.it/pub/Debian_Mirror/">/pub/Debian_Mirror/</a> all
cdn.mirror.garr.it <a href="http://cdn.mirror.garr.it/mirrors/debian/">/mirrors/debian/</a> alpha arm hppa i386 ia64 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 arm hppa i386 ia64 sparc
debian.fastweb.it <a href="ftp://debian.fastweb.it/debian/">/debian/</a> <a href="http://debian.fastweb.it/debian/">/debian/</a> all
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 arm hppa 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> all
<b>JP Japan</b>
--------
ftp2.jp.debian.org <a href="ftp://ftp2.jp.debian.org/debian/">/debian/</a> <a href="http://ftp2.jp.debian.org/debian/">/debian/</a> all
ftp.jp.debian.org <a href="ftp://ftp.jp.debian.org/debian/">/debian/</a> <a href="http://ftp.jp.debian.org/debian/">/debian/</a> all
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> all
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> all
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> all
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> all
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> all
sb.itc.u-tokyo.ac.jp <a href="ftp://sb.itc.u-tokyo.ac.jp/DEBIAN/debian/">/DEBIAN/debian/</a> all
ftp.riken.go.jp <a href="ftp://ftp.riken.go.jp/pub/Linux/debian/debian/">/pub/Linux/debian/debian/</a> <a href="http://ftp.riken.go.jp/pub/Linux/debian/debian/">/pub/Linux/debian/debian/</a> i386
debian.shimpinomori.net <a href="http://debian.shimpinomori.net/debian/">/debian/</a> i386
ring.hosei.ac.jp <a href="ftp://ring.hosei.ac.jp/pub/linux/debian/debian/">/pub/linux/debian/debian/</a> <a href="http://ring.hosei.ac.jp/archives/linux/debian/debian/">/archives/linux/debian/debian/</a> all
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> all
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 arm hppa 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> all
ftp.kreonet.re.kr <a href="ftp://ftp.kreonet.re.kr/pub/Linux/debian/">/pub/Linux/debian/</a> <a href="http://ftp.kreonet.re.kr/pub/Linux/debian/">/pub/Linux/debian/</a> all
<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> arm i386 sparc
debian.vinita.lt <a href="ftp://debian.vinita.lt/debian/">/debian/</a> <a href="http://debian.vinita.lt/debian/">/debian/</a> i386
<b>LV Latvia</b>
---------
ftp.latnet.lv <a href="ftp://ftp.latnet.lv/linux/debian/">/linux/debian/</a> <a href="http://ftp.latnet.lv/linux/debian/">/linux/debian/</a> hurd-i386 i386
<b>MX Mexico</b>
---------
nisamox.fciencias.unam.mx <a href="ftp://nisamox.fciencias.unam.mx/debian/">/debian/</a> <a href="http://nisamox.fciencias.unam.mx/debian/">/debian/</a> all
<b>NI Nicaragua</b>
------------
debian.uni.edu.ni <a href="http://debian.uni.edu.ni/debian/">/debian/</a> 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> all
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> all
ftp.eu.uu.net <a href="ftp://ftp.eu.uu.net/debian/">/debian/</a> <a href="http://ftp.eu.uu.net/debian/">/debian/</a> all
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> all
download.xs4all.nl <a href="ftp://download.xs4all.nl/pub/mirror/debian/">/pub/mirror/debian/</a> all
ftp.debian.nl <a href="ftp://ftp.debian.nl/debian/">/debian/</a> <a href="http://ftp.debian.nl/debian/">/debian/</a> i386
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> all
debian.essentkabel.com <a href="ftp://debian.essentkabel.com/debian/">/debian/</a> <a href="http://debian.essentkabel.com/debian/">/debian/</a> all
<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> !m68k
debian.marked.no <a href="ftp://debian.marked.no/debian/">/debian/</a> <a href="http://debian.marked.no/debian/">/debian/</a> all
<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> all
debian.ihug.co.nz <a href="ftp://debian.ihug.co.nz/debian/">/debian/</a> <a href="http://debian.ihug.co.nz/debian/">/debian/</a> 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> all
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> !arm !m68k
mirror.ipartners.pl <a href="ftp://mirror.ipartners.pl/pub/debian/">/pub/debian/</a> all
ftp.man.szczecin.pl <a href="ftp://ftp.man.szczecin.pl/pub/Linux/debian/">/pub/Linux/debian/</a> all
<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> 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> i386
debian.ua.pt <a href="ftp://debian.ua.pt/debian/">/debian/</a> <a href="http://debian.ua.pt/debian/">/debian/</a> all
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> hurd-i386 i386
<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> all
ftp.lug.ro <a href="ftp://ftp.lug.ro/debian/">/debian/</a> <a href="http://ftp.lug.ro/debian/">/debian/</a> i386 ia64
<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> all
debian.nsu.ru <a href="ftp://debian.nsu.ru/debian/">/debian/</a> <a href="http://debian.nsu.ru/debian/">/debian/</a> i386
debian.udsu.ru <a href="ftp://debian.udsu.ru/debian/">/debian/</a> <a href="http://debian.udsu.ru/debian/">/debian/</a> i386
ftp.psn.ru <a href="ftp://ftp.psn.ru/debian/">/debian/</a> <a href="http://ftp.psn.ru/debian/">/debian/</a> hurd-i386 i386
ftp.corbina.ru <a href="ftp://ftp.corbina.ru/pub/Linux/debian/">/pub/Linux/debian/</a> i386 ia64
<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> all
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>all
ftp.du.se <a href="ftp://ftp.du.se/debian/">/debian/</a> <a href="http://ftp.du.se/debian/">/debian/</a> all
kalle.csb.ki.se <a href="ftp://kalle.csb.ki.se/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://kalle.csb.ki.se/pub/linux/debian/">/pub/linux/debian/</a> i386 sparc
mirror.pudas.net <a href="ftp://mirror.pudas.net/debian/">/debian/</a> <a href="http://mirror.pudas.net/debian/">/debian/</a> all
ftp.port80.se <a href="ftp://ftp.port80.se/debian/">/debian/</a> <a href="http://ftp.port80.se/debian/">/debian/</a> all
ftp.ds.hj.se <a href="ftp://ftp.ds.hj.se/pub/Linux/distributions/debian/">/pub/Linux/distributions/debian/</a> <a href="http://ftp.ds.hj.se/pub/Linux/distributions/debian/">/pub/Linux/distributions/debian/</a> i386 powerpc sparc
<b>SG Singapore</b>
------------
mirror.averse.net <a href="ftp://mirror.averse.net/debian/">/debian/</a> <a href="http://mirror.averse.net/debian/">/debian/</a> i386
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> alpha hurd-i386 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> 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 i386 ia64 m68k sparc
ftp.arnes.si <a href="ftp://ftp.arnes.si/packages/debian/">/packages/debian/</a> all
<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> all
<b>TH Thailand</b>
-----------
ftp.nectec.or.th <a href="ftp://ftp.nectec.or.th/pub/linux-distributions/Debian/">/pub/linux-distributions/Debian/</a> all
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> !arm !hppa !ia64 !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> all
ftp.linux.org.tr <a href="ftp://ftp.linux.org.tr/pub/mirrors/debian/">/pub/mirrors/debian/</a> all
<b>TW Taiwan</b>
---------
ftp.tku.edu.tw <a href="ftp://ftp.tku.edu.tw/OS/Linux/distributions/debian/">/OS/Linux/distributions/debian/</a> <a href="http://ftp.tku.edu.tw/OS/Linux/distributions/debian/">/OS/Linux/distributions/debian/</a> all
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> hurd-i386 i386
debian.linux.org.tw <a href="ftp://debian.linux.org.tw/debian/">/debian/</a> <a href="http://debian.linux.org.tw/debian/">/debian/</a> all
linux.cdpa.nsysu.edu.tw <a href="ftp://linux.cdpa.nsysu.edu.tw/debian/">/debian/</a> <a href="http://linux.cdpa.nsysu.edu.tw/debian/">/debian/</a> all
opensource.nchc.org.tw <a href="ftp://opensource.nchc.org.tw/debian/">/debian/</a> <a href="http://opensource.nchc.org.tw/debian/">/debian/</a> all
debian.nctu.edu.tw <a href="http://debian.nctu.edu.tw/debian/">/debian/</a> all
<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> !m68k !s390
ftp.debian.org <a href="ftp://ftp.debian.org/debian/">/debian/</a> <a href="http://ftp.debian.org/debian/">/debian/</a> i386
debian.crosslink.net <a href="ftp://debian.crosslink.net/debian/">/debian/</a> <a href="http://debian.crosslink.net/debian/">/debian/</a> all
ftp-linux.cc.gatech.edu <a href="ftp://ftp-linux.cc.gatech.edu/debian/">/debian/</a> <a href="http://ftp-linux.cc.gatech.edu/debian/">/debian/</a> all
ftp.egr.msu.edu <a href="ftp://ftp.egr.msu.edu/debian/">/debian/</a> <a href="http://ftp.egr.msu.edu/debian/">/debian/</a> all
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> hurd-i386 i386 sparc
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> all
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> i386
ftp.cs.unm.edu <a href="ftp://ftp.cs.unm.edu/mirrors/debian/">/mirrors/debian/</a> all
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> 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> all
natasha.stmarytx.edu <a href="http://natasha.stmarytx.edu/debian/">/debian/</a> all
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> all
debian.uchicago.edu <a href="ftp://debian.uchicago.edu/debian/">/debian/</a> <a href="http://debian.uchicago.edu/debian/">/debian/</a> all
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> all
debian.fifi.org <a href="ftp://debian.fifi.org/pub/debian/">/pub/debian/</a> <a href="http://debian.fifi.org/debian/">/debian/</a> i386 sparc
gladiator.real-time.com <a href="ftp://gladiator.real-time.com/linux/debian/">/linux/debian/</a> i386
mirrors.kernel.org <a href="ftp://mirrors.kernel.org/debian/">/debian/</a> <a href="http://mirrors.kernel.org/debian/">/debian/</a> all
mirrors.rcn.net <a href="ftp://mirrors.rcn.net/debian/">/debian/</a> <a href="http://mirrors.rcn.net/debian/">/debian/</a> i386
ftp.keystealth.org <a href="ftp://ftp.keystealth.org/debian/">/debian/</a> <a href="http://ftp.keystealth.org/debian/">/debian/</a> !alpha !arm !hppa !m68k !s390
debian.lcs.mit.edu <a href="ftp://debian.lcs.mit.edu/debian/">/debian/</a> <a href="http://debian.lcs.mit.edu/debian/">/debian/</a> all
archive.progeny.com <a href="ftp://archive.progeny.com/debian/">/debian/</a> <a href="http://archive.progeny.com/debian/">/debian/</a> all
linux.csua.berkeley.edu <a href="ftp://linux.csua.berkeley.edu/debian/">/debian/</a> <a href="http://linux.csua.berkeley.edu/debian/">/debian/</a> all
debian.secsup.org <a href="ftp://debian.secsup.org/pub/linux/debian/">/pub/linux/debian/</a> <a href="http://debian.secsup.org/">/</a> all
debian.teleglobe.net <a href="ftp://debian.teleglobe.net/debian/">/debian/</a> <a href="http://debian.teleglobe.net/">/</a> all
techweb.rfa.org <a href="ftp://techweb.rfa.org/debian/">/debian/</a> <a href="http://techweb.rfa.org/debian/">/debian/</a> all
debian.osuosl.org <a href="ftp://debian.osuosl.org/debian/">/debian/</a> <a href="http://debian.osuosl.org/debian/">/debian/</a> all
lyre.mit.edu <a href="http://lyre.mit.edu/debian/">/debian/</a> all
mirror.mcs.anl.gov <a href="ftp://mirror.mcs.anl.gov/pub/debian/">/pub/debian/</a> <a href="http://mirror.mcs.anl.gov/debian/">/debian/</a> all
debian.2z.net <a href="http://debian.2z.net/debian/">/debian/</a> i386
sluglug.ucsc.edu <a href="ftp://sluglug.ucsc.edu/debian/">/debian/</a> <a href="http://sluglug.ucsc.edu/debian/">/debian/</a> all
cudlug.cudenver.edu <a href="ftp://cudlug.cudenver.edu/debian/">/debian/</a> <a href="http://cudlug.cudenver.edu/debian/">/debian/</a> alpha hurd-i386 i386 ia64 sparc
mirrors.geeks.org <a href="ftp://mirrors.geeks.org/debian/">/debian/</a> <a href="http://mirrors.geeks.org/debian/">/debian/</a> i386
mirrors.engr.arizona.edu <a href="http://mirrors.engr.arizona.edu/debian/">/debian/</a> i386
mirrors.terrabox.com <a href="ftp://mirrors.terrabox.com/debian/">/debian/</a> <a href="http://mirrors.terrabox.com/debian/">/debian/</a> all
debian.midco.net <a href="http://debian.midco.net/debian/">/debian/</a> all
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> all
debian.mirrors.pair.com <a href="ftp://debian.mirrors.pair.com/">/</a> <a href="http://debian.mirrors.pair.com/">/</a> all
lug.mtu.edu <a href="ftp://lug.mtu.edu/debian/">/debian/</a> <a href="http://lug.mtu.edu/debian/">/debian/</a> alpha 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> all
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> alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 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> all
debian.mirror.frontiernet.net <a href="ftp://debian.mirror.frontiernet.net/debian/">/debian/</a> <a href="http://debian.mirror.frontiernet.net/debian/">/debian/</a> all
<b>VE Venezuela</b>
------------
debian.unesr.edu.ve <a href="http://debian.unesr.edu.ve/debian/">/debian/</a> all
<b>ZA South Africa</b>
---------------
ftp.is.co.za <a href="ftp://ftp.is.co.za/debian/">/debian/</a> <a href="http://ftp.is.co.za/debian/">/debian/</a> i386
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> i386
</small></pre><hr>
<table border="0" width="100%"><tr>
<td align="left"><small>Last modified: Wed May 17 18:52:18 2006</small></td>
<td align="right"><small>Number of sites listed: 330</small></td>
</tr></table>
</body>
</html>

541
templates/iso/README.mirrors.txt Normal file
View File

@ -0,0 +1,541 @@
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 arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Australia ftp.au.debian.org /debian/ all
Australia ftp.wa.au.debian.org /debian/ all
Bulgaria ftp.bg.debian.org /debian/ !hppa !hurd-i386 !s390
Brazil ftp.br.debian.org /debian/ all
Switzerland ftp.ch.debian.org /debian/ all
Chile ftp.cl.debian.org /debian/ all
Czech Republic ftp.cz.debian.org /debian/ all
Germany ftp.de.debian.org /debian/ all
Germany ftp2.de.debian.org /debian/ all
Estonia ftp.ee.debian.org /debian/ all
Spain ftp.es.debian.org /debian/ all
Finland ftp.fi.debian.org /debian/ all
France ftp.fr.debian.org /debian/ all
France ftp2.fr.debian.org /debian/ all
Great Britain ftp.uk.debian.org /debian/ all
Hong Kong ftp.hk.debian.org /debian/ all
Croatia ftp.hr.debian.org /debian/ all
Hungary ftp.hu.debian.org /debian/ all
Ireland ftp.ie.debian.org /debian/ all
Iceland ftp.is.debian.org /debian/ all
Italy ftp.it.debian.org /debian/ all
Japan ftp.jp.debian.org /debian/ all
Japan ftp2.jp.debian.org /debian/ all
Korea ftp.kr.debian.org /debian/ all
Netherlands ftp.nl.debian.org /debian/ all
Norway ftp.no.debian.org /debian/ !m68k
New Zealand ftp.nz.debian.org /debian/ all
Poland ftp.pl.debian.org /debian/ all
Romania ftp.ro.debian.org /debian/ all
Russia ftp.ru.debian.org /debian/ all
Sweden ftp.se.debian.org /debian/ all
Slovenia ftp.si.debian.org /debian/ alpha i386 ia64 m68k sparc
Slovakia ftp.sk.debian.org /debian/ all
Turkey ftp.tr.debian.org /debian/ all
United States ftp.us.debian.org /debian/ !m68k !s390
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/ /download/pub/linux/debian/debian/ i386
debian.usla.org.ar /debian/ i386
AT Austria
----------
ftp.at.debian.org /debian/ /debian/ alpha arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
gd.tuwien.ac.at /opsys/linux/debian/ /opsys/linux/debian/ all
debian.mur.at /debian/ /debian/ i386 ia64
ftp.tu-graz.ac.at /mirror/debian/ /mirror/debian/ all
ftp.univie.ac.at /systems/linux/debian/debian/ /systems/linux/debian/debian/ hurd-i386 i386
debian.inode.at /debian/ /debian/ alpha arm i386 m68k sparc
AU Australia
------------
ftp.wa.au.debian.org /debian/ /debian/ all
ftp.au.debian.org /debian/ /debian/ all
mirror.aarnet.edu.au /debian/ /debian/ !alpha
ftp.monash.edu.au /pub/linux/debian/ /pub/linux/debian/ i386
ftp.uwa.edu.au /mirrors/linux/debian/ all
mirror.eftel.com /debian/ /debian/ i386
mirror.pacific.net.au /debian/ /debian/ all
ftp.iinet.net.au /debian/debian/ /debian/debian/ all
debian.goldweb.com.au /debian/ hurd-i386 i386
mirror.datafast.net.au /debian/ /debian/ i386
debian.ihug.com.au /debian/ /debian/ i386
debian.vicnet.net.au /debian/ /debian/ i386
mirror.optus.net /debian/ all
BE Belgium
----------
ftp.tiscali.be /pub/debian/ /pub/debian/ all
ftp.kulnet.kuleuven.ac.be /debian/ /debian/ all
ftp.easynet.be /debian/ /ftp/debian/ all
ftp.belnet.be /debian/ /debian/ all
ftp.debian.skynet.be /debian/ /ftp/debian/ all
ftp.scarlet.be /pub/debian/ /pub/debian/ all
BG Bulgaria
-----------
ftp.bg.debian.org /debian/ /debian/ !hppa !hurd-i386 !s390
debian.ludost.net /debian/ /debian/ i386
ftp.uni-sofia.bg /debian/ /debian/ all
debian.telecoms.bg /debian/ /debian/ all
BR Brazil
---------
ftp.br.debian.org /debian/ /debian/ all
sft.if.usp.br /debian/ i386
linorg.usp.br /debian/ /debian/ i386
linux.iq.usp.br /debian/ i386 m68k
ftp.pucpr.br /debian/ /debian/ hurd-i386 i386
www.las.ic.unicamp.br /pub/debian/ /pub/debian/ i386
BY Belarus
----------
linux.org.by /debian/ /debian/ i386
ftp.mgts.by /debian/ i386
CA Canada
---------
mirror.direct.ca /pub/linux/debian/ /linux/debian/ i386 ia64 sparc
debian.yorku.ca /debian/ alpha i386
ftp3.nrc.ca /debian/ /debian/ i386
gulus.usherbrooke.ca /debian/ /debian/ all
mirror.cpsc.ucalgary.ca /debian/ /debian/ i386
mirror.peer1.net /debian/ !hppa !ia64 !s390
debian.savoirfairelinux.net /debian/ /debian/ all
debian.mirror.cygnal.ca /debian/ /debian/ all
CH Switzerland
--------------
ftp.ch.debian.org /debian/ /debian/ all
mirror.switch.ch /mirror/debian/ /ftp/mirror/debian/ all
CL Chile
--------
ftp.cl.debian.org /debian/ /debian/ all
debian.experimentos.cl /Debian/debian/ /debian/ i386
debian.ubiobio.cl /debian/ i386 sparc
CN China
--------
ftp.linuxforum.net /debian/ i386
mirrors.geekbone.org /debian/ /debian/ all
debian.cn99.com /debian/ /debian/ i386
mirror.vmmatrix.net /debian/ !alpha !hppa !m68k !mipsel !s390
CO Colombia
-----------
fatboy.umng.edu.co /debian/ alpha hurd-i386 i386 ia64 sparc
debian.funlam.edu.co /debian/ i386
CR Costa Rica
-------------
debian.efis.ucr.ac.cr /debian/ all
CZ Czech Republic
-----------------
ftp.cz.debian.org /debian/ /debian/ all
debian.sh.cvut.cz /debian/ /debian/ all
ftp.zcu.cz /pub/linux/debian/ /ftp/pub/linux/debian/ i386
DE Germany
----------
ftp.de.debian.org /debian/ /debian/ all
ftp2.de.debian.org /debian/ /debian/ all
ftp.tu-clausthal.de /pub/linux/debian/ alpha arm i386 ia64 m68k mips mipsel powerpc sparc
debian.uni-essen.de /debian/ /debian/ i386
ftp.freenet.de /pub/ftp.debian.org/debian/ /debian/ all
ftp.uni-erlangen.de /pub/Linux/debian/ /pub/Linux/debian/ all
sunsite.informatik.rwth-aachen.de /pub/Linux/debian/ /ftp/pub/Linux/debian/ alpha i386 sparc
ftp-stud.fht-esslingen.de /debian/ /debian/ all
ftp.stw-bonn.de /debian/ /debian/ i386
ftp.fu-berlin.de /pub/unix/linux/mirrors/debian/ all
debian.tu-bs.de /debian/ /debian/ all
ftp.uni-koeln.de /debian/ /debian/ alpha i386 sparc
debian.pffa.de /pub/mirrors/debian/ /mirrors/debian/ hurd-i386 i386
ftp.mpi-sb.mpg.de /pub/linux/distributions/debian/debian/ all
ftp.tiscali.de /pub/debian/debian/ /pub/debian/debian/ all
ftp.tu-chemnitz.de /pub/linux/debian/debian/ /pub/linux/debian/debian/ all
ftp.uni-kl.de /pub/linux/debian/ /debian/ i386 ia64 sparc
ftp.uni-bayreuth.de /pub/linux/Debian/debian/ /linux/Debian/debian/ !arm
ftp.informatik.hu-berlin.de /pub/Mirrors/ftp.de.debian.org/debian/ all
ftp.gwdg.de /pub/linux/debian/debian/ /pub/linux/debian/debian/ all
ftp.hosteurope.de /pub/linux/debian/ /pub/linux/debian/ alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
ftp.informatik.uni-frankfurt.de /pub/linux/Mirror/ftp.debian.org/debian//debian/ i386 ia64
debian.netcologne.de /debian/ /debian/ all
DK Denmark
----------
mirrors.dotsrc.org /debian/ /debian/ all
ftp.dkuug.dk /pub/debian/ /debian/ all
mirror.here.dk /debian/ !mips !mipsel
debian.uni-c.dk /debian/ all
mirrors.telianet.dk /debian/ /debian/ hurd-i386 i386 sparc
EE Estonia
----------
ftp.ee.debian.org /debian/ /debian/ all
ES Spain
--------
ftp.es.debian.org /debian/ /debian/ all
toxo.com.uvigo.es /debian/ /debian/ all
ftp.rediris.es /debian/ /debian/ alpha i386 ia64 sparc
jane.uab.es /debian/ hurd-i386 i386
ftp.caliu.info /debian/ /debian/ i386 ia64 m68k mips mipsel powerpc sparc
ftp.cica.es /debian/ all
ftp.dat.etsit.upm.es /debian/ /debian/ i386
ftp.gva.es /pub/mirror/debian/ /mirror/debian/ alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
FI Finland
----------
ftp.fi.debian.org /debian/ /debian/ all
ftp.funet.fi /pub/linux/mirrors/debian/ /pub/linux/mirrors/debian/ all
ftp.jyu.fi /debian/ /debian/ !arm !m68k !mips !mipsel !s390
FR France
---------
ftp.fr.debian.org /debian/ /debian/ all
ftp2.fr.debian.org /debian/ /debian/ all
ftp.iut-bm.univ-fcomte.fr /debian/ /debian/ all
ftp.proxad.net /mirrors/ftp.debian.org/ all
ftp.minet.net /debian/ all
ftp.info.iut-tlse3.fr /debian/ /debian/ i386 m68k
ftp.lip6.fr /pub/linux/distributions/debian/ /pub/linux/distributions/debian/ all
debian.ens-cachan.fr /debian/ /ftp/debian/ i386 sparc
ftp.u-picardie.fr /mirror/debian/ /mirror/debian/ alpha i386
debian.mirrors.easynet.fr /debian/ / alpha i386 powerpc
ftp.u-strasbg.fr /debian/ /debian/ !arm !hppa !mips !mipsel !s390
ftp.ipv6.opentransit.net /debian/ /debian/ !mipsel
debian.lami.univ-evry.fr /debian/ i386 sparc
mir1.ovh.net /debian/ /debian/ all
mir2.ovh.net /debian/ all
ftp.nerim.net /debian/ /debian/ i386
ftp.crihan.fr /debian/ /debian/ all
debian.mines.inpl-nancy.fr /debian/ /debian/ !alpha !arm !m68k
ftp.debian.ikoula.com /debian/ all
webb.ens-cachan.fr /debian/ /debian/ alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
mirrors.ircam.fr /pub/debian/ /pub/debian/ !arm !hppa !s390
GB Great Britain
----------------
ftp.uk.debian.org /debian/ /debian/ all
debian.hands.com /debian/ /debian/ all
ftp.demon.co.uk /pub/mirrors/linux/debian/ all
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/ i386
download.mirror.ac.uk /sites/ftp.debian.org/debian/ /sites/ftp.debian.org/debian/ all
ftp.ticklers.org /debian/ /debian/ all
debian.blueyonder.co.uk /pub/debian/ / all
mirror.positive-internet.com /debian/ /debian/ i386
the.earth.li /debian/ /debian/ hurd-i386 i386
mirror.ox.ac.uk /debian/ /debian/ all
GR Greece
---------
debian.otenet.gr /pub/linux/debian/ /debian/ all
ftp.ntua.gr /pub/linux/debian/ /pub/linux/debian/ i386 sparc
ftp.duth.gr /debian/ /debian/ all
ftp.softnet.tuc.gr /pub/linux/debian/ /ftp/linux/debian/ all
debian.spark.net.gr /debian/ i386 sparc
debian.internet.gr /debian/ /debian/ i386 ia64 s390 sparc
HK Hong Kong
------------
ftp.hk.debian.org /debian/ /debian/ all
sunsite.ust.hk /pub/debian/ all
www.zentek-international.com /mirrors/debian/debian/ all
HR Croatia
----------
ftp.hr.debian.org /debian/ /debian/ all
ftp.irb.hr /debian/ /debian/ arm hurd-i386 i386 ia64 sparc
ftp.carnet.hr /debian/ /debian/ all
debian.iskon.hr /debian/ /debian/ hurd-i386 i386 ia64 s390
HU Hungary
----------
ftp.hu.debian.org /debian/ /debian/ all
ftp.index.hu /debian/ i386
debian.inf.elte.hu /debian/ /debian/ all
ftp.bme.hu /OS/Linux/dist/debian/ /OS/Linux/dist/debian/ hurd-i386 i386 ia64
ID Indonesia
------------
kebo.vlsm.org /debian/ /debian/ i386
debian.3wsi.net /debian/ i386
debian.indika.net.id /debian/ all
IE Ireland
----------
ftp.ie.debian.org /debian/ /debian/ all
ftp.esat.net /pub/linux/debian/ /pub/linux/debian/ all
IL Israel
---------
mirror.hamakor.org.il /pub/mirrors/debian/ i386
IN India
--------
ftp.iitm.ac.in /debian/ /debian/ i386
IS Iceland
----------
ftp.is.debian.org /debian/ /debian/ all
IT Italy
--------
ftp.it.debian.org /debian/ /debian/ all
ftp.bononia.it /debian/ /debian/ all
freedom.dicea.unifi.it /ftp/pub/linux/debian/ /ftp/pub/linux/debian/ hurd-i386 i386
ftp.eutelia.it /pub/Debian_Mirror/ all
cdn.mirror.garr.it /mirrors/debian/ alpha arm hppa i386 ia64 sparc
mi.mirror.garr.it /mirrors/debian/ /mirrors/debian/ alpha arm hppa i386 ia64 sparc
debian.fastweb.it /debian/ /debian/ all
ftp.unina.it /pub/linux/distributions/debian/ /pub/linux/distributions/debian/ alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
debian.fastbull.org /debian/ /debian/ all
JP Japan
--------
ftp2.jp.debian.org /debian/ /debian/ all
ftp.jp.debian.org /debian/ /debian/ all
ring.asahi-net.or.jp /pub/linux/debian/debian/ /archives/linux/debian/debian/ all
ftp.dti.ad.jp /pub/Linux/debian/ /pub/Linux/debian/ all
dennou-k.gfd-dennou.org /library/Linux/debian/ /library/Linux/debian/ all
dennou-q.gfd-dennou.org /library/Linux/debian/ /library/Linux/debian/ all
ftp.yz.yamagata-u.ac.jp /debian/ /debian/ all
sb.itc.u-tokyo.ac.jp /DEBIAN/debian/ all
ftp.riken.go.jp /pub/Linux/debian/debian/ /pub/Linux/debian/debian/ i386
debian.shimpinomori.net /debian/ i386
ring.hosei.ac.jp /pub/linux/debian/debian/ /archives/linux/debian/debian/ all
www.ring.gr.jp /pub/linux/debian/debian/ /archives/linux/debian/debian/ all
ftp.jaist.ac.jp /pub/Linux/Debian/ /pub/Linux/Debian/ alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
KR Korea
--------
ftp.kr.debian.org /debian/ /debian/ all
ftp.kreonet.re.kr /pub/Linux/debian/ /pub/Linux/debian/ all
LT Lithuania
------------
ameba.sc-uni.ktu.lt /debian/ /debian/ i386
debian.balt.net /debian/ /debian/ arm i386 sparc
debian.vinita.lt /debian/ /debian/ i386
LV Latvia
---------
ftp.latnet.lv /linux/debian/ /linux/debian/ hurd-i386 i386
MX Mexico
---------
nisamox.fciencias.unam.mx /debian/ /debian/ all
NI Nicaragua
------------
debian.uni.edu.ni /debian/ hurd-i386 i386
NL Netherlands
--------------
ftp.nl.debian.org /debian/ /debian/ all
ftp.nluug.nl /pub/os/Linux/distr/debian/ /pub/os/Linux/distr/debian/ all
ftp.eu.uu.net /debian/ /debian/ all
ftp.surfnet.nl /pub/os/Linux/distr/debian/ /os/Linux/distr/debian/ all
download.xs4all.nl /pub/mirror/debian/ all
ftp.debian.nl /debian/ /debian/ i386
ftp.tiscali.nl /pub/mirrors/debian/ /debian/ all
debian.essentkabel.com /debian/ /debian/ all
NO Norway
---------
ftp.no.debian.org /debian/ /debian/ !m68k
debian.marked.no /debian/ /debian/ all
NZ New Zealand
--------------
ftp.nz.debian.org /debian/ /debian/ all
debian.ihug.co.nz /debian/ /debian/ i386
PL Poland
---------
ftp.pl.debian.org /debian/ /debian/ all
ftp.icm.edu.pl /pub/Linux/debian/ /pub/Linux/debian/ !arm !m68k
mirror.ipartners.pl /pub/debian/ all
ftp.man.szczecin.pl /pub/Linux/debian/ all
PT Portugal
-----------
ftp.uevora.pt /debian/ /debian/ i386
ftp.eq.uc.pt /pub/software/Linux/debian/ /software/Linux/debian/ i386
debian.ua.pt /debian/ /debian/ all
ftp.linux.pt /pub/mirrors/debian/ /pub/mirrors/debian/ hurd-i386 i386
RO Romania
----------
ftp.ro.debian.org /debian/ /debian/ all
ftp.lug.ro /debian/ /debian/ i386 ia64
RU Russia
---------
ftp.ru.debian.org /debian/ /debian/ all
debian.nsu.ru /debian/ /debian/ i386
debian.udsu.ru /debian/ /debian/ i386
ftp.psn.ru /debian/ /debian/ hurd-i386 i386
ftp.corbina.ru /pub/Linux/debian/ i386 ia64
SE Sweden
---------
ftp.se.debian.org /debian/ /debian/ all
ftp.sunet.se /pub/os/Linux/distributions/debian/ /pub/os/Linux/distributions/debian/all
ftp.du.se /debian/ /debian/ all
kalle.csb.ki.se /pub/linux/debian/ /pub/linux/debian/ i386 sparc
mirror.pudas.net /debian/ /debian/ all
ftp.port80.se /debian/ /debian/ all
ftp.ds.hj.se /pub/Linux/distributions/debian/ /pub/Linux/distributions/debian/ i386 powerpc sparc
SG Singapore
------------
mirror.averse.net /debian/ /debian/ i386
mirror.nus.edu.sg /pub/Debian/ /Debian/ alpha hurd-i386 i386
debian.wow-vision.com.sg /debian/ /debian/ i386
SI Slovenia
-----------
ftp.si.debian.org /debian/ /debian/ alpha i386 ia64 m68k sparc
ftp.arnes.si /packages/debian/ all
SK Slovakia
-----------
ftp.sk.debian.org /debian/ /debian/ all
TH Thailand
-----------
ftp.nectec.or.th /pub/linux-distributions/Debian/ all
ftp.coe.psu.ac.th /debian/ /debian/ !arm !hppa !ia64 !sparc
TR Turkey
---------
ftp.tr.debian.org /debian/ /debian/ all
ftp.linux.org.tr /pub/mirrors/debian/ all
TW Taiwan
---------
ftp.tku.edu.tw /OS/Linux/distributions/debian/ /OS/Linux/distributions/debian/ all
debian.csie.ntu.edu.tw /pub/debian/ /debian/ hurd-i386 i386
debian.linux.org.tw /debian/ /debian/ all
linux.cdpa.nsysu.edu.tw /debian/ /debian/ all
opensource.nchc.org.tw /debian/ /debian/ all
debian.nctu.edu.tw /debian/ all
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/ !m68k !s390
ftp.debian.org /debian/ /debian/ i386
debian.crosslink.net /debian/ /debian/ all
ftp-linux.cc.gatech.edu /debian/ /debian/ all
ftp.egr.msu.edu /debian/ /debian/ all
distro.ibiblio.org /pub/linux/distributions/debian/ /pub/linux/distributions/debian/ hurd-i386 i386 sparc
ftp-mirror.internap.com /pub/debian/ /pub/debian/ all
ftp.cerias.purdue.edu /pub/os/debian/ /pub/os/debian/ i386
ftp.cs.unm.edu /mirrors/debian/ all
mirror.cs.wisc.edu /pub/mirrors/linux/debian/ /pub/mirrors/linux/debian/ i386
ftp.uwsg.indiana.edu /linux/debian/ /linux/debian/ all
natasha.stmarytx.edu /debian/ all
ftp.ndlug.nd.edu /debian/ /mirrors/debian/ all
debian.uchicago.edu /debian/ /debian/ all
carroll.aset.psu.edu /pub/linux/distributions/debian/ /pub/linux/distributions/debian/ all
debian.fifi.org /pub/debian/ /debian/ i386 sparc
gladiator.real-time.com /linux/debian/ i386
mirrors.kernel.org /debian/ /debian/ all
mirrors.rcn.net /debian/ /debian/ i386
ftp.keystealth.org /debian/ /debian/ !alpha !arm !hppa !m68k !s390
debian.lcs.mit.edu /debian/ /debian/ all
archive.progeny.com /debian/ /debian/ all
linux.csua.berkeley.edu /debian/ /debian/ all
debian.secsup.org /pub/linux/debian/ / all
debian.teleglobe.net /debian/ / all
techweb.rfa.org /debian/ /debian/ all
debian.osuosl.org /debian/ /debian/ all
lyre.mit.edu /debian/ all
mirror.mcs.anl.gov /pub/debian/ /debian/ all
debian.2z.net /debian/ i386
sluglug.ucsc.edu /debian/ /debian/ all
cudlug.cudenver.edu /debian/ /debian/ alpha hurd-i386 i386 ia64 sparc
mirrors.geeks.org /debian/ /debian/ i386
mirrors.engr.arizona.edu /debian/ i386
mirrors.terrabox.com /debian/ /debian/ all
debian.midco.net /debian/ all
mirrors.usc.edu /pub/linux/distributions/debian/ /pub/linux/distributions/debian/ all
debian.mirrors.pair.com / / all
lug.mtu.edu /debian/ /debian/ alpha hppa i386 mips mipsel powerpc sparc
debian.mirrors.tds.net /debian/ /debian/ all
debian.cites.uiuc.edu /pub/debian/ /pub/debian/ alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
mirrors.tummy.com /pub/ftp.debian.org/ /debian/ all
debian.mirror.frontiernet.net /debian/ /debian/ all
VE Venezuela
------------
debian.unesr.edu.ve /debian/ all
ZA South Africa
---------------
ftp.is.co.za /debian/ /debian/ i386
ftp.sun.ac.za /debian/ /ftp/debian/ i386
-------------------------------------------------------------------------------
Last modified: Wed May 17 18:52:18 2006 Number of sites listed: 330

164
templates/iso/README.txt Normal file
View File

@ -0,0 +1,164 @@
(HTML version in README.html)
Debian GNU/Linux testing "Etch" - Official Snapshot i386 Binary-1
CD
CONTENTS:
* Intro
* About This CD
* Installing
* Last-Minute Notes
* Using CDs with apt
* CD Manufacturers
* More Information
Welcome to the exciting world of
Debian GNU/Linux!
Intro
=====
This is one of the CD-ROMs of 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").
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, Motorola's 680x0
(m68k), Sun's Sparc, Motorola/IBM's PowerPC, and (Strong)ARM
processors. Check the ports page (http://www.debian.org/ports) for
more information.
Read more at
http://www.debian.org/intro/about
About This CD
=============
This CD-ROM is labeled
Debian GNU/Linux testing "Etch" - Official Snapshot i386 Binary-1
which means that this CD is number 1 of 1 CDs containing programs
("binaries") for `i386' computers.
The programs on the Binary CDs are ordered by popularity. The Binary-1
CD contains the most popular programs and the installation tools; it
is possible to install and run Debian with only the Binary-1 CD. The
other CDs, up to Binary-1, contain mostly special-interest programs.
The Release Notes for "etch" 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 CD is available from the Debian web
site.
Programs and other files that are needed for the installation can be
found on this CD under
/tools/ and /install/floppy/
For the impatient ones: you can start the installation program easily
by booting off this CD-ROM. 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 CD of the
current development version of the Debian system. This means that
all sorts of bugs may be present anywhere in the system.
Using Apt
=============
After installing or upgrading, Debian's packaging system can use
CD-ROMs, 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 Manufacturers
================
You are completely free to manufacture and re-distribute CD-ROMs 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 CD. 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.
Last Modified: Sat Mar 20 12:30:45 EST 2004

3
templates/iso/autorun.bat Normal file
View File

@ -0,0 +1,3 @@
@echo Starting "README.html"...
@start README.html
@exit

2
templates/iso/autorun.inf Normal file
View File

@ -0,0 +1,2 @@
[autorun]
open=autorun.bat

22
templates/iso/doc/00-INDEX Normal file
View File

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

BIN
templates/iso/doc/FAQ/debian-faq.en.html.tar.gz Normal file
View File

Binary file not shown.

BIN
templates/iso/doc/FAQ/debian-faq.en.pdf.gz Normal file
View File

Binary file not shown.

BIN
templates/iso/doc/FAQ/debian-faq.en.ps.gz Normal file
View File

Binary file not shown.

BIN
templates/iso/doc/FAQ/debian-faq.en.txt.gz Normal file
View File

Binary file not shown.

431
templates/iso/doc/FAQ/html/ch-basic_defs.en.html Normal file
View File

@ -0,0 +1,431 @@
<!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 15400 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 450 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 1649 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 &quot;vertical market&quot;. 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 &quot;Linux&quot; 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 &quot;free&quot; 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 1649 volunteer package maintainers are working on over 15400 packages
and improving Debian GNU/Linux. The Debian developers contribute to the
project not by writing new applications (in most cases), but by packaging
existing software according to the standards of the project, by communicating
bug reports to upstream developers, and by providing user support. See also
additional information on how to become a contributor in <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
15400 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 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 &quot;Debian GNU/Linux&quot;, 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-basic_defs.html Symbolic link
View File

@ -0,0 +1 @@
ch-basic_defs.en.html

386
templates/iso/doc/FAQ/html/ch-compat.en.html Normal file
View File

@ -0,0 +1,386 @@
<!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, 3.1, 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&gt;=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 (&quot;Itanium&quot;) 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
&quot;about most&quot; 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 (&quot;.deb&quot; files) on my Red Hat/Slackware/... Linux system? Can I use Red Hat packages (&quot;.rpm&quot; 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 &quot;foo.tar&quot; 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 &quot;can't load
library 'libtermcap.so.2'&quot;, 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-compat.html Symbolic link
View File

@ -0,0 +1 @@
ch-compat.en.html

191
templates/iso/doc/FAQ/html/ch-contributing.en.html Normal file
View File

@ -0,0 +1,191 @@
<!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 &quot;orphaned&quot; 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 &quot;GNU&quot; 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-contributing.html Symbolic link
View File

@ -0,0 +1 @@
ch-contributing.en.html

522
templates/iso/doc/FAQ/html/ch-customizing.en.html Normal file
View File

@ -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 - 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 &quot;group&quot;
of packages is upgraded.
</p>
<p>
Instead, create a local package that modifies the configuration files of the
&quot;group&quot; 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 &quot;sysadmin&quot; 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
&quot;login-local&quot; rather than the program &quot;login&quot; 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] &gt; my_Packages
</pre>
<p>
where:
</p>
<ul>
<li>
<p>
BIN-DIR is a directory where Debian archive files (which usually have an
extension of &quot;.deb&quot;) 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 &quot;main&quot; 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 &quot;virtual&quot; 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-customizing.html Symbolic link
View File

@ -0,0 +1 @@
ch-customizing.en.html

210
templates/iso/doc/FAQ/html/ch-faqinfo.en.html Normal file
View File

@ -0,0 +1,210 @@
<!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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-faqinfo.html Symbolic link
View File

@ -0,0 +1 @@
ch-faqinfo.en.html

567
templates/iso/doc/FAQ/html/ch-ftparchives.en.html Normal file
View File

@ -0,0 +1,567 @@
<!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 &quot;distributions&quot;, 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 &quot;stable&quot; distribution, the
&quot;testing&quot; distribution, and the &quot;unstable&quot; distribution.
The &quot;testing&quot; distribution is sometimes `frozen' (see <a
href="#s-frozen">What about &quot;testing&quot;? 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 &quot;codenames&quot;. 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>sarge</samp> (i.e.
Debian GNU/Linux 3.1) and <samp>testing</samp> is a symbolic link to
<samp>etch</samp>. This means that <samp>sarge</samp> is the current stable
distribution and <samp>etch</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 &quot;sid&quot;?, 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 and <samp>woody</samp> for release 3.0.
</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 &quot;Toy Story&quot; 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>sid</em> was the boy next door who destroyed toys.
</p>
</li>
</ul>
<hr>
<h2><a name="s-sid"></a>5.4 What about &quot;sid&quot;?</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 &quot;sid&quot; also comes from the &quot;Toy Story&quot; 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 &quot;testing&quot; 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 &quot;testing&quot;? How is it `frozen'?</h3>
<p>
When the &quot;testing&quot; 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 &quot;unstable&quot; enter
&quot;testing&quot;.
</p>
<p>
After a while, the &quot;testing&quot; distribution becomes truly `frozen'.
This means that all new packages that are to propagate to the
&quot;testing&quot; are held back, unless they include release-critical bug
fixes. The &quot;testing&quot; 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 &quot;testing&quot; 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
&quot;testing&quot; distribution is declared &quot;stable&quot; and released
with a version number.
</p>
<p>
With each new release, the previous &quot;stable&quot; 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 &quot;contrib&quot;
and &quot;non-free&quot; 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 &quot;incoming&quot;?</h2>
<p>
After a developer uploads a package, it stays for a short while in the
&quot;incoming&quot; 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-ftparchives.html Symbolic link
View File

@ -0,0 +1 @@
ch-ftparchives.en.html

374
templates/iso/doc/FAQ/html/ch-getting.en.html Normal file
View File

@ -0,0 +1,374 @@
<!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 3.1, 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 &quot;i386&quot;, &quot;sparc&quot;, 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 &quot;High Sierra&quot;). 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 -&gt; sarge/
/dists/stable -&gt; sarge/
/dists/testing -&gt; sarge/
/dists/unstable -&gt; sarge/
</pre>
<p>
so that they work when your sources.list has an entry like
</p>
<pre>
deb cdrom:[&lt;name as on cd label&gt;]/ 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 &quot;ext2&quot;, or the &quot;minix&quot; 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-getting.html Symbolic link
View File

@ -0,0 +1 @@
ch-getting.en.html

311
templates/iso/doc/FAQ/html/ch-kernel.en.html Normal file
View File

@ -0,0 +1,311 @@
<!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
kernel-image 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
kernel-source-version package is available (where &quot;version&quot; 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 tty one-line-at-a-time-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.N kernel_image</samp>, where N
is a revision number assigned by the user. The new Debian archive thus formed
would have revision Custom.1, e.g.,
<samp>kernel-image-2.2.14_Custom.1_i386.deb</samp> for the Linux kernel 2.2.14
on i386.
</p>
</li>
</ul>
<ul>
<li>
<p>
Install the package created.
</p>
<ul>
<li>
<p>
<samp>Run dpkg --install /usr/src/kernel-image-VVV_Custom.N.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 /boot/vmlinuz_VVV-Custom.N, 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 <samp>loadlin</samp>, 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 syslinux.cfg 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
<samp>/usr/share/doc/boot-floppies/README</samp> 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
(<samp>/usr/sbin/modconf</samp>) 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
<samp>/etc/modules.conf</samp> (which lists aliases, and other arguments that
must be used in conjunction with various modules) through files in
<samp>/etc/modutils/</samp>, and <samp>/etc/modules</samp> (which lists the
modules that must be loaded at boot time).
</p>
<p>
Like the (new) Configure.help files that are now available to support the
construction of custom kernels, the modconf package comes with a series of help
files (in <samp>/usr/lib/modules_help/</samp>) 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 <samp>kernel-image-NNN.prerm</samp> 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-NNN
</pre>
<p>
(replace &quot;NNN&quot; 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-kernel.html Symbolic link
View File

@ -0,0 +1 @@
ch-kernel.en.html

149
templates/iso/doc/FAQ/html/ch-nexttime.en.html Normal file
View File

@ -0,0 +1,149 @@
<!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 advanced authentication methods such as Kerberos, as
well as additional security enhancements for mandatory access control
mechanisms such as SElinux, RSBAC and buffer overflow protection like
Exec-shield or PaX is still in progress.
</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, for AMD64 there is a development archive at
<code><a href="http://amd64.debian.net/">http://amd64.debian.net/</a></code>
that provides intallation images as well as binary packages for most of the
distribution. This architecture will probably be added for <samp>etch</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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-nexttime.html Symbolic link
View File

@ -0,0 +1 @@
ch-nexttime.en.html

860
templates/iso/doc/FAQ/html/ch-pkg_basics.en.html Normal file
View File

@ -0,0 +1,860 @@
<!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 &quot;dependencies&quot;
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>)
&quot;depends&quot; 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 &quot;package&quot;, 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:
&lt;foo&gt;_&lt;VersionNumber&gt;-&lt;DebianRevisionNumber&gt;.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 &quot;Packages&quot; 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 &quot;19990513&quot; and &quot;1.3.8pre1&quot;.
</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 &lt;doogie@debian.org&gt;
Architecture: i386
Version: 1.3-16
Depends: libc6 (&gt;= 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 &quot;section&quot; 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., &quot;Control files and their
fields&quot;.
</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 &quot;Conffiles:&quot;.
</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 &quot;control&quot; 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 (&quot;.deb&quot;) 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 (&quot;.deb&quot;) 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 &quot;foo&quot; and have file extensions
of &quot;preinst&quot;, &quot;postinst&quot;, 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.
</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 some development
software like the GNU C and C++ compilers (<samp>gcc</samp>, <samp>g++</samp>),
GNU make, as well as the Python interpreter and some server software like
OpenSSH, the BSD printer daemon (<samp>lpr</samp>) and the RPC portmapper
(<samp>portmap</samp>).
</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
&quot;Optional&quot;.
</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 &quot;virtual package&quot; 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, &quot;mail transport agent&quot;. 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 &quot;dependencies&quot; 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. &quot;Conflicts&quot; are
often combined with &quot;replaces&quot;.
</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>
&quot;Pre-Depends&quot; 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 &quot;configure&quot; 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
&quot;Pre-depend&quot; 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 &quot;want&quot; flags tell what the user wanted to do with a package (as
indicated either by the user's actions in the &quot;Select&quot; 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 \* &gt; 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 &lt; 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 &quot;installed&quot;, 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 &quot;deb-src&quot;
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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-pkg_basics.html Symbolic link
View File

@ -0,0 +1 @@
ch-pkg_basics.en.html

936
templates/iso/doc/FAQ/html/ch-pkgtools.en.html Normal file
View File

@ -0,0 +1,936 @@
<!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 &quot;blurf&quot; (or a group of files named
&quot;blurf*&quot; 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) &quot;foo*&quot;: <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 &quot;Obsolete and Locally Created Packages&quot;.
</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>&lt;enter&gt;</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 (&quot;info&quot;) 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 &quot;Access Method&quot; 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 &quot;Packages.gz&quot; 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 15400 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 &quot;All Packages&quot;. If you try
that, your system will instead be reduced to the initial installed base
packages.
</p>
</dd>
</dl>
<dl>
<dt>to be put &quot;on hold&quot;</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 &quot;Install&quot; menu
item to unpack and configure the selected packages. Alternatively, users
wishing to remove files can choose the &quot;Remove&quot; menu item. At any
point, users can choose &quot;Quit&quot; 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
&quot;foo*&quot;</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 &quot;foo&quot; 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/sarge</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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-pkgtools.html Symbolic link
View File

@ -0,0 +1 @@
ch-pkgtools.en.html

170
templates/iso/doc/FAQ/html/ch-redistrib.en.html Normal file
View File

@ -0,0 +1,170 @@
<!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 &quot;vertical market&quot;. 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 &quot;Linux for Hams&quot; distribution, with
specialized programs for Radio Amateurs. He is starting with Debian as the
&quot;base system&quot;, 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 &quot;package&quot; 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-redistrib.html Symbolic link
View File

@ -0,0 +1 @@
ch-redistrib.en.html

410
templates/iso/doc/FAQ/html/ch-software.en.html Normal file
View File

@ -0,0 +1,410 @@
<!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 15180 packages, ranging from news servers and readers to sound
support, FAX programs, database and spreadsheet programs, image processing
programs, communications, net, and mail utilities, Web servers, and even
ham-radio programs are included in the distribution. Another 450 software
suites are available as Debian packages, but are not formally part of Debian
due to license restrictions.
</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 &quot;sections&quot; 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 &quot;ld: cannot find -lfoo&quot; 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>
Since the official Java Development kit and Runtime Environment from Sun
Microsystems is non-free software, even undistributeable by Debian, it cannot
properly be included in Debian. If you want those installed anyway, please
refer to the <code>java-package</code> package in contrib.
</p>
<p>
However, both the JDK and several <em>free</em> implementations of Java
technology are available as Debian packages. 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.
Netscape Navigator, while non-free, is also available as a Debian package and
it can run Java applets.
</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
&quot;release&quot; 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-software.html Symbolic link
View File

@ -0,0 +1 @@
ch-software.en.html

525
templates/iso/doc/FAQ/html/ch-support.en.html Normal file
View File

@ -0,0 +1,525 @@
<!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
&quot;subscribe&quot; 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 &quot;cgi-perl&quot; 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 &quot;We will not hide problems&quot; 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 &quot;help&quot; 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-support.html Symbolic link
View File

@ -0,0 +1 @@
ch-support.en.html

479
templates/iso/doc/FAQ/html/ch-uptodate.en.html Normal file
View File

@ -0,0 +1,479 @@
<!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 &quot;Setting up for an
upgrade from a local mirror&quot;.
</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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/ch-uptodate.html Symbolic link
View File

@ -0,0 +1 @@
ch-uptodate.en.html

112
templates/iso/doc/FAQ/html/footnotes.en.html Normal file
View File

@ -0,0 +1,112 @@
<!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
&quot;sid&quot;. 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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/footnotes.html Symbolic link
View File

@ -0,0 +1 @@
footnotes.en.html

311
templates/iso/doc/FAQ/html/index.en.html Normal file
View File

@ -0,0 +1,311 @@
<!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 &copy; 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></li>
<li><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></li>
</ul></li>
<li><a href="ch-getting.en.html">2 Getting and installing Debian GNU/Linux</a></li>
<li><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></li>
</ul></li>
<li><a href="ch-compat.en.html">3 Compatibility issues</a></li>
<li><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 (&quot;.deb&quot; files) on my Red Hat/Slackware/... Linux system? Can I use Red Hat packages (&quot;.rpm&quot; 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></li>
</ul></li>
<li><a href="ch-software.en.html">4 Software available in the Debian system</a></li>
<li><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 &quot;ld: cannot find -lfoo&quot; 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></li>
</ul></li>
<li><a href="ch-ftparchives.en.html">5 The Debian FTP archives</a></li>
<li><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></li>
<li><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></li>
</ul></li>
<li><a href="ch-ftparchives.en.html#s-sid">5.4 What about &quot;sid&quot;?</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></li>
<li><ul>
<li><a href="ch-ftparchives.en.html#s-frozen">5.6.1 What about &quot;testing&quot;? How is it `frozen'?</a></li>
</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 &quot;incoming&quot;?</a></li>
<li><a href="ch-ftparchives.en.html#s-ownrepository">5.12 How do I set up my own apt-able repository?</a></li>
</ul></li>
<li><a href="ch-pkg_basics.en.html">6 Basics of the Debian package management system</a></li>
<li><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></li>
</ul></li>
<li><a href="ch-pkgtools.en.html">7 The Debian package management tools</a></li>
<li><ul>
<li><a href="ch-pkgtools.en.html#s-pkgprogs">7.1 What programs does Debian provide for managing its packages?</a></li>
<li><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></li>
</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></li>
</ul></li>
<li><a href="ch-uptodate.en.html">8 Keeping your Debian system up-to-date</a></li>
<li><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></li>
<li><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></li>
</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></li>
</ul></li>
<li><a href="ch-kernel.en.html">9 Debian and the kernel</a></li>
<li><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></li>
</ul></li>
<li><a href="ch-customizing.en.html">10 Customizing your installation of Debian GNU/Linux</a></li>
<li><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></li>
</ul></li>
<li><a href="ch-support.en.html">11 Getting support for Debian GNU/Linux</a></li>
<li><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></li>
<li><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></li>
</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></li>
</ul></li>
<li><a href="ch-contributing.en.html">12 Contributing to the Debian Project</a></li>
<li><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></li>
<li><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></li>
</ul></li>
</ul></li>
<li><a href="ch-redistrib.en.html">13 Redistributing Debian GNU/Linux in a commercial product</a></li>
<li><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 &quot;vertical market&quot;. 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 &quot;package&quot; so that it installs effortlessly on any Debian system?</a></li>
</ul></li>
<li><a href="ch-nexttime.en.html">14 Changes expected in the next major release of Debian</a></li>
<li><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></li>
</ul></li>
<li><a href="ch-faqinfo.en.html">15 General information about the FAQ</a></li>
<li><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.3, 25 April 2006<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>
</body>
</html>

1
templates/iso/doc/FAQ/html/index.html Symbolic link
View File

@ -0,0 +1 @@
index.en.html

55
templates/iso/doc/bug-log-access.txt Normal file
View File

@ -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.
_________________________________________________________________

137
templates/iso/doc/bug-log-mailserver.txt Normal file
View File

@ -0,0 +1,137 @@
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 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.
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...
--...
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.
_________________________________________________________________

81
templates/iso/doc/bug-mailserver-refcard.txt Normal file
View File

@ -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.
_________________________________________________________________

396
templates/iso/doc/bug-maint-info.txt Normal file
View File

@ -0,0 +1,396 @@
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 are allowed to 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 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 Etch.
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.
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 6 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.
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@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.
_________________________________________________________________

323
templates/iso/doc/bug-maint-mailcontrol.txt Normal file
View File

@ -0,0 +1,323 @@
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.
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
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.
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 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.
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 the the other
listed bugs.
unblock bugnumber by bug ...
Note that the fix for the first bug is no longer blocked the
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 and will receive all
mail regarding 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.
#...
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...
--...
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.
_________________________________________________________________

304
templates/iso/doc/bug-reporting.txt Normal file
View File

@ -0,0 +1,304 @@
How to report a bug in Debian
Important things to note before sending
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.
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
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.
Sending the bug report using an automatic bug report tool
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.
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.
Sending the bug report via e-mail
Send email to submit@bugs.debian.org, as described below.
Of course, like any email, 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>
Replace <something> with the name of the package which has the bug.
The second line of the message should say:
Version: <something>
Replace <something> 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.
The pseudo-header fields should start at the very start of their
lines.
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 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.
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.).
For more advice on how to help the developers solve your problem,
please read How to Report Bugs Effectively.
Example
A bug report, with mail 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.
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.
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.
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 developers' documentation. Separate multiple tags with commas,
spaces, or both.
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
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.
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.
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.
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.
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.
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 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.
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.
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.
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
_________________________________________________________________
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.
_________________________________________________________________

603
templates/iso/doc/constitution.txt Normal file
View File

@ -0,0 +1,603 @@
Debian Constitution
Constitution for the Debian Project (v1.0)
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
decisionmaking 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 decisionmaking process.
2. Decisionmaking 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 decisionmaking. 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 s.4.1(3),
s.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 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.
6. Together with the Project Leader and SPI, make decisions about
property held in trust for purposes related to Debian. (See
s.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 s4.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 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 and tallies
results are not be 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, and may be ended by the Project Secretary when the
outcome of a vote is no longer in doubt.
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 s.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 s.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 Concorde Vote Counting. The quorum
is the same as for a General Resolution (s.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 s.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 vote 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 None Of The Above option. The
vote finishes when all the members have voted or when the outcome
is no longer in doubt. The result is determined according to
Concorde Vote Counting.
8. The Chairman can stand in for the Leader, together with the
Secretary
As detailed in s.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 decisionmaking.
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 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 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 decisionmaking 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 or 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 mininum 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 a sponsor of a motion may call for a vote on any
or all of the amendments individually or together; the proposer or
sponsor of an amendment may call for a vote only on that amendment
and 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(6).
4. The minimum discussion period is counted from the time the last
formal amendment was accepted, or the last related formal
amendment was accepted if an amendment is being voted on, or since
the whole resolution was proposed if no amendments have been
proposed and accepted.
A.3. Voting procedure
1. Each independent set of related amendments is voted on in a
separate ballot. Each such ballot has as options all the sensible
combinations of amendments and options, and an option Further
Discussion. If Further Discussion wins then the entire resolution
procedure is set back to the start of the discussion period. No
quorum is required for an amendment.
2. When the final form of the resolution has been determined it is
voted on in a final ballot, in which the options are Yes, No and
Further Discussion. If Further Discussion wins then the entire
procedure is set back to the start of the discussion period.
3. The vote taker (if there is one) or the voters (if voting is done
by public pronouncement) may arrange for these ballots to be held
simultaneously, even (for example) using a single voting message.
If amendment ballot(s) and the final ballot are combined in this
way then it must be possible for a voter to vote differently in
the final ballot for each of the possible forms of the final draft
resolution.
4. Votes may be cast during the voting period, as specified
elsewhere. If the voting period can end if the outcome is no
longer in doubt, the possibility that voters may change their
votes is not considered.
5. The votes are counted according to the Concorde Vote Counting. If
a quorum is required then the default option is Further
Discussion.
6. In cases of doubt the Project Secretary shall decide on matters of
procedure (for example, whether particular amendments should be
considered independent or not).
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 then it is considered to have been
withdrawn.
A.6. Concorde Vote Counting
1. This is used to determine the winner amongst a list of options.
Each ballot paper gives a ranking of the voter's preferred
options. (The ranking need not be complete.)
2. Option A is said to Dominate option B if strictly more ballots
prefer A to B than prefer B to A.
3. All options which are Dominated by at least one other option are
discarded, and references to them in ballot papers will be
ignored.
4. If there is any option which Dominates all others then that is the
winner.
5. If there is now more than one option remaining Single
Transferrable Vote will be applied to choose amongst those
remaining:
+ The number of first preferences for each option is counted,
and if any option has more than half it is the winner.
+ Otherwise the option with the lowest number of first
preferences is eliminated and its votes redistributed
according to the second preferences.
+ This elimination procedure is repeated, moving down ballot
papers to 2nd, 3rd, 4th, etc. preferences as required, until
one option gets more than half of the `first' preferences.
6. In the case of ties the elector with a casting vote will decide.
The casting vote does not count as a normal vote; however that
elector will usually also get a normal vote.
7. If a supermajority is required the number of Yes votes in the
final ballot is reduced by an appropriate factor. Strictly
speaking, for a supermajority of F:A, the number of ballots which
prefer Yes to X (when considering whether Yes Dominates X or X
Dominates Yes) or the number of ballots whose first (remaining)
preference is Yes (when doing STV comparisons for winner and
elimination purposes) is multiplied by a factor A/F before the
comparison is done. This means that a 2:1 vote, for example, means
twice as many people voted for as against; abstentions are not
counted.
8. If a quorum is required, there must be at least that many votes
which prefer the winning option to the default option. If there
are not then the default option wins after all. For votes
requiring a supermajority, the actual number of Yes votes is used
when checking whether the quorum has been reached.
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. `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.

135
templates/iso/doc/debian-manifesto Normal file
View File

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

1649
templates/iso/doc/mailing-lists.txt Normal file
View File

File diff suppressed because it is too large Load Diff

131
templates/iso/doc/social-contract.txt Normal file
View File

@ -0,0 +1,131 @@
Debian GNU/Linux Social Contract
The Debian Project is an association of individuals who have made common
cause to create a free operating system. This is the "social contract"
we offer to the free software community.
------------------------------------------------------------------------
"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
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 to not 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".
------------------------------------------------------------------------

33
templates/iso/doc/source-unpack.txt Normal file
View File

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

BIN
templates/iso/pics/blue-lowerleft.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 294 B

Some files were not shown because too many files have changed in this diff Show More