X-Git-Url: https://git.rrq.au/?a=blobdiff_plain;f=debian%2FREADME.Debian;h=d539ccd7428451f8a8e3fcd17b5e7130cb4fae86;hb=ef0786f33eaf718b9de4159e8b60df47f45b47af;hp=ab6c8ec724beab7f25c784d695c34f8836dd2048;hpb=e54ace12fd683ce1f41b25ed66641e40b84212b0;p=rrq%2Fmaintain_lilo.git

diff --git a/debian/README.Debian b/debian/README.Debian
index ab6c8ec..d539ccd 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -1,31 +1,78 @@
---[ Distribution upgrade
+README for lilo in Debian
+-------------------------
+
+
+** Distribution upgrade **
 
 If you are upgrading or dist-upgrading, it is recommended to run 
-/sbin/lilo after that.
+/sbin/lilo after that. Usually this work will be done by the (new)
+hook scripts for kernel and initramfs.
+
+
+** Other installed bootloader **
+
+Please pay attention to the hook scripts for kernel and initrd, if  you
+have also installed another bootloader. With every update of kernel or
+initrd these hook scripts will be executed and then Lilo rewrite the MBR.
+They don't check whether another bootloader is activated. 
+
+Grub and Grub2 have its own hook scripts which will be executed, too, but
+don't rewrite the MBR every time. If you have installed and configured 
+other bootloader, then be aware, that they work differently and have its
+own hook scripts, which could give you accidental situations. Please read
+the package information about other installed bootloader for correct
+configuration.
+
+
+** Large initrd files **
 
---[ Large initrd files and lilo
+Usually LILO loads the initrd file into the first 15MB of memory to
+avoid a BIOS limitation with older systems (earlier than 2001 and
+few systems until 2004).
 
-By default, LILO loads the initrd file into the first 15MB of memory
-to avoid a BIOS limitation with older systems (earlier than 2001).
+With newer kernels the combination of kernel and initrd may not fit
+into the first 15MB of memory. LILO compute the needed size of memory
+and will automatically use the memory above 15MB, too, if there is
+enough physical memory. Then lilo give you information about this
+while running lilo.
 
-However, with newer kernels the combination of kernel and initrd
-may not fit into the first 15MB of memory and so the system will not
-boot properly. It seems that the boot issues appear when the
-kernel+initrd combination is larger than 8MB.
+If this machine has a recent BIOS without a 15MB limitation and you
+want to use memory above 15MB for all kernels, set the 'large-memory'
+option. You will need to re-run the 'lilo' command to make this 
+option take effect.
 
-If this machine has a recent BIOS without the 15MB limitation, you can
-add the 'large-memory' option to /etc/lilo.conf to instruct LILO to use
-more memory for passing the initrd to the kernel. You will need to
-re-run the 'lilo' command to make this option take effect.
 
-If this machine has an older BIOS, you may need to reduce the size of
-the initrd *before* rebooting.
+** Solve the 15MB problem **
+
+If the machine has an older BIOS which don't can use any memory above
+15MB you should use the newer option 'small-memory' in /etc/lilo.conf 
+to instruct LILO to use only the memory below the 15MB line. You may 
+need to reduce the size of the initrd *before* rebooting.
 
 If you are using initramfs-tools, you should replace MODULES=most with
 MODULES=dep in your configuration and regenerate your initrd file:
 
-sed -i -e s/MODULES=most/MODULES=dep/ /etc/initramfs-tools/initramfs.conf
-update-initramfs -u
+  sed -i -e s/MODULES=most/MODULES=dep/ /etc/initramfs-tools/initramfs.conf
+  update-initramfs -u
+
+
+** Inaccessible devices **
+
+The old patch for better support for inaccessible disks based on
+problems with usb sticks. But this option 'inaccessible' is only 
+usable, if hard disks can not be accessed by the BIOS, but can always 
+be accessed by linux. This option is not sensible for usb sticks, 
+which will always bring failures if they are named in the lilo.conf. 
+So please don't use the option 'inaccessible' with USB sticks or other
+removable devices.
+
+
+** Inactive disks of MD RAID-1 array **
+
+RAID-1 devices are supported as boot device. If not all RAID-1 disks
+are activated use '-H' to install only to active disks. This option 
+override fatal halt while found an inactive disk of an RAID-1 array.
+
+Warning: Booting with partial RAID-1 installation only on active disks
+is not failsafe!
 
-If you are using yaird or any other initrd generator, please consult
-the documentation for your initrd generator.