diff -Nru /tmp/AeSHTp7tni/kernel-package-11.001/debian/changelog /tmp/E5EkzFiCzF/kernel-package-11.001.1/debian/changelog
--- /tmp/AeSHTp7tni/kernel-package-11.001/debian/changelog	2007-05-05 14:48:33.000000000 +0900
+++ /tmp/E5EkzFiCzF/kernel-package-11.001.1/debian/changelog	2007-11-15 22:28:40.000000000 +0900
@@ -1,3 +1,9 @@
+kernel-package (11.001.1) unstable; urgency=low
+
+  * Applied po-debconf patch. (Closes: #xxxxxx)
+
+ -- Kenshi Muto <kmuto@debian.org>  Thu, 15 Nov 2007 22:27:46 +0900
+
 kernel-package (11.001) unstable; urgency=low
 
   * Bug fix: "kernel-package: Typo "call" -> "cause" in make-kpkg(1)
diff -Nru /tmp/AeSHTp7tni/kernel-package-11.001/kernel/po/POTFILES.in /tmp/E5EkzFiCzF/kernel-package-11.001.1/kernel/po/POTFILES.in
--- /tmp/AeSHTp7tni/kernel-package-11.001/kernel/po/POTFILES.in	1970-01-01 09:00:00.000000000 +0900
+++ /tmp/E5EkzFiCzF/kernel-package-11.001.1/kernel/po/POTFILES.in	2007-11-15 22:29:23.000000000 +0900
@@ -0,0 +1 @@
+[type: gettext/rfc822deb] templates
diff -Nru /tmp/AeSHTp7tni/kernel-package-11.001/kernel/po/templates.pot /tmp/E5EkzFiCzF/kernel-package-11.001.1/kernel/po/templates.pot
--- /tmp/AeSHTp7tni/kernel-package-11.001/kernel/po/templates.pot	1970-01-01 09:00:00.000000000 +0900
+++ /tmp/E5EkzFiCzF/kernel-package-11.001.1/kernel/po/templates.pot	2007-11-15 22:29:23.000000000 +0900
@@ -0,0 +1,475 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
+# This file is distributed under the same license as the PACKAGE package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2007-11-15 22:29+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=CHARSET\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Type: text
+#. Description
+#: ../templates:1001
+msgid "You are installing a kernel with an initrd image"
+msgstr ""
+
+#. Type: text
+#. Description
+#: ../templates:1001
+msgid ""
+"You are attempting to install an initrd kernel image (version =V) on a "
+"machine currently running kernel version ${hostversion}."
+msgstr ""
+
+#. Type: text
+#. Description
+#: ../templates:1001
+msgid ""
+"I have been unable to find a suitable tool for generating initrd images (I "
+"looked at the list \"${ramdisk}\") 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})"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#: ../templates:2001 ../templates:3001 ../templates:4001 ../templates:13001
+#: ../templates:14001
+msgid "Do you want to abort now?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#: ../templates:2001 ../templates:3001 ../templates:4001
+msgid ""
+"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)."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#: ../templates:2001 ../templates:3001 ../templates:4001
+msgid ""
+"I repeat, You need to configure your boot loader -- please read your "
+"bootloader documentation for details on how to add initrd images."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#: ../templates:2001 ../templates:3001 ../templates:4001
+msgid ""
+"If you have already done so, and you wish to get rid of this message, please "
+"put\n"
+" \"do_initrd = Yes\"\n"
+"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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:3001
+msgid ""
+"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"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:4001
+msgid ""
+"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"
+msgstr ""
+
+#. Type: text
+#. Description
+#: ../templates:5001
+msgid "Lilo has a ramdisk line, which should be commented or removed"
+msgstr ""
+
+#. Type: text
+#. Description
+#: ../templates:5001
+msgid ""
+"I have found a line ${LINE} in /etc/lilo.conf that should be removed or "
+"commented out, since you are using initrd/initramfs."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:6001
+msgid "Aborting install since loading an initrd kernel image"
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:6001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:7001
+msgid "Failed to move modules out of the way, aborting"
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:7001
+msgid ""
+"You are attempting to install a kernel image (version =V) However, the "
+"directory ${modules_base}/=V/kernel still exists."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:7001
+msgid ""
+"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}."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:7001
+msgid ""
+"I suggest you move $modules_base/$version out of the way manually, and then "
+"try re-installing this image."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:7001
+msgid "I am aborting."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:8001
+msgid "Stop install since the kernel-image is already installed?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:8001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:8001
+msgid ""
+"If ${modules_base}/=V/kernel belongs to a old install of ${package}, then "
+"this is your last chance to abort the installation of this kernel image "
+"(nothing has been changed yet)."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:8001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:8001
+msgid ""
+"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 re-"
+"installing this image."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:9001
+msgid "Aborting install since modules exist"
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:9001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:10001
+msgid "The kernel version running is the same as the one being installed"
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:10001
+msgid ""
+"You are attempting to install a kernel version that is the same as the "
+"version you are currently running (version ${running}). The modules list is "
+"quite likely to have been changed, and the modules dependency file "
+"${modules_base}/=V/modules.dep needs to be re-built. It can not be built "
+"correctly right now, since the module list for the running kernel are likely "
+"to be different from the kernel installed. I am creating a new modules.dep "
+"file, but that may not be correct. It shall be regenerated correctly at next "
+"reboot."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:10001
+msgid ""
+"I repeat: you have to reboot in order for the modules file to be created "
+"correctly. Until you reboot, it may be impossible to load some modules. "
+"Reboot as soon as this install is finished (Do not reboot right now, since "
+"you may not be able to boot back up until installation is over, but boot "
+"immediately after). I can not stress that too much. You need to reboot soon."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:11001
+msgid "Create a symbolic link to the current kernel image?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:11001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:12001
+msgid "Image symbolic link destination is a directory, aborting"
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:12001
+msgid ""
+"${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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:13001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:14001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#: ../templates:15001 ../templates:16001
+msgid "Should the old initrd link be deleted now?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:15001
+msgid ""
+"I note that you have 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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:16001
+msgid ""
+"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 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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:17001
+msgid "Should the old /System.map link be deleted now?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:17001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:18001
+msgid "Run the default bootloader?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:18001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: note
+#. Description
+#. Type: note
+#. Description
+#: ../templates:19001 ../templates:20001
+msgid "Error running the boot loader in test mode."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:19001
+msgid ""
+"An error occurred while running the boot loader ${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."
+msgstr ""
+
+#. Type: note
+#. Description
+#: ../templates:20001
+msgid ""
+"An error occurred while running the boot loader ${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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#. Type: boolean
+#. Description
+#: ../templates:21001 ../templates:22001
+msgid "Do you want to abort removal now?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:21001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:21001
+msgid ""
+"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."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:22001
+msgid ""
+"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})."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates:22001
+msgid ""
+"I repeat: you shall have to make changes to your boot loader setup and will "
+"have to re-run ${loader}."
+msgstr ""
diff -Nru /tmp/AeSHTp7tni/kernel-package-11.001/kernel/ruleset/common/debconf.mk /tmp/E5EkzFiCzF/kernel-package-11.001.1/kernel/ruleset/common/debconf.mk
--- /tmp/AeSHTp7tni/kernel-package-11.001/kernel/ruleset/common/debconf.mk	2007-05-05 14:48:37.000000000 +0900
+++ /tmp/E5EkzFiCzF/kernel-package-11.001.1/kernel/ruleset/common/debconf.mk	2007-11-15 23:08:25.000000000 +0900
@@ -54,15 +54,15 @@
 # templates.master, or else the debian/templates file can get
 # damamged. 
 ifeq ($(PO2DEBCONF),yes)
-  ifeq (,$(wildcard debian/templates.master))
+  ifeq (,$(wildcard debian/templates.l10n))
 define CREATE_COMPATIBLE_TEMPLATE
-	echo Not modifying templates
+	echo 1 > debian/po/output
+	po2debconf debian/templates.in > debian/templates.l10n
+	rm -f debian/po/output
 endef
   else
 define CREATE_COMPATIBLE_TEMPLATE
-	echo 1 > debian/po/output
-	po2debconf debian/templates.master > debian/templates
-	rm -f debian/po/output
+	echo Not modifying templates
 endef
   endif
 else
@@ -73,13 +73,13 @@
 
 
 ifeq ($(PO2DEBCONF),yes)
-  ifeq (,$(wildcard debian/templates.master))
+  ifeq (,$(wildcard debian/templates.l10n))
 define INSTALL_TEMPLATE
-	echo using old template
+	po2debconf debian/templates.in > debian/templates.l10n
 endef
   else
 define INSTALL_TEMPLATE
-	po2debconf debian/templates.master > debian/templates
+	echo using old template
 endef
   endif
 else
diff -Nru /tmp/AeSHTp7tni/kernel-package-11.001/kernel/ruleset/targets/image.mk /tmp/E5EkzFiCzF/kernel-package-11.001.1/kernel/ruleset/targets/image.mk
--- /tmp/AeSHTp7tni/kernel-package-11.001/kernel/ruleset/targets/image.mk	2007-05-05 14:48:30.000000000 +0900
+++ /tmp/E5EkzFiCzF/kernel-package-11.001.1/kernel/ruleset/targets/image.mk	2007-11-15 22:52:53.000000000 +0900
@@ -276,6 +276,7 @@
             -e 's/=S/$(no_symlink)/g' -e 's@=B@$(KERNEL_ARCH)@g'     \
          $(DEBDIR)/pkg/image/prerm > $(TMPTOP)/DEBIAN/prerm
 	chmod 755 $(TMPTOP)/DEBIAN/prerm
+	$(INSTALL_TEMPLATE)
 	sed -e 's/=V/$(version)/g'    -e 's/=IB/$(link_in_boot)/g'    \
             -e 's/=ST/$(INT_STEM)/g'  -e 's/=R/$(reverse_symlink)/g' \
             -e 's/=K/$(kimage)/g'     -e 's/=L/$(loader)/g'          \
@@ -284,8 +285,7 @@
             -e 's/=MD/$(initrddep)/g'                                \
             -e 's@=M@$(MKIMAGE)@g'    -e 's/=OF/$(AM_OFFICIAL)/g'    \
             -e 's/=S/$(no_symlink)/g' -e 's@=B@$(KERNEL_ARCH)@g'     \
-          $(DEBDIR)/templates.in   > ./debian/templates.master
-	$(INSTALL_TEMPLATE)
+          ./debian/templates.l10n   > ./debian/templates.master
 	$(install_file) ./debian/templates.master $(TMPTOP)/DEBIAN/templates
   else
 	sed -e 's/=V/$(version)/g'    -e 's/=IB/$(link_in_boot)/g'    \
diff -Nru /tmp/AeSHTp7tni/kernel-package-11.001/kernel/templates.in /tmp/E5EkzFiCzF/kernel-package-11.001.1/kernel/templates.in
--- /tmp/AeSHTp7tni/kernel-package-11.001/kernel/templates.in	2007-05-05 14:48:30.000000000 +0900
+++ /tmp/E5EkzFiCzF/kernel-package-11.001.1/kernel/templates.in	2007-11-15 22:29:23.000000000 +0900
@@ -1,25 +1,22 @@
 Template: =ST-image-=V/preinst/initrd-=V
 Type: text
-Description:  You are installing a kernel with an initrd image
- 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}")
- 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})
+_Description:  You are installing a kernel with an initrd image
+ 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}") 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})
 
 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
