diff options
| author |   Azamat H. Hackimov <azamat.hackimov@gmail.com> | 2011-10-28 22:41:49 +0600 |
|---|---|---|
| committer | Azamat H. Hackimov <azamat.hackimov@gmail.com> | 2011-10-28 22:41:49 +0600 |
| commit | 1c2c93e6e853d1b06e64f8f1733830c11235150f (patch) | |
| tree | 2872d991405751f18bb77f317cef15999c3aedcb /doc | |
| parent | l10n: Updated Russian (ru) translation to 100% (diff) | |
| download | gentoo-doc-translations-1c2c93e6e853d1b06e64f8f1733830c11235150f.tar.gz gentoo-doc-translations-1c2c93e6e853d1b06e64f8f1733830c11235150f.tar.bz2 gentoo-doc-translations-1c2c93e6e853d1b06e64f8f1733830c11235150f.zip | |
Sync with g.o
Diffstat (limited to 'doc')
21 files changed, 3741 insertions, 6814 deletions
diff --git a/doc/gettext/el/faq.xml.po b/doc/gettext/el/faq.xml.po index ff55a5b..d287787 100644 --- a/doc/gettext/el/faq.xml.po +++ b/doc/gettext/el/faq.xml.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-18 15:18+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-10-21 23:56+0600\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -118,11 +118,11 @@ msgid "" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(version):50 -msgid "6" +msgid "7" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(date):51 -msgid "2011-09-11" +msgid "2011-10-13" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):54 @@ -291,20 +291,28 @@ msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):205 msgid "" "In fact, there is no difference between the various releases after they have " -"been installed. Gentoo 1.4 and later are <c>glibc-2.3.x</c> based. As such, " -"running <c>emerge --sync && emerge -uDN world</c> will bring your " -"entire system up to speed with the \"latest Gentoo\". The differences " -"between individual releases lie in the installation medium and pre-compiled " -"packages. See the <uri link=\"/doc/en/gentoo-upgrading.xml\">Gentoo " -"Upgrading Guide</uri> for more information about profiles and their role in " -"upgrading." +"been installed. Gentoo 1.4 and later are <c>glibc-2.3.x</c> (or higher) " +"based. As such, running <c>emerge --sync && emerge -uDN world</c> " +"will bring your entire system up to speed with the \"latest Gentoo\". The " +"differences between individual releases lie in the installation medium and " +"pre-compiled packages. See the <uri link=\"/doc/en/gentoo-upgrading.xml" +"\">Gentoo Upgrading Guide</uri> for more information about profiles and " +"their role in upgrading." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):218 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):215 +msgid "" +"Also note that the <c>emerge -uDN world</c> command updates the packages you " +"have installed as well as its dependencies, but not the build-time " +"dependencies (packages needed during builds but not when the software is " +"installed). To update those as well, add the <c>--with-bdeps=y</c> option." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):225 msgid "My kernel doesn't boot, what should I do now?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):221 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):228 msgid "" "You don't need to redo every step of the installation, but investigating the " "kernel and all associated steps is necessary. Suppose you have installed " @@ -312,11 +320,11 @@ msgid "" "<path>/dev/hda2</path> being the swap space:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):228 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):235 msgid "Reconfiguring the kernel" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):228 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):235 #, no-wrap msgid "" "\n" @@ -344,28 +352,28 @@ msgid "" "# <i>reboot</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):253 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):260 msgid "" "If, on the other hand, the problem lies with your bootloader configuration, " "follow the same steps, but instead of configuring/compiling your kernel, you " "should reconfigure your bootloader (recompilation isn't necessary)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):262 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):269 msgid "My proxy requires authentication, what do I have to do?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):265 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):272 msgid "" "To have Portage automatically use this scheme, define it in <path>/etc/make." "conf</path>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):270 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):277 msgid "/etc/make.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):270 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):277 #, no-wrap msgid "" "\n" @@ -374,23 +382,23 @@ msgid "" "RSYNC_PROXY=\"rsync://username:password@yourproxybox.server:portnumber\"\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):279 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):286 msgid "How do I burn an ISO file?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):282 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):289 msgid "" "You need to burn the file in raw mode. This means that you should <e>not</e> " "just place the file on the CD, but interpret the file as an entire CD." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):287 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):294 msgid "" "There are lots of CD burning tools available; covering them all would be a " "Sisyphean problem. However, describing a few popular tools never hurts:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):293 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):300 msgid "" "With EasyCD Creator you select <c>File</c>, <c>Record CD from CD image</c>. " "Then you change the <c>Files of type</c> to <c>ISO image file</c>. Then " @@ -398,7 +406,7 @@ msgid "" "recording</c> the ISO image will be burned correctly onto the CD-R." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):299 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):306 msgid "" "With Nero Burning ROM, cancel the wizard which automatically pops up and " "select <c>Burn Image</c> from the <c>File</c> menu. Select the image you " @@ -406,21 +414,21 @@ msgid "" "your brand new CD being burnt." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):305 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):312 msgid "" "With cdrecord, you simply type <c>cdrecord dev=/dev/hdc</c> (replace <path>/" "dev/hdc</path> with your CD-RW drive's device path) followed by the path to " "the ISO file :)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):310 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):317 msgid "" "With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn CD Image</c>. Then " "you can locate your ISO file within the 'Image to Burn' area. Finally click " "<c>Start</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):315 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):322 msgid "" "With Mac OS X Panther, launch <c>Disk Utility</c> from <path>Applications/" "Utilities</path>, select <c>Open</c> from the <c>Images</c> menu, select the " @@ -428,18 +436,18 @@ msgid "" "<c>Images</c> menu." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):321 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):328 msgid "" "With Mac OS X Jaguar, launch <c>Disk Copy</c> from <path>Applications/" "Utilities</path>, select <c>Burn Image</c> from the <c>File</c> menu, select " "the ISO and click the <c>Burn</c> button." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):332 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):339 msgid "What CD/stage should I use for my CPU?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):335 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):342 msgid "" "First you need to find out what CPU you use. Suppose it's a Pentium-M. Then " "you need to find out what CPU it is, instruction-wise, compatible with. You " @@ -447,14 +455,14 @@ msgid "" "\"http://www.google.com\">Google</uri> is at least as efficient :-)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):342 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):349 msgid "" "If you are uncertain, take a \"lower\" CD/stage file, for instance a i686 or " "even generic x86 (or the equivalent in your arch). This will ensure that " "your system will work, but may not be as fast as further optimizations." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):348 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):355 msgid "" "Please note that many more options exist than those for which Gentoo builds " "binary stages. Please see the <uri link=\"http://gcc.gnu.org/onlinedocs/" @@ -462,11 +470,11 @@ msgid "" "\">gcc guide</uri> for setting <c>-march</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):358 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):365 msgid "I can't get online after rebooting. What is wrong?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):361 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):368 msgid "" "First you need to check if your network card is discovered properly by the " "kernel. Run <c>ifconfig -a</c> and look for eth0 or wlan0 (in case of " @@ -476,13 +484,13 @@ msgid "" "modules</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):370 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):377 msgid "" "If you have forgotten to include support for your network card in your " "kernel, you will need to reconfigure your kernel." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):375 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):382 msgid "" "If your network card is found by your kernel, but you have set your " "networking configuration to use DHCP, you might have forgotten to " @@ -490,19 +498,19 @@ msgid "" "to install <c>dhcpcd</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):382 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):389 msgid "" "Information on how to rescue your system using the installation CD is <uri " "link=\"#bootrescue\">available</uri> as well." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):390 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):397 msgid "" "I want to boot Windows from grub or lilo but it shows only black screen. " "What should I do?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):396 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):403 msgid "" "This is a known problem. Windows refuses to boot when it isn't installed on " "the first hard drive and shows a black/blank screen. To handle this, you " @@ -513,11 +521,11 @@ msgid "" "config as needed." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):405 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):412 msgid "Example dual boot entry for Windows in grub.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):405 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):412 #, no-wrap msgid "" "\n" @@ -528,11 +536,11 @@ msgid "" " chainloader +1\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):413 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):420 msgid "Example dual boot entry for Windows in lilo.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):413 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):420 #, no-wrap msgid "" "\n" @@ -545,7 +553,7 @@ msgid "" " to = 0x80\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):423 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):430 msgid "" "This will make Windows believe it is installed on the first hard drive and " "boot without problems. More information can be found in the <uri link=" @@ -553,11 +561,11 @@ msgid "" "lilo.conf</c>, depending on the boot loader you're using." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):433 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):440 msgid "How do I Install Gentoo Using a Stage1 or Stage2 Tarball?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):436 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):443 msgid "" "The Gentoo Handbook only describes a Gentoo installation using a stage3 " "tarball. However, Gentoo still provides stage1 and stage2 tarballs. This is " @@ -567,7 +575,7 @@ msgid "" "Internet connection." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):444 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):451 msgid "" "Bootstrapping means building the toolchain (the C library and compiler) for " "your system after which you install all core system packages. To bootstrap " @@ -576,11 +584,11 @@ msgid "" "to suit your needs and then run it:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):452 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):459 msgid "Bootstrapping the system" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):452 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):459 #, no-wrap msgid "" "\n" @@ -590,38 +598,38 @@ msgid "" "# <i>./bootstrap.sh</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):459 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):466 msgid "" "Next, rebuild all core system packages with the newly built toolchain. We " "need to rebuild them since the stage3 tarball already offers them:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):464 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):471 msgid "Rebuilding the core system packages" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):464 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):471 #, no-wrap msgid "" "\n" "# <i>emerge -e system</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):468 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):475 msgid "" "Now you can continue with <e>Configuring the Kernel</e>. You can not use the " "prebuilt GRP packages anymore though." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):478 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):485 msgid "Package Management" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):480 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):487 msgid "In what form are the packages stored?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):483 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):490 msgid "" "Packages aren't \"stored\" per se. Instead, Gentoo provides a set of scripts " "which can resolve dependencies, fetch source code, and compile a version of " @@ -631,7 +639,7 @@ msgid "" "contents of an ebuild script in detail." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):492 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):499 msgid "" "For full ISO releases, we create a full suite of binary packages in an " "enhanced <c>.tbz2</c> format, which is <c>.tar.bz2</c> compatible with meta-" @@ -640,18 +648,18 @@ msgid "" "efficiently." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):499 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):506 msgid "" "It is possible to create RPMs (Redhat package manager files) using Gentoo's " "Portage, but it is not currently possible to use already existing RPMs to " "install packages." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):508 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):515 msgid "I want to perform the ./configure step myself. Can I?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):511 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):518 msgid "" "Yes, but it is not trivial, nor is it recommended. Since the method to do " "this requires a good understanding of Portage internals and commands, it is " @@ -662,22 +670,22 @@ msgid "" "HOWTO</uri> for more information." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):524 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):531 msgid "How do I use emerge from behind a firewall?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):527 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):534 msgid "" "See the questions on <uri link=\"#proxy\">proxies</uri>, <uri link=\"#norsync" "\">rsync</uri>, and <uri link=\"#manualdownload\">downloading source files " "manually</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):536 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):543 msgid "What if rsync doesn't work for me?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):539 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):546 msgid "" "If you're behind a firewall that doesn't permit rsync traffic, then you can " "use <c>emerge-webrsync</c> which will fetch and install a Portage snapshot " @@ -686,13 +694,13 @@ msgid "" "Portage snapshots via a proxy." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):550 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):557 msgid "" "I have only slow modem connection at home. Can I download sources somewhere " "else and add them to my system?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):556 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):563 msgid "" "Definitely. You can run <c>emerge --pretend package</c> to see what programs " "are going to be installed. To find out the sources for those packages and " @@ -702,13 +710,13 @@ msgid "" "c>. Be warned, however, that this is a tedious process." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):568 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):575 msgid "" "Source tarballs are collecting in /usr/portage/distfiles/. Is it safe to " "delete these files?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):574 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):581 msgid "" "Deleting these files will have no negative impact on day-to-day performance. " "However, it might be wise to keep the most recent version of the files; " @@ -717,7 +725,7 @@ msgid "" "software it will be necessary to download them from the internet again." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):582 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):589 msgid "" "You can use the <c>eclean</c> script from <c>app-portage/gentoolkit</c> to " "manage the contents of <path>/usr/portage/distfiles/</path> and a few other " @@ -725,13 +733,13 @@ msgid "" "well as the <uri link=\"/doc/en/gentoolkit.xml\">Gentoolkit Guide</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):592 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):599 msgid "" "What's in /var/tmp/portage? Is it safe to delete the files and directories " "in /var/tmp/portage?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):598 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):605 msgid "" "During compilation, Gentoo saves the sources of the package in <path>/var/" "tmp/portage</path>. These files and folder are usually deleted upon a " @@ -740,15 +748,15 @@ msgid "" "always <c>pgrep emerge</c> before cleaning out this directory." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):611 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):618 msgid "Usage" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):613 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):620 msgid "How do I set up an International Keyboard Layout?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):616 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):623 msgid "" "Edit the <c>KEYMAP</c> variable in <path>/etc/conf.d/keymaps</path>. To have " "console working correctly with extended characters in your keymap you might " @@ -759,11 +767,11 @@ msgid "" "the keymaps and consolefont scripts:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):626 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):633 msgid "Restarting keymaps" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):626 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):633 #, no-wrap msgid "" "\n" @@ -771,98 +779,98 @@ msgid "" "# <i>/etc/init.d/consolefont restart</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):634 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):641 msgid "DNS name resolution works for root only" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):637 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):644 msgid "" "<path>/etc/resolv.conf</path> has the wrong permissions; <c>chmod</c> it as " "follows:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):642 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):649 msgid "Changing permissions on /etc/resolv.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):642 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):649 #, no-wrap msgid "" "\n" "# <i>chmod 0644 /etc/resolv.conf</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):649 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):656 msgid "Why can't my user use their own crontab?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):652 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):659 msgid "You need to add that user to the <c>cron</c> group." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):659 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):666 msgid "How do I get numlock to start on boot?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):662 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):669 msgid "" "If you work in command line, you only need to <c>rc-update add numlock " "default &&/etc/init.d/numlock start</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):667 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):674 msgid "" "Each GUI provides different tools for this sort of thing; please check the " "help section or online manuals for assistance." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):675 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):682 msgid "How do I have my terminal cleared when I log out?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):678 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):685 msgid "" "To have your terminal cleared, add <c>clear</c> to your <path>~/." "bash_logout</path> script:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):683 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):690 msgid "Clearing the terminal during logout" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):683 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):690 #, no-wrap msgid "" "\n" "$ <i>echo clear >> ~/.bash_logout</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):687 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):694 msgid "" "If you want this to happen automatically when you add a new user, do the " "same for the <path>/etc/skel/.bash_logout</path>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):692 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):699 msgid "Making new users their terminal clear on logout" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):692 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):699 #, no-wrap msgid "" "\n" "# <i>echo clear >> /etc/skel/.bash_logout</i>" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):700 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):707 msgid "Maintenance" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):702 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):709 msgid "ReiserFS and filesystem corruption issues -- how to fix them, etc" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):705 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):712 msgid "" "If your ReiserFS partition is corrupt, try booting the Gentoo Install CD and " "run <c>reiserfsck --rebuild-tree</c> on the corrupted filesystem. This " @@ -870,26 +878,26 @@ msgid "" "files or directories due to the corruption." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):717 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):724 msgid "Development" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):719 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):726 msgid "Where can I report bugs?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):722 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):729 msgid "" "Use our <uri link=\"https://bugs.gentoo.org\">Bugzilla</uri>. If you are " "unsure if your problem is an actual bug, you can visit <uri link=\"irc://irc." "gentoo.org/gentoo\">#gentoo</uri> on IRC." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):731 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):738 msgid "How often are new releases made?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):734 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):741 msgid "" "Gentoo's packages are usually updated shortly after the main authors release " "new code. As for when Gentoo itself makes new stage/profile/ISO releases, " @@ -899,26 +907,26 @@ msgid "" "\"#upgrade\">upgrading</uri> for more information." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):746 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):753 msgid "My speaker beeps like crazy. How do I disable console beeps?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):751 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):758 msgid "Console beeps can be turned off using setterm, like this:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):755 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):762 msgid "Using setterm" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):755 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):762 #, no-wrap msgid "" "\n" "# <i>setterm -blength 0</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):759 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):766 msgid "" "If you would like to turn off the console beeps on boot, you need to put " "this command in <path>/etc/conf.d/local.start</path>. However, this only " @@ -926,42 +934,42 @@ msgid "" "terminals, pipe the command output to the target terminal, like this:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):765 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):772 msgid "Using setterm (bis)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):765 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):772 #, no-wrap msgid "" "\n" "# <i>setterm -blength 0 >/dev/vc/1</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):769 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):776 msgid "" "You need to replace /dev/vc/1 with the terminal you would like to disable " "console beeps for." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):779 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):786 msgid "Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):781 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):788 msgid "Where can I find more information about Gentoo Linux?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):784 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):791 msgid "" "The official Gentoo documentation can be found at <uri>http://www.gentoo.org/" "doc/en/</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):792 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):799 msgid "Can I buy a CD of Gentoo Linux?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):795 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):802 msgid "" "Install CDs for all supported architectures are available on our <uri link=" "\"http://www.cafepress.com/officialgentoo/\">Gentoo Store</uri>. When you " @@ -969,17 +977,17 @@ msgid "" "please consider buying from our store if possible." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):802 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):809 msgid "" "You can also find fresh CDs from various resellers listed on our <uri link=" "\"/main/en/where.xml\">Get Gentoo!</uri> page." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):810 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):817 msgid "This FAQ hasn't answered my question. What do I do now?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):813 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):820 msgid "" "A good first step is to browse through the relevant <uri link=\"/doc/en/" "index.xml\">documentation</uri>, failing that, the various Gentoo Linux " diff --git a/doc/gettext/el/gcc-upgrading-upto-4.1.xml.po b/doc/gettext/el/gcc-upgrading-upto-4.1.xml.po new file mode 100644 index 0000000..7ea7e42 --- /dev/null +++ b/doc/gettext/el/gcc-upgrading-upto-4.1.xml.po @@ -0,0 +1,633 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" +"PO-Revision-Date: 2011-10-28 22:38+0600\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: el\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):7 +msgid "Gentoo GCC Upgrade Guide for GCC Up To 4.1" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):9 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):12 +msgid "Author" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):10 +msgid "amne@gentoo.org" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail):10 +msgid "Wernfried Haas" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):13 +msgid "jkt@gentoo.org" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail):13 +msgid "Jan Kundrát" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):15 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):18 +msgid "Editor" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):16 +msgid "halcy0n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):19 +msgid "nightmorph" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(abstract):22 +msgid "This document will guide the user through the process of upgrading GCC." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(version):30 +msgid "23" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(date):31 +msgid "2008-07-19" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):34 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):80 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):167 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):333 +msgid "Introduction" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):36 +msgid "GCC Upgrading" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):39 +msgid "" +"Why should you upgrade? Well, GCC is quite similar to any other package on " +"your system, just a bit more critical. You should upgrade GCC whenever a new " +"version fixes some bug that annoys you, new functionality you need is " +"introduced, or if you want to keep your system up-to-date. If none of the " +"previous cases apply to you, you can safely postpone upgrade as long as your " +"GCC version is supported by Gentoo developers." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):48 +msgid "" +"If you install a new major version of GCC (such as 3.3.6 to 3.4.5), the " +"system will not switch over to use it automatically. You'll have to " +"explicitly request the change because the migration process might require " +"some additional steps. If you decide not to switch, Portage will continue to " +"use older version of your compiler until you change your mind, or remove the " +"old compiler from the system. Non-major gcc upgrades are switched " +"automatically for you (such as 3.4.5 to 3.4.6)." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):58 +msgid "" +"This guide will document the necessary steps required to perform a seamless " +"upgrade of the compiler used by your Gentoo box. A specific section is " +"dedicated to the <uri link=\"#upgrade-3.3-to-3.4\">upgrade from GCC 3.3 to " +"3.4</uri> and issues with <c>libstdc++</c>. A second specific section is for " +"users <uri link=\"#first-install\">first installing</uri> Gentoo using a " +"stage3 tarball, after a new GCC major/minor version has been released." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(warn):67 +msgid "" +"It should be noted that upgrading from GCC-3.4 (or 3.3) to GCC-4.1 or " +"greater still requires you to follow the <uri link=\"#upgrade-general" +"\">general upgrading instructions</uri>, as GCC-3.4 and GCC-4.1 use slightly " +"different ABIs." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):78 +msgid "General Upgrade Instructions" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):83 +msgid "" +"If you're looking for instructions specific to upgrades from GCC-3.3 to " +"GCC-3.4, please consult the <uri link=\"#upgrade-3.3-to-3.4\">dedicated " +"section</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):89 +msgid "" +"If you're looking for instructions specific to upgrades in GCC for new " +"installs, please consult the <uri link=\"#first-install\">dedicated section</" +"uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):95 +msgid "" +"Generally speaking, upgrades to <e>bug fix releases</e>, like from 3.3.5 to " +"3.3.6, should be quite safe -- just emerge new version, switch your system " +"to use it and rebuild the only affected package, <c>libtool</c>. However, " +"some GCC upgrades break binary compatibility; in such cases a rebuild of the " +"affected packages (or even whole toolchain and system) might be required." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):103 +msgid "" +"When we spoke about the need to switch your compiler to the newer version by " +"hand, we said it won't happen automatically. However, there is one exception " +"-- upgrades to bug fix releases, like from 3.3.5 to 3.3.6 in case you don't " +"use the \"multislot\" feature allowing them to coexist on one system. " +"Multislot is disabled by default as the majority of users won't benefit from " +"it." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):111 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):278 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):366 +msgid "Upgrading GCC" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):111 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -uav gcc</i>\n" +"\n" +"<comment>(Please substitute \"i686-pc-linux-gnu-4.1.1\" with the GCC\n" +"version and CHOST settings you've upgraded to:)</comment>\n" +"# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>\n" +"# <i>env-update && source /etc/profile</i>\n" +"\n" +"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this\n" +"example) you will have to run fix_libtool_files.sh manually</comment>\n" +"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n" +"<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n" +"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.4.6</i>\n" +"\n" +"<comment>(Rebuilding libtool)</comment>\n" +"# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):129 +msgid "" +"To be completely safe that your system is in a sane state, you <e>must</e> " +"rebuild the toolchain and then world to make use of the new compiler." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):134 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):433 +msgid "Rebuilding system" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):134 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -eav system</i>\n" +"# <i>emerge -eav world</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):139 +msgid "" +"It is safe to remove the older GCC version at this time. If you feel the " +"need, please issue the following command (as usual, substitute <c>=sys-devel/" +"gcc-3.4*</c> with the version you want to uninstall):" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):145 +msgid "Removing older GCC version" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):145 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -aC =sys-devel/gcc-3.4*</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):149 +msgid "" +"Please note that the GCC 4.1 and newer can compile only kernels newer than " +"2.4.34. Don't remove your old GCC version if you want to use an older kernel." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):154 +msgid "" +"In case you're upgrading from GCC-3.3, you should run <c>emerge --oneshot " +"sys-libs/libstdc++-v3</c> to provide compatibility with older binary C++ " +"applications." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):165 +msgid "Upgrading from GCC-3.3 to 3.4" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):170 +msgid "" +"The upgrade from GCC-3.3 to 3.4 is not seamless as the C++ ABI changed " +"between these two versions. There is an issue with the <c>libstdc++</c> " +"library which must be taken care of, as well." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):179 +msgid "The Choices" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):182 +msgid "" +"If you upgrade from gcc 3.4 to 4.1, please consult the <uri link=\"#upgrade-" +"general\">General Update instructions</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):187 +msgid "" +"If you're upgrading on a SPARC machine, you will have to take the way of " +"<uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system rebuild</uri> due " +"to some internal <uri link=\"http://gcc.gnu.org/gcc-3.4/sparc-abi.html\">ABI " +"changes</uri> in GCC's parameter passing." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):194 +msgid "" +"If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to " +"upgrade your system. The <uri link=\"#upgrade-3.3-to-3.4-revdep-rebuild" +"\">first method</uri> is faster and requires use of the <c>revdep-rebuild</" +"c> tool from package <c>gentoolkit</c> while the <uri link=\"#upgrade-3.3-" +"to-3.4-emerge-e\">second one</uri> rebuilds the entire system from scratch " +"so it will make use of new GCC features. It's up to you to decide which of " +"these two ways you will choose. In most cases, the first method is " +"sufficient." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):205 +msgid "" +"If you upgrade from gcc 3.3 to 4.1, do not use the method based on revdep-" +"rebuild, but do a <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system " +"rebuild</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):214 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):242 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):390 +msgid "Using revdep-rebuild" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):217 +msgid "" +"This method requires that you first install <c>gentoolkit</c> if you have " +"not already done so. Then we will upgrade GCC and switch to the new " +"compiler. We will also rebuild the <c>libtool</c> package to ensure that " +"toolchain is in healthy state." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):224 +msgid "Installing gentoolkit and upgrading GCC" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):224 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -an gentoolkit</i>\n" +"# <i>emerge -uav gcc</i>\n" +"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" +"version and CHOST settings you've upgraded to:)</comment>\n" +"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" +"# <i>source /etc/profile</i>\n" +"\n" +"<comment>(Rebuilding libtool)</comment>\n" +"# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):236 +msgid "" +"Now, we want to see which packages that revdep-rebuild will want to rebuild. " +"Then we will tell revdep-rebuild to actually rebuild the packages. This may " +"take some time, so have some patience." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):242 +#, no-wrap +msgid "" +"\n" +"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" +"# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(note):247 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(note):405 +msgid "" +"It is possible that you might have problems with non-existing package " +"versions due to them being outdated or masked. If this is the case, you will " +"want to use the <c>--package-names</c> option to <c>revdep-rebuild</c>. This " +"causes packages to be recompiled based on the package name, rather than the " +"exact name and version." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):255 +msgid "" +"To provide compatibility with older binary C++ applications and any packages " +"that revdep-rebuild might have missed, <c>sys-libs/libstdc++-v3</c> needs to " +"be merged before you unmerge GCC 3.3 from your system." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):261 +msgid "Installing libstdc++-v3 and cleaning up" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):261 +#, no-wrap +msgid "" +"\n" +"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" +"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):269 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):416 +msgid "Using emerge -e" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):272 +msgid "" +"This method, while much slower, will rebuild your whole system to ensure " +"that everything has been rebuilt with your new compiler, and therefore " +"safer. At first, you will upgrade GCC and libtool and switch to your new " +"compiler." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):278 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -uav gcc</i>\n" +"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" +"version and CHOST settings you've upgraded to:)</comment>\n" +"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" +"# <i>source /etc/profile</i>\n" +"\n" +"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this\n" +"example) you will have to run fix_libtool_files.sh manually</comment>\n" +"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n" +"<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n" +"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</i>\n" +"\n" +"<comment>(Rebuilding libtool)</comment>\n" +"# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):295 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):377 +msgid "" +"To provide compatibility with older binary C++ applications, <c>sys-libs/" +"libstdc++-v3</c> needs to be merged onto your system." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):300 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):382 +msgid "Installing libstdc++-v3" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):300 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):382 +#, no-wrap +msgid "" +"\n" +"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):304 +msgid "" +"Now we will go about first rebuilding the system target, then the world " +"target. This will take a very long time, depending on the number of packages " +"that you have installed, as it will rebuild your entire toolchain and " +"supporting system files, followed by every package on your system, including " +"the toolchain. This is necessary to ensure that all packages have been " +"compiled with the new toolchain, including the toolchain itself." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):313 +msgid "Rebuilding system and world" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):313 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -e system</i>\n" +"# <i>emerge -e world</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):318 +msgid "It is also safe to remove older GCC versions at this time:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):322 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):440 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):448 +msgid "Cleaning up" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):322 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):331 +msgid "Upgrading to GCC on a First Install" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):336 +msgid "" +"A GCC upgrade on a system after installation from a stage3 tarball is a " +"simple affair. One advantage users of new installations have is they do not " +"have a plethora of software installed that links against the older version " +"of GCC. The following example is for a GCC-3.3 to 3.4 upgrade. Certain parts " +"will be different if upgrading from other versions of GCC. For example, the " +"library names used for <c>revdep-rebuild</c> below are GCC 3.3 specific, as " +"well as the need to install <c>libstdc++-v3</c>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):346 +msgid "" +"If a user has not made any customizations to their system yet, then there " +"are very few steps to get their system upgraded to a new GCC version. As " +"with the GCC-3.3 to 3.4 upgrade, the user has a couple options. However, " +"unlike the GCC-3.3 to 3.4 upgrade, this one is less complicated as there are " +"fewer differences between the methods. The <uri link=\"#first-install-revdep-" +"rebuild\">first method</uri> is faster and makes use of the <c>revdep-" +"rebuild</c> tool from <c>gentoolkit</c>, similar to the above procedure. " +"Using revdep-rebuild causes only packages which actually link against GCC " +"libraries to be rebuilt, while the <uri link=\"#first-install-emerge-e" +"\">second method</uri> causes your entire new install to be recompiled with " +"the new GCC version and takes much longer. This second method is never " +"required and only documented for completeness." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):361 +msgid "" +"These first steps are common between both methods, and should be completed " +"by everyone." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):366 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -uav gcc</i>\n" +"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" +"version and CHOST settings you've upgraded to:)</comment>\n" +"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" +"# <i>source /etc/profile</i>\n" +"\n" +"<comment>(Rebuilding libtool)</comment>\n" +"# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):393 +msgid "" +"This method requires that you first install <c>gentoolkit</c> if you have " +"not already done so. We will then run <c>revdep-rebuild</c> to actually scan " +"the installed packages for ones we need to rebuild, then rebuild them." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):399 +msgid "Installing gentoolkit and running revdep-rebuild" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):399 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -an gentoolkit</i>\n" +"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" +"# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):419 +msgid "" +"This method, while much slower, will rebuild the system target to ensure " +"that everything has been rebuilt with your new compiler. This is not " +"necessary, but is valid if you are also making changes to CFLAGS or other " +"make.conf variables that will affect the system compile." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):426 +msgid "" +"Since we are performing these actions after an initial installation, we do " +"not need to recompile the <c>world</c> target as we would when doing an " +"upgrade on an already installed system. However, you may choose to perform a " +"world update in place of the system update, to ensure that all packages are " +"updated." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):433 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -e system</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):443 +msgid "" +"It is also safe to remove older GCC versions at this time. Please substitute " +"<c>YOUR-NEW-GCC-VERSION</c> with the actual version you've upgraded to:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):448 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -aC \"<sys-devel/gcc-YOUR-NEW-GCC-VERSION\"</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):457 +msgid "Common Pitfalls" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):461 +msgid "" +"It's important to disable <c>distcc</c> during upgrade. Mixing compiler " +"versions on your nodes <e>will</e> cause build issues. This is not required " +"for ccache, as the cache objects will be invalidated anyway." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):467 +msgid "" +"Always use same GCC version for your kernel and additional kernel modules. " +"Once you rebuild your world with new GCC, external modules (like <c>app-" +"emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel " +"with the new GCC to fix that." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):474 +msgid "" +"If you're upgrading on a SPARC machine, make sure to rerun <c>silo -f</c> " +"after re-emerging world to avoid possible issues." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):482 +msgid "Frequent Error Messages" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):485 +msgid "" +"If your system complains about something like <e>libtool: link: `/usr/lib/" +"gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool " +"archive</e>, please run <c>/usr/share/gcc-data/$CHOST/<gcc-version>/" +"fix_libtool_files.sh 3.3.6</c> (substitute \"3.3.6\" with the version " +"numbers from the error message, and $CHOST and <gcc-version> with your " +"actual CHOST and GCC version)." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):494 +msgid "" +"If you see <e>error: /usr/bin/gcc-config: line 632: /etc/env.d/gcc/i686-pc-" +"linux-gnu-3.3.5: No such file or directory</e>, then try deleting <path>/etc/" +"env.d/gcc/config-i686-pc-linux-gnu</path> and running <c>gcc-config</c> " +"again, followed by <c>source /etc/profile</c>. Only do this if you do not " +"have any cross-compilers set up, though." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):502 +msgid "" +"If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, " +"you can resume operation with <c>emerge --resume</c>. If a package fails " +"repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any " +"other instances of emerge in between or you will lose the resume information." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):509 +msgid "" +"If you get an error message <e>spec failure: unrecognized spec option</e> " +"while upgrading your compiler, try to switch back to your default compiler, " +"unset the <c>GCC_SPECS</c> variable and upgrade GCC again:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):515 +msgid "Restoring primary specs" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):515 +#, no-wrap +msgid "" +"\n" +"# <i>gcc-config 1</i>\n" +"# <i>source /etc/profile</i>\n" +"# <i>unset GCC_SPECS</i>\n" +"# <i>emerge -uav gcc</i>\n" +msgstr "" + +#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(None):0 +msgid "translator-credits" +msgstr "" diff --git a/doc/gettext/el/gcc-upgrading.xml.po b/doc/gettext/el/gcc-upgrading.xml.po index 006108e..8bcced3 100644 --- a/doc/gettext/el/gcc-upgrading.xml.po +++ b/doc/gettext/el/gcc-upgrading.xml.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-10-21 23:56+0600\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -16,615 +16,278 @@ msgid "Gentoo GCC Upgrade Guide" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):9 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):12 msgid "Author" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):10 -msgid "amne@gentoo.org" +msgid "swift" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail):10 -msgid "Wernfried Haas" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):13 -msgid "jkt@gentoo.org" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail):13 -msgid "Jan Kundrát" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):15 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):18 -msgid "Editor" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):16 -msgid "halcy0n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):19 -msgid "nightmorph" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(abstract):22 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(abstract):13 msgid "This document will guide the user through the process of upgrading GCC." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(version):30 -msgid "23" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(version):21 +msgid "25" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(date):31 -msgid "2008-07-19" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):34 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):80 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):167 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):333 -msgid "Introduction" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(date):22 +msgid "2011-10-15" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):36 -msgid "GCC Upgrading" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):25 +msgid "Quickstart" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):39 -msgid "" -"Why should you upgrade? Well, GCC is quite similar to any other package on " -"your system, just a bit more critical. You should upgrade GCC whenever a new " -"version fixes some bug that annoys you, new functionality you need is " -"introduced, or if you want to keep your system up-to-date. If none of the " -"previous cases apply to you, you can safely postpone upgrade as long as your " -"GCC version is supported by Gentoo developers." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):48 -msgid "" -"If you install a new major version of GCC (such as 3.3.6 to 3.4.5), the " -"system will not switch over to use it automatically. You'll have to " -"explicitly request the change because the migration process might require " -"some additional steps. If you decide not to switch, Portage will continue to " -"use older version of your compiler until you change your mind, or remove the " -"old compiler from the system. Non-major gcc upgrades are switched " -"automatically for you (such as 3.4.5 to 3.4.6)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):58 -msgid "" -"This guide will document the necessary steps required to perform a seamless " -"upgrade of the compiler used by your Gentoo box. A specific section is " -"dedicated to the <uri link=\"#upgrade-3.3-to-3.4\">upgrade from GCC 3.3 to " -"3.4</uri> and issues with <c>libstdc++</c>. A second specific section is for " -"users <uri link=\"#first-install\">first installing</uri> Gentoo using a " -"stage3 tarball, after a new GCC major/minor version has been released." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(warn):67 -msgid "" -"It should be noted that upgrading from GCC-3.4 (or 3.3) to GCC-4.1 or " -"greater still requires you to follow the <uri link=\"#upgrade-general" -"\">general upgrading instructions</uri>, as GCC-3.4 and GCC-4.1 use slightly " -"different ABIs." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):78 -msgid "General Upgrade Instructions" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):27 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):84 +msgid "Introduction" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):83 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):30 msgid "" -"If you're looking for instructions specific to upgrades from GCC-3.3 to " -"GCC-3.4, please consult the <uri link=\"#upgrade-3.3-to-3.4\">dedicated " -"section</uri>." +"This is about <e>upgrading</e> GCC. Downgrading GCC might have unwanted side " +"effects. Please refer to <uri link=\"#troubleshooting\">Troubleshooting</" +"uri> for some commonly reported issues." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):89 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):36 msgid "" -"If you're looking for instructions specific to upgrades in GCC for new " -"installs, please consult the <uri link=\"#first-install\">dedicated section</" -"uri>." +"The next section gives a quick primer into GCC upgrades (and how easy they " +"are). If you want to read the lengthy reasoning behind GCC upgrades, please " +"continue with <uri link=\"#explanation\">GCC Upgrading Explained</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):95 -msgid "" -"Generally speaking, upgrades to <e>bug fix releases</e>, like from 3.3.5 to " -"3.3.6, should be quite safe -- just emerge new version, switch your system " -"to use it and rebuild the only affected package, <c>libtool</c>. However, " -"some GCC upgrades break binary compatibility; in such cases a rebuild of the " -"affected packages (or even whole toolchain and system) might be required." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):45 +msgid "Short Version" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):103 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):48 msgid "" -"When we spoke about the need to switch your compiler to the newer version by " -"hand, we said it won't happen automatically. However, there is one exception " -"-- upgrades to bug fix releases, like from 3.3.5 to 3.3.6 in case you don't " -"use the \"multislot\" feature allowing them to coexist on one system. " -"Multislot is disabled by default as the majority of users won't benefit from " -"it." +"If you are upgrading GCC then you do not need to do anything except switch " +"compiler version and rebuild libtool:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):111 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):278 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):366 -msgid "Upgrading GCC" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):53 +msgid "Switching GCC version" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):111 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):53 #, no-wrap msgid "" "\n" -"# <i>emerge -uav gcc</i>\n" +"# <i>emerge -u gcc</i>\n" +"# <i>gcc-config -l</i>\n" +"[1] i686-pc-linux-gnu-4.4.5 *\n" +"[2] i686-pc-linux-gnu-4.5.3\n" "\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-4.1.1\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>\n" +"# <i>gcc-config 2</i>\n" "# <i>env-update && source /etc/profile</i>\n" -"\n" -"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this\n" -"example) you will have to run fix_libtool_files.sh manually</comment>\n" -"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n" -"<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n" -"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.4.6</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):129 -msgid "" -"To be completely safe that your system is in a sane state, you <e>must</e> " -"rebuild the toolchain and then world to make use of the new compiler." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):134 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):433 -msgid "Rebuilding system" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):134 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -eav system</i>\n" -"# <i>emerge -eav world</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):139 -msgid "" -"It is safe to remove the older GCC version at this time. If you feel the " -"need, please issue the following command (as usual, substitute <c>=sys-devel/" -"gcc-3.4*</c> with the version you want to uninstall):" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):145 -msgid "Removing older GCC version" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):145 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -aC =sys-devel/gcc-3.4*</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):149 -msgid "" -"Please note that the GCC 4.1 and newer can compile only kernels newer than " -"2.4.34. Don't remove your old GCC version if you want to use an older kernel." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):154 -msgid "" -"In case you're upgrading from GCC-3.3, you should run <c>emerge --oneshot " -"sys-libs/libstdc++-v3</c> to provide compatibility with older binary C++ " -"applications." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):165 -msgid "Upgrading from GCC-3.3 to 3.4" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):170 -msgid "" -"The upgrade from GCC-3.3 to 3.4 is not seamless as the C++ ABI changed " -"between these two versions. There is an issue with the <c>libstdc++</c> " -"library which must be taken care of, as well." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):179 -msgid "The Choices" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):182 -msgid "" -"If you upgrade from gcc 3.4 to 4.1, please consult the <uri link=\"#upgrade-" -"general\">General Update instructions</uri>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):187 -msgid "" -"If you're upgrading on a SPARC machine, you will have to take the way of " -"<uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system rebuild</uri> due " -"to some internal <uri link=\"http://gcc.gnu.org/gcc-3.4/sparc-abi.html\">ABI " -"changes</uri> in GCC's parameter passing." +"# <i>emerge --oneshot libtool</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):194 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):64 msgid "" -"If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to " -"upgrade your system. The <uri link=\"#upgrade-3.3-to-3.4-revdep-rebuild" -"\">first method</uri> is faster and requires use of the <c>revdep-rebuild</" -"c> tool from package <c>gentoolkit</c> while the <uri link=\"#upgrade-3.3-" -"to-3.4-emerge-e\">second one</uri> rebuilds the entire system from scratch " -"so it will make use of new GCC features. It's up to you to decide which of " -"these two ways you will choose. In most cases, the first method is " -"sufficient." +"If you upgrade GCC from a version earlier than 3.4.0 (for the 3.x series) or " +"4.1, you will need to run <c>revdep-rebuild</c> as well:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):205 -msgid "" -"If you upgrade from gcc 3.3 to 4.1, do not use the method based on revdep-" -"rebuild, but do a <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system " -"rebuild</uri>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):214 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):242 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):390 -msgid "Using revdep-rebuild" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):217 -msgid "" -"This method requires that you first install <c>gentoolkit</c> if you have " -"not already done so. Then we will upgrade GCC and switch to the new " -"compiler. We will also rebuild the <c>libtool</c> package to ensure that " -"toolchain is in healthy state." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):224 -msgid "Installing gentoolkit and upgrading GCC" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):69 +msgid "Upgrading from a non-forward compatible GCC version" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):224 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):69 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):135 #, no-wrap msgid "" "\n" -"# <i>emerge -an gentoolkit</i>\n" -"# <i>emerge -uav gcc</i>\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" -"# <i>source /etc/profile</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):236 -msgid "" -"Now, we want to see which packages that revdep-rebuild will want to rebuild. " -"Then we will tell revdep-rebuild to actually rebuild the packages. This may " -"take some time, so have some patience." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):242 -#, no-wrap -msgid "" -"\n" -"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" "# <i>revdep-rebuild --library libstdc++.so.5</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(note):247 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(note):405 -msgid "" -"It is possible that you might have problems with non-existing package " -"versions due to them being outdated or masked. If this is the case, you will " -"want to use the <c>--package-names</c> option to <c>revdep-rebuild</c>. This " -"causes packages to be recompiled based on the package name, rather than the " -"exact name and version." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):73 +msgid "There you go. Enjoy the new compiler!" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):255 -msgid "" -"To provide compatibility with older binary C++ applications and any packages " -"that revdep-rebuild might have missed, <c>sys-libs/libstdc++-v3</c> needs to " -"be merged before you unmerge GCC 3.3 from your system." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):82 +msgid "GCC Upgrading Explained" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):261 -msgid "Installing libstdc++-v3 and cleaning up" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):261 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):87 msgid "" -"\n" -"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" -"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +"GCC upgrading has always been mystified, with suggestions ranging from \"You " +"do not need to do anything\" up to \"You will need to rebuild your entire " +"system twice\". Most of this FUD comes from the confusion surrounding ABI " +"incompatibility. But first a quick pointer towards <c>libtool</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):269 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):416 -msgid "Using emerge -e" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):97 +msgid "libtool and fix_libtool_files.sh" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):272 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):100 msgid "" -"This method, while much slower, will rebuild your whole system to ensure " -"that everything has been rebuilt with your new compiler, and therefore " -"safer. At first, you will upgrade GCC and libtool and switch to your new " -"compiler." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):278 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -uav gcc</i>\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" -"# <i>source /etc/profile</i>\n" -"\n" -"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this\n" -"example) you will have to run fix_libtool_files.sh manually</comment>\n" -"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n" -"<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n" -"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" +"Earlier installments of GCC on Gentoo required you to run a specific command " +"called <c>fix_libtool_files.sh</c>. Some time ago, the execution of this " +"command has been integrated in the package deployments itself (through the " +"toolchain eclass) so there is no need for users to call this themselves " +"anymore." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):295 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):377 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):107 msgid "" -"To provide compatibility with older binary C++ applications, <c>sys-libs/" -"libstdc++-v3</c> needs to be merged onto your system." +"The reason we need to rebuild libtool after the upgrade of gcc versions is " +"because of its main purpose: <e>libtool</e> is a toolset that aggregates " +"platform-specific code in a generic interface, allowing applications to " +"build against shared libraries without needing to deal with the platform " +"specific aspects of shared libraries. To fulfill its function properly, the " +"<c>libtool</c> script uses various library locations that have hardcoded GCC " +"version information in them." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):300 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):382 -msgid "Installing libstdc++-v3" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):120 +msgid "ABI Changes" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):300 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):382 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):123 msgid "" -"\n" -"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" +"An ABI, or <e>Application Binary Interface</e>, is a set of conventions used " +"by all tools that deal with binary representation of programs, including " +"compilers, assemblers, linkers and language runtime support (source: <uri " +"link=\"http://gcc.gnu.org/onlinedocs/gcc/Compatibility.html\">GCC Binary " +"Compatibility</uri>). When the ABI used for binary applications and " +"libraries is changed, you will risk getting linker errors or malfunctioning " +"programs unless you rebuild all libraries that use C++ code. Yes, C++, since " +"most incompatibilities occur within the C++ ABI. This is also why we use the " +"<c>revdep-rebuild</c> command against the <path>libstdc++.so.5</path> " +"library." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):304 -msgid "" -"Now we will go about first rebuilding the system target, then the world " -"target. This will take a very long time, depending on the number of packages " -"that you have installed, as it will rebuild your entire toolchain and " -"supporting system files, followed by every package on your system, including " -"the toolchain. This is necessary to ensure that all packages have been " -"compiled with the new toolchain, including the toolchain itself." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):135 +msgid "Rebuilding applications linked against libstdc++.so.5" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):313 -msgid "Rebuilding system and world" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):313 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -e system</i>\n" -"# <i>emerge -e world</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):318 -msgid "It is also safe to remove older GCC versions at this time:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):322 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):440 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):448 -msgid "Cleaning up" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):322 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):139 msgid "" -"\n" -"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +"So why is this only needed up to GCC 3.4.0/4.1 ? That's because from that " +"version onwards, GCC uses a forward compatible ABI, which removes the need " +"for rebuilding applications and libraries. Of course, guarantees can never " +"be given indefinitely, but when an incompatibility occurs again, we'll " +"definitely document it here ;-) In that case, the version of the " +"<path>libstdc++.so</path> library will probably be increased." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):331 -msgid "Upgrading to GCC on a First Install" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):151 +msgid "Rebuilding Everything" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):336 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):154 msgid "" -"A GCC upgrade on a system after installation from a stage3 tarball is a " -"simple affair. One advantage users of new installations have is they do not " -"have a plethora of software installed that links against the older version " -"of GCC. The following example is for a GCC-3.3 to 3.4 upgrade. Certain parts " -"will be different if upgrading from other versions of GCC. For example, the " -"library names used for <c>revdep-rebuild</c> below are GCC 3.3 specific, as " -"well as the need to install <c>libstdc++-v3</c>." +"Some people swear that they need to rebuild every single package on their " +"system when a new GCC version is made available. Of course, that doesn't " +"make sense, since there are many applications that are not using GCC for " +"their build and install process anyhow, so they would never be affected by " +"such changes." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):346 -msgid "" -"If a user has not made any customizations to their system yet, then there " -"are very few steps to get their system upgraded to a new GCC version. As " -"with the GCC-3.3 to 3.4 upgrade, the user has a couple options. However, " -"unlike the GCC-3.3 to 3.4 upgrade, this one is less complicated as there are " -"fewer differences between the methods. The <uri link=\"#first-install-revdep-" -"rebuild\">first method</uri> is faster and makes use of the <c>revdep-" -"rebuild</c> tool from <c>gentoolkit</c>, similar to the above procedure. " -"Using revdep-rebuild causes only packages which actually link against GCC " -"libraries to be rebuilt, while the <uri link=\"#first-install-emerge-e" -"\">second method</uri> causes your entire new install to be recompiled with " -"the new GCC version and takes much longer. This second method is never " -"required and only documented for completeness." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):361 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):161 msgid "" -"These first steps are common between both methods, and should be completed " -"by everyone." +"That however doesn't mean they are completely incorrect: newer GCC versions " +"often include better support for the processors' instruction set, which " +"might influence the performance of some applications in a positive way. " +"Although it is expected that this improvement is generally only marginally, " +"in some cases (especially CPU intensive applications) this might yield " +"notable improvements." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):366 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):169 msgid "" -"\n" -"# <i>emerge -uav gcc</i>\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" -"# <i>source /etc/profile</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" +"There are also known cases where packages need to be built with the same " +"compiler. Although these packages are usually bumped by Gentoo " +"simultaneously (so that they are always built with the same GCC version) " +"cherry-picking reinstalls on these packages might prove to be troublesome. " +"The various <path>qt-*</path> packages are a nice example on this matter." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):393 -msgid "" -"This method requires that you first install <c>gentoolkit</c> if you have " -"not already done so. We will then run <c>revdep-rebuild</c> to actually scan " -"the installed packages for ones we need to rebuild, then rebuild them." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):399 -msgid "Installing gentoolkit and running revdep-rebuild" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):182 +msgid "Troubleshooting" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):399 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -an gentoolkit</i>\n" -"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" -"# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):184 +msgid "libstdc++.so.6: version `GLIBCXX_3.4.15' not found" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):419 -msgid "" -"This method, while much slower, will rebuild the system target to ensure " -"that everything has been rebuilt with your new compiler. This is not " -"necessary, but is valid if you are also making changes to CFLAGS or other " -"make.conf variables that will affect the system compile." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):187 +msgid "During updates, you might encounter an error like the following:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):426 -msgid "" -"Since we are performing these actions after an initial installation, we do " -"not need to recompile the <c>world</c> target as we would when doing an " -"upgrade on an already installed system. However, you may choose to perform a " -"world update in place of the system update, to ensure that all packages are " -"updated." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):191 +msgid "GLIBCXX_x.y.z not found" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):433 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):191 #, no-wrap msgid "" "\n" -"# <i>emerge -e system</i>\n" +"cmake_bootstrap_28021_test: /usr/lib/gcc/i486-pc-linux-gnu/4.1.2/libstdc++.so.6:\n" +"version `GLIBCXX_3.4.11' not found \n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):443 -msgid "" -"It is also safe to remove older GCC versions at this time. Please substitute " -"<c>YOUR-NEW-GCC-VERSION</c> with the actual version you've upgraded to:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):448 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):196 msgid "" -"\n" -"# <i>emerge -aC \"<sys-devel/gcc-YOUR-NEW-GCC-VERSION\"</i>\n" +"This means that you are trying to build a package with an <e>older</e> GCC " +"version than with which some depending libraries were built. Remember when " +"we told that the C++ ABI if forward-compatible? That is true, but it ensures " +"only that <e>higher</e> (or same) GCC versions can be used when building " +"applications and linking libraries (compared to the GCC version used to " +"build those libraries)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):457 -msgid "Common Pitfalls" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):208 +msgid "Which packages are known to need a rebuild?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):461 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):211 msgid "" -"It's important to disable <c>distcc</c> during upgrade. Mixing compiler " -"versions on your nodes <e>will</e> cause build issues. This is not required " -"for ccache, as the cache objects will be invalidated anyway." +"The following table gives the packages that, <e>if installed</e>, need to be " +"rebuild and why." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):467 -msgid "" -"Always use same GCC version for your kernel and additional kernel modules. " -"Once you rebuild your world with new GCC, external modules (like <c>app-" -"emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel " -"with the new GCC to fix that." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(th):218 +msgid "Package" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):474 -msgid "" -"If you're upgrading on a SPARC machine, make sure to rerun <c>silo -f</c> " -"after re-emerging world to avoid possible issues." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(th):219 +msgid "Rebuild needed because ..." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):482 -msgid "Frequent Error Messages" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):222 +msgid "sys-devel/libtool" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):485 -msgid "" -"If your system complains about something like <e>libtool: link: `/usr/lib/" -"gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool " -"archive</e>, please run <c>/usr/share/gcc-data/$CHOST/<gcc-version>/" -"fix_libtool_files.sh 3.3.6</c> (substitute \"3.3.6\" with the version " -"numbers from the error message, and $CHOST and <gcc-version> with your " -"actual CHOST and GCC version)." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):223 +msgid "libtool application has hardcoded paths towards GCC internal libraries" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):494 -msgid "" -"If you see <e>error: /usr/bin/gcc-config: line 632: /etc/env.d/gcc/i686-pc-" -"linux-gnu-3.3.5: No such file or directory</e>, then try deleting <path>/etc/" -"env.d/gcc/config-i686-pc-linux-gnu</path> and running <c>gcc-config</c> " -"again, followed by <c>source /etc/profile</c>. Only do this if you do not " -"have any cross-compilers set up, though." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):229 +msgid "dev-lang/ghc" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):502 -msgid "" -"If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, " -"you can resume operation with <c>emerge --resume</c>. If a package fails " -"repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any " -"other instances of emerge in between or you will lose the resume information." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):230 +msgid "ghc application has hardcoded paths towards GCC internal libraries" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):509 -msgid "" -"If you get an error message <e>spec failure: unrecognized spec option</e> " -"while upgrading your compiler, try to switch back to your default compiler, " -"unset the <c>GCC_SPECS</c> variable and upgrade GCC again:" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):241 +msgid "Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):515 -msgid "Restoring primary specs" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):243 +msgid "Gentoo Guides and Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):515 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(li):247 msgid "" -"\n" -"# <i>gcc-config 1</i>\n" -"# <i>source /etc/profile</i>\n" -"# <i>unset GCC_SPECS</i>\n" -"# <i>emerge -uav gcc</i>\n" +"<uri link=\"gcc-upgrading-upto-4.1.xml\">GCC Upgrading up to 4.1</uri>, the " +"previous version of this document" msgstr "" #. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL diff --git a/doc/gettext/el/gentoo-x86-quickinstall-system.xml.po b/doc/gettext/el/gentoo-x86-quickinstall-system.xml.po index 454696b..b84e2d8 100644 --- a/doc/gettext/el/gentoo-x86-quickinstall-system.xml.po +++ b/doc/gettext/el/gentoo-x86-quickinstall-system.xml.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-10-21 23:56+0600\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -12,11 +12,11 @@ msgstr "" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(version):7 -msgid "4" +msgid "6" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(date):8 -msgid "2011-08-23" +msgid "2011-09-23" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):11 @@ -78,15 +78,16 @@ msgid "" "Configure your network in <path>/etc/conf.d/net</path>. Add the <c>net.eth0</" "c> init script to the default run level. If you have multiple NICs, symlink " "them to the <c>net.eth0</c> init script and add them to the default run " -"level as well. Either edit <path>/etc/conf.d/net</path> with <c>nano</c> or " +"level as well. Don't forget to set your hostname too. Either edit <path>/etc/" +"conf.d/net</path> and <path>/etc/conf.d/hostname</path> with <c>nano</c> or " "use the following commands:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):66 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):67 msgid "Configure networking" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):66 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):67 #, no-wrap msgid "" "\n" @@ -95,6 +96,7 @@ msgid "" "livecd init.d # <i>cd ../conf.d</i>\n" "livecd conf.d # <i>echo 'config_eth0=\"192.168.1.10 netmask 255.255.255.0 brd 192.168.1.255\"' >> net</i>\n" "livecd conf.d # <i>echo 'routes_eth0=\"default via 192.168.1.1\"' >> net</i>\n" +"livecd conf.d # <i>echo 'hostname=\"myhostname\"' > hostname</i>\n" "livecd conf.d # <i>rc-update add net.eth0 default</i>\n" "<comment>(If you compiled your network card driver as a module, add it to /etc/conf.d/modules</comment>\n" "livecd conf.d # <i>echo 'modules=\"r8169\"' >> /etc/conf.d/modules</i>\n" @@ -102,19 +104,19 @@ msgid "" "livecd conf.d # <i>rc-update add sshd default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):79 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):81 msgid "Emerge <c>pcmciautils</c> if you need support for PCMCIA cards." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):83 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):85 msgid "Set the root password using <c>passwd</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):87 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):89 msgid "Set the root password" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):87 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):89 #, no-wrap msgid "" "\n" @@ -124,33 +126,33 @@ msgid "" "passwd: password updated successfully\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):94 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):96 msgid "" "Edit <path>/etc/timezone</path> to define the time zone you used previously." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):99 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):101 msgid "Edit /etc/timezone" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):99 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):101 #, no-wrap msgid "" "\n" "Europe/Brussels\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):103 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):105 msgid "" "Check the system configuration in <path>/etc/rc.conf</path> and <path>/etc/" "conf.d/keymaps</path> and edit any of those files if required." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):108 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):110 msgid "Optional: edit some config files" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):108 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):110 #, no-wrap msgid "" "\n" @@ -158,32 +160,34 @@ msgid "" "livecd conf.d # <i>nano -w /etc/conf.d/keymaps</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):116 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):118 msgid "Installing System Tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):120 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):122 msgid "Install RAID and LVM2 utilities." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):124 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):126 msgid "Install RAID LVM2 tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):124 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):126 #, no-wrap msgid "" "\n" "livecd conf.d # <i>emerge mdadm lvm2</i>\n" +"livecd conf.d # <i>rc-update add mdraid boot</i>\n" +"livecd conf.d # <i>rc-update add lvm boot</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):131 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):135 msgid "" "Install a system logger like <c>syslog-ng</c> and a cron daemon like " "<c>vixie-cron</c>, and add them to the default run level." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):136 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):140 msgid "" "Cron daemons depend on an MTA. <c>mail-mta/ssmtp</c> will be pulled in as a " "dependency. If you want to use a more advanced MTA, you might want to " @@ -191,11 +195,11 @@ msgid "" "later when you install the MTA of your choice." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):143 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):147 msgid "Install a syslogger and a cron daemon" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):143 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):147 #, no-wrap msgid "" "\n" @@ -208,18 +212,18 @@ msgid "" "livecd conf.d # <i>rc-update add vixie-cron default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):153 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):157 msgid "" "Install the necessary file system tools (<c>xfsprogs</c>, <c>reiserfsprogs</" "c> or <c>jfsutils</c>) and networking tools (<c>dhcpcd</c> or <c>ppp</c>) if " "you need any." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):159 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):163 msgid "Install extra tools if required" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):159 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):163 #, no-wrap msgid "" "\n" @@ -230,21 +234,21 @@ msgid "" "livecd conf.d # <i>emerge ppp</i> <comment>(If you need PPPoE ADSL connectivity)</comment>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):171 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):175 msgid "Configuring the Bootloader" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):174 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):178 msgid "" "Emerge <c>grub</c> and configure it. Do not forget to update the necessary " "boot parameters if you are using an initramfs." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):179 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):183 msgid "Emerge grub and edit its configuration file" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):179 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):183 #, no-wrap msgid "" "\n" @@ -256,11 +260,11 @@ msgid "" "livecd conf.d # <i>nano -w /boot/grub/grub.conf</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):188 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):192 msgid "Example grub.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):188 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):192 #, no-wrap msgid "" "\n" @@ -272,11 +276,11 @@ msgid "" "kernel /boot/kernel root=<keyval id=\"root\"></keyval>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):197 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):201 msgid "Install grub" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):197 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):201 #, no-wrap msgid "" "\n" @@ -299,11 +303,11 @@ msgid "" "grub> <i>quit</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):217 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):221 msgid "Install grub on both disks" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):217 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):221 #, no-wrap msgid "" "\n" diff --git a/doc/gettext/el/gnome-config.xml.po b/doc/gettext/el/gnome-config.xml.po index 36ab808..d5e54f4 100644 --- a/doc/gettext/el/gnome-config.xml.po +++ b/doc/gettext/el/gnome-config.xml.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-10-21 23:56+0600\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -51,11 +51,11 @@ msgid "" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(version):27 -msgid "3" +msgid "4" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(date):28 -msgid "2011-08-13" +msgid "2011-10-23" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):31 @@ -172,47 +172,50 @@ msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):122 msgid "" -"You can also opt for a minimal Gnome installation using <c>gnome-light</c>:" +"You can also opt for a minimal Gnome installation using <c>gnome-light</c>. " +"If you do so, you will have a lightweight Gnome installation without the " +"additional tools that a full Gnome installation provides so you might need " +"to install additional packages afterwards." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):126 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):129 msgid "Installing a minimal GNOME environment" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):126 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):129 #, no-wrap msgid "" "\n" "# <i>emerge gnome-light</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):130 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):133 msgid "" "This will take a while, so you might want to start reading all those books " "your mother bought you but you never opened. Done? Great, now update your " "environment variables:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):136 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):139 msgid "Updating environment variables" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):136 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):139 #, no-wrap msgid "" "\n" "# <i>env-update && source /etc/profile</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):140 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):143 msgid "Next we'll clean up the remaining services and user groups." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):144 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):147 msgid "Setting up the DBUS service" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):144 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):147 #, no-wrap msgid "" "\n" @@ -220,18 +223,18 @@ msgid "" "# <i>rc-update add dbus default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):149 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):152 msgid "" "Check if the <e>plugdev</e> group exists. If it does, it is adviseable to " "make yourself member of that group, but this is optional (the group is not " "that common anymore)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):155 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):158 msgid "Checking and adding users to plugdev" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):155 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):158 #, no-wrap msgid "" "\n" @@ -242,11 +245,11 @@ msgid "" "~# <i>gpasswd -a yourUserName plugdev</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):166 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):169 msgid "First Impressions" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):169 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):172 msgid "" "Let us first take a look at what we just built. Exit your root shell and log " "on as a regular user. We will configure our session to run GNOME when we " @@ -255,18 +258,18 @@ msgid "" "xml\">X Server Configuration Howto</uri>):" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):177 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):180 msgid "Setting GNOME as the default desktop environment" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):177 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):180 #, no-wrap msgid "" "\n" "$ <i>echo \"exec gnome-session\" > ~/.xinitrc</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):181 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):184 msgid "" "Starting with <c>gnome-base/gnome-session-2.26.2</c>, you will need to " "prepend the XDG_MENU_PREFIX variable to get the Gnome menus if you're using " @@ -275,81 +278,99 @@ msgid "" "additional configuration is needed.)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):189 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):192 msgid "Prepending XDG_MENU_PREFIX to ~/.xinitrc" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):189 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):192 #, no-wrap msgid "" "\n" "$ <i>sed -i '1i\\export XDG_MENU_PREFIX=gnome-' ~/.xinitrc</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):193 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):196 msgid "Now start your graphical environment by running <c>startx</c>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):197 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):200 msgid "Starting GNOME" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):197 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):200 #, no-wrap msgid "" "\n" "$ <i>startx</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):201 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):204 msgid "" "If all goes well, you should be greeted by GNOME. Congratulations. Now let " "us take a look at how you can configure GNOME to suit your needs." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):210 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):213 msgid "Configuring GNOME" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):212 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):215 msgid "GNOME's Graphical Login Manager" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):215 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):218 msgid "" "If you want the GNOME Display Manager (GDM) to run automatically when you " "boot (so you can log on graphically), you must add the <c>xdm</c> init " "script to the default runlevel:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):221 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):224 msgid "Adding xdm to the default runlevel" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):221 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):224 #, no-wrap msgid "" "\n" "# <i>rc-update add xdm default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):225 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):228 msgid "" "Now edit <path>/etc/conf.d/xdm</path> and alter the DISPLAYMANAGER variable." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):229 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):232 msgid "Editing /etc/conf.d/xdm" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):229 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):232 #, no-wrap msgid "" "\n" "DISPLAYMANAGER=\"gdm\"\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):233 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):236 +msgid "" +"If you installed Gnome using the <c>gnome-light</c> package, you will need " +"to install <c>gdm</c> too (as it is not defined as part of the <c>gnome-" +"light</c> package)." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):242 +msgid "Installing the gdm application" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):242 +#, no-wrap +msgid "" +"\n" +"# <i>emerge gdm</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):246 msgid "" "If you reboot now, the GNOME Display Manager will prompt you for your " "username and password and will default to using GNOME as Desktop Environment " diff --git a/doc/gettext/el/power-management-guide.xml.po b/doc/gettext/el/power-management-guide.xml.po index f47b7b4..ebb8a05 100644 --- a/doc/gettext/el/power-management-guide.xml.po +++ b/doc/gettext/el/power-management-guide.xml.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-10-21 23:56+0600\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -20,2223 +20,723 @@ msgid "Author" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):9 -msgid "earthwings@gentoo.org" +msgid "swift" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):9 -msgid "Dennis Nienhüser" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):11 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):14 -msgid "Editor" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):12 -msgid "chriswhite@gentoo.org" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):12 -msgid "Chris White" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):15 -msgid "nightmorph" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(abstract):18 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(abstract):12 msgid "" -"Power Management is the key to extend battery run time on mobile systems " -"like laptops. This guide assists you setting it up on your laptop." +"In recent years, power management has become one of the differentiating " +"features in the quest for finding the perfect laptop. Yet, the operating " +"system must support the various power saving functionalities too. In this " +"guide, we cover how to setup your Gentoo installation so it manages power-" +"hungry resources in a flexible yet automated manner." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(version):27 -msgid "4" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(version):24 +msgid "5" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(date):28 -msgid "2011-08-17" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(date):25 +msgid "2011-09-22" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):31 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):28 msgid "Introduction" msgstr "" -#. Remove this note after 6 months - ETA 01/02/2012 -#. By then, we can assume that OpenRC migrations are not that frequent -#. anymore and this note can be dropped. -#. ~ Sven Vermeulen -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(impo):41 -msgid "" -"Since the introduction of OpenRC, the <c>pmg_switch_runlevel.sh</c> script " -"needs to be updated. If you have issues after the OpenRC upgrade, please " -"update this script according to this guide." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):30 +msgid "About this document..." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):47 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):33 msgid "" -"Capacity and lifetime of laptop batteries have improved much in the last " -"years. Nevertheless modern processors consume much more energy than older " -"ones and each laptop generation introduces more devices hungry for energy. " -"That's why Power Management is more important than ever. Increasing battery " -"run time doesn't necessarily mean buying another battery. Much can be " -"achieved applying intelligent Power Management policies." +"This document describes the setup of power management features on your " +"laptop. Although some of the information in this guide can be applied to " +"power management for servers, it is not the intention of this document to go " +"that route. Please be careful when applying this on a non-laptop system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):59 -msgid "A Quick Overview" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):62 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):40 msgid "" -"Please notice that this guide describes Power Management for <e>laptops</e>. " -"While some sections might also suite for <e>servers</e>, others do not and " -"may even cause harm. Please do not apply anything from this guide to a " -"server unless you really know what you are doing." +"Within this document, we will focus primarily on the laptop mode tools since " +"it offers a complete set of functionalities. However, we will also refer to " +"other tools that might offer a more detailed approach on individual " +"settings. In such cases, you will need to disable the feature from the " +"laptop mode tools so that both tools do not fight over the same resource " +"control." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):69 -msgid "" -"As this guide has become rather long, here's a short overview helping you to " -"find your way through it." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):51 +msgid "About laptop_mode" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):74 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):54 msgid "" -"The <uri link=\"#doc_chap2\">Prerequisites</uri> chapter talks about some " -"requirements that should be met before any of the following device " -"individual sections will work. This includes BIOS settings, kernel " -"configuration and some simplifications in user land. The following three " -"chapters focus on devices that typically consume most energy - processor, " -"display and hard drive. Each can be configured separately. <uri link=" -"\"#doc_chap3\">CPU Power Management</uri> shows how to adjust the " -"processor's frequency to save a maximum of energy without losing too much " -"performance. A few different tricks prevent your hard drive from working " -"unnecessarily often in <uri link=\"#doc_chap5\">Disk Power Management</uri> " -"(decreasing noise level as a nice side effect). Some notes on graphics " -"cards, Wireless LAN and USB finish the device section in <uri link=" -"\"#doc_chap6\">Power Management For Other Devices</uri> while another " -"chapter is dedicated to the (rather experimental) <uri link=" -"\"#doc_chap7\">sleep states</uri>. Last not least <uri link=" -"\"#doc_chap8\">Troubleshooting</uri> lists common pitfalls." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):95 -msgid "Power Budget For Each Component" +"The <c>laptop_mode</c> setting is an in-kernel configuration setting that " +"optimizes I/O, allowing disks to spin down properly (and not be woken up " +"immediately afterwards for queued operations)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:link):99 -msgid "/images/energy-budget.png" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):63 +msgid "About laptop-mode-tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:short):99 -msgid "Which component consumes how much energy?" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:caption):99 -msgid "Power budget for each component" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):101 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):66 msgid "" -"Nearly every component can operate in different states - off, sleep, idle, " -"active to name a few - consuming a different amount of energy. Major parts " -"are consumed by the LCD display, CPU, chipset and hard drives. Often one is " -"able to activate OS-independent Power Management in the BIOS, but an " -"intelligent setup in the operating system adapting to different situations " -"can achieve much more." +"The <e>Laptop Mode Tools</e> is a software package (<c>app-laptop/laptop-" +"mode-tools</c>) which allows the user to optimize power saving functions. It " +"allows managing the <c>laptop_mode</c> setting in the Linux kernel, but has " +"additional features allowing you to tweak other power-related settings on " +"the system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):114 -msgid "Prerequisites" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):79 +msgid "Linux Kernel Configuration" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):118 -msgid "" -"Before discussing the details of making individual devices Power Management " -"aware, make sure certain requirements are met. After controlling BIOS " -"settings, some kernel options want to be enabled - these are in short ACPI, " -"sleep states and CPU frequency scaling. As power saving most of the time " -"comes along with performance loss or increased latency, it should only be " -"enabled when running on batteries. That's where a new runlevel <e>battery</" -"e> comes in handy." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):130 -msgid "The BIOS Part" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):133 -msgid "" -"First have a look into your BIOS Power Management settings. The best way is " -"to combine BIOS and operating system policies, but for the moment it's " -"better to disable most of the BIOS part. This makes sure it doesn't " -"interfere with your policies. Don't forget to re-check BIOS settings after " -"you configured everything else." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):144 -msgid "Setting USE Flags" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):147 -msgid "" -"Please check that the <c>acpi</c> USE flag is set in <path>/etc/make.conf</" -"path>. Other USE flags that might be interesting for your system are <c>apm</" -"c>, <c>lm_sensors</c>, <c>nforce2</c>, <c>nvidia</c>, <c>pmu</c>. See <path>/" -"usr/portage/profiles/use*.desc</path> for details. If you forgot to set one " -"of these flags, you can recompile affected packages using the <c>--newuse</" -"c> flag in <c>emerge</c>, see <c>man emerge</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):159 -msgid "Configuring The Kernel" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):162 -msgid "" -"ACPI (Advanced Configuration and Power Interface) support in the kernel is " -"still work in progress. Using a recent kernel will make sure you'll get the " -"most out of it." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):81 +msgid "Minimum kernel setup" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):168 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):84 msgid "" -"There are different kernel sources in Portage. I'd recommend using <c>gentoo-" -"sources</c> or <c>tuxonice-sources</c>. The latter contains patches for " -"TuxOnIce, see the chapter about <uri link=\"#doc_chap7\">sleep states</uri> " -"for more details. When configuring the kernel, activate at least these " -"options:" +"There are different kernel sources in Portage. We recommend using <c>gentoo-" +"sources</c>, but if you want advanced hibernation support you might need " +"<c>tuxonice-sources</c>. To enable proper power management features in the " +"Linux kernel, enable at least the following settings:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):175 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):91 msgid "Minimum kernel setup for Power Management (Kernel 2.6)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):175 -#, no-wrap -msgid "" -"\n" -"Power management and ACPI options --->\n" -"[*] Power Management support\n" -" [ ] Software Suspend\n" -"\n" -" ACPI( Advanced Configuration and Power Interface ) Support --->\n" -" [ ] Deprecated /proc/acpi/ files\n" -" [*] AC Adapter\n" -" [*] Battery\n" -" <M> Button\n" -" <M> Video\n" -" [ ] Generic Hotkey\n" -" <M> Fan\n" -" <M> Processor\n" -" <M> Thermal Zone\n" -" < > ASUS/Medion Laptop Extras\n" -" < > IBM ThinkPad Laptop Extras\n" -" < > Toshiba Laptop Extras\n" -" (0) Disable ACPI for systems before Jan 1st this year\n" -" [ ] Debug Statements\n" -" [*] Power Management Timer Support\n" -" < > ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL)\n" -"\n" -" CPU Frequency Scaling --->\n" -" [*] CPU Frequency scaling\n" -" [ ] Enable CPUfreq debugging\n" -" < > CPU frequency translation statistics\n" -" [ ] CPU frequency translation statistics details\n" -" Default CPUFreq governor (userspace)\n" -" <*> 'performance' governor\n" -" <*> 'powersave' governor\n" -" <*> 'ondemand' cpufreq policy governor\n" -" <*> 'conservative' cpufreq governor\n" -" <*> CPU frequency table helpers\n" -" <M> ACPI Processor P-States driver\n" -" <*> <i>CPUFreq driver for your processor</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):213 -msgid "" -"Decide yourself whether you want to enable Software Suspend, and Sleep " -"States (see below). If you own an ASUS, Medion, IBM Thinkpad or Toshiba " -"laptop, enable the appropriate section." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):219 -msgid "" -"The kernel has to know how to enable CPU frequency scaling on your " -"processor. As each type of CPU has a different interface, you've got to " -"choose the right driver for your processor. Be careful here - enabling " -"<c>Intel Pentium 4 clock modulation</c> on a Pentium M system will lead to " -"strange results for example. Consult the kernel documentation if you're " -"unsure which one to take." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):227 -msgid "" -"Compile your kernel, make sure the right modules get loaded at startup and " -"boot into your new ACPI-enabled kernel. Next run <c>emerge sys-power/acpid</" -"c> to get the acpi daemon. This one informs you about events like switching " -"from AC to battery or closing the lid. Make sure the modules are loaded if " -"you didn't compile them into the kernel and start acpid by executing <c>/etc/" -"init.d/acpid start</c>. Run <c>rc-update add acpid default</c> to load it on " -"startup. You'll soon see how to use it." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):237 -msgid "Installing acpid" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):237 -#, no-wrap -msgid "" -"\n" -"# <i>emerge sys-power/acpid</i>\n" -"# <i>/etc/init.d/acpid start</i>\n" -"# <i>rc-update add acpid default</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):246 -msgid "Creating A \"battery\" Runlevel" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):249 -msgid "" -"The default policy will be to enable Power Management only when needed - " -"running on batteries. To make the switch between AC and battery convenient, " -"create a runlevel <c>battery</c> that holds all the scripts starting and " -"stopping Power Management." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):256 -msgid "" -"You can safely skip this section if you don't like the idea of having " -"another runlevel. However, skipping this step will make the rest a bit " -"trickier to set up. The next sections assume a runlevel <c>battery</c> " -"exists." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):262 -msgid "Creating a battery runlevel" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):262 -#, no-wrap -msgid "" -"\n" -"# <i>cd /etc/runlevels</i>\n" -"# <i>cp -a default battery</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):267 -msgid "" -"Finished. Your new runlevel <c>battery</c> contains everything like " -"<c>default</c>, but there is no automatic switch between both yet. Time to " -"change it." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):276 -msgid "Reacting On ACPI Events" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):279 -msgid "" -"Typical ACPI events are closing the lid, changing the power source or " -"pressing the sleep button. An important event is changing the power source, " -"which should cause a runlevel switch. A small script will take care of it." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):285 -msgid "" -"First you need a script which changes the runlevel to <c>default</c> " -"respectively <c>battery</c> depending on the power source. The script uses " -"the <c>on_ac_power</c> command from <c>sys-power/pm-utils</c> - make sure " -"the package is installed on your system." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):292 -msgid "Installing pm-utils" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):292 -#, no-wrap -msgid "" -"\n" -"# <i>emerge pm-utils</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):296 -msgid "" -"You are now able to determine the power source by executing <c>on_ac_power " -"&& echo AC available || echo Running on batteries</c> in a shell. " -"The script below is responsible for changing runlevels. Save it as <path>/" -"etc/acpi/actions/pmg_switch_runlevel.sh</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):303 -msgid "/etc/acpi/actions/pmg_switch_runlevel.sh" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):303 -#, no-wrap -msgid "" -"\n" -"#!/bin/bash\n" -"\n" -"# BEGIN configuration\n" -"RUNLEVEL_AC=\"default\"\n" -"RUNLEVEL_BATTERY=\"battery\"\n" -"\n" -"if [ -x /usr/bin/logger ]; then\n" -" LOGGER=\"/usr/bin/logger -s -p daemon.info -t /etc/acpi/actions/pmg_switch_runlevel.sh\"\n" -"else\n" -" LOGGER=\"/bin/echo\"\n" -"fi\n" -"\n" -"ON_AC_POWER=/usr/bin/on_ac_power\n" -"# END configuration\n" -"\n" -"\n" -"if [ ! -d \"/etc/runlevels/${RUNLEVEL_AC}\" ]\n" -"then\n" -" ${LOGGER} \"${0}: Runlevel ${RUNLEVEL_AC} does not exist. Aborting.\"\n" -" exit 1\n" -"fi\n" -"\n" -"if [ ! -d \"/etc/runlevels/${RUNLEVEL_BATTERY}\" ]\n" -"then\n" -" ${LOGGER} \"${0}: Runlevel ${RUNLEVEL_BATTERY} does not exist. Aborting.\"\n" -" exit 1\n" -"fi\n" -"\n" -"if ${on_ac_power}\n" -"then\n" -" if [[ \"$(rc-status --runlevel)\" != \"${RUNLEVEL_AC}\" ]]\n" -" then\n" -" ${LOGGER} \"Switching to ${RUNLEVEL_AC} runlevel\"\n" -" /sbin/rc ${RUNLEVEL_AC}\n" -" fi\n" -"elif [[ \"$(rc-status --runlevel)\" != \"${RUNLEVEL_BATTERY}\" ]]\n" -"then\n" -" ${LOGGER} \"Switching to ${RUNLEVEL_BATTERY} runlevel\"\n" -" /sbin/rc ${RUNLEVEL_BATTERY}\n" -"fi\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):346 -msgid "" -"Dont forget to run <c>chmod +x /etc/acpi/actions/pmg_switch_runlevel.sh</c> " -"to make the script executable. The last thing that needs to be done is " -"calling the script whenever the power source changes. That's done by " -"catching ACPI events with the help of <c>acpid</c>. First you need to know " -"which events are generated when the power source changes. The events are " -"called <c>ac_adapter</c> and <c>battery</c> on most laptops, but it might be " -"different on yours." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):356 -msgid "Determining ACPI events for changing the power source" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):356 -#, no-wrap -msgid "" -"\n" -"# <i>tail -f /var/log/messages | grep \"ACPI event\"</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):360 -msgid "" -"Run the command above and pull the power cable. You should see something " -"like this:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):365 -msgid "Sample output for power source changes" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):365 -#, no-wrap -msgid "" -"\n" -"[Tue Sep 20 17:39:06 2005] ACPI event \"ac_adapter AC 00000080 00000000\"\n" -"[Tue Sep 20 17:39:06 2005] ACPI event \"battery BAT0 00000080 00000001\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):370 -msgid "" -"The interesting part is the quoted string after <c>ACPI event</c>. It will " -"be matched by the event line in the files you are going to create below. " -"Don't worry if your system generates multiple events or always the same. As " -"long as any event is generated, runlevel changing will work." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):377 -msgid "/etc/acpi/events/pmg_ac_adapter" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):377 -#, no-wrap -msgid "" -"\n" -"<comment># replace \"ac_adapter\" below with the event generated on your laptop</comment>\n" -"<comment># For example, ac_adapter.* will match ac_adapter AC 00000080 00000000</comment>\n" -"event=ac_adapter.*\n" -"action=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):384 -msgid "/etc/acpi/events/pmg_battery" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):384 -#, no-wrap -msgid "" -"\n" -"<comment># replace \"battery\" below with the event generated on your laptop</comment>\n" -"<comment># For example, battery.* will match battery BAT0 00000080 00000001</comment>\n" -"event=battery.*\n" -"action=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):391 -msgid "Finally acpid has to be restarted to recognize the changes." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):395 -msgid "Finishing runlevel switching with acpid" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):395 -#, no-wrap -msgid "" -"\n" -"# <i>/etc/init.d/acpid restart</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):399 -msgid "" -"Give it a try: Plug AC in and out and watch syslog for the \"Switching to AC " -"mode\" or \"Switching to battery mode\" messages. See the <uri link=" -"\"#doc_chap8\">Troubleshooting section</uri> if the script is not able to " -"detect the power source correctly." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):406 -msgid "" -"Due to the nature of the event mechanism, your laptop will boot into " -"runlevel <c>default</c> regardless of the AC/battery state. This is fine " -"when running from AC, but we'd like to boot into the battery runlevel " -"otherwise. One solution would be to add another entry to the boot loader " -"with the parameter <c>softlevel=battery</c>, but it's likely to forget " -"choosing it. A better way is faking an ACPI event in the end of the boot " -"process and letting <path>pmg_switch_runlevel.sh</path> script decide " -"whether a runlevel change is necessary. Create a <path>/etc/local.d/battery." -"start</path> file with the following contents:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):418 -msgid "Runlevel adjustment at boot time through local.d/battery.start" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):418 -#, no-wrap -msgid "" -"\n" -"#!/bin/sh\n" -"<comment># Fake acpi event to switch runlevel if running on batteries</comment>\n" -"/etc/acpi/actions/pmg_switch_runlevel.sh \"battery/battery\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):424 -msgid "" -"Don't forget to mark the file as executable (<c>chmod +x /etc/local.d/" -"battery.start</c>). Prepared like this you can activate Power Management " -"policies for individual devices." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):435 -msgid "CPU Power Management" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):439 -msgid "" -"Mobile processors can operate at different frequencies. Some allow changing " -"voltage as well. Most of the time your CPU doesn't need to run at full speed " -"and scaling it down will save much energy - often without any performance " -"decrease." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):449 -msgid "Some Technical Terms" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):452 -msgid "" -"CPU frequency scaling brings up some technical terms that might be unknown " -"to you. Here's a quick introduction." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):457 -msgid "" -"First of all, the kernel has to be able to change the processor's frequency. " -"The <b>CPUfreq processor driver</b> knows the commands to do it on your CPU. " -"Thus it's important to choose the right one in your kernel. You should " -"already have done it above. Once the kernel knows how to change frequencies, " -"it has to know which frequency it should set. This is done according to the " -"<b>policy</b> which consists of a <b>CPUfreq policy</b> and a <b>governor</" -"b>. A CPUfreq policy are just two numbers which define a range the frequency " -"has to stay between - minimal and maximal frequency. The governor now " -"decides which of the available frequencies in between minimal and maximal " -"frequency to choose. For example, the <b>powersave governor</b> always " -"chooses the lowest frequency available, the <b>performance governor</b> the " -"highest one. The <b>userspace governor</b> makes no decision but chooses " -"whatever the user (or a program in userspace) wants - which means it reads " -"the frequency from <path>/sys/devices/system/cpu/cpu0/cpufreq/" -"scaling_setspeed</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):474 -msgid "" -"This doesn't sound like dynamic frequency changes yet and in fact it isn't. " -"Dynamics however can be accomplished with various approaches. For example, " -"the <b>ondemand governor</b> makes its decisions depending on the current " -"CPU load. The same is done by various userland tools like <c>cpudyn</c>, " -"<c>cpufreqd</c>, <c>powernowd</c> and many more. ACPI events can be used to " -"enable or disable dynamic frequency changes depending on power source." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):486 -msgid "Setting The Frequency" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):489 -msgid "" -"Decreasing CPU speed and voltage has two advantages: On the one hand less " -"energy is consumed, on the other hand there is thermal improvement as your " -"system doesn't get as hot as running on full speed. The main disadvantage is " -"obviously the loss of performance. Decreasing processor speed is a trade off " -"between performance loss and energy saving." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):497 -msgid "" -"Not every laptop supports frequency scaling. If unsure, have a look at the " -"list of supported processors in the <uri link=" -"\"#doc_chap8\">Troubleshooting</uri> section to verify yours is supported." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):503 -msgid "" -"It's time to test whether CPU frequency changing works. Let's install " -"another tool: <c>sys-power/cpufrequtils</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):508 -msgid "Checking CPU frequency" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):508 -#, no-wrap -msgid "" -"\n" -"# <i>emerge cpufrequtils</i>\n" -"# <i>cpufreq-info</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):513 -msgid "Here is an example output:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):517 -msgid "Sample output from cpufreq-info" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):517 -#, no-wrap -msgid "" -"\n" -"cpufrequtils 0.3: cpufreq-info (C) Dominik Brodowski 2004\n" -"Report errors and bugs to linux@brodo.de, please.\n" -"analyzing CPU 0:\n" -" driver: centrino\n" -" CPUs which need to switch frequency at the same time: 0\n" -" hardware limits: 600 MHz - 1.40 GHz\n" -" available frequency steps: 600 MHz, 800 MHz, 1000 MHz, 1.20 GHz, 1.40 GHz\n" -" available cpufreq governors: conservative, ondemand, powersave, userspace, performance\n" -" current policy: frequency should be within 924 MHz and 1.40 GHz.\n" -" The governor \"performance\" may decide which speed to use\n" -" within this range.\n" -" current CPU frequency is 1.40 GHz.\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):532 -msgid "" -"Now play around with <c>cpufreq-set</c> to make sure frequency switching " -"works. Run <c>cpufreq-set -g ondemand</c> for example to activate the " -"ondemand governor and verify the change with <c>cpufreq-info</c>. If it " -"doesn't work as expected, you might find help in the <uri link=" -"\"#doc_chap8\">Troubleshooting section</uri> in the end of this guide." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):540 -msgid "" -"<c>cpufrequtils</c> can operate in an automatic mode (when you use the " -"<b>ondemand</b> governor), you can also switch to the <b>userspace</b> " -"governor if you want to manually set a specific speed. You can also " -"statically set your CPU to its highest or lowest frequency by using the " -"<b>performance</b> and <b>powersave</b> governors, respectively." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):548 -msgid "Changing CPU speeds" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):548 -#, no-wrap -msgid "" -"\n" -"<comment>(Set the highest available frequency)</comment>\n" -"# <i>cpufreq-set -g performance</i>\n" -"<comment>(Set the lowest available frequency)</comment>\n" -"# <i>cpufreq-set -g powersave</i>\n" -"<comment>(Set a specific frequency)</comment>\n" -"# <i>cpufreq-set -g userspace</i>\n" -"# <i>cpufreq-set -f 2.00ghz</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):561 -msgid "Other CPU Speed Utilities" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):564 -msgid "" -"While <c>cpufrequtils</c> may be the best all-around program, there are some " -"other choices available in Portage. The following table gives a quick " -"overview of available CPU speed utilities. It's roughly separated in three " -"categories <b>kernel</b> for approaches that only need kernel support, " -"<b>daemon</b> for programs that run in the background and <b>graphical</b> " -"for programs that provide a GUI for easy configuration and changes." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):575 -msgid "Name" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):576 -msgid "Category" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):577 -msgid "Switch decision" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):578 -msgid "Kernel governors" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):579 -msgid "Further governors" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):580 -msgid "Comments" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):583 -msgid "'ondemand' governor" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):584 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):598 -msgid "Kernel" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):585 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):599 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):614 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):640 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):664 -msgid "CPU load" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):586 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):587 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):600 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):601 -msgid "N.A." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):588 -msgid "" -"Chooses maximal frequency on CPU load and slowly steps down when the CPU is " -"idle. Further tuning through files in <path>/sys/devices/system/cpu/cpu0/" -"cpufreq/ondemand/</path>. Still requires userland tools (programs, scripts) " -"if governor switching or similar is desired." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):597 -msgid "'conservative' governor" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):602 -msgid "" -"Unlike the ondemand governor, conversative doesn't jump to maximum frequency " -"when CPU load is high, but increases the frequency step by step. Further " -"tuning through files in <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/" -"</path>. Still requires userland tools (programs, scripts) if governor " -"switching or similar is desired." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):612 -msgid "http://mnm.uib.es/~gallir/cpudyn/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):612 -msgid "cpudyn" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):613 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):624 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):639 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):652 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):663 -msgid "Daemon" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):615 -msgid "Performance, powersave" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):616 -msgid "Dynamic" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):617 -msgid "" -"Also supports disk standby - notice however that <e>laptop mode</e> in most " -"cases will do a better job." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):623 -msgid "http://sourceforge.net/projects/cpufreqd/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):623 -msgid "cpufreqd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):625 -msgid "Battery state, CPU load, temperature, running programs and more" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):626 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):688 -msgid "All available" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):627 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):641 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):654 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):665 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):676 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):677 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):678 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):689 -msgid "None" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):628 -msgid "" -"Sophisticated (but somewhat complicated) setup. Extendible through plugins " -"like sensor monitoring (lm_sensors) or coordinating some NVidia based " -"graphics card memory and core. Cpufreqd is SMP aware and can optionally be " -"controlled manually at runtime." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):637 -msgid "http://www.deater.net/john/powernowd.html" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):637 -msgid "powernowd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):642 -msgid "Passive, sine, aggressive" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):643 -msgid "Supports SMP." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):650 -msgid "http://projects.simpledesigns.com.pl/project/ncpufreqd/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):650 -msgid "ncpufreqd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):653 -msgid "Temperature" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):655 -msgid "Powersave, performance" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):656 -msgid "" -"Toggles the used governor between performance and powersave depending on " -"system temperature. Very useful on laptops with notorious heat problems." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):662 -msgid "http://www.goop.org/~jeremy/speedfreq/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):662 -msgid "speedfreq" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):666 -msgid "Dynamic, powersave, performance, fixed speed" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):667 -msgid "" -"Easy to configure with a nice client/server interface. Requires a 2.6 " -"kernel. Unmaintained, broken and thus removed from Portage. Please switch to " -"cpufreqd if you're still using it." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):674 -msgid "http://cpuspeedy.sourceforge.net/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):674 -msgid "gtk-cpuspeedy" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):675 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):686 -msgid "Graphical" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):679 -msgid "" -"Gnome application, a graphical tool to set CPU frequency manually. It does " -"not offer any automation." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):685 -msgid "klaptopdaemon" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):687 -msgid "Battery state" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):690 -msgid "KDE only, 'ondemand' governor required for dynamic frequency scaling." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):696 -msgid "" -"While adjusting the frequency to the current load looks simple at a first " -"glance, it's not such a trivial task. A bad algorithm can cause switching " -"between two frequencies all the time or wasting energy when setting " -"frequency to an unnecessary high level." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):703 -msgid "Which one to choose? If you have no idea about it, try <c>cpufreqd</c>:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):707 -msgid "Installing cpufreqd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):707 -#, no-wrap -msgid "" -"\n" -"# <i>emerge cpufreqd</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):711 -msgid "" -"<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</" -"path>. The default one that ships with cpufreqd may look a bit confusing. I " -"recommend replacing it with the one from former Gentoo developer Henrik Brix " -"Andersen (see below). Please notice that you need cpufreqd-2.0.0 or later. " -"Earlier versions have a different syntax for the config file." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):719 -msgid "/etc/cpufreqd.conf (cpufreqd-2.0.0 and later)" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):719 -#, no-wrap -msgid "" -"\n" -"[General]\n" -"pidfile=/var/run/cpufreqd.pid\n" -"poll_interval=3\n" -"enable_plugins=acpi_ac, acpi_battery\n" -"enable_remote=1\n" -"remote_group=wheel\n" -"verbosity=5\n" -"[/General]\n" -"\n" -"[Profile]\n" -"name=ondemand\n" -"minfreq=0%\n" -"maxfreq=100%\n" -"policy=ondemand\n" -"[/Profile]\n" -"\n" -"[Profile]\n" -"name=conservative\n" -"minfreq=0%\n" -"maxfreq=100%\n" -"policy=conservative\n" -"[/Profile]\n" -"\n" -"[Profile]\n" -"name=powersave\n" -"minfreq=0%\n" -"maxfreq=100%\n" -"policy=powersave\n" -"[/Profile]\n" -"\n" -"[Profile]\n" -"name=performance\n" -"minfreq=0%\n" -"maxfreq=100%\n" -"policy=performance\n" -"[/Profile]\n" -"\n" -"[Rule]\n" -"name=battery\n" -"ac=off\n" -"profile=conservative\n" -"[/Rule]\n" -"\n" -"[Rule]\n" -"name=battery_low\n" -"ac=off\n" -"battery_interval=0-10\n" -"profile=powersave\n" -"[/Rule]\n" -"\n" -"[Rule]\n" -"name=ac\n" -"ac=on\n" -"profile=ondemand\n" -"[/Rule]\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):777 -msgid "" -"Now you can start the cpufreqd daemon. Add it to the <c>default</c> and " -"<c>battery</c> runlevel as well." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):782 -msgid "Starting cpufreqd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):782 -#, no-wrap -msgid "" -"\n" -"# <i>rc-update add cpufreqd default battery</i>\n" -"# <i>/etc/init.d/cpufreqd start</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):787 -msgid "" -"Sometimes it can be desirable to select another policy than the daemon " -"chooses, for example when battery power is low, but you know that AC will be " -"available soon. In that case you can turn on cpufreqd's manual mode with " -"<c>cpufreqd-set manual</c> and select one of your configured policies (as " -"listed by <c>cpufreqd-get</c>). You can leave manual mode by executing " -"<c>cpufreqd-set dynamic</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):796 -msgid "" -"Do not run more than one of the above programs at the same time. It may " -"cause confusion like switching between two frequencies all the time." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):804 -msgid "Verifying the result" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):807 -msgid "" -"The last thing to check is that your new policies do a good job. An easy way " -"to do so is monitoring CPU speed while working with your laptop:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):812 -msgid "Monitoring CPU speed" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):812 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):118 msgid "" -"\n" -"# <i>watch grep \\\"cpu MHz\\\" /proc/cpuinfo</i>\n" +"Don't forget to enable the CPU frequency scaling driver for your CPU, " +"located right after the <e>ACPI Processor P-States driver</e> mentioned " +"above." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):816 -msgid "" -"If <path>/proc/cpuinfo</path> doesn't get updated (see <uri link=" -"\"#doc_chap8\">Troubleshooting</uri>), monitor the CPU frequency with <c>sys-" -"apps/x86info</c>:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):123 +msgid "Build and install the new kernel (if necessary) and reboot." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):822 -msgid "Alternative CPU speed monitoring" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):169 +msgid "Using Laptop Mode Tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):822 -#, no-wrap -msgid "" -"\n" -"# <i>watch x86info -mhz</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):171 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):469 +msgid "Installation" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):826 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):174 msgid "" -"Depending on your setup, CPU speed should increase on heavy load, decrease " -"on no activity or just stay at the same level. When using <c>cpufreqd</c> " -"and verbosity set to 5 or higher in <path>cpufreqd.conf</path> you'll get " -"additional information about what's happening reported to <c>syslog</c>." +"It comes to no surprise that installation of the <e>Laptop Mode Tools</e> " +"software is easily done through <c>emerge laptop-mode-tools</c>. However, " +"this package takes on additional, optional settings through USE flag " +"configuration. So let's first take a look at the supported USE flags and " +"what they mean to the package." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):838 -msgid "LCD Power Management" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):184 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):481 +msgid "USE flag" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):842 -msgid "" -"As you can see in <uri link=\"#doc_chap1_fig1\">figure 1.1</uri>, the LCD " -"display consumes the biggest part of energy (might not be the case for non-" -"mobile CPU's). Thus it's quite important not only to shut the display off " -"when not needed, but also to reduce it's backlight if possible. Most laptops " -"offer the possibility to control the backlight dimming." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):185 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):482 +msgid "Description" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):853 -msgid "Standby settings" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):186 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):483 +msgid "Suggested when..." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):856 -msgid "" -"The first thing to check is the standby/suspend/off timings of the display. " -"As this depends heavily on your windowmanager, I'll let you figure it out " -"yourself. Just two common places: Blanking the terminal can be done with " -"<c>setterm -blank <number-of-minutesM></c>, <c>setterm -powersave on</" -"c> and <c>setterm -powerdown <number-of-minutesM></c>. For X.org, " -"modify <path>/etc/X11/xorg.conf</path> similar to this:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):189 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):486 +msgid "acpi" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):865 -msgid "LCD suspend settings in X.org" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):865 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):190 msgid "" -"\n" -"Section \"ServerFlags\"\n" -" Option \"blank time\" \"5\" <comment># Blank the screen after 5 minutes (Fake)</comment>\n" -" Option \"standby time\" \"10\" <comment># Turn off screen after 10 minutes (DPMS)</comment>\n" -" Option \"suspend time\" \"20\" <comment># Full suspend after 20 minutes</comment>\n" -" Option \"off time\" \"30\" <comment># Turn off after half an hour</comment>\n" -" [...]\n" -"EndSection\n" -"\n" -"[...]\n" -"\n" -"Section \"Monitor\"\n" -" Identifier [...]\n" -" Option \"DPMS\"\n" -" [...]\n" -"EndSection\n" +"Depend on <c>sys-power/acpid</c> so that changes in the system are captured " +"and power saving features are automatically enabled/disabled." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):886 -msgid "Backlight dimming" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):194 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):491 +msgid "your laptop is not too old (~ year 2003 and later)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):889 -msgid "" -"Probably more important is the backlight dimming. If you have access to the " -"dimming settings via a tool, write a small script that dims the backlight in " -"battery mode and place it in your <c>battery</c> runlevel. The following " -"script should work on most IBM Thinkpads and Toshiba laptops. You've got to " -"enable the appropriate option in your kernel (IBM Thinkpads only). For " -"Toshiba laptops, install <c>sys-power/acpitool</c> and skip configuration of " -"<c>thinkpad_acpi</c> (formerly called <c>ibm_acpi</c>) as described below." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):197 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):494 +msgid "apm" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):899 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):198 msgid "" -"Support for setting brightness is marked experimental in thinkpad_acpi. It " -"accesses hardware directly and may cause severe harm to your system. Please " -"read the <uri link=\"http://ibm-acpi.sourceforge.net/\">thinkpad_acpi " -"website</uri>" +"Depend on <c>sys-apps/apmd</c> so that changes in the system are captured " +"and power saving features are automatically enabled/disabled." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):906 -msgid "" -"To be able to set the brightness level, the thinkpad_acpi module has to be " -"loaded with the experimental parameter." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):202 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):499 +msgid "your laptop is very old" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):911 -msgid "Automatically loading the thinkpad_acpi module" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):205 +msgid "bluetooth" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):911 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):206 msgid "" -"\n" -"<comment>(Please read the warnings above before doing this!)</comment>\n" -"\n" -"# <i>echo \"options thinkpad_acpi experimental=1\" >> /etc/modprobe.d/thinkpad_acpi</i>\n" -"# <i>update-modules</i>\n" -"# <i>nano /etc/conf.d/modules</i>\n" -"<comment># Autoload the thinkpad_acpi module</comment>\n" -"modules_2_6=\"thinkpad_acpi\"\n" -"<comment># Parameters for the thinkpad_acpi module</comment>\n" -"modules_thinkpad_acpi_args_2_6=\"experimental=1\"\n" -"\n" -"# <i>modprobe thinkpad_acpi</i>\n" +"Depend on <c>net-wireless/bluez</c>, enabling the <c>laptop-mode-tools</c> " +"to manage bluetooth settings (enabling/disabling the service based on " +"battery availability)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):925 -msgid "" -"This should work without error messages and a file <path>/proc/acpi/ibm/" -"brightness</path> should be created after loading the module. An init script " -"will take care of choosing the brightness according to the power source." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):211 +msgid "your laptop (and kernel) supports bluetooth" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):932 -msgid "/etc/conf.d/lcd-brightness" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):214 +msgid "scsi" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):932 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):215 msgid "" -"\n" -"<comment># See /proc/acpi/ibm/brightness for available values</comment>\n" -"<comment># Please read /usr/src/linux/Documentation/thinkpad-acpi.txt</comment>\n" -"\n" -"<comment># brightness level in ac mode. Default is 7.</comment>\n" -"BRIGHTNESS_AC=7\n" -"\n" -"<comment># brightness level in battery mode. Default is 4.</comment>\n" -"BRIGHTNESS_BATTERY=4\n" +"Depend on <c>sys-apps/sdparm</c>, enabling the <c>laptop-mode-tools</c> to " +"manage SCSI (<e>and not</e> SATA) disk parameters." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):943 -msgid "/etc/init.d/lcd-brightness" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):219 +msgid "your laptop uses SCSI disks" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):943 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):223 msgid "" -"\n" -"#!/sbin/runscript\n" -"\n" -"set_brightness() {\n" -" if on_ac_power\n" -" then\n" -" LEVEL=${BRIGHTNESS_AC:-7}\n" -" else\n" -" LEVEL=${BRIGHTNESS_BATTERY:-4}\n" -" fi\n" -"\n" -" if [ -f /proc/acpi/ibm/brightness ]\n" -" then\n" -" ebegin \"Setting LCD brightness\"\n" -" echo \"level ${LEVEL}\" > /proc/acpi/ibm/brightness\n" -" eend $?\n" -" elif [[ -e /usr/bin/acpitool && -n $(acpitool -T | grep \"LCD brightness\") ]]\n" -" then\n" -" ebegin \"Setting LCD brightness\"\n" -" acpitool -l $LEVEL >/dev/null || ewarn \"Unable to set lcd brightness\"\n" -" eend $?\n" -" else\n" -" ewarn \"Setting LCD brightness is not supported.\"\n" -" ewarn \"For IBM Thinkpads, check that thinkpad_acpi is loaded into the kernel\"\n" -" ewarn \"For Toshiba laptops, you've got to install sys-power/acpitool\"\n" -" fi\n" -"}\n" -"\n" -"start() {\n" -" set_brightness\n" -"}\n" -"\n" -"stop () {\n" -" set_brightness\n" -"}\n" +"As you can see, there are two USE flags that seem to collide: <c>acpi</c> " +"and <c>apm</c>. So what's the deal there?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):980 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):229 msgid "" -"When done, make sure brightness is adjusted automatically by adding it to " -"the battery runlevel." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):985 -msgid "Enabling automatic brightness adjustment" +"The <c>apm</c> USE flag enables support for <e>Advanced Power Management</" +"e>, an older (before year 2000) standard for power management features " +"within a system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):985 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):234 msgid "" -"\n" -"# <i>chmod +x /etc/init.d/lcd-brightness</i>\n" -"# <i>rc-update add lcd-brightness battery</i>\n" -"# <i>rc</i>\n" +"The <c>acpi</c> USE flag enables support for <e>Advanced Configuration and " +"Power Interface</e>, the successor of APM. All modern laptops support ACPI." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):996 -msgid "Disk Power Management" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1000 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):240 msgid "" -"Hard disks consume less energy in sleep mode. Therefore it makes sense to " -"activate power saving features whenever the hard disk is not used for a " -"certain amount of time. I'll show you two alternative possibilities to do " -"it. First, laptop-mode will save most energy due to several measures which " -"prevent or at least delay write accesses. The drawback is that due to the " -"delayed write accesses a power outage or kernel crash will be more dangerous " -"for data loss. If you don't like this, you have to make sure that there are " -"no processes which write to your hard disk frequently. Afterwards you can " -"enable power saving features of your hard disk with <c>hdparm</c> as the " -"second alternative." +"Depending on your system, you will either need <c>acpi</c> or <c>apm</c> " +"set. In the remainder of this guide, we assume that your laptop is recent " +"enough to use ACPI." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1015 -msgid "Increasing idle time - laptop-mode" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):246 +msgid "So, with the USE flags set, let's install <c>laptop-mode-tools</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1018 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):250 msgid "" -"Recent 2.6 kernels include the so-called <c>laptop-mode</c>. When activated, " -"dirty buffers are written to disk on read calls or after 10 minutes (instead " -"of 30 seconds). This minimizes the time the hard disk needs to be spun up." +"If you have USE=\"acpi\" set, the installation will pull in <c>acpid</c>. " +"However, the current stable ACPI daemon (2.0.9) does not support the new " +"ACPI interfaces within the Linux kernel (using the netlink interface). As " +"such, we recommend unmasking <c>sys-power/acpid-2.0.12</c> (or higher). For " +"more information about unmasking packages, please read <uri link=\"/doc/en/" +"handbook/handbook-amd64.xml?part=3&chap=3\">Mixing Software Branches</" +"uri> in the Gentoo Handbook." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1024 -msgid "Automated start of laptop-mode" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):260 +msgid "Installing laptop-mode-tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1024 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):260 #, no-wrap msgid "" "\n" "# <i>emerge laptop-mode-tools</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1028 -msgid "" -"<c>laptop-mode-tools</c> has its configuration file in <path>/etc/laptop-" -"mode/laptop-mode.conf</path>. Adjust it the way you like it, it's well " -"commented. Run <c>rc-update add laptop_mode battery</c> to start it " -"automatically." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):267 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):564 +msgid "Configuration" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1035 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):270 msgid "" -"Recent versions (1.11 and later) of laptop-mode-tools include a new tool " -"<c>lm-profiler</c>. It will monitor your system's disk usage and running " -"network services and suggests to disable unneeded ones. You can either " -"disable them through laptop-mode-tools builtin runlevel support (which will " -"be reverted by Gentoo's <c>/sbin/rc</c>) or use your <c>default</c>/" -"<c>battery</c> runlevels (recommended)." +"Having <c>laptop-mode-tools</c> installed on your system does not " +"automatically enable the power management features that you might need. To " +"configure the package, first take a look at <path>/etc/laptop-mode/laptop-" +"mode.conf</path>. This is the main configuration file for the package and is " +"pretty well described (through comments)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1044 -msgid "Sample output from running lm-profiler" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1044 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):278 msgid "" -"\n" -"# <i>lm-profiler</i>\n" -"Profiling session started.\n" -"Time remaining: 600 seconds\n" -"[4296896.602000] amarokapp\n" -"Time remaining: 599 seconds\n" -"[4296897.714000] sort\n" -"[4296897.970000] mv\n" -"Time remaining: 598 seconds\n" -"Time remaining: 597 seconds\n" -"[4296900.482000] reiserfs/0\n" +"But it is not the only configuration file to work with. The Laptop Mode " +"Tools package supports plugins (or modules) which have their own " +"configuration file(s). These files are located in <path>/etc/laptop-mode/" +"conf.d</path> and are named after the module they represent (such as " +"<path>intel-sata-powermgmt.conf</path>)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1057 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):286 msgid "" -"After profiling your system for ten minutes, lm-profiler will present a list " -"of services which might have caused disk accesses during that time." +"Now, one of the important settings in each configuration file is if the " +"Laptop Mode Tools package should govern a particular setting or not. This is " +"important when you want to combine <c>laptop-mode-tools</c> with other " +"services like <c>cpufreqd</c>. In this example case, you will need to set " +"<c>CONTROL_CPU_FREQUENCY=0</c>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1062 -msgid "lm-profiler suggests to disable some services" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):294 +msgid "Editing /etc/laptop-mode/conf.d/cpufreq.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1062 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):294 #, no-wrap msgid "" "\n" -"Program: \"atd\"\n" -"Reason: standard recommendation (program may not be running)\n" -"Init script: /etc/init.d/atd (GUESSED)\n" -"\n" -"Do you want to disable this service in battery mode? [y/N]: <i>n</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1070 -msgid "" -"To disable atd as suggested in the example above, you would run <c>rc-update " -"del atd battery</c>. Be careful not to disable services that are needed for " -"your system to run properly - <c>lm-profiler</c> is likely to generate some " -"false positives. Do not disable a service if you are unsure whether it's " -"needed." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1081 -msgid "Limiting Write Accesses" +"# <i>nano -w /etc/laptop-mode/conf.d/cpufreq.conf</i>\n" +"CONTROL_CPU_FREQUENCY=<i>0</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1084 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):299 msgid "" -"If you don't want to use laptop-mode, you must take special care to disable " -"services that write to your disk frequently - <c>syslogd</c> is a good " -"candidate, for example. You probably don't want to shut it down completely, " -"but it's possible to modify the config file so that \"unnecessary\" things " -"don't get logged and thus don't create disk traffic. <c>Cups</c> writes to " -"disk periodically, so consider shutting it down and only enable it manually " -"when needed." +"The next few sections will help you configure <c>laptop-mode-tools</c> to " +"suit your needs. When you are finished, start the <c>laptop_mode</c> service " +"and make sure it is started when you boot up your system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1094 -msgid "Disabling cups in battery mode" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):305 +msgid "Starting the laptop_mode service" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1094 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):305 #, no-wrap msgid "" "\n" -"# <i>rc-update del cupsd battery</i>\n" +"# <i>/etc/init.d/laptop_mode start</i>\n" +"# <i>rc-update add laptop_mode default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1098 -msgid "" -"You can also use <c>lm-profiler</c> from laptop-mode-tools (see above) to " -"find services to disable. Once you eliminated all of them, go on with " -"configuring hdparm." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1107 -msgid "hdparm" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):313 +msgid "How does laptop-mode-tools work" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1110 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):316 msgid "" -"The second possibility is using <c>hdparm</c>. Skip this if you are using " -"laptop-mode. Otherwise, edit <path>/etc/conf.d/hdparm</path> and add the " -"following values to your drive entries. This example assumes your hard drive " -"is called <b>hda</b>:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1117 -msgid "Using /etc/conf.d/hdparm for disk standby" +"When running the <c>laptop_mode</c> service, the software will check in " +"which state your system is in. The states are defined as:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1117 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):322 msgid "" -"\n" -"hda_args=\"-q -S12\"\n" +"<e>Battery</e>, in the configuration files using the <c>BATT_</c> prefix, is " +"active when the system is running on battery power" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1121 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):326 msgid "" -"This will activate power management for your hard drive. If you ever want to " -"deactivate power management, you can edit <path>/etc/conf.d/hdparm</path> " -"and change the values to <c>-q -S0</c>, or just run <c>hdparm -q -S0 /dev/" -"hda</c>." +"<e>AC</e>, in the configuration files using the <c>AC_</c> prefix, is active " +"when the system is running on AC power" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1127 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):330 msgid "" -"See <c>man hdparm</c> for the options. Though you can always start " -"<c>hdparm</c> manually when you are on battery power by running <c>/etc/init." -"d/hdparm start</c>, it's much easier to automate its startup and shutdown. " -"To do so, add <c>hdparm</c> to the battery runlevel so that it will " -"automatically enable power management." +"<e>Laptop Mode</e>, in the configuration files using the <c>LM_</c> prefix, " +"is active when <e>laptop mode</e> is enabled" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1135 -msgid "Automate disk standby settings" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1135 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):334 msgid "" -"\n" -"# <i>rc-update add hdparm battery</i>\n" +"<e>No Laptop Mode</e>, in the configuration files using the <c>NOLM_</c> " +"prefix, is active when <e>laptop mode</e> is disabled" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(impo):1139 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):340 msgid "" -"Be careful with sleep/spin down settings of your hard drive. Setting it to " -"small values might wear out your drive and lose warranty." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1147 -msgid "Other tricks" +"The <c>AC/BATT_</c> and <c>LM/NOLM_</c> prefixes can be combined (so you can " +"have a <c>AC_LM_</c> prefix)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1150 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):345 msgid "" -"Another possibility is to deactivate swap in battery mode. Before writing a " -"swapon/swapoff switcher, make sure there is enough RAM and swap isn't used " -"heavily, otherwise you'll be in big problems." +"When the <c>laptop_mode</c> service is started, it will switch modes based " +"on events that occur (and of course based on the configuration settings). " +"For instance, the setting <c>ENABLE_LAPTOP_MODE_ON_BATTERY=1</c> will make " +"sure that the laptop mode tools switch to <e>laptop mode</e> when battery " +"power is used. If that is the case, then the settings starting with <c>LM_</" +"c>, <c>LM_BATT_</c>, <c>BATT_LM_</c> and <c>BATT_</c> will be used." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1156 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):354 msgid "" -"If you don't want to use laptop-mode, it's still possible to minimize disk " -"access by mounting certain directories as <c>tmpfs</c> - write accesses are " -"not stored on a disk, but in main memory and get lost with unmounting. Often " -"it's useful to mount <path>/tmp</path> like this - you don't have to pay " -"special attention as it gets cleared on every reboot regardless whether it " -"was mounted on disk or in RAM. Just make sure you have enough RAM and no " -"program (like a download client or compress utility) needs extraordinary " -"much space in <path>/tmp</path>. To activate this, enable tmpfs support in " -"your kernel and add a line to <path>/etc/fstab</path> like this:" +"To make sure settings to not collide, it is not allowed to have overlapping " +"settigns. In the next example, the first set (for <c>CPU_MAXFREQ</c>) is " +"valid, but the second one (for <c>CPU_GOVERNOR</c>) isn't." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1168 -msgid "Editing /etc/fstab to make /tmp even more volatile" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):360 +msgid "Colliding settings" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1168 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):360 #, no-wrap msgid "" "\n" -"none /tmp tmpfs size=32m 0 0\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1172 -msgid "" -"Pay attention to the size parameter and modify it for your system. If you're " -"unsure, don't try this at all, it can become a performance bottleneck " -"easily. In case you want to mount <path>/var/log</path> like this, make sure " -"to merge the log files to disk before unmounting. They are essential. Don't " -"attempt to mount <path>/var/tmp</path> like this. Portage uses it for " -"compiling..." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1185 -msgid "Power Management For Other Devices" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1187 -msgid "Graphics Cards" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1190 -msgid "" -"In case you own an ATI graphics card supporting PowerPlay (dynamic clock " -"scaling for the graphics processing unit GPU), you can activate this feature " -"in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable) the " -"<c>DynamicClocks</c> option in the Device section. Please notice that this " -"feature will lead to crashes on some systems." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1198 -msgid "Enabling ATI PowerPlay support in X.org" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1198 -#, no-wrap -msgid "" +"<comment>## Valid set</comment>\n" +"BATT_CPU_MAXFREQ=fastest\n" +"LM_AC_CPU_MAXFREQ=fastest\n" +"NOLM_AC_CPU_MAXFREQ=fastest\n" "\n" -"Section \"Device\"\n" -"[...]\n" -"Option \"DynamicClocks\" \"on\"\n" -"EndSection\n" +"<comment>## Invalid set</comment>\n" +"BATT_CPU_MINFREQ=fastest\n" +"LM_AC_CPU_MINFREQ=fastest\n" +"<comment># The following includes AC and BATT, but BATT is already defined</comment>\n" +"NOLM_CPU_MINFREQ=fastest\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1208 -msgid "Wireless Power Management" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):376 +msgid "Configuring CPU frequency management" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1211 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):379 msgid "" -"Wireless LAN cards consume quite a bit of energy. Put them in Power " -"Management mode just like your hard drives." +"The support for CPU frequency management in the laptop mode tools allows " +"switching frequencies. It supports setting the CPU frequency governor, " +"minimum frequency and maximum frequency. The configuration file used here is " +"<path>/etc/laptop-mode/conf.d/cpufreq.conf</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1216 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):386 msgid "" -"This script assumes your wireless interface is called <c>wlan0</c>; replace " -"this with the actual name of your interface." +"The <e>CPU frequency governor</e> is a kernel-level policy that defines how " +"the kernel will select the CPU frequency. We already selected the governors " +"we want to use in the kernel configuration earlier. Let's recap:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1221 -msgid "" -"Add the following option to <path>/etc/conf.d/net</path> to automatically " -"enable power management for your wireless card:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):393 +msgid "<c>performance</c> always picks the highest frequency" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1226 -msgid "Automated WLAN Power Management" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):396 +msgid "<c>powersave</c> always picks the lowest frequency" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1226 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):399 msgid "" -"\n" -"iwconfig_wlan0=\"power on\"\n" +"<c>userspace</c> does not pick anything, but let the user decide (or any " +"process that the user is running that will decide for the user)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1230 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):403 msgid "" -"See <c>man iwconfig</c> for details and more options like the period between " -"wakeups or timeout settings. If your driver and access point support " -"changing the beacon time, this is a good starting point to save even more " -"energy." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1239 -msgid "USB Power Management" +"<c>ondemand</c> will scale the CPU frequency up to the highest frequency " +"when load is available" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1242 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):407 msgid "" -"There are two problems with USB devices regarding energy consumption: First, " -"devices like USB mice, digital cameras or USB sticks consume energy while " -"plugged in. You cannot avoid this (nevertheless remove them in case they're " -"not needed). Second, when there are USB devices plugged in, the USB host " -"controller periodically accesses the bus which in turn prevents the CPU from " -"going into sleep mode. The kernel offers an experimental option to enable " -"suspension of USB devices through driver calls or one of the <path>power/" -"state</path> files in <path>/sys</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1253 -msgid "Enabling USB suspend support in the kernel" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1253 -#, no-wrap -msgid "" -"\n" -"Device Drivers\n" -" USB support\n" -" [*] Support for Host-side USB\n" -" [*] USB suspend/resume (EXPERIMENTAL)\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1265 -msgid "Sleep States: sleep, standby, and suspend to disk" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1269 -msgid "ACPI defines different sleep states. The more important ones are" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1274 -msgid "S1 aka Standby" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1275 -msgid "S3 aka Suspend to RAM aka Sleep" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1276 -msgid "S4 aka Suspend to Disk aka Hibernate" +"<c>conservative</c> will scale the CPU frequency up gradually when load is " +"available" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1279 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):413 msgid "" -"They can be called whenever the system is not in use, but a shutdown is not " -"wanted due to the long boot time." +"When switching between AC or battery, or (no) laptop mode, the appropriate " +"governor (as well as its minimum and maximum frequency) is selected." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1287 -msgid "Sleep (S3)" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):421 +msgid "Configuring display brightness" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1290 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):424 msgid "" -"The ACPI support for these sleep states is marked experimental for good " -"reason. APM sleep states seem to be more stable, however you can't use APM " -"and ACPI together." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1296 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1390 -msgid "Kernel configuration for the various suspend types" +"With <path>/etc/laptop-mode/conf.d/lcd-brightness.conf</path>, you can have " +"the laptop mode tools govern the brightness of your LCD screen." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1296 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):429 msgid "" -"\n" -" Power Management Options --->\n" -" [*] Power Management support\n" -" [*] Suspend to RAM and standby \n" +"The file currently uses the <path>/proc/acpi/video/VID/LCD/brightness</path> " +"file to set brightness values. Recent kernels do not provide this anymore - " +"you will need to adjust this to <path>/sys/class/backlight/acpi_video0/" +"brightness</path> instead." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1302 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):436 msgid "" -"Once your kernel is properly configured, you can use the <c>hibernate-" -"script</c> to activate suspend or sleep mode. Let's install that first." +"The values you can use are between 0 and 15, with 0 being the lowest " +"brightness value." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1308 -msgid "Installing the hibernate-script" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1308 -#, no-wrap -msgid "" -"\n" -"# <i>emerge hibernate-script</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):444 +msgid "Configuring other services" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1312 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):447 msgid "" -"Some configuration has to be done in <path>/etc/hibernate</path>. The " -"default package introduces a few configuration files for each sleep state. " -"Options that are common to all suspend methods are placed in <path>common." -"conf</path>; make sure this file is properly set up for your system." +"An interesting feature of <c>laptop-mode-tools</c> is to support reloading " +"particular services (like the system logger) after switching its " +"configuration file. This is handled through <path>/etc/laptop-mode/conf.d/" +"configuration-file-control.conf</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1319 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):454 msgid "" -"To configure sleep, edit <path>sysfs-ram.conf</path> in <path>/etc/" -"hibernate</path>. <c>UseSysfsPowerState mem</c> is already setup correctly, " -"but if you need to make further changes to this particular sleep state (or " -"any other sleep state) you should add them to <path>/etc/hibernate/hibernate." -"conf</path>. The comments and option names will guide you. If you use nfs or " -"samba shares over the network, make sure to shutdown the appropriate init " -"scripts to avoid timeouts." +"If enabled, the <c>laptop_mode</c> application will switch the configuration " +"file(s) of the mentioned services with the same file, but suffixed with " +"<path>-nolm-ac</path>, <path>-lm-ac</path> or <path>-batt</path>. It willl " +"then signal or reload the appropriate services so they can use the new " +"configuration file." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1329 -msgid "" -"For more information on setting up sleep states, read <c>man hibernate.conf</" -"c>." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):467 +msgid "Using cpufreqd" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1334 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):472 msgid "" -"Ready? Now is the last chance to backup any data you want to keep after " -"executing the next command. Notice that you probably have to hit a special " -"key like <c>Fn</c> to resume from sleep." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1340 -msgid "Calling sleep" +"The <c>cpufreqd</c> application allows you to manage CPU frequencies in a " +"more granular approach then what <c>laptop-mode-tools</c> supports. But " +"before we dive into the installation of <c>cpufreqd</c>, let's first look at " +"the USE flags it supports." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1340 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):487 msgid "" -"\n" -"# <i>hibernate-ram</i>\n" +"Enable support for ACPI, allowing <c>cpufreqd</c> to be notified about " +"specific events as well as govern power through the ACPI interface" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1344 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):495 msgid "" -"If you're still reading, it seems to work. You can also setup standby (S1) " -"in a similar way by editing <path>sysfs-ram.conf</path> and changing " -"\"UseSysfsPowerState mem\" to \"UseSysfsPowerState standby\". S3 and S4 are " -"the more interesting sleep states due to greater energy savings however." +"Enable support for APM, allowing <c>cpufreqd</c> to be notified about " +"specific events as well as govern power through the APM interface" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1354 -msgid "Hibernate (S4)" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):502 +msgid "lm_sensors" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1357 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):503 msgid "" -"This section introduces hibernation, where a snapshot of the running system " -"is written to disk before powering off. On resume, the snapshot is loaded " -"and you can go on working at exactly the point you called hibernate before." +"Enable support for the Linux hardware sensors (through <c>sys-apps/" +"lm_sensors</c>), allowing to switch profiles based on hardware sensor results" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1363 -msgid "" -"Don't exchange non hot-pluggable hardware when suspended. Don't attempt to " -"load a snapshot with a different kernel image than the one it was created " -"with. Shutdown any NFS or samba server/client before hibernating." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):508 +msgid "you want to use advanced events through lm_sensors" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1369 -msgid "" -"There are two different implementations for S4. The original one is swsusp, " -"then there is the newer tuxonice (formerly suspend2) with a nicer interface " -"(including fbsplash support). A <uri link=\"http://tuxonice.net/features." -"html#compare\">feature comparison</uri> is available at the <uri link=" -"\"http://www.tuxonice.net\">tuxonice homepage</uri>. There used to be " -"Suspend-to-Disk (pmdisk), a fork of swsusp, but it has been merged back." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):513 +msgid "nforce2" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1379 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):514 msgid "" -"TuxOnIce is not included in the mainline kernel yet, therefore you either " -"have to patch your kernel sources with the patches provided by <uri link=" -"\"http://www.tuxonice.net\">tuxonice.net</uri> or use <c>sys-kernel/tuxonice-" -"sources</c>." +"Enable support for NForce, allowing <c>cpufreqd</c> to change the NForce FSB " +"clock and video card frequency" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1386 -msgid "The kernel part for both swusp and TuxOnIce is as follows:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):518 +msgid "you have an NVidia graphical card based on the NForce chipset" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1390 -#, no-wrap -msgid "" -"\n" -"Power Management support --->\n" -" <comment>(hibernate with swsusp)</comment>\n" -" [*] Hibernation (aka 'suspend to disk')\n" -" <comment>(replace /dev/SWAP with your swap partition)</comment>\n" -" (/dev/SWAP) Default resume partition\n" -"\n" -" <comment>(hibernate with TuxOnIce)</comment>\n" -" Enhanced Hibernation (TuxOnIce)\n" -" --- Image Storage (you need at least one allocator)\n" -" [*] File Allocator\n" -" [*] Swap Allocator\n" -" --- General Options\n" -" [*] Compression support\n" -" [ ] Allow Keep Image Mode\n" -" [*] Replace swsusp by default\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1408 -msgid "" -"The configuration for swsusp is rather easy. If you didn't store the " -"location of your swap partition in the kernel config, you can also pass it " -"as a parameter with the <c>resume=/dev/SWAP</c> directive. If booting is not " -"possible due to a broken image, use the <c>noresume</c> kernel parameter. " -"The <c>hibernate-cleanup</c> init script invalidates swsusp images during " -"the boot process." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1417 -msgid "Invalidating swsusp images during the boot process" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1417 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1459 -#, no-wrap -msgid "" -"\n" -"# <i>rc-update add hibernate-cleanup boot</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):523 +msgid "nvidia" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1421 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):524 msgid "" -"To activate hibernate with swsusp, use the hibernate script and set " -"<c>UseSysfsPowerState disk</c> in <path>/etc/hibernate/sysfs-disk</path>." +"Enable support for NVidia graphical card configuration (through the NVidia " +"<e>nvclock</e> interface), allowing <c>cpufreqd</c> to change the video card " +"frequency of NVidia graphical cards" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1426 -msgid "" -"Backup your data before doing this. Run <c>sync</c> before executing one of " -"the commands to have cached data written to disk. First try it outside of X, " -"then with X running, but not logged in." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1432 -msgid "" -"If you experience kernel panics due to uhci or similar, try to compile USB " -"support as module and unload the modules before sending your laptop to sleep " -"mode. There are configuration options for this in <path>common.conf</path>" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):529 +msgid "you have an NVidia graphical card" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1438 -msgid "Hibernating with swsusp" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):534 +msgid "pmu" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1438 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):535 msgid "" -"\n" -"# <i>nano -w /etc/hibernate/common.conf</i>\n" -"<comment>(Make sure you have a backup of your data)</comment>\n" -"# <i>hibernate</i>\n" +"Enable the Power Management Unit plug-in of <c>cpufreqd</c>. This allows the " +"software to poll the Linux kernel Power Supply interface, getting more " +"detailed information on battery charge." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1444 -msgid "" -"The following section discusses the setup of TuxOnIce including fbsplash " -"support for a nice graphical progress bar during suspend and resume." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):540 +msgid "your laptop does not support ACPI or APM" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1449 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):546 msgid "" -"The first part of the configuration is similar to the configuration of " -"swsusp. In case you didn't store the location of your swap partition in the " -"kernel config, you have to pass it as a kernel parameter with the " -"<c>resume=swap:/dev/SWAP</c> directive. If booting is not possible due to a " -"broken image, append the <c>noresume</c> parameter. Additionally, the " -"<c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the " -"boot process." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1459 -msgid "Invalidating TuxOnIce images during the boot process" +"The USE flags <c>acpi</c>, <c>apm</c> and <c>pmu</c> overlap, so you should " +"only have one active. If your laptop is sufficiently recent, <c>acpi</c> is " +"your best bet. If not, <c>apm</c> offers all that is needed. When even APM " +"isn't supported, you can try <c>pmu</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1463 -msgid "" -"Now edit <path>/etc/hibernate/tuxonice.conf</path>, enable the <c>TuxOnIce</" -"c> options you need. Do not enable the <c>fbsplash</c> options in <c>common." -"conf</c> just yet." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):553 +msgid "With the USE flags configured, it is time to install <c>cpufreqd</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1469 -msgid "Hibernating with TuxOnIce" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):557 +msgid "Installing cpufreqd" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1469 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):557 #, no-wrap msgid "" "\n" -"# <i>nano -w /etc/hibernate/tuxonice.conf</i>\n" -"<comment>(Make sure you have a backup of your data)</comment>\n" -"# <i>hibernate</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1475 -msgid "" -"Please configure <c>fbsplash</c> now if you didn't do already. To enable " -"fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c> " -"package is needed. Additionally, you've got to enable the <c>fbsplash</c> " -"USE flag." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1481 -msgid "Installing tuxonice-userui" +"# <i>emerge cpufreqd</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1481 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):567 msgid "" -"\n" -"# <i>echo \"sys-apps/tuxonice-userui fbsplash\" >> /etc/portage/package.use</i>\n" -"# <i>emerge tuxonice-userui</i>\n" +"The <c>cpufreqd</c> application monitors the status of the system through " +"several plugins. Based on the feedback it receives from those plugins, it " +"will adjust the policy used to govern the CPU frequency." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1486 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):573 msgid "" -"The ebuild tells you to make a symlink to the theme you want to use. For " -"example, to use the <c>livecd-2005.1</c> theme, run the following command:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1491 -msgid "Using the livecd-2005.1 theme during hibernation" +"<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</" +"path>. It contains three different sections:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1491 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):579 msgid "" -"\n" -"# <i>ln -sfn /etc/splash/livecd-2005.1 /etc/splash/tuxonice</i>\n" +"The <c>[General]...[/General]</c> section contains general configuration " +"information" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1495 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):583 msgid "" -"If you don't want a black screen in the first part of the resume process, " -"you have to add the <c>tuxoniceui_fbsplash</c> tool to your initrd image. " -"Assuming you created the initrd image with <c>splash_geninitramfs</c> and " -"saved it as <path>/boot/fbsplash-emergence-1024x768</path>, here's how to do " -"that." +"The <c>[Profile]...[/Profile]</c> section defines the policies that the " +"<c>cpufreqd</c> daemon can switch to. The section is very similar to the " +"information you use when manually setting the CPU frequency policy using " +"<c>cpufreq-set</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1502 -msgid "Adding tuxoniceui_fbsplash to an initrd image" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1502 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):589 msgid "" -"\n" -"# <i>mount /boot</i>\n" -"# <i>mkdir ~/initrd.d</i>\n" -"# <i>cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i>\n" -"# <i>cd ~/initrd.d</i>\n" -"# <i>gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i>\n" -"# <i>rm fbsplash-emergence-1024x768</i>\n" -"# <i>cp /usr/sbin/tuxoniceui_fbsplash sbin/</i>\n" -"# <i>find . | cpio --quiet --dereference -o -H newc | gzip -9 > /boot/fbsplash-tuxonice-emergence-1024x768</i>\n" +"The <c>[Rule]...[/Rule]</c> section is the work-horse of the <c>cpufreqd</c> " +"daemon, defining when the daemon decides to switch to a different profile." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1513 -msgid "" -"Afterwards adjust <path>grub.conf</path> (or <path>lilo.conf</path>) so that " -"your TuxOnIce kernel uses <path>/boot/fbsplash-tuxonice-emergence-1024x768</" -"path> as initrd image. You can now test a dry run to see if everything is " -"setup correctly." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):595 +msgid "Let's take a quick look at an example rule." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1520 -msgid "Test run for fbsplash hibernation" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):599 +msgid "Sample cpufreqd rule" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1520 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):599 #, no-wrap msgid "" "\n" -"# <i>tuxoniceui_fbsplash -t</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1524 -msgid "" -"Afterwards open <path>/etc/hibernate/common.conf</path> and activate the " -"fbsplash options. Execute <c>hibernate</c> and enjoy." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1534 -msgid "Troubleshooting" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1538 -msgid "" -"<e>Q:</e> I'm trying to change the CPU frequency, but <path>/sys/devices/" -"system/cpu/cpu0/cpufreq/scaling_governor</path> does not exist." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1544 -msgid "" -"<e>A:</e> Make sure your processor supports CPU frequency scaling and you " -"chose the right CPUFreq driver for your processor. Here is a list of " -"processors that are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-" -"SA1100, ARM-SA1110, AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile " -"K6-3+, AMD mobile Duron, AMD mobile Athlon, AMD Opteron, AMD Athlon 64, " -"Cyrix Media GXm, Intel mobile PIII and Intel mobile PIII-M on certain " -"chipsets, Intel Pentium 4, Intel Xeon, Intel Pentium M (Centrino), National " -"Semiconductors Geode GX, Transmeta Crusoe, VIA Cyrix 3 / C3, UltraSPARC-III, " -"SuperH SH-3, SH-4, several \"PowerBook\" and \"iBook2\" and various " -"processors on some ACPI 2.0-compatible systems (only if \"ACPI Processor " -"Performance States\" are available to the ACPI/BIOS interface)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1557 -msgid "" -"<e>Q:</e> My laptop supports frequency scaling, but <path>/sys/devices/" -"system/cpu/cpu0/cpufreq/</path> is empty." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1562 -msgid "" -"<e>A:</e> Look for ACPI related error messages with <c>dmesg | grep ACPI</" -"c>. Try to update the BIOS, especially if a broken DSDT is reported. You can " -"also try to fix it yourself (which is beyond the scope of this guide)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1568 -msgid "" -"<e>Q:</e> My laptop supports frequency scaling, but according to <path>/proc/" -"cpuinfo</path> the speed never changes." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1573 -msgid "" -"<e>A:</e> Probably you have activated symmetric multiprocessing support " -"(CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older " -"kernels had a bug causing this. In that case, run <c>emerge x86info</c>, " -"update your kernel as asked and check the current frequency with <c>x86info -" -"mhz</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1580 -msgid "" -"<e>Q:</e> I can change the CPU frequency, but the range is not as wide as in " -"another OS." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1585 -msgid "" -"<e>A:</e> You can combine frequency scaling with ACPI throttling to get a " -"lower minimum frequency. Notice that throttling doesn't save much energy and " -"is mainly used for thermal management (keeping your laptop cool and quiet). " -"You can read the current throttling state with <c>cat /proc/acpi/processor/" -"CPU/throttling</c> and change it with <c>echo -n \"0:x\" > /proc/acpi/" -"processor/CPU/limit</c>, where x is one of the Tx states listed in <path>/" -"proc/acpi/processor/CPU/throttling</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1595 -msgid "" -"<e>Q:</e> When configuring the kernel, powersave, performance and userspace " -"governors show up, but that ondemand thing is missing. Where do I get it?" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1600 -msgid "" -"<e>A:</e> The ondemand governor is only included in recent kernel sources. " -"Try updating them." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1605 -msgid "<e>Q:</e> Battery life time seems to be worse than before." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1609 -msgid "" -"<e>A:</e> Check your BIOS settings. Maybe you forgot to re-enable some of " -"the settings." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1614 -msgid "" -"<e>Q:</e> My battery is charged, but KDE reports there would be 0% left and " -"immediately shuts down." +"[Profile]\n" +"name=On Demand High\n" +"minfreq=40%\n" +"maxfreq=100%\n" +"policy=ondemand\n" +"[/Profile]\n" +"\n" +"[Rule]\n" +"name=AC Off - High Power\n" +"ac=off\n" +"battery_interval=70-100\n" +"profile=On Demand High\n" +"[/Rule]\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1619 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):615 msgid "" -"<e>A:</e> Check that battery support is compiled into your kernel. If you " -"use it as a module, make sure the module is loaded." +"In the above example, <c>cpufreqd</c> will switch the system to the <e>On " +"Demand High</e> profile (also shown in the above excerpt). This profile by " +"itself uses the <c>ondemand</c> governor with a minimum frequency of 40% " +"(iow, a CPU of 2Ghz will have by this policy a minimum frequency of 800Mhz)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1624 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):622 msgid "" -"<e>Q:</e> My system logger reports things like \"logger: ACPI group " -"battery / action battery is not defined\"." +"As you can see, the <c>cpufreqd</c> application can offer a more granular " +"approach on CPU frequency scaling. But not only that, you can tweak the CPU " +"frequency scaling based on various other metrics available. The default " +"configuration offers a sample rule for when you watch a movie, where you " +"want maximum performance, unless the CPU temperature is getting too high." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1629 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):630 msgid "" -"<e>A:</e> This message is generated by the <path>/etc/acpi/default.sh</path> " -"script that is shipped with acpid. You can safely ignore it. If you like to " -"get rid of it, you can comment the appropriate line in <path>/etc/acpi/" -"default.sh</path> as shown below:" +"When you have configured <c>cpufreqd</c>, it is time to start it (and make " +"sure the service is loaded automatically). Make sure that CPU frequency " +"handling by other tools (like <c>laptop-mode-tools</c>) is disabled!" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1636 -msgid "Disabling warnings about unknown acpi events" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):636 +msgid "Starting cpufreqd" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1636 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):636 #, no-wrap msgid "" "\n" -" *) # logger \"ACPI action $action is not defined\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1640 -msgid "<e>Q:</e> I have a Dell Inspiron 51XX and I don't get any ACPI events." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1644 -msgid "" -"<e>A:</e> This seems to be a kernel bug. Read on <uri link=\"http://bugme." -"osdl.org/show_bug.cgi?id=1752\">here</uri>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1649 -msgid "" -"<e>Q:</e> I activated the <c>DynamicClocks</c> option in <path>xorg.conf</" -"path> and now X.org crashes / the screen stays black / my laptop doesn't " -"shutdown properly." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1655 -msgid "" -"<e>A:</e> This happens on some systems. You have to disable " -"<c>DynamicClocks</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1660 -msgid "" -"<e>Q:</e> I want to use TuxOnIce, but it tells me my swap partition is too " -"small. Resizing is not an option." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1665 -msgid "" -"<e>A:</e> If there is enough free space on your system, you can use the " -"filewriter instead of the swapwriter. The <c>hibernate-script</c> supports " -"it as well. More information can be found in <path>/usr/src/linux/" -"Documentation/power/tuxonice.txt</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1672 -msgid "" -"<e>Q:</e> I just bought a brand new battery, but it only lasts for some " -"minutes! What am I doing wrong?" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1677 -msgid "" -"<e>A:</e> First follow your manufacturer's advice on how to charge the " -"battery correctly." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1682 -msgid "<e>Q:</e> The above didn't help. What should I do then?" +"# <i>rc-service add cpufreqd default</i>\n" +"# <i>/etc/init.d/cpufreqd start</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1686 -msgid "" -"<e>A:</e> Some batteries sold as \"new\" are in fact old ones. Try the " -"following:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):646 +msgid "Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1690 -msgid "Querying battery state" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):648 +msgid "Tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1690 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):652 msgid "" -"\n" -"$ <i>grep capacity /proc/acpi/battery/BAT0/info</i>\n" -"design capacity: 47520 mWh\n" -"last full capacity: 41830 mWh\n" +"<uri link=\"http://samwel.tk/laptop_mode/\">Laptop Mode Tools Homepage</" +"uri>, includes <uri link=\"http://samwel.tk/laptop_mode/laptop_mode\">About " +"laptop mode</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1696 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):657 msgid "" -"If the \"last full capacity\" differs significantly from the design " -"capacity, your battery is probably broken. Try to claim your warranty." +"<uri link=\"http://www.lesswatts.org/projects/powertop/\">PowerTOP</uri>, an " +"interactive application helping users to find out which processes are " +"forcing wakeups on the CPU most often." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1701 -msgid "<e>Q:</e> My problem is not listed above. Where should I go next?" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):667 +msgid "Articles and Guides" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1705 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):671 msgid "" -"<e>A:</e> Don't fear to contact me, <mail link=\"earthwings@gentoo.org" -"\">Dennis Nienhüser</mail>, directly. The <uri link=\"http://forums.gentoo." -"org\">Gentoo Forums</uri> are a good place to get help as well. If you " -"prefer IRC, try the <c>#gentoo-laptop</c><uri link=\"irc://irc.gentoo.org" -"\">channel</uri>." +"A ThinkWiki article on <uri link=\"http://www.thinkwiki.org/wiki/" +"How_to_reduce_power_consumption\">How to reduce power consumption</uri> (on " +"Linux). This article offers an exhaustive list of measures one can take. " +"However, it should be noted that the laptop mode tools implements the " +"majority of these (if properly configured)." msgstr "" #. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL diff --git a/doc/gettext/el/xfce-config.xml.po b/doc/gettext/el/xfce-config.xml.po index afbc572..7885aea 100644 --- a/doc/gettext/el/xfce-config.xml.po +++ b/doc/gettext/el/xfce-config.xml.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-03-02 17:28+0500\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-10-21 23:56+0600\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -30,11 +30,11 @@ msgid "" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(version):21 -msgid "5" +msgid "6" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(date):22 -msgid "2011-02-14" +msgid "2011-09-18" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):25 @@ -113,9 +113,9 @@ msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):86 msgid "" -"Next, add your regular user(s) to the <c>plugdev</c>, <c>cdrom</c>, <c>cdrw</" -"c>, and <c>usb</c> groups, so that they can mount and use devices such as " -"cameras, optical drives, and USB sticks." +"Next, add your regular user(s) to the <c>cdrom</c>, <c>cdrw</c>, and <c>usb</" +"c> groups, so that they can mount and use devices such as cameras, optical " +"drives, and USB sticks." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):92 @@ -127,7 +127,7 @@ msgstr "" msgid "" "\n" "<comment>(Replace username with your actual user)</comment>\n" -"# <i>for x in plugdev cdrom cdrw usb ; do gpasswd -a username $x ; done</i>\n" +"# <i>for x in cdrom cdrw usb ; do gpasswd -a username $x ; done</i>\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):97 diff --git a/doc/gettext/faq.xml.pot b/doc/gettext/faq.xml.pot index 034074d..e805e81 100644 --- a/doc/gettext/faq.xml.pot +++ b/doc/gettext/faq.xml.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-18 15:18+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\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" @@ -106,11 +106,11 @@ msgid "This FAQ is a collection of questions and answers collected from the gent msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(version):50 -msgid "6" +msgid "7" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(date):51 -msgid "2011-09-11" +msgid "2011-10-13" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):54 @@ -220,442 +220,446 @@ msgid "Can I upgrade Gentoo from one release to another without reinstalling?" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):205 -msgid "In fact, there is no difference between the various releases after they have been installed. Gentoo 1.4 and later are <c>glibc-2.3.x</c> based. As such, running <c>emerge --sync && emerge -uDN world</c> will bring your entire system up to speed with the \"latest Gentoo\". The differences between individual releases lie in the installation medium and pre-compiled packages. See the <uri link=\"/doc/en/gentoo-upgrading.xml\">Gentoo Upgrading Guide</uri> for more information about profiles and their role in upgrading." +msgid "In fact, there is no difference between the various releases after they have been installed. Gentoo 1.4 and later are <c>glibc-2.3.x</c> (or higher) based. As such, running <c>emerge --sync && emerge -uDN world</c> will bring your entire system up to speed with the \"latest Gentoo\". The differences between individual releases lie in the installation medium and pre-compiled packages. See the <uri link=\"/doc/en/gentoo-upgrading.xml\">Gentoo Upgrading Guide</uri> for more information about profiles and their role in upgrading." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):218 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):215 +msgid "Also note that the <c>emerge -uDN world</c> command updates the packages you have installed as well as its dependencies, but not the build-time dependencies (packages needed during builds but not when the software is installed). To update those as well, add the <c>--with-bdeps=y</c> option." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):225 msgid "My kernel doesn't boot, what should I do now?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):221 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):228 msgid "You don't need to redo every step of the installation, but investigating the kernel and all associated steps is necessary. Suppose you have installed Gentoo on <path>/dev/hda1</path> (/boot) and <path>/dev/hda3</path> (/) with <path>/dev/hda2</path> being the swap space:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):228 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):235 msgid "Reconfiguring the kernel" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):228 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):235 #, no-wrap msgid "\n<comment>Boot from the Install CD and wait until you receive a prompt</comment>\n<comment>We first mount all partitions:</comment>\n# <i>mount /dev/hda3 /mnt/gentoo</i>\n# <i>mount /dev/hda1 /mnt/gentoo/boot</i>\n# <i>swapon /dev/hda2</i>\n# <i>mount -t proc none /mnt/gentoo/proc</i>\n<comment>Then we chroot into our Gentoo environment and configure the kernel:</comment>\n# <i>chroot /mnt/gentoo /bin/bash</i>\n# <i>env-update && source /etc/profile</i>\n# <i>cd /usr/src/linux</i>\n# <i>make menuconfig</i>\n<comment>Now (de)select anything you have (de)selected wrongly at your</comment>\n<comment>previous attempt. Then quit and compile your kernel:</comment>\n# <i>make && make modules_install</i>\n<comment>Now copy over your bzImage file, overwriting your previous one:</comment>\n# <i>cp arch/i386/boot/bzImage /boot/<kernel_name></i>\n<comment>If you use LILO, rerun lilo -- GRUB users should skip this:</comment>\n# <i>/sbin/lilo</i>\n<comment>Now exit the chroot and reboot.</comment>\n# <i>exit</i>\n# <i>umount /mnt/gentoo/proc /mnt/gentoo/boot /mnt/gentoo</i>\n# <i>reboot</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):253 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):260 msgid "If, on the other hand, the problem lies with your bootloader configuration, follow the same steps, but instead of configuring/compiling your kernel, you should reconfigure your bootloader (recompilation isn't necessary)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):262 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):269 msgid "My proxy requires authentication, what do I have to do?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):265 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):272 msgid "To have Portage automatically use this scheme, define it in <path>/etc/make.conf</path>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):270 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):277 msgid "/etc/make.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):270 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):277 #, no-wrap msgid "\nhttp_proxy=\"http://username:password@yourproxybox.org:portnumber\"\nftp_proxy=\"ftp://username:password@yourproxybox.org:portnumber\"\nRSYNC_PROXY=\"rsync://username:password@yourproxybox.server:portnumber\"\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):279 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):286 msgid "How do I burn an ISO file?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):282 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):289 msgid "You need to burn the file in raw mode. This means that you should <e>not</e> just place the file on the CD, but interpret the file as an entire CD." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):287 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):294 msgid "There are lots of CD burning tools available; covering them all would be a Sisyphean problem. However, describing a few popular tools never hurts:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):293 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):300 msgid "With EasyCD Creator you select <c>File</c>, <c>Record CD from CD image</c>. Then you change the <c>Files of type</c> to <c>ISO image file</c>. Then locate the ISO file and click <c>Open</c>. When you click on <c>Start recording</c> the ISO image will be burned correctly onto the CD-R." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):299 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):306 msgid "With Nero Burning ROM, cancel the wizard which automatically pops up and select <c>Burn Image</c> from the <c>File</c> menu. Select the image you want to burn and click <c>Open</c>. Now hit the <c>Burn</c> button and watch your brand new CD being burnt." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):305 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):312 msgid "With cdrecord, you simply type <c>cdrecord dev=/dev/hdc</c> (replace <path>/dev/hdc</path> with your CD-RW drive's device path) followed by the path to the ISO file :)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):310 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):317 msgid "With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn CD Image</c>. Then you can locate your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):315 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):322 msgid "With Mac OS X Panther, launch <c>Disk Utility</c> from <path>Applications/Utilities</path>, select <c>Open</c> from the <c>Images</c> menu, select the mounted disk image in the main window and select <c>Burn</c> in the <c>Images</c> menu." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):321 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):328 msgid "With Mac OS X Jaguar, launch <c>Disk Copy</c> from <path>Applications/Utilities</path>, select <c>Burn Image</c> from the <c>File</c> menu, select the ISO and click the <c>Burn</c> button." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):332 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):339 msgid "What CD/stage should I use for my CPU?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):335 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):342 msgid "First you need to find out what CPU you use. Suppose it's a Pentium-M. Then you need to find out what CPU it is, instruction-wise, compatible with. You may need to consult the CPU's vendor website for this, although <uri link=\"http://www.google.com\">Google</uri> is at least as efficient :-)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):342 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):349 msgid "If you are uncertain, take a \"lower\" CD/stage file, for instance a i686 or even generic x86 (or the equivalent in your arch). This will ensure that your system will work, but may not be as fast as further optimizations." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):348 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):355 msgid "Please note that many more options exist than those for which Gentoo builds binary stages. Please see the <uri link=\"http://gcc.gnu.org/onlinedocs/gcc-4.4.3/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options\">gcc guide</uri> for setting <c>-march</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):358 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):365 msgid "I can't get online after rebooting. What is wrong?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):361 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):368 msgid "First you need to check if your network card is discovered properly by the kernel. Run <c>ifconfig -a</c> and look for eth0 or wlan0 (in case of certain wireless network cards). You might need to load specific kernel modules for the kernel to properly detect the network card. If that is the case, make sure that these kernel modules are listed in <path>/etc/conf.d/modules</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):370 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):377 msgid "If you have forgotten to include support for your network card in your kernel, you will need to reconfigure your kernel." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):375 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):382 msgid "If your network card is found by your kernel, but you have set your networking configuration to use DHCP, you might have forgotten to <c>emerge dhcpcd</c>. You will need to reboot with your installation CD to install <c>dhcpcd</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):382 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):389 msgid "Information on how to rescue your system using the installation CD is <uri link=\"#bootrescue\">available</uri> as well." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):390 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):397 msgid "I want to boot Windows from grub or lilo but it shows only black screen. What should I do?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):396 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):403 msgid "This is a known problem. Windows refuses to boot when it isn't installed on the first hard drive and shows a black/blank screen. To handle this, you will have to \"fool\" Windows into believing that it is installed on the first hard drive with a little tweak in your boot loader configuration. Please note that in the below example, Gentoo is installed on <path>hda</path> (first disk) and Windows on <path>hdb</path> (second one). Adjust your config as needed." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):405 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):412 msgid "Example dual boot entry for Windows in grub.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):405 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):412 #, no-wrap msgid "\ntitle Windows XP\n map (hd1) (hd0)\n map (hd0) (hd1)\n rootnoverify (hd1,0)\n chainloader +1\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):413 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):420 msgid "Example dual boot entry for Windows in lilo.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):413 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):420 #, no-wrap msgid "\nother=/dev/hdb1\n label=WindowsXP\n table=/dev/hdb\n map-drive = 0x80\n to = 0x81\n map-drive = 0x81\n to = 0x80\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):423 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):430 msgid "This will make Windows believe it is installed on the first hard drive and boot without problems. More information can be found in the <uri link=\"http://www.gnu.org/software/grub/\">GRUB documentation</uri> and in <c>man lilo.conf</c>, depending on the boot loader you're using." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):433 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):440 msgid "How do I Install Gentoo Using a Stage1 or Stage2 Tarball?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):436 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):443 msgid "The Gentoo Handbook only describes a Gentoo installation using a stage3 tarball. However, Gentoo still provides stage1 and stage2 tarballs. This is for development purposes (the Release Engineering team starts from a stage1 tarball to obtain a stage3) but shouldn't be used by users: a stage3 tarball can very well be used to bootstrap the system. You do need a working Internet connection." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):444 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):451 msgid "Bootstrapping means building the toolchain (the C library and compiler) for your system after which you install all core system packages. To bootstrap the system, perform a stage3 installation. Before you start the chapter on <e>Configuring the Kernel</e>, modify the <path>bootstrap.sh</path> script to suit your needs and then run it:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):452 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):459 msgid "Bootstrapping the system" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):452 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):459 #, no-wrap msgid "\n# <i>cd /usr/portage/scripts</i>\n# <i>vi bootstrap.sh</i>\n\n# <i>./bootstrap.sh</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):459 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):466 msgid "Next, rebuild all core system packages with the newly built toolchain. We need to rebuild them since the stage3 tarball already offers them:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):464 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):471 msgid "Rebuilding the core system packages" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):464 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):471 #, no-wrap msgid "\n# <i>emerge -e system</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):468 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):475 msgid "Now you can continue with <e>Configuring the Kernel</e>. You can not use the prebuilt GRP packages anymore though." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):478 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):485 msgid "Package Management" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):480 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):487 msgid "In what form are the packages stored?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):483 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):490 msgid "Packages aren't \"stored\" per se. Instead, Gentoo provides a set of scripts which can resolve dependencies, fetch source code, and compile a version of the package specifically for your needs. We generally only build binaries for releases and snapshots. The <uri link=\"/proj/en/devrel/handbook/handbook.xml?part=2&chap=1\">Gentoo Ebuild HOWTO</uri> covers the contents of an ebuild script in detail." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):492 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):499 msgid "For full ISO releases, we create a full suite of binary packages in an enhanced <c>.tbz2</c> format, which is <c>.tar.bz2</c> compatible with meta-information attached to the end of the file. These can be used to install a working (though not fully optimized) version of the package quickly and efficiently." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):499 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):506 msgid "It is possible to create RPMs (Redhat package manager files) using Gentoo's Portage, but it is not currently possible to use already existing RPMs to install packages." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):508 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):515 msgid "I want to perform the ./configure step myself. Can I?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):511 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):518 msgid "Yes, but it is not trivial, nor is it recommended. Since the method to do this requires a good understanding of Portage internals and commands, it is instead recommended that you patch the ebuild to do whatever it is that you want and place it in a Portage overlay (that's why overlays exist). This is <e>much</e> better for maintainability, and usually easier. See the <uri link=\"/proj/en/devrel/handbook/handbook.xml?part=2&chap=1\">Ebuild HOWTO</uri> for more information." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):524 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):531 msgid "How do I use emerge from behind a firewall?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):527 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):534 msgid "See the questions on <uri link=\"#proxy\">proxies</uri>, <uri link=\"#norsync\">rsync</uri>, and <uri link=\"#manualdownload\">downloading source files manually</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):536 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):543 msgid "What if rsync doesn't work for me?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):539 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):546 msgid "If you're behind a firewall that doesn't permit rsync traffic, then you can use <c>emerge-webrsync</c> which will fetch and install a Portage snapshot for you through regular HTTP. See the <uri link=\"#proxy\">proxy section</uri> of this document for information on downloading source files and Portage snapshots via a proxy." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):550 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):557 msgid "I have only slow modem connection at home. Can I download sources somewhere else and add them to my system?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):556 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):563 msgid "Definitely. You can run <c>emerge --pretend package</c> to see what programs are going to be installed. To find out the sources for those packages and where to download the sources from, you can run <c>emerge -fp package</c>. Download sources and bring them on any media home. Put the sources into <path>/usr/portage/distfiles/</path> and then simply run <c>emerge package</c>. Be warned, however, that this is a tedious process." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):568 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):575 msgid "Source tarballs are collecting in /usr/portage/distfiles/. Is it safe to delete these files?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):574 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):581 msgid "Deleting these files will have no negative impact on day-to-day performance. However, it might be wise to keep the most recent version of the files; often several ebuilds will be released for the same version of a specific piece of software. If you have deleted the archive and you upgrade the software it will be necessary to download them from the internet again." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):582 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):589 msgid "You can use the <c>eclean</c> script from <c>app-portage/gentoolkit</c> to manage the contents of <path>/usr/portage/distfiles/</path> and a few other locations. Please read <c>man eclean</c> to learn more about its usage, as well as the <uri link=\"/doc/en/gentoolkit.xml\">Gentoolkit Guide</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):592 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):599 msgid "What's in /var/tmp/portage? Is it safe to delete the files and directories in /var/tmp/portage?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):598 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):605 msgid "During compilation, Gentoo saves the sources of the package in <path>/var/tmp/portage</path>. These files and folder are usually deleted upon a successful merge, but this sometimes fails. It is safe to clean out all contents of this directory <e>if</e> emerge is not running. Just to be sure, always <c>pgrep emerge</c> before cleaning out this directory." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):611 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):618 msgid "Usage" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):613 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):620 msgid "How do I set up an International Keyboard Layout?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):616 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):623 msgid "Edit the <c>KEYMAP</c> variable in <path>/etc/conf.d/keymaps</path>. To have console working correctly with extended characters in your keymap you might also need to set up variables <c>CONSOLETRANSLATION</c> and <c>CONSOLEFONT</c> in your <path>/etc/conf.d/consolefont</path> (for further information on localising your environment, refer to <uri link=\"/doc/en/guide-localization.xml\">our localisation guide</uri>). Then, either <c>reboot</c>, or restart the keymaps and consolefont scripts:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):626 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):633 msgid "Restarting keymaps" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):626 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):633 #, no-wrap msgid "\n# <i>/etc/init.d/keymaps restart</i>\n# <i>/etc/init.d/consolefont restart</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):634 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):641 msgid "DNS name resolution works for root only" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):637 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):644 msgid "<path>/etc/resolv.conf</path> has the wrong permissions; <c>chmod</c> it as follows:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):642 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):649 msgid "Changing permissions on /etc/resolv.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):642 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):649 #, no-wrap msgid "\n# <i>chmod 0644 /etc/resolv.conf</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):649 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):656 msgid "Why can't my user use their own crontab?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):652 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):659 msgid "You need to add that user to the <c>cron</c> group." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):659 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):666 msgid "How do I get numlock to start on boot?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):662 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):669 msgid "If you work in command line, you only need to <c>rc-update add numlock default &&/etc/init.d/numlock start</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):667 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):674 msgid "Each GUI provides different tools for this sort of thing; please check the help section or online manuals for assistance." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):675 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):682 msgid "How do I have my terminal cleared when I log out?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):678 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):685 msgid "To have your terminal cleared, add <c>clear</c> to your <path>~/.bash_logout</path> script:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):683 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):690 msgid "Clearing the terminal during logout" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):683 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):690 #, no-wrap msgid "\n$ <i>echo clear >> ~/.bash_logout</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):687 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):694 msgid "If you want this to happen automatically when you add a new user, do the same for the <path>/etc/skel/.bash_logout</path>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):692 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):699 msgid "Making new users their terminal clear on logout" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):692 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):699 #, no-wrap msgid "\n# <i>echo clear >> /etc/skel/.bash_logout</i>" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):700 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):707 msgid "Maintenance" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):702 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):709 msgid "ReiserFS and filesystem corruption issues -- how to fix them, etc" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):705 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):712 msgid "If your ReiserFS partition is corrupt, try booting the Gentoo Install CD and run <c>reiserfsck --rebuild-tree</c> on the corrupted filesystem. This should make the filesystem consistent again, although you may have lost some files or directories due to the corruption." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):717 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):724 msgid "Development" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):719 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):726 msgid "Where can I report bugs?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):722 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):729 msgid "Use our <uri link=\"https://bugs.gentoo.org\">Bugzilla</uri>. If you are unsure if your problem is an actual bug, you can visit <uri link=\"irc://irc.gentoo.org/gentoo\">#gentoo</uri> on IRC." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):731 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):738 msgid "How often are new releases made?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):734 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):741 msgid "Gentoo's packages are usually updated shortly after the main authors release new code. As for when Gentoo itself makes new stage/profile/ISO releases, check our <uri link=\"/proj/en/releng\">Release Engineering Project</uri> page. New releases are announced on the <uri link=\"/main/en/lists.xml\">gentoo-announce</uri> mailing list. See the question on <uri link=\"#upgrade\">upgrading</uri> for more information." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):746 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):753 msgid "My speaker beeps like crazy. How do I disable console beeps?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):751 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):758 msgid "Console beeps can be turned off using setterm, like this:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):755 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):762 msgid "Using setterm" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):755 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):762 #, no-wrap msgid "\n# <i>setterm -blength 0</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):759 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):766 msgid "If you would like to turn off the console beeps on boot, you need to put this command in <path>/etc/conf.d/local.start</path>. However, this only disables beeps for the current terminal. To disable beeps for other terminals, pipe the command output to the target terminal, like this:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):765 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):772 msgid "Using setterm (bis)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):765 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):772 #, no-wrap msgid "\n# <i>setterm -blength 0 >/dev/vc/1</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):769 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):776 msgid "You need to replace /dev/vc/1 with the terminal you would like to disable console beeps for." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):779 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):786 msgid "Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):781 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):788 msgid "Where can I find more information about Gentoo Linux?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):784 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):791 msgid "The official Gentoo documentation can be found at <uri>http://www.gentoo.org/doc/en/</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):792 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):799 msgid "Can I buy a CD of Gentoo Linux?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):795 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):802 msgid "Install CDs for all supported architectures are available on our <uri link=\"http://www.cafepress.com/officialgentoo/\">Gentoo Store</uri>. When you purchase a CD from our store, you are also supporting our development. So, please consider buying from our store if possible." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):802 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):809 msgid "You can also find fresh CDs from various resellers listed on our <uri link=\"/main/en/where.xml\">Get Gentoo!</uri> page." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):810 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):817 msgid "This FAQ hasn't answered my question. What do I do now?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):813 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):820 msgid "A good first step is to browse through the relevant <uri link=\"/doc/en/index.xml\">documentation</uri>, failing that, the various Gentoo Linux mailing lists listed on <uri link=\"http://www.google.com\">Google</uri>. To search through the Gentoo mailing lists, just enter \"lists.gentoo.org foo\" to search for \"foo\". If all else fails, or you just want to hang out with Gentoo folks, visit us on irc: <uri link=\"irc://irc.gentoo.org/gentoo\">#gentoo</uri>." msgstr "" diff --git a/doc/gettext/gcc-upgrading-upto-4.1.xml.pot b/doc/gettext/gcc-upgrading-upto-4.1.xml.pot new file mode 100644 index 0000000..cf2586c --- /dev/null +++ b/doc/gettext/gcc-upgrading-upto-4.1.xml.pot @@ -0,0 +1,375 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\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=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):7 +msgid "Gentoo GCC Upgrade Guide for GCC Up To 4.1" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):9 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):12 +msgid "Author" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):10 +msgid "amne@gentoo.org" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail):10 +msgid "Wernfried Haas" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):13 +msgid "jkt@gentoo.org" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail):13 +msgid "Jan Kundrát" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):15 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):18 +msgid "Editor" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):16 +msgid "halcy0n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):19 +msgid "nightmorph" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(abstract):22 +msgid "This document will guide the user through the process of upgrading GCC." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(version):30 +msgid "23" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(date):31 +msgid "2008-07-19" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):34 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):80 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):167 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):333 +msgid "Introduction" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):36 +msgid "GCC Upgrading" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):39 +msgid "Why should you upgrade? Well, GCC is quite similar to any other package on your system, just a bit more critical. You should upgrade GCC whenever a new version fixes some bug that annoys you, new functionality you need is introduced, or if you want to keep your system up-to-date. If none of the previous cases apply to you, you can safely postpone upgrade as long as your GCC version is supported by Gentoo developers." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):48 +msgid "If you install a new major version of GCC (such as 3.3.6 to 3.4.5), the system will not switch over to use it automatically. You'll have to explicitly request the change because the migration process might require some additional steps. If you decide not to switch, Portage will continue to use older version of your compiler until you change your mind, or remove the old compiler from the system. Non-major gcc upgrades are switched automatically for you (such as 3.4.5 to 3.4.6)." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):58 +msgid "This guide will document the necessary steps required to perform a seamless upgrade of the compiler used by your Gentoo box. A specific section is dedicated to the <uri link=\"#upgrade-3.3-to-3.4\">upgrade from GCC 3.3 to 3.4</uri> and issues with <c>libstdc++</c>. A second specific section is for users <uri link=\"#first-install\">first installing</uri> Gentoo using a stage3 tarball, after a new GCC major/minor version has been released." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(warn):67 +msgid "It should be noted that upgrading from GCC-3.4 (or 3.3) to GCC-4.1 or greater still requires you to follow the <uri link=\"#upgrade-general\">general upgrading instructions</uri>, as GCC-3.4 and GCC-4.1 use slightly different ABIs." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):78 +msgid "General Upgrade Instructions" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):83 +msgid "If you're looking for instructions specific to upgrades from GCC-3.3 to GCC-3.4, please consult the <uri link=\"#upgrade-3.3-to-3.4\">dedicated section</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):89 +msgid "If you're looking for instructions specific to upgrades in GCC for new installs, please consult the <uri link=\"#first-install\">dedicated section</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):95 +msgid "Generally speaking, upgrades to <e>bug fix releases</e>, like from 3.3.5 to 3.3.6, should be quite safe -- just emerge new version, switch your system to use it and rebuild the only affected package, <c>libtool</c>. However, some GCC upgrades break binary compatibility; in such cases a rebuild of the affected packages (or even whole toolchain and system) might be required." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):103 +msgid "When we spoke about the need to switch your compiler to the newer version by hand, we said it won't happen automatically. However, there is one exception -- upgrades to bug fix releases, like from 3.3.5 to 3.3.6 in case you don't use the \"multislot\" feature allowing them to coexist on one system. Multislot is disabled by default as the majority of users won't benefit from it." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):111 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):278 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):366 +msgid "Upgrading GCC" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):111 +#, no-wrap +msgid "\n# <i>emerge -uav gcc</i>\n\n<comment>(Please substitute \"i686-pc-linux-gnu-4.1.1\" with the GCC\nversion and CHOST settings you've upgraded to:)</comment>\n# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>\n# <i>env-update && source /etc/profile</i>\n\n<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this\nexample) you will have to run fix_libtool_files.sh manually</comment>\n<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.4.6</i>\n\n<comment>(Rebuilding libtool)</comment>\n# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):129 +msgid "To be completely safe that your system is in a sane state, you <e>must</e> rebuild the toolchain and then world to make use of the new compiler." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):134 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):433 +msgid "Rebuilding system" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):134 +#, no-wrap +msgid "\n# <i>emerge -eav system</i>\n# <i>emerge -eav world</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):139 +msgid "It is safe to remove the older GCC version at this time. If you feel the need, please issue the following command (as usual, substitute <c>=sys-devel/gcc-3.4*</c> with the version you want to uninstall):" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):145 +msgid "Removing older GCC version" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):145 +#, no-wrap +msgid "\n# <i>emerge -aC =sys-devel/gcc-3.4*</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):149 +msgid "Please note that the GCC 4.1 and newer can compile only kernels newer than 2.4.34. Don't remove your old GCC version if you want to use an older kernel." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):154 +msgid "In case you're upgrading from GCC-3.3, you should run <c>emerge --oneshot sys-libs/libstdc++-v3</c> to provide compatibility with older binary C++ applications." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):165 +msgid "Upgrading from GCC-3.3 to 3.4" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):170 +msgid "The upgrade from GCC-3.3 to 3.4 is not seamless as the C++ ABI changed between these two versions. There is an issue with the <c>libstdc++</c> library which must be taken care of, as well." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):179 +msgid "The Choices" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):182 +msgid "If you upgrade from gcc 3.4 to 4.1, please consult the <uri link=\"#upgrade-general\">General Update instructions</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):187 +msgid "If you're upgrading on a SPARC machine, you will have to take the way of <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system rebuild</uri> due to some internal <uri link=\"http://gcc.gnu.org/gcc-3.4/sparc-abi.html\">ABI changes</uri> in GCC's parameter passing." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):194 +msgid "If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to upgrade your system. The <uri link=\"#upgrade-3.3-to-3.4-revdep-rebuild\">first method</uri> is faster and requires use of the <c>revdep-rebuild</c> tool from package <c>gentoolkit</c> while the <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">second one</uri> rebuilds the entire system from scratch so it will make use of new GCC features. It's up to you to decide which of these two ways you will choose. In most cases, the first method is sufficient." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):205 +msgid "If you upgrade from gcc 3.3 to 4.1, do not use the method based on revdep-rebuild, but do a <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system rebuild</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):214 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):242 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):390 +msgid "Using revdep-rebuild" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):217 +msgid "This method requires that you first install <c>gentoolkit</c> if you have not already done so. Then we will upgrade GCC and switch to the new compiler. We will also rebuild the <c>libtool</c> package to ensure that toolchain is in healthy state." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):224 +msgid "Installing gentoolkit and upgrading GCC" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):224 +#, no-wrap +msgid "\n# <i>emerge -an gentoolkit</i>\n# <i>emerge -uav gcc</i>\n<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\nversion and CHOST settings you've upgraded to:)</comment>\n# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n# <i>source /etc/profile</i>\n\n<comment>(Rebuilding libtool)</comment>\n# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):236 +msgid "Now, we want to see which packages that revdep-rebuild will want to rebuild. Then we will tell revdep-rebuild to actually rebuild the packages. This may take some time, so have some patience." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):242 +#, no-wrap +msgid "\n# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(note):247 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(note):405 +msgid "It is possible that you might have problems with non-existing package versions due to them being outdated or masked. If this is the case, you will want to use the <c>--package-names</c> option to <c>revdep-rebuild</c>. This causes packages to be recompiled based on the package name, rather than the exact name and version." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):255 +msgid "To provide compatibility with older binary C++ applications and any packages that revdep-rebuild might have missed, <c>sys-libs/libstdc++-v3</c> needs to be merged before you unmerge GCC 3.3 from your system." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):261 +msgid "Installing libstdc++-v3 and cleaning up" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):261 +#, no-wrap +msgid "\n# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):269 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):416 +msgid "Using emerge -e" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):272 +msgid "This method, while much slower, will rebuild your whole system to ensure that everything has been rebuilt with your new compiler, and therefore safer. At first, you will upgrade GCC and libtool and switch to your new compiler." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):278 +#, no-wrap +msgid "\n# <i>emerge -uav gcc</i>\n<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\nversion and CHOST settings you've upgraded to:)</comment>\n# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n# <i>source /etc/profile</i>\n\n<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this\nexample) you will have to run fix_libtool_files.sh manually</comment>\n<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</i>\n\n<comment>(Rebuilding libtool)</comment>\n# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):295 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):377 +msgid "To provide compatibility with older binary C++ applications, <c>sys-libs/libstdc++-v3</c> needs to be merged onto your system." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):300 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):382 +msgid "Installing libstdc++-v3" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):300 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):382 +#, no-wrap +msgid "\n# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):304 +msgid "Now we will go about first rebuilding the system target, then the world target. This will take a very long time, depending on the number of packages that you have installed, as it will rebuild your entire toolchain and supporting system files, followed by every package on your system, including the toolchain. This is necessary to ensure that all packages have been compiled with the new toolchain, including the toolchain itself." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):313 +msgid "Rebuilding system and world" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):313 +#, no-wrap +msgid "\n# <i>emerge -e system</i>\n# <i>emerge -e world</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):318 +msgid "It is also safe to remove older GCC versions at this time:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):322 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):440 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):448 +msgid "Cleaning up" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):322 +#, no-wrap +msgid "\n# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):331 +msgid "Upgrading to GCC on a First Install" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):336 +msgid "A GCC upgrade on a system after installation from a stage3 tarball is a simple affair. One advantage users of new installations have is they do not have a plethora of software installed that links against the older version of GCC. The following example is for a GCC-3.3 to 3.4 upgrade. Certain parts will be different if upgrading from other versions of GCC. For example, the library names used for <c>revdep-rebuild</c> below are GCC 3.3 specific, as well as the need to install <c>libstdc++-v3</c>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):346 +msgid "If a user has not made any customizations to their system yet, then there are very few steps to get their system upgraded to a new GCC version. As with the GCC-3.3 to 3.4 upgrade, the user has a couple options. However, unlike the GCC-3.3 to 3.4 upgrade, this one is less complicated as there are fewer differences between the methods. The <uri link=\"#first-install-revdep-rebuild\">first method</uri> is faster and makes use of the <c>revdep-rebuild</c> tool from <c>gentoolkit</c>, similar to the above procedure. Using revdep-rebuild causes only packages which actually link against GCC libraries to be rebuilt, while the <uri link=\"#first-install-emerge-e\">second method</uri> causes your entire new install to be recompiled with the new GCC version and takes much longer. This second method is never required and only documented for completeness." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):361 +msgid "These first steps are common between both methods, and should be completed by everyone." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):366 +#, no-wrap +msgid "\n# <i>emerge -uav gcc</i>\n<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\nversion and CHOST settings you've upgraded to:)</comment>\n# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n# <i>source /etc/profile</i>\n\n<comment>(Rebuilding libtool)</comment>\n# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):393 +msgid "This method requires that you first install <c>gentoolkit</c> if you have not already done so. We will then run <c>revdep-rebuild</c> to actually scan the installed packages for ones we need to rebuild, then rebuild them." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):399 +msgid "Installing gentoolkit and running revdep-rebuild" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):399 +#, no-wrap +msgid "\n# <i>emerge -an gentoolkit</i>\n# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):419 +msgid "This method, while much slower, will rebuild the system target to ensure that everything has been rebuilt with your new compiler. This is not necessary, but is valid if you are also making changes to CFLAGS or other make.conf variables that will affect the system compile." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):426 +msgid "Since we are performing these actions after an initial installation, we do not need to recompile the <c>world</c> target as we would when doing an upgrade on an already installed system. However, you may choose to perform a world update in place of the system update, to ensure that all packages are updated." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):433 +#, no-wrap +msgid "\n# <i>emerge -e system</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):443 +msgid "It is also safe to remove older GCC versions at this time. Please substitute <c>YOUR-NEW-GCC-VERSION</c> with the actual version you've upgraded to:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):448 +#, no-wrap +msgid "\n# <i>emerge -aC \"<sys-devel/gcc-YOUR-NEW-GCC-VERSION\"</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):457 +msgid "Common Pitfalls" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):461 +msgid "It's important to disable <c>distcc</c> during upgrade. Mixing compiler versions on your nodes <e>will</e> cause build issues. This is not required for ccache, as the cache objects will be invalidated anyway." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):467 +msgid "Always use same GCC version for your kernel and additional kernel modules. Once you rebuild your world with new GCC, external modules (like <c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel with the new GCC to fix that." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):474 +msgid "If you're upgrading on a SPARC machine, make sure to rerun <c>silo -f</c> after re-emerging world to avoid possible issues." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):482 +msgid "Frequent Error Messages" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):485 +msgid "If your system complains about something like <e>libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool archive</e>, please run <c>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</c> (substitute \"3.3.6\" with the version numbers from the error message, and $CHOST and <gcc-version> with your actual CHOST and GCC version)." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):494 +msgid "If you see <e>error: /usr/bin/gcc-config: line 632: /etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try deleting <path>/etc/env.d/gcc/config-i686-pc-linux-gnu</path> and running <c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this if you do not have any cross-compilers set up, though." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):502 +msgid "If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, you can resume operation with <c>emerge --resume</c>. If a package fails repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any other instances of emerge in between or you will lose the resume information." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):509 +msgid "If you get an error message <e>spec failure: unrecognized spec option</e> while upgrading your compiler, try to switch back to your default compiler, unset the <c>GCC_SPECS</c> variable and upgrade GCC again:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):515 +msgid "Restoring primary specs" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):515 +#, no-wrap +msgid "\n# <i>gcc-config 1</i>\n# <i>source /etc/profile</i>\n# <i>unset GCC_SPECS</i>\n# <i>emerge -uav gcc</i>\n" +msgstr "" + +#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(None):0 +msgid "translator-credits" +msgstr "" + diff --git a/doc/gettext/gcc-upgrading.xml.pot b/doc/gettext/gcc-upgrading.xml.pot index 4a9183a..3ab4010 100644 --- a/doc/gettext/gcc-upgrading.xml.pot +++ b/doc/gettext/gcc-upgrading.xml.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\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" @@ -13,359 +13,195 @@ msgstr "" msgid "Gentoo GCC Upgrade Guide" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):9 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):12 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):9 msgid "Author" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):10 -msgid "amne@gentoo.org" +msgid "swift" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail):10 -msgid "Wernfried Haas" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):13 -msgid "jkt@gentoo.org" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail):13 -msgid "Jan Kundrát" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):15 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):18 -msgid "Editor" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):16 -msgid "halcy0n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):19 -msgid "nightmorph" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(abstract):22 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(abstract):13 msgid "This document will guide the user through the process of upgrading GCC." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(version):30 -msgid "23" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(date):31 -msgid "2008-07-19" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):34 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):80 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):167 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):333 -msgid "Introduction" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):36 -msgid "GCC Upgrading" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):39 -msgid "Why should you upgrade? Well, GCC is quite similar to any other package on your system, just a bit more critical. You should upgrade GCC whenever a new version fixes some bug that annoys you, new functionality you need is introduced, or if you want to keep your system up-to-date. If none of the previous cases apply to you, you can safely postpone upgrade as long as your GCC version is supported by Gentoo developers." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):48 -msgid "If you install a new major version of GCC (such as 3.3.6 to 3.4.5), the system will not switch over to use it automatically. You'll have to explicitly request the change because the migration process might require some additional steps. If you decide not to switch, Portage will continue to use older version of your compiler until you change your mind, or remove the old compiler from the system. Non-major gcc upgrades are switched automatically for you (such as 3.4.5 to 3.4.6)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):58 -msgid "This guide will document the necessary steps required to perform a seamless upgrade of the compiler used by your Gentoo box. A specific section is dedicated to the <uri link=\"#upgrade-3.3-to-3.4\">upgrade from GCC 3.3 to 3.4</uri> and issues with <c>libstdc++</c>. A second specific section is for users <uri link=\"#first-install\">first installing</uri> Gentoo using a stage3 tarball, after a new GCC major/minor version has been released." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(warn):67 -msgid "It should be noted that upgrading from GCC-3.4 (or 3.3) to GCC-4.1 or greater still requires you to follow the <uri link=\"#upgrade-general\">general upgrading instructions</uri>, as GCC-3.4 and GCC-4.1 use slightly different ABIs." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):78 -msgid "General Upgrade Instructions" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):83 -msgid "If you're looking for instructions specific to upgrades from GCC-3.3 to GCC-3.4, please consult the <uri link=\"#upgrade-3.3-to-3.4\">dedicated section</uri>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):89 -msgid "If you're looking for instructions specific to upgrades in GCC for new installs, please consult the <uri link=\"#first-install\">dedicated section</uri>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):95 -msgid "Generally speaking, upgrades to <e>bug fix releases</e>, like from 3.3.5 to 3.3.6, should be quite safe -- just emerge new version, switch your system to use it and rebuild the only affected package, <c>libtool</c>. However, some GCC upgrades break binary compatibility; in such cases a rebuild of the affected packages (or even whole toolchain and system) might be required." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):103 -msgid "When we spoke about the need to switch your compiler to the newer version by hand, we said it won't happen automatically. However, there is one exception -- upgrades to bug fix releases, like from 3.3.5 to 3.3.6 in case you don't use the \"multislot\" feature allowing them to coexist on one system. Multislot is disabled by default as the majority of users won't benefit from it." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):111 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):278 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):366 -msgid "Upgrading GCC" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):111 -#, no-wrap -msgid "\n# <i>emerge -uav gcc</i>\n\n<comment>(Please substitute \"i686-pc-linux-gnu-4.1.1\" with the GCC\nversion and CHOST settings you've upgraded to:)</comment>\n# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>\n# <i>env-update && source /etc/profile</i>\n\n<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this\nexample) you will have to run fix_libtool_files.sh manually</comment>\n<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.4.6</i>\n\n<comment>(Rebuilding libtool)</comment>\n# <i>emerge --oneshot -av libtool</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):129 -msgid "To be completely safe that your system is in a sane state, you <e>must</e> rebuild the toolchain and then world to make use of the new compiler." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):134 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):433 -msgid "Rebuilding system" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(version):21 +msgid "25" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):134 -#, no-wrap -msgid "\n# <i>emerge -eav system</i>\n# <i>emerge -eav world</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):139 -msgid "It is safe to remove the older GCC version at this time. If you feel the need, please issue the following command (as usual, substitute <c>=sys-devel/gcc-3.4*</c> with the version you want to uninstall):" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):145 -msgid "Removing older GCC version" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):145 -#, no-wrap -msgid "\n# <i>emerge -aC =sys-devel/gcc-3.4*</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):149 -msgid "Please note that the GCC 4.1 and newer can compile only kernels newer than 2.4.34. Don't remove your old GCC version if you want to use an older kernel." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):154 -msgid "In case you're upgrading from GCC-3.3, you should run <c>emerge --oneshot sys-libs/libstdc++-v3</c> to provide compatibility with older binary C++ applications." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):165 -msgid "Upgrading from GCC-3.3 to 3.4" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):170 -msgid "The upgrade from GCC-3.3 to 3.4 is not seamless as the C++ ABI changed between these two versions. There is an issue with the <c>libstdc++</c> library which must be taken care of, as well." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):179 -msgid "The Choices" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):182 -msgid "If you upgrade from gcc 3.4 to 4.1, please consult the <uri link=\"#upgrade-general\">General Update instructions</uri>." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(date):22 +msgid "2011-10-15" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):187 -msgid "If you're upgrading on a SPARC machine, you will have to take the way of <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system rebuild</uri> due to some internal <uri link=\"http://gcc.gnu.org/gcc-3.4/sparc-abi.html\">ABI changes</uri> in GCC's parameter passing." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):25 +msgid "Quickstart" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):194 -msgid "If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to upgrade your system. The <uri link=\"#upgrade-3.3-to-3.4-revdep-rebuild\">first method</uri> is faster and requires use of the <c>revdep-rebuild</c> tool from package <c>gentoolkit</c> while the <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">second one</uri> rebuilds the entire system from scratch so it will make use of new GCC features. It's up to you to decide which of these two ways you will choose. In most cases, the first method is sufficient." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):205 -msgid "If you upgrade from gcc 3.3 to 4.1, do not use the method based on revdep-rebuild, but do a <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system rebuild</uri>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):214 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):242 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):390 -msgid "Using revdep-rebuild" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):217 -msgid "This method requires that you first install <c>gentoolkit</c> if you have not already done so. Then we will upgrade GCC and switch to the new compiler. We will also rebuild the <c>libtool</c> package to ensure that toolchain is in healthy state." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):224 -msgid "Installing gentoolkit and upgrading GCC" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):224 -#, no-wrap -msgid "\n# <i>emerge -an gentoolkit</i>\n# <i>emerge -uav gcc</i>\n<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\nversion and CHOST settings you've upgraded to:)</comment>\n# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n# <i>source /etc/profile</i>\n\n<comment>(Rebuilding libtool)</comment>\n# <i>emerge --oneshot -av libtool</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):27 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):84 +msgid "Introduction" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):236 -msgid "Now, we want to see which packages that revdep-rebuild will want to rebuild. Then we will tell revdep-rebuild to actually rebuild the packages. This may take some time, so have some patience." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):30 +msgid "This is about <e>upgrading</e> GCC. Downgrading GCC might have unwanted side effects. Please refer to <uri link=\"#troubleshooting\">Troubleshooting</uri> for some commonly reported issues." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):242 -#, no-wrap -msgid "\n# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):36 +msgid "The next section gives a quick primer into GCC upgrades (and how easy they are). If you want to read the lengthy reasoning behind GCC upgrades, please continue with <uri link=\"#explanation\">GCC Upgrading Explained</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(note):247 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(note):405 -msgid "It is possible that you might have problems with non-existing package versions due to them being outdated or masked. If this is the case, you will want to use the <c>--package-names</c> option to <c>revdep-rebuild</c>. This causes packages to be recompiled based on the package name, rather than the exact name and version." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):45 +msgid "Short Version" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):255 -msgid "To provide compatibility with older binary C++ applications and any packages that revdep-rebuild might have missed, <c>sys-libs/libstdc++-v3</c> needs to be merged before you unmerge GCC 3.3 from your system." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):48 +msgid "If you are upgrading GCC then you do not need to do anything except switch compiler version and rebuild libtool:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):261 -msgid "Installing libstdc++-v3 and cleaning up" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):53 +msgid "Switching GCC version" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):261 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):53 #, no-wrap -msgid "\n# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +msgid "\n# <i>emerge -u gcc</i>\n# <i>gcc-config -l</i>\n[1] i686-pc-linux-gnu-4.4.5 *\n[2] i686-pc-linux-gnu-4.5.3\n\n# <i>gcc-config 2</i>\n# <i>env-update && source /etc/profile</i>\n# <i>emerge --oneshot libtool</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):269 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):416 -msgid "Using emerge -e" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):64 +msgid "If you upgrade GCC from a version earlier than 3.4.0 (for the 3.x series) or 4.1, you will need to run <c>revdep-rebuild</c> as well:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):272 -msgid "This method, while much slower, will rebuild your whole system to ensure that everything has been rebuilt with your new compiler, and therefore safer. At first, you will upgrade GCC and libtool and switch to your new compiler." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):69 +msgid "Upgrading from a non-forward compatible GCC version" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):278 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):69 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):135 #, no-wrap -msgid "\n# <i>emerge -uav gcc</i>\n<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\nversion and CHOST settings you've upgraded to:)</comment>\n# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n# <i>source /etc/profile</i>\n\n<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this\nexample) you will have to run fix_libtool_files.sh manually</comment>\n<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</i>\n\n<comment>(Rebuilding libtool)</comment>\n# <i>emerge --oneshot -av libtool</i>\n" +msgid "\n# <i>revdep-rebuild --library libstdc++.so.5</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):295 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):377 -msgid "To provide compatibility with older binary C++ applications, <c>sys-libs/libstdc++-v3</c> needs to be merged onto your system." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):73 +msgid "There you go. Enjoy the new compiler!" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):300 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):382 -msgid "Installing libstdc++-v3" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):82 +msgid "GCC Upgrading Explained" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):300 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):382 -#, no-wrap -msgid "\n# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):87 +msgid "GCC upgrading has always been mystified, with suggestions ranging from \"You do not need to do anything\" up to \"You will need to rebuild your entire system twice\". Most of this FUD comes from the confusion surrounding ABI incompatibility. But first a quick pointer towards <c>libtool</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):304 -msgid "Now we will go about first rebuilding the system target, then the world target. This will take a very long time, depending on the number of packages that you have installed, as it will rebuild your entire toolchain and supporting system files, followed by every package on your system, including the toolchain. This is necessary to ensure that all packages have been compiled with the new toolchain, including the toolchain itself." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):97 +msgid "libtool and fix_libtool_files.sh" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):313 -msgid "Rebuilding system and world" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):100 +msgid "Earlier installments of GCC on Gentoo required you to run a specific command called <c>fix_libtool_files.sh</c>. Some time ago, the execution of this command has been integrated in the package deployments itself (through the toolchain eclass) so there is no need for users to call this themselves anymore." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):313 -#, no-wrap -msgid "\n# <i>emerge -e system</i>\n# <i>emerge -e world</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):107 +msgid "The reason we need to rebuild libtool after the upgrade of gcc versions is because of its main purpose: <e>libtool</e> is a toolset that aggregates platform-specific code in a generic interface, allowing applications to build against shared libraries without needing to deal with the platform specific aspects of shared libraries. To fulfill its function properly, the <c>libtool</c> script uses various library locations that have hardcoded GCC version information in them." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):318 -msgid "It is also safe to remove older GCC versions at this time:" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):120 +msgid "ABI Changes" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):322 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):440 ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):448 -msgid "Cleaning up" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):123 +msgid "An ABI, or <e>Application Binary Interface</e>, is a set of conventions used by all tools that deal with binary representation of programs, including compilers, assemblers, linkers and language runtime support (source: <uri link=\"http://gcc.gnu.org/onlinedocs/gcc/Compatibility.html\">GCC Binary Compatibility</uri>). When the ABI used for binary applications and libraries is changed, you will risk getting linker errors or malfunctioning programs unless you rebuild all libraries that use C++ code. Yes, C++, since most incompatibilities occur within the C++ ABI. This is also why we use the <c>revdep-rebuild</c> command against the <path>libstdc++.so.5</path> library." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):322 -#, no-wrap -msgid "\n# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):135 +msgid "Rebuilding applications linked against libstdc++.so.5" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):331 -msgid "Upgrading to GCC on a First Install" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):139 +msgid "So why is this only needed up to GCC 3.4.0/4.1 ? That's because from that version onwards, GCC uses a forward compatible ABI, which removes the need for rebuilding applications and libraries. Of course, guarantees can never be given indefinitely, but when an incompatibility occurs again, we'll definitely document it here ;-) In that case, the version of the <path>libstdc++.so</path> library will probably be increased." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):336 -msgid "A GCC upgrade on a system after installation from a stage3 tarball is a simple affair. One advantage users of new installations have is they do not have a plethora of software installed that links against the older version of GCC. The following example is for a GCC-3.3 to 3.4 upgrade. Certain parts will be different if upgrading from other versions of GCC. For example, the library names used for <c>revdep-rebuild</c> below are GCC 3.3 specific, as well as the need to install <c>libstdc++-v3</c>." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):151 +msgid "Rebuilding Everything" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):346 -msgid "If a user has not made any customizations to their system yet, then there are very few steps to get their system upgraded to a new GCC version. As with the GCC-3.3 to 3.4 upgrade, the user has a couple options. However, unlike the GCC-3.3 to 3.4 upgrade, this one is less complicated as there are fewer differences between the methods. The <uri link=\"#first-install-revdep-rebuild\">first method</uri> is faster and makes use of the <c>revdep-rebuild</c> tool from <c>gentoolkit</c>, similar to the above procedure. Using revdep-rebuild causes only packages which actually link against GCC libraries to be rebuilt, while the <uri link=\"#first-install-emerge-e\">second method</uri> causes your entire new install to be recompiled with the new GCC version and takes much longer. This second method is never required and only documented for completeness." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):154 +msgid "Some people swear that they need to rebuild every single package on their system when a new GCC version is made available. Of course, that doesn't make sense, since there are many applications that are not using GCC for their build and install process anyhow, so they would never be affected by such changes." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):361 -msgid "These first steps are common between both methods, and should be completed by everyone." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):161 +msgid "That however doesn't mean they are completely incorrect: newer GCC versions often include better support for the processors' instruction set, which might influence the performance of some applications in a positive way. Although it is expected that this improvement is generally only marginally, in some cases (especially CPU intensive applications) this might yield notable improvements." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):366 -#, no-wrap -msgid "\n# <i>emerge -uav gcc</i>\n<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\nversion and CHOST settings you've upgraded to:)</comment>\n# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n# <i>source /etc/profile</i>\n\n<comment>(Rebuilding libtool)</comment>\n# <i>emerge --oneshot -av libtool</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):169 +msgid "There are also known cases where packages need to be built with the same compiler. Although these packages are usually bumped by Gentoo simultaneously (so that they are always built with the same GCC version) cherry-picking reinstalls on these packages might prove to be troublesome. The various <path>qt-*</path> packages are a nice example on this matter." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):393 -msgid "This method requires that you first install <c>gentoolkit</c> if you have not already done so. We will then run <c>revdep-rebuild</c> to actually scan the installed packages for ones we need to rebuild, then rebuild them." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):182 +msgid "Troubleshooting" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):399 -msgid "Installing gentoolkit and running revdep-rebuild" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):184 +msgid "libstdc++.so.6: version `GLIBCXX_3.4.15' not found" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):399 -#, no-wrap -msgid "\n# <i>emerge -an gentoolkit</i>\n# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):187 +msgid "During updates, you might encounter an error like the following:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):419 -msgid "This method, while much slower, will rebuild the system target to ensure that everything has been rebuilt with your new compiler. This is not necessary, but is valid if you are also making changes to CFLAGS or other make.conf variables that will affect the system compile." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):191 +msgid "GLIBCXX_x.y.z not found" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):426 -msgid "Since we are performing these actions after an initial installation, we do not need to recompile the <c>world</c> target as we would when doing an upgrade on an already installed system. However, you may choose to perform a world update in place of the system update, to ensure that all packages are updated." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):433 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):191 #, no-wrap -msgid "\n# <i>emerge -e system</i>\n" +msgid "\ncmake_bootstrap_28021_test: /usr/lib/gcc/i486-pc-linux-gnu/4.1.2/libstdc++.so.6:\nversion `GLIBCXX_3.4.11' not found \n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):443 -msgid "It is also safe to remove older GCC versions at this time. Please substitute <c>YOUR-NEW-GCC-VERSION</c> with the actual version you've upgraded to:" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):196 +msgid "This means that you are trying to build a package with an <e>older</e> GCC version than with which some depending libraries were built. Remember when we told that the C++ ABI if forward-compatible? That is true, but it ensures only that <e>higher</e> (or same) GCC versions can be used when building applications and linking libraries (compared to the GCC version used to build those libraries)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):448 -#, no-wrap -msgid "\n# <i>emerge -aC \"<sys-devel/gcc-YOUR-NEW-GCC-VERSION\"</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):208 +msgid "Which packages are known to need a rebuild?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):457 -msgid "Common Pitfalls" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):211 +msgid "The following table gives the packages that, <e>if installed</e>, need to be rebuild and why." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):461 -msgid "It's important to disable <c>distcc</c> during upgrade. Mixing compiler versions on your nodes <e>will</e> cause build issues. This is not required for ccache, as the cache objects will be invalidated anyway." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(th):218 +msgid "Package" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):467 -msgid "Always use same GCC version for your kernel and additional kernel modules. Once you rebuild your world with new GCC, external modules (like <c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel with the new GCC to fix that." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(th):219 +msgid "Rebuild needed because ..." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):474 -msgid "If you're upgrading on a SPARC machine, make sure to rerun <c>silo -f</c> after re-emerging world to avoid possible issues." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):222 +msgid "sys-devel/libtool" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):482 -msgid "Frequent Error Messages" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):223 +msgid "libtool application has hardcoded paths towards GCC internal libraries" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):485 -msgid "If your system complains about something like <e>libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool archive</e>, please run <c>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</c> (substitute \"3.3.6\" with the version numbers from the error message, and $CHOST and <gcc-version> with your actual CHOST and GCC version)." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):229 +msgid "dev-lang/ghc" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):494 -msgid "If you see <e>error: /usr/bin/gcc-config: line 632: /etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try deleting <path>/etc/env.d/gcc/config-i686-pc-linux-gnu</path> and running <c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this if you do not have any cross-compilers set up, though." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):230 +msgid "ghc application has hardcoded paths towards GCC internal libraries" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):502 -msgid "If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, you can resume operation with <c>emerge --resume</c>. If a package fails repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any other instances of emerge in between or you will lose the resume information." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):241 +msgid "Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):509 -msgid "If you get an error message <e>spec failure: unrecognized spec option</e> while upgrading your compiler, try to switch back to your default compiler, unset the <c>GCC_SPECS</c> variable and upgrade GCC again:" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):243 +msgid "Gentoo Guides and Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):515 -msgid "Restoring primary specs" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):515 -#, no-wrap -msgid "\n# <i>gcc-config 1</i>\n# <i>source /etc/profile</i>\n# <i>unset GCC_SPECS</i>\n# <i>emerge -uav gcc</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(li):247 +msgid "<uri link=\"gcc-upgrading-upto-4.1.xml\">GCC Upgrading up to 4.1</uri>, the previous version of this document" msgstr "" #. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL diff --git a/doc/gettext/gentoo-x86-quickinstall-system.xml.pot b/doc/gettext/gentoo-x86-quickinstall-system.xml.pot index 4bc35e2..29b9a38 100644 --- a/doc/gettext/gentoo-x86-quickinstall-system.xml.pot +++ b/doc/gettext/gentoo-x86-quickinstall-system.xml.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\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" @@ -10,11 +10,11 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(version):7 -msgid "4" +msgid "6" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(date):8 -msgid "2011-08-23" +msgid "2011-09-23" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):11 @@ -44,148 +44,148 @@ msgid "\nlivecd linux # <i>cd /etc</i>\nlivecd etc # <i>nano -w fstab</i>\n/dev/ msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):58 -msgid "Configure your network in <path>/etc/conf.d/net</path>. Add the <c>net.eth0</c> init script to the default run level. If you have multiple NICs, symlink them to the <c>net.eth0</c> init script and add them to the default run level as well. Either edit <path>/etc/conf.d/net</path> with <c>nano</c> or use the following commands:" +msgid "Configure your network in <path>/etc/conf.d/net</path>. Add the <c>net.eth0</c> init script to the default run level. If you have multiple NICs, symlink them to the <c>net.eth0</c> init script and add them to the default run level as well. Don't forget to set your hostname too. Either edit <path>/etc/conf.d/net</path> and <path>/etc/conf.d/hostname</path> with <c>nano</c> or use the following commands:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):66 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):67 msgid "Configure networking" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):66 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):67 #, no-wrap -msgid "\nlivecd etc # <i>cd init.d</i>\nlivecd init.d # <i>ln -s net.lo net.eth0</i>\nlivecd init.d # <i>cd ../conf.d</i>\nlivecd conf.d # <i>echo 'config_eth0=\"192.168.1.10 netmask 255.255.255.0 brd 192.168.1.255\"' >> net</i>\nlivecd conf.d # <i>echo 'routes_eth0=\"default via 192.168.1.1\"' >> net</i>\nlivecd conf.d # <i>rc-update add net.eth0 default</i>\n<comment>(If you compiled your network card driver as a module, add it to /etc/conf.d/modules</comment>\nlivecd conf.d # <i>echo 'modules=\"r8169\"' >> /etc/conf.d/modules</i>\n<comment>(If you want to reconnect via ssh after you have rebooted your new box)</comment>\nlivecd conf.d # <i>rc-update add sshd default</i>\n" +msgid "\nlivecd etc # <i>cd init.d</i>\nlivecd init.d # <i>ln -s net.lo net.eth0</i>\nlivecd init.d # <i>cd ../conf.d</i>\nlivecd conf.d # <i>echo 'config_eth0=\"192.168.1.10 netmask 255.255.255.0 brd 192.168.1.255\"' >> net</i>\nlivecd conf.d # <i>echo 'routes_eth0=\"default via 192.168.1.1\"' >> net</i>\nlivecd conf.d # <i>echo 'hostname=\"myhostname\"' > hostname</i>\nlivecd conf.d # <i>rc-update add net.eth0 default</i>\n<comment>(If you compiled your network card driver as a module, add it to /etc/conf.d/modules</comment>\nlivecd conf.d # <i>echo 'modules=\"r8169\"' >> /etc/conf.d/modules</i>\n<comment>(If you want to reconnect via ssh after you have rebooted your new box)</comment>\nlivecd conf.d # <i>rc-update add sshd default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):79 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):81 msgid "Emerge <c>pcmciautils</c> if you need support for PCMCIA cards." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):83 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):85 msgid "Set the root password using <c>passwd</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):87 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):89 msgid "Set the root password" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):87 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):89 #, no-wrap msgid "\nlivecd conf.d # <i>passwd</i>\nNew UNIX password: <comment>type_the_password</comment>\nRetype new UNIX password: <comment>type_the_password_again</comment>\npasswd: password updated successfully\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):94 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):96 msgid "Edit <path>/etc/timezone</path> to define the time zone you used previously." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):99 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):101 msgid "Edit /etc/timezone" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):99 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):101 #, no-wrap msgid "\nEurope/Brussels\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):103 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):105 msgid "Check the system configuration in <path>/etc/rc.conf</path> and <path>/etc/conf.d/keymaps</path> and edit any of those files if required." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):108 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):110 msgid "Optional: edit some config files" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):108 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):110 #, no-wrap msgid "\nlivecd conf.d # <i>nano -w /etc/rc.conf</i>\nlivecd conf.d # <i>nano -w /etc/conf.d/keymaps</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):116 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):118 msgid "Installing System Tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):120 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):122 msgid "Install RAID and LVM2 utilities." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):124 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):126 msgid "Install RAID LVM2 tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):124 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):126 #, no-wrap -msgid "\nlivecd conf.d # <i>emerge mdadm lvm2</i>\n" +msgid "\nlivecd conf.d # <i>emerge mdadm lvm2</i>\nlivecd conf.d # <i>rc-update add mdraid boot</i>\nlivecd conf.d # <i>rc-update add lvm boot</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):131 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):135 msgid "Install a system logger like <c>syslog-ng</c> and a cron daemon like <c>vixie-cron</c>, and add them to the default run level." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):136 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):140 msgid "Cron daemons depend on an MTA. <c>mail-mta/ssmtp</c> will be pulled in as a dependency. If you want to use a more advanced MTA, you might want to install it now. If you are in a hurry, let ssmtp be installed and remove it later when you install the MTA of your choice." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):143 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):147 msgid "Install a syslogger and a cron daemon" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):143 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):147 #, no-wrap msgid "\nlivecd conf.d # <i>time emerge syslog-ng vixie-cron</i>\n\nreal 1m54.099s\nuser 1m2.630s\nsys 0m34.620s\nlivecd conf.d # <i>rc-update add syslog-ng default</i>\nlivecd conf.d # <i>rc-update add vixie-cron default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):153 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):157 msgid "Install the necessary file system tools (<c>xfsprogs</c>, <c>reiserfsprogs</c> or <c>jfsutils</c>) and networking tools (<c>dhcpcd</c> or <c>ppp</c>) if you need any." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):159 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):163 msgid "Install extra tools if required" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):159 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):163 #, no-wrap msgid "\nlivecd conf.d # <i>emerge xfsprogs</i> <comment>(If you use the XFS file system)</comment>\nlivecd conf.d # <i>emerge jfsutils</i> <comment>(If you use the JFS file system)</comment>\nlivecd conf.d # <i>emerge reiserfsprogs</i> <comment>(If you use the Reiser file system)</comment>\nlivecd conf.d # <i>emerge dhcpcd</i> <comment>(If you need a DHCP client)</comment>\nlivecd conf.d # <i>emerge ppp</i> <comment>(If you need PPPoE ADSL connectivity)</comment>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):171 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):175 msgid "Configuring the Bootloader" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):174 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):178 msgid "Emerge <c>grub</c> and configure it. Do not forget to update the necessary boot parameters if you are using an initramfs." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):179 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):183 msgid "Emerge grub and edit its configuration file" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):179 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):183 #, no-wrap msgid "\nlivecd conf.d # <i>time emerge grub</i>\n\nreal 1m4.634s\nuser 0m39.460s\nsys 0m15.280s\nlivecd conf.d # <i>nano -w /boot/grub/grub.conf</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):188 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):192 msgid "Example grub.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):188 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):192 #, no-wrap msgid "\ndefault 0\ntimeout 10\n\ntitle Gentoo\nroot (hd0,0)\nkernel /boot/kernel root=<keyval id=\"root\"></keyval>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):197 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):201 msgid "Install grub" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):197 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):201 #, no-wrap msgid "\nlivecd conf.d # <i>grub</i>\nProbing devices to guess BIOS drives. This may take a long time.\n\ngrub> <i>root (hd0,0)</i>\n Filesystem type is ext2fs, partition type 0xfd\n\ngrub> <i>setup (hd0)</i>\n Checking if \"/boot/grub/stage1\" exists... yes\n Checking if \"/boot/grub/stage2\" exists... yes\n Checking if \"/boot/grub/e2fs_stage1_5\" exists... yes\n Running \"embed /boot/grub/e2fs_stage1_5 (hd0)\"... 16 sectors are embedded.\nsucceeded\n Running \"install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/\ngrub/menu.lst\"... succeeded\nDone.\n\ngrub> <i>quit</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):217 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):221 msgid "Install grub on both disks" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):217 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):221 #, no-wrap msgid "\nlivecd conf.d # <i>grub</i>\nProbing devices to guess BIOS drives. This may take a long time.\n\ngrub> <i>root (hd0,0)</i>\n Filesystem type is ext2fs, partition type 0xfd\n\ngrub> <i>setup (hd0)</i>\n Checking if \"/boot/grub/stage1\" exists... yes\n Checking if \"/boot/grub/stage2\" exists... yes\n Checking if \"/boot/grub/e2fs_stage1_5\" exists... yes\n Running \"embed /boot/grub/e2fs_stage1_5 (hd0)\"... 16 sectors are embedded.\nsucceeded\n Running \"install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/\ngrub/menu.lst\"... succeeded\nDone.\n\ngrub> <i>root (hd1,0)</i>\n Filesystem type is ext2fs, partition type 0xfd\n\ngrub> <i>setup (hd1)</i>\n\ngrub> <i>quit</i>\n" msgstr "" diff --git a/doc/gettext/gnome-config.xml.pot b/doc/gettext/gnome-config.xml.pot index 2260d08..78e7137 100644 --- a/doc/gettext/gnome-config.xml.pot +++ b/doc/gettext/gnome-config.xml.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\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" @@ -46,11 +46,11 @@ msgid "A frequently used environment is GNOME. This HOWTO tries to describe all msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(version):27 -msgid "3" +msgid "4" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(date):28 -msgid "2011-08-13" +msgid "2011-10-23" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):31 @@ -133,139 +133,152 @@ msgid "\n# <i>emerge gnome</i>\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):122 -msgid "You can also opt for a minimal Gnome installation using <c>gnome-light</c>:" +msgid "You can also opt for a minimal Gnome installation using <c>gnome-light</c>. If you do so, you will have a lightweight Gnome installation without the additional tools that a full Gnome installation provides so you might need to install additional packages afterwards." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):126 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):129 msgid "Installing a minimal GNOME environment" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):126 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):129 #, no-wrap msgid "\n# <i>emerge gnome-light</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):130 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):133 msgid "This will take a while, so you might want to start reading all those books your mother bought you but you never opened. Done? Great, now update your environment variables:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):136 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):139 msgid "Updating environment variables" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):136 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):139 #, no-wrap msgid "\n# <i>env-update && source /etc/profile</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):140 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):143 msgid "Next we'll clean up the remaining services and user groups." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):144 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):147 msgid "Setting up the DBUS service" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):144 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):147 #, no-wrap msgid "\n# <i>/etc/init.d/dbus start</i>\n# <i>rc-update add dbus default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):149 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):152 msgid "Check if the <e>plugdev</e> group exists. If it does, it is adviseable to make yourself member of that group, but this is optional (the group is not that common anymore)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):155 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):158 msgid "Checking and adding users to plugdev" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):155 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):158 #, no-wrap msgid "\n~# <i>getent group plugdev</i>\nplugdev:x:104:\n\n<comment># Substitute yourUserName with your user name ;-)</comment>\n~# <i>gpasswd -a yourUserName plugdev</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):166 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):169 msgid "First Impressions" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):169 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):172 msgid "Let us first take a look at what we just built. Exit your root shell and log on as a regular user. We will configure our session to run GNOME when we issue the <c>startx</c> command (see also <uri link=\"/doc/en/xorg-config.xml#using_startx\">Using startx</uri> in the <uri link=\"/doc/en/xorg-config.xml\">X Server Configuration Howto</uri>):" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):177 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):180 msgid "Setting GNOME as the default desktop environment" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):177 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):180 #, no-wrap msgid "\n$ <i>echo \"exec gnome-session\" > ~/.xinitrc</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):181 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):184 msgid "Starting with <c>gnome-base/gnome-session-2.26.2</c>, you will need to prepend the XDG_MENU_PREFIX variable to get the Gnome menus if you're using the <path>~/.xinitrc</path> method to start your desktop. (If you're not using <path>~/.xinitrc</path>, it will be handled automatically for you; no additional configuration is needed.)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):189 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):192 msgid "Prepending XDG_MENU_PREFIX to ~/.xinitrc" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):189 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):192 #, no-wrap msgid "\n$ <i>sed -i '1i\\export XDG_MENU_PREFIX=gnome-' ~/.xinitrc</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):193 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):196 msgid "Now start your graphical environment by running <c>startx</c>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):197 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):200 msgid "Starting GNOME" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):197 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):200 #, no-wrap msgid "\n$ <i>startx</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):201 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):204 msgid "If all goes well, you should be greeted by GNOME. Congratulations. Now let us take a look at how you can configure GNOME to suit your needs." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):210 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):213 msgid "Configuring GNOME" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):212 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):215 msgid "GNOME's Graphical Login Manager" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):215 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):218 msgid "If you want the GNOME Display Manager (GDM) to run automatically when you boot (so you can log on graphically), you must add the <c>xdm</c> init script to the default runlevel:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):221 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):224 msgid "Adding xdm to the default runlevel" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):221 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):224 #, no-wrap msgid "\n# <i>rc-update add xdm default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):225 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):228 msgid "Now edit <path>/etc/conf.d/xdm</path> and alter the DISPLAYMANAGER variable." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):229 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):232 msgid "Editing /etc/conf.d/xdm" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):229 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):232 #, no-wrap msgid "\nDISPLAYMANAGER=\"gdm\"\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):233 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):236 +msgid "If you installed Gnome using the <c>gnome-light</c> package, you will need to install <c>gdm</c> too (as it is not defined as part of the <c>gnome-light</c> package)." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):242 +msgid "Installing the gdm application" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):242 +#, no-wrap +msgid "\n# <i>emerge gdm</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):246 msgid "If you reboot now, the GNOME Display Manager will prompt you for your username and password and will default to using GNOME as Desktop Environment (even though you will have the option of selecting a different one of course, choosing from those available in <path>/usr/share/xsessions/</path>). Thus, if you use GDM, you don't need to edit <path>~/.xinitrc</path>." msgstr "" diff --git a/doc/gettext/power-management-guide.xml.pot b/doc/gettext/power-management-guide.xml.pot index 6001bf6..06fe08f 100644 --- a/doc/gettext/power-management-guide.xml.pot +++ b/doc/gettext/power-management-guide.xml.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\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" @@ -18,1310 +18,486 @@ msgid "Author" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):9 -msgid "earthwings@gentoo.org" +msgid "swift" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):9 -msgid "Dennis Nienhüser" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(abstract):12 +msgid "In recent years, power management has become one of the differentiating features in the quest for finding the perfect laptop. Yet, the operating system must support the various power saving functionalities too. In this guide, we cover how to setup your Gentoo installation so it manages power-hungry resources in a flexible yet automated manner." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):11 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):14 -msgid "Editor" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(version):24 +msgid "5" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):12 -msgid "chriswhite@gentoo.org" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(date):25 +msgid "2011-09-22" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):12 -msgid "Chris White" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):15 -msgid "nightmorph" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(abstract):18 -msgid "Power Management is the key to extend battery run time on mobile systems like laptops. This guide assists you setting it up on your laptop." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(version):27 -msgid "4" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(date):28 -msgid "2011-08-17" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):31 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):28 msgid "Introduction" msgstr "" -#. Remove this note after 6 months - ETA 01/02/2012 -#. By then, we can assume that OpenRC migrations are not that frequent -#. anymore and this note can be dropped. -#. ~ Sven Vermeulen -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(impo):41 -msgid "Since the introduction of OpenRC, the <c>pmg_switch_runlevel.sh</c> script needs to be updated. If you have issues after the OpenRC upgrade, please update this script according to this guide." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):30 +msgid "About this document..." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):47 -msgid "Capacity and lifetime of laptop batteries have improved much in the last years. Nevertheless modern processors consume much more energy than older ones and each laptop generation introduces more devices hungry for energy. That's why Power Management is more important than ever. Increasing battery run time doesn't necessarily mean buying another battery. Much can be achieved applying intelligent Power Management policies." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):33 +msgid "This document describes the setup of power management features on your laptop. Although some of the information in this guide can be applied to power management for servers, it is not the intention of this document to go that route. Please be careful when applying this on a non-laptop system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):59 -msgid "A Quick Overview" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):40 +msgid "Within this document, we will focus primarily on the laptop mode tools since it offers a complete set of functionalities. However, we will also refer to other tools that might offer a more detailed approach on individual settings. In such cases, you will need to disable the feature from the laptop mode tools so that both tools do not fight over the same resource control." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):62 -msgid "Please notice that this guide describes Power Management for <e>laptops</e>. While some sections might also suite for <e>servers</e>, others do not and may even cause harm. Please do not apply anything from this guide to a server unless you really know what you are doing." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):51 +msgid "About laptop_mode" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):69 -msgid "As this guide has become rather long, here's a short overview helping you to find your way through it." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):54 +msgid "The <c>laptop_mode</c> setting is an in-kernel configuration setting that optimizes I/O, allowing disks to spin down properly (and not be woken up immediately afterwards for queued operations)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):74 -msgid "The <uri link=\"#doc_chap2\">Prerequisites</uri> chapter talks about some requirements that should be met before any of the following device individual sections will work. This includes BIOS settings, kernel configuration and some simplifications in user land. The following three chapters focus on devices that typically consume most energy - processor, display and hard drive. Each can be configured separately. <uri link=\"#doc_chap3\">CPU Power Management</uri> shows how to adjust the processor's frequency to save a maximum of energy without losing too much performance. A few different tricks prevent your hard drive from working unnecessarily often in <uri link=\"#doc_chap5\">Disk Power Management</uri> (decreasing noise level as a nice side effect). Some notes on graphics cards, Wireless LAN and USB finish the device section in <uri link=\"#doc_chap6\">Power Management For Other Devices</uri> while another chapter is dedicated to the (rather experimental) <uri link=\"#doc_chap7\">sleep states</uri>. Last not least <uri link=\"#doc_chap8\">Troubleshooting</uri> lists common pitfalls." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):63 +msgid "About laptop-mode-tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):95 -msgid "Power Budget For Each Component" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):66 +msgid "The <e>Laptop Mode Tools</e> is a software package (<c>app-laptop/laptop-mode-tools</c>) which allows the user to optimize power saving functions. It allows managing the <c>laptop_mode</c> setting in the Linux kernel, but has additional features allowing you to tweak other power-related settings on the system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:link):99 -msgid "/images/energy-budget.png" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):79 +msgid "Linux Kernel Configuration" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:short):99 -msgid "Which component consumes how much energy?" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):81 +msgid "Minimum kernel setup" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:caption):99 -msgid "Power budget for each component" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):84 +msgid "There are different kernel sources in Portage. We recommend using <c>gentoo-sources</c>, but if you want advanced hibernation support you might need <c>tuxonice-sources</c>. To enable proper power management features in the Linux kernel, enable at least the following settings:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):101 -msgid "Nearly every component can operate in different states - off, sleep, idle, active to name a few - consuming a different amount of energy. Major parts are consumed by the LCD display, CPU, chipset and hard drives. Often one is able to activate OS-independent Power Management in the BIOS, but an intelligent setup in the operating system adapting to different situations can achieve much more." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):114 -msgid "Prerequisites" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):91 +msgid "Minimum kernel setup for Power Management (Kernel 2.6)" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):118 -msgid "Before discussing the details of making individual devices Power Management aware, make sure certain requirements are met. After controlling BIOS settings, some kernel options want to be enabled - these are in short ACPI, sleep states and CPU frequency scaling. As power saving most of the time comes along with performance loss or increased latency, it should only be enabled when running on batteries. That's where a new runlevel <e>battery</e> comes in handy." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):130 -msgid "The BIOS Part" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):133 -msgid "First have a look into your BIOS Power Management settings. The best way is to combine BIOS and operating system policies, but for the moment it's better to disable most of the BIOS part. This makes sure it doesn't interfere with your policies. Don't forget to re-check BIOS settings after you configured everything else." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):144 -msgid "Setting USE Flags" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):147 -msgid "Please check that the <c>acpi</c> USE flag is set in <path>/etc/make.conf</path>. Other USE flags that might be interesting for your system are <c>apm</c>, <c>lm_sensors</c>, <c>nforce2</c>, <c>nvidia</c>, <c>pmu</c>. See <path>/usr/portage/profiles/use*.desc</path> for details. If you forgot to set one of these flags, you can recompile affected packages using the <c>--newuse</c> flag in <c>emerge</c>, see <c>man emerge</c>." +msgid "Don't forget to enable the CPU frequency scaling driver for your CPU, located right after the <e>ACPI Processor P-States driver</e> mentioned above." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):159 -msgid "Configuring The Kernel" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):123 +msgid "Build and install the new kernel (if necessary) and reboot." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):162 -msgid "ACPI (Advanced Configuration and Power Interface) support in the kernel is still work in progress. Using a recent kernel will make sure you'll get the most out of it." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):169 +msgid "Using Laptop Mode Tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):168 -msgid "There are different kernel sources in Portage. I'd recommend using <c>gentoo-sources</c> or <c>tuxonice-sources</c>. The latter contains patches for TuxOnIce, see the chapter about <uri link=\"#doc_chap7\">sleep states</uri> for more details. When configuring the kernel, activate at least these options:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):171 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):469 +msgid "Installation" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):175 -msgid "Minimum kernel setup for Power Management (Kernel 2.6)" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):174 +msgid "It comes to no surprise that installation of the <e>Laptop Mode Tools</e> software is easily done through <c>emerge laptop-mode-tools</c>. However, this package takes on additional, optional settings through USE flag configuration. So let's first take a look at the supported USE flags and what they mean to the package." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):175 -#, no-wrap -msgid "\nPower management and ACPI options --->\n[*] Power Management support\n [ ] Software Suspend\n\n ACPI( Advanced Configuration and Power Interface ) Support --->\n [ ] Deprecated /proc/acpi/ files\n [*] AC Adapter\n [*] Battery\n <M> Button\n <M> Video\n [ ] Generic Hotkey\n <M> Fan\n <M> Processor\n <M> Thermal Zone\n < > ASUS/Medion Laptop Extras\n < > IBM ThinkPad Laptop Extras\n < > Toshiba Laptop Extras\n (0) Disable ACPI for systems before Jan 1st this year\n [ ] Debug Statements\n [*] Power Management Timer Support\n < > ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL)\n\n CPU Frequency Scaling --->\n [*] CPU Frequency scaling\n [ ] Enable CPUfreq debugging\n < > CPU frequency translation statistics\n [ ] CPU frequency translation statistics details\n Default CPUFreq governor (userspace)\n <*> 'performance' governor\n <*> 'powersave' governor\n <*> 'ondemand' cpufreq policy governor\n <*> 'conservative' cpufreq governor\n <*> CPU frequency table helpers\n <M> ACPI Processor P-States driver\n <*> <i>CPUFreq driver for your processor</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):184 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):481 +msgid "USE flag" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):213 -msgid "Decide yourself whether you want to enable Software Suspend, and Sleep States (see below). If you own an ASUS, Medion, IBM Thinkpad or Toshiba laptop, enable the appropriate section." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):185 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):482 +msgid "Description" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):219 -msgid "The kernel has to know how to enable CPU frequency scaling on your processor. As each type of CPU has a different interface, you've got to choose the right driver for your processor. Be careful here - enabling <c>Intel Pentium 4 clock modulation</c> on a Pentium M system will lead to strange results for example. Consult the kernel documentation if you're unsure which one to take." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):186 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):483 +msgid "Suggested when..." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):227 -msgid "Compile your kernel, make sure the right modules get loaded at startup and boot into your new ACPI-enabled kernel. Next run <c>emerge sys-power/acpid</c> to get the acpi daemon. This one informs you about events like switching from AC to battery or closing the lid. Make sure the modules are loaded if you didn't compile them into the kernel and start acpid by executing <c>/etc/init.d/acpid start</c>. Run <c>rc-update add acpid default</c> to load it on startup. You'll soon see how to use it." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):189 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):486 +msgid "acpi" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):237 -msgid "Installing acpid" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):190 +msgid "Depend on <c>sys-power/acpid</c> so that changes in the system are captured and power saving features are automatically enabled/disabled." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):237 -#, no-wrap -msgid "\n# <i>emerge sys-power/acpid</i>\n# <i>/etc/init.d/acpid start</i>\n# <i>rc-update add acpid default</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):194 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):491 +msgid "your laptop is not too old (~ year 2003 and later)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):246 -msgid "Creating A \"battery\" Runlevel" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):197 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):494 +msgid "apm" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):249 -msgid "The default policy will be to enable Power Management only when needed - running on batteries. To make the switch between AC and battery convenient, create a runlevel <c>battery</c> that holds all the scripts starting and stopping Power Management." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):198 +msgid "Depend on <c>sys-apps/apmd</c> so that changes in the system are captured and power saving features are automatically enabled/disabled." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):256 -msgid "You can safely skip this section if you don't like the idea of having another runlevel. However, skipping this step will make the rest a bit trickier to set up. The next sections assume a runlevel <c>battery</c> exists." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):202 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):499 +msgid "your laptop is very old" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):262 -msgid "Creating a battery runlevel" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):205 +msgid "bluetooth" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):262 -#, no-wrap -msgid "\n# <i>cd /etc/runlevels</i>\n# <i>cp -a default battery</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):206 +msgid "Depend on <c>net-wireless/bluez</c>, enabling the <c>laptop-mode-tools</c> to manage bluetooth settings (enabling/disabling the service based on battery availability)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):267 -msgid "Finished. Your new runlevel <c>battery</c> contains everything like <c>default</c>, but there is no automatic switch between both yet. Time to change it." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):211 +msgid "your laptop (and kernel) supports bluetooth" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):276 -msgid "Reacting On ACPI Events" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):214 +msgid "scsi" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):279 -msgid "Typical ACPI events are closing the lid, changing the power source or pressing the sleep button. An important event is changing the power source, which should cause a runlevel switch. A small script will take care of it." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):215 +msgid "Depend on <c>sys-apps/sdparm</c>, enabling the <c>laptop-mode-tools</c> to manage SCSI (<e>and not</e> SATA) disk parameters." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):285 -msgid "First you need a script which changes the runlevel to <c>default</c> respectively <c>battery</c> depending on the power source. The script uses the <c>on_ac_power</c> command from <c>sys-power/pm-utils</c> - make sure the package is installed on your system." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):219 +msgid "your laptop uses SCSI disks" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):292 -msgid "Installing pm-utils" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):223 +msgid "As you can see, there are two USE flags that seem to collide: <c>acpi</c> and <c>apm</c>. So what's the deal there?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):292 -#, no-wrap -msgid "\n# <i>emerge pm-utils</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):229 +msgid "The <c>apm</c> USE flag enables support for <e>Advanced Power Management</e>, an older (before year 2000) standard for power management features within a system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):296 -msgid "You are now able to determine the power source by executing <c>on_ac_power && echo AC available || echo Running on batteries</c> in a shell. The script below is responsible for changing runlevels. Save it as <path>/etc/acpi/actions/pmg_switch_runlevel.sh</path>." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):234 +msgid "The <c>acpi</c> USE flag enables support for <e>Advanced Configuration and Power Interface</e>, the successor of APM. All modern laptops support ACPI." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):303 -msgid "/etc/acpi/actions/pmg_switch_runlevel.sh" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):240 +msgid "Depending on your system, you will either need <c>acpi</c> or <c>apm</c> set. In the remainder of this guide, we assume that your laptop is recent enough to use ACPI." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):303 -#, no-wrap -msgid "\n#!/bin/bash\n\n# BEGIN configuration\nRUNLEVEL_AC=\"default\"\nRUNLEVEL_BATTERY=\"battery\"\n\nif [ -x /usr/bin/logger ]; then\n LOGGER=\"/usr/bin/logger -s -p daemon.info -t /etc/acpi/actions/pmg_switch_runlevel.sh\"\nelse\n LOGGER=\"/bin/echo\"\nfi\n\nON_AC_POWER=/usr/bin/on_ac_power\n# END configuration\n\n\nif [ ! -d \"/etc/runlevels/${RUNLEVEL_AC}\" ]\nthen\n ${LOGGER} \"${0}: Runlevel ${RUNLEVEL_AC} does not exist. Aborting.\"\n exit 1\nfi\n\nif [ ! -d \"/etc/runlevels/${RUNLEVEL_BATTERY}\" ]\nthen\n ${LOGGER} \"${0}: Runlevel ${RUNLEVEL_BATTERY} does not exist. Aborting.\"\n exit 1\nfi\n\nif ${on_ac_power}\nthen\n if [[ \"$(rc-status --runlevel)\" != \"${RUNLEVEL_AC}\" ]]\n then\n ${LOGGER} \"Switching to ${RUNLEVEL_AC} runlevel\"\n /sbin/rc ${RUNLEVEL_AC}\n fi\nelif [[ \"$(rc-status --runlevel)\" != \"${RUNLEVEL_BATTERY}\" ]]\nthen\n ${LOGGER} \"Switching to ${RUNLEVEL_BATTERY} runlevel\"\n /sbin/rc ${RUNLEVEL_BATTERY}\nfi\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):246 +msgid "So, with the USE flags set, let's install <c>laptop-mode-tools</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):346 -msgid "Dont forget to run <c>chmod +x /etc/acpi/actions/pmg_switch_runlevel.sh</c> to make the script executable. The last thing that needs to be done is calling the script whenever the power source changes. That's done by catching ACPI events with the help of <c>acpid</c>. First you need to know which events are generated when the power source changes. The events are called <c>ac_adapter</c> and <c>battery</c> on most laptops, but it might be different on yours." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):250 +msgid "If you have USE=\"acpi\" set, the installation will pull in <c>acpid</c>. However, the current stable ACPI daemon (2.0.9) does not support the new ACPI interfaces within the Linux kernel (using the netlink interface). As such, we recommend unmasking <c>sys-power/acpid-2.0.12</c> (or higher). For more information about unmasking packages, please read <uri link=\"/doc/en/handbook/handbook-amd64.xml?part=3&chap=3\">Mixing Software Branches</uri> in the Gentoo Handbook." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):356 -msgid "Determining ACPI events for changing the power source" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):260 +msgid "Installing laptop-mode-tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):356 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):260 #, no-wrap -msgid "\n# <i>tail -f /var/log/messages | grep \"ACPI event\"</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):360 -msgid "Run the command above and pull the power cable. You should see something like this:" +msgid "\n# <i>emerge laptop-mode-tools</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):365 -msgid "Sample output for power source changes" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):267 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):564 +msgid "Configuration" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):365 -#, no-wrap -msgid "\n[Tue Sep 20 17:39:06 2005] ACPI event \"ac_adapter AC 00000080 00000000\"\n[Tue Sep 20 17:39:06 2005] ACPI event \"battery BAT0 00000080 00000001\"\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):270 +msgid "Having <c>laptop-mode-tools</c> installed on your system does not automatically enable the power management features that you might need. To configure the package, first take a look at <path>/etc/laptop-mode/laptop-mode.conf</path>. This is the main configuration file for the package and is pretty well described (through comments)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):370 -msgid "The interesting part is the quoted string after <c>ACPI event</c>. It will be matched by the event line in the files you are going to create below. Don't worry if your system generates multiple events or always the same. As long as any event is generated, runlevel changing will work." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):278 +msgid "But it is not the only configuration file to work with. The Laptop Mode Tools package supports plugins (or modules) which have their own configuration file(s). These files are located in <path>/etc/laptop-mode/conf.d</path> and are named after the module they represent (such as <path>intel-sata-powermgmt.conf</path>)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):377 -msgid "/etc/acpi/events/pmg_ac_adapter" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):286 +msgid "Now, one of the important settings in each configuration file is if the Laptop Mode Tools package should govern a particular setting or not. This is important when you want to combine <c>laptop-mode-tools</c> with other services like <c>cpufreqd</c>. In this example case, you will need to set <c>CONTROL_CPU_FREQUENCY=0</c>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):377 -#, no-wrap -msgid "\n<comment># replace \"ac_adapter\" below with the event generated on your laptop</comment>\n<comment># For example, ac_adapter.* will match ac_adapter AC 00000080 00000000</comment>\nevent=ac_adapter.*\naction=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):294 +msgid "Editing /etc/laptop-mode/conf.d/cpufreq.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):384 -msgid "/etc/acpi/events/pmg_battery" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):384 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):294 #, no-wrap -msgid "\n<comment># replace \"battery\" below with the event generated on your laptop</comment>\n<comment># For example, battery.* will match battery BAT0 00000080 00000001</comment>\nevent=battery.*\naction=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n" +msgid "\n# <i>nano -w /etc/laptop-mode/conf.d/cpufreq.conf</i>\nCONTROL_CPU_FREQUENCY=<i>0</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):391 -msgid "Finally acpid has to be restarted to recognize the changes." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):299 +msgid "The next few sections will help you configure <c>laptop-mode-tools</c> to suit your needs. When you are finished, start the <c>laptop_mode</c> service and make sure it is started when you boot up your system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):395 -msgid "Finishing runlevel switching with acpid" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):305 +msgid "Starting the laptop_mode service" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):395 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):305 #, no-wrap -msgid "\n# <i>/etc/init.d/acpid restart</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):399 -msgid "Give it a try: Plug AC in and out and watch syslog for the \"Switching to AC mode\" or \"Switching to battery mode\" messages. See the <uri link=\"#doc_chap8\">Troubleshooting section</uri> if the script is not able to detect the power source correctly." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):406 -msgid "Due to the nature of the event mechanism, your laptop will boot into runlevel <c>default</c> regardless of the AC/battery state. This is fine when running from AC, but we'd like to boot into the battery runlevel otherwise. One solution would be to add another entry to the boot loader with the parameter <c>softlevel=battery</c>, but it's likely to forget choosing it. A better way is faking an ACPI event in the end of the boot process and letting <path>pmg_switch_runlevel.sh</path> script decide whether a runlevel change is necessary. Create a <path>/etc/local.d/battery.start</path> file with the following contents:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):418 -msgid "Runlevel adjustment at boot time through local.d/battery.start" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):418 -#, no-wrap -msgid "\n#!/bin/sh\n<comment># Fake acpi event to switch runlevel if running on batteries</comment>\n/etc/acpi/actions/pmg_switch_runlevel.sh \"battery/battery\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):424 -msgid "Don't forget to mark the file as executable (<c>chmod +x /etc/local.d/battery.start</c>). Prepared like this you can activate Power Management policies for individual devices." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):435 -msgid "CPU Power Management" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):439 -msgid "Mobile processors can operate at different frequencies. Some allow changing voltage as well. Most of the time your CPU doesn't need to run at full speed and scaling it down will save much energy - often without any performance decrease." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):449 -msgid "Some Technical Terms" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):452 -msgid "CPU frequency scaling brings up some technical terms that might be unknown to you. Here's a quick introduction." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):457 -msgid "First of all, the kernel has to be able to change the processor's frequency. The <b>CPUfreq processor driver</b> knows the commands to do it on your CPU. Thus it's important to choose the right one in your kernel. You should already have done it above. Once the kernel knows how to change frequencies, it has to know which frequency it should set. This is done according to the <b>policy</b> which consists of a <b>CPUfreq policy</b> and a <b>governor</b>. A CPUfreq policy are just two numbers which define a range the frequency has to stay between - minimal and maximal frequency. The governor now decides which of the available frequencies in between minimal and maximal frequency to choose. For example, the <b>powersave governor</b> always chooses the lowest frequency available, the <b>performance governor</b> the highest one. The <b>userspace governor</b> makes no decision but chooses whatever the user (or a program in userspace) wants - which means it reads the frequency from <path>/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):474 -msgid "This doesn't sound like dynamic frequency changes yet and in fact it isn't. Dynamics however can be accomplished with various approaches. For example, the <b>ondemand governor</b> makes its decisions depending on the current CPU load. The same is done by various userland tools like <c>cpudyn</c>, <c>cpufreqd</c>, <c>powernowd</c> and many more. ACPI events can be used to enable or disable dynamic frequency changes depending on power source." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):486 -msgid "Setting The Frequency" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):489 -msgid "Decreasing CPU speed and voltage has two advantages: On the one hand less energy is consumed, on the other hand there is thermal improvement as your system doesn't get as hot as running on full speed. The main disadvantage is obviously the loss of performance. Decreasing processor speed is a trade off between performance loss and energy saving." +msgid "\n# <i>/etc/init.d/laptop_mode start</i>\n# <i>rc-update add laptop_mode default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):497 -msgid "Not every laptop supports frequency scaling. If unsure, have a look at the list of supported processors in the <uri link=\"#doc_chap8\">Troubleshooting</uri> section to verify yours is supported." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):313 +msgid "How does laptop-mode-tools work" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):503 -msgid "It's time to test whether CPU frequency changing works. Let's install another tool: <c>sys-power/cpufrequtils</c>." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):316 +msgid "When running the <c>laptop_mode</c> service, the software will check in which state your system is in. The states are defined as:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):508 -msgid "Checking CPU frequency" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):322 +msgid "<e>Battery</e>, in the configuration files using the <c>BATT_</c> prefix, is active when the system is running on battery power" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):508 -#, no-wrap -msgid "\n# <i>emerge cpufrequtils</i>\n# <i>cpufreq-info</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):326 +msgid "<e>AC</e>, in the configuration files using the <c>AC_</c> prefix, is active when the system is running on AC power" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):513 -msgid "Here is an example output:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):330 +msgid "<e>Laptop Mode</e>, in the configuration files using the <c>LM_</c> prefix, is active when <e>laptop mode</e> is enabled" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):517 -msgid "Sample output from cpufreq-info" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):334 +msgid "<e>No Laptop Mode</e>, in the configuration files using the <c>NOLM_</c> prefix, is active when <e>laptop mode</e> is disabled" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):517 -#, no-wrap -msgid "\ncpufrequtils 0.3: cpufreq-info (C) Dominik Brodowski 2004\nReport errors and bugs to linux@brodo.de, please.\nanalyzing CPU 0:\n driver: centrino\n CPUs which need to switch frequency at the same time: 0\n hardware limits: 600 MHz - 1.40 GHz\n available frequency steps: 600 MHz, 800 MHz, 1000 MHz, 1.20 GHz, 1.40 GHz\n available cpufreq governors: conservative, ondemand, powersave, userspace, performance\n current policy: frequency should be within 924 MHz and 1.40 GHz.\n The governor \"performance\" may decide which speed to use\n within this range.\n current CPU frequency is 1.40 GHz.\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):340 +msgid "The <c>AC/BATT_</c> and <c>LM/NOLM_</c> prefixes can be combined (so you can have a <c>AC_LM_</c> prefix)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):532 -msgid "Now play around with <c>cpufreq-set</c> to make sure frequency switching works. Run <c>cpufreq-set -g ondemand</c> for example to activate the ondemand governor and verify the change with <c>cpufreq-info</c>. If it doesn't work as expected, you might find help in the <uri link=\"#doc_chap8\">Troubleshooting section</uri> in the end of this guide." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):345 +msgid "When the <c>laptop_mode</c> service is started, it will switch modes based on events that occur (and of course based on the configuration settings). For instance, the setting <c>ENABLE_LAPTOP_MODE_ON_BATTERY=1</c> will make sure that the laptop mode tools switch to <e>laptop mode</e> when battery power is used. If that is the case, then the settings starting with <c>LM_</c>, <c>LM_BATT_</c>, <c>BATT_LM_</c> and <c>BATT_</c> will be used." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):540 -msgid "<c>cpufrequtils</c> can operate in an automatic mode (when you use the <b>ondemand</b> governor), you can also switch to the <b>userspace</b> governor if you want to manually set a specific speed. You can also statically set your CPU to its highest or lowest frequency by using the <b>performance</b> and <b>powersave</b> governors, respectively." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):354 +msgid "To make sure settings to not collide, it is not allowed to have overlapping settigns. In the next example, the first set (for <c>CPU_MAXFREQ</c>) is valid, but the second one (for <c>CPU_GOVERNOR</c>) isn't." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):548 -msgid "Changing CPU speeds" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):360 +msgid "Colliding settings" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):548 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):360 #, no-wrap -msgid "\n<comment>(Set the highest available frequency)</comment>\n# <i>cpufreq-set -g performance</i>\n<comment>(Set the lowest available frequency)</comment>\n# <i>cpufreq-set -g powersave</i>\n<comment>(Set a specific frequency)</comment>\n# <i>cpufreq-set -g userspace</i>\n# <i>cpufreq-set -f 2.00ghz</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):561 -msgid "Other CPU Speed Utilities" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):564 -msgid "While <c>cpufrequtils</c> may be the best all-around program, there are some other choices available in Portage. The following table gives a quick overview of available CPU speed utilities. It's roughly separated in three categories <b>kernel</b> for approaches that only need kernel support, <b>daemon</b> for programs that run in the background and <b>graphical</b> for programs that provide a GUI for easy configuration and changes." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):575 -msgid "Name" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):576 -msgid "Category" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):577 -msgid "Switch decision" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):578 -msgid "Kernel governors" +msgid "\n<comment>## Valid set</comment>\nBATT_CPU_MAXFREQ=fastest\nLM_AC_CPU_MAXFREQ=fastest\nNOLM_AC_CPU_MAXFREQ=fastest\n\n<comment>## Invalid set</comment>\nBATT_CPU_MINFREQ=fastest\nLM_AC_CPU_MINFREQ=fastest\n<comment># The following includes AC and BATT, but BATT is already defined</comment>\nNOLM_CPU_MINFREQ=fastest\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):579 -msgid "Further governors" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):376 +msgid "Configuring CPU frequency management" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):580 -msgid "Comments" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):379 +msgid "The support for CPU frequency management in the laptop mode tools allows switching frequencies. It supports setting the CPU frequency governor, minimum frequency and maximum frequency. The configuration file used here is <path>/etc/laptop-mode/conf.d/cpufreq.conf</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):583 -msgid "'ondemand' governor" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):386 +msgid "The <e>CPU frequency governor</e> is a kernel-level policy that defines how the kernel will select the CPU frequency. We already selected the governors we want to use in the kernel configuration earlier. Let's recap:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):584 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):598 -msgid "Kernel" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):393 +msgid "<c>performance</c> always picks the highest frequency" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):585 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):599 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):614 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):640 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):664 -msgid "CPU load" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):396 +msgid "<c>powersave</c> always picks the lowest frequency" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):586 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):587 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):600 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):601 -msgid "N.A." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):399 +msgid "<c>userspace</c> does not pick anything, but let the user decide (or any process that the user is running that will decide for the user)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):588 -msgid "Chooses maximal frequency on CPU load and slowly steps down when the CPU is idle. Further tuning through files in <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/</path>. Still requires userland tools (programs, scripts) if governor switching or similar is desired." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):403 +msgid "<c>ondemand</c> will scale the CPU frequency up to the highest frequency when load is available" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):597 -msgid "'conservative' governor" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):407 +msgid "<c>conservative</c> will scale the CPU frequency up gradually when load is available" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):602 -msgid "Unlike the ondemand governor, conversative doesn't jump to maximum frequency when CPU load is high, but increases the frequency step by step. Further tuning through files in <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/</path>. Still requires userland tools (programs, scripts) if governor switching or similar is desired." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):413 +msgid "When switching between AC or battery, or (no) laptop mode, the appropriate governor (as well as its minimum and maximum frequency) is selected." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):612 -msgid "http://mnm.uib.es/~gallir/cpudyn/" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):421 +msgid "Configuring display brightness" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):612 -msgid "cpudyn" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):613 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):624 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):639 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):652 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):663 -msgid "Daemon" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):615 -msgid "Performance, powersave" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):616 -msgid "Dynamic" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):617 -msgid "Also supports disk standby - notice however that <e>laptop mode</e> in most cases will do a better job." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):623 -msgid "http://sourceforge.net/projects/cpufreqd/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):623 -msgid "cpufreqd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):625 -msgid "Battery state, CPU load, temperature, running programs and more" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):626 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):688 -msgid "All available" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):627 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):641 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):654 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):665 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):676 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):677 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):678 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):689 -msgid "None" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):424 +msgid "With <path>/etc/laptop-mode/conf.d/lcd-brightness.conf</path>, you can have the laptop mode tools govern the brightness of your LCD screen." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):628 -msgid "Sophisticated (but somewhat complicated) setup. Extendible through plugins like sensor monitoring (lm_sensors) or coordinating some NVidia based graphics card memory and core. Cpufreqd is SMP aware and can optionally be controlled manually at runtime." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):429 +msgid "The file currently uses the <path>/proc/acpi/video/VID/LCD/brightness</path> file to set brightness values. Recent kernels do not provide this anymore - you will need to adjust this to <path>/sys/class/backlight/acpi_video0/brightness</path> instead." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):637 -msgid "http://www.deater.net/john/powernowd.html" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):436 +msgid "The values you can use are between 0 and 15, with 0 being the lowest brightness value." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):637 -msgid "powernowd" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):444 +msgid "Configuring other services" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):642 -msgid "Passive, sine, aggressive" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):447 +msgid "An interesting feature of <c>laptop-mode-tools</c> is to support reloading particular services (like the system logger) after switching its configuration file. This is handled through <path>/etc/laptop-mode/conf.d/configuration-file-control.conf</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):643 -msgid "Supports SMP." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):454 +msgid "If enabled, the <c>laptop_mode</c> application will switch the configuration file(s) of the mentioned services with the same file, but suffixed with <path>-nolm-ac</path>, <path>-lm-ac</path> or <path>-batt</path>. It willl then signal or reload the appropriate services so they can use the new configuration file." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):650 -msgid "http://projects.simpledesigns.com.pl/project/ncpufreqd/" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):467 +msgid "Using cpufreqd" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):650 -msgid "ncpufreqd" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):472 +msgid "The <c>cpufreqd</c> application allows you to manage CPU frequencies in a more granular approach then what <c>laptop-mode-tools</c> supports. But before we dive into the installation of <c>cpufreqd</c>, let's first look at the USE flags it supports." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):653 -msgid "Temperature" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):487 +msgid "Enable support for ACPI, allowing <c>cpufreqd</c> to be notified about specific events as well as govern power through the ACPI interface" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):655 -msgid "Powersave, performance" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):495 +msgid "Enable support for APM, allowing <c>cpufreqd</c> to be notified about specific events as well as govern power through the APM interface" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):656 -msgid "Toggles the used governor between performance and powersave depending on system temperature. Very useful on laptops with notorious heat problems." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):502 +msgid "lm_sensors" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):662 -msgid "http://www.goop.org/~jeremy/speedfreq/" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):503 +msgid "Enable support for the Linux hardware sensors (through <c>sys-apps/lm_sensors</c>), allowing to switch profiles based on hardware sensor results" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):662 -msgid "speedfreq" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):508 +msgid "you want to use advanced events through lm_sensors" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):666 -msgid "Dynamic, powersave, performance, fixed speed" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):513 +msgid "nforce2" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):667 -msgid "Easy to configure with a nice client/server interface. Requires a 2.6 kernel. Unmaintained, broken and thus removed from Portage. Please switch to cpufreqd if you're still using it." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):514 +msgid "Enable support for NForce, allowing <c>cpufreqd</c> to change the NForce FSB clock and video card frequency" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):674 -msgid "http://cpuspeedy.sourceforge.net/" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):518 +msgid "you have an NVidia graphical card based on the NForce chipset" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):674 -msgid "gtk-cpuspeedy" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):523 +msgid "nvidia" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):675 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):686 -msgid "Graphical" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):524 +msgid "Enable support for NVidia graphical card configuration (through the NVidia <e>nvclock</e> interface), allowing <c>cpufreqd</c> to change the video card frequency of NVidia graphical cards" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):679 -msgid "Gnome application, a graphical tool to set CPU frequency manually. It does not offer any automation." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):529 +msgid "you have an NVidia graphical card" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):685 -msgid "klaptopdaemon" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):534 +msgid "pmu" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):687 -msgid "Battery state" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):535 +msgid "Enable the Power Management Unit plug-in of <c>cpufreqd</c>. This allows the software to poll the Linux kernel Power Supply interface, getting more detailed information on battery charge." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):690 -msgid "KDE only, 'ondemand' governor required for dynamic frequency scaling." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):540 +msgid "your laptop does not support ACPI or APM" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):696 -msgid "While adjusting the frequency to the current load looks simple at a first glance, it's not such a trivial task. A bad algorithm can cause switching between two frequencies all the time or wasting energy when setting frequency to an unnecessary high level." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):546 +msgid "The USE flags <c>acpi</c>, <c>apm</c> and <c>pmu</c> overlap, so you should only have one active. If your laptop is sufficiently recent, <c>acpi</c> is your best bet. If not, <c>apm</c> offers all that is needed. When even APM isn't supported, you can try <c>pmu</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):703 -msgid "Which one to choose? If you have no idea about it, try <c>cpufreqd</c>:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):553 +msgid "With the USE flags configured, it is time to install <c>cpufreqd</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):707 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):557 msgid "Installing cpufreqd" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):707 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):557 #, no-wrap msgid "\n# <i>emerge cpufreqd</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):711 -msgid "<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</path>. The default one that ships with cpufreqd may look a bit confusing. I recommend replacing it with the one from former Gentoo developer Henrik Brix Andersen (see below). Please notice that you need cpufreqd-2.0.0 or later. Earlier versions have a different syntax for the config file." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):719 -msgid "/etc/cpufreqd.conf (cpufreqd-2.0.0 and later)" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):719 -#, no-wrap -msgid "\n[General]\npidfile=/var/run/cpufreqd.pid\npoll_interval=3\nenable_plugins=acpi_ac, acpi_battery\nenable_remote=1\nremote_group=wheel\nverbosity=5\n[/General]\n\n[Profile]\nname=ondemand\nminfreq=0%\nmaxfreq=100%\npolicy=ondemand\n[/Profile]\n\n[Profile]\nname=conservative\nminfreq=0%\nmaxfreq=100%\npolicy=conservative\n[/Profile]\n\n[Profile]\nname=powersave\nminfreq=0%\nmaxfreq=100%\npolicy=powersave\n[/Profile]\n\n[Profile]\nname=performance\nminfreq=0%\nmaxfreq=100%\npolicy=performance\n[/Profile]\n\n[Rule]\nname=battery\nac=off\nprofile=conservative\n[/Rule]\n\n[Rule]\nname=battery_low\nac=off\nbattery_interval=0-10\nprofile=powersave\n[/Rule]\n\n[Rule]\nname=ac\nac=on\nprofile=ondemand\n[/Rule]\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):777 -msgid "Now you can start the cpufreqd daemon. Add it to the <c>default</c> and <c>battery</c> runlevel as well." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):782 -msgid "Starting cpufreqd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):782 -#, no-wrap -msgid "\n# <i>rc-update add cpufreqd default battery</i>\n# <i>/etc/init.d/cpufreqd start</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):787 -msgid "Sometimes it can be desirable to select another policy than the daemon chooses, for example when battery power is low, but you know that AC will be available soon. In that case you can turn on cpufreqd's manual mode with <c>cpufreqd-set manual</c> and select one of your configured policies (as listed by <c>cpufreqd-get</c>). You can leave manual mode by executing <c>cpufreqd-set dynamic</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):796 -msgid "Do not run more than one of the above programs at the same time. It may cause confusion like switching between two frequencies all the time." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):804 -msgid "Verifying the result" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):807 -msgid "The last thing to check is that your new policies do a good job. An easy way to do so is monitoring CPU speed while working with your laptop:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):812 -msgid "Monitoring CPU speed" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):812 -#, no-wrap -msgid "\n# <i>watch grep \\\"cpu MHz\\\" /proc/cpuinfo</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):816 -msgid "If <path>/proc/cpuinfo</path> doesn't get updated (see <uri link=\"#doc_chap8\">Troubleshooting</uri>), monitor the CPU frequency with <c>sys-apps/x86info</c>:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):822 -msgid "Alternative CPU speed monitoring" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):822 -#, no-wrap -msgid "\n# <i>watch x86info -mhz</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):826 -msgid "Depending on your setup, CPU speed should increase on heavy load, decrease on no activity or just stay at the same level. When using <c>cpufreqd</c> and verbosity set to 5 or higher in <path>cpufreqd.conf</path> you'll get additional information about what's happening reported to <c>syslog</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):838 -msgid "LCD Power Management" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):842 -msgid "As you can see in <uri link=\"#doc_chap1_fig1\">figure 1.1</uri>, the LCD display consumes the biggest part of energy (might not be the case for non-mobile CPU's). Thus it's quite important not only to shut the display off when not needed, but also to reduce it's backlight if possible. Most laptops offer the possibility to control the backlight dimming." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):853 -msgid "Standby settings" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):856 -msgid "The first thing to check is the standby/suspend/off timings of the display. As this depends heavily on your windowmanager, I'll let you figure it out yourself. Just two common places: Blanking the terminal can be done with <c>setterm -blank <number-of-minutesM></c>, <c>setterm -powersave on</c> and <c>setterm -powerdown <number-of-minutesM></c>. For X.org, modify <path>/etc/X11/xorg.conf</path> similar to this:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):865 -msgid "LCD suspend settings in X.org" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):865 -#, no-wrap -msgid "\nSection \"ServerFlags\"\n Option \"blank time\" \"5\" <comment># Blank the screen after 5 minutes (Fake)</comment>\n Option \"standby time\" \"10\" <comment># Turn off screen after 10 minutes (DPMS)</comment>\n Option \"suspend time\" \"20\" <comment># Full suspend after 20 minutes</comment>\n Option \"off time\" \"30\" <comment># Turn off after half an hour</comment>\n [...]\nEndSection\n\n[...]\n\nSection \"Monitor\"\n Identifier [...]\n Option \"DPMS\"\n [...]\nEndSection\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):886 -msgid "Backlight dimming" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):889 -msgid "Probably more important is the backlight dimming. If you have access to the dimming settings via a tool, write a small script that dims the backlight in battery mode and place it in your <c>battery</c> runlevel. The following script should work on most IBM Thinkpads and Toshiba laptops. You've got to enable the appropriate option in your kernel (IBM Thinkpads only). For Toshiba laptops, install <c>sys-power/acpitool</c> and skip configuration of <c>thinkpad_acpi</c> (formerly called <c>ibm_acpi</c>) as described below." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):899 -msgid "Support for setting brightness is marked experimental in thinkpad_acpi. It accesses hardware directly and may cause severe harm to your system. Please read the <uri link=\"http://ibm-acpi.sourceforge.net/\">thinkpad_acpi website</uri>" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):906 -msgid "To be able to set the brightness level, the thinkpad_acpi module has to be loaded with the experimental parameter." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):911 -msgid "Automatically loading the thinkpad_acpi module" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):911 -#, no-wrap -msgid "\n<comment>(Please read the warnings above before doing this!)</comment>\n\n# <i>echo \"options thinkpad_acpi experimental=1\" >> /etc/modprobe.d/thinkpad_acpi</i>\n# <i>update-modules</i>\n# <i>nano /etc/conf.d/modules</i>\n<comment># Autoload the thinkpad_acpi module</comment>\nmodules_2_6=\"thinkpad_acpi\"\n<comment># Parameters for the thinkpad_acpi module</comment>\nmodules_thinkpad_acpi_args_2_6=\"experimental=1\"\n\n# <i>modprobe thinkpad_acpi</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):925 -msgid "This should work without error messages and a file <path>/proc/acpi/ibm/brightness</path> should be created after loading the module. An init script will take care of choosing the brightness according to the power source." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):932 -msgid "/etc/conf.d/lcd-brightness" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):932 -#, no-wrap -msgid "\n<comment># See /proc/acpi/ibm/brightness for available values</comment>\n<comment># Please read /usr/src/linux/Documentation/thinkpad-acpi.txt</comment>\n\n<comment># brightness level in ac mode. Default is 7.</comment>\nBRIGHTNESS_AC=7\n\n<comment># brightness level in battery mode. Default is 4.</comment>\nBRIGHTNESS_BATTERY=4\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):943 -msgid "/etc/init.d/lcd-brightness" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):943 -#, no-wrap -msgid "\n#!/sbin/runscript\n\nset_brightness() {\n if on_ac_power\n then\n LEVEL=${BRIGHTNESS_AC:-7}\n else\n LEVEL=${BRIGHTNESS_BATTERY:-4}\n fi\n\n if [ -f /proc/acpi/ibm/brightness ]\n then\n ebegin \"Setting LCD brightness\"\n echo \"level ${LEVEL}\" > /proc/acpi/ibm/brightness\n eend $?\n elif [[ -e /usr/bin/acpitool && -n $(acpitool -T | grep \"LCD brightness\") ]]\n then\n ebegin \"Setting LCD brightness\"\n acpitool -l $LEVEL >/dev/null || ewarn \"Unable to set lcd brightness\"\n eend $?\n else\n ewarn \"Setting LCD brightness is not supported.\"\n ewarn \"For IBM Thinkpads, check that thinkpad_acpi is loaded into the kernel\"\n ewarn \"For Toshiba laptops, you've got to install sys-power/acpitool\"\n fi\n}\n\nstart() {\n set_brightness\n}\n\nstop () {\n set_brightness\n}\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):980 -msgid "When done, make sure brightness is adjusted automatically by adding it to the battery runlevel." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):985 -msgid "Enabling automatic brightness adjustment" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):985 -#, no-wrap -msgid "\n# <i>chmod +x /etc/init.d/lcd-brightness</i>\n# <i>rc-update add lcd-brightness battery</i>\n# <i>rc</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):996 -msgid "Disk Power Management" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1000 -msgid "Hard disks consume less energy in sleep mode. Therefore it makes sense to activate power saving features whenever the hard disk is not used for a certain amount of time. I'll show you two alternative possibilities to do it. First, laptop-mode will save most energy due to several measures which prevent or at least delay write accesses. The drawback is that due to the delayed write accesses a power outage or kernel crash will be more dangerous for data loss. If you don't like this, you have to make sure that there are no processes which write to your hard disk frequently. Afterwards you can enable power saving features of your hard disk with <c>hdparm</c> as the second alternative." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1015 -msgid "Increasing idle time - laptop-mode" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1018 -msgid "Recent 2.6 kernels include the so-called <c>laptop-mode</c>. When activated, dirty buffers are written to disk on read calls or after 10 minutes (instead of 30 seconds). This minimizes the time the hard disk needs to be spun up." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1024 -msgid "Automated start of laptop-mode" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1024 -#, no-wrap -msgid "\n# <i>emerge laptop-mode-tools</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1028 -msgid "<c>laptop-mode-tools</c> has its configuration file in <path>/etc/laptop-mode/laptop-mode.conf</path>. Adjust it the way you like it, it's well commented. Run <c>rc-update add laptop_mode battery</c> to start it automatically." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1035 -msgid "Recent versions (1.11 and later) of laptop-mode-tools include a new tool <c>lm-profiler</c>. It will monitor your system's disk usage and running network services and suggests to disable unneeded ones. You can either disable them through laptop-mode-tools builtin runlevel support (which will be reverted by Gentoo's <c>/sbin/rc</c>) or use your <c>default</c>/<c>battery</c> runlevels (recommended)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1044 -msgid "Sample output from running lm-profiler" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1044 -#, no-wrap -msgid "\n# <i>lm-profiler</i>\nProfiling session started.\nTime remaining: 600 seconds\n[4296896.602000] amarokapp\nTime remaining: 599 seconds\n[4296897.714000] sort\n[4296897.970000] mv\nTime remaining: 598 seconds\nTime remaining: 597 seconds\n[4296900.482000] reiserfs/0\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1057 -msgid "After profiling your system for ten minutes, lm-profiler will present a list of services which might have caused disk accesses during that time." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1062 -msgid "lm-profiler suggests to disable some services" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1062 -#, no-wrap -msgid "\nProgram: \"atd\"\nReason: standard recommendation (program may not be running)\nInit script: /etc/init.d/atd (GUESSED)\n\nDo you want to disable this service in battery mode? [y/N]: <i>n</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1070 -msgid "To disable atd as suggested in the example above, you would run <c>rc-update del atd battery</c>. Be careful not to disable services that are needed for your system to run properly - <c>lm-profiler</c> is likely to generate some false positives. Do not disable a service if you are unsure whether it's needed." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1081 -msgid "Limiting Write Accesses" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1084 -msgid "If you don't want to use laptop-mode, you must take special care to disable services that write to your disk frequently - <c>syslogd</c> is a good candidate, for example. You probably don't want to shut it down completely, but it's possible to modify the config file so that \"unnecessary\" things don't get logged and thus don't create disk traffic. <c>Cups</c> writes to disk periodically, so consider shutting it down and only enable it manually when needed." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1094 -msgid "Disabling cups in battery mode" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1094 -#, no-wrap -msgid "\n# <i>rc-update del cupsd battery</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1098 -msgid "You can also use <c>lm-profiler</c> from laptop-mode-tools (see above) to find services to disable. Once you eliminated all of them, go on with configuring hdparm." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1107 -msgid "hdparm" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1110 -msgid "The second possibility is using <c>hdparm</c>. Skip this if you are using laptop-mode. Otherwise, edit <path>/etc/conf.d/hdparm</path> and add the following values to your drive entries. This example assumes your hard drive is called <b>hda</b>:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1117 -msgid "Using /etc/conf.d/hdparm for disk standby" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1117 -#, no-wrap -msgid "\nhda_args=\"-q -S12\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1121 -msgid "This will activate power management for your hard drive. If you ever want to deactivate power management, you can edit <path>/etc/conf.d/hdparm</path> and change the values to <c>-q -S0</c>, or just run <c>hdparm -q -S0 /dev/hda</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1127 -msgid "See <c>man hdparm</c> for the options. Though you can always start <c>hdparm</c> manually when you are on battery power by running <c>/etc/init.d/hdparm start</c>, it's much easier to automate its startup and shutdown. To do so, add <c>hdparm</c> to the battery runlevel so that it will automatically enable power management." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1135 -msgid "Automate disk standby settings" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1135 -#, no-wrap -msgid "\n# <i>rc-update add hdparm battery</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(impo):1139 -msgid "Be careful with sleep/spin down settings of your hard drive. Setting it to small values might wear out your drive and lose warranty." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1147 -msgid "Other tricks" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1150 -msgid "Another possibility is to deactivate swap in battery mode. Before writing a swapon/swapoff switcher, make sure there is enough RAM and swap isn't used heavily, otherwise you'll be in big problems." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1156 -msgid "If you don't want to use laptop-mode, it's still possible to minimize disk access by mounting certain directories as <c>tmpfs</c> - write accesses are not stored on a disk, but in main memory and get lost with unmounting. Often it's useful to mount <path>/tmp</path> like this - you don't have to pay special attention as it gets cleared on every reboot regardless whether it was mounted on disk or in RAM. Just make sure you have enough RAM and no program (like a download client or compress utility) needs extraordinary much space in <path>/tmp</path>. To activate this, enable tmpfs support in your kernel and add a line to <path>/etc/fstab</path> like this:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1168 -msgid "Editing /etc/fstab to make /tmp even more volatile" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1168 -#, no-wrap -msgid "\nnone /tmp tmpfs size=32m 0 0\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1172 -msgid "Pay attention to the size parameter and modify it for your system. If you're unsure, don't try this at all, it can become a performance bottleneck easily. In case you want to mount <path>/var/log</path> like this, make sure to merge the log files to disk before unmounting. They are essential. Don't attempt to mount <path>/var/tmp</path> like this. Portage uses it for compiling..." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1185 -msgid "Power Management For Other Devices" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1187 -msgid "Graphics Cards" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1190 -msgid "In case you own an ATI graphics card supporting PowerPlay (dynamic clock scaling for the graphics processing unit GPU), you can activate this feature in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable) the <c>DynamicClocks</c> option in the Device section. Please notice that this feature will lead to crashes on some systems." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1198 -msgid "Enabling ATI PowerPlay support in X.org" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1198 -#, no-wrap -msgid "\nSection \"Device\"\n[...]\nOption \"DynamicClocks\" \"on\"\nEndSection\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1208 -msgid "Wireless Power Management" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1211 -msgid "Wireless LAN cards consume quite a bit of energy. Put them in Power Management mode just like your hard drives." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1216 -msgid "This script assumes your wireless interface is called <c>wlan0</c>; replace this with the actual name of your interface." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1221 -msgid "Add the following option to <path>/etc/conf.d/net</path> to automatically enable power management for your wireless card:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1226 -msgid "Automated WLAN Power Management" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1226 -#, no-wrap -msgid "\niwconfig_wlan0=\"power on\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1230 -msgid "See <c>man iwconfig</c> for details and more options like the period between wakeups or timeout settings. If your driver and access point support changing the beacon time, this is a good starting point to save even more energy." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1239 -msgid "USB Power Management" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1242 -msgid "There are two problems with USB devices regarding energy consumption: First, devices like USB mice, digital cameras or USB sticks consume energy while plugged in. You cannot avoid this (nevertheless remove them in case they're not needed). Second, when there are USB devices plugged in, the USB host controller periodically accesses the bus which in turn prevents the CPU from going into sleep mode. The kernel offers an experimental option to enable suspension of USB devices through driver calls or one of the <path>power/state</path> files in <path>/sys</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1253 -msgid "Enabling USB suspend support in the kernel" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1253 -#, no-wrap -msgid "\nDevice Drivers\n USB support\n [*] Support for Host-side USB\n [*] USB suspend/resume (EXPERIMENTAL)\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1265 -msgid "Sleep States: sleep, standby, and suspend to disk" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):567 +msgid "The <c>cpufreqd</c> application monitors the status of the system through several plugins. Based on the feedback it receives from those plugins, it will adjust the policy used to govern the CPU frequency." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1269 -msgid "ACPI defines different sleep states. The more important ones are" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):573 +msgid "<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</path>. It contains three different sections:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1274 -msgid "S1 aka Standby" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):579 +msgid "The <c>[General]...[/General]</c> section contains general configuration information" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1275 -msgid "S3 aka Suspend to RAM aka Sleep" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):583 +msgid "The <c>[Profile]...[/Profile]</c> section defines the policies that the <c>cpufreqd</c> daemon can switch to. The section is very similar to the information you use when manually setting the CPU frequency policy using <c>cpufreq-set</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1276 -msgid "S4 aka Suspend to Disk aka Hibernate" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):589 +msgid "The <c>[Rule]...[/Rule]</c> section is the work-horse of the <c>cpufreqd</c> daemon, defining when the daemon decides to switch to a different profile." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1279 -msgid "They can be called whenever the system is not in use, but a shutdown is not wanted due to the long boot time." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):595 +msgid "Let's take a quick look at an example rule." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1287 -msgid "Sleep (S3)" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):599 +msgid "Sample cpufreqd rule" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1290 -msgid "The ACPI support for these sleep states is marked experimental for good reason. APM sleep states seem to be more stable, however you can't use APM and ACPI together." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1296 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1390 -msgid "Kernel configuration for the various suspend types" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1296 -#, no-wrap -msgid "\n Power Management Options --->\n [*] Power Management support\n [*] Suspend to RAM and standby \n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1302 -msgid "Once your kernel is properly configured, you can use the <c>hibernate-script</c> to activate suspend or sleep mode. Let's install that first." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1308 -msgid "Installing the hibernate-script" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1308 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):599 #, no-wrap -msgid "\n# <i>emerge hibernate-script</i>\n" +msgid "\n[Profile]\nname=On Demand High\nminfreq=40%\nmaxfreq=100%\npolicy=ondemand\n[/Profile]\n\n[Rule]\nname=AC Off - High Power\nac=off\nbattery_interval=70-100\nprofile=On Demand High\n[/Rule]\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1312 -msgid "Some configuration has to be done in <path>/etc/hibernate</path>. The default package introduces a few configuration files for each sleep state. Options that are common to all suspend methods are placed in <path>common.conf</path>; make sure this file is properly set up for your system." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):615 +msgid "In the above example, <c>cpufreqd</c> will switch the system to the <e>On Demand High</e> profile (also shown in the above excerpt). This profile by itself uses the <c>ondemand</c> governor with a minimum frequency of 40% (iow, a CPU of 2Ghz will have by this policy a minimum frequency of 800Mhz)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1319 -msgid "To configure sleep, edit <path>sysfs-ram.conf</path> in <path>/etc/hibernate</path>. <c>UseSysfsPowerState mem</c> is already setup correctly, but if you need to make further changes to this particular sleep state (or any other sleep state) you should add them to <path>/etc/hibernate/hibernate.conf</path>. The comments and option names will guide you. If you use nfs or samba shares over the network, make sure to shutdown the appropriate init scripts to avoid timeouts." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):622 +msgid "As you can see, the <c>cpufreqd</c> application can offer a more granular approach on CPU frequency scaling. But not only that, you can tweak the CPU frequency scaling based on various other metrics available. The default configuration offers a sample rule for when you watch a movie, where you want maximum performance, unless the CPU temperature is getting too high." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1329 -msgid "For more information on setting up sleep states, read <c>man hibernate.conf</c>." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):630 +msgid "When you have configured <c>cpufreqd</c>, it is time to start it (and make sure the service is loaded automatically). Make sure that CPU frequency handling by other tools (like <c>laptop-mode-tools</c>) is disabled!" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1334 -msgid "Ready? Now is the last chance to backup any data you want to keep after executing the next command. Notice that you probably have to hit a special key like <c>Fn</c> to resume from sleep." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1340 -msgid "Calling sleep" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1340 -#, no-wrap -msgid "\n# <i>hibernate-ram</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1344 -msgid "If you're still reading, it seems to work. You can also setup standby (S1) in a similar way by editing <path>sysfs-ram.conf</path> and changing \"UseSysfsPowerState mem\" to \"UseSysfsPowerState standby\". S3 and S4 are the more interesting sleep states due to greater energy savings however." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1354 -msgid "Hibernate (S4)" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1357 -msgid "This section introduces hibernation, where a snapshot of the running system is written to disk before powering off. On resume, the snapshot is loaded and you can go on working at exactly the point you called hibernate before." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1363 -msgid "Don't exchange non hot-pluggable hardware when suspended. Don't attempt to load a snapshot with a different kernel image than the one it was created with. Shutdown any NFS or samba server/client before hibernating." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1369 -msgid "There are two different implementations for S4. The original one is swsusp, then there is the newer tuxonice (formerly suspend2) with a nicer interface (including fbsplash support). A <uri link=\"http://tuxonice.net/features.html#compare\">feature comparison</uri> is available at the <uri link=\"http://www.tuxonice.net\">tuxonice homepage</uri>. There used to be Suspend-to-Disk (pmdisk), a fork of swsusp, but it has been merged back." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1379 -msgid "TuxOnIce is not included in the mainline kernel yet, therefore you either have to patch your kernel sources with the patches provided by <uri link=\"http://www.tuxonice.net\">tuxonice.net</uri> or use <c>sys-kernel/tuxonice-sources</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1386 -msgid "The kernel part for both swusp and TuxOnIce is as follows:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1390 -#, no-wrap -msgid "\nPower Management support --->\n <comment>(hibernate with swsusp)</comment>\n [*] Hibernation (aka 'suspend to disk')\n <comment>(replace /dev/SWAP with your swap partition)</comment>\n (/dev/SWAP) Default resume partition\n\n <comment>(hibernate with TuxOnIce)</comment>\n Enhanced Hibernation (TuxOnIce)\n --- Image Storage (you need at least one allocator)\n [*] File Allocator\n [*] Swap Allocator\n --- General Options\n [*] Compression support\n [ ] Allow Keep Image Mode\n [*] Replace swsusp by default\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1408 -msgid "The configuration for swsusp is rather easy. If you didn't store the location of your swap partition in the kernel config, you can also pass it as a parameter with the <c>resume=/dev/SWAP</c> directive. If booting is not possible due to a broken image, use the <c>noresume</c> kernel parameter. The <c>hibernate-cleanup</c> init script invalidates swsusp images during the boot process." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1417 -msgid "Invalidating swsusp images during the boot process" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1417 ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1459 -#, no-wrap -msgid "\n# <i>rc-update add hibernate-cleanup boot</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1421 -msgid "To activate hibernate with swsusp, use the hibernate script and set <c>UseSysfsPowerState disk</c> in <path>/etc/hibernate/sysfs-disk</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1426 -msgid "Backup your data before doing this. Run <c>sync</c> before executing one of the commands to have cached data written to disk. First try it outside of X, then with X running, but not logged in." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1432 -msgid "If you experience kernel panics due to uhci or similar, try to compile USB support as module and unload the modules before sending your laptop to sleep mode. There are configuration options for this in <path>common.conf</path>" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1438 -msgid "Hibernating with swsusp" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1438 -#, no-wrap -msgid "\n# <i>nano -w /etc/hibernate/common.conf</i>\n<comment>(Make sure you have a backup of your data)</comment>\n# <i>hibernate</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1444 -msgid "The following section discusses the setup of TuxOnIce including fbsplash support for a nice graphical progress bar during suspend and resume." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1449 -msgid "The first part of the configuration is similar to the configuration of swsusp. In case you didn't store the location of your swap partition in the kernel config, you have to pass it as a kernel parameter with the <c>resume=swap:/dev/SWAP</c> directive. If booting is not possible due to a broken image, append the <c>noresume</c> parameter. Additionally, the <c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the boot process." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1459 -msgid "Invalidating TuxOnIce images during the boot process" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1463 -msgid "Now edit <path>/etc/hibernate/tuxonice.conf</path>, enable the <c>TuxOnIce</c> options you need. Do not enable the <c>fbsplash</c> options in <c>common.conf</c> just yet." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1469 -msgid "Hibernating with TuxOnIce" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1469 -#, no-wrap -msgid "\n# <i>nano -w /etc/hibernate/tuxonice.conf</i>\n<comment>(Make sure you have a backup of your data)</comment>\n# <i>hibernate</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1475 -msgid "Please configure <c>fbsplash</c> now if you didn't do already. To enable fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c> package is needed. Additionally, you've got to enable the <c>fbsplash</c> USE flag." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1481 -msgid "Installing tuxonice-userui" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1481 -#, no-wrap -msgid "\n# <i>echo \"sys-apps/tuxonice-userui fbsplash\" >> /etc/portage/package.use</i>\n# <i>emerge tuxonice-userui</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1486 -msgid "The ebuild tells you to make a symlink to the theme you want to use. For example, to use the <c>livecd-2005.1</c> theme, run the following command:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1491 -msgid "Using the livecd-2005.1 theme during hibernation" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1491 -#, no-wrap -msgid "\n# <i>ln -sfn /etc/splash/livecd-2005.1 /etc/splash/tuxonice</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1495 -msgid "If you don't want a black screen in the first part of the resume process, you have to add the <c>tuxoniceui_fbsplash</c> tool to your initrd image. Assuming you created the initrd image with <c>splash_geninitramfs</c> and saved it as <path>/boot/fbsplash-emergence-1024x768</path>, here's how to do that." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1502 -msgid "Adding tuxoniceui_fbsplash to an initrd image" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1502 -#, no-wrap -msgid "\n# <i>mount /boot</i>\n# <i>mkdir ~/initrd.d</i>\n# <i>cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i>\n# <i>cd ~/initrd.d</i>\n# <i>gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i>\n# <i>rm fbsplash-emergence-1024x768</i>\n# <i>cp /usr/sbin/tuxoniceui_fbsplash sbin/</i>\n# <i>find . | cpio --quiet --dereference -o -H newc | gzip -9 > /boot/fbsplash-tuxonice-emergence-1024x768</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1513 -msgid "Afterwards adjust <path>grub.conf</path> (or <path>lilo.conf</path>) so that your TuxOnIce kernel uses <path>/boot/fbsplash-tuxonice-emergence-1024x768</path> as initrd image. You can now test a dry run to see if everything is setup correctly." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1520 -msgid "Test run for fbsplash hibernation" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1520 -#, no-wrap -msgid "\n# <i>tuxoniceui_fbsplash -t</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1524 -msgid "Afterwards open <path>/etc/hibernate/common.conf</path> and activate the fbsplash options. Execute <c>hibernate</c> and enjoy." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1534 -msgid "Troubleshooting" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1538 -msgid "<e>Q:</e> I'm trying to change the CPU frequency, but <path>/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor</path> does not exist." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1544 -msgid "<e>A:</e> Make sure your processor supports CPU frequency scaling and you chose the right CPUFreq driver for your processor. Here is a list of processors that are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-SA1100, ARM-SA1110, AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile K6-3+, AMD mobile Duron, AMD mobile Athlon, AMD Opteron, AMD Athlon 64, Cyrix Media GXm, Intel mobile PIII and Intel mobile PIII-M on certain chipsets, Intel Pentium 4, Intel Xeon, Intel Pentium M (Centrino), National Semiconductors Geode GX, Transmeta Crusoe, VIA Cyrix 3 / C3, UltraSPARC-III, SuperH SH-3, SH-4, several \"PowerBook\" and \"iBook2\" and various processors on some ACPI 2.0-compatible systems (only if \"ACPI Processor Performance States\" are available to the ACPI/BIOS interface)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1557 -msgid "<e>Q:</e> My laptop supports frequency scaling, but <path>/sys/devices/system/cpu/cpu0/cpufreq/</path> is empty." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1562 -msgid "<e>A:</e> Look for ACPI related error messages with <c>dmesg | grep ACPI</c>. Try to update the BIOS, especially if a broken DSDT is reported. You can also try to fix it yourself (which is beyond the scope of this guide)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1568 -msgid "<e>Q:</e> My laptop supports frequency scaling, but according to <path>/proc/cpuinfo</path> the speed never changes." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1573 -msgid "<e>A:</e> Probably you have activated symmetric multiprocessing support (CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older kernels had a bug causing this. In that case, run <c>emerge x86info</c>, update your kernel as asked and check the current frequency with <c>x86info -mhz</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1580 -msgid "<e>Q:</e> I can change the CPU frequency, but the range is not as wide as in another OS." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1585 -msgid "<e>A:</e> You can combine frequency scaling with ACPI throttling to get a lower minimum frequency. Notice that throttling doesn't save much energy and is mainly used for thermal management (keeping your laptop cool and quiet). You can read the current throttling state with <c>cat /proc/acpi/processor/CPU/throttling</c> and change it with <c>echo -n \"0:x\" > /proc/acpi/processor/CPU/limit</c>, where x is one of the Tx states listed in <path>/proc/acpi/processor/CPU/throttling</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1595 -msgid "<e>Q:</e> When configuring the kernel, powersave, performance and userspace governors show up, but that ondemand thing is missing. Where do I get it?" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1600 -msgid "<e>A:</e> The ondemand governor is only included in recent kernel sources. Try updating them." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1605 -msgid "<e>Q:</e> Battery life time seems to be worse than before." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1609 -msgid "<e>A:</e> Check your BIOS settings. Maybe you forgot to re-enable some of the settings." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1614 -msgid "<e>Q:</e> My battery is charged, but KDE reports there would be 0% left and immediately shuts down." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1619 -msgid "<e>A:</e> Check that battery support is compiled into your kernel. If you use it as a module, make sure the module is loaded." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1624 -msgid "<e>Q:</e> My system logger reports things like \"logger: ACPI group battery / action battery is not defined\"." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1629 -msgid "<e>A:</e> This message is generated by the <path>/etc/acpi/default.sh</path> script that is shipped with acpid. You can safely ignore it. If you like to get rid of it, you can comment the appropriate line in <path>/etc/acpi/default.sh</path> as shown below:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1636 -msgid "Disabling warnings about unknown acpi events" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):636 +msgid "Starting cpufreqd" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1636 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):636 #, no-wrap -msgid "\n *) # logger \"ACPI action $action is not defined\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1640 -msgid "<e>Q:</e> I have a Dell Inspiron 51XX and I don't get any ACPI events." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1644 -msgid "<e>A:</e> This seems to be a kernel bug. Read on <uri link=\"http://bugme.osdl.org/show_bug.cgi?id=1752\">here</uri>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1649 -msgid "<e>Q:</e> I activated the <c>DynamicClocks</c> option in <path>xorg.conf</path> and now X.org crashes / the screen stays black / my laptop doesn't shutdown properly." +msgid "\n# <i>rc-service add cpufreqd default</i>\n# <i>/etc/init.d/cpufreqd start</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1655 -msgid "<e>A:</e> This happens on some systems. You have to disable <c>DynamicClocks</c>." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):646 +msgid "Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1660 -msgid "<e>Q:</e> I want to use TuxOnIce, but it tells me my swap partition is too small. Resizing is not an option." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):648 +msgid "Tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1665 -msgid "<e>A:</e> If there is enough free space on your system, you can use the filewriter instead of the swapwriter. The <c>hibernate-script</c> supports it as well. More information can be found in <path>/usr/src/linux/Documentation/power/tuxonice.txt</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1672 -msgid "<e>Q:</e> I just bought a brand new battery, but it only lasts for some minutes! What am I doing wrong?" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1677 -msgid "<e>A:</e> First follow your manufacturer's advice on how to charge the battery correctly." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1682 -msgid "<e>Q:</e> The above didn't help. What should I do then?" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1686 -msgid "<e>A:</e> Some batteries sold as \"new\" are in fact old ones. Try the following:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1690 -msgid "Querying battery state" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1690 -#, no-wrap -msgid "\n$ <i>grep capacity /proc/acpi/battery/BAT0/info</i>\ndesign capacity: 47520 mWh\nlast full capacity: 41830 mWh\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):652 +msgid "<uri link=\"http://samwel.tk/laptop_mode/\">Laptop Mode Tools Homepage</uri>, includes <uri link=\"http://samwel.tk/laptop_mode/laptop_mode\">About laptop mode</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1696 -msgid "If the \"last full capacity\" differs significantly from the design capacity, your battery is probably broken. Try to claim your warranty." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):657 +msgid "<uri link=\"http://www.lesswatts.org/projects/powertop/\">PowerTOP</uri>, an interactive application helping users to find out which processes are forcing wakeups on the CPU most often." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1701 -msgid "<e>Q:</e> My problem is not listed above. Where should I go next?" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):667 +msgid "Articles and Guides" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1705 -msgid "<e>A:</e> Don't fear to contact me, <mail link=\"earthwings@gentoo.org\">Dennis Nienhüser</mail>, directly. The <uri link=\"http://forums.gentoo.org\">Gentoo Forums</uri> are a good place to get help as well. If you prefer IRC, try the <c>#gentoo-laptop</c><uri link=\"irc://irc.gentoo.org\">channel</uri>." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):671 +msgid "A ThinkWiki article on <uri link=\"http://www.thinkwiki.org/wiki/How_to_reduce_power_consumption\">How to reduce power consumption</uri> (on Linux). This article offers an exhaustive list of measures one can take. However, it should be noted that the laptop mode tools implements the majority of these (if properly configured)." msgstr "" #. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL diff --git a/doc/gettext/ru/faq.xml.po b/doc/gettext/ru/faq.xml.po index b68b294..31bfe49 100644 --- a/doc/gettext/ru/faq.xml.po +++ b/doc/gettext/ru/faq.xml.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: 2011-09-18 15:18+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2009-10-17 04:24+0600\n" "Last-Translator: Azamat H. Hackimov <azamat.hackimov@gmail.com>\n" "Language-Team: Russian <kde-russian@lists.kde.ru>\n" @@ -121,11 +121,11 @@ msgid "" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(version):50 -msgid "6" +msgid "7" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(date):51 -msgid "2011-09-11" +msgid "2011-10-13" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):54 @@ -294,20 +294,28 @@ msgstr "" #: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):205 msgid "" "In fact, there is no difference between the various releases after they have " -"been installed. Gentoo 1.4 and later are <c>glibc-2.3.x</c> based. As such, " -"running <c>emerge --sync && emerge -uDN world</c> will bring your " -"entire system up to speed with the \"latest Gentoo\". The differences " -"between individual releases lie in the installation medium and pre-compiled " -"packages. See the <uri link=\"/doc/en/gentoo-upgrading.xml\">Gentoo " -"Upgrading Guide</uri> for more information about profiles and their role in " -"upgrading." +"been installed. Gentoo 1.4 and later are <c>glibc-2.3.x</c> (or higher) " +"based. As such, running <c>emerge --sync && emerge -uDN world</c> " +"will bring your entire system up to speed with the \"latest Gentoo\". The " +"differences between individual releases lie in the installation medium and " +"pre-compiled packages. See the <uri link=\"/doc/en/gentoo-upgrading.xml" +"\">Gentoo Upgrading Guide</uri> for more information about profiles and " +"their role in upgrading." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):218 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):215 +msgid "" +"Also note that the <c>emerge -uDN world</c> command updates the packages you " +"have installed as well as its dependencies, but not the build-time " +"dependencies (packages needed during builds but not when the software is " +"installed). To update those as well, add the <c>--with-bdeps=y</c> option." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):225 msgid "My kernel doesn't boot, what should I do now?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):221 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):228 msgid "" "You don't need to redo every step of the installation, but investigating the " "kernel and all associated steps is necessary. Suppose you have installed " @@ -315,11 +323,11 @@ msgid "" "<path>/dev/hda2</path> being the swap space:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):228 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):235 msgid "Reconfiguring the kernel" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):228 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):235 #, no-wrap msgid "" "\n" @@ -347,28 +355,28 @@ msgid "" "# <i>reboot</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):253 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):260 msgid "" "If, on the other hand, the problem lies with your bootloader configuration, " "follow the same steps, but instead of configuring/compiling your kernel, you " "should reconfigure your bootloader (recompilation isn't necessary)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):262 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):269 msgid "My proxy requires authentication, what do I have to do?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):265 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):272 msgid "" "To have Portage automatically use this scheme, define it in <path>/etc/make." "conf</path>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):270 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):277 msgid "/etc/make.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):270 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):277 #, no-wrap msgid "" "\n" @@ -377,23 +385,23 @@ msgid "" "RSYNC_PROXY=\"rsync://username:password@yourproxybox.server:portnumber\"\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):279 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):286 msgid "How do I burn an ISO file?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):282 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):289 msgid "" "You need to burn the file in raw mode. This means that you should <e>not</e> " "just place the file on the CD, but interpret the file as an entire CD." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):287 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):294 msgid "" "There are lots of CD burning tools available; covering them all would be a " "Sisyphean problem. However, describing a few popular tools never hurts:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):293 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):300 msgid "" "With EasyCD Creator you select <c>File</c>, <c>Record CD from CD image</c>. " "Then you change the <c>Files of type</c> to <c>ISO image file</c>. Then " @@ -401,7 +409,7 @@ msgid "" "recording</c> the ISO image will be burned correctly onto the CD-R." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):299 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):306 msgid "" "With Nero Burning ROM, cancel the wizard which automatically pops up and " "select <c>Burn Image</c> from the <c>File</c> menu. Select the image you " @@ -409,21 +417,21 @@ msgid "" "your brand new CD being burnt." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):305 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):312 msgid "" "With cdrecord, you simply type <c>cdrecord dev=/dev/hdc</c> (replace <path>/" "dev/hdc</path> with your CD-RW drive's device path) followed by the path to " "the ISO file :)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):310 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):317 msgid "" "With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn CD Image</c>. Then " "you can locate your ISO file within the 'Image to Burn' area. Finally click " "<c>Start</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):315 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):322 msgid "" "With Mac OS X Panther, launch <c>Disk Utility</c> from <path>Applications/" "Utilities</path>, select <c>Open</c> from the <c>Images</c> menu, select the " @@ -431,18 +439,18 @@ msgid "" "<c>Images</c> menu." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):321 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(li):328 msgid "" "With Mac OS X Jaguar, launch <c>Disk Copy</c> from <path>Applications/" "Utilities</path>, select <c>Burn Image</c> from the <c>File</c> menu, select " "the ISO and click the <c>Burn</c> button." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):332 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):339 msgid "What CD/stage should I use for my CPU?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):335 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):342 msgid "" "First you need to find out what CPU you use. Suppose it's a Pentium-M. Then " "you need to find out what CPU it is, instruction-wise, compatible with. You " @@ -450,14 +458,14 @@ msgid "" "\"http://www.google.com\">Google</uri> is at least as efficient :-)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):342 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):349 msgid "" "If you are uncertain, take a \"lower\" CD/stage file, for instance a i686 or " "even generic x86 (or the equivalent in your arch). This will ensure that " "your system will work, but may not be as fast as further optimizations." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):348 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):355 msgid "" "Please note that many more options exist than those for which Gentoo builds " "binary stages. Please see the <uri link=\"http://gcc.gnu.org/onlinedocs/" @@ -465,11 +473,11 @@ msgid "" "\">gcc guide</uri> for setting <c>-march</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):358 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):365 msgid "I can't get online after rebooting. What is wrong?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):361 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):368 msgid "" "First you need to check if your network card is discovered properly by the " "kernel. Run <c>ifconfig -a</c> and look for eth0 or wlan0 (in case of " @@ -479,13 +487,13 @@ msgid "" "modules</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):370 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):377 msgid "" "If you have forgotten to include support for your network card in your " "kernel, you will need to reconfigure your kernel." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):375 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):382 msgid "" "If your network card is found by your kernel, but you have set your " "networking configuration to use DHCP, you might have forgotten to " @@ -493,19 +501,19 @@ msgid "" "to install <c>dhcpcd</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):382 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):389 msgid "" "Information on how to rescue your system using the installation CD is <uri " "link=\"#bootrescue\">available</uri> as well." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):390 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):397 msgid "" "I want to boot Windows from grub or lilo but it shows only black screen. " "What should I do?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):396 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):403 msgid "" "This is a known problem. Windows refuses to boot when it isn't installed on " "the first hard drive and shows a black/blank screen. To handle this, you " @@ -516,11 +524,11 @@ msgid "" "config as needed." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):405 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):412 msgid "Example dual boot entry for Windows in grub.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):405 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):412 #, no-wrap msgid "" "\n" @@ -531,11 +539,11 @@ msgid "" " chainloader +1\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):413 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):420 msgid "Example dual boot entry for Windows in lilo.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):413 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):420 #, no-wrap msgid "" "\n" @@ -548,7 +556,7 @@ msgid "" " to = 0x80\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):423 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):430 msgid "" "This will make Windows believe it is installed on the first hard drive and " "boot without problems. More information can be found in the <uri link=" @@ -556,11 +564,11 @@ msgid "" "lilo.conf</c>, depending on the boot loader you're using." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):433 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):440 msgid "How do I Install Gentoo Using a Stage1 or Stage2 Tarball?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):436 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):443 msgid "" "The Gentoo Handbook only describes a Gentoo installation using a stage3 " "tarball. However, Gentoo still provides stage1 and stage2 tarballs. This is " @@ -570,7 +578,7 @@ msgid "" "Internet connection." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):444 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):451 msgid "" "Bootstrapping means building the toolchain (the C library and compiler) for " "your system after which you install all core system packages. To bootstrap " @@ -579,11 +587,11 @@ msgid "" "to suit your needs and then run it:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):452 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):459 msgid "Bootstrapping the system" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):452 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):459 #, no-wrap msgid "" "\n" @@ -593,38 +601,38 @@ msgid "" "# <i>./bootstrap.sh</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):459 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):466 msgid "" "Next, rebuild all core system packages with the newly built toolchain. We " "need to rebuild them since the stage3 tarball already offers them:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):464 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):471 msgid "Rebuilding the core system packages" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):464 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):471 #, no-wrap msgid "" "\n" "# <i>emerge -e system</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):468 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):475 msgid "" "Now you can continue with <e>Configuring the Kernel</e>. You can not use the " "prebuilt GRP packages anymore though." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):478 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):485 msgid "Package Management" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):480 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):487 msgid "In what form are the packages stored?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):483 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):490 msgid "" "Packages aren't \"stored\" per se. Instead, Gentoo provides a set of scripts " "which can resolve dependencies, fetch source code, and compile a version of " @@ -634,7 +642,7 @@ msgid "" "contents of an ebuild script in detail." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):492 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):499 msgid "" "For full ISO releases, we create a full suite of binary packages in an " "enhanced <c>.tbz2</c> format, which is <c>.tar.bz2</c> compatible with meta-" @@ -643,18 +651,18 @@ msgid "" "efficiently." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):499 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):506 msgid "" "It is possible to create RPMs (Redhat package manager files) using Gentoo's " "Portage, but it is not currently possible to use already existing RPMs to " "install packages." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):508 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):515 msgid "I want to perform the ./configure step myself. Can I?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):511 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):518 msgid "" "Yes, but it is not trivial, nor is it recommended. Since the method to do " "this requires a good understanding of Portage internals and commands, it is " @@ -665,22 +673,22 @@ msgid "" "HOWTO</uri> for more information." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):524 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):531 msgid "How do I use emerge from behind a firewall?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):527 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):534 msgid "" "See the questions on <uri link=\"#proxy\">proxies</uri>, <uri link=\"#norsync" "\">rsync</uri>, and <uri link=\"#manualdownload\">downloading source files " "manually</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):536 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):543 msgid "What if rsync doesn't work for me?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):539 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):546 msgid "" "If you're behind a firewall that doesn't permit rsync traffic, then you can " "use <c>emerge-webrsync</c> which will fetch and install a Portage snapshot " @@ -689,13 +697,13 @@ msgid "" "Portage snapshots via a proxy." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):550 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):557 msgid "" "I have only slow modem connection at home. Can I download sources somewhere " "else and add them to my system?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):556 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):563 msgid "" "Definitely. You can run <c>emerge --pretend package</c> to see what programs " "are going to be installed. To find out the sources for those packages and " @@ -705,13 +713,13 @@ msgid "" "c>. Be warned, however, that this is a tedious process." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):568 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):575 msgid "" "Source tarballs are collecting in /usr/portage/distfiles/. Is it safe to " "delete these files?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):574 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):581 msgid "" "Deleting these files will have no negative impact on day-to-day performance. " "However, it might be wise to keep the most recent version of the files; " @@ -720,7 +728,7 @@ msgid "" "software it will be necessary to download them from the internet again." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):582 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):589 msgid "" "You can use the <c>eclean</c> script from <c>app-portage/gentoolkit</c> to " "manage the contents of <path>/usr/portage/distfiles/</path> and a few other " @@ -728,13 +736,13 @@ msgid "" "well as the <uri link=\"/doc/en/gentoolkit.xml\">Gentoolkit Guide</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):592 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):599 msgid "" "What's in /var/tmp/portage? Is it safe to delete the files and directories " "in /var/tmp/portage?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):598 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):605 msgid "" "During compilation, Gentoo saves the sources of the package in <path>/var/" "tmp/portage</path>. These files and folder are usually deleted upon a " @@ -743,15 +751,15 @@ msgid "" "always <c>pgrep emerge</c> before cleaning out this directory." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):611 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):618 msgid "Usage" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):613 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):620 msgid "How do I set up an International Keyboard Layout?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):616 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):623 msgid "" "Edit the <c>KEYMAP</c> variable in <path>/etc/conf.d/keymaps</path>. To have " "console working correctly with extended characters in your keymap you might " @@ -762,11 +770,11 @@ msgid "" "the keymaps and consolefont scripts:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):626 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):633 msgid "Restarting keymaps" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):626 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):633 #, no-wrap msgid "" "\n" @@ -774,98 +782,98 @@ msgid "" "# <i>/etc/init.d/consolefont restart</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):634 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):641 msgid "DNS name resolution works for root only" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):637 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):644 msgid "" "<path>/etc/resolv.conf</path> has the wrong permissions; <c>chmod</c> it as " "follows:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):642 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):649 msgid "Changing permissions on /etc/resolv.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):642 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):649 #, no-wrap msgid "" "\n" "# <i>chmod 0644 /etc/resolv.conf</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):649 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):656 msgid "Why can't my user use their own crontab?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):652 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):659 msgid "You need to add that user to the <c>cron</c> group." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):659 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):666 msgid "How do I get numlock to start on boot?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):662 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):669 msgid "" "If you work in command line, you only need to <c>rc-update add numlock " "default &&/etc/init.d/numlock start</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):667 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):674 msgid "" "Each GUI provides different tools for this sort of thing; please check the " "help section or online manuals for assistance." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):675 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):682 msgid "How do I have my terminal cleared when I log out?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):678 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):685 msgid "" "To have your terminal cleared, add <c>clear</c> to your <path>~/." "bash_logout</path> script:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):683 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):690 msgid "Clearing the terminal during logout" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):683 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):690 #, no-wrap msgid "" "\n" "$ <i>echo clear >> ~/.bash_logout</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):687 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):694 msgid "" "If you want this to happen automatically when you add a new user, do the " "same for the <path>/etc/skel/.bash_logout</path>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):692 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):699 msgid "Making new users their terminal clear on logout" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):692 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):699 #, no-wrap msgid "" "\n" "# <i>echo clear >> /etc/skel/.bash_logout</i>" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):700 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):707 msgid "Maintenance" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):702 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):709 msgid "ReiserFS and filesystem corruption issues -- how to fix them, etc" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):705 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):712 msgid "" "If your ReiserFS partition is corrupt, try booting the Gentoo Install CD and " "run <c>reiserfsck --rebuild-tree</c> on the corrupted filesystem. This " @@ -873,26 +881,26 @@ msgid "" "files or directories due to the corruption." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):717 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):724 msgid "Development" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):719 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):726 msgid "Where can I report bugs?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):722 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):729 msgid "" "Use our <uri link=\"https://bugs.gentoo.org\">Bugzilla</uri>. If you are " "unsure if your problem is an actual bug, you can visit <uri link=\"irc://irc." "gentoo.org/gentoo\">#gentoo</uri> on IRC." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):731 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):738 msgid "How often are new releases made?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):734 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):741 msgid "" "Gentoo's packages are usually updated shortly after the main authors release " "new code. As for when Gentoo itself makes new stage/profile/ISO releases, " @@ -902,26 +910,26 @@ msgid "" "\"#upgrade\">upgrading</uri> for more information." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):746 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):753 msgid "My speaker beeps like crazy. How do I disable console beeps?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):751 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):758 msgid "Console beeps can be turned off using setterm, like this:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):755 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):762 msgid "Using setterm" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):755 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):762 #, no-wrap msgid "" "\n" "# <i>setterm -blength 0</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):759 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):766 msgid "" "If you would like to turn off the console beeps on boot, you need to put " "this command in <path>/etc/conf.d/local.start</path>. However, this only " @@ -929,42 +937,42 @@ msgid "" "terminals, pipe the command output to the target terminal, like this:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):765 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre:caption):772 msgid "Using setterm (bis)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):765 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(pre):772 #, no-wrap msgid "" "\n" "# <i>setterm -blength 0 >/dev/vc/1</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):769 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):776 msgid "" "You need to replace /dev/vc/1 with the terminal you would like to disable " "console beeps for." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):779 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):786 msgid "Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):781 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):788 msgid "Where can I find more information about Gentoo Linux?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):784 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):791 msgid "" "The official Gentoo documentation can be found at <uri>http://www.gentoo.org/" "doc/en/</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):792 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):799 msgid "Can I buy a CD of Gentoo Linux?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):795 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):802 msgid "" "Install CDs for all supported architectures are available on our <uri link=" "\"http://www.cafepress.com/officialgentoo/\">Gentoo Store</uri>. When you " @@ -972,17 +980,17 @@ msgid "" "please consider buying from our store if possible." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):802 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):809 msgid "" "You can also find fresh CDs from various resellers listed on our <uri link=" "\"/main/en/where.xml\">Get Gentoo!</uri> page." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):810 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(title):817 msgid "This FAQ hasn't answered my question. What do I do now?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):813 +#: ../../gentoo/xml/htdocs/doc/en//faq.xml(p):820 msgid "" "A good first step is to browse through the relevant <uri link=\"/doc/en/" "index.xml\">documentation</uri>, failing that, the various Gentoo Linux " diff --git a/doc/gettext/ru/gcc-upgrading-upto-4.1.xml.po b/doc/gettext/ru/gcc-upgrading-upto-4.1.xml.po new file mode 100644 index 0000000..a0651a5 --- /dev/null +++ b/doc/gettext/ru/gcc-upgrading-upto-4.1.xml.po @@ -0,0 +1,634 @@ +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" +"PO-Revision-Date: 2011-10-28 22:38+0600\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\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//gcc-upgrading-upto-4.1.xml(title):7 +msgid "Gentoo GCC Upgrade Guide for GCC Up To 4.1" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):9 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):12 +msgid "Author" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):10 +msgid "amne@gentoo.org" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail):10 +msgid "Wernfried Haas" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):13 +msgid "jkt@gentoo.org" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail):13 +msgid "Jan Kundrát" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):15 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(author:title):18 +msgid "Editor" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):16 +msgid "halcy0n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(mail:link):19 +msgid "nightmorph" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(abstract):22 +msgid "This document will guide the user through the process of upgrading GCC." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(version):30 +msgid "23" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(date):31 +msgid "2008-07-19" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):34 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):80 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):167 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):333 +msgid "Introduction" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):36 +msgid "GCC Upgrading" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):39 +msgid "" +"Why should you upgrade? Well, GCC is quite similar to any other package on " +"your system, just a bit more critical. You should upgrade GCC whenever a new " +"version fixes some bug that annoys you, new functionality you need is " +"introduced, or if you want to keep your system up-to-date. If none of the " +"previous cases apply to you, you can safely postpone upgrade as long as your " +"GCC version is supported by Gentoo developers." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):48 +msgid "" +"If you install a new major version of GCC (such as 3.3.6 to 3.4.5), the " +"system will not switch over to use it automatically. You'll have to " +"explicitly request the change because the migration process might require " +"some additional steps. If you decide not to switch, Portage will continue to " +"use older version of your compiler until you change your mind, or remove the " +"old compiler from the system. Non-major gcc upgrades are switched " +"automatically for you (such as 3.4.5 to 3.4.6)." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):58 +msgid "" +"This guide will document the necessary steps required to perform a seamless " +"upgrade of the compiler used by your Gentoo box. A specific section is " +"dedicated to the <uri link=\"#upgrade-3.3-to-3.4\">upgrade from GCC 3.3 to " +"3.4</uri> and issues with <c>libstdc++</c>. A second specific section is for " +"users <uri link=\"#first-install\">first installing</uri> Gentoo using a " +"stage3 tarball, after a new GCC major/minor version has been released." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(warn):67 +msgid "" +"It should be noted that upgrading from GCC-3.4 (or 3.3) to GCC-4.1 or " +"greater still requires you to follow the <uri link=\"#upgrade-general" +"\">general upgrading instructions</uri>, as GCC-3.4 and GCC-4.1 use slightly " +"different ABIs." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):78 +msgid "General Upgrade Instructions" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):83 +msgid "" +"If you're looking for instructions specific to upgrades from GCC-3.3 to " +"GCC-3.4, please consult the <uri link=\"#upgrade-3.3-to-3.4\">dedicated " +"section</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):89 +msgid "" +"If you're looking for instructions specific to upgrades in GCC for new " +"installs, please consult the <uri link=\"#first-install\">dedicated section</" +"uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):95 +msgid "" +"Generally speaking, upgrades to <e>bug fix releases</e>, like from 3.3.5 to " +"3.3.6, should be quite safe -- just emerge new version, switch your system " +"to use it and rebuild the only affected package, <c>libtool</c>. However, " +"some GCC upgrades break binary compatibility; in such cases a rebuild of the " +"affected packages (or even whole toolchain and system) might be required." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):103 +msgid "" +"When we spoke about the need to switch your compiler to the newer version by " +"hand, we said it won't happen automatically. However, there is one exception " +"-- upgrades to bug fix releases, like from 3.3.5 to 3.3.6 in case you don't " +"use the \"multislot\" feature allowing them to coexist on one system. " +"Multislot is disabled by default as the majority of users won't benefit from " +"it." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):111 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):278 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):366 +msgid "Upgrading GCC" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):111 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -uav gcc</i>\n" +"\n" +"<comment>(Please substitute \"i686-pc-linux-gnu-4.1.1\" with the GCC\n" +"version and CHOST settings you've upgraded to:)</comment>\n" +"# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>\n" +"# <i>env-update && source /etc/profile</i>\n" +"\n" +"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this\n" +"example) you will have to run fix_libtool_files.sh manually</comment>\n" +"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n" +"<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n" +"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.4.6</i>\n" +"\n" +"<comment>(Rebuilding libtool)</comment>\n" +"# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):129 +msgid "" +"To be completely safe that your system is in a sane state, you <e>must</e> " +"rebuild the toolchain and then world to make use of the new compiler." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):134 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):433 +msgid "Rebuilding system" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):134 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -eav system</i>\n" +"# <i>emerge -eav world</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):139 +msgid "" +"It is safe to remove the older GCC version at this time. If you feel the " +"need, please issue the following command (as usual, substitute <c>=sys-devel/" +"gcc-3.4*</c> with the version you want to uninstall):" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):145 +msgid "Removing older GCC version" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):145 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -aC =sys-devel/gcc-3.4*</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):149 +msgid "" +"Please note that the GCC 4.1 and newer can compile only kernels newer than " +"2.4.34. Don't remove your old GCC version if you want to use an older kernel." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):154 +msgid "" +"In case you're upgrading from GCC-3.3, you should run <c>emerge --oneshot " +"sys-libs/libstdc++-v3</c> to provide compatibility with older binary C++ " +"applications." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):165 +msgid "Upgrading from GCC-3.3 to 3.4" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):170 +msgid "" +"The upgrade from GCC-3.3 to 3.4 is not seamless as the C++ ABI changed " +"between these two versions. There is an issue with the <c>libstdc++</c> " +"library which must be taken care of, as well." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):179 +msgid "The Choices" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):182 +msgid "" +"If you upgrade from gcc 3.4 to 4.1, please consult the <uri link=\"#upgrade-" +"general\">General Update instructions</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(impo):187 +msgid "" +"If you're upgrading on a SPARC machine, you will have to take the way of " +"<uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system rebuild</uri> due " +"to some internal <uri link=\"http://gcc.gnu.org/gcc-3.4/sparc-abi.html\">ABI " +"changes</uri> in GCC's parameter passing." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):194 +msgid "" +"If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to " +"upgrade your system. The <uri link=\"#upgrade-3.3-to-3.4-revdep-rebuild" +"\">first method</uri> is faster and requires use of the <c>revdep-rebuild</" +"c> tool from package <c>gentoolkit</c> while the <uri link=\"#upgrade-3.3-" +"to-3.4-emerge-e\">second one</uri> rebuilds the entire system from scratch " +"so it will make use of new GCC features. It's up to you to decide which of " +"these two ways you will choose. In most cases, the first method is " +"sufficient." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):205 +msgid "" +"If you upgrade from gcc 3.3 to 4.1, do not use the method based on revdep-" +"rebuild, but do a <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system " +"rebuild</uri>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):214 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):242 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):390 +msgid "Using revdep-rebuild" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):217 +msgid "" +"This method requires that you first install <c>gentoolkit</c> if you have " +"not already done so. Then we will upgrade GCC and switch to the new " +"compiler. We will also rebuild the <c>libtool</c> package to ensure that " +"toolchain is in healthy state." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):224 +msgid "Installing gentoolkit and upgrading GCC" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):224 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -an gentoolkit</i>\n" +"# <i>emerge -uav gcc</i>\n" +"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" +"version and CHOST settings you've upgraded to:)</comment>\n" +"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" +"# <i>source /etc/profile</i>\n" +"\n" +"<comment>(Rebuilding libtool)</comment>\n" +"# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):236 +msgid "" +"Now, we want to see which packages that revdep-rebuild will want to rebuild. " +"Then we will tell revdep-rebuild to actually rebuild the packages. This may " +"take some time, so have some patience." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):242 +#, no-wrap +msgid "" +"\n" +"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" +"# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(note):247 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(note):405 +msgid "" +"It is possible that you might have problems with non-existing package " +"versions due to them being outdated or masked. If this is the case, you will " +"want to use the <c>--package-names</c> option to <c>revdep-rebuild</c>. This " +"causes packages to be recompiled based on the package name, rather than the " +"exact name and version." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):255 +msgid "" +"To provide compatibility with older binary C++ applications and any packages " +"that revdep-rebuild might have missed, <c>sys-libs/libstdc++-v3</c> needs to " +"be merged before you unmerge GCC 3.3 from your system." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):261 +msgid "Installing libstdc++-v3 and cleaning up" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):261 +#, no-wrap +msgid "" +"\n" +"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" +"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):269 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):416 +msgid "Using emerge -e" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):272 +msgid "" +"This method, while much slower, will rebuild your whole system to ensure " +"that everything has been rebuilt with your new compiler, and therefore " +"safer. At first, you will upgrade GCC and libtool and switch to your new " +"compiler." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):278 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -uav gcc</i>\n" +"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" +"version and CHOST settings you've upgraded to:)</comment>\n" +"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" +"# <i>source /etc/profile</i>\n" +"\n" +"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this\n" +"example) you will have to run fix_libtool_files.sh manually</comment>\n" +"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n" +"<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n" +"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</i>\n" +"\n" +"<comment>(Rebuilding libtool)</comment>\n" +"# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):295 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):377 +msgid "" +"To provide compatibility with older binary C++ applications, <c>sys-libs/" +"libstdc++-v3</c> needs to be merged onto your system." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):300 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):382 +msgid "Installing libstdc++-v3" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):300 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):382 +#, no-wrap +msgid "" +"\n" +"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):304 +msgid "" +"Now we will go about first rebuilding the system target, then the world " +"target. This will take a very long time, depending on the number of packages " +"that you have installed, as it will rebuild your entire toolchain and " +"supporting system files, followed by every package on your system, including " +"the toolchain. This is necessary to ensure that all packages have been " +"compiled with the new toolchain, including the toolchain itself." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):313 +msgid "Rebuilding system and world" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):313 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -e system</i>\n" +"# <i>emerge -e world</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):318 +msgid "It is also safe to remove older GCC versions at this time:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):322 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):440 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):448 +msgid "Cleaning up" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):322 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):331 +msgid "Upgrading to GCC on a First Install" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):336 +msgid "" +"A GCC upgrade on a system after installation from a stage3 tarball is a " +"simple affair. One advantage users of new installations have is they do not " +"have a plethora of software installed that links against the older version " +"of GCC. The following example is for a GCC-3.3 to 3.4 upgrade. Certain parts " +"will be different if upgrading from other versions of GCC. For example, the " +"library names used for <c>revdep-rebuild</c> below are GCC 3.3 specific, as " +"well as the need to install <c>libstdc++-v3</c>." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):346 +msgid "" +"If a user has not made any customizations to their system yet, then there " +"are very few steps to get their system upgraded to a new GCC version. As " +"with the GCC-3.3 to 3.4 upgrade, the user has a couple options. However, " +"unlike the GCC-3.3 to 3.4 upgrade, this one is less complicated as there are " +"fewer differences between the methods. The <uri link=\"#first-install-revdep-" +"rebuild\">first method</uri> is faster and makes use of the <c>revdep-" +"rebuild</c> tool from <c>gentoolkit</c>, similar to the above procedure. " +"Using revdep-rebuild causes only packages which actually link against GCC " +"libraries to be rebuilt, while the <uri link=\"#first-install-emerge-e" +"\">second method</uri> causes your entire new install to be recompiled with " +"the new GCC version and takes much longer. This second method is never " +"required and only documented for completeness." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):361 +msgid "" +"These first steps are common between both methods, and should be completed " +"by everyone." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):366 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -uav gcc</i>\n" +"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" +"version and CHOST settings you've upgraded to:)</comment>\n" +"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" +"# <i>source /etc/profile</i>\n" +"\n" +"<comment>(Rebuilding libtool)</comment>\n" +"# <i>emerge --oneshot -av libtool</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):393 +msgid "" +"This method requires that you first install <c>gentoolkit</c> if you have " +"not already done so. We will then run <c>revdep-rebuild</c> to actually scan " +"the installed packages for ones we need to rebuild, then rebuild them." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):399 +msgid "Installing gentoolkit and running revdep-rebuild" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):399 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -an gentoolkit</i>\n" +"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" +"# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):419 +msgid "" +"This method, while much slower, will rebuild the system target to ensure " +"that everything has been rebuilt with your new compiler. This is not " +"necessary, but is valid if you are also making changes to CFLAGS or other " +"make.conf variables that will affect the system compile." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):426 +msgid "" +"Since we are performing these actions after an initial installation, we do " +"not need to recompile the <c>world</c> target as we would when doing an " +"upgrade on an already installed system. However, you may choose to perform a " +"world update in place of the system update, to ensure that all packages are " +"updated." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):433 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -e system</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):443 +msgid "" +"It is also safe to remove older GCC versions at this time. Please substitute " +"<c>YOUR-NEW-GCC-VERSION</c> with the actual version you've upgraded to:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):448 +#, no-wrap +msgid "" +"\n" +"# <i>emerge -aC \"<sys-devel/gcc-YOUR-NEW-GCC-VERSION\"</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):457 +msgid "Common Pitfalls" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):461 +msgid "" +"It's important to disable <c>distcc</c> during upgrade. Mixing compiler " +"versions on your nodes <e>will</e> cause build issues. This is not required " +"for ccache, as the cache objects will be invalidated anyway." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):467 +msgid "" +"Always use same GCC version for your kernel and additional kernel modules. " +"Once you rebuild your world with new GCC, external modules (like <c>app-" +"emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel " +"with the new GCC to fix that." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):474 +msgid "" +"If you're upgrading on a SPARC machine, make sure to rerun <c>silo -f</c> " +"after re-emerging world to avoid possible issues." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(title):482 +msgid "Frequent Error Messages" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):485 +msgid "" +"If your system complains about something like <e>libtool: link: `/usr/lib/" +"gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool " +"archive</e>, please run <c>/usr/share/gcc-data/$CHOST/<gcc-version>/" +"fix_libtool_files.sh 3.3.6</c> (substitute \"3.3.6\" with the version " +"numbers from the error message, and $CHOST and <gcc-version> with your " +"actual CHOST and GCC version)." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):494 +msgid "" +"If you see <e>error: /usr/bin/gcc-config: line 632: /etc/env.d/gcc/i686-pc-" +"linux-gnu-3.3.5: No such file or directory</e>, then try deleting <path>/etc/" +"env.d/gcc/config-i686-pc-linux-gnu</path> and running <c>gcc-config</c> " +"again, followed by <c>source /etc/profile</c>. Only do this if you do not " +"have any cross-compilers set up, though." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):502 +msgid "" +"If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, " +"you can resume operation with <c>emerge --resume</c>. If a package fails " +"repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any " +"other instances of emerge in between or you will lose the resume information." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(p):509 +msgid "" +"If you get an error message <e>spec failure: unrecognized spec option</e> " +"while upgrading your compiler, try to switch back to your default compiler, " +"unset the <c>GCC_SPECS</c> variable and upgrade GCC again:" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre:caption):515 +msgid "Restoring primary specs" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(pre):515 +#, no-wrap +msgid "" +"\n" +"# <i>gcc-config 1</i>\n" +"# <i>source /etc/profile</i>\n" +"# <i>unset GCC_SPECS</i>\n" +"# <i>emerge -uav gcc</i>\n" +msgstr "" + +#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading-upto-4.1.xml(None):0 +msgid "translator-credits" +msgstr "" diff --git a/doc/gettext/ru/gcc-upgrading.xml.po b/doc/gettext/ru/gcc-upgrading.xml.po index 5683388..316c346 100644 --- a/doc/gettext/ru/gcc-upgrading.xml.po +++ b/doc/gettext/ru/gcc-upgrading.xml.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2011-01-26 13:57+0500\n" "Last-Translator: Azamat H. Hackimov <azamat.hackimov@gmail.com>\n" "Language-Team: Russian <kde-russian@lists.kde.ru>\n" @@ -22,757 +22,284 @@ msgid "Gentoo GCC Upgrade Guide" msgstr "Руководство Gentoo по обновлению GCC" #: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):9 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):12 msgid "Author" msgstr "автор" #: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):10 -msgid "amne@gentoo.org" -msgstr "amne@gentoo.org" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail):10 -msgid "Wernfried Haas" -msgstr "Wernfried Haas" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):13 -msgid "jkt@gentoo.org" -msgstr "jkt@gentoo.org" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail):13 -msgid "Jan Kundrát" -msgstr "Jan Kundrát" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):15 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):18 -msgid "Editor" -msgstr "редактор" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):16 -msgid "halcy0n" -msgstr "halcy0n" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):19 -msgid "nightmorph" -msgstr "nightmorph" +msgid "swift" +msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(abstract):22 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(abstract):13 msgid "This document will guide the user through the process of upgrading GCC." msgstr "Этот документ поможет пользователю осуществить обновление GCC." -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(version):30 -msgid "23" -msgstr "23" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(date):31 -msgid "2008-07-19" -msgstr "2008-07-19" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):34 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):80 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):167 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):333 -msgid "Introduction" -msgstr "Введение" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):36 -msgid "GCC Upgrading" -msgstr "Обновление GCC" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):39 -msgid "" -"Why should you upgrade? Well, GCC is quite similar to any other package on " -"your system, just a bit more critical. You should upgrade GCC whenever a new " -"version fixes some bug that annoys you, new functionality you need is " -"introduced, or if you want to keep your system up-to-date. If none of the " -"previous cases apply to you, you can safely postpone upgrade as long as your " -"GCC version is supported by Gentoo developers." -msgstr "" -"Зачем нужно обновлять? Ну, GCC схож с любым другим пакетов в вашей системе, " -"только он чуточку важнее. GCC следует обновлять всякий раз, когда в новой " -"версии исправляются какие-нибудь раздражающие вас ошибки, добавляется новые " -"нужные функции, или если вы хотите держать свою систему обновленной. Если ни " -"один из этих случаев к вам не относится, обновление можно спокойно " -"откладывать, пока ваша версия GCC поддерживается разработчиками Gentoo." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):48 -msgid "" -"If you install a new major version of GCC (such as 3.3.6 to 3.4.5), the " -"system will not switch over to use it automatically. You'll have to " -"explicitly request the change because the migration process might require " -"some additional steps. If you decide not to switch, Portage will continue to " -"use older version of your compiler until you change your mind, or remove the " -"old compiler from the system. Non-major gcc upgrades are switched " -"automatically for you (such as 3.4.5 to 3.4.6)." -msgstr "" -"Если вы обновляете основную версию GCC (например, с 3.3.6 на 3.4.5), система " -"не переключится на ее использование автоматически. Вам необходимо явно " -"запросить изменение, потому что в процессе перехода может потребоваться " -"несколько дополнительных действий. Если вы решите не переключаться, система " -"Portage будет использовать более старую версию компилятора до тех пор, пока " -"вы не передумаете или пока не удалите старый компилятор из своей системы. " -"Неосновные обновления GCC (например, с 3.4.5 на 3.4.6) переключаются " -"автоматически." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):58 -msgid "" -"This guide will document the necessary steps required to perform a seamless " -"upgrade of the compiler used by your Gentoo box. A specific section is " -"dedicated to the <uri link=\"#upgrade-3.3-to-3.4\">upgrade from GCC 3.3 to " -"3.4</uri> and issues with <c>libstdc++</c>. A second specific section is for " -"users <uri link=\"#first-install\">first installing</uri> Gentoo using a " -"stage3 tarball, after a new GCC major/minor version has been released." -msgstr "" -"В этом руководстве описываются обязательные шаги, необходимые для " -"полноценного обновления компилятора, используемого в вашей системе Gentoo. " -"Отдельный разделпосвящен <uri link=\"#upgrade-3.3-to-3.4\">переходу с GCC " -"3.3 на 3.4</uri> и проблемам с <c>libstdc++</c>. Другой частный раздел " -"предназначен пользователям, <uri link=\"#first-install\">впервые " -"устанавливающим</uri> Gentoo из архива третьей стадии (stage3) после выхода " -"новой основной/неосновной версии GCC." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(warn):67 -msgid "" -"It should be noted that upgrading from GCC-3.4 (or 3.3) to GCC-4.1 or " -"greater still requires you to follow the <uri link=\"#upgrade-general" -"\">general upgrading instructions</uri>, as GCC-3.4 and GCC-4.1 use slightly " -"different ABIs." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(version):21 +msgid "25" msgstr "" -"Необходимо заметить, что обновление с GCC-3.4 (или 3.3) до GCC-4.1 или более " -"нового также требует от вас следованию <uri link=\"#upgrade-general\">общим " -"инструкциям по обновлению</uri>, так как в GCC-3.4 и GCC-4.1 используются " -"слегка отличные друг от друга двоичные прикладные интерфейсы (ABI)." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):78 -msgid "General Upgrade Instructions" -msgstr "Общие указания по обновлению" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):83 -msgid "" -"If you're looking for instructions specific to upgrades from GCC-3.3 to " -"GCC-3.4, please consult the <uri link=\"#upgrade-3.3-to-3.4\">dedicated " -"section</uri>." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(date):22 +msgid "2011-10-15" msgstr "" -"Если вам нужны указания по обновлению с GCC-3.3 на GCC-3.4, обратитесь к " -"<uri link=\"#upgrade-3.3-to-3.4\">соответствующему разделу</uri>." -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):89 -msgid "" -"If you're looking for instructions specific to upgrades in GCC for new " -"installs, please consult the <uri link=\"#first-install\">dedicated section</" -"uri>." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):25 +msgid "Quickstart" msgstr "" -"Если вам нужны указания по обновлению GCC на вновь установленных системах, " -"обратитесь к <uri link=\"#first-install\">соответствующему разделу</uri>." -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):95 -msgid "" -"Generally speaking, upgrades to <e>bug fix releases</e>, like from 3.3.5 to " -"3.3.6, should be quite safe -- just emerge new version, switch your system " -"to use it and rebuild the only affected package, <c>libtool</c>. However, " -"some GCC upgrades break binary compatibility; in such cases a rebuild of the " -"affected packages (or even whole toolchain and system) might be required." -msgstr "" -"Вообще говоря, переход на <e>версии с исправленными ошибками (bugfix release)" -"</e>, как с 3.3.5 на 3.3.6, должен быть довольно безопасен — надо только " -"установить новую версию, переключиться на нее и пересобрать единственный " -"затрагиваемый пакет — <c>libtool</c>. Однако при некоторых обновлениях GCC " -"может нарушаться двоичная совместимость; в таких случаях необходима " -"пересборка всех затрагиваемых пакетов (или даже всего системного набора и " -"пакетов, необходимых для компиляции)." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):103 -msgid "" -"When we spoke about the need to switch your compiler to the newer version by " -"hand, we said it won't happen automatically. However, there is one exception " -"-- upgrades to bug fix releases, like from 3.3.5 to 3.3.6 in case you don't " -"use the \"multislot\" feature allowing them to coexist on one system. " -"Multislot is disabled by default as the majority of users won't benefit from " -"it." -msgstr "" -"Говоря о необходимости ручного переключения на новую версию компилятора, мы " -"сказали, что оно не происходит автоматически. Тем не менее, есть одно " -"исключение — переход на версию с исправленными ошибками (например, с 3.3.5 " -"на 3.3.6), если при этом не задействован режим «multislot», позволяющий " -"обеим версиям сосуществовать в одной системе. По умолчанию этот режим " -"выключен, ведь большинству пользователей он ничего не даст." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):111 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):278 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):366 -msgid "Upgrading GCC" -msgstr "Обновление GCC" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):27 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):84 +msgid "Introduction" +msgstr "Введение" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):111 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):30 msgid "" -"\n" -"# <i>emerge -uav gcc</i>\n" -"\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-4.1.1\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>\n" -"# <i>env-update && source /etc/profile</i>\n" -"\n" -"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this\n" -"example) you will have to run fix_libtool_files.sh manually</comment>\n" -"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n" -"<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n" -"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.4.6</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" +"This is about <e>upgrading</e> GCC. Downgrading GCC might have unwanted side " +"effects. Please refer to <uri link=\"#troubleshooting\">Troubleshooting</" +"uri> for some commonly reported issues." msgstr "" -"\n" -"# <i>emerge -uav gcc</i>\n" -"\n" -"<comment>(Вместо \"i686-pc-linux-gnu-4.4.1\" укажите обновленную\n" -" версию GCC и настройки CHOST)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>\n" -"# <i>env-update && source /etc/profile</i>\n" -"\n" -"<comment>Если вы обновляетесь с gcc 3 на 4 (например, с 3.4.6 на 4.1.1)\n" -"вам понадобится запустить fix_libtool_files.sh вручную</comment>\n" -"<comment>(Замените $CHOST собственным значением CHOST из /etc/make.conf)</comment>\n" -"<comment>(Замените <gcc-version> новой версией GCC)</comment>\n" -"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.4.6</i>\n" -"\n" -"<comment>(Пересборка libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):129 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):36 msgid "" -"To be completely safe that your system is in a sane state, you <e>must</e> " -"rebuild the toolchain and then world to make use of the new compiler." +"The next section gives a quick primer into GCC upgrades (and how easy they " +"are). If you want to read the lengthy reasoning behind GCC upgrades, please " +"continue with <uri link=\"#explanation\">GCC Upgrading Explained</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):134 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):433 -msgid "Rebuilding system" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):134 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -eav system</i>\n" -"# <i>emerge -eav world</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):45 +msgid "Short Version" msgstr "" -"\n" -"# <i>emerge -eav system</i>\n" -"# <i>emerge -eav world</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):139 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):48 msgid "" -"It is safe to remove the older GCC version at this time. If you feel the " -"need, please issue the following command (as usual, substitute <c>=sys-devel/" -"gcc-3.4*</c> with the version you want to uninstall):" +"If you are upgrading GCC then you do not need to do anything except switch " +"compiler version and rebuild libtool:" msgstr "" -"Теперь можно без опасений удалить старую версию GCC. Если вы чувствуете " -"такую необходимость, введите следующую команду (как обычно, вместо <c>=sys-" -"devel/gcc-3.4*</c> укажите версию, которую собираетесь удалить):" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):145 -msgid "Removing older GCC version" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):53 +#, fuzzy +msgid "Switching GCC version" msgstr "Удаление более старой версии GCC" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):145 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):53 #, no-wrap msgid "" "\n" -"# <i>emerge -aC =sys-devel/gcc-3.4*</i>\n" -msgstr "" +"# <i>emerge -u gcc</i>\n" +"# <i>gcc-config -l</i>\n" +"[1] i686-pc-linux-gnu-4.4.5 *\n" +"[2] i686-pc-linux-gnu-4.5.3\n" "\n" -"# <i>emerge -aC =sys-devel/gcc-3.4*</i>\n" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):149 -msgid "" -"Please note that the GCC 4.1 and newer can compile only kernels newer than " -"2.4.34. Don't remove your old GCC version if you want to use an older kernel." -msgstr "" -"Помните, что GCC 4.1 и выше не может собирать ядра ниже 2.4.34. Если вы " -"собираетесь использовать старое ядро, то не удаляйте старую версию GCC." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):154 -msgid "" -"In case you're upgrading from GCC-3.3, you should run <c>emerge --oneshot " -"sys-libs/libstdc++-v3</c> to provide compatibility with older binary C++ " -"applications." -msgstr "" -"При обновлении с GCC-3.3 вам необходимо выполнить <c>emerge --oneshot sys-" -"libs/libstdc++-v3</c>, чтобы установить режим совместимости для старых " -"двоичных приложений, написанных на C++." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):165 -msgid "Upgrading from GCC-3.3 to 3.4" -msgstr "Переход с GCC-3.3 на 3.4" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):170 -msgid "" -"The upgrade from GCC-3.3 to 3.4 is not seamless as the C++ ABI changed " -"between these two versions. There is an issue with the <c>libstdc++</c> " -"library which must be taken care of, as well." -msgstr "" -"Переход с GCC-3.3 на 3.4 или более новую версию не так гладок, так как между " -"этими версиями изменился двоичный прикладной интерфейс C++ (ABI). Также " -"придется позаботиться о существующей проблеме с библиотекой <c>libstdc++</c>." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):179 -msgid "The Choices" -msgstr "Варианты" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):182 -msgid "" -"If you upgrade from gcc 3.4 to 4.1, please consult the <uri link=\"#upgrade-" -"general\">General Update instructions</uri>." -msgstr "" -"Если обновляете gcc с 3.4 до 4.1, ознакомьтесь с <uri link=\"#upgrade-general" -"\">общими инструкциями по обновлению</uri>." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):187 -msgid "" -"If you're upgrading on a SPARC machine, you will have to take the way of " -"<uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system rebuild</uri> due " -"to some internal <uri link=\"http://gcc.gnu.org/gcc-3.4/sparc-abi.html\">ABI " -"changes</uri> in GCC's parameter passing." -msgstr "" -"Если вы обновляете GCC на машине SPARC, вам придется выбрать путь <uri link=" -"\"#upgrade-3.3-to-3.4-emerge-e\">полной пересборки системы</uri> из-за " -"некоторых внутренних <uri link=\"http://gcc.gnu.org/gcc-3.4/sparc-abi.html" -"\">изменений ABI</uri> GCC в области передачи параметров функций." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):194 -msgid "" -"If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to " -"upgrade your system. The <uri link=\"#upgrade-3.3-to-3.4-revdep-rebuild" -"\">first method</uri> is faster and requires use of the <c>revdep-rebuild</" -"c> tool from package <c>gentoolkit</c> while the <uri link=\"#upgrade-3.3-" -"to-3.4-emerge-e\">second one</uri> rebuilds the entire system from scratch " -"so it will make use of new GCC features. It's up to you to decide which of " -"these two ways you will choose. In most cases, the first method is " -"sufficient." -msgstr "" -"Если вы обновляете gcc 3.4 до 3.4, у вас есть два варианта обновления " -"системы. <uri link=\"#upgrade-3.3-to-3.4-revdep-rebuild\">Первый способ</" -"uri> быстрее и требует использования программы <c>revdep-rebuild</c> из " -"пакета <c>gentoolkit</c>, а <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">во " -"втором</uri> вся система пересобирается с нуля, чтобы задействовать новые " -"возможности GCC. Ваше дело, какой из способов выбрать. В большинстве случаев " -"первого способавполне достаточно." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):205 -msgid "" -"If you upgrade from gcc 3.3 to 4.1, do not use the method based on revdep-" -"rebuild, but do a <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system " -"rebuild</uri>." -msgstr "" -"Если вы обновляете gcc с 3.3 до 4.1, не используйте способ, основанный на " -"revdep-rebuild, необходимо <uri link=\"#upgrade-3.3-to-3.4-emerge-e" -"\">пересобрать систему целиком</uri>." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):214 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):242 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):390 -msgid "Using revdep-rebuild" -msgstr "Использование revdep-rebuild" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):217 -msgid "" -"This method requires that you first install <c>gentoolkit</c> if you have " -"not already done so. Then we will upgrade GCC and switch to the new " -"compiler. We will also rebuild the <c>libtool</c> package to ensure that " -"toolchain is in healthy state." +"# <i>gcc-config 2</i>\n" +"# <i>env-update && source /etc/profile</i>\n" +"# <i>emerge --oneshot libtool</i>\n" msgstr "" -"Для этого способа необходимо сначала установить <c>gentoolkit</c>, если вы " -"еще этого не сделали. Затем обновите GCC и переключите систему на новый " -"компилятор. Также пересоберите пакет <c>libtool</c>, чтобы обеспечить " -"пригодность программ для компиляции." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):224 -msgid "Installing gentoolkit and upgrading GCC" -msgstr "Установка gentoolkit и обновление GCC" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):224 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):64 msgid "" -"\n" -"# <i>emerge -an gentoolkit</i>\n" -"# <i>emerge -uav gcc</i>\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" -"# <i>source /etc/profile</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" +"If you upgrade GCC from a version earlier than 3.4.0 (for the 3.x series) or " +"4.1, you will need to run <c>revdep-rebuild</c> as well:" msgstr "" -"\n" -"# <i>emerge -an gentoolkit</i>\n" -"# <i>emerge -uav gcc</i>\n" -"<comment>(Вместо \"i686-pc-linux-gnu-3.4.5\" укажите обновленную\n" -"версию GCC и настройки CHOST:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" -"# <i>source /etc/profile</i>\n" -"\n" -"<comment>(Пересборка libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):236 -msgid "" -"Now, we want to see which packages that revdep-rebuild will want to rebuild. " -"Then we will tell revdep-rebuild to actually rebuild the packages. This may " -"take some time, so have some patience." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):69 +msgid "Upgrading from a non-forward compatible GCC version" msgstr "" -"Теперь посмотрите, какие пакеты собирается пересобирать revdep-rebuild, " -"затем запустите revdep-rebuild на собственно пересборку. Это займет " -"некоторое время, так что потерпите." -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):242 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):69 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):135 +#, fuzzy, no-wrap msgid "" "\n" -"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" "# <i>revdep-rebuild --library libstdc++.so.5</i>\n" msgstr "" "\n" "# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" "# <i>revdep-rebuild --library libstdc++.so.5</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(note):247 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(note):405 -msgid "" -"It is possible that you might have problems with non-existing package " -"versions due to them being outdated or masked. If this is the case, you will " -"want to use the <c>--package-names</c> option to <c>revdep-rebuild</c>. This " -"causes packages to be recompiled based on the package name, rather than the " -"exact name and version." -msgstr "" -"Возможно, у вас появятся проблемы с несуществующими версиями пакетов из-за " -"того, что они устарели или замаскированы. В этом случае можно при запуске " -"<c>revdep-rebuild</c> указать параметр <c>--package-names</c>. Этом случае " -"пакеты будут пересобираться на основе на имен, вместо точного имени и версии." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):255 -msgid "" -"To provide compatibility with older binary C++ applications and any packages " -"that revdep-rebuild might have missed, <c>sys-libs/libstdc++-v3</c> needs to " -"be merged before you unmerge GCC 3.3 from your system." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):73 +msgid "There you go. Enjoy the new compiler!" msgstr "" -"Для обеспечения совместимости с более старыми двоичными приложениями C++ и " -"любыми пакетами, которые revdep-rebuild мог пропустить, надо установить " -"пакет<c>sys-libs/libstdc++-v3</c> до того, как удалять GCC 3.3 из своей " -"системы." - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):261 -msgid "Installing libstdc++-v3 and cleaning up" -msgstr "Установка libstdc++-v3 и удаление GCC" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):261 -#, no-wrap -msgid "" -"\n" -"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" -"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" -msgstr "" -"\n" -"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" -"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):269 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):416 -msgid "Using emerge -e" -msgstr "Использование emerge -e" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):272 -msgid "" -"This method, while much slower, will rebuild your whole system to ensure " -"that everything has been rebuilt with your new compiler, and therefore " -"safer. At first, you will upgrade GCC and libtool and switch to your new " -"compiler." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):278 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -uav gcc</i>\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" -"# <i>source /etc/profile</i>\n" -"\n" -"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this\n" -"example) you will have to run fix_libtool_files.sh manually</comment>\n" -"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n" -"<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n" -"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" -msgstr "" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):82 +#, fuzzy +msgid "GCC Upgrading Explained" +msgstr "Обновление GCC" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):295 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):377 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):87 msgid "" -"To provide compatibility with older binary C++ applications, <c>sys-libs/" -"libstdc++-v3</c> needs to be merged onto your system." +"GCC upgrading has always been mystified, with suggestions ranging from \"You " +"do not need to do anything\" up to \"You will need to rebuild your entire " +"system twice\". Most of this FUD comes from the confusion surrounding ABI " +"incompatibility. But first a quick pointer towards <c>libtool</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):300 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):382 -msgid "Installing libstdc++-v3" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):97 +msgid "libtool and fix_libtool_files.sh" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):300 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):382 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):100 msgid "" -"\n" -"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" +"Earlier installments of GCC on Gentoo required you to run a specific command " +"called <c>fix_libtool_files.sh</c>. Some time ago, the execution of this " +"command has been integrated in the package deployments itself (through the " +"toolchain eclass) so there is no need for users to call this themselves " +"anymore." msgstr "" -"\n" -"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):304 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):107 msgid "" -"Now we will go about first rebuilding the system target, then the world " -"target. This will take a very long time, depending on the number of packages " -"that you have installed, as it will rebuild your entire toolchain and " -"supporting system files, followed by every package on your system, including " -"the toolchain. This is necessary to ensure that all packages have been " -"compiled with the new toolchain, including the toolchain itself." +"The reason we need to rebuild libtool after the upgrade of gcc versions is " +"because of its main purpose: <e>libtool</e> is a toolset that aggregates " +"platform-specific code in a generic interface, allowing applications to " +"build against shared libraries without needing to deal with the platform " +"specific aspects of shared libraries. To fulfill its function properly, the " +"<c>libtool</c> script uses various library locations that have hardcoded GCC " +"version information in them." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):313 -msgid "Rebuilding system and world" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):120 +msgid "ABI Changes" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):313 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):123 msgid "" -"\n" -"# <i>emerge -e system</i>\n" -"# <i>emerge -e world</i>\n" -msgstr "" -"\n" -"# <i>emerge -e system</i>\n" -"# <i>emerge -e world</i>\n" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):318 -msgid "It is also safe to remove older GCC versions at this time:" +"An ABI, or <e>Application Binary Interface</e>, is a set of conventions used " +"by all tools that deal with binary representation of programs, including " +"compilers, assemblers, linkers and language runtime support (source: <uri " +"link=\"http://gcc.gnu.org/onlinedocs/gcc/Compatibility.html\">GCC Binary " +"Compatibility</uri>). When the ABI used for binary applications and " +"libraries is changed, you will risk getting linker errors or malfunctioning " +"programs unless you rebuild all libraries that use C++ code. Yes, C++, since " +"most incompatibilities occur within the C++ ABI. This is also why we use the " +"<c>revdep-rebuild</c> command against the <path>libstdc++.so.5</path> " +"library." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):322 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):440 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):448 -msgid "Cleaning up" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):135 +msgid "Rebuilding applications linked against libstdc++.so.5" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):322 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):139 msgid "" -"\n" -"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +"So why is this only needed up to GCC 3.4.0/4.1 ? That's because from that " +"version onwards, GCC uses a forward compatible ABI, which removes the need " +"for rebuilding applications and libraries. Of course, guarantees can never " +"be given indefinitely, but when an incompatibility occurs again, we'll " +"definitely document it here ;-) In that case, the version of the " +"<path>libstdc++.so</path> library will probably be increased." msgstr "" -"\n" -"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):331 -msgid "Upgrading to GCC on a First Install" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):151 +msgid "Rebuilding Everything" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):336 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):154 msgid "" -"A GCC upgrade on a system after installation from a stage3 tarball is a " -"simple affair. One advantage users of new installations have is they do not " -"have a plethora of software installed that links against the older version " -"of GCC. The following example is for a GCC-3.3 to 3.4 upgrade. Certain parts " -"will be different if upgrading from other versions of GCC. For example, the " -"library names used for <c>revdep-rebuild</c> below are GCC 3.3 specific, as " -"well as the need to install <c>libstdc++-v3</c>." +"Some people swear that they need to rebuild every single package on their " +"system when a new GCC version is made available. Of course, that doesn't " +"make sense, since there are many applications that are not using GCC for " +"their build and install process anyhow, so they would never be affected by " +"such changes." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):346 -msgid "" -"If a user has not made any customizations to their system yet, then there " -"are very few steps to get their system upgraded to a new GCC version. As " -"with the GCC-3.3 to 3.4 upgrade, the user has a couple options. However, " -"unlike the GCC-3.3 to 3.4 upgrade, this one is less complicated as there are " -"fewer differences between the methods. The <uri link=\"#first-install-revdep-" -"rebuild\">first method</uri> is faster and makes use of the <c>revdep-" -"rebuild</c> tool from <c>gentoolkit</c>, similar to the above procedure. " -"Using revdep-rebuild causes only packages which actually link against GCC " -"libraries to be rebuilt, while the <uri link=\"#first-install-emerge-e" -"\">second method</uri> causes your entire new install to be recompiled with " -"the new GCC version and takes much longer. This second method is never " -"required and only documented for completeness." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):361 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):161 msgid "" -"These first steps are common between both methods, and should be completed " -"by everyone." +"That however doesn't mean they are completely incorrect: newer GCC versions " +"often include better support for the processors' instruction set, which " +"might influence the performance of some applications in a positive way. " +"Although it is expected that this improvement is generally only marginally, " +"in some cases (especially CPU intensive applications) this might yield " +"notable improvements." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):366 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):169 msgid "" -"\n" -"# <i>emerge -uav gcc</i>\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" -"# <i>source /etc/profile</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" +"There are also known cases where packages need to be built with the same " +"compiler. Although these packages are usually bumped by Gentoo " +"simultaneously (so that they are always built with the same GCC version) " +"cherry-picking reinstalls on these packages might prove to be troublesome. " +"The various <path>qt-*</path> packages are a nice example on this matter." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):393 -msgid "" -"This method requires that you first install <c>gentoolkit</c> if you have " -"not already done so. We will then run <c>revdep-rebuild</c> to actually scan " -"the installed packages for ones we need to rebuild, then rebuild them." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):182 +msgid "Troubleshooting" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):399 -msgid "Installing gentoolkit and running revdep-rebuild" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):184 +msgid "libstdc++.so.6: version `GLIBCXX_3.4.15' not found" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):399 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -an gentoolkit</i>\n" -"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" -"# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):187 +msgid "During updates, you might encounter an error like the following:" msgstr "" -"\n" -"# <i>emerge -an gentoolkit</i>\n" -"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" -"# <i>revdep-rebuild --library libstdc++.so.5</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):419 -msgid "" -"This method, while much slower, will rebuild the system target to ensure " -"that everything has been rebuilt with your new compiler. This is not " -"necessary, but is valid if you are also making changes to CFLAGS or other " -"make.conf variables that will affect the system compile." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):191 +msgid "GLIBCXX_x.y.z not found" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):426 -msgid "" -"Since we are performing these actions after an initial installation, we do " -"not need to recompile the <c>world</c> target as we would when doing an " -"upgrade on an already installed system. However, you may choose to perform a " -"world update in place of the system update, to ensure that all packages are " -"updated." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):433 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):191 #, no-wrap msgid "" "\n" -"# <i>emerge -e system</i>\n" +"cmake_bootstrap_28021_test: /usr/lib/gcc/i486-pc-linux-gnu/4.1.2/libstdc++.so.6:\n" +"version `GLIBCXX_3.4.11' not found \n" msgstr "" -"\n" -"# <i>emerge -e system</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):443 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):196 msgid "" -"It is also safe to remove older GCC versions at this time. Please substitute " -"<c>YOUR-NEW-GCC-VERSION</c> with the actual version you've upgraded to:" +"This means that you are trying to build a package with an <e>older</e> GCC " +"version than with which some depending libraries were built. Remember when " +"we told that the C++ ABI if forward-compatible? That is true, but it ensures " +"only that <e>higher</e> (or same) GCC versions can be used when building " +"applications and linking libraries (compared to the GCC version used to " +"build those libraries)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):448 -#, fuzzy, no-wrap -msgid "" -"\n" -"# <i>emerge -aC \"<sys-devel/gcc-YOUR-NEW-GCC-VERSION\"</i>\n" -msgstr "" -"\n" -"# <i>emerge -aC \"<sys-devel/gcc-YOUR-NEW-GCC-VERSION\"</i>\n" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):457 -msgid "Common Pitfalls" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):208 +msgid "Which packages are known to need a rebuild?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):461 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):211 msgid "" -"It's important to disable <c>distcc</c> during upgrade. Mixing compiler " -"versions on your nodes <e>will</e> cause build issues. This is not required " -"for ccache, as the cache objects will be invalidated anyway." +"The following table gives the packages that, <e>if installed</e>, need to be " +"rebuild and why." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):467 -msgid "" -"Always use same GCC version for your kernel and additional kernel modules. " -"Once you rebuild your world with new GCC, external modules (like <c>app-" -"emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel " -"with the new GCC to fix that." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(th):218 +msgid "Package" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):474 -msgid "" -"If you're upgrading on a SPARC machine, make sure to rerun <c>silo -f</c> " -"after re-emerging world to avoid possible issues." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(th):219 +msgid "Rebuild needed because ..." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):482 -msgid "Frequent Error Messages" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):222 +msgid "sys-devel/libtool" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):485 -msgid "" -"If your system complains about something like <e>libtool: link: `/usr/lib/" -"gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool " -"archive</e>, please run <c>/usr/share/gcc-data/$CHOST/<gcc-version>/" -"fix_libtool_files.sh 3.3.6</c> (substitute \"3.3.6\" with the version " -"numbers from the error message, and $CHOST and <gcc-version> with your " -"actual CHOST and GCC version)." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):223 +msgid "libtool application has hardcoded paths towards GCC internal libraries" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):494 -msgid "" -"If you see <e>error: /usr/bin/gcc-config: line 632: /etc/env.d/gcc/i686-pc-" -"linux-gnu-3.3.5: No such file or directory</e>, then try deleting <path>/etc/" -"env.d/gcc/config-i686-pc-linux-gnu</path> and running <c>gcc-config</c> " -"again, followed by <c>source /etc/profile</c>. Only do this if you do not " -"have any cross-compilers set up, though." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):229 +msgid "dev-lang/ghc" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):502 -msgid "" -"If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, " -"you can resume operation with <c>emerge --resume</c>. If a package fails " -"repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any " -"other instances of emerge in between or you will lose the resume information." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):230 +msgid "ghc application has hardcoded paths towards GCC internal libraries" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):509 -msgid "" -"If you get an error message <e>spec failure: unrecognized spec option</e> " -"while upgrading your compiler, try to switch back to your default compiler, " -"unset the <c>GCC_SPECS</c> variable and upgrade GCC again:" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):241 +msgid "Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):515 -msgid "Restoring primary specs" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):243 +msgid "Gentoo Guides and Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):515 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(li):247 msgid "" -"\n" -"# <i>gcc-config 1</i>\n" -"# <i>source /etc/profile</i>\n" -"# <i>unset GCC_SPECS</i>\n" -"# <i>emerge -uav gcc</i>\n" +"<uri link=\"gcc-upgrading-upto-4.1.xml\">GCC Upgrading up to 4.1</uri>, the " +"previous version of this document" msgstr "" -"\n" -"# <i>gcc-config 1</i>\n" -"# <i>source /etc/profile</i>\n" -"# <i>unset GCC_SPECS</i>\n" -"# <i>emerge -uav gcc</i>\n" #. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL #: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(None):0 diff --git a/doc/gettext/ru/gentoo-x86-quickinstall-system.xml.po b/doc/gettext/ru/gentoo-x86-quickinstall-system.xml.po index b2a28fb..264b94d 100644 --- a/doc/gettext/ru/gentoo-x86-quickinstall-system.xml.po +++ b/doc/gettext/ru/gentoo-x86-quickinstall-system.xml.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-02-09 00:57+0500\n" "Last-Translator: Azamat H. Hackimov <azamat.hackimov@gmail.com>\n" "Language-Team: Russian <gentoo-doc-ru@gentoo.org>\n" @@ -15,11 +15,11 @@ msgstr "" "X-Generator: Lokalize 1.0\n" #: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(version):7 -msgid "4" +msgid "6" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(date):8 -msgid "2011-08-23" +msgid "2011-09-23" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):11 @@ -81,15 +81,16 @@ msgid "" "Configure your network in <path>/etc/conf.d/net</path>. Add the <c>net.eth0</" "c> init script to the default run level. If you have multiple NICs, symlink " "them to the <c>net.eth0</c> init script and add them to the default run " -"level as well. Either edit <path>/etc/conf.d/net</path> with <c>nano</c> or " +"level as well. Don't forget to set your hostname too. Either edit <path>/etc/" +"conf.d/net</path> and <path>/etc/conf.d/hostname</path> with <c>nano</c> or " "use the following commands:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):66 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):67 msgid "Configure networking" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):66 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):67 #, no-wrap msgid "" "\n" @@ -98,6 +99,7 @@ msgid "" "livecd init.d # <i>cd ../conf.d</i>\n" "livecd conf.d # <i>echo 'config_eth0=\"192.168.1.10 netmask 255.255.255.0 brd 192.168.1.255\"' >> net</i>\n" "livecd conf.d # <i>echo 'routes_eth0=\"default via 192.168.1.1\"' >> net</i>\n" +"livecd conf.d # <i>echo 'hostname=\"myhostname\"' > hostname</i>\n" "livecd conf.d # <i>rc-update add net.eth0 default</i>\n" "<comment>(If you compiled your network card driver as a module, add it to /etc/conf.d/modules</comment>\n" "livecd conf.d # <i>echo 'modules=\"r8169\"' >> /etc/conf.d/modules</i>\n" @@ -105,19 +107,19 @@ msgid "" "livecd conf.d # <i>rc-update add sshd default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):79 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):81 msgid "Emerge <c>pcmciautils</c> if you need support for PCMCIA cards." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):83 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):85 msgid "Set the root password using <c>passwd</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):87 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):89 msgid "Set the root password" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):87 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):89 #, no-wrap msgid "" "\n" @@ -127,33 +129,33 @@ msgid "" "passwd: password updated successfully\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):94 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):96 msgid "" "Edit <path>/etc/timezone</path> to define the time zone you used previously." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):99 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):101 msgid "Edit /etc/timezone" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):99 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):101 #, no-wrap msgid "" "\n" "Europe/Brussels\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):103 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):105 msgid "" "Check the system configuration in <path>/etc/rc.conf</path> and <path>/etc/" "conf.d/keymaps</path> and edit any of those files if required." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):108 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):110 msgid "Optional: edit some config files" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):108 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):110 #, no-wrap msgid "" "\n" @@ -161,32 +163,34 @@ msgid "" "livecd conf.d # <i>nano -w /etc/conf.d/keymaps</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):116 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):118 msgid "Installing System Tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):120 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):122 msgid "Install RAID and LVM2 utilities." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):124 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):126 msgid "Install RAID LVM2 tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):124 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):126 #, no-wrap msgid "" "\n" "livecd conf.d # <i>emerge mdadm lvm2</i>\n" +"livecd conf.d # <i>rc-update add mdraid boot</i>\n" +"livecd conf.d # <i>rc-update add lvm boot</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):131 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):135 msgid "" "Install a system logger like <c>syslog-ng</c> and a cron daemon like " "<c>vixie-cron</c>, and add them to the default run level." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):136 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(note):140 msgid "" "Cron daemons depend on an MTA. <c>mail-mta/ssmtp</c> will be pulled in as a " "dependency. If you want to use a more advanced MTA, you might want to " @@ -194,11 +198,11 @@ msgid "" "later when you install the MTA of your choice." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):143 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):147 msgid "Install a syslogger and a cron daemon" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):143 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):147 #, no-wrap msgid "" "\n" @@ -211,18 +215,18 @@ msgid "" "livecd conf.d # <i>rc-update add vixie-cron default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):153 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):157 msgid "" "Install the necessary file system tools (<c>xfsprogs</c>, <c>reiserfsprogs</" "c> or <c>jfsutils</c>) and networking tools (<c>dhcpcd</c> or <c>ppp</c>) if " "you need any." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):159 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):163 msgid "Install extra tools if required" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):159 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):163 #, no-wrap msgid "" "\n" @@ -233,21 +237,21 @@ msgid "" "livecd conf.d # <i>emerge ppp</i> <comment>(If you need PPPoE ADSL connectivity)</comment>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):171 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(title):175 msgid "Configuring the Bootloader" msgstr "Настройка начального загрузчика" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):174 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(p):178 msgid "" "Emerge <c>grub</c> and configure it. Do not forget to update the necessary " "boot parameters if you are using an initramfs." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):179 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):183 msgid "Emerge grub and edit its configuration file" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):179 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):183 #, no-wrap msgid "" "\n" @@ -259,11 +263,11 @@ msgid "" "livecd conf.d # <i>nano -w /boot/grub/grub.conf</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):188 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):192 msgid "Example grub.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):188 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):192 #, no-wrap msgid "" "\n" @@ -275,11 +279,11 @@ msgid "" "kernel /boot/kernel root=<keyval id=\"root\"></keyval>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):197 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):201 msgid "Install grub" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):197 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):201 #, no-wrap msgid "" "\n" @@ -302,11 +306,11 @@ msgid "" "grub> <i>quit</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):217 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre:caption):221 msgid "Install grub on both disks" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):217 +#: ../../gentoo/xml/htdocs/doc/en//gentoo-x86-quickinstall-system.xml(pre):221 #, no-wrap msgid "" "\n" diff --git a/doc/gettext/ru/gnome-config.xml.po b/doc/gettext/ru/gnome-config.xml.po index 77d3dc5..2732de5 100644 --- a/doc/gettext/ru/gnome-config.xml.po +++ b/doc/gettext/ru/gnome-config.xml.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-02-09 00:59+0500\n" "Last-Translator: Azamat H. Hackimov <azamat.hackimov@gmail.com>\n" "Language-Team: Russian <gentoo-doc-ru@gentoo.org>\n" @@ -54,11 +54,11 @@ msgid "" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(version):27 -msgid "3" +msgid "4" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(date):28 -msgid "2011-08-13" +msgid "2011-10-23" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):31 @@ -175,32 +175,35 @@ msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):122 msgid "" -"You can also opt for a minimal Gnome installation using <c>gnome-light</c>:" +"You can also opt for a minimal Gnome installation using <c>gnome-light</c>. " +"If you do so, you will have a lightweight Gnome installation without the " +"additional tools that a full Gnome installation provides so you might need " +"to install additional packages afterwards." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):126 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):129 msgid "Installing a minimal GNOME environment" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):126 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):129 #, no-wrap msgid "" "\n" "# <i>emerge gnome-light</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):130 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):133 msgid "" "This will take a while, so you might want to start reading all those books " "your mother bought you but you never opened. Done? Great, now update your " "environment variables:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):136 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):139 msgid "Updating environment variables" msgstr "Обновление переменных среды" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):136 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):139 #, no-wrap msgid "" "\n" @@ -209,15 +212,15 @@ msgstr "" "\n" "# <i>env-update && source /etc/profile</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):140 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):143 msgid "Next we'll clean up the remaining services and user groups." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):144 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):147 msgid "Setting up the DBUS service" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):144 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):147 #, fuzzy, no-wrap msgid "" "\n" @@ -227,18 +230,18 @@ msgstr "" "\n" "# <i>rc-update add xdm default</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):149 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):152 msgid "" "Check if the <e>plugdev</e> group exists. If it does, it is adviseable to " "make yourself member of that group, but this is optional (the group is not " "that common anymore)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):155 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):158 msgid "Checking and adding users to plugdev" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):155 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):158 #, no-wrap msgid "" "\n" @@ -249,11 +252,11 @@ msgid "" "~# <i>gpasswd -a yourUserName plugdev</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):166 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):169 msgid "First Impressions" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):169 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):172 msgid "" "Let us first take a look at what we just built. Exit your root shell and log " "on as a regular user. We will configure our session to run GNOME when we " @@ -262,18 +265,18 @@ msgid "" "xml\">X Server Configuration Howto</uri>):" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):177 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):180 msgid "Setting GNOME as the default desktop environment" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):177 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):180 #, no-wrap msgid "" "\n" "$ <i>echo \"exec gnome-session\" > ~/.xinitrc</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):181 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):184 msgid "" "Starting with <c>gnome-base/gnome-session-2.26.2</c>, you will need to " "prepend the XDG_MENU_PREFIX variable to get the Gnome menus if you're using " @@ -282,26 +285,26 @@ msgid "" "additional configuration is needed.)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):189 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):192 msgid "Prepending XDG_MENU_PREFIX to ~/.xinitrc" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):189 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):192 #, no-wrap msgid "" "\n" "$ <i>sed -i '1i\\export XDG_MENU_PREFIX=gnome-' ~/.xinitrc</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):193 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):196 msgid "Now start your graphical environment by running <c>startx</c>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):197 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):200 msgid "Starting GNOME" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):197 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):200 #, no-wrap msgid "" "\n" @@ -310,32 +313,32 @@ msgstr "" "\n" "$ <i>startx</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):201 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):204 msgid "" "If all goes well, you should be greeted by GNOME. Congratulations. Now let " "us take a look at how you can configure GNOME to suit your needs." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):210 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):213 msgid "Configuring GNOME" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):212 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(title):215 msgid "GNOME's Graphical Login Manager" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):215 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):218 msgid "" "If you want the GNOME Display Manager (GDM) to run automatically when you " "boot (so you can log on graphically), you must add the <c>xdm</c> init " "script to the default runlevel:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):221 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):224 msgid "Adding xdm to the default runlevel" msgstr "Добавление xdm в уровень исполнения по умолчанию" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):221 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):224 #, no-wrap msgid "" "\n" @@ -344,23 +347,41 @@ msgstr "" "\n" "# <i>rc-update add xdm default</i>\n" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):225 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):228 msgid "" "Now edit <path>/etc/conf.d/xdm</path> and alter the DISPLAYMANAGER variable." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):229 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):232 msgid "Editing /etc/conf.d/xdm" msgstr "Изменение /etc/conf.d/xdm" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):229 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):232 #, no-wrap msgid "" "\n" "DISPLAYMANAGER=\"gdm\"\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):233 +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):236 +msgid "" +"If you installed Gnome using the <c>gnome-light</c> package, you will need " +"to install <c>gdm</c> too (as it is not defined as part of the <c>gnome-" +"light</c> package)." +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre:caption):242 +msgid "Installing the gdm application" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(pre):242 +#, no-wrap +msgid "" +"\n" +"# <i>emerge gdm</i>\n" +msgstr "" + +#: ../../gentoo/xml/htdocs/doc/en//gnome-config.xml(p):246 msgid "" "If you reboot now, the GNOME Display Manager will prompt you for your " "username and password and will default to using GNOME as Desktop Environment " diff --git a/doc/gettext/ru/power-management-guide.xml.po b/doc/gettext/ru/power-management-guide.xml.po index 9cd4579..c3fc70a 100644 --- a/doc/gettext/ru/power-management-guide.xml.po +++ b/doc/gettext/ru/power-management-guide.xml.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-02-09 01:06+0500\n" "Last-Translator: Azamat H. Hackimov <azamat.hackimov@gmail.com>\n" "Language-Team: Russian <gentoo-doc-ru@gentoo.org>\n" @@ -23,2225 +23,725 @@ msgid "Author" msgstr "автор" #: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):9 -msgid "earthwings@gentoo.org" -msgstr "earthwings@gentoo.org" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):9 -msgid "Dennis Nienhüser" -msgstr "Dennis Nienhüser" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):11 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(author:title):14 -msgid "Editor" -msgstr "редактор" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):12 -msgid "chriswhite@gentoo.org" -msgstr "chriswhite@gentoo.org" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail):12 -msgid "Chris White" -msgstr "Chris White" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(mail:link):15 -#, fuzzy -msgid "nightmorph" -msgstr "nightmorph@gentoo.org" +msgid "swift" +msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(abstract):18 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(abstract):12 msgid "" -"Power Management is the key to extend battery run time on mobile systems " -"like laptops. This guide assists you setting it up on your laptop." +"In recent years, power management has become one of the differentiating " +"features in the quest for finding the perfect laptop. Yet, the operating " +"system must support the various power saving functionalities too. In this " +"guide, we cover how to setup your Gentoo installation so it manages power-" +"hungry resources in a flexible yet automated manner." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(version):27 -msgid "4" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(version):24 +msgid "5" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(date):28 -msgid "2011-08-17" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(date):25 +msgid "2011-09-22" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):31 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):28 msgid "Introduction" msgstr "Введение" -#. Remove this note after 6 months - ETA 01/02/2012 -#. By then, we can assume that OpenRC migrations are not that frequent -#. anymore and this note can be dropped. -#. ~ Sven Vermeulen -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(impo):41 -msgid "" -"Since the introduction of OpenRC, the <c>pmg_switch_runlevel.sh</c> script " -"needs to be updated. If you have issues after the OpenRC upgrade, please " -"update this script according to this guide." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):30 +msgid "About this document..." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):47 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):33 msgid "" -"Capacity and lifetime of laptop batteries have improved much in the last " -"years. Nevertheless modern processors consume much more energy than older " -"ones and each laptop generation introduces more devices hungry for energy. " -"That's why Power Management is more important than ever. Increasing battery " -"run time doesn't necessarily mean buying another battery. Much can be " -"achieved applying intelligent Power Management policies." +"This document describes the setup of power management features on your " +"laptop. Although some of the information in this guide can be applied to " +"power management for servers, it is not the intention of this document to go " +"that route. Please be careful when applying this on a non-laptop system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):59 -msgid "A Quick Overview" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):62 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):40 msgid "" -"Please notice that this guide describes Power Management for <e>laptops</e>. " -"While some sections might also suite for <e>servers</e>, others do not and " -"may even cause harm. Please do not apply anything from this guide to a " -"server unless you really know what you are doing." +"Within this document, we will focus primarily on the laptop mode tools since " +"it offers a complete set of functionalities. However, we will also refer to " +"other tools that might offer a more detailed approach on individual " +"settings. In such cases, you will need to disable the feature from the " +"laptop mode tools so that both tools do not fight over the same resource " +"control." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):69 -msgid "" -"As this guide has become rather long, here's a short overview helping you to " -"find your way through it." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):51 +msgid "About laptop_mode" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):74 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):54 msgid "" -"The <uri link=\"#doc_chap2\">Prerequisites</uri> chapter talks about some " -"requirements that should be met before any of the following device " -"individual sections will work. This includes BIOS settings, kernel " -"configuration and some simplifications in user land. The following three " -"chapters focus on devices that typically consume most energy - processor, " -"display and hard drive. Each can be configured separately. <uri link=" -"\"#doc_chap3\">CPU Power Management</uri> shows how to adjust the " -"processor's frequency to save a maximum of energy without losing too much " -"performance. A few different tricks prevent your hard drive from working " -"unnecessarily often in <uri link=\"#doc_chap5\">Disk Power Management</uri> " -"(decreasing noise level as a nice side effect). Some notes on graphics " -"cards, Wireless LAN and USB finish the device section in <uri link=" -"\"#doc_chap6\">Power Management For Other Devices</uri> while another " -"chapter is dedicated to the (rather experimental) <uri link=" -"\"#doc_chap7\">sleep states</uri>. Last not least <uri link=" -"\"#doc_chap8\">Troubleshooting</uri> lists common pitfalls." +"The <c>laptop_mode</c> setting is an in-kernel configuration setting that " +"optimizes I/O, allowing disks to spin down properly (and not be woken up " +"immediately afterwards for queued operations)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):95 -msgid "Power Budget For Each Component" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):63 +msgid "About laptop-mode-tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:link):99 -msgid "/images/energy-budget.png" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:short):99 -msgid "Which component consumes how much energy?" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(figure:caption):99 -msgid "Power budget for each component" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):101 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):66 msgid "" -"Nearly every component can operate in different states - off, sleep, idle, " -"active to name a few - consuming a different amount of energy. Major parts " -"are consumed by the LCD display, CPU, chipset and hard drives. Often one is " -"able to activate OS-independent Power Management in the BIOS, but an " -"intelligent setup in the operating system adapting to different situations " -"can achieve much more." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):114 -msgid "Prerequisites" +"The <e>Laptop Mode Tools</e> is a software package (<c>app-laptop/laptop-" +"mode-tools</c>) which allows the user to optimize power saving functions. It " +"allows managing the <c>laptop_mode</c> setting in the Linux kernel, but has " +"additional features allowing you to tweak other power-related settings on " +"the system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):118 -msgid "" -"Before discussing the details of making individual devices Power Management " -"aware, make sure certain requirements are met. After controlling BIOS " -"settings, some kernel options want to be enabled - these are in short ACPI, " -"sleep states and CPU frequency scaling. As power saving most of the time " -"comes along with performance loss or increased latency, it should only be " -"enabled when running on batteries. That's where a new runlevel <e>battery</" -"e> comes in handy." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):79 +msgid "Linux Kernel Configuration" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):130 -msgid "The BIOS Part" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):81 +msgid "Minimum kernel setup" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):133 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):84 msgid "" -"First have a look into your BIOS Power Management settings. The best way is " -"to combine BIOS and operating system policies, but for the moment it's " -"better to disable most of the BIOS part. This makes sure it doesn't " -"interfere with your policies. Don't forget to re-check BIOS settings after " -"you configured everything else." +"There are different kernel sources in Portage. We recommend using <c>gentoo-" +"sources</c>, but if you want advanced hibernation support you might need " +"<c>tuxonice-sources</c>. To enable proper power management features in the " +"Linux kernel, enable at least the following settings:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):144 -msgid "Setting USE Flags" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):147 -msgid "" -"Please check that the <c>acpi</c> USE flag is set in <path>/etc/make.conf</" -"path>. Other USE flags that might be interesting for your system are <c>apm</" -"c>, <c>lm_sensors</c>, <c>nforce2</c>, <c>nvidia</c>, <c>pmu</c>. See <path>/" -"usr/portage/profiles/use*.desc</path> for details. If you forgot to set one " -"of these flags, you can recompile affected packages using the <c>--newuse</" -"c> flag in <c>emerge</c>, see <c>man emerge</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):159 -#, fuzzy -msgid "Configuring The Kernel" -msgstr "Конфигурация ядра" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):162 -msgid "" -"ACPI (Advanced Configuration and Power Interface) support in the kernel is " -"still work in progress. Using a recent kernel will make sure you'll get the " -"most out of it." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):168 -msgid "" -"There are different kernel sources in Portage. I'd recommend using <c>gentoo-" -"sources</c> or <c>tuxonice-sources</c>. The latter contains patches for " -"TuxOnIce, see the chapter about <uri link=\"#doc_chap7\">sleep states</uri> " -"for more details. When configuring the kernel, activate at least these " -"options:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):175 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):91 msgid "Minimum kernel setup for Power Management (Kernel 2.6)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):175 -#, no-wrap -msgid "" -"\n" -"Power management and ACPI options --->\n" -"[*] Power Management support\n" -" [ ] Software Suspend\n" -"\n" -" ACPI( Advanced Configuration and Power Interface ) Support --->\n" -" [ ] Deprecated /proc/acpi/ files\n" -" [*] AC Adapter\n" -" [*] Battery\n" -" <M> Button\n" -" <M> Video\n" -" [ ] Generic Hotkey\n" -" <M> Fan\n" -" <M> Processor\n" -" <M> Thermal Zone\n" -" < > ASUS/Medion Laptop Extras\n" -" < > IBM ThinkPad Laptop Extras\n" -" < > Toshiba Laptop Extras\n" -" (0) Disable ACPI for systems before Jan 1st this year\n" -" [ ] Debug Statements\n" -" [*] Power Management Timer Support\n" -" < > ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL)\n" -"\n" -" CPU Frequency Scaling --->\n" -" [*] CPU Frequency scaling\n" -" [ ] Enable CPUfreq debugging\n" -" < > CPU frequency translation statistics\n" -" [ ] CPU frequency translation statistics details\n" -" Default CPUFreq governor (userspace)\n" -" <*> 'performance' governor\n" -" <*> 'powersave' governor\n" -" <*> 'ondemand' cpufreq policy governor\n" -" <*> 'conservative' cpufreq governor\n" -" <*> CPU frequency table helpers\n" -" <M> ACPI Processor P-States driver\n" -" <*> <i>CPUFreq driver for your processor</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):213 -msgid "" -"Decide yourself whether you want to enable Software Suspend, and Sleep " -"States (see below). If you own an ASUS, Medion, IBM Thinkpad or Toshiba " -"laptop, enable the appropriate section." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):219 -msgid "" -"The kernel has to know how to enable CPU frequency scaling on your " -"processor. As each type of CPU has a different interface, you've got to " -"choose the right driver for your processor. Be careful here - enabling " -"<c>Intel Pentium 4 clock modulation</c> on a Pentium M system will lead to " -"strange results for example. Consult the kernel documentation if you're " -"unsure which one to take." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):227 -msgid "" -"Compile your kernel, make sure the right modules get loaded at startup and " -"boot into your new ACPI-enabled kernel. Next run <c>emerge sys-power/acpid</" -"c> to get the acpi daemon. This one informs you about events like switching " -"from AC to battery or closing the lid. Make sure the modules are loaded if " -"you didn't compile them into the kernel and start acpid by executing <c>/etc/" -"init.d/acpid start</c>. Run <c>rc-update add acpid default</c> to load it on " -"startup. You'll soon see how to use it." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):237 -msgid "Installing acpid" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):237 -#, no-wrap -msgid "" -"\n" -"# <i>emerge sys-power/acpid</i>\n" -"# <i>/etc/init.d/acpid start</i>\n" -"# <i>rc-update add acpid default</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):246 -msgid "Creating A \"battery\" Runlevel" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):249 -msgid "" -"The default policy will be to enable Power Management only when needed - " -"running on batteries. To make the switch between AC and battery convenient, " -"create a runlevel <c>battery</c> that holds all the scripts starting and " -"stopping Power Management." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):256 -msgid "" -"You can safely skip this section if you don't like the idea of having " -"another runlevel. However, skipping this step will make the rest a bit " -"trickier to set up. The next sections assume a runlevel <c>battery</c> " -"exists." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):262 -msgid "Creating a battery runlevel" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):262 -#, no-wrap -msgid "" -"\n" -"# <i>cd /etc/runlevels</i>\n" -"# <i>cp -a default battery</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):267 -msgid "" -"Finished. Your new runlevel <c>battery</c> contains everything like " -"<c>default</c>, but there is no automatic switch between both yet. Time to " -"change it." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):276 -msgid "Reacting On ACPI Events" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):279 -msgid "" -"Typical ACPI events are closing the lid, changing the power source or " -"pressing the sleep button. An important event is changing the power source, " -"which should cause a runlevel switch. A small script will take care of it." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):285 -msgid "" -"First you need a script which changes the runlevel to <c>default</c> " -"respectively <c>battery</c> depending on the power source. The script uses " -"the <c>on_ac_power</c> command from <c>sys-power/pm-utils</c> - make sure " -"the package is installed on your system." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):292 -msgid "Installing pm-utils" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):292 -#, no-wrap -msgid "" -"\n" -"# <i>emerge pm-utils</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):296 -msgid "" -"You are now able to determine the power source by executing <c>on_ac_power " -"&& echo AC available || echo Running on batteries</c> in a shell. " -"The script below is responsible for changing runlevels. Save it as <path>/" -"etc/acpi/actions/pmg_switch_runlevel.sh</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):303 -msgid "/etc/acpi/actions/pmg_switch_runlevel.sh" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):303 -#, no-wrap -msgid "" -"\n" -"#!/bin/bash\n" -"\n" -"# BEGIN configuration\n" -"RUNLEVEL_AC=\"default\"\n" -"RUNLEVEL_BATTERY=\"battery\"\n" -"\n" -"if [ -x /usr/bin/logger ]; then\n" -" LOGGER=\"/usr/bin/logger -s -p daemon.info -t /etc/acpi/actions/pmg_switch_runlevel.sh\"\n" -"else\n" -" LOGGER=\"/bin/echo\"\n" -"fi\n" -"\n" -"ON_AC_POWER=/usr/bin/on_ac_power\n" -"# END configuration\n" -"\n" -"\n" -"if [ ! -d \"/etc/runlevels/${RUNLEVEL_AC}\" ]\n" -"then\n" -" ${LOGGER} \"${0}: Runlevel ${RUNLEVEL_AC} does not exist. Aborting.\"\n" -" exit 1\n" -"fi\n" -"\n" -"if [ ! -d \"/etc/runlevels/${RUNLEVEL_BATTERY}\" ]\n" -"then\n" -" ${LOGGER} \"${0}: Runlevel ${RUNLEVEL_BATTERY} does not exist. Aborting.\"\n" -" exit 1\n" -"fi\n" -"\n" -"if ${on_ac_power}\n" -"then\n" -" if [[ \"$(rc-status --runlevel)\" != \"${RUNLEVEL_AC}\" ]]\n" -" then\n" -" ${LOGGER} \"Switching to ${RUNLEVEL_AC} runlevel\"\n" -" /sbin/rc ${RUNLEVEL_AC}\n" -" fi\n" -"elif [[ \"$(rc-status --runlevel)\" != \"${RUNLEVEL_BATTERY}\" ]]\n" -"then\n" -" ${LOGGER} \"Switching to ${RUNLEVEL_BATTERY} runlevel\"\n" -" /sbin/rc ${RUNLEVEL_BATTERY}\n" -"fi\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):346 -msgid "" -"Dont forget to run <c>chmod +x /etc/acpi/actions/pmg_switch_runlevel.sh</c> " -"to make the script executable. The last thing that needs to be done is " -"calling the script whenever the power source changes. That's done by " -"catching ACPI events with the help of <c>acpid</c>. First you need to know " -"which events are generated when the power source changes. The events are " -"called <c>ac_adapter</c> and <c>battery</c> on most laptops, but it might be " -"different on yours." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):356 -msgid "Determining ACPI events for changing the power source" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):356 -#, no-wrap -msgid "" -"\n" -"# <i>tail -f /var/log/messages | grep \"ACPI event\"</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):360 -msgid "" -"Run the command above and pull the power cable. You should see something " -"like this:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):365 -msgid "Sample output for power source changes" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):365 -#, no-wrap -msgid "" -"\n" -"[Tue Sep 20 17:39:06 2005] ACPI event \"ac_adapter AC 00000080 00000000\"\n" -"[Tue Sep 20 17:39:06 2005] ACPI event \"battery BAT0 00000080 00000001\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):370 -msgid "" -"The interesting part is the quoted string after <c>ACPI event</c>. It will " -"be matched by the event line in the files you are going to create below. " -"Don't worry if your system generates multiple events or always the same. As " -"long as any event is generated, runlevel changing will work." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):377 -msgid "/etc/acpi/events/pmg_ac_adapter" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):377 -#, no-wrap -msgid "" -"\n" -"<comment># replace \"ac_adapter\" below with the event generated on your laptop</comment>\n" -"<comment># For example, ac_adapter.* will match ac_adapter AC 00000080 00000000</comment>\n" -"event=ac_adapter.*\n" -"action=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):384 -msgid "/etc/acpi/events/pmg_battery" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):384 -#, no-wrap -msgid "" -"\n" -"<comment># replace \"battery\" below with the event generated on your laptop</comment>\n" -"<comment># For example, battery.* will match battery BAT0 00000080 00000001</comment>\n" -"event=battery.*\n" -"action=/etc/acpi/actions/pmg_switch_runlevel.sh %e\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):391 -msgid "Finally acpid has to be restarted to recognize the changes." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):395 -msgid "Finishing runlevel switching with acpid" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):395 -#, no-wrap -msgid "" -"\n" -"# <i>/etc/init.d/acpid restart</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):399 -msgid "" -"Give it a try: Plug AC in and out and watch syslog for the \"Switching to AC " -"mode\" or \"Switching to battery mode\" messages. See the <uri link=" -"\"#doc_chap8\">Troubleshooting section</uri> if the script is not able to " -"detect the power source correctly." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):406 -msgid "" -"Due to the nature of the event mechanism, your laptop will boot into " -"runlevel <c>default</c> regardless of the AC/battery state. This is fine " -"when running from AC, but we'd like to boot into the battery runlevel " -"otherwise. One solution would be to add another entry to the boot loader " -"with the parameter <c>softlevel=battery</c>, but it's likely to forget " -"choosing it. A better way is faking an ACPI event in the end of the boot " -"process and letting <path>pmg_switch_runlevel.sh</path> script decide " -"whether a runlevel change is necessary. Create a <path>/etc/local.d/battery." -"start</path> file with the following contents:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):418 -msgid "Runlevel adjustment at boot time through local.d/battery.start" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):418 -#, no-wrap -msgid "" -"\n" -"#!/bin/sh\n" -"<comment># Fake acpi event to switch runlevel if running on batteries</comment>\n" -"/etc/acpi/actions/pmg_switch_runlevel.sh \"battery/battery\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):424 -msgid "" -"Don't forget to mark the file as executable (<c>chmod +x /etc/local.d/" -"battery.start</c>). Prepared like this you can activate Power Management " -"policies for individual devices." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):435 -msgid "CPU Power Management" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):439 -msgid "" -"Mobile processors can operate at different frequencies. Some allow changing " -"voltage as well. Most of the time your CPU doesn't need to run at full speed " -"and scaling it down will save much energy - often without any performance " -"decrease." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):449 -msgid "Some Technical Terms" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):452 -msgid "" -"CPU frequency scaling brings up some technical terms that might be unknown " -"to you. Here's a quick introduction." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):457 -msgid "" -"First of all, the kernel has to be able to change the processor's frequency. " -"The <b>CPUfreq processor driver</b> knows the commands to do it on your CPU. " -"Thus it's important to choose the right one in your kernel. You should " -"already have done it above. Once the kernel knows how to change frequencies, " -"it has to know which frequency it should set. This is done according to the " -"<b>policy</b> which consists of a <b>CPUfreq policy</b> and a <b>governor</" -"b>. A CPUfreq policy are just two numbers which define a range the frequency " -"has to stay between - minimal and maximal frequency. The governor now " -"decides which of the available frequencies in between minimal and maximal " -"frequency to choose. For example, the <b>powersave governor</b> always " -"chooses the lowest frequency available, the <b>performance governor</b> the " -"highest one. The <b>userspace governor</b> makes no decision but chooses " -"whatever the user (or a program in userspace) wants - which means it reads " -"the frequency from <path>/sys/devices/system/cpu/cpu0/cpufreq/" -"scaling_setspeed</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):474 -msgid "" -"This doesn't sound like dynamic frequency changes yet and in fact it isn't. " -"Dynamics however can be accomplished with various approaches. For example, " -"the <b>ondemand governor</b> makes its decisions depending on the current " -"CPU load. The same is done by various userland tools like <c>cpudyn</c>, " -"<c>cpufreqd</c>, <c>powernowd</c> and many more. ACPI events can be used to " -"enable or disable dynamic frequency changes depending on power source." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):486 -msgid "Setting The Frequency" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):489 -msgid "" -"Decreasing CPU speed and voltage has two advantages: On the one hand less " -"energy is consumed, on the other hand there is thermal improvement as your " -"system doesn't get as hot as running on full speed. The main disadvantage is " -"obviously the loss of performance. Decreasing processor speed is a trade off " -"between performance loss and energy saving." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):497 -msgid "" -"Not every laptop supports frequency scaling. If unsure, have a look at the " -"list of supported processors in the <uri link=" -"\"#doc_chap8\">Troubleshooting</uri> section to verify yours is supported." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):503 -msgid "" -"It's time to test whether CPU frequency changing works. Let's install " -"another tool: <c>sys-power/cpufrequtils</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):508 -msgid "Checking CPU frequency" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):508 -#, no-wrap -msgid "" -"\n" -"# <i>emerge cpufrequtils</i>\n" -"# <i>cpufreq-info</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):513 -msgid "Here is an example output:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):517 -msgid "Sample output from cpufreq-info" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):517 -#, no-wrap -msgid "" -"\n" -"cpufrequtils 0.3: cpufreq-info (C) Dominik Brodowski 2004\n" -"Report errors and bugs to linux@brodo.de, please.\n" -"analyzing CPU 0:\n" -" driver: centrino\n" -" CPUs which need to switch frequency at the same time: 0\n" -" hardware limits: 600 MHz - 1.40 GHz\n" -" available frequency steps: 600 MHz, 800 MHz, 1000 MHz, 1.20 GHz, 1.40 GHz\n" -" available cpufreq governors: conservative, ondemand, powersave, userspace, performance\n" -" current policy: frequency should be within 924 MHz and 1.40 GHz.\n" -" The governor \"performance\" may decide which speed to use\n" -" within this range.\n" -" current CPU frequency is 1.40 GHz.\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):532 -msgid "" -"Now play around with <c>cpufreq-set</c> to make sure frequency switching " -"works. Run <c>cpufreq-set -g ondemand</c> for example to activate the " -"ondemand governor and verify the change with <c>cpufreq-info</c>. If it " -"doesn't work as expected, you might find help in the <uri link=" -"\"#doc_chap8\">Troubleshooting section</uri> in the end of this guide." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):540 -msgid "" -"<c>cpufrequtils</c> can operate in an automatic mode (when you use the " -"<b>ondemand</b> governor), you can also switch to the <b>userspace</b> " -"governor if you want to manually set a specific speed. You can also " -"statically set your CPU to its highest or lowest frequency by using the " -"<b>performance</b> and <b>powersave</b> governors, respectively." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):548 -msgid "Changing CPU speeds" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):548 -#, no-wrap -msgid "" -"\n" -"<comment>(Set the highest available frequency)</comment>\n" -"# <i>cpufreq-set -g performance</i>\n" -"<comment>(Set the lowest available frequency)</comment>\n" -"# <i>cpufreq-set -g powersave</i>\n" -"<comment>(Set a specific frequency)</comment>\n" -"# <i>cpufreq-set -g userspace</i>\n" -"# <i>cpufreq-set -f 2.00ghz</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):561 -msgid "Other CPU Speed Utilities" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):564 -msgid "" -"While <c>cpufrequtils</c> may be the best all-around program, there are some " -"other choices available in Portage. The following table gives a quick " -"overview of available CPU speed utilities. It's roughly separated in three " -"categories <b>kernel</b> for approaches that only need kernel support, " -"<b>daemon</b> for programs that run in the background and <b>graphical</b> " -"for programs that provide a GUI for easy configuration and changes." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):575 -msgid "Name" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):576 -msgid "Category" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):577 -msgid "Switch decision" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):578 -msgid "Kernel governors" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):579 -msgid "Further governors" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):580 -msgid "Comments" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):583 -msgid "'ondemand' governor" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):584 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):598 -msgid "Kernel" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):585 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):599 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):614 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):640 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):664 -msgid "CPU load" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):586 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):587 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):600 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):601 -msgid "N.A." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):588 -msgid "" -"Chooses maximal frequency on CPU load and slowly steps down when the CPU is " -"idle. Further tuning through files in <path>/sys/devices/system/cpu/cpu0/" -"cpufreq/ondemand/</path>. Still requires userland tools (programs, scripts) " -"if governor switching or similar is desired." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):597 -msgid "'conservative' governor" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):602 -msgid "" -"Unlike the ondemand governor, conversative doesn't jump to maximum frequency " -"when CPU load is high, but increases the frequency step by step. Further " -"tuning through files in <path>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/" -"</path>. Still requires userland tools (programs, scripts) if governor " -"switching or similar is desired." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):612 -msgid "http://mnm.uib.es/~gallir/cpudyn/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):612 -msgid "cpudyn" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):613 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):624 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):639 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):652 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):663 -msgid "Daemon" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):615 -msgid "Performance, powersave" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):616 -msgid "Dynamic" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):617 -msgid "" -"Also supports disk standby - notice however that <e>laptop mode</e> in most " -"cases will do a better job." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):623 -msgid "http://sourceforge.net/projects/cpufreqd/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):623 -msgid "cpufreqd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):625 -msgid "Battery state, CPU load, temperature, running programs and more" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):626 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):688 -msgid "All available" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):627 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):641 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):654 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):665 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):676 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):677 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):678 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):689 -msgid "None" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):628 -msgid "" -"Sophisticated (but somewhat complicated) setup. Extendible through plugins " -"like sensor monitoring (lm_sensors) or coordinating some NVidia based " -"graphics card memory and core. Cpufreqd is SMP aware and can optionally be " -"controlled manually at runtime." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):637 -msgid "http://www.deater.net/john/powernowd.html" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):637 -msgid "powernowd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):642 -msgid "Passive, sine, aggressive" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):643 -msgid "Supports SMP." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):650 -msgid "http://projects.simpledesigns.com.pl/project/ncpufreqd/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):650 -msgid "ncpufreqd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):653 -msgid "Temperature" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):655 -msgid "Powersave, performance" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):656 -msgid "" -"Toggles the used governor between performance and powersave depending on " -"system temperature. Very useful on laptops with notorious heat problems." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):662 -msgid "http://www.goop.org/~jeremy/speedfreq/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):662 -msgid "speedfreq" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):666 -msgid "Dynamic, powersave, performance, fixed speed" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):667 -msgid "" -"Easy to configure with a nice client/server interface. Requires a 2.6 " -"kernel. Unmaintained, broken and thus removed from Portage. Please switch to " -"cpufreqd if you're still using it." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri:link):674 -msgid "http://cpuspeedy.sourceforge.net/" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(uri):674 -msgid "gtk-cpuspeedy" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):675 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):686 -msgid "Graphical" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):679 -msgid "" -"Gnome application, a graphical tool to set CPU frequency manually. It does " -"not offer any automation." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):685 -msgid "klaptopdaemon" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):687 -msgid "Battery state" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):690 -msgid "KDE only, 'ondemand' governor required for dynamic frequency scaling." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):696 -msgid "" -"While adjusting the frequency to the current load looks simple at a first " -"glance, it's not such a trivial task. A bad algorithm can cause switching " -"between two frequencies all the time or wasting energy when setting " -"frequency to an unnecessary high level." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):703 -msgid "Which one to choose? If you have no idea about it, try <c>cpufreqd</c>:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):707 -msgid "Installing cpufreqd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):707 -#, no-wrap -msgid "" -"\n" -"# <i>emerge cpufreqd</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):711 -msgid "" -"<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</" -"path>. The default one that ships with cpufreqd may look a bit confusing. I " -"recommend replacing it with the one from former Gentoo developer Henrik Brix " -"Andersen (see below). Please notice that you need cpufreqd-2.0.0 or later. " -"Earlier versions have a different syntax for the config file." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):719 -msgid "/etc/cpufreqd.conf (cpufreqd-2.0.0 and later)" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):719 -#, no-wrap -msgid "" -"\n" -"[General]\n" -"pidfile=/var/run/cpufreqd.pid\n" -"poll_interval=3\n" -"enable_plugins=acpi_ac, acpi_battery\n" -"enable_remote=1\n" -"remote_group=wheel\n" -"verbosity=5\n" -"[/General]\n" -"\n" -"[Profile]\n" -"name=ondemand\n" -"minfreq=0%\n" -"maxfreq=100%\n" -"policy=ondemand\n" -"[/Profile]\n" -"\n" -"[Profile]\n" -"name=conservative\n" -"minfreq=0%\n" -"maxfreq=100%\n" -"policy=conservative\n" -"[/Profile]\n" -"\n" -"[Profile]\n" -"name=powersave\n" -"minfreq=0%\n" -"maxfreq=100%\n" -"policy=powersave\n" -"[/Profile]\n" -"\n" -"[Profile]\n" -"name=performance\n" -"minfreq=0%\n" -"maxfreq=100%\n" -"policy=performance\n" -"[/Profile]\n" -"\n" -"[Rule]\n" -"name=battery\n" -"ac=off\n" -"profile=conservative\n" -"[/Rule]\n" -"\n" -"[Rule]\n" -"name=battery_low\n" -"ac=off\n" -"battery_interval=0-10\n" -"profile=powersave\n" -"[/Rule]\n" -"\n" -"[Rule]\n" -"name=ac\n" -"ac=on\n" -"profile=ondemand\n" -"[/Rule]\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):777 -msgid "" -"Now you can start the cpufreqd daemon. Add it to the <c>default</c> and " -"<c>battery</c> runlevel as well." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):782 -msgid "Starting cpufreqd" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):782 -#, no-wrap -msgid "" -"\n" -"# <i>rc-update add cpufreqd default battery</i>\n" -"# <i>/etc/init.d/cpufreqd start</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):787 -msgid "" -"Sometimes it can be desirable to select another policy than the daemon " -"chooses, for example when battery power is low, but you know that AC will be " -"available soon. In that case you can turn on cpufreqd's manual mode with " -"<c>cpufreqd-set manual</c> and select one of your configured policies (as " -"listed by <c>cpufreqd-get</c>). You can leave manual mode by executing " -"<c>cpufreqd-set dynamic</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):796 -msgid "" -"Do not run more than one of the above programs at the same time. It may " -"cause confusion like switching between two frequencies all the time." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):804 -msgid "Verifying the result" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):807 -msgid "" -"The last thing to check is that your new policies do a good job. An easy way " -"to do so is monitoring CPU speed while working with your laptop:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):812 -msgid "Monitoring CPU speed" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):812 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):118 msgid "" -"\n" -"# <i>watch grep \\\"cpu MHz\\\" /proc/cpuinfo</i>\n" +"Don't forget to enable the CPU frequency scaling driver for your CPU, " +"located right after the <e>ACPI Processor P-States driver</e> mentioned " +"above." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):816 -msgid "" -"If <path>/proc/cpuinfo</path> doesn't get updated (see <uri link=" -"\"#doc_chap8\">Troubleshooting</uri>), monitor the CPU frequency with <c>sys-" -"apps/x86info</c>:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):123 +msgid "Build and install the new kernel (if necessary) and reboot." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):822 -msgid "Alternative CPU speed monitoring" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):169 +msgid "Using Laptop Mode Tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):822 -#, no-wrap -msgid "" -"\n" -"# <i>watch x86info -mhz</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):171 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):469 +msgid "Installation" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):826 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):174 msgid "" -"Depending on your setup, CPU speed should increase on heavy load, decrease " -"on no activity or just stay at the same level. When using <c>cpufreqd</c> " -"and verbosity set to 5 or higher in <path>cpufreqd.conf</path> you'll get " -"additional information about what's happening reported to <c>syslog</c>." +"It comes to no surprise that installation of the <e>Laptop Mode Tools</e> " +"software is easily done through <c>emerge laptop-mode-tools</c>. However, " +"this package takes on additional, optional settings through USE flag " +"configuration. So let's first take a look at the supported USE flags and " +"what they mean to the package." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):838 -msgid "LCD Power Management" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):184 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):481 +msgid "USE flag" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):842 -msgid "" -"As you can see in <uri link=\"#doc_chap1_fig1\">figure 1.1</uri>, the LCD " -"display consumes the biggest part of energy (might not be the case for non-" -"mobile CPU's). Thus it's quite important not only to shut the display off " -"when not needed, but also to reduce it's backlight if possible. Most laptops " -"offer the possibility to control the backlight dimming." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):185 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):482 +msgid "Description" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):853 -msgid "Standby settings" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):186 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(th):483 +msgid "Suggested when..." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):856 -msgid "" -"The first thing to check is the standby/suspend/off timings of the display. " -"As this depends heavily on your windowmanager, I'll let you figure it out " -"yourself. Just two common places: Blanking the terminal can be done with " -"<c>setterm -blank <number-of-minutesM></c>, <c>setterm -powersave on</" -"c> and <c>setterm -powerdown <number-of-minutesM></c>. For X.org, " -"modify <path>/etc/X11/xorg.conf</path> similar to this:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):865 -msgid "LCD suspend settings in X.org" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):189 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):486 +msgid "acpi" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):865 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):190 msgid "" -"\n" -"Section \"ServerFlags\"\n" -" Option \"blank time\" \"5\" <comment># Blank the screen after 5 minutes (Fake)</comment>\n" -" Option \"standby time\" \"10\" <comment># Turn off screen after 10 minutes (DPMS)</comment>\n" -" Option \"suspend time\" \"20\" <comment># Full suspend after 20 minutes</comment>\n" -" Option \"off time\" \"30\" <comment># Turn off after half an hour</comment>\n" -" [...]\n" -"EndSection\n" -"\n" -"[...]\n" -"\n" -"Section \"Monitor\"\n" -" Identifier [...]\n" -" Option \"DPMS\"\n" -" [...]\n" -"EndSection\n" +"Depend on <c>sys-power/acpid</c> so that changes in the system are captured " +"and power saving features are automatically enabled/disabled." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):886 -msgid "Backlight dimming" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):194 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):491 +msgid "your laptop is not too old (~ year 2003 and later)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):889 -msgid "" -"Probably more important is the backlight dimming. If you have access to the " -"dimming settings via a tool, write a small script that dims the backlight in " -"battery mode and place it in your <c>battery</c> runlevel. The following " -"script should work on most IBM Thinkpads and Toshiba laptops. You've got to " -"enable the appropriate option in your kernel (IBM Thinkpads only). For " -"Toshiba laptops, install <c>sys-power/acpitool</c> and skip configuration of " -"<c>thinkpad_acpi</c> (formerly called <c>ibm_acpi</c>) as described below." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):197 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):494 +msgid "apm" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):899 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):198 msgid "" -"Support for setting brightness is marked experimental in thinkpad_acpi. It " -"accesses hardware directly and may cause severe harm to your system. Please " -"read the <uri link=\"http://ibm-acpi.sourceforge.net/\">thinkpad_acpi " -"website</uri>" +"Depend on <c>sys-apps/apmd</c> so that changes in the system are captured " +"and power saving features are automatically enabled/disabled." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):906 -msgid "" -"To be able to set the brightness level, the thinkpad_acpi module has to be " -"loaded with the experimental parameter." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):202 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):499 +msgid "your laptop is very old" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):911 -msgid "Automatically loading the thinkpad_acpi module" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):205 +msgid "bluetooth" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):911 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):206 msgid "" -"\n" -"<comment>(Please read the warnings above before doing this!)</comment>\n" -"\n" -"# <i>echo \"options thinkpad_acpi experimental=1\" >> /etc/modprobe.d/thinkpad_acpi</i>\n" -"# <i>update-modules</i>\n" -"# <i>nano /etc/conf.d/modules</i>\n" -"<comment># Autoload the thinkpad_acpi module</comment>\n" -"modules_2_6=\"thinkpad_acpi\"\n" -"<comment># Parameters for the thinkpad_acpi module</comment>\n" -"modules_thinkpad_acpi_args_2_6=\"experimental=1\"\n" -"\n" -"# <i>modprobe thinkpad_acpi</i>\n" +"Depend on <c>net-wireless/bluez</c>, enabling the <c>laptop-mode-tools</c> " +"to manage bluetooth settings (enabling/disabling the service based on " +"battery availability)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):925 -msgid "" -"This should work without error messages and a file <path>/proc/acpi/ibm/" -"brightness</path> should be created after loading the module. An init script " -"will take care of choosing the brightness according to the power source." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):211 +msgid "your laptop (and kernel) supports bluetooth" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):932 -msgid "/etc/conf.d/lcd-brightness" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):214 +msgid "scsi" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):932 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):215 msgid "" -"\n" -"<comment># See /proc/acpi/ibm/brightness for available values</comment>\n" -"<comment># Please read /usr/src/linux/Documentation/thinkpad-acpi.txt</comment>\n" -"\n" -"<comment># brightness level in ac mode. Default is 7.</comment>\n" -"BRIGHTNESS_AC=7\n" -"\n" -"<comment># brightness level in battery mode. Default is 4.</comment>\n" -"BRIGHTNESS_BATTERY=4\n" +"Depend on <c>sys-apps/sdparm</c>, enabling the <c>laptop-mode-tools</c> to " +"manage SCSI (<e>and not</e> SATA) disk parameters." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):943 -msgid "/etc/init.d/lcd-brightness" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):219 +msgid "your laptop uses SCSI disks" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):943 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):223 msgid "" -"\n" -"#!/sbin/runscript\n" -"\n" -"set_brightness() {\n" -" if on_ac_power\n" -" then\n" -" LEVEL=${BRIGHTNESS_AC:-7}\n" -" else\n" -" LEVEL=${BRIGHTNESS_BATTERY:-4}\n" -" fi\n" -"\n" -" if [ -f /proc/acpi/ibm/brightness ]\n" -" then\n" -" ebegin \"Setting LCD brightness\"\n" -" echo \"level ${LEVEL}\" > /proc/acpi/ibm/brightness\n" -" eend $?\n" -" elif [[ -e /usr/bin/acpitool && -n $(acpitool -T | grep \"LCD brightness\") ]]\n" -" then\n" -" ebegin \"Setting LCD brightness\"\n" -" acpitool -l $LEVEL >/dev/null || ewarn \"Unable to set lcd brightness\"\n" -" eend $?\n" -" else\n" -" ewarn \"Setting LCD brightness is not supported.\"\n" -" ewarn \"For IBM Thinkpads, check that thinkpad_acpi is loaded into the kernel\"\n" -" ewarn \"For Toshiba laptops, you've got to install sys-power/acpitool\"\n" -" fi\n" -"}\n" -"\n" -"start() {\n" -" set_brightness\n" -"}\n" -"\n" -"stop () {\n" -" set_brightness\n" -"}\n" +"As you can see, there are two USE flags that seem to collide: <c>acpi</c> " +"and <c>apm</c>. So what's the deal there?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):980 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):229 msgid "" -"When done, make sure brightness is adjusted automatically by adding it to " -"the battery runlevel." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):985 -msgid "Enabling automatic brightness adjustment" +"The <c>apm</c> USE flag enables support for <e>Advanced Power Management</" +"e>, an older (before year 2000) standard for power management features " +"within a system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):985 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):234 msgid "" -"\n" -"# <i>chmod +x /etc/init.d/lcd-brightness</i>\n" -"# <i>rc-update add lcd-brightness battery</i>\n" -"# <i>rc</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):996 -msgid "Disk Power Management" +"The <c>acpi</c> USE flag enables support for <e>Advanced Configuration and " +"Power Interface</e>, the successor of APM. All modern laptops support ACPI." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1000 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):240 msgid "" -"Hard disks consume less energy in sleep mode. Therefore it makes sense to " -"activate power saving features whenever the hard disk is not used for a " -"certain amount of time. I'll show you two alternative possibilities to do " -"it. First, laptop-mode will save most energy due to several measures which " -"prevent or at least delay write accesses. The drawback is that due to the " -"delayed write accesses a power outage or kernel crash will be more dangerous " -"for data loss. If you don't like this, you have to make sure that there are " -"no processes which write to your hard disk frequently. Afterwards you can " -"enable power saving features of your hard disk with <c>hdparm</c> as the " -"second alternative." +"Depending on your system, you will either need <c>acpi</c> or <c>apm</c> " +"set. In the remainder of this guide, we assume that your laptop is recent " +"enough to use ACPI." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1015 -msgid "Increasing idle time - laptop-mode" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):246 +msgid "So, with the USE flags set, let's install <c>laptop-mode-tools</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1018 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):250 msgid "" -"Recent 2.6 kernels include the so-called <c>laptop-mode</c>. When activated, " -"dirty buffers are written to disk on read calls or after 10 minutes (instead " -"of 30 seconds). This minimizes the time the hard disk needs to be spun up." +"If you have USE=\"acpi\" set, the installation will pull in <c>acpid</c>. " +"However, the current stable ACPI daemon (2.0.9) does not support the new " +"ACPI interfaces within the Linux kernel (using the netlink interface). As " +"such, we recommend unmasking <c>sys-power/acpid-2.0.12</c> (or higher). For " +"more information about unmasking packages, please read <uri link=\"/doc/en/" +"handbook/handbook-amd64.xml?part=3&chap=3\">Mixing Software Branches</" +"uri> in the Gentoo Handbook." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1024 -msgid "Automated start of laptop-mode" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):260 +msgid "Installing laptop-mode-tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1024 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):260 #, no-wrap msgid "" "\n" "# <i>emerge laptop-mode-tools</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1028 -msgid "" -"<c>laptop-mode-tools</c> has its configuration file in <path>/etc/laptop-" -"mode/laptop-mode.conf</path>. Adjust it the way you like it, it's well " -"commented. Run <c>rc-update add laptop_mode battery</c> to start it " -"automatically." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):267 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):564 +msgid "Configuration" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1035 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):270 msgid "" -"Recent versions (1.11 and later) of laptop-mode-tools include a new tool " -"<c>lm-profiler</c>. It will monitor your system's disk usage and running " -"network services and suggests to disable unneeded ones. You can either " -"disable them through laptop-mode-tools builtin runlevel support (which will " -"be reverted by Gentoo's <c>/sbin/rc</c>) or use your <c>default</c>/" -"<c>battery</c> runlevels (recommended)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1044 -msgid "Sample output from running lm-profiler" +"Having <c>laptop-mode-tools</c> installed on your system does not " +"automatically enable the power management features that you might need. To " +"configure the package, first take a look at <path>/etc/laptop-mode/laptop-" +"mode.conf</path>. This is the main configuration file for the package and is " +"pretty well described (through comments)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1044 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):278 msgid "" -"\n" -"# <i>lm-profiler</i>\n" -"Profiling session started.\n" -"Time remaining: 600 seconds\n" -"[4296896.602000] amarokapp\n" -"Time remaining: 599 seconds\n" -"[4296897.714000] sort\n" -"[4296897.970000] mv\n" -"Time remaining: 598 seconds\n" -"Time remaining: 597 seconds\n" -"[4296900.482000] reiserfs/0\n" +"But it is not the only configuration file to work with. The Laptop Mode " +"Tools package supports plugins (or modules) which have their own " +"configuration file(s). These files are located in <path>/etc/laptop-mode/" +"conf.d</path> and are named after the module they represent (such as " +"<path>intel-sata-powermgmt.conf</path>)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1057 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):286 msgid "" -"After profiling your system for ten minutes, lm-profiler will present a list " -"of services which might have caused disk accesses during that time." +"Now, one of the important settings in each configuration file is if the " +"Laptop Mode Tools package should govern a particular setting or not. This is " +"important when you want to combine <c>laptop-mode-tools</c> with other " +"services like <c>cpufreqd</c>. In this example case, you will need to set " +"<c>CONTROL_CPU_FREQUENCY=0</c>:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1062 -msgid "lm-profiler suggests to disable some services" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):294 +msgid "Editing /etc/laptop-mode/conf.d/cpufreq.conf" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1062 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):294 #, no-wrap msgid "" "\n" -"Program: \"atd\"\n" -"Reason: standard recommendation (program may not be running)\n" -"Init script: /etc/init.d/atd (GUESSED)\n" -"\n" -"Do you want to disable this service in battery mode? [y/N]: <i>n</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1070 -msgid "" -"To disable atd as suggested in the example above, you would run <c>rc-update " -"del atd battery</c>. Be careful not to disable services that are needed for " -"your system to run properly - <c>lm-profiler</c> is likely to generate some " -"false positives. Do not disable a service if you are unsure whether it's " -"needed." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1081 -msgid "Limiting Write Accesses" +"# <i>nano -w /etc/laptop-mode/conf.d/cpufreq.conf</i>\n" +"CONTROL_CPU_FREQUENCY=<i>0</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1084 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):299 msgid "" -"If you don't want to use laptop-mode, you must take special care to disable " -"services that write to your disk frequently - <c>syslogd</c> is a good " -"candidate, for example. You probably don't want to shut it down completely, " -"but it's possible to modify the config file so that \"unnecessary\" things " -"don't get logged and thus don't create disk traffic. <c>Cups</c> writes to " -"disk periodically, so consider shutting it down and only enable it manually " -"when needed." +"The next few sections will help you configure <c>laptop-mode-tools</c> to " +"suit your needs. When you are finished, start the <c>laptop_mode</c> service " +"and make sure it is started when you boot up your system." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1094 -msgid "Disabling cups in battery mode" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):305 +msgid "Starting the laptop_mode service" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1094 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):305 #, no-wrap msgid "" "\n" -"# <i>rc-update del cupsd battery</i>\n" +"# <i>/etc/init.d/laptop_mode start</i>\n" +"# <i>rc-update add laptop_mode default</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1098 -msgid "" -"You can also use <c>lm-profiler</c> from laptop-mode-tools (see above) to " -"find services to disable. Once you eliminated all of them, go on with " -"configuring hdparm." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1107 -msgid "hdparm" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):313 +msgid "How does laptop-mode-tools work" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1110 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):316 msgid "" -"The second possibility is using <c>hdparm</c>. Skip this if you are using " -"laptop-mode. Otherwise, edit <path>/etc/conf.d/hdparm</path> and add the " -"following values to your drive entries. This example assumes your hard drive " -"is called <b>hda</b>:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1117 -msgid "Using /etc/conf.d/hdparm for disk standby" +"When running the <c>laptop_mode</c> service, the software will check in " +"which state your system is in. The states are defined as:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1117 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):322 msgid "" -"\n" -"hda_args=\"-q -S12\"\n" +"<e>Battery</e>, in the configuration files using the <c>BATT_</c> prefix, is " +"active when the system is running on battery power" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1121 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):326 msgid "" -"This will activate power management for your hard drive. If you ever want to " -"deactivate power management, you can edit <path>/etc/conf.d/hdparm</path> " -"and change the values to <c>-q -S0</c>, or just run <c>hdparm -q -S0 /dev/" -"hda</c>." +"<e>AC</e>, in the configuration files using the <c>AC_</c> prefix, is active " +"when the system is running on AC power" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1127 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):330 msgid "" -"See <c>man hdparm</c> for the options. Though you can always start " -"<c>hdparm</c> manually when you are on battery power by running <c>/etc/init." -"d/hdparm start</c>, it's much easier to automate its startup and shutdown. " -"To do so, add <c>hdparm</c> to the battery runlevel so that it will " -"automatically enable power management." +"<e>Laptop Mode</e>, in the configuration files using the <c>LM_</c> prefix, " +"is active when <e>laptop mode</e> is enabled" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1135 -msgid "Automate disk standby settings" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1135 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):334 msgid "" -"\n" -"# <i>rc-update add hdparm battery</i>\n" +"<e>No Laptop Mode</e>, in the configuration files using the <c>NOLM_</c> " +"prefix, is active when <e>laptop mode</e> is disabled" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(impo):1139 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):340 msgid "" -"Be careful with sleep/spin down settings of your hard drive. Setting it to " -"small values might wear out your drive and lose warranty." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1147 -msgid "Other tricks" +"The <c>AC/BATT_</c> and <c>LM/NOLM_</c> prefixes can be combined (so you can " +"have a <c>AC_LM_</c> prefix)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1150 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):345 msgid "" -"Another possibility is to deactivate swap in battery mode. Before writing a " -"swapon/swapoff switcher, make sure there is enough RAM and swap isn't used " -"heavily, otherwise you'll be in big problems." +"When the <c>laptop_mode</c> service is started, it will switch modes based " +"on events that occur (and of course based on the configuration settings). " +"For instance, the setting <c>ENABLE_LAPTOP_MODE_ON_BATTERY=1</c> will make " +"sure that the laptop mode tools switch to <e>laptop mode</e> when battery " +"power is used. If that is the case, then the settings starting with <c>LM_</" +"c>, <c>LM_BATT_</c>, <c>BATT_LM_</c> and <c>BATT_</c> will be used." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1156 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):354 msgid "" -"If you don't want to use laptop-mode, it's still possible to minimize disk " -"access by mounting certain directories as <c>tmpfs</c> - write accesses are " -"not stored on a disk, but in main memory and get lost with unmounting. Often " -"it's useful to mount <path>/tmp</path> like this - you don't have to pay " -"special attention as it gets cleared on every reboot regardless whether it " -"was mounted on disk or in RAM. Just make sure you have enough RAM and no " -"program (like a download client or compress utility) needs extraordinary " -"much space in <path>/tmp</path>. To activate this, enable tmpfs support in " -"your kernel and add a line to <path>/etc/fstab</path> like this:" +"To make sure settings to not collide, it is not allowed to have overlapping " +"settigns. In the next example, the first set (for <c>CPU_MAXFREQ</c>) is " +"valid, but the second one (for <c>CPU_GOVERNOR</c>) isn't." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1168 -msgid "Editing /etc/fstab to make /tmp even more volatile" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):360 +msgid "Colliding settings" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1168 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):360 #, no-wrap msgid "" "\n" -"none /tmp tmpfs size=32m 0 0\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1172 -msgid "" -"Pay attention to the size parameter and modify it for your system. If you're " -"unsure, don't try this at all, it can become a performance bottleneck " -"easily. In case you want to mount <path>/var/log</path> like this, make sure " -"to merge the log files to disk before unmounting. They are essential. Don't " -"attempt to mount <path>/var/tmp</path> like this. Portage uses it for " -"compiling..." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1185 -msgid "Power Management For Other Devices" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1187 -msgid "Graphics Cards" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1190 -msgid "" -"In case you own an ATI graphics card supporting PowerPlay (dynamic clock " -"scaling for the graphics processing unit GPU), you can activate this feature " -"in X.org. Open <path>/etc/X11/xorg.conf</path> and add (or enable) the " -"<c>DynamicClocks</c> option in the Device section. Please notice that this " -"feature will lead to crashes on some systems." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1198 -msgid "Enabling ATI PowerPlay support in X.org" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1198 -#, no-wrap -msgid "" +"<comment>## Valid set</comment>\n" +"BATT_CPU_MAXFREQ=fastest\n" +"LM_AC_CPU_MAXFREQ=fastest\n" +"NOLM_AC_CPU_MAXFREQ=fastest\n" "\n" -"Section \"Device\"\n" -"[...]\n" -"Option \"DynamicClocks\" \"on\"\n" -"EndSection\n" +"<comment>## Invalid set</comment>\n" +"BATT_CPU_MINFREQ=fastest\n" +"LM_AC_CPU_MINFREQ=fastest\n" +"<comment># The following includes AC and BATT, but BATT is already defined</comment>\n" +"NOLM_CPU_MINFREQ=fastest\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1208 -msgid "Wireless Power Management" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):376 +msgid "Configuring CPU frequency management" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1211 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):379 msgid "" -"Wireless LAN cards consume quite a bit of energy. Put them in Power " -"Management mode just like your hard drives." +"The support for CPU frequency management in the laptop mode tools allows " +"switching frequencies. It supports setting the CPU frequency governor, " +"minimum frequency and maximum frequency. The configuration file used here is " +"<path>/etc/laptop-mode/conf.d/cpufreq.conf</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1216 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):386 msgid "" -"This script assumes your wireless interface is called <c>wlan0</c>; replace " -"this with the actual name of your interface." +"The <e>CPU frequency governor</e> is a kernel-level policy that defines how " +"the kernel will select the CPU frequency. We already selected the governors " +"we want to use in the kernel configuration earlier. Let's recap:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1221 -msgid "" -"Add the following option to <path>/etc/conf.d/net</path> to automatically " -"enable power management for your wireless card:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):393 +msgid "<c>performance</c> always picks the highest frequency" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1226 -msgid "Automated WLAN Power Management" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):396 +msgid "<c>powersave</c> always picks the lowest frequency" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1226 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):399 msgid "" -"\n" -"iwconfig_wlan0=\"power on\"\n" +"<c>userspace</c> does not pick anything, but let the user decide (or any " +"process that the user is running that will decide for the user)" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1230 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):403 msgid "" -"See <c>man iwconfig</c> for details and more options like the period between " -"wakeups or timeout settings. If your driver and access point support " -"changing the beacon time, this is a good starting point to save even more " -"energy." +"<c>ondemand</c> will scale the CPU frequency up to the highest frequency " +"when load is available" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1239 -msgid "USB Power Management" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1242 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):407 msgid "" -"There are two problems with USB devices regarding energy consumption: First, " -"devices like USB mice, digital cameras or USB sticks consume energy while " -"plugged in. You cannot avoid this (nevertheless remove them in case they're " -"not needed). Second, when there are USB devices plugged in, the USB host " -"controller periodically accesses the bus which in turn prevents the CPU from " -"going into sleep mode. The kernel offers an experimental option to enable " -"suspension of USB devices through driver calls or one of the <path>power/" -"state</path> files in <path>/sys</path>." +"<c>conservative</c> will scale the CPU frequency up gradually when load is " +"available" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1253 -msgid "Enabling USB suspend support in the kernel" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1253 -#, no-wrap -msgid "" -"\n" -"Device Drivers\n" -" USB support\n" -" [*] Support for Host-side USB\n" -" [*] USB suspend/resume (EXPERIMENTAL)\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1265 -msgid "Sleep States: sleep, standby, and suspend to disk" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1269 -msgid "ACPI defines different sleep states. The more important ones are" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1274 -msgid "S1 aka Standby" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1275 -msgid "S3 aka Suspend to RAM aka Sleep" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):1276 -msgid "S4 aka Suspend to Disk aka Hibernate" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1279 -msgid "" -"They can be called whenever the system is not in use, but a shutdown is not " -"wanted due to the long boot time." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1287 -msgid "Sleep (S3)" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1290 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):413 msgid "" -"The ACPI support for these sleep states is marked experimental for good " -"reason. APM sleep states seem to be more stable, however you can't use APM " -"and ACPI together." +"When switching between AC or battery, or (no) laptop mode, the appropriate " +"governor (as well as its minimum and maximum frequency) is selected." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1296 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1390 -msgid "Kernel configuration for the various suspend types" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1296 -#, no-wrap -msgid "" -"\n" -" Power Management Options --->\n" -" [*] Power Management support\n" -" [*] Suspend to RAM and standby \n" -msgstr "" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):421 +#, fuzzy +msgid "Configuring display brightness" +msgstr "Конфигурация ядра" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1302 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):424 msgid "" -"Once your kernel is properly configured, you can use the <c>hibernate-" -"script</c> to activate suspend or sleep mode. Let's install that first." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1308 -msgid "Installing the hibernate-script" +"With <path>/etc/laptop-mode/conf.d/lcd-brightness.conf</path>, you can have " +"the laptop mode tools govern the brightness of your LCD screen." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1308 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):429 msgid "" -"\n" -"# <i>emerge hibernate-script</i>\n" +"The file currently uses the <path>/proc/acpi/video/VID/LCD/brightness</path> " +"file to set brightness values. Recent kernels do not provide this anymore - " +"you will need to adjust this to <path>/sys/class/backlight/acpi_video0/" +"brightness</path> instead." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1312 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):436 msgid "" -"Some configuration has to be done in <path>/etc/hibernate</path>. The " -"default package introduces a few configuration files for each sleep state. " -"Options that are common to all suspend methods are placed in <path>common." -"conf</path>; make sure this file is properly set up for your system." +"The values you can use are between 0 and 15, with 0 being the lowest " +"brightness value." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1319 -msgid "" -"To configure sleep, edit <path>sysfs-ram.conf</path> in <path>/etc/" -"hibernate</path>. <c>UseSysfsPowerState mem</c> is already setup correctly, " -"but if you need to make further changes to this particular sleep state (or " -"any other sleep state) you should add them to <path>/etc/hibernate/hibernate." -"conf</path>. The comments and option names will guide you. If you use nfs or " -"samba shares over the network, make sure to shutdown the appropriate init " -"scripts to avoid timeouts." -msgstr "" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):444 +#, fuzzy +msgid "Configuring other services" +msgstr "Конфигурация ядра" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(note):1329 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):447 msgid "" -"For more information on setting up sleep states, read <c>man hibernate.conf</" -"c>." +"An interesting feature of <c>laptop-mode-tools</c> is to support reloading " +"particular services (like the system logger) after switching its " +"configuration file. This is handled through <path>/etc/laptop-mode/conf.d/" +"configuration-file-control.conf</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1334 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):454 msgid "" -"Ready? Now is the last chance to backup any data you want to keep after " -"executing the next command. Notice that you probably have to hit a special " -"key like <c>Fn</c> to resume from sleep." +"If enabled, the <c>laptop_mode</c> application will switch the configuration " +"file(s) of the mentioned services with the same file, but suffixed with " +"<path>-nolm-ac</path>, <path>-lm-ac</path> or <path>-batt</path>. It willl " +"then signal or reload the appropriate services so they can use the new " +"configuration file." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1340 -msgid "Calling sleep" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1340 -#, no-wrap -msgid "" -"\n" -"# <i>hibernate-ram</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):467 +msgid "Using cpufreqd" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1344 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):472 msgid "" -"If you're still reading, it seems to work. You can also setup standby (S1) " -"in a similar way by editing <path>sysfs-ram.conf</path> and changing " -"\"UseSysfsPowerState mem\" to \"UseSysfsPowerState standby\". S3 and S4 are " -"the more interesting sleep states due to greater energy savings however." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1354 -msgid "Hibernate (S4)" +"The <c>cpufreqd</c> application allows you to manage CPU frequencies in a " +"more granular approach then what <c>laptop-mode-tools</c> supports. But " +"before we dive into the installation of <c>cpufreqd</c>, let's first look at " +"the USE flags it supports." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1357 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):487 msgid "" -"This section introduces hibernation, where a snapshot of the running system " -"is written to disk before powering off. On resume, the snapshot is loaded " -"and you can go on working at exactly the point you called hibernate before." +"Enable support for ACPI, allowing <c>cpufreqd</c> to be notified about " +"specific events as well as govern power through the ACPI interface" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1363 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):495 msgid "" -"Don't exchange non hot-pluggable hardware when suspended. Don't attempt to " -"load a snapshot with a different kernel image than the one it was created " -"with. Shutdown any NFS or samba server/client before hibernating." +"Enable support for APM, allowing <c>cpufreqd</c> to be notified about " +"specific events as well as govern power through the APM interface" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1369 -msgid "" -"There are two different implementations for S4. The original one is swsusp, " -"then there is the newer tuxonice (formerly suspend2) with a nicer interface " -"(including fbsplash support). A <uri link=\"http://tuxonice.net/features." -"html#compare\">feature comparison</uri> is available at the <uri link=" -"\"http://www.tuxonice.net\">tuxonice homepage</uri>. There used to be " -"Suspend-to-Disk (pmdisk), a fork of swsusp, but it has been merged back." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):502 +msgid "lm_sensors" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1379 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):503 msgid "" -"TuxOnIce is not included in the mainline kernel yet, therefore you either " -"have to patch your kernel sources with the patches provided by <uri link=" -"\"http://www.tuxonice.net\">tuxonice.net</uri> or use <c>sys-kernel/tuxonice-" -"sources</c>." +"Enable support for the Linux hardware sensors (through <c>sys-apps/" +"lm_sensors</c>), allowing to switch profiles based on hardware sensor results" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1386 -msgid "The kernel part for both swusp and TuxOnIce is as follows:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):508 +msgid "you want to use advanced events through lm_sensors" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1390 -#, no-wrap -msgid "" -"\n" -"Power Management support --->\n" -" <comment>(hibernate with swsusp)</comment>\n" -" [*] Hibernation (aka 'suspend to disk')\n" -" <comment>(replace /dev/SWAP with your swap partition)</comment>\n" -" (/dev/SWAP) Default resume partition\n" -"\n" -" <comment>(hibernate with TuxOnIce)</comment>\n" -" Enhanced Hibernation (TuxOnIce)\n" -" --- Image Storage (you need at least one allocator)\n" -" [*] File Allocator\n" -" [*] Swap Allocator\n" -" --- General Options\n" -" [*] Compression support\n" -" [ ] Allow Keep Image Mode\n" -" [*] Replace swsusp by default\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):513 +msgid "nforce2" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1408 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):514 msgid "" -"The configuration for swsusp is rather easy. If you didn't store the " -"location of your swap partition in the kernel config, you can also pass it " -"as a parameter with the <c>resume=/dev/SWAP</c> directive. If booting is not " -"possible due to a broken image, use the <c>noresume</c> kernel parameter. " -"The <c>hibernate-cleanup</c> init script invalidates swsusp images during " -"the boot process." +"Enable support for NForce, allowing <c>cpufreqd</c> to change the NForce FSB " +"clock and video card frequency" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1417 -msgid "Invalidating swsusp images during the boot process" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):518 +msgid "you have an NVidia graphical card based on the NForce chipset" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1417 -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1459 -#, no-wrap -msgid "" -"\n" -"# <i>rc-update add hibernate-cleanup boot</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):523 +msgid "nvidia" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1421 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):524 msgid "" -"To activate hibernate with swsusp, use the hibernate script and set " -"<c>UseSysfsPowerState disk</c> in <path>/etc/hibernate/sysfs-disk</path>." +"Enable support for NVidia graphical card configuration (through the NVidia " +"<e>nvclock</e> interface), allowing <c>cpufreqd</c> to change the video card " +"frequency of NVidia graphical cards" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(warn):1426 -msgid "" -"Backup your data before doing this. Run <c>sync</c> before executing one of " -"the commands to have cached data written to disk. First try it outside of X, " -"then with X running, but not logged in." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1432 -msgid "" -"If you experience kernel panics due to uhci or similar, try to compile USB " -"support as module and unload the modules before sending your laptop to sleep " -"mode. There are configuration options for this in <path>common.conf</path>" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):529 +msgid "you have an NVidia graphical card" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1438 -msgid "Hibernating with swsusp" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):534 +msgid "pmu" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1438 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):535 msgid "" -"\n" -"# <i>nano -w /etc/hibernate/common.conf</i>\n" -"<comment>(Make sure you have a backup of your data)</comment>\n" -"# <i>hibernate</i>\n" +"Enable the Power Management Unit plug-in of <c>cpufreqd</c>. This allows the " +"software to poll the Linux kernel Power Supply interface, getting more " +"detailed information on battery charge." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1444 -msgid "" -"The following section discusses the setup of TuxOnIce including fbsplash " -"support for a nice graphical progress bar during suspend and resume." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(ti):540 +msgid "your laptop does not support ACPI or APM" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1449 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):546 msgid "" -"The first part of the configuration is similar to the configuration of " -"swsusp. In case you didn't store the location of your swap partition in the " -"kernel config, you have to pass it as a kernel parameter with the " -"<c>resume=swap:/dev/SWAP</c> directive. If booting is not possible due to a " -"broken image, append the <c>noresume</c> parameter. Additionally, the " -"<c>hibernate-cleanup</c> init script invalidates TuxOnIce images during the " -"boot process." +"The USE flags <c>acpi</c>, <c>apm</c> and <c>pmu</c> overlap, so you should " +"only have one active. If your laptop is sufficiently recent, <c>acpi</c> is " +"your best bet. If not, <c>apm</c> offers all that is needed. When even APM " +"isn't supported, you can try <c>pmu</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1459 -msgid "Invalidating TuxOnIce images during the boot process" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):553 +msgid "With the USE flags configured, it is time to install <c>cpufreqd</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1463 -msgid "" -"Now edit <path>/etc/hibernate/tuxonice.conf</path>, enable the <c>TuxOnIce</" -"c> options you need. Do not enable the <c>fbsplash</c> options in <c>common." -"conf</c> just yet." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1469 -msgid "Hibernating with TuxOnIce" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):557 +msgid "Installing cpufreqd" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1469 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):557 #, no-wrap msgid "" "\n" -"# <i>nano -w /etc/hibernate/tuxonice.conf</i>\n" -"<comment>(Make sure you have a backup of your data)</comment>\n" -"# <i>hibernate</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1475 -msgid "" -"Please configure <c>fbsplash</c> now if you didn't do already. To enable " -"fbsplash support during hibernation, the <c>sys-apps/tuxonice-userui</c> " -"package is needed. Additionally, you've got to enable the <c>fbsplash</c> " -"USE flag." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1481 -msgid "Installing tuxonice-userui" +"# <i>emerge cpufreqd</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1481 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):567 msgid "" -"\n" -"# <i>echo \"sys-apps/tuxonice-userui fbsplash\" >> /etc/portage/package.use</i>\n" -"# <i>emerge tuxonice-userui</i>\n" +"The <c>cpufreqd</c> application monitors the status of the system through " +"several plugins. Based on the feedback it receives from those plugins, it " +"will adjust the policy used to govern the CPU frequency." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1486 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):573 msgid "" -"The ebuild tells you to make a symlink to the theme you want to use. For " -"example, to use the <c>livecd-2005.1</c> theme, run the following command:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1491 -msgid "Using the livecd-2005.1 theme during hibernation" +"<c>cpufreqd</c> can be configured by editing <path>/etc/cpufreqd.conf</" +"path>. It contains three different sections:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1491 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):579 msgid "" -"\n" -"# <i>ln -sfn /etc/splash/livecd-2005.1 /etc/splash/tuxonice</i>\n" +"The <c>[General]...[/General]</c> section contains general configuration " +"information" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1495 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):583 msgid "" -"If you don't want a black screen in the first part of the resume process, " -"you have to add the <c>tuxoniceui_fbsplash</c> tool to your initrd image. " -"Assuming you created the initrd image with <c>splash_geninitramfs</c> and " -"saved it as <path>/boot/fbsplash-emergence-1024x768</path>, here's how to do " -"that." +"The <c>[Profile]...[/Profile]</c> section defines the policies that the " +"<c>cpufreqd</c> daemon can switch to. The section is very similar to the " +"information you use when manually setting the CPU frequency policy using " +"<c>cpufreq-set</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1502 -msgid "Adding tuxoniceui_fbsplash to an initrd image" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1502 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):589 msgid "" -"\n" -"# <i>mount /boot</i>\n" -"# <i>mkdir ~/initrd.d</i>\n" -"# <i>cp /boot/fbsplash-emergence-1024x768 ~/initrd.d/</i>\n" -"# <i>cd ~/initrd.d</i>\n" -"# <i>gunzip -c fbsplash-emergence-1024x768 | cpio -idm --quiet -H newc</i>\n" -"# <i>rm fbsplash-emergence-1024x768</i>\n" -"# <i>cp /usr/sbin/tuxoniceui_fbsplash sbin/</i>\n" -"# <i>find . | cpio --quiet --dereference -o -H newc | gzip -9 > /boot/fbsplash-tuxonice-emergence-1024x768</i>\n" +"The <c>[Rule]...[/Rule]</c> section is the work-horse of the <c>cpufreqd</c> " +"daemon, defining when the daemon decides to switch to a different profile." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1513 -msgid "" -"Afterwards adjust <path>grub.conf</path> (or <path>lilo.conf</path>) so that " -"your TuxOnIce kernel uses <path>/boot/fbsplash-tuxonice-emergence-1024x768</" -"path> as initrd image. You can now test a dry run to see if everything is " -"setup correctly." +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):595 +msgid "Let's take a quick look at an example rule." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1520 -msgid "Test run for fbsplash hibernation" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):599 +msgid "Sample cpufreqd rule" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1520 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):599 #, no-wrap msgid "" "\n" -"# <i>tuxoniceui_fbsplash -t</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1524 -msgid "" -"Afterwards open <path>/etc/hibernate/common.conf</path> and activate the " -"fbsplash options. Execute <c>hibernate</c> and enjoy." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):1534 -msgid "Troubleshooting" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1538 -msgid "" -"<e>Q:</e> I'm trying to change the CPU frequency, but <path>/sys/devices/" -"system/cpu/cpu0/cpufreq/scaling_governor</path> does not exist." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1544 -msgid "" -"<e>A:</e> Make sure your processor supports CPU frequency scaling and you " -"chose the right CPUFreq driver for your processor. Here is a list of " -"processors that are supported by cpufreq (kernel 2.6.7): ARM Integrator, ARM-" -"SA1100, ARM-SA1110, AMD Elan - SC400, SC410, AMD mobile K6-2+, AMD mobile " -"K6-3+, AMD mobile Duron, AMD mobile Athlon, AMD Opteron, AMD Athlon 64, " -"Cyrix Media GXm, Intel mobile PIII and Intel mobile PIII-M on certain " -"chipsets, Intel Pentium 4, Intel Xeon, Intel Pentium M (Centrino), National " -"Semiconductors Geode GX, Transmeta Crusoe, VIA Cyrix 3 / C3, UltraSPARC-III, " -"SuperH SH-3, SH-4, several \"PowerBook\" and \"iBook2\" and various " -"processors on some ACPI 2.0-compatible systems (only if \"ACPI Processor " -"Performance States\" are available to the ACPI/BIOS interface)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1557 -msgid "" -"<e>Q:</e> My laptop supports frequency scaling, but <path>/sys/devices/" -"system/cpu/cpu0/cpufreq/</path> is empty." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1562 -msgid "" -"<e>A:</e> Look for ACPI related error messages with <c>dmesg | grep ACPI</" -"c>. Try to update the BIOS, especially if a broken DSDT is reported. You can " -"also try to fix it yourself (which is beyond the scope of this guide)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1568 -msgid "" -"<e>Q:</e> My laptop supports frequency scaling, but according to <path>/proc/" -"cpuinfo</path> the speed never changes." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1573 -msgid "" -"<e>A:</e> Probably you have activated symmetric multiprocessing support " -"(CONFIG_SMP) in your kernel. Deactivate it and it should work. Some older " -"kernels had a bug causing this. In that case, run <c>emerge x86info</c>, " -"update your kernel as asked and check the current frequency with <c>x86info -" -"mhz</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1580 -msgid "" -"<e>Q:</e> I can change the CPU frequency, but the range is not as wide as in " -"another OS." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1585 -msgid "" -"<e>A:</e> You can combine frequency scaling with ACPI throttling to get a " -"lower minimum frequency. Notice that throttling doesn't save much energy and " -"is mainly used for thermal management (keeping your laptop cool and quiet). " -"You can read the current throttling state with <c>cat /proc/acpi/processor/" -"CPU/throttling</c> and change it with <c>echo -n \"0:x\" > /proc/acpi/" -"processor/CPU/limit</c>, where x is one of the Tx states listed in <path>/" -"proc/acpi/processor/CPU/throttling</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1595 -msgid "" -"<e>Q:</e> When configuring the kernel, powersave, performance and userspace " -"governors show up, but that ondemand thing is missing. Where do I get it?" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1600 -msgid "" -"<e>A:</e> The ondemand governor is only included in recent kernel sources. " -"Try updating them." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1605 -msgid "<e>Q:</e> Battery life time seems to be worse than before." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1609 -msgid "" -"<e>A:</e> Check your BIOS settings. Maybe you forgot to re-enable some of " -"the settings." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1614 -msgid "" -"<e>Q:</e> My battery is charged, but KDE reports there would be 0% left and " -"immediately shuts down." +"[Profile]\n" +"name=On Demand High\n" +"minfreq=40%\n" +"maxfreq=100%\n" +"policy=ondemand\n" +"[/Profile]\n" +"\n" +"[Rule]\n" +"name=AC Off - High Power\n" +"ac=off\n" +"battery_interval=70-100\n" +"profile=On Demand High\n" +"[/Rule]\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1619 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):615 msgid "" -"<e>A:</e> Check that battery support is compiled into your kernel. If you " -"use it as a module, make sure the module is loaded." +"In the above example, <c>cpufreqd</c> will switch the system to the <e>On " +"Demand High</e> profile (also shown in the above excerpt). This profile by " +"itself uses the <c>ondemand</c> governor with a minimum frequency of 40% " +"(iow, a CPU of 2Ghz will have by this policy a minimum frequency of 800Mhz)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1624 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):622 msgid "" -"<e>Q:</e> My system logger reports things like \"logger: ACPI group " -"battery / action battery is not defined\"." +"As you can see, the <c>cpufreqd</c> application can offer a more granular " +"approach on CPU frequency scaling. But not only that, you can tweak the CPU " +"frequency scaling based on various other metrics available. The default " +"configuration offers a sample rule for when you watch a movie, where you " +"want maximum performance, unless the CPU temperature is getting too high." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1629 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):630 msgid "" -"<e>A:</e> This message is generated by the <path>/etc/acpi/default.sh</path> " -"script that is shipped with acpid. You can safely ignore it. If you like to " -"get rid of it, you can comment the appropriate line in <path>/etc/acpi/" -"default.sh</path> as shown below:" +"When you have configured <c>cpufreqd</c>, it is time to start it (and make " +"sure the service is loaded automatically). Make sure that CPU frequency " +"handling by other tools (like <c>laptop-mode-tools</c>) is disabled!" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1636 -msgid "Disabling warnings about unknown acpi events" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):636 +msgid "Starting cpufreqd" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1636 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):636 #, no-wrap msgid "" "\n" -" *) # logger \"ACPI action $action is not defined\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1640 -msgid "<e>Q:</e> I have a Dell Inspiron 51XX and I don't get any ACPI events." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1644 -msgid "" -"<e>A:</e> This seems to be a kernel bug. Read on <uri link=\"http://bugme." -"osdl.org/show_bug.cgi?id=1752\">here</uri>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1649 -msgid "" -"<e>Q:</e> I activated the <c>DynamicClocks</c> option in <path>xorg.conf</" -"path> and now X.org crashes / the screen stays black / my laptop doesn't " -"shutdown properly." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1655 -msgid "" -"<e>A:</e> This happens on some systems. You have to disable " -"<c>DynamicClocks</c>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1660 -msgid "" -"<e>Q:</e> I want to use TuxOnIce, but it tells me my swap partition is too " -"small. Resizing is not an option." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1665 -msgid "" -"<e>A:</e> If there is enough free space on your system, you can use the " -"filewriter instead of the swapwriter. The <c>hibernate-script</c> supports " -"it as well. More information can be found in <path>/usr/src/linux/" -"Documentation/power/tuxonice.txt</path>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1672 -msgid "" -"<e>Q:</e> I just bought a brand new battery, but it only lasts for some " -"minutes! What am I doing wrong?" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1677 -msgid "" -"<e>A:</e> First follow your manufacturer's advice on how to charge the " -"battery correctly." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1682 -msgid "<e>Q:</e> The above didn't help. What should I do then?" +"# <i>rc-service add cpufreqd default</i>\n" +"# <i>/etc/init.d/cpufreqd start</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1686 -msgid "" -"<e>A:</e> Some batteries sold as \"new\" are in fact old ones. Try the " -"following:" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):646 +msgid "Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre:caption):1690 -msgid "Querying battery state" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):648 +msgid "Tools" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(pre):1690 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):652 msgid "" -"\n" -"$ <i>grep capacity /proc/acpi/battery/BAT0/info</i>\n" -"design capacity: 47520 mWh\n" -"last full capacity: 41830 mWh\n" +"<uri link=\"http://samwel.tk/laptop_mode/\">Laptop Mode Tools Homepage</" +"uri>, includes <uri link=\"http://samwel.tk/laptop_mode/laptop_mode\">About " +"laptop mode</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1696 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):657 msgid "" -"If the \"last full capacity\" differs significantly from the design " -"capacity, your battery is probably broken. Try to claim your warranty." +"<uri link=\"http://www.lesswatts.org/projects/powertop/\">PowerTOP</uri>, an " +"interactive application helping users to find out which processes are " +"forcing wakeups on the CPU most often." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1701 -msgid "<e>Q:</e> My problem is not listed above. Where should I go next?" +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(title):667 +msgid "Articles and Guides" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(p):1705 +#: ../../gentoo/xml/htdocs/doc/en//power-management-guide.xml(li):671 msgid "" -"<e>A:</e> Don't fear to contact me, <mail link=\"earthwings@gentoo.org" -"\">Dennis Nienhüser</mail>, directly. The <uri link=\"http://forums.gentoo." -"org\">Gentoo Forums</uri> are a good place to get help as well. If you " -"prefer IRC, try the <c>#gentoo-laptop</c><uri link=\"irc://irc.gentoo.org" -"\">channel</uri>." +"A ThinkWiki article on <uri link=\"http://www.thinkwiki.org/wiki/" +"How_to_reduce_power_consumption\">How to reduce power consumption</uri> (on " +"Linux). This article offers an exhaustive list of measures one can take. " +"However, it should be noted that the laptop mode tools implements the " +"majority of these (if properly configured)." msgstr "" #. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL diff --git a/doc/gettext/ru/xfce-config.xml.po b/doc/gettext/ru/xfce-config.xml.po index 97af8ce..f022574 100644 --- a/doc/gettext/ru/xfce-config.xml.po +++ b/doc/gettext/ru/xfce-config.xml.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: 2011-03-02 17:28+0500\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-02-09 00:53+0500\n" "Last-Translator: Azamat H. Hackimov <azamat.hackimov@gmail.com>\n" "Language-Team: Russian <gentoo-doc-ru@gentoo.org>\n" @@ -36,11 +36,11 @@ msgstr "" "полноценной графической средой." #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(version):21 -msgid "5" +msgid "6" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(date):22 -msgid "2011-02-14" +msgid "2011-09-18" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):25 @@ -142,9 +142,9 @@ msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):86 #, fuzzy msgid "" -"Next, add your regular user(s) to the <c>plugdev</c>, <c>cdrom</c>, <c>cdrw</" -"c>, and <c>usb</c> groups, so that they can mount and use devices such as " -"cameras, optical drives, and USB sticks." +"Next, add your regular user(s) to the <c>cdrom</c>, <c>cdrw</c>, and <c>usb</" +"c> groups, so that they can mount and use devices such as cameras, optical " +"drives, and USB sticks." msgstr "" "Теперь добавим обычных пользователей в группы <c>plugdev</c>, <c>cdrom</c>, " "<c>cdrw</c> и <c>usb</c> для того, чтобы они имели доступ ко всем " @@ -156,11 +156,11 @@ msgid "Adding users to the hardware groups" msgstr "Добавление пользователей в группы аппаратуры" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):92 -#, no-wrap +#, fuzzy, no-wrap msgid "" "\n" "<comment>(Replace username with your actual user)</comment>\n" -"# <i>for x in plugdev cdrom cdrw usb ; do gpasswd -a username $x ; done</i>\n" +"# <i>for x in cdrom cdrw usb ; do gpasswd -a username $x ; done</i>\n" msgstr "" "\n" "<comment>(Замените \"username\" существующим пользователем)</comment>\n" diff --git a/doc/gettext/xfce-config.xml.pot b/doc/gettext/xfce-config.xml.pot index d8bd4d6..b2a9d3f 100644 --- a/doc/gettext/xfce-config.xml.pot +++ b/doc/gettext/xfce-config.xml.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-03-02 17:28+0500\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\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" @@ -26,11 +26,11 @@ msgid "This guide provides an extensive introduction to Xfce, a fast, lightweigh msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(version):21 -msgid "5" +msgid "6" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(date):22 -msgid "2011-02-14" +msgid "2011-09-18" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(title):25 @@ -83,7 +83,7 @@ msgid "\n# <i>emerge -avt xfce4-meta</i>\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):86 -msgid "Next, add your regular user(s) to the <c>plugdev</c>, <c>cdrom</c>, <c>cdrw</c>, and <c>usb</c> groups, so that they can mount and use devices such as cameras, optical drives, and USB sticks." +msgid "Next, add your regular user(s) to the <c>cdrom</c>, <c>cdrw</c>, and <c>usb</c> groups, so that they can mount and use devices such as cameras, optical drives, and USB sticks." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre:caption):92 @@ -92,7 +92,7 @@ msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(pre):92 #, no-wrap -msgid "\n<comment>(Replace username with your actual user)</comment>\n# <i>for x in plugdev cdrom cdrw usb ; do gpasswd -a username $x ; done</i>\n" +msgid "\n<comment>(Replace username with your actual user)</comment>\n# <i>for x in cdrom cdrw usb ; do gpasswd -a username $x ; done</i>\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xfce-config.xml(p):97 |