diff options
Diffstat (limited to 'doc/gettext/ru/kernel-upgrade.xml.po')
| -rw-r--r-- | doc/gettext/ru/kernel-upgrade.xml.po | 569 |
1 files changed, 569 insertions, 0 deletions
diff --git a/doc/gettext/ru/kernel-upgrade.xml.po b/doc/gettext/ru/kernel-upgrade.xml.po new file mode 100644 index 0000000..e0a727d --- /dev/null +++ b/doc/gettext/ru/kernel-upgrade.xml.po @@ -0,0 +1,569 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2010-10-21 23:56+0600\n" +"PO-Revision-Date: 2010-10-21 23:46+0600\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: ru\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" +"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(guide:link):5 +msgid "/doc/en/kernel-upgrade.xml" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):6 +msgid "Gentoo Linux Kernel Upgrade Guide" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(author:title):7 +msgid "Author" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(mail:link):8 +msgid "dsd@gentoo.org" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(mail):8 +msgid "Daniel Drake" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(abstract):11 +msgid "" +"This document describes the process of upgrading your kernel from one " +"release to another." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(version):20 +msgid "0.6" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(date):21 +msgid "2007-06-22" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):24 +msgid "Introduction" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):28 +msgid "" +"The kernel is one of the few package classes in portage that requires some " +"manual intervention to complete the upgrade. Portage will download and " +"install the kernel source for you, but then it is up to you to step in and " +"compile the new kernel before any changes will take effect." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):35 +msgid "" +"Although this guide is targeted at users upgrading from one kernel release " +"to another, it will also be useful for users migrating from one kernel " +"package to another." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):41 +msgid "" +"<c>gentoo-sources</c> is used as an example in this document, however, the " +"instructions here also apply to the other packages present in our tree." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):51 +msgid "Why upgrade the kernel?" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):55 +msgid "" +"Generally, upgrading from one minor kernel release to the next won't bring " +"any major differences. There are several reasons to upgrade the kernel. One " +"is to take advantage of a specific new feature or driver; another is to be " +"protected against a security vulnerability, or just to maintain an up-to-" +"date and healthy system." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):63 +msgid "" +"Even if you choose not to update to every new kernel revision, it is " +"recommended that you at least upgrade from time to time. It is strongly " +"recommended that you immediately upgrade to a new kernel if that new release " +"solves a security problem." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):75 +msgid "Obtaining the newer sources through Portage" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):79 +msgid "" +"You upgrade the kernel sources like you would upgrade any other package - " +"using the <c>emerge</c> utility. It will probably be the case that you want " +"to upgrade your kernel when you see the upgrade appearing on your world " +"updates list. For example:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):86 +msgid "New kernel sources appearing on update list" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):86 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -Dup world</i>\n" +"Calculating dependencies ...done!\n" +"[ebuild NS ] sys-kernel/gentoo-sources-2.6.9-r2 [2.6.8-r5]\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(note):92 +msgid "" +"The \"NS\" label in the above output means that the new kernel will be " +"installed in a New Slot, i.e. the sources of your old kernel will be kept " +"around, until you manually remove them." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):98 +msgid "You can then go ahead and install the update, e.g.:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):102 +msgid "Upgrading your kernel sources" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):102 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -u gentoo-sources</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):106 +msgid "" +"The kernel sources will then be installed into a subdirectory of <path>/usr/" +"src</path>. In the above example, the new kernel sources will be installed " +"at <path>/usr/src/linux-2.6.9-gentoo-r2</path>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):117 +msgid "Updating the /usr/src/linux symbolic link" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):121 +msgid "" +"Gentoo requires that the <path>/usr/src/linux</path> symbolic link points to " +"the sources of the kernel you are running." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):126 +msgid "" +"Portage can update the symlink automatically when you emerge new kernel " +"sources. All you have to do is add the <c>symlink</c> flag to the USE " +"variable in <path>/etc/make.conf</path>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):132 +msgid "Example of USE variable in /etc/make.conf" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):132 +#, no-wrap +msgid "" +"\n" +"<comment>(Add the symlink keyword)</comment>\n" +"USE=\"<i>symlink</i> x86 3dnow 3dnowex X aac aalib adns alsa apache2\"\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):137 +msgid "" +"Alternatively, you could use <c>app-admin/eselect</c> to modify the symlink." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):141 +msgid "Using eselect to symlink" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):141 +#, no-wrap +msgid "" +"\n" +"<comment>(Install eselect if you don't have it)</comment>\n" +"# <i>emerge eselect</i>\n" +"<comment>(See the list of available kernels)</comment>\n" +"# <i>eselect kernel list</i>\n" +"Available kernel symlink targets:\n" +" [1] linux-2.6.9-gentoo-r1\n" +" [2] linux-2.6.9-gentoo-r2\n" +"<comment>(Select the correct kernel)</comment>\n" +"# <i>eselect kernel set 1</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):153 +msgid "" +"If you really want to do it yourself, the following example shows you how to " +"make the link point to <path>linux-2.6.9-gentoo-r2</path>:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):158 +msgid "Updating the /usr/src/linux softlink manually" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):158 +#, no-wrap +msgid "" +"\n" +"# <i>cd /usr/src</i>\n" +"# <i>ln -sfn linux-2.6.9-gentoo-r2 linux</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):168 +msgid "Configuring, compiling and installing the new kernel" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):172 +msgid "" +"For either of these options, you should refer to the instructions given in " +"the <uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri> relating to " +"<e>Configuring the Kernel</e> and <e>Configuring the Bootloader</e>. Below " +"is an outline of the required actions:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):182 +msgid "Option 1: Automatic kernel setup with Genkernel" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):185 +msgid "" +"If you are a genkernel user, you just need to repeat the stages you went " +"through when installing your kernel for the first time." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):190 +msgid "Simply run genkernel in the normal way:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):194 +msgid "Invoking genkernel" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):194 +#, no-wrap +msgid "" +"\n" +"# <i>genkernel all</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):198 +msgid "" +"You can also use extra parameters for other genkernel functionality. For " +"example, if you wish to configure some extra kernel options using " +"<c>menuconfig</c> and you wish genkernel to automatically update your grub " +"boot loader configuration, then invoke genkernel as follows:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):205 +msgid "Invoking genkernel with some common arguments" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):205 +#, no-wrap +msgid "" +"\n" +"# <i>genkernel --menuconfig --bootloader=grub all</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):209 +msgid "" +"For more info, follow the <uri link=\"/doc/en/genkernel.xml\">Gentoo Linux " +"Genkernel Guide</uri>, or refer to the <uri link=\"/doc/en/handbook/" +"\">Gentoo Handbook</uri>. Many of the options can be set in the " +"configuration file for <c>genkernel</c>, <path>/etc/genkernel.conf</path>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):219 +msgid "Option 2: Manual configuration" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):222 +msgid "To begin, open the <c>menuconfig</c> utility in the kernel source tree:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):226 +msgid "Invoking menuconfig" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):226 +#, no-wrap +msgid "" +"\n" +"# <i>cd /usr/src/linux</i>\n" +"# <i>make menuconfig</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):231 +msgid "" +"Select the options required for your hardware and operating environment. For " +"additional information on kernel configuration, refer to the chapter " +"entitled <e>Configuring the Kernel</e> of the <uri link=\"/doc/en/handbook/" +"index.xml\">Gentoo Handbook</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):238 +msgid "" +"Next, compile your kernel and copy it over to your boot partition. Again, " +"follow the <uri link=\"/doc/en/handbook/index.xml\">Gentoo Handbook</uri> " +"instructions outlined in the chapter on <e>Configuring the Bootloader</e>. " +"If <path>/boot</path> is a separate partition, ensure it is mounted before " +"copying the compiled kernel to this directory! Failing to do so would keep " +"you from booting the system with your new kernel." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):247 +msgid "Compiling and installing the new kernel" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):247 +#, no-wrap +msgid "" +"\n" +"# <i>make && make modules_install</i>\n" +"# <i>mount /boot</i>\n" +"# <i>cp arch/i386/boot/bzImage /boot/bzImage-2.6.9-gentoo-r2</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):253 +msgid "" +"Finally, you should update your boot loader configuration, adding an entry " +"for the new kernel (don't delete the old one just yet!) and unmount the " +"<path>/boot</path> partition. Again, refer to the <uri link=\"/doc/en/" +"handbook/index.xml\">Gentoo Handbook</uri> for detailed instructions on this " +"procedure." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):266 +msgid "Reinstalling external modules" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):270 +msgid "" +"If you use any kernel modules that are not included in the kernel source " +"tree but are provided elsewhere in Portage (e.g. ALSA drivers and NVIDIA or " +"ATI graphics drivers), then you must reinstall these after upgrading the " +"kernel. This is as simple as re-merging the packages involved. For more " +"information, refer to the chapter on <e>Configuring the Kernel</e> in the " +"<uri link=\"/doc/en/handbook/\">Gentoo Handbook</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):279 +msgid "" +"We provide you with an easy tool (<c>sys-kernel/module-rebuild</c>) which " +"rebuilds all the kernel modules you have installed using separate ebuilds " +"for the kernel at <path>/usr/src/linux</path>. Its use is straightforward. " +"After emerging it, simply run <c>module-rebuild populate</c> to populate the " +"database with a list of packages that will need to be rebuilt after " +"upgrading the kernel. Once you have finished upgrading or recompiling your " +"kernel, run <c>module-rebuild rebuild</c> to rebuild the drivers for your " +"new kernel." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):289 +msgid "" +"For more information, run <c>module-rebuild</c> without any options to see a " +"list of commands that can be passed to the utility." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):299 +msgid "Rebooting into the new kernel" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):303 +msgid "" +"Next, close all applications and reboot your system. If you followed the " +"above instructions correctly, the boot loader menu should include an entry " +"for the new kernel. Select the new kernel and let the system boot." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):309 +msgid "" +"Hopefully, your system successfully boots with the new kernel, and you can " +"log in to resume whatever you were doing. If this is the case, then the " +"upgrade is complete." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):315 +msgid "" +"If you made a mistake and the system fails to boot with the new kernel, " +"reboot the system and select the entry from the boot loader that corresponds " +"to the last known working kernel. You can then restart from the <uri link=" +"\"#install\"> Configuring, compiling, and installing the new kernel</uri> " +"stage -- making the appropriate changes to correct your mistake. In some " +"cases, you might not even need to reboot to do this (e.g. you missed a " +"driver for an audio device, Ethernet adapter, etc.)" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):330 +msgid "Running multiple kernels" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):334 +msgid "" +"You may have noticed, that when installing the sources for your newer " +"kernel, the sources for your existing kernel were not removed. This is by " +"design -- it allows you to easily switch between running different kernels." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):340 +msgid "" +"Switching between multiple kernels is as simple as leaving the kernel " +"sources under <path>/usr/src/</path> and leaving the <path>bzImage</path> " +"binaries on your <path>/boot</path> partition (referenced by entries in your " +"boot loader configuration). Every time you boot up, you will be presented " +"with a choice of which kernel to boot into." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):353 +msgid "Removing older kernels" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):357 +msgid "" +"Continuing on from the last section, you may be happy with your new kernel " +"and not have any need to keep older kernel versions around. To easily remove " +"all sources for a particular kernel except for the newest one, you can take " +"advantage of the <e>prune</e> option available through <c>emerge</c>. " +"Continuing the example using <c>gentoo-sources</c>:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):365 +msgid "Pruning old versions" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):365 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -P gentoo-sources</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):369 +msgid "" +"In most cases, temporary files used during compilation will still remain " +"under the appropriate source directory under <path>/usr/src</path>. It is " +"safe to remove these using <c>rm</c>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):375 +msgid "" +"You can also safely delete any modules that were used by this kernel. This " +"can be done by removing the appropriate directories under <path>/lib/modules/" +"</path> that relate to the kernel versions you are removing. Be careful not " +"to delete modules belonging to kernels that you still use!" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):382 +msgid "" +"Finally, you can mount your <path>/boot</path> partition and remove the " +"<path>bzImage</path> file(s) for the kernel(s) you are pruning. You should " +"also edit your boot loader configuration so that it no longer references " +"such kernel(s)." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):394 +msgid "Advanced: Using your old kernel .config to configure a new one" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):398 +msgid "" +"It is sometimes possible to save time by re-using the configuration file " +"from your old kernel when configuring the new one. Note that this is " +"generally unsafe -- too many changes between every kernel release for this " +"to be a reliable upgrade path." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):405 +msgid "" +"The only situation where this is appropriate is when upgrading from one " +"Gentoo kernel revision to another. For example, the changes made between " +"<c>gentoo-sources-2.6.9-r1</c> and <c>gentoo-sources-2.6.9-r2</c> will be " +"very small, so it is usually OK to use the following method. However, it is " +"not appropriate to use it in the example used throughout this document: " +"upgrading from 2.6.8 to 2.6.9. Too many changes between the official " +"releases, and the method described below does not display enough context to " +"the user, often resulting in the user running into problems because they " +"disabled options that they really didn't want to." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):417 +msgid "" +"To reuse your old <path>.config</path>, you simply need to copy it over and " +"then run <c>make oldconfig</c>. In the following example, we take the " +"configuration from <c>gentoo-sources-2.6.9-r1</c> and import it into " +"<c>gentoo-sources-2.6.9-r2</c>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):424 +msgid "Reusing your old config" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):424 +#, no-wrap +msgid "" +"\n" +"# <i>cd /usr/src/linux-2.6.9-gentoo-r2</i>\n" +"# <i>cp ../linux-2.6.9-gentoo-r1/.config .</i>\n" +"# <i>make oldconfig</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre:caption):430 +msgid "Reusing your old config with genkernel" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(pre):430 +#, no-wrap +msgid "" +"\n" +"# <i>cd /etc/kernels</i>\n" +"# <i>cp kernel-config-x86-2.6.9-gentoo-r1 kernel-config-x86-2.6.9-gentoo-r2</i>\n" +"# <i>genkernel all</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):436 +msgid "" +"At this point, you may be asked to produce answers for configuration options " +"which have changed between the two versions. Once you have done that, you " +"can compile and install your kernel as normal, without having to go through " +"the <c>menuconfig</c> configuration process." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):443 +msgid "" +"A much safer upgrading method is to copy your config as previously shown, " +"and then simply run <c>make menuconfig</c>. This avoids the problems of " +"<c>make oldconfig</c> mentioned previously, as <c>make menuconfig</c> will " +"load up your previous configuration as much as possible into the menu. Now " +"all you have to do is go through each option and look for new sections, " +"removals, and so on. By using <c>menuconfig</c>, you gain context for all " +"the new changes, and can easily view the new choices and review help screens " +"much easier. You can even use this for upgrades such as 2.6.8 to 2.6.9; just " +"make sure you read through the options carefully. Once you've finished, " +"compile and install your kernel as normal." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(title):461 +msgid "Problems after a kernel upgrade?" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(p):465 +msgid "" +"With the rapid development of the Linux kernel, it is inevitable that some " +"changes made from one kernel release to another may cause some problems. If " +"you have any issues with the latest versions of <uri link=\"/doc/en/gentoo-" +"kernel.xml#doc_chap2\"> Gentoo-supported kernels</uri> then please do report " +"the issues to us." +msgstr "" + +#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL +#: ../../gentoo/xml/htdocs/doc/en//kernel-upgrade.xml(None):0 +msgid "translator-credits" +msgstr "" |