Category : Linux Files
Archive   : LILO07.ZIP
Filename : LILO07.TAR

Output of file : LILO07.TAR contained in archive : LILO07.ZIP
lilo/README 644 0 0 50616 5310565731 10730 0ustar rootrootLILO - Generic Boot Loader for Linux ("LInux LOader") by Werner Almesberger

This is an ALPHA test release of a new boot loader. Be sure to have some
means to boot your system from a different media if you install LILO on your
hard disk.

NOTE: Most of the documentation has moved into the LaTeX document doc.tex.
This is only a minimal description for those who can't print or pre-
view LaTeX documents.


- does not depend on the file system. (Tested with Minix, EXT FS and MS-DOS
- can be used to boot from floppies and from hard disks.
- can replace the master boot record.
- can boot non-Linux systems (MS-DOS, DR DOS, OS/2, ...) and unstripped
- supports up to 16 different boot images that can be selected at boot
time. The root disk/partition can be set independently for each
- boot sector, file map and boot images can be all on different disks or

Restrictions and known problems

- SCSI disks are not fully supported yet. (But there's progress.)
- booting non-Linux systems from the second hard disk ("D:") is not yet


Files contained in lilo.7.tar.Z:

README This file.
INCOMP List of incompatibilities.
Makefile Makefile for everything else.
*.c, *.h LILO map installer source.
*.S LILO boot loader source.
activate.c Simple boot partition setter.
dparam.s Disk parameter dumper source.
disktab Sample disk parameter table. Replacement of /etc/lilo/install for new-style

Files created after make (among others):

boot.b Combined boot sector.
chain.b Chain loader.
lilo LILO installer.
activate Simple boot partition setter. MS-DOS executable of the disk parameter dumper.


The LaTeX part is generally more up to date and contains more useful
hints and examples. The following sections have been trimmed to make
it easier to maintain them, e.g. by removing as many version-dependen-
cies as possible.


LILO 0.7 is compatible with all kernels that don't support presetting
of a swap device. This change has probably occurred at some 0.97 version.
If the swap device preset code is disabled, you can also use 0.96c-pl1
(or newer) kernels.

This section describes one possible installation of LILO. Please read
"Booting basics" in the LaTeX document for the whole story.

Non-SCSI installation:

Step 1: Extract all files from lilo.7.tar.Z, run make to compile and assemble
all parts.
Step 2: Read the "LILO installer" section in this README and be sure to
understand what the command-line options do.
Step 3: Do make install to copy all LILO files to /etc/lilo
Step 4: Install lilo on a floppy disk:
lilo -b /dev/fd0 -i boot.b -v -v -v /your_kernel_image
Step 5: Reboot. If this doesn't work or if you don't want to install LILO on
your hard disk anyway, you can stop here.
Step 6: Get a working bootimage and a rootimage. If you have reason to be
paranoid about your boot sector, mount the rootimage and copy your
current boot sector to a file on it, e.g.
dd if=/dev/hda2 of=/fd/boot_sector bs=512 count=1
Step 7: Create a shell script /etc/lilo/install that installs LILO on your
hard disk, e.g.
# cat >/etc/lilo/install
$ROOT/etc/lilo/lilo -C /etc/lilo/config $*
# chmod 755 /etc/lilo/install

Then create a configuration file /etc/lilo/config, e.g.
# cat >/etc/lilo/config

Step 8: Now, you can check what LILO would do if you
were about to install it on your hard disk:
/etc/lilo/install -v -v -v -t
Step 9: If necessary, install a boot partition switcher. Run /etc/lilo/install
to install LILO on your hard disk. If necessary, mark that partition
Step 10: Reboot.

SCSI installation:

Like non-SCSI installation, but you have to put the parameters of your
SCSI drive into the file /etc/lilo/disktab.

IMPORTANT: You have to repeat the installation procedure whenever any of the
boot images is replaced or moved (e.g. after the kernel is re-

LILO Installer

The LILO installer accepts the following command-line options:

-b boot_device

Sets the name of the device that contains the boot sector. If -b is
omitted, the boot sector is read from (and possibly written to) the
device that is currently mounted as root. A BIOS device code can be


Tries to merge read requests for adjacent sectors into a single read
request. This drastically reduces load time and keeps the map

-C config_file

Specifies the new-style configuration file that is used by the map
installer. If -C is omitted, old-style configuration is used.

-d tsecs

Specifies the number of tenths of seconds LILO should wait before
booting the first image. This is useful on systems that immediately
boot from the hard disk after enabling the keyboard. LILO doesn't
wait if -d is omitted.


Selects dump mode. Dumps are used during migration from earlier
versions of LILO. -D also implies -t and disables all other
informational messages.

-f disktab_file

Specifies the name of the disk parameter table. The map installer
looks for /etc/lilo/disktab if -f is omitted.

-i boot_sector

Install the specified file as the new boot sector. If -i is omitted,
the old boot sector is modified. A BIOS device code can be specified.


Generate linear sector addresses instead of sector/head/cylinder
addresses. Linear addresses are translated at run time and do not
depend on disk geometry. This is experimental and is not (yet)
intended for common use.

-m map_file

Specifies the location of the map file. If -m is omitted, a file
/etc/lilo/map is used. A BIOS device code can be specified.


List the currently mapped files.

-r root_dir

Change the root directory to root_dir before doing anything else.
This is typically used when running off a floppy, with the normal
root mounted at some directory.

-s backup_file

Copy the old boot sector to backup_file instead of

-S backup_file

Like -s, but overwrite an old backup copy if it already exists.

Test only. This performs the entire installation procedure except
replacing the map file and writing the modified boot sector. This
can be used in conjunction with the -v option to verify that LILO
will use sane values.


Turns on lots of progress reporting. Repeating -v will turn on more
reporting. (-v -v -v -v -v is the highest verbosity level and
displays all sector mappings before and after compaction.)

There are two ways how image files can be specified: the traditional
approach is to specify them on the command line, typically in
/etc/lilo/install. The new, preferred method uses a configuration file
/etc/lilo/config. There is a section that describes the migration

Old-style configuration

If no image files are specified on the command line, the currently mapped
files are listed. Only the options -m, -v and -r can be used in this mode.

If at least one file name is specified, a new map is created for those files
and they are registered in the boot sector. If the root device has been
set in the images, it is copied into the descriptors in the boot sector.
Changing the root device specification in a boot image after the map file
has been built has no effect.

If no root device has been set (or if this is not a traditional boot image),
the current root device is used. The root device can be overridden by
appending it to the image specification, e.g.

lilo foo,/dev/hda1
^ ^
image root

Either numbers or device names can be used.

It is perfectly valid to use different root settings for the same image,
because LILO stores them in the image descriptors and not in the images
themselves. Example:

lin-hd=/linux,/dev/hda2 \

The image files can reside on any media that is accessible at boot time.
There's no need to put them on the root device, although this certainly
doesn't hurt.

LILO uses the first file name (without its path) of each image specification
to identify that image. A different name can be used by prefixing the
specification with

  3 Responses to “Category : Linux Files
Archive   : LILO07.ZIP
Filename : LILO07.TAR

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: