diff --git a/Makefile b/Makefile
index 39807b8b3..aeb83189b 100644
--- a/Makefile
+++ b/Makefile
@@ -4,7 +4,7 @@ SHELL := sh -e
LANGUAGES = de
-SCRIPTS = cgi/* functions/* examples/*/*.sh examples/auto/* scripts/*.sh scripts/*/*
+SCRIPTS = cgi/* functions/* examples/*/*.sh scripts/*.sh scripts/*/*
all: test build
diff --git a/VERSION b/VERSION
index 280a1e336..cfb3a5a8d 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-2.0.12
+3.0~a1
diff --git a/cgi/cgi b/cgi/cgi
index a55cbc522..2ab6e5b0b 100755
--- a/cgi/cgi
+++ b/cgi/cgi
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
@@ -66,7 +66,7 @@ else
LB_DISTRIBUTION=$(echo "${QUERY_STRING}" | grep -oE '(^|[?&])distribution=[a-z]+' | cut -f 2 -d '=' | head -n1)
LB_PACKAGES_LISTS=$(echo "${QUERY_STRING}" | grep -oE '(^|[?&])packages_lists=[-0-9a-z]+' | cut -f 2 -d '=' | head -n1)
LB_TASKS=$(echo "${QUERY_STRING}" | grep -oE '(^|[?&])tasks=[-0-9a-zA-Z. _]+' | cut -f 2 -d '=' | head -n1)
- LB_PACKAGES=$(echo "${QUERY_STRING}" | grep -oE '(^|[?&])packages=[-0-9a-zA-Z. _+]+' | cut -f 2 -d '=' | head -n1)
+ LB_PACKAGES=$(echo "${QUERY_STRING}" | grep -oE '(^|[?&])packages=[-0-9a-zA-Z. _]+' | cut -f 2 -d '=' | head -n1)
# Advanced bootstrap options
LB_ARCHITECTURE=$(echo "${QUERY_STRING}" | grep -oE '(^|[?&])architecture=[0-9a-z]+' | cut -f 2 -d '=' | head -n1)
diff --git a/cgi/cron b/cgi/cron
index 50b74c2fd..1cbf018d7 100755
--- a/cgi/cron
+++ b/cgi/cron
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/contrib/syslinux-splash/squeeze/COPYING b/contrib/syslinux-splash/squeeze/COPYING
new file mode 100644
index 000000000..bd2bc0825
--- /dev/null
+++ b/contrib/syslinux-splash/squeeze/COPYING
@@ -0,0 +1,104 @@
+Creative Commons Attribution-ShareAlike 3.0 Unported
+====================================================
+
+CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE LEGAL SERVICES. DISTRIBUTION OF THIS LICENSE DOES NOT CREATE AN ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES REGARDING THE INFORMATION PROVIDED, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM ITS USE.
+
+--------------------------------------------------------------------------------
+
+License
+
+THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED.
+
+BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. TO THE EXTENT THIS LICENSE MAY BE CONSIDERED TO BE A CONTRACT, THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
+
+1. Definitions
+
+ a. "Adaptation" means a work based upon the Work, or upon the Work and other pre-existing works, such as a translation, adaptation, derivative work, arrangement of music or other alterations of a literary or artistic work, or phonogram or performance and includes cinematographic adaptations or any other form in which the Work may be recast, transformed, or adapted including in any form recognizably derived from the original, except that a work that constitutes a Collection will not be considered an Adaptation for the purpose of this License. For the avoidance of doubt, where the Work is a musical work, performance or phonogram, the synchronization of the Work in timed-relation with a moving image ("synching") will be considered an Adaptation for the purpose of this License.
+
+ b. "Collection" means a collection of literary or artistic works, such as encyclopedias and anthologies, or performances, phonograms or broadcasts, or other works or subject matter other than works listed in Section 1(f) below, which, by reason of the selection and arrangement of their contents, constitute intellectual creations, in which the Work is included in its entirety in unmodified form along with one or more other contributions, each constituting separate and independent works in themselves, which together are assembled into a collective whole. A work that constitutes a Collection will not be considered an Adaptation (as defined below) for the purposes of this License.
+
+ c. "Creative Commons Compatible License" means a license that is listed at http://creativecommons.org/compatiblelicenses that has been approved by Creative Commons as being essentially equivalent to this License, including, at a minimum, because that license: (i) contains terms that have the same purpose, meaning and effect as the License Elements of this License; and, (ii) explicitly permits the relicensing of adaptations of works made available under that license under this License or a Creative Commons jurisdiction license with the same License Elements as this License.
+
+ d. "Distribute" means to make available to the public the original and copies of the Work or Adaptation, as appropriate, through sale or other transfer of ownership.
+
+ e. "License Elements" means the following high-level license attributes as selected by Licensor and indicated in the title of this License: Attribution, ShareAlike.
+
+ f. "Licensor" means the individual, individuals, entity or entities that offer(s) the Work under the terms of this License.
+
+ g. "Original Author" means, in the case of a literary or artistic work, the individual, individuals, entity or entities who created the Work or if no individual or entity can be identified, the publisher; and in addition (i) in the case of a performance the actors, singers, musicians, dancers, and other persons who act, sing, deliver, declaim, play in, interpret or otherwise perform literary or artistic works or expressions of folklore; (ii) in the case of a phonogram the producer being the person or legal entity who first fixes the sounds of a performance or other sounds; and, (iii) in the case of broadcasts, the organization that transmits the broadcast.
+
+ h. "Work" means the literary and/or artistic work offered under the terms of this License including without limitation any production in the literary, scientific and artistic domain, whatever may be the mode or form of its expression including digital form, such as a book, pamphlet and other writing; a lecture, address, sermon or other work of the same nature; a dramatic or dramatico-musical work; a choreographic work or entertainment in dumb show; a musical composition with or without words; a cinematographic work to which are assimilated works expressed by a process analogous to cinematography; a work of drawing, painting, architecture, sculpture, engraving or lithography; a photographic work to which are assimilated works expressed by a process analogous to photography; a work of applied art; an illustration, map, plan, sketch or three-dimensional work relative to geography, topography, architecture or science; a performance; a broadcast; a phonogram; a compilation of data to the extent it is protected as a copyrightable work; or a work performed by a variety or circus performer to the extent it is not otherwise considered a literary or artistic work.
+
+ i. "You" means an individual or entity exercising rights under this License who has not previously violated the terms of this License with respect to the Work, or who has received express permission from the Licensor to exercise rights under this License despite a previous violation.
+
+ j. "Publicly Perform" means to perform public recitations of the Work and to communicate to the public those public recitations, by any means or process, including by wire or wireless means or public digital performances; to make available to the public Works in such a way that members of the public may access these Works from a place and at a place individually chosen by them; to perform the Work to the public by any means or process and the communication to the public of the performances of the Work, including by public digital performance; to broadcast and rebroadcast the Work by any means including signs, sounds or images.
+
+ k "Reproduce" means to make copies of the Work by any means including without limitation by sound or visual recordings and the right of fixation and reproducing fixations of the Work, including storage of a protected performance or phonogram in digital form or other electronic medium.
+
+2. Fair Dealing Rights. Nothing in this License is intended to reduce, limit, or restrict any uses free from copyright or rights arising from limitations or exceptions that are provided for in connection with the copyright protection under copyright law or other applicable laws.
+
+3. License Grant. Subject to the terms and conditions of this License, Licensor hereby grants You a worldwide, royalty-free, non-exclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in the Work as stated below:
+
+ a. to Reproduce the Work, to incorporate the Work into one or more Collections, and to Reproduce the Work as incorporated in the Collections;
+
+ b. to create and Reproduce Adaptations provided that any such Adaptation, including any translation in any medium, takes reasonable steps to clearly label, demarcate or otherwise identify that changes were made to the original Work. For example, a translation could be marked "The original work was translated from English to Spanish," or a modification could indicate "The original work has been modified.";
+
+ c. to Distribute and Publicly Perform the Work including as incorporated in Collections; and,
+
+ d. to Distribute and Publicly Perform Adaptations.
+
+ e. For the avoidance of doubt:
+
+ i. Non-waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme cannot be waived, the Licensor reserves the exclusive right to collect such royalties for any exercise by You of the rights granted under this License;
+
+ ii. Waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme can be waived, the Licensor waives the exclusive right to collect such royalties for any exercise by You of the rights granted under this License; and,
+
+ iii. Voluntary License Schemes. The Licensor waives the right to collect royalties, whether individually or, in the event that the Licensor is a member of a collecting society that administers voluntary licensing schemes, via that society, from any exercise by You of the rights granted under this License.
+
+ The above rights may be exercised in all media and formats whether now known or hereafter devised. The above rights include the right to make such modifications as are technically necessary to exercise the rights in other media and formats. Subject to Section 8(f), all rights not expressly granted by Licensor are hereby reserved.
+
+4. Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:
+
+ a. You may Distribute or Publicly Perform the Work only under the terms of this License. You must include a copy of, or the Uniform Resource Identifier (URI) for, this License with every copy of the Work You Distribute or Publicly Perform. You may not offer or impose any terms on the Work that restrict the terms of this License or the ability of the recipient of the Work to exercise the rights granted to that recipient under the terms of the License. You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties with every copy of the Work You Distribute or Publicly Perform. When You Distribute or Publicly Perform the Work, You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License. This Section 4(a) applies to the Work as incorporated in a Collection, but this does not require the Collection apart from the Work itself to be made subject to the terms of this License. If You create a Collection, upon notice from any Licensor You must, to the extent practicable, remove from the Collection any credit as required by Section 4(c), as requested. If You create an Adaptation, upon notice from any Licensor You must, to the extent practicable, remove from the Adaptation any credit as required by Section 4(c), as requested.
+
+ b. You may Distribute or Publicly Perform an Adaptation only under the terms of: (i) this License; (ii) a later version of this License with the same License Elements as this License; (iii) a Creative Commons jurisdiction license (either this or a later license version) that contains the same License Elements as this License (e.g., Attribution-ShareAlike 3.0 US)); (iv) a Creative Commons Compatible License. If you license the Adaptation under one of the licenses mentioned in (iv), you must comply with the terms of that license. If you license the Adaptation under the terms of any of the licenses mentioned in (i), (ii) or (iii) (the "Applicable License"), you must comply with the terms of the Applicable License generally and the following provisions: (I) You must include a copy of, or the URI for, the Applicable License with every copy of each Adaptation You Distribute or Publicly Perform; (II) You may not offer or impose any terms on the Adaptation that restrict the terms of the Applicable License or the ability of the recipient of the Adaptation to exercise the rights granted to that recipient under the terms of the Applicable License; (III) You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties with every copy of the Work as included in the Adaptation You Distribute or Publicly Perform; (IV) when You Distribute or Publicly Perform the Adaptation, You may not impose any effective technological measures on the Adaptation that restrict the ability of a recipient of the Adaptation from You to exercise the rights granted to that recipient under the terms of the Applicable License. This Section 4(b) applies to the Adaptation as incorporated in a Collection, but this does not require the Collection apart from the Adaptation itself to be made subject to the terms of the Applicable License.
+
+ c. If You Distribute, or Publicly Perform the Work or any Adaptations or Collections, You must, unless a request has been made pursuant to Section 4(a), keep intact all copyright notices for the Work and provide, reasonable to the medium or means You are utilizing: (i) the name of the Original Author (or pseudonym, if applicable) if supplied, and/or if the Original Author and/or Licensor designate another party or parties (e.g., a sponsor institute, publishing entity, journal) for attribution ("Attribution Parties") in Licensor's copyright notice, terms of service or by other reasonable means, the name of such party or parties; (ii) the title of the Work if supplied; (iii) to the extent reasonably practicable, the URI, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work; and (iv) , consistent with Ssection 3(b), in the case of an Adaptation, a credit identifying the use of the Work in the Adaptation (e.g., "French translation of the Work by Original Author," or "Screenplay based on original Work by Original Author"). The credit required by this Section 4(c) may be implemented in any reasonable manner; provided, however, that in the case of a Adaptation or Collection, at a minimum such credit will appear, if a credit for all contributing authors of the Adaptation or Collection appears, then as part of these credits and in a manner at least as prominent as the credits for the other contributing authors. For the avoidance of doubt, You may only use the credit required by this Section for the purpose of attribution in the manner set out above and, by exercising Your rights under this License, You may not implicitly or explicitly assert or imply any connection with, sponsorship or endorsement by the Original Author, Licensor and/or Attribution Parties, as appropriate, of You or Your use of the Work, without the separate, express prior written permission of the Original Author, Licensor and/or Attribution Parties.
+
+ d. Except as otherwise agreed in writing by the Licensor or as may be otherwise permitted by applicable law, if You Reproduce, Distribute or Publicly Perform the Work either by itself or as part of any Adaptations or Collections, You must not distort, mutilate, modify or take other derogatory action in relation to the Work which would be prejudicial to the Original Author's honor or reputation. Licensor agrees that in those jurisdictions (e.g. Japan), in which any exercise of the right granted in Section 3(b) of this License (the right to make Adaptations) would be deemed to be a distortion, mutilation, modification or other derogatory action prejudicial to the Original Author's honor and reputation, the Licensor will waive or not assert, as appropriate, this Section, to the fullest extent permitted by the applicable national law, to enable You to reasonably exercise Your right under Section 3(b) of this License (right to make Adaptations) but not otherwise.
+
+5. Representations, Warranties and Disclaimer
+
+UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING, LICENSOR OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU.
+
+6. Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. Termination
+
+ a. This License and the rights granted hereunder will terminate automatically upon any breach by You of the terms of this License. Individuals or entities who have received Adaptations or Collections from You under this License, however, will not have their licenses terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will survive any termination of this License.
+
+ b. Subject to the above terms and conditions, the license granted here is perpetual (for the duration of the applicable copyright in the Work). Notwithstanding the above, Licensor reserves the right to release the Work under different license terms or to stop distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other license that has been, or is required to be, granted under the terms of this License), and this License will continue in full force and effect unless terminated as stated above.
+
+8. Miscellaneous
+
+ a. Each time You Distribute or Publicly Perform the Work or a Collection, the Licensor offers to the recipient a license to the Work on the same terms and conditions as the license granted to You under this License.
+
+ b. Each time You Distribute or Publicly Perform an Adaptation, Licensor offers to the recipient a license to the original Work on the same terms and conditions as the license granted to You under this License.
+
+ c. If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this License, and without further action by the parties to this agreement, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
+
+ d. No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party to be charged with such waiver or consent.
+
+ e. This License constitutes the entire agreement between the parties with respect to the Work licensed here. There are no understandings, agreements or representations with respect to the Work not specified here. Licensor shall not be bound by any additional provisions that may appear in any communication from You. This License may not be modified without the mutual written agreement of the Licensor and You.
+
+ f. The rights granted under, and the subject matter referenced, in this License were drafted utilizing the terminology of the Berne Convention for the Protection of Literary and Artistic Works (as amended on September 28, 1979), the Rome Convention of 1961, the WIPO Copyright Treaty of 1996, the WIPO Performances and Phonograms Treaty of 1996 and the Universal Copyright Convention (as revised on July 24, 1971). These rights and subject matter take effect in the relevant jurisdiction in which the License terms are sought to be enforced according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law. If the standard suite of rights granted under applicable copyright law includes additional rights not granted under this License, such additional rights are deemed to be included in the License; this License is not intended to restrict the license of any rights under applicable law.
+
+--------------------------------------------------------------------------------
+
+Creative Commons Notice
+
+Creative Commons is not a party to this License, and makes no warranty whatsoever in connection with the Work. Creative Commons will not be liable to You or any party on any legal theory for any damages whatsoever, including without limitation any general, special, incidental or consequential damages arising in connection to this license. Notwithstanding the foregoing two (2) sentences, if Creative Commons has expressly identified itself as the Licensor hereunder, it shall have all rights and obligations of Licensor.
+
+Except for the limited purpose of indicating to the public that the Work is licensed under the CCPL, Creative Commons does not authorize the use by either party of the trademark "Creative Commons" or any related trademark or logo of Creative Commons without the prior written consent of Creative Commons. Any permitted use will be in compliance with Creative Commons' then-current trademark usage guidelines, as may be published on its website or otherwise made available upon request from time to time. For the avoidance of doubt, this trademark restriction does not form part of the License.
+
+Creative Commons may be contacted at http://creativecommons.org/.
diff --git a/contrib/syslinux-splash/squeeze/README b/contrib/syslinux-splash/squeeze/README
new file mode 100644
index 000000000..292c4adf3
--- /dev/null
+++ b/contrib/syslinux-splash/squeeze/README
@@ -0,0 +1,3 @@
+This splash for Debian was made by Agnieszka Czajkowska
+and licensed under the terms of the Creative Commons Attribution-Share Alike 3.0
+(Unported) license, http://creativecommons.org/licenses/by-sa/3.0/.
diff --git a/contrib/syslinux-splash/squeeze/debian_bootscreen1.png b/contrib/syslinux-splash/squeeze/debian_bootscreen1.png
new file mode 100644
index 000000000..b3877c517
Binary files /dev/null and b/contrib/syslinux-splash/squeeze/debian_bootscreen1.png differ
diff --git a/contrib/syslinux-splash/squeeze/debian_bootscreen1.svg b/contrib/syslinux-splash/squeeze/debian_bootscreen1.svg
new file mode 100644
index 000000000..737276463
--- /dev/null
+++ b/contrib/syslinux-splash/squeeze/debian_bootscreen1.svg
@@ -0,0 +1,231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+]>
+
diff --git a/contrib/syslinux-splash/squeeze/splash.png b/contrib/syslinux-splash/squeeze/splash.png
deleted file mode 100644
index 32f097d10..000000000
Binary files a/contrib/syslinux-splash/squeeze/splash.png and /dev/null differ
diff --git a/data/debian-cd/dapper b/data/debian-cd/dapper
deleted file mode 120000
index 5cb6e6000..000000000
--- a/data/debian-cd/dapper
+++ /dev/null
@@ -1 +0,0 @@
-maverick
\ No newline at end of file
diff --git a/data/debian-cd/hardy b/data/debian-cd/hardy
deleted file mode 120000
index 5cb6e6000..000000000
--- a/data/debian-cd/hardy
+++ /dev/null
@@ -1 +0,0 @@
-maverick
\ No newline at end of file
diff --git a/data/debian-cd/intrepid b/data/debian-cd/intrepid
deleted file mode 120000
index 5cb6e6000..000000000
--- a/data/debian-cd/intrepid
+++ /dev/null
@@ -1 +0,0 @@
-maverick
\ No newline at end of file
diff --git a/data/debian-cd/jaunty b/data/debian-cd/jaunty
deleted file mode 120000
index 5cb6e6000..000000000
--- a/data/debian-cd/jaunty
+++ /dev/null
@@ -1 +0,0 @@
-maverick
\ No newline at end of file
diff --git a/data/debian-cd/karmic b/data/debian-cd/karmic
deleted file mode 120000
index 5cb6e6000..000000000
--- a/data/debian-cd/karmic
+++ /dev/null
@@ -1 +0,0 @@
-maverick
\ No newline at end of file
diff --git a/data/debian-cd/lenny/alpha_businesscard_udeb_include b/data/debian-cd/lenny/alpha_businesscard_udeb_include
deleted file mode 100644
index eea4461a8..000000000
--- a/data/debian-cd/lenny/alpha_businesscard_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
-fdisk-udeb
diff --git a/data/debian-cd/lenny/alpha_netinst_udeb_include b/data/debian-cd/lenny/alpha_netinst_udeb_include
deleted file mode 100644
index 70df4f616..000000000
--- a/data/debian-cd/lenny/alpha_netinst_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-netcfg
-ethdetect
-fdisk-udeb
diff --git a/data/debian-cd/lenny/alpha_udeb_include b/data/debian-cd/lenny/alpha_udeb_include
deleted file mode 100644
index 70df4f616..000000000
--- a/data/debian-cd/lenny/alpha_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-netcfg
-ethdetect
-fdisk-udeb
diff --git a/data/debian-cd/lenny/amd64_businesscard_udeb_include b/data/debian-cd/lenny/amd64_businesscard_udeb_include
deleted file mode 100644
index 0089df09a..000000000
--- a/data/debian-cd/lenny/amd64_businesscard_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
-pcmciautils-udeb
diff --git a/data/debian-cd/lenny/amd64_netinst_udeb_include b/data/debian-cd/lenny/amd64_netinst_udeb_include
deleted file mode 100644
index 155327762..000000000
--- a/data/debian-cd/lenny/amd64_netinst_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-netcfg
-ethdetect
-pcmciautils-udeb
diff --git a/data/debian-cd/lenny/amd64_udeb_include b/data/debian-cd/lenny/amd64_udeb_include
deleted file mode 100644
index 155327762..000000000
--- a/data/debian-cd/lenny/amd64_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-netcfg
-ethdetect
-pcmciautils-udeb
diff --git a/data/debian-cd/lenny/arm_businesscard_udeb_include b/data/debian-cd/lenny/arm_businesscard_udeb_include
deleted file mode 100644
index 6326d6c5b..000000000
--- a/data/debian-cd/lenny/arm_businesscard_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/arm_netinst_udeb_include b/data/debian-cd/lenny/arm_netinst_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/arm_netinst_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/arm_udeb_include b/data/debian-cd/lenny/arm_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/arm_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/exclude-udebs b/data/debian-cd/lenny/exclude-udebs
deleted file mode 100644
index db2096762..000000000
--- a/data/debian-cd/lenny/exclude-udebs
+++ /dev/null
@@ -1,117 +0,0 @@
-# These udebs build the d-i cdrom initrd. As such, there is no reason
-# to keep another copy of them on the CD in udeb form.
-#
-# This duplicates data found in the file build/pkg-lists/kernel, in d-i svn
-kernel-image-*
-# build/pkg-lists/base in d-i svn
-archdetect
-rootskel
-main-menu
-cdebconf-udeb
-udpkg
-anna
-di-utils
-di-utils-shell
-di-utils-reboot
-lowmemcheck
-# build/pkg-lists/cdrom/common, in d-i svn (also included in the
-# root+cd-drivers floppies)
-busybox-udeb
-installation-locale
-localechooser
-iso-3166-udeb
-hw-detect
-cdrom-detect
-cdrom-retriever
-load-cdrom
-cdrom-checker
-bogl-bterm-udeb
-di-utils-terminfo
-cdebconf-priority
-cdebconf-newt-udeb
-usb-discover
-preseed-common
-initrd-preseed
-file-preseed
-nano-udeb
-floppy-retriever
-libfribidi0-udeb
-# Already on the initrd as dependencies
-libdebconfclient0-udeb
-libdebian-installer4-udeb
-libdebian-installer-extra4-udeb
-# These udebs are only useful in building the boot floppy image.
-busybox-floppy-udeb
-rootskel-bootfloppy
-# gtk stuff included in initrd if needed
-rootskel-gtk
-cdebconf-gtk-udeb
-fontconfig-udeb
-gtk2-engines-udeb
-libatk1.0-udeb
-libcairo-directfb2-udeb
-libdirectfb-*-udeb
-libexpat1-udeb
-libfreetype6-udeb
-libglib2.0-udeb
-libgtk-directfb-2.0-0-udeb
-libgtk2-engines-udeb
-libpango1.0-udeb
-libpcre3-udeb
-libpixman-1-0-udeb
-libpng12-0-udeb
-libsdl1.2debian-udeb
-mouse-modules-*
-ttf-*
-fbset-udeb
-# terminal for gtk frontend is also included in initrd
-cdebconf-gtk-terminal
-libvte9-udeb
-# Not currently used
-cdebootstrap-udeb
-hdparm-udeb
-dhcp-client-udeb
-# This package is only useful in the d-i-demo.
-di-utils-exit-installer
-# No need for these loaders.
-download-installer
-load-floppy
-# Only useful in the hd-media initrd.
-iso-scan
-load-iso
-# Nothing currently depends on this, and it seems not useful on its own.
-reiserfsprogs-udeb
-# reiser4 is not in the Debian kernel.
-mkreiser4-udeb
-reiser4progs-udeb
-# These are not really needed, the regular netcfg subsumes them.
-netcfg-static
-# skolelinux stuff, not for the stock CDs
-debian-edu-install-udeb
-debian-edu-profile-udeb
-debian-edu-archive-keyring-udeb
-ltsp-client-builder
-autopartkit
-# live CD stuff
-live-installer
-simple-cdd-profiles
-# If needed, will be on the initrd already.
-module-init-tools-udeb
-env-preseed
-rescue-check
-cdebconf-text-udeb
-brltty-udeb
-klibc-utils-udeb
-libklibc-udeb
-udev-udeb
-ai-choosers
-auto-install
-libslang2-udeb
-# Currently unused
-nbd-client-udeb
-pwgen-udeb
-# Eh?
-gnumach-udeb
-# Exclude kbd and console-setup udebs, they're not currently used
-kbd-udeb
-console-setup-*
diff --git a/data/debian-cd/lenny/exclude-udebs-amd64 b/data/debian-cd/lenny/exclude-udebs-amd64
deleted file mode 100644
index 8f81f6e5c..000000000
--- a/data/debian-cd/lenny/exclude-udebs-amd64
+++ /dev/null
@@ -1,43 +0,0 @@
-# These udebs are in the d-i cdrom initrd and the hd-media initrd.
-# As such, there is no reason to keep another copy of them on the CD
-# in udeb form.
-console-keymaps-at
-console-keymaps-usb
-kbd-chooser
-acpi-modules-*
-ata-modules-*
-cdrom-core-modules-*
-core-modules-*
-fat-modules-*
-fb-modules-*
-ide-core-modules-*
-ide-modules-*
-input-modules-*
-isofs-modules-*
-mmc-modules-*
-nls-core-modules-*
-parport-modules-*
-pcmcia-modules-*
-sata-modules-*
-scsi-common-modules-*
-scsi-core-modules-*
-scsi-modules-*
-serial-modules-*
-speakup-modules-*
-usb-modules-*
-usb-serial-modules-*
-usb-storage-modules-*
-zlib-modules-*
-# Not used on amd64
-console-keymaps-acorn
-console-keymaps-amiga
-console-keymaps-atari
-console-keymaps-dec
-console-keymaps-sun
-# Not needed with the 2.6 kernel on amd64.
-userdevfs
-# Only needed on arches that use partconf or autopartkit.
-partconf-mkfstab
-# Not needed on arches that use partman
-mdcfg
-lvmcfg
diff --git a/data/debian-cd/lenny/exclude-udebs-i386 b/data/debian-cd/lenny/exclude-udebs-i386
deleted file mode 100644
index eeed4700c..000000000
--- a/data/debian-cd/lenny/exclude-udebs-i386
+++ /dev/null
@@ -1,45 +0,0 @@
-# These udebs are in the d-i cdrom initrd and the cd-drivers+root floppies.
-# As such, there is no reason to keep another copy of them on the CD
-# in udeb form.
-console-keymaps-at
-console-keymaps-usb
-kbd-chooser
-acpi-modules-*
-ata-modules-*
-cdrom-core-modules-*
-core-modules-*
-fat-modules-*
-fb-modules-*
-ide-core-modules-*
-ide-modules-*
-input-modules-*
-isofs-modules-*
-mmc-modules-*
-nls-core-modules-*
-parport-modules-*
-pcmcia-modules-*
-sata-modules-*
-scsi-common-modules-*
-scsi-core-modules-*
-scsi-modules-*
-serial-modules-*
-speakup-modules-*
-usb-modules-*
-usb-serial-modules-*
-usb-storage-modules-*
-zlib-modules-*
-# 686-bigmem kernel udebs are only used for the Xen netboot image
-*-686-bigmem-di
-# Not used on i386
-console-keymaps-acorn
-console-keymaps-amiga
-console-keymaps-atari
-console-keymaps-dec
-console-keymaps-sun
-# Not needed with the 2.4 kernel on i386.
-userdevfs
-# Only needed on arches that use partconf or autopartkit.
-partconf-mkfstab
-# Not needed on arches that use partman
-mdcfg
-lvmcfg
diff --git a/data/debian-cd/lenny/exclude-udebs-powerpc b/data/debian-cd/lenny/exclude-udebs-powerpc
deleted file mode 100644
index 5a7df81a5..000000000
--- a/data/debian-cd/lenny/exclude-udebs-powerpc
+++ /dev/null
@@ -1,28 +0,0 @@
-# These udebs build the d-i cdrom initrd. As such, there is no reason
-# to keep another copy of them on the CD in udeb form.
-#
-# This duplicates data found in the file build/pkg-lists/cdrom/powerpc,
-# in d-i Subversion.
-
-cdrom-core-modules-*
-console-keymaps-at
-console-keymaps-usb
-eject-udeb
-firewire-core-modules-*
-fs-common-modules-*
-ide-modules-*
-input-modules-*
-kbd-chooser
-scsi-common-modules-*
-scsi-core-modules-*
-scsi-modules-*
-socket-modules-*
-usb-modules-*
-usb-storage-modules-*
-# Not needed with the 2.4 kernel on powerpc.
-userdevfs
-# Only needed on arches that use partconf or autopartkit.
-partconf-mkfstab
-# Not needed on arches that use partman
-mdcfg
-lvmcfg
diff --git a/data/debian-cd/lenny/exclude-udebs-s390 b/data/debian-cd/lenny/exclude-udebs-s390
deleted file mode 100644
index e075e4bcf..000000000
--- a/data/debian-cd/lenny/exclude-udebs-s390
+++ /dev/null
@@ -1,3 +0,0 @@
-# S/390 does not support loading udebs off the CD image,
-# so we can exclude all udebs from it
-*
diff --git a/data/debian-cd/lenny/exclude-udebs-sparc b/data/debian-cd/lenny/exclude-udebs-sparc
deleted file mode 100644
index d11a81bc8..000000000
--- a/data/debian-cd/lenny/exclude-udebs-sparc
+++ /dev/null
@@ -1,5 +0,0 @@
-# Only needed on arches that use partconf or autopartkit.
-partconf-mkfstab
-# Not needed on arches that use partman
-mdcfg
-lvmcfg
diff --git a/data/debian-cd/lenny/hppa_businesscard_udeb_include b/data/debian-cd/lenny/hppa_businesscard_udeb_include
deleted file mode 100644
index 6326d6c5b..000000000
--- a/data/debian-cd/lenny/hppa_businesscard_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/hppa_netinst_udeb_include b/data/debian-cd/lenny/hppa_netinst_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/hppa_netinst_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/hppa_udeb_include b/data/debian-cd/lenny/hppa_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/hppa_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/i386_businesscard_udeb_include b/data/debian-cd/lenny/i386_businesscard_udeb_include
deleted file mode 100644
index 0089df09a..000000000
--- a/data/debian-cd/lenny/i386_businesscard_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
-pcmciautils-udeb
diff --git a/data/debian-cd/lenny/i386_netinst_udeb_include b/data/debian-cd/lenny/i386_netinst_udeb_include
deleted file mode 100644
index 155327762..000000000
--- a/data/debian-cd/lenny/i386_netinst_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-netcfg
-ethdetect
-pcmciautils-udeb
diff --git a/data/debian-cd/lenny/i386_udeb_include b/data/debian-cd/lenny/i386_udeb_include
deleted file mode 100644
index 155327762..000000000
--- a/data/debian-cd/lenny/i386_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-netcfg
-ethdetect
-pcmciautils-udeb
diff --git a/data/debian-cd/lenny/ia64_businesscard_udeb_include b/data/debian-cd/lenny/ia64_businesscard_udeb_include
deleted file mode 100644
index 6326d6c5b..000000000
--- a/data/debian-cd/lenny/ia64_businesscard_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/ia64_netinst_udeb_include b/data/debian-cd/lenny/ia64_netinst_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/ia64_netinst_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/ia64_udeb_include b/data/debian-cd/lenny/ia64_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/ia64_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/m68k_businesscard_udeb_include b/data/debian-cd/lenny/m68k_businesscard_udeb_include
deleted file mode 100644
index 6326d6c5b..000000000
--- a/data/debian-cd/lenny/m68k_businesscard_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/m68k_netinst_udeb_include b/data/debian-cd/lenny/m68k_netinst_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/m68k_netinst_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/m68k_udeb_include b/data/debian-cd/lenny/m68k_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/m68k_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/mips_businesscard_udeb_include b/data/debian-cd/lenny/mips_businesscard_udeb_include
deleted file mode 100644
index 6326d6c5b..000000000
--- a/data/debian-cd/lenny/mips_businesscard_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/mips_netinst_udeb_include b/data/debian-cd/lenny/mips_netinst_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/mips_netinst_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/mips_udeb_include b/data/debian-cd/lenny/mips_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/mips_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/mipsel_businesscard_udeb_include b/data/debian-cd/lenny/mipsel_businesscard_udeb_include
deleted file mode 100644
index 6326d6c5b..000000000
--- a/data/debian-cd/lenny/mipsel_businesscard_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/mipsel_netinst_udeb_include b/data/debian-cd/lenny/mipsel_netinst_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/mipsel_netinst_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/mipsel_udeb_include b/data/debian-cd/lenny/mipsel_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/mipsel_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/powerpc_businesscard_udeb_include b/data/debian-cd/lenny/powerpc_businesscard_udeb_include
deleted file mode 100644
index 6326d6c5b..000000000
--- a/data/debian-cd/lenny/powerpc_businesscard_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/powerpc_netinst_udeb_include b/data/debian-cd/lenny/powerpc_netinst_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/powerpc_netinst_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/powerpc_udeb_include b/data/debian-cd/lenny/powerpc_udeb_include
deleted file mode 100644
index 155327762..000000000
--- a/data/debian-cd/lenny/powerpc_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-netcfg
-ethdetect
-pcmciautils-udeb
diff --git a/data/debian-cd/lenny/s390_businesscard_udeb_include b/data/debian-cd/lenny/s390_businesscard_udeb_include
deleted file mode 100644
index 6326d6c5b..000000000
--- a/data/debian-cd/lenny/s390_businesscard_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/s390_netinst_udeb_include b/data/debian-cd/lenny/s390_netinst_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/s390_netinst_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/s390_udeb_include b/data/debian-cd/lenny/s390_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/s390_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/sparc_businesscard_udeb_include b/data/debian-cd/lenny/sparc_businesscard_udeb_include
deleted file mode 100644
index 6326d6c5b..000000000
--- a/data/debian-cd/lenny/sparc_businesscard_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/sparc_netinst_udeb_include b/data/debian-cd/lenny/sparc_netinst_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/sparc_netinst_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/sparc_udeb_include b/data/debian-cd/lenny/sparc_udeb_include
deleted file mode 100644
index 6f1c801c0..000000000
--- a/data/debian-cd/lenny/sparc_udeb_include
+++ /dev/null
@@ -1,2 +0,0 @@
-netcfg
-ethdetect
diff --git a/data/debian-cd/lenny/udeb_exclude b/data/debian-cd/lenny/udeb_exclude
deleted file mode 100644
index 8b1378917..000000000
--- a/data/debian-cd/lenny/udeb_exclude
+++ /dev/null
@@ -1 +0,0 @@
-
diff --git a/data/debian-cd/lucid b/data/debian-cd/lucid
deleted file mode 120000
index 5cb6e6000..000000000
--- a/data/debian-cd/lucid
+++ /dev/null
@@ -1 +0,0 @@
-maverick
\ No newline at end of file
diff --git a/data/debian-cd/maverick/amd64_netinst_udeb_include b/data/debian-cd/maverick/amd64_netinst_udeb_include
deleted file mode 100644
index 275197a49..000000000
--- a/data/debian-cd/maverick/amd64_netinst_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/amd64_udeb_include b/data/debian-cd/maverick/amd64_udeb_include
deleted file mode 100644
index 275197a49..000000000
--- a/data/debian-cd/maverick/amd64_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/armel_netinst_udeb_include b/data/debian-cd/maverick/armel_netinst_udeb_include
deleted file mode 100644
index 275197a49..000000000
--- a/data/debian-cd/maverick/armel_netinst_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/armel_udeb_include b/data/debian-cd/maverick/armel_udeb_include
deleted file mode 100644
index 275197a49..000000000
--- a/data/debian-cd/maverick/armel_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/exclude-udebs b/data/debian-cd/maverick/exclude-udebs
deleted file mode 100644
index 252dba2a0..000000000
--- a/data/debian-cd/maverick/exclude-udebs
+++ /dev/null
@@ -1 +0,0 @@
-kernel-image-*
diff --git a/data/debian-cd/maverick/i386_businesscard_udeb_include b/data/debian-cd/maverick/i386_businesscard_udeb_include
deleted file mode 100644
index c8849a918..000000000
--- a/data/debian-cd/maverick/i386_businesscard_udeb_include
+++ /dev/null
@@ -1,5 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/i386_netinst_udeb_include b/data/debian-cd/maverick/i386_netinst_udeb_include
deleted file mode 100644
index 275197a49..000000000
--- a/data/debian-cd/maverick/i386_netinst_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/i386_udeb_include b/data/debian-cd/maverick/i386_udeb_include
deleted file mode 100644
index 275197a49..000000000
--- a/data/debian-cd/maverick/i386_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/ia64_netinst_udeb_include b/data/debian-cd/maverick/ia64_netinst_udeb_include
deleted file mode 100644
index 275197a49..000000000
--- a/data/debian-cd/maverick/ia64_netinst_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/ia64_udeb_include b/data/debian-cd/maverick/ia64_udeb_include
deleted file mode 100644
index 275197a49..000000000
--- a/data/debian-cd/maverick/ia64_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/powerpc_businesscard_udeb_include b/data/debian-cd/maverick/powerpc_businesscard_udeb_include
deleted file mode 100644
index b5c5e7ea2..000000000
--- a/data/debian-cd/maverick/powerpc_businesscard_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-choose-mirror
-netcfg
-ethdetect
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/powerpc_netinst_udeb_include b/data/debian-cd/maverick/powerpc_netinst_udeb_include
deleted file mode 100644
index 4a83dd2ab..000000000
--- a/data/debian-cd/maverick/powerpc_netinst_udeb_include
+++ /dev/null
@@ -1,3 +0,0 @@
-netcfg
-ethdetect
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/powerpc_udeb_include b/data/debian-cd/maverick/powerpc_udeb_include
deleted file mode 100644
index 275197a49..000000000
--- a/data/debian-cd/maverick/powerpc_udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/maverick/udeb_include b/data/debian-cd/maverick/udeb_include
deleted file mode 100644
index 275197a49..000000000
--- a/data/debian-cd/maverick/udeb_include
+++ /dev/null
@@ -1,4 +0,0 @@
-netcfg
-ethdetect
-pcmcia-cs-udeb
-wireless-tools-udeb
diff --git a/data/debian-cd/natty b/data/debian-cd/natty
deleted file mode 120000
index 5cb6e6000..000000000
--- a/data/debian-cd/natty
+++ /dev/null
@@ -1 +0,0 @@
-maverick
\ No newline at end of file
diff --git a/data/debian-cd/squeeze/udeb_exclude b/data/debian-cd/squeeze/udeb_exclude
index 8b1378917..2e372f611 100644
--- a/data/debian-cd/squeeze/udeb_exclude
+++ b/data/debian-cd/squeeze/udeb_exclude
@@ -1 +1 @@
-
+apt-mirror-setup
diff --git a/debian/changelog b/debian/changelog
index 23a1ffe14..2c6bd326c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,253 +1,9 @@
-live-build (2.0.12-2) unstable; urgency=low
+live-build (3.0~a1-1) experimental; urgency=low
- * Adding preinst script to remove
- /usr/share/live/build/includes/squeeze (Closes: #611794).
+ * Removing lenny support.
+ * Switching to source format 3.0 (quilt).
- -- Daniel Baumann Wed, 02 Feb 2011 12:35:41 +0100
-
-live-build (2.0.12-1) unstable; urgency=low
-
- [ Daniel Baumann ]
- * Removing l10n support for 2.0 branch.
- * Correcting outdated program variable.
- * Updating help function in lb for live-build.
- * Updating man function for newer live-build versions (Closes:
- #608477).
- * Marking xresprobe in standard-x11 list as lenny only (Closes:
- #608566).
- * Updating year in copyright.
- * Removing headers in copyright file.
- * Updating year in manpage, hooks, script and template files.
-
- [ Luigi Capriotti ]
- * Support for newer grub-common package.
-
- [ Daniel Baumann ]
- * Simplyfing grub-mkimage legacy handling for lenny in lb_binary_iso.
- * Adding ubuntu lucid for grub-mkimage legacy handling in
- lb_binary_iso.
- * Adding missing netinst udeb include files for ubuntu.
-
- [ Cody A.W. Somerville ]
- * Adding missing debian-cd data files for Ubuntu releases for some
- architectures.
-
- [ Daniel Baumann ]
- * Adding support for Ubuntu jaunty and natty, thanks to Cody A.W.
- Somerville .
-
- [ Philip Newborough ]
- * Update example path in 'all_binary_debian-installer-banner.sh'
- example hook.
-
- [ Daniel Baumann ]
- * Account for the + character in packages for l-b.cgi
- * Updating includes for squeeze.
- * Updating syslinux theme for squeeze.
- * Removing wheezy splash.
-
- -- Daniel Baumann Tue, 01 Feb 2011 22:32:56 +0100
-
-live-build (2.0.11-1) unstable; urgency=low
-
- [ Daniel Baumann ]
- * Disabling inclusion of GUI installer images on ubuntu.
- * Updating losetup-lukshome example hook to use blkid where available,
- thanks to Clint Adams (Closes: #607108).
-
- [ Cody A.W. Somerville ]
- * Fixing numbering of live kernels and initrd files when using
- syslinux.
-
- [ Daniel Baumann ]
- * Removing unmaintained package lists (Closes: #598100).
-
- -- Daniel Baumann Fri, 24 Dec 2010 18:49:26 +0100
-
-live-build (2.0.10-1) unstable; urgency=low
-
- [ Ben Armstrong ]
- * Adding '--includes none' documentation in help and man page.
-
- [ Daniel Baumann ]
- * Marking afio in rescue list as sid and lenny only.
- * Adding debian-installer-launcher in prebuilt images.
-
- [ Ben Armstrong ]
- * Fixing numerous spelling and other minor details in lb_config man
- page.
- * Adding *-desktop virtual package lists files (just comments for doc
- purposes).
-
- [ Daniel Baumann ]
- * Adding debian-cd data for ubuntu releases.
- * Removing old ubuntu release (jaunty).
- * Applying patch from Cody A.W. Somerville
- to update kernel packages for ubuntu
- in lb_binary_debian-installer.
- * Removing last live-helper remains in internal variables.
- * Removing old and outdated FAQ.
- * Mentioning Richard in authors file.
- * Updating credits file.
- * Removing unused name header in package lists.
- * Unfuzzying German manpage translations.
- * Marking ntop as lenny and sid only in rescue list.
- * Marking tob as lenny and sid only in rescue list.
-
- -- Daniel Baumann Tue, 14 Dec 2010 13:05:39 +0100
-
-live-build (2.0.9-1) unstable; urgency=medium
-
- [ Daniel Baumann ]
- * Once again updating volatile urls for squeeze.
-
- [ Ben Armstrong ]
- * Updating lb config --help and man page.
-
- [ Daniel Baumann ]
- * Unfuzzying German manpage translations.
-
- -- Daniel Baumann Mon, 06 Dec 2010 12:01:43 +0100
-
-live-build (2.0.8-1) unstable; urgency=medium
-
- [ Daniel Baumann ]
- * Replacing last occurences of lh with lb.
- * Adding warning about non-usefullnes of the stripped hook.
-
- [ Ben Armstrong ]
- * Adding example auto scripts.
-
- [ Daniel Baumann ]
- * Applying slightly modified patch from Michael Hudson
- to make arguments in debootstrap
- calls more robust.
- * Updating initramfs switch in lb config manpage (Closes: #605255).
-
- -- Daniel Baumann Mon, 29 Nov 2010 23:12:54 +0100
-
-live-build (2.0.7-1) unstable; urgency=medium
-
- [ Daniel Baumann ]
- * Enabling volatile for squeeze.
- * Updating volatile urls for squeeze.
-
- [ Richard Nelson ]
- * Cleanup l-b.cgi header file to reflect Live Build.
-
- [ Daniel Baumann ]
- * Removing apt-mirror-setup from udeb_exclude (Closes: #604027).
- * Removing cdrom-detect/try-usb workaround, not needed anymore.
- * Correcting quoting of auto calls, thanks to Andreas Loibl
- .
- * Also including auxiliary packages in d-i pool (Closes: #604551).
- * Enabling removal of ssh host keys, they are regenerated by live-
- config.
- * Simplyfing ssh host key removal.
-
- -- Daniel Baumann Mon, 22 Nov 2010 23:13:43 +0100
-
-live-build (2.0.6-1) unstable; urgency=medium
-
- [ Ben Armstrong ]
- * Adding reference material to debian-live-devel list: live-boot,
- live-config and live-manual.
-
- [ Daniel Baumann ]
- * Adding vpnc in rescue list.
- * Updating debian-live-devel packages list (Closes: #602139).
- * Correcting typo in defaults handling of apt http proxy.
- * Workarounding symlink on usb-hdd when including debian-installer and
- using vfat filesystems.
-
- [ Ben Armstrong ]
- * Fixing typo in symlink on fat workaround.
-
- [ Daniel Baumann ]
- * Making d-i indices copying depending on binary image type.
-
- -- Daniel Baumann Sat, 13 Nov 2010 16:10:43 +0100
-
-live-build (2.0.5-1) unstable; urgency=medium
-
- * Removing dpkg-tmpfs hack, this is too intrusive atm.
-
- -- Daniel Baumann Thu, 28 Oct 2010 09:44:14 +0200
-
-live-build (2.0.4-1) unstable; urgency=medium
-
- [ Richard Nelson ]
- * Addng lenny build option back to forms and removing wheezy on l-b-
- cgi.
-
- [ Daniel Baumann ]
- * Adding fsarchiver to rescue list.
- * Removing deep link to bug page in the manual, since we don't have
- stable references yet.
-
- -- Daniel Baumann Thu, 28 Oct 2010 09:34:43 +0200
-
-live-build (2.0.3-1) unstable; urgency=medium
-
- [ Daniel Baumann ]
- * Removing cron examples, autobuild is handled by live-autobuild now.
- * Using old lenny syslinux bootsplash for squeeze, moving new splash
- to wheezy.
-
- [ Richard Nelson ]
- * Make iso-hybrid default on l-b-cgi.
- * Make squeeze default on l-b-cgi.
-
- [ Daniel Baumann ]
- * Updating path in copyright file.
- * Removing remaining last leftovers from lh in lb and live-build
- manpages.
- * Removing debian-maintainers.org and debian-projects.org repository
- entries, will re-add them after squeeze.
- * Updating special handling for backports.
-
- -- Daniel Baumann Tue, 12 Oct 2010 11:05:07 +0200
-
-live-build (2.0.2-1) unstable; urgency=medium
-
- [ Daniel Baumann ]
- * Removing superfluous 'releasing' changelog entry in previous
- version.
- * Updating defaults for squeeze and d-i gui.
- * Updating images autobuild script for squeeze beta1.
- * Adding temporary workarounds to deal with latest archive breakages
- in image autobuild script.
- * Handling live.debian.net repository differently, so that ubuntu
- people can use it too.
- * Marking mrt in rescue list as lenny only.
- * Also using gdm legacy hack on xfce-desktop default images.
-
- [ intrigeri ]
- * Fixing squashfs.sort location with --build-with-chroot false.
-
- [ Daniel Baumann ]
- * Correcting typo with lb config call for usb-hdd in autobuild script.
-
- -- Daniel Baumann Sat, 02 Oct 2010 10:00:45 +0200
-
-live-build (2.0.1-1) unstable; urgency=medium
-
- [ Daniel Baumann ]
- * Adding squeeze-backports as valid distribution codename in
- lb_config.
- * Correcting wrong stage file in lb_chroot_interactive.
- * Removing d-i hacks, should be fixed with newer live-installer.
-
- [ Otavio Salvador ]
- * Fixing debian-installer index generation.
- * Fixing debian-installer Release file generation.
-
- [ Daniel Baumann ]
- * Also correcting version number in debian-installer release file.
- * Avoid using bashism when handling codename/suite mapping for debian-
- installer release file.
-
- -- Daniel Baumann Mon, 27 Sep 2010 07:41:45 +0200
+ -- Daniel Baumann Sun, 26 Sep 2010 12:38:28 +0200
live-build (2.0.0-1) unstable; urgency=medium
@@ -283,6 +39,7 @@ live-build (2.0.0-1) unstable; urgency=medium
finally migrated some time ago.
* Not fail if /dev/random is not available in chroot, newer
debootstrap seems not to create it anymore.
+ * Releasing debian version 2.0.0-1.
-- Daniel Baumann Sun, 26 Sep 2010 12:14:46 +0200
diff --git a/debian/control b/debian/control
index 0e2cde43c..fae32f93a 100644
--- a/debian/control
+++ b/debian/control
@@ -4,6 +4,7 @@ Priority: optional
Maintainer: Debian Live Project
Uploaders: Daniel Baumann
Build-Depends: debhelper (>= 7.0.50~)
+Build-Depends-Indep: gettext
Standards-Version: 3.9.1
Homepage: http://live.debian.net/devel/live-build/
Vcs-Browser: http://live.debian.net/gitweb/?p=live-build.git
@@ -12,9 +13,7 @@ Vcs-Git: git://live.debian.net/git/live-build.git
Package: live-build
Architecture: all
Depends: ${misc:Depends}, debootstrap | cdebootstrap | cdebootstrap-static
-Conflicts: live-helper (<< 2.0~a20)
-Replaces: live-helper
-Recommends: cpio, gnu-fdisk
+Recommends: cpio, gettext-base, gnu-fdisk
Suggests:
dosfstools, genisoimage, memtest86+ | memtest86, mtools, parted,
squashfs-tools | genext2fs | mtd-tools, sudo | fakeroot, syslinux | grub,
@@ -25,22 +24,10 @@ Description: Debian Live - System Build Scripts
Package: live-build-cgi
Architecture: all
-Depends: ${misc:Depends}, live-helper (= ${source:Version})
-Conflicts: live-helper (<< 2.0~a20)
-Replaces: live-helper
+Depends: ${misc:Depends}
Recommends: apache2 | httpd
Description: Debian Live - System Build Scripts (cgi frontend)
live-build contains the scripts that build a Debian Live system image from a
configuration directory.
.
This package contains the cgi frontend.
-
-Package: live-helper
-Architecture: all
-Depends: ${misc:Depends}, live-build
-Description: Debian Live - System Build Scripts (transitional package)
- Package to ease upgrading from older live-helper packages to the new
- live-build package.
- .
- This package can be purged at anytime once the live-build package has been
- installed.
diff --git a/debian/copyright b/debian/copyright
index a4a985531..58bc04708 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,5 +1,8 @@
+Upstream-Contact: Debian Live Project
+Upstream-Homepage: http://live.debian.net/
+
Files: *
-Copyright: (C) 2006-2011 Daniel Baumann
+Copyright: (C) 2006-2010 Daniel Baumann
License: GPL-3+
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
@@ -65,21 +68,109 @@ License: other
http://www.debian.org/ if you use it on a web page.
Files: contrib/syslinux-splash/squeeze
-Copyright: (C) 2010 2010 Valessio S. Brito
-License: GPL-2
- 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; version 2
- of the License.
+Copyright: (C) 2009 Agnieszka Czajkowska
+License: CC-BY-SA-3
+ Creative Commons Attribution-ShareAlike 3.0 Unported
+ ====================================================
.
- 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.
+ CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE LEGAL SERVICES. DISTRIBUTION OF THIS LICENSE DOES NOT CREATE AN ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES REGARDING THE INFORMATION PROVIDED, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM ITS USE.
.
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+ --------------------------------------------------------------------------------
.
- On Debian systems, the complete text of the GNU General Public License
- can be found in /usr/share/common-licenses/GPL-2 file.
+ License
+ .
+ THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED.
+ .
+ BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. TO THE EXTENT THIS LICENSE MAY BE CONSIDERED TO BE A CONTRACT, THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
+ .
+ 1. Definitions
+ .
+ a. "Adaptation" means a work based upon the Work, or upon the Work and other pre-existing works, such as a translation, adaptation, derivative work, arrangement of music or other alterations of a literary or artistic work, or phonogram or performance and includes cinematographic adaptations or any other form in which the Work may be recast, transformed, or adapted including in any form recognizably derived from the original, except that a work that constitutes a Collection will not be considered an Adaptation for the purpose of this License. For the avoidance of doubt, where the Work is a musical work, performance or phonogram, the synchronization of the Work in timed-relation with a moving image ("synching") will be considered an Adaptation for the purpose of this License.
+ .
+ b. "Collection" means a collection of literary or artistic works, such as encyclopedias and anthologies, or performances, phonograms or broadcasts, or other works or subject matter other than works listed in Section 1(f) below, which, by reason of the selection and arrangement of their contents, constitute intellectual creations, in which the Work is included in its entirety in unmodified form along with one or more other contributions, each constituting separate and independent works in themselves, which together are assembled into a collective whole. A work that constitutes a Collection will not be considered an Adaptation (as defined below) for the purposes of this License.
+ .
+ c. "Creative Commons Compatible License" means a license that is listed at http://creativecommons.org/compatiblelicenses that has been approved by Creative Commons as being essentially equivalent to this License, including, at a minimum, because that license: (i) contains terms that have the same purpose, meaning and effect as the License Elements of this License; and, (ii) explicitly permits the relicensing of adaptations of works made available under that license under this License or a Creative Commons jurisdiction license with the same License Elements as this License.
+ .
+ d. "Distribute" means to make available to the public the original and copies of the Work or Adaptation, as appropriate, through sale or other transfer of ownership.
+ .
+ e. "License Elements" means the following high-level license attributes as selected by Licensor and indicated in the title of this License: Attribution, ShareAlike.
+ .
+ f. "Licensor" means the individual, individuals, entity or entities that offer(s) the Work under the terms of this License.
+ .
+ g. "Original Author" means, in the case of a literary or artistic work, the individual, individuals, entity or entities who created the Work or if no individual or entity can be identified, the publisher; and in addition (i) in the case of a performance the actors, singers, musicians, dancers, and other persons who act, sing, deliver, declaim, play in, interpret or otherwise perform literary or artistic works or expressions of folklore; (ii) in the case of a phonogram the producer being the person or legal entity who first fixes the sounds of a performance or other sounds; and, (iii) in the case of broadcasts, the organization that transmits the broadcast.
+ .
+ h. "Work" means the literary and/or artistic work offered under the terms of this License including without limitation any production in the literary, scientific and artistic domain, whatever may be the mode or form of its expression including digital form, such as a book, pamphlet and other writing; a lecture, address, sermon or other work of the same nature; a dramatic or dramatico-musical work; a choreographic work or entertainment in dumb show; a musical composition with or without words; a cinematographic work to which are assimilated works expressed by a process analogous to cinematography; a work of drawing, painting, architecture, sculpture, engraving or lithography; a photographic work to which are assimilated works expressed by a process analogous to photography; a work of applied art; an illustration, map, plan, sketch or three-dimensional work relative to geography, topography, architecture or science; a performance; a broadcast; a phonogram; a compilation of data to the extent it is protected as a copyrightable work; or a work performed by a variety or circus performer to the extent it is not otherwise considered a literary or artistic work.
+ .
+ i. "You" means an individual or entity exercising rights under this License who has not previously violated the terms of this License with respect to the Work, or who has received express permission from the Licensor to exercise rights under this License despite a previous violation.
+ .
+ j. "Publicly Perform" means to perform public recitations of the Work and to communicate to the public those public recitations, by any means or process, including by wire or wireless means or public digital performances; to make available to the public Works in such a way that members of the public may access these Works from a place and at a place individually chosen by them; to perform the Work to the public by any means or process and the communication to the public of the performances of the Work, including by public digital performance; to broadcast and rebroadcast the Work by any means including signs, sounds or images.
+ .
+ k "Reproduce" means to make copies of the Work by any means including without limitation by sound or visual recordings and the right of fixation and reproducing fixations of the Work, including storage of a protected performance or phonogram in digital form or other electronic medium.
+ .
+ 2. Fair Dealing Rights. Nothing in this License is intended to reduce, limit, or restrict any uses free from copyright or rights arising from limitations or exceptions that are provided for in connection with the copyright protection under copyright law or other applicable laws.
+ .
+ 3. License Grant. Subject to the terms and conditions of this License, Licensor hereby grants You a worldwide, royalty-free, non-exclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in the Work as stated below:
+ .
+ a. to Reproduce the Work, to incorporate the Work into one or more Collections, and to Reproduce the Work as incorporated in the Collections;
+ .
+ b. to create and Reproduce Adaptations provided that any such Adaptation, including any translation in any medium, takes reasonable steps to clearly label, demarcate or otherwise identify that changes were made to the original Work. For example, a translation could be marked "The original work was translated from English to Spanish," or a modification could indicate "The original work has been modified.";
+ .
+ c. to Distribute and Publicly Perform the Work including as incorporated in Collections; and,
+ .
+ d. to Distribute and Publicly Perform Adaptations.
+ .
+ e. For the avoidance of doubt:
+ .
+ i. Non-waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme cannot be waived, the Licensor reserves the exclusive right to collect such royalties for any exercise by You of the rights granted under this License;
+ .
+ ii. Waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme can be waived, the Licensor waives the exclusive right to collect such royalties for any exercise by You of the rights granted under this License; and,
+ .
+ iii. Voluntary License Schemes. The Licensor waives the right to collect royalties, whether individually or, in the event that the Licensor is a member of a collecting society that administers voluntary licensing schemes, via that society, from any exercise by You of the rights granted under this License.
+ .
+ The above rights may be exercised in all media and formats whether now known or hereafter devised. The above rights include the right to make such modifications as are technically necessary to exercise the rights in other media and formats. Subject to Section 8(f), all rights not expressly granted by Licensor are hereby reserved.
+ .
+ 4. Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:
+ .
+ a. You may Distribute or Publicly Perform the Work only under the terms of this License. You must include a copy of, or the Uniform Resource Identifier (URI) for, this License with every copy of the Work You Distribute or Publicly Perform. You may not offer or impose any terms on the Work that restrict the terms of this License or the ability of the recipient of the Work to exercise the rights granted to that recipient under the terms of the License. You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties with every copy of the Work You Distribute or Publicly Perform. When You Distribute or Publicly Perform the Work, You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License. This Section 4(a) applies to the Work as incorporated in a Collection, but this does not require the Collection apart from the Work itself to be made subject to the terms of this License. If You create a Collection, upon notice from any Licensor You must, to the extent practicable, remove from the Collection any credit as required by Section 4(c), as requested. If You create an Adaptation, upon notice from any Licensor You must, to the extent practicable, remove from the Adaptation any credit as required by Section 4(c), as requested.
+ .
+ b. You may Distribute or Publicly Perform an Adaptation only under the terms of: (i) this License; (ii) a later version of this License with the same License Elements as this License; (iii) a Creative Commons jurisdiction license (either this or a later license version) that contains the same License Elements as this License (e.g., Attribution-ShareAlike 3.0 US)); (iv) a Creative Commons Compatible License. If you license the Adaptation under one of the licenses mentioned in (iv), you must comply with the terms of that license. If you license the Adaptation under the terms of any of the licenses mentioned in (i), (ii) or (iii) (the "Applicable License"), you must comply with the terms of the Applicable License generally and the following provisions: (I) You must include a copy of, or the URI for, the Applicable License with every copy of each Adaptation You Distribute or Publicly Perform; (II) You may not offer or impose any terms on the Adaptation that restrict the terms of the Applicable License or the ability of the recipient of the Adaptation to exercise the rights granted to that recipient under the terms of the Applicable License; (III) You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties with every copy of the Work as included in the Adaptation You Distribute or Publicly Perform; (IV) when You Distribute or Publicly Perform the Adaptation, You may not impose any effective technological measures on the Adaptation that restrict the ability of a recipient of the Adaptation from You to exercise the rights granted to that recipient under the terms of the Applicable License. This Section 4(b) applies to the Adaptation as incorporated in a Collection, but this does not require the Collection apart from the Adaptation itself to be made subject to the terms of the Applicable License.
+ .
+ c. If You Distribute, or Publicly Perform the Work or any Adaptations or Collections, You must, unless a request has been made pursuant to Section 4(a), keep intact all copyright notices for the Work and provide, reasonable to the medium or means You are utilizing: (i) the name of the Original Author (or pseudonym, if applicable) if supplied, and/or if the Original Author and/or Licensor designate another party or parties (e.g., a sponsor institute, publishing entity, journal) for attribution ("Attribution Parties") in Licensor's copyright notice, terms of service or by other reasonable means, the name of such party or parties; (ii) the title of the Work if supplied; (iii) to the extent reasonably practicable, the URI, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work; and (iv) , consistent with Ssection 3(b), in the case of an Adaptation, a credit identifying the use of the Work in the Adaptation (e.g., "French translation of the Work by Original Author," or "Screenplay based on original Work by Original Author"). The credit required by this Section 4(c) may be implemented in any reasonable manner; provided, however, that in the case of a Adaptation or Collection, at a minimum such credit will appear, if a credit for all contributing authors of the Adaptation or Collection appears, then as part of these credits and in a manner at least as prominent as the credits for the other contributing authors. For the avoidance of doubt, You may only use the credit required by this Section for the purpose of attribution in the manner set out above and, by exercising Your rights under this License, You may not implicitly or explicitly assert or imply any connection with, sponsorship or endorsement by the Original Author, Licensor and/or Attribution Parties, as appropriate, of You or Your use of the Work, without the separate, express prior written permission of the Original Author, Licensor and/or Attribution Parties.
+ .
+ d. Except as otherwise agreed in writing by the Licensor or as may be otherwise permitted by applicable law, if You Reproduce, Distribute or Publicly Perform the Work either by itself or as part of any Adaptations or Collections, You must not distort, mutilate, modify or take other derogatory action in relation to the Work which would be prejudicial to the Original Author's honor or reputation. Licensor agrees that in those jurisdictions (e.g. Japan), in which any exercise of the right granted in Section 3(b) of this License (the right to make Adaptations) would be deemed to be a distortion, mutilation, modification or other derogatory action prejudicial to the Original Author's honor and reputation, the Licensor will waive or not assert, as appropriate, this Section, to the fullest extent permitted by the applicable national law, to enable You to reasonably exercise Your right under Section 3(b) of this License (right to make Adaptations) but not otherwise.
+ .
+ 5. Representations, Warranties and Disclaimer
+ .
+ UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING, LICENSOR OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU.
+ .
+ 6. Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+ .
+ 7. Termination
+ .
+ a. This License and the rights granted hereunder will terminate automatically upon any breach by You of the terms of this License. Individuals or entities who have received Adaptations or Collections from You under this License, however, will not have their licenses terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will survive any termination of this License.
+ .
+ b. Subject to the above terms and conditions, the license granted here is perpetual (for the duration of the applicable copyright in the Work). Notwithstanding the above, Licensor reserves the right to release the Work under different license terms or to stop distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other license that has been, or is required to be, granted under the terms of this License), and this License will continue in full force and effect unless terminated as stated above.
+ .
+ 8. Miscellaneous
+ .
+ a. Each time You Distribute or Publicly Perform the Work or a Collection, the Licensor offers to the recipient a license to the Work on the same terms and conditions as the license granted to You under this License.
+ .
+ b. Each time You Distribute or Publicly Perform an Adaptation, Licensor offers to the recipient a license to the original Work on the same terms and conditions as the license granted to You under this License.
+ .
+ c. If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this License, and without further action by the parties to this agreement, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
+ .
+ d. No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party to be charged with such waiver or consent.
+ .
+ e. This License constitutes the entire agreement between the parties with respect to the Work licensed here. There are no understandings, agreements or representations with respect to the Work not specified here. Licensor shall not be bound by any additional provisions that may appear in any communication from You. This License may not be modified without the mutual written agreement of the Licensor and You.
+ .
+ f. The rights granted under, and the subject matter referenced, in this License were drafted utilizing the terminology of the Berne Convention for the Protection of Literary and Artistic Works (as amended on September 28, 1979), the Rome Convention of 1961, the WIPO Copyright Treaty of 1996, the WIPO Performances and Phonograms Treaty of 1996 and the Universal Copyright Convention (as revised on July 24, 1971). These rights and subject matter take effect in the relevant jurisdiction in which the License terms are sought to be enforced according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law. If the standard suite of rights granted under applicable copyright law includes additional rights not granted under this License, such additional rights are deemed to be included in the License; this License is not intended to restrict the license of any rights under applicable law.
+ .
+ --------------------------------------------------------------------------------
+ .
+ Creative Commons Notice
+ .
+ Creative Commons is not a party to this License, and makes no warranty whatsoever in connection with the Work. Creative Commons will not be liable to You or any party on any legal theory for any damages whatsoever, including without limitation any general, special, incidental or consequential damages arising in connection to this license. Notwithstanding the foregoing two (2) sentences, if Creative Commons has expressly identified itself as the Licensor hereunder, it shall have all rights and obligations of Licensor.
+ .
+ Except for the limited purpose of indicating to the public that the Work is licensed under the CCPL, Creative Commons does not authorize the use by either party of the trademark "Creative Commons" or any related trademark or logo of Creative Commons without the prior written consent of Creative Commons. Any permitted use will be in compliance with Creative Commons' then-current trademark usage guidelines, as may be published on its website or otherwise made available upon request from time to time. For the avoidance of doubt, this trademark restriction does not form part of the License.
+ .
+ Creative Commons may be contacted at http://creativecommons.org/.
diff --git a/debian/live-build.bug-presubj b/debian/live-build.bug-presubj
index 3c9a0b00e..b019b1580 100644
--- a/debian/live-build.bug-presubj
+++ b/debian/live-build.bug-presubj
@@ -1,7 +1,7 @@
Before submitting a bug report against live-build, please make sure
that you have read your guidlines for Debian Live bug reports:
- http://live.debian.net/manual/
+ http://live.debian.net/manual/html/bugs.html
By providing the required information as outlined in the guidlines makes
sure that we can optimally reproduce and fix bugs, not doing so wastes a
diff --git a/debian/live-build.preinst b/debian/live-build.preinst
deleted file mode 100644
index 1d53a0a0f..000000000
--- a/debian/live-build.preinst
+++ /dev/null
@@ -1,25 +0,0 @@
-#!/bin/sh
-
-set -e
-
-case "${1}" in
- upgrade)
- if [ -h /usr/share/live/build/includes/squeeze ]
- then
- rm -f /usr/share/live/build/includes/squeeze
- fi
- ;;
-
- install|abort-upgrade)
-
- ;;
-
- *)
- echo "preinst called with unknown argument \`${1}'" >&2
- exit 1
- ;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff --git a/debian/live-helper.links b/debian/live-helper.links
deleted file mode 100644
index 691e14a62..000000000
--- a/debian/live-helper.links
+++ /dev/null
@@ -1,4 +0,0 @@
-/usr/bin/lb /usr/bin/lh
-/usr/share/man/man1/lb.1.gz /usr/share/man/man1/lh.1.gz
-/usr/bin/live-build /usr/bin/live-helper
-/usr/share/man/man7/live-build.7.gz /usr/share/man/man7/live-helper.7.gz
diff --git a/debian/rules b/debian/rules
index ea8565100..6a24cd52c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,8 +3,15 @@
%:
dh ${@}
+override_dh_auto_clean:
+ $(MAKE) -C po clean
+
+override_dh_auto_build:
+ $(MAKE) -C po update-po
+
override_dh_auto_install:
$(MAKE) DESTDIR=$(CURDIR)/debian/live-build install
+ $(MAKE) -C po DESTDIR=$(CURDIR)/debian/live-build install
mv debian/live-build/usr/share/doc/live-build/ChangeLog.live-package debian/live-build/usr/share/doc/live-build/changelog.live-package
mv debian/live-build/usr/share/doc/live-build/ChangeLog.live-webhelper debian/live-build/usr/share/doc/live-build/changelog.live-webhelper
diff --git a/debian/source/format b/debian/source/format
index d3827e75a..163aaf8d8 100644
--- a/debian/source/format
+++ b/debian/source/format
@@ -1 +1 @@
-1.0
+3.0 (quilt)
diff --git a/docs/AUTHORS b/docs/AUTHORS
index 1d63e4742..3cc45330d 100644
--- a/docs/AUTHORS
+++ b/docs/AUTHORS
@@ -6,4 +6,3 @@ Main Contributors:
* Chris Lamb
* Otavio Salvador
- * Richard Nelson
diff --git a/docs/CREDITS b/docs/CREDITS
index e38e2ee9c..4d89790f4 100644
--- a/docs/CREDITS
+++ b/docs/CREDITS
@@ -48,8 +48,7 @@ Donations (alphabetical order):
Special thanks (alphabetical order):
- * Ben Armstrong for his IRC support and tremendous work on
- documentation.
+ * Ben Armstrong for his IRC support.
* Jason D. Clinton for his work on netboot type.
* Otavio Salvador for his QA patches.
* Richard Nelson for live-webhelper.
diff --git a/docs/FAQ b/docs/FAQ
new file mode 100644
index 000000000..7be46df8b
--- /dev/null
+++ b/docs/FAQ
@@ -0,0 +1,70 @@
+Frequently Asked Questions (FAQ)
+================================
+
+Build Time
+----------
+
+Q: Is live-helper/make-live Debian specific?
+A: live-helper supports Debian and Ubuntu right now. Adding automatic defaults
+ for other Debian derivatives is easy - let us know about them and we may
+ include it.
+
+
+Q: How can I build images with an unprivileged user account?
+A: You can use --root-command sudo or set LH_ROOT_COMMAND="sudo" in
+ config/common.
+
+ *BIG* *FAT* *WARNING*: Building an image as non-root can make your image
+ different compared to a regular Debian system (different owners of files). It
+ is *NOT* recommended to build images as non-root. Do *NOT* use this feature
+ yet.
+
+
+Q: How do I drop in to a shell during make-live chroot process?
+A: Use "--interactive shell", then exit with 'logout' when you have made the
+ setting changes you want and the build process will continue.
+
+
+Q: Where to set the username or the hostname?
+A: casper uses default username 'casper' and hostname 'live'. You can specify
+ them by passing 'username=' and 'hostname=' as kernel parameters.
+
+ live-helper automatically sets the username to 'user' and the hostname to
+ 'debian'. If you want to change this at build time, pass --username and
+ --hostname to make-live, or alter LIVE_USERNAME and LIVE_HOSTNAME in
+ config/image.
+
+
+Q: How can I make my own grub bootsplash?
+A: To add a grub splash screen, you can use --grub-splash FILE, or copy your
+ custom splash to config/binary_grub/splash.xpm.gz.
+
+ Documentation about creating a bootsplash for grub can be found at:
+
+
+
+Q: How can I make my own syslinux bootsplash?
+A: To add a syslinux splash screen, you can use --syslinux-splash FILE, or copy
+ your custom splash to config/binary_syslinux/splash.rle.
+
+ Documentation about creating a bootsplash for grub can be found at:
+
+ contrib/syslinux-splash/COPYING in the live-helper sources.
+
+ Basically, you need to install netpbm and syslinux, and run this:
+ anytopnm < $your_splash > $your_splash.pnm
+ pnmcolormap 15 < $your_splash.pnm > $your_splash.map
+ pnmremap -map=$your_splash.map $your_splash.pnm | \
+ ppmtolss16 '#ffffff=7' > splash.rle
+
+
+Run Time
+--------
+
+Q: What is the root password?
+A: There is none set. You can switch to root with 'sudo -i' or set a password
+ with 'sudo passwd'.
+
+
+Q: What is the user password?
+A: The password for the default user is 'live'.
diff --git a/examples/auto/build b/examples/auto/build
deleted file mode 100755
index 34956c13d..000000000
--- a/examples/auto/build
+++ /dev/null
@@ -1,3 +0,0 @@
-#!/bin/sh
-
-lb build noauto "${@}" 2>&1 | tee binary.log
diff --git a/examples/auto/clean b/examples/auto/clean
deleted file mode 100755
index 436f52d9d..000000000
--- a/examples/auto/clean
+++ /dev/null
@@ -1,5 +0,0 @@
-#!/bin/sh
-
-lb clean noauto "${@}"
-rm -f config/binary config/bootstrap config/chroot config/common config/source
-rm -f binary.log
diff --git a/examples/auto/config b/examples/auto/config
deleted file mode 100755
index e67a471c7..000000000
--- a/examples/auto/config
+++ /dev/null
@@ -1,5 +0,0 @@
-#!/bin/sh
-
-lb config noauto \
- --packages-lists "standard" \
- "${@}"
diff --git a/examples/cron/cron.daily b/examples/cron/cron.daily
new file mode 100755
index 000000000..561075687
--- /dev/null
+++ b/examples/cron/cron.daily
@@ -0,0 +1,155 @@
+#!/bin/sh
+
+set -e
+
+BUILD="daily"
+HOST="$(hostname)"
+
+# Checking for live-build availability
+if [ ! -x /usr/bin/lb ]
+then
+ exit 0
+fi
+
+# Checking for live-build defaults
+if [ -r /etc/default/live-build_autobuild ]
+then
+ . /etc/default/live-build_autobuild
+else
+ echo "E: /etc/default/live-build_autobuild missing."
+ exit 1
+fi
+
+# Checking for autobuild
+if [ "${AUTOBUILD}" != "true" ]
+then
+ exit 0
+fi
+
+# Checking for build directory
+if [ ! -d "${TEMPDIR}" ]
+then
+ mkdir -p "${TEMPDIR}"/debian-live
+else
+ # FIXME: maybe we should just remove the left overs.
+ echo "E: ${TEMPDIR} needs cleanup."
+ exit 1
+fi
+
+echo "$(date +%b\ %d\ %H:%M:%S) ${HOST} live-build: begin daily build." >> /var/log/live
+
+for ARCHITECTURE in ${ARCHITECTURES}
+do
+ for DISTRIBUTION in ${DISTRIBUTIONS}
+ do
+ for PACKAGES_LIST in ${PACKAGES_LISTS}
+ do
+ if [ ! -f "${DESTDIR}"/"${BUILD}"-builds/${DATE}/log/debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${PACKAGES_LIST}_${DATE}-iso-log.txt ]
+ then
+ # Creating build directory
+ mkdir -p "${TEMPDIR}"/debian-live
+
+ cd "${TEMPDIR}"/debian-live
+ echo "Begin: $(date -R)" > "${TEMPDIR}"/debian-live/log.txt
+
+ # Generating images
+ lh_config -b iso -s tar --distribution ${DISTRIBUTION} --packages-lists ${PACKAGES_LIST} --mirror-bootstrap ${MIRROR_BOOTSTRAP} --mirror-binary ${MIRROR_BINARY} --mirror-binary-security ${MIRROR_BINARY_SECURITY} --source true ${OPTIONS}
+ lh_build >> "${TEMPDIR}"/debian-live/log.txt 2>&1
+
+ echo "End: $(date -R)" >> "${TEMPDIR}"/debian-live/log.txt
+ fi
+
+ if [ -f "${TEMPDIR}"/debian-live/binary.iso ] && [ -f "${TEMPDIR}"/debian-live/source.tar ]
+ then
+ # Creating log directory
+ mkdir -p "${DESTDIR}"/"${BUILD}"-builds/${DATE}/log
+
+ # Moving logs
+ mv "${TEMPDIR}"/debian-live/log.txt "${DESTDIR}"/"${BUILD}"-builds/${DATE}/log/debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${PACKAGES_LIST}_${DATE}-iso-log.txt
+ mv "${TEMPDIR}"/debian-live/packages.txt "${DESTDIR}"/"${BUILD}"-builds/${DATE}/log/debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${PACKAGES_LIST}_${DATE}-iso-packages.txt
+
+ # Creating images directory
+ mkdir -p "${DESTDIR}"/"${BUILD}"-builds/${DATE}/${ARCHITECTURE}
+ mkdir -p "${DESTDIR}"/"${BUILD}"-builds/${DATE}/source
+
+ # Moving images
+ mv "${TEMPDIR}"/debian-live/binary.iso "${DESTDIR}"/"${BUILD}"-builds/${DATE}/${ARCHITECTURE}/debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${PACKAGES_LIST}.iso
+ mv "${TEMPDIR}"/debian-live/source.tar "${DESTDIR}"/"${BUILD}"-builds/${DATE}/source/debian-live-${DISTRIBUTION}-source-${PACKAGES_LIST}.tar
+ fi
+
+ if [ ! -f "${DESTDIR}"/"${BUILD}"-builds/${DATE}/log/debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${PACKAGES_LIST}_${DATE}-usb-hdd-log.txt ]
+ then
+ # Workaround of missing multi-binary support in live-build
+ mv "${TEMPDIR}"/debian-live/binary/casper "${TEMPDIR}"/debian-live/casper.tmp
+ rm -rf "${TEMPDIR}"/debian-live/binary* "${TEMPDIR}"/debian-live/.stage/binary_*
+ mkdir "${TEMPDIR}"/debian-live/binary
+ mv "${TEMPDIR}"/debian-live/casper.tmp "${TEMPDIR}"/debian-live/binary/casper
+ touch "${TEMPDIR}"/debian-live/.stage/binary_chroot
+ touch "${TEMPDIR}"/debian-live/.stage/binary_rootfs
+
+ # Creating build directory
+ mkdir -p "${TEMPDIR}"/debian-live
+
+ cd "${TEMPDIR}"/debian-live
+ echo "Begin: $(date -R)" > "${TEMPDIR}"/debian-live/log.txt
+
+ # Generating images
+ lh_config -b usb-hdd -s tar --distribution ${DISTRIBUTION} --packages-lists ${PACKAGES_LIST} --mirror-bootstrap ${MIRROR_BOOTSTRAP} --mirror-binary ${MIRROR_BINARY} --mirror-binary-security ${MIRROR_BINARY_SECURITY} --source false ${OPTIONS}
+ lh_build >> "${TEMPDIR}"/debian-live/log.txt 2>&1
+
+ echo "End: $(date -R)" >> "${TEMPDIR}"/debian-live/log.txt
+ fi
+
+ if [ -f "${TEMPDIR}"/debian-live/binary.img ]
+ then
+ # Creating log directory
+ mkdir -p "${DESTDIR}"/"${BUILD}"-builds/${DATE}/log
+
+ # Moving logs
+ mv "${TEMPDIR}"/debian-live/log.txt "${DESTDIR}"/"${BUILD}"-builds/${DATE}/log/debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${PACKAGES_LIST}_${DATE}-usb-hdd-log.txt
+ cp "${DESTDIR}"/"${BUILD}"-builds/${DATE}/log/debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${PACKAGES_LIST}_${DATE}-iso-packages.txt "${DESTDIR}"/"${BUILD}"-builds/${DATE}/log/debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${PACKAGES_LIST}_${DATE}-usb-hdd-packages.txt
+
+ # Creating image directory
+ mkdir -p "${DESTDIR}"/"${BUILD}"-builds/${DATE}/${ARCHITECTURE}
+
+ # Moving images
+ mv "${TEMPDIR}"/debian-live/binary.img "${DESTDIR}"/"${BUILD}"-builds/${DATE}/${ARCHITECTURE}/debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${PACKAGES_LIST}.img
+ fi
+
+ # Cleanup
+ cd "${TEMPDIR}"/debian-live
+ lh_clean
+ done
+
+ # Cleanup
+ cd "${TEMPDIR}"/debian-live
+ lh_clean purge
+ done
+done
+
+# Cleaning up
+if [ -f "${TEMPDIR}"/debian-live/chroot/proc/version ]
+then
+ umount "${TEMPDIR}"/debian-live/chroot/proc
+fi
+
+if [ -d "${TEMPDIR}"/debian-live/chroot/sys/kernel ]
+then
+ umount "${TEMPDIR}"/debian-live/chroot/sys
+fi
+
+# Removing build directory
+rm -rf "${TEMPDIR}"
+
+# Creating md5sums
+for DIRECTORY in "${DESTDIR}"/"${BUILD}"-builds/${DATE}/*
+do
+ cd "${DIRECTORY}"
+ md5sum * > MD5SUMS
+done
+
+# Creating current symlink
+rm -f "${DESTDIR}"/"${BUILD}"-builds/current
+ln -s ${DATE} "${DESTDIR}"/"${BUILD}"-builds/current
+
+echo "$(date +%b\ %d\ %H:%M:%S) ${HOST} live-build: end daily build." >> /var/log/live
diff --git a/examples/cron/default b/examples/cron/default
new file mode 100644
index 000000000..1778b5e89
--- /dev/null
+++ b/examples/cron/default
@@ -0,0 +1,16 @@
+# Defaults for /etc/cron.daily/live-build_autobuild
+
+AUTOBUILD="false"
+
+DATE="$(date +%Y%m%d)"
+DESTDIR="/srv/debian-live"
+TEMPDIR="/srv/tmp/live-build"
+
+OPTIONS="--binary-indices false"
+
+ARCHITECTURES="$(dpkg --print-architecture)"
+DISTRIBUTIONS="sid"
+MIRROR_BOOTSTRAP="http://ftp.debian.org/debian/"
+MIRROR_BINARY="http://ftp.debian.org/debian/"
+MIRROR_BINARY_SECURITY="http://security.debian.org/"
+PACKAGES_LISTS="standard rescue gnome-desktop kde-desktop xfce-desktop"
diff --git a/examples/cron/images.sh b/examples/cron/images.sh
new file mode 100755
index 000000000..a6aebd95d
--- /dev/null
+++ b/examples/cron/images.sh
@@ -0,0 +1,192 @@
+#!/bin/sh
+
+set -e
+
+# Static variables
+DISTRIBUTIONS="${DISTRIBUTIONS:-lenny squeeze sid}"
+FLAVOURS="${FLAVOURS:-standard rescue gnome-desktop kde-desktop lxde-desktop xfce-desktop}"
+SOURCE="${SOURCE:-true}"
+
+MIRROR="${MIRROR:-http://cdn.debian.net/debian/}"
+MIRROR_SECURITY="${MIRROR_SECURITY:-http://security.debian.org/}"
+
+# Dynamic variables
+ARCHITECTURE="$(dpkg --print-architecture)"
+DATE="$(date +%Y%m%d)"
+
+Set_defaults ()
+{
+ # Distribution defaults
+ APT_RECOMMENDS="true"
+ BINARY_INDICES="true"
+ DEBIAN_INSTALLER="live"
+ DEBIAN_INSTALLER_GUI="true"
+ PACKAGES="--packages live-installer-launcher"
+ TASKSEL="tasksel"
+
+ # Distribution specific options (ugly!)
+ case "${DISTRIBUTION}" in
+ lenny)
+ APT_RECOMMENDS="false"
+ BINARY_INDICES="true"
+ DEBIAN_INSTALLER="false"
+ PACKAGES=""
+ TASKSEL="aptitude"
+
+ case "${ARCHITECTURE}" in
+ amd64)
+ case "${FLAVOUR}" in
+ gnome-desktop)
+ BINARY_INDICES="false"
+
+ mkdir -p config/chroot_local-hooks
+ cd config/chroot_local-hooks
+ echo "apt-get remove --yes --purge openoffice.org-help-en-us" > package-removals
+ echo "apt-get remove --yes --purge epiphany-browser epiphany-browser-data epiphany-extensions epiphany-gecko" >> package-removals
+ echo "apt-get remove --yes --purge gnome-user-guide" >> package-removals
+ cd -
+ ;;
+
+ kde-desktop)
+ BINARY_INDICES="false"
+ ;;
+ esac
+ ;;
+
+ i386)
+ case "${FLAVOUR}" in
+ gnome-desktop|kde-desktop)
+ BINARY_INDICES="false"
+ KERNEL="-k 686"
+ ;;
+ esac
+ ;;
+ esac
+ ;;
+
+ squeeze)
+ DEBIAN_INSTALLER_DISTRIBUTION="daily"
+ DEBIAN_INSTALLER_GUI="false"
+
+ LIVE_INSTALLER="20"
+ LIVE_BOOT="2.0~a15-1"
+ LIVE_CONFIG="2.0~a15-1"
+
+ mkdir -p config/binary_local-udebs
+ cd config/binary_local-udebs
+ wget -c http://live.debian.net/archive/packages/live-installer/${LIVE_INSTALLER}/live-installer_${LIVE_INSTALLER}.dsc
+ wget -c http://live.debian.net/archive/packages/live-installer/${LIVE_INSTALLER}/live-installer_${LIVE_INSTALLER}.tar.gz
+ wget -c http://live.debian.net/archive/packages/live-installer/${LIVE_INSTALLER}/live-installer_${LIVE_INSTALLER}_i386.udeb
+ cd -
+
+ mkdir -p config/chroot_local-packages
+ cd config/chroot_local-packages
+
+ wget -c http://live.debian.net/archive/packages/live-installer/${LIVE_INSTALLER}/live-installer_${LIVE_INSTALLER}.dsc
+ wget -c http://live.debian.net/archive/packages/live-installer/${LIVE_INSTALLER}/live-installer_${LIVE_INSTALLER}.tar.gz
+ wget -c http://live.debian.net/archive/packages/live-installer/${LIVE_INSTALLER}/live-installer-launcher_${LIVE_INSTALLER}_all.deb
+
+ wget -c http://live.debian.net/archive/packages/live-boot/${LIVE_BOOT}/live-boot_${LIVE_BOOT}.dsc
+ wget -c http://live.debian.net/archive/packages/live-boot/${LIVE_BOOT}/live-boot_${LIVE_BOOT}.diff.gz
+ wget -c http://live.debian.net/archive/packages/live-boot/${LIVE_BOOT}/live-boot_$(echo ${LIVE_BOOT} | awk -F- '{ print $1 }').orig.tar.gz
+ wget -c http://live.debian.net/archive/packages/live-boot/${LIVE_BOOT}/live-boot_${LIVE_BOOT}_all.deb
+ wget -c http://live.debian.net/archive/packages/live-boot/${LIVE_BOOT}/live-boot-initramfs-tools_${LIVE_BOOT}_all.deb
+ wget -c http://live.debian.net/archive/packages/live-boot/${LIVE_BOOT}/live-initramfs_${LIVE_BOOT}_all.deb
+
+ wget -c http://live.debian.net/archive/packages/live-config/${LIVE_CONFIG}/live-config_${LIVE_CONFIG}.dsc
+ wget -c http://live.debian.net/archive/packages/live-config/${LIVE_CONFIG}/live-config_${LIVE_CONFIG}.diff.gz
+ wget -c http://live.debian.net/archive/packages/live-config/${LIVE_CONFIG}/live-config_$(echo ${LIVE_CONFIG} | awk -F- '{ print $1 }').orig.tar.gz
+ wget -c http://live.debian.net/archive/packages/live-config/${LIVE_CONFIG}/live-config_${LIVE_CONFIG}_all.deb
+ wget -c http://live.debian.net/archive/packages/live-config/${LIVE_CONFIG}/live-config-sysvinit_${LIVE_CONFIG}_all.deb
+
+ cd -
+ ;;
+ esac
+}
+
+# Build images
+for DISTRIBUTION in ${DISTRIBUTIONS}
+do
+ rm -rf cache/stages*
+
+ for FLAVOUR in ${FLAVOURS}
+ do
+ if [ -e .stage ]
+ then
+ lb clean
+ fi
+
+ if [ -e config ]
+ then
+ rm -f config/* || true
+ rmdir --ignore-fail-on-non-empty config/* || true
+ fi
+
+ rm -rf cache/packages*
+ rm -rf cache/stages_rootfs
+
+ Set_defaults
+
+ lb config \
+ --apt-recommends ${APT_RECOMMENDS} \
+ --binary-indices ${BINARY_INDICES} \
+ --cache-stages "bootstrap rootfs" \
+ --debian-installer ${DEBIAN_INSTALLER} \
+ --debian-installer-distribution ${DEBIAN_INSTALLER_DISTRIBUTION} \
+ --debian-installer-gui ${DEBIAN_INSTALLER_GUI} \
+ --distribution ${DISTRIBUTION} \
+ --mirror-bootstrap ${MIRROR} \
+ --mirror-chroot ${MIRROR} \
+ --mirror-chroot-security ${MIRROR_SECURITY} \
+ ${PACKAGES} \
+ --packages-lists ${FLAVOUR} \
+ --tasksel ${TASKSEL} ${KERNEL}
+
+ lb build 2>&1 | tee debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.iso.log
+
+ mv binary*.iso debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.iso
+ mv binary.list debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.iso.list
+ mv binary.packages debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.iso.packages
+
+ if [ "${DISTRIBUTION}" = "lenny" ] && [ "${ARCHITECTURE}" != "powerpc" ]
+ then
+ lb clean --binary
+ lb config -binary-images usb-hdd
+ lb binary 2>&1 | tee debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.img.log
+
+ mv binary.img debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.img
+ mv binary.list debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.img.list
+ mv binary.packages debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.img.packages
+ fi
+
+ if [ "${ARCHITECTURE}" != "powerpc" ]
+ then
+ lb clean
+ rm -rf cache/stages_rootfs
+ lb config --binary-images net
+
+ lb build 2>&1 | tee debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.tar.gz.log
+
+ mv binary-net.tar.gz debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.tar.gz
+ mv binary.list debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.tar.gz.list
+ mv binary.packages debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.tar.gz.packages
+
+ mv binary/*/filesystem.squashfs debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.squashfs
+ for memtest in tftpboot/debian-live/${ARCHITECTURE}/memtest*; do cp -f ${memtest} debian-live-${DISTRIBUTION}-${ARCHITECTURE}.$(basename ${memtest}); done || true
+ for kernel in tftpboot/debian-live/${ARCHITECTURE}/vmlinuz*; do cp -f ${kernel} debian-live-${DISTRIBUTION}-${ARCHITECTURE}.$(basename ${kernel}); done
+ for initrd in tftpboot/debian-live/${ARCHITECTURE}/initrd*; do cp ${initrd} debian-live-${DISTRIBUTION}-${ARCHITECTURE}-${FLAVOUR}.$(basename ${initrd}); done
+ fi
+
+ if [ "${SOURCE}" = "true" ]
+ then
+ lb config --source true
+
+ lb source 2>&1 | tee debian-live-${DISTRIBUTION}-source-${FLAVOUR}.log
+
+ mv source.debian.tar.gz debian-live-${DISTRIBUTION}-source-${FLAVOUR}.debian.tar.gz
+ mv source.debian.list debian-live-${DISTRIBUTION}-source-${FLAVOUR}.debian.tar.gz.list
+ mv source.debian-live.tar.gz debian-live-${DISTRIBUTION}-source-${FLAVOUR}.debian-live.tar.gz
+ mv source.debian-live.list debian-live-${DISTRIBUTION}-source-${FLAVOUR}.debian-live.tar.gz.list
+ fi
+ done
+done
diff --git a/examples/hooks/all_binary_debian-installer-banner.sh b/examples/hooks/all_binary_debian-installer-banner.sh
index 61c160ca6..76c5d0785 100755
--- a/examples/hooks/all_binary_debian-installer-banner.sh
+++ b/examples/hooks/all_binary_debian-installer-banner.sh
@@ -5,7 +5,7 @@
# To enable it, copy or symlink this hook into your config/binary_local-hooks
# directory and add a replacement banner.png at:
#
-# config/binary_debian-installer/banner.png
+# config/binary_local-includes/binary/install/banner.png
#
# The file should be a PNG image of dimensions 800 x 75.
diff --git a/examples/hooks/all_chroot_losetup-lukshome.sh b/examples/hooks/all_chroot_losetup-lukshome.sh
index b6f33bf7f..95d3c053a 100755
--- a/examples/hooks/all_chroot_losetup-lukshome.sh
+++ b/examples/hooks/all_chroot_losetup-lukshome.sh
@@ -333,32 +333,27 @@ do
esac
done
-if [ -x /sbin/blkid ]
-then
- CRYPTHOME=$(/sbin/blkid -L ${LUKSPART})
-else
- # search for a partition labeled "lukshome" or $LUKSPART
- for sysblock in $(echo /sys/block/* | tr ' ' '\n' | grep -v loop | grep -v ram | grep -v fd)
+# search for a partition labeled "lukshome" or $LUKSPART
+for sysblock in $(echo /sys/block/* | tr ' ' '\n' | grep -v loop | grep -v ram | grep -v fd)
+do
+ for dev in $(subdevices "${sysblock}")
do
- for dev in $(subdevices "${sysblock}")
- do
- devname=$(sys2dev "${dev}")
- # find partition name and filesystem type
- if [ "$(/lib/udev/vol_id -l ${devname} 2>/dev/null)" = "${LUKSPART}" ]
- then
- # found one partition with correct label
- CRYPTHOME="${devname}"
- # don't search further
- break
- fi
- done
- # if already found, don't search further
- if [ -n "${CRYPTHOME}" ]
+ devname=$(sys2dev "${dev}")
+ # find partition name and filesystem type
+ if [ "$(/lib/udev/vol_id -l ${devname} 2>/dev/null)" = "${LUKSPART}" ]
then
+ # found one partition with correct label
+ CRYPTHOME="${devname}"
+ # don't search further
break
fi
done
-fi
+ # if already found, don't search further
+ if [ -n "${CRYPTHOME}" ]
+ then
+ break
+ fi
+done
# if no partition found, exit
if [ -z "${CRYPTHOME}" ]
diff --git a/examples/hooks/lenny_binary_live-installer-usbfix.sh b/examples/hooks/lenny_binary_live-installer-usbfix.sh
deleted file mode 100755
index ded8b80ed..000000000
--- a/examples/hooks/lenny_binary_live-installer-usbfix.sh
+++ /dev/null
@@ -1,96 +0,0 @@
-#!/bin/sh
-
-echo "BINARY-HOOK: fix install from USB in Lenny."
-
-# This is a *binary-hook* to allow disk installations from USB for
-# Debian 5.0.x Lenny. Place this file in config/binary_local-hooks/,
-# make it executable and rebuild your live image (binary only).
-
-# This workaround for debian-installer was adapted from Chris Lamb
-original patch:
-# http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498143#5
-
-# It works by fooling apt-setup. With an existing /hd-media directory
-# apt-setup will not try to umount /cdrom. Enable live installer with
-# lh_config:
-#
-# lh_config --debian-installer "live"
-#
-# Rebuild your binary image. No options needed on boot.
-
-cat > cdrom-detect.postinst.patch << 'EOF'
-@@ -44,6 +44,30 @@ do
- fi
- done
-
-+ # Try disk partitions masquerading as Debian CDs for Debian Live
-+ # "usb-hdd" images. Only vfat and ext are supported.
-+ modprobe vfat >/dev/null 2>&1 || true
-+ for device in $(list-devices partition); do
-+ if mount -t vfat -o ro,exec $device /cdrom ||
-+ mount -t ext2 -o ro,exec $device /cdrom; then
-+ log "Pseudo CD-ROM mount succeeded: device=$device"
-+
-+ # Test whether it's a Debian CD
-+ if [ -e /cdrom/.disk/info ]; then
-+ mounted=1
-+ db_set cdrom-detect/cdrom_device $device
-+ # fake hd-media install so that apt-setup doesn't break.
-+ mkdir /hd-media
-+ break
-+ else
-+ log "Ignoring pseudo CD-ROM device $device - it is not a Debian CD"
-+ umount /cdrom 2>/dev/null || true
-+ fi
-+ else
-+ log "Psuedo CD-ROM mount failed: device=$device"
-+ fi
-+ done
-+
- if [ "$mounted" = "1" ]; then
- break
- fi
-
-EOF
-
-# for the syslinux installer
-mkdir usb-install-syslinux
-cd usb-install-syslinux
-zcat ../binary/install/initrd.gz | cpio -iv
-patch ./var/lib/dpkg/info/cdrom-detect.postinst < ../cdrom-detect.postinst.patch
-PATCH_ERROR=${?}
-if [ "${PATCH_ERROR}" != 0 ]
-then
- # if there was an error, say it and undo everything.
- echo "ERROR: error while patching cdrom-detect.postinst."
- cd ..
- rmdir -rf usb-install-syslinux
- exit 0
-fi
-# rebuild the initrd
-find . -print0 | cpio -0 -H newc -ov | gzip -c > ../initrd-new.gz
-cd ..
-mv initrd-new.gz binary/install/initrd.gz
-rm -rf usb-install-syslinux
-
-# for the gtk installer
-mkdir usb-install-gtk
-cd usb-install-gtk
-zcat ../binary/install/gtk/initrd.gz | cpio -iv
-patch ./var/lib/dpkg/info/cdrom-detect.postinst < ../cdrom-detect.postinst.patch
-PATCH_ERROR=${?}
-if [ "${PATCH_ERROR}" != 0 ]
-then
- # if there was an error, say it and undo everything
- echo "ERROR: error while patching cdrom-detect.postinst."
- cd ..
- rmdir -rf usb-install-gtk
- exit 0
-fi
-# rebuild the initrd
-find . -print0 | cpio -0 -H newc -ov | gzip -c > ../initrd-new.gz
-cd ..
-mv initrd-new.gz binary/install/gtk/initrd.gz
-rm -rf usb-install-gtk
-
-rm cdrom-detect.postinst.patch
diff --git a/examples/hooks/lenny_chroot_aufs-modules.sh b/examples/hooks/lenny_chroot_aufs-modules.sh
deleted file mode 100755
index 2d0d16e40..000000000
--- a/examples/hooks/lenny_chroot_aufs-modules.sh
+++ /dev/null
@@ -1,23 +0,0 @@
-#!/bin/sh
-
-# This is a hook for live-build(7) to install aufs drivers
-# To enable it, copy or symlink this hook into your config/chroot_local-hooks
-# directory.
-#
-# Note: You only want to use this hook if there is no prebuild aufs-modules-*
-# package available for your kernel flavour.
-
-apt-get install --yes build-essential
-
-# Building kernel module
-which module-assistant || apt-get install --yes module-assistant
-module-assistant update
-
-for KERNEL in /boot/vmlinuz-*
-do
- VERSION="$(basename ${KERNEL} | sed -e 's|vmlinuz-||')"
-
- module-assistant --non-inter --quiet auto-install aufs -l ${VERSION}
-done
-
-module-assistant clean aufs
diff --git a/examples/hooks/lenny_chroot_kpdf-nodrm.sh b/examples/hooks/lenny_chroot_kpdf-nodrm.sh
deleted file mode 100755
index 20a4f9f33..000000000
--- a/examples/hooks/lenny_chroot_kpdf-nodrm.sh
+++ /dev/null
@@ -1,17 +0,0 @@
-#!/bin/sh
-
-# This is a hook for live-build(7) to configure KDE's PDF viewer to ignore
-# manipulation restriction on "DRM protect" PDF documents.
-#
-# To enable it, copy or symlink this hook into your config/chroot_local-hooks
-# directory.
-
-if [ -d /usr/share/config ]
-then
-
-cat > /usr/share/config/kpdfpartrc << EOF
-[General]
-ObeyDRM=false
-EOF
-
-fi
diff --git a/examples/hooks/lenny_chroot_madwifi-modules.sh b/examples/hooks/lenny_chroot_madwifi-modules.sh
deleted file mode 100755
index 336e84ca3..000000000
--- a/examples/hooks/lenny_chroot_madwifi-modules.sh
+++ /dev/null
@@ -1,26 +0,0 @@
-#!/bin/sh
-
-# This is a hook for live-build(7) to install madwifi drivers
-# To enable it, copy or symlink this hook into your config/chroot_local-hooks
-# directory.
-#
-# Note: This hook requires packages from the contrib category. Make sure you enabled
-# it in your configuration.
-
-apt-get install --yes build-essential
-
-# Building kernel module
-which module-assistant || apt-get install --yes module-assistant
-module-assistant update
-
-for KERNEL in /boot/vmlinuz-*
-do
- VERSION="$(basename ${KERNEL} | sed -e 's|vmlinuz-||')"
-
- module-assistant --non-inter --quiet auto-install madwifi -l ${VERSION}
-done
-
-module-assistant clean madwifi
-
-# Installing additional stuff
-apt-get install --yes madwifi-tools
diff --git a/examples/hooks/lenny_chroot_nvidia-legacy-modules.sh b/examples/hooks/lenny_chroot_nvidia-legacy-modules.sh
deleted file mode 100755
index 7374ce4a2..000000000
--- a/examples/hooks/lenny_chroot_nvidia-legacy-modules.sh
+++ /dev/null
@@ -1,56 +0,0 @@
-#!/bin/sh
-
-# This is a hook for live-build(7) to install nvidia-kernel-legacy drivers
-# To enable it, copy or symlink this hook into your config/chroot_local-hooks
-# directory.
-#
-# Note: This hook requires packages from the non-free category. Make sure you
-# enabled it in your configuration.
-
-apt-get install --yes build-essential
-
-# Building kernel module
-which module-assistant || apt-get install --yes module-assistant nvidia-kernel-common
-module-assistant update
-
-for KERNEL in /boot/vmlinuz-*
-do
- VERSION="$(basename ${KERNEL} | sed -e 's|vmlinuz-||')"
-
- module-assistant --non-inter --quiet auto-install nvidia-kernel-legacy -l ${VERSION}
-done
-
-module-assistant clean nvidia-kernel-legacy
-
-# Installing additional stuff
-apt-get install --yes nvidia-glx-legacy nvidia-xconfig discover
-
-# Fix #421028
-if [ -f /usr/lib/xorg/modules/drivers/nvidia_drv.o ]
-then
- cd /usr/lib/xorg/modules/drivers
- gcc -shared -o nvidia_drv.so nvidia_drv.o
- cd ${OLDPWD}
-fi
-
-# Adding init script
-cat > /etc/init.d/nvidia-debian-live << EOF
-#!/bin/sh
-# script that modify xorg configuration enabling
-# the nvidia proprietary module if the card is detected
-# as an NVidia
-
-if discover --type-summary display | grep -i nvidia
-then
- # forcing depth to 24, bad detection on some card (e.g my GeForce4 440 Go)
- echo "Configuring Xorg for nvidia ..."
- nvidia-xconfig -d 24
-else
- # not with nvidia h/w ? remove those GLX diversions
- # (FIXME)
- apt-get --quiet --yes remove nvidia-glx-legacy
-fi
-EOF
-
-chmod 0755 /etc/init.d/nvidia-debian-live
-update-rc.d nvidia-debian-live defaults
diff --git a/examples/hooks/lenny_chroot_squashfs-modules.sh b/examples/hooks/lenny_chroot_squashfs-modules.sh
deleted file mode 100755
index cfa2f776c..000000000
--- a/examples/hooks/lenny_chroot_squashfs-modules.sh
+++ /dev/null
@@ -1,23 +0,0 @@
-#!/bin/sh
-
-# This is a hook for live-build(7) to install squashfs drivers
-# To enable it, copy or symlink this hook into your config/chroot_local-hooks
-# directory.
-#
-# Note: You only want to use this hook if there is no prebuild
-# squashfs-modules-* package available for your kernel flavour.
-
-apt-get install --yes build-essential
-
-# Building kernel module
-which module-assistant || apt-get install --yes module-assistant
-module-assistant update
-
-for KERNEL in /boot/vmlinuz-*
-do
- VERSION="$(basename ${KERNEL} | sed -e 's|vmlinuz-||')"
-
- module-assistant --non-inter --quiet auto-install squashfs -l ${VERSION}
-done
-
-module-assistant clean squashfs
diff --git a/examples/hooks/lenny_chroot_sun-java5.sh b/examples/hooks/lenny_chroot_sun-java5.sh
deleted file mode 100755
index 27034a7e3..000000000
--- a/examples/hooks/lenny_chroot_sun-java5.sh
+++ /dev/null
@@ -1,28 +0,0 @@
-#!/bin/sh
-
-# This is a hook for live-build(7) to install sun-java.
-# To enable it, copy or symlink this hook into your config/chroot_local-hooks
-# directory.
-#
-# Note: This hook requires packages from the non-free category. Make sure you
-# enabled it in your configuration.
-
-# live-build sets DEBIAN_FRONTEND to 'noninteractive' to advise debconf to not
-# ask any questions while installing packages. Suns redistribution terms for
-# Java do not allow this, therefore we need to overwrite DEBIAN_FRONTEND for
-# this apt-get call only.
-
-# In case you do accept the license terms, you can also preseed the values
-# for a complete non-interactive build, by uncommenting the following three lines:
-
-#echo "sun-java5-bin shared/accepted-sun-dlj-v1-1 boolean true" > /root/preseed
-#debconf-set-selections < /root/preseed
-#rm -f /root/preseed
-
-DEBIAN_FRONTEND="dialog" apt-get install --yes sun-java5-bin sun-java5-demo \
- sun-java5-doc sun-java5-fonts sun-java5-jdk sun-java5-jre \
- sun-java5-plugin sun-java5-source
-
-# Ensure that /tmp has the right permissions; apparently sun-java5-doc tampers
-# with it
-chmod 1777 /tmp
diff --git a/functions/aliases.sh b/functions/aliases.sh
index 9c7972983..8e1dddad4 100755
--- a/functions/aliases.sh
+++ b/functions/aliases.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/architecture.sh b/functions/architecture.sh
index c3361a785..b49729348 100755
--- a/functions/architecture.sh
+++ b/functions/architecture.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/arguments.sh b/functions/arguments.sh
index 9a675e6a6..0db3c13d0 100755
--- a/functions/arguments.sh
+++ b/functions/arguments.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/breakpoints.sh b/functions/breakpoints.sh
index 025628517..29ab8610c 100755
--- a/functions/breakpoints.sh
+++ b/functions/breakpoints.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/cache.sh b/functions/cache.sh
index c2978318e..bae606dd2 100755
--- a/functions/cache.sh
+++ b/functions/cache.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/chroot.sh b/functions/chroot.sh
index dff13d062..589200add 100755
--- a/functions/chroot.sh
+++ b/functions/chroot.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/color.sh b/functions/color.sh
index 78e37e0a1..9bdd8371d 100755
--- a/functions/color.sh
+++ b/functions/color.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/common.sh b/functions/common.sh
index 75f4ae784..98c8cfaee 100755
--- a/functions/common.sh
+++ b/functions/common.sh
@@ -1,15 +1,15 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build 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.
-PROGRAM="live-build"
-VERSION="2.0.12-1"
+PACKAGE="live-build"
+VERSION="3.0~a1-1"
CONFIG_VERSION="$(echo ${VERSION} | awk -F- '{ print $1 }')"
PATH="${PWD}/auto/scripts:${PATH}"
diff --git a/functions/conffile.sh b/functions/conffile.sh
index 05fd7e8ef..02730dfd8 100755
--- a/functions/conffile.sh
+++ b/functions/conffile.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
@@ -17,9 +17,9 @@ Get_conffiles ()
for FILE in ${@}
do
FILES="${FILES} ${FILE} ${FILE}.${LB_ARCHITECTURE} ${FILE}.${DISTRIBUTION}"
- FILES="${FILES} config/$(echo ${PROGRAM} | sed -e 's|^lb_||')"
- FILES="${FILES} config/$(echo ${PROGRAM} | sed -e 's|^lb_||').${ARCHITECTURE}"
- FILES="${FILES} config/$(echo ${PROGRAM} | sed -e 's|^lb_||').${DISTRIBUTION}"
+ FILES="${FILES} config/$(echo ${PROGRAM} | sed -e 's|^lh_||')"
+ FILES="${FILES} config/$(echo ${PROGRAM} | sed -e 's|^lh_||').${ARCHITECTURE}"
+ FILES="${FILES} config/$(echo ${PROGRAM} | sed -e 's|^lh_||').${DISTRIBUTION}"
done
fi
diff --git a/functions/cursor.sh b/functions/cursor.sh
index f01300943..6ea1d9a9e 100755
--- a/functions/cursor.sh
+++ b/functions/cursor.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/defaults.sh b/functions/defaults.sh
index bd6c67953..57cf37c20 100755
--- a/functions/defaults.sh
+++ b/functions/defaults.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
@@ -57,7 +57,7 @@ Set_defaults ()
then
LB_APT_HTTP_PROXY="${http_proxy}"
else
- if [ -n "${LB_APT_HTTP_PROXY}" ] && [ "${LB_APT_HTTP_PROXY}" != "${http_proxy}" ]
+ if [ -n "${LB_APT_HTTP_PROXY}" ] && [ "${LB_APT_HTT_PROXY}" != "${http_proxy}" ]
then
http_proxy="${LB_APT_HTTP_PROXY}"
fi
@@ -348,10 +348,6 @@ Set_defaults ()
lenny)
LB_MIRROR_CHROOT_VOLATILE="http://volatile.debian.org/debian-volatile/"
;;
-
- squeeze)
- LB_MIRROR_CHROOT_VOLATILE="${LB_MIRROR_CHROOT}"
- ;;
esac
;;
@@ -448,9 +444,6 @@ Set_defaults ()
lenny)
LB_MIRROR_BINARY_VOLATILE="http://volatile.debian.org/debian-volatile/"
;;
-
- squeeze)
- LB_MIRROR_BINARY_VOLATILE="${LB_MIRROR_BINARY}"
esac
;;
@@ -728,7 +721,6 @@ Set_defaults ()
*)
LB_TASKS="$(echo ${LB_TASKS} | sed -e 's|standard||' -e 's|gnome-desktop||' -e 's|desktop||' -e 's|laptop||') standard gnome-desktop desktop laptop"
- LB_PACKAGES="$(echo ${LB_PACKAGES} | sed -e 's|debian-installer-launcher||') debian-installer-launcher"
;;
esac
;;
@@ -743,7 +735,6 @@ Set_defaults ()
*)
LB_TASKS="$(echo ${LB_TASKS} | sed -e 's|standard||' -e 's|kde-desktop||' -e 's|desktop||' -e 's|laptop||') standard kde-desktop desktop laptop"
- LB_PACKAGES="$(echo ${LB_PACKAGES} | sed -e 's|debian-installer-launcher||') debian-installer-launcher"
esac
;;
@@ -757,7 +748,6 @@ Set_defaults ()
*)
LB_TASKS="$(echo ${LB_TASKS} | sed -e 's|standard||' -e 's|lxde-desktop||' -e 's|desktop||' -e 's|laptop||') standard lxde-desktop desktop laptop"
- LB_PACKAGES="$(echo ${LB_PACKAGES} | sed -e 's|debian-installer-launcher||') debian-installer-launcher"
;;
esac
;;
@@ -772,7 +762,6 @@ Set_defaults ()
*)
LB_TASKS="$(echo ${LB_TASKS} | sed -e 's|standard||' -e 's|xfce-desktop||' -e 's|desktop||' -e 's|laptop||') standard xfce-desktop desktop laptop"
- LB_PACKAGES="$(echo ${LB_PACKAGES} | sed -e 's|debian-installer-launcher||') debian-installer-launcher"
;;
esac
;;
@@ -877,7 +866,28 @@ Set_defaults ()
# Setting debian-installer-gui
case "${LB_MODE}" in
debian)
- LB_DEBIAN_INSTALLER_GUI="${LB_DEBIAN_INSTALLER_GUI:-true}"
+ case "${LB_DISTRIBUTION}" in
+ squeeze|sid)
+ LB_DEBIAN_INSTALLER_GUI="${LB_DEBIAN_INSTALLER_GUI:-false}"
+ ;;
+
+ *)
+ LB_DEBIAN_INSTALLER_GUI="${LB_DEBIAN_INSTALLER_GUI:-true}"
+ ;;
+ esac
+ ;;
+
+ ubuntu)
+ case "${LB_DEBIAN_INSTALLER_DISTRIBUTION}" in
+ karmic)
+ # Not available for Karmic currently.
+ LB_DEBIAN_INSTALLER_GUI="${LB_DEBIAN_INSTALLER_GUI:-false}"
+ ;;
+
+ *)
+ LB_DEBIAN_INSTALLER_GUI="${LB_DEBIAN_INSTALLER_GUI:-true}"
+ ;;
+ esac
;;
*)
@@ -931,6 +941,16 @@ Set_defaults ()
esac
fi
+ case "${LB_BINARY_IMAGES}" in
+ iso-hybrid|usb*)
+ # Try USB block devices for install media
+ if ! echo "${LB_BOOTAPPEND_INSTALL}" | grep -q try-usb
+ then
+ LB_BOOTAPPEND_INSTALL="cdrom-detect/try-usb=true ${LB_BOOTAPPEND_INSTALL}"
+ fi
+ ;;
+ esac
+
if [ -n ${_LB_BOOTAPPEND_PRESEED} ]
then
LB_BOOTAPPEND_INSTALL="${LB_BOOTAPPEND_INSTALL} ${_LB_BOOTAPPEND_PRESEED}"
diff --git a/functions/echo.sh b/functions/echo.sh
index 7dbfac4d7..555bc42bb 100755
--- a/functions/echo.sh
+++ b/functions/echo.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
@@ -13,7 +13,12 @@ Echo ()
STRING="${1}"
shift
- printf "${STRING}\n" "${@}"
+ if [ "${_L10N}" = "false" ]
+ then
+ printf "${STRING}\n" "${@}"
+ else
+ printf "$(eval_gettext "${STRING}")" "${@}"; echo;
+ fi
}
Echo_debug ()
@@ -23,7 +28,12 @@ Echo_debug ()
STRING="${1}"
shift
- printf "D: ${STRING}\n" "${@}"
+ if [ "${_L10N}" = "false" ]
+ then
+ printf "D: ${STRING}\n" "${@}"
+ else
+ printf "D: $(eval_gettext "${STRING}")" "${@}"; echo;
+ fi
fi
}
@@ -34,7 +44,12 @@ Echo_debug_running ()
STRING="${1}"
shift
- printf "D: ${STRING}" "${@}"
+ if [ "${_L10N}" = "false" ]
+ then
+ printf "D: ${STRING}" "${@}"
+ else
+ printf "D: $(eval_gettext "${STRING}")" "${@}"
+ fi
if [ "${_COLOR}" = "false" ]
then
@@ -57,7 +72,12 @@ Echo_error ()
printf "${RED}E${NO_COLOR}:"
fi
- printf " ${STRING}\n" "${@}" >&2
+ if [ "${_L10N}" = "false" ]
+ then
+ printf " ${STRING}\n" "${@}" >&2
+ else
+ (printf " $(eval_gettext "${STRING}")" "${@}"; echo;) >&2
+ fi
}
Echo_message ()
@@ -74,7 +94,12 @@ Echo_message ()
printf "${WHITE}P${NO_COLOR}:"
fi
- printf " ${STRING}\n" "${@}"
+ if [ "${_L10N}" = "false" ]
+ then
+ printf " ${STRING}\n" "${@}"
+ else
+ printf " $(eval_gettext "${STRING}")" "${@}"; echo;
+ fi
fi
}
@@ -92,7 +117,12 @@ Echo_message_running ()
printf "${WHITE}P${NO_COLOR}:"
fi
- printf " ${STRING}" "${@}"
+ if [ "${_L10N}" = "false" ]
+ then
+ printf " ${STRING}" "${@}"
+ else
+ printf " $(eval_gettext "${STRING}")" "${@}";
+ fi
if [ "${_COLOR}" = "false" ]
then
@@ -110,7 +140,12 @@ Echo_verbose ()
STRING="${1}"
shift
- printf "I: ${STRING}\n" "${@}"
+ if [ "${_L10N}" = "false" ]
+ then
+ printf "I: ${STRING}\n" "${@}"
+ else
+ printf "I: $(eval_gettext "${STRING}")" "${@}"; echo;
+ fi
fi
}
@@ -121,7 +156,12 @@ Echo_verbose_running ()
STRING="${1}"
shift
- printf "I: ${STRING}" "${@}"
+ if [ "${_L10N}" = "false" ]
+ then
+ printf "I: ${STRING}" "${@}"
+ else
+ printf "I: $(eval_gettext "${STRING}")" "${@}";
+ fi
if [ "${_COLOR}" = "false" ]
then
@@ -144,7 +184,12 @@ Echo_warning ()
printf "${YELLOW}W${NO_COLOR}:"
fi
- printf " ${STRING}\n" "${@}"
+ if [ "${_L10N}" = "false" ]
+ then
+ printf " ${STRING}\n" "${@}"
+ else
+ printf " $(eval_gettext "${STRING}")" "${@}"; echo;
+ fi
}
Echo_status ()
diff --git a/functions/exit.sh b/functions/exit.sh
index b6f2e2bfe..5fa1fa86f 100755
--- a/functions/exit.sh
+++ b/functions/exit.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
@@ -15,7 +15,7 @@ Exit ()
if [ "${_DEBUG}" = "true" ]
then
# Dump variables
- set | grep -e ^LB
+ set | grep -e ^LH
fi
# Always exit true in case we are not able to unmount
diff --git a/functions/help.sh b/functions/help.sh
index f5a56df9a..86f7782ac 100755
--- a/functions/help.sh
+++ b/functions/help.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/l10n.sh b/functions/l10n.sh
new file mode 100755
index 000000000..d32106b69
--- /dev/null
+++ b/functions/l10n.sh
@@ -0,0 +1,27 @@
+#!/bin/sh
+
+## live-build(7) - System Build Scripts
+## Copyright (C) 2006-2010 Daniel Baumann
+##
+## live-build 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.
+
+
+if [ -x "$(which gettext.sh 2>/dev/null)" ] && Find_files /usr/share/locale/*/LC_MESSAGES/${PACKAGE}.mo
+then
+ _L10N="true"
+
+ # gettext domain (.mo file name)
+ TEXTDOMAIN="${PACKAGE}"
+ export TEXTDOMAIN
+
+ # locale dir for gettext codes
+ TEXTDOMAINDIR="/usr/share/locale"
+ export TEXTDOMAINDIR
+
+ # load gettext functions
+ . gettext.sh
+else
+ _L10N="false"
+fi
diff --git a/functions/lockfile.sh b/functions/lockfile.sh
index b3a0ab640..ea551743f 100755
--- a/functions/lockfile.sh
+++ b/functions/lockfile.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/losetup.sh b/functions/losetup.sh
index df7e2d27f..fa6cd8373 100755
--- a/functions/losetup.sh
+++ b/functions/losetup.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/man.sh b/functions/man.sh
index 1551ab266..672ed7bc3 100755
--- a/functions/man.sh
+++ b/functions/man.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
@@ -12,7 +12,7 @@ Man ()
{
if [ -x "$(which man 2>/dev/null)" ]
then
- man $(basename ${0})
+ man lh_$(basename ${0})
exit 0
fi
}
diff --git a/functions/packages.sh b/functions/packages.sh
index 5df87cc91..20d53df61 100755
--- a/functions/packages.sh
+++ b/functions/packages.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/packageslists.sh b/functions/packageslists.sh
index 1d6c68142..94f016fbf 100755
--- a/functions/packageslists.sh
+++ b/functions/packageslists.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/releases.sh b/functions/releases.sh
index 07894f487..cb5fca77f 100755
--- a/functions/releases.sh
+++ b/functions/releases.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
@@ -22,4 +22,3 @@ RELEASE_jaunty="9.04"
RELEASE_karmic="9.10"
RELEASE_lucid="10.04" # LTS
RELEASE_maverick="10.10"
-RELEASE_natty="11.04"
diff --git a/functions/stagefile.sh b/functions/stagefile.sh
index b3b4dd9d6..504b6234a 100755
--- a/functions/stagefile.sh
+++ b/functions/stagefile.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/templates.sh b/functions/templates.sh
index 65125c09e..d365ccda2 100755
--- a/functions/templates.sh
+++ b/functions/templates.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/usage.sh b/functions/usage.sh
index bc9b2544d..ef82babee 100755
--- a/functions/usage.sh
+++ b/functions/usage.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/functions/version.sh b/functions/version.sh
index 581ac5631..9c1fcbf18 100755
--- a/functions/version.sh
+++ b/functions/version.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
@@ -13,7 +13,7 @@ Version ()
Echo "%s, version %s" "${PROGRAM}" "${VERSION}"
Echo "This program is a part of %s" "${PACKAGE}"
echo
- Echo "Copyright (C) 2006-2011 Daniel Baumann "
+ Echo "Copyright (C) 2006-2010 Daniel Baumann "
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"
diff --git a/functions/wrapper.sh b/functions/wrapper.sh
index dbcba8256..3b8a67232 100755
--- a/functions/wrapper.sh
+++ b/functions/wrapper.sh
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/hooks/debian-live-pxe-server b/hooks/debian-live-pxe-server
index 4bde28bcb..565ead59f 100755
--- a/hooks/debian-live-pxe-server
+++ b/hooks/debian-live-pxe-server
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/hooks/minimal b/hooks/minimal
index 65af09495..a33c006d1 100755
--- a/hooks/minimal
+++ b/hooks/minimal
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
diff --git a/hooks/stripped b/hooks/stripped
index 380141be1..ac895da45 100755
--- a/hooks/stripped
+++ b/hooks/stripped
@@ -1,7 +1,7 @@
#!/bin/sh
## live-build(7) - System Build Scripts
-## Copyright (C) 2006-2011 Daniel Baumann
+## Copyright (C) 2006-2010 Daniel Baumann
##
## live-build comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
## This is free software, and you are welcome to redistribute it
@@ -10,15 +10,6 @@
set -e
-# WARNING: Using this hook will result in a stripped system, means,
-# it may very well be possible that other packages are depending
-# on certain files that get removed here.
-# Therefore, this hooks is merely an inspiration for what could be
-# removed and not a generic nor recommendet solution to get the
-# image filesize down. In any event, using this hook can lead to
-# unforseen bugs and breakages in other packages and you should
-# be prepared to find and fix it for your own images.
-
# Removing unused packages
for PACKAGE in apt-utils aptitude man-db manpages info wget dselect
do
diff --git a/includes/lenny/common/doc/00-INDEX b/includes/lenny/common/doc/00-INDEX
deleted file mode 100644
index 85b5927f2..000000000
--- a/includes/lenny/common/doc/00-INDEX
+++ /dev/null
@@ -1,23 +0,0 @@
-What's in /debian/doc?
-
-dedication/ Dedications of Debian Releases
-
---- 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
-
-
---- The Bug Tracking System for users
-bug-reporting.txt How to report a bug in Debian
-bug-log-mailserver.txt Introduction to the bug system request server
-bug-log-access.txt Accessing bug reports in the tracking system
-bug-mailserver-refcard.txt Mail server's reference card
-
-
---- Debian Developer's Information
-bug-maint-info.txt Developer's information re the bug system
-bug-maint-mailcontrol.txt Introduction to the bug control mailserver
diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.html.tar.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.html.tar.gz
deleted file mode 100644
index abee0f971..000000000
Binary files a/includes/lenny/common/doc/FAQ/debian-faq.en.html.tar.gz and /dev/null differ
diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz
deleted file mode 100644
index 3b428a113..000000000
Binary files a/includes/lenny/common/doc/FAQ/debian-faq.en.pdf.gz and /dev/null differ
diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz
deleted file mode 100644
index 0ff09491e..000000000
Binary files a/includes/lenny/common/doc/FAQ/debian-faq.en.ps.gz and /dev/null differ
diff --git a/includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz b/includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz
deleted file mode 100644
index aeaaa4122..000000000
Binary files a/includes/lenny/common/doc/FAQ/debian-faq.en.txt.gz and /dev/null differ
diff --git a/includes/lenny/common/doc/FAQ/html/ch-basic_defs.en.html b/includes/lenny/common/doc/FAQ/html/ch-basic_defs.en.html
deleted file mode 100644
index cc5565314..000000000
--- a/includes/lenny/common/doc/FAQ/html/ch-basic_defs.en.html
+++ /dev/null
@@ -1,610 +0,0 @@
-
-
-
-
-
-
-
-
-The Debian GNU/Linux FAQ - Definitions and overview
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-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.
-
-Debian GNU/Linux is a particular distribution of the Linux operating
-system, and numerous packages that run on it.
-
-
-
-Debian GNU/Linux is:
-
-
-
-
-full featured: Debian includes more than 18200 software
-packages at present. Users can select which packages to install; Debian
-provides a tool for this purpose. You can find a list and descriptions of the
-packages currently available in Debian at any of the Debian 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 560 software packages (in the
-non-free and contrib sections), which are
-distributable under specific terms included with each package.
-
-
-
-
-
-
-dynamic: With about 1060 volunteers constantly contributing
-new and improved code, Debian is evolving rapidly. The FTP archives are
-updated twice every day.
-
-
-
-
-
-Most Linux users run a specific distribution of Linux, like Debian
-GNU/Linux. However, in principle, users could obtain the Linux kernel via the
-Internet or from elsewhere, and compile it themselves. They could then obtain
-source code for many applications in the same way, compile the programs, then
-install them into their systems. For complicated programs, this process can be
-not only time-consuming but error-prone. To avoid it, users often choose to
-obtain the operating system and the application packages from one of the Linux
-distributors. What distinguishes the various Linux distributors are the
-software, protocols, and practices they use for packaging, installing, and
-tracking applications packages on users' systems, combined with installation
-and maintenance tools, documentation, and other services.
-
-
-
-Debian GNU/Linux is the result of a volunteer effort to create a free,
-high-quality Unix-compatible operating system, complete with a suite of
-applications. The idea of a free Unix-like system originates from the GNU
-project, and many of the applications that make Debian GNU/Linux so useful were
-developed by the GNU project.
-
-
-
-For Debian, free has the GNUish meaning (see the Debian Free Software
-Guidelines). When we speak of free software, we are referring to
-freedom, not price. Free software means that you have the freedom to
-distribute copies of free software, that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it in new
-free programs; and that you know you can do these things.
-
-
-
-The Debian Project was created by Ian Murdock in 1993, initially under the
-sponsorship of the Free Software Foundation's GNU project. Today, Debian's
-developers think of it as a direct descendent of the GNU project.
-
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:
-
-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.
-
1.5 What is the difference between Debian GNU/Linux and other Linux distributions? Why should I choose Debian over some other distribution?
-
-
-These key features distinguish Debian from other Linux distributions:
-
-
-
Freedom:
-
-
-As stated in the Debian
-Social Contract, Debian will remain 100% free. Debian is very
-strict about shipping truly free software. The guidelines used to determine if
-a work is "free" are provided in The Debian Free
-Software.
-
-
-
-
-
The Debian package maintenance system:
-
-
-The entire system, or any individual component of it, can be upgraded in place
-without reformatting, without losing custom configuration files, and (in most
-cases) without rebooting the system. Most Linux distributions available today
-have some kind of package maintenance system; the Debian package maintenance
-system is unique and particularly robust (see Basics of the Debian package management system,
-Chapter 7).
-
-
-
-
-
Open development:
-
-
-Whereas other Linux distributions are developed by individuals, small, closed
-groups, or commercial vendors, Debian is the only major Linux distribution that
-is being developed cooperatively by many individuals through the Internet, in
-the same spirit as Linux and other free software.
-
-
-
-More than 1060 volunteer package maintainers are working on over 18200 packages
-and improving Debian GNU/Linux. The Debian developers contribute to the
-project not by writing new applications (in most cases), but by packaging
-existing software according to the standards of the project, by communicating
-bug reports to upstream developers, and by providing user support. See also
-additional information on how to become a contributor in How can I become a Debian software
-developer?, Section 13.1.
-
-The geographical dispersion of the Debian developers required sophisticated
-tools and quick communication of bugs and bug-fixes to accelerate the
-development of the system. Users are encouraged to send bugs in a formal
-style, which are quickly accessible by WWW archives or via e-mail. See
-additional information in this FAQ on the management of the bug log in Are there logs of known bugs?, Section
-12.4.
-
-
-
-
-
The Debian Policy:
-
-
-Debian has an extensive specification of our standards of quality, the Debian
-Policy. This document defines the qualities and standards to which we hold
-Debian packages.
-
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.)
-
-The Debian GNU/Linux FAQ
- Chapter 3 - Choosing a Debian distribution
-
-
-
-
-
-There are many different Debian distributions. Choosing the proper Debian
-distribution is an important decission. This section covers some information
-useful for users that want to make the choice best suited for their system and
-also answers possible questions that might be arising during the process. It
-does not deal with "why you should choose Debian" but rather
-"which distribution of Debian".
-
3.1 Which Debian distribution (stable/testing/unstable) is better for me?
-
-
-The answer is a bit complicated. It really depends on what you intend to do.
-One solution would be to ask a friend who runs Debian. But that does not mean
-that you cannot make an independent decision. In fact, you should be able to
-decide once you complete reading this chapter.
-
-
-
-
-If security or stability are at all important for you: install stable. period.
-This is the most preferred way.
-
-
-
-
-
-
-If you are a new user installing to a desktop machine, start with stable. Some
-of the software is quite old, but it's the least buggy environment to work in.
-You can easily switch to the more modern unstable once you are a little more
-confident.
-
-
-
-
-
-
-If you are a desktop user with some experience in Linux and does not mind
-facing the odd bug now and then, use unstable. It has all the latest and
-greatest software, and bugs are usually fixed swiftly.
-
-
-
-
-
-
-If you are running a server, especially one that has strong stability
-requirements or is exposed to the Internet, install stable. This is by far the
-strongest and safest choice.
-
-
-
-
-
-The following questions (hopefully) provide more detail on these choices.
-After reading this whole FAQ, if you still could not make a decision, stick
-with the stable distribution.
-
-
-
-
-
3.1.1 You asked me to install stable, but in stable so and so hardware is not detected/working. What should I do?
-
-
-Try to search the web using a search engine and see if someone else is able to
-get it working in stable. Most of the hardware should work fine with stable.
-But if you have some state-of-the-art, cutting edge hardware, it might not work
-with stable. If this is the case, you might want to install/upgrade to
-unstable.
-
-
-
-For laptops, http://www.linux-on-laptops.com/
-is a very good website to see if someone else is able to get it to work under
-Linux. The website is not specific to Debian, but is nevertheless a tremendous
-resource. I am not aware of any such website for desktops.
-
-
-
-Another option would be to ask in the debian-user mailing list by sending an
-email to debian-user@lists.debian.org . Messages can be posted to the list
-even without subscribing. The archives can be read through http://lists.debian.org/debian-user/
-Information regarding subscribing to the list can be found at the location of
-archives. You are strongly encourage to post your questions on the
-mailing-list than on irc. The mailing-list messages
-are archived, so solution to your problem can help others with the same issue.
-
-
-
-
-
3.1.2 Will there be different different versions of packages in different distributions?
-
-
-Yes. Unstable has the most recent (latest) versions. But the packages in
-unstable are not well tested and might have bugs.
-
-
-
-On the other hand, stable contains old versions of packages. But this package
-is well tested and is less likely to have any bugs.
-
-
-
-The packages in testing fall between these two extremes.
-
-
-
-
-
3.1.3 The stable distributions really contains outdated packages. Just look at Kde, Gnome, Xorg or even the kernel. They are very old. Why is it so?
-
-
-Well, you might be correct. The age of the packages at stable depends on when
-the last release was made. Since there is typically over 1 year between
-releases you might find that stable contains old versions of packages.
-However, they have been tested in and out. One can confidently say that the
-packages do not have any known severe bugs, security holes etc., in them. The
-packages in stable integrate seamlessly with other stable packages. These
-characteristics are very important for production servers which have to work 24
-hours a day, 7 days a week.
-
-
-
-On the other hand, packages in testing or unstable can have hidden bugs,
-security holes etc., Moreover, some packages in testing and unstable might not
-be working as intended. Usually people working on a single desktop prefer
-having the latest and most modern set of packages. Unstable is the solution
-for this group of people.
-
-
-
-As you can see, stability and novelty are two opposing ends of the spectrum.
-If stability is required: install stable distribution. If you want to work
-with the latest packages, then install unstable.
-
-
-
-
-
3.1.4 If I were to decide to change to another distribution, Can I do that?
-
-
-Yes, but it is a one way process. You can go from stable --> testing -->
-unstable. But the reverse direction is not "possible". So better be
-sure if you are planning to install/upgrade to unstable.
-
-
-
-Actually, if you are an expert and if you are willing to spend some time and if
-you are real careful and if you know what you are doing, then it might be
-possible to go from unstable to testing and then to stable. The installer
-scripts are not designed to do that. So in the process, your configuration
-files might be lost and....
-
-
-
-
-
3.1.5 Could you tell me whether to install testing or unstable?
-
-
-This is a rather subjective issue. There is no perfect answer but only a
-"wise guess" could be made while deciding between unstable and
-testing. My personal order of preference is Stable, Unstable and Testing. The
-issue is like this:
-
-
-
-
-Stable is rock solid. It does not break.
-
-
-
-
-
-
-Testing breaks less often than Unstable. But when it breaks, it takes a long
-time for things to get rectified. Sometimes this could be days and it could be
-months at times.
-
-
-
-
-
-
-Unstable changes a lot, and it can break at any point. However, fixes get
-rectified in many occasions in a couple of days and it always has the latest
-releases of software packaged for Debian.
-
-
-
-
-
-But there are times when tracking testing would be beneficial as opposed to
-unstable. The author such situation due to the gcc transition from gcc3 to
-gcc4. He was trying to install the labplot package on a machine
-tracking unstable and it could not be installed in unstable as some of its
-dependencies have undergone gcc4 transition and some have not. But the package
-in testing was installable on a testing machine as the gcc4 transitioned
-packages had not "trickled down" to testing.
-
-
-
-
-
3.1.6 You are talking about testing being broken. What do you mean by that?
-
-
-Sometimes, a package might not be installable through package management tools.
-Sometimes, a package might not be available at all, maybe it was (temporarily)
-removed due to bugs or unmet dependencies. Sometimes, a package installs but
-does not behave in the proper way.
-
-
-
-When these things happen, the distribution is said to be broken (at least for
-this package).
-
-
-
-
-
3.1.7 Why is it that testing could be broken for months? Wont the fixes introduced in unstable flow directly down into testing?
-
-
-The bug fixes and improvements introduced in the unstable distribution trickle
-down to testing after a certain number of days. Let's say this threshold is 10
-days. The packages in unstable go into testing only when there are no RC-bugs
-reported against them. If there is a RC-bug filed against a package in
-unstable, it will not go into testing after the 10 days.
-
-
-
-The idea is that, if the package has any problems, it would be discovered by
-people using unstable and will be fixed before it enters testing. This keeps
-the testing in an usable state for most period of the time. Overall a
-brilliant concept, if you ask me. But things are alwasy not so simple.
-Consider the following situation:
-
-
-
-
-Imagine you are interested in package XYZ.
-
-
-
-
-
-
-Let's assume that on June 10, the version in testing is XYZ-3.6 and in unstable
-it is XYZ-3.7
-
-
-
-
-
-
-After 10 days, XYZ-3.7 from unstable migrates into testing.
-
-
-
-
-
-
-So on June 20, both testing and unstable have XYZ-3.7 in their repositories.
-
-
-
-
-
-
-Let's say, The user of testing distribution sees that a new XYZ package is
-available and updates his XYZ-3.6 to XYZ-3.7
-
-
-
-
-
-
-Now on June 25, someone using testing or unstable discovers an RC bug in
-XYZ-3.7 and files it in the BTS.
-
-
-
-
-
-
-The maintainer of XYZ fixes this bug and uploads it to unstable say on June 30.
-Here it is assumed that it takes 5 days for the maintainer to fix the bug and
-upload the new version. The number 5 should not be taken literally. It could
-be less or more, depending upon the severity of the RC-bug at hand.
-
-
-
-
-
-
-This new version in unstable, XYZ-3.8 is scheduled to enter testing on July
-10th.
-
-
-
-
-
-
-But on July 5th some other person, discovers another RC-bug in XYZ-3.8
-
-
-
-
-
-
-Let's say the maintainer of XYZ fixes this new RC-bug and uploads new version
-of XYZ after 5 days.
-
-
-
-
-
-
-So on July 10, testing has XYZ-3.7 while unstable has XYZ-3.9
-
-
-
-
-
-
-This new version XYZ-3.9 is now rescheduled to enter testing on July 20th.
-
-
-
-
-
-
-Now since you are running testing, and since XYZ-3.7 is buggy, you could
-probably use XYZ only after July 20th. That is you essentially ended up with a
-broken XYZ for about one month.
-
-
-
-
-
-The situation can get much more complicated, if say, XYZ depends on 4 other
-packages. This could in turn lead to unusable testing distribution for months.
-The above scenario which is artificially created by me, can occur in the real
-life. But such occurrences are rare.
-
-
-
-
-
3.1.8 From an administrator's point of view, Which distribution requires more attention?
-
-
-One of the main reasons many people chose Debian over other Linux distributions
-is that it requires very little administration. People want a system that just
-works. In general one can say that, stable requires very little maintenance
-while testing and unstable require constant maintenance from the administrator.
-If you are running stable, all you need to worry about is, keeping track of
-security updates. If you are running either testing or unstable it is a good
-idea to be aware of the new bugs discovered in the installed packages, new
-bugfixes/features introduced etc.
-
-
-
-
-
3.1.9 What happens when a new release is made?
-
-
-This question will not help you in choosing a Debian distribution. But sooner
-or later you will face this question.
-
-
-
-The stable distribution is currently etch; The next stable distribution will be
-called as lenny. Let's consider the particular case as to what happens when
-lenny is released as the new stable version.
-
-Unstable is always referred to as sid irrespective of whether a release is made
-or not.
-
-
-
-
-
-
-packages constantly migrate from sid to testing (i.e. lenny). But packages in
-stable (i.e. etch) remain the same except for security updates.
-
-
-
-
-
-
-after sometime testing becomes frozen. But it will still be called testing.
-At this point no new packages from unstable can migrate to testing unless they
-include release-critical (RC) bug fixes.
-
-
-
-
-
-
-When testing is frozen, all the new bugfixes introduced, have to be manualy
-checked by the members of the release team. This is done to ensure that there
-wont be any unknown severe problems in the frozen testing.
-
-
-
-
-
-
-RC bugs in 'frozen testing' are reduced to zero.
-
-
-
-
-
-
-The 'frozen testing' with no rc-bugs will be released as the new stable
-version. In our example, this new stable release will be called as lenny.
-
-
-
-
-
-
-At this stage oldstable = etch, stable = lenny. The contents of stable and
-'frozen testing' are same at this point.
-
-
-
-
-
-
-A new testing is forked from the current stable.
-
-
-
-
-
-
-Packages start coming down from sid to testing and the Debian community will be
-working towards making the next stable release.
-
-
-
-
-
-
-
3.1.10 I have a working Desktop/cluster with Debian installed. How do I know which distribution I am running?
-
-
-In most situations it is very easy to figure this out. Take a look at the
-/etc/apt/sources.list file. There will be an entry similar to
-this:
-
-
-
- deb http://ftp.us.debian.org/debian/ unstable main contrib
-
-
-
-The third field ('unstable' in the above example) indicates the Debian
-distribution the system is currently tracking.
-
-
-
-You can also use lsb_release (available in the
-lsb-release package). If you run this program in an unstable
-system you will get:
-
-However, this is always not that easy. Some systems might have
-sources.list files with multiple entries corresponding to
-different distributions. This could happen if the administrator is tracking
-different packages from different Debian distributions. This is frequently
-referred to as apt-pinning. These systems might run a mixture of
-distributions.
-
-
-
-
-
3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?
-
-
-If you are currently running stable, then in the
-/etc/apt/sources.list file the third field will be either etch or
-stable. You need to change this to the distribution you want to run. If you
-want to run testing, then change the third field of
-/etc/apt/sources.list to testing. If you want to run unstable,
-then change the third field to unstable.
-
-
-
-Currently testing is called lenny. So, if you change the third field of
-/etc/apt/sources.list to lenny, then also you will be running
-testing. But when lenny becomes stable, you will still be tracking lenny.
-
-
-
-Unstable is always called Sid. So if you change the third field of
-/etc/apt/sources.list to sid, then you will be tracking unstable.
-
-
-
-Currently Debian offers security updates for testing but not for unstable, as
-fixes in unstable are directly made to the main archive. So if you are running
-unstable make sure that you remove the lines relating to security updates in
-/etc/apt/sources.list.
-
-
-
-If there is a release notes document available for the distribution you are
-upgrading to (even though it has not yet been released) it would be wise to
-review it, as it might provide information on how you should upgrade to it.
-
-
-
-Nevertheless, once you make the above changes, you can run aptitude
-update and then install the packages that you want. Notice that
-installing a package from a different distribution might automatically upgrade
-half of your system. If you install individual packages you will end up with a
-system running mixed distributions.
-
-
-
-It might be best in some situations to just fully upgrade to the new
-distribution running apt-get dist-upgrade, aptitude
-safe-upgrade or aptitude full-upgrade. Read apt's and
-aptitude's manual pages for more information.
-
-
-
-
-
3.1.12 I am currently tracking testing (lenny). What will happen when a release is made? Will I still be tracking testing or will my machine be running the new stable distribution?
-
-
-It depends on the entries in the /etc/apt/sources.list file. If
-you are currently tracking testing, these entries are similar to either:
-
-
-
- deb http://ftp.us.debian.org/debian/ testing main
-
-
-
-or
-
-
-
- deb http://ftp.us.debian.org/debian/ lenny main
-
-
-
-If the third field in /etc/apt/sources.list is 'testing' then you
-will be tracking testing even after a release is made. So after lenny is
-released, you will be running a new Debian distribution which will have a
-different codename. Changes might not be apparent at first but will be evident
-as soon as new packages from unstable go over to the testing distribution.
-
-
-
-But if the third field contains 'lenny' then you will be tracking stable (since
-lenny will then be the new stable distribution).
-
-
-
-
-
3.1.13 I am still confused. What did you say I should install?
-
-
-If unsure, the best bet would be stable distribution.
-
-
-
-
-
3.2 But what about Knoppix, Linex, Ubuntu, and others?
-
-
-They are not Debian; they are Debian based. Though there are many
-similarities and commonalities between them, there are also crucial
-differences.
-
-
-
-All these distributions have their own merits and are suited to some specific
-set of users. For more information, read the information of software distributions based
-on Debian available at the Debian website.
-
-
-
-
-
3.2.1 I know that Knoppix/Linex/Ubuntu/... is Debian-based. So after installing it on the hard disk, can I use 'apt' package tools on it?
-
-
-These distributions are Debian based. But they are not Debian. You will be
-still able to use apt package tools by pointing the
-/etc/apt/sources.list file to these distributions' repositories.
-But then you are not running Debian, you are running a different distribution.
-They are not the same.
-
-
-
-In most situations if you stick with one distribution you should use that and
-not mix packages from other distributions. Many common breakages arise due to
-people running a distribution and trying to install Debian packages from other
-distributions. The fact that they use the same formatting and name (.deb) does
-not make them inmediately compatible.
-
-
-
-For example, Knoppix is a Linux distribution designed to be booted as a live CD
-where as Debian is designed to be installed on hard-disk. Knoppix is great if
-you want to know whether a particular hardware works, or if you want to
-experience how a linux system 'feels' etc., Knoppix is good for demonstration
-purposes while Debian is designed to run 24/7. Moreover the number of packages
-available, the number of architectures supported by Debian are far more greater
-than that of Knoppix.
-
-
-
-If you want Debian, it is best to install Debian from the get-go. Although it
-is possible to install Debian through other distributions, such as Knoppix, the
-procedure calls for expertise. If you are reading this FAQ, I would assume
-that you are new to both Debian and Knoppix. In that case, save yourself a lot
-of trouble later and install Debian right at the beginning.
-
-
-
-
-
3.2.2 I installed Knoppix/Linex/Ubuntu/... on my hard disk. Now I have a problem. What should I do?
-
-
-You are advised not to use the Debian forums (either mailing lists or IRC) for
-help as people might advise you thinking that you are running a Debian system
-and the "fixes" they provide might not be suited to what you are
-running. They might even worsen the problem you are facing.
-
-
-
-Use the forums of the specific distribution you are using first. If you do not
-get help or the help you get does not fix your problem you might want to try
-asking in Debian forums, but keep the advise of the previous paragraph in mind.
-
-
-
-
-
3.2.3 I'm using Knoppix/Linex/Ubuntu/... and now I want to use Debian. How do I migrate?
-
-
-Consider the change from a Debian-based distribution to Debian just like a
-change from one operating system to another one. You should make a backup of
-all your date and reinstall the operating system from scratch. You should not
-attempt to "upgrade" to Debian using the package management tools as
-you might end up with an unusable system.
-
-
-
-If all your user data (i.e. your /home) is under a separate
-partition migrating to Debian is actually quite simple, you just have to tell
-the installation system to mount (but not reformat) that partition when
-reinstalling. Making backups of your data, as well as your previous system's
-configuration (i.e. /etc/ and, maybe, /var/) is
-still encouraged.
-
4.1 On what hardware architectures/systems does Debian GNU/Linux run?
-
-
-Debian GNU/Linux includes complete source-code for all of the included
-programs, so it should work on all systems which are supported by the Linux
-kernel; see the Linux
-FAQ for details.
-
-
-
-The current Debian GNU/Linux release, 4.0, contains a complete, binary
-distribution for the following architectures:
-
-
-
-i386: this covers systems based on Intel and compatible processors,
-including Intel's 386, 486, Pentium, Pentium Pro, Pentium II (both Klamath and
-Celeron), and Pentium III, and most compatible processors by AMD, Cyrix and
-others.
-
-
-
-amd64: this covers systems based on AMD 64bit CPUs with AMD64
-extension and all Intel CPUs with EM64T extension, and a common 64bit
-userspace.
-
-
-
-alpha: Compaq/Digital's Alpha systems.
-
-
-
-sparc: this covers Sun's SPARC and most UltraSPARC systems.
-
-
-
-powerpc: this covers some IBM/Motorola PowerPC machines, including
-CHRP, PowerMac and PReP machines.
-
-
-
-arm: ARM and StrongARM machines.
-
-
-
-mips: SGI's big-endian MIPS systems, Indy and Indigo2;
-mipsel: little-endian MIPS machines, Digital DECstations.
-
-The development of binary distributions of Debian for Sparc64 (UltraSPARC
-native) architectures is currently underway.
-
-
-
-Support for the m68k architecture was dropped in this release, because
-it did not meet the criteria set by the Debian Release Managers. This
-architecture covers Amigas and ATARIs having a Motorola 680x0 processor for
-x>=2; with MMU. However, the port is still active and available for
-installation even if not a part of this official stable release and might be
-reactivated for future releases.
-
-For further information on booting, partitioning your drive, enabling PCMCIA
-(PC Card) devices and similar issues please follow the instructions given in
-the Installation Manual, which is available from our WWW site at http://www.debian.org/releases/stable/installmanual.
-
-
-
-
-
4.2 How compatible is Debian with other distributions of Linux?
-
-
-Debian developers communicate with other Linux distribution creators in an
-effort to maintain binary compatibility across Linux distributions. Most
-commercial Linux products run as well under Debian as they do on the system
-upon which they were built.
-
-
-
-Debian GNU/Linux adheres to the Linux Filesystem Hierarchy
-Standard. However, there is room for interpretation in some of the
-rules within this standard, so there may be slight differences between a Debian
-system and other Linux systems.
-
-
-
-Debian GNU/Linux supports software developed for the Linux Standard Base. The LSB is a
-specification for allowing the same binary package to be used on multiple
-distributions. The Debian Etch release is Certified for LSB Release 3.1, see
-the Linux
-Foundation Certification webpage. Discussion and coordination of
-efforts towards ensuring Debian meets the requirements of the Linux Standard
-Base is taking place on the debian-lsb mailing list.
-
-
-
-
-
4.3 How source code compatible is Debian with other Unix systems?
-
-
-For most applications Linux source code is compatible with other Unix systems.
-It supports almost everything that is available in System V Unix systems and
-the free and commercial BSD-derived systems. However in the Unix business such
-claim has nearly no value because there is no way to prove it. In the software
-development area complete compatibility is required instead of compatibility in
-"about most" cases. So years ago the need for standards arose, and
-nowadays POSIX.1 (IEEE Standard 1003.1-1990) is one of the major standards for
-source code compatibility in Unix-like operating systems.
-
-
-
-Linux is intended to adhere to POSIX.1, but the POSIX standards cost real money
-and the POSIX.1 (and FIPS 151-2) certification is quite expensive; this made it
-more difficult for the Linux developers to work on complete POSIX conformance.
-The certification costs make it unlikely that Debian will get an official
-conformance certification even if it completely passed the validation suite.
-(The validation suite is now freely available, so it is expected that more
-people will work on POSIX.1 issues.)
-
-
-
-Unifix GmbH (Braunschweig, Germany) developed a Linux system that has been
-certified to conform to FIPS 151-2 (a superset of POSIX.1). This technology
-was available in Unifix' own distribution called Unifix Linux 2.0 and in
-Lasermoon's Linux-FT.
-
-
-
-
-
4.4 Can I use Debian packages (".deb" files) on my Red Hat/Slackware/... Linux system? Can I use Red Hat packages (".rpm" files) on my Debian GNU/Linux system?
-
-
-Different Linux distributions use different package formats and different
-package management programs.
-
-
-
You probably can:
-
-
-A program to unpack a Debian package onto a Linux host that is been built from
-a `foreign' distribution is available, and will generally work, in the sense
-that files will be unpacked. The converse is probably also true, that is, a
-program to unpack a Red Hat or Slackware package on a host that is based on
-Debian GNU/Linux will probably succeed in unpacking the package and placing
-most files in their intended directories. This is largely a consequence of the
-existence (and broad adherence to) the Linux Filesystem Hierarchy Standard.
-The Alien package
-is used to convert between different package formats.
-
-
-
-
-
You probably do not want to:
-
-
-Most package managers write administrative files when they are used to unpack
-an archive. These administrative files are generally not standardized.
-Therefore, the effect of unpacking a Debian package on a `foreign' host will
-have unpredictable (certainly not useful) effects on the package manager on
-that system. Likewise, utilities from other distributions might succeed in
-unpacking their archives on Debian systems, but will probably cause the Debian
-package management system to fail when the time comes to upgrade or remove some
-packages, or even simply to report exactly what packages are present on a
-system.
-
-
-
-
-
A better way:
-
-
-The Linux File System Standard (and therefore Debian GNU/Linux) requires that
-subdirectories under /usr/local/ be entirely under the user's
-discretion. Therefore, users can unpack `foreign' packages into this
-directory, and then manage their configuration, upgrade and removal
-individually.
-
-
-
-
-
-
-
4.5 How should I install a non-Debian program?
-
-
-Files under the directory /usr/local/ are not under the control of
-the Debian package management system. Therefore, it is good practice to place
-the source code for your program in /usr/local/src/. For example, you might
-extract the files for a package named "foo.tar" into the directory
-/usr/local/src/foo. After you compile them, place the binaries in
-/usr/local/bin/, the libraries in /usr/local/lib/,
-and the configuration files in /usr/local/etc/.
-
-
-
-If your programs and/or files really must be placed in some other directory,
-you could still store them in /usr/local/, and build the
-appropriate symbolic links from the required location to its location in
-/usr/local/, e.g., you could make the link
-
-
-
- ln -s /usr/local/bin/foo /usr/bin/foo
-
-
-
-In any case, if you obtain a package whose copyright allows redistribution, you
-should consider making a Debian package of it, and uploading it for the Debian
-system. Guidelines for becoming a package developer are included in the Debian
-Policy manual (see What other
-documentation exists on and for a Debian system?, Section 12.1).
-
-
-
-
-
4.6 Why can't I compile programs that require libtermcap?
-
-
-Debian uses the terminfo database and the ncurses
-library of terminal interface routes, rather than the termcap
-database and the termcap library. Users who are compiling
-programs that require some knowledge of the terminal interface should replace
-references to libtermcap with references to
-libncurses.
-
-
-
-To support binaries that have already been linked with the termcap
-library, and for which you do not have the source, Debian provides a package
-called termcap-compat. This provides both
-libtermcap.so.2 and /etc/termcap. Install this
-package if the program fails to run with the error message "can't load
-library 'libtermcap.so.2'", or complains about a missing
-/etc/termcap file.
-
4.8 Why do my old XFree 2.1 Motif applications crash?
-
-
-You need to install the motifnls package, which provides the
-XFree-2.1 configuration files needed to allow Motif applications compiled under
-XFree-2.1 to run under XFree-3.1.
-
-
-
-Without these files, some Motif applications compiled on other machines (such
-as Netscape) may crash when attempting to copy or paste from or to a text
-field, and may also exhibit other problems.
-
-The Debian GNU/Linux FAQ
- Chapter 13 - Contributing to the Debian Project
-
-
-
-
-
-Donations of time
-(to develop new packages, maintain existing packages, or provide user support),
-resources (to mirror the FTP and WWW archives), and money (to pay for new
-testbeds as well as hardware for the archives) can help the project.
-
-
-
-
-
13.1 How can I become a Debian software developer?
-
-
-The development of Debian is open to all, and new users with the right skills
-and/or the willingness to learn are needed to maintain existing packages which
-have been "orphaned" by their previous maintainers, to develop new
-packages, and to provide user support.
-
-
-
-The description of becoming a Debian developer can be found at the New Maintainer's
-Corner at the Debian web site.
-
-
-
-
-
13.2 How can I contribute resources to the Debian project?
-
-
-Since the project aims to make a substantial body of software rapidly and
-easily accessible throughout the globe, mirrors are urgently needed. It is
-desirable but not absolutely necessary to mirror all of the archive. Please
-visit the Debian mirror
-size page for information on the disk space requirements.
-
-
-
-Most of the mirroring is accomplished entirely automatically by scripts,
-without any interaction. However, the occasional glitch or system change
-occurs which requires human intervention.
-
-
-
-If you have a high-speed connection to the Internet, the resources to mirror
-all or part of the distribution, and are willing to take the time (or find
-someone) who can provide regular maintenance of the system, then please contact
-debian-admin@lists.debian.org.
-
-
-
-
-
13.3 How can I contribute financially to the Debian project?
-
-
-One can make individual donations to one of two organizations that are critical
-to the development of the Debian project.
-
-
-
-
-
13.3.1 Software in the Public Interest
-
-
-Software in the Public Interest (SPI) is an IRS 501(c)(3) non-profit
-organization, formed when FSF withdrew their sponsorship of Debian. The
-purpose of the organization is to develop and distribute free software.
-
-
-
-Our goals are very much like those of FSF, and we encourage programmers to use
-the GNU General Public License on their programs. However, we have a slightly
-different focus in that we are building and distributing a Linux system that
-diverges in many technical details from the GNU system as originally planned by
-FSF. We still communicate with FSF, and we cooperate in sending them changes
-to GNU software and in asking our users to donate to FSF and the GNU project.
-
-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.
-
-The Debian GNU/Linux FAQ
- Chapter 11 - Customizing your installation of Debian GNU/Linux
-
-
-
-
-
11.1 How can I ensure that all programs use the same paper size?
-
-
-Install the libpaper1 package, and it will ask you for a
-system-wide default paper size. This setting will be kept in the file
-/etc/papersize.
-
-
-
-Users can override the paper size setting using the PAPERSIZE
-environment variable. For details, see the manual page
-papersize(5).
-
-
-
-
-
11.2 How can I provide access to hardware peripherals, without compromising security?
-
-
-Many device files in the /dev directory belong to some predefined
-groups. For example, /dev/fd0 belongs to the floppy
-group, and /dev/dsp belongs to the audio group.
-
-
-
-If you want a certain user to have access to one of these devices, just add the
-user to the group the device belongs to, i.e. do:
-
-
-
- adduser user group
-
-
-
-This way you won't have to change the file permissions on the device.
-
-
-
-If you do this from within a user's shell or a GUI environment you have to
-logout and login again to become an effective member of that group. To check
-which groups you belong to run groups.
-
-
-
-Notice that, since the introduction of udev if you change the
-permissions of a hardware peripheral they might be be adjusted for some devices
-when the system starts, if this happens to the hardware peripherals you are
-instered in you will have to adjust the rules at /etc/udev.
-
-
-
-
-
11.3 How do I load a console font on startup the Debian way?
-
-
-The kbd and console-tools packages support this, edit
-/etc/kbd/config or /etc/console-tools/config files.
-
-
-
-
-
11.4 How can I configure an X11 program's application defaults?
-
-
-Debian's X programs will install their application resource data in the
-/etc/X11/app-defaults/ directory. If you want to customize X
-applications globally, put your customizations in those files. They are marked
-as configuration files, so their contents will be preserved during upgrades.
-
-
-
-
-
11.5 Every distribution seems to have a different boot-up method. Tell me about Debian's.
-
-
-Like all Unices, Debian boots up by executing the program init.
-The configuration file for init (which is
-/etc/inittab) specifies that the first script to be executed
-should be /etc/init.d/rcS. This script runs all of the scripts in
-/etc/rcS.d/ by sourcing or forking subprocess depending on their
-file extension to perform initialization such as to check and to mount file
-systems, to load modules, to start the network services, to set the clock, and
-to perform other initialization. Then, for compatibility, it runs the files
-(except those with a `.'in the filename) in /etc/rc.boot/ too.
-Any scripts in the latter directory are usually reserved for system
-administrator use, and using them in packages is deprecated.
-
-
-
-After completing the boot process, init executes all start scripts
-in a directory specified by the default runlevel (this runlevel is given by the
-entry for id in /etc/inittab). Like most System V
-compatible Unices, Linux has 7 runlevels:
-
-
-
-
-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/.)
-
-
-
-
-
11.6 It looks as if Debian does not use rc.local to customize the boot process; what facilities are provided?
-
-
-Suppose a system needs to execute script foo on start-up, or on
-entry to a particular (System V) runlevel. Then the system administrator
-should:
-
-
-
-
-Enter the script foo into the directory /etc/init.d/.
-
-
-
-
-
-
-Run the Debian command update-rc.d with appropriate arguments, to
-specify which runlevels should start the service, and which runlevels should
-stop the service.
-
-
-
-
-
-
-Consider rebooting the system to check that the service starts correctly
-(assuming that you've asked for it to be started in the default runlevel).
-Otherwise, manually start it by running `/etc/init.d/foo start'.
-
-
-
-
-
-One might, for example, cause the script foo to execute at
-boot-up, by putting it in /etc/init.d/ and running
-update-rc.d foo defaults 19. The argument `defaults'
-refers to the default runlevels, which means (at least in absence of any LSB
-comment block to the contrary) to start the service in runlevels 2 through 5,
-and to stop the service in runlevels 0, 1 and 6. (Any LSB Default-Start and
-Default-Stop directives in foo take precedence when using the
-sysv-rc version of update-rc.d, but are ignored by the current (v0.8.10)
-file-rc version of update-rc.d.) The argument `19' ensures that
-foo is called after all scripts whose number is less than 19 have
-completed, and before all scripts whose number is 20 or greater.
-
-
-
-
-
11.7 How does the package management system deal with packages that contain configuration files for other packages?
-
-
-Some users wish to create, for example, a new server by installing a group of
-Debian packages and a locally generated package consisting of configuration
-files. This is not generally a good idea, because dpkg will not
-know about those configuration files if they are in a different package, and
-may write conflicting configurations when one of the initial "group"
-of packages is upgraded.
-
-
-
-Instead, create a local package that modifies the configuration files of the
-"group" of Debian packages of interest. Then dpkg and
-the rest of the package management system will see that the files have been
-modified by the local "sysadmin" and will not try to overwrite them
-when those packages are upgraded.
-
-
-
-
-
11.8 How do I override a file installed by a package, so that a different version can be used instead?
-
-
-Suppose a sysadmin or local user wishes to use a program
-"login-local" rather than the program "login" provided by
-the Debian login package.
-
-
-
-Do not:
-
-
-
-
-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.
-
-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.
-
-
-
-
-
11.10 Some users like mawk, others like gawk; some like vim, others like elvis; some like trn, others like tin; how does Debian support diversity?
-
-
-There are several cases where two packages provide two different versions of a
-program, both of which provide the same core functionality. Users might prefer
-one over another out of habit, or because the user interface of one package is
-somehow more pleasing than the interface of another. Other users on the same
-system might make a different choice.
-
-
-
-Debian uses a "virtual" package system to allow system administrators
-to choose (or let users choose) their favorite tools when there are two or more
-that provide the same basic functionality, yet satisfy package dependency
-requirements without specifying a particular package.
-
-
-
-For example, there might exist two different versions of newsreaders on a
-system. The news server package might 'recommend' that there exist
-some news reader on the system, but the choice of tin or
-trn is left up to the individual user. This is satisfied by
-having both the tin and trn packages provide the
-virtual package news-reader. Which program is invoked is
-determined by a link pointing from a file with the virtual package name
-/etc/alternatives/news-reader to the selected file, e.g.,
-/usr/bin/trn.
-
-
-
-A single link is insufficient to support full use of an alternate program;
-normally, manual pages, and possibly other supporting files must be selected as
-well. The Perl script update-alternatives provides a way of
-ensuring that all the files associated with a specified package are selected as
-a system default.
-
-
-
-For example, to check what executables provide `x-window-manager', run:
-
-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:
-
-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:
-
-The Debian GNU/Linux FAQ
- Chapter 16 - General information about the FAQ
-
-
-
-
-
16.1 Authors
-
-
-The first edition of this FAQ was made and maintained by J.H.M. Dassen (Ray)
-and Chuck Stickelman. Authors of the rewritten Debian GNU/Linux FAQ are Susan
-G. Kleinmann and Sven Rudolph. After them, the FAQ was maintained by Santiago
-Vila and, later, by Josip Rodin. The current maintainer is Javier
-Fernandez-Sanguino.
-
-
-
-Parts of the information came from:
-
-
-
-
-The Debian-1.1 release announcement, by Bruce Perens.
-
-The authors would like to thank all those who helped make this document
-possible.
-
-
-
-All warranties are disclaimed. All trademarks are property of their respective
-trademark owners.
-
-
-
-
-
16.2 Feedback
-
-
-Comments and additions to this document are always welcome. Please send e-mail
-to doc-debian@packages.debian.org,
-or submit a wishlist bug report against the debian-faq package.
-
-It is also available for download in plain text, HTML, PostScript and PDF
-formats at http://www.debian.org/doc/user-manuals#faq.
-Also, there are several translations there.
-
-
-
-This document is available in the debian-faq package.
-Translations are available in debian-faq-de,
-debian-faq-fr and other packages.
-
-
-
-The original SGML files used to create this document are also available in
-debian-faq's source package, or in SVN at:
-svn://svn.debian.org/svn/ddp/manuals/trunk/debian-faq and http://svn.debian.org/viewsvn/ddp/manuals/trunk/debian-faq/.
-
-
-
-
-
16.4 Document format
-
-
-This document was written using the DebianDoc SGML DTD (rewritten from LinuxDoc
-SGML). DebianDoc SGML systems enables us to create files in a variety of
-formats from one source, e.g. this document can be viewed as HTML, plain text,
-TeX DVI, PostScript, PDF, or GNU info.
-
-
-
-Conversion utilities for DebianDoc SGML are available in Debian package
-debiandoc-sgml.
-
-There are three major distributions: the "stable" distribution, the
-"testing" distribution, and the "unstable" distribution.
-The "testing" distribution is sometimes `frozen' (see What about "testing"? How is it `frozen'?, Section
-6.5.1). Next to these, there is the "oldstable" distribution
-(that's just the one from before "stable"), and the
-"experimental" distribution.
-
-
-
-Experimental is used for packages which are still being developed, and with a
-high risk of breaking your system. It's used by developers who'd like to study
-and test bleeding edge software. Users shouldn't be using packages from here,
-because they can be dangerous and harmful even for the most experienced people.
-
6.2 What are all those names like etch, lenny, etc.?
-
-
-They are just "codenames". When a Debian distribution is in the
-development stage, it has no version number but a codename. The purpose of
-these codenames is to make easier the mirroring of the Debian distributions (if
-a real directory like unstable suddenly changed its name to
-stable, a lot of stuff would have to be needlessly downloaded
-again).
-
-
-
-Currently, stable is a symbolic link to etch (i.e.
-Debian GNU/Linux 4.0) and testing is a symbolic link to
-lenny. This means that etch is the current stable
-distribution and lenny is the current testing distribution.
-
-
-
-unstable is a permanent symbolic link to sid, as
-sid is always the unstable distribution (see What
-about "sid"?, Section 6.3).
-
-
-
-
-
6.2.1 Which other codenames have been used in the past?
-
-
-Other codenames that have been already used are: buzz for release
-1.1, rex for release 1.2, bo for releases 1.3.x,
-hamm for release 2.0, slink for release 2.1,
-potato for release 2.2, woody for release 3.0,
-sarge for release 3.1, and etch for release 4.0.
-
-
-
-
-
6.2.2 Where do these codenames come from?
-
-
-So far they have been characters taken from the movie "Toy Story" by
-Pixar.
-
-
-
-
-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)),
-
-
-
-
-
-
-lenny was the binoculars.
-
-
-
-
-
-
-sid was the boy next door who destroyed toys.
-
-
-
-
-
-
-
6.3 What about "sid"?
-
-
-sid or unstable is the place where most of the packages are
-initially uploaded. It will never be released directly, because packages which
-are to be released will first have to be included in testing, in order
-to be released in stable later on. sid contains packages for both
-released and unreleased architectures.
-
-
-
-The name "sid" also comes from the "Toy Story" animated
-motion picture: Sid was the boy next door who destroyed toys :-)
-
-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
-free software. The licenses of each of these packages must be studied, and
-possibly negotiated, before the packages are included in any redistribution
-(e.g., in a CD-ROM).
-
-
-
-
-
-
-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.
-
-
-
-
-
-
-
6.5 What does the testing distribution contain?
-
-
-Packages are installed into the `testing' directory after they have undergone
-some degree of testing in unstable.
-
-
-
-They must be in sync on all architectures where they have been built and
-mustn't have dependencies that make them uninstallable; they also have to have
-fewer release-critical bugs than the versions currently in testing. This way,
-we hope that `testing' is always close to being a release candidate.
-
-
-
-More information about the status of "testing" in general and the
-individual packages is available at http://www.debian.org/devel/testing.
-
-
-
-
-
6.5.1 What about "testing"? How is it `frozen'?
-
-
-When the "testing" distribution is mature enough, the release manager
-starts `freezing' it. The normal propagation delays are increased to ensure
-that as little as possible new bugs from "unstable" enter
-"testing".
-
-
-
-After a while, the "testing" distribution becomes truly `frozen'.
-This means that all new packages that are to propagate to the
-"testing" are held back, unless they include release-critical bug
-fixes. The "testing" distribution can also remain in such a deep
-freeze during the so-called `test cycles', when the release is imminent.
-
-
-
-We keep a record of bugs in the "testing" distribution that can hold
-off a package from being released, or bugs that can hold back the whole
-release. For details, please see current testing release
-information.
-
-
-
-Once that bug count lowers to maximum acceptable values, the frozen
-"testing" distribution is declared "stable" and released
-with a version number.
-
-
-
-With each new release, the previous "stable" distribution becomes
-obsolete and moves to the archive. For more information please see Debian archive.
-
-
-
-
-
6.6 What does the unstable distribution contain?
-
-
-The `unstable' directory contains a snapshot of the current development system.
-Users are welcome to use and test these packages, but are warned about their
-state of readiness. The advantage of using the unstable distribution is that
-you are always up-to-date with the latest in GNU/Linux software industry, but
-if it breaks: you get to keep both parts :-)
-
-
-
-There are also main, contrib and non-free subdirectories in `unstable',
-separated on the same criteria as in `stable'.
-
-
-
-
-
6.7 What are all those directories at the Debian FTP archives?
-
-
-The software that has been packaged for Debian GNU/Linux is available in one of
-several directory trees on each Debian mirror site.
-
-
-
-The dists directory is short for "distributions", and it
-is the canonical way to access the currently available Debian releases (and
-pre-releases).
-
-There are the following supplementary directories:
-
-
-
/tools/:
-
-
-DOS utilities for creating boot disks, partitioning your disk drive,
-compressing/decompressing files, and booting Linux.
-
-
-
-
-
/doc/:
-
-
-The basic Debian documentation, such as this FAQ, the bug reporting system
-instructions, etc.
-
-
-
-
-
/indices/:
-
-
-various indices of the site (the Maintainers file and the override files).
-
-
-
-
-
/project/:
-
-
-mostly developer-only materials and some miscellaneous files.
-
-
-
-
-
-
-
6.8 What are all those directories inside dists/stable/main?
-
-
-Within each of the major directory trees[3], there are three sets of subdirectories containing index
-files.
-
-
-
-There's one set of binary-something subdirectories
-which contain index files for binary packages of each available computer
-architecture, for example binary-i386 for packages which execute
-on Intel x86 PC machines or binary-sparc for packages which
-execute on Sun SPARCStations.
-
-The index files in binary-* are called Packages(.gz, .bz2) and they include a
-summary of each binary package that is included in that distribution. The
-actual binary packages reside in the top level pool directory.
-
-
-
-Furthermore, there's a subdirectory called source/ which contains index files
-for source packages included in the distribution. The index file is called
-Sources(.gz, .bz2).
-
-
-
-Last but not least, there's a set of subdirectories meant for the installation
-system index files, they are at
-debian-installer/binary-architecture.
-
-
-
-
-
6.9 Where is the source code?
-
-
-Source code is included for everything in the Debian system. Moreover, the
-license terms of most programs in the system require that source code
-be distributed along with the programs, or that an offer to provide the source
-code accompany the programs.
-
-
-
-The source code is distributed in the pool directory (see What's in the pool directory?, Section 6.10)
-together with all the architecture-specific binary directories. To retrieve
-the source code without having to be familiar with the structure of the FTP
-archive, try a command like apt-get source mypackagename.
-
-
-
-Some packages are only distributed as source code due to the restrictions in
-their licenses. Notably, one such package is pine, see Where is pine?, Section 5.10 for more
-information.
-
-
-
-Source code may or may not be available for packages in the "contrib"
-and "non-free" directories, which are not formally part of the Debian
-system.
-
-
-
-
-
6.10 What's in the pool directory?
-
-
-Packages are kept in a large `pool', structured according to the name of the
-source package. To make this manageable, the pool is subdivided by section
-(`main', `contrib' and `non-free') and by the first letter of the source
-package name. These directories contain several files: the binary packages for
-each architecture, and the source packages from which the binary packages were
-generated.
-
-
-
-You can find out where each package is placed by executing a command like
-apt-cache showsrc mypackagename and looking at the `Directory:'
-line. For example, the apache packages are stored in
-pool/main/a/apache/.
-
-
-
-Additionally, since there are so many lib* packages, these are
-treated specially: for instance, libpaper packages are stored in
-pool/main/libp/libpaper/.
-
-After a developer uploads a package, it stays for a short while in the
-"incoming" directory before it is checked that it's genuine and
-allowed into the archive.
-
-
-
-Usually nobody should install things from this place. However, in some rare
-cases of emergency, the incoming directory is available at http://incoming.debian.org/. You
-can manually fetch packages, check the GPG signature and MD5sums in the
-.changes and .dsc files, and then install them.
-
-
-
-
-
6.12 How do I set up my own apt-able repository?
-
-
-If you have built some private Debian packages which you'd like to install
-using the standard Debian package management tools, you can set up your own
-apt-able package archive. This is also useful if you'd like to share your
-Debian packages while these are not distributed by the Debian project.
-Instructions on how to do this are given in the Debian
-Repository HOWTO.
-
-The official document giving installation instructions is the Debian GNU/Linux
-Installation Guide. We'll give some additional notes about getting
-and installing Debian GNU/Linux here.
-
-
-
-
-
2.1 What is the latest version of Debian?
-
-
-Currently there are three versions of Debian GNU/Linux:
-
-
-
release 4.0, a.k.a. the `stable' distribution or etch
-
-
-This is stable and well tested software, it changes if major security or
-usability fixes are incorporated.
-
-
-
-
-
the `testing' distribution, currently called lenny
-
-
-This is where packages that will be released as the next `stable' are placed;
-they've had some testing in unstable but they may not be completely fit for
-release yet. This distribution is updated more often than `stable', but not
-more often than `unstable'.
-
-
-
-
-
the `unstable' distribution
-
-
-This is the version currently under development; it is updated continuously.
-You can retrieve packages from the `unstable' archive on any Debian FTP site
-and use them to upgrade your system at any time, but you may not expect the
-system to be as usable or as stable as before - that's why it's called
-`unstable'!
-
-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.
-
-Installing Debian from CD is straightforward: configure your system for booting
-off a CD, insert your CD, and reboot. Your system will now be running the
-Debian Installer. See the Debian GNU/Linux
-Installation Guide for more information.
-
-
-
-
-
2.5 Why does the official stable released CD-ROM contain symlinks for `frozen' and `unstable'? I thought this CD contains just `stable'!
-
-
-Official Debian CD images indeed contain symlinks like:
-
-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.
-
2.6 Can I get and install Debian directly from a remote Internet site?
-
-
-Yes. You can boot the Debian installation system from a set of files you can
-download from our FTP site and its mirrors.
-
-
-
-You can download a small CD image file, create a bootable CD from it, install
-the basic system from it and the rest over the network. For more information
-please see http://www.debian.org/CD/netinst/.
-
-
-
-You can also download even smaller floppy disk image files, create bootable
-diskettes from them, start the installation procedure and get the rest of
-Debian over the network.
-
-
-
-
-
2.7 Are there any alternative strategies for booting the system installer?
-
-
-Yes. Apart from CD or DVD, you can install Debian GNU/Linux by booting from
-floppy disks, USB memory stick, directly from hard disk, or using TFTP net
-booting. For installing on multiple computers it's possible to do fully
-automatic installations. NB: not all methods are supported by all computer
-architectures. Once the installer has booted, the rest of the system can be
-downloaded over the network, or installed from local media. See the Debian GNU/Linux
-Installation Guide for more information.
-
-The Debian GNU/Linux FAQ
- Chapter 10 - Debian and the kernel
-
-
-
-
-
10.1 Can I install and compile a kernel without some Debian-specific tweaking?
-
-
-Yes.
-
-
-
-There's only one common catch: the Debian C libraries are built with the most
-recent stable releases of the kernel headers. If you
-happen to need to compile a program with kernel headers newer than the ones
-from the stable branch, then you should either upgrade the package containing
-the headers (libc6-dev), or use the new headers from an unpacked
-tree of the newer kernel. That is, if the kernel sources are in
-/usr/src/linux, then you should add
--I/usr/src/linux/include/ to your command line when compiling.
-
-
-
-
-
10.2 What tools does Debian provide to build custom kernels?
-
-
-Users who wish to (or must) build a custom kernel are encouraged to download
-the package kernel-package. This package contains the script to
-build the kernel package, and provides the capability to create a Debian
-linux-image-version package just by running the command
-
-
-
- make-kpkg --initrd kernel_image
-
-
-
-in the top-level kernel source directory. Help is available by executing the
-command
-
-
-
- make-kpkg --help
-
-
-
-and through the manual page make-kpkg(1).
-
-
-
-Users must separately download the source code for the most recent kernel (or
-the kernel of their choice) from their favorite Linux archive site, unless a
-linux-source-version package is available (where
-version stands for the kernel version).
-
-
-
-Detailed instructions for using the kernel-package package are
-given in the file /usr/share/doc/kernel-package/README.gz.
-
-
-
-
-
10.3 How can I make a custom boot floppy?
-
-
-This task is greatly aided by the Debian package boot-floppies,
-normally found in the admin section of the Debian FTP archive.
-Shell scripts in this package produce boot floppies in the
-SYSLINUX format. These are MS-DOS formatted floppies
-whose master boot records have been altered so that they boot Linux directly
-(or whatever other operating system has been defined in the
-syslinux.cfg file on the floppy). Other scripts in this package
-produce emergency root disks and can even reproduce the base disks.
-
-
-
-You will find more information about this in the
-/usr/share/doc/boot-floppies/README file after installing the
-boot-floppies package.
-
-
-
-
-
10.4 What special provisions does Debian provide to deal with modules?
-
-
-Debian's modconf package provides a shell script
-(/usr/sbin/modconf) which can be used to customize the
-configuration of modules. This script presents a menu-based interface,
-prompting the user for particulars on the loadable device drivers in his
-system. The responses are used to customize the file
-/etc/modules.conf (which lists aliases, and other arguments that
-must be used in conjunction with various modules) through files in
-/etc/modutils/, and /etc/modules (which lists the
-modules that must be loaded at boot time).
-
-
-
-Like the (new) Configure.help files that are now available to
-support the construction of custom kernels, the modconf package
-comes with a series of help files (in /usr/lib/modules_help/)
-which provide detailed information on appropriate arguments for each of the
-modules.
-
-
-
-
-
10.5 Can I safely de-install an old kernel package, and if so, how?
-
-
-Yes. The linux-image-NNN.prerm script checks to see
-whether the kernel you are currently running is the same as the kernel you are
-trying to de-install. Therefore you can remove unwanted kernel image packages
-using this command:
-
-
-
- dpkg --purge linux-image-NNN
-
-
-
-(replace NNN with your kernel version and revision number, of
-course)
-
-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.
-
-Specifically for Debian lenny, we're working on things like the following:
-
-
-
-
-I18n support in all debconf-using packages: Packages using the Debian
-configuration management must allow for translation of all messages displayed
-to the user during package configuration.
-
-
-
-
-
-
-I18n support for package descriptions: Update package management frontends to
-use the translated descriptions of packages.
-
-
-
-
-
-
-UTF-8 debian/changelog and debian/control. This way, e.g. names of people
-from asian countries can get typeset the right way in changelogs.
-
-
-
-
-
-
-
15.2 Faster booting: Dependency based boot sequence
-
-
-Work is being done on converting the
-Debian boot sequence to use dynamic and dependency based ordering
-instead of hardcoded sequence numbers. Once that's finished, Debian systems
-will boot much faster.
-
-
-
-
-
15.3 Improvements in the Debian Installer
-
-
-Lots of work has been done on the Debian Installer, resulting in major
-improvements. We'll mention just two of them here.
-
-
-
-Starting the installer from Microsoft Windows: It is now possible to start the
-installer directly from Microsoft Windows without the need to change BIOS
-settings. Upon insertion of a CD-ROM, DVD-ROM or USB stick, an autorun program
-will be started, offering a step-by-step process to start the Debian Installer.
-
-
-
-The debian-installer now includes experimental support for installing Debian on
-systems with Serial ATA RAID.
-
-
-
-
-
15.4 More architectures
-
-
-Complete Debian system on other architectures such as ARM EABI (referred to as
-"armel") (next to the old "arm") will likely get supported
-with lenny. Support for SuperH is expected soon.
-Notice that even though some architectures are dropped for a given the release
-there still might be a way to install and upgrade using the latest
-sid.
-
-
-
-
-
15.5 More kernels
-
-
-In addition to Debian GNU/Hurd, Debian is being ported also to BSD kernels,
-namely to FreeBSD. This port
-runs on both AMD64 ("kfreebsd-amd64") and traditional Intel
-("kfreebsd-i386").
-
-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
-7.2); they are usually distinguished by having a '.deb' file extension.
-Binary packages can be unpacked using the Debian utility dpkg
-(possibly via a frontend like aptitude); 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. (The program apt-get can get used a
-frontend for dpkg-source.)
-
-
-
-
-
-Installation of software by the package system uses "dependencies"
-which are carefully designed by the package maintainers. These dependencies
-are documented in the control file associated with each package.
-For example, the package containing the GNU C compiler (gcc)
-"depends" on the package binutils which includes the
-linker and assembler. If a user attempts to install gcc without
-having first installed binutils, the package management system
-(dpkg) will send an error message that it also needs binutils, and
-stop installing gcc. (However, this facility can be overridden by
-the insistent user, see dpkg(8).) See more in What is meant by saying that a package Depends,
-Recommends, Suggests, Conflicts, Replaces
-or Provides another package?, Section 7.9 below.
-
-
-
-Debian's packaging tools can be used to:
-
-
-
-
-manipulate and manage packages or parts of packages,
-
-
-
-
-
-
-administer local overrides of files in a package,
-
-
-
-
-
-
-aid developers in the construction of package archives, and
-
-
-
-
-
-
-aid users in the installation of packages which reside on a remote FTP site.
-
-
-
-
-
-
-
7.2 What is the format of a Debian binary package?
-
-
-A Debian "package", or a Debian archive file, contains the executable
-files, libraries, and documentation associated with a particular suite of
-program or set of related programs. Normally, a Debian archive file has a
-filename that ends in .deb.
-
-
-
-The internals of this Debian binary packages format are described in the
-deb(5) manual page. This internal format is subject to change
-(between major releases of Debian GNU/Linux), therefore please always use
-dpkg-deb(1) if you need to do lowlevel manipulations on
-.deb files.
-
-
-
-
-
7.3 Why are Debian package file names so long?
-
-
-The Debian binary package file names conform to the following convention:
-<foo>_<VersionNumber>-<DebianRevisionNumber>_<DebianArchitecture>.deb
-
-
-
-Note that foo is supposed to be the package name. As a check, one
-can learn the package name associated with a particular Debian archive file
-(.deb file) in one of these ways:
-
-
-
-
-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_AAA.deb (where VVV, RRR
-and AAA are the version, revision and architecture of the package in question,
-respectively). This displays, among other things, the package name
-corresponding to the archive file being unpacked.
-
-
-
-
-
-The VVV component is the version number specified by the upstream
-developer. There are no standards in place here, so the version number may
-have formats as different as "19990513" and "1.3.8pre1".
-
-
-
-The RRR component is the Debian revision number, and is specified
-by the Debian developer (or an individual user if he chooses to build the
-package himself). This number corresponds to the revision level of the Debian
-package, thus, a new revision level usually signifies changes in the Debian
-Makefile (debian/rules), the Debian control file
-(debian/control), the installation or removal scripts
-(debian/p*), or in the configuration files used with the package.
-
-
-
-The AAA component identifies the processor for which the package
-was built. This is commonly i386, which refers to chips
-compatible to Intel's 386 or later versions. For other possibilities review
-Debian's FTP directory structure at What are all those directories at the
-Debian FTP archives?, Section 6.7. For details, see the description of
-"Debian architecture" in the manual page
-dpkg-architecture(1).
-
-Briefly, a sample control file is shown below for the Debian package hello:
-
-
-
- Package: hello
- Priority: optional
- Section: devel
- Installed-Size: 45
- Maintainer: Adam Heath <doogie@debian.org>
- Architecture: i386
- Version: 1.3-16
- Depends: libc6 (>= 2.1)
- Description: The classic greeting, and a good example
- The GNU hello program produces a familiar, friendly greeting. It
- allows nonprogrammers to use a classic computer science tool which
- would otherwise be unavailable to them.
- .
- Seriously, though: this is an example of how to do a Debian package.
- It is the Debian version of the GNU Project's `hello world' program
- (which is itself an example for the GNU Project).
-
-
-
-The Package field gives the package name. This is the name by which the
-package can be manipulated by the package tools, and usually similar to but not
-necessarily the same as the first component string in the Debian archive file
-name.
-
-
-
-The Version field gives both the upstream developer's version number and (in
-the last component) the revision level of the Debian package of this program as
-explained in Why are Debian package file names so long?,
-Section 7.3.
-
-
-
-The Architecture field specifies the chip for which this particular binary was
-compiled.
-
-
-
-The Depends field gives a list of packages that have to be installed in order
-to install this package successfully.
-
-
-
-The Installed-Size indicates how much disk space the installed package will
-consume. This is intended to be used by installation front-ends in order to
-show whether there is enough disk space available to install the program.
-
-
-
-The Section line gives the "section" where this Debian package is
-stored at the Debian FTP sites.
-
-The Maintainer field gives the e-mail address of the person who is currently
-responsible for maintaining this package.
-
-
-
-The Description field gives a brief summary of the package's features.
-
-
-
-For more information about all possible fields a package can have, please see
-the Debian Policy Manual, section 5., "Control files and their
-fields".
-
-
-
-
-
7.5 What is a Debian conffile?
-
-
-Conffiles is a list of configuration files (usually placed in
-/etc) that the package management system will not overwrite when
-the package is upgraded. This ensures that local values for the contents of
-these files will be preserved, and is a critical feature enabling the in-place
-upgrade of packages on a running system.
-
-
-
-To determine exactly which files are preserved during an upgrade, run:
-
-
-
- dpkg --status package
-
-
-
-And look under "Conffiles:".
-
-
-
-
-
7.6 What is a Debian preinst, postinst, prerm, and postrm script?
-
-
-These files are executable scripts which are automatically run before or after
-a package is installed. Along with a file named control, all of
-these files are part of the "control" section of a Debian archive
-file.
-
-
-
-The individual files are:
-
-
-
preinst
-
-
-This script executes before that package will be unpacked from its Debian
-archive (".deb") file. Many 'preinst' scripts stop services for
-packages which are being upgraded until their installation or upgrade is
-completed (following the successful execution of the 'postinst' script).
-
-
-
-
-
postinst
-
-
-This script typically completes any required configuration of the package
-foo once foo has been unpacked from its Debian
-archive (".deb") file. Often, 'postinst' scripts ask the user for
-input, and/or warn the user that if he accepts default values, he should
-remember to go back and re-configure that package as the situation warrants.
-Many 'postinst' scripts then execute any commands necessary to start or restart
-a service once a new package has been installed or upgraded.
-
-
-
-
-
prerm
-
-
-This script typically stops any daemons which are associated with a package.
-It is executed before the removal of files associated with the package.
-
-
-
-
-
postrm
-
-
-This script typically modifies links or other files associated with
-foo, and/or removes files created by the package. (Also see What is a Virtual Package?, Section 7.8.)
-
-
-
-
-
-Currently all of the control files can be found in directory
-/var/lib/dpkg/info. The files relevant to package
-foo begin with the name "foo" and have file extensions
-of "preinst", "postinst", etc., as appropriate. The file
-foo.list in that directory lists all of the files that were
-installed with the package foo. (Note that the location of these
-files is a dpkg internal; you should not rely on it.)
-
-
-
-
-
7.7 What is an Essential, Required, Important, Standard, Optional, or Extra package?
-
-
-Each Debian package is assigned a priority by the distribution
-maintainers, as an aid to the package management system. The priorities are:
-
-
-
-
-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 X 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. Tools are
-included to be able to browse the web (using w3m), send e-mail (with mutt) and
-download files from FTP servers.
-
-
-
-This is what will install by default if users do not select anything else. It
-does not include many large applications, but it does include the Python
-interpreter and some server software like OpenSSH (for remote administration),
-Exim (for mail delivery, although it can be configured for local delivery
-only), an identd server (pidentd) and the RPC portmapper
-(portmap). It also includes some common generic documentation
-that most users will find helpful.
-
-
-
-
-
-
-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 X, 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.
-
-
-
-
-
7.8 What is a Virtual Package?
-
-
-A virtual package is a generic name that applies to any one of a group of
-packages, all of which provide similar basic functionality. For example, both
-the tin and trn programs are news readers, and should
-therefore satisfy any dependency of a program that required a news reader on a
-system, in order to work or to be useful. They are therefore both said to
-provide the "virtual package" called news-reader.
-
-
-
-Similarly, smail and sendmail both provide the
-functionality of a mail transport agent. They are therefore said to provide
-the virtual package, "mail transport agent". If either one is
-installed, then any program depending on the installation of a
-mail-transport-agent will be satisfied by the existence of this
-virtual package.
-
7.9 What is meant by saying that a package Depends, Recommends, Suggests, Conflicts, Replaces or Provides another package?
-
-
-The Debian package system has a range of package "dependencies" which
-are designed to indicate (in a single flag) the level at which Program A can
-operate independently of the existence of Program B on a given system:
-
-
-
-
-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.
-
-
-
-
-
7.10 What is meant by Pre-Depends?
-
-
-"Pre-Depends" is a special dependency. In the case of most packages,
-dpkg will unpack its archive file (i.e., its .deb
-file) independently of whether or not the files on which it depends exist on
-the system. Simplistically, unpacking means that dpkg will
-extract the files from the archive file that were meant to be installed on your
-file system, and put them in place. If those packages depend on the
-existence of some other packages on your system, dpkg will refuse
-to complete the installation (by executing its "configure" action)
-until the other packages are installed.
-
-
-
-However, for some packages, dpkg will refuse even to unpack them
-until certain dependencies are resolved. Such packages are said to
-"Pre-depend" on the presence of some other packages. The Debian
-project provided this mechanism to support the safe upgrading of systems from
-a.out format to ELF format, where the order
-in which packages were unpacked was critical. There are other large upgrade
-situations where this method is useful, e.g. the packages with the required
-priority and their LibC dependency.
-
-
-
-As before, more detailed information about this can be found in the Policy
-manual.
-
-
-
-
-
7.11 What is meant by unknown, install, remove, purge and hold in the package status?
-
-
-These "want" flags tell what the user wanted to do with a package (as
-indicated either by the user's actions in the "Select" section of
-dselect, or by the user's direct invocations of
-dpkg).
-
-
-
-Their meanings are:
-
-
-
-
-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.
-
-
-
-
-
-
-
7.12 How do I put a package on hold?
-
-
-There are three ways of holding back packages, with dpkg, aptitude or with
-dselect.
-
-
-
-With dpkg, you have to export the list of package selections, with:
-
-
-
- dpkg --get-selections \* > selections.txt
-
-
-
-Then edit the resulting file selections.txt, change the line
-containing the package you wish to hold, e.g. libc6, from this:
-
-
-
- libc6 install
-
-
-
-to this:
-
-
-
- libc6 hold
-
-
-
-Save the file, and reload it into dpkg database with:
-
-
-
- dpkg --set-selections < selections.txt
-
-
-
-With aptitude, you can hold a package using
-
-
-
- aptitude hold package_name
-
-
-
-and remove the hold with
-
-
-
- aptitude unhold package_name
-
-
-
-With dselect, you have to enter the [S]elect screen, find the package you wish
-to hold in its present state, and press the `=' key (or `H'). The changes will
-go live immediately after you exit the [S]elect screen.
-
-
-
-
-
7.13 How do I install a source package?
-
-
-Debian source packages can't actually be "installed", they are just
-unpacked in whatever directory you want to build the binary packages they
-produce.
-
-
-
-Source packages are distributed on most of the same mirrors where you can
-obtain the binary packages. If you set up your APT's
-sources.list(5) to include the appropriate "deb-src"
-lines, you'll be able to easily download any source packages by running
-
-
-
- apt-get source foo
-
-
-
-To help you in actually building the source package, Debian source package
-provide the so-called build-dependencies mechanism. This means that the source
-package maintainer keeps a list of other packages that are required to build
-their package. To see how this is useful, run
-
-
-
- apt-get build-dep foo
-
-
-
-before building the source.
-
-
-
-
-
7.14 How do I build binary packages from a source package?
-
-
-The preferred way to do this is by using various wrapper tools. We'll show how
-it's done using the devscripts tools. Install this package if you
-haven't done so already.
-
-Then create a dedicated version of your own build (so that you won't get
-confused later when Debian itself releases a new version)
-
-
-
- dch -l local 'Blah blah blah'
-
-
-
-And finally build your package
-
-
-
- debuild -us -uc
-
-
-
-If everything worked out fine, you should now be able to install your package
-by running
-
-
-
- sudo dpkg -i ../*.deb
-
-
-
-If you prefer to do things manually, and don't want to use
-devscripts, follow this procedure:
-
-
-
-You will need all of foo_*.dsc, foo_*.tar.gz and foo_*.diff.gz to compile the
-source (note: there is no .diff.gz for some packages that are native to
-Debian).
-
8.1 What programs does Debian provide for managing its packages?
-
-
-There are multiple tools that are used to manage Debian packages, from graphic
-or text-based interfaces to the low level tools used to install packages. All
-the available tools rely on the lower level tools to properly work and are
-presented here in decreasing complexity level.
-
-
-
-It is important to understand that the higher level package management tools
-such as aptitude or dselect rely on apt
-which, itself, relies on dpkg to manage the packages in the
-system.
-
-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 7.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 7.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*'.
-
-
-
-
-
-
-
8.1.2 APT
-
-
-APT is the Advanced Package Tool and provides the apt-get
-program. apt-get provides a simple way to retrieve and install
-packages from multiple sources using the command line. Unlike
-dpkg, apt-get does not understand .deb files, it
-works with the packages proper name and can only install .deb archives from a
-source specified in /etc/apt/sources.list. apt-get
-will call dpkg directly after downloading the .deb archives[5] from the configured sources.
-
-
-
-Some common ways to use apt-get are:
-
-
-
-
-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 (without installing extra packages
-or removing packages), 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, and, if needed for a package
-upgrade, installing extra packages or removing packages, run:
-
-
-
- apt-get dist-upgrade
-
-
-
-(The command upgrade keeps a package at its installed obsolete
-version if upgrading would need an extra package to be installed, for a new
-dependency to be satisfied. The dist-upgrade command is less
-conservative.)
-
-
-
-
-
-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 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.
-
-
-
-
-
8.1.3 aptitude
-
-
-aptitude is a package manager for Debian GNU/Linux systems that
-provides a frontend to the apt package management infrastructure.
-aptitude is a text-based interface using the curses library, it
-can be used to perform management tasks in a fast and easy way.
-
-
-
-aptitude provides the functionality of dselect and
-apt-get, as well as many additional features not found in either
-program:
-
-
-
-
-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[6].
-
-
-
-
-
-
-aptitude can be used to install the predefined tasks available.
-For more information see tasksel, Section 8.1.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 preferred program for package management
-from console both for package installations and package or system upgrades.
-
-
-
-For more informations, read the manual page aptitude(8) and
-install the aptitude-doc package.
-
-
-
-
-
8.1.4 synaptic
-
-
-synaptic is a graphical package manager. It enables you to
-install, upgrade and remove software packages in a user friendly way. Next to
-all features offered by aptitude, it also has a feature for editing the list of
-used repositories, and supports browsing all available documentation related to
-a package. See the Synaptic
-Website for more information.
-
-
-
-
-
8.1.5 tasksel
-
-
-When you want to perform a specific task it might be difficult to find the
-appropiate suite of packages that fill your need. The Debian developers have
-defined tasks, a task is a collection of several individual Debian
-packages all related to a specific activity. Tasks can be installed through
-the tasksel program or through aptitude.
-
-
-
-The Debian installer will typically install automaticaly the task associated
-with a standard system and a desktop environment. The specific desktop
-environment installed will depend on the CD/DVD media used, most commonly it
-will be the GNOME desktop (gnome-desktop task). Also, depending
-on your selections throughout the installation process, tasks might be
-automatically installed in your system. For example, if you selected a
-language, the task associated with it will be installed automatically too and
-if you are running in a laptop system the installer recognises the
-laptop task will be installed too.
-
-
-
-
-
8.1.6 Other package management tools
-
-
-
-
8.1.6.1 dselect
-
-
-This program is a menu-driven interface to the Debian package management
-system. For woody and earlier releases, this was the main package management
-interface for for first-time installations, but currently users are encouraged
-to use aptitude instead. Some users might feel more comfortable
-using aptitude and it is also recommended over
-dselect for large-scale upgrades. For more information on
-aptitude please see aptitude, Section
-8.1.3.
-
-
-
-dselect can:
-
-
-
-
-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 18200 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
-7.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.
-
-
-
-
-
-
-
8.1.6.2 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.
-
-
-
-
-
-
-Extract the control information files from a package: dpkg-deb --control
-foo_VVV-RRR.deb tmp.
-
-
-
-
-
-Note that any packages that were merely unpacked using dpkg-deb
---extract will be incorrectly installed, you should use dpkg
---install instead.
-
-
-
-More information is given in the manual page dpkg-deb(1).
-
-
-
-
-
8.1.6.3 dpkg-split
-
-
-This program splits large package into smaller files (e.g., for writing onto a
-set of floppy disks), and can also be used to merge a set of split files back
-into a single file. It can only be used on a Debian system (i.e. a system
-containing the dpkg package), since it calls the program
-dpkg-deb to parse the debian package file into its component
-records.
-
-
-
-For example, to split a big .deb file into N parts,
-
-
-
-
-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*".
-
-
-
-
-
-
-
8.2 Debian claims to be able to update a running program; how is this accomplished?
-
-
-The kernel (file system) in Debian GNU/Linux systems supports replacing files
-even while they're being used.
-
-
-
-We also provide a program called start-stop-daemon which is used
-to start daemons at boot time or to stop daemons when the runlevel is changed
-(e.g., from multi-user to single-user or to halt). The same program is used by
-installation scripts when a new package containing a daemon is installed, to
-stop running daemons, and restart them as necessary.
-
-
-
-
-
8.3 How can I tell what packages are already installed on a Debian system?
-
-
-To learn the status of all the packages installed on a Debian system, execute
-the command
-
-
-
- dpkg --list
-
-
-
-This prints out a one-line summary for each package, giving a 2-letter status
-symbol (explained in the header), the package name, the version which is
-installed, and a brief description.
-
-
-
-To learn the status of packages whose names match the string any pattern
-beginning with "foo" by executing the command:
-
-
-
- dpkg --list 'foo*'
-
-
-
-To get a more verbose report for a particular package, execute the command:
-
-
-
- dpkg --status packagename
-
-
-
-
-
8.4 How to display the files of a package installed?
-
-
-To list all the files provided by the installed package foo
-execute the command
-
-
-
- dpkg --listfiles foo
-
-
-
-Note that the files created by the installation scripts aren't displayed.
-
-
-
-
-
8.5 How can I find out what package produced a particular file?
-
-
-To identify the package that produced the file named foo execute
-either:
-
-
-
-
-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.
-
-
-
- dlocate -S filename
-
-
-
-
-
-
-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/etch). 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
-
-
-
-If you install the apt-file, 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.
-
-
-
-
-
-
-
8.6 Why doesn't get `foo-data' removed when I uninstall `foo'? How do I make sure old unused library-packages get purged?
-
-
-Some packages are split in program (`foo') and data (`foo-data') (or in `foo'
-and `foo-doc'). This is true for many games, multimedia applications and
-dictionaries in Debian and has been introduced since some users might want to
-access the raw data without installing the program or because the program can
-be run without the data itself, making it optional.
-
-
-
-Similar situations occur when dealing with libraries: generally these get
-installed since packages containing applications depend on them. When the
-application-package is purged, the library-package might stay on the system.
-Or: when the application-package no longer depends upon e.g. libdb4.2, but
-upon libdb4.3, the libdb4.2 package might stay when the application-package is
-upgraded.
-
-
-
-In these cases, `foo-data' doesn't depend on `foo', so when you remove the
-`foo' package it will not get automatically removed by most package management
-tools. The same holds true for the library packages. This is necessary to
-avoid circular dependencies. If you use aptitude (see aptitude, Section 8.1.3) as your package management tool
-it will, however, track automatically installed packages and remove them when
-no packages remain that need them in your system.
-
-The Debian GNU/Linux FAQ
- Chapter 14 - Redistributing Debian GNU/Linux in a commercial product
-
-
-
-
-
14.1 Can I make and sell Debian CDs?
-
-
-Go ahead. You do not need permission to distribute anything we have
-released, so that you can master your CD as soon as the beta-test
-ends. You do not have to pay us anything. Of course, all CD manufacturers
-must honor the licenses of the programs in Debian. For example, many of the
-programs are licensed under the GPL, which requires you to distribute their
-source code.
-
-
-
-Also, we will publish a list of CD manufacturers who donate money, software,
-and time to the Debian project, and we will encourage users to buy from
-manufacturers who donate, so it is good advertising to make donations.
-
-
-
-
-
14.2 Can Debian be packaged with non-free software?
-
-
-Yes. While all the main components of Debian are free software, we provide a
-non-free directory for programs that are not freely redistributable.
-
-
-
-CD manufacturers may be able to distribute the programs we have placed
-in that directory, depending on the license terms or their private arrangements
-with the authors of those software packages. CD manufacturers can also
-distribute the non-free software they get from other sources on the same CD.
-This is nothing new: free and commercial software are distributed on the same
-CD by many manufacturers now. Of course we still encourage software authors to
-release the programs they write as free software.
-
-
-
-
-
14.3 I am making a special Linux distribution for a "vertical market". Can I use Debian GNU/Linux for the guts of a Linux system and add my own applications on top of it?
-
-
-Yes. Debian-derived distributions are being created both in close cooperation
-with the Debian project itself and by external parties. One can use the
-Custom Debian
-Distributions framework to work together with Debian; Skolelinux is one such project.
-
-
-
-There are several other Debian-derived distributions already on the market,
-such as Progeny Debian, Linspire, Knoppix and Ubuntu, that are targeted at a
-different kind of audience than the original Debian GNU/Linux is, but use most
-of our components in their product.
-
-The Debian GNU/Linux FAQ
- Chapter 5 - Software available in the Debian system
-
-
-
-
-
5.1 What types of applications and development software are available for Debian GNU/Linux?
-
-
-Like most Linux distributions, Debian GNU/Linux provides:
-
-
-
-
-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 Xorg windowing system, which provides a networked graphical user interface
-for Linux, and countless X applications including the GNOME, KDE and Xfce
-desktop environments.
-
-
-
-
-
-
-a full suite of networking applications, including servers for Internet
-protocols such as HTTP (WWW), FTP, NNTP (news), SMTP and POP (mail) and DNS
-(name servers); relational databases like PostgreSQL, MySQL; also provided are
-web browsers including the various Mozilla products [1],
-
-
-
-
-
-
-a complete set of office applications, including the OpenOffice.org
-productivity suite, Gnumeric and other spreadsheets, WYSIWYG editors,
-calendars.
-
-
-
-
-
-More than 18040 packages, ranging from news servers and readers to sound
-support, FAX programs, database and spreadsheet programs, image processing
-programs, communications, net, and mail utilities, Web servers, and even
-ham-radio programs are included in the distribution. Another 560 software
-suites are available as Debian packages, but are not formally part of Debian
-due to license restrictions.
-
-
-
-
-
5.2 Who wrote all that software?
-
-
-For each package the authors of the program(s) are credited in the
-file /usr/share/doc/PACKAGE/copyright, where PACKAGE is to be
-substituted with the package's name.
-
-
-
-Maintainers who package this software for the Debian GNU/Linux system
-are listed in the Debian control file (see What is a Debian control file?,
-Section 7.4) that comes with each package. The Debian changelog, in
-/usr/share/doc/PACKAGE/changelog.Debian.gz, mentions the people
-who've worked on the Debian packaging too.
-
-
-
-
-
5.3 How can I get a current list of programs that have been packaged for Debian?
-
-
-A complete list is available from any of the Debian mirrors, in the
-file indices/Maintainers. That file includes the package names
-and the names and e-mails of their respective maintainers.
-
5.4 How can I install a developer's environment to build packages?
-
-
-If you want to build packages in your Debian system you will need to have a
-basic development environment, including a C/C++ compiler and some other
-essential packages. In order to install this environment you just need to
-install the build-essential. This package is a meta-package or
-place-holder package which depends on the standard development tools one needs
-to build a Debian package.
-
-
-
-Some software can, however, need additional software to be rebuilt, including
-library headers or additional tools such as autoconf or
-gettext. Debian provides many of the tools needed to build other
-software as Debian packages.
-
-
-
-Finding which software is precisely required can be tricky, however, unless you
-are planning on rebuilding Debian packages. This last task is rather easy to
-do, as official packages have to include a list of the additional software
-(besides the packages in build-essential) needed to build the
-pacakge, this is known as Build-Dependencies. To install all the
-packages needed to build a given source package and then build said source
-package you can just run:
-
5.6 Why do I get "ld: cannot find -lfoo" messages when compiling programs? Why aren't there any libfoo.so files in Debian library packages?
-
-
-Debian Policy requires that such symbolic links (to libfoo.so.x.y.z or similar)
-are placed in separate, development packages. Those packages are usually named
-libfoo-dev or libfooX-dev (presuming the library package is named libfooX, and
-X is a whole number).
-
-
-
-
-
5.7 (How) Does Debian support Java?
-
-
-Several free implementations of Java technology are available as
-Debian packages, providing both Java Development Kits as well as Runtime
-Environments. You can write, debug and run Java programs using Debian.
-
-
-
-Running a Java applet requires a web browser with the capability to recognize
-and execute them. Several web browsers available in Debian, such as Mozilla or
-Konqueror, support Java plug-ins that enable running Java applets within them.
-
5.8 How can I check that I am using a Debian system, and what version is it?
-
-
-In order to make sure that your system has been installed from the real Debian
-base disks check for the existence of /etc/debian_version file,
-which contains a single one-line entry giving the version number of the
-release, as defined by the package base-files.
-
-
-
-The existence of the program dpkg shows that you should be able to
-install Debian packages on your system, but as the program has been ported to
-many other operating systems and architectures, this is no longer a reliable
-method of determining is a system Debian GNU/Linux.
-
-
-
-Users should be aware, however, that the Debian system consists of many parts,
-each of which can be updated (almost) independently. Each Debian
-"release" contains well defined and unchanging contents. Updates are
-separately available. For a one-line description of the installation status of
-package foo, use the command dpkg --list foo. To
-view versions of all installed packages, run:
-
-
-
- dpkg -l
-
-
-
-For a more verbose description, use:
-
-
-
- dpkg --status foo
-
-
-
-
-
5.9 How does Debian support non-English languages?
-
-
-
-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-, Dutch-, Polish-, Portuguese-, Russian-, Turkish-,
-and Chinese-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/.
-
-
-
-
-
-
-
5.10 Where is pine?
-
-
-Due to its restrictive license, it's in the non-free area. Moreover, since
-license does not even allow modified binaries to be distributed, you have to
-compile it yourself from the source and the Debian patches.
-
-
-
-The source package name is pine. You can use the
-pine-tracker package to be notified about when you need to
-upgrade.
-
-
-
-Note that there are many replacements for both pine and pico, such as
-mutt and nano, that are located in the main section.
-
-
-
-
-
5.11 Where is qmail/ezmlm/djbdns?
-
-
-Dan J. Bernstein used to distribute all software he has written
-with a restrictive license which does not allow modified binaries to be
-distributed. In november 2007 however, Bernstein said "[...] i have
-decided to put all of my future and [...] past software into the public
-domain". See FAQ from
-distributors for his distribution terms.
-
-
-
-As of 2008-04, daemontools, djbdns and
-ucspi-tcp are shipped with Debian lenny (in main). As of this
-writing (2008-04), qmail is not yet packaged for Debian main; see
-Bug #457318 (ITP
-qmail) for the current status.
-
-
-
-As of 2008-04, publicfile and ezmlm were still not
-free software. For ezmlm, there's the ezmlm-src
-package in the non-free area.
-
-
-
-
-
5.12 Where is a player for Flash (SWF)?
-
-
-Debian ships both gnash and swfdec: two free SWF
-movie players.
-
-
-
-
-
5.13 Where is Google Earth?
-
-
-Google Earth is available for GNU/Linux from Google's web site, but is not only
-not Free Software, but is completely undistributable by a third party.
-However, googleearth-package (in the contrib-section) might be
-helpful in using this software.
-
-
-
-
-
5.14 Where is VoIP software?
-
-
-Two main open protocols are used for Voice Over IP: SIP and H.323. Both are
-implemented by a wide variety of software in Debian main. ekiga
-is one of the popular clients.
-
-
-
-
-
5.15 I have a wireless network card which doesn't work with Linux. What should I do?
-
-
-Buy one which does :)
-
-
-
-Alternatively, use ndiswrapper to use a driver for Windows (if you
-have one) on your Linux system. See the Debian Wiki ndiswapper
-page for more information.
-
-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.
-
-The Debian Policy manual documents the policy requirements for the
-distribution, i.e. the structure and contents of the Debian archive, several
-design issues of the operating system etc. It also includes the technical
-requirements that each package must satisfy to be included in the distribution,
-and documents the basic technical aspects of Debian binary and source packages.
-
-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. For instance, to see the manual page for the
-command `ls', execute man ls. Execute man man for
-more information on finding and viewing manual pages.
-
-
-
-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, or by using `yelp'.
-
-
-
-
-
12.2 Are there any on-line resources for discussing Debian?
-
-
-Yes. In fact, the main method of support Debian provides to our users is by
-the way of e-mail. We'll give some details on that, and mention some other
-useful resources. Even more resources are listed at the Debian Support webpage.
-
-On a system with the doc-debian package installed there is a
-complete list of mailing lists in
-/usr/share/doc/debian/mailing-lists.txt.
-
-
-
-Debian mailing lists are named following the pattern
-debian-list-subject. Examples are debian-announce, debian-user,
-debian-news. To subscribe to any list debian-list-subject, send
-mail to debian-list-subject-request@lists.debian.org with the word
-"subscribe" in the Subject: header. Be sure to remember to add
--request to the e-mail address when using this method to subscribe or
-unsubscribe. Otherwise your e-mail will go to the list itself, which could be
-embarrassing or annoying, depending on your point of view.
-
-
-
-You can subscribe to mailing lists using the WWW form. You
-can also un-subscribe using a WWW form.
-
-The 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.
-
-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[7]
-
-debianHELP and Debian User Forums are web forums
-on which you can submit questions about Debian and have them answered by other
-users. (These are not officially part of the Debian project.)
-
-
-
-
-
12.2.3 Wiki
-
-
-Solutions to common problems, howto's, guides, tips and other documentation can
-be found at the constantly changing Debian Wiki.
-
-
-
-
-
12.2.4 Maintainers
-
-
-Users can address questions to individual package maintainers using e-mail. To
-reach a maintainer of a package called xyz, send e-mail to
-xyz@packages.debian.org.
-
-
-
-
-
12.2.5 Usenet newsgroups
-
-
-Users should post non-Debian-specific questions to one of the Linux USENET
-groups, which are named comp.os.linux.* or linux.*. There are several lists of
-Linux Usenet newsgroups and other related resources on the WWW, e.g. on the
-Linux Online
-and LinuxJournal sites.
-
-
-
-
-
12.3 Is there a quick way to search for information on Debian GNU/Linux?
-
-
-There is a variety of search engines that serve documentation related to
-Debian:
-
-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.
-
-
-
-
-
-
-
12.4 Are there logs of known bugs?
-
-
-Reports on unsolved (and closed) issues are publicly available: Debian
-promissed to do so by stating "We will not hide problems" in the
-Debian Social
-Contract.
-
-
-
-The Debian GNU/Linux distribution has a bug tracking system (BTS) which files
-details of bugs reported by users and developers. Each bug is given a number,
-and is kept on file. Once it has been dealt with, it is marked as such.
-
-A mail server provides access to the bug tracking system database via e-mail.
-In order to get the instructions, send an e-mail to request@bugs.debian.org
-with "help" in the body.
-
-
-
-
-
12.5 How do I report a bug in Debian?
-
-
-If you have found a bug in Debian, please read the instructions for reporting a
-bug in Debian. These instructions can be obtained in one of several ways:
-
-On any Debian system with the doc-debian package installed. The
-instructions are in the file
-/usr/share/doc/debian/bug-reporting.txt.
-
-
-
-
-
-
-By anonymous FTP. Debian mirror sites contain the instructions in the file
-doc/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 add additional information to the
-existing bug report.
-
-
-
-Expect to get an automatic acknowledgement of your bug report. It will also be
-automatically given a bug tracking number, entered into the bug log and
-forwarded to the debian-bugs-dist mailing list.
-
-The Debian GNU/Linux FAQ
- Chapter 9 - Keeping your Debian system up-to-date
-
-
-
-
-
-A Debian goal is to provide a consistent upgrade path and a secure upgrade
-process. We always do our best to make upgrading to new releases a smooth
-procedure. In case there's some important note to add to the upgrade process,
-the packages will alert the user, and often provide a solution to a possible
-problem.
-
-
-
-You should also read the Release Notes document that describes the details of
-specific upgrades. It is shipped on all Debian CDs and available on the WWW at
-http://www.debian.org/releases/stable/releasenotes.
-
-
-
-
-
9.1 How can I keep my Debian system current?
-
-
-One could simply execute an anonymous ftp call to a Debian archive, then peruse
-the directories until one finds the desired file, and then fetch it, and
-finally install it using dpkg. Note that dpkg will
-install upgrade files in place, even on a running system. Sometimes, a revised
-package will require the installation of a newly revised version of another
-package, in which case the installation will fail until/unless the other
-package is installed.
-
-
-
-Many people find this approach much too time-consuming, since Debian evolves so
-quickly -- typically, a dozen or more new packages are uploaded every week.
-This number is larger just before a new major release. To deal with this
-avalanche, many people prefer to use a more automated method. Several
-different packages are available for this purpose:
-
-
-
-
-
9.1.1 aptitude
-
-
-APT is an advanced interface to the Debian packaging system. It features
-complete installation ordering, multiple source capability and several other
-unique features, see the User's Guide in
-/usr/share/doc/apt-doc/guide.html/index.html (you will have to
-install the apt-doc package).
-
-
-
-aptitude is the recommended package manager for Debian GNU/Linux
-systems. It is a text-based interface to APT using the curses library, and can
-be used to perform management tasks in a fast and easy way.
-
-
-
-Before you can use aptitude, you'll have to edit the
-/etc/apt/sources.list file to set it up. If you wish to upgrade
-to the latest stable version of Debian, you'll probably want to use a source
-like this one:
-
-
-
- http://ftp.us.debian.org/debian stable main contrib non-free
-
-
-
-You can replace ftp.us.debian.org with the name of a faster Debian mirror near
-you. See the mirror list at http://www.debian.org/mirror/list
-for more information.
-
-
-
-More details on this can be found in the sources.list(8) manual
-page.
-
-
-
-To update your system, run
-
-
-
- aptitude update
-
-
-
-followed by
-
-
-
- aptitude dist-upgrade
-
-
-
-Answer any questions that might come up, and your system will be upgraded. See
-also aptitude, Section 8.1.3.
-
-
-
-
-
9.1.2 apt-get, dselect and apt-cdrom
-
-
-apt-get is an APT-based command-line tool for handling packages,
-and the APT dselect method is an interface to APT through dselect.
-Both of these provide a simple, safe way to install and upgrade packages.
-
-
-
-To use apt-get, install the apt package, and edit the
-/etc/apt/sources.list file to set it up, just as for aptitude, Section 9.1.1.
-
-
-
-Then run
-
-
-
- apt-get update
-
-
-
-followed by
-
-
-
- apt-get dist-upgrade
-
-
-
-Answer any questions that might come up, and your system will be upgraded. See
-also the apt-get(8) manual page, as well as APT, Section 8.1.2.
-
-
-
-To use APT with dselect, choose the APT access method in dselect's
-method selection screen (option 0) and then specify the sources that should be
-used. The configuration file is /etc/apt/sources.list. See also
-dselect, Section 8.1.6.1.
-
-
-
-If you want to use CDs to install packages, you can use apt-cdrom.
-For details, please see the Release Notes, section "Setting up for an
-upgrade from a local mirror".
-
-
-
-Please note that when you get and install the packages, you'll still have them
-kept in your /var directory hierarchy. To keep your partition from
-overflowing, remember to delete extra files using apt-get clean
-and apt-get autoclean, or to move them someplace else (hint: use
-apt-move).
-
-
-
-
-
9.1.3 aptitude
-
-
-aptitude is a text-based interface to the Debian package system.
-It allows the user to view the list of packages and to perform package
-management tasks such as installing, upgrading, and removing packages (see aptitude, Section 8.1.3). Actions
-may be performed from a visual interface or from the command-line.
-
-
-
-In command line, the actions are similar to that of APT, so to upgrade your
-system run
-
-For details, see the manual page aptitude(8), and the file
-/usr/share/aptitude/README
-
-
-
-
-
9.1.4 mirror
-
-
-This Perl script, and its (optional) manager program called
-mirror-master, can be used to fetch user-specified parts of a
-directory tree from a specified host via anonymous FTP.
-
-
-
-mirror is particularly useful for downloading large volumes of
-software. After the first time files have been downloaded from a site, a file
-called .mirrorinfo is stored on the local host. Changes to the
-remote file system are tracked automatically by mirror, which
-compares this file to a similar file on the remote system and downloads only
-changed files.
-
-
-
-The mirror program is generally useful for updating local copies
-of remote directory trees. The files fetched need not be Debian files. (Since
-mirror is a Perl script, it can also run on non-Unix systems.)
-Though the mirror program provides mechanisms for excluding files
-names of which match user-specified strings, this program is most useful when
-the objective is to download whole directory trees, rather than selected
-packages.
-
-
-
-
-
9.1.5 dpkg-mountable
-
-
-dpkg-mountable adds an access method called `mountable' to dselect's list,
-which allows you to install from any file system specified in /etc/fstab. For
-example, the archive could be a normal hard disk partition or an NFS server,
-which it will automatically mount and umount for you if necessary.
-
-
-
-It also has some extra features not found in the standard dselect methods, such
-as provision for a local file tree (either parallel to the main distribution or
-totally separate), and only getting packages which are required, rather than
-the time-consuming recursive directory scan, as well as logging of all dpkg
-actions in the install method.
-
-
-
-
-
9.2 Must I go into single user mode in order to upgrade a package?
-
-
-No. Packages can be upgraded in place, even in running systems. Debian has a
-start-stop-daemon program that is invoked to stop, then restart
-running process if necessary during a package upgrade.
-
-
-
-
-
9.3 Do I have to keep all those .deb archive files on my disk?
-
-
-No. If you have downloaded the files to your disk then after you have
-installed the packages, you can remove them from your system, e.g. by running
-aptitude clean.
-
-
-
-
-
9.4 How can I keep a log of the packages I added to the system? I'd like to know when which package upgrades and removals have occured!
-
-
-Passing the --log-option to dpkg makes
-dpkg log status change updates and actions. It logs both the
-dpkg-invokation (e.g.
-
- 2005-12-30 18:10:35 status installed hello 2.1.1-4
-
-
-
-) If you'd like to log all your dpkg invokations (even those done
-using frontends like aptitude), you could add
-
-
-
- log /var/log/dpkg.log
-
-
-
-to your /etc/dpkg/dpkg.cfg. Be sure the created logfile gets
-rotated periodically. If you're using logrotate, this can be
-achieved by creating a file /etc/logrotate.d/dpkg with contents
-
-
-
- /var/log/dpkg {
- missingok
- notifempty
- }
-
-
-
-More details on dpkg logging can be found in the
-dpkg(1) manual page.
-
-
-
-aptitude logs the package installations, removals, and upgrades
-that it intends to perform to /var/log/aptitude. Note that the
-results of those actions are not recorded in this file!
-
-
-
-Another way to record your actions is to run your package management session
-within the script(1) program.
-
-
-
-
-
9.5 Can I automatically update the system?
-
-
-Yes. You can use cron-apt, this tool updates the system at
-regular interval by using a cron job. By default it just updates the package
-list and download new packages without installing.
-
-
-
-Note: Automatic upgrade of packages is NOT recommended in
-testing or unstable systems as this might bring unexpected
-behaviour and remove packages without notice.
-
-
-
-
-
9.6 I have several machines how can I download the updates only one time?
-
-
-If you have more than one Debian machine on your network, it is useful to use
-apt-proxy to keep all of your Debian systems up-to-date.
-
-
-
-apt-proxy reduces the bandwidth requirements of Debian mirrors by
-restricting the frequency of Packages, Releases and Sources file updates from
-the back end and only doing a single fetch for any file, independently of the
-actual request it from the proxy. apt-proxy automatically builds
-a Debian HTTP mirror based on requests which pass through the proxy.
-
-When the present-day sid did not exist, the FTP site organization had one major
-flaw: there was an assumption that when an architecture is created in the
-current unstable, it will be released when that distribution becomes the new
-stable. For many architectures that isn't the case, with the result that those
-directories had to be moved at release time. This was impractical because the
-move would chew up lots of bandwidth.
-
-
-
-The archive administrators worked around this problem for several years by
-placing binaries for unreleased architectures in a special directory called
-"sid". For those architectures not yet released, the first time they
-were released there was a link from the current stable to sid, and from then on
-they were created inside the unstable tree as normal. This layout was somewhat
-confusing to users.
-
-
-
-With the advent of package pools (see What's in the
-pool directory?, Section 6.10), binary packages began to be
-stored in a canonical location in the pool, regardless of the distribution, so
-releasing a distribution no longer causes large bandwidth consumption on the
-mirrors (there is, however, a lot of gradual bandwidth consumption throughout
-the development process).
-
-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.
-
-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.
-
This disc contains the installer for the
- Debian GNU/Linux distribution.
- Debian is a very extensive collection of software. But it
- is more. It is a complete Operating System (OS) for your
- computer. And it is free (as in
- “freedom”).
An operating system is the set of basic programs and
- utilities that make your computer run. At the core of an
- operating system is the kernel. The kernel is the most
- fundamental program on the computer, which does all the basic
- housekeeping and lets you start other programs. Debian is
- kernel independent. It currently uses the Linux kernel but work is in
- progress to provide Debian for other kernels, using the Hurd. Most
- of the basic operating system tools come from the GNU project; hence the name
- GNU/Linux.
-
-
Debian is available for various kinds of computers
- (“architectures”), like “IBM-compatible” PCs (i386),
- Compaq's Alpha, Sun's Sparc, Motorola/IBM's
- PowerPC, and (Strong)ARM processors. Check the
- ports page for more
- information.
This disc is labeled
- Debian GNU/Linux 5.0.0 "Lenny" - Official i386 NETINST Binary-1 20090214-14:36
- .
- It contains programs ("binaries") for `i386' computers.
-
This disc is a netinst image. It contains the installer and
- a very basic system. Any other packages you might want to install will
- be downloaded from the network.
-
The Release Notes for "lenny" are available on the
- Debian web
- site.
-
-
- Installing
-
-
-
Because Debian is a complete Operating System, the
- installation procedure may seem a bit unusual. You can install
- Debian GNU/Linux either alongside your current OS, or as
- the only OS on your computer.
For the impatient ones: you can start the installation program easily by
- booting off this disc. Note that not all (esp. older) systems support
- this.
-
-
You can also examine the /install/
- directory; you might be able to start the installation system directly
- from there.
-
-
-
- Last-Minute Notes
-
-
-
-
You should keep in mind that this is a beta disc of the current
- development version of the Debian system. This means that all sorts of
- bugs may be present anywhere in the system. Please report any bugs you
- find in the Debian Bug Tracking System; details at bugs.debian.org.
-
-
If you're reporting bugs against this disc or the installation
- system, please also mention the version of this disc; this can be found
- in the file /.disk/info.
-
-
-
-
- Installing software using Apt
-
-
-
After installing or upgrading, Debian's packaging system can
- use CDs, DVDs, local collections, or networked servers (FTP,
- HTTP) to automatically install software from (.deb
- packages). This is done preferably with the ‘apt’ and
- ‘aptitude’ programs.
-
-
You can install packages from the commandline using
- apt-get. For example, if you want to install the
- packages ‘commprog’ and ‘maxgame’, you can give the
- command:
-
-
- apt-get install commprog maxgame
-
-
-
Note that you don't have to enter the complete path, or the
- ‘.deb’ extension. ‘Apt’ will figure this out
- itself.
-
-
Or use aptitude for a full screen interactive selection of
- available Debian packages.
-
-
- CD/DVD Manufacturers
-
-
-
You are completely free to manufacture and re-distribute CDs/DVDs of the
- Debian GNU/Linux Operating System, like this one. There is no charge from
- us (but of course donations are always welcome).
-
-
For all needed information and contact addresses, please
- refer to:
There is much more information present on this disc. Besides
- the already mentioned installation and upgrading procedures,
- this is the most interesting:
Debian is distributed (mirrored) on hundreds of servers on the Internet.
-Using a nearby server will probably speed up your download, and also
-reduce the load on our central servers and on the Internet as a whole.
-
-
Debian mirrors can be primary and secondary. The definitions are as follows:
-
-
- A primary mirror site has good bandwidth, is available 24 hours a day,
- and has an easy to remember name of the form ftp.<country>.debian.org.
-
- They are all automatically updated whenever there are updates to
- the Debian archive.
-
-
-
- A secondary mirror site may have restrictions on what they mirror (due to
- space restrictions). Just because a site is secondary doesn't necessarily
- mean it'll be any slower or less up to date than a primary site.
-
-
-
Use the site closest to you for the fastest downloads possible whether it is
-
-a primary or secondary site. The program
-
-netselect can be used to
-determine the site with the least latency; use a download program such as
-
-
-wget or
-
-rsync for determining the site with the most throughput.
-Note that geographic proximity often isn't the most important factor for
-determining which machine will serve you best.
-
-
This disc is labeled
- Debian GNU/Linux squeeze-di-rc2 "Squeeze" - Official Snapshot i386 NETINST Binary-1 20110121-20:12
+ Debian GNU/Linux 5.0.0 "Lenny" - Official i386 NETINST Binary-1 20090214-14:36
.
It contains programs ("binaries") for `i386' computers.
This disc is a netinst image. It contains the installer and
a very basic system. Any other packages you might want to install will
be downloaded from the network.
+
The Release Notes for "lenny" are available on the
+ Debian web
+ site.
Installing
@@ -119,12 +122,9 @@
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.
-
For the impatient ones: you can start the installation program easily by
@@ -146,9 +146,10 @@
bugs may be present anywhere in the system. Please report any bugs you
find in the Debian Bug Tracking System; details at bugs.debian.org.
-
If you're reporting bugs against this disc or the installation
- system, please also mention the version of this disc; this can be found
- in the file /.disk/info.
+
+
If you're reporting bugs against this disc or the installation
+ system, please also mention the version of this disc; this can be found
+ in the file /.disk/info.
diff --git a/includes/squeeze/install/README.mirrors.html b/includes/squeeze/install/README.mirrors.html
index 7d918fadc..6d01dfb2d 100644
--- a/includes/squeeze/install/README.mirrors.html
+++ b/includes/squeeze/install/README.mirrors.html
@@ -48,9 +48,9 @@ please have the site maintainer fill out the form at:
Everything else you want to know about Debian mirrors:
http://www.debian.org/mirror/.
-
Primary Debian mirror sites
+
Primary Debian mirror sites
-
+
Country
Site
@@ -59,247 +59,222 @@ Everything else you want to know about Debian mirrors: