]>
Commit | Line | Data |
---|---|---|
c3f29c31 | 1 | |
2 | # This file is concatenated. Do not delete the newline above. | |
3 | ||
21bcb0cb | 4 | Template: grub-pc/chainload_from_menu.lst |
5 | Type: boolean | |
6 | Default: true | |
bbc92c01 | 7 | #flag:translate!:6 |
0cfadf0a | 8 | _Description: Chainload from menu.lst? |
21bcb0cb | 9 | GRUB upgrade scripts have detected a GRUB Legacy setup in /boot/grub. |
10 | . | |
11 | In order to replace the Legacy version of GRUB in your system, it is | |
12 | recommended that /boot/grub/menu.lst is adjusted to chainload GRUB 2 | |
13 | from your existing GRUB Legacy setup. This step may be automaticaly | |
14 | performed now. | |
15 | . | |
16 | It's recommended that you accept chainloading GRUB 2 from menu.lst, and | |
17 | verify that your new GRUB 2 setup is functional for you, before you install | |
18 | it directly to your MBR (Master Boot Record). | |
19 | . | |
46017f53 | 20 | In either case, whenever you want GRUB 2 to be loaded directly from MBR, |
21bcb0cb | 21 | you can do so by issuing (as root) the following command: |
22 | . | |
10c72361 | 23 | upgrade-from-grub-legacy |
401dd69b | 24 | |
9f2facb3 | 25 | Template: grub-pc/install_devices |
26 | Type: multiselect | |
ce2a43c8 | 27 | Choices-C: ${RAW_CHOICES} |
9f2facb3 | 28 | Choices: ${CHOICES} |
29 | # Intentionally not marked for translations yet; will do after a review period | |
30 | Description: GRUB install devices: | |
31 | The grub-pc package is being upgraded. This menu allows you to select which | |
32 | devices you'd like grub-install to be automatically run for, if any. | |
33 | . | |
34 | It is recommended that you do this in most situations, to prevent the installed | |
35 | GRUB from getting out of sync with other components such as grub.cfg or with | |
36 | newer Linux images it will have to load. | |
37 | . | |
38 | If you're unsure which drive is designated as boot drive by your BIOS, it is | |
39 | often a good idea to install GRUB to all of them. | |
d7c23e1d | 40 | . |
ce2a43c8 CW |
41 | Note: It is possible to install GRUB to partition boot records as well, and |
42 | some appropriate partitions are offered here. However, this forces GRUB to | |
43 | use the blocklist mechanism, which makes it less reliable, and therefore is | |
44 | not recommended. | |
45 | ||
46 | Template: grub-pc/install_devices_disks_changed | |
47 | Type: multiselect | |
48 | Choices-C: ${RAW_CHOICES} | |
49 | Choices: ${CHOICES} | |
50 | # Intentionally not marked for translations yet; will do after a review period | |
51 | Description: GRUB install devices: | |
52 | The GRUB boot loader was previously installed to a disk that is no longer | |
53 | present, or whose normally unique identifier has changed for some reason. | |
54 | It is important to make sure that the installed GRUB stays in sync with | |
55 | other components such as grub.cfg or with newer Linux images it will have | |
56 | to load, and so you should check again to make sure that GRUB is installed | |
57 | to the appropriate boot devices. | |
58 | . | |
59 | If you're unsure which drive is designated as boot drive by your BIOS, it is | |
60 | often a good idea to install GRUB to all of them. | |
61 | . | |
62 | Note: It is possible to install GRUB to partition boot records as well, and | |
63 | some appropriate partitions are offered here. However, this forces GRUB to | |
64 | use the blocklist mechanism, which makes it less reliable, and therefore is | |
65 | not recommended. | |
66 | ||
67 | Template: grub-pc/disk_description | |
68 | Type: text | |
69 | # Disk sizes are in decimal megabytes, to match how disk manufacturers | |
70 | # usually describe them. | |
71 | _Description: ${DEVICE} (${SIZE} MB, ${MODEL}) | |
72 | ||
73 | Template: grub-pc/partition_description | |
74 | Type: text | |
75 | # The "-" is used to indicate indentation. Leading spaces may not work. | |
76 | Description: - ${DEVICE} (${SIZE} MB, ${PATH}) | |
77 | ||
78 | Template: grub-pc/install_devices_failed | |
79 | Type: boolean | |
80 | Default: false | |
81 | #flag:translate!:3 | |
82 | _Description: GRUB installation failed. Continue? | |
83 | GRUB failed to install to the following devices: | |
84 | . | |
85 | ${FAILED_DEVICES} | |
86 | . | |
87 | Do you want to continue anyway? If you do, your computer may not start up | |
88 | properly. | |
90159517 | 89 | |
e074c3fc CW |
90 | Template: grub-pc/install_devices_failed_upgrade |
91 | Type: boolean | |
92 | Default: true | |
93 | #flag:translate!:3 | |
94 | _Description: GRUB installation failed. Try again? | |
95 | GRUB failed to install to the following devices: | |
96 | . | |
97 | ${FAILED_DEVICES} | |
98 | . | |
99 | You may be able to install GRUB to some other device, although you should | |
100 | check that your system will boot from that device. Otherwise, the upgrade | |
101 | from GRUB Legacy will be cancelled. | |
102 | ||
c14d87ed CW |
103 | Template: grub-pc/install_devices_empty |
104 | Type: boolean | |
105 | Default: false | |
106 | _Description: Continue without installing GRUB? | |
107 | You chose not to install GRUB to any devices. If you continue, the boot | |
108 | loader may not be properly configured, and when your computer next starts | |
109 | up it will use whatever was previously in the boot sector. If there is an | |
110 | earlier version of GRUB 2 in the boot sector, it may be unable to load | |
111 | modules or handle the current configuration file. | |
112 | . | |
113 | If you are already running a different boot loader and want to carry on | |
114 | doing so, or if this is a special environment where you do not need a boot | |
115 | loader, then you should continue anyway. Otherwise, you should install | |
116 | GRUB somewhere. | |
117 | ||
90159517 | 118 | Template: grub-pc/postrm_purge_boot_grub |
119 | Type: boolean | |
120 | Default: false | |
f4d02196 | 121 | # This should get reviewed before it can be translated |
90159517 | 122 | Description: Remove GRUB 2 from /boot/grub? |
123 | Do you want to have all GRUB 2 files removed from /boot/grub? | |
124 | . | |
125 | Your system would be then unbootable if you don't install another bootloader. | |
c3af9ad6 | 126 | |
4830efd9 CW |
127 | Template: grub-pc/mixed_legacy_and_grub2 |
128 | Type: boolean | |
129 | Default: true | |
146206b7 | 130 | #flag:translate!:3 |
4830efd9 CW |
131 | _Description: Finish conversion to GRUB 2 now? |
132 | This system still has files from the GRUB Legacy boot loader installed, but | |
133 | it now also has GRUB 2 boot records installed on these disks: | |
134 | . | |
146206b7 | 135 | ${DISKS} |
4830efd9 CW |
136 | . |
137 | It seems likely that GRUB Legacy is no longer in use, and that you should | |
138 | instead upgrade the GRUB 2 images on these disks and finish the conversion | |
139 | to GRUB 2 by removing old GRUB Legacy files. If you do not upgrade these | |
140 | GRUB 2 images, then they may be incompatible with the new packages and | |
141 | cause your system to stop booting properly. | |
142 | . | |
143 | You should generally finish the conversion to GRUB 2 unless these boot | |
144 | records were created by a GRUB 2 installation on some other operating | |
145 | system. | |
146 | ||
c3af9ad6 | 147 | Template: grub-pc/kopt_extracted |
148 | Type: boolean | |
149 | Default: false | |
150 | Description: for internal use |