summaryrefslogtreecommitdiff
path: root/po/pot/post-install.pot
diff options
context:
space:
mode:
Diffstat (limited to 'po/pot/post-install.pot')
-rw-r--r--po/pot/post-install.pot4
1 files changed, 2 insertions, 2 deletions
diff --git a/po/pot/post-install.pot b/po/pot/post-install.pot
index 2dc1bcc82..120fa6b0e 100644
--- a/po/pot/post-install.pot
+++ b/po/pot/post-install.pot
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2006-08-07 22:39+0000\n"
+"POT-Creation-Date: 2006-08-16 18:10+0000\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"
@@ -284,7 +284,7 @@ msgstr ""
#. Tag: para
#: post-install.xml:419
#, no-c-format
-msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <phrase condition=\"classic-kpkg\"> <userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> <phrase condition=\"common-kpkg\"> <userinput>dpkg -i ../linux-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"x86\"> such as <quote>i586</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, <phrase condition=\"classic-kpkg\">e.g., if you have PCMCIA,</phrase> you'll need to install that package as well."
+msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <phrase condition=\"classic-kpkg\"> <userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> <phrase condition=\"common-kpkg\"> <userinput>dpkg -i ../linux-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, <phrase condition=\"classic-kpkg\">e.g., if you have PCMCIA,</phrase> you'll need to install that package as well."
msgstr ""
#. Tag: para