debconf template rewirte.
project smith hit the linux-2.6 templates. linux-2.6 should generate now much less lintian warnings. thanks to bubulle!!! svn path=/dists/trunk/linux-2.6/; revision=11084
This commit is contained in:
Maximilian Attems
parent
1be0575a02
commit
ebf431faad
|
|
@ -95,6 +95,10 @@ linux-2.6 (2.6.25~rc9-1~experimental.1) UNRELEASED; urgency=low
|
|||
* topconfig: Enable CONFIG_CIFS_WEAK_PW_HASH, required for compatibility
|
||||
with legacy (pre-NTLM) fileservers.
|
||||
|
||||
[ Christian Perrier ]
|
||||
* Debconf template rewrite + mark them as translatable.
|
||||
Thanks to Justin B Rye <jbr@edlug.org.uk> for review.
|
||||
|
||||
-- Bastian Blank <waldi@debian.org> Tue, 26 Feb 2008 23:59:55 -0700
|
||||
|
||||
linux-2.6 (2.6.24-5) unstable; urgency=low
|
||||
|
|
|
|||
|
|
@ -1,193 +1,200 @@
|
|||
Template: =ST-image-=V/preinst/initrd-=V
|
||||
Type: text
|
||||
Description: You are installing a kernel with an initrd image
|
||||
#flag:translate!:4
|
||||
_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}.
|
||||
.
|
||||
I have been unable to find a suitable tool for generating initrd images
|
||||
(I looked at the list "${ramdisk}")
|
||||
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 in the same run. (This means, one from the following list
|
||||
${initrddep})
|
||||
right now. Suitable tools:
|
||||
.
|
||||
${initrddep}
|
||||
|
||||
Template: =ST-image-=V/preinst/bootloader-initrd-=V
|
||||
Type: boolean
|
||||
Default: true
|
||||
Description: Do you want to abort now?
|
||||
You are attempting to install an initrd kernel image (version =V)
|
||||
This will not work unless you have configured your boot loader to use
|
||||
initrd. (An initrd image is a kernel image that expects to use an INITial
|
||||
#flag:translate!:6
|
||||
_Description: Abort initrd kernel image installation?
|
||||
You are attempting to install an initrd kernel image (version =V).
|
||||
This will not work unless the boot loader is configured to use an
|
||||
initrd.
|
||||
.
|
||||
An initrd image is a kernel image that expects to use an INITial
|
||||
Ram Disk to mount a minimal root file system into RAM and use that for
|
||||
booting).
|
||||
booting.
|
||||
.
|
||||
I repeat, You need to configure your boot loader -- please read your
|
||||
bootloader documentation for details on how to add initrd images.
|
||||
The boot loader must be configured to use such images and the system will not
|
||||
boot until this is done.
|
||||
.
|
||||
If you have already done so, and you wish to get rid of this message,
|
||||
please put
|
||||
"do_initrd = Yes"
|
||||
in /etc/kernel-img.conf. Note that this is optional, but if you do not,
|
||||
you will continue to see this message whenever you install a kernel
|
||||
image using initrd.
|
||||
This message will appear for any new kernel installation unless the
|
||||
following is added to /etc/kernel-img.conf:
|
||||
.
|
||||
"do_initrd = Yes"
|
||||
|
||||
Template: =ST-image-=V/preinst/lilo-initrd-=V
|
||||
Type: boolean
|
||||
Default: true
|
||||
Description: Do you want to abort now?
|
||||
You are attempting to install an initrd kernel image (version =V)
|
||||
This will not work unless you have configured your boot loader to use
|
||||
initrd. (An initrd image is a kernel image that expects to use an INITial
|
||||
Ram Disk to mount a minimal root file system into RAM and use that for
|
||||
booting).
|
||||
#flag:translate!:6
|
||||
_Description: Abort initrd kernel image installation?
|
||||
You are attempting to install an initrd kernel image (version =V).
|
||||
This will not work unless the boot loader is configured to use an
|
||||
initrd.
|
||||
.
|
||||
As a reminder, in order to configure LILO, you need to add an
|
||||
'initrd=/initrd.img' to the image=/vmlinuz stanza of your /etc/lilo.conf
|
||||
In order to configure LILO, you need to add
|
||||
'initrd=/initrd.img' to the image=/vmlinuz stanza of /etc/lilo.conf.
|
||||
.
|
||||
I repeat, You need to configure your boot loader -- please read your
|
||||
bootloader documentation for details on how to add initrd images.
|
||||
The boot loader must be configured to use such images and the system will not
|
||||
boot until this is done.
|
||||
.
|
||||
If you have already done so, and you wish to get rid of this message,
|
||||
please put
|
||||
"do_initrd = Yes"
|
||||
in /etc/kernel-img.conf. Note that this is optional, but if you do not,
|
||||
you will continue to see this message whenever you install a kernel
|
||||
image using initrd.
|
||||
This message will appear for any new kernel installation unless the
|
||||
following is added to /etc/kernel-img.conf:
|
||||
.
|
||||
"do_initrd = Yes"
|
||||
|
||||
Template: =ST-image-=V/preinst/elilo-initrd-=V
|
||||
Type: boolean
|
||||
Default: true
|
||||
Description: Do you want to abort now?
|
||||
You are attempting to install an initrd kernel image (version =V)
|
||||
This will not work unless you have configured your boot loader to use
|
||||
initrd. (An initrd image is a kernel image that expects to use an INITial
|
||||
Ram Disk to mount a minimal root file system into RAM and use that for
|
||||
booting).
|
||||
#flag:translate!:6
|
||||
_Description: Abort initrd kernel image installation?
|
||||
You are attempting to install an initrd kernel image (version =V).
|
||||
This will not work unless the boot loader is configured to use an
|
||||
initrd.
|
||||
.
|
||||
As a reminder, in order to configure ELILO, you need to add an
|
||||
'initrd=/initrd.img' to the image=/vmlinuz stanza of your /etc/elilo.conf
|
||||
In order to configure LILO, you need to add
|
||||
'initrd=/initrd.img' to the image=/vmlinuz stanza of /etc/elilo.conf.
|
||||
.
|
||||
I repeat, You need to configure your boot loader -- please read your
|
||||
bootloader documentation for details on how to add initrd images.
|
||||
The boot loader must be configured to use such images and the system will not
|
||||
boot until this is done.
|
||||
.
|
||||
If you have already done so, and you wish to get rid of this message,
|
||||
please put
|
||||
"do_initrd = Yes"
|
||||
in /etc/kernel-img.conf. Note that this is optional, but if you do not,
|
||||
you will continue to see this message whenever you install a kernel
|
||||
image using initrd.
|
||||
This message will appear for any new kernel installation unless the
|
||||
following is added to /etc/kernel-img.conf:
|
||||
.
|
||||
"do_initrd = Yes"
|
||||
|
||||
Template: =ST-image-=V/preinst/lilo-has-ramdisk
|
||||
Type: text
|
||||
Description: Lilo has a ramdisk line, which should be commented or removed
|
||||
I have found a line
|
||||
#flag:translate!:3
|
||||
_Description: Removal of 'ramdisk' in /etc/lilo.conf
|
||||
The following line in /etc/lilo.conf should be removed or commented out,
|
||||
since the system uses initrd (or initramfs):
|
||||
.
|
||||
${LINE}
|
||||
in /etc/lilo.conf that should be removed or commented out, since you are using
|
||||
initrd/initramfs.
|
||||
|
||||
Template: =ST-image-=V/preinst/abort-install-=V
|
||||
Type: note
|
||||
Description: Aborting install since loading an initrd kernel image
|
||||
You are attempting to install an initrd kernel image (version
|
||||
=V) This will not work unless you have configured your boot
|
||||
loader to use initrd. (An initrd image is a kernel image that expects
|
||||
to use an INITial Ram Disk to mount a minimal root file system into
|
||||
RAM and use that for booting). Unfortunately, since this Question
|
||||
pertaining to this was not shown, and the default action is to abort
|
||||
the install. =ST-image-=V aborted.
|
||||
|
||||
_Description: Aborting install of unsupported initrd kernel image
|
||||
You are attempting to install an initrd kernel image (version =V).
|
||||
This will not work unless the boot loader is configured to use an
|
||||
initrd.
|
||||
.
|
||||
An initrd image is a kernel image that expects to use an INITial
|
||||
Ram Disk to mount a minimal root file system into RAM and use that for
|
||||
booting.
|
||||
.
|
||||
As the question that's relevant for this situation
|
||||
was not shown, =ST-image-=V installation has been aborted.
|
||||
|
||||
Template: =ST-image-=V/preinst/failed-to-move-modules-=V
|
||||
Type: note
|
||||
Description: Failed to move modules out of the way, aborting
|
||||
You are attempting to install a kernel image (version =V)
|
||||
_Description: Modules removal failure
|
||||
You are attempting to install a kernel image (version =V).
|
||||
However, the directory ${modules_base}/=V/kernel still exists.
|
||||
.
|
||||
As you have instructed, an attempt was made to move the directory out
|
||||
of the way. Unfortunately, There was a problem moving
|
||||
${modules_base}/=V to ${modules_base}/${dest}.
|
||||
An attempt was made to move the directory. However, that
|
||||
action failed and ${modules_base}/=V could not be moved to
|
||||
${modules_base}/${dest}.
|
||||
.
|
||||
I suggest you move $modules_base/$version out of the way manually,
|
||||
and then try re-installing this image.
|
||||
.
|
||||
I am aborting.
|
||||
You should move $modules_base/$version manually
|
||||
and try re-installing this image.
|
||||
|
||||
Template: =ST-image-=V/preinst/overwriting-modules-=V
|
||||
Type: boolean
|
||||
Default: true
|
||||
Description: Stop install since the kernel-image is already installed?
|
||||
You are attempting to install a kernel image (version =V)
|
||||
However, the directory ${modules_base}/=V/kernel still exists. If this
|
||||
directory belongs to a previous ${package} package, and if
|
||||
you have deselected some modules, or installed standalone modules
|
||||
packages, this could be bad.
|
||||
_Description: Abort installation since the kernel-image is already installed?
|
||||
You are attempting to install a kernel image (version =V).
|
||||
However, the directory ${modules_base}/=V/kernel still exists.
|
||||
.
|
||||
If ${modules_base}/=V/kernel belongs to a old install of
|
||||
${package}, then this is your last chance to abort the
|
||||
If this directory belongs to a previous ${package} package, and if
|
||||
you have deselected some modules, or installed standalone modules
|
||||
packages, this could have unexpected consequences.
|
||||
.
|
||||
If ${modules_base}/=V/kernel belongs to an old install of
|
||||
${package}, you can now abort the
|
||||
installation of this kernel image (nothing has been changed yet).
|
||||
.
|
||||
If you know what you are doing, and if you feel that this
|
||||
image should be installed despite this anomaly, Please answer n to the
|
||||
question.
|
||||
It is recommended to abort the installation unless you are
|
||||
sure of what you are doing.
|
||||
.
|
||||
Otherwise, I suggest you move ${modules_base}/=V/kernel out of the way,
|
||||
perhaps to ${modules_base}/=V.kernel.old or something, and then try
|
||||
If you abort the installation, you should then move
|
||||
${modules_base}/=V/kernel (for instance as
|
||||
${modules_base}/=V.kernel.old) and then try
|
||||
re-installing this image.
|
||||
|
||||
Template: =ST-image-=V/preinst/abort-overwrite-=V
|
||||
Type: note
|
||||
Description: Aborting install since modules exist
|
||||
_Description: Aborting installation since modules exist
|
||||
You are attempting to install an initrd kernel image (version
|
||||
=V). However, the corresponding kernel modules directory exists,
|
||||
and there was no permission given to silently delete the modules
|
||||
directory. Unfortunately, since this Question
|
||||
pertaining to this was not shown, and the default action is to abort
|
||||
the install. =ST-image-=V aborted.
|
||||
=V).
|
||||
.
|
||||
However, the corresponding kernel modules directory exists,
|
||||
and there was no permission given to silently delete the modules
|
||||
directory.
|
||||
.
|
||||
As the question that's relevant for this situation
|
||||
was not shown, =ST-image-=V installation has been aborted.
|
||||
|
||||
Template: =ST-image-=V/postinst/create-kimage-link-=V
|
||||
Type: boolean
|
||||
Default: true
|
||||
Description: Create a symbolic link to the current kernel image?
|
||||
I notice that you do not have ${kimage} symbolic link. I can create one
|
||||
for you, and it shall be updated by newer kernel image packages. This is
|
||||
useful if you use a boot loader like lilo.
|
||||
_Description: Create a symbolic link to the current kernel image?
|
||||
There is no ${kimage} symbolic link.
|
||||
.
|
||||
Such a link can be created now and will be updated by subsequently
|
||||
installed image packages. This will be useful with some boot loaders
|
||||
such as LILO.
|
||||
|
||||
Template: =ST-image-=V/postinst/kimage-is-a-directory
|
||||
Type: note
|
||||
Description: Image symbolic link destination is a directory, aborting
|
||||
${kimage} is a directory, which I did not expect. I am trying to create a
|
||||
symbolic link with that name linked to ${image_dest}. Since a directory
|
||||
exists here, my assumptions are way off, and I am aborting.
|
||||
_Description: Image symbolic link destination is a directory, aborting
|
||||
${kimage} is a directory, which is unepected. There is no method to
|
||||
handle that situation automatically and the kernel image
|
||||
installation has been aborted.
|
||||
|
||||
Template: =ST-image-=V/postinst/depmod-error-=V
|
||||
Type: boolean
|
||||
Default: false
|
||||
Description: Do you want to abort now?
|
||||
This may be benign, (You may have versioned symbol names, for instance).
|
||||
Or this could be an error. depmod exited with return value ${exit_value}
|
||||
${SIGNAL}${CORE}.
|
||||
I am deleting the file ${modules_base}/=V/modules.dep. However,
|
||||
since depmod is run at install time, we could just defer running depmod.
|
||||
_Description: Abort installation after depmod error?
|
||||
The 'depmod' command exited with the exit code ${exit_value}
|
||||
(${SIGNAL}${CORE}).
|
||||
.
|
||||
This may be benign, for instance because of versioned symbol names.
|
||||
.
|
||||
Please choose whether the installation should be aborted or the error
|
||||
just ignored.
|
||||
|
||||
Template: =ST-image-=V/postinst/depmod-error-initrd-=V
|
||||
Type: boolean
|
||||
Default: false
|
||||
Description: Do you want to abort now?
|
||||
This may be benign, (You may have versioned symbol names, for instance).
|
||||
Or this could be an error. depmod exited with return value ${exit_value}
|
||||
. ${SIGNAL} ${CORE}
|
||||
Since this image uses initrd, I am not deleting the file
|
||||
${modules_base}/=V/modules.dep. However, there is no guarantee that the
|
||||
file is valid. I would strongly advice you to either abort and fix the
|
||||
errors in depmod, or regenerate the initrd image with a known good
|
||||
modules.dep file. I repeat, an initrd kernel image with a bad modules.dep
|
||||
shall fail to boot.
|
||||
_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: =ST-image-=V/postinst/old-initrd-link-=V
|
||||
Type: boolean
|
||||
Default: true
|
||||
Description: Should the old initrd link be deleted now?
|
||||
I note that you have an old initrd symbolic link in place. The name of
|
||||
_Description: Should the old initrd link be deleted now?
|
||||
There is an old initrd symbolic link in place. The name of
|
||||
the symbolic link is being changed to initrd.img. If the old link is
|
||||
deleted, you may have to update the boot loader. If the link is left in
|
||||
place, it will point to the wrong image.
|
||||
|
|
@ -195,83 +202,88 @@ Description: Should the old initrd link be deleted now?
|
|||
Template: =ST-image-=V/postinst/old-dir-initrd-link-=V
|
||||
Type: boolean
|
||||
Default: true
|
||||
Description: Should the old initrd link be deleted now?
|
||||
I note that you have an old ${image_dir}/initrd symbolic link in
|
||||
place. The location of the symbolic link is now the same location as
|
||||
the kernel image symbolic links, namely, in ${image_dest}. If the old
|
||||
_Description: Should the old initrd link be deleted now?
|
||||
There is an old ${image_dir}/initrd symbolic link in
|
||||
place. The location of the symbolic link is now the same location as
|
||||
the kernel image symbolic links, in ${image_dest}. If the old
|
||||
link is deleted, you may have to update the boot loader. If the link
|
||||
is left in place, it will point to the wrong image.
|
||||
|
||||
Template: =ST-image-=V/postinst/old-system-map-link-=V
|
||||
Type: boolean
|
||||
Default: true
|
||||
Description: Should the old /System.map link be deleted now?
|
||||
You have /System.map symbolic link. These were installed by ancient
|
||||
kernel image packages. However, all the programs that look at the
|
||||
information in the map files (including top, ps, and klogd)
|
||||
also will look at /boot/System.map-=V
|
||||
Having the symbolic link in / is technically detrimental
|
||||
(apart from cluttering up /); many programs, though looking in /boot,
|
||||
still allow /System.map to override. If you install multiple kernels
|
||||
on this machine, then the /System.map symbolic link only
|
||||
applies to one such kernel, for all other choices the symbols loaded
|
||||
will be wrong. Not having /System.map at all prevents this.
|
||||
_Description: Should the old /System.map link be deleted now?
|
||||
There is a /System.map symbolic link. Such links were installed by ancient
|
||||
kernel image packages.
|
||||
.
|
||||
However, all the programs that look at the
|
||||
information in the map files (including top, ps, and klogd)
|
||||
will also look at /boot/System.map-=V.
|
||||
.
|
||||
Some programs may however give priority to /System.map and it
|
||||
is therefore recommended to delete that link.
|
||||
|
||||
Template: shared/kernel-image/really-run-bootloader
|
||||
Type: boolean
|
||||
Default: true
|
||||
Description: Run the default bootloader?
|
||||
_Description: Run the default boot loader?
|
||||
The default boot loader for this architecture is $loader, which is
|
||||
present. However, you have not explicitly requested the boot loader
|
||||
$loader should be run in the configuration file /etc/kernel-img.conf,
|
||||
and you seem to have grub installed, and have set a postinst hook
|
||||
(which is used to hook in grub after a kernel image installation). At
|
||||
this point, it is perfectly likely that this system is using grub as a
|
||||
bootloader, and not the builtin default of $loader. If that is the case,
|
||||
running $loader instead of grub might make the machine unbootable. I need
|
||||
to know whether to run the default bootloader $loader, or just let the
|
||||
postinst hook script update grub later. The default is to run $loader.
|
||||
|
||||
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 boot loader ${loader} in test mode.
|
||||
_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}, or make other arrangements to boot your machine.
|
||||
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 in test mode.
|
||||
An error occurred while running the boot loader ${loader}.
|
||||
_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}, or make other arrangements to boot your machine.
|
||||
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: Do you want to abort removal now?
|
||||
_Description: Abort kernel removal?
|
||||
You are running a kernel (version ${running}) and attempting to remove
|
||||
the same version. This is a potentially disastrous action. Not only
|
||||
will /boot/vmlinuz-${running} be removed, making it impossible to boot
|
||||
it, (you will have to take action to change your boot loader to boot
|
||||
a new kernel), it will also remove all modules under the directory
|
||||
/lib/modules/${running}. Just having a copy of the kernel image is not
|
||||
enough, you will have to replace the modules too.
|
||||
the same version.
|
||||
.
|
||||
I repeat, this is very dangerous. If at all in doubt, answer Yes. If
|
||||
you know exactly what you are doing, and are prepared to hose your
|
||||
system, then answer No.
|
||||
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: Do you want to abort removal now?
|
||||
You have a valid /etc/${loader}.conf file that mentions
|
||||
${kimage}-=V. Removing =ST-image-=V would invalidate
|
||||
that file. (you will have to edit /etc/${loader}.conf or re-target
|
||||
symbolic links mentioned there (typically, /vmlinuz and /vmlinuz.old)
|
||||
to not refer to ${kimage}-=V and will have to re-run ${loader}).
|
||||
_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.
|
||||
.
|
||||
I repeat: you shall have to make changes to your boot loader setup
|
||||
and will have to re-run ${loader}.
|
||||
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.
|
||||
|
|
|
|||
Loading…
Reference in New Issue