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/upgrade
12 _Description: Deprecated parameters in LILO configuration
13 Deprecated files have been found on your system.
14 You must update the 'install=' parameter in your LILO configuration file
15 (/etc/lilo.conf) in order to properly upgrade the package.
17 The new 'install=' options are:
20 old: install=/boot/boot-bmp.b
23 old: install=/boot/boot-text.b
26 old: install=/boot/boot-menu.b or boot.b
28 Template: lilo/add_large_memory
31 _Description: Do you want to add the large-memory option?
32 Usually LILO loads the initrd file into the first 15MB of memory to
33 avoid a BIOS limitation with older systems (earlier than 2001 and
34 few systems until 2004).
36 With newer kernels the combination of kernel and initrd may not fit
37 into the first 15MB of memory. LILO compute the needed size of memory
38 and will automatically use the memory above 15MB, too, if there is
39 enough physical memory.
41 If this machine has a recent BIOS without a 15MB limitation and you
42 want to use memory above 15MB for all kernels, set the 'large-memory'
48 _Description: Do you want to run /sbin/lilo now?
49 It was detected that it's necessary to run /sbin/lilo in order to update
50 the new LILO configuration.
52 WARNING: This procedure will write data in your MBR and may overwrite
53 some things in that place. If you skip this step, you must run /sbin/lilo
54 before reboot your computer or your system may not boot again.
56 Template: lilo/diskid_uuid
59 _Description: Do you want to convert boot and root options?
60 Until kernel using the newer disk interface 'libata' you need the newer
61 DiskID and/or UUID in your /etc/lilo.conf the for boot and root options.
62 For the most modern systems you should use this conversion and then run
65 Template: liloconfig/maintitle
67 _Description: LILO configuration.
69 Template: liloconfig/banner
71 _Description: LILO, the LInux LOader, sets up your system to boot Linux directly from your hard disk, without the need for a boot floppy.
73 Template: liloconfig/configuring_base
75 _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...
77 Template: liloconfig/liloconf_exists
79 _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.
81 Template: liloconfig/liloconf_incompatible
83 _Description: WARNING!
84 You have an old incompatible lilo configuration file!
85 Read the file /usr/share/doc/lilo/INCOMPAT.gz and rerun /sbin/lilo to write the
86 changes to your boot sectors
88 Template: liloconfig/use_current_lilo
91 _Description: Install a boot block using your current LILO configuration?
93 Template: liloconfig/lilo_warning
95 _Description: WARNING!
96 Even if lilo runs successfully, see /usr/share/doc/lilo/INCOMPAT.gz for
97 changes in the usage of the ${liloconf} file. If needed: edit ${liloconf} and
100 Template: liloconfig/select_bitmap
102 Choices: /boot/tuxlogo.bmp, /boot/inside.bmp, /boot/debianlilo.bmp, /boot/coffee.bmp, /boot/onlyblue.bmp
103 Default: /boot/debian.bmp
104 _Description: The following is the list of the available bitmaps
106 Template: liloconfig/lilo_error
109 Correct ${liloconf} manually and rerun /sbin/lilo.
111 Template: liloconfig/wipe_old_liloconf
114 _Description: Wipe out your old LILO configuration and make a new one?
116 Template: liloconfig/no_changes
118 _Description: No changes made.
120 Template: liloconfig/fstab_broken
122 _Description: WARNING!
123 Either your ${fstab} configuration file is missing, or it doesn't contain a
124 valid entry for the root filesystem! This generally means that your system is
125 very badly broken. Configuration of LILO will be aborted; you should try to
126 repair the situation and then run /usr/sbin/liloconfig again to retry the
127 configuration process.
129 Template: liloconfig/odd_fstab
131 _Description: WARNING!
132 Your ${fstab} configuration file gives device ${device} as the root filesystem
133 device. This doesn't look to me like an "ordinary" block device. Either your
134 fstab is broken and you should fix it, or you are using hardware (such as a
135 RAID array) which this simple configuration program does not handle.
137 You should either repair the situation or hand-roll your own ${liloconf}
138 configuration file; you can then run /usr/sbin/liloconfig again to retry the
139 configuration process. Documentation for LILO can be found in
140 /usr/share/doc/lilo/.
142 Template: liloconfig/instruction
144 _Description: Booting from hard disk.
145 You must do three things to make the Linux system boot from the hard disk.
146 Install a partition boot record, install a master boot record, and set the
147 partition active. You'll be asked to perform each of these tasks. You may skip
148 any or all of them, and perform them manually later on.
150 This will result in Linux being booted by default from the hard disk. If your
151 setup is complicated or unusual you should consider writing your own
152 customised ${liloconf}. To do this you should exit this configuration program
153 and refer to the comprehensive lilo documentation, which can be found in
154 /usr/share/doc/lilo/.
156 Template: liloconfig/install_from_root_device
159 _Description: Install a partition boot record to boot Linux from ${device}?
161 Template: liloconfig/use_lba32
164 _Description: Use LBA32 for addressing big disks using new BIOS features?
166 Template: liloconfig/install_mbr
169 _Description: Install a master boot record on ${disk}?
170 A master boot record is required to run the partition boot record. If you are
171 already using a boot manager, and want to keep it, answer "no" to the
172 following question. If you don't know what a boot manager is or whether you
173 have one, answer "yes".
175 Template: liloconfig/mbr_error
178 install-mbr failed! Your system may not be bootable.
180 Template: liloconfig/make_active_partition
183 _Description: Make ${device} the active partition
184 The master boot record will boot the active partition. If you want your system
185 to boot another operating system, such as DOS or Windows, by default, answer
186 "no" to the following question. You may still use your boot manager or the
187 master boot record to boot Linux. If you want the system to boot Linux by
188 default, answer "yes". In this case you could still boot some other OS if you
189 know what partition it is on.
191 Template: liloconfig/activate_error
194 activate failed! Your system may not be bootable.