-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathtemplates.in
83 lines (75 loc) · 3.45 KB
/
templates.in
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
Template: grub2/linux_cmdline
Type: string
_Description: Linux command line:
The following Linux command line was extracted from /etc/default/grub or the
`kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct,
and modify it if necessary. The command line is allowed to be empty.
Template: grub2/linux_cmdline_default
Type: string
Default: @DEFAULT_CMDLINE@
_Description: Linux default command line:
The following string will be used as Linux parameters for the default menu
entry but not for the recovery mode.
Template: grub2/no_efi_extra_removable
Type: boolean
Default: false
_Description: Skip extra installation to the EFI removable media path?
Some EFI-based systems are buggy and do not handle new bootloaders correctly.
If you do not make an extra installation of GRUB to the EFI removable media
path, this may prevent your system from booting Debian correctly in case it is
affected by this problem. However, it may remove the ability to boot any other
operating systems that also depend on this path. If so, you will need to make
sure that GRUB is configured successfully to be able to boot any other OS
installations correctly.
Template: grub2/update_nvram
Type: boolean
Default: true
_Description: Update NVRAM variables to automatically boot into Debian?
GRUB can configure your platform's NVRAM variables so that it boots into
Debian automatically when powered on. However, you may prefer to disable
this behavior and avoid changes to your boot configuration. For example,
if your NVRAM variables have been set up such that your system contacts a
PXE server on every boot, this would preserve that behavior.
# still unused
Template: grub2/kfreebsd_cmdline
Type: string
_Description: kFreeBSD command line:
The following kFreeBSD command line was extracted from /etc/default/grub or the
`kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct,
and modify it if necessary. The command line is allowed to be empty.
# still unused
Template: grub2/kfreebsd_cmdline_default
Type: string
Default: @DEFAULT_CMDLINE@
_Description: kFreeBSD default command line:
The following string will be used as kFreeBSD parameters for the default menu
entry but not for the recovery mode.
Template: grub2/device_map_regenerated
Type: note
_Description: /boot/grub/device.map has been regenerated
The file /boot/grub/device.map has been rewritten to use stable device
names. In most cases, this should significantly reduce the need to change
it in future, and boot menu entries generated by GRUB should not be
affected.
.
However, since more than one disk is present in the system, it is possible
that the system is depending on the old device map. Please check whether
there are any custom boot menu entries that rely on GRUB's (hdN) drive
numbering, and update them if necessary.
.
If you do not understand this message, or if there are no custom
boot menu entries, you can ignore this message.
Template: grub2/unsigned_kernels_title
Type: title
_Description: unsigned kernels
Template: grub2/unsigned_kernels
Type: note
_Description: Cannot upgrade Secure Boot enforcement policy due to unsigned kernels
Your system has UEFI Secure Boot enabled in firmware, and the following kernels
present on your system are unsigned:
.
${unsigned_versions}
.
These kernels cannot be verified under Secure Boot. To ensure your system
remains bootable, GRUB will not be upgraded on your disk until these kernels are
removed or replaced with signed kernels.