X-Git-Url: https://git.rrq.au/?a=blobdiff_plain;f=man%2Flilo.8;h=b12bc79514ded2117e502dc0dc00eef79eb00d4b;hb=5e2488fd48f0fd96df446672285aa92114d1eca7;hp=c16e6da92e148285ad90d4791917a8751d15d511;hpb=e05a6f05e7fce66ac7560e066d995c456073d29f;p=rrq%2Fmaintain_lilo.git diff --git a/man/lilo.8 b/man/lilo.8 index c16e6da..b12bc79 100644 --- a/man/lilo.8 +++ b/man/lilo.8 @@ -1,4 +1,4 @@ -.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16) +.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== @@ -38,6 +38,8 @@ . ds PI \(*p . ds L" `` . ds R" '' +. ds C` +. ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. @@ -48,21 +50,28 @@ .\" 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" +.\" +.\" Avoid warning from groff about undefined register 'F'. +.de IX .. -. nr % 0 -. rr F -.\} -.el \{\ -. de IX +.nr rF 0 +.if \n(.g .if rF .nr rF 1 +.if (\n(rF:(\n(.g==0)) \{ +. if \nF \{ +. de IX +. tm Index:\\$1\t\\n%\t"\\$2" .. +. if !\nF==2 \{ +. nr % 0 +. nr F 2 +. \} +. \} .\} +.rr rF .\" ======================================================================== .\" .IX Title "LILO 8" -.TH LILO 8 "2014-10-15" "24.1" "lilo documentation" +.TH LILO 8 "2015-11-22" "24.2" "lilo documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l @@ -113,7 +122,7 @@ 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 a logical partition depends on the characteristics -of the \s-1OS\s0. \s-1LILO\s0 boot records for Linux may be booted from a logical partition. +of the \s-1OS. LILO\s0 boot records for Linux may be booted from a logical 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 @@ -173,7 +182,7 @@ 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. +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. @@ -201,7 +210,7 @@ Use another map file instead of the default file /boot/map. 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 +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 logical partitions as well. @@ -327,7 +336,7 @@ versions is achieved using the \fI'\-x mbr\-only'\fR switch. .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. +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 @@ -340,7 +349,7 @@ following sequence to generate a new Volume-ID: .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 +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" @@ -372,7 +381,7 @@ indicated below. .SH "BOOT OPTIONS" .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 +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 @@ -392,13 +401,13 @@ non-IBM-compliant \s-1BIOS\s0's which hang with the lines: \& Loading............... \& BIOS data check .Ve -.IP "\fBvga=[\s-1ASK\s0,EXT,EXTENDED,NORMAL,###,0x###]\fR" 4 +.IP "\fBvga=[\s-1ASK,EXT,EXTENDED,NORMAL\s0,###,0x###]\fR" 4 .IX Item "vga=[ASK,EXT,EXTENDED,NORMAL,###,0x###]" Allows overriding the default video mode upon kernel startup. .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 +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 @@ -426,19 +435,19 @@ codes follows: \& 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 +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 +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. +the letter \*(L"O\*(R", to form the full word \*(L"\s-1LILO\*(R",\s0 in uppercase. .PP All second stage loader error messages are English text and try to pinpoint, more or less successfully, the point of failure.