lilo.conf.5

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

    \fBother=\fP\fI<device>\fP
.fi
.sp
to indicate an arbitrary system to boot.
.LP

In the former case, if an \fBimage\fP line specifies booting
from a device, then one has to indicate the range of sectors to be mapped
using
.sp
.nf
    \fBrange=\fP\fI<start>-<end>\fP
    \fBrange=\fP\fI<start>+<nsec>\fP
    \fBrange=\fP\fI<sector>\fP
.fi
.LP
In the third case, 'nsec=1' is assumed.

.SH "KERNEL OPTIONS (image=)"
If the booted image is a Linux kernel, then one may pass
command line parameters to this kernel.
.TP
.BI "append=" <string>
Appends the options specified to the parameter line passed to the kernel.
This is typically used to specify parameters of hardware that can't be
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.  Append may be used only once per "image="
section.  Example:
.sp
.nf
     append="mem=96M hd=576,64,32 console=ttyS1,9600"
.fi
.sp
.TP
.BI "initrd=" <name>
Specifies the initial ramdisk image to be loaded with the kernel.  The
image will contain modules needed at boot time, such as network and scsi
drivers. See man pages for \fImkinitrd(8)\fP.
.TP
.BI "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.
.TP
.BI "ramdisk=" <size>
This specifies the size (e.g., "4096k") 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.
.TP
.BI "read-only"
This specifies that the root file system should be mounted read-only.
It may be specified as a global option.
Typically, the system startup procedure re-mounts the root 
file system read-write later (e.g. after fsck'ing it).
.TP
.BI "read-write"
This specifies that the root file system should be mounted read-write.
It may be specified as a global option.
.TP
.BI "root=" <root-device>
This specifies the device that should be mounted as root. 
It may be specified as a global option.
If the special name
.B 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.
(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.)
.TP
.BI "vga=" <mode>
This specifies the VGA text mode that should be selected when 
booting.
It may be specified as a global option.
The following values are recognized (case is ignored): 
.sp
.BR normal :
select normal 80x25 text mode. 
.sp
.BR extended " (or " ext ):
select 80x50 text mode.
.sp
.BR ask :
stop and ask for user input (at boot time).
.sp
<number>: use the corresponding text mode. A list of available modes 
can be obtained by booting with
.I vga=ask
and pressing [Enter]. 
.sp
If this variable is omitted, the VGA mode setting contained in the 
kernel image is used. (And that is set at compile time using the
SVGA_MODE variable in the kernel Makefile, and can later be changed with
the rdev(8) program.)

.SH "ALTERNATE SYSTEM (other=)"
.LP
Used to load systems other than Linux. The `other = <device>' specifies
the boot sector of an alternate system contained on a device or disk
partition; e.g., DOS on, say, `/dev/hda2', or a floppy on `/dev/fd0'.
In the case of booting another system there are these options:
.TP
.BI "loader=" <chain-loader>
This specifies the chain loader that should be used.  It may also be
specified as a global option.
By default
.I /boot/chain.b
is used.  This chain loader passes partition and drive information in the
boot sector it loads only to DOS on FAT12 or FAT16, Windows on FAT16 or
FAT32, or OS/2 on FAT16 or HPFS.
The alternate chain loader,
.I /boot/os2_d.b
passes partition and drive information unconditionally, and uses a format
suitalble for OS/2 and DOS (see 
.I table=<letter>
below).
.TP
.BI "table=" <device>
This specifies the device that contains the partition table. 
The boot loader will pass default 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.
.TP
.BI "table=" <drive-letter>
This is a special case for the
.I os2_d.b
chain loader.  It specifies the DOS drive letter for the partition
that will be booted.  This is
.I mandatory
when booting OS/2 installed on
an extended partition.  The drive letter may be specified with or without a
trailing colon.
.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
.B change
is omitted, change rules are generated as though the 
.I "automatic"
keyword were specified.  The keyword
.B change
alone, without any rules following, will suppress automatic change-rules.
For example,
.IP
.nf
   other=/dev/hda2
      label=dos
      table=/dev/hda
      change
        automatic
        partition=/dev/hda1
           set=DOS12_hidden
           deactivate
        partition=/dev/hda2
           set=DOS16_big_normal
           activate
.fi
.IP
specifies that when primary partition /dev/hda2 is booted, automatic
change-rules will be in effect; plus, partition 1, a DOS12 partition, will
be set hidden, and deactivated.  In addition, partition 2, will be set
normal, and activated.  Activation sets the boot-flag in the partition
table.  The 
.I automatic
keyword may confict with default change rules, so the
.I set=
lines above may be redundant.
.TP
.BI "map-drive=" <num>
Maps BIOS calls for the specified drive to the device code specified on the
next line as \fBto=\fP<num>.  This mapping is useful for booting operating
systems, such as DOS, from the second hard drive.  The following, swaps the
C: and D: drives,
.sp
.nf
   map-drive=0x80
      to=0x81
   map-drive=0x81
      to=0x80
.fi
.TP
.BI "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. If the boot sector is on a hard drive, the BIOS device code
of the drive will have to be specified explicitly with "disk=/dev/XXXX
bios=0x8X inaccessible" in the configuration file.
`unsafe' and `table' (explicit or implicit) are mutually incompatible. 

.SH "COMMON OPTIONS (image= & other=)"
.LP
In both the
.BR image= " and " other=
cases, the following options apply.
.TP
.BI "label=" <name>
The boot loader 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'.
.TP
.BI "alias=" <name>
A second name for the same entry can be used by specifying an alias.
.TP
.BI "lock"
(See above.)
.TP
.BI "optional"
Omit the image if it is not available at map creation time.
It may be specified as a global option.
This is useful to specify test kernels that are not always present.
.TP
.BI "password=" <password>
Protect the `image=' or `other=' with a password (or passphrase).
It may be specified as a global option.
The interpretation of the `password=' setting is modified by the words
`mandatory', `restricted', and `bypass' (see below).
.br
The password may be specified in the config-file (less secure) or entered
at the time the boot loader is installed. To request interactive entry of
the password, it should be specified: \fBpassword=""\fP.
Passwords entered interactively are not required to be entered again if the
boot installer is re-run. They are cached, in hashed form, in a companion
file to the config-file, default name: \fB/etc/lilo.conf.crc\fP. If the 
config-file is updated, a warning message
will be issued telling you to re-run \fIlilo -p\fP to force re-creation of the
password cache file.
.TP
.BI "mandatory"
A password is required to boot this image. This is the default. May be used
on a single `image=' or `other=' to override a different global setting.
.TP
.BI "restricted"
A password is only required to boot the image if kernel parameters
are specified on the command line (e.g. 'single').  May be used
on a single `image=' or `other=' to override a different global setting.
.TP
.BI "bypass"
No password is required to boot this image. Used to indicate that the global
password does not apply to this `image=' or `other='.
.TP
.BI "vmwarn"
If booting under a virtual monitor such as VMware(tm), the image with this
label will cause a cautionary warning to be issued at boot time, and user
intervention will be required to continue or to abort the boot process.
.TP
.BI "vmdisable"
If booting under a virtual monitor, the image with this label will not be
displayed as a boot option.  The image is only bootable in real mode.  See
.I vmdefault
above.

.LP

.SH "SEE ALSO"
lilo(8), mkinitrd(8), mkrescue(8), rdev(8).
.br
.sp
The lilo distribution comes with very extensive documentation
of which the above is an extract.  (lilo 22.3)