Incompatibilities between LILO >= 22 and earlier versions=========================================================Boot loaders------------Starting with version 22, a third boot loader, '/boot/boot-bmp.b' is nowavailable.  This loader supports booting from a bitmapped screen, defined ina bitmap file referenced from the config file.  This boot loader requires aVGA adapter which supports video mode 0x12: 16-color, 640x480 pixels.  Itwill fall back to the teletype-text interface if such an adapter is notpresent.Chain loaders-------------The chain loader for loading OS/2 from other than the C: drive, 'os2_d.b',is now obsolete.  All of the functionality is combined into 'chain.b'.Disk addressing---------------A Makefile option in version 22, LBA32, makes 32-bit sector addressing thedefault, instead of geometric addressing.  Thus, the 1024 cylinder limit onlarge disks will be avoided on virtually all newer (post 1998) systems. With the fallback to geometric addressing as before, compatibility witholder systems is extremely likely.  If geometric addressing must be forcedon older system, there is now the 'geometric' command and '-g' switch.  Notall versions of LILO will be compiled with the LBA32 switch to enable thisfeature.RAID installation-----------------Installation on RAID1 partitions is completely re-written.  Consult thetutorial "README.raid1" for details.  The boot loaders are no longer writtenunconditionally to the MBRs of the disks containing the raid set partitions,but preferably to the raid partition itself.  Auxiliary records may bewritten to MBRs, but this writing may be controlled with 'raid-extra-boot='.A mode of operation compatible with previous versions is available.Incompatibilities between LILO >= 21 and earlier versions=========================================================Serial lines------------Since version 21.7, all IBM standard bit rates from 110 to 9600 aresupported, as well as extended rates of 19200, 38400, 57600, & 115200.Boot loaders------------Starting with version 21.5, the default boot loader is '/boot/boot-menu.b',referenced as '/boot/boot.b' through a symbolic link.  This boot loaderallows booting from a text-based menu using the keyboard arrow keys to makethe kernel/other selection.  For strict compatibility with earlierteletype-text based boot loaders, '/boot/boot-text.b' is still available,although probably unneeded.Change Rules------------A more complete set of default partition change-rules is available starting with version 21.6 and later.A Makefile option allows the automatic insertion of the "CHANGE AUTOMATIC"command into the config file.  A comment is now issued when this is done,and it is possible to see the partition change rules in force by using averbosity level of 3:  -v3 or verbose=3.  Not all versions of LILO will becompiled with the AUTOAUTO switch to enable this feature.Disk addressing---------------32-bit 0-based sector addressing has been available since version 21.2,enabled by the 'lba32' (-L) option.  If the BIOS does not support the EDDpacket calls on int 0x13 to use this feature, then the boot loader will fallback to geometric (Cylinder:Head:Sector) addressing by using int 0x13, fn 8,to obtain the disk geometry.  Incompatibilities between LILO >= 20 and earlier versions=========================================================Special chain loaders---------------------The functionality of the chain loaders any_b.b and any_d.b has beengeneralized and integrated into chain.b. any_b.b and any_d.b aretherefore no longer supported. Their behaviour can be emulated asfollows:   other = foo     loader = /boot/any_b.bbecomes   other = foo     map-drive = 0       to = 1     map-drive = 1       to = 0and   other = foo     loader = /boot/any_d.bbecomes   other = foo     map-drive = 0x80       to = 0x81     map-drive = 0x81       to = 0x80The use of os2_d.b changes as follows:   other = foo     loader = /boot/os2_d.bbecomes   other = foo     loader = /boot/os2_d.b     map-drive = 0x80       to = 0x81     map-drive = 0x81       to = 0x80Removal of less common baud rates---------------------------------The baud rates 150 bps and 600 bps are no longer available with the SERIALoption.Incompatibilities between LILO >= 18 and earlier versions=========================================================Partition type check--------------------Starting with version 18, LILO checks the type of the partition where itstores its boot sector. LILO installation may therefore fail on systemswhere the LILO boot sector resides on a seemingly unsuitable partition.This problem can be solved by either changing the partition type of byusing the IGNORE-TABLE configuration option.disktab-------Is no longer documented and support for it will be removed in a futureversion of LILO. See section "Disk geometry" in the accompanyingdocumentation for the right way to configure unusual disk geometry.Booting kernel images from a device-----------------------------------An essentially useless feature of LILO is to be able to boot a kernelfrom a device without file system, e.g.  image = /dev/fd0    range = 1+512Support for this will be removed in a future version of LILO. Also, newfunctions such as kernels > 512kB are not supported for kernels bootedfrom a device.Note that booting of non-Linux systems (other = /dev/...) will in noway be affected by this feature removal.REWRITE-TABLE-------------The REWRITE-TABLE configuration option and the compile-time optionsREWRITE_TABLE, FIX_TYPE, and HIDE_DOS are not available in the currentversion of LILO, because deficiencies were found in the implementationin version 17 (e.g. attempts to alter the partition table of the seconddisk resulted in a modification of the partition table of the firstdisk, using the parameters of the second disk), and there was notenough time to complete an improved version.Future versions will use a radically different internal mechanism, butno configuration change should be required in most cases. Users whodepend on REWRITE-TABLE to be available should continue to use theircurrent version of LILO and wait for a later version before upgrading.Incompatibilities between LILO >= 17 and earlier versions=========================================================Documentation change--------------------The last traces of "old-style" configuration have been removed.Incompatibilities between LILO >= 0.16 and earlier versions===========================================================Sanity checks-------------When booting an operating system from any device than the first hard or floppydisk, specifying the chain loader is now mandatory.Incompatibilities between LILO >= 0.14 and earlier versions===========================================================mkbindist---------... is gone. I don't think anybody used it and I got tired of updating it.Variable-size setup-------------------Kernels >= 1.1.43 support setup segments of variable size. LILO 0.15 is ableto detect this and act accordingly. However, older kernels could possiblycontain other information at that place. This can be discovered by runningthe following command:# /sbin/lilo -t -v -v | grep SetupIf very unusual numbers (e.g. below four or significantly bigger than five)are shown, you may have such a kernel.LILO has to be compiled without the VARSETUP option in such cases. Note thatlater kernels may no longer support running LILO without VARSETUP.Incompatibilities between LILO >= 0.13 and earlier versions===========================================================Possible conflict with /etc/disktab from Shoelace-------------------------------------------------When using the new path names, installation of LILO may fail with    Invalid line in /etc/disktab:    "w0|wini|Generic hard disk:\"if you have an old /etc/disktab file from Shoelace (a different boot loaderthat is quite obsolete nowadays). Remove or rename that file before running/sbin/lilo (or QuickInst).Note: you may have an /etc/disktab file even if you've never used Shoelace,because even current versions of SLS still install that file.Removal of support for unstripped kernels-----------------------------------------(Compound) unstripped kernels are no longer supported by LILO, becausecurrent kernels are expected to be compressed. This change also obsoletes/etc/lilo/install (see below).A new concept to support compressed kernels carrying symbol information maybe devised later.Removal of /etc/lilo/install----------------------------Early versions of LILO expected to find all parameters on the command line.In order to simplify repeated re-installations of LILO, the invocation ofLILO with all its parameters was stored in /etc/lilo/install.