====== Configurar LiLo ======



===== Configurar =====


Modificar los parámetros en ''lilo.conf'':
<code>#nano /etc/lilo.conf</code>

Verificar que los archivos del kernel y de initramfs sean los correctos para que LiLo los pueda encontrar.

''liloconfig'' corriendo en Slackware 11 genera algo así:
<code>
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda1                # Install LILO in the MBR
# compact                       # faster, but won't work on all systems.
prompt                          # Give the user the chance to select another section
timeout = 300                   # Wait 30 seconds before booting the default section
vga = 787                       # VESA framebuffer console @ 800x600x32k


# vga = normal                  # Normal VGA console
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0                 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda1
  label = slack
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
</code>

<WRAP center round important 60%>
''compact'' reduce el tiempo de carga comprimiendo el mapfile y realizando lecturas secuenciales del disco. Es útil para arrancar desde un floppy, pero puede dar errores según el chipset o BIOS.

El manual dice:
//Enable  map compaction. This will merge read requests from adjacent sectors. Speeds up the booting (especially from floppy).//

Puede devolver un error 9A: //no second stage loader signature//


//Errors 99 and 9A  usually  mean  the  map file  (-m  or map=) is not readable, likely because LILO was not re-run after some system change, or there is a geometry mis-match between what LILO  used (lilo -v3 to display) and what is actually being used by the BIOS (one of the lilo diagnostic disks, available in the source distribution, may be needed to diagnose this problem).//

</WRAP>



===== Instalar =====

Para aplicar los cambios (i.e. escribir la configuración en el arranque), ejecutar lilo o /sbin/lilo

<code>#/sbin/lilo </code>