few systems until 2004).
.
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
+ into the first 15MB of memory. LILO will compute the needed size of memory
and will automatically use the memory above 15MB, too, if there is
enough physical memory.
.
Type: boolean
Default: false
_Description: Do you want to convert boot and root options?
- Until kernel using the newer disk interface 'libata' you need the newer
- DiskID and/or UUID in your /etc/lilo.conf the for boot and root options.
+ Since kernel using the newer disk interface 'libata' you need the newer
+ DiskID and/or UUID in your /etc/lilo.conf for the boot and root options.
For the most modern systems you should use this conversion and then run
'/sbin/lilo'.
-
-Template: liloconfig/maintitle
-Type: title
-_Description: LILO configuration.
-
-Template: liloconfig/banner
-Type: text
-_Description: LILO, the LInux LOader, sets up your system to boot Linux directly from your hard disk, without the need for a boot floppy.
-
-Template: liloconfig/configuring_base
-Type: error
-_Description: Hmm. I think you're configuring the base filesystem, and I'm therefore simply going to exit successfully without trying to actually configure LILO properly. If you're not doing that, this is an important bug against Debian's lilo package, and should be reported as such...
-
-Template: liloconfig/liloconf_exists
-Type: note
-_Description: You already have a LILO configuration in the file ${liloconf}. If you want to use the new LILO boot menu, please take a look to /usr/share/doc/lilo/examples/conf.sample and choose one of the bitmaps located on /boot.
-
-Template: liloconfig/liloconf_incompatible
-Type: error
-_Description: WARNING!
- You have an old incompatible lilo configuration file!
- Read the file /usr/share/doc/lilo/INCOMPAT.gz and rerun /sbin/lilo to write the
- changes to your boot sectors
-
-Template: liloconfig/use_current_lilo
-Type: boolean
-Default: true
-_Description: Install a boot block using your current LILO configuration?
-
-Template: liloconfig/lilo_warning
-Type: error
-_Description: WARNING!
- Even if lilo runs successfully, see /usr/share/doc/lilo/INCOMPAT.gz for
- changes in the usage of the ${liloconf} file. If needed: edit ${liloconf} and
- rerun '/sbin/lilo -v'
-
-Template: liloconfig/select_bitmap
-Type: select
-Choices: /boot/tuxlogo.bmp, /boot/inside.bmp, /boot/debian.bmp, /boot/debian-de.bmp, /boot/debianlilo.bmp, /boot/coffee.bmp, /boot/onlyblue.bmp
-Default: /boot/debian.bmp
-_Description: The following is the list of the available bitmaps
-
-Template: liloconfig/lilo_error
-Type: error
-_Description: ERROR!
- Correct ${liloconf} manually and rerun /sbin/lilo.
-
-Template: liloconfig/wipe_old_liloconf
-Type: boolean
-Default: false
-_Description: Wipe out your old LILO configuration and make a new one?
-
-Template: liloconfig/no_changes
-Type: error
-_Description: No changes made.
-
-Template: liloconfig/fstab_broken
-Type: error
-_Description: WARNING!
- Either your ${fstab} configuration file is missing, or it doesn't contain a
- valid entry for the root filesystem! This generally means that your system is
- very badly broken. Configuration of LILO will be aborted; you should try to
- repair the situation and then run /usr/sbin/liloconfig again to retry the
- configuration process.
-
-Template: liloconfig/odd_fstab
-Type: error
-_Description: WARNING!
- Your ${fstab} configuration file gives device ${device} as the root filesystem
- device. This doesn't look to me like an "ordinary" block device. Either your
- fstab is broken and you should fix it, or you are using hardware (such as a
- RAID array) which this simple configuration program does not handle.
- .
- You should either repair the situation or hand-roll your own ${liloconf}
- configuration file; you can then run /usr/sbin/liloconfig again to retry the
- configuration process. Documentation for LILO can be found in
- /usr/share/doc/lilo/.
-
-Template: liloconfig/instruction
-Type: note
-_Description: Booting from hard disk.
- You must do three things to make the Linux system boot from the hard disk.
- Install a partition boot record, install a master boot record, and set the
- partition active. You'll be asked to perform each of these tasks. You may skip
- any or all of them, and perform them manually later on.
- .
- This will result in Linux being booted by default from the hard disk. If your
- setup is complicated or unusual you should consider writing your own
- customised ${liloconf}. To do this you should exit this configuration program
- and refer to the comprehensive lilo documentation, which can be found in
- /usr/share/doc/lilo/.
-
-Template: liloconfig/install_from_root_device
-Type: boolean
-Default: true
-_Description: Install a partition boot record to boot Linux from ${device}?
-
-Template: liloconfig/use_lba32
-Type: boolean
-Default: true
-_Description: Use LBA32 for addressing big disks using new BIOS features?
-
-Template: liloconfig/install_mbr
-Type: boolean
-Default: false
-_Description: Install a master boot record on ${disk}?
- A master boot record is required to run the partition boot record. If you are
- already using a boot manager, and want to keep it, answer "no" to the
- following question. If you don't know what a boot manager is or whether you
- have one, answer "yes".
-
-Template: liloconfig/mbr_error
-Type: error
-_Description: ERROR!
- install-mbr failed! Your system may not be bootable.
-
-Template: liloconfig/make_active_partition
-Type: boolean
-Default: true
-_Description: Make ${device} the active partition
- The master boot record will boot the active partition. If you want your system
- to boot another operating system, such as DOS or Windows, by default, answer
- "no" to the following question. You may still use your boot manager or the
- master boot record to boot Linux. If you want the system to boot Linux by
- default, answer "yes". In this case you could still boot some other OS if you
- know what partition it is on.
-
-Template: liloconfig/activate_error
-Type: error
-_Description: ERROR!
- activate failed! Your system may not be bootable.
projects / rrq / maintain_lilo.git / blobdiff