1 Template: lilo/new-config
3 _Description: LILO configuration
4 It seems to be your first LILO installation. It is absolutely necessary to
5 run liloconfig(8) when you complete this process and execute /sbin/lilo
8 LILO won't work if you don't do this.
10 Template: lilo/add_large_memory
13 _Description: Do you want to add the large-memory option?
14 Usually LILO loads the initrd file into the first 15MB of memory to
15 avoid a BIOS limitation with older systems (earlier than 2001 and
16 few systems until 2004).
18 With newer kernels the combination of kernel and initrd may not fit
19 into the first 15MB of memory. LILO compute the needed size of memory
20 and will automatically use the memory above 15MB, too, if there is
21 enough physical memory.
23 If this machine has a recent BIOS without a 15MB limitation and you
24 want to use memory above 15MB for all kernels, set the 'large-memory'
30 _Description: Do you want to run /sbin/lilo now?
31 It was detected that it's necessary to run /sbin/lilo in order to activate
32 the new LILO configuration.
34 WARNING: This procedure will write data in your MBR and may overwrite
35 some data there. If you skip this step, you must run /sbin/lilo before
36 rebooting your computer, or your system may not boot again.
38 Template: lilo/diskid_uuid
41 _Description: Do you want to convert boot and root options?
42 Until kernel using the newer disk interface 'libata' you need the newer
43 DiskID and/or UUID in your /etc/lilo.conf the for boot and root options.
44 For the most modern systems you should use this conversion and then run
47 Template: liloconfig/maintitle
49 _Description: LILO configuration.
51 Template: liloconfig/banner
53 _Description: LILO, the LInux LOader, sets up your system to boot Linux directly from your hard disk, without the need for a boot floppy.
55 Template: liloconfig/configuring_base
57 _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...
59 Template: liloconfig/liloconf_exists
61 _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.
63 Template: liloconfig/liloconf_incompatible
65 _Description: WARNING!
66 You have an old incompatible lilo configuration file!
67 Read the file /usr/share/doc/lilo/INCOMPAT.gz and rerun /sbin/lilo to write the
68 changes to your boot sectors
70 Template: liloconfig/use_current_lilo
73 _Description: Install a boot block using your current LILO configuration?
75 Template: liloconfig/lilo_warning
77 _Description: WARNING!
78 Even if lilo runs successfully, see /usr/share/doc/lilo/INCOMPAT.gz for
79 changes in the usage of the ${liloconf} file. If needed: edit ${liloconf} and
82 Template: liloconfig/select_bitmap
84 Choices: /boot/tuxlogo.bmp, /boot/inside.bmp, /boot/debian.bmp, /boot/debian-de.bmp, /boot/debianlilo.bmp, /boot/coffee.bmp, /boot/onlyblue.bmp
85 Default: /boot/debian.bmp
86 _Description: The following is the list of the available bitmaps
88 Template: liloconfig/lilo_error
91 Correct ${liloconf} manually and rerun /sbin/lilo.
93 Template: liloconfig/wipe_old_liloconf
96 _Description: Wipe out your old LILO configuration and make a new one?
98 Template: liloconfig/no_changes
100 _Description: No changes made.
102 Template: liloconfig/fstab_broken
104 _Description: WARNING!
105 Either your ${fstab} configuration file is missing, or it doesn't contain a
106 valid entry for the root filesystem! This generally means that your system is
107 very badly broken. Configuration of LILO will be aborted; you should try to
108 repair the situation and then run /usr/sbin/liloconfig again to retry the
109 configuration process.
111 Template: liloconfig/odd_fstab
113 _Description: WARNING!
114 Your ${fstab} configuration file gives device ${device} as the root filesystem
115 device. This doesn't look to me like an "ordinary" block device. Either your
116 fstab is broken and you should fix it, or you are using hardware (such as a
117 RAID array) which this simple configuration program does not handle.
119 You should either repair the situation or hand-roll your own ${liloconf}
120 configuration file; you can then run /usr/sbin/liloconfig again to retry the
121 configuration process. Documentation for LILO can be found in
122 /usr/share/doc/lilo/.
124 Template: liloconfig/instruction
126 _Description: Booting from hard disk.
127 You must do three things to make the Linux system boot from the hard disk.
128 Install a partition boot record, install a master boot record, and set the
129 partition active. You'll be asked to perform each of these tasks. You may skip
130 any or all of them, and perform them manually later on.
132 This will result in Linux being booted by default from the hard disk. If your
133 setup is complicated or unusual you should consider writing your own
134 customised ${liloconf}. To do this you should exit this configuration program
135 and refer to the comprehensive lilo documentation, which can be found in
136 /usr/share/doc/lilo/.
138 Template: liloconfig/install_from_root_device
141 _Description: Install a partition boot record to boot Linux from ${device}?
143 Template: liloconfig/use_lba32
146 _Description: Use LBA32 for addressing big disks using new BIOS features?
148 Template: liloconfig/install_mbr
151 _Description: Install a master boot record on ${disk}?
152 A master boot record is required to run the partition boot record. If you are
153 already using a boot manager, and want to keep it, answer "no" to the
154 following question. If you don't know what a boot manager is or whether you
155 have one, answer "yes".
157 Template: liloconfig/mbr_error
160 install-mbr failed! Your system may not be bootable.
162 Template: liloconfig/make_active_partition
165 _Description: Make ${device} the active partition
166 The master boot record will boot the active partition. If you want your system
167 to boot another operating system, such as DOS or Windows, by default, answer
168 "no" to the following question. You may still use your boot manager or the
169 master boot record to boot Linux. If you want the system to boot Linux by
170 default, answer "yes". In this case you could still boot some other OS if you
171 know what partition it is on.
173 Template: liloconfig/activate_error
176 activate failed! Your system may not be bootable.