Incompatibilities between LILO >= 0.9 and earlier versions
==========================================================

Case-insensitive name matching
------------------------------

By default, LILO is now configured to ignore case when matching image
names. This can cause problems if labels are being used that differ
only in case. (Detected at map creation time.) Either change the
label names or remove -DIGNORECASE from the configuration section of
the Makefile.


New keyword "auto" passed to init
---------------------------------

If the system boots without manual intervention, the word "auto" is
passed on the command line to the kernel, which in turn passes it to
init. Some init programs don't recognize that word and issue an error
message or fail to process other command-line options (e.g. some
versions of poeigl init expects "single" to be the only word on the
command line). The old behaviour can be obtained by setting the build-
time configuration variable NOAUTO in the configuration section of the
Makefile.


-r implied if environment variable ROOT is set
----------------------------------------------

The map installer acts as if the option -r was on the command line if
the environment variable ROOT is set. If you are using ROOT for other
purposes than indicating the path of the actual root of the file
system (i.e. it should be set to "/" during normal system operation),
you have to pass the option  -r /  to the map installer. Typically,
ROOT is not used for anything but LILO (or possibly programs that are
aware of how LILO uses it), so this should be no problem.


Incompatibilities between LILO >= 0.7 and earlier versions
==========================================================

There are a number of incompatibilities between LILO 0.7 (or newer)
and earlier versions that cause working /etc/lilo/install scripts to
fail or that change earlier behaviour without warning.


Root device presetting
----------------------

The way how the root device is preset differs from LILO >= 0.7 and
earlier versions if using /etc/lilo/config. If the boot images are
listed on the command line, LILO >= 0.7 emulates the old behaviour.

Old behaviour:
  - if the root device was specified after the image descriptor
    (e.g. foo=/bar,/dev/hda1), that device was used.
  - if a root device was set in the boot image and no device was
    specified at the command line, the setting from the boot
    image was used. Later changes of the settings (e.g. with rdev
    aka setroot) had no effect.
  - if no root device was set in the boot image, LILO used the
    current root partition instead. Again, changing the setting
    later had no effect.

New behaviour:
  - if the ROOT variable is set, that value is used and the
    setting in the boot image is ignored.
  - otherwise, the value found in the boot image at boot time is
    used. This means that changing the root device setting after
    map creation has the desired effect.


Swap device settings
--------------------

Presetting the swap device (e.g. /linux,/dev/root,/dev/swap) is no
longer supported. Linus has already stopped providing that feature
in recent kernels.

Kernels that expect swap device settings in the boot sector may no
longer work. I'm not sure when presettable swap devices were removed,
but generally 0.96 and early 0.97 kernels may be considered
incompatible.

The memory location where the swap device preset value used to be
stored has been occupied by the VGA mode value in 0.98pl6 and
possibly also in SLS versions of 0.98pl5.

Workaround: Create a /etc/lilo/config file and set the VGA variable
	    to zero to disable using a swap device at boot time.


BIOS code overrides
-------------------

Appending BIOS codes to file names (e.g. /foo/bar:0x80) is no longer
supported. /etc/lilo/disktab can be used for most purposes where
BIOS code overrides might have been useful.


Command-line arguments of the map installer
-------------------------------------------

Older versions of the map installer accepted multiple ocurrences of
the same flag. LILO 0.7 and later versions are only guaranteed to
accept repetition of -v. However, variables set in /etc/lilo/config
can be overridden on the command line in LILO 0.8.