- Ram Disk to mount a minimal root file system into RAM and use that for
- booting).
+_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).
  .
  I repeat, You need to configure your boot loader -- please read your
  bootloader documentation for details on how to add initrd images.
@@ -28,20 +25,19 @@
  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.
+ you will continue to see this message whenever you install a kernel image
+ using initrd.
 
 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).
+_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).
  .
- As a reminder, in order to configure LILO, you need to add an 
+ 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
  .
  I repeat, You need to configure your boot loader -- please read your
@@ -51,20 +47,19 @@
  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.
+ you will continue to see this message whenever you install a kernel image
+ using initrd.
 
 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).
+_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).
  .
- As a reminder, in order to configure ELILO, you need to add an 
+ 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
  .
  I repeat, You need to configure your boot loader -- please read your
@@ -74,61 +69,55 @@
  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.
+ you will continue to see this message whenever you install a kernel image
+ using initrd.
 
 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
- ${LINE}
- in /etc/lilo.conf that should be removed or commented out, since you are using 
- initrd/initramfs.
+_Description:  Lilo has a ramdisk line, which should be commented or removed
+ I have found a line ${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 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.
 
 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)
- 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}.
+_Description:  Failed to move modules out of the way, aborting
+ 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}.
  .
- I suggest you move $modules_base/$version out of the way manually,
- and then try re-installing this image.
+ I suggest you move $modules_base/$version out of the way manually, and
+ then try re-installing this image.
  .
  I am aborting.
 
 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. 
