Difference between revisions of "LILO"
(→Installation: plain lilo is now in the AUR too) |
(update as discussed in Help_talk:Style/Article_summary_templates#Deprecation_of_summaries_and_overviews) |
||
| Line 4: | Line 4: | ||
{{Stub}} | {{Stub}} | ||
| − | {{ | + | {{Related articles start}} |
| − | {{ | + | {{Related|Arch Boot Process}} |
| − | {{ | + | {{Related|Boot Loaders}} |
| − | + | {{Related articles end}} | |
| − | {{ | ||
The ''LI''nux ''LO''ader, or '''LILO''' for short, is a legacy multi-boot loader for Linux systems. In spite of being the standard choice over the course of several years, it has been slowly phased out thanks to the advent of [[GRUB]], an alternative boot loader offering easier configuration and less chance of rendering systems unbootable. However, many users still prefer the simplicity of traditional LILO, and it is still actively developed. | The ''LI''nux ''LO''ader, or '''LILO''' for short, is a legacy multi-boot loader for Linux systems. In spite of being the standard choice over the course of several years, it has been slowly phased out thanks to the advent of [[GRUB]], an alternative boot loader offering easier configuration and less chance of rendering systems unbootable. However, many users still prefer the simplicity of traditional LILO, and it is still actively developed. | ||
Revision as of 11:35, 16 November 2013
The LInux LOader, or LILO for short, is a legacy multi-boot loader for Linux systems. In spite of being the standard choice over the course of several years, it has been slowly phased out thanks to the advent of GRUB, an alternative boot loader offering easier configuration and less chance of rendering systems unbootable. However, many users still prefer the simplicity of traditional LILO, and it is still actively developed.
Installation
LILO is available as liloAUR and lilo-gitAUR from the AUR.
Configuration
LILO is configured by editing the /etc/lilo.conf file and running lilo afterwards to apply the new configuration. If choosing LILO during the Arch Linux installation process, the configuration file should have been already performed.
As a reminder, consider that LILO needs to be run after every kernel upgrade, otherwise the system is likely to be left in an unbootable state.
More help on setting up LILO can be found in the LILO-mini-HOWTO.
Sample setup
A typical LILO setup:
compact to /etc/lilo.conf's global section, as shown below./etc/lilo.conf
#
# /etc/lilo.conf
#
boot=/dev/hda
# This line often fixes L40 errors on bootup
# disk=/dev/hda bios=0x80
default=Arch
timeout=100
lba32
prompt
compact
image=/boot/vmlinuz-linux
label=Arch
append="devfs=nomount"
vga=788
root=/dev/hda2
read-only
image=/boot/vmlinuz-linux
label=ArchRescue
root=/dev/hda8
read-only
other=/dev/hda1
label=Windows
# End of file
You can use hwinfo --framebuffer to determine what vga modes you can use.