2 Subject: fix for manpage lilo.conf.5
3 Author: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
4 Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902711
6 Last-Update: 2018-09-09
8 Fix the warning: (macro BI): only 1 argument, but more are expected.
11 diff -urN s08/man/lilo.conf.5 s09/man/lilo.conf.5
12 --- s08/man/lilo.conf.5 2016-07-15 22:02:52.000000000 +0200
13 +++ s09/man/lilo.conf.5 2018-09-09 15:41:31.019967938 +0200
15 From a text file with all the information about 'bmp-colors', 'bmp-table'
16 and 'bmp-timer' options together with the 'bitmap' option are stored in
17 the special LILO header of the bitmap image file by the
20 command. Another way works without these special header information: All
21 the information about 'bmp-colors', 'bmp-table' and 'bmp-timer' options
22 together with the 'bitmap' option are stored in the configuration file.
24 then "none" is assumed. The list entries are separated by commas, with no
29 Option applies to all 'image=' and 'other=' sections.
30 (See COMMON OPTIONS, below.)
33 boot = /dev/disk/by-id/ata-SAMSUNG_SV1604N_S01FJ10X999999
38 Defines boot-time changes to partition type numbers (`hiding').
42 See section "Partition type change rules" of html/user_21-5.html inside
43 the old documentation for more details.
47 Tries to merge read requests for adjacent sectors into a single
48 read request. This drastically reduces load time and keeps the map file
49 smaller. Using `compact' is especially recommended when booting
52 probably only useful for floppy disks and loopback devices,
53 because for hard disks the
56 disk addressing option ignores disk geometry.
58 Developers who have implemented a disk driver for a new block storage
61 if `disktab' is omitted. The use of disktabs is discouraged.
63 -.BI "el-torito-bootable-CD"
64 +.B el-torito-bootable-CD
65 Flag second stage loader to terminate disk emulation when booting
66 from an El Torito Bootable CD. This option is used by the
67 \fBmkrescue\fP utility when the "\-\-iso" switch is specified.
71 This allows lilo to adjust 3D addresses in partition tables. Each
72 partition entry contains a 3D (cylinder/head/sector) and a linear
73 address of the first and the last sector of the partition. If a
75 Operation is identical to \fBbackup=\fP above, except an existing backup
76 file is unconditionally overwritten if it exists.
80 Force disk addressing which is compatible with older versions of LILO.
81 Geometric addressing uses cylinder/head/sector addresses, and is limited to
82 disk cylinders up to 1023. If inaccessible cylinders are referenced,
83 diagnostics will be issued at boot-install time, rather than boot-time.
84 With a newer BIOS, use of 'lba32' is recommended.
88 tells lilo to ignore corrupt partition tables.
90 .BI "install=" <user-interface>
92 (Prior to LILO version 22.3, `install=' specified the user interface as
93 a file in the `/boot' directory.)
97 Normally any initial ramdisk (initrd) loaded with a kernel is loaded as
98 high in memory as possible, but never above 15Mb. This is due to a BIOS
99 limitation on older systems. On newer systems, this option enables using
101 kernel documentation for the kernel command line parameter
102 "mem=" for limiting the memory used by the kernel.)
106 Generate 32-bit Logical Block Addresses instead of cylinder/head/sector
107 addresses. If the BIOS supports packet addressing, then packet calls will be
108 used to access the disk. This allows booting from any partition on disks
110 all post-1998 systems. Beginning with LILO version 22, 'lba32' is the
111 default disk addressing scheme.
115 Generate 24-bit linear sector addresses instead of cylinder/head/sector
116 (geometric) addresses. Linear addresses are translated at run time to
117 geometric addresses, and are limited to cylinders <= 1023. When using
118 @@ -426,12 +426,12 @@
119 recent BIOS (post-1998). The 'linear' option is considered obsolete,
120 and its use is strongly discouraged.
124 Enables automatic recording of boot command lines as the defaults
125 for the following boots. This way, lilo "locks" on a choice until it is
130 The per-image password option `mandatory' (see below) applies to all images.
132 .BI "map=" <map-file>
134 message file is changed or moved. 'message=' and 'bitmap=' are mutually
140 Disables pre-loading of the internal device cache. May be needed for
141 Linux distributions which use non-standard device naming conventions;
143 The keyboard detection codes cannot detect the presence or absence of
144 a newer USB keyboard.
148 Disables the automatic marking of disk volumes which are components of
149 RAID arrays as \fBinaccessible\fP. This allows the user to edit the \fBdisk=\fP
150 / \fBinaccessible\fP declarations into the configuration file himself. Without
151 @@ -521,10 +521,10 @@
152 confusing situations at boot-time, and possible failure to boot. The use
153 of this keyword is generally not necessary.
157 Disables warnings about possible future dangers.
161 The per-image option `optional' (see below) applies to all images.
163 .BI "password=" <password>
165 protected at the default level `mandatory', which is a level higher than
170 Automatic booting (see `delay' above) will not take place unless a locked or
171 pre-stored ("lilo \-R") command line is present. Instead, the boot
172 loader will issue the
174 one way to have it written. Use of \fImbr\fP is the other way to force
175 writing to the MBR of device 0x80.
179 The per-image password option `restricted' (see below) applies to all images.
181 .BI "serial=" <parameters>
182 @@ -606,13 +606,13 @@
184 Example: "serial=0,2400n8" initializes COM1 with the default parameters.
188 This option specifies that boot images or 'other's are to be selected and
189 launched with a single keystroke. Selection is based upon the first
190 character of each name, which must be unique. This option should not be
191 used with the menu or bitmap user interface ("install=").
193 -.BI "static-BIOS-codes"
194 +.B static-BIOS-codes
195 Causes the operation of the boot installer and boot loader to bypass the
196 use of Volume-ID information, and to revert to a mode of operation of
197 versions of LILO from 22.4 backward. With Volume-ID booting (22.5 and later),
199 In general, this option should
200 never be used, except as a bug workaround.
202 -.BI "suppress-boot-time-BIOS-data"
203 +.B suppress-boot-time-BIOS-data
204 This global option suppresses the boot-time real mode collection of BIOS data
205 on systems which hang on certain BIOS calls. It is equivalent to using the
206 boot-time switch 'nobd'.
208 If no key is pressed for the specified time, the default image is
209 automatically booted. The default timeout is infinite.
213 (22.6) Alters the operation of the "timeout" parameter in a manner which
215 noisy serial lines. Each typed (or noise) character restarts the "timeout"
216 @@ -765,13 +765,13 @@
217 zero indicates that no RAM disk should be created. If this variable is
218 omitted, the RAM disk size configured into the boot image is used.
222 This specifies that the root file system should be mounted read-only.
223 It may be specified as a global option.
224 Typically, the system startup procedure re-mounts the root
225 file system read-write later (e.g. after fsck'ing it).
229 This specifies that the root file system should be mounted read-write.
230 It may be specified as a global option.
233 Note that /sbin/lilo must be re-run if a partition table mapped referenced
234 with `table' is modified.
238 This keyword starts a section which describes how primary partition IDs are
239 changed, and how primary partitions are activated and deactivated. If
242 interfere with floppy disk BIOS device codes; "boot-as=" is then used as a
243 local option to override "master-boot" as necessary.
247 This flag (LILO version 22.5) indicates a DOS/Windows or other
248 system which will only boot from BIOS device 0x80, the "C:" drive, or BIOS
249 device 0, the A: drive. When this
251 This option is largely
252 rendered obsolete by "boot-as=", introduced with LILO version 22.5.
256 Do not access the boot sector at map creation time. This disables
257 some sanity checks, including a partition table check. If the boot
258 sector is on a fixed-format floppy disk device, using UNSAFE avoids the
260 .BR image= " and " other=
261 cases, the following options apply.
265 No password is required to boot this image. Used to indicate that the global
266 password does not apply to this `image=' or `other='. See 'password=' below.
270 A second name for the same entry can be used by specifying an alias.
274 The bitmap graphic (install=bmp) is retained when control is passed to the
275 loaded kernel image, or other= bootloader; i.e., the screen is not
276 blanked to alphanumeric mode before starting the kernel. This feature is
277 @@ -999,19 +999,19 @@
278 command line if the current image is booted. This is useful when
279 experimenting with kernels which may crash before allowing interaction
280 with the system. If using the
283 option, the next reboot (e.g.
284 triggered by a manual reset or by a watchdog timer) will load a
285 different (supposedly stable) kernel. The command line stored by the fallback
286 mechanism is cleared by removing or changing the default command line
290 option, which should be a part of the boot startup scripts.
298 Omit the image if it is not available at map creation time.
299 It may be specified as a global option.
300 This is useful to specify test kernels that are not always present.
301 @@ -1032,11 +1032,11 @@
302 will be issued telling you to re-run \fIlilo \-p\fP to force re-creation of the
307 A password is required to boot this image. This is the default. May be used
308 on a single `image=' or `other=' to override a different global setting.
313 The specified descriptor is not bootable if the IBM-PC keyboard is not present.
314 This option is really only useful if the "serial=" boot terminal is in use.
315 @@ -1046,17 +1046,17 @@
321 A password is only required to boot the image if kernel parameters
322 are specified on the command line (e.g. 'single'). May be used
323 on a single `image=' or `other=' to override a different global setting.
327 If booting under a virtual monitor such as VMware(tm), the image with this
328 label will cause a cautionary warning to be issued at boot time, and user
329 intervention will be required to continue or to abort the boot process.
333 If booting under a virtual monitor, the image with this label will not be
334 displayed as a boot option. The image is only bootable in real mode. See
projects / rrq / maintain_lilo.git / blob