- .
- If ${modules_base}/=V/kernel belongs to a old install of
- ${package}, then this is your last chance to 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.
+_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.
+ .
+ If ${modules_base}/=V/kernel belongs to a old install of ${package}, then
+ this is your last chance to 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.
  .
  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
@@ -136,45 +125,43 @@
 
 Template: =ST-image-=V/preinst/abort-overwrite-=V
 Type: note
-Description:  Aborting install 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.
-
+_Description:  Aborting install 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.
 
 Template: =ST-image-=V/preinst/already-running-this-=V
 Type: note
-Description:  The kernel version running is the same as the one being installed
- You are attempting to install a kernel version that is the same as
- the version you are currently running (version ${running}). The modules
- list is quite likely to have been changed, and the modules dependency
- file ${modules_base}/=V/modules.dep needs to be re-built. It can
- not be built correctly right now, since the module list for the
- running kernel are likely to be different from the kernel installed.
- I am creating a new modules.dep file, but that may not be
- correct. It shall be regenerated correctly at next reboot.
- .
- I repeat: you have to reboot in order for the modules file to be
- created correctly. Until you reboot, it may be impossible to load
- some modules. Reboot as soon as this install is finished (Do not
- reboot right now, since you may not be able to boot back up until
- installation is over, but boot immediately after). I can not stress
- that too much. You need to reboot soon.
+_Description:  The kernel version running is the same as the one being installed
+ You are attempting to install a kernel version that is the same as the
+ version you are currently running (version ${running}). The modules list
+ is quite likely to have been changed, and the modules dependency file
+ ${modules_base}/=V/modules.dep needs to be re-built. It can not be built
+ correctly right now, since the module list for the running kernel are
+ likely to be different from the kernel installed. I am creating a new
+ modules.dep file, but that may not be correct. It shall be regenerated
+ correctly at next reboot.
+ .
+ I repeat: you have to reboot in order for the modules file to be created
+ correctly. Until you reboot, it may be impossible to load some modules.
+ Reboot as soon as this install is finished (Do not reboot right now, since
+ you may not be able to boot back up until installation is over, but boot
+ immediately after). I can not stress that too much. You need to reboot
+ soon.
 
 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 
