lilo.conf.5

linux 的引导程序源码The Microsoft&reg Windows&reg Software Development Kit (SDK) provides the documentation

'\" t
.\" @(#)lilo.conf.5 1.0 950728 aeb
.\" This page is based on the lilo docs, which carry the following
.\" COPYING condition:
.\"
.\" LILO program code, documentation and auxiliary programs are
.\" Copyright 1992-1998 Werner Almesberger.
.\" Extensions to LILO, documentation and auxiliary programs are
.\" Copyright 1999-2002 John Coffman.
.\" All rights reserved by the respective copyright holders.
.\" 
.\" Redistribution and use in source and binary forms of parts of or the
.\" whole original or derived work are permitted provided that the
.\" original work is properly attributed to the author. The name of the
.\" author may not be used to endorse or promote products derived from
.\" this software without specific prior written permission. This work
.\" is provided "as is" and without any express or implied warranties.
.\"
.TH LILO.CONF 5 "12 Nov 2002"
.SH NAME
lilo.conf \- configuration file for lilo
.SH DESCRIPTION
.LP
This file, by default
.IR /etc/lilo.conf ,
is read by the boot loader installer 'lilo' (see lilo(8)).
.LP
It might look as follows:
.IP
.nf
# lilo.conf
#
#  global options:
boot=/dev/hda
prompt
timeout=150
lba32
compact
vga=normal
root=/dev/hda1
read-only
menu-title=" John's Computer "
#
#  bootable kernel images:
image=/boot/zImage-1.5.99
     label=try
image=/boot/zImage-1.0.9
     label=1.0.9
image=/tamu/vmlinuz
     label=tamu
     root=/dev/hdb2
     vga=ask
#
#  other operating systems:
other=/dev/hda3
     label=dos
other=/dev/hdb5
     label=os2
     loader=/boot/os2_d.b
     table=E:
