blob: 99149f229cb1eae2df28ce987560e134c0b4beff (
plain)
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
84
85
86
87
88
89
90
91
92
93
|
Template: =ST-image-=V/preinst/initrd-=V
Type: text
Description: Initial RAMdisk image generation impossible
You are attempting to install an initrd kernel image (version
=V) on a machine currently running kernel version
${hostversion}.
.
No suitable tool for generating initrd images was found in
${ramdisk} and therefore no initrd image can be generated.
This will break the installation, unless such tools are also being installed
right now. Suitable tools:
.
${initrddep}
Template: =ST-image-=V/postinst/depmod-error-initrd-=V
Type: boolean
Default: false
Description: Abort installation after depmod error?
The 'depmod' command exited with the exit code ${exit_value}
(${SIGNAL}${CORE}).
.
Since this image uses initrd, the ${modules_base}/=V/modules.dep file
will not be deleted, even though it may be invalid.
.
You should abort the installation and fix the
errors in depmod, or regenerate the initrd image with a known good
modules.dep file. If you don't abort the installation, there is
a danger that the system will fail to boot.
Template: shared/kernel-image/really-run-bootloader
Type: boolean
Default: true
Description: Run the default boot loader?
The default boot loader for this architecture is $loader, which is
present.
.
However, there is no explicit request to run that boot loader in
/etc/kernel-img.conf while GRUB seems to be installed with
a postinst hook set.
.
It thus seems that this system is using GRUB as
boot loader instead of $loader.
.
Please choose which should run: the default boot loader now, or the
GRUB update later.
Template: =ST-image-=V/postinst/bootloader-test-error-=V
Type: note
Description: Error running the boot loader in test mode
An error occurred while running the ${loader} boot loader in test mode.
.
A log is available in ${temp_file_name}. Please edit /etc/${loader}.conf
manually and re-run ${loader} to fix that issue and keep this system
bootable.
Template: =ST-image-=V/postinst/bootloader-error-=V
Type: note
Description: Error running the boot loader
An error occurred while running the ${loader} boot loader.
.
A log is available in ${temp_file_name}. Please edit /etc/${loader}.conf
manually and re-run ${loader} to fix that issue and keep this system
bootable.
Template: =ST-image-=V/prerm/removing-running-kernel-=V
Type: boolean
Default: true
Description: Abort kernel removal?
You are running a kernel (version ${running}) and attempting to remove
the same version.
.
This can make the system unbootable as it will remove
/boot/vmlinuz-${running} and all modules under the directory
/lib/modules/${running}. This can only be fixed with a copy of the
kernel image and the corresponding modules.
.
It is highly recommended to abort the kernel removal unless you are
prepared to fix the system after removal.
Template: =ST-image-=V/prerm/would-invalidate-boot-loader-=V
Type: boolean
Default: true
Description: Abort kernel removal?
This system uses a valid /etc/${loader}.conf file that mentions
${kimage}-=V. Removing =ST-image-=V will invalidate
that file.
.
You will need to edit /etc/${loader}.conf or re-target
symbolic links mentioned there (typically, /vmlinuz and /vmlinuz.old)
to not refer to ${kimage}-=V. Then, you will have to re-run ${loader}.
.
It is highly recommended to abort the kernel removal unless you are
prepared to fix the system after removal.
|
