From f574e1127a225e2de2e77a6b9e46a65986789f1f Mon Sep 17 00:00:00 2001 From: Joachim Wiedorn Date: Sun, 9 Jun 2013 21:14:10 +0200 Subject: [PATCH] Imported Upstream version 24.0 --- CHANGELOG | 28 + COPYING | 2 +- Makefile | 7 +- NEWS | 13 +- TODO | 6 +- TOOLS | 12 +- doc/{Makefile => Makefile.old} | 0 doc/html/index.html | 45 + doc/html/tech_21-5.css | 141 + doc/html/tech_21-5.html | 522 ++++ doc/html/tech_21-50x.png | Bin 0 -> 15263 bytes doc/html/tech_21-51x.png | Bin 0 -> 6847 bytes doc/html/tech_21-52.html | 22 + doc/html/tech_21-52x.png | Bin 0 -> 3084 bytes doc/html/tech_21-53.html | 22 + doc/html/tech_21-53x.png | Bin 0 -> 10755 bytes doc/html/tech_21-54x.png | Bin 0 -> 6384 bytes doc/html/tech_21-55x.png | Bin 0 -> 6707 bytes doc/html/user_21-5.css | 152 ++ doc/html/user_21-5.html | 4412 ++++++++++++++++++++++++++++++++ doc/html/user_21-50x.png | Bin 0 -> 843 bytes doc/html/user_21-510.html | 31 + doc/html/user_21-510x.png | Bin 0 -> 1934 bytes doc/html/user_21-511.html | 24 + doc/html/user_21-511x.png | Bin 0 -> 1444 bytes doc/html/user_21-512.html | 28 + doc/html/user_21-512x.png | Bin 0 -> 1986 bytes doc/html/user_21-513.html | 26 + doc/html/user_21-513x.png | Bin 0 -> 3501 bytes doc/html/user_21-514.html | 106 + doc/html/user_21-514x.png | Bin 0 -> 2774 bytes doc/html/user_21-515.html | 24 + doc/html/user_21-516.html | 52 + doc/html/user_21-517.html | 24 + doc/html/user_21-518.html | 30 + doc/html/user_21-519.html | 24 + doc/html/user_21-51x.png | Bin 0 -> 3123 bytes doc/html/user_21-52.html | 23 + doc/html/user_21-520.html | 27 + doc/html/user_21-520x.png | Bin 0 -> 13708 bytes doc/html/user_21-521.html | 27 + doc/html/user_21-521x.png | Bin 0 -> 3658 bytes doc/html/user_21-522.html | 26 + doc/html/user_21-522x.png | Bin 0 -> 6291 bytes doc/html/user_21-523.html | 26 + doc/html/user_21-524.html | 22 + doc/html/user_21-525.html | 30 + doc/html/user_21-526.html | 22 + doc/html/user_21-527.html | 24 + doc/html/user_21-528.html | 24 + doc/html/user_21-529.html | 27 + doc/html/user_21-52x.png | Bin 0 -> 1579 bytes doc/html/user_21-53.html | 27 + doc/html/user_21-530.html | 24 + doc/html/user_21-53x.png | Bin 0 -> 3188 bytes doc/html/user_21-54.html | 30 + doc/html/user_21-54x.png | Bin 0 -> 2095 bytes doc/html/user_21-55.html | 28 + doc/html/user_21-55x.png | Bin 0 -> 2321 bytes doc/html/user_21-56.html | 26 + doc/html/user_21-56x.png | Bin 0 -> 3299 bytes doc/html/user_21-57.html | 24 + doc/html/user_21-574x.png | Bin 0 -> 7089 bytes doc/html/user_21-57x.png | Bin 0 -> 2861 bytes doc/html/user_21-58.html | 36 + doc/html/user_21-58x.png | Bin 0 -> 4071 bytes doc/html/user_21-59.html | 34 + doc/html/user_21-59x.png | Bin 0 -> 2935 bytes lilo.lsm | 8 +- make.vars | 2 +- man/Makefile | 34 +- man/lilo-uuid-diskid.8 | 118 + man/lilo-uuid-diskid.pod | 71 + man/lilo.8 | 946 ++++--- man/lilo.conf.5 | 94 +- man/lilo.pod | 451 ++++ man/liloconfig.8 | 151 ++ man/liloconfig.pod | 105 + man/pod2manpage | 80 + mkrescue | 100 +- sample/lilo.old-raid.conf | 21 - scripts/liloconfig | 48 +- src/Makefile | 9 +- src/bdata.h | 2 +- src/biosdata.S | 10 +- src/bitmap.S | 11 +- src/bitmap.h | 2 +- src/boot.h | 2 +- src/bsect.c | 2 +- src/bsect.h | 2 +- src/cfg.c | 2 +- src/cfg.h | 2 +- src/chain.S | 11 +- src/common.c | 21 +- src/common.h | 22 +- src/config.h | 21 +- src/crt.S | 17 +- src/device.c | 20 +- src/device.h | 19 +- src/disk.S | 16 +- src/display4.S | 33 +- src/dparam.S | 18 +- src/dump.S | 19 +- src/edit.c | 18 +- src/edit.h | 21 +- src/first.S | 19 +- src/geometry.c | 62 +- src/geometry.h | 19 +- src/graph.S | 18 +- src/identify.c | 22 +- src/identify.h | 20 +- src/lilo.c | 4 +- src/lilo.h | 13 +- src/loader.h | 19 +- src/map.c | 21 +- src/map.h | 20 +- src/mapper.S | 13 +- src/mbr.S | 11 +- src/md-int.h | 7 +- src/menu.S | 18 +- src/partition.c | 42 +- src/partition.h | 22 +- src/probe.c | 22 +- src/probe.h | 19 +- src/pseudo.S | 17 +- src/raid.c | 18 +- src/raid.h | 18 +- src/read.S | 17 +- src/second.S | 20 +- src/shs2.c | 11 +- src/shs2.h | 6 +- src/shs3.S | 17 +- src/strlen.S | 18 +- src/temp.h | 19 +- src/version.h | 16 +- src/vesainfo.h | 18 +- src/volume.S | 18 +- 137 files changed, 8281 insertions(+), 1112 deletions(-) rename doc/{Makefile => Makefile.old} (100%) create mode 100644 doc/html/index.html create mode 100644 doc/html/tech_21-5.css create mode 100644 doc/html/tech_21-5.html create mode 100644 doc/html/tech_21-50x.png create mode 100644 doc/html/tech_21-51x.png create mode 100644 doc/html/tech_21-52.html create mode 100644 doc/html/tech_21-52x.png create mode 100644 doc/html/tech_21-53.html create mode 100644 doc/html/tech_21-53x.png create mode 100644 doc/html/tech_21-54x.png create mode 100644 doc/html/tech_21-55x.png create mode 100644 doc/html/user_21-5.css create mode 100644 doc/html/user_21-5.html create mode 100644 doc/html/user_21-50x.png create mode 100644 doc/html/user_21-510.html create mode 100644 doc/html/user_21-510x.png create mode 100644 doc/html/user_21-511.html create mode 100644 doc/html/user_21-511x.png create mode 100644 doc/html/user_21-512.html create mode 100644 doc/html/user_21-512x.png create mode 100644 doc/html/user_21-513.html create mode 100644 doc/html/user_21-513x.png create mode 100644 doc/html/user_21-514.html create mode 100644 doc/html/user_21-514x.png create mode 100644 doc/html/user_21-515.html create mode 100644 doc/html/user_21-516.html create mode 100644 doc/html/user_21-517.html create mode 100644 doc/html/user_21-518.html create mode 100644 doc/html/user_21-519.html create mode 100644 doc/html/user_21-51x.png create mode 100644 doc/html/user_21-52.html create mode 100644 doc/html/user_21-520.html create mode 100644 doc/html/user_21-520x.png create mode 100644 doc/html/user_21-521.html create mode 100644 doc/html/user_21-521x.png create mode 100644 doc/html/user_21-522.html create mode 100644 doc/html/user_21-522x.png create mode 100644 doc/html/user_21-523.html create mode 100644 doc/html/user_21-524.html create mode 100644 doc/html/user_21-525.html create mode 100644 doc/html/user_21-526.html create mode 100644 doc/html/user_21-527.html create mode 100644 doc/html/user_21-528.html create mode 100644 doc/html/user_21-529.html create mode 100644 doc/html/user_21-52x.png create mode 100644 doc/html/user_21-53.html create mode 100644 doc/html/user_21-530.html create mode 100644 doc/html/user_21-53x.png create mode 100644 doc/html/user_21-54.html create mode 100644 doc/html/user_21-54x.png create mode 100644 doc/html/user_21-55.html create mode 100644 doc/html/user_21-55x.png create mode 100644 doc/html/user_21-56.html create mode 100644 doc/html/user_21-56x.png create mode 100644 doc/html/user_21-57.html create mode 100644 doc/html/user_21-574x.png create mode 100644 doc/html/user_21-57x.png create mode 100644 doc/html/user_21-58.html create mode 100644 doc/html/user_21-58x.png create mode 100644 doc/html/user_21-59.html create mode 100644 doc/html/user_21-59x.png create mode 100644 man/lilo-uuid-diskid.8 create mode 100644 man/lilo-uuid-diskid.pod create mode 100644 man/lilo.pod create mode 100644 man/liloconfig.8 create mode 100644 man/liloconfig.pod create mode 100644 man/pod2manpage diff --git a/CHANGELOG b/CHANGELOG index 287b813..b468412 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,3 +1,31 @@ +Changes for version 24.0 (unreleased) - Joachim Wiedorn + + Documentations + -------------- + - Update of lilo.conf.5 manpage with some corrections. + - Add new manpages as pod files (sources): + * liloconfig.pod (from Debian) + * lilo-uuid-diskid.pod (from Debian) + * lilo.pod (converted from lilo.8) + - Add script man/pod2manpages for converting pod files. + - Create manpages from pod files. + - Deactivate Makefile for docs. Don't generate html/pdf. + - Add complete html documentation for history (v21.5). + + Sources + ------- + - Support for kernel images on GPT hard disks in the first 15 + partitions, otherwise set comments (src/geometry.c, src/lilo.h) + - Update src/Makefile to always stipping lilo and lilo.static. + + General + ------- + - Fix abort problem in script mkrescue. (thanks to S. R. Wright) + - Update script liloconf to find kernel versions 3.x, too. + - Remove some more hints to obsolete OS/2 (source, doc). + - Fix to be compatible to gcc 4.8 and higher (use -ffreestanding) + + Changes for version 23.2 (09-Apr-2011) - Joachim Wiedorn Documentations diff --git a/COPYING b/COPYING index 0586be0..d18efbd 100644 --- a/COPYING +++ b/COPYING @@ -2,7 +2,7 @@ LInux LOader (LILO) program code, documentation, and auxiliary programs: Copyright 1992-1998 Werner Almesberger Copyright 1999-2007 John Coffman -Copyright 2009-2011 Joachim Wiedorn +Copyright 2009-2013 Joachim Wiedorn All rights reserved. diff --git a/Makefile b/Makefile index e16f6bb..f135b42 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ # -*- makefile -*- # -# Copyright 2009-2011 Joachim Wiedorn +# Copyright 2009-2013 Joachim Wiedorn # All rights reserved. # # Licensed under the terms contained in the file 'COPYING' @@ -17,7 +17,7 @@ help: @echo " make dosexe # DOS lilo.com utility" @echo " make diagnostic # standalone diagnostics" @echo " make alles # all above + static binary" - @echo " make docs # doc/[user,tech].[pdf,dvi] docs" + @echo " make docs # doc/[user,tech].html docs" @echo " make floppy # 2 standalone bootable diagnostic floppies" @echo "" @echo " make install # install binaries++ into root directory" @@ -51,7 +51,6 @@ alles: test # documentation files # docs: - $(MAKE) -C doc all # # if you have the 'bcc' compiler, then you can make the diagnostics, too @@ -116,7 +115,6 @@ tidy: $(MAKE) -C src tidy $(MAKE) -C diagnose tidy $(MAKE) -C dos tidy - $(MAKE) -C doc tidy clean: tidy rm -f test.img @@ -124,7 +122,6 @@ clean: tidy $(MAKE) -C images clean $(MAKE) -C diagnose clean $(MAKE) -C dos clean - $(MAKE) -C doc clean spotless: distclean distclean: clean diff --git a/NEWS b/NEWS index 0de9b0b..83b9b21 100644 --- a/NEWS +++ b/NEWS @@ -3,7 +3,16 @@ NEWS about project LILO (For details see file 'CHANGELOG' in the source directory) -Version 23.2 (major and bugfix update of 23.1) +Version 24.0 (major and bugfix update of 23.2) + + o Update many manpages and add some from Debian. + o Add old documentation as (static) html. + o Better support for GPT hard disks. + o Support for use with kernel 3.x. + o Fix to be compatible with gcc 4.8 and higher. + + +Version 23.2 (minor and bugfix update of 23.1) o Many fixes in source code and fixes for some error messages. o Remove all obsolete OS/2 code and information. @@ -13,7 +22,7 @@ Version 23.2 (major and bugfix update of 23.1) o Add new scripts 'liloconfig' and 'lilo-uuid-diskid'. -Version 23.1 (major and bugfix update of 23.0) +Version 23.1 (minor and bugfix update of 23.0) o Many fixes of typos in sources and documentation. o LVM volumes can now be used as root device. diff --git a/TODO b/TODO index 1e7dbdf..66ac4b9 100644 --- a/TODO +++ b/TODO @@ -5,10 +5,8 @@ TODO for project LILO behaviour of 'large-memory'. * patching sources because of some warnings while compiling - with gcc 4.4.x + with gcc 4.4.x and higher -* Upgrade of all manpages. - -* Upgrade of all documentations. +* Upgrade of all manpages (move to po files). * code cleanup. diff --git a/TOOLS b/TOOLS index 764f36d..ff3427d 100644 --- a/TOOLS +++ b/TOOLS @@ -8,17 +8,17 @@ they can be found in: at least tested programs package version until inside ----------------------------------------------------------------- -coreutils 6.4.10 8.5 (general) +coreutils 6.4.10 8.13 (general) bcc 0.16.14 0.16.17 bcc bin86 0.16.14 0.16.17 as86, ld86 -gcc 3.3.5 4.4.5 gcc +gcc 3.3.5 4.8.0 gcc -sharutils 4.6.3 4.9 uuencode, uudecode +sharutils 4.6.3 4.11.1 uuencode, uudecode -texlive-latex-base 2007-01 2009-11 ifpdf.sty +perl 5.8.4 5.14.2 pod2man @@ -32,8 +32,8 @@ they can be found in: at least tested programs package version until inside ----------------------------------------------------------------- -perl 5.8.8 5.10.1 (general) +perl 5.8.8 5.14.2 (general) -perl-modules 5.8.8 5.10.1 Getopt::Std, +perl-modules 5.8.8 5.14.2 Getopt::Std, Pod::Usage File::Copy diff --git a/doc/Makefile b/doc/Makefile.old similarity index 100% rename from doc/Makefile rename to doc/Makefile.old diff --git a/doc/html/index.html b/doc/html/index.html new file mode 100644 index 0000000..55a36c6 --- /dev/null +++ b/doc/html/index.html @@ -0,0 +1,45 @@ + + + + +LILO +Generic boot loader for Linux +Version 21.5 Documentation + + + + + +
+ + + +

LILO
+Generic boot loader for Linux
+Version 21.5
+July 17, 2000

+ +

Documentation

+ +

User’s guide
+(written by Werner Almesberger and John R. Coffman)
+

+ +

Technical overview
+(written by Werner Almesberger and John R. Coffman)
+

+ +


+(Documentation reconstructed by Joachim Wiedorn on January 29, 2011)
+

+ + + + + diff --git a/doc/html/tech_21-5.css b/doc/html/tech_21-5.css new file mode 100644 index 0000000..cba9cc6 --- /dev/null +++ b/doc/html/tech_21-5.css @@ -0,0 +1,141 @@ + +/* start css.sty */ + +description { margin-top: 1em; } +dt.description { margin-top: 1em; } +dd.description { margin-top: 0.5em; } + +.line-10{font-size:90%;} +.cmr-10{font-size:90%;} +.cmr-10x-x-109{} +.cmr-17{font-size:154%;} +.cmr-12x-x-120{font-size:130%;} +.cmbx-12x-x-120{font-size:130%; font-weight: bold;} +.cmbx-12x-x-120{ font-weight: bold;} +.cmr-12{font-size:109%;} +.cmr-6{font-size:54%;} +.cmti-12{font-size:109%; font-style: italic;} +.cmtt-10x-x-109{font-family: monospace;} +.cmtt-10x-x-109{font-family: monospace;} +.cmbx-10x-x-109{ font-weight: bold;} +.cmbx-10x-x-109{ font-weight: bold;} +.cmss-10x-x-109{ font-family: sans-serif;} +.cmr-9{font-size:81%;} +.cmtt-10{font-size:90%;font-family: monospace;} +.cmtt-10{font-family: monospace;} +.cmti-10x-x-109{ font-style: italic;} +p.noindent { text-indent: 0em } +td p.noindent { text-indent: 0em; margin-top:0em; } +p.nopar { text-indent: 0em; } +p.indent{ text-indent: 1.5em } +@media print {div.crosslinks {visibility:hidden;}} +a img { border-top: 0; border-left: 0; border-right: 0; } +center { margin-top:1em; margin-bottom:1em; } +td center { margin-top:0em; margin-bottom:0em; } +.Canvas { position:relative; } +img.math{vertical-align:middle;} +li p.indent { text-indent: 0em } +li p:first-child{ margin-top:0em; } +li p:last-child, li div:last-child { margin-bottom:0.5em; } +li p~ul:last-child, li p~ol:last-child{ margin-bottom:0.5em; } +.enumerate1 {list-style-type:decimal;} +.enumerate2 {list-style-type:lower-alpha;} +.enumerate3 {list-style-type:lower-roman;} +.enumerate4 {list-style-type:upper-alpha;} +div.newtheorem { margin-bottom: 2em; margin-top: 2em;} +.obeylines-h,.obeylines-v {white-space: nowrap; } +div.obeylines-v p { margin-top:0; margin-bottom:0; } +.overline{ text-decoration:overline; } +.overline img{ border-top: 1px solid black; } +td.displaylines {text-align:center; white-space:nowrap;} +.centerline {text-align:center;} +.rightline {text-align:right;} +div.verbatim {font-family: monospace; white-space: nowrap; text-align:left; clear:both; } +.fbox {padding-left:3.0pt; padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; } +div.fbox {display:table} +div.center div.fbox {text-align:center; clear:both; padding-left:3.0pt; padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; } +div.minipage{width:100%;} +div.center, div.center div.center {text-align: center; margin-left:1em; margin-right:1em;} +div.center div {text-align: left;} +div.flushright, div.flushright div.flushright {text-align: right;} +div.flushright div {text-align: left;} +div.flushleft {text-align: left;} +.underline{ text-decoration:underline; } +.underline img{ border-bottom: 1px solid black; margin-bottom:1pt; } +.framebox-c, .framebox-l, .framebox-r { padding-left:3.0pt; padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; } +.framebox-c {text-align:center;} +.framebox-l {text-align:left;} +.framebox-r {text-align:right;} +span.thank-mark{ vertical-align: super } +span.footnote-mark sup.textsuperscript, span.footnote-mark a sup.textsuperscript{ font-size:80%; } +div.tabular, div.center div.tabular {text-align: center; margin-top:0.5em; margin-bottom:0.5em; } +table.tabular td p{margin-top:0em;} +table.tabular {margin-left: auto; margin-right: auto;} +td p:first-child{ margin-top:0em; } +td p:last-child{ margin-bottom:0em; } +div.td00{ margin-left:0pt; margin-right:0pt; } +div.td01{ margin-left:0pt; margin-right:5pt; } +div.td10{ margin-left:5pt; margin-right:0pt; } +div.td11{ margin-left:5pt; margin-right:5pt; } +table[rules] {border-left:solid black 0.4pt; border-right:solid black 0.4pt; } +td.td00{ padding-left:0pt; padding-right:0pt; } +td.td01{ padding-left:0pt; padding-right:5pt; } +td.td10{ padding-left:5pt; padding-right:0pt; } +td.td11{ padding-left:5pt; padding-right:5pt; } +table[rules] {border-left:solid black 0.4pt; border-right:solid black 0.4pt; } +.hline hr, .cline hr{ height : 1px; margin:0px; } +.tabbing-right {text-align:right;} +span.TEX {letter-spacing: -0.125em; } +span.TEX span.E{ position:relative;top:0.5ex;left:-0.0417em;} +a span.TEX span.E {text-decoration: none; } +span.LATEX span.A{ position:relative; top:-0.5ex; left:-0.4em; font-size:85%;} +span.LATEX span.TEX{ position:relative; left: -0.4em; } +div.float, div.figure {margin-left: auto; margin-right: auto;} +div.float img {text-align:center;} +div.figure img {text-align:center;} +.marginpar {width:20%; float:right; text-align:left; margin-left:auto; margin-top:0.5em; font-size:85%; text-decoration:underline;} +.marginpar p{margin-top:0.4em; margin-bottom:0.4em;} +table.equation {width:100%;} +.equation td{text-align:center; } +td.equation { margin-top:1em; margin-bottom:1em; } +td.equation-label { width:5%; text-align:center; } +td.eqnarray4 { width:5%; white-space: normal; } +td.eqnarray2 { width:5%; } +table.eqnarray-star, table.eqnarray {width:100%;} +div.eqnarray{text-align:center;} +div.array {text-align:center;} +div.pmatrix {text-align:center;} +table.pmatrix {width:100%;} +span.pmatrix img{vertical-align:middle;} +div.pmatrix {text-align:center;} +table.pmatrix {width:100%;} +span.bar-css {text-decoration:overline;} +img.cdots{vertical-align:middle;} +.partToc a, .partToc, .likepartToc a, .likepartToc {line-height: 200%; font-weight:bold; font-size:110%;} +.index-item, .index-subitem, .index-subsubitem {display:block} +div.caption {text-indent:-2em; margin-left:3em; margin-right:1em; text-align:left;} +div.caption span.id{font-weight: bold; white-space: nowrap; } +h1.partHead{text-align: center} +p.bibitem { text-indent: -2em; margin-left: 2em; margin-top:0.6em; margin-bottom:0.6em; } +p.bibitem-p { text-indent: 0em; margin-left: 2em; margin-top:0.6em; margin-bottom:0.6em; } +.paragraphHead, .likeparagraphHead { margin-top:2em; font-weight: bold;} +.subparagraphHead, .likesubparagraphHead { font-weight: bold;} +.quote {margin-bottom:0.25em; margin-top:0.25em; margin-left:1em; margin-right:1em; text-align:justify;} +.verse{white-space:nowrap; margin-left:2em} +div.maketitle {text-align:center;} +h2.titleHead{text-align:center;} +div.maketitle{ margin-bottom: 2em; } +div.author, div.date {text-align:center;} +div.thanks{text-align:left; margin-left:10%; font-size:85%; font-style:italic; } +div.author{white-space: nowrap;} +.quotation {margin-bottom:0.25em; margin-top:0.25em; margin-left:1em; } +.abstract p {margin-left:5%; margin-right:5%;} +div.abstract {width:100%;} +.figure img.graphics {margin-left:10%;} +.caption span.id{font-weight: bold;} + .wrapfig-r, .wrapfig-ri, .wrapfig-ir, .wrapfig-ro, .wrapfig-or {float:right; text-align:left; margin-left:auto; margin-top:0.5em;} + .wrapfig-l, .wrapfig-li, .wrapfig-il, .wrapfig-lo, .wrapfig-ol {float:left; text-align:left; margin-right:auto; margin-top:0.5em;} +.wrapfig-r .caption td.content, .wrapfig-ri .caption td.content, .wrapfig-ir .caption td.content, .wrapfig-ro .caption td.content, .wrapfig-or .caption td.content, .wrapfig-l .caption td.content, .wrapfig-li .caption td.content, .wrapfig-il .caption td.content, .wrapfig-lo .caption td.content, .wrapfig-ol .caption td.content {white-space: normal; } +.wrapfig-r .caption, .wrapfig-ri .caption, .wrapfig-ir .caption, .wrapfig-ro .caption, .wrapfig-or .caption, .wrapfig-l .caption, .wrapfig-li .caption, .wrapfig-il .caption, .wrapfig-lo .caption, .wrapfig-ol .caption {width:30%; } +/* end css.sty */ + diff --git a/doc/html/tech_21-5.html b/doc/html/tech_21-5.html new file mode 100644 index 0000000..4b2c77d --- /dev/null +++ b/doc/html/tech_21-5.html @@ -0,0 +1,522 @@ + + + + +LILO +Generic boot loader for Linux +Version 21.5 +Technical overview + + + + + + + + +
+ + + +

LILO
+Generic boot loader for Linux
+Version 21.5

+Technical overview

+
Werner Almesberger +
John R. Coffman +
(reconstructed by Joachim Wiedorn)
+
+
July 17, 2000
+
+

Contents

+ +

This document describes internals of LILO and related parts of its environment (kernel, etc.). It is not +necessary to read or understand this document in order to install or use LILO. A general introduction and +installation instructions can be found in the user’s guide. +

This document has only been partially updated and does reflect the status of Linux (until +2.2.16) and of LILO (until 21.5) in the year 2000. +

+ +

+

1 Load sequence

+

The boot sector is loaded by the ROM-BIOS at address 0x07C00. It moves itself to address 0x96A00, sets +up the stack (growing downwards from 0x96A00 to 0x96800), loads the secondary boot loader at address +0x96C00 and transfers control to it. It displays an “L” after moving itself and an “I” before starting the +secondary boot loader. If a read error occurs when loading the secondary boot loader, a two-digit hex +code is displayed after the “L”. This results in an endless stream of error codes if the problem +is permanent. Displaying these error codes is disabled if the build-time option NO1STDIAG is +set. +

The secondary boot loader loads the descriptor table at 0x98800 and the sector containing the +default command line at 0x98C00. If the default command line is enabled, its magic number is +invalidated and the sector is written back to disk. This potentially dangerous operation can be +disabled by defining LCF_READONLY when passing second.S through cpp. Next, the secondary +boot loader checks for user input. If either the default is used or if the user has specified an +alternate image, the options sector is loaded at 0x98C00 and the parameter line is constructed at +0x99000. If the resulting line contains the option lock, the command line as entered by the +user (it is saved before the final line is constructed) is written to the disk as the new default +command line. Also, if a fallback command line is set, it is copied to the default command line +sector. +

If the user has supplied an initial RAM disk image, this file is loaded below the end of physical memory or +16 MB, whichever is lower. The start address is lowered to the next page boundary so that the memory area +occupied by the initial RAM disk can later be easily returned to the system’s free memory pool. The 16 MB +limit exists because the BIOS functions used to transfer data in memory are only specified for an 24 bit +address space. +

Next, the floppy boot sector of that image is loaded at +0x900001, +the setup part is loaded at 0x90200 and the kernel part is loaded at 0x10000, or, if the kernel has been +compiled for being loaded “high” (i.e. with make bzImage), it is loaded at 0x100000 instead. During the +load operations, the sectors of the map file are loaded at 0x98600. +

If the loaded image is a kernel image, control is transferred to its setup code. If a different operating system +is booted, things are a bit more difficult: the chain loader is loaded at 0x90200 and the boot sector of the +other OS is loaded at 0x90400. The chain loader moves the partition table (loaded at 0x903BE as part of +the chain loader) to 0x00600 and the boot sector to 0x07C00. After that, it passes control to the boot +sector. +

Chain loaders that allow booting from a second drive (either floppy or hard disk) also install a +small function to intercept BIOS calls and to swap the drive numbers at the top of available +memory. +

The secondary boot loader displays an “L” after being started and an “O” after loading the descriptor table +and the default command line. Before loading the descriptor table, it checks, whether it has been loaded at + +the correct location and displays a question mark if it hasn’t. If the descriptor table has an incorrect +checksum, a minus sign is displayed. +

+

+
+0x00000  |-------------------------------|1982 bytes
+         |-------------------------------|
+0x007BE  |--------Partition-table---------|64 bytes
+0x007FE  |-------------------------------|29 kB
+0x07C00  |--------Boot-load-area---------|512 bytes
+0x07E00  |-------------------------------|32.5 kB
+0x10000  |                               |448 kB
+         |                               |
+         |            Kernel             |
+         |                               |
+         |                               |
+         |-------------------------------|
+0x90000  |------Floppy-boot-sector-------|512 bytes
+0x90200  |---------Setup-(kernel)---------|39.5 kB (2 kB used)
+0x9A000  |------Primary--boot-loader-------|512 bytes
+0x9A200  |             Stack              |3.5 kB
+0x9B000  |-----Secondary-boot-loader------|8 kB (3.5 kB used)
+0x9D000  |--------Map--load-area---------|512 bytes
+         |-------------------------------|
+0x9D200  |--------Descriptor-table---------|1 kB
+0x9D600  |---Default command--line, etc.--|512 bytes
+0x9D800  |---Keyboard-translation-table----|512 bytes
+0x9DA00  |Parameter-line-construction-area-|1 kB
+0x9DC00  |                               |7.5 kB
+         |                               |
+         |--------Drive-swapper----------|1 kB
+         ---------------------------------
+0xA0000
+
+

The area 0x90020-0x90023 is overlaid by a command-line descriptor while the secondary boot loader is +running. +

If the build-time configuration option LARGE_EBDA is set, all the addresses in the area 0x90000-0x9FFFF are +changed to 0x80000-0x8FFFF, with the exception of the location of the driver swapper, which automatically +follows the end of the available memory. +

+ +

+

2 File references

+

This section describes the references among files involved in the boot procedures. +

+

+
+                          --------------|
+                          |  Default    |
+                         /|             |
+                      //  -command--line---
+                     /    |  Image      |
+                   /   // |             |
+                  /  /    |-descriptors-- |
+                 / /      |             |
+              // /        |             |
+-------------/-/          |   map       |
+|Boot sector  /\ |
+|            \\|\
+-------------\\\\  \ \ \   |-------------|
+              \ \\      \ \  Primary    |
+               \ \ \      | boot loader  |
+                \\\  \ \  ---------------
+                  \\    \ |             |
+                   \ \\   |             |
+                    \  \  |- --- --- -- |
+                     \   \| Secondary   |
+                      \\  | boot loader  |
+                        \ |- --- --- -- |
+                         \\|             |
+                          |             |
+                          ---------------
+                            boot.b
+
+

The boot sector contains the primary boot loader, the address of the default command line sector, the +address of both descriptor table sectors and the addresses of the sectors of the secondary boot loader. The +generic boot sector is copied from boot.b. +

The primary boot loader can store up to eight sector addresses of the secondary boot loader. +

+ +

+
+|-------------|
+|   Default   |
+|             |
+--command--line-|
+|             |
+|    Image    |
+- --- --- --- -
+|             |
+|  descriptors  |
+--------------|
+|             |
+|  Zero sector  |
+--------------|
+|  Keyboard   |
+|             |
+--trans. table-|
+|    First    |
+|             |
+----section----|
+|             |
+|   Second    |
+- --- --/ --- -
+|    //       |
+|   section    |
+--------------|
+|    Third    |
+|             |
+----section----|
+
+

The map file consists of so-called sections and of special data sectors. Each section spans an integral number +of disk sectors and contains addresses of sectors of other files. +

There are three exceptions: 1. If a “hole” is being covered or if the floppy boot sector of an unstripped +kernel has been omitted, the address of the zero sector is used. This sector is part of the map file. 2. When +booting a different operating system, the first sector is the merged chain loader that has been written to the +map file before that section. 3. Each map section describing an image is followed by a sector containing the +options line of that image. +

The last address slot of each map sector is either unused (if the map section ends in this sector) or contains +the address of the next map sector in the section. +

The ifive sectors at the beginning of the map file are special: the first sector contains the default command +line, the next two sectors contain the boot image descriptor table and the fourth sector is filled with zero +bytes. This sector is mapped whenever a file contains a “hole”. The fifth sector contains the keyboard +translation table. +

+ +

+
+|-----------|                       --------------|
+|Descriptor  |                       |             |
+------------                        |             |
+   |    | \    |-------------|     //-- -- --- -- -
+    ||   || \\  |             |    / |             |
+     |    |    |   Fallback    |   /  |             |
+     |    |    |             |  /  /|             |
+      |    |   -- --- -- --- - /  / --- -- --- -- -
+      |     |  |   Options    |////// |             |
+       ||    || |             // /   |             |
+        |    | |- --- -- ---///     --- -- --- --
+        |     |||            //      |             |
+        |      |            /|      |             |
+         |     -- -// /-/--- -
+         ||    |             |      |             |
+          |    |             |      |             |
+           |   -------------\-\     --- -- --- -- -
+           |                   \ \\ |             |
+            |    Map section         |             |
+            ||                      ---------------
+             |
+    optional   |                       Kernel image
+              |
+               |
+               ||----------------------------------|
+               |             |      |             |
+               |             |      |             |
+               -- --/ /-/--- -      --- -- --- -- -
+               |   /         |      |             |
+               |             |      |             |
+               -------------\-
+                             \      |             |
+                 Map section   \     |             |
+                                \   --- -- --- -- -
+                                 \\ |             |
+                                    |             |
+                                    |             |
+                                    ---------------
+                                   Initial RAM  disk
+
+

A kernel image consists simply of a sequence of sectors being loaded. The map section also contains a sector +with a fallback command line and a sector with parameter line options. Optionally, a RAM disk image, +specified by a second map section, can be loaded. +

+ +

+
+                             |--------------|         |-------------|
+                             |              |         |  Original   |
+                             |  chain.b     |         |  partition   |
+|-----------|                -----/---------|        /----table------
+|           |                    /                 /
+-Descriptor--                    /              / /
+       \                      //           / /
+         \\ |--------------|  /           /
+           |              | /         //
+           |   Fallback    |/        /
+           - --- -- --- --/     / /
+           |            //| / /
+           |   (Options)/  /
+           | --- -- --/// /-|
+           |              \
+           | Chain loader  |\ |
+           | --- -- --- --cccccccccccmmmmmmmmmmmcmcmcmcmcmcmcmccccrmrmrmrmrmrrrrrrrrrrrrrmmmmnnnnnmmmmmmmmmmmmmrmrmrmrm.....n.nnnnnnnnnnnnnnnn................
+           |            cccccccmmcmcmcmcccccc/mmmmmcmcmcmcmcmcmcmcrrrrrmmmmmmcmcmcmccccccrrrrrrrrrrrrmmmmmmrmrmrmrrrrrrmmmmmmcmcmcmcmccmmmmmmmmmmmmrmnnnnnnnnmmmmmmrmrmrmrrrrrrrmmnnnnnnnnnnnnn........n.nnnnnnnnmmmmmmmrmrm.....................n.nnnnnnnn........     |-------------|
+           |            /-|----------|Boot sector   |
+           ---------------|          |             |
+                                     ---------------
+             Map  section
+
+

When booting another operating system, the chain loader (chain.b) is merged with the patched partition +table2 +and written into the map file. The map section of this boot image starts after that sector and contains only +the address of a dummy floppy boot sector (the zero sector, but its contents are irrelevant), the loader +sector and the boot sector of the other operating system. Not that the map section also contains the +fallback sector and a (useless) sector for options. +

+

3 Configuration parameters

+

The boot sector of each kernel contains a set of configuration parameters that have to be available at boot +time before the kernel can access file systems. These parameters can be set when the kernel is +compiled and later be changed with programs like rdev. LILO can supersede the parameters (in +memory) at boot time by placing the corresponding items on the parameter line passed to the +kernel. + +

The parameters are stored at the following (decimal) offsets: +

+

+497
the size of the setup code in sectors (512 bytes). Older kernels may put a zero at this place. +
+498-499
is a flag specifying whether the root file system should be mounted read-only (if non-zero) + or read-write (if zero). +
+500-501
the size of the kernel, counted in paragraphs (16 bytes). +
+502-503
this parameter is currently unused. +
+504-505
the size of the RAM disk in kilobytes. No RAM disk is created if this parameter is set to + zero. +
+506-507
the text mode the VGA is set to. +
+ 0xFFFD
the user is asked to specify the VGA mode at boot time. +
+ 0xFFFE
uses 80x50 (“extended”) mode. +
+ 0xFFFF
uses 80x25 (“normal”) mode.
+

Any other value selects the corresponding mode as displayed in the interactive VGA mode selection + menu. This is the only option that is set by LILO by patching the boot sector instead of passing it on + the parameter line. +

+508
the minor number of the device that should be mounted as root. +
+509
the major number of the device that should be mounted as root.
+

+

+

4 Parameter line interface

+

The kernel supports processing of parameters that are provided by the boot loader. The parameter string is +a NUL-terminated ASCII string that contains space-separated words or variable=value pairs. A description +of how they are interpreted can be found in the section of the user’s guide labeled “The boot +prompt”. +

The following descriptor has to be set up to pass a parameter string to the kernel: + +

+

+0x90020
the magic number 0xA33F. +
+0x90022
the offset of the first byte of the parameter line relative to 0x90000.
+

The boot loader composes the parameter line from the command line, from the options sector and from +some internally generated prefixes (typically auto and BOOT_IMAGE=), as follows: +

+

+
+                  |---------------------------------------|
+                  |  Image    |                            |
+Command  line      |  name    |    Command  -line options    |
+                  ---------------------------\------------
+                       |                       \ \ \
+                       |                             \ \
+                       |                                 \ \
+                       |                                    \ \ \
+           |-----------|----------------------------------|-------\\-------------------|
+           | Pre- |  Image    |                            |                            |
+           |fixes  |  name    |       Static options         |    Command  -line options    |
+           --------------------------------|--------------------------------------------
+Parameter string                            |
+passed to the kernel                         |
+                                           |
+                                           |
+                             |----------------------------|
+Options sector                |       Static options         |
+                             |                            |
+                             ------------------------------
+
+

Example:
Command line: vmlinuz root=802
Options sector: root=801 ro +

yields BOOT_IMAGE=vmlinuz root=801 ro root=802 +

Because parameter line options can typically be overridden, the first root option is ignored by the +kernel. + +

+

+

5 External interface

+

LILO is able to receive its command line from a program that is booted before it. This externally provided +command line is only used if the user does not use the normal mechanism to invoke the boot +prompt. +

The following register contents are expected: +

+

+DL
contains the value 0xFE. +
+ES:SI
points to the string “LILO”. The string must be in upper case and no terminating character + is needed. The string must not cross segment boundaries, i.e. SI must be below 0xFFFD. +
+ES:BX
points to a NUL-terminated string that is used as the command line. This string has a + maximum length of 78 characters (not including the terminating NUL) and must not cross + segment boundaries.
+

There are two values of the externally provided command line that have a special meaning: +

+ +

LILO can also obtain the default command line from the map file. It is only used if no externally provided +command line is available. +

+

+

6 Default command line in map file

+

The first sector of the map file is reserved for a default command line. Unless the user invokes the boot +prompt by pressing a shift key or unless an externally provided command line is present, the command line +in the map file is interpreted as if it had been typed on the keyboard. +

The first two bytes of the first sector of the map file have to contain the magic number DC_MAGIC (0xF4F2) +in little-endian byte order. They are followed by a NUL-terminated string with a maximum length of 510 +bytes, including the NUL. Note that the boot loader limits command lines to 78 characters after removing +duplicate spaces. + +

The command line is disabled by either clobbering the magic number or by using an empty string (i.e. only +a NUL byte) as the command line. +

+
+

+

Last updated by John R. Coffman on July 17, 2000
+reconstructed by Joachim Wiedorn on January 29, 2011

+ + + + + diff --git a/doc/html/tech_21-50x.png b/doc/html/tech_21-50x.png new file mode 100644 index 0000000000000000000000000000000000000000..720d30d86ee934c10a2d473e72f7cd580efa85ca GIT binary patch literal 15263 zcmeIZRZyGZ*Ds2@wYU}c;!xb(-Q6h;!Ha7P#XY#YLvhzag1bX$C{Wyer~mIe-|UNh zb7s!PzBrl5B=aO|y-S|=S@wIssjJFiqLHA%z`$TC$V+R&z`%Au--9Ud&=nb1IU?u> zx4N>n%-h==^y~kt*F}gj29yBDQ&Uw7#`a8GdJ~5l%$3zu{mnZxD&2(x28I$wL0UrF z7xu&?wzG*DZ{g#~(cw$}ZO!_}(1n(k?UjeXFDW4nQ5xDrgfbTp?>DLSY?ao=p)=BE zI~Bm?AdnE~zGY`odwenY>UZ>!=WS!{4g;kjy%x`l#TEahV!eq~pnH>zZ0?6x-pyFd z+vH}v;~nPHw4?~7_%FKs$DzhkS2>GQMNA*3m_6CAN{=emi}oNcn<++254tNk)uglQy7);iTi$}_7sy97 z3E(_7&%a{m8jc}I8mm#Tx)ycmTgg_gV_ollY!lPanSIIVxwgaHgjec?9GPe>L>JKl zCv7r|;VLsk)h#Ag>ih`8@?bEFnlRyO294bvV;?2UUpop#V=1)$JeRX5ezJ%;EM`lk zPz}g$(vH5pW^+gMmtlUI@UnU{U|gE*`)|?-V-20B^;UlOq1=jPS}chiE**{ilMPNE zAzgf*jNiXq+J^W@j^*_{Mn?Wl6V?$x9Z=0Beiij@+uc4yC+pWSMDmWyPiDtX(O;SA zZ`8puQ4fQg=vw_(P6ZQ;+wC2Gl!R9ptPxueE0MM_(%c)E!38 z`pf9{>fc7a05G!G1j~cmroVSw%=1()PynjuJCc*lb2`$PO==rQXO(MiJ-f`-ZUag) z)_YI(Qj$08djr0PCz}VG-s)5ht!*d<;g;7%IalDx22e&g!0K3-4fSk|S2%wz&iX>) zxC=%)ARv9&vmhhs@gow?D6=aJ>BaxaPDB#+3xmU6FEJ+s>HoOR1hR_n!GvXhXm z_}%9kx1Zp~CgqBx=D$3H#@2Jm-uebm7WRK>N_>fhZ6Ll!a+&K-BfIu)&yIy0%Nz3= z`bjVg3?!jvK{vWMj)=Opb-iEOOn-zg8#`&%FS^QDesGZo_eWlJR~rLr(y1U-J9GNU z9i(28Ux0l@N4H}}ewEsAGl`7lPcn1-#C4@liaNP*4)bU$13Xzp#XSMwte~A**{1MN zui$OHT8xi+Ui}+umyrl?+UN`Lw^hW9T_keUX+nB z4i!^pa(-aVYQ_S}830Ib9L~AEX5-9s)XkyLXIaW`@eF$B2Mf?WbhwOMA<|=4_pApF z7)58X$dA$9b=2V$99o(_{s!e9*6eWI=>87yTHc7u7ra*;(z6`Qp#a6nE5c2{z4R;T z(jmhhD`0HkW19G*0;(qn-vbH^i8Q(KzGy`M42;ibitL!E7c5Xv%L_oWx@ z=J4IEtVfkmv)G6Isj>GV^O3EOudxWQ&moeH&Vb(SzuyUKL&%j$g8hD!e7x?ac?>mx zVAz~CY#I9H6lsnBEs?6xd~DTtkc6w2N};uG7s6*TNiu6tk-0)t&ja$KvTW)Efkd1q zu$l1rjT9LcKKO=(ZTluX@t6Ymk-?Q{EcSmz-2%Ft^5D{kkD~KaKEH2 zrnHG1{$Oh^o~T;E^~?K$srzO|vL}S3fufq&>2Ha#0yt!Xk6aMI6Gkgaw397S3mJ?qC?B8XMA&B3XG#{iP?1I^s<>UHAcd`O%t!| zDqECO0FO_53(!L6s}lYer=2K~ukJErw6x8d93!)fIZkPDQ)^0_S88};&mro=&=11j zpn-q3R#$ph)$Ek-fB=OSoQ`)3_*{T!CF?68u1GrE>YX{#xAgICQ>C7a#{)(U)*Q>@ zI6|E8+Ze`UuO1agLv<~jcop0PH9@;YA-21gdOXKM_KZ!W|5u=hLTVo-EoED zOzzW|;SaB33Z9B)DLuaPu^*!Hjh!m$>;*;oBjQ%6(NB@(CrQ|a5FZ}?=T>#u?~nK} zbvGX_TXrbwdUbEEi^*6pX&bqh;aF603@D5(;E<$x690CoMa7Knx$q3c2B5I^6%Sn0 zM+)|CRl}SEGW#lz)?Z-(m}PFmEF24%mN{y1L)vW=@021#9VB8fZe>O&8I}v*%aJ^z zdL~XiWLVef!OnE>uiyZ-?gz;hFyCi$Ew7#-vtGep0V-XQ*m89+1g|<>6S1ir%#sB( zU^0&p+s!%Z(T&NuqqTi4DqL-B<}DZeB7?|xQeg!w&PfZcoGUd?hQZN-_>YbF^f2b~ zVDZCCR325&eW|a%$T6u+(S;C00+JPfouhQ2(tSc~JRcONsGE;lIg&29_X^QMlJ2$D z^Gvm}VWqnh;USId$eFI?fK5sLHkL-uXcE9R4Dw=8-|>|T|GF&MG2I9UQ%8t{MDZzw z>4T#wQ3Ow<_)VuHQZJRFo*EGTKdiJPZa(^$*iCJU-5=~>M4g08MwRMjhA2p!5mpkP zWB&LwSt%!^6)1GvU<(Y!Fnqi5oMco@%G)w5_2LyVdC{b8xN%eUvQ0R0i}5o;K3Ka{F{@CFBZMxw6pKo3wgq#zc?RV&FRxJYtr9>&uV^-L>7 z7-M!yyxtadORUDz$k2?iqIICthsp$>qtpQ!GoFvaphge&aUXqSfI6Ss_Z;JV_gQh* zCF`HXKnWd;NBXHYYw&WU6GYM#u@J7`n7u&_@urr}l(2%{*Dz5Z>b~jgOk`KxMl)o< zL`aV1$(OgBj;I{>OZb>t{@o)awpZwm<_F%9{AP*I`=+x^`YG0l9thscv|J&pS@)Uc zKnABSt$O4M=wDRzng|1CoCrsFCjToFN4gq()Z+f$+_SmRJvDUUJ%#RQY99oOYwK?- zdo);UDg9{qu7c^WO%_qwAv%9NuS~`=ap}QuvLh9+~XPXJbT{*P--pZu6|Ihv-dYP zEo)zfkya8J>ha^?(*f22$xo8X3}ZYxvFQ?G@5y)k*00FIJnO`Nh!CSXg2PD0nCCxv^TH!u znpnpJ%Nx!iXNj{fWlsjHvXn}vPnsS`?%No9>nS)p@}s;Ds>-)#Ck1Al$FW(*htKM1 zgNeX_t>K^Vp?k;ry>oDqfMwNhIxXXoenAdKvUZK$LA9ZL>-g1&$CI&*HqCph)3J?P zBg*<_9(JBzc50^j!46UGKiabY6CJ1ix9GTV{;}5CLvFB>^@Mau4VAbA)yfM_CfD;& zeHc4(?Uf4XYGYlsNwrj6ThC0@mCSl#)R=%mJiI5JE8Yx;{6K;WP4)*cXO*2pUBQIr zBE$faOSwc$HG-K@sr05=ChJ7B_g<2X+m+RUP=2;%A)}U;m~b_vwKR3RNdX&IEwHYf zfMXQm5^B)21Xw)j@-zQlw4^}hE22G4n)8Z9t%J?fAhh5@FB{S$lksbdgb}5(PW&Y6Dlb%ITX4Q?gq0I$URRixlqJQ;;?}?dyCq6(od`6} zHFrR=I+f@N2|)S1)8_}CMgDv8du9oR#jhrn!NX6|z-*i{4%-WE0mB^YLTZ=7HokEC zZ(#foPyu}#Z3!y#akb*WA_l_;DTvSeI0~$PO!AATF2~WlBEYpboT>E&Zg7Epmzj5O z-3^dP+h@?^|8`qKywd-z2g{)p8&u%>6R4zEL$#A1q!;(JKq8L!+Np}Zl*F`TR_n`IymXalf!t+f8r zwlCE^u!cSBW>4a{m^tEtegLFq-NdT z%Rk4`+cN+E3($D;|GhnqU)Y_Q(#(4Dp_#v`jH$lZw=#N$Z*Lyi5jSR}0v)0Bg?=AT zJj)Pi*Vf(jl+CEa0$juhu748!%L1iTNk6lURDTKVG6Bi`Vu<_bBXlW#Y81GYwQL+rBT!MFred zvNWPZ9oi?@pH8s70Os6IUB<^iHA?8&m%cf>b6;7=rMJkvu_(racI5BDDyksMq$V}C z_K9IKzy<=OF$vZaMD_c^;ZeEPdcX6Qq`%&rVZAwC?xm44-YN_|7$?u{oq|0IKpMEp zKEIx37TfDj956*wyp$4IX(o&C<2% zc-hns{I%?<81ZYMTbJlm9?_=x6%gOb%2KV7nPQCG^#dfI>C&1l<6vrhRQ)Bu4}T;y zXM!SI#O!8t>6MudHmTE%P3S?Vu@wo!zuUG~!`Z(_9BOtMlt5%` zdV7mOINC?G#KsaWCu?8gph1CGkVIM;^8uKGSoc-HPky)B#QcXGHu_Ptn}C6XpR`Ma zET*0@`5Laq2>J4b_6egobJhx5^JW60%PE0{h?2k*8EZ&k_L3|?=3(zN!8boZHTihL zR$_8}ujb03R8MK5Bxti8-@#Bt(p)o^=A+9&YKKGg1`0gnYr)gIShX2q%51zPo1m9( z16jY&Pv}d-JGj4o;V^L=BO!L$(p*mxq%mcTG_7GX4phq6PMgw%?hM_&;w;Am(ZU&x z0I>T@&oY^alM%bLK*_s5z~&7Ufh~V+tUtPy8EM7<|IC{{&5)q;C3bfiwnat|n^wJsKi4tdwD6xBc zcN|JRf0IZH-RdD5DDpZM7pR@n7lU{K4l|0%5tYB0x9n6qVcE#;I;uo+RlUb>=WQ<7 zcugGmVnM==oo(>`LuID1rfe*RQ-vR^HeUvPb|imAOV!@XK&)X=D`nHa7A#WV!$t~r zY3kBTF$&wu2&7*1R!b=9=tPN8`U52H#Q%m-=XJ z$N#6%cQ*f%U2Fcwp+J5{8w$Xcbhwyy+Bq=K>K%_ZW)E+h4bvH9nx*zuOB$yrrJyF( zIllF?A6v{1qo2*HO0}!WXAwhE2E}Xjz7u+MPulSBd41SC&~-0e#34FX}Hm?#oKb@ zVQI#YG5})nRd`qF%Tg5Bf`~xhXyy{r)d?RE64c_WiLqE!o@a2_E~#4HldBjGb-w`Z ztgTzt<4GOQN%@u{F62nKXuF)XCnf?J+-er+N9xjk_U$>Pd!t3q@aN*+&fbKnoDqtZ z2t;GxLlE#5(9*SR1AR58_WT@@RU1g2J{Shcacj@F+&@miw=?uXJZVkw+=6=j6@)oN zvpOU_o*K`d|0U^q?g)_NBHUp$mfhmsVkLa5#}RCWDcC>5UCNQTjG$@EN@CB~eN!3= z$rkYlq$Ku;<)>Ebc+WL6UYMs}rS^3`gnasq3<8st?y7f_3Rl&#p?H8a4E=0x@w$$^ zOZgY{+Y2fx-P3P(gE`j(!v!p4jOD}(-0TaLM>V)3)rZFEu@rc+K-`&F{XF+##Rvho zQot58udj>rSDaq{oso(XH`;yQCo(fQ?@?X-^Amade%XPR3`3yXUe#z4iJh6(gG{md ztTt9|iaIwVfUD}QNaMnS9H27U)&_hkZXWUQDMUklEF7IpAkSAS`QE6aQl6{&Ov&*9 zKyr=jhotfZFhD?aKs*h4TENJOJ2-=u=3`e&g|jbwugfQa>|{w?los&}hcm3RtKhWM zgBZza_Hy279NhV@+K}hNGtBwx85~D20LbT$v|}gYROMD6!W$nXPvL9noat2Oc{Gd- z_lvWflW>x|otZ8~9I?l&9vFJngo5{g6GL^)E*;)ZD2dOJ=gO!2G#OEqRWEEALkc2q z-#&ky3pWgsCIMI_R5mMn)dU2hTIsa*tuC-{A87B2iz#x(2mJwzA>J8s5PqdV@({e% z&a(i$W30fBTEOtMm}Gf(Nk!Z23*hN|I(n0JIX?lHy=1Wnnyfsl?-!JQarNu17~Wi;4)bCMKxbGx0e+x{YSFqHZy8CU!#o70%%IsZxZXO6`A0>Eyr zFij`KxE0!?WRyWN{32RGy27>=B70~0x;Oe2D!k;gu-`385i*k%%=Tow%~wc&>3YvcFU=7;*g^XZQKcR@E)iSb zv3r{#r90RRH%}Cn88qQJ>Nky6uFU=foBM z8AHyYEQ{WY9>|H5RQpYQ?c{fGY6GhtABAb;*v#aCw=GglWlQT+LP7qML*z4TO|vq^ z4<}T0^aA2fI83O3CxK})uAQ*3Ep)EyNMns?I!fUo5|Ebf=LbF(NlfeSI3H_s0kBY`m_8_v zZl|c2tf+mj5Aos923hoM_wR>(iZtWU)mTfI zLR=9?M^UHz_R#Hrx67O;I`)uoi!zl|gC-9TUd$iXo(!(OVm)M?G1%gp%DlaAV*WR`zghS6q z>zNyi+_tXE&8z*gaRxDKy~P!YBp`*Is?b}0$S2E@W5g_<=Q~?Q}ngYBi=Pa1l0Q4_Q2uOc1JHNPQfkj$h2eMGcgc z+IW47`OJ+%=P5a`2q)>)U-0Q2;OlLXe)_mzi2SoT4n1;E`lX0JRPaAG%>tVS;z?CR z4fP@9VC(0-bP10xq(Tq!!4p+0mIG3SDwnt}4N5WMm7Tm$9qc_Yti?e-mB+2QOd~qS z>^~Q#3J7@CsIxr>a0`F#a`D|)7)?vb?f87-H1ZeL(XNP?(T3JvN)-!YzL~fRA18zi z7Jv6^mej+81Nk@#^uc~xz#b{)9{A_KN^sf<^kX$J$JDJiw9kw^wl2V4<5&2=$+rd9 ztR+Xrhw+)vcA0Y*20B>agC}2LBDLSQt1FL0O^de_0KX{ z+5wuanLmwhBw^$HNrJ&yvkFKoUd}eY!n8DbTko&)ETs*Vk4$q?eN13Y;{uuQZlb7Jh{(cwUw#y^zz4tZ9|NO-$@wa*3$++$B;UKaa2WPWelw4MzN>VN`YB3Gz-2ybNd_(| zb!l$+uZ{El=l`)!^Z#rnJwfdJfbVZpcGqe#A3h(g>W9NNC0Ul!C+#W`@FRoA7rdQb zniDP<0{$c%9=7k?^(!=x3WZ9$vW>!oe?!F$Dc`Q4hGF5y8B1lS}!e zG2N@?d{;7}F)exs2~By$#9UJuqJ7B2&$Y((A!iBJKMq1gIvB8V4*Oj;J#vn7H=PB4nYyIU=;%_sA+;*z)LeDR7y}9TqzL9^7dE3`QanX6Uabn6n zlz-UB<)FI_XgA53t!@xl zuo+~Fdw_tV!M*CCi?IfI(E{$a@k@Q;{v>O=&As`t%d|V}#qE=g2^WElumRu2E_21a zB0F{2uw?Co6ZRb9(LEzj|A@BKWQqJ;}%Rys4>{CZvD9ii?C`%!Jh9Jn3aa$hj zB~`>`JkmQWi*9<@xSQq)M2cVQmhhJfRKZp;m1lWp&o|i%7uYXZ0(fynThCK{L;gZB zYNi8`Yw>1Pn`SkDaG+wB=#5R}-2)6u-%eB26{0vjeWPwyM*E|Rk#6-fkxqYgQ$zJ?Kh2Wkh)CIT?u?C*rrYhq5Lwcro7CXA*(Ra@A zHyepA(G*&~R|i4m`jZMZnCF5(OD9ZQDOQkQzcOik`tjCRry(5BR6UvVe2I_xc1p?VP~xXIk6# z+dD$Rebc+<5d+b$3vgd={`rAIf6=FBM$UItG%J-5lH7_4QOj2|sOUHB2v#-T8peKx zDLqUm{D8%yyQ06Nwf>kT!hSV=XYnMvEp|CJc2BeYFz?tPVzdVz9PwKCMzZ}Nv;>hw z*Cx?cp17-5IUl@!I6}wI+>N*W-YhdWqaBNPt4YP($ky^n!usevI=+4=_pG!nXr-|C z={VEK-Z`uyEnUB2ry1nD7yi&;cS!AsD?QBGq&{Gm75n#1PY93|+ect9=pc;Gs#8BXp>Huk)b&%iwoN!ypU$!Eyk z3V82C@Cp3(*lRVS_p)wWAA*!k3S2f+2Xm}h|CY(~WyzNK^K(+FF>t-l+-3e4zrjBg zc~uJ^{T^;w0wa1|O6Jvf2Pk>P+hK+~dHh(W*6rV`(=AK?l4+wWWif1N&^Ak+ZBu!;-o88p7tSLxF{coz2O35Y5 zMD5`%8`biZ=Oz~*Vr1k5`+bDg%TBLFlI_l5uw`rb>f<8DY&O46PYBRr29El~zx?ON z&gxdV4^jhs&(AsDKaf*3{KD|aCn=P9j1e) zmYO%}Wo4c#mT&@{{?TFXZTMR zqXl}Q6Bzn8F7MoQbn!D7@NVq&nCp&}{e6GH(z{9Cuxklmg#Rfrd%n$4681-6-#|M= zM+YMSX5#Dud|uP-GY=gQ1(r9i&)!*xMm0V9BR-;HjJ6}qv@;;6QUr{|y+6mCNkp?O zC`+=p!(vAIDfB1XqNGG7c?SR+Y0(2m+*VSiAJ_vIX!i?tv~qpthLA2qfP~-J9suDm zW%^x|Cm9MwHxN{LH4x?D?&wT9r*ydHskU~6-7K>-w4G=S-!T1A5qd-CSR3SrWqmY& zz-?oE^HMsKEIo%NS6RQs&R$48j_sjTFHPZh^VUf_OkJwP;VYOSL|Vtz!K9O9_~ z??cP8DH$!fM%iKd#y4(U?;5pyoaJ4@wcKnf(ZA7ojPJRe!-TWI8rtE)fs8ho^O-b) zlJFA(Hsu7_H9GKwkr{6|>@)q~s*V8C2ID zeaM-l=U|Su>(z%sUHN4eN{BSL0lEtYjaknCRpJc-!Csp$oLRGS`d^lJih$ z>Ev8Dr+p`E8p0n!P%ykU&TQ9nNtECCJ}7r>v#}M|Vuo*MXqPnBjpum1w5{>xn7C#) zTp!t4pKUiBI@M;CBTc&&fV}qn*ahelmf9CIbkAUfwEQQ-hm39bq6auSnA#nhz2~+b z-B@BPz!%|Fwsi4(H=@WY97XRxDf?oR%|?YO0^`w*+gXmppn9UgA1oJ(UBx zY4V06*h1cz;zMUzn>v(KG%A3;b||TUF7-9RCnhdywmESOa*<-oF^BvKjU+BU(`IgS zeh*X#Tge3RZ|tlUiiC#_310XvK)k?#S+qZB!FDaLY$EZRIGc$U)-TX=IV3S82a>*x&`JGJ3QfXd5g!AWMNlW zp6G`p_?B>l%)tS}yBaf4;DD}^m+Yw6U;d@~bMVZDLWX1zN`b#Pias=z(^xS9lxeF& zb_@$M1X4K1tV1GP6br05RJD_r zUC>3K%Tq7$%2=?(=>k*?`xP=3c3m4bb>?wif0@ zBB+pv>YImj9*HL80|MsP#2BjFKZv_Y{r~pL1Wo0AMGuq{e{P3*B_&A0%{-R5AnC%g zlnd$J0)~Cb2nk9)9U4hH+_Dc0FOXQi+aY7l-3hO>Oi_)P>>}=`gaJ?|9MBYa)vc*K z+RiZG`Qc{#(7Az!fg;fmEO?@d6cOhLT3Vk>XJqiDU3ZkE)sffw;6_e@obS&e%0Xnl z$RobAOBLq0?dp%!!m|Oq8yn`aGcmQQCvfm6v(u+DKhk(Bl^18mcWQf>@2QE-^I=aA zG0`(sX_&9`PxyhswgaG;L#mraXL{Xhs(RhFOLy+s8YghX-ieDK)qzyHfd1PL*Qn?+ zBg(%>o*&K&` zMQpHf!UJg5rEc$+{A7?ygC7rwNc?fd=AJ$WnrFaXAWfsXJGCElMsPH}`6Q580^?zI zukmK|QmkIEc;N&4Cz^%1qNvX#)p;2|$;~4#mT6P?{+i2Em3bmNY+y%P_{J%}x*VD} zu>9lC3z4ogV!=Z6Ok+?qaM!I^Ko!Uo8UtIn>%oJ~FCa-j)J42ciM{smt74EhNQ5qH zj4|*_vXEjFz6PwRCKQSu6bY1&J?w~%hSCgp@GvQ_+ClukWdpz>%kUAH>>bfw815GJ zTnFZDHMZ>=_O>^VMZnNZ+>FtPg<*JP5-Zowm&kdzpb^P(WgI>9o7x)vAH&&4m(N81ofVPrd9mPVN*v)p~yQiPzoUoq}yIk+zr-HKQ&9a7;Zy+YOzlMkkjqQ8*XBS zeS8ID1nu;HxD2d&e?v43KLSOY>zx=k!`Osv_*t5SaWW(jjE@>$u6-8MxA<3ZEKNgJWcz9%H z)h7P+P|=Ft#nkVU2D|Mr;LY;$QDOWaaquUROaX;HlbXXI&QcTGX33`Z(C~#&fkU1j^|mP6!w*O!+xYSoFyt!OrvG39 z-QN+0;XnOMPza8Jl%p`>f)*t!lql!LGRptzRF zTWC@I55V61KN%jh3h{LPbmIedP6skX2>|ZDhK$W_uP?b(!^D5gp`%wgI9-q6^s1}@Y?xoS&N0`Z7Ct??-6BQ&CrX`Ef=XT%p)m#!C(6*r^+*}hf zKF}VHShi9_!y1dqO!xPXaIpB$sKzTN_0aC@nK<`8A1SG&A8=K$A8QmGs<|RRH#`AX z)42Ra#1t9PCehn6^vp(S0hOy_N=t}r+Un?fB)dINLNr3xF+}#G>#1;%n0ss~Vh|2C zVYHHx@8CRzMd5g*p#;M0(wRYI{7`~M?T8YIefl7Q?OWvG#v74kF^7~QFKl({d5~gs z-u!)!+o)WX$nf)CQ@uSKG*S+BCJGo1g)5v!AT~K5q{0^(A=WSrq%dwP}vX`<$=hQ>cYzs@P2$y`5pN4!XTBjf) zEsJI{rya8XdzrFm!&(llWDPoM=OSU<-8yjI#9 zX3P@!K{9Iu!SadUf`DO|#aIl@--!oEX}l}E3^#^>Ze2Ue#(fi^kUQ-lHroP4Y34N; zM_;hBS1IZ#vwRKMm-M^u$2W;1%V2sbknqI(YhZyTq#_fEe0zimD z*EPuxe_6cLId)_i2h5*lZf>}w6rNBSI3fP2QJr#I`g5MxxN%E-3d**jAy1=z+^QJejG zQrSK$&38$~lk!Rnu=AioziZCTM{;;a@dY0;=tZJy&Y{6D?u4Z_=q{X)*4+27r``j} zwm|&yW|73N6mnNSAwjb~*ifV=foQ6w_eb4RYVZ;a z5YaLxb=!N=*&tr{Y4CYe01EG?wnpKCBW!qx!^RAnZQ>IH6dswtM4F1~&A3hGr&(3t zs_n!2rNhpVO$W450hEZFz7Ou-VAX7|%tw+m%@Zqkf}$i@I$b*VPJ{(>Qdj3=Syc9A ztoq6Fk2)^`r%dWH^0hy;3t9vdn9$X$Odp%cs4=#L2cUq@Vd6&iNj>!q0?Ukc%0sCu z+N=*_nC{W8_KF1v->}Wld21O5*x3H~{jiA?NLnQO6S3D8mYl~4H7)U6p}|HI7=OiL zlLhc>+kduoR2~|1-b}~-xoiyzC`Mp$sZuQ=DTZDnxzG(Dr!%rfkMnZ6Gq@eK|Z(B20(LlNlSryZNMQq3l$8BHJm70$#5{Qolr z*aiZZ4gT}U5cB^XYmXVm|H_y)Q*ri{7pv38S?#aEy+?9a$*)U5oCMyF?{GQVzNOJ` z4dE5|RZ~9D_6qF$QhPk7ef)7=+ms==(&%DU`i;**0LV9~VTbg0*sIGZg!lT_ckBeQ z-2{t)QPi1kovOjpXZ7wj`eCCoj1OeyEcfl*GKLJjzVBo2QSw4>*f7z#VNMRue}{c|s#!$XNl^Ls{L- zMMj5EA4779reFkBxFwuA|G^}%{u!-778E!|F~p*aO^#bYJi*1ZmH8{Jj-58r(q5Z71rDw{p$Hgtq@-8)09`Dyexhi5pnKc6=O9M z8+n1~2q0b|!_WQ8MLWe#3aHc-C5RkVE>!4!OTM)fy|*6-8hmR!ZI%C<*w#=u9ZH;j z@)^jXH~D1TZ|rXUVX%}QN@;i#>GFBse~d7E=4pNF6yV9XFhc!T*w^qa6$5rDvjh9l zD%0|yMHm+N8TlH5Hm2_R6V(7WjE(OI`+>7@IM#1nS1?E-bxE0pAe@oi#>>_&o?uM^ zYP=r&=@`!%=vipnx}E}>Gt&GJq1M!w{1?>YaSn-J#USB`a*Iq~!&s7Oa7F~@5nNe_ zqY%Po;5Fgbd^2D_g`S$-@BWi}h>dKR0r4mpZZjSoL(R~i4R@B|vYkSGf1_|E*%{hP zJ*zWj1--qRpwqI*B~l3`;ZX)LKKl^7IV=&F2ZO)lO%DF(`zmG!MMI6hqQ7aN_xlLy z0t<+f*W+YqaK!LlX#l~C{^*`8ax03s!pAaJ=TKNvPsnyc@B-X~a>JZ-WA*2z)y!kv zbSRShZG6M5bqnqfCX=Kd(B4POu47i@S5J_TFV!mxkO*eb}V KO4mu6hy5?jTAA+v literal 0 HcmV?d00001 diff --git a/doc/html/tech_21-51x.png b/doc/html/tech_21-51x.png new file mode 100644 index 0000000000000000000000000000000000000000..efd7e5d740cbbcbfcc79629fe739e2fc13b38c86 GIT binary patch literal 6847 zcmd6MXE@t$*fzCy8){UoHb!ivTD4b2>{vyVs#4TmwO6&3DiOO@k=R15s##Rku00Z) zT1D;6llVW!`}zI$zB!KExyLon-+5hkawJM$SA&lF7BvwO5uGMj4N62r48*?+C`s@; z&M>BT%x1L^oKtub9)z5 zZ!6SC^>CK`V0xnG(YkkH7N3zE)_o40k?$5G1%dZ=R;J!S8@~HP8S{j|Bl~tGjYsb( zd6XSnZ4Fy5()24TOWjV9;+Cq8zY-?{PK~+r@&mlILN3cb^kyW?Tx}h&;_PGdpMS3dmj?8LKX1t4)vliW9ZfV-VXr_yC&`WHd zjG;wvNuSPX6P>RRMv(yU&QtkE8Y1ks(pMj%2Pk*g80P)_4^cn?wpX$!;N6>q5l9%B zfE@Ud6s34MbNk1XryC^CW$0p*Z`?<3UYS1nK!Yd-I>T-7HcDA(N;@5%rC`vhIMsUk zXH)D&-lq!$2T?^?z1E?=uCaLv+}B@doG$>XZspdl;gx|K)U5`Aead^OJL{P*Hj}tz zTBMb7`mV1PHch!EKlcuR72I76tRFJ94#0Z3b+`SPJ@R%kuBFm@1m|?~1pC12Q));% zscJX}Q|m_PlO?^&jbqI(qJfVbWU0BgJLJ^DJZu#7Wy4xRBcEU^F z0af$m6$;GjinGqLcjP)ZXY<-Bv>)K6-t;>(4`s|_-z-vCFccyi$452>gE>}NE{3*8 z?=K%fn!)DSx(F=Lz{RnaeV|$7q;B&-}%||#N0zDfihh61sU5y^{8g7R- zgA^y_H6s?;o#TjogWMrxoTy5^TN@lmy9D~0sd!+X7v2vkN*h1EHxM270h5AQ@Qk?8 zk`xXkpN(eA;mz^yu}8-e9b0QD7xj63-bp!$?W%-=kMWVc*m`BWzn};hGkpzR4mUX$S(dxzK66afs+3AfR4>0dM0VW`qnB`fI=Vk_E zGc)_M3}>d8fcqv%fixP8ZQgv~Sc^S*k>#_CzFRy?9IN^K?S`#hTu8rnAD#kGhbeor zFSy8>v-Ia_L;`_W$FW|$J-97iVDKM(GOH(hfS!;U`VF)K7fw-G>N7QbQ=WV~uX`D| zYm)RjtD6?;Qr8g`uHSfYzlpkG@W`_#O_KeU9j)%SRguOcy@+ogHbhJXlLUkjG}3JX zbDHTnfwU|rYQ^G+1e%)60UCs$KVuWxP3XLY4k|hxe1;BLWwd{!>wsJ8CdI}!pRM#q zNOI&4n~GM)QAwu_2+buSb#Gg+;1QOIR$zuc8izg3q6Tri@|LX9xFhYR9BK&p(V&2T z7<1EQl?!-wEb;I*pHW1s=n1m=r$6}F_vH>)Q-hi<644{BSRZVMWrNGv*?POVPtfL^YrAD)f=kDF>GYujCERMXkTr5xuoURH{JqAS$~l9;7QHyD7rlP@W->U zdpl0*l*3!CNQSss%@nY&4F}2eez$YiU-J3(Fu*A+fl~Ty98G6*k?}%w>==bk1Y#!gs=x%hj>RiM(yEJwzHP4@JaC0~2M7vH=`u zwWdgh?UtYSJmfoR7^wpK&QpYY%3U#e@L>kIzzu| ztf&&aapnVtW>V^NfKk4^4i_ryE{?U3*29aXT-nR0bTcSl8K9H|u6E1R2J2CUc z{qS}=)au)_yPU7?vIV{8$Ct41U3q;oZqvI-S~X8W_h7JD6S?unk|(r!aB}SH$6Umq zTd&BX6^Nly<3FcPz2igcmuC|iMnw_!uBL+@Y;Z>99=xI(U za2(FoD31~!?_z6|MRDVcPUY3~lsK+^D#ab5DiUFxs{#IVc#*AN8;K{U)bQZpCuGOp zIpHl1m*DcoU%y(b_xPsc&#WyJ?|$z8)V)E5C1;)E@oPC~EuH!OlZ;qbbEKE1hAKLA zjD@cAd`B_z#&zVj=8flCVyp|}-v4+|61_8){J2rENVe2J;I-V# zjMc}{Xr^LAmXM0%+@omaFop3yFQjfkgBp$ZCwWq>(^3asf^BGbb(9_%?-$R#wTN4Z z%&H*yS_P<3R@&H$zqN7VvB7ES>!NFU=-8GqQt{XS*$}D4l(29@b!oN(|I>5fSM~JL zC!!VQ`ZX8pk*KX#^QV&!R3FKeiA`Pdo~b*JweU3$i3%p{=Q^-4S6h;$olG|u{FWl0 z7}T1?gzLEb!pY zUNGsJn>AgkkF|kb1?xuU4;X*i06mDl^I4TDT(u~D>-@vd`_I3_I>oWiR6OIp^pR9@ z@Yx!>V02P8#IwKsda@igLC;tr_+TurA|r{b4!5OK5+Hd$z zrC2yoY}kRT{5_3T^8Z!%JmUmySEkF68$Yag?(X1fH{I$R=G6o}D@ZNswYncr{XH+g z)PzR5s}K{BTFOypv;5#hb|fUbrIRaDgwqvV=QOVk zp34}Sx81p3WNa{GQcT890q*M=1-w0teYk$S90JJy8a6CfbXVuPmG|;RSxTe%sD+M2 zDPKdLs$01y2V+;XdD%5ltRA$XiP^9Cc+oS;%p9^C zxMJaU`J4QJrQ!P@ei!vQhgwrc!+rqftb`l~~o!P)hX}E&{SejR)N>jUA zr9xm|rFn&dUx;a}X#(4X$PTKvrE=~|6UHw8^kVMMZ4{GHVQ*U;SCGv65NI;iv`FPl z9dCcykTQHXG>3`OnbOeuG(E-Wd*S;Jl+NUaKMvR=3Pa-)a#Yw`n5u&mv`zIg^qK}u!@a#>VFvG=H2^lO*jS1>G(B@rub%%cGuag6AK$gq0P3{UTNzmn2u2=p# z*g-@KO*GHOWGA$}i6pI0HaGQS;&t3)WFXZCC#}*rce%RFhfO}ZdPexe>c45$` zW2h0p?(Eq#MfMe2ivGYCTWzU2M4qbkYebZ{J<*SMYTW%|LPY+AGaqiI^SW#2#Lsn0 zir7@Wtfgj;^X~cWfnTQZ;uw`JP0!@0vA69K$|6`>Gzzz-ja`5h{!SKlg_u2Mq&SY- z($NBwLbTiWKa(s62$2sI_!gCoOwgKHJEb6PXc|4f*CNM!SZcIX%mNI%c7Ui)Peqt< zOem6G`=nD8%Hzd{m_y8B^^}-CGzFT(&r{8W{}LA1{K?VnuL)^kh{;+=>0dUydd_V> z!)wUbx=0DHfZs}pg;g&F1>Fvdv2^UZspSKY(D!nW^K)dFJ+s~zVP4K{PbY?l3b`b| z*%9+>WX^Q1IgMFvrEX4Wbj9xnL=6g;MOwui+p$x3dXdwXQP7rj98l5ns=1c$D_L_0 zOf&|a4NDc1Nm_U1nUk^CbVu3AJYNGQ z38`Ph^dyHSk)TN%TSCq@i8^b3{I`4?EtGf!9p16%QRclIRxD+eNjp+Q1CH}KZ^1yL zKFPR+`J_V*EG9dz_tBu+{;%b@O_3-q^*%{M4qX-k>Dk_L)o#S5(xU?FddQTOf9u@wmd*wqw}AXziXHntFI<+ z($b%*`26ErkIF5h0ahuca2_Iyuj7)1%@Gw}BAW}~M>etN3r9e7&( zQS12I9~{>s5}PSvsDn|K63%0S&p-@b%hcPhedC_gGHEBU2;(ASO0EnY`mmy4S=QtZ z5*uo$PZE+Ke$bUXpHzwP8j@2Qw49O$?%%bnnv2!y)oPbbn-avIzs0A<;o>iPLlRAC zYC7XD8u7lK13e^glPYW2m zO&@F+v`xLAaGb1>=9t;^{;2iM@6U9lWfVvQKv)V;!EQ7@$%F>(yH46_lKu9X+IB-1ya3~(eDahtOH-C zp!%tY@uu1jg3$?toT&|o=$w{PcNml&IF@)6x&R^^$Pf;)l8)?M30f@3DK;gIqtN0M z1>*nK%aEwh=XdA{_9GUn@rw_J*Uae?cDRo*36!-0yyKKofE}HVjQ~snbuH^v%tXz2 zBNT?jEZKw@Zz}Crf^NF;{C9+$5mdKgSkXG3(I*h^WbJ@m9kX}}z-MRFZ#VwW9Bqr$ zapk={)CZi@EFY@ibtimGN6MtHlETvU)NDaIYp`g7bQ zzndixEc=Teyd7gh;5oMxEb;tt7=G)ObQ@m#Tj+WgDM5l<{J`Y5;L^1|eL_MN15dDF zLN7MmipnZD^PX4qRsa5Ts7eh3vAZp5?X}Y417z||B{A(HPk-{am>jP$&mDK@d0%y!E2%SW(m9Z5H^^EHF_e#t}?t9plCk3 z+f?rmI9CZ>>tLK+B7-c+feuR4`sZO1gvXAlQT6Xh9RJCVckLM3;@ob|d*DFe7+m!^ zx&szPLkI;#L;jWRY(?bWJz@$%ym4QKaxqLH=2vJwbHfgpfH>Us7cflZ1fc|q2{0zgFM$yYs}1W#^v?bf|oA-^l5H(O_+IT^&k zzC;Aq?|{g@S|p>J|K|#UQfb0Z6~LEWi})0iPO66lJQA(#VVzBFgbGPinum2#Ux5z* zf64NEaXiPuNAPq9oGwInW!soE${Rg%p_N5}53-0BunZZQ*%PiIB>w{O#PnW2F<}~s zpAPn3QJn`kojC0IovGWiTkCb6ZrqOU{X@}ph~Vse5|>!jEiK|ee@AD$77)5#ld=}&V?DxR1Ivc>qly<6Z`_?MKSmf~Dnm<@dKVw@9K~69r~B z4Zy~}j{P@FrFq6;t~18XI6T^^f5NIEQlw4Uy8~EYF^SQN>i!bWFe7-rACek1x~6)F z+6RwJ-mq~zZEG(PyGPd)J3Xe=QrNgI}yP^!YRR6*Uos#n3p!^0_X|5v`Vc=#q zmKNe?5-z!&2=5Hhy0s4J(6~Klpb+D0bA00j$a7P;q`?JTB4og-E}}T-*m?6jcQghO zH}Z*>zluL~iIkzzhTgW z<{)|l7d?lXA|(wz;0B>y2S2-KOETy`^(CXJ<0~aLC@wK4sksB*B^C#-gEB$y z3%9HaI6JAo=-3;O{bG-Ph+6p+H!^Bs#7XzFkJS?m09#lXOkhrrHr@+KAf}(IFKyeF zq~9>L;cmnmF&UweR>jYwg0mkyG5AK*i@5KFRsq*>c?t;$GTaxNpoT?-p<10!g#?q! zS9i%VKa~8FZzi6?S)7kBOz(`my1t}_L7(f`?BH7rAsOu@4gLVk)eZ28Jbu6_kx=9* zb+LLrmV_J~<>>hG*RRsn9-%>UTxBQtxy9D|3IcecpJv6z)iJMBN<)nhf#ni6#UM3T z$3^eS<0m|>iY#yXMQ4Oi&>1U?6E_R_-c6G*@AT9I<$Kl30Zf6@O_En-S@wG1#=@0B zb%CRvyekmr*DZb2>aW<&My+sI7LwdSi1Nshh4c9Ny9E9`7}aaPFzE4QZ148FUzGR` za-UgQA?vET3j>!lmX9JluHggw_!!YIa21%K)#0|x#W>H>v-6WfJ&XDK{lH)D#~OjJ z9T4tGZ=By+Oo@{u+CKxN+omC2g8HZ8!=2dp&d3`YlnTpp;-LiZd^}V%gvJoLpPq1y z;F3!72`e5k!IEVZ6QQOx!L6+XgrCXtqlxf>Iw}BWLW`kZmjRIxpamey#qp#udeW~6 zA_&GK-b4~EmsWpW2r*vp(;J{LE#C6YQBNo}fn7l0vu6a$<(dCqhLEG-dG|uQ!c(k) zah&Qesn0dpu#E4z*8JuFyW|XO+x>(7Wf{Px#HUpbZuI z`W6th_T$#lT0c6#C*#SeQIHpNi=7V&a z;@re5}%$e^EY#m1s{)5s~*Hy!)Scm@)kjv5i literal 0 HcmV?d00001 diff --git a/doc/html/tech_21-52.html b/doc/html/tech_21-52.html new file mode 100644 index 0000000..2231347 --- /dev/null +++ b/doc/html/tech_21-52.html @@ -0,0 +1,22 @@ + + + + + + + + + + + + + +
+

1The floppy boot sector is only used as a source of setup information.

+ + diff --git a/doc/html/tech_21-52x.png b/doc/html/tech_21-52x.png new file mode 100644 index 0000000000000000000000000000000000000000..c8d23952d4fc1abf22b877850a47dc46ac07443e GIT binary patch literal 3084 zcmbtWc|6mNAE(7~O>~aszK-XR9^T+#oeO~Xs-!Ycv27KH?+-z)Yd`5=In}67ijg7tI1n7@) z$vuwzL)R@$t*;*)9sQC2=ZQGIUHnsV*6*gd6`RD9)RQsf9P5&%f{cw_HPI>%7{Ui!a*_j^26&=qZXBny8J8P*&i(oY*%6Qt(f5exj;yi%|9>p+28!QeF;i>78h3$;C$Y zpc-L&32R2VhSPDtx%c>*^dLYC~hkPXi5o=bZ*;|gkX9T zc=CtAY@dr29ws1M_0-?g?MU-J-{0}FL>T$yX-(8V`SRTHo*n& zwHq~YdH-08x+VM_7wF)6CmEbAY%9m%oueJ25Y&ru;+9JkLh_8BA`F`^njCAAYUcsY z$Q7xm${`$@62((cFMK1)wBK)5`(mW?srF8uJtfo?6pBk8Z8JQ&bqwui`StARF_|-` zByZqQQmWDY`<1>S|Ksyeff{29M<|b2CTV)MMc;@W{qeIFzOWU1HttcxgWdWk~*N!HQ-yRt2552gx`QgEB#Uz;Zr_c zkttq%;7IDMyVby9j_JUI%!|C>U!eA|*SL}po)+(6f-^zbkIdIr1d_=s(4K;zHTU1{R;h3rv~XvNc+=PJf>jlf>t$MvqNgxERnC0U>wFmtWF{K$;_ zD5FUj7^soaNUoNhlMW~c;E^+nG&@o&k&IXe3t!#(;myZmm&JUK(^KKgs%H&if z%9sfm`-{0n{wzqqyJ2AWAG>rx7XzNaB~GjM=L=|*kz#=IV!2lFL78e22cVyJ=}Fav zcB_jKK+9d6a~E`G-3M9JWcXVDyHw2UIa7-|!gN(nj=NWY4-i4HmHVum7GEwdR#v+IanMqyuXoMzr+=<2&H(9+}Hsw8io zRg*v*iJ^;SXWHUQ|)1$`rlRh80#m7aXy;hNs7>*o$e5TC*oA4GA>@moHnL?|xDZ;?&Q_uz>=4ToS>TU{I>F!ExEEo%a=e)E(M$jLss?Iq!H@3u{H*#vp|Cu+qfMj0A8A@L&!<7QYbc3=YbwlY;P~RPyFlhn`lvI2Et%Z4=4`X!YWBFtC*0>@X2R zBG35i#JG8L_eLn3e?l~N_VID|Ed%fDXw~?w>_?c=TTjP>)LrMa4q)Nb5j=yE`@{Ey z`Nv)z*fQ(kf-`3t<%_Y3JvseuQ$|Xm zqmarGe!}8vNBU1gFYO+1Lsl=-5q)DEWlVC6os)!8ySq>lYu#zgw%51; zD(GL^=K~Yti%@O8W*bjzaGkvO<&KSa5%28qJ^5c_;Y(NcmD)Zu-27qi6&h-GY9_lr z`lGb6Pl2fNj*anZo!V0_T^QZr;2rSbyF8jEthS!9&kh-wUeBoY^4^6S zY_q1so+Ph;o9XWw(m(hDz?pAh{A2djJtAnuaMJJE0zk66rgU)SF>&P?7vwIjy(z8n z>qnN(Fnl{8c1+!D{j#`YPfFwR5koPOykbnD54)`%w$KPI^5$HgzsK#`(l!gJP|ib} zNreBYN;w>Pb9;x)@U>K$ z>fW6kGx!`ooMkB474P;r$-hKFNKK|Dm`{^KHa{WoNo-iF`2GTr2_ z+t@DE(-t<2f5kiCO?}#A@)4MOQ8r#Q@Y&zj>=HxleVl@x8Q3l^6&e33tG?jTe3GYdXDa zuAL(z8H3vrp>KO;B#%&h^x%wf>ih6BZ{xJ*&9Hi$RiaP#L)Pb$q>ou29a9Pg$Br*{ RGXFd1jjo#`%XJ;Y{sZ!D=$rrm literal 0 HcmV?d00001 diff --git a/doc/html/tech_21-53.html b/doc/html/tech_21-53.html new file mode 100644 index 0000000..c728b63 --- /dev/null +++ b/doc/html/tech_21-53.html @@ -0,0 +1,22 @@ + + + + + + + + + + + + + +
+

2If the partition table is omitted, that area is filled with zero bytes.

+ + diff --git a/doc/html/tech_21-53x.png b/doc/html/tech_21-53x.png new file mode 100644 index 0000000000000000000000000000000000000000..be1d7eaba1eed65827cb9adf34dd28184f1a66b3 GIT binary patch literal 10755 zcmeHtXFS`{|F2clYD=p|ZBer}wOcz;yMmall^~SXDk*B$DuUW-?-_|vw6t19Nvulj zS=6pkiW~j^{`cQ!_rZN~AKX01_mj`}ob%Zy=lyw|7$XB6dKxww5)u-6psuC~2?;5j zgoF%1O-|(W&J8mY9|cAa9%`MRpA*Udmp?zmCgq6w$v!hNFeSMfo@n4h;f7U0qesLrLmuilY&~h>-XGeRuiZA7~dgCNVrLWn)e_2 zlWyeDV=B?9k-uHpnBGLjrFa>79?uy_4?D_k^uIYjA9tp`%02XXTG#!(j_tZ_*msBubOdCyeph^9-Hjc#rFk#?Qj#wt zY@N{o)9{18?d_<{Etp&WPw;ivRwQ`%Nl|rZgOzbnJ3B1{UB2?vT;!UBGEO1D@^0WV`-cb576k0<(ordi zG@~mzMe*}Rl+{o*?v|{EUR*&{g($G1N+@O3vEFJ3hZ-)%t-0(N(qJVy$SHu%jBmr9h|k>510C~K{lW4g6FcPOZKFo zouh9HLX0l?9+XuG)T-rL3L})6dazh#b~qOMje9?ZDw`(0ay#Chd|K;9M@J1bSccbp zj#N8I1&&(R4fMiix9Q;(nlxzjm!%6Rz|mM6p4~+v+ zz9uW!)`}p$q4MFcN5^cir{BOas1LHP59ha+Xe*S)xH~!+VOD`EYG34EwydGy9Ua>E z+rEs?c8RZB^?L4gbo5L*e}hlSmysb^O;?{$-F<2$@4rJCy^ozDBwmYXRZ6pST!7*Y zp8x(CcFF!Zd{SrF_PzBAwBDbvg=#Klm(lQX6*y#m5Xcn@l+yR?J4>DPZZfCv12Ts3IIDTOKV<0X;Mo4lao;kUqK11FFWQNs3v0yo{Xv9 zW8k9*V!BwmdNH|~@C%DxztW&FYlC`JblSA%c<$_VsEYcd*-m13tZw=KOt7Q#>r2I_b%yy2 zg8Em3#U{nfU9F&eafIx%^sXtX7W6)o(cxql6p${JBJM1oV=djErq!F>Qixg#x4zxh z*&xB9!{*#w5H8_CxZFasDIVM?K}{au{;6c~h0E8+fON?e(I!cj`0dTw8V9bwl*nbP$D)6K9C~>W|Gs|z(k6-Boa{~{%F`h7nyrO>iZ_cVR20lLT$=gD&xTWEO|(I+h%^@;YRv= zE2YqQ@iX6I<=!%9@>P=)(OQL@K&=_kdDY&s z5`%+sMB1eGJ9_Hi)0&f?2)1kPz{%3WsnP=&RA~=fHxjI@up;&(&$&d_$6a@0c*u7} z>=%a@=v9`*@QQnjO3?xAI6}&!U+8x&^O&(BD?9_gvU=0GC%!KExDdX#7gr(A^p_PW z*8@sk>pXvwYwUyiJfdpYDRCz$4k%?4B4ZWYk=F+-vCS*76I{@?h{+F5_S=Zkyy|&I zpEx|EJ_2`PzAF#5S`=C34B}CRLQpO4)Mx zhI9VS38S^2HzWCXrC`Itt!9pHzuRr=f6X@knSE>#U0m%BvT@rRQDuUUR8j1a)h+w- zLT|#lG_8Oe(pc>Qkc2pi{03zZ1$g4R`724xqx;H9Q5s&DGSS6@4cPgeP7zG%i0Tda zgX#IIk3IR&J?rL!I_Rn{`zFiRVRR4b*L}7XV}c{ zi=EX3-z|QP`X`JQ_RMLi5swMoB`DB_>5|-Xo>P%CR5SHbY|?f^Xy4 z9RSo~aIVz|x#EeeV2y4xv=v=Vsoi^4!2!|f2T4HC9rKA3NN_pg&g~CD91_4=cGTC4 z-08OYC6kzom%ZyFK40JsT)Sl4;_EK%}8 zh}_2+&b6T^Bq*lkzn%ajikWw_CaC_I98xgtM3%hn`QPvE6DRgw36{|Gynz|%7MhDA zI05d8>A7H|=s=kxk+CNV;2Uq^>2(M`VGi~Z!E{Zgl6C5YAfv(};KuX?`;}M0<8}jA zmItz79=@Qm?-6DQq`QD_ryPPzYgmg^ zn_BgwPChF_I4_^Zf!R)+w?YR%LlED~AF-*)0!^Q4*$)%VP|8>TuvR({#HJ96L>G;?Vt|G**|fU6lqS;>>=XZy5yUSfkmhJzY*) ziPxW$l*N%?o6M6h3NVLwf;)hgQpqSyzXG%_f1bJJSmX~bT+vbYWJ12H4$ogwcwp9> zgfA_MKT*uz5Dzn>%)M7VdZW0>ZBRUED1i|UA3x;2zgp4K4uUT+27vKtC(KLP?Bb>2 z(v>p0GZ`Y)CRXj5xvA)+`InJ9QVK40Wla8lHNm zDvnqzLe=}F^lUK?vWWf&pUx2yGYwqj3qIS)HU~O`n$%Tqx8mQ zxv^&bQm4mPSvD(LfUpdFMdFCzPJExx^HHN&vR91wX8O{If+hKWo#YIPv3 zmUbYpKsW_S$577@~3dBrJ?+A`3jTggO+alT z`W~Ap{`PN9H%@=sw_*!R!pG_@n%nh3&@X!5NDOKMex8Kj+x%j|ihsKN4nP$v)j~Y< zSu2I2Yf9X;pn4jI{eJd(;RnXx)b%1iQ0$1UHE-vsF9mdUoQ26btSme?^+!z#bM^D1 zwwhayKXxgOGC9-nVjhv^s(FP%e7KfDpL*xUo~g>;vk|4 z_*JDTzl4VNPIi2NXiu%Z>c+!f`U*&~rX4VfaH(V#o%!Fnn-In-ACBW~GULj4z|Jdn z%4S8^c;C#sJ@T_H%=VI8b>NnHUd;3O&$Jylk|Uwzme>WgjyMn`FNJ!L;g%5u^yc#<&0TagZ}U6Db=P zh_H1>g&Isy*OK7tI*LO~m5FEKX`b{wfyzhMdID|QIkj@lD@35b?gRDVO+CEW>Qfx5 zqdmGJTz+#u;J&MmK?6dwz`0F#EJ0z@}E8+N?*|C&W7`ez>Nj z4yE_*S5cIjg*qHDRGHaW?Oz*3wVA)HRw+xaUK${I3~y(6q` zxD5>hLx=jGH$kW3LaWmb>z`>`1t5f!Qs~S((eGM!(tDQ*e5?z@J5sQxIy-|N!rmk5!AAx7q_ey@>Kt$kkiiJf%?KOM zWa0~oz3>0@*?Rp81d_{o5XeWaX(+>EMST@20&dXK8+HmbK4bva$_zRe!Zh4OPuHHe zYXR%2PQItg?_;0}nRXnTGk?~R%c=!MzZ)2JI-d`Sfvzv)4ua57vEJr`6Z!M-WU^-T z>8zkmCwjP~zj+1RB~dY#6|4?BD^`p6vlcG-%WY_~DE#bY<}s!s3k7zsx`c40y$vQA zx-mYNZ7o=(bz0+=&&eJrL2T7li>ykbKhm=J6ENQrs zcm4+89$T!y9;p_kK#X==Y7(l~|Yf;=UmqJF3f{y}%~%~lPTq{4{k8-8`^C3f3Pue zLWt=@z0GJpk==h*h(p$ynwC`W^nbtkfu_R)JkC`L(?HhP;ni)p+xtKES{q1i?)1AW zH!jGX_vWCD9(_@SQb)p9H^JS!RJa>}tFwCkLJaUfH7DhF_t|^t(j5Cr8o7 z4z3!CdVp}4-OB^$6>5RxFvpNG^((BVR+Hm&AeP|{3ivB8J&}o2v~n@WoNf6X7rTsx z>`t4L;vXJhUKR{0c>n@R+*ex2JN5NE^#Oh9=d`P>-NsxT= znjh%Rs_wXqPN$&5&_@&RKwXan$v5Vz)r`9Ib!ybJ zq=Z;ipU>o>QLaaA?CNqqXKKxkjcEl_lILhcPZB{8pUTr*G%Wh$u&*di{5GrKA?Q2e z;erme*fi?V`?f>cE2Atx|8jxe@n9F0(M8UUKjQb}_+C>TK|RfRS^aizQ{r(t$-k9q z7|WLel*si8@fw6wXwNA@ysh)G4j0e^WsEIoVo8eN1o1C0gXiByuna8n1?Za=Xz{f^ zrrR;%#a?ioex5(G|8?yRY#0f}rtl*AG-8}5gHO~Q@7?PA!N>a3LbW$81D2Rg2YqKt%n$$5M~-Be*DbR0%|yp z^Mbt9X1iByl!oP}XEeP9CF!(N^Cu0Mxo)AN{LY{#7*?1JpPSAI1Czzt47Z|rAhsef z5b6j06kDag5Y`#c=?{xnLBqc&$m_>2!-xGi_Dl;{C^*9{FYu8aUw1^5G+jT!l}zd%yIMxp-_;~~TD(ZNtpkJv#?&&u zuqRHH>A1PBYX|sR^wHdHD$w-ug+;iJ$Uu>6aRe(`>HIs9hL@*`B|<3{mL1-gUZ>=3 zz46j(Pjc2&{V5HTt^`qj5a<#2ywwMGc`kBQfO4rsQj#xALNj=~heKxJ70x>|On6R0 zLTfHwi6yMy-4tkNJ+DMZ0+90FYbouPsnU&b(#2=a05O>`!SWonKF;IykTW`K1+k0d#hjIEIhLo>ILPiG-!^>N&TK~-%z#4pN+S* z^!pWFr2g!(k_eB>Eq|)9@=>qXsUvGE(;95@F&}0*EK0$oNyw3kl^G%G6PWqc=TZrR6J7!Fo=)YnOXkiJ{-%)Rg&}LgQpBPQV z5v7T`K8Os)6RCGmD~s_wZ;=uy$wrW#4{=mbVrCjUc54d);=H18-d9peG-G`$v-s47 z9>pmk(*k66sfjTalSL~>nRK!E35p%wB_=Zz)2hJxhOw(T43-fkeQVCt+t(>CL^qJD z<`{gfXCU1x2=tt#EuA+mE0Hu0w`omJ=0Vi?9#K4dWTG%b>EfB9{avx~A)<6>I(ozZ z9>B$$YNUbwasrlEwG6QJxe(AdLT?CUOcFtZ|7Hm+;&>hM6wGKOvW(s%&u+x|X1Atr z`m*{JaqNCSwof6`x@z$f{ z_aN{BLscrXh3Qeu*;jqwC>dC#BR-LNFObKpa^RpN0roQBPp$T`aFhiB2 z?B;t&&(00ji;_ZW-J-5`l-?YIEYCGH{*F-qaX$K)j->k)#E6f1XZtwP#|AIAu*`8I zSKhNzVug#{LE2-}_));qL)t#ZYcBPSXU22>dxx|iuHAh6TXFVUVb}K99numJI@8F7 z=s2m{elwP7=Pn4JJyl*>XO3TZ)U?6#rgu%dp11Zshzz3#Kq}ed3hsChG;byUS;`%35Ju2I_gH(JQqyu*h zJAbcXKyBkCh{p?@g2C0>9da9{?3k`LyRt((%Fts{dK%*qFyJ=q8^mF>)6eJEaaIBs z`SHF9X2*vi-J_pQtP(doLHVV`nwwZIpC7b&*5(pc@{s*?H_b~C5y0NK!%qlyr%9i& z16mI?)vt56nVczpWj#(hH*a=orAn$Kc18T22gb}XPas&D_JnTai~KD2lDkb_V?dk* z+k1KWzDX(+pEwJfBJEU!BfU!X&sbpQX5?I4=7UzI)5nWqUn^b~l(;v@lsA-!X8z~M z|5dn_N70iF8@{rzhBEHSkrVp!1C;u#Wr{hbxt=L+96Xp{ODWIkWTG)Ik0DcDN%Ok~ z%)K4qFRMJPnOz;#thN(KjAJifIx4myG>4zbmUMB>I9QpdyphTgG2Kp0(tMW&CA}j? zLmf4+h>fygKRJZ@jMRLKpIpBvQSxku zXYS)PTlWG}ylRalknhMh)>#gfhB^|wIxk4Sq5=Ey!jD!%9dTZrmp1xX4*#314C2^c zo0(>kQbwqo0UfzghIs6}z zxN<<--W^o!qe)Q_n|wTLHbLe2dWnPg)7oQB$?yWypy+1b7e`PSMBSc z7FXi~b(+^p3R9~xeuBL-YRNaXLz?Ddm*lGaE(L4kDckPlb=Z(p=Iz=anbk0xj7(Kd z=`)K}abm?DIdPU-uoee~+bw++eWmE#1dPew2$`xbe#xdBI5a8%xYx!4u3TeoV(c?- z?~$!K_Nj67h&8J@*3dG0bbtaQgC&(#0= zt&O*2dRy6VF?`sgy#=-4S}(M!cBWn~Mo2E)fmjq%j@=9cz+1Jdk3ZE=fGt*B1e05) z9&s@M3@y@2?6@jP@P-zIlG;JNlgB+%HUO?Jy<@HFhj_%=8))BtJ@-JK!)Z0DS|re5 zxIk;~ru60ugI&_~#{F1`5Gsn73ErX#&Xs@fN^Lv)ep3;AaI3A(eaob0Y7i6aLMz_u zVJu=%P?9-TxAw~3tMbJtTm9Em>*VY*|d~sX+NGExOtK z9~H^3fg-#w4ZdhMT=<&Xjry!hR1JP9Mp4j1`_XaKD~_;5nq2R8!!n`hgGPZCyj>?I>4ZF6X*T(si32ulGp4a{Jg!IIW!adI4MU~uJ*t}( z*I%eE<8j4*u>#xN`z1(NQ)K6@PBr_v@EcISh^heQrt0G*eOxgG zb-%bW8-_~_Ld-}R+ZR}D^XU=RRcE1OXE!dPXXEnghblOMxm~*d&}{OT(>7PkHX~ z)nDchJvMi=r=z_;n{_q*qugtXGl4Yi=qmzb*yfCTep1+G1=wxkm)E%}n>^oU=h^AE zvV-2@1~dZUO_ALljP9QI%r3|Si@<}=P!4MLv%!B(NDK0ecdI%@kM4AemoGn56HXA~ zj-Rn?yjQF$9y#$D=)sRKlXGqBJvFS}hH#9w!@2Zd#e@0fHnxQ}vI$>* z)EB-oD6l6qhZRrB8^%t5FRo$B!?8Y9!X5N-Sf;0GprGaTOBsej%W}6#4a6V}*aFNV zs;ay6I_xRq>`1}VRWZo&YMP5`v2IohNhz~f6clUa4H=s=eT7oE{KOUO9nCDZ_pDDk z&!lJo7-AYrT=9pPg4p`DkQP3h;%*aEK{GZjp!GroZkhjmxmF(!LBFh{ zS_euOwFs*tYt0wvtrCP%Q7s-o85>k5WL~UNp-EUUCBsi?{4&H83yFekxY2a<>f`w( z^2Z+Q!i2t|(_LEroQV%gbq3W3aYdThAIgYJKsupt@j@(w{hh|Bx`@vx6kEXvPc-aZ zC3LHYcK%slUkSp?YF{MO9XP>D6>xLom`^_(@uy)x8F?Q^gka$CXr&+!13rLow$=gE zOh_Q=BGW*Nmrw z_+#)*>cNY<0RM#4!9)D=&=IyE9fCxt7QZ3 zcL4|Xo3{Z$pp|yeF0p9-Cv)Qu<9+!5$&w#FJ@a};$ZvY=hU=iDAeS`5)pvg`;0Q67 zb8ip_W1A8$xQC+vrsKYz)HU!vt}1U z7*+btYUnbZ<@#+>ofTcCC(}O!^@bu+zxDgC5x&uJx`R@NVlciXHV?+y8*wqLhBkz( z4~|oTBKi)BTVtDa+UwIctM6Wa&fOTi2RS?gE#w=t)vJ-ircOk1n0LQRQc{NbNDIan zDy~yfg-y3AAiseu4`L(kyG)6Kye)1coF5HY%E#h>LVX_lu~zke!~qL?-zac-e$3GW zgO?v*kbAi1cBassH1E;_hejIG0KM|-JvlklU#!07WF`(&P!#x7D*H~yj+mvr!08`V2O@(z?9un@!GVsH_cNDiS z4!lg!YXNRwt@7S!S(+J*AobG(%*K#fdqGGo1l6LM<&v!Civ9wM2I<4D^jnS!ClJA9 zQ=WVWL*Q*8?Ge5CrH#kgEEx%;kC~aI+0M3_*5VJyy*@v>{eZ~}&3V;1`0ij-`*GGS z{j9|#J-pV$dxPZ5wIsXSWoo&vM<&P{RJUv?NUU#N!e_kE(YWg_koem!B>H(})Nt$X z8k-=H2+h5=7o)Ir!fNG@?*q`A_FRMf>o3xr3T%d9x9_Z9bQ+2ZbKY_5MWj%lv@gZa z^V`o{xyxl#d(9yEJ(lq-EW9RSoNncF4q^LM{kih>3*-#gINotjZUAK}^<##0Ol1#g zOj=wcD;;yqd4=YVzdthv9(DT5JV|}0F}9))CjWKO&Gtp+R86&Bq`Vl+?NI49mUBlK zW%aj_alIx7O86T_#z@~w(;+c@pFfIIB`5uU_+&sY2%q3%PH}55*(^wOo7X-s-CveN zq?Y>o3ZQb^VpiupbSg;tk}5#$A&+ZT)kP|pP}}ChS^kpAx67}N(vJ-gi&%)_&Wzlz zzhrOv!`H`1Bx3%0Sq|3=4)!(kR>rpBG54p!bd9oWFG}L=&H*}o7aam`_tJo~ zoIhkd7ychMO5+fEA@9CJ)G9eld2p|j@~^hfIKMg=zW8xo6MB*DcYB!NzvLAzWEoHd ztbzPex`~c}vCYSzX9Y?XHpC@!qfPT`{%ospCHZoveREz*M2iu3p&-z=BrZmy7bw8r zE{Q#_X7I7yg{9Go1$Vrew&kt(vMB{o zo(Vk|xi^;gI^g}v6c|cNmw1UI!dHs_>E7ClCp>Ul-ibDY z)`=yw{XyCD2KgicndFC!dXTAW76Ah_E#=NJYk+A7>R^YzI_4q zou*jY!7lmg{34~kG?C`VCj2v5C!CR)Na$;5A{9Wx!#x}8u&FY z?p5>2BxQv(zUf|e$EyUCx>6v`+NuMtE##JQYDPGGYW?Qtj4OB2+8e9bp8Ei7*)Yc$AKDJqO%$dK$= zvWKzn#uky@(f56?-ygrZuID;u&T~KKUe4!p?)y9s=9Y;rC%XVU9UUE~z8>6+j*gy6 zyKGpQXcoU((^i^burt(!)BTM}>?G0tvH9p(`P0#H@SI%qbXht4G$TuZzOgpT1T)KN zPTp6s9IcD8yx`b_L|fmA)E*{Ko3)Qe^UkDz)=wK}m(LcMRo?UmqAF>P>+OP$IE ztS!Te5P>l2H8$Z@z4lI8y+^3k*4ARJqU>h~Y4Y#+!qYFL&kZJ6S{1efCfhcujx*Lv zg_EQU$l9qj=!?EU1O=RSLG-o$Q;D^6r1O0?sFe$1e=?m@+aJb00%?!#Kd0OE(+v+btGS?><+C2mcjkMs@l!Fe z`b&^Rm%i6pPfZ$j!$`~%;}hZnbJ`y!sWs6bzxw3Dst8HBzsDP_1?fB5pybb>|DD z|NL@wzOnSFwkU90ohPthOFFwGPA`GGLjJrC+;ZJF`O&wUiQvNgVV66e_lEAQ!UzNX zZX?@hC{$3~sSW$^2d=CIoARb*49j*wVmU(ZP1?hbg0%F3Ti-gV)Czsa-0zA3F>PZglrg zP}%K!o2IaBy3l{q$os=3=+M@sP@mUz`s;p13`D|ICgETzw(8m+D-3Z4@=_FU8pCX? zJkk*uW)>4yDkd;c(qEWv$|74o=P`;#%ZpXLjyuD%Ycwu-ddcq&CP*_yO#HV-HqY~& zbJq%W62-(#_|39Mc^FJuk=*A)b}V654=lKM73-uCL326-ih`Cw2!%fWF+W-HvAN5i zi2MVRbfcLyb%qL72_ACg;J2N=SJZNQM79F(D-PkUvOTSRdxy7$p_aV9+?sBMw^Njj zOgMdab5%rcr}xcD;fmv~B0y3a#%+Ts%F!GiwAq+Kz_V z^!}=7f!ogRtpb6!7H-tYl{U8woaq&t&uALH0K`?FR?IhU*Ah0Tt^H&5N(*&!nXtcFTB*!q>^>cPc(_8r$9S&_^ax+O7CgZsX}VT;l)8u`tzF7qmM199$(|7@7abV36tUkb_@*0;S+u}Y=o)~gKvM{We7+7dUv3c zo^PpCdIK@}M3C1ZO;s(Te{Lgx%a6aQ#Nlr$$^v!-h1{rPv4%hzn$fx3s*5THM9uNR z36ExS*;QUsH{FOKgWEO$QU{Z59QIYQ)`6ZJ(ck#xi1NOt@Ksb z#I8w?M3Y~jUHb~F0?HI}R5${SF)P!8uRL!$zVu+wIhgtWx^6(JKnZZyCys3~twz}E zNrNAz`CCqlb$UTLdDn+$r_0Z_4y73vP308~!stC#X3>D>f>x7niO*wGGjz!T!8-6x z>z&~_dX^mIJxRQdf!>#>i|T$of|cBWvH3k8XW!aaagP?S*V<|29E9+cIQG}&rH%IR zVO(FNJ?$QfL|5*LbPqi%aa?$+)+Jfi___(K&ldaXX))nKVuMS zw0X>$_bsObZ)!X@iE#I$s#G}}0rQ(LWPfjfc`yG6OJDdlWSpe+f7BfzEKf|9oBlilXPJn2M6YhZBWG?qA;*gg7! z26{q}ZnVB}GU$E!4Jj&j=*c>EtQZgrX&8sP8@rZ+EJk4C7(Q)`<&Wk-9|VPW&!>DC zj+s;}+d|Q%i6?stSy;8EXXeLo-KAb+V`w zLtTp_LcobujV@ah_TnTs`j&bq9dW7|#yqap51=|0NWY88OCuTgYGWqBWt8;h%aJs{ zH_f&Gg@|l<#zIzgocS7pA`@GNrVSCP`34b##uh%f(X9Q(u$m?NY-@{_@(GnM%+Dro zNAI{M{sElN;;3hT&aqYgY~Jb>_YV4wE6%F&5|X;F$t^0zz#!~*)tSTsr{!(7VjtHHwDOf<$hW<< zO=(lb(O5r}h6g|%f;7)+v{z%)NK`djmRs1L!7}LucRw`@9a?sKFx5Gc8if^DBL9qE6}l|yl(+!9SLMyu(%d6t^H_$e znc@I&PgIurbV_9HAe7WRw7B(v0|qNBdTRMN)EekWjygNcDBxeuqsd%|+f!>7j1$mk zk8+6LozSMz;+Bef#pX(%=&vNH@f0l_Xu?){Te9;niyp@1eUJO?(BhA1*WM{h`08zY zJ>uu?BJIu1C@wZr-WZQ3Ys-!Iq9c|*KcLD0n8!A(3o(%!LwfiGY7jPom>3+sR%~?^(vVcL-bxFsH6M;0cM@P| z!>bbcjcIu-hI{g^dA2tVkRV7yQ;GcA^xgxWf7%I^@MHy{K?xcq!#O_a{P7xbuqE7B z#K(EV%8Y|)u!Ta?_IzmmZI8I{qc3Qb#FIBJlywahS+__S93|jKqhrRHy{w4l;K|aq z&({Hw&Rs?Jme+u^_67H~@9jE4NQV&t4*+9>T%~F@!m91m)D$CaMTA zq9I{G^bu|#lz52pbWonj#8kW^({S>=g=1;D9No@z;#8Gbk1sKz!5%c+>@Aq~uj8d@ zDm(rfZ7q-}0Lj?gm?xn2+%F=N;MV5YP!UT2szc2K9|xLf#>KTu%UiLJwRB8R(*guV z3IIs1=660|xbw6;?S;d4H)gEijweCz@~b=NYGc`b+*rPXrOCpVg!Ikhd0w-e8$-)rL}q@6L5W)( zsx8iDS+{UxK|E+d@gV!4*a1V>aPac{RT;SC3BGqSo`^Jf_XYWOp1td)=NW+E%5pAF zCL{T#IEfpYA(?r)au^pLr^9O3-ZsCd0>)tchqJ^;MgR#a{SPb}ONyQ2VRB-)pazEr zDm;GbW2DTD@62w&29y6CFX0+F_3~LmdPm;-t(*mZS=zFQ``D@r3a5g;eqNu`KXgsE zi@BctCbGM6#<|ZZxX~UtmmzRV#BfBMVVRho)?%M6(& zc4`a^3~|V_=MG|fOuy0Vpwam7SYUCYy*Zb~_H+8&Sc{6~u{;w0w8J7&Cc|%zwxO*y zNf?B&xmmJ1r*T(wDGm+BaU@D`2MD&oF;}$ZEMdU#5Sf%a{yN{3kr$;y-($G1%vC2; z0N2}?Yzv9pr0(XPAGECuBvneDaZlMu>c7^>ukV@?OTeJf{!`gnuJ$w+ z|F62Kr50}d^@re^AU*}mLn$~iUy2QS9_OG~k8*s)w3p+@f;dDAsQvEb;udH%i_ zo?Hw&BHY9q*j$Rk)d+bVSkE#;)sDS?{IK&>G3>1vGX;U95C)+LuKNLeAPCfqTNW;N zAQq|DY3$@nE1w}itrQ?>KJ>*tPOy`LCueynCAHzKf|$asVg6CN<}UC^^$I1 z?5|O~)YsEQ(aJ9KPv2L^tg0<>B78i%23sK5sfeX#*ubjWDAHKzl!ba+SqDdg3zf?> z{7ehHJ_M2bDEuuj`+XdDMUZ*BO)6@xz-+#f`Hhzh*Vo3c#MAgVOC{;t|FzSykH$>w zAlX|a?HUO363EkEs1HxUqL0)1`1^>I>ggN0rhTNQobnE0O=_)2J(=-2yjD~v+D0Ke zI3Rxev$ts3&n(EhPRCQJq5KB8=nIEA&;i{`QdZGYECcA^n4082M{vyjrD@>qhdhAN zsi^|FsBmG&22Of_5}l?U0VWQf#|C&*xK>vraVKA`3E*NKDb{WDLP}50WyHXy2Um%* zq3+n)wsgqy!}P5CCZFmun{`LdxoJqsJk67&;C^Kp4Y==YZ3X!(3Egt--Om8;LpPxrwYtN zi7>^jCT>VXsEIyG?hYXVC1W`FHRXU-;8?#k_nS~kFtq%FyNn+{e^&$;4;lR=^;qj< zH?$TF7rrv68~ku;u}>*s>&s0a*U9IJDT|cyJt_ zkUVQi5 zY)wW?Vi`<>8ypk&-+LSy*anFkkTVdZW5hfJD{WVY`cx6UNI7Zbzy(#aIg6zHxpZ!l z9!Yt+x`~Krk2&C1w`V$nlBTp)H>=(_cr8OYrYfJcpqF`n+RI6do=4in;DYmTQTMmh zNb|fAErvw$U#c2u?>jF9`LaaqOX$&7GI?6KV733S@o>CjV@Qt$#It*iN*@uS|5-e! zGJO+qY`~wHW61mG-ETyAEZ{P>{Gu0vQuJc^*TLm=DH?q&;+JPQ_8AHOAWX|DKhC{I?NRNR=rTTzYWtcX!mb00foW;o{B&G`FA|#W_pv_a`uAS`1{gT z@gt?bOV4;9NUooCh#+nsIxUK^mDtEY&9g6p4T#uPpTyi}c(b1;9j0yZ zL69RQsnu^3eJ>ICKijW=_HXF;72H~SW$Pr+Xf9V;@si zUl`Xb3K;ePhNrC!4}Ni7p=Li?J_0v{SD?%87J1v+fN;FOe}{8LNrt??NG+oZhCQy> zQg6358Yt%<%-gg*F2fqzODq#=#*@_bpz6Htb6In|^-ViTyvn1>5b=Gm*3eu&GZ!;&|jWL3Qtv-b#1efM< zS$pjSx3ShejQ3=bDlrGKM4`Mb4KPPiW2ep7!2j})c@j1Q=$R$A)Q8+G8BLCSJAbPB zl9ze*u@`*-ad|U(p23-wZ`3{Ts}nkP6=!pOEXoCK7*wLs_czC#ue{6z{Fhc*lU5{8df{gnHIq%@wbW)@tzmii>;RT|Zb;qXSRPLM-fv3;m%UIjoXSTMEbO?Efu9X-ykYI#om zx71js6hj?h^?Qm4N+p=^5tO0-uA5G=v(JlFDT})8n(mc&=%?|8o_1K~Oz^v@(3(&e zrdG?#rS*Yty385ukSEWQ!~Om%^#06QG^>7a+e74p{IP$0h8DB^pr_{p4Q$bvvxNtC zcF@x~?@EH8`h9q(tn9aRHQltY%b&Y??a62;XGIOly^McQ8^6vA@-{9i*ow70T|RcQ z75pE|PZ*Ep1|cX&1|S4_5}#OIs$@`^-H?{9Du&zgH2A;7@c%zTYyMxt&|7*Bs4=>> zr33<={E}*EZzEh1JeT}5{T~Nbdbb`Jj5K3N5U{&sezT8JtZe;_qj>*^x-yZ$=r_5Q z3R$~RS8@A3oRQOAN4LL}0$!xX;|%_+sl($_!wH$>jqTuLG5>J^vHK8uFab8D6_zA1 zxiBF+6iE(u`=}Sie1G0^I(c+1&VB1n&OB0Qui(_4+~&@L)qe~;$@bfQv?#j84CqyP#=s;Y(`@g1TqVAX zaWd0=bULoTvuCYWMLGmWPNOeUZ)`?G*}RQwLKBr;ks!5=IiEbVa!)XwP|B>As&NK~ zb)mWWtHj@;{?i;_=E6qdUVi`K?X`snA*_!EyU@IA(9;4ULq*cz-(`}I63B3eCdWTSh2!ezTp@Vb*=}H$+LPtnw3aB7WiWHHeAVq-)5(MeJ z2?PR4lM+A-O}@l;-Sypd@4xTIT{nN`$(fuzGiS}-&#V)q8BC9!hMNWe0MHxgLoEP+ zD{ugSM3st^u%Zs57a^FNX2w=JmzS4>$N%xChkWTOVKZx}1Q?%ep{Sj?WcpuA9JX@ysXUzG*8D1KqXa!Y9s3& z3%v^uGdI6y?szA%zj>&W`~clRYie(WUh!7r;7S*)(3e0gB3=qJ=+P<5fb@)mjLjl} z3Pzv|?)z3ZGIC21{NVzgFCZY*h1^&WxMyE;PkT@*2=b^M2vl`TDP93^xOpPGc>xhI z`Wd;$je&`j;70UHhGx5(h@Nqq0R$bFYljU?)?DIwCRot{0=b(Kwzs;=?WOetCtx%T z@}dOv1+C&gkAEP1_(=8aSO~#)#U|UZ!RQaEvE6A-gA6|!L0J3H$Em5Iys{a&bzODY zbEk7U$HQDQ^3&D}5VubhEig|V_~9BvJddX@T8I?pX%4@*Ej~3J6_U^wRd0A+|HgmI zrb_pDQOOvWOoN|o&?;h+d*S-aDM6Phb{z+{9@5a`np6i%*2`r}C%QkS0P5>1UXV%; zjmIFcQ$mzzqb{7k-G;5_Hiyol*r+Q#mglVWo-2Q%;ml9Eb@{=nG{FkR(+)~hp=;rw zOwUYLgzZbMK&g~*g)P^C;Xt*v4<0b`sJDf0{?Zv+I#m93d0{f40zTv}3**+EBm)86 zRYV(&aN>|F7zy$#R&sOoqHQUkY@92DjBuuG4j5B1;)1V zh=QIz8kvis^5$rKR20Cur+w+|_q+brC!60}OB_4y?e3A~7DXaXD+P=EvCbP~5Hff& zW|&Fa%QgY5+9B%@p+fntifi#D-eP~p)kce|xqYHP^}{@KYH_8Rv6Nf&0T;uu#?H^)58YpFw7>Z|&E|VApWE)Vm`k?o^s3iW3r%{CF|Hg4xKIdKJQ!;Vz>Qri%q1AtIvP78@S1L{={O zCtGiH`{!<^Of|{XhAOs65V*2 zQHM)&rIG~`a%Hy&EY|v*Z5O#3^+~$==9faL+e7bvFUKn^C_UBv6E9fdEw9g8I5?kQ z9=7>4bdPlp5}@9?Os6-$a+nZ=4%JAlV=o-E$4M7?jbgt?1a@%^Px!oRBWMmnJcUk=Sh~L12Y(QFOrDh|op^%ptMo4*ZUVw$ z*Exx@SL$khJs1uBW(u#_!JM(un!B{4^l#J`#xl&j`S$gBoL?#;zw*n z2=lA7XiBQ(oNI^7uln|K?5_o=so;?3eZu=~u_s8=wLfZ2Of3avcxW_Q0B_xTqet}M z?76f4_aSSzJnoi60)}kB7A}8!p$kr|{VAo9$ydS@4U`BVKtz{tH7JL0yy|;mOtVhe z?*bS2d}ysbDL_f^A<%(goL8~g$ehLp+T&L_aNjoc1d>A%_JM>X9Dgu<_-X(bxOqjZ zfGa+S5ZcRE^rN&tmgPj)2-^-gClse;Xy=8DO{yhN$IS*MVY$7})Z;QSm`H9s&xv*Vo$P~(4EtpGXToc{n zybil*ka-!4f6Di;$2!Z9A^5K#AtdkXSFhj2=n}FQDgSOfg;4t1In`jjB<9t3r zquZ>s?@D1Cp(*DG)+WI;#GcNJzCE2D12q8@*VsV@UFYxHaLu}i%Sr)PsJ2jPImYuJFUbdj_v*UEp z>uVk^*9tmrBuB}7yiF=Uml!8UQKiGH1kq7FiG+cMF{4N&bgoR$fpOX!vC=ELswWDj z|5=R}kNqWDHBpDy-zlU;Aoh0Wt2Y*G3;_`{<%o zD!&_yE%0|o1skWv+QWZ;F5#2>EoN0_I1}=Lwz363YSQ!oQ~c=6`8l2s)H^lALn~FV zVmx~9lBObdQd)njDBV{gBB_+@BXKU8g9p%xx);$2IR|a3H%C)kKWdeWAJ0b%$~W& zH7Yo2V(RY^ifU-&-?W53n)K@hCN(~}zjAl$1$O&R``bZ&$X4c&Ao@H(VS!M_g@WA2 z5oCs7DriDrIT@cs2?%n+%M{Qpl;c_Tk8Q-6isM~Jd1wm?S8l0-sw>9256>SOEyUE+ zw^7Sc@5B%IQ&u$G%R?bwR&b|J$YI0bymdS7%v-#EEloHnm6P79|{@ z`3L{|P(@Sv;R%jm4ezFvqj9#s*gM4xk(K6deYfekwtcZQb!b}!$j-Sx2$QSWjT=bV zs`B6te|!5zXH9n#)3_O>JB_fE#PU^9^3o0eI^5w@kNS!;EUYp~`;j@|WXBkOcu}5k z0lI_5(Md9V4OOuXHD@^r!I3|Zq<SRQ&vn@2L(0S9B~etLJ71>?v;=w*@FS&TB+HoBP2b z9x26<+H;bTvptr6=!5D=(@YbvfmyN}jfkwovW#e7^f$qevL*EE(4u ztq-G8hr(D(*c5P^ergVXil+12#)}zxST&!3ku;nHPFNU1ZoJ>NZ*SHb%AG6BX^`Uz zlMK3%@RG0KR-Pw6*ws?CNVy9%wjU4*du!?%f63URm=2fYyA$ahS?cxn=NWsx^!O+W z?WNgX*;kRPSfvfl%sv7>ZRHSOp@Yb<$U^3&c+)1Yf`H58C%ToIga2|8ZtF8@4`uhf-0I3)wx=1{jw*;5ZG zPxhwY0k_Q;BKOp5m3m%l@uvA?^ZGHd$q`hd>{+1pL}!QlQ{%y$#G9mC2Th1_ESZ{>uInpTcf9=!zZ?%igw0d)u z?+fj`GfZnbUl+Zi{9UbEQ;z)Ijm*hTtIQ5y(~gqreFq9Vres>*LvO(@*3NyX1vLv@ z2`S(2ADffOvAdq`1O>40Fxc9=Z+*eD{P+B};=Xq-N@=HKV3#mL+I}aDkgcMBQDZy5 zGXFC|cCkLKK?=2V_R?y#rcQ*0^*sI~bGCK_#4Jq}`4? zevw+dIDY_(K{kFl)4iRs*ftY1e>sclaJI5LEkN zzWyU*z5mK4O^DxoWKLA@DI#F1xs@cNMGT|z=_bgTuVBTw>ESL_MQpo?PzQR3H9Vq0 zzkX?d$>UXl2G#*5?H^l)U;00PYL^wr;CRvYAmY7wmubbO+QCxWFB#9uw)s?^<%k$~ zbPQ%n*cOuG1oI$d?C^iR7yh5Tp1PyAEou@;?(l1xx?$ZlsiQP}U!QwZ*aIS$0tPy3n@A>c{BBux~6+yI%PS%_e`^FUC&GR#yyYe`cz$x#RoZJ5we&C4@?N~ zfBem!21j|ke6fu`Jt)4vQyy9W>D?%vOXv3vc_Afc=UCdwiw1Fhd1Ff5O zt)V0PjR;w=k1qVlO#NU@vcp+nSJS88RUfBQ@XQL8J+|GcAWVQOeDK)XFZ%sxJ7(;h zvn*Ow5LE}nT$1KL+%Bt|DCfIrH`}e{L~i&!abUfk0B5_{Xl_DY>38f!wL*T^cm6V3 zP_PIzpQGTbz1SMHU8WH~nlu&ez%kb>cZFH~5^Ai#v?njP-vN}8Ny@5xxCKN8ZX1ucK zFo)t~!bO<}Yj#xyTz)CD8JIN#j69JsI!o69b+-)2L)l;Hz`b5m$0&lD|47h(uafEX za$)~|7W7u<@x?}95RY@46*^oux(1K3@!7bNoCSq@-4#AlKE+k!@f3`|6b5;!CY|`b zxZl}b)*+wl)EHkDaN2+Mv5A(o1ROA$=clU)Z!v$#+)+b%IhY1|G?Zz;b;8_e^F^yM z*(-gBnV}KXeXiuE*O@!)ebo#I(VsW`kj$lXm~#bW8Y!V)mOwetN{nj z=;@mk*?n<+;hy{1vzDUTQwG(LI8v)Vq<~Fed}rS+vorePneaL2!m89k^J52L(l(yV zrs_@^k@+q+03LK{v~j<0w#gj4g_=P-~NK*JUo=xJAnS^~&w{;3Gykxu3IzSAXSusXF`uOH+b%HnL`S zj9LfC_1w6RTvfndT^?}Yggu?n9Hzwx*&?;0#HI|Xj94Ej=%ZA;0FtF8lmZIh1Q{mk z6Kp0L>2RG?02Rt0d`pO6^|5H_LK2|M^Z<lFMaQq;fcoj3B zGi6+(Nt`DXEmQuAvlz4e6HUH1&p*e8H&*03zOaz%Jez#q+}$*5_=<`}#s4-+Wk_srRqKFmYtH z-aWe3+|`$Rk*Cc623}Yf>+~1dnonN!`O%N?MX5%vPot2Wk%ma`8qBpDcSK9bxaV_p1`t@8ojgC!%McH`tZvE=U_^WdR16J&|ee7#;TNRq+{3!meTRLWZ zX4+y#cLm5T-6r%tVFIq7lIj;B0|F8CNrE*R!ts(?3kf6)%`Nz(CuyL$_20ANNbaK` zfL?0_=e|AN=ZMxPYTHa~p+1s~3E)4U zmTX-X+p_5*@8$j4V)&etDT?n@&%xHZe(+<#VuBHUxh!N^_Vo5ybbEekE?I-6qb0MF zqKTymD71Eq?asr)5|V8cm+u#GBN8%{crJ6k#t7x-hn zZCmY#@uc0eLZpw%3M)fktKx(VYgaVqDjHg-JBQ4T&Q+x_2_ZH+-RooeIAV*R4ucYy ziM@-An?zj;B>FHf-OaubI~@FUUWJV4+f)moGyKOe3X8L(PNFZ$D?^K#*y(6ZUknq` zSFtw;7F!|mfm45n=L*qxRH#ZJOk@oU>6<9+WugzI&|92H4D80=6hQTlQQ<#1pZyE` hFR4}8q6SvN*uZP&_&!+P + + + +LILO +Generic boot loader for Linux +Version 21.5 +User’s guide + + + + + + + + +
+ + + +

LILO
+Generic boot loader for Linux
+Version 21.5

+User’s guide

+
Werner Almesberger +
John R. Coffman +
(reconstructed by Joachim Wiedorn)
+
+
July 17, 2000
+
+

Contents

+
+1 Overview +
 1.1 Easy rules +
 1.2 System overview +
2 Introduction +
 2.1 Disk organization +
 2.2 Booting basics +
  2.2.1 MS-DOS alone +
  2.2.2 LOADLIN +
  2.2.3 LILO started by DOS-MBR +
  2.2.4 Several alternate branches +
  2.2.5 LILO started by BOOTACTV1 +
  2.2.6 LILO alone +
  2.2.7 Names +
 2.3 Choosing the “right” boot concept +
  2.3.1 BIOS restrictions +
  2.3.2 One disk, Linux on a primary partition +
  2.3.3 One disk, Linux on a logical partition +
  2.3.4 Two disks, Linux (at least partially) on the first disk +
  2.3.5 Two disks, Linux on second disk, first disk has an extended partition +
  2.3.6 Two disks, Linux on second disk, first disk has no extended partition +
  2.3.7 More than two disks +
  2.3.8 /boot on a DOS partition +
3 The boot prompt +
 3.1 Boot command-line options +
  3.1.1 Standard options +
  3.1.2 Device-specific options +
  3.1.3 Other options +
  3.1.4 Repeating options +
  3.1.5 Implicit options +
 3.2 Boot image selection +
4 Map installer +
 4.1 Command-line options +
  4.1.1 Show current installation +
  4.1.2 Create or update map +
  4.1.3 Change default command line +
  4.1.4 Kernel name translation + +
  4.1.5 De-installation +
  4.1.6 Print version number +
  4.1.7 Options corresponding to configuration variables +
 4.2 Configuration +
  4.2.1 Syntax +
  4.2.2 Global options +
  4.2.3 General per-image options +
  4.2.4 Per-image options for kernels +
 4.3 Boot image types +
  4.3.1 Booting kernel images from a file +
  4.3.2 Booting kernel images from a device +
  4.3.3 Booting a foreign operating system +
 4.4 Disk geometry +
  4.4.1 Obtaining the geometry +
  4.4.2 Specifying the geometry +
 4.5 Partition table manipulation +
  4.5.1 Partition activation +
  4.5.2 Partition type change rules +
  4.5.3 Partition type changes +
 4.6 Keyboard translation +
  4.6.1 Compiling keyboard translation tables +
  4.6.2 Using keyboard translation tables +
5 Installation and updates +
 5.1 Installation +
  5.1.1 Compatibility +
  5.1.2 Quick installation +
  5.1.3 Files +
  5.1.4 Normal first-time installation +
  5.1.5 Build-time configuration +
  5.1.6 Floppy disk installation +
 5.2 Updates +
  5.2.1 LILO update +
  5.2.2 Kernel update +
  5.2.3 System upgrade +
 5.3 LILO de-installation +
 5.4 Installation of other operating systems +
6 Troubleshooting +
 6.1 Map installer warnings and errors +
  6.1.1 Fatal errors +
  6.1.2 Warnings +
 6.2 Boot loader messages +
  6.2.1 LILO start message +
  6.2.2 Disk error codes +
 6.3 Other problems +
+

 
This document has only been partially updated and does reflect the status of Linux (until +2.2.16) and of LILO (until 21.5) in the year 2000.  
+

+

+

1 Overview

+

LILO is a versatile boot loader for Linux. It does not depend on a specific file system, can boot Linux kernel +images from floppy disks and from hard disks and can even act as a “boot manager” for other operating +systems.2 + +

One of up to sixteen different images can be selected at boot time. Various parameters, such as the root +device, can be set independently for each kernel. LILO can even be used as the master boot +record. +

This document introduces the basics of disk organization and booting, continues with an overview of +common boot techniques and finally describes installation and use of LILO in greater detail. The +troubleshooting section at the end describes diagnostic messages and contains suggestions for most problems +that have been observed in the past. +

Please read at least the sections about installation and configuration if you’re already using an older version +of LILO. This distribution is accompanied by a file named INCOMPAT that describes further incompatibilities +to older versions. +

For the impatient: there is a quick-installation script to create a simple but quite usable installation. See +section 5.1.2 for details. +

+

1.1 Easy rules

+

But wait here are a few easy rules that will help you to avoid most problems people experience with +LILO: +

+
    +
  • Don’t panic. If something doesn’t work, try to find out what is wrong, try to verify your + assumption and only then attempt to fix it. +
  • +
  • Read the documentation. Especially if what the system does doesn’t correspond to what you + think it should do. +
  • +
  • Make sure you have an emergency boot disk, that you know how to use it, and that it is always + kept up to date. +
  • +
  • Run /sbin/lilo whenever the kernel or any part of LILO, including its configuration file, + has changed. When in doubt, run it. You can’t run /sbin/lilo too many times. +
  • +
  • If performing a destructive upgrade and/or erasing your Linux partitions, de-install + LILO before that if using it as the MBR. +
  • +
  • Don’t trust setup scripts. Always verify the /etc/lilo.conf they create before booting. +
  • +
  • If using a big disk, be prepared for inconveniences: you may have to use the linear option.
+ +

+

+

1.2 System overview

+

LILO is a collection of several programs and other files: +

+

+The map installer
is the program you run under Linux to put all files belonging to LILO at the + appropriate places and to record information about the location of data needed at boot time. + This program normally resides in /sbin/lilo. It has to be run to refresh that information + whenever any part of the system that LILO knows about changes, e.g. after installing a new + kernel. +
+Various files
contain data LILO needs at boot time, e.g. the boot loader. Those files normally reside + in /boot. The most important files are the boot loader (see below) and the map file (/boot/map), + where the map installer records the location of the kernel(s).3 + Another important file is the configuration file, which is normally called /etc/lilo.conf +
+The boot loader
is the part of LILO that is loaded by the BIOS and that loads kernels or the + boot sectors of other operating systems. It also provides a simple command-line interface to + interactively select the item to boot and to add boot options.
+

LILO primarily accesses the following parts of the system: +

+

+The root file system partition
is important for two reasons: first, LILO sometimes has to tell + the kernel where to look for it. Second, it is frequently a convenient place for many other items + LILO uses, such as the boot sector, the /boot directory, and the kernels. +
+The boot sector
contains the first part of LILO’s boot loader. It loads the much larger second-stage + loader. Both loaders are typically stored in the file /boot/boot.b +
+The kernel
is loaded and started by the boot loader. Kernels typically reside in the root directory + or in /boot.
+

Note that many of the files LILO needs at boot time have to be accessible with the BIOS. This creates +certain restrictions, see section 2.3.1. +

+ +

+

2 Introduction

+

The following sections describe how PCs boot in general and what has to be known when booting Linux +and using LILO in particular. +

+

+

2.1 Disk organization

+

When designing a boot concept, it is important to understand some of the subtleties of how +PCs typically organize disks. The most simple case are floppy disks. They consist of a boot +sector, some administrative data (FAT or super block, etc.) and the data area. Because that +administrative data is irrelevant as far as booting is concerned, it is regarded as part of the data area for +simplicity. +

+

+
+|------------|----------------------|
+|-Boot-sector--                      |
+|                                   |
+|             Data area             |
+|                                   |
+ ------------------------------------
+
+

The entire disk appears as one device (e.g. /dev/fd0) on Linux. +

The MS-DOS boot sector has the following structure: +

+

+
+       0x000 |Jump--to-the-program--code-|
+             |--------------------------|
+       0x003 |                          |
+             |     Disk parameters      |
+             |--------------------------|
+0x02C/0x03E  |                          |
+             |      Program  code       |
+             |                          |
+             |                          |
+       0x1FE |-Magic-number--(0xAA55-)--|
+             ---------------------------|
+
+

LILO uses a similar boot sector, but it does not contain the disk parameters part. This is no problem for +Minix, Ext2 or similar file systems, because they don’t look at the boot sector, but putting a LILO boot +sector on an MS-DOS file system would make it inaccessible for MS-DOS. +

Hard disks are organized in a more complex way than floppy disks. They contain several data areas called +partitions. Up to four so-called primary partitions can exist on an MS-DOS hard disk. If more partitions are +needed, one primary partition is used as an extended partition that contains several logical +partitions. +

The first sector of each hard disk contains a partition table, and an extended partition and each logical +partition contains a partition table too. +

+

+
+|------------------------------------------|
+|Partition table                  /dev/hda   |
+| |Partition-1-------------------/dev/hda1--|
+| |                                        |
+| |----------------------------------------|
+| |Partition 2                   /dev/hda2  |
+--------------------------------------------
+
+

The entire disk can be accessed as /dev/hda, /dev/hdb, /dev/sda, etc. The primary partitions are +/dev/hda1 /dev/hda4. +

+

+ +
+|------------------------------------------|
+|Partition-table------------------/dev/hda---|
+| |Partition 1                   /dev/hda1  |
+| |----------------------------------------|
+| |Partition 2                   /dev/hda2  |
+| |                                        |
+| |Extended--partition------------/dev/hda3--|
+| | |--------------------------------------|
+| | |Extended--partition-table---------------|
+| | |Partition 3                 /dev/hda5  |
+| | |--------------------------------------|
+| | |Extended--partition-table---------------|
+| | |Partition 4                 /dev/hda6  |
+| | |                                      |
+--------------------------------------------
+
+

This hard disk has two primary partitions and an extended partition that contains two logical partitions. +They are accessed as /dev/hda5 +

Note that the partition tables of logical partitions are not accessible as the first blocks of some devices, +while the main partition table, all boot sectors and the partition tables of extended partitions +are. +

Partition tables are stored in partition boot sectors. Normally, only the partition boot sector of the entire +disk is used as a boot sector. It is also frequently called the master boot record (MBR). Its structure is as +follows: +

+

+
+       |------------------------|
+0x000  |                        |
+       |     Program code       |
+       |                        |
+       |------------------------|
+0x1BE  |     Partition table     |
+       |                        |
+       |------------------------|
+0x1FE  -Magic-number--(0xAA55--)--
+
+

The LILO boot sector is designed to be usable as a partition boot sector. (I.e. there is room for the +partition table.) Therefore, the LILO boot sector can be stored at the following locations: +

+ +
    +
  • boot sector of a Linux floppy disk. (/dev/fd0, ) +
  • +
  • MBR of the first hard disk. (/dev/hda, /dev/sda, ) +
  • +
  • boot sector of a primary Linux file system partition on the first hard disk. (/dev/hda1, ) +
  • +
  • partition boot sector of an extended partition on the first hard disk. (/dev/hda1, )4
+

It can’t be stored at any of the following locations: +

+
    +
  • boot sector of a non-Linux floppy disk or primary partition. +
  • +
  • a Linux swap partition. +
  • +
  • boot sector of a logical partition in an extended partition.5 +
  • +
  • on the second hard disk. (Unless for backup installations, if the current first disk will be removed + or disabled, or if some other boot loader is used, that is capable of loading boot sectors from + other drives.)
+

Although LILO tries to detect attempts to put its boot sector at an invalid location, you should not rely on +that. +

+

+

2.2 Booting basics

+

When booting from a floppy disk, the first sector of the disk, the so-called boot sector, is loaded. That boot +sector contains a small program that loads the respective operating system. MS-DOS boot sectors also +contain a data area, where disk and file system parameters (cluster size, number of sectors, number of +heads, etc.) are stored. +

When booting from a hard disk, the very first sector of that disk, the so-called master boot +record (MBR) is loaded. This sector contains a loader program and the partition table of the +disk. The loader program usually loads the boot sector, as if the system was booting from a +floppy. + +

Note that there is no functional difference between the MBR and the boot sector other than that the MBR +contains the partition information but doesn’t contain any file system-specific information (e.g. MS-DOS +disk parameters). +

The first 446 (0x1BE) bytes of the MBR are used by the loader program. They are followed by the partition +table, with a length of 64 (0x40) bytes. The last two bytes contain a magic number that is sometimes used +to verify that a given sector really is a boot sector. +

There is a large number of possible boot configurations. The most common ones are described in the +following sections. +

+

+
2.2.1 MS-DOS alone
+

+

+
+|--------------------------------------------------------|
+|Master-Boot-Record-Boot-sector---------Operating system--|
+-DOS--MBR--------→----MS--DOS--------→----COMMAND.COM--------
+
+

This is what usually happens when MS-DOS boots from a hard disk: the DOS-MBR determines the active +partition and loads the MS-DOS boot sector. This boot sector loads MS-DOS and finally passes control to +COMMAND.COM. (This is greatly simplified.) +

+

+
2.2.2 LOADLIN
+

+

+ +
+|--------------------------------------------------------------|
+|MasterBoot-Record-Boot--sector-------Operating-systems-----------
+|DOS -MBR  ----→   MS  -DOS  --- -→   COMMAND.COM
+---------------→---LOADLIN-------→---Linux----------------------
+
+

A typical LOADLIN setup: everything happens like when booting MS-DOS, but in CONFIG.SYS or +AUTOEXEC.BAT, LOADLIN is invoked. Typically, a program like BOOT.SYS is used to choose among +configuration sections in CONFIG.SYS and AUTOEXEC.BAT. This approach has the pleasant property that no +boot sectors have to be altered. +

Please refer to the documentation accompanying the LOADLIN package for installation instructions and +further details. +

+

+
2.2.3 LILO started by DOS-MBR
+

+

+
+|--------------------------------------------------------|
+|Master Boot Record Boot sector        Operating system   |
+|DOS---MBR-------→---LILO-----------→---Linux-------------|
+|                                                        |
+----------------→---other-OS-----------------------------
+
+

This is a “safe” LILO setup: LILO is booted by the DOS-MBR. No other boot sectors have to be touched. +If the other OS (or one of them, if there are several other operating systems being used) should +be booted without using LILO, the other partition has to be marked “active” with fdisk or +activate. +

Installation:

+
    +
  • install LILO with its boot sector on the Linux partition. +
  • +
  • use fdisk or activate to make that partition active. +
  • +
  • reboot.
+ +

Deinstallation:

+
    +
  • make a different partition active. +
  • +
  • install whatever should replace LILO and/or Linux.
+

+

+
2.2.4 Several alternate branches
+

+

+
+|--------------------------------------------------------------|
+|MasterBoot-Record-Boot--sector-------Operating-systems-----------
+|DOS -MBR  ----→   MS  -DOS  --- -→   COMMAND.COM
+|             -→   LOADLIN    ---→   Linux
+|             -→   LILO  ----- --→   Linux
+---------------→---MS---DOS--—--⋅⋅⋅------------------------------
+
+

An extended form of the above setup: the MBR is not changed and both branches can either boot Linux or +MS-DOS. (LILO could also boot other operating systems.) +

+

+
2.2.5 LILO started by BOOTACTV6
+

+

+ +

+
+|--------------------------------------------------------|
+|Master-Boot-Record-Boot-sector--------Operating-system---|
+|BOOTACTV     --→   LILO  ------- -→   Linux             |
+|             - →   other OS
+---------------------------------------------------------
+
+

Here, the MBR is replaced by BOOTACTV (or any other interactive boot partition +selector) and the choice between Linux and the other operating system(s) can be made +at boot time. This approach should be used if LILO fails to boot the other operating +system(s).7 +

Installation:

+
    +
  • boot Linux. +
  • +
  • make a backup copy of your MBR on a floppy disk, e.g.
    dd if=/dev/hda of=/fd/MBR bs=512 count=1 +
  • +
  • install LILO with the boot sector on the Linux partition. +
  • +
  • install BOOTACTV as the MBR, e.g.
    dd if=bootactv.bin of=/dev/hda bs=446 count=1 +
  • +
  • reboot.
+

Deinstallation:

+
    +
  • boot Linux. +
  • +
  • restore the old MBR, e.g.
    dd if=/MBR of=/dev/hda bs=446 count=1
    or FDISK /MBR under MS-DOS.
+

If replacing the MBR appears undesirable and if a second Linux partition exists (e.g. /usr, +not a swap partition), BOOTACTV can be merged with the partition table and stored as the + +“boot sector” of that partition. Then, the partition can be marked active to be booted by the +DOS-MBR. +

Example: + +

+
+# dd if=/dev/hda of=/dev/hda3 bs=512 count=1 + 
# dd if=bootactv.bin of=/dev/hda3 bs=446 count=1
+

+

WARNING: Whenever the disk is re-partitioned, the merged boot sector on that “spare” Linux partition +has to be updated too. +

+
2.2.6 LILO alone
+

+

+
+|------------------------------------|
+|MasterBoot-Record-Operating-system--|
+|LILO --- -----→   Linux             |
+|             -→   other OS          |
+--------------------------------------
+
+

LILO can also take over the entire boot procedure. If installed as the MBR, LILO is responsible for either +booting Linux or any other OS. This approach has the disadvantage, that the old MBR is overwritten and +has to be restored (either from a backup copy, with FDISK /MBR on recent versions of MS-DOS or +by overwriting it with something like BOOTACTV) if Linux should ever be removed from the +system. +

You should verify that LILO is able to boot your other operating system(s) before relying on this +method. +

Installation:

+
    +
  • boot Linux. +
  • +
  • make a backup copy of your MBR on a floppy disk, e.g.
    dd if=/dev/hda of=/fd/MBR bs=512 count=1 +
  • +
  • install LILO with its boot sector as the MBR. + +
  • +
  • reboot.
+

Deinstallation:

+
    +
  • boot Linux. +
  • +
  • restore the old MBR, e.g.
    dd if=/fd/MBR of=/dev/hda bs=446 count=1
+

If you’ve installed LILO as the master boot record, you have to explicitly specify the boot sector +(configuration variable boot=) when updating the map. Otherwise, it will try to use the boot sector of +your current root partition, which will usually work, but it will probably leave your system +unbootable. +

+

+
2.2.7 Names
+

The following names have been used to describe boot sectors or parts of operating systems: +

+

+“DOS-MBR”
is the original MS-DOS MBR. It scans the partition table for a partition that is + marked “active” and loads the boot sector of that partition. Programs like MS-DOS’ FDISK, + Linux fdisk or activate (accompanies LILO) can change the active marker in the partition table. +
+“MS-DOS”
denotes the MS-DOS boot sector that loads the other parts of the system (IO.SYS, + etc.). +
+“COMMAND.COM”
is the standard command interpreter of MS-DOS. +
+“LOADLIN”
is a program that loads a Linux kernel image from an MS-DOS partition into memory + and executes it. It is usually invoked from CONFIG.SYS and is used in combination with a + CONFIG.SYS configuration switcher, like BOOT.SYS.8 +
+“LILO”
can either load a Linux kernel or the boot sector of any other operating system. It has a first + + stage boot sector that loads the remaining parts of LILO from various locations.9 +
+“BOOTACTV”
permits interactive selection of the partition from which the boot sector should + be read. If no key is pressed within a given interval, the partition marked active is booted. + BOOTACTV is included in the pfdisk package. There are also several similar programs, like + PBOOT and OS-BS.10
+

+

+

2.3 Choosing the “right” boot concept

+

Although LILO can be installed in many different ways, the choice is usually limited by the present +setup and therefore, typically only a small number of configurations which fit naturally into an +existing system remains. The following sections describe various possible cases. See also section +2.3.1. +

The configuration file /etc/lilo.conf for the examples could look like this: + +

+
+boot = /dev/hda2 + 
compact + 
image = /vmlinuz + 
image = /vmlinuz.old + 
other = /dev/hda1 + 
  table = /dev/hda + 
  label = msdos
+

+

It installs a Linux kernel image (/vmlinuz), an alternate Linux kernel image (/vmlinuz.old) and a chain +loader to boot MS-DOS from /dev/hda1. The option compact on the second line instructs the map installer +to optimize loading. +

In all examples, the names of the IDE-type hard disk devices (/dev/hda) are used. Everything applies to +other disk types (e.g. SCSI disks; /dev/sda) too. +

+

+
2.3.1 BIOS restrictions
+

Nowadays, an increasing number of systems is equipped with comparably large disks or even with +multiple disks. At the time the disk interface of the standard PC BIOS has been designed (about +16 years ago), such configurations were apparently considered to be too unlikely to be worth +supporting. +

The most common BIOS restrictions that affect LILO are the limitation to two hard disks and the inability +to access more than 1024 cylinders per disk. LILO can detect both conditions, but in order to work around +the underlying problems, manual intervention is necessary. +

The drive limit does not exist in every BIOS. Some modern motherboards and disk controllers +are equipped with a BIOS that supports more (typically four) disk drives. When attempting +to access the third, fourth, etc. drive, LILO prints a warning message but continues. Unless +the BIOS really supports more than two drives, the system will not be able to boot in that +case.11 +

The cylinder limit is a very common problem with IDE disks. There, the number of cylinders may already +exceed 1024 if the drive has a capacity of more than 504 MB. Many SCSI driver BIOSes present the disk +geometry in a way that makes the limit occur near 1 GB. Modern disk controllers may even push + +the limit up to about 8 GB. All cylinders beyond the 1024th are inaccessible for the BIOS. +LILO detects this problem and aborts the installation (unless the linear option is used, see section +4.2.2). +

Note that large partitions that only partially extend into the “forbidden zone” are still in jeopardy even +if they appear to work at first, because the file system does not know about the restrictions +and may allocate disk space from the area beyond the 1024th cylinder when installing new +kernels. LILO therefore prints a warning message but continues as long as no imminent danger +exists. +

There are four approaches of how such problems can be solved:

+
    +
  • use of a different partition which is on an accessible disk and which does not exceed the 1024 + cylinder limit. If there is only a DOS partition which fulfills all the criteria, that partition can + be used to store the relevant files. (See section 2.3.8.) +
  • +
  • rearranging partitions and disks. This is typically a destructive operation, so extra care should + be taken to make good backups. +
  • +
  • if the system is running DOS or Windows 95, LOADLIN can be used instead of LILO. +
  • +
  • if all else fails, installation of a more capable BIOS, a different controller or a different disk + configuration.
+

LILO depends on the BIOS to load the following items:

+
    +
  • /boot/boot.b +
  • +
  • /boot/map (created when running /sbin/lilo) +
  • +
  • all kernels +
  • +
  • the boot sectors of all other operating systems it boots +
  • +
  • the startup message, if one has been defined
+

Normally, this implies that the Linux root file system should be in the “safe” area. However, it is already +sufficient to put all kernels into /boot and to either mount a “good” partition on /boot or to let /boot be a +symbolic link pointing to or into such a partition. +

See also /usr/src/linux/Documentation/ide.txt (or /usr/src/linux/drivers/block/README.ide in +older kernels) for a detailed description of problems with large disks. +

+
2.3.2 One disk, Linux on a primary partition
+ +

If at least one primary partition of the first hard disk is used as a Linux file system (/, /usr, etc. but not as +a swap partition), the LILO boot sector should be stored on that partition and it should be booted by the +original master boot record or by a program like BOOTACTV. +

+

+
+   |------------------------|
+   |MBR----------/dev/hda---|
+   | |MS--DOS----/dev/hda1--|
+→  ---Linux-/----/dev/hda2---
+
+

In this example, the boot variable could be omitted, because the boot sector is on the root +partition. +

+

+
2.3.3 One disk, Linux on a logical partition
+

If no primary partition is available for Linux, but at least one logical partition of an extended partition on +the first hard disk contains a Linux file system, the LILO boot sector should be stored in the partition +sector of the extended partition and it should be booted by the original master boot record or by a program +like BOOTACTV. +

+

+
+   |------------------------|
+   |MBR----------/dev/hda---|
+   | |MS -DOS    /dev/hda1  |
+→  | |Extended---/dev/hda2--|
+   | |  |Linux---/dev/hda5--|
+   | |  |-------------------|
+   ------...-----/dev/hda6---
+
+ +

Because many disk partitioning programs refuse to make an extended partition (in our example /dev/hda2) +active, you might have to use activate, which comes with the LILO distribution. +

OS/2 BootManager should be able to boot LILO boot sectors from logical partitions. The installation on +the extended partition itself is not necessary in this case. +

+

+
2.3.4 Two disks, Linux (at least partially) on the first disk
+

This case is equivalent to the configurations where only one disk is in the system. The Linux boot sector +resides on the first hard disk and the second disk is used later in the boot process. +

Only the location of the boot sector matters – everything else (/boot/boot.b, /boot/map, the root file +system, a swap partition, other Linux file systems, etc.) can be located anywhere on the second disk, +provided that the constraints described in section 2.3.1 are met. +

+

+
2.3.5 Two disks, Linux on second disk, first disk has an extended partition
+

If there is no Linux partition on the first disk, but there is an extended partition, the LILO boot sector can +be stored in the partition sector of the extended partition and it should be booted by the original master +boot record or by a program like BOOTACTV. +

+

+
+   |-------First-disk-------|  |-----Second--disk-------|
+   |MBR          /dev/hda   |  |MBR          /dev/hdb   |
+   |  |MS--DOS----/dev/hda1--|  | |Linux------/dev/hdb1--|
+→  |  |Extended--/dev/hda2--|  | |...--------/dev/hdb2--|
+   |  | |-------------------|  | |                      |
+   |  | |...-----/dev/hda5--|  | |                      |
+   ------...-----/dev/hda6---  --------------------------
+
+

The program activate, that accompanies LILO, may have to be used to set the active marker on an extended +partition, because MS-DOS’ FDISK and some older version of Linux fdisk refuse to do that. (Which is +generally a good idea.) + +

+

+
2.3.6 Two disks, Linux on second disk, first disk has no extended partition
+

If there is neither a Linux partition nor an extended partition on the first disk, then there’s only one place +left, where a LILO boot sector could be stored: the master boot record. +

In this configuration, LILO is responsible for booting all other operating systems too. +

+

+
+   |-------First-disk-------|  |-----Second--disk-------|
+→  |MBR----------/dev/hda---|  |MBR----------/dev/hdb---|
+   |  |MS--DOS----/dev/hda1--|  | |Linux------/dev/hdb1--|
+   ----...-------/dev/hda2---  ---...--------/dev/hdb2---
+
+

You should back up your old MBR before installing LILO and verify that LILO is able to boot your other +operating system(s) before relying on this approach. +

The line boot = /dev/hda2 in /etc/lilo.conf would have to be changed to boot = /dev/hda in this +example. +

+

+
2.3.7 More than two disks
+

On systems with more than two disks, typically only the first two can be accessed. The configuration choices +are therefore the same as with two disks. +

When attempting to access one of the extra disks, LILO displays a warning message (Warning: BIOS +drive 0xnumber may not be accessible) but does not abort. This is done in order to allow the lucky +few whose BIOS (or controller-BIOS) does support more than two drives to make use of this feature. By all +others, this warning should be considered a fatal error. +

Note that the two disks restriction is only imposed by the BIOS. Linux normally has no problems using all +disks once it is booted. + +

+

+
2.3.8 /boot on a DOS partition
+

Recent kernels support all the functions LILO needs to map files also on MS-DOS (or UMSDOS) file +systems. Since DOS partitions tend to occupy exactly the places where BIOS restrictions (see section 2.3.1) +are invisible, they’re an ideal location for /boot if the native Linux file systems can’t be used because of +BIOS problems. +

In order to accomplish this, the DOS partition is mounted read-write, a directory (e.g. /dos/linux) is +created, all files from /boot are moved to that directory, /boot is replaced by a symbolic link to it, the +kernels are also moved to the new directory, their new location is recorded in /etc/lilo.conf, and finally +/sbin/lilo is run. +

From then on, new kernels must always be copied into that directory on the DOS partition +before running /sbin/lilo, e.g. when recompiling a kernel, the standard procedure changes +from + +

+
+# make zlilo
+

+

to + +

+
+# make zImage + 
# mv /dos/linux/vmlinuz /dos/linux/vmlinuz.old + 
# mv arch/i386/boot/zImage /dos/linux/vmlinuz + 
# /sbin/lilo
+

+

WARNING: De-fragmenting such a DOS partition is likely to make Linux or even the whole +system unbootable. Therefore, the DOS partition should either not be de-fragmented, or a Linux +boot disk should be prepared (and tested) to bring up Linux and to run /sbin/lilo after the +de-fragmentation.12 +

+ +

+

3 The boot prompt

+

Immediately after it’s loaded, LILO checks whether one of the following is happening: +

+
    +
  • any of the [Shift], [Control] or [Alt] keys is pressed. +
  • +
  • [CapsLock] or [ScrollLock] is set.
+

If this is the case, LILO displays the boot: prompt and waits for the name of a boot +image (i.e. Linux kernel or other operating system). Otherwise, it boots the default boot +image13 +or – if a delay has been specified – waits for one of the listed activities until that amount of time has +passed. +

At the boot prompt, the name of the image to boot can be entered. Typing errors can be corrected with +[BackSpace], [Delete], [Ctrl U] and [Ctrl X]. A list of known images can be obtained by pressing [?] or +[Tab]. +

If [Enter] is pressed and no file name has been entered, the default image is booted. +

+

3.1 Boot command-line options

+

LILO is also able to pass command-line options to the kernel. Command-line options are words that follow +the name of the boot image and that are separated by spaces. +

Example: + +

+
+boot: linux single root=200
+

+

This document only gives an overview of boot options. Please consult Paul Gortmaker’s BootPrompt-HOWTO +for a more complete and more up to date list. You can get it from +

ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/BootPrompt-HOWTO.gz +

or from one of the many mirror sites. +

+

+
3.1.1 Standard options
+

Recent kernels recognize a large number of options, among them are debug, no387, no-hlt, ramdisk=size, +reserve=base,size,, root=device, ro, and rw. All current init programs also recognize the option single. +The options lock and vga are processed by the boot loader itself. Boot command-line options are always +case-sensitive. +

single boots the system in single-user mode. This bypasses most system initialization procedures and +directly starts a root shell on the console. Multi-user mode can typically be entered by exiting the +single-user shell or by rebooting. +

root=device changes the root device. This overrides settings that may have been made in the +boot image and on the LILO command line. device is either the hexadecimal device number +14 or the full path name of +the device, e.g. /dev/hda3.15 + +

reserve=base,size, reserves IO port regions. This can be used to prevent device drivers from auto-probing +addresses where other devices are located, which get confused by the probing. +

ro instructs the kernel to mount the root file system read-only. rw mounts it read-write. If neither ro nor rw +is specified, the setting from the boot image is used. +

no-hlt avoids executing a HLT instructions whenever the system is idle. HLT normally significantly reduces +power consumption and therefore also heat dissipation of the CPU, but may not work properly with some +clone CPUs. no387 disables using the hardware FPU even if one is present. +

debug enables more verbose console logging. +

Recent kernels also accept the options init=name and noinitrd. init specifies the name of the init +program to execute. Therefore, if single mode cannot be entered because init is mis-configured, one may still +be able to reach a shell using init=/bin/sh. noinitrd disables automatic loading of the initial RAM disk. +Instead, its content is then available on /dev/initrd. +

vga=mode alters the VGA mode set at startup. The values normal, extended, ask or a decimal number are +recognized. (See also page §.) +

kbd=code, preloads a sequence of keystrokes in the BIOS keyboard buffer. The keystrokes have to be +entered as 16 bit hexadecimal numbers, with the upper byte containing the scan code and the lower byte +containing the ASCII code. Note that most programs only use the ASCII code, so the scan code can +frequently be omitted. Scan code tables can be found in many books on PC hardware. Note that scan codes +depend on the keyboard layout. +

Finally, lock stores the current command-line as the default command-line, so that LILO boots the same +image with the same options (including lock) when invoked the next time. +

+
3.1.2 Device-specific options
+

There is also a plethora of options to specify certain characteristics (e.g. IO and memory addresses) of +devices. Some common ones are ether, floppy, hd, bmouse, and sound. The usage of these options is +option=number,. Please consult the corresponding FAQs and HOWTOs for details. For an overview of all +available options, consult the file init/main.c in the kernel source tree. +

+

+
3.1.3 Other options
+

Options of the type variable=value which are neither standard options nor device-specific options, cause the +respective variables to be set in the environment passed to init. The case of the variable name is preserved, +i.e. it isn’t automatically converted to upper case. +

Note that environment variables passed to init are typically available in system initialization scripts (e.g. +/etc/rc.local), but they’re not visible from ordinary login sessions, because the login program removes +them from the user’s environment. + +

+

+
3.1.4 Repeating options
+

The effect of repeating boot command-line options depends on the +options.16 +There are three possible behaviours: +

Options that only enable or disable a certain functionality can be repeated any number of times. debug, +lock, no-hlt, and no387 fall into this category. +

Other options change a global setting whenever they appear, so only the value or presence of the last option +matters. The antagonists ro and rw are such options. Also, ramdisk, root, and vga work this way. +Example: ro rw would mount the root file system read-write. +

Finally, when reserve and many device-specific options are repeated, each occurrence has its own meaning, +e.g. +

hd= hd= would configure two hard disks, and +

reserve=0x300,8 reserve=0x5f0,16 would reserve the ranges 0x300 to 0x307 and 0x5f0 to 0x5ff (which is +equivalent to writing reserve=0x300,8,0x5f0,16). +

+
3.1.5 Implicit options
+

LILO always passes the string BOOT_IMAGE=name to the kernel, where name is the name by which the +kernel is identified (e.g. the label). This variable can be used in /etc/rc to select a different behaviour, +depending on the kernel. +

When booting automatically, i.e. without human intervention, the word auto is also passed +on the command line. This can be used by init to suppress interactive prompts in the boot +phase. +

+

+

3.2 Boot image selection

+

The details of selecting the boot image are somewhat complicated. The following tables illustrate them. +First, if neither prompt is set nor a shift key is being pressed: +

+ +

+
+                        |
+ Externally   Command   | Auto-  Booted  image
+  provided     line in  | matic
+ cmd. line17   map file18 |boot19
+-----No----------No-----|--Yes---Default-image--------------- 17Externally provided command lines could be used to add front- ends to LILO. They would pass the respective 18This command line is set by invoking the map installer with the -R option, by using the boot command -line option
+     Yes         —      |  Yes   Specified by external      command string to LILO, which would then interpret it like keyboard input. This feature is currently not used. lock, or if a fallback command line is set (with fallback).                                    19I.e. the keyword auto is a
+                        |
+                        |        command   line
+     No          Yes    |  Yes   Specified by command   line
+                        |        in map file
+
+

If prompt is not set and a shift key is being pressed: +

+
+                                    |
+  Input    Empty   Extern.  Cmd.l.  |Auto-  Booted  image
+ timeout   cmd.l.   cmd.l.  in map  |matic
+                              file   |boot
+----No------No-------—--------—-----|-No----Specified-by-the-user-
+                                    |
+    No      Yes      —        —     | No    Default image
+   Yes      n/a      —        —     | Yes   Default image
+
+

Finally, if the configuration variable prompt is set: +

+
+   Input    Empty   Extern.   Cmd.l. |Auto -  Booted image
+                                    |
+  timeout   cmd.l.   cmd.l.  in map  |matic
+------------------------------file---|-boot------------------------
+    No       No      No       No    | No     Specified by the user
+    No      Yes      No       No    | No     Default image
+    Yes     n/a      No       No    | Yes    Default image
+   n/a      n/a      Yes       —    | Yes    Specified by external
+                                    |        command  line
+                                    |
+   n/a      n/a      No       Yes   | Yes    Specified by command
+                                    |        line in map  file
+
+

Note that LILO pauses for the amount of time specified in delay when at the end of a default command +line. The automatic boot can then be interrupted by pressing a modifier key ([Shift], [Ctrl], +etc.). +

The default image is the first image in the map file or the image specified with the default +variable. However, after an unsuccessful boot attempt, the respective image becomes the default +image. +

+ +

+

4 Map installer

+

The map installer program /sbin/lilo updates the boot sector and creates the map file. If the map +installer detects an error, it terminates immediately and does not touch the boot sector and the map +file. +

Whenever the map installer updates a boot sector, the original boot sector is copied to
/boot/boot.number
where number is the hexadecimal device number. If such a file already exists, no backup copy is made. +Similarly, a file
/boot/part.number
is created if LILO modifies the partition table. (See page §.) +

+

+

4.1 Command-line options

+

The LILO map installer can be invoked in the following ways: +

+

+
4.1.1 Show current installation
+

The currently mapped files are listed. With -v, also many parameters are shown. +

+

/sbin/lilo [ -C config_file ] -q [ -m map_file ] [ -v ]   +

+

+-C config_file
 
Specifies the configuration file that is used by the map installer (see section 4.2). If -C is omitted, + /etc/lilo.conf is used. +
+-m map_file
 
Specifies an alternate map file. See also sections 4.1.7 and 4.2.2. +
+-q
 
Lists the currently mapped files. +
+-v
 
Increase verbosity. See also sections 4.1.7 and 4.2.2.
+ +

+

+
4.1.2 Create or update map
+

A new map is created for the images described in the configuration file /etc/lilo.conf and they are +registered in the boot sector. +

+

/sbin/lilo [ -C config_file ] [ -b boot_device ] [ -c ] [ -l ] [ -i boot_sector ]
        [ -f disk_tab ] [ -m map_file ] [ -d delay ] [ -v ] [ -t ] [ -s save_file |
        -S save_file ] [ -P fix | -P ignore ] [ -r root_dir ]   +

+

+-b boot<_device
 
Specifies the boot device. See also sections 4.1.7 and 4.2.2. +
+-c
 
Enables map compaction. See also sections 4.1.7 and 4.2.2. +
+-C config_file
 
Specifies an alternate configuration file. See also section 4.1.1. +
+-d delay
 
Sets the delay before LILO boots the default image. Note that the delay is specified in tenths + of a second. See also sections 4.1.7 and 4.2.2. +
+-D name
 
Specifies the default image. See also sections 4.1.7 and 4.2.2. +
+-f disk_tab
 
Specifies a disk parameter table file. See also sections 4.1.7 and 4.2.2. +
+-i boot_sector
 
Specifies an alternate boot file. See also sections 4.1.7 and 4.2.2. +
+-L
 
Enables lba32 sector addresses. See also sections 4.1.7 and 4.2.2. +
+-l
 
Enables linear sector addresses. See also sections 4.1.7 and 4.2.2. + +
+-m map_file
 
Specifies an alternate map file. See also sections 4.1.7 and 4.2.2. +
+-P mode
 
Specifies how invalid partition table entries should be handled. See also sections 4.1.7 and 4.2.2. +
+-r root_directory
 
Chroots to the specified directory before doing anything else. This is useful when running the + map installer while the normal root file system is mounted somewhere else, e.g. when recovering + from an installation failure with a recovery disk. The -r option is implied if the environment + variable ROOT is set.20 + The current directory is changed to the new root directory, so using relative paths may not + work. +
+-s save_file
 
Specifies an alternate boot sector save file. See also sections 4.1.7 and 4.2.2. +
+-S save_file
 
Like -s, but overwrites old save files. +
+-t
 
Test only. This performs the entire installation procedure except replacing the map file, writing + the modified boot sector and fixing partition tables. This can be used in conjunction with the + -v option to verify that LILO will use sane values. +
+-v
 
Increase verbosity. See also sections 4.1.7 and 4.2.2.
+

+

+
4.1.3 Change default command line
+

Changes LILO’s default command line. See also section 3.2. +

+

/sbin/lilo [ -C config_file ] [ -m map_file ] -R [ word ]   +

+

+-C config_file
 
Specifies an alternate configuration file. See also section 4.1.1. + +
+-m map_file
 
Specifies an alternate map file. See also sections 4.1.7 and 4.2.2. +
+-R word
 
Stores the specified words in the map file. The boot loader uses those words as the default + command line when booting the next time. That command line is removed from the map file by + the boot loader by overwriting the sector immediately after reading it. The first word has to be + the name of a boot image. If -R is not followed by any words, the current default command line in + the map file is erased.21 + If the command line isn’t valid, the map installer issues an error message and returns a non-zero + exit code.
+

+

+
4.1.4 Kernel name translation
+

Determines the path of the kernel. +

/sbin/lilo [ -C config_file ] -I name [ options ]   +

+

+-C config_file
 
Specifies an alternate configuration file. See also section 4.1.1. +
+-I name [ options ]
 
Translates the specified label name to the path of the corresponding kernel image and prints that + path on standard output. This can be used to synchronize files that depend on the kernel (e.g. + the ps database). The image name can be obtained from the environment variable BOOT_IMAGE. + An error message is issued and a non-zero exit code is returned if no matching label name can + be found. The existence of the image file is verified if the option character v is added.
+

+

+
4.1.5 De-installation
+

Restores the boot sector that was used before the installation of LILO. Note that this option only works +properly if LILO’s directories (e.g. /boot) have not been touched since the first installation. See also section + +5.3. +

/sbin/lilo [ -C config_file ] [ -s save_file ] -u | -U [ boot_device ]   +

+

+-C config_file
 
Specifies an alternate configuration file. See also section 4.1.1. +
+-s save_file
 
Specifies an alternate boot sector save file. See also sections 4.1.7 and 4.2.2. +
+-u [ device_name ]
 
Restores the backup copy of the specified boot sector. If no device is specified, the value of the + boot variable is used. If this one is also unavailable, LILO uses the current root device. The + name of the backup copy is derived from the device name. The -s option or the backup variable + can be used to override this. LILO validates the backup copy by checking a time stamp. +
+-U [ device_name ]
 
Like -u, but does not check the time stamp.
+

+

+
4.1.6 Print version number
+

/sbin/lilo -V   +

+

+-V
 
Print the version number and exit.
+

+

+
4.1.7 Options corresponding to configuration variables
+

There are also many command-line options that correspond to configuration variables. See section 4.2.2 for +a description. +

+ +

+
+                      |
+-Command----line option|Con-figuration-variable-----
+ -b  bootxdevice       |boot=bootxdevice
+ -c                   |compact
+ -d  tsecs             |delay=tsecs
+                      |
+ -D  name             |default=name
+ -i  bootxsector        |install=bootxsector
+ -L                   |lba32
+ -l                   |linear
+ -m  mapxfile          |map=mapx  file
+ -P  fix              |fix -table
+ -P  ignore           |ignore -table
+                      |
+ -s  backupx file        |backup=backupx file
+ -S  backupx file        |force -backup=backupx file
+ -v  ...               |verbose=level
+
+

+

+

4.2 Configuration

+

The configuration information is stored in the file /etc/lilo.conf and consists of variable +assignments. +

+

+
4.2.1 Syntax
+

The following syntax rules apply: +

+
    +
  • flag variables consist of a single word and are followed by whitespace or the end of the file. +
  • +
  • string variables consist of the variable name, optional whitespace, an equal sign, optional + whitespace, the value and required whitespace, or the end of the file. + +
  • +
  • a non-empty sequence of blanks, tabs, newlines and comments counts as whitespace. +
  • +
  • variable names are case-insensitive. Values are usually case-sensitive, but there are a few + exceptions. (See below.) +
  • +
  • tabs and newlines are special characters and may not be part of a variable name or a value. + The use of other control characters and non-ASCII characters is discouraged. +
  • +
  • blanks and equal signs may only be part of a variable name or a value if they are escaped by + a backslash or if the value is embedded in double quotes. An equal sign may not be the only + character in a name or value. +
  • +
  • an escaped tab is converted to an escaped blank. An escaped newline is removed from the input + stream. An escaped backslash (i.e. two backslashes) is converted to a backslash. Inside quoted + strings, only double quotes, backslashes, dollar signs, and newlines can be escaped. +
  • +
  • quoted strings can be continued over several lines by ending each incomplete line with a + backslash. A single space is inserted in the string for the line end and all spaces or tabs that + follow immediately on the next line. +
  • +
  • environment variables can be used by specifying them in the form $name or ${name}. Dollar + signs can be escaped. +
  • +
  • comments begin with a number sign and end with the next newline. All characters (including + backslashes) until the newline are ignored.
+

Example: + +

+
+boot = $FD + 
install = $MNT/boot.b + 
map = $MNT/map + 
compact + 
read-only + 
append = "nfsroot=/home/linux-install/root \ + 
  nfsaddrs=128.178.156.28:128.178.156.24::255.255.255.0:lrcinst" + 
image = $MNT/zImage
+

+

+

+
4.2.2 Global options
+

/etc/lilo.conf begins with a possibly empty global options section. Many global options can also be +set from the command line, but storing permanent options in the configuration file is more +convenient. +

The following global options are recognized: +

+

+backup=backup_file
Copy the original boot sector to backup_file (which may also be a device, e.g. + /dev/null) instead of /boot/boot.number +
+boot=boot_device
Sets the name of the device (e.g. a hard disk partition) that contains the boot + sector. If boot is omitted, the boot sector is read from (and possibly written to) the device that + is currently mounted as root. +
+change-rules
Defines partition type numbers. See section 4.5.2 for details. +
+compact
Tries to merge read requests for adjacent sectors into a single read request. This drastically + reduces load time and keeps the map smaller. Using compact is especially recommended when + booting from a floppy disk. compact may conflict with linear or lba32, see section 6.3. +
+default=name
Uses the specified image as the default boot image. If default is omitted, the image + appearing first in the configuration file is used. +
+delay=tsecs
Specifies the number of tenths of a second LILO should wait before booting the first + + image. This is useful on systems that immediately boot from the hard disk after enabling the + keyboard. LILO doesn’t wait if delay is omitted or if delay is set to zero. +
+disk=device_name
Defines non-standard parameters for the specified disk. See section 4.4 for details. +
+fix-table
Allows LILO to adjust 3D addresses in partition tables. Each partition entry contains + a 3D (sector/head/cylinder) and a linear 32-bit address of the first and the last sector of + the partition. If a partition is not track-aligned and if certain other operating systems (e.g. + PC/MS-DOS or OS/2) are using the same disk, they may change the 3D address. LILO can + store its boot sector only on partitions where both address types correspond. LILO re-adjusts + incorrect 3D start addresses if fix-table is set. +

WARNING: This does not guarantee that other operating systems may not attempt to reset + the address later. It is also possible that this change has other, unexpected side-effects. The + correct fix is to re-partition the drive with a program that does align partitions to tracks. Also, + with some disks (e.g. some large EIDE disks with address translation enabled), under some + circumstances, it may even be unavoidable to have conflicting partition table entries. +

+force-backup=backup_file
Like backup, but overwrite an old backup copy if it exists.
backup=backup_file is ignored if force-backup appears in the same configuration file. +
+ignore-table
Tells LILO to ignore corrupt partition tables and to put the boot sector even on + partitions that appear to be unsuitable for that. +
+install=boot_sector
Install the specified file as the new boot sector. If install is omitted,
/boot/boot.b is used as the default. +
+keytable=table_file
Re-map the keyboard as specified in this file. See section 4.6 for details. +
+lba32
Generate 32-bit Logical Block Addresses instead of sector/head/cylinder addresses. If the + BIOS supports packet addressing, then packet calls will be used to access the disk. This allows + booting from any partition on disks with more than 1024 cylinders. If the BIOS does not + support packet addressing, then lba32 addresses are translated to C:H:S, just as for linear. + All floppy disk references are retained in C:H:S form. Use of lba32 is recommended on all + post-1998 systems. lba32 may conflict with compact, see section 6.3. +
+linear
Generate linear sector addresses instead of sector/head/cylinder addresses. Linear addresses + are translated at run time and do not depend on disk geometry. Note that boot disks may + not be portable if linear is used, because the BIOS service to determine the disk geometry + does not work reliably for floppy disks. When using linear with large disks, /sbin/lilo may + generate references to inaccessible disk areas (see section 2.3.1), because 3D sector addresses + are not known before boot time. linear may conflict with compact, see section 6.3. +
+map=map_file
Specifies the location of the map file. If map is omitted, a file /boot/map is used. +
+ +message=message_file
Specifies a file containing a message that is displayed before the boot prompt. + No message is displayed while waiting for a modifier key ([Shift], etc.) after printing “LILO ”. + In the message, the FF character ([Ctrl L]) clears the local screen. The size of the message file + is limited to 65535 bytes. The map file has to be rebuilt if the message file is changed or moved. +
+nowarn
Disables warnings about possible future dangers. +
+prompt
Forces entering the boot prompt without expecting any prior key-presses. Unattended + reboots are impossible if prompt is set and timeout isn’t. +
+serial=parameters
Enables control from a serial line. The specified serial port is initialized and LILO is + accepting input from it and from the PC’s keyboard. Sending a break on the serial line corresponds + to pressing a shift key on the console in order to get LILO’s attention. All boot images + should be password-protected if the serial access is less secure than access to the console, + e.g. if the line is connected to a modem. The parameter string has the following syntax: +
port,bps parity bits
The components bps, parity and bits can be omitted. If a component is omitted, all following + components have to be omitted too. Additionally, the comma has to be omitted if only the port + number is specified. +
+ port
the number of the serial port, zero-based. 0 corresponds to COM1 alias /dev/ttyS0, etc. + All four ports can be used (if present). +
+ bps
the baud rate of the serial port. The following baud rates are supported: 110, 300, 1200, + 2400, 4800, 9600, 19200, and 38400 bps. Default is 2400 bps. +
+ parity
the parity used on the serial line. LILO ignores input parity and strips the 8th bit. The + following (upper or lower case) characters are used to describe the parity: n for no parity, + e for even parity and o for odd parity. +
+ bits
the number of bits in a character. Only 7 and 8 bits are supported. Default is 8 if parity + is “none”, 7 if parity is “even” or “odd”.
+

If serial is set, the value of delay is automatically raised to 20. +

Example: serial=0,2400n8 initializes COM1 with the default parameters. +

+timeout=tsecs
Sets a timeout (in tenths of a second) for keyboard input. If no key is pressed for the + specified time, the first image is automatically booted. Similarly, password input is aborted if the user + is idle for too long. The default timeout is infinite. +
+verbose=level
Turns on lots of progress reporting. Higher numbers give more verbose output. If -v is + additionally specified on the command line, level is increased accordingly. The following verbosity + levels exist: + +
+ <0
only warnings and errors are shown +
+ 0
prints one line for each added or skipped image +
+ 1
mentions names of important files and devices and why they are accessed. Also displays + informational messages for exceptional but harmless conditions and prints the version + number. +
+ 2
displays statistics and processing of temporary files and devices +
+ 3
displays disk geometry information and partition table change rules +
+ 4
lists sector mappings as they are written into the map file (i.e. after compaction, in a format + suitable to pass it to the BIOS) +
+ 5
lists the mapping of each sector (i.e. before compaction, raw)
+

When using the -q option, the levels have a slightly different meaning: +

+ 0
displays only image names +
+ 1
also displays all global and per-image settings +
+ 2
displays the address of the first map sector
+
+

Additionally, the kernel configuration parameters append, initrd, ramdisk, read-only, read-write, root +and vga, and the general per-image options fallback, lock, optional, password, restricted, and +single-key can be set in the global options section. They are used as defaults if they aren’t specified in the +configuration sections of the respective images. See below for a description. +

The plethora of options may be intimidating at first, but in “normal” configurations, hardly any options but +boot, compact, delay, root, and vga are used. +

+

+
4.2.3 General per-image options
+

The following options can be specified for all images, independent of their type: +

+alias=name
Specifies a second name for the current entry. + +
+fallback=command_line
Specifies a string that is stored as the default command line if the current + image is booted. This is useful when experimenting with kernels which may crash before allowing + interaction with the system. If using the fallback option, the next reboot (e.g. triggered + by a manual reset or by a watchdog timer) will load a different (supposedly stable) kernel. + The command line by the fallback mechanism is cleared by removing or changing the default + command line with the -R option, see 4.1.3. +
+label=name
By default, LILO uses the main file name (without its path) of each image specification + to identify that image. A different name can be used by setting the variable label. +
+lock
Enables automatic recording of boot command lines as the defaults for the following boots. + This way, LILO “locks” on a choice until it is manually overridden. +
+optional
Omit this image if its main file is not available at map creation time. This is useful to + specify test kernels that are not always present. +
+password=password
Ask the user for a password when trying to load this image. Because the + configuration file contains unencrypted passwords when using this option, it should only be + readable for the super-user. Passwords are always case-sensitive. +
+restricted
Relaxes the password protection by requiring a password only if parameters are specified + on the command line (e.g. single). restricted can only be used together with password. +
+single-key
Enables booting the image by hitting a single key, without the need to press [Enter] + afterwards. single-key requires that either the image’s label or its alias (or both) is a single + character. Furthermore, no other image label or alias may start with that character, e.g. an + entry specifying a label linux and an alias l is not allowed with single-key. Note that you + can’t specify command-line parameters for an entry for which only single-keyed names exist.
+

All general per-image options, with the exception of label and alias, can also be set in the global options +section as defaults for all images. +

Example: + +

+
+password = Geheim + 
single-key + 
image = /vmlinuz + 
  label = linux + 
  alias = 1 + 
  restricted + 
other = /dev/hda1 + 
  label = dos + 
  alias = 2
+

+

+

+
4.2.4 Per-image options for kernels
+

Each (kernel or non-kernel) image description begins with a special variable (see section 4.3) which is +followed by optional variables. The following variables can be used for all image descriptions that describe a +Linux kernel: +

+

+append=string
Appends the options specified in string to the parameter line passed to the kernel. + This is typically used to specify parameters of hardware that can’t be entirely auto-detected, + e.g.
append = "aha152x=0x140,11" +
+initrd=name
Specifies the file that will be loaded at boot time as the initial RAM disk. +
+literal=string
like append, but removes all other options (e.g. setting of the root device). Because + vital options can be removed unintentionally with literal, this option cannot be set in the + global options section. +
+ramdisk=size
Specifies the size of the optional RAM disk. A value of zero indicates that no RAM + disk should be created. If this variable is omitted, the RAM disk size configured into the boot + image is used. +
+read-only
Specifies that the root file system should be mounted read-only. Typically, the system + startup procedure re-mounts the root file system read-write later (e.g. after fsck’ing it). + +
+read-write
specifies that the root file system should be mounted read-write. +
+root=root_device
Specifies the device that should be mounted as root. If the special name current + is used, the root device is set to the device on which the root file system is currently mounted. + If the root has been changed with -r, the respective device is used. If the variable root is + omitted, the root device setting contained in the kernel image is used. It can be changed with + the rdev program. +
+vga=mode
Specifies the VGA text mode that should be selected when booting. The following values are + recognized (case is ignored): +
+ normal
select normal 80x25 text mode. +
+ extended
select 80x50 text mode. The word extended can be abbreviated to ext. +
+ ask
stop and ask for user input (at boot time). +
+ number
use the corresponding text mode. A list of available modes can be obtained by booting + with vga=ask and pressing [Enter].
+

If this variable is omitted, the VGA mode setting contained in the kernel image is used. rdev supports + manipulation of the VGA text mode setting in the kernel image.

+

All kernel per-image options but literal can also be set in the global options section as defaults for all +kernels. +

If one of ramdisk, read-only, read-write, root, or vga is omitted in the configuration file and +the corresponding value in the kernel image is changed, LILO or the kernel will use the new +value. +

It is perfectly valid to use different settings for the same image, because LILO stores them in the image +descriptors and not in the images themselves. +

Example: + +

+
+image = /vmlinuz + 
  label = lin-hd + 
  root = /dev/hda2 + 
image = /vmlinuz + 
  label = lin-fd + 
  root = /dev/fd0
+

+

+

+

4.3 Boot image types

+

LILO can boot the following types of images:

+
    +
  • kernel images from a file. +
  • +
  • kernel images from a block device. (E.g. a floppy disk.) +
  • +
  • the boot sector of some other operating system.
+

The image type is determined by the name of the initial variable of the configuration section. +

The image files can reside on any media that is accessible at boot time. There’s no need to put them on the +root device, although this certainly doesn’t hurt. +

+

+
4.3.1 Booting kernel images from a file
+

The image is specified as follows: image=name +

Example: + +

+
+image = /linux
+

+

See sections 4.2.3 and 4.2.4 for the options that can be added in a kernel image section. +

+

+
4.3.2 Booting kernel images from a device
+

The range of sectors that should be mapped has to be specified. Either a range (start-end) or a start and a +distance (start+number) have to be specified. start and end are zero-based. If only the start is specified, +only that sector is mapped. +

The image is specified as follows: image=device_name Additionally, the range variable must be +set. +

Example: + +

+
+image = /dev/fd0 + 
  range = 1+512
+

+

All kernel options can also be used when booting the kernel from a device. +

+

+
4.3.3 Booting a foreign operating system
+

LILO can even boot other operating systems, i.e. MS-DOS. To boot an other operating system, the name of +a loader program, the device or file that contains the boot sector and the device that contains the partition +table have to be specified. +

The boot sector is merged with the partition table and stored in the map file. +

Currently, the loaders chain.b and os2_d.b exist. chain.b simply starts the specified boot +sector.22 +os2_d.b it a variant of chain.b that can boot OS/2 from the second hard disk. The map-drive option has +to be used with os2_d.b to actually swap the drives. +

The image is specified as follows: other=device_name or other=file_name +

In addition to the options listen in section 4.2.3, the following variables are recognized: +

+change
Change the partition table according to the rules specified in this change section. This option + is intended for booting systems which find their partitions by examining the partition table. + See section 4.5.3 for details. +
+loader=chain_loader
Specifies the chain loader that should be used. If it is omitted, /boot/chain.b + is used. +
+map-drive=bios_device_code
Instructs chain.b to installs a resident driver that re-maps the floppy + or hard disk drives. This way, one can boot any operating system from a hard disk different + from the first one, as long as that operating system uses only the BIOS to access that hard + + disk.23 + This is known to work for PC/MS-DOS. +

map-drive is followed by the variable to=bios_device_code which specifies the drive that should + effectively be accessed instead of the original one. The list of mappings is only searched until + the first match is found. It is therefore possible to “swap” drives, see the second example below. +

+table=device
Specifies the device that contains the partition table. LILO does not pass partition + information to the booted operating system if this variable is omitted. (Some operating systems + have other means to determine from which partition they have been booted. E.g. MS-DOS + usually stores the geometry of the boot disk or partition in its boot sector.) Note that + /sbin/lilo must be re-run if a partition table mapped referenced with table is modified. +
+unsafe
Do not access the boot sector at map creation time. This disables some sanity checks, + including a partition table check. If the boot sector is on a fixed-format floppy disk device, using + unsafe avoids the need to put a readable disk into the drive when running the map installer. + unsafe and table are mutually incompatible.
+

None of these options can be set in the global options section. +

Examples: + +

+
+other = /dev/hda2 + 
  label = dos + 
  table = /dev/hda
+

+ +

+
+other = /dev/hdb2 + 
  label = os2 + 
  loader = /boot/os2_d.b + 
  map-drive = 0x80 + 
    to = 0x81 + 
  map-drive = 0x81 + 
    to = 0x80
+

+

+

4.4 Disk geometry

+

For floppies and most hard disks, LILO can obtain the disk geometry information from the kernel. +Unfortunately, there are some exotic disks or adapters which may either not supply this information or +which may even return incorrect information. +

If no geometry information is available, LILO reports either the error
geo_query_dev HDIO_GETGEO (dev 0xnumber)
or
Device 0xnumber: Got bad geometry sec/hd/cyl +

If incorrect information is returned, booting may fail in several ways, typically with a partial “LILO” +banner message. In this document, that is called a “geometry mismatch”. +

The next step should be to attempt setting the lba32 or linear configuration variable or the -L or -l +command-line option. If this doesn’t help, the entire disk geometry has to be specified explicitly. Note that +linear doesn’t always work with floppy disks. +

Another common use of disk sections is if an (E)IDE and a SCSI drive are used in the same system and the +BIOS is configured to use the SCSI drive as the first drive. (Normally, the (E)IDE drive would be the first +drive and the SCSI drive would be the second one.) Since LILO doesn’t know how the BIOS +is configured, it needs to be told explicitly about this arrangement. (See the second example +below.) +

+

+
4.4.1 Obtaining the geometry
+

The disk geometry parameters can be obtained by booting MS-DOS and running the program DPARAM.COM +with the hexadecimal BIOS code of the drive as its argument, e.g. dparam 0x80 for the first hard disk. It +displays the number of sectors per track, the number of heads per cylinder and the number of cylinders. All +three numbers are one-based. + +

Alternatively, the geometry may also be determined by reading the information presented by the “setup” +section of the ROM-BIOS or by using certain disk utilities under operating systems accessing the disk +through the BIOS. +

+

+
4.4.2 Specifying the geometry
+

Disk geometry parameters are specified in the options section of the configuration file. Each disk parameter +section begins with disk=disk_device, similar to the way how boot images are specified. It is suggested to +group disk parameter sections together, preferably at the beginning or the end of the options +section. +

For each disk, the following variables can be specified: +

+bios=bios_device_code
Is the number the BIOS uses to refer to that device. Normally, it’s 0x80 for + the first hard disk and 0x81 for the second hard disk. Note that hexadecimal numbers have to + begin with “0x”. If bios is omitted, LILO tries to “guess” that number. +
+sectors=sectors
and +
+heads=heads
specify the number of sectors per track and the number of heads, i.e. the number of + tracks per cylinder. Both parameters have to be either specified together or they have to be + entirely omitted. If omitted, LILO tries to obtain that geometry information from the kernel. +
+cylinders=cylinders
Specifies the number of cylinders. This value is only used for sanity checks. + If cylinders is omitted, LILO uses the information obtained from the kernel if geometry + information had to be requested in order to determine some other parameter. Otherwise,24 + it just assumes the number of cylinders to be 1024, which is the cylinder limit imposed by the + BIOS. +
+inaccessible
Marks the device as inaccessible (for the BIOS). This is useful if some disks on + the system can’t be read by the BIOS, although LILO “thinks” they can. If one accidentally + tries to use files located on such disks for booting, the map installer won’t notice and the + system becomes unbootable. The most likely use of inaccessible is to prevent repetition after + experiencing such a situation once. No other variables may be specified if a device is configured + as inaccessible.
+

Additionally, partition subsections can be added with partition=partition_device. Each partition section +can contain only one variable: +

+start=partition_offset
Specifies the zero-based number of the start sector of that partition. The + + whole disk always has a partition offset of zero. The partition offset is only necessary when + using devices for which the kernel does not provide that information, e.g. CD-ROMs.
+

Examples: + +

+
+disk = /dev/sda + 
  bios = 0x80 + 
  sectors = 32 + 
  heads = 64 + 
  cylinders = 632 + 
  partition = /dev/sda1 + 
    start = 2048 + 
  partition = /dev/sda2 + 
    start = 204800 + 
  partition = /dev/sda3 + 
    start = 500000 + 
  partition = /dev/sda4 + 
    start = 900000
+

+ +

+
+disk = /dev/sda + 
  bios = 0x80 + 
disk = /dev/hda + 
  bios = 0x81
+

+

+

+

4.5 Partition table manipulation

+

Some non-Linux operating systems obtain information about their partitions (e.g. their equivalent of the +root file system) from the partition table. If more than one such operating system is installed on a PC, +they may have conflicting interpretations of the content of the partition table. Those problems +can be avoided by changing the partition table, depending on which operating system is being +booted. +

Partition table changes are specified in a change section in the configuration file section describing the +foreign operating system. Note that change sections are only accepted if the build-time option +REWRITE_TABLE is set. +

The change section contains subsections for each partition whose table entry needs to be modified. +Partitions are specified with partition=device_name +

Changes are applied in the sequence in which they appear in the configuration file. Configurations +containing changes that are redundant either by repeating a previous change or by changing its result +further are invalid and refused by the map installer. +

Internally, all changes are expressed as rules which specify the location (disk and offset in the +partition table), the value this location must contain before the change, and the value that +has to be stored. As a safety measure, the rule is ignored if the previous value is found to be +different. +

+

+
4.5.1 Partition activation
+

This option is intended for booting systems which determine their boot partition by examining the active +flag in the partition table. The flag is enabled with activate and disabled with deactivate. +Note that only the current partition is affected. LILO does not automatically change the active +flags of other partitions and it also allows more than one partition to be active at the same +time. + +

Example: + +

+
+other = /dev/sda4 + 
  label = sco + 
  change + 
    partition = /dev/sda4 + 
      activate + 
    partition = /dev/sda3 + 
      deactivate
+

+

+

+
4.5.2 Partition type change rules
+

Partition type changes are normally a transition between two possible values, e.g. a typical convention is to +set the lowest bit in the upper nibble of the partition type (i.e. 0x10) in order to “hide”, and to clear it to +“unhide” a partition. LILO performs these changes based on a set of rules. Each rule defines +the name of a partition type, its normal value, and the value when hidden. Those rules are +defined in the options section of the configuration file. The section defining them begins with +change-rules. +

The following options and variables can appear in the section: +

+reset
Removes all previously defined rules. This is needed if a user doesn’t wish to use the pre-defined + rules (see below). +
+type=name
Adds a rule for the type with the specified name. Type names are case-insensitive. The + values are defined with normal=byte and hidden=byte. Values can be specified as decimal or as + hexadecimal numbers with a leading 0x. If only one of the values is present, the other value is + assumed to be the same number, but with the most significant bit inverted.
+

LILO pre-defines rules for the three partition types of DOS partitions. The following example removes the +pre-defined rules and creates them again: + +

+
+change-rules + 
  reset + 
  type = DOS12 + 
    normal = 0x01 + 
    hidden = 0x11 + 
  type = DOS16_small + 
    normal = 4 # hidden is 0x14 + 
  type = DOS16_big + 
    hidden = 0x16
+

+

+

+
4.5.3 Partition type changes
+

Partition type changes are specified in the partition section as set=name_state, where name is the name of +the partition type, and state is its state, i.e. normal or hidden. +

Example: + +

+
+other = /dev/sda3 + 
  label = dos + 
  change + 
    partition = /dev/sda2 + 
      set = dos16_big_normal + 
    partition = /dev/sda3 + 
      activate + 
      set = DOS16_big_normal
+

+

Only one set variable is allowed per partition section. In the rare event that more than one set variable is +needed, further partition sections can be used. +

+

+

4.6 Keyboard translation

+

The PC keyboard emits so-called scan codes, which are basically key numbers. The BIOS then translates +those scan codes to the character codes of the characters printed on the key-caps. By default, the BIOS +normally assumes that the keyboard has a US layout. Once an operating system is loaded, this operating +system can use a different mapping. +

At boot time, LILO only has access to the basic services provided by the BIOS and therefore receives the character +codes for an US keyboard. It provides a simple mechanism to re-map the character codes to what is appropriate for the +actual layout.25 +

+
4.6.1 Compiling keyboard translation tables
+

LILO obtains layout information from the keyboard translation tables Linux uses for the text +console. They are usually stored in /usr/lib/kbd/keytables. LILO comes with a program +keytab-lilo.pl that reads those tables and generates a table suitable for use by the map installer. +keytab-lilo.pl invokes the program loadkeys to print the tables in a format that is easy to parse. +26 + +

keytab-lilo.pl is used as follows: +

keytab-lilo.pl [ -p old_code=new_code ] [path]default_layout[.extension]
        [path]kbd_layout[.extension]   +

+-p old_code=new_code
 
Specifies corrections (“patches”) to the mapping obtained from the translation table files. E.g. + if pressing the upper case “A” should yield an at sign, -p 65=64 would be used. The -p option + can be repeated any number of times. The codes can also be given as hexadecimal or as octal + numbers if they are prefixed with 0x or 0, respectively. +
+path
The directory in which the file resides. The default path is /usr/lib/kbd/keytables. +
+extension
Usually the trailing .map, which is automatically added if the file name doesn’t contain dots. +
+default_layout
Is the layout which specifies the translation by the BIOS. If none is specified, us is assumed. +
+kbd_layout
Is the actual layout of the keyboard.
+

keytab-lilo.pl writes the resulting translation table as a binary string to standard output. Such tables can be +stored anywhere with any name, but the suggested naming convention is /boot/kbd.ktl (“Keyboard Table +for Lilo”), where kbd is the name of the keyboard layout. +

Example: + +

+
+keytab-lilo.pl de >/boot/de.ktl
+

+

+
4.6.2 Using keyboard translation tables
+

The keyboard translation table file is specified with the global configuration option keytable=table_file. The +complete name of the file has to be given. +

Example: + +

+
+keytable = /boot/de.klt
+

+

+ +

+

5 Installation and updates

+

+

+

5.1 Installation

+

This section describes the installation of LILO. See section 5.3 for how to uninstall LILO. +

+

+
5.1.1 Compatibility
+

The kernel header files have to be in /usr/include/linux and the kernel usually has to be configured by +running make config before LILO can be compiled. +

/bin/sh has to be a real Bourne shell. bash is sufficiently compatible, but some ksh clones may cause +problems. +

A file named INCOMPAT is included in the distribution. It describes incompatibilities to older versions of +LILO and may also contain further compatibility notes. +

+

+
5.1.2 Quick installation
+

If you want to install LILO on your hard disk and if you don’t want to use all its features, you can use the +quick installation script. Read QuickInst for details. +

QuickInst can only be used for first-time installations or to entirely replace an existing installation, not to +update or modify an existing installation of LILO. Be sure you’ve extracted LILO into a directory that +doesn’t contain any files of other LILO installations. +

+

+
5.1.3 Files
+

Some of the files contained in lilo-21.tar.gz: +

+ +

+lilo/README
 
This documentation in plain ASCII format. Some sections containing complex tables are only + included in the LATEX version in doc/user.tex +
+lilo/INCOMPAT
 
List of incompatibilities to previous versions of LILO. +
+lilo/CHANGES
 
Change history. +
+lilo/VERSION
 
The version number of the respective release. +
+lilo/QuickInst
 
Quick installation script. +
+lilo/lilo-version.lsm
 
The LSM (“Linux Software Map”) entry of the respective LILO release. +
+lilo/Makefile
 
Makefile to generate everything else. +
+lilo/*.c, lilo/*.h
 
LILO map installer C source and common header files. +
+lilo/*.S
 
LILO boot loader assembler source. +
+lilo/activate.c
 
C source of a simple boot partition setter. +
+lilo/dparam.s
 
Assembler source of a disk parameter dumper. +
+lilo/mkdist
 
Shell script used to create the current LILO distribution. +
+lilo/keytab-lilo.pl
 
Perl script to generate keyboard translation tables. +
+lilo/doc/README
 
Description of how to generate the documentation. + +
+lilo/doc/Makefile
 
Makefile used to convert the LATEX source into either DVI output or the plain ASCII + README file. +
+lilo/doc/user.tex
 
LATEX source of LILO’s user’s guide (this document). +
+lilo/doc/tech.tex
 
LATEX source of LILO’s technical overview. +
+lilo/doc/*.fig
 
Various xfig pictures used in the technical overview. +
+lilo/doc/fullpage.sty
 
Style file to save a few square miles of forest. +
+lilo/doc/rlatex
 
Shell script that invokes LATEX repeatedly until all references have settled. +
+lilo/doc/t2a.pl
 
Perl script to convert the LATEX source of the user’s guide to plain ASCII.
+

Files created after make in lilo/ (among others): +

+

+lilo/boot.b
 
Combined boot sector. make install puts this file into /boot +
+lilo/chain.b
 
Generic chain loader. make install puts this file into /boot +
+lilo/os2_d.b
 
Chain loader to load OS/2 from the second hard disk. make install puts this file into /boot +
+lilo/lilo
 
LILO (map) installer. make install puts this file into /sbin +
+lilo/activate
 
Simple boot partition setter. +
+lilo/dparam.com
 
MS-DOS executable of the disk parameter dumper.
+ +

+

+
5.1.4 Normal first-time installation
+

First, you have to install the LILO files: +

+
    +
  • extract all files from lilo-version.tar.gz in a new directory.27 +
  • +
  • configure the Makefile (see section 5.1.5) +
  • +
  • run make to compile and assemble all parts. +
  • +
  • run make install to copy all LILO files to the directories where they’re installed. /sbin + should now contain the file lilo, /usr/sbin should contain keytab-lilo.pl, and /boot should + contain boot.b, chain.b, and os2_d.b.
+

If you want to use LILO on a non-standard disk, you might have to determine the parameters of your +disk(s) and specify them in the configuration file. See section 4.4 for details. If you’re using +such a non-standard system, the next step is to test LILO with the boot sector on a floppy +disk: +

+
    +
  • insert a blank (but low-level formatted) floppy disk into /dev/fd0. +
  • +
  • run echo image=kernel_image |
    /sbin/lilo -C - -b /dev/fd0 -v -v -v
    If you’ve already installed LILO on your system, you might not want to overwrite your old + map file. Use the -m option to specify an alternate map file name. +
  • +
  • reboot. LILO should now load its boot loaders from the floppy disk and then continue loading + the kernel from the hard disk.
+

Now, you have to decide, which boot concept you want to use. Let’s assume you have a Linux partition on +/dev/hda2 and you want to install your LILO boot sector there. The DOS-MBR loads the LILO boot +sector. +

+ +
    +
  • get a working boot disk, e.g. an install or recovery disk. Verify that you can boot with this + setup and that you can mount your Linux partition(s) with it. +
  • +
  • if the boot sector you want to overwrite with LILO is of any value (e.g. it’s the MBR or if + it contains a boot loader you might want to use if you encounter problems with LILO), you + should mount your boot disk and make a backup copy of your boot sector to a file on that + floppy, e.g. dd if=/dev/hda of=/fd/boot_sector bs=512 count=1 +
  • +
  • create the configuration file /etc/lilo.conf, e.g.
    global settings
    image specification
      per-image options

    Be sure to use absolute paths for all files. Relative paths may cause unexpected behaviour when + using the -r option. +
  • +
  • now, you can check what LILO would do if you were about to install it on your hard disk:
    /sbin/lilo -v -v -v -t +
  • +
  • if you need some additional boot utility (i.e. BOOTACTV), you should install that now +
  • +
  • run /sbin/lilo to install LILO on your hard disk +
  • +
  • if you have to change the active partition, use fdisk or activate to do that +
  • +
  • reboot
+

+

+
5.1.5 Build-time configuration
+

Certain build-time parameters can be configured. They can either be edited in the top-level Makefile or +they can be stored in a file /etc/lilo.defines. Settings in the Makefile are ignored if that file +exists. +

The following items can be configured: +

+BEEP
Enables beeping after displaying “LILO”. This is useful on machines which don’t beep at the + right time when booting and when working over a serial console. This option is disabled by + default. +
+IGNORECASE
Makes image name matching case-insensitive, i.e. “linux” and “Linux” are identical. + + This option is enabled by default. Note that password matching is always case-sensitive. +
+LARGE_EDBA
Loads LILO at a lower address in order to leave more space for the EBDA (Extended + BIOS Data Area). This is necessary on some recent MP systems. Note that enabling LARGE_EDBA + reduces the maximum size of “small” images (e.g. “Image” or “zImage”). +
+NO1STDIAG
Do not generate diagnostics on read errors in the first stage boot loader. This avoids + possibly irritating error codes if the disk controller has transient read problems. This option is + disabled by default. +
+NODRAIN
The boot loader empties the keyboard buffer when starting, because it may contain garbage + on some systems. Draining the keyboard buffer can be disabled by setting the NODRAIN option. + NODRAIN is disabled by default. +
+NOINSTDEF
If the option install is omitted, don’t install a new boot sector, but try to modify the + old boot sector instead. This option is disabled by default. +
+ONE_SHOT
Disables the command-line timeout (configuration variable timeout) if any key is pressed. + This way, very short timeouts can be used if prompt is set. ONE_SHOT is disabled by default. +
+READONLY
Disallows overwriting the default command line sector of the map file. This way, command + lines set with -R stay in effect until they are explicitly removed. READONLY also disables lock, + fallback, and everything enabled by REWRITE_TABLE. This option is disabled by default. +
+REWRITE_TABLE
Enables rewriting the partition table at boot time. This may be necessary to boot + certain operating systems who expect the active flag to be set on their partition or who need + changes in partition types. See also section 4.5. This option is dangerous and it is disabled by + default. +
+USE_TMPDIR
Use the directory indicated in the TMPDIR environment variable when creating temporary + device files. If TMPDIR is not set or if LILO is compiled without USE_TMPDIR, temporary device + files are created in /tmp.28 + This option is disabled by default. +
+VARSETUP
Enables the use of variable-size setup segments. This option is enabled by default and is + only provided to fall back to fixed-size setup segments in the unlikely case of problems when + using prehistoric kernels. +
+XL_SECS=sectors
Enable support for extra large (non-standard) floppy disks. The number of sectors + is set in the BIOS disk parameter table to the specified value. Note that this hack may yield + incorrect behaviour on some systems. This option is disabled by default.
+ +

/etc/lilo.defines should be used if one wishes to make permanent configuration changes. The usual +installation procedures don’t touch that file. Example: + +

+
+-DIGNORECASE -DONE_SHOT
+

+

After changing the build-time configuration, LILO has to be recompiled with the following +commands: + +

+
+make spotless + 
make
+

+

+

+
5.1.6 Floppy disk installation
+

In some cases29, +it may be desirable to install LILO on a floppy disk in a way that it can boot a kernel without accessing the +hard disk. +

The basic procedure is quite straightforward (see also section 2.3.1):

+
    +
  • a file system has to be created on the file system +
  • +
  • the kernel and boot.b have to be copied to the floppy disk +
  • +
  • /sbin/lilo has to be run to create the map file
+

This can be as easy as + +

+
+/sbin/mke2fs /dev/fd0 + 
[ -d /fd ] || mkdir /fd + 
mount /dev/fd0 /fd + 
cp /boot/boot.b /fd + 
cp /zImage /fd + 
echo image=/fd/zImage label=linux | + 
  /sbin/lilo -C - -b /dev/fd0 -i /fd/boot.b -c -m /fd/map + 
umount /fd
+

+

The command line of /sbin/lilo is a little tricky. -C - takes the configuration from standard input +(naturally, one could also write the configuration into a file), -b /dev/fd0 specifies that the boot +sector is written to the floppy disk, -i /fd/boot.b takes the first and second stage loaders from +the floppy, -c speeds up the load process, and -m /fd/map puts the map file on the floppy +too. +

+

5.2 Updates

+

LILO is affected by updates of kernels, the whole system and (trivially) of LILO itself. Typically, only +/sbin/lilo has to be run after any of those updates and everything will be well again (at least as far as +LILO is concerned). +

+

+
5.2.1 LILO update
+

Before updating to a new version of LILO, you should read at least the file INCOMPAT which describes +incompatibilities with previous releases. +

After that, the initial steps are the same as for a first time installation: extract all files, configure the +Makefile, run make to build the executables and run make install to install the files. +

The old versions of boot.b, chain.b, etc. are automatically renamed to boot.old, chain.old, etc. This is +done to ensure that you can boot even if the installation procedure does not finish. boot.old, chain.old, +etc. can be deleted after the map file is rebuilt. +

Because the locations of boot.b, chain.b, etc. have changed and because the map file format may be +different too, you have to update the boot sector and the map file. Run /sbin/lilo to do +this. + +

+

+
5.2.2 Kernel update
+

Whenever any of the kernel files that are accessed by LILO is moved or overwritten, the map has to be +re-built.30 +Run /sbin/lilo to do this. +

The kernel has a make target “zlilo” that copies the kernel to /vmlinuz and runs /sbin/lilo. +

+
5.2.3 System upgrade
+

Normally, system upgrades (i.e. installation or removal of packages, possibly replacement of a large part of +the installed binaries) do not affect LILO. Of course, if a new kernel is installed in the process, the normal +kernel update procedure has to be followed (see section 5.2.2). Also, if kernels are removed or added, it may +be necessary to update the configuration file. +

If LILO is updated by this system upgrade, /sbin/lilo should be run before booting the upgraded system. +It is generally a good idea not to rely on the upgrade procedure to perform this essential step +automatically. +

However, system upgrades which involve removal and re-creation of entire partitions (e.g. /, /usr, etc.) are +different. First, they should be avoided, because they bear a high risk of losing other critical files, e.g. the +/etc/XF86Config you’ve spent the last week fiddling with. If an upgrade really has to be performed in such +a brute-force way, this is equal with total removal of LILO, followed by a new installation. Therefore, the +procedures described in the sections 5.3 and 5.2.1 have to be performed. If you’ve forgotten to make a +backup copy of /etc/lilo.conf before the destructive upgrade, you might also have to go through section +5.1.4 again. +

+

+

5.3 LILO de-installation

+

In order to stop LILO from being invoked when the system boots, its boot sector has to be either removed +or disabled. All other files belonging to LILO can be deleted after removing the boot sector, if + +desired.31 +

Again, when removing Linux, LILO must be de-installed before (!) its files (/boot, etc.) are +deleted. This is especially important if LILO is operating as the MBR. +

LILO 14 (and newer) can be de-installed with lilo -u. If LILO 14 or newer is currently installed, but the +first version of LILO installed was older than 14, lilo -U may work. When using -U, the warning at the +end of this section applies. +

If LILO’s boot sector has been installed on a primary partition and is booted by the “standard” MBR or +some partition switcher program, it can be disabled by making a different partition active. MS-DOS’ +FDISK, Linux fdisk or LILO’s activate can do that. +

If LILO’s boot sector is the master boot record (MBR) of a disk, it has to be replaced with a different +MBR, typically MS-DOS’ “standard” MBR. When using MS-DOS 5.0 or above, the MS-DOS +MBR can be restored with FDISK /MBR. This only alters the boot loader code, not the partition +table. +

LILO automatically makes backup copies when it overwrites boot sectors. They are named +
/boot/boot.nnnn, with nnnn corresponding to the device number, e.g. 0300 is /dev/hda, 0800 is +/dev/sda, etc. Those backups can be used to restore the old MBR if no easier method is available. The +commands are
dd if=/boot/boot.0300 of=/dev/hda bs=446 count=1 or
dd if=/boot/boot.0800 of=/dev/sda bs=446 count=1
respectively. +

WARNING: Some Linux distributions install boot.nnnn files from the system where the distribution was +created. Using those files may yield unpredictable results. Therefore, the file creation date should be +carefully checked. +

+

5.4 Installation of other operating systems

+

Some other operating systems (e.g. MS-DOS 6.0) appear to modify the MBR in their install procedures. It +is therefore possible that LILO will stop to work after such an installation and Linux has to be +booted from floppy disk. The original state can be restored by either re-running /sbin/lilo (if +LILO is installed as the MBR) or by making LILO’s partition active (if it’s installed on a primary +partition). +

It is generally a good idea to install LILO after the other operating systems have been installed. E.g. OS/2 +is said to cause trouble when attempting to add it to an existing Linux system. (However, booting from +floppy and running /sbin/lilo should get around most interferences.) +

Typically, the new operating system then has to be added to LILO’s configuration (and /sbin/lilo has to +be re-run) in order to boot it. + +

See also section 6.3 for a list of known problems with some other operating systems. +

+ +

+

6 Troubleshooting

+

All parts of LILO display some messages that can be used to diagnose problems. +

+

+

6.1 Map installer warnings and errors

+

Most messages of the map installer (/sbin/lilo) should be self-explanatory. Some messages that indicate +common errors are listed below. They are grouped into fatal errors and warnings (non-fatal +errors). +

+

+
6.1.1 Fatal errors
+

+

+Boot sector of device_name doesn’t have a boot signature
+
+Boot sector of device_name doesn’t have a LILO signature
 
The sector from which LILO should be uninstalled doesn’t appear to be a LILO boot sector. +
+Can’t put the boot sector on logical partition number
 
An attempt has been made to put LILO’s boot sector on the current root file system partition + which is on a logical partition. This usually doesn’t have the desired effect, because common + MBRs can only boot primary partitions. This check can be bypassed by explicitly specifying + the boot partition with the -b option or by setting the configuration variable boot. +
+Checksum error
 
The descriptor table of the map file has an invalid checksum. Refresh the map file immediately + ! +
+Device 0xnumber: Configured as inaccessible.
 
There is a disk section entry indicating that the device is inaccessible from the BIOS. You + should check carefully that all files LILO tries to access when booting are on the right device. +
+Device 0xnumber: Got bad geometry sec/hd/cyl
 
The device driver for your SCSI controller does not support geometry detection. You have to + specify the geometry explicitly (see section 4.4). + +
+Device 0xnumber: Invalid partition table, entry number
 
The 3D and linear addresses of the first sector of the specified partition don’t correspond. This + is typically caused by partitioning a disk with a program that doesn’t align partitions to tracks + and later using PC/MS-DOS or OS/2 on that disk. LILO can attempt to correct the problem, + see page §. +
+Device 0xnumber: Partition type 0xnumber
 
does not seem suitable for a LILO boot sector 
The location where the LILO boot sector should be placed does not seem to be suitable for + that. (See also also section 2.1). You should either adjust the partition type to reflect the actual + use or put the boot sector on a different partition. This consistency check only yields a warning + (i.e. LILO continues) if the option ignore-table is set. +
+device_name is not a valid partition device
 
The specified device is either not a device at all, a whole disk, or a partition on a different disk + than the one in whose section its entry appears. +
+device_name is not a whole disk device
 
Only the geometry of whole disks (e.g. /dev/hda, /dev/sdb, etc.) can be redefined when using + disk sections. +
+DISKTAB and DISK are mutually exclusive
 
You cannot use a disktab file and disk geometry definitions in the configuration file at + the same time. Maybe /etc/disktab was accidentally used, because that’s the default for + backward-compatibility. You should delete /etc/disktab after completing the transition to + disk sections. +
+Duplicate entry in partition table
 
A partition table entry appears twice. The partition table has to be fixed with fdisk. +
+Duplicate geometry definition for device_name
 
A disk or partition geometry definition entry for the same device appears twice in the + configuration file. Note that you mustn’t write a partition section for the whole disk — its start + sector is always the first sector of the disk. +
+First sector of device doesn’t have a valid boot signature
 
The first sector of the specified device does not appear to be a valid boot sector. You might have + confused the device name.32 +
+geo_comp_addr: Cylinder number beyond end of media (number)
 
A file block appears to be located beyond the last cylinder of the disk. This probably indicates + + an error in the disk geometry specification (see section 4.4) or a file system corruption. +
+geo_comp_addr: Cylinder number is too big (number > 1023)
 
Blocks of a file are located beyond the 1024th cylinder of a hard disk. LILO can’t access such + files, because the BIOS limits cylinder numbers to the range 01023. Try moving the file to a + different place, preferably a partition that is entirely within the first 1024 cylinders of the disk. +
+Hole found in map file (location)
 
The map installer is confused about the disk organization. Please report this error. +
+item doesn’t have a valid LILO signature
 
The specified item has been located, but is not part of LILO. +
+item has an invalid stage code (number)
 
The specified item has probably been corrupted. Try re-building LILO. +
+item is version number. Expecting versionnumber.
 
The specified entity is either too old or too new. Make sure all parts of LILO (map installer, + boot loaders and chain loaders) are from the same distribution. 33 +
+Kernel name is too big
 
The kernel image (without the setup code) is bigger than 512 kbytes (or 448 kbytes, if built with + LARGE_EDBA). LILO would overwrite itself when trying to load such a kernel. This limitation + only applies to old kernels which are loaded below 0x10000 (e.g. “Image” or “zImage”). Try + building the kernel with “bzImage”. If this is undesirable for some reason, try removing some + unused drivers and compiling the kernel again. This error may also occur if the kernel image is + damaged or if it contains trailing “junk”, e.g. as the result of copying an entire boot floppy to + the hard disk. +
+LOCK and FALLBACK are mutually exclusive
 
Since lock and fallback both change the default command line, they can’t be reasonably used + together. +
+Map path is not a regular file.
 
This is probably the result of an attempt to omit writing a map file, e.g. with -m /dev/null. + The -t option should be used to accomplish this. +
+Must specify SECTORS and HEADS together
 
It is assumed that disks with a “strange” number of sectors will also have a “strange” number + of heads. Therefore, it’s all or nothing. +
+No geometry variables allowed if INACCESSIBLE
 
If a device is configured as inaccessible (see section 4.4.2), its disk section must not contain + any geometry variables. +
+No image image is defined
 
The command line specified either with the -R option or with fallback does not contain the + name of a valid image. Note that optional images which have not been included in the map file + are not considered as valid. +
+Partition entry not found
 
The partition from which an other operating system should be booted isn’t listed in the specified + partition table. This either means that an incorrect partition table has been specified or that + you’re trying to boot from a logical partition. The latter usually doesn’t work. You can bypass + this check by omitting the partition table specification (e.g. omitting the variable table). +
+Single-key clash: "name" vs. "name"
 
The specified image labels or aliases conflict because one of them is a single character and has + the single-key option set, and the other name begins with that character. +
+Sorry, don’t know how to handle device number
 
LILO uses files that are located on a device for which there is no easy way to determine the + disk geometry. Such devices have to be explicitly described, see section 4.4. +
+This LILO is compiled READONLY and doesn’t support
 
If LILO is not allowed to write to the disk at boot time (see section 5.1.5), options like lock + and fallback are unavailable. +
+This LILO is compiled without REWRITE_TABLE and doesn’t support
 
If LILO is not allowed to rewrite partition tables at boot time (see section 4.5), options like + activate and set (in a change section) are unavailable. You may also get this error if LILO is + compiled with READONLY enabled. +
+Timestamp in boot sector of device differs from date of file
 
The backup copy of the boot sector does not appear to be an ancestor of the current boot + sector. If you are absolutely sure that the boot sector is indeed correct, you can bypass this + check by using -U instead of -u. +
+Trying to map files from unnamed device 0xnumber (NFS ?)
 
This is probably the same problem as described below, only with the root file system residing + on NFS. +
+Trying to map files from your RAM disk.
 
Please check -r option or ROOT environment variable. 
Most likely, you or some installation script is trying to invoke LILO in a way that some of the + files is has to access reside on the RAM disk. Normally, the ROOT environment variable should + be set to the mount point of the effective root device if installing LILO with a different root + + directory. See also sections 4.1.2 and 5.1.4. +
+VGA mode presetting is not supported by your kernel.
 
Your kernel sources appear to be very old (’93 ?). LILO may work on your system if you remove + the vga option. +
+write item: error_reason
 
The disk is probably full or mounted read-only.
+

+

+
6.1.2 Warnings
+

Messages labeled with “Warning” can be turned off with the nowarn option. +

+

+FIGETBSZ file_name: error_reason
 
The map installer is unable to determine the block size of a file system. It assumes a block size + of two sectors (1kB). +
+Ignoring entry ’variable_name
 
The command-line option corresponding to the specified variable is set. Therefore, the + configuration file entry is ignored. +
+Setting DELAY to 20 (2 seconds)
 
Because accidentally booting the wrong kernel or operating system may be very inconvenient + on systems that are not run from a local display, the minimum delay is two seconds if the + serial variable is set. +
+(temp) item: error_reason
 
Deleting a temporary file has failed for the specified reason. +
+Warning: BIOS drive 0xnumber may not be accessible
 
Because most BIOS versions only support two floppies and two hard disks, files located on + additional disks may be inaccessible. This warning indicates that some kernels or even the + whole system may be unbootable. +
+Warning: COMPACT may conflict with LINEAR on some systems
 
Please see section 6.3 for a description of this problem. +
+Warning: config_file should be owned by root
 
In order to prevent users from compromising system integrity, the configuration file should be + + owned by root and write access for all other users should be disabled. +
+Warning: config_file should be readable only for root if using PASSWORD
 
Users should not be allowed to read the configuration file when using the password option, + because then, it contains unencrypted passwords. +
+Warning: config_file should be writable only for root
 
See “Warning: config_file should be owned by root”. +
+Warning: device 0xnumber exceeds 1024 cylinder limit
 
A disk or partition exceeds the 1024 cylinder limit imposed by the BIOS. This may result in + a fatal error in the current installation run or in later installation runs. See “geo_comp_addr: + Cylinder number is too big (number > 1023)” for details. +
+Warning: device is not on the first disk
 
The specified partition is probably not on the first disk. LILO’s boot sector can only be booted + from the first disk unless some special boot manager is used. +
+WARNING: The system is unbootable !
 
One of the last installation steps has failed. This warning is typically followed by a fatal error + describing the problem.
+

+

+

6.2 Boot loader messages

+

The boot loader generates three types of messages: progress and error messages while it is loading, messages +indicating disk access errors, and error messages in response to invalid command-line input. +Since messages of the latter type are usually self-explanatory, only the two other categories are +explained. +

+

+
6.2.1 LILO start message
+

When LILO loads itself, it displays the word “LILO”. Each letter is printed before or after performing some +specific action. If LILO fails at some point, the letters printed so far can be used to identify the problem. +This is described in more detail in the technical overview. +

Note that some hex digits may be inserted after the first “L” if a transient disk problem occurs. Unless +LILO stops at that point, generating an endless stream of error codes, such hex digits do not indicate a +severe problem. +

+ +

+(nothing)
No part of LILO has been loaded. LILO either isn’t installed or the partition on which + its boot sector is located isn’t active. +
+L error
The first stage boot loader has been loaded and started, but it can’t load the second + stage boot loader. The two-digit error codes indicate the type of problem. (See also section + 6.2.2.) This condition usually indicates a media failure or a geometry mismatch (e.g. bad disk + parameters, see section 4.4). +
+LI
The first stage boot loader was able to load the second stage boot loader, but has failed to execute + it. This can either be caused by a geometry mismatch or by moving /boot/boot.b without + running the map installer. +
+LIL
The second stage boot loader has been started, but it can’t load the descriptor table from the + map file. This is typically caused by a media failure or by a geometry mismatch. +
+LIL?
The second stage boot loader has been loaded at an incorrect address. This is typically caused + by a subtle geometry mismatch or by moving /boot/boot.b without running the map installer. +
+LIL-
The descriptor table is corrupt. This can either be caused by a geometry mismatch or by + moving /boot/map without running the map installer. +
+LILO
All parts of LILO have been successfully loaded.
+

+

+
6.2.2 Disk error codes
+

If the BIOS signals an error when LILO is trying to load a boot image, the respective error code is +displayed. The following BIOS error codes are known: +

+

+0x00
“Internal error”. This code is generated by the sector read routine of the LILO boot loader + whenever an internal inconsistency is detected. This might be caused by corrupt files. Try + re-building the map file. Another possible cause for this error are attempts to access cylinders + beyond 1024 while using the linear option. See section 2.3.1 for more details and for how to + solve the problem. +
+0x01
“Illegal command”. This shouldn’t happen, but if it does, it may indicate an attempt to access + a disk which is not supported by the BIOS. See also “Warning: BIOS drive 0xnumber may not + be accessible” in section 6.1.2. + +
+0x02
“Address mark not found”. This usually indicates a media problem. Try again several times. +
+0x03
“Write-protected disk”. This should only occur on write operations. +
+0x04
“Sector not found”. This typically indicates a geometry mismatch. If you’re booting a + raw-written disk image, verify whether it was created for disks with the same geometry as the + one you’re using. If you’re booting from a SCSI disk or a large IDE disk, you should check, + whether LILO has obtained correct geometry data from the kernel or whether the geometry + definition corresponds to the real disk geometry. (See section 4.4.) Removing compact may help + too. So may adding lba32 or linear. +
+0x06
“Change line active”. This should be a transient error. Try booting a second time. +
+0x07
“Invalid initialization”. The BIOS failed to properly initialize the disk controller. You should + control the BIOS setup parameters. A warm boot might help too. +
+0x08
“DMA overrun”. This shouldn’t happen. Try booting again. +
+0x09
“DMA attempt across 64k boundary”. This shouldn’t happen, but may inicate a disk geometry + mis-match. Try omitting the compact option. You may need to specify the disk geometry + yourself. +
+0x0C
“Invalid media”. This shouldn’t happen and might be caused by a media error. Try booting + again. +
+0x10
“CRC error”. A media error has been detected. Try booting several times, running the map + installer a second time (to put the map file at some other physical location or to write “good + data” over the bad spot), mapping out the bad sectors/tracks and, if all else fails, replacing + the media. +
+0x11
“ECC correction successful”. A read error occurred, but was corrected. LILO does not + recognize this condition and aborts the load process anyway. A second load attempt should + succeed. +
+0x20
“Controller error”. This shouldn’t happen. +
+0x40
“Seek failure”. This might be a media problem. Try booting again. +
+0x80
“Disk timeout”. The disk or the drive isn’t ready. Either the media is bad or the disk isn’t + spinning. If you’re booting from a floppy, you might not have closed the drive door. Otherwise, + trying to boot again might help. +
+ +0xBB
“BIOS error”. This shouldn’t happen. Try booting again. If the problem persists, removing the + compact option or adding/removing linear or lba32 might help.
+

If the error occurred during a write operation, the error code (two hex digits) is prefixed with a “W”. +Although write errors don’t affect the boot process, they might indicate a severe problem, because +they usually imply that LILO has tried to write to an invalid location. If spurious write errors +occur on a system, it might be a good idea to configure LILO to run read-only (see section +5.1.5). +

Generally, invalid geometry and attempts to use more than two disks without a very modern BIOS may +yield misleading error codes. Please check carefully if /sbin/lilo doesn’t emit any warnings. Then try +using the linear or lba32 option (see section 4.2.2). +

+

+

6.3 Other problems

+

This section contains a collection of less common problems that have been observed. See also section 5.4 for +general remarks on using LILO with other operating systems. Some of the problems are obscure and so are +the work-arounds. +

+
    +
  • If LILO doesn’t go away even if you erase its files, format your Linux partition, etc., you’ve + probably installed LILO as your MBR and you’ve forgotten to deinstall it before deleting its + files. See section 5.3 for what you can do now. +
  • +
  • For yet unknown reasons, LILO may fail on some systems with AMI BIOS if the “Hard Disk + Type 47 RAM area” is set to “0:300” instead of “DOS 1K”. +
  • +
  • Some disk controller BIOSes perform disk geometry/address translations that are incompatible + with the way the device’s geometry is seen from Linux, i.e. without going through the BIOS. + Particularly, large IDE disks and some PCI SCSI controllers appear to have this problem. In + such cases, either the translated geometry has to be specified in a disk section or the sector + address translation can be deferred by using the linear option. In a setup where floppies are + not normally used for booting, the linear approach should be preferred, because this avoids + the risk of specifying incorrect numbers. +
  • +
  • OS/2 is said to be bootable from a logical partition with LILO acting as the primary boot + selector if LILO is installed on the MBR, the OS/2 BootManager is on an active primary + partition and LILO boots BootManager. Putting LILO on an extended partition instead is + said to crash the OS/2 FDISK in this scenario. +

    Note that booting LILO from BootManager (so BootManager is the primary selector) or + booting OS/2 directly from a primary partition (without BootManager) should generally work. + See also section 5.4. + +

  • +
  • Windows NT is reported to be bootable with LILO when LILO acts as the MBR and the + Windows NT boot loader is on the DOS partition. However, NT’s disk manager complains + about LILO’s MBR when trying to edit the partition table. +
  • +
  • Some PC UNIX systems (SCO and Unixware have been reported to exhibit this problem) + depend on their partition being active. See section 4.5 for how this can be accomplished. +
  • +
  • Future Domain TMC-1680 adapters with the BIOS versions 3.4 and 3.5 assign BIOS device + numbers in the wrong order, e.g. on a two-disk system, /dev/sda becomes 0x81 and /dev/sdb + becomes 0x80. This can be fixed with the following disk section:
    disk=/dev/sda bios=0x81 disk=/dev/sdb bios=0x80
    Note that this is only valid for a two-disk system. In three-disk systems, /dev/sdc would + become 0x80, etc. Also, single-disk systems don’t have this problem (and the “fix” would break + them). +
  • +
  • Some BIOSes don’t properly recognize disks with an unusual partition table (e.g. without any + partition marked active) and refuse to boot from them. This can also affect the second hard + disk and the problem may only occur if the system is booted in a particular way (e.g. only after + a cold boot). +
  • +
  • On some systems, using linear and compact or lba32 and compact together leads to a boot + failure. The exact circumstances under which this happens are still unknown. +
  • +
  • If the kernel crashes after booting on a multi-processor system, LILO may have overwritten + data structures set up by the BIOS. Try the option LARGE_EBDA in this case.
+
+

+

Last updated by John R. Coffman on July 17, 2000
+reconstructed by Joachim Wiedorn on January 29, 2011

+ + + + + diff --git a/doc/html/user_21-50x.png b/doc/html/user_21-50x.png new file mode 100644 index 0000000000000000000000000000000000000000..eaaf507b72a87fd9c3524aa394fc60a6cee153e7 GIT binary patch literal 843 zcmeAS@N?(olHy`uVBq!ia0y~yU}OifeOZ`+WTfF9Eg)qO;1lBd|Nnm=lX#$icR@8! zHGfHvUoeAF=k7A4_h}<7o3Q>!QbfaxVh|({4`}$B+!xw=)ehgaajx|MwKWAA5PX z44>=vFwHW7GXVz=Do$yTl-b1YEB>--f`j)O)g?jAO|~*D?UNcNM{78FFV~WdY2jf# z8Pt?esPV<&4omI*qwCqki{15npUUp}ecw9n-uM0YYv1qq-Sp(V@%@+`AGZFKxp)1J za*9$>a^AnR_+@{aUT0srucCM3MuA^_!hE?(_C?#JAHAKRHmTmpym~QH=e@igYOh55 zre=Hy3@@+V{cu(VZ|$}xTesFWO{#tMWc9Rtd)M6E*DUUT>Dlij*Li%GkDS|VZZIce z)~t*Z35%5DY%fH&g%+H0ke0L&lC8A!5jIm>tMo|E^n6QMLFAiw?@ui}-LWj-ysb=A=f`VZOB{Snv>MtzE*06}r)F|;Nkifc zjV0!DZ-|)cstOz5x~P>~W2j@iUG0n6GiP&0|1-5mwj0MCo}(godfJ5eRWI_x4X3&8 zn__0aOm(V(@Z@Fh^SKL4zoa*~X$qftWv}+|^V2*Pj}N($OMcbul};&`=RGq(Wd_6Q zQ=G0%oEuinLE%`uSJA6G{U)kLkols5<;IR5iRL?O1^7Q*zVyHSh*H6o-g`E|!gs44 z-%s7QU>egT1F5uJwoPZ;nJ)bMack|5b0+)3iudhhF)^HI^rm{kQC*>m>WfjeGjAVR zUXdN4*5mf%Bil@c#_iKZ_lf#MOyBfxvW`OMlDRXyCUFWyRxI-qzMdVLt?jUk-K6k| z&!W6jM)I5wN@s<d?v3S)3&C(ils f^LdWM;k)tfQlpj1@{an^LB{Ts5_GoG3 literal 0 HcmV?d00001 diff --git a/doc/html/user_21-510.html b/doc/html/user_21-510.html new file mode 100644 index 0000000..d6a15d6 --- /dev/null +++ b/doc/html/user_21-510.html @@ -0,0 +1,31 @@ + + + + + + + + + + + + + +
+

10pfdisk is available for anonymous FTP from
ftp://sunsite.unc.edu/pub/Linux/utils/disk-management/pfdisk.tar.Z or
ftp://ftp.funet.fi/pub/Linux/tools/pfdisk.tar.Z
PBOOT can be found in
ftp://ftp.funet.fi/pub/Linux/tools/pboot.zip

+ diff --git a/doc/html/user_21-510x.png b/doc/html/user_21-510x.png new file mode 100644 index 0000000000000000000000000000000000000000..c95e97eced65b91050618960aed09f3f48f90deb GIT binary patch literal 1934 zcmbW2`y&&M0>u$x7}fT@c}0JTQg>ulvoWF z^8Sj7=8<=ONiuoObraY97w-AtoX;=k{CdcE2aFs*2_PaOB8R<^dMW%DVTmQ5%ztId7;eG|5Wyi4)H=ubrr%Vc z{)`@;V0W}kcSIfo6OO0Q3yb1FpCkIjrUF6jQKejGD&d31wBnvHzP=~m2RYl-*p%)L zv_!JU>D8mH0O!jtuz@1rO&e&A2+|M z%C2X$;tOk?QTP}O6pf(RHMtQkev=jAfGQ(-sp4S0D}R7(sUzVkI@F!ER^zqap%=+E zsDc^aXO79-Q1K+pU>$R0#;LO3S-ekuNAW_u?VV5CbZgJp2V4jDwT}Qmqg<8@C5tZv zQIx+dcwF$E>$tErvxEP<^=-z{&((JJQ56B`IeMwnI&19fj9Vm|@^S^tY`j`#D)XCr zg&xpQob`Q<=K(@62P-2gr-M4w(mN`3WGXEp83L?|gVIe~-nkGP=0?(ke)in6#4l0n zt{0X5u~y+V;5)YQ9@8PI7OEz1xE|LDfR}m9 z1iRgc+&QbpWE4J;J(_7dy^Mf73YF|QA$=-G6oUhkZ1mb zBm9@qE)_}7q7wK0!@Hww_dj74msG zp|z^{EJj2};8{DU$xmwwzi(2O9mF1w2>%9D#>octbY)Q5(bNq+bLNL{toe)3Z_b6A5IqG6H@P`@R{H)3># zNHa$>RM-0TMo0dHe`o(b%=-FeIAVTv)Gfb6YvHV-2>ICF4Y^6!g87P9PaFvYQ9$fv&-4EhxtyHBd$+q)VQYBsj@nou(@MHGagACndu zI)ra-wz}X$CuN8~?UBau^ulkC+*TAwS?4*fv5fksB*aeiP^K8TO?FX3ci(MgN%8I7 zfb#7Dy4S*~@?i700~M$~Jgpj*Fn*r7;oaca8Uv(lQsy(W9l8yJw2SZ)w{uh@;??nh zHwV8|poPkR={K*r2gv=C^v)~@$IhSnBF^uoSnZxJxW#fAa@48DPr%d0TFzWs@C>#- zYjCd9oHe!&B&Os>+~Z|_2NNNem@e!8Ix4KWE~{^#d!yyya?-1hekK)SE$QT5bP1x< z??;thoeQ3k%tlLW=bhIa;Z|>qm0Kok<|O=EU&*I=tsJ3g)d#Z)tMHf`<1|SfvV|$6dQgb#CUo3`NkI3|HJB2k?&q*EZy$fz z+2=2)!cSDcZNInX(A)wG( zG<%9Ys=#iZeip`bvU$vp>>Wq|(a46SH-?y@{toNgldkUZuz2;birw^HfMt99&nn(^ z2kkes#+oM(OBHaukx<@~uAm+A#J|^4L-_y+pQQ|Fq&f9~H&xY`PVj2gvoq{Pm#%>$ zX<@|~%e@7vJZy#El-**utVWnLACAEWHf2qfvg+3e;*O`!FVjn5l@K`Pz7CP6a zkmNj!8@xJg*UPTH?J?;r6cJS?`*)Eiwy>DYFblX%AFMg; + + + + + + + + + + + + +
+

11However, if only “unimportant” parts of the system are located on the “high” drives, some functionality may be + available.

+ + diff --git a/doc/html/user_21-511x.png b/doc/html/user_21-511x.png new file mode 100644 index 0000000000000000000000000000000000000000..f96b98d174d8b446ca6a4caf2ad3343bdc872d40 GIT binary patch literal 1444 zcmV;V1zY-wP)X5faCb&YQ){*>F4dOqS`d1Y z(4PgqL3jzRX`EHk)S8n(@S4j#8C+(o%2&NDW$McrgikUE*BJDE+?B)YQePzRaHWUr zJH>MOl>IM*4yP=T@uz^yN)FGfK!V(^q-3uSlwQPbGNVX>K?gjuyPUB&wy%sJa5)z! zoiAlTcITml_>Qh*?Ldz`N`Htffxe#DmqhE{V|hEYUQ4la+A_M#NgTnw0NFkH2gNrO zowrAMfu@m{8EF@2M%q_)XuWn8(G)G+BKq(Yt^l(@H-^Ord~A>M0=1s!yP}8T0baUG zc4(b8TtLephIKkr(7Yo7vT2Wo*@vCK%Jat~y+DCaEYN2R`ne9kb~k4cPGJj{pd&Pv z2H6Y}-zC#|NIXCpZN3cBml^c1Zm0BaH<5cT%zJbi`in`hO(6Ce^Tvohs1~$wA(;yu z;*+5(W4y5yyGHF;@0NFA*B?{4(Bxs&uQi+?|uV2Bh_n&IA|C zC&vz(0KLEa;z0DCm*OynM_-Y_R;5a}YD-vs5CTiU&J^xLKY{3s)qmk*83z$Gjf)mT z8Xqa&C_xQCEn9$hQ^pKJCWX>rK8@%M&}a4oCuDHB@{w}mdkJdwz=*>8GAL-6J9QmMX zB<1a;-#NI!Q&-8=@T#Ensl8wlq>S`?I+y9XPejqg|OS$6nk@7i1B-R3* zlfe#ER)=R~+`=735=jZ*s?)i$E*eX@zJwSLwsPMtgK9zg+2{)sd%s9LUOctfzg2>q z-(QR4C*|2HP?OwoEePW{lYAnaFp9=^0m;moTV4F59A9$0mD~8hWdKF7(l7{g3Ihzn z9T|3_H7|{;@{@9%e$yG$^bD6DcuF-hY9Y|L1!@}Pc$|^iRryN!rYuKWxuYE}qcWqA z4bqEv>>!8GhpJNiq&zAUvOy6UT{EN4%OEWkE+W&*lh$Swj{Jo;`YS&gmj}Sg{a!7I zPKNGfZQDEBPVC=2G_iav(fcC>ManznqWS!lU!eoqq;LzwH|rSI(uqs0+EfP$ibu7r yZfCXFc8sFcdlMTc_d4i$SG9WS) + + + + + + + + + + + + +
+

12Setting the “system” attribute from DOS on the critical files (e.g. everything in C:\LINUX) may help to protect them from + being rearranged. However, the boot floppy should still be ready, just in case.

+ + diff --git a/doc/html/user_21-512x.png b/doc/html/user_21-512x.png new file mode 100644 index 0000000000000000000000000000000000000000..2c74f9b5f9150eb722dfe7b9bab1362841b7ae92 GIT binary patch literal 1986 zcma)7dpHve7vExXZG;%fr3<@|yb`U;u-q2SC6T-|tqpV6$R)Y-vfTC&C1Iqs7^a%r zT;7NzGpQ+KAu00?S*+;d)%V}`-*=wpoZorQ`Tg}f=RAjkb#qiv)KLTg04mN-Xpc=C z-t<6Onax;^nzq;kbL>g46B`>Fo9X{=`-QZ`O*S~z!_5<5LE#vwmT)hUy=u`*LQr)^ z1pu(s!WnJrMFcIB1dudNYxH%65d^}8CVzK(YM@fqUTI~rxsiLMvd;(GwgXTF@HGc@ z(hGYnC(F-vyLD)?6RJkNTYU`GFtRmh^nu6VU(U+fS%Dd}93XDK;%)Jc2a2oZoIm0S zi$jA8E)+1iV5n?qB8C^SST?qHu^B~%>vv@P?U1>F?6ubCgm9j|wRMM{9&H~#U7GFu z#`l>g*tM-Qk**fv_a)K=RtSezQ<<0J%;XO$5cdNo4G-sxkardhd>9BqO}jdN^O=^1 zo*7K`wRoKiMaQYhA5w_jv&fjf#87D@Vwy5VkaIS;kyYMRD`QjYFXOF{F`aTp5E~&j z8CZFXTCi`a;4!L;QK3g_k!iD0h?b6Rpqm^ehf}%qzgGrT*hiWc$O5;O7Ka6W11@TE z*SR88@ITT&k^BaHYjUNU7vvcWln*%hX64vW5VsMSctdN>GGQ&pjxd&E_i4eaOS&EB z+!Slicouz5#tg_OP9K;G+9WYnG|DtNkdMP7{w&XA0fQ2$e%4ZowO#H$YtF5ASL(%n z)$Q6KR%akSmwP_qv~`R)<4-J8!F3dePvzNM`+TBG!yJA6SKam|CuU8u~NWxRLQ{Xf<2}L#*GukBq*2 zkX0N|)cw-ffdeJak@JId2SAr^e#sXUiIsi*mXTY>04I<@4+J%(`Rj;K#WAitohC)z zoryt&c-k0BWS)Xr+^E5Mx-Q!#>%W+nazj!_==W2#NQ(V!&zpYMB`MS9 zEoJVhKDdAv)niz3XS}qtQ}ukQBLhV=dDwg9*u3O$YbQd*-IC#yz8Jahkrdb9Ss0c< z@KzwJn29Hrq41ESkScCOUt>JxQp40|tr`P(gLa4Qb6}i*llRnrpsNFd`OX;X)8#^S zgRUa?zK)xVDfn5+ppht#UGQ5{exhjIH-Hf)%-dB}kzxPlOv>lMxMP`4 zcM7`ms&1F4VRkkK!UG~}DbeY+3AdxK6A59v46YS@6;0qwhd;IF(MCoZA=jP|9uK5p zXMl=L(P7%Nu|TH4Gu{;9l`;1hp>r+7&3Ing+eJz?uH!9Qut!Dlok3uIDnyes8?431 zqFHJ74-yxh124C4_p7XU#hp9IMPxg29fEAGJe@{3;b*@I-2GA}4N2HUSqfHP+vLvE zd7{VC@f>QaLNEAMyt$HxZ);yC{nei9-Xqe&AU%*g@tMmOP3Cdyqi1WsF5zf3>EG#l z^bGD5ox%`Mj~$r>Qpv$B9)eWMCWjujSa>y+=%Bk6YDac}!Sk0D#@Lvwploptu1Ia+ zh%|F-NuxrIF(_Y(r`(Ft9A5(n9x#*q?o0wk_q>~#IroPmpJm*`IrCUwpfqVG{J7Gg zH7}=on-fmt>iGy7n<@E$$lhj2s2CW=vaGf05|Pex`|GQTt`7o6y_;{z1{;1`2*c-i z?hZM1RpS40>YgqyV4{q$k0Iq6Y#Cyv#ED^h(N_${+VEW7$=Cb#W~e_s)*|;=nKhTZ+4dzayQBBLL)W^Te{NoGnatE`+2qfzTek8}Ws-Y`#s zWc_R;GQo~P`}Ik=b^L_>i9}O0-8~7;184lSzT?v^g}1bFP>S%4IZ5UXGw&CBKiqo- zc@Ice%^DQ4q0A(Qp6q&onPGajvaRa+?wGi67kFF;2=8!R^qiIj;HM7?TcONz2@RfC zJ6Wj0DA@~(L$3H)tyT3KX8WeM4?!A@?N^k;RVZqKE3R&e#mu9r1b?=_(SB<8`Ao*cnRO2OPg-CmU+$Th^&?{o`N_6g zq4uL5IdcYPnw79|OV1nVVU4KIgS_q?I^6qf`Mr#njhHU?DZ;kI=-sKmU^D{-R$q*# z4e3d|P??@_lg&5XXL~lQJv^eeph}HxjJjSlAo`VG9KN&6&y2qT_AT9bf;oBs{`(C( MpKwFh+Xbfm3y{{Tx&QzG literal 0 HcmV?d00001 diff --git a/doc/html/user_21-513.html b/doc/html/user_21-513.html new file mode 100644 index 0000000..a7d3917 --- /dev/null +++ b/doc/html/user_21-513.html @@ -0,0 +1,26 @@ + + + + + + + + + + + + + +
+

13The default boot image is either the first boot image, the image specified with the default variable, or the image that has + been selected at the boot prompt.

+ + diff --git a/doc/html/user_21-513x.png b/doc/html/user_21-513x.png new file mode 100644 index 0000000000000000000000000000000000000000..70a1318589303f8144a65fa5a5b437e178d9fc6b GIT binary patch literal 3501 zcma)9`8yQc7oUk&rijd|7=-LQgRw8wSjv_yTNq}HWXYB#24hW)WfB^bElc)g$U3i* zXa<8wc4Dk$NmB^vJMa4!eD4qUp8K57ea?A4=X1{U+|-+vCY)y=X8-^I=XF!K4FCXq z#RqL^r|P#a5I0K9XKhPLCroC*!wAyn5_ z`!HRcLf7F}>>_|$w>fbFy}U8{e>SJ}7x*jS*0%Z9MK^(Zaw}G#Bwyz;L+O^d((KXT z03M?k#oA^Yu~#$(=VfD7FKW=y-WjgfIkTU-k-ne}#ahPr;%PwOD3k5>HE zcQO}*+%JgV{T?vj;EeIcvLG%Y_s!;}PD=ss31VH1p{|v3p_cg>W?{bC5usc2m)0BQ z7$A0Y&p-**%)!UJ#^Zv}4l|@vtkoT8CI`n6xX*fBTP~VU6JRI;s`Nu$PNa0>Ck<&% z)%VTIV*9Cr(5rNV<{kO2l96u857!{sA9c-DoV79mZU$;28UV2CU#bh%Jo1)Jy0Ex3QVfHAD_P2GzjWL_KYPwNyxhebc*r;r zKUQowd$P8pQjWDZ1^^H&ooHq-S#1?tZbaxdL|^z7uH9jxh>x4iU7w#?qnDI(GK;+)1_2wdOm zc&6-fzWqQ8x=5X+mcK%cCBKZ`$_f6wn;@Odo-k$ka%>sdZ_z^Ch}3on$hFmRHr}W@ zBol(O?EBVdGe@udbmj9}!&>WZpHNv!W;B*B*WYfOvKbYm8!w;Xv8Ymd0gs>QP(f6m zs%E}Y7Ccua62kSSP(%&1g@zc4bvcUA}Z4Ja@#ygF;0`q_P7FpvpDMjuAgdcw&$2*jZbyIFzXD7`C z@(pe?6xzHYY$hG)0Kw#M{3W^<1Uqh?D|Z67xZ#F$YXn?47K=UGLT#w0erS~P=(dR7 zhhe$d_Wg?{L=sR1u0Mk>Oz*o1ysWeLYd(Ga>6Tn{q>1RAB-OZ>h*AZbXJe>Cf${kf zoHAh8`^qxA-=I*O*Eb~M1aWMBNdRY1;~BWXmd6t0MxdxV5-5saoO@f|FJjsTwL?}L z@IS=fdgvsN*4MC0Gso~1i?g0>7=HKiG<&oXaGkE+ zl+im9R=O2Z370%}Ck|HQ2FpS}*>7Hs%N{}BM~j}GX$2MyQyLtPN>&6|fFNQWmslq7 z*ke`j87uh3%vhYhSP#-g0e1(X2Imw zlSWUqZecz=HqBhgPUTSSGhfqsVy`n>rBU7Hr?qwsW&^N#g-v;VD$7Qx?0CgXwnfA4US3j2w zJZ%KO(3*GOR3k-N#D|OVpoCC@?Nvf|QB5ktNsD2c{G$F7tBWyyaOgqSoAHPrDs*M| zzv)E|pcfXvWC6U0izM>+N%#ST@3MOtMicwt3n?=FVBBaGEmPVa!zEq1&s8))8I48<_o!pc`LF`H(5{EHgAKzi6Sb zA}2yjtchD4_~yz(x4jEHiecJQH4-cX9!7h&X6uvGBa`ht#;9mLW}1sG2RCln^&!Mp zm!jm?q|}%|F{DUZwrL_hRldS7F)5VfWR+|-v%^A;7+?6ll;`v?vQVAzIU1Y+ow9{} zrLf}J#NM7H<;rG(Hc(9k9Jwv6EV{|;Os38rlDG*_g@@X=5-gcOxC9|a*#Rv}0C z2fxY9`OPxupYgjISDHn`+f=@JFy@Mre@$EjzsV89hrEv1E~%g8b(wDUFZgBG@w_9N z33D+s$>)nMI$QC)pJAF!t+Gmx(Qpd#Ex(m!A-h#|Ph((qFn6c{+6Gc&>hU50vg;M_ z$z59kIzMItHfpiw-}xn5FFyhGrJ{FyN>+@*VDhRx`YSc`kE-d&unOi3HqETf!pUaY zFEII^oZFnB&$OChYuL))1VT-Vj(r5$LTu#eZ*Vwy@U$-ew&@`f1+ zy!WmqO&`ySjNywnI`;A5%xz(KB<-qoCDT&+QK2OMXtI*U-&2ROC0VqUts+nZ9z8F;V@g^eFXkQTkc zF;i=y_LS)7in^=IMIipnwS0`*|M3Bi_qXqh>gt!PUV{3rI?U{)lB2SHmR?;Gr*ts} zYG6?QvcsxjB2#2eH;kDQSE}Fvk(!<|^^%@_K-7o~8VZK~*4huJZD%y=j7r&gk-Zoo zW2Q0+9Z_nec6!x@yvv=?+RXfXjkvI#jOL#3x#yZe%p!%@#^ig96)&L1og6ksgw059 zkxcw+nb*X~e8YB&0)w;HQ%nOp^UPcfZGFb5t9yeAMzHkYEKF`4bGQ)R);4dTLd3_P zF67Bw5e8?0d!0+^Rf8(X+dz9}HSaSiSSafs*-%3>Q@_AZi|$YL{9S7M9y+$1OJmYd z4Gq34D@;lCq>UE$t1)Vu(qcJ`R~UKLcB|-;vTG>Hko2o4?iEQLmt3bl%yiLz&6r?VGbj+BYgg)q=A=|*?H{~Vh3dFS6@T?lxf434m%}5n<3cs5}%hxhqfmbr; z{r&>u(i7TmC2|T%H70T{F$40>W_)Xf*4tjUl3$)91xWMTTSM~_`cNU?Y-tDFrVii_ zZr8jZS+s-LK#F#?BG9+;fxjS1i7*3l9ERF@k-mU=fcR{_kHw%{s|7Ly=V5FdrG;__ zZE0y&4b3A2!^UdxdM5)l1gH~L;-1?La^?0PAV2{+TV{{Y&- Bq9p(T literal 0 HcmV?d00001 diff --git a/doc/html/user_21-514.html b/doc/html/user_21-514.html new file mode 100644 index 0000000..7090aa3 --- /dev/null +++ b/doc/html/user_21-514.html @@ -0,0 +1,106 @@ + + + + + + + + + + + + + +
+

14This is a list of device numbers of some frequently used devices:

+ + + + + + + + + +
/dev/fd0200/dev/hda1301/dev/sda1801
/dev/fd1201/dev/hda2302/dev/sda2802
/dev/hdb1341/dev/sdb1811
/dev/hdb2342/dev/sdb2812
+ + diff --git a/doc/html/user_21-514x.png b/doc/html/user_21-514x.png new file mode 100644 index 0000000000000000000000000000000000000000..48756178d42dc3f5cdec6e7973d496f68c166525 GIT binary patch literal 2774 zcma)8c{J2*8y?HpcSW=zjT#g)mK4+2*Ro`262>w=+n6kc;>AnChe~A`L&m-vBg>$o zY?EdhA!T3lO)}XsS&DDo@0{=d@A>0??sG5Kbh89V!f**Ai5$1D|MnXfyhCN>Mm;!a6I8>oN)M>ky3U~zdVg!Dv;RuF%v z6uD|uyiYPloQ)B-3Aaf^Ha*EW%EKdb(n(s=Y|BL0Cds4t}(%>&2 zUH#il`pY!ik8 zc*Of>hDS3^NaU{fIW&3%;|T4?^KG~N*`g0><#@;s@{IO{v?NNRsed`!XxfY4#5!n* zKlrv*nYct&b9f>^yT?j}$s$h#ui>KSXkw%=UlpA!aWnU_P~bRzY#+C{JPj`x3?S15 zl?>C8I+W4@kGi3nA1ZZIc~G553%~B;bL&e@5r@a|sSG|@kWeJD978vAG=OEYs))@l z-FBR0I{mcf#XraQ-pRC!Si^>!cLZo`SkRrinwxPLQbmm*Fg|dv>U|HTb*o2>3PQRm z^wGqimgj=2(wMD|kUc#>;3S0U7VsLD`F_$a1|t*p>-ILs)wz$SeOPV!?%HvK{9m$= zrkrv5HorWm%LHaRkXa>v*!hn0Ldlq(&!Nr>(uGz^htxNpW!rv@ed!=*%YbN7a|Wm? zO+t@-)DwZyEak7XmxokG#rv2ml$~B?qB}PHH41K zp>vGESH!S1bl%#-j8(y4R&mvg`|z@Z?~?W z@^)4a#R|9p7_2}w16k7?(@&MUi4cA-qj<<|3X@6(x2D+IFcb)t}bFK&uLLM_|}ahba9pfIJiEw ztL5rMdPFMWY-9U)g-30eqhX+qvHS+qT=r0 z#Am`<37AFn@8H#vq!1x!wD0WIio!3v839e%n3)l|6!G+)+V2{&Qon$q+FJea8Yzmd z3>eywuDlEDN&m_diYq>Ai%rG3S^s=O=N|?g zW8Pa3Id;Y)p1tO-G?~**$l5A^hkBp4?~pt_`DWE z_IH{A0)#IP=2&XyD~76d`Gw3*W$Q{1IXp@aw^Z$*!=4J2SV*o#6Q2t9$mlwo=k1IQ zpZ80@2UTJ|upmjs^9Bb=uL-*q&lbX_FJLMzTfB{kcOUd^ks}H9KjKw_z@10KYBw;C zUAQ0@B)5|Z6BxPMDJPk{-mvZg3DXPMN4=v~FxuY%^liT4rz=U0aY}3EKwK6ol z1roH=j6Ai{KgKa&)epkmUwbY<0l^oN#JFw#$H9g#XR3h zfiFV$iM5gFQ_h_C(fCXq5iwC?N3=aITk+j>XHmSg`CWI4Y2ay}j`40bkJCY~$s5gi z@15$cUm?-R=Fzk>vXd(35~=}L$yULUm7(iNvvL$|xdV?Ac*(U@d8$iD+L2t+Lx~f3 zK@H2mAjze;qBo_-iq0WC7^x#pf zNEfSvt^f1f?r8AkE+)3W^)Na*7FKGIt$pjXT?);mk2R5C7fGcBx^rv~!+=i``pSY0 zbL%55Rh6&qqqaRZ&%BZt4*FQP7Lu7aVcEDs)H`~rwqRB+^VW+|4VUR#vO8e&@!#o| z-J-b)&&LsBA!6zu?O3X{eXcnMY}KB$TBFN%PF22inAa~URvVst3NY>qOS=OXGFH)< zdO<-(iXL6`wULNh!q4B@=p@F;eEFB_>hRK=GmV_zi-mg0`}zNEPzRa{DFU7X8Jnm} z{X^GpTnhGJ94ya=$R_b|X%TAj2y2utz=v@X`?uFhAs8x?tP=dN9BukW)4Mkvp}5OR z^fNiSMe$!EcG?Qxu*acF8J7&X)Qq(e4!TBA{Tf@TBLw_7%<*A_`FPPfQ<_%&)^ks{et!9=La;E4(ruFsUHb zfcoxax%2~eliI`LyY(?BeJ|8_txor~iTi)3v&C6eMZ zCgr%(t8{i?GO>ZLuk3>@h^yLv(?_aSL#{;&*5TA;vVo(v;e#E*`#{Mv* zB`4*8JfU%Z>@ioKA!cI#+s_1~J)8@!T@u0JKHR$oY2n$F$lv!BWjE}JTb$t&MSVJl zJc+;lRIDg;3i97jIB04ci&14S;pyor!5-v{c3oEco2+$vVu$Eum5X2q+x?phxq*@v7h#HSkT^%I_S!xX$g%{2TZ3ebzNkp0g&H>>mn&~B> zb%aXcH7O9d(=Hpc=_SpeU|dC~?(d4zdy-TD2*I z)H#K + + + + + + + + + + + + +
+

15The device names are hard-coded in the kernel. Therefore, only the “standard” names are supported and some less common + devices may not be recognized. In those cases, only numbers can be used.

+ + diff --git a/doc/html/user_21-516.html b/doc/html/user_21-516.html new file mode 100644 index 0000000..6e7a3e4 --- /dev/null +++ b/doc/html/user_21-516.html @@ -0,0 +1,52 @@ + + + + + + + + + + + + + +
+

16Options are frequently repeated when a string defined with append or literal is prepended to the parameters typed in + by the user. Also, LILO implicitly prepends the options ramdisk, ro, root, or rw when ramdisk, read-only, + read-write, or root, respectively, are set in the configuration file. (lock and vga are handled by a different internal + mechanism.)

+ + diff --git a/doc/html/user_21-517.html b/doc/html/user_21-517.html new file mode 100644 index 0000000..4d927da --- /dev/null +++ b/doc/html/user_21-517.html @@ -0,0 +1,24 @@ + + + + + + + + + + + + + +
+

20E.g. if your root partition is mounted on /mnt, you can update the map by simply running ROOT=/mnt /mnt/sbin/lilo

+ diff --git a/doc/html/user_21-518.html b/doc/html/user_21-518.html new file mode 100644 index 0000000..f921800 --- /dev/null +++ b/doc/html/user_21-518.html @@ -0,0 +1,30 @@ + + + + + + + + + + + + + +
+

21-R is typically used in reboot scripts, e.g.
#!/bin/sh
cd /
/sbin/lilo -R "$*" && reboot

+ diff --git a/doc/html/user_21-519.html b/doc/html/user_21-519.html new file mode 100644 index 0000000..79d3f14 --- /dev/null +++ b/doc/html/user_21-519.html @@ -0,0 +1,24 @@ + + + + + + + + + + + + + +
+

22The boot sector is loaded by LILO’s secondary boot loader before control is passed to the code of chain.b.

+ + diff --git a/doc/html/user_21-51x.png b/doc/html/user_21-51x.png new file mode 100644 index 0000000000000000000000000000000000000000..c4245e6fe061b46a4de2b7a9fa4e232bcac8b3d0 GIT binary patch literal 3123 zcmb_e`8N~{7Z!=JWvmq<*~U6UmSN;ImKtWV%qWBy>qrt=i(VqeR+uqEmTZ$5O9^SL z*|RfaDJ=*|rj&|d$mf0kg6})$yFc9foO_?=+%9JCj_{-xP%esEgiYI z4k;ht>ccz-ek}g+{6PTQBQaL{`}+s*zc-!tk8T~XkKS~=fadaB$5_4>RUFaHYpKFV z*h~{5xwr(&5SHecs6$`f?gYu6ll(K?(zIg28C@|xG$hiAQ-q7swDogs+*Qxbid8ub zIAzFMrF_AFlr76Wl8&SZvh7{%*$x*lRDp^Omtc)@gQXMPf!n8VBuV_KwAZo0Ri+MD z#T(Ql#-4g`2G{-L1MBOa^Lh{~BvND|^NgY1`Uvax*2ue<-OaB&pYmn}eqY#*R^*=j zWQuL)sXc{kPTEt4@Q&{GHz$NqGfak-9rv$m77D5?_f>xGtso*iYYQ2tZ%)YrtEgPI z)jI`4?icN(k&$uHIscaD6F}G8_4(iVO|7_%@-j~!lbBg#3@WL4#c)-~d5+2yoUxrx zGWKHp3_uIGC#hC08T%J8yUO>*_wzUJe!%xX2D5FXbuRCF1NYdDv`U@Au4`@L$Bv&r zG<$!xzfnH&Tx9j=!iu|lr2X&BLuE!{xLR3^_a-jeJQ~v0v^LcPM))3Y)*zII-YkND#9A-Fo7j z;dk~bYz?R6mE5Q9$kN!1?DVOflJBe_;_fkK0Yzku_*FlKXhYMZE23a$nOP=>5>RRC z&hHBjk`-7U=Vd*{jbzR1bko+A>Yluw;}zc=kDMs7!)LD*fPTaYxM5;G)5>}^NKvT~ zQqhhs7IVc+vBVsA1u^T14pC^7o1jS>IUj!5l{|P34+wBtwx}^Znu0f*tkrp*L z7`{=8qQrh);-`37d_i++N3!I2S4`k|Txz(ve3#h+il21DNiF$0@V4XZj7#J3G_TFb z?(%oX0MapnK=sukoL@7A{XV>v@36^q`>pSVJl6|$?{0joabV1cOq!h?A?7j-#U|=RRJB|{Ryo7wm&=>9HzAQEw1r=<@3nl@{xn#*dIj(TBR|dfUjD}6@!zsfgoei#_iHeuOMwZ9xa}&2n=1KB>@O`h zRhawK$-FTI=_1z3u&Us>?Lm>Pgl(iza=SM9AfvOe&D-x|<{vi+i_})KyM2}l^Jf%O z`la$!IZ)=ffW-_Kg%(CRv_}%mz|V-N73%@+>sZMP(u-LuNUb}42vP1j5v;94sROaZJ7Qwa?mg3sUKc8xugQrkAEel21u zx-Xj_yJ9y`aT?;^Oljr)9tNl?Pwzk?YRc?~ij3y~+c=6fGdTlv(}L*xPYx^IwnWU0 zqU&(P462jC6epv`r^(x!CU(U#b}e(jkm|Sd0i`AmEJ{V)3qsaBqehfM8xu2|n;GmETZU5@UaL%RA zeh|S9b1~iw!z|+O@L%ey6p0Zl&Z>w3<>DJmEMP=|NAoxuApW~XL*?h$Ka(4)Q*`02 zVBZ$Gyo+zhJN5^w*xBj2Ubvf1y}K2^GcCzvrIAoo_2J*LTU%z$HMZaCR;}o#P#F!z zf=^l=#lh%fYn0z$dL4Q?8b+jtR7J!7H|(wo(<&IV!1R4{+g~AMbUbr=9&sqI6f*XA zuyZi{G2_k>`mZ^@4!&20HSm+{fn-kTIfCVJ_$cf_}?8!!d>IME-$^pJ~#hJQ?e>TXz68Mvm$F!@-w zji)L!%rP)E?`!sLlbZMa&P-8ct98IgY9rhe>K)A;3x1m``x?%ndXe+X0>vWRgdA$q zNWN6c-CaF8Ai?`YTL=9B26z{fx>V z!RPcW4&aGzp1FP}kYnEn;D4oDo_O4>-rqAel>TLOv?h6RbfdH(m;6*{P}R*}Lw$9i z@iGmfvRD1qC%3kaynB<-5gMpTvCqDJoW1<)C7Z2>nToOV4EZ=cCgKBF-P}~G`sID~ z;}S<9*@M~0xygY%(BbKDoA$Y>{NltL-tbo)+^u8J*<>MACwl`bRsYBw$S$8#v$Vdu`x23))ayn~) zuRl?`c2Ez@UrN{pb%3 zP*!0cQ!!q~!n+Y3f2kYK2%=wj(9v$MKBi; z@N^XGhtFwC#;>SsQE%~Eus8f!XH1KfdS3UOwEKV1Z%ZCrNyii6TXfKtj@lMz>X#*T zkm&4G)m%c%ztounH3-qQsFTu>nI^{hJJAL^Z~CG$7K}_~#Ri0Q&yV2=O&x{v$U$sq zr%$g@x6WsrTgg*`?$P=vfkHm(?A{@+(XqwPby%y}%xTQkK?$Li%1Mw-$cv|NpK=s$ zi@8mXGk1HbXAlMc(u&CZOFzNkX5t#+Vj59!C-xgl4+XLqF?_E)H*PrEFMfOm>8BXSb|M- z2Ll&1txj10#K9HTQI-JoLtqqmphVWl^4rd(Hx=aFf(h2Y~v7NBB@8?SxDhWz9yBuq(1Vsa9xxX^0O4NqK<;D zONkV>M#wG>FM%HP65db~0UFpuyahBQK31=A1yyikGUouEHlq5$zEb$NasMY!|p=LCyXYoFx!F-)QK1dh$ff0#eLRo^cTK8{MW;p9g7gcLN4>h2Ce+OUUF0OZ{HAi;^PIHTYl2RlE zzXe=%O=c9=C+c_lxU*7yajwZlAJ@|!7)s^vNbpUBCs6N|v8Y)}=`TG%8 L7c6Vxo(cZ}ZPM5= literal 0 HcmV?d00001 diff --git a/doc/html/user_21-52.html b/doc/html/user_21-52.html new file mode 100644 index 0000000..024f028 --- /dev/null +++ b/doc/html/user_21-52.html @@ -0,0 +1,23 @@ + + + + + + + + + + + + + +
+

2PC/MS-DOS, DR DOS, OS/2, Windows 95, Windows NT, 386BSD, SCO UNIX, Unixware,

+ + diff --git a/doc/html/user_21-520.html b/doc/html/user_21-520.html new file mode 100644 index 0000000..5b0d815 --- /dev/null +++ b/doc/html/user_21-520.html @@ -0,0 +1,27 @@ + + + + + + + + + + + + + +
+

23So you should be very suspicious if the operating system requires any specific configuration or even drivers + to use the disk it is booted from. Since there is a general trend to use optimized drivers to fully exploit the + hardware capabilities (e.g. non-blocking disk access), booting systems from the second disk may become increasingly + difficult.

+ diff --git a/doc/html/user_21-520x.png b/doc/html/user_21-520x.png new file mode 100644 index 0000000000000000000000000000000000000000..27ce36ead5ac9b8b1b8479da5305e5a6835bfb74 GIT binary patch literal 13708 zcmbumbyQT}7dDOv0!ky@QqmnFAtelr^w11Fl+rETB@L3&F!T^ZcY_i`my|Fx5>o!~ zqkMnwTJN9lth;9JojY^xK0BU$&e_iiS5=n9dP?>b2?+@cASe9}2?-5yf1Zl|`2IcY zHfrzwLsC^yL+1DI-}k5gFRzf73bptDCv<+Ntd7K!HtHH)hHIhGyd?eNQ2C8biNET4 z4fF>R5)BeST0+D9(SBxRKp9Iy@U&HnH1Fwn)Zy>a+Fj(lZ}g0=Zk`w4KQD(P%N+Y_ zy~(fHYY0AWU{>@2d_}S@z4||GxW(;v4eDFsi7gd~BTxF-5Gz z=!YZeTQT&Z_*_nz9(##_iXGx|5i!z2_F4l(jEf)@fVhYzTTA}n5nmLB$-`VVa|?oW+$Ze;>mK+t zkNzB&0>~B+M9)i6Dy8}=_=y|mPkTbn%BVmYN4`|udJ;XsC2PYIP&9ul5HZ3cLLA4= zKp)Kc?j-J?^ljN6NjPuBqal%}QVdzuaHfW>%CVr8YPhEOuCpt=;}pATC}_8@kqXaB^t>kTR{00TgSi!a#9ZD=eK7rL#H*W;6c*%-F(FTc#L% zaVf#|S=Q49vpXuyvy+M;X9Z<-N}JQ39ON(eB-|u>Po@RXiHOA89@6*%HtZ^jXlG1*L|GH6HFstyU{mEHUh8vZDfkCk039N4YVsHIu= z)DunfQ8Du_x=pi2-ybFX(Zd3YnJt#WQ}SdZvmTrJ%6O*kqQ#j{P$B%<)CP0b@whWeh1=_|lQyv}IFNx>2s3o~$4dwh6$hIur77!3KE9{b)Qg1u27W`by z(j|+yLi235Y`LOzH7@bdlxs;8?SF=+@o&Jm%wy$-1y?{P-dniXa3ipq3yT7D*|^TL zbP=Vqb?~(&7d>s^izwMqi6~t#H3>q3g~YWgapkEV+_S?=r{InV{X`MOx#`^6MOFDE zqqZL(nxl5f2j2hlP`Ibkbj3K!4Gbek>)8h2pSuZ#eAEMzWaWwumJ8S#k*|!W>mqJS zrEEu{y1fUfxBT_ebPS)FD7k~WRVej}v^Z0N)o|XV zCni{{NO}^_V$FFKT-0{a3{q?F^{A=UVQJg_4ojEesUx?|nFSherztUKDoa1zDXxWp zP8P)SSJ<%=_G5P5)6(~B3}&!f4KO>-l+^r@HNIq~WpLzJ$+DUzY9J5Al%2JR)PKSG z1{n>n1f&4ZLeuw4OJ~o`Te7N5$KKc_51~H<`+H>5>UOb_KDd$5A}_;$ zne>&_ZJLPUgSaayIWGlgQYp(u(174Hzm6QktX$p)2Sp>WGAB# zEy98I^S+`YCXjWGg36Sx&kvyLg)!CSm7|}!-MhB*v=@-wh=>uR$pEQZnP5_Ts%2$O+P{AK&u zBCz|ysZyDyH&gRjY$Cs6nIfp$F>+ytY`GXrVkhnm8+#%7d({{pbVAd2!i0xFRtICT z(|nH*74L0j@($U-rRJ!>)Bk32Q$M|nxH@6`r+V*4kN90TnG<@A&&O$q@C$Xd96Hgv zRLh2$`4L4T6yG4E7 zHXIsm57hn@x;_0P*=rKmTOzQgX$=Ce9yejs9%3>$4b(0oavJv#@`g=(14;>$LnDv( zXz}q7Ca#9>!1C2_)WU8{IFMg2rR!fq^haeFJ=IVhFy-a$EE&OARaou))rZf=x%E^c zrz%_n_BJk<)ThA%w{YQpIkF~CQoV)5))>eav;SGhFZ82mL&!G*u)%t#qt*~v#U7t1 zcF0_xx}8rU7J=_^wp6Y8>@f zehOD*vDEe7t%Q$kL!euIyDk+^RgR8X|Aial*Uu)9&|}Zmd4yqTj%qGHN?|*4Ry{oZ zb-%**nlrM;|D?K^M9DghppAif(u+C=r=vrvdjY#uo;C2Z$D{NOwtEx7q65EoEKE25 zN^{5MpPLXZ1NyP1z>9c?*ikbj!<$DVno_Uy`FS)tX9;{0rjit~*~vhSrE55Yr8P5r_~rsvfj}SUSP4Nm2>oUBF9>sA49NXJ_J{!sSW! zW?bu3$O|7Vp+b+eLXo=G*S$(4CVE12P;P=?X+cU-mMY_>95aw(G8A9^PWEhMEHlcl z7c>J*jqGLB{qFtc9!1_}1uFb#R?r;e{XnWW9+Z5PXJ`F$r3cu3E61S5pXELba{6uC ztd3Dq`p%$kGekLD(U;+$`Bx;66e>fjLmGC416dJl&0PcG{QwsuQB8@ck~;wG8P!u9 z9jK^`gHJ}J9X%^!)8FzYamaw<)rSi63lzY~{@f{Ve z)f%O6;3n7vdAfmbq>60U+dlFOwBFgqQDsp2>@9c6EStlyR#XLW`kieBg(Cc_;%g6Z z__^T3F0AfR7GyJCSWKy6!0cb9@b`;&!A~kGG?_-!#jESt2%pJL=@LPp zcZx_uJ-`)0SQUJLgLN?X6j#g|^1CE!aOiIqQbY;(rZ~F0R1MWd{PZaU%IZ5-y+k*(nPCcy}VpA2FzDs|NK6 z)?C9PatYNgxt=T_9Ro3=8Y?xHs~F*gL+yQ(gg&L5c)jqpFlb8hGGHA4H$X{pCC>9A?z7J7MI`#dE`fd@5E52O7kj!L~o|9oVlO{E7Ou=8^LX74NeRwM8HDWCd8sgaX$ExXB33B7%K$Gn{Vco+_vCvT~` zpAc5m5A;(5v6Z*VzTw*vfyDtT7lCP9qn-`>&bCY0RgkWl`|ga&>x!Z$Hh7LFU;ft@ zx=<$l=%rYDX2#+`VR@wkzQ7IrtbUTA^eu;FR z|FcK$sJulV#X!{iY#?XUO~1A$Wi(fou+Ka9Y1wIgafqX{QYm}rReS(7%S}>tVJ8%7 zee;Tk5M3tKVOoa|3sJ0;?91D{g68%_qa8nM6 zUgQCV?c0I@n5h*fVHPjw14S%0r;^(DY^|}x-TDy+9CqJ;iyHQrt+MnX0!#M%f5rNgl|*wE%0hr=f?19?u`5>(h}NZ3p!R`1&gESEN%fqcz+to4wR*06 zoL-2D*^oStcTy{a{Zhz*SLIpp9yAup;hBq;yUl7 zyjz)AX91}$%MSAVJigQH(T(l%$jb^_i31YsDX3GKog!fuQ~Sgo*NmJ{io{f(@Q@0TU&uruwxzi~hd?(eU81&QkmUMiF_fqtSt zr(Y&O_Avq>Qr)Zp+T|{j(evbEAa3d$Tb7J3Z_RZ_wr$gS&Y8z&(GC}U7k3E0E0u_o z(Iz8lkxB6^aT;)Le=q0Iu1oh7?{`FNQ$2eUq=#}KYC6Y1AfrVjOdFCBv$t_jEyuPz z_TKE|<_&KNxpNZ+z>^c%t>tG~ij{WT;4%IevgB|1+cRUDzy#499`$)vn{CDPp(f4Q z1E>E?(E84LX-|y(XzQ%@HN%N#iB{J3=P4uR!Sb_@gD4y4kEt~rq994>DG35ZEe)1Q zwxQzMcHy!PomLu|?S`8=Ou9T5cpGRC0#@XTXIcCONoWj7_S!dUfCCfxyfi?N z`0TwmxFAt0HGhqkCl(; zZnBK2fpv+_-d=|#pkhS(t!~t%OET8Uc(qCUDj_)fphTSEEafQSYNu>j3dTW3%;NiV zEKry|{G4rJ5!)pTAse%|mE8>-9-?Z^#GZ)9!v{zEH|%v)%w**YV^zEQLK)%AuQ%}{ zd+Z|=v#7&1m^j*0^9+AkYbAVM>`}Z@y|AyC;n)KZvx_a7w&b~vl^5Ns+8vp$c~OB2 z)u6U1Ab@$zBtS{ht;twR19hbQEdS09V4t%v1#CE2UGg<85xHgJcgS@GfO3Z$+}{ea z9keKjjP;immlj-w4+f*~zS1IAr@5+Z2o;b%kv8v#G;^E?DSU18z{AdXsKwsjhQziPK z7_74?BUzj=-E%fItT}YV2>%T5z=x`}y$y#Z|HhM)p`mV{Q|x;T&NNl4D%{V%l|ol{ zh&MV4c^63(Z3uQ~n#atEOK-Ty5{`KC+xMjc=0MGrJGj;8s1$1NLiOH`azkrjwvX+* zF+IvnVk-vhd^-?rD!j`AV!k)Od-&Tamefu$+!$Y<(+{!!{k3_ySL^xLV{Yu3?JqB6 zIe5}AQb?WCSh}-&UsS79ri+MwtuZ$RlZf0pSIR#j&6RHLnJ6Eio~nvsq~tG#(5BQB zgd}hPy;Iv7%3bA$-o8r$ZEqJmO;wc`G z{G_|Xs8Y_4{b6y2+bkhlcW^}2X1V2aT{R7b3QJ3xDtXx{7L|iW+4tY*a~k4h1Nm*! zPYDx*^>ULJVIi5-TF2$N&rq>~hiv4^=zwqelcU*u-0UHOufGBhboLQt z6(1u8Yc&48Wzi#CKsrNs@NeYGtf$QqmQ4A`6;LCMiew|AN4s&MFn>CE49^hmK*4I3 zxWpnd`u>Ka_uAb&g!#`1j}`Q;*oTg5D{Ozbu<8^(v&KOo*a()!YH^}mS*}KD_JP2^ zk?+TPC(fa|g;Z9-n^7x)h&`0DZ_?eT(q)$dHlW6$*%N!yNV@SR{SOpROEY=aikO< zx7H+IV?oaKIu00ugj_aK0U3OTmW~zqHlG3z`(hQda8zX}&if1>a;d8&N5mhIlL6pV z`y^=gg8cAh1J>uku!)LDBBQ#tAw`zm&QIwSs9eKq#w`H@rcdGbSvdx{fq^6YQnc4A zS{|o}-7@b!BhSC>6`H+z^Y7UUPl#qUC^2iT#6;q z_PxLKvRzVOT7^(QkruOcEMV%>HHcb)*)#ern)R6K7&17{PQ3H;~I(nJG7|G*B8ab8j zW20XJ@@Dc0_iuTt`ZG7C$@{dtyfEAlR{S@tzms*vy7(FFX#B5v0`}wtWE-#VY@@`@b z!wk9ow^i*jV!xtAmB@%ElA$Kqg_LJ$c&TJy*Q+uAsQqP}emM`L*g%H8KIU~zQVKC@ zvA{(i_GFUe{>b@*&??*`{?H4=CBM0Eu?9)kZXO)y1E997xOisR0M~t=r1TQ(zS*Zw zrti0#h3RGmgNEpyi|BGb9(?9IX3C-5H+7<~E=I6I_hB}m!%^nZiET$hB=6A^*2RG0 z*PFf?8c7w>#%{lh>zmXp;5vfU4;ic~xai`mKNqop zIE`4sl9p@Wmv-!Grn$T-6#$csz+x{{zjvSA`EVW)IO4y-*S1`abf+xyRuBZhI&^OJB=!@Z=lKE;>)5 z#J`1-*BD`HqhmEAa#5?DAcRlAArMS?1*!+uW&XBEe45``?h?CWJN^ZPpeSSJRy{Bu z(zDs&U0Vahj0G{lh3Qk2!txtwSlGi>{w}PF1%F)Zt=*+Q-z(@oQ&zi>bL?P8w#oscm?5CqTl;Q z&8xIojp9)LNcWx9yRNf2LyKfISmLZezRmU1vaV;g+9Jt9Xt@SEATUM!C)<~OPb$@i@bLG*;XHx9$@&b4wDBA9Mp7alzO#`V4Dsj8XXsdT+pFs*0l zjs+g4tW`JLE(ck#dS1h>?*cw}|Ez_|u;eSLJ+Hl5mhs^0m)uq|RQ@p~hd$qk)eaeq z7n@Pc7+dzae@tb}r`Jt`Eo5W8PSSM`&9XcgL9SJW$Dvu*(qOy5LylH&@o=hhjm)kM zYXOny?C%>3&mFeyV)>fZ6!L$+_%_CSI%peyT)B4>gd2Qaouz-llyTSKd?L}n8NCB$W{->XCf|ak$)sk!Fp@< z-ahM0>t_}(BUtSX%c`15ESRidkScXJ2b(d4X>y%#x={T@=}rr1x~ai(es`f-Qj&kY zBejQu*s9)U|50&h9x052-7jY5Kl}nk6=we9MNB9fzN%3L>hb@0apn%c6tv~nx z8rS^ZQ*@f`c+WWgE&)e;0_exYWxEt=sTbbAX-SE!V(&8Te_T2YbjwGySr-7o@GCfz zlXG9B-Ayh{q00M6O{FEYs<4P~{a>2dBfKhYyQ#CS$dM>X2*aRhFK0O#?3U?Hh}I|t zs%#M~Pf;W;qunMHj8mCfhD4Z2fwt1$mXZ5SRlA4LP=FNcln|q@I6%vmMXh(8dWG#Z za)feLbtRo)1Fq4=7Ljf(%xf)Ql0|kXk`(KGIu9VG(&~}=<0R~)faj6N%6vO%!hEhS z6X_u~wtndhL!8>A)bJ(3;dix8K4e9f(zy%ikDrx9!VRR;%PfBt7VW8)m)v+L%mSK` z%UkJN)!a8fp=Z(}g}0i#opS^)q9~k4L{kDky|%J5(A*U^?0xw-P%JV_4{;E&za}~) zhpPIESWHC|c*BH`E+}}ozjjm349bqnj#`UZBUax-sy@vH70pCJxeDLO@1X*7Wd}AI zjA%T`(>cr!7hJ*bNwr*AxQZ_o#D2q|$-RIq3?!uIvwye%fFCm=@*sj2?lEwtk6XvU zgP`4Yf#Zd;;{zToFX{R*qsXO3JBJq)KmB^-|+>DVb78;#t z+s5h>(m(d~l9HWEWQ{N6X*BhO_~6$*-Y2A3AKf|66JO}Hl3rH}so|67`c-f!VlR`Z zy3LfpSQh!630q97r6)yz2=oCmY17<<6x#xl$EUpU8gi(#b|Y4qotZMJ)Ti`K*5);; z1eJ-&MJTPN30Z}W@`5fFSYHZOZu>DOP<_pev#WM%wZT~Yl1KP5vZ93ZlGx>2$90q; zC~*AbKGyx^qWHBlg)TBqLo|Sc95d6K!UD{zMey!foJkJE1xogWs88EF(26OR+L1YU zM)Y3enc&BoD`Lv3);HVk$j4hD*(o}F6jBq3fNY&+sgb3Tl|{;y;Nvo^87=qX4dO7v z^W%5tZFUVr?FWW1bP$8s+VK6lkn5bd_NNNq$7;wpV3U&kG}l>O~hz=~n( z_JEz#1z3s&@fF91r<)+=N)J0(>cI6SSwZS(e5IpOPPl$czx$BT3`jd->%(|!33{s! zI6q%O6nPj+^m1FEeVGL?l%!bu_*L$5B*99@4tHX_Af{q|8Mq=W__GFEDOk{3u)Ht; zL9Xzekp6OZenK+%$A+$1BcoP?g$wsP)4am`=zH%rE{CMk3qE3emhMp?O%Qn;q2xJl zon+5224;D6_yh|7P5}7Pu_!N;-OYxA-6E~2@uGloLnUBZzkR4AZQIfT*3^p zG1FG-Q*k9^qF=ic&wYR;IUgTa`_c*1ym+VlQE^F*>9)uaCwlVjqz%bzTeGn~v<^<< zY;-(P{Fbx?$>yXqSMqY47#|%j+}f7kn9rP0ob+1y2NIxPxmnwGZ3-Cr%xrnEuq`^W z-@L^c&zH91HqUPg*k7bHIq~(D-<`96T~FOHy}5;7$=+q3J7>9M#97hTtKdti(OwhO zcQ4_U@OpIL06!E|R>zROqMh4U9vF!n{z~F)b5eQ`U?=D0SVmeGJNJDNWweBTkTJ~y z?So`1aU=_sMgNw(FcjWta?AnFywR6sRsh>!z37#qp6pQokXUWv^E2GLYS`nPL7*Na zDq|4ei~Co<>$;iv&xcO9c|lU?JO3iu&^U()$nCp_Cp+!lAC!njv}nXJH4tBtLorz8vJ$4yzcdmHv$CC5`dMSzNfJc9y6;IqVB|a{wm(w? zY!;cCs#5#*yp+zsjg-|!{O2HrZxXEC+-;4uYdQ%+{rZuLS%rh3H_wVYwz3SpeA)0~ z4_y_z^h9YB^}(u!c2XMlNQnS`#Krd?8ScKelkp`*hE6g!ev(CH6jvr3?eUM&Xf&DKR%T z^M3}9P=X$X=wEj%0M<1R1l}i+h9vd6@5?S`Ek@QPTM5gzLY|c_ou-2c{XuKL=73$3 zKM0X%Cwxl>hEsY9$2W9O^WVH+b2bn9iYRDiwQ}=_E`GwdLHrWEBdMtyBT9J*6{n3| z9=>jHv|H&v)MGcG-csNl;)Z@dEk<7O^y)G5a%7EL-f0`jt!`8I^I+ z;5FoL2h@j;avc^>w|UNuf?h%?H%mLlKjNU5!96Pj1b%7Q1HmOlBxWOe`6fkBU)ygk z!}E1P*}v{$hJns!MRlOHAbKg^UK&VLOOK(SOWU?pcdY{jyRAi zhmP&;ux<6M4mvm;HmX=$eKJE!AL>{3odG-MJVl_kIGs<+x2kU?UN~J1=1+R90Lf?C znKlG2VlcWEMnq1PP<+o#Jyi$2ZCzwra;-MU40l=Ea8A6{e!`&3Wvd<{!w2tfcNY1s zj%LAH2(k69faX0O4OGkEVD%Es*<4}F$Nj@>ovibgW ziu1HAQ0@i>?IZB_d77N^zGte<6RFjBGnJuNVKm?@s`y0|6qa(4(fh$}vrA@EOe`Rt16{Q?1bN=}GV)bRi zp_`nQqfoz4elRNE+DuhZq8aQb zOW~lhT>h6IM6Wiciz&*`^Iz1#KX&|OG&+*_t38RE#^@tdUvoEqYO!tE6#^Y|WwvrS zH|}PG7Vq;3}P1``F6)Ps}y(ATBw91%5DO8S~JD`Y`>C2k@oOjNvX6Qs3kdA>k?mYt(i9>!(l-n1yF*WA z8i*@-??Z@GQ+-{FQO^%%A%+Xfa$j~VcTpkmFCV7b4tT2IXuE7~H4zOS?L8du3jUS+ zRx|uc7ZuHCnvBx`u?KZetVthq0&8$V;oMKkx{i+K0=K%Iz9+K|8P}5Dg5i^5+S02^PY9I?pelbTE*y%$*J2VRalN8E9YCUGqg3)2?SB< z!oydU=a!m>^Z3Z!C3cG#)q)WXSiE-RT-<#+&Jp^uwYo^p*lX z-UlvM3jXCwaP;V+HKe_+iTU$ij-58X&=l~(L0P7u<~POzO(d@4b4M=RlOtXBUy=F^ zawu*NR1AeK_<>VK{D&AO+4x-P-|EHxeg6^(Oew&5-35I2Q2V~IKo+-$puPXXoJ*{o zVKB?tJ9cdJPjni8rP#EUu(v)2@*Xv4LiMho|54OZ2`-PTp&o@q1wRr%%X}g){!%9% zF&*i`VPk7gg8ctc9^{PQu9ASUs400u4YYT&^Ti3-KYMN1p|(%f29}3P9nyYIz&zT= z6M1i9EBd*a`NPYeUxE)^zVSfr*8#itQSODN$qj4B^ zmCp$g#v#(ZpVwq>YGuzbVORYAaA>ylcbz7xgBA`8@{uVvwl^t2gEl2V`{vwLjqUZz zp_!B34ezpvVOq#sJ8@TK1 z7f&RKANm#7p?0V@e7fyhd>kaq%I&F)^>Z&L6nY@rqPf3y6OeYYWx*&SEeVW8!F(Vj z^kY!))Q|1v*;W>-D45lYb!Efc{XPy5rwHP@ewZ@81+d`_7q& zb}!jKdt9HohdY!>KloWSjfJ9}Rl*mqex7 zrb8X3>+GM7Md6ehgxZVO_J9AmQykc?cW0>>J7$#(9Y1BhI;?>M@A9$#N08=48DgXM zg2MT!wx}+C3R5ot^Ra@3LpT=BMH*roh9G)~)_}3~CJDfw)OeC3WQ9~onHo$rW&n3f zDgA^tU7=^tncdGvu*`2aZLyC!)-qIv{-$aqjjpS9zn*=*1;XXQ_4?!EvHC7fRPper z65A*U)O(m}xZ%Ym=RekqE&fLt2!{=1x_{&S7OYW=r#FUa;EW-G-@sJrFvJC%xlgEJ z*oUX3A*ydQpCj>P{dE*nc=TR1PbMoe{v^6-KBJlL)fZ~+Z&uSD=Mfo&uU)Fih7ktX@2`i-Oq?~IbzD@$P0JbB-md|VV09nd z52mMXt4tuZ1_4iWm!7OlTR==K3?9$gVTD7LL3uLKziLXu;Pbo);SUn@l8oR?svP6n z={06PP$DG+x`}S9$bI)fr^`Tb-o5tjodu4}`Gdf`HNq6VssuITCi$>}VFU1Od5#3D z#{FVPHNPTV0CwyqL8yuCJ~vN!4AFEsw4=DvE*1M|1n*lRbc`E4l=LuAbcIAO1L`^| z{rbs2Aa0a>6HSgukj2q0&^bg&DG+;zR=Ys{=0A5t(tlsH;Xub9(7O5yv75a#C`uXl$@}p60%h> zM}(8b^bf@u;@q^M=s(c0W2U4>evkaqJX2b9HYP?Nbf8CGUn5|xB)ChkO#)7*N zpFDna_K6+vCvC!VyX^d6eBGq6(;!TEP^^i1V&OFZ+Cb_}OV!9Dyr4uWZY>x7tkAhf zg{uo~rG*JPid5!w=5(9=6oz-SEzCjx;HfRR0|xblS{az1+gOZVSZ&?0uZ<`^kQYC7 z$m$~UqQE1*42modxz0#(RTaDhn*T+~zHkEBJA6Lc@_?O9DA-VVww{vB+lLlXksxQB z_9CUq|9x>Jdyjp;<3lX?|DwMy_dV~*Xwh9G^FML!H=5k1RXVIuo4*{g8`Jx&gy67s zstJ_FvCKV!6<`avnStItc6Vu2nmp?Tl`A3jlri@2-El?0qu4MHZYB zY#~}n+1gr1#Tb$NCzW5&pR6-BZN9}}W(whTr_O~g2SkS?ha8erU5D=9lZqChMD5E-MD5rGW$-)o>}=gGSPSIQ|hu3xmQGGRnZcL2zG+=pGf`($`F2`ui}sRU87LuRzdTs!&}0*ATk* zKAHEMCb)O=%AOm+FJsaixeuz~Ha#j7`mDrv4{Ucqlsu2t@Hr>R!rD#FYWSL5xr_hK zkria2OkTO%<$gnirZTuSRA};_5*d(JOdw9Pmb1scPPSOXV-GP)UnR5py4(c^ycFwb zU^fmq<|3yh)w6W(%RD0qd|=NbVU*(v^#He*puI+~o`X=kBXMI(k422{m*`o`pE|%8 z*~kx7QY?gG8SqUpfZtlG+K1%r+#~*Z*PRS^wx0}1fsJqyP|<$+qM z!gQ1gho$H`Jj5W4e + + + + + + + + + + + + +
+

24I.e. if the BIOS device code, the number of sectors, the number of heads and the partition start are specified. Note that + the number of cylinders may appear to vary if cylinders is absent and only some of the partition starts are + specified.

+ diff --git a/doc/html/user_21-521x.png b/doc/html/user_21-521x.png new file mode 100644 index 0000000000000000000000000000000000000000..f60dcb1652a2dd631dee523657548ac13250779a GIT binary patch literal 3658 zcma)9XH*jmuZB`UrcAK~WXO^wvy7H4l~VR7Wfu@A2=dC3EtI_qh$2g-uM8`csUjj} zZxIm6s>l=pWh$G?ckeyt{=NB;$}5C(TFsHmvPm%cxc z=28Rb=W{NNoSBi8{>8<`rThPv+w&#im*}g37ABTdcan#LJ@TyP*@QnR{C>Upd3ye` zTnplkj#UWtmP4eEoT;N`Ad9HWjpyL7A5{Hcv@*vSx?_5Maix~`{__kv0F%R^GLe{zuUR7ji?6A z;Jgi)y}gYY?DLP2pRs-^rXSqznZ;oVbcM7QYqdPY3@DScE!oR!7)B6 zY=hfaXGkW(hK%Sh)M}tCc2WH9pJqFEX(sGQs zv0!-`)4l`5b8lGoVmxZZk#(_3z!N1J5WuZ_;sg5!(! znmACrCT1k=-BVjVRmHa~iy(0_JU3gBw5T#A2ik+s?WBs_OHq#IIbrXlHId8V`c}{M zyg9vlbsVOCWs<6@C_9$cAPW~WuY>vILc?T^-4rM8(W&r+rAae<|DpKWgN6PD2hlH3 z=C>TrXl7#R&Bq_H#yzHk_9C#fj5#ni1iP*IA7U6JxKTG?aYMRU`SZtKl7&a2OS-p; zzVZ(~X%7fXVo{UP_N*$PRx1uOo@*^ZkNnnS9^h3!q)C?!va-Ys6)HCTlN@Ih6W00w z*3k3hoJ!BI5lYJiHMkta6S8AZrk#y%{1Rv-#Vam`By_LaDBydo-3ce}&EXFrukhwPl94p4{?Vot@O$n_Fe=2_15#^*vHa zm1yR>@x!Fx+DW*8ew|_fB`j8(8-Ik5*{IAe4fctW^NLyrLnw1-Ssyv(aAxk6D#mV9bR z758^Q%|e!D688(t*MLm3Jlfs6zZb!Lc?aXXK*o`V5U#Wt1m-%r06qMhD&DFIONSm3 zbr2kJqsC6Xz}!T*ruPBDIfzkVOP&x}%A&d4PgdQ|_L(m4BFA_;?QZ8+OI{JYiV|I+ zgnN1E-)B{amt0njh&6c!6VP^r8~Q^8?b=aSvh@Nx#qWIG4qO)Q`2P?{*hntWY-EQ zEU{{}@cPJ2fb(w8dYzFe)d$LJCc*LHAX-hu|TT8Wf1;+NzZ0UITL(R1SRGgcJbKEYz z$?W^t&4cY62R8-fNQ;nMdV-8RE@~_ogf5E$0{IBXZB3%^QPY{4tm#(YGd`bv>ifvF zVb>?D*DnEa2L+fN#S?B9WEw^e@nN9T)X53*MEB=iDhzI`+t2O4o&!jI4aIDK``iunn*mlt#N zgxZ+I0F`I7s9%wlRG&Ck7khaB7t#wrikdqaU$`v_F2U#0B3S0c!un{5W7{&t8YIRF zGQ23pX)Z)>nYH#F?nl+IS9w{AWMQ!D4p(_(r3horuc5_~tzXWDiyJI?u>>oFGB;so znzzX}{HY1B({dFk)-&C_RVnR2;ZV=K@}BNILqi#(77U1F|j z_McK;aHI`ZFv6K>W3+Sy=ENAzl2td;%W!EU3PXpXN=LAo_(`R~9HXx&o-W9}jrdU7H8pmuD;lMH&^#)2Db9X> zUZQ=a;!y4->t_Nogpfut!_<|1Q*k;XDGi?)In8Gm^3+9~u`Do6O1!*5zo9$0z#t;u z%*2aV;u^{gIVtFUMPaz^PA(z{Q`KfTtb#9J_zKXpo;^iBKWyTO8S&F;E}vmr*#i=H~^ zyurQ19pvB-Hc)k~#U7y}<+)R2XaFl^eH|gE`wA9kwK&*vx_m<&N;i$4iGDV&a3vUC zgirTM6ocJK_^B`fJMl7;{D@o23j4qoIZ$`?Zb}x@8Jg$%*!pQsLpWv0a`Q$0sDgAu z;5}pLsE|T15mBv-Ye1%k&?ZJjVNg_A$3NaF`QfK7*YFiI1+1gEW8z9S@C+xS}I?EqAi>D}Jh>T&%0%DaGR{ z$-f?KR5l7eTxm^`<0LH}$s}fNvBhz2reOYkd9`T2seqq%9RC=%dMEu@@-hkVy3jJE zD#{@-QUJf!;Sj=p-z4Jut@b^8;lALwDOL3I?H+!vg!Bv;yxY{uSy{bDk`S`~b;dX# zVDRFv@gkz>cNQ}O2LYAOKY;_!js4!Lm zX=JXG?eYoq{pvpG0X5$~VMqdIfvm)rFpdVr>SGG@)q2bFsj&w{h7t>J?ZHzy?YRLX zU4T84oky#J2sJ?uU{7NQ-?&0N9Wd$u*xOF1+nUC{>5sqAg7zY87yors`_DUw&^NhL Iql>})7cJn>hyVZp literal 0 HcmV?d00001 diff --git a/doc/html/user_21-522.html b/doc/html/user_21-522.html new file mode 100644 index 0000000..e312d4c --- /dev/null +++ b/doc/html/user_21-522.html @@ -0,0 +1,26 @@ + + + + + + + + + + + + + +
+

25The current mechanism isn’t perfect, because it sits on top of the scan code to character code translation performed by the + BIOS. This means that key combinations that don’t produce any useful character on the US keyboard will be ignored by LILO. + The advantage of this approach is its simplicity.

+ + diff --git a/doc/html/user_21-522x.png b/doc/html/user_21-522x.png new file mode 100644 index 0000000000000000000000000000000000000000..d9ad026803141d9d51099ea125ca5776ff195c7a GIT binary patch literal 6291 zcmb7JWmwd~x28Lm{?REVwX}dpibzXH%d&JYAt55WNH5(XARvths37ewEFd5t5(+M{ zl#&Y~DO|k&dq3QdcRtLV^US<+&YYR|nKREMni}iTQgKib5D?Jn-_v>TlGpSC;d+2yl;_zW$4=S$_l`s^di*{2F^WzW=WjKcjZ z8*S%-I~(O$f2PJBDyV(jaldnWX^!<~(n@$J*X6`(2nSL9;y{e%ERwN-@TXFjT;u@aYk`+zI$z)T-$DKCco2!aLu_x7UAn3#6@%`pSE- zPCqW~Su>MMp38DuzOCFM+t+US=TV3D(4Ol@zoH-8e+n=#YBp6h97k8cZCe7i(fD(# zR>joPBi`6d=B|i zqwHb0Wv7ghN#$qerqQ)BjUJ$3@i22AI#+nY2q|jz&XjVbrxK-{U=Ji_@1XM@FjjKq zLTmm2N$`a|;s?;K&!uN(Y>XU^XIcxUZ>Qkc&SDj{v~5~PJ`s;lVdjuu>KpAgiO{K% z1HSbYFBAdjp@iR}84$yr!U}-NB&l$}dZNMlXwuRW%X?)V?*dq2P9~)iyXWmb@U{iy zim^=)DfcdM0MRh|M+h$!Go4~1jm?giz1@ohtC7p9^lFWkbuSyfxvs%oNufS-)(gv@ zVyh=xCB&7{13TgVKcB1v^)TcHIBdJ?)BQFfWQ>`Xyz?jyc-5(-v1I#J-hRY?F0%uN zr{*LCMuHUVL59=~4A03MNQvunIcO`A72bd0naa2293)+MRr#_(l3wDb8_sg0>esW$wGW>RSIuTXw9gEG_Bm$c@XY9OS%3z0}>< zU&Q=4xp{EJMxX7lfdAred;fgXt-Cy7gV8YLgRs6#MVTtS_p<~mxr5w49H$Q#8cf1A z`^uKk(el~vcHq{U91}EC7)BYXW$~t7U$HjsA2)Vaj_sQ^I(PT9rxnJ@N}HA!{JyjD zdXyZYl;hacFG}jCsp^*LCm1B}cZB=`UKNq6VS0H%%8Z+Pv|Tcy{$Xi6EVyqQ)|78B2d(+op(z*_re)t(#$a zaMSk|gveF|fK>{!b#2p=OFPpEt#Da0mkgUJ^_T=oQNryMDE6`vZgt2c^9$dnwzj)R z2WwGwY+?^KQ2El?c>l4syJh`bwg=AMo_UMqLdUF4OZEU;2=SiXlI@E;ZovRqWaw{+ z`b-KJ3!VRvlF1lywRL{2%zL;{QrU zAn4pgbkzMv-u_%y3WiW2#+1)Sm)80r6Vj4X_GN&-ax#r+t<+VCZpE*txU|Ens^T3-w7X-_V4Fn zC7IHmd-AdVg@gdYVlt!dQ^khV%dZlS1Tml2p)UKehgF^M-@kVhdIKuIf%5U2Eb-cN z6!Q3TVPE<1K8UO-cf``zHxlw<(gP!`aY&`u#QMm&<2-2KZCSw`r?wi`{xIh@`D#yD zi$)~V$B{-_B;)}ZtpCF!s==LC;k27Si7*-@(d@F(UrixKMdcS?GHaq`a(kM2r_!~+ zl3^<)Zrj7mOwbJ7v!rRR4Z?x;8|21MNBgXo6M&nFh;@YqCkc3#+m;Yg-;j|7gmG4{ zQ>2|Vqz=p>sK6Q_by>lz&T*+oK&kmurD%!LzPo{MS$Q2+9Znl&KP9;SS$}DC0+R-v z=rn`7su#NdVlQ9~!*dfJI{7GW3?+otoMck#5ciPVYNE0VzEKp;I!y|4MF|{%lsVlz zs9)Yu)(6bFJ*gxP&E9z?xY_RiwKmxalbIRQj88(!`gt9Oyw3;%yNiha^VIq};z2*U z$q+syl+Zc>{cD3>?`avTV%J{mD+^8oYNzjErqr&3@rT6ABxhT{2!=u}BY%k|ZL-B(N+_ZhJ#a~U2epU`ZL8nuC=|9 z+lSYKt+H>l(J~>Y|5|SvwP5BWF5|XSmuCNHW#*GHYRvR~AuRt*bp8|pt1qdK#R_e$ zMJhcCk_+WxB;>?_5*OCJt}};6w9R2pbEywpi<{=HpDj!{vz_7GiPEh+O`g1aVlU9C&oG1P|;j`ZS>=C zDh^}4f8M_;TM=7Xf%?La@jJ(fvyb`lbcR&hD(?Q`(d>A@Qu&DuPQ?YF=|=^-2C00N zwRh}f;uF$GkcycYj2?eQ8!l_njeX@wWP`UM>0aaDJFM=trSO_n##J~IPQwPN6;CNk zRU_K^c8P>Ca|G#13+4FHDB|AxQe+wGpr-MR3X@2s?i$UB3&5#17@2nY5Tx{(-xccz z>dV-#ue4F#AczFzTN($>J2L~`qLfgGqOSOT%XD#iOEHAnz7v;_0skrIB}er55akW_ zCXe^YviB)J7^VWc12wF~rbFAm-0ChKp6gA2HPk8;nh^i>KDPWpLxw@IuE6u0+&XfI zL}HPELZ$e<9Qvca7})dUBWNE&Q%9t)*i?(x{6k5)e2s8xil9m<%LrlY=xaYr=nAW! zlFX8BDxb#FbbCs34*3^c%Z%=L5K9`>>*>PD-w@JhydKRyglj7NAzC5L^rO8j$)6qF zTh0U&#L!!aQ*`hoMJ8I%Dnu?8ynRQiCja&YrQAm>jUjB=^fZZ^p@MP@o_GwouDLKFoh&CTmlB-V7QMDrM14T224rkUu@<^tLYB zEPpON$ipnCR@!RWw=74HQ-+L{dHRO8W`>(Qj1BV4{QAH_u~jnkTmboqv&30PZT+2u zseGpUlY_wm;x#`KK0*M+ssu10g&kc%GP^Vce zgyfhR{1R{Aj<4p6Q>t5LV>)!yi6rncI(TesdMX*W<^*ju~R4@Yp`sZ7}nNlu-jgAJAj+Y}K+9y|1l_v8sSl}eY-`il7o;|C~R z#2lEpi>1XcF4QvqE~(^r1;r$0leVmMh}4qx73+ZPhHs@3yMCj#+<6KN*2Fdk1c7j1 z;;-+^1GgZ_o(x0T__|11-*|Jqq#vk$W`FNNxCJo*j;|+`9LHy)Xa_;MGe0>$i#a_n z_nD`%b}TF+25yqkC$a0US!k+G_k{i6JZZ`vx~0`RE7d2GvK92~;l1tW1#P=86U5Bk z-{1t*{5N^1aP#>>b^Rj;+AI-heDYyTyW+ZJz?6+1oxn_AMctdQas=xvFzCcMTg_=o zYLrT}7kiCo75aydhqWK$l&!F=&zqSe>`?i&Y8Ff;ROrc{1TK7&EG%!^F~CcW_sM$T z$q5BE(nK*cgBC(KRTn`1%* zp%rYS`7Ja?fEn``A8ZKRlu8n)3bR!S75V3H8m#8{In2E!@*jFk)Gxm5Q-S(`bz5H3 zL*d>*_Lu!H%zW6~ADx_$|A71hD%+`q3Uh)Q`rxoP5`})<8_xckJ-bWa=W|)qZRC{5 zA8VKWLn&e1K{(=W9uf=*J{k+84lV(E3b9FwIpoe1e5#tJc3dY#8O>R;xtrnG@ z4}{(97yLE%)nZ^x~B#A5clAz2cP2*83Q(%nrg8}qb}8iYnNgE zgE|a*6WKI)q+jt1lt?O9)b|#A$$+JfqO*58sm@3tVrj>~7}mN`ClU6g@^!{Hg>uU) zPaiCIldL3ZHiZA$4nNG^+b}Z2#7|IwvL%cjgnB_LBrx_QD-~ z;$>gzHzeVagnpGy_gWi>d-Me!pZp{=bC z7VDN>N!*z%2h*h$MH4Eo_f+>;3509@6t2+aTwJhDo0Q>DYybAOR~F)4$5;momQ@b9 z%(nPDM_OKNQd6Nzm~86z50}#Jf_>=BYEyd=v(6V^AODK?T!3Cklm%^5BGZ;MO`?H( z2G#s^#3sKhi6>OdZ(>*OD9fa-oN-y8y;p|vK^}ol3rMu`Ki3G>nJpao^!=Gi0gvBN z_$+GZPc>1oNq&W{?D-wv&CcUi3rhGX!a)U-NiRwV{j8LwHT?~~g%0M__eZnTvwr*@ zHW3Tsn%zj?aLk;pjzI~Yw4^f<4I4|%-2k)lSV~}OEnaZ9s~fgu{8r>-B!2ft;E`oj zHG&Bz`kKDd?R$4z-kZ3k*>!n(V_?KMsv{GiP7`N^mJvbe_?L&bWmr-b{5b5Ykmk-Qnt&$^6m?NZg+Zk+l@D`DitQ zUi*x|w|Ry6M$mf3DcQhlxAVuJKq4nO9EUAlxR4I^d3pYzh8lQcl`TnRG1Ukh2r7$- ze|}_fU+zCz53+er;f%lMvi^Q=66|XATQ?$KMMQM#sL1`}L$FjtEcn%n@t<|{Dg(v{ z*uwmJj5EI8Ydi+e{wd}6vHmA7FSG6VAR3>= zUFE#sEIF2GaAcauyQ~ix6JExd5{ejoT4p6_lHz&^UXRh*Ivu{Av(^IXUBzdaFV@T% zQSX-34ap3QrqD$MAq#HYcw3Sdj}uWf9LUFj(_tVlv1wfkMUFv~w_I}Ya(XOl32c-+ zcIGgP|Ek@*7MSvVx2?Lm{8b~%k|K~+HwZ1Twq&y(oqTJ;BYbk!E5u6le|!^$()4<2 z|54fx*v~L94|wyR75_F4YWNPU&w+Lt}DiWv$!}ReeWZ7&jI}0ryyVci?Gm%VWNAmo!nK3lVfUDx>c1$SYUw zU8(^0Xne_Ka(QdyfBTeW=yC^ur=m@1eGDzB17T3xlF95wDk6h`6mBE+SYfh2r$|(n zI@3n3lD5o@53}jJT9St?M4QTQNb+XwhR0fSfuY#up(t>ZiBQZvy#)bKcnmSQkSk4O z<;})77P&4B&|#{Y9&=mTroMg+DP(WyEV;Wx1)#$SOV)6K$bOq(&S|{Sp2@OpioPiW zPG`b3Z5$=Kfoc=x`(r2@W~xfQV{H*PZ3v-UrihW2c`Sti&1(P2R`}C$b{+8*Mfgx^ ze76GpUUh1-outo=n@-3qudv!x6Yt@0RvAa8R|H&Hvm%9>l>$8wE`Otu3NW@#15*3| zZ2;-YEp{iwDVSk^a63|=-Wzvki68wEE1|=37zpDb!aU{kC{EEi*XGE3yNQ7&IB#L< zc)0|jm0T~`iNAWSX76*C?puKz5hFW<+c^tr_fUkXPaK#Ao?;iS!|^&HvnA%>Oh-21 z@=4FurMkrneZE4~t+}k?ToD^My5>db2N~>F-OpRCVm_rH6>7|_rg50ZUM%eMRuI?S z+QMU$@^q@iGy7|j4i5a0D3rsvYpy7({$K3@*zxmFtC*z;r5NRXIoj{4jtkT5({D{O|+9i0Ee7^IFTv-hnqO38o$QJ$PP|Ob|O3{5%frFg3$j#n{Z8kX{q!$VlDSC%}}!=Y120KJ^bK`GcOz$%vO(C;lXB6oU$P z*FVw@vPwFKI2+C_I`ODTi!sd6LxGm`b@b;UZQzj5RcLqe7DQ;89@5axD~x&H!mM=V z`K=rLz85b6ZP2&C!e~Tv95V&qC}B{)A?RH2Ol{QN5>NvBG1ShcrRnPW&4Xle z5JeS|#fCq-o~mot<9lbsDuU6$=t}8pjWt8grKQiG163BB!}h%m${lA+llU-jCEil; y$h}WFM?^j%>&^#(05YV* + + + + + + + + + + + + +
+

26On some systems, only root can execute loadkeys. It is then necessary to run keytab-lilo.pl as root too.

+ + diff --git a/doc/html/user_21-524.html b/doc/html/user_21-524.html new file mode 100644 index 0000000..ca64239 --- /dev/null +++ b/doc/html/user_21-524.html @@ -0,0 +1,22 @@ + + + + + + + + + + + + + +
+

27E.g. /usr/src/lilo

+ diff --git a/doc/html/user_21-525.html b/doc/html/user_21-525.html new file mode 100644 index 0000000..2c1f266 --- /dev/null +++ b/doc/html/user_21-525.html @@ -0,0 +1,30 @@ + + + + + + + + + + + + + +
+

28Note that, while honoring TMPDIR is the “right” thing to do, the fact that LILO has to create temporary device files at + all may indicate that the operating environment is not completely set up, so TMPDIR may point to an invalid + location.

+ diff --git a/doc/html/user_21-526.html b/doc/html/user_21-526.html new file mode 100644 index 0000000..6da2ac4 --- /dev/null +++ b/doc/html/user_21-526.html @@ -0,0 +1,22 @@ + + + + + + + + + + + + + +
+

29E.g. if no hard disk is accessible through the BIOS.

+ + diff --git a/doc/html/user_21-527.html b/doc/html/user_21-527.html new file mode 100644 index 0000000..8d46004 --- /dev/null +++ b/doc/html/user_21-527.html @@ -0,0 +1,24 @@ + + + + + + + + + + + + + +
+

30It is advisable to keep a second, stable, kernel image that can be booted if you forget to update the map after a change to + your usual kernel image.

+ + diff --git a/doc/html/user_21-528.html b/doc/html/user_21-528.html new file mode 100644 index 0000000..4876315 --- /dev/null +++ b/doc/html/user_21-528.html @@ -0,0 +1,24 @@ + + + + + + + + + + + + + +
+

31Backup copies of old boot sectors may be needed when removing the boot sector. They are stored in /boot.

+ + diff --git a/doc/html/user_21-529.html b/doc/html/user_21-529.html new file mode 100644 index 0000000..acb59d9 --- /dev/null +++ b/doc/html/user_21-529.html @@ -0,0 +1,27 @@ + + + + + + + + + + + + + +
+

32Because different partition programs may display the partitions in a different order, it is possible that what you think is + your first partition isn’t /dev/hda1, etc. A good method to verify the content of a partition is to try to mount + it.

+ diff --git a/doc/html/user_21-52x.png b/doc/html/user_21-52x.png new file mode 100644 index 0000000000000000000000000000000000000000..fcf03b4fad0670cad4feafc649223259410f31a2 GIT binary patch literal 1579 zcmb7^`#aMM0LC}09L7>|DJRu(q>e_GoyTSC!a+QH+(I5&4iP0P$ztElG7FWCN^ZsT zl;%X)ng25;O5g&zpE<%f zdZTkV`@Fp$@|O@_ebq@C)xOEDffzkh`|tq}T>(zu&Sfr88~{C`i`~zP+1Tw?(Y#Fd zy197I!kZI^UYm0*1hW^3$?!Vz_hQ6|(2^s`*4Gin6#>7FMeKvdgdx4ycNQj2IG70- zYLR=1U7HdX)j}BxHpLgHt~f^D@2s`kUa$L=A%1b(t&mk{2%N|tCoTn9 z6NGe-o1}vttcs0%<*-|@({Ibnu6h2DSjdx&upz!HiqyMkOmjg4RGs43o(8Yb)qe7# z5FRt~$j~jSD?8GM9Y}!AzBWcS4};lMK7N4G-BlS;%}$=Ofh>J=w|pJVcbW=NZKE8; zOWKi-&HMZ=s55|@6dJHe)7?=F!dBq?uzN-}7B0pVtgtiszSq|AQVNjAtU==1>)}B~ z@y)HBQ*;icL(x6V4zxylCpXg(y&U2$yBc-K-eHOZbvCIOO=Iy zjzw}4%HZMsZPbOuIG{nwhSJ+tKUp%;{ai^fq;wrFiZ3VBwzFJeL#J{#VH#zVF8P*I zIPFxNd}(o1oA{o-heopI5LBwwftr;7gE!|Z%Ok7}62A`qjU?0cRsw1Z&lTWWHNl$k7 zC(VSiTAD1ehEuSWfkuTM)!sfwsjj!HJ2w+5>*d;YEv$>uS-w4G3yur-o$aVa0A+Sx zIAuky84>C41?#YlZ!ZvfZX}nyks=r5W4%l!fNF{7qWA_a3{(pZ=X$W{m<9EWjP0Qa zkSpz19Ct|tKbcF6o45#+`c#Ww$i^>TqhcEse)6g00)@cOIvVdB1*DbV8xuFo+}qOA zWLQ?t#Szd~HZS{@SYHCiO9po6xIQ1N+^sqLn=@gu(?KR6uaA){gP%IT%gf?`thuo>R0#5^+)iOE(63P+Z*D)E={sOX)M9(FrZnfp+cGi3pg19zW%kE+ z4T+ZxruFxzrq$_Ph=!Lo33)B#q=RVO6EY$%HJByptkSqohotp00eEzs#yx|3*~Ve5 zYN>l!?IFFrEOw&lHA+o`wb)Amrnv%J(YQ5K8ZPw-R4Y5K+}8){G_B`jFnPU3PX6k2 z^?|e!^Mn~MnOF+?I&$n~6|3^Q;UZ^L|2tGFFCD*OVUSM3^{FR?gN)dY{6O!Ud)3pc m{#E@yip@;qux#t25i&H$Z37F8HOKt>_dcF@k7tKZQvU&?sVA=h literal 0 HcmV?d00001 diff --git a/doc/html/user_21-53.html b/doc/html/user_21-53.html new file mode 100644 index 0000000..cffd4e6 --- /dev/null +++ b/doc/html/user_21-53.html @@ -0,0 +1,27 @@ + + + + + + + + + + + + + +
+

3LILO does not know how to read a file system. Instead, the map installer asks the kernel for the physical location of files + (e.g. the kernel image(s)) and records that information. This allows LILO to work with most file systems that are supported by + Linux.

+ diff --git a/doc/html/user_21-530.html b/doc/html/user_21-530.html new file mode 100644 index 0000000..89658cb --- /dev/null +++ b/doc/html/user_21-530.html @@ -0,0 +1,24 @@ + + + + + + + + + + + + + +
+

33The expected version number may be different from the version number of the LILO package, because file version numbers + are only increased when the file formats change.

+ diff --git a/doc/html/user_21-53x.png b/doc/html/user_21-53x.png new file mode 100644 index 0000000000000000000000000000000000000000..85834202f940d599542fb3346c61a6dc677b4a58 GIT binary patch literal 3188 zcmb`Kdpy(MAIIksmDsmj$|}BHebHPBQ@KR6gvqsBhVqNbJ+v|}bsmrNew?(62)N>Q z$aWA2q-b~E#svhDvXJnctc;{LElBm23y>LY6%(nP=&3EX`7ldZT#Av`S!(cuW(x(9b}vR z54b496K)*55GAX#r`&U1GgMryP;K>Xw6V_4upCwG1!+32=>B}$)HAt*LBpOQt_R)h zyme+f9d)6G(2$!ojuowB{?f;#q2?1Slgo>7K>~{pFy54q%-{G0Ys59{uLz}cqex@r zN>Qz-R4O+f@FW!JBR#&$k+)n*HOcetW-GGVe|Vij!S1D6dKg{9T_tEdtr}De&h04m zw_E`e?;^L12_WxG&U}4H)sq|D7A72_5mLS9USMML?O|5?rzb9H%^@Nz%5;rOXp8eN zzvk`Q>i2ej;V}|E08($B3wU0laag-bVY<;GL}@s0I%vz7vFc41yKU_~&3nw{8ji`S z`Nf;TqG1ll1oVaz`IQ-jsO1S67!ff9-+rJi(D~_#U77VtpkF;RG!pZ!;f@ zQh(k~=l)G^(lG zrO^JBr8gbi>^RKdxQ#BwXdLATl=A9Gu7e48Z;|pM?c_gUH;ueNet{8p$si~?qpS4^ zbREcRl_g%wu%~1lrNnIa*T1S>SW?@)*Ga0ZL}RGsc_aCq?skUO6{AYdjBX(A)r6Bs z01yUhfr%wd%VAn0NbAbe)6-V!spHaR4#0WX=FB+%XeVP!%k@L#kcP)l!tz5J>`Tvs z*T-x4`YUq-c4Z^<(dbV83JSgXdSa#!mjAcQE4KHA;V1-9^NHaO-eGvhIQd9l_C*5s zf7E84eHB4@f{8Z`i_0JSl~ys9a=I>4crmwjWN%=paM(R|HeM=BmjDYJ%OAdEhnrlZ zVbLp&Vl?+9lK1TbX|Xs+0pCHsZ44YvjTP2)GdfEi@w`Qf92@Fmlp5Fl4Yqc0U|%23 z>#eAqDEBh)$+A0JHw2@Sq!b7%mZ}u}DZfb;p*wGh}{u@&>ES8WS6$w0fKLHLZXI90@Z?nNU&+P7wJ%5Se?5)1Ml(d}FM0e~tPZE%JxS)5K$AsPx;S}l&wbaa zw@;b5OyM51-u;#U3DbpKNXbAnd+X6`xTAWY6Lb+`36FU&Ti$GU-qA!ddC=6wwA zCxN|yYMrrs_)HND;vid9zTws?Nzm3v$(_3 z=ffj7bUY=C%D~2Q{BC{A!crM$@3bf!b9MzpiE7Wdc7lYKXcdD_OVXg8Dt--Hy6tpq;cq^#NJ?t=pD7V(|I4N(HzZc99Zl&K;8a#!<}mK;8a) zMR}EMS9HKBBb59CB$AA3d0H?lu7D_lU6%2JVQXqgm{T`MNv z2&~_pJAIQ;o@YodU~x2>m2rIzm39JQhGyLCIm)HKWb{#K=@UCY-1vq}*zRIXcTRvS zs*T9D$u6{(wipGTavWl4?$d&W0`uO2Bkyq*r=zu&l#o~;0=`7)tK_uzE%lTtnLv`j zNp&6aX#Xzc>9^W(i5d-UMWbQ{C6hp3v(a@-+ofd&9+0_B) z4u*P>t>qqW%$$O8#FU+Di$j?w^!1Ip$Vh|lG$TM>L6aha!$p=Ga7 z5iPL;@sUiWBqErMQoBL88sXG-Nfl$eJ~PeoruGU<8+L0g8vs+%F*Oh5*%u|N80}6< z0iK!2bb823xXncDAa4OyuwbxCGdV+^?H@smrn%h38g?XcEoO3=qN$P=+UrUvqB#wuS`!C^s>Fj{C~VYPMKB)4~hDw(!Y~kovE~iTit#; zEX=YWTN?0AL{zw*`4($|!55b7d%lee05T`^yOcuP5w;c>1_N#OpP2)O7_`{8kD^&n zI1ev;Rzzjk1J7kn)UC}SG_S|L%kEg&44uVTT5HM-fZLHFMNi|e{}#=*87v$A8X}g| z&wqjmvY4Y7s;k=TbDZ6;AIMf}#~py`n(lv;c}pdUI?A@mQ7zAy!TxyQkcg1=Bk4S~ zbj4RhsUD&5f__9j1O7yDMfa+yBmL>w0l<%OuSj#2I3L(Tl~ zGESRtt~wS=q~3En+)JUcO&LoyBl77Ktx@)(UAj{hRohclL(>nRyAkJtMkjteQ~0Tu zr!~fYN5AC4YgI#MB7;rVBJj0=0o*=60BEi1Cx`^)jY9IK;@AK<(Ppe*cHrSL}cD^BnW!f*>{s13h$7oBIX}ryHb=cl2}o_33k?hk-sQgoAdX_ N!Oj+8Q*Z5m|KHM;jtl?* literal 0 HcmV?d00001 diff --git a/doc/html/user_21-54.html b/doc/html/user_21-54.html new file mode 100644 index 0000000..b1500fe --- /dev/null +++ b/doc/html/user_21-54.html @@ -0,0 +1,30 @@ + + + + + + + + + + + + + +
+

4Most FDISK-type programs don’t believe in booting from an extended partition and refuse to activate it. LILO is + accompanied by a simple program (activate) that doesn’t have this restriction. Linux fdisk also supports activating extended + partitions.

+ diff --git a/doc/html/user_21-54x.png b/doc/html/user_21-54x.png new file mode 100644 index 0000000000000000000000000000000000000000..b1e63f3a9a7e3006a426a56b99a800533e2b9da5 GIT binary patch literal 2095 zcmb7F`!^Ge8=u!u?zbTNTm!(0El^F|!c% z#;TdoT4_YQ6S-6_A??+F@clmLJkRHIKIikp=Q-y&=PB{^c9oG-mjnO+GVX2&|2>@F z>q4OD-qg#SIJF06zFsJ#P$=A^|9c(b6SMc+a;g5_Cjl`lC~^4g-NyR`)8!L3RM z03`0ZBV15%VoQY6XOsh!UkJx)mT{e5a7-91q))wy5I1y_1JpBB((`bJ?fS#KUJU~8 zK2Iu^Z@ctB!KxB)4XETYbBt)tjMR(klk@!~5m7piwJl3yEE*Cxc2EOs`FD7g)Vj>wo*Zswmsj~F#mlxAbyzt78ndv~%6nry zVMR#1fycG77NfJ84!qZ3nJk47V&*FzQ_Sh@jJ}@2LJ%tFzQesQaSl|$9}f6tC*bmX zwe15AOSu~(sGf}8+szRjq_k;CLZe*QkH0#V61Vl+JS19nveK4A%8&U_np0>*antdA zMrBwZ|78+nBg`wpXm`#JB%%VJKD@v)Mtt7AEokTm;a+9vrZ(luMu;j*kss-~Vqw8UDCft)+ z9XkFeyVzd>s(`|F`w}xyoLOl|uHq}BCFMh=PA3X&t>#I^mhsS;I+L->m9v#MZemAE zmTPD;rY*XS(&s?K0VMx5(!3h_dKeP=e@KBONi4?Q*70552zz=IYz+sqW}fondydRY zVMBGhDyq%Hs|gb~$qM7N?ir1~a|>BfCe_;oJBjtSJ=**Cx#-rchgXu+f~lW^U)wT{ zpN~aaCKeBz1vcP;9VvW;IJlOLxSaUYv0^c8 zh9x4|l{# zC`_mF@{(Q?$2kWl^O|q{B;fEw+2<+?W*x6$R2N8Y(UP1CRAVffzCrMdX>E0T0I4Qh zYz$zK$)I8EQRbPn--lxn@XrM*1=7W>&hz*}zOApTC!)-(0iNhf$i=IC{|@s$y6%>ny6^!}-Z271<9{ z)EoL59gjlAJK3)7O$aie*B`wO~SmSh=hNhK1)k$HQvhDFtcN_iw%h z6eO1wCr4cP70LzWLtfDCVF&CQ!m~>r_6pftn<pdcGPb*3kHq-(A~R4t&lZRbO;b?&B+799 z8;*INw)TGRnUs{d#8Y(*|DlgC=piDHeM=j^ZHEt^71f5h{-aPdUlZS)I()vLrs%~d z)x`v(=R>g?ViTS;_n73{NgR%@t%q}=zxNG6rC5=SQU9P>1T5EwP5ld2xenjArPOlL z-Zl76nx2}Svu~1*@MCL$v6*DYt?>jW#c>o=B+3veQeDfdfUt17xlLN4lVj*4k%wUi zJlUDDCB-WlpTicfWHtqJK~}3Em&?ycSdiVEyZ(4B-otOQ@gl2;ja}iG1;jH)rmagys+RPm*OAdu%vffjvIu5CfRl7tfdMaW?oN&XyWi~J6UOUMiSY+}7vdSrc8?W#=68YT{@34DIH!S_xXC05&!t+b=jR$HwUi!?rXw4b*8T)@rH0f4)1?8}R@Zp8p?0_SujC literal 0 HcmV?d00001 diff --git a/doc/html/user_21-55.html b/doc/html/user_21-55.html new file mode 100644 index 0000000..272f2d6 --- /dev/null +++ b/doc/html/user_21-55.html @@ -0,0 +1,28 @@ + + + + + + + + + + + + + +
+

5LILO can be forced to put the boot sector on such a partition by using the -b option or the boot variable. However, only + few programs that operate as master boot records support booting from a logical partition.

+ diff --git a/doc/html/user_21-55x.png b/doc/html/user_21-55x.png new file mode 100644 index 0000000000000000000000000000000000000000..d116e6501ca442201916600c5abf9e467d88dfcd GIT binary patch literal 2321 zcmbVOX*d*&79M+J%M$fjW~`Bz6pdTv8~cn=_AO*9Mkti6d^2Sm3}Ir-mkGsK#*!Ml z>^oWd7(>|-VTv#&TNAGP++X+aJwM*_o*(adpYuHDJkP<~SRq9OWds2LfC$Rm)D8gP zq8xMe6FkT0bIsTPIKgbLJD43E9UasEFVrW+oQ{=}VRlybfJ^u$C9&*bbc92>>Bel= z(Np%rIQ=D7T{{&!!cwShD$pX?g|YZP4Wh&$EX? zX9zSjhh**7es|do{vzf_CT9Ez)cHv2-7GS7*41b@$sLvihNJK2% zE`gWP-QM?>_&}Y0FV9*PdI|3ae5@+J^W1@PYZ&|06|~;rxyOvcXdj`QE|GZ0)1^#U z^Ay>Z((;~kpE@d*%9Ob2r3>eMW_D zj;78@o+~Xli^xl@!GPgBA;uPOfM~E?Q2!a2QfmnWE-w};*Rt0yCCr12yt~o0v zMqU|x=QPv#J5+Ar;&9lE2HZ3r0h=G%Evd!}b~$h&Zwro@#OqtDA48 zy+&cM8Y13)iCVk^+rH)(waIicVWEd6NswHtpbq4> z9IEjf1$}j?>Y@MyYp&=Tyi-;XnSHtN@d=Ulnc64PNjiisDSjvXD~q_YniCYs{THDDEQHXzk2c9Zr7@h1QK|3ujdl24w18 zw0j(KY8O$ern1f;OxS;|{PM}#&F+ZptyqYTz!`5<5xkm5<3}VxQJ}V(CZmyMc3WU; zRH{V9+*p^BwluG-uSk&a7D4Fypj{)+BKNeBQk$d56BDqyJ0K&61Z`l5H~2L(CYcTE zv=2am+Q`V|Mh_z=4aXc@fDvoi@$-2ZS1KL$-aiS3_r-@>)SK8=zgOz?F*IyksF^^9 zL{)pcD}e8h^Q=g-HF&E;{yMedms~~b8#3Vgk@q*?#kz*!j|P!jW~Y1nzhyV6=TA8) z?(vVUrtEVaCHflQL>);f&r~p4u8uHtXd+^6@bT;I=ufP)yCCQ6&M1)fnB<|UTSAzgW^^MHI`oJ>+G^8Hd&90t zD2os1LSNXkeCJ3xt<875kwc`inD2TPhJE~VwoMbP$CjM@_AIr3P9~5efO{Vzc^ZCB z*F9ybTlhRn;2aX~ljGN*xv}n`)f=;8}152XkQqo}t(0y|8;ZhqqAf;@p*%&@HrCYN0*RX7X=K z3sM_FvQ4!}*Lb5DhusJ^oRfK2WTfM=q2D~~MWPxPZN@c)vQze5LSPmu_hyJkTy=LIy$Ak_dYw9Wo=0tv;eJ)b zjMFqZ)8Em0Km8NJ;|yBS_3Q}k~k$X z{~R`g?V+z_9j)^U^buY-+zaMRDZQVn^oU^DK|E zl-0(JwW#d*khNG2%Jq@+iDJT?bHF#t z*GT%Dw=RWb?!%J94I)3+|1|JpPmQf8Tv_A + + + + + + + + + + + + +
+

6Other, possibly better known boot switchers, e.g. OS/2 BootManager operate in a similar way. The installation procedures +typically vary.

+ + diff --git a/doc/html/user_21-56x.png b/doc/html/user_21-56x.png new file mode 100644 index 0000000000000000000000000000000000000000..b5a2f0ad9d79021cf3b05a8987beb01199024dad GIT binary patch literal 3299 zcmV<93>@=`P)LNf$v|>j{*%cnUZ=6DV)e=I}E6qa9p(0+h8KKC^k)cb4l|TNO=^#?Zr}COnxM# zMW-O2*z{MX?;`L^R8AVS!rwi-LS*{VFK;DU`yWS)>N>rBx{`^Gve>Gyb0sy}z~R#J zU*Y0hi`$CPchz4P+miZJ!>cMS>;j}l_MOpQiQYROMVO)=o3?ngu(T!{R~`ut3z0v* zwvp>_h5jhw>!RDzu5>kEKz(VMk$o1lMcSbRYbu=$=lJZ8u{Tv}AH`JVT@4bwQHE4tDz`IV<4!%ndH zihbUsuDqChm6VsFV#R)d|*<+XIDW4Rhuk5i88Jfnw&eHli z(Bz-Ik*>dHkLS3wIN)=3@Yxbp>hnEba%B6qIN@)+#HGa!ci83$cX$gp9J7Vb7Cs-s z`2e}h{lF7`<{be)GNLzkd5qGz!yb=05EYS}J7vMKZfxoUEgE7Z20>WV`uNi5&Bqo0 zTYw*qUo1x0Vq$0dyf3{y8|yXk@MzKsM|yqnDw$?>fjOJiSIo61USN|$SqO!^>6@R zF})K_$vBJ>Z`n)|SNbsZLm8GLZBJM+wL>Md6BdyNLIebOO7r~dtr*Rf0NZ_yvz~i#UkY~o=#LDBxRQ*OmAmA?1}=@joqy= zmc}J*HmK6zGBH@Mh*miII%@&rk_*n+krqLQvEly^uyd9`E&-p@RNB#ZUGXd_a}b8W zyd&FX^p!o9rD@WeI<2n*V=fb8$6a10-Wg!$+r_2J1DYBSPN$!0;bPAG z<#CvsJ2zqqY36`HWnSy*^qw&=*6xE zG5P8YejvJEa@vE~oMc}kb6TLR1q$v}^_4xArD@!odabVq&u}I0I9Q3+byj)k^F3K| z@^W+5xwi2WE8@vA_l!e4QEe<+9#!9$I83L`e1(@N6dPe}I?b8~!r`wN0z)kE&KY)? zA^B7HHXcpjHJ13w<1}$aOuh;OF|v!N-DW6S0vB5$Q?5x7y6&z}U)f_>n#x~iX?;Ct zb1IGVT2!Sz$gHibXXbmd=E#I)oue=3*e(Tk-GFF0bGFBs8F$&73E zf@8M0&nAa#@ng&)Dq1{?n)_p;e~Z%|@5{41QaQ_mbU6AMKjDQ+?0mMISgS8VO- z>{3sR9g9T3m?0Zj;($eZ%ExBB!t_hhnwn0pfr07t8WZiQv-w2L%j>>J34&DCVPCtWBR<4p1Rbq+2K%}k%Z|v$!+%df*nTTIgd!vOX>R# zFSyHq`%)?osq;phZ9V1(9#Y|eD%;n(&n635mW*=kU*41D@WFF-aoFP>M_h>Wm}x8K z$#u0KqdPx@r#)S2(ia{tX)xh^re}-PxD0u4tQ(s~hqi3#B&UuMrz7@B&QA5o$YNDe zvkR?)-KYrYEy=RKI8Uw@0lm=rAoPTeAt@`@^LVzb)alkHlTfxD{?d82c#TUif0P%d z(YaIk*VL4WIBGkRT$3zZJ{`&Fo^*0Gp2{Tr9S>foG|tjll5Kx+o?Iu~1W8+89LZK$ zk(cXP&t}h)d>27@n%Gi=X;PD-HNFv3NL?)95FI0q6$X=Pr^r04N_uvo@d}IHqKAKV zmSo#soF~_3eS>Z+C)$}-v0oW?jD)Sg|P z#y22LEyki#dM|N*5Ozu`d`_J}S>rWD&7C&BN1HY^p7Dz`3hmM6jH*Npwi?tqUvTWJ zvn1R8;yk$?>jx=)$+03k*R!5g7%*jRuv7YyQF&Q0S;cF-R@|PmHf^A1#Idos1jd|F z;edv4@P63sP_rt<>&hv+Q2gGE-6&q$&fePQPXPRf|A{-li93XE{1!g@OXA&G*XW%6 z1+qnDNxuD8^<-CR_ssUVEm^ittxwv%i1kT*J-WFJNm;qBduC&Y6FIe1U#dnY(P>S3 zc6Az;K1^N4!kA~Yq*^Ot#Bsv{+2@{;?CFdeuX4JBwxafXppaDLG|G74ZnesieEYBF z$yM3Cxb<~9vG!_%afTK1gjQ$9S%8I;P&wAF7 zTKZ@)E|5B@BgKM@>{&N_yEu(Y5Tg^ttX_i&9RdQHv{IdiCO!ep@V-rePe6lKVm#&0 zVnPEeEEEAfCN!{PsWj*bH(B^h=mp>= zvU6Sk%%u~qp4&8;(8I@}6Pr+*>aF)|Lkh1VG%jtJek%C1|Awjg3$8Z@hP}bSp!{KK zPRJM-lpZEb4Gc_}8WkeT08>5UdTE&vq=fsSoJC0D+u<}O&j_5Rv) z`2=Isgz41_s-6o##X+EB8^{Y&HFrT7Dk+0&^8KgW>2;UhiIc?zpyD8ikY*dmLLPU) zI;^*FG{@kqP_o(SWX7gTW4LttpyvY6aS+HseXu}E)hq15U9I&SJf#7+^k|C1{T|@* z6D`1|#Yl{&C)ikw!oAuCCQRqXRoEMdb#nFhbQ}Z`#tWsL$6av!)(^yiuP)DU>C&b_ zLtIavPY;~6*=K;on6tzQS_2cNb767z2Bhv>78ih?gCKf$tdXnJm4b;^ma{%y$W6Ay-YKjIUV7Pumk67eF=#!7Sz13$>Ae?*ZWCM4v9xH0fvl3N!?&ff zUO#Hx5Y^TU9&M_eo0(tJnl27+fk_#MM?ejWd)QJ7S;wPE4~q&_E}8zJdzU_EfK3fJ zr^yA6u&81I6*k1XYPl{4;@&9^4R*OF(i`(_VXSw{TJKO}7mooob_r;U(epDdxxg14 z;eau927-95M`Hz?PM-t}dxNpwp!6|nb|D!Ulsrt$)_Vhk(!+$Qfq@BA0|NsSrUnKd hJ#LvPBm;x8 + + + + + + + + + + + + +
+

7And the author would like to be notified if booting the other operating system(s) doesn’t work with LILO, but if it works + with an other boot partition selector.

+ + diff --git a/doc/html/user_21-574x.png b/doc/html/user_21-574x.png new file mode 100644 index 0000000000000000000000000000000000000000..096aed5c1d574e7aa697f725b5209c5e9602296a GIT binary patch literal 7089 zcmb7JcQjnzw->!c7f}X@E_$Dd7M(CeZy^{7qXeUu5Q3ht}*_11dp{rApVXPte{+U?xC&)NHPZ`?BjZE8w3N&*4`YF!--V*-LZklRj0 zPISAX&~ks}c946fZ>o87b8}1nf19>=Vb!e+y|1x>34v63oIf|+FO9ht(^uL1&r++4 zEX)ZA*jaToR80f#?Aj(Y)>Y6PSDl=4E!@1s@}|T#x!RQahkqHLf5fd{#3Tw)W13T@ zZqh!xARxm0cD4jw2<*+r;+7$dINo2iif`&rtzj&V54D%-+x8uw5t@$hi z8i(}=?lx$F=wLZc+#d~Tm-*c`qC`87`?`3J^b{Fa9y-eD&7?NGZj=|+hMy!hy52ES z$VEM<2QXG9YJ&JpxK+ymo(-B@sV2GNMP>Z=zH_dCE2Pd&Z+^N=FonJoi+LXMZi&Ss zl{)l~!?8Ua%->9yqHTKmhU@5MmvoiRPg0(QRm<&HAvs|ymRNEXLMu>M({*R32dr{S>Yy?|KDmvDZ!rVhrghF`^8%T7F)_8tG`w9PCWj_YD?jlVj-fR!5)kC`dIgV+jS}nUAWok?e4t~7X0UyC2YN#x zFF2Yug>AXopwcVMiJ!I(9%~&31+lYLWfrM6F=O$*2)~uA&#qOrFAjZ zuFRE`%c(dQs-^JN!d@SZm>18~UkvXnEka`|9&yRQEbGapmpvmyUyHqRF;<;9@F6+$ z!Uj|_RQ#Pr*5Jwc-{abr?6;X69}|1rN-#;EJGvjRJ2^6YT?e{my1pti2?2#7u%=VE2=?5Ieogw)S) z{DB|5TC3IBes|D&x|Tx4@3(lxNZHT zv+w-ut`~bhef6Q~WzMi+G0;QDQ6lFNN6J*A5EIX(tKLi$|BJGU-lhlJhvbyB9?gNT zjxs$sez1a=ouCUxnZMjk!cJW!uzeKIZvAyLe{7oi)W`I(uGJ&-rkaF{{F!8;y4RE= zXUwUjJZ+iLW7h;?S*O;5Wz8F|_5H?HBm0#}ZoO@E2|o3QTq`OjQDe`#uO77(H*b5CTxRf91uhAs^oO)5}9*2u0a~bKnRY46VYjt{1 zOaF9TSHtu15En}W`*fpb(h^G!%hjpTORdHCm4OJfg=H`uxVP}e$b*Kgg|3K13ocqq zgOj`xOA~FkGa|j4CZ;X&M6Su|YD1uImbIhiZ41k$VXf*yDP`->&`?e&G+~|M@>xOg zU8aHbn6L)kX1?LJYEk#=SLs+oK}@{+`E%9$n`hq))hu|zUSm11k1zqmf3+n@;8)=( z5xDO);iQ*Mbm!iSlPW~lHsn`8ubuomH=x#%zTl*x1#jj$Q42XY_4MVHWeUAb~{Rs9QJQ7zhzhxWC zT7GEwBND-0uG)F8vg=sDE=pcmNGc$l^)RTrOxEG)nVs%!XqiL0>Sad>2Ei>`EV@m` zd;Wm#d*d$Pm1*ztPq!}`EvdTq{gbS>{?QFf$kE==2s_ZV(*px3In6q0r~mn*=0P3X zNWUcX8J+V|8-w3ya&KfdsUKI)BjATL9;`ah2SP=Mh(g|I6Y9S*mH=c#vD6hF;AfA=j(w~0s!)_TVSe>$o4 zHKlFf$zotSa>RfbZdeGbLo30z??7NWT#{cfc^Y?J7@H(!E zZl^tuz0Q^Vaa}4g45QQ4m*Y<4b5`5LP|8>S8q&fLWQatPb9?PNY|uv;QXbNAAf}~E zXgieyQ#`V_7TTBHCW4D=wd?BH(b6K@(wr2tHaH;qEi4$mLk~0qzai!M^dn5X$SxW3 zcfB+wbu5c+y(rRk`@-m*q zAFbWX3ljkdOPvsTD;iEI(TyNu-zc2R+a`soMvozZi{nv{Q~R#JOkodSZK3iqyp+~O zw?InjKxU_}tW+f&K3K*ip{I{dRffVsWe-IkO)|zQ-jz)yGf7OzZUc&W(Uc^V5Mn5T18xZ~1a7O-pxd*aP7L(J z8~^8i6d_bx>UQ;hIdv}wDItc273EKaLB;x&Q3Dj50;jJ+00GA{1OEu^#x>tB^8=w= zz-Mz)hGvo`+wG($YTI`4+=Jlu#O;mGrI3to07GZnns!oc9;;D^Y{|^ItdZbD>xv~g zXb$dI|Ir8BOuIIA2`Olu1J?Y|(>h2f1ZMpf^Q#2dnp9$FJl$;$LP5cjSRSI1F{B`8 zF^66j1n*|Ny9v`n0M@cz{FS$2tu*i17WFP^1*B$446snwFB7}SZ>8JqI%tFJT)>T7 z3F8`rY<>>Y$uECj!}K)Vq#Q5+I0S~}ehlK|-1Q;l6&l7WQzZv%Fw(;_t<$B=Q^xB% zYg`R8ZO~!h*<>h(q%IRxGD4Cf1Jj9jVFe_zbH!lN`BAToo>v<*q~+R?4Tgc_>f5 zDNi8;W_U!)3OW;WxqB(1h>|(?EeBxh`8k~_a$UfhalOcoX>p_tv6TT0e1^YTk3Yde zh2lHr0v9K5*4h8(Bo}az!LOtjJEH$26JeYsyxdO;rLC>2ajjvY4Seu7mUK>O@X9cm zuf*x7OZ0`vQKkBO9H{o>T*EDG*K*5IPwRn^bOK$M+gsrJuRS>S&+ko5zZq56aWEyatbiRalQi_~l+&qpe4B zaaUu>iSN==^Lp0fp2r7r9j%BMwCPvceObx!6++)7o*K zx_#{Q1{DYrm@jT3*U1f5@qp>m$X)W21Np(aGQ}Xw@bT&gays{79R7MsyRUPg-(Y+_ z&Nkj9Kl(RzzHNRb>w{vM&Wr>y&DFpL@ZxnGERjy9`^oR3G=B>fBv6SpUtl&yf_a7y zCCI-Fy1?<)TIpnr4jPp6_?|2`B*wXae7y8*zsd^0Q(KUZHI0{v4YTDc8(M0KFV(I9+*lD>4_U9z%#Tq zXKDr#y*gR7AagD|hk_XS%6VL$Qmk60{JP5FZV5|2adT|gk)IE_kju!~6~g53b;TL7 zk^{njEMA{P;NHNMMd^Xph|a5RBFqKgjWxH|rO>;J2{QO!(0RSa;-r-2XHil9EuN=y z1Aq{XbEs!Qk?^mXCt)85j$NNoF@!sb5A%u=w*Tpd#&pzyv+SIstJ%2@gTH|ZP=Yd206)>-!TxaPWrA#t=Hg2HQ zLyo+*sC3v4H|``mF+9DmzXh<#+=TRO;3rnqW6y*H1QiXWftfh4iuzgH2Wp>y!NuZB zp8!<1Ml7p4Lt86^{Xxd7FlXlh$vM8ALw%-uhMDe;v>>*(5Id=IxG+oh{abz1;7Y{@3B;NdYH63l!f7u~iT2jFkexAMi5Oy@MdoZv8D!L7zkK}$~RZjKMUZT7~q`bJ$nbm;}~Gv#`(?4%l_T!ZwCgvszF zhz9@(HjDW}&D+R@Z4g|tyv#RHJu%=z%i^W%(nIEFYg-W?-|p8Roy*Pu*m>ihkN2VZ z0iu-JuPVH*^6lPx_uX5bsAp+e18BbpYoA=3@e#?Il!ClO^v`BU;aA?mvNuX_ zi~1sQ>>Y}xT0fvN$pE#C;JJrNwo3bB$GmQQj_bs(j37$IyMcex(87ZQz7XZ5K<)aw zW-Lo$R|#>FGENl4m|6o}DEygBza1(B`hm~Ud0nDfnRrhhn#nZBgUQ(r4B_y^YC~vds2B2*==Az)^$ zN_~084rs)axAiBS?l2d(odO`f^skA(f2Vc%@4~3xz!@2W{{D>BNAjfua6)jcYWBI@1xaG?Ar+fl2 zWw%8SPnz6LV@^9UNa5%EZOaLt)pJJClt=mQ6aQh7{SVVFd)07Pvxm$03e+0&4JCXp z&n3e2YnyFyLKCXI;n@@BrwYCL1?x8|>wz3S!Bvi+A;L-%e;3W2_ZO5fn?|9wM7x(v z%Czas(03!``+y_}JBHYx{{Dg1+cNAGf1xKJ_IGX;J^= zNvgbW>k;v++=ep1tYtx&d{0I$Rhp5Be2_|$r2VDt43pIev#zEuPiS7#$6y|e+$+?X zs99{H&iS3bc*KfCwqG7*oTn*OPn7PpS$1g)C1Io!gi5>!;6Hs3)Y=QBBp~e)a%A4) z0JPJbo|Bi!!`vO$BxQyZb<94Ee$vPH*9aBYoQO4j|K1aB_G)@%$>8c4tqW&r6t++_ zWAB$z1b0fRu+_WD;(v{s)6@NmRZB8*Jx}8>t>@AM(NvLDSlHOxKfZB$kUXTo_i&M2 zD2YKixlzZy*)1V=S*t6Gg-kAY?jO|?EqDZPS3RQVPx&BlioSQ0fawb8iY_Ssb^Q_{6Js}4Xmm^(>|e;* zc~>VS@!`>AaHh=z)2-7xe5Jk|2epk5j%v+W#p7HNHzBEq%H&9qray|LVw5xZSR->6``d)U{Ix5K_5f23L1)n^1vUfWq3My)+jm!@0--WN@s# zy=}VHZDh8jkISGRH#WVV3Es2BQ8D94THj}5(tb|JW}iI&8nfmQ$Z#1XDRk|=op_Hy zec#GkDFEV8=K16|@1Gyv`0G%@%&3ylM1b2}CFtru{@Z`&SErc*+Q(M||5a~RXlUxH z1(yv*$Q}8vd%!0=Y_Mj;)s~3^6(wHlQB~%yQIMnp`SyQi{fR0WUdjrrjD!p!d1L0U z>Psoz9K8dzT&G_ZhN?`G(oOQaF zK1!fUJHy3bTwPOC*RvQLH?G0p+esr6v-&dw8Ki;=G1WBpF~&ZsiNZk6W@Zg?q@)-r z{>a%@jShnB0!`!AWd2s9u>?1b6fHj#MW24KPEWk&ll*8XcMWAG_aC2H_0J=GO~4ky zvct);G4p579hAxv*N9mw@=Kh;^>YqON69hg1^I1tCxEMZj(p~7`5lweuL2llQM=X2 za$_Goc$;(Cm7N)-38W%ShjiJAdJ z_4jV~;Mz`FCc_(V&_YvRxdTb8up%bE@t$bii}*|~fp8HdqpbGv;f*}whxFtP+r1gy zB_M-SnULQ(Yt&;1><=osJReX;&}NZ##7 zs=g9uz!OP^Tbv_^AFN%~y5VQ@yI`jATuCO;CTRX}K+h4%7pKOU0m^0bL?9pu`m%gU z!CG68VK^HCKR65#e-pY}A3b=#2cz-rXIOg}JAe7V!dR{IWIP zF&!9X~S6X*?GF#b{SJ2EfO8B7IvL0k^R(I|wRk16F z?Bb407guMpJHIqUy6E1$Jd&N=@d_+~1-Jkq60j(Fe}zQ++npWE?9ME9X74aYLqlUO zXywt+m`ij1q6cR&-T81f!EEc(kt(nhqNK*oTtu{h!yIaO zgN^kWL?$nKi+uL;j5;o*;HX3sbKx?>HlNcfjPjf~o8S@hY@HSTnzBM*=2f+dD+Hn0lo2y^4?pE==Fp_%72c+C*7=(58%oQvMZVw-1p z3<0RH&NipC`5OmpVDNx0VDddHJY&EmHchrL`JRt_2+5S1pm%^RHZcV1)DWQP^DdCm$S0E-hgaM{4+Q^fa_W$`DT z^9z?$c*~G(W;qS(T49f897H;ZC{ENqj|()Z2@4-8!RzniNwLrmes z``7!@-4h?8frCSXX5c~e#jgq#<*_T-*wJ!a`a$XO+WT05DLj?wGDF(>qPKIDK2IL> z${b6lQ+_s$=IesVSWpvMD`P=jC@oH^EJUR#+Ga<1u#RZ`fWNVNbruXBB#;1LRC#rp1X;cI^s1(hpjRr$+B&+N{Jf1mO& znn`&KG4<=jUe#*Q$M~#yD4P6+0WiQ2_ncz}ESWuhY2wfTe#8(@In))$at$hY!e@xq z-eMqnNE=g8W^@YLl-gGWy)wtr=#-yLqxm|~qAqz4O-j-jJ{ei6DY6ikrdjVdoXk2G z(^n*L*6-ln^F-JZ`N(O8**1%pJm((o`HgRQ2~>E3#XUT_n0$-DC;rO;O*UC)oky&5 z0es*o>-^3K;4LR?u)~;l*c`FViZnB0@q&H6Vx2u6bHqQX1E0iG`@pHmgKngDc*POhJYYz7s>~>DuQ*|YP1ZSNgSWZU3s!_<$#lxkrqg_#=Sk1*d%&ExWkw``kiRxI5t$-rK<2s@EGDDECXtPa2 z+JEAXY{$0uG*9_+2K&cpnxBT zvdtb3*kLGrjh&SAT6(_CEAHX3Db@0rD(^(>&L0CyeWnfBA|q7J)?J*~*mixU{9Oy^a(a6s;wE4N;Y{ zZmjaCxpmu>NBcYxbT9;ql4914K*UvFe6wUjNX`mSTuuVJ;M{EaNB9?yMR}5xdB6zD zy;b?}vP>9wB8OYJuE<9Z8yL}|OA{A^o+8@h982`MR^oDs3p$EiDaX_cj9wWO+-s`2 zwcJ>gC#xJ&!w-U<1g$&R{7e%tX^LD0UB;Lg3~Ap0t}LWHBN5j<4gXw;Di#ffQ^8O^ zS|XxvI#P2-Fc>L?k$={uPqom#y2n<5{h*og+;U-2o_M?w7RVVk9a_|=(cw&7{fCf; zeLM_CoTnz(xE0D{FcN0fTI~E}T&T0f*Hoz}`;ms|&!$bVE-hM=Ipa5JxbM>9oRXAi zqZm}VnA4{+W?oO@)-oeMo{WUln9A#GnU^sI$cZHNmd^ zAh1=P4I$d&`B?#?=O#G`q7x9|UEACTe&v6`@gKo&AAfLP{Q6G(|21-l#RdCw_*I89 zR_q>fJ~P7KjkI^0`!U)=+SRQ~Yi+hWzMJAlo;(@M7~?vTgvPg2d2B}FwV%-xqma+! zNzA$(s7aqSWj4lh%3?rIHVsXM1^!S`Ql9SdXwJUR$Z$Q0TSc_wCh)}fiNX%K%`r}a zSwWY;Y%^$35+aZkvwj>1{=rmElca12@v+UBdNRyOP!!5@iitg=&-AY+NBA!@is6YT z)FvE@9a@yQxY@IB>Rl2HN*KTvtCXa?B2^q3bTQbH&ih$Z)-b8XqRNkPSmTTyEqY9{ zA=GGKNVTkCQ>6|V9AZ$yqXU#_QYkE`Nu{pIGiOhLvS_746@PyK|6E;pJ&9Y(j7523 zQDzqhk21SdXi)`fobeu47;+UxRPlsC-levrV{j&XsS88(4m_GC3u}&ERjr{hm-6UU z)fyTFO&DlsXlUip(9p`Gp`n#WLqjW%hQ=3&yP5?H!lp!bt`B{xZP*QJ^zj$bcJzkz z%MSgWXFkZAp3jrm{OTd?8cU}+T6yL}xRAw}LwV*2Y1ddX<@s`bp2b3r7u}A0zL0he zJz=mExLU}uK@A62Br|a^F{wm0>GMO5{c)s$Lk$Z*Ai0K1JC;>uzL0he?ei>+;gx;t zN!uje5&Llao1Ld^oi3Yc>TTGeLZ9)}PSYCN=UFNkG&6=Ar*9G;-GDr8>-4bZq;1$I z*DH)~a%zk(LwRoJRJA)5&-$0CaAV(i$`*1wYm@jv?B1lU( zq)Hb9f_y%0+IY0EsIki#EvmTGIb)S7U0^^9n;Hgl8{H00000 LNkvXXu0mjf_?&AN literal 0 HcmV?d00001 diff --git a/doc/html/user_21-58.html b/doc/html/user_21-58.html new file mode 100644 index 0000000..ada07ce --- /dev/null +++ b/doc/html/user_21-58.html @@ -0,0 +1,36 @@ + + + + + + + + + + + + + +
+

8LOADLIN is available for anonymous FTP from
ftp://tsx-11.mit.edu/pub/linux/dos_utils/lodlinn.tar.gz
ftp://sunsite.unc.edu/pub/Linux/system/boot/dualboot/lodlinn.tgz
BOOT.SYS is available for anonymous FTP from
ftp://ftp.funet.fi/pub/Linux/tools/boot142.zip

+ diff --git a/doc/html/user_21-58x.png b/doc/html/user_21-58x.png new file mode 100644 index 0000000000000000000000000000000000000000..99361f069411d2d7c442450335a7d22ba83db66e GIT binary patch literal 4071 zcmaJ^XH*l+(nflbrt~TjK#D+UQUy_|p$I5NssW@*uOda>5R?`}4ZQ~GE%c7G1R_Z2 z9qEK3z3YeHeb4=Qf9&keo-?zv&pbP4_LIJ@IyEI5B>@2ewWh{10|J6uxSO>NIq{7Y z_!z!@GZDVgR)0qD2O2lnexp&iYnXZw5K!IyJ8luArnB5^l6hZIpn*5 zA|Rmk*L?QG$bWh#L&<+;oH4?xo+}*`Ioq>k>+U7-1hayQ$}Ynao4uAG;mDvsJqj== zDmqqkbW)UCNpi8R^Djo11vkOwwjO`D1AkpzMI;s$6{1QksG+!EO%<}9>9wnL`X{*M z8%LOmzK2E%B{5^%kA+CuJ2sJ2#ABUv|GZ}s@IR6p-#xCBE5tVBdnY>{g?@7 z!vbtm#FSuXw!R zt6Ibu&#kdJEQ}W5&x_f7P5cgm(Ts}yb4pOifG9snuAwiRo1xEh%$TSDfPE%hHOarU zsO97xCg3~}5))I)Sf7};hin(E=kqDLH1?5C;nSerZq9C|Z>4?rJO%z(X2;#Y#4N2< zIF4ALpg+sibwz$ETN!iKv|Wd)u!v#BnZLHT&I+sjLRqK9Wlq(;n!x<2c9_J~5=bIK z%JGYWx!AJSzdJb^LAbads@{^_mnCb@9UjL@z#p>2WhJqsB*W>Has{#SUoYH`Zrjpo z|Ea8K%z8o?J|z27XB$I-)`K5t`3xSRIv3rxy*i%G_t-{AOZtbQpK^Ki52WZ}ei)xl zR?lNx(@%kPo5Ux~&&kw5hxOy(&0tTB{PyeQ@BvPH;g<^&+k zv>H`wnBKtly!yi)ijT9pjZATR^L9TdzqOSEU+dxSfZJCOSs~OAhIZ z#RuBSZV&StQMHYs?ueS}txiFGu5fSUR#ef2>Yp~%L-kD?r;?Kq8b}c&9GchW#j<20 zm`7MoJoTu9aQ2_g3~R04H*5g|wp@)`w1yMOHh}z{2f|Fg0QC0xbGrmNCNXuZIk0JJ zL@T2F*jN7C>!lr;WKCXVY}6fi;@%QGo(V~$+_T#L!%5P7?bl(hM!@aDyGGueSKl*=nr_%es-18A??2G!POOp(VH|_|zl`Y2$`;Zskn3ah|Udzh8#0 zKF}CCbwHyBuy*Uy-7%$+>I1W^dhSNGRqp~o7j0cOP3~*X=^8ncht9a?<3Yt7zf&p1 zJN5U>tuI*N%06yChe_Ld^sVI5)yv7zdR-)a)k+zLwK#%2jP&PGgoh+Pj~A7|i_}@*%AtD+GC|)Y zx%PpEq(FoXwrwfl1J^;Q!1m#XegV6UW?24v5evg>yh~Yq_~Z6p2_Ir_QowyBE^!_T zRV*mGN=({Y)<7eiPD~Y-Vf3f|y*ys?UYJ|l2TbwYa;wgn;wQopm1MVqm$EQ@<65gf zJ{KH*>$>*#5~XkpEyxB{YY|q`NQ(WX}$2zh7459Y{jBc|=M4Q9{0zFf9Ax z+A>V#UdD~6Bn5y-K4N$Sm`5g#&Z2MdplY-2e!o+sLljSx`Bf5LDJyUu*%vf;%kWRS z`n}D>lMiujXD}dbtz~Rbq7kKgY-g%}5SObGOR?K|J>)TX|olSPV2q_4t z3yKjI4@qD~b~YMbS3m^4d`5kX8~M!|%mY(#oI5K{vWbm<{AB&hFtWl}xXWLEK3%ae zRLtm?ZGiBBrxJeZARu9{>rn45JB1C~SiVb)TQ`FN_ft7Q41M3Pa6!kyexXvW&27~h zYNpm)Xb4UOUDvLtXPI^U@FFLD!`|#mGJc9LSB*;8Kr=%UJ$swm-&c}tAyP2E>gP7~ ziHWFqH>tfh>u_g}b&5ONL6=`sqS=|~rhxl^(t1#Mp|Aj?-bLUw{B1};X3JxIS-&7w zrp8G4z)J~_=o~si^nA}5_mB{@>*cZBtd?%0w~;q&0eYlhAUYz`ATSh?EN%Ll*sDrZ=&g4w*M~)B`Gt zM5hKY^ZP(CKxsS`R06c`oVM;g;>$abP_4#HoSAv}^-QCl%k##5>ZD8Y z(2W6`VLH`=>v<6`1G9gq8_(s- zUi`fh23mv#v3jYgm(&ufamp*Jd zKA6h~vBU1q*+%_Mn_HQm_n=yN+Zwr)n!F^M@R9{>Buis3e$E+ZM+P?PI@%(U&Zy@7 zBm{_I0EmI&1=Wi6H7V*=E-iMCrk&kV26F$JQqT#IpjEkg`h85?tP9d#Ne7{;d0zA) zox#<VNc_*sCqOo#e-gM zLlh=%LD8f6YPiYEG=X!|h^Mo;hN021$v{GRByb#Bl1}0ijWFOD+gx-_nAl2M-Yr96 zVt@}&hSRmV0AX##rTgL4ylFzVQ@eErD@dMCZ=ThAKaszyUzDH+j7P2l>Q{FSj2Fp$Q#HQn=FtIMhFgwfwlatO3G~+pzrV|%eKb-aXj{RffRrZBox^ALu z#v;f%C-$cFOFWX4bE_Elet~vQ#$L5=BzuR<6Fw^y^imLyQ!jg8JZ;vMqn)9RI8Pi$ z$)*#=OE3wj5QSf+m{Co2=U@rK*?b~Gb?&CoGlyytHRNMo>xzE`6G)$oHlsaVW5-&( zM9ermtqLA3myGlaPSnolcJk1G**Jdwc$v2@8PU@7lG7%RRj2nex2K9T(WtY+Egn;P zJV|2Qizx_z&PWkthj0B~`Dl8xOIyD}njo#*`AV)pQ}5x}BcvrOfce zvh&~NXV&0KkMsWaVo8I(nRisSGg;n&^>@_L=EReqcX}R{F~e`Vu`=swn>*#+lu0wz zt+3MmNpEcj=Hk7m7#%FjEr-H4ZI%;(>ic90(c&hYB@!Civ0PZBok__xrS!%qhqx>&AA`kut zIuq1#ZcS_=y1zD{!SW4Itek5v3yS5IWOjw?89*E33u_GKOgDDWt9~7Kuxz zT==y{i<8WR;KtibIRYiU_$Yj3K# z(2&ui`BB|$TMG&RsDd*M?6yJVYrEp`Mx59_-EcW2$%!@Yju1gSleo5xZ=}|ibJ>}Y zZ11=#5U+I)jAJKi)}Qc{JIB3no$+*Wa#{w7@dM>?&R@r0Sj|?AraXELw}yhflfR)1 zH(ZBk1#i;Y$@W$Z{G>OsH0=a+`JEC@tiX=!ny+LN$y|2Nl8o?XCFBw?K{*h;o%}qN z%{VP*>+$gkXLye&AfuB9F~y?;S796Fgop%^=ihX4_W;41n)SKKxmFBByG94v0W + + + + + + + + + + + + +
+

9LILO can be found in
ftp://tsx-11.mit.edu/pub/linux/packages/lilo/lilo-n.tar.gz
ftp://sunsite.unc.edu/pub/Linux/system/boot/lilo/lilo-n.tar.gz
ftp://lrcftp.epfl.ch/pub/linux/local/lilo/lilo-n.tar.gz

+ diff --git a/doc/html/user_21-59x.png b/doc/html/user_21-59x.png new file mode 100644 index 0000000000000000000000000000000000000000..e53d32d9a8993bb171a340ea84359422d353c13c GIT binary patch literal 2935 zcmV--3yAcIP)K~#9! z?VUe#+sF}zKPN79t`NyD?}@1dbvjp&T-kSxpe}I*$(>yVEbWSvJE_u9Rn8r#>g>uU zJG&#@ovRbo#V-wUot2k&CfV5?Q(y@!zy_}w|Y>x5pbD}z+(EwJkC{Ee3MG==Xnt(x@ z<6O8i@i1AR1Hab~HaoO|b>486Ys(FMidS*kR-rHTy(S*5vD$JcpxX`ac4E{fr4Y4K zqmh$LOxknfcYL@DZ#orf;omKs99ndxznr=8osVQwrfqGS5&=u0N@{FQ#Y7$0%Ynih zY^)1VnY{R&XWfe#bzFACU%S*WXKpik<|_5Mah{W8(|n#9k0)-+V|i--qLUMa-UazX zow-V6*18up?lh%eK0f6cTa2FBz?xe}n44t(%mIfA%dFz@nl50`Vv~DRMQ>xV!Bc#? z0F+o|gF_npogE4od`}B7`H3Z-(%~GN8ta(+#8*CrH1=tV$>3`~^FoO15QB$o^HK5J ziBV9s^IA+JWa?n>GX*wTzp#l*VT3NkwMl;F0*CyA*Vxq9WQh%)vBW39;(!7!1zf(xd{0>y-|>uJ zIj6*Xy0pgD(}>m*4|vK>tb>T-K<)FmK#hu+;X^5W{cT*yCvdUF{|4ZOGhl-*rf}ke z>uu@ofe+!~;NVdUJ&3mWt3*lp+m+_n@pfF=Ve3iiZ7jePp2~2W5pQkL+c`>~Cl7vQ ziDmOC*UjSjvS88|+(fgLzThs>7AI2|;@T8{W=D9ij(GaPT|sLuUc&E;>!K}qFmWc( z(}-4A)aYh-xBYbEvBlV8$Bf6qp@bu9IkYKZ2?7yQk@#9zfU9ujBM01~o4CuQulSv2 zJZ{*Ep`h-F=Lnue)n+4nUF{4nFCTtoiDmH_mu5Q8mj{Es=w74vSUbUaiB_gA#I-5S zcv>O7!N02REv}1%?`RS|jnj%uHN|*tr(SA`*BBqRiu9zJZJlLysc@EX!Pdoy71hoP z?VfSU37b-IxC60Zaqv4kJbVVY91l^C>NUl+WSf4dn&Wv)v+yfREQ`;iG}Cy#JoGqA zcqLoBP2A%Psif&bT$|F+iBWB0)8sy0hGc_)Lop0>kFTelNkowKk+e!NF=$!rQD*Q7 z(Z-?54!7{7*qj5j=}@Omo$^@G|DKpo4IH^;z#sZ8Q&0=}zL+e?)csiBk=ADLQjM_{ zXIg$`iDmH_mu5Q8mx&{6Nn#d8Vk8O-JzW=)+BE9@4km{tuHu_sQWuZd!x843m!6Jg zJcbDUI*C`c9QHARXzq(genSW7V2FFFn4w5Uhc8VWJm4*csO501_$^aV!52P5oO+#( z=pk)PMVs*uv?)E`JouF*mc^%BH;d=XM4e;Fd#JH1jp2ilrJSJ)No^YSexqPkRfMld zk!;Yxo$^@BCGyeJF`{i2FL}ltPWhdCyaY--#^Me>ElhsE;2ZyChZ<|FvdTkNIRQTL zgjGKC33$%|1vcsP5u1HBSdt<$7SGw{J63tXBlh_h$G|sHYa2LJ{EkxyUfC0N`HpjZ z;3JPPDA0;ghga;g!S{4&4Ye8P?G*8UkD>yT~!Ml1A2$BMRTXiN`PSSK&o;nZ;Sr~7%Y(9jD*HLesaehb4k={~BL z2%^skx9D?AzY~od$A&Unloeh{J}A+n!!m|g5R5X+V$z!%2jR%0r)?S41km6e-x5?`vW3M1&e`Xb4Q2gpe&!YTXbUPe-o{n}%nN}`9$|1Ut$i+v zvX9E^S@OCLP(O2nhZpcZ76S+BX`4Duo&R=aCTQ>!)R`tILNoV|roPIu$HQ zl`1r2_t!J)d(uMq^%?dou;*-e`DgggAG69NZRY_aZ1-C2hd0W2PH2i_-iU7Q2%9E#DpY84B(DBbbbs6U81$%SZm@A>ji*JOIz^87 z9ZO8zRuV(8pHZHUb$o(+Kr=Lzm5F%v!n(7e%*mA78yO?7PcE0mKz=d_rr90ko9eMk zjnWmE$Y$d9$i67Z*H6n>A19MN-us$igsdopmu$gF_&~!v`4nj=`z%+=Qs3Y%@E`sM z{0QOS^3>{t?J4}Gy%8&R_o$APiyOuKd`IP8jh*KvgLlxavU!1Bmf=kWrR{njMQ(Cx9d zpO|js87-IULh8f(WD>mDs1t4QV#bO0!Uqfn`TFS@>*<;7Dy)R+~eCoqi^a{5)5`RfE8@Y;ieO1 z96VYWtg|ac$kNJ99PR@Zexr_$O&OauRluYOoZwLfj%jj&&ljK>wvenZzl`S0eU>w{ zc~Ms6>@iTpU{xj{T`r4@S!H5TWD5tMB3qQGQwAy=af&M@awU3{@r72k zs4VChJQi;1!cctzkCw^ImZMiyYiLYmJbG2NhQ^!%1{xX~+ITcHwDD+YXyeh)(8i;o zaRYH%i(p3B?9!U*L!asxc7qCSf_$c?KCph#p}+G?2l>$RX*M=jCuujryxHzG%sjnz zmZOblIz$UuoGFY)ouq9@r6p}Vi*7tO*XNln<#^WP$kURvjd1Z~Q){OV7%VC#OF1^E z;NXf}BuC^W$%pg>DaXM$;^9!iB1lNC;L=F!Dx*%)?op>j4Httm?eS=zXOSmfZHO9>_p6eN^b`wX2!(WHejf2V4cqzxD4vFt1?oB&7eSoy&brXX#pvN)mS9^1e zn}F+SJmY^eA*Lki=v?e1{a9&Q;sJ&)PB6< z$ Primary-site: http://lilo.alioth.debian.org/ Original-site: http://lilo.alioth.debian.org/ Alternate-site: http://alioth.debian.org/projects/lilo/ (developer's site) -Files: 561kB lilo-23.1.tar.gz +Files: 751kB lilo-24.0.tar.gz Platforms: Linux (>= 2.4.0), gcc (>= 3.3.5), as86 (>= 0.16.14) needed to compile. bcc (0.16.14) needed to compile diagnostic disk 2 & DOS *.com. - LaTeX and (optionally) Perl and Transfig needed to print the - documentation. Copying-policy: BSD-License End diff --git a/make.vars b/make.vars index c38e694..4e47243 100644 --- a/make.vars +++ b/make.vars @@ -1,6 +1,6 @@ ### Configuration variables for makefiles ### # -# Copyright 2009-2011 Joachim Wiedorn +# Copyright 2009-2013 Joachim Wiedorn # All rights reserved. # # Licensed under the terms contained in the file 'COPYING' diff --git a/man/Makefile b/man/Makefile index 05ae551..a980969 100644 --- a/man/Makefile +++ b/man/Makefile @@ -1,25 +1,41 @@ +#!/usr/bin/make -f # -*- makefile -*- # adding variables include ../make.vars +PODFILES := lilo-uuid-diskid lilo liloconfig +MANFILES5 := lilo.conf +MANFILES8 := keytab-lilo lilo-uuid-diskid lilo liloconfig mkrescue + all: +build: + for PF in $(PODFILES); do \ + sh ./pod2manpage $$PF.pod; \ + done + install: mkdir -p $$DESTDIR$(MAN_DIR)/man5 - mkdir -p $$DESTDIR$(MAN_DIR)/man8 + for MF in $(MANFILES5); do \ + install -m 0644 $$MF.5 $$DESTDIR$(MAN_DIR)/man5; \ + done - install -m 0644 lilo.8 $$DESTDIR$(MAN_DIR)/man8 - install -m 0644 mkrescue.8 $$DESTDIR$(MAN_DIR)/man8 - install -m 0644 lilo.conf.5 $$DESTDIR$(MAN_DIR)/man5 - install -m 0644 keytab-lilo.8 $$DESTDIR$(MAN_DIR)/man8 + mkdir -p $$DESTDIR$(MAN_DIR)/man8 + for MF in $(MANFILES8); do \ + install -m 0644 $$MF.8 $$DESTDIR$(MAN_DIR)/man8; \ + done clean: distclean: uninstall: - rm -f $$DESTDIR$(MAN_DIR)/man8/lilo.8 - rm -f $$DESTDIR$(MAN_DIR)/man8/mkrescue.8 - rm -f $$DESTDIR$(MAN_DIR)/man5/lilo.conf.5 - rm -f $$DESTDIR$(MAN_DIR)/man8/keytab-lilo.8 + for MF in $(MANFILES5); do \ + rm -vf $$DESTDIR$(MAN_DIR)/man5/$$MF.5 || true; \ + done + + for MF in $(MANFILES8); do \ + rm -vf $$DESTDIR$(MAN_DIR)/man8/$$MF.8 || true; \ + done + diff --git a/man/lilo-uuid-diskid.8 b/man/lilo-uuid-diskid.8 new file mode 100644 index 0000000..facfd7b --- /dev/null +++ b/man/lilo-uuid-diskid.8 @@ -0,0 +1,118 @@ +.\" Automatically generated by Pod::Man 2.22 (Pod::Simple 3.07) +.\" +.\" Standard preamble: +.\" ======================================================================== +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Vb \" Begin verbatim text +.ft CW +.nf +.ne \\$1 +.. +.de Ve \" End verbatim text +.ft R +.fi +.. +.\" Set up some character translations and predefined strings. \*(-- will +.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left +.\" double quote, and \*(R" will give a right double quote. \*(C+ will +.\" give a nicer C++. Capital omega is used to do unbreakable dashes and +.\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, +.\" nothing in troff, for use with C<>. +.tr \(*W- +.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' +.ie n \{\ +. ds -- \(*W- +. ds PI pi +. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch +. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch +. ds L" "" +. ds R" "" +. ds C` "" +. ds C' "" +'br\} +.el\{\ +. ds -- \|\(em\| +. ds PI \(*p +. ds L" `` +. ds R" '' +'br\} +.\" +.\" Escape single quotes in literal strings from groff's Unicode transform. +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" +.\" If the F register is turned on, we'll generate index entries on stderr for +.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index +.\" entries marked with X<> in POD. Of course, you'll have to process the +.\" output yourself in some meaningful fashion. +.ie \nF \{\ +. de IX +. tm Index:\\$1\t\\n%\t"\\$2" +.. +. nr % 0 +. rr F +.\} +.el \{\ +. de IX +.. +.\} +.\" ======================================================================== +.\" +.IX Title "LILO-UUID-DISKID 8" +.TH LILO-UUID-DISKID 8 "2013-05-01" "23.3" "lilo documentation" +.\" For nroff, turn off justification. Always turn off hyphenation; it makes +.\" way too many mistakes in technical documents. +.if n .ad l +.nh +.SH "NAME" +lilo\-uuid\-diskid \- convert boot / root options to diskid and uuid in lilo.conf. +.SH "SYNOPSIS" +.IX Header "SYNOPSIS" +\&\fBlilo-uuid-diskid\fR [\fB\-h\fR] [\fB\-v\fR] [\fBlilo.conf\fR] +.SH "DESCRIPTION" +.IX Header "DESCRIPTION" +This script looks for the boot block device or boot partition and create the +right diskid or uuid as boot option. Then it looks for all root partitions +and create the right uuids as root options. +.PP +These conversions are necessary for use with newer kernel (>= 2.6.26) if it +use the libata module for parallel and serial \s-1ATA\s0 interfaces of block devices +(i. e. hard disks with \s-1IDE\s0 or \s-1SATA\s0 interface, usbsticks). +.SH "OPTIONS" +.IX Header "OPTIONS" +.IP "\fB\-h\fR" 4 +.IX Item "-h" +Print a brief help. +.IP "\fB\-v\fR" 4 +.IX Item "-v" +Print verbose messages. +.SH "EXAMPLES" +.IX Header "EXAMPLES" +Lines in the configuration file /etc/lilo.conf: +.PP +.Vb 2 +\& #boot = /dev/sda +\& boot = /dev/disk/by\-id/ata\-SAMSUNG_SV1604N_S01FJ10X999999 +\& +\& #root = /dev/sda1 +\& root = "UUID=/dev/disk/by\-uuid/18843936\-00f9\-4df0\-a373\-000d05a5dd44" +.Ve +.SH "COPYRIGHT and LICENSE" +.IX Header "COPYRIGHT and LICENSE" +Copyright (C) 2010\-2013 Joachim Wiedorn +.PP +This script is free software; you can redistribute it and/or modify +it under the terms of the \s-1GNU\s0 General Public License as published by +the Free Software Foundation; either version 2 of the License, or +(at your option) any later version. +.SH "AUTHOR" +.IX Header "AUTHOR" +\&\fBlilo-uuid-diskid\fR was written by Joachim Wiedorn. +.PP +This manual page was written by Joachim Wiedorn . +.SH "SEE ALSO" +.IX Header "SEE ALSO" +\&\fBlilo\fR(8), \fBupdate-lilo\fR(8), \fBliloconfig\fR(8) diff --git a/man/lilo-uuid-diskid.pod b/man/lilo-uuid-diskid.pod new file mode 100644 index 0000000..3d43ba1 --- /dev/null +++ b/man/lilo-uuid-diskid.pod @@ -0,0 +1,71 @@ +=for header +manpage: LILO-UUID-DISKID +section: 8 +title: lilo documentation +version: 23.3 +datum: 2013-05-01 + +=encoding utf8 + +=head1 NAME + +lilo-uuid-diskid - convert boot / root options to diskid and uuid in lilo.conf. + +=head1 SYNOPSIS + +B [B<-h>] [B<-v>] [B] + +=head1 DESCRIPTION + +This script looks for the boot block device or boot partition and create the +right diskid or uuid as boot option. Then it looks for all root partitions +and create the right uuids as root options. + +These conversions are necessary for use with newer kernel (>= 2.6.26) if it +use the libata module for parallel and serial ATA interfaces of block devices +(i. e. hard disks with IDE or SATA interface, usbsticks). + +=head1 OPTIONS + +=over 4 + +=item B<-h> + +Print a brief help. + +=item B<-v> + +Print verbose messages. + +=back + +=head1 EXAMPLES + +Lines in the configuration file /etc/lilo.conf: + + #boot = /dev/sda + boot = /dev/disk/by-id/ata-SAMSUNG_SV1604N_S01FJ10X999999 + + #root = /dev/sda1 + root = "UUID=/dev/disk/by-uuid/18843936-00f9-4df0-a373-000d05a5dd44" + +=head1 COPYRIGHT and LICENSE + +Copyright (C) 2010-2013 Joachim Wiedorn + +This script is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 2 of the License, or +(at your option) any later version. + +=head1 AUTHOR + +B was written by Joachim Wiedorn. + +This manual page was written by Joachim Wiedorn . + +=head1 SEE ALSO + +B(8), B(8), B(8) + +=cut diff --git a/man/lilo.8 b/man/lilo.8 index 9309925..02512f4 100644 --- a/man/lilo.8 +++ b/man/lilo.8 @@ -1,496 +1,474 @@ -'\" t -.\" @(#)lilo.8 1.0 950728 aeb -.\" This page is based on the lilo docs, which carry the following -.\" COPYING condition: +.\" Automatically generated by Pod::Man 2.22 (Pod::Simple 3.07) .\" -.\" LILO program code, documentation and auxiliary programs are -.\" Copyright 1992-1998 Werner Almesberger. -.\" Extensions to LILO, documentation and auxiliary programs are -.\" Copyright 1999-2005 John Coffman. -.\" All rights reserved by the respective copyright holders. -.\" -.\" Redistribution and use is subject to the terms set forth in -.\" the file COPYING in the source directory. +.\" Standard preamble: +.\" ======================================================================== +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Vb \" Begin verbatim text +.ft CW +.nf +.ne \\$1 +.. +.de Ve \" End verbatim text +.ft R +.fi +.. +.\" Set up some character translations and predefined strings. \*(-- will +.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left +.\" double quote, and \*(R" will give a right double quote. \*(C+ will +.\" give a nicer C++. Capital omega is used to do unbreakable dashes and +.\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, +.\" nothing in troff, for use with C<>. +.tr \(*W- +.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' +.ie n \{\ +. ds -- \(*W- +. ds PI pi +. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch +. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch +. ds L" "" +. ds R" "" +. ds C` "" +. ds C' "" +'br\} +.el\{\ +. ds -- \|\(em\| +. ds PI \(*p +. ds L" `` +. ds R" '' +'br\} .\" -.\" Original version, Andries Brouwer (aeb@cwi.nl), 950728 -.\" Added t directive, as Daniel Quinlan asked, 950824 -.\" Added L switch, John Coffman, 991118 -.\" Added T switch, John Coffman, 001001 -.\" Added p switch, John Coffman, 010402 -.\" Added x switch, John Coffman, 010409 -.\" Added A switch, John Coffman, 010417 -.\" Added M switch, John Coffman, 010417 -.\" Added g switch, John Coffman, 010526 -.\" Added z switch, John Coffman, 010829 -.\" Added E switch, John Coffman, 020409 -.\" Added B,F & X switches, John Coffman, 020418 -.\" Added "k" option to I switch, John Coffman, 020609 -.\" Added Z switch, John Coffman, 030314 -.\" Added I switch options "D" and "a", John Coffman, 030513 -.\" Added I switch option "R", John Coffman, 041116 -.\" Added H switch, John Coffman, 050927 +.\" Escape single quotes in literal strings from groff's Unicode transform. +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' .\" -.TH LILO 8 "07 Oct 2005" -.SH NAME -lilo \- install boot loader -.SH SYNOPSIS +.\" If the F register is turned on, we'll generate index entries on stderr for +.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index +.\" entries marked with X<> in POD. Of course, you'll have to process the +.\" output yourself in some meaningful fashion. +.ie \nF \{\ +. de IX +. tm Index:\\$1\t\\n%\t"\\$2" +.. +. nr % 0 +. rr F +.\} +.el \{\ +. de IX +.. +.\} +.\" ======================================================================== +.\" +.IX Title "LILO 8" +.TH LILO 8 "2013-05-01" "23.3" "lilo documentation" +.\" For nroff, turn off justification. Always turn off hyphenation; it makes +.\" way too many mistakes in technical documents. +.if n .ad l +.nh +.SH "NAME" +lilo \- install boot loader of LiLO +.SH "SYNOPSIS" +.IX Header "SYNOPSIS" Main function: -.LP -.B " /sbin/lilo" -\- install boot loader -.LP +.PP + +  +\&\fBlilo\fR +.PP Auxiliary uses: -.LP -.B " /sbin/lilo -A" -\- activate/show active partition -.br -.B " /sbin/lilo -E" -\- edit header or update a bitmap file -.br -.B " /sbin/lilo -I" -\- inquire path name of current kernel -.br -.B " /sbin/lilo -M " -\- write a Master Boot Loader on a device -.br -.B " /sbin/lilo -q" -\- query map -.br -.B " /sbin/lilo -R" -\- set default command line for next reboot -.br -.B " /sbin/lilo -T" -\- tell more about specified topic -.br -.B " /sbin/lilo {-u|-U}" -\- uninstall LILO boot loader -.SH DESCRIPTION -.LP -.B lilo -installs a boot loader that will be activated the next time you boot your -system. The default configuration file -.I "/etc/lilo.conf" -(see 'man lilo.conf') will contain most options, but many, including -those which override the -configuration file, may be specified on the command line. -.LP -.TP -.BI "\-\^A " "master-device [ N ]" -Used with a single argument, inquire of active partition on device -.IR master-device ; -e.g., \fI/dev/hda\fP. With N==0, deactivate all partitions on the device. With -N in the range [1..n], activate the specified partition and deactivate all -others. Normally, only primary partitions [1..4] may be activated, but if -the Extended Master Boot Loader is present on the Master Boot Record -of the device -(see the \fI-M\fP option), any partition may be made active. Whether the -actual OS in the partition will boot from an extended partition depends on -the characteristics of the OS. LILO boot records for Linux -may be booted from an extended partition. -.TP -.BI "\-\^b " bootdev -Specify the boot device; i.e., where the boot loader will be installed. -"\-b /dev/hda" specifies the Master Boot Record; "\-b /dev/sdb5" specifies -the first extended partition on the second SCSI disk. -.TP -.BI "\-\^B " bitmap-file -Specify a bitmap file for the boot-time graphics screen, preferably one -already pre-processed with the 'lilo \-E' command. -.TP -.B "\-\^c" -Enable map compaction. This will merge read requests from adjacent -sectors. Speeds up the booting (especially from floppy). -.TP -.BI "\-\^C " config-file -.B lilo -Specify an alternate pathname for the configuration file. -This option overrides the use of the default configuration file, -.IR "/etc/lilo.conf" . -.TP -.BI "\-\^d " delay -Specifies the delay time in tenths of a second (20 = 2 sec) before -automatically booting the first image. Gives you time to interrupt the -automatic boot process with Shift, Alt, Ctrl, ScrollLock, or CapsLock. If -interrupted, the `boot:' prompt is displayed. This switch is overridden by -the appearance of -.I prompt -in the configuration file. -.TP -.BI "\-\^D " label -Use the kernel with the given label, instead of the first one -in the list, as the default kernel to boot. -.TP -.BI "\-\^E " filename.ext -If \fB.ext\fP is \fB.bmp\fP, then take the file to be a bitmap graphic file -for use in the "bitmap=" configuration file directive. Enter an interactive -editor to create or update the color/placement information in the -bitmap file LILO header. (see 'bmp-colors', 'bmp-table', and 'bmp-timer' -on the man page for 'lilo.conf(5)'.) -.sp -If \fB.ext\fP is \fB.dat\fP, then take the file to be a configuration file which -specifies bitmap graphic parameters, which are transferred into the LILO -header in the bitmap file of the same name. -.sp -When a \fB.bmp\fP file is modified using a graphics editor (e.g., GIMP), the -LILO header will be lost. It can be restored using the \fB.dat\fP file, -which is used as a text-based backup for the LILO header information. -.TP -.BI "\-\^f " disk-tab -Specify disk geometry parameter file. (The default is -.IR /etc/disktab .) -.TP -.BI "\-\^F" -Override boot sector check for filesystems (e.g., swap, XFS, ...) which might be -destroyed by the installation of the LILO boot sector on the first sector of -the partition. These filesystems use the first sector as a superblock. +.PP -Compare with "\-P ignore", which bypasses certain partition table checks. -.TP -.BI "\-\^g" -Generate cylinder/head/sector (geometric) disk addresses. Limited to -cylinders up to 1023. Forces compatibility with older versions of LILO. -.TP -.BI "\-\^H" -Override fatal halt when a RAID array does not have all disks active. -.TP -.BI "\-\^i " boot-loader -Specify a file to be used as the new boot loader. (The default is -.IR /boot/boot.b .) -.TP -.BI "\-I " "label [D|a|i|k|r|R]" -.B label -is taken to be the name of an image specified in the configuration file. +  +\&\fBlilo\fR \fB\-A\fR # activate/show active partition +  +\&\fBlilo\fR \fB\-E\fR # edit header or update a bitmap file +  +\&\fBlilo\fR \fB\-I\fR # inquire path name of current kernel +  +\&\fBlilo\fR \fB\-M\fR # write a Master Boot Loader on a device +  +\&\fBlilo\fR \fB\-q\fR # query map and show its content +  +\&\fBlilo\fR \fB\-R\fR # set default command line for next reboot +  +\&\fBlilo\fR \fB\-T\fR # tell more about specified topic +  +\&\fBlilo\fR \fB{\-u|\-U}\fR # uninstall LiLO boot loader +.SH "DESCRIPTION" +.IX Header "DESCRIPTION" +lilo installs a boot loader that will be activated the next time you boot +your system. The default configuration file \fI/etc/lilo.conf\fR (see manpage +\&\fIlilo.conf\fR\|(5)) will contain most options, but many, including those which +override the configuration file, may be specified on the command line. +.SH "OPTIONS" +.IX Header "OPTIONS" +.IP "\fB\-A\fR \fImaster-device [N]\fR" 4 +.IX Item "-A master-device [N]" +Used with a single argument, inquire of active partition on device \fImaster-device\fR; +e.g. \fI/dev/sda\fR. With N==0: deactivate all partitions on the device. With N in +the range [1..n]: activate the specified partition and deactivate all others. +Normally, only primary partitions [1..4] may be activated, but if the 'Extended +Master Boot Loader' is present on the Master Boot Record (\s-1MBR\s0) of the device +(see the \-M option), any partition may be made active. Whether the actual \s-1OS\s0 +in the partition will boot from an extended partition depends on the characteristics +of the \s-1OS\s0. \s-1LILO\s0 boot records for Linux may be booted from an extended partition. +.IP "\fB\-b\fR \fIbootdev\fR" 4 +.IX Item "-b bootdev" +Set the boot device where the boot loader will be installed. For example +\&\fI\*(L"\-b /dev/sda\*(R"\fR set the Master Boot Record (\s-1MBR\s0) on the first disk as boot +device. \fI\*(L"\-b /dev/sdb5\*(R"\fR set the first extended partition on the second disk +as boot device. +.IP "\fB\-B\fR \fIbitmap-file\fR" 4 +.IX Item "-B bitmap-file" +Define a bitmap file for the boot-time graphics screen, preferably one already +pre-processed with the \fI\-E\fR option. +.IP "\fB\-c\fR" 4 +.IX Item "-c" +Enable map compaction. This will merge read requests from adjacent sectors. +Speeds up the booting especially from floppy. +.IP "\fB\-C\fR \fIconfig-file\fR" 4 +.IX Item "-C config-file" +Set another pathname and filename for the configuration file. The default +configuration file is \fI/etc/lilo.conf\fR. +.IP "\fB\-d\fR \fIdelay-time\fR" 4 +.IX Item "-d delay-time" +Set the delay time in tenths of a second ('20' = 2 sec) before automatically +booting the first image. This give you time to interrupt the automatic boot +process with: Shift, Alt, Ctrl, ScrollLock, or CapsLock. If interrupted, the +\&\fIboot:\fR prompt will be displayed. +.Sp +This switch will be overridden by the appearance of \fIprompt\fR in the +configuration file! +.IP "\fB\-D\fR \fIlabel\fR" 4 +.IX Item "-D label" +Use the kernel with the given label as the default kernel to boot, instead of +the first one in the list of the configuration file. +.IP "\fB\-E\fR \fIfilename.xxx\fR" 4 +.IX Item "-E filename.xxx" +If the extension \fB.xxx\fR is \fB.bmp\fR, then take the file to be a bitmap graphic file +for use in the \fIbitmap=\fR configuration file directive. Enter an interactive +editor to create or update the color/placement information in the \s-1LILO\s0 header +of this bitmap file. (see \fIbmp-colors\fR, \fIbmp-table\fR, and \fIbmp-timer\fR on the +manual page for \fIlilo.conf (5)\fR.) +.Sp +If \fB.xxx\fR is \fB.dat\fR then take this file to be a configuration file to set bitmap +graphic parameters, which are transferred into the \s-1LILO\s0 header in the bitmap file +of the same name. +.Sp +When a \fB.bmp\fR file is modified using a graphics editor (e.g. \s-1GIMP\s0), the \s-1LILO\s0 +header will be lost. It can be restored using the \fBdat\fR file, which is used as +a text-based backup for the \s-1LILO\s0 header information. +.IP "\fB\-f\fR \fIdisk-tab\fR" 4 +.IX Item "-f disk-tab" +Set another disk geometry parameter file. The default is \fI/etc/disktab\fR. +.IP "\fB\-F\fR" 4 +.IX Item "-F" +Override boot sector check for filesystems (e.g., swap, ext4, xfs ...) which +might be destroyed by the installation of the \s-1LILO\s0 boot sector on the first +sector of the partition if these filesystems use the first sector as a superblock. +.Sp +Compare with \fI\-P ignore\fR, which bypasses certain partition table checks. +.IP "\fB\-g\fR" 4 +.IX Item "-g" +Generate 'cylinder/head/sector' (\s-1CHS\s0 geometric) disk addresses. Limited to cylinders +up to 1023. Forces compatibility with very old versions of \s-1LILO\s0 \fI(obsolete switch)\fR. +.IP "\fB\-H\fR" 4 +.IX Item "-H" +Override fatal halt if a \s-1RAID\s0 array does not have all disks active. +.IP "\fB\-I\fR \fIlabel [D|a|i|k|r|R]\fR" 4 +.IX Item "-I label [D|a|i|k|r|R]" +\&\fBlabel\fR is taken to be the name of an image specified in the configuration file. This command will print the path name of the corresponding kernel file, keytable -file, initial ramdisk file, root specification, or "append=" -string ("i", "k", "r", "R", or "a" option). -The "D" option ignores the -.B label -parameter, and prints the default "image=" label, or first "image=" label -if no default -.BI image -is specified. -.TP -.BI "\-\^l" -Generate 24-bit linear sector addresses instead of cylinder/head/sector -addresses. -.TP -.BI "\-\^L" -Generate 32-bit Logical Block Addresses instead of cylinder/head/sector -addresses, allowing -access to all partitions on disks with more than 1024 cylinders. -.TP -.BI "\-\^m " map-file -Use specified map file instead of the default. -.TP -.BI "\-\^M " "master-device " "[mbr|ext]" -Install a Master Boot Record on the device specified as -.IR master-device , -selecting the Standard or Extended Master Boot Loader per the option. -The primary partition table on -.I master-device -is undisturbed. If no valid Volume-ID (serial number) -is present, then generate one -and write it to the MBR. If \fBmbr\fP is specified, the Standard Master -Boot Loader -will search partitions 1-4 for an active flag, and boot the flagged -partition. Only one active flag is allowed. If \fBext\fP is specified, the -search for an active partition will include extended partitions as well. -The presence of the Extended Master Boot Loader on the -Master Boot Record (MBR = sector 0) of a disk -affects the operation of the \fI-A\fP option. -.TP -.BI "\-\^p" -Require interactive entry of all passwords specified as -.B """""" -in the configuration file. -.TP -.BI "\-\^P " "{fix|ignore|\}" -Fix or ignore `corrupt' partition tables, i.e., partition tables -with linear and cylinder/head/sector addresses that do not correspond. -Always try -.I -P ignore -first, as -.I -P fix -will re-write the partition table, possibly destroying all partitions -on the disk. - -.I -P ignore -is also used to bypass the partition table check for partition types within -the partition table which -might not allow the installation of a LILO boot sector. Compare with the -"\-F" flag, which overrides the check of the actual boot sector. - -.I "-P " -allows the passing of any global option which may appear in the global -section (top) of the configuration file (/etc/lilo.conf). For instance, -.I -P nowarn -will pass the "nowarn" option, just as though "nowarn" appeared in the -configuration file (same as the "\-w" switch). Similarly, -.I -P timeout=50 -will add or override the "timeout=" line in the configuration file. Note -that the general -.I -P -switch actually duplicates a number of command line option switches. -However, it is not strictly the same as some switches whick cause an -override of other options; e.g., "\-g" (\-P geometric), "\-L" (\-P lba32). -.TP -.B \-\^q -List the currently mapped files. -.B lilo -maintains a file, by default -.IR "/boot/map" , -containing the name and location of the kernel(s) to boot. -This option will list the names therein. Use with \fB-v\fP for -more detailed information about the installed boot loader. -.TP -.BI "\-\^r " root-directory -Before doing anything else, do a \fIchroot\fP to the indicated -directory. The new root directory must contain a -.I /dev -directory, and may need a -.I /boot -directory. It may also need an -.IR /etc/lilo.conf " file." -.TP -.BI "\-\^R " "command line" -This option sets the default command for the boot loader the next -time it executes. The boot loader will then erase this line: this -is a once-only command. It is typically used in reboot scripts, -just before calling `shutdown \-r'. Used without any arguments, it will -cancel a \fIlock\fP-ed or \fIfallback\fP command line. -.TP -.BI "\-\^s " save-file -When -.B lilo -writes a new boot sector, it preserves the former contents of the sector -in a file, named by default \fI/boot/boot.NNNN\fP, -where NNNN is the hexadecimal representation of the major and minor -device numbers of the drive/partition. This option specifies the backup -save file in one of three ways: a save directory (default is '/boot') using -the default filename 'boot.NNNN' in the specified directory; a pathname template -to which '.NNNN' is appended (default would be '/boot/boot'); -or the full pathname of the file, which must include the correct '.NNNN' -suffix. When used with the -\fB-u\fP option, the full file pathname must be specified. -.TP -.BI "\-\^S " save-file -Normally, -.B lilo -will not overwrite an existing boot sector save file. This options says -that overwriting is to be forced. As with \fB-s\fP, the specification may be of a -save directory, pathname template, or full pathname (which includes the '.NNNN' -suffix.) -.TP -.BI "\-\^t " -Test only. Do not really write a new boot sector or map file. -Use together with \fB-v\fP to find out what -.B lilo -is about to do. -.TP -.BI "\-\^T " option -Print out system information, some of it extracted from the system -bios. This is more convenient than booting the LILO diagnostic -floppy on problem systems. -.I option +file, initial ramdisk file, root specification, or \*(L"append=\*(R" string (\*(L"i\*(R", \*(L"k\*(R", +\&\*(L"r\*(R", \*(L"R\*(R", or \*(L"a\*(R" option). The \*(L"D\*(R" option ignores the \fBlabel\fR parameter and +prints the default \*(L"image=\*(R" label, or the first \*(L"image=\*(R" label is selected if +no default \fBimage\fR is set. +.IP "\fB\-l\fR" 4 +.IX Item "-l" +Generate 24\-bit linear sector addresses instead of cylinder/head/sector addresses. +.IP "\fB\-L\fR" 4 +.IX Item "-L" +Generate 32\-bit Logical Block Addresses (\s-1LBA\s0) instead of cylinder/head/sector (\s-1CHS\s0) +addresses, allowing access to all partitions on disks with more than 1024 cylinders. +(This is the default geometry). +.IP "\fB\-m\fR \fImap-file\fR" 4 +.IX Item "-m map-file" +Use another map file instead of the default file /boot/map. +.IP "\fB\-M\fR \fImaster-device\fR \fB{mbr|ext}\fR" 4 +.IX Item "-M master-device {mbr|ext}" +Install a Master Boot Record on the device specified as master-device, selecting +the Standard or Extended Master Boot Loader per option. The primary partition +table on master-device is undisturbed. If no valid Volume-ID (serial number) is +present, then generate one and write it to the \s-1MBR\s0. If \fImbr\fR is set, the +Standard Master Boot Loader will search partitions 1\-4 for an active flag, and +boot the flagged partition. Only one active flag is allowed. If \fIext\fR is set, +the search for an active partition will include extended partitions as well. +The presence of the Extended Master Boot Loader on the Master Boot Record +(\s-1MBR\s0 = sector 0) of a disk affects the operation of the \fI\-A\fR option. +.IP "\fB\-p\fR" 4 +.IX Item "-p" +Require interactive entry of all passwords set as "" in the configuration file. +.IP "\fB\-P\fR \fI{fix|ignore|" 4 +.IX Item "-P {fix|ignore|" +Fix or ignore 'corrupt' partition tables, e.g. partition tables with linear and +cylinder/head/sector addresses that do not correspond. Always try \fBignore\fR +first, as \fBfix\fR will re-write the partition table, possibly destroying all +partitions on the disk. +.Sp +\&\fBignore\fR is also used to bypass the partition table check for partition types +within the partition table which might not allow the installation of a \s-1LILO\s0 boot +sector. Compare with the '\-F' flag, which overrides the check of the actual +boot sector. +.Sp +\&\fB\fR allows the passing of any global option which may +appear in the global section (top) of the configuration file (\fI/etc/lilo.conf\fR). +For instance \fI'\-P nowarn'\fR will pass the 'nowarn' option, just as though 'nowarn' +appeared in the configuration file (same as the '\-w' switch). Similarly +\&\fI'\-P timeout=50'\fR will add or override the 'timeout=' line in the configuration +file. Note that the general \fB\-P\fR switch actually duplicates a number of command +line option switches. However, it is not strictly the same as some switches which +cause an override of other options; e.g. '\-g' (\-P geometric), '\-L' (\-P lba32). +.IP "\fB\-q\fR" 4 +.IX Item "-q" +List the currently mapped files. \fBlilo\fR maintains a file, by default \fI/boot/map\fR, +containing each name and location of the kernel(s) to boot. This option will list +the names therein. Use with \fB\-v\fR for more detailed information about the +installed boot loader. +.IP "\fB\-r\fR \fIroot-directory\fR" 4 +.IX Item "-r root-directory" +Before doing anything else, do a \fI'chroot'\fR to the indicated directory. The new +root directory must contain a \fI/dev\fR directory and may need a /boot directory. +It may also need an \fI/etc/lilo.conf\fR file. +.IP "\fB\-R\fR \fIcommand-line\fR" 4 +.IX Item "-R command-line" +This option sets the default command for the boot loader for the next time it +executes. After execution the boot loader will erase this line because it is a +once-only command. It is typically used in reboot scripts, just before calling +\&'shutdown \-r'. Used without any arguments, it will cancel a \fIlock\fR\-ed or +\&\fIfallback\fR command line. +.IP "\fB\-s\fR \fIsave-file\fR" 4 +.IX Item "-s save-file" +When lilo writes a new boot sector, it preserves the former contents of the boot +sector in a file, named by default /boot/boot.NNNN, where \s-1NNNN\s0 is the hexadecimal +representation of the major and minor device numbers of the drive/partition. +.Sp +This option defines the backup save file in one of three ways: a save directory +(default is '/boot') using the default filename 'boot.NNNN' in the defined +directory; a pathname template to which '.NNNN' is appended (default would be +\&'/boot/boot'); or the full pathname of the file, which must include the correct +\&'.NNNN' suffix. When used with the \-u option, the full file pathname must be set. +.IP "\fB\-S\fR \fIsave-file\fR" 4 +.IX Item "-S save-file" +Normally lilo will not overwrite an existing boot sector save file. This options +says that overwriting is to be forced. As with \-s, the setting may be of a save +directory, pathname template, or full pathname (which includes the '.NNNN' suffix). +.IP "\fB\-t\fR" 4 +.IX Item "-t" +Test only. Do not really write a new boot sector or map file. Use together with +\&\fB\-v\fR to find out what lilo is about to do. +.IP "\fB\-T\fR \fIoption\fR" 4 +.IX Item "-T option" +Print out system information, some of it extracted from system bios. This is more +convenient than booting the \s-1LILO\s0 diagnostic floppy on problem systems. \fBoption\fR may be any one of the following: -.IP -.nf - help - print a list of available diagnostics - ChRul - list the partition types subject to - Change-Rules - EBDA - list Extended BIOS Data Area information - geom= list drive geometry for bios drive; - e.g., geom=0x80 - geom - list drive geometry for all drives - table= list the primary partition table; - e.g., table=/dev/sda - video - list graphic modes available to boot - loader -.fi -.TP -.BI "\-\^u " [device-name] -Uninstall \fIlilo\fP by copying the saved boot sector back. -The '\-s' and '\-C' switches may be used with this option. -The \fIdevice-name\fP is optional. A time-stamp is checked. -.TP -.BI "\-\^U " [device-name] -Idem, but do not check the time-stamp. -.TP -.B "\-\^v" -Increase verbosity. Giving one to five \fB-v\fP options -will make lilo more verbose, or use, \fB-v\fP \fIn\fP (n=1..5) to -set verbosity level '\fIn\fP'. -.TP -.B "\-\^V" +.Sp +.Vb 11 +\& help print a list of available diagnostics +\& ChRul list the partition types subject to +\& Change\-Rules +\& EBDA list Extended BIOS Data Area information +\& geom= list drive geometry for bios drive; +\& e.g. geom=0x80 +\& geom list drive geometry for all drives +\& table= list the primary partition table; +\& e.g. table=/dev/sda +\& video list graphic modes available to boot +\& loader +.Ve +.IP "\fB\-u\fR \fI[device\-name]\fR" 4 +.IX Item "-u [device-name]" +Uninstall lilo by copying the saved boot sector back. The \fB\-s\fR and \fB\-C\fR switches +may be used with this option. The device-name is optional. A time-stamp is +checked. +.IP "\fB\-U\fR \fI[device\-name]\fR" 4 +.IX Item "-U [device-name]" +The same as '\-u', but do not check the time-stamp. +.IP "\fB\-v\fR \fI[number]\fR" 4 +.IX Item "-v [number]" +Increase verbosity. Giving one to five \fB\-v\fR options will make lilo more verbose. +The \fBnumber\fR (range 1..5) set verbosity level. +.IP "\fB\-V\fR" 4 +.IX Item "-V" Print version number. -.TP -.B "\-\^w" -Used as \fB-w\fP or \fB-w-\fP, suppress warning messages. -Used as \fB-w+\fP, override \fInowarn\fP in -the configuration file, and show warning messages. -.TP -.BI "\-\^x " option -For RAID installations only. The option may be any of the keywords -.IR none , -.IR auto , -.IR mbr , -.IR mbr-only , -or a comma separated list of additional boot devices (no spaces allowed in -the list). -.TP -.BI "\-\^X" -Reserved for LILO internal use. May produce different -output for different LILO versions. The line beginning "CFLAGS=" -will contain the compiler options used to generate this version of LILO. -.TP -.B "\-\^z" -When used with the `\-M' switch, clears the Volume-ID. Usually used -in the following sequence to generate a new Volume-ID: -.nf - lilo \-z \-M /dev/hda - lilo \-M /dev/hda -.fi -.br -.TP -.BI "\-\^Z " option -Tells the boot installer whether special precautions need to be taken -because the BIOS fails to pass the correct device code in DL (\-Z0). Or may -specify that the BIOS always gets DL right (\-Z1). Corresponds to, and -overrides, the configuration file option 'bios-passes-dl='. -.LP -The above command line options correspond to the key words -in the config file indicated below. -.IP -.TS -l l. -\-b bootdev boot=bootdev -\-B file.bmp bitmap=file.bmp -\-c compact -\-d dsec delay=dsec -\-D label default=label -\-i boot-loader install=boot-loader -\-f file disktab=file -\-g geometric -\-l linear -\-L lba32 -\-m mapfile map=mapfile -\-P fix fix-table -\-P ignore ignore-table -\-s file backup=file -\-S file force-backup=file -\-v [N] verbose=N -\-w nowarn -\-x option raid-extra-boot=option -\-Z option bios-passes-dl=option -.TE +.IP "\fB\-w\fR\fI[+|\-]\fR" 4 +.IX Item "-w[+|-]" +Used as \fB\-w\fR or \fB\-w\-\fR to suppress warning messages. Used as '\-w+' to override +\&\fI'nowarn'\fR in the configuration file and show warning messages. +.IP "\fB\-x\fR \fIoption\fR" 4 +.IX Item "-x option" +For \s-1RAID\s0 installations only. The option may be any of the keywords: \fInone\fR, +\&\fIauto\fR, \fImbr\fR, \fImbr-only\fR, or a comma separated list of additional boot +devices (no spaces allowed in the list). +.Sp +\&\s-1RAID\s0 installations write the boot record to the \s-1RAID\s0 partition. Conditional +writing of MBRs may occur to aid in making the \s-1RAID\s0 set bootable in a recovery +situation, but all default actions may be overridden. Action similar to previous +versions is achieved using the \fI'\-x mbr\-only'\fR switch. +.IP "\fB\-X\fR" 4 +.IX Item "-X" +Reserved for \s-1LILO\s0 internal use. May produce different output for different \s-1LILO\s0 +versions. The line beginning \*(L"CFLAGS=\*(R" will contain the compiler options used to +generate this version of \s-1LILO\s0. +.IP "\fB\-z\fR" 4 +.IX Item "-z" +When used with the '\-M' switch, clears the Volume-ID. Usually used in the +following sequence to generate a new Volume-ID: +.Sp +.Vb 2 +\& lilo \-z \-M /dev/hda +\& lilo \-M /dev/hda +.Ve +.IP "\fB\-Z\fR \fIoption\fR" 4 +.IX Item "-Z option" +Tells the boot installer whether special precautions need to be taken because +the \s-1BIOS\s0 fails to pass the correct device code in \s-1DL\s0 (\-Z0). Or may specify +that the \s-1BIOS\s0 always gets \s-1DL\s0 right (\-Z1). Corresponds to, and overrides, the +configuration file option 'bios\-passes\-dl='. +.SH "CONFIG OPTIONS" +.IX Header "CONFIG OPTIONS" +The above command line options correspond to the key words in the config file +indicated below. +.PP +.Vb 1 +\& \-b bootdev boot=bootdev +\& +\& \-B file.bmp bitmap=file.bmp +\& \-c compact +\& \-d dsec delay=dsec +\& \-D label default=label +\& \-f file disktab=file +\& \-g geometric +\& \-l linear +\& \-L lba32 +\& \-m mapfile map=mapfile +\& \-P fix fix\-table +\& \-P ignore ignore\-table +\& \-s file backup=file +\& \-S file force\-backup=file +\& \-v [N] verbose=N +\& \-w nowarn +\& \-x option raid\-extra\-boot=option +\& \-Z option bios\-passes\-dl=option +.Ve .SH "BOOT OPTIONS" -The options described here may be specified at boot time on -the command line when a -kernel image is booted. These options are processed by LILO, and are -removed from the command line before it is passed to the kernel, -unless otherwise noted. -.LP -.TP -.BI lock -Locks the command line, as though 'lock' had been specified in 'lilo.conf.' -.TP -.BI "mem=###[,K,M,G]" -Specifies the maximum memory in the system in bytes, kilobytes, megabytes, -or gigabytes. -This option is not removed from the command line, and is always passed to -the kernel. -.TP -.BI nobd -Suppresses the BIOS data check. This option is reserved for use with -non-IBM-compliant BIOS's which hang with the lines: -.sp -.nf - Loading............... - BIOS data check -.fi -.TP -.BI "vga=[ASK,EXT,EXTENDED,NORMAL,###,0x###]" +.IX Header "BOOT OPTIONS" +The options described here may be specified at boot time on the command line +when a kernel image is booted. These options are processed by \s-1LILO\s0, and are +removed from the command line before it is passed to the kernel, unless otherwise +noted. +.IP "\fBlock\fR" 4 +.IX Item "lock" +Locks the command line, as though 'lock' had been defined in \fI/etc/lilo.conf\fR. +.IP "\fBmem=###[,K,M,G]\fR" 4 +.IX Item "mem=###[,K,M,G]" +Set the maximum memory in the system in bytes, kilobytes, megabytes or gigabytes. +This option is not removed from the command line, and is always passed to the +kernel. +.IP "\fBnobd\fR" 4 +.IX Item "nobd" +Suppresses the \s-1BIOS\s0 data check. This option is reserved for use with +non-IBM-compliant \s-1BIOS\s0's which hang with the lines: +.Sp +.Vb 2 +\& Loading............... +\& BIOS data check +.Ve +.IP "\fBvga=[\s-1ASK\s0,EXT,EXTENDED,NORMAL,###,0x###]\fR" 4 +.IX Item "vga=[ASK,EXT,EXTENDED,NORMAL,###,0x###]" Allows overriding the default video mode upon kernel startup. -.br -.SH BOOT ERRORS -The boot process takes place in two stages. The first stage loader is a -single sector, and is loaded by the BIOS or by the loader in the MBR. It -loads the multi-sector second stage loader, but is very space limited. When -the first stage loader gets control, it types the letter "L"; when it is -ready to transfer control to the second stage loader it types the letter -"I". If any error occurs, like a disk read error, it will put out a -hexadecimal error code, and then it will re-try the operation. All hex -error codes are BIOS return values, except for the lilo-generated 40, 99 and 9A. -A partial list of error codes follows: -.br -.IP -.TS -l l. -00 no error -01 invalid disk command -02 address mark not found -03 disk write-protected -04 sector not found -06 floppy disk removed -08 DMA overrun -0A bad sector flag -0B bad track flag -20 controller failure -40 seek failure (BIOS) -40 cylinder>1023 (LILO) -99 invalid second stage index sector (LILO) -9A no second stage loader signature (LILO) -AA drive not ready -FF sense operation failed -.TE -.br -.LP -Error code 40 is generated by the BIOS, or by LILO during the conversion of -a linear (24-bit) disk address to a geometric (C:H:S) address. On older -systems which do not support lba32 (32-bit) addressing, this error may also -be generated. Errors 99 and 9A usually mean the map file (\-m or map=) is -not readable, likely because LILO was not re-run after some system change, -or there is a geometry mis-match between what LILO used (lilo \-v3 to -display) and what is actually being used by the BIOS (one of the lilo -diagnostic disks, available in the source distribution, may be needed to -diagnose this problem). - -When the second stage loader has received control from the first stage, it -prints the letter "L", and when it has initialized itself, including -verifying the "Descriptor Table" \- the list of kernels/others to boot \- it -will print the letter "O", to form the full word "LILO", in uppercase. - -All second stage loader error messages are English text, and try to -pinpoint, more or less successfully, the point of failure. -.br -.SH INCOMPATIBILITIES -.B lilo -is known to have problems with the -.I reiserfs -introduced with the 2.2.x kernels, unless the file system is -mounted with the 'notail' option. This incompatibility has been -resolved with reiserfs 3.6.18 and lilo 21.6. -.I reiser4 -introduced with the 2.5.x kernels requires lilo 22.5.2 or later. -.sp -Beginning with version 22.0, RAID installations write the boot record to -the RAID partition. Conditional writing of MBRs may occur to aid in making -the RAID set bootable in a recovery situation, but all default actions may -be overridden. Action similar to previous versions is -achieved using the `\-x mbr-only' switch. -.SH BUGS -Configuration file options `backup' and `force-backup' -should specify a backup directory or backup file pathname template on -all RAID installations. Use of an explicit filename may not allow multiple -backup files to be created correctly. It is best to use the default mechanism, -as it works correctly in all cases. +.SH "BOOT ERRORS" +.IX Header "BOOT ERRORS" +The boot process takes place in two stages. The first stage loader is a single +sector, and is loaded by the \s-1BIOS\s0 or by the loader in the \s-1MBR\s0. It loads the +multi-sector second stage loader, but is very space limited. When the first +stage loader gets control, it types the letter 'L'; when it is ready to +transfer control to the second stage loader it types the letter 'I'. If any +error occurs, like a disk read error, it will put out a hexadecimal error code +and then re-try the operation. All hex error codes are \s-1BIOS\s0 return values, +except for the lilo-generated codes: 40, 99 and 9A. A partial list of error +codes follows: +.PP +.Vb 10 +\& 00 no error +\& 01 invalid disk command +\& 02 address mark not found +\& 03 disk write\-protected +\& 04 sector not found +\& 06 floppy disk removed +\& 08 DMA overrun +\& 0A bad sector flag +\& 0B bad track flag +\& 20 controller failure +\& 40 seek failure (BIOS) +\& 40 cylinder>1023 (LILO) +\& 99 invalid second stage index sector (LILO) +\& 9A no second stage loader signature (LILO) +\& AA drive not ready +\& FF sense operation failed +.Ve +.PP +Error code 40 is generated by the \s-1BIOS\s0, or by \s-1LILO\s0 during the conversion of a +linear (24\-bit) disk address to a geometric (C:H:S) address. On older systems +which do not support lba32 (32\-bit) addressing, this error may also be generated. +Errors 99 and 9A usually mean the map file ('\-m' or 'map=') is not readable, +likely because \s-1LILO\s0 was not re-run after some system change, or there is a +geometry mismatch between what \s-1LILO\s0 used (lilo \-v3 to display) and what is +actually being used by the \s-1BIOS\s0 (one of the lilo diagnostic disks, available +in the source distribution, may be needed to diagnose this problem). +.PP +When the second stage loader has received control from the first stage, it +prints the letter 'L', and when it has initialized itself, including verifying +the \*(L"Descriptor Table\*(R" \- the list of kernels/others to boot \- it will print +the letter \*(L"O\*(R", to form the full word \*(L"\s-1LILO\s0\*(R", in uppercase. +.PP +All second stage loader error messages are English text and try to pinpoint, +more or less successfully, the point of failure. +.SH "BUGS" +.IX Header "BUGS" +Configuration file options 'backup' and 'force\-backup' should specify a backup +directory or backup file pathname template on all \s-1RAID\s0 installations. Use of an +explicit filename may not allow multiple backup files to be created correctly. +It is best to use the default mechanism, as it works correctly in all cases. +.SH "COPYRIGHT and LICENSE" +.IX Header "COPYRIGHT and LICENSE" +.Vb 3 +\& Copyright (C) 1992\-1998 Werner Almesberger +\& Copyright (C) 1999\-2007 John Coffman +\& Copyright (C) 2009\-2013 Joachim Wiedorn +.Ve +.PP +Redistribution and use in source and binary forms, with or without +modification, are permitted under the terms of the \s-1BSD\s0 license found in +the \s-1COPYING\s0 file. +.SH "AUTHOR" +.IX Header "AUTHOR" +\&\fBlilo\fR was written by: +.PP +.Vb 3 +\& Werner Almesberger (version 0 to 21), +\& John Coffman (version 21.2 to 22.8), +\& Joachim Wiedorn (since version 23.0). +.Ve +.PP +This manual page was written by Werner Almesberger and Joachim Wiedorn +. .SH "SEE ALSO" -fdisk(8), lilo.conf(5), mkrescue(8), mkinitrd(8). -.sp -The lilo distribution comes with very extensive TeX documentation through -Version 21. Text file README's in the source directory provide updates on -more recent topics. -.SH "AUTHORS" -Werner Almesberger (versions 0 to 21) -.br -John Coffman (21.2 to present date) +.IX Header "SEE ALSO" +\&\fBlilo.conf\fR(5), +\&\fBliloconfig\fR(8), +\&\fBlilo-uuid-diskid\fR(8), +\&\fBmkrescue\fR(8), +\&\fBfdisk\fR(8), +\&\fBmkinitrd\fR(8) diff --git a/man/lilo.conf.5 b/man/lilo.conf.5 index c769b4d..557646b 100644 --- a/man/lilo.conf.5 +++ b/man/lilo.conf.5 @@ -1,5 +1,5 @@ '\" t -.\" @(#)lilo.conf.5 1.0 950728 aeb +.\" @(#)lilo.conf.5 .\" This page is based on the lilo docs, which carry the following .\" COPYING condition: .\" @@ -7,6 +7,9 @@ .\" Copyright 1992-1998 Werner Almesberger. .\" Extensions to LILO, documentation and auxiliary programs are .\" Copyright 1999-2005 John Coffman. +.\" Extensions to LILO, documentation and auxiliary programs are +.\" Copyright 2009-2011 Joachim Wiedorn. +.\" .\" All rights reserved by the respective copyright holders. .\" .\" Redistribution and use in source and binary forms of parts of or the @@ -16,7 +19,7 @@ .\" this software without specific prior written permission. This work .\" is provided "as is" and without any express or implied warranties. .\" -.TH LILO.CONF 5 "April 2011" +.TH LILO.CONF 5 "June 2011" .SH NAME lilo.conf \- configuration file for lilo .SH DESCRIPTION @@ -69,22 +72,22 @@ other=/dev/hdb5 This configuration file specifies that lilo uses the Master Boot Record on /dev/hda. (For a discussion of the various ways to use lilo, and the interaction with other operating systems, -see user.tex from the lilo documentation.) +see user.pdf from the lilo documentation.) .LP When booting, the boot loader will issue its .I "boot:" -prompt and wait for you to enter the label of the kernel (and any options) -which you wish to boot. At any time you may hit [Tab] to see -a list of kernel/other labels. +prompt and wait for you to enter the label of the kernel (and any +options) which you wish to boot. At any time you may hit [Tab] to +see a list of kernel/other labels. Alternately, if the \fBmenu\fP boot loader is installed, a menu of boot options will be presented for your selection. The title of this menu is overridden with the menu title specification in this configuration file. -If you enter nothing, -then the default kernel image, the first mentioned, (/boot/zImage-1.5.99) -will be booted after a timeout of 15 seconds (150 deciseconds). -There may be at least 16 images mentioned in lilo.conf. (The exact number depends -upon compilation options.) +If you enter nothing, then the default kernel image, the first +mentioned, (in the example /boot/vmlinuz-2.6.29-1-i386) will be +booted after a timeout of 15 seconds (150 deciseconds). There may +be at least 16 images mentioned in lilo.conf. (The exact number +depends upon compilation options.) .LP As can be seen above, a configuration file starts with a number of global options (the top 9 lines in the example), @@ -95,7 +98,7 @@ Comment lines may appear anywhere, and begin with the "#" character. .SH "GLOBAL OPTIONS" There are many possible keywords. The description below is -almost literally from user.tex (just slightly abbreviated). +almost literally from user.pdf (just slightly abbreviated). .TP .BI "backup=" Specifies the location where a copy of any modified boot sector will be @@ -119,8 +122,8 @@ loader in the DL register. Its only function at this point is experimental, as certain RAID installations may benefit from knowing that the BIOS is 100% reliable. Its use should be considered experimental. .sp -N.B.: This option may not be retained in releases beyond 22.5.1, and -may be specified on the command line with the '\-Z' switch: yes=1, no=0. +This option may be specified on the command line with the '\-Z' switch: +yes=1, no=0. .TP .BI "bitmap=" Specifies use of a 640x480x16 (VGA BIOS) or 640x480x256 (VGA/VESA BIOS) @@ -138,12 +141,12 @@ From a text file with all the information about 'bmp-colors', 'bmp-table' and 'bmp-timer' options together with the 'bitmap' option are stored in the special LILO header of the bitmap image file by the .BI "lilo -E" -+command. Another way works without these special header information: All -+the information about 'bmp-colors', 'bmp-table' and 'bmp-timer' options -+together with the 'bitmap' option are stored in the configuration file. -+Any use of the 'bmp-' options within the configuration file overrides -+the options stored in the bitmap file header. If lilo cannot find any of -+the 'bmp-' options, then default values are used. +command. Another way works without these special header information: All +the information about 'bmp-colors', 'bmp-table' and 'bmp-timer' options +together with the 'bitmap' option are stored in the configuration file. +Any use of the 'bmp-' options within the configuration file overrides +the options stored in the bitmap file header. If lilo cannot find any of +the 'bmp-' options, then default values are used. .TP .BI "bmp-colors=" ,,,,, Specifies the decimal values of the colors to be used for the menu display @@ -184,14 +187,12 @@ then the form 'bmp-timer = none' is acceptable. This will disable the timer display entirely. .TP .BI "boot=" -Sets the name of the device (e.g. a hard disk partition) that contains -the boot sector. If this keyword is omitted, the boot sector is read -from (and possibly written to) the device that is currently mounted as root. +Sets the name of the device (e.g. hard disk or partition) that contains +the boot sector and where the new boot sector should be written to. Notice: +The boot-device should be the device with the currently mounted root partition. .sp A raid installation is initiated by specifying a RAID1 device as the boot -device; e.g., "boot=/dev/md0". Note that LILO version 22.0 and later -operate differently from earlier versions with respect to the actual -location of the boot records. +device; e.g., "boot=/dev/md0". .sp On newer systems you need an unique ID for the boot device. If the boot sector should write to a partition you can use its UUID in the same manner @@ -230,7 +231,7 @@ rules are sufficient. The strings which define the partition types are used in a .I change section (see below), with the suffixes "_normal" or "_hidden" appended. -See section "Partition type change rules" of user.tex for more details. +See section "Partition type change rules" of user.pdf for more details. .TP .BI "compact" Tries to merge read requests for adjacent sectors into a single @@ -260,7 +261,7 @@ This action is modified by specifying `prompt' (see below). .TP .BI "disk=" Defines non-standard parameters for the specified disk. -See section "Disk geometry" of user.tex for details. +See section "Disk geometry" of user.pdf for details. For versions of LILO prior to 22.5, the `bios=' parameter is quite useful for specifying how the BIOS has assigned device codes to your disks. @@ -707,17 +708,26 @@ If the booted image is a Linux kernel, then one may pass command line parameters to this kernel. .TP .BI "addappend=" -(22.6) The kernel parameters from the specified string, are concatenated to the +The kernel parameters of this string are concatenated to the parameter(s) from an .B "append=" -specification (see below). -The string must be enclosed within double quotes. Usually, the previous +option (see below). +The string of addappend must be enclosed within double quotes. +Usually, the previous .B "append=" -will specify parameters common to all kernels by appearing in the top, -or global, section of the configuration file and +will set parameters common to all kernels by appearing in the global +section of the configuration file and .B "addappend=" will be used to add local parameter(s) to an individual image. -Addappend= may be used only once per "image=" section. +The addappend option may be used only once per "image=" section. +.sp +If the string is a very long line, this line can be divided +in more lines using "\\" as last character of a line, e.g. +.sp +.nf + addappend="noapic acpi=off pci=usepirqmask \\ + pnpbios=off pnpacpi=off noisapnp" +.fi .TP .BI "append=" Appends the options specified to the parameter line passed to the kernel. @@ -726,14 +736,16 @@ entirely auto-detected or for which probing may be dangerous. Multiple kernel parameters are separated by a blank space, and the string must be enclosed in double quotes. A local append= appearing withing an image= section overrides any -global append= appearing in the top section of the configuration file. -Append= may be used only once per "image=" +global append= appearing in the global section of the configuration file. +The append option may be used only once per "image=" section. To concatenate parameter strings, use "addappend=". Example: .sp .nf append="mem=96M hd=576,64,32 console=ttyS1,9600" .fi .sp +If the string is a very long line, this line can be divided in more lines +using "\\" as last character of a line. See example of addappend option. .TP .BI "initrd=" Specifies the initial ramdisk image to be loaded with the kernel. The @@ -769,9 +781,8 @@ If the special name is used, the root device is set to the device on which the root file system is currently mounted. If the root has been changed with \-r , the respective device is used. If the variable `root' is omitted, -the root device setting contained in the kernel image is used. -(And that is set at compile time using the ROOT_DEV variable in -the kernel Makefile, and can later be changed with the rdev(8) program.) +the root device setting contained in the running kernel image is used. +Warning: This can induce to an unbootable system! .sp The root filesystem may also be specified by a .B LABEL= @@ -855,11 +866,6 @@ in its boot sector.) Note that /sbin/lilo must be re-run if a partition table mapped referenced with `table' is modified. .TP -.BI "table=" -This option is obsolete. It were used in the special case with the obsolete -.I os2_d -chain loader. -.TP .BI "change" This keyword starts a section which describes how primary partition IDs are changed, and how primary partitions are activated and deactivated. If diff --git a/man/lilo.pod b/man/lilo.pod new file mode 100644 index 0000000..602c857 --- /dev/null +++ b/man/lilo.pod @@ -0,0 +1,451 @@ +=for header +manpage: LILO +section: 8 +title: lilo documentation +version: 23.3 +datum: 2013-05-01 + +=encoding utf8 + +=head1 NAME + +lilo - install boot loader of LiLO + +=head1 SYNOPSIS + +Main function: + +E<10> E<8> +B + +Auxiliary uses: + +E<10> E<8> +B B<-A> # activate/show active partition E<10> E<8> +B B<-E> # edit header or update a bitmap file E<10> E<8> +B B<-I> # inquire path name of current kernel E<10> E<8> +B B<-M> # write a Master Boot Loader on a device E<10> E<8> +B B<-q> # query map and show its content E<10> E<8> +B B<-R> # set default command line for next reboot E<10> E<8> +B B<-T> # tell more about specified topic E<10> E<8> +B B<{-u|-U}> # uninstall LiLO boot loader + +=head1 DESCRIPTION + +lilo installs a boot loader that will be activated the next time you boot +your system. The default configuration file F (see manpage +lilo.conf(5)) will contain most options, but many, including those which +override the configuration file, may be specified on the command line. + +=head1 OPTIONS + +=over 4 + +=item B<-A> I + +Used with a single argument, inquire of active partition on device I; +e.g. I. With N==0: deactivate all partitions on the device. With N in +the range [1..n]: activate the specified partition and deactivate all others. +Normally, only primary partitions [1..4] may be activated, but if the 'Extended +Master Boot Loader' is present on the Master Boot Record (MBR) of the device +(see the -M option), any partition may be made active. Whether the actual OS +in the partition will boot from an extended partition depends on the characteristics +of the OS. LILO boot records for Linux may be booted from an extended partition. + +=item B<-b> I + +Set the boot device where the boot loader will be installed. For example +I<"-b /dev/sda"> set the Master Boot Record (MBR) on the first disk as boot +device. I<"-b /dev/sdb5"> set the first extended partition on the second disk +as boot device. + +=item B<-B> I + +Define a bitmap file for the boot-time graphics screen, preferably one already +pre-processed with the I<-E> option. + +=item B<-c> + +Enable map compaction. This will merge read requests from adjacent sectors. +Speeds up the booting especially from floppy. + +=item B<-C> I + +Set another pathname and filename for the configuration file. The default +configuration file is F. + +=item B<-d> I + +Set the delay time in tenths of a second ('20' = 2 sec) before automatically +booting the first image. This give you time to interrupt the automatic boot +process with: Shift, Alt, Ctrl, ScrollLock, or CapsLock. If interrupted, the +I prompt will be displayed. + +This switch will be overridden by the appearance of I in the +configuration file! + +=item B<-D> I