aboutsummaryrefslogtreecommitdiffhomepage
path: root/test/reference/abstraction/live-manual.en.ssp
diff options
context:
space:
mode:
authorRalph Amissah <ralph.amissah@gmail.com>2026-09-03 12:44:01 -0400
committerRalph Amissah <ralph.amissah@gmail.com>2026-09-03 15:25:55 -0400
commit569d38694b10e3de1dc493f5b5ac08f99164b1a0 (patch)
tree5fdfef70053941cd0d451329b38916d3facdfcb1 /test/reference/abstraction/live-manual.en.ssp
parentocda a fix & ssp code-style use curly braces (diff)
test-abstraction-ssp re-generated
Several structure fields (now) computed in ocda do not yet have a consumer outside the `.ssp` writer (which shares ocda fields in a PEG parsable .ssp file). Their addition is to facilitate future output processing: each representing document structure information that document output generators of various formats, such as html, epub, latex, sql and any DOM based / tree-graph (node based hierarchical) representations, previously had to, or would have to, work out for themselves based on what ocda offered (without them). Computing them (upstream) in ocda once and sharing them (and providing the .ssp), means that: - future output formats can start from prepared structure rather than deriving it; - existing generators can be simplified to consume them instead of re-deriving; - a (dlang) generator could in principle be populated either from ocda directly or from a `.ssp` file; - `.ssp` being PEG parsable puts the same prepared structure in reach of implementations in other languages. `test/test-abstraction-ssp.sh` the `.ssp` reference regression test is used to catch regression in ocda including these as yet unused fields, which otherwise would remain unseen until used by other output-format consumers. This also is the reason issues now made easily visible and are being addressed (without issue to existing output generators). (assisted by Claude-Code)
Diffstat (limited to 'test/reference/abstraction/live-manual.en.ssp')
-rw-r--r--test/reference/abstraction/live-manual.en.ssp678
1 files changed, 0 insertions, 678 deletions
diff --git a/test/reference/abstraction/live-manual.en.ssp b/test/reference/abstraction/live-manual.en.ssp
index 583355d..4c88581 100644
--- a/test/reference/abstraction/live-manual.en.ssp
+++ b/test/reference/abstraction/live-manual.en.ssp
@@ -1620,7 +1620,6 @@
.ancestors: 1 3 0 0 4 0 0 0
.ancestors_collapsed: 1 3 4 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: CF6A6826A6E817A3FA731837482BECD2B27975CAAA105B9575D7FDBFC80A9FAA
.has: links
@@ -1633,7 +1632,6 @@
.ancestors: 1 3 0 0 4 0 0 0
.ancestors_collapsed: 1 3 4 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 652A953F649650F722575033962EA34FF4B0169A5F698CE7CEF2AF549096B261
.has: links
@@ -1645,7 +1643,6 @@
.ancestors: 1 3 0 0 4 0 0 0
.ancestors_collapsed: 1 3 4 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 2B1A72406999251894DFBA79B240DA9C0A9BDBF563F2194B957B59DC9CE09288
| Some of the commands mentioned in the text must be executed with superuser privileges which can be obtained by becoming the root user via ⑆■┨su┣■ or by using ⑆■┨sudo┣■. To distinguish between commands which may be executed by an unprivileged user and those requiring superuser privileges, commands are prepended by ⑆■┨$┣■ or ⑆■┨#┣■ respectively. This symbol is not a part of the command.
@@ -1673,7 +1670,6 @@
.ancestors: 1 3 0 0 4 8 0 0
.ancestors_collapsed: 1 3 4 8 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4777A818B6A263BC9B3A17D4C1423D94451E2E67863C606375516368B323DCCD
| While we believe that everything in this manual is important to at least some of our users, we realize it is a lot of material to cover and that you may wish to experience early success using the software before delving into the details. Therefore, we suggest reading in the following order.
@@ -1684,7 +1680,6 @@
.ancestors: 1 3 0 0 4 8 0 0
.ancestors_collapsed: 1 3 4 8 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 032BAA6A01F5A7D212632F90BC9761C7F20F55066149CCDB2E765698154116FD
.has: links
@@ -1696,7 +1691,6 @@
.ancestors: 1 3 0 0 4 8 0 0
.ancestors_collapsed: 1 3 4 8 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4D1E6AC7C0BC57A072C70772F7AEA18DA380BD81189159C9AA59D7B49735C987
.has: links
@@ -1726,7 +1720,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E1409C47189F446658FB519D5B5B0EDA67143633DA95A1F49C76C6FF3EC8AABB
.bullet: true
@@ -1739,7 +1732,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7057601CBA7E62A6D099573EBC1A3A78E24FCCDE6AF2D30EDEF3580CA8CADF65
.bullet: true
@@ -1751,7 +1743,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0E391B8809195B666F041886BBD0A670958AE5A7A2BF3D29F0C168F5AB776959
.bullet: true
@@ -1763,7 +1754,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4A0E0D5934B68CD7092C45C124A658FE3C451004B028D9C323E18725E13FA926
.bullet: true
@@ -1775,7 +1765,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 17DB661E0E1D3EFF7F9046271C19DA6007D26A76DF6AE4806D4D0E7AF4A70E52
.bullet: true
@@ -1787,7 +1776,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E5040633CD1304F9C9089DE8877FF8EF5786ADE52D84173F9971999C16A473A2
.bullet: true
@@ -1799,7 +1787,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 51359C80D0DD29A243F7DEC4F43EEF38B5ECA0DF1D491D4C9F983CD88A02763E
.bullet: true
@@ -1811,7 +1798,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 67E3C8D55AA9A76F7977FBBCCA3F791B98AA3BA6031242D68ABF2B181076EEBB
.bullet: true
@@ -1823,7 +1809,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6DDB37A427F0B06B0D0263E66808C22DB61DED9A6900239EA751F8E061D385F9
.bullet: true
@@ -1835,7 +1820,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BAC576F207E3C6E1B002B455DB0489FE879F25CBE4C27DA8E26DF8E36F46BD15
.bullet: true
@@ -1847,7 +1831,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0CB214FFF534842E2CE5D321DE1295FA5447EDDF0D0486923A6CF00D83ACD152
.bullet: true
@@ -1859,7 +1842,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 294886AE72BB7E00C1883F4976F7483EF2A271BC5CC04A06EA56CCD858E544F5
.bullet: true
@@ -1871,7 +1853,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DB83FE42D9646F24F50AB2FA960B972D2BAD71003A5539D80F7F0D8121DE6E09
.bullet: true
@@ -1883,7 +1864,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E8223CE086081589E69814B900FB663C1CAE53B16EB72C6D02DA83A963312329
.bullet: true
@@ -1895,7 +1875,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8DA1C84FD5D24752BCB2BB12F42DF845BE5120229568CA9619F77AF147FA94BB
.bullet: true
@@ -1907,7 +1886,6 @@
.ancestors: 1 3 0 0 4 12 0 0
.ancestors_collapsed: 1 3 4 12 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DF1466A22CC2FD6EBD69A24241AFB553B22CE76AFE7AFF32E778363855815566
.bullet: true
@@ -1936,7 +1914,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 673847822EE0A65A38DC58631721FE5C969D89AE3B04D417B290395249B6B3F2
| A list of authors (in alphabetical order):
@@ -1947,7 +1924,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A109C0542678BB6982B8E9FC014E3815FA489B924E45403B69A5537FC81D7B81
.bullet: true
@@ -1959,7 +1935,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FA898105BFB1CD02986ED56ABA1274D8B552ADFD70918B31C94090E45A3C7AB7
.bullet: true
@@ -1971,7 +1946,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 635D9F20E9308BA714AF627BF2255628424542007E4C929BA675B4F72D1DDFC0
.bullet: true
@@ -1983,7 +1957,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5F0C9DD3AB56364AE3D2A2F301419B9C3C45D76D3F57D7D888FE9D737834A942
.bullet: true
@@ -1995,7 +1968,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D8313C6494B025E33CAA3429FCCF6B6A1E3A83431574AAC5B8BC7F0DDD8B81D5
.bullet: true
@@ -2007,7 +1979,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F40A3B6D4760AB73B902084F077788C63F96A31B149CCA4725FEC2F83513E962
.bullet: true
@@ -2019,7 +1990,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CAC93328B0209AC53328687869B3954400C224322DFA14F653B99DC3D1480A6C
.bullet: true
@@ -2031,7 +2001,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C54C8286CDF93399A964A853ACFFA1922C89F0D824F6C2A792EFD59D04742C42
.bullet: true
@@ -2043,7 +2012,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4EB13C4C455AFE5DD93BA815A72259E7F41592B79848EB7EBDD8E92A3A1BFE7C
.bullet: true
@@ -2055,7 +2023,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2D524759328A6CED7E0B1ACA1AD21400E2344A3A4A7848626D20852C75249748
.bullet: true
@@ -2067,7 +2034,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6AD9C66B111A2F642BD62CDBF67FED3F0C338355AF2DFC5295BCF3539A22EE5D
.bullet: true
@@ -2079,7 +2045,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1E42E9F0ED3066FE2E01A595F6B3505002FA2AA0FB8B3E6955DF8C613473297B
.bullet: true
@@ -2091,7 +2056,6 @@
.ancestors: 1 3 0 0 4 29 0 0
.ancestors_collapsed: 1 3 4 29 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C32CDFB7850107ED56F3DDF0A998685CF7E8425D7A00671852F1DE076DDC905D
.bullet: true
@@ -2122,7 +2086,6 @@
.ancestors: 1 3 0 0 4 44 0 0
.ancestors_collapsed: 1 3 4 44 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 967EEAEF6738C5191941809921E22DDA9FE11BAC05C9199D97EDF82C5DFDE50B
.has: links
@@ -2152,7 +2115,6 @@
.ancestors: 1 3 0 0 4 44 46 0
.ancestors_collapsed: 1 3 4 44 46 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D752C0633E0D4C4EB750A33D2B75381D86BB247356A3F9040944C73F915401E2
| In order to make changes to the English manual you have to edit the right files in ⑆■┨manual/en/┣■ but prior to the submission of your contribution, please preview your work. To preview the live-manual, ensure the packages needed for building it are installed by executing:
@@ -2173,7 +2135,6 @@
.ancestors: 1 3 0 0 4 44 46 0
.ancestors_collapsed: 1 3 4 44 46 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 0272408EDECDF04883BEDF9F2440ACB33CB60AF6A1DE062C5F8DA31284063190
| You may build the live-manual from the top level directory of your Git checkout by executing:
@@ -2194,7 +2155,6 @@
.ancestors: 1 3 0 0 4 44 46 0
.ancestors_collapsed: 1 3 4 44 46 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: FD71F7AF4A07D73D04CA3EFD2DBC9EC3B9824FC0F6C44A623F941F42030CD433
| Since it takes a while to build the manual in all supported languages, authors may find it convenient to use one of the fast proofing shortcuts when reviewing the new documentation they have added to the English manual. Using ⑆■┨PROOF=1┣■ builds live-manual in html format, but without the segmented html files, and using ⑆■┨PROOF=2┣■ builds live-manual in pdf format, but only the A4 and letter portraits. That is why using either of the ⑆■┨PROOF=┣■ possibilities can save up a considerable amount of time, e.g:
@@ -2215,7 +2175,6 @@
.ancestors: 1 3 0 0 4 44 46 0
.ancestors_collapsed: 1 3 4 44 46 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 53C3D0C0731F7781F11C2DD9B70986BD64419EDB2AAB0E81B7F6C8FAA29B7884
| When proofing one of the translations it is possible to build only one language by executing, e.g:
@@ -2236,7 +2195,6 @@
.ancestors: 1 3 0 0 4 44 46 0
.ancestors_collapsed: 1 3 4 44 46 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 5DDF2E0E3B517F0CC8CAFE862C26F3412D6D3A302A15B2C4C642642A85C45419
| It is also possible to build by document type, e.g:
@@ -2257,7 +2215,6 @@
.ancestors: 1 3 0 0 4 44 46 0
.ancestors_collapsed: 1 3 4 44 46 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: CA2765464FADA7B160C5820144A26EDE027C87DCC1820A0BC8B9C680DBBBBC90
| Or combine both, e.g:
@@ -2278,7 +2235,6 @@
.ancestors: 1 3 0 0 4 44 46 0
.ancestors_collapsed: 1 3 4 44 46 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 87813A1F47C8CF44D7C75E152E51EC0E1F1B22B4C09D36BA8C2CE3C4A1687F6E
.has: links
@@ -2308,7 +2264,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: ECA2C5B99AF6D00F4AA504BDBAFFDE2D5D71DF629938D13E98450BB5119DAAAA
| In order to translate live-manual, follow these steps depending on whether you are starting a translation from scratch or continue working on an already existing one:
@@ -2319,7 +2274,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E71D2D7E0FB56E2A8E604CF802094E9051661D642677BC8129844057D80C0089
.bullet: true
@@ -2331,7 +2285,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: DE78828BE1F4156B91CF6B154F42E51DC243AD152AB29E6E4E7329F30F35BEAA
.indent: 2 2
@@ -2344,7 +2297,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 76A9D3CEE18A75DF219D1308566221C218E5F4EC29B6C5B8E9E3A03E43AD60E0
.indent: 2 2
@@ -2357,7 +2309,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B78D04056EB5B94C7C15CA9928F70C9A1269C9B78B6E64D6D23EEA5741183C45
.bullet: true
@@ -2369,7 +2320,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8AFFA8A2DF9C9DD60ED001589AB4DF59FF4CC2E510279246B6F7A89BDEF0991D
.indent: 2 2
@@ -2382,7 +2332,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 20303F17924D8B02C723668ABBB7F5C237B3476A9B771B66B44B02F9594E5E26
.indent: 2 2
@@ -2396,7 +2345,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D955CF3077D91BAF06C3EA0408E10B43E2E7CE95C21706A8E47B479249315E96
| After running ⑆■┨make commit┣■ you will see some text scroll by. These are basically informative messages about the processing status and also some hints about what can be done in order to improve live-manual. Unless you see a fatal error, you usually can proceed and submit your contribution.
@@ -2407,7 +2355,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BCF30C9FCF7AFDC055740594A00EA0722E22CB53B4D9E3C61AE043F730ABAD02
| live-manual comes with two utilities that can greatly help translators to find untranslated and changed strings. The first one is “make translate”. It launches an script that tells you in detail how many untranslated strings there are in each .po file. The second one, the “make fixfuzzy” target, only acts upon changed strings but it helps you to find and fix them one by one.
@@ -2418,7 +2365,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8A65A074F8F94B9A1C8CF629D93EA381243E11B6E9650EA1D44D599644731684
.has: links
@@ -2430,7 +2376,6 @@
.ancestors: 1 3 0 0 4 44 60 0
.ancestors_collapsed: 1 3 4 44 60 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E23346A4B108CB331AB31D2E3C5EF7AC35B38DD7BB46DC2361F1D55F91EFCE19
| ⑆*┨Note:┣* You can use ⑆■┨make clean┣■ to clean your git tree before pushing. This step is not compulsory thanks to the .gitignore file but it is a good practice to avoid committing files involuntarily.
@@ -2522,7 +2467,6 @@
.ancestors: 1 72 0 0 73 74 75 0
.ancestors_collapsed: 1 72 73 74 75 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BF065D02DAA07D9438558C29E4D2C51BB713E1720DC6ACA94C970B4F73E1B1CB
| When ${project} was initiated, there were already several Debian based live systems available and they are doing a great job. From the Debian perspective most of them have one or more of the following disadvantages:
@@ -2533,7 +2477,6 @@
.ancestors: 1 72 0 0 73 74 75 0
.ancestors_collapsed: 1 72 73 74 75 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C5C01BAEE153FCBF7C24F47A748985A352BB5FDEC95C5468DEA3991826D1596C
.bullet: true
@@ -2545,7 +2488,6 @@
.ancestors: 1 72 0 0 73 74 75 0
.ancestors_collapsed: 1 72 73 74 75 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B565654D903E835DF82F565CE4369504FE309D4E5D4CE59D1509C062EC2D35F4
.bullet: true
@@ -2557,7 +2499,6 @@
.ancestors: 1 72 0 0 73 74 75 0
.ancestors_collapsed: 1 72 73 74 75 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: A36A29DDBA5295B359687C99ED0F047408C69C1DE98BE45B09F22FC9E35BB14F
.bullet: true
@@ -2569,7 +2510,6 @@
.ancestors: 1 72 0 0 73 74 75 0
.ancestors_collapsed: 1 72 73 74 75 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: CE7F94B7C96138F10579723098B636B279FD28A98317B5E0D2885808AC31F957
.bullet: true
@@ -2581,7 +2521,6 @@
.ancestors: 1 72 0 0 73 74 75 0
.ancestors_collapsed: 1 72 73 74 75 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C272D0619ACF8A43627A0B5FB0EC6C1EC3998903185FB38E1A4AFB3E49DEBC28
.bullet: true
@@ -2593,7 +2532,6 @@
.ancestors: 1 72 0 0 73 74 75 0
.ancestors_collapsed: 1 72 73 74 75 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 31D6FD0E8B72AF80D0AE16E4BD2157C83B2EEA515699EC59FF63FE97D0420B65
.bullet: true
@@ -2605,7 +2543,6 @@
.ancestors: 1 72 0 0 73 74 75 0
.ancestors_collapsed: 1 72 73 74 75 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 953C66A52431991D3A643A6AB8B6B9BE9278827A771E4974BA502C9FAAD19F94
.bullet: true
@@ -2617,7 +2554,6 @@
.ancestors: 1 72 0 0 73 74 75 0
.ancestors_collapsed: 1 72 73 74 75 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: FB99D8B1660C92AB5D25832776E95CC3EE0F7739052462852C5D0BE1F7FE3E24
.bullet: true
@@ -2646,7 +2582,6 @@
.ancestors: 1 72 0 0 73 74 85 0
.ancestors_collapsed: 1 72 73 74 85 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D40F21B03A6E19544B079769BB5B5DEB88907C3DD5AD86590CB6276EE90D3BE0
| Debian is the Universal Operating System: Debian has a live system to show around and to accurately represent the Debian system with the following main advantages:
@@ -2657,7 +2592,6 @@
.ancestors: 1 72 0 0 73 74 85 0
.ancestors_collapsed: 1 72 73 74 85 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: CDC5430A007E0F77F8CBD61A4D26630D2E65EA993EFEBB1496142EA703CCA76C
.bullet: true
@@ -2669,7 +2603,6 @@
.ancestors: 1 72 0 0 73 74 85 0
.ancestors_collapsed: 1 72 73 74 85 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 56C555C48C60DFF0D70E0619BF3A4ACE1C8CCE80A26F8E0E32592826E55ACD89
.bullet: true
@@ -2681,7 +2614,6 @@
.ancestors: 1 72 0 0 73 74 85 0
.ancestors_collapsed: 1 72 73 74 85 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: EBAC9D704C668D02543FB0C9E4FD9AC1BD30AB8371C577F89D1136F8C451180A
.bullet: true
@@ -2693,7 +2625,6 @@
.ancestors: 1 72 0 0 73 74 85 0
.ancestors_collapsed: 1 72 73 74 85 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: DCC758644982A757259B33794FF72F97BA941CCCFC6C07BAF7513A107260CBD6
.bullet: true
@@ -2705,7 +2636,6 @@
.ancestors: 1 72 0 0 73 74 85 0
.ancestors_collapsed: 1 72 73 74 85 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: AD1056476C42CE8D11D129EF1FA897EE4CEFD2DF666E741A2CCB884789504389
.bullet: true
@@ -2717,7 +2647,6 @@
.ancestors: 1 72 0 0 73 74 85 0
.ancestors_collapsed: 1 72 73 74 85 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 11FD0BC3AC07F28AA861C4E6211B5872EAB973756036670E3C7FA61AF3716C7B
.bullet: true
@@ -2764,7 +2693,6 @@
.ancestors: 1 72 0 0 73 93 94 0
.ancestors_collapsed: 1 72 73 93 94 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C2D19980583346E82E9FFEF558CB390D03533638882BF3CE242250B0B2F4198F
| We will only use packages from the Debian repository in the “main” section. The non-free section is not part of Debian and therefore cannot be used for official live system images.
@@ -2775,7 +2703,6 @@
.ancestors: 1 72 0 0 73 93 94 0
.ancestors_collapsed: 1 72 73 93 94 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 19B96107FE67860521B601CB90B4D1213D12F01F023851CC21CBC94498799F9C
| We will not change any packages. Whenever we need to change something, we will do that in coordination with its package maintainer in Debian.
@@ -2786,7 +2713,6 @@
.ancestors: 1 72 0 0 73 93 94 0
.ancestors_collapsed: 1 72 73 93 94 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E8033608838EFB7C396059F53454B27DA39E063EA2D1717CF024FAAC4B085310
| As an exception, our own packages such as live-boot, live-build or live-config may temporarily be used from our own repository for development reasons (e.g. to create development snapshots). They will be uploaded to Debian on a regular basis.
@@ -2814,7 +2740,6 @@
.ancestors: 1 72 0 0 73 93 98 0
.ancestors_collapsed: 1 72 73 93 98 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6D2E5AA15BCE92D56A09512B17CED0675838AE8213D658B68D4ED70658ABBB77
| In this phase we will not ship or install sample or alternative configurations. All packages are used in their default configuration as they are after a regular installation of Debian.
@@ -2825,7 +2750,6 @@
.ancestors: 1 72 0 0 73 93 98 0
.ancestors_collapsed: 1 72 73 93 98 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D71ED7CC51D9D1D0CD9179E7EB7E23A657B0F9266074FA04F0ED0B75F1F83E5C
| Whenever we need a different default configuration, we will do that in coordination with its package maintainer in Debian.
@@ -2836,7 +2760,6 @@
.ancestors: 1 72 0 0 73 93 98 0
.ancestors_collapsed: 1 72 73 93 98 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C786DCCA05FA86B0472C6FE2C4205C760BB1A11CD907E7ACDB2A45ACD0F8872C
.has: links
@@ -2866,7 +2789,6 @@
.ancestors: 1 72 0 0 73 102 0 0
.ancestors_collapsed: 1 72 73 102 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B97834A21DEEB972210009E1E0E6894830835C6F23C05458CF568CF8723FA014
.bullet: true
@@ -2881,7 +2803,6 @@
.ancestors: 1 72 0 0 73 102 0 0
.ancestors_collapsed: 1 72 73 102 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2E706D6D203736FF1056CFEBBB59F146FE85373F1611BD81665C4F97A6875F2C
.bullet: true
@@ -2894,7 +2815,6 @@
.ancestors: 1 72 0 0 73 102 0 0
.ancestors_collapsed: 1 72 73 102 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 698C5218007E40C46F8DFD2713632390C4AE623BEA2EE7DDDA3E9862B57315EB
.bullet: true
@@ -2991,7 +2911,6 @@
.ancestors: 1 107 0 0 108 109 0 0
.ancestors_collapsed: 1 107 108 109 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DC43C513B5630F20C261FE4EAED140510E65B0269B008A1862CC52FCBCF09116
| Building live system images has very few system requirements:
@@ -3002,7 +2921,6 @@
.ancestors: 1 107 0 0 108 109 0 0
.ancestors_collapsed: 1 107 108 109 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D9606F0FA8CEE78E78C94A109A49B189C9DFF4F80EED3105E32938F8383CC0A5
.bullet: true
@@ -3014,7 +2932,6 @@
.ancestors: 1 107 0 0 108 109 0 0
.ancestors_collapsed: 1 107 108 109 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E14A43D1AE91BE947D3C99BB337C0558AB3C3D5772C766CAF054FC82D86741A8
.bullet: true
@@ -3026,7 +2943,6 @@
.ancestors: 1 107 0 0 108 109 0 0
.ancestors_collapsed: 1 107 108 109 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A8F845AA0B4A30CCE7DD1430F7893C2A05155FEF15AC60ED45B03BA56B27E56D
.bullet: true
@@ -3038,7 +2954,6 @@
.ancestors: 1 107 0 0 108 109 0 0
.ancestors_collapsed: 1 107 108 109 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E1E4B6F8EF16A84D97ACA13C07482CD70A701D7745E4445C7C1782DB324F46A3
.bullet: true
@@ -3050,7 +2965,6 @@
.ancestors: 1 107 0 0 108 109 0 0
.ancestors_collapsed: 1 107 108 109 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 683A85D38E7AFBD9D2EC2715AC8AE31E540968A1D7A819C0727DE945511CC82A
.bullet: true
@@ -3062,7 +2976,6 @@
.ancestors: 1 107 0 0 108 109 0 0
.ancestors_collapsed: 1 107 108 109 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3E5E441D78EEED814B36B6A6495425F631B0DF8D2457192D4A43D939296E27F4
| Note that using Debian or a Debian-derived distribution is not required - live-build will run on almost any distribution with the above requirements.
@@ -3092,7 +3005,6 @@
.ancestors: 1 107 0 0 108 117 0 0
.ancestors_collapsed: 1 107 108 117 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E8756C9A371A975D2975884461A37E63DDBD1649FDB19FAF8866109A1A7B7AB4
| You can install live-build in a number of different ways:
@@ -3103,7 +3015,6 @@
.ancestors: 1 107 0 0 108 117 0 0
.ancestors_collapsed: 1 107 108 117 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EF997A1C7482E5A7ABE40056894C7639C519075477BF473C1A9039A241BBE188
.bullet: true
@@ -3115,7 +3026,6 @@
.ancestors: 1 107 0 0 108 117 0 0
.ancestors_collapsed: 1 107 108 117 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5BE49BD81AF3BBAF8C8E1392407F0323FBA03D6400CB80FEB154050D724E8177
.bullet: true
@@ -3127,7 +3037,6 @@
.ancestors: 1 107 0 0 108 117 0 0
.ancestors_collapsed: 1 107 108 117 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 30E809C77778CBCBEEE98585F18680055F8BF46678AD31160B6DD93C8CF7A4C7
.bullet: true
@@ -3139,7 +3048,6 @@
.ancestors: 1 107 0 0 108 117 0 0
.ancestors_collapsed: 1 107 108 117 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 781333611E8BEE69E26281CEDAD36AF2A7658910A1046FAD4669991281E5882D
| If you are using Debian, the recommended way is to install live-build via the Debian repository.
@@ -3167,7 +3075,6 @@
.ancestors: 1 107 0 0 108 117 123 0
.ancestors_collapsed: 1 107 108 117 123 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 50B96DE95B6A5D97C377069D3C06506286237681CF7C92E8B552298AA74B4157
| Simply install live-build like any other package:
@@ -3205,7 +3112,6 @@
.ancestors: 1 107 0 0 108 117 126 0
.ancestors_collapsed: 1 107 108 117 126 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 31D758EB066C9AA2717341CC81E957BBD98547499013F9DBC94F6902103D6F45
| live-build is developed using the Git version control system. On Debian based systems, this is provided by the ⑆/┨git┣/ package. To check out the latest code, execute:
@@ -3226,7 +3132,6 @@
.ancestors: 1 107 0 0 108 117 126 0
.ancestors_collapsed: 1 107 108 117 126 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E29A7845A74BAB9F3779965E07ABDE8BF603A96F5F844AB75F01C218F524A6DC
| You can build and install your own Debian package by executing:
@@ -3249,7 +3154,6 @@
.ancestors: 1 107 0 0 108 117 126 0
.ancestors_collapsed: 1 107 108 117 126 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B892BEBFDE8CAEB391E3F0326D7857F1A6830FD0CC1C3901E2D8B117CC1A4723
| Now install whichever of the freshly built ⑆■┨.deb┣■ files you were interested in, e.g.
@@ -3270,7 +3174,6 @@
.ancestors: 1 107 0 0 108 117 126 0
.ancestors_collapsed: 1 107 108 117 126 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 91A6FF04FA0B32BB77C76AF4FB62558647E74C42421BB652801EC14594044376
| You can also install live-build directly to your system by executing:
@@ -3291,7 +3194,6 @@
.ancestors: 1 107 0 0 108 117 126 0
.ancestors_collapsed: 1 107 108 117 126 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C9F9E50B95D8D50898EF6B2AA2E04D5AD4AD5BB802E7E2919021A6F99F0955D5
| and uninstall it with:
@@ -3329,7 +3231,6 @@
.ancestors: 1 107 0 0 108 117 137 0
.ancestors_collapsed: 1 107 108 117 137 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7AB8D61594041535EA62B1A24E559A8F14AD5DDE3E9781E6D629F2949860637A
.has: links
@@ -3360,7 +3261,6 @@
.ancestors: 1 107 0 0 108 139 0 0
.ancestors_collapsed: 1 107 108 139 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7BC879A6D8532B83778FB136E8846525E983C72C700E0DD17343B4771B7060B9
| ⑆*┨Note:┣* You do not need to install live-boot or live-config on your system to create customized live systems. However, doing so will do no harm and is useful for reference purposes. If you only want the documentation, you may now install the ⑆/┨live-boot-doc┣/ and ⑆/┨live-config-doc┣/ packages separately.
@@ -3388,7 +3288,6 @@
.ancestors: 1 107 0 0 108 139 141 0
.ancestors_collapsed: 1 107 108 139 141 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 520373676A1FD07DC28A80F2231F323789BE39B0B3EF8CB5E0BC1376405602DC
.has: links
@@ -3417,7 +3316,6 @@
.ancestors: 1 107 0 0 108 139 143 0
.ancestors_collapsed: 1 107 108 139 143 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7FF503F5581925DA649D616292134E24B305DC553EBDC1455A227BB75A3BA36E
.has: links
@@ -3429,7 +3327,6 @@
.ancestors: 1 107 0 0 108 139 143 0
.ancestors_collapsed: 1 107 108 139 143 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6A95613F2EC21B7ED58829CE50AEAA15640044E7D9B5240220A81817AB777479
.bullet: true
@@ -3452,7 +3349,6 @@
.ancestors: 1 107 0 0 108 139 143 0
.ancestors_collapsed: 1 107 108 139 143 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1EB0837AE5B2BC82135D0B12AC1ED6687B761637E81B8311FDF67E84350541E8
| Consult the live-boot and live-config man pages for details on customizing if that is your reason for building these packages from source.
@@ -3463,7 +3359,6 @@
.ancestors: 1 107 0 0 108 139 143 0
.ancestors_collapsed: 1 107 108 139 143 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6005CF3094FFA2643E50CFE1C3080DD7A056A6AEAEA50C8B300D0C7CA5A9EBED
.bullet: true
@@ -3475,7 +3370,6 @@
.ancestors: 1 107 0 0 108 139 143 0
.ancestors_collapsed: 1 107 108 139 143 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: FBF869A12788AF9D0DAB37EAED256F78EF7DDF7C3E2A8A496B5638751CD73AF0
| You must build either on your target distribution or in a chroot containing your target platform: this means if your target is ${testing} then you should build against ${testing}.
@@ -3486,7 +3380,6 @@
.ancestors: 1 107 0 0 108 139 143 0
.ancestors_collapsed: 1 107 108 139 143 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: F2AFA8E92935D6BEAD8A8286AB6F6DA5A4629E27CDEC5C0AD28EF1DAF1A77F7C
| Use a personal builder such as ⑆/┨pbuilder┣/ or ⑆/┨sbuild┣/ if you need to build live-boot for a target distribution that differs from your build system. For example, for ${testing} live images, build live-boot in a ${testing} chroot. If your target distribution happens to match your build system distribution, you may build directly on the build system using ⑆■┨dpkg-buildpackage┣■ (provided by the ⑆/┨dpkg-dev┣/ package):
@@ -3510,7 +3403,6 @@
.ancestors: 1 107 0 0 108 139 143 0
.ancestors_collapsed: 1 107 108 139 143 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BFD93A232F27CFE45DA01F3D52BD54DF87804413BF470C29813661901F261487
.bullet: true
@@ -3522,7 +3414,6 @@
.ancestors: 1 107 0 0 108 139 143 0
.ancestors_collapsed: 1 107 108 139 143 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C99D37ACD9BF2B7D2F7624E19E72AE63BBE064F097FED0873046C1E47AC978B0
.has: links
@@ -3562,7 +3453,6 @@
.ancestors: 1 107 0 0 108 139 155 0
.ancestors_collapsed: 1 107 108 139 155 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 889EBC7B1E794B32605153A923CD8133C98F4B4934DE7B64B41ECB20966AED2B
| You can let live-build automatically use the latest snapshots of live-boot and live-config by configuring the package repository on live-systems.org as a third-party repository in your live-build configuration directory.
@@ -3634,7 +3524,6 @@
.ancestors: 1 157 0 0 158 0 0 0
.ancestors_collapsed: 1 157 158 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: B329CD8B12E126D48CBFF572EC13B750DF94027EA7F77D625AFE5B57102403B1
| This chapter contains a brief overview of the build process and instructions for using the three most commonly used image types. The most versatile image type, ⑆■┨iso-hybrid┣■, may be used on a virtual machine, optical medium or USB portable storage device. In certain special cases, as explained later, the ⑆■┨hdd┣■ type may be more suitable. The chapter includes detailed instructions for building and using a ⑆■┨netboot┣■ type image, which is a bit more involved due to the setup required on the server. This is an slightly advanced topic for anyone who is not already familiar with netbooting, but it is included here because once the setup is done, it is a very convenient way to test and deploy images for booting on the local network without the hassle of dealing with image media.
@@ -3645,7 +3534,6 @@
.ancestors: 1 157 0 0 158 0 0 0
.ancestors_collapsed: 1 157 158 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 56D1456189B7CA93DBEDE73F37B0FD23AA231EB1BA62AF9A3EFC47A654BE60A2
.has: links
@@ -3657,7 +3545,6 @@
.ancestors: 1 157 0 0 158 0 0 0
.ancestors_collapsed: 1 157 158 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: F0D6BB40DD7083D828F18AAF3BEFE0447BA8615D8EAF67A58DFE873A200F5216
.has: links
@@ -3687,7 +3574,6 @@
.ancestors: 1 157 0 0 158 162 0 0
.ancestors_collapsed: 1 157 158 162 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 809331FC8E008257FCF250E608478A458992EE01C5AB84173638803A6859EA89
.has: links
@@ -3699,7 +3585,6 @@
.ancestors: 1 157 0 0 158 162 0 0
.ancestors_collapsed: 1 157 158 162 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2745A89A7F7B839F79DF6E3EA5DA4A9C9DA8D2524069E5DD98F3F5C6DED6F1DC
| With live systems, it's an operating system, built for one of the supported architectures (currently amd64 and i386). It is made from the following parts:
@@ -3710,7 +3595,6 @@
.ancestors: 1 157 0 0 158 162 0 0
.ancestors_collapsed: 1 157 158 162 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C01421947A7065DC1A18C714F4995FE1A8295413E8DA986FF4AF6B1F7699AC7F
.bullet: true
@@ -3722,7 +3606,6 @@
.ancestors: 1 157 0 0 158 162 0 0
.ancestors_collapsed: 1 157 158 162 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0189B169C4B604C51670D45555EDD22FA79565B6E54110FD756133CD6C526BF0
.bullet: true
@@ -3734,7 +3617,6 @@
.ancestors: 1 157 0 0 158 162 0 0
.ancestors_collapsed: 1 157 158 162 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C9FC96741D3D4D6709C3E79F6B9171FB92800CA12C2C904E8A942F60A42A880B
.bullet: true
@@ -3747,7 +3629,6 @@
.ancestors: 1 157 0 0 158 162 0 0
.ancestors_collapsed: 1 157 158 162 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6B099EF22840FF0CAF5D93F7AC823A29FEAD6746E586B14C221E9B3CF6EC874A
.bullet: true
@@ -3759,7 +3640,6 @@
.ancestors: 1 157 0 0 158 162 0 0
.ancestors_collapsed: 1 157 158 162 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4B830F65FE37C5335722CB60192E5BF15AF172ED9CC87B6BBCB6E3632F4BA7BB
| You can use live-build to build the system image from your specifications, set up a Linux kernel, its initrd, and a bootloader to run them, all in one medium-dependant format (ISO9660 image, disk image, etc.).
@@ -3788,7 +3668,6 @@
.ancestors: 1 157 0 0 158 170 0 0
.ancestors_collapsed: 1 157 158 170 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 35F2E6E347658AE8BA536815BE043B258E8D9EF712324CFB897C5C3C83668065
.has: links
@@ -3821,7 +3700,6 @@
.ancestors: 1 157 0 0 158 172 0 0
.ancestors_collapsed: 1 157 158 172 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 51AEF748B5BD06945FCE30432F2F57EB1668BF0BD4C851EFD31D1AE172087635
.has: links
@@ -3851,7 +3729,6 @@
.ancestors: 1 157 0 0 158 172 174 0
.ancestors_collapsed: 1 157 158 172 174 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 352A72B49764BB8B5EF09AD4EAC8C763CBE6A456F0096743D68E3E3DD069435E
| The web interface currently makes no provision to prevent the use of invalid combinations of options, and in particular, where changing an option would normally (i.e. using live-build directly) change defaults of other options listed in the web form, the web builder does not change these defaults. Most notably, if you change ⑆■┨--architectures┣■ from the default ⑆■┨i386┣■ to ⑆■┨amd64┣■, you must change the corresponding option ⑆■┨--linux-flavours┣■ from the default ⑆■┨586┣■ to ⑆■┨amd64┣■. See the ⑆■┨lb_config┣■ man page for the version of live-build installed on the web builder for more details. The version number of live-build is listed at the bottom of the web builder page.
@@ -3862,7 +3739,6 @@
.ancestors: 1 157 0 0 158 172 174 0
.ancestors_collapsed: 1 157 158 172 174 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 68BA590F160EC02CBF0514F214CDE7DFF46334B0D0A75FCB2802FD98A3C63BD2
.has: links
@@ -3874,7 +3750,6 @@
.ancestors: 1 157 0 0 158 172 174 0
.ancestors_collapsed: 1 157 158 172 174 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: F841D0992C15CA2E80368DD6B355E7C7A9553E76E50C2A00BCD95A73D55B3602
| The web builder is limited in the kinds of images it can build. This keeps it simple and efficient to use and maintain. If you would like to make customizations that are not provided for by the web interface, the rest of this manual explains how to build your own images using live-build.
@@ -3903,7 +3778,6 @@
.ancestors: 1 157 0 0 158 178 0 0
.ancestors_collapsed: 1 157 158 178 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F4337173B8C6D3D2288770F15380E96DC42AE4C251C215D3267BD01C908C874A
| Regardless of the image type, you will need to perform the same basic steps to build an image each time. As a first example, create a build directory, change to that directory and then execute the following sequence of live-build commands to create a basic ISO hybrid image containing a default live system without X.org. It is suitable for burning to CD or DVD media, and also to copy onto a USB stick.
@@ -3914,7 +3788,6 @@
.ancestors: 1 157 0 0 158 178 0 0
.ancestors_collapsed: 1 157 158 178 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2E5A4C334DE23419D1749C311379FD670A325D5002F6895FB33C10906B6EE559
| The name of the working directory is absolutely up to you, but if you take a look at the examples used throughout live-manual, it is a good idea to use a name that helps you identify the image you are working with in each directory, especially if you are working or experimenting with different image types. In this case you are going to build a default system so let's call it, for example, live-default.
@@ -3935,7 +3808,6 @@
.ancestors: 1 157 0 0 158 178 0 0
.ancestors_collapsed: 1 157 158 178 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 11243FD298964C8388063E9A66AE66C7F85AD8517B62032D3B9697AB3E6D99F2
| Then, run the ⑆■┨lb config┣■ command. This will create a “config/” hierarchy in the current directory for use by other commands:
@@ -3956,7 +3828,6 @@
.ancestors: 1 157 0 0 158 178 0 0
.ancestors_collapsed: 1 157 158 178 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 517545976DC1CCF443F5636792C52071F967FE1B6B0C6BB9B43D913A916CCFA8
.has: links
@@ -3968,7 +3839,6 @@
.ancestors: 1 157 0 0 158 178 0 0
.ancestors_collapsed: 1 157 158 178 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 48D617D82ACA1D73AE3FCFE78152115033526DEC3CEB75858E8EAD13999F7108
| Now that the “config/” hierarchy exists, build the image with the ⑆■┨lb build┣■ command:
@@ -3989,7 +3859,6 @@
.ancestors: 1 157 0 0 158 178 0 0
.ancestors_collapsed: 1 157 158 178 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A9F0139F7BE340CD4989F9AFEFA635F528F63E1AEBA4CD9E57A654FAF0CFCF71
| This process can take a while, depending on the speed of your computer and your network connection. When it is complete, there should be a ⑆■┨live-image-i386.hybrid.iso┣■ image file, ready to use, in the current directory.
@@ -4000,7 +3869,6 @@
.ancestors: 1 157 0 0 158 178 0 0
.ancestors_collapsed: 1 157 158 178 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0F0C2BD035A1729433A2BFCFEBC396250E091775E24C625D94249837B790DB6B
| ⑆*┨Note:┣* If you are building on an amd64 system the name of the resulting image will be ⑆■┨live-image-amd64.hybrid.iso┣■. Keep in mind this naming convention throughout the manual.
@@ -4030,7 +3898,6 @@
.ancestors: 1 157 0 0 158 189 0 0
.ancestors_collapsed: 1 157 158 189 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 60995B2E09520AE9A12CEC3080335BC77191DBDCBD7642C666B354BC740DD760
.has: links
@@ -4061,7 +3928,6 @@
.ancestors: 1 157 0 0 158 189 191 0
.ancestors_collapsed: 1 157 158 189 191 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E083FED62624738113652AF5C3821C816A9CEBD5E81AC6346843CF55CC77BD7A
| Burning an ISO image is easy. Just install ⑆/┨xorriso┣/ and use it from the command-line to burn the image. For instance:
@@ -4101,7 +3967,6 @@
.ancestors: 1 157 0 0 158 189 194 0
.ancestors_collapsed: 1 157 158 189 194 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 4D143C0F427BC5EF25DE818335F8858F290CC799BFAE6DCE4DC7370F431C0B3F
| ISO images prepared with ⑆■┨xorriso┣■, can be simply copied to a USB stick with the ⑆■┨cp┣■ program or an equivalent. Plug in a USB stick with a size large enough for your image file and determine which device it is, which we hereafter refer to as ⑆■┨${USBSTICK}┣■. This is the device file of your key, such as ⑆■┨/dev/sdb┣■, not a partition, such as ⑆■┨/dev/sdb1┣■! You can find the right device name by looking in ⑆■┨dmesg┣■'s output after plugging in the stick, or better yet, ⑆■┨ls -l /dev/disk/by-id┣■.
@@ -4112,7 +3977,6 @@
.ancestors: 1 157 0 0 158 189 194 0
.ancestors_collapsed: 1 157 158 189 194 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 045D95B67FBA6D6965ED7F7C9B19694DAF84FFD7502EFB46555547CD79153CA9
| Once you are certain you have the correct device name, use the ⑆■┨cp┣■ command to copy the image to the stick. ⑆*┨This will definitely overwrite any previous contents on your stick!┣*
@@ -4134,7 +3998,6 @@
.ancestors: 1 157 0 0 158 189 194 0
.ancestors_collapsed: 1 157 158 189 194 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 00D86A00EBDAAF1410D7A77B4A1D6876EBD0B60793E4165998CAF5C45AFD9B42
| ⑆*┨Note:┣* The ⑆/┨sync┣/ command is useful to ensure that all the data, which is stored in memory by the kernel while copying the image, is written to the USB stick.
@@ -4163,7 +4026,6 @@
.ancestors: 1 157 0 0 158 189 199 0
.ancestors_collapsed: 1 157 158 189 199 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 454DD76430E8CD324B405ACA42C7D52E31E2A37DBA46E499949B5F515B9F3EC3
| After copying the ⑆■┨live-image-i386.hybrid.iso┣■ to a USB stick, the first partition on the device will be filled up by the live system. To use the remaining free space, use a partitioning tool such as ⑆/┨gparted┣/ or ⑆/┨parted┣/ to create a new partition on the stick.
@@ -4184,7 +4046,6 @@
.ancestors: 1 157 0 0 158 189 199 0
.ancestors_collapsed: 1 157 158 189 199 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C63D5BBCF76C72BE0A4814A06EE0F3C9A98E56B28B2380CB9C9827D3ADD72FC1
| After the partition is created, where ⑆■┨${PARTITION}┣■ is the name of the partition, such as ⑆■┨/dev/sdb2┣■, you have to create a filesystem on it. One possible choice would be ext4.
@@ -4205,7 +4066,6 @@
.ancestors: 1 157 0 0 158 189 199 0
.ancestors_collapsed: 1 157 158 189 199 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 24BF0CDCDDBF6F63DE1D1280D859B2D02E7F7E08DB9C7AEDCDC250C4EDC04A1E
.has: links
@@ -4217,7 +4077,6 @@
.ancestors: 1 157 0 0 158 189 199 0
.ancestors_collapsed: 1 157 158 189 199 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: A0FB8DE3F7161487FCBC4FA030B877DC7C62A50D99F556BFBA183EF3D21670AF
| ⑆*┨Remember: Every time you install a new live-image-i386.hybrid.iso on the stick, all data on the stick will be lost because the partition table is overwritten by the contents of the image, so back up your extra partition first to restore again after updating the live image.┣*
@@ -4246,7 +4105,6 @@
.ancestors: 1 157 0 0 158 189 206 0
.ancestors_collapsed: 1 157 158 189 206 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C22F5CC72E7CADC435A61E50B1904D3F813F4F841F6B85B3D95556B70A803FFF
| The first time you boot your live medium, whether CD, DVD, USB key, or PXE boot, some setup in your computer's BIOS may be needed first. Since BIOSes vary greatly in features and key bindings, we cannot get into the topic in depth here. Some BIOSes provide a key to bring up a menu of boot devices at boot time, which is the easiest way if it is available on your system. Otherwise, you need to enter the BIOS configuration menu and change the boot order to place the boot device for the live system before your normal boot device.
@@ -4257,7 +4115,6 @@
.ancestors: 1 157 0 0 158 189 206 0
.ancestors_collapsed: 1 157 158 189 206 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D6BE3612D64D02AE17E1A982F7787FAB69872AAC61A48B97EE8CE99B91BFDC82
| Once you've booted the medium, you are presented with a boot menu. If you just press enter here, the system will boot using the default entry, ⑆■┨Live┣■ and default options. For more information about boot options, see the “help” entry in the menu and also the live-boot and live-config man pages found within the live system.
@@ -4268,7 +4125,6 @@
.ancestors: 1 157 0 0 158 189 206 0
.ancestors_collapsed: 1 157 158 189 206 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 9F0DDA85F5B5A466BF9F2D7F64C6F0CB92CD1BF2FE7B6C57F53EB7A8976527D7
.has: links
@@ -4299,7 +4155,6 @@
.ancestors: 1 157 0 0 158 210 0 0
.ancestors_collapsed: 1 157 158 210 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 75E771FF35B2CB609DE63C765688187402BB759F39FE1489D7B9A379D563E974
| It can be a great time-saver for the development of live images to run them in a virtual machine (VM). This is not without its caveats:
@@ -4310,7 +4165,6 @@
.ancestors: 1 157 0 0 158 210 0 0
.ancestors_collapsed: 1 157 158 210 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 944F3BB2016AD36F309A952E9899C6DD1604EBC250FEE0187AB2E004BEC5D195
.bullet: true
@@ -4322,7 +4176,6 @@
.ancestors: 1 157 0 0 158 210 0 0
.ancestors_collapsed: 1 157 158 210 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 71266B62F10948BAFDFF743603F89698D9B010F3DCAE7B0DF956D420469E2283
.bullet: true
@@ -4334,7 +4187,6 @@
.ancestors: 1 157 0 0 158 210 0 0
.ancestors_collapsed: 1 157 158 210 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AA062368C44E398D1F777B2E2D8E41D68E7FE5E554E84AE143214A452E0F74AA
.bullet: true
@@ -4346,7 +4198,6 @@
.ancestors: 1 157 0 0 158 210 0 0
.ancestors_collapsed: 1 157 158 210 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4AB65A513543458F3D009DD2FEB54910E3653D3049BF7315B548E16222FCBA71
.bullet: true
@@ -4358,7 +4209,6 @@
.ancestors: 1 157 0 0 158 210 0 0
.ancestors_collapsed: 1 157 158 210 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0A86B74BB4CB9EAA3257D011D9C5305B9B60204789A78C3B71315679397E1830
| Provided you can work within these constraints, survey the available VM software and choose one that is suitable for your needs.
@@ -4387,7 +4237,6 @@
.ancestors: 1 157 0 0 158 210 217 0
.ancestors_collapsed: 1 157 158 210 217 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 27F9A117A99CF1E88ACEB5BD4578C7C519D9A81BD8BEBF9DABFCA0F1B8003F89
| The most versatile VM in Debian is QEMU. If your processor has hardware support for virtualization, use the ⑆/┨qemu-kvm┣/ package; the ⑆/┨qemu-kvm┣/ package description briefly lists the requirements.
@@ -4398,7 +4247,6 @@
.ancestors: 1 157 0 0 158 210 217 0
.ancestors_collapsed: 1 157 158 210 217 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 5129A3F6381448796626738C2BED29B98CEFAD4276F7759967DB5B051AAF8B18
| First, install ⑆/┨qemu-kvm┣/ if your processor supports it. If not, install ⑆/┨qemu┣/, in which case the program name is ⑆■┨qemu┣■ instead of ⑆■┨kvm┣■ in the following examples. The ⑆/┨qemu-utils┣/ package is also valuable for creating virtual disk images with ⑆■┨qemu-img┣■.
@@ -4419,7 +4267,6 @@
.ancestors: 1 157 0 0 158 210 217 0
.ancestors_collapsed: 1 157 158 210 217 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: EC7F746E79723DC771021B1776AEE5092D43F673778AD8E9BAEF04C6CB5D3D97
| Booting an ISO image is simple:
@@ -4440,7 +4287,6 @@
.ancestors: 1 157 0 0 158 210 217 0
.ancestors_collapsed: 1 157 158 210 217 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 9FE152135DCE3DDF9D59FE47F57DD403AA54DB0EC2BF1948D1E5E7422B45BA91
| See the man pages for more details.
@@ -4469,7 +4315,6 @@
.ancestors: 1 157 0 0 158 210 224 0
.ancestors_collapsed: 1 157 158 210 224 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8E7BCFA157F2E2700FC7258037C186001C762963C436103F8002BEB521A205E3
| In order to test the ISO with ⑆/┨virtualbox┣/:
@@ -4491,7 +4336,6 @@
.ancestors: 1 157 0 0 158 210 224 0
.ancestors_collapsed: 1 157 158 210 224 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C53D7FD98F9BA67AC7F7BCB606461BC2D4FF914303A001DA439358E6A23C7A22
| Create a new virtual machine, change the storage settings to use ⑆■┨live-image-i386.hybrid.iso┣■ as the CD/DVD device, and start the machine.
@@ -4502,7 +4346,6 @@
.ancestors: 1 157 0 0 158 210 224 0
.ancestors_collapsed: 1 157 158 210 224 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C0C6645F51C3ED072299D29178E77AC6ED627AA57BB58CDF3F0D8E0B5C0646B6
| ⑆*┨Note:┣* For live systems containing X.org that you want to test with ⑆/┨virtualbox┣/, you may wish to include the VirtualBox X.org driver package, ⑆/┨virtualbox-guest-dkms┣/ and ⑆/┨virtualbox-guest-x11┣/, in your live-build configuration. Otherwise, the resolution is limited to 800x600.
@@ -4523,7 +4366,6 @@
.ancestors: 1 157 0 0 158 210 224 0
.ancestors_collapsed: 1 157 158 210 224 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: CEBCFF9B03324E0BA70D9D3CF4B87C753102632FD4E445506C06573BD3EAE88D
| In order to make the dkms package work, also the kernel headers for the kernel flavour used in your image need to be installed. Instead of manually listing the correct ⑆/┨linux-headers┣/ package in above created package list, the selection of the right package can be done automatically by live-build.
@@ -4562,7 +4404,6 @@
.ancestors: 1 157 0 0 158 232 0 0
.ancestors_collapsed: 1 157 158 232 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7426EB1A17A9E6CCEB61DDA3376D7274D66E672F66153BEA601D5BEA30DB949F
| Building an HDD image is similar to an ISO hybrid one in all respects except you specify ⑆■┨-b hdd┣■ and the resulting filename is ⑆■┨live-image-i386.img┣■ which cannot be burnt to optical media. It is suitable for booting from USB sticks, USB hard drives, and various other portable storage devices. Normally, an ISO hybrid image can be used for this purpose instead, but if you have a BIOS which does not handle hybrid images properly, you need an HDD image.
@@ -4573,7 +4414,6 @@
.ancestors: 1 157 0 0 158 232 0 0
.ancestors_collapsed: 1 157 158 232 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3CECCC0761A525A6B37B0A6CE5B9F905B389B35E511796BE222E26F86C2F524B
.has: links
@@ -4595,7 +4435,6 @@
.ancestors: 1 157 0 0 158 232 0 0
.ancestors_collapsed: 1 157 158 232 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E73BDBF54BDCEEA5C2B5F04511DA2E6B4C9AA317C5FC8715EF133873ACC3F0E2
| Run the ⑆■┨lb config┣■ command as before, except this time specifying the HDD image type:
@@ -4616,7 +4455,6 @@
.ancestors: 1 157 0 0 158 232 0 0
.ancestors_collapsed: 1 157 158 232 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2A73C7E53086437064C08A8611080C48B89504C6DEA74C09FD27927414E17C49
| Now build the image with the ⑆■┨lb build┣■ command:
@@ -4637,7 +4475,6 @@
.ancestors: 1 157 0 0 158 232 0 0
.ancestors_collapsed: 1 157 158 232 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 82DB0531F055D2935E326701C1C2EA1095E251E248D27A550E4AFDB8D1AD84D6
| When the build finishes, a ⑆■┨live-image-i386.img┣■ file should be present in the current directory.
@@ -4648,7 +4485,6 @@
.ancestors: 1 157 0 0 158 232 0 0
.ancestors_collapsed: 1 157 158 232 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 16D188A4C11DF3B46E6FEE44642137E4B026B6337D777C4B91EF94A874F68555
.has: links
@@ -4660,7 +4496,6 @@
.ancestors: 1 157 0 0 158 232 0 0
.ancestors_collapsed: 1 157 158 232 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6E3282FAA8AA5782F5CD2C53058E5A0EA0EB0CC876C96D3F84F2DF33B1E3436E
.has: links
@@ -4701,7 +4536,6 @@
.ancestors: 1 157 0 0 158 244 0 0
.ancestors_collapsed: 1 157 158 244 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 237B93FBF331F98226BE7800BCAF74845A596F0BE275BA4B4788C41320548964
| The following sequence of commands will create a basic netboot image containing a default live system without X.org. It is suitable for booting over the network.
@@ -4712,7 +4546,6 @@
.ancestors: 1 157 0 0 158 244 0 0
.ancestors_collapsed: 1 157 158 244 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B62F932ACE3F5CAF4A41D3963151476A414C170751F624ED39E46459BE3D0658
| ⑆*┨Note:┣* if you performed any previous examples, you will need to clean up your working directory with the ⑆■┨lb clean┣■ command:
@@ -4733,7 +4566,6 @@
.ancestors: 1 157 0 0 158 244 0 0
.ancestors_collapsed: 1 157 158 244 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 01F5B315BA926387D7540E9AB03F62EFC19EEBD6B163B1DE5B3ED8A7C861E518
| In this specific case, a ⑆■┨lb clean --binary┣■ would not be enough to clean up the necessary stages. The cause for this is that in netboot setups, a different initramfs configuration needs to be used which live-build performs automatically when building netboot images. Since the initramfs creation belongs to the chroot stage, switching to netboot in an existing build directory means to rebuild the chroot stage too. Therefore, ⑆■┨lb clean┣■ (which will remove the chroot stage, too) needs to be used.
@@ -4744,7 +4576,6 @@
.ancestors: 1 157 0 0 158 244 0 0
.ancestors_collapsed: 1 157 158 244 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 33294BF53373363348169C9E1788CF381818586B19D5E8D8FD7D1D41089F4055
| Run the ⑆■┨lb config┣■ command as follows to configure your image for netbooting:
@@ -4765,7 +4596,6 @@
.ancestors: 1 157 0 0 158 244 0 0
.ancestors_collapsed: 1 157 158 244 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DB10B917CB3930F9ABED8F33AACE0887B69C94C2CA838331CE2FBC3F46E47972
| In contrast with the ISO and HDD images, netbooting does not, itself, serve the filesystem image to the client, so the files must be served via NFS. Different network filesystems can be chosen through lb config. The ⑆■┨--net-root-path┣■ and ⑆■┨--net-root-server┣■ options specify the location and server, respectively, of the NFS server where the filesystem image will be located at boot time. Make sure these are set to suitable values for your network and server.
@@ -4776,7 +4606,6 @@
.ancestors: 1 157 0 0 158 244 0 0
.ancestors_collapsed: 1 157 158 244 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2A73C7E53086437064C08A8611080C48B89504C6DEA74C09FD27927414E17C49
| Now build the image with the ⑆■┨lb build┣■ command:
@@ -4797,7 +4626,6 @@
.ancestors: 1 157 0 0 158 244 0 0
.ancestors_collapsed: 1 157 158 244 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7E52BAF56DFA5252EF2ED782C3B34C6584AF28C7F89D752C3D0458035594469A
| In a network boot, the client runs a small piece of software which usually resides on the EPROM of the Ethernet card. This program sends a DHCP request to get an IP address and information about what to do next. Typically, the next step is getting a higher level bootloader via the TFTP protocol. That could be pxelinux, GRUB, or even boot directly to an operating system like Linux.
@@ -4808,7 +4636,6 @@
.ancestors: 1 157 0 0 158 244 0 0
.ancestors_collapsed: 1 157 158 244 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7DF246B11D92C8DF430E69774F41FEA6D2FA4D28AE4044A5534C790F8181C0FE
| For example, if you unpack the generated ⑆■┨live-image-i386.netboot.tar┣■ archive in the ⑆■┨/srv/debian-live┣■ directory, you'll find the filesystem image in ⑆■┨live/filesystem.squashfs┣■ and the kernel, initrd and pxelinux bootloader in ⑆■┨tftpboot/┣■.
@@ -4819,7 +4646,6 @@
.ancestors: 1 157 0 0 158 244 0 0
.ancestors_collapsed: 1 157 158 244 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E92C29EAB7FAA008A6020BDF8A2427542595680698D188E462087F4A94FCA2B3
| We must now configure three services on the server to enable netbooting: the DHCP server, the TFTP server and the NFS server.
@@ -4847,7 +4673,6 @@
.ancestors: 1 157 0 0 158 244 257 0
.ancestors_collapsed: 1 157 158 244 257 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: FA8B516E142F143D14A90982A63E1CD74ECDE8AE50E99E59D00E34C80F05F222
| We must configure our network's DHCP server to be sure to give an IP address to the netbooting client system, and to advertise the location of the PXE bootloader.
@@ -4858,7 +4683,6 @@
.ancestors: 1 157 0 0 158 244 257 0
.ancestors_collapsed: 1 157 158 244 257 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 862C5A535889DFB5D1BD8712C9DD541E7391F5F4CCB54AB3EAED3C00B403FC14
| Here is an example for inspiration, written for the ISC DHCP server ⑆■┨isc-dhcp-server┣■ in the ⑆■┨/etc/dhcp/dhcpd.conf┣■ configuration file:
@@ -4915,7 +4739,6 @@
.ancestors: 1 157 0 0 158 244 261 0
.ancestors_collapsed: 1 157 158 244 261 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D141EB929C1FFCC4F0E4D63E25E2CBE6BBDFCDF88D88DC91CAF056A040C3A051
| This serves the kernel and initial ramdisk to the system at run time.
@@ -4926,7 +4749,6 @@
.ancestors: 1 157 0 0 158 244 261 0
.ancestors_collapsed: 1 157 158 244 261 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8ACF327591FC421A6655F43B5AC90751CF9D20383362EC396DE888F1B265B5DB
| You should install the ⑆/┨tftpd-hpa┣/ package. It can serve all files contained inside a root directory, usually ⑆■┨/srv/tftp┣■. To let it serve files inside ⑆■┨/srv/debian-live/tftpboot┣■, run as root the following command:
@@ -4947,7 +4769,6 @@
.ancestors: 1 157 0 0 158 244 261 0
.ancestors_collapsed: 1 157 158 244 261 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8B3C784AEEAC78A7694B8DFB991A32AE45D7339DB933334D74D98A07231B1C2E
| and fill in the new tftp server directory when being asked about it.
@@ -4975,7 +4796,6 @@
.ancestors: 1 157 0 0 158 244 266 0
.ancestors_collapsed: 1 157 158 244 266 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 4C9415CC80168949ACF2CB0B110E4C4A30012CD034D3FAA5D2B2C0B0ED3F2801
| Once the guest computer has downloaded and booted a Linux kernel and loaded its initrd, it will try to mount the Live filesystem image through a NFS server.
@@ -4986,7 +4806,6 @@
.ancestors: 1 157 0 0 158 244 266 0
.ancestors_collapsed: 1 157 158 244 266 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 4DC0D4CB164217F4AF08B026B153B0D2C3F571DA3C3A7E090733A6688CA70D04
| You need to install the ⑆/┨nfs-kernel-server┣/ package.
@@ -4997,7 +4816,6 @@
.ancestors: 1 157 0 0 158 244 266 0
.ancestors_collapsed: 1 157 158 244 266 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 55AB7166A003C5D916CF6211A370E463F1464EBCCDAB944A6E47C1A45FFFF61D
| Then, make the filesystem image available through NFS by adding a line like the following to ⑆■┨/etc/exports┣■:
@@ -5018,7 +4836,6 @@
.ancestors: 1 157 0 0 158 244 266 0
.ancestors_collapsed: 1 157 158 244 266 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 13E65DB8B218B1EFFA3172B0F361E3E07BB8BCED473564AE00B677F06CE3FB22
| and tell the NFS server about this new export with the following command:
@@ -5039,7 +4856,6 @@
.ancestors: 1 157 0 0 158 244 266 0
.ancestors_collapsed: 1 157 158 244 266 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 90BB714099BC7E81FE2F308E7980D21904B405C984E94508562E4BF501D78C3E
.has: links
@@ -5069,7 +4885,6 @@
.ancestors: 1 157 0 0 158 244 274 0
.ancestors_collapsed: 1 157 158 244 274 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7A3F0297490FE18FE0E0631A7C53C3AA7819FA5477E5E93820D4ABAEBD4F2A0E
| Netboot image creation is made easy with live-build, but testing the images on physical machines can be really time consuming.
@@ -5080,7 +4895,6 @@
.ancestors: 1 157 0 0 158 244 274 0
.ancestors_collapsed: 1 157 158 244 274 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6B530583274E2D837213A225BEFDF182AEC73EEFDD5149A70D5E98DA4528491E
| To make our life easier, we can use virtualization.
@@ -5108,7 +4922,6 @@
.ancestors: 1 157 0 0 158 244 277 0
.ancestors_collapsed: 1 157 158 244 277 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 92FBEC9536FF4CAE8FEDED45886CEE81FE568551D2DB53C05B367B56A0EF4FD2
.bullet: true
@@ -5120,7 +4933,6 @@
.ancestors: 1 157 0 0 158 244 277 0
.ancestors_collapsed: 1 157 158 244 277 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E9EBFD6F3DBCF7F8884E3329B522C4E54D52EF19FD60F6498F78D315D669D4A2
| Edit ⑆■┨/etc/qemu-ifup┣■:
@@ -5148,7 +4960,6 @@
.ancestors: 1 157 0 0 158 244 277 0
.ancestors_collapsed: 1 157 158 244 277 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8F96D398559DDFADB88D3B6AF91B9E012EE8B2102B1BE4B949EEE6381C0D29C3
| Get, or build a ⑆■┨grub-floppy-netboot┣■.
@@ -5159,7 +4970,6 @@
.ancestors: 1 157 0 0 158 244 277 0
.ancestors_collapsed: 1 157 158 244 277 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BD7D8CA6059A5729C03DD6C9C63EB42250C64FEBB5AD7D73F989E421EB5954EF
| Launch ⑆■┨qemu┣■ with “⑆■┨-net nic,vlan=0 -net tap,vlan=0,ifname=tun0┣■”
@@ -5189,7 +4999,6 @@
.ancestors: 1 157 0 0 158 283 0 0
.ancestors_collapsed: 1 157 158 283 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 14609B21E4014FFD47C12B94B627969040D8370043FCF876CB1174C081853BB7
| Webbooting is a convenient way of retrieving and booting live systems using the internet as a means. The requirements for webbooting are very few. On the one hand, you need a medium with a bootloader, an initial ramdisk and a kernel. On the other hand, a web server to store the squashfs files which contain the filesystem.
@@ -5217,7 +5026,6 @@
.ancestors: 1 157 0 0 158 283 285 0
.ancestors_collapsed: 1 157 158 283 285 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 188A19F14C6CE8880E6026188F8ED5698E85D130E4128D72552EA344D7F87E0A
.has: links
@@ -5230,7 +5038,6 @@
.ancestors: 1 157 0 0 158 283 285 0
.ancestors_collapsed: 1 157 158 283 285 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E820A71B7CA13AC2413FC60EADC42F2B9565775DBEBEF45ABD25BF8C7AED1202
| It is also possible to extract those files from an already existing iso image. In order to achieve that, loopback mount the image as follows:
@@ -5251,7 +5058,6 @@
.ancestors: 1 157 0 0 158 283 285 0
.ancestors_collapsed: 1 157 158 283 285 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 15E6986ADD3B1D3B443A5C2441BC77049C91FF360AAA36BEF683901842C36C51
| The files are to be found under the ⑆■┨live/┣■ directory. In this specific case, it would be ⑆■┨/mnt/live/┣■. This method has the disadvantage that you need to be root to be able to mount the image. However, it has the advantage that it is easily scriptable and thus, easily automatized.
@@ -5262,7 +5068,6 @@
.ancestors: 1 157 0 0 158 283 285 0
.ancestors_collapsed: 1 157 158 283 285 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: FD19B1186645F03C097F4541B113378E52E499B73C82F1F91C5D71AD979E65DF
| But undoubtedly, the easiest way of extracting the files from an iso image and uploading it to the web server at the same time, is using the midnight commander or ⑆/┨mc┣/. If you have the ⑆/┨genisoimage┣/ package installed, the two-pane file manager allows you to browse the contents of an iso file in one pane and upload the files via ftp in the other pane. Even though this method requires manual work, it does not require root privileges.
@@ -5290,7 +5095,6 @@
.ancestors: 1 157 0 0 158 283 291 0
.ancestors_collapsed: 1 157 158 283 291 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 95F280FE1B6C12A5CABEAE07B8236C4C968E49BCC93011E0089F4E4F5E7D384E
| While some users will prefer virtualization to test webbooting, we refer to real hardware here to match the following possible use case which should only be considered as an example.
@@ -5301,7 +5105,6 @@
.ancestors: 1 157 0 0 158 283 291 0
.ancestors_collapsed: 1 157 158 283 291 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 76147ACC53EA53DA945B974D4529BC9B2D479D66155DBFC8F6FB317D55A19E2B
| In order to boot a webboot image it is enough to have the components mentioned above, i.e. ⑆■┨vmlinuz┣■ and ⑆■┨initrd.img┣■ in a usb stick inside a directory named ⑆■┨live/┣■ and install syslinux as bootloader. Then boot from the usb stick and type ⑆■┨fetch=URL/PATH/TO/FILE┣■ at the boot options. live-boot will retrieve the squashfs file and store it into ram. This way, it is possible to use the downloaded compressed filesystem as a regular live system. For example:
@@ -5322,7 +5125,6 @@
.ancestors: 1 157 0 0 158 283 291 0
.ancestors_collapsed: 1 157 158 283 291 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: AD7BE22871BB0695B33D9387FD290965CA234A8A604A4A6E0892265C5C69BC89
| ⑆*┨Use case:┣* You have a web server in which you have stored two squashfs files, one which contains a full desktop, like for example gnome, and a standard one. If you need a graphical environment for one machine, you can plug your usb stick in and webboot the gnome image. If you need one of the tools included in the second type of image, perhaps for another machine, you can webboot the standard one.
@@ -5377,7 +5179,6 @@
.ancestors: 1 296 0 0 297 0 0 0
.ancestors_collapsed: 1 296 297 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 454BD46F79A7347AC97C59C927CE5AE8EB939BEC4292EF49C697567C8BEA8C7D
| This chapter contains an overview of the three main tools used in building live systems: live-build, live-boot and live-config.
@@ -5407,7 +5208,6 @@
.ancestors: 1 296 0 0 297 299 0 0
.ancestors_collapsed: 1 296 297 299 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: ED4020E5F366509CB6A7B81D391F80CFC91291A0BB33E3BA2C74B36CE7089BFD
| live-build is a collection of scripts to build live systems. These scripts are also referred to as “commands”.
@@ -5418,7 +5218,6 @@
.ancestors: 1 296 0 0 297 299 0 0
.ancestors_collapsed: 1 296 297 299 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E03C8E784D71B3D63BBFEFFF87B6FA842EE47A02A00D7444104C96E2631D989D
| The idea behind live-build is to be a framework that uses a configuration directory to completely automate and customize all aspects of building a Live image.
@@ -5429,7 +5228,6 @@
.ancestors: 1 296 0 0 297 299 0 0
.ancestors_collapsed: 1 296 297 299 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E5F8C08B5D62DDD0F3C81AAB61FF725A74F55EAA06688092C303F78CB6256C6A
| Many concepts are similar to those used to build Debian packages with ⑆/┨debhelper┣/:
@@ -5440,7 +5238,6 @@
.ancestors: 1 296 0 0 297 299 0 0
.ancestors_collapsed: 1 296 297 299 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 930C0E1EDCF386C7BAA87FECECF09E63DDC895D1320B38DD85C752C98BEC4E07
.bullet: true
@@ -5452,7 +5249,6 @@
.ancestors: 1 296 0 0 297 299 0 0
.ancestors_collapsed: 1 296 297 299 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: ABD73BFA59EF1886C65BEB6DBAB266E89C60DAE00184205BC8F41135F84F221B
.bullet: true
@@ -5464,7 +5260,6 @@
.ancestors: 1 296 0 0 297 299 0 0
.ancestors_collapsed: 1 296 297 299 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A69D00B274EAA6857F84D0F6EF4EEB55A84DF6FF8B963F97B2ADBE005A074AC6
| Unlike ⑆/┨debhelper┣/, live-build provides the tools to generate a skeleton configuration directory. This could be considered to be similar to tools such as ⑆/┨dh-make┣/. For more information about these tools, read on, since the remainder of this section discuses the four most important commands. Note that the preceding ⑆■┨lb┣■ is a generic wrapper for live-build commands.
@@ -5475,7 +5270,6 @@
.ancestors: 1 296 0 0 297 299 0 0
.ancestors_collapsed: 1 296 297 299 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 64093EB7D807A8150A63EBD299F5437230E44A0A6C6E741584790E4E272F2959
.bullet: true
@@ -5488,7 +5282,6 @@
.ancestors: 1 296 0 0 297 299 0 0
.ancestors_collapsed: 1 296 297 299 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 525129AA404B81EED7F10C08E67D52C22C3AE7C2FC8B98D4A6C2FEC5FCE6C091
.bullet: true
@@ -5501,7 +5294,6 @@
.ancestors: 1 296 0 0 297 299 0 0
.ancestors_collapsed: 1 296 297 299 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DE681A33B969767A57A736D5078C7247EF88B45BC304257F2C1A27873136AFE2
.bullet: true
@@ -5532,7 +5324,6 @@
.ancestors: 1 296 0 0 297 299 309 0
.ancestors_collapsed: 1 296 297 299 309 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 446C0E4CF1EF38815CDA44651E27BBD3BB865FD2CE937F0CE65CAA845DD29435
.has: links
@@ -5544,7 +5335,6 @@
.ancestors: 1 296 0 0 297 299 309 0
.ancestors_collapsed: 1 296 297 299 309 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 697FAEA02D1A931E0DB8CD16C2BFC864E5E679F1B134E56325AB020D98AFB3AA
| Issuing ⑆■┨lb config┣■ without any arguments creates the ⑆■┨config/┣■ subdirectory which is populated with some default settings in configuration files, and two skeleton trees named ⑆■┨auto/┣■ and ⑆■┨local/┣■.
@@ -5568,7 +5358,6 @@
.ancestors: 1 296 0 0 297 299 309 0
.ancestors_collapsed: 1 296 297 299 309 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: F782CB88C3A54269FA96B9A8C30377D80CD5C498FBB682DAF837321997332293
.has: links
@@ -5580,7 +5369,6 @@
.ancestors: 1 296 0 0 297 299 309 0
.ancestors_collapsed: 1 296 297 299 309 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 50D6971989CAE23E0CC8C63D18AAAC44C3FC45D6DD78D8232FB7582C5B313066
| Normally, you will want to specify some options. For example, to specify which package manager to use while building the image:
@@ -5601,7 +5389,6 @@
.ancestors: 1 296 0 0 297 299 309 0
.ancestors_collapsed: 1 296 297 299 309 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 556E18B47F8EB61428491224BF06432184485EFCE81ACB8171B2DB820B68C5FB
| It is possible to specify many options, such as:
@@ -5622,7 +5409,6 @@
.ancestors: 1 296 0 0 297 299 309 0
.ancestors_collapsed: 1 296 297 299 309 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 835FA28F750F7249F78DC9B88733CA9424E995730D4EFC1B087909A53DCDF0EE
| A full list of options is available in the ⑆■┨lb_config┣■ man page.
@@ -5651,7 +5437,6 @@
.ancestors: 1 296 0 0 297 299 319 0
.ancestors_collapsed: 1 296 297 299 319 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B922CB07332FE5539A94468631992B6499DE1FA880AE7F303DBD4F3E4864D55C
| The ⑆■┨lb build┣■ command reads in your configuration from the ⑆■┨config/┣■ directory. It then runs the lower level commands needed to build your Live system.
@@ -5680,7 +5465,6 @@
.ancestors: 1 296 0 0 297 299 321 0
.ancestors_collapsed: 1 296 297 299 321 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BCC03699E7A989C088464F41973D849407A1863E1B3F6FAF4AD0FD56B0A9C3E4
| It is the job of the ⑆■┨lb clean┣■ command to remove various parts of a build so subsequent builds can start from a clean state. By default, ⑆■┨chroot┣■, ⑆■┨binary┣■ and ⑆■┨source┣■ stages are cleaned, but the cache is left intact. Also, individual stages can be cleaned. For example, if you have made changes that only affect the binary stage, use ⑆■┨lb clean --binary┣■ prior to building a new binary. If your changes invalidate the bootstrap and/or package caches, e.g. changes to ⑆■┨--mode┣■, ⑆■┨--architecture┣■, or ⑆■┨--bootstrap┣■, you must use ⑆■┨lb clean --purge┣■. See the ⑆■┨lb_clean┣■ man page for a full list of options.
@@ -5709,7 +5493,6 @@
.ancestors: 1 296 0 0 297 323 0 0
.ancestors_collapsed: 1 296 297 323 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1E34A0B9224DB2E97FB023FA8B6A1CA6E99A2023316D5A4990F6089E1D5694C9
| live-boot is a collection of scripts providing hooks for the ⑆/┨initramfs-tools┣/, used to generate an initramfs capable of booting live systems, such as those created by live-build. This includes the live system ISOs, netboot tarballs, and USB stick images.
@@ -5720,7 +5503,6 @@
.ancestors: 1 296 0 0 297 323 0 0
.ancestors_collapsed: 1 296 297 323 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 89E24D8AD2A79845B361DDDF08708790E74410DFD9671CA6483E0AD87426E993
| At boot time it will look for read-only media containing a ⑆■┨/live/┣■ directory where a root filesystem (often a compressed filesystem image like squashfs) is stored. If found, it will create a writable environment, using aufs, for Debian like systems to boot from.
@@ -5731,7 +5513,6 @@
.ancestors: 1 296 0 0 297 323 0 0
.ancestors_collapsed: 1 296 297 323 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4081C5D1ED922A89DA6BE2A0D720226941F6372C3BD7670693E4566918B10D6A
.has: links
@@ -5762,7 +5543,6 @@
.ancestors: 1 296 0 0 297 327 0 0
.ancestors_collapsed: 1 296 297 327 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 670DA3A76E8F4282764CBF06590B67C10E4D557979A6C4D586FA936AF02BA126
| live-config consists of the scripts that run at boot time after live-boot to configure the live system automatically. It handles such tasks as setting the hostname, locales and timezone, creating the live user, inhibiting cron jobs and performing autologin of the live user.
@@ -5816,7 +5596,6 @@
.ancestors: 1 329 0 0 330 0 0 0
.ancestors_collapsed: 1 329 330 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 4B430C5730723D5B816AF3313F632C541A5AD9C57EA56AC1E6ED1EE0AACCF106
| This chapter explains how to manage a live configuration from initial creation, through successive revisions and successive releases of both the live-build software and the live image itself.
@@ -5845,7 +5624,6 @@
.ancestors: 1 329 0 0 330 332 0 0
.ancestors_collapsed: 1 329 330 332 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 785B27B0A8AC5D4285067869D4EB46748E3CFBCDB6B57718A347C2026204F608
| Live configurations rarely are perfect on the first try. It may be fine to pass ⑆■┨lb config┣■ options from the command-line to perform a single build, but it is more typical to revise those options and build again until you are satisfied. To support these changes, you will need auto scripts which ensure your configuration is kept in a consistent state.
@@ -5873,7 +5651,6 @@
.ancestors: 1 329 0 0 330 332 334 0
.ancestors_collapsed: 1 329 330 332 334 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 54B879A3FC1A84739423622E0F407502C7250CE646E275208C848D15CB53AFFF
| The ⑆■┨lb config┣■ command stores the options you pass to it in ⑆■┨config/*┣■ files along with many other options set to default values. If you run ⑆■┨lb config┣■ again, it will not reset any option that was defaulted based on your initial options. So, for example, if you run ⑆■┨lb config┣■ again with a new value for ⑆■┨--binary-images┣■, any dependent options that were defaulted for the old image type may no longer work with the new ones. Nor are these files intended to be read or edited. They store values for over a hundred options, so nobody, let alone yourself, will be able to see in these which options you actually specified. And finally, if you run ⑆■┨lb config┣■, then upgrade live-build and it happens to rename an option, ⑆■┨config/*┣■ would still contain variables named after the old option that are no longer valid.
@@ -5884,7 +5661,6 @@
.ancestors: 1 329 0 0 330 332 334 0
.ancestors_collapsed: 1 329 330 332 334 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 5C768057B2B169249385CB61255724C1F49065A2D4D17297CC64F74FD744A3C4
| For all these reasons, ⑆■┨auto/*┣■ scripts will make your life easier. They are simple wrappers to the ⑆■┨lb config┣■, ⑆■┨lb build┣■ and ⑆■┨lb clean┣■ commands that are designed to help you manage your configuration. The ⑆■┨auto/config┣■ script stores your ⑆■┨lb config┣■ command with all desired options, the ⑆■┨auto/clean┣■ script removes the files containing configuration variable values, and the ⑆■┨auto/build┣■ script keeps a ⑆■┨build.log┣■ of each build. Each of these scripts is run automatically every time you run the corresponding ⑆■┨lb┣■ command. By using these scripts, your configuration is easier to read and is kept internally consistent from one revision to the next. Also, it will be much easier for you identify and fix options which need to change when you upgrade live-build after reading the updated documentation.
@@ -5912,7 +5688,6 @@
.ancestors: 1 329 0 0 330 332 337 0
.ancestors_collapsed: 1 329 330 332 337 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: ED8BA313ECACB7B76AFAFE0D25F0989D5D679324055E215F143492320B762E2E
| For your convenience, live-build comes with example auto shell scripts to copy and edit. Start a new, default configuration, then copy the examples into it:
@@ -5935,7 +5710,6 @@
.ancestors: 1 329 0 0 330 332 337 0
.ancestors_collapsed: 1 329 330 332 337 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 008D98146BFFC11A46FD312C077E8B03EA06EA1A966C0584AF392E5CE1AC3CB3
| Edit ⑆■┨auto/config┣■, adding any options as you see fit. For instance:
@@ -5963,7 +5737,6 @@
.ancestors: 1 329 0 0 330 332 337 0
.ancestors_collapsed: 1 329 330 332 337 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 038F1936E614025D45B3F4B32485AEB566F737073CA498AD10AA2969A7BF9B44
| Now, each time you use ⑆■┨lb config┣■, ⑆■┨auto/config┣■ will reset the configuration based on these options. When you want to make changes to them, edit the options in this file instead of passing them to ⑆■┨lb config┣■. When you use ⑆■┨lb clean┣■, ⑆■┨auto/clean┣■ will clean up the ⑆■┨config/*┣■ files along with any other build products. And finally, when you use ⑆■┨lb build┣■, a log of the build will be written by ⑆■┨auto/build┣■ in ⑆■┨build.log┣■.
@@ -5974,7 +5747,6 @@
.ancestors: 1 329 0 0 330 332 337 0
.ancestors_collapsed: 1 329 330 332 337 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 637A8B21F5EDB6BE3FA18BA0B427C21E60157A3A687ED620F0F755D20A3D0E1A
| ⑆*┨Note:┣* A special ⑆■┨noauto┣■ parameter is used here to suppress another call to ⑆■┨auto/config┣■, thereby preventing infinite recursion. Make sure you don't accidentally remove it when making edits. Also, take care to ensure when you split the ⑆■┨lb config┣■ command across multiple lines for readability, as shown in the example above, that you don't forget the backslash (\) at the end of each line that continues to the next.
@@ -6003,7 +5775,6 @@
.ancestors: 1 329 0 0 330 344 0 0
.ancestors_collapsed: 1 329 330 344 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 898D14A6C785BAB469F0FB898156F99F9514742368809B1C5AD6139014C95B1E
.has: links
@@ -6016,7 +5787,6 @@
.ancestors: 1 329 0 0 330 344 0 0
.ancestors_collapsed: 1 329 330 344 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9A88700EF2FA0017F64DD07A5D41678E265620CD173F19E77FD0027A352FB35A
| For example, to build a standard image, use the ⑆■┨live-images┣■ repository as follows:
@@ -6039,7 +5809,6 @@
.ancestors: 1 329 0 0 330 344 0 0
.ancestors_collapsed: 1 329 330 344 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 26FC7B9B484B9DC1A262A7AD8A7B7F25C023541418405E8F0C7287A2211D25BC
| Edit ⑆■┨auto/config┣■ and any other things you need in the ⑆■┨config┣■ tree to suit your needs. For example, the unofficial non-free prebuilt images are made by simply adding ⑆■┨--archive-areas “main contrib non-free”┣■.
@@ -6050,7 +5819,6 @@
.ancestors: 1 329 0 0 330 344 0 0
.ancestors_collapsed: 1 329 330 344 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 403CF798EC71814FC77771E03A2FA2659C71897FCB50AFF4693F33763E4B2227
| You may optionally define a shortcut in your Git configuration by adding the following to your ⑆■┨${HOME}/.gitconfig┣■:
@@ -6072,7 +5840,6 @@
.ancestors: 1 329 0 0 330 344 0 0
.ancestors_collapsed: 1 329 330 344 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 487CD3B47660A2E5CA1E95478B9F056AC12E053563D89CFAE4DFB870D8EE3207
| This enables you to use ⑆■┨lso:┣■ anywhere you need to specify the address of a ⑆■┨live-systems.org┣■ git repository. If you also drop the optional ⑆■┨.git┣■ suffix, starting a new image using this configuration is as easy as:
@@ -6093,7 +5860,6 @@
.ancestors: 1 329 0 0 330 344 0 0
.ancestors_collapsed: 1 329 330 344 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4B72F653A96FED865A6130B1BFE13E6BDFB39D44C0C634508EA02B614E0B89E7
| Cloning the entire ⑆■┨live-images┣■ repository pulls the configurations used for several images. If you feel like building a different image after you have finished with the first one, change to another directory and again and optionally, make any changes to suit your needs.
@@ -6104,7 +5870,6 @@
.ancestors: 1 329 0 0 330 344 0 0
.ancestors_collapsed: 1 329 330 344 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A6A287CF848AEC3360B1825C2374D66648AF81A5C13588C0F024B8A3435B05D9
| In any case, remember that every time you will have to build the image as superuser: ⑆■┨lb build┣■
@@ -6158,7 +5923,6 @@
.ancestors: 1 355 0 0 356 0 0 0
.ancestors_collapsed: 1 355 356 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: F347967258FB6A8D53C53D6324A474A89DC76F2973BEECD82820F0143C27E1DE
| This chapter gives an overview of the various ways in which you may customize a live system.
@@ -6186,7 +5950,6 @@
.ancestors: 1 355 0 0 356 358 0 0
.ancestors_collapsed: 1 355 356 358 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C657BB102B9E506DB89C555EB0C16A0015CF0CA5FED42CDCB5C117D584039BD5
.has: links
@@ -6198,7 +5961,6 @@
.ancestors: 1 355 0 0 356 358 0 0
.ancestors_collapsed: 1 355 356 358 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AFA78F0F71B65981D235793AB9D2821CCCBECBDEDBE138C4D0D5517B4971D519
| Build-time configuration options are described in the ⑆■┨lb config┣■ man page. Boot-time options are described in the man pages for live-boot and live-config. Although the live-boot and live-config packages are installed within the live system you are building, it is recommended that you also install them on your build system for easy reference when you are working on your configuration. It is safe to do so, as none of the scripts contained within them are executed unless the system is configured as a live system.
@@ -6227,7 +5989,6 @@
.ancestors: 1 355 0 0 356 361 0 0
.ancestors_collapsed: 1 355 356 361 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 81E51D0147556104C42F0A999498B280C711F27248F5E7B723420D1DB7786B10
| The build process is divided into stages, with various customizations applied in sequence in each. The first stage to run is the ⑆*┨bootstrap┣* stage. This is the initial phase of populating the chroot directory with packages to make a barebones Debian system. This is followed by the ⑆*┨chroot┣* stage, which completes the construction of chroot directory, populating it with all of the packages listed in the configuration, along with any other materials. Most customization of content occurs in this stage. The final stage of preparing the live image is the ⑆*┨binary┣* stage, which builds a bootable image, using the contents of the chroot directory to construct the root filesystem for the Live system, and including the installer and any other additional material on the target medium outside of the Live system's filesystem. After the live image is built, if enabled, the source tarball is built in the ⑆*┨source┣* stage.
@@ -6238,7 +5999,6 @@
.ancestors: 1 355 0 0 356 361 0 0
.ancestors_collapsed: 1 355 356 361 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 83AFF944B24B3FE81F647CA71643978DD3407F8863759D64817C62EA458A5FF4
| Within each of these stages, there is a particular sequence in which commands are applied. These are arranged in such a way as to ensure customizations can be layered in a reasonable fashion. For example, within the ⑆*┨chroot┣* stage, preseeds are applied before any packages are installed, packages are installed before any locally included files are copied, and hooks are run later, after all of the materials are in place.
@@ -6266,7 +6026,6 @@
.ancestors: 1 355 0 0 356 364 0 0
.ancestors_collapsed: 1 355 356 364 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 90FDECC5489E65B0A06CDD0F74951343DD59E06892FD47741487F5DA571ADD4A
| Although ⑆■┨lb config┣■ creates a skeletal configuration in the ⑆■┨config/┣■ directory, to accomplish your goals, you may need to provide additional files in subdirectories of ⑆■┨config/┣■. Depending on where the files are stored in the configuration, they may be copied into the live system's filesystem or into the binary image filesystem, or may provide build-time configurations of the system that would be cumbersome to pass as command-line options. You may include things such as custom lists of packages, custom artwork, or hook scripts to run either at build time or at boot time, boosting the already considerable flexibility of debian-live with code of your own.
@@ -6294,7 +6053,6 @@
.ancestors: 1 355 0 0 356 366 0 0
.ancestors_collapsed: 1 355 356 366 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 370915ACDFCD128F1D7F1DFE2288ADAB77DF47D0418C292605EE95C4A88F947D
.has: links
@@ -6371,7 +6129,6 @@
.ancestors: 1 368 0 0 369 0 0 0
.ancestors_collapsed: 1 368 369 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 8860DBE2E7B9AA68357BD54B699B95AB9F1E9DDA851A8DB254DE596F50E3476F
| Perhaps the most basic customization of a live system is the selection of packages to be included in the image. This chapter guides you through the various build-time options to customize live-build's installation of packages. The broadest choices influencing which packages are available to install in the image are the distribution and archive areas. To ensure decent download speeds, you should choose a nearby distribution mirror. You can also add your own repositories for backports, experimental or custom packages, or include packages directly as files. You can define lists of packages, including metapackages which will install many related packages at once, such as packages for a particular desktop or language. Finally, a number of options give some control over ⑆/┨apt┣/, or if you prefer, ⑆/┨aptitude┣/, at build time when packages are installed. You may find these handy if you use a proxy, want to disable installation of recommended packages to save space, or need to control which versions of packages are installed via APT pinning, to name a few possibilities.
@@ -6417,7 +6174,6 @@
.ancestors: 1 368 0 0 369 371 372 0
.ancestors_collapsed: 1 368 369 371 372 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 3E5339303E6A04DC655ACD1AEE14762B99AA3D8B65008B1F83614A19239B2C9A
.has: links
@@ -6439,7 +6195,6 @@
.ancestors: 1 368 0 0 369 371 372 0
.ancestors_collapsed: 1 368 369 371 372 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: FA88B7E1520E555AB02E961652CAE4D46ADCCD45898597DA204D5BA27A89D4F9
| Within the distribution archive, archive areas are major divisions of the archive. In Debian, these are ⑆■┨main┣■, ⑆■┨contrib┣■ and ⑆■┨non-free┣■. Only ⑆■┨main┣■ contains software that is part of the Debian distribution, hence that is the default. One or more values may be specified, e.g.
@@ -6460,7 +6215,6 @@
.ancestors: 1 368 0 0 369 371 372 0
.ancestors_collapsed: 1 368 369 371 372 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6F4AC4F36F28A01C973BE0F7B7AF1545E53927D96E23696CF7D0BE19DF8682B8
| Experimental support is available for some Debian derivatives through a ⑆■┨--mode┣■ option. By default, this option is set to ⑆■┨debian┣■ only if you are building on a Debian or on an unknown system. If ⑆■┨lb config┣■ is invoked on any of the supported derivatives, it will default to create an image of that derivative. If ⑆■┨lb config┣■ is run in e.g. ⑆■┨ubuntu┣■ mode, the distribution names and archive areas for the specified derivative are supported instead of the ones for Debian. The mode also modifies live-build behaviour to suit the derivatives.
@@ -6471,7 +6225,6 @@
.ancestors: 1 368 0 0 369 371 372 0
.ancestors_collapsed: 1 368 369 371 372 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7DBBC464D19AD8237D26C37B386D56307E5EAF1758109940EF88F3BE02F4F0BD
| ⑆*┨Note:┣* The projects for whom these modes were added are primarily responsible for supporting users of these options. The ${project}, in turn, provides development support on a best-effort basis only, based on feedback from the derivative projects as we do not develop or support these derivatives ourselves.
@@ -6499,7 +6252,6 @@
.ancestors: 1 368 0 0 369 371 379 0
.ancestors_collapsed: 1 368 369 371 379 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BB489DC45E183F9BD5B81421CBC500F413B85B6E52D813EF875CC6F7C39F6B36
.has: links
@@ -6529,7 +6281,6 @@
.ancestors: 1 368 0 0 369 371 381 0
.ancestors_collapsed: 1 368 369 371 381 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1025CBB216E2A468E8542BC313B7E45A0EDB628D31F4197B25F5CF544DB1E44E
| To set the distribution mirrors used at build time to point at a local mirror, it is sufficient to set ⑆■┨--mirror-bootstrap┣■ and ⑆■┨--mirror-chroot-security┣■ as follows.
@@ -6551,7 +6302,6 @@
.ancestors: 1 368 0 0 369 371 381 0
.ancestors_collapsed: 1 368 369 371 381 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E01A0567C6A2D6417D7A034CDF66306C30367FC856C18967BDEA3DDA429F7C82
| The chroot mirror, specified by ⑆■┨--mirror-chroot┣■, defaults to the ⑆■┨--mirror-bootstrap┣■ value.
@@ -6579,7 +6329,6 @@
.ancestors: 1 368 0 0 369 371 385 0
.ancestors_collapsed: 1 368 369 371 385 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 9857F153F27081C6D306FA12613BF89FCA20154E5F9573DAA457C39E427DEB09
| The ⑆■┨--mirror-binary*┣■ options govern the distribution mirrors placed in the binary image. These may be used to install additional packages while running the live system. The defaults employ ⑆■┨httpredir.debian.org┣■, a service that chooses a geographically close mirror based, among other things, on the user's IP family and the availability of the mirrors. This is a suitable choice when you cannot predict which mirror will be best for all of your users. Or you may specify your own values as shown in the example below. An image built from this configuration would only be suitable for users on a network where “⑆■┨mirror┣■” is reachable.
@@ -6620,7 +6369,6 @@
.ancestors: 1 368 0 0 369 371 388 0
.ancestors_collapsed: 1 368 369 371 388 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 70C3A14E35AC4B5AF239649A2EFFC9191634CF9881077010230BE6C9907A0442
| You may add more repositories, broadening your package choices beyond what is available in your target distribution. These may be, for example, for backports, experimental or custom packages. To configure additional repositories, create ⑆■┨config/archives/your-repository.list.chroot┣■, and/or ⑆■┨config/archives/your-repository.list.binary┣■ files. As with the ⑆■┨--mirror-*┣■ options, these govern the repositories used in the ⑆*┨chroot┣* stage when building the image, and in the ⑆*┨binary┣* stage, i.e. for use when running the live system.
@@ -6631,7 +6379,6 @@
.ancestors: 1 368 0 0 369 371 388 0
.ancestors_collapsed: 1 368 369 371 388 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: EC07426074EC752C1146129A18E52440D31099A07D4C83C26614410FED93D053
| For example, ⑆■┨config/archives/live.list.chroot┣■ allows you to install packages from the debian-live snapshot repository at live system build time.
@@ -6652,7 +6399,6 @@
.ancestors: 1 368 0 0 369 371 388 0
.ancestors_collapsed: 1 368 369 371 388 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 43F835EF4C97E92BCC7FBABD74916A2F1B75280695ADE3CDD575BAB6FA492F7B
| If you add the same line to ⑆■┨config/archives/live.list.binary┣■, the repository will be added to your live system's ⑆■┨/etc/apt/sources.list.d/┣■ directory.
@@ -6663,7 +6409,6 @@
.ancestors: 1 368 0 0 369 371 388 0
.ancestors_collapsed: 1 368 369 371 388 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: AA91F02DCD1C7E8EE806DB8CB740DB755999C5FE314EC7120DF4A242551C82A4
| If such files exist, they will be picked up automatically.
@@ -6674,7 +6419,6 @@
.ancestors: 1 368 0 0 369 371 388 0
.ancestors_collapsed: 1 368 369 371 388 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: ACD4DADD068ED9210A05EAC85381156257E91BD9FDA43D55629B964DE3D23EFB
| You should also put the GPG key used to sign the repository into ⑆■┨config/archives/your-repository.key.{binary,chroot}┣■ files.
@@ -6685,7 +6429,6 @@
.ancestors: 1 368 0 0 369 371 388 0
.ancestors_collapsed: 1 368 369 371 388 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6F9548EAEFBDB1E36630C9AEE67D21D20265A7BAB5AB632CFB0AE42C4DD69894
| Should you need custom APT pinning, such APT preferences snippets can be placed in ⑆■┨config/archives/your-repository.pref.{binary,chroot}┣■ files and will be automatically added to your live system's ⑆■┨/etc/apt/preferences.d/┣■ directory.
@@ -6715,7 +6458,6 @@
.ancestors: 1 368 0 0 369 396 0 0
.ancestors_collapsed: 1 368 369 396 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 22B1AC8E330A8AC97BDEBFA0A35FF6966737E7805C51A79E9E92AAD121FECECD
| There are a number of ways to choose which packages live-build will install in your image, covering a variety of different needs. You can simply name individual packages to install in a package list. You can also use metapackages in those lists, or select them using package control file fields. And finally, you may place package files in your ⑆■┨config/┣■ tree, which is well suited to testing of new or experimental packages before they are available from a repository.
@@ -6744,7 +6486,6 @@
.ancestors: 1 368 0 0 369 396 398 0
.ancestors_collapsed: 1 368 369 396 398 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7FCE228FBC58CACEBDAB8E642D4F9DB377735CEE811A7DA587FE6CC504270A67
| Package lists are a powerful way of expressing which packages should be installed. The list syntax supports conditional sections which makes it easy to build lists and adapt them for use in multiple configurations. Package names may also be injected into the list using shell helpers at build time.
@@ -6755,7 +6496,6 @@
.ancestors: 1 368 0 0 369 396 398 0
.ancestors_collapsed: 1 368 369 396 398 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 422213280B7BA4964D04B1BC9ED36648C57F072DBC9DB66FAE385F1DB165D8FE
.has: links
@@ -6785,7 +6525,6 @@
.ancestors: 1 368 0 0 369 396 401 0
.ancestors_collapsed: 1 368 369 396 401 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1B5E159237FF1909A65D56CC7FAA4E936051C8792BB47D05373F549083095C69
| The simplest way to populate your package list is to use a task metapackage maintained by your distribution. For example:
@@ -6807,7 +6546,6 @@
.ancestors: 1 368 0 0 369 396 401 0
.ancestors_collapsed: 1 368 369 396 401 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C85BA3C176046CE892C66B3989F0D123812D77B3A0F40002D83A65786AB801EA
| This supercedes the older predefined list method supported in ⑆■┨live-build┣■ 2.x. Unlike predefined lists, task metapackages are not specific to the Live System project. Instead, they are maintained by specialist working groups within the distribution and therefore reflect the consensus of each group about which packages best serve the needs of the intended users. They also cover a much broader range of use cases than the predefined lists they replace.
@@ -6818,7 +6556,6 @@
.ancestors: 1 368 0 0 369 396 401 0
.ancestors_collapsed: 1 368 369 396 401 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: ACE60D336988AA8EF826455D4633F392B8DBD53D113139EB143AF5F726085226
| All task metapackages are prefixed ⑆■┨task-┣■, so a quick way to determine which are available (though it may contain a handful of false hits that match the name but aren't metapackages) is to match on the package name with:
@@ -6839,7 +6576,6 @@
.ancestors: 1 368 0 0 369 396 401 0
.ancestors_collapsed: 1 368 369 396 401 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 878668152544075B93FBDB864A941621F7490D05A2C59DCE3844D7153FE43895
| In addition to these, you will find other metapackages with various purposes. Some are subsets of broader task packages, like ⑆■┨gnome-core┣■, while others are individual specialized parts of a Debian Pure Blend, such as the ⑆■┨education-*┣■ metapackages. To list all metapackages in the archive, install the ⑆■┨debtags┣■ package and list all packages with the ⑆■┨role::metapackage┣■ tag as follows:
@@ -6877,7 +6613,6 @@
.ancestors: 1 368 0 0 369 396 409 0
.ancestors_collapsed: 1 368 369 396 409 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 4397D9EEF614DC284F0259911612A39D501F108D73620616238AC92C5FD80024
| Whether you list metapackages, individual packages, or a combination of both, all local package lists are stored in ⑆■┨config/package-lists/┣■. Since more than one list can be used, this lends itself well to modular designs. For example, you may decide to devote one list to a particular choice of desktop, another to a collection of related packages that might as easily be used on top of a different desktop. This allows you to experiment with different combinations of sets of packages with a minimum of fuss, sharing common lists between different live image projects.
@@ -6888,7 +6623,6 @@
.ancestors: 1 368 0 0 369 396 409 0
.ancestors_collapsed: 1 368 369 396 409 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6A6C1C3101A69D1E1300CFB48C64830BAFAEF99B393553E718B859E726256FFB
| Package lists that exist in this directory need to have a ⑆■┨.list┣■ suffix in order to be processed, and then an additional stage suffix, ⑆■┨.chroot┣■ or ⑆■┨.binary┣■ to indicate which stage the list is for.
@@ -6899,7 +6633,6 @@
.ancestors: 1 368 0 0 369 396 409 0
.ancestors_collapsed: 1 368 369 396 409 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 86A6CA8C504634B0033C5ECAE37E156ADAA5611B25D99C15885ADF691A36AA77
| ⑆*┨Note:┣* If you don't specify the stage suffix, the list will be used for both stages. Normally, you want to specify ⑆■┨.list.chroot┣■ so that the packages will only be installed in the live filesystem and not have an extra copy of the ⑆■┨.deb┣■ placed on the medium.
@@ -6927,7 +6660,6 @@
.ancestors: 1 368 0 0 369 396 413 0
.ancestors_collapsed: 1 368 369 396 413 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: DF750B19B1C3B01111D7F8A8BF1F5B18E7410013BDBF17E7058F8720A251CCC9
| To make a binary stage list, place a file suffixed with ⑆■┨.list.binary┣■ in ⑆■┨config/package-lists/┣■. These packages are not installed in the live filesystem, but are included on the live medium under ⑆■┨pool/┣■. You would typically use such a list with one of the non-live installer variants. As mentioned above, if you want this list to be the same as your chroot stage list, simply use the ⑆■┨.list┣■ suffix by itself.
@@ -6956,7 +6688,6 @@
.ancestors: 1 368 0 0 369 396 415 0
.ancestors_collapsed: 1 368 369 396 415 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1259A19FB44C04133F93DBFFB03262C4484EC91EA8D146887C6703A8DF029B57
| It sometimes happens that the best way to compose a list is to generate it with a script. Any line starting with an exclamation point indicates a command to be executed within the chroot when the image is built. For example, one might include the line ⑆■┨! grep-aptavail -n -sPackage -FPriority standard | sort┣■ in a package list to produce a sorted list of available packages with ⑆■┨Priority: standard┣■.
@@ -6967,7 +6698,6 @@
.ancestors: 1 368 0 0 369 396 415 0
.ancestors_collapsed: 1 368 369 396 415 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 72DDD5A1948C47C353B46088FD3504BFD76BAD5729816A48C2F55EDBA3C93A1E
| In fact, selecting packages with the ⑆■┨grep-aptavail┣■ command (from the ⑆■┨dctrl-tools┣■ package) is so useful that ⑆■┨live-build┣■ provides a ⑆■┨Packages┣■ helper script as a convenience. This script takes two arguments: ⑆■┨field┣■ and ⑆■┨pattern┣■. Thus, you can create a list with the following contents:
@@ -7006,7 +6736,6 @@
.ancestors: 1 368 0 0 369 396 419 0
.ancestors_collapsed: 1 368 369 396 419 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D2B5D86F9CB60EAB13369F4EFFC340FDF9D7334740975028BB99CFC75294886A
| Any of the live-build configuration variables stored in ⑆■┨config/*┣■ (minus the ⑆■┨LB_┣■ prefix) may be used in conditional statements in package lists. Generally, this means any ⑆■┨lb config┣■ option uppercased and with dashes changed to underscores. But in practice, it is only the ones that influence package selection that make sense, such as ⑆■┨DISTRIBUTION┣■, ⑆■┨ARCHITECTURES┣■ or ⑆■┨ARCHIVE_AREAS┣■.
@@ -7017,7 +6746,6 @@
.ancestors: 1 368 0 0 369 396 419 0
.ancestors_collapsed: 1 368 369 396 419 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 0CFBFCE68B37EC7DF64D8B1AFCF4D1020EC63564CD447307FA8DC7CAD82C7DA8
| For example, to install ⑆■┨ia32-libs┣■ if the ⑆■┨--architectures amd64┣■ is specified:
@@ -7040,7 +6768,6 @@
.ancestors: 1 368 0 0 369 396 419 0
.ancestors_collapsed: 1 368 369 396 419 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 14B965236F3FA98A724CE77291099CACBDCEE6B1663F0EC2BC3DE96F92A62005
| You may test for any one of a number of values, e.g. to install ⑆/┨memtest86+┣/ if either ⑆■┨--architectures i386┣■ or ⑆■┨--architectures amd64┣■ is specified:
@@ -7063,7 +6790,6 @@
.ancestors: 1 368 0 0 369 396 419 0
.ancestors_collapsed: 1 368 369 396 419 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 172163A9288F67127C62A5A5A85D760BF5CA7CAA39AF88CC2844E6C20ADD895A
| You may also test against variables that may contain more than one value, e.g. to install ⑆/┨vrms┣/ if either ⑆■┨contrib┣■ or ⑆■┨non-free┣■ is specified via ⑆■┨--archive-areas┣■:
@@ -7086,7 +6812,6 @@
.ancestors: 1 368 0 0 369 396 419 0
.ancestors_collapsed: 1 368 369 396 419 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D5C7F311462593760829B7CFD285EAB8659A572CDC28FA1D97F2256ACCD55483
| The nesting of conditionals is not supported.
@@ -7125,7 +6850,6 @@
.ancestors: 1 368 0 0 369 396 428 0
.ancestors_collapsed: 1 368 369 396 428 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C9426ABE6FEA51932AC353B0779100F6CC551E617343F4785B38AA372FC80876
| You can list packages in files with ⑆■┨.list.chroot_live┣■ and ⑆■┨.list.chroot_install┣■ suffixes inside the ⑆■┨config/package-lists┣■ directory. If both a live and an install list exist, the packages in the ⑆■┨.list.chroot_live┣■ list are removed with a hook after the installation (if the user uses the installer). The packages in the ⑆■┨.list.chroot_install┣■ list are present both in the live system and in the installed system. This is a special tweak for the installer and may be useful if you have ⑆■┨--debian-installer live┣■ set in your config, and wish to remove live system-specific packages at install time.
@@ -7154,7 +6878,6 @@
.ancestors: 1 368 0 0 369 396 430 0
.ancestors_collapsed: 1 368 369 396 430 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: F1E525E8D3685E83682FEF0ADA15D8E709DCE6F4EC2AB828F1A886B3E6BC6D61
| Desktop and language tasks are special cases that need some extra planning and configuration. Live images are different from Debian Installer images in this respect. In the Debian Installer, if the medium was prepared for a particular desktop environment flavour, the corresponding task will be automatically installed. Thus, there are internal ⑆■┨gnome-desktop┣■, ⑆■┨kde-desktop┣■, ⑆■┨lxde-desktop┣■ and ⑆■┨xfce-desktop┣■ tasks, none of which are offered in ⑆■┨tasksel┣■'s menu. Likewise, there are no menu entries for tasks for languages, but the user's language choice during the install influences the selection of corresponding language tasks.
@@ -7165,7 +6888,6 @@
.ancestors: 1 368 0 0 369 396 430 0
.ancestors_collapsed: 1 368 369 396 430 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 17B9A10782B482E5F23BBD30F25F29F2DF34A9186AF56E3714873324460A1FE8
| When developing a desktop live image, the image typically boots directly to a working desktop, the choices of both desktop and default language having been made at build time, not at run time as in the case of the Debian Installer. That's not to say that a live image couldn't be built to support multiple desktops or multiple languages and offer the user a choice, but that is not live-build's default behaviour.
@@ -7176,7 +6898,6 @@
.ancestors: 1 368 0 0 369 396 430 0
.ancestors_collapsed: 1 368 369 396 430 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1FB29DE5B5D897B39520DEBB4EB7416BD464FE14587405557DB0D122F8F0471E
| Because there is no provision made automatically for language tasks, which include such things as language-specific fonts and input-method packages, if you want them, you need to specify them in your configuration. For example, a GNOME desktop image containing support for German might include these task metapackages:
@@ -7217,7 +6938,6 @@
.ancestors: 1 368 0 0 369 396 435 0
.ancestors_collapsed: 1 368 369 396 435 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2F214BB6D2A5A5691A96F061A62DF5C46AB9DF27375D167D4496649FBA60DB81
| One or more kernel flavours will be included in your image by default, depending on the architecture. You can choose different flavours via the ⑆■┨--linux-flavours┣■ option. Each flavour is suffixed to the default stub ⑆■┨linux-image┣■ to form each metapackage name which in turn depends on an exact kernel package to be included in your image.
@@ -7228,7 +6948,6 @@
.ancestors: 1 368 0 0 369 396 435 0
.ancestors_collapsed: 1 368 369 396 435 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 57665C670CD6D405AC16FDC7D2AC2F679CC1AFB321812BE5C33361EECEAB00D8
| Thus by default, an ⑆■┨amd64┣■ architecture image will include the ⑆■┨linux-image-amd64┣■ flavour metapackage, and an ⑆■┨i386┣■ architecture image will include the ⑆■┨linux-image-586┣■ metapackage.
@@ -7239,7 +6958,6 @@
.ancestors: 1 368 0 0 369 396 435 0
.ancestors_collapsed: 1 368 369 396 435 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 9041EC82D6B2FC3DE4BB14FB06909A3A8966F9112599F731943F3483837AF0DC
| When more than one kernel package version is available in your configured archives, you can specify a different kernel package name stub with the ⑆■┨--linux-packages┣■ option. For example, supposing you are building an ⑆■┨amd64┣■ architecture image and add the experimental archive for testing purposes so you can install the ⑆■┨linux-image-3.18.0-trunk-amd64┣■ kernel. You would configure that image as follows:
@@ -7279,7 +6997,6 @@
.ancestors: 1 368 0 0 369 396 440 0
.ancestors_collapsed: 1 368 369 396 440 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 50BC4ACEFEEED826B72A4934D4E13BA88E6849E65F6BB44D73720B8535FC361D
| You can build and include your own custom kernels, so long as they are integrated within the Debian package management system. The live-build system does not support kernels not built as ⑆■┨.deb┣■ packages.
@@ -7290,7 +7007,6 @@
.ancestors: 1 368 0 0 369 396 440 0
.ancestors_collapsed: 1 368 369 396 440 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 5BE0939F095E255E49FDE1748CB989D7D09C51D0642E050A0A3DA0A766EA381F
| The proper and recommended way to deploy your own kernel packages is to follow the instructions in the ⑆■┨kernel-handbook┣■. Remember to modify the ABI and flavour suffixes appropriately, then include a complete build of the ⑆■┨linux┣■ and matching ⑆■┨linux-latest┣■ packages in your repository.
@@ -7301,7 +7017,6 @@
.ancestors: 1 368 0 0 369 396 440 0
.ancestors_collapsed: 1 368 369 396 440 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C940F2B82D4AB131422F6706FE38AE0CB8728C60321B9378D56C8E5069CECEC5
.has: links
@@ -7313,7 +7028,6 @@
.ancestors: 1 368 0 0 369 396 440 0
.ancestors_collapsed: 1 368 369 396 440 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C3972A8A7E87272A8B61EE61D3C9E960B0E7CD8236EC1C13B7FD41E7D2DA58C0
| It is beyond the scope of this document to give advice on how to customize your kernel. However, you must at least ensure your configuration satisfies these minimum requirements:
@@ -7324,7 +7038,6 @@
.ancestors: 1 368 0 0 369 396 440 0
.ancestors_collapsed: 1 368 369 396 440 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 001C8E64E7CA0FECE480402BC61FF2A64E7465EEF0AC73B932DA23C02D60F1F2
.bullet: true
@@ -7336,7 +7049,6 @@
.ancestors: 1 368 0 0 369 396 440 0
.ancestors_collapsed: 1 368 369 396 440 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 3967DFC08BF7EE976214F02A9EBB6CE8AF818610FAD930CE6575002A87F8667C
.bullet: true
@@ -7348,7 +7060,6 @@
.ancestors: 1 368 0 0 369 396 440 0
.ancestors_collapsed: 1 368 369 396 440 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: EB9AB8C7CA159E8A7010E01AE3A252362AF1A5E560383C946BDC8B0EF4EE4542
.bullet: true
@@ -7379,7 +7090,6 @@
.ancestors: 1 368 0 0 369 448 0 0
.ancestors_collapsed: 1 368 369 448 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2DC17C70C6DD4EB48058AFB4553AE1E3BEB519C0E373EDB9D0E0C3CDAD076170
| While it is against the philosophy of a live system, it may sometimes be necessary to build a live system with modified versions of packages that are in the Debian repository. This may be to modify or support additional features, languages and branding, or even to remove elements of existing packages that are undesirable. Similarly, “third-party” packages may be used to add bespoke and/or proprietary functionality.
@@ -7390,7 +7100,6 @@
.ancestors: 1 368 0 0 369 448 0 0
.ancestors_collapsed: 1 368 369 448 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0D9B19F4A11DE49058537F20E5B0A6CFD8C2B196A1E2DAF1A27952517CD020F2
.has: links
@@ -7403,7 +7112,6 @@
.ancestors: 1 368 0 0 369 448 0 0
.ancestors_collapsed: 1 368 369 448 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F35344658FA77526D904A6CA6220A1EF644AFDA55957E65D45AA4536DB793210
| There are two ways of installing modified custom packages:
@@ -7414,7 +7122,6 @@
.ancestors: 1 368 0 0 369 448 0 0
.ancestors_collapsed: 1 368 369 448 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3E2CBFAA76119E8E67DA6B66EF3B51B5D88438B3D996747A46A7B006E6EC921C
.bullet: true
@@ -7426,7 +7133,6 @@
.ancestors: 1 368 0 0 369 448 0 0
.ancestors_collapsed: 1 368 369 448 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B79D80A0372A52725F00F1F0BA17D57217BC9A6E2F24D5BAF8151234B26EF885
.bullet: true
@@ -7438,7 +7144,6 @@
.ancestors: 1 368 0 0 369 448 0 0
.ancestors_collapsed: 1 368 369 448 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B82636509B9BF947B3FCBF041AD1DDD3006F01EDD5D4B158AF8673356309AFA4
| Using ⑆■┨packages.chroot┣■ is simpler to achieve and useful for “one-off” customizations but has a number of drawbacks, while using a custom APT repository is more time-consuming to set up.
@@ -7466,7 +7171,6 @@
.ancestors: 1 368 0 0 369 448 455 0
.ancestors_collapsed: 1 368 369 448 455 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 19CFD0713F22C882EF4D15344EFD4CC5ABE4ED8F15EF184C8B82357E2525A8CB
| To install a custom package, simply copy it to the ⑆■┨config/packages.chroot/┣■ directory. Packages that are inside this directory will be automatically installed into the live system during build - you do not need to specify them elsewhere.
@@ -7477,7 +7181,6 @@
.ancestors: 1 368 0 0 369 448 455 0
.ancestors_collapsed: 1 368 369 448 455 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1ECB38AE1F97CC59DBFA702D4BD81098B615E71E5C9CE8924316539D099D599B
| Packages ⑆*┨must┣* be named in the prescribed way. One simple way to do this is to use ⑆■┨dpkg-name┣■.
@@ -7488,7 +7191,6 @@
.ancestors: 1 368 0 0 369 448 455 0
.ancestors_collapsed: 1 368 369 448 455 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7719EAA7C880C1445C84EBACEE826BCF9AE7B557D93C74D2A258AC9166C0217C
| Using ⑆■┨packages.chroot┣■ for installation of custom packages has disadvantages:
@@ -7499,7 +7201,6 @@
.ancestors: 1 368 0 0 369 448 455 0
.ancestors_collapsed: 1 368 369 448 455 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 74CC3AA111D26B033F191406C01BCFD9954794DC699280E73FA2E07575D26EBF
.bullet: true
@@ -7511,7 +7212,6 @@
.ancestors: 1 368 0 0 369 448 455 0
.ancestors_collapsed: 1 368 369 448 455 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7F7451FA75AFE0C0E4E95C016F0B58C5CA2BFE0A5F17CB1F98844CE0360F6421
.bullet: true
@@ -7523,7 +7223,6 @@
.ancestors: 1 368 0 0 369 448 455 0
.ancestors_collapsed: 1 368 369 448 455 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6F699D81711EA4E5BBDA0BBF6D82F65A24CE25749F1BDEF6694B70003866DF51
.bullet: true
@@ -7552,7 +7251,6 @@
.ancestors: 1 368 0 0 369 448 462 0
.ancestors_collapsed: 1 368 369 448 462 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 56BE09ECEC44FE068A02A6684E995597774E207E08553C8936EA23D71600C423
.has: links
@@ -7564,7 +7262,6 @@
.ancestors: 1 368 0 0 369 448 462 0
.ancestors_collapsed: 1 368 369 448 462 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 78BAA3E7D1F8707D82FBA10FBBD10BB089979F56D3242307E02BCA4C4FC67576
| While it may seem unnecessary effort to create an APT repository to install custom packages, the infrastructure can be easily re-used at a later date to offer updates of the modified packages.
@@ -7592,7 +7289,6 @@
.ancestors: 1 368 0 0 369 448 465 0
.ancestors_collapsed: 1 368 369 448 465 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 66B1F80CA08029BED450662C38AC6C7015E76D63973FD814051B3AD595510604
| live-build uses APT to install all packages into the live system so will therefore inherit behaviours from this program. One relevant example is that (assuming a default configuration) given a package available in two different repositories with different version numbers, APT will elect to install the package with the higher version number.
@@ -7603,7 +7299,6 @@
.ancestors: 1 368 0 0 369 448 465 0
.ancestors_collapsed: 1 368 369 448 465 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E0A823D9339363C9B29D0F384F61340C5B93AC65CE266C45A2F97BDFC4F70E2F
.has: links
@@ -7633,7 +7328,6 @@
.ancestors: 1 368 0 0 369 468 0 0
.ancestors_collapsed: 1 368 369 468 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A9D13402A3A325545EC2F22E43A5EFDBC255774998D7A103E9B28DA0C3B2BDA6
| You can configure APT through a number of options applied only at build time. (APT configuration used in the running live system may be configured in the normal way for live system contents, that is, by including the appropriate configurations through ⑆■┨config/includes.chroot/┣■.) For a complete list, look for options starting with ⑆■┨apt┣■ in the ⑆■┨lb_config┣■ man page.
@@ -7662,7 +7356,6 @@
.ancestors: 1 368 0 0 369 468 470 0
.ancestors_collapsed: 1 368 369 468 470 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BF3AD318889E70AC00FEDCA3AB09C64865D317EE0D0CE5A9D9CF9D0E1F185482
| You can elect to use either ⑆/┨apt┣/ or ⑆/┨aptitude┣/ when installing packages at build time. Which utility is used is governed by the ⑆■┨--apt┣■ argument to ⑆■┨lb config┣■. Choose the method implementing the preferred behaviour for package installation, the notable difference being how missing packages are handled.
@@ -7673,7 +7366,6 @@
.ancestors: 1 368 0 0 369 468 470 0
.ancestors_collapsed: 1 368 369 468 470 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: DBEBED29DB4B80627BAF05F372015E4E229951E7C96F3A4E9FA47A32A9F8C29E
.bullet: true
@@ -7685,7 +7377,6 @@
.ancestors: 1 368 0 0 369 468 470 0
.ancestors_collapsed: 1 368 369 468 470 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 61487ADAF0B8BD95839136DE259A98D25B8AE8363E83155A13E62F956441E496
.bullet: true
@@ -7714,7 +7405,6 @@
.ancestors: 1 368 0 0 369 468 474 0
.ancestors_collapsed: 1 368 369 468 474 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 3347816D2ADC0CF1EEAC1529787345BC50124715F5E89FF3D9F2E16C0D1A1494
| One commonly required APT configuration is to deal with building an image behind a proxy. You may specify your APT proxy with the ⑆■┨--apt-ftp-proxy┣■ or ⑆■┨--apt-http-proxy┣■ options as needed, e.g.
@@ -7753,7 +7443,6 @@
.ancestors: 1 368 0 0 369 468 477 0
.ancestors_collapsed: 1 368 369 468 477 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 537006823B5598C2FDA4F9CFB5A765D300E12144CF338343AAC2DD96B98CAA43
| You may find yourself needing to save some space on the image medium, in which case one or the other or both of the following options may be of interest.
@@ -7764,7 +7453,6 @@
.ancestors: 1 368 0 0 369 468 477 0
.ancestors_collapsed: 1 368 369 468 477 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7CCD240D9233D47C3C09B2912DE8B6B4B124C38EB9D3F84C6F8D339A0599A312
| If you don't want to include APT indices in the image, you can omit those with:
@@ -7785,7 +7473,6 @@
.ancestors: 1 368 0 0 369 468 477 0
.ancestors_collapsed: 1 368 369 468 477 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 4ECE1D67F36E632DBC38D7C0A437BE2DA284AC84C820A28BDDFE8770B05D08F0
| This will not influence the entries in ⑆■┨/etc/apt/sources.list┣■, but merely whether ⑆■┨/var/lib/apt┣■ contains the indices files or not. The tradeoff is that APT needs those indices in order to operate in the live system, so before performing ⑆■┨apt-cache search┣■ or ⑆■┨apt-get install┣■, for instance, the user must ⑆■┨apt-get update┣■ first to create those indices.
@@ -7796,7 +7483,6 @@
.ancestors: 1 368 0 0 369 468 477 0
.ancestors_collapsed: 1 368 369 468 477 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: F7F9AF1199D4CCE57B9CF616DC5523FD3C8745A8E30F4764600E4CD00B966274
| If you find the installation of recommended packages bloats your image too much, provided you are prepared to deal with the consequences discussed below, you may disable that default option of APT with:
@@ -7817,7 +7503,6 @@
.ancestors: 1 368 0 0 369 468 477 0
.ancestors_collapsed: 1 368 369 468 477 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 67862AD185D234A808FE10308910823CDF0E306EE7F71EA40838ED6C4932274A
| The most important consequence of turning off recommends is that ⑆■┨live-boot┣■ and ⑆■┨live-config┣■ themselves recommend some packages that provide important functionality used by most Live configurations, such as ⑆■┨user-setup┣■ which ⑆■┨live-config┣■ recommends and is used to create the live user. In all but the most exceptional circumstances you need to add back at least some of these recommends to your package lists or else your image will not work as expected, if at all. Look at the recommended packages for each of the ⑆■┨live-*┣■ packages included in your build and if you are not certain you can omit them, add them back into your package lists.
@@ -7828,7 +7513,6 @@
.ancestors: 1 368 0 0 369 468 477 0
.ancestors_collapsed: 1 368 369 468 477 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7C6F70E088B00092C7B9B7E0E4B8DB3B3517CB2A32B708C1BE1B6D362AD1AF5E
.has: links
@@ -7857,7 +7541,6 @@
.ancestors: 1 368 0 0 369 468 486 0
.ancestors_collapsed: 1 368 369 468 486 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: FA86ACEFED35A4AA49C2CCE647550E40C42F5F70D03F0BE4BC39151B05AF774F
| If there is not a ⑆■┨lb config┣■ option to alter APT's behaviour in the way you need, use ⑆■┨--apt-options┣■ or ⑆■┨--aptitude-options┣■ to pass any options through to your configured APT tool. See the man pages for ⑆■┨apt┣■ and ⑆■┨aptitude┣■ for details. Note that both options have default values that you will need to retain in addition to any overrides you may provide. So, for example, suppose you have included something from ⑆■┨snapshot.debian.org┣■ for testing purposes and want to specify ⑆■┨Acquire::Check-Valid-Until=false┣■ to make APT happy with the stale ⑆■┨Release┣■ file, you would do so as per the following example, appending the new option after the default value ⑆■┨--yes┣■:
@@ -7878,7 +7561,6 @@
.ancestors: 1 368 0 0 369 468 486 0
.ancestors_collapsed: 1 368 369 468 486 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: EF873A3B22E28D71FF963C5C500802890BCCFF76417C54138A29CFAC2E9003B3
| Please check the man pages to fully understand these options and when to use them. This is an example only and should not be construed as advice to configure your image this way. This option would not be appropriate for, say, a final release of a live image.
@@ -7889,7 +7571,6 @@
.ancestors: 1 368 0 0 369 468 486 0
.ancestors_collapsed: 1 368 369 468 486 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 5D75EBAD3AE73D3237C5177DA65F7A5CBD74D1874D8B7070FDEB3D17A8445A1D
| For more complicated APT configurations involving ⑆■┨apt.conf┣■ options you might want to create a ⑆■┨config/apt/apt.conf┣■ file instead. See also the other ⑆■┨apt-*┣■ options for a few convenient shortcuts for frequently needed options.
@@ -7918,7 +7599,6 @@
.ancestors: 1 368 0 0 369 468 491 0
.ancestors_collapsed: 1 368 369 468 491 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 15A90EBAEF2088367187B46FD37278D5CD5EF0E5A525BB184237A8556B2B5E44
| For background, please first read the ⑆■┨apt_preferences(5)┣■ man page. APT pinning can be configured either for build time, or else for run time. For the former, create ⑆■┨config/archives/*.pref┣■, ⑆■┨config/archives/*.pref.chroot┣■, and ⑆■┨config/apt/preferences┣■. For the latter, create ⑆■┨config/includes.chroot/etc/apt/preferences┣■.
@@ -7929,7 +7609,6 @@
.ancestors: 1 368 0 0 369 468 491 0
.ancestors_collapsed: 1 368 369 468 491 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E3B9F1AC52DB598841A87F543DFA91E0E2BFC6569C0C5FEA4873E5FE2C5EBEEB
| Let's say you are building a ${testing} live system but need all the live packages that end up in the binary image to be installed from sid at build time. You need to add sid to your APT sources and pin the live packages from it higher, but all other packages from it lower, than the default priority. Thus, only the packages you want are installed from sid at build time and all others are taken from the target system distribution, ${testing}. The following will accomplish this:
@@ -7959,7 +7638,6 @@
.ancestors: 1 368 0 0 369 468 491 0
.ancestors_collapsed: 1 368 369 468 491 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 37CB2F94D2B29166C023AC3A0BF69ED3727AB0DE07080A0EA54FC206A30B58D0
| Negative pin priorities will prevent a package from being installed, as in the case where you do not want a package that is recommended by another package. Suppose you are building an LXDE image using ⑆■┨task-lxde-desktop┣■ in ⑆■┨config/package-lists/desktop.list.chroot┣■, but don't want the user prompted to store wifi passwords in the keyring. This metapackage depends on ⑆/┨lxde-core┣/, which recommends ⑆/┨gksu┣/, which in turn recommends ⑆/┨gnome-keyring┣/. So you want to omit the recommended ⑆/┨gnome-keyring┣/ package. This can be done by adding the following stanza to ⑆■┨config/apt/preferences┣■:
@@ -8029,7 +7707,6 @@
.ancestors: 1 497 0 0 498 0 0 0
.ancestors_collapsed: 1 497 498 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 601759478CFD887C99AAD31C9F14431B25E9F315A1A2A4CF77FC1B533067CF72
| This chapter discusses fine-tuning customization of the live system contents beyond merely choosing which packages to include. Includes allow you to add or replace arbitrary files in your live system image, hooks allow you to execute arbitrary commands at different stages of the build and at boot time, and preseeding allows you to configure packages when they are installed by supplying answers to debconf questions.
@@ -8059,7 +7736,6 @@
.ancestors: 1 497 0 0 498 500 0 0
.ancestors_collapsed: 1 497 498 500 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6FF80081F06F3199A439F3E934148B96AB44F59557B7658563DC6859C84E3423
| While ideally a live system would include files entirely provided by unmodified packages, it is sometimes convenient to provide or modify some content by means of files. Using includes, it is possible to add (or replace) arbitrary files in your live system image. live-build provides two mechanisms for using them:
@@ -8070,7 +7746,6 @@
.ancestors: 1 497 0 0 498 500 0 0
.ancestors_collapsed: 1 497 498 500 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C2B57575D19831565F383B9ACD98E6C8F8142E36044EE11D28CFC146062C9489
.bullet: true
@@ -8083,7 +7758,6 @@
.ancestors: 1 497 0 0 498 500 0 0
.ancestors_collapsed: 1 497 498 500 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DF309B01399C34D77AEE12D0165A62C8FFAFA95E74BF8B8B509E52573F808C39
.bullet: true
@@ -8096,7 +7770,6 @@
.ancestors: 1 497 0 0 498 500 0 0
.ancestors_collapsed: 1 497 498 500 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6836AF76855CC0C3DADCA2D6DC35F6669DCC7E8ABDE1E68857655DA4DAC5D2E5
.has: links
@@ -8126,7 +7799,6 @@
.ancestors: 1 497 0 0 498 500 505 0
.ancestors_collapsed: 1 497 498 500 505 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: A34C986DF8B60D5F20222809489B3F53C66F4FB2D26758BAB4661C24164B8D90
.has: links
@@ -8138,7 +7810,6 @@
.ancestors: 1 497 0 0 498 500 505 0
.ancestors_collapsed: 1 497 498 500 505 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E581879004592DDE93907FFF28D4EF30D611A7517DBBB9747973AC907A86AC23
| To include files, simply add them to your ⑆■┨config/includes.chroot┣■ directory. This directory corresponds to the root directory ⑆■┨/┣■ of the live system. For example, to add a file ⑆■┨/var/www/index.html┣■ in the live system, use:
@@ -8160,7 +7831,6 @@
.ancestors: 1 497 0 0 498 500 505 0
.ancestors_collapsed: 1 497 498 500 505 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 47822F86D4F6A449D077135D511CC9E82440A57BDB2492508161973EC2978ABA
| Your configuration will then have the following layout:
@@ -8187,7 +7857,6 @@
.ancestors: 1 497 0 0 498 500 505 0
.ancestors_collapsed: 1 497 498 500 505 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D866BD20A908F1E3ADD0AD2A1AE4B95F5E7D4B8A6F085984D9993A8F1BCFEFB0
| Chroot local includes are installed after package installation so that files installed by packages are overwritten.
@@ -8216,7 +7885,6 @@
.ancestors: 1 497 0 0 498 500 512 0
.ancestors_collapsed: 1 497 498 500 512 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1EFE653F5659A0827864CCA4E505D963011397F23B1EFE7E53CBAD8DBAFC77DE
| To include material such as documentation or videos on the medium filesystem so that it is accessible immediately upon insertion of the medium without booting the Live system, you can use binary local includes. This works in a similar fashion to chroot local includes. For example, suppose the files ⑆■┨~/video_demo.*┣■ are demo videos of the live system described by and linked to by an HTML index page. Simply copy the material to ⑆■┨config/includes.binary/┣■ as follows:
@@ -8237,7 +7905,6 @@
.ancestors: 1 497 0 0 498 500 512 0
.ancestors_collapsed: 1 497 498 500 512 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B3FE6E30E6CD34AB61E327E97EED75820CBCCE6CA7D9AA8E9264E1B1A4DA8A5D
| These files will now appear in the root directory of the live medium.
@@ -8267,7 +7934,6 @@
.ancestors: 1 497 0 0 498 516 0 0
.ancestors_collapsed: 1 497 498 516 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EB67445CB95CCD61404801AC692893B89B66953BA9F0FA02A9111338A4F13185
| Hooks allow commands to be performed in the chroot and binary stages of the build in order to customize the image.
@@ -8296,7 +7962,6 @@
.ancestors: 1 497 0 0 498 516 518 0
.ancestors_collapsed: 1 497 498 516 518 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: F4BEE4044E8FDF61F7B72C76EBF8438975BDB54455794B7DFBDCBC01500A74BD
| To run commands in the chroot stage, create a hook script with a ⑆■┨.hook.chroot┣■ suffix containing the commands in the ⑆■┨config/hooks/┣■ directory. The hook will run in the chroot after the rest of your chroot configuration has been applied, so remember to ensure your configuration includes all packages and files your hook needs in order to run. See the example chroot hook scripts for various common chroot customization tasks provided in ⑆■┨/usr/share/doc/live-build/examples/hooks┣■ which you can copy or symlink to use them in your own configuration.
@@ -8325,7 +7990,6 @@
.ancestors: 1 497 0 0 498 516 520 0
.ancestors_collapsed: 1 497 498 516 520 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 656F1093F78B70B6CA34635063DA4D6FB9AD8A48CCB8C37F5B07FC32095D844E
.has: links
@@ -8354,7 +8018,6 @@
.ancestors: 1 497 0 0 498 516 522 0
.ancestors_collapsed: 1 497 498 516 522 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E1FA9C6D5F788087574187DC9EC990206F0CEE415DA7C16730D916D16FD97E14
| To run commands in the binary stage, create a hook script with a ⑆■┨.hook.binary┣■ suffix containing the commands in the ⑆■┨config/hooks/┣■ directory. The hook will run after all other binary commands are run, but before binary_checksums, the very last binary command. The commands in your hook do not run in the chroot, so take care to not modify any files outside of the build tree, or you may damage your build system! See the example binary hook scripts for various common binary customization tasks provided in ⑆■┨/usr/share/doc/live-build/examples/hooks┣■ which you can copy or symlink to use them in your own configuration.
@@ -8382,7 +8045,6 @@
.ancestors: 1 497 0 0 498 524 0 0
.ancestors_collapsed: 1 497 498 524 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FEC4211447917D9348D88DB6FCB7AE8098123A0A9C53D582C78AEC364D821BF9
| Files in the ⑆■┨config/preseed/┣■ directory suffixed with ⑆■┨.cfg┣■ followed by the stage (⑆■┨.chroot┣■ or ⑆■┨.binary┣■) are considered to be debconf preseed files and are installed by live-build using ⑆■┨debconf-set-selections┣■ during the corresponding stage.
@@ -8393,7 +8055,6 @@
.ancestors: 1 497 0 0 498 524 0 0
.ancestors_collapsed: 1 497 498 524 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E21AD59E2AA8D7918E1D4887A9DF1A393821A3899A9143BFA188B10A446765CF
| For more information about debconf, please see ⑆■┨debconf(7)┣■ in the ⑆/┨debconf┣/ package.
@@ -8448,7 +8109,6 @@
.ancestors: 1 527 0 0 528 0 0 0
.ancestors_collapsed: 1 527 528 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 0A56E4669046996EF858229DBAC2A28200BA8101B2827F7D26E3C35E60AC2933
| All configuration that is done during run time is done by live-config. Here are some of the most common options of live-config that users are interested in. A full list of all possibilities can be found in the man page of live-config.
@@ -8476,7 +8136,6 @@
.ancestors: 1 527 0 0 528 530 0 0
.ancestors_collapsed: 1 527 528 530 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 896A0BB961CAEB765016E78BB1756081E41D01EFB5ADF248F78FB43E20B92133
.has: links
@@ -8488,7 +8147,6 @@
.ancestors: 1 527 0 0 528 530 0 0
.ancestors_collapsed: 1 527 528 530 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DD5ACE11091C81D52919C13E08300C2D44ADA06E09DA912F0786187970D362ED
| You can specify additional groups that the live user will belong to by using any of the possibilities to configure live-config. For example, to add the live user to the ⑆■┨fuse┣■ group, you can either add the following file in ⑆■┨config/includes.chroot/etc/live/config/user-setup.conf┣■:
@@ -8509,7 +8167,6 @@
.ancestors: 1 527 0 0 528 530 0 0
.ancestors_collapsed: 1 527 528 530 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 70A23EA5DFA6EF98C3A33E47B121423833ED353150A4BB61B4372A7E578D2458
| or use ⑆■┨live-config.user-default-groups=audio,cdrom,dip,floppy,video,plugdev,netdev,powerdev,scanner,bluetooth,fuse┣■ as a boot parameter.
@@ -8520,7 +8177,6 @@
.ancestors: 1 527 0 0 528 530 0 0
.ancestors_collapsed: 1 527 528 530 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 395073D0C377ED0A9EC0864502271C0658DE523D3CC482AAFACE1F8A8DF38F93
| It is also possible to change the default username “user” and the default password “live”. If you want to do that for any reason, you can easily achieve it as follows:
@@ -8531,7 +8187,6 @@
.ancestors: 1 527 0 0 528 530 0 0
.ancestors_collapsed: 1 527 528 530 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B9CDB82DE2A71DE5443D3BD9476228DC3C7B4845891CD2B44CE2B5419BECD1DC
| To change the default username you can simply specify it in your config:
@@ -8552,7 +8207,6 @@
.ancestors: 1 527 0 0 528 530 0 0
.ancestors_collapsed: 1 527 528 530 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F54B43A9DB8B7379828E4EE7F223FD68A36551429CFC1E1D0128E49B80BBEDB2
.has: links
@@ -8582,7 +8236,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 615B14F241E641DB547DF1E396F380E74C9FF028ADD10DAA1873689806A8260D
| When the live system boots, language is involved in two steps:
@@ -8593,7 +8246,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F67C54061F18C685A9AE6EEDDB5E47EA00E7A8FE50CCB1BE5E4B05981CBF51ED
.bullet: true
@@ -8605,7 +8257,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 060DC9D1395B1814C0739C08DE1529E5AEB033D601692A57A596405BBA4C5F8E
.bullet: true
@@ -8617,7 +8268,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8C5F1BE3D5F42C625511AE89E60BCCEEB3A66CB4C533F04F86B7AE875BF8BCF1
| The default locale when building a Live system is ⑆■┨locales=en_US.UTF-8┣■. To define the locale that should be generated, use the ⑆■┨locales┣■ parameter in the ⑆■┨--bootappend-live┣■ option of ⑆■┨lb config┣■, e.g.
@@ -8638,7 +8288,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0F7F24ED9FE49953D8D31292412EBA2EBAB62B8EFBACCC03EF9F15345FB67F90
| Multiple locales may be specified as a comma-delimited list.
@@ -8649,7 +8298,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 250ACEA1A4641E44D1F28582C7EDB8310A451EF32BCD9E12A601E963D022DE41
| This parameter, as well as the keyboard configuration parameters indicated below, can also be used at the kernel command line. You can specify a locale by ⑆■┨language_country┣■ (in which case the default encoding is used) or the full ⑆■┨language_country.encoding┣■ word. A list of supported locales and the encoding for each can be found in ⑆■┨/usr/share/i18n/SUPPORTED┣■.
@@ -8660,7 +8308,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7189B1FCB9BA3C6EF868706BA9A8E660676A260CDC7D0EB7FF72141EB6583C92
| Both the console and X keyboard configuration are performed by ⑆■┨live-config┣■ using the ⑆■┨console-setup┣■ package. To configure them, use the ⑆■┨keyboard-layouts┣■, ⑆■┨keyboard-variants┣■, ⑆■┨keyboard-options┣■ and ⑆■┨keyboard-model┣■ boot parameters via the ⑆■┨--bootappend-live┣■ option. Valid options for these can be found in ⑆■┨/usr/share/X11/xkb/rules/base.lst┣■. To find layouts and variants for a given language, try searching for the English name of the language and/or the country where the language is spoken, e.g:
@@ -8690,7 +8337,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 99C2C04B78DC5CB2AA2670EC321FA36280E90CD5B1D703FF482E5F5FB6D7F7ED
| Note that each variant lists the layout to which it applies in the description.
@@ -8701,7 +8347,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 86DDC25F91189D06FC87120577D747DF9E9D8B463FFA70BDF7C7C3DE262B217E
| Often, only the layout needs to be configured. For example, to get the locale files for German and Swiss German keyboard layout in X use:
@@ -8722,7 +8367,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 91DBBF101ECEFDB28C7C258AE2DC7E27DFD8D3EE331EB639A2B9D580F49AF7F7
| However, for very specific use cases, you may wish to include other parameters. For example, to set up a French system with a French-Dvorak layout (called Bepo) on a TypeMatrix EZ-Reach 2030 USB keyboard, use:
@@ -8744,7 +8388,6 @@
.ancestors: 1 527 0 0 528 539 0 0
.ancestors_collapsed: 1 527 528 539 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F9A15A642057024EB7F30929385F6DF55C8A2BAD7C6DD417EC6082E76E56F5A0
| Multiple values may be specified as comma-delimited lists for each of the ⑆■┨keyboard-*┣■ options, with the exception of ⑆■┨keyboard-model┣■, which accepts only one value. Please see the ⑆■┨keyboard(5)┣■ man page for details and examples of ⑆■┨XKBMODEL┣■, ⑆■┨XKBLAYOUT┣■, ⑆■┨XKBVARIANT┣■ and ⑆■┨XKBOPTIONS┣■ variables. If multiple ⑆■┨keyboard-variants┣■ values are given, they will be matched one-to-one with ⑆■┨keyboard-layouts┣■ values (see ⑆■┨setxkbmap(1)┣■ ⑆■┨-variant┣■ option). Empty values are allowed; e.g. to define two layouts, the default being US QWERTY and the other being US Dvorak, use:
@@ -8785,7 +8428,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5AB08E8A3A8C089C743CB348DF191C2DA72F0F0B7480A255A056F2487D94647F
| A live cd paradigm is a pre-installed system which runs from read-only media, like a cdrom, where writes and modifications do not survive reboots of the host hardware which runs it.
@@ -8796,7 +8438,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FFDED9D80F5BA4ECF11F0B884706381BA6681FF16194CAB5CE4A7E5C13FF99D2
| A live system is a generalization of this paradigm and thus supports other media in addition to CDs; but still, in its default behaviour, it should be considered read-only and all the run-time evolutions of the system are lost at shutdown.
@@ -8807,7 +8448,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C70A65821C4ED24BF11C1A8E277D29D1A6CADA14B3D48CE132D21CF9A8D10CFD
| 'Persistence' is a common name for different kinds of solutions for saving across reboots some, or all, of this run-time evolution of the system. To understand how it works it would be handy to know that even if the system is booted and run from read-only media, modifications to the files and directories are written on writable media, typically a ram disk (tmpfs) and ram disks' data do not survive reboots.
@@ -8818,7 +8458,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C7B2592D34BEBA5CCA794AB18EA8F6165FCC3E0AF5C41ECDEF7933C8CA4FA509
| The data stored on this ramdisk should be saved on a writable persistent medium like local storage media, a network share or even a session of a multisession (re)writable CD/DVD. All these media are supported in live systems in different ways, and all but the last one require a special boot parameter to be specified at boot time: ⑆■┨persistence┣■.
@@ -8829,7 +8468,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A1398C1CF2C2BCC1C3AD7E35568D99805063247E7A746D37EA964A9A04C3DF21
| If the boot parameter ⑆■┨persistence┣■ is set (and ⑆■┨nopersistence┣■ is not set), local storage media (e.g. hard disks, USB drives) will be probed for persistence volumes during boot. It is possible to restrict which types of persistence volumes to use by specifying certain boot parameters described in the live-boot(7) man page. A persistence volume is any of the following:
@@ -8840,7 +8478,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 18058328FD599C10A116E9E037890E5238ECC98A638356AE4E6ACEE7BB26B163
.bullet: true
@@ -8852,7 +8489,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D4D8DC51F02EB2E38BE3EA0507007D92DAEDC25EF7783EE5598E8CE3F3798213
.bullet: true
@@ -8864,7 +8500,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EFB25EDE0624F783B5D0E378A2629F05C5DD4472957E41A605FFCED2E20E7CE8
.bullet: true
@@ -8876,7 +8511,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D5E52B300464251582F19ED172C70CBDF1926319A94C0CB6066E0ADC54B2ABD4
.has: links
@@ -8888,7 +8522,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3A77A25D4B4BFF73009F4B71E320925B79363465E9CCB08BE81AF958F4643048
| Here are some examples of how to prepare a volume to be used for persistence. It can be, for instance, an ext4 partition on a hard disk or on a usb key created with, e.g.:
@@ -8909,7 +8542,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D6CEF7A38E4402C26956BE459691D5D4DDBDBB5407222082338DFBF606A72646
.has: links
@@ -8921,7 +8553,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 78347C1BB7304E6DAF97485A748D393DFF9710974997E28A39BEEAED854FF066
| If you already have a partition on your device, you could just change the label with one of the following:
@@ -8942,7 +8573,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2578028B5DF5D49B09DBA4931918B05E5798A8701ADD23629FD4A0B895638C62
| Here's an example of how to create an ext4-based image file to be used for persistence:
@@ -8964,7 +8594,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 86412F9FC3F0FDCD85112F5C98CEAFD07F7623E6104137F3C671BD2E665B2E91
| Once the image file is created, as an example, to make ⑆■┨/usr┣■ persistent but only saving the changes you make to that directory and not all the contents of ⑆■┨/usr┣■, you can use the “union” option. If the image file is located in your home directory, copy it to the root of your hard drive's filesystem and mount it in ⑆■┨/mnt┣■ as follows:
@@ -8986,7 +8615,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A9B8FDCD6411EBCB914049AC540A5826834F846E6653254F8ECE59E6D2D5070D
| Then, create the ⑆■┨persistence.conf┣■ file adding content and unmount the image file.
@@ -9008,7 +8636,6 @@
.ancestors: 1 527 0 0 528 556 0 0
.ancestors_collapsed: 1 527 528 556 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1A93FBB3C66A3181A76E630A7630247DB20370303CB0CA0D98C9249AF5E92028
| Now, reboot into your live medium with the boot parameter “persistence”.
@@ -9037,7 +8664,6 @@
.ancestors: 1 527 0 0 528 556 578 0
.ancestors_collapsed: 1 527 528 556 578 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D2246C5891AA0844FA359DDEF0E3822B61820259E9BED62F8184F0AA91C25C3A
| A volume with the label ⑆■┨persistence┣■ must be configured by means of the ⑆■┨persistence.conf┣■ file to make arbitrary directories persistent. That file, located on the volume's filesystem root, controls which directories it makes persistent, and in which way.
@@ -9048,7 +8674,6 @@
.ancestors: 1 527 0 0 528 556 578 0
.ancestors_collapsed: 1 527 528 556 578 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 21D976B59918FD50BD02D20A7EBF848FE5576C6BEBA5B7629ED03AE53581EC5D
| How custom overlay mounts are configured is described in full detail in the persistence.conf(5) man page, but a simple example should be sufficient for most uses. Let's say we want to make our home directory and APT cache persistent in an ext4 filesystem on the /dev/sdb1 partition:
@@ -9073,7 +8698,6 @@
.ancestors: 1 527 0 0 528 556 578 0
.ancestors_collapsed: 1 527 528 556 578 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: EE61B81635CE2CD1C919B12E11F20D8E850543A77F80925BB900AC213CDE5A1E
| Then we reboot. During the first boot the contents of ⑆■┨/home┣■ and ⑆■┨/var/cache/apt┣■ will be copied into the persistence volume, and from then on all changes to these directories will live in the persistence volume. Please note that any paths listed in the ⑆■┨persistence.conf┣■ file cannot contain white spaces or the special ⑆■┨.┣■ and ⑆■┨..┣■ path components. Also, neither ⑆■┨/lib┣■, ⑆■┨/lib/live┣■ (or any of their sub-directories) nor ⑆■┨/┣■ can be made persistent using custom mounts. As a workaround for this limitation you can add ⑆■┨/ union┣■ to your ⑆■┨persistence.conf┣■ file to achieve full persistence.
@@ -9101,7 +8725,6 @@
.ancestors: 1 527 0 0 528 556 583 0
.ancestors_collapsed: 1 527 528 556 583 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 3D4973F91068B7C0B60B4C1CEF35110180DCD9E3BD35644ABE7171254D5625C2
| There are different methods of using multiple persistence store for different use cases. For instance, using several volumes at the same time or selecting only one, among various, for very specific purposes.
@@ -9112,7 +8735,6 @@
.ancestors: 1 527 0 0 528 556 583 0
.ancestors_collapsed: 1 527 528 556 583 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 4E044630663AE771F99743E97A6D7E3D5CF8BBD192632CC1E40C63F771418E3E
| Several different custom overlay volumes (with their own ⑆■┨persistence.conf┣■ files) can be used at the same time, but if several volumes make the same directory persistent, only one of them will be used. If any two mounts are “nested” (i.e. one is a sub-directory of the other) the parent will be mounted before the child so no mount will be hidden by the other. Nested custom mounts are problematic if they are listed in the same ⑆■┨persistence.conf┣■ file. See the persistence.conf(5) man page for how to handle that case if you really need it (hint: you usually don't).
@@ -9123,7 +8745,6 @@
.ancestors: 1 527 0 0 528 556 583 0
.ancestors_collapsed: 1 527 528 556 583 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B4DF4F9EAEEEE37C2F9F0C3BABF994ABEAC60C95C41BE583A233EF9B8087FA15
| One possible use case: If you wish to store the user data i.e. ⑆■┨/home┣■ and the superuser data i.e. ⑆■┨/root┣■ in different partitions, create two partitions with the ⑆■┨persistence┣■ label and add a ⑆■┨persistence.conf┣■ file in each one like this, ⑆■┨# echo “/home” > persistence.conf┣■ for the first partition that will save the user's files and ⑆■┨# echo “/root” > persistence.conf┣■ for the second partition which will store the superuser's files. Finally, use the ⑆■┨persistence┣■ boot parameter.
@@ -9134,7 +8755,6 @@
.ancestors: 1 527 0 0 528 556 583 0
.ancestors_collapsed: 1 527 528 556 583 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B37C65AC062BD6AE887DE7878A8AEC50C0E2D8764E6B4F36487004B9E57EBCB6
| If a user would need multiple persistence store of the same type for different locations or testing, such as ⑆■┨private┣■ and ⑆■┨work┣■, the boot parameter ⑆■┨persistence-label┣■ used in conjunction with the boot parameter ⑆■┨persistence┣■ will allow for multiple but unique persistence media. An example would be if a user wanted to use a persistence partition labeled ⑆■┨private┣■ for personal data like browser bookmarks or other types, they would use the boot parameters: ⑆■┨persistence┣■ ⑆■┨persistence-label=private┣■. And to store work related data, like documents, research projects or other types, they would use the boot parameters: ⑆■┨persistence┣■ ⑆■┨persistence-label=work┣■.
@@ -9145,7 +8765,6 @@
.ancestors: 1 527 0 0 528 556 583 0
.ancestors_collapsed: 1 527 528 556 583 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C7E1EBF1A81E7D98AD8E35A5E08351A7EA7542B2572D2881A6640F386BDB103E
| It is important to remember that each of these volumes, ⑆■┨private┣■ and ⑆■┨work┣■, also needs a ⑆■┨persistence.conf┣■ file in its root. The live-boot man page contains more information about how to use these labels with legacy names.
@@ -9173,7 +8792,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: DF89172B0FA9381BA1E0C8A0FC3111DF8B470A0662C07ED44AD8A9A8AF31B77C
| Using the persistence feature means that some sensible data might get exposed to risk. Especially if the persistent data is stored on a portable device such as a usb stick or an external hard drive. That is when encryption comes in handy. Even if the entire procedure might seem complicated because of the number of steps to be taken, it is really easy to handle encrypted partitions with live-boot. In order to use ⑆*┨luks┣*, which is the supported encryption type, you need to install ⑆/┨cryptsetup┣/ both on the machine you are creating the encrypted partition with and also in the live system you are going to use the encrypted persistent partition with.
@@ -9184,7 +8802,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2EE1B2DE10414F855E4D92A6087D5BB38693499112D6C9F3759553EB54F984F5
| To install ⑆/┨cryptsetup┣/ on your machine:
@@ -9205,7 +8822,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 27A5488916A5CD1A5BBA088AF1B9102ACC5F5204C1FE6BE1B5545637088EF416
| To install ⑆/┨cryptsetup┣/ in your live system, add it to your package-lists:
@@ -9227,7 +8843,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6D67A9C376C7CAE1ACE765E78F26823CB4D48FD51FD5261FC64B7F8E3053AE1A
| Once you have your live system with ⑆/┨cryptsetup┣/, you basically only need to create a new partition, encrypt it and boot with the ⑆■┨persistence┣■ and ⑆■┨persistence-encryption=luks┣■ parameters. We could have already anticipated this step and added the boot parameters following the usual procedure:
@@ -9248,7 +8863,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 3BE9C9E325057D394317F953B18295EB55F214061F85F924C3623F58B797FFDA
| Let's go into the details for all of those who are not familiar with encryption. In the following example we are going to use a partition on a usb stick which corresponds to ⑆■┨/dev/sdc2┣■. Please be warned that you need to determine which partition is the one you are going to use in your specific case.
@@ -9259,7 +8873,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 58E5E6AC76E94C1D56EDF80D7F395672F6A40CE5886FB802CA28C169D4CC0B10
| The first step is plugging in your usb stick and determine which device it is. The recommended method of listing devices in live-manual is using ⑆■┨ls -l /dev/disk/by-id┣■. After that, create a new partition and then, encrypt it with a passphrase as follows:
@@ -9280,7 +8893,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: A0C798CD411B3B4791A47CB5F70A649CDEB71BB589657DF11FC5C4B316D37979
| Then open the luks partition in the virtual device mapper. Use any name you like. We use ⑆*┨live┣* here as an example:
@@ -9301,7 +8913,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B91FE1C2F65598D18D16A8FE2EC203760A58C42327EAC74FE88A66B493CD2D64
| The next step is filling the device with zeros before creating the filesystem:
@@ -9322,7 +8933,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B78607DAAA035254CB7BB7C2A4BA6F148B38389487701FA22F58E0D20C60398C
| Now, we are ready to create the filesystem. Notice that we are adding the label ⑆■┨persistence┣■ so that the device is mounted as persistence store at boot time.
@@ -9343,7 +8953,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 05F92514306FF188390B135CF702E8C4A6196CC3C3C70058FB21B2C028A76006
| To continue with our setup, we need to mount the device, for example in ⑆■┨/mnt┣■.
@@ -9364,7 +8973,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 63C3169818306312A1305EF55A4317C22E185D98DFD7223CD0BCE1974C74ADF4
.has: links
@@ -9386,7 +8994,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B611F81B3C4387E2C6CEDC6052CAF6B7E4F23FDDB7204ACC4D66A72029C58E73
| Then unmount the mount point:
@@ -9407,7 +9014,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: A6D36222DC57F888235FEF097DA36A12AD94BD65146EF42D4876443DA7D4F2DA
| And optionally, although it might be a good way of securing the data we have just added to the partition, we can close the device:
@@ -9428,7 +9034,6 @@
.ancestors: 1 527 0 0 528 556 589 0
.ancestors_collapsed: 1 527 528 556 589 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: AD4F573ABA5BB10FE6D6809FF70443DD068FC0F5857D72B90499C7D0CE65A28B
.has: links
@@ -9497,7 +9102,6 @@
.ancestors: 1 615 0 0 616 617 0 0
.ancestors_collapsed: 1 615 616 617 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FE5D24090A67147C406070F8A0242D317C164061BBF7D967412BE25A8903EE41
| live-build uses ⑆/┨syslinux┣/ and some of its derivatives (depending on the image type) as bootloaders by default. They can be easily customized to suit your needs.
@@ -9508,7 +9112,6 @@
.ancestors: 1 615 0 0 616 617 0 0
.ancestors_collapsed: 1 615 616 617 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3708BC2854BE72824D5DBC30FFF7B32E36A2106005DCD0D3B2DCD14E4327D67A
| In order to use a full theme, copy ⑆■┨/usr/share/live/build/bootloaders┣■ into ⑆■┨config/bootloaders┣■ and edit the files in there. If you do not want to bother modifying all supported bootloader configurations, only providing a local customized copy of one of the bootloaders, e.g. ⑆*┨isolinux┣* in ⑆■┨config/bootloaders/isolinux┣■ is enough too, depending on your use case.
@@ -9519,7 +9122,6 @@
.ancestors: 1 615 0 0 616 617 0 0
.ancestors_collapsed: 1 615 616 617 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B14455FCEA9DD2753ED1507E1A8784B87B97875E532D42BCBE13535A27E5B38A
| When modifying one of the default themes, if you want to use a personalized background image that will be displayed together with the boot menu, add a splash.png picture of 640x480 pixels. Then, remove the splash.svg file.
@@ -9530,7 +9132,6 @@
.ancestors: 1 615 0 0 616 617 0 0
.ancestors_collapsed: 1 615 616 617 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7BE4935B9DFCAD102F96E5F811B424869E1B83CBCDB93237F61D6CAA45B67349
| There are many possibilities when it comes to making changes. For instance, syslinux derivatives are configured by default with a timeout of 0 (zero) which means that they will pause indefinitely at their splash screen until you press a key.
@@ -9541,7 +9142,6 @@
.ancestors: 1 615 0 0 616 617 0 0
.ancestors_collapsed: 1 615 616 617 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 25DFD3C4D4F43DC9323E2A0A35AE604610746B0577195787581D2B7A8A11D085
| To modify the boot timeout of a default ⑆■┨iso-hybrid┣■ image just edit a default ⑆*┨isolinux.cfg┣* file specifying the timeout in units of 1/10 seconds. A modified ⑆*┨isolinux.cfg┣* to boot after five seconds would be similar to this:
@@ -9582,7 +9182,6 @@
.ancestors: 1 615 0 0 616 624 0 0
.ancestors_collapsed: 1 615 616 624 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F3FBDFA1A91C0B8E0197826EB17B67DF196B68EA10D19D37279622605EF725E5
| When creating an ISO9660 binary image, you can use the following options to add various textual metadata for your image. This can help you easily identify the version or configuration of an image without booting it.
@@ -9593,7 +9192,6 @@
.ancestors: 1 615 0 0 616 624 0 0
.ancestors_collapsed: 1 615 616 624 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1AE77789E058F94A2BA9F21AA69D34BF543E931F0698839D78B1C25FBED6CA4C
.bullet: true
@@ -9605,7 +9203,6 @@
.ancestors: 1 615 0 0 616 624 0 0
.ancestors_collapsed: 1 615 616 624 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DD8E777F29A4870DF5EF07A9FDE1F86CAAFF3195B95605439D308D817CBEEADF
.bullet: true
@@ -9617,7 +9214,6 @@
.ancestors: 1 615 0 0 616 624 0 0
.ancestors_collapsed: 1 615 616 624 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B2516200FEF6EEAAD7D2059B667AB4BE562049DDB94948A73E7CE47976E42021
.bullet: true
@@ -9629,7 +9225,6 @@
.ancestors: 1 615 0 0 616 624 0 0
.ancestors_collapsed: 1 615 616 624 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3C0B34757903767F58A220A937D5A93E81F3FA31F669BC17573112CC4782CFAB
.bullet: true
@@ -9682,7 +9277,6 @@
.ancestors: 1 630 0 0 631 0 0 0
.ancestors_collapsed: 1 630 631 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 66141603122FBC2F675DB622E59E3E0EA1A20A2B9EFCDBA6836CD564C5FEC4C3
| Live system images can be integrated with Debian Installer. There are a number of different types of installation, varying in what is included and how the installer operates.
@@ -9693,7 +9287,6 @@
.ancestors: 1 630 0 0 631 0 0 0
.ancestors_collapsed: 1 630 631 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: A1D6645BA98565D7D0BD5791109AB085A14FADA673BB312D1551533229658592
| Please note the careful use of capital letters when referring to the “Debian Installer” in this section - when used like this we refer explicitly to the official installer for the Debian system, not anything else. It is often seen abbreviated to “d-i”.
@@ -9721,7 +9314,6 @@
.ancestors: 1 630 0 0 631 634 0 0
.ancestors_collapsed: 1 630 631 634 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 78A4C4B0EFB5BE8564EF4335BA5B263461EEBFE077D1F9C55425BA6087071100
| The three main types of installer are:
@@ -9732,7 +9324,6 @@
.ancestors: 1 630 0 0 631 634 0 0
.ancestors_collapsed: 1 630 631 634 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 125EE17AF29F9D357C3822A26EB7FF9757A32A5873EBD53E3481EF522973AD2C
| ⑆*┨“Normal” Debian Installer┣*: This is a normal live system image with a separate kernel and initrd which (when selected from the appropriate bootloader) launches into a standard Debian Installer instance, just as if you had downloaded a CD image of Debian and booted it. Images containing a live system and such an otherwise independent installer are often referred to as “combined images”.
@@ -9743,7 +9334,6 @@
.ancestors: 1 630 0 0 631 634 0 0
.ancestors_collapsed: 1 630 631 634 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BAE1463345BB542942913492DF7E2733F03B6970DF9BCC638765461C21D77072
| On such images, Debian is installed by fetching and installing .deb packages using ⑆/┨debootstrap┣/, from local media or some network-based network, resulting in a default Debian system being installed to the hard disk.
@@ -9754,7 +9344,6 @@
.ancestors: 1 630 0 0 631 634 0 0
.ancestors_collapsed: 1 630 631 634 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1AE8FBEDA059EDA95CBFC2CD94A0B06BCF18CACAF8815E3F3A294BB97CF86DB0
| This whole process can be preseeded and customized in a number of ways; see the relevant pages in the Debian Installer manual for more information. Once you have a working preseeding file, live-build can automatically put it in the image and enable it for you.
@@ -9765,7 +9354,6 @@
.ancestors: 1 630 0 0 631 634 0 0
.ancestors_collapsed: 1 630 631 634 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9E351C1A951F9EC369731A5F0F0E595B7A9F3BC31019F6ACC7FFC58EDA59B8C5
| ⑆*┨“Live” Debian Installer┣*: This is a live system image with a separate kernel and initrd which (when selected from the appropriate bootloader) launches into an instance of the Debian Installer.
@@ -9776,7 +9364,6 @@
.ancestors: 1 630 0 0 631 634 0 0
.ancestors_collapsed: 1 630 631 634 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5FD7B315A3DD42CE1F352993E5B9E62B4ABA389ECCA09D7839F75B65DB17D584
| Installation will proceed in an identical fashion to the “normal” installation described above, but at the actual package installation stage, instead of using ⑆/┨debootstrap┣/ to fetch and install packages, the live filesystem image is copied to the target. This is achieved with a special udeb called live-installer.
@@ -9787,7 +9374,6 @@
.ancestors: 1 630 0 0 631 634 0 0
.ancestors_collapsed: 1 630 631 634 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7E11AE9567A6D343BD093E2D756EF0205EE141AABA661724C324086DFAD23D59
| After this stage, the Debian Installer continues as normal, installing and configuring items such as bootloaders and local users, etc.
@@ -9798,7 +9384,6 @@
.ancestors: 1 630 0 0 631 634 0 0
.ancestors_collapsed: 1 630 631 634 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DCEBAB0FC3CDC540D28259CE753536D4676579F4C45C258C27114E89E53282C2
| ⑆*┨Note:┣* to support both normal and live installer entries in the bootloader of the same live medium, you must disable live-installer by preseeding ⑆■┨live-installer/enable=false┣■.
@@ -9809,7 +9394,6 @@
.ancestors: 1 630 0 0 631 634 0 0
.ancestors_collapsed: 1 630 631 634 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E9C4C8C41B89BB251235F35ED32788B8FB87BECBCA7933F9E4D86CE880B0C512
| ⑆*┨“Desktop” Debian Installer┣*: Regardless of the type of Debian Installer included, ⑆■┨d-i┣■ can be launched from the Desktop by clicking on an icon. This is user friendlier in some situations. In order to make use of this, the debian-installer-launcher package needs to be included.
@@ -9820,7 +9404,6 @@
.ancestors: 1 630 0 0 631 634 0 0
.ancestors_collapsed: 1 630 631 634 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 96F8474213E22BACF3E7502605C9E15071B807A51C48CE0756540605711ADBA6
| Note that by default, live-build does not include Debian Installer images in the images, it needs to be specifically enabled with ⑆■┨lb config┣■. Also, please note that for the “Desktop” installer to work, the kernel of the live system must match the kernel ⑆■┨d-i┣■ uses for the specified architecture. For example:
@@ -9860,7 +9443,6 @@
.ancestors: 1 630 0 0 631 646 0 0
.ancestors_collapsed: 1 630 631 646 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D8F34B9E2D23B0F5BE9A976FBF8323BF636A7C158EA0497753573A47D5575058
.has: links
@@ -9900,7 +9482,6 @@
.ancestors: 1 630 0 0 631 649 0 0
.ancestors_collapsed: 1 630 631 649 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EB9FC0B316C1596E7FCB8416E8DB5057F189FE7E3B00B1C3B32164583E6B2C70
.has: links
@@ -9967,7 +9548,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 7EDA19AA17E81BC3358F5EEED43A6E0F925F7240B80BACFF589B16BDC39FE7A4
| When submitting a contribution, please clearly identify its copyright holder and include any applicable licensing statement. Note that to be accepted, the contribution must be licensed under the same license as the rest of the documents, namely, GPL version 3 or later.
@@ -9978,7 +9558,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: AFC7563F386088EF3209EB049B74CE6EA93E5E3D5FD5D098DA91EED96BD8BA3E
.has: links
@@ -9990,7 +9569,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 9A0F43A3F3384ACA9754389311EA7726B65EC673EB5E64D63F26BB89669AF7B5
.has: links
@@ -10002,7 +9580,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 339B294E1A7D800159D7EBA7F0B3D693A98E1AECF376FC6538590BF312ACF407
| However, there are certain restrictions. The server will reject:
@@ -10013,7 +9590,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 61599B746109885C0C5006BB6C2BFF88246269D9D4BA9D3E71C162C8AD2BF061
.bullet: true
@@ -10025,7 +9601,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 4CEA1AE910E13857A59D4E374964812F82EC923CD2DA3607D9A5A5B515CE5882
.bullet: true
@@ -10037,7 +9612,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 8AA2B6D96DA670F6EC00BDC4B0CFA54C821AFDCCC4E1B3B8C33539774E60F92F
.bullet: true
@@ -10049,7 +9623,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: DC4A89AF098F114CACBD89745050A2989FBC2DFB4FE83086A5B4908CE40956D4
| Even though all commits might be revised, we ask you to use your common sense and make good commits with good commit messages.
@@ -10060,7 +9633,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 1BC7051227EE3972FFA46A96D04CDE52ABA4FA59F1FEC8B6A4117A602F06993E
.bullet: true
@@ -10072,7 +9644,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 8CEC3D989715D24EE9FCE9EE9F67FFF74B3FD7A94D459D41438B305C611511B3
.bullet: true
@@ -10084,7 +9655,6 @@
.ancestors: 1 652 0 0 653 0 0 0
.ancestors_collapsed: 1 652 653 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 771B4D4FD9472084CEB92AEEEC705A9CF25832D3D444CEE9A366FA81E955421B
.bullet: true
@@ -10113,7 +9683,6 @@
.ancestors: 1 652 0 0 653 665 0 0
.ancestors_collapsed: 1 652 653 665 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7ADC81FBD5407E72F80FEA35719AE91E74A101BE53FC69F44FD532A86889B3D2
.has: links
@@ -10125,7 +9694,6 @@
.ancestors: 1 652 0 0 653 665 0 0
.ancestors_collapsed: 1 652 653 665 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DDD63DB24140BA4973D30FADDA8772F92A3E672CCCB395ABAFD56BE901201A18
.bullet: true
@@ -10150,7 +9718,6 @@
.ancestors: 1 652 0 0 653 665 0 0
.ancestors_collapsed: 1 652 653 665 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 10FE8FF8770E511E6DBF8E87C90531793D5FADFC54E299539BEFF48DC7A3653F
.bullet: true
@@ -10178,7 +9745,6 @@
.ancestors: 1 652 0 0 653 665 0 0
.ancestors_collapsed: 1 652 653 665 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9F3BCE8E4928FF6102F9F5037DBB90680B71B72D315DD9299398AA7D0B34A89A
.bullet: true
@@ -10201,7 +9767,6 @@
.ancestors: 1 652 0 0 653 665 0 0
.ancestors_collapsed: 1 652 653 665 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5BA37CD27874DA127199C02BB96EE9B07A7549BC8F32DD0CEEC867EA6FC8CF7A
.bullet: true
@@ -10224,7 +9789,6 @@
.ancestors: 1 652 0 0 653 665 0 0
.ancestors_collapsed: 1 652 653 665 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2F3173C9797F84603537FB91851F4803ACC128B37E9750868E4C5F05F5AC908A
| ⑆*┨Important:┣* Remember that you should commit any changes on the ⑆*┨debian-next┣* branch.
@@ -10235,7 +9799,6 @@
.ancestors: 1 652 0 0 653 665 0 0
.ancestors_collapsed: 1 652 653 665 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6DD6D35C362DA39A2AEA117F3E2ED1FC0C3E99D82BE3B1B363E51AB2305C1315
.bullet: true
@@ -10257,7 +9820,6 @@
.ancestors: 1 652 0 0 653 665 0 0
.ancestors_collapsed: 1 652 653 665 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: ACCA6A567384B9894D6A49C01DFBA408E532386C9CE1B0734437CDB0FAA15ECF
.bullet: true
@@ -10329,7 +9891,6 @@
.ancestors: 1 680 0 0 681 0 0 0
.ancestors_collapsed: 1 680 681 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 1893FDB6090143F14E441F1CEA8C8B5DFA4A873131AAE5B479B01CCC71693544
| Live systems are far from being perfect, but we want to make it as close as possible to perfect - with your help. Do not hesitate to report a bug. It is better to fill a report twice than never. However, this chapter includes recommendations on how to file good bug reports.
@@ -10340,7 +9901,6 @@
.ancestors: 1 680 0 0 681 0 0 0
.ancestors_collapsed: 1 680 681 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 2AD92B4716D4D5B38380DBCFA8115E5B59BC890E48A914E512F70E9D809ED65A
| For the impatient:
@@ -10351,7 +9911,6 @@
.ancestors: 1 680 0 0 681 0 0 0
.ancestors_collapsed: 1 680 681 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 8E9DBE46AFCFAB7040389DFD441A75B9B6294CA45D73C985FE1A029686D4D5D1
.bullet: true
@@ -10365,7 +9924,6 @@
.ancestors: 1 680 0 0 681 0 0 0
.ancestors_collapsed: 1 680 681 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: A0D94CDBCEF704E0FA1E143B630B552A569C7E3DB38C4FFF42A7A2B6C91F8113
.bullet: true
@@ -10377,7 +9935,6 @@
.ancestors: 1 680 0 0 681 0 0 0
.ancestors_collapsed: 1 680 681 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 0E20C807380B9F49DBB6C04948160CD76DE1D5CD052768A1285AE443B643BA18
.bullet: true
@@ -10406,7 +9963,6 @@
.ancestors: 1 680 0 0 681 687 0 0
.ancestors_collapsed: 1 680 681 687 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: ED47B76F8AD26F8649AE5564C09E0CE806DC99FD9052FCD8C9CD9D9173563114
| Since Debian ⑆*┨testing┣* and Debian ⑆*┨unstable┣* distributions are moving targets, when you specify either of them as the target system distribution, a successful build may not always be possible.
@@ -10428,7 +9984,6 @@
.ancestors: 1 680 0 0 681 687 0 0
.ancestors_collapsed: 1 680 681 687 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 490D5F57477C481251875CD0FDFCE77584A4A7555DBF79C1A225AC7E3FFE6956
| If this causes too much difficulty for you, do not build a system based on ⑆*┨testing┣* or ⑆*┨unstable┣*, but rather, use ⑆*┨stable┣*. live-build always defaults to the ⑆*┨stable┣* release.
@@ -10439,7 +9994,6 @@
.ancestors: 1 680 0 0 681 687 0 0
.ancestors_collapsed: 1 680 681 687 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4825D87855B0C68F8E94CECF35914F81AEBB4DB69F57FF7BE6CDE77AE9B9838B
.has: links
@@ -10452,7 +10006,6 @@
.ancestors: 1 680 0 0 681 687 0 0
.ancestors_collapsed: 1 680 681 687 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F2B1D1861D83B44B37EC2F57F38CE8B8626C783522CBB1E28BDEA9979F1389BC
.has: links
@@ -10481,7 +10034,6 @@
.ancestors: 1 680 0 0 681 692 0 0
.ancestors_collapsed: 1 680 681 692 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 69C23DFDF4C24A7FD3F40E21BE5065DA1118BFAE4A9EB543F12AF2A7B08EE901
| To ensure that a particular bug is not caused by an uncleanly built system, please always rebuild the whole live system from scratch to see if the bug is reproducible.
@@ -10509,7 +10061,6 @@
.ancestors: 1 680 0 0 681 694 0 0
.ancestors_collapsed: 1 680 681 694 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1E7A99B2B9D969983D361A73B68F942058057C24FDE9BF25A0FB6708731E15A0
| Using outdated packages can cause significant problems when trying to reproduce (and ultimately fix) your problem. Make sure your build system is up-to-date and any packages included in your image are up-to-date as well.
@@ -10538,7 +10089,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 52F6529B2318492303C6E07D8AD129529A888D685D989A9D8A126F145A9B4EA2
| Please provide enough information with your report. Include, at least, the exact version of live-build where the bug is encountered and the steps to reproduce it. Please use your common sense and provide any other relevant information if you think that it might help in solving the problem.
@@ -10549,7 +10099,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 94B5915EA15CE743DD840EC76B9EC801D47F1AD9053061F45212337A71D98103
| To make the most out of your bug report, we require at least the following information:
@@ -10560,7 +10109,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 523176A66B820A2159C9BA90F6743610B0B4459832A5D0C412BC0AAE6CEFBF5C
.bullet: true
@@ -10572,7 +10120,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FFDDC65AC7867C6BA53400AC0EB7576D2C8D27B840EF35D554A3B471C96E2326
.bullet: true
@@ -10584,7 +10131,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D2F5BABAA26DC8195DECBDD6715C88244325B23E5E0E9EBCF32C17E3D5861873
.bullet: true
@@ -10596,7 +10142,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 411642AE6A96A003009728B7C29502B699E96F2A8DDB7D3B5A2EFA38BB9B2A92
.bullet: true
@@ -10608,7 +10153,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0CFD639A95AD268F3574CFD7E9BCA5416A67C86A2037039C6A38D8ADA38124AA
.bullet: true
@@ -10620,7 +10164,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 446F892ADFCDB074DD0F5B7ADA45CF5634A1B508A4425D2DD0812CCD506757D5
.bullet: true
@@ -10632,7 +10175,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 287DCCEF2F492A80F4B42C1553D19572E5707A256AB40F2998D616A717BDF46E
.bullet: true
@@ -10644,7 +10186,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D091FDB70DA5D13E950C2135C85AA58A0C509A06F67E8D4123607798C66064B5
.bullet: true
@@ -10656,7 +10197,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9D35077F9F0C39C9B32AA1B2D836AC49E8D99822C46C40165987CB4A5AA8609C
.bullet: true
@@ -10668,7 +10208,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E9B3D229907371C3CBDD15AA109DA1A17451DCE85A23E1B0E5AC1C42C4670577
.has: links
@@ -10690,7 +10229,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 17E9F3A9847DE9B4751BC5A3F03A9D2EFA2190DF85F36F8A360A49E1833B4197
| At boot time, live-boot and live-config store their logfiles in ⑆■┨/var/log/live/┣■. Check them for error messages.
@@ -10701,7 +10239,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 45D5CFBE1D5EABDF43D101B6A170ADDFCE7C611E6DE5C90B49B4B2808C1C9C9A
| Additionally, to rule out other errors, it is always a good idea to tar up your ⑆■┨config/┣■ directory and upload it somewhere (do ⑆*┨not┣* send it as an attachment to the mailing list), so that we can try to reproduce the errors you encountered. If this is difficult (e.g. due to size) you can use the output of ⑆■┨lb config --dump┣■ which produces a summary of your config tree (i.e. lists files in subdirectories of ⑆■┨config/┣■ but does not include them).
@@ -10712,7 +10249,6 @@
.ancestors: 1 680 0 0 681 696 0 0
.ancestors_collapsed: 1 680 681 696 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7A0B327920EDC4E4C417362CA876A8B74D0D38C273436D2EBE825A6B94B3FC06
| Remember to send in any logs that were produced with English locale settings, e.g. run your live-build commands with a leading ⑆■┨LC_ALL=C┣■ or ⑆■┨LC_ALL=en_US┣■.
@@ -10740,7 +10276,6 @@
.ancestors: 1 680 0 0 681 713 0 0
.ancestors_collapsed: 1 680 681 713 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DF050F66AFA6902CE05E141CFC33C4AA785885FC1782245B36C839A112952542
| If possible, isolate the failing case to the smallest possible change that breaks. It is not always easy to do this so if you cannot manage it for your report, do not worry. However, if you plan your development cycle well, using small enough change sets per iteration, you may be able to isolate the problem by constructing a simpler 'base' configuration that closely matches your actual configuration plus just the broken change set added to it. If you have a hard time sorting out which of your changes broke, it may be that you are including too much in each change set and should develop in smaller increments.
@@ -10769,7 +10304,6 @@
.ancestors: 1 680 0 0 681 715 0 0
.ancestors_collapsed: 1 680 681 715 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3972A9A5C88F319243206A88A6F5D42E0FBF642E233040C29C3F6F5FD76C2CCE
| If you do not know what component is responsible for the bug or if the bug is a general bug concerning live systems, you can fill a bug against the debian-live pseudo-package.
@@ -10780,7 +10314,6 @@
.ancestors: 1 680 0 0 681 715 0 0
.ancestors_collapsed: 1 680 681 715 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6A45C90DD06CAF9B66B13FEFD99F3F514CAF11BFD3350230C0C9BA00B6684D51
| However, we would appreciate it if you try to narrow it down according to where the bug appears.
@@ -10808,7 +10341,6 @@
.ancestors: 1 680 0 0 681 715 718 0
.ancestors_collapsed: 1 680 681 715 718 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: A94C7EC37A9AA9EF6C7BFAD994466BCA2C42679CC206267EADCA9B2C80A1BA2A
| live-build first bootstraps a basic Debian system with ⑆/┨debootstrap┣/. If a bug appears here, check if the error is related to a specific Debian package (most likely), or if it is related to the bootstrapping tool itself.
@@ -10819,7 +10351,6 @@
.ancestors: 1 680 0 0 681 715 718 0
.ancestors_collapsed: 1 680 681 715 718 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 153E2F50DCC99168C03FBE27B40AF0AE25337A085ABCC0502D4CB2ADE632353C
| In both cases, this is not a bug in the live system, but rather in Debian itself and probably we cannot fix it directly. Please report such a bug against the bootstrapping tool or the failing package.
@@ -10847,7 +10378,6 @@
.ancestors: 1 680 0 0 681 715 721 0
.ancestors_collapsed: 1 680 681 715 721 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 74F73EB1DA04E3576FB8B974D93A861A31BA198C93030081AD21A02FB117285B
| live-build installs additional packages from the Debian archive and depending on the Debian distribution used and the daily archive state, it can fail. If a bug appears here, check if the error is also reproducible on a normal system.
@@ -10858,7 +10388,6 @@
.ancestors: 1 680 0 0 681 715 721 0
.ancestors_collapsed: 1 680 681 715 721 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: FB6D12CD09C3B395D8F2FF7903FDBF121F018690E44625696C858BD6B62C227A
| If this is the case, this is not a bug in the live system, but rather in Debian - please report it against the failing package. Running ⑆/┨debootstrap┣/ separately from the Live system build or running ⑆■┨lb bootstrap --debug┣■ will give you more information.
@@ -10869,7 +10398,6 @@
.ancestors: 1 680 0 0 681 715 721 0
.ancestors_collapsed: 1 680 681 715 721 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D3E0F485BEF8B20A2654D1F00A856118DE4DC8C8DCDDDBEC45F6BE6FCD1BDADB
| Also, if you are using a local mirror and/or any sort of proxy and you are experiencing a problem, please always reproduce it first by bootstrapping from an official mirror.
@@ -10897,7 +10425,6 @@
.ancestors: 1 680 0 0 681 715 725 0
.ancestors_collapsed: 1 680 681 715 725 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: AD5E182FBDC41B6EF0BFE591C6DE142F920C19BFF1E941787CA0C99C2661953B
.has: links
@@ -10926,7 +10453,6 @@
.ancestors: 1 680 0 0 681 715 727 0
.ancestors_collapsed: 1 680 681 715 727 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1FA8C523C3F158C167644A4013BF56E68BD92F3E188C76317DE07DC6264FA5B1
| If a package was successfully installed, but fails while actually running the Live system, this is probably a bug in the live system. However:
@@ -10954,7 +10480,6 @@
.ancestors: 1 680 0 0 681 729 0 0
.ancestors_collapsed: 1 680 681 729 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B784A47CDEAEC076520F6BDC3779C6DB9011ED9F96931B1CFA4B6472C3D9ABDC
| Before filing the bug, please search the web for the particular error message or symptom you are getting. As it is highly unlikely that you are the only person experiencing a particular problem. There is always a chance that it has been discussed elsewhere and a possible solution, patch, or workaround has been proposed.
@@ -10965,7 +10490,6 @@
.ancestors: 1 680 0 0 681 729 0 0
.ancestors_collapsed: 1 680 681 729 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FDA3D1C25E47432CFB5E2ACEC9F4461D24AA91BA30E58D72C4A75DEB7B54BE56
| You should pay particular attention to the live systems mailing list, as well as the homepage, as these are likely to contain the most up-to-date information. If such information exists, always include the references to it in your bug report.
@@ -10976,7 +10500,6 @@
.ancestors: 1 680 0 0 681 729 0 0
.ancestors_collapsed: 1 680 681 729 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: EBE191C0D5CDD3F56DFE8E76DED3181C988195B0142D0F8A9B92F1E57A3DCBE4
| In addition, you should check the current bug lists for live-build, live-boot, live-config and live-tools to see whether something similar has already been reported.
@@ -11004,7 +10527,6 @@
.ancestors: 1 680 0 0 681 733 0 0
.ancestors_collapsed: 1 680 681 733 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B3A9AA5723894842A009ACEC1F0911FBD238717FA075739A0CA123AE09DB6F2C
.has: links
@@ -11017,7 +10539,6 @@
.ancestors: 1 680 0 0 681 733 0 0
.ancestors_collapsed: 1 680 681 733 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1898919D5964D5EA3B62E43C78DE08B1237F247A3E3D775EBDC4E4D8995FC089
| In general, you should report build time errors against the live-build package, boot time errors against live-boot, and run time errors against live-config. If you are unsure of which package is appropriate or need more help before submitting a bug report, please report it against the debian-live pseudo-package. We will then take care about it and reassign it where appropriate.
@@ -11028,7 +10549,6 @@
.ancestors: 1 680 0 0 681 733 0 0
.ancestors_collapsed: 1 680 681 733 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 2088EF091E03D11010CB444455D62314AAC885CC07C7E747945A61746519AC8A
| Please note that bugs found in distributions derived from Debian (such as Ubuntu and others) should ⑆*┨not┣* be reported to the Debian BTS unless they can be also reproduced on a Debian system using official Debian packages.
@@ -11082,7 +10602,6 @@
.ancestors: 1 737 0 0 738 0 0 0
.ancestors_collapsed: 1 737 738 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: EA9896516DE94A240C98DF8DE5696D6C5352FA77B4E708F866769ECF4B8B1552
| This chapter documents the coding style used in live systems.
@@ -11110,7 +10629,6 @@
.ancestors: 1 737 0 0 738 740 0 0
.ancestors_collapsed: 1 737 738 740 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1CBA4662A574FDCA6F8A7118AFB03A7ED4DE2D7BB05F678EB07AAC2FF493E179
.bullet: true
@@ -11122,7 +10640,6 @@
.ancestors: 1 737 0 0 738 740 0 0
.ancestors_collapsed: 1 737 738 740 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9D50F01E012C4D97C1737F7559BFE132263D6BABB0E7438630D699E70A5D6CA3
.bullet: true
@@ -11134,7 +10651,6 @@
.ancestors: 1 737 0 0 738 740 0 0
.ancestors_collapsed: 1 737 738 740 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 05D4D4989AA8888013AC397C84C320E5F0E5E7517F58BFC09562CF37C6E078ED
.bullet: true
@@ -11146,7 +10662,6 @@
.ancestors: 1 737 0 0 738 740 0 0
.ancestors_collapsed: 1 737 738 740 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 45664091F4A8D8C6444FACBB0A4E98D10A96D533B9C623F92987239BBAD75F35
.bullet: true
@@ -11175,7 +10690,6 @@
.ancestors: 1 737 0 0 738 745 0 0
.ancestors_collapsed: 1 737 738 745 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 10F27C90A27583E16DACA7C9B9FBF8813FAEA475DA776CE508FA9F6517580CB3
.bullet: true
@@ -11204,7 +10718,6 @@
.ancestors: 1 737 0 0 738 747 0 0
.ancestors_collapsed: 1 737 738 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B800E69ED60084E703E74FD22315626D72336849541328370183DFD3E74CA579
.bullet: true
@@ -11216,7 +10729,6 @@
.ancestors: 1 737 0 0 738 747 0 0
.ancestors_collapsed: 1 737 738 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F1FB3F3848F2BA7A1D62198F6D2525775E3E88567868072B51DE673CEC5ED0CB
.bullet: true
@@ -11228,7 +10740,6 @@
.ancestors: 1 737 0 0 738 747 0 0
.ancestors_collapsed: 1 737 738 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5EF07ED3CAF4DEDC4C58C70A2B2B2D259A387F919E5B254A3CB769B4FBF9FD0B
| Bad:
@@ -11251,7 +10762,6 @@
.ancestors: 1 737 0 0 738 747 0 0
.ancestors_collapsed: 1 737 738 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DEFDE7D0B095F055E6184B8526FBF8636A21FF011B298C9C09727314A6CD8FA8
| Good:
@@ -11275,7 +10785,6 @@
.ancestors: 1 737 0 0 738 747 0 0
.ancestors_collapsed: 1 737 738 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 05D9D5197F771E25C3AEC2BC2334553BA81DC2D05622DB981F6C788AA70A251C
.bullet: true
@@ -11287,7 +10796,6 @@
.ancestors: 1 737 0 0 738 747 0 0
.ancestors_collapsed: 1 737 738 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5EF07ED3CAF4DEDC4C58C70A2B2B2D259A387F919E5B254A3CB769B4FBF9FD0B
| Bad:
@@ -11310,7 +10818,6 @@
.ancestors: 1 737 0 0 738 747 0 0
.ancestors_collapsed: 1 737 738 747 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DEFDE7D0B095F055E6184B8526FBF8636A21FF011B298C9C09727314A6CD8FA8
| Good:
@@ -11351,7 +10858,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 692739D4656D53223AEA963BCC7CC1F250731142ECD6E1DF1E564E44D1387C30
.bullet: true
@@ -11363,7 +10869,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 15F0471467E19721C5D41E66F06481B26DA4CE4D2607AD2B4E6C3AD8CF3D4132
.bullet: true
@@ -11375,7 +10880,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 778A780747909E1C83E95A35AFBC7241E5AD1F4354006576237FD98D3FF66B4F
.bullet: true
@@ -11387,7 +10891,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 19804CCA11D49B5661CD09806F51A57518692073D267A974FB82569EB4F8F3C0
.bullet: true
@@ -11399,7 +10902,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5E37F47DF4E4A06AD2367EB92434FFF57D208A45BAB580E029B57C9C886CA581
.bullet: true
@@ -11411,7 +10913,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: ABE4055648AB319B9C82E537FAF71D8C7AB3AA0AC99C27B4ED3013811D148B33
.bullet: true
@@ -11423,7 +10924,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 05D64485DE4475F1E2B6CE476CA0F4C114D3033AEFF668A294B3998FB7762EAD
.bullet: true
@@ -11435,7 +10935,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: B003D06196942F855BAD9948886558F2A175D160DE920FFA0A34BCBF4AC99669
.bullet: true
@@ -11447,7 +10946,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 447B2F027F441B99C72EA93E176067ECC5D1A5AC5F8C41A08BBCDE2FEAECC42E
.bullet: true
@@ -11459,7 +10957,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5EF07ED3CAF4DEDC4C58C70A2B2B2D259A387F919E5B254A3CB769B4FBF9FD0B
| Bad:
@@ -11480,7 +10977,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DEFDE7D0B095F055E6184B8526FBF8636A21FF011B298C9C09727314A6CD8FA8
| Good:
@@ -11501,7 +10997,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9FA0B866238E9BBD5EF0124E0DBCF5B6765BA78ACB4BC0F5A34750383CCC95BE
.bullet: true
@@ -11513,7 +11008,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5EF07ED3CAF4DEDC4C58C70A2B2B2D259A387F919E5B254A3CB769B4FBF9FD0B
| Bad:
@@ -11537,7 +11031,6 @@
.ancestors: 1 737 0 0 738 759 0 0
.ancestors_collapsed: 1 737 738 759 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: DEFDE7D0B095F055E6184B8526FBF8636A21FF011B298C9C09727314A6CD8FA8
| Good:
@@ -11578,7 +11071,6 @@
.ancestors: 1 737 0 0 738 778 0 0
.ancestors_collapsed: 1 737 738 778 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 53F218F9DCDCAB10785DC98CCF752C673FFD93950F0EC7F65BCA35CE96EB413D
.bullet: true
@@ -11590,7 +11082,6 @@
.ancestors: 1 737 0 0 738 778 0 0
.ancestors_collapsed: 1 737 738 778 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0DE003B3027DB42D99DE370E8DFF36EA15DDF16A7891A53990375E338604A213
.bullet: true
@@ -11602,7 +11093,6 @@
.ancestors: 1 737 0 0 738 778 0 0
.ancestors_collapsed: 1 737 738 778 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 9E80C2425023E508CE0850C2D2726834DCEAEAE729A1878D0706E5C0970AE8BB
.bullet: true
@@ -11614,7 +11104,6 @@
.ancestors: 1 737 0 0 738 778 0 0
.ancestors_collapsed: 1 737 738 778 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8B56459BE23460E5D945DDE1F44D922215BF9B9269258E5E190B3D1BEDBD5DD7
.bullet: true
@@ -11668,7 +11157,6 @@
.ancestors: 1 783 0 0 784 0 0 0
.ancestors_collapsed: 1 783 784 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: EC0E9EE1E76F4F07D5AC464263842D223F33011B95D87424E889BB0659AC54E6
| This chapter documents the procedures within the ${project} for various tasks that need cooperation with other teams in Debian.
@@ -11696,7 +11184,6 @@
.ancestors: 1 783 0 0 784 786 0 0
.ancestors_collapsed: 1 783 784 786 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5F53D376FCEEA13F17DDA011962B9534F1253F679D30022278B2DDE21B3D01E2
| Releasing a new stable major version of Debian includes a lot of different teams working together to make it happen. At some point, the Live team comes in and builds live system images. The requirements to do this are:
@@ -11707,7 +11194,6 @@
.ancestors: 1 783 0 0 784 786 0 0
.ancestors_collapsed: 1 783 784 786 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 684AFDD94EA6B3AF10F7950E17BA5F2ED05F2A952FC01162EF212FA5C7425C65
.bullet: true
@@ -11719,7 +11205,6 @@
.ancestors: 1 783 0 0 784 786 0 0
.ancestors_collapsed: 1 783 784 786 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 6EF4C3AFEA3C536B0BCA1E5F5BBAE3FB33B58684D573CEE45D88D108BF9A4119
.bullet: true
@@ -11731,7 +11216,6 @@
.ancestors: 1 783 0 0 784 786 0 0
.ancestors_collapsed: 1 783 784 786 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 10589485AB45C76F31585064A64A7F7848C88E07EAE8841C8ADFC2D2825FE867
.bullet: true
@@ -11743,7 +11227,6 @@
.ancestors: 1 783 0 0 784 786 0 0
.ancestors_collapsed: 1 783 784 786 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 68E82A61BA458007C4851115F32A1516AB4E6BEACFAE92C61A342E1DC7FC424B
.bullet: true
@@ -11773,7 +11256,6 @@
.ancestors: 1 783 0 0 784 792 0 0
.ancestors_collapsed: 1 783 784 792 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 40B9FD6E4E4700A95007A7DB0A1BB5DD46B662F83F7339E7878685A2A9EE214E
.bullet: true
@@ -11785,7 +11267,6 @@
.ancestors: 1 783 0 0 784 792 0 0
.ancestors_collapsed: 1 783 784 792 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 68E82A61BA458007C4851115F32A1516AB4E6BEACFAE92C61A342E1DC7FC424B
.bullet: true
@@ -11797,7 +11278,6 @@
.ancestors: 1 783 0 0 784 792 0 0
.ancestors_collapsed: 1 783 784 792 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AA6BC2A94781E6AE0613A88961E88AEB5F943A0B8C966C59DCE3C5104B724E48
.bullet: true
@@ -11826,7 +11306,6 @@
.ancestors: 1 783 0 0 784 792 796 0
.ancestors_collapsed: 1 783 784 792 796 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BCD3823773787E03FECB826B34A98DC383FB6DBF785DC23A2984C142F9293C48
| Remember to adjust both chroot and binary mirrors when building the last set of images for a Debian release after it has been moved away from ftp.debian.org to archive.debian.org. That way, old prebuilt live images are still useful without user modifications.
@@ -11854,7 +11333,6 @@
.ancestors: 1 783 0 0 784 792 798 0
.ancestors_collapsed: 1 783 784 792 798 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 0FDCD9859AB12287F09C1B4A922333345067CA4E988E0FAC3CF62F519D600CD0
| An announcement mail for point releases can be generated using the template below and the following command:
@@ -11879,7 +11357,6 @@
.ancestors: 1 783 0 0 784 792 798 0
.ancestors_collapsed: 1 783 784 792 798 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 33E0367FD6EE1EEB8E9BB9099827F22150AAE5BF90D26A83F71F23D088CC6B5D
| Please check the mail carefully before sending and pass it to others for proof-reading.
@@ -11977,7 +11454,6 @@
.ancestors: 1 803 0 0 804 0 0 0
.ancestors_collapsed: 1 803 804 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 5B4F550C1B5FCE9AF33308DF6D6B4FFC1B841C683FCCA61AEB6FD73C6E8763B2
.has: links
@@ -12000,7 +11476,6 @@
.ancestors: 1 803 0 0 804 0 0 0
.ancestors_collapsed: 1 803 804 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: E34C246FB759D8B8AA2AF9999B23AA3519832A35675076E016771881EF31294D
| Or,
@@ -12021,7 +11496,6 @@
.ancestors: 1 803 0 0 804 0 0 0
.ancestors_collapsed: 1 803 804 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: E34C246FB759D8B8AA2AF9999B23AA3519832A35675076E016771881EF31294D
| Or,
@@ -12042,7 +11516,6 @@
.ancestors: 1 803 0 0 804 0 0 0
.ancestors_collapsed: 1 803 804 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 277295830C351F510E38E42AAEEC19B22B3C1AA7CA518C19F87BC7F354C54EDB
| The cloning addresses with write permission have the form: ⑆■┨git@live-systems.org:/repository┣■.
@@ -12053,7 +11526,6 @@
.ancestors: 1 803 0 0 804 0 0 0
.ancestors_collapsed: 1 803 804 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 4EB5A419CD482FA721DB07DCEFECF7D300F55C00A184C43558457110CBC915A1
| So, again, to clone live-manual over ssh you must type:
@@ -12074,7 +11546,6 @@
.ancestors: 1 803 0 0 804 0 0 0
.ancestors_collapsed: 1 803 804 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: FCB7C4ECA03B465932D1B1E6D87741355D6C7585CE8D3C30E4260F4B03292869
| The git tree is made up of several different branches. The ⑆*┨debian┣* and the ⑆*┨debian-next┣* branches are particularly noteworthy because they contain the actual work that will eventually be included in each new release.
@@ -12085,7 +11556,6 @@
.ancestors: 1 803 0 0 804 0 0 0
.ancestors_collapsed: 1 803 804 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: CB8EC7CFF81476BA0FB4F46BA9F9AD2A8A6CA5EAD4ED93B96E41C6BF9AE6062A
| After cloning any of the existing repositories, you will be on the ⑆*┨debian┣* branch. This is appropriate to take a look at the state of the project's latest release but before starting work it is crucial to switch to the ⑆*┨debian-next┣* branch. To do so:
@@ -12106,7 +11576,6 @@
.ancestors: 1 803 0 0 804 0 0 0
.ancestors_collapsed: 1 803 804 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: CE885C1293AAFBA4D0BBD115A5EE387EAE86284F83366AF64055BD584823061B
| The ⑆*┨debian-next┣* branch, which is not always fast-forward, is where all the changes are committed first before being merged into the ⑆*┨debian┣* branch. To make an analogy, it is like a testing ground. If you are working on this branch and need to pull, you will have to do a ⑆■┨git pull --rebase┣■ so that your local modifications are staged while pulling from the server and then your changes will be put on top of it all.
@@ -12134,7 +11603,6 @@
.ancestors: 1 803 0 0 804 818 0 0
.ancestors_collapsed: 1 803 804 818 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 77DDDFE48F88D446F0062565073D80A160BC2BA20165837CCC820B328C0E2070
| If you intend to clone several of the live systems repositories and want to switch to the ⑆*┨debian-next┣* branch right away to check the latest code, write a patch or contribute with a translation you ought to know that the git server provides a ⑆■┨mrconfig┣■ file to ease the handling of multiple repositories. In order to use it you need to install the ⑆/┨mr┣/ package and after that, launch:
@@ -12155,7 +11623,6 @@
.ancestors: 1 803 0 0 804 818 0 0
.ancestors_collapsed: 1 803 804 818 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 25E16C1EDD3DB927997382FEA738AE45EA3B9B95CEDA930248F2ECE0CD31844D
.has: links
@@ -12230,7 +11697,6 @@
.ancestors: 1 823 0 0 824 0 0 0
.ancestors_collapsed: 1 823 824 0 0 0 0 0
.parent_lev: 4
-.ocn_off: true
.is_of_type: para
.sha256: 2BDACD75E0A07B0B438C9E9EC2D9036C98449B7DF5DD8A1381C7C3C2A5F0A793
| This chapter covers example builds for specific use cases with live systems. If you are new to building your own live system images, we recommend you first look at the three tutorials in sequence, as each one teaches new techniques that will help you use and understand the remaining examples.
@@ -12259,7 +11725,6 @@
.ancestors: 1 823 0 0 824 826 0 0
.ancestors_collapsed: 1 823 824 826 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F2AC2E6F4F5870D0C06D5C5656A87DB31CEF67492EE1868E7A39A8502FC61326
.has: links
@@ -12271,7 +11736,6 @@
.ancestors: 1 823 0 0 824 826 0 0
.ancestors_collapsed: 1 823 824 826 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 65F699DB33B6C7F79F485DCE6AE4E1A4DBB2256BA08D4343FCFA74EBE0CF945F
.has: links
@@ -12313,7 +11777,6 @@
.ancestors: 1 823 0 0 824 830 0 0
.ancestors_collapsed: 1 823 824 830 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 139F738D31C3D0CA3EFBC4B383D0299F742ADCEE90F9F234A17B24BC890C7C3A
| ⑆*┨Use case:┣* Create a simple first image, learning the basics of live-build.
@@ -12324,7 +11787,6 @@
.ancestors: 1 823 0 0 824 830 0 0
.ancestors_collapsed: 1 823 824 830 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: BC3EC77259896C24487BCAD12C62810451F41711F461D41DE27D412D0958F2FC
| In this tutorial, we will build a default ISO hybrid live system image containing only base packages (no Xorg) and some live system support packages, as a first exercise in using live-build.
@@ -12335,7 +11797,6 @@
.ancestors: 1 823 0 0 824 830 0 0
.ancestors_collapsed: 1 823 824 830 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 5B369D5D6625DD1E7DFEFC749E1B6401FE1233F447E6B279D7F29E6C79E385E7
| You can't get much simpler than this:
@@ -12356,7 +11817,6 @@
.ancestors: 1 823 0 0 824 830 0 0
.ancestors_collapsed: 1 823 824 830 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 031F0E1986AF93EB2C7A21C702F49C2F6EBD4A1D1C7B112A50A1CFAE84025C6B
| Examine the contents of the ⑆■┨config/┣■ directory if you wish. You will see stored here a skeletal configuration, ready to customize or, in this case, use immediately to build a default image.
@@ -12367,7 +11827,6 @@
.ancestors: 1 823 0 0 824 830 0 0
.ancestors_collapsed: 1 823 824 830 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7B08E735F5A590831AC3137352511D9F1DD5AC239797E924356257F220856A19
| Now, as superuser, build the image, saving a log as you build with ⑆■┨tee┣■.
@@ -12388,7 +11847,6 @@
.ancestors: 1 823 0 0 824 830 0 0
.ancestors_collapsed: 1 823 824 830 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7CD36FAEDEC99F157CE8BBCA5A073A5DBBFE6AD33E28106D3A2F5C8D8D4E49C4
.has: links
@@ -12418,7 +11876,6 @@
.ancestors: 1 823 0 0 824 839 0 0
.ancestors_collapsed: 1 823 824 839 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 87FAB580F59A96A80437F0A3CCCE75EA4C2871ECFEF3AEB6FA89312662912764
| ⑆*┨Use case:┣* Create a web browser utility image, learning how to apply customizations.
@@ -12429,7 +11886,6 @@
.ancestors: 1 823 0 0 824 839 0 0
.ancestors_collapsed: 1 823 824 839 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: CE61D8F6164710372B4FD3E35D7105A51DA13697F4350992C2123252CF66BCF1
| In this tutorial, we will create an image suitable for use as a web browser utility, serving as an introduction to customizing live system images.
@@ -12453,7 +11909,6 @@
.ancestors: 1 823 0 0 824 839 0 0
.ancestors_collapsed: 1 823 824 839 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8817B03B269DB094BAB2E3E0E759347C62DCFFF143688A36B222F47278FA5D2A
| Our choice of LXDE for this example reflects our desire to provide a minimal desktop environment, since the focus of the image is the single use we have in mind, the web browser. We could go even further and provide a default configuration for the web browser in ⑆■┨config/includes.chroot/etc/iceweasel/profile/┣■, or additional support packages for viewing various kinds of web content, but we leave this as an exercise for the reader.
@@ -12464,7 +11919,6 @@
.ancestors: 1 823 0 0 824 839 0 0
.ancestors_collapsed: 1 823 824 839 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 242162E623F55908BD44542A16B040719345B032C76A4E0BD5D81CA3AA920934
.has: links
@@ -12486,7 +11940,6 @@
.ancestors: 1 823 0 0 824 839 0 0
.ancestors_collapsed: 1 823 824 839 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 841130E5418248D4547402709F2E41694936B1055A231B20C1AD3D27190E7B2D
.has: links
@@ -12517,7 +11970,6 @@
.ancestors: 1 823 0 0 824 847 0 0
.ancestors_collapsed: 1 823 824 847 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 051CBE31EF4C29E5596AC6A52320E2D575D9BC6AFC7C5B651E194C58CF4F66CB
| ⑆*┨Use case:┣* Create a project to build a personalized image, containing your favourite software to take with you on a USB stick wherever you go, and evolving in successive revisions as your needs and preferences change.
@@ -12528,7 +11980,6 @@
.ancestors: 1 823 0 0 824 847 0 0
.ancestors_collapsed: 1 823 824 847 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 816D9560C9B9CF32E88FB8BC238A76930FC7FC4E0401CF74EC9D02C2A6752B31
.has: links
@@ -12569,7 +12020,6 @@
.ancestors: 1 823 0 0 824 847 850 0
.ancestors_collapsed: 1 823 824 847 850 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: EF2B966B99DE56399B4E8B024FFC4256798CDDBDE44D62567237A6B998D4DD7A
| Edit ⑆■┨auto/config┣■ to read as follows:
@@ -12595,7 +12045,6 @@
.ancestors: 1 823 0 0 824 847 850 0
.ancestors_collapsed: 1 823 824 847 850 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8D88FEAF14837A6C99EF2A7CD87BEB42E8F1EA53D81E5F8227F27D41B70874A8
| Perform ⑆■┨lb config┣■ to generate the config tree, using the ⑆■┨auto/config┣■ script you just created:
@@ -12616,7 +12065,6 @@
.ancestors: 1 823 0 0 824 847 850 0
.ancestors_collapsed: 1 823 824 847 850 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 86383D5671CBAC4108C74C846536841A91A083F42839B9B4E5F4B2FDFF674509
| Now populate your local package list:
@@ -12637,7 +12085,6 @@
.ancestors: 1 823 0 0 824 847 850 0
.ancestors_collapsed: 1 823 824 847 850 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2B23228443ECCB7B1FB81219CFBB15553CD3864733ED465839363A334D9A2D1E
| First, ⑆■┨--architectures i386┣■ ensures that on our ⑆■┨amd64┣■ build system, we build a 32-bit version suitable for use on most machines. Second, we use ⑆■┨--linux-flavours 686-pae┣■ because we don't anticipate using this image on much older systems. Third, we have chosen the ⑆/┨lxde┣/ task metapackage to give us a minimal desktop. And finally, we have added two initial favourite packages: ⑆/┨iceweasel┣/ and ⑆/┨xchat┣/.
@@ -12648,7 +12095,6 @@
.ancestors: 1 823 0 0 824 847 850 0
.ancestors_collapsed: 1 823 824 847 850 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1D77508189AE0DD7FD9959594B6AD5DD21821CE506E9A5E3897B9F562DA7D473
| Now, build the image:
@@ -12669,7 +12115,6 @@
.ancestors: 1 823 0 0 824 847 850 0
.ancestors_collapsed: 1 823 824 847 850 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2D3AE77E4CE35E5403CD484F09C87709519156C27BBA3024774C67DA0A4E707A
| Note that unlike in the first two tutorials, we no longer have to type ⑆■┨2>&1 | tee build.log┣■ as that is now included in ⑆■┨auto/build┣■.
@@ -12680,7 +12125,6 @@
.ancestors: 1 823 0 0 824 847 850 0
.ancestors_collapsed: 1 823 824 847 850 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B4F5C7DF88D7ECC7E72819D618A29FA28188C32D3C1232C82388A5FACA666194
.has: links
@@ -12722,7 +12166,6 @@
.ancestors: 1 823 0 0 824 847 864 0
.ancestors_collapsed: 1 823 824 847 864 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 76737CDBB567CD13FB9A647FE204CD1AC11530A7FB4036A77A3F06F97E33C2AA
| In this revision, we're going to clean up from the first build, add the ⑆/┨vlc┣/ package to our configuration, rebuild, test and commit.
@@ -12733,7 +12176,6 @@
.ancestors: 1 823 0 0 824 847 864 0
.ancestors_collapsed: 1 823 824 847 864 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2C1DF6EBB629DEE34280B681B457C6815AF39C30D4F350965452392BAE7C547F
| The ⑆■┨lb clean┣■ command will clean up all generated files from the previous build except for the cache, which saves having to re-download packages. This ensures that the subsequent ⑆■┨lb build┣■ will re-run all stages to regenerate the files from our new configuration.
@@ -12754,7 +12196,6 @@
.ancestors: 1 823 0 0 824 847 864 0
.ancestors_collapsed: 1 823 824 847 864 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 16F827BEAEA8113EE2C2064C0DEBE00EC2919EDF300867294A70FEA6309371FF
| Now append the ⑆/┨vlc┣/ package to our local package list in ⑆■┨config/package-lists/my.list.chroot┣■:
@@ -12775,7 +12216,6 @@
.ancestors: 1 823 0 0 824 847 864 0
.ancestors_collapsed: 1 823 824 847 864 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D1400B492E577FF6A871F25FB703583E5D6CC71FEBD9FC5E0AB43CAE425F6C53
| Build again:
@@ -12796,7 +12236,6 @@
.ancestors: 1 823 0 0 824 847 864 0
.ancestors_collapsed: 1 823 824 847 864 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: CBFC9BBAB9A9E0EB9846039FA5F3215C5A2596D9ECB45A782819E387CDCE0DD7
| Test, and when you're satisfied, commit the next revision:
@@ -12817,7 +12256,6 @@
.ancestors: 1 823 0 0 824 847 864 0
.ancestors_collapsed: 1 823 824 847 864 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6180D69019327D5DAE61971D81E904E9A251891AE3DD5E3808E7B66EC46FF02E
| Of course, more complicated changes to the configuration are possible, perhaps adding files in subdirectories of ⑆■┨config/┣■. When you commit new revisions, just take care not to hand edit or commit the top-level files in ⑆■┨config┣■ containing ⑆■┨LB_*┣■ variables, as these are build products, too, and are always cleaned up by ⑆■┨lb clean┣■ and re-created with ⑆■┨lb config┣■ via their respective ⑆■┨auto┣■ scripts.
@@ -12828,7 +12266,6 @@
.ancestors: 1 823 0 0 824 847 864 0
.ancestors_collapsed: 1 823 824 847 864 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 5AF3D8365EA144B5F529EA71C2CFA743F1FB161CF360D6EFE07A4AD46B945A43
| We've come to the end of our tutorial series. While many more kinds of customization are possible, even just using the few features explored in these simple examples, an almost infinite variety of different images can be created. The remaining examples in this section cover several other use cases drawn from the collected experiences of users of live systems.
@@ -12856,7 +12293,6 @@
.ancestors: 1 823 0 0 824 876 0 0
.ancestors_collapsed: 1 823 824 876 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: FC66C4EF415E3566DB4E7931724DEF5696ADD39234965C1B4465489E636EA5F3
| ⑆*┨Use case:┣* Create an image with live-build to boot directly to a VNC server.
@@ -12867,7 +12303,6 @@
.ancestors: 1 823 0 0 824 876 0 0
.ancestors_collapsed: 1 823 824 876 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 095D602D5508E7CE7B911846895E0FAB72577870E0ADB469ABFB7B13827D17B2
.has: links
@@ -12893,7 +12328,6 @@
.ancestors: 1 823 0 0 824 876 0 0
.ancestors_collapsed: 1 823 824 876 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F87DD99EEE4B57AA79A34300414FC252D5E4081798A99DC8629AFA354F677720
.has: links
@@ -12905,7 +12339,6 @@
.ancestors: 1 823 0 0 824 876 0 0
.ancestors_collapsed: 1 823 824 876 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 61BBF61500AB78DA52E88BA9F208D828B69DF71C8616EADE5A7C23C336478CDD
| An easy way to list recommends is using ⑆/┨apt-cache┣/. For example:
@@ -12926,7 +12359,6 @@
.ancestors: 1 823 0 0 824 876 0 0
.ancestors_collapsed: 1 823 824 876 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F8EFA683F1D965484E8063095D981BBF847DAF74793B67D2A7E4A8A92CCC1858
| In this example we found out that we had to re-include several packages recommended by live-config and live-boot: ⑆■┨user-setup┣■ to make autologin work and ⑆■┨sudo┣■ as an essential program to shutdown the system. Besides, it could be handy to add ⑆■┨live-tools┣■ to be able to copy the image to RAM and ⑆■┨eject┣■ to eventually eject the live medium. So:
@@ -12947,7 +12379,6 @@
.ancestors: 1 823 0 0 824 876 0 0
.ancestors_collapsed: 1 823 824 876 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: C76D7C7B32E5748502430F67D3C4480DF576124689074E6BA8214BF776651BF8
| After that, create the directory ⑆■┨/etc/skel┣■ in ⑆■┨config/includes.chroot┣■ and put a custom ⑆■┨.xsession┣■ in it for the default user that will launch ⑆/┨metacity┣/ and start ⑆/┨xvncviewer┣/, connecting to port ⑆■┨5901┣■ on a server at ⑆■┨192.168.1.2┣■:
@@ -12976,7 +12407,6 @@
.ancestors: 1 823 0 0 824 876 0 0
.ancestors_collapsed: 1 823 824 876 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 372F7C2E17F5C5698CDBAD699EB6432E16F7AB9C09BBAA4D7E550EA0AB7F7F73
| Build the image:
@@ -12997,7 +12427,6 @@
.ancestors: 1 823 0 0 824 876 0 0
.ancestors_collapsed: 1 823 824 876 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: AF3BEE800D9FAC1D6CF36964CCB627A7104ECC6ADC9DC99E7B31EC7179315B7B
| Enjoy.
@@ -13025,7 +12454,6 @@
.ancestors: 1 823 0 0 824 890 0 0
.ancestors_collapsed: 1 823 824 890 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 92F5A11345839BD4F53B19EB890BD541CA2B2051D3AECCE9782D0B1F67B1B6B0
| ⑆*┨Use case:┣* Create a default image with some components removed in order to fit on a 128MB USB key with a little space left over to use as you see fit.
@@ -13036,7 +12464,6 @@
.ancestors: 1 823 0 0 824 890 0 0
.ancestors_collapsed: 1 823 824 890 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 53076819253373C1C3F6356D978690F011602C6060F8629108460ED240E11250
| When optimizing an image to fit a certain media size, you need to understand the tradeoffs you are making between size and functionality. In this example, we trim only so much as to make room for additional material within a 128MB media size, but without doing anything to destroy the integrity of the packages contained within, such as the purging of locale data via the ⑆/┨localepurge┣/ package, or other such “intrusive” optimizations. Of particular note, we use ⑆■┨--debootstrap-options┣■ to create a minimal system from scratch.
@@ -13057,7 +12484,6 @@
.ancestors: 1 823 0 0 824 890 0 0
.ancestors_collapsed: 1 823 824 890 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 4D1666D6D301310E9106080297B13AE646B91F370146EB24804F438DC071515A
.has: links
@@ -13079,7 +12505,6 @@
.ancestors: 1 823 0 0 824 890 0 0
.ancestors_collapsed: 1 823 824 890 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 66F0336BBC7A0F3CC19D6BCAE9067365B7A812D4BB30856ED9753F922CE7191F
| Now, build the image in the usual way:
@@ -13100,7 +12525,6 @@
.ancestors: 1 823 0 0 824 890 0 0
.ancestors_collapsed: 1 823 824 890 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 28B85ADCA833992D1FD240343E9757DFD6992404579C5CDA02A6B62BECC00C87
.has: links
@@ -13112,7 +12536,6 @@
.ancestors: 1 823 0 0 824 890 0 0
.ancestors_collapsed: 1 823 824 890 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 0DFFFCE1A0078F51AF6FF13B9175B2A7D1B751C6C4997987BD2B101603E55CBB
| Leaving off APT's indices with ⑆■┨--apt-indices false┣■ saves a fair amount of space, the tradeoff being that you need to do an ⑆■┨apt-get update┣■ before using ⑆/┨apt┣/ in the live system. Dropping recommended packages with ⑆■┨--apt-recommends false┣■ saves some additional space, at the expense of omitting some packages you might otherwise expect to be there. ⑆■┨--debootstrap-options “--variant=minbase”┣■ bootstraps a minimal system from the start. Not automatically including firmware packages with ⑆■┨--firmware-chroot false┣■ saves some space too. And finally, ⑆■┨--memtest none┣■ prevents the installation of a memory tester.
@@ -13123,7 +12546,6 @@
.ancestors: 1 823 0 0 824 890 0 0
.ancestors_collapsed: 1 823 824 890 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A8C656C51AF263FD7F4E173EE5D288F46DE750F1C5FE71568D7A8B78DB275EAE
| ⑆*┨Note:┣* A minimal system can also be achieved using hooks, like for example the ⑆■┨stripped.hook.chroot┣■ hook found in ⑆■┨/usr/share/doc/live-build/examples/hooks┣■. It may shave off additional small amounts of space and produce an image of 91MB. However, it does so by removal of documentation and other files from packages installed on the system. This violates the integrity of those packages and that, as the comment header warns, may have unforeseen consequences. That is why using a minimal ⑆/┨debootstrap┣/ is the recommended way of achieving this goal.
@@ -13151,7 +12573,6 @@
.ancestors: 1 823 0 0 824 901 0 0
.ancestors_collapsed: 1 823 824 901 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1DBCA20676778E8D5CB6C2F166C43FD4B8272573133CC1F3B14D21391273DE91
| ⑆*┨Use case:┣* Create a GNOME desktop image, localized for Switzerland and including an installer.
@@ -13162,7 +12583,6 @@
.ancestors: 1 823 0 0 824 901 0 0
.ancestors_collapsed: 1 823 824 901 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 8F87613A18F0E863C73D5823910CF933A8D18B045A5319FEC2FA2F2DC2495BB4
| We want to make an iso-hybrid image for i386 architecture using our preferred desktop, in this case GNOME, containing all of the same packages that would be installed by the standard Debian installer for GNOME.
@@ -13173,7 +12593,6 @@
.ancestors: 1 823 0 0 824 901 0 0
.ancestors_collapsed: 1 823 824 901 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: F760EA2DC1DA2A5C580F7DF3472C8E9E212BB94F76CF9D3A3ECF6AB05B5B6ABE
| Our initial problem is the discovery of the names of the appropriate language tasks. Currently, live-build cannot help with this. While we might get lucky and find this by trial-and-error, there is a tool, ⑆■┨grep-dctrl┣■, which can be used to dig it out of the task descriptions in tasksel-data, so to prepare, make sure you have both of those things:
@@ -13194,7 +12613,6 @@
.ancestors: 1 823 0 0 824 901 0 0
.ancestors_collapsed: 1 823 824 901 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 339AEC39555C05F59BF1C94520EDBCA0DF7FD36746C5DA88C91625791804B531
| Now we can search for the appropriate tasks, first with:
@@ -13216,7 +12634,6 @@
.ancestors: 1 823 0 0 824 901 0 0
.ancestors_collapsed: 1 823 824 901 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: D0B92B7F6B7A919E3178391541D36F14D5607008AC9747767DAA6B59B59F0D57
| By this command, we discover the task is called, plainly enough, german. Now to find the related tasks:
@@ -13239,7 +12656,6 @@
.ancestors: 1 823 0 0 824 901 0 0
.ancestors_collapsed: 1 823 824 901 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3EC50FDA0BBBE6134804901C0F8DFC7EB7476D9253B1B8BB8CF0D6A27467A30D
.has: links
@@ -13269,7 +12685,6 @@
.ancestors: 1 823 0 0 824 901 0 0
.ancestors_collapsed: 1 823 824 901 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: A57A267D936A45319E8461542D66AF8DBB735D08B6732F6C711D88E676831B32
| Note that we have included the ⑆/┨debian-installer-launcher┣/ package to launch the installer from the live desktop. The ⑆■┨586┣■ kernel flavour, which is currently necessary for the launcher to work properly, will be included by default.
@@ -13356,7 +12771,6 @@
.ancestors: 1 914 0 0 915 916 0 0
.ancestors_collapsed: 1 914 915 916 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 3D7BF31057C5A719B8E2DEB6261B8174C031383668FA2434B9CFBA5E053BDEF4
| This section deals with some general considerations to be taken into account when writing technical documentation for live-manual. They are divided into linguistic features and recommended procedures.
@@ -13367,7 +12781,6 @@
.ancestors: 1 914 0 0 915 916 0 0
.ancestors_collapsed: 1 914 915 916 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: E1D2CADB4C1A2755430718665D78549869E723264C86284DF29A8776A62F9FF6
.has: links
@@ -13396,7 +12809,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 58739E38CA6AC7FCBFAB8103C74D16F4E0D911A6BDFCD94C0BC05659CC9AD021
.bullet: true
@@ -13408,7 +12820,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6C5FE8001212C13B9FC01BE3B0AD17BE19FCCC09BBE92A6CF66B835E766C24DB
| Keep in mind that a high percentage of your readers are not native speakers of English. So as a general rule try to use short, meaningful sentences, followed by a full stop.
@@ -13419,7 +12830,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 36A285DFDD366FB7D7DA00FEC34E5140EF8E911C25753C10D85DB834988F2984
| This does not mean that you have to use a simplistic, naive style. It is a suggestion to try to avoid, as much as possible, complex subordinate sentences that make the text difficult to understand for non-native speakers of English.
@@ -13430,7 +12840,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 523535F3982FD4581E4BDB1CDBF378C42C85651CD49C7507B64CB7D6B587262B
.bullet: true
@@ -13442,7 +12851,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8105BDC93DEE0722DB2A9F9550C8654E5E08F6F5DB1A9573283D6FEB3AD5595B
| The most widely spread varieties of English are British and American so it is very likely that most authors will use either one or the other. In a collaborative environment, the ideal variety would be “International English” but it is very difficult, not to say impossible, to decide on which variety among all the existing ones, is the best to use.
@@ -13453,7 +12861,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2AB4935F93B14D1BF72305DC74F03F18694948D3EC1BB891DFFA774E528CC431
| We expect that different varieties may mix without creating misunderstandings but in general terms you should try to be coherent and before deciding on using British, American or any other English flavour at your discretion, please take a look at how other people write and try to imitate them.
@@ -13464,7 +12871,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: EE866D207E23D1BB12A5E1A6EA4D99521002BD24C39F54CF6707AB22AD8702FB
.bullet: true
@@ -13476,7 +12882,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D3B06B0E8B8E2C146623E159F03CA9478A45329D4B8819137608745625A8AD7E
| Do not be biased. Avoid including references to ideologies completely unrelated to live-manual. Technical writing should be as neutral as possible. It is in the very nature of scientific writing.
@@ -13487,7 +12892,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 37A0F68BD2DA7BC1FFDC7D3380F23769B73B499A3999FB42AA2EF24257CC000D
.bullet: true
@@ -13499,7 +12903,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D4906AC583B0D27327647072B9EB44D62DE0EA98321CFFAD869A5318B60F53FE
| Try to avoid sexist language as much as possible. If you need to make references to the third person singular preferably use “they” rather than “he” or “she” or awkward inventions such as “s/he”, “s(he)” and the like.
@@ -13510,7 +12913,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1174CF4572349040E2E42B545471847791F29C8EE5BA4119CE2AEE464EB1AB13
.bullet: true
@@ -13522,7 +12924,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 9362372353986B6F71FF8CECABDA778BA462C27BC616D5FD38C73AD71DBF1E57
| Go straight to the point and do not wander around aimlessly. Give as much information as necessary but do not give more information than necessary, this is to say, do not explain unnecessary details. Your readers are intelligent. Presume some previous knowledge on their part.
@@ -13533,7 +12934,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 918A15F4B06038174756B0A84F03230BC81F1375685EA956466667DF90AC9C28
.bullet: true
@@ -13545,7 +12945,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B645C74A9DBB4B7C7DD7B066B1B0522785B1750E948F43FBB98E5261593EA3E8
| Keep in mind that whatever you write will have to be translated into several other languages. This implies that a number of people will have to do an extra work if you add useless or redundant information.
@@ -13556,7 +12955,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 881AB896D6C9394C85963BDE49F2CE367D95DC6F7D8179218EA837502B014168
.bullet: true
@@ -13568,7 +12966,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 16909B30C1C36A8D85E3302525CF838E781B04C79ED2C6AFFC529EF4B791F2C6
| As suggested before, it is almost impossible to standardize a collaborative document into a perfectly unified whole. However, every effort on your side to write in a coherent way with the rest of the authors will be appreciated.
@@ -13579,7 +12976,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: F8032C62E00612EF6CE9F0896C1F3206A6BBEB73BB9E1F5F4BFF7BEBDFCE5A43
.bullet: true
@@ -13591,7 +12987,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BF535E6FB1E7E28F1967077C056C8047C2951F0A8D6FA073C4FCF0ACF1690066
| Use as many text-forming devices as necessary to make your text cohesive and unambiguous. (Text-forming devices are linguistic markers such as connectors).
@@ -13602,7 +12997,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 999EACA48D8A607B9E43CF6356C91A76734D9966DEEA5B84AACD803AD89569A7
.bullet: true
@@ -13614,7 +13008,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 62BC9AEB1B70983EE782DC9272B13307EA92D3FAD9D7A5D53C1AD8F0FD3D269B
| It is preferable to describe the point in one or several paragraphs than merely using a number of sentences in a typical “changelog” style. Describe it! Your readers will appreciate it.
@@ -13625,7 +13018,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8DF049844058682E26E004BA33CA7A57532BBA3F9BF3CF6990183DAD6852D621
.bullet: true
@@ -13637,7 +13029,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: A95C5F1543DF3355C0E1826D91F015E712EFE5E06C4CC9D54AD2EE60591DF151
| Look up the meaning of words in a dictionary or encyclopedia if you do not know how to express certain concepts in English. But keep in mind that a dictionary can either be your best friend or can turn into your worst enemy if you do not know how to use it correctly.
@@ -13648,7 +13039,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 74C24D4DAF20D1ED6ACE02530DB3CFE6765B031F1FE74CCC1A1EFE2DB75FA1F2
| English has the largest vocabulary that exists (with over one million words). Many of these words are borrowings from other languages. When looking up the meaning of words in a bilingual dictionary the tendency of a non-native speaker of English is to choose the one that sounds more similar in their mother tongue. This often turns into an excessively formal discourse which does not sound quite natural in English.
@@ -13659,7 +13049,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 58AB8B0DAB8FDC4E9EF321B182C6D8CCB0BF89C304D895E16491E996DF874CFD
| As a general rule, if a concept can be expressed using different synonyms, it is a good advice to choose the first word proposed by the dictionary. If in doubt, choosing words of Germanic origin (Usually monosyllabic words) is often the right thing to do. Be warned that these two techniques might produce a rather informal discourse but at least your choice of words will be of wide use and generally accepted.
@@ -13670,7 +13059,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 94BF7A962810086C60C6C5925AAB1288897E65A1D2255F1F24D046229F5BC428
| Using a dictionary of collocations is recommended. They are extremely helpful when it comes to know which words usually occur together.
@@ -13681,7 +13069,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: FF758BE965CE4E428B8363C0F0293C75BB62F7F2E2E65259730F20DFABBAC071
| Again it is a good practice to learn from the work of others. Using a search engine to check how other authors use certain expressions may help a lot.
@@ -13692,7 +13079,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 3DF5485222263EFD3D43C4BEE8198A78E11F8E851B87D9174AACD969BCB51B6E
.bullet: true
@@ -13704,7 +13090,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D44FCDB9831AB6025A6FF90613CF0E43819E67F5895795C1D5ACB814B95273BF
| Watch out for false friends. No matter how proficient you are in a foreign language you cannot help falling from time to time in the trap of the so called “false friends”, words that look similar in two languages but whose meanings or uses might be completely different.
@@ -13715,7 +13100,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8497920BDD4C3BE0021ABC705BA2998DAB9DC686E039A0A530858904F65621E4
| Try to avoid idioms as much as possible. “Idioms” are expressions that may convey a completely different meaning from what their individual words seem to mean. Sometimes, idioms might be difficult to understand even for native speakers of English!
@@ -13726,7 +13110,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 15D5388434457142341AD69AF59FABCEC61B04417670DA7AEA8FB79094923417
.bullet: true
@@ -13738,7 +13121,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6AF00DEC375B4CC69C1C394191DE527276A654C4DB3F1B8CCE4DA9894647A05B
| Even though you are encouraged to use plain, everyday English, technical writing belongs to the formal register of the language.
@@ -13749,7 +13131,6 @@
.ancestors: 1 914 0 0 915 916 919 0
.ancestors_collapsed: 1 914 915 916 919 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: FD8E6B504EC8B2BE9BE6AD3947411C08CB2BB7F25D6A944982751B5167A1BCFC
| Try to avoid slang, unusual abbreviations that are difficult to understand and above all contractions that try to imitate the spoken language. Not to mention typical irc and family friendly expressions.
@@ -13777,7 +13158,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1EB737E9E3AA551F19CFC1CBCAB59ADE146B99A339E812183370046704EDE292
.bullet: true
@@ -13789,7 +13169,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1865D8C8E376018EE6A94479C11477D381839B7C1DA574119F48D196D7C765F9
| It is important that authors test their examples before adding them to live-manual to ensure that everything works as described. Testing on a clean chroot or VM can be a good starting point. Besides, it would be ideal if the tests were then carried out on different machines with different hardware to spot possible problems that may arise.
@@ -13800,7 +13179,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 55A9610C7FE68A5903EA6B6056BF3CE3D4DE3746417123627172CAE22ABD911F
.bullet: true
@@ -13812,7 +13190,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 92E2E2FE8D905A39DE68AB621499208A15AB5F170C24FD569541409A682C5E4A
| When providing an example try to be as specific as you can. An example is, after all, just an example.
@@ -13823,7 +13200,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6CE4BF819216AFAE12A1B1B6359EB16A6406DB17F06F44CBB3211BA9112999E1
| It is often better to use a line that only applies to a specific case than using abstractions that may confuse your readers. In this case you can provide a brief explanation of the effects of the proposed example.
@@ -13834,7 +13210,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: CF79347FAA65DAFA5B00A6C35EEEF9998083F06496F59099E97590D2806093F1
| There may be some exceptions when the example suggests using some potentially dangerous commands that, if misused, may cause data loss or other similar undesirable effects. In this case you should provide a thorough explanation of the possible side effects.
@@ -13845,7 +13220,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 013F7583A1A01A90F197AB442C7C82E4DA3D38A32AD6037DC3E2712F686A86C1
.bullet: true
@@ -13857,7 +13231,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7F79C2036BA2DAC9C58DCDBFD1F4E10EB2113A503F213D223C8065B9BED23687
| Links to external sites should only be used when the information on those sites is crucial when it comes to understanding a special point. Even so, try to use links to external sites as sparsely as possible. Internet links are likely to change from time to time resulting in broken links and leaving your arguments in an incomplete state.
@@ -13868,7 +13241,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 3995E7A0DCDA2D8AD2B6D558993C2DA7A2A50817EAB28116E5CD20D94B0012E5
| Besides, people who read the manual offline will not have the chance to follow those links.
@@ -13879,7 +13251,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2313CDEA536B96F58BADCF42B88FF08F20C5BAC63941E11C5244F56BF50CF240
.bullet: true
@@ -13891,7 +13262,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 0D00E25FAFEAB1AD72AAE8EF8096F2630D0B0935647350339AD999ACAB4A929A
| Try to avoid branding as much as possible. Keep in mind that other downstream projects might make use of the documentation you write. So you are complicating things for them if you add certain specific material.
@@ -13902,7 +13272,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BB01A87EAC5A1E26460569C2EFF214CF54498383CBA65F84BE3CDB6E2EC49486
| live-manual is licensed under the GNU GPL. This has a number of implications that apply to the distribution of the material (of any kind, including copyrighted graphics or logos) that is published with it.
@@ -13913,7 +13282,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 61D03D4E63BA46FB0C498C5A3F1EC3DD61805464289BF17A30D2B0D3ECCF58D0
.bullet: true
@@ -13925,7 +13293,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1CE1632D7BD5C84D51E174AF937CEBE30D15F93C87D2D44391133AC322BBE8D8
| - Brainstorm!. You need to organize your ideas first in a logical sequence of events.
@@ -13936,7 +13303,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 59AA1B62B176D6B1B07ADEE8A504EEBE642906FD0E021511EB182730CD85E304
| - Once you have somehow organized those ideas in your mind write a first draft.
@@ -13947,7 +13313,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 8E3E72FB8D0B678547827A1794160C21316BBA1F21ADBDC3BD865FD1DB09CDD2
| - Revise grammar, syntax and spelling. Keep in mind that the proper names of the releases, such as ${testing} or sid, should not be capitalized when referred to as code names. In order to check the spelling you can run the “spell” target. i.e. ⑆■┨make spell┣■
@@ -13958,7 +13323,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 90DE64A3A7D965619503B63C89E99D45F1B7087EC6B8F193287D66BAEA05CA0D
| - Improve your statements and redo any part if necessary.
@@ -13969,7 +13333,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: E8F16DF79930F43E41FB814C31764EF54242D8411524660893937C5A48A184BF
.bullet: true
@@ -13981,7 +13344,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C786A24C2CB874892F4BC20E315DFB82DD88C9AD551BDCFA83D73D724025F802
| Use the conventional numbering system for chapters and subtitles. e.g. 1, 1.1, 1.1.1, 1.1.2 ... 1.2, 1.2.1, 1.2.2 ... 2, 2.1 ... and so on. See markup below.
@@ -13992,7 +13354,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 3C0E9186DDB2C3DC9C4D5DC327A9A57F80F47E8B5F01314D4D7254C26CF490EF
| If you have to enumerate a series of steps or stages in your description, you can also use ordinal numbers: First, second, third ... or First, Then, After that, Finally ... Alternatively you can use bulleted items.
@@ -14003,7 +13364,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2496FD78E4AF25D968DA0EBCDE21C6E7696F42828DD10B8A7934653F1DF0599D
.bullet: true
@@ -14015,7 +13375,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C6C0A1FD3658D01EC11EB6A61EE1E54C55DE9E4B023F69624EBED1FC61929BC1
.has: links
@@ -14039,7 +13398,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 641131990CEBEE17D06F96C3FC58D0F36D46184637015D3C079DED17828F2E06
| Here are some markup examples that may prove useful:
@@ -14050,7 +13408,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: DC9E22C20DC35C3E0008F18834638DA2877DB343471CDEAE0BDBB832B64B32CF
| - For emphasis/bold text:
@@ -14071,7 +13428,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 61595FD1502968579A7AE104A9F2880498A650FF504F6AFF1B7F6A8DF36BEC69
| produces: ⑆*┨foo┣* or ⑆!┨foo┣!. Use it to emphasize certain key words.
@@ -14082,7 +13438,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 437AA729509D76C6BD3619B32CF214129BB76D52D92FDBB7AAD61BFDA38DD2D9
| - For italics:
@@ -14103,7 +13458,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B3518AE9811EAB6983C60093D9B50796C2083AED3A22F1609646AC3D2F9D6D2E
| produces: ⑆/┨foo┣/. Use them e.g. for the names of Debian packages.
@@ -14114,7 +13468,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: BB283248096FA10FBA5519A89E4D5ADF4EC5B2B2B3A4D779B7918100732C14B8
| - For monospace:
@@ -14135,7 +13488,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: F5C6EE1D673D21B51FB9D216D9C191269F3E820BC86EB6BB0876FB1D3E8584C9
| produces: ⑆■┨foo┣■. Use it e.g. for the names of commands. And also to highlight some key words or things like paths.
@@ -14146,7 +13498,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 02705FAFF24CA6860C8F542DFB8D20F5157384A76A4B54DB56793D3AC58D9B0C
| - For code blocks:
@@ -14172,7 +13523,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1F70DA180C4EFEBF09E8E052D32790F24016329F440B5C55BA66F8FA2F9D36EF
| produces:
@@ -14194,7 +13544,6 @@
.ancestors: 1 914 0 0 915 916 952 0
.ancestors_collapsed: 1 914 915 916 952 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 3EE14AC8FDCA52CEC0D5BEB3668E5D9CA05B1040F5E1D5984A65563090D9EFB5
| Use ⑆■┨code{┣■ to open and ⑆■┨}code┣■ to close the tags. It is important to remember to leave a space at the beginning of each line of code.
@@ -14224,7 +13573,6 @@
.ancestors: 1 914 0 0 915 991 0 0
.ancestors_collapsed: 1 914 915 991 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 728F8AB8DD86AB3C43FC42C9C7A4CD950C46954A4A6CC095876A429658E2A6A0
| This section deals with some general considerations to be taken into account when translating the contents of live-manual.
@@ -14235,7 +13583,6 @@
.ancestors: 1 914 0 0 915 991 0 0
.ancestors_collapsed: 1 914 915 991 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 7D88CA13E43D6DF657C259D8BF693FD9778029A4BDFBA720FF79648EB651FD35
| As a general recommendation, translators should have read and understood the translation rules that apply to their specific languages. Usually, translation groups and mailing lists provide information on how to produce translated work that complies with Debian quality standards.
@@ -14246,7 +13593,6 @@
.ancestors: 1 914 0 0 915 991 0 0
.ancestors_collapsed: 1 914 915 991 0 0 0 0
.parent_lev: 5
-.ocn_off: true
.is_of_type: para
.sha256: 1B985BA983BD637F0D688E53C2C5DCCABB2C37FC04A7FF37450D208D7FE1EC5B
.has: links
@@ -14275,7 +13621,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6D4CA66D7828C00E4B0ECC78AC60AD7D8CDC7C750911E81E1504E711E7F0BDFF
.bullet: true
@@ -14287,7 +13632,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 45BE05B5A81F9725A5B67513045C3FBD328B7C2E79A43ADD68EAB5E115D60B90
| The role of the translator is to convey as faithfully as possible the meaning of words, sentences, paragraphs and texts as written by the original authors into their target language.
@@ -14298,7 +13642,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: DBFCDE0B23B9467538C44600CB963F9EA96E28BA8B650DC9C8F11F919F5CBB74
| So they should refrain from adding personal comments or extra bits of information of their own. If they want to add a comment for other translators working on the same documents, they can leave it in the space reserved for that. That is, the header of the strings in the ⑆*┨po┣* files preceded by a number sign ⑆*┨#┣*. Most graphical translation programs can automatically handle those types of comments.
@@ -14309,7 +13652,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: CF1E1E01C814A1E700BADC348D1129941F445AE83FABE8D57EE823B3DE2A6608
.bullet: true
@@ -14321,7 +13663,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B4ABC561DC4857FC2ED7E6AAD2E4C3D92B0EF01A5EFEC611B35A56B86F32696F
| It is perfectly acceptable however, to include a word or an expression in brackets in the translated text if, and only if, that makes the meaning of a difficult word or expression clearer to the reader. Inside the brackets the translator should make evident that the addition was theirs using the abbreviation “TN” or “Translator's Note”.
@@ -14332,7 +13673,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: D0FE0F82EB7662112735B548FFACEC0D333AD0327A0ECB322DAB65602DF8004C
.bullet: true
@@ -14344,7 +13684,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: ADD16658A0C6141C84D8FDB3FC869393376481D3FD91A79400E23F10F50D93AC
| Documents written in English make an extensive use of the impersonal form “you”. In some other languages that do not share this characteristic, this might give the false impression that the original texts are directly addressing the reader when they are actually not doing so. Translators must be aware of that fact and reflect it in their language as accurately as possible.
@@ -14355,7 +13694,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: CC13F103FF05AF3741F18BF0847338A398AA2A32CA69E9657DAAF3120E04A230
.bullet: true
@@ -14367,7 +13705,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: F8D6F49E2B09CDC8C0C51D788D4EDA72D34E371A3B17CC725F4D9976A7922AC0
| The trap of “false friends” explained before especially applies to translators. Double check the meaning of suspicious false friends if in doubt.
@@ -14378,7 +13715,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2496FD78E4AF25D968DA0EBCDE21C6E7696F42828DD10B8A7934653F1DF0599D
.bullet: true
@@ -14390,7 +13726,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: C53501383F3C4668BE88415473CBBF4B9A41D15D5C3C13F8EFB894900E29E99D
| Translators working initially with ⑆*┨pot┣* files and later on with ⑆*┨po┣* files will find many markup features in the strings. They can translate the text anyway, as long as it is translatable, but it is extremely important that they use exactly the same markup as the original English version.
@@ -14401,7 +13736,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 6457D042A6D0835CCDE22C36402831559BCFD1D0DB3C794C9062C1F13F4631DE
.bullet: true
@@ -14413,7 +13747,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: B5E1B829D2A9F4AF8C9664987D626B0624BD606AAA13A84C3CB02D471C698208
| Even though the code blocks are usually untranslatable, including them in the translation is the only way to score a 100% complete translation. And even though it means more work at first because it might require the intervention of the translators if the code changes, it is the best way, in the long run, to identify what has already been translated and what has not when checking the integrity of the .po files.
@@ -14424,7 +13757,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 9116ECDAF4A2ECBE6B0396AB14B30B42EDC874434DEB38634EEA4F45A1FC6C57
.bullet: true
@@ -14436,7 +13768,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 7DEF9965F9F6AD469351C9B4CE8A38DCDBAC619629753481DD607F9BF4178535
| The translated texts need to have the exact same newlines as the original texts. Be careful to press the “Enter” key or type ⑆*┨\n┣* if they appear in the original files. These newlines often appear, for instance, in the code blocks.
@@ -14447,7 +13778,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 315D6B3AFCE964F26E1AD8A3BDB6C2E7A224E4B838DD002BEBF7B2F9E4BC4FC2
| Make no mistake, this does not mean that the translated text needs to have the same length as the English version. That is nearly impossible.
@@ -14458,7 +13788,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 12278699F524587AA859B9D17AFAFB46379DA3F64B6653F4AABE9832CBAA5400
.bullet: true
@@ -14470,7 +13799,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2BAEE8CB8304AFC27E70DD8987A1F56BDAC58CD10BF1925D60D3DD833C2C25B3
| Translators should never translate:
@@ -14481,7 +13809,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 219AD96CFA4A58CA0807A28FA5B18E875C84D7E51E3AAB9FD69B63203A0DD8B6
| - The code names of releases (which should be written in lowercase)
@@ -14492,7 +13819,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: A0542C0F563E9E0943A6DC9351930CE8B727100BA5131213786A6F6AF38F49D0
| - The names of programs
@@ -14503,7 +13829,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: F40F10CA886CA9E5017C52E47D5ABEEFA33BBBBBBA25A46A2DC303D641BF1CFD
| - The commands given as examples
@@ -14514,7 +13839,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 9046FCE9858AA18F0B2ADA685BD5501321F0CB2CBD5C8BD7ECC1BEFE6BF4807D
| - Metadata (often between colons ⑆*┨:metadata:┣*)
@@ -14525,7 +13849,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 1E2DA35F669831F16DA73B8A260EA2FA84C65F090F359C0D4D5C361A57E5513A
| - Links
@@ -14536,7 +13859,6 @@
.ancestors: 1 914 0 0 915 991 995 0
.ancestors_collapsed: 1 914 915 991 995 0 0 0
.parent_lev: 6
-.ocn_off: true
.is_of_type: para
.sha256: 2F81D17AA7408BEB2B1AE1158BDDAAE703CC5BCCC81BBA080A642973A68E3483
| - Paths