Because this was messy and introduced syntactical limitations,/etc/lilo/config was introduced after a while and support for command-lineoptions was drastically reduced later. /etc/lilo/install now typically justinvoked /etc/lilo/lilo with no options or with -C /etc/lilo/config, whichbecame the default. Only when using compound unstripped kernels, one had toput additional instructions to build the kernel file into /etc/lilo/install.Now, that unstripped kernels are gone too (see above), /etc/lilo/install issuperfluous. Because the kernel Makefile still invokes LILO by calling/etc/lilo/install, /etc/lilo/install should be a symbolic link to /sbin/liloor /etc/lilo/lilo until everybody has switched to the new directorystructure.Directory hierarchy change--------------------------A new Linux directory structure is in the process of being standardized.Most distributions will support the new structure. In order to install LILOwith the new structure, you have to use the .new versions of QuickInst andMakefile. Otherwise, you have to use the .old versions.The locations of the following files change:  Old location			New location  ------------------------	-----------------  /etc/lilo/config.defines	/etc/lilo.defines  /etc/lilo/config		/etc/lilo.conf  /etc/lilo/disktab		/etc/disktab  /etc/lilo/lilo		/sbin/lilo  /etc/lilo/boot.NNNN		/boot/boot.NNNN  /etc/lilo/part.NNNN		/boot/part.NNNN  /etc/lilo/map			/boot/map  /etc/lilo/*.b			/boot/*.b/etc/lilo/install should be a symbolic link to /sbin/lilo for backwardscompatibility. If you already have a (very old) /etc/disktab file fromShoelace, you have to delete or replace it. (Note: SLS 1.03 still installsthat file, so you might have it even if you've never heard of Shoelace.)The current documentation still uses the old paths.Temporary unavailability of RAM disk size override--------------------------------------------------The RAM disk size override option (RAMDISK) has no effect when using0.99pl13 or older kernels, because no corresponding parameter line itemexists. Support for it may be available in 0.99pl14 or later kernels.Incompatibilities between LILO >= 0.12 and earlier versions===========================================================The first stage boot loader now displays diagnostic codes if loadingthe second stage loader fails. This may create irritating messageslike L06ILO on systems, where the first read access on a disk afterbooting usually fails. These diagnostics can be disabled by settingthe compile-time option NO1STDIAG.Incompatibilities between LILO >= 0.11 and earlier versions===========================================================The configuration variable INSTALL is no longer required. If absent, adefault of /etc/lilo/boot.b is used. This means that it is no longerpossible to avoid installing a new boot sector when updating the mapfile. The old behaviour can be restored by setting the compile-timeoption NOINSTDEF.Incompatibilities between LILO >= 0.10 and earlier versions===========================================================Version 0.10 of LILO is intentionally incompatible in many ways withearlier versions. However, in most cases, there is an easy migrationpath.LILO 0.10 may not work with versions of the following programs olderthan specified:  Kernel				0.99pl8  Peter Orbaek's poeigl			1.13a  Miquel van Smoorenburg's SysV-init	2.1  Mike Jagdis' bootsys			version 3 (?)Documentation cleaning and splitting------------------------------------Because the documentation was slowly becoming a multiple-choice test,all references to old versions of kernels and other programs have beenremoved. All traces of removed features have vanished too.The single file "doc.tex" is now split in two parts: the user's guide"user.tex" and the technical overview "tech.tex". Reading thetechnical overview is not necessary in order to install LILO.Old-style configuration has been removed----------------------------------------Old-style configuration (e.g. /etc/lilo/lilo /vmlinux,/dev/hda1) is nolonger supported. New-style configuration uses a configuration file ina far better readable format (/etc/lilo/config). There is also spacefor future extensions.If you're still using old-style configuration, you have to switch tonew-style configuration before installing LILO 0.10.For all versions of LILO since 0.7, an automated migration facility isprovided. See section "Migration" in the documentation of that versionof LILO. In short, you have to run the following commands _before_upgrading to LILO 0.10:# /etc/lilo/install -D >/etc/lilo/config# mv install.new /etc/lilo/installIf you're using an older version of LILO than 0.7 or if you're notusing /etc/lilo/install, you should either manually create aconfiguration file or use QuickInst to re-install from scratch.No support for dumps--------------------Because LILO 0.10 doesn't understand old-style configuration, the dumpoption (-D) is no longer supported. Therefore, if you need to migratefrom old-style configuration, you have to use the installed version ofLILO to do that.No support for not-compound unstripped kernels----------------------------------------------Since LILO 0.9, compound unstripped kernels are supported. They areeasier to handle and provide the same functionality as not-compoundunstripped kernels. Note: all this has _nothing_ to do with compressed(zipped) kernels. They work fine with all versions of LILO.Suggesting using a link for /etc/lilo/install---------------------------------------------Because not-compound unstripped kernels, which were needing somesupport code in /etc/lilo/install, have been removed, and because the-C option is no longer necessary to distinguish between old-style andnew-style configuration, /etc/lilo/install is unnecessary in mostcases.In order to preserve compatibility with older installations and withinstallations that use code for special actions in /etc/lilo/install,a symbolic link should be created from /etc/lilo/install to lilo.Removed configuration option NOAUTO-----------------------------------The compile-time configuration option NOAUTO has been removed. Thismeans that you have to upgrade to poeigl ?.??? (or later) if you'reusing simpleinit from an earlier version of poeigl. If the optionNOAUTO is still present, it is ignored.Incompatibilities between LILO >= 0.9 and earlier versions==========================================================Case-insensitive name matching------------------------------By default, LILO is now configured to ignore case when matching imagenames. This can cause problems if labels are being used that differonly in case. (Detected at map creation time.) Either change thelabel names or remove -DIGNORECASE from the configuration section ofthe Makefile.New keyword "auto" passed to init---------------------------------If the system boots without manual intervention, the word "auto" ispassed on the command line to the kernel, which in turn passes it toinit. Some init programs don't recognize that word and issue an errormessage or fail to process other command-line options (e.g. someversions of poeigl init expects "single" to be the only word on thecommand line). The old behaviour can be obtained by setting the build-time configuration variable NOAUTO in the configuration section of theMakefile.-r implied if environment variable ROOT is set----------------------------------------------The map installer acts as if the option -r was on the command line ifthe environment variable ROOT is set. If you are using ROOT for otherpurposes than indicating the path of the actual root of the filesystem (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 areaware 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 tofail or that change earlier behaviour without warning.Root device presetting----------------------The way how the root device is preset differs from LILO >= 0.7 andearlier versions if using /etc/lilo/config. If the boot images arelisted 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 nolonger supported. Linus has already stopped providing that featurein recent kernels.Kernels that expect swap device settings in the boot sector may nolonger work. I'm not sure when presettable swap devices were removed,but generally 0.96 and early 0.97 kernels may be consideredincompatible.The memory location where the swap device preset value used to bestored has been occupied by the VGA mode value in 0.98pl6 andpossibly 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 longersupported. /etc/lilo/disktab can be used for most purposes whereBIOS code overrides might have been useful.Command-line arguments of the map installer-------------------------------------------Older versions of the map installer accepted multiple ocurrences ofthe same flag. LILO 0.7 and later versions are only guaranteed toaccept repetition of -v. However, variables set in /etc/lilo/configcan be overridden on the command line in LILO 0.8.