From fe6eb1c593e2df135c8807bf94df614984b4d6ec Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 23 Sep 2007 10:04:46 +0200 Subject: Adding live-helper 1.0~a1-1. --- AUTHORS | 18 - ChangeLog | 474 --- HISTORY | 16 - Makefile | 64 +- README | 12 - TODO | 10 - debian/changelog | 209 +- debian/control | 25 +- debian/copyright | 6 +- debian/cron.daily | 103 - debian/default | 17 - debian/docs | 3 - debian/rules | 17 +- doc/AUTHORS | 4 + doc/CREDITS | 30 + doc/ChangeLog | 4 + doc/ChangeLog.old | 474 +++ doc/NEWS | 27 + doc/README | 84 + doc/TODO | 13 + doc/faq.txt | 9 - doc/man/make-live.8 | 215 -- doc/man/make-live.conf.5 | 94 - functions/chroot.sh | 13 + functions/conffile.sh | 16 + functions/defaults.sh | 384 +++ functions/lockfile.sh | 35 + functions/stagefile.sh | 46 + functions/version.sh | 6 + helpers/Makefile | 11 - helpers/lh_binary | 46 + helpers/lh_binary_encryption | 73 + helpers/lh_binary_includes | 42 + helpers/lh_binary_iso | 54 + helpers/lh_binary_linuximage | 59 + helpers/lh_binary_localincludes | 39 + helpers/lh_binary_manifest | 34 + helpers/lh_binary_md5sum | 51 + helpers/lh_binary_memtest86 | 97 + helpers/lh_binary_net | 53 + helpers/lh_binary_rootfs | 76 + helpers/lh_binary_syslinux | 152 + helpers/lh_binary_usb | 128 + helpers/lh_bootstrap | 19 + helpers/lh_bootstrap_cdebootstrap | 103 + helpers/lh_bootstrap_debootstrap | 93 + helpers/lh_build | 17 + helpers/lh_buildbinary | 200 -- helpers/lh_buildsource | 84 - helpers/lh_cdebootstrap | 33 - helpers/lh_chroot | 50 +- helpers/lh_chroot_apt | 141 + helpers/lh_chroot_debianchroot | 63 + helpers/lh_chroot_hacks | 60 + helpers/lh_chroot_hooks | 50 + helpers/lh_chroot_hosts | 66 + helpers/lh_chroot_linuximage | 74 + helpers/lh_chroot_localhooks | 53 + helpers/lh_chroot_localincludes | 39 + helpers/lh_chroot_localization | 695 ++++ helpers/lh_chroot_localpackages | 75 + helpers/lh_chroot_localpackageslist | 73 + helpers/lh_chroot_packages | 65 + helpers/lh_chroot_packageslist | 76 + helpers/lh_chroot_proc | 61 + helpers/lh_chroot_resolv | 66 + helpers/lh_chroot_sources | 131 + helpers/lh_chroot_symlinks | 70 + helpers/lh_chroot_sysfs | 58 + helpers/lh_chroot_sysvinit | 50 + helpers/lh_chroot_sysvrc | 72 + helpers/lh_chroot_tasks | 55 + helpers/lh_clean | 71 + helpers/lh_cleanapt | 17 - helpers/lh_clone | 25 - helpers/lh_config | 240 +- helpers/lh_configapt | 56 - helpers/lh_confignetwork | 60 - helpers/lh_debootstrap | 25 - helpers/lh_depends | 86 - helpers/lh_genrootfs | 76 - helpers/lh_hook | 21 - helpers/lh_includechroot | 11 - helpers/lh_installapt | 35 - helpers/lh_installlinux | 25 - helpers/lh_installmemtest86+ | 24 - helpers/lh_installpackagelists | 29 - helpers/lh_installpackages | 9 - helpers/lh_installsyslinux | 79 - helpers/lh_installtasks | 12 - helpers/lh_localdeb | 10 - helpers/lh_losetup | 10 +- helpers/lh_manifest | 13 - helpers/lh_md5sums | 17 - helpers/lh_patchchroot | 18 - helpers/lh_patchlinux | 32 - helpers/lh_patchnetwork | 18 - helpers/lh_patchrunlevel | 27 - helpers/lh_preseed | 23 - helpers/lh_setupapt | 124 - helpers/lh_source | 33 + helpers/lh_source_download | 67 + helpers/lh_source_generic | 53 + helpers/lh_source_iso | 53 + helpers/lh_source_net | 53 + helpers/lh_source_usb | 121 + helpers/lh_testroot | 4 +- helpers/make-live | 324 ++ helpers/overview.txt | 51 - hooks/mini | 27 + hooks/minimal | 19 + includes/common/README.html | 660 ++++ includes/common/README.mirrors.html | 746 +++++ includes/common/README.mirrors.txt | 541 ++++ includes/common/README.txt | 164 + includes/common/doc/00-INDEX | 22 + includes/common/doc/FAQ/debian-faq.en.html.tar.gz | Bin 0 -> 57330 bytes includes/common/doc/FAQ/debian-faq.en.pdf.gz | Bin 0 -> 318890 bytes includes/common/doc/FAQ/debian-faq.en.ps.gz | Bin 0 -> 103911 bytes includes/common/doc/FAQ/debian-faq.en.txt.gz | Bin 0 -> 50961 bytes includes/common/doc/FAQ/html/ch-basic_defs.en.html | 431 +++ includes/common/doc/FAQ/html/ch-basic_defs.html | 431 +++ includes/common/doc/FAQ/html/ch-compat.en.html | 386 +++ includes/common/doc/FAQ/html/ch-compat.html | 386 +++ .../common/doc/FAQ/html/ch-contributing.en.html | 191 ++ includes/common/doc/FAQ/html/ch-contributing.html | 191 ++ .../common/doc/FAQ/html/ch-customizing.en.html | 522 +++ includes/common/doc/FAQ/html/ch-customizing.html | 522 +++ includes/common/doc/FAQ/html/ch-faqinfo.en.html | 210 ++ includes/common/doc/FAQ/html/ch-faqinfo.html | 210 ++ .../common/doc/FAQ/html/ch-ftparchives.en.html | 567 ++++ includes/common/doc/FAQ/html/ch-ftparchives.html | 567 ++++ includes/common/doc/FAQ/html/ch-getting.en.html | 374 +++ includes/common/doc/FAQ/html/ch-getting.html | 374 +++ includes/common/doc/FAQ/html/ch-kernel.en.html | 311 ++ includes/common/doc/FAQ/html/ch-kernel.html | 311 ++ includes/common/doc/FAQ/html/ch-nexttime.en.html | 149 + includes/common/doc/FAQ/html/ch-nexttime.html | 149 + includes/common/doc/FAQ/html/ch-pkg_basics.en.html | 860 +++++ includes/common/doc/FAQ/html/ch-pkg_basics.html | 860 +++++ includes/common/doc/FAQ/html/ch-pkgtools.en.html | 936 ++++++ includes/common/doc/FAQ/html/ch-pkgtools.html | 936 ++++++ includes/common/doc/FAQ/html/ch-redistrib.en.html | 170 + includes/common/doc/FAQ/html/ch-redistrib.html | 170 + includes/common/doc/FAQ/html/ch-software.en.html | 410 +++ includes/common/doc/FAQ/html/ch-software.html | 410 +++ includes/common/doc/FAQ/html/ch-support.en.html | 525 +++ includes/common/doc/FAQ/html/ch-support.html | 525 +++ includes/common/doc/FAQ/html/ch-uptodate.en.html | 479 +++ includes/common/doc/FAQ/html/ch-uptodate.html | 479 +++ includes/common/doc/FAQ/html/footnotes.en.html | 112 + includes/common/doc/FAQ/html/footnotes.html | 112 + includes/common/doc/FAQ/html/index.en.html | 311 ++ includes/common/doc/FAQ/html/index.html | 311 ++ includes/common/doc/bug-log-access.txt | 55 + includes/common/doc/bug-log-mailserver.txt | 137 + includes/common/doc/bug-mailserver-refcard.txt | 81 + includes/common/doc/bug-maint-info.txt | 396 +++ includes/common/doc/bug-maint-mailcontrol.txt | 323 ++ includes/common/doc/bug-reporting.txt | 304 ++ includes/common/doc/constitution.txt | 603 ++++ includes/common/doc/debian-manifesto | 135 + includes/common/doc/mailing-lists.txt | 1649 ++++++++++ includes/common/doc/social-contract.txt | 131 + includes/common/doc/source-unpack.txt | 33 + includes/common/pics/blue-lowerleft.png | Bin 0 -> 294 bytes includes/common/pics/blue-lowerright.png | Bin 0 -> 266 bytes includes/common/pics/blue-upperleft.png | Bin 0 -> 280 bytes includes/common/pics/blue-upperright.png | Bin 0 -> 290 bytes includes/common/pics/debian.jpg | Bin 0 -> 8442 bytes includes/common/pics/logo-50.jpg | Bin 0 -> 3986 bytes includes/common/pics/red-lowerleft.png | Bin 0 -> 353 bytes includes/common/pics/red-lowerright.png | Bin 0 -> 299 bytes includes/common/pics/red-upperleft.png | Bin 0 -> 321 bytes includes/common/pics/red-upperright.png | Bin 0 -> 344 bytes includes/common/tools/README | 13 + includes/common/tools/diskio.zip | Bin 0 -> 10290 bytes includes/common/tools/fips20.zip | Bin 0 -> 162110 bytes includes/common/tools/gzip124.exe | Bin 0 -> 119146 bytes includes/common/tools/lodlin16.zip | Bin 0 -> 105410 bytes includes/common/tools/md5sum-w32.zip | Bin 0 -> 70352 bytes includes/common/tools/rawrite1.zip | Bin 0 -> 11157 bytes includes/common/tools/rawrite2.zip | Bin 0 -> 15655 bytes includes/common/tools/rwwrtwin.zip | Bin 0 -> 261448 bytes includes/common/tools/src/md5sum-w32_1.1.dsc | 25 + includes/common/tools/src/md5sum-w32_1.1.tar.gz | Bin 0 -> 7617 bytes includes/common/tools/unz512x3.exe | Bin 0 -> 236134 bytes includes/iso/autorun.bat | 3 + includes/iso/autorun.inf | 2 + includes/usb/autorun.bat | 3 + includes/usb/autorun.inf | 2 + lists/gnome | 16 + lists/gnome-core | 13 + lists/gnome-full | 13 + lists/gnome-junior | 22 + lists/gnustep | 31 + lists/kde | 13 + lists/kde-core | 13 + lists/kde-extra | 19 + lists/kde-full | 16 + lists/kde-junior | 19 + lists/knoppix | 1292 ++++++++ lists/knoppix-dvd | 3417 ++++++++++++++++++++ lists/mini | 4 + lists/minimal | 4 + lists/minimal-net | 8 + lists/rescue | 57 + lists/standard | 7 + lists/standard-x11 | 10 + lists/xfce | 13 + lists/xfce-junior | 19 + src/config | 116 - src/hooks/mini | 9 - src/hooks/minimal | 4 - src/lists/gnome | 17 - src/lists/gnome-core | 14 - src/lists/gnome-full | 14 - src/lists/gnome-junior | 23 - src/lists/gnustep | 29 - src/lists/kde | 14 - src/lists/kde-core | 14 - src/lists/kde-core-i18n | 33 - src/lists/kde-extra | 20 - src/lists/kde-extra-i18n | 52 - src/lists/kde-full | 17 - src/lists/kde-full-i18n | 49 - src/lists/kde-i18n | 33 - src/lists/kde-junior | 20 - src/lists/knoppix | 1292 -------- src/lists/knoppix-dvd | 3417 -------------------- src/lists/mini | 4 - src/lists/minimal | 4 - src/lists/minimal-net | 8 - src/lists/rescue | 57 - src/lists/standard | 7 - src/lists/standard-i18n | 13 - src/lists/x11 | 11 - src/lists/x11-core | 11 - src/lists/xfce | 14 - src/lists/xfce-junior | 20 - src/main.sh | 424 --- src/scripts/02defaults.sh | 376 --- src/scripts/13chroot.sh | 106 - templates/common/README.html | 660 ---- templates/common/README.mirrors.html | 746 ----- templates/common/README.mirrors.txt | 541 ---- templates/common/README.txt | 164 - templates/common/doc/00-INDEX | 22 - templates/common/doc/FAQ/debian-faq.en.html.tar.gz | Bin 57330 -> 0 bytes templates/common/doc/FAQ/debian-faq.en.pdf.gz | Bin 318890 -> 0 bytes templates/common/doc/FAQ/debian-faq.en.ps.gz | Bin 103911 -> 0 bytes templates/common/doc/FAQ/debian-faq.en.txt.gz | Bin 50961 -> 0 bytes .../common/doc/FAQ/html/ch-basic_defs.en.html | 431 --- templates/common/doc/FAQ/html/ch-basic_defs.html | 1 - templates/common/doc/FAQ/html/ch-compat.en.html | 386 --- templates/common/doc/FAQ/html/ch-compat.html | 1 - .../common/doc/FAQ/html/ch-contributing.en.html | 191 -- templates/common/doc/FAQ/html/ch-contributing.html | 1 - .../common/doc/FAQ/html/ch-customizing.en.html | 522 --- templates/common/doc/FAQ/html/ch-customizing.html | 1 - templates/common/doc/FAQ/html/ch-faqinfo.en.html | 210 -- templates/common/doc/FAQ/html/ch-faqinfo.html | 1 - .../common/doc/FAQ/html/ch-ftparchives.en.html | 567 ---- templates/common/doc/FAQ/html/ch-ftparchives.html | 1 - templates/common/doc/FAQ/html/ch-getting.en.html | 374 --- templates/common/doc/FAQ/html/ch-getting.html | 1 - templates/common/doc/FAQ/html/ch-kernel.en.html | 311 -- templates/common/doc/FAQ/html/ch-kernel.html | 1 - templates/common/doc/FAQ/html/ch-nexttime.en.html | 149 - templates/common/doc/FAQ/html/ch-nexttime.html | 1 - .../common/doc/FAQ/html/ch-pkg_basics.en.html | 860 ----- templates/common/doc/FAQ/html/ch-pkg_basics.html | 1 - templates/common/doc/FAQ/html/ch-pkgtools.en.html | 936 ------ templates/common/doc/FAQ/html/ch-pkgtools.html | 1 - templates/common/doc/FAQ/html/ch-redistrib.en.html | 170 - templates/common/doc/FAQ/html/ch-redistrib.html | 1 - templates/common/doc/FAQ/html/ch-software.en.html | 410 --- templates/common/doc/FAQ/html/ch-software.html | 1 - templates/common/doc/FAQ/html/ch-support.en.html | 525 --- templates/common/doc/FAQ/html/ch-support.html | 1 - templates/common/doc/FAQ/html/ch-uptodate.en.html | 479 --- templates/common/doc/FAQ/html/ch-uptodate.html | 1 - templates/common/doc/FAQ/html/footnotes.en.html | 112 - templates/common/doc/FAQ/html/footnotes.html | 1 - templates/common/doc/FAQ/html/index.en.html | 311 -- templates/common/doc/FAQ/html/index.html | 1 - templates/common/doc/bug-log-access.txt | 55 - templates/common/doc/bug-log-mailserver.txt | 137 - templates/common/doc/bug-mailserver-refcard.txt | 81 - templates/common/doc/bug-maint-info.txt | 396 --- templates/common/doc/bug-maint-mailcontrol.txt | 323 -- templates/common/doc/bug-reporting.txt | 304 -- templates/common/doc/constitution.txt | 603 ---- templates/common/doc/debian-manifesto | 135 - templates/common/doc/mailing-lists.txt | 1649 ---------- templates/common/doc/social-contract.txt | 131 - templates/common/doc/source-unpack.txt | 33 - templates/common/pics/blue-lowerleft.png | Bin 294 -> 0 bytes templates/common/pics/blue-lowerright.png | Bin 266 -> 0 bytes templates/common/pics/blue-upperleft.png | Bin 280 -> 0 bytes templates/common/pics/blue-upperright.png | Bin 290 -> 0 bytes templates/common/pics/debian.jpg | Bin 8442 -> 0 bytes templates/common/pics/logo-50.jpg | Bin 3986 -> 0 bytes templates/common/pics/red-lowerleft.png | Bin 353 -> 0 bytes templates/common/pics/red-lowerright.png | Bin 299 -> 0 bytes templates/common/pics/red-upperleft.png | Bin 321 -> 0 bytes templates/common/pics/red-upperright.png | Bin 344 -> 0 bytes templates/common/tools/README | 13 - templates/common/tools/diskio.zip | Bin 10290 -> 0 bytes templates/common/tools/fips20.zip | Bin 162110 -> 0 bytes templates/common/tools/gzip124.exe | Bin 119146 -> 0 bytes templates/common/tools/lodlin16.zip | Bin 105410 -> 0 bytes templates/common/tools/md5sum-w32.zip | Bin 70352 -> 0 bytes templates/common/tools/rawrite1.zip | Bin 11157 -> 0 bytes templates/common/tools/rawrite2.zip | Bin 15655 -> 0 bytes templates/common/tools/rwwrtwin.zip | Bin 261448 -> 0 bytes templates/common/tools/src/md5sum-w32_1.1.dsc | 25 - templates/common/tools/src/md5sum-w32_1.1.tar.gz | Bin 7617 -> 0 bytes templates/common/tools/unz512x3.exe | Bin 236134 -> 0 bytes templates/iso/autorun.bat | 3 - templates/iso/autorun.inf | 2 - templates/syslinux/f10.txt | 4 +- 322 files changed, 30434 insertions(+), 21751 deletions(-) delete mode 100644 AUTHORS delete mode 100644 ChangeLog delete mode 100644 HISTORY delete mode 100644 README delete mode 100644 TODO delete mode 100644 debian/cron.daily delete mode 100644 debian/default delete mode 100644 debian/docs create mode 100644 doc/AUTHORS create mode 100644 doc/CREDITS create mode 100644 doc/ChangeLog create mode 100644 doc/ChangeLog.old create mode 100644 doc/NEWS create mode 100644 doc/README create mode 100644 doc/TODO delete mode 100644 doc/faq.txt delete mode 100644 doc/man/make-live.8 delete mode 100644 doc/man/make-live.conf.5 create mode 100755 functions/chroot.sh create mode 100755 functions/conffile.sh create mode 100755 functions/defaults.sh create mode 100755 functions/lockfile.sh create mode 100755 functions/stagefile.sh create mode 100755 functions/version.sh delete mode 100644 helpers/Makefile create mode 100755 helpers/lh_binary create mode 100755 helpers/lh_binary_encryption create mode 100755 helpers/lh_binary_includes create mode 100755 helpers/lh_binary_iso create mode 100755 helpers/lh_binary_linuximage create mode 100755 helpers/lh_binary_localincludes create mode 100755 helpers/lh_binary_manifest create mode 100755 helpers/lh_binary_md5sum create mode 100755 helpers/lh_binary_memtest86 create mode 100755 helpers/lh_binary_net create mode 100755 helpers/lh_binary_rootfs create mode 100755 helpers/lh_binary_syslinux create mode 100755 helpers/lh_binary_usb create mode 100755 helpers/lh_bootstrap create mode 100755 helpers/lh_bootstrap_cdebootstrap create mode 100755 helpers/lh_bootstrap_debootstrap create mode 100755 helpers/lh_build delete mode 100755 helpers/lh_buildbinary delete mode 100755 helpers/lh_buildsource delete mode 100755 helpers/lh_cdebootstrap create mode 100755 helpers/lh_chroot_apt create mode 100755 helpers/lh_chroot_debianchroot create mode 100755 helpers/lh_chroot_hacks create mode 100755 helpers/lh_chroot_hooks create mode 100755 helpers/lh_chroot_hosts create mode 100755 helpers/lh_chroot_linuximage create mode 100755 helpers/lh_chroot_localhooks create mode 100755 helpers/lh_chroot_localincludes create mode 100755 helpers/lh_chroot_localization create mode 100755 helpers/lh_chroot_localpackages create mode 100755 helpers/lh_chroot_localpackageslist create mode 100755 helpers/lh_chroot_packages create mode 100755 helpers/lh_chroot_packageslist create mode 100755 helpers/lh_chroot_proc create mode 100755 helpers/lh_chroot_resolv create mode 100755 helpers/lh_chroot_sources create mode 100755 helpers/lh_chroot_symlinks create mode 100755 helpers/lh_chroot_sysfs create mode 100755 helpers/lh_chroot_sysvinit create mode 100755 helpers/lh_chroot_sysvrc create mode 100755 helpers/lh_chroot_tasks create mode 100755 helpers/lh_clean delete mode 100755 helpers/lh_cleanapt delete mode 100755 helpers/lh_clone delete mode 100755 helpers/lh_configapt delete mode 100755 helpers/lh_confignetwork delete mode 100755 helpers/lh_debootstrap delete mode 100755 helpers/lh_depends delete mode 100755 helpers/lh_genrootfs delete mode 100755 helpers/lh_hook delete mode 100755 helpers/lh_includechroot delete mode 100755 helpers/lh_installapt delete mode 100755 helpers/lh_installlinux delete mode 100755 helpers/lh_installmemtest86+ delete mode 100755 helpers/lh_installpackagelists delete mode 100755 helpers/lh_installpackages delete mode 100755 helpers/lh_installsyslinux delete mode 100755 helpers/lh_installtasks delete mode 100755 helpers/lh_localdeb delete mode 100755 helpers/lh_manifest delete mode 100755 helpers/lh_md5sums delete mode 100755 helpers/lh_patchchroot delete mode 100755 helpers/lh_patchlinux delete mode 100755 helpers/lh_patchnetwork delete mode 100755 helpers/lh_patchrunlevel delete mode 100755 helpers/lh_preseed delete mode 100755 helpers/lh_setupapt create mode 100755 helpers/lh_source create mode 100755 helpers/lh_source_download create mode 100755 helpers/lh_source_generic create mode 100755 helpers/lh_source_iso create mode 100755 helpers/lh_source_net create mode 100755 helpers/lh_source_usb create mode 100755 helpers/make-live delete mode 100644 helpers/overview.txt create mode 100644 hooks/mini create mode 100644 hooks/minimal create mode 100644 includes/common/README.html create mode 100644 includes/common/README.mirrors.html create mode 100644 includes/common/README.mirrors.txt create mode 100644 includes/common/README.txt create mode 100644 includes/common/doc/00-INDEX create mode 100644 includes/common/doc/FAQ/debian-faq.en.html.tar.gz create mode 100644 includes/common/doc/FAQ/debian-faq.en.pdf.gz create mode 100644 includes/common/doc/FAQ/debian-faq.en.ps.gz create mode 100644 includes/common/doc/FAQ/debian-faq.en.txt.gz create mode 100644 includes/common/doc/FAQ/html/ch-basic_defs.en.html create mode 100644 includes/common/doc/FAQ/html/ch-basic_defs.html create mode 100644 includes/common/doc/FAQ/html/ch-compat.en.html create mode 100644 includes/common/doc/FAQ/html/ch-compat.html create mode 100644 includes/common/doc/FAQ/html/ch-contributing.en.html create mode 100644 includes/common/doc/FAQ/html/ch-contributing.html create mode 100644 includes/common/doc/FAQ/html/ch-customizing.en.html create mode 100644 includes/common/doc/FAQ/html/ch-customizing.html create mode 100644 includes/common/doc/FAQ/html/ch-faqinfo.en.html create mode 100644 includes/common/doc/FAQ/html/ch-faqinfo.html create mode 100644 includes/common/doc/FAQ/html/ch-ftparchives.en.html create mode 100644 includes/common/doc/FAQ/html/ch-ftparchives.html create mode 100644 includes/common/doc/FAQ/html/ch-getting.en.html create mode 100644 includes/common/doc/FAQ/html/ch-getting.html create mode 100644 includes/common/doc/FAQ/html/ch-kernel.en.html create mode 100644 includes/common/doc/FAQ/html/ch-kernel.html create mode 100644 includes/common/doc/FAQ/html/ch-nexttime.en.html create mode 100644 includes/common/doc/FAQ/html/ch-nexttime.html create mode 100644 includes/common/doc/FAQ/html/ch-pkg_basics.en.html create mode 100644 includes/common/doc/FAQ/html/ch-pkg_basics.html create mode 100644 includes/common/doc/FAQ/html/ch-pkgtools.en.html create mode 100644 includes/common/doc/FAQ/html/ch-pkgtools.html create mode 100644 includes/common/doc/FAQ/html/ch-redistrib.en.html create mode 100644 includes/common/doc/FAQ/html/ch-redistrib.html create mode 100644 includes/common/doc/FAQ/html/ch-software.en.html create mode 100644 includes/common/doc/FAQ/html/ch-software.html create mode 100644 includes/common/doc/FAQ/html/ch-support.en.html create mode 100644 includes/common/doc/FAQ/html/ch-support.html create mode 100644 includes/common/doc/FAQ/html/ch-uptodate.en.html create mode 100644 includes/common/doc/FAQ/html/ch-uptodate.html create mode 100644 includes/common/doc/FAQ/html/footnotes.en.html create mode 100644 includes/common/doc/FAQ/html/footnotes.html create mode 100644 includes/common/doc/FAQ/html/index.en.html create mode 100644 includes/common/doc/FAQ/html/index.html create mode 100644 includes/common/doc/bug-log-access.txt create mode 100644 includes/common/doc/bug-log-mailserver.txt create mode 100644 includes/common/doc/bug-mailserver-refcard.txt create mode 100644 includes/common/doc/bug-maint-info.txt create mode 100644 includes/common/doc/bug-maint-mailcontrol.txt create mode 100644 includes/common/doc/bug-reporting.txt create mode 100644 includes/common/doc/constitution.txt create mode 100644 includes/common/doc/debian-manifesto create mode 100644 includes/common/doc/mailing-lists.txt create mode 100644 includes/common/doc/social-contract.txt create mode 100644 includes/common/doc/source-unpack.txt create mode 100644 includes/common/pics/blue-lowerleft.png create mode 100644 includes/common/pics/blue-lowerright.png create mode 100644 includes/common/pics/blue-upperleft.png create mode 100644 includes/common/pics/blue-upperright.png create mode 100644 includes/common/pics/debian.jpg create mode 100644 includes/common/pics/logo-50.jpg create mode 100644 includes/common/pics/red-lowerleft.png create mode 100644 includes/common/pics/red-lowerright.png create mode 100644 includes/common/pics/red-upperleft.png create mode 100644 includes/common/pics/red-upperright.png create mode 100644 includes/common/tools/README create mode 100644 includes/common/tools/diskio.zip create mode 100644 includes/common/tools/fips20.zip create mode 100644 includes/common/tools/gzip124.exe create mode 100644 includes/common/tools/lodlin16.zip create mode 100644 includes/common/tools/md5sum-w32.zip create mode 100644 includes/common/tools/rawrite1.zip create mode 100644 includes/common/tools/rawrite2.zip create mode 100644 includes/common/tools/rwwrtwin.zip create mode 100644 includes/common/tools/src/md5sum-w32_1.1.dsc create mode 100644 includes/common/tools/src/md5sum-w32_1.1.tar.gz create mode 100644 includes/common/tools/unz512x3.exe create mode 100644 includes/iso/autorun.bat create mode 100644 includes/iso/autorun.inf create mode 100644 includes/usb/autorun.bat create mode 100644 includes/usb/autorun.inf create mode 100644 lists/gnome create mode 100644 lists/gnome-core create mode 100644 lists/gnome-full create mode 100644 lists/gnome-junior create mode 100644 lists/gnustep create mode 100644 lists/kde create mode 100644 lists/kde-core create mode 100644 lists/kde-extra create mode 100644 lists/kde-full create mode 100644 lists/kde-junior create mode 100644 lists/knoppix create mode 100644 lists/knoppix-dvd create mode 100644 lists/mini create mode 100644 lists/minimal create mode 100644 lists/minimal-net create mode 100644 lists/rescue create mode 100644 lists/standard create mode 100644 lists/standard-x11 create mode 100644 lists/xfce create mode 100644 lists/xfce-junior delete mode 100644 src/config delete mode 100644 src/hooks/mini delete mode 100644 src/hooks/minimal delete mode 100644 src/lists/gnome delete mode 100644 src/lists/gnome-core delete mode 100644 src/lists/gnome-full delete mode 100644 src/lists/gnome-junior delete mode 100644 src/lists/gnustep delete mode 100644 src/lists/kde delete mode 100644 src/lists/kde-core delete mode 100644 src/lists/kde-core-i18n delete mode 100644 src/lists/kde-extra delete mode 100644 src/lists/kde-extra-i18n delete mode 100644 src/lists/kde-full delete mode 100644 src/lists/kde-full-i18n delete mode 100644 src/lists/kde-i18n delete mode 100644 src/lists/kde-junior delete mode 100644 src/lists/knoppix delete mode 100644 src/lists/knoppix-dvd delete mode 100644 src/lists/mini delete mode 100644 src/lists/minimal delete mode 100644 src/lists/minimal-net delete mode 100644 src/lists/rescue delete mode 100644 src/lists/standard delete mode 100644 src/lists/standard-i18n delete mode 100644 src/lists/x11 delete mode 100644 src/lists/x11-core delete mode 100644 src/lists/xfce delete mode 100644 src/lists/xfce-junior delete mode 100755 src/main.sh delete mode 100644 src/scripts/02defaults.sh delete mode 100644 src/scripts/13chroot.sh delete mode 100644 templates/common/README.html delete mode 100644 templates/common/README.mirrors.html delete mode 100644 templates/common/README.mirrors.txt delete mode 100644 templates/common/README.txt delete mode 100644 templates/common/doc/00-INDEX delete mode 100644 templates/common/doc/FAQ/debian-faq.en.html.tar.gz delete mode 100644 templates/common/doc/FAQ/debian-faq.en.pdf.gz delete mode 100644 templates/common/doc/FAQ/debian-faq.en.ps.gz delete mode 100644 templates/common/doc/FAQ/debian-faq.en.txt.gz delete mode 100644 templates/common/doc/FAQ/html/ch-basic_defs.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-basic_defs.html delete mode 100644 templates/common/doc/FAQ/html/ch-compat.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-compat.html delete mode 100644 templates/common/doc/FAQ/html/ch-contributing.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-contributing.html delete mode 100644 templates/common/doc/FAQ/html/ch-customizing.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-customizing.html delete mode 100644 templates/common/doc/FAQ/html/ch-faqinfo.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-faqinfo.html delete mode 100644 templates/common/doc/FAQ/html/ch-ftparchives.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-ftparchives.html delete mode 100644 templates/common/doc/FAQ/html/ch-getting.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-getting.html delete mode 100644 templates/common/doc/FAQ/html/ch-kernel.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-kernel.html delete mode 100644 templates/common/doc/FAQ/html/ch-nexttime.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-nexttime.html delete mode 100644 templates/common/doc/FAQ/html/ch-pkg_basics.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-pkg_basics.html delete mode 100644 templates/common/doc/FAQ/html/ch-pkgtools.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-pkgtools.html delete mode 100644 templates/common/doc/FAQ/html/ch-redistrib.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-redistrib.html delete mode 100644 templates/common/doc/FAQ/html/ch-software.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-software.html delete mode 100644 templates/common/doc/FAQ/html/ch-support.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-support.html delete mode 100644 templates/common/doc/FAQ/html/ch-uptodate.en.html delete mode 120000 templates/common/doc/FAQ/html/ch-uptodate.html delete mode 100644 templates/common/doc/FAQ/html/footnotes.en.html delete mode 120000 templates/common/doc/FAQ/html/footnotes.html delete mode 100644 templates/common/doc/FAQ/html/index.en.html delete mode 120000 templates/common/doc/FAQ/html/index.html delete mode 100644 templates/common/doc/bug-log-access.txt delete mode 100644 templates/common/doc/bug-log-mailserver.txt delete mode 100644 templates/common/doc/bug-mailserver-refcard.txt delete mode 100644 templates/common/doc/bug-maint-info.txt delete mode 100644 templates/common/doc/bug-maint-mailcontrol.txt delete mode 100644 templates/common/doc/bug-reporting.txt delete mode 100644 templates/common/doc/constitution.txt delete mode 100644 templates/common/doc/debian-manifesto delete mode 100644 templates/common/doc/mailing-lists.txt delete mode 100644 templates/common/doc/social-contract.txt delete mode 100644 templates/common/doc/source-unpack.txt delete mode 100644 templates/common/pics/blue-lowerleft.png delete mode 100644 templates/common/pics/blue-lowerright.png delete mode 100644 templates/common/pics/blue-upperleft.png delete mode 100644 templates/common/pics/blue-upperright.png delete mode 100644 templates/common/pics/debian.jpg delete mode 100644 templates/common/pics/logo-50.jpg delete mode 100644 templates/common/pics/red-lowerleft.png delete mode 100644 templates/common/pics/red-lowerright.png delete mode 100644 templates/common/pics/red-upperleft.png delete mode 100644 templates/common/pics/red-upperright.png delete mode 100644 templates/common/tools/README delete mode 100644 templates/common/tools/diskio.zip delete mode 100644 templates/common/tools/fips20.zip delete mode 100644 templates/common/tools/gzip124.exe delete mode 100644 templates/common/tools/lodlin16.zip delete mode 100644 templates/common/tools/md5sum-w32.zip delete mode 100644 templates/common/tools/rawrite1.zip delete mode 100644 templates/common/tools/rawrite2.zip delete mode 100644 templates/common/tools/rwwrtwin.zip delete mode 100644 templates/common/tools/src/md5sum-w32_1.1.dsc delete mode 100644 templates/common/tools/src/md5sum-w32_1.1.tar.gz delete mode 100644 templates/common/tools/unz512x3.exe delete mode 100644 templates/iso/autorun.bat delete mode 100644 templates/iso/autorun.inf diff --git a/AUTHORS b/AUTHORS deleted file mode 100644 index fb0631e..0000000 --- a/AUTHORS +++ /dev/null @@ -1,18 +0,0 @@ -Main Authors: - - * Daniel Baumann - * Marco Amadori - -Patches (alphabetical order): - - * Alex Owen - * Bas Wijnen - * Cedric Lucantis - * Frederic Lehobey - * Guerkan Senguen - * Jason D. Clinton - * Kai Hendry - * Marcelo D. Re - * Markus Bauer - * Otavio Salvador - * Sebastian Raveau diff --git a/ChangeLog b/ChangeLog deleted file mode 100644 index 03dba64..0000000 --- a/ChangeLog +++ /dev/null @@ -1,474 +0,0 @@ -2007-03-10 Daniel Baumann - - * Added knoppix and knoppix-dvd package lists. - -2007-03-09 Daniel Baumann - - * Getting free loopdevice from inside the chroot, not outside. - -2007-03-09 Daniel Baumann - - * Added kbd to all !minimal lists. - * Uploaded 0.99.25. - -2007-03-08 Otavio Salvador - - * helpers/lh_configapt: Fix aptitude configuration to really avoid - recommended packages to get installed. - * src/scripts/02defaults.sh: Export LIVE_ISOLINUX_SPLASH. - -2007-03-04 Daniel Baumann - - * Replaced removal of kernel on minimal flavours with excludes on the - mksquashfs call. - * Added LIVE_INCLUDE_CHROOT to the manual exported variables as reported - by Mathieu Geli . - * Exported CODENAME_* manually as reported by Cédric Lucantis - . - * Fixed typo s/aptiude/aptitude/ as reported by Kai Hendry - . - * Uploaded 0.99.24. - -2007-02-22 Daniel Baumann - - * Added xresprobe to all x11 lists. - -2007-02-22 Daniel Baumann - - * Applied patches from Otavio Salvador : - - add and cleanup variable exporting in defaults. - - add LIVE_BOOTSTRAP_CONFIG to lh_debootstrap. - * Uploaded 0.99.23. - -2007-02-21 Daniel Baumann - - * Added gnome-junior, kde-junior and xfce-junior lists. - * Uploaded 0.99.22. - -2007-02-19 Daniel Baumann - - * Fixed manifest. - -2007-02-15 Daniel Baumann - - * Applied patch from Sebastian Raveau to - add support for filesystem images encrypted with loop-aes. - -2007-02-13 Daniel Baumann - - * Broken out scripts into modularized lh_* subscripts. - -2007-02-12 Daniel Baumann - - * Added some code as suggested by Alex Owen to - check if the depends (syslinux, memtest etc.) are intentionally - installed in the chroot, and hence, don't remove them. - * Moved some depends into the chroot. - * Uploaded 0.99.21. - -2007-02-11 Daniel Baumann - - * Added mini flavour. - -2007-02-10 Daniel Baumann - - * Added legacy code for genisoimage. - * Uploaded 0.99.20. - -2007-02-09 Daniel Baumann - - * Added usb type. - -2007-02-08 Daniel Baumann - - * Added desktop task to the *-desktop flavours. - -2007-02-07 Daniel Baumann - - * Extended cron job a bit. - * Fixed manual pruning in minimal flavour as suggested by Bas Wijnen - - -2007-02-02 Daniel Baumann - - * Added "--without-daemons". - -2007-02-01 Daniel Baumann - - * Added "--tasks". - * Added desktop-base to all desktop package lists. - -2007-01-31 Daniel Baumann - - * Changed vars in autobuilding script to be able to source - make-live.conf. - * Uploaded 0.99.19. - -2007-01-30 Daniel Baumann - - * Added cron job for autobuilding images. - -2007-01-25 Daniel Baumann - - * Added additional pruning to minimal flavour. - * Using interactive frontend while processing --hook. - * Uploaded 0.99.18. - -2007-01-24 Daniel Baumann - - * Applied patches from Otavio Salvador : - - adding "--keyring" flag. - - adding LIVE_DISK_VOLUME. - - adding start-stop-daemon wrapper to avoid daemons to be started. - - adding workaround to prevent binfmt locking /proc. - - adding LIVE_ISOLINUX_SPLASH. - * Uploaded 0.99.17. - -2007-01-19 Daniel Baumann - - * Replacing mkisofs with genisoimage. - -2007-01-18 Daniel Baumann - - * Cleanups. - * Uploaded 0.99.16. - -2007-01-16 Daniel Baumann - - * Switched default distribution back to unstable, as unstable is usable - again from the kernel point of view. - * Added file to the minimal package list. - * Uploaded 0.99.15. - -2007-01-04 Daniel Baumann - - * Added workaround for new xorg packages by including - xserver-xorg-input-all and xserver-xorg-video-all in all X11 package - lists. See #405639 for more information. - * Added xdebconfigurator to all X11 package lists. - * Adding workaround for initrd backup files. - -2006-11-06 Daniel Baumann - - * Uploaded 0.99.14. - -2006-11-05 Daniel Baumann - - * Applied patch from Markus Bauer : - - fixing script sourcing to exclude files in .svn - -2006-11-03 Daniel Baumann - - * Fixed typo in the policy-rc.d hack. - -2006-11-02 Daniel Baumann - - * Using aptitude instead of apt-get. - * Added '--with-recommends' and '--without-recommends'. - -2006-11-01 Daniel Baumann - - * Fixed regression when using -d ${CODENAME} wrt/ kernel packages. - -2006-10-30 Daniel Baumann - - * Uploaded 0.99.13. - -2006-10-29 Daniel Baumann - - * Added minimal-net flavour. - -2006-10-28 Daniel Baumann - - * Added console-common to standard selection. - -2006-10-27 Daniel Baumann - - * Added patch from Otavio Salvador : - - fixing preseeding error-handling. - -2006-10-26 Daniel Baumann - - * Added gnustep package selection based on the suggestion of - Guerkan Senguen . - -2006-10-25 Daniel Baumann - - * Applied patch from Marcelo D. Re : - - skip deb-src source-list entries when building images with - --without-source. - * Applied patches from Otavio Salvador : - - adding '--bootstrap-config' to support cdebootstraps - '--suite-config'. - - allowing override of ${BASE}. - - adjust sourcing of scripts, so that only the real scripts are - sourced and not other (backup) files. - - allowing override of kernel-packages. - * Reverted mangling of LIVE_DISTRIBUTION for sources.list generation. - -2006-10-23 Daniel Baumann - - * Uploaded 0.99.12. - -2006-10-18 Daniel Baumann - - * Autodetecting proxy now. - -2006-10-16 Daniel Baumann - - * Readded and slightly changed --clone and --preseed. - * Uploaded 0.99.11. - -2006-10-09 Daniel Baumann - - * Cleanups. - * Uploaded 0.99.10. - -2006-10-02 Daniel Baumann - - * Uploaded 0.99.9. - -2006-10-01 Daniel Baumann - - * Added multiple repositories. - * Using LIVE_PROXY_* also for bootstraping. - -2006-09-27 Daniel Baumann - - * Changing manpage section. - -2006-09-26 Daniel Baumann - - * Added default flavour hooks. - * minimal flavour does not install debian-archive-keyring to save space. - * Adjusted network patch. - -2006-09-25 Daniel Baumann - - * Removed now unused initramfs-tools hack. - * Simplified xorg check based on distribution rather than version. - * Added fix from Bas Wijnen for space handling in - arguments. - * Fixed package list handling similar to the fix suggested by Alex Owen - . - * Uploaded 0.99.8. - -2006-09-24 Marco Amadori - - * 13hack.sh: initramfs-tools hack, check added for xorg. - -2006-09-18 Daniel Baumann - - * Uploaded 0.99.7. - -2006-09-15 Daniel Baumann - - * Added eject to minimal package selection. - -2006-09-14 Daniel Baumann - - * Adjustements for linux 2.6.17 testing propagation. - -2006-09-11 Daniel Baumann - - * Uploaded 0.99.6. - -2006-09-08 Marco Amadori - - * 23net.sh: Fixed binary missing directory creation. - * templates/iso: Moved common files to templates/common. - -2006-09-07 Daniel Baumann - - * Minor cleanups. - * Fixed dist target. - -2006-09-06 Marco Amadori - - * 14chroot.sh, main.sh: Added manifest support. - * 23net.sh: Added 2 variables for basenames to ease readability. - * main.sh, 02default.sh: Modified Usage() uses. - -2006-09-04 Daniel Baumann - - * Uploaded 0.99.5. - -2006-09-03 Daniel Baumann - - * Added dist parameter to easily pull images for live.debian.net. - * Added "--output" to specify the image name prefix. - * Exclude iso templates for minimal flavour. - -2006-09-02 Daniel Baumann - - * Added experimental as distribution. - * Added source image generation. - * Using dpkg instead of dpkg-architecture, removed dpkg-dev dependency. - -2006-08-31 Daniel Baumann - - * Added "--disable-generic-indices" and "--enable-generic-indices". - * Fixed i18n lists. - * Rewritten all lists, comments are now possible. - * Lists must be now explicitly given with --package-list, no longer as - last argument of the make-live call. - * Setting default sources.list while the image generation, restoring - customized ones afterwards. - -2006-08-30 Daniel Baumann - - * Cleanups: - - moved 14patch_packages.sh to 13hack.sh. - - simplified 13hack.sh. - -2006-08-29 Marco Amadori - - * pxelinux.cfg: Updated to right defaults, first cifs then nfs or - select your favorite way. Rationale: /dev/nfs is for kernel - discovering, not for initramfs discover, casper will be just fine - with "netboot". - * 13chroot.sh, 14patch_packages.sh: Added a simple system for patching - packages, mainly for xserver-xorg so far. - -2006-08-28 Daniel Baumann - - * Updated documentation. - * Added patch from Alex Owen to update - pxelinux.cfg for NFS root in casper. - * Uploaded 0.99.4. - -2006-08-27 Daniel Baumann - - * Cleanups. - -2006-08-27 Marco Amadori - - * Added sysv init blocking policy. - -2006-08-22 Daniel Baumann - - * Reorganised sources. - * Added staging support. - * Cleaned up parameter names. - * testing is now supported. - -2006-08-21 Daniel Baumann - - * Uploaded 0.99.3. - -2006-08-02 Marco Amadori - - * Rewrote netboot support. - * Added support for pure directory rootfs images. - -2006-07-31 Daniel Baumann - - * Uploaded 0.99.2. - -2006-07-28 Daniel Baumann - - * Added DEBIAN_FRONTEND to chroots(), now completely non-interactive. - * Fixed wrong chroot patch. - -2006-07-27 Marco Amadori - - * Changed amd64 kernel naming scheme. - -2006-07-24 Daniel Baumann - - * Uploaded 0.99.1. - -2006-07-19 Daniel Baumann - - * Bugfixes. - -2006-07-18 Daniel Baumann - - * Added iso templates. - -2006-07-17 Daniel Baumann - - * Added chroot to 01-patch.sh. - * Added "--logfile". - * Uploaded 0.99. - -2006-07-01 Daniel Baumann - - * Added "--flavour". - -2006-06-28 Daniel Baumann - - * Added "--debug" and "--verbose". - -2006-06-23 Daniel Baumann - - * Rewritten manpages. - -2006-06-19 Marco Amadori - - * Added "--templates" options. - * Fixed some typos. - -2006-06-15 Daniel Baumann - - * General fixes. - -2006-06-18 Marco Amadori - - * Added "-a|--architecture" and "-p|--package-list" options. - * Reworked how lists works. - -2006-06-15 Daniel Baumann - - * General cleanup. - -2006-06-14 Marco Amadori - - * Re-added "-f|--filesystem". - -2006-06-12 Marco Amadori - - * Added "--conffile", "--preseed", "--clone", and "--rootfs" options. - -2006-06-12 Daniel Baumann - - * 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 - - * Added handling of md5sums. - -2006-06-09 Marco Amadori - - * Added splashy support. - * Added ext2 rootfs support. - * Added external hook and path support. - * Swiched to getopt. - -2006-06-02 Daniel Baumann - - * Added patch from Jason D. Clinton : - - Added netboot flavour. - - Thanks to SafeDesk Solutions . - -2006-06-01 Daniel Baumann - - * Moved syslinux inside the chroot. - -2006-05-31 Daniel Baumann - - * Added kde-*i18n and standard-i18n lists. - -2006-05-28 Daniel Baumann - - * Added patch from Frederic Lehobey : - - Added locales to LIVE_PACKAGES. - - Added LIVE_MIRROR_KEY, LIVE_REPOSITORY, LIVE_REPOSITORY_KEY, and - LIVE_BOOTAPPEND. - -2006-05-27 Daniel Baumann - - * Initial release. diff --git a/HISTORY b/HISTORY deleted file mode 100644 index 5690ea4..0000000 --- a/HISTORY +++ /dev/null @@ -1,16 +0,0 @@ -Milestones of Debian Live -------------------------- - -2006-02-14: Initial idea -http://blog.daniel-baumann.ch/2006/02/14#20060214_debian-live-initiative - -2006-03-16: First CD images available -http://lists.alioth.debian.org/pipermail/debian-live-devel/2006-March/000048.html - -2006-06-02: First netboot images available - -2007-02-05: Image autobuilder in place -http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-February/000764.html - -2007-02-10: First USB images available -http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-February/000790.html diff --git a/Makefile b/Makefile index 084e1a4..02ab179 100644 --- a/Makefile +++ b/Makefile @@ -1,58 +1,30 @@ -# Makefile +#!/usr/bin/make -f all: install install: - @# Install main script - install -D -m 0755 src/main.sh $(DESTDIR)/usr/sbin/make-live + # Installing executables + mkdir -p $(DESTDIR)/usr/bin + cp helpers/lh_* helpers/make-live $(DESTDIR)/usr/bin - @# Install configuration file - install -D -m 0644 src/config $(DESTDIR)/etc/make-live.conf + # Installing shared data + mkdir -p $(DESTDIR)/usr/share/live-helper + cp -r functions hooks includes lists templates $(DESTDIR)/usr/share/live-helper - @# Install package lists - install -d -m 0755 $(DESTDIR)/usr/share/make-live/lists - install -m 0644 src/lists/* $(DESTDIR)/usr/share/make-live/lists - - @# Install flavour hooks - install -d -m 0755 $(DESTDIR)/usr/share/make-live/hooks - install -m 0644 src/hooks/* $(DESTDIR)/usr/share/make-live/hooks - - @# Install sub scripts - install -d -m 0755 $(DESTDIR)/usr/share/make-live/scripts - install -m 0755 src/scripts/*.sh $(DESTDIR)/usr/share/make-live/scripts - - @# Install templates - cp -r templates $(DESTDIR)/usr/share/make-live - - @# Install documentation - install -d -m 0755 $(DESTDIR)/usr/share/doc/live-package - install -m 0644 doc/*.txt $(DESTDIR)/usr/share/doc/live-package - - @# Install manpages - install -d -m 0755 $(DESTDIR)/usr/share/man/man5 - install -m 0644 doc/man/*.5 $(DESTDIR)/usr/share/man/man5 - install -d -m 0755 $(DESTDIR)/usr/share/man/man8 - install -m 0644 doc/man/*.8 $(DESTDIR)/usr/share/man/man8 - - $(MAKE) -C helpers install + # Installing documentation + mkdir -p $(DESTDIR)/usr/share/doc/live-helper + cp -r COPYING doc/* $(DESTDIR)/usr/share/doc/live-helper uninstall: - @# Remove main script - rm -f $(DESTDIR)/usr/sbin/make-live - - @# Remove configuration file - rm -f $(DESTDIR)/etc/make-live.conf - - @# Remove shared data - rm -rf $(DESTDIR)/usr/share/make-live + # Uninstalling executables + rm -f $(DESTDIR)/usr/bin/lh_* $(DESTDIR)/usr/bin/make-live - @# Remove documentation - rm -rf $(DESTDIR)/usr/share/doc/live-package + # Uninstalling shared data + rm -rf $(DESTDIR)/usr/share/live-helper - @# Remove manpages - rm -f $(DESTDIR)/usr/share/man/man5/make-live.* - rm -f $(DESTDIR)/usr/share/man/man8/make-live.* + # Uninstalling documentation + rm -rf $(DESTDIR)/usr/share/doc/live-helper - $(MAKE) -C helpers uninstall +clean: -reinstall: uninstall install +reinstall: uninstall install diff --git a/README b/README deleted file mode 100644 index 771c4e2..0000000 --- a/README +++ /dev/null @@ -1,12 +0,0 @@ -Debian Live Framework: make-live -================================ - -make-live is a utility to build Debian Live systems. It takes a Debian mirror as -an input and outputs a live system image (ISO image for CDs and DVDs, tarball -for netboot, or images for USB sticks). make-live is still in the early stage of -development, but has basic functionality and can be run successfully. - -More information about Debian Live can be found at: - - * - * diff --git a/TODO b/TODO deleted file mode 100644 index bec431f..0000000 --- a/TODO +++ /dev/null @@ -1,10 +0,0 @@ -Todo: - - * output hiding - * d-i/g-i integration - * documentation - - * l10n flags - * --disable-daemons - - * general source tarballs diff --git a/debian/changelog b/debian/changelog index 907eb05..053e68a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,208 +1,5 @@ -live-package (0.99.26-1) unstable; urgency=low +live-helper (1.0~a1-1) unstable; urgency=low - * New upstream release. + * Initial release, replacing live-package. - -- Daniel Baumann Fri, 9 Mar 2007 12:27:00 +0100 - -live-package (0.99.25-1) unstable; urgency=low - - * New upstream release. - - -- Daniel Baumann Fri, 9 Mar 2007 01:49:00 +0100 - -live-package (0.99.24-1) unstable; urgency=low - - * New upstream release: - - adds LIVE_INCLUDE_CHROOT to the manual exported variables as reported by - Mathieu Geli (Closes: #412325). - - -- Daniel Baumann Sun, 3 Mar 2007 12:25:00 +0100 - -live-package (0.99.23-1) unstable; urgency=low - - * New upstream release. - - -- Daniel Baumann Wed, 21 Feb 2007 22:08:00 +0100 - -live-package (0.99.22-1) unstable; urgency=low - - * New upstream release: - - updates manpage (Closes: #411008). - - -- Daniel Baumann Fri, 16 Feb 2007 20:38:00 +0100 - -live-package (0.99.21-1) unstable; urgency=low - - * New upstream release. - - -- Daniel Baumann Mon, 12 Feb 2007 15:06:00 +0100 - -live-package (0.99.20-1) unstable; urgency=low - - * New upstream release: - - Fixed manual pruning in minimal flavour as suggested by - Bas Wijnen (Closes: #410040). - - -- Daniel Baumann Thu, 1 Feb 2007 17:35:00 +0100 - -live-package (0.99.19-1) unstable; urgency=low - - * New upstream release. - - -- Daniel Baumann Wed, 31 Jan 2007 12:38:00 +0100 - -live-package (0.99.18-1) unstable; urgency=low - - * New upstream release. - - -- Daniel Baumann Thu, 25 Jan 2007 08:29:00 +0100 - -live-package (0.99.17-1) unstable; urgency=low - - * New upstream release. - - -- Daniel Baumann Wed, 24 Jan 2007 22:18:00 +0100 - -live-package (0.99.16-1) unstable; urgency=low - - * New upstream release. - - -- Daniel Baumann Thu, 18 Jan 2007 16:25:00 +0100 - -live-package (0.99.15-1) unstable; urgency=low - - * New upstream release: - - switched default distribution back to unstable, as unstable is usable - again from the kernel point of view (Closes: #400457). - - added file to the minimal package list (Closes: #400485). - - -- Daniel Baumann Tue, 16 Jan 2007 21:24:00 +0100 - -live-package (0.99.14-3) unstable; urgency=high - - * Adding workaround for new xorg packages by including xserver-xorg-input-all - and xserver-xorg-video-all in all X11 package lists. See #405639 for more - information. - * Adding xdebconfigurator to all X11 package lists. - - -- Daniel Baumann Fri, 5 Jan 2007 22:34:00 +0100 - -live-package (0.99.14-2) unstable; urgency=high - - * Adding workaround for initrd backup files (Closes: #404314). - - -- Daniel Baumann Thu, 4 Jan 2007 20:52:00 +0100 - -live-package (0.99.14-1) unstable; urgency=medium - - * New upstream release: - - fixed typo for policy-rc.d hack (Closes: #396813), thanks to - Markus Bauer . - - corrected manpage section (Closes: #396083), thanks to - Sune Vuorela . - - fixes script sourcing to exclude files in .svn (Closes: #396861), - thanks to Markus Bauer . - - -- Daniel Baumann Mon, 6 Nov 2006 00:00:00 +0200 - -live-package (0.99.13-1) unstable; urgency=medium - - * New upstream release. - - -- Daniel Baumann Mon, 30 Oct 2006 00:00:00 +0200 - -live-package (0.99.12-1) unstable; urgency=medium - - * New upstream release. - - Reverted mangling of LIVE_DISTRIBUTION for sources.list generation - (Closes: #394226). - - -- Daniel Baumann Mon, 23 Oct 2006 00:00:00 +0200 - -live-package (0.99.11-1) unstable; urgency=medium - - * New upstream release. - - -- Daniel Baumann Mon, 16 Oct 2006 00:00:00 +0200 - -live-package (0.99.10-1) unstable; urgency=medium - - * New upstream release. - - -- Daniel Baumann Mon, 9 Oct 2006 00:00:00 +0200 - -live-package (0.99.9-1) unstable; urgency=medium - - * New upstream release: - - adds support for custom repositories (Closes: #387068). - - using proxy for chroot creating too (Closes: #390378). - - -- Daniel Baumann Mon, 2 Oct 2006 00:00:00 +0200 - -live-package (0.99.8-1) unstable; urgency=medium - - * New upstream release. - - -- Daniel Baumann Mon, 25 Sep 2006 00:00:00 +0200 - -live-package (0.99.7-1) unstable; urgency=medium - - * New upstream release: - - removes the now outdated handling of testing specific kernels - (Closes: #387562). - - added fix from Bas Wijnen for space handling in - arguments (Closes: #388204). - - fixes package list handling similar to the fix suggested by Alex Owen - (Closes: #388060). - - -- Daniel Baumann Mon, 18 Sep 2006 00:00:00 +0200 - -live-package (0.99.6-1) unstable; urgency=medium - - * New upstream release: - - fixing netboot. - - -- Daniel Baumann Mon, 11 Sep 2006 00:00:00 +0200 - -live-package (0.99.5-1) unstable; urgency=low - - * New upstream release. - * Set maintainer to the project list. - - -- Daniel Baumann Mon, 4 Sep 2006 00:00:00 +0200 - -live-package (0.99.4-1) unstable; urgency=low - - * New upstream release: - - Added patch from Alex Owen to update pxelinux.cfg - for NFS root in casper (Closes: #380512). - - Temporarily hacks xorg configuration file to remove BusID and set - default driver to vesa (Closes: #382391). - - -- Daniel Baumann Mon, 28 Aug 2006 00:00:00 +0200 - -live-package (0.99.3-1) unstable; urgency=low - - * New upstream release: - - fixed configuration file handling (Closes: #384598). - * Update long descriptiong (Closes: #382473). - - -- Daniel Baumann Mon, 21 Aug 2006 00:00:00 +0200 - -live-package (0.99.2-1) unstable; urgency=low - - * New upstream release. - - -- Daniel Baumann Mon, 31 Jul 2006 00:00:00 +0200 - -live-package (0.99.1-1) unstable; urgency=low - - * New upstream release. - - -- Daniel Baumann Mon, 24 Jul 2006 00:00:00 +0200 - -live-package (0.99-1) unstable; urgency=low - - * Initial release. - - -- Daniel Baumann Mon, 17 Jul 2006 00:00:00 +0200 + -- Daniel Baumann Mon, 12 Mar 2007 00:00:00 +0100 diff --git a/debian/control b/debian/control index 181f4f8..3a4f192 100644 --- a/debian/control +++ b/debian/control @@ -1,4 +1,4 @@ -Source: live-package +Source: live-helper Section: misc Priority: optional Maintainer: Debian Live @@ -6,16 +6,21 @@ Uploaders: Daniel Baumann , Marco Amadori = 5) Standards-Version: 3.7.2 -Package: live-package +Package: live-helper Architecture: all -Depends: cdebootstrap, genext2fs, genisoimage | mkisofs, squashfs-tools -Recommends: aespipe +Depends: cdebootstrap | debootstrap, genext2fs, genisoimage | mkisofs, squashfs-tools +Conflicts: live-package +Replaces: live-package +Suggests: aesloop Provides: make-live -Description: utility to build Debian Live systems - make-live is a utility to build Debian Live systems. It takes a Debian mirror - as an input and outputs a live system image (ISO image for CDs and DVDs, - tarballs for netboot, or images for USB sticks). make-live is still in the - early stage of development, but has basic functionality and can be run - successfully. +Description: Debian Live helper programs + Live-helper is a collection of programs that can be used to build Debian Live + system images. The philosophy behind live-helper is to provide a collection of + small, simple, and easily understood tools that can be used in your own program + to automate building of a Live system. + . + A typical program that uses live-helper will call several live-helper commands + in sequence. Live-helper commands are all named with a "lh_" prefix. Examples + of such a program that uses live-helper is make-live (included here). . Homepage: diff --git a/debian/copyright b/debian/copyright index a5b3f42..7e2baf5 100644 --- a/debian/copyright +++ b/debian/copyright @@ -1,9 +1,9 @@ This package was debianized by Daniel Baumann on -Mon, 17 Jul 2006 00:00:00 +0200. +Mon, 12 Mar 2007 00:00:00 +0100. It was downloaded from . -Upstream: Debian Live Project +Upstream Author: Debian Live License: @@ -27,7 +27,7 @@ License: 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): +License (contrib/syslinux-splash/*, templates/syslinux/splash.rle): The derivated splash for Debian Live was done by Daniel Baumann from the original of Mark Riedesel. Daniels own diff --git a/debian/cron.daily b/debian/cron.daily deleted file mode 100644 index db65e90..0000000 --- a/debian/cron.daily +++ /dev/null @@ -1,103 +0,0 @@ -#!/bin/sh - -# Check for make-live executable -if [ ! -x /usr/sbin/make-live ] -then - exit 0 -fi - -# Check for make-live default -if [ -r /etc/default/make-live ] -then - . /etc/default/make-live -else - echo "E: /etc/default/make-live missing." - exit 1 -fi - -# Check for autobuild -if [ "${AUTOBUILD}" = "false" ] -then - exit 0 -fi - -# Check for build directory -if [ ! -d "${AUTOBUILD_DIRECTORY}" ] -then - mkdir -p "${AUTOBUILD_DIRECTORY}" -else - # FIXME: maybe we should just remove the left overs. - echo "E: ${AUTOBUILD_DIRECTORY} needs cleanup." - exit 1 -fi - -# Process image autobuilding -cd "${AUTOBUILD_DIRECTORY}" - -for AUTOBUILD_DISTRIBUTION in ${AUTOBUILD_DISTRIBUTIONS} -do - for AUTOBUILD_PACKAGE_LIST in ${AUTOBUILD_PACKAGE_LISTS} - do - if [ ! -f "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/log/debian-live-${AUTOBUILD_DISTRIBUTION}-${AUTOBUILD_ARCHITECTURE}-${AUTOBUILD_PACKAGE_LIST}_${AUTOBUILD_DATE}-iso-log.txt ] - then - # Generating images - mkdir debian-live - make-live -t iso -d ${AUTOBUILD_DISTRIBUTION} -p ${AUTOBUILD_PACKAGE_LIST} -m ${LIVE_MIRROR} ${AUTOBUILD_OPTIONS} > debian-live/log.txt 2>&1 - fi - - if [ -f debian-live/binary.iso ] && [ -f debian-live/source.iso ] - then - # Moving logs - mkdir -p "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/log - mv debian-live/log.txt "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/log/debian-live-${AUTOBUILD_DISTRIBUTION}-${AUTOBUILD_ARCHITECTURE}-${AUTOBUILD_PACKAGE_LIST}_${AUTOBUILD_DATE}-iso-log.txt - mv debian-live/packages.txt "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/log/debian-live-${AUTOBUILD_DISTRIBUTION}-${AUTOBUILD_ARCHITECTURE}-${AUTOBUILD_PACKAGE_LIST}_${AUTOBUILD_DATE}-iso-packages.txt - - # Moving images - mkdir -p "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/${AUTOBUILD_ARCHITECTURE} - mv debian-live/binary.iso "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/${AUTOBUILD_ARCHITECTURE}/debian-live-${AUTOBUILD_DISTRIBUTION}-${AUTOBUILD_ARCHITECTURE}-${AUTOBUILD_PACKAGE_LIST}.iso - - mkdir -p "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/source - mv debian-live/source.iso "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/source/debian-live-${AUTOBUILD_DISTRIBUTION}-source-${AUTOBUILD_PACKAGE_LIST}.iso - fi - - # Cleanup - rm -rf debian-live - - if [ ! -f "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/log/debian-live-${AUTOBUILD_DISTRIBUTION}-${AUTOBUILD_ARCHITECTURE}-${AUTOBUILD_PACKAGE_LIST}_${AUTOBUILD_DATE}-usb-log.txt ] - then - # Generating images - mkdir debian-live - make-live -t usb -d ${AUTOBUILD_DISTRIBUTION} -p ${AUTOBUILD_PACKAGE_LIST} -m ${LIVE_MIRROR} ${AUTOBUILD_OPTIONS} > debian-live/log.txt 2>&1 - fi - - if [ -f debian-live/binary.img ] - then - # Moving logs - mkdir -p "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/log - mv debian-live/log.txt "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/log/debian-live-${AUTOBUILD_DISTRIBUTION}-${AUTOBUILD_ARCHITECTURE}-${AUTOBUILD_PACKAGE_LIST}_${AUTOBUILD_DATE}-usb-log.txt - mv debian-live/packages.txt "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/log/debian-live-${AUTOBUILD_DISTRIBUTION}-${AUTOBUILD_ARCHITECTURE}-${AUTOBUILD_PACKAGE_LIST}_${AUTOBUILD_DATE}-usb-packages.txt - - # Moving images - mkdir -p "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/${AUTOBUILD_ARCHITECTURE} - mv debian-live/binary.img "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/${AUTOBUILD_ARCHITECTURE}/debian-live-${AUTOBUILD_DISTRIBUTION}-${AUTOBUILD_ARCHITECTURE}-${AUTOBUILD_PACKAGE_LIST}.img - fi - - # Cleanup - rm -rf debian-live - done -done - -# Cleanup -umount -f "${AUTOBUILD_DIRECTORY}"/debian-live/chroot/proc > /dev/null 2>&1 -rm -rf "${AUTOBUILD_DIRECTORY}" - -# MD5SUMS -for DIRECTORY in "${AUTOBUILD_SERVER}"/daily-builds/${AUTOBUILD_DATE}/* -do - cd "${DIRECTORY}" - md5sum * > MD5SUMS -done - -# Current symlink -rm -f "${AUTOBUILD_SERVER}"/daily-builds/current -ln -s ${AUTOBUILD_DATE} "${AUTOBUILD_SERVER}"/daily-builds/current diff --git a/debian/default b/debian/default deleted file mode 100644 index 43d17d7..0000000 --- a/debian/default +++ /dev/null @@ -1,17 +0,0 @@ -# Defaults for make-live cron.daily - -AUTOBUILD="false" - -AUTOBUILD_DISTRIBUTIONS="etch sid" -AUTOBUILD_PACKAGE_LISTS="standard kde-desktop gnome-desktop xfce-desktop" -AUTOBUILD_OPTIONS="--with-source" - -AUTOBUILD_DIRECTORY="/srv/tmp/make-live" -AUTOBUILD_SERVER="/srv/debian-live" -AUTOBUILD_ARCHITECTURE="`dpkg --print-architecture`" -AUTOBUILD_DATE="`date +%Y%m%d`" - -LIVE_MIRROR="http://ftp.debian.org/debian/" - -# Source /etc/make-live.conf -# . /etc/make-live.conf diff --git a/debian/docs b/debian/docs deleted file mode 100644 index 2b0402c..0000000 --- a/debian/docs +++ /dev/null @@ -1,3 +0,0 @@ -AUTHORS -HISTORY -TODO diff --git a/debian/rules b/debian/rules index ef72dea..1d9b92c 100755 --- a/debian/rules +++ b/debian/rules @@ -3,8 +3,9 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 -upstream: # Needs svn - cd .. && svn co svn://svn.debian.org/debian-live/dists/trunk/live-package || exit 0 +upstream: + # Needs: subversion + cd .. && svn co svn://svn.debian.org/debian-live/dists/trunk/live-helper || exit 0 find . -type d -name .svn -exec rm -rf {} \; || exit 0 build: @@ -22,18 +23,22 @@ install: build dh_installdirs # Installing package - $(MAKE) install DESTDIR=$(CURDIR)/debian/live-package - install -D debian/default debian/live-package/etc/default/make-live + $(MAKE) install DESTDIR=$(CURDIR)/debian/live-helper + + # Removing double files + rm -f debian/live-helper/usr/share/doc/live-helper/COPYING + rm -f debian/live-helper/usr/share/doc/live-helper/ChangeLog + mv debian/live-helper/usr/share/doc/live-helper/ChangeLog.old \ + debian/live-helper/usr/share/doc/live-helper/changelog.old binary-arch: build install binary-indep: build install dh_testdir dh_testroot - dh_installchangelogs ChangeLog + dh_installchangelogs doc/ChangeLog dh_installdocs dh_install - dh_installcron dh_compress dh_fixperms dh_installdeb diff --git a/doc/AUTHORS b/doc/AUTHORS new file mode 100644 index 0000000..ce0a01a --- /dev/null +++ b/doc/AUTHORS @@ -0,0 +1,4 @@ +Main Authors: + + * Daniel Baumann + * Marco Amadori diff --git a/doc/CREDITS b/doc/CREDITS new file mode 100644 index 0000000..cf8a3d4 --- /dev/null +++ b/doc/CREDITS @@ -0,0 +1,30 @@ +Patches (alphabetical order): + + * Alex Owen + * Bas Wijnen + * Ben Armstrong + * Cedric Lucantis + * Frederic Lehobey + * Guerkan Senguen + * Hadar Weiss + * Jason D. Clinton + * Kai Hendry + * Marcelo D. Re + * Markus Bauer + * Mathieu Geli + * Otavio Salvador + * Scott Edwards + * Sebastian Raveau + +Donations (alphaetical order): + + * Gracie + +Special thanks (alphabetical order): + + * Ben Armstrong for his IRC support. + * Jason D. Clinton for his work on netboot type. + * Otavio Salvador for his QA patches. + * Sebastian Raveau for his work on encryption + support. + * Scott Edwards for his work on d-i/g-i integration. diff --git a/doc/ChangeLog b/doc/ChangeLog new file mode 100644 index 0000000..fff6279 --- /dev/null +++ b/doc/ChangeLog @@ -0,0 +1,4 @@ +2007-03-12 Daniel Baumann + + * Rewritten live-package. + * Uploaded 1.0~a1-1. diff --git a/doc/ChangeLog.old b/doc/ChangeLog.old new file mode 100644 index 0000000..03dba64 --- /dev/null +++ b/doc/ChangeLog.old @@ -0,0 +1,474 @@ +2007-03-10 Daniel Baumann + + * Added knoppix and knoppix-dvd package lists. + +2007-03-09 Daniel Baumann + + * Getting free loopdevice from inside the chroot, not outside. + +2007-03-09 Daniel Baumann + + * Added kbd to all !minimal lists. + * Uploaded 0.99.25. + +2007-03-08 Otavio Salvador + + * helpers/lh_configapt: Fix aptitude configuration to really avoid + recommended packages to get installed. + * src/scripts/02defaults.sh: Export LIVE_ISOLINUX_SPLASH. + +2007-03-04 Daniel Baumann + + * Replaced removal of kernel on minimal flavours with excludes on the + mksquashfs call. + * Added LIVE_INCLUDE_CHROOT to the manual exported variables as reported + by Mathieu Geli . + * Exported CODENAME_* manually as reported by Cédric Lucantis + . + * Fixed typo s/aptiude/aptitude/ as reported by Kai Hendry + . + * Uploaded 0.99.24. + +2007-02-22 Daniel Baumann + + * Added xresprobe to all x11 lists. + +2007-02-22 Daniel Baumann + + * Applied patches from Otavio Salvador : + - add and cleanup variable exporting in defaults. + - add LIVE_BOOTSTRAP_CONFIG to lh_debootstrap. + * Uploaded 0.99.23. + +2007-02-21 Daniel Baumann + + * Added gnome-junior, kde-junior and xfce-junior lists. + * Uploaded 0.99.22. + +2007-02-19 Daniel Baumann + + * Fixed manifest. + +2007-02-15 Daniel Baumann + + * Applied patch from Sebastian Raveau to + add support for filesystem images encrypted with loop-aes. + +2007-02-13 Daniel Baumann + + * Broken out scripts into modularized lh_* subscripts. + +2007-02-12 Daniel Baumann + + * Added some code as suggested by Alex Owen to + check if the depends (syslinux, memtest etc.) are intentionally + installed in the chroot, and hence, don't remove them. + * Moved some depends into the chroot. + * Uploaded 0.99.21. + +2007-02-11 Daniel Baumann + + * Added mini flavour. + +2007-02-10 Daniel Baumann + + * Added legacy code for genisoimage. + * Uploaded 0.99.20. + +2007-02-09 Daniel Baumann + + * Added usb type. + +2007-02-08 Daniel Baumann + + * Added desktop task to the *-desktop flavours. + +2007-02-07 Daniel Baumann + + * Extended cron job a bit. + * Fixed manual pruning in minimal flavour as suggested by Bas Wijnen + + +2007-02-02 Daniel Baumann + + * Added "--without-daemons". + +2007-02-01 Daniel Baumann + + * Added "--tasks". + * Added desktop-base to all desktop package lists. + +2007-01-31 Daniel Baumann + + * Changed vars in autobuilding script to be able to source + make-live.conf. + * Uploaded 0.99.19. + +2007-01-30 Daniel Baumann + + * Added cron job for autobuilding images. + +2007-01-25 Daniel Baumann + + * Added additional pruning to minimal flavour. + * Using interactive frontend while processing --hook. + * Uploaded 0.99.18. + +2007-01-24 Daniel Baumann + + * Applied patches from Otavio Salvador : + - adding "--keyring" flag. + - adding LIVE_DISK_VOLUME. + - adding start-stop-daemon wrapper to avoid daemons to be started. + - adding workaround to prevent binfmt locking /proc. + - adding LIVE_ISOLINUX_SPLASH. + * Uploaded 0.99.17. + +2007-01-19 Daniel Baumann + + * Replacing mkisofs with genisoimage. + +2007-01-18 Daniel Baumann + + * Cleanups. + * Uploaded 0.99.16. + +2007-01-16 Daniel Baumann + + * Switched default distribution back to unstable, as unstable is usable + again from the kernel point of view. + * Added file to the minimal package list. + * Uploaded 0.99.15. + +2007-01-04 Daniel Baumann + + * Added workaround for new xorg packages by including + xserver-xorg-input-all and xserver-xorg-video-all in all X11 package + lists. See #405639 for more information. + * Added xdebconfigurator to all X11 package lists. + * Adding workaround for initrd backup files. + +2006-11-06 Daniel Baumann + + * Uploaded 0.99.14. + +2006-11-05 Daniel Baumann + + * Applied patch from Markus Bauer : + - fixing script sourcing to exclude files in .svn + +2006-11-03 Daniel Baumann + + * Fixed typo in the policy-rc.d hack. + +2006-11-02 Daniel Baumann + + * Using aptitude instead of apt-get. + * Added '--with-recommends' and '--without-recommends'. + +2006-11-01 Daniel Baumann + + * Fixed regression when using -d ${CODENAME} wrt/ kernel packages. + +2006-10-30 Daniel Baumann + + * Uploaded 0.99.13. + +2006-10-29 Daniel Baumann + + * Added minimal-net flavour. + +2006-10-28 Daniel Baumann + + * Added console-common to standard selection. + +2006-10-27 Daniel Baumann + + * Added patch from Otavio Salvador : + - fixing preseeding error-handling. + +2006-10-26 Daniel Baumann + + * Added gnustep package selection based on the suggestion of + Guerkan Senguen . + +2006-10-25 Daniel Baumann + + * Applied patch from Marcelo D. Re : + - skip deb-src source-list entries when building images with + --without-source. + * Applied patches from Otavio Salvador : + - adding '--bootstrap-config' to support cdebootstraps + '--suite-config'. + - allowing override of ${BASE}. + - adjust sourcing of scripts, so that only the real scripts are + sourced and not other (backup) files. + - allowing override of kernel-packages. + * Reverted mangling of LIVE_DISTRIBUTION for sources.list generation. + +2006-10-23 Daniel Baumann + + * Uploaded 0.99.12. + +2006-10-18 Daniel Baumann + + * Autodetecting proxy now. + +2006-10-16 Daniel Baumann + + * Readded and slightly changed --clone and --preseed. + * Uploaded 0.99.11. + +2006-10-09 Daniel Baumann + + * Cleanups. + * Uploaded 0.99.10. + +2006-10-02 Daniel Baumann + + * Uploaded 0.99.9. + +2006-10-01 Daniel Baumann + + * Added multiple repositories. + * Using LIVE_PROXY_* also for bootstraping. + +2006-09-27 Daniel Baumann + + * Changing manpage section. + +2006-09-26 Daniel Baumann + + * Added default flavour hooks. + * minimal flavour does not install debian-archive-keyring to save space. + * Adjusted network patch. + +2006-09-25 Daniel Baumann + + * Removed now unused initramfs-tools hack. + * Simplified xorg check based on distribution rather than version. + * Added fix from Bas Wijnen for space handling in + arguments. + * Fixed package list handling similar to the fix suggested by Alex Owen + . + * Uploaded 0.99.8. + +2006-09-24 Marco Amadori + + * 13hack.sh: initramfs-tools hack, check added for xorg. + +2006-09-18 Daniel Baumann + + * Uploaded 0.99.7. + +2006-09-15 Daniel Baumann + + * Added eject to minimal package selection. + +2006-09-14 Daniel Baumann + + * Adjustements for linux 2.6.17 testing propagation. + +2006-09-11 Daniel Baumann + + * Uploaded 0.99.6. + +2006-09-08 Marco Amadori + + * 23net.sh: Fixed binary missing directory creation. + * templates/iso: Moved common files to templates/common. + +2006-09-07 Daniel Baumann + + * Minor cleanups. + * Fixed dist target. + +2006-09-06 Marco Amadori + + * 14chroot.sh, main.sh: Added manifest support. + * 23net.sh: Added 2 variables for basenames to ease readability. + * main.sh, 02default.sh: Modified Usage() uses. + +2006-09-04 Daniel Baumann + + * Uploaded 0.99.5. + +2006-09-03 Daniel Baumann + + * Added dist parameter to easily pull images for live.debian.net. + * Added "--output" to specify the image name prefix. + * Exclude iso templates for minimal flavour. + +2006-09-02 Daniel Baumann + + * Added experimental as distribution. + * Added source image generation. + * Using dpkg instead of dpkg-architecture, removed dpkg-dev dependency. + +2006-08-31 Daniel Baumann + + * Added "--disable-generic-indices" and "--enable-generic-indices". + * Fixed i18n lists. + * Rewritten all lists, comments are now possible. + * Lists must be now explicitly given with --package-list, no longer as + last argument of the make-live call. + * Setting default sources.list while the image generation, restoring + customized ones afterwards. + +2006-08-30 Daniel Baumann + + * Cleanups: + - moved 14patch_packages.sh to 13hack.sh. + - simplified 13hack.sh. + +2006-08-29 Marco Amadori + + * pxelinux.cfg: Updated to right defaults, first cifs then nfs or + select your favorite way. Rationale: /dev/nfs is for kernel + discovering, not for initramfs discover, casper will be just fine + with "netboot". + * 13chroot.sh, 14patch_packages.sh: Added a simple system for patching + packages, mainly for xserver-xorg so far. + +2006-08-28 Daniel Baumann + + * Updated documentation. + * Added patch from Alex Owen to update + pxelinux.cfg for NFS root in casper. + * Uploaded 0.99.4. + +2006-08-27 Daniel Baumann + + * Cleanups. + +2006-08-27 Marco Amadori + + * Added sysv init blocking policy. + +2006-08-22 Daniel Baumann + + * Reorganised sources. + * Added staging support. + * Cleaned up parameter names. + * testing is now supported. + +2006-08-21 Daniel Baumann + + * Uploaded 0.99.3. + +2006-08-02 Marco Amadori + + * Rewrote netboot support. + * Added support for pure directory rootfs images. + +2006-07-31 Daniel Baumann + + * Uploaded 0.99.2. + +2006-07-28 Daniel Baumann + + * Added DEBIAN_FRONTEND to chroots(), now completely non-interactive. + * Fixed wrong chroot patch. + +2006-07-27 Marco Amadori + + * Changed amd64 kernel naming scheme. + +2006-07-24 Daniel Baumann + + * Uploaded 0.99.1. + +2006-07-19 Daniel Baumann + + * Bugfixes. + +2006-07-18 Daniel Baumann + + * Added iso templates. + +2006-07-17 Daniel Baumann + + * Added chroot to 01-patch.sh. + * Added "--logfile". + * Uploaded 0.99. + +2006-07-01 Daniel Baumann + + * Added "--flavour". + +2006-06-28 Daniel Baumann + + * Added "--debug" and "--verbose". + +2006-06-23 Daniel Baumann + + * Rewritten manpages. + +2006-06-19 Marco Amadori + + * Added "--templates" options. + * Fixed some typos. + +2006-06-15 Daniel Baumann + + * General fixes. + +2006-06-18 Marco Amadori + + * Added "-a|--architecture" and "-p|--package-list" options. + * Reworked how lists works. + +2006-06-15 Daniel Baumann + + * General cleanup. + +2006-06-14 Marco Amadori + + * Re-added "-f|--filesystem". + +2006-06-12 Marco Amadori + + * Added "--conffile", "--preseed", "--clone", and "--rootfs" options. + +2006-06-12 Daniel Baumann + + * 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 + + * Added handling of md5sums. + +2006-06-09 Marco Amadori + + * Added splashy support. + * Added ext2 rootfs support. + * Added external hook and path support. + * Swiched to getopt. + +2006-06-02 Daniel Baumann + + * Added patch from Jason D. Clinton : + - Added netboot flavour. + - Thanks to SafeDesk Solutions . + +2006-06-01 Daniel Baumann + + * Moved syslinux inside the chroot. + +2006-05-31 Daniel Baumann + + * Added kde-*i18n and standard-i18n lists. + +2006-05-28 Daniel Baumann + + * Added patch from Frederic Lehobey : + - Added locales to LIVE_PACKAGES. + - Added LIVE_MIRROR_KEY, LIVE_REPOSITORY, LIVE_REPOSITORY_KEY, and + LIVE_BOOTAPPEND. + +2006-05-27 Daniel Baumann + + * Initial release. diff --git a/doc/NEWS b/doc/NEWS new file mode 100644 index 0000000..3b7dbc7 --- /dev/null +++ b/doc/NEWS @@ -0,0 +1,27 @@ +News: + + * 2006-02-14: Project announcement. + http://blog.daniel-baumann.ch/2006/02/14#20060214_debian-live-initiative + + * 2006-02-28: Setup project resources. + http://blog.daniel-baumann.ch/2006/02/28#20060228_debian-live-resources + + * 2006-03-16: Added support for ISO image generation. + http://lists.alioth.debian.org/pipermail/debian-live-devel/2006-March/000048.html + + * 2006-06-02: Added support for netboot image generation. + http://lists.alioth.debian.org/pipermail/debian-live-devel/2006-May/000185.html + + * 2006-07-17: Uploaded live-package to Debian unstable. + http://packages.debian.org/changelogs/pool/main/l/live-package/current/changelog#versionversion0.99-1 + + * 2007-02-05: Setup image autobuild server. + http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-February/000764.html + + * 2007-02-10: Added support for USB image generation. + http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-February/000790.html + + * 2007-02-17: Added support for encrypted live filesystem. + http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-February/000836.html + + * 2007-03-12: Uploaded live-helper to Debian unstable. diff --git a/doc/README b/doc/README new file mode 100644 index 0000000..dbccc7c --- /dev/null +++ b/doc/README @@ -0,0 +1,84 @@ + * lh_config + + * lh_bootstrap + |_ lh_cdebootstrap | lh_debootstrap + + * lh_chroot + |_ lh_chroot_proc install + |_ lh_chroot_sysfs install + |_ lh_chroot_debianchroot install + |_ lh_chroot_sysvrc install + |_ lh_chroot_hosts install + |_ lh_chroot_resolv install + |_ lh_chroot_apt install + |_ lh_chroot_sources install + |_ lh_chroot_linuximage install + | + |_ lh_chroot_tasks + |_ lh_chroot_packageslists + |_ lh_chroot_packages + |_ lh_chroot_localpackages + |_ lh_chroot_localpackageslist + |_ lh_chroot_localization + |_ lh_chroot_hacks + |_ lh_chroot_localincludes + |_ lh_chroot_sysvinit + |_ lh_chroot_hooks + |_ lh_chroot_localhooks + |_ lh_chroot_symlinks + | + |_ lh_chroot_linuximage remove + |_ lh_chroot_sources remove + |_ lh_chroot_apt remove + |_ lh_chroot_resolv remove + |_ lh_chroot_hosts remove + |_ lh_chroot_sysvrc remove + |_ lh_chroot_debianchroot remove + |_ lh_chroot_sysfs remove + |_ lh_chroot_proc remove + + * lh_binary + |_ lh_binary_rootfs + |_ lh_binary_manifest + |_ lh_binary_encryption + | + |_ lh_chroot_proc install + |_ lh_chroot_sysfs install + |_ lh_chroot_hosts install + |_ lh_chroot_resolv install + |_ lh_chroot_sources install + | + |_ lh_binary_linuximage + |_ lh_binary_memtest86 + |_ lh_binary_syslinux + |_ lh_binary_includes + |_ lh_binary_localincludes + |_ lh_binary_md5sum + | + |_ lh_binary_iso + |_ lh_binary_net + |_ lh_binary_usb + | + |_ rm -f .stage/chroot_sources + |_ lh_chroot_resolv remove + |_ lh_chroot_hosts remove + |_ lh_chroot_sysfs remove + |_ lh_chroot_proc remove + + * lh_source + |_ lh_chroot_hosts install + |_ lh_chroot_resolv install + |_ lh_chroot_sources install + | + |_ lh_source_download + | + |_ lh_source_generic + |_ lh_source_iso + |_ lh_source_net + |_ lh_source_usb + | + |_ rm -f .stage/chroot_sources + |_ lh_chroot_resolv remove + |_ lh_chroot_hosts remove + + * lh_clean diff --git a/doc/TODO b/doc/TODO new file mode 100644 index 0000000..b1c0faf --- /dev/null +++ b/doc/TODO @@ -0,0 +1,13 @@ +Fixme: + + * check all Require_stagefile calls + * make helpers call required stuff when needed + * integrate lh_chroot_hacks + * cleanup variable names + * do not use full-path anymore + +Todo: + + * write manpage and documentation + * write lh_binary_di and lh_binary_gi + * write lh_binary_grub diff --git a/doc/faq.txt b/doc/faq.txt deleted file mode 100644 index e83dcd6..0000000 --- a/doc/faq.txt +++ /dev/null @@ -1,9 +0,0 @@ -Debian Live Framework: Frequently Asked Questions (FAQ) -======================================================= - -Q: What is the root password? -A: There is none. You can switch to root with 'sudo su -' or set a password with - 'sudo passwd'. - -Q: What is the user password? -A: The user password for casper is 'live'. diff --git a/doc/man/make-live.8 b/doc/man/make-live.8 deleted file mode 100644 index ee2d8d9..0000000 --- a/doc/man/make-live.8 +++ /dev/null @@ -1,215 +0,0 @@ -.TH MAKE-LIVE 8 "Mon, 4 Sep 2006" "0.99" "Debian Live framework" - -.SH NAME -make-live \- utility to build Debian Live systems - -.SH SYNOPSIS -.B make-live -.RB [\| \-a \||\| \-\-architecture -.IR ARCHITECTURE \|] -.RB [\| \-b \||\| \-\-bootappend -.IR KERNEL_PARAMETER \||\| \|"KERNEL_PARAMETERS\|" \|] -.RB [\| \-\-config -.IR FILE \|] -.RB [\| \-\-clone -.IR DIRECTORY \|] -.RB [\| \-c \||\| \-\-chroot -.IR DIRECTORY \|] -.RB [\| \-d \||\| \-\-distribution -.IR DISTRIBUTION \|] -.RB [\| \-e \||\| \-\-encryption -.IR ALGORITHM \|] -.RB [\| \-\-filesystem -.IR FILESYSTEM \|] -.RB [\| \-f \||\| \-\-flavour -.IR BOOTSTRAP_FLAVOUR \|] -.RB [\| \-\-hook -.IR COMMAND \||\| \|"COMMANDS\|" \||\|| FILE \|] -.RB [\| \-\-include-chroot -.IR FILE \||\| DIRECTORY \|] -.RB [\| \-\-include-image -.IR FILE \||\| DIRECTORY \|] -.RB [\| \-k \||\| \-\-kernel -.IR KERNEL_FLAVOUR \|] -.RB [ \-\-manifest -.IR PACKAGE \|] -.RB [\| \-m \||\| \-\-mirror -.IR URL \|] -.RB [\| \-\-mirror-security -.IR URL \|] -.RB [\| \-\-packages -.IR PACKAGE \||\| \|"PACKAGES\|" \|] -.RB [\| \-\-preseed -.IR FILE \|] -.RB [\| \-p \||\| \-\-package-list -.IR LIST \||\| FILE \|] -.RB [\| \-\-proxy-ftp -.IR URL \|] -.RB [\| \-\-proxy-http -.IR URL \|] -.RB [\| \-r \||\| \-\-root -.IR DIRECTORY \|] -.RB [\| \-s \||\| \-\-sections -.IR SECTION \||\| \|"SECTIONS\|" \|] -.RB [\| \-\-server-address -.IR HOSTNAME \||\| IP \|] -.RB [\| \-\-server-path -.IR DIRECTORY \|] -.RB [\| \-\-templates -.IR DIRECTORY \|] -.RB [\| \-t \||\| \-\-type -.IR TYPE \|] -.RB [\| \-\-with-generic-indices \|] -.RB [\| \-\-without-generic-indices \|] -.RB [\| \-\-with-source \|] -.RB [\| \-\-without-source \|] -.PP -.B make-live -.RB \-h \||\| \-\-help -.br -.B make-live -.RB \-u \||\| \-\-usage -.br -.B make-live -.RB \-v \||\| \-\-version - -.SH DESCRIPTION -make-live is a utility to build Debian Live systems. It takes a Debian mirror as an input and outputs a live system image (ISO image for CDs and DVDs, or tarball for netboot). make-live is still in the early stage of development, but has basic functionality and can be run successfully. - -.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 (Default: `dpkg-architecture -qDEB_BUILD_ARCH`). -.TP -.BI "\-b, \-\-bootappend " KERNEL_PARAMETER \||\| \|"KERNEL_PARAMETERS\|" -passes kernel parameters to the bootloader, e.g. 'quiet' or 'vga=792' etc. Instead of this flag, the environment variable LIVE_BOOTAPPEND can be used (Default: empty). -.TP -.BI "\-\-config " FILE -uses another configuration file in addition to the default one. Settings in the additional configuration file do overwrite the settings from /etc/make-live.conf. Instead of this flag, the environment variable LIVE_CONFIG can be used (Default: /etc/make-live.conf). -.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 "\-c, \-\-chroot " DIRECTORY -specifies the chroot directory. Instead of this flag, the environment variable LIVE_CHROOT (Default: $LIVE_ROOT/chroot"). -.TP -.BI "\-d, \-\-distribution " DISTRIBUTION -specifies the distribution to be used. Allowed values are distributions names like unstable and testing, or codenames like sid and etch. Instead of this flag, the environment variable LIVE_DISTRIBUTION can be used (Default: sid). -.TP -.BI "\-e, \-\-encryption " ALGORITHM -specifies the filesystem encryption algorithm. Does not work if -t is set to plain. Instead of this flag, the environment variable LIVE_ENCRYPTION can be used (Default: empty). Valid algorithms are: AES128, AES192 and AES256. -.TP -.BI "\-\-filesystem " FILESYSTEM -Specifies the filesystem for the compressed image. At the moment, ext2, plain and squashfs are supported. Instead of this flag, the environment variable LIVE_FILESYSTEM can be used (Default: squashfs for iso, plain for net). -.TP -.BI "\-f, \-\-flavour " BOOTSTRAP_FLAVOUR -specifies the bootstrap flavour. This can be either standard or minimal. Instead of this flag, the environment variable LIVE_FLAVOUR can be used (Default: standard). -.TP -.BI "\-\-hook " COMMAND \||\| \|"COMMANDS\|" \||\|| FILE -specifies one or more commands to be executed in the chroot. Instead of this flag, the environment variable LIVE_HOOK can be used (Default: empty). -.TP -.BI "\-\-include-chroot " FILE \||\| DIRECTORY -specifies a file or a directory to be included into the chroot. Instead of this flag, the environment variable LIVE_INCLUDE_CHROOT can be used (Default: empty). -.TP -.BI "\-\-include-image " FILE \||\| DIRECTORY -specifies a file or directory which will be copied inside the image. Instead of this flag, the environment variable LIVE_INCLUDE_IMAGE can be used (Default: empty). -.TP -.BI "\-k, \-\-kernel " KERNEL_FLAVOUR -specifies the kernel image flavour. Instead of this flag, the environment variable LIVE_KERNEL can be used (Default: auto-detected). -.TP -.BI "\-\-manifest " PACKAGE -specifies the last package to install before creating the filesystem.manifest-desktop list, mainly used with ubuntu live, PACKAGE should probably be "ubuntu-live" for ubuntu desktop livecd's. Instead of this flag, the environment variable LIVE_MANIFEST can be used (Default: do not create filesystem.manifest-desktop). -.TP -.BI "\-m, \-\-mirror " URL -specifies the debian mirror where make-live will download the packages from. Instead of this flag, the environment variable LIVE_MIRROR can be used (Default: http://ftp.debian.org/debian). -.TP -.BI "\-\-mirror-security" URL -specifies the debian security mirror where make-live will download the packages from. Instead of this flag, the environment variable LIVE_MIRROR_SECURITY can be used (Default: http://security.debian.org/debian). -.TP -.BI "\-\-packages " PACKAGE \||\| \|"PACKAGES\|" -specifies a list of packages to install into the chroot. Instead of this flag, the environment variable LIVE_PACKAGES can be used (Default: empty). -.TP -.BI "\-p, \-\-package-list " FILE -specifies an external package list file, one package for each line. It overrides list option. Instead of this flag, the environment variable LIVE_PACKAGE_LIST can be used (Default: standard). -.TP -.BI "\-\-preseed " FILE -clone the packages selection and configuration from the provided -root directory. -.TP -.BI "\-\-proxy-ftp " URL -specifies the value of ftp_proxy inside the chrooted environment. Instead of this flag, the environment variable LIVE_PROXY_FTP can be used (Default: empty). -.TP -.BI "\-\-proxy-http " URL -specifies the value of http_proxy inside the chrooted environment. Instead of this flag, the environment variable LIVE_PROXY_HTTP can be used (Default: empty). -.TP -.BI "\-r, \-\-root " DIRECTORY -specifies the root directory where the images/tarballs are built. Instead of this flag, the environment variable LIVE_ROOT can be used (Default: `pwd`/debian-live). -.TP -.BI "\-s, \-\-sections " SECTIONS -specifies the debian sections. Instead of this flag, the environment variable LIVE_SECTIONS can be used (Default: main). -.TP -.BI "\-\-server-address " HOSTNAME \||\| IP -specifies the server address you want to use for netboot. Instead of this flag, the environment variable LIVE_SERVER_ADDRESS can be used (Default: 192.168.1.1). -.TP -.BI "\-\-server-path" DIRECTORY -specifies the directory on the server, where you have unpacked the netboot image. Instead of this flag, the environment variable LIVE_SERVER_PATH can be used (Default: /srv/debian-live). -.TP -.BI "\-\-templates " DIRECTORY -specifies a templates directory to use instead of the default one. Instead of this flag, the environment variable LIVE_TEMPLATES can be used (Default: /usr/share/make-live/templates). -.TP -.BI "\-t, \-\-type " TYPE -specifies the image type to generate. TYPE can be one of: iso, net, or usb. Instead of this flag, the environment variable LIVE_TYPE can be used (Default: iso). -.TP -.B \-\-with-generic-indices -enables use of generic Debian package indices. Instead of this flag, the environment variable LIVE_GENERIC_INDICES can be used (Default: yes). -.TP -.B \-\-without-generic-indices -disables use of generic Debian package indices. Instead of this flag, the environment variable LIVE_GENERIC_INDICES can be used (Default: yes). -.TP -.B \-\-with-source -enables generation of source images. Instead of this flag, the environment variable LIVE_SOURCE can be used (Default: no). -.TP -.B \-\-without-source -disables generation of source images. Instead of this flag, the environment variable LIVE_SOURCE can be used (Default: no). -.PP -.TP -.B \-h, \-\-help -display 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 - -.SH SEE ALSO -.BR make-live.conf(5) - -.SH AUTHOR -make-live was written by Daniel Baumann and Marco Amadori -. diff --git a/doc/man/make-live.conf.5 b/doc/man/make-live.conf.5 deleted file mode 100644 index f44351d..0000000 --- a/doc/man/make-live.conf.5 +++ /dev/null @@ -1,94 +0,0 @@ -.TH MAKE-LIVE.CONF 5 "Mon, 4 Sep 2006" "0.99" "Debian Live framework" - -.SH NAME -make-live.conf \- configuration file for make-live(1) - -.SH DESCRIPTION -make-live is a utility to build Debian Live systems. It takes a Debian mirror as an input and outputs a live system image (ISO image for CDs and DVDs, or tarball for netboot). make-live is still in the early stage of development, but has basic functionality and can be run successfully. - -.SH ENVIRONMENT -.TP -.B LIVE_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 environment variable, the flag \-a, \-\-architecture can be used (Default: `dpkg-architecture -qDEB_BUILD_ARCH`). -.TP -.B LIVE_BOOTAPPEND -specifies additional bootparameters to the kernel (Default: none). -.TP -.B LIVE_CONFIG -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 variable, the flag \-c or \-\-config can be used (Default: empty). -.TP -.B LIVE_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 environment variable, the flag \-d, \-\-distribution can be used (Default: unstable). -.TP -.B LIVE_FLAVOUR -specifies the bootstrap flavour. This can be either standard (default) or minimal. Instead of this environment variable, the flag \-f, \-\-flavour can be used. -.TP -.B LIVE_FILESYSTEM -specifies the filesystem to be used for the root filesystem image -(Default: squashfs). -.TP -.B LIVE_GENERIC_INDICES -specifies if generic Debian indices should be used (Default: enable). -.TP -.B LIVE_FTPPROXY -specifies the value of ftp_proxy inside the chrooted environment. Instead of this environment variable, the flag \-\-ftp-proxy can be used (Default: empty). -.TP -.B LIVE_HOOK -specifies one or more commands to be executed in the chroot. Instead of this environment variable, the flag \-\-hook can be used (Default: empty). -.TP -.B LIVE_INCLUDE_ROOT -specifies a file or a directory to be included into the chroot. Instead of this environment variable. the flag \-\-include-root can be used (Default: empty). -.TP -.B LIVE_KERNEL -specifies the kernel image flavour. Instead of this environment variable, the flag \-k, \-\-kernel can be used. -.TP -.BI LIVE_MANIFEST -specifies the last package to install before creating the filesystem.manifest-desktop list, mainly used with ubuntu live, in those system it should probably be set to "ubuntu-live" for ubuntu desktop livecd's (Default: do not create filesystem.manifest-desktop). -.TP -.B LIVE_MIRROR -specifies the debian mirror where make-live will download the packages from. Instead of this environment variable, the flag \-m, \-\-mirror LIVE_MIRROR can be used (Default: http://ftp.debian.org/debian). -.B LIVE_MIRROR_KEY -specifies the archive signing key. Instead of this environment variable, the flav \-\-mirror-key can be used (Default: http://ftp-master.debian.org/ziyi_key_2006.asc). -.TP -.B LIVE_PACKAGES -specifies a list of packages to install into the chroot. Instead of this environment variable, the flag \-\-packakges can be used (Default: empty). -.TP -.B LIVE_PACKAGE_LIST -specifies a file which contains a list of packages to install. -.TP -.B LIVE_PROXY_FTP -specifies the value of ftp_proxy inside the chrooted environment. Instead of this environment variable, the flag \-\-ftp-proxy can be used (Default: empty). -.TP -.B LIVE_PROXY_HTTP -specifies the value of http_proxy inside the chrooted environment. Instead of this environment variable, the flag \-\-http-proxy can be used (Default: empty). -.TP -.B LIVE_ROOT -specifies the root directory where the images/tarballs are built. Instead of this environment variable, the flag \-r or \-\-root can bse used (Default: `pwd`/debian-live). -.B LIVE_SECTIONS -specifies the debian sections. Instead of this environment variable, the flag \-s, \-\-sections can be used (Default: main). -.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_TEMPLATES -specifies a directory to be used for templates instead of the default one. -(Default: "/usr/share/make-live/templates") -.TP -.B LIVE_TYPE -specifies the image type. - -.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 - -.SH SEE ALSO -.BR make-live(1) - -.SH AUTHOR -make-live was written by Daniel Baumann and Marco Amadori -. diff --git a/functions/chroot.sh b/functions/chroot.sh new file mode 100755 index 0000000..60de2dd --- /dev/null +++ b/functions/chroot.sh @@ -0,0 +1,13 @@ +#!/bin/sh + +# chroot.sh - chroot wrapper + +set -e + +Chroot () +{ + COMMANDS="${1}" + + # Executing commands in chroot + chroot "${LIVE_CHROOT}" /usr/bin/env -i HOME="/root" PATH="/usr/sbin:/usr/bin:/sbin:/bin" TERM="${TERM}" ftp_proxy="${LH_APT_FTPPROXY}" http_proxy="${LH_APT_HTTPPPROXY}" DEBIAN_FRONTEND="${LH_DEBCONF_FRONTEND}" DEBIAN_PRIORITY="${LH_DEBCONF_PRIORITY}" ${COMMANDS} +} diff --git a/functions/conffile.sh b/functions/conffile.sh new file mode 100755 index 0000000..5df00d3 --- /dev/null +++ b/functions/conffile.sh @@ -0,0 +1,16 @@ +#!/bin/sh + +# conffile.sh - handle configuration files + +set -e + +Read_conffile () +{ + CONFFILE="${1}" + + # Reading configuration file + if [ -r "${CONFFILE}" ] + then + . "${CONFFILE}" + fi +} diff --git a/functions/defaults.sh b/functions/defaults.sh new file mode 100755 index 0000000..462c1eb --- /dev/null +++ b/functions/defaults.sh @@ -0,0 +1,384 @@ +#!/bin/sh + +# defaults.sh - handle default values + +set -e + +Set_defaults () +{ + ## config/common + + # Setting package manager + if [ -z "${LH_APT}" ] + then + LH_APT="aptitude" + fi + + # Setting apt ftp proxy + if [ -z "${LH_APT_FTPPROXY}" ] && [ -n "${ftp_proxy}" ] + then + LH_APT_FTPPROXY="${ftp_proxy}" + else + if [ -n "${LH_APT_FTPPROXY}" ] && [ "${LH_APT_FTPRPOXY}" != "${ftp_proxy}" ] + then + ftp_proxy="${LH_APT_FTPRPOXY}" + fi + fi + + # Setting apt http proxy + if [ -z "${LH_APT_HTTPPROXY}" ] && [ -n "${http_proxy}" ] + then + LH_APT_HTTPPROXY="${http_proxy}" + else + if [ -n "${LH_APT_HTTPPROXY}" ] && [ "${LH_APT_HTTPRPOXY}" != "${http_proxy}" ] + then + http_proxy="${LH_APT_HTTPPROXY}" + fi + fi + + # Setting apt indices + if [ -z "${LH_APT_GENERIC}" ] + then + LH_APT_GENERIC="enabled" + fi + + # Setting apt pdiffs + if [ -z "${LH_APT_PDIFFS}" ] + then + LH_APT_PDIFFS="enabled" + fi + + # Setting apt recommends + if [ -z "${LH_APT_RECOMMENDS}" ] + then + LH_APT_RECOMMENDS="enabled" + fi + + # Setting bootstrap program + if [ -z "${LH_BOOTSTRAP}" ] + then + if [ -x "/usr/bin/cdebootstrap" ] + then + LH_BOOTSTRAP="cdebootstrap" + elif [ -x "/usr/sbin/debootstrap" ] + then + LH_BOOTSTRAP="debootstrap" + else + echo "E: Can't process file /usr/bin/cdebootstrap or /usr/sbin/debootstrap (FIXME)" + exit 1 + fi + fi + + # Setting cache option + if [ -z "${LH_CACHE}" ] + then + LH_CACHE="enabled" + fi + + # Setting debconf frontend + if [ -z "${LH_DEBCONF_FRONTEND}" ] + then + LH_DEBCONF_FRONTEND="noninteractive" + fi + + if [ -z "${LH_DEBCONF_PRIORITY}" ] + then + LH_DEBCONF_PRIORITY="critical" + fi + + # Setting genisoimage + if [ -x /usr/bin/genisoimage ] + then + LH_GENISOIMAGE="genisoimage" + elif [ -x /usr/bin/mkisofs ] + then + LH_GENISOIMAGE="mkisofs" + else + echo "E: cannot find genisoimage nor mkisofs (FIXME)." + exit 1 + fi + + # Setting root directory + if [ -z "${LIVE_ROOT}" ] + then + LIVE_ROOT="`pwd`/debian-live" + fi + + # Setting chroot directory + if [ -z "${LIVE_CHROOT}" ] + then + LIVE_CHROOT="${LIVE_ROOT}/chroot" + fi + + ## config/bootstrap + + # Setting architecture string + if [ -z "${LIVE_ARCHITECTURE}" ] + then + if [ -x "/usr/bin/dpkg" ] + then + LIVE_ARCHITECTURE="`dpkg --print-architecture`" + else + echo "E: Can't process file /usr/bin/dpkg (FIXME)" + fi + fi + + # Setting distribution string + if [ -z "${LIVE_DISTRIBUTION}" ] + then + LIVE_DISTRIBUTION="sid" + fi + + # Setting distribution configuration string + # LIVE_DISTRIBUTION_CONFIG + + # Setting flavour string + if [ -z "${LIVE_FLAVOUR}" ] + then + LIVE_FLAVOUR="standard" + fi + + # Setting mirror string + if [ -z "${LIVE_MIRROR}" ] + then + LIVE_MIRROR="http://ftp.debian.org/debian/" + fi + + # Setting security mirror string + if [ -z "${LIVE_MIRROR_SECURITY}" ] + then + LIVE_MIRROR_SECURITY="http://security.debian.org/" + fi + + # Setting mirror string + if [ -z "${LIVE_MIRROR_GENERIC}" ] + then + LIVE_MIRROR_GENERIC="http://ftp.debian.org/debian/" + fi + + # Setting security mirror string + if [ -z "${LIVE_MIRROR_GENERIC_SECURITY}" ] + then + LIVE_MIRROR_GENERIC_SECURITY="http://security.debian.org/" + fi + + # Setting sections string + if [ -z "${LIVE_SECTIONS}" ] + then + LIVE_SECTIONS="main" + fi + + ## config/chroot + + # Setting kernel flavour string + if [ -z "${LIVE_KERNEL}" ] + then + case "${LIVE_ARCHITECTURE}" in + alpha) + LIVE_KERNEL="alpha-generic" + ;; + + amd64) + LIVE_KERNEL="amd64" + ;; + + arm) + echo "E: You need to specify the linux kernel flavour manually on arm (FIXME)." + exit 1 + ;; + + hppa) + LIVE_KERNEL="parisc" + ;; + + i386) + LIVE_KERNEL="486" + ;; + + ia64) + LIVE_KERNEL="itanium" + ;; + + m68k) + LIVE_KERNEL="E: You need to specify the linux kernel flavour manually on m68k." + exit 1 + ;; + + powerpc) + LIVE_KERNEL="powerpc" + ;; + + s390) + LIVE_KERNEL="s390" + ;; + + sparc) + LIVE_KERNEL="sparc32" + ;; + + *) + echo "E: Architecture notyet supported (FIXME)" + ;; + esac + fi + + # Set kernel packages + if [ -z "${LIVE_KERNEL_PACKAGES}" ] + then + LIVE_KERNEL_PACKAGES="linux-image-2.6-${LIVE_KERNEL} squashfs-modules-2.6-${LIVE_KERNEL} unionfs-modules-2.6-${LIVE_KERNEL} casper" + + if [ -n "${LIVE_ENCRYPTION}" ] + then + LIVE_KERNEL_PACKAGES="${LIVE_KERNEL_PACKAGES} loop-aes-modules-2.6-${LIVE_KERNEL} loop-aes-utils" + fi + fi + + # Setting language string + # LIVE_LANGUAGE + + # Setting tasks + # LIVE_TASKS + + # Setting packages string + # LIVE_PACKAGES + + # Setting packages list string + if [ -z "${LIVE_PACKAGES_LIST}" ] + then + if [ "${LIVE_FLAVOUR}" = "mini" ] || [ "${LIVE_FLAVOUR}" = "minimal" ] + then + LIVE_PACKAGES_LIST="minimal" + else + LIVE_PACKAGES_LIST="standard" + fi + fi + + # Setting tasks string + for LIST in ${LIVE_PACKAGES_LIST} + do + case "${LIST}" in + gnome-desktop) + LIVE_PACKAGES_LIST="`echo ${LIVE_PACKAGES_LIST} | sed -e 's/gnome-desktop//'` standard-x11" + LIVE_TASKS="${LIVE_TASKS} standard laptop desktop gnome-desktop" + ;; + + kde-desktop) + LIVE_PACKAGES_LIST="`echo ${LIVE_PACKAGES_LIST} | sed -e 's/kde-desktop//'` standard-x11" + LIVE_TASKS="${LIVE_TASKS} standard laptop desktop kde-desktop" + ;; + + xfce-desktop) + LIVE_PACKAGES_LIST="`echo ${LIVE_PACKAGES_LIST} | sed -e 's/xfce-desktop//'` standard-x11" + LIVE_TASKS="${LIVE_TASKS} standard laptop desktop xfce-desktop" + ;; + esac + done + + # Setting security updates option + if [ -z "${LIVE_SECURITY}" ] + then + LIVE_SECURITY="enabled" + fi + + # Setting symlink convertion option + if [ -z "${LIVE_SYMLINKS}" ] + then + LIVE_SYMLINKS="disabled" + fi + + # Setting sysvinit option + if [ -z "${LIVE_SYSVINIT}" ] && [ "${LIVE_FLAVOUR}" != "mini" ] + then + LIVE_SYSVINIT="enabled" + else + LIVE_SYSVINIT="disabled" + fi + + ## config/image + + # Setting boot parameters + # LIVE_BOOTAPPEND + + # Setting encryption + # LIVE_ENCRYPTION + + # Setting image type + if [ -z "${LIVE_BINARY_IMAGE}" ] + then + LIVE_BINARY_IMAGE="iso" + fi + + # Setting image type + if [ -z "${LIVE_SOURCE_IMAGE}" ] + then + if [ "${LIVE_BINARY_IMAGE}" = "iso" ] + then + LIVE_SOURCE_IMAGE="iso" + elif [ "${LIVE_BINARY_IMAGE}" = "usb" ] + then + LIVE_SOURCE_IMAGE="usb" + elif [ "${LIVE_BINARY_IMAGE}" = "net" ] + then + LIVE_SOURCE_IMAGE="net" + fi + fi + + # Setting filesystem + if [ -z "${LIVE_FILESYSTEM}" ] && [ "${LIVE_BINARY_IMAGE}" = "iso" ] + then + LIVE_FILESYSTEM="squashfs" + elif [ -z "${LIVE_FILESYSTEM}" ] && [ "${LIVE_BINARY_IMAGE}" = "usb" ] + then + LIVE_FILESYSTEM="squashfs" + elif [ -z "${LIVE_FILESYSTEM}" ] && [ "${LIVE_BINARY_IMAGE}" = "net" ] + then + LIVE_FILESYSTEM="plain" + else + LIVE_FILESYSTEM="squashfs" + fi + + # Setting memtest86 option + if [ -z "${LIVE_MEMTEST86}" ] + then + LIVE_MEMTEST86="enabled" + fi + + # Setting iso volume + if [ -z "${LIVE_ISO_VOLUME}" ] + then + LIVE_ISO_VOLUME='Debian Live ${DATE}' + fi + + # Setting netboot server address + if [ -z "${LIVE_SERVER_ADDRESS}" ] + then + LIVE_SERVER_ADDRESS="192.168.1.1" + fi + + # Setting netboot server path + if [ -z "${LIVE_SERVER_PATH}" ] + then + LIVE_SERVER_PATH="/srv/debian-live" + fi + + # Setting source option + if [ -z "${LIVE_SOURCE}" ] + then + LIVE_SOURCE="disabled" + fi + + # Setting syslinux + if [ -z "${LIVE_SYSLINUX}" ] + then + LIVE_SYSLINUX="enabled" + fi + + # Setting syslinux splash + # LIVE_SYSLINUX_SPLASH + + # Setting templates + if [ -z "${LIVE_TEMPLATES}" ] + then + LIVE_TEMPLATES="/usr/share/live-helper/templates" + fi +} diff --git a/functions/lockfile.sh b/functions/lockfile.sh new file mode 100755 index 0000000..9eb2f9b --- /dev/null +++ b/functions/lockfile.sh @@ -0,0 +1,35 @@ +#!/bin/sh + +# lockfile.sh - handle lock files + +set -e + +Check_lockfile () +{ + LOCKFILE="${1}" + + # Checking lock file + if [ -f "${LOCKFILE}" ] + then + echo "E: system locked" + exit 1 + fi +} + +Create_lockfile () +{ + LOCKFILE="${1}" + LOCKDIRECTORY="`dirname ${1}`" + + # Creating lock directory + if [ ! -d "${LOCKDIRECTORY}" ] + then + mkdir -p "${LOCKDIRECTORY}" + fi + + # Creating lock file + trap "test -f ${LOCKFILE} && \ + rm -f ${LOCKFILE}; exit 0" 0 2 15 + + touch "${LOCKFILE}" +} diff --git a/functions/stagefile.sh b/functions/stagefile.sh new file mode 100755 index 0000000..23c3a34 --- /dev/null +++ b/functions/stagefile.sh @@ -0,0 +1,46 @@ +#!/bin/sh + +# stagefile.sh - handle stage files + +set -e + +Check_stagefile () +{ + STAGEFILE="${1}" + STAGENAME="`basename ${1}`" + + # Checking stage file + if [ -f "${STAGEFILE}" ] + then + echo "W: skipping ${STAGENAME}" + exit 0 + fi +} + +Create_stagefile () +{ + STAGEFILE="${1}" + STAGEDIRECTORY="`dirname ${1}`" + + # Creating stage directory + if [ ! -d "${STAGEDIRECTORY}" ] + then + mkdir -p "${STAGEDIRECTORY}" + fi + + # Creating stage file + touch "${STAGEFILE}" +} + +Require_stagefile () +{ + STAGEFILE="${1}" + STAGENAME="`basename ${1}`" + + # Checking stage file + if [ ! -f "${STAGEFILE}" ] + then + echo "E: ${STAGENAME} missing" + exit 1 + fi +} diff --git a/functions/version.sh b/functions/version.sh new file mode 100755 index 0000000..2d5ff20 --- /dev/null +++ b/functions/version.sh @@ -0,0 +1,6 @@ +#!/bin/sh + +# version.sh - handle version information + +DATE="`date +%Y%m%d`" +VERSION="1.0~a1" diff --git a/helpers/Makefile b/helpers/Makefile deleted file mode 100644 index f2f31d4..0000000 --- a/helpers/Makefile +++ /dev/null @@ -1,11 +0,0 @@ -# Makefile - -all: install - -install: - install -d -m 0755 $(DESTDIR)/usr/sbin/ - install -m 0755 lh_* $(DESTDIR)/usr/sbin - -uninstall: - -reinstall: install diff --git a/helpers/lh_binary b/helpers/lh_binary new file mode 100755 index 0000000..36dc722 --- /dev/null +++ b/helpers/lh_binary @@ -0,0 +1,46 @@ +#!/bin/sh + +# lh_image(1) - building the images + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +# Building root filesystem +lh_binary_rootfs +lh_binary_manifest +lh_binary_encryption + +# Configuring chroot +lh_chroot_proc install +lh_chroot_sysfs install +lh_chroot_hosts install +lh_chroot_resolv install +lh_chroot_sources install + +# Prepare images +lh_binary_linuximage +lh_binary_memtest86 +lh_binary_syslinux +lh_binary_includes +lh_binary_localincludes +lh_binary_md5sum + +# Building images +lh_binary_iso +lh_binary_net +lh_binary_usb + +# Deconfiguring chroot +rm -f .stage/chroot_sources +lh_chroot_resolv remove +lh_chroot_hosts remove +lh_chroot_sysfs remove +lh_chroot_proc remove diff --git a/helpers/lh_binary_encryption b/helpers/lh_binary_encryption new file mode 100755 index 0000000..9df73b2 --- /dev/null +++ b/helpers/lh_binary_encryption @@ -0,0 +1,73 @@ +#!/bin/sh + +# lh_binary_encryption(1) - encrypts rootfs + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap +Require_stagefile "${LIVE_ROOT}"/.stage/binary_rootfs + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_encryption + +if [ -n "${LIVE_ENCRYPTION}" ] +then + if [ ! -x /usr/bin/aespipe ] + then + echo "E: aespipe is missing (FIXME)." + exit 1 + fi + + case "${LIVE_FILESYSTEM}" in + ext2) + ROOTFS="ext2" + ;; + + plain) + echo "W: encryption not supported on plain filesystem." + exit 0 + ;; + + squashfs) + ROOTFS="squashfs" + ;; + esac + + echo "Encrypting ${LIVE_ROOT}/binary/casper/filesystem.${ROOTFS} with ${LIVE_ENCRYPTION}..." + + while true + do + cat ${LIVE_ROOT}/binary/casper/filesystem.${ROOTFS} | aespipe -e "${LIVE_ENCRYPTION}" -T > "${LIVE_ROOT}"/binary/casper/filesystem.${ROOTFS} && break + + echo -n "Something went wrong... Retry? [YES/no] " + + read ANSWER + + if [ 'no' = "${ANSWER}" ] + then + unset ANSWER + break + fi + done + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/binary_encryption +fi diff --git a/helpers/lh_binary_includes b/helpers/lh_binary_includes new file mode 100755 index 0000000..b170514 --- /dev/null +++ b/helpers/lh_binary_includes @@ -0,0 +1,42 @@ +#!/bin/sh + +# lh_binary_includes(1) - copy files into binary + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_includes + +if ls /usr/share/live-helper/includes/common/* &> /dev/null +then + cp -r /usr/share/live-helper/includes/common/* "${LIVE_ROOT}"/binary +fi + +if ls /usr/share/live-helper/includes/"${LIVE_BINARY_IMAGE}"/* &> /dev/null +then + cp -r /usr/share/live-helper/includes/"${LIVE_BINARY_IMAGE}"/* "${LIVE_ROOT}"/binary +fi + +# Creating stage file +Create_stagefile "${LIVE_ROOT}"/.stage/binary_includes diff --git a/helpers/lh_binary_iso b/helpers/lh_binary_iso new file mode 100755 index 0000000..d39313f --- /dev/null +++ b/helpers/lh_binary_iso @@ -0,0 +1,54 @@ +#!/bin/sh + +# lh_binary_iso(1) - build iso binary image + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/bootstrap +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_iso + +for IMAGE in ${LIVE_BINARY_IMAGE} +do + if [ "${IMAGE}" = "iso" ] + then + # Remove old binary + if [ -f "${LIVE_ROOT}"/binary.iso ] + then + rm -f "${LIVE_ROOT}"/binary.iso + fi + + # Create image + if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ] + then + ${LH_GENISOIMAGE} -A "Debian Live" -p "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -publisher "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -o "${LIVE_ROOT}"/"${LIVE_IMAGE}"binary.iso -r -J -l -V "${LIVE_ISO_VOLUME}" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table "${LIVE_ROOT}"/binary ${LIVE_INCLUDE_IMAGE} + else + echo "W: Bootloader on your architecture not yet supported (Continuing in 5 seconds)." + sleep 5 + ${LH_GENISOIMAGE} -A "Debian Live" -p "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -publisher "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -o "${LIVE_ROOT}"/"${LIVE_IMAGE}"binary.iso -r -J -l -V "${LIVE_ISO_VOLUME}" "${LIVE_ROOT}"/binary ${LIVE_INCLUDE_IMAGE} + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/binary_iso + fi +done diff --git a/helpers/lh_binary_linuximage b/helpers/lh_binary_linuximage new file mode 100755 index 0000000..d332c53 --- /dev/null +++ b/helpers/lh_binary_linuximage @@ -0,0 +1,59 @@ +#!/bin/sh + +# lh_binary_linuximage(1) - install linux-image into binary + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_linuximage + +# Removing initrd backup files +rm -f "${LIVE_CHROOT}"/boot/initrd*bak* + +# Setting destination directory +case "${LIVE_BINARY_IMAGE}" in + iso) + DESTDIR="${LIVE_ROOT}/binary/isolinux" + ;; + + net) + DESTDIR="${LIVE_ROOT}/tftpboot" + ;; + + usb) + DESTDIR="${LIVE_ROOT}/binary" + ;; +esac + +# Creating directory +if [ ! -d "${DESTDIR}" ] +then + mkdir -p "${DESTDIR}" +fi + +# Installing linux-image +cp "${LIVE_CHROOT}"/boot/vmlinuz* "${DESTDIR}"/vmlinuz +cp "${LIVE_CHROOT}"/boot/initrd.img* "${DESTDIR}"/initrd.gz + +# Creating stage file +Create_stagefile "${LIVE_ROOT}"/.stage/binary_linuximage diff --git a/helpers/lh_binary_localincludes b/helpers/lh_binary_localincludes new file mode 100755 index 0000000..2aa6547 --- /dev/null +++ b/helpers/lh_binary_localincludes @@ -0,0 +1,39 @@ +#!/bin/sh + +# lh_binary_localincludes(1) - copy files into binary + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_localincludes + +if ls "${LIVE_ROOT}"/config/binary_localincludes/* &> /dev/null +then + cd "${LIVE_ROOT}"/config/binary_localincludes + + # Copying includes + find . | cpio -dmpu "${LIVE_ROOT}"/binary + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/binary_localincludes +fi diff --git a/helpers/lh_binary_manifest b/helpers/lh_binary_manifest new file mode 100755 index 0000000..d109280 --- /dev/null +++ b/helpers/lh_binary_manifest @@ -0,0 +1,34 @@ +#!/bin/sh + +# lh_binary_manifest(1) - create manifest + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_manifest + +# Add filesystem.manifest +Chroot "dpkg --get-selections" | awk '{ print $1 }' | sort -u > "${LIVE_ROOT}"/binary/casper/filesystem.manifest + +# Creating stage file +Create_stagefile "${LIVE_ROOT}"/.stage/binary_manifest diff --git a/helpers/lh_binary_md5sum b/helpers/lh_binary_md5sum new file mode 100755 index 0000000..9ab3f35 --- /dev/null +++ b/helpers/lh_binary_md5sum @@ -0,0 +1,51 @@ +#!/bin/sh + +# lh_binary_md5sum(1) - create md5sum.txt + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_md5sum + +# Remove old md5sums +if [ -f "${LIVE_ROOT}"/binary/md5sum.txt ] +then + rm -f "${LIVE_ROOT}"/binary/md5sum.txt +fi + +# Calculating md5sums +cd "${LIVE_ROOT}"/binary +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}"/binary + +# Creating stage file +Create_stagefile "${LIVE_ROOT}"/.stage/binary_md5sum diff --git a/helpers/lh_binary_memtest86 b/helpers/lh_binary_memtest86 new file mode 100755 index 0000000..95952af --- /dev/null +++ b/helpers/lh_binary_memtest86 @@ -0,0 +1,97 @@ +#!/bin/sh + +# lh_binary_memtest86(1) - installs memtest86+ + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/bootstrap +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_memtest86 + +if [ "${LIVE_ARCHITECTURE}" != "amd64" ] && [ "${LIVE_ARCHITECTURE}" != "i386" ] +then + echo "W: skipping binary_memtest86, foreign architecture." + exit 0 +fi + +if [ "${LIVE_MEMTEST86}" = "enabled" ] +then + if [ ! -f "${LIVE_CHROOT}"/boot/memtest86+.bin ] + then + PACKAGES="${PACKAGES} memtest86+" + fi + + if [ -n "${PACKAGES}" ] + then + # Installing symlinks + case "${LH_APT}" in + apt) + Chroot "apt-get install --yes ${PACKAGES}" + ;; + + aptitude) + Chroot "aptitude install --assume-yes ${PACKAGES}" + ;; + esac + fi + + case "${LIVE_BINARY_IMAGE}" in + iso) + DESTDIR="${LIVE_ROOT}/binary/isolinux" + ;; + + net) + DESTDIR="${LIVE_ROOT}/tftpboot" + ;; + + usb) + DESTDIR="${LIVE_ROOT}/binary" + ;; + esac + + # Creating directory + if [ ! -d "${DESTDIR}" ] + then + mkdir -p "${DESTDIR}" + fi + + # Installing memtest86+ + cp "${LIVE_ROOT}"/chroot/boot/memtest86+.bin "${DESTDIR}"/memtest + + if [ -n "${PACKAGES}" ] + then + # Removing syslinux + case "${LH_APT}" in + apt) + Chroot "apt-get remove --purge --yes ${PACKAGES}" + ;; + + aptitude) + Chroot "aptitude purge --assume-yes ${PACKAGES}" + ;; + esac + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/binary_memtest86 +fi diff --git a/helpers/lh_binary_net b/helpers/lh_binary_net new file mode 100755 index 0000000..6281448 --- /dev/null +++ b/helpers/lh_binary_net @@ -0,0 +1,53 @@ +#!/bin/sh + +# lh_binary_net(1) - build netboot binary image + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/bootstrap +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_net + +for IMAGE in ${LIVE_BINARY_IMAGE} +do + if [ "${IMAGE}" = "net" ] + then + # Remove old binary + if [ -f "${LIVE_ROOT}"/binary.tar.gz ] + then + rm -f "${LIVE_ROOT}"/binary.tar.gz + fi + + # Creating image file + cd "${LIVE_ROOT}" && \ + mv binary "`basename ${LIVE_SERVER_PATH}`" && \ + cd .. && \ + tar cfz binary.tar.gz "`basename ${LIVE_ROOT}`/`basename ${LIVE_SERVER_PATH}`" "`basename ${LIVE_ROOT}`/tftpboot" && \ + mv binary.tar.gz "${LIVE_ROOT}" && \ + cd "${OLDPWD}" && \ + mv "`basename ${LIVE_SERVER_PATH}`" binary + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/binary_net + fi +done diff --git a/helpers/lh_binary_rootfs b/helpers/lh_binary_rootfs new file mode 100755 index 0000000..bbb2153 --- /dev/null +++ b/helpers/lh_binary_rootfs @@ -0,0 +1,76 @@ +#!/bin/sh + +# lh_binary_rootfs(1) - build rootfs image + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_rootfs + +# Creating directory +if [ ! -d "${LIVE_ROOT}"/binary/casper ] +then + mkdir -p "${LIVE_ROOT}"/binary/casper +fi + +case "${LIVE_FILESYSTEM}" in + ext2) + if [ -f "${LIVE_ROOT}"/binary/casper/filesystem.ext2 ] + then + rm -f "${LIVE_ROOT}"/binary/casper/filesystem.ext2 + fi + + 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}"/binary/casper/filesystem.ext2 + ;; + + plain) + if [ -d "${LIVE_ROOT}"/binary/casper/filesystem.dir ] + then + rm -rf "${LIVE_ROOT}"/binary/casper/filesystem.dir + fi + + cd "${LIVE_CHROOT}" + find . | cpio -pumd "${LIVE_ROOT}"/binary/casper/filesystem.dir + cd "${OLDPWD}" + ;; + + squashfs) + if [ -f "${LIVE_ROOT}"/binary/casper/filesystem.squashfs ] + then + rm "${LIVE_ROOT}"/binary/casper/filesystem.squashfs + fi + + if [ "${LIVE_FLAVOUR}" = "minimal" ] || [ "${LIVE_FLAVOUR}" = "mini" ] + then + mksquashfs "${LIVE_CHROOT}" "${LIVE_ROOT}"/binary/casper/filesystem.squashfs -e "${LIVE_CHROOT}"/boot/vmlinuz* "${LIVE_CHROOT}"/boot/initrd.img* "${LIVE_CHROOT}"/vmlinuz "${LIVE_CHROOT}"/initrd.img "${LIVE_CHROOT}"/boot/config-* "${LIVE_CHROOT}"/boot/System.map-* + else + mksquashfs "${LIVE_CHROOT}" "${LIVE_ROOT}"/binary/casper/filesystem.squashfs + fi + ;; +esac + +# Creating stage file +Create_stagefile "${LIVE_ROOT}"/.stage/binary_rootfs diff --git a/helpers/lh_binary_syslinux b/helpers/lh_binary_syslinux new file mode 100755 index 0000000..5384232 --- /dev/null +++ b/helpers/lh_binary_syslinux @@ -0,0 +1,152 @@ +#!/bin/sh + +# lh_binary_syslinux(1) - installs syslinux + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/bootstrap +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_syslinux + +if [ "${LIVE_ARCHITECTURE}" != "amd64" ] && [ "${LIVE_ARCHITECTURE}" != "i386" ] +then + echo "W: skipping binary_syslinux, foreign architecture." + exit 0 +fi + +if [ "${LIVE_SYSLINUX}" = "enabled" ] +then + if [ ! -f "${LIVE_CHROOT}"/usr/bin/syslinux ] + then + PACKAGES="${PACKAGES} syslinux" + fi + + if [ -n "${PACKAGES}" ] + then + # Installing symlinks + case "${LH_APT}" in + apt) + Chroot "apt-get install --yes ${PACKAGES}" + ;; + + aptitude) + Chroot "aptitude install --assume-yes ${PACKAGES}" + ;; + esac + fi + + if [ -n "${LIVE_ENCRYPTION}" ] + then + LIVE_BOOTAPPEND="${LIVE_BOOTAPPEND} encryption=${LIVE_ENCRYPTION}" + fi + + case "${LIVE_BINARY_IMAGE}" in + iso) + # Copying syslinux + mkdir -p "${LIVE_ROOT}"/binary/isolinux + cp "${LIVE_CHROOT}"/usr/lib/syslinux/isolinux.bin "${LIVE_ROOT}"/binary/isolinux + cp -r "${LIVE_TEMPLATES}"/syslinux/* "${LIVE_ROOT}"/binary/isolinux + + # Copying splash screen + if [ -n "${LIVE_SYSLINUX_SPLASH}" ] + then + cp "${LIVE_SYSLINUX_SPLASH}" "${LIVE_ROOT}/binary/isolinux/splash.rle" + fi + + # Configure syslinux templates + sed -i -e "s#LIVE_BOOTAPPEND#${LIVE_BOOTAPPEND}#" "${LIVE_ROOT}"/binary/isolinux/isolinux.cfg + sed -i -e "s/LIVE_DATE/${DATE}/" "${LIVE_ROOT}"/binary/isolinux/f1.txt + sed -i -e "s/LIVE_VERSION/${VERSION}/" "${LIVE_ROOT}"/binary/isolinux/f10.txt + + # Remove unused files + rm -f "${LIVE_ROOT}"/binary/isolinux/pxelinux.cfg + ;; + + net) + # Copying syslinux + mkdir -p "${LIVE_ROOT}"/tftpboot + cp "${LIVE_CHROOT}"/usr/lib/syslinux/pxelinux.0 "${LIVE_ROOT}"/tftpboot + + # Install syslinux templates + mkdir -p "${LIVE_ROOT}"/tftpboot/pxelinux.cfg + cp -r "${LIVE_TEMPLATES}"/syslinux/* "${LIVE_ROOT}"/tftpboot/pxelinux.cfg + mv "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/pxelinux.cfg "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/default + sed -i -e 's#splash.rle#pxelinux.cfg/splash.rle#' "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/isolinux.txt + + # Copying splash screen + if [ -n "${LIVE_SYSLINUX_SPLASH}" ] + then + cp "${LIVE_SYSLINUX_SPLASH}" "${LIVE_ROOT}/tftpboot/pxelinux.cfg/splash.rle" + fi + + # 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}/" "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/f1.txt + sed -i -e "s/LIVE_VERSION/${VERSION}/" "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/f10.txt + + # Remove unused files + rm -f "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/isolinux.cfg + ;; + + usb) + # Copying syslinux + mkdir -p "${LIVE_ROOT}"/binary + cp "${LIVE_CHROOT}"/usr/lib/syslinux/isolinux.bin "${LIVE_ROOT}"/binary/syslinux.bin + cp -r "${LIVE_TEMPLATES}"/syslinux/* "${LIVE_ROOT}"/binary + mv "${LIVE_ROOT}"/binary/isolinux.cfg "${LIVE_ROOT}"/binary/syslinux.cfg + mv "${LIVE_ROOT}"/binary/isolinux.txt "${LIVE_ROOT}"/binary/syslinux.txt + sed -i -e "s/isolinux.txt/syslinux.txt/" "${LIVE_ROOT}"/binary/syslinux.cfg + + # Copying splash screen + if [ -n "${LIVE_SYSLINUX_SPLASH}" ] + then + cp "${LIVE_SYSLINUX_SPLASH}" "${LIVE_ROOT}/binary/splash.rle" + fi + + # Configure syslinux templates + sed -i -e "s#LIVE_BOOTAPPEND#${LIVE_BOOTAPPEND}#" "${LIVE_ROOT}"/binary/syslinux.cfg + sed -i -e "s/LIVE_DATE/${DATE}/" "${LIVE_ROOT}"/binary/f1.txt + sed -i -e "s/LIVE_VERSION/${VERSION}/" "${LIVE_ROOT}"/binary/f10.txt + + # Remove unused files + rm -f "${LIVE_ROOT}"/binary/pxelinux.cfg + ;; + esac + + if [ -n "${PACKAGES}" ] + then + # Removing syslinux + case "${LH_APT}" in + apt) + Chroot "apt-get remove --purge --yes ${PACKAGES}" + ;; + + aptitude) + Chroot "aptitude purge --assume-yes ${PACKAGES}" + ;; + esac + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/binary_syslinux +fi diff --git a/helpers/lh_binary_usb b/helpers/lh_binary_usb new file mode 100755 index 0000000..ec0d13f --- /dev/null +++ b/helpers/lh_binary_usb @@ -0,0 +1,128 @@ +#!/bin/sh + +# lh_binary_usb(1) - build binary image + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/bootstrap +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/binary_usb + +for IMAGE in ${LIVE_BINARY_IMAGE} +do + if [ "${IMAGE}" = "usb" ] + then + if [ ! -f "${LIVE_CHROOT}"/sbin/mkdosfs ] + then + PACKAGES="${PACKAGES} dosfstools" + fi + + if [ ! -f "${LIVE_CHROOT}"/usr/bin/mtools ] + then + PACKAGES="${PACKAGES} mtools" + fi + + if [ ! -f "${LIVE_CHROOT}"/sbin/parted ] + then + PACKAGES="${PACKAGES} parted" + fi + + if [ ! -f "${LIVE_CHROOT}"/usr/bin/syslinux ] + then + PACKAGES="${PACKAGES} syslinux" + fi + + if [ -n "${PACKAGES}" ] + then + # Installing packages + case "${LH_APT}" in + apt) + Chroot "apt-get install --yes ${PACKAGES}" + ;; + + aptitude) + Chroot "aptitude install --assume-yes ${PACKAGES}" + ;; + esac + fi + + # Remove old binary + if [ -f "${LIVE_ROOT}"/binary.img ] + then + rm -f "${LIVE_ROOT}"/binary.img + fi + + # Everything which comes here needs to be cleaned up, + DU_DIM="`du -ms ${LIVE_ROOT}/binary | cut -f1`" + REAL_DIM="`expr ${DU_DIM} + ${DU_DIM} / 20`" # Just 5% more to be sure, need something more sophistcated here... + dd if=/dev/zero of="${LIVE_ROOT}"/binary.img bs=1024k count=${REAL_DIM} + FREELO="`losetup -f`" + if [ ! -b "${LIVE_CHROOT}"/${FREELO} ] + then + MAKEDEV="true" + Chroot "cd /dev && ./MAKEDEV ${FREELO}" + fi + + echo "!!! The following error/warning messages can be ignored !!!" + lh_losetup $FREELO "${LIVE_ROOT}"/binary.img 0 + Chroot "parted -s ${FREELO} mklabel msdos" || true + Chroot "parted -s ${FREELO} mkpartfs primary fat16 0.0 100%" || true + Chroot "parted -s ${FREELO} set 1 boot on" || true + Chroot "parted -s ${FREELO} set 1 lba off" || true + cat "${LIVE_CHROOT}"/usr/lib/syslinux/mbr.bin > ${FREELO} + losetup -d ${FREELO} + + lh_losetup $FREELO "${LIVE_ROOT}"/binary.img 1 + Chroot "mkfs.msdos -n DEBIAN_LIVE ${FREELO}" + mkdir -p "${LIVE_ROOT}"/binary.tmp + mount ${FREELO} "${LIVE_ROOT}"/binary.tmp + cp -r "${LIVE_ROOT}"/binary/* "${LIVE_ROOT}"/binary.tmp + umount "${LIVE_ROOT}"/binary.tmp + rmdir "${LIVE_ROOT}"/binary.tmp + Chroot "syslinux ${FREELO}" + losetup -d ${FREELO} + echo "!!! The above error/warning messages can be ignored !!!" + + if [ -n "${MAKEDEV}" ] + then + rm -f "${LIVE_CHROOT}"/${FREELO} + fi + + if [ -n "${PACKAGES}" ] + then + # Removing packages + case "${LH_APT}" in + apt) + Chroot "apt-get remove --purge --yes ${PACKAGES}" + ;; + + aptitude) + Chroot "aptitude purge --assume-yes ${PACKAGES}" + ;; + esac + fi + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/binary_usb +done diff --git a/helpers/lh_bootstrap b/helpers/lh_bootstrap new file mode 100755 index 0000000..9d1170d --- /dev/null +++ b/helpers/lh_bootstrap @@ -0,0 +1,19 @@ +#!/bin/sh + +# lh_bootstrap(1) - bootstrap a Debian system + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/bootstrap +Set_defaults + +# Bootstrapping system +lh_bootstrap_"${LH_BOOTSTRAP}" diff --git a/helpers/lh_bootstrap_cdebootstrap b/helpers/lh_bootstrap_cdebootstrap new file mode 100755 index 0000000..c5602a6 --- /dev/null +++ b/helpers/lh_bootstrap_cdebootstrap @@ -0,0 +1,103 @@ +#!/bin/sh + +# lh_bootstrap_cdebootstrap(1) - bootstrap a Debian system with cdebootstrap(1) + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Ensure that a system is built as root +lh_testroot + +# Reading configuration files +Read_conffile config/common +Read_conffile config/bootstrap +Set_defaults + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Creating root directory +if [ ! -d "${LIVE_ROOT}" ] +then + mkdir -p "${LIVE_ROOT}" +fi + +# Creating chroot directory +if [ ! -d "${LIVE_CHROOT}" ] +then + mkdir -p "${LIVE_CHROOT}" +fi + +# Setting cdebootstrap options +if [ -n "${LIVE_ARCHITECTURE}" ] +then + CDEBOOTSTRAP_OPTIONS="${CDEBOOTSTRAP_OPTIONS} --arch=${LIVE_ARCHITECTURE}" +fi + +if [ -n "${LIVE_DISTRIBUTION_CONFIG}" ] +then + CDEBOOTSTRAP_OPTIONS="${CDEBOOTSTRAP_OPTIONS} --suite-config=${LIVE_DISTRIBUTION_CONFIG}" +fi + +if [ "${LIVE_FLAVOUR}" = "mini" ] || [ "${LIVE_FLAVOUR}" = "minimal" ] || [ "${LIVE_FLAVOUR}" = "minimal-net" ] +then + CDEBOOTSTRAP_OPTIONS="${CDEBOOTSTRAP_OPTIONS} --flavour=minimal" +else + CDEBOOTSTRAP_OPTIONS="${CDEBOOTSTRAP_OPTIONS} --flavour=standard" +fi + +if [ -x "/usr/bin/cdebootstrap" ] +then + # Restore old cache + if [ -d "${LIVE_ROOT}"/cache/bootstrap ] + then + mkdir -p "${LIVE_CHROOT}"/var/cache/bootstrap + cp "${LIVE_ROOT}"/cache/bootstrap/*.deb "${LIVE_CHROOT}"/var/cache/bootstrap + fi + + if [ "${LH_CACHE}" = "enabled" ] + then + # Executing cdebootstrap (download-only) + cdebootstrap ${CDEBOOTSTRAP_OPTIONS} --download-only "${LIVE_DISTRIBUTION}" "${LIVE_CHROOT}" "${LIVE_MIRROR}" + + # Removing old cache + if [ -d "${LIVE_ROOT}"/cache/bootstrap ] + then + rm -f "${LIVE_ROOT}"/cache/bootstrap/*.deb + fi + + # Saving new cache + if [ ! -d "${LIVE_ROOT}"/cache/bootstrap ] + then + mkdir -p "${LIVE_ROOT}"/cache/bootstrap + fi + + cp "${LIVE_CHROOT}"/var/cache/bootstrap/*.deb "${LIVE_ROOT}"/cache/bootstrap + fi + + # Executing cdebootstrap (regular run) + cdebootstrap ${CDEBOOTSTRAP_OPTIONS} "${LIVE_DISTRIBUTION}" "${LIVE_CHROOT}" "${LIVE_MIRROR}" +else + echo "E: Can't process file /usr/bin/cdebootstrap (FIXME)" + exit 1 +fi + +# Removing bootstrap cache +if [ -d "${LIVE_CHROOT}/var/cache/bootstrap" ] +then + rm -rf "${LIVE_CHROOT}"/var/cache/bootstrap +fi + +# Creating stage file +Create_stagefile "${LIVE_ROOT}"/.stage/bootstrap diff --git a/helpers/lh_bootstrap_debootstrap b/helpers/lh_bootstrap_debootstrap new file mode 100755 index 0000000..42009cb --- /dev/null +++ b/helpers/lh_bootstrap_debootstrap @@ -0,0 +1,93 @@ +#!/bin/sh + +# lh_bootstrap_debootstrap(1) - bootstrap a Debian system with debootstrap(8) + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Ensure that a system is built as root +lh_testroot + +# Reading configuration files +Read_conffile config/common +Read_conffile config/bootstrap +Set_defaults + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Creating root directory +if [ ! -d "${LIVE_ROOT}" ] +then + mkdir -p "${LIVE_ROOT}" +fi + +# Creating chroot directory +if [ ! -d "${LIVE_CHROOT}" ] +then + mkdir -p "${LIVE_CHROOT}" +fi + +# Setting debootstrap options +if [ -n "${LIVE_ARCHITECTURE}" ] +then + DEBOOTSTRAP_OPTIONS="${DEBOOTSTRAP_OPTIONS} --arch ${LIVE_ARCHITECTURE}" +fi + +if [ -n "${LIVE_BOOTSTRAP_CONFIG}" ] +then + LIVE_DEBOOTSTRAP_SCRIPT="/usr/lib/debootstrap/scripts/${LIVE_BOOTSTRAP_CONFIG}" +fi + +if [ -x "/usr/sbin/debootstrap" ] +then + # Restore old cache + if [ -d "${LIVE_ROOT}"/cache/bootstrap ] + then + mkdir -p "${LIVE_CHROOT}"/var/cache/apt/archives + cp "${LIVE_ROOT}"/cache/bootstrap/*.deb "${LIVE_CHROOT}"/var/cache/apt/archives + fi + + if [ "${LH_CACHE}" = "enabled" ] + then + # Executing debootstrap (download-only) + debootstrap ${DEBOOTSTRAP_OPTIONS} --download-only "${LIVE_DISTRIBUTION}" "${LIVE_CHROOT}" "${LIVE_MIRROR}" "${LIVE_DEBOOTSTRAP_SCRIPT}" + + # Removing old cache + if [ -d "${LIVE_ROOT}"/cache/bootstrap ] + then + rm -f "${LIVE_ROOT}"/cache/bootstrap/*.deb + fi + + # Saving new cache + if [ ! -d "${LIVE_ROOT}"/cache/bootstrap ] + then + mkdir -p "${LIVE_ROOT}"/cache/bootstrap + fi + + cp "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb "${LIVE_ROOT}"/cache/bootstrap + fi + + # Executing debootstrap (regular run) + debootstrap ${DEBOOTSTRAP_OPTIONS} "${LIVE_DISTRIBUTION}" "${LIVE_CHROOT}" "${LIVE_MIRROR}" "${LIVE_DEBOOTSTRAP_SCRIPT}" +else + echo "E: Can't process file /usr/bin/debootstrap (FIXME)" + exit 1 +fi + +# Removing bootstrap cache +rm -rf "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb + +# Creating stage file +Create_stagefile "${LIVE_ROOT}"/.stage/bootstrap diff --git a/helpers/lh_build b/helpers/lh_build new file mode 100755 index 0000000..1d839a9 --- /dev/null +++ b/helpers/lh_build @@ -0,0 +1,17 @@ +#!/bin/sh + +# lh_build(1) - build a Debian system + +set -e + +# Bootstrapping system +lh_bootstrap + +# Customizing chroot +lh_chroot + +# Building binary image +lh_binary + +# Building source image +lh_source diff --git a/helpers/lh_buildbinary b/helpers/lh_buildbinary deleted file mode 100755 index 2a11c9b..0000000 --- a/helpers/lh_buildbinary +++ /dev/null @@ -1,200 +0,0 @@ -#!/bin/sh - -# lh_buildbinary - -if [ ! -f "${LIVE_ROOT}"/.stage/image_binary ] -then - # Configure chroot - lh_patchchroot apply - lh_patchrunlevel apply - - # Configure network - lh_patchnetwork apply - - mkdir -p "${LIVE_ROOT}"/binary/casper - for MANIFEST in "${LIVE_ROOT}"/filesystem.manifest* - do - if [ -e "${MANIFEST}" ]; then - mv "${MANIFEST}" "${LIVE_ROOT}"/binary/casper/ - fi - done - - if [ "${LIVE_TYPE}" = "Net" ] - then - # Mount proc - mount proc-live -t proc "${LIVE_CHROOT}"/proc - - # Installing smbfs - lh_chroot "aptitude install --assume-yes smbfs" - - # Unmount proc - umount "${LIVE_CHROOT}"/proc - - if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ] - then - if [ ! -d "${LIVE_CHROOT}"/etc/initramfs-tools ] - then - mkdir "${LIVE_CHROOT}"/etc/initramfs-tools - fi - - # Configuring initramfs for NFS -cat >> "${LIVE_CHROOT}"/etc/initramfs-tools/initramfs.conf << EOF -MODULES=netboot -BOOT=nfs -NFSROOT=auto -EOF - lh_chroot "update-initramfs -tu" - fi - fi - - lh_cleanapt - - # Switching package indices to default - if [ "${LIVE_GENERIC_INDICES}" = "yes" ] - then - lh_setupapt default - lh_configapt deapply-proxy - lh_configapt deapply-recommends - fi - - # Deconfigure network - lh_patchnetwork deapply - - # Deconfigure chroot - lh_patchrunlevel deapply - lh_patchchroot deapply - - # Generating rootfs image - lh_genrootfs - - # Configure chroot - lh_patchchroot apply - lh_patchrunlevel apply - - # Configure network - lh_patchnetwork apply - - lh_cleanapt - - # Switching package indices to custom - lh_setupapt custom - lh_configapt apply-proxy - lh_configapt apply-recommends - - case "${LIVE_TYPE}" in - Iso) - TYPE=iso - ;; - Usb) - TYPE=usb - ;; - Net) - TYPE=net - ;; - esac - - # Mount proc - mount proc-live -t proc "${LIVE_CHROOT}"/proc - - # Install depends - lh_depends install $TYPE - - # Installing syslinux - lh_installsyslinux $TYPE - - # Installing linux-image - lh_installlinux $TYPE - - # Installing memtest - lh_installmemtest86+ $TYPE - - # Deconfigure network - lh_patchnetwork deapply - - # Deconfigure chroot - lh_patchrunlevel deapply - lh_patchchroot deapply - - # Installing templates - if [ "${LIVE_FLAVOUR}" != "minimal" ] || [ "${LIVE_FLAVOUR}" != "mini" ] - then - if [ "${TYPE}" != "usb" ] - then - cp -r "${LIVE_TEMPLATES}"/common/* "${LIVE_ROOT}"/binary - fi - - if [ "${TYPE}" = "iso" ] || [ "${TYPE}" = "usb" ] - then - cp -r "${LIVE_TEMPLATES}"/iso/* "${LIVE_ROOT}"/binary - fi - fi - - # Calculating md5sums - lh_md5sums - - case "${TYPE}" in - iso) - if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ] - then - # Create image - ${GENISOIMAGE} -A "Debian Live" -p "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -publisher "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -o "${LIVE_ROOT}"/"${LIVE_IMAGE}"binary.iso -r -J -l -V "${LIVE_DISK_VOLUME}" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table "${LIVE_ROOT}"/binary ${LIVE_INCLUDE_IMAGE} - else - echo "W: Bootloader on your architecture not yet supported (Continuing in 5 seconds)." - sleep 5 - # Create image - ${GENISOIMAGE} -A "Debian Live" -p "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -publisher "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -o "${LIVE_ROOT}"/"${LIVE_IMAGE}"binary.iso -r -J -l -V "${LIVE_DISK_VOLUME}" "${LIVE_ROOT}"/binary ${LIVE_INCLUDE_IMAGE} - fi - ;; - - net) - cd "${LIVE_ROOT}" && \ - mv binary "`basename ${LIVE_SERVER_PATH}`" && \ - cd .. && \ - tar cfz binary.tar.gz "`basename ${LIVE_ROOT}`/`basename ${LIVE_SERVER_PATH}`" "`basename ${LIVE_ROOT}`/tftpboot" && \ - mv binary.tar.gz "${LIVE_ROOT}" && \ - cd "${OLDPWD}" && \ - mv "`basename ${LIVE_SERVER_PATH}`" binary - ;; - - usb) - # Everything which comes here needs to be cleaned up, - DU_DIM="`du -ms ${LIVE_ROOT}/binary | cut -f1`" - REAL_DIM="`expr ${DU_DIM} + ${DU_DIM} / 20`" # Just 5% more to be sure, need something more sophistcated here... - dd if=/dev/zero of="${LIVE_ROOT}"/binary.img bs=1024k count=${REAL_DIM} - - FREELO="`lh_chroot 'losetup -f'`" - - echo "!!! The following error/warning messages can be ignored !!!" - lh_losetup $FREELO "${LIVE_ROOT}"/binary.img 0 - set +e - lh_chroot "parted -s ${FREELO} mklabel msdos" - lh_chroot "parted -s ${FREELO} mkpartfs primary fat16 0.0 100%" - lh_chroot "parted -s ${FREELO} set 1 boot on" - lh_chroot "parted -s ${FREELO} set 1 lba off" - set -e - cat "${LIVE_CHROOT}"/usr/lib/syslinux/mbr.bin > ${FREELO} - losetup -d ${FREELO} - - lh_losetup $FREELO "${LIVE_ROOT}"/binary.img 1 - lh_chroot "mkfs.msdos -n DEBIAN_LIVE ${FREELO}" - mkdir "${LIVE_ROOT}"/binary.tmp - mount ${FREELO} "${LIVE_ROOT}"/binary.tmp - cp -r "${LIVE_ROOT}"/binary/* "${LIVE_ROOT}"/binary.tmp - umount "${LIVE_ROOT}"/binary.tmp - rmdir "${LIVE_ROOT}"/binary.tmp - lh_chroot "syslinux ${FREELO}" - losetup -d ${FREELO} - - echo "!!! The above error/warning messages can be ignored !!!" - ;; - esac - - # Remove depends - lh_depends remove $TYPE - - # Unmount proc - umount "${LIVE_CHROOT}"/proc - - # Touching stage file - touch "${LIVE_ROOT}"/.stage/image_binary -fi diff --git a/helpers/lh_buildsource b/helpers/lh_buildsource deleted file mode 100755 index 836bd3c..0000000 --- a/helpers/lh_buildsource +++ /dev/null @@ -1,84 +0,0 @@ -#!/bin/sh - -# lh_buildsource.sh - -if [ ! -f "${LIVE_ROOT}"/.stage/image_source ] && [ "${LIVE_SOURCE}" = "yes" ] -then - # Configure chroot - lh_patchnetwork apply - - # Download sources - lh_chroot "dpkg --get-selections" | awk '{ print $1 }' > "${LIVE_CHROOT}"/root/dpkg-selection.txt - lh_chroot "xargs --arg-file=/root/dpkg-selection.txt apt-get source --download-only" - rm -f "${LIVE_CHROOT}"/root/dpkg-selection.txt - - # Sort sources - for DSC in "${LIVE_CHROOT}"/*.dsc - do - SOURCE="`awk '/Source:/ { print $2; }' ${DSC}`" - - if [ "`echo ${SOURCE} | cut -b 1-3`" == "lib" ] - then - LETTER="`echo ${SOURCE} | cut -b 1-4`" - else - LETTER="`echo ${SOURCE} | cut -b 1`" - fi - - # Install directory - install -d -m 0755 "${LIVE_ROOT}"/source/"${LETTER}"/"${SOURCE}" - - # Move files - mv "${LIVE_CHROOT}"/"${SOURCE}"_* "${LIVE_ROOT}"/source/"${LETTER}"/"${SOURCE}" - done - - case "${1}" in - generic) - # Create tarball - tar cf source.tar "$LIVE_ROOT"/source - ;; - - iso) - # Create image - ${GENISOIMAGE} -A "Debian Live" -p "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -publisher "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -o "${LIVE_ROOT}"/"${LIVE_IMAGE}"source.iso -r -J -l -V "${LIVE_DISK_VOLUME}" "${LIVE_ROOT}"/source - ;; - - net) - # Create tarball - tar cfz source.tar.gz "${LIVE_ROOT}"/source - ;; - - usb) - # Create image - DU_DIM="`du -ms ${LIVE_ROOT}/source | cut -f1`" - REAL_DIM="`expr ${DU_DIM} + ${DU_DIM} / 20`" # Just 5% more to be sure, need something more sophistcated here... - dd if=/dev/zero of="${LIVE_ROOT}"/source.img bs=1024k count=${REAL_DIM} - FREELO=`losetup -f` - - echo "!!! The following error/warning messages can be ignored !!!" - lh_losetup $FREELO "${LIVE_ROOT}"/source.img 0 - set +e - lh_chroot "parted -s ${FREELO} mklabel msdos" - lh_chroot "parted -s ${FREELO} mkpartfs primary fat16 0.0 100%" - lh_chroot "parted -s ${FREELO} set 1 lba off" - set -e - losetup -d ${FREELO} - - lh_losetup $FREELO "${LIVE_ROOT}"/source.img 1 - lh_chroot "mkfs.msdos -n DEBIAN_LIVE ${FREELO}" - mkdir "${LIVE_ROOT}"/source.tmp - mount ${FREELO} "${LIVE_ROOT}"/source.tmp - cp -r "${LIVE_ROOT}"/source/* "${LIVE_ROOT}"/source.tmp - umount "${LIVE_ROOT}"/source.tmp - rmdir "${LIVE_ROOT}"/source.tmp - losetup -d ${FREELO} - echo "!!! The above error/warning messages can be ignored !!!" - ;; - esac - - - # Deconfigure network - lh_patchnetwork deapply - - # Touching stage file - touch "${LIVE_ROOT}"/.stage/image_source -fi diff --git a/helpers/lh_cdebootstrap b/helpers/lh_cdebootstrap deleted file mode 100755 index c1f0d7a..0000000 --- a/helpers/lh_cdebootstrap +++ /dev/null @@ -1,33 +0,0 @@ -#!/bin/sh - -if [ ! -f "${LIVE_ROOT}"/.stage/bootstrap ] -then - # Create chroot directory - if [ ! -d "${LIVE_CHROOT}" ] - then - mkdir -p "${LIVE_CHROOT}" - fi - - if [ -n "${LIVE_BOOTSTRAP_CONFIG}" ]; then - SUITE_CONFIG="--suite-config ${LIVE_BOOTSTRAP_CONFIG}" - fi - - # Bootstrap system - if [ "${LIVE_FLAVOUR}" = "mini" ] - then - cdebootstrap --arch="${LIVE_ARCHITECTURE}" --flavour=minimal ${SUITE_CONFIG} "${LIVE_DISTRIBUTION}" "${LIVE_CHROOT}" "${LIVE_MIRROR}" - else - cdebootstrap --arch="${LIVE_ARCHITECTURE}" --flavour="${LIVE_FLAVOUR}" ${SUITE_CONFIG} "${LIVE_DISTRIBUTION}" "${LIVE_CHROOT}" "${LIVE_MIRROR}" - fi - - # Remove package cache - rm -rf "${LIVE_CHROOT}"/var/cache/bootstrap - - # Touching stage file - if [ ! -d "${LIVE_ROOT}"/.stage ] - then - mkdir "${LIVE_ROOT}"/.stage - fi - - touch "${LIVE_ROOT}"/.stage/bootstrap -fi diff --git a/helpers/lh_chroot b/helpers/lh_chroot index 511cdca..75f3174 100755 --- a/helpers/lh_chroot +++ b/helpers/lh_chroot @@ -1,6 +1,50 @@ #!/bin/sh -# lh_chroot.sh +# lh_chroot(1) - customize the Debian system -# Execute commands chrooted -chroot "${LIVE_CHROOT}" /usr/bin/env -i HOME="/root" PATH="/usr/sbin:/usr/bin:/sbin:/bin" TERM="${TERM}" ftp_proxy="${LIVE_PROXY_FTP}" http_proxy="${LIVE_PPROXY_HTTP}" DEBIAN_FRONTEND="${LIVE_DEBCONF_FRONTEND}" DEBIAN_PRIORITY="${LIVE_DEBCONF_PRIORITY}" ${1} +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Configuring chroot +lh_chroot_proc install +lh_chroot_sysfs install +lh_chroot_debianchroot install +lh_chroot_sysvrc install +lh_chroot_hosts install +lh_chroot_resolv install +lh_chroot_apt install +lh_chroot_sources install +lh_chroot_linuximage install + +# Customizing chroot +lh_chroot_tasks +lh_chroot_packageslist +lh_chroot_packages +lh_chroot_localpackages +lh_chroot_localpackageslist +lh_chroot_localization +lh_chroot_hacks +lh_chroot_localincludes +lh_chroot_sysvinit +lh_chroot_hooks +lh_chroot_localhooks +lh_chroot_symlinks + +# Deconfiguring chroot +lh_chroot_linuximage remove +lh_chroot_sources remove +lh_chroot_apt remove +lh_chroot_resolv remove +lh_chroot_hosts remove +lh_chroot_sysvrc remove +lh_chroot_debianchroot remove +lh_chroot_sysfs remove +lh_chroot_proc remove diff --git a/helpers/lh_chroot_apt b/helpers/lh_chroot_apt new file mode 100755 index 0000000..3983923 --- /dev/null +++ b/helpers/lh_chroot_apt @@ -0,0 +1,141 @@ +#!/bin/sh + +# lh_chroot_apt(1) - manage /etc/apt/apt.conf + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +case "${1}" in + install) + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/chroot_apt + + if [ "${LH_APT}" = "aptitude" ] && [ ! -d "${LIVE_CHROOT}"/etc/apt/apt.conf.d ] + then + mkdir -p "${LIVE_CHROOT}"/etc/apt/apt.conf.d + fi + + # Configuring apt ftp proxy + if [ -n "${LH_APT_FTPPROXY}" ] + then + case "${LH_APT}" in + apt) + echo "Acquire::ftp::Proxy \"${LH_APT_FTPPROXY}\";" >> "${LIVE_CHROOT}"/etc/apt/apt.conf + ;; + + aptitude) + echo "Acquire::ftp::Proxy \"${LH_APT_FTPPROXY}\";" > "${LIVE_CHROOT}"/etc/apt/apt.conf.d/ftp-proxy + ;; + esac + fi + + # Configuring apt http proxy + if [ -n "${LH_APT_HTTPPROXY}" ] + then + case "${LH_APT}" in + apt) + echo "Acquire::http::Proxy \"${LH_APT_HTTPPROXY}\";" >> "${LIVE_CHROOT}"/etc/apt/apt.conf + ;; + + aptitude) + echo "Acquire::http::Proxy \"${LH_APT_HTTPPROXY}\";" > "${LIVE_CHROOT}"/etc/apt/apt.conf.d/http-proxy + ;; + esac + fi + + # Configuring apt pdiffs + if [ "${LH_APT_PDIFFS}" = "enabled" ] + then + case "${LH_APT}" in + apt) + echo "Acquire::PDiffs \"true\";" >> "${LIVE_CHROOT}"/etc/apt/apt.conf + ;; + + aptitude) + echo "Acquire::PDiffs \"true\";" > "${LIVE_CHROOT}"/etc/apt/apt.conf.d/pdiffs + ;; + esac + else + case "${LH_APT}" in + apt) + echo "Acquire::PDiffs \"false\";" >> "${LIVE_CHROOT}"/etc/apt/apt.conf + ;; + + aptitude) + echo "Acquire::PDiffs \"false\";" > "${LIVE_CHROOT}"/etc/apt/apt.conf.d/pdiffs + ;; + esac + fi + + # Configuring apt recommends + if [ "${LH_APT_RECOMMENDS}" = "enabled" ] + then + case "${LH_APT}" in + apt) + echo "Aptitude::Recommends-Important \"true\";" >> "${LIVE_CHROOT}"/etc/apt/apt.conf + ;; + + aptitude) + echo "Aptitude::Recommends-Important \"true\";" > "${LIVE_CHROOT}"/etc/apt/apt.conf.d/recommends + ;; + esac + else + case "${LH_APT}" in + apt) + echo "Aptitude::Recommends-Important \"false\";" >> "${LIVE_CHROOT}"/etc/apt/apt.conf + ;; + + aptitude) + echo "Aptitude::Recommends-Important \"false\";" > "${LIVE_CHROOT}"/etc/apt/apt.conf.d/recommends + ;; + esac + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_apt + ;; + + remove) + # Deconfiguring apt settings + rm -f "${LIVE_CHROOT}"/etc/apt/apt.conf + + # Deconfiguring aptitude ftp proxy + rm -f "${LIVE_CHROOT}"/etc/apt/apt.conf.d/ftp-proxy + + # Deconfiguring aptitude http proxy + rm -f "${LIVE_CHROOT}"/etc/apt/apt.conf.d/http-proxy + + # Deconfiguring aptitude pdiffs + rm -f "${LIVE_CHROOT}"/etc/apt/apt.conf.d/pdiffs + + # Deconfiguring aptitude recommends + rm -f "${LIVE_CHROOT}"/etc/apt/apt.conf.d/recommends + + # Removing stage file + rm -f "${LIVE_ROOT}"/.stage/chroot_apt + ;; + + *) + echo "Usage: ${0} {install|remove}" + exit 1 + ;; +esac diff --git a/helpers/lh_chroot_debianchroot b/helpers/lh_chroot_debianchroot new file mode 100755 index 0000000..6272fe0 --- /dev/null +++ b/helpers/lh_chroot_debianchroot @@ -0,0 +1,63 @@ +#!/bin/sh + +# lh_chroot_debianchroot(1) - manage /etc/debian_chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +case "${1}" in + install) + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/chroot_debianchroot + + if [ -f "${LIVE_CHROOT}"/etc/debian_chroot ] + then + # Save chroot file + mv "${LIVE_CHROOT}"/etc/debian_chroot "${LIVE_CHROOT}"/etc/debian_chroot.orig + fi + + # Create chroot file + echo "live" > "${LIVE_CHROOT}"/etc/debian_chroot + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_debianchroot + ;; + + remove) + if [ -f "${LIVE_CHROOT}"/etc/debian_chroot.orig ] + then + # Restore chroot file + mv "${LIVE_CHROOT}"/etc/debian_chroot.orig "${LIVE_CHROOT}"/etc/debian_chroot + else + # Remove chroot file + rm -f "${LIVE_CHROOT}"/etc/debian_chroot + fi + + # Removing stage file + rm -f "${LIVE_ROOT}"/.stage/chroot_debianchroot + ;; + + *) + echo "Usage: ${0} {install|remove}" + exit 1 + ;; +esac diff --git a/helpers/lh_chroot_hacks b/helpers/lh_chroot_hacks new file mode 100755 index 0000000..5535458 --- /dev/null +++ b/helpers/lh_chroot_hacks @@ -0,0 +1,60 @@ +#!/bin/sh + +# lh_chroot_hacks(1) - execute hacks in chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_hacks + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +case "${LIVE_BINARY_IMAGE}" in + net) + case "${LH_APT}" in + apt) + Chroot "apt-get install --yes smbfs" + ;; + + aptitude) + Chroot "aptitude install --assume-yes smbfs" + ;; + esac + + if [ ! -d "${LIVE_CHROOT}"/etc/initramfs-tools ] + then + mkdir "${LIVE_CHROOT}"/etc/initramfs-tools + fi + + # Configuring initramfs for NFS +cat >> "${LIVE_CHROOT}"/etc/initramfs-tools/initramfs.conf << EOF +MODULES=netboot +BOOT=nfs +NFSROOT=auto +EOF + ;; +esac + +# Update initramfs +Chroot "update-initramfs -tu" + +# Creating stage file +Create_stagefile "${LIVE_ROOT}"/.stage/chroot_hacks diff --git a/helpers/lh_chroot_hooks b/helpers/lh_chroot_hooks new file mode 100755 index 0000000..727eed9 --- /dev/null +++ b/helpers/lh_chroot_hooks @@ -0,0 +1,50 @@ +#!/bin/sh + +# lh_chroot_hooks(1) - execute hooks in chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_hooks + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Processing hooks +if [ -n "${LIVE_PACKAGES_LIST}" ] && [ -f /usr/share/live-helper/hooks/"${LIVE_PACKAGES_LIST}" ] +then + # Copying hook + cp /usr/share/live-helper/hooks/"${LIVE_PACKAGES_LIST}" "${LIVE_CHROOT}"/root + + # Making hook executable + if [ -x "${LIVE_CHROOT}"/root/${LIVE_PACKAGES_LIST} ] + then + chmod +x "${LIVE_CHROOT}"/root/${LIVE_PACKAGES_LIST} + fi + + # Executing hook + Chroot "/root/${LIVE_PACKAGES_LIST}" + + # Removing hook + rm -f "${LIVE_CHROOT}"/root/"${LIVE_PACKAGE_LIST}" + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_hooks +fi diff --git a/helpers/lh_chroot_hosts b/helpers/lh_chroot_hosts new file mode 100755 index 0000000..d1c1607 --- /dev/null +++ b/helpers/lh_chroot_hosts @@ -0,0 +1,66 @@ +#!/bin/sh + +# lh_chroot_hosts(1) - manage /etc/hosts + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +case "${1}" in + install) + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/chroot_hosts + + if [ -f "${LIVE_CHROOT}"/etc/hosts ] + then + # Save hosts file + cp "${LIVE_CHROOT}"/etc/hosts "${LIVE_CHROOT}"/etc/hosts.orig + fi + + if [ -f /etc/hosts ] + then + # Copy hosts file + cp /etc/hosts "${LIVE_CHROOT}"/etc/hosts + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_hosts + ;; + + remove) + if [ -f "${LIVE_CHROOT}"/etc/hosts.orig ] + then + # Restore hosts file + mv "${LIVE_CHROOT}"/etc/hosts.orig "${LIVE_CHROOT}"/etc/hosts + else + # Remove hosts file + rm -f "${LIVE_CHROOT}"/etc/hosts + fi + + # Removing stage file + rm -f "${LIVE_ROOT}"/.stage/chroot_hosts + ;; + + *) + echo "Usage: ${0} {install|remove}" + exit 1 + ;; +esac diff --git a/helpers/lh_chroot_linuximage b/helpers/lh_chroot_linuximage new file mode 100755 index 0000000..354c507 --- /dev/null +++ b/helpers/lh_chroot_linuximage @@ -0,0 +1,74 @@ +#!/bin/sh + +# lh_chroot_linuximage(1) - manage /etc/kernel-img.conf + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +case "${1}" in + install) + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/chroot_linuximage + + if [ -f "${LIVE_CHROOT}"/etc/kernel-img.conf ] + then + # Saving kernel-img.conf + cp "${LIVE_CHROOT}"/etc/kernel-img.conf "${LIVE_CHROOT}"/etc/kernel-img.conf.old + fi + + # Configuring kernel-img.conf + echo "do_initrd = Yes" >> "${LIVE_CHROOT}"/etc/kernel-img.conf + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_linuximage + + # Installing linux-image, modules and casper + case "${LH_APT}" in + apt) + Chroot "apt-get install --yes ${LIVE_KERNEL_PACKAGES}" + ;; + + aptitude) + Chroot "aptitude install --assume-yes ${LIVE_KERNEL_PACKAGES}" + ;; + esac + ;; + + remove) + if [ -f "${LIVE_CHROOT}"/etc/kernel-img.conf.old ] + then + # Restoring kernel-img.conf file + mv "${LIVE_CHROOT}"/etc/kernel-img.conf.old "${LIVE_CHROOT}"/etc/kernel-img.conf + else + # Removing kernel-img.conf file + rm -f "${LIVE_CHROOT}"/etc/kernel-img.conf + fi + + # Removing stage file + rm -f "${LIVE_ROOT}"/.stage/chroot_linuximage + ;; + + *) + echo "Usage: ${0} {install|remove}" + exit 1 + ;; +esac diff --git a/helpers/lh_chroot_localhooks b/helpers/lh_chroot_localhooks new file mode 100755 index 0000000..4d0bf3b --- /dev/null +++ b/helpers/lh_chroot_localhooks @@ -0,0 +1,53 @@ +#!/bin/sh + +# lh_chroot_localhooks(1) - execute hooks in chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_localhooks + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Processing localhooks +if ls "${LIVE_ROOT}"/config/chroot_localhooks/* &> /dev/null +then + for HOOK in "${LIVE_ROOT}"/config/chroot_localhooks/* + do + # Copying hook + cp "${HOOK}" "${LIVE_CHROOT}"/root + + # Making hook executable + if [ -x "${LIVE_CHROOT}"/root/"${HOOK}" ] + then + chmod +x "${LIVE_CHROOT}"/root/${HOOK} + fi + + # Executing hook + Chroot "/root/`basename ${HOOK}`" + + # Removing hook + rm -f "${LIVE_CHROOT}"/"`basename ${HOOK}`" + done + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_localhooks +fi diff --git a/helpers/lh_chroot_localincludes b/helpers/lh_chroot_localincludes new file mode 100755 index 0000000..4c0957a --- /dev/null +++ b/helpers/lh_chroot_localincludes @@ -0,0 +1,39 @@ +#!/bin/sh + +# lh_chroot_localincludes(1) - copy files into chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_localincludes + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +if ls "${LIVE_ROOT}"/config/chroot_localincludes/* &> /dev/null +then + cd "${LIVE_ROOT}"/config/chroot_localincludes + + # Copying includes + find . | cpio -dmpu "${LIVE_CHROOT}" + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_localincludes +fi diff --git a/helpers/lh_chroot_localization b/helpers/lh_chroot_localization new file mode 100755 index 0000000..bbf05bf --- /dev/null +++ b/helpers/lh_chroot_localization @@ -0,0 +1,695 @@ +#!/bin/sh + +# lh_chroot_localization(1) - install localization packages into chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_localization + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Setting localizations +if [ -n "${LIVE_LANGUAGE}" ] +then + case "${LIVE_LANGUAGE}" in + af) + # Afrikaans + LOCALIZATIONS="iceweasel kde openoffice" + ;; + + as-in) + # Assamese + LOCALIZATIONS="openoffice" + ;; + + ar) + # Arabic + LOCALIZATIONS="iceweasel kde openoffice" + ;; + + az) + # Azerbaijani + LOCALIZATIONS="kde" + ;; + + be) + # Belarusian + LOCALIZATIONS="iceape iceweasel openoffice" + + # Overrides + OPENOFFICE="be-by" + ;; + + bg) + # Bulgarian + LOCALIZATIONS="icedove iceweasel kde openoffice" + ;; + + bn) + # Bengali + LOCALIZATIONS="kde openoffice" + ;; + + br) + # Breton + LOCALIZATIONS="kde openoffice" + ;; + + bs) + # Bosnian + LOCALIZATION="kde openoffice" + ;; + + ca) + # Catalan + LOCALIZATIONS="iceape icedove iceweasel kde koffice openoffice" + ;; + + cs) + # Czech + LOCALIZATIONS="iceape icedove iceweasel kde koffice openoffice" + ;; + + cy-gb) + # Welsh + LOCALIZATIONS="iceweasel kde koffice openoffice" + + # Overrides + KDE="cy" + KOFFICE="cy" + OPENOFFICE="cy" + ;; + + da) + # Danish + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + ;; + + de) + # German + LOCALIZATIONS="iceape icedove iceweasel kde koffice openoffice" + ;; + + dz-bt) + # Dzongkha + LOCALIZATIONS="iceweasel openoffice" + + # Overrides + OPENOFFICE="dz" + ;; + + el) + # Greek + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + ;; + + en-gb) + # English (Great Britain) + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + + # Overrides + KDE="engb" + KOFFICE="engb" + ;; + + en-za) + # English (South Africa) + LOCALIZATIONS="openoffice" + ;; + + eo) + # Esperanto + LOCALIZATIONS="kde openoffice" + ;; + + es-ar) + # Spanish (Argentina) + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + + # Overrides + KDE="es" + KOFFICE="es" + OPENOFFICE="es" + ;; + + es-es) + # Spanish (Spain) + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + + # Overrides + KDE="es" + KOFFICE="es" + OPENOFFICE="es" + ;; + + et-ee) + # Estonian + LOCALIZATIONS="iceweasel kde koffice openoffice" + + # Overrides + KDE="et" + KOFFICE="et" + OPENOFFICE="et" + ;; + + eu) + # Basque + LOCALIZATIONS="icedove iceweasel kde koffice" + ;; + + fa-ir) + # Persian + LOCALIZATIONS="iceweasel kde openoffice" + + # Overrides + KDE="fa" + OPENOFFICE="fa" + ;; + + fi) + # Finnish + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + ;; + + fr) + # French + LOCALIZATIONS="iceape icedove iceweasel kde koffice openoffice" + ;; + + fur-it) + # Furlan + LOCALIZATIONS="iceweasel" + ;; + + fy-nl) + # Frisian + LOCALIZATIONS="iceweasel kde" + + # Overrides + KDE="fy" + ;; + + ga-ie) + # Irish (Ireland) + LOCALIZATIONS="icedove iceweasel kde openoffice" + + # Overrides + ICEDOVE="ga" + KDE="ga" + OPENOFFICE="ga" + ;; + + gl) + # Galician + LOCALIZATIONS="kde" + ;; + + gu-in) + # Gujarati (India) + LOCALIZATIONS="icedove iceweasel openoffice" + + # Overrides + ICEDOVE="gu" + ;; + + he) + # Hebrew + LOCALIZATIONS="iceape icedove iceweasel kde openoffice" + ;; + + hi) + # Hindi + LOCALIZATIONS="kde openoffice" + ;; + + hr) + # Croatian + LOCALIZATIONS="kde koffice openoffice" + ;; + + hu) + # Hungarian + LOCALIZATIONS="icedove iceweasel kde openoffice" + ;; + + in) + # Indic + LOCALIZATIONS="openoffice" + ;; + + is) + # Icelandic + LOCALIZATIONS="kde" + ;; + + it) + # Italian + LOCALIZATIONS="iceape icedove iceweasel kde koffice openoffice" + ;; + + ja) + # Japanese + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + ;; + + ka) + # Georgian + LOCALIZATIONS="iceweasel openoffice" + ;; + + km) + # Khmer + LOCALIZATIONS="kde openoffice" + ;; + + ko) + # Korean + LOCALIZATIONS="icedove iceweasel kde openoffice" + ;; + + ku) + # Kurdish + LOCALIZATIONS="iceweasel openoffice" + ;; + + lo) + # Lao + LOCALIZATIONS="openoffice" + ;; + + lt) + # Lithuanian + LOCALIZATIONS="icedove iceweasel kde openoffice" + ;; + + lv) + # Latvian + LOCALIZATIONS="kde koffice openoffice" + ;; + + mk) + # Macedonian + LOCALIZATIONS="icedove iceweasel kde openoffice" + ;; + + ml-in) + # Malayalam + LOCALIZATIONS="openoffice" + ;; + + mn) + # Mongolian + LOCALIZATIONS="iceweasel kde" + ;; + + ms) + # Malay + LOCALIZATIONS="kde koffice" + ;; + + nb-no) + # Bokmaal (Norway) + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + + # Overrides + ICEDOVE="nb" + KDE="nb" + KOFFICE="nb" + OPENOFFICE="nb" + ;; + + nds) + # Low Saxon + LOCALIZATIONS="kde" + ;; + + ne) + # Nepalese + LOCALIZATIONS="openoffice" + ;; + + nl) + # Dutch + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + ;; + + nn-no) + # Nynorsk (Norway) + LOCALIZATIONS="iceweasel kde openoffice" + + # Overrides + KDE="nn" + OPENOFFICE="nn" + ;; + + nr) + # Ndebele + LOCALIZATIONS="openoffice" + ;; + + ns) + # Northernsotho + LOCALIZATIONS="openoffice" + ;; + + or-in) + # Oriya + LOCALIZATIONS="openoffice" + ;; + + pa-in) + # Punjabi (India) + LOCALIZATIONS="icedove iceweasel kde openoffice" + + # Overrides + ICEDOVE="pa" + KDE="pa" + ;; + + pl) + # Polish + LOCALIZATIONS="iceape icedove iceweasel kde koffice openoffice" + ;; + + pt-br) + # Portugese (Brazil) + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + + # Overrides + KDE="ptbr" + KOFFICE="ptbr" + ;; + + pt-pt) + # Portugese (Portugal) + LOCALIZATIONS="iceweasel kde koffice openoffice" + + # Overrides + KDE="pt" + KOFFICE="pt" + OPENOFFICE="pt" + ;; + + ro) + # Romanian + LOCALIZATIONS="iceweasel kde" + ;; + + roa-es-val) + # Valencian (Spain) + LOCALIZATIONS="iceweasel" + ;; + + ru) + # Russian + LOCALIZATIONS="iceape icedove iceweasel kde koffice openoffice" + ;; + + rw) + # Kinarwanda + LOCALIZATIONS="kde openoffice" + ;; + + se) + # Northern Sami + LOCALIZATIONS="kde" + ;; + + sk) + # Slovak + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + ;; + + sl) + # Slovenian + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + ;; + + sr-cs) + # Serbian + LOCALIZATIONS="kde koffice openoffice" + + # Overrides + KDE="sr" + KOFFICE="sr" + ;; + + sr-latin) + # Latin Serbian + LOCALIZATIONS="kde koffice" + + # Overrides + KDE="srlatin" + KOFFICE="srlatin" + ;; + + ss) + # Swazi + LOCALIZATIONS="kde openoffice" + ;; + + st) + # Southern_sotho + LOCALIZATIONS="openoffice" + ;; + + sv-se) + # Swedish + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + + # Overrides + ICEDOVE="sv" + KDE="sv" + KOFFICE="sv" + OPENOFFICE="sv" + ;; + + ta-in) + # Tamil + LOCALIZATIONS="kde openoffice" + + # Overrides + KDE="ta" + ;; + + te-in) + # Telugu + LOCALIZATIONS="openoffice" + ;; + + tg) + # Tajik + LOCALIZATIONS="kde openoffice" + ;; + + th) + # Thai + LOCALIZATIONS="openoffice" + ;; + + tn) + # Tswana + LOCALIZATIONS="openoffice" + ;; + + tr) + # Turkish + LOCALIZATIONS="icedove iceweasel kde kofffice openoffice" + ;; + + ts) + # Tsonga + LOCALIZATIONS="openoffice" + ;; + + uk-ua) + # Ukrainian + LOCALIZATIONS="icedove iceweasel kde kofffice openoffice" + + # Overrides + ICEDOVE="uk" + KDE="uk" + KDE="uk" + OPENOFFICE="uk" + ;; + + uz) + # Uzbek + LOCALIZATIONS="kde" + ;; + + ve) + # Venda + LOCALIZATIONS="openoffice" + ;; + + vi) + # Vietnamese + LOCALIZATIONS="openoffice" + ;; + + xh) + # Xhosa + LOCALIZATIONS="openoffice" + ;; + + za) + # South African + LOCALIZATIONS="openoffice" + ;; + + zh-cn) + # Chinese (China) + LOCALIZATIONS="icedove iceweasel kde koffice openoffice" + + # Overrides + KDE="zhcn" + KOFFICE="zhcn" + ;; + + zh-tw) + # Chinese (Taiwan) + LOCALIZATIONS="iceweasel kde koffice openoffice" + + # Overrides + KDE="zhtw" + KOFFICE="zhtw" + ;; + + zu) + # Zulu + LOCALIZATIONS="openoffice" + ;; + esac + + # Setting languages + if [ -z "${ICEAPE}" ] + then + ICEAPE="${LIVE_LANGUAGE}" + fi + + if [ -z "${ICEDOCE}" ] + then + ICEDOVE="${LIVE_LANGUAGE}" + fi + + if [ -z "${ICEWEASEL}" ] + then + ICEWEASEL="${LIVE_LANGUAGE}" + fi + + if [ -z "${KDE}" ] + then + KDE="${LIVE_LANGUAGE}" + fi + + if [ -z "${KOFFICE}" ] + then + KOFFICE="${LIVE_LANGUAGE}" + fi + + if [ -z "${OPENOFFICE}" ] + then + OPENOFFICE="${LIVE_LANGUAGE}" + fi + + # Setting packages + for LOCALIZATION in ${LOCALIZATIONS} + do + case "${LOCALZATION}" in + iceape) + if [ -f "${LIVE_CHROOT}"/usr/bin/iceape ] + then + PACKAGES="${PACKAGES} iceweasel-l10n-${ICEAPE}" + fi + ;; + + icedove) + if [ -f "${LIVE_CHROOT}"/usr/bin/icedove ] + then + PACKAGES="${PACKAGES} icedove-locale-${ICEDOVE}" + fi + ;; + + iceweasel) + if [ -f "${LIVE_CHROOT}"/usr/bin/iceweasel ] + then + PACKAGES="${PACKAGES} iceweasel-l10n-${ICEWEASEL}" + fi + ;; + + kde) + if [ -f "${LIVE_CHROOT}"/usr/bin/kstart ] + then + PACKAGES="${PACKAGES} kde-i18n-${KDE}" + fi + ;; + + koffice) + if [ -f "${LIVE_CHROOT}" ] + then + PACKAGES="${PACKAGES} koffice-i18n-${KOFFICE}" + fi + ;; + + openoffice) + if [ -f "${LIVE_CHROOT}"/usr/bin/ooffice ] + then + PACKAGES="${PACKAGES} openoffice.org-l10n-${OPENOFFICE}" + fi + ;; + esac + done + + # Restore old cache + if [ -d "${LIVE_ROOT}"/cache/chroot_localization ] + then + cp "${LIVE_ROOT}"/cache/chroot_localization/*.deb "${LIVE_CHROOT}"/var/cache/apt/archives + fi + + # Installing packages + case "${LH_APT}" in + apt) + Chroot "apt-get install --yes ${PACKAGES}" + ;; + + aptitude) + Chroot "apt-get install --assume-yes ${PACKAGES}" + ;; + esac + + # Saving new cache + Chroot "apt-get autoclean" + + if ls "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb &> /dev/null + then + if [ ! -d "${LIVE_ROOT}"/cache/chroot_localization ] + then + mkdir -p "${LIVE_ROOT}"/cache/chroot_localization + fi + + mv -f "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb "${LIVE_ROOT}"/cache/chroot_localization + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_localization +fi diff --git a/helpers/lh_chroot_localpackages b/helpers/lh_chroot_localpackages new file mode 100755 index 0000000..1ed4339 --- /dev/null +++ b/helpers/lh_chroot_localpackages @@ -0,0 +1,75 @@ +#!/bin/sh + +# lh_chroot_localpackages(1) - install local packages into chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_localpackages + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +if ls "${LIVE_ROOT}"/config/chroot_localpackages/*.deb &> /dev/null +then + # Restore old cache + if [ -d "${LIVE_ROOT}"/cache/chroot_localpackages ] + then + cp "${LIVE_ROOT}"/cache/chroot_localpackages/*.deb "${LIVE_CHROOT}"/var/cache/apt/archives + fi + + # Copying packages + cp "${LIVE_ROOT}"/config/chroot_localpackages/*.deb "${LIVE_CHROOT}"/root + + # Installing packages + Chroot "find /root -name *.deb" > "${LIVE_CHROOT}"/root/localpackages + Chroot "xargs --arg-file=/root/localpackages dpkg -i" || true + + # Cleaning dependencies + case "${LH_APT}" in + apt) + Chroot "apt-get install -f --yes" + ;; + + aptitude) + Chroot "aptitude install -f --assume-yes" + ;; + esac + + # Removing package files + rm -f "${LIVE_CHROOT}"/root/*.deb + rm -f "${LIVE_CHROOT}"/root/localpackages + + # Saving new cache + Chroot "apt-get autoclean" + + if ls "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb &> /dev/null + then + if [ ! -d "${LIVE_ROOT}"/cache/chroot_localpackages ] + then + mkdir -p "${LIVE_ROOT}"/cache/chroot_localpackages + fi + + mv -f "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb "${LIVE_ROOT}"/cache/chroot_localpackages + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_localpackages +fi diff --git a/helpers/lh_chroot_localpackageslist b/helpers/lh_chroot_localpackageslist new file mode 100755 index 0000000..a7313cb --- /dev/null +++ b/helpers/lh_chroot_localpackageslist @@ -0,0 +1,73 @@ +#!/bin/sh + +# lh_chroot_localpackageslist(1) - install local packages into chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_localpackageslist + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +if ls "${LIVE_ROOT}"/config/chroot_localpackageslist/* &> /dev/null +then + # Restore old cache + if [ -d "${LIVE_ROOT}"/cache/chroot_localpackageslist ] + then + cp "${LIVE_ROOT}"/cache/chroot_localpackageslist/*.deb "${LIVE_CHROOT}"/var/cache/apt/archives + fi + + for PACKAGESLIST in "${LIVE_ROOT}"/config/chroot_localpackageslist/* + do + # Copying package list + grep -v "^#" "${PACKAGESLIST}" > "${LIVE_CHROOT}"/root/"`basename ${PACKAGESLIST}`" + + # Installing package list + case "${LH_APT}" in + apt) + Chroot "xargs --arg-file=/root/`basename ${PACKAGESLIST}` apt-get install --yes" + ;; + + aptitude) + Chroot "xargs --arg-file=/root/`basename ${PACKAGESLIST}` aptitude install --assume-yes" + ;; + esac + + # Removing package list + rm -f "${LIVE_CHROOT}"/root/"`basename ${PACKAGESLIST}`" + done + + # Saving new cache + Chroot "apt-get autoclean" + + if ls "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb &> /dev/null + then + if [ ! -d "${LIVE_ROOT}"/cache/chroot_localpackageslist ] + then + mkdir -p "${LIVE_ROOT}"/cache/chroot_localpackageslist + fi + + mv -f "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb "${LIVE_ROOT}"/cache/chroot_localpackageslist + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_localpackageslist +fi diff --git a/helpers/lh_chroot_packages b/helpers/lh_chroot_packages new file mode 100755 index 0000000..14e9659 --- /dev/null +++ b/helpers/lh_chroot_packages @@ -0,0 +1,65 @@ +#!/bin/sh + +# lh_chroot_packages(1) - install packages into chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/bootstrap +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_packages + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +if [ -n "${LIVE_PACKAGES}" ] +then + # Restore old cache + if [ -d "${LIVE_ROOT}"/cache/chroot ] + then + cp "${LIVE_ROOT}"/cache/chroot_packages/*.deb "${LIVE_CHROOT}"/var/cache/apt/archives + fi + + # Installing packages + case "${LH_APT}" in + apt) + Chroot "apt-get install --yes ${LIVE_PACKAGES}" + ;; + + aptitude) + Chroot "aptitude install --assume-yes ${LIVE_PACKAGES}" + ;; + esac + + # Saving new cache + Chroot "apt-get autoclean" + + if ls "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb &> /dev/null + then + if [ ! -d "${LIVE_ROOT}"/cache/chroot_packages ] + then + mkdir -p "${LIVE_ROOT}"/cache/chroot_packages + fi + + mv -f "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb "${LIVE_ROOT}"/cache/chroot_packages + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_packages +fi diff --git a/helpers/lh_chroot_packageslist b/helpers/lh_chroot_packageslist new file mode 100755 index 0000000..c222d7d --- /dev/null +++ b/helpers/lh_chroot_packageslist @@ -0,0 +1,76 @@ +#!/bin/sh + +# lh_chroot_packageslist(1) - install packages list into chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_packageslist + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +if [ -n "${LIVE_PACKAGES_LIST}" ] +then + # Restore old cache + if [ -d "${LIVE_ROOT}"/cache/chroot_packageslist ] + then + cp "${LIVE_ROOT}"/cache/chroot_packageslist/*.deb "${LIVE_CHROOT}"/var/cache/apt/archives + fi + + for LIST in ${LIVE_PACKAGES_LIST} + do + if [ -f /usr/share/live-helper/lists/"${LIST}" ] + then + # Copying package list + grep -v "^#" /usr/share/live-helper/lists/"${LIST}" > "${LIVE_CHROOT}"/root/"${LIST}" + + # Installing package list + case "${LH_APT}" in + apt) + Chroot "xargs --arg-file=/root/${LIST} apt-get install --yes" + ;; + + aptitude) + Chroot "xargs --arg-file=/root/${LIST} aptitude install --assume-yes" + ;; + esac + + # Removing package list + rm -f "${LIVE_CHROOT}"/root/"${LIST}" + fi + done + + # Saving new cache + Chroot "apt-get autoclean" + + if ls "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb &> /dev/null + then + if [ ! -d "${LIVE_ROOT}"/cache/chroot_packageslist ] + then + mkdir -p "${LIVE_ROOT}"/cache/chroot_packageslist + fi + + mv -f "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb "${LIVE_ROOT}"/cache/chroot_packageslist + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_packageslist +fi diff --git a/helpers/lh_chroot_proc b/helpers/lh_chroot_proc new file mode 100755 index 0000000..1b78ecf --- /dev/null +++ b/helpers/lh_chroot_proc @@ -0,0 +1,61 @@ +#!/bin/sh + +# lh_chroot_proc(1) - mount /proc + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +case "${1}" in + install) + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/chroot_proc + + if [ ! -d "${LIVE_CHROOT}"/proc ] + then + # Creating mountpoint + mkdir -p "${LIVE_CHROOT}"/proc + fi + + # Mounting /proc + mount proc-live -t proc "${LIVE_CHROOT}"/proc + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_proc + ;; + + remove) + # Workaround binfmt-support /proc locking + umount "${LIVE_CHROOT}"/proc/sys/fs/binfmt_misc > /dev/null 2>&1 || true + + # Unmounting /proc + #fuser -km "${LIVE_CHROOT}"/proc + umount "${LIVE_CHROOT}"/proc > /dev/null 2>&1 + + # Removing stage file + rm -f "${LIVE_ROOT}"/.stage/chroot_proc + ;; + + *) + echo "Usage: ${0} {install|remove}" + exit 1 + ;; +esac diff --git a/helpers/lh_chroot_resolv b/helpers/lh_chroot_resolv new file mode 100755 index 0000000..b6a7948 --- /dev/null +++ b/helpers/lh_chroot_resolv @@ -0,0 +1,66 @@ +#!/bin/sh + +# lh_chroot_resolv(1) - manage /etc/resolv.conf + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +case "${1}" in + install) + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/chroot_resolv + + if [ -f "${LIVE_CHROOT}"/etc/resolv.conf ] + then + # Save resolv file + cp "${LIVE_CHROOT}"/etc/resolv.conf "${LIVE_CHROOT}"/etc/resolv.conf.orig + fi + + if [ -f /etc/resolv.conf ] + then + # Copy resolv file + cp /etc/resolv.conf "${LIVE_CHROOT}"/etc/resolv.conf + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_resolv + ;; + + remove) + if [ -f "${LIVE_CHROOT}"/etc/resolv.conf.orig ] + then + # Restore resolv file + mv "${LIVE_CHROOT}"/etc/resolv.conf.orig "${LIVE_CHROOT}"/etc/resolv.conf + else + # Remove resolv file + rm -f "${LIVE_CHROOT}"/etc/resolv.conf + fi + + # Removing stage file + rm -f "${LIVE_ROOT}"/.stage/chroot_resolv + ;; + + *) + echo "Usage: ${0} {install|remove}" + exit 1 + ;; +esac diff --git a/helpers/lh_chroot_sources b/helpers/lh_chroot_sources new file mode 100755 index 0000000..8d4ddbe --- /dev/null +++ b/helpers/lh_chroot_sources @@ -0,0 +1,131 @@ +#!/bin/sh + +# lh_chroot_sources(1) - manage /etc/apt/sources.list + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Read_conffile config/bootstrap #FIXME +Read_conffile config/image +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +case "${1}" in + install) + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/chroot_sources + + # Configure custom sources.list + echo "deb ${LIVE_MIRROR} ${LIVE_DISTRIBUTION} ${LIVE_SECTIONS}" > "${LIVE_CHROOT}"/etc/apt/sources.list + + if [ "${LIVE_SOURCE}" = "enabled" ] + then + echo "deb-src ${LIVE_MIRROR} ${LIVE_DISTRIBUTION} ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list + fi + + if [ "${LIVE_SECURITY}" = "enabled" ] + then + if [ "${LIVE_DISTRIBUTION}" = "etch" ] || [ "${LIVE_DISTRIBUTION}" = "testing" ] + then + echo "deb ${LIVE_MIRROR_SECURITY} ${LIVE_DISTRIBUTION}/updates ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list + + if [ "${LIVE_SOURCE}" = "yes" ] + then + echo "deb-src ${LIVE_MIRROR_SECURITY} ${LIVE_DISTRIBUTION}/updates ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list + fi + fi + fi + + # Installing aptitude + if [ "${LH_APT}" = "apt" ] + then + Chroot "apt-get update" + elif [ "${LH_APT}" = "aptitude" ] + then + if [ ! -x "${LH_CHROOT}"/usr/bin/aptitude ] + then + Chroot "apt-get update" + Chroot "apt-get install --yes --force-yes aptitude" + fi + + Chroot "aptitude update" + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_sources + ;; + + remove) + # Configure generic indices + if [ "${LH_APT_GENERIC}" = "enabled" ] + then + # Cleaning apt list cache + rm -rf "${LIVE_CHROOT}"/var/lib/apt/lists + mkdir -p "${LIVE_CHROOT}"/var/lib/apt/lists/partial + + echo "deb ${LIVE_MIRROR_GENERIC} ${LIVE_DISTRIBUTION} ${LIVE_SECTIONS}" > "${LIVE_CHROOT}"/etc/apt/sources.list + + if [ "${LIVE_SOURCE}" = "enabled" ] + then + echo "deb-src ${LIVE_MIRROR_GENERIC} ${LIVE_DISTRIBUTION} ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list + fi + + if [ "${LIVE_SECURITY}" = "enabled" ] + then + if [ "${LIVE_DISTRIBUTION}" = "etch" ] || [ "${LIVE_DISTRIBUTION}" = "testing" ] + then + echo "deb ${LIVE_MIRROR_GENERIC_SECURITY} ${LIVE_DISTRIBUTION}/updates ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list + + if [ "${LIVE_SOURCE}" = "yes" ] + then + echo "deb-src ${LIVE_MIRROR_GENERIC_SECURITY} ${LIVE_DISTRIBUTION}/updates ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list + fi + fi + fi + + case "${LH_APT}" in + apt) + Chroot "apt-get update" + ;; + + aptitude) + Chroot "aptitude update" + ;; + esac + fi + + # Cleaning apt packages cache + rm -rf "${LIVE_CHROOT}"/var/cache/apt + mkdir -p "${LIVE_CHROOT}"/var/cache/apt/archives/partial + + # Removing old files + rm -f "${LIVE_CHROOT}"/var/lib/dpkg/available-old + rm -f "${LIVE_CHROOT}"/var/lib/dpkg/diversions-old + rm -f "${LIVE_CHROOT}"/var/lib/dpkg/statoverride-old + rm -f "${LIVE_CHROOT}"/var/lib/dpkg/status-old + + # Removing stage file + rm -f "${LIVE_ROOT}"/.stage/chroot_sources + ;; + + *) + echo "Usage: ${0} {install|remove}" + exit 1 + ;; +esac diff --git a/helpers/lh_chroot_symlinks b/helpers/lh_chroot_symlinks new file mode 100755 index 0000000..8da149f --- /dev/null +++ b/helpers/lh_chroot_symlinks @@ -0,0 +1,70 @@ +#!/bin/sh + +# lh_chroot_symlinks(1) - convert symlinks + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_symlinks + +if [ "${LIVE_SYMLINKS}" = "enabled" ] +then + if [ -f "${LIVE_CHROOT}"/usr/bin/symlinks ] + then + SYMLINKS="true" + fi + + if [ -n "${SYMLINKS}" ] + then + # Installing symlinks + case "${LH_APT}" in + apt) + Chroot "apt-get install --yes symlinks" + ;; + + aptitude) + Chroot "aptitude install --assume-yes symlinks" + ;; + esac + fi + + # Converting symlinks + Chroot "symlinks -c -r -s /" + + if [ -n "${SYMLINKS}" ] + then + # Removing symlinks + case "${LH_APT}" in + apt) + Chroot "apt-get remove --purge --yes symlinks" + ;; + + aptitude) + Chroot "aptitude purge --assume-yes symlinks" + ;; + esac + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_symlinks +fi diff --git a/helpers/lh_chroot_sysfs b/helpers/lh_chroot_sysfs new file mode 100755 index 0000000..421d993 --- /dev/null +++ b/helpers/lh_chroot_sysfs @@ -0,0 +1,58 @@ +#!/bin/sh + +# lh_chroot_sysfs(1) - mount /sys + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +case "${1}" in + install) + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/chroot_sysfs + + if [ ! -d "${LIVE_CHROOT}"/sys ] + then + # Create mountpoint + mkdir -p "${LIVE_CHROOT}"/sys + fi + + # Mounting /sys + mount sys-live -t sysfs "${LIVE_CHROOT}"/sys + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_sysfs + ;; + + remove) + # Unmounting /sys + #fuser -km "${LIVE_CHROOT}"/sys + umount "${LIVE_CHROOT}"/sys > /dev/null 2>&1 + + # Removing stage file + rm -f "${LIVE_ROOT}"/.stage/chroot_sysfs + ;; + + *) + echo "Usage: ${0} {install|remove}" + exit 1 + ;; +esac diff --git a/helpers/lh_chroot_sysvinit b/helpers/lh_chroot_sysvinit new file mode 100755 index 0000000..e4746d6 --- /dev/null +++ b/helpers/lh_chroot_sysvinit @@ -0,0 +1,50 @@ +#!/bin/sh + +# lh_chroot_sysvinit(1) - configures sysvinit + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_sysvinit + +if [ "${LIVE_SYSVINIT}" = "disabled" ] +then + # Disable all + for FILE in "${LIVE_CHROOT}"/etc/init.d/* + do + Chroot "update-rc.d -f `basename ${FILE}` remove" + done + + # Re-enable all required (taken from -f standard chroot) + for PACKAGE in casper console-common cron dpkg ifupdown initscripts kbd klogd libc6 libdevmapper1.02 libselinux1 libsepol1 login makedev module-init-tools netbase openbsd-inetd procps sudo sysklogd udev util-linux + do + if [ -f "${LIVE_CHROOT}"/var/lib/dpkg/info/${PACKAGE}.postinst ] + then + # Re-configure if existing + Chroot "/var/lib/dpkg/info/${PACKAGE}.postinst configure" + fi + done + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_sysvinit +fi diff --git a/helpers/lh_chroot_sysvrc b/helpers/lh_chroot_sysvrc new file mode 100755 index 0000000..4f4eeef --- /dev/null +++ b/helpers/lh_chroot_sysvrc @@ -0,0 +1,72 @@ +#!/bin/sh + +# lh_chroot_sysvrc(1) - manage /usr/sbin/policy-rc.d + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +case "${1}" in + install) + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/chroot_sysvrc + + if [ -f "${LIVE_CHROOT}"/usr/sbin/policy-rc.d ] + then + # Save policy-rc.d file + mv "${LIVE_CHROOT}"/usr/sbin/policy-rc.d "${LIVE_CHROOT}"/usr/sbin/policy-rc.d.orig + fi + + # Create policy-rc.d file +cat > "${LIVE_CHROOT}"/usr/sbin/policy-rc.d << EOF +#!/bin/sh + +echo +echo "Warning: invoke-rc.d policy in action. Skiping daemon starting" + +exit 101 +EOF + + chmod 0755 "${LIVE_CHROOT}"/usr/sbin/policy-rc.d + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_sysvrc + ;; + + remove) + if [ -f "${LIVE_CHROOT}"/usr/sbin/policy-rc.d.orig ] + then + # Restore policy-rc.d file + mv "${LIVE_CHROOT}"/usr/sbin/policy-rc.d.orig "${LIVE_CHROOT}"/usr/sbin/policy-rc.d + else + # Remove policy-rc.d file + rm -f "${LIVE_CHROOT}"/usr/sbin/policy-rc.d + fi + + # Removing stage file + rm -f "${LIVE_ROOT}"/.stage/chroot_sysvrc + ;; + + *) + echo "Usage: ${0} {install|remove}" + exit 1 + ;; +esac diff --git a/helpers/lh_chroot_tasks b/helpers/lh_chroot_tasks new file mode 100755 index 0000000..4959d76 --- /dev/null +++ b/helpers/lh_chroot_tasks @@ -0,0 +1,55 @@ +#!/bin/sh + +# lh_chroot_tasks(1) - install tasks into chroot + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/chroot +Set_defaults + +# Requiring stage file +Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + +# Checking stage file +Check_stagefile "${LIVE_ROOT}"/.stage/chroot_tasks + +# Checking lock file +Check_lockfile "${LIVE_ROOT}"/.lock + +# Creating lock file +Create_lockfile "${LIVE_ROOT}"/.lock + +if [ -n "${LIVE_TASKS}" ] && [ "${LH_APT}" = "aptitude" ] +then + # Restore old cache + if [ -d "${LIVE_ROOT}"/cache/chroot_tasks ] + then + cp "${LIVE_ROOT}"/cache/chroot_tasks/*.deb "${LIVE_CHROOT}"/var/cache/apt/archives + fi + + Chroot "aptitude install --assume-yes ${LIVE_TASKS}" + + # Saving new cache + Chroot "apt-get autoclean" + + if ls "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb &> /dev/null + then + if [ ! -d "${LIVE_ROOT}"/cache/chroot_tasks ] + then + mkdir -p "${LIVE_ROOT}"/cache/chroot_tasks + fi + + mv -f "${LIVE_CHROOT}"/var/cache/apt/archives/*.deb "${LIVE_ROOT}"/cache/chroot_tasks + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/chroot_tasks +fi diff --git a/helpers/lh_clean b/helpers/lh_clean new file mode 100755 index 0000000..f4c8960 --- /dev/null +++ b/helpers/lh_clean @@ -0,0 +1,71 @@ +#!/bin/sh + +# lh_clean(1) - clean up system build directories + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Ensure that a system is built as root +lh_testroot + +# Reading configuration files +Read_conffile config/common +Set_defaults + +case "${1}" in + all) + "${0}" chroot + "${0}" binary + "${0}" stage + "${0}" source + ;; + + cache) + rm -rf "${LIVE_ROOT}"/cache + ;; + + chroot) + umount -f "${LIVE_CHROOT}"/sys > /dev/null 2>&1 || true + umount -f "${LIVE_CHROOT}"/proc > /dev/null 2>&1 || true + umount -f "${LIVE_CHROOT}"/lib/init/rw > /dev/null 2>&1 || true + umount -f "${LIVE_CHROOT}"/dev/shm > /dev/null 2>&1 || true + umount -f "${LIVE_CHROOT}"/dev/pts > /dev/null 2>&1 || true + umount -f "${LIVE_CHROOT}"/dev > /dev/null 2>&1 || true + + rm -rf "${LIVE_CHROOT}" + ;; + + binary) + rm -rf "${LIVE_ROOT}"/binary + + rm -f "${LIVE_ROOT}"/binary.iso + rm -f "${LIVE_ROOT}"/binary.img + rm -f "${LIVE_ROOT}"/binary.tar.gz + + rm -f "${LIVE_ROOT}"/.stage/binary* + ;; + + stage) + rm -rf "${LIVE_ROOT}"/.stage + rm -f "${LIVE_ROOT}"/.lock + ;; + + source) + rm -rf "${LIVE_ROOT}"/source + + rm -f "${LIVE_ROOT}"/source.iso + rm -f "${LIVE_ROOT}"/source.img + rm -f "${LIVE_ROOT}"/source.tar.gz + + rm -f "${LIVE_ROOT}"/.stage/source* + ;; + + *) + "${0}" all + ;; +esac diff --git a/helpers/lh_cleanapt b/helpers/lh_cleanapt deleted file mode 100755 index ec28865..0000000 --- a/helpers/lh_cleanapt +++ /dev/null @@ -1,17 +0,0 @@ -#!/bin/sh - -# lh_cleanapt - -# Clean apt packages cache -rm -rf "${LIVE_CHROOT}"/var/cache/apt -mkdir -p "${LIVE_CHROOT}"/var/cache/apt/archives/partial - -# Clean apt list cache -rm -rf "${LIVE_CHROOT}"/var/lib/apt/lists/* -mkdir -p "${LIVE_CHROOT}"/var/lib/apt/lists/partial - -# Remove old files -rm -f "${LIVE_CHROOT}"/var/lib/dpkg/available-old -rm -f "${LIVE_CHROOT}"/var/lib/dpkg/diversions-old -rm -f "${LIVE_CHROOT}"/var/lib/dpkg/statoverride-old -rm -f "${LIVE_CHROOT}"/var/lib/dpkg/status-old diff --git a/helpers/lh_clone b/helpers/lh_clone deleted file mode 100755 index d89eba4..0000000 --- a/helpers/lh_clone +++ /dev/null @@ -1,25 +0,0 @@ -#!/bin/sh - -# lh_clone - -# Cloning existing system configuration -if [ -d "${LIVE_CLONE}" ] -then - # Swapping chroot directories - LIVE_CHROOT_TMP="${LIVE_CHROOT}" - LIVE_CHROOT="${LIVE_CLONE}" - - # Extract debconf settings - lh_chroot "aptitude install --assume-yes debconf-utils" - lh_chroot "debconf-get-selections" > "${LIVE_ROOT}"/preseed.cloned - - # Extract package selection - lh_chroot "dpkg --get-selections" | grep -v deinstall | cut -f1 > "${LIVE_ROOT}"/package-list.cloned - - # Restoring chroot directories - LIVE_CHROOT="${LIVE_CHROOT_TMP}" - LIVE_CHROOT_TMP="" - - LIVE_PRESEED="${LIVE_ROOT}/preseed.cloned" - LIVE_PACKAGE_LIST_CLONED="${LIVE_ROOT}/package-list.cloned" -fi diff --git a/helpers/lh_config b/helpers/lh_config index a664988..a9bdb98 100755 --- a/helpers/lh_config +++ b/helpers/lh_config @@ -1,26 +1,218 @@ #!/bin/sh -# lh_config - -case "${1}" in - disable-daemons) - if [ "${LIVE_DAEMONS}" = "no" ] - then - # Disable all - for FILE in "${LIVE_CHROOT}"/etc/init.d/* - do - lh_chroot "update-rc.d -f `basename ${FILE}` remove" - done - - # Re-enable all required (taken from -f standard chroot) - for PACKAGE in casper console-common cron dpkg ifupdown initscripts kbd klogd libc6 libdevmapper1.02 libselinux1 libsepol1 login makedev module-init-tools netbase openbsd-inetd procps sudo sysklogd udev util-linux - do - # Re-configure if existing - if [ -f "${LIVE_CHROOT}"/var/lib/dpkg/info/${PACKAGE}.postinst ] - then - lh_chroot "/var/lib/dpkg/info/${PACKAGE}.postinst configure" - fi - done - fi - ;; -esac +# lh_make(1) - create sample configuration for live-helper(7) + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +Set_defaults + +# Creating configuration directory +install -d -m 0755 "${LIVE_ROOT}"/config || true + +# Creating live-helper configuration +cat > "${LIVE_ROOT}"/config/common << EOF +# config/common: configuration for live-helper(7) + +# \$LH_APT: set package manager +# (Default: ${LH_APT}) +LH_APT="${LH_APT}" + +# \$LH_APT_FTPPROXY: set apt/aptitude ftp proxy +# (Default: autodetected or empty) +LH_APT_FTPPROXY="${LH_APT_FTPPROXY}" + +# \$LH_APT_HTTPPROXY: set apt/aptitude http proxy +# (Default: autodetected or empty) +LH_APT_HTTPPROXY="${LH_APT_HTTPPROXY}" + +# \$LH_APT_GENERIC: set apt/aptitude generic indices +# (Default: ${LH_APT_GENERIC}) +LH_APT_GENERIC="${LH_APT_GENERIC}" + +# \$LH_APT_PDIFFS: set apt/aptitude pdiff indices +# (Default: ${LH_APT_PDIFFS}) +LH_APT_PDIFFS="${LH_APT_PDIFFS}" + +# \$LH_APT_RECOMMENDS: enable recommends +# (Default: ${LH_APT_RECOMMENDS}) +LH_APT_RECOMMENDS="${LH_APT_RECOMMENDS}" + +# \$LH_BOOTSTRAP: select the bootstrap program +# (Default: ${LH_BOOTSTRAP}) +LH_BOOTSTRAP="${LH_BOOTSTRAP}" + +# \$LH_CACHE: enable cache +# (Default: ${LH_CACHE}) +LH_CACHE="${LH_CACHE}" + +# \$LH_DEBCONF_FRONTEND: set the debconf(1) frontend to use +# (Default: ${LH_DEBCONF_FRONTEND}) +LH_DEBCONF_FRONTEND="${LH_DEBCONF_FRONTEND}" + +# \$LH_DEBCONF_PRIORITY: set the debconf(1) priority to use +# (Default: ${LH_DEBCONF_PRIORITY}) +LH_DEBCONF_PRIORITY="${LH_DEBCONF_PRIORITY}" + +# \$LH_GENISOIMAGE: set the genisoimage program +# (Default: autodetected) +LH_GENISOIMAGE="${LH_GENISOIMAGE}" + +# \$LIVE_ROOT: set the root directory +# (Default: \`pwd\`/debian-live) +LIVE_ROOT="${LIVE_ROOT}" + +# \$LIVE_CHROOT: set the chroot directory +# (Default: \${LIVE_ROOT}/chroot) +LIVE_CHROOT="${LIVE_CHROOT}" +EOF + +# Creating lh_chroot_* configuration +cat > "${LIVE_ROOT}"/config/chroot << EOF +# config/chroot: configuration for lh_chroot_* + +# \$LIVE_KERNEL: set the kernel flavour to use +# (Default: autodetected) +LIVE_KERNEL="${LIVE_KERNEL}" + +# \$LIVE_KERNEL: set the kernel packages to use +# (Default: autodetected) +#LIVE_KERNEL_PACKAGES + +# \$LIVE_LANGUAGE: set the language to use +# (Default: empty) +LIVE_LANGUAGE="${LIVE_LANGUAGE}" + +# \$LIVE_PACKAGES: set the packages to install +# (Default: empty) +LIVE_PACKAGES="${LIVE_PACKAGES}" + +# \$LIVE_PACKAGES_LIST: set the package list to install +# (Default: ${LIVE_PACKAGES_LIST}) +LIVE_PACKAGES_LIST="${LIVE_PACKAGES_LIST}" + +# \$LIVE_TASKS: set the tasks to install +# (Default: empty) +LIVE_TASKS="${LIVE_TASKS}" + +# \$LIVE_SECURITY: enable security updates +# (Default: ${LIVE_SECURITY}) +LIVE_SECURITY="${LIVE_SECURITY}" + +# \$LIVE_SYMLINKS: enable symlink convertion +# (Default: ${LIVE_SYMLINKS}) +LIVE_SYMLINKS="${LIVE_SYMLINKS}" + +# \$LIVE_SYSVINIT: enable sysvinit +# (Default: ${LIVE_SYSVINIT}) +LIVE_SYSVINIT="${LIVE_SYSVINIT}" +EOF + +# Creating lh_chroot_* directories +install -d -m 0755 "${LIVE_ROOT}"/config/chroot_localhooks || true +install -d -m 0755 "${LIVE_ROOT}"/config/chroot_localincludes || true +install -d -m 0755 "${LIVE_ROOT}"/config/chroot_localpackages || true +install -d -m 0755 "${LIVE_ROOT}"/config/chroot_localpackageslist || true + +# Creating lh_bootstrap_* configuration +cat > "${LIVE_ROOT}"/config/bootstrap << EOF +# config/bootstrap: configuration for lh_bootstrap_* + +# \$LIVE_ARCHITECTURE: select the chroot architecture +# (Default: autodetected) +LIVE_ARCHITECTURE="${LIVE_ARCHITECTURE}" + +# \$LIVE_DISTRIBUTION: select the distribution to use +# (Default: ${LIVE_DISTRIBUTION}) +LIVE_DISTRIBUTION="${LIVE_DISTRIBUTION}" + +# \$LIVE_DISTRIBUTION_CONFIG: set distribution config directory +# (Default: empty) +LIVE_DISTRIBUTION_CONFIG="${LIVE_DISTRIBUTION_CONFIG}" + +# \$LIVE_FLAVOUR: select the flavour to use +# (Default: ${LIVE_FLAVOUR}) +LIVE_FLAVOUR="${LIVE_FLAVOUR}" + +# \$LIVE_MIRROR: set the mirror to use +# (Default: ${LIVE_MIRROR}) +LIVE_MIRROR="${LIVE_MIRROR}" + +# \$LIVE_MIRROR_SECURITY: set the security mirror to use +# (Default: ${LIVE_MIRROR_SECURITY}) +LIVE_MIRROR_SECURITY="${LIVE_MIRROR_SECURITY}" + +# \$LIVE_MIRROR_GENERIC: set the generic mirror to use +# (Default: ${LIVE_MIRROR_GENERIC}) +LIVE_MIRROR_GENERIC="${LIVE_MIRROR_GENERIC}" + +# \$LIVE_MIRROR_GENERIC_SECURITY: set the generic security mirror to use +# (Default: ${LIVE_MIRROR_GENERIC_SECURITY}) +LIVE_MIRROR_GENERIC_SECURITY="${LIVE_MIRROR_GENERIC_SECURITY}" + +# \$LIVE_SECTIONS: select the section to use +# (Default: ${LIVE_SECTIONS}) +LIVE_SECTIONS="${LIVE_SECTIONS}" +EOF + +# Creating lh_image_* configuration +cat > "${LIVE_ROOT}"/config/image << EOF +# config/chroot: configuration for lh_image_* + +# \$LIVE_BOOTAPPEND: set boot parameters +# (Default: empty) +LIVE_BOOTAPPEND="${LIVE_BOOTAPPEND}" + +# \$LIVE_ENCRYPTION: set encrytion +# (Default: empty) +LIVE_ENCRYPTION="${LIVE_ENCRYPTION}" + +# \$LIVE_FILESYSTEM: set filesystem +# (Default: ${LIVE_FILESYSTEM}) +LIVE_FILESYSTEM="${LIVE_FILESYSTEM}" + +# \$LIVE_MEMTEST86: set memtest86+ +# (Default: ${LIVE_MEMTEST86}) +LIVE_MEMTEST86="${LIVE_MEMTEST86}" + +# \$LIVE_ISO_VOLUME: set iso volume +# (Default: ${LIVE_ISO_VOLUME}) +LIVE_ISO_VOLUME="${LIVE_ISO_VOLUME}" + +# \$LIVE_SERVER_ADDRESS: set the netboot server address +# (Default: ${LIVE_SERVER_ADDRESS}) +LIVE_SERVER_ADDRESS="${LIVE_SERVER_ADDRESS}" + +# \$LIVE_SERVER_PATH: set the netboot server directory +# (Default: ${LIVE_SERVER_PATH}) +LIVE_SERVER_PATH="${LIVE_SERVER_PATH}" + +# \$LIVE_SOURCE: set source option +# (Default: ${LH_SOURCE}) +LIVE_SOURCE="${LIVE_SOURCE}" + +# \$LIVE_SYSLINUX: set syslinux option +# (Default: ${LIVE_SYSLINUX}) +LIVE_SYSLINUX="${LIVE_SYSLINUX}" + +# \$LIVE_SYSLINUX_SPLASH: set custom syslinux splash +# (Default: empty) +LIVE_SYSLINUX_SPLASH="${LIVE_SYSLINUX_SPLASH}" + +# \$LIVE_BINARY_IMAGE: set image type +# (Default: ${LIVE_BINARY_IMAGE}) +LIVE_BINARY_IMAGE="${LIVE_BINARY_IMAGE}" + +# \$LIVE_SOURCE_IMAGE: set image type +# (Default: ${LIVE_SOURCE_IMAGE}) +LIVE_SOURCE_IMAGE="${LIVE_SOURCE_IMAGE}" + +# \$LIVE_TEMPLATES: set templates +# (Default: ${LIVE_TEMPLATES}) +LIVE_TEMPLATES="${LIVE_TEMPLATES}" +EOF diff --git a/helpers/lh_configapt b/helpers/lh_configapt deleted file mode 100755 index 971d02e..0000000 --- a/helpers/lh_configapt +++ /dev/null @@ -1,56 +0,0 @@ -#!/bin/sh - -# lh_configapt.sh - -case "${1}" in - apply-proxy) - # Configure ftp proxy - if [ -n "${LIVE_PROXY_FTP}" ] - then - echo "Acquire::ftp::Proxy \"${LIVE_PROXY_FTP}\";" > "${LIVE_CHROOT}"/etc/apt/apt.conf.d/00make-live_ftp-proxy.conf - fi - - # Configure http proxy - if [ -n "${LIVE_PROXY_HTTP}" ] - then - echo "Acquire::http::Proxy \"${LIVE_PROXY_HTTP}\";" > "${LIVE_CHROOT}"/etc/apt/apt.conf.d/00make-live_http-proxy.conf - fi - ;; - - apply-recommends) - # Configure recommends - if [ ! -d "${LIVE_CHROOT}"/etc/apt/apt.conf.d ] - then - mkdir -p "${LIVE_CHROOT}"/etc/apt/apt.conf.d - fi - - if [ "${LIVE_RECOMMENDS}" = "yes" ] - then - echo "Aptitude::Recommends-Important \"true\";" >> "${LIVE_CHROOT}"/etc/apt/apt.conf - else - echo "Aptitude::Recommends-Important \"false\";" >> "${LIVE_CHROOT}"/etc/apt/apt.conf - fi - ;; - - deapply-proxy) - # Deconfigure ftp proxy - if [ -f "${LIVE_CHROOT}"/etc/apt/apt.conf.d/00make-live_ftp-proxy.conf ] - then - rm -f "${LIVE_CHROOT}"/etc/apt/apt.conf.d/00make-live_ftp-proxy.conf - fi - - # Deconfigure http proxy - if [ -f "${LIVE_CHROOT}"/etc/apt/apt.conf.d/00make-live_http-proxy.conf ] - then - rm -f "${LIVE_CHROOT}"/etc/apt/apt.conf.d/00make-live_http-proxy.conf - fi - ;; - - deapply-recommends) - # Deconfigure recommends - if [ -f "${LIVE_CHROOT}"/etc/apt/apt.conf.d/00make-live_recommends.conf ] - then - rm -f "${LIVE_CHROOT}"/etc/apt/apt.conf.d/00make-live_recommends.conf - fi - ;; -esac diff --git a/helpers/lh_confignetwork b/helpers/lh_confignetwork deleted file mode 100755 index 892020d..0000000 --- a/helpers/lh_confignetwork +++ /dev/null @@ -1,60 +0,0 @@ -#!/bin/sh - -# lh_patchnetwork.sh - -# 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-hosts) - # Save host lookup table - if [ -f "${LIVE_CHROOT}"/etc/hosts ] - then - cp "${LIVE_CHROOT}"/etc/hosts \ - "${LIVE_CHROOT}"/etc/hosts.orig - fi - - # Copy host lookup table - if [ -f /etc/hosts ] - then - cp /etc/hosts "${LIVE_CHROOT}"/etc/hosts - fi - ;; - - apply-resolv) - # 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 resolver configuration - if [ -f /etc/resolv.conf ] - then - cp /etc/resolv.conf "${LIVE_CHROOT}"/etc/resolv.conf - fi - ;; - - deapply-hosts) - # Restore host lookup table - if [ -f "${LIVE_CHROOT}"/etc/hosts.orig ] - then - mv "${LIVE_CHROOT}"/etc/hosts.orig \ - "${LIVE_CHROOT}"/etc/hosts - else - rm -f "${LIVE_CHROOT}"/etc/hosts - fi - ;; - - deapply-resolv) - # Restore resolver configuration - if [ -f "${LIVE_CHROOT}"/etc/resolv.conf.orig ] - then - mv "${LIVE_CHROOT}"/etc/resolv.conf.orig \ - "${LIVE_CHROOT}"/etc/resolv.conf - else - rm -f "${LIVE_CHROOT}"/etc/resolv.conf - fi - ;; -esac diff --git a/helpers/lh_debootstrap b/helpers/lh_debootstrap deleted file mode 100755 index fd43b16..0000000 --- a/helpers/lh_debootstrap +++ /dev/null @@ -1,25 +0,0 @@ -#!/bin/sh - -if [ ! -f "${LIVE_ROOT}"/.stage/bootstrap ] -then - # Create chroot directory - if [ ! -d "${LIVE_CHROOT}" ] - then - mkdir -p "${LIVE_CHROOT}" - fi - - if [ -n "${LIVE_BOOTSTRAP_CONFIG}" ]; - then - LIVE_DEBOOTSTRAP_SCRIPT="/usr/lib/debootstrap/scripts/${LIVE_BOOTSTRAP_CONFIG}" - fi - - debootstrap --arch="${LIVE_ARCHITECTURE}" --variant=buildd "${LIVE_DISTRIBUTION}" "${LIVE_CHROOT}" "${LIVE_MIRROR}" "${LIVE_DEBOOTSTRAP_SCRIPT}" - - # Touching stage file - if [ ! -d "${LIVE_ROOT}"/.stage ] - then - mkdir "${LIVE_ROOT}"/.stage - fi - - touch "${LIVE_ROOT}"/.stage/bootstrap -fi diff --git a/helpers/lh_depends b/helpers/lh_depends deleted file mode 100755 index 1cb1f52..0000000 --- a/helpers/lh_depends +++ /dev/null @@ -1,86 +0,0 @@ -#!/bin/sh - -# lh_depends.sh - -case "${1}" in - install) - if [ -z "${KEEP_MEMTEST86}" ] - then - if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ] - then - lh_chroot "aptitude install --assume-yes memtest86+" - fi - fi - - if [ -z "${KEEP_SYSLINUX}" ] - then - lh_chroot "aptitude install --assume-yes syslinux" - fi - - case "${2}" in - usb) - if [ -z "${KEEP_DOSFSTOOLS}" ] - then - lh_chroot "aptitude install --assume-yes dosfstools" - fi - - if [ -z "${KEEP_MTOOLS}" ] - then - lh_chroot "aptitude install --assume-yes mtools" - fi - - if [ -z "${KEEP_PARTED}" ] - then - lh_chroot "aptitude install --assume-yes parted" - fi - ;; - esac - ;; - - remove) - if [ -z "${KEEP_MEMTEST86}" ] - then - if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ] - then - lh_chroot "aptitude purge --assume-yes memtest86+" - fi - fi - - if [ -z "${KEEP_SYSLINUX}" ] - then - lh_chroot "aptitude purge --assume-yes syslinux" - fi - - case "${2}" in - usb) - if [ -z "${KEEP_DOSFSTOOLS}" ] - then - lh_chroot "aptitude purge --assume-yes dosfstools" - fi - - if [ -z "${KEEP_MEMTEST86}" ] - then - if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ] - then - lh_chroot "aptitude purge --assume-yes memtest86+" - fi - fi - - if [ -z "${KEEP_MTOOLS}" ] - then - lh_chroot "aptitude purge --assume-yes mtools" - fi - - if [ -z "${KEEP_PARTED}" ] - then - lh_chroot "aptitude purge --assume-yes parted" - fi - - if [ -z "${KEEP_SYSLINUX}" ] - then - lh_chroot "aptitude purge --assume-yes syslinux" - fi - ;; - esac - ;; -esac diff --git a/helpers/lh_genrootfs b/helpers/lh_genrootfs deleted file mode 100755 index 5853ed2..0000000 --- a/helpers/lh_genrootfs +++ /dev/null @@ -1,76 +0,0 @@ -#!/bin/sh - -# lh_genrootfs.sh - -case "${LIVE_FILESYSTEM}" in - ext2) - 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... - - if [ -z "${LIVE_ENCRYPTION}" ] - then - genext2fs --size-in-blocks=${REAL_DIM} --reserved-blocks=0 --root="${LIVE_CHROOT}" "${LIVE_ROOT}"/binary/casper/filesystem.ext2 - else - echo "Encrypting ${LIVE_ROOT}/binary/casper/filesystem.ext2 with ${LIVE_ENCRYPTION}..." - - while true - do - genext2fs --size-in-blocks=${REAL_DIM} --reserved-blocks=0 --root="${LIVE_CHROOT}" | aespipe -e "${LIVE_ENCRYPTION}" -T > "${LIVE_ROOT}"/binary/casper/filesystem.ext2 && break - - echo -n "Something went wrong... Retry? [YES/no] " - read ANSWER - - if [ 'no' = "${ANSWER}" ] - then - unset ANSWER - break - fi - done - fi - ;; - - plain) - if [ -n "${LIVE_ENCRYPTION}" ] - then - echo "Error: encryption is not supported for filesystem type 'plain'" - exit 1 - fi - - cd "${LIVE_CHROOT}" - find . | cpio -pumd "${LIVE_ROOT}"/binary/casper/filesystem.dir - cd "${OLDPWD}" - ;; - - squashfs) - if [ -f "${LIVE_ROOT}"/binary/casper/filesystem.squashfs ] - then - rm "${LIVE_ROOT}"/binary/casper/filesystem.squashfs - fi - - if [ "${LIVE_FLAVOUR}" = "minimal" ] || [ "${LIVE_FLAVOUR}" = "mini" ] - then - mksquashfs "${LIVE_CHROOT}" "${LIVE_ROOT}"/binary/casper/filesystem.squashfs -e "${LIVE_CHROOT}"/boot/vmlinuz* "${LIVE_CHROOT}"/boot/initrd.img* "${LIVE_CHROOT}"/vmlinuz "${LIVE_CHROOT}"/initrd.img "${LIVE_CHROOT}"/boot/config-* "${LIVE_CHROOT}"/boot/System.map-* - else - mksquashfs "${LIVE_CHROOT}" "${LIVE_ROOT}"/binary/casper/filesystem.squashfs - fi - - if [ -n "$LIVE_ENCRYPTION" ] - then - echo "Encrypting ${LIVE_ROOT}/binary/casper/filesystem.squashfs with ${LIVE_ENCRYPTION}..." - - while true - do - cat "${LIVE_ROOT}"/binary/casper/filesystem.squashfs | aespipe -e "${LIVE_ENCRYPTION}" -T > "${LIVE_ROOT}"/binary/casper/filesystem.squashfs.encrypted && mv "${LIVE_ROOT}"/binary/casper/filesystem.squashfs.encrypted "${LIVE_ROOT}"/binary/casper/filesystem.squashfs && break - - echo -n "Something went wrong... Retry? [YES/no] " - read ANSWER - - if [ 'no' = "${ANSWER}" ] - then - unset ANSWER - break - fi - done - fi - ;; -esac diff --git a/helpers/lh_hook b/helpers/lh_hook deleted file mode 100755 index 084a385..0000000 --- a/helpers/lh_hook +++ /dev/null @@ -1,21 +0,0 @@ -#!/bin/sh - -# lh_hook - -# Process flavour specific hooks -if [ -r "${BASE}"/hooks/"${LIVE_FLAVOUR}" ] -then - grep -v "^#" "${BASE}"/hooks/"${LIVE_FLAVOUR}" > "${LIVE_CHROOT}"/root/"${LIVE_FLAVOUR}" - LIVE_DEBCONF_FRONTEND="readline" LIVE_DEBCONF_PRIORITY="low" lh_chroot "sh /root/${LIVE_FLAVOUR}" - rm -f "${LIVE_CHROOT}"/root/"${LIVE_FLAVOUR}" -fi - -# Execute extra command in the chroot -if [ -r "${LIVE_HOOK}" ] -then - # FIXME - LIVE_DEBCONF_FRONTEND="readline" LIVE_DEBCONF_PRIORITY="low" lh_chroot "`cat ${LIVE_HOOK}`" -elif [ -n "${LIVE_HOOK}" ] -then - LIVE_DEBCONF_FRONTEND="readline" LIVE_DEBCONF_PRIORITY="low" lh_chroot "${LIVE_HOOK}" -fi diff --git a/helpers/lh_includechroot b/helpers/lh_includechroot deleted file mode 100755 index eedd31d..0000000 --- a/helpers/lh_includechroot +++ /dev/null @@ -1,11 +0,0 @@ -#!/bin/sh - -# lh_includechroot - -# Copy external directory into the chroot -if [ -d "${LIVE_INCLUDE_CHROOT}" ] -then - cd "${LIVE_INCLUDE_CHROOT}" - find . | cpio -pumd "${LIVE_CHROOT}" - cd "${OLDPWD}" -fi diff --git a/helpers/lh_installapt b/helpers/lh_installapt deleted file mode 100755 index ec19931..0000000 --- a/helpers/lh_installapt +++ /dev/null @@ -1,35 +0,0 @@ -#!/bin/sh - -# lh_installapt - -# Install aptitude -lh_chroot "apt-get install --yes --force-yes aptitude" - -# FIXME -lh_chroot "apt-key update" - -# Install secure apt -if [ "${LIVE_DISTRIBUTION}" = "unstable" ] || [ "${LIVE_DISTRIBUTION}" = "${CODENAME_UNSTABLE}" ] || \ -[ "${LIVE_DISTRIBUTION}" = "testing" ] || [ "${LIVE_DISTRIBUTION}" = "${CODENAME_TESTING}" ] -then - if [ "${LIVE_FLAVOUR}" != "minimal" ] || [ "${LIVE_FLAVOUR}" != "mini" ] - then - lh_chroot "apt-get install --yes --force-yes ${LIVE_REPOSITORY_KEYRING}" - - for NAME in ${LIVE_REPOSITORIES} - do - eval REPOSITORY_KEY="$`echo LIVE_REPOSITORY_KEY_$NAME`" - eval REPOSITORY_KEYRING="$`echo LIVE_REPOSITORY_KEYRING_$NAME`" - - if [ -n "${REPOSITORY_KEYRING}" ] - then - lh_chroot "aptitude install ${REPOSITORY_KEYRING}" - elif [ -n "${REPOSITORY_KEY}" ] - then - lh_chroot "wget ${REPOSITORY_KEY}" - lh_chroot "apt-key add `basename ${REPOSITORY_KEY}`" - lh_chroot "rm -f `basename ${REPOSITORY_KEY}`" - fi - done - fi -fi diff --git a/helpers/lh_installlinux b/helpers/lh_installlinux deleted file mode 100755 index 24dd7d1..0000000 --- a/helpers/lh_installlinux +++ /dev/null @@ -1,25 +0,0 @@ -#!/bin/sh - -# lh_installinux - -# Removing initrd backup files -rm -f "${LIVE_CHROOT}"/boot/initrd*bak* - -# Setting destination directory -case "${1}" in - iso) - DESTDIR="${LIVE_ROOT}/binary/isolinux" - ;; - - net) - DESTDIR="${LIVE_ROOT}/tftpboot" - ;; - - usb) - DESTDIR="${LIVE_ROOT}/binary" - ;; -esac - -# Installing linux image -cp "${LIVE_CHROOT}"/boot/vmlinuz* "${DESTDIR}"/vmlinuz -cp "${LIVE_CHROOT}"/boot/initrd.img* "${DESTDIR}"/initrd.gz diff --git a/helpers/lh_installmemtest86+ b/helpers/lh_installmemtest86+ deleted file mode 100755 index b35b26a..0000000 --- a/helpers/lh_installmemtest86+ +++ /dev/null @@ -1,24 +0,0 @@ -#!/bin/sh - -# lh_installmemtest86+.sh - -# Setting destination directory -case "${1}" in - iso) - DESTDIR="${LIVE_ROOT}/binary/isolinux" - ;; - - net) - DESTDIR="${LIVE_ROOT}/tftpboot" - ;; - - usb) - DESTDIR="${LIVE_ROOT}/binary" - ;; -esac - -# Installing memtest86+ -if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ] -then - cp "${LIVE_ROOT}"/chroot/boot/memtest86+.bin "${DESTDIR}"/memtest -fi diff --git a/helpers/lh_installpackagelists b/helpers/lh_installpackagelists deleted file mode 100755 index 71ba2fa..0000000 --- a/helpers/lh_installpackagelists +++ /dev/null @@ -1,29 +0,0 @@ -#!/bin/sh - -# lh_installpackagelists - -# Install packages list -if [ -n "${LIVE_PACKAGE_LIST}" ] -then - if [ "${LIVE_PACKAGE_LIST}" = "everything" ] - then - #for FILE in "${LIVE_CHROOT}"/var/lib/apt/lists/*_Packages - #do - # awk '/Package: / { print $2 }' "${FILE}" | grep -v ".*-dbg$" >> "${LIVE_CHROOT}"/root/everything - #done - - #lh_chroot "xargs --arg-file=/root/everything aptitude install --assume-yes" - #rm -f "${LIVE_CHROOT}"/root/everything - - # FIXME - - for SECTION in admin base comm devel doc editors electronics embedded games gnome graphics hamradio interpreters kde libs libdevel mail math misc net news oldlibs otherosfs perl python science shells sound tex text utils web x11 - do - lh_chroot "aptitude install --assume-yes ~s${SECTION}" - done - else - grep -v "^#" "${LIVE_PACKAGE_LIST}" > "${LIVE_CHROOT}"/root/"`basename ${LIVE_PACKAGE_LIST}`" - lh_chroot "xargs --arg-file=/root/`basename ${LIVE_PACKAGE_LIST}` aptitude install --assume-yes" - rm -f "${LIVE_CHROOT}"/root/"`basename ${LIVE_PACKAGE_LIST}`" - fi -fi diff --git a/helpers/lh_installpackages b/helpers/lh_installpackages deleted file mode 100755 index 4cce341..0000000 --- a/helpers/lh_installpackages +++ /dev/null @@ -1,9 +0,0 @@ -#!/bin/sh - -# lh_installpackages - -# Install extra packages -if [ -n "${LIVE_PACKAGES}" ] -then - lh_chroot "aptitude install --assume-yes ${LIVE_PACKAGES}" -fi diff --git a/helpers/lh_installsyslinux b/helpers/lh_installsyslinux deleted file mode 100755 index 641f7db..0000000 --- a/helpers/lh_installsyslinux +++ /dev/null @@ -1,79 +0,0 @@ -#!/bin/sh - -# lh_installsyslinux.sh - -if [ "${LIVE_ARCHITECTURE}" = "amd64" ] || [ "${LIVE_ARCHITECTURE}" = "i386" ] -then - if [ -n "${LIVE_ENCRYPTION}" ] - then - LIVE_BOOTAPPEND="${LIVE_BOOTAPPEND} encryption=${LIVE_ENCRYPTION}" - fi - - case "${1}" in - iso) - # Copy syslinux - mkdir -p "${LIVE_ROOT}"/binary/isolinux - cp "${LIVE_CHROOT}"/usr/lib/syslinux/isolinux.bin "${LIVE_ROOT}"/binary/isolinux - cp -r "${LIVE_TEMPLATES}"/syslinux/* "${LIVE_ROOT}"/binary/isolinux - - # Copy splash screen - if [ -n "${LIVE_ISOLINUX_SPLASH}" ]; then - cp "${LIVE_ISOLINUX_SPLASH}" "${LIVE_ROOT}/binary/isolinux/splash.rle" - fi - - # Configure syslinux templates - sed -i -e "s#LIVE_BOOTAPPEND#${LIVE_BOOTAPPEND}#" "${LIVE_ROOT}"/binary/isolinux/isolinux.cfg - sed -i -e "s/LIVE_DATE/`date +%Y%m%d`/" "${LIVE_ROOT}"/binary/isolinux/f1.txt - sed -i -e "s/LIVE_VERSION/${VERSION}/" "${LIVE_ROOT}"/binary/isolinux/f10.txt - - # Remove unused files - rm -f "${LIVE_ROOT}"/binary/isolinux/pxelinux.cfg - ;; - - 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 -r "${LIVE_TEMPLATES}"/syslinux/* "${LIVE_ROOT}"/tftpboot/pxelinux.cfg - mv "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/pxelinux.cfg "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/default - sed -i -e 's#splash.rle#pxelinux.cfg/splash.rle#' "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/isolinux.txt - - # Copy splash screen - if [ -n "${LIVE_ISOLINUX_SPLASH}" ]; then - cp "${LIVE_ISOLINUX_SPLASH}" "${LIVE_ROOT}/tftpboot/pxelinux.cfg/splash.rle" - fi - - # 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 - - # Remove unused files - rm -f "${LIVE_ROOT}"/tftpboot/pxelinux.cfg/isolinux.cfg - ;; - - usb) - # Copy syslinux - mkdir -p "${LIVE_ROOT}"/binary - cp "${LIVE_CHROOT}"/usr/lib/syslinux/isolinux.bin "${LIVE_ROOT}"/binary/syslinux.bin - cp -r "${LIVE_TEMPLATES}"/syslinux/* "${LIVE_ROOT}"/binary - mv "${LIVE_ROOT}"/binary/isolinux.cfg "${LIVE_ROOT}"/binary/syslinux.cfg - - # Copy splash screen - if [ -n "${LIVE_ISOLINUX_SPLASH}" ]; then - cp "${LIVE_ISOLINUX_SPLASH}" "${LIVE_ROOT}/binary/splash.rle" - fi - - # Configure syslinux templates - sed -i -e "s#LIVE_BOOTAPPEND#${LIVE_BOOTAPPEND}#" "${LIVE_ROOT}"/binary/syslinux.cfg - sed -i -e "s/LIVE_DATE/`date +%Y%m%d`/" "${LIVE_ROOT}"/binary/f1.txt - sed -i -e "s/LIVE_VERSION/${VERSION}/" "${LIVE_ROOT}"/binary/f10.txt - - # Remove unused files - rm -f "${LIVE_ROOT}"/binary/isolinux/pxelinux.cfg - ;; - esac -fi diff --git a/helpers/lh_installtasks b/helpers/lh_installtasks deleted file mode 100755 index 0a21a4a..0000000 --- a/helpers/lh_installtasks +++ /dev/null @@ -1,12 +0,0 @@ -#!/bin/sh - -# lh_installtasks - -# Install aptitude tasks -if [ -n "${LIVE_TASKS}" ] -then - for TASK in ${LIVE_TASKS} - do - lh_chroot "aptitude install --assume-yes ${TASK}" - done -fi diff --git a/helpers/lh_localdeb b/helpers/lh_localdeb deleted file mode 100755 index 0fe71aa..0000000 --- a/helpers/lh_localdeb +++ /dev/null @@ -1,10 +0,0 @@ -#!/bin/sh - -# lh_localdeb - -if [ `ls "${LIVE_ROOT}"/localdeb/*.deb` ] -then - cp "${LIVE_ROOT}"/localdeb/*.deb "${LIVE_CHROOT}"/root - lh_chroot "dpkg -i /root/*.deb" - rm -f "${LIVE_CHROOT}"/root/*.deb -fi diff --git a/helpers/lh_losetup b/helpers/lh_losetup index e2b3c0d..442afdb 100755 --- a/helpers/lh_losetup +++ b/helpers/lh_losetup @@ -2,7 +2,13 @@ # lh_losetup -DEVICE="${1}" +if [ -z "${1}" ] +then + DEVICE="`losetup -f`" +else + DEVICE="${1}" +fi + FILE="${2}" PARTITION="${3}" @@ -11,7 +17,7 @@ FDISK_OUT="`fdisk -l -u ${DEVICE} 2>&1`" losetup -d "${DEVICE}" LOOPDEVICE="`echo ${DEVICE}p${PARTITION:=1}`" -CYL="`echo ${FDISK_OUT} | sed -ne "s_^${LOOPDEVICE}[ *]*\([0-9]*\).*_\1_p" `" +CYL=`echo "$FDISK_OUT" | sed -ne "s_^$LOOPDEVICE[ *]*\([0-9]*\).*_\1_p"` #OFFSET="`expr 512 '*' ${CYL}`" OFFSET="$((CYL*512))" diff --git a/helpers/lh_manifest b/helpers/lh_manifest deleted file mode 100755 index d755335..0000000 --- a/helpers/lh_manifest +++ /dev/null @@ -1,13 +0,0 @@ -#!/bin/sh - -# lh_manifest - -# Add filesystem.manifest -lh_chroot "dpkg --get-selections" | awk '{ print $1 }' | sort -u > "${LIVE_ROOT}"/filesystem.manifest - -if [ -n "${LIVE_MANIFEST}" ] -then - # FIXME; what should that be good for anyway? - lh_chroot "aptitude install --assume-yes ${LIVE_MANIFEST}" - lh_chroot "dpkg-query -W \*" | awk '$2 ~ /./ {print $1 " " $2 }' > "${LIVE_ROOT}"/filesystem.manifest-desktop -fi diff --git a/helpers/lh_md5sums b/helpers/lh_md5sums deleted file mode 100755 index 8097e6c..0000000 --- a/helpers/lh_md5sums +++ /dev/null @@ -1,17 +0,0 @@ -#!/bin/sh - -# lh_md5sums.sh - -# Calculating md5sums -cd "${LIVE_ROOT}"/binary -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}"/binary diff --git a/helpers/lh_patchchroot b/helpers/lh_patchchroot deleted file mode 100755 index ae99997..0000000 --- a/helpers/lh_patchchroot +++ /dev/null @@ -1,18 +0,0 @@ -#!/bin/sh - -# lh_patchchroot.sh - -# Some maintainer scripts can detect if they are in a chrooted system. -# Therefore, we create the needed file. - -case "${1}" in - apply) - # Create chroot file - echo "debian-live" > "${LIVE_CHROOT}"/etc/debian_chroot - ;; - - deapply) - # Remove chroot file - rm -f "${LIVE_CHROOT}"/etc/debian_chroot - ;; -esac diff --git a/helpers/lh_patchlinux b/helpers/lh_patchlinux deleted file mode 100755 index 7193f23..0000000 --- a/helpers/lh_patchlinux +++ /dev/null @@ -1,32 +0,0 @@ -#!/bin/sh - -# lh_patchlinux.sh - -# The linux-image package asks interactively for initial ramdisk -# creation. Therefore, we preconfigure /etc/kernel-img.conf. -# FIXME: preseeding? - -case "${1}" in - apply) - # Save kernel configuration - if [ -f "${LIVE_CHROOT}"/etc/kernel-img.conf ] - then - cp "${LIVE_CHROOT}"/etc/kernel-img.conf \ - "${LIVE_CHROOT}"/etc/kernel-img.conf.old - fi - - # Configure kernel-img.conf - echo "do_initrd = Yes" >> "${LIVE_CHROOT}"/etc/kernel-img.conf - ;; - - deapply) - # Restore kernel configuration - if [ -f "${LIVE_CHROOT}"/etc/kernel-img.conf.old ] - then - mv "${LIVE_CHROOT}"/etc/kernel-img.conf.old \ - "${LIVE_CHROOT}"/etc/kernel-img.conf - else - rm -f "${LIVE_CHROOT}"/etc/kernel-img.conf - fi - ;; -esac diff --git a/helpers/lh_patchnetwork b/helpers/lh_patchnetwork deleted file mode 100755 index 9d0b4b0..0000000 --- a/helpers/lh_patchnetwork +++ /dev/null @@ -1,18 +0,0 @@ -#!/bin/sh - -# lh_patchnetwork.sh - -# 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) - lh_confignetwork apply-hosts - lh_confignetwork apply-resolv - ;; - - deapply) - lh_confignetwork deapply-hosts - lh_confignetwork deapply-resolv - ;; -esac diff --git a/helpers/lh_patchrunlevel b/helpers/lh_patchrunlevel deleted file mode 100755 index 05fa9fb..0000000 --- a/helpers/lh_patchrunlevel +++ /dev/null @@ -1,27 +0,0 @@ -#!/bin/sh - -# lh_patchrunlevel.sh - -# Disabling all init scripts with a blocking policy as in -# /usr/share/doc/sysv-rc/README.policy-rc.d.gz. - -case "${1}" in - apply) - # Create init policy - cat > "${LIVE_CHROOT}"/usr/sbin/policy-rc.d << EOF -#!/bin/sh - -echo -echo "Warning: invoke-rc.d policy in action. Skiping daemon starting" - -exit 101 -EOF - - chmod 0755 "${LIVE_CHROOT}"/usr/sbin/policy-rc.d - ;; - - deapply) - # Removing init policy - rm -f "${LIVE_CHROOT}"/usr/sbin/policy-rc.d - ;; -esac diff --git a/helpers/lh_preseed b/helpers/lh_preseed deleted file mode 100755 index bcad060..0000000 --- a/helpers/lh_preseed +++ /dev/null @@ -1,23 +0,0 @@ -#!/bin/sh - -# lh_preseed - -# Restore preseed configuration -if [ -f "${LIVE_PRESEED}" ] -then - lh_chroot "aptitude install --assume-yes debconf-utils" - cp "${LIVE_PRESEED}" "${LIVE_CHROOT}"/root/preseed - lh_chroot "debconf-set-selections /root/preseed" - rm -f "${LIVE_CHROOT}"/root/preseed -else - if [ -n "${LIVE_PRESEED}" ]; then - echo "'${LIVE_PRESEED}' file doesn't exists. Exiting..." - exit 1 - fi -fi - -# Restore cloned package selection -if [ -f "${LIVE_PACKAGE_LIST_CLONED}" ] -then - lh_chroot "xargs --arg-file=/root/`basename ${LIVE_PACKAGE_LIST_CLONED}` aptitude install --assume-yes" -fi diff --git a/helpers/lh_setupapt b/helpers/lh_setupapt deleted file mode 100755 index 37a3dbd..0000000 --- a/helpers/lh_setupapt +++ /dev/null @@ -1,124 +0,0 @@ -#!/bin/sh - -case "${1}" in - custom) - # Configure custom sources.list - case "${LIVE_DISTRIBUTION}" in - stable|"${CODENAME_STABLE}"|testing|"${CODENAME_TESTING}") - echo "deb ${LIVE_MIRROR} ${LIVE_DISTRIBUTION} ${LIVE_SECTIONS}" > "${LIVE_CHROOT}"/etc/apt/sources.list - - if [ "${LIVE_SOURCE}" = "yes" ] - then - echo "deb-src ${LIVE_MIRROR} ${LIVE_DISTRIBUTION} ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - fi - - echo "deb ${LIVE_MIRROR_SECURITY} ${LIVE_DISTRIBUTION}/updates ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - - if [ "${LIVE_SOURCE}" = "yes" ] - then - echo "deb-src ${LIVE_MIRROR_SECURITY} ${LIVE_DISTRIBUTION}/updates ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - fi - ;; - - unstable|"${CODENAME_UNSTABLE}") - echo "deb ${LIVE_MIRROR} unstable ${LIVE_SECTIONS}" > "${LIVE_CHROOT}"/etc/apt/sources.list - - if [ "${LIVE_SOURCE}" = "yes" ] - then - echo "deb-src ${LIVE_MIRROR} unstable ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - fi - - if [ "${LIVE_DISTRIBUTION_EXPERIMENTAL}" = "yes" ] - then - echo "deb ${LIVE_MIRROR} experimental ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - - if [ "${LIVE_SOURCE}" = "yes" ] - then - echo "deb-src ${LIVE_MIRROR} experimental ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - fi - -cat > "${LIVE_CHROOT}"/etc/apt/preferences << EOF -Package: * -Pin: release a=experimental -Pin-Priority: 999 -EOF - fi - ;; - esac - ;; - - default) - # Configure default sources.list - case "${LIVE_DISTRIBUTION}" in - oldstable|"${CODENAME_OLDSTABLE}"|stable|"${CODENAME_STABLE}"|testing|"${CODENAME_TESTING}") - echo "deb http://ftp.debian.org/debian/ ${LIVE_DISTRIBUTION} ${LIVE_SECTIONS}" > "${LIVE_CHROOT}"/etc/apt/sources.list - - if [ "${LIVE_SOURCE}" = "yes" ] - then - echo "deb-src http://ftp.debian.org/debian/ ${LIVE_DISTRIBUTION} ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - fi - - echo "deb http://security.debian.org/ ${LIVE_DISTRIBUTION}/updates ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - - if [ "${LIVE_SOURCE}" = "yes" ] - then - echo "deb-src http://security.debian.org/ ${LIVE_DISTRIBUTION}/updates ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - fi - ;; - - unstable|"${CODENAME_UNSTABLE}") - echo "deb http://ftp.debian.org/debian/ unstable ${LIVE_SECTIONS}" > "${LIVE_CHROOT}"/etc/apt/sources.list - - if [ "${LIVE_SOURCE}" = "yes" ] - then - echo "deb-src http://ftp.debian.org/debian/ unstable ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - fi - - if [ "${LIVE_DISTRIBUTION_EXPERIMENTAL}" = "yes" ] - then - echo "deb http://ftp.debian.org/debian/ experimental ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - - if [ "${LIVE_SOURCE}" = "yes" ] - then - echo "deb-src http://ftp.debian.org/debian/ experimental ${LIVE_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - fi - fi - ;; - esac - ;; -esac - -# Add custom repositories -echo "" >> "${LIVE_CHROOT}"/etc/apt/sources.list -echo "# Custom repositories" >> "${LIVE_CHROOT}"/etc/apt/sources.list - -for NAME in ${LIVE_REPOSITORIES} -do - eval REPOSITORY="$`echo LIVE_REPOSITORY_$NAME`" - eval REPOSITORY_DISTRIBUTION="$`echo LIVE_REPOSITORY_DISTRIBUTION_$NAME`" - eval REPOSITORY_SECTIONS="$`echo LIVE_REPOSITORY_SECTIONS_$NAME`" - - # Configure /etc/apt/sources.list - if [ -n "${REPOSITORY_DISTRIBUTION}" ] - then - echo "deb ${REPOSITORY} ${REPOSITORY_DISTRIBUTION} ${REPOSITORY_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - else - echo "deb ${REPOSITORY} ${LIVE_DISTRIBUTION} ${REPOSITORY_SECTIONS}" >> "${LIVE_CHROOT}"/etc/apt/sources.list - fi -done - -# Update indices -if [ "${2}" = "initial" ] -then - lh_chroot "apt-get update" -else - lh_chroot "aptitude update" -fi - -if [ "${LIVE_DISTRIBUTION_EXPERIMENTAL}" = "yes" ] -then - # experimental is sometimes broken, - # therefore this is intentionally kept interactive. - lh_chroot "aptitude upgrade" || return 0 - lh_chroot "aptitude dist-upgrade" || return 0 -fi diff --git a/helpers/lh_source b/helpers/lh_source new file mode 100755 index 0000000..5d08385 --- /dev/null +++ b/helpers/lh_source @@ -0,0 +1,33 @@ +#!/bin/sh + +# lh_source(1) - building the source images + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +# Enabling network in chroot +lh_chroot_hosts install +lh_chroot_resolv install +lh_chroot_sources install + +# Preparing images +lh_source_download + +# Building images +lh_source_generic +lh_source_iso +lh_source_net +lh_source_usb + +# Deconfiguring chroot +rm -f "${LIVE_ROOT}"/.stage/chroot_sources +lh_chroot_resolv remove +lh_chroot_hosts remove diff --git a/helpers/lh_source_download b/helpers/lh_source_download new file mode 100755 index 0000000..0684d87 --- /dev/null +++ b/helpers/lh_source_download @@ -0,0 +1,67 @@ +#!/bin/sh + +# lh_source_download(1) - download sources + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +if [ "${LIVE_SOURCE}" = "enabled" ] +then + # Requiring stage file + Require_stagefile "${LIVE_ROOT}"/.stage/bootstrap + + # Checking lock file + Check_lockfile "${LIVE_ROOT}"/.lock + + # Creating lock file + Create_lockfile "${LIVE_ROOT}"/.lock + + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/source_download + + # Remove old sources + if [ "${LIVE_ROOT}"/source ] + then + rm -rf "${LIVE_ROOT}"/source + fi + + # Download sources + Chroot "dpkg --get-selections" | awk '{ print $1 }' > "${LIVE_CHROOT}"/root/dpkg-selection.txt + Chroot "xargs --arg-file=/root/dpkg-selection.txt apt-get source --download-only" + rm -f "${LIVE_CHROOT}"/root/dpkg-selection.txt + + # Sort sources + for DSC in "${LIVE_CHROOT}"/*.dsc + do + SOURCE="`awk '/Source:/ { print $2; }' ${DSC}`" + + if [ "`echo ${SOURCE} | cut -b 1-3`" == "lib" ] + then + LETTER="`echo ${SOURCE} | cut -b 1-4`" + else + LETTER="`echo ${SOURCE} | cut -b 1`" + fi + + # Install directory + install -d -m 0755 "${LIVE_ROOT}"/source/"${LETTER}"/"${SOURCE}" + + # Move files + mv "${LIVE_CHROOT}"/"${SOURCE}"_* "${LIVE_ROOT}"/source/"${LETTER}"/"${SOURCE}" + done + + # Copy system configuration + cp -a "${LIVE_ROOT}"/config "${LIVE_ROOT}"/source + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/source_download +fi diff --git a/helpers/lh_source_generic b/helpers/lh_source_generic new file mode 100755 index 0000000..a4fa1cc --- /dev/null +++ b/helpers/lh_source_generic @@ -0,0 +1,53 @@ +#!/bin/sh + +# lh_source_generic(1) - build source generic image + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +if [ "${LIVE_SOURCE}" = "disabled" ] +then + echo "W: source images disabled (FIXME)" + exit 0 +fi + +for IMAGE in ${LIVE_SOURCE_IMAGE} +do + if [ "${IMAGE}" = "generic" ] + then + # Requiring stage file + Require_stagefile "${LIVE_ROOT}"/.stage/source_download + + # Checking lock file + Check_lockfile "${LIVE_ROOT}"/.lock + + # Creating lock file + Create_lockfile "${LIVE_ROOT}"/.lock + + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/source_generic + + # Remove old source + if [ -f "${LIVE_ROOT}"/source.tar ] + then + rm -f "${LIVE_ROOT}"/source.tar + fi + + # Create tarball + cd "${LIVE_ROOT}" && + tar cf source.tar source + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/source_generic + fi +done diff --git a/helpers/lh_source_iso b/helpers/lh_source_iso new file mode 100755 index 0000000..96d24ae --- /dev/null +++ b/helpers/lh_source_iso @@ -0,0 +1,53 @@ +#!/bin/sh + +# lh_source_iso(1) - build source iso image + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +if [ "${LIVE_SOURCE}" = "disabled" ] +then + echo "W: source images disabled (FIXME)" + exit 0 +fi + +for IMAGE in ${LIVE_SOURCE_IMAGE} +do + if [ "${IMAGE}" = "iso" ] + then + # Requiring stage file + Require_stagefile "${LIVE_ROOT}"/.stage/source_download + + # Checking lock file + Check_lockfile "${LIVE_ROOT}"/.lock + + # Creating lock file + Create_lockfile "${LIVE_ROOT}"/.lock + + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/source_iso + + # Remove old source + if [ -f "${LIVE_ROOT}"/source.iso ] + then + rm -f "${LIVE_ROOT}"/source.iso + fi + + # Create image + cd "${LIVE_ROOT}" && + ${LH_GENISOIMAGE} -A "Debian Live" -p "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -publisher "Debian Live; http://debian-live.alioth.debian.org/; debian-live-devel@lists.alioth.debian.org" -o source.iso -r -J -l -V "${LIVE_DISK_VOLUME}" source + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/source_iso + fi +done diff --git a/helpers/lh_source_net b/helpers/lh_source_net new file mode 100755 index 0000000..30a8b83 --- /dev/null +++ b/helpers/lh_source_net @@ -0,0 +1,53 @@ +#!/bin/sh + +# lh_source_net(1) - build source net image + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/image +Set_defaults + +if [ "${LIVE_SOURCE}" = "disabled" ] +then + echo "W: source images disabled (FIXME)" + exit 0 +fi + +for IMAGE in ${LIVE_SOURCE_IMAGE} +do + if [ "${IMAGE}" = "net" ] + then + # Requiring stage file + Require_stagefile "${LIVE_ROOT}"/.stage/source_download + + # Checking lock file + Check_lockfile "${LIVE_ROOT}"/.lock + + # Creating lock file + Create_lockfile "${LIVE_ROOT}"/.lock + + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/source_net + + # Remove old source + if [ -f "${LIVE_ROOT}"/source.tar.gz ] + then + rm -f "${LIVE_ROOT}"/source.tar.gz + fi + + # Create tarball + cd "${LIVE_ROOT}" && + tar cfz source.tar.gz source + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/source_net + fi +done diff --git a/helpers/lh_source_usb b/helpers/lh_source_usb new file mode 100755 index 0000000..03e90d7 --- /dev/null +++ b/helpers/lh_source_usb @@ -0,0 +1,121 @@ +#!/bin/sh + +# lh_source_usb(1) - build source image + +set -e + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +# Reading configuration files +Read_conffile config/common +Read_conffile config/bootstrap +Read_conffile config/image +Set_defaults + +if [ "${LIVE_SOURCE}" = "disabled" ] +then + echo "W: source images disabled (FIXME)" + exit 0 +fi + +for IMAGE in ${LIVE_SOURCE_IMAGE} +do + if [ "${IMAGE}" = "usb" ] + then + # Requiring stage file + Require_stagefile "${LIVE_ROOT}"/.stage/source_download + + # Checking lock file + Check_lockfile "${LIVE_ROOT}"/.lock + + # Creating lock file + Create_lockfile "${LIVE_ROOT}"/.lock + + # Checking stage file + Check_stagefile "${LIVE_ROOT}"/.stage/source_usb + + if [ ! -f "${LIVE_CHROOT}"/sbin/mkdosfs ] + then + PACKAGES="${PACKAGES} dosfstools" + fi + + if [ ! -f "${LIVE_CHROOT}"/sbin/parted ] + then + PACKAGES="${PACKAGES} parted" + fi + + if [ -n "${PACKAGES}" ] + then + # Installing packages + case "${LH_APT}" in + apt) + Chroot "apt-get install --yes ${PACKAGES}" + ;; + + aptitude) + Chroot "aptitude install --assume-yes ${PACKAGES}" + ;; + esac + fi + + # Remove old source + if [ -f "${LIVE_ROOT}"/source.img ] + then + rm -f "${LIVE_ROOT}"/source.img + fi + + # Everything which comes here needs to be cleaned up, + DU_DIM="`du -ms ${LIVE_ROOT}/source | cut -f1`" + REAL_DIM="`expr ${DU_DIM} + ${DU_DIM} / 20`" # Just 5% more to be sure, need something more sophistcated here... + dd if=/dev/zero of="${LIVE_ROOT}"/source.img bs=1024k count=${REAL_DIM} + FREELO="`losetup -f`" + if [ ! -b "${LIVE_CHROOT}"/${FREELO} ] + then + MAKEDEV="true" + Chroot "cd /dev && ./MAKEDEV ${FREELO}" + fi + + echo "!!! The following error/warning messages can be ignored !!!" + lh_losetup $FREELO "${LIVE_ROOT}"/source.img 0 + Chroot "parted -s ${FREELO} mklabel msdos" || true + Chroot "parted -s ${FREELO} mkpartfs primary fat16 0.0 100%" || true + Chroot "parted -s ${FREELO} set 1 lba off" || true + losetup -d ${FREELO} + + lh_losetup $FREELO "${LIVE_ROOT}"/source.img 1 + Chroot "mkfs.msdos -n DEBIAN_LIVE ${FREELO}" + mkdir -p "${LIVE_ROOT}"/source.tmp + mount ${FREELO} "${LIVE_ROOT}"/source.tmp + cp -r "${LIVE_ROOT}"/source/* "${LIVE_ROOT}"/source.tmp + umount "${LIVE_ROOT}"/source.tmp + rmdir "${LIVE_ROOT}"/source.tmp + losetup -d ${FREELO} + echo "!!! The above error/warning messages can be ignored !!!" + + if [ -n "${MAKEDEV}" ] + then + rm -f "${LIVE_CHROOT}"/${FREELO} + fi + + if [ -n "${PACKAGES}" ] + then + # Removing packages + case "${LH_APT}" in + apt) + Chroot "apt-get remove --purge --yes ${PACKAGES}" + ;; + + aptitude) + Chroot "aptitude purge --assume-yes ${PACKAGES}" + ;; + esac + fi + + # Creating stage file + Create_stagefile "${LIVE_ROOT}"/.stage/source_usb + fi +done diff --git a/helpers/lh_testroot b/helpers/lh_testroot index 6725850..e213ec5 100755 --- a/helpers/lh_testroot +++ b/helpers/lh_testroot @@ -1,6 +1,8 @@ #!/bin/sh -# lh_testroot.sh +# lh_testroot(1) - ensure that a system is built as root + +set -e # Checking user account if [ "`id -u`" -ne "0" ] diff --git a/helpers/make-live b/helpers/make-live new file mode 100755 index 0000000..8ae82ae --- /dev/null +++ b/helpers/make-live @@ -0,0 +1,324 @@ +#!/bin/sh + +set -e + +# Set static variables +PROGRAM="`basename ${0}`" + +# Source common functions +for FUNCTION in /usr/share/live-helper/functions/*.sh +do + . ${FUNCTION} +done + +USAGE="Usage: ${PROGRAM} build|config [--apt apt|aptitude] [--apt-ftpproxy URL] [--apt-httpproxy URL] [--apt-generic enabled|disabled] [--apt-pdiffs enabled|disabled] [--apt-recommends enabled|disabled] [--bootstrap cdebootstrap|deboostrap] [--cache enabled|disabled] [--debconf-frontend dialog|readline|noninteractive] [--debconf-priority low|medium|high|critical] [--genisoimage genisoimage|mkisofs] [--root DIRECTORY] [--chroot DIRECTORY] [-a|--architecture ARCHITECTURE] [-d|--distribution testing|unstable|etch|sid] [--distribution-config DIRECTORY] [-f|--flavour minimal|standard] [-m|--mirror URL] [--mirror-security URL] [--mirror-generic URL] [--mirror-generic-security URL] [--sections SECTION|\"SECTIONS\"] [-k|--kernel KERNEL] [--kernel-packages PACKAGES] [-l|--language LANGUAGE] [--packages PACKAGE|\"PACKAGES\"] [-p|--packages-list LIST] [--tasks TASK|\"TASKS\"] [--security enabled|disabled] [--symlinks enabled|disabled] [--sysvinit enabled|disabled] [--bootappend KERNEL_PARAMETER|\"KERNEL_PARAMETERS\"] [-e|--encryption ALGORITHM] [--filesystem ext2|plain|squashfs] [--memtest86 enabled|disabled] [--iso-volume STRING] [--server-address HOSTNAME|IP] [--server-path DIRECTORY] [--source enabled|disabled] [--syslinux enabled|disabled] [--syslinux-splash FILE] [-b|--binary-image iso|usb|net] [-s|--source-image generic|iso|usb|net] [--templates DIRECTORY]" + +Help () +{ + echo "${PROGRAM} - utility to build Debian Live systems" + echo + echo "${USAGE}" + echo "Usage: ${PROGRAM} [-h|--help]" + echo "Usage: ${PROGRAM} [-u|--usage]" + echo "Usage: ${PROGRAM} [-v|--version]" + echo + echo "Lists: gnome, gnome-core, gnome-desktop, gnome-full, gnome-junior, gnustep, kde, kde-core, kde-desktop, kde-extra, kde-full, kde-junior, mini, minimal, minimal-net, rescue, standard, standard-x11, xfce, xfce-desktop, xfce-junior" + echo + echo "Report bugs to Debian Live project ." + exit 0 +} + +Usage () +{ + echo "${PROGRAM} - utility to build Debian Live systems" + echo + echo "${USAGE}" + echo "Usage: ${PROGRAM} [-h|--help]" + echo "Usage: ${PROGRAM} [-u|--usage]" + echo "Usage: ${PROGRAM} [-v|--version]" + echo + echo "Try \"${PROGRAM} --help\" for more information." + exit ${1} +} + +Version () +{ + echo "${PROGRAM}, version ${VERSION}" + echo + echo "Copyright (C) 2006-2007 Daniel Baumann " + echo "Copyright (C) 2006-2007 Marco Amadori " + 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 "You should have received a copy of the GNU General Public License" + echo "along with this program; if not, write to the Free Software" + echo "Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA" + echo + echo "On Debian systems, the complete text of the GNU General Public License" + echo "can be found in /usr/share/common-licenses/GPL file." + echo + echo "Homepage: " + exit 0 +} + +Main () +{ + ARGUMENTS="`getopt --longoptions build,config,apt:,apt-ftpproxy:,apt-httpprox:,apt-generic:,apt-pdiffs:,apt-recommends:,bootstrap:,cache:,debconf-frontend:,debconf-priority:,genisoimage:,root:,chroot:,architecture:,distribution:,distribution-config:,flavour:,mirror:,mirror-security:,mirror-generic:,mirror-generic-security:,sections:,kernel:,kernel-packages:,language:,packages:,packages-list:,tasks:,security:,symlinks:,sysvinit:,bootappend:,encryption:,filesystem:,memtest86:,iso-volume:,server-address:,server-path:,source:,syslinux:,syslinux-splash:,binary-image:,binary-source:,templates:,help,usage,version --name=${PROGRAM} --options a:d:f:m:k:l:p:e:b:s:huv --shell sh -- "${@}"`" + + if [ "${?}" != "0" ] + then + echo "Terminating." >&2 + exit 1 + fi + + case "${1}" in + config) + CONFIG="true" + ;; + + build) + BUILD="true" + ;; + + *) + echo "E: no operation (config|build) specified." + exit 1 + ;; + esac + + eval set -- "${ARGUMENTS}" + + while true + do + case "${1}" in + # common + --apt) + LH_APT="${2}"; shift 2 + ;; + + --apt-ftpproxy) + LH_APT_FTPPROXY="${2}"; shift 2 + ;; + + --apt-httpproxy) + LH_APT_HTTPPROXY="${2}"; shift 2 + ;; + + --apt-generic) + LH_APT_GENERIC="${2}"; shift 2 + ;; + + --apt-pdiffs) + LH_APT_PDIFFS="${2}"; shift 2 + ;; + + --apt-recommends) + LH_APT_RECOMMENDS="${2}"; shift 2 + ;; + + --bootstrap) + LH_BOOTSTRAP="${2}"; shift 2 + ;; + + --cache) + LH_CACHE="${2}"; shift 2 + ;; + + --debconf-frontend) + LH_DEBCONF_FRONTEND="${2}"; shift 2 + ;; + + --debconf-priority) + LH_DEBCONF_PRIORITY="${2}"; shift 2 + ;; + + --genisoimage) + LH_GENISOIMAGE="${2}"; shift 2 + ;; + + --root) + LIVE_ROOT="${2}"; shift 2 + ;; + + --chroot) + LIVE_CHROOT="${2}"; shift 2 + ;; + + # bootstrap + -a|--architecture) + LIVE_ARCHITECTURE="${2}"; shift 2 + ;; + + -d|--distribution) + LIVE_DISTRIBUTION="${2}"; shift 2 + export LIVE_DISTRIBUTION + ;; + + --distribution-config) + LIVE_DISTRIBUTION_CONFIG="${2}"; shift 2 + ;; + + -f|--flavour) + LIVE_FLAVOUR="${2}"; shift 2 + ;; + + -m|--mirror) + LIVE_MIRROR="${2}"; shift 2 + ;; + + --mirror-security) + LIVE_MIRROR_SECURITY="${2}"; shift 2 + ;; + + --mirror-generic) + LIVE_MIRROR_GENERIC="${2}"; shift 2 + ;; + + --mirror-generic-security) + LIVE_MIRROR_GENERIC_SECURITY="${2}"; shift 2 + ;; + + --sections) + LIVE_SECTIONS="${2}"; shift 2 + ;; + + # chroot + -k|--kernel) + LIVE_KERNEL="${2}"; shift 2 + ;; + + --kernel-packages) + LIVE_KERNEL_PACKAGES="${2}"; shift 2 + ;; + + -l|--language) + LIVE_LANGUAGE="${2}"; shift 2 + ;; + + --packages) + LIVE_PACKAGES="${2}"; shift 2 + ;; + + -p|--packages-list) + LIVE_PACKAGES_LIST="${2}"; shift 2 + ;; + + --tasks) + LIVE_TASKS="${2}"; shift 2 + ;; + + --security) + LIVE_SECURITY="${2}"; shift 2 + ;; + + --symlinks) + LIVE_SYMLINKS="${2}"; shift 2 + ;; + + --sysvinit) + LIVE_SYSVINIT="${2}"; shift 2 + ;; + + # image + --bootappend) + LIVE_BOOTAPPEND="${2}"; shift 2 + ;; + + -e|--encryption) + LIVE_ENCRYPTION="${2}"; shift 2 + ;; + + --filesystem) + LIVE_FILESYSTEM="${2}"; shift 2 + ;; + + --memtest86) + LIVE_MEMTEST86="${2}"; shift 2 + ;; + + --iso-volume) + LIVE_ISO_VOLUME="${2}"; shift 2 + ;; + + --server-address) + LIVE_SERVER_ADDRESS="${2}"; shift 2 + ;; + + --server-path) + LIVE_SERVER_PATH="${2}"; shift 2 + ;; + + --source) + LIVE_SOURCE="${2}"; shift 2 + ;; + + --syslinux) + LIVE_SYSLINUX="${2}"; shift 2 + ;; + + --syslinux-splash) + LIVE_SYSLINUX_SPLASH="${2}"; shift 2 + ;; + + -b|--binary-image) + LIVE_BINARY_IMAGE="${2}"; shift 2 + ;; + + -s|--source-image) + LIVE_SOURCE_IMAGE="${2}"; shift 2 + ;; + + --templates) + LIVE_TEMPLATES="${2}"; shift 2 + ;; + + # other + -h|--help) + Help; shift + ;; + + -u|--usage) + Usage 0; shift + ;; + + -v|--version) + Version; shift + ;; + + --) + shift; break + ;; + + *) + echo "Internal error." + exit 1 + ;; + esac + done + + # Initializing + lh_testroot + Set_defaults + + # Configuring (this is really shit!) + if [ "${CONFIG}" = "true" ] + then + LH_APT="${LH_APT}" LH_APT_FTPPROXY="${LH_APT_FTPPROXY}" LH_APT_HTTPPROXY="${LH_APT_HTTPPROXY}" LH_APT_GENERIC="${LH_APT_GENERIC}" LH_APT_PDIFFS="${LH_APT_PDIFFS}" LH_APT_RECOMMENDS="${LH_APT_RECOMMENDS}" LH_BOOTSTRAP="${LH_BOOTSTRAP}" LH_CACHE="${LH_CACHE}" LH_DEBCONF_FRONTEND="${LH_DEBCONF_FRONTEND}" LH_DEBCONF_PRIORITY="${LH_DEBCONF_PRIORITY}" LH_GENISOIMAGE="${LH_GENISOIMAGE}" LIVE_ROOT="${LIVE_ROOT}" LIVE_CHROOT="${LIVE_CHROOT}" LIVE_ARCHITECTURE="${LIVE_ARCHITECTURE}" LIVE_DISTRIBUTION="${LIVE_DISTRIBUTION}" LIVE_DISTRIBUTION_CONFIG="${LIVE_DISTRIBUTION_CONFIG}" LIVE_FLAVOUR="${LIVE_FLAVOUR}" LIVE_MIRROR="${LIVE_MIRROR}" LIVE_MIRROR_SECURITY="${LIVE_MIRROR_SECURITY}" LIVE_MIRROR_GENERIC="${LIVE_MIRROR_GENERIC}" LIVE_MIRROR_GENERIC_SECURITY="${LIVE_MIRROR_GENERIC_SECURITY}" LIVE_SECTIONS="${LIVE_SECTIONS}" LIVE_KERNEL="${LIVE_KERNEL}" LIVE_KERNEL_PACKAGES="${LIVE_KERNEL_PACKAGES}" LIVE_LANGUAGE="${LIVE_LANGUAGE}" LIVE_PACKAGES="${LIVE_PACKAGES}" LIVE_PACKAGES_LIST="${LIVE_PACKAGES_LIST}" LIVE_TASKS="${LIVE_TASKS}" LIVE_SECURITY="${LIVE_SECURITY}" LIVE_SYMLINKS="${LIVE_SYMLINKS}" LIVE_SYSVINIT="${LIVE_SYSVINIT}" LIVE_BOOTAPPEND="${LIVE_BOOTAPPEND}" LIVE_ENCRYPTION="${LIVE_ENCRYPTION}" LIVE_FILESYSTEM="${LIVE_FILESYSTEM}" LIVE_MEMTEST86="${LIVE_MEMTEST86}" LIVE_ISO_VOLUME="${LIVE_ISO_VOLUME}" LIVE_SERVER_ADDRESS="${LIVE_SERVER_ADDRESS}" LIVE_SERVER_PATH="${LIVE_SERVER_PATH}" LIVE_SOURCE="${LIVE_SOURCE}" LIVE_SYSLINUX="${LIVE_SYSLINUX}" LIVE_SYSLINUX_SPLASH="${LIVE_SYSLINUX_SPLASH}" LIVE_BINARY_IMAGE="${LIVE_BINARY_IMAGE}" LIVE_SOURCE_IMAGE="${LIVE_SOURCE_IMAGE}" LIVE_TEMPLATES="${LIVE_TEMPLATES}" lh_config + fi + + # Building + if [ "${BUILD}" = "true" ] + then + cd "${LIVE_ROOT}" && lh_build + fi +} + +Main "${@}" diff --git a/helpers/overview.txt b/helpers/overview.txt deleted file mode 100644 index f84421f..0000000 --- a/helpers/overview.txt +++ /dev/null @@ -1,51 +0,0 @@ -Overview -======== - -The basic concept is threefold: - - 1. Create a chroot - 2. Install additional packages - 3. Create images - -In detail: - -We start make-live, which handels configuration file, commandline paramters and defaults. Then, we start the helpers: - - * lh_testroot - - Tests if we are root, and fails if not. - - * lh_cdebootstrap - - Creates a bootstrap with cdebootstrap. - - * Configure chroot - * Configure policy-id - * Configure network - * Mount proc - * Configure sources.list - * Configure apt: proxy and recommends - * install aptitude - * install secure apt - * aptitude update - * Configure linux-image - * Install linux-image squashfs/unionfs - * Deconfigure linux-image - * CLONING/PRESEEDING - * Install tasks lists - * Install packages lists - * Install LIVE_PACKAGES - * Copy INCLUDE_ROOT - * Process hooks - * Save packages list - * Disable daemons - * Add manifest - * Clean apt cache - * Binfmt hack - * Unmount proc - * Deconfigure network - * Deconfigure chroot - * Check the chroot for depends - - build binary - build source diff --git a/hooks/mini b/hooks/mini new file mode 100644 index 0000000..a8cc33a --- /dev/null +++ b/hooks/mini @@ -0,0 +1,27 @@ +# /usr/share/live-helper/hooks/mini - hook list for live-helper(7) + +# Removing unused packages +apt-get remove --purge apt-utils aptitude libdb4.4 +apt-get remove --purge man-db manpages info +apt-get remove --purge ssl wget + +# Removing unused files +rm -rf /usr/include/* +#rm -rf /usr/share/groff/* +rm -rf /usr/share/doc/* +rm -rf /usr/share/locale/* +rm -rf /usr/share/man/* +rm -rf /usr/share/i18n/* +rm -rf /usr/share/info/* +rm -rf /usr/share/zoneinfo/* +rm -rf /var/cache/man/* + +# Cleaning apt +rm -rf /var/lib/apt/lists +mkdir -p /var/lib/apt/lists/partial + +# Truncating logs +for FILE in `find /var/log/ -type f` +do + cat < /dev/null > $FILE +done diff --git a/hooks/minimal b/hooks/minimal new file mode 100644 index 0000000..9eb24f7 --- /dev/null +++ b/hooks/minimal @@ -0,0 +1,19 @@ +# /usr/share/live-helper/hooks/minimal - hook list for live-helper(7) + +# Removing unused packages +apt-get remove --purge apt-utils aptitude libdb4.4 +apt-get remove --purge man-db manpages info +apt-get remove --purge ssl wget + +# Removing unused files +rm -rf /var/cache/man/* + +# Cleaning apt +rm -rf /var/lib/apt/lists +mkdir -p /var/lib/apt/lists/partial + +# Truncating logs +for FILE in `find /var/log/ -type f` +do + cat < /dev/null > $FILE +done diff --git a/includes/common/README.html b/includes/common/README.html new file mode 100644 index 0000000..33565f3 --- /dev/null +++ b/includes/common/README.html @@ -0,0 +1,660 @@ + + + + + Debian GNU/Linux -- The Universal Operating System + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Debian +
+ + + + + + + + + + + + + + + + + + +
+ + + + + +
+
   + + + + Debian GNU/Linux testing "Etch" - Official Snapshot i386 Binary-1 CD +   
+
+ +		 + +
+ + + +
+ + + + + +
+ + + + + + + + + + + + + + + + + + +
+ + +
   + + + + +

Debian home page

+ + + 
+

+ + + + + + + + + + + + + +Intro +

+ + + + + +About This CD +

+ + + + + +Installing +

+ + + + + + +Last-Minute Notes +

+ + + + + + + + Using CDs with apt +

+ + + + + + + +CD Manufacturers +

+ + + + + + +More Information + +

+ + + 

+Browse this CD-ROM

+

+                +

+ + + + + + + + + + + + 		     + +
+ +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 + + + +for more information. +

+ + + + + + +Read more... + + + + + + +

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

+ +

+ + + + + + + + + +

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

+ +

+ +

+ +

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

+ + +Last Modified: Sat Mar 20 12:30:45 EST 2004 + +
 +

+ +
+ + +
+ + + diff --git a/includes/common/README.mirrors.html b/includes/common/README.mirrors.html new file mode 100644 index 0000000..b16637b --- /dev/null +++ b/includes/common/README.mirrors.html @@ -0,0 +1,746 @@ + + + + Debian worldwide mirror sites + + + +

Debian worldwide mirror sites

+

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

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

+ A primary mirror site has good bandwidth, is available 24 hours a day, + and has an easy to remember name of the form ftp.<country>.debian.org. +
+ 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

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CountrySiteDebian archiveArchitectures
Austriaftp.at.debian.org/debian/alpha arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Australiaftp.au.debian.org/debian/all
Australiaftp.wa.au.debian.org/debian/all
Bulgariaftp.bg.debian.org/debian/!hppa !hurd-i386 !s390
Brazilftp.br.debian.org/debian/all
Switzerlandftp.ch.debian.org/debian/all
Chileftp.cl.debian.org/debian/all
Czech Republicftp.cz.debian.org/debian/all
Germanyftp.de.debian.org/debian/all
Germanyftp2.de.debian.org/debian/all
Estoniaftp.ee.debian.org/debian/all
Spainftp.es.debian.org/debian/all
Finlandftp.fi.debian.org/debian/all
Franceftp.fr.debian.org/debian/all
Franceftp2.fr.debian.org/debian/all
Great Britainftp.uk.debian.org/debian/all
Hong Kongftp.hk.debian.org/debian/all
Croatiaftp.hr.debian.org/debian/all
Hungaryftp.hu.debian.org/debian/all
Irelandftp.ie.debian.org/debian/all
Icelandftp.is.debian.org/debian/all
Italyftp.it.debian.org/debian/all
Japanftp.jp.debian.org/debian/all
Japanftp2.jp.debian.org/debian/all
Koreaftp.kr.debian.org/debian/all
Netherlandsftp.nl.debian.org/debian/all
Norwayftp.no.debian.org/debian/!m68k
New Zealandftp.nz.debian.org/debian/all
Polandftp.pl.debian.org/debian/all
Romaniaftp.ro.debian.org/debian/all
Russiaftp.ru.debian.org/debian/all
Swedenftp.se.debian.org/debian/all
Sloveniaftp.si.debian.org/debian/alpha i386 ia64 m68k sparc
Slovakiaftp.sk.debian.org/debian/all
Turkeyftp.tr.debian.org/debian/all
United Statesftp.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 2006Number of sites listed: 330
+ + diff --git a/includes/common/README.mirrors.txt b/includes/common/README.mirrors.txt new file mode 100644 index 0000000..286f181 --- /dev/null +++ b/includes/common/README.mirrors.txt @@ -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..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 diff --git a/includes/common/README.txt b/includes/common/README.txt new file mode 100644 index 0000000..b847f71 --- /dev/null +++ b/includes/common/README.txt @@ -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 diff --git a/includes/common/doc/00-INDEX b/includes/common/doc/00-INDEX new file mode 100644 index 0000000..041eaca --- /dev/null +++ b/includes/common/doc/00-INDEX @@ -0,0 +1,22 @@ +What's in /debian/doc? + +--- General Documentation +FAQ/ Debian FAQ List in html, postscript, and plain text +constitution.txt Debian Constitution +debian-manifesto How it all started... +mailing-lists.txt How to subscribe to the Debian mailing lists +social-contract.txt Debian Social Contract and Free Software Guidelines +source-unpack.txt How to unpack a Debian source package +debian-keyring.tar.gz PGP keys of all the developers. + + +--- The Bug Tracking System for users +bug-reporting.txt How to report a bug in Debian +bug-log-mailserver.txt Introduction to the bug system request server +bug-log-access.txt Accessing bug reports in the tracking system +bug-mailserver-refcard.txt Mail server's reference card + + +--- Debian Developer's Information +bug-maint-info.txt Developer's information re the bug system +bug-maint-mailcontrol.txt Introduction to the bug control mailserver diff --git a/includes/common/doc/FAQ/debian-faq.en.html.tar.gz b/includes/common/doc/FAQ/debian-faq.en.html.tar.gz new file mode 100644 index 0000000..d85f3d0 Binary files /dev/null and b/includes/common/doc/FAQ/debian-faq.en.html.tar.gz differ diff --git a/includes/common/doc/FAQ/debian-faq.en.pdf.gz b/includes/common/doc/FAQ/debian-faq.en.pdf.gz new file mode 100644 index 0000000..c8aa37b Binary files /dev/null and b/includes/common/doc/FAQ/debian-faq.en.pdf.gz differ diff --git a/includes/common/doc/FAQ/debian-faq.en.ps.gz b/includes/common/doc/FAQ/debian-faq.en.ps.gz new file mode 100644 index 0000000..86aa67f Binary files /dev/null and b/includes/common/doc/FAQ/debian-faq.en.ps.gz differ diff --git a/includes/common/doc/FAQ/debian-faq.en.txt.gz b/includes/common/doc/FAQ/debian-faq.en.txt.gz new file mode 100644 index 0000000..ecb1b1a Binary files /dev/null and b/includes/common/doc/FAQ/debian-faq.en.txt.gz differ diff --git a/includes/common/doc/FAQ/html/ch-basic_defs.en.html b/includes/common/doc/FAQ/html/ch-basic_defs.en.html new file mode 100644 index 0000000..7425706 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-basic_defs.en.html @@ -0,0 +1,431 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Definitions and overview + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

1.1 What is this FAQ?

+ +

+This document gives frequently asked questions (with their answers!) about the +Debian distribution (Debian GNU/Linux and others) and about the Debian project. +If applicable, pointers to other documentation will be given: we won't quote +large parts of external documentation in this document. You'll find out that +some answers assume some knowledge of Unix-like operating systems. We'll try +to assume as little prior knowledge as possible: answers to general beginners +questions will be kept simple. +

+ +

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

+ +
+ +

1.2 What is Debian GNU/Linux?

+ +

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

+ +

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

+ +

+Debian GNU/Linux is the result of a volunteer effort to create a free, +high-quality Unix-compatible operating system, complete with a suite of +applications. The idea of a free Unix-like system originates from the GNU +project, and many of the applications that make Debian GNU/Linux so useful were +developed by the GNU project. +

+ +

+For Debian, free has the GNUish meaning (see the Debian Free Software +Guidelines). When we speak of free software, we are referring to +freedom, not price. Free software means that you have the freedom to +distribute copies of free software, that you receive source code or can get it +if you want it, that you can change the software or use pieces of it in new +free programs; and that you know you can do these things. +

+ +

+The Debian Project was created by Ian Murdock in 1993, initially under the +sponsorship of the Free Software Foundation's GNU project. Today, Debian's +developers think of it as a direct descendent of the GNU project. +

+ +

+Debian GNU/Linux is: +

+
    +
  • +

    +full featured: 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 mirror sites. +

    +
    • +
+
    +
  • +

    +free to use and redistribute: 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. +

    + +

    +The Debian FTP archives also carry approximately 450 software packages (in the +non-free and contrib sections), which are +distributable under specific terms included with each package. +

    +
    • +
+
    +
  • +

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

    +
    • +
+ +

+Although Debian GNU/Linux itself is free software, it is a base upon which +value-added Linux distributions can be built. By providing a reliable, +full-featured base system, Debian provides Linux users with increased +compatibility, and allows Linux distribution creators to eliminate duplication +of effort and focus on the things that make their distribution special. See I am making a special Linux +distribution for a "vertical market". Can I use Debian GNU/Linux for +the guts of a Linux system and add my own applications on top of it?, Section +13.3 for more information. +

+ +
+ +

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

+ +

+In short, Linux is the kernel of a Unix-like operating system. It was +originally designed for 386 (and better) PCs; today Linux also runs on a dozen +of other systems. Linux is written by Linus Torvalds and many computer +scientists around the world. +

+ +

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

+ +
    +
  • +

    +a wide range of Unix utilities, many of which have been developed by the GNU +project and the Free Software Foundation. +

    +
    • +
+ +

+The combination of the Linux kernel, the file system, the GNU and FSF +utilities, and the other utilities are designed to achieve compliance with the +POSIX (IEEE 1003.1) standard; see How +source code compatible is Debian with other Unix systems?, Section 3.3. +

+ +

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

+ +
+ +

1.4 Does Debian just do GNU/Linux?

+ +

+Currently, Debian is only available for Linux, but with Debian GNU/Hurd and +Debian on BSD kernels, we have started to offer non-Linux-based OSes as a +development, server and desktop platform, too. However, these non-linux ports +are not officially released yet. +

+ +

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

+ +

+The Hurd is a set of servers running on top of the GNU Mach microkernel. +Together they build the base for the GNU operating system. +

+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +

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

+
+
Freedom:
+
+

+As stated in the Debian +Social Contract, Debian will remain 100% free. Debian is very +strict about shipping truly free software. The guidelines used to determine if +a work is "free" are provided in The Debian Free +Software. +

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

+The entire system, or any individual component of it, can be upgraded in place +without reformatting, without losing custom configuration files, and (in most +cases) without rebooting the system. Most Linux distributions available today +have some kind of package maintenance system; the Debian package maintenance +system is unique and particularly robust (see Basics of the Debian package management system, +Chapter 6). +

+
+
+
+
Open development:
+
+

+Whereas other Linux distributions are developed by individuals, small, closed +groups, or commercial vendors, Debian is the only major Linux distribution that +is being developed cooperatively by many individuals through the Internet, in +the same spirit as Linux and other free software. +

+ +

+More than 1649 volunteer package maintainers are working on over 15400 packages +and improving Debian GNU/Linux. The Debian developers contribute to the +project not by writing new applications (in most cases), but by packaging +existing software according to the standards of the project, by communicating +bug reports to upstream developers, and by providing user support. See also +additional information on how to become a contributor in How can I become a Debian software +developer?, Section 12.1. +

+
+
+
+
The Universal Operating System:
+
+

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

+
+
+
+
The Bug Tracking System:
+
+

+The geographical dispersion of the Debian developers required sophisticated +tools and quick communication of bugs and bug-fixes to accelerate the +development of the system. Users are encouraged to send bugs in a formal +style, which are quickly accessible by WWW archives or via e-mail. See +additional information in this FAQ on the management of the bug log in Are there logs of known bugs?, Section +11.4. +

+
+
+
+
The Debian Policy:
+
+

+Debian has an extensive specification of our standards of quality, the Debian +Policy. This document defines the qualities and standards to which we hold +Debian packages. +

+
+
+ +

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

+ +
+ +

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

+ +

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

+ +

+The Debian Project is a separate entity from the FSF, however we communicate +regularly and cooperate on various projects. The FSF explicitly requested that +we call our system "Debian GNU/Linux", and we are happy to comply +with that request. +

+ +

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

+ +
+ +

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

+ +

+The project name is pronounced Deb'-ee-en, with a short e in Deb, and emphasis +on the first syllable. This word is a contraction of the names of Debra and +Ian Murdock, who founded the project. (Dictionaries seem to offer some +ambiguity in the pronunciation of Ian (!), but Ian prefers ee'-en.) +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-basic_defs.html b/includes/common/doc/FAQ/html/ch-basic_defs.html new file mode 100644 index 0000000..7425706 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-basic_defs.html @@ -0,0 +1,431 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Definitions and overview + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

1.1 What is this FAQ?

+ +

+This document gives frequently asked questions (with their answers!) about the +Debian distribution (Debian GNU/Linux and others) and about the Debian project. +If applicable, pointers to other documentation will be given: we won't quote +large parts of external documentation in this document. You'll find out that +some answers assume some knowledge of Unix-like operating systems. We'll try +to assume as little prior knowledge as possible: answers to general beginners +questions will be kept simple. +

+ +

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

+ +
+ +

1.2 What is Debian GNU/Linux?

+ +

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

+ +

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

+ +

+Debian GNU/Linux is the result of a volunteer effort to create a free, +high-quality Unix-compatible operating system, complete with a suite of +applications. The idea of a free Unix-like system originates from the GNU +project, and many of the applications that make Debian GNU/Linux so useful were +developed by the GNU project. +

+ +

+For Debian, free has the GNUish meaning (see the Debian Free Software +Guidelines). When we speak of free software, we are referring to +freedom, not price. Free software means that you have the freedom to +distribute copies of free software, that you receive source code or can get it +if you want it, that you can change the software or use pieces of it in new +free programs; and that you know you can do these things. +

+ +

+The Debian Project was created by Ian Murdock in 1993, initially under the +sponsorship of the Free Software Foundation's GNU project. Today, Debian's +developers think of it as a direct descendent of the GNU project. +

+ +

+Debian GNU/Linux is: +

+
    +
  • +

    +full featured: 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 mirror sites. +

    +
    • +
+
    +
  • +

    +free to use and redistribute: 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. +

    + +

    +The Debian FTP archives also carry approximately 450 software packages (in the +non-free and contrib sections), which are +distributable under specific terms included with each package. +

    +
    • +
+
    +
  • +

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

    +
    • +
+ +

+Although Debian GNU/Linux itself is free software, it is a base upon which +value-added Linux distributions can be built. By providing a reliable, +full-featured base system, Debian provides Linux users with increased +compatibility, and allows Linux distribution creators to eliminate duplication +of effort and focus on the things that make their distribution special. See I am making a special Linux +distribution for a "vertical market". Can I use Debian GNU/Linux for +the guts of a Linux system and add my own applications on top of it?, Section +13.3 for more information. +

+ +
+ +

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

+ +

+In short, Linux is the kernel of a Unix-like operating system. It was +originally designed for 386 (and better) PCs; today Linux also runs on a dozen +of other systems. Linux is written by Linus Torvalds and many computer +scientists around the world. +

+ +

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

+ +
    +
  • +

    +a wide range of Unix utilities, many of which have been developed by the GNU +project and the Free Software Foundation. +

    +
    • +
+ +

+The combination of the Linux kernel, the file system, the GNU and FSF +utilities, and the other utilities are designed to achieve compliance with the +POSIX (IEEE 1003.1) standard; see How +source code compatible is Debian with other Unix systems?, Section 3.3. +

+ +

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

+ +
+ +

1.4 Does Debian just do GNU/Linux?

+ +

+Currently, Debian is only available for Linux, but with Debian GNU/Hurd and +Debian on BSD kernels, we have started to offer non-Linux-based OSes as a +development, server and desktop platform, too. However, these non-linux ports +are not officially released yet. +

+ +

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

+ +

+The Hurd is a set of servers running on top of the GNU Mach microkernel. +Together they build the base for the GNU operating system. +

+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +

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

+
+
Freedom:
+
+

+As stated in the Debian +Social Contract, Debian will remain 100% free. Debian is very +strict about shipping truly free software. The guidelines used to determine if +a work is "free" are provided in The Debian Free +Software. +

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

+The entire system, or any individual component of it, can be upgraded in place +without reformatting, without losing custom configuration files, and (in most +cases) without rebooting the system. Most Linux distributions available today +have some kind of package maintenance system; the Debian package maintenance +system is unique and particularly robust (see Basics of the Debian package management system, +Chapter 6). +

+
+
+
+
Open development:
+
+

+Whereas other Linux distributions are developed by individuals, small, closed +groups, or commercial vendors, Debian is the only major Linux distribution that +is being developed cooperatively by many individuals through the Internet, in +the same spirit as Linux and other free software. +

+ +

+More than 1649 volunteer package maintainers are working on over 15400 packages +and improving Debian GNU/Linux. The Debian developers contribute to the +project not by writing new applications (in most cases), but by packaging +existing software according to the standards of the project, by communicating +bug reports to upstream developers, and by providing user support. See also +additional information on how to become a contributor in How can I become a Debian software +developer?, Section 12.1. +

+
+
+
+
The Universal Operating System:
+
+

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

+
+
+
+
The Bug Tracking System:
+
+

+The geographical dispersion of the Debian developers required sophisticated +tools and quick communication of bugs and bug-fixes to accelerate the +development of the system. Users are encouraged to send bugs in a formal +style, which are quickly accessible by WWW archives or via e-mail. See +additional information in this FAQ on the management of the bug log in Are there logs of known bugs?, Section +11.4. +

+
+
+
+
The Debian Policy:
+
+

+Debian has an extensive specification of our standards of quality, the Debian +Policy. This document defines the qualities and standards to which we hold +Debian packages. +

+
+
+ +

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

+ +
+ +

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

+ +

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

+ +

+The Debian Project is a separate entity from the FSF, however we communicate +regularly and cooperate on various projects. The FSF explicitly requested that +we call our system "Debian GNU/Linux", and we are happy to comply +with that request. +

+ +

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

+ +
+ +

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

+ +

+The project name is pronounced Deb'-ee-en, with a short e in Deb, and emphasis +on the first syllable. This word is a contraction of the names of Debra and +Ian Murdock, who founded the project. (Dictionaries seem to offer some +ambiguity in the pronunciation of Ian (!), but Ian prefers ee'-en.) +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-compat.en.html b/includes/common/doc/FAQ/html/ch-compat.en.html new file mode 100644 index 0000000..24b527d --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-compat.en.html @@ -0,0 +1,386 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Compatibility issues + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

+Debian GNU/Linux includes complete source-code for all of the included +programs, so it should work on all systems which are supported by the Linux +kernel; see the Linux +FAQ for details. +

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+ +

+arm: ARM and StrongARM machines. +

+ +

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

+ +

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

+ +

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

+ +

+s390: IBM S/390 mainframe systems. +

+ +

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

+ +

+For further information on booting, partitioning your drive, enabling PCMCIA +(PC Card) devices and similar issues please follow the instructions given in +the Installation Manual, which is available from our WWW site at http://www.debian.org/releases/stable/installmanual. +

+ +
+ +

3.2 How compatible is Debian with other distributions of Linux?

+ +

+Debian developers communicate with other Linux distribution creators in an +effort to maintain binary compatibility across Linux distributions. Most +commercial Linux products run as well under Debian as they do on the system +upon which they were built. +

+ +

+Debian GNU/Linux adheres to the Linux Filesystem Hierarchy +Standard. However, there is room for interpretation in some of the +rules within this standard, so there may be slight differences between a Debian +system and other Linux systems. +

+ +

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

+ +
+ +

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

+ +

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

+ +

+Linux is intended to adhere to POSIX.1, but the POSIX standards cost real money +and the POSIX.1 (and FIPS 151-2) certification is quite expensive; this made it +more difficult for the Linux developers to work on complete POSIX conformance. +The certification costs make it unlikely that Debian will get an official +conformance certification even if it completely passed the validation suite. +(The validation suite is now freely available, so it is expected that more +people will work on POSIX.1 issues.) +

+ +

+Unifix GmbH (Braunschweig, Germany) developed a Linux system that has been +certified to conform to FIPS 151-2 (a superset of POSIX.1). This technology +was available in Unifix' own distribution called Unifix Linux 2.0 and in +Lasermoon's Linux-FT. +

+ +
+ +

3.4 Can I use Debian packages (".deb" files) on my Red Hat/Slackware/... Linux system? Can I use Red Hat packages (".rpm" files) on my Debian GNU/Linux system?

+ +

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

+
+
You probably can:
+
+

+A program to unpack a Debian package onto a Linux host that is been built from +a `foreign' distribution is available, and will generally work, in the sense +that files will be unpacked. The converse is probably also true, that is, a +program to unpack a Red Hat or Slackware package on a host that is based on +Debian GNU/Linux will probably succeed in unpacking the package and placing +most files in their intended directories. This is largely a consequence of the +existence (and broad adherence to) the Linux Filesystem Hierarchy Standard. +The Alien package +is used to convert between different package formats. +

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

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

+
+
+
+
A better way:
+
+

+The Linux File System Standard (and therefore Debian GNU/Linux) requires that +subdirectories under /usr/local/ be entirely under the user's +discretion. Therefore, users can unpack `foreign' packages into this +directory, and then manage their configuration, upgrade and removal +individually. +

+
+
+ +
+ +

3.5 Is Debian able to run my old libc5 programs?

+ +

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

+ +
+ +

3.6 Can Debian be used to compile libc5 programs?

+ +

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

+ +

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

+ +
+ +

3.7 How should I install a non-Debian program?

+ +

+Files under the directory /usr/local/ are not under the control of +the Debian package management system. Therefore, it is good practice to place +the source code for your program in /usr/local/src/. For example, you might +extract the files for a package named "foo.tar" into the directory +/usr/local/src/foo. After you compile them, place the binaries in +/usr/local/bin/, the libraries in /usr/local/lib/, +and the configuration files in /usr/local/etc/. +

+ +

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

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

+In any case, if you obtain a package whose copyright allows redistribution, you +should consider making a Debian package of it, and uploading it for the Debian +system. Guidelines for becoming a package developer are included in the Debian +Policy manual (see What other +documentation exists on and for a Debian system?, Section 11.1). +

+ +
+ +

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

+ +

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

+ +

+To support binaries that have already been linked with the termcap +library, and for which you do not have the source, Debian provides a package +called termcap-compat. This provides both +libtermcap.so.2 and /etc/termcap. Install this +package if the program fails to run with the error message "can't load +library 'libtermcap.so.2'", or complains about a missing +/etc/termcap file. +

+ +
+ +

3.9 Why can't I install AccelX?

+ +

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

+ +
+ +

3.10 Why do my old XFree 2.1 Motif applications crash?

+ +

+You need to install the motifnls package, which provides the +XFree-2.1 configuration files needed to allow Motif applications compiled under +XFree-2.1 to run under XFree-3.1. +

+ +

+Without these files, some Motif applications compiled on other machines (such +as Netscape) may crash when attempting to copy or paste from or to a text +field, and may also exhibit other problems. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-compat.html b/includes/common/doc/FAQ/html/ch-compat.html new file mode 100644 index 0000000..24b527d --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-compat.html @@ -0,0 +1,386 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Compatibility issues + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

+Debian GNU/Linux includes complete source-code for all of the included +programs, so it should work on all systems which are supported by the Linux +kernel; see the Linux +FAQ for details. +

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+ +

+arm: ARM and StrongARM machines. +

+ +

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

+ +

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

+ +

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

+ +

+s390: IBM S/390 mainframe systems. +

+ +

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

+ +

+For further information on booting, partitioning your drive, enabling PCMCIA +(PC Card) devices and similar issues please follow the instructions given in +the Installation Manual, which is available from our WWW site at http://www.debian.org/releases/stable/installmanual. +

+ +
+ +

3.2 How compatible is Debian with other distributions of Linux?

+ +

+Debian developers communicate with other Linux distribution creators in an +effort to maintain binary compatibility across Linux distributions. Most +commercial Linux products run as well under Debian as they do on the system +upon which they were built. +

+ +

+Debian GNU/Linux adheres to the Linux Filesystem Hierarchy +Standard. However, there is room for interpretation in some of the +rules within this standard, so there may be slight differences between a Debian +system and other Linux systems. +

+ +

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

+ +
+ +

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

+ +

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

+ +

+Linux is intended to adhere to POSIX.1, but the POSIX standards cost real money +and the POSIX.1 (and FIPS 151-2) certification is quite expensive; this made it +more difficult for the Linux developers to work on complete POSIX conformance. +The certification costs make it unlikely that Debian will get an official +conformance certification even if it completely passed the validation suite. +(The validation suite is now freely available, so it is expected that more +people will work on POSIX.1 issues.) +

+ +

+Unifix GmbH (Braunschweig, Germany) developed a Linux system that has been +certified to conform to FIPS 151-2 (a superset of POSIX.1). This technology +was available in Unifix' own distribution called Unifix Linux 2.0 and in +Lasermoon's Linux-FT. +

+ +
+ +

3.4 Can I use Debian packages (".deb" files) on my Red Hat/Slackware/... Linux system? Can I use Red Hat packages (".rpm" files) on my Debian GNU/Linux system?

+ +

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

+
+
You probably can:
+
+

+A program to unpack a Debian package onto a Linux host that is been built from +a `foreign' distribution is available, and will generally work, in the sense +that files will be unpacked. The converse is probably also true, that is, a +program to unpack a Red Hat or Slackware package on a host that is based on +Debian GNU/Linux will probably succeed in unpacking the package and placing +most files in their intended directories. This is largely a consequence of the +existence (and broad adherence to) the Linux Filesystem Hierarchy Standard. +The Alien package +is used to convert between different package formats. +

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

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

+
+
+
+
A better way:
+
+

+The Linux File System Standard (and therefore Debian GNU/Linux) requires that +subdirectories under /usr/local/ be entirely under the user's +discretion. Therefore, users can unpack `foreign' packages into this +directory, and then manage their configuration, upgrade and removal +individually. +

+
+
+ +
+ +

3.5 Is Debian able to run my old libc5 programs?

+ +

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

+ +
+ +

3.6 Can Debian be used to compile libc5 programs?

+ +

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

+ +

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

+ +
+ +

3.7 How should I install a non-Debian program?

+ +

+Files under the directory /usr/local/ are not under the control of +the Debian package management system. Therefore, it is good practice to place +the source code for your program in /usr/local/src/. For example, you might +extract the files for a package named "foo.tar" into the directory +/usr/local/src/foo. After you compile them, place the binaries in +/usr/local/bin/, the libraries in /usr/local/lib/, +and the configuration files in /usr/local/etc/. +

+ +

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

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

+In any case, if you obtain a package whose copyright allows redistribution, you +should consider making a Debian package of it, and uploading it for the Debian +system. Guidelines for becoming a package developer are included in the Debian +Policy manual (see What other +documentation exists on and for a Debian system?, Section 11.1). +

+ +
+ +

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

+ +

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

+ +

+To support binaries that have already been linked with the termcap +library, and for which you do not have the source, Debian provides a package +called termcap-compat. This provides both +libtermcap.so.2 and /etc/termcap. Install this +package if the program fails to run with the error message "can't load +library 'libtermcap.so.2'", or complains about a missing +/etc/termcap file. +

+ +
+ +

3.9 Why can't I install AccelX?

+ +

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

+ +
+ +

3.10 Why do my old XFree 2.1 Motif applications crash?

+ +

+You need to install the motifnls package, which provides the +XFree-2.1 configuration files needed to allow Motif applications compiled under +XFree-2.1 to run under XFree-3.1. +

+ +

+Without these files, some Motif applications compiled on other machines (such +as Netscape) may crash when attempting to copy or paste from or to a text +field, and may also exhibit other problems. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-contributing.en.html b/includes/common/doc/FAQ/html/ch-contributing.en.html new file mode 100644 index 0000000..9ed5a56 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-contributing.en.html @@ -0,0 +1,191 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Contributing to the Debian Project + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

+Donations of time +(to develop new packages, maintain existing packages, or provide user support), +resources (to mirror the FTP and WWW archives), and money (to pay for new +testbeds as well as hardware for the archives) can help the project. +

+ +
+ +

12.1 How can I become a Debian software developer?

+ +

+The development of Debian is open to all, and new users with the right skills +and/or the willingness to learn are needed to maintain existing packages which +have been "orphaned" by their previous maintainers, to develop new +packages, and to provide user support. +

+ +

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

+ +
+ +

12.2 How can I contribute resources to the Debian project?

+ +

+Since the project aims to make a substantial body of software rapidly and +easily accessible throughout the globe, mirrors are urgently needed. It is +desirable but not absolutely necessary to mirror all of the archive. Please +visit the Debian mirror +size page for information on the disk space requirements. +

+ +

+Most of the mirroring is accomplished entirely automatically by scripts, +without any interaction. However, the occasional glitch or system change +occurs which requires human intervention. +

+ +

+If you have a high-speed connection to the Internet, the resources to mirror +all or part of the distribution, and are willing to take the time (or find +someone) who can provide regular maintenance of the system, then please contact +debian-admin@lists.debian.org. +

+ +
+ +

12.3 How can I contribute financially to the Debian project?

+ +

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

+ +
+ +

12.3.1 Software in the Public Interest

+ +

+Software in the Public Interest (SPI) is an IRS 501(c)(3) non-profit +organization, formed when FSF withdrew their sponsorship of Debian. The +purpose of the organization is to develop and distribute free software. +

+ +

+Our goals are very much like those of FSF, and we encourage programmers to use +the GNU General Public License on their programs. However, we have a slightly +different focus in that we are building and distributing a Linux system that +diverges in many technical details from the GNU system planned by FSF. We +still communicate with FSF, and we cooperate in sending them changes to GNU +software and in asking our users to donate to FSF and the GNU project. +

+ +

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

+ +
+ +

12.3.2 Free Software Foundation

+ +

+At this time there is no formal connection between Debian and the Free Software +Foundation. However, the Free Software Foundation is responsible for some of +the most important software components in Debian, including the GNU C compiler, +GNU Emacs, and much of the C run-time library that is used by all programs on +the system. FSF pioneered much of what free software is today: they wrote the +General Public License that is used on much of the Debian software, and they +invented the "GNU" project to create an entirely free Unix system. +Debian should be considered a descendent of the GNU system. +

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-contributing.html b/includes/common/doc/FAQ/html/ch-contributing.html new file mode 100644 index 0000000..9ed5a56 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-contributing.html @@ -0,0 +1,191 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Contributing to the Debian Project + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

+Donations of time +(to develop new packages, maintain existing packages, or provide user support), +resources (to mirror the FTP and WWW archives), and money (to pay for new +testbeds as well as hardware for the archives) can help the project. +

+ +
+ +

12.1 How can I become a Debian software developer?

+ +

+The development of Debian is open to all, and new users with the right skills +and/or the willingness to learn are needed to maintain existing packages which +have been "orphaned" by their previous maintainers, to develop new +packages, and to provide user support. +

+ +

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

+ +
+ +

12.2 How can I contribute resources to the Debian project?

+ +

+Since the project aims to make a substantial body of software rapidly and +easily accessible throughout the globe, mirrors are urgently needed. It is +desirable but not absolutely necessary to mirror all of the archive. Please +visit the Debian mirror +size page for information on the disk space requirements. +

+ +

+Most of the mirroring is accomplished entirely automatically by scripts, +without any interaction. However, the occasional glitch or system change +occurs which requires human intervention. +

+ +

+If you have a high-speed connection to the Internet, the resources to mirror +all or part of the distribution, and are willing to take the time (or find +someone) who can provide regular maintenance of the system, then please contact +debian-admin@lists.debian.org. +

+ +
+ +

12.3 How can I contribute financially to the Debian project?

+ +

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

+ +
+ +

12.3.1 Software in the Public Interest

+ +

+Software in the Public Interest (SPI) is an IRS 501(c)(3) non-profit +organization, formed when FSF withdrew their sponsorship of Debian. The +purpose of the organization is to develop and distribute free software. +

+ +

+Our goals are very much like those of FSF, and we encourage programmers to use +the GNU General Public License on their programs. However, we have a slightly +different focus in that we are building and distributing a Linux system that +diverges in many technical details from the GNU system planned by FSF. We +still communicate with FSF, and we cooperate in sending them changes to GNU +software and in asking our users to donate to FSF and the GNU project. +

+ +

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

+ +
+ +

12.3.2 Free Software Foundation

+ +

+At this time there is no formal connection between Debian and the Free Software +Foundation. However, the Free Software Foundation is responsible for some of +the most important software components in Debian, including the GNU C compiler, +GNU Emacs, and much of the C run-time library that is used by all programs on +the system. FSF pioneered much of what free software is today: they wrote the +General Public License that is used on much of the Debian software, and they +invented the "GNU" project to create an entirely free Unix system. +Debian should be considered a descendent of the GNU system. +

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-customizing.en.html b/includes/common/doc/FAQ/html/ch-customizing.en.html new file mode 100644 index 0000000..fb89888 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-customizing.en.html @@ -0,0 +1,522 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Customizing your installation of Debian GNU/Linux + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +

+If you want a certain user to have access to one of these devices, just add the +user to the group the device belongs to, i.e. do: +

+ +
+     adduser user group
+
+ +

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

+ +
+ +

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

+ +

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

+ +
+ +

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

+ +

+Debian's X programs will install their application resource data in the +/etc/X11/app-defaults/ directory. If you want to customize X +applications globally, put your customizations in those files. They are marked +as configuration files, so their contents will be preserved during upgrades. +

+ +
+ +

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

+ +

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

+ +

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

+
    +
  • +

    +0 (halt the system), +

    +
    • +
+
    +
  • +

    +1 (single-user mode), +

    +
    • +
+
    +
  • +

    +2 through 5 (various multi-user modes), and +

    +
    • +
+
    +
  • +

    +6 (reboot the system). +

    +
    • +
+ +

+Debian systems come with id=2, which indicates that the default runlevel will +be '2' when the multi-user state is entered, and the scripts in +/etc/rc2.d/ will be run. +

+ +

+In fact, the scripts in any of the directories, /etc/rcN.d/ are +just symbolic links back to scripts in /etc/init.d/. However, the +names of the files in each of the /etc/rcN.d/ directories +are selected to indicate the way the scripts in +/etc/init.d/ will be run. Specifically, before entering any +runlevel, all the scripts beginning with 'K' are run; these scripts kill +services. Then all the scripts beginning with 'S' are run; these scripts start +services. The two-digit number following the 'K' or 'S' indicates the order in +which the script is run. Lower numbered scripts are executed first. +

+ +

+This approach works because the scripts in /etc/init.d/ all take +an argument which can be either `start', `stop', `reload', `restart' or +`force-reload' and will then do the task indicated by the argument. These +scripts can be used even after a system has been booted, to control various +processes. +

+ +

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

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

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

+ +
+ +

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

+ +

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

+
    +
  • +

    +Enter the script foo into the directory /etc/init.d/. +

    +
    • +
+
    +
  • +

    +Run the Debian command update-rc.d with appropriate arguments, to +set up links between the (command-line-specified) directories rc?.d and +/etc/init.d/foo. Here, '?' is a number from 0 through 6 and +corresponds to each of the System V runlevels. +

    +
    • +
+
    +
  • +

    +Reboot the system. +

    +
    • +
+ +

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

+ +

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

+ +
+ +

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

+ +

+Some users wish to create, for example, a new server by installing a group of +Debian packages and a locally generated package consisting of configuration +files. This is not generally a good idea, because dpkg will not +know about those configuration files if they are in a different package, and +may write conflicting configurations when one of the initial "group" +of packages is upgraded. +

+ +

+Instead, create a local package that modifies the configuration files of the +"group" of Debian packages of interest. Then dpkg and +the rest of the package management system will see that the files have been +modified by the local "sysadmin" and will not try to overwrite them +when those packages are upgraded. +

+ +
+ +

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

+ +

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

+ +

+Do not: +

+
    +
  • +

    +Overwrite /bin/login with login-local. +

    +
    • +
+ +

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

+ +

+Rather, do +

+
    +
  • +

    +Execute: +

    + +
    +     dpkg-divert --divert /bin/login.debian /bin/login
+
    + +

    +in order to cause all future installations of the Debian login +package to write the file /bin/login to +/bin/login.debian instead. +

    +
    • +
+
    +
  • +

    +Then execute: +

    + +
    +     cp login-local /bin/login
+
    + +

    +to move your own locally-built program into place. +

    +
    • +
+ +

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

+ +
+ +

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

+ +

+Execute the command: +

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

+where: +

+
    +
  • +

    +BIN-DIR is a directory where Debian archive files (which usually have an +extension of ".deb") are stored. +

    +
    • +
+
    +
  • +

    +OVERRIDE_FILE is a file that is edited by the distribution maintainers and is +usually stored on a Debian FTP archive at indices/override.main.gz +for the Debian packages in the "main" distribution. You can ignore +this for local packages. +

    +
    • +
+
    +
  • +

    +PATHPREFIX is an optional string that can be prepended to the +my_Packages file being produced. +

    +
    • +
+ +

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

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

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

+ +
+ +

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

+ +

+There are several cases where two packages provide two different versions of a +program, both of which provide the same core functionality. Users might prefer +one over another out of habit, or because the user interface of one package is +somehow more pleasing than the interface of another. Other users on the same +system might make a different choice. +

+ +

+Debian uses a "virtual" package system to allow system administrators +to choose (or let users choose) their favorite tools when there are two or more +that provide the same basic functionality, yet satisfy package dependency +requirements without specifying a particular package. +

+ +

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

+ +

+A single link is insufficient to support full use of an alternate program; +normally, manual pages, and possibly other supporting files must be selected as +well. The Perl script update-alternatives provides a way of +ensuring that all the files associated with a specified package are selected as +a system default. +

+ +

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

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

+If you want to change it, run: +

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

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

+ +

+If a package doesn't register itself as a window manager for some reason (file +a bug if it's in error), or if you use a window manager from /usr/local +directory, the selections on screen won't contain your preferred entry. You +can update the link through command line options, like this: +

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

+The first argument to `--install' option is the symlink that points to +/etc/alternatives/NAME, where NAME is the second argument. The third argument +is the program to which /etc/alternatives/NAME should point to, and the fourth +argument is the priority (larger value means the alternative will more probably +get picked automatically). +

+ +

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

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

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-customizing.html b/includes/common/doc/FAQ/html/ch-customizing.html new file mode 100644 index 0000000..fb89888 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-customizing.html @@ -0,0 +1,522 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Customizing your installation of Debian GNU/Linux + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +

+If you want a certain user to have access to one of these devices, just add the +user to the group the device belongs to, i.e. do: +

+ +
+     adduser user group
+
+ +

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

+ +
+ +

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

+ +

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

+ +
+ +

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

+ +

+Debian's X programs will install their application resource data in the +/etc/X11/app-defaults/ directory. If you want to customize X +applications globally, put your customizations in those files. They are marked +as configuration files, so their contents will be preserved during upgrades. +

+ +
+ +

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

+ +

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

+ +

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

+
    +
  • +

    +0 (halt the system), +

    +
    • +
+
    +
  • +

    +1 (single-user mode), +

    +
    • +
+
    +
  • +

    +2 through 5 (various multi-user modes), and +

    +
    • +
+
    +
  • +

    +6 (reboot the system). +

    +
    • +
+ +

+Debian systems come with id=2, which indicates that the default runlevel will +be '2' when the multi-user state is entered, and the scripts in +/etc/rc2.d/ will be run. +

+ +

+In fact, the scripts in any of the directories, /etc/rcN.d/ are +just symbolic links back to scripts in /etc/init.d/. However, the +names of the files in each of the /etc/rcN.d/ directories +are selected to indicate the way the scripts in +/etc/init.d/ will be run. Specifically, before entering any +runlevel, all the scripts beginning with 'K' are run; these scripts kill +services. Then all the scripts beginning with 'S' are run; these scripts start +services. The two-digit number following the 'K' or 'S' indicates the order in +which the script is run. Lower numbered scripts are executed first. +

+ +

+This approach works because the scripts in /etc/init.d/ all take +an argument which can be either `start', `stop', `reload', `restart' or +`force-reload' and will then do the task indicated by the argument. These +scripts can be used even after a system has been booted, to control various +processes. +

+ +

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

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

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

+ +
+ +

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

+ +

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

+
    +
  • +

    +Enter the script foo into the directory /etc/init.d/. +

    +
    • +
+
    +
  • +

    +Run the Debian command update-rc.d with appropriate arguments, to +set up links between the (command-line-specified) directories rc?.d and +/etc/init.d/foo. Here, '?' is a number from 0 through 6 and +corresponds to each of the System V runlevels. +

    +
    • +
+
    +
  • +

    +Reboot the system. +

    +
    • +
+ +

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

+ +

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

+ +
+ +

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

+ +

+Some users wish to create, for example, a new server by installing a group of +Debian packages and a locally generated package consisting of configuration +files. This is not generally a good idea, because dpkg will not +know about those configuration files if they are in a different package, and +may write conflicting configurations when one of the initial "group" +of packages is upgraded. +

+ +

+Instead, create a local package that modifies the configuration files of the +"group" of Debian packages of interest. Then dpkg and +the rest of the package management system will see that the files have been +modified by the local "sysadmin" and will not try to overwrite them +when those packages are upgraded. +

+ +
+ +

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

+ +

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

+ +

+Do not: +

+
    +
  • +

    +Overwrite /bin/login with login-local. +

    +
    • +
+ +

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

+ +

+Rather, do +

+
    +
  • +

    +Execute: +

    + +
    +     dpkg-divert --divert /bin/login.debian /bin/login
+
    + +

    +in order to cause all future installations of the Debian login +package to write the file /bin/login to +/bin/login.debian instead. +

    +
    • +
+
    +
  • +

    +Then execute: +

    + +
    +     cp login-local /bin/login
+
    + +

    +to move your own locally-built program into place. +

    +
    • +
+ +

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

+ +
+ +

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

+ +

+Execute the command: +

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

+where: +

+
    +
  • +

    +BIN-DIR is a directory where Debian archive files (which usually have an +extension of ".deb") are stored. +

    +
    • +
+
    +
  • +

    +OVERRIDE_FILE is a file that is edited by the distribution maintainers and is +usually stored on a Debian FTP archive at indices/override.main.gz +for the Debian packages in the "main" distribution. You can ignore +this for local packages. +

    +
    • +
+
    +
  • +

    +PATHPREFIX is an optional string that can be prepended to the +my_Packages file being produced. +

    +
    • +
+ +

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

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

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

+ +
+ +

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

+ +

+There are several cases where two packages provide two different versions of a +program, both of which provide the same core functionality. Users might prefer +one over another out of habit, or because the user interface of one package is +somehow more pleasing than the interface of another. Other users on the same +system might make a different choice. +

+ +

+Debian uses a "virtual" package system to allow system administrators +to choose (or let users choose) their favorite tools when there are two or more +that provide the same basic functionality, yet satisfy package dependency +requirements without specifying a particular package. +

+ +

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

+ +

+A single link is insufficient to support full use of an alternate program; +normally, manual pages, and possibly other supporting files must be selected as +well. The Perl script update-alternatives provides a way of +ensuring that all the files associated with a specified package are selected as +a system default. +

+ +

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

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

+If you want to change it, run: +

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

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

+ +

+If a package doesn't register itself as a window manager for some reason (file +a bug if it's in error), or if you use a window manager from /usr/local +directory, the selections on screen won't contain your preferred entry. You +can update the link through command line options, like this: +

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

+The first argument to `--install' option is the symlink that points to +/etc/alternatives/NAME, where NAME is the second argument. The third argument +is the program to which /etc/alternatives/NAME should point to, and the fourth +argument is the priority (larger value means the alternative will more probably +get picked automatically). +

+ +

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

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

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-faqinfo.en.html b/includes/common/doc/FAQ/html/ch-faqinfo.en.html new file mode 100644 index 0000000..6fdb982 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-faqinfo.en.html @@ -0,0 +1,210 @@ + + + + + + + + +The Debian GNU/Linux FAQ - General information about the FAQ + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

15.1 Authors

+ +

+The first edition of this FAQ was made and maintained by J.H.M. Dassen (Ray) +and Chuck Stickelman. Authors of the rewritten Debian GNU/Linux FAQ are Susan +G. Kleinmann and Sven Rudolph. After them, the FAQ was maintained by Santiago +Vila and, later, by Josip Rodin. The current maintainer is Javier +Fernandez-Sanguino. +

+ +

+Parts of the information came from: +

+
    +
  • +

    +The Debian-1.1 release announcement, by Bruce Perens. +

    +
    • +
+ + + +
    +
  • +

    +many developers, volunteers, and beta testers, and +

    +
    • +
+
    +
  • +

    +the flaky memories of its authors. :-) +

    +
    • +
+ +

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

+ +

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

+ +
+ +

15.2 Feedback

+ +

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

+ +
+ +

15.3 Availability

+ +

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

+ +

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

+ +

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

+ +
+ +

15.4 Document format

+ +

+This document was written using the DebianDoc SGML DTD (rewritten from LinuxDoc +SGML). DebianDoc SGML systems enables us to create files in a variety of +formats from one source, e.g. this document can be viewed as HTML, plain text, +TeX DVI, PostScript, PDF, or GNU info. +

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-faqinfo.html b/includes/common/doc/FAQ/html/ch-faqinfo.html new file mode 100644 index 0000000..6fdb982 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-faqinfo.html @@ -0,0 +1,210 @@ + + + + + + + + +The Debian GNU/Linux FAQ - General information about the FAQ + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

15.1 Authors

+ +

+The first edition of this FAQ was made and maintained by J.H.M. Dassen (Ray) +and Chuck Stickelman. Authors of the rewritten Debian GNU/Linux FAQ are Susan +G. Kleinmann and Sven Rudolph. After them, the FAQ was maintained by Santiago +Vila and, later, by Josip Rodin. The current maintainer is Javier +Fernandez-Sanguino. +

+ +

+Parts of the information came from: +

+
    +
  • +

    +The Debian-1.1 release announcement, by Bruce Perens. +

    +
    • +
+ + + +
    +
  • +

    +many developers, volunteers, and beta testers, and +

    +
    • +
+
    +
  • +

    +the flaky memories of its authors. :-) +

    +
    • +
+ +

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

+ +

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

+ +
+ +

15.2 Feedback

+ +

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

+ +
+ +

15.3 Availability

+ +

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

+ +

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

+ +

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

+ +
+ +

15.4 Document format

+ +

+This document was written using the DebianDoc SGML DTD (rewritten from LinuxDoc +SGML). DebianDoc SGML systems enables us to create files in a variety of +formats from one source, e.g. this document can be viewed as HTML, plain text, +TeX DVI, PostScript, PDF, or GNU info. +

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-ftparchives.en.html b/includes/common/doc/FAQ/html/ch-ftparchives.en.html new file mode 100644 index 0000000..0133507 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-ftparchives.en.html @@ -0,0 +1,567 @@ + + + + + + + + +The Debian GNU/Linux FAQ - The Debian FTP archives + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +

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

+ +

+There are the following supplementary directories: +

+
+
/tools/:
+
+

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

+
+
+
+
/doc/:
+
+

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

+
+
+
+
/indices/:
+
+

+The Maintainers file and the override files. +

+
+
+
+
/project/:
+
+

+mostly developer-only materials, such as: +

+
+
project/experimental/:
+
+

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

+
+
+
+
+ +
+ +

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

+ +

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

+ +
+ +

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

+ +

+They are just "codenames". When a Debian distribution is in the +development stage, it has no version number but a codename. The purpose of +these codenames is to make easier the mirroring of the Debian distributions (if +a real directory like unstable suddenly changed its name to +stable, a lot of stuff would have to be needlessly downloaded +again). +

+ +

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

+ +

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

+ +
+ +

5.3.1 Which other codenames have been used in the past?

+ +

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

+ +
+ +

5.3.2 Where do these codenames come from?

+ +

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

+
    +
  • +

    +buzz (Buzz Lightyear) was the spaceman, +

    +
    • +
+
    +
  • +

    +rex was the tyrannosaurus, +

    +
    • +
+
    +
  • +

    +bo (Bo Peep) was the girl who took care of the sheep, +

    +
    • +
+
    +
  • +

    +hamm was the piggy bank, +

    +
    • +
+
    +
  • +

    +slink (Slinky Dog (R)) was the toy dog, +

    +
    • +
+
    +
  • +

    +potato was, of course, Mr. Potato (R), +

    +
    • +
+
    +
  • +

    +woody was the cowboy, +

    +
    • +
+
    +
  • +

    +sarge was the sergeant of the Green Plastic Army Men, +

    +
    • +
+
    +
  • +

    +etch was the toy blackboard (Etch-a-Sketch (R)). +

    +
    • +
+
    +
  • +

    +sid was the boy next door who destroyed toys. +

    +
    • +
+ +
+ +

5.4 What about "sid"?

+ +

+sid or unstable is the place where most of the packages are +initially uploaded. It will never be released directly, because packages which +are to be released will first have to be included in testing, in order +to be released in stable later on. sid contains packages for both +released and unreleased architectures. +

+ +

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

+ +

+[1] +

+ +
+ +

5.5 What does the stable directory contain?

+
    +
  • +

    +stable/main/: This directory contains the packages which formally constitute +the most recent release of the Debian GNU/Linux system. +

    + +

    +These packages all comply with the Debian Free Software +Guidelines, and are all freely usable and distributable. +

    +
    • +
+
    +
  • +

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

    + +

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

    +
    • +
+
    +
  • +

    +stable/contrib/: This directory contains packages which are DFSG-free and +freely distributable themselves, but somehow depend on a package that +is not freely distributable and thus available only in the non-free +section. +

    +
    • +
+ +
+ +

5.6 What does the testing directory contain?

+ +

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

+ +

+They must be in sync on all architectures where they have been built and +mustn't have dependencies that make them uninstallable; they also have to have +fewer release-critical bugs than the versions currently in testing. This way, +we hope that `testing' is always close to being a release candidate. +

+ +

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

+ +
+ +

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

+ +

+When the "testing" distribution is mature enough, the release manager +starts `freezing' it. The normal propagation delays are increased to ensure +that as little as possible new bugs from "unstable" enter +"testing". +

+ +

+After a while, the "testing" distribution becomes truly `frozen'. +This means that all new packages that are to propagate to the +"testing" are held back, unless they include release-critical bug +fixes. The "testing" distribution can also remain in such a deep +freeze during the so-called `test cycles', when the release is imminent. +

+ +

+We keep a record of bugs in the "testing" distribution that can hold +off a package from being released, or bugs that can hold back the whole +release. For details, please see current testing release +information. +

+ +

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

+ +

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

+ +
+ +

5.7 What does the unstable directory contain?

+ +

+The `unstable' directory contains a snapshot of the current development system. +Users are welcome to use and test these packages, but are warned about their +state of readiness. The advantage of using the unstable distribution is that +you are always up-to-date with the latest in GNU/Linux software industry, but +if it breaks: you get to keep both parts :-) +

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+ +

+Furthermore, there's a subdirectory called source/ which contains index files +for source packages included in the distribution. The index file is called +Sources(.gz). +

+ +

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

+ +
+ +

5.9 Where is the source code?

+ +

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

+ +

+The source code is distributed in the pool directory (see What's in the pool directory?, Section 5.10) +together with all the architecture-specific binary directories. To retrieve +the source code without having to be familiar with the structure of the FTP +archive, try a command like apt-get source mypackagename. +

+ +

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

+ +

+Source code may or may not be available for packages in the "contrib" +and "non-free" directories, which are not formally part of the Debian +system. +

+ +
+ +

5.10 What's in the pool directory?

+ +

+Packages are kept in a large `pool', structured according to the name of the +source package. To make this manageable, the pool is subdivided by section +(`main', `contrib' and `non-free') and by the first letter of the source +package name. These directories contain several files: the binary packages for +each architecture, and the source packages from which the binary packages were +generated. +

+ +

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

+ +

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

+ +

+[3] +

+ +
+ +

5.11 What is "incoming"?

+ +

+After a developer uploads a package, it stays for a short while in the +"incoming" directory before it is checked that it's genuine and +allowed into the archive. +

+ +

+Usually nobody should install things from this place. However, in some rare +cases of emergency, the incoming directory is available at http://incoming.debian.org/. You +can manually fetch packages, check the GPG signature and MD5sums in the +.changes and .dsc files, and then install them. +

+ +
+ +

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

+ +

+If you have built some private Debian packages which you'd like to install +using the standard Debian package management tools, you can set up your own +apt-able package archive. This is also useful if you'd like to share your +Debian packages while these are not distributed by the Debian project. +Instructions on how to do this are given in the Debian +Repository HOWTO. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-ftparchives.html b/includes/common/doc/FAQ/html/ch-ftparchives.html new file mode 100644 index 0000000..0133507 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-ftparchives.html @@ -0,0 +1,567 @@ + + + + + + + + +The Debian GNU/Linux FAQ - The Debian FTP archives + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +

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

+ +

+There are the following supplementary directories: +

+
+
/tools/:
+
+

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

+
+
+
+
/doc/:
+
+

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

+
+
+
+
/indices/:
+
+

+The Maintainers file and the override files. +

+
+
+
+
/project/:
+
+

+mostly developer-only materials, such as: +

+
+
project/experimental/:
+
+

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

+
+
+
+
+ +
+ +

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

+ +

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

+ +
+ +

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

+ +

+They are just "codenames". When a Debian distribution is in the +development stage, it has no version number but a codename. The purpose of +these codenames is to make easier the mirroring of the Debian distributions (if +a real directory like unstable suddenly changed its name to +stable, a lot of stuff would have to be needlessly downloaded +again). +

+ +

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

+ +

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

+ +
+ +

5.3.1 Which other codenames have been used in the past?

+ +

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

+ +
+ +

5.3.2 Where do these codenames come from?

+ +

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

+
    +
  • +

    +buzz (Buzz Lightyear) was the spaceman, +

    +
    • +
+
    +
  • +

    +rex was the tyrannosaurus, +

    +
    • +
+
    +
  • +

    +bo (Bo Peep) was the girl who took care of the sheep, +

    +
    • +
+
    +
  • +

    +hamm was the piggy bank, +

    +
    • +
+
    +
  • +

    +slink (Slinky Dog (R)) was the toy dog, +

    +
    • +
+
    +
  • +

    +potato was, of course, Mr. Potato (R), +

    +
    • +
+
    +
  • +

    +woody was the cowboy, +

    +
    • +
+
    +
  • +

    +sarge was the sergeant of the Green Plastic Army Men, +

    +
    • +
+
    +
  • +

    +etch was the toy blackboard (Etch-a-Sketch (R)). +

    +
    • +
+
    +
  • +

    +sid was the boy next door who destroyed toys. +

    +
    • +
+ +
+ +

5.4 What about "sid"?

+ +

+sid or unstable is the place where most of the packages are +initially uploaded. It will never be released directly, because packages which +are to be released will first have to be included in testing, in order +to be released in stable later on. sid contains packages for both +released and unreleased architectures. +

+ +

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

+ +

+[1] +

+ +
+ +

5.5 What does the stable directory contain?

+
    +
  • +

    +stable/main/: This directory contains the packages which formally constitute +the most recent release of the Debian GNU/Linux system. +

    + +

    +These packages all comply with the Debian Free Software +Guidelines, and are all freely usable and distributable. +

    +
    • +
+
    +
  • +

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

    + +

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

    +
    • +
+
    +
  • +

    +stable/contrib/: This directory contains packages which are DFSG-free and +freely distributable themselves, but somehow depend on a package that +is not freely distributable and thus available only in the non-free +section. +

    +
    • +
+ +
+ +

5.6 What does the testing directory contain?

+ +

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

+ +

+They must be in sync on all architectures where they have been built and +mustn't have dependencies that make them uninstallable; they also have to have +fewer release-critical bugs than the versions currently in testing. This way, +we hope that `testing' is always close to being a release candidate. +

+ +

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

+ +
+ +

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

+ +

+When the "testing" distribution is mature enough, the release manager +starts `freezing' it. The normal propagation delays are increased to ensure +that as little as possible new bugs from "unstable" enter +"testing". +

+ +

+After a while, the "testing" distribution becomes truly `frozen'. +This means that all new packages that are to propagate to the +"testing" are held back, unless they include release-critical bug +fixes. The "testing" distribution can also remain in such a deep +freeze during the so-called `test cycles', when the release is imminent. +

+ +

+We keep a record of bugs in the "testing" distribution that can hold +off a package from being released, or bugs that can hold back the whole +release. For details, please see current testing release +information. +

+ +

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

+ +

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

+ +
+ +

5.7 What does the unstable directory contain?

+ +

+The `unstable' directory contains a snapshot of the current development system. +Users are welcome to use and test these packages, but are warned about their +state of readiness. The advantage of using the unstable distribution is that +you are always up-to-date with the latest in GNU/Linux software industry, but +if it breaks: you get to keep both parts :-) +

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+ +

+Furthermore, there's a subdirectory called source/ which contains index files +for source packages included in the distribution. The index file is called +Sources(.gz). +

+ +

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

+ +
+ +

5.9 Where is the source code?

+ +

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

+ +

+The source code is distributed in the pool directory (see What's in the pool directory?, Section 5.10) +together with all the architecture-specific binary directories. To retrieve +the source code without having to be familiar with the structure of the FTP +archive, try a command like apt-get source mypackagename. +

+ +

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

+ +

+Source code may or may not be available for packages in the "contrib" +and "non-free" directories, which are not formally part of the Debian +system. +

+ +
+ +

5.10 What's in the pool directory?

+ +

+Packages are kept in a large `pool', structured according to the name of the +source package. To make this manageable, the pool is subdivided by section +(`main', `contrib' and `non-free') and by the first letter of the source +package name. These directories contain several files: the binary packages for +each architecture, and the source packages from which the binary packages were +generated. +

+ +

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

+ +

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

+ +

+[3] +

+ +
+ +

5.11 What is "incoming"?

+ +

+After a developer uploads a package, it stays for a short while in the +"incoming" directory before it is checked that it's genuine and +allowed into the archive. +

+ +

+Usually nobody should install things from this place. However, in some rare +cases of emergency, the incoming directory is available at http://incoming.debian.org/. You +can manually fetch packages, check the GPG signature and MD5sums in the +.changes and .dsc files, and then install them. +

+ +
+ +

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

+ +

+If you have built some private Debian packages which you'd like to install +using the standard Debian package management tools, you can set up your own +apt-able package archive. This is also useful if you'd like to share your +Debian packages while these are not distributed by the Debian project. +Instructions on how to do this are given in the Debian +Repository HOWTO. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-getting.en.html b/includes/common/doc/FAQ/html/ch-getting.en.html new file mode 100644 index 0000000..5f608d5 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-getting.en.html @@ -0,0 +1,374 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Getting and installing Debian GNU/Linux + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
+ +

2.1 What is the latest version of Debian?

+ +

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

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

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

+
+
+
+
the `testing' distribution
+
+

+This is where packages that will be released as the next `stable' are placed; +they've had some testing in unstable but they may not be completely fit for +release yet. This distribution is updated more often than `stable', but not +more often than `unstable'. +

+
+
+
+
the `unstable' distribution
+
+

+This is the version currently under development; it is updated continuously. +You can retrieve packages from the `unstable' archive on any Debian FTP site +and use them to upgrade your system at any time, but you may not expect the +system to be as usable or as stable as before - that's why it's called +`unstable'! +

+
+
+ +

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

+ +
+ +

2.2 Are there package upgrades in `stable'?

+ +

+No new functionality is added to the stable release. Once a Debian version is +released and tagged `stable' it will only get security updates. That is, only +packages for which a security vulnerability has been found after the release +will be upgraded. All the security updates are served through security.debian.org. +

+ +

+Security updates serve one purpose: to supply a fix for a security +vulnerability. They are not a method for sneaking additional changes into the +stable release without going through normal point release procedure. +Consequently, fixes for packages with security issues will not upgrade the +software. The Debian Security Team will backport the necessary fixes to the +version of the software distributed in `stable' instead. +

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +

+Official Debian CD images indeed contain symlinks like: +

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

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

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

+. +

+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +

+Using floppy disks has these complications: +

+
    +
  • +

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

    +
    • +
+
    +
  • +

    +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 +dpkg-split, Section 7.1.5.2), +available in the tools directory on Debian mirrors. +

    +
    • +
+ +

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

+ +

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

+
    +
  • +
    +     mount -t msdos /dev/fd0 /floppy/
+
    + +

    +if the floppy disk is in drive A: and has an MS-DOS file system, +

    +
    • +
+
    +
  • +
    +     mount -t msdos /dev/fd1 /floppy/
+
    + +

    +if the floppy disk is in drive B: and has an MS-DOS file system, +

    +
    • +
+
    +
  • +
    +     mount -t ext2 /dev/fd0 /floppy/
+
    + +

    +if the floppy disk is in drive A: and has an ext2 (i.e., a normal Linux) file +system. +

    +
    • +
+ +
+ +

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

+ +

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

+ +

+You can download a small CD image file, create a bootable CD from it, install +the basic system from it and the rest over the network. For more information +please see http://www.debian.org/CD/netinst/. +

+ +

+You can also download even smaller floppy disk image files, create bootable +diskettes from them, start the installation procedure and get the rest of +Debian over the network. For more information, please see http://www.debian.org/distrib/floppyinst. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-getting.html b/includes/common/doc/FAQ/html/ch-getting.html new file mode 100644 index 0000000..5f608d5 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-getting.html @@ -0,0 +1,374 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Getting and installing Debian GNU/Linux + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
+ +

2.1 What is the latest version of Debian?

+ +

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

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

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

+
+
+
+
the `testing' distribution
+
+

+This is where packages that will be released as the next `stable' are placed; +they've had some testing in unstable but they may not be completely fit for +release yet. This distribution is updated more often than `stable', but not +more often than `unstable'. +

+
+
+
+
the `unstable' distribution
+
+

+This is the version currently under development; it is updated continuously. +You can retrieve packages from the `unstable' archive on any Debian FTP site +and use them to upgrade your system at any time, but you may not expect the +system to be as usable or as stable as before - that's why it's called +`unstable'! +

+
+
+ +

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

+ +
+ +

2.2 Are there package upgrades in `stable'?

+ +

+No new functionality is added to the stable release. Once a Debian version is +released and tagged `stable' it will only get security updates. That is, only +packages for which a security vulnerability has been found after the release +will be upgraded. All the security updates are served through security.debian.org. +

+ +

+Security updates serve one purpose: to supply a fix for a security +vulnerability. They are not a method for sneaking additional changes into the +stable release without going through normal point release procedure. +Consequently, fixes for packages with security issues will not upgrade the +software. The Debian Security Team will backport the necessary fixes to the +version of the software distributed in `stable' instead. +

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +

+Official Debian CD images indeed contain symlinks like: +

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

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

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

+. +

+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +

+Using floppy disks has these complications: +

+
    +
  • +

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

    +
    • +
+
    +
  • +

    +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 +dpkg-split, Section 7.1.5.2), +available in the tools directory on Debian mirrors. +

    +
    • +
+ +

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

+ +

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

+
    +
  • +
    +     mount -t msdos /dev/fd0 /floppy/
+
    + +

    +if the floppy disk is in drive A: and has an MS-DOS file system, +

    +
    • +
+
    +
  • +
    +     mount -t msdos /dev/fd1 /floppy/
+
    + +

    +if the floppy disk is in drive B: and has an MS-DOS file system, +

    +
    • +
+
    +
  • +
    +     mount -t ext2 /dev/fd0 /floppy/
+
    + +

    +if the floppy disk is in drive A: and has an ext2 (i.e., a normal Linux) file +system. +

    +
    • +
+ +
+ +

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

+ +

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

+ +

+You can download a small CD image file, create a bootable CD from it, install +the basic system from it and the rest over the network. For more information +please see http://www.debian.org/CD/netinst/. +

+ +

+You can also download even smaller floppy disk image files, create bootable +diskettes from them, start the installation procedure and get the rest of +Debian over the network. For more information, please see http://www.debian.org/distrib/floppyinst. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-kernel.en.html b/includes/common/doc/FAQ/html/ch-kernel.en.html new file mode 100644 index 0000000..5e88fad --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-kernel.en.html @@ -0,0 +1,311 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Debian and the kernel + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

+Yes. +

+ +

+There's only one common catch: the Debian C libraries are built with the most +recent stable releases of the kernel headers. If you +happen to need to compile a program with kernel headers newer than the ones +from the stable branch, then you should either upgrade the package containing +the headers (libc6-dev), or use the new headers from an unpacked +tree of the newer kernel. That is, if the kernel sources are in +/usr/src/linux, then you should add +-I/usr/src/linux/include/ to your command line when compiling. +

+ +
+ +

9.2 What tools does Debian provide to build custom kernels?

+ +

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

+ +
+     make-kpkg kernel_image
+
+ +

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

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

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

+ +

+Users must separately download the source code for the most recent kernel (or +the kernel of their choice) from their favorite Linux archive site, unless a +kernel-source-version package is available (where "version" stands +for the kernel version). +

+ +

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

+
    +
  • +

    +Unpack the kernel sources, and cd to the newly created directory. +

    +
    • +
+
    +
  • +

    +Modify the kernel configuration using one of these commands: +

    +
      +
    • +

      +make config (for a tty one-line-at-a-time-interface). +

      +
      • +
    +
      +
    • +

      +make menuconfig (for an ncurses-based menu driven interface). +Note that to use this option, the libncurses5-dev package must be +installed. +

      +
      • +
    +
      +
    • +

      +make xconfig (for an X11 interface). Using this option requires +that relevant X and Tcl/Tk packages be installed. +

      +
      • +
    + +

    +Any of the above steps generates a new .config in the top-level +kernel source directory. +

    +
    • +
+
    +
  • +

    +Execute the command: make-kpkg -rev Custom.N kernel_image, where N +is a revision number assigned by the user. The new Debian archive thus formed +would have revision Custom.1, e.g., +kernel-image-2.2.14_Custom.1_i386.deb for the Linux kernel 2.2.14 +on i386. +

    +
    • +
+
    +
  • +

    +Install the package created. +

    +
      +
    • +

      +Run dpkg --install /usr/src/kernel-image-VVV_Custom.N.deb to +install the kernel itself. The installation script will: +

      +
        +
      • +

        +run the boot loader (grub, LILO or some other) if needed, +

        +
        • +
      +
        +
      • +

        +install the custom kernel in /boot/vmlinuz_VVV-Custom.N, and set up appropriate +symbolic links to the most recent kernel version. +

        +
        • +
      + +
      • +
    +
      +
    • +

      +To employ secondary boot loaders such as loadlin, copy this image +to other locations (e.g. to an MS-DOS partition). +

      +
      • +
    +
    • +
+ +
+ +

9.3 How can I make a custom boot floppy?

+ +

+This task is greatly aided by the Debian package boot-floppies, +normally found in the admin section of the Debian FTP archive. +Shell scripts in this package produce boot floppies in the +SYSLINUX format. These are MS-DOS formatted floppies +whose master boot records have been altered so that they boot Linux directly +(or whatever other operating system has been defined in the syslinux.cfg file +on the floppy). Other scripts in this package produce emergency root disks and +can even reproduce the base disks. +

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +

+Yes. The kernel-image-NNN.prerm script checks to see whether the +kernel you are currently running is the same as the kernel you are trying to +de-install. Therefore you can remove unwanted kernel image packages using this +command: +

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

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-kernel.html b/includes/common/doc/FAQ/html/ch-kernel.html new file mode 100644 index 0000000..5e88fad --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-kernel.html @@ -0,0 +1,311 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Debian and the kernel + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

+Yes. +

+ +

+There's only one common catch: the Debian C libraries are built with the most +recent stable releases of the kernel headers. If you +happen to need to compile a program with kernel headers newer than the ones +from the stable branch, then you should either upgrade the package containing +the headers (libc6-dev), or use the new headers from an unpacked +tree of the newer kernel. That is, if the kernel sources are in +/usr/src/linux, then you should add +-I/usr/src/linux/include/ to your command line when compiling. +

+ +
+ +

9.2 What tools does Debian provide to build custom kernels?

+ +

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

+ +
+     make-kpkg kernel_image
+
+ +

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

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

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

+ +

+Users must separately download the source code for the most recent kernel (or +the kernel of their choice) from their favorite Linux archive site, unless a +kernel-source-version package is available (where "version" stands +for the kernel version). +

+ +

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

+
    +
  • +

    +Unpack the kernel sources, and cd to the newly created directory. +

    +
    • +
+
    +
  • +

    +Modify the kernel configuration using one of these commands: +

    +
      +
    • +

      +make config (for a tty one-line-at-a-time-interface). +

      +
      • +
    +
      +
    • +

      +make menuconfig (for an ncurses-based menu driven interface). +Note that to use this option, the libncurses5-dev package must be +installed. +

      +
      • +
    +
      +
    • +

      +make xconfig (for an X11 interface). Using this option requires +that relevant X and Tcl/Tk packages be installed. +

      +
      • +
    + +

    +Any of the above steps generates a new .config in the top-level +kernel source directory. +

    +
    • +
+
    +
  • +

    +Execute the command: make-kpkg -rev Custom.N kernel_image, where N +is a revision number assigned by the user. The new Debian archive thus formed +would have revision Custom.1, e.g., +kernel-image-2.2.14_Custom.1_i386.deb for the Linux kernel 2.2.14 +on i386. +

    +
    • +
+
    +
  • +

    +Install the package created. +

    +
      +
    • +

      +Run dpkg --install /usr/src/kernel-image-VVV_Custom.N.deb to +install the kernel itself. The installation script will: +

      +
        +
      • +

        +run the boot loader (grub, LILO or some other) if needed, +

        +
        • +
      +
        +
      • +

        +install the custom kernel in /boot/vmlinuz_VVV-Custom.N, and set up appropriate +symbolic links to the most recent kernel version. +

        +
        • +
      + +
      • +
    +
      +
    • +

      +To employ secondary boot loaders such as loadlin, copy this image +to other locations (e.g. to an MS-DOS partition). +

      +
      • +
    +
    • +
+ +
+ +

9.3 How can I make a custom boot floppy?

+ +

+This task is greatly aided by the Debian package boot-floppies, +normally found in the admin section of the Debian FTP archive. +Shell scripts in this package produce boot floppies in the +SYSLINUX format. These are MS-DOS formatted floppies +whose master boot records have been altered so that they boot Linux directly +(or whatever other operating system has been defined in the syslinux.cfg file +on the floppy). Other scripts in this package produce emergency root disks and +can even reproduce the base disks. +

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +

+Yes. The kernel-image-NNN.prerm script checks to see whether the +kernel you are currently running is the same as the kernel you are trying to +de-install. Therefore you can remove unwanted kernel image packages using this +command: +

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

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-nexttime.en.html b/includes/common/doc/FAQ/html/ch-nexttime.en.html new file mode 100644 index 0000000..0c1d3ec --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-nexttime.en.html @@ -0,0 +1,149 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Changes expected in the next major release of Debian + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

14.1 Increased security

+ +

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

+ +

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

+ +
+ +

14.2 Extended support for non-English users

+ +

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

+ +

+We hope to find people who will provide support for even more languages, and +translate. Some programs already support internationalization, so we need +message catalogs translators. Many programs still remain to be properly +internationalized. +

+ +

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

+ +
+ +

14.3 More architectures

+ +

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

+ +
+ +

14.4 More kernels

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-nexttime.html b/includes/common/doc/FAQ/html/ch-nexttime.html new file mode 100644 index 0000000..0c1d3ec --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-nexttime.html @@ -0,0 +1,149 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Changes expected in the next major release of Debian + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

14.1 Increased security

+ +

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

+ +

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

+ +
+ +

14.2 Extended support for non-English users

+ +

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

+ +

+We hope to find people who will provide support for even more languages, and +translate. Some programs already support internationalization, so we need +message catalogs translators. Many programs still remain to be properly +internationalized. +

+ +

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

+ +
+ +

14.3 More architectures

+ +

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

+ +
+ +

14.4 More kernels

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-pkg_basics.en.html b/includes/common/doc/FAQ/html/ch-pkg_basics.en.html new file mode 100644 index 0000000..0ebd3fe --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-pkg_basics.en.html @@ -0,0 +1,860 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Basics of the Debian package management system + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

6.1 What is a Debian package?

+ +

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

+
    +
  • +

    +Binary packages, which contain executables, configuration files, +man/info pages, copyright information, and other documentation. These packages +are distributed in a Debian-specific archive format (see What is the format of a Debian binary package?, Section +6.2); they are usually distinguished by having a '.deb' file extension. +Binary packages can be unpacked using the Debian utility dpkg; +details are given in its manual page. +

    +
    • +
+
    +
  • +

    +Source packages, which consist of a .dsc file describing +the source package (including the names of the following files), a +.orig.tar.gz file that contains the original unmodified source in +gzip-compressed tar format and usually a .diff.gz file that +contains the Debian-specific changes to the original source. The utility +dpkg-source packs and unpacks Debian source archives; details are +provided in its manual page. +

    +
    • +
+ +

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

+ +

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

+
    +
  • +

    +manipulate and manage packages or parts of packages, +

    +
    • +
+
    +
  • +

    +aid the user in the break-up of packages that must be transmitted through a +limited-size medium such as floppy disks, +

    +
    • +
+
    +
  • +

    +aid developers in the construction of package archives, and +

    +
    • +
+
    +
  • +

    +aid users in the installation of packages which reside on a remote FTP site. +

    +
    • +
+ +
+ +

6.2 What is the format of a Debian binary package?

+ +

+A Debian "package", or a Debian archive file, contains the executable +files, libraries, and documentation associated with a particular suite of +program or set of related programs. Normally, a Debian archive file has a +filename that ends in .deb. +

+ +

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

+ +
+ +

6.3 Why are Debian package file names so long?

+ +

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

+ +

+Note that foo is supposed to be the package name. As a check, one +can learn the package name associated with a particular Debian archive file +(.deb file) in one of these ways: +

+
    +
  • +

    +inspect the "Packages" file in the directory where it was stored at a +Debian FTP archive site. This file contains a stanza describing each package; +the first field in each stanza is the formal package name. +

    +
    • +
+
    +
  • +

    +use the command dpkg --info foo_VVV-RRR.deb (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. +

    +
    • +
+ +

+The VVV component is the version number specified by the upstream +developer. There are no standards in place here, so the version number may +have formats as different as "19990513" and "1.3.8pre1". +

+ +

+The RRR component is the Debian revision number, and is specified +by the Debian developer (or an individual user if he chooses to build the +package himself). This number corresponds to the revision level of the Debian +package, thus, a new revision level usually signifies changes in the Debian +Makefile (debian/rules), the Debian control file +(debian/control), the installation or removal scripts +(debian/p*), or in the configuration files used with the package. +

+ +
+ +

6.4 What is a Debian control file?

+ +

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

+ +

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

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

+The Package field gives the package name. This is the name by which the +package can be manipulated by the package tools, and usually similar to but not +necessarily the same as the first component string in the Debian archive file +name. +

+ +

+The Version field gives both the upstream developer's version number and (in +the last component) the revision level of the Debian package of this program as +explained in Why are Debian package file names so long?, +Section 6.3. +

+ +

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

+ +

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

+ +

+The Installed-Size indicates how much disk space the installed package will +consume. This is intended to be used by installation front-ends in order to +show whether there is enough disk space available to install the program. +

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+ +
+ +

6.5 What is a Debian conffile?

+ +

+Conffiles is a list of configuration files (usually placed in +/etc) that the package management system will not overwrite when +the package is upgraded. This ensures that local values for the contents of +these files will be preserved, and is a critical feature enabling the in-place +upgrade of packages on a running system. +

+ +

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

+ +
+     dpkg --status package
+
+ +

+And look under "Conffiles:". +

+ +
+ +

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

+ +

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

+ +

+The individual files are: +

+
+
preinst
+
+

+This script executes before that package will be unpacked from its Debian +archive (".deb") file. Many 'preinst' scripts stop services for +packages which are being upgraded until their installation or upgrade is +completed (following the successful execution of the 'postinst' script). +

+
+
+
+
postinst
+
+

+This script typically completes any required configuration of the package +foo once foo has been unpacked from its Debian +archive (".deb") file. Often, 'postinst' scripts ask the user for +input, and/or warn the user that if he accepts default values, he should +remember to go back and re-configure that package as the situation warrants. +Many 'postinst' scripts then execute any commands necessary to start or restart +a service once a new package has been installed or upgraded. +

+
+
+
+
prerm
+
+

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

+
+
+
+
postrm
+
+

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

+
+
+ +

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

+ +
+ +

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

+ +

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

+
    +
  • +

    +Required: packages that are necessary for the proper +functioning of the system. +

    + +

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

    +
    • +
+
    +
  • +

    +Important packages should be found on any Unix-like system. +

    + +

    +Other packages which the system will not run well or be usable without will be +here. This does NOT include Emacs or X11 or TeX or any other large +applications. These packages only constitute the bare infrastructure. +

    +
    • +
+
    +
  • +

    +Standard packages are standard on any Linux system, including +a reasonably small but not too limited character-mode system. +

    + +

    +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 (gcc, g++), +GNU make, as well as the Python interpreter and some server software like +OpenSSH, the BSD printer daemon (lpr) and the RPC portmapper +(portmap). +

    +
    • +
+
    +
  • +

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

    + +

    +This includes X11, a full TeX distribution, and lots of applications. +

    +
    • +
+
    +
  • +

    +Extra: packages that either conflict with others with higher +priorities, are only likely to be useful if you already know what they are, or +have specialized requirements that make them unsuitable for +"Optional". +

    +
    • +
+ +

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

+ +

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

+ +
+ +

6.8 What is a Virtual Package?

+ +

+A virtual package is a generic name that applies to any one of a group of +packages, all of which provide similar basic functionality. For example, both +the tin and trn programs are news readers, and should +therefore satisfy any dependency of a program that required a news reader on a +system, in order to work or to be useful. They are therefore both said to +provide the "virtual package" called news-reader. +

+ +

+Similarly, smail and sendmail both provide the +functionality of a mail transport agent. They are therefore said to provide +the virtual package, "mail transport agent". If either one is +installed, then any program depending on the installation of a +mail-transport-agent will be satisfied by the existence of this +virtual package. +

+ +

+Debian provides a mechanism so that, if more than one package which provide the +same virtual package is installed on a system, then system administrators can +set one as the preferred package. The relevant command is +update-alternatives, and is described further in Some users like mawk, others like gawk; +some like vim, others like elvis; some like trn, others like tin; how does +Debian support diversity?, Section 10.10. +

+ +
+ +

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

+ +

+The Debian package system has a range of package "dependencies" which +are designed to indicate (in a single flag) the level at which Program A can +operate independently of the existence of Program B on a given system: +

+
    +
  • +

    +Package A depends 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. +

    +
    • +
+
    +
  • +

    +Package A recommends Package B, if the package maintainer judges that +most users would not want A without also having the functionality provided by +B. +

    +
    • +
+
    +
  • +

    +Package A suggests Package B if B contains files that are related to +(and usually enhance) the functionality of A. +

    +
    • +
+
    +
  • +

    +Package A conflicts with Package B when A will not operate if B is +installed on the system. Most often, conflicts are cases where A contains +files which are an improvement over those in B. "Conflicts" are +often combined with "replaces". +

    +
    • +
+
    +
  • +

    +Package A replaces Package B when files installed by B are removed and +(in some cases) over-written by files in A. +

    +
    • +
+
    +
  • +

    +Package A provides 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. +

    +
    • +
+ +

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

+ +
+ +

6.10 What is meant by Pre-Depends?

+ +

+"Pre-Depends" is a special dependency. In the case of most packages, +dpkg will unpack its archive file (i.e., its .deb +file) independently of whether or not the files on which it depends exist on +the system. Simplistically, unpacking means that dpkg will +extract the files from the archive file that were meant to be installed on your +file system, and put them in place. If those packages depend on the +existence of some other packages on your system, dpkg will refuse +to complete the installation (by executing its "configure" action) +until the other packages are installed. +

+ +

+However, for some packages, dpkg will refuse even to unpack them +until certain dependencies are resolved. Such packages are said to +"Pre-depend" on the presence of some other packages. The Debian +project provided this mechanism to support the safe upgrading of systems from +a.out format to ELF format, where the order +in which packages were unpacked was critical. There are other large upgrade +situations where this method is useful, e.g. the packages with the required +priority and their LibC dependency. +

+ +

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

+ +
+ +

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

+ +

+These "want" flags tell what the user wanted to do with a package (as +indicated either by the user's actions in the "Select" section of +dselect, or by the user's direct invocations of +dpkg). +

+ +

+Their meanings are: +

+
    +
  • +

    +unknown - the user has never indicated whether he wants the package +

    +
    • +
+
    +
  • +

    +install - the user wants the package installed or upgraded +

    +
    • +
+
    +
  • +

    +remove - the user wants the package removed, but does not want to remove any +existing configuration files. +

    +
    • +
+
    +
  • +

    +purge - the user wants the package to be removed completely, including its +configuration files. +

    +
    • +
+
    +
  • +

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

    +
    • +
+ +
+ +

6.12 How do I put a package on hold?

+ +

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

+ +

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

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

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

+ +
+     libc6                                           install
+
+ +

+to this: +

+ +
+     libc6                                           hold
+
+ +

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

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

+With aptitude, you can hold a package using +

+ +
+     aptitude hold package_name
+
+ +

+and remove the hold with +

+ +
+     aptitude unhold package_name
+
+ +

+With dselect, you just have to enter the [S]elect screen, find the package you +wish to hold in its present state, and press the `=' key (or `H'). The changes +will go live immediately after you exit the [S]elect screen. +

+ +
+ +

6.13 How do I install a source package?

+ +

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

+ +

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

+ +
+     apt-get source foo
+
+ +

+To help you in actually building the source package, Debian source package +provide the so-called build-dependencies mechanism. This means that the source +package maintainer keeps a list of other packages that are required to build +their package. To see how this is useful, run +

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

+before building the source. +

+ +
+ +

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

+ +

+You will need all of foo_*.dsc, foo_*.tar.gz and foo_*.diff.gz to compile the +source (note: there is no .diff.gz for some packages that are native to +Debian). +

+ +

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

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

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

+ +

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

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

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

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

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

+ +
+ +

6.15 How do I create Debian packages myself?

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-pkg_basics.html b/includes/common/doc/FAQ/html/ch-pkg_basics.html new file mode 100644 index 0000000..0ebd3fe --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-pkg_basics.html @@ -0,0 +1,860 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Basics of the Debian package management system + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

6.1 What is a Debian package?

+ +

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

+
    +
  • +

    +Binary packages, which contain executables, configuration files, +man/info pages, copyright information, and other documentation. These packages +are distributed in a Debian-specific archive format (see What is the format of a Debian binary package?, Section +6.2); they are usually distinguished by having a '.deb' file extension. +Binary packages can be unpacked using the Debian utility dpkg; +details are given in its manual page. +

    +
    • +
+
    +
  • +

    +Source packages, which consist of a .dsc file describing +the source package (including the names of the following files), a +.orig.tar.gz file that contains the original unmodified source in +gzip-compressed tar format and usually a .diff.gz file that +contains the Debian-specific changes to the original source. The utility +dpkg-source packs and unpacks Debian source archives; details are +provided in its manual page. +

    +
    • +
+ +

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

+ +

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

+
    +
  • +

    +manipulate and manage packages or parts of packages, +

    +
    • +
+
    +
  • +

    +aid the user in the break-up of packages that must be transmitted through a +limited-size medium such as floppy disks, +

    +
    • +
+
    +
  • +

    +aid developers in the construction of package archives, and +

    +
    • +
+
    +
  • +

    +aid users in the installation of packages which reside on a remote FTP site. +

    +
    • +
+ +
+ +

6.2 What is the format of a Debian binary package?

+ +

+A Debian "package", or a Debian archive file, contains the executable +files, libraries, and documentation associated with a particular suite of +program or set of related programs. Normally, a Debian archive file has a +filename that ends in .deb. +

+ +

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

+ +
+ +

6.3 Why are Debian package file names so long?

+ +

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

+ +

+Note that foo is supposed to be the package name. As a check, one +can learn the package name associated with a particular Debian archive file +(.deb file) in one of these ways: +

+
    +
  • +

    +inspect the "Packages" file in the directory where it was stored at a +Debian FTP archive site. This file contains a stanza describing each package; +the first field in each stanza is the formal package name. +

    +
    • +
+
    +
  • +

    +use the command dpkg --info foo_VVV-RRR.deb (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. +

    +
    • +
+ +

+The VVV component is the version number specified by the upstream +developer. There are no standards in place here, so the version number may +have formats as different as "19990513" and "1.3.8pre1". +

+ +

+The RRR component is the Debian revision number, and is specified +by the Debian developer (or an individual user if he chooses to build the +package himself). This number corresponds to the revision level of the Debian +package, thus, a new revision level usually signifies changes in the Debian +Makefile (debian/rules), the Debian control file +(debian/control), the installation or removal scripts +(debian/p*), or in the configuration files used with the package. +

+ +
+ +

6.4 What is a Debian control file?

+ +

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

+ +

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

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

+The Package field gives the package name. This is the name by which the +package can be manipulated by the package tools, and usually similar to but not +necessarily the same as the first component string in the Debian archive file +name. +

+ +

+The Version field gives both the upstream developer's version number and (in +the last component) the revision level of the Debian package of this program as +explained in Why are Debian package file names so long?, +Section 6.3. +

+ +

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

+ +

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

+ +

+The Installed-Size indicates how much disk space the installed package will +consume. This is intended to be used by installation front-ends in order to +show whether there is enough disk space available to install the program. +

+ +

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

+ +

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

+ +

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

+ +

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

+ +

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

+ +
+ +

6.5 What is a Debian conffile?

+ +

+Conffiles is a list of configuration files (usually placed in +/etc) that the package management system will not overwrite when +the package is upgraded. This ensures that local values for the contents of +these files will be preserved, and is a critical feature enabling the in-place +upgrade of packages on a running system. +

+ +

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

+ +
+     dpkg --status package
+
+ +

+And look under "Conffiles:". +

+ +
+ +

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

+ +

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

+ +

+The individual files are: +

+
+
preinst
+
+

+This script executes before that package will be unpacked from its Debian +archive (".deb") file. Many 'preinst' scripts stop services for +packages which are being upgraded until their installation or upgrade is +completed (following the successful execution of the 'postinst' script). +

+
+
+
+
postinst
+
+

+This script typically completes any required configuration of the package +foo once foo has been unpacked from its Debian +archive (".deb") file. Often, 'postinst' scripts ask the user for +input, and/or warn the user that if he accepts default values, he should +remember to go back and re-configure that package as the situation warrants. +Many 'postinst' scripts then execute any commands necessary to start or restart +a service once a new package has been installed or upgraded. +

+
+
+
+
prerm
+
+

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

+
+
+
+
postrm
+
+

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

+
+
+ +

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

+ +
+ +

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

+ +

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

+
    +
  • +

    +Required: packages that are necessary for the proper +functioning of the system. +

    + +

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

    +
    • +
+
    +
  • +

    +Important packages should be found on any Unix-like system. +

    + +

    +Other packages which the system will not run well or be usable without will be +here. This does NOT include Emacs or X11 or TeX or any other large +applications. These packages only constitute the bare infrastructure. +

    +
    • +
+
    +
  • +

    +Standard packages are standard on any Linux system, including +a reasonably small but not too limited character-mode system. +

    + +

    +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 (gcc, g++), +GNU make, as well as the Python interpreter and some server software like +OpenSSH, the BSD printer daemon (lpr) and the RPC portmapper +(portmap). +

    +
    • +
+
    +
  • +

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

    + +

    +This includes X11, a full TeX distribution, and lots of applications. +

    +
    • +
+
    +
  • +

    +Extra: packages that either conflict with others with higher +priorities, are only likely to be useful if you already know what they are, or +have specialized requirements that make them unsuitable for +"Optional". +

    +
    • +
+ +

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

+ +

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

+ +
+ +

6.8 What is a Virtual Package?

+ +

+A virtual package is a generic name that applies to any one of a group of +packages, all of which provide similar basic functionality. For example, both +the tin and trn programs are news readers, and should +therefore satisfy any dependency of a program that required a news reader on a +system, in order to work or to be useful. They are therefore both said to +provide the "virtual package" called news-reader. +

+ +

+Similarly, smail and sendmail both provide the +functionality of a mail transport agent. They are therefore said to provide +the virtual package, "mail transport agent". If either one is +installed, then any program depending on the installation of a +mail-transport-agent will be satisfied by the existence of this +virtual package. +

+ +

+Debian provides a mechanism so that, if more than one package which provide the +same virtual package is installed on a system, then system administrators can +set one as the preferred package. The relevant command is +update-alternatives, and is described further in Some users like mawk, others like gawk; +some like vim, others like elvis; some like trn, others like tin; how does +Debian support diversity?, Section 10.10. +

+ +
+ +

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

+ +

+The Debian package system has a range of package "dependencies" which +are designed to indicate (in a single flag) the level at which Program A can +operate independently of the existence of Program B on a given system: +

+
    +
  • +

    +Package A depends 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. +

    +
    • +
+
    +
  • +

    +Package A recommends Package B, if the package maintainer judges that +most users would not want A without also having the functionality provided by +B. +

    +
    • +
+
    +
  • +

    +Package A suggests Package B if B contains files that are related to +(and usually enhance) the functionality of A. +

    +
    • +
+
    +
  • +

    +Package A conflicts with Package B when A will not operate if B is +installed on the system. Most often, conflicts are cases where A contains +files which are an improvement over those in B. "Conflicts" are +often combined with "replaces". +

    +
    • +
+
    +
  • +

    +Package A replaces Package B when files installed by B are removed and +(in some cases) over-written by files in A. +

    +
    • +
+
    +
  • +

    +Package A provides 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. +

    +
    • +
+ +

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

+ +
+ +

6.10 What is meant by Pre-Depends?

+ +

+"Pre-Depends" is a special dependency. In the case of most packages, +dpkg will unpack its archive file (i.e., its .deb +file) independently of whether or not the files on which it depends exist on +the system. Simplistically, unpacking means that dpkg will +extract the files from the archive file that were meant to be installed on your +file system, and put them in place. If those packages depend on the +existence of some other packages on your system, dpkg will refuse +to complete the installation (by executing its "configure" action) +until the other packages are installed. +

+ +

+However, for some packages, dpkg will refuse even to unpack them +until certain dependencies are resolved. Such packages are said to +"Pre-depend" on the presence of some other packages. The Debian +project provided this mechanism to support the safe upgrading of systems from +a.out format to ELF format, where the order +in which packages were unpacked was critical. There are other large upgrade +situations where this method is useful, e.g. the packages with the required +priority and their LibC dependency. +

+ +

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

+ +
+ +

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

+ +

+These "want" flags tell what the user wanted to do with a package (as +indicated either by the user's actions in the "Select" section of +dselect, or by the user's direct invocations of +dpkg). +

+ +

+Their meanings are: +

+
    +
  • +

    +unknown - the user has never indicated whether he wants the package +

    +
    • +
+
    +
  • +

    +install - the user wants the package installed or upgraded +

    +
    • +
+
    +
  • +

    +remove - the user wants the package removed, but does not want to remove any +existing configuration files. +

    +
    • +
+
    +
  • +

    +purge - the user wants the package to be removed completely, including its +configuration files. +

    +
    • +
+
    +
  • +

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

    +
    • +
+ +
+ +

6.12 How do I put a package on hold?

+ +

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

+ +

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

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

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

+ +
+     libc6                                           install
+
+ +

+to this: +

+ +
+     libc6                                           hold
+
+ +

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

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

+With aptitude, you can hold a package using +

+ +
+     aptitude hold package_name
+
+ +

+and remove the hold with +

+ +
+     aptitude unhold package_name
+
+ +

+With dselect, you just have to enter the [S]elect screen, find the package you +wish to hold in its present state, and press the `=' key (or `H'). The changes +will go live immediately after you exit the [S]elect screen. +

+ +
+ +

6.13 How do I install a source package?

+ +

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

+ +

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

+ +
+     apt-get source foo
+
+ +

+To help you in actually building the source package, Debian source package +provide the so-called build-dependencies mechanism. This means that the source +package maintainer keeps a list of other packages that are required to build +their package. To see how this is useful, run +

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

+before building the source. +

+ +
+ +

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

+ +

+You will need all of foo_*.dsc, foo_*.tar.gz and foo_*.diff.gz to compile the +source (note: there is no .diff.gz for some packages that are native to +Debian). +

+ +

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

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

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

+ +

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

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

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

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

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

+ +
+ +

6.15 How do I create Debian packages myself?

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-pkgtools.en.html b/includes/common/doc/FAQ/html/ch-pkgtools.en.html new file mode 100644 index 0000000..114bb9f --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-pkgtools.en.html @@ -0,0 +1,936 @@ + + + + + + + + +The Debian GNU/Linux FAQ - The Debian package management tools + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

7.1 What programs does Debian provide for managing its packages?

+ +

+There are multiple tools that are used to manage Debian packages, from graphic +or text-based interfaces to the low level tools used to install packages. All +the available tools rely on the lower level tools to properly work and are +presented here in decreasing complexity level. +

+ +

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

+ +

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

+ +
+ +

7.1.1 dpkg

+ +

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

+
    +
  • +

    +Find out all the options: dpkg --help. +

    +
    • +
+
    +
  • +

    +Print out the control file (and other information) for a specified package: +dpkg --info foo_VVV-RRR.deb +

    +
    • +
+
    +
  • +

    +Install a package (including unpacking and configuring) onto the file system of +the hard disk: dpkg --install foo_VVV-RRR.deb. +

    +
    • +
+
    +
  • +

    +Unpack (but do not configure) a Debian archive into the file system of the hard +disk: dpkg --unpack foo_VVV-RRR.deb. Note that this operation +does not 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 What is a Debian preinst, postinst, +prerm, and postrm script?, Section 6.6) script associated with the package. +

    +
    • +
+
    +
  • +

    +Configure a package that already has been unpacked: dpkg --configure +foo. Among other things, this action runs the postinst (see What is a Debian preinst, postinst, +prerm, and postrm script?, Section 6.6) script associated with the package. +It also updates the files listed in the conffiles for this +package. Notice that the 'configure' operation takes as its argument a package +name (e.g., foo), not the name of a Debian archive file (e.g., +foo_VVV-RRR.deb). +

    +
    • +
+
    +
  • +

    +Extract a single file named "blurf" (or a group of files named +"blurf*" from a Debian archive: dpkg --fsys-tarfile +foo_VVV-RRR.deb | tar -xf - blurf* +

    +
    • +
+
    +
  • +

    +Remove a package (but not its configuration files): dpkg --remove +foo. +

    +
    • +
+
    +
  • +

    +Remove a package (including its configuration files): dpkg --purge +foo. +

    +
    • +
+
    +
  • +

    +List the installation status of packages containing the string (or regular +expression) "foo*": dpkg --list 'foo*'. +

    +
    • +
+ +
+ +

7.1.2 APT

+ +

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

+ +

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

+
    +
  • +

    +To update the list of package known by your system, you can run: +

    + +
    +     apt-get update
+
    + +

    +(you should execute this regularly to update your package lists) +

    +
    • +
+
    +
  • +

    +To upgrade all the packages on your system, run: +

    + +
    +     apt-get upgrade
+
    +
    • +
+
    +
  • +

    +To install the foo package and all its dependencies, run: +

    + +
    +     apt-get install foo
+
    +
    • +
+
    +
  • +

    +To remove the foo package from your system, run: +

    + +
    +     apt-get remove foo
+
    +
    • +
+
    +
  • +

    +To remove the foo package and its configuration files from your system, run: +

    + +
    +     apt-get --purge remove foo
+
    +
    • +
+
    +
  • +

    +To upgrade all the packages on your system to a new Debian GNU/Linux release, +run: +

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

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

+ +

+The apt tool suite also includes the apt-cache tool to query the +package lists. You can use it to find packages providing specific +functionality through simple text or regular expression queries and through +queries of dependencies in the package management system. Some common ways to +use apt-cache are: +

+
    +
  • +

    +To find packages whose description contain word: +

    + +
    +     apt-cache search word
+
    +
    • +
+
    +
  • +

    +To print the detailed information of a package: +

    + +
    +     apt-cache show package
+
    +
    • +
+
    +
  • +

    +To print the packages a given package depends on: +

    + +
    +     apt-cache depends package
+
    +
    • +
+
    +
  • +

    +To print detailed information of the versions available for a package and the +packages that reverse-depends on it: +

    + +
    +     apt-cache showpkg package
+
    +
    • +
+ +

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

+ +
+ +

7.1.3 aptitude

+ +

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

+ +

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

+
    +
  • +

    +aptitude offers access to all versions of a package. +

    +
    • +
+
    +
  • +

    +aptitude logs all its actions in /var/log/aptitude. +

    +
    • +
+
    +
  • +

    +aptitude makes it easy to keep track of obsolete software by +listing it under "Obsolete and Locally Created Packages". +

    +
    • +
+
    +
  • +

    +aptitude includes a fairly powerful system for searching +particular packages and limiting the package display. Users familiar with +mutt will pick up quickly, as mutt was the +inspiration for the expression syntax. +

    +
    • +
+
    +
  • +

    +aptitude tracks which packages have been installed due to +dependencies and removes them automatically when the packages that needed them +are removed from the system. +

    +
    • +
+
    +
  • +

    +aptitude can automatically install Recommended: +packages[5]. +

    +
    • +
+
    +
  • +

    +aptitude in full screen mode has su functionality +embedded and can be run by a normal user. It will call su (and +ask for the root password, if any) when you really need administrative +privileges +

    +
    • +
+ +

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

+ +

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

+ +

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

+ +
+ +

7.1.4 dselect

+ +

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

+ +

+dselect can: +

+
    +
  • +

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

    +
    • +
+
    +
  • +

    +warn the user about inconsistencies or incompatibilities in their selections; +

    +
    • +
+
    +
  • +

    +determine the order in which the packages must be installed; +

    +
    • +
+
    +
  • +

    +automatically perform the installation or removal; and +

    +
    • +
+
    +
  • +

    +guide the user through whatever configuration process are required for each +package. +

    +
    • +
+ +

+dselect begins by presenting the user with a menu of 7 items, each +of which is a specific action. The user can select one of the actions by using +the arrow keys to move the highlighter bar, then pressing the +<enter> key to select the highlighted action. +

+ +

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

+ +

+Both the Access menu item and the Select menu item +lead to additional menus. In both cases, the menus are presented as split +screens; the top screen gives a scrollable list of choices, while the bottom +screen gives a brief explanation ("info") for each choice. +

+ +

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

+ +

+The order in which the actions are presented in the first dselect +menu represents the order in which a user would normally choose +dselect to install packages. However, a user can pick any of the +main menu choices as often as needed (including not at all, depending on what +one wants to do). +

+
    +
  • +

    +Begin by choosing an Access Method. This is the method by +which the user plans on accessing Debian packages; e.g., some users have Debian +packages available on CD-ROM, while others plan to fetch them using anonymous +FTP. The selected "Access Method" is stored after +dselect exits, so if it does not change, then this option need not +be invoked again. +

    +
    • +
+
    +
  • +

    +Then Update the list of available packages. To do this, +dselect reads the file "Packages.gz" which should be +included in the top level of the directory where the Debian packages to be +installed are stored. (But if it is not there, dselect will offer +to make it for you.) +

    +
    • +
+
    +
  • +

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

    + +

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

    + +

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

    +
    +
    to be installed:
    +
    +

    +This is accomplished by pressing the `+' key. +

    +
    +
    +
    +
    to be deleted:
    +
    +

    +Packages can be deleted two ways: +

    +
      +
    • +

      +removed: this removes most of the files associated with the package, but +preserves the files listed as configuration files (see What is a Debian conffile?, Section +6.5) and package configuration information. This is done by pressing the +`-' key. +

      +
      • +
    +
      +
    • +

      +purged: this removes every file that is part of the package. This is +done by pressing the `_' key. +

      +
      • +
    + +

    +Note that it's not possible to remove "All Packages". If you try +that, your system will instead be reduced to the initial installed base +packages. +

    +
    +
    +
    +
    to be put "on hold"
    +
    +

    +This is done by pressing `=', and it effectively tells dselect 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 Access Method, and +acquired when you used Update). +

    + +

    +Just like you can put a package on hold, you can reverse such setting by +pressing `:'. That tells dselect that the package(s) may be +upgraded if a newer version is available. This is the default setting. +

    +
    +
    + +

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

    + +

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

    + +

    +If you select a package for installation or removal, e.g., +foo.deb, and that package depends on (or recommends) another +package, e.g., blurf.deb, then dselect 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. +

    +
    • +
+
    +
  • +

    +Users returning to the main menu can then select the "Install" menu +item to unpack and configure the selected packages. Alternatively, users +wishing to remove files can choose the "Remove" menu item. At any +point, users can choose "Quit" to exit dselect; users' selections are +preserved by dselect. +

    +
    • +
+ +
+ +

7.1.5 Other package management tools

+ +
+ +

7.1.5.1 dpkg-deb

+ +

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

+
    +
  • +

    +Find out all the options: dpkg-deb --help. +

    +
    • +
+
    +
  • +

    +Determine what files are contained in a Debian archive file: dpkg-deb +--contents foo_VVV-RRR.deb) +

    +
    • +
+
    +
  • +

    +Extract the files contained in a named Debian archive into a user specified +directory: dpkg-deb --extract foo_VVV-RRR.deb tmp extracts each of +the files in foo_VVV-RRR.deb into the directory tmp/. +This is convenient for examining the contents of a package in a localized +directory, without installing the package into the root file system. +

    +
    • +
+ +

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

+ +

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

+ +
+ +

7.1.5.2 dpkg-split

+ +

+This program splits large package into smaller files (e.g., for writing onto a +set of floppy disks), and can also be used to merge a set of split files back +into a single file. It can only be used on a Debian system (i.e. a system +containing the dpkg package), since it calls the program +dpkg-deb to parse the debian package file into its component +records. +

+ +

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

+
    +
  • +

    +Execute the command dpkg-split --split foo.deb. This will produce +N files each of approximately 460 KBytes long in the current directory. +

    +
    • +
+
    +
  • +

    +Copy those N files to floppy disks. +

    +
    • +
+
    +
  • +

    +Copy the contents of the floppy disks onto the hard disk of your choice on the +other machine. +

    +
    • +
+
    +
  • +

    +Join those part-files together using dpkg-split --join +"foo*". +

    +
    • +
+ +
+ +

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

+ +

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

+ +

+We also provide a program called start-stop-daemon which is used +to start daemons at boot time or to stop daemons when the kernel runlevel is +changed (e.g., from multi-user to single-user or to halt). The same program is +used by installation scripts when a new package containing a daemon is +installed, to stop running daemons, and restart them as necessary. +

+ +
+ +

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

+ +

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

+ +
+     dpkg --list
+
+ +

+This prints out a one-line summary for each package, giving a 2-letter status +symbol (explained in the header), the package name, the version which is +installed, and a brief description. +

+ +

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

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

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

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

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

+ +

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

+
    +
  • +

    +dpkg --search filename +

    + +

    +This searches for filename in installed packages. (This is +(currently) equivalent to searching all of the files having the file extension +of .list in the directory /var/lib/dpkg/info/, and +adjusting the output to print the names of all the packages containing it, and +diversions.) +

    + +

    +A faster alternative to this is the dlocate tool. +

    +
    • +
+
    +
  • +

    +zgrep foo Contents-ARCH.gz +

    + +

    +This searches for files which contain the substring foo in their +full path names. The files Contents-ARCH.gz (where ARCH +represents the wanted architecture) reside in the major package directories +(main, non-free, contrib) at a Debian FTP site (i.e. under +/debian/dists/sarge). A Contents file refers only to +the packages in the subdirectory tree where it resides. Therefore, a user +might have to search more than one Contents files to find the +package containing the file foo. +

    + +

    +This method has the advantage over dpkg --search in that it will +find files in packages that are not currently installed on your system. +

    +
    • +
+
    +
  • +

    +apt-file search foo +

    + +

    +Similar to the above, it searches files which contain the substring or regular +expression foo in their full path names. The advantage over the +sample above is that there is no need to retrieve the +Contents-ARCH.gz files as it will do this automatically for all +the sources defined in /etc/apt/sources.list when you run (as +root) apt-file update. +

    +
    • +
+ +
+ +

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

+ +

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

+ +

+Similar situations occur when dealing with libraries: generally these get +installed since packages containing applications depend on them. When the +application-package is purged, the library-package might stay on the system. +Or: when the application-package no longer depends upon e.g. libdb4.2, but +upon libdb4.3, the libdb4.2 package might stay when the application-package is +upgraded. +

+ +

+In these cases, `foo-data' doesn't depend on `foo', so when you remove the +`foo' package it will not get automatically removed by most package management +tools. The same holds true for the library packages. This is necessary to +avoid circular dependencies. If you use aptitude (see aptitude, Section 7.1.3) as your package management tool +it will, however, track automatically installed packages and remove them when +no packages remain that need them in your system. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-pkgtools.html b/includes/common/doc/FAQ/html/ch-pkgtools.html new file mode 100644 index 0000000..114bb9f --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-pkgtools.html @@ -0,0 +1,936 @@ + + + + + + + + +The Debian GNU/Linux FAQ - The Debian package management tools + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

7.1 What programs does Debian provide for managing its packages?

+ +

+There are multiple tools that are used to manage Debian packages, from graphic +or text-based interfaces to the low level tools used to install packages. All +the available tools rely on the lower level tools to properly work and are +presented here in decreasing complexity level. +

+ +

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

+ +

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

+ +
+ +

7.1.1 dpkg

+ +

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

+
    +
  • +

    +Find out all the options: dpkg --help. +

    +
    • +
+
    +
  • +

    +Print out the control file (and other information) for a specified package: +dpkg --info foo_VVV-RRR.deb +

    +
    • +
+
    +
  • +

    +Install a package (including unpacking and configuring) onto the file system of +the hard disk: dpkg --install foo_VVV-RRR.deb. +

    +
    • +
+
    +
  • +

    +Unpack (but do not configure) a Debian archive into the file system of the hard +disk: dpkg --unpack foo_VVV-RRR.deb. Note that this operation +does not 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 What is a Debian preinst, postinst, +prerm, and postrm script?, Section 6.6) script associated with the package. +

    +
    • +
+
    +
  • +

    +Configure a package that already has been unpacked: dpkg --configure +foo. Among other things, this action runs the postinst (see What is a Debian preinst, postinst, +prerm, and postrm script?, Section 6.6) script associated with the package. +It also updates the files listed in the conffiles for this +package. Notice that the 'configure' operation takes as its argument a package +name (e.g., foo), not the name of a Debian archive file (e.g., +foo_VVV-RRR.deb). +

    +
    • +
+
    +
  • +

    +Extract a single file named "blurf" (or a group of files named +"blurf*" from a Debian archive: dpkg --fsys-tarfile +foo_VVV-RRR.deb | tar -xf - blurf* +

    +
    • +
+
    +
  • +

    +Remove a package (but not its configuration files): dpkg --remove +foo. +

    +
    • +
+
    +
  • +

    +Remove a package (including its configuration files): dpkg --purge +foo. +

    +
    • +
+
    +
  • +

    +List the installation status of packages containing the string (or regular +expression) "foo*": dpkg --list 'foo*'. +

    +
    • +
+ +
+ +

7.1.2 APT

+ +

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

+ +

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

+
    +
  • +

    +To update the list of package known by your system, you can run: +

    + +
    +     apt-get update
+
    + +

    +(you should execute this regularly to update your package lists) +

    +
    • +
+
    +
  • +

    +To upgrade all the packages on your system, run: +

    + +
    +     apt-get upgrade
+
    +
    • +
+
    +
  • +

    +To install the foo package and all its dependencies, run: +

    + +
    +     apt-get install foo
+
    +
    • +
+
    +
  • +

    +To remove the foo package from your system, run: +

    + +
    +     apt-get remove foo
+
    +
    • +
+
    +
  • +

    +To remove the foo package and its configuration files from your system, run: +

    + +
    +     apt-get --purge remove foo
+
    +
    • +
+
    +
  • +

    +To upgrade all the packages on your system to a new Debian GNU/Linux release, +run: +

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

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

+ +

+The apt tool suite also includes the apt-cache tool to query the +package lists. You can use it to find packages providing specific +functionality through simple text or regular expression queries and through +queries of dependencies in the package management system. Some common ways to +use apt-cache are: +

+
    +
  • +

    +To find packages whose description contain word: +

    + +
    +     apt-cache search word
+
    +
    • +
+
    +
  • +

    +To print the detailed information of a package: +

    + +
    +     apt-cache show package
+
    +
    • +
+
    +
  • +

    +To print the packages a given package depends on: +

    + +
    +     apt-cache depends package
+
    +
    • +
+
    +
  • +

    +To print detailed information of the versions available for a package and the +packages that reverse-depends on it: +

    + +
    +     apt-cache showpkg package
+
    +
    • +
+ +

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

+ +
+ +

7.1.3 aptitude

+ +

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

+ +

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

+
    +
  • +

    +aptitude offers access to all versions of a package. +

    +
    • +
+
    +
  • +

    +aptitude logs all its actions in /var/log/aptitude. +

    +
    • +
+
    +
  • +

    +aptitude makes it easy to keep track of obsolete software by +listing it under "Obsolete and Locally Created Packages". +

    +
    • +
+
    +
  • +

    +aptitude includes a fairly powerful system for searching +particular packages and limiting the package display. Users familiar with +mutt will pick up quickly, as mutt was the +inspiration for the expression syntax. +

    +
    • +
+
    +
  • +

    +aptitude tracks which packages have been installed due to +dependencies and removes them automatically when the packages that needed them +are removed from the system. +

    +
    • +
+
    +
  • +

    +aptitude can automatically install Recommended: +packages[5]. +

    +
    • +
+
    +
  • +

    +aptitude in full screen mode has su functionality +embedded and can be run by a normal user. It will call su (and +ask for the root password, if any) when you really need administrative +privileges +

    +
    • +
+ +

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

+ +

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

+ +

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

+ +
+ +

7.1.4 dselect

+ +

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

+ +

+dselect can: +

+
    +
  • +

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

    +
    • +
+
    +
  • +

    +warn the user about inconsistencies or incompatibilities in their selections; +

    +
    • +
+
    +
  • +

    +determine the order in which the packages must be installed; +

    +
    • +
+
    +
  • +

    +automatically perform the installation or removal; and +

    +
    • +
+
    +
  • +

    +guide the user through whatever configuration process are required for each +package. +

    +
    • +
+ +

+dselect begins by presenting the user with a menu of 7 items, each +of which is a specific action. The user can select one of the actions by using +the arrow keys to move the highlighter bar, then pressing the +<enter> key to select the highlighted action. +

+ +

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

+ +

+Both the Access menu item and the Select menu item +lead to additional menus. In both cases, the menus are presented as split +screens; the top screen gives a scrollable list of choices, while the bottom +screen gives a brief explanation ("info") for each choice. +

+ +

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

+ +

+The order in which the actions are presented in the first dselect +menu represents the order in which a user would normally choose +dselect to install packages. However, a user can pick any of the +main menu choices as often as needed (including not at all, depending on what +one wants to do). +

+
    +
  • +

    +Begin by choosing an Access Method. This is the method by +which the user plans on accessing Debian packages; e.g., some users have Debian +packages available on CD-ROM, while others plan to fetch them using anonymous +FTP. The selected "Access Method" is stored after +dselect exits, so if it does not change, then this option need not +be invoked again. +

    +
    • +
+
    +
  • +

    +Then Update the list of available packages. To do this, +dselect reads the file "Packages.gz" which should be +included in the top level of the directory where the Debian packages to be +installed are stored. (But if it is not there, dselect will offer +to make it for you.) +

    +
    • +
+
    +
  • +

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

    + +

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

    + +

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

    +
    +
    to be installed:
    +
    +

    +This is accomplished by pressing the `+' key. +

    +
    +
    +
    +
    to be deleted:
    +
    +

    +Packages can be deleted two ways: +

    +
      +
    • +

      +removed: this removes most of the files associated with the package, but +preserves the files listed as configuration files (see What is a Debian conffile?, Section +6.5) and package configuration information. This is done by pressing the +`-' key. +

      +
      • +
    +
      +
    • +

      +purged: this removes every file that is part of the package. This is +done by pressing the `_' key. +

      +
      • +
    + +

    +Note that it's not possible to remove "All Packages". If you try +that, your system will instead be reduced to the initial installed base +packages. +

    +
    +
    +
    +
    to be put "on hold"
    +
    +

    +This is done by pressing `=', and it effectively tells dselect 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 Access Method, and +acquired when you used Update). +

    + +

    +Just like you can put a package on hold, you can reverse such setting by +pressing `:'. That tells dselect that the package(s) may be +upgraded if a newer version is available. This is the default setting. +

    +
    +
    + +

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

    + +

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

    + +

    +If you select a package for installation or removal, e.g., +foo.deb, and that package depends on (or recommends) another +package, e.g., blurf.deb, then dselect 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. +

    +
    • +
+
    +
  • +

    +Users returning to the main menu can then select the "Install" menu +item to unpack and configure the selected packages. Alternatively, users +wishing to remove files can choose the "Remove" menu item. At any +point, users can choose "Quit" to exit dselect; users' selections are +preserved by dselect. +

    +
    • +
+ +
+ +

7.1.5 Other package management tools

+ +
+ +

7.1.5.1 dpkg-deb

+ +

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

+
    +
  • +

    +Find out all the options: dpkg-deb --help. +

    +
    • +
+
    +
  • +

    +Determine what files are contained in a Debian archive file: dpkg-deb +--contents foo_VVV-RRR.deb) +

    +
    • +
+
    +
  • +

    +Extract the files contained in a named Debian archive into a user specified +directory: dpkg-deb --extract foo_VVV-RRR.deb tmp extracts each of +the files in foo_VVV-RRR.deb into the directory tmp/. +This is convenient for examining the contents of a package in a localized +directory, without installing the package into the root file system. +

    +
    • +
+ +

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

+ +

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

+ +
+ +

7.1.5.2 dpkg-split

+ +

+This program splits large package into smaller files (e.g., for writing onto a +set of floppy disks), and can also be used to merge a set of split files back +into a single file. It can only be used on a Debian system (i.e. a system +containing the dpkg package), since it calls the program +dpkg-deb to parse the debian package file into its component +records. +

+ +

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

+
    +
  • +

    +Execute the command dpkg-split --split foo.deb. This will produce +N files each of approximately 460 KBytes long in the current directory. +

    +
    • +
+
    +
  • +

    +Copy those N files to floppy disks. +

    +
    • +
+
    +
  • +

    +Copy the contents of the floppy disks onto the hard disk of your choice on the +other machine. +

    +
    • +
+
    +
  • +

    +Join those part-files together using dpkg-split --join +"foo*". +

    +
    • +
+ +
+ +

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

+ +

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

+ +

+We also provide a program called start-stop-daemon which is used +to start daemons at boot time or to stop daemons when the kernel runlevel is +changed (e.g., from multi-user to single-user or to halt). The same program is +used by installation scripts when a new package containing a daemon is +installed, to stop running daemons, and restart them as necessary. +

+ +
+ +

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

+ +

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

+ +
+     dpkg --list
+
+ +

+This prints out a one-line summary for each package, giving a 2-letter status +symbol (explained in the header), the package name, the version which is +installed, and a brief description. +

+ +

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

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

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

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

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

+ +

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

+
    +
  • +

    +dpkg --search filename +

    + +

    +This searches for filename in installed packages. (This is +(currently) equivalent to searching all of the files having the file extension +of .list in the directory /var/lib/dpkg/info/, and +adjusting the output to print the names of all the packages containing it, and +diversions.) +

    + +

    +A faster alternative to this is the dlocate tool. +

    +
    • +
+
    +
  • +

    +zgrep foo Contents-ARCH.gz +

    + +

    +This searches for files which contain the substring foo in their +full path names. The files Contents-ARCH.gz (where ARCH +represents the wanted architecture) reside in the major package directories +(main, non-free, contrib) at a Debian FTP site (i.e. under +/debian/dists/sarge). A Contents file refers only to +the packages in the subdirectory tree where it resides. Therefore, a user +might have to search more than one Contents files to find the +package containing the file foo. +

    + +

    +This method has the advantage over dpkg --search in that it will +find files in packages that are not currently installed on your system. +

    +
    • +
+
    +
  • +

    +apt-file search foo +

    + +

    +Similar to the above, it searches files which contain the substring or regular +expression foo in their full path names. The advantage over the +sample above is that there is no need to retrieve the +Contents-ARCH.gz files as it will do this automatically for all +the sources defined in /etc/apt/sources.list when you run (as +root) apt-file update. +

    +
    • +
+ +
+ +

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

+ +

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

+ +

+Similar situations occur when dealing with libraries: generally these get +installed since packages containing applications depend on them. When the +application-package is purged, the library-package might stay on the system. +Or: when the application-package no longer depends upon e.g. libdb4.2, but +upon libdb4.3, the libdb4.2 package might stay when the application-package is +upgraded. +

+ +

+In these cases, `foo-data' doesn't depend on `foo', so when you remove the +`foo' package it will not get automatically removed by most package management +tools. The same holds true for the library packages. This is necessary to +avoid circular dependencies. If you use aptitude (see aptitude, Section 7.1.3) as your package management tool +it will, however, track automatically installed packages and remove them when +no packages remain that need them in your system. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-redistrib.en.html b/includes/common/doc/FAQ/html/ch-redistrib.en.html new file mode 100644 index 0000000..f0ac5d0 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-redistrib.en.html @@ -0,0 +1,170 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Redistributing Debian GNU/Linux in a commercial product + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

13.1 Can I make and sell Debian CDs?

+ +

+Go ahead. You do not need permission to distribute anything we have +released, so that you can master your CD as soon as the beta-test +ends. You do not have to pay us anything. Of course, all CD manufacturers +must honor the licenses of the programs in Debian. For example, many of the +programs are licensed under the GPL, which requires you to distribute their +source code. +

+ +

+Also, we will publish a list of CD manufacturers who donate money, software, +and time to the Debian project, and we will encourage users to buy from +manufacturers who donate, so it is good advertising to make donations. +

+ +
+ +

13.2 Can Debian be packaged with non-free software?

+ +

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

+ +

+CD manufacturers may be able to distribute the programs we have placed +in that directory, depending on the license terms or their private arrangements +with the authors of those software packages. CD manufacturers can also +distribute the non-free software they get from other sources on the same CD. +This is nothing new: free and commercial software are distributed on the same +CD by many manufacturers now. Of course we still encourage software authors to +release the programs they write as free software. +

+ +
+ +

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

+ +

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

+ +

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

+ +

+There are several other Debian-derived distributions already on the market, +such as Progeny Debian, Linspire, Knoppix and Ubuntu, that are targeted at a +different kind of audience than the original Debian GNU/Linux is, but use most +of our components in their product. +

+ +

+Debian also provides a mechanism to allow developers and system administrators +to install local versions of selected files in such a way that they will not be +overwritten when other packages are upgraded. This is discussed further in the +question on How do I override a file +installed by a package, so that a different version can be used instead?, +Section 10.8. +

+ +
+ +

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

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-redistrib.html b/includes/common/doc/FAQ/html/ch-redistrib.html new file mode 100644 index 0000000..f0ac5d0 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-redistrib.html @@ -0,0 +1,170 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Redistributing Debian GNU/Linux in a commercial product + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

13.1 Can I make and sell Debian CDs?

+ +

+Go ahead. You do not need permission to distribute anything we have +released, so that you can master your CD as soon as the beta-test +ends. You do not have to pay us anything. Of course, all CD manufacturers +must honor the licenses of the programs in Debian. For example, many of the +programs are licensed under the GPL, which requires you to distribute their +source code. +

+ +

+Also, we will publish a list of CD manufacturers who donate money, software, +and time to the Debian project, and we will encourage users to buy from +manufacturers who donate, so it is good advertising to make donations. +

+ +
+ +

13.2 Can Debian be packaged with non-free software?

+ +

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

+ +

+CD manufacturers may be able to distribute the programs we have placed +in that directory, depending on the license terms or their private arrangements +with the authors of those software packages. CD manufacturers can also +distribute the non-free software they get from other sources on the same CD. +This is nothing new: free and commercial software are distributed on the same +CD by many manufacturers now. Of course we still encourage software authors to +release the programs they write as free software. +

+ +
+ +

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

+ +

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

+ +

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

+ +

+There are several other Debian-derived distributions already on the market, +such as Progeny Debian, Linspire, Knoppix and Ubuntu, that are targeted at a +different kind of audience than the original Debian GNU/Linux is, but use most +of our components in their product. +

+ +

+Debian also provides a mechanism to allow developers and system administrators +to install local versions of selected files in such a way that they will not be +overwritten when other packages are upgraded. This is discussed further in the +question on How do I override a file +installed by a package, so that a different version can be used instead?, +Section 10.8. +

+ +
+ +

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

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-software.en.html b/includes/common/doc/FAQ/html/ch-software.en.html new file mode 100644 index 0000000..bedb65f --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-software.en.html @@ -0,0 +1,410 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Software available in the Debian system + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

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

+
    +
  • +

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

    +
    • +
+
    +
  • +

    +Perl, Python, Tcl/Tk and various related programs, modules and libraries for +each of them, +

    +
    • +
+
    +
  • +

    +TeX (LaTeX) and Lyx, dvips, Ghostscript, +

    +
    • +
+
    +
  • +

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

    +
    • +
+
    +
  • +

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

    +
    • +
+
    +
  • +

    +a complete set of office applications, including the OpenOffice.org +productivity suite, Gnumeric and other spreadsheets, WYSIWYG editors, +calendars. +

    +
    • +
+ +

+More than 15180 packages, ranging from news servers and readers to sound +support, FAX programs, database and spreadsheet programs, image processing +programs, communications, net, and mail utilities, Web servers, and even +ham-radio programs are included in the distribution. Another 450 software +suites are available as Debian packages, but are not formally part of Debian +due to license restrictions. +

+ +
+ +

4.2 Who wrote all that software?

+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +
+ +

4.4 What is missing from Debian GNU/Linux?

+ +

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

+ +

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

+ +
+ +

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

+ +

+Debian Policy requires that such symbolic links (to libfoo.so.x.y.z or similar) +are placed in separate, development packages. Those packages are usually named +libfoo-dev or libfooX-dev (presuming the library package is named libfooX, and +X is a whole number). +

+ +
+ +

4.6 (How) Does Debian support Java?

+ +

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

+ +

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

+ +

+Running a Java applet requires a web browser with the capability to recognize +and execute them. Several web browsers available in Debian, such as Mozilla or +Konqueror, support Java plug-ins that enable running Java applets within them. +Netscape Navigator, while non-free, is also available as a Debian package and +it can run Java applets. +

+ +

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

+ +
+ +

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

+ +

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

+ +

+The existence of the program dpkg shows that you should be able to +install Debian packages on your system, but as the program has been ported to +many other operating systems and architectures, this is no longer a reliable +method of determining is a system Debian GNU/Linux. +

+ +

+Users should be aware, however, that the Debian system consists of many parts, +each of which can be updated (almost) independently. Each Debian +"release" contains well defined and unchanging contents. Updates are +separately available. For a one-line description of the installation status of +package foo, use the command dpkg --list foo. To +view versions of all installed packages, run: +

+ +
+     dpkg -l
+
+ +

+For a more verbose description, use: +

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

4.8 How does Debian support non-English languages?

+
    +
  • +

    +Debian GNU/Linux is distributed with keymaps for nearly two dozen keyboards, +and with utilities (in the kbd package) to install, view, and +modify the tables. +

    + +

    +The installation prompts the user to specify the keyboard he will use. +

    +
    • +
+
    +
  • +

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

    +
    • +
+
    +
  • +

    +Currently, support for German-, Spanish-, Finnish-, French-, Hungarian-, +Italian-, Japanese-, Korean- and Polish-language manual pages is provided +through the manpages-LANG 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. +

    + +

    +For example, in the case of the Italian-language manual pages, LC_MESSAGES +needs to be set to 'italian'. The man program will then search +for Italian manual pages under /usr/share/man/it/. +

    +
    • +
+ +
+ +

4.9 What about the US export regulation limitations?

+ +

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

+ +

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

+ +
+ +

4.10 Where is pine?

+ +

+Due to its restrictive license, it's in the non-free area. Moreover, since +license does not even allow modified binaries to be distributed, you have to +compile it yourself from the source and the Debian patches. +

+ +

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

+ +

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

+ +
+ +

4.11 Where is qmail/ezmlm/djbdns?

+ +

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

+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-software.html b/includes/common/doc/FAQ/html/ch-software.html new file mode 100644 index 0000000..bedb65f --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-software.html @@ -0,0 +1,410 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Software available in the Debian system + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +

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

+
    +
  • +

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

    +
    • +
+
    +
  • +

    +Perl, Python, Tcl/Tk and various related programs, modules and libraries for +each of them, +

    +
    • +
+
    +
  • +

    +TeX (LaTeX) and Lyx, dvips, Ghostscript, +

    +
    • +
+
    +
  • +

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

    +
    • +
+
    +
  • +

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

    +
    • +
+
    +
  • +

    +a complete set of office applications, including the OpenOffice.org +productivity suite, Gnumeric and other spreadsheets, WYSIWYG editors, +calendars. +

    +
    • +
+ +

+More than 15180 packages, ranging from news servers and readers to sound +support, FAX programs, database and spreadsheet programs, image processing +programs, communications, net, and mail utilities, Web servers, and even +ham-radio programs are included in the distribution. Another 450 software +suites are available as Debian packages, but are not formally part of Debian +due to license restrictions. +

+ +
+ +

4.2 Who wrote all that software?

+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +

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

+ +
+ +

4.4 What is missing from Debian GNU/Linux?

+ +

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

+ +

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

+ +
+ +

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

+ +

+Debian Policy requires that such symbolic links (to libfoo.so.x.y.z or similar) +are placed in separate, development packages. Those packages are usually named +libfoo-dev or libfooX-dev (presuming the library package is named libfooX, and +X is a whole number). +

+ +
+ +

4.6 (How) Does Debian support Java?

+ +

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

+ +

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

+ +

+Running a Java applet requires a web browser with the capability to recognize +and execute them. Several web browsers available in Debian, such as Mozilla or +Konqueror, support Java plug-ins that enable running Java applets within them. +Netscape Navigator, while non-free, is also available as a Debian package and +it can run Java applets. +

+ +

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

+ +
+ +

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

+ +

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

+ +

+The existence of the program dpkg shows that you should be able to +install Debian packages on your system, but as the program has been ported to +many other operating systems and architectures, this is no longer a reliable +method of determining is a system Debian GNU/Linux. +

+ +

+Users should be aware, however, that the Debian system consists of many parts, +each of which can be updated (almost) independently. Each Debian +"release" contains well defined and unchanging contents. Updates are +separately available. For a one-line description of the installation status of +package foo, use the command dpkg --list foo. To +view versions of all installed packages, run: +

+ +
+     dpkg -l
+
+ +

+For a more verbose description, use: +

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

4.8 How does Debian support non-English languages?

+
    +
  • +

    +Debian GNU/Linux is distributed with keymaps for nearly two dozen keyboards, +and with utilities (in the kbd package) to install, view, and +modify the tables. +

    + +

    +The installation prompts the user to specify the keyboard he will use. +

    +
    • +
+
    +
  • +

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

    +
    • +
+
    +
  • +

    +Currently, support for German-, Spanish-, Finnish-, French-, Hungarian-, +Italian-, Japanese-, Korean- and Polish-language manual pages is provided +through the manpages-LANG 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. +

    + +

    +For example, in the case of the Italian-language manual pages, LC_MESSAGES +needs to be set to 'italian'. The man program will then search +for Italian manual pages under /usr/share/man/it/. +

    +
    • +
+ +
+ +

4.9 What about the US export regulation limitations?

+ +

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

+ +

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

+ +
+ +

4.10 Where is pine?

+ +

+Due to its restrictive license, it's in the non-free area. Moreover, since +license does not even allow modified binaries to be distributed, you have to +compile it yourself from the source and the Debian patches. +

+ +

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

+ +

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

+ +
+ +

4.11 Where is qmail/ezmlm/djbdns?

+ +

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

+ +

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

+ +

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

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-support.en.html b/includes/common/doc/FAQ/html/ch-support.en.html new file mode 100644 index 0000000..57e21da --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-support.en.html @@ -0,0 +1,525 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Getting support for Debian GNU/Linux + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
    +
  • +

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

    + +

    +Get it from the debian-reference package, or at http://www.debian.org/doc/user-manuals#quick-reference. +

    +
    • +
+
    +
  • +

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

    + +

    +Get it from the debian-policy package, or at http://www.debian.org/doc/devel-manuals#policy. +

    +
    • +
+
    +
  • +

    +Documentation developed by the Debian Documentation Project. It is available +at http://www.debian.org/doc/ and +includes user guides, administration guides and security guides for the Debian +GNU/Linux operating system. +

    +
    • +
+
    +
  • +

    +Documentation on installed Debian packages: Most packages have files that are +unpacked into /usr/share/doc/PACKAGE. +

    +
    • +
+
    +
  • +

    +Documentation on the Linux project: The Debian package doc-linux +installs all of the most recent versions of the HOWTOs and mini-HOWTOs from the +Linux Documentation Project. +

    +
    • +
+
    +
  • +

    +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: +man 3 foo, or just man foo if section 3 is the first +one containing a page on foo. +

    + +

    +One can learn which directory of /usr/share/man/ contains a +certain manual page by executing man -w foo. +

    + +

    +New Debian users should note that the 'man' pages of many general system +commands are not available until they install these packages: +

    +
      +
    • +

      +man-db, which contains the man program itself, and +other programs for manipulating the manual pages. +

      +
      • +
    + +
    • +
+
    +
  • +

    +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 info, by running M-x info within GNU +Emacs, or with some other Info page viewer. +

    + +

    +Its main advantage over the original `man' pages are that it is a hypertext +system. It does not require the WWW, however; info can +be run from a plain text console. It was designed by Richard Stallman and +preceded the WWW. +

    +
    • +
+ +

+Note that you may access a lot of documentation on your system by using a WWW +browser, through `dwww', `dhelp' or `doccentral' commands, found in respective +packages. +

+ +
+ +

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

+ +

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

+ +
+ +

11.2.1 Mailing lists

+ +

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

+ +

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

+ +

+Debian mailing lists are named following the pattern +debian-list-subject. Examples are debian-announce, debian-user, +debian-news. To subscribe to any list debian-list-subject, send +mail to debian-list-subject-request@lists.debian.org with the word +"subscribe" in the Subject: header. Be sure to remember to add +-request to the e-mail address when using this method to subscribe or +unsubscribe. Otherwise your e-mail will go to the list itself, which could be +embarrassing or annoying, depending on your point of view. +

+ +

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

+ +

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

+ +

+The mailing lists are public forums. All e-mails sent to the lists are also +copied to the public archive, for anybody (even non-subscribers) to browse or +search. Please make sure you never send any confidential or unlicensed +material to the lists. This includes things like e-mail addresses. Of +particular note is the fact that spammers have been known to abuse e-mail +addresses posted to our mailing lists. See the Mailing +Lists Privacy policy for more information. +

+ +

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

+ +
+ +

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

+ +

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

+ +
    +
  • +

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

    +
    • +
+
    +
  • +

    +Do not use foul language; besides, some people receive the lists via packet +radio, where swearing is illegal. +

    +
    • +
+
    +
  • +

    +Make sure that you are using the proper list. Never post your +(un)subscription requests to the mailing list itself[6] +

    +
    • +
+ + +
+ +

11.2.2 Maintainers

+ +

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

+ +
+ +

11.2.3 Usenet newsgroups

+ +

+Users should post non-Debian-specific questions to one of the Linux USENET +groups, which are named comp.os.linux.* or linux.*. There are several lists of +Linux Usenet newsgroups and other related resources on the WWW, e.g. on the +Linux Online +and LinuxJournal sites. +

+ +
+ +

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

+ +

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

+ +
    +
  • +

    +Google Groups: a search +engine for newsgroups. +

    + +

    +For example, to find out what experiences people have had with finding drivers +for Promise controllers under Debian, try searching on the phrase Promise +Linux driver. This will show you all the postings that contain these +strings, i.e. those where people discussed these topics. If you add +Debian to those search strings, you'll also get the postings +specifically related to Debian. +

    +
    • +
+
    +
  • +

    +Any of the common web spidering engines, such as AltaVista or Google, as long as you use the right +search terms. +

    + +

    +For example, searching on the string "cgi-perl" gives a more detailed +explanation of this package than the brief description field in its control +file. +

    +
    • +
+ +
+ +

11.4 Are there logs of known bugs?

+ +

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

+ +

+The Debian GNU/Linux distribution has a bug tracking system (BTS) which files +details of bugs reported by users and developers. Each bug is given a number, +and is kept on file until it is marked as having been dealt with. +

+ +

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

+ +

+A mail server provides access to the bug tracking system database via e-mail. +In order to get the instructions, send an e-mail to request@bugs.debian.org +with "help" in the body. +

+ +
+ +

11.5 How do I report a bug in Debian?

+ +

+If you have found a bug in Debian, please read the instructions for reporting a +bug in Debian. These instructions can be obtained in one of several ways: +

+
    +
  • +

    +By anonymous FTP. Debian mirror sites contain the instructions in the file +doc/bug-reporting.txt. +

    +
    • +
+ +
    +
  • +

    +On any Debian system with the doc-debian package installed. The +instructions are in the file +/usr/share/doc/debian/bug-reporting.txt. +

    +
    • +
+ +

+You can use the package reportbug that will guide you through the +reporting process and mail the message to the proper address, with some extra +details about your system added automatically. It will also show you a list of +bugs already reported to the package you are reporting against in case your bug +has been reported previously, so that you can additional information to the +existing bug report. +

+ +

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

+ +
+     Package: package-name
+
+ +

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

+ +
+     Version: version-number
+
+ +

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

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

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

+ +
+     cat /etc/debian_version
+
+ +

+Expect to get an automatic acknowledgement of your bug report. It will also be +automatically given a bug tracking number, entered into the bug log and +forwarded to the debian-bugs-dist mailing list. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-support.html b/includes/common/doc/FAQ/html/ch-support.html new file mode 100644 index 0000000..57e21da --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-support.html @@ -0,0 +1,525 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Getting support for Debian GNU/Linux + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

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

+ +
    +
  • +

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

    + +

    +Get it from the debian-reference package, or at http://www.debian.org/doc/user-manuals#quick-reference. +

    +
    • +
+
    +
  • +

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

    + +

    +Get it from the debian-policy package, or at http://www.debian.org/doc/devel-manuals#policy. +

    +
    • +
+
    +
  • +

    +Documentation developed by the Debian Documentation Project. It is available +at http://www.debian.org/doc/ and +includes user guides, administration guides and security guides for the Debian +GNU/Linux operating system. +

    +
    • +
+
    +
  • +

    +Documentation on installed Debian packages: Most packages have files that are +unpacked into /usr/share/doc/PACKAGE. +

    +
    • +
+
    +
  • +

    +Documentation on the Linux project: The Debian package doc-linux +installs all of the most recent versions of the HOWTOs and mini-HOWTOs from the +Linux Documentation Project. +

    +
    • +
+
    +
  • +

    +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: +man 3 foo, or just man foo if section 3 is the first +one containing a page on foo. +

    + +

    +One can learn which directory of /usr/share/man/ contains a +certain manual page by executing man -w foo. +

    + +

    +New Debian users should note that the 'man' pages of many general system +commands are not available until they install these packages: +

    +
      +
    • +

      +man-db, which contains the man program itself, and +other programs for manipulating the manual pages. +

      +
      • +
    + +
    • +
+
    +
  • +

    +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 info, by running M-x info within GNU +Emacs, or with some other Info page viewer. +

    + +

    +Its main advantage over the original `man' pages are that it is a hypertext +system. It does not require the WWW, however; info can +be run from a plain text console. It was designed by Richard Stallman and +preceded the WWW. +

    +
    • +
+ +

+Note that you may access a lot of documentation on your system by using a WWW +browser, through `dwww', `dhelp' or `doccentral' commands, found in respective +packages. +

+ +
+ +

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

+ +

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

+ +
+ +

11.2.1 Mailing lists

+ +

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

+ +

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

+ +

+Debian mailing lists are named following the pattern +debian-list-subject. Examples are debian-announce, debian-user, +debian-news. To subscribe to any list debian-list-subject, send +mail to debian-list-subject-request@lists.debian.org with the word +"subscribe" in the Subject: header. Be sure to remember to add +-request to the e-mail address when using this method to subscribe or +unsubscribe. Otherwise your e-mail will go to the list itself, which could be +embarrassing or annoying, depending on your point of view. +

+ +

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

+ +

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

+ +

+The mailing lists are public forums. All e-mails sent to the lists are also +copied to the public archive, for anybody (even non-subscribers) to browse or +search. Please make sure you never send any confidential or unlicensed +material to the lists. This includes things like e-mail addresses. Of +particular note is the fact that spammers have been known to abuse e-mail +addresses posted to our mailing lists. See the Mailing +Lists Privacy policy for more information. +

+ +

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

+ +
+ +

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

+ +

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

+ +
    +
  • +

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

    +
    • +
+
    +
  • +

    +Do not use foul language; besides, some people receive the lists via packet +radio, where swearing is illegal. +

    +
    • +
+
    +
  • +

    +Make sure that you are using the proper list. Never post your +(un)subscription requests to the mailing list itself[6] +

    +
    • +
+ + +
+ +

11.2.2 Maintainers

+ +

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

+ +
+ +

11.2.3 Usenet newsgroups

+ +

+Users should post non-Debian-specific questions to one of the Linux USENET +groups, which are named comp.os.linux.* or linux.*. There are several lists of +Linux Usenet newsgroups and other related resources on the WWW, e.g. on the +Linux Online +and LinuxJournal sites. +

+ +
+ +

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

+ +

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

+ +
    +
  • +

    +Google Groups: a search +engine for newsgroups. +

    + +

    +For example, to find out what experiences people have had with finding drivers +for Promise controllers under Debian, try searching on the phrase Promise +Linux driver. This will show you all the postings that contain these +strings, i.e. those where people discussed these topics. If you add +Debian to those search strings, you'll also get the postings +specifically related to Debian. +

    +
    • +
+
    +
  • +

    +Any of the common web spidering engines, such as AltaVista or Google, as long as you use the right +search terms. +

    + +

    +For example, searching on the string "cgi-perl" gives a more detailed +explanation of this package than the brief description field in its control +file. +

    +
    • +
+ +
+ +

11.4 Are there logs of known bugs?

+ +

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

+ +

+The Debian GNU/Linux distribution has a bug tracking system (BTS) which files +details of bugs reported by users and developers. Each bug is given a number, +and is kept on file until it is marked as having been dealt with. +

+ +

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

+ +

+A mail server provides access to the bug tracking system database via e-mail. +In order to get the instructions, send an e-mail to request@bugs.debian.org +with "help" in the body. +

+ +
+ +

11.5 How do I report a bug in Debian?

+ +

+If you have found a bug in Debian, please read the instructions for reporting a +bug in Debian. These instructions can be obtained in one of several ways: +

+
    +
  • +

    +By anonymous FTP. Debian mirror sites contain the instructions in the file +doc/bug-reporting.txt. +

    +
    • +
+ +
    +
  • +

    +On any Debian system with the doc-debian package installed. The +instructions are in the file +/usr/share/doc/debian/bug-reporting.txt. +

    +
    • +
+ +

+You can use the package reportbug that will guide you through the +reporting process and mail the message to the proper address, with some extra +details about your system added automatically. It will also show you a list of +bugs already reported to the package you are reporting against in case your bug +has been reported previously, so that you can additional information to the +existing bug report. +

+ +

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

+ +
+     Package: package-name
+
+ +

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

+ +
+     Version: version-number
+
+ +

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

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

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

+ +
+     cat /etc/debian_version
+
+ +

+Expect to get an automatic acknowledgement of your bug report. It will also be +automatically given a bug tracking number, entered into the bug log and +forwarded to the debian-bugs-dist mailing list. +

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-uptodate.en.html b/includes/common/doc/FAQ/html/ch-uptodate.en.html new file mode 100644 index 0000000..b271f29 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-uptodate.en.html @@ -0,0 +1,479 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Keeping your Debian system up-to-date + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

+A Debian goal is to provide a consistent upgrade path and a secure upgrade +process. We always do our best to make upgrading to new releases a smooth +procedure. In case there's some important note to add to the upgrade process, +the packages will alert the user, and often provide a solution to a possible +problem. +

+ +

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

+ +
+ +

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

+ +

+There are several ways to upgrade: +

+ +
    +
  • +

    +Following closely the Debian +libc5 to libc6 Mini-HOWTO and upgrade the most important packages by +hand. autoup.sh is based on this Mini-HOWTO, so this method +should work more or less like using autoup.sh. +

    +
    • +
+
    +
  • +

    +Using a libc5-based apt. 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 dists/slink/main/upgrade-older-i386 directory at +the Debian archives. +

    +
    • +
+
    +
  • +

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

    +
    • +
+ +
+ +

8.2 How can I keep my Debian system current?

+ +

+One could simply execute an anonymous ftp call to a Debian archive, then peruse +the directories until one finds the desired file, and then fetch it, and +finally install it using dpkg. Note that dpkg will +install upgrade files in place, even on a running system. Sometimes, a revised +package will require the installation of a newly revised version of another +package, in which case the installation will fail until/unless the other +package is installed. +

+ +

+Many people find this approach much too time-consuming, since Debian evolves so +quickly -- typically, a dozen or more new packages are uploaded every week. +This number is larger just before a new major release. To deal with this +avalanche, many people prefer to use a more automated method. Several +different packages are available for this purpose: +

+ +
+ +

8.2.1 aptitude

+ +

+APT is an advanced interface to the Debian packaging system. It features +complete installation ordering, multiple source capability and several other +unique features, see the User's Guide in +/usr/share/doc/apt-doc/guide.html/index.html (you will have to +install the apt-doc package). +

+ +

+aptitude is the recommended package manager for Debian GNU/Linux +systems. It is a text-based interface to APT using the curses library, and can +be used to perform management tasks in a fast and easy way. +

+ +

+Before you can use aptitude, you'll have to edit the +/etc/apt/sources.list file to set it up. If you wish to upgrade +to the latest stable version of Debian, you'll probably want to use a source +like this one: +

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

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

+ +

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

+ +

+To update your system, run +

+ +
+     aptitude update
+
+ +

+followed by +

+ +
+     aptitude dist-upgrade
+
+ +

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

+ +
+ +

8.2.2 apt-get, dselect and apt-cdrom

+ +

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

+ +

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

+ +

+Then run +

+ +
+     apt-get update
+
+ +

+followed by +

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

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

+ +

+To use APT with dselect, choose the APT access method in dselect's +method selection screen (option 0) and then specify the sources that should be +used. The configuration file is /etc/apt/sources.list. See also +dselect, Section 7.1.4. +

+ +

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

+ +

+Please note that when you get and install the packages, you'll still have them +kept in your /var directory hierarchy. To keep your partition from +overflowing, remember to delete extra files using apt-get clean +and apt-get autoclean, or to move them someplace else (hint: use +apt-move). +

+ +
+ +

8.2.3 dpkg-ftp

+ +

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

+ +

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

+ +

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

+ +
+ +

8.2.4 mirror

+ +

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

+ +

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

+ +

+The mirror program is generally useful for updating local copies +of remote directory trees. The files fetched need not be Debian files. (Since +mirror is a Perl script, it can also run on non-Unix systems.) +Though the mirror program provides mechanisms for excluding files +names of which match user-specified strings, this program is most useful when +the objective is to download whole directory trees, rather than selected +packages. +

+ +
+ +

8.2.5 dpkg-mountable

+ +

+dpkg-mountable adds an access method called `mountable' to dselect's list, +which allows you to install from any file system specified in /etc/fstab. For +example, the archive could be a normal hard disk partition or an NFS server, +which it will automatically mount and umount for you if necessary. +

+ +

+It also has some extra features not found in the standard dselect methods, such +as provision for a local file tree (either parallel to the main distribution or +totally separate), and only getting packages which are required, rather than +the time-consuming recursive directory scan, as well as logging of all dpkg +actions in the install method. +

+ +
+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +
+ +

8.5 How can I keep a log of the packages I added to the system? I'd like to know when which package upgrades and removals have occured!

+ +

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

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

+) and the results (e.g. +

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

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

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

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

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

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

+ +

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

+ +

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

+ +
+ +

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

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/ch-uptodate.html b/includes/common/doc/FAQ/html/ch-uptodate.html new file mode 100644 index 0000000..b271f29 --- /dev/null +++ b/includes/common/doc/FAQ/html/ch-uptodate.html @@ -0,0 +1,479 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Keeping your Debian system up-to-date + + + + + +

+
+ +

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

+ +
+ +

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

+ +
+ +

+A Debian goal is to provide a consistent upgrade path and a secure upgrade +process. We always do our best to make upgrading to new releases a smooth +procedure. In case there's some important note to add to the upgrade process, +the packages will alert the user, and often provide a solution to a possible +problem. +

+ +

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

+ +
+ +

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

+ +

+There are several ways to upgrade: +

+ +
    +
  • +

    +Following closely the Debian +libc5 to libc6 Mini-HOWTO and upgrade the most important packages by +hand. autoup.sh is based on this Mini-HOWTO, so this method +should work more or less like using autoup.sh. +

    +
    • +
+
    +
  • +

    +Using a libc5-based apt. 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 dists/slink/main/upgrade-older-i386 directory at +the Debian archives. +

    +
    • +
+
    +
  • +

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

    +
    • +
+ +
+ +

8.2 How can I keep my Debian system current?

+ +

+One could simply execute an anonymous ftp call to a Debian archive, then peruse +the directories until one finds the desired file, and then fetch it, and +finally install it using dpkg. Note that dpkg will +install upgrade files in place, even on a running system. Sometimes, a revised +package will require the installation of a newly revised version of another +package, in which case the installation will fail until/unless the other +package is installed. +

+ +

+Many people find this approach much too time-consuming, since Debian evolves so +quickly -- typically, a dozen or more new packages are uploaded every week. +This number is larger just before a new major release. To deal with this +avalanche, many people prefer to use a more automated method. Several +different packages are available for this purpose: +

+ +
+ +

8.2.1 aptitude

+ +

+APT is an advanced interface to the Debian packaging system. It features +complete installation ordering, multiple source capability and several other +unique features, see the User's Guide in +/usr/share/doc/apt-doc/guide.html/index.html (you will have to +install the apt-doc package). +

+ +

+aptitude is the recommended package manager for Debian GNU/Linux +systems. It is a text-based interface to APT using the curses library, and can +be used to perform management tasks in a fast and easy way. +

+ +

+Before you can use aptitude, you'll have to edit the +/etc/apt/sources.list file to set it up. If you wish to upgrade +to the latest stable version of Debian, you'll probably want to use a source +like this one: +

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

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

+ +

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

+ +

+To update your system, run +

+ +
+     aptitude update
+
+ +

+followed by +

+ +
+     aptitude dist-upgrade
+
+ +

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

+ +
+ +

8.2.2 apt-get, dselect and apt-cdrom

+ +

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

+ +

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

+ +

+Then run +

+ +
+     apt-get update
+
+ +

+followed by +

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

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

+ +

+To use APT with dselect, choose the APT access method in dselect's +method selection screen (option 0) and then specify the sources that should be +used. The configuration file is /etc/apt/sources.list. See also +dselect, Section 7.1.4. +

+ +

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

+ +

+Please note that when you get and install the packages, you'll still have them +kept in your /var directory hierarchy. To keep your partition from +overflowing, remember to delete extra files using apt-get clean +and apt-get autoclean, or to move them someplace else (hint: use +apt-move). +

+ +
+ +

8.2.3 dpkg-ftp

+ +

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

+ +

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

+ +

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

+ +
+ +

8.2.4 mirror

+ +

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

+ +

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

+ +

+The mirror program is generally useful for updating local copies +of remote directory trees. The files fetched need not be Debian files. (Since +mirror is a Perl script, it can also run on non-Unix systems.) +Though the mirror program provides mechanisms for excluding files +names of which match user-specified strings, this program is most useful when +the objective is to download whole directory trees, rather than selected +packages. +

+ +
+ +

8.2.5 dpkg-mountable

+ +

+dpkg-mountable adds an access method called `mountable' to dselect's list, +which allows you to install from any file system specified in /etc/fstab. For +example, the archive could be a normal hard disk partition or an NFS server, +which it will automatically mount and umount for you if necessary. +

+ +

+It also has some extra features not found in the standard dselect methods, such +as provision for a local file tree (either parallel to the main distribution or +totally separate), and only getting packages which are required, rather than +the time-consuming recursive directory scan, as well as logging of all dpkg +actions in the install method. +

+ +
+ +

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

+ +

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

+ +
+ +

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

+ +

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

+ +
+ +

8.5 How can I keep a log of the packages I added to the system? I'd like to know when which package upgrades and removals have occured!

+ +

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

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

+) and the results (e.g. +

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

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

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

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

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

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

+ +

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

+ +

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

+ +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/footnotes.en.html b/includes/common/doc/FAQ/html/footnotes.en.html new file mode 100644 index 0000000..0d5b7d4 --- /dev/null +++ b/includes/common/doc/FAQ/html/footnotes.en.html @@ -0,0 +1,112 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Footnotes + + + + + +
+ +

+The Debian GNU/Linux FAQ +
Footnotes

+ +

1

+ +

+When the present-day sid did not exist, the FTP site organization had one major +flaw: there was an assumption that when an architecture is created in the +current unstable, it will be released when that distribution becomes the new +stable. For many architectures that isn't the case, with the result that those +directories had to be moved at release time. This was impractical because the +move would chew up lots of bandwidth. +

+ +

+The archive administrators worked around this problem for several years by +placing binaries for unreleased architectures in a special directory called +"sid". For those architectures not yet released, the first time they +were released there was a link from the current stable to sid, and from then on +they were created inside the unstable tree as normal. This layout was somewhat +confusing to users. +

+ +

+With the advent of package pools (see What's in the +pool directory?, Section 5.10), binary packages began to be +stored in a canonical location in the pool, regardless of the distribution, so +releasing a distribution no longer causes large bandwidth consumption on the +mirrors (there is, however, a lot of gradual bandwidth consumption throughout +the development process). +

+ +

2

+ +

+dists/stable/main, dists/stable/contrib, +dists/stable/non-free, and dists/unstable/main/, etc. +

+ +

3

+ +

+Historically, packages were kept in the subdirectory of dists +corresponding to which distribution contained them. This turned out to cause +various problems, such as large bandwidth consumption on mirrors when major +changes were made. This was fixed with the introduction of the package pool. +

+ +

+The dists directories are still used for the index files used by +programs like apt. You may also still see paths containing +dists/potato or dists/woody in the Filename header +field of some older packages. +

+ +

4

+ +

+Notice that there are ports that make this tool available with other package +management systems, like Red Hat package manager, also known as +rpm +

+ +

5

+ +

+Although this can also lead to systems with more packages installed than they +actually need to work. +

+ +

6

+ +

+Use the debian-list-subject-REQUEST@lists.debian.org address for +that. +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/footnotes.html b/includes/common/doc/FAQ/html/footnotes.html new file mode 100644 index 0000000..0d5b7d4 --- /dev/null +++ b/includes/common/doc/FAQ/html/footnotes.html @@ -0,0 +1,112 @@ + + + + + + + + +The Debian GNU/Linux FAQ - Footnotes + + + + + +
+ +

+The Debian GNU/Linux FAQ +
Footnotes

+ +

1

+ +

+When the present-day sid did not exist, the FTP site organization had one major +flaw: there was an assumption that when an architecture is created in the +current unstable, it will be released when that distribution becomes the new +stable. For many architectures that isn't the case, with the result that those +directories had to be moved at release time. This was impractical because the +move would chew up lots of bandwidth. +

+ +

+The archive administrators worked around this problem for several years by +placing binaries for unreleased architectures in a special directory called +"sid". For those architectures not yet released, the first time they +were released there was a link from the current stable to sid, and from then on +they were created inside the unstable tree as normal. This layout was somewhat +confusing to users. +

+ +

+With the advent of package pools (see What's in the +pool directory?, Section 5.10), binary packages began to be +stored in a canonical location in the pool, regardless of the distribution, so +releasing a distribution no longer causes large bandwidth consumption on the +mirrors (there is, however, a lot of gradual bandwidth consumption throughout +the development process). +

+ +

2

+ +

+dists/stable/main, dists/stable/contrib, +dists/stable/non-free, and dists/unstable/main/, etc. +

+ +

3

+ +

+Historically, packages were kept in the subdirectory of dists +corresponding to which distribution contained them. This turned out to cause +various problems, such as large bandwidth consumption on mirrors when major +changes were made. This was fixed with the introduction of the package pool. +

+ +

+The dists directories are still used for the index files used by +programs like apt. You may also still see paths containing +dists/potato or dists/woody in the Filename header +field of some older packages. +

+ +

4

+ +

+Notice that there are ports that make this tool available with other package +management systems, like Red Hat package manager, also known as +rpm +

+ +

5

+ +

+Although this can also lead to systems with more packages installed than they +actually need to work. +

+ +

6

+ +

+Use the debian-list-subject-REQUEST@lists.debian.org address for +that. +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/index.en.html b/includes/common/doc/FAQ/html/index.en.html new file mode 100644 index 0000000..952a225 --- /dev/null +++ b/includes/common/doc/FAQ/html/index.en.html @@ -0,0 +1,311 @@ + + + + + + + + +The Debian GNU/Linux FAQ + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+ +

Abstract

+ +

+This document answers questions frequently asked about Debian GNU/Linux. +

+ +
+ +

Copyright Notice

+ +

+Copyright © 1996-2005 by Software in the Public Interest +

+ +

+Permission is granted to make and distribute verbatim copies of this document +provided the copyright notice and this permission notice are preserved on all +copies. +

+ +

+Permission is granted to copy and distribute modified versions of this document +under the conditions for verbatim copying, provided that the entire resulting +derived work is distributed under the terms of a permission notice identical to +this one. +

+ +

+Permission is granted to copy and distribute translations of this document into +another language, under the above conditions for modified versions, except that +this permission notice may be included in translations approved by the Free +Software Foundation instead of in the original English. +

+ +
+ +

Contents

+ + + +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/FAQ/html/index.html b/includes/common/doc/FAQ/html/index.html new file mode 100644 index 0000000..952a225 --- /dev/null +++ b/includes/common/doc/FAQ/html/index.html @@ -0,0 +1,311 @@ + + + + + + + + +The Debian GNU/Linux FAQ + + + + + +

+
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+ +

Abstract

+ +

+This document answers questions frequently asked about Debian GNU/Linux. +

+ +
+ +

Copyright Notice

+ +

+Copyright © 1996-2005 by Software in the Public Interest +

+ +

+Permission is granted to make and distribute verbatim copies of this document +provided the copyright notice and this permission notice are preserved on all +copies. +

+ +

+Permission is granted to copy and distribute modified versions of this document +under the conditions for verbatim copying, provided that the entire resulting +derived work is distributed under the terms of a permission notice identical to +this one. +

+ +

+Permission is granted to copy and distribute translations of this document into +another language, under the above conditions for modified versions, except that +this permission notice may be included in translations approved by the Free +Software Foundation instead of in the original English. +

+ +
+ +

Contents

+ + + +
+ +

+[ previous ] +[ Contents ] +[ 1 ] +[ 2 ] +[ 3 ] +[ 4 ] +[ 5 ] +[ 6 ] +[ 7 ] +[ 8 ] +[ 9 ] +[ 10 ] +[ 11 ] +[ 12 ] +[ 13 ] +[ 14 ] +[ 15 ] +[ next ] +

+ +
+ +

+The Debian GNU/Linux FAQ +

+ +
+version 3.1.3, 25 April 2006
+
+Authors are listed at Debian FAQ Authors
+
+
+
+ + + + + diff --git a/includes/common/doc/bug-log-access.txt b/includes/common/doc/bug-log-access.txt new file mode 100644 index 0000000..c8fa75f --- /dev/null +++ b/includes/common/doc/bug-log-access.txt @@ -0,0 +1,55 @@ +Methods of accessing the bug tracking system logs + +Accessing active bug reports + + Each message received at or sent by the bug processing system is + logged and made available in a number of ways. + + The primary access method is to use the web pages. See the forms on + the main BTS page at http://bugs.debian.org/ + + There is a mailserver which can send bug reports as plain text on + request. To use it send the word help as the sole contents of an email + to request@bugs.debian.org (the Subject of the message is ignored), or + read the instructions on the World Wide Web or in the file + bug-log-mailserver.txt. + +Accessing archived bug reports + + Each closed bug report is archived 28 days after the last message + relating to it is received and filed. This means that it is no longer + possible to access it or change anything about it using the control + and service bots. However, the reports are still accessible for + viewing. + + You can search the bug report archive using the WWW forms at + http://bugs.debian.org/, simply select the "archived bugs" option. + + Note that it doesn't contain the oldest closed bug reports, only those + after #40000, approximately. + +Accessing the raw bug data + + If you need to get hold of the raw data used by the bug tracking + system, you can mirror it using rsync from bugs-mirror.debian.org. The + relevant modules are bts-spool-db (for the active bug spool), + bts-spool-archive (for bugs that have been closed for a while and thus + archived), and bts-spool-index (for the bug index files). + + At the time of writing, the active spool is about 2.5GB and the + archived spool is about 10GB. If you only need a sample for testing + purposes, please consider downloading only part of the active spool + rather than the whole thing. + + Please do not rely on *.status files in the bug spools, as they are + obsolete, for compatibility purposes only, and will be removed at some + point in the future. Use the *.summary files instead. + _________________________________________________________________ + + Debian BTS administrators + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/common/doc/bug-log-mailserver.txt b/includes/common/doc/bug-log-mailserver.txt new file mode 100644 index 0000000..aa28efc --- /dev/null +++ b/includes/common/doc/bug-log-mailserver.txt @@ -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 + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/common/doc/bug-mailserver-refcard.txt b/includes/common/doc/bug-mailserver-refcard.txt new file mode 100644 index 0000000..b3ce545 --- /dev/null +++ b/includes/common/doc/bug-mailserver-refcard.txt @@ -0,0 +1,81 @@ +Mail servers' reference card + + Full documentation of the mail servers is available on the WWW, in the + files bug-log-mailserver.txt and bug-maint-mailcontrol.txt or by + sending the word help to each mailserver. + +Synopsis of commands available at request@bugs.debian.org + + * send bugnumber + * send-detail bugnumber + * index [full] + * index-summary by-package + * index-summary by-number + * index-maint + * index maint maintainer + * index-packages + * index packages package + * send-unmatched [this|0] + * send-unmatched last|-1 + * send-unmatched old|-2 + * getinfo filename (ftp.debian.org/debian/doc/*) + * help + * refcard + * quit|stop|thank...|--... + * #... (comment) + * debug level + +Synopsis of extra commands available at control@bugs.debian.org + + * reassign bugnumber package [ version ] + * severity bugnumber severity + * reopen bugnumber [ originator-address | = | ! ] + * found bugnumber [ version ] + * notfound bugnumber version + * submitter bugnumber originator-address | ! + * forwarded bugnumber address + * notforwarded bugnumber + * owner bugnumber address | ! + * noowner bugnumber + * retitle bugnumber new-title + * clone bugnumber NewID [ new IDs ... ] + * merge bugnumber bugnumber ... + * unmerge bugnumber + * forcemerge bugnumber bugnumber ... + * tag bugnumber [ + | - | = ] tag [ tag ... ] + * block bugnumber by bug ... + * unblock bugnumber by bug ... + * close bugnumber [ fixed-version ] (deprecated - you must + separately tell originator why, see "Closing bug reports" instead) + + reopen with = or no originator address leaves the originator as the + original submitter; ! sets it to you, the person doing the reopen. + + Severities are critical, grave, serious, important, normal, minor, and + wishlist. + + Tags currently include patch, wontfix, moreinfo, unreproducible, help, + pending, fixed, security, upstream, confirmed, fixed-upstream, + fixed-in-experimental, d-i, ipv6, lfs, l10n, potato, woody, sarge, + sarge-ignore, etch, etch-ignore, sid, and experimental. + +Synopsis of bug submission and followup addresses + + * nnn[ -submit | ] + * nnn-maintonly + * nnn-quiet + * nnn-forwarded + * nnn-request + * nnn-submitter + * nnn-done + * nnn-close + * nnn-subscribe + _________________________________________________________________ + + Debian BTS administrators + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/common/doc/bug-maint-info.txt b/includes/common/doc/bug-maint-info.txt new file mode 100644 index 0000000..1a450eb --- /dev/null +++ b/includes/common/doc/bug-maint-info.txt @@ -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 + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/common/doc/bug-maint-mailcontrol.txt b/includes/common/doc/bug-maint-mailcontrol.txt new file mode 100644 index 0000000..1167b10 --- /dev/null +++ b/includes/common/doc/bug-maint-mailcontrol.txt @@ -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 + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/common/doc/bug-reporting.txt b/includes/common/doc/bug-reporting.txt new file mode 100644 index 0000000..ca14c2a --- /dev/null +++ b/includes/common/doc/bug-reporting.txt @@ -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 + # by sending e-mail to @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: + + Replace with the name of the package which has the bug. + + The second line of the message should say: +Version: + + Replace with the version of the package. Please don't + include any text here other than the version itself, as the bug + tracking system relies on this field to work out which releases are + affected by the bug. + + You need to supply a correct Package line in the pseudo-header in + order for the bug tracking system to deliver the message to the + package's maintainer. See this example for information on how to find + this information. + + 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: + + Replace 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: + + Replace 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 +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 + + Debian bug tracking system + Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, + 1994-1997 Ian Jackson. + _________________________________________________________________ + diff --git a/includes/common/doc/constitution.txt b/includes/common/doc/constitution.txt new file mode 100644 index 0000000..191f73b --- /dev/null +++ b/includes/common/doc/constitution.txt @@ -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. diff --git a/includes/common/doc/debian-manifesto b/includes/common/doc/debian-manifesto new file mode 100644 index 0000000..9322c93 --- /dev/null +++ b/includes/common/doc/debian-manifesto @@ -0,0 +1,135 @@ +Please note that this document is provided in order to document +Debian's history. While the general ideas still apply some details +changed. + + +******************** +Appendix +The Debian Manifesto +******************** + + + The Debian Linux Manifesto + + Written by Ian A. Murdock + Revised 01/06/94 + + +What is Debian Linux? +===================== + +Debian Linux is a brand-new kind of Linux distribution. Rather than +being developed by one isolated individual or group, as other +distributions of Linux have been developed in the past, Debian is being +developed openly in the spirit of Linux and GNU. The primary purpose +of the Debian project is to finally create a distribution that lives up +to the Linux name. Debian is being carefully and conscientiously put +together and will be maintained and supported with similar care. + +It is also an attempt to create a non-commercial distribution that will +be able to effectively compete in the commercial market. It will +eventually be distributed by The Free Software Foundation on CD-ROM, +and The Debian Linux Association will offer the distribution on floppy +disk and tape along with printed manuals, technical support and other +end-user essentials. All of the above will be available at little more +than cost, and the excess will be put toward further development of +free software for all users. Such distribution is essential to the +success of the Linux operating system in the commercial market, and it +must be done by organizations in a position to successfully advance and +advocate free software without the pressure of profits or returns. + + +Why is Debian being constructed? +================================ + +Distributions are essential to the future of Linux. Essentially, they +eliminate the need for the user to locate, download, compile, install +and integrate a fairly large number of essential tools to assemble a +working Linux system. Instead, the burden of system construction is +placed on the distribution creator, whose work can be shared with +thousands of other users. Almost all users of Linux will get their +first taste of it through a distribution, and most users will continue +to use a distribution for the sake of convenience even after they are +familiar with the operating system. Thus, distributions play a very +important role indeed. + +Despite their obvious importance, distributions have attracted little +attention from developers. There is a simple reason for this: they are +neither easy nor glamorous to construct and require a great deal of +ongoing effort from the creator to keep the distribution bug-free and +up-to-date. It is one thing to put together a system from scratch; it +is quite another to ensure that the system is easy for others to +install, is installable and usable under a wide variety of hardware +configurations, contains software that others will find useful, and is +updated when the components themselves are improved. + +Many distributions have started out as fairly good systems, but as time +passes attention to maintaining the distribution becomes a secondary +concern. A case-in-point is the Softlanding Linux System (better known +as SLS). It is quite possibly the most bug-ridden and badly maintained +Linux distribution available; unfortunately, it is also quite possibly +the most popular. It is, without question, the distribution that +attracts the most attention from the many commercial "distributors" of +Linux that have surfaced to capitalize on the growing popularity of the +operating system. + +This is a bad combination indeed, as most people who obtain Linux from +these "distributors" receive a bug-ridden and badly maintained Linux +distribution. As if this wasn't bad enough, these "distributors" have +a disturbing tendency to misleadingly advertise non-functional or +extremely unstable "features" of their product. Combine this with the +fact that the buyers will, of course, expect the product to live up to +its advertisement and the fact that many may believe it to be a +commercial operating system (there is also a tendency not to mention +that Linux is free nor that it is distributed under the GNU General +Public License). To top it all off, these "distributors" are actually +making enough money from their effort to justify buying larger +advertisements in more magazines; it is the classic example of +unacceptable behavior being rewarded by those who simply do not know +any better. Clearly something needs to be done to remedy the +situation. + + +How will Debian attempt to put an end to these problems? +======================================================== + +The Debian design process is open to ensure that the system is of the +highest quality and that it reflects the needs of the user community. +By involving others with a wide range of abilities and backgrounds, +Debian is able to be developed in a modular fashion. Its components +are of high quality because those with expertise in a certain area are +given the opportunity to construct or maintain the individual +components of Debian involving that area. Involving others also +ensures that valuable suggestions for improvement can be incorporated +into the distribution during its development; thus, a distribution is +created based on the needs and wants of the users rather than the needs +and wants of the constructor. It is very difficult for one individual +or small group to anticipate these needs and wants in advance without +direct input from others. + +Debian Linux will also be distributed on physical media by the Free +Software Foundation and the Debian Linux Association. This provides +Debian to users without access to the Internet or FTP and additionally +makes products and services such as printed manuals and technical +support available to all users of the system. In this way, Debian may +be used by many more individuals and organizations than is otherwise +possible, the focus will be on providing a first-class product and not +on profits or returns, and the margin from the products and services +provided may be used to improve the software itself for all users +whether they paid to obtain it or not. + +The Free Software Foundation plays an extremely important role in the +future of Debian. By the simple fact that they will be distributing +it, a message is sent to the world that Linux is not a commercial +product and that it never should be, but that this does not mean that +Linux will never be able to compete commercially. For those of you who +disagree, I challenge you to rationalize the success of GNU Emacs and +GCC, which are not commercial software but which have had quite an +impact on the commercial market regardless of that fact. + +The time has come to concentrate on the future of Linux rather than on +the destructive goal of enriching oneself at the expense of the entire +Linux community and its future. The development and distribution of +Debian may not be the answer to the problems that I have outlined in +the Manifesto, but I hope that it will at least attract enough +attention to these problems to allow them to be solved. diff --git a/includes/common/doc/mailing-lists.txt b/includes/common/doc/mailing-lists.txt new file mode 100644 index 0000000..2d92973 --- /dev/null +++ b/includes/common/doc/mailing-lists.txt @@ -0,0 +1,1649 @@ + Introduction to the Debian mailing lists + ======================================== + + Debian GNU/Linux is developed through distributed development all + around the world. Therefore, email is the preferred way to discuss + various items. Much of the conversation between Debian developers + and users is managed through several mailing lists. + + There are many world-open mailing lists, meaning anyone can read + everything that is posted, and participate in the discussions. Everyone is + encouraged to help development of Debian and to spread the word of free + software. There are also a few lists which are only open to official Debian + developers; please don't interpret this as closed development, it sometimes + doesn't make much sense discussing internal topics with non-developers. + + All original Debian mailing lists run on a special server, using an + automatic mail processing software called SmartList. This server is called + lists.debian.org. All submission, subscription and unsubscription messages + have to be sent to a particular address at this host. + + The language used on all lists is English, unless stated otherwise. + There are some user lists for other languages available. + +Subscription / Unsubscription +----------------------------- + + Anyone is able to subscribe/unsubscribe on their own to any mailing list, + presuming the subscription policy for a particular list is `open'. + + The requests for subscription or unsubscription can be sent to a special + control address, which is slightly different from the list address. + Subscription or unsubscription messages should NOT be sent to the address + of the mailing list itself. + + To subscribe or unsubscribe from a mailing list, please send mail to + + -REQUEST@lists.debian.org + + with the word `subscribe' or `unsubscribe' as subject. + + Please remember the -REQUEST part of the address. + + As part of the subscription process, the list software will send you an + email to which you must reply in order to finish subscribing. This is a + security measure to keep people from subscribing others to the lists without + their permission. + + If you need to contact a human listmaster, direct your mail to + listmaster@lists.debian.org . To find out who is responsible for the + lists, take a look at http://www.debian.org/intro/organization + +User lists + + There are several user based mailing lists where developers and + users can get in contact to discuss and solve problems. + + debian-announce@lists.debian.org + + Description : Major news and very important changes in the project + are announced here. + Moderated : yes + Subscription: open + + debian-chinese-big5@lists.debian.org + + Description : Debian Chinese Project: Chinese localization (l10n), + documentation and web site translation, user support + etc. + + Posts may be in English or Big5-encoded Chinese. + All posts are automatically converted to GB encoding + and cross-posted to the debian-chinese-gb mailing list. + + If you would rather read and post in GB-encoded + Chinese, please subscribe to debian-chinese-gb instead. + Language : Chinese + Moderated : subscribers + Subscription: open + + debian-chinese-gb@lists.debian.org + + Description : Debian Chinese Project: Chinese localization (l10n) + issues, documentation and web site translation, user + support etc. + + Posts may be in English or GB-encoded Chinese. + All posts are automatically converted to Big5 encoding + and cross-posted to the debian-chinese-big5 mailing list. + + If you would rather read and post in Big5-encoded + Chinese, please subscribe to debian-chinese-big5 instead. + Language : Chinese + Moderated : subscribers + Subscription: open + + debian-commercial@lists.debian.org + + Description : Information about Debian related products from + software and hardware vendors is published here. + This is a moderated list, so please send your + submissions to the moderator at press@debian.org. + + Please note that posting commercial posts to any + other Debian mailing list is not permitted. + Moderated : yes + Subscription: open + + debian-esperanto@lists.debian.org + + Description : Debian users who speak Esperanto. + Language : Esperanto + Moderated : no + Subscription: open + + debian-firewall@lists.debian.org + + Description : Discussion of implementation and maintenance of + firewalls using Debian. Both basic issues and new + more exotic developments are discussed here. + Moderated : no + Subscription: open + + debian-isp@lists.debian.org + + Description : Discussion about issues and problems specific to + Internet Service Providers (ISPs for short) that + use Debian. + Moderated : no + Subscription: open + + debian-italian@lists.debian.org + + Description : Support for Debian users that speak Italian. + (High-volume mailing list.) + Language : Italian + Moderated : no + Subscription: open + + debian-japanese@lists.debian.org + + Description : Support for Debian users that speak Japanese, + Japanese localization issues, integrating + Debian JP packages into Debian etc. + + The English language is allowed, but using Japanese is + encouraged even for those who aren't native speakers. + + For native Japanese, Debian JP Project provides + several mailing lists discussing the Debian system in + Japanese, see http://www.debian.or.jp/MailingList.html + Language : English/Japanese + Moderated : no + Subscription: open + + debian-kde@lists.debian.org + + Description : Discussions related to KDE in Debian. + Those developing KDE-based packages are + encouraged to use this to discuss issues + and share their experience. + Moderated : no + Subscription: open + + debian-laptop@lists.debian.org + + Description : Installing, updating and using laptops with Debian. + Suggestions on special packaging, complaints, etc. + are welcome. + Moderated : no + Subscription: open + + debian-news-french@lists.debian.org + + Description : News about Debian for users speaking French. + Language : French + Moderated : yes + Subscription: open + + debian-news-german@lists.debian.org + + Description : News about Debian for users speaking German. + Language : German + Moderated : yes + Subscription: open + + debian-news-italian@lists.debian.org + + Description : Releases, news, internationalization efforts and + other related news about Debian for Italian-speaking users. + Language : Italian + Moderated : yes + Subscription: open + + debian-news-portuguese@lists.debian.org + + Description : Releases, news, internationalization efforts and other + related news about Debian for users speaking Portuguese. + Language : Portuguese + Moderated : yes + Subscription: open + + debian-news-spanish@lists.debian.org + + Description : Releases, news, internationalization efforts and + other related news about Debian for Spanish-speaking users. + Language : Spanish + Moderated : yes + Subscription: open + + debian-news@lists.debian.org + + Description : General news about the distribution and the project. + + The current events and news about Debian are + summarized in the Debian Weekly News, a newsletter + regularly posted on this list. + Moderated : yes + Subscription: open + + debian-russian@lists.debian.org + + Description : Support for Debian users that speak Russian, + and Russian localization issues: translating + "po" files, coordinating patches for Debian + packages to work with the Russian language. + Language : Russian + Moderated : no + Subscription: open + + debian-security-announce@lists.debian.org + + Description : The security team informs the users about security + problems by posting security advisories about + Debian packages on this list. + Moderated : yes + Subscription: open + + debian-user-catalan@lists.debian.org + + Description : Support for Debian users that speak Catalan. + Language : Catalan + Moderated : no + Subscription: open + + debian-user-danish@lists.debian.org + + Description : Support for Debian users who speak Danish. + Language : Danish + Moderated : no + Subscription: open + + debian-user-french@lists.debian.org + + Description : Support for Debian users that speak French. + (High-volume mailing list.) + Language : French + Moderated : no + Subscription: open + + debian-user-german@lists.debian.org + + Description : Support for Debian users that speak German. + (High-volume mailing list.) + Language : German + Moderated : no + Subscription: open + + debian-user-hungarian + + Description : Support for Debian users that speak Hungarian. + Language : Hungarian + Subscription: http://lists.linux.hu/mailman/listinfo/debian + + debian-user-icelandic@lists.debian.org + + Description : Support for Debian users that speak Icelandic. + Moderated : no + Subscription: open + + debian-user-indonesian@lists.debian.org + + Description : Support for Debian users who speak Indonesian. + Language : Indonesian + Moderated : no + Subscription: open + + debian-user-polish@lists.debian.org + + Description : Support for Debian users that speak Polish. + Language : Polish + Moderated : no + Subscription: open + + debian-user-portuguese@lists.debian.org + + Description : Support for Debian users who speak Portuguese. + (High-volume mailing list.) + Language : Portuguese (both European and Brazilian, and other dialects are welcome) + Moderated : no + Subscription: open + + debian-user-spanish@lists.debian.org + + Description : Support for Debian users that speak Spanish. + (High-volume mailing list.) + Language : Spanish + Moderated : no + Subscription: open + + debian-user-swedish@lists.debian.org + + Description : Support for Debian users that speak Swedish. + Language : Swedish + Moderated : no + Subscription: open + + debian-user-turkish@lists.debian.org + + Description : Support for Debian users that speak Turkish. + Language : Turkish + Moderated : no + Subscription: open + + debian-user-ukrainian@lists.debian.org + + Description : Support for Debian users who speak Ukrainian. + Language : Ukrainian + Moderated : no + Subscription: open + + debian-user-vietnamese@lists.debian.org + + Description : Support for Debian users that speak Vietnamese, and discussions on translations + Language : Vietnamese + Moderated : no + Subscription: open + + debian-user@lists.debian.org + + Description : Support for Debian users who speak English. + (High-volume mailing list.) + Digest : debian-user-digest@lists.debian.org + Moderated : no + Subscription: open + + debian-volatile-announce@lists.debian.org + + Description : Announcements relating to the debian-volatile project include new uploads and changes + Moderated : yes + Subscription: open + + debian-volatile@lists.debian.org + + Description : Discussion about the debian-volatile archive + Moderated : no + Subscription: open + +Development lists + + There are several lists on which developers and experienced + users discuss more technical issues. In addition, there are some + announcement lists to help experienced users keep track of + development. + + debian-accessibility@lists.debian.org + + Description : User and Developer list for accessibility-related issues. + Moderated : no + Subscription: open + + debian-admin@lists.debian.org + + Description : This is our internal list used for administering the + Debian machine park. + Moderated : no + Subscription: closed + + debian-apache@lists.debian.org + + Description : Maintenance of the Apache HTTP server and related + packages in Debian: code changes, reproducing bugs, + talking to upstream etc. + + It is neither for submitting bug reports (please + use the BTS for that), nor for support requests. + Moderated : no + Subscription: open + + debian-beowulf@lists.debian.org + + Description : Discussion about Beowulf systems running Debian. + Moderated : no + Subscription: open + + debian-boot@lists.debian.org + + Description : Discussion and maintenance of the Debian + installation system. + Moderated : no + Subscription: open + + debian-cd@lists.debian.org + + Description : Creating Debian CD sets, official and unofficial. + Moderated : no + Subscription: open + + debian-ctte-private@lists.debian.org + + Description : Private communication between tech committee members. + Moderated : no + Subscription: Debian Technical Committee only + + debian-ctte@lists.debian.org + + Description : Public meeting, business and announcements of the Debian + Technical Committee + Moderated : subscribers + Subscription: open + + debian-custom@lists.debian.org + + Description : People on this list work on the challenges common to + all custom Debian distributions, ensuring that the + tools and procedures developed are shared, making + the most efficient use of our energies. + Moderated : no + Subscription: open + + debian-dak@lists.debian.org + + Description : Discussion about the Debian Archive Software, consisting of dak for the + archive and the buildd related parts wanna-build/sbuild. + Moderated : no + Subscription: open + + debian-ddtp@lists.debian.org + + Description : Discussions on the DDTP and coordination of the development process + Moderated : no + Subscription: open + + debian-debbugs-cvs@lists.debian.org + + Description : CVS commit messages when modifications are done to + debbugs + Moderated : no + Subscription: open + + debian-debbugs@lists.debian.org + + Description : Discussion and development of debbugs, the Debian + Bug Tracking System software. + Moderated : no + Subscription: open + + debian-desktop@lists.debian.org + + Description : Discussion about the Debian Desktop sub-project, + the integration of the various desktop-related + packages, bug reports, questions and patches. + Moderated : no + Subscription: open + + debian-devel-announce@lists.debian.org + + Description : Announcements of development issues like policy changes, + important release issues &c. + Moderated : signed + Subscription: open + + debian-devel-austrian + + Description : Discussion among the Debian developers in Austria. + Language : (mostly) German + Subscription: https://www.gibraltar.at/mailman/listinfo/debian-at + + debian-devel-french@lists.debian.org + + Description : This is the list used to discuss development + issues in French. + Moderated : no + Subscription: open + + debian-devel-games@lists.debian.org + + Description : Development and packaging discussion for games and game-related software in Debian. + Identification of potential new games suitable for Debian. Discussion about + infrastructure issues covering a wider range of games (e.g. multiplayer issues). + Moderated : no + Subscription: open + + debian-devel-italian@lists.debian.org + + Description : Discussion on development issues in Italian. + Moderated : no + Subscription: open + + debian-devel-portuguese@lists.debian.org + + Description : This is the list used by Portuguese developers + (or wannabes) to discuss development issues. + Moderated : no + Subscription: open + + debian-devel-spanish@lists.debian.org + + Description : This is the list used by Spanish developers + (or wannabes) to discuss issues besides + translation: provide help for new Spanish + developers, arrange key-signing meetings, arrange + work in booths on different shows, share experience + etc. + Moderated : no + Subscription: open + + debian-devel@lists.debian.org + + Description : Discussion about technical development topics. + (High-volume mailing list.) + Digest : debian-devel-digest@lists.debian.org + Moderated : no + Subscription: open + + debian-doc@lists.debian.org + + Description : Debian Documentation Project: anything related + to documentation in Debian is on topic here. + Moderated : no + Subscription: open + + debian-dpkg-bugs@lists.debian.org + + Description : Email sent by the bug tracking system regarding + the dpkg packages. + Moderated : no + Subscription: open + + debian-dpkg-cvs@lists.debian.org + + Description : The CVS commit messages from the dpkg CVS tree. + Moderated : no + Subscription: open + + debian-dpkg@lists.debian.org + + Description : Discussions and maintenance of dpkg, the basis of + the Debian packaging system. + Moderated : no + Subscription: open + + debian-edu-french@lists.debian.org + + Description : Discussions in french between all educational Debian-based projects. + This list should ease the collaboration between the projects themselves + and between Debian and those projects. + Moderated : no + Subscription: open + + debian-edu@lists.debian.org + + Description : Making Debian the best distribution in the + education landscape. + Moderated : no + Subscription: open + + debian-emacsen@lists.debian.org + + Description : Discussion of all things related to the several + Debian Emacs packages and their add-ons. + Moderated : no + Subscription: open + + debian-email@lists.debian.org + + Description : A generic "grab-bag" list for Debian related + correspondence such as contacting upstream authors + about licenses, bugs etc, or discussing the project + with others where it might be useful to have the + discussion archived somewhere. + + This list is archived internally on a Debian Project + machine, only developers have access to the archive. + Moderated : no + Subscription: developers only + + debian-embedded@lists.debian.org + + Description : Discussion about improving Debian for use with + embedded systems, including building cross-compiler + toolchains, cross-compiling packages, creating and + updating system images, using alternate libraries, + compile-time configuration of packages, etc. + Moderated : no + Subscription: open + + debian-events-eu@lists.debian.org + + Description : Discussions and organizational stuff about booths for + Debian at european exhibitions. + Moderated : no + Subscription: open + + debian-events-na@lists.debian.org + + Description : Discussions and organizational stuff about booths and + presentations for Debian at North American exhibitions. + Moderated : no + Subscription: open + + debian-events-nl@lists.debian.org + + Description : Announcements of small meetings and keysigning parties of Dutch + Debian Developers and other discussions of interest mainly for + Debian people in the Netherlands. Posts in both Dutch and English + are common. + Moderated : no + Subscription: open + + debian-flash@lists.debian.org + + Description : For discussion of issues relating to the development and use of Debian for + Flash development and viewing of Flash content. For general discussion of Flash + related free software, please visit the osflash community: http://osflash.org + Moderated : no + Subscription: open + + debian-gcc@lists.debian.org + + Description : Discussion on Debian packaging of GCC, the + GNU compiler collection: bug reports, porting + issues, any kind of questions or patches. + Moderated : no + Subscription: open + + debian-glibc@lists.debian.org + + Description : Discussion on Debian packaging of the GNU C Library, + the most important library on Debian systems. + Moderated : no + Subscription: open + + debian-gtk-gnome@lists.debian.org + + Description : Discussion and coordination among maintainers of + Debian's GTK+, GNOME and dependent or related + packages. + Moderated : no + Subscription: open + + debian-hams@lists.debian.org + + Description : Support for HAMRadio within Debian GNU/Linux. + Moderated : no + Subscription: open + + debian-handheld@lists.debian.org + + Description : Discussion among people who run Debian on + handheld computers. + Moderated : no + Subscription: open + + debian-ipv6@lists.debian.org + + Description : Discussions on the use of Debian in an IPv6 network + and implementing IPv6 support in Debian packages. + Moderated : no + Subscription: open + + debian-java@lists.debian.org + + Description : Discussion about the packaging and use in Debian of VMs + and compilers for the Java(tm) language, and programs + written on it. + Moderated : no + Subscription: open + + debian-jr@lists.debian.org + + Description : Discussion and working on making Debian the sort + of operating system that children will want to use. + + The Debian Jr. Project web page is at + http://www.debian.org/devel/debian-jr/ + Moderated : no + Subscription: open + + debian-kernel@lists.debian.org + + Description : Discussion about kernels used with Debian (Linux, Hurd, + etc.), available patches and flavors, packaging issues, + bug reports, porting issues, automated tools, and any + other questions or patches that are kernel-related. + Moderated : no + Subscription: open + + debian-knoppix@lists.debian.org + + Description : Development of the Debian-based live CD/DVD takes place. As it is mainly a + development list, user questions are best placed on the debian-user list. + Moderated : no + Subscription: open + + debian-lex@lists.debian.org + + Description : Discussion on developing Debian into an operating + system that is particularly well fit for the + requirements for legal offices. The goal of + Debian-Lex is a complete system for all tasks in + legal practice which is built completely on free + software. + Moderated : no + Subscription: open + + debian-lint-maint@lists.debian.org + + Description : The maintenance of Debian "lint" tools like lintian or linda + is discussed on this list. This may or may not be limited to + bug reports regarding the checks. + Moderated : no + Subscription: open + + debian-lsb@lists.debian.org + + Description : Discussion and coordination of efforts towards ensuring + Debian meets the requirements of the Linux Standard Base. + Moderated : no + Subscription: open + + debian-med@lists.debian.org + + Description : Discussion on providing a free operating system + for medical care. + + The Debian-Med Project web page is at + http://www.debian.org/devel/debian-med/ + Moderated : no + Subscription: open + + debian-mentors@lists.debian.org + + Description : Newbie Debian developers can seek help with + packaging and other developer-related issues here. + + This list is not meant for users' questions, + but for new maintainers'! + Moderated : no + Subscription: open + + debian-multimedia@lists.debian.org + + Description : Discussion about the development of applications + that produce multimedia content, handling multimedia + data, supporting multimedia hardware etc. + Moderated : no + Subscription: open + + debian-newmaint@lists.debian.org + + Description : Discussion about the Debian New Maintainer process, + application manager reports etc. + Moderated : no + Subscription: open + + debian-nonprofit@lists.debian.org + + Description : Discussions about the subproject to support + use of Debian in non-profit organizations. + Moderated : no + Subscription: open + + debian-ocaml-maint@lists.debian.org + + Description : Packaging of Objective Caml programs and libraries. + (http://pauillac.inria.fr/caml/) + Moderated : no + Subscription: open + + debian-openoffice@lists.debian.org + + Description : Coordination of the maintenance of the OpenOffice + packages in Debian. + Moderated : no + Subscription: open + + debian-perl@lists.debian.org + + Description : The list is dedicated to coordinate the work of various + perl package maintainer and to write a kind of perl + sub-policy. + Moderated : no + Subscription: open + + debian-policy@lists.debian.org + + Description : Discussion and editing of the Debian Policy Manual. + Moderated : no + Subscription: open + + debian-printing@lists.debian.org + + Description : Discussion of issues related to printing on Debian systems. This + covers all aspects of printing, from spoolers, to RIPs and printer + drivers. The list is used for coordination of development, + integration and bugfixing of printing packages between package + maintainers. User printing and printing setup questions are also + on topic. + Moderated : no + Subscription: open + + debian-private@lists.debian.org + + Description : Private discussions among developers: only for + issues that may not be discussed on public lists. + + Anything sent there should be treated as sensitive + and not to be spread to other lists; thus + cross-posting between it and an open list defeats + the purpose of this list. + + This list is archived internally on a Debian Project + machine, only developers have access to the archive. + Moderated : no + Subscription: developers only + + debian-python@lists.debian.org + + Description : Discussion of issues related to Python on Debian + systems with a stress on packaging standards. Therefore + relevant for maintainers of Python related packages. + Moderated : no + Subscription: open + + debian-qa-packages@lists.debian.org + + Description : Bug reports against orphaned packages and discussions + about fixing them. + Moderated : no + Subscription: open + + debian-qa@lists.debian.org + + Description : Quality assurance is important for a distribution. This + list addresses this quality. + Moderated : no + Subscription: open + + debian-qt-kde@lists.debian.org + + Description : Discussion and coordination among maintainers of + Debian's Qt, KDE and dependent or related packages. + Moderated : no + Subscription: open + + debian-release@lists.debian.org + + Description : Coordination of Debian releases issues such as testing migrations, transitions + and removals. + + This list should not be considered a discussion list; discussions related to + releases issues should be held on more appropriate lists such as debian-devel, + debian-legal or debian-project. + Moderated : no + Subscription: open + + debian-ruby@lists.debian.org + + Description : Discussion of issues related to Ruby on Debian systems + with a stress on packaging standards. Therefore + relevant for maintainers of Ruby related packages. + Moderated : no + Subscription: open + + debian-science@lists.debian.org + + Description : Discussion of issues relating to the use of Debian for science research, + including useful packages, particular problems faced by scientists using + Debian, how to make Debian more useful to scientists, etc. + Moderated : no + Subscription: open + + debian-security@lists.debian.org + + Description : Discussion about security issues, including + cryptographic issues, that are of interest to + all parts of the Debian community. + + Please note that this is NOT an announcement + mailing list. If you're looking for security + advisories from Debian, subscribe to + debian-security-announce instead. + Moderated : no + Subscription: open + + debian-sgml@lists.debian.org + + Description : Discussion of issues related to SGML on Debian systems + with a stress on proper integration of tools, packaging + standards and the writing of documentation for SGML + users. Therefore relevant for maintainers of SGML + related packages. + Moderated : no + Subscription: open + + debian-ssh@lists.debian.org + + Description : Maintenance of the OpenSSH packages for Debian. + It exists to facilitate coordination of ssh + maintenance (talking to upstream, reproducing bugs, + hacking on the code, etc.). + + It is *not* the place to mail bug reports + (use the BTS for that), nor support requests. + Moderated : no + Subscription: open + + debian-testing@lists.debian.org + + Description : Finding problems with the next Debian release: + testing the installation and the upgrade process. + Moderated : no + Subscription: open + + debian-tetex-maint@lists.debian.org + + Description : Coordination of the maintenance of Debian teTeX + and related packages. + + It is not meant for user support; for that, please + use debian-user or one of the general TeX mailing + lists or news groups. + Moderated : no + Subscription: open + + debian-tex-maint@lists.debian.org + + Description : Coordination of the maintenance of Debian TeX + and related packages. + + It is not meant for user support; for that, please + use debian-user or one of the general TeX mailing + lists or news groups. + Moderated : no + Subscription: open + + debian-toolchain@lists.debian.org + + Description : Discussion about the Debian toolchain: compilers, + assemblers, linkers and such. New releases for + many of these tools are coordinated here. + Moderated : no + Subscription: open + + debian-vote@lists.debian.org + + Description : Proposals, discussions and announcements related to + Official Debian Votes. + Moderated : no + Subscription: open + + debian-webapps@lists.debian.org + + Description : This list is used to coordinate the maintenance of web application packages. + Moderated : no + Subscription: open + + debian-wnpp@lists.debian.org + + Description : Orphaning and adopting packages which is done through + the `wnpp' BTS pseudo-package is recorded on this + list. Additionally, discussion about particular bugs + and the WNPP web pages is held here. + Moderated : no + Subscription: open + + debian-www-cvs@lists.debian.org + + Description : CVS commit logs for the Debian web pages in the + webwml CVS tree. + Moderated : yes + Subscription: open + + debian-www@lists.debian.org + + Description : Design, structure and translation of Debian + web pages. All important changes to the web + site are announced here as well. + Moderated : no + Subscription: open + + debian-x@lists.debian.org + + Description : Discussion about the X Window System within Debian. + This is NOT a user support list; this list is + intended for those who deal with the source code. + Moderated : no + Subscription: open + + deity@lists.debian.org + + Description : Debian GNU/Linux will get a new, friendly frontend to + its package maintenance system. Its codename is deity + (now known as APT) and its development is discussed + here. The -digest is open to everyone. + Moderated : no + Subscription: open + +Internationalization and Translations + + These lists cover issues like localization, translation and support for + users that don't speak English. + + debian-i18n@lists.debian.org + + Description : Internationalization (i18n) of the distribution is + discussed here. + Moderated : no + Subscription: open + + debian-l10n-arabic@lists.debian.org + + Description : Discussing Arabic localization issues, mainly + translating Debian docs and programs to Arabic. + Language : Arabic + Moderated : no + Subscription: open + + debian-l10n-catalan@lists.debian.org + + Description : Discussing Catalan localization issues, mainly + translating Debian docs and programs to Catalan. + Language : Catalan + Moderated : no + Subscription: open + + debian-l10n-czech@lists.debian.org + + Description : Discussion forum for the translators of + Debian-specific packages and documentation to the Czech language. + Moderated : no + Subscription: open + + debian-l10n-danish@lists.debian.org + + Description : Discussing Danish localization issues, mainly + translating Debian docs and programs to Danish. + Language : Danish + Moderated : no + Subscription: open + + debian-l10n-dutch@lists.debian.org + + Description : Discussion forum for the translators of Debian-specific + packages and documentation to the Dutch language. + Language : Dutch + Moderated : no + Subscription: open + + debian-l10n-english@lists.debian.org + + Description : Discussing English localization issues, mainly + translating Debian docs and programs to English. + Language : English + Moderated : no + Subscription: open + + debian-l10n-esperanto@lists.debian.org + + Description : Discussing Esperanto localization issues, mainly + translating Debian docs and programs to Esperanto. + Language : Esperanto + Moderated : no + Subscription: open + + debian-l10n-finnish@lists.debian.org + + Description : Discussing Finnish localization issues, mainly + translating Debian docs and programs to Finnish. + Language : Finnish + Moderated : no + Subscription: open + + debian-l10n-french@lists.debian.org + + Description : Discussion forum for the translators of Debian-specific + packages and documentation to the French language. + Language : French + Moderated : no + Subscription: open + + debian-l10n-german@lists.debian.org + + Description : Discussing German localization issues, mainly + translating Debian docs and programs to German. + Language : German + Moderated : no + Subscription: open + + debian-l10n-greek@lists.debian.org + + Description : Discussion on Greek localization issues, mainly + translating Debian docs and programs to Greek. + Language : Greek + Moderated : no + Subscription: open + + debian-l10n-hungarian@lists.debian.org + + Description : Discussing Hungarian localization issues, mainly + translating Debian docs and programs to Hungarian. + Language : Hungarian + Moderated : no + Subscription: open + + debian-l10n-italian@lists.debian.org + + Description : Italian localization efforts within Debian. + Language : Italian + Moderated : no + Subscription: open + + debian-l10n-korean@lists.debian.org + + Description : Discussion forum for the translators of Debian-specific packages and + documentation to the Korean language. + Moderated : no + Subscription: open + + debian-l10n-polish@lists.debian.org + + Description : Polish localization issues, mainly translating Debian + web pages, documentation and programs to Polish. + Language : Polish + Moderated : no + Subscription: open + + debian-l10n-portuguese@lists.debian.org + + Description : Portuguese localization issues such as translating + the documentation and programs. + Language : Portuguese + Moderated : no + Subscription: open + + debian-l10n-romanian@lists.debian.org + + Description : Discussing Romanian localization issues, mainly + translating Debian docs and programs to Romanian. + Language : Romanian + Moderated : no + Subscription: open + + debian-l10n-russian@lists.debian.org + + Description : Discussing Russian localization issues, mainly + translating Debian docs and programs to Russian. + Language : Russian + Moderated : no + Subscription: open + + debian-l10n-spanish@lists.debian.org + + Description : Discussing Spanish localization issues, mainly + translating Debian docs and programs to Spanish. + Language : Spanish + Moderated : no + Subscription: open + + debian-l10n-swedish@lists.debian.org + + Description : Discussion forum for translators of Debian-specific packages + and documentation for the Swedish language. + Moderated : no + Subscription: open + + debian-l10n-turkish@lists.debian.org + + Description : Discussing Turkish localization issues, mainly + translating Debian docs and website into Turkish, + improving Turkish environment support in Debian. + Language : Turkish + Moderated : no + Subscription: open + + debian-laespiral@lists.debian.org + + Description : La Espiral (http://laespiral.org/) is a project + meant to promote the use of Debian amongst the + people who speak Spanish. We work on custom + Debian internationalisation CDs, do installation + parties and new programs for Spanish users (see + http://www.debian.org/international/spanish/). + + Becoming a member of La Espiral is for people + that do not find themselves able to contribute + technically to Debian (at first), but might be a + good step towards becoming a Debian developer. + Language : Spanish + Moderated : no + Subscription: open + +Ports to non-i386 Linux architectures and to non-Linux kernels + + Debian GNU/Linux is ported to several other types of computers, and there + are also efforts to create Debian systems on kernels other than Linux. + + debian-68k@lists.debian.org + + Description : Discussions on the m68k port of Debian GNU/Linux. + Moderated : no + Subscription: open + + debian-alpha@lists.debian.org + + Description : Discussion on the Alpha port of Debian GNU/Linux. + Moderated : no + Subscription: open + + debian-amd64@lists.debian.org + + Description : Porting Debian to AMD x86-64 architecture. + Moderated : no + Subscription: open + + debian-arm@lists.debian.org + + Description : Discussion on the ARM (esp. Corel Netwinder) port for + Debian GNU/Linux. + Moderated : no + Subscription: open + + debian-bsd@lists.debian.org + + Description : Porting Debian to BSD (all *BSD variants). + Moderated : no + Subscription: open + + debian-hppa@lists.debian.org + + Description : Discussions on the PA-RISC port of Debian GNU/Linux. + Moderated : no + Subscription: open + + debian-hurd@lists.debian.org + + Description : Debian port of the GNU Hurd operating system. + Moderated : no + Subscription: open + + debian-ia64@lists.debian.org + + Description : Discussions on the intel IA64 (aka Itanium, Merced) + port of Debian GNU/Linux. + Moderated : no + Subscription: open + + debian-mips@lists.debian.org + + Description : Discussions on the MIPS port of Debian GNU/Linux. + Moderated : no + Subscription: open + + debian-powerpc@lists.debian.org + + Description : Discussion on the PowerPC port of Debian GNU/Linux. + Moderated : no + Subscription: open + + debian-s390@lists.debian.org + + Description : Discussions on the IBM S/390 port of Debian GNU/Linux. + Moderated : no + Subscription: open + + debian-sparc@lists.debian.org + + Description : Discussions on the SPARC port of Debian GNU/Linux. + Moderated : no + Subscription: open + + debian-superh@lists.debian.org + + Description : Discussions on the SuperH port of Debian GNU/Linux. For + more information about running Linux on SH processors, + have a look at http://www.m17n.org/linux-sh/ + Moderated : no + Subscription: open + + debian-win32@lists.debian.org + + Description : Porting the Debian distribution to Win32 systems + (Debian GNU/Win32). + Moderated : no + Subscription: open + +The Bug Tracking System + + The Debian bug tracking system is open to the public, and it produces + a lot of email. Some of this might be of interest to developers or even + users, so it is distributed through these (high-volume) mailing lists. + + debian-bugs-closed@lists.debian.org + + Description : Messages that close Debian bug reports. + Moderated : no + Subscription: open + + debian-bugs-dist@lists.debian.org + + Description : All submitted bug reports as well as further information + on them are distributed here. + Moderated : no + Subscription: open + + debian-bugs-forwarded@lists.debian.org + + Description : Mails in which Debian maintainers forward bugs + to their upstream authors. + Moderated : no + Subscription: open + + debian-bugs-rc@lists.debian.org + + Description : All mail regarding release-critical bugs is + copied to this mailing list. + + See http://bugs.debian.org/release-critical/ + for more information. + Moderated : no + Subscription: open + +Miscellaneous Debian lists + + There are several mailing lists which don't + necessarily have a clear distinction in the + audience, between developers and users. + + debian-all-changes@lists.debian.org + + Description : Notices about uploaded binary-all packages for the + stable distribution. + Moderated : no + Subscription: open + + debian-alpha-changes@lists.debian.org + + Description : Notices about uploaded packages for the stable alpha + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-arm-changes@lists.debian.org + + Description : Notices about uploaded packages for the stable arm + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-cd-vendors@lists.debian.org + + Description : Communication among and with vendors of Debian CDs. + (Low-volume mailing list.) + Moderated : no + Subscription: open + + debian-changes@lists.debian.org + + Description : Changes to the releases are announced here. This + includes security upgrades as well as important + bugfixes. + Digest : debian-changes-digest@lists.debian.org + Moderated : yes + Subscription: open + + debian-consultants@lists.debian.org + + Description : Communication among Debian consultants. See at the bottom of the + consultants page (http://www.debian.org/consultants/#policy) for how + to add/update entries to this page. + Moderated : no + Subscription: open + + debian-curiosa@lists.debian.org + + Description : Funny thing from and with the project, funny quotes, + discussions irc communication and fortune cookies. + Some kind of (de.)alt.netdigest for Debian-related stuff. + Moderated : no + Subscription: open + + debian-devel-all-changes@lists.debian.org + + Description : Notices about uploaded packages for the unstable + distribution. (Quiz: binary-all or all binaries?) + Moderated : no + Subscription: open + + debian-devel-alpha-changes@lists.debian.org + + Description : Notices about uploaded packages for the unstable alpha + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-devel-arm-changes@lists.debian.org + + Description : Notices about uploaded packages for the unstable arm + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-devel-changes@lists.debian.org + + Description : Notices about uploaded packages for the unstable + distribution, from developers, buildds and katie, + the archive sentinel. + (High-volume mailing list.) + Moderated : no + Subscription: open + + debian-devel-hurd-i386-changes@lists.debian.org + + Description : Notices about uploaded packages for the unstable + hurd-i386 distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-devel-i386-changes@lists.debian.org + + Description : Notices about uploaded packages for the unstable i386 + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-devel-m68k-changes@lists.debian.org + + Description : Notices about uploaded packages for the unstable m68k + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-devel-powerpc-changes@lists.debian.org + + Description : Notices about uploaded packages for the unstable powerpc + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-devel-s390-changes@lists.debian.org + + Description : Notices about uploaded packages for the unstable s390 + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-devel-sparc-changes@lists.debian.org + + Description : Notices about uploaded packages for the unstable sparc + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-hurd-i386-changes@lists.debian.org + + Description : Notices about uploaded packages for the stable hurd-i386 + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-i386-changes@lists.debian.org + + Description : Notices about uploaded packages for the stable i386 + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-jobs@lists.debian.org + + Description : Job postings can be published on this list in + order to make them public to members of the Debian + community. While the jobs do not necessarily have + to involve the use of Debian, it is encouraged that + they do. Jobs can be about the development of + proprietary system, but jobs involving free software + (either development or system administration) are + preferred. Please include information such as + location and remuneration if appropriate. The list + is moderated; it is also an open list - job postings + which have to be kept private should be sent to + leader@debian.org who will distribute them. + Moderated : yes + Subscription: open + + debian-legal@lists.debian.org + + Description : Discussions about legality issues such as + copyrights, patents etc. + Moderated : no + Subscription: open + + debian-m68k-changes@lists.debian.org + + Description : Notices about uploaded packages for the stable m68k + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-mirrors-announce@lists.debian.org + + Description : Important changes to the FTP archive are announced here. + These are mainly useful to maintainers of Debian + mirrors. + Moderated : yes + Subscription: open + + debian-mirrors@lists.debian.org + + Description : Discussions relating to the Debian mirror network, + and the maintenance of mirrors. + Moderated : no + Subscription: open + + debian-powerpc-changes@lists.debian.org + + Description : Notices about uploaded packages for the stable powerpc + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-project@lists.debian.org + + Description : Discussion about non-technical topics related + to the Debian Project. + Moderated : no + Subscription: open + + debian-publicity@lists.debian.org + + Description : Coordination of all the work related to the external + communication of Debian: drafting new announces, + collecting important information that Debian should relay + to its community, improving the infrastructure offered to + people who want to create Debian booth, etc. + Moderated : no + Subscription: open + + debian-s390-changes@lists.debian.org + + Description : Notices about uploaded packages for the stable s390 + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-sparc-changes@lists.debian.org + + Description : Notices about uploaded packages for the stable sparc + distribution, mostly from buildd's. + Moderated : no + Subscription: open + + debian-testing-changes@lists.debian.org + + Description : Changes to the "testing" distribution are announced + here. This includes various bugfixes. + Moderated : no + Subscription: open + + debian-women@lists.debian.org + + Description : Debian users and developers who wish to involve more + women in the Debian project. For discussion and + sharing of ideas as well as project collaboration. + Moderated : no + Subscription: open + + whitelist@lists.debian.org + + Description : This is a special pseudo-mailing list to which + people can subscribe to prove they are not + spammers. + + This allows one to avoid the restrictions imposed + on non-subscriber posts to other mailing lists, + in particular the mailing lists that allow posts + only from subscribers. + Moderated : yes + Subscription: open + +Lists hosted for other projects + + Our list server provides mailing list facilities for other free + projects as well. + + other-cdwrite@lists.debian.org + + Description : cdwrite mailing list + Moderated : no + Subscription: open + + other-sart@lists.debian.org + + Description : Discussions and announcements about SART, + a free raytracer that uses Guile extension + language and is distributed under GPL. + + The SART website is at + http://petra.zesoi.fer.hr/~silovic/sart/ + Moderated : no + Subscription: open + + other-vgui-discuss@lists.debian.org + + Description : The V C++ GUI Framework - an object-oriented GUI library + for X, Win32 and OS/2. V is licensed under the GNU + LGPL. The web page is at http://www.objectcentral.com/ . + Moderated : no + Subscription: open + + +Debian mailing list advertising policy +-------------------------------------- + + This policy is intended to fight mailing-list "spamming". + + The Debian mailing lists accept commercial advertising for payment. The fee + for advertisments is a donation of USD 1000 or more to "Software in the + Public Interest" (SPI). One donation per advertisement, please. If you + prefer to pay in arrears, simply post your advertisement to the list, and + the list operator will bill you USD 1999. The list operator will donate + this amount, minus the expense of collecting it, to SPI. Please note that + the lists are distributed automatically -- messages are generally not read + or checked in any way before they are distributed. + + The act of posting an advertisement indicates your willingness to + * accept responsibility for the fee, + * indemnify the list operator against any legal claims from you or + others in connection with your advertisement, and + * pay any legal and business expenses incurred in collecting late payment. + Our liability to you is limited to a good-faith effort to deliver your + message. + + Reduced rates and/or waiver of fee are available for Debian-related + advertisements. You must consult the list operator in advance of posting for + any reduction or fee waiver. + +-- +Online HTML version of this document is available at + http://www.debian.org/MailingLists/subscribe diff --git a/includes/common/doc/social-contract.txt b/includes/common/doc/social-contract.txt new file mode 100644 index 0000000..cd9c368 --- /dev/null +++ b/includes/common/doc/social-contract.txt @@ -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". + + ------------------------------------------------------------------------ diff --git a/includes/common/doc/source-unpack.txt b/includes/common/doc/source-unpack.txt new file mode 100644 index 0000000..151b733 --- /dev/null +++ b/includes/common/doc/source-unpack.txt @@ -0,0 +1,33 @@ + HOW TO UNPACK A DEBIAN SOURCE PACKAGE + +There are two kinds of Debian source packages: old ones and new ones. + +A. Old ones look like this: + hello-1.3-4.tar.gz + hello-1.3-4.diff.gz + You unpack them by untarring the .tar.gz. There is NO need to apply + the diff. + +B. New ones look like this: + hello_1.3-11.dsc + hello_1.3-11.diff.gz + hello_1.3-11.orig.tar.gz - note the `.orig' part + Here you MUST use dpkg-source or apply the diff manually - see below. + + If you have `dpkg-source' you should put the files in the same + directory and type `dpkg-source -x .dsc'. + + If you do not you can extract the Debian source as follows: + 1. untar P_V.orig.tar.gz. + 2. rename the resulting P-V.orig directory to P-V. If some other + directory results, rename *it* to P-V. + 3. mkdir P-V/debian. + 4. apply the diff with patch -p0. + 5. do `chmod +x P-V/debian/rules' + (where P is the package name and V the version.) + +C. There are some packages where the Debian source is the upstream + source. In this case there will be no .diff.gz and you can just use + the .tar.gz. If a .dsc is provided you can use `dpkg-source -x'. + + -- Ian Jackson Sat, 31 Aug 1996 diff --git a/includes/common/pics/blue-lowerleft.png b/includes/common/pics/blue-lowerleft.png new file mode 100644 index 0000000..2a2245e Binary files /dev/null and b/includes/common/pics/blue-lowerleft.png differ diff --git a/includes/common/pics/blue-lowerright.png b/includes/common/pics/blue-lowerright.png new file mode 100644 index 0000000..7e66271 Binary files /dev/null and b/includes/common/pics/blue-lowerright.png differ diff --git a/includes/common/pics/blue-upperleft.png b/includes/common/pics/blue-upperleft.png new file mode 100644 index 0000000..a58d0ec Binary files /dev/null and b/includes/common/pics/blue-upperleft.png differ diff --git a/includes/common/pics/blue-upperright.png b/includes/common/pics/blue-upperright.png new file mode 100644 index 0000000..2f36849 Binary files /dev/null and b/includes/common/pics/blue-upperright.png differ diff --git a/includes/common/pics/debian.jpg b/includes/common/pics/debian.jpg new file mode 100644 index 0000000..db62d7a Binary files /dev/null and b/includes/common/pics/debian.jpg differ diff --git a/includes/common/pics/logo-50.jpg b/includes/common/pics/logo-50.jpg new file mode 100644 index 0000000..542f0a4 Binary files /dev/null and b/includes/common/pics/logo-50.jpg differ diff --git a/includes/common/pics/red-lowerleft.png b/includes/common/pics/red-lowerleft.png new file mode 100644 index 0000000..caca9c5 Binary files /dev/null and b/includes/common/pics/red-lowerleft.png differ diff --git a/includes/common/pics/red-lowerright.png b/includes/common/pics/red-lowerright.png new file mode 100644 index 0000000..c27056c Binary files /dev/null and b/includes/common/pics/red-lowerright.png differ diff --git a/includes/common/pics/red-upperleft.png b/includes/common/pics/red-upperleft.png new file mode 100644 index 0000000..c1e3301 Binary files /dev/null and b/includes/common/pics/red-upperleft.png differ diff --git a/includes/common/pics/red-upperright.png b/includes/common/pics/red-upperright.png new file mode 100644 index 0000000..54d17ca Binary files /dev/null and b/includes/common/pics/red-upperright.png differ diff --git a/includes/common/tools/README b/includes/common/tools/README new file mode 100644 index 0000000..bc56f93 --- /dev/null +++ b/includes/common/tools/README @@ -0,0 +1,13 @@ +/debian/tools contains MS-DOS tools for installing and booting Linux. + +fips20.zip Non-destructively split harddisk partitions (works with FAT32) +gzip124.exe gzip for DOS +lodlin16.zip load Linux kernel from DOS +rawrite1.zip rawrite version 1.3 (rawrite 2.0 is much faster, but +rawrite2.zip rawrite version 2.0 it locks up on some machines.) +unz512x3.exe Info-ZIP's free UnZipper for DOS +rwwrtwin.zip Win32 version of rawrite runs on Windows 95, NT, 98, 2000, + ME, XP and probably later versions. +diskio.zip Under 95, 98 & ME you need diskio.dll. It must be in + the same directory as rwwrtwin.exe. (uncompressed) +md5sum-w32.zip Win32 version of md5sum diff --git a/includes/common/tools/diskio.zip b/includes/common/tools/diskio.zip new file mode 100644 index 0000000..b30fa96 Binary files /dev/null and b/includes/common/tools/diskio.zip differ diff --git a/includes/common/tools/fips20.zip b/includes/common/tools/fips20.zip new file mode 100644 index 0000000..c4a64b6 Binary files /dev/null and b/includes/common/tools/fips20.zip differ diff --git a/includes/common/tools/gzip124.exe b/includes/common/tools/gzip124.exe new file mode 100644 index 0000000..1a8d137 Binary files /dev/null and b/includes/common/tools/gzip124.exe differ diff --git a/includes/common/tools/lodlin16.zip b/includes/common/tools/lodlin16.zip new file mode 100644 index 0000000..1e5441e Binary files /dev/null and b/includes/common/tools/lodlin16.zip differ diff --git a/includes/common/tools/md5sum-w32.zip b/includes/common/tools/md5sum-w32.zip new file mode 100644 index 0000000..982202b Binary files /dev/null and b/includes/common/tools/md5sum-w32.zip differ diff --git a/includes/common/tools/rawrite1.zip b/includes/common/tools/rawrite1.zip new file mode 100644 index 0000000..abdc229 Binary files /dev/null and b/includes/common/tools/rawrite1.zip differ diff --git a/includes/common/tools/rawrite2.zip b/includes/common/tools/rawrite2.zip new file mode 100644 index 0000000..aa33885 Binary files /dev/null and b/includes/common/tools/rawrite2.zip differ diff --git a/includes/common/tools/rwwrtwin.zip b/includes/common/tools/rwwrtwin.zip new file mode 100644 index 0000000..2c3fd11 Binary files /dev/null and b/includes/common/tools/rwwrtwin.zip differ diff --git a/includes/common/tools/src/md5sum-w32_1.1.dsc b/includes/common/tools/src/md5sum-w32_1.1.dsc new file mode 100644 index 0000000..44393f8 --- /dev/null +++ b/includes/common/tools/src/md5sum-w32_1.1.dsc @@ -0,0 +1,25 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA1 + +Format: 1.0 +Source: md5sum-w32 +Version: 1.1 +Binary: md5sum-w32 +Maintainer: Bas Zoetekouw +Architecture: any +Standards-Version: 3.5.2 +Build-Depends: debhelper (>> 3.0.0), mingw32, zip +Files: + b5741a5c7e027ee1e9242163c5eb711b 7617 md5sum-w32_1.1.tar.gz + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.0.7 (GNU/Linux) + +iQEXAwUBPXo9/Z6S+2TcVAFTFAKpcwP/bDWljR/VQxCFtjg4epqZczN5MRWHQ0Qc +qjRw5F0of0V0jELCVClRGl68VBX96o3tJSGvhCkXqT3UXQYd1vsiakHQotcEib3V +r07De88Bzxm9NE43AR/98TU+9niIkrOmkbxGJQXU3puKMXd/WpCw4XgNOYT6A1hg +7ugByZ32x9ID/RtIpCehPvrqCVn8J1v2dTam3m3obGt6yESg+2PcxzEeIVwN3jb3 +AwkLTKi7VyelSmMWPdJUxsMZvGmBFyjjNqwZeMYPnuGS60sHxREHA/heDsM1hIbS +7PZ9hcPXw588Y79ItGFZY4Rfdc0cJQSTkPvt2z5gAk1Eeii5kzCC25nZ +=aPY9 +-----END PGP SIGNATURE----- diff --git a/includes/common/tools/src/md5sum-w32_1.1.tar.gz b/includes/common/tools/src/md5sum-w32_1.1.tar.gz new file mode 100644 index 0000000..bf42ec8 Binary files /dev/null and b/includes/common/tools/src/md5sum-w32_1.1.tar.gz differ diff --git a/includes/common/tools/unz512x3.exe b/includes/common/tools/unz512x3.exe new file mode 100644 index 0000000..e8b36c8 Binary files /dev/null and b/includes/common/tools/unz512x3.exe differ diff --git a/includes/iso/autorun.bat b/includes/iso/autorun.bat new file mode 100644 index 0000000..4718afe --- /dev/null +++ b/includes/iso/autorun.bat @@ -0,0 +1,3 @@ +@echo Starting "README.html"... +@start README.html +@exit diff --git a/includes/iso/autorun.inf b/includes/iso/autorun.inf new file mode 100644 index 0000000..1b28f75 --- /dev/null +++ b/includes/iso/autorun.inf @@ -0,0 +1,2 @@ +[autorun] +open=autorun.bat diff --git a/includes/usb/autorun.bat b/includes/usb/autorun.bat new file mode 100644 index 0000000..4718afe --- /dev/null +++ b/includes/usb/autorun.bat @@ -0,0 +1,3 @@ +@echo Starting "README.html"... +@start README.html +@exit diff --git a/includes/usb/autorun.inf b/includes/usb/autorun.inf new file mode 100644 index 0000000..1b28f75 --- /dev/null +++ b/includes/usb/autorun.inf @@ -0,0 +1,2 @@ +[autorun] +open=autorun.bat diff --git a/lists/gnome b/lists/gnome new file mode 100644 index 0000000..c7ac989 --- /dev/null +++ b/lists/gnome @@ -0,0 +1,16 @@ +# /usr/share/make-live/lists/gnome - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# GNOME +gdm gdm-themes gnome-desktop-environment gnome-cups-manager gnome-screensaver +gnome-themes-extras +desktop-base + +rhythmbox synaptic + +xorg xresprobe diff --git a/lists/gnome-core b/lists/gnome-core new file mode 100644 index 0000000..8d34c63 --- /dev/null +++ b/lists/gnome-core @@ -0,0 +1,13 @@ +# /usr/share/make-live/lists/gnome-core - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# GNOME Core +gdm gnome-core +desktop-base + +xorg xresprobe diff --git a/lists/gnome-full b/lists/gnome-full new file mode 100644 index 0000000..f5e1c3e --- /dev/null +++ b/lists/gnome-full @@ -0,0 +1,13 @@ +# /usr/share/make-live/lists/gnome-full - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# GNOME Full +gdm gnome +desktop-base + +xorg xresprobe diff --git a/lists/gnome-junior b/lists/gnome-junior new file mode 100644 index 0000000..facf95d --- /dev/null +++ b/lists/gnome-junior @@ -0,0 +1,22 @@ +# /usr/share/make-live/lists/gnome - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# GNOME +gdm gdm-themes gnome-desktop-environment gnome-cups-manager gnome-screensaver +gnome-themes-extras +desktop-base + +rhythmbox synaptic + +xorg xresprobe + +# Debian Junior +junior-sound junior-typing junior-internet junior-gnome junior-toys +junior-games-net junior-games-sim junior-games-gl junior-puzzle junior-arcade +junior-math junior-writing junior-games-card junior-programming junior-system +junior-art junior-doc junior-games-text diff --git a/lists/gnustep b/lists/gnustep new file mode 100644 index 0000000..653be15 --- /dev/null +++ b/lists/gnustep @@ -0,0 +1,31 @@ +# /usr/share/make-live/lists/x11-core - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# X11 +xorg xresprobe + +# GNUstep +wdm + +gnustep gnumail.app talksoup.app viewpdf.app wmaker gnustep-icons +gnustep-examples gnumail-doc aclock.app biococoa.app timemon.app cenon.app wmnd +bubblefishymon wmmixer wmpinboard gworkspace.app clipbook.app poe.app +plopfolio.app mpdcon.app lusernet.app helpviewer.app gnuwash.app easydiff.app +displaycalibrator.app cynthiune.app agenda.app stepulator.app edenmath.app +price.app volumecontrol.app latex.service wildmenus.bundle innerspace.app + +gnustep-core + +gnustep-core-devel gnustep-base-examples + +gnustep-core-doc gnustep-tutorial-html gnustep-tutorial-pdf + +gnustep-games gridlock.app + +gnustep-devel librenaissance0-dev steptalk libpantomime1-dev +popplerkit.framework gnustep-netclasses diff --git a/lists/kde b/lists/kde new file mode 100644 index 0000000..7bfd909 --- /dev/null +++ b/lists/kde @@ -0,0 +1,13 @@ +# /usr/share/make-live/lists/kde - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# KDE +kde kdm +desktop-base + +xorg xresprobe diff --git a/lists/kde-core b/lists/kde-core new file mode 100644 index 0000000..14ac905 --- /dev/null +++ b/lists/kde-core @@ -0,0 +1,13 @@ +# /usr/share/make-live/lists/kde-core - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# KDE Core +kde-core kdm +desktop-base + +xorg xresprobe diff --git a/lists/kde-extra b/lists/kde-extra new file mode 100644 index 0000000..2b47a2b --- /dev/null +++ b/lists/kde-extra @@ -0,0 +1,19 @@ +# /usr/share/make-live/lists/kde-extra - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# KDE +kde kdm +desktop-base + +xorg xresprobe + +# KDE Full +koffice + +# KDE Extra +kde-extras diff --git a/lists/kde-full b/lists/kde-full new file mode 100644 index 0000000..1ce47e5 --- /dev/null +++ b/lists/kde-full @@ -0,0 +1,16 @@ +# /usr/share/make-live/lists/kde-full - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# KDE +kde kdm +desktop-base + +xorg xresprobe + +# KDE Full +koffice diff --git a/lists/kde-junior b/lists/kde-junior new file mode 100644 index 0000000..da159e5 --- /dev/null +++ b/lists/kde-junior @@ -0,0 +1,19 @@ +# /usr/share/make-live/lists/kde - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# KDE +kde kdm +desktop-base + +xorg xresprobe + +# Debian Junior +junior-sound junior-typing junior-internet junior-toys junior-games-net +junior-games-sim junior-games-gl junior-puzzle junior-arcade junior-math +junior-writing junior-games-card junior-programming junior-system junior-art +junior-doc junior-games-text junior-kde diff --git a/lists/knoppix b/lists/knoppix new file mode 100644 index 0000000..e981fd7 --- /dev/null +++ b/lists/knoppix @@ -0,0 +1,1292 @@ +# /usr/share/make-live/lists/gnome - package list for make-live(1) +# + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# X11 +desktop-base xresprobe + +# Knoppix packages +# URL: http://ftp.kernel.org/pub/dist/knoppix/packages.txt +0wn +aalib-bin +aalib1 +ace-of-penguins +acpi +adduser +adtool +aespipe +afio +airsnort +alevt +alien +alsa-base +alsa-utils +amanda-client +amanda-common +amanda-server +anacron +apache2 +apache2-mpm-prefork +apache2-utils +apache2.2-common +apmd +apt +apt-file +apt-method-installed +apt-show-versions +apt-utils +arj +ark +arpwatch +artwiz-cursor +at +atitvout +atmel-firmware +attr +audacity +aufs-cvs-modules-2.6.19 +aufs-cvs-utils +aumix-gtk +autoconf +autofs +autotools-dev +autotrace +avm-firmware +base-files +base-passwd +bash +bb +bc +beryl +beryl-core +beryl-manager +beryl-plugins +beryl-plugins-data +beryl-settings +biew +bin86 +bind9 +bind9-host +binfmt-support +bing +binutils +binutils-dev +bittorrent +blt +bluetooth +bluez-firmware +bluez-utils +bochsbios +bonnie++ +bridge-utils +brltty +bsdiff +bsdmainutils +bsdutils +buffer +build-essential +busybox +bzip2 +ca-certificates +cabextract +capiutils +cdbackup +cdbs +cdda2wav +cddb +cdparanoia +cdrdao +cdrecord +checkmem +chkrootkit +clamav +clamav-base +clamav-freshclam +cloop-module-2.6.19 +hi +configure-xawtv +console-common +console-data +console-tools +convertfs +coreutils +cowsay +cpio +cpp +cpp-4.1 +cpuburn +cramfsprogs +cron +cryptcat +cryptsetup +cups-pdf +cupsys +cupsys-bsd +cupsys-client +cupsys-common +cupsys-driver-gutenprint +cvs +dante-client +dash +dbus +dc +dcraw +dctrl-tools +dd-rescue +dds2tar +debconf +debconf-i18n +debconf-utils +debfoster +debhelper +debian-archive-keyring +debianutils +debootstrap +deborphan +debsums +defoma +devscripts +dh-make +dhcp3-common +dhcp3-server +dialog +dict +dictionaries-common +dietlibc-dev +diff +diffstat +ding +distcc +dmidecode +dmraid +dmsetup +dnsutils +doc-base +docbook-xml +dosfstools +dpkg +dpkg-dev +dpkg-repack +drdsl +dselect +dsniff +dump +dupload +dvb-mpegtools +dvb-utils +dvbackup +dvbsnoop +dvbstream +dvbtune +dvd+rw-tools +dvdauthor +dvdbackup +dvgrab +e00compr +e2fslibs +e2fsprogs +ed +efax +eject +elinks +emerald +enscript +escputil +esound-common +etherwake +ethtool +ettercap-common +ettercap-gtk +euro-support +euro-support-console +expect +ext2resize +fakeroot +fb-music-low +fbi +fbset +fdflush +fdisk-udeb +fdutils +fetchmail +ffmpeg +file +fileutils +findutils +finger +firefox +fluxbox +fontconfig +fontconfig-config +foomatic-bin +foomatic-db +foomatic-db-engine +foomatic-db-gutenprint +foomatic-db-hpijs +foomatic-filters +foremost +fortune-mod +fortunes-debian-hints +fortunes-min +fping +freeglut3 +freemind +freenx +frozen-bubble +hi +ftp +ftpd +fttools +fuse-utils +g++ +g++-4.1 +gaim +gaim-data +gaim-encryption +gawk +gcc +gcc-3.3-base +gcc-4.1 +gcc-4.1-base +gconf2 +gconf2-common +gdb +genisoimage +genliloconf +gettext +gettext-base +gif2png +giflib-bin +giflib3g +giftrans +gimp +gimp-data +gimp-print +gksu +gnome-keyring +gnuchess +gnupg +gnupg2 +gocr +gpart +gparted +gpgsm +gpgv +gphoto2 +gpm +gpsdrive +gpstrans +gq +gqcam +grep +groff +groff-base +hi +grub-disk +gs-common +gs-esp +gscanbus +gsfonts +gsfonts-x11 +gsm-utils +gtans +gtk-smooth-themes +gtk2-engines +gtk2-engines-smooth +gtkam +gv +gzip +hal +hdparm +hexedit +hfsplus +hfsutils +hicolor-icon-theme +hostap-utils +hostapd +hostname +hpijs +hping2 +html2text +httptunnel +hunt +hwsetup +hwtools +i810switch +ibod +icedax +icedove +icedove-locale-de +iceweasel +iceweasel-l10n-de +icewm +icewm-common +icmpush +idswakeup +iftop +ifupdown +ijsgutenprint +imagemagick +imaze +imlib-base +imlib11 +info +infobash +ingerman +initramfs-tools +initrd-tools +initscripts +intltool-debian +ipcalc +ipchains +iperf +ipppd +iproute +ipsec-tools +iptables +iptraf +iputils-ping +iputils-tracepath +ipv6calc +ipw2100-nonfree +ipw2200-nonfree +ipx +irda-common +irda-tools +irssi +irssi-plugin-icq +irssi-scripts +isapnptools +isdnactivecards +isdnutils-base +isdnvboxclient +isomaster +ispell +java-common +jfsutils +joe +k3b +k3b-defaults +k3b-i18n +kaffeine +kalarm +kamera +kandy +kappfinder +kate +katomic +kbackup +kbackup-multibuf +kbattleship +kbdconfig +kcalc +kcharselect +kcontrol +kde-i18n-de +kde-i18n-es +kde-i18n-fr +kde-i18n-it +kde-i18n-ja +kde-i18n-nl +kde-i18n-pl +kde-i18n-tr +kdeaddons-kfile-plugins +kdeadmin-kfile-plugins +kdebase +kdebase-bin +kdebase-data +kdebase-kio-plugins +kdebluetooth +kdegraphics-kfile-plugin +kdelibs-data +kdelibs4c2a +kdemultimedia-kfile-plug +kdemultimedia-kio-plugin +kdenetwork-kfile-plugins +kdepasswd +kdepim-kfile-plugins +kdepim-kio-plugins +kdeprint +kdesktop +kdessh +kdf +kdm +kexec-tools +kfax +kfind +kfloppy +kget +kghostview +khelpcenter +khexedit +kicker +kiconedit +kismet +klaptopdaemon +klibc-utils +klipper +klogd +kmahjongg +kmail +kmailcvt +kmenuedit +kmix +knode +knotes +konq-plugins +konqueror +konqueror-nsplugins +konsole +konsolekalendar +kooka +kpackage +kpager +kpdf +kpersonalizer +kpf +kphone +kppp +krdc +kreversi +krfb +ksmserver +ksnapshot +ksokoban +ksplash +ksudoku +ksync +ksysguard +ksysguardd +ksysv +kteatime +ktimer +ktip +ktnef +ktuberling +kuickshow +kuser +kview +kviewshell +kwin +kwlan +laptop-detect +ldap-utils +lde +less +lesstif2 +lftp +lha +liba52-0.7.4 +libaa1 +libacl1 +libadns1 +libao2 +libapache2-mod-php4 +libapm1 +libapr1 +libaprutil1 +libapt-pkg-perl +libart-2.0-2 +libarts1c2a +libartsc0 +libasound2 +libaspell15 +libatk1.0-0 +libatm1 +libattr1 +libaudio2 +libaudiofile0 +libautotrace3 +libavahi-client3 +libavahi-common-data +libavahi-common3 +libavahi-compat-howl0 +libavahi-compat-libdnssd +libavahi-qt3-1 +libavc1394-0 +libavcodec0d +libavformat0d +libbeecrypt6 +libberylsettings0 +libbind9-0 +libblkid1 +libbluetooth2 +libbz2-1.0 +libc6 +libc6-dev +libcaca0 +libcairo2 +libcap1 +libcapi20-3 +libcapi20-dev +libcdio6 +libcdk5 +libcdparanoia0 +libclamav1 +libcomerr2 +libconfhelper-perl +libconfig-file-perl +libconsole +libcroco3 +libcucul0 +libcupsimage2 +libcupsys2 +libcurl3 +libcurl3-gnutls +libdate-manip-perl +libdb1-compat +libdb4.2 +libdb4.3 +libdb4.4 +libdbd-mysql-perl +libdbi-perl +libdbus-1-3 +libdbus-glib-1-2 +libdbus-qt-1-1c2 +libdc1394-13 +libdevmapper1.02 +libdirectfb-0.9-25 +libdm0 +libdns21 +libdrm2 +libdv-bin +libdv4 +libdvdread3 +libedit2 +libelfg0 +libemeraldengine0 +libenchant1c2a +libesd-alsa0 +libevent1 +libexif-gtk5 +libexif12 +libexpat1 +libfam0 +libflac++5 +libflac7 +libfontconfig1 +libfontenc1 +libfreetype6 +libfribidi0 +libfs6 +libft-perl +libfuse2 +libgcc1 +libgconf2-4 +libgcrypt11 +libgd2-xpm +libgdbm3 +libgdchart-gd2-noxpm +libgeoip1 +libgimp2.0 +libgksu2-0 +libgl1-mesa-dri +libgl1-mesa-glx +libglade2-0 +libglib1.2 +libglib2.0-0 +libglib2.0-data +libglibmm-2.4-1c2a +libglu1-mesa +libgmp3c2 +libgnome-keyring0 +libgnutls13 +libgpg-error0 +libgpgme11 +libgphoto2-2 +libgphoto2-port0 +libgpmg1 +libgsf-1-114 +libgsf-1-common +libgsm1 +libgsmme1c2a +libgssapi2 +libgstreamer0.10-0 +libgtk1.2 +libgtk1.2-common +libgtk2.0-0 +libgtk2.0-bin +libgtk2.0-common +libgtkmm-2.4-1c2a +libgtkspell0 +libgtop2-7 +libgtop2-common +libgutenprint2 +libgutenprintui2-1 +libhal-storage1 +libhal1 +libhfsp0 +libhtml-parser-perl +libhtml-tagset-perl +libhtml-tree-perl +libice6 +libid3tag0 +libident +libidl0 +libidn11 +libieee1284-3 +libijs-0.35 +libisc11 +libisccc0 +libisccfg1 +libiso9660-4 +libiw28 +libjack0.100.0-0 +libjasper-1.701-1 +libjcode-pm-perl +libjpeg-progs +libjpeg62 +libjpeg62-dev +libk3b2 +libkcal2b +libkcddb1 +libkdegames1 +libkdepim1a +libkleopatra1 +libklibc +libkmime2 +libkonq4 +libkpimidentities1 +libkrb53 +libksba8 +libkscan1 +libksieve0 +libktnef1 +liblcms1 +libldap-2.3-0 +libldap2 +liblircclient0 +liblocale-gettext-perl +liblockdev1 +liblockfile1 +liblogfile-rotate-perl +libltdl3 +liblua50 +liblualib50 +liblwres9 +liblzo1 +libmad0 +libmagic1 +libmagick++9c2a +libmagick9 +libmikmod2 +libmimelib1c2a +libmng1 +libmodplug0c2 +libmpcdec3 +libmusicbrainz4c2a +libmyspell3c2 +libmysqlclient15off +libnasl2 +libncp +libncurses5 +libncurses5-dev +libncursesw5 +libneon25 +libnessus2 +libnet-daemon-perl +libnet0 +libnet1 +libnetpbm10 +libnewt-utf8-0 +libnewt0.52 +libnfsidmap2 +libnids1.20 +libnspr4 +libnspr4-0d +libnss3-0d +libntfs9 +libogg0 +liboggflac3 +libopencdk8 +libopenexr2c2a +libopenobex1 +liborbit2 +libpam-modules +libpam-ncp +libpam-runtime +libpam0g +libpango1.0-0 +libpango1.0-common +libpaper-utils +libpaper1 +libparted1.6-0 +libparted1.7-1 +libpcap0.7 +libpcap0.8 +libpcd2 +libpci2 +libpcre3 +libperl5.8 +libpisock9 +libplot2c2 +libplrpc-perl +libpng12-0 +libpoppler0c2 +libpoppler0c2-qt +libpopt0 +libportaudio0 +libpostproc0d +libpq4 +libpstoedit0c2a +libpth20 +libqt3-mt +libquicktime0 +libraw1394-8 +libreadline4 +libreadline5 +librecode0 +librpcsecgss3 +librpm4 +librsvg2-2 +libsamplerate0 +libsane +libsane-extras +libsasl2 +libsasl2-2 +libsasl2-modules +libscrollkeeper0 +libsdl-console +libsdl-gfx1.2-4 +libsdl-image1.2 +libsdl-mixer1.2 +libsdl-net1.2 +libsdl-pango1 +libsdl-perl +libsdl-ttf2.0-0 +libsdl1.2debian +libsdl1.2debian-alsa +libselinux1 +libsensors3 +libsepol1 +libsexy2 +libsigc++-2.0-0c2a +libslang2 +libslp1 +libsm6 +libsmbclient +libsmpeg0 +libsndfile1 +libsnmp-base +libsnmp9 +libspeex1 +libsqlite3-0 +libss2 +libssl0.9.7 +libssl0.9.8 +libssp0 +libstartup-notification0 +libstdc++2.10-glibc2.2 +libstdc++5 +libstdc++6 +libstdc++6-4.1-dev +libsvga1 +libsysfs2 +libt1-5 +libtag1c2a +libtasn1-3 +libtext-charwidth-perl +libtext-iconv-perl +libtext-wrapi18n-perl +libtheora0 +libtiff-tools +libtiff4 +libttf2 +libungif4g +libuniconf4.2 +liburi-perl +libusb-0.1-4 +libuuid1 +libvcdinfo0 +libvolume-id0 +libvorbis0a +libvorbisenc2 +libvorbisfile3 +libvte-common +libvte4 +libweakref-perl +libwmf0.2-7 +libwnck-common +libwnck18 +libwrap0 +libwvstreams4.2-base +libwvstreams4.2-extras +libwww-perl +libwxgtk2.4-1 +libx11-6 +libx11-data +libxau6 +libxaw7 +libxcomp1 +libxcompext1 +libxcomposite1 +libxcursor1 +libxdamage1 +libxdelta2 +libxdmcp6 +libxext6 +libxfixes3 +libxfont1 +libxft2 +libxi6 +libxine1 +libxinerama1 +libxkbfile1 +libxml2 +libxmu6 +libxmuu1 +libxp6 +libxplc0.3.13 +libxpm4 +libxrandr2 +libxrender1 +libxres1 +libxslt1.1 +libxss1 +libxt6 +libxtrap6 +libxtst6 +libxv1 +libxvmc1 +libxxf86dga1 +libxxf86misc1 +libxxf86vm1 +libzvbi-common +libzvbi0 +libzzip-0-12 +lilo +linux-image-2.6.19 +linux-kernel-headers +linux-sound-base +lisa +loadlin +locales +lockfile-progs +login +logrotate +loop-aes-modules-2.6.19 +loop-aes-utils +lrzsz +lsb-base +lsof +ltrace +lvm-common +lvm2 +lynx +lzop +m4 +macutils +madwifi-modules-2.6.19 +madwifi-tools +mailx +make +makedev +man-db +manpages +manpages-de +manpages-dev +mawk +mbr +mc +mdadm +memtester +menu +menu-xdg +mesa-utils +mikmod +mime-support +minicom +mkbootdev +mkisofs +hi +mktemp +mobilemesh +modconf +module-init-tools +modutils +mount +mouseconfig +mpack +mpg321 +mplayer +mplayer-skin-blue +ms-sys +mt-st +mtools +mtr-tiny +mutt +myspell-en-us +mysql-client +mysql-client-5.0 +mysql-common +nano +nasm +ncpfs +ncurses-base +ncurses-bin +ndiswrapper-modules-2.6. +ndiswrapper-utils +nedit +nessus +nessus-plugins +nessusd +net-tools +netbase +netcat +netcat6 +netpbm +netpipe-tcp +networkstatus +nfs-common +nfs-kernel-server +ngrep +nmap +ntfs-3g +ntpdate +nvtv +nxagent +nxclient +nxdesktop +nxlibs +nxproxy +nxssh +nxtunnel-client +nxtunnel-server +odbcinst1debian1 +openbsd-inetd +openhackware +openoffice-de-en +openoffice.org-debian-me +openssh-client +openssh-server +openssl +openvpn +outguess +p0f +parted-bf +partimage +partimage-server +passwd +patch +pciutils +pciutils-dev +pcmcia-cs +pcmciautils +perl +perl-base +perl-modules +perl-suid +pgpgpg +php4-common +php4-mysql +pia +pkg-config +playmidi +pmount +pnm2ppa +po-debconf +portmap +poster +powermgmt-base +ppmd +ppp +hi +pppdcapiplugin +pppoe +pppoeconf +pppstatus +pptp-linux +print-utils-pfeifle +prism54-nonfree +procinfo +procmail +procps +proll +psfontmgr +psmisc +psutils +pump +python +python-central +python-imaging +python-imaging-tk +python-minimal +python-support +python-tk +python2.4 +python2.4-minimal +qemu +qobex +qps +qtparted +radio +rcs +rdate +rdesktop +readline-common +recode +recover +reiserfsprogs +reportbug +rpm +rsync +rt2x00-cvs-modules-2.6.1 +rxvt-beta +s3switch +samba +samba-common +sane +sane-utils +sash +scanmodem +scantv +scli +screen +scribus +scrollkeeper +sed +sendfile +sendip +setserial +sgml-base +sgml-data +shaper +sharutils +sitar +slang1 +slang1a-utf8 +sleuthkit +smail +smartmontools +smbclient +smbconf-pfeifle +smbconf-pfeifle-nonfree +smbfs +sniffit +sound-recorder +sox +speedtouch +speex +squid +squid-common +squidclient +ssh +ssl-cert +sslwrap +star +statserial +strace +stress +stunnel +sudo +sun-java5-bin +sun-java5-demo +sun-java5-jdk +sun-java5-jre +sun-java5-plugin +sweep +symlinks +synaptic +sysklogd +syslinux +sysv-rc +sysvinit +sysvinit-utils +tar +tcl8.4 +tcpd +tcpdump +telnet-ssl +telnetd-ssl +testdisk +tftp +tftpd-hpa +thttpd +thunderbird +thunderbird-locale-de +tiger +tightvncserver +tk8.4 +tnef +tofrodos +tpconfig +traceroute +trans-de-en +transfig +tshark +tsocks +ttf-bitstream-vera +ttf-f500 +ttf-freefont +ttf-isabella +ttf-openoffice +ttf-opensymbol +ttf-staypuft +ttf-summersby +ttmkfdir +twm +txt2regex +type-handling +type1inst +tzdata +ucf +udev +udpcast +uml-utilities +umlrun-uml +unifont +units +unixodbc +unp +unzip +unzoo +update +update-inetd +urlview +usbutils +usbview +user-de +util-linux +util-linux-locales +uudeview +v4l-conf +vcdimager +vcdtools +vgabios +vim +vim-common +vim-gtk +vim-gui-common +vim-runtime +vim-scripts +vimpart +vlan +vnc-common +vorbis-tools +vpnc +vrms +wakeonlan +wavemon +wavtools +wget +whiptail +whois +wine +winetools +wipe +wireless-tools +wireshark +wireshark-common +wodim +wpasupplicant +wprint +wvdial +x-ttcidfont-conf +x11-common +xaos +xaw3dg +xawtv +xawtv-plugins +xbase-clients +xbattle +xbitmaps +xboard +xchat +xchat-common +xdelta +xdialog +xdm +xfonts-100dpi +xfonts-100dpi-transcoded +xfonts-75dpi +xfonts-75dpi-transcoded +xfonts-base +xfonts-bolkhov-cp1251-75 +xfonts-bolkhov-cp1251-mi +xfonts-dosemu +xfonts-encodings +xfonts-scalable +xfonts-terminus +xfonts-utils +xfsdump +xfsprogs +xgalaga +xkb-data +xkbset +xlibmesa-gl +xlibs +xloadimage +xml-core +xmms +xmms-cdread +xmms-goom +xmms-modplug +xmms-volnorm +xnest +xorg +xosview +xpdf +xpdf-common +xpdf-reader +xpdf-utils +xsane +xsane-common +xserver-xorg +xserver-xorg-core +xserver-xorg-input-evdev +xserver-xorg-input-kbd +xserver-xorg-input-mouse +xserver-xorg-input-synap +xserver-xorg-video-all +xserver-xorg-video-apm +xserver-xorg-video-ark +xserver-xorg-video-ati +xserver-xorg-video-chips +xserver-xorg-video-cirru +xserver-xorg-video-cyrix +xserver-xorg-video-dummy +xserver-xorg-video-fbdev +xserver-xorg-video-glint +xserver-xorg-video-i128 +xserver-xorg-video-i740 +xserver-xorg-video-i810 +xserver-xorg-video-imstt +xserver-xorg-video-mga +xserver-xorg-video-neoma +xserver-xorg-video-newpo +xserver-xorg-video-nsc +xserver-xorg-video-nv +xserver-xorg-video-rendi +xserver-xorg-video-s3 +xserver-xorg-video-s3vir +xserver-xorg-video-savag +xserver-xorg-video-silic +xserver-xorg-video-sis +xserver-xorg-video-sisus +xserver-xorg-video-tdfx +xserver-xorg-video-tga +xserver-xorg-video-tride +xserver-xorg-video-tseng +xserver-xorg-video-v4l +xserver-xorg-video-vesa +xserver-xorg-video-vga +xserver-xorg-video-via +xserver-xorg-video-vmwar +xserver-xorg-video-voodo +xskat +xterm +xtightvncviewer +xtv +xutils +xutils-dev +xviddetect +xzoom +zile +zip +zlib1g +zlib1g-dev diff --git a/lists/knoppix-dvd b/lists/knoppix-dvd new file mode 100644 index 0000000..c6ab94e --- /dev/null +++ b/lists/knoppix-dvd @@ -0,0 +1,3417 @@ +# /usr/share/make-live/lists/gnome - package list for make-live(1) +# + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# X11 +desktop-base xresprobe + +# Knoppix packages +# URL: http://ftp.kernel.org/pub/dist/knoppix-dvd/packages-dvd.txt +0wn +3270-common +a2ps +aalib-bin +aalib1 +abiword-common +abiword-gnome +abiword-help +ace-of-penguins +acpi +adduser +adtool +aespipe +afio +airsnort +akregator +alevt +alien +alsa-base +alsa-utils +amanda-client +amanda-common +amanda-server +amarok +amarok-engines +amarok-xine +amor +anacron +ant +ant-optional +antlr +apache +apache-common +apache-dev +apache-doc +apache-utils +apache2 +apache2-doc +apache2-mpm-prefork +apache2-utils +apache2.2-common +apcalc +apcalc-common +apel +apmd +apt +apt-doc +apt-file +apt-listchanges +apt-method-installed +apt-show-versions +apt-utils +aptitude +aribas +arj +ark +arpwatch +arts +artsbuilder +artwiz-cursor +asclock +asclock-themes +aspell +aspell-de +aspell-doc +aspell-en +aspell-es +aspell-fr +aspell-it +aspell-pl +at +at-spi +atitvout +atlantik +atlantikdesigner +atlas2-base +atlas3-base +atlas3-base-dev +atlas3-headers +atmel-firmware +attr +auctex +audacious +audacious-plugins +audacious-plugins-extra +audacity +aufs-cvs-modules-2.6.19 +aufs-cvs-utils +aumix-gtk +autoclass +autoconf +autofs +automake1.4 +automake1.7 +automake1.9 +autotools-dev +autotrace +avce00 +avm-firmware +axiom +axiom-databases +axkit +axkit-examples +axkit-language-htmldoc +axkit-language-query +axyftp-doc +axyftp-gtk +bacula +bacula-client +bacula-common +bacula-console +bacula-director-common +bacula-director-mysql +bacula-doc +bacula-fd +bacula-sd +bacula-sd-sqlite3 +bacula-server +base-files +base-passwd +bash +basket +bb +bc +beneath-a-steel-sky +beryl +beryl-core +beryl-manager +beryl-plugins +beryl-plugins-data +beryl-settings +biew +bin86 +bind9 +bind9-host +binfmt-support +bing +binutils +binutils-dev +bison +bitmap-mule +bittorrent +blas +blender +blinken +blt +bluefish +bluez-firmware +bluez-utils +bochs +bochs-doc +bochs-sdl +bochs-term +bochs-wx +bochs-x +bochsbios +bonnie++ +bridge-utils +brltty +bsdiff +bsdmainutils +bsdutils +buffer +bug-buddy +build-essential +busybox +bximage +bzflag +bzflag-server +bzip2 +ca-certificates +cabextract +capisuite +capiutils +capplets-data +cdbackup +cdbs +cdd-common +cdda2wav +cddb +cdparanoia +cdrdao +cdrecord +cdrtools-doc +cdrw-taper +cernlib-base +cervisia +cfortran +cgoban +checkmem +chipcard-tools +chkrootkit +chktex +chromium +chromium-data +cjk-latex +cl-asdf +cl-cil +cl-reversi +cl-utilities +clamav +clamav-base +clamav-docs +clamav-freshclam +clara +cli-common +cli-common-dev +cloop-module-2.6.19 +cloop-utils +cmt +colorgcc +comerr-dev +common-lisp-controller +compiz +compiz-core +compiz-gnome +compiz-gtk +compiz-plugins +configure-xawtv +console-common +console-data +console-tools +convertfs +coreutils +cowsay +cpio +cpp +cpp-3.3 +cpp-3.4 +cpp-4.0 +cpp-4.0-doc +cpp-4.1 +cpp-4.1-doc +cpp-doc +cpuburn +crack-attack +cramfsprogs +cron +crossfire-client +crossfire-client-gtk +crossfire-client-gtk2 +crossfire-client-images +crossfire-client-sounds +crossfire-client-x11 +crossfire-common +crossfire-doc +crossfire-edit +crossfire-maps +crossfire-server +cryptcat +cryptsetup +crystalspace +crystalspace-dev +crystalspace-doc +csh +csound +csound-doc +cups-pdf +cupsys +cupsys-bsd +cupsys-client +cupsys-common +cupsys-driver-gutenprint +cvs +cycle +d4x +d4x-common +dante-client +dash +dasher +dasher-data +db4.2-util +db4.3-util +dbconfig-common +dbishell +dbus +dc +dcraw +dctrl-tools +dd-rescue +ddd +dds2tar +debconf +debconf-i18n +debconf-utils +debfoster +debhelper +debian-archive-keyring +debian-keyring +debiandoc-sgml +debianutils +debootstrap +deborphan +debsums +defoma +defrag +desktop-base +desktop-file-utils +devscripts +dh-make +dhcp3-common +dhcp3-server +dia +dia-common +dia-gnome +dia-libs +dialog +dict +dictionaries-common +dietlibc-dev +diff +diffstat +digikam +digikamimageplugins +dillo +ding +dirmngr +discover1 +discover1-data +distcc +dlint +dlocate +dmidecode +dmraid +dmsetup +dnsutils +doc-base +doc-linux-html +docbook +docbook-dsssl +docbook-xml +docbook-xsl +dosfstools +dpatch +dpkg +dpkg-dev +dpkg-repack +drdsl +dselect +dsh +dsniff +dump +dupload +dvb-mpegtools +dvb-utils +dvbackup +dvbsnoop +dvbstream +dvbtune +dvd+rw-tools +dvdauthor +dvdbackup +dvdrecord +dvgrab +dvipng +e00compr +e2fslibs +e2fslibs-dev +e2fsprogs +ec-fonts-mftraced +ecj-bootstrap +eclipse +eclipse-jdt +eclipse-pde +eclipse-platform +eclipse-rcp +eclipse-source +ed +edict +efax +efax-gtk +effectv +efibootmgr +eject +ekiga +elinks +emacs-intl-fonts +emacs21 +emacs21-bin-common +emacs21-common +emacsen-common +emerald +emerald-themes +enigma +enigma-data +enlightenment +enlightenment-data +enscript +eog +epiphany-browser +erlang +erlang-base +erlang-dev +erlang-examples +erlang-mode +erlang-nox +erlang-src +erlang-x11 +escputil +esound +esound-common +ess +eterm +etherwake +ethtool +ettercap-common +ettercap-gtk +euler +euro-support +euro-support-console +euro-support-x +evilwm +evince +evolution +evolution-common +evolution-data-server +evolution-data-server-co +evolution-exchange +evolver +expect +ext2resize +eyesapplet +f2c +fakeroot +falconseye +falconseye-data +fast-user-switch-applet +fastjar +fb-music-low +fbi +fbset +fdflush +fdisk-udeb +fdutils +fenris +festival +festlex-cmu +festlex-poslex +festvox-kallpc16k +festvox-kdlpc16k +fetchmail +ffmpeg +fftw-dev +fftw2 +fftw3 +fftw3-dev +fifteenapplet +file +file-roller +fileutils +findutils +finger +firefox +firefox-dom-inspector +flex +flobopuyo +fluxbox +fnlib-data +fontconfig +fontconfig-config +fontforge +fontforge-doc +fonty +foomatic-bin +foomatic-db +foomatic-db-engine +foomatic-db-gimp-print +foomatic-db-gutenprint +foomatic-db-hpijs +foomatic-filters +foremost +fortune-mod +fortunes-debian-hints +fortunes-min +fp-compiler +fp-docs +fp-ide +fp-units-base +fp-units-db +fp-units-fcl +fp-units-fv +fp-units-gfx +fp-units-gnome1 +fp-units-gtk +fp-units-gtk2 +fp-units-misc +fp-units-net +fp-units-rtl +fp-utils +fpc-crosswin32 +fpc-src +fping +freeciv-client-gtk +freeciv-data +freeciv-server +freefem +freefem-doc +freefem-examples +freefem3d +freeglut3 +freemind +freenx +freepats +freepops +freeradius +frozen-bubble +hi +ftape-util +ftp +ftpd +fttools +fuse-utils +g++ +g++-3.3 +g++-4.0 +g++-4.1 +g-wrap +g77 +g77-3.3 +g77-3.3-doc +g77-3.4 +gaim +gaim-data +gaim-encryption +gambas-gb-qt +gambas-runtime +gambit +gambit-doc +gamin +gap +gap-character-tables +gap-core +gap-dev +gap-doc +gap-libs +gap-online-help +gap-prim-groups +gap-small-groups +gap-small-groups-extra +gap-table-of-marks +gap-trans-groups +gawk +gbib +gcalctool +gcc +gcc-3.3 +gcc-3.3-base +gcc-3.4 +gcc-3.4-base +gcc-4.0 +gcc-4.0-base +gcc-4.0-doc +gcc-4.1 +gcc-4.1-base +gcc-4.1-doc +gcc-doc +gcc-doc-base +gcj +gcj-3.3 +gcj-4.0-base +gcj-4.1 +gcj-4.1-base +gcom +gcompris +gcompris-data +gcompris-sound-da +gcompris-sound-de +gcompris-sound-en +gcompris-sound-es +gcompris-sound-fr +gcompris-sound-it +gcompris-sound-pt +gcompris-sound-ru +gconf +gconf-editor +gconf2 +gconf2-common +gdal-bin +gdb +gdk-imlib1 +gdk-imlib11 +gdm +gdm-themes +geant321-doc +geas +geas-doc +geda +geda-doc +geda-examples +geda-gattrib +geda-gnetlist +geda-gschem +geda-gsymcheck +geda-symbols +geda-utils +gedit +gedit-common +geg +genisoimage +genliloconf +geomview +gerbv +gettext +gettext-base +gettext-el +gfortran +gfortran-4.1 +gftp +gftp-common +gftp-gtk +gftp-text +ghemical +gif2png +giflib-bin +giflib3g +giftrans +gij +gij-4.0 +gij-4.1 +gimp +gimp-data +gimp-print +ginac-tools +git-core +gjdoc +gkrellm +gkrellmd +gksu +glibc-doc +glpk +gmessage +gmsh +gmt +gmt-coast-low +gmt-doc +gmt-examples +gmt-tutorial +gmt-tutorial-pdf +gnokii +gnome +gnome-about +gnome-accessibility-them +gnome-applets +gnome-applets-data +gnome-backgrounds +gnome-bin +gnome-cards-data +gnome-control-center +gnome-core +gnome-cups-manager +gnome-desktop-data +gnome-desktop-environmen +gnome-doc-tools +gnome-doc-utils +gnome-games +gnome-games-data +gnome-games-extra-data +gnome-gv +gnome-icon-theme +gnome-keyring +gnome-keyring-manager +gnome-libs-data +gnome-mag +gnome-media +gnome-media-common +gnome-menus +gnome-mime-data +gnome-netstatus-applet +gnome-nettool +gnome-office +gnome-panel +gnome-panel-data +gnome-session +gnome-system-monitor +gnome-system-tools +gnome-terminal +gnome-terminal-data +gnome-themes +gnome-themes-extras +gnome-user-guide +gnome-utils +gnome-volume-manager +gnome2-user-guide +gnopernicus +gnubg +gnubg-data +gnucash +gnucash-common +gnucash-docs +gnuchess +gnuchess-book +gnue-appserver +gnue-common +gnue-designer +gnue-forms +gnue-navigator +gnue-reports +gnugo +gnuhtml2latex +gnumeric +gnumeric-common +gnumeric-doc +gnumeric-plugins-extra +gnupg +gnupg-agent +gnupg2 +gnuplot +gnuplot-doc +gnuplot-nox +gnuplot-x11 +gnustep-base-common +gnustep-common +gnustep-make +gnutls-bin +gocr +gok +gok-doc +gpart +gparted +gpc +gpc-2.1-3.4 +gpc-2.1-3.4-doc +gpdf +gperiodic +gpgsm +gpgv +gphoto2 +gpm +gpp +gprolog +gprolog-doc +gpsdrive +gpstrans +gq +gqcam +gqview +grace +gramofile +graphviz +graphviz-doc +grass +grass-doc +grep +grep-dctrl +gri +gri-el +gri-html-doc +grip +groff +groff-base +hi +grub-disk +gs-common +gs-esp +gs-gpl +gscanbus +gsfonts +gsfonts-x11 +gsl-bin +gsl-doc-pdf +gsl-ref-html +gsl-ref-psdoc +gsm-utils +gstreamer0.10-alsa +gstreamer0.10-gnomevfs +gstreamer0.10-gnonlin +gstreamer0.10-plugins-ba +gstreamer0.10-plugins-go +gstreamer0.10-plugins-ug +gstreamer0.8-plugin-apps +gstreamer0.8-tools +gtans +gthumb +gtk-engines-qtpixmap +gtk-smooth-themes +gtk2-engines +gtk2-engines-pixbuf +gtk2-engines-spherecryst +gtk2-engines-xfce +gtkam +gtkglarea5 +gtkhtml3.2 +gtkhtml3.6 +gtkhtml3.8 +gucharmap +guile-1.6 +guile-1.6-dev +guile-1.6-libs +guile-1.6-slib +guile-g-wrap +guile-library +gutenprint-doc +gutenprint-locales +gv +gwenview +gzip +hal +hal-device-manager +hdparm +helix-player +hermes1 +hevea +hexedit +hfsplus +hfsutils +hicolor-icon-theme +hostap-utils +hostapd +hostname +hotplug-utils +hpijs +hping2 +hspell +htdig +html2text +htmldoc +htmldoc-common +httptunnel +hunt +hwinfo +hwsetup +hwtools +i810switch +iamerican +iasl +ibod +ibritish +iceape-browser +icedax +icedove +icedove-inspector +icedove-locale-bg +icedove-locale-cs +icedove-locale-da +icedove-locale-de +icedove-locale-el +icedove-locale-es-es +icedove-locale-fi +icedove-locale-fr +icedove-locale-gu +icedove-locale-he +icedove-locale-hu +icedove-locale-it +icedove-locale-ja +icedove-locale-ko +icedove-locale-mk +icedove-locale-nb +icedove-locale-nl +icedove-locale-ru +icedove-locale-sk +icedove-locale-sl +icedove-locale-sv +icedove-locale-tr +icedove-locale-zh-cn +icedove-typeaheadfind +iceweasel +iceweasel-dom-inspector +iceweasel-l10n-ar +iceweasel-l10n-bg +iceweasel-l10n-ca +iceweasel-l10n-cs +iceweasel-l10n-da +iceweasel-l10n-de +iceweasel-l10n-el +iceweasel-l10n-es-es +iceweasel-l10n-eu +iceweasel-l10n-fi +iceweasel-l10n-fr +iceweasel-l10n-hu +iceweasel-l10n-it +iceweasel-l10n-ja +iceweasel-l10n-lt +iceweasel-l10n-nl +iceweasel-l10n-pl +iceweasel-l10n-pt-br +iceweasel-l10n-ru +iceweasel-l10n-sk +iceweasel-l10n-sl +iceweasel-l10n-zh-cn +icewm +icewm-common +icewm-themes +icmpush +iconx +idswakeup +iftop +ifupdown +ijsgimpprint +ijsgutenprint +ilisp +imageindex +imagemagick +imaze +imlib-base +imlib-progs +imlib11 +indi +industrial-cursor-theme +info +infobash +initramfs-tools +initrd-tools +initscripts +inkscape +intltool-debian +ipcalc +ipchains +iperf +ipppd +iproute +ipsec-tools +iptables +iptraf +iputils-ping +iputils-tracepath +ipv6calc +ipw2100-nonfree +ipw2200-nonfree +ipx +ipython +irb +irb1.8 +ircii +irda-common +irda-tools +irssi +irssi-plugin-icq +irssi-scripts +isapnptools +isdnactivecards +isdnutils-base +isdnvboxclient +iso-codes +isomaster +ispell +jackd +jade +java-common +jfsutils +jikes +joe +john +jokosher +jpilot +jpilot-backup +jpilot-mail +jpilot-plugins +jpilot-syncmal +juk +junit +k3b +k3b-defaults +k3b-i18n +kaddressbook +kaffe +kaffe-common +kaffe-pthreads +kaffeine +kakasi +kakasi-dic +kalarm +kalzium +kalzium-data +kamera +kanagram +kandy +kanjidic +kappfinder +kapptemplate +karbon +karm +kasteroids +kate +kate-plugins +katomic +kbabel +kbabel-dev +kbackgammon +kbackup +kbackup-doc +kbackup-multibuf +kbattleship +kbdconfig +kbear +kblackbox +kbounce +kbruch +kbugbuster +kcachegrind +kcalc +kcharselect +kchart +kcoloredit +kcontrol +kcron +kdat +kde-amusements +kde-core +kde-i18n-az +kde-i18n-bg +kde-i18n-ca +kde-i18n-cs +kde-i18n-da +kde-i18n-de +kde-i18n-el +kde-i18n-es +kde-i18n-et +kde-i18n-fa +kde-i18n-fi +kde-i18n-fr +kde-i18n-he +kde-i18n-hu +kde-i18n-it +kde-i18n-ja +kde-i18n-nl +kde-i18n-pl +kde-i18n-pt +kde-i18n-ptbr +kde-i18n-ru +kde-i18n-sk +kde-i18n-sl +kde-i18n-sr +kde-i18n-sv +kde-i18n-tr +kde-i18n-zhcn +kde-i18n-zhtw +kdeaddons-kfile-plugins +kdeadmin +kdeadmin-kfile-plugins +kdeartwork +kdeartwork-emoticons +kdeartwork-misc +kdeartwork-style +kdeartwork-theme-icon +kdeartwork-theme-window +kdebase +kdebase-bin +kdebase-data +kdebase-kio-plugins +kdebluetooth +kdeedu +kdeedu-data +kdeedu-doc-html +kdegames +kdegames-card-data +kdegames-doc-html +kdegraphics-doc-html +kdegraphics-kfile-plugin +kdelibs +kdelibs-data +kdelibs4-dev +kdelibs4c2a +kdemultimedia-kfile-plug +kdemultimedia-kio-plugin +kdenetwork-kfile-plugins +kdepasswd +kdepim +kdepim-kfile-plugins +kdepim-kio-plugins +kdepim-kresources +kdepim-wizards +kdeprint +kdesdk +kdesdk-doc-html +kdesdk-kfile-plugins +kdesdk-kio-plugins +kdesdk-misc +kdesdk-scripts +kdesktop +kdessh +kdetoys +kdetoys-doc-html +kdevelop +kdevelop-data +kdevelop-doc +kdewallpapers +kdewebdev +kdewebdev-doc-html +kdf +kdict +kdiff3 +kdissert +kdm +kdoc +kdvi +keduca +kenolaba +kernel-package +kexec-tools +kexi +kfax +kfilereplace +kfind +kfloppy +kformula +kfouleggs +kgamma +kget +kghostview +kgoldrunner +khangman +khelpcenter +khexedit +kicker +kiconedit +kig +kile +kile-i18n +kimagemapeditor +kino +kiosktool +kipi-plugins +kismet +kitchensync +kiten +kivio +kivio-data +kjumpingcube +klaptopdaemon +klatin +kleopatra +klettres +klettres-data +klibc-utils +klickety +klines +klinkstatus +klipper +klogd +kmahjongg +kmail +kmailcvt +kmenuedit +kmessedwords +kmines +kmix +kmoon +kmplot +kmrml +kmtrace +kmymoney2 +knetwalk +knetworkconf +knode +knotes +kodo +koffice +koffice-data +koffice-dev +koffice-doc +koffice-doc-html +koffice-i18n-af +koffice-i18n-bg +koffice-i18n-br +koffice-i18n-ca +koffice-i18n-cs +koffice-i18n-da +koffice-i18n-de +koffice-i18n-el +koffice-i18n-es +koffice-i18n-et +koffice-i18n-fa +koffice-i18n-fi +koffice-i18n-fr +koffice-i18n-he +koffice-i18n-hu +koffice-i18n-it +koffice-i18n-ja +koffice-i18n-nl +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-tr +koffice-i18n-zhcn +koffice-i18n-zhtw +koffice-libs +kolf +kolourpaint +kommander +kommander-dev +kompare +konq-plugins +konqueror +konqueror-nsplugins +konquest +konsole +konsolekalendar +kontact +konversation +kooka +kopete +korganizer +korn +koshell +kpackage +kpager +kpat +kpdf +kpercentage +kpersonalizer +kpf +kphone +kpilot +kplato +kpoker +kppp +kpresenter +kpresenter-data +kqemu-gui +krdc +kreversi +krfb +krita +krita-data +kruler +krusader +ksame +kscreensaver +kscreensaver-xsavers +kshisen +ksim +ksirtet +ksmiletris +ksmserver +ksnake +ksnapshot +ksokoban +kspaceduel +ksplash +kspread +kspy +kstars +kstars-data +ksudoku +ksvg +ksync +ksysguard +ksysguardd +ksysv +kteatime +kthesaurus +ktimer +ktip +ktnef +ktouch +ktron +ktuberling +kturtle +ktux +kugar +kuickshow +kuiviewer +kunittest +kuser +kvdr +kverbos +kview +kviewshell +kvoctrain +kweather +kwifimanager +kwin +kwin4 +kwlan +kword +kword-data +kwordquiz +kworldclock +kxsldbg +lacheck +ladcca2 +ladspa-sdk +lam-runtime +lam4c2 +lapack +lapack3 +laptop-detect +larswm +latex-beamer +latex-cjk-common +latex-xcolor +latex-xft-fonts +latex2html +lazarus +ldap-utils +lde +less +lesstif-dev +lesstif1 +lesstif2 +lftp +lha +liba52-0.7.4 +libaa1 +libaa1-dev +libacl1 +libacl1-dev +libadns1 +libaiksaurus-1.2-0c2a +libaiksaurus-1.2-data +libakode2 +libalgorithm-dependency- +libalut0 +libanthy0 +libao2 +libapache-dbi-perl +libapache-mod-perl +libapache-mod-ssl +libapache-request-perl +libapache-session-perl +libapache2-mod-jk +libapache2-mod-php5 +libapm1 +libappconfig-perl +libapr0 +libapr1 +libaprutil1 +libapt-pkg-perl +libaqbanking-data +libaqbanking-plugins-lib +libaqbanking16 +libaqdtaus3 +libaqgeldkarte4 +libaqhbci10 +libarchive-zip-perl +libart-2.0-2 +libart-2.0-dev +libart2 +libarts1-dev +libarts1c2a +libartsc0 +libartsc0-dev +libasound2 +libasound2-dev +libaspell-dev +libaspell15 +libast2 +libasyncns0 +libatk1.0-0 +libatk1.0-dev +libatm1 +libatspi1.0-0 +libattr1 +libattr1-dev +libaudacious4 +libaudio-dev +libaudio2 +libaudiofile-dev +libaudiofile0 +libauthen-sasl-perl +libautotrace3 +libavahi-client-dev +libavahi-client3 +libavahi-common-data +libavahi-common-dev +libavahi-common3 +libavahi-compat-howl0 +libavahi-compat-libdnssd +libavahi-glib1 +libavahi-qt3-1 +libavahi-qt3-dev +libavc1394-0 +libavc1394-dev +libavcodec0d +libavformat0d +libbcel-java +libbeecrypt6 +libberylsettings0 +libbind9-0 +libblkid1 +libbluetooth2 +libbonobo2-0 +libbonobo2-common +libbonoboui2-0 +libbonoboui2-common +libboost-date-time1.33.1 +libboost-filesystem1.33. +libboost-python1.32.0 +libboost-python1.33.0c2a +libboost-python1.33.1 +libboost-regex1.33.1 +libbraille +libbrlapi1 +libbz2-1.0 +libbz2-dev +libc-client2002edebian +libc6 +libc6-dev +libcaca0 +libcache-cache-perl +libcache-simple-timedexp +libcairo-perl +libcairo2 +libcairo2-dev +libcamel1.2-8 +libcanlock2 +libcap-dev +libcap1 +libcapi20-3 +libcapi20-dev +libcapsinetwork0c2a +libcdio6 +libcdk5 +libcdparanoia0 +libcfitsio2 +libchipcard-common +libchipcard2-0c2 +libchipcard20 +libclamav1 +libclan2c2a-gui +libclan2c2a-jpeg +libclan2c2a-mikmod +libclan2c2a-png +libclan2c2a-sound +libclan2c2a-vorbis +libclanlib2c2a +libclass-accessor-perl +libclass-autouse-perl +libclass-container-perl +libclass-data-inheritabl +libclass-inspector-perl +libclass-returnvalue-per +libcln4 +libclone-perl +libcomerr2 +libcommons-beanutils-jav +libcommons-collections-j +libcommons-collections3- +libcommons-dbcp-java +libcommons-digester-java +libcommons-el-java +libcommons-fileupload-ja +libcommons-launcher-java +libcommons-logging-java +libcommons-modeler-java +libcommons-pool-java +libcommons-validator-jav +libcompfaceg1 +libcompress-zlib-perl +libconfhelper-perl +libconfig-file-perl +libconfig-tiny-perl +libconsole +libconvert-asn1-perl +libconvert-binhex-perl +libcroco3 +libcrypt-ssleay-perl +libcsiro0 +libcucul0 +libcupsimage2 +libcupsys2 +libcupsys2-dev +libcurl3 +libcurl3-gnutls +libcvsservice0 +libdate-manip-perl +libdb1-compat +libdb3 +libdb4.2 +libdb4.3 +libdb4.4 +libdb4.4-dev +libdbd-mysql-perl +libdbd-pg-perl +libdbi-perl +libdbix-dbschema-perl +libdbix-searchbuilder-pe +libdbus-1-2 +libdbus-1-3 +libdbus-1-dev +libdbus-glib-1-2 +libdbus-qt-1-1c2 +libdc1394-13 +libdevel-stacktrace-perl +libdevel-symdump-perl +libdevmapper1.02 +libdigest-sha1-perl +libdirectfb-0.9-25 +libdirectfb-dev +libdirectfb-extra +libdiscover1 +libdjvulibre15 +libdm0 +libdmx-dev +libdmx1 +libdns21 +libdrm2 +libdshconfig1 +libdv-bin +libdv4 +libdv4-dev +libdvdread-dev +libdvdread3 +libebook1.2-5 +libecal1.2-6 +libedata-book1.2-2 +libedata-cal1.2-5 +libedataserver1.2-7 +libedataserverui1.2-6 +libedit2 +libeel2-2 +libeel2-data +libegroupwise1.2-10 +libelfg0 +libemeraldengine0 +libenchant1c2a +liberror-perl +libesd-alsa0 +libesd0-dev +libestools1.2 +libevent1 +libexception-class-perl +libexchange-storage1.2-1 +libexif-dev +libexif-gtk5 +libexif12 +libexiv2-0.10 +libexo-0.3-0 +libexpat1 +libexpat1-dev +libextutils-autoinstall- +libf2c2 +libf2c2-dev +libfcgi-perl +libffi4 +libffi4-dev +libfile-find-rule-perl +libfile-flat-perl +libfile-ncopy-perl +libfile-remove-perl +libfile-slurp-perl +libfinance-quote-perl +libflac++5 +libflac7 +libfltk1.1 +libfluidsynth1 +libfont-afm-perl +libfontconfig1 +libfontconfig1-dev +libfontenc-dev +libfontenc1 +libforms1 +libfreefem0 +libfreetype6 +libfreetype6-dev +libfreezethaw-perl +libfribidi0 +libfs-dev +libfs6 +libft-perl +libfuse-dev +libfuse2 +libg2c0 +libg2c0-dev +libgadu3 +libgail-common +libgail-gnome-module +libgail17 +libgal2.2-1 +libgal2.2-common +libgal2.4-0 +libgal2.4-common +libgamin-dev +libgamin0 +libgc1c2 +libgcc1 +libgcj-bc +libgcj-common +libgcj4 +libgcj4-awt +libgcj4-common +libgcj6 +libgcj6-jar +libgcj7-0 +libgcj7-awt +libgcj7-dev +libgcj7-jar +libgcompris-1-0 +libgconf11 +libgconf2-4 +libgconf2.0-cil +libgcrypt11 +libgcrypt11-dev +libgd2-xpm +libgda2-3 +libgda2-common +libgdal1-1.3.2 +libgdbm3 +libgdchart-gd2-noxpm +libgdgeda6 +libgdiplus +libgdk-pixbuf-dev +libgdk-pixbuf2 +libgecko2.0-cil +libgeda20 +libgeo-ipfree-perl +libgeoip1 +libgeos2c2a +libgfortran1 +libgfortran1-dev +libghemical-data +libghemical0c2a +libghttp1 +libgimp2.0 +libginac1.3c2a +libgksu1.2-0 +libgksu2-0 +libgksuui1.0-1 +libgl1-mesa-dev +libgl1-mesa-dri +libgl1-mesa-glx +libglade2-0 +libglade2.0-cil +libgle3 +libglib-perl +libglib1.2 +libglib1.2-dev +libglib2.0-0 +libglib2.0-cil +libglib2.0-data +libglib2.0-dev +libglibmm-2.4-1c2a +libglibmm-2.4-dev +libglide3 +libglpk0 +libglpng +libglu1-mesa +libglu1-mesa-dev +libglu1-xorg +libglu1-xorg-dev +libgmp3c2 +libgnokii3 +libgnome-desktop-2 +libgnome-keyring0 +libgnome-mag2 +libgnome-media0 +libgnome-menu2 +libgnome-pilot2 +libgnome-speech3 +libgnome-window-settings +libgnome2-0 +libgnome2-canvas-perl +libgnome2-common +libgnome2-perl +libgnome2-vfs-perl +libgnome2.0-cil +libgnome32 +libgnomecanvas2-0 +libgnomecanvas2-common +libgnomecups1.0-1 +libgnomecupsui1.0-1c2a +libgnomeprint2.2-0 +libgnomeprint2.2-data +libgnomeprintui2.2-0 +libgnomeprintui2.2-commo +libgnomesupport0 +libgnomeui-0 +libgnomeui-common +libgnomeui32 +libgnomevfs2-0 +libgnomevfs2-bin +libgnomevfs2-common +libgnomevfs2-extra +libgnorba27 +libgnorbagtk0 +libgnutls-dev +libgnutls12 +libgnutls13 +libgoffice-1-2 +libgoffice-1-common +libgpg-error-dev +libgpg-error0 +libgpgme11 +libgphoto2-2 +libgphoto2-2-dev +libgphoto2-port0 +libgpmg1 +libgpod0 +libgraflib1 +libgraflib1-dev +libgrafx11-1 +libgrafx11-1-dev +libgraphicsmagick1 +libgsf-1-114 +libgsf-1-common +libgsf-gnome-1-114 +libgsl0 +libgsl0-dev +libgsm1 +libgsmme1c2a +libgssapi2 +libgstreamer-plugins-bas +libgstreamer0.10-0 +libgstreamer0.8-0 +libgtk1.2 +libgtk1.2-common +libgtk1.2-dev +libgtk2-perl +libgtk2.0-0 +libgtk2.0-bin +libgtk2.0-cil +libgtk2.0-common +libgtk2.0-dev +libgtkglext1 +libgtkhtml3.2-11 +libgtkhtml3.6-18 +libgtkhtml3.8-15 +libgtkmm-2.4-1c2a +libgtkmm-2.4-dev +libgtksourceview-common +libgtksourceview1.0-0 +libgtksourceview2.0-cil +libgtkspell0 +libgtop2-7 +libgtop2-common +libgts-0.7-1 +libgucharmap4 +libguile-ltdl-1 +libgutenprint2 +libgutenprintui2-1 +libgwenhywfar-data +libgwenhywfar38 +libgwrap-runtime0 +libgwrap-runtime0-dev +libhal-storage1 +libhal1 +libhd13 +libhdf4g +libhdf5-serial-1.6.5-0 +libhdf5-serial-dev +libhfsp0 +libhtml-format-perl +libhtml-mason-perl +libhtml-parser-perl +libhtml-scrubber-perl +libhtml-tableextract-per +libhtml-tagset-perl +libhtml-template-expr-pe +libhtml-template-perl +libhtml-tree-perl +libhttp-ghttp-perl +libice-dev +libice6 +libicu36 +libid3-3.8.3c2a +libid3tag0 +libident +libidl0 +libidn11 +libidn11-dev +libiec61883-0 +libieee1284-3 +libifp4 +libijs-0.35 +libimage-base-bundle-per +libimage-info-perl +libimlib2 +libimlib2-dev +libindex0 +libio-pty-perl +libio-socket-ssl-perl +libio-string-perl +libio-stringy-perl +libiodbc2 +libipc-run-perl +libipc-sharelite-perl +libisc11 +libisccc0 +libisccfg1 +libiso9660-4 +libiw-dev +libiw28 +libjack0.100.0-0 +libjack0.100.0-dev +libjasper-1.701-1 +libjasper-1.701-dev +libjaxp1.3-java +libjcode-perl +libjcode-pm-perl +libjpeg-progs +libjpeg62 +libjpeg62-dev +libjsch-java +libk3b2 +libkadm55 +libkbanking1 +libkcal2b +libkcddb1 +libkdeedu3 +libkdegames1 +libkdepim1a +libkernlib1 +libkernlib1-dev +libkexif1 +libkgantt0 +libkipi0 +libkiten1 +libkjsembed1 +libkleopatra1 +libklibc +libkmime2 +libkonq4 +libkpathsea4 +libkpimexchange1 +libkpimidentities1 +libkrb5-dev +libkrb53 +libksba8 +libkscan1 +libksieve0 +libktnef1 +libktoblzcheck1c2a +liblcms1 +liblcms1-dev +libldap-2.3-0 +libldap2 +libldap2-dev +liblinphone1 +liblircclient0 +liblo0 +liblocale-gettext-perl +liblocale-maketext-fuzzy +liblocale-maketext-lexic +liblockdev1 +liblockfile1 +liblog-dispatch-perl +liblog4j1.2-java +liblog4net1.2-cil +liblogfile-rotate-perl +libloudmouth1-0 +liblrdf0 +libltdl3 +libltdl3-dev +liblua50 +liblua50-dev +liblualib50 +liblualib50-dev +liblucene-java +liblucene-java-doc +liblwres1 +liblwres9 +liblzo-dev +liblzo1 +libm17n-0 +libmad0 +libmad0-dev +libmagic1 +libmagick++9c2a +libmagick9 +libmagick9-dev +libmailtools-perl +libmal1 +libmath++0c2a +libmathlib2 +libmathlib2-dev +libmdc2 +libmeanwhile1 +libmediastreamer0 +libmetacity0 +libmhash2 +libmikmod2 +libmime-perl +libmimelib1c2a +libmldbm-perl +libmms0 +libmng-dev +libmng1 +libmodplug0c2 +libmodule-versions-repor +libmono-accessibility2.0 +libmono-cairo1.0-cil +libmono-cecil0.4-cil +libmono-corlib1.0-cil +libmono-corlib2.0-cil +libmono-data-tds1.0-cil +libmono-data-tds2.0-cil +libmono-microsoft-build2 +libmono-peapi1.0-cil +libmono-peapi2.0-cil +libmono-relaxng1.0-cil +libmono-security1.0-cil +libmono-security2.0-cil +libmono-sharpzip0.84-cil +libmono-sharpzip2.84-cil +libmono-system-data1.0-c +libmono-system-data2.0-c +libmono-system-runtime1. +libmono-system-runtime2. +libmono-system-web1.0-ci +libmono-system-web2.0-ci +libmono-system1.0-cil +libmono-system2.0-cil +libmono-winforms2.0-cil +libmono0 +libmono1.0-cil +libmono2.0-cil +libmopac7-0 +libmozjs0d +libmpcdec3 +libmpeg2-4 +libmpeg2-4-dev +libmpeg3-1 +libmpeg3-dev +libmpfr1 +libmpich1.0c2 +libmusicbrainz4c2a +libmx4j-java +libmyspell3c2 +libmysqlclient10 +libmysqlclient15-dev +libmysqlclient15off +libnasl2 +libnautilus-burn2 +libnautilus-burn3 +libnautilus-extension1 +libncp +libncurses5 +libncurses5-dev +libncursesw5 +libncursesw5-dev +libneon25 +libneon26 +libnessus2 +libnet-daemon-perl +libnet-ip-perl +libnet-ldap-perl +libnet-ssleay-perl +libnet0 +libnet1 +libnetcdf3 +libnetpbm10 +libnewt-dev +libnewt-utf8-0 +libnewt0.52 +libnfsidmap2 +libnids1.20 +libniftiio0 +libnjb5 +libnm-glib0 +libnotify1 +libnspr4 +libnspr4-0d +libnss-mdns +libnss3 +libnss3-0d +libntfs9 +libnumber-compare-perl +liboaf0 +libofx3 +libogg-dev +libogg0 +liboggflac3 +liboil0.3 +libopal-2.2.0 +libopenal0a +libopenbabel1 +libopencdk8 +libopencdk8-dev +libopenexr-dev +libopenexr2c2a +libopenobex1 +liborbit0 +liborbit2 +liboro-java +libortp5 +libosip2-3 +libosp5 +libostyle1c2 +libotf0 +libpacklib1 +libpacklib1-dev +libpam-modules +libpam-ncp +libpam-runtime +libpam0g +libpam0g-dev +libpanel-applet2-0 +libpango1.0-0 +libpango1.0-common +libpango1.0-dev +libpaper-utils +libpaper1 +libparams-util-perl +libparams-validate-perl +libpari-dev +libpari2-gmp +libparse-recdescent-perl +libparted1.6-0 +libparted1.7-1 +libparted1.7-dev +libpath-class-perl +libpawlib2 +libpawlib2-dev +libpcap0.7 +libpcap0.8 +libpcd2 +libpci2 +libpcre3 +libpcre3-dev +libpcrecpp0 +libpcsclite1 +libperl5.8 +libpg-perl +libpgsql2 +libpisock8 +libpisock9 +libpisync0 +libplot2c2 +libplplot9 +libplrpc-perl +libpng12-0 +libpng12-dev +libpod-tests-perl +libpoppler0c2 +libpoppler0c2-glib +libpoppler0c2-qt +libpopt-dev +libpopt0 +libportaudio0 +libpostproc0d +libpq-dev +libpq4 +libpqxx-2.6.8 +libprefork-perl +libpstoedit0c2a +libpt-1.10.0 +libpt-plugins-oss +libpt-plugins-v4l2 +libpth20 +libpulse0 +libpvm3 +libqbanking4 +libqcad0 +libqhull5 +libqscintilla6 +libqt3-compat-headers +libqt3-headers +libqt3-mt +libqt3-mt-dev +libqt3-mt-psql +libqt4-core +libqt4-gui +libqthreads-12 +libquantlib-0.3.13 +libquicktime-dev +libquicktime0 +libraptor1 +libraw1394-8 +libraw1394-dev +libreadline-ruby1.8 +libreadline4 +libreadline5 +libreadline5-dev +librecode0 +libregexp-common-perl +libregexp-java +libresid-builder0c2a +libresmgr1 +libroman-perl +librpcsecgss3 +librplay3 +librpm4 +librsvg2-2 +librsvg2-common +libruby1.8 +librxp1 +libsablot0 +libsamplerate0 +libsane +libsane-extras +libsasl2 +libsasl2-2 +libsasl2-dev +libsasl2-modules +libsc7 +libscrollkeeper0 +libsdl-console +libsdl-erlang +libsdl-gfx1.2-4 +libsdl-image1.2 +libsdl-mixer1.2 +libsdl-net1.2 +libsdl-pango1 +libsdl-perl +libsdl-ttf2.0-0 +libsdl1.2-dev +libsdl1.2debian +libsdl1.2debian-alsa +libselinux1 +libsensors3 +libsepol1 +libservlet2.3-java +libservlet2.4-java +libsexy2 +libsgmls-perl +libsgutils1 +libshout3 +libsidplay1 +libsidplay2 +libsigc++-2.0-0c2a +libsigc++-2.0-dev +libslang2 +libslang2-dev +libslp1 +libsm-dev +libsm6 +libsmbclient +libsmpeg0 +libsndfile1 +libsnmp-base +libsnmp9 +libsoup2.2-8 +libsp1c2 +libspeex1 +libsqlite0 +libsqlite3-0 +libss2 +libssl-dev +libssl0.9.6 +libssl0.9.7 +libssl0.9.8 +libssp0 +libstartup-notification0 +libstdc++2.10-glibc2.2 +libstdc++5 +libstdc++5-3.3-dev +libstdc++6 +libstdc++6-4.0-dev +libstdc++6-4.1-dev +libstroke0 +libstruts1.2-java +libsufary2 +libsvga1 +libsvga1-dev +libsvn1 +libswt3.2-gtk-java +libswt3.2-gtk-jni +libsysfs2 +libt1-5 +libtag1c2a +libtagc0 +libtasn1-3 +libtasn1-3-dev +libtemplate-perl +libterm-readkey-perl +libterm-readline-perl-pe +libtest-classapi-perl +libtest-inline-perl +libtext-autoformat-perl +libtext-charwidth-perl +libtext-format-perl +libtext-glob-perl +libtext-iconv-perl +libtext-quoted-perl +libtext-reform-perl +libtext-template-perl +libtext-wikiformat-perl +libtext-wrapi18n-perl +libtext-wrapper-perl +libtheora-dev +libtheora0 +libthunar-vfs-1-2 +libtidy-0.99-0 +libtiff-tools +libtiff4 +libtiff4-dev +libtiffxx0c2 +libtime-modules-perl +libtimedate-perl +libtomcat5-java +libtomcat5.5-java +libtool +libtotem-plparser1 +libtree-simple-perl +libtse3-0.3.1c2a +libttf2 +libtunepimp-bin +libtunepimp3 +libufsparse +libungif4-dev +libungif4g +libuniconf4.2 +liburi-perl +libusb-0.1-4 +libusb-dev +libuuid1 +libvcdinfo0 +libvisual-0.4-0 +libvolume-id0 +libvorbis-dev +libvorbis0a +libvorbisenc2 +libvorbisfile3 +libvte-common +libvte4 +libvtk5 +libvtk5-dev +libwant-perl +libwavpack0 +libweakref-perl +libwmf-bin +libwmf-dev +libwmf0.2-7 +libwnck-common +libwnck18 +libwpd8c2a +libwrap0 +libwrap0-dev +libwraster3 +libwv-1.2-1 +libwv-1.2-3 +libwv2-1c2 +libwvstreams4.2-base +libwvstreams4.2-extras +libwww-perl +libwxbase2.6-0 +libwxgtk2.4-1 +libwxgtk2.6-0 +libx11-6 +libx11-data +libx11-dev +libxalan110 +libxau-dev +libxau6 +libxaw-headers +libxaw6 +libxaw7 +libxaw7-dev +libxcomp1 +libxcompext1 +libxcomposite-dev +libxcomposite1 +libxcursor-dev +libxcursor1 +libxdamage-dev +libxdamage1 +libxdelta2 +libxdmcp-dev +libxdmcp6 +libxerces2-java +libxerces27 +libxevie-dev +libxevie1 +libxext-dev +libxext6 +libxfce4mcs-client3 +libxfce4mcs-manager3 +libxfce4util4 +libxfcegui4-4 +libxfixes-dev +libxfixes3 +libxfont-dev +libxfont1 +libxft-dev +libxft2 +libxi-dev +libxi6 +libxine-dev +libxine1 +libxinerama-dev +libxinerama1 +libxkbfile-dev +libxkbfile1 +libxkbui-dev +libxkbui1 +libxklavier10 +libxml++1.0c2a +libxml-dom-perl +libxml-filter-buffertext +libxml-libxml-common-per +libxml-libxml-perl +libxml-libxslt-perl +libxml-namespacesupport- +libxml-parser-perl +libxml-perl +libxml-regexp-perl +libxml-rss-perl +libxml-sablot-perl +libxml-sax-machines-perl +libxml-sax-perl +libxml-sax-writer-perl +libxml-simple-perl +libxml-xpath-perl +libxml1 +libxml2 +libxml2-dev +libxml2-utils +libxmu-dev +libxmu-headers +libxmu6 +libxmuu-dev +libxmuu1 +libxp-dev +libxp6 +libxplc0.3.13 +libxpm-dev +libxpm4 +libxrandr-dev +libxrandr2 +libxrender-dev +libxrender1 +libxres-dev +libxres1 +libxslt1-dev +libxslt1.1 +libxss-dev +libxss1 +libxt-dev +libxt6 +libxtrap-dev +libxtrap6 +libxtst-dev +libxtst6 +libxul-common +libxul0d +libxv-dev +libxv1 +libxvmc-dev +libxvmc1 +libxxf86dga-dev +libxxf86dga1 +libxxf86misc-dev +libxxf86misc1 +libxxf86vm-dev +libxxf86vm1 +libzipios++0c2a +libzvbi-common +libzvbi-dev +libzvbi-doc +libzvbi0 +libzvt2.0-0 +lilo +lilypond-data +lilypond-doc +linneighborhood +linphone +linphone-common +linphone-nox +linux-image-2.6.19 +linux-kernel-headers-kno +linux-sound-base +linuxdoc-tools +linuxdoc-tools-info +linuxdoc-tools-latex +linuxdoc-tools-text +lisa +loadlin +locales +lockfile-progs +login +logrotate +lookup +loop-aes-modules-2.6.19 +loop-aes-source +loop-aes-utils +lrzsz +lsb +lsb-base +lsb-core +lsb-cxx +lsb-desktop +lsb-graphics +lsb-qt4 +lsb-release +lsdvd +lskat +lsof +ltrace +lua50 +lvm-common +lvm2 +lynx +lyx +lyx-common +lyx-qt +lyx-xforms +lzop +m17n-db +m4 +macutils +madwifi-modules-2.6.19 +madwifi-source +madwifi-tools +mailx +make +makedev +man-db +manpages +manpages-de +manpages-dev +matwrap +mawk +maxima +maxima-doc +maxima-emacs +maxima-share +maxima-src +maxima-test +mayavi +mbr +mc +mcl +mcl-doc +mdadm +med-common +med-tools +medcon +memtest86 +memtest86+ +memtester +mencal +menu +menu-xdg +mesa-common-dev +mesa-utils +metacity +metacity-common +metamail +mgdiff +mgp +mikmod +mime-support +mimms +mindi +mindi-busybox +mindi-kernel +mindi-partimagehack +minicom +misdn-utils +misdn-voipisdn +mkbootdev +mkisofs +hi +mktemp +mldonkey-gui +mldonkey-server +mlock +mobilemesh +modconf +module-assistant +module-init-tools +modutils +mondo +mondo-doc +mono +mono-apache-server +mono-common +mono-devel +mono-gac +mono-gmcs +mono-jay +mono-jit +mono-mcs +mono-runtime +mono-utils +mono-xsp-base +monodevelop +monodoc-base +monodoc-browser +monodoc-http +monodoc-manual +monopd +monotone +mount +mouseconfig +mozilla-browser +mozilla-firefox +mozilla-helix-player +mozilla-psm +mozilla-thunderbird +mozilla-thunderbird-insp +mozilla-thunderbird-type +mpack +mpage +mpg321 +mplayer +mplayer-skin-blue +mpqc +mpqc-support +ms-sys +mt-st +mtools +mtr +mtx +multimix +mutt +myspell-bg +myspell-de-at +myspell-de-ch +myspell-de-de +myspell-en-gb +myspell-en-us +myspell-es +myspell-fr +myspell-it +myspell-pl +mysql-client +mysql-client-5.0 +mysql-common +mysql-server +mysql-server-5.0 +mysql-zrm +mysql-zrm-socket-server +nagios-nrpe-plugin +nagios-plugins-basic +nagios2 +nagios2-common +nagios2-doc +nano +nasm +nautilus +nautilus-cd-burner +nautilus-data +ncftp +ncpfs +ncurses-base +ncurses-bin +ncurses-term +ndiswrapper-modules-2.6. +ndiswrapper-source +nedit +nessus +nessus-plugins +nessusd +net-tools +netbase +netcat +netcat6 +nethack-common +nethack-console +nethack-qt +nethack-x11 +netpbm +netpipe-tcp +netpipes +netris +netspeed +networkstatus +neverball +neverdata +nfs-common +nfs-kernel-server +ngrep +nis +nkf +nmap +noteedit +noteedit-data +nowebm +nparted +ntfs-3g +ntpdate +nvtv +nvu +nxagent +nxclient +nxdesktop +nxlibs +nxproxy +nxssh +nxtunnel-client +nxtunnel-server +oaf +obconf +ocaml-base-nox +ocfs2-tools +ocfs2console +octave +octave-epstk +octave-sp +octave-statdataml +octave2.1 +octave2.9 +octave2.9-doc +octave2.9-headers +octave2.9-htmldoc +odbc-postgresql +odbcinst1debian1 +ofx +oneko +openbox +openbsd-inetd +openhackware +openjade +openjade1.3 +openoffice-de-en +openoffice.org-debian-me +opensched +openssh-client +openssh-server +openssl +openvpn +outguess +p0f +pari-doc +pari-extra +pari-gp +parted-bf +partimage +partimage-server +passwd +patch +patchutils +paw +paw-common +paw-demos +pax +pcb +pciutils +pciutils-dev +pcmcia-cs +pcmciautils +pdl +pentanet-doc +pentanet-utils +perl +perl-base +perl-doc +perl-modules +perl-suid +perl-tk +perlmagick +pgapack +pgdocs-pdf-a4 +pgf +pgpgpg +php5 +php5-common +php5-gd +php5-imap +php5-ldap +php5-mhash +php5-mysql +phpmyadmin +pi +pia +pilot-link +pinentry-qt +pingus +pingus-data +pioneers-ai +pioneers-client +pioneers-help +pioneers-server-console +pioneers-server-data +pioneers-server-gtk +pkg-config +planetpenguin-racer +planetpenguin-racer-data +planner +playmidi +plib1.8.4c2 +plotutils +pm-dev +pmidi +pmount +pmtools +pnm2ppa +po-debconf +portmap +poster +postgresql-8.0 +postgresql-client-8.0 +postgresql-client-common +postgresql-common +postgresql-contrib-8.0 +postgresql-doc-8.0 +postgresql-plperl-8.0 +postgresql-plpython-8.0 +postgresql-pltcl-8.0 +postgresql-server-dev-8. +potrace +powermgmt-base +poxml +ppmd +ppp +hi +pppdcapiplugin +pppoe +pppoeconf +pppstatus +pptp-linux +prelink +preview-latex-style +print-utils-pfeifle +prism54-nonfree +procinfo +procmail +procps +proj +proll +psfontmgr +psgml +psmisc +pspp +psutils +pump +pvm +pxlib1 +pybliographer +python +python-alsaaudio +python-apt +python-bibtex +python-cairo +python-central +python-dbus +python-doc +python-egenix-mxdatetime +python-egenix-mxtools +python-extclass +python-glade2 +python-gmenu +python-gnome2 +python-gnome2-desktop +python-gst0.10 +python-gtk-1.2 +python-gtk2 +python-imaging +python-imaging-doc +python-imaging-doc-html +python-imaging-doc-pdf +python-imaging-tk +python-ldap +python-libxml2 +python-minimal +python-netcdf +python-numeric +python-numeric-ext +python-numeric-tutorial +python-pygresql +python-pyorbit +python-pysqlite2 +python-scientific +python-scientific-doc +python-sigmask +python-support +python-tk +python-vtk +python-wxgtk2.4 +python-wxgtk2.6 +python-wxversion +python-xml +python2.1 +python2.3 +python2.3-dev +python2.3-doc +python2.4 +python2.4-doc +python2.4-minimal +qca-tls +qcad +qemu +qm +qmtest +qobex +qps +qt3-assistant +qt3-designer +qt3-dev-tools +qt3-doc +qtparted +quanta +quanta-data +quantlib-examples +quantlib-python +quantlib-refman +quantlib-refman-html +quantlib-ruby +r-base +r-base-core +r-base-dev +r-base-html +r-base-latex +r-cran-abind +r-cran-acepack +r-cran-boot +r-cran-car +r-cran-chron +r-cran-cluster +r-cran-coda +r-cran-dbi +r-cran-design +r-cran-effects +r-cran-foreign +r-cran-gdata +r-cran-gmodels +r-cran-gplots +r-cran-gregmisc +r-cran-gtkdevice +r-cran-gtools +r-cran-hmisc +r-cran-its +r-cran-kernsmooth +r-cran-lattice +r-cran-lmtest +r-cran-mapdata +r-cran-maps +r-cran-mcmcpack +r-cran-mgcv +r-cran-multcomp +r-cran-mvtnorm +r-cran-nlme +r-cran-qtl +r-cran-quadprog +r-cran-rcmdr +r-cran-relimp +r-cran-rgl +r-cran-rmysql +r-cran-rodbc +r-cran-rpart +r-cran-rquantlib +r-cran-sandwich +r-cran-sm +r-cran-statdataml +r-cran-strucchange +r-cran-survival +r-cran-tkrplot +r-cran-tseries +r-cran-vr +r-cran-xml +r-cran-zoo +r-doc-html +r-doc-info +r-doc-pdf +r-mathlib +r-recommended +radio +raptor-utils +ratmenu +ratpoison +rcalc +rcs +rdate +rdesktop +readline-common +realpath +recode +recover +refblas3 +refblas3-dev +reiserfsprogs +reportbug +request-tracker3 +request-tracker3.4 +resmgr +rfb +rhythmbox +rocklight +rootstrap +rosegarden +rosegarden-data +rosegarden4 +rplay-client +rpm +rsync +rt2x00-cvs-modules-2.6.1 +rt3-clients +rt3.4-apache +rt3.4-clients +rtai +rtai-doc +rtai-source +rtfm +rubber +ruby +ruby-examples +ruby1.8 +rxp +rxvt-beta +s3switch +samba +samba-common +sane +sane-utils +sash +sbcl +sbl-auto-udeb +scanmodem +scantv +scli +scons +screen +scribus +scribus-doc-de +scribus-doc-en +scribus-doc-fr +scrollkeeper +scsitools +scummvm +sdic +sdic-edict +secpolicy +sed +selfhtml +sendemail +sendfile +sendip +setserial +sfftobmp +sffview +sg3-utils +sgml-base +sgml-data +sgmlspl +sgmltools-lite +shaper +shared-mime-info +sharutils +sitar +slang1 +slang1a-utf8 +slapd +sleuthkit +slib +slirp +slrn +smail +smake +smartmontools +smbclient +smbconf-pfeifle +smbconf-pfeifle-nonfree +smbfs +smpeg-plaympeg +smpeg-xmms +sniffit +sodipodi +sound-juicer +sound-recorder +sox +sp +speedtouch +speex +spell +spellutils +sqlite +sqlite-doc +squid +squid-common +squidclient +ssh +ssl-cert +sslwrap +star +statserial +stellarium +stellarium-data +strace +stress +stunnel +subversion +sudo +sufary +sun-java5-bin +sun-java5-demo +sun-java5-fonts +sun-java5-jdk +sun-java5-jre +sun-java5-plugin +sunbird +sweep +swi-prolog +sylpheed +sylpheed-doc +sylpheed-i18n +symlinks +synaptic +sysklogd +syslinux +system-tools-backends +sysv-rc +sysvinit +sysvinit-utils +tar +tcl8.3 +tcl8.4 +tclreadline +tcpd +tcpdump +telnet-ssl +telnetd-ssl +terminatorx +testdisk +tetex-base +tetex-bin +tetex-doc +tetex-extra +tex-common +tex4ht +tex4ht-common +texi2html +texinfo +texmacs +texmacs-common +tftp +tftpd-hpa +thttpd +thunar +thunderbird +thunderbird-inspector +thunderbird-locale-bg +thunderbird-locale-cs +thunderbird-locale-da +thunderbird-locale-de +thunderbird-locale-el +thunderbird-locale-es-es +thunderbird-locale-fi +thunderbird-locale-fr +thunderbird-locale-gu +thunderbird-locale-he +thunderbird-locale-hu +thunderbird-locale-it +thunderbird-locale-ja +thunderbird-locale-ko +thunderbird-locale-mk +thunderbird-locale-nb +thunderbird-locale-nl +thunderbird-locale-ru +thunderbird-locale-sk +thunderbird-locale-sl +thunderbird-locale-sv +thunderbird-locale-tr +thunderbird-locale-zh-cn +thunderbird-typeaheadfin +tidy +tidy-doc +tiger +tightvncserver +timeout +timezoneconf +timidity +timidity-patches +tint +tix +tk8.3 +tk8.4 +tkdiff +tnef +tofrodos +tomcat5 +tomcat5-admin +tomcat5-webapps +toppler +tora +totem +totem-mozilla +totem-xine +tpconfig +traceroute +trang +trans-de-en +transfig +tripwire +tsclient +tshark +tsocks +ttf-arabeyes +ttf-arphic-bsmi00lp +ttf-bengali-fonts +ttf-bitstream-vera +ttf-dejavu +ttf-devanagari-fonts +ttf-dustin +ttf-f500 +ttf-farsiweb +ttf-freefont +ttf-gentium +ttf-gujarati-fonts +ttf-indic-fonts +ttf-isabella +ttf-junicode +ttf-kannada-fonts +ttf-kochi-gothic +ttf-malayalam-fonts +ttf-openoffice +ttf-opensymbol +ttf-oriya-fonts +ttf-punjabi-fonts +ttf-sjfonts +ttf-staypuft +ttf-summersby +ttf-tamil-fonts +ttf-telugu-fonts +ttmkfdir +tuxeyes +tuxkart +tuxkart-data +tuxmath +tuxpaint +tuxpaint-data +tuxpaint-stamps-default +tuxpuck +tuxtype +tuxtype-data +tvtime +twm +txt2regex +type-handling +type1inst +tzdata +ucf +udev +udpcast +umbrello +uml-utilities +umlrun +umlrun-uml +unifont +units +unixodbc +unp +unzip +unzoo +update +update-inetd +urlview +usbutils +usbview +user-de +user-mode-linux +user-mode-linux-doc +util-linux +util-linux-locales +uudeview +uuid-dev +v4l-conf +valgrind +vcdimager +vcdtools +vdr +vegastrike +vegastrike-data +vegastrike-music +verilog +vgabios +vigor +vim +vim-common +vim-gtk +vim-gui-common +vim-runtime +vim-scripts +vimpart +vino +vis5d-doc +vlan +vnc-common +vorbis-tools +vpnc +vrms +vtk-doc +vtk-examples +vtk-tcl +w3-dtd-mathml +w3c-dtd-xhtml +w3m +wakeonlan +wamerican +wavemon +wavtools +wbritish +wcanadian +wcatalan +wfrench +wget +wheretero +whiptail +whisker +whitespace +whois +wine +wine-dev +winetools +wings3d +wipe +wireless-tools +wireshark +wireshark-common +witalian +wmaker +wmaker-data +wmaker-usersguide-ps +wmakerconf +wmakerconf-data +wngerman +wnorwegian +wodim +wordnet +wordnet-base +wordtrans-data +wpasupplicant +wpolish +wprint +wv +wvdial +wwwconfig-common +wxmaxima +x-ttcidfont-conf +x11-common +x11proto-bigreqs-dev +x11proto-composite-dev +x11proto-core-dev +x11proto-damage-dev +x11proto-dmx-dev +x11proto-evie-dev +x11proto-fixes-dev +x11proto-fontcache-dev +x11proto-fonts-dev +x11proto-gl-dev +x11proto-input-dev +x11proto-kb-dev +x11proto-print-dev +x11proto-randr-dev +x11proto-record-dev +x11proto-render-dev +x11proto-resource-dev +x11proto-scrnsaver-dev +x11proto-trap-dev +x11proto-video-dev +x11proto-xcmisc-dev +x11proto-xext-dev +x11proto-xf86bigfont-dev +x11proto-xf86dga-dev +x11proto-xf86dri-dev +x11proto-xf86misc-dev +x11proto-xf86vidmode-dev +x11proto-xinerama-dev +x3270 +xalan +xaos +xaw3dg +xawtv +xawtv-plugins +xbase-clients +xbattle +xbitmaps +xboard +xboing +xchat +xchat-common +xclass-common +xcursor-themes +xdelta +xdg-utils +xdialog +xdm +xemacs21 +xemacs21-basesupport +xemacs21-bin +xemacs21-mule +xemacs21-mulesupport +xemacs21-support +xemacs21-supportel +xen-docs-3.0 +xen-hypervisor-3.0-i386 +xen-utils-3.0.3-1 +xen-utils-common +xfce +xfce4 +xfce4-icon-theme +xfce4-mcs-manager +xfce4-mcs-plugins +xfce4-mixer +xfce4-mixer-alsa +xfce4-panel +xfce4-session +xfce4-utils +xfdesktop4 +xfig +xfonts-100dpi +xfonts-100dpi-transcoded +xfonts-75dpi +xfonts-75dpi-transcoded +xfonts-base +xfonts-base-transcoded +xfonts-bolkhov-cp1251-75 +xfonts-bolkhov-cp1251-mi +xfonts-dosemu +xfonts-encodings +xfonts-scalable +xfonts-terminus +xfonts-utils +xfonts-x3270-misc +xfprint4 +xfsdump +xfsprogs +xfwm4 +xfwm4-themes +xgalaga +xine-ui +xjdic +xkb-data +xkbset +xlib6g +xlibmesa-gl +xlibmesa-gl-dev +xlibs +xlibs-static-dev +xloadimage +xmaxima +xmedcon +xmhtml1 +xml-core +xmms +xmms-cdread +xmms-goom +xmms-modplug +xmms-volnorm +xnest +xorg +xorg-dev +xosview +xpaint +xpdf +xpdf-common +xpdf-reader +xpdf-utils +xppaut +xsane +xsane-common +xscreensaver +xscreensaver-gl +xscreensaver-gnome +xserver-xorg +xserver-xorg-core +xserver-xorg-dev +xserver-xorg-input-all +xserver-xorg-input-evdev +xserver-xorg-input-kbd +xserver-xorg-input-mouse +xserver-xorg-input-synap +xserver-xorg-input-wacom +xserver-xorg-video-all +xserver-xorg-video-apm +xserver-xorg-video-ark +xserver-xorg-video-ati +xserver-xorg-video-chips +xserver-xorg-video-cirru +xserver-xorg-video-cyrix +xserver-xorg-video-dummy +xserver-xorg-video-fbdev +xserver-xorg-video-glint +xserver-xorg-video-i128 +xserver-xorg-video-i740 +xserver-xorg-video-i810 +xserver-xorg-video-imstt +xserver-xorg-video-mga +xserver-xorg-video-neoma +xserver-xorg-video-newpo +xserver-xorg-video-nsc +xserver-xorg-video-nv +xserver-xorg-video-rendi +xserver-xorg-video-s3 +xserver-xorg-video-s3vir +xserver-xorg-video-savag +xserver-xorg-video-silic +xserver-xorg-video-sis +xserver-xorg-video-sisus +xserver-xorg-video-tdfx +xserver-xorg-video-tga +xserver-xorg-video-tride +xserver-xorg-video-tseng +xserver-xorg-video-v4l +xserver-xorg-video-vesa +xserver-xorg-video-vga +xserver-xorg-video-via +xserver-xorg-video-vmwar +xserver-xorg-video-voodo +xskat +xsltproc +xterm +xtightvncviewer +xtrans-dev +xtv +xutils +xutils-dev +xviddetect +xvier +xvncviewer +xvt +xwpe +xzoom +yacas +yacas-doc +yacas-proteus +yafray +yelp +yorick +yorick-data +yorick-doc +zenity +zile +zip +zlib-bin +zlib1g +zlib1g-dev diff --git a/lists/mini b/lists/mini new file mode 100644 index 0000000..434bde0 --- /dev/null +++ b/lists/mini @@ -0,0 +1,4 @@ +# /usr/share/make-live/lists/mini - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny diff --git a/lists/minimal b/lists/minimal new file mode 100644 index 0000000..dd81279 --- /dev/null +++ b/lists/minimal @@ -0,0 +1,4 @@ +# /usr/share/make-live/lists/minimal - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny diff --git a/lists/minimal-net b/lists/minimal-net new file mode 100644 index 0000000..0609035 --- /dev/null +++ b/lists/minimal-net @@ -0,0 +1,8 @@ +# /usr/share/make-live/lists/minimal-net - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Network +bind9-host dhcp-client dnsutils ftp ifupdown iptables iputils-ping mtr-tiny +net-tools netbase netcat openssh-client telnet traceroute wget whois diff --git a/lists/rescue b/lists/rescue new file mode 100644 index 0000000..256b6ea --- /dev/null +++ b/lists/rescue @@ -0,0 +1,57 @@ +# /usr/share/make-live/lists/rescue - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# Rescue + +# Editors +mc nano-tiny qemacs-nox mg aview +# Harddisk +hdparm blktool scsitools +# Memory +memtester memtest86+ dmidecode +# System +procinfo pciutils usbutils hwinfo hwtools x86info cpuid +# Tools +tofrodos rpncalc units +# Browser +lynx links w3m +# Compression +unzip zip +# Backup +dar ddrescue gddrescue + +hal +read-edid +discover +wdiff +gawk +dc +dash +rlwrap +posh +chkrootkit +rkhunter +parted +partimage +grub +lilo +testdisk +xfsprogs +reiserfsprogs +e2fsprogs +ext2resize +ntfsprogs +dosfstools +genisoimage +wodim +dvd+rw-tools +clamav +clamav-data +wipe +secure-delete +minicom diff --git a/lists/standard b/lists/standard new file mode 100644 index 0000000..4da4dd2 --- /dev/null +++ b/lists/standard @@ -0,0 +1,7 @@ +# /usr/share/make-live/lists/standard - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales diff --git a/lists/standard-x11 b/lists/standard-x11 new file mode 100644 index 0000000..7f4bc4b --- /dev/null +++ b/lists/standard-x11 @@ -0,0 +1,10 @@ +# /usr/share/make-live/lists/x11 - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# X11 +xorg xresprobe diff --git a/lists/xfce b/lists/xfce new file mode 100644 index 0000000..b6c22ae --- /dev/null +++ b/lists/xfce @@ -0,0 +1,13 @@ +# /usr/share/make-live/lists/xfce - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# Xfce +gdm xfce4 +desktop-base + +xorg xresprobe diff --git a/lists/xfce-junior b/lists/xfce-junior new file mode 100644 index 0000000..1fc3269 --- /dev/null +++ b/lists/xfce-junior @@ -0,0 +1,19 @@ +# /usr/share/make-live/lists/xfce - package list for make-live(1) + +# Minimal +eject file sudo vim-tiny + +# Standard +console-common kbd locales + +# Xfce +gdm xfce4 +desktop-base + +xorg xresprobe + +# Debian Junior +junior-sound junior-typing junior-internet junior-gnome junior-toys +junior-games-net junior-games-sim junior-games-gl junior-puzzle junior-arcade +junior-math junior-writing junior-games-card junior-programming junior-system +junior-art junior-doc junior-games-text junior-kde diff --git a/src/config b/src/config deleted file mode 100644 index 7196b6c..0000000 --- a/src/config +++ /dev/null @@ -1,116 +0,0 @@ -# /etc/make-live.conf - configuration file for make-live(8) - -# make-live does work out of the box. However, if you want to customize it, -# you can edit the variables below. Look make-live.conf(8) for more information. - -# Root directory (Default: `pwd`/debian-live) -#LIVE_ROOT="`pwd`/debian-live" - -# Image type (Default: iso) -#LIVE_TYPE="iso" - -# Bootstrap architecture (Default: auto-detected) -#LIVE_ARCHITECTURE="i386" - -# Boot parameters (Default: empty) -#LIVE_BOOTAPPEND="" - -# Chroot directory (Default: ${LIVE_ROOT}/chroot) -#LIVE_CHROOT="${LIVE_ROOT}/chroot" - -# Configuration file (Default: /etc/make-live.conf) -#LIVE_CONFIG="/etc/make-live.conf" - -# Debian distribution (Default: sid) -#LIVE_DISTRIBUTION="sid" - -# Image filesystem (Default: squashfs for iso, plain for net) -#LIVE_FILESYSTEM="squashfs" - -# Bootstrap flavour (Default: standard) -#LIVE_FLAVOUR="standard" - -# Bootstrap config (Default: empty) -#LIVE_BOOTSTRAP_CONFIG="" - -# User command (Default: empty) -#LIVE_HOOK="" - -# Chroot includes (Default: empty) -#LIVE_INCLUDE_CHROOT="" - -# Image includes (Default: empty) -#LIVE_INCLUDE_IMAGE="" - -# Kernel flavour (Default: auto-detected) -#LIVE_KERNEL="" - -# Kernel packages (Default: auto-detected) -#LIVE_KERNEL_PACKAGES="" - -# Desktop package manifest (Default: empty) -#LIVE_MANIFEST="" - -# Debian mirror (Default: http://ftp.debian.org/debian/) -#LIVE_MIRROR="http://ftp.debian.org/debian/" - -# Debian security mirror (Default: http://security.debian.org/) -#LIVE_MIRROR_SECURITY="http://security.debian.org/" - -# Packages (Default: empty) -#LIVE_PACKAGES="" - -# Package list (Default: standard) -#LIVE_PACKAGE_LIST="standard" - -# Chroots ftp_proxy (Default: empty) -#LIVE_PROXY_FTP="" - -# Chroots http_proxy (Default: empty) -#LIVE_PROXY_HTTP="" - -# Custom repositories (Default: none) -#LIVE_REPOSITORIES="" - -# Custom repository list -LIVE_REPOSITORY_bpo="http://www.backports.org/debian/" -LIVE_REPOSITORY_KEY_bpo="http://backports.org/debian/archive.key" -LIVE_REPOSITORY_KEYRING_bpo="" -LIVE_REPOSITORY_DISTRIBUTION_bpo="sarge-backports" -LIVE_REPOSITORY_SECTIONS_bpo="main contrib non-free" - -LIVE_REPOSITORY_edu="http://ftp.skolelinux.org/skolelinux/" -LIVE_REPOSITORY_KEY_edu="" -LIVE_REPOSITORY_KEYRING_edu="debian-edu-archive-keyring" -LIVE_REPOSITORY_DISTRIBUTION_edu="etch-test" -LIVE_REPOSITORY_SECTIONS_edu="local" - -LIVE_REPOSITORY_restricted="http://ftp.debian-unofficial.org/debian-restricted/" -LIVE_REPOSITORY_KEY_restricted="http://ftp-master.debian-unofficial.org/key_2007.asc" -LIVE_REPOSITORY_KEYRING_restricted="debian-unofficial-archive-keyring" -LIVE_REPOSITORY_DISTRIBUTION_restricted="" -LIVE_REPOSITORY_SECTIONS_restricted="restricted" - -LIVE_REPOSITORY_fai="http://www.informatik.uni-koeln.de/fai/download/" -LIVE_REPOSITORY_KEY_fai="" -LIVE_REPOSITORY_KEYRING_fai="" -LIVE_REPOSITORY_DISTRIBUTION_fai="etch" -LIVE_REPOSITORY_SECTIONS_fai="koeln" - -# Debian section (Default: main) -#LIVE_SECTIONS="main" - -# Netboot server (Default: 192.168.1.1) -#LIVE_SERVER_ADDRESS="" - -# Netboot path (Default: /srv/debian-live/chroot) -#LIVE_SERVER_PATH="" - -# Image templates (Default: /usr/share/make-live/templates) -#LIVE_TEMPLATES="/usr/share/make-live/templates" - -# Generic package indices (Default: no) -#LIVE_GENERIC_INDICES="no" - -# Source images (Default: no) -#LIVE_SOURCE="no" diff --git a/src/hooks/mini b/src/hooks/mini deleted file mode 100644 index 16df392..0000000 --- a/src/hooks/mini +++ /dev/null @@ -1,9 +0,0 @@ -# /usr/share/make-live/hooks/minimal - hook list for make-live(8) - -# Remove unused packages -apt-get remove --purge --yes apt-utils libdb4.4 - -# Remove unused files -rm -rf /usr/share/doc -rm -rf /usr/share/locale -rm -rf /usr/share/man diff --git a/src/hooks/minimal b/src/hooks/minimal deleted file mode 100644 index de36a30..0000000 --- a/src/hooks/minimal +++ /dev/null @@ -1,4 +0,0 @@ -# /usr/share/make-live/hooks/minimal - hook list for make-live(8) - -# Remove unused packages -#apt-get remove --purge --yes apt-utils libdb4.4 diff --git a/src/lists/gnome b/src/lists/gnome deleted file mode 100644 index 3e831cf..0000000 --- a/src/lists/gnome +++ /dev/null @@ -1,17 +0,0 @@ -# /usr/share/make-live/lists/gnome - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# GNOME -gdm gdm-themes gnome-desktop-environment gnome-cups-manager gnome-screensaver -gnome-themes-extras -desktop-base - -rhythmbox synaptic - -x-window-system-core -xresprobe diff --git a/src/lists/gnome-core b/src/lists/gnome-core deleted file mode 100644 index f51a2ef..0000000 --- a/src/lists/gnome-core +++ /dev/null @@ -1,14 +0,0 @@ -# /usr/share/make-live/lists/gnome-core - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# GNOME Core -gdm gnome-core -desktop-base - -x-window-system-core -xresprobe diff --git a/src/lists/gnome-full b/src/lists/gnome-full deleted file mode 100644 index d049e15..0000000 --- a/src/lists/gnome-full +++ /dev/null @@ -1,14 +0,0 @@ -# /usr/share/make-live/lists/gnome-full - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# GNOME Full -gdm gnome -desktop-base - -x-window-system-core -xresprobe diff --git a/src/lists/gnome-junior b/src/lists/gnome-junior deleted file mode 100644 index e05a969..0000000 --- a/src/lists/gnome-junior +++ /dev/null @@ -1,23 +0,0 @@ -# /usr/share/make-live/lists/gnome - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# GNOME -gdm gdm-themes gnome-desktop-environment gnome-cups-manager gnome-screensaver -gnome-themes-extras -desktop-base - -rhythmbox synaptic - -x-window-system-core -xresprobe - -# Debian Junior -junior-sound junior-typing junior-internet junior-gnome junior-toys -junior-games-net junior-games-sim junior-games-gl junior-puzzle junior-arcade -junior-math junior-writing junior-games-card junior-programming junior-system -junior-art junior-doc junior-games-text diff --git a/src/lists/gnustep b/src/lists/gnustep deleted file mode 100644 index 89623b0..0000000 --- a/src/lists/gnustep +++ /dev/null @@ -1,29 +0,0 @@ -# /usr/share/make-live/lists/x11-core - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# X11 -wdm x-window-system-core - -# GNUstep -gnustep gnumail.app talksoup.app viewpdf.app wmaker gnustep-icons -gnustep-examples gnumail-doc aclock.app biococoa.app timemon.app cenon.app wmnd -bubblefishymon wmmixer wmpinboard gworkspace.app clipbook.app poe.app -plopfolio.app mpdcon.app lusernet.app helpviewer.app gnuwash.app easydiff.app -displaycalibrator.app cynthiune.app agenda.app stepulator.app edenmath.app -price.app volumecontrol.app latex.service wildmenus.bundle innerspace.app - -gnustep-core - -gnustep-core-devel gnustep-base-examples - -gnustep-core-doc gnustep-tutorial-html gnustep-tutorial-pdf - -gnustep-games gridlock.app - -gnustep-devel librenaissance0-dev steptalk libpantomime1-dev -popplerkit.framework gnustep-netclasses diff --git a/src/lists/kde b/src/lists/kde deleted file mode 100644 index 0dedbf6..0000000 --- a/src/lists/kde +++ /dev/null @@ -1,14 +0,0 @@ -# /usr/share/make-live/lists/kde - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# KDE -kde kdm -desktop-base - -x-window-system-core -xresprobe diff --git a/src/lists/kde-core b/src/lists/kde-core deleted file mode 100644 index 9e85cf4..0000000 --- a/src/lists/kde-core +++ /dev/null @@ -1,14 +0,0 @@ -# /usr/share/make-live/lists/kde-core - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# KDE Core -kde-core kdm -desktop-base - -x-window-system-core -xresprobe diff --git a/src/lists/kde-core-i18n b/src/lists/kde-core-i18n deleted file mode 100644 index cdb1501..0000000 --- a/src/lists/kde-core-i18n +++ /dev/null @@ -1,33 +0,0 @@ -# /usr/share/make-live/lists/kde-core-i18n - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# Standard i18n -manpages manpages-dev manpages-de manpages-de-dev manpages-es manpages-es-extra -manpages-fi manpages-fr manpages-fr-dev manpages-fr-extra 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 - -# KDE Core -kde-core kdm -desktop-base - -x-window-system-core -xresprobe - -# KDE i18n -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 kde-i18n-zhtw diff --git a/src/lists/kde-extra b/src/lists/kde-extra deleted file mode 100644 index cd7c01a..0000000 --- a/src/lists/kde-extra +++ /dev/null @@ -1,20 +0,0 @@ -# /usr/share/make-live/lists/kde-extra - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# KDE -kde kdm -desktop-base - -x-window-system-core -xresprobe - -# KDE Full -koffice - -# KDE Extra -kde-extras diff --git a/src/lists/kde-extra-i18n b/src/lists/kde-extra-i18n deleted file mode 100644 index 7a25a58..0000000 --- a/src/lists/kde-extra-i18n +++ /dev/null @@ -1,52 +0,0 @@ -# /usr/share/make-live/lists/kde-extra-i18n - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# Standard i18n -manpages manpages-dev manpages-de manpages-de-dev manpages-es manpages-es-extra -manpages-fi manpages-fr manpages-fr-dev manpages-fr-extra 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 - -# KDE -kde kdm -desktop-base - -x-window-system-core -xresprobe - -# KDE i18n -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 kde-i18n-zhtw - -# KDE Full -koffice - -# KDE Full i18n -koffice-i18n-af koffice-i18n-ar koffice-i18n-bg koffice-i18n-br koffice-i18n-bs -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-eu koffice-i18n-fi koffice-i18n-fr koffice-i18n-ga -koffice-i18n-he koffice-i18n-hi koffice-i18n-hu koffice-i18n-it koffice-i18n-ja -koffice-i18n-lt koffice-i18n-mk koffice-i18n-ms koffice-i18n-nb koffice-i18n-nl -koffice-i18n-nn koffice-i18n-pl koffice-i18n-pt koffice-i18n-ptbr -koffice-i18n-ro koffice-i18n-ru koffice-i18n-se koffice-i18n-sk koffice-i18n-sl -koffice-i18n-sr koffice-i18n-srlatin koffice-i18n-sv koffice-i18n-ta -koffice-i18n-tg koffice-i18n-tr koffice-i18n-uk koffice-i18n-uz -koffice-i18n-zhcn koffice-i18n-zhtw - -# KDE Extra -kde-extras diff --git a/src/lists/kde-full b/src/lists/kde-full deleted file mode 100644 index ec74bec..0000000 --- a/src/lists/kde-full +++ /dev/null @@ -1,17 +0,0 @@ -# /usr/share/make-live/lists/kde-full - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# KDE -kde kdm -desktop-base - -x-window-system-core -xresprobe - -# KDE Full -koffice diff --git a/src/lists/kde-full-i18n b/src/lists/kde-full-i18n deleted file mode 100644 index d40cd74..0000000 --- a/src/lists/kde-full-i18n +++ /dev/null @@ -1,49 +0,0 @@ -# /usr/share/make-live/lists/kde-full-i18n - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# Standard i18n -manpages manpages-dev manpages-de manpages-de-dev manpages-es manpages-es-extra -manpages-fi manpages-fr manpages-fr-dev manpages-fr-extra 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 - -# KDE -kde kdm -desktop-base - -x-window-system-core -xresprobe - -# KDE i18n -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 kde-i18n-zhtw - -# KDE Full -koffice - -# KDE Full i18n -koffice-i18n-af koffice-i18n-ar koffice-i18n-bg koffice-i18n-br koffice-i18n-bs -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-eu koffice-i18n-fi koffice-i18n-fr koffice-i18n-ga -koffice-i18n-he koffice-i18n-hi koffice-i18n-hu koffice-i18n-it koffice-i18n-ja -koffice-i18n-lt koffice-i18n-mk koffice-i18n-ms koffice-i18n-nb koffice-i18n-nl -koffice-i18n-nn koffice-i18n-pl koffice-i18n-pt koffice-i18n-ptbr -koffice-i18n-ro koffice-i18n-ru koffice-i18n-se koffice-i18n-sk koffice-i18n-sl -koffice-i18n-sr koffice-i18n-srlatin koffice-i18n-sv koffice-i18n-ta -koffice-i18n-tg koffice-i18n-tr koffice-i18n-uk koffice-i18n-uz -koffice-i18n-zhcn koffice-i18n-zhtw diff --git a/src/lists/kde-i18n b/src/lists/kde-i18n deleted file mode 100644 index 55469a5..0000000 --- a/src/lists/kde-i18n +++ /dev/null @@ -1,33 +0,0 @@ -# /usr/share/make-live/lists/kde-i18n - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# Standard i18n -manpages manpages-dev manpages-de manpages-de-dev manpages-es manpages-es-extra -manpages-fi manpages-fr manpages-fr-dev manpages-fr-extra 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 - -# KDE -kde kdm -desktop-base - -x-window-system-core -xresprobe - -# KDE i18n -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 kde-i18n-zhtw diff --git a/src/lists/kde-junior b/src/lists/kde-junior deleted file mode 100644 index 53cdf2a..0000000 --- a/src/lists/kde-junior +++ /dev/null @@ -1,20 +0,0 @@ -# /usr/share/make-live/lists/kde - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# KDE -kde kdm -desktop-base - -x-window-system-core -xresprobe - -# Debian Junior -junior-sound junior-typing junior-internet junior-toys junior-games-net -junior-games-sim junior-games-gl junior-puzzle junior-arcade junior-math -junior-writing junior-games-card junior-programming junior-system junior-art -junior-doc junior-games-text junior-kde diff --git a/src/lists/knoppix b/src/lists/knoppix deleted file mode 100644 index e981fd7..0000000 --- a/src/lists/knoppix +++ /dev/null @@ -1,1292 +0,0 @@ -# /usr/share/make-live/lists/gnome - package list for make-live(1) -# - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# X11 -desktop-base xresprobe - -# Knoppix packages -# URL: http://ftp.kernel.org/pub/dist/knoppix/packages.txt -0wn -aalib-bin -aalib1 -ace-of-penguins -acpi -adduser -adtool -aespipe -afio -airsnort -alevt -alien -alsa-base -alsa-utils -amanda-client -amanda-common -amanda-server -anacron -apache2 -apache2-mpm-prefork -apache2-utils -apache2.2-common -apmd -apt -apt-file -apt-method-installed -apt-show-versions -apt-utils -arj -ark -arpwatch -artwiz-cursor -at -atitvout -atmel-firmware -attr -audacity -aufs-cvs-modules-2.6.19 -aufs-cvs-utils -aumix-gtk -autoconf -autofs -autotools-dev -autotrace -avm-firmware -base-files -base-passwd -bash -bb -bc -beryl -beryl-core -beryl-manager -beryl-plugins -beryl-plugins-data -beryl-settings -biew -bin86 -bind9 -bind9-host -binfmt-support -bing -binutils -binutils-dev -bittorrent -blt -bluetooth -bluez-firmware -bluez-utils -bochsbios -bonnie++ -bridge-utils -brltty -bsdiff -bsdmainutils -bsdutils -buffer -build-essential -busybox -bzip2 -ca-certificates -cabextract -capiutils -cdbackup -cdbs -cdda2wav -cddb -cdparanoia -cdrdao -cdrecord -checkmem -chkrootkit -clamav -clamav-base -clamav-freshclam -cloop-module-2.6.19 -hi -configure-xawtv -console-common -console-data -console-tools -convertfs -coreutils -cowsay -cpio -cpp -cpp-4.1 -cpuburn -cramfsprogs -cron -cryptcat -cryptsetup -cups-pdf -cupsys -cupsys-bsd -cupsys-client -cupsys-common -cupsys-driver-gutenprint -cvs -dante-client -dash -dbus -dc -dcraw -dctrl-tools -dd-rescue -dds2tar -debconf -debconf-i18n -debconf-utils -debfoster -debhelper -debian-archive-keyring -debianutils -debootstrap -deborphan -debsums -defoma -devscripts -dh-make -dhcp3-common -dhcp3-server -dialog -dict -dictionaries-common -dietlibc-dev -diff -diffstat -ding -distcc -dmidecode -dmraid -dmsetup -dnsutils -doc-base -docbook-xml -dosfstools -dpkg -dpkg-dev -dpkg-repack -drdsl -dselect -dsniff -dump -dupload -dvb-mpegtools -dvb-utils -dvbackup -dvbsnoop -dvbstream -dvbtune -dvd+rw-tools -dvdauthor -dvdbackup -dvgrab -e00compr -e2fslibs -e2fsprogs -ed -efax -eject -elinks -emerald -enscript -escputil -esound-common -etherwake -ethtool -ettercap-common -ettercap-gtk -euro-support -euro-support-console -expect -ext2resize -fakeroot -fb-music-low -fbi -fbset -fdflush -fdisk-udeb -fdutils -fetchmail -ffmpeg -file -fileutils -findutils -finger -firefox -fluxbox -fontconfig -fontconfig-config -foomatic-bin -foomatic-db -foomatic-db-engine -foomatic-db-gutenprint -foomatic-db-hpijs -foomatic-filters -foremost -fortune-mod -fortunes-debian-hints -fortunes-min -fping -freeglut3 -freemind -freenx -frozen-bubble -hi -ftp -ftpd -fttools -fuse-utils -g++ -g++-4.1 -gaim -gaim-data -gaim-encryption -gawk -gcc -gcc-3.3-base -gcc-4.1 -gcc-4.1-base -gconf2 -gconf2-common -gdb -genisoimage -genliloconf -gettext -gettext-base -gif2png -giflib-bin -giflib3g -giftrans -gimp -gimp-data -gimp-print -gksu -gnome-keyring -gnuchess -gnupg -gnupg2 -gocr -gpart -gparted -gpgsm -gpgv -gphoto2 -gpm -gpsdrive -gpstrans -gq -gqcam -grep -groff -groff-base -hi -grub-disk -gs-common -gs-esp -gscanbus -gsfonts -gsfonts-x11 -gsm-utils -gtans -gtk-smooth-themes -gtk2-engines -gtk2-engines-smooth -gtkam -gv -gzip -hal -hdparm -hexedit -hfsplus -hfsutils -hicolor-icon-theme -hostap-utils -hostapd -hostname -hpijs -hping2 -html2text -httptunnel -hunt -hwsetup -hwtools -i810switch -ibod -icedax -icedove -icedove-locale-de -iceweasel -iceweasel-l10n-de -icewm -icewm-common -icmpush -idswakeup -iftop -ifupdown -ijsgutenprint -imagemagick -imaze -imlib-base -imlib11 -info -infobash -ingerman -initramfs-tools -initrd-tools -initscripts -intltool-debian -ipcalc -ipchains -iperf -ipppd -iproute -ipsec-tools -iptables -iptraf -iputils-ping -iputils-tracepath -ipv6calc -ipw2100-nonfree -ipw2200-nonfree -ipx -irda-common -irda-tools -irssi -irssi-plugin-icq -irssi-scripts -isapnptools -isdnactivecards -isdnutils-base -isdnvboxclient -isomaster -ispell -java-common -jfsutils -joe -k3b -k3b-defaults -k3b-i18n -kaffeine -kalarm -kamera -kandy -kappfinder -kate -katomic -kbackup -kbackup-multibuf -kbattleship -kbdconfig -kcalc -kcharselect -kcontrol -kde-i18n-de -kde-i18n-es -kde-i18n-fr -kde-i18n-it -kde-i18n-ja -kde-i18n-nl -kde-i18n-pl -kde-i18n-tr -kdeaddons-kfile-plugins -kdeadmin-kfile-plugins -kdebase -kdebase-bin -kdebase-data -kdebase-kio-plugins -kdebluetooth -kdegraphics-kfile-plugin -kdelibs-data -kdelibs4c2a -kdemultimedia-kfile-plug -kdemultimedia-kio-plugin -kdenetwork-kfile-plugins -kdepasswd -kdepim-kfile-plugins -kdepim-kio-plugins -kdeprint -kdesktop -kdessh -kdf -kdm -kexec-tools -kfax -kfind -kfloppy -kget -kghostview -khelpcenter -khexedit -kicker -kiconedit -kismet -klaptopdaemon -klibc-utils -klipper -klogd -kmahjongg -kmail -kmailcvt -kmenuedit -kmix -knode -knotes -konq-plugins -konqueror -konqueror-nsplugins -konsole -konsolekalendar -kooka -kpackage -kpager -kpdf -kpersonalizer -kpf -kphone -kppp -krdc -kreversi -krfb -ksmserver -ksnapshot -ksokoban -ksplash -ksudoku -ksync -ksysguard -ksysguardd -ksysv -kteatime -ktimer -ktip -ktnef -ktuberling -kuickshow -kuser -kview -kviewshell -kwin -kwlan -laptop-detect -ldap-utils -lde -less -lesstif2 -lftp -lha -liba52-0.7.4 -libaa1 -libacl1 -libadns1 -libao2 -libapache2-mod-php4 -libapm1 -libapr1 -libaprutil1 -libapt-pkg-perl -libart-2.0-2 -libarts1c2a -libartsc0 -libasound2 -libaspell15 -libatk1.0-0 -libatm1 -libattr1 -libaudio2 -libaudiofile0 -libautotrace3 -libavahi-client3 -libavahi-common-data -libavahi-common3 -libavahi-compat-howl0 -libavahi-compat-libdnssd -libavahi-qt3-1 -libavc1394-0 -libavcodec0d -libavformat0d -libbeecrypt6 -libberylsettings0 -libbind9-0 -libblkid1 -libbluetooth2 -libbz2-1.0 -libc6 -libc6-dev -libcaca0 -libcairo2 -libcap1 -libcapi20-3 -libcapi20-dev -libcdio6 -libcdk5 -libcdparanoia0 -libclamav1 -libcomerr2 -libconfhelper-perl -libconfig-file-perl -libconsole -libcroco3 -libcucul0 -libcupsimage2 -libcupsys2 -libcurl3 -libcurl3-gnutls -libdate-manip-perl -libdb1-compat -libdb4.2 -libdb4.3 -libdb4.4 -libdbd-mysql-perl -libdbi-perl -libdbus-1-3 -libdbus-glib-1-2 -libdbus-qt-1-1c2 -libdc1394-13 -libdevmapper1.02 -libdirectfb-0.9-25 -libdm0 -libdns21 -libdrm2 -libdv-bin -libdv4 -libdvdread3 -libedit2 -libelfg0 -libemeraldengine0 -libenchant1c2a -libesd-alsa0 -libevent1 -libexif-gtk5 -libexif12 -libexpat1 -libfam0 -libflac++5 -libflac7 -libfontconfig1 -libfontenc1 -libfreetype6 -libfribidi0 -libfs6 -libft-perl -libfuse2 -libgcc1 -libgconf2-4 -libgcrypt11 -libgd2-xpm -libgdbm3 -libgdchart-gd2-noxpm -libgeoip1 -libgimp2.0 -libgksu2-0 -libgl1-mesa-dri -libgl1-mesa-glx -libglade2-0 -libglib1.2 -libglib2.0-0 -libglib2.0-data -libglibmm-2.4-1c2a -libglu1-mesa -libgmp3c2 -libgnome-keyring0 -libgnutls13 -libgpg-error0 -libgpgme11 -libgphoto2-2 -libgphoto2-port0 -libgpmg1 -libgsf-1-114 -libgsf-1-common -libgsm1 -libgsmme1c2a -libgssapi2 -libgstreamer0.10-0 -libgtk1.2 -libgtk1.2-common -libgtk2.0-0 -libgtk2.0-bin -libgtk2.0-common -libgtkmm-2.4-1c2a -libgtkspell0 -libgtop2-7 -libgtop2-common -libgutenprint2 -libgutenprintui2-1 -libhal-storage1 -libhal1 -libhfsp0 -libhtml-parser-perl -libhtml-tagset-perl -libhtml-tree-perl -libice6 -libid3tag0 -libident -libidl0 -libidn11 -libieee1284-3 -libijs-0.35 -libisc11 -libisccc0 -libisccfg1 -libiso9660-4 -libiw28 -libjack0.100.0-0 -libjasper-1.701-1 -libjcode-pm-perl -libjpeg-progs -libjpeg62 -libjpeg62-dev -libk3b2 -libkcal2b -libkcddb1 -libkdegames1 -libkdepim1a -libkleopatra1 -libklibc -libkmime2 -libkonq4 -libkpimidentities1 -libkrb53 -libksba8 -libkscan1 -libksieve0 -libktnef1 -liblcms1 -libldap-2.3-0 -libldap2 -liblircclient0 -liblocale-gettext-perl -liblockdev1 -liblockfile1 -liblogfile-rotate-perl -libltdl3 -liblua50 -liblualib50 -liblwres9 -liblzo1 -libmad0 -libmagic1 -libmagick++9c2a -libmagick9 -libmikmod2 -libmimelib1c2a -libmng1 -libmodplug0c2 -libmpcdec3 -libmusicbrainz4c2a -libmyspell3c2 -libmysqlclient15off -libnasl2 -libncp -libncurses5 -libncurses5-dev -libncursesw5 -libneon25 -libnessus2 -libnet-daemon-perl -libnet0 -libnet1 -libnetpbm10 -libnewt-utf8-0 -libnewt0.52 -libnfsidmap2 -libnids1.20 -libnspr4 -libnspr4-0d -libnss3-0d -libntfs9 -libogg0 -liboggflac3 -libopencdk8 -libopenexr2c2a -libopenobex1 -liborbit2 -libpam-modules -libpam-ncp -libpam-runtime -libpam0g -libpango1.0-0 -libpango1.0-common -libpaper-utils -libpaper1 -libparted1.6-0 -libparted1.7-1 -libpcap0.7 -libpcap0.8 -libpcd2 -libpci2 -libpcre3 -libperl5.8 -libpisock9 -libplot2c2 -libplrpc-perl -libpng12-0 -libpoppler0c2 -libpoppler0c2-qt -libpopt0 -libportaudio0 -libpostproc0d -libpq4 -libpstoedit0c2a -libpth20 -libqt3-mt -libquicktime0 -libraw1394-8 -libreadline4 -libreadline5 -librecode0 -librpcsecgss3 -librpm4 -librsvg2-2 -libsamplerate0 -libsane -libsane-extras -libsasl2 -libsasl2-2 -libsasl2-modules -libscrollkeeper0 -libsdl-console -libsdl-gfx1.2-4 -libsdl-image1.2 -libsdl-mixer1.2 -libsdl-net1.2 -libsdl-pango1 -libsdl-perl -libsdl-ttf2.0-0 -libsdl1.2debian -libsdl1.2debian-alsa -libselinux1 -libsensors3 -libsepol1 -libsexy2 -libsigc++-2.0-0c2a -libslang2 -libslp1 -libsm6 -libsmbclient -libsmpeg0 -libsndfile1 -libsnmp-base -libsnmp9 -libspeex1 -libsqlite3-0 -libss2 -libssl0.9.7 -libssl0.9.8 -libssp0 -libstartup-notification0 -libstdc++2.10-glibc2.2 -libstdc++5 -libstdc++6 -libstdc++6-4.1-dev -libsvga1 -libsysfs2 -libt1-5 -libtag1c2a -libtasn1-3 -libtext-charwidth-perl -libtext-iconv-perl -libtext-wrapi18n-perl -libtheora0 -libtiff-tools -libtiff4 -libttf2 -libungif4g -libuniconf4.2 -liburi-perl -libusb-0.1-4 -libuuid1 -libvcdinfo0 -libvolume-id0 -libvorbis0a -libvorbisenc2 -libvorbisfile3 -libvte-common -libvte4 -libweakref-perl -libwmf0.2-7 -libwnck-common -libwnck18 -libwrap0 -libwvstreams4.2-base -libwvstreams4.2-extras -libwww-perl -libwxgtk2.4-1 -libx11-6 -libx11-data -libxau6 -libxaw7 -libxcomp1 -libxcompext1 -libxcomposite1 -libxcursor1 -libxdamage1 -libxdelta2 -libxdmcp6 -libxext6 -libxfixes3 -libxfont1 -libxft2 -libxi6 -libxine1 -libxinerama1 -libxkbfile1 -libxml2 -libxmu6 -libxmuu1 -libxp6 -libxplc0.3.13 -libxpm4 -libxrandr2 -libxrender1 -libxres1 -libxslt1.1 -libxss1 -libxt6 -libxtrap6 -libxtst6 -libxv1 -libxvmc1 -libxxf86dga1 -libxxf86misc1 -libxxf86vm1 -libzvbi-common -libzvbi0 -libzzip-0-12 -lilo -linux-image-2.6.19 -linux-kernel-headers -linux-sound-base -lisa -loadlin -locales -lockfile-progs -login -logrotate -loop-aes-modules-2.6.19 -loop-aes-utils -lrzsz -lsb-base -lsof -ltrace -lvm-common -lvm2 -lynx -lzop -m4 -macutils -madwifi-modules-2.6.19 -madwifi-tools -mailx -make -makedev -man-db -manpages -manpages-de -manpages-dev -mawk -mbr -mc -mdadm -memtester -menu -menu-xdg -mesa-utils -mikmod -mime-support -minicom -mkbootdev -mkisofs -hi -mktemp -mobilemesh -modconf -module-init-tools -modutils -mount -mouseconfig -mpack -mpg321 -mplayer -mplayer-skin-blue -ms-sys -mt-st -mtools -mtr-tiny -mutt -myspell-en-us -mysql-client -mysql-client-5.0 -mysql-common -nano -nasm -ncpfs -ncurses-base -ncurses-bin -ndiswrapper-modules-2.6. -ndiswrapper-utils -nedit -nessus -nessus-plugins -nessusd -net-tools -netbase -netcat -netcat6 -netpbm -netpipe-tcp -networkstatus -nfs-common -nfs-kernel-server -ngrep -nmap -ntfs-3g -ntpdate -nvtv -nxagent -nxclient -nxdesktop -nxlibs -nxproxy -nxssh -nxtunnel-client -nxtunnel-server -odbcinst1debian1 -openbsd-inetd -openhackware -openoffice-de-en -openoffice.org-debian-me -openssh-client -openssh-server -openssl -openvpn -outguess -p0f -parted-bf -partimage -partimage-server -passwd -patch -pciutils -pciutils-dev -pcmcia-cs -pcmciautils -perl -perl-base -perl-modules -perl-suid -pgpgpg -php4-common -php4-mysql -pia -pkg-config -playmidi -pmount -pnm2ppa -po-debconf -portmap -poster -powermgmt-base -ppmd -ppp -hi -pppdcapiplugin -pppoe -pppoeconf -pppstatus -pptp-linux -print-utils-pfeifle -prism54-nonfree -procinfo -procmail -procps -proll -psfontmgr -psmisc -psutils -pump -python -python-central -python-imaging -python-imaging-tk -python-minimal -python-support -python-tk -python2.4 -python2.4-minimal -qemu -qobex -qps -qtparted -radio -rcs -rdate -rdesktop -readline-common -recode -recover -reiserfsprogs -reportbug -rpm -rsync -rt2x00-cvs-modules-2.6.1 -rxvt-beta -s3switch -samba -samba-common -sane -sane-utils -sash -scanmodem -scantv -scli -screen -scribus -scrollkeeper -sed -sendfile -sendip -setserial -sgml-base -sgml-data -shaper -sharutils -sitar -slang1 -slang1a-utf8 -sleuthkit -smail -smartmontools -smbclient -smbconf-pfeifle -smbconf-pfeifle-nonfree -smbfs -sniffit -sound-recorder -sox -speedtouch -speex -squid -squid-common -squidclient -ssh -ssl-cert -sslwrap -star -statserial -strace -stress -stunnel -sudo -sun-java5-bin -sun-java5-demo -sun-java5-jdk -sun-java5-jre -sun-java5-plugin -sweep -symlinks -synaptic -sysklogd -syslinux -sysv-rc -sysvinit -sysvinit-utils -tar -tcl8.4 -tcpd -tcpdump -telnet-ssl -telnetd-ssl -testdisk -tftp -tftpd-hpa -thttpd -thunderbird -thunderbird-locale-de -tiger -tightvncserver -tk8.4 -tnef -tofrodos -tpconfig -traceroute -trans-de-en -transfig -tshark -tsocks -ttf-bitstream-vera -ttf-f500 -ttf-freefont -ttf-isabella -ttf-openoffice -ttf-opensymbol -ttf-staypuft -ttf-summersby -ttmkfdir -twm -txt2regex -type-handling -type1inst -tzdata -ucf -udev -udpcast -uml-utilities -umlrun-uml -unifont -units -unixodbc -unp -unzip -unzoo -update -update-inetd -urlview -usbutils -usbview -user-de -util-linux -util-linux-locales -uudeview -v4l-conf -vcdimager -vcdtools -vgabios -vim -vim-common -vim-gtk -vim-gui-common -vim-runtime -vim-scripts -vimpart -vlan -vnc-common -vorbis-tools -vpnc -vrms -wakeonlan -wavemon -wavtools -wget -whiptail -whois -wine -winetools -wipe -wireless-tools -wireshark -wireshark-common -wodim -wpasupplicant -wprint -wvdial -x-ttcidfont-conf -x11-common -xaos -xaw3dg -xawtv -xawtv-plugins -xbase-clients -xbattle -xbitmaps -xboard -xchat -xchat-common -xdelta -xdialog -xdm -xfonts-100dpi -xfonts-100dpi-transcoded -xfonts-75dpi -xfonts-75dpi-transcoded -xfonts-base -xfonts-bolkhov-cp1251-75 -xfonts-bolkhov-cp1251-mi -xfonts-dosemu -xfonts-encodings -xfonts-scalable -xfonts-terminus -xfonts-utils -xfsdump -xfsprogs -xgalaga -xkb-data -xkbset -xlibmesa-gl -xlibs -xloadimage -xml-core -xmms -xmms-cdread -xmms-goom -xmms-modplug -xmms-volnorm -xnest -xorg -xosview -xpdf -xpdf-common -xpdf-reader -xpdf-utils -xsane -xsane-common -xserver-xorg -xserver-xorg-core -xserver-xorg-input-evdev -xserver-xorg-input-kbd -xserver-xorg-input-mouse -xserver-xorg-input-synap -xserver-xorg-video-all -xserver-xorg-video-apm -xserver-xorg-video-ark -xserver-xorg-video-ati -xserver-xorg-video-chips -xserver-xorg-video-cirru -xserver-xorg-video-cyrix -xserver-xorg-video-dummy -xserver-xorg-video-fbdev -xserver-xorg-video-glint -xserver-xorg-video-i128 -xserver-xorg-video-i740 -xserver-xorg-video-i810 -xserver-xorg-video-imstt -xserver-xorg-video-mga -xserver-xorg-video-neoma -xserver-xorg-video-newpo -xserver-xorg-video-nsc -xserver-xorg-video-nv -xserver-xorg-video-rendi -xserver-xorg-video-s3 -xserver-xorg-video-s3vir -xserver-xorg-video-savag -xserver-xorg-video-silic -xserver-xorg-video-sis -xserver-xorg-video-sisus -xserver-xorg-video-tdfx -xserver-xorg-video-tga -xserver-xorg-video-tride -xserver-xorg-video-tseng -xserver-xorg-video-v4l -xserver-xorg-video-vesa -xserver-xorg-video-vga -xserver-xorg-video-via -xserver-xorg-video-vmwar -xserver-xorg-video-voodo -xskat -xterm -xtightvncviewer -xtv -xutils -xutils-dev -xviddetect -xzoom -zile -zip -zlib1g -zlib1g-dev diff --git a/src/lists/knoppix-dvd b/src/lists/knoppix-dvd deleted file mode 100644 index c6ab94e..0000000 --- a/src/lists/knoppix-dvd +++ /dev/null @@ -1,3417 +0,0 @@ -# /usr/share/make-live/lists/gnome - package list for make-live(1) -# - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# X11 -desktop-base xresprobe - -# Knoppix packages -# URL: http://ftp.kernel.org/pub/dist/knoppix-dvd/packages-dvd.txt -0wn -3270-common -a2ps -aalib-bin -aalib1 -abiword-common -abiword-gnome -abiword-help -ace-of-penguins -acpi -adduser -adtool -aespipe -afio -airsnort -akregator -alevt -alien -alsa-base -alsa-utils -amanda-client -amanda-common -amanda-server -amarok -amarok-engines -amarok-xine -amor -anacron -ant -ant-optional -antlr -apache -apache-common -apache-dev -apache-doc -apache-utils -apache2 -apache2-doc -apache2-mpm-prefork -apache2-utils -apache2.2-common -apcalc -apcalc-common -apel -apmd -apt -apt-doc -apt-file -apt-listchanges -apt-method-installed -apt-show-versions -apt-utils -aptitude -aribas -arj -ark -arpwatch -arts -artsbuilder -artwiz-cursor -asclock -asclock-themes -aspell -aspell-de -aspell-doc -aspell-en -aspell-es -aspell-fr -aspell-it -aspell-pl -at -at-spi -atitvout -atlantik -atlantikdesigner -atlas2-base -atlas3-base -atlas3-base-dev -atlas3-headers -atmel-firmware -attr -auctex -audacious -audacious-plugins -audacious-plugins-extra -audacity -aufs-cvs-modules-2.6.19 -aufs-cvs-utils -aumix-gtk -autoclass -autoconf -autofs -automake1.4 -automake1.7 -automake1.9 -autotools-dev -autotrace -avce00 -avm-firmware -axiom -axiom-databases -axkit -axkit-examples -axkit-language-htmldoc -axkit-language-query -axyftp-doc -axyftp-gtk -bacula -bacula-client -bacula-common -bacula-console -bacula-director-common -bacula-director-mysql -bacula-doc -bacula-fd -bacula-sd -bacula-sd-sqlite3 -bacula-server -base-files -base-passwd -bash -basket -bb -bc -beneath-a-steel-sky -beryl -beryl-core -beryl-manager -beryl-plugins -beryl-plugins-data -beryl-settings -biew -bin86 -bind9 -bind9-host -binfmt-support -bing -binutils -binutils-dev -bison -bitmap-mule -bittorrent -blas -blender -blinken -blt -bluefish -bluez-firmware -bluez-utils -bochs -bochs-doc -bochs-sdl -bochs-term -bochs-wx -bochs-x -bochsbios -bonnie++ -bridge-utils -brltty -bsdiff -bsdmainutils -bsdutils -buffer -bug-buddy -build-essential -busybox -bximage -bzflag -bzflag-server -bzip2 -ca-certificates -cabextract -capisuite -capiutils -capplets-data -cdbackup -cdbs -cdd-common -cdda2wav -cddb -cdparanoia -cdrdao -cdrecord -cdrtools-doc -cdrw-taper -cernlib-base -cervisia -cfortran -cgoban -checkmem -chipcard-tools -chkrootkit -chktex -chromium -chromium-data -cjk-latex -cl-asdf -cl-cil -cl-reversi -cl-utilities -clamav -clamav-base -clamav-docs -clamav-freshclam -clara -cli-common -cli-common-dev -cloop-module-2.6.19 -cloop-utils -cmt -colorgcc -comerr-dev -common-lisp-controller -compiz -compiz-core -compiz-gnome -compiz-gtk -compiz-plugins -configure-xawtv -console-common -console-data -console-tools -convertfs -coreutils -cowsay -cpio -cpp -cpp-3.3 -cpp-3.4 -cpp-4.0 -cpp-4.0-doc -cpp-4.1 -cpp-4.1-doc -cpp-doc -cpuburn -crack-attack -cramfsprogs -cron -crossfire-client -crossfire-client-gtk -crossfire-client-gtk2 -crossfire-client-images -crossfire-client-sounds -crossfire-client-x11 -crossfire-common -crossfire-doc -crossfire-edit -crossfire-maps -crossfire-server -cryptcat -cryptsetup -crystalspace -crystalspace-dev -crystalspace-doc -csh -csound -csound-doc -cups-pdf -cupsys -cupsys-bsd -cupsys-client -cupsys-common -cupsys-driver-gutenprint -cvs -cycle -d4x -d4x-common -dante-client -dash -dasher -dasher-data -db4.2-util -db4.3-util -dbconfig-common -dbishell -dbus -dc -dcraw -dctrl-tools -dd-rescue -ddd -dds2tar -debconf -debconf-i18n -debconf-utils -debfoster -debhelper -debian-archive-keyring -debian-keyring -debiandoc-sgml -debianutils -debootstrap -deborphan -debsums -defoma -defrag -desktop-base -desktop-file-utils -devscripts -dh-make -dhcp3-common -dhcp3-server -dia -dia-common -dia-gnome -dia-libs -dialog -dict -dictionaries-common -dietlibc-dev -diff -diffstat -digikam -digikamimageplugins -dillo -ding -dirmngr -discover1 -discover1-data -distcc -dlint -dlocate -dmidecode -dmraid -dmsetup -dnsutils -doc-base -doc-linux-html -docbook -docbook-dsssl -docbook-xml -docbook-xsl -dosfstools -dpatch -dpkg -dpkg-dev -dpkg-repack -drdsl -dselect -dsh -dsniff -dump -dupload -dvb-mpegtools -dvb-utils -dvbackup -dvbsnoop -dvbstream -dvbtune -dvd+rw-tools -dvdauthor -dvdbackup -dvdrecord -dvgrab -dvipng -e00compr -e2fslibs -e2fslibs-dev -e2fsprogs -ec-fonts-mftraced -ecj-bootstrap -eclipse -eclipse-jdt -eclipse-pde -eclipse-platform -eclipse-rcp -eclipse-source -ed -edict -efax -efax-gtk -effectv -efibootmgr -eject -ekiga -elinks -emacs-intl-fonts -emacs21 -emacs21-bin-common -emacs21-common -emacsen-common -emerald -emerald-themes -enigma -enigma-data -enlightenment -enlightenment-data -enscript -eog -epiphany-browser -erlang -erlang-base -erlang-dev -erlang-examples -erlang-mode -erlang-nox -erlang-src -erlang-x11 -escputil -esound -esound-common -ess -eterm -etherwake -ethtool -ettercap-common -ettercap-gtk -euler -euro-support -euro-support-console -euro-support-x -evilwm -evince -evolution -evolution-common -evolution-data-server -evolution-data-server-co -evolution-exchange -evolver -expect -ext2resize -eyesapplet -f2c -fakeroot -falconseye -falconseye-data -fast-user-switch-applet -fastjar -fb-music-low -fbi -fbset -fdflush -fdisk-udeb -fdutils -fenris -festival -festlex-cmu -festlex-poslex -festvox-kallpc16k -festvox-kdlpc16k -fetchmail -ffmpeg -fftw-dev -fftw2 -fftw3 -fftw3-dev -fifteenapplet -file -file-roller -fileutils -findutils -finger -firefox -firefox-dom-inspector -flex -flobopuyo -fluxbox -fnlib-data -fontconfig -fontconfig-config -fontforge -fontforge-doc -fonty -foomatic-bin -foomatic-db -foomatic-db-engine -foomatic-db-gimp-print -foomatic-db-gutenprint -foomatic-db-hpijs -foomatic-filters -foremost -fortune-mod -fortunes-debian-hints -fortunes-min -fp-compiler -fp-docs -fp-ide -fp-units-base -fp-units-db -fp-units-fcl -fp-units-fv -fp-units-gfx -fp-units-gnome1 -fp-units-gtk -fp-units-gtk2 -fp-units-misc -fp-units-net -fp-units-rtl -fp-utils -fpc-crosswin32 -fpc-src -fping -freeciv-client-gtk -freeciv-data -freeciv-server -freefem -freefem-doc -freefem-examples -freefem3d -freeglut3 -freemind -freenx -freepats -freepops -freeradius -frozen-bubble -hi -ftape-util -ftp -ftpd -fttools -fuse-utils -g++ -g++-3.3 -g++-4.0 -g++-4.1 -g-wrap -g77 -g77-3.3 -g77-3.3-doc -g77-3.4 -gaim -gaim-data -gaim-encryption -gambas-gb-qt -gambas-runtime -gambit -gambit-doc -gamin -gap -gap-character-tables -gap-core -gap-dev -gap-doc -gap-libs -gap-online-help -gap-prim-groups -gap-small-groups -gap-small-groups-extra -gap-table-of-marks -gap-trans-groups -gawk -gbib -gcalctool -gcc -gcc-3.3 -gcc-3.3-base -gcc-3.4 -gcc-3.4-base -gcc-4.0 -gcc-4.0-base -gcc-4.0-doc -gcc-4.1 -gcc-4.1-base -gcc-4.1-doc -gcc-doc -gcc-doc-base -gcj -gcj-3.3 -gcj-4.0-base -gcj-4.1 -gcj-4.1-base -gcom -gcompris -gcompris-data -gcompris-sound-da -gcompris-sound-de -gcompris-sound-en -gcompris-sound-es -gcompris-sound-fr -gcompris-sound-it -gcompris-sound-pt -gcompris-sound-ru -gconf -gconf-editor -gconf2 -gconf2-common -gdal-bin -gdb -gdk-imlib1 -gdk-imlib11 -gdm -gdm-themes -geant321-doc -geas -geas-doc -geda -geda-doc -geda-examples -geda-gattrib -geda-gnetlist -geda-gschem -geda-gsymcheck -geda-symbols -geda-utils -gedit -gedit-common -geg -genisoimage -genliloconf -geomview -gerbv -gettext -gettext-base -gettext-el -gfortran -gfortran-4.1 -gftp -gftp-common -gftp-gtk -gftp-text -ghemical -gif2png -giflib-bin -giflib3g -giftrans -gij -gij-4.0 -gij-4.1 -gimp -gimp-data -gimp-print -ginac-tools -git-core -gjdoc -gkrellm -gkrellmd -gksu -glibc-doc -glpk -gmessage -gmsh -gmt -gmt-coast-low -gmt-doc -gmt-examples -gmt-tutorial -gmt-tutorial-pdf -gnokii -gnome -gnome-about -gnome-accessibility-them -gnome-applets -gnome-applets-data -gnome-backgrounds -gnome-bin -gnome-cards-data -gnome-control-center -gnome-core -gnome-cups-manager -gnome-desktop-data -gnome-desktop-environmen -gnome-doc-tools -gnome-doc-utils -gnome-games -gnome-games-data -gnome-games-extra-data -gnome-gv -gnome-icon-theme -gnome-keyring -gnome-keyring-manager -gnome-libs-data -gnome-mag -gnome-media -gnome-media-common -gnome-menus -gnome-mime-data -gnome-netstatus-applet -gnome-nettool -gnome-office -gnome-panel -gnome-panel-data -gnome-session -gnome-system-monitor -gnome-system-tools -gnome-terminal -gnome-terminal-data -gnome-themes -gnome-themes-extras -gnome-user-guide -gnome-utils -gnome-volume-manager -gnome2-user-guide -gnopernicus -gnubg -gnubg-data -gnucash -gnucash-common -gnucash-docs -gnuchess -gnuchess-book -gnue-appserver -gnue-common -gnue-designer -gnue-forms -gnue-navigator -gnue-reports -gnugo -gnuhtml2latex -gnumeric -gnumeric-common -gnumeric-doc -gnumeric-plugins-extra -gnupg -gnupg-agent -gnupg2 -gnuplot -gnuplot-doc -gnuplot-nox -gnuplot-x11 -gnustep-base-common -gnustep-common -gnustep-make -gnutls-bin -gocr -gok -gok-doc -gpart -gparted -gpc -gpc-2.1-3.4 -gpc-2.1-3.4-doc -gpdf -gperiodic -gpgsm -gpgv -gphoto2 -gpm -gpp -gprolog -gprolog-doc -gpsdrive -gpstrans -gq -gqcam -gqview -grace -gramofile -graphviz -graphviz-doc -grass -grass-doc -grep -grep-dctrl -gri -gri-el -gri-html-doc -grip -groff -groff-base -hi -grub-disk -gs-common -gs-esp -gs-gpl -gscanbus -gsfonts -gsfonts-x11 -gsl-bin -gsl-doc-pdf -gsl-ref-html -gsl-ref-psdoc -gsm-utils -gstreamer0.10-alsa -gstreamer0.10-gnomevfs -gstreamer0.10-gnonlin -gstreamer0.10-plugins-ba -gstreamer0.10-plugins-go -gstreamer0.10-plugins-ug -gstreamer0.8-plugin-apps -gstreamer0.8-tools -gtans -gthumb -gtk-engines-qtpixmap -gtk-smooth-themes -gtk2-engines -gtk2-engines-pixbuf -gtk2-engines-spherecryst -gtk2-engines-xfce -gtkam -gtkglarea5 -gtkhtml3.2 -gtkhtml3.6 -gtkhtml3.8 -gucharmap -guile-1.6 -guile-1.6-dev -guile-1.6-libs -guile-1.6-slib -guile-g-wrap -guile-library -gutenprint-doc -gutenprint-locales -gv -gwenview -gzip -hal -hal-device-manager -hdparm -helix-player -hermes1 -hevea -hexedit -hfsplus -hfsutils -hicolor-icon-theme -hostap-utils -hostapd -hostname -hotplug-utils -hpijs -hping2 -hspell -htdig -html2text -htmldoc -htmldoc-common -httptunnel -hunt -hwinfo -hwsetup -hwtools -i810switch -iamerican -iasl -ibod -ibritish -iceape-browser -icedax -icedove -icedove-inspector -icedove-locale-bg -icedove-locale-cs -icedove-locale-da -icedove-locale-de -icedove-locale-el -icedove-locale-es-es -icedove-locale-fi -icedove-locale-fr -icedove-locale-gu -icedove-locale-he -icedove-locale-hu -icedove-locale-it -icedove-locale-ja -icedove-locale-ko -icedove-locale-mk -icedove-locale-nb -icedove-locale-nl -icedove-locale-ru -icedove-locale-sk -icedove-locale-sl -icedove-locale-sv -icedove-locale-tr -icedove-locale-zh-cn -icedove-typeaheadfind -iceweasel -iceweasel-dom-inspector -iceweasel-l10n-ar -iceweasel-l10n-bg -iceweasel-l10n-ca -iceweasel-l10n-cs -iceweasel-l10n-da -iceweasel-l10n-de -iceweasel-l10n-el -iceweasel-l10n-es-es -iceweasel-l10n-eu -iceweasel-l10n-fi -iceweasel-l10n-fr -iceweasel-l10n-hu -iceweasel-l10n-it -iceweasel-l10n-ja -iceweasel-l10n-lt -iceweasel-l10n-nl -iceweasel-l10n-pl -iceweasel-l10n-pt-br -iceweasel-l10n-ru -iceweasel-l10n-sk -iceweasel-l10n-sl -iceweasel-l10n-zh-cn -icewm -icewm-common -icewm-themes -icmpush -iconx -idswakeup -iftop -ifupdown -ijsgimpprint -ijsgutenprint -ilisp -imageindex -imagemagick -imaze -imlib-base -imlib-progs -imlib11 -indi -industrial-cursor-theme -info -infobash -initramfs-tools -initrd-tools -initscripts -inkscape -intltool-debian -ipcalc -ipchains -iperf -ipppd -iproute -ipsec-tools -iptables -iptraf -iputils-ping -iputils-tracepath -ipv6calc -ipw2100-nonfree -ipw2200-nonfree -ipx -ipython -irb -irb1.8 -ircii -irda-common -irda-tools -irssi -irssi-plugin-icq -irssi-scripts -isapnptools -isdnactivecards -isdnutils-base -isdnvboxclient -iso-codes -isomaster -ispell -jackd -jade -java-common -jfsutils -jikes -joe -john -jokosher -jpilot -jpilot-backup -jpilot-mail -jpilot-plugins -jpilot-syncmal -juk -junit -k3b -k3b-defaults -k3b-i18n -kaddressbook -kaffe -kaffe-common -kaffe-pthreads -kaffeine -kakasi -kakasi-dic -kalarm -kalzium -kalzium-data -kamera -kanagram -kandy -kanjidic -kappfinder -kapptemplate -karbon -karm -kasteroids -kate -kate-plugins -katomic -kbabel -kbabel-dev -kbackgammon -kbackup -kbackup-doc -kbackup-multibuf -kbattleship -kbdconfig -kbear -kblackbox -kbounce -kbruch -kbugbuster -kcachegrind -kcalc -kcharselect -kchart -kcoloredit -kcontrol -kcron -kdat -kde-amusements -kde-core -kde-i18n-az -kde-i18n-bg -kde-i18n-ca -kde-i18n-cs -kde-i18n-da -kde-i18n-de -kde-i18n-el -kde-i18n-es -kde-i18n-et -kde-i18n-fa -kde-i18n-fi -kde-i18n-fr -kde-i18n-he -kde-i18n-hu -kde-i18n-it -kde-i18n-ja -kde-i18n-nl -kde-i18n-pl -kde-i18n-pt -kde-i18n-ptbr -kde-i18n-ru -kde-i18n-sk -kde-i18n-sl -kde-i18n-sr -kde-i18n-sv -kde-i18n-tr -kde-i18n-zhcn -kde-i18n-zhtw -kdeaddons-kfile-plugins -kdeadmin -kdeadmin-kfile-plugins -kdeartwork -kdeartwork-emoticons -kdeartwork-misc -kdeartwork-style -kdeartwork-theme-icon -kdeartwork-theme-window -kdebase -kdebase-bin -kdebase-data -kdebase-kio-plugins -kdebluetooth -kdeedu -kdeedu-data -kdeedu-doc-html -kdegames -kdegames-card-data -kdegames-doc-html -kdegraphics-doc-html -kdegraphics-kfile-plugin -kdelibs -kdelibs-data -kdelibs4-dev -kdelibs4c2a -kdemultimedia-kfile-plug -kdemultimedia-kio-plugin -kdenetwork-kfile-plugins -kdepasswd -kdepim -kdepim-kfile-plugins -kdepim-kio-plugins -kdepim-kresources -kdepim-wizards -kdeprint -kdesdk -kdesdk-doc-html -kdesdk-kfile-plugins -kdesdk-kio-plugins -kdesdk-misc -kdesdk-scripts -kdesktop -kdessh -kdetoys -kdetoys-doc-html -kdevelop -kdevelop-data -kdevelop-doc -kdewallpapers -kdewebdev -kdewebdev-doc-html -kdf -kdict -kdiff3 -kdissert -kdm -kdoc -kdvi -keduca -kenolaba -kernel-package -kexec-tools -kexi -kfax -kfilereplace -kfind -kfloppy -kformula -kfouleggs -kgamma -kget -kghostview -kgoldrunner -khangman -khelpcenter -khexedit -kicker -kiconedit -kig -kile -kile-i18n -kimagemapeditor -kino -kiosktool -kipi-plugins -kismet -kitchensync -kiten -kivio -kivio-data -kjumpingcube -klaptopdaemon -klatin -kleopatra -klettres -klettres-data -klibc-utils -klickety -klines -klinkstatus -klipper -klogd -kmahjongg -kmail -kmailcvt -kmenuedit -kmessedwords -kmines -kmix -kmoon -kmplot -kmrml -kmtrace -kmymoney2 -knetwalk -knetworkconf -knode -knotes -kodo -koffice -koffice-data -koffice-dev -koffice-doc -koffice-doc-html -koffice-i18n-af -koffice-i18n-bg -koffice-i18n-br -koffice-i18n-ca -koffice-i18n-cs -koffice-i18n-da -koffice-i18n-de -koffice-i18n-el -koffice-i18n-es -koffice-i18n-et -koffice-i18n-fa -koffice-i18n-fi -koffice-i18n-fr -koffice-i18n-he -koffice-i18n-hu -koffice-i18n-it -koffice-i18n-ja -koffice-i18n-nl -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-tr -koffice-i18n-zhcn -koffice-i18n-zhtw -koffice-libs -kolf -kolourpaint -kommander -kommander-dev -kompare -konq-plugins -konqueror -konqueror-nsplugins -konquest -konsole -konsolekalendar -kontact -konversation -kooka -kopete -korganizer -korn -koshell -kpackage -kpager -kpat -kpdf -kpercentage -kpersonalizer -kpf -kphone -kpilot -kplato -kpoker -kppp -kpresenter -kpresenter-data -kqemu-gui -krdc -kreversi -krfb -krita -krita-data -kruler -krusader -ksame -kscreensaver -kscreensaver-xsavers -kshisen -ksim -ksirtet -ksmiletris -ksmserver -ksnake -ksnapshot -ksokoban -kspaceduel -ksplash -kspread -kspy -kstars -kstars-data -ksudoku -ksvg -ksync -ksysguard -ksysguardd -ksysv -kteatime -kthesaurus -ktimer -ktip -ktnef -ktouch -ktron -ktuberling -kturtle -ktux -kugar -kuickshow -kuiviewer -kunittest -kuser -kvdr -kverbos -kview -kviewshell -kvoctrain -kweather -kwifimanager -kwin -kwin4 -kwlan -kword -kword-data -kwordquiz -kworldclock -kxsldbg -lacheck -ladcca2 -ladspa-sdk -lam-runtime -lam4c2 -lapack -lapack3 -laptop-detect -larswm -latex-beamer -latex-cjk-common -latex-xcolor -latex-xft-fonts -latex2html -lazarus -ldap-utils -lde -less -lesstif-dev -lesstif1 -lesstif2 -lftp -lha -liba52-0.7.4 -libaa1 -libaa1-dev -libacl1 -libacl1-dev -libadns1 -libaiksaurus-1.2-0c2a -libaiksaurus-1.2-data -libakode2 -libalgorithm-dependency- -libalut0 -libanthy0 -libao2 -libapache-dbi-perl -libapache-mod-perl -libapache-mod-ssl -libapache-request-perl -libapache-session-perl -libapache2-mod-jk -libapache2-mod-php5 -libapm1 -libappconfig-perl -libapr0 -libapr1 -libaprutil1 -libapt-pkg-perl -libaqbanking-data -libaqbanking-plugins-lib -libaqbanking16 -libaqdtaus3 -libaqgeldkarte4 -libaqhbci10 -libarchive-zip-perl -libart-2.0-2 -libart-2.0-dev -libart2 -libarts1-dev -libarts1c2a -libartsc0 -libartsc0-dev -libasound2 -libasound2-dev -libaspell-dev -libaspell15 -libast2 -libasyncns0 -libatk1.0-0 -libatk1.0-dev -libatm1 -libatspi1.0-0 -libattr1 -libattr1-dev -libaudacious4 -libaudio-dev -libaudio2 -libaudiofile-dev -libaudiofile0 -libauthen-sasl-perl -libautotrace3 -libavahi-client-dev -libavahi-client3 -libavahi-common-data -libavahi-common-dev -libavahi-common3 -libavahi-compat-howl0 -libavahi-compat-libdnssd -libavahi-glib1 -libavahi-qt3-1 -libavahi-qt3-dev -libavc1394-0 -libavc1394-dev -libavcodec0d -libavformat0d -libbcel-java -libbeecrypt6 -libberylsettings0 -libbind9-0 -libblkid1 -libbluetooth2 -libbonobo2-0 -libbonobo2-common -libbonoboui2-0 -libbonoboui2-common -libboost-date-time1.33.1 -libboost-filesystem1.33. -libboost-python1.32.0 -libboost-python1.33.0c2a -libboost-python1.33.1 -libboost-regex1.33.1 -libbraille -libbrlapi1 -libbz2-1.0 -libbz2-dev -libc-client2002edebian -libc6 -libc6-dev -libcaca0 -libcache-cache-perl -libcache-simple-timedexp -libcairo-perl -libcairo2 -libcairo2-dev -libcamel1.2-8 -libcanlock2 -libcap-dev -libcap1 -libcapi20-3 -libcapi20-dev -libcapsinetwork0c2a -libcdio6 -libcdk5 -libcdparanoia0 -libcfitsio2 -libchipcard-common -libchipcard2-0c2 -libchipcard20 -libclamav1 -libclan2c2a-gui -libclan2c2a-jpeg -libclan2c2a-mikmod -libclan2c2a-png -libclan2c2a-sound -libclan2c2a-vorbis -libclanlib2c2a -libclass-accessor-perl -libclass-autouse-perl -libclass-container-perl -libclass-data-inheritabl -libclass-inspector-perl -libclass-returnvalue-per -libcln4 -libclone-perl -libcomerr2 -libcommons-beanutils-jav -libcommons-collections-j -libcommons-collections3- -libcommons-dbcp-java -libcommons-digester-java -libcommons-el-java -libcommons-fileupload-ja -libcommons-launcher-java -libcommons-logging-java -libcommons-modeler-java -libcommons-pool-java -libcommons-validator-jav -libcompfaceg1 -libcompress-zlib-perl -libconfhelper-perl -libconfig-file-perl -libconfig-tiny-perl -libconsole -libconvert-asn1-perl -libconvert-binhex-perl -libcroco3 -libcrypt-ssleay-perl -libcsiro0 -libcucul0 -libcupsimage2 -libcupsys2 -libcupsys2-dev -libcurl3 -libcurl3-gnutls -libcvsservice0 -libdate-manip-perl -libdb1-compat -libdb3 -libdb4.2 -libdb4.3 -libdb4.4 -libdb4.4-dev -libdbd-mysql-perl -libdbd-pg-perl -libdbi-perl -libdbix-dbschema-perl -libdbix-searchbuilder-pe -libdbus-1-2 -libdbus-1-3 -libdbus-1-dev -libdbus-glib-1-2 -libdbus-qt-1-1c2 -libdc1394-13 -libdevel-stacktrace-perl -libdevel-symdump-perl -libdevmapper1.02 -libdigest-sha1-perl -libdirectfb-0.9-25 -libdirectfb-dev -libdirectfb-extra -libdiscover1 -libdjvulibre15 -libdm0 -libdmx-dev -libdmx1 -libdns21 -libdrm2 -libdshconfig1 -libdv-bin -libdv4 -libdv4-dev -libdvdread-dev -libdvdread3 -libebook1.2-5 -libecal1.2-6 -libedata-book1.2-2 -libedata-cal1.2-5 -libedataserver1.2-7 -libedataserverui1.2-6 -libedit2 -libeel2-2 -libeel2-data -libegroupwise1.2-10 -libelfg0 -libemeraldengine0 -libenchant1c2a -liberror-perl -libesd-alsa0 -libesd0-dev -libestools1.2 -libevent1 -libexception-class-perl -libexchange-storage1.2-1 -libexif-dev -libexif-gtk5 -libexif12 -libexiv2-0.10 -libexo-0.3-0 -libexpat1 -libexpat1-dev -libextutils-autoinstall- -libf2c2 -libf2c2-dev -libfcgi-perl -libffi4 -libffi4-dev -libfile-find-rule-perl -libfile-flat-perl -libfile-ncopy-perl -libfile-remove-perl -libfile-slurp-perl -libfinance-quote-perl -libflac++5 -libflac7 -libfltk1.1 -libfluidsynth1 -libfont-afm-perl -libfontconfig1 -libfontconfig1-dev -libfontenc-dev -libfontenc1 -libforms1 -libfreefem0 -libfreetype6 -libfreetype6-dev -libfreezethaw-perl -libfribidi0 -libfs-dev -libfs6 -libft-perl -libfuse-dev -libfuse2 -libg2c0 -libg2c0-dev -libgadu3 -libgail-common -libgail-gnome-module -libgail17 -libgal2.2-1 -libgal2.2-common -libgal2.4-0 -libgal2.4-common -libgamin-dev -libgamin0 -libgc1c2 -libgcc1 -libgcj-bc -libgcj-common -libgcj4 -libgcj4-awt -libgcj4-common -libgcj6 -libgcj6-jar -libgcj7-0 -libgcj7-awt -libgcj7-dev -libgcj7-jar -libgcompris-1-0 -libgconf11 -libgconf2-4 -libgconf2.0-cil -libgcrypt11 -libgcrypt11-dev -libgd2-xpm -libgda2-3 -libgda2-common -libgdal1-1.3.2 -libgdbm3 -libgdchart-gd2-noxpm -libgdgeda6 -libgdiplus -libgdk-pixbuf-dev -libgdk-pixbuf2 -libgecko2.0-cil -libgeda20 -libgeo-ipfree-perl -libgeoip1 -libgeos2c2a -libgfortran1 -libgfortran1-dev -libghemical-data -libghemical0c2a -libghttp1 -libgimp2.0 -libginac1.3c2a -libgksu1.2-0 -libgksu2-0 -libgksuui1.0-1 -libgl1-mesa-dev -libgl1-mesa-dri -libgl1-mesa-glx -libglade2-0 -libglade2.0-cil -libgle3 -libglib-perl -libglib1.2 -libglib1.2-dev -libglib2.0-0 -libglib2.0-cil -libglib2.0-data -libglib2.0-dev -libglibmm-2.4-1c2a -libglibmm-2.4-dev -libglide3 -libglpk0 -libglpng -libglu1-mesa -libglu1-mesa-dev -libglu1-xorg -libglu1-xorg-dev -libgmp3c2 -libgnokii3 -libgnome-desktop-2 -libgnome-keyring0 -libgnome-mag2 -libgnome-media0 -libgnome-menu2 -libgnome-pilot2 -libgnome-speech3 -libgnome-window-settings -libgnome2-0 -libgnome2-canvas-perl -libgnome2-common -libgnome2-perl -libgnome2-vfs-perl -libgnome2.0-cil -libgnome32 -libgnomecanvas2-0 -libgnomecanvas2-common -libgnomecups1.0-1 -libgnomecupsui1.0-1c2a -libgnomeprint2.2-0 -libgnomeprint2.2-data -libgnomeprintui2.2-0 -libgnomeprintui2.2-commo -libgnomesupport0 -libgnomeui-0 -libgnomeui-common -libgnomeui32 -libgnomevfs2-0 -libgnomevfs2-bin -libgnomevfs2-common -libgnomevfs2-extra -libgnorba27 -libgnorbagtk0 -libgnutls-dev -libgnutls12 -libgnutls13 -libgoffice-1-2 -libgoffice-1-common -libgpg-error-dev -libgpg-error0 -libgpgme11 -libgphoto2-2 -libgphoto2-2-dev -libgphoto2-port0 -libgpmg1 -libgpod0 -libgraflib1 -libgraflib1-dev -libgrafx11-1 -libgrafx11-1-dev -libgraphicsmagick1 -libgsf-1-114 -libgsf-1-common -libgsf-gnome-1-114 -libgsl0 -libgsl0-dev -libgsm1 -libgsmme1c2a -libgssapi2 -libgstreamer-plugins-bas -libgstreamer0.10-0 -libgstreamer0.8-0 -libgtk1.2 -libgtk1.2-common -libgtk1.2-dev -libgtk2-perl -libgtk2.0-0 -libgtk2.0-bin -libgtk2.0-cil -libgtk2.0-common -libgtk2.0-dev -libgtkglext1 -libgtkhtml3.2-11 -libgtkhtml3.6-18 -libgtkhtml3.8-15 -libgtkmm-2.4-1c2a -libgtkmm-2.4-dev -libgtksourceview-common -libgtksourceview1.0-0 -libgtksourceview2.0-cil -libgtkspell0 -libgtop2-7 -libgtop2-common -libgts-0.7-1 -libgucharmap4 -libguile-ltdl-1 -libgutenprint2 -libgutenprintui2-1 -libgwenhywfar-data -libgwenhywfar38 -libgwrap-runtime0 -libgwrap-runtime0-dev -libhal-storage1 -libhal1 -libhd13 -libhdf4g -libhdf5-serial-1.6.5-0 -libhdf5-serial-dev -libhfsp0 -libhtml-format-perl -libhtml-mason-perl -libhtml-parser-perl -libhtml-scrubber-perl -libhtml-tableextract-per -libhtml-tagset-perl -libhtml-template-expr-pe -libhtml-template-perl -libhtml-tree-perl -libhttp-ghttp-perl -libice-dev -libice6 -libicu36 -libid3-3.8.3c2a -libid3tag0 -libident -libidl0 -libidn11 -libidn11-dev -libiec61883-0 -libieee1284-3 -libifp4 -libijs-0.35 -libimage-base-bundle-per -libimage-info-perl -libimlib2 -libimlib2-dev -libindex0 -libio-pty-perl -libio-socket-ssl-perl -libio-string-perl -libio-stringy-perl -libiodbc2 -libipc-run-perl -libipc-sharelite-perl -libisc11 -libisccc0 -libisccfg1 -libiso9660-4 -libiw-dev -libiw28 -libjack0.100.0-0 -libjack0.100.0-dev -libjasper-1.701-1 -libjasper-1.701-dev -libjaxp1.3-java -libjcode-perl -libjcode-pm-perl -libjpeg-progs -libjpeg62 -libjpeg62-dev -libjsch-java -libk3b2 -libkadm55 -libkbanking1 -libkcal2b -libkcddb1 -libkdeedu3 -libkdegames1 -libkdepim1a -libkernlib1 -libkernlib1-dev -libkexif1 -libkgantt0 -libkipi0 -libkiten1 -libkjsembed1 -libkleopatra1 -libklibc -libkmime2 -libkonq4 -libkpathsea4 -libkpimexchange1 -libkpimidentities1 -libkrb5-dev -libkrb53 -libksba8 -libkscan1 -libksieve0 -libktnef1 -libktoblzcheck1c2a -liblcms1 -liblcms1-dev -libldap-2.3-0 -libldap2 -libldap2-dev -liblinphone1 -liblircclient0 -liblo0 -liblocale-gettext-perl -liblocale-maketext-fuzzy -liblocale-maketext-lexic -liblockdev1 -liblockfile1 -liblog-dispatch-perl -liblog4j1.2-java -liblog4net1.2-cil -liblogfile-rotate-perl -libloudmouth1-0 -liblrdf0 -libltdl3 -libltdl3-dev -liblua50 -liblua50-dev -liblualib50 -liblualib50-dev -liblucene-java -liblucene-java-doc -liblwres1 -liblwres9 -liblzo-dev -liblzo1 -libm17n-0 -libmad0 -libmad0-dev -libmagic1 -libmagick++9c2a -libmagick9 -libmagick9-dev -libmailtools-perl -libmal1 -libmath++0c2a -libmathlib2 -libmathlib2-dev -libmdc2 -libmeanwhile1 -libmediastreamer0 -libmetacity0 -libmhash2 -libmikmod2 -libmime-perl -libmimelib1c2a -libmldbm-perl -libmms0 -libmng-dev -libmng1 -libmodplug0c2 -libmodule-versions-repor -libmono-accessibility2.0 -libmono-cairo1.0-cil -libmono-cecil0.4-cil -libmono-corlib1.0-cil -libmono-corlib2.0-cil -libmono-data-tds1.0-cil -libmono-data-tds2.0-cil -libmono-microsoft-build2 -libmono-peapi1.0-cil -libmono-peapi2.0-cil -libmono-relaxng1.0-cil -libmono-security1.0-cil -libmono-security2.0-cil -libmono-sharpzip0.84-cil -libmono-sharpzip2.84-cil -libmono-system-data1.0-c -libmono-system-data2.0-c -libmono-system-runtime1. -libmono-system-runtime2. -libmono-system-web1.0-ci -libmono-system-web2.0-ci -libmono-system1.0-cil -libmono-system2.0-cil -libmono-winforms2.0-cil -libmono0 -libmono1.0-cil -libmono2.0-cil -libmopac7-0 -libmozjs0d -libmpcdec3 -libmpeg2-4 -libmpeg2-4-dev -libmpeg3-1 -libmpeg3-dev -libmpfr1 -libmpich1.0c2 -libmusicbrainz4c2a -libmx4j-java -libmyspell3c2 -libmysqlclient10 -libmysqlclient15-dev -libmysqlclient15off -libnasl2 -libnautilus-burn2 -libnautilus-burn3 -libnautilus-extension1 -libncp -libncurses5 -libncurses5-dev -libncursesw5 -libncursesw5-dev -libneon25 -libneon26 -libnessus2 -libnet-daemon-perl -libnet-ip-perl -libnet-ldap-perl -libnet-ssleay-perl -libnet0 -libnet1 -libnetcdf3 -libnetpbm10 -libnewt-dev -libnewt-utf8-0 -libnewt0.52 -libnfsidmap2 -libnids1.20 -libniftiio0 -libnjb5 -libnm-glib0 -libnotify1 -libnspr4 -libnspr4-0d -libnss-mdns -libnss3 -libnss3-0d -libntfs9 -libnumber-compare-perl -liboaf0 -libofx3 -libogg-dev -libogg0 -liboggflac3 -liboil0.3 -libopal-2.2.0 -libopenal0a -libopenbabel1 -libopencdk8 -libopencdk8-dev -libopenexr-dev -libopenexr2c2a -libopenobex1 -liborbit0 -liborbit2 -liboro-java -libortp5 -libosip2-3 -libosp5 -libostyle1c2 -libotf0 -libpacklib1 -libpacklib1-dev -libpam-modules -libpam-ncp -libpam-runtime -libpam0g -libpam0g-dev -libpanel-applet2-0 -libpango1.0-0 -libpango1.0-common -libpango1.0-dev -libpaper-utils -libpaper1 -libparams-util-perl -libparams-validate-perl -libpari-dev -libpari2-gmp -libparse-recdescent-perl -libparted1.6-0 -libparted1.7-1 -libparted1.7-dev -libpath-class-perl -libpawlib2 -libpawlib2-dev -libpcap0.7 -libpcap0.8 -libpcd2 -libpci2 -libpcre3 -libpcre3-dev -libpcrecpp0 -libpcsclite1 -libperl5.8 -libpg-perl -libpgsql2 -libpisock8 -libpisock9 -libpisync0 -libplot2c2 -libplplot9 -libplrpc-perl -libpng12-0 -libpng12-dev -libpod-tests-perl -libpoppler0c2 -libpoppler0c2-glib -libpoppler0c2-qt -libpopt-dev -libpopt0 -libportaudio0 -libpostproc0d -libpq-dev -libpq4 -libpqxx-2.6.8 -libprefork-perl -libpstoedit0c2a -libpt-1.10.0 -libpt-plugins-oss -libpt-plugins-v4l2 -libpth20 -libpulse0 -libpvm3 -libqbanking4 -libqcad0 -libqhull5 -libqscintilla6 -libqt3-compat-headers -libqt3-headers -libqt3-mt -libqt3-mt-dev -libqt3-mt-psql -libqt4-core -libqt4-gui -libqthreads-12 -libquantlib-0.3.13 -libquicktime-dev -libquicktime0 -libraptor1 -libraw1394-8 -libraw1394-dev -libreadline-ruby1.8 -libreadline4 -libreadline5 -libreadline5-dev -librecode0 -libregexp-common-perl -libregexp-java -libresid-builder0c2a -libresmgr1 -libroman-perl -librpcsecgss3 -librplay3 -librpm4 -librsvg2-2 -librsvg2-common -libruby1.8 -librxp1 -libsablot0 -libsamplerate0 -libsane -libsane-extras -libsasl2 -libsasl2-2 -libsasl2-dev -libsasl2-modules -libsc7 -libscrollkeeper0 -libsdl-console -libsdl-erlang -libsdl-gfx1.2-4 -libsdl-image1.2 -libsdl-mixer1.2 -libsdl-net1.2 -libsdl-pango1 -libsdl-perl -libsdl-ttf2.0-0 -libsdl1.2-dev -libsdl1.2debian -libsdl1.2debian-alsa -libselinux1 -libsensors3 -libsepol1 -libservlet2.3-java -libservlet2.4-java -libsexy2 -libsgmls-perl -libsgutils1 -libshout3 -libsidplay1 -libsidplay2 -libsigc++-2.0-0c2a -libsigc++-2.0-dev -libslang2 -libslang2-dev -libslp1 -libsm-dev -libsm6 -libsmbclient -libsmpeg0 -libsndfile1 -libsnmp-base -libsnmp9 -libsoup2.2-8 -libsp1c2 -libspeex1 -libsqlite0 -libsqlite3-0 -libss2 -libssl-dev -libssl0.9.6 -libssl0.9.7 -libssl0.9.8 -libssp0 -libstartup-notification0 -libstdc++2.10-glibc2.2 -libstdc++5 -libstdc++5-3.3-dev -libstdc++6 -libstdc++6-4.0-dev -libstdc++6-4.1-dev -libstroke0 -libstruts1.2-java -libsufary2 -libsvga1 -libsvga1-dev -libsvn1 -libswt3.2-gtk-java -libswt3.2-gtk-jni -libsysfs2 -libt1-5 -libtag1c2a -libtagc0 -libtasn1-3 -libtasn1-3-dev -libtemplate-perl -libterm-readkey-perl -libterm-readline-perl-pe -libtest-classapi-perl -libtest-inline-perl -libtext-autoformat-perl -libtext-charwidth-perl -libtext-format-perl -libtext-glob-perl -libtext-iconv-perl -libtext-quoted-perl -libtext-reform-perl -libtext-template-perl -libtext-wikiformat-perl -libtext-wrapi18n-perl -libtext-wrapper-perl -libtheora-dev -libtheora0 -libthunar-vfs-1-2 -libtidy-0.99-0 -libtiff-tools -libtiff4 -libtiff4-dev -libtiffxx0c2 -libtime-modules-perl -libtimedate-perl -libtomcat5-java -libtomcat5.5-java -libtool -libtotem-plparser1 -libtree-simple-perl -libtse3-0.3.1c2a -libttf2 -libtunepimp-bin -libtunepimp3 -libufsparse -libungif4-dev -libungif4g -libuniconf4.2 -liburi-perl -libusb-0.1-4 -libusb-dev -libuuid1 -libvcdinfo0 -libvisual-0.4-0 -libvolume-id0 -libvorbis-dev -libvorbis0a -libvorbisenc2 -libvorbisfile3 -libvte-common -libvte4 -libvtk5 -libvtk5-dev -libwant-perl -libwavpack0 -libweakref-perl -libwmf-bin -libwmf-dev -libwmf0.2-7 -libwnck-common -libwnck18 -libwpd8c2a -libwrap0 -libwrap0-dev -libwraster3 -libwv-1.2-1 -libwv-1.2-3 -libwv2-1c2 -libwvstreams4.2-base -libwvstreams4.2-extras -libwww-perl -libwxbase2.6-0 -libwxgtk2.4-1 -libwxgtk2.6-0 -libx11-6 -libx11-data -libx11-dev -libxalan110 -libxau-dev -libxau6 -libxaw-headers -libxaw6 -libxaw7 -libxaw7-dev -libxcomp1 -libxcompext1 -libxcomposite-dev -libxcomposite1 -libxcursor-dev -libxcursor1 -libxdamage-dev -libxdamage1 -libxdelta2 -libxdmcp-dev -libxdmcp6 -libxerces2-java -libxerces27 -libxevie-dev -libxevie1 -libxext-dev -libxext6 -libxfce4mcs-client3 -libxfce4mcs-manager3 -libxfce4util4 -libxfcegui4-4 -libxfixes-dev -libxfixes3 -libxfont-dev -libxfont1 -libxft-dev -libxft2 -libxi-dev -libxi6 -libxine-dev -libxine1 -libxinerama-dev -libxinerama1 -libxkbfile-dev -libxkbfile1 -libxkbui-dev -libxkbui1 -libxklavier10 -libxml++1.0c2a -libxml-dom-perl -libxml-filter-buffertext -libxml-libxml-common-per -libxml-libxml-perl -libxml-libxslt-perl -libxml-namespacesupport- -libxml-parser-perl -libxml-perl -libxml-regexp-perl -libxml-rss-perl -libxml-sablot-perl -libxml-sax-machines-perl -libxml-sax-perl -libxml-sax-writer-perl -libxml-simple-perl -libxml-xpath-perl -libxml1 -libxml2 -libxml2-dev -libxml2-utils -libxmu-dev -libxmu-headers -libxmu6 -libxmuu-dev -libxmuu1 -libxp-dev -libxp6 -libxplc0.3.13 -libxpm-dev -libxpm4 -libxrandr-dev -libxrandr2 -libxrender-dev -libxrender1 -libxres-dev -libxres1 -libxslt1-dev -libxslt1.1 -libxss-dev -libxss1 -libxt-dev -libxt6 -libxtrap-dev -libxtrap6 -libxtst-dev -libxtst6 -libxul-common -libxul0d -libxv-dev -libxv1 -libxvmc-dev -libxvmc1 -libxxf86dga-dev -libxxf86dga1 -libxxf86misc-dev -libxxf86misc1 -libxxf86vm-dev -libxxf86vm1 -libzipios++0c2a -libzvbi-common -libzvbi-dev -libzvbi-doc -libzvbi0 -libzvt2.0-0 -lilo -lilypond-data -lilypond-doc -linneighborhood -linphone -linphone-common -linphone-nox -linux-image-2.6.19 -linux-kernel-headers-kno -linux-sound-base -linuxdoc-tools -linuxdoc-tools-info -linuxdoc-tools-latex -linuxdoc-tools-text -lisa -loadlin -locales -lockfile-progs -login -logrotate -lookup -loop-aes-modules-2.6.19 -loop-aes-source -loop-aes-utils -lrzsz -lsb -lsb-base -lsb-core -lsb-cxx -lsb-desktop -lsb-graphics -lsb-qt4 -lsb-release -lsdvd -lskat -lsof -ltrace -lua50 -lvm-common -lvm2 -lynx -lyx -lyx-common -lyx-qt -lyx-xforms -lzop -m17n-db -m4 -macutils -madwifi-modules-2.6.19 -madwifi-source -madwifi-tools -mailx -make -makedev -man-db -manpages -manpages-de -manpages-dev -matwrap -mawk -maxima -maxima-doc -maxima-emacs -maxima-share -maxima-src -maxima-test -mayavi -mbr -mc -mcl -mcl-doc -mdadm -med-common -med-tools -medcon -memtest86 -memtest86+ -memtester -mencal -menu -menu-xdg -mesa-common-dev -mesa-utils -metacity -metacity-common -metamail -mgdiff -mgp -mikmod -mime-support -mimms -mindi -mindi-busybox -mindi-kernel -mindi-partimagehack -minicom -misdn-utils -misdn-voipisdn -mkbootdev -mkisofs -hi -mktemp -mldonkey-gui -mldonkey-server -mlock -mobilemesh -modconf -module-assistant -module-init-tools -modutils -mondo -mondo-doc -mono -mono-apache-server -mono-common -mono-devel -mono-gac -mono-gmcs -mono-jay -mono-jit -mono-mcs -mono-runtime -mono-utils -mono-xsp-base -monodevelop -monodoc-base -monodoc-browser -monodoc-http -monodoc-manual -monopd -monotone -mount -mouseconfig -mozilla-browser -mozilla-firefox -mozilla-helix-player -mozilla-psm -mozilla-thunderbird -mozilla-thunderbird-insp -mozilla-thunderbird-type -mpack -mpage -mpg321 -mplayer -mplayer-skin-blue -mpqc -mpqc-support -ms-sys -mt-st -mtools -mtr -mtx -multimix -mutt -myspell-bg -myspell-de-at -myspell-de-ch -myspell-de-de -myspell-en-gb -myspell-en-us -myspell-es -myspell-fr -myspell-it -myspell-pl -mysql-client -mysql-client-5.0 -mysql-common -mysql-server -mysql-server-5.0 -mysql-zrm -mysql-zrm-socket-server -nagios-nrpe-plugin -nagios-plugins-basic -nagios2 -nagios2-common -nagios2-doc -nano -nasm -nautilus -nautilus-cd-burner -nautilus-data -ncftp -ncpfs -ncurses-base -ncurses-bin -ncurses-term -ndiswrapper-modules-2.6. -ndiswrapper-source -nedit -nessus -nessus-plugins -nessusd -net-tools -netbase -netcat -netcat6 -nethack-common -nethack-console -nethack-qt -nethack-x11 -netpbm -netpipe-tcp -netpipes -netris -netspeed -networkstatus -neverball -neverdata -nfs-common -nfs-kernel-server -ngrep -nis -nkf -nmap -noteedit -noteedit-data -nowebm -nparted -ntfs-3g -ntpdate -nvtv -nvu -nxagent -nxclient -nxdesktop -nxlibs -nxproxy -nxssh -nxtunnel-client -nxtunnel-server -oaf -obconf -ocaml-base-nox -ocfs2-tools -ocfs2console -octave -octave-epstk -octave-sp -octave-statdataml -octave2.1 -octave2.9 -octave2.9-doc -octave2.9-headers -octave2.9-htmldoc -odbc-postgresql -odbcinst1debian1 -ofx -oneko -openbox -openbsd-inetd -openhackware -openjade -openjade1.3 -openoffice-de-en -openoffice.org-debian-me -opensched -openssh-client -openssh-server -openssl -openvpn -outguess -p0f -pari-doc -pari-extra -pari-gp -parted-bf -partimage -partimage-server -passwd -patch -patchutils -paw -paw-common -paw-demos -pax -pcb -pciutils -pciutils-dev -pcmcia-cs -pcmciautils -pdl -pentanet-doc -pentanet-utils -perl -perl-base -perl-doc -perl-modules -perl-suid -perl-tk -perlmagick -pgapack -pgdocs-pdf-a4 -pgf -pgpgpg -php5 -php5-common -php5-gd -php5-imap -php5-ldap -php5-mhash -php5-mysql -phpmyadmin -pi -pia -pilot-link -pinentry-qt -pingus -pingus-data -pioneers-ai -pioneers-client -pioneers-help -pioneers-server-console -pioneers-server-data -pioneers-server-gtk -pkg-config -planetpenguin-racer -planetpenguin-racer-data -planner -playmidi -plib1.8.4c2 -plotutils -pm-dev -pmidi -pmount -pmtools -pnm2ppa -po-debconf -portmap -poster -postgresql-8.0 -postgresql-client-8.0 -postgresql-client-common -postgresql-common -postgresql-contrib-8.0 -postgresql-doc-8.0 -postgresql-plperl-8.0 -postgresql-plpython-8.0 -postgresql-pltcl-8.0 -postgresql-server-dev-8. -potrace -powermgmt-base -poxml -ppmd -ppp -hi -pppdcapiplugin -pppoe -pppoeconf -pppstatus -pptp-linux -prelink -preview-latex-style -print-utils-pfeifle -prism54-nonfree -procinfo -procmail -procps -proj -proll -psfontmgr -psgml -psmisc -pspp -psutils -pump -pvm -pxlib1 -pybliographer -python -python-alsaaudio -python-apt -python-bibtex -python-cairo -python-central -python-dbus -python-doc -python-egenix-mxdatetime -python-egenix-mxtools -python-extclass -python-glade2 -python-gmenu -python-gnome2 -python-gnome2-desktop -python-gst0.10 -python-gtk-1.2 -python-gtk2 -python-imaging -python-imaging-doc -python-imaging-doc-html -python-imaging-doc-pdf -python-imaging-tk -python-ldap -python-libxml2 -python-minimal -python-netcdf -python-numeric -python-numeric-ext -python-numeric-tutorial -python-pygresql -python-pyorbit -python-pysqlite2 -python-scientific -python-scientific-doc -python-sigmask -python-support -python-tk -python-vtk -python-wxgtk2.4 -python-wxgtk2.6 -python-wxversion -python-xml -python2.1 -python2.3 -python2.3-dev -python2.3-doc -python2.4 -python2.4-doc -python2.4-minimal -qca-tls -qcad -qemu -qm -qmtest -qobex -qps -qt3-assistant -qt3-designer -qt3-dev-tools -qt3-doc -qtparted -quanta -quanta-data -quantlib-examples -quantlib-python -quantlib-refman -quantlib-refman-html -quantlib-ruby -r-base -r-base-core -r-base-dev -r-base-html -r-base-latex -r-cran-abind -r-cran-acepack -r-cran-boot -r-cran-car -r-cran-chron -r-cran-cluster -r-cran-coda -r-cran-dbi -r-cran-design -r-cran-effects -r-cran-foreign -r-cran-gdata -r-cran-gmodels -r-cran-gplots -r-cran-gregmisc -r-cran-gtkdevice -r-cran-gtools -r-cran-hmisc -r-cran-its -r-cran-kernsmooth -r-cran-lattice -r-cran-lmtest -r-cran-mapdata -r-cran-maps -r-cran-mcmcpack -r-cran-mgcv -r-cran-multcomp -r-cran-mvtnorm -r-cran-nlme -r-cran-qtl -r-cran-quadprog -r-cran-rcmdr -r-cran-relimp -r-cran-rgl -r-cran-rmysql -r-cran-rodbc -r-cran-rpart -r-cran-rquantlib -r-cran-sandwich -r-cran-sm -r-cran-statdataml -r-cran-strucchange -r-cran-survival -r-cran-tkrplot -r-cran-tseries -r-cran-vr -r-cran-xml -r-cran-zoo -r-doc-html -r-doc-info -r-doc-pdf -r-mathlib -r-recommended -radio -raptor-utils -ratmenu -ratpoison -rcalc -rcs -rdate -rdesktop -readline-common -realpath -recode -recover -refblas3 -refblas3-dev -reiserfsprogs -reportbug -request-tracker3 -request-tracker3.4 -resmgr -rfb -rhythmbox -rocklight -rootstrap -rosegarden -rosegarden-data -rosegarden4 -rplay-client -rpm -rsync -rt2x00-cvs-modules-2.6.1 -rt3-clients -rt3.4-apache -rt3.4-clients -rtai -rtai-doc -rtai-source -rtfm -rubber -ruby -ruby-examples -ruby1.8 -rxp -rxvt-beta -s3switch -samba -samba-common -sane -sane-utils -sash -sbcl -sbl-auto-udeb -scanmodem -scantv -scli -scons -screen -scribus -scribus-doc-de -scribus-doc-en -scribus-doc-fr -scrollkeeper -scsitools -scummvm -sdic -sdic-edict -secpolicy -sed -selfhtml -sendemail -sendfile -sendip -setserial -sfftobmp -sffview -sg3-utils -sgml-base -sgml-data -sgmlspl -sgmltools-lite -shaper -shared-mime-info -sharutils -sitar -slang1 -slang1a-utf8 -slapd -sleuthkit -slib -slirp -slrn -smail -smake -smartmontools -smbclient -smbconf-pfeifle -smbconf-pfeifle-nonfree -smbfs -smpeg-plaympeg -smpeg-xmms -sniffit -sodipodi -sound-juicer -sound-recorder -sox -sp -speedtouch -speex -spell -spellutils -sqlite -sqlite-doc -squid -squid-common -squidclient -ssh -ssl-cert -sslwrap -star -statserial -stellarium -stellarium-data -strace -stress -stunnel -subversion -sudo -sufary -sun-java5-bin -sun-java5-demo -sun-java5-fonts -sun-java5-jdk -sun-java5-jre -sun-java5-plugin -sunbird -sweep -swi-prolog -sylpheed -sylpheed-doc -sylpheed-i18n -symlinks -synaptic -sysklogd -syslinux -system-tools-backends -sysv-rc -sysvinit -sysvinit-utils -tar -tcl8.3 -tcl8.4 -tclreadline -tcpd -tcpdump -telnet-ssl -telnetd-ssl -terminatorx -testdisk -tetex-base -tetex-bin -tetex-doc -tetex-extra -tex-common -tex4ht -tex4ht-common -texi2html -texinfo -texmacs -texmacs-common -tftp -tftpd-hpa -thttpd -thunar -thunderbird -thunderbird-inspector -thunderbird-locale-bg -thunderbird-locale-cs -thunderbird-locale-da -thunderbird-locale-de -thunderbird-locale-el -thunderbird-locale-es-es -thunderbird-locale-fi -thunderbird-locale-fr -thunderbird-locale-gu -thunderbird-locale-he -thunderbird-locale-hu -thunderbird-locale-it -thunderbird-locale-ja -thunderbird-locale-ko -thunderbird-locale-mk -thunderbird-locale-nb -thunderbird-locale-nl -thunderbird-locale-ru -thunderbird-locale-sk -thunderbird-locale-sl -thunderbird-locale-sv -thunderbird-locale-tr -thunderbird-locale-zh-cn -thunderbird-typeaheadfin -tidy -tidy-doc -tiger -tightvncserver -timeout -timezoneconf -timidity -timidity-patches -tint -tix -tk8.3 -tk8.4 -tkdiff -tnef -tofrodos -tomcat5 -tomcat5-admin -tomcat5-webapps -toppler -tora -totem -totem-mozilla -totem-xine -tpconfig -traceroute -trang -trans-de-en -transfig -tripwire -tsclient -tshark -tsocks -ttf-arabeyes -ttf-arphic-bsmi00lp -ttf-bengali-fonts -ttf-bitstream-vera -ttf-dejavu -ttf-devanagari-fonts -ttf-dustin -ttf-f500 -ttf-farsiweb -ttf-freefont -ttf-gentium -ttf-gujarati-fonts -ttf-indic-fonts -ttf-isabella -ttf-junicode -ttf-kannada-fonts -ttf-kochi-gothic -ttf-malayalam-fonts -ttf-openoffice -ttf-opensymbol -ttf-oriya-fonts -ttf-punjabi-fonts -ttf-sjfonts -ttf-staypuft -ttf-summersby -ttf-tamil-fonts -ttf-telugu-fonts -ttmkfdir -tuxeyes -tuxkart -tuxkart-data -tuxmath -tuxpaint -tuxpaint-data -tuxpaint-stamps-default -tuxpuck -tuxtype -tuxtype-data -tvtime -twm -txt2regex -type-handling -type1inst -tzdata -ucf -udev -udpcast -umbrello -uml-utilities -umlrun -umlrun-uml -unifont -units -unixodbc -unp -unzip -unzoo -update -update-inetd -urlview -usbutils -usbview -user-de -user-mode-linux -user-mode-linux-doc -util-linux -util-linux-locales -uudeview -uuid-dev -v4l-conf -valgrind -vcdimager -vcdtools -vdr -vegastrike -vegastrike-data -vegastrike-music -verilog -vgabios -vigor -vim -vim-common -vim-gtk -vim-gui-common -vim-runtime -vim-scripts -vimpart -vino -vis5d-doc -vlan -vnc-common -vorbis-tools -vpnc -vrms -vtk-doc -vtk-examples -vtk-tcl -w3-dtd-mathml -w3c-dtd-xhtml -w3m -wakeonlan -wamerican -wavemon -wavtools -wbritish -wcanadian -wcatalan -wfrench -wget -wheretero -whiptail -whisker -whitespace -whois -wine -wine-dev -winetools -wings3d -wipe -wireless-tools -wireshark -wireshark-common -witalian -wmaker -wmaker-data -wmaker-usersguide-ps -wmakerconf -wmakerconf-data -wngerman -wnorwegian -wodim -wordnet -wordnet-base -wordtrans-data -wpasupplicant -wpolish -wprint -wv -wvdial -wwwconfig-common -wxmaxima -x-ttcidfont-conf -x11-common -x11proto-bigreqs-dev -x11proto-composite-dev -x11proto-core-dev -x11proto-damage-dev -x11proto-dmx-dev -x11proto-evie-dev -x11proto-fixes-dev -x11proto-fontcache-dev -x11proto-fonts-dev -x11proto-gl-dev -x11proto-input-dev -x11proto-kb-dev -x11proto-print-dev -x11proto-randr-dev -x11proto-record-dev -x11proto-render-dev -x11proto-resource-dev -x11proto-scrnsaver-dev -x11proto-trap-dev -x11proto-video-dev -x11proto-xcmisc-dev -x11proto-xext-dev -x11proto-xf86bigfont-dev -x11proto-xf86dga-dev -x11proto-xf86dri-dev -x11proto-xf86misc-dev -x11proto-xf86vidmode-dev -x11proto-xinerama-dev -x3270 -xalan -xaos -xaw3dg -xawtv -xawtv-plugins -xbase-clients -xbattle -xbitmaps -xboard -xboing -xchat -xchat-common -xclass-common -xcursor-themes -xdelta -xdg-utils -xdialog -xdm -xemacs21 -xemacs21-basesupport -xemacs21-bin -xemacs21-mule -xemacs21-mulesupport -xemacs21-support -xemacs21-supportel -xen-docs-3.0 -xen-hypervisor-3.0-i386 -xen-utils-3.0.3-1 -xen-utils-common -xfce -xfce4 -xfce4-icon-theme -xfce4-mcs-manager -xfce4-mcs-plugins -xfce4-mixer -xfce4-mixer-alsa -xfce4-panel -xfce4-session -xfce4-utils -xfdesktop4 -xfig -xfonts-100dpi -xfonts-100dpi-transcoded -xfonts-75dpi -xfonts-75dpi-transcoded -xfonts-base -xfonts-base-transcoded -xfonts-bolkhov-cp1251-75 -xfonts-bolkhov-cp1251-mi -xfonts-dosemu -xfonts-encodings -xfonts-scalable -xfonts-terminus -xfonts-utils -xfonts-x3270-misc -xfprint4 -xfsdump -xfsprogs -xfwm4 -xfwm4-themes -xgalaga -xine-ui -xjdic -xkb-data -xkbset -xlib6g -xlibmesa-gl -xlibmesa-gl-dev -xlibs -xlibs-static-dev -xloadimage -xmaxima -xmedcon -xmhtml1 -xml-core -xmms -xmms-cdread -xmms-goom -xmms-modplug -xmms-volnorm -xnest -xorg -xorg-dev -xosview -xpaint -xpdf -xpdf-common -xpdf-reader -xpdf-utils -xppaut -xsane -xsane-common -xscreensaver -xscreensaver-gl -xscreensaver-gnome -xserver-xorg -xserver-xorg-core -xserver-xorg-dev -xserver-xorg-input-all -xserver-xorg-input-evdev -xserver-xorg-input-kbd -xserver-xorg-input-mouse -xserver-xorg-input-synap -xserver-xorg-input-wacom -xserver-xorg-video-all -xserver-xorg-video-apm -xserver-xorg-video-ark -xserver-xorg-video-ati -xserver-xorg-video-chips -xserver-xorg-video-cirru -xserver-xorg-video-cyrix -xserver-xorg-video-dummy -xserver-xorg-video-fbdev -xserver-xorg-video-glint -xserver-xorg-video-i128 -xserver-xorg-video-i740 -xserver-xorg-video-i810 -xserver-xorg-video-imstt -xserver-xorg-video-mga -xserver-xorg-video-neoma -xserver-xorg-video-newpo -xserver-xorg-video-nsc -xserver-xorg-video-nv -xserver-xorg-video-rendi -xserver-xorg-video-s3 -xserver-xorg-video-s3vir -xserver-xorg-video-savag -xserver-xorg-video-silic -xserver-xorg-video-sis -xserver-xorg-video-sisus -xserver-xorg-video-tdfx -xserver-xorg-video-tga -xserver-xorg-video-tride -xserver-xorg-video-tseng -xserver-xorg-video-v4l -xserver-xorg-video-vesa -xserver-xorg-video-vga -xserver-xorg-video-via -xserver-xorg-video-vmwar -xserver-xorg-video-voodo -xskat -xsltproc -xterm -xtightvncviewer -xtrans-dev -xtv -xutils -xutils-dev -xviddetect -xvier -xvncviewer -xvt -xwpe -xzoom -yacas -yacas-doc -yacas-proteus -yafray -yelp -yorick -yorick-data -yorick-doc -zenity -zile -zip -zlib-bin -zlib1g -zlib1g-dev diff --git a/src/lists/mini b/src/lists/mini deleted file mode 100644 index 434bde0..0000000 --- a/src/lists/mini +++ /dev/null @@ -1,4 +0,0 @@ -# /usr/share/make-live/lists/mini - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny diff --git a/src/lists/minimal b/src/lists/minimal deleted file mode 100644 index dd81279..0000000 --- a/src/lists/minimal +++ /dev/null @@ -1,4 +0,0 @@ -# /usr/share/make-live/lists/minimal - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny diff --git a/src/lists/minimal-net b/src/lists/minimal-net deleted file mode 100644 index 0609035..0000000 --- a/src/lists/minimal-net +++ /dev/null @@ -1,8 +0,0 @@ -# /usr/share/make-live/lists/minimal-net - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Network -bind9-host dhcp-client dnsutils ftp ifupdown iptables iputils-ping mtr-tiny -net-tools netbase netcat openssh-client telnet traceroute wget whois diff --git a/src/lists/rescue b/src/lists/rescue deleted file mode 100644 index 256b6ea..0000000 --- a/src/lists/rescue +++ /dev/null @@ -1,57 +0,0 @@ -# /usr/share/make-live/lists/rescue - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# Rescue - -# Editors -mc nano-tiny qemacs-nox mg aview -# Harddisk -hdparm blktool scsitools -# Memory -memtester memtest86+ dmidecode -# System -procinfo pciutils usbutils hwinfo hwtools x86info cpuid -# Tools -tofrodos rpncalc units -# Browser -lynx links w3m -# Compression -unzip zip -# Backup -dar ddrescue gddrescue - -hal -read-edid -discover -wdiff -gawk -dc -dash -rlwrap -posh -chkrootkit -rkhunter -parted -partimage -grub -lilo -testdisk -xfsprogs -reiserfsprogs -e2fsprogs -ext2resize -ntfsprogs -dosfstools -genisoimage -wodim -dvd+rw-tools -clamav -clamav-data -wipe -secure-delete -minicom diff --git a/src/lists/standard b/src/lists/standard deleted file mode 100644 index 4da4dd2..0000000 --- a/src/lists/standard +++ /dev/null @@ -1,7 +0,0 @@ -# /usr/share/make-live/lists/standard - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales diff --git a/src/lists/standard-i18n b/src/lists/standard-i18n deleted file mode 100644 index b7c7391..0000000 --- a/src/lists/standard-i18n +++ /dev/null @@ -1,13 +0,0 @@ -# /usr/share/make-live/lists/standard-i18n - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# Standard i18n -manpages manpages-dev manpages-de manpages-de-dev manpages-es manpages-es-extra -manpages-fi manpages-fr manpages-fr-dev manpages-fr-extra 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 diff --git a/src/lists/x11 b/src/lists/x11 deleted file mode 100644 index 8928ee4..0000000 --- a/src/lists/x11 +++ /dev/null @@ -1,11 +0,0 @@ -# /usr/share/make-live/lists/x11 - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# X11 -xdm x-window-system -xresprobe diff --git a/src/lists/x11-core b/src/lists/x11-core deleted file mode 100644 index 89182c1..0000000 --- a/src/lists/x11-core +++ /dev/null @@ -1,11 +0,0 @@ -# /usr/share/make-live/lists/x11-core - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# X11 -xdm x-window-system-core -xresprobe diff --git a/src/lists/xfce b/src/lists/xfce deleted file mode 100644 index 0390a39..0000000 --- a/src/lists/xfce +++ /dev/null @@ -1,14 +0,0 @@ -# /usr/share/make-live/lists/xfce - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# Xfce -gdm xfce4 -desktop-base - -x-window-system-core -xresprobe diff --git a/src/lists/xfce-junior b/src/lists/xfce-junior deleted file mode 100644 index 56184e7..0000000 --- a/src/lists/xfce-junior +++ /dev/null @@ -1,20 +0,0 @@ -# /usr/share/make-live/lists/xfce - package list for make-live(1) - -# Minimal -eject file sudo vim-tiny - -# Standard -console-common kbd locales - -# Xfce -gdm xfce4 -desktop-base - -x-window-system-core -xresprobe - -# Debian Junior -junior-sound junior-typing junior-internet junior-gnome junior-toys -junior-games-net junior-games-sim junior-games-gl junior-puzzle junior-arcade -junior-math junior-writing junior-games-card junior-programming junior-system -junior-art junior-doc junior-games-text junior-kde diff --git a/src/main.sh b/src/main.sh deleted file mode 100755 index 346ec14..0000000 --- a/src/main.sh +++ /dev/null @@ -1,424 +0,0 @@ -#!/bin/sh - -# make-live - utility to build Debian Live systems -# -# Copyright (C) 2006 Daniel Baumann -# Copyright (C) 2006 Marco Amadori -# -# 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. - -set -e - -# Set static variables -BASE=${LIVE_BASE:-"/usr/share/make-live"} -CONFIG="/etc/make-live.conf" -PROGRAM="`basename ${0}`" -VERSION="0.99.26" - -export VERSION - -CODENAME_OLDSTABLE="woody" -CODENAME_STABLE="sarge" -CODENAME_TESTING="etch" -CODENAME_UNSTABLE="sid" - -export CODENAME_OLDSTABLE CODENAME_STABLE CODENAME_TESTING CODENAME_UNSTABLE - -# Source sub scripts -for SCRIPT in `find ${BASE}/scripts/ -not -name '*~' -not -wholename "${BASE}/scripts/.*" -and -type f` -do - . "${SCRIPT}" -done - -USAGE="Usage: ${PROGRAM} [-a|--architecture ARCHITECTURE] [-b|--bootappend KERNEL_PARAMETER|\"KERNEL_PARAMETERS\"] [--clone DIRECTORY] [--config FILE] [-c|--chroot DIRECTORY] [-d|--distribution DISTRIBUTION] [-e|--encryption ALGORITHM] [--with-generic-indices] [--without-generic-indices] [--with-recommends] [--without-recommends] [--with-daemons] [--without-daemons] [--filesystem FILESYSTEM] [-f|--flavour BOOTSTRAP_FLAVOUR] [--hook COMMAND|\"COMMANDS\"] [--include-chroot FILE|DIRECTORY] [--include-image FILE|DIRECTORY] [-k|--kernel KERNEL_FLAVOUR] [--manifest PACKAGE] [-m|--mirror URL] [-k|--keyring] [--mirror-security URL] [--packages PACKAGE|\"PACKAGES\"] [-p|--package-list LIST|FILE] [--preseed FILE] [--proxy-ftp URL] [--proxy-http URL] [--repositories NAME] [-r|--root DIRECTORY] [-s|--section SECTION|\"SECTIONS\"] [--server-address HOSTNAME|IP] [--server-path DIRECTORY] [--templates DIRECTORY] [-t|--type TYPE] [--tasks TASK]" - -Help () -{ - echo "${PROGRAM} - utility to build Debian Live systems" - echo - echo "${USAGE}" - echo "Usage: ${PROGRAM} [-h|--help]" - echo "Usage: ${PROGRAM} [-u|--usage]" - echo "Usage: ${PROGRAM} [-v|--version]" - echo - echo "Lists: gnome, gnome-core, gnome-full, kde, kde-core, kde-core-i18n, kde-extra, kde-extra-i18n, kde-full, kde-full-i18n, kde-i18n, standard, standard-i18n, x11, x11-core, xfce." - echo - echo "Values:" - echo " Architectures: alpha, amd64, arm, hppa, i386, ia64, m68k, powerpc, s390, sparc." - echo " Distributions: testing, unstable, experimental or etch, sid". - echo " Filesystems: ext2, plain, squashfs." - echo " Boostrap flavours: minimal, standard." - echo " Kernel flavours: Debian Kernel flavour of your architecture." - echo " Types: iso, net, usb." - echo - echo "Options:" - echo " -a, --architecture: specifies the bootstrap architecture." - echo " -b, --bootappend: specifies the kernel parameter(s)." - echo " --config: specifies an alternate configuration file." - echo " -c, --chroot: specifies the chroot directory." - echo " --clone: specifies a chroot directory to clone." - echo " -d, --distribution: specifies the debian distribution." - echo " -e, --encryption: specifies the filesystem encryption algorithm." - echo " --filesystem: specifies the chroot filesystem." - echo " -f, --flavour: specifies the bootstrap flavour." - echo " --bootstrap-config: specifies the suite configuration to be used for bootstraping." - echo " --hook: specifies extra command(s)." - echo " --include-chroot: specifies file or directory for chroot inclusion." - echo " --include-image: specifies file or directory for image inclusion." - echo " -k, --kernel: specifies debian kernel flavour." - echo " --manifest: specifies the pivot package to create filesystem.manifest-desktop upon (mostly \"ubuntu-live\")." - echo " -m, --mirror: specifies debian mirror." - echo " --mirror-security: specifies debian security mirror." - echo " --keyring: specifies keyring package." - echo " --packages: specifies aditional packages." - echo " -p, --package-list: specifies additonal package list." - echo " --repositories: specifies custom repositories." - echo " -r, --root: specifies build root." - echo " --preseed: specifies a debconf preseeding file." - echo " --proxy-ftp: specifies \${ftp_proxy}." - echo " --proxy-http: specifies \${http_proxy}." - echo " -s, --section: specifies the debian sections." - echo " --server-address: specifies the netboot server address." - echo " --server-path: specifies the netboot server path for chroot." - echo " --templates: specifies location of the templates." - echo " -t, --type: specifies live system type." - echo " --tasks: specifies one or more aptitude tasks." - echo " --with-generic-indices: enables generic debian package indices (default)." - echo " --without-generic-indices: disables generic debian package indices." - echo " --with-recommends: installes recommended packages too." - echo " --without-recommends: does not install recommended packages (default)." - echo " --with-daemons: don't touch daemons." - echo " --without-daemons: disable all non-essential daemons." - echo - echo "Environment:" - echo " All settings can be also specified trough environment variables. Please see make-live.conf(5) for more information." - echo - echo "Report bugs to Debian Live project ." - exit 0 -} - -Usage () -{ - echo "${PROGRAM} - utility to build Debian Live systems" - echo - echo "${USAGE}" - echo "Usage: ${PROGRAM} [-h|--help]" - echo "Usage: ${PROGRAM} [-u|--usage]" - echo "Usage: ${PROGRAM} [-v|--version]" - echo - echo "Try \"${PROGRAM} --help\" for more information." - exit ${1} -} - -Version () -{ - echo "${PROGRAM}, version ${VERSION}" - echo - echo "Copyright (C) 2006 Daniel Baumann " - echo "Copyright (C) 2006 Marco Amadori " - 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 "You should have received a copy of the GNU General Public License" - echo "along with this program; if not, write to the Free Software" - echo "Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA" - echo - echo "On Debian systems, the complete text of the GNU General Public License" - echo "can be found in /usr/share/common-licenses/GPL file." - echo - echo "Homepage: " - exit 0 -} - -Configuration () -{ - # Source default configuration - if [ -r "${CONFIG}" ] - then - . "${CONFIG}" - fi - - # Source alternate configuration - if [ -n "${LIVE_CONFIG}" ] - then - if [ -r "${LIVE_CONFIG}" ] - then - . "${LIVE_CONFIG}" - fi - fi -} - -Main () -{ - ARGUMENTS="`getopt --longoptions root:,tasks:,type:,architecture:,bootappend:,clone:,config:,chroot:,distribution:,encryption:,filesystem:,flavour:,bootstrap-config:,hook:,include-chroot:,include-image:,kernel:,manifest:,mirror:,keyring:,mirror-security:,output:,packages:,package-list:,proxy-ftp:,preseed:,proxy-http:,repositories:,section:,server-address:,server-path:,templates:,with-generic-indices,without-generic-indices,with-recommends,without-recommends,with-daemons,without-daemons,with-source,without-source,help,usage,version --name=${PROGRAM} --options r:t:a:b:c:d:e:f:k:m:o:p:s:huv --shell sh -- "${@}"`" - - if [ "${?}" != "0" ] - then - echo "Terminating." >&2 - exit 1 - fi - - eval set -- "${ARGUMENTS}" - - while true - do - case "${1}" in - -r|--root) - LIVE_ROOT="${2}"; shift 2 - export LIVE_ROOT - ;; - - -t|--type) - LIVE_TYPE="${2}"; shift 2 - export LIVE_TYPE - ;; - - --tasks) - LIVE_TASKS="${2}"; shift 2 - export LIVE_TASKS - ;; - - -a|--architecture) - LIVE_ARCHITECTURE="${2}"; shift 2 - export LIVE_ARCHITECTURE - ;; - - -b|--bootappend) - LIVE_BOOTAPPEND="${2}"; shift 2 - export LIVE_BOOTAPPEND - ;; - - --clone) - LIVE_CLONE="${2}"; shift 2 - export LIVE_CLONE - ;; - - --config) - LIVE_CONFIG="${2}"; shift 2 - export LIVE_CONFIG - ;; - - -c|--chroot) - LIVE_CHROOT="${2}"; shift 2 - export LIVE_CHROOT - ;; - - -d|--distribution) - LIVE_DISTRIBUTION="${2}"; shift 2 - export LIVE_DISTRIBUTION - ;; - - -e|--encryption) - LIVE_ENCRYPTION="${2}"; shift 2 - export LIVE_ENCRYPTION - ;; - - --filesystem) - LIVE_FILESYSTEM="${2}"; shift 2 - export LIVE_FILESYSTEM - ;; - - -f|--flavour) - LIVE_FLAVOUR="${2}"; shift 2 - export LIVE_FLAVOUR - ;; - --bootstrap-config) - LIVE_BOOTSTRAP_CONFIG="${2}"; shift 2 - export LIVE_BOOTSTRAP_CONFIG - ;; - --hook) - LIVE_HOOK="${2}"; shift 2 - export LIVE_HOOK - ;; - - --include-chroot) - LIVE_INCLUDE_CHROOT="${2}"; shift 2 - export LIVE_INCLUDE_CHROOT - ;; - - --include-image) - LIVE_INCLUDE_IMAGE="${2}"; shift 2 - export LIVE_INCLUDE_IMAGE - ;; - - -k|--kernel) - LIVE_KERNEL="${2}"; shift 2 - export LIVE_KERNEL - ;; - - --manifest) - LIVE_MANIFEST="${2}"; shift 2 - export LIVE_MANIFEST - ;; - - -m|--mirror) - LIVE_MIRROR="${2}"; shift 2 - export LIVE_MIRROR - ;; - - --keyring) - LIVE_REPOSITORY_KEYRING="${2}"; shift 2 - export LIVE_REPOSITORY_KEYRING - ;; - - --mirror-security) - LIVE_MIRROR_SECURITY="${2}"; shift 2 - export LIVE_MIRROR_SECURITY - ;; - - -o|--output) - LIVE_IMAGE="${2}"; shift 2 - export LIVE_IMAGE - ;; - - --packages) - LIVE_PACKAGES="${2}"; shift 2 - export LIVE_PACKAGES - ;; - - -p|--package-list) - LIVE_PACKAGE_LIST="${2}"; shift 2 - export LIVE_PACKAGE_LIST - ;; - - --preseed) - LIVE_PRESEED="${2}"; shift 2 - export LIVE_PRESEED - ;; - - --proxy-ftp) - LIVE_PROXY_FTP="${2}"; shift 2 - export LIVE_PROXY_FTP - ;; - - --proxy-http) - LIVE_PROXY_HTTP="${2}"; shift 2 - export LIVE_PROXY_HTTP - ;; - - --repositories) - LIVE_REPOSITORIES="${2}"; shift 2 - export LIVE_REPOSITORIES - ;; - - -s|--section) - LIVE_SECTION="${2}"; shift 2 - export LIVE_SECTION - ;; - - --server-address) - LIVE_SERVER_ADDRESS="${2}"; shift 2 - export LIVE_SERVER_ADDRESS - ;; - - --server-path) - LIVE_SERVER_PATH="${2}"; shift 2 - export LIVE_SERVER_PATH - ;; - - --templates) - LIVE_TEMPLATES="${2}"; shift 2 - export LIVE_TEMPLATES - ;; - - --with-generic-indices) - LIVE_GENERIC_INDICES="yes"; shift - export LIVE_GENERIC_INDICES - ;; - - --without-generic-indices) - LIVE_GENERIC_INDICES="no"; shift - export LIVE_GENERIC_INDIDCES - ;; - - --with-recommends) - LIVE_RECOMMENDS="yes"; shift - export LIVE_RECOMMENDS - ;; - - --without-recommends) - LIVE_RECOMMENDS="no"; shift - export LIVE_RECOMMENDS - ;; - - --with-daemons) - LIVE_DAEMONS="yes"; shift - export LIVE_DAEMONS - ;; - - --without-daemons) - LIVE_DAEMONS="no"; shift - export LIVE_DEAMONS - ;; - - --with-source) - LIVE_SOURCE="yes"; shift - export LIVE_SOURCE - ;; - - --without-source) - LIVE_SOURCE="no"; shift - export LIVE_SOURCE - ;; - - -h|--help) - Help; shift - ;; - - -u|--usage) - Usage 0; shift - ;; - - -v|--version) - Version; shift - ;; - - --) - shift; break - ;; - - *) - echo "Internal error." - exit 1 - ;; - esac - done - - # Initialising - lh_testroot - Configuration - Defaults - - # Building live system - lh_cdebootstrap - Chroot - - # Building live image - lh_buildbinary - lh_buildsource -} - -Main "${@}" diff --git a/src/scripts/02defaults.sh b/src/scripts/02defaults.sh deleted file mode 100644 index 06e7c96..0000000 --- a/src/scripts/02defaults.sh +++ /dev/null @@ -1,376 +0,0 @@ -#!/bin/sh - -# make-live - utility to build Debian Live systems -# -# Copyright (C) 2006 Daniel Baumann -# Copyright (C) 2006 Marco Amadori -# -# make-live comes with ABSOLUTELY NO WARRANTY; for details see COPYING. -# This is free software, and you are welcome to redistribute it -# under certain conditions; see COPYING for details. - -Defaults () -{ - # Set root directory - if [ -z "${LIVE_ROOT}" ] - then - LIVE_ROOT="`pwd`/debian-live" - fi - - export LIVE_ROOT - - # Set image type - if [ -n "${LIVE_TYPE}" ] - then - case "${LIVE_TYPE}" in - iso) - LIVE_TYPE="Iso" - ;; - - net) - LIVE_TYPE="Net" - ;; - - usb) - LIVE_TYPE="Usb" - ;; - - *) - echo "E: image type wrong or not yet supported." - Usage 1 - ;; - esac - else - LIVE_TYPE="Iso" - fi - - export LIVE_TYPE - - # Set bootstrap architecture - if [ -z "${LIVE_ARCHITECTURE}" ] - then - LIVE_ARCHITECTURE="`dpkg --print-architecture`" - fi - - export LIVE_ARCHITECTURE - - # Set chroot directory - if [ -z "${LIVE_CHROOT}" ] - then - LIVE_CHROOT="${LIVE_ROOT}/chroot" - fi - - export LIVE_CHROOT - - # Set debian distribution - if [ -z "${LIVE_DISTRIBUTION}" ] - then - LIVE_DISTRIBUTION="unstable" - fi - - if [ "${LIVE_DISTRIBUTION}" = "experimental" ] - then - LIVE_DISTRIBUTION="unstable" - LIVE_DISTRIBUTION_EXPERIMENTAL="yes" - fi - - export LIVE_DISTRIBUTION - export LIVE_DISTRIBUTION_EXPERIMENTAL - - # Set bootstrap flavour - if [ -z "${LIVE_FLAVOUR}" ] - then - LIVE_FLAVOUR="standard" - fi - - export LIVE_FLAVOUR - - # Set filesystem - if [ -z "${LIVE_FILESYSTEM}" ] && [ "${LIVE_TYPE}" = "Iso" ] - then - LIVE_FILESYSTEM="squashfs" - elif [ -z "${LIVE_FILESYSTEM}" ] && [ "${LIVE_TYPE}" = "Usb" ] - then - LIVE_FILESYSTEM="squashfs" - elif [ -z "${LIVE_FILESYSTEM}" ] && [ "${LIVE_TYPE}" = "Net" ] - then - LIVE_FILESYSTEM="plain" - fi - - export LIVE_FILESYSTEM - - # Set kernel flavour - if [ -z "${LIVE_KERNEL}" ] - then - case "${LIVE_ARCHITECTURE}" in - alpha) - LIVE_KERNEL="alpha-generic" - ;; - - amd64) - LIVE_KERNEL="amd64" - ;; - - arm) - echo "E: You need to specify the linux kernel flavour manually on arm." - exit 1 - ;; - - hppa) - LIVE_KERNEL="parisc" - ;; - - i386) - if [ "${LIVE_DISTRIBUTION}" = "oldstable" ] || [ "${LIVE_DISTRIBUTION}" = "${CODENAME_OLDSTABLE}" ] || \ - [ "${LIVE_DISTRIBUTION}" = "stable" ] || [ "${LIVE_DISTRIBUTION}" = "${CODENAME_STABLE}" ] - then - LIVE_KERNEL="386" - else - LIVE_KERNEL="486" - fi - ;; - - ia64) - LIVE_KERNEL="itanium" - ;; - - m68k) - echo "E: You need to specify the linux kernel flavour manually on m68k." - exit 1 - ;; - - powerpc) - LIVE_KERNEL="powerpc" - ;; - - s390) - LIVE_KERNEL="s390" - ;; - - sparc) - LIVE_KERNEL="sparc32" - ;; - - *) - echo "FIXME: Architecture not yet supported." - Usage 1 - ;; - esac - fi - - export LIVE_KERNEL - - # Set kernel packages - if [ -z "${LIVE_KERNEL_PACKAGES}" ] - then - LIVE_KERNEL_PACKAGES="linux-image-2.6-${LIVE_KERNEL} squashfs-modules-2.6-${LIVE_KERNEL} unionfs-modules-2.6-${LIVE_KERNEL}" - - if [ -n "${LIVE_ENCRYPTION}" ] - then - LIVE_KERNEL_PACKAGES="${LIVE_KERNEL_PACKAGES} loop-aes-modules-2.6-${LIVE_KERNEL} loop-aes-utils" - fi - - fi - - export LIVE_KERNEL_PACKAGES - - # Set debian mirror - if [ -z "${LIVE_MIRROR}" ] - then - LIVE_MIRROR="http://ftp.debian.org/debian/" - fi - - export LIVE_MIRROR - - # Set debian keyring - if [ -z "${LIVE_REPOSITORY_KEYRING}" ] - then - LIVE_REPOSITORY_KEYRING="debian-archive-keyring" - fi - - export LIVE_REPOSITORY_KEYRING - - # Set debian security mirror - if [ -z "${LIVE_MIRROR_SECURITY}" ] - then - LIVE_MIRROR_SECURITY="http://security.debian.org/" - fi - - export LIVE_MIRROR_SECURITY - - # Set default aptitude tasks - if [ "${LIVE_PACKAGE_LIST}" = "gnome-desktop" ] - then - LIVE_PACKAGE_LIST="gnome" - LIVE_TASKS="${LIVE_TASKS} standard laptop desktop gnome-desktop" - elif [ "${LIVE_PACKAGE_LIST}" = "kde-desktop" ] - then - LIVE_PACKAGE_LIST="kde" - LIVE_TASKS="${LIVE_TASKS} standard laptop desktop kde-desktop" - elif [ "${LIVE_PACKAGE_LIST}" = "xfce-desktop" ] - then - LIVE_PACKAGE_LIST="xfce" - LIVE_TASKS="${LIVE_TASKS} standard laptop desktop xfce-desktop" - fi - - export LIVE_PACKAGE_LIST LIVE_TASKS - - # Check for package lists - if [ -z "${LIVE_PACKAGE_LIST}" ] - then - if [ "${LIVE_FLAVOUR}" = "minimal" ] - then - LIVE_PACKAGE_LIST="${BASE}/lists/minimal" - elif [ "${LIVE_FLAVOUR}" = "mini" ] - then - LIVE_PACKAGE_LISTS="${BASE}/lists/mini" - else - LIVE_PACKAGE_LIST="${BASE}/lists/standard" - fi - else - if [ "${LIVE_PACKAGE_LIST}" != "everything" ] - then - if [ ! -r "${LIVE_PACKAGE_LIST}" ] - then - if [ -r "${BASE}/lists/${LIVE_PACKAGE_LIST}" ] - then - LIVE_PACKAGE_LIST="${BASE}/lists/${LIVE_PACKAGE_LIST}" - else - LIVE_PACKAGE_LIST="${BASE}/lists/standard" - fi - fi - fi - fi - - export LIVE_PACKAGE_LIST - - if [ -n "${LIVE_PACKAGES}" ] - then - export LIVE_PACKAGES - fi - - # Set FTP proxy - if [ -z "${LIVE_PROXY_FTP}" ] && [ -n "${ftp_proxy}" ] - then - LIVE_PROXY_FTP="${ftp_proxy}" - export LIVE_PROXY_FTP - else - if [ -n "${LIVE_PROXY_FTP}" ] && [ "${LIVE_PROXY_FTP}" != "${ftp_proxy}" ] - then - ftp_proxy="${LIVE_PROXY_FTP}" - export ftp_proxy - fi - fi - - # Set HTTP proxy - if [ -z "${LIVE_PROXY_HTTP}" ] && [ -n "${http_proxy}" ] - then - LIVE_PROXY_HTTP="${http_proxy}" - export LIVE_PROXY_HTTP - else - if [ -n "${LIVE_PROXY_HTTP}" ] && [ "${LIVE_PROXY_HTTP}" != "${http_proxy}" ] - then - http_proxy="${LIVE_PROXY_HTTP}" - export http_proxy - fi - fi - - # Set debian sections - if [ -z "${LIVE_SECTIONS}" ] - then - LIVE_SECTIONS="main" - fi - - export LIVE_SECTIONS - - # Set netboot server - if [ -z "${LIVE_SERVER_ADDRESS}" ] - then - LIVE_SERVER_ADDRESS="192.168.1.1" - fi - - export LIVE_SERVER_ADDRESS - - # Set netboot path - if [ -z "${LIVE_SERVER_PATH}" ] - then - LIVE_SERVER_PATH="/srv/debian-live" - fi - - export LIVE_SERVER_PATH - - # Set templates directory - if [ -z "${LIVE_TEMPLATES}" ] - then - LIVE_TEMPLATES="${BASE}/templates" - fi - - export LIVE_TEMPLATES - - # Set package indices - if [ -z "${LIVE_GENERIC_INDICES}" ] && [ "${LIVE_FLAVOUR}" != "minimal" ] && [ "${LIVE_FLAVOUR}" != "mini" ] - then - LIVE_GENERIC_INDICES="yes" - fi - - export LIVE_GENERIC_INDICES - - # Set recommends - if [ -z "${LIVE_RECOMMENDS}" ] - then - LIVE_RECOMMENDS="no" - fi - - export LIVE_RECOMMENDS - - # Set source image - if [ -z "${LIVE_SOURCE}" ] - then - LIVE_SOURCE="no" - fi - - export LIVE_SOURCE - - # Set disk volume - if [ -z "${LIVE_DISK_VOLUME}" ] - then - LIVE_DISK_VOLUME="Debian Live `date +%Y%m%d`" - fi - - export LIVE_DISK_VOLUME - - if [ -z "${LIVE_DEBCONF_FRONTEND}" ] - then - LIVE_DEBCONF_FRONTEND="noninteractive" - fi - - export LIVE_DEBCONF_FRONTEND - - if [ -z "${LIVE_DEBCONF_PRIORITY}" ] - then - LIVE_DEBCONF_PRIORITY="critical" - fi - - export LIVE_DEBCONF_PRIORITY - - if [ -z "${LIVE_DAEMONS}" ] - then - LIVE_DAEMONS="yes" - fi - - export LIVE_DAEMONS - - # This is a hack because Ubuntu does not ship cdrkit already - if [ -x /usr/bin/genisoimage ] - then - GENISOIMAGE="/usr/bin/genisoimage" - else - GENISOIMAGE="/usr/bin/mkisofs" - fi - - export GENISOIMAGE - - # Variables that do not have defaults but need to be exported to - # allow other helpers to use their values - export LIVE_BOOTAPPEND LIVE_BOOTSTRAP_CONFIG LIVE_INCLUDE_CHROOT LIVE_PRESEED LIVE_ISOLINUX_SPLASH -} diff --git a/src/scripts/13chroot.sh b/src/scripts/13chroot.sh deleted file mode 100644 index f06cf4d..0000000 --- a/src/scripts/13chroot.sh +++ /dev/null @@ -1,106 +0,0 @@ -#!/bin/sh - -# make-live - utility to build Debian Live systems -# -# Copyright (C) 2006 Daniel Baumann -# Copyright (C) 2006 Marco Amadori -# -# make-live comes with ABSOLUTELY NO WARRANTY; for details see COPYING. -# This is free software, and you are welcome to redistribute it -# under certain conditions; see COPYING for details. - -Chroot () -{ - if [ ! -f "${LIVE_ROOT}"/.stage/chroot ] - then - # Configure chroot - lh_patchchroot apply - lh_patchrunlevel apply - - # Configure network - lh_patchnetwork apply - - # Mount proc - mount proc-live -t proc "${LIVE_CHROOT}"/proc - - # Configure sources.list - lh_setupapt custom initial - lh_configapt apply-proxy - lh_configapt apply-recommends - - # Install aptitude - lh_installapt - - # Update indices - lh_chroot "aptitude update" - - # Configure linux-image - lh_patchlinux apply - - # Install linux-image, modules and casper - lh_chroot "aptitude install --assume-yes ${LIVE_KERNEL_PACKAGES} casper" - - # Deconfigure linux-image - lh_patchlinux deapply - - lh_clone - lh_preseed - - lh_installtasks - lh_installpackagelists - lh_installpackages - lh_includechroot - lh_hook - - # Save package list - lh_chroot "dpkg --get-selections" > "${LIVE_ROOT}"/packages.txt - - lh_config disable-daemons - - lh_manifest - - lh_cleanapt - - # Workaround binfmt-support /proc locking - umount "${LIVE_CHROOT}"/proc/sys/fs/binfmt_misc > /dev/null || true - - # Unmount proc - umount "${LIVE_CHROOT}"/proc - - # Deconfigure network - lh_patchnetwork deapply - - # Deconfigure chroot - lh_patchrunlevel deapply - lh_patchchroot deapply - - # Touching stage file - touch "${LIVE_ROOT}"/.stage/chroot - fi - - # Check depends - if [ "`grep dosfstools ${LIVE_ROOT}/packages.txt`" ] - then - KEEP_DOSFSTOOLS="true" - fi - - if [ "`grep memtest86+ ${LIVE_ROOT}/packages.txt`" ] - then - KEEP_MEMTEST86="true" - fi - - if [ "`grep mtools ${LIVE_ROOT}/packages.txt`" ] - then - KEEP_MTOOLS="true" - fi - - if [ "`grep parted ${LIVE_ROOT}/packages.txt`" ] - then - KEEP_PARTED="true" - fi - - if [ "`grep syslinux ${LIVE_ROOT}/packages.txt`" ] - then - KEEP_SYSLINUX="true" - fi -} diff --git a/templates/common/README.html b/templates/common/README.html deleted file mode 100644 index 33565f3..0000000 --- a/templates/common/README.html +++ /dev/null @@ -1,660 +0,0 @@ - - - - - Debian GNU/Linux -- The Universal Operating System - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -Debian -
- - - - - - - - - - - - - - - - - - -
- - - - - -
-
   - - - - Debian GNU/Linux testing "Etch" - Official Snapshot i386 Binary-1 CD -   
-
- -		 - -
- - - -
- - - - - -
- - - - - - - - - - - - - - - - - - -
- - -
   - - - - -

Debian home page

- - - 
-

- - - - - - - - - - - - - -Intro -

- - - - - -About This CD -

- - - - - -Installing -

- - - - - - -Last-Minute Notes -

- - - - - - - - Using CDs with apt -

- - - - - - - -CD Manufacturers -

- - - - - - -More Information - -

- - - 

-Browse this CD-ROM

-

-                -

- - - - - - - - - - - - 		     - -
- -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 - - - -for more information. -

- - - - - - -Read more... - - - - - - -

- -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:

- -

- - - - - - - - - -

-Also on the Internet are many resources. To name a few: -

- -

- -

- -

- - - - - - -
- - -See the Debian -contact page - - - - - -for information on contacting us. -

- - -Last Modified: Sat Mar 20 12:30:45 EST 2004 - -
 -

- -
- - -
- - - diff --git a/templates/common/README.mirrors.html b/templates/common/README.mirrors.html deleted file mode 100644 index b16637b..0000000 --- a/templates/common/README.mirrors.html +++ /dev/null @@ -1,746 +0,0 @@ - - - - Debian worldwide mirror sites - - - -

Debian worldwide mirror sites

-

Debian is distributed (mirrored) on hundreds of -servers on the Internet. Using a nearby server will probably speed up your -download, and also reduce the load on our central servers and on the -Internet as a whole. - -

Debian mirrors can be primary and secondary. The definitions are as follows: - -

- A primary mirror site has good bandwidth, is available 24 hours a day, - and has an easy to remember name of the form ftp.<country>.debian.org. -
- 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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CountrySiteDebian archiveArchitectures
Austriaftp.at.debian.org/debian/alpha arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc
Australiaftp.au.debian.org/debian/all
Australiaftp.wa.au.debian.org/debian/all
Bulgariaftp.bg.debian.org/debian/!hppa !hurd-i386 !s390
Brazilftp.br.debian.org/debian/all
Switzerlandftp.ch.debian.org/debian/all
Chileftp.cl.debian.org/debian/all
Czech Republicftp.cz.debian.org/debian/all
Germanyftp.de.debian.org/debian/all
Germanyftp2.de.debian.org/debian/all
Estoniaftp.ee.debian.org/debian/all
Spainftp.es.debian.org/debian/all
Finlandftp.fi.debian.org/debian/all
Franceftp.fr.debian.org/debian/all
Franceftp2.fr.debian.org/debian/all
Great Britainftp.uk.debian.org/debian/all
Hong Kongftp.hk.debian.org/debian/all
Croatiaftp.hr.debian.org/debian/all
Hungaryftp.hu.debian.org/debian/all
Irelandftp.ie.debian.org/debian/all
Icelandftp.is.debian.org/debian/all
Italyftp.it.debian.org/debian/all
Japanftp.jp.debian.org/debian/all
Japanftp2.jp.debian.org/debian/all
Koreaftp.kr.debian.org/debian/all
Netherlandsftp.nl.debian.org/debian/all
Norwayftp.no.debian.org/debian/!m68k
New Zealandftp.nz.debian.org/debian/all
Polandftp.pl.debian.org/debian/all
Romaniaftp.ro.debian.org/debian/all
Russiaftp.ru.debian.org/debian/all
Swedenftp.se.debian.org/debian/all
Sloveniaftp.si.debian.org/debian/alpha i386 ia64 m68k sparc
Slovakiaftp.sk.debian.org/debian/all
Turkeyftp.tr.debian.org/debian/all
United Statesftp.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 2006Number of sites listed: 330
- - diff --git a/templates/common/README.mirrors.txt b/templates/common/README.mirrors.txt deleted file mode 100644 index 286f181..0000000 --- a/templates/common/README.mirrors.txt +++ /dev/null @@ -1,541 +0,0 @@ - Debian worldwide mirror sites - ----------------------------- - -Debian is distributed (mirrored) on hundreds of -servers on the Internet. Using a nearby server will probably speed up your -download, and also reduce the load on our central servers and on the -Internet as a whole. - -Debian mirrors can be primary and secondary. The definitions are as follows: - - A primary mirror site has good bandwidth, is available 24 hours a day, - and has an easy to remember name of the form ftp..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 diff --git a/templates/common/README.txt b/templates/common/README.txt deleted file mode 100644 index b847f71..0000000 --- a/templates/common/README.txt +++ /dev/null @@ -1,164 +0,0 @@ - - (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 diff --git a/templates/common/doc/00-INDEX b/templates/common/doc/00-INDEX deleted file mode 100644 index 041eaca..0000000 --- a/templates/common/doc/00-INDEX +++ /dev/null @@ -1,22 +0,0 @@ -What's in /debian/doc? - ---- General Documentation -FAQ/ Debian FAQ List in html, postscript, and plain text -constitution.txt Debian Constitution -debian-manifesto How it all started... -mailing-lists.txt How to subscribe to the Debian mailing lists -social-contract.txt Debian Social Contract and Free Software Guidelines -source-unpack.txt How to unpack a Debian source package -debian-keyring.tar.gz PGP keys of all the developers. - - ---- The Bug Tracking System for users -bug-reporting.txt How to report a bug in Debian -bug-log-mailserver.txt Introduction to the bug system request server -bug-log-access.txt Accessing bug reports in the tracking system -bug-mailserver-refcard.txt Mail server's reference card - - ---- Debian Developer's Information -bug-maint-info.txt Developer's information re the bug system -bug-maint-mailcontrol.txt Introduction to the bug control mailserver diff --git a/templates/common/doc/FAQ/debian-faq.en.html.tar.gz b/templates/common/doc/FAQ/debian-faq.en.html.tar.gz deleted file mode 100644 index d85f3d0..0000000 Binary files a/templates/common/doc/FAQ/debian-faq.en.html.tar.gz and /dev/null differ diff --git a/templates/common/doc/FAQ/debian-faq.en.pdf.gz b/templates/common/doc/FAQ/debian-faq.en.pdf.gz deleted file mode 100644 index c8aa37b..0000000 Binary files a/templates/common/doc/FAQ/debian-faq.en.pdf.gz and /dev/null differ diff --git a/templates/common/doc/FAQ/debian-faq.en.ps.gz b/templates/common/doc/FAQ/debian-faq.en.ps.gz deleted file mode 100644 index 86aa67f..0000000 Binary files a/templates/common/doc/FAQ/debian-faq.en.ps.gz and /dev/null differ diff --git a/templates/common/doc/FAQ/debian-faq.en.txt.gz b/templates/common/doc/FAQ/debian-faq.en.txt.gz deleted file mode 100644 index ecb1b1a..0000000 Binary files a/templates/common/doc/FAQ/debian-faq.en.txt.gz and /dev/null differ diff --git a/templates/common/doc/FAQ/html/ch-basic_defs.en.html b/templates/common/doc/FAQ/html/ch-basic_defs.en.html deleted file mode 100644 index 7425706..0000000 --- a/templates/common/doc/FAQ/html/ch-basic_defs.en.html +++ /dev/null @@ -1,431 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Definitions and overview - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 1 - Definitions and overview -

- -
- -

1.1 What is this FAQ?

- -

-This document gives frequently asked questions (with their answers!) about the -Debian distribution (Debian GNU/Linux and others) and about the Debian project. -If applicable, pointers to other documentation will be given: we won't quote -large parts of external documentation in this document. You'll find out that -some answers assume some knowledge of Unix-like operating systems. We'll try -to assume as little prior knowledge as possible: answers to general beginners -questions will be kept simple. -

- -

-If you can't find what you're looking for in this FAQ, be sure to check out What other documentation exists on and -for a Debian system?, Section 11.1. If even that doesn't help, refer to Feedback, Section 15.2. -

- -
- -

1.2 What is Debian GNU/Linux?

- -

-Debian GNU/Linux is a particular distribution of the Linux operating -system, and numerous packages that run on it. -

- -

-In principle, users could obtain the Linux kernel via the Internet or from -elsewhere, and compile it themselves. They could then obtain source code for -many applications in the same way, compile the programs, then install them into -their systems. For complicated programs, this process can be not only -time-consuming but error-prone. To avoid it, users often choose to obtain the -operating system and the application packages from one of the Linux -distributors. What distinguishes the various Linux distributors are the -software, protocols, and practices they use for packaging, installing, and -tracking applications packages on users' systems, combined with installation -and maintenance tools, documentation, and other services. -

- -

-Debian GNU/Linux is the result of a volunteer effort to create a free, -high-quality Unix-compatible operating system, complete with a suite of -applications. The idea of a free Unix-like system originates from the GNU -project, and many of the applications that make Debian GNU/Linux so useful were -developed by the GNU project. -

- -

-For Debian, free has the GNUish meaning (see the Debian Free Software -Guidelines). When we speak of free software, we are referring to -freedom, not price. Free software means that you have the freedom to -distribute copies of free software, that you receive source code or can get it -if you want it, that you can change the software or use pieces of it in new -free programs; and that you know you can do these things. -

- -

-The Debian Project was created by Ian Murdock in 1993, initially under the -sponsorship of the Free Software Foundation's GNU project. Today, Debian's -developers think of it as a direct descendent of the GNU project. -

- -

-Debian GNU/Linux is: -

-
    -
  • -

    -full featured: 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 mirror sites. -

    -
    • -
-
    -
  • -

    -free to use and redistribute: 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. -

    - -

    -The Debian FTP archives also carry approximately 450 software packages (in the -non-free and contrib sections), which are -distributable under specific terms included with each package. -

    -
    • -
-
    -
  • -

    -dynamic: 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. -

    -
    • -
- -

-Although Debian GNU/Linux itself is free software, it is a base upon which -value-added Linux distributions can be built. By providing a reliable, -full-featured base system, Debian provides Linux users with increased -compatibility, and allows Linux distribution creators to eliminate duplication -of effort and focus on the things that make their distribution special. See I am making a special Linux -distribution for a "vertical market". Can I use Debian GNU/Linux for -the guts of a Linux system and add my own applications on top of it?, Section -13.3 for more information. -

- -
- -

1.3 OK, now I know what Debian is... what is Linux?!

- -

-In short, Linux is the kernel of a Unix-like operating system. It was -originally designed for 386 (and better) PCs; today Linux also runs on a dozen -of other systems. Linux is written by Linus Torvalds and many computer -scientists around the world. -

- -

-Besides its kernel, a "Linux" system usually has: -

- -
    -
  • -

    -a wide range of Unix utilities, many of which have been developed by the GNU -project and the Free Software Foundation. -

    -
    • -
- -

-The combination of the Linux kernel, the file system, the GNU and FSF -utilities, and the other utilities are designed to achieve compliance with the -POSIX (IEEE 1003.1) standard; see How -source code compatible is Debian with other Unix systems?, Section 3.3. -

- -

-For more information about Linux, see Michael K. Johnson's Linux Information -Sheet and Meta-FAQ. -

- -
- -

1.4 Does Debian just do GNU/Linux?

- -

-Currently, Debian is only available for Linux, but with Debian GNU/Hurd and -Debian on BSD kernels, we have started to offer non-Linux-based OSes as a -development, server and desktop platform, too. However, these non-linux ports -are not officially released yet. -

- -

-The oldest porting effort is Debian GNU/Hurd. -

- -

-The Hurd is a set of servers running on top of the GNU Mach microkernel. -Together they build the base for the GNU operating system. -

- -

-Please see http://www.gnu.org/software/hurd/ -for more information about the GNU/Hurd in general, and http://www.debian.org/ports/hurd/ -for more information about Debian GNU/Hurd. -

- -

-A second effort is the port to a BSD kernel. People are working with both the -NetBSD and the FreeBSD kernels. -

- -

-See http://www.debian.org/ports/#nonlinux -for more information about these non-linux ports. -

- -
- -

1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?

- -

-These key features distinguish Debian from other Linux distributions: -

-
-
Freedom:
-
-

-As stated in the Debian -Social Contract, Debian will remain 100% free. Debian is very -strict about shipping truly free software. The guidelines used to determine if -a work is "free" are provided in The Debian Free -Software. -

-
-
-
-
The Debian package maintenance system:
-
-

-The entire system, or any individual component of it, can be upgraded in place -without reformatting, without losing custom configuration files, and (in most -cases) without rebooting the system. Most Linux distributions available today -have some kind of package maintenance system; the Debian package maintenance -system is unique and particularly robust (see Basics of the Debian package management system, -Chapter 6). -

-
-
-
-
Open development:
-
-

-Whereas other Linux distributions are developed by individuals, small, closed -groups, or commercial vendors, Debian is the only major Linux distribution that -is being developed cooperatively by many individuals through the Internet, in -the same spirit as Linux and other free software. -

- -

-More than 1649 volunteer package maintainers are working on over 15400 packages -and improving Debian GNU/Linux. The Debian developers contribute to the -project not by writing new applications (in most cases), but by packaging -existing software according to the standards of the project, by communicating -bug reports to upstream developers, and by providing user support. See also -additional information on how to become a contributor in How can I become a Debian software -developer?, Section 12.1. -

-
-
-
-
The Universal Operating System:
-
-

-Debian comes with more than -15400 packages and runs on 11 architectures. This is far -more than is available for any other GNU/Linux distribution. See What types of applications and development -software are available for Debian GNU/Linux?, Section 4.1 for an overview -of the provided software and see On what -hardware architectures/systems does Debian GNU/Linux run?, Section 3.1 for -a description of the supported hardware platforms. -

-
-
-
-
The Bug Tracking System:
-
-

-The geographical dispersion of the Debian developers required sophisticated -tools and quick communication of bugs and bug-fixes to accelerate the -development of the system. Users are encouraged to send bugs in a formal -style, which are quickly accessible by WWW archives or via e-mail. See -additional information in this FAQ on the management of the bug log in Are there logs of known bugs?, Section -11.4. -

-
-
-
-
The Debian Policy:
-
-

-Debian has an extensive specification of our standards of quality, the Debian -Policy. This document defines the qualities and standards to which we hold -Debian packages. -

-
-
- -

-For additional information about this, please see our web page about reasons to choose -Debian. -

- -
- -

1.6 How does the Debian project fit in or compare with the Free Software Foundation's GNU project?

- -

-The Debian system builds on the ideals of free software first championed by the -Free Software Foundation and in -particular by Richard -Stallman. FSF's powerful system development tools, utilities, and -applications are also a key part of the Debian system. -

- -

-The Debian Project is a separate entity from the FSF, however we communicate -regularly and cooperate on various projects. The FSF explicitly requested that -we call our system "Debian GNU/Linux", and we are happy to comply -with that request. -

- -

-The FSF's long-standing objective is to develop a new operating system called -GNU, based on Hurd. Debian is working -with FSF on this system, called Debian GNU/Hurd. -

- -
- -

1.7 How does one pronounce Debian and what does this word mean?

- -

-The project name is pronounced Deb'-ee-en, with a short e in Deb, and emphasis -on the first syllable. This word is a contraction of the names of Debra and -Ian Murdock, who founded the project. (Dictionaries seem to offer some -ambiguity in the pronunciation of Ian (!), but Ian prefers ee'-en.) -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-basic_defs.html b/templates/common/doc/FAQ/html/ch-basic_defs.html deleted file mode 120000 index 6bee626..0000000 --- a/templates/common/doc/FAQ/html/ch-basic_defs.html +++ /dev/null @@ -1 +0,0 @@ -ch-basic_defs.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-compat.en.html b/templates/common/doc/FAQ/html/ch-compat.en.html deleted file mode 100644 index 24b527d..0000000 --- a/templates/common/doc/FAQ/html/ch-compat.en.html +++ /dev/null @@ -1,386 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Compatibility issues - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 3 - Compatibility issues -

- -
- -

3.1 On what hardware architectures/systems does Debian GNU/Linux run?

- -

-Debian GNU/Linux includes complete source-code for all of the included -programs, so it should work on all systems which are supported by the Linux -kernel; see the Linux -FAQ for details. -

- -

-The current Debian GNU/Linux release, 3.1, contains a complete, binary -distribution for the following architectures: -

- -

-i386: this covers PCs based on Intel and compatible processors, -including Intel's 386, 486, Pentium, Pentium Pro, Pentium II (both Klamath and -Celeron), and Pentium III, and most compatible processors by AMD, Cyrix and -others. -

- -

-m68k: this covers Amigas and ATARIs having a Motorola 680x0 processor -for x>=2; with MMU. -

- -

-alpha: Compaq/Digital's Alpha systems. -

- -

-sparc: this covers Sun's SPARC and most UltraSPARC systems. -

- -

-powerpc: this covers some IBM/Motorola PowerPC machines, including -CHRP, PowerMac and PReP machines. -

- -

-arm: ARM and StrongARM machines. -

- -

-mips: SGI's big-endian MIPS systems, Indy and Indigo2; -mipsel: little-endian MIPS machines, Digital DECstations. -

- -

-hppa: Hewlett-Packard's PA-RISC machines (712, C3000, L2000, A500). -

- -

-ia64: Intel IA-64 ("Itanium") computers. -

- -

-s390: IBM S/390 mainframe systems. -

- -

-The development of binary distributions of Debian for Sparc64 (UltraSPARC -native) architectures is currently underway. -

- -

-For further information on booting, partitioning your drive, enabling PCMCIA -(PC Card) devices and similar issues please follow the instructions given in -the Installation Manual, which is available from our WWW site at http://www.debian.org/releases/stable/installmanual. -

- -
- -

3.2 How compatible is Debian with other distributions of Linux?

- -

-Debian developers communicate with other Linux distribution creators in an -effort to maintain binary compatibility across Linux distributions. Most -commercial Linux products run as well under Debian as they do on the system -upon which they were built. -

- -

-Debian GNU/Linux adheres to the Linux Filesystem Hierarchy -Standard. However, there is room for interpretation in some of the -rules within this standard, so there may be slight differences between a Debian -system and other Linux systems. -

- -

-Debian GNU/Linux supports software developed for the Linux Standard Base. The LSB is a -specification for allowing the same binary package to be used on multiple -distributions. Packages for the Debian Etch release must not conflict with -requirements of the LSB, v1.3. As of this writing, Debian GNU/Linux is not -formally LSB-certified. However, some Debian derived distributions are. -Discussion and coordination of efforts towards ensuring Debian meets the -requirements of the Linux Standard Base is taking place on the debian-lsb mailing list. -

- -
- -

3.3 How source code compatible is Debian with other Unix systems?

- -

-For most applications Linux source code is compatible with other Unix systems. -It supports almost everything that is available in System V Unix systems and -the free and commercial BSD-derived systems. However in the Unix business such -claim has nearly no value because there is no way to prove it. In the software -development area complete compatibility is required instead of compatibility in -"about most" cases. So years ago the need for standards arose, and -nowadays POSIX.1 (IEEE Standard 1003.1-1990) is one of the major standards for -source code compatibility in Unix-like operating systems. -

- -

-Linux is intended to adhere to POSIX.1, but the POSIX standards cost real money -and the POSIX.1 (and FIPS 151-2) certification is quite expensive; this made it -more difficult for the Linux developers to work on complete POSIX conformance. -The certification costs make it unlikely that Debian will get an official -conformance certification even if it completely passed the validation suite. -(The validation suite is now freely available, so it is expected that more -people will work on POSIX.1 issues.) -

- -

-Unifix GmbH (Braunschweig, Germany) developed a Linux system that has been -certified to conform to FIPS 151-2 (a superset of POSIX.1). This technology -was available in Unifix' own distribution called Unifix Linux 2.0 and in -Lasermoon's Linux-FT. -

- -
- -

3.4 Can I use Debian packages (".deb" files) on my Red Hat/Slackware/... Linux system? Can I use Red Hat packages (".rpm" files) on my Debian GNU/Linux system?

- -

-Different Linux distributions use different package formats and different -package management programs. -

-
-
You probably can:
-
-

-A program to unpack a Debian package onto a Linux host that is been built from -a `foreign' distribution is available, and will generally work, in the sense -that files will be unpacked. The converse is probably also true, that is, a -program to unpack a Red Hat or Slackware package on a host that is based on -Debian GNU/Linux will probably succeed in unpacking the package and placing -most files in their intended directories. This is largely a consequence of the -existence (and broad adherence to) the Linux Filesystem Hierarchy Standard. -The Alien package -is used to convert between different package formats. -

-
-
-
-
You probably do not want to:
-
-

-Most package managers write administrative files when they are used to unpack -an archive. These administrative files are generally not standardized. -Therefore, the effect of unpacking a Debian package on a `foreign' host will -have unpredictable (certainly not useful) effects on the package manager on -that system. Likewise, utilities from other distributions might succeed in -unpacking their archives on Debian systems, but will probably cause the Debian -package management system to fail when the time comes to upgrade or remove some -packages, or even simply to report exactly what packages are present on a -system. -

-
-
-
-
A better way:
-
-

-The Linux File System Standard (and therefore Debian GNU/Linux) requires that -subdirectories under /usr/local/ be entirely under the user's -discretion. Therefore, users can unpack `foreign' packages into this -directory, and then manage their configuration, upgrade and removal -individually. -

-
-
- -
- -

3.5 Is Debian able to run my old libc5 programs?

- -

-Yes. Just install the required libc5 libraries, from the -oldlibs section (containing old packages included for -compatibility with older applications). -

- -
- -

3.6 Can Debian be used to compile libc5 programs?

- -

-Yes. Install libc5-altdev and altgcc packages (from -the oldlibs section). You can find the appropriate libc5-compiled -gcc and g++ in directory -/usr/i486-linuxlibc1/bin. Put them in your $PATH variable to get -make and other programs to execute these first. -

- -

-Be aware that libc5 environment isn't fully supported by our other packages -anymore. -

- -
- -

3.7 How should I install a non-Debian program?

- -

-Files under the directory /usr/local/ are not under the control of -the Debian package management system. Therefore, it is good practice to place -the source code for your program in /usr/local/src/. For example, you might -extract the files for a package named "foo.tar" into the directory -/usr/local/src/foo. After you compile them, place the binaries in -/usr/local/bin/, the libraries in /usr/local/lib/, -and the configuration files in /usr/local/etc/. -

- -

-If your programs and/or files really must be placed in some other directory, -you could still store them in /usr/local/, and build the -appropriate symbolic links from the required location to its location in -/usr/local/, e.g., you could make the link -

- -
-     ln -s /usr/local/bin/foo /usr/bin/foo
-
- -

-In any case, if you obtain a package whose copyright allows redistribution, you -should consider making a Debian package of it, and uploading it for the Debian -system. Guidelines for becoming a package developer are included in the Debian -Policy manual (see What other -documentation exists on and for a Debian system?, Section 11.1). -

- -
- -

3.8 Why can't I compile programs that require libtermcap?

- -

-Debian uses the terminfo database and the ncurses -library of terminal interface routes, rather than the termcap -database and the termcap library. Users who are compiling -programs that require some knowledge of the terminal interface should replace -references to libtermcap with references to -libncurses. -

- -

-To support binaries that have already been linked with the termcap -library, and for which you do not have the source, Debian provides a package -called termcap-compat. This provides both -libtermcap.so.2 and /etc/termcap. Install this -package if the program fails to run with the error message "can't load -library 'libtermcap.so.2'", or complains about a missing -/etc/termcap file. -

- -
- -

3.9 Why can't I install AccelX?

- -

-AccelX uses the termcap library for installation. See Why can't I compile programs that require libtermcap?, -Section 3.8 above. -

- -
- -

3.10 Why do my old XFree 2.1 Motif applications crash?

- -

-You need to install the motifnls package, which provides the -XFree-2.1 configuration files needed to allow Motif applications compiled under -XFree-2.1 to run under XFree-3.1. -

- -

-Without these files, some Motif applications compiled on other machines (such -as Netscape) may crash when attempting to copy or paste from or to a text -field, and may also exhibit other problems. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-compat.html b/templates/common/doc/FAQ/html/ch-compat.html deleted file mode 120000 index 0696449..0000000 --- a/templates/common/doc/FAQ/html/ch-compat.html +++ /dev/null @@ -1 +0,0 @@ -ch-compat.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-contributing.en.html b/templates/common/doc/FAQ/html/ch-contributing.en.html deleted file mode 100644 index 9ed5a56..0000000 --- a/templates/common/doc/FAQ/html/ch-contributing.en.html +++ /dev/null @@ -1,191 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Contributing to the Debian Project - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 12 - Contributing to the Debian Project -

- -
- -

-Donations of time -(to develop new packages, maintain existing packages, or provide user support), -resources (to mirror the FTP and WWW archives), and money (to pay for new -testbeds as well as hardware for the archives) can help the project. -

- -
- -

12.1 How can I become a Debian software developer?

- -

-The development of Debian is open to all, and new users with the right skills -and/or the willingness to learn are needed to maintain existing packages which -have been "orphaned" by their previous maintainers, to develop new -packages, and to provide user support. -

- -

-The description of becoming a Debian developer can be found at the New Maintainer's -Corner at the Debian web site. -

- -
- -

12.2 How can I contribute resources to the Debian project?

- -

-Since the project aims to make a substantial body of software rapidly and -easily accessible throughout the globe, mirrors are urgently needed. It is -desirable but not absolutely necessary to mirror all of the archive. Please -visit the Debian mirror -size page for information on the disk space requirements. -

- -

-Most of the mirroring is accomplished entirely automatically by scripts, -without any interaction. However, the occasional glitch or system change -occurs which requires human intervention. -

- -

-If you have a high-speed connection to the Internet, the resources to mirror -all or part of the distribution, and are willing to take the time (or find -someone) who can provide regular maintenance of the system, then please contact -debian-admin@lists.debian.org. -

- -
- -

12.3 How can I contribute financially to the Debian project?

- -

-One can make individual donations to one of two organizations that are critical -to the development of the Debian project. -

- -
- -

12.3.1 Software in the Public Interest

- -

-Software in the Public Interest (SPI) is an IRS 501(c)(3) non-profit -organization, formed when FSF withdrew their sponsorship of Debian. The -purpose of the organization is to develop and distribute free software. -

- -

-Our goals are very much like those of FSF, and we encourage programmers to use -the GNU General Public License on their programs. However, we have a slightly -different focus in that we are building and distributing a Linux system that -diverges in many technical details from the GNU system planned by FSF. We -still communicate with FSF, and we cooperate in sending them changes to GNU -software and in asking our users to donate to FSF and the GNU project. -

- -

-SPI can be reached at: http://www.spi-inc.org/. -

- -
- -

12.3.2 Free Software Foundation

- -

-At this time there is no formal connection between Debian and the Free Software -Foundation. However, the Free Software Foundation is responsible for some of -the most important software components in Debian, including the GNU C compiler, -GNU Emacs, and much of the C run-time library that is used by all programs on -the system. FSF pioneered much of what free software is today: they wrote the -General Public License that is used on much of the Debian software, and they -invented the "GNU" project to create an entirely free Unix system. -Debian should be considered a descendent of the GNU system. -

- -

-FSF can be reached at: http://www.fsf.org/. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-contributing.html b/templates/common/doc/FAQ/html/ch-contributing.html deleted file mode 120000 index 4185524..0000000 --- a/templates/common/doc/FAQ/html/ch-contributing.html +++ /dev/null @@ -1 +0,0 @@ -ch-contributing.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-customizing.en.html b/templates/common/doc/FAQ/html/ch-customizing.en.html deleted file mode 100644 index fb89888..0000000 --- a/templates/common/doc/FAQ/html/ch-customizing.en.html +++ /dev/null @@ -1,522 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Customizing your installation of Debian GNU/Linux - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 10 - Customizing your installation of Debian GNU/Linux -

- -
- -

10.1 How can I ensure that all programs use the same paper size?

- -

-Install the libpaper1 package, and it will ask you for a -system-wide default paper size. This setting will be kept in the file -/etc/papersize. -

- -

-Users can override the paper size setting using the PAPERSIZE -environment variable. For details, see the manual page -papersize(5). -

- -
- -

10.2 How can I provide access to hardware peripherals, without compromising security?

- -

-Many device files in the /dev directory belong to some predefined -groups. For example, /dev/fd0 belongs to the floppy -group, and /dev/dsp belongs to the audio group. -

- -

-If you want a certain user to have access to one of these devices, just add the -user to the group the device belongs to, i.e. do: -

- -
-     adduser user group
-
- -

-This way you won't have to change the file permissions on the device. -

- -
- -

10.3 How do I load a console font on startup the Debian way?

- -

-The kbd and console-tools packages support this, edit -/etc/kbd/config or /etc/console-tools/config files. -

- -
- -

10.4 How can I configure an X11 program's application defaults?

- -

-Debian's X programs will install their application resource data in the -/etc/X11/app-defaults/ directory. If you want to customize X -applications globally, put your customizations in those files. They are marked -as configuration files, so their contents will be preserved during upgrades. -

- -
- -

10.5 Every distribution seems to have a different boot-up method. Tell me about Debian's.

- -

-Like all Unices, Debian boots up by executing the program init. -The configuration file for init (which is -/etc/inittab) specifies that the first script to be executed -should be /etc/init.d/rcS. This script runs all of the scripts in -/etc/rcS.d/ by sourcing or forking subprocess depending on their -file extension to perform initialization such as to check and to mount file -systems, to load modules, to start the network services, to set the clock, and -to perform other initialization. Then, for compatibility, it runs the files -(except those with a `.'in the filename) in /etc/rc.boot/ too. -Any scripts in the latter directory are usually reserved for system -administrator use, and using them in packages is deprecated. -

- -

-After completing the boot process, init executes all start scripts -in a directory specified by the default runlevel (this runlevel is given by the -entry for id in /etc/inittab). Like most System V -compatible Unices, Linux has 7 runlevels: -

-
    -
  • -

    -0 (halt the system), -

    -
    • -
-
    -
  • -

    -1 (single-user mode), -

    -
    • -
-
    -
  • -

    -2 through 5 (various multi-user modes), and -

    -
    • -
-
    -
  • -

    -6 (reboot the system). -

    -
    • -
- -

-Debian systems come with id=2, which indicates that the default runlevel will -be '2' when the multi-user state is entered, and the scripts in -/etc/rc2.d/ will be run. -

- -

-In fact, the scripts in any of the directories, /etc/rcN.d/ are -just symbolic links back to scripts in /etc/init.d/. However, the -names of the files in each of the /etc/rcN.d/ directories -are selected to indicate the way the scripts in -/etc/init.d/ will be run. Specifically, before entering any -runlevel, all the scripts beginning with 'K' are run; these scripts kill -services. Then all the scripts beginning with 'S' are run; these scripts start -services. The two-digit number following the 'K' or 'S' indicates the order in -which the script is run. Lower numbered scripts are executed first. -

- -

-This approach works because the scripts in /etc/init.d/ all take -an argument which can be either `start', `stop', `reload', `restart' or -`force-reload' and will then do the task indicated by the argument. These -scripts can be used even after a system has been booted, to control various -processes. -

- -

-For example, with the argument `reload' the command -

- -
-     /etc/init.d/sendmail reload
-
- -

-sends the sendmail daemon a signal to reread its configuration file. (BTW, -Debian supplies invoke-rc.d as a wrapper for invoking the scripts -in /etc/init.d/.) -

- -
- -

10.6 It looks as if Debian does not use rc.local to customize the boot process; what facilities are provided?

- -

-Suppose a system needs to execute script foo on start-up, or on -entry to a particular (System V) runlevel. Then the system administrator -should: -

-
    -
  • -

    -Enter the script foo into the directory /etc/init.d/. -

    -
    • -
-
    -
  • -

    -Run the Debian command update-rc.d with appropriate arguments, to -set up links between the (command-line-specified) directories rc?.d and -/etc/init.d/foo. Here, '?' is a number from 0 through 6 and -corresponds to each of the System V runlevels. -

    -
    • -
-
    -
  • -

    -Reboot the system. -

    -
    • -
- -

-The command update-rc.d will set up links between files in the -directories rc?.d and the script in /etc/init.d/. Each link will -begin with a 'S' or a 'K', followed by a number, followed by the name of the -script. Scripts beginning with 'S' in /etc/rcN.d/ are executed -when runlevel N is entered. Scripts beginning with a 'K' are -executed when leaving runlevel N. -

- -

-One might, for example, cause the script foo to execute at -boot-up, by putting it in /etc/init.d/ and installing the links -with update-rc.d foo defaults 19. The argument 'defaults' refers -to the default runlevels, which are 2 through 5. The argument '19' ensures -that foo is called before any scripts containing numbers 20 or -larger. -

- -
- -

10.7 How does the package management system deal with packages that contain configuration files for other packages?

- -

-Some users wish to create, for example, a new server by installing a group of -Debian packages and a locally generated package consisting of configuration -files. This is not generally a good idea, because dpkg will not -know about those configuration files if they are in a different package, and -may write conflicting configurations when one of the initial "group" -of packages is upgraded. -

- -

-Instead, create a local package that modifies the configuration files of the -"group" of Debian packages of interest. Then dpkg and -the rest of the package management system will see that the files have been -modified by the local "sysadmin" and will not try to overwrite them -when those packages are upgraded. -

- -
- -

10.8 How do I override a file installed by a package, so that a different version can be used instead?

- -

-Suppose a sysadmin or local user wishes to use a program -"login-local" rather than the program "login" provided by -the Debian login package. -

- -

-Do not: -

-
    -
  • -

    -Overwrite /bin/login with login-local. -

    -
    • -
- -

-The package management system will not know about this change, and will simply -overwrite your custom /bin/login whenever login (or -any package that provides /bin/login) is installed or updated. -

- -

-Rather, do -

-
    -
  • -

    -Execute: -

    - -
    -     dpkg-divert --divert /bin/login.debian /bin/login
-
    - -

    -in order to cause all future installations of the Debian login -package to write the file /bin/login to -/bin/login.debian instead. -

    -
    • -
-
    -
  • -

    -Then execute: -

    - -
    -     cp login-local /bin/login
-
    - -

    -to move your own locally-built program into place. -

    -
    • -
- -

-Details are given in the manual page dpkg-divert(8). -

- -
- -

10.9 How can I have my locally-built package included in the list of available packages that the package management system knows about?

- -

-Execute the command: -

- -
-     dpkg-scanpackages BIN_DIR OVERRIDE_FILE [PATHPREFIX] > my_Packages
-
- -

-where: -

-
    -
  • -

    -BIN-DIR is a directory where Debian archive files (which usually have an -extension of ".deb") are stored. -

    -
    • -
-
    -
  • -

    -OVERRIDE_FILE is a file that is edited by the distribution maintainers and is -usually stored on a Debian FTP archive at indices/override.main.gz -for the Debian packages in the "main" distribution. You can ignore -this for local packages. -

    -
    • -
-
    -
  • -

    -PATHPREFIX is an optional string that can be prepended to the -my_Packages file being produced. -

    -
    • -
- -

-Once you have built the file my_Packages, tell the package -management system about it by using the command: -

- -
-     dpkg --merge-avail my_Packages
-
- -

-If you are using APT, you can add the local repository to your -sources.list(5) file, too. -

- -
- -

10.10 Some users like mawk, others like gawk; some like vim, others like elvis; some like trn, others like tin; how does Debian support diversity?

- -

-There are several cases where two packages provide two different versions of a -program, both of which provide the same core functionality. Users might prefer -one over another out of habit, or because the user interface of one package is -somehow more pleasing than the interface of another. Other users on the same -system might make a different choice. -

- -

-Debian uses a "virtual" package system to allow system administrators -to choose (or let users choose) their favorite tools when there are two or more -that provide the same basic functionality, yet satisfy package dependency -requirements without specifying a particular package. -

- -

-For example, there might exist two different versions of newsreaders on a -system. The news server package might 'recommend' that there exist -some news reader on the system, but the choice of tin or -trn is left up to the individual user. This is satisfied by -having both the tin and trn packages provide the -virtual package news-reader. Which program is invoked is -determined by a link pointing from a file with the virtual package name -/etc/alternatives/news-reader to the selected file, e.g., -/usr/bin/trn. -

- -

-A single link is insufficient to support full use of an alternate program; -normally, manual pages, and possibly other supporting files must be selected as -well. The Perl script update-alternatives provides a way of -ensuring that all the files associated with a specified package are selected as -a system default. -

- -

-For example, to check what executables provide `x-window-manager', run: -

- -
-     update-alternatives --display x-window-manager
-
- -

-If you want to change it, run: -

- -
-     update-alternatives --config x-window-manager
-
- -

-And follow the instructions on the screen (basically, press the number next to -the entry you'd like better). -

- -

-If a package doesn't register itself as a window manager for some reason (file -a bug if it's in error), or if you use a window manager from /usr/local -directory, the selections on screen won't contain your preferred entry. You -can update the link through command line options, like this: -

- -
-     update-alternatives --install /usr/bin/x-window-manager \
-       x-window-manager /usr/local/bin/wmaker-cvs 50
-
- -

-The first argument to `--install' option is the symlink that points to -/etc/alternatives/NAME, where NAME is the second argument. The third argument -is the program to which /etc/alternatives/NAME should point to, and the fourth -argument is the priority (larger value means the alternative will more probably -get picked automatically). -

- -

-To remove an alternative you added, simply run: -

- -
-     update-alternatives --remove x-window-manager /usr/local/bin/wmaker-cvs
-
- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-customizing.html b/templates/common/doc/FAQ/html/ch-customizing.html deleted file mode 120000 index 1cfdfaa..0000000 --- a/templates/common/doc/FAQ/html/ch-customizing.html +++ /dev/null @@ -1 +0,0 @@ -ch-customizing.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-faqinfo.en.html b/templates/common/doc/FAQ/html/ch-faqinfo.en.html deleted file mode 100644 index 6fdb982..0000000 --- a/templates/common/doc/FAQ/html/ch-faqinfo.en.html +++ /dev/null @@ -1,210 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - General information about the FAQ - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 15 - General information about the FAQ -

- -
- -

15.1 Authors

- -

-The first edition of this FAQ was made and maintained by J.H.M. Dassen (Ray) -and Chuck Stickelman. Authors of the rewritten Debian GNU/Linux FAQ are Susan -G. Kleinmann and Sven Rudolph. After them, the FAQ was maintained by Santiago -Vila and, later, by Josip Rodin. The current maintainer is Javier -Fernandez-Sanguino. -

- -

-Parts of the information came from: -

-
    -
  • -

    -The Debian-1.1 release announcement, by Bruce Perens. -

    -
    • -
- - - -
    -
  • -

    -many developers, volunteers, and beta testers, and -

    -
    • -
-
    -
  • -

    -the flaky memories of its authors. :-) -

    -
    • -
- -

-The authors would like to thank all those who helped make this document -possible. -

- -

-All warranties are disclaimed. All trademarks are property of their respective -trademark owners. -

- -
- -

15.2 Feedback

- -

-Comments and additions to this document are always welcome. Please send e-mail -to doc-debian@packages.debian.org, -or submit a wishlist bug report against the doc-debian package. -

- -
- -

15.3 Availability

- -

-The latest version of this document can be viewed on the Debian WWW pages at -http://www.debian.org/doc/FAQ/. -

- -

-It is also available for download in plain text, HTML, PostScript and PDF -formats at http://www.debian.org/doc/user-manuals#faq. -Also, there are several translations there. -

- -

-The original SGML files used to create this document are also available in -doc-debian's source package, or in CVS at: -:pserver:anonymous@cvs.debian.org:/cvs/debian-doc/ddp/manuals.sgml/faq -

- -
- -

15.4 Document format

- -

-This document was written using the DebianDoc SGML DTD (rewritten from LinuxDoc -SGML). DebianDoc SGML systems enables us to create files in a variety of -formats from one source, e.g. this document can be viewed as HTML, plain text, -TeX DVI, PostScript, PDF, or GNU info. -

- -

-Conversion utilities for DebianDoc SGML are available in Debian package -debiandoc-sgml. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-faqinfo.html b/templates/common/doc/FAQ/html/ch-faqinfo.html deleted file mode 120000 index 0f759b4..0000000 --- a/templates/common/doc/FAQ/html/ch-faqinfo.html +++ /dev/null @@ -1 +0,0 @@ -ch-faqinfo.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-ftparchives.en.html b/templates/common/doc/FAQ/html/ch-ftparchives.en.html deleted file mode 100644 index 0133507..0000000 --- a/templates/common/doc/FAQ/html/ch-ftparchives.en.html +++ /dev/null @@ -1,567 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - The Debian FTP archives - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 5 - The Debian FTP archives -

- -
- -

5.1 What are all those directories at the Debian FTP archives?

- -

-The software that has been packaged for Debian GNU/Linux is available in one of -several directory trees on each Debian mirror site. -

- -

-The dists directory is short for "distributions", and it -is the canonical way to access the currently available Debian releases (and -pre-releases). -

- -

-The pool directory contains the actual packages, see What's in the pool directory?, Section 5.10. -

- -

-There are the following supplementary directories: -

-
-
/tools/:
-
-

-DOS utilities for creating boot disks, partitioning your disk drive, -compressing/decompressing files, and booting Linux. -

-
-
-
-
/doc/:
-
-

-The basic Debian documentation, such as the FAQ, the bug reporting system -instructions, etc. -

-
-
-
-
/indices/:
-
-

-The Maintainers file and the override files. -

-
-
-
-
/project/:
-
-

-mostly developer-only materials, such as: -

-
-
project/experimental/:
-
-

-This directory contains packages and tools which are still being developed, and -are still in the alpha testing stage. Users shouldn't be using packages from -here, because they can be dangerous and harmful even for the most experienced -people. -

-
-
-
-
- -
- -

5.2 How many Debian distributions are there in the dists directory?

- -

-There are three distributions, the "stable" distribution, the -"testing" distribution, and the "unstable" distribution. -The "testing" distribution is sometimes `frozen' (see What about "testing"? How is it `frozen'?, Section -5.6.1). -

- -
- -

5.3 What are all those names like slink, potato, etc.?

- -

-They are just "codenames". When a Debian distribution is in the -development stage, it has no version number but a codename. The purpose of -these codenames is to make easier the mirroring of the Debian distributions (if -a real directory like unstable suddenly changed its name to -stable, a lot of stuff would have to be needlessly downloaded -again). -

- -

-Currently, stable is a symbolic link to sarge (i.e. -Debian GNU/Linux 3.1) and testing is a symbolic link to -etch. This means that sarge is the current stable -distribution and etch is the current testing distribution. -

- -

-unstable is a permanent symbolic link to sid, as -sid is always the unstable distribution (see What -about "sid"?, Section 5.4). -

- -
- -

5.3.1 Which other codenames have been used in the past?

- -

-Other codenames that have been already used are: buzz for release -1.1, rex for release 1.2, bo for releases 1.3.x, -hamm for release 2.0, slink for release 2.1, -potato for release 2.2 and woody for release 3.0. -

- -
- -

5.3.2 Where do these codenames come from?

- -

-So far they have been characters taken from the movie "Toy Story" by -Pixar. -

-
    -
  • -

    -buzz (Buzz Lightyear) was the spaceman, -

    -
    • -
-
    -
  • -

    -rex was the tyrannosaurus, -

    -
    • -
-
    -
  • -

    -bo (Bo Peep) was the girl who took care of the sheep, -

    -
    • -
-
    -
  • -

    -hamm was the piggy bank, -

    -
    • -
-
    -
  • -

    -slink (Slinky Dog (R)) was the toy dog, -

    -
    • -
-
    -
  • -

    -potato was, of course, Mr. Potato (R), -

    -
    • -
-
    -
  • -

    -woody was the cowboy, -

    -
    • -
-
    -
  • -

    -sarge was the sergeant of the Green Plastic Army Men, -

    -
    • -
-
    -
  • -

    -etch was the toy blackboard (Etch-a-Sketch (R)). -

    -
    • -
-
    -
  • -

    -sid was the boy next door who destroyed toys. -

    -
    • -
- -
- -

5.4 What about "sid"?

- -

-sid or unstable is the place where most of the packages are -initially uploaded. It will never be released directly, because packages which -are to be released will first have to be included in testing, in order -to be released in stable later on. sid contains packages for both -released and unreleased architectures. -

- -

-The name "sid" also comes from the "Toy Story" animated -motion picture: Sid was the boy next door who destroyed toys :-) -

- -

-[1] -

- -
- -

5.5 What does the stable directory contain?

-
    -
  • -

    -stable/main/: This directory contains the packages which formally constitute -the most recent release of the Debian GNU/Linux system. -

    - -

    -These packages all comply with the Debian Free Software -Guidelines, and are all freely usable and distributable. -

    -
    • -
-
    -
  • -

    -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. -

    - -

    -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). -

    -
    • -
-
    -
  • -

    -stable/contrib/: This directory contains packages which are DFSG-free and -freely distributable themselves, but somehow depend on a package that -is not freely distributable and thus available only in the non-free -section. -

    -
    • -
- -
- -

5.6 What does the testing directory contain?

- -

-Packages are installed into the `testing' directory after they have undergone -some degree of testing in unstable. -

- -

-They must be in sync on all architectures where they have been built and -mustn't have dependencies that make them uninstallable; they also have to have -fewer release-critical bugs than the versions currently in testing. This way, -we hope that `testing' is always close to being a release candidate. -

- -

-More information about the status of "testing" in general and the -individual packages is available at http://www.debian.org/devel/testing -

- -
- -

5.6.1 What about "testing"? How is it `frozen'?

- -

-When the "testing" distribution is mature enough, the release manager -starts `freezing' it. The normal propagation delays are increased to ensure -that as little as possible new bugs from "unstable" enter -"testing". -

- -

-After a while, the "testing" distribution becomes truly `frozen'. -This means that all new packages that are to propagate to the -"testing" are held back, unless they include release-critical bug -fixes. The "testing" distribution can also remain in such a deep -freeze during the so-called `test cycles', when the release is imminent. -

- -

-We keep a record of bugs in the "testing" distribution that can hold -off a package from being released, or bugs that can hold back the whole -release. For details, please see current testing release -information. -

- -

-Once that bug count lowers to maximum acceptable values, the frozen -"testing" distribution is declared "stable" and released -with a version number. -

- -

-With each new release, the previous "stable" distribution becomes -obsolete and moves to the archive. For more information please see Debian archive. -

- -
- -

5.7 What does the unstable directory contain?

- -

-The `unstable' directory contains a snapshot of the current development system. -Users are welcome to use and test these packages, but are warned about their -state of readiness. The advantage of using the unstable distribution is that -you are always up-to-date with the latest in GNU/Linux software industry, but -if it breaks: you get to keep both parts :-) -

- -

-There are also main, contrib and non-free subdirectories in `unstable', -separated on the same criteria as in `stable'. -

- -
- -

5.8 What are all those directories inside dists/stable/main?

- -

-Within each of the major directory trees[2], there are three sets of subdirectories containing index -files. -

- -

-There's one set of binary-something subdirectories -which contain index files for binary packages of each available computer -architecture, for example binary-i386 for packages which execute -on Intel x86 PC machines or binary-sparc for packages which -execute on Sun SPARCStations. -

- -

-The complete list of available architectures for each release is available at -the release's web -page. For the current release, please see On what hardware architectures/systems does -Debian GNU/Linux run?, Section 3.1. -

- -

-The index files in binary-* are called Packages(.gz) and they include a summary -of each binary package that is included in that distribution. The actual -binary packages (for woody and subsequent releases) reside in the top -level pool directory. -

- -

-Furthermore, there's a subdirectory called source/ which contains index files -for source packages included in the distribution. The index file is called -Sources(.gz). -

- -

-Last but not least, there's a set of subdirectories meant for the installation -system index files. In the woody release, these are named -disks-architecture; in sarge, they are at -debian-installer/binary-architecture. -

- -
- -

5.9 Where is the source code?

- -

-Source code is included for everything in the Debian system. Moreover, the -license terms of most programs in the system require that source code -be distributed along with the programs, or that an offer to provide the source -code accompany the programs. -

- -

-The source code is distributed in the pool directory (see What's in the pool directory?, Section 5.10) -together with all the architecture-specific binary directories. To retrieve -the source code without having to be familiar with the structure of the FTP -archive, try a command like apt-get source mypackagename. -

- -

-Some packages are only distributed as source code due to the restrictions in -their licenses. Notably, one such package is pine, see Where is pine?, Section 4.10 for more -information. -

- -

-Source code may or may not be available for packages in the "contrib" -and "non-free" directories, which are not formally part of the Debian -system. -

- -
- -

5.10 What's in the pool directory?

- -

-Packages are kept in a large `pool', structured according to the name of the -source package. To make this manageable, the pool is subdivided by section -(`main', `contrib' and `non-free') and by the first letter of the source -package name. These directories contain several files: the binary packages for -each architecture, and the source packages from which the binary packages were -generated. -

- -

-You can find out where each package is placed by executing a command like -apt-cache showsrc mypackagename and looking at the `Directory:' -line. For example, the apache packages are stored in -pool/main/a/apache/. -

- -

-Additionally, since there are so many lib* packages, these are -treated specially: for instance, libpaper packages are stored in -pool/main/libp/libpaper/. -

- -

-[3] -

- -
- -

5.11 What is "incoming"?

- -

-After a developer uploads a package, it stays for a short while in the -"incoming" directory before it is checked that it's genuine and -allowed into the archive. -

- -

-Usually nobody should install things from this place. However, in some rare -cases of emergency, the incoming directory is available at http://incoming.debian.org/. You -can manually fetch packages, check the GPG signature and MD5sums in the -.changes and .dsc files, and then install them. -

- -
- -

5.12 How do I set up my own apt-able repository?

- -

-If you have built some private Debian packages which you'd like to install -using the standard Debian package management tools, you can set up your own -apt-able package archive. This is also useful if you'd like to share your -Debian packages while these are not distributed by the Debian project. -Instructions on how to do this are given in the Debian -Repository HOWTO. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-ftparchives.html b/templates/common/doc/FAQ/html/ch-ftparchives.html deleted file mode 120000 index cdad69f..0000000 --- a/templates/common/doc/FAQ/html/ch-ftparchives.html +++ /dev/null @@ -1 +0,0 @@ -ch-ftparchives.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-getting.en.html b/templates/common/doc/FAQ/html/ch-getting.en.html deleted file mode 100644 index 5f608d5..0000000 --- a/templates/common/doc/FAQ/html/ch-getting.en.html +++ /dev/null @@ -1,374 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Getting and installing Debian GNU/Linux - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 2 - Getting and installing Debian GNU/Linux -

- -
- -

-The official document giving installation instructions is the Debian GNU/Linux -Installation Guide. We'll give some additional notes about getting -and installing Debian GNU/Linux here. -

- -
- -

2.1 What is the latest version of Debian?

- -

-Currently there are three versions of Debian GNU/Linux: -

-
-
release 3.1, a.k.a. the `stable' distribution
-
-

-This is stable and well tested software, it changes if major security or -usability fixes are incorporated. -

-
-
-
-
the `testing' distribution
-
-

-This is where packages that will be released as the next `stable' are placed; -they've had some testing in unstable but they may not be completely fit for -release yet. This distribution is updated more often than `stable', but not -more often than `unstable'. -

-
-
-
-
the `unstable' distribution
-
-

-This is the version currently under development; it is updated continuously. -You can retrieve packages from the `unstable' archive on any Debian FTP site -and use them to upgrade your system at any time, but you may not expect the -system to be as usable or as stable as before - that's why it's called -`unstable'! -

-
-
- -

-Please see How many Debian -distributions are there in the dists directory?, Section 5.2 -for more information. -

- -
- -

2.2 Are there package upgrades in `stable'?

- -

-No new functionality is added to the stable release. Once a Debian version is -released and tagged `stable' it will only get security updates. That is, only -packages for which a security vulnerability has been found after the release -will be upgraded. All the security updates are served through security.debian.org. -

- -

-Security updates serve one purpose: to supply a fix for a security -vulnerability. They are not a method for sneaking additional changes into the -stable release without going through normal point release procedure. -Consequently, fixes for packages with security issues will not upgrade the -software. The Debian Security Team will backport the necessary fixes to the -version of the software distributed in `stable' instead. -

- -

-For more information related to security support please read the Security FAQ or the -Debian -Security Manual. -

- -
- -

2.3 Where/how can I get the Debian installation disks?

- -

-You can get the installation disks by downloading the appropriate files from -one of the Debian -mirrors. -

- -

-The installation system files are separated in subdirectories of -dists/stable/main directory, and the names of these subdirectories -correspond to your architecture like this: disks-arch -(arch is "i386", "sparc", etc, check the site -for an exact list). In each of these architecture subdirectories there can be -several directories, each for a version of the installation system, and the -currently used one is in the `current' directory (that's a symbolic link). -

- -

-See the README.txt file in that directory for further -instructions. -

- -
- -

2.4 How do I install the Debian from CD-ROMs?

- -

-Linux supports the ISO 9660 (CD-ROM) file system with Rock Ridge extensions -(formerly known as "High Sierra"). Several vendors provide Debian -GNU/Linux in this format. -

- -

-Warning: When installing from CD-ROM, it is usually not a good idea to choose -dselect's cdrom access method. This method is usually very slow. -The mountable and apt methods, for example, are much -better for installing from CD-ROM (see dpkg-mountable, Section 8.2.5 -and apt-get, dselect and apt-cdrom, Section -8.2.2). -

- -
- -

2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!

- -

-Official Debian CD images indeed contain symlinks like: -

- -
-      /dists/frozen -> sarge/
-      /dists/stable -> sarge/
-      /dists/testing -> sarge/
-      /dists/unstable -> sarge/
-
- -

-so that they work when your sources.list has an entry like -

- -
-      deb cdrom:[<name as on cd label>]/ unstable main [...]
-
- -

-. -

- -

-The fact these symlinks are present does not mean the image is -`unstable' or `testing' or anything. Read the CD label in -/.disk/info to find out which Debian version it contains. This -information is also present in /README.txt on the CD. -

- -

-Read http://www.debian.org/releases/ -to find out what the current `stable' and `testing' releases are. -

- -
- -

2.6 I have my own CD-writer, are there CD images available somewhere?

- -

-Yes. To make it easier for CD vendors to provide high quality disks, we -provide the Official CD -images. -

- -
- -

2.7 Can I install it from a pile of floppy disks?

- -

-First of all, a warning: whole Debian GNU/Linux is way too large to be -installed from media as small as a standard 1.44MB floppy disk - you may not -find installing from floppies a very pleasant experience. -

- -

-Copy the Debian packages onto formatted floppy disks. Either a DOS, the native -Linux "ext2", or the "minix" format will do; one just has -to use a mount command appropriate to the floppy being used. -

- -

-Using floppy disks has these complications: -

-
    -
  • -

    -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. -

    -
    • -
-
    -
  • -

    -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 -dpkg-split, Section 7.1.5.2), -available in the tools directory on Debian mirrors. -

    -
    • -
- -

-You must have support in the kernel for floppy disks in order to read and write -to floppy disk; most kernels come with floppy drive support included in them. -

- -

-To mount a floppy disk under the mount point /floppy (a directory -which should have been created during installation), use: -

-
    -
  • -
    -     mount -t msdos /dev/fd0 /floppy/
-
    - -

    -if the floppy disk is in drive A: and has an MS-DOS file system, -

    -
    • -
-
    -
  • -
    -     mount -t msdos /dev/fd1 /floppy/
-
    - -

    -if the floppy disk is in drive B: and has an MS-DOS file system, -

    -
    • -
-
    -
  • -
    -     mount -t ext2 /dev/fd0 /floppy/
-
    - -

    -if the floppy disk is in drive A: and has an ext2 (i.e., a normal Linux) file -system. -

    -
    • -
- -
- -

2.8 Can I get and install Debian directly from a remote Internet site?

- -

-Yes. You can boot the Debian installation system from a set of files you can -download from our FTP site and its mirrors. -

- -

-You can download a small CD image file, create a bootable CD from it, install -the basic system from it and the rest over the network. For more information -please see http://www.debian.org/CD/netinst/. -

- -

-You can also download even smaller floppy disk image files, create bootable -diskettes from them, start the installation procedure and get the rest of -Debian over the network. For more information, please see http://www.debian.org/distrib/floppyinst. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-getting.html b/templates/common/doc/FAQ/html/ch-getting.html deleted file mode 120000 index 568d808..0000000 --- a/templates/common/doc/FAQ/html/ch-getting.html +++ /dev/null @@ -1 +0,0 @@ -ch-getting.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-kernel.en.html b/templates/common/doc/FAQ/html/ch-kernel.en.html deleted file mode 100644 index 5e88fad..0000000 --- a/templates/common/doc/FAQ/html/ch-kernel.en.html +++ /dev/null @@ -1,311 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Debian and the kernel - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 9 - Debian and the kernel -

- -
- -

9.1 Can I install and compile a kernel without some Debian-specific tweaking?

- -

-Yes. -

- -

-There's only one common catch: the Debian C libraries are built with the most -recent stable releases of the kernel headers. If you -happen to need to compile a program with kernel headers newer than the ones -from the stable branch, then you should either upgrade the package containing -the headers (libc6-dev), or use the new headers from an unpacked -tree of the newer kernel. That is, if the kernel sources are in -/usr/src/linux, then you should add --I/usr/src/linux/include/ to your command line when compiling. -

- -
- -

9.2 What tools does Debian provide to build custom kernels?

- -

-Users who wish to (or must) build a custom kernel are encouraged to download -the package kernel-package. This package contains the script to -build the kernel package, and provides the capability to create a Debian -kernel-image package just by running the command -

- -
-     make-kpkg kernel_image
-
- -

-in the top-level kernel source directory. Help is available by executing the -command -

- -
-     make-kpkg --help
-
- -

-and through the manual page make-kpkg(1). -

- -

-Users must separately download the source code for the most recent kernel (or -the kernel of their choice) from their favorite Linux archive site, unless a -kernel-source-version package is available (where "version" stands -for the kernel version). -

- -

-Detailed instructions for using the kernel-package package are -given in the file /usr/share/doc/kernel-package/README.gz. -Briefly, one should: -

-
    -
  • -

    -Unpack the kernel sources, and cd to the newly created directory. -

    -
    • -
-
    -
  • -

    -Modify the kernel configuration using one of these commands: -

    -
      -
    • -

      -make config (for a tty one-line-at-a-time-interface). -

      -
      • -
    -
      -
    • -

      -make menuconfig (for an ncurses-based menu driven interface). -Note that to use this option, the libncurses5-dev package must be -installed. -

      -
      • -
    -
      -
    • -

      -make xconfig (for an X11 interface). Using this option requires -that relevant X and Tcl/Tk packages be installed. -

      -
      • -
    - -

    -Any of the above steps generates a new .config in the top-level -kernel source directory. -

    -
    • -
-
    -
  • -

    -Execute the command: make-kpkg -rev Custom.N kernel_image, where N -is a revision number assigned by the user. The new Debian archive thus formed -would have revision Custom.1, e.g., -kernel-image-2.2.14_Custom.1_i386.deb for the Linux kernel 2.2.14 -on i386. -

    -
    • -
-
    -
  • -

    -Install the package created. -

    -
      -
    • -

      -Run dpkg --install /usr/src/kernel-image-VVV_Custom.N.deb to -install the kernel itself. The installation script will: -

      -
        -
      • -

        -run the boot loader (grub, LILO or some other) if needed, -

        -
        • -
      -
        -
      • -

        -install the custom kernel in /boot/vmlinuz_VVV-Custom.N, and set up appropriate -symbolic links to the most recent kernel version. -

        -
        • -
      - -
      • -
    -
      -
    • -

      -To employ secondary boot loaders such as loadlin, copy this image -to other locations (e.g. to an MS-DOS partition). -

      -
      • -
    -
    • -
- -
- -

9.3 How can I make a custom boot floppy?

- -

-This task is greatly aided by the Debian package boot-floppies, -normally found in the admin section of the Debian FTP archive. -Shell scripts in this package produce boot floppies in the -SYSLINUX format. These are MS-DOS formatted floppies -whose master boot records have been altered so that they boot Linux directly -(or whatever other operating system has been defined in the syslinux.cfg file -on the floppy). Other scripts in this package produce emergency root disks and -can even reproduce the base disks. -

- -

-You will find more information about this in the -/usr/share/doc/boot-floppies/README file after installing the -boot-floppies package. -

- -
- -

9.4 What special provisions does Debian provide to deal with modules?

- -

-Debian's modconf package provides a shell script -(/usr/sbin/modconf) which can be used to customize the -configuration of modules. This script presents a menu-based interface, -prompting the user for particulars on the loadable device drivers in his -system. The responses are used to customize the file -/etc/modules.conf (which lists aliases, and other arguments that -must be used in conjunction with various modules) through files in -/etc/modutils/, and /etc/modules (which lists the -modules that must be loaded at boot time). -

- -

-Like the (new) Configure.help files that are now available to support the -construction of custom kernels, the modconf package comes with a series of help -files (in /usr/lib/modules_help/) which provide detailed -information on appropriate arguments for each of the modules. -

- -
- -

9.5 Can I safely de-install an old kernel package, and if so, how?

- -

-Yes. The kernel-image-NNN.prerm script checks to see whether the -kernel you are currently running is the same as the kernel you are trying to -de-install. Therefore you can remove unwanted kernel image packages using this -command: -

- -
-     dpkg --purge --force-remove-essential kernel-image-NNN
-
- -

-(replace "NNN" with your kernel version and revision number, of -course) -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-kernel.html b/templates/common/doc/FAQ/html/ch-kernel.html deleted file mode 120000 index 125039f..0000000 --- a/templates/common/doc/FAQ/html/ch-kernel.html +++ /dev/null @@ -1 +0,0 @@ -ch-kernel.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-nexttime.en.html b/templates/common/doc/FAQ/html/ch-nexttime.en.html deleted file mode 100644 index 0c1d3ec..0000000 --- a/templates/common/doc/FAQ/html/ch-nexttime.en.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Changes expected in the next major release of Debian - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 14 - Changes expected in the next major release of Debian -

- -
- -

14.1 Increased security

- -

-Debian contains support for shadow passwords since release 1.3. In addition, -the Linux library of Pluggable Authentication Modules (a.k.a. libpam;) that -allows sysadmins to choose authorization modes on an application-specific basis -is available, and initially set to authenticate via shadow password. -

- -

-Including full support for advanced authentication methods such as Kerberos, as -well as additional security enhancements for mandatory access control -mechanisms such as SElinux, RSBAC and buffer overflow protection like -Exec-shield or PaX is still in progress. -

- -
- -

14.2 Extended support for non-English users

- -

-Debian already has very good support for non-English users, see How does Debian support non-English -languages?, Section 4.8. -

- -

-We hope to find people who will provide support for even more languages, and -translate. Some programs already support internationalization, so we need -message catalogs translators. Many programs still remain to be properly -internationalized. -

- -

-The GNU Translation Project ftp://ftp.gnu.org/pub/gnu/ABOUT-NLS -works on internationalizing the GNU programs. -

- -
- -

14.3 More architectures

- -

-Complete Debian system on other architectures such as AMD64 or SuperH is -expected soon. Notice that, for AMD64 there is a development archive at -http://amd64.debian.net/ -that provides intallation images as well as binary packages for most of the -distribution. This architecture will probably be added for etch. -

- -
- -

14.4 More kernels

- -

-In addition to Debian GNU/Hurd, Debian is being ported also to BSD kernels, -namely to NetBSD. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-nexttime.html b/templates/common/doc/FAQ/html/ch-nexttime.html deleted file mode 120000 index da23d48..0000000 --- a/templates/common/doc/FAQ/html/ch-nexttime.html +++ /dev/null @@ -1 +0,0 @@ -ch-nexttime.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-pkg_basics.en.html b/templates/common/doc/FAQ/html/ch-pkg_basics.en.html deleted file mode 100644 index 0ebd3fe..0000000 --- a/templates/common/doc/FAQ/html/ch-pkg_basics.en.html +++ /dev/null @@ -1,860 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Basics of the Debian package management system - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 6 - Basics of the Debian package management system -

- -
- -

6.1 What is a Debian package?

- -

-Packages generally contain all of the files necessary to implement a set of -related commands or features. There are two types of Debian packages: -

-
    -
  • -

    -Binary packages, which contain executables, configuration files, -man/info pages, copyright information, and other documentation. These packages -are distributed in a Debian-specific archive format (see What is the format of a Debian binary package?, Section -6.2); they are usually distinguished by having a '.deb' file extension. -Binary packages can be unpacked using the Debian utility dpkg; -details are given in its manual page. -

    -
    • -
-
    -
  • -

    -Source packages, which consist of a .dsc file describing -the source package (including the names of the following files), a -.orig.tar.gz file that contains the original unmodified source in -gzip-compressed tar format and usually a .diff.gz file that -contains the Debian-specific changes to the original source. The utility -dpkg-source packs and unpacks Debian source archives; details are -provided in its manual page. -

    -
    • -
- -

-Installation of software by the package system uses "dependencies" -which are carefully designed by the package maintainers. These dependencies -are documented in the control file associated with each package. -For example, the package containing the GNU C compiler (gcc) -"depends" on the package binutils which includes the -linker and assembler. If a user attempts to install gcc without -having first installed binutils, the package management system -(dpkg) will send an error message that it also needs binutils, and -stop installing gcc. (However, this facility can be overridden by -the insistent user, see dpkg(8).) See more in What is meant by saying that a package Depends, -Recommends, Suggests, Conflicts, Replaces -or Provides another package?, Section 6.9 below. -

- -

-Debian's packaging tools can be used to: -

-
    -
  • -

    -manipulate and manage packages or parts of packages, -

    -
    • -
-
    -
  • -

    -aid the user in the break-up of packages that must be transmitted through a -limited-size medium such as floppy disks, -

    -
    • -
-
    -
  • -

    -aid developers in the construction of package archives, and -

    -
    • -
-
    -
  • -

    -aid users in the installation of packages which reside on a remote FTP site. -

    -
    • -
- -
- -

6.2 What is the format of a Debian binary package?

- -

-A Debian "package", or a Debian archive file, contains the executable -files, libraries, and documentation associated with a particular suite of -program or set of related programs. Normally, a Debian archive file has a -filename that ends in .deb. -

- -

-The internals of this Debian binary packages format are described in the -deb(5) manual page. This internal format is subject to change -(between major releases of Debian GNU/Linux), therefore please always use -dpkg-deb(1) for manipulating .deb files. -

- -
- -

6.3 Why are Debian package file names so long?

- -

-The Debian binary package file names conform to the following convention: -<foo>_<VersionNumber>-<DebianRevisionNumber>.deb -

- -

-Note that foo is supposed to be the package name. As a check, one -can learn the package name associated with a particular Debian archive file -(.deb file) in one of these ways: -

-
    -
  • -

    -inspect the "Packages" file in the directory where it was stored at a -Debian FTP archive site. This file contains a stanza describing each package; -the first field in each stanza is the formal package name. -

    -
    • -
-
    -
  • -

    -use the command dpkg --info foo_VVV-RRR.deb (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. -

    -
    • -
- -

-The VVV component is the version number specified by the upstream -developer. There are no standards in place here, so the version number may -have formats as different as "19990513" and "1.3.8pre1". -

- -

-The RRR component is the Debian revision number, and is specified -by the Debian developer (or an individual user if he chooses to build the -package himself). This number corresponds to the revision level of the Debian -package, thus, a new revision level usually signifies changes in the Debian -Makefile (debian/rules), the Debian control file -(debian/control), the installation or removal scripts -(debian/p*), or in the configuration files used with the package. -

- -
- -

6.4 What is a Debian control file?

- -

-Specifics regarding the contents of a Debian control file are provided in the -Debian Policy Manual, section 5, see What other documentation exists on and -for a Debian system?, Section 11.1. -

- -

-Briefly, a sample control file is shown below for the Debian package hello: -

- -
-     Package: hello
-     Priority: optional
-     Section: devel
-     Installed-Size: 45
-     Maintainer: Adam Heath <doogie@debian.org>
-     Architecture: i386
-     Version: 1.3-16
-     Depends: libc6 (>= 2.1)
-     Description: The classic greeting, and a good example
-      The GNU hello program produces a familiar, friendly greeting.  It
-      allows nonprogrammers to use a classic computer science tool which
-      would otherwise be unavailable to them.
-      .
-      Seriously, though: this is an example of how to do a Debian package.
-      It is the Debian version of the GNU Project's `hello world' program
-      (which is itself an example for the GNU Project).
-
- -

-The Package field gives the package name. This is the name by which the -package can be manipulated by the package tools, and usually similar to but not -necessarily the same as the first component string in the Debian archive file -name. -

- -

-The Version field gives both the upstream developer's version number and (in -the last component) the revision level of the Debian package of this program as -explained in Why are Debian package file names so long?, -Section 6.3. -

- -

-The Architecture field specifies the chip for which this particular binary was -compiled. -

- -

-The Depends field gives a list of packages that have to be installed in order -to install this package successfully. -

- -

-The Installed-Size indicates how much disk space the installed package will -consume. This is intended to be used by installation front-ends in order to -show whether there is enough disk space available to install the program. -

- -

-The Section line gives the "section" where this Debian package is -stored at the Debian FTP sites. This is the name of a subdirectory (within one -of the main directories, see What -are all those directories at the Debian FTP archives?, Section 5.1) where -the package is stored. -

- -

-The Priority indicates how important is this package for installation, so that -semi-intelligent software like dselect or console-apt can sort the package into -a category of e.g. packages optionally installed. See What is an Essential Required, -Important, Standard, Optional, or Extra -package?, Section 6.7. -

- -

-The Maintainer field gives the e-mail address of the person who is currently -responsible for maintaining this package. -

- -

-The Description field gives a brief summary of the package's features. -

- -

-For more information about all possible fields a package can have, please see -the Debian Policy Manual, section 5., "Control files and their -fields". -

- -
- -

6.5 What is a Debian conffile?

- -

-Conffiles is a list of configuration files (usually placed in -/etc) that the package management system will not overwrite when -the package is upgraded. This ensures that local values for the contents of -these files will be preserved, and is a critical feature enabling the in-place -upgrade of packages on a running system. -

- -

-To determine exactly which files are preserved during an upgrade, run: -

- -
-     dpkg --status package
-
- -

-And look under "Conffiles:". -

- -
- -

6.6 What is a Debian preinst, postinst, prerm, and postrm script?

- -

-These files are executable scripts which are automatically run before or after -a package is installed. Along with a file named control, all of -these files are part of the "control" section of a Debian archive -file. -

- -

-The individual files are: -

-
-
preinst
-
-

-This script executes before that package will be unpacked from its Debian -archive (".deb") file. Many 'preinst' scripts stop services for -packages which are being upgraded until their installation or upgrade is -completed (following the successful execution of the 'postinst' script). -

-
-
-
-
postinst
-
-

-This script typically completes any required configuration of the package -foo once foo has been unpacked from its Debian -archive (".deb") file. Often, 'postinst' scripts ask the user for -input, and/or warn the user that if he accepts default values, he should -remember to go back and re-configure that package as the situation warrants. -Many 'postinst' scripts then execute any commands necessary to start or restart -a service once a new package has been installed or upgraded. -

-
-
-
-
prerm
-
-

-This script typically stops any daemons which are associated with a package. -It is executed before the removal of files associated with the package. -

-
-
-
-
postrm
-
-

-This script typically modifies links or other files associated with -foo, and/or removes files created by the package. (Also see What is a Virtual Package?, Section 6.8.) -

-
-
- -

-Currently all of the control files can be found in directory -/var/lib/dpkg/info. The files relevant to package -foo begin with the name "foo" and have file extensions -of "preinst", "postinst", etc., as appropriate. The file -foo.list in that directory lists all of the files that were -installed with the package foo. (Note that the location of these -files is a dpkg internal; you should not rely on it.) -

- -
- -

6.7 What is an Essential Required, Important, Standard, Optional, or Extra package?

- -

-Each Debian package is assigned a priority by the distribution -maintainers, as an aid to the package management system. The priorities are: -

-
    -
  • -

    -Required: packages that are necessary for the proper -functioning of the system. -

    - -

    -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. -

    -
    • -
-
    -
  • -

    -Important packages should be found on any Unix-like system. -

    - -

    -Other packages which the system will not run well or be usable without will be -here. This does NOT include Emacs or X11 or TeX or any other large -applications. These packages only constitute the bare infrastructure. -

    -
    • -
-
    -
  • -

    -Standard packages are standard on any Linux system, including -a reasonably small but not too limited character-mode system. -

    - -

    -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 (gcc, g++), -GNU make, as well as the Python interpreter and some server software like -OpenSSH, the BSD printer daemon (lpr) and the RPC portmapper -(portmap). -

    -
    • -
-
    -
  • -

    -Optional 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. -

    - -

    -This includes X11, a full TeX distribution, and lots of applications. -

    -
    • -
-
    -
  • -

    -Extra: packages that either conflict with others with higher -priorities, are only likely to be useful if you already know what they are, or -have specialized requirements that make them unsuitable for -"Optional". -

    -
    • -
- -

-If you do a default Debian installation all the packages of priority -Standard or higher will be installed in your system. If you -select pre-defined tasks you will get lower priority packages too. -

- -

-Additionally, some packages are marked as Essential since they -are absolutely necessary for the proper functioning of the system. The package -management tools will refuse to remove these. -

- -
- -

6.8 What is a Virtual Package?

- -

-A virtual package is a generic name that applies to any one of a group of -packages, all of which provide similar basic functionality. For example, both -the tin and trn programs are news readers, and should -therefore satisfy any dependency of a program that required a news reader on a -system, in order to work or to be useful. They are therefore both said to -provide the "virtual package" called news-reader. -

- -

-Similarly, smail and sendmail both provide the -functionality of a mail transport agent. They are therefore said to provide -the virtual package, "mail transport agent". If either one is -installed, then any program depending on the installation of a -mail-transport-agent will be satisfied by the existence of this -virtual package. -

- -

-Debian provides a mechanism so that, if more than one package which provide the -same virtual package is installed on a system, then system administrators can -set one as the preferred package. The relevant command is -update-alternatives, and is described further in Some users like mawk, others like gawk; -some like vim, others like elvis; some like trn, others like tin; how does -Debian support diversity?, Section 10.10. -

- -
- -

6.9 What is meant by saying that a package Depends, Recommends, Suggests, Conflicts, Replaces or Provides another package?

- -

-The Debian package system has a range of package "dependencies" which -are designed to indicate (in a single flag) the level at which Program A can -operate independently of the existence of Program B on a given system: -

-
    -
  • -

    -Package A depends 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. -

    -
    • -
-
    -
  • -

    -Package A recommends Package B, if the package maintainer judges that -most users would not want A without also having the functionality provided by -B. -

    -
    • -
-
    -
  • -

    -Package A suggests Package B if B contains files that are related to -(and usually enhance) the functionality of A. -

    -
    • -
-
    -
  • -

    -Package A conflicts with Package B when A will not operate if B is -installed on the system. Most often, conflicts are cases where A contains -files which are an improvement over those in B. "Conflicts" are -often combined with "replaces". -

    -
    • -
-
    -
  • -

    -Package A replaces Package B when files installed by B are removed and -(in some cases) over-written by files in A. -

    -
    • -
-
    -
  • -

    -Package A provides 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. -

    -
    • -
- -

-More detailed information on the use of each these terms can be found in the -Policy manual. -

- -
- -

6.10 What is meant by Pre-Depends?

- -

-"Pre-Depends" is a special dependency. In the case of most packages, -dpkg will unpack its archive file (i.e., its .deb -file) independently of whether or not the files on which it depends exist on -the system. Simplistically, unpacking means that dpkg will -extract the files from the archive file that were meant to be installed on your -file system, and put them in place. If those packages depend on the -existence of some other packages on your system, dpkg will refuse -to complete the installation (by executing its "configure" action) -until the other packages are installed. -

- -

-However, for some packages, dpkg will refuse even to unpack them -until certain dependencies are resolved. Such packages are said to -"Pre-depend" on the presence of some other packages. The Debian -project provided this mechanism to support the safe upgrading of systems from -a.out format to ELF format, where the order -in which packages were unpacked was critical. There are other large upgrade -situations where this method is useful, e.g. the packages with the required -priority and their LibC dependency. -

- -

-As before, more detailed information about this can be found in the Policy -manual. -

- -
- -

6.11 What is meant by unknown, install, remove purge and hold in the package status?

- -

-These "want" flags tell what the user wanted to do with a package (as -indicated either by the user's actions in the "Select" section of -dselect, or by the user's direct invocations of -dpkg). -

- -

-Their meanings are: -

-
    -
  • -

    -unknown - the user has never indicated whether he wants the package -

    -
    • -
-
    -
  • -

    -install - the user wants the package installed or upgraded -

    -
    • -
-
    -
  • -

    -remove - the user wants the package removed, but does not want to remove any -existing configuration files. -

    -
    • -
-
    -
  • -

    -purge - the user wants the package to be removed completely, including its -configuration files. -

    -
    • -
-
    -
  • -

    -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. -

    -
    • -
- -
- -

6.12 How do I put a package on hold?

- -

-There are three ways of holding back packages, with dpkg, aptitude or with -dselect. -

- -

-With dpkg, you just have to export the list of package selections, with: -

- -
-     dpkg --get-selections \* > selections.txt
-
- -

-Then edit the resulting file selections.txt, change the line -containing the package you wish to hold, e.g. libc6, from this: -

- -
-     libc6                                           install
-
- -

-to this: -

- -
-     libc6                                           hold
-
- -

-Save the file, and reload it into dpkg database with: -

- -
-     dpkg --set-selections < selections.txt
-
- -

-With aptitude, you can hold a package using -

- -
-     aptitude hold package_name
-
- -

-and remove the hold with -

- -
-     aptitude unhold package_name
-
- -

-With dselect, you just have to enter the [S]elect screen, find the package you -wish to hold in its present state, and press the `=' key (or `H'). The changes -will go live immediately after you exit the [S]elect screen. -

- -
- -

6.13 How do I install a source package?

- -

-Debian source packages can't actually be "installed", they are just -unpacked in whatever directory you want to build the binary packages they -produce. -

- -

-Source packages are distributed on most of the same mirrors where you can -obtain the binary packages. If you set up your APT's -sources.list(5) to include the appropriate "deb-src" -lines, you'll be able to easily download any source packages by running -

- -
-     apt-get source foo
-
- -

-To help you in actually building the source package, Debian source package -provide the so-called build-dependencies mechanism. This means that the source -package maintainer keeps a list of other packages that are required to build -their package. To see how this is useful, run -

- -
-     apt-get build-dep foo
-
- -

-before building the source. -

- -
- -

6.14 How do I build binary packages from a source package?

- -

-You will need all of foo_*.dsc, foo_*.tar.gz and foo_*.diff.gz to compile the -source (note: there is no .diff.gz for some packages that are native to -Debian). -

- -

-Once you have them (How do I install a source package?, -Section 6.13), if you have the dpkg-dev package installed, the -following command: -

- -
-     dpkg-source -x foo_version-revision.dsc
-
- -

-will extract the package into a directory called foo-version. -

- -

-If you want just to compile the package, you may cd into -foo-version directory and issue the command -

- -
-     dpkg-buildpackage -rfakeroot -b
-
- -

-to build the package (note that this also requires the fakeroot -package), and then -

- -
-     dpkg -i ../foo_version-revision_arch.deb
-
- -

-to install the newly-built package(s). -

- -
- -

6.15 How do I create Debian packages myself?

- -

-For more detailed description on this, read the New Maintainers' Guide, -available in the maint-guide package, or at http://www.debian.org/doc/devel-manuals#maint-guide. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-pkg_basics.html b/templates/common/doc/FAQ/html/ch-pkg_basics.html deleted file mode 120000 index 98c97fe..0000000 --- a/templates/common/doc/FAQ/html/ch-pkg_basics.html +++ /dev/null @@ -1 +0,0 @@ -ch-pkg_basics.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-pkgtools.en.html b/templates/common/doc/FAQ/html/ch-pkgtools.en.html deleted file mode 100644 index 114bb9f..0000000 --- a/templates/common/doc/FAQ/html/ch-pkgtools.en.html +++ /dev/null @@ -1,936 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - The Debian package management tools - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 7 - The Debian package management tools -

- -
- -

7.1 What programs does Debian provide for managing its packages?

- -

-There are multiple tools that are used to manage Debian packages, from graphic -or text-based interfaces to the low level tools used to install packages. All -the available tools rely on the lower level tools to properly work and are -presented here in decreasing complexity level. -

- -

-It is important to understand that the higher level package management tools -such as aptitude or dselect rely on apt -which, itself, relies on dpkg to manage the packages in the -system. -

- -

-See the APT -HOWTO for more information about the Debian package management -utilities. This document is available in various languages and formats, see -the APT HOWTO -entry on the DDP Users' Manuals overview. -

- -
- -

7.1.1 dpkg

- -

-This is the main package management program. dpkg can be invoked -with many options. Some common uses are: -

-
    -
  • -

    -Find out all the options: dpkg --help. -

    -
    • -
-
    -
  • -

    -Print out the control file (and other information) for a specified package: -dpkg --info foo_VVV-RRR.deb -

    -
    • -
-
    -
  • -

    -Install a package (including unpacking and configuring) onto the file system of -the hard disk: dpkg --install foo_VVV-RRR.deb. -

    -
    • -
-
    -
  • -

    -Unpack (but do not configure) a Debian archive into the file system of the hard -disk: dpkg --unpack foo_VVV-RRR.deb. Note that this operation -does not 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 What is a Debian preinst, postinst, -prerm, and postrm script?, Section 6.6) script associated with the package. -

    -
    • -
-
    -
  • -

    -Configure a package that already has been unpacked: dpkg --configure -foo. Among other things, this action runs the postinst (see What is a Debian preinst, postinst, -prerm, and postrm script?, Section 6.6) script associated with the package. -It also updates the files listed in the conffiles for this -package. Notice that the 'configure' operation takes as its argument a package -name (e.g., foo), not the name of a Debian archive file (e.g., -foo_VVV-RRR.deb). -

    -
    • -
-
    -
  • -

    -Extract a single file named "blurf" (or a group of files named -"blurf*" from a Debian archive: dpkg --fsys-tarfile -foo_VVV-RRR.deb | tar -xf - blurf* -

    -
    • -
-
    -
  • -

    -Remove a package (but not its configuration files): dpkg --remove -foo. -

    -
    • -
-
    -
  • -

    -Remove a package (including its configuration files): dpkg --purge -foo. -

    -
    • -
-
    -
  • -

    -List the installation status of packages containing the string (or regular -expression) "foo*": dpkg --list 'foo*'. -

    -
    • -
- -
- -

7.1.2 APT

- -

-APT is the Advanced Package Tool and provides the apt-get -program. apt-get provides a simple way to retrieve and install -packages from multiple sources using the command line. Unlike -dpkg, apt-get does not understand .deb files, it -works with the packages proper name and can only install .deb archives from a -source specified in /etc/apt/sources.list. apt-get -will call dpkg directly after downloading the .deb archives[4] from the configured sources. -

- -

-Some common ways to use apt-get are: -

-
    -
  • -

    -To update the list of package known by your system, you can run: -

    - -
    -     apt-get update
-
    - -

    -(you should execute this regularly to update your package lists) -

    -
    • -
-
    -
  • -

    -To upgrade all the packages on your system, run: -

    - -
    -     apt-get upgrade
-
    -
    • -
-
    -
  • -

    -To install the foo package and all its dependencies, run: -

    - -
    -     apt-get install foo
-
    -
    • -
-
    -
  • -

    -To remove the foo package from your system, run: -

    - -
    -     apt-get remove foo
-
    -
    • -
-
    -
  • -

    -To remove the foo package and its configuration files from your system, run: -

    - -
    -     apt-get --purge remove foo
-
    -
    • -
-
    -
  • -

    -To upgrade all the packages on your system to a new Debian GNU/Linux release, -run: -

    - -
    -     apt-get dist-upgrade
-
    -
    • -
- -

-Note that you must be logged in as root to perform any commands that modify the -system packages. -

- -

-The apt tool suite also includes the apt-cache tool to query the -package lists. You can use it to find packages providing specific -functionality through simple text or regular expression queries and through -queries of dependencies in the package management system. Some common ways to -use apt-cache are: -

-
    -
  • -

    -To find packages whose description contain word: -

    - -
    -     apt-cache search word
-
    -
    • -
-
    -
  • -

    -To print the detailed information of a package: -

    - -
    -     apt-cache show package
-
    -
    • -
-
    -
  • -

    -To print the packages a given package depends on: -

    - -
    -     apt-cache depends package
-
    -
    • -
-
    -
  • -

    -To print detailed information of the versions available for a package and the -packages that reverse-depends on it: -

    - -
    -     apt-cache showpkg package
-
    -
    • -
- -

-For more information, install the apt package and read -apt-get(8), sources.list(5) and install the -apt-doc package and read -/usr/share/doc/apt-doc/guide.html/index.html. -

- -
- -

7.1.3 aptitude

- -

-aptitude is a package manager for Debian GNU/Linux systems that -provides a frontend to the apt package management infrastructure. -aptitude is a text-based interface using the curses library, it -can be used to perform management tasks in a fast and easy way. -

- -

-aptitude provides the functionality of dselect and -apt-get, as well as many additional features not found in either -program: -

-
    -
  • -

    -aptitude offers access to all versions of a package. -

    -
    • -
-
    -
  • -

    -aptitude logs all its actions in /var/log/aptitude. -

    -
    • -
-
    -
  • -

    -aptitude makes it easy to keep track of obsolete software by -listing it under "Obsolete and Locally Created Packages". -

    -
    • -
-
    -
  • -

    -aptitude includes a fairly powerful system for searching -particular packages and limiting the package display. Users familiar with -mutt will pick up quickly, as mutt was the -inspiration for the expression syntax. -

    -
    • -
-
    -
  • -

    -aptitude tracks which packages have been installed due to -dependencies and removes them automatically when the packages that needed them -are removed from the system. -

    -
    • -
-
    -
  • -

    -aptitude can automatically install Recommended: -packages[5]. -

    -
    • -
-
    -
  • -

    -aptitude in full screen mode has su functionality -embedded and can be run by a normal user. It will call su (and -ask for the root password, if any) when you really need administrative -privileges -

    -
    • -
- -

-You can use aptitude through a visual interface (simply run -aptitude) or directly from the command line. The command line -syntax used is very similar to the one used in apt-get. For -example, to install the foo package, you can run aptitude -install foo. -

- -

-Note that aptitude is the recommended program by Debian to install -a package and/or to upgrade your system. -

- -

-For more informations, read the manual page aptitude(8) and -install the aptitude-doc-en package. -

- -
- -

7.1.4 dselect

- -

-This program is a menu-driven interface to the Debian package management -system. It is particularly useful for first-time installations. Some users -might feel more comfortable using aptitude which is also -recommended over dselect for large-scale upgrades. For more -information on aptitude please see aptitude, -Section 7.1.3. -

- -

-dselect can: -

-
    -
  • -

    -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; -

    -
    • -
-
    -
  • -

    -warn the user about inconsistencies or incompatibilities in their selections; -

    -
    • -
-
    -
  • -

    -determine the order in which the packages must be installed; -

    -
    • -
-
    -
  • -

    -automatically perform the installation or removal; and -

    -
    • -
-
    -
  • -

    -guide the user through whatever configuration process are required for each -package. -

    -
    • -
- -

-dselect begins by presenting the user with a menu of 7 items, each -of which is a specific action. The user can select one of the actions by using -the arrow keys to move the highlighter bar, then pressing the -<enter> key to select the highlighted action. -

- -

-What the user sees next depends on the action he selected. If he selects any -option but Access or Select, then -dselect will simply proceed to execute the specified action: e.g., -if the user selected the action Remove, then dselect would proceed -to remove all of the files selected for removal when the user last chose the -Select action. -

- -

-Both the Access menu item and the Select menu item -lead to additional menus. In both cases, the menus are presented as split -screens; the top screen gives a scrollable list of choices, while the bottom -screen gives a brief explanation ("info") for each choice. -

- -

-Extensive on-line help is available, use the '?' key to get to a help screen -at any time. -

- -

-The order in which the actions are presented in the first dselect -menu represents the order in which a user would normally choose -dselect to install packages. However, a user can pick any of the -main menu choices as often as needed (including not at all, depending on what -one wants to do). -

-
    -
  • -

    -Begin by choosing an Access Method. This is the method by -which the user plans on accessing Debian packages; e.g., some users have Debian -packages available on CD-ROM, while others plan to fetch them using anonymous -FTP. The selected "Access Method" is stored after -dselect exits, so if it does not change, then this option need not -be invoked again. -

    -
    • -
-
    -
  • -

    -Then Update the list of available packages. To do this, -dselect reads the file "Packages.gz" which should be -included in the top level of the directory where the Debian packages to be -installed are stored. (But if it is not there, dselect will offer -to make it for you.) -

    -
    • -
-
    -
  • -

    -Select 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). -

    - -

    -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. -

    - -

    -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: -

    -
    -
    to be installed:
    -
    -

    -This is accomplished by pressing the `+' key. -

    -
    -
    -
    -
    to be deleted:
    -
    -

    -Packages can be deleted two ways: -

    -
      -
    • -

      -removed: this removes most of the files associated with the package, but -preserves the files listed as configuration files (see What is a Debian conffile?, Section -6.5) and package configuration information. This is done by pressing the -`-' key. -

      -
      • -
    -
      -
    • -

      -purged: this removes every file that is part of the package. This is -done by pressing the `_' key. -

      -
      • -
    - -

    -Note that it's not possible to remove "All Packages". If you try -that, your system will instead be reduced to the initial installed base -packages. -

    -
    -
    -
    -
    to be put "on hold"
    -
    -

    -This is done by pressing `=', and it effectively tells dselect 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 Access Method, and -acquired when you used Update). -

    - -

    -Just like you can put a package on hold, you can reverse such setting by -pressing `:'. That tells dselect that the package(s) may be -upgraded if a newer version is available. This is the default setting. -

    -
    -
    - -

    -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. -

    - -

    -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. -

    - -

    -If you select a package for installation or removal, e.g., -foo.deb, and that package depends on (or recommends) another -package, e.g., blurf.deb, then dselect 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. -

    -
    • -
-
    -
  • -

    -Users returning to the main menu can then select the "Install" menu -item to unpack and configure the selected packages. Alternatively, users -wishing to remove files can choose the "Remove" menu item. At any -point, users can choose "Quit" to exit dselect; users' selections are -preserved by dselect. -

    -
    • -
- -
- -

7.1.5 Other package management tools

- -
- -

7.1.5.1 dpkg-deb

- -

-This program manipulates Debian archive(.deb) files. Some common -uses are: -

-
    -
  • -

    -Find out all the options: dpkg-deb --help. -

    -
    • -
-
    -
  • -

    -Determine what files are contained in a Debian archive file: dpkg-deb ---contents foo_VVV-RRR.deb) -

    -
    • -
-
    -
  • -

    -Extract the files contained in a named Debian archive into a user specified -directory: dpkg-deb --extract foo_VVV-RRR.deb tmp extracts each of -the files in foo_VVV-RRR.deb into the directory tmp/. -This is convenient for examining the contents of a package in a localized -directory, without installing the package into the root file system. -

    -
    • -
- -

-Note that any packages that were merely unpacked using dpkg-deb ---extract will be incorrectly installed, you should use dpkg ---install instead. -

- -

-More information is given in the manual page dpkg-deb(1). -

- -
- -

7.1.5.2 dpkg-split

- -

-This program splits large package into smaller files (e.g., for writing onto a -set of floppy disks), and can also be used to merge a set of split files back -into a single file. It can only be used on a Debian system (i.e. a system -containing the dpkg package), since it calls the program -dpkg-deb to parse the debian package file into its component -records. -

- -

-For example, to split a big .deb file into N parts, -

-
    -
  • -

    -Execute the command dpkg-split --split foo.deb. This will produce -N files each of approximately 460 KBytes long in the current directory. -

    -
    • -
-
    -
  • -

    -Copy those N files to floppy disks. -

    -
    • -
-
    -
  • -

    -Copy the contents of the floppy disks onto the hard disk of your choice on the -other machine. -

    -
    • -
-
    -
  • -

    -Join those part-files together using dpkg-split --join -"foo*". -

    -
    • -
- -
- -

7.2 Debian claims to be able to update a running program; how is this accomplished?

- -

-The kernel (file system) in Debian GNU/Linux systems supports replacing files -even while they're being used. -

- -

-We also provide a program called start-stop-daemon which is used -to start daemons at boot time or to stop daemons when the kernel runlevel is -changed (e.g., from multi-user to single-user or to halt). The same program is -used by installation scripts when a new package containing a daemon is -installed, to stop running daemons, and restart them as necessary. -

- -
- -

7.3 How can I tell what packages are already installed on a Debian system?

- -

-To learn the status of all the packages installed on a Debian system, execute -the command -

- -
-     dpkg --list
-
- -

-This prints out a one-line summary for each package, giving a 2-letter status -symbol (explained in the header), the package name, the version which is -installed, and a brief description. -

- -

-To learn the status of packages whose names match the string any pattern -beginning with "foo" by executing the command: -

- -
-     dpkg --list 'foo*'
-
- -

-To get a more verbose report for a particular package, execute the command: -

- -
-     dpkg --status packagename
-
- -
- -

7.4 How can I find out what package produced a particular file?

- -

-To identify the package that produced the file named foo execute -either: -

-
    -
  • -

    -dpkg --search filename -

    - -

    -This searches for filename in installed packages. (This is -(currently) equivalent to searching all of the files having the file extension -of .list in the directory /var/lib/dpkg/info/, and -adjusting the output to print the names of all the packages containing it, and -diversions.) -

    - -

    -A faster alternative to this is the dlocate tool. -

    -
    • -
-
    -
  • -

    -zgrep foo Contents-ARCH.gz -

    - -

    -This searches for files which contain the substring foo in their -full path names. The files Contents-ARCH.gz (where ARCH -represents the wanted architecture) reside in the major package directories -(main, non-free, contrib) at a Debian FTP site (i.e. under -/debian/dists/sarge). A Contents file refers only to -the packages in the subdirectory tree where it resides. Therefore, a user -might have to search more than one Contents files to find the -package containing the file foo. -

    - -

    -This method has the advantage over dpkg --search in that it will -find files in packages that are not currently installed on your system. -

    -
    • -
-
    -
  • -

    -apt-file search foo -

    - -

    -Similar to the above, it searches files which contain the substring or regular -expression foo in their full path names. The advantage over the -sample above is that there is no need to retrieve the -Contents-ARCH.gz files as it will do this automatically for all -the sources defined in /etc/apt/sources.list when you run (as -root) apt-file update. -

    -
    • -
- -
- -

7.5 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?

- -

-Some packages that are split in program (`foo') and data (`foo-data'). This is -true for many games, multimedia applications and dictionaries in Debian and has -been introduced since some users might want to access the raw data without -installing the program or because the program can be run without the data -itself, making it optional. -

- -

-Similar situations occur when dealing with libraries: generally these get -installed since packages containing applications depend on them. When the -application-package is purged, the library-package might stay on the system. -Or: when the application-package no longer depends upon e.g. libdb4.2, but -upon libdb4.3, the libdb4.2 package might stay when the application-package is -upgraded. -

- -

-In these cases, `foo-data' doesn't depend on `foo', so when you remove the -`foo' package it will not get automatically removed by most package management -tools. The same holds true for the library packages. This is necessary to -avoid circular dependencies. If you use aptitude (see aptitude, Section 7.1.3) as your package management tool -it will, however, track automatically installed packages and remove them when -no packages remain that need them in your system. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-pkgtools.html b/templates/common/doc/FAQ/html/ch-pkgtools.html deleted file mode 120000 index 6c9eeed..0000000 --- a/templates/common/doc/FAQ/html/ch-pkgtools.html +++ /dev/null @@ -1 +0,0 @@ -ch-pkgtools.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-redistrib.en.html b/templates/common/doc/FAQ/html/ch-redistrib.en.html deleted file mode 100644 index f0ac5d0..0000000 --- a/templates/common/doc/FAQ/html/ch-redistrib.en.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Redistributing Debian GNU/Linux in a commercial product - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 13 - Redistributing Debian GNU/Linux in a commercial product -

- -
- -

13.1 Can I make and sell Debian CDs?

- -

-Go ahead. You do not need permission to distribute anything we have -released, so that you can master your CD as soon as the beta-test -ends. You do not have to pay us anything. Of course, all CD manufacturers -must honor the licenses of the programs in Debian. For example, many of the -programs are licensed under the GPL, which requires you to distribute their -source code. -

- -

-Also, we will publish a list of CD manufacturers who donate money, software, -and time to the Debian project, and we will encourage users to buy from -manufacturers who donate, so it is good advertising to make donations. -

- -
- -

13.2 Can Debian be packaged with non-free software?

- -

-Yes. While all the main components of Debian are free software, we provide a -non-free directory for programs that are not freely redistributable. -

- -

-CD manufacturers may be able to distribute the programs we have placed -in that directory, depending on the license terms or their private arrangements -with the authors of those software packages. CD manufacturers can also -distribute the non-free software they get from other sources on the same CD. -This is nothing new: free and commercial software are distributed on the same -CD by many manufacturers now. Of course we still encourage software authors to -release the programs they write as free software. -

- -
- -

13.3 I am making a special Linux distribution for a "vertical market". Can I use Debian GNU/Linux for the guts of a Linux system and add my own applications on top of it?

- -

-Yes. Debian-derived distributions are being created both in close cooperation -with the Debian project itself and by external parties. One can use the -Custom Debian -Distributions framework to work together with Debian; Skolelinux is one such project. -

- -

-One person is building a "Linux for Hams" distribution, with -specialized programs for Radio Amateurs. He is starting with Debian as the -"base system", and adding programs to control the transmitter, track -satellites, etc. All of the programs he adds are packaged with the Debian -packaging system so that his users will be able to upgrade easily when he -releases subsequent CDs. -

- -

-There are several other Debian-derived distributions already on the market, -such as Progeny Debian, Linspire, Knoppix and Ubuntu, that are targeted at a -different kind of audience than the original Debian GNU/Linux is, but use most -of our components in their product. -

- -

-Debian also provides a mechanism to allow developers and system administrators -to install local versions of selected files in such a way that they will not be -overwritten when other packages are upgraded. This is discussed further in the -question on How do I override a file -installed by a package, so that a different version can be used instead?, -Section 10.8. -

- -
- -

13.4 Can I put my commercial program in a Debian "package" so that it installs effortlessly on any Debian system?

- -

-Go right ahead. The package tool is free software; the packages may or may not -be free software, it can install them all. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-redistrib.html b/templates/common/doc/FAQ/html/ch-redistrib.html deleted file mode 120000 index f182623..0000000 --- a/templates/common/doc/FAQ/html/ch-redistrib.html +++ /dev/null @@ -1 +0,0 @@ -ch-redistrib.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-software.en.html b/templates/common/doc/FAQ/html/ch-software.en.html deleted file mode 100644 index bedb65f..0000000 --- a/templates/common/doc/FAQ/html/ch-software.en.html +++ /dev/null @@ -1,410 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Software available in the Debian system - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 4 - Software available in the Debian system -

- -
- -

4.1 What types of applications and development software are available for Debian GNU/Linux?

- -

-Like most Linux distributions, Debian GNU/Linux provides: -

-
    -
  • -

    -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, -

    -
    • -
-
    -
  • -

    -Perl, Python, Tcl/Tk and various related programs, modules and libraries for -each of them, -

    -
    • -
-
    -
  • -

    -TeX (LaTeX) and Lyx, dvips, Ghostscript, -

    -
    • -
-
    -
  • -

    -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, -

    -
    • -
-
    -
  • -

    -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, -

    -
    • -
-
    -
  • -

    -a complete set of office applications, including the OpenOffice.org -productivity suite, Gnumeric and other spreadsheets, WYSIWYG editors, -calendars. -

    -
    • -
- -

-More than 15180 packages, ranging from news servers and readers to sound -support, FAX programs, database and spreadsheet programs, image processing -programs, communications, net, and mail utilities, Web servers, and even -ham-radio programs are included in the distribution. Another 450 software -suites are available as Debian packages, but are not formally part of Debian -due to license restrictions. -

- -
- -

4.2 Who wrote all that software?

- -

-For each package the authors of the program(s) are credited in the -file /usr/share/doc/PACKAGE/copyright, where PACKAGE is to be -substituted with the package's name. -

- -

-Maintainers who package this software for the Debian GNU/Linux system -are listed in the Debian control file (see What is a Debian control file?, -Section 6.4) that comes with each package. The Debian changelog, in -/usr/share/doc/PACKAGE/changelog.Debian.gz, mentions the people -who've worked on the Debian packaging too. -

- -
- -

4.3 How can I get a current list of programs that have been packaged for Debian?

- -

-A complete list is available from any of the Debian mirrors, in the -file indices/Maintainers. That file includes the package names -and the names and e-mails of their respective maintainers. -

- -

-The WWW interface to the Debian -packages conveniently summarizes the packages in each of about -twenty "sections" of the Debian archive. -

- -
- -

4.4 What is missing from Debian GNU/Linux?

- -

-A list of packages which are still needed to be packaged for Debian exists, the -Work-Needing and Prospective -Packages list. -

- -

-For more details about adding the missing things, see How can I become a Debian software -developer?, Section 12.1. -

- -
- -

4.5 Why do I get "ld: cannot find -lfoo" messages when compiling programs? Why aren't there any libfoo.so files in Debian library packages?

- -

-Debian Policy requires that such symbolic links (to libfoo.so.x.y.z or similar) -are placed in separate, development packages. Those packages are usually named -libfoo-dev or libfooX-dev (presuming the library package is named libfooX, and -X is a whole number). -

- -
- -

4.6 (How) Does Debian support Java?

- -

-Since the official Java Development kit and Runtime Environment from Sun -Microsystems is non-free software, even undistributeable by Debian, it cannot -properly be included in Debian. If you want those installed anyway, please -refer to the java-package package in contrib. -

- -

-However, both the JDK and several free implementations of Java -technology are available as Debian packages. You can write, debug and run Java -programs using Debian. -

- -

-Running a Java applet requires a web browser with the capability to recognize -and execute them. Several web browsers available in Debian, such as Mozilla or -Konqueror, support Java plug-ins that enable running Java applets within them. -Netscape Navigator, while non-free, is also available as a Debian package and -it can run Java applets. -

- -

-Please refer to the Debian Java -FAQ for more information. -

- -
- -

4.7 How can I check that I am using a Debian system, and what version is it?

- -

-In order to make sure that your system has been installed from the real Debian -base disks check for the existence of /etc/debian_version file, -which contains a single one-line entry giving the version number of the -release, as defined by the package base-files. -

- -

-The existence of the program dpkg shows that you should be able to -install Debian packages on your system, but as the program has been ported to -many other operating systems and architectures, this is no longer a reliable -method of determining is a system Debian GNU/Linux. -

- -

-Users should be aware, however, that the Debian system consists of many parts, -each of which can be updated (almost) independently. Each Debian -"release" contains well defined and unchanging contents. Updates are -separately available. For a one-line description of the installation status of -package foo, use the command dpkg --list foo. To -view versions of all installed packages, run: -

- -
-     dpkg -l
-
- -

-For a more verbose description, use: -

- -
-     dpkg --status foo
-
- -
- -

4.8 How does Debian support non-English languages?

-
    -
  • -

    -Debian GNU/Linux is distributed with keymaps for nearly two dozen keyboards, -and with utilities (in the kbd package) to install, view, and -modify the tables. -

    - -

    -The installation prompts the user to specify the keyboard he will use. -

    -
    • -
-
    -
  • -

    -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. -

    -
    • -
-
    -
  • -

    -Currently, support for German-, Spanish-, Finnish-, French-, Hungarian-, -Italian-, Japanese-, Korean- and Polish-language manual pages is provided -through the manpages-LANG 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. -

    - -

    -For example, in the case of the Italian-language manual pages, LC_MESSAGES -needs to be set to 'italian'. The man program will then search -for Italian manual pages under /usr/share/man/it/. -

    -
    • -
- -
- -

4.9 What about the US export regulation limitations?

- -

-US laws placed restrictions on the export of defense articles, which includes -some types of cryptographic software. PGP and ssh, among others, fall into -this category. For the sarge release packages in this archive were -moved to the main archive (or to non-free, if applicable) due to the -US relaxing its regulations on the export of cryptography. -

- -

-To prevent anyone from taking unnecessary legal risks, certain Debian GNU/Linux -packages were only available from a non-US site ftp://non-US.debian.org/debian-non-US/, -with numerous mirror sites all of which are also outside of the US, see -ftp://non-US.debian.org/debian-non-US/README.non-US -for a full list. These sites still exist (for the benefit of users of -woody) but its contents are no longer supported and are considered -obsolete. Please remove any mentions to non-US from your sources in your -/etc/apt/sources.list configuration file. -

- -
- -

4.10 Where is pine?

- -

-Due to its restrictive license, it's in the non-free area. Moreover, since -license does not even allow modified binaries to be distributed, you have to -compile it yourself from the source and the Debian patches. -

- -

-The source package name is pine. You can use the -pine-tracker package to be notified about when you need to -upgrade. -

- -

-Note that there are many replacements for both pine and pico, such as -mutt and nano, that are located in the main section. -

- -
- -

4.11 Where is qmail/ezmlm/djbdns?

- -

-Dan J. Bernstein distributes all -software he has written with a restrictive license, consequently, -it's in the non-free area. Since the license he uses does not allow modified -binaries to be distributed, you have to compile it yourself from the source and -the Debian patches to obtain a binary package you can install in your Debian -GNU/Linux system. -

- -

-The source package names are qmail-src, ezmlm-src and -djbdns-installer, respectively. -

- -

-For qmail you need to install qmail-src first and -then run build-qmail to build the Debian package. You also need -to do install the ucspi-tcp-src package to get ucspi-tcp, which -qmail depends on. -

- -

-Dan J. Bernstein maintains a FAQ from distributors page -if you are interested in reading his reasons (one of which is Cross-platform -compatibility) -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-software.html b/templates/common/doc/FAQ/html/ch-software.html deleted file mode 120000 index f75c0ab..0000000 --- a/templates/common/doc/FAQ/html/ch-software.html +++ /dev/null @@ -1 +0,0 @@ -ch-software.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-support.en.html b/templates/common/doc/FAQ/html/ch-support.en.html deleted file mode 100644 index 57e21da..0000000 --- a/templates/common/doc/FAQ/html/ch-support.en.html +++ /dev/null @@ -1,525 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Getting support for Debian GNU/Linux - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 11 - Getting support for Debian GNU/Linux -

- -
- -

11.1 What other documentation exists on and for a Debian system?

- -
    -
  • -

    -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. -

    - -

    -Get it from the debian-reference package, or at http://www.debian.org/doc/user-manuals#quick-reference. -

    -
    • -
-
    -
  • -

    -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. -

    - -

    -Get it from the debian-policy package, or at http://www.debian.org/doc/devel-manuals#policy. -

    -
    • -
-
    -
  • -

    -Documentation developed by the Debian Documentation Project. It is available -at http://www.debian.org/doc/ and -includes user guides, administration guides and security guides for the Debian -GNU/Linux operating system. -

    -
    • -
-
    -
  • -

    -Documentation on installed Debian packages: Most packages have files that are -unpacked into /usr/share/doc/PACKAGE. -

    -
    • -
-
    -
  • -

    -Documentation on the Linux project: The Debian package doc-linux -installs all of the most recent versions of the HOWTOs and mini-HOWTOs from the -Linux Documentation Project. -

    -
    • -
-
    -
  • -

    -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: -man 3 foo, or just man foo if section 3 is the first -one containing a page on foo. -

    - -

    -One can learn which directory of /usr/share/man/ contains a -certain manual page by executing man -w foo. -

    - -

    -New Debian users should note that the 'man' pages of many general system -commands are not available until they install these packages: -

    -
      -
    • -

      -man-db, which contains the man program itself, and -other programs for manipulating the manual pages. -

      -
      • -
    - -
    • -
-
    -
  • -

    -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 info, by running M-x info within GNU -Emacs, or with some other Info page viewer. -

    - -

    -Its main advantage over the original `man' pages are that it is a hypertext -system. It does not require the WWW, however; info can -be run from a plain text console. It was designed by Richard Stallman and -preceded the WWW. -

    -
    • -
- -

-Note that you may access a lot of documentation on your system by using a WWW -browser, through `dwww', `dhelp' or `doccentral' commands, found in respective -packages. -

- -
- -

11.2 Are there any on-line resources for discussing Debian?

- -

-Yes. In fact, the main method of support Debian provides to our users is by -the way of e-mail. -

- -
- -

11.2.1 Mailing lists

- -

-There are a lot of Debian-related mailing -lists. -

- -

-On a system with the doc-debian package installed there is a -complete list of mailing lists in -/usr/share/doc/debian/mailing-lists.txt. -

- -

-Debian mailing lists are named following the pattern -debian-list-subject. Examples are debian-announce, debian-user, -debian-news. To subscribe to any list debian-list-subject, send -mail to debian-list-subject-request@lists.debian.org with the word -"subscribe" in the Subject: header. Be sure to remember to add --request to the e-mail address when using this method to subscribe or -unsubscribe. Otherwise your e-mail will go to the list itself, which could be -embarrassing or annoying, depending on your point of view. -

- -

-If you have a forms-capable World Wide Web browser, you can subscribe to -mailing lists using the WWW form. You -can also un-subscribe using a WWW form. -

- -

-The list manager's e-mail address is listmaster@lists.debian.org, -in case you have any trouble. -

- -

-The mailing lists are public forums. All e-mails sent to the lists are also -copied to the public archive, for anybody (even non-subscribers) to browse or -search. Please make sure you never send any confidential or unlicensed -material to the lists. This includes things like e-mail addresses. Of -particular note is the fact that spammers have been known to abuse e-mail -addresses posted to our mailing lists. See the Mailing -Lists Privacy policy for more information. -

- -

-Archives of the Debian mailing lists are available via WWW at http://lists.debian.org/. -

- -
- -

11.2.1.1 What is the code of conduct for the mailing lists?

- -

-When using the Debian mailing lists, please follow these rules: -

- -
    -
  • -

    -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. -

    -
    • -
-
    -
  • -

    -Do not use foul language; besides, some people receive the lists via packet -radio, where swearing is illegal. -

    -
    • -
-
    -
  • -

    -Make sure that you are using the proper list. Never post your -(un)subscription requests to the mailing list itself[6] -

    -
    • -
- - -
- -

11.2.2 Maintainers

- -

-Users can address questions to individual package maintainers using e-mail. To -reach a maintainer of a package called xyz, send e-mail to -xyz@packages.debian.org. -

- -
- -

11.2.3 Usenet newsgroups

- -

-Users should post non-Debian-specific questions to one of the Linux USENET -groups, which are named comp.os.linux.* or linux.*. There are several lists of -Linux Usenet newsgroups and other related resources on the WWW, e.g. on the -Linux Online -and LinuxJournal sites. -

- -
- -

11.3 Is there a quick way to search for information on Debian GNU/Linux?

- -

-There is a variety of search engines that serve documentation related to -Debian: -

- -
    -
  • -

    -Google Groups: a search -engine for newsgroups. -

    - -

    -For example, to find out what experiences people have had with finding drivers -for Promise controllers under Debian, try searching on the phrase Promise -Linux driver. This will show you all the postings that contain these -strings, i.e. those where people discussed these topics. If you add -Debian to those search strings, you'll also get the postings -specifically related to Debian. -

    -
    • -
-
    -
  • -

    -Any of the common web spidering engines, such as AltaVista or Google, as long as you use the right -search terms. -

    - -

    -For example, searching on the string "cgi-perl" gives a more detailed -explanation of this package than the brief description field in its control -file. -

    -
    • -
- -
- -

11.4 Are there logs of known bugs?

- -

-Reports on unsolved (and closed) issues are publicly available: Debian -promissed to do so by stating "We will not hide problems" in the -Debian Social -Contract. -

- -

-The Debian GNU/Linux distribution has a bug tracking system (BTS) which files -details of bugs reported by users and developers. Each bug is given a number, -and is kept on file until it is marked as having been dealt with. -

- -

-Copies of this information are available at http://www.debian.org/Bugs/. -

- -

-A mail server provides access to the bug tracking system database via e-mail. -In order to get the instructions, send an e-mail to request@bugs.debian.org -with "help" in the body. -

- -
- -

11.5 How do I report a bug in Debian?

- -

-If you have found a bug in Debian, please read the instructions for reporting a -bug in Debian. These instructions can be obtained in one of several ways: -

-
    -
  • -

    -By anonymous FTP. Debian mirror sites contain the instructions in the file -doc/bug-reporting.txt. -

    -
    • -
- -
    -
  • -

    -On any Debian system with the doc-debian package installed. The -instructions are in the file -/usr/share/doc/debian/bug-reporting.txt. -

    -
    • -
- -

-You can use the package reportbug that will guide you through the -reporting process and mail the message to the proper address, with some extra -details about your system added automatically. It will also show you a list of -bugs already reported to the package you are reporting against in case your bug -has been reported previously, so that you can additional information to the -existing bug report. -

- -

-If you want to mail the report with an e-mail program, send a message to -submit@bugs.debian.org. The -message's first line must be similar to -

- -
-     Package: package-name
-
- -

-(replace package-name with the name of the package). The next line -should relate the package version number in a similar way: -

- -
-     Version: version-number
-
- -

-The version number for any package installed on your system can be obtained -using the command line -

- -
-     dpkg -s package-name
-
- -

-This section is referred to as the pseudo-header. The rest of the message -should contain the description of the bug (please make it moderately detailed), -the Debian release you are using, and versions of other relevant packages. The -Debian release number will be displayed by the command -

- -
-     cat /etc/debian_version
-
- -

-Expect to get an automatic acknowledgement of your bug report. It will also be -automatically given a bug tracking number, entered into the bug log and -forwarded to the debian-bugs-dist mailing list. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-support.html b/templates/common/doc/FAQ/html/ch-support.html deleted file mode 120000 index 978d556..0000000 --- a/templates/common/doc/FAQ/html/ch-support.html +++ /dev/null @@ -1 +0,0 @@ -ch-support.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/ch-uptodate.en.html b/templates/common/doc/FAQ/html/ch-uptodate.en.html deleted file mode 100644 index b271f29..0000000 --- a/templates/common/doc/FAQ/html/ch-uptodate.en.html +++ /dev/null @@ -1,479 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Keeping your Debian system up-to-date - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -
Chapter 8 - Keeping your Debian system up-to-date -

- -
- -

-A Debian goal is to provide a consistent upgrade path and a secure upgrade -process. We always do our best to make upgrading to new releases a smooth -procedure. In case there's some important note to add to the upgrade process, -the packages will alert the user, and often provide a solution to a possible -problem. -

- -

-You should also read the Release Notes document that describes the details of -specific upgrades. It is shipped on all Debian CDs and available on the WWW at -http://www.debian.org/releases/stable/releasenotes. -

- -
- -

8.1 How can I upgrade my Debian 1.3.1 (or earlier) distribution, based on libc5, to 2.0 (or later), based on libc6?

- -

-There are several ways to upgrade: -

- -
    -
  • -

    -Following closely the Debian -libc5 to libc6 Mini-HOWTO and upgrade the most important packages by -hand. autoup.sh is based on this Mini-HOWTO, so this method -should work more or less like using autoup.sh. -

    -
    • -
-
    -
  • -

    -Using a libc5-based apt. 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 dists/slink/main/upgrade-older-i386 directory at -the Debian archives. -

    -
    • -
-
    -
  • -

    -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. -

    -
    • -
- -
- -

8.2 How can I keep my Debian system current?

- -

-One could simply execute an anonymous ftp call to a Debian archive, then peruse -the directories until one finds the desired file, and then fetch it, and -finally install it using dpkg. Note that dpkg will -install upgrade files in place, even on a running system. Sometimes, a revised -package will require the installation of a newly revised version of another -package, in which case the installation will fail until/unless the other -package is installed. -

- -

-Many people find this approach much too time-consuming, since Debian evolves so -quickly -- typically, a dozen or more new packages are uploaded every week. -This number is larger just before a new major release. To deal with this -avalanche, many people prefer to use a more automated method. Several -different packages are available for this purpose: -

- -
- -

8.2.1 aptitude

- -

-APT is an advanced interface to the Debian packaging system. It features -complete installation ordering, multiple source capability and several other -unique features, see the User's Guide in -/usr/share/doc/apt-doc/guide.html/index.html (you will have to -install the apt-doc package). -

- -

-aptitude is the recommended package manager for Debian GNU/Linux -systems. It is a text-based interface to APT using the curses library, and can -be used to perform management tasks in a fast and easy way. -

- -

-Before you can use aptitude, you'll have to edit the -/etc/apt/sources.list file to set it up. If you wish to upgrade -to the latest stable version of Debian, you'll probably want to use a source -like this one: -

- -
-     http://http.us.debian.org/debian stable main contrib non-free
-
- -

-You can replace http.us.debian.org with the name of a faster Debian mirror near -you. See the mirror list at http://www.debian.org/misc/README.mirrors -for more information. -

- -

-More details on this can be found in the sources.list(8) manual -page. -

- -

-To update your system, run -

- -
-     aptitude update
-
- -

-followed by -

- -
-     aptitude dist-upgrade
-
- -

-Answer any questions that might come up, and your system will be upgraded. See -also aptitude, Section 7.1.3. -

- -
- -

8.2.2 apt-get, dselect and apt-cdrom

- -

-apt-get is an APT-based command-line tool for handling packages, -and the APT dselect method is an interface to APT through dselect. -Both of these provide a simple, safe way to install and upgrade packages. -

- -

-To use apt-get, install the apt package, and edit the -/etc/apt/sources.list file to set it up, just as for aptitude, Section 8.2.1. -

- -

-Then run -

- -
-     apt-get update
-
- -

-followed by -

- -
-     apt-get dist-upgrade
-
- -

-Answer any questions that might come up, and your system will be upgraded. See -also the apt-get(8) manual page, as well as APT, Section 7.1.2. -

- -

-To use APT with dselect, choose the APT access method in dselect's -method selection screen (option 0) and then specify the sources that should be -used. The configuration file is /etc/apt/sources.list. See also -dselect, Section 7.1.4. -

- -

-If you want to use CDs to install packages, you can use apt-cdrom. -For details, please see the Release Notes, section "Setting up for an -upgrade from a local mirror". -

- -

-Please note that when you get and install the packages, you'll still have them -kept in your /var directory hierarchy. To keep your partition from -overflowing, remember to delete extra files using apt-get clean -and apt-get autoclean, or to move them someplace else (hint: use -apt-move). -

- -
- -

8.2.3 dpkg-ftp

- -

-This is an older access method for dselect. It can be invoked -from within dselect, thereby allowing a user the ability to -download files and install them directly in one step. To do this, select the -ftp access method in dselect (option 0) and specify -the remote host name and directory. dpkg-ftp will then -automatically download the files that are selected (either in this session of -dselect or earlier ones). -

- -

-Note that, unlike the mirror program, dpkg-ftp does -not grab everything at a mirror site. Rather, it downloads only those files -which you have selected (when first starting up dpkg-ftp), and -which need to be updated. -

- -

-dpkg-ftp is somewhat obsolete. You should use the APT access -method with ftp:// URLs in sources.list instead. -

- -
- -

8.2.4 mirror

- -

-This Perl script, and its (optional) manager program called -mirror-master, can be used to fetch user-specified parts of a -directory tree from a specified host via anonymous FTP. -

- -

-mirror is particularly useful for downloading large volumes of -software. After the first time files have been downloaded from a site, a file -called .mirrorinfo is stored on the local host. Changes to the -remote file system are tracked automatically by mirror, which -compares this file to a similar file on the remote system and downloads only -changed files. -

- -

-The mirror program is generally useful for updating local copies -of remote directory trees. The files fetched need not be Debian files. (Since -mirror is a Perl script, it can also run on non-Unix systems.) -Though the mirror program provides mechanisms for excluding files -names of which match user-specified strings, this program is most useful when -the objective is to download whole directory trees, rather than selected -packages. -

- -
- -

8.2.5 dpkg-mountable

- -

-dpkg-mountable adds an access method called `mountable' to dselect's list, -which allows you to install from any file system specified in /etc/fstab. For -example, the archive could be a normal hard disk partition or an NFS server, -which it will automatically mount and umount for you if necessary. -

- -

-It also has some extra features not found in the standard dselect methods, such -as provision for a local file tree (either parallel to the main distribution or -totally separate), and only getting packages which are required, rather than -the time-consuming recursive directory scan, as well as logging of all dpkg -actions in the install method. -

- -
- -

8.3 Must I go into single user mode in order to upgrade a package?

- -

-No. Packages can be upgraded in place, even in running systems. Debian has a -start-stop-daemon program that is invoked to stop, then restart -running process if necessary during a package upgrade. -

- -
- -

8.4 Do I have to keep all those .deb archive files on my disk?

- -

-No. If you have downloaded the files to your disk (which is not absolutely -necessary, see above for the description of dpkg-ftp), then after you have -installed the packages, you can remove them from your system. -

- -
- -

8.5 How can I keep a log of the packages I added to the system? I'd like to know when which package upgrades and removals have occured!

- -

-Passing the --log-option to dpkg makes -dpkg log status change updates and actions. It logs both the -dpkg-invokation (e.g. -

- -
-     2005-12-30 18:10:33 install hello 1.3.18 2.1.1-4
-
- -

-) and the results (e.g. -

- -
-     2005-12-30 18:10:35 status installed hello 2.1.1-4
-
- -

-) If you'd like to log all your dpkg invokations (even those done -using frontends like aptitude), you could add -

- -
-     log /var/log/dpkg.log
-
- -

-to your /etc/dpkg/dpkg.cfg. Be sure the created logfile gets -rotated periodically. If you're using logrotate, this can be -achieved by creating a file /etc/logrotate.d/dpkg with contents -

- -
-     /var/log/dpkg {
-       missingok
-       notifempty
-     }
-
- -

-More details on dpkg logging can be found in the -dpkg(1) manual page. -

- -

-aptitude logs the package installations, removals, and upgrades -that it intends to perform to /var/log/aptitude. Note that the -results of those actions are not recorded in this file! -

- -

-Another way to record your actions is to run your package management session -within the script(1) program. -

- -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/ch-uptodate.html b/templates/common/doc/FAQ/html/ch-uptodate.html deleted file mode 120000 index 37f6852..0000000 --- a/templates/common/doc/FAQ/html/ch-uptodate.html +++ /dev/null @@ -1 +0,0 @@ -ch-uptodate.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/footnotes.en.html b/templates/common/doc/FAQ/html/footnotes.en.html deleted file mode 100644 index 0d5b7d4..0000000 --- a/templates/common/doc/FAQ/html/footnotes.en.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - Footnotes - - - - - -
- -

-The Debian GNU/Linux FAQ -
Footnotes

- -

1

- -

-When the present-day sid did not exist, the FTP site organization had one major -flaw: there was an assumption that when an architecture is created in the -current unstable, it will be released when that distribution becomes the new -stable. For many architectures that isn't the case, with the result that those -directories had to be moved at release time. This was impractical because the -move would chew up lots of bandwidth. -

- -

-The archive administrators worked around this problem for several years by -placing binaries for unreleased architectures in a special directory called -"sid". For those architectures not yet released, the first time they -were released there was a link from the current stable to sid, and from then on -they were created inside the unstable tree as normal. This layout was somewhat -confusing to users. -

- -

-With the advent of package pools (see What's in the -pool directory?, Section 5.10), binary packages began to be -stored in a canonical location in the pool, regardless of the distribution, so -releasing a distribution no longer causes large bandwidth consumption on the -mirrors (there is, however, a lot of gradual bandwidth consumption throughout -the development process). -

- -

2

- -

-dists/stable/main, dists/stable/contrib, -dists/stable/non-free, and dists/unstable/main/, etc. -

- -

3

- -

-Historically, packages were kept in the subdirectory of dists -corresponding to which distribution contained them. This turned out to cause -various problems, such as large bandwidth consumption on mirrors when major -changes were made. This was fixed with the introduction of the package pool. -

- -

-The dists directories are still used for the index files used by -programs like apt. You may also still see paths containing -dists/potato or dists/woody in the Filename header -field of some older packages. -

- -

4

- -

-Notice that there are ports that make this tool available with other package -management systems, like Red Hat package manager, also known as -rpm -

- -

5

- -

-Although this can also lead to systems with more packages installed than they -actually need to work. -

- -

6

- -

-Use the debian-list-subject-REQUEST@lists.debian.org address for -that. -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/footnotes.html b/templates/common/doc/FAQ/html/footnotes.html deleted file mode 120000 index c18fdfb..0000000 --- a/templates/common/doc/FAQ/html/footnotes.html +++ /dev/null @@ -1 +0,0 @@ -footnotes.en.html \ No newline at end of file diff --git a/templates/common/doc/FAQ/html/index.en.html b/templates/common/doc/FAQ/html/index.en.html deleted file mode 100644 index 952a225..0000000 --- a/templates/common/doc/FAQ/html/index.en.html +++ /dev/null @@ -1,311 +0,0 @@ - - - - - - - - -The Debian GNU/Linux FAQ - - - - - -

-
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
- -

Abstract

- -

-This document answers questions frequently asked about Debian GNU/Linux. -

- -
- -

Copyright Notice

- -

-Copyright © 1996-2005 by Software in the Public Interest -

- -

-Permission is granted to make and distribute verbatim copies of this document -provided the copyright notice and this permission notice are preserved on all -copies. -

- -

-Permission is granted to copy and distribute modified versions of this document -under the conditions for verbatim copying, provided that the entire resulting -derived work is distributed under the terms of a permission notice identical to -this one. -

- -

-Permission is granted to copy and distribute translations of this document into -another language, under the above conditions for modified versions, except that -this permission notice may be included in translations approved by the Free -Software Foundation instead of in the original English. -

- -
- -

Contents

- - - -
- -

-[ previous ] -[ Contents ] -[ 1 ] -[ 2 ] -[ 3 ] -[ 4 ] -[ 5 ] -[ 6 ] -[ 7 ] -[ 8 ] -[ 9 ] -[ 10 ] -[ 11 ] -[ 12 ] -[ 13 ] -[ 14 ] -[ 15 ] -[ next ] -

- -
- -

-The Debian GNU/Linux FAQ -

- -
-version 3.1.3, 25 April 2006
-
-Authors are listed at Debian FAQ Authors
-
-
-
- - - - - diff --git a/templates/common/doc/FAQ/html/index.html b/templates/common/doc/FAQ/html/index.html deleted file mode 120000 index 0e85422..0000000 --- a/templates/common/doc/FAQ/html/index.html +++ /dev/null @@ -1 +0,0 @@ -index.en.html \ No newline at end of file diff --git a/templates/common/doc/bug-log-access.txt b/templates/common/doc/bug-log-access.txt deleted file mode 100644 index c8fa75f..0000000 --- a/templates/common/doc/bug-log-access.txt +++ /dev/null @@ -1,55 +0,0 @@ -Methods of accessing the bug tracking system logs - -Accessing active bug reports - - Each message received at or sent by the bug processing system is - logged and made available in a number of ways. - - The primary access method is to use the web pages. See the forms on - the main BTS page at http://bugs.debian.org/ - - There is a mailserver which can send bug reports as plain text on - request. To use it send the word help as the sole contents of an email - to request@bugs.debian.org (the Subject of the message is ignored), or - read the instructions on the World Wide Web or in the file - bug-log-mailserver.txt. - -Accessing archived bug reports - - Each closed bug report is archived 28 days after the last message - relating to it is received and filed. This means that it is no longer - possible to access it or change anything about it using the control - and service bots. However, the reports are still accessible for - viewing. - - You can search the bug report archive using the WWW forms at - http://bugs.debian.org/, simply select the "archived bugs" option. - - Note that it doesn't contain the oldest closed bug reports, only those - after #40000, approximately. - -Accessing the raw bug data - - If you need to get hold of the raw data used by the bug tracking - system, you can mirror it using rsync from bugs-mirror.debian.org. The - relevant modules are bts-spool-db (for the active bug spool), - bts-spool-archive (for bugs that have been closed for a while and thus - archived), and bts-spool-index (for the bug index files). - - At the time of writing, the active spool is about 2.5GB and the - archived spool is about 10GB. If you only need a sample for testing - purposes, please consider downloading only part of the active spool - rather than the whole thing. - - Please do not rely on *.status files in the bug spools, as they are - obsolete, for compatibility purposes only, and will be removed at some - point in the future. Use the *.summary files instead. - _________________________________________________________________ - - Debian BTS administrators - - Debian bug tracking system - Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, - 1994-1997 Ian Jackson. - _________________________________________________________________ - diff --git a/templates/common/doc/bug-log-mailserver.txt b/templates/common/doc/bug-log-mailserver.txt deleted file mode 100644 index aa28efc..0000000 --- a/templates/common/doc/bug-log-mailserver.txt +++ /dev/null @@ -1,137 +0,0 @@ -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 - - Debian bug tracking system - Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, - 1994-1997 Ian Jackson. - _________________________________________________________________ - diff --git a/templates/common/doc/bug-mailserver-refcard.txt b/templates/common/doc/bug-mailserver-refcard.txt deleted file mode 100644 index b3ce545..0000000 --- a/templates/common/doc/bug-mailserver-refcard.txt +++ /dev/null @@ -1,81 +0,0 @@ -Mail servers' reference card - - Full documentation of the mail servers is available on the WWW, in the - files bug-log-mailserver.txt and bug-maint-mailcontrol.txt or by - sending the word help to each mailserver. - -Synopsis of commands available at request@bugs.debian.org - - * send bugnumber - * send-detail bugnumber - * index [full] - * index-summary by-package - * index-summary by-number - * index-maint - * index maint maintainer - * index-packages - * index packages package - * send-unmatched [this|0] - * send-unmatched last|-1 - * send-unmatched old|-2 - * getinfo filename (ftp.debian.org/debian/doc/*) - * help - * refcard - * quit|stop|thank...|--... - * #... (comment) - * debug level - -Synopsis of extra commands available at control@bugs.debian.org - - * reassign bugnumber package [ version ] - * severity bugnumber severity - * reopen bugnumber [ originator-address | = | ! ] - * found bugnumber [ version ] - * notfound bugnumber version - * submitter bugnumber originator-address | ! - * forwarded bugnumber address - * notforwarded bugnumber - * owner bugnumber address | ! - * noowner bugnumber - * retitle bugnumber new-title - * clone bugnumber NewID [ new IDs ... ] - * merge bugnumber bugnumber ... - * unmerge bugnumber - * forcemerge bugnumber bugnumber ... - * tag bugnumber [ + | - | = ] tag [ tag ... ] - * block bugnumber by bug ... - * unblock bugnumber by bug ... - * close bugnumber [ fixed-version ] (deprecated - you must - separately tell originator why, see "Closing bug reports" instead) - - reopen with = or no originator address leaves the originator as the - original submitter; ! sets it to you, the person doing the reopen. - - Severities are critical, grave, serious, important, normal, minor, and - wishlist. - - Tags currently include patch, wontfix, moreinfo, unreproducible, help, - pending, fixed, security, upstream, confirmed, fixed-upstream, - fixed-in-experimental, d-i, ipv6, lfs, l10n, potato, woody, sarge, - sarge-ignore, etch, etch-ignore, sid, and experimental. - -Synopsis of bug submission and followup addresses - - * nnn[ -submit | ] - * nnn-maintonly - * nnn-quiet - * nnn-forwarded - * nnn-request - * nnn-submitter - * nnn-done - * nnn-close - * nnn-subscribe - _________________________________________________________________ - - Debian BTS administrators - - Debian bug tracking system - Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, - 1994-1997 Ian Jackson. - _________________________________________________________________ - diff --git a/templates/common/doc/bug-maint-info.txt b/templates/common/doc/bug-maint-info.txt deleted file mode 100644 index 1a450eb..0000000 --- a/templates/common/doc/bug-maint-info.txt +++ /dev/null @@ -1,396 +0,0 @@ -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 - - Debian bug tracking system - Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, - 1994-1997 Ian Jackson. - _________________________________________________________________ - diff --git a/templates/common/doc/bug-maint-mailcontrol.txt b/templates/common/doc/bug-maint-mailcontrol.txt deleted file mode 100644 index 1167b10..0000000 --- a/templates/common/doc/bug-maint-mailcontrol.txt +++ /dev/null @@ -1,323 +0,0 @@ -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 - - Debian bug tracking system - Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, - 1994-1997 Ian Jackson. - _________________________________________________________________ - diff --git a/templates/common/doc/bug-reporting.txt b/templates/common/doc/bug-reporting.txt deleted file mode 100644 index ca14c2a..0000000 --- a/templates/common/doc/bug-reporting.txt +++ /dev/null @@ -1,304 +0,0 @@ -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 - # by sending e-mail to @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: - - Replace with the name of the package which has the bug. - - The second line of the message should say: -Version: - - Replace with the version of the package. Please don't - include any text here other than the version itself, as the bug - tracking system relies on this field to work out which releases are - affected by the bug. - - You need to supply a correct Package line in the pseudo-header in - order for the bug tracking system to deliver the message to the - package's maintainer. See this example for information on how to find - this information. - - 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: - - Replace 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: - - Replace 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 -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 - - Debian bug tracking system - Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, - 1994-1997 Ian Jackson. - _________________________________________________________________ - diff --git a/templates/common/doc/constitution.txt b/templates/common/doc/constitution.txt deleted file mode 100644 index 191f73b..0000000 --- a/templates/common/doc/constitution.txt +++ /dev/null @@ -1,603 +0,0 @@ - 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. diff --git a/templates/common/doc/debian-manifesto b/templates/common/doc/debian-manifesto deleted file mode 100644 index 9322c93..0000000 --- a/templates/common/doc/debian-manifesto +++ /dev/null @@ -1,135 +0,0 @@ -Please note that this document is provided in order to document -Debian's history. While the general ideas still apply some details -changed. - - -******************** -Appendix -The Debian Manifesto -******************** - - - The Debian Linux Manifesto - - Written by Ian A. Murdock - Revised 01/06/94 - - -What is Debian Linux? -===================== - -Debian Linux is a brand-new kind of Linux distribution. Rather than -being developed by one isolated individual or group, as other -distributions of Linux have been developed in the past, Debian is being -developed openly in the spirit of Linux and GNU. The primary purpose -of the Debian project is to finally create a distribution that lives up -to the Linux name. Debian is being carefully and conscientiously put -together and will be maintained and supported with similar care. - -It is also an attempt to create a non-commercial distribution that will -be able to effectively compete in the commercial market. It will -eventually be distributed by The Free Software Foundation on CD-ROM, -and The Debian Linux Association will offer the distribution on floppy -disk and tape along with printed manuals, technical support and other -end-user essentials. All of the above will be available at little more -than cost, and the excess will be put toward further development of -free software for all users. Such distribution is essential to the -success of the Linux operating system in the commercial market, and it -must be done by organizations in a position to successfully advance and -advocate free software without the pressure of profits or returns. - - -Why is Debian being constructed? -================================ - -Distributions are essential to the future of Linux. Essentially, they -eliminate the need for the user to locate, download, compile, install -and integrate a fairly large number of essential tools to assemble a -working Linux system. Instead, the burden of system construction is -placed on the distribution creator, whose work can be shared with -thousands of other users. Almost all users of Linux will get their -first taste of it through a distribution, and most users will continue -to use a distribution for the sake of convenience even after they are -familiar with the operating system. Thus, distributions play a very -important role indeed. - -Despite their obvious importance, distributions have attracted little -attention from developers. There is a simple reason for this: they are -neither easy nor glamorous to construct and require a great deal of -ongoing effort from the creator to keep the distribution bug-free and -up-to-date. It is one thing to put together a system from scratch; it -is quite another to ensure that the system is easy for others to -install, is installable and usable under a wide variety of hardware -configurations, contains software that others will find useful, and is -updated when the components themselves are improved. - -Many distributions have started out as fairly good systems, but as time -passes attention to maintaining the distribution becomes a secondary -concern. A case-in-point is the Softlanding Linux System (better known -as SLS). It is quite possibly the most bug-ridden and badly maintained -Linux distribution available; unfortunately, it is also quite possibly -the most popular. It is, without question, the distribution that -attracts the most attention from the many commercial "distributors" of -Linux that have surfaced to capitalize on the growing popularity of the -operating system. - -This is a bad combination indeed, as most people who obtain Linux from -these "distributors" receive a bug-ridden and badly maintained Linux -distribution. As if this wasn't bad enough, these "distributors" have -a disturbing tendency to misleadingly advertise non-functional or -extremely unstable "features" of their product. Combine this with the -fact that the buyers will, of course, expect the product to live up to -its advertisement and the fact that many may believe it to be a -commercial operating system (there is also a tendency not to mention -that Linux is free nor that it is distributed under the GNU General -Public License). To top it all off, these "distributors" are actually -making enough money from their effort to justify buying larger -advertisements in more magazines; it is the classic example of -unacceptable behavior being rewarded by those who simply do not know -any better. Clearly something needs to be done to remedy the -situation. - - -How will Debian attempt to put an end to these problems? -======================================================== - -The Debian design process is open to ensure that the system is of the -highest quality and that it reflects the needs of the user community. -By involving others with a wide range of abilities and backgrounds, -Debian is able to be developed in a modular fashion. Its components -are of high quality because those with expertise in a certain area are -given the opportunity to construct or maintain the individual -components of Debian involving that area. Involving others also -ensures that valuable suggestions for improvement can be incorporated -into the distribution during its development; thus, a distribution is -created based on the needs and wants of the users rather than the needs -and wants of the constructor. It is very difficult for one individual -or small group to anticipate these needs and wants in advance without -direct input from others. - -Debian Linux will also be distributed on physical media by the Free -Software Foundation and the Debian Linux Association. This provides -Debian to users without access to the Internet or FTP and additionally -makes products and services such as printed manuals and technical -support available to all users of the system. In this way, Debian may -be used by many more individuals and organizations than is otherwise -possible, the focus will be on providing a first-class product and not -on profits or returns, and the margin from the products and services -provided may be used to improve the software itself for all users -whether they paid to obtain it or not. - -The Free Software Foundation plays an extremely important role in the -future of Debian. By the simple fact that they will be distributing -it, a message is sent to the world that Linux is not a commercial -product and that it never should be, but that this does not mean that -Linux will never be able to compete commercially. For those of you who -disagree, I challenge you to rationalize the success of GNU Emacs and -GCC, which are not commercial software but which have had quite an -impact on the commercial market regardless of that fact. - -The time has come to concentrate on the future of Linux rather than on -the destructive goal of enriching oneself at the expense of the entire -Linux community and its future. The development and distribution of -Debian may not be the answer to the problems that I have outlined in -the Manifesto, but I hope that it will at least attract enough -attention to these problems to allow them to be solved. diff --git a/templates/common/doc/mailing-lists.txt b/templates/common/doc/mailing-lists.txt deleted file mode 100644 index 2d92973..0000000 --- a/templates/common/doc/mailing-lists.txt +++ /dev/null @@ -1,1649 +0,0 @@ - Introduction to the Debian mailing lists - ======================================== - - Debian GNU/Linux is developed through distributed development all - around the world. Therefore, email is the preferred way to discuss - various items. Much of the conversation between Debian developers - and users is managed through several mailing lists. - - There are many world-open mailing lists, meaning anyone can read - everything that is posted, and participate in the discussions. Everyone is - encouraged to help development of Debian and to spread the word of free - software. There are also a few lists which are only open to official Debian - developers; please don't interpret this as closed development, it sometimes - doesn't make much sense discussing internal topics with non-developers. - - All original Debian mailing lists run on a special server, using an - automatic mail processing software called SmartList. This server is called - lists.debian.org. All submission, subscription and unsubscription messages - have to be sent to a particular address at this host. - - The language used on all lists is English, unless stated otherwise. - There are some user lists for other languages available. - -Subscription / Unsubscription ------------------------------ - - Anyone is able to subscribe/unsubscribe on their own to any mailing list, - presuming the subscription policy for a particular list is `open'. - - The requests for subscription or unsubscription can be sent to a special - control address, which is slightly different from the list address. - Subscription or unsubscription messages should NOT be sent to the address - of the mailing list itself. - - To subscribe or unsubscribe from a mailing list, please send mail to - - -REQUEST@lists.debian.org - - with the word `subscribe' or `unsubscribe' as subject. - - Please remember the -REQUEST part of the address. - - As part of the subscription process, the list software will send you an - email to which you must reply in order to finish subscribing. This is a - security measure to keep people from subscribing others to the lists without - their permission. - - If you need to contact a human listmaster, direct your mail to - listmaster@lists.debian.org . To find out who is responsible for the - lists, take a look at http://www.debian.org/intro/organization - -User lists - - There are several user based mailing lists where developers and - users can get in contact to discuss and solve problems. - - debian-announce@lists.debian.org - - Description : Major news and very important changes in the project - are announced here. - Moderated : yes - Subscription: open - - debian-chinese-big5@lists.debian.org - - Description : Debian Chinese Project: Chinese localization (l10n), - documentation and web site translation, user support - etc. - - Posts may be in English or Big5-encoded Chinese. - All posts are automatically converted to GB encoding - and cross-posted to the debian-chinese-gb mailing list. - - If you would rather read and post in GB-encoded - Chinese, please subscribe to debian-chinese-gb instead. - Language : Chinese - Moderated : subscribers - Subscription: open - - debian-chinese-gb@lists.debian.org - - Description : Debian Chinese Project: Chinese localization (l10n) - issues, documentation and web site translation, user - support etc. - - Posts may be in English or GB-encoded Chinese. - All posts are automatically converted to Big5 encoding - and cross-posted to the debian-chinese-big5 mailing list. - - If you would rather read and post in Big5-encoded - Chinese, please subscribe to debian-chinese-big5 instead. - Language : Chinese - Moderated : subscribers - Subscription: open - - debian-commercial@lists.debian.org - - Description : Information about Debian related products from - software and hardware vendors is published here. - This is a moderated list, so please send your - submissions to the moderator at press@debian.org. - - Please note that posting commercial posts to any - other Debian mailing list is not permitted. - Moderated : yes - Subscription: open - - debian-esperanto@lists.debian.org - - Description : Debian users who speak Esperanto. - Language : Esperanto - Moderated : no - Subscription: open - - debian-firewall@lists.debian.org - - Description : Discussion of implementation and maintenance of - firewalls using Debian. Both basic issues and new - more exotic developments are discussed here. - Moderated : no - Subscription: open - - debian-isp@lists.debian.org - - Description : Discussion about issues and problems specific to - Internet Service Providers (ISPs for short) that - use Debian. - Moderated : no - Subscription: open - - debian-italian@lists.debian.org - - Description : Support for Debian users that speak Italian. - (High-volume mailing list.) - Language : Italian - Moderated : no - Subscription: open - - debian-japanese@lists.debian.org - - Description : Support for Debian users that speak Japanese, - Japanese localization issues, integrating - Debian JP packages into Debian etc. - - The English language is allowed, but using Japanese is - encouraged even for those who aren't native speakers. - - For native Japanese, Debian JP Project provides - several mailing lists discussing the Debian system in - Japanese, see http://www.debian.or.jp/MailingList.html - Language : English/Japanese - Moderated : no - Subscription: open - - debian-kde@lists.debian.org - - Description : Discussions related to KDE in Debian. - Those developing KDE-based packages are - encouraged to use this to discuss issues - and share their experience. - Moderated : no - Subscription: open - - debian-laptop@lists.debian.org - - Description : Installing, updating and using laptops with Debian. - Suggestions on special packaging, complaints, etc. - are welcome. - Moderated : no - Subscription: open - - debian-news-french@lists.debian.org - - Description : News about Debian for users speaking French. - Language : French - Moderated : yes - Subscription: open - - debian-news-german@lists.debian.org - - Description : News about Debian for users speaking German. - Language : German - Moderated : yes - Subscription: open - - debian-news-italian@lists.debian.org - - Description : Releases, news, internationalization efforts and - other related news about Debian for Italian-speaking users. - Language : Italian - Moderated : yes - Subscription: open - - debian-news-portuguese@lists.debian.org - - Description : Releases, news, internationalization efforts and other - related news about Debian for users speaking Portuguese. - Language : Portuguese - Moderated : yes - Subscription: open - - debian-news-spanish@lists.debian.org - - Description : Releases, news, internationalization efforts and - other related news about Debian for Spanish-speaking users. - Language : Spanish - Moderated : yes - Subscription: open - - debian-news@lists.debian.org - - Description : General news about the distribution and the project. - - The current events and news about Debian are - summarized in the Debian Weekly News, a newsletter - regularly posted on this list. - Moderated : yes - Subscription: open - - debian-russian@lists.debian.org - - Description : Support for Debian users that speak Russian, - and Russian localization issues: translating - "po" files, coordinating patches for Debian - packages to work with the Russian language. - Language : Russian - Moderated : no - Subscription: open - - debian-security-announce@lists.debian.org - - Description : The security team informs the users about security - problems by posting security advisories about - Debian packages on this list. - Moderated : yes - Subscription: open - - debian-user-catalan@lists.debian.org - - Description : Support for Debian users that speak Catalan. - Language : Catalan - Moderated : no - Subscription: open - - debian-user-danish@lists.debian.org - - Description : Support for Debian users who speak Danish. - Language : Danish - Moderated : no - Subscription: open - - debian-user-french@lists.debian.org - - Description : Support for Debian users that speak French. - (High-volume mailing list.) - Language : French - Moderated : no - Subscription: open - - debian-user-german@lists.debian.org - - Description : Support for Debian users that speak German. - (High-volume mailing list.) - Language : German - Moderated : no - Subscription: open - - debian-user-hungarian - - Description : Support for Debian users that speak Hungarian. - Language : Hungarian - Subscription: http://lists.linux.hu/mailman/listinfo/debian - - debian-user-icelandic@lists.debian.org - - Description : Support for Debian users that speak Icelandic. - Moderated : no - Subscription: open - - debian-user-indonesian@lists.debian.org - - Description : Support for Debian users who speak Indonesian. - Language : Indonesian - Moderated : no - Subscription: open - - debian-user-polish@lists.debian.org - - Description : Support for Debian users that speak Polish. - Language : Polish - Moderated : no - Subscription: open - - debian-user-portuguese@lists.debian.org - - Description : Support for Debian users who speak Portuguese. - (High-volume mailing list.) - Language : Portuguese (both European and Brazilian, and other dialects are welcome) - Moderated : no - Subscription: open - - debian-user-spanish@lists.debian.org - - Description : Support for Debian users that speak Spanish. - (High-volume mailing list.) - Language : Spanish - Moderated : no - Subscription: open - - debian-user-swedish@lists.debian.org - - Description : Support for Debian users that speak Swedish. - Language : Swedish - Moderated : no - Subscription: open - - debian-user-turkish@lists.debian.org - - Description : Support for Debian users that speak Turkish. - Language : Turkish - Moderated : no - Subscription: open - - debian-user-ukrainian@lists.debian.org - - Description : Support for Debian users who speak Ukrainian. - Language : Ukrainian - Moderated : no - Subscription: open - - debian-user-vietnamese@lists.debian.org - - Description : Support for Debian users that speak Vietnamese, and discussions on translations - Language : Vietnamese - Moderated : no - Subscription: open - - debian-user@lists.debian.org - - Description : Support for Debian users who speak English. - (High-volume mailing list.) - Digest : debian-user-digest@lists.debian.org - Moderated : no - Subscription: open - - debian-volatile-announce@lists.debian.org - - Description : Announcements relating to the debian-volatile project include new uploads and changes - Moderated : yes - Subscription: open - - debian-volatile@lists.debian.org - - Description : Discussion about the debian-volatile archive - Moderated : no - Subscription: open - -Development lists - - There are several lists on which developers and experienced - users discuss more technical issues. In addition, there are some - announcement lists to help experienced users keep track of - development. - - debian-accessibility@lists.debian.org - - Description : User and Developer list for accessibility-related issues. - Moderated : no - Subscription: open - - debian-admin@lists.debian.org - - Description : This is our internal list used for administering the - Debian machine park. - Moderated : no - Subscription: closed - - debian-apache@lists.debian.org - - Description : Maintenance of the Apache HTTP server and related - packages in Debian: code changes, reproducing bugs, - talking to upstream etc. - - It is neither for submitting bug reports (please - use the BTS for that), nor for support requests. - Moderated : no - Subscription: open - - debian-beowulf@lists.debian.org - - Description : Discussion about Beowulf systems running Debian. - Moderated : no - Subscription: open - - debian-boot@lists.debian.org - - Description : Discussion and maintenance of the Debian - installation system. - Moderated : no - Subscription: open - - debian-cd@lists.debian.org - - Description : Creating Debian CD sets, official and unofficial. - Moderated : no - Subscription: open - - debian-ctte-private@lists.debian.org - - Description : Private communication between tech committee members. - Moderated : no - Subscription: Debian Technical Committee only - - debian-ctte@lists.debian.org - - Description : Public meeting, business and announcements of the Debian - Technical Committee - Moderated : subscribers - Subscription: open - - debian-custom@lists.debian.org - - Description : People on this list work on the challenges common to - all custom Debian distributions, ensuring that the - tools and procedures developed are shared, making - the most efficient use of our energies. - Moderated : no - Subscription: open - - debian-dak@lists.debian.org - - Description : Discussion about the Debian Archive Software, consisting of dak for the - archive and the buildd related parts wanna-build/sbuild. - Moderated : no - Subscription: open - - debian-ddtp@lists.debian.org - - Description : Discussions on the DDTP and coordination of the development process - Moderated : no - Subscription: open - - debian-debbugs-cvs@lists.debian.org - - Description : CVS commit messages when modifications are done to - debbugs - Moderated : no - Subscription: open - - debian-debbugs@lists.debian.org - - Description : Discussion and development of debbugs, the Debian - Bug Tracking System software. - Moderated : no - Subscription: open - - debian-desktop@lists.debian.org - - Description : Discussion about the Debian Desktop sub-project, - the integration of the various desktop-related - packages, bug reports, questions and patches. - Moderated : no - Subscription: open - - debian-devel-announce@lists.debian.org - - Description : Announcements of development issues like policy changes, - important release issues &c. - Moderated : signed - Subscription: open - - debian-devel-austrian - - Description : Discussion among the Debian developers in Austria. - Language : (mostly) German - Subscription: https://www.gibraltar.at/mailman/listinfo/debian-at - - debian-devel-french@lists.debian.org - - Description : This is the list used to discuss development - issues in French. - Moderated : no - Subscription: open - - debian-devel-games@lists.debian.org - - Description : Development and packaging discussion for games and game-related software in Debian. - Identification of potential new games suitable for Debian. Discussion about - infrastructure issues covering a wider range of games (e.g. multiplayer issues). - Moderated : no - Subscription: open - - debian-devel-italian@lists.debian.org - - Description : Discussion on development issues in Italian. - Moderated : no - Subscription: open - - debian-devel-portuguese@lists.debian.org - - Description : This is the list used by Portuguese developers - (or wannabes) to discuss development issues. - Moderated : no - Subscription: open - - debian-devel-spanish@lists.debian.org - - Description : This is the list used by Spanish developers - (or wannabes) to discuss issues besides - translation: provide help for new Spanish - developers, arrange key-signing meetings, arrange - work in booths on different shows, share experience - etc. - Moderated : no - Subscription: open - - debian-devel@lists.debian.org - - Description : Discussion about technical development topics. - (High-volume mailing list.) - Digest : debian-devel-digest@lists.debian.org - Moderated : no - Subscription: open - - debian-doc@lists.debian.org - - Description : Debian Documentation Project: anything related - to documentation in Debian is on topic here. - Moderated : no - Subscription: open - - debian-dpkg-bugs@lists.debian.org - - Description : Email sent by the bug tracking system regarding - the dpkg packages. - Moderated : no - Subscription: open - - debian-dpkg-cvs@lists.debian.org - - Description : The CVS commit messages from the dpkg CVS tree. - Moderated : no - Subscription: open - - debian-dpkg@lists.debian.org - - Description : Discussions and maintenance of dpkg, the basis of - the Debian packaging system. - Moderated : no - Subscription: open - - debian-edu-french@lists.debian.org - - Description : Discussions in french between all educational Debian-based projects. - This list should ease the collaboration between the projects themselves - and between Debian and those projects. - Moderated : no - Subscription: open - - debian-edu@lists.debian.org - - Description : Making Debian the best distribution in the - education landscape. - Moderated : no - Subscription: open - - debian-emacsen@lists.debian.org - - Description : Discussion of all things related to the several - Debian Emacs packages and their add-ons. - Moderated : no - Subscription: open - - debian-email@lists.debian.org - - Description : A generic "grab-bag" list for Debian related - correspondence such as contacting upstream authors - about licenses, bugs etc, or discussing the project - with others where it might be useful to have the - discussion archived somewhere. - - This list is archived internally on a Debian Project - machine, only developers have access to the archive. - Moderated : no - Subscription: developers only - - debian-embedded@lists.debian.org - - Description : Discussion about improving Debian for use with - embedded systems, including building cross-compiler - toolchains, cross-compiling packages, creating and - updating system images, using alternate libraries, - compile-time configuration of packages, etc. - Moderated : no - Subscription: open - - debian-events-eu@lists.debian.org - - Description : Discussions and organizational stuff about booths for - Debian at european exhibitions. - Moderated : no - Subscription: open - - debian-events-na@lists.debian.org - - Description : Discussions and organizational stuff about booths and - presentations for Debian at North American exhibitions. - Moderated : no - Subscription: open - - debian-events-nl@lists.debian.org - - Description : Announcements of small meetings and keysigning parties of Dutch - Debian Developers and other discussions of interest mainly for - Debian people in the Netherlands. Posts in both Dutch and English - are common. - Moderated : no - Subscription: open - - debian-flash@lists.debian.org - - Description : For discussion of issues relating to the development and use of Debian for - Flash development and viewing of Flash content. For general discussion of Flash - related free software, please visit the osflash community: http://osflash.org - Moderated : no - Subscription: open - - debian-gcc@lists.debian.org - - Description : Discussion on Debian packaging of GCC, the - GNU compiler collection: bug reports, porting - issues, any kind of questions or patches. - Moderated : no - Subscription: open - - debian-glibc@lists.debian.org - - Description : Discussion on Debian packaging of the GNU C Library, - the most important library on Debian systems. - Moderated : no - Subscription: open - - debian-gtk-gnome@lists.debian.org - - Description : Discussion and coordination among maintainers of - Debian's GTK+, GNOME and dependent or related - packages. - Moderated : no - Subscription: open - - debian-hams@lists.debian.org - - Description : Support for HAMRadio within Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-handheld@lists.debian.org - - Description : Discussion among people who run Debian on - handheld computers. - Moderated : no - Subscription: open - - debian-ipv6@lists.debian.org - - Description : Discussions on the use of Debian in an IPv6 network - and implementing IPv6 support in Debian packages. - Moderated : no - Subscription: open - - debian-java@lists.debian.org - - Description : Discussion about the packaging and use in Debian of VMs - and compilers for the Java(tm) language, and programs - written on it. - Moderated : no - Subscription: open - - debian-jr@lists.debian.org - - Description : Discussion and working on making Debian the sort - of operating system that children will want to use. - - The Debian Jr. Project web page is at - http://www.debian.org/devel/debian-jr/ - Moderated : no - Subscription: open - - debian-kernel@lists.debian.org - - Description : Discussion about kernels used with Debian (Linux, Hurd, - etc.), available patches and flavors, packaging issues, - bug reports, porting issues, automated tools, and any - other questions or patches that are kernel-related. - Moderated : no - Subscription: open - - debian-knoppix@lists.debian.org - - Description : Development of the Debian-based live CD/DVD takes place. As it is mainly a - development list, user questions are best placed on the debian-user list. - Moderated : no - Subscription: open - - debian-lex@lists.debian.org - - Description : Discussion on developing Debian into an operating - system that is particularly well fit for the - requirements for legal offices. The goal of - Debian-Lex is a complete system for all tasks in - legal practice which is built completely on free - software. - Moderated : no - Subscription: open - - debian-lint-maint@lists.debian.org - - Description : The maintenance of Debian "lint" tools like lintian or linda - is discussed on this list. This may or may not be limited to - bug reports regarding the checks. - Moderated : no - Subscription: open - - debian-lsb@lists.debian.org - - Description : Discussion and coordination of efforts towards ensuring - Debian meets the requirements of the Linux Standard Base. - Moderated : no - Subscription: open - - debian-med@lists.debian.org - - Description : Discussion on providing a free operating system - for medical care. - - The Debian-Med Project web page is at - http://www.debian.org/devel/debian-med/ - Moderated : no - Subscription: open - - debian-mentors@lists.debian.org - - Description : Newbie Debian developers can seek help with - packaging and other developer-related issues here. - - This list is not meant for users' questions, - but for new maintainers'! - Moderated : no - Subscription: open - - debian-multimedia@lists.debian.org - - Description : Discussion about the development of applications - that produce multimedia content, handling multimedia - data, supporting multimedia hardware etc. - Moderated : no - Subscription: open - - debian-newmaint@lists.debian.org - - Description : Discussion about the Debian New Maintainer process, - application manager reports etc. - Moderated : no - Subscription: open - - debian-nonprofit@lists.debian.org - - Description : Discussions about the subproject to support - use of Debian in non-profit organizations. - Moderated : no - Subscription: open - - debian-ocaml-maint@lists.debian.org - - Description : Packaging of Objective Caml programs and libraries. - (http://pauillac.inria.fr/caml/) - Moderated : no - Subscription: open - - debian-openoffice@lists.debian.org - - Description : Coordination of the maintenance of the OpenOffice - packages in Debian. - Moderated : no - Subscription: open - - debian-perl@lists.debian.org - - Description : The list is dedicated to coordinate the work of various - perl package maintainer and to write a kind of perl - sub-policy. - Moderated : no - Subscription: open - - debian-policy@lists.debian.org - - Description : Discussion and editing of the Debian Policy Manual. - Moderated : no - Subscription: open - - debian-printing@lists.debian.org - - Description : Discussion of issues related to printing on Debian systems. This - covers all aspects of printing, from spoolers, to RIPs and printer - drivers. The list is used for coordination of development, - integration and bugfixing of printing packages between package - maintainers. User printing and printing setup questions are also - on topic. - Moderated : no - Subscription: open - - debian-private@lists.debian.org - - Description : Private discussions among developers: only for - issues that may not be discussed on public lists. - - Anything sent there should be treated as sensitive - and not to be spread to other lists; thus - cross-posting between it and an open list defeats - the purpose of this list. - - This list is archived internally on a Debian Project - machine, only developers have access to the archive. - Moderated : no - Subscription: developers only - - debian-python@lists.debian.org - - Description : Discussion of issues related to Python on Debian - systems with a stress on packaging standards. Therefore - relevant for maintainers of Python related packages. - Moderated : no - Subscription: open - - debian-qa-packages@lists.debian.org - - Description : Bug reports against orphaned packages and discussions - about fixing them. - Moderated : no - Subscription: open - - debian-qa@lists.debian.org - - Description : Quality assurance is important for a distribution. This - list addresses this quality. - Moderated : no - Subscription: open - - debian-qt-kde@lists.debian.org - - Description : Discussion and coordination among maintainers of - Debian's Qt, KDE and dependent or related packages. - Moderated : no - Subscription: open - - debian-release@lists.debian.org - - Description : Coordination of Debian releases issues such as testing migrations, transitions - and removals. - - This list should not be considered a discussion list; discussions related to - releases issues should be held on more appropriate lists such as debian-devel, - debian-legal or debian-project. - Moderated : no - Subscription: open - - debian-ruby@lists.debian.org - - Description : Discussion of issues related to Ruby on Debian systems - with a stress on packaging standards. Therefore - relevant for maintainers of Ruby related packages. - Moderated : no - Subscription: open - - debian-science@lists.debian.org - - Description : Discussion of issues relating to the use of Debian for science research, - including useful packages, particular problems faced by scientists using - Debian, how to make Debian more useful to scientists, etc. - Moderated : no - Subscription: open - - debian-security@lists.debian.org - - Description : Discussion about security issues, including - cryptographic issues, that are of interest to - all parts of the Debian community. - - Please note that this is NOT an announcement - mailing list. If you're looking for security - advisories from Debian, subscribe to - debian-security-announce instead. - Moderated : no - Subscription: open - - debian-sgml@lists.debian.org - - Description : Discussion of issues related to SGML on Debian systems - with a stress on proper integration of tools, packaging - standards and the writing of documentation for SGML - users. Therefore relevant for maintainers of SGML - related packages. - Moderated : no - Subscription: open - - debian-ssh@lists.debian.org - - Description : Maintenance of the OpenSSH packages for Debian. - It exists to facilitate coordination of ssh - maintenance (talking to upstream, reproducing bugs, - hacking on the code, etc.). - - It is *not* the place to mail bug reports - (use the BTS for that), nor support requests. - Moderated : no - Subscription: open - - debian-testing@lists.debian.org - - Description : Finding problems with the next Debian release: - testing the installation and the upgrade process. - Moderated : no - Subscription: open - - debian-tetex-maint@lists.debian.org - - Description : Coordination of the maintenance of Debian teTeX - and related packages. - - It is not meant for user support; for that, please - use debian-user or one of the general TeX mailing - lists or news groups. - Moderated : no - Subscription: open - - debian-tex-maint@lists.debian.org - - Description : Coordination of the maintenance of Debian TeX - and related packages. - - It is not meant for user support; for that, please - use debian-user or one of the general TeX mailing - lists or news groups. - Moderated : no - Subscription: open - - debian-toolchain@lists.debian.org - - Description : Discussion about the Debian toolchain: compilers, - assemblers, linkers and such. New releases for - many of these tools are coordinated here. - Moderated : no - Subscription: open - - debian-vote@lists.debian.org - - Description : Proposals, discussions and announcements related to - Official Debian Votes. - Moderated : no - Subscription: open - - debian-webapps@lists.debian.org - - Description : This list is used to coordinate the maintenance of web application packages. - Moderated : no - Subscription: open - - debian-wnpp@lists.debian.org - - Description : Orphaning and adopting packages which is done through - the `wnpp' BTS pseudo-package is recorded on this - list. Additionally, discussion about particular bugs - and the WNPP web pages is held here. - Moderated : no - Subscription: open - - debian-www-cvs@lists.debian.org - - Description : CVS commit logs for the Debian web pages in the - webwml CVS tree. - Moderated : yes - Subscription: open - - debian-www@lists.debian.org - - Description : Design, structure and translation of Debian - web pages. All important changes to the web - site are announced here as well. - Moderated : no - Subscription: open - - debian-x@lists.debian.org - - Description : Discussion about the X Window System within Debian. - This is NOT a user support list; this list is - intended for those who deal with the source code. - Moderated : no - Subscription: open - - deity@lists.debian.org - - Description : Debian GNU/Linux will get a new, friendly frontend to - its package maintenance system. Its codename is deity - (now known as APT) and its development is discussed - here. The -digest is open to everyone. - Moderated : no - Subscription: open - -Internationalization and Translations - - These lists cover issues like localization, translation and support for - users that don't speak English. - - debian-i18n@lists.debian.org - - Description : Internationalization (i18n) of the distribution is - discussed here. - Moderated : no - Subscription: open - - debian-l10n-arabic@lists.debian.org - - Description : Discussing Arabic localization issues, mainly - translating Debian docs and programs to Arabic. - Language : Arabic - Moderated : no - Subscription: open - - debian-l10n-catalan@lists.debian.org - - Description : Discussing Catalan localization issues, mainly - translating Debian docs and programs to Catalan. - Language : Catalan - Moderated : no - Subscription: open - - debian-l10n-czech@lists.debian.org - - Description : Discussion forum for the translators of - Debian-specific packages and documentation to the Czech language. - Moderated : no - Subscription: open - - debian-l10n-danish@lists.debian.org - - Description : Discussing Danish localization issues, mainly - translating Debian docs and programs to Danish. - Language : Danish - Moderated : no - Subscription: open - - debian-l10n-dutch@lists.debian.org - - Description : Discussion forum for the translators of Debian-specific - packages and documentation to the Dutch language. - Language : Dutch - Moderated : no - Subscription: open - - debian-l10n-english@lists.debian.org - - Description : Discussing English localization issues, mainly - translating Debian docs and programs to English. - Language : English - Moderated : no - Subscription: open - - debian-l10n-esperanto@lists.debian.org - - Description : Discussing Esperanto localization issues, mainly - translating Debian docs and programs to Esperanto. - Language : Esperanto - Moderated : no - Subscription: open - - debian-l10n-finnish@lists.debian.org - - Description : Discussing Finnish localization issues, mainly - translating Debian docs and programs to Finnish. - Language : Finnish - Moderated : no - Subscription: open - - debian-l10n-french@lists.debian.org - - Description : Discussion forum for the translators of Debian-specific - packages and documentation to the French language. - Language : French - Moderated : no - Subscription: open - - debian-l10n-german@lists.debian.org - - Description : Discussing German localization issues, mainly - translating Debian docs and programs to German. - Language : German - Moderated : no - Subscription: open - - debian-l10n-greek@lists.debian.org - - Description : Discussion on Greek localization issues, mainly - translating Debian docs and programs to Greek. - Language : Greek - Moderated : no - Subscription: open - - debian-l10n-hungarian@lists.debian.org - - Description : Discussing Hungarian localization issues, mainly - translating Debian docs and programs to Hungarian. - Language : Hungarian - Moderated : no - Subscription: open - - debian-l10n-italian@lists.debian.org - - Description : Italian localization efforts within Debian. - Language : Italian - Moderated : no - Subscription: open - - debian-l10n-korean@lists.debian.org - - Description : Discussion forum for the translators of Debian-specific packages and - documentation to the Korean language. - Moderated : no - Subscription: open - - debian-l10n-polish@lists.debian.org - - Description : Polish localization issues, mainly translating Debian - web pages, documentation and programs to Polish. - Language : Polish - Moderated : no - Subscription: open - - debian-l10n-portuguese@lists.debian.org - - Description : Portuguese localization issues such as translating - the documentation and programs. - Language : Portuguese - Moderated : no - Subscription: open - - debian-l10n-romanian@lists.debian.org - - Description : Discussing Romanian localization issues, mainly - translating Debian docs and programs to Romanian. - Language : Romanian - Moderated : no - Subscription: open - - debian-l10n-russian@lists.debian.org - - Description : Discussing Russian localization issues, mainly - translating Debian docs and programs to Russian. - Language : Russian - Moderated : no - Subscription: open - - debian-l10n-spanish@lists.debian.org - - Description : Discussing Spanish localization issues, mainly - translating Debian docs and programs to Spanish. - Language : Spanish - Moderated : no - Subscription: open - - debian-l10n-swedish@lists.debian.org - - Description : Discussion forum for translators of Debian-specific packages - and documentation for the Swedish language. - Moderated : no - Subscription: open - - debian-l10n-turkish@lists.debian.org - - Description : Discussing Turkish localization issues, mainly - translating Debian docs and website into Turkish, - improving Turkish environment support in Debian. - Language : Turkish - Moderated : no - Subscription: open - - debian-laespiral@lists.debian.org - - Description : La Espiral (http://laespiral.org/) is a project - meant to promote the use of Debian amongst the - people who speak Spanish. We work on custom - Debian internationalisation CDs, do installation - parties and new programs for Spanish users (see - http://www.debian.org/international/spanish/). - - Becoming a member of La Espiral is for people - that do not find themselves able to contribute - technically to Debian (at first), but might be a - good step towards becoming a Debian developer. - Language : Spanish - Moderated : no - Subscription: open - -Ports to non-i386 Linux architectures and to non-Linux kernels - - Debian GNU/Linux is ported to several other types of computers, and there - are also efforts to create Debian systems on kernels other than Linux. - - debian-68k@lists.debian.org - - Description : Discussions on the m68k port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-alpha@lists.debian.org - - Description : Discussion on the Alpha port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-amd64@lists.debian.org - - Description : Porting Debian to AMD x86-64 architecture. - Moderated : no - Subscription: open - - debian-arm@lists.debian.org - - Description : Discussion on the ARM (esp. Corel Netwinder) port for - Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-bsd@lists.debian.org - - Description : Porting Debian to BSD (all *BSD variants). - Moderated : no - Subscription: open - - debian-hppa@lists.debian.org - - Description : Discussions on the PA-RISC port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-hurd@lists.debian.org - - Description : Debian port of the GNU Hurd operating system. - Moderated : no - Subscription: open - - debian-ia64@lists.debian.org - - Description : Discussions on the intel IA64 (aka Itanium, Merced) - port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-mips@lists.debian.org - - Description : Discussions on the MIPS port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-powerpc@lists.debian.org - - Description : Discussion on the PowerPC port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-s390@lists.debian.org - - Description : Discussions on the IBM S/390 port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-sparc@lists.debian.org - - Description : Discussions on the SPARC port of Debian GNU/Linux. - Moderated : no - Subscription: open - - debian-superh@lists.debian.org - - Description : Discussions on the SuperH port of Debian GNU/Linux. For - more information about running Linux on SH processors, - have a look at http://www.m17n.org/linux-sh/ - Moderated : no - Subscription: open - - debian-win32@lists.debian.org - - Description : Porting the Debian distribution to Win32 systems - (Debian GNU/Win32). - Moderated : no - Subscription: open - -The Bug Tracking System - - The Debian bug tracking system is open to the public, and it produces - a lot of email. Some of this might be of interest to developers or even - users, so it is distributed through these (high-volume) mailing lists. - - debian-bugs-closed@lists.debian.org - - Description : Messages that close Debian bug reports. - Moderated : no - Subscription: open - - debian-bugs-dist@lists.debian.org - - Description : All submitted bug reports as well as further information - on them are distributed here. - Moderated : no - Subscription: open - - debian-bugs-forwarded@lists.debian.org - - Description : Mails in which Debian maintainers forward bugs - to their upstream authors. - Moderated : no - Subscription: open - - debian-bugs-rc@lists.debian.org - - Description : All mail regarding release-critical bugs is - copied to this mailing list. - - See http://bugs.debian.org/release-critical/ - for more information. - Moderated : no - Subscription: open - -Miscellaneous Debian lists - - There are several mailing lists which don't - necessarily have a clear distinction in the - audience, between developers and users. - - debian-all-changes@lists.debian.org - - Description : Notices about uploaded binary-all packages for the - stable distribution. - Moderated : no - Subscription: open - - debian-alpha-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable alpha - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-arm-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable arm - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-cd-vendors@lists.debian.org - - Description : Communication among and with vendors of Debian CDs. - (Low-volume mailing list.) - Moderated : no - Subscription: open - - debian-changes@lists.debian.org - - Description : Changes to the releases are announced here. This - includes security upgrades as well as important - bugfixes. - Digest : debian-changes-digest@lists.debian.org - Moderated : yes - Subscription: open - - debian-consultants@lists.debian.org - - Description : Communication among Debian consultants. See at the bottom of the - consultants page (http://www.debian.org/consultants/#policy) for how - to add/update entries to this page. - Moderated : no - Subscription: open - - debian-curiosa@lists.debian.org - - Description : Funny thing from and with the project, funny quotes, - discussions irc communication and fortune cookies. - Some kind of (de.)alt.netdigest for Debian-related stuff. - Moderated : no - Subscription: open - - debian-devel-all-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable - distribution. (Quiz: binary-all or all binaries?) - Moderated : no - Subscription: open - - debian-devel-alpha-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable alpha - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-arm-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable arm - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable - distribution, from developers, buildds and katie, - the archive sentinel. - (High-volume mailing list.) - Moderated : no - Subscription: open - - debian-devel-hurd-i386-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable - hurd-i386 distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-i386-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable i386 - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-m68k-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable m68k - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-powerpc-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable powerpc - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-s390-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable s390 - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-devel-sparc-changes@lists.debian.org - - Description : Notices about uploaded packages for the unstable sparc - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-hurd-i386-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable hurd-i386 - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-i386-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable i386 - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-jobs@lists.debian.org - - Description : Job postings can be published on this list in - order to make them public to members of the Debian - community. While the jobs do not necessarily have - to involve the use of Debian, it is encouraged that - they do. Jobs can be about the development of - proprietary system, but jobs involving free software - (either development or system administration) are - preferred. Please include information such as - location and remuneration if appropriate. The list - is moderated; it is also an open list - job postings - which have to be kept private should be sent to - leader@debian.org who will distribute them. - Moderated : yes - Subscription: open - - debian-legal@lists.debian.org - - Description : Discussions about legality issues such as - copyrights, patents etc. - Moderated : no - Subscription: open - - debian-m68k-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable m68k - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-mirrors-announce@lists.debian.org - - Description : Important changes to the FTP archive are announced here. - These are mainly useful to maintainers of Debian - mirrors. - Moderated : yes - Subscription: open - - debian-mirrors@lists.debian.org - - Description : Discussions relating to the Debian mirror network, - and the maintenance of mirrors. - Moderated : no - Subscription: open - - debian-powerpc-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable powerpc - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-project@lists.debian.org - - Description : Discussion about non-technical topics related - to the Debian Project. - Moderated : no - Subscription: open - - debian-publicity@lists.debian.org - - Description : Coordination of all the work related to the external - communication of Debian: drafting new announces, - collecting important information that Debian should relay - to its community, improving the infrastructure offered to - people who want to create Debian booth, etc. - Moderated : no - Subscription: open - - debian-s390-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable s390 - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-sparc-changes@lists.debian.org - - Description : Notices about uploaded packages for the stable sparc - distribution, mostly from buildd's. - Moderated : no - Subscription: open - - debian-testing-changes@lists.debian.org - - Description : Changes to the "testing" distribution are announced - here. This includes various bugfixes. - Moderated : no - Subscription: open - - debian-women@lists.debian.org - - Description : Debian users and developers who wish to involve more - women in the Debian project. For discussion and - sharing of ideas as well as project collaboration. - Moderated : no - Subscription: open - - whitelist@lists.debian.org - - Description : This is a special pseudo-mailing list to which - people can subscribe to prove they are not - spammers. - - This allows one to avoid the restrictions imposed - on non-subscriber posts to other mailing lists, - in particular the mailing lists that allow posts - only from subscribers. - Moderated : yes - Subscription: open - -Lists hosted for other projects - - Our list server provides mailing list facilities for other free - projects as well. - - other-cdwrite@lists.debian.org - - Description : cdwrite mailing list - Moderated : no - Subscription: open - - other-sart@lists.debian.org - - Description : Discussions and announcements about SART, - a free raytracer that uses Guile extension - language and is distributed under GPL. - - The SART website is at - http://petra.zesoi.fer.hr/~silovic/sart/ - Moderated : no - Subscription: open - - other-vgui-discuss@lists.debian.org - - Description : The V C++ GUI Framework - an object-oriented GUI library - for X, Win32 and OS/2. V is licensed under the GNU - LGPL. The web page is at http://www.objectcentral.com/ . - Moderated : no - Subscription: open - - -Debian mailing list advertising policy --------------------------------------- - - This policy is intended to fight mailing-list "spamming". - - The Debian mailing lists accept commercial advertising for payment. The fee - for advertisments is a donation of USD 1000 or more to "Software in the - Public Interest" (SPI). One donation per advertisement, please. If you - prefer to pay in arrears, simply post your advertisement to the list, and - the list operator will bill you USD 1999. The list operator will donate - this amount, minus the expense of collecting it, to SPI. Please note that - the lists are distributed automatically -- messages are generally not read - or checked in any way before they are distributed. - - The act of posting an advertisement indicates your willingness to - * accept responsibility for the fee, - * indemnify the list operator against any legal claims from you or - others in connection with your advertisement, and - * pay any legal and business expenses incurred in collecting late payment. - Our liability to you is limited to a good-faith effort to deliver your - message. - - Reduced rates and/or waiver of fee are available for Debian-related - advertisements. You must consult the list operator in advance of posting for - any reduction or fee waiver. - --- -Online HTML version of this document is available at - http://www.debian.org/MailingLists/subscribe diff --git a/templates/common/doc/social-contract.txt b/templates/common/doc/social-contract.txt deleted file mode 100644 index cd9c368..0000000 --- a/templates/common/doc/social-contract.txt +++ /dev/null @@ -1,131 +0,0 @@ -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". - - ------------------------------------------------------------------------ diff --git a/templates/common/doc/source-unpack.txt b/templates/common/doc/source-unpack.txt deleted file mode 100644 index 151b733..0000000 --- a/templates/common/doc/source-unpack.txt +++ /dev/null @@ -1,33 +0,0 @@ - HOW TO UNPACK A DEBIAN SOURCE PACKAGE - -There are two kinds of Debian source packages: old ones and new ones. - -A. Old ones look like this: - hello-1.3-4.tar.gz - hello-1.3-4.diff.gz - You unpack them by untarring the .tar.gz. There is NO need to apply - the diff. - -B. New ones look like this: - hello_1.3-11.dsc - hello_1.3-11.diff.gz - hello_1.3-11.orig.tar.gz - note the `.orig' part - Here you MUST use dpkg-source or apply the diff manually - see below. - - If you have `dpkg-source' you should put the files in the same - directory and type `dpkg-source -x .dsc'. - - If you do not you can extract the Debian source as follows: - 1. untar P_V.orig.tar.gz. - 2. rename the resulting P-V.orig directory to P-V. If some other - directory results, rename *it* to P-V. - 3. mkdir P-V/debian. - 4. apply the diff with patch -p0. - 5. do `chmod +x P-V/debian/rules' - (where P is the package name and V the version.) - -C. There are some packages where the Debian source is the upstream - source. In this case there will be no .diff.gz and you can just use - the .tar.gz. If a .dsc is provided you can use `dpkg-source -x'. - - -- Ian Jackson Sat, 31 Aug 1996 diff --git a/templates/common/pics/blue-lowerleft.png b/templates/common/pics/blue-lowerleft.png deleted file mode 100644 index 2a2245e..0000000 Binary files a/templates/common/pics/blue-lowerleft.png and /dev/null differ diff --git a/templates/common/pics/blue-lowerright.png b/templates/common/pics/blue-lowerright.png deleted file mode 100644 index 7e66271..0000000 Binary files a/templates/common/pics/blue-lowerright.png and /dev/null differ diff --git a/templates/common/pics/blue-upperleft.png b/templates/common/pics/blue-upperleft.png deleted file mode 100644 index a58d0ec..0000000 Binary files a/templates/common/pics/blue-upperleft.png and /dev/null differ diff --git a/templates/common/pics/blue-upperright.png b/templates/common/pics/blue-upperright.png deleted file mode 100644 index 2f36849..0000000 Binary files a/templates/common/pics/blue-upperright.png and /dev/null differ diff --git a/templates/common/pics/debian.jpg b/templates/common/pics/debian.jpg deleted file mode 100644 index db62d7a..0000000 Binary files a/templates/common/pics/debian.jpg and /dev/null differ diff --git a/templates/common/pics/logo-50.jpg b/templates/common/pics/logo-50.jpg deleted file mode 100644 index 542f0a4..0000000 Binary files a/templates/common/pics/logo-50.jpg and /dev/null differ diff --git a/templates/common/pics/red-lowerleft.png b/templates/common/pics/red-lowerleft.png deleted file mode 100644 index caca9c5..0000000 Binary files a/templates/common/pics/red-lowerleft.png and /dev/null differ diff --git a/templates/common/pics/red-lowerright.png b/templates/common/pics/red-lowerright.png deleted file mode 100644 index c27056c..0000000 Binary files a/templates/common/pics/red-lowerright.png and /dev/null differ diff --git a/templates/common/pics/red-upperleft.png b/templates/common/pics/red-upperleft.png deleted file mode 100644 index c1e3301..0000000 Binary files a/templates/common/pics/red-upperleft.png and /dev/null differ diff --git a/templates/common/pics/red-upperright.png b/templates/common/pics/red-upperright.png deleted file mode 100644 index 54d17ca..0000000 Binary files a/templates/common/pics/red-upperright.png and /dev/null differ diff --git a/templates/common/tools/README b/templates/common/tools/README deleted file mode 100644 index bc56f93..0000000 --- a/templates/common/tools/README +++ /dev/null @@ -1,13 +0,0 @@ -/debian/tools contains MS-DOS tools for installing and booting Linux. - -fips20.zip Non-destructively split harddisk partitions (works with FAT32) -gzip124.exe gzip for DOS -lodlin16.zip load Linux kernel from DOS -rawrite1.zip rawrite version 1.3 (rawrite 2.0 is much faster, but -rawrite2.zip rawrite version 2.0 it locks up on some machines.) -unz512x3.exe Info-ZIP's free UnZipper for DOS -rwwrtwin.zip Win32 version of rawrite runs on Windows 95, NT, 98, 2000, - ME, XP and probably later versions. -diskio.zip Under 95, 98 & ME you need diskio.dll. It must be in - the same directory as rwwrtwin.exe. (uncompressed) -md5sum-w32.zip Win32 version of md5sum diff --git a/templates/common/tools/diskio.zip b/templates/common/tools/diskio.zip deleted file mode 100644 index b30fa96..0000000 Binary files a/templates/common/tools/diskio.zip and /dev/null differ diff --git a/templates/common/tools/fips20.zip b/templates/common/tools/fips20.zip deleted file mode 100644 index c4a64b6..0000000 Binary files a/templates/common/tools/fips20.zip and /dev/null differ diff --git a/templates/common/tools/gzip124.exe b/templates/common/tools/gzip124.exe deleted file mode 100644 index 1a8d137..0000000 Binary files a/templates/common/tools/gzip124.exe and /dev/null differ diff --git a/templates/common/tools/lodlin16.zip b/templates/common/tools/lodlin16.zip deleted file mode 100644 index 1e5441e..0000000 Binary files a/templates/common/tools/lodlin16.zip and /dev/null differ diff --git a/templates/common/tools/md5sum-w32.zip b/templates/common/tools/md5sum-w32.zip deleted file mode 100644 index 982202b..0000000 Binary files a/templates/common/tools/md5sum-w32.zip and /dev/null differ diff --git a/templates/common/tools/rawrite1.zip b/templates/common/tools/rawrite1.zip deleted file mode 100644 index abdc229..0000000 Binary files a/templates/common/tools/rawrite1.zip and /dev/null differ diff --git a/templates/common/tools/rawrite2.zip b/templates/common/tools/rawrite2.zip deleted file mode 100644 index aa33885..0000000 Binary files a/templates/common/tools/rawrite2.zip and /dev/null differ diff --git a/templates/common/tools/rwwrtwin.zip b/templates/common/tools/rwwrtwin.zip deleted file mode 100644 index 2c3fd11..0000000 Binary files a/templates/common/tools/rwwrtwin.zip and /dev/null differ diff --git a/templates/common/tools/src/md5sum-w32_1.1.dsc b/templates/common/tools/src/md5sum-w32_1.1.dsc deleted file mode 100644 index 44393f8..0000000 --- a/templates/common/tools/src/md5sum-w32_1.1.dsc +++ /dev/null @@ -1,25 +0,0 @@ ------BEGIN PGP SIGNED MESSAGE----- -Hash: SHA1 - -Format: 1.0 -Source: md5sum-w32 -Version: 1.1 -Binary: md5sum-w32 -Maintainer: Bas Zoetekouw -Architecture: any -Standards-Version: 3.5.2 -Build-Depends: debhelper (>> 3.0.0), mingw32, zip -Files: - b5741a5c7e027ee1e9242163c5eb711b 7617 md5sum-w32_1.1.tar.gz - ------BEGIN PGP SIGNATURE----- -Version: GnuPG v1.0.7 (GNU/Linux) - -iQEXAwUBPXo9/Z6S+2TcVAFTFAKpcwP/bDWljR/VQxCFtjg4epqZczN5MRWHQ0Qc -qjRw5F0of0V0jELCVClRGl68VBX96o3tJSGvhCkXqT3UXQYd1vsiakHQotcEib3V -r07De88Bzxm9NE43AR/98TU+9niIkrOmkbxGJQXU3puKMXd/WpCw4XgNOYT6A1hg -7ugByZ32x9ID/RtIpCehPvrqCVn8J1v2dTam3m3obGt6yESg+2PcxzEeIVwN3jb3 -AwkLTKi7VyelSmMWPdJUxsMZvGmBFyjjNqwZeMYPnuGS60sHxREHA/heDsM1hIbS -7PZ9hcPXw588Y79ItGFZY4Rfdc0cJQSTkPvt2z5gAk1Eeii5kzCC25nZ -=aPY9 ------END PGP SIGNATURE----- diff --git a/templates/common/tools/src/md5sum-w32_1.1.tar.gz b/templates/common/tools/src/md5sum-w32_1.1.tar.gz deleted file mode 100644 index bf42ec8..0000000 Binary files a/templates/common/tools/src/md5sum-w32_1.1.tar.gz and /dev/null differ diff --git a/templates/common/tools/unz512x3.exe b/templates/common/tools/unz512x3.exe deleted file mode 100644 index e8b36c8..0000000 Binary files a/templates/common/tools/unz512x3.exe and /dev/null differ diff --git a/templates/iso/autorun.bat b/templates/iso/autorun.bat deleted file mode 100644 index 4718afe..0000000 --- a/templates/iso/autorun.bat +++ /dev/null @@ -1,3 +0,0 @@ -@echo Starting "README.html"... -@start README.html -@exit diff --git a/templates/iso/autorun.inf b/templates/iso/autorun.inf deleted file mode 100644 index 1b28f75..0000000 --- a/templates/iso/autorun.inf +++ /dev/null @@ -1,2 +0,0 @@ -[autorun] -open=autorun.bat diff --git a/templates/syslinux/f10.txt b/templates/syslinux/f10.txt index 9d1ed8d..33f6f11 100644 --- a/templates/syslinux/f10.txt +++ b/templates/syslinux/f10.txt @@ -12,8 +12,8 @@ permitted by applicable law. --- -This Debian Live system was built with make-live, version LIVE_VERSION. -make-live was written by Daniel Baumann and +This Debian Live system was built with live-helper, version LIVE_VERSION. +live-helper was written by Daniel Baumann and Marco Amadori . -- cgit v1.0