lilo.conf.5

来自「LINUX lilo-22.7.1 源代码。」· 5 代码 · 共 1,017 行 · 第 1/3 页

'\" 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-2004 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 "16 Nov 2004"
.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
     initrd=initramdisk.img
     root=/dev/hdb2
     vga=ask
#
#  other operating systems:
other=/dev/hda3
     label=dos
     boot-as=0x80    # must be C:
other=/dev/hdb1
     label=Win98
     boot-as=0x80    # must be C:
other=/dev/hdb5
     label=os2
     loader=os2_d
     table=E:   # os2 sees as 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 \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.)
.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>
Specifies the location where a copy of any modified boot sector will be
saved in a file. 'backup=' may specify this location in one of three ways:
a directory where the default backup file 'boot.NNNN' will be created;
a file pathname template to which the '.NNNN' suffix will be added; or
the full file pathname, which must include the correct '.NNNN' suffix.
All RAID installations should use only the first two alternatives, as
multiple backups may be created.  The '.NNNN' suffix is the hexadecimal
representation of the major and minor device numbers of the device or
partition. If this option is not specified, the default name of boot sector
backups is '/boot/boot.NNNN'. If a backup already exists, it will be
preserved, rather than overwritten.  C.f., \fBforce-backup=\fP below.
.TP
.BI "bios-passes-dl=" <option>
The option is indicated as \fIyes\fP, \fIno\fP, or \fIunknown\fP.  If not
specified, a value of "unknown" is assumed, unless additional information
is available to the boot installer. When "no" is specified, it indicates
that the BIOS is known not to pass the current boot device code to the boot
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.
.TP
.BI "bitmap=" <bitmap-file>
Specifies use of a 640x480x16 (VGA BIOS) or 640x480x256 (VGA/VESA BIOS)
bitmap file as the background on which a boot
menu is displayed.  May not be used if 'message=' is specified.
Use of this option will select a bitmap-capable boot
loader, unless overridden with "install=" (see below).
.sp
When a bitmap file is specified as a background screen during the boot
process, the color selection and layout of the text which overlays the
graphic image must be specified in one of two ways.  One way, is to use
a bitmap image (*.bmp) file which has had a header written by the
.BI "lilo -E"
command.  If this command is used, then all of the
information specified by the 'bmp-colors', 'bmp-table', and 'bmp-timer'
options is stored in a special LILO header within the bitmap file.
Without this header, the 'bmp-' option values should be
specified in the configuration file; if not, default values are used.
Any use of the 'bmp-' options
within the configuration file overrides the values stored in the
bitmap file header.
.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-retain"
Option applies to all 'image=' and 'other=' sections.
(See COMMON OPTIONS, below.)
.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 file
smaller. Using `compact' is especially recommended when booting
using a map file on 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.
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.
For example,
.sp
.nf
       disk=/dev/sda
            bios=0x80
       disk=/dev/hda
            bios=0x81
       disk=/dev/sdb
            inaccessible
.fi
.sp
would say that your SCSI disk is the first BIOS disk (0x80),
that your (primary master) IDE disk is the second BIOS disk (0x81),
and that your second SCSI disk (perhaps a USB device) receives no
device code, and is therefore inaccessible at boot time.
.sp
NOTE: Use of the 'bios=' option is largely obsolete beginning
with LILO version 22.5, as the boot loader now identifies disks
by 32-bit Volume-ID, and defers BIOS device code determination
until boot time.
.sp
Most USB devices which are implemented as SCSI disks MUST be marked
.BI inaccessible
unless they are actually assigned a device code by the BIOS.
.sp
Other options include the specification of disk geometry; e.g.,
.sp
.nf
       disk=/dev/fd0
            sectors=18
            heads=2
            cylinders=80
.fi
.sp
probably only useful for floppy disks and loopback devices,
since for hard disks the
.BI lba32
disk addressing option (LILO 21.2) ignores disk geometry.
.sp
In cases where there is no
kernel paritition information available, such as on loopback devices,
the 'disk=' specification may include paritition start information;
viz.,
.sp
.nf
       disk=/dev/loop0
            bios=0x80
            paritition=/dev/loop1
                 start=63		# offset from sector 0
            paritition=/dev/loop2
                 start=102400		# offset from sector 0
.fi
.sp
(22.5.8) Developers who have implemented a disk driver for a new block storage
device will have to indicate to LILO the maximum number of partitions
on the device.  This is in addition to making all of the necessary
entries for the device in the "/dev" directory (with 'mknod').  The
maximum number of partitions must be one of 63 (like an IDE disk), 15
(like SCSI disks -- most common value), or 7 (like one array controller).
An example specifictaion would be:
.sp
.nf
     disk=/dev/userd0
          max-partitions=15
.fi
.sp
.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 "el-torito-bootable-CD"
Flag second stage loader to terminate floppy disk emulation when booting
from an El Torito Bootable CD. This option is used only by the
\fBmkrescue\fP utility used with the "--iso" switch.
.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.