+_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.
 
 Template: =ST-image-=V/postinst/kimage-is-a-directory
 Type: note
-Description:  Image symbolic link destination is a directory, aborting
+_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.
@@ -182,116 +169,114 @@
 Template: =ST-image-=V/postinst/depmod-error-=V
 Type: boolean
 Default: false
-Description:  Do you want to abort now?
+_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.
+ ${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.
 
 Template: =ST-image-=V/postinst/depmod-error-initrd-=V
 Type: boolean
 Default: false
-Description:  Do you want to abort now?
+_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 
+ 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 
+ 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.
 
 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
- 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.
+_Description:  Should the old initrd link be deleted now?
+ I note that you have 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.
 
 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
- 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.
+_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 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?
+ 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.
 
 Template: shared/kernel-image/really-run-bootloader
 Type: boolean
 Default: true
-Description: Run the default bootloader?
+_Description: Run the default bootloader?
  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, 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.
 
 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.
- 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.
+_Description:  Error running the boot loader in test mode.
+ An error occurred while running the boot loader ${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.
 
 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}.
- 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.
+_Description:  Error running the boot loader in test mode.
+ An error occurred while running the boot loader ${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.
 
 Template: =ST-image-=V/prerm/removing-running-kernel-=V
 Type: boolean
 Default: true
-Description:  Do you want to abort removal now?
- 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
+_Description:  Do you want to abort removal now?
+ 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.
  .
- 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.
+ 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.
 
 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:  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}).
  .
- I repeat: you shall have to make changes to your boot loader setup
- and will have to re-run ${loader}.
+ I repeat: you shall have to make changes to your boot loader setup and
+ will have to re-run ${loader}.