.fi
.LP
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.)
.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.
Alternately, if the \fBboot-menu.b\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 can be up to 16 images mentioned in lilo.conf.
.LP
As can be seen above, a configuration file starts with a number
of global options (the top 9 lines in the example),
followed by descriptions of the options for the various images.
An option in an image description will override a global option.
.LP
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).
.TP
.BI "backup=" <backup-file>
Copy the original boot sector to
.I backup-file
(which may also be a device, e.g.
.IR /dev/null )
instead of
.IR /boot/boot.NNNN .
.TP
.BI "bitmap=" <bitmap-file>
Specifies use of a 640x480x16 bitmap file as the background on which a boot
menu is displayed.  May not be used if 'message=' is specified.  Requires
that 'install=' specify a boot-loader which is capable of displaying the
bitmap; i.e., 
.IR boot-bmp.b "."
(Version 22.3): Use of this option now implies use of a bitmap-capable boot
loader, unless overridden with "install=" (see below).
.TP
.BI "bmp-colors=" <fg>,<bg>,<sh>,<hfg>,<hbg>,<hsh>
Specifies the decimal values of the colors to be used for the menu display
on a 'bitmap=' background.  The list consists of 6 entries, 3 for normal
text followed by 3 for highlighted text.  The order of each triple is:
foreground color, background color, shadow color.  If background color is
not specified, "transparent" is assumed.  If shadow color is not specified,
then "none" is assumed.  The list entries are separated by commas, with no
spaces.
.TP
.BI "bmp-table=" <x>,<y>,<ncol>,<nrow>,<xsep>,<spill>
Specifies the location and layout of the menu table.  <x>,<y> specify the
starting x- and y-position of the upper left corner of the table in
character coordinates: x in [1..80], y in [1..30]. <ncol> is the number of
columns in the menu (1..5); and <nrow> is the number of rows (entries)
in each column.
If more than one column is specified, then <xsep> is the number of character
columns between the leftmost characters in each column: (18..40), and
<spill> is the number of entries in one column which must be filled before
entries spill into the next column. <spill> must be .le. <nrow>. If pixel
addressing is used, instead of character addressing, then any of <x>, <y>,
or <xsep> may be specified with a 'p' suffix on the decimal value.
.TP
.BI "bmp-timer=" <x>,<y>,<fg>,<bg>,<sh>
Optional specification of the 'timeout='
countdown timer.  <x>,<y> 
specifies the character (or pixel) coordinate of the location of the timer
the same as 'bmp-table='
above; and the color triple specifes the character color attributes
the same as 'bmp-colors=' above, with the exception that the background color
.I must
be specified.  If used to override the timer specification in a bitmap file,
then the form 'bmp-timer = none' is acceptable.  This will disable the timer
display entirely.
.TP
.BI "boot=" <boot-device>
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.
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.
.TP
.BI "change-rules"
Defines boot-time changes to partition type numbers (`hiding').
.IP
.nf
change-rules
   reset
   type=DOS12
      normal=1
      hidden=0x11
   type=DOS16_small
      normal=4
      hidden=0x14
   type=DOS16_big
      normal=0x06
      hidden=0x16
.fi
.IP
The above excerpt from a configuration file specifies that all default
.I change-rules
are removed ("reset"), and the change-rules for three partition types
are specified.  Without the \fIreset\fP, the three types specified would
have been added to the existing default change-rules.  Normally, the default
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.
.TP
.BI "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. 
.TP
.BI "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. See also,
.I vmdefault
below.
.TP
.BI "delay=" <tsecs>
Specifies the number of tenths of a second the boot loader should 
wait before automatically booting a locked command line,
a command line pre-stored by
"lilo -R", or the default `image=' or `other='.
When `delay' is non-zero, the boot loader will wait for an interrupt for the 
specified interval. If an interrupt is received, or
is already waiting, the \fBboot:\fP
prompt will be be issued, and no automatic boot will take place. The setting
of CAPS LOCK or SCROLL LOCK, or any of the
keys ALT, CTRL, or SHIFT, when held down, are taken as interrupts.

This action is modified by specifying `prompt' (see below).
.TP
.BI "disk=" <device-name>
Defines non-standard parameters for the specified disk.
See section "Disk geometry" of user.tex for details.
Especially useful is the `bios=' parameter.
The BIOS numbers your disks 0x80, 0x81, etc. and it is impossible
to decide which Linux disk corresponds to which BIOS disk
(since this depends on the BIOS setup, and on the type of BIOS),
so if you have an unusual setup you need to state the correspondence
between Linux disks and BIOS disks.
For example,
.sp
.nf
       disk=/dev/sda
            bios=0x80
       disk=/dev/hda
            bios=0x81
.fi
.sp
would say that your SCSI disk is the first BIOS disk,
and your (primary master) IDE disk is the second BIOS disk.
.TP
.BI "disktab=" <disktab-file>
Specifies the name of the disk parameter table.
The map installer looks for
.I /etc/disktab
if `disktab' is omitted. The use of disktabs is discouraged.
.TP
.BI "fix-table"
This allows lilo to adjust 3D addresses in partition tables. Each 
partition entry contains a 3D (cylinder/head/sector) and a linear 
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.
.TP
.BI "force-backup=" <backup-file>
Like `backup', but overwrite an old backup copy if it exists.
.TP
.BI "geometric"
Force disk addressing which is compatible with older versions of LILO. 
Geometric addressing uses cylinder/head/sector addresses, and is limited to
disk cylinders up to 1023.  If inaccessible cylinders are referenced,
diagnostics will be issued at boot-install time, rather than boot-time. 
With a newer BIOS, use of 'lba32' is recommended.
.TP
.BI "ignore-table"
tells lilo to ignore corrupt partition tables. 
.TP
.BI "install=" <boot-loader>
Install the specified file as the new boot loader. Starting with
version 21.5, two boot loaders are available:
.I boot-text.b