diff options
| -rw-r--r-- | blackboard/ml/about.po | 155 | ||||
| -rw-r--r-- | blackboard/ml/installing.po | 411 | ||||
| -rw-r--r-- | blackboard/ml/issues.po | 979 | ||||
| -rw-r--r-- | blackboard/ml/moreinfo.po | 177 | ||||
| -rw-r--r-- | blackboard/ml/old-stuff.po | 110 | ||||
| -rw-r--r-- | blackboard/ml/release-notes.po | 93 | ||||
| -rw-r--r-- | blackboard/ml/upgrading.po | 2270 | ||||
| -rw-r--r-- | blackboard/ml/whats-new.po | 859 |
8 files changed, 5030 insertions, 24 deletions
diff --git a/blackboard/ml/about.po b/blackboard/ml/about.po index 6f57580..1d23635 100644 --- a/blackboard/ml/about.po +++ b/blackboard/ml/about.po @@ -6,11 +6,160 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2008-10-27 03:39-0400\n" +"Project-Id-Version: release-notes 5.0\n" +"POT-Creation-Date: 2008-08-07 07:55+0300\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: ENCODING\n" +"Content-Transfer-Encoding: ENCODING" + +# type: Content of: <chapter><title> +#: en/about.dbk:9 +msgid "Introduction" +msgstr "" + +# type: Content of: <chapter><para> +#: en/about.dbk:11 +msgid "" +"The primary goals of these Release Notes are to inform users of major " +"changes in this release of the &debian; distribution, to provide information " +"on how to upgrade safely from the previous release to the current release " +"and finally to inform users of known potential issues they could encounter " +"when upgrading to or using the &releasename; release." +msgstr "" + +# type: Content of: <chapter><para> +#: en/about.dbk:19 +msgid "" +"Note that it is impossible to list every known issue and that therefore a " +"selection has been made based on a combination of the expected prevalence " +"and impact of issues." +msgstr "" + +# type: Content of: <chapter><para><footnote> +#: en/about.dbk:24 +msgid "" +"The most recent version of this document is always available at <ulink url=" +"\"&url-release-notes;\"></ulink>. If the version you are reading is more " +"than a month old<footnote>" +msgstr "" + +# type: Content of: <chapter><para><footnote><para> +#: en/about.dbk:26 +msgid "" +"As listed on the front page of the PDF version and in the footer of the HTML " +"version." +msgstr "" + +# type: Content of: <chapter><para> +#: en/about.dbk:28 +msgid "</footnote>, you might wish to obtain the latest version." +msgstr "" + +# type: Content of: <chapter><para> +#: en/about.dbk:31 +msgid "" +"Please note that we only support and document upgrading from the previous " +"release of Debian (in this case, the upgrade from &oldreleasename;). If you " +"need to upgrade from older releases, we suggest you read previous editions " +"of the release notes and upgrade to &oldreleasename; first." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/about.dbk:39 +msgid "Reporting bugs on this document" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/about.dbk:41 +msgid "" +"We have attempted to test all the different upgrade steps described in this " +"document and we have also tried to anticipate all the possible issues our " +"users might encounter." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/about.dbk:46 +msgid "" +"Nevertheless, if you think you have found any bug in this documentation " +"(incorrect information or information that is missing), please file a bug in " +"the <ulink url=\"&url-bts;\">bug tracking system</ulink> against the " +"<systemitem role=\"package\">release-notes</systemitem> package." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/about.dbk:55 +msgid "Contributing upgrade reports" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/about.dbk:57 +msgid "" +"We welcome any information from users related to upgrades from " +"&oldreleasename; to &releasename;. If you are willing to share information " +"please file a bug in the <ulink url=\"&url-bts;\">bug tracking system</" +"ulink> against the <systemitem role=\"package\">upgrade-reports</systemitem> " +"package with your results. We request that you compress any attachments " +"that are included (using <command>gzip</command>)." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/about.dbk:66 +msgid "" +"Please include the following information when submitting your upgrade report:" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#. TODO: check status of #494028 about apt-get vs. aptitude +#. TODO: any more things to add here? +#: en/about.dbk:74 +msgid "" +"The status of your package database before and after the upgrade: " +"<command>dpkg</command>'s status database available at <filename>/var/lib/" +"dpkg/status</filename> and <command>aptitude</command>'s package state " +"information, available at <filename>/var/lib/aptitude/pkgstates</filename>. " +"You should have made a backup before the upgrade as described at <xref " +"linkend=\"data-backup\"/> , but you can also find backups of this " +"information in <filename>/var/backups</filename>." +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/about.dbk:86 +msgid "" +"Session logs using <command>script</command>, as described in <xref linkend=" +"\"record-session\"/> ." +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/about.dbk:92 +msgid "" +"Your <command>aptitude</command> logs, available at <filename>/var/log/" +"aptitude</filename>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/about.dbk:98 +msgid "" +"Note: you should take some time to review and remove any sensitive and/or " +"confidential information from the logs before including them in a bug report " +"as the information will be published in a public database." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/about.dbk:106 +msgid "Sources for this document" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/about.dbk:108 +msgid "" +"This document is generated using <systemitem role=\"package\">docbook-xsl</" +"systemitem>. Sources for the Release Notes are available in the SVN " +"repository of the <emphasis>Debian Documentation Project</emphasis>. You " +"can use the <ulink url=\"&url-svn-release-notes;\">web interface</ulink> to " +"access its files individually through the web and see their changes. For " +"more information on how to access the SVN please consult the <ulink url=" +"\"&url-ddp-svn-info;\">Debian Documentation Project SVN pages</ulink>." +msgstr "" diff --git a/blackboard/ml/installing.po b/blackboard/ml/installing.po index 6f57580..36c980a 100644 --- a/blackboard/ml/installing.po +++ b/blackboard/ml/installing.po @@ -6,11 +6,416 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2008-10-27 03:39-0400\n" +"Project-Id-Version: release-notes 5.0\n" +"POT-Creation-Date: 2008-08-07 07:55+0300\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: ENCODING\n" +"Content-Transfer-Encoding: ENCODING" + +# type: Content of: <chapter><title> +#: en/installing.dbk:9 +msgid "Installation System" +msgstr "" + +# type: Content of: <chapter><para> +#: en/installing.dbk:11 +msgid "" +"The Debian Installer is the official installation system for Debian. It " +"offers a variety of installation methods. Which methods are available to " +"install your system depends on your architecture." +msgstr "" + +# type: Content of: <chapter><para> +#: en/installing.dbk:16 +msgid "" +"Images of the installer for &releasename; can be found together with the " +"Installation Guide on the <ulink url=\"http://www.debian.org/releases/stable/" +"debian-installer/\">Debian website</ulink>." +msgstr "" + +# type: Content of: <chapter><para> +#: en/installing.dbk:22 +msgid "" +"The Installation Guide is also included on the first CD/DVD of the official " +"Debian CD/DVD sets, at:" +msgstr "" + +# type: Content of: <chapter><screen> +#: en/installing.dbk:25 +#, no-wrap +msgid "" +"\n" +"/doc/install/manual/<replaceable>language</replaceable>/index.html\n" +msgstr "" + +# type: Content of: <chapter><para> +#: en/installing.dbk:29 +msgid "" +"You may also want to check the <ulink url=\"http://www.debian.org/releases/" +"stable/debian-installer/index#errata\">errata</ulink> for debian-installer " +"for a list of known issues." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/installing.dbk:34 +msgid "What's new in the installation system?" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/installing.dbk:36 +msgid "" +"There has been a lot of development on the Debian Installer since its first " +"official release with &oldreleasename; resulting in both improved hardware " +"support and some exciting new features." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/installing.dbk:41 +msgid "" +"In these Release Notes we'll only list the major changes in the installer. " +"If you are interested in an overview of the detailed changes since " +"&oldreleasename;, please check the release announcements for the " +"&releasename; beta and RC releases available from the Debian Installer's " +"<ulink url=\"http://www.debian.org/devel/debian-installer/News/\">news " +"history</ulink>." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/installing.dbk:48 +msgid "Major changes" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:51 +msgid "No reboot during the installation" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:54 +msgid "" +"Previously, the installation was split into two parts: setting up the base " +"system and making it bootable, followed by a reboot and after that the " +"execution of <command>base-config</command> which would take care of things " +"like user setup, setup of the package management system and installation of " +"additional packages (using tasksel)." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:61 +msgid "" +"For &releasename; the second stage has been integrated into Debian Installer " +"itself. This has a number of advantages, including increased security and " +"the fact that after the reboot at the end of the installation the new system " +"should already have the correct timezone and, if you installed the Desktop " +"environment, will at once start the graphical user interface." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:70 +msgid "UTF-8 encoding default for new systems" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:73 +msgid "" +"The installer will set up systems to use UTF-8 encoding rather than the old " +"language-specific encodings (like ISO-8859-1, EUC-JP or KOI-8)." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:79 +msgid "More flexible partitioning" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:82 +msgid "" +"It is now possible to set up file systems on an LVM volume using guided " +"partitioning." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:86 +msgid "" +"The installer is also able to set up encrypted file systems. Using manual " +"partitioning you have the choice between <literal>dm-crypt</literal> and " +"<literal>loop-aes</literal>, using a passphrase or a random key, and you can " +"tune various other options. Using guided partitioning, the installer will " +"create an encrypted LVM partition that contains any other file systems " +"(except <filename>/boot</filename>) as logical volumes." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:96 +msgid "Graphical user interface" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:99 +msgid "" +"If you prefer a graphical user interface, try booting the installer with " +"<literal>installgui</literal>." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:103 +msgid "" +"The functionality of the graphical installer is almost identical to the " +"regular installer, only the presentation differs. There is one exception: " +"the graphical frontend does not support setting up encrypted partitions " +"using random keys." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:109 +msgid "" +"The major advantage of the graphical user interface is that it supports more " +"languages than the regular user interface (newt). Information about the " +"graphical installer and the most important differences between the graphical " +"and regular installer are documented in an appendix in the installation " +"guide." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:115 +msgid "" +"Note: the graphical user interface is not available for all architectures." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:120 +msgid "Rescue mode" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:123 +msgid "" +"You can use the installer to solve problems with your system, for example " +"when it refuses to boot. The first steps will be just like a regular " +"installation, but the installer will not start the partitioner. Instead it " +"will offer you a menu of rescue options." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:129 +msgid "" +"Activate the rescue mode by booting the installer with <literal>rescue</" +"literal>, or by adding a boot parameter <literal>rescue/enable=true</" +"literal>." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:136 +msgid "Using sudo instead of root account" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:139 +msgid "" +"During expert installations you can choose to not set up the root account " +"(it will be locked), but instead set up <command>sudo</command> so that the " +"first user can use that for system administration." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:146 +msgid "Cryptographic verification of downloaded packages" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:149 +msgid "" +"Packages downloaded with the installer are now cryptographically checked " +"using <command>apt</command>, making it more difficult to compromise a " +"system being installed over the network." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:156 +msgid "Simplified mail configuration" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:159 +msgid "" +"If the standard system is installed, the installer sets up a basic " +"configuration for the system's mail server which will only provide for local " +"e-mail delivery. The mail server will be unavailable to other systems " +"connected to the same network. If you want to configure your system to " +"handle e-mail not local to the system (either to send e-mail or to receive " +"it), you will have to reconfigure the mail system after installation." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:169 +msgid "Desktop selection" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:172 +msgid "" +"The installation system will install a GNOME desktop as the default desktop " +"if the user asks for one." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:176 +msgid "" +"However, users wishing to install alternate desktop environments can easily " +"do so by adding boot parameters: <literal>tasks=standard, kde-desktop</" +"literal> for KDE and <literal>tasks=standard, xfce-desktop</literal> for " +"Xfce. Note that this will not work when installing from a full CD image " +"without using a network mirror as an additional package source; it will work " +"when using a DVD image or any other installation method." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:184 +msgid "" +"There are also separate CD images available that install the KDE or Xfce " +"desktop environment by default." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:190 +msgid "New languages" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:193 +msgid "" +"Thanks to the huge efforts of translators, Debian can now be installed in 47 " +"languages using the text-based installation user interface. This is six " +"languages more than in &oldreleasename;. Languages added in this release " +"include Belarusian, Esperanto, Estonian, Kurdish, Macedonian, Tagalog, " +"Vietnamese and Wolof. Due to lack of translation updates, two languages " +"have been dropped in this release: Persian and Welsh." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:201 +msgid "" +"If the graphical user interface is used, an additional eleven languages are " +"supported. These languages can only be selected using this installer as " +"their character sets cannot be presented in a non-graphical environment. " +"The new languages are: Bengali, Dzongkha, Gujarati, Hindi, Georgian, Khmer, " +"Malayalam, Nepali, Punjabi, Tamil and Thai." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:208 +msgid "" +"Users that do not wish to use any locale can now select <emphasis>C</" +"emphasis> as their preferred locale in the installer's language selection. " +"More information on language coverage is available at the <ulink url=" +"\"http://d-i.alioth.debian.org/i18n-doc/languages.html\">d-i languages list</" +"ulink>." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:217 +msgid "Simplified localization and timezone selection" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:220 +msgid "" +"Configuration of language, countries and timezones has been simplified to " +"reduce the amount of information needed from the user. The installer will " +"now guess what the system's country and timezone is based on the language " +"selected, or will provide a limited selection if it cannot. Users can still " +"introduce obscure combinations if need be." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/installing.dbk:229 +msgid "Improved system-wide localization" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:232 +msgid "" +"Most of the internationalization and localization tasks that were previously " +"handled by the <systemitem role=\"package\">localization-config</systemitem> " +"tool are now included in the stock Debian installer or in packages " +"themselves. This means that selection of a language will automatically " +"install packages necessary for that language (dictionaries, documentation, " +"fonts...) in both standard and desktop environments. Configuration that is " +"no longer handled automatically includes the papersize configuration and " +"some advanced X Windows keyboard settings for some languages." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/installing.dbk:242 +msgid "" +"Note that language-specific packages will only be installed automatically if " +"they are available during the installation." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/installing.dbk:251 +msgid "Automated installation" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/installing.dbk:253 +msgid "" +"A lot of the changes mentioned in the previous section also imply changes in " +"the support in the installer for automated installation using " +"preconfiguration files. This means that if you have existing " +"preconfiguration files that worked with the &oldreleasename; installer, you " +"cannot expect these to work with the new installer without modification." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/installing.dbk:260 +msgid "" +"The good news is that the <ulink url=\"http://www.debian.org/releases/stable/" +"installmanual\">Installation Guide</ulink> now has a separate appendix with " +"extensive documentation on using preconfiguration." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/installing.dbk:266 +msgid "" +"The &releasename; installer introduces some exciting new features that allow " +"further and easier automation of installs. It also adds support for " +"advanced partitioning using RAID, LVM and encrypted LVM. See the " +"documentation for details." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/installing.dbk:275 +msgid "Popularity contest" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/installing.dbk:277 +msgid "" +"The installation system will again offer to install the <systemitem role=" +"\"package\">popularity-contest</systemitem> package. This package was not " +"installed by default in &oldreleasename; but it was installed in older " +"releases." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/installing.dbk:282 +msgid "" +"<systemitem role=\"package\">popularity-contest</systemitem> provides the " +"Debian project with valuable information on which packages in the " +"distribution are actually used. This information is used mainly to decide " +"the order in which packages are included on installation CD-ROMs, but is " +"also often consulted by Debian developers in deciding whether or not to " +"adopt a package that no longer has a maintainer." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/installing.dbk:290 +msgid "" +"Information from <systemitem role=\"package\">popularity-contest</" +"systemitem> is processed anonymously. We would appreciate it if you would " +"participate in this official survey, helping to improve Debian." +msgstr "" diff --git a/blackboard/ml/issues.po b/blackboard/ml/issues.po index 6f57580..cdab74b 100644 --- a/blackboard/ml/issues.po +++ b/blackboard/ml/issues.po @@ -6,11 +6,984 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2008-10-27 03:39-0400\n" +"Project-Id-Version: release-notes 5.0\n" +"POT-Creation-Date: 2008-08-07 07:55+0300\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: ENCODING\n" +"Content-Transfer-Encoding: ENCODING" + +# type: Content of: <chapter><title> +#: en/issues.dbk:9 +msgid "Issues to be aware of for &releasename;" +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:11 +msgid "Potential problems" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:13 +msgid "" +"Sometimes, changes have side-effects we cannot reasonably avoid, or we " +"expose bugs somewhere else. We document here the issues we are aware of. " +"Please also read the errata, the relevant packages' documentation, bug " +"reports and other information mentioned in <xref linkend=\"morereading\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:19 +msgid "Problems with devices related to udev" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:21 +msgid "" +"Although <systemitem role=\"package\">udev</systemitem> has been tested " +"extensively, you may experience minor problems with some devices that will " +"need to be fixed. The most common problems are changed permission and/or " +"ownership of a device. In some cases a device may not be created by default " +"(e.g. <filename>/dev/video</filename> and <filename>/dev/radio</filename>)." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:28 +msgid "" +"<systemitem role=\"package\">udev</systemitem> provides configuration " +"mechanisms to deal with these issues. See <citerefentry> " +"<refentrytitle>udev</refentrytitle> <manvolnum>8</manvolnum> </citerefentry> " +"and <filename>/etc/udev</filename> for further information." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:36 +msgid "Some applications may no longer work with a 2.4 kernel" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:38 +msgid "" +"Some applications in &releasename; may no longer work with a 2.4 kernel, for " +"example because they require <literal>epoll()</literal> support, which is " +"not available in 2.4 kernels. Such applications may either not work at all " +"or not work correctly until the system has been rebooted with a 2.6 kernel." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:44 +msgid "" +"One example is the HTTP proxy <systemitem role=\"package\">squid</" +"systemitem>." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:49 +msgid "Certain network sites cannot be reached by TCP" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:51 +msgid "" +"Since 2.6.17, Linux aggressively uses TCP window scaling which is specified " +"in RFC 1323. Some servers have a broken behavior, and announce wrong window " +"sizes for themselves. For more details, please see the bug reports <ulink " +"url=\"http://bugs.debian.org/381262\">#381262</ulink>, <ulink url=\"http://" +"bugs.debian.org/395066\">#395066</ulink>, <ulink url=\"http://bugs.debian." +"org/401435\">#401435</ulink>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:59 +msgid "" +"There are usually two workarounds to these problems: either revert the " +"maximum allowed TCP window sizes to a smaller value (preferable) or turn off " +"TCP window scaling altogether (deprecated). See the example commands in the " +"<ulink url=\"http://www.debian.org/devel/debian-installer/errata\">debian-" +"installer errata page</ulink>." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:68 +msgid "Automatic poweroff stops working" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:70 +msgid "" +"On some older systems, <literal>shutdown -h</literal> may not power off the " +"system anymore (but just stop it). This happens because apm needs to be " +"used there. Adding <literal>acpi=off apm=power_off</literal> to the " +"kernel's command line, e.g. in <systemitem role=\"package\">grub</" +"systemitem> or <systemitem role=\"package\">lilo</systemitem> configuration " +"files should fix this issue. Please see bug <ulink url=\"http://bugs.debian." +"org/390547\">#390547</ulink> for additional information." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:81 +msgid "Slower updates of APT package index files" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:83 +msgid "" +"By default, the &releasename; version of <command>apt</command> uses a new " +"way to update APT package index files (when you run <literal>aptitude " +"update</literal>) which downloads differences files (instead of the full " +"package index file) called <literal>pdiff</literal>. This new feature " +"should use less bandwidth and be faster for most systems. Unfortunately, it " +"can also have the opposite effect of making the updates slower on systems " +"with fast network connections (or a very nearby mirror) which are " +"infrequently updated, as it might take more time for the system to merge the " +"differences files than to download a full package index. It is possible to " +"disable this feature by adding <literal>Acquire::Pdiffs false;</literal> to " +"the <filename>/etc/apt/apt.conf</filename> configuration file." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:96 +msgid "" +"This change mostly affects users of the <emphasis>unstable</emphasis> and " +"<emphasis>testing</emphasis> branch of &debian;, due to the changing nature " +"of these archives. Users of &releasename; will notice this feature mainly " +"when updating their package status for the security archive." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:104 +msgid "ACPI support disabled for some HP laptop models in &releasename; kernel" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:106 +msgid "" +"Certain models of HP laptops have an ACPI BIOS that is incompatible with the " +"Linux &kernelversion; kernel shipped in &releasename;, which would prevent " +"the fans from spinning up leading to unnecessary heat stress. Also, fans " +"might not work after the system is suspended. The kernel therefore disables " +"ACPI support internally when it detects certain ACPI BIOS versions. Models " +"known to be affected by this change include the HP nx6125, nx6120, nx6325, " +"nc6120 and nc6000 models." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:114 +msgid "" +"Users who require ACPI support on these systems may install a Linux 2.6.19 " +"or later kernel. Please see Debian bug <ulink url=\"http://bugs.debian." +"org/404143\">#404143</ulink> and <ulink url=\"http://bugs.debian.org/400488" +"\">#400488</ulink>, and Linux Kernel's bugs <ulink url=\"http://bugzilla." +"kernel.org/show_bug.cgi?id=5534\">#5534</ulink> and <ulink url=\"http://" +"bugzilla.kernel.org/show_bug.cgi?id=7122\">#7122</ulink> for additional " +"information." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:125 +msgid "Asynchronous network initialization may cause unpredictable behavior" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:127 +msgid "" +"On systems which use <systemitem role=\"package\">udev</systemitem> to load " +"drivers for network interfaces, it is possible due to the asynchronous " +"nature of <systemitem role=\"package\">udev</systemitem> that the network " +"driver will not be loaded before <command>/etc/init.d/networking</command> " +"runs on system boot. Although including <literal>allow-hotplug</literal> to " +"<filename>/etc/network/interfaces</filename> (in addition to <literal>auto</" +"literal>) will ensure that the network interface is enabled once it becomes " +"available, there is no guarantee that this will finish before the boot " +"sequence begins to start network services, some of which may not behave " +"correctly in the absence of the network interface." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:141 +msgid "Trouble when using WPA secured wireless networks" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:143 +msgid "" +"In &oldreleasename;, the <systemitem role=\"package\">wpasupplicant</" +"systemitem> package was set up as a system service, configured via " +"<filename>/etc/default/wpasupplicant</filename> and a user-provided " +"<filename>/etc/wpasupplicant.conf</filename>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:149 +msgid "" +"In &releasename;, <filename>/etc/init.d/wpasupplicant</filename> has been " +"dropped and the Debian package now integrates with <filename>/etc/network/" +"interfaces</filename>, similar to other packages such as <systemitem role=" +"\"package\">wireless-tools</systemitem>. This means <systemitem role=" +"\"package\">wpasupplicant</systemitem> no longer provides a system service " +"directly." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:157 +msgid "" +"For information on configuring wpasupplicant please refer to <filename>/usr/" +"share/doc/wpasupplicant/README.modes.gz</filename>, which gives examples for " +"<filename>/etc/network/interfaces</filename> files. Updated information " +"about the usage of the <systemitem role=\"package\">wpasupplicant</" +"systemitem> package in Debian can be found in the <ulink url=\"http://wiki." +"debian.org/WPA\">Debian Wiki</ulink>." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:167 +msgid "Problems with non-ASCII characters in filenames" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:169 +msgid "" +"Mounting vfat, ntfs or iso9660 file systems with files that include non-" +"ASCII characters in their filenames will give failures when one tries to use " +"the filenames unless mounting is done with the utf8 option. An indication " +"might be the following failure: 'Invalid or incomplete multibyte or wide " +"character'. A possible solution is to use <literal>defaults,utf8</literal> " +"as mount options for vfat, ntfs and iso9660 file systems when they contain " +"filenames with non-ASCII characters." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:178 +msgid "" +"Note that the Linux kernel does not support case-insensitive filename " +"handling for vfat when the <literal>utf8</literal> option is used." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:184 +msgid "Sound stops working" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:186 +msgid "" +"In rare cases the sound might stop working after the upgrade. If this " +"happens, go through the alsa checklist: run <command>alsaconf</command> as " +"root user, add your user to the <literal>audio</literal> group, use " +"alsamixer and make sure levels are up and it is unmuted, make sure arts or " +"esound stopped, make sure OSS modules unloaded, make sure speakers are on, " +"check whether the command <literal>cat /dev/urandom > /dev/dsp</literal> " +"works for root." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:198 +msgid "Upgrading to a 2.6 kernel" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:200 +msgid "" +"The 2.6 kernel series contains major changes from the 2.4 series. Modules " +"have been renamed and a lot of drivers have been partially or sometimes " +"almost completely rewritten. Upgrading to a 2.6 kernel from an earlier " +"version is therefore not a process to be undertaken lightly. This section " +"aims to make you aware of some of the issues you may face." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:207 +msgid "" +"If you compile your own kernel from source, make sure you install " +"<systemitem role=\"package\">module-init-tools</systemitem> before you " +"reboot with the 2.6 kernel. This package replaces <systemitem role=\"package" +"\">modutils</systemitem> for 2.6 kernels. If you install one of the Debian " +"<systemitem role=\"package\">linux-image</systemitem> packages, this package " +"will be installed automatically because of dependencies." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:215 +msgid "" +"If you use <emphasis>LVM</emphasis>, you should also install <systemitem " +"role=\"package\">lvm2</systemitem> before you reboot as the 2.6 kernel does " +"not directly support LVM1. To access LVM1 volumes, the compatibility layer " +"of <systemitem role=\"package\">lvm2</systemitem> (the dm-mod module) is " +"used. You can leave <systemitem role=\"package\">lvm10</systemitem> " +"installed; the init scripts will detect which kernel is used and execute the " +"appropriate version." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:223 +msgid "" +"If you have entries in the <filename>/etc/modules</filename> file (the list " +"of modules to be loaded during system boot), be aware that some module names " +"may have changed. If this happens you will have to update this file with " +"the new module names." +msgstr "" + +# type: Content of: <chapter><section><para><footnote> +#: en/issues.dbk:229 +msgid "" +"For some SATA disk controllers, the device assigned to a drive and its " +"partitions may change from <filename>/dev/hdX</filename> to <filename>/dev/" +"sdX</filename>. If this happens, you will have to modify your <filename>/" +"etc/fstab</filename> and bootloader configuration accordingly. Unless these " +"changes are made correctly, your system may not boot correctly<footnote>" +msgstr "" + +# type: Content of: <chapter><section><para><footnote><para> +#: en/issues.dbk:234 +msgid "" +"It will boot the kernel but will fail when trying to mount the root file " +"system and will abort with an error <emphasis>waiting for root file system</" +"emphasis> followed by <emphasis>unable to mount /dev/hdX ..not found</" +"emphasis>. You can use the <command>initramfs</command> shell to fix this " +"issue, after you identify the newly assigned device names in the kernel boot " +"messages or by reviewing the contents of <filename>/dev/disk/</filename>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:240 +msgid "</footnote>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:243 +msgid "" +"Once you have installed your 2.6 kernel, but before you reboot, make sure " +"you have a recovery method. First, make sure that the bootloader " +"configuration has entries for both the new kernel and the old, working 2.4 " +"kernel. You should also ensure you have a rescue floppy or CD-ROM to hand, " +"in case misconfiguration of the bootloader prevents you from booting the old " +"kernel." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:250 +msgid "Keyboard configuration" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:252 +msgid "" +"The most invasive change in the 2.6 kernels is a fundamental change of the " +"input layer. This change makes all keyboards look like normal PC " +"keyboards. This means that if you currently have a different type of " +"keyboard selected (e.g. a USB-MAC or Sun keyboard), you will very likely " +"end up with a non-working keyboard after rebooting with the new 2.6 kernel." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:259 +msgid "" +"If you can SSH into the box from another system, you can resolve this issue " +"by running <literal>dpkg-reconfigure console-data</literal>, choosing the " +"option Select keymap from full list and selecting a pc keyboard." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:264 +msgid "" +"If your console keyboard is affected, you will probably also need to " +"reconfigure your keyboard for the X Window System. You can do this either " +"by running <literal>dpkg-reconfigure xserver-xorg</literal> or by editing " +"<filename>/etc/X11/xorg.conf</filename> directly. Don't forget to read the " +"documentation referred to in <xref linkend=\"nownownow\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:271 +msgid "" +"This issue is unlikely to affect the &arch-title; architecture as all PS/2 " +"and most USB keyboards will already be configured as a normal PC keyboard." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:276 +msgid "" +"Note that if you are using a USB keyboard, this may be configured as either " +"a \"normal\" PC keyboard or as a USB-MAC keyboard. In the first case you " +"will not be affected by this issue." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:283 +msgid "Mouse configuration" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:285 +msgid "" +"Again because of the changes in the input layer, you may have to reconfigure " +"the X Window System and <systemitem role=\"package\">gpm</systemitem> if " +"your mouse is not working after upgrading to a 2.6 kernel. The most likely " +"cause is that the device which gets the data from the mouse has changed. " +"You may also need to load different modules." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/issues.dbk:294 +msgid "Sound configuration" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/issues.dbk:296 +msgid "" +"For the 2.6 kernel series the ALSA sound drivers are recommended over the " +"older OSS sound drivers. ALSA sound drivers are provided as modules by " +"default. In order for sound to work, the ALSA modules appropriate for your " +"sound hardware need to be loaded. In general this will happen automatically " +"if you have, in addition to the <systemitem role=\"package\">alsa-base</" +"systemitem> package, either the <systemitem role=\"package\">hotplug</" +"systemitem> package or the <systemitem role=\"package\">discover</" +"systemitem> package installed. The <systemitem role=\"package\">alsa-base</" +"systemitem> package also blacklists OSS modules to prevent <command>hotplug</" +"command> and <command>discover</command> from loading them. If you have OSS " +"modules listed in <filename>/etc/modules</filename>, you should remove them." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:313 +msgid "XFree86 to X.Org transition" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:315 +msgid "" +"The transition to X.Org involves some structural changes. In case all " +"installed packages are from Debian and also included in &releasename;, the " +"upgrade should work without problems. However, experience has shown that " +"there are a few changes to be aware of, as they can potentially cause issues " +"during the upgrade." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:322 +msgid "" +"The most important change is that <filename>/usr/X11R6/bin</filename> has " +"been dropped and only remains as a symlink to <filename>/usr/bin</" +"filename>. This means the directory has to be empty at the time the new " +"packages are installed. The new packages conflict with most packages that " +"used <filename>/usr/X11R6/bin</filename>, but in some cases manual " +"intervention may be needed. Please remember to not run the distribution " +"upgrade from within an X session." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:331 +msgid "" +"In case the upgrade aborts during X.Org installation, you should check if " +"any files are still left in <filename>/usr/X11R6/bin</filename>. You can " +"then use <literal>dpkg -S</literal> to find out which Debian package " +"installed that file (if any), and remove such packages with <literal>dpkg --" +"remove</literal>. Please make a note which packages you remove, so that you " +"can install substitute packages later on. Before continuing with the " +"upgrade, all files in <filename>/usr/X11R6/bin</filename> need to be removed." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:340 +msgid "" +"Please read <ulink url=\"http://wiki.debian.org/Xorg69To7\"></ulink> for " +"more details and other issues." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:344 +msgid "" +"If you experience problems with X.Org after restarting, it might be also " +"worth to restart the font server by running <literal>/etc/init.d/xfs " +"restart</literal>. This happens due to <filename>/etc/X11/fs/xfs.options</" +"filename> containing a line with <literal>no-restart-on-upgrade</literal>, " +"but the font paths have changed." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:353 +msgid "No support for 8-bit displays in many applications" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:355 +msgid "" +"After the upgrade to the X.Org and the latest libraries, X terminals which " +"can only represent colors 8 bits depth will not work. This is because the " +"Cairo 2D vector graphics library (<systemitem role=\"package\">libcairo2</" +"systemitem>) doesn't have 8-bit pseudocolor support. This library is used " +"by the GNOME and Xfce desktops as well as by many desktop applications " +"compiled with the Gtk2+ toolkit, such as <systemitem role=\"package" +"\">abiword</systemitem>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:363 +msgid "" +"Known systems that are affected by this include some Sun machines and X " +"terminals from Tektronix, NCD, IBM and SGI, as well as some other remote X " +"windowing systems. You should configure these terminals to use 16-bit " +"colour, if possible." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:369 +msgid "" +"More information is available in Freedesktop's <ulink url=\"https://bugs." +"freedesktop.org/show_bug.cgi?id=4945\">bug #4945</ulink>." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:375 +msgid "Upgrading from exim to exim4" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:377 +msgid "" +"One of the packages that has been obsoleted by the &releasename; release is " +"the Mail Transfer Agent (MTA) <systemitem role=\"package\">exim</" +"systemitem>, which has been replaced by the completely new package " +"<systemitem role=\"package\">exim4</systemitem>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:383 +msgid "" +"<command>exim</command> (version 3.xx) has been unmaintained upstream for " +"years, and Debian has dropped support for that version as well. If you are " +"still using <command>exim</command> 3.xx, please upgrade your <systemitem " +"role=\"package\">exim</systemitem> installation to <systemitem role=\"package" +"\">exim4</systemitem> manually. Since <systemitem role=\"package\">exim4</" +"systemitem> is already part of &oldreleasename;, you can choose to do the " +"upgrade on your &oldreleasename; system before the upgrade to &releasename;, " +"or after the &releasename; upgrade at your convenience. Just remember that " +"your old <systemitem role=\"package\">exim</systemitem> package is not going " +"to be upgraded and that it won't get security support after support for " +"&oldreleasename; has been discontinued." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:395 +msgid "" +"Note that, depending on your configuration of <systemitem role=\"package" +"\">debconf</systemitem>, you may not be asked any configuration question " +"during installation of <systemitem role=\"package\">exim4</systemitem>. If " +"no questions are asked, the system will default to a 'local delivery' " +"setup. Configuration is possible using the command <literal>dpkg-" +"reconfigure exim4-config</literal>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:403 +msgid "" +"The <systemitem role=\"package\">exim4</systemitem> packages in Debian are " +"extensively documented. The package's home page is <ulink url=\"http://wiki." +"debian.org/PkgExim4\"></ulink> on the Debian Wiki, and the README file can " +"be found at <ulink url=\"http://pkg-exim4.alioth.debian.org/README/README." +"Debian.html\"></ulink> and inside the packages as well." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:411 +msgid "" +"The README file has a chapter about Packaging, which explains the different " +"package variations we offer, and it has a chapter about Updating from " +"<command>Exim</command> 3, which will help you in doing the actual " +"transition." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:418 +msgid "Upgrading apache2" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:420 +msgid "" +"Apache has been upgraded to the new version 2.2. Although this shouldn't " +"impact the average user, there are some potential issues to be aware of." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:424 +msgid "" +"<ulink url=\"http://httpd.apache.org/docs/2.2/upgrading.html\"></ulink> " +"contains the upstream changes. Please read this page, and remember that " +"especially:" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/issues.dbk:430 +msgid "all modules need to be recompiled" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/issues.dbk:435 +msgid "authorization modules have been resorted and renamed" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/issues.dbk:440 +msgid "some configuration options have been renamed" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:445 +msgid "" +"Debian-specific changes include that the string SSL is no longer defined, as " +"ssl is now supported by the default package." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:449 +msgid "" +"If you are using the experimental ITK MPM (from the <systemitem role=" +"\"package\">apache2-mpm-itk</systemitem> package), the cgi module will not " +"be correctly enabled by default. To properly enable it, you will need to " +"manually disable <literal>mod_cgid</literal> and enable <literal>mod_cgi</" +"literal>:" +msgstr "" + +# type: Content of: <chapter><section><screen> +#: en/issues.dbk:455 +#, no-wrap +msgid "" +"\n" +"# cd /etc/apache2/mods-enabled\n" +"# rm cgid.conf cgid.load\n" +"# ln -s ../mods-available/cgi.load .\n" +"# /etc/init.d/apache2 force-reload\n" +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:464 +msgid "Upgrading Zope and Plone" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:466 +msgid "" +"Zope and all related products have been updated. Many products were also " +"dropped from the distribution (either because they were obsoleted, or " +"because they are incompatible with the newer Zope, CMF or Plone)." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:471 +msgid "" +"Unfortunately there is no easy and guaranteed way to upgrade a complex " +"<command>zope</command> or <command>plone</command> server. Even though " +"Plone includes a migration tool, experience has shown that automatic " +"migrations can easily fail." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:477 +msgid "" +"For this reason, users are recommended to set up their system so they can " +"continue to run the &oldreleasename; installation of Zope/Plone alongside " +"the new &releasename; versions while testing the migration." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:482 +msgid "" +"The easiest and safest way to achieve this, is to make a copy of your " +"&oldreleasename; system to another hard disk or partition, and then upgrade " +"only one of the two copies. You can then use <command>chroot</command> to " +"run the &oldreleasename; version in parallel to the &releasename; version." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:488 +msgid "" +"It is not possible to have the old and new versions of Zope/Plone installed " +"together on an &releasename; system, partly because the old packages depend " +"on <systemitem role=\"package\">python2.3</systemitem> which cannot be " +"installed together with <systemitem role=\"package\">python2.4</systemitem>." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:496 +msgid "Wildcard expansion (globbing) with GNU tar" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:498 +msgid "" +"Previous versions of GNU <command>tar</command> assumed shell-style globbing " +"when extracting files from or listing an archive. For example:" +msgstr "" + +# type: Content of: <chapter><section><screen> +#: en/issues.dbk:501 +#, no-wrap +msgid "" +"\n" +"tar xf foo.tar '*.c'\n" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:505 +msgid "" +"would extract all files whose names end in '.c'. This behavior was not " +"documented and was incompatible with traditional <command>tar</command> " +"implementations. Therefore, starting from version 1.15.91, GNU " +"<command>tar</command> no longer uses globbing by default. For example, the " +"above invocation is now interpreted as a request to extract from the archive " +"the file named '*.c'." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:513 +msgid "" +"See <filename>/usr/share/doc/tar/NEWS.gz</filename> for further information." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:518 +msgid "NIS and Network Manager" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:520 +msgid "" +"The version of <command>ypbind</command> included with <systemitem role=" +"\"package\">nis</systemitem> for &releasename; contains support for Network " +"Manager. This support causes <command>ypbind</command> to disable NIS " +"client functionality when Network Manager reports that the computer is " +"disconnected from the network. Since Network Manager will usually report " +"that the computer is disconnected when it is not in use, NIS users with NIS " +"client systems should ensure that Network Manager support is disabled on " +"those systems." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:529 +msgid "" +"This can be done by either uninstalling the <systemitem role=\"package" +"\">network-manager</systemitem> package, or editing <filename>/etc/default/" +"nis</filename> to add <literal>-no-dbus</literal> to <literal>YPBINDARGS</" +"literal>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:535 +msgid "" +"The use of <literal>-no-dbus</literal> is the default for new installs of " +"Debian, but was not the default in previous releases." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:541 +msgid "Deprecated insecure php configurations" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:543 +msgid "" +"For many years, turning on the <literal>register_globals</literal> settings " +"in PHP has been known to be insecure and dangerous, and this option has " +"defaulted to off for some time now. This configuration is now finally " +"deprecated on Debian systems as too dangerous. The same applies to flaws in " +"<literal>safe_mode</literal> and <literal>open_basedir</literal>, which have " +"also been unmaintained for some time." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:551 +msgid "" +"Starting with this release, the Debian security team does not provide " +"security support for a number of PHP configurations which are known to be " +"insecure. Most importantly, issues resulting from " +"<literal>register_globals</literal> being turned on will no longer be " +"addressed." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:557 +msgid "" +"If you run legacy applications that require <literal>register_globals</" +"literal>, enable it for the respective paths only, e.g. through the Apache " +"configuration file. More information is available in the <filename>README." +"Debian.security</filename> file in the PHP documentation directory " +"(<filename>/usr/share/doc/php4</filename>, <filename>/usr/share/doc/php5</" +"filename>)." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:567 +msgid "Security status of Mozilla products" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:569 +msgid "" +"The Mozilla programs <systemitem role=\"package\">firefox</systemitem> and " +"<systemitem role=\"package\">thunderbird</systemitem> (rebranded in Debian " +"to <systemitem role=\"package\">iceweasel</systemitem> and <systemitem role=" +"\"package\">icedove</systemitem>, respectively), are important tools for " +"many users. Unfortunately the upstream security policy is to urge users to " +"update to new upstream versions, which conflicts with Debian's policy of not " +"shipping large functional changes in security updates. We cannot predict it " +"today, but during the lifetime of &releasename; the Debian Security Team may " +"come to a point where supporting Mozilla products is no longer feasible and " +"announce the end of security support for Mozilla products. You should take " +"this into account when deploying Mozilla and consider alternatives available " +"in Debian if the absence of security support would pose a problem for you." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:585 +msgid "KDE desktop" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:587 +msgid "" +"KDE media handling has changed in the version available in &releasename; " +"from using <filename>device:/</filename> to <filename>media:/</filename>. " +"Some user configuration files might have stored <filename>device:/</" +"filename> links in them which should be adapted. Notably, <filename>~/.kde/" +"share/apps/konqsidebartng/virtual_folders/services</filename> contains this " +"reference and can be safely deleted as it will not be created when setting " +"up new users." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:596 +msgid "" +"There have been many changes in the KDE desktop environment from the version " +"shipped in &oldreleasename; to the version in &releasename;, you can find " +"more information in the <ulink url=\"http://www.kde.org/announcements/" +"announce-3.5.php\">KDE 3.5 Release Notes</ulink>." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:604 +msgid "GNOME desktop changes and support" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:606 +msgid "" +"If you used the GNOME desktop in &oldreleasename; you will not benefit from " +"some of the changes introduced in the default configuration in Debian for " +"&releasename;. In some extreme cases the GNOME desktop might not properly " +"handle your old configuration and might not behave properly." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:612 +msgid "" +"If you have not heavily invested in configuring your GNOME desktop you might " +"want to move the <filename>.gconf</filename> directory in user's home " +"directories to a different name (such as <filename>.gconf.old</filename>) so " +"that it gets recreated, with the default configuration for &releasename;, " +"upon starting a new session." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:619 +msgid "" +"With the release of &releasename;, Debian no longer contains packages for " +"most of the obsolete version 1 release of GNOME, although some packages " +"remain in order to support some Debian packages which have not yet been " +"updated to GNOME 2. Packages for GTK1.2 remain fully maintained." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:625 +msgid "" +"There have been many changes in the GNOME desktop environment from the " +"version shipped in &oldreleasename; to the version in &releasename;, you can " +"find more information in the <ulink url=\"http://www.gnome.org/start/2.14/" +"notes/en/\">GNOME 2.14 Release Notes</ulink>." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:633 +msgid "Default editor" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:635 +msgid "" +"If you were using <command>vim</command> as your default editor, this may be " +"changed to <command>nano</command> during the upgrade." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:639 +msgid "" +"Administrators who wish to change the default editor for all users will have " +"to update the alternatives system using:" +msgstr "" + +# type: Content of: <chapter><section><screen> +#: en/issues.dbk:642 +#, no-wrap +msgid "" +"\n" +"# update-alternatives --config editor\n" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:646 +msgid "" +"Users wishing to change the default editor can define the environment " +"variable <emphasis>EDITOR</emphasis> by introducing the following lines in " +"their own profiles:" +msgstr "" + +# type: Content of: <chapter><section><screen> +#: en/issues.dbk:650 +#, no-wrap +msgid "" +"\n" +"EDITOR=vi\n" +"export EDITOR\n" +"alias editor=$EDITOR\n" +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:658 +msgid "Message of the day" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:660 +msgid "" +"<filename>/etc/motd</filename> is now a symlink to <filename>/var/run/motd</" +"filename> which is rebuilt by <command>/etc/init.d/bootmisc.sh</command> " +"from a template, <command>/etc/motd.tail</command>, at each reboot. It " +"means that changes made to <filename>/etc/motd</filename> will be lost. " +"Changes made into <filename>/etc/motd.tail</filename> are not automatically " +"applied to <filename>/etc/motd</filename> other than at reboot." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:669 +msgid "" +"Also, the EDITMOTD variable at <filename>/etc/default/rcS</filename> no " +"longer has any effect. If you wish to disable updating of the motd, or want " +"to maintain your own content for the message of the day you just have to " +"point the <filename>/etc/motd</filename> symlink to a different file such as " +"<filename>/etc/motd.static</filename> and make your changes there." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/issues.dbk:678 +msgid "Not default support for unicode in emacs21*" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/issues.dbk:680 +msgid "" +"Emacs21 and emacs21-nox are not configured to use Unicode by default. For " +"more information and a workaround please see <ulink url=\"http://bugs.debian." +"org/419490\">Bug #419490</ulink>." +msgstr "" diff --git a/blackboard/ml/moreinfo.po b/blackboard/ml/moreinfo.po index 6f57580..cffde07 100644 --- a/blackboard/ml/moreinfo.po +++ b/blackboard/ml/moreinfo.po @@ -6,11 +6,182 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2008-10-27 03:39-0400\n" +"Project-Id-Version: release-notes 5.0\n" +"POT-Creation-Date: 2008-08-07 07:55+0300\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: ENCODING\n" +"Content-Transfer-Encoding: ENCODING" + +# type: Content of: <chapter><title> +#: en/moreinfo.dbk:9 +msgid "More information on &debian;" +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/moreinfo.dbk:11 +msgid "Further reading" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/moreinfo.dbk:13 +msgid "" +"Beyond these release notes and the installation guide, further documentation " +"on &debian; is available from the Debian Documentation Project (DDP), whose " +"goal is to create high-quality documentation for Debian users and " +"developers. Documentation, including the Debian Reference, Debian New " +"Maintainers Guide, and Debian FAQ are available, and many more. For full " +"details of the existing resources see the <ulink url=\"http://www.debian.org/" +"doc/ddp\">DDP website</ulink>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/moreinfo.dbk:22 +msgid "" +"Documentation for individual packages is installed into <filename>/usr/share/" +"doc/<replaceable>package</replaceable></filename>. This may include " +"copyright information, Debian specific details and any upstream " +"documentation." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/moreinfo.dbk:30 +msgid "Getting help" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/moreinfo.dbk:32 +msgid "" +"There are many sources of help, advice and support for Debian users, but " +"these should only be considered if research into documentation of the issue " +"has exhausted all sources. This section provides a short introduction into " +"these which may be helpful for new Debian users." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/moreinfo.dbk:38 +msgid "Mailing lists" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/moreinfo.dbk:40 +msgid "" +"The mailing lists of most interest to Debian users are the debian-user list " +"(English) and other debian-user-<replaceable>language</replaceable> lists " +"(for other languages). For information on these lists and details of how to " +"subscribe see <ulink url=\"http://lists.debian.org/\"></ulink>. Please " +"check the archives for answers to your question prior to posting and also " +"adhere to standard list etiquette." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/moreinfo.dbk:50 +msgid "Internet Relay Chat" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/moreinfo.dbk:52 +msgid "" +"Debian has an IRC channel dedicated to the support and aid of Debian users " +"located on the OFTC IRC network. To access the channel, point your favorite " +"IRC client at irc.debian.org and join #debian." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/moreinfo.dbk:57 +msgid "" +"Please follow the channel guidelines, respecting other users fully. The " +"guidelines are available at the <ulink url=\"http://wiki.debian.org/DebianIRC" +"\">Debian Wiki</ulink>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/moreinfo.dbk:62 +msgid "" +"For more information on OFTC please visit the <ulink url=\"http://www.oftc." +"net/\">website</ulink>." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/moreinfo.dbk:70 +msgid "Reporting bugs" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/moreinfo.dbk:72 +msgid "" +"We strive to make &debian; a high quality operating system, however that " +"does not mean that the packages we provide are totally free of bugs. " +"Consistent with Debian's open development philosophy and as a service to our " +"users, we provide all the information on reported bugs at our own Bug " +"Tracking System (BTS). The BTS is browseable at <ulink url=\"http://bugs." +"debian.org/\">bugs.debian.org</ulink>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/moreinfo.dbk:80 +msgid "" +"If you find a bug in the distribution or in packaged software that is part " +"of it, please report it so that it can be properly fixed for future " +"releases. Reporting bugs requires a valid email address. We ask for this " +"so that we can trace bugs and developers can get in contact with submitters " +"should additional information be needed." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/moreinfo.dbk:87 +msgid "" +"You can submit a bug report using the program <command>reportbug</command> " +"or manually using email. You can read more about the Bug Tracking System " +"and how to use it by reading the reference cards (available at <filename>/" +"usr/share/doc/debian</filename> if you have <systemitem role=\"package\">doc-" +"debian</systemitem> installed) or online at the <ulink url=\"http://bugs." +"debian.org/\">Bug Tracking System</ulink>." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/moreinfo.dbk:97 +msgid "Contributing to Debian" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/moreinfo.dbk:99 +msgid "" +"You do not need to be an expert to contribute to Debian. By assisting users " +"with problems on the various user support <ulink url=\"http://lists.debian." +"org/\">lists</ulink> you are contributing to the community. Identifying " +"(and also solving) problems related to the development of the distribution " +"by participating on the development <ulink url=\"http://lists.debian.org/" +"\">lists</ulink> is also extremely helpful. To maintain Debian's high " +"quality distribution, <ulink url=\"http://bugs.debian.org/\">submit bugs</" +"ulink> and help developers track them down and fix them. If you have a way " +"with words then you may want to contribute more actively by helping to write " +"<ulink url=\"http://www.debian.org/doc/ddp\">documentation</ulink> or <ulink " +"url=\"http://www.debian.org/international/\">translate</ulink> existing " +"documentation into your own language." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/moreinfo.dbk:114 +msgid "" +"If you can dedicate more time, you could manage a piece of the Free Software " +"collection within Debian. Especially helpful is if people adopt or maintain " +"items that people have requested for inclusion within Debian. The <ulink " +"url=\"http://www.debian.org/devel/wnpp/\">Work Needing and Prospective " +"Packages database</ulink> details this information. If you have an interest " +"in specific groups then you may find enjoyment in contributing to some of " +"Debian's subprojects which include ports to particular architectures, <ulink " +"url=\"http://www.debian.org/devel/debian-jr/\">Debian Jr.</ulink> and <ulink " +"url=\"http://www.debian.org/devel/debian-med/\">Debian Med</ulink>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/moreinfo.dbk:125 +msgid "" +"In any case, if you are working in the free software community in any way, " +"as a user, programmer, writer or translator you are already helping the free " +"software effort. Contributing is rewarding and fun, and as well as allowing " +"you to meet new people it gives you that warm fuzzy feeling inside." +msgstr "" diff --git a/blackboard/ml/old-stuff.po b/blackboard/ml/old-stuff.po index 6f57580..14bf8b3 100644 --- a/blackboard/ml/old-stuff.po +++ b/blackboard/ml/old-stuff.po @@ -6,11 +6,115 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2008-10-27 03:39-0400\n" +"Project-Id-Version: release-notes 5.0\n" +"POT-Creation-Date: 2008-08-07 07:55+0300\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: ENCODING\n" +"Content-Transfer-Encoding: ENCODING" + +# type: Content of: <appendix><title> +#: en/old-stuff.dbk:9 +msgid "Managing your &oldreleasename; system" +msgstr "" + +# type: Content of: <appendix><para> +#: en/old-stuff.dbk:11 +msgid "" +"This appendix contains information on how to make sure you can install or " +"upgrade &oldreleasename; packages before you upgrade to &releasename;. This " +"should only be necessary in specific situations." +msgstr "" + +# type: Content of: <appendix><section><title> +#: en/old-stuff.dbk:16 +msgid "Upgrading your &oldreleasename; system" +msgstr "" + +# type: Content of: <appendix><section><para> +#: en/old-stuff.dbk:18 +msgid "" +"Basically this is no different than any other upgrade of &oldreleasename; " +"you've been doing. The only difference is that you first need to make sure " +"your package list still contains &oldreleasename; packages as explained in " +"<xref linkend=\"old-sources\"/> ." +msgstr "" + +# type: Content of: <appendix><section><para> +#: en/old-stuff.dbk:24 +msgid "" +"If you upgrade your system using a Debian mirror, it will automatically be " +"upgraded to the latest &oldreleasename; point release." +msgstr "" + +# type: Content of: <appendix><section><title> +#: en/old-stuff.dbk:30 +msgid "Checking your sources list" +msgstr "" + +# type: Content of: <appendix><section><para> +#: en/old-stuff.dbk:32 +msgid "" +"If any of the lines in your <filename>/etc/apt/sources.list</filename> refer " +"to 'stable', you are effectively already using &releasename;. If you have " +"already run <literal>apt-get update</literal>, you can still get back " +"without problems following the procedure below." +msgstr "" + +# type: Content of: <appendix><section><para> +#: en/old-stuff.dbk:38 +msgid "" +"If you have also already installed packages from &releasename;, there " +"probably is not much point in installing packages from &oldreleasename; " +"anymore. In that case you will have to decide for yourself whether you want " +"to continue or not. It is possible to downgrade packages, but that is not " +"covered here." +msgstr "" + +# type: Content of: <appendix><section><para> +#: en/old-stuff.dbk:44 +msgid "" +"Open the file <filename>/etc/apt/sources.list</filename> with your favorite " +"editor (as root) and check all lines beginning with <literal>deb http:</" +"literal> or <literal>deb ftp:</literal> for a reference to <literal>stable</" +"literal>. If you find any, change <literal>stable</literal> to " +"<literal>&oldreleasename;</literal>." +msgstr "" + +# type: Content of: <appendix><section><para> +#: en/old-stuff.dbk:51 +msgid "" +"If you have any lines starting with <literal>deb file:</literal>, you will " +"have to check for yourself if the location they refer to contains a " +"&oldreleasename; or an &releasename; archive." +msgstr "" + +# type: Content of: <appendix><section><para> +#: en/old-stuff.dbk:56 +msgid "" +"<emphasis role=\"strong\">Important!</emphasis> Do not change any lines that " +"begin with <literal>deb cdrom:</literal>. Doing so would invalidate the " +"line and you would have to run <command>apt-cdrom</command> again. Do not " +"be alarmed if a 'cdrom' source line refers to <literal>unstable</literal>. " +"Although confusing, this is normal." +msgstr "" + +# type: Content of: <appendix><section><para> +#: en/old-stuff.dbk:63 +msgid "If you've made any changes, save the file and execute" +msgstr "" + +# type: Content of: <appendix><section><screen> +#: en/old-stuff.dbk:65 +#, no-wrap +msgid "" +"\n" +"# apt-get update\n" +msgstr "" + +# type: Content of: <appendix><section><para> +#: en/old-stuff.dbk:69 +msgid "to refresh the package list." +msgstr "" diff --git a/blackboard/ml/release-notes.po b/blackboard/ml/release-notes.po index 6f57580..796cb29 100644 --- a/blackboard/ml/release-notes.po +++ b/blackboard/ml/release-notes.po @@ -6,11 +6,98 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2008-10-27 03:39-0400\n" +"Project-Id-Version: release-notes 5.0\n" +"POT-Creation-Date: 2008-08-07 07:55+0300\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: ENCODING\n" +"Content-Transfer-Encoding: ENCODING" + +# type: Attribute 'lang' of: <book> +#: en/release-notes.dbk:8 +msgid "en" +msgstr "" + +# type: Content of: <book><title> +#: en/release-notes.dbk:9 +msgid "Release Notes for &debian; &release; (&releasename;), &arch-title;" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author><contrib> +#: en/release-notes.dbk:16 en/release-notes.dbk:22 +msgid "current release" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author> +#: en/release-notes.dbk:19 +msgid "<author> <firstname>Luk</firstname> <surname>Claes</surname>" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author> +#: en/release-notes.dbk:23 +msgid "" +"<email>doc-update@release.debian.org</email> </author> <author> " +"<firstname>Josip</firstname> <surname>Rodin</surname>" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author><contrib> +#: en/release-notes.dbk:28 en/release-notes.dbk:33 en/release-notes.dbk:38 +#: en/release-notes.dbk:43 en/release-notes.dbk:48 en/release-notes.dbk:53 +#: en/release-notes.dbk:58 en/release-notes.dbk:63 en/release-notes.dbk:68 +msgid "old release" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author> +#: en/release-notes.dbk:29 +msgid "" +"</author> <author> <firstname>Bob</firstname> <surname>Hilliard</surname>" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author> +#: en/release-notes.dbk:34 +msgid "" +"</author> <author> <firstname>Adam</firstname> <surname>Di Carlo</surname>" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author> +#: en/release-notes.dbk:39 +msgid "" +"</author> <author> <firstname>Anne</firstname> <surname>Bezemer</surname>" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author> +#: en/release-notes.dbk:44 +msgid "" +"</author> <author> <firstname>Rob</firstname> <surname>Bradford</surname>" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author> +#: en/release-notes.dbk:49 +msgid "</author> <author> <firstname>Frans</firstname> <surname>Pop</surname>" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author> +#: en/release-notes.dbk:54 +msgid "" +"</author> <author> <firstname>Andreas</firstname> <surname>Barth</surname>" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author> +#: en/release-notes.dbk:59 +msgid "" +"</author> <author> <firstname>Javier</firstname> <surname>Fernández-Sanguino " +"Peña</surname>" +msgstr "" + +# type: Content of: <book><bookinfo><authorgroup><author> +#: en/release-notes.dbk:64 +msgid "" +"</author> <author> <firstname>Steve</firstname> <surname>Langasek</surname>" +msgstr "" + +# type: Content of: <book><bookinfo><pubdate> +#: en/release-notes.dbk:71 +msgid "2008-08-06" +msgstr "" diff --git a/blackboard/ml/upgrading.po b/blackboard/ml/upgrading.po index 6f57580..1fbd519 100644 --- a/blackboard/ml/upgrading.po +++ b/blackboard/ml/upgrading.po @@ -6,11 +6,2275 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2008-10-27 03:39-0400\n" +"Project-Id-Version: release-notes 5.0\n" +"POT-Creation-Date: 2008-08-07 07:55+0300\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: ENCODING\n" +"Content-Transfer-Encoding: ENCODING" + +# type: Content of: <chapter><title> +#: en/upgrading.dbk:9 +msgid "Upgrades from previous releases" +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/upgrading.dbk:11 +msgid "Preparing for the upgrade" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:13 +msgid "" +"We suggest that before upgrading you also read the information in <xref " +"linkend=\"information\"/> . That chapter covers potential issues not " +"directly related to the upgrade process but which could still be important " +"to know about before you begin." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:19 +msgid "Back up any data or configuration information" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:21 +msgid "" +"Before upgrading your system, it is strongly recommended that you make a " +"full backup, or at least back up any data or configuration information you " +"can't afford to lose. The upgrade tools and process are quite reliable, but " +"a hardware failure in the middle of an upgrade could result in a severely " +"damaged system." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:28 +msgid "" +"The main things you'll want to back up are the contents of <filename>/etc</" +"filename>, <filename>/var/lib/dpkg</filename>, <filename>/var/lib/aptitude/" +"pkgstates</filename> and the output of <literal>dpkg --get-selections *</" +"literal> (the quotes are important)." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:34 +msgid "" +"The upgrade process itself does not modify anything in the <filename>/home</" +"filename> directory. However, some applications (e.g. parts of the Mozilla " +"suite, and the GNOME and KDE desktop environments) are known to overwrite " +"existing user settings with new defaults when a new version of the " +"application is first started by a user. As a precaution, you may want to " +"make a backup of the hidden files and directories (dotfiles) in users' home " +"directories. This backup may help to restore or recreate the old settings. " +"You may also want to inform users about this." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:44 +msgid "" +"Any package installation operation must be run with superuser privileges, so " +"either login as root or use <command>su</command> or <command>sudo</command> " +"to gain the necessary access rights." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:49 +msgid "" +"The upgrade has a few preconditions; you should check them before actually " +"executing the upgrade." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:55 +msgid "Inform users in advance" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:57 +msgid "" +"It's wise to inform all users in advance of any upgrades you're planning, " +"although users accessing your system via an <command>ssh</command> " +"connection should notice little during the upgrade, and should be able to " +"continue working." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:63 +msgid "" +"If you wish to take extra precautions, back up or unmount users' partitions " +"(<filename>/home</filename>) before upgrading." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:67 +msgid "" +"You will probably have to do a kernel upgrade when upgrading to " +"&releasename;, so a reboot will normally be necessary. Typically, this will " +"be done after the upgrade is finished." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:74 +msgid "Prepare for recovery" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:76 +msgid "" +"Because of the many changes in the kernel between &oldreleasename; and " +"&releasename; regarding drivers, hardware discovery and the naming and " +"ordering of device files, there is a real risk that you may experience " +"problems rebooting your system after the upgrade. A lot of known potential " +"issues are documented in this and the next chapters of these Release Notes." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:83 +msgid "" +"For that reason it makes sense to ensure that you will be able to recover if " +"your system should fail to reboot or, for remotely managed systems, fail to " +"bring up networking." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:88 +msgid "" +"If you are upgrading remotely via an <command>ssh</command> link it is " +"highly recommended that you take the necessary precautions to be able to " +"access the server through a remote serial terminal. There is a chance that, " +"after upgrading the kernel and rebooting, some devices will be renamed (as " +"described in <xref linkend=\"device-reorder\"/> ) and you will have to fix " +"the system configuration through a local console. Also, if the system is " +"rebooted accidentally in the middle of an upgrade there is a chance you will " +"need to recover using a local console." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:98 +msgid "" +"The most obvious thing to try first is to reboot with your old kernel. " +"However, for various reasons documented elsewhere in this document, this is " +"not guaranteed to work." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:103 +msgid "" +"If that fails, you will need an alternative way to boot your system so you " +"can access and repair it. One option is to use a special rescue image or a " +"Linux live CD. After booting from that, you should be able to mount your " +"root file system and <literal>chroot</literal> into it to investigate and " +"fix the problem." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:110 +msgid "" +"Another option we'd like to recommend is to use the <emphasis>rescue mode</" +"emphasis> of the &releasename; Debian Installer. The advantage of using the " +"installer is that you can choose between its many installation methods for " +"one that best suits your situation. For more information, please consult " +"the section Recovering a Broken System in chapter 8 of the <ulink url=" +"\"http://www.debian.org/releases/stable/installmanual\">Installation Guide</" +"ulink> and the <ulink url=\"http://wiki.debian.org/DebianInstaller/FAQ" +"\">Debian Installer FAQ</ulink>." +msgstr "" + +# type: Content of: <chapter><section><section><section><title> +#: en/upgrading.dbk:120 +msgid "Debug shell during boot using initrd" +msgstr "" + +# type: Content of: <chapter><section><section><section><para><footnote> +#: en/upgrading.dbk:122 +msgid "" +"The <systemitem role=\"package\">initramfs-tools</systemitem> includes a " +"debug shell<footnote>" +msgstr "" + +# type: Content of: <chapter><section><section><section><para><footnote><para> +#: en/upgrading.dbk:123 +msgid "" +"This feature can be disabled by adding the parameter <literal>panic=0</" +"literal> to your boot parameters." +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:124 +msgid "" +"</footnote> in the initrds it generates. If for example the initrd is " +"unable to mount your root file system, you will be dropped into this debug " +"shell which has basic commands available to help trace the problem and " +"possibly fix it." +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:130 +msgid "" +"Basic things to check are: presence of correct device files in <filename>/" +"dev</filename>; what modules are loaded (<literal>cat /proc/modules</" +"literal>); output of <command>dmesg</command> for errors loading drivers. " +"The output of <command>dmesg</command> will also show what device files have " +"been assigned to which disks; you should check that against the output of " +"<literal>echo $ROOT</literal> to make sure that the root file system is on " +"the expected device." +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:139 +msgid "" +"If you do manage to fix the problem, typing <literal>exit</literal> will " +"quit the debug shell and continue the boot process at the point it failed. " +"Of course you will also need to fix the underlying problem and regenerate " +"the initrd so the next boot won't fail again." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:149 +msgid "Prepare a safe environment for the upgrade" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:151 +msgid "" +"The distribution upgrade should be done either locally from a textmode " +"virtual console (or a directly connected serial terminal), or remotely via " +"an <command>ssh</command> link." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:156 +msgid "" +"In order to gain extra safety margin when upgrading remotely, we suggest " +"that you run upgrade processes in the virtual console provided by the " +"<command>screen</command> program, which enables safe reconnection and " +"ensures the upgrade process is not interrupted even if the remote connection " +"process fails." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:163 +msgid "" +"<emphasis role=\"strong\">Important!</emphasis> You should <emphasis>not</" +"emphasis> upgrade using <command>telnet</command>, <command>rlogin</" +"command>, <command>rsh</command>, or from an X session managed by " +"<command>xdm</command>, <command>gdm</command> or <command>kdm</command> etc " +"on the machine you are upgrading. That is because each of those services " +"may well be terminated during the upgrade, which can result in an " +"<emphasis>inaccessible</emphasis> system that is only half-upgraded." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:177 +msgid "Support for 2.2-kernels has been dropped" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:179 +msgid "" +"In case you run a kernel prior to 2.4.1, you need to upgrade to (at least) " +"the 2.4-series before upgrading <systemitem role=\"package\">glibc</" +"systemitem>. This should be done before starting the upgrade. It is " +"recommended that you directly upgrade to the 2.6.8 kernel available in " +"&oldreleasename;, instead of upgrading to a 2.4 kernel." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/upgrading.dbk:190 +msgid "Checking system status" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:192 +msgid "" +"The upgrade process described in this chapter has been designed for upgrades " +"from pure &oldreleasename; systems without third-party packages. In " +"particular, there are known problems with third-party packages which install " +"programs under <filename>/usr/X11R6/bin/</filename> causing problems with " +"upgrades due to the X.Org transition (<xref linkend=\"xorg\"/> ). For " +"greatest reliability of the upgrade process, you may wish to remove third-" +"party packages from your system before you begin upgrading." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:201 +msgid "" +"This procedure also assumes your system has been updated to the latest point " +"release of &oldreleasename;. If you have not done this or are unsure, " +"follow the instructions in <xref linkend=\"old-upgrade\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:206 +msgid "Review actions pending in package manager" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:208 +msgid "" +"In some cases, the use of <command>apt-get</command> for installing packages " +"instead of <command>aptitude</command> might make <command>aptitude</" +"command> consider a package as unused and schedule it for removal. In " +"general, you should make sure the system is fully up-to-date and clean " +"before proceeding with the upgrade." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:215 +msgid "" +"Because of this you should review if there are any pending actions in the " +"package manager <command>aptitude</command>. If a package is scheduled for " +"removal or update in the package manager, it might negatively impact the " +"upgrade procedure. Note that correcting this is only possible if your " +"<filename>sources.list</filename> still points to <emphasis>&oldreleasename;" +"</emphasis>; and not to <emphasis>stable</emphasis> or " +"<emphasis>&releasename;</emphasis>; see <xref linkend=\"old-sources\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:224 +msgid "" +"To do this, you have to run <command>aptitude</command>'s user interface and " +"press 'g' (Go). If it shows any actions, you should review them and either " +"fix them or implement the suggested actions. If no actions are suggested " +"you will be presented with a message saying No packages are scheduled to be " +"installed, removed, or upgraded." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:233 +msgid "Disabling APT pinning" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:235 +msgid "" +"If you have configured APT to install certain packages from a distribution " +"other than stable (e.g. from testing), you may have to change your APT " +"pinning configuration (stored in <filename>/etc/apt/preferences</filename>) " +"to allow the upgrade of packages to the versions in the new stable release. " +"Further information on APT pinning can be found in <citerefentry> " +"<refentrytitle>apt_preferences</refentrytitle> <manvolnum>5</manvolnum> </" +"citerefentry>." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:246 +msgid "Checking packages status" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:248 +msgid "" +"Regardless of the method used for upgrading, it is recommended that you " +"check the status of all packages first, and verify that all packages are in " +"an upgradable state. The following command will show any packages which " +"have a status of Half-Installed or Failed-Config, and those with any error " +"status." +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:253 +#, no-wrap +msgid "" +"\n" +"# dpkg --audit\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:257 +msgid "" +"You could also inspect the state of all packages on your system using " +"<command>dselect</command>, <command>aptitude</command>, or with commands " +"such as" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:261 +#, no-wrap +msgid "" +"\n" +"# dpkg -l | pager\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:265 +msgid "or" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:267 +#, no-wrap +msgid "" +"\n" +"# dpkg --get-selections * > ~/curr-pkgs.txt\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:271 +msgid "" +"It is desirable to remove any holds before upgrading. If any package that " +"is essential for the upgrade is on hold, the upgrade will fail." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:275 +msgid "" +"Note that <command>aptitude</command> uses a different method for " +"registering packages that are on hold than <command>apt-get</command> and " +"<command>dselect</command>. You can identify packages on hold for " +"<command>aptitude</command> with" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:280 +#, no-wrap +msgid "" +"\n" +"# aptitude search ~ahold | grep ^.h\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:284 +msgid "" +"If you want to check which packages you had on hold for <command>apt-get</" +"command>, you should use" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:287 +#, no-wrap +msgid "" +"\n" +"# dpkg --get-selections | grep hold\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:291 +msgid "" +"If you changed and recompiled a package locally, and didn't rename it or put " +"an epoch in the version, you must put it on hold to prevent it from being " +"upgraded." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:296 +msgid "" +"The hold package state for <command>aptitude</command> can be changed using:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:298 +#, no-wrap +msgid "" +"\n" +"# aptitude hold <replaceable>package_name</replaceable>\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:302 +msgid "" +"Replace <literal>hold</literal> with <literal>unhold</literal> to unset the " +"hold state." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:306 +msgid "" +"If there is anything you need to fix, it is best to make sure your " +"<filename>sources.list</filename> still refers to &oldreleasename; as " +"explained in <xref linkend=\"old-sources\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:313 +msgid "Unofficial sources and backports" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:315 +msgid "" +"If you have any non-Debian packages on your system, you should be aware that " +"these may be removed during the upgrade because of conflicting " +"dependencies. If these packages were installed by adding an extra package " +"archive in your <filename>/etc/apt/sources.list</filename>, you should check " +"if that archive also offers packages compiled for &releasename; and change " +"the source line accordingly at the same time as your source lines for Debian " +"packages." +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote> +#: en/upgrading.dbk:323 +msgid "" +"Some users may have unofficial backported newer versions of packages that " +"<emphasis>are</emphasis> in Debian installed on their &oldreleasename; " +"system. Such packages are most likely to cause problems during an upgrade " +"as they may result in file conflicts<footnote>" +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote><para> +#: en/upgrading.dbk:326 +msgid "" +"Debian's package management system normally does not allow a package to " +"remove or replace a file owned by another package unless it has been defined " +"to replace that package." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:328 +msgid "" +"</footnote>. Section <xref linkend=\"trouble\"/> has some information on " +"how to deal with file conflicts if they should occur." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/upgrading.dbk:337 +msgid "Manually unmarking packages" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:339 +msgid "" +"To prevent <command>aptitude</command> from removing some packages that were " +"pulled in through dependencies, you need to manually unmark them as " +"<emphasis>auto</emphasis> packages. This includes OpenOffice and Vim for " +"desktop installs:" +msgstr "" + +# type: Content of: <chapter><section><screen> +#: en/upgrading.dbk:344 +#, no-wrap +msgid "" +"\n" +"# aptitude unmarkauto openoffice.org vim\n" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:348 +msgid "" +"And 2.6 kernel images if you have installed them using a kernel metapackage:" +msgstr "" + +# type: Content of: <chapter><section><screen> +#: en/upgrading.dbk:350 +#, no-wrap +msgid "" +"\n" +"# aptitude unmarkauto $(dpkg-query -W 'kernel-image-2.6.*' | cut -f1)\n" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:354 +msgid "" +"Note: You can review which packages are marked as <emphasis>auto</emphasis> " +"in aptitude by running:" +msgstr "" + +# type: Content of: <chapter><section><screen> +#: en/upgrading.dbk:357 +#, no-wrap +msgid "" +"\n" +"# aptitude search 'i~M <package name>'\n" +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/upgrading.dbk:363 +msgid "Preparing sources for APT" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:365 +msgid "" +"Before starting the upgrade you must set up <systemitem role=\"package" +"\">apt</systemitem>'s configuration file for package lists, <filename>/etc/" +"apt/sources.list</filename>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:370 +msgid "" +"<systemitem role=\"package\">apt</systemitem> will consider all packages " +"that can be found via any <literal>deb</literal> line, and install the " +"package with the highest version number, giving priority to the first " +"mentioned lines (that way, in case of multiple mirror locations, you'd " +"typically first name a local harddisk, then CD-ROMs, and then HTTP/FTP " +"mirrors)." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:377 +msgid "" +"A release can often be referred to by both its codename (e.g. " +"&oldreleasename;, &releasename;) and by its status name (i.e. oldstable, " +"stable, testing, unstable). Referring to a release by its codename has the " +"advantage that you will never be surprised by a new release and for this " +"reason is the approach taken here. It does of course mean that you will " +"have to watch out for release announcements yourself. If you use the status " +"name instead, you will just see loads of updates for packages available as " +"soon as a release has happened." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:386 +msgid "Adding APT Internet sources" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:388 +msgid "" +"The default configuration is set up for installation from main Debian " +"Internet servers, but you may wish to modify <filename>/etc/apt/sources." +"list</filename> to use other mirrors, preferably a mirror that is network-" +"wise closest to you." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:393 +msgid "" +"Debian HTTP or FTP mirror addresses can be found at <ulink url=\"http://www." +"debian.org/distrib/ftplist\"></ulink> (look at the Full list of mirrors " +"section). HTTP mirrors are generally speedier than FTP mirrors." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:398 +msgid "" +"For example, suppose your closest Debian mirror is <literal>http://mirrors." +"kernel.org/debian/</literal>. When inspecting that mirror with a web " +"browser or FTP program, you will notice that the main directories are " +"organized like this:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:403 +#, no-wrap +msgid "" +"\n" +"http://mirrors.kernel.org/debian/dists/&releasename;/main/binary-i386/...\n" +"http://mirrors.kernel.org/debian/dists/&releasename;/contrib/binary-i386/...\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:408 +msgid "" +"To use this mirror with <command>apt</command>, you add this line to your " +"<filename>sources.list</filename> file:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:411 +#, no-wrap +msgid "" +"\n" +"deb http://mirrors.kernel.org/debian &releasename; main contrib\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:415 en/upgrading.dbk:448 +msgid "" +"Note that the `<literal>dists</literal>' is added implicitly, and the " +"arguments after the release name are used to expand the path into multiple " +"directories." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:419 en/upgrading.dbk:452 +msgid "" +"After adding your new sources, disable the previously existing <literal>deb</" +"literal> lines in <filename>sources.list</filename> by placing a hash sign " +"(<literal>#</literal>) in front of them." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:426 +msgid "Adding APT sources for a local mirror" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:428 +msgid "" +"Instead of using HTTP or FTP packages mirrors, you may wish to modify " +"<filename>/etc/apt/sources.list</filename> to use a mirror on a local disk " +"(possibly mounted over NFS)." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:433 +msgid "" +"For example, your packages mirror may be under <filename>/var/ftp/debian/</" +"filename>, and have main directories like this:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:436 +#, no-wrap +msgid "" +"\n" +"/var/ftp/debian/dists/&releasename;/main/binary-i386/...\n" +"/var/ftp/debian/dists/&releasename;/contrib/binary-i386/...\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:441 +msgid "" +"To use this with <command>apt</command>, add this line to your " +"<filename>sources.list</filename> file:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:444 +#, no-wrap +msgid "" +"\n" +"deb file:/var/ftp/debian &releasename; main contrib\n" +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:459 +msgid "Adding APT source from CD-ROM or DVD" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:461 +msgid "" +"If you want to use CDs <emphasis>only</emphasis>, comment out the existing " +"<literal>deb</literal> lines in <filename>/etc/apt/sources.list</filename> " +"by placing a hash sign (<literal>#</literal>) in front of them." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:466 +msgid "" +"Make sure there is a line in <filename>/etc/fstab</filename> that enables " +"mounting your CD-ROM drive at the <filename>/cdrom</filename> mount point " +"(the exact <filename>/cdrom</filename> mount point is required for " +"<command>apt-cdrom</command>). For example, if <filename>/dev/hdc</" +"filename> is your CD-ROM drive, <filename>/etc/fstab</filename> should " +"contain a line like:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:473 +#, no-wrap +msgid "" +"\n" +"/dev/hdc /cdrom auto defaults,noauto,ro 0 0\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:477 +msgid "" +"Note that there must be <emphasis>no spaces</emphasis> between the words " +"<literal>defaults,noauto,ro</literal> in the fourth field." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:481 +msgid "To verify it works, insert a CD and try running" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:483 +#, no-wrap +msgid "" +"\n" +"# mount /cdrom # this will mount the CD to the mount point\n" +"# ls -alF /cdrom # this should show the CD's root directory\n" +"# umount /cdrom # this will unmount the CD\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:489 +msgid "Next, run:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:491 +#, no-wrap +msgid "" +"\n" +"# apt-cdrom add\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:495 +msgid "" +"for each Debian Binary CD-ROM you have, to add the data about each CD to " +"APT's database." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/upgrading.dbk:503 +msgid "Upgrading packages" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:505 +msgid "" +"The recommended way to upgrade from previous &debian; releases is to use the " +"package management tool <command>aptitude</command>. This program makes " +"safer decisions about package installations than running <command>apt-get</" +"command> directly." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:511 +msgid "" +"Don't forget to mount all needed partitions (notably the root and <filename>/" +"usr</filename> partitions) read-write, with a command like:" +msgstr "" + +# type: Content of: <chapter><section><screen> +#: en/upgrading.dbk:514 +#, no-wrap +msgid "" +"\n" +"# mount -o remount,rw /<replaceable>mountpoint</replaceable>\n" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:518 +msgid "" +"Next you should double-check that the APT source entries (in <filename>/etc/" +"apt/sources.list</filename>) refer either to <literal>&releasename;</" +"literal> or to <literal>stable</literal>. There should not be any sources " +"entries pointing to &oldreleasename;. Note: source lines for a CD-ROM will " +"often refer to <literal>unstable</literal>; although this may be confusing, " +"you should <emphasis>not</emphasis> change it." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:526 +msgid "Recording the session" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:528 +msgid "" +"It is strongly recommended that you use the <command>/usr/bin/script</" +"command> program to record a transcript of the upgrade session. Then if a " +"problem occurs, you will have a log of what happened, and if needed, can " +"provide exact information in a bug report. To start the recording, type:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:533 +#, no-wrap +msgid "" +"\n" +"# script -t 2>~/upgrade-&releasename;.time -a ~/upgrade-&releasename;.script\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:537 +msgid "" +"or similar. Do not put the typescript file in a temporary directory such as " +"<filename>/tmp</filename> or <filename>/var/tmp</filename> (files in those " +"directories may be deleted during the upgrade or during any restart)." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:542 +msgid "" +"The typescript will also allow you to review information that has scrolled " +"off-screen. Just switch to VT2 (using <literal>Alt-F2</literal>) and, after " +"logging in, use <literal>less -R ~root/upgrade-&releasename;.script</" +"literal> to view the file." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:548 +msgid "" +"After you have completed the upgrade, you can stop <command>script</command> " +"by typing <literal>exit</literal> at the prompt." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:554 +msgid "" +"If you have used the <emphasis>-t</emphasis> switch for <command>script</" +"command> you can use the <command>scriptreplay</command> program to replay " +"the whole session:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:558 +#, no-wrap +msgid "" +"\n" +"# scriptreplay ~/upgrade-&releasename;.time ~/upgrade-&releasename;.script\n" +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:564 +msgid "Updating the package list" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:566 +msgid "" +"First the list of available packages for the new release needs to be " +"fetched. This is done by executing:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:569 en/upgrading.dbk:893 +#, no-wrap +msgid "" +"\n" +"# aptitude update\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:573 +msgid "" +"Running this the first time new sources are updated will print out some " +"warnings related to the availability of the sources. These warnings are " +"harmless and will not appear if you rerun the command again." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:580 +msgid "Make sure you have sufficient space for the upgrade" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:582 +msgid "" +"You have to make sure before upgrading your system that you have sufficient " +"hard disk space when you start the full system upgrade described in <xref " +"linkend=\"upgrading-other\"/> . First, any package needed for installation " +"that is fetched from the network is stored in <filename>/var/cache/apt/" +"archives</filename> (and the <filename>partial/</filename> subdirectory, " +"during download), so you must make sure you have enough space on the file " +"system partition that holds <filename>/var/</filename> to temporarily " +"download the packages that will be installed in your system. After the " +"download, you will probably need more space in other file system partitions " +"in order to both install upgraded packages (which might contain bigger " +"binaries or more data) and new packages that will be pulled in for the " +"upgrade. If your system does not have sufficient space you might end up " +"with an incomplete upgrade that might be difficult to recover from." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:598 +msgid "" +"Both <command>aptitude</command> and <command>apt</command> will show you " +"detailed information of the disk space needed for the installation. Before " +"executing the upgrade, you can see this estimate by running:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:602 +#, no-wrap +msgid "" +"\n" +"# aptitude -y -s -f --with-recommends dist-upgrade\n" +"[ ... ]\n" +"XXX upgraded, XXX newly installed, XXX to remove and XXX not upgraded.\n" +"Need to get xx.xMB/yyyMB of archives. After unpacking AAAMB will be used.\n" +"Would download/install/remove packages.\n" +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote> +#: en/upgrading.dbk:610 +msgid "<footnote>" +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote><para> +#: en/upgrading.dbk:610 +msgid "" +"Running this command at the beginning of the upgrade process may give an " +"error, for the reasons described in the next sections. In that case you " +"will need to wait until you've done the minimal system upgrade as in <xref " +"linkend=\"minimal-upgrade\"/> and upgraded your kernel as in <xref linkend=" +"\"upgrading-kernel\"/> before running this command to estimate the disk " +"space." +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:615 en/upgrading.dbk:784 +msgid "</footnote>" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:618 +msgid "" +"If you do not have enough space for the upgrade, make sure you free up space " +"beforehand. You can:" +msgstr "" + +# type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:624 +msgid "" +"Remove packages that have been previously downloaded for installation (at " +"<filename>/var/cache/apt/archive</filename>). Cleaning up the package cache " +"by running <command>apt-get clean</command> or <command>aptitude clean</" +"command> will remove all previously downloaded package files." +msgstr "" + +# type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:632 +msgid "" +"Remove old packages you no longer use. If you have <command>popularity-" +"contest</command> installed, you can use <command>popcon-largest-unused</" +"command> to list the packages you do not use in the system that occupy the " +"most space. You can also use <command>deborphan</command> or " +"<command>debfoster</command> to find obsolete packages (see <xref linkend=" +"\"obsolete\"/> ). Alternatively you can start <command>aptitude</command> " +"in visual mode and find obsolete packages under Obsolete and Locally Created " +"Packages." +msgstr "" + +# type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:644 +msgid "" +"Remove packages taking up too much space, which are not currently needed " +"(you can always reinstall them after the upgrade). You can list the " +"packages that take up most of the disk space with <command>dpigs</command> " +"(available in the <systemitem role=\"package\">debian-goodies</systemitem> " +"package) or with <command>wajig</command> (running <literal>wajig size</" +"literal>)." +msgstr "" + +# type: Content of: <chapter><section><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:662 +msgid "" +"Temporarily move to another system, or permanently remove, system logs " +"residing under <filename>/var/log/</filename>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:668 +msgid "" +"Note that in order to safely remove packages, it is advisable to switch your " +"<filename>sources.list</filename> back to &oldreleasename; as described in " +"<xref linkend=\"old-sources\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:675 +msgid "Minimal system upgrade" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:677 +msgid "" +"Because of certain necessary package conflicts between &oldreleasename; and " +"&releasename;, running <literal>aptitude dist-upgrade</literal> directly " +"will often remove large numbers of packages that you will want to keep. We " +"therefore recommend a two-part upgrade process, first a minimal upgrade to " +"overcome these conflicts, then a full <literal>dist-upgrade</literal>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:684 +msgid "First, run:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:686 +#, no-wrap +msgid "" +"\n" +"# aptitude upgrade\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:690 +msgid "" +"This has the effect of upgrading those packages which can be upgraded " +"without requiring any other packages to be removed or installed." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:694 +msgid "Follow the minimal upgrade with:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:696 +#, no-wrap +msgid "" +"\n" +"# aptitude install initrd-tools\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:700 +msgid "" +"This step will automatically upgrade <systemitem role=\"package\">libc6</" +"systemitem> and <systemitem role=\"package\">locales</systemitem> and will " +"pull in SELinux support libraries (<systemitem role=\"package\">libselinux1</" +"systemitem>). At this point, some running services will be restarted, " +"including <command>xdm</command>, <command>gdm</command> and <command>kdm</" +"command>. As a consequence, local X11 sessions will be disconnected." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:709 +msgid "" +"The next step will vary depending on the set of packages that you have " +"installed. These release notes give general advice about which method " +"should be used, but if in doubt, it is recommended that you examine the " +"package removals proposed by each method before proceeding." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:715 +msgid "" +"Some common packages that are expected to be removed include <systemitem " +"role=\"package\">base-config</systemitem>, <systemitem role=\"package" +"\">hotplug</systemitem>, <systemitem role=\"package\">xlibs</systemitem>, " +"<systemitem role=\"package\">netkit-inetd</systemitem>, <systemitem role=" +"\"package\">python2.3</systemitem>, <systemitem role=\"package\">xfree86-" +"common</systemitem>, and <systemitem role=\"package\">xserver-common</" +"systemitem>. For a more complete list of packages obsoleted in " +"&releasename;, see <xref linkend=\"obsolete\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><section><title> +#: en/upgrading.dbk:726 +msgid "Upgrading a desktop system" +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:728 +msgid "" +"This upgrade path has been verified to work on systems with the " +"&oldreleasename; <literal>desktop</literal> task installed. It is probably " +"the method that will give the best results on systems with the " +"<literal>desktop</literal> task installed, or with the <literal>gnome</" +"literal> or <literal>kde</literal> packages installed." +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:735 +msgid "" +"It is probably <emphasis>not</emphasis> the correct method to use if you do " +"not already have the <systemitem role=\"package\">libfam0c102</systemitem> " +"and <systemitem role=\"package\">xlibmesa-glu</systemitem> packages " +"installed:" +msgstr "" + +# type: Content of: <chapter><section><section><section><screen> +#: en/upgrading.dbk:739 en/upgrading.dbk:771 +#, no-wrap +msgid "" +"\n" +"# dpkg -l libfam0c102 | grep ^ii\n" +"# dpkg -l xlibmesa-glu | grep ^ii\n" +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:744 +msgid "If you do have a full desktop system installed, run:" +msgstr "" + +# type: Content of: <chapter><section><section><section><screen> +#: en/upgrading.dbk:746 +#, no-wrap +msgid "" +"\n" +"# aptitude install libfam0 xlibmesa-glu\n" +msgstr "" + +# type: Content of: <chapter><section><section><section><title> +#: en/upgrading.dbk:752 +msgid "Upgrading a system with some X packages installed" +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:754 +msgid "" +"Systems with some X packages installed, but not the full <literal>desktop</" +"literal> task, require a different method. This method applies in general " +"to systems with <systemitem role=\"package\">xfree86-common</systemitem> " +"installed, including some server systems which have <systemitem role=" +"\"package\">tasksel</systemitem> server tasks installed as some of these " +"tasks include graphical management tools. It is likely the correct method " +"to use on systems which run X, but do not have the full <literal>desktop</" +"literal> task installed." +msgstr "" + +# type: Content of: <chapter><section><section><section><screen> +#: en/upgrading.dbk:763 +#, no-wrap +msgid "" +"\n" +"# dpkg -l xfree86-common | grep ^ii\n" +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:767 +msgid "" +"First, check whether you have the <systemitem role=\"package\">libfam0c102</" +"systemitem> and <systemitem role=\"package\">xlibmesa-glu</systemitem> " +"packages installed." +msgstr "" + +# type: Content of: <chapter><section><section><section><para><footnote> +#: en/upgrading.dbk:776 +msgid "" +"If you do not have <systemitem role=\"package\">libfam0c102</systemitem> " +"installed, do not include <systemitem role=\"package\">libfam0</systemitem> " +"in the following commandline. If you do not have <systemitem role=\"package" +"\">xlibmesa-glu</systemitem> installed, do not include it in the following " +"commandline. <footnote>" +msgstr "" + +# type: Content of: <chapter><section><section><section><para><footnote><para> +#: en/upgrading.dbk:780 +msgid "" +"This command will determine whether you need libfam0 and xlibmesa-glu " +"installed, and auto-select them for you:" +msgstr "" + +# type: Content of: <chapter><section><section><section><para><footnote><screen> +#: en/upgrading.dbk:782 +#, no-wrap +msgid "" +" # aptitude install x11-common \\ $(dpkg-query --showformat\n" +"'${Package} ${Status}\\n' -W libfam0c102 xlibmesa-glu \\ | grep 'ok installed$' |\n" +"sed -e's/ .*//; s/c102//') " +msgstr "" + +# type: Content of: <chapter><section><section><section><screen> +#: en/upgrading.dbk:786 +#, no-wrap +msgid "" +"\n" +"# aptitude install x11-common <replaceable>libfam0</replaceable> <replaceable>xlibmesa-glu</replaceable>\n" +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:790 +msgid "" +"Note that installing <systemitem role=\"package\">libfam0</systemitem> will " +"also install the File Alteration Monitor (<systemitem role=\"package\">fam</" +"systemitem>) as well as the RPC portmapper (<systemitem role=\"package" +"\">portmap</systemitem>) if not already available in your system. Both " +"packages will enable a new network service in the system although they can " +"both be configured to be bound to the (internal) loopback network device." +msgstr "" + +# type: Content of: <chapter><section><section><section><title> +#: en/upgrading.dbk:800 +msgid "Upgrading a system with no X support installed" +msgstr "" + +# type: Content of: <chapter><section><section><section><para> +#: en/upgrading.dbk:802 +msgid "" +"On a system with no X, no additional <literal>aptitude install</literal> " +"command should be required, and you can move on to the next step." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:810 +msgid "Upgrading the kernel" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:812 +msgid "" +"The <systemitem role=\"package\">udev</systemitem> version in &releasename; " +"does not support kernel versions earlier than 2.6.15 (which includes " +"&oldreleasename; 2.6.8 kernels), and the <systemitem role=\"package\">udev</" +"systemitem> version in &oldreleasename; will not work properly with the " +"latest kernels. In addition, installing the &releasename; version of " +"<systemitem role=\"package\">udev</systemitem> will force the removal of " +"<systemitem role=\"package\">hotplug</systemitem>, used by Linux 2.4 kernels." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:821 +msgid "" +"As a consequence, the previous kernel package will probably not boot " +"properly after this upgrade. Similarly, there is a time window during the " +"upgrade in which <systemitem role=\"package\">udev</systemitem> has been " +"upgraded but the latest kernel has not been installed. If the system were " +"to be rebooted at this point, in the middle of the upgrade, it might not be " +"bootable because of drivers not being properly detected and loaded. (See " +"<xref linkend=\"upgrade-preparations\"/> for recommendations on preparing " +"for this possibility if you are upgrading remotely.)" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:831 +msgid "" +"Unless your system has the <literal>desktop</literal> task installed, or " +"other packages that would cause an unacceptable number of package removals, " +"it is therefore recommended that you upgrade the kernel on its own at this " +"point." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:836 +msgid "To proceed with this kernel upgrade, run:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:838 +#, no-wrap +msgid "" +"\n" +"# aptitude install linux-image-2.6-<replaceable>flavor</replaceable>\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:842 +msgid "" +"See <xref linkend=\"kernel-metapackage\"/> for help in determining which " +"flavor of kernel package you should install." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:846 +msgid "" +"In the desktop case, it is unfortunately not possible to ensure the new " +"kernel package is installed immediately after the new <systemitem role=" +"\"package\">udev</systemitem> is installed, so there is a window of unknown " +"length when your system will have no kernel installed with full hotplug " +"support. See <xref linkend=\"newkernel\"/> for information on configuring " +"your system to not depend on hotplug for booting." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:856 +msgid "Upgrading the rest of the system" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:858 +msgid "" +"You are now ready to continue with the main part of the upgrade. Execute:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:860 +#, no-wrap +msgid "" +"\n" +"# aptitude dist-upgrade\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:864 +msgid "" +"This will perform a complete upgrade of the system, i.e. install the newest " +"available versions of all packages, and resolve all possible dependency " +"changes between packages in different releases. If necessary, it will " +"install some new packages (usually new library versions, or renamed " +"packages), and remove any conflicting obsoleted packages." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:871 +msgid "" +"When upgrading from a set of CD-ROMs, you will be asked to insert specific " +"CDs at several points during the upgrade. You might have to insert the same " +"CD multiple times; this is due to inter-related packages that have been " +"spread out over the CDs." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:877 +msgid "" +"New versions of currently installed packages that cannot be upgraded without " +"changing the install status of another package will be left at their current " +"version (displayed as held back). This can be resolved by either using " +"<command>aptitude</command> to choose these packages for installation or by " +"trying <literal>aptitude -f install <replaceable>package</replaceable></" +"literal>." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:887 +msgid "Getting package signatures" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:889 +msgid "" +"After the upgrade, with the new version of <command>apt</command> you can " +"now update your package information, which will include the new package " +"signature checking mechanism:" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:897 +msgid "" +"The upgrade will have already retrieved and enabled the signing keys for " +"Debian's package archives. If you add other (unofficial) package sources, " +"<command>apt</command> will print warnings related to its inability to " +"confirm that packages downloaded from them are legitimate and have not been " +"tampered with. For more information please see <xref linkend=\"pkgmgmt\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:904 +msgid "" +"You will notice that, since you are using the new version of <command>apt</" +"command>, it will download package differences files (<literal>pdiff</" +"literal>) instead of the full package index list. For more information on " +"this feature please read <xref linkend=\"apt-pdiff\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:912 +msgid "Possible issues during upgrade" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:914 +msgid "" +"If an operation using <command>aptitude</command>, <command>apt-get</" +"command>, or <command>dpkg</command> fails with the error" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:917 +#, no-wrap +msgid "" +"\n" +"E: Dynamic MMap ran out of room\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:921 +msgid "" +"the default cache space is insufficient. You can solve this by either " +"removing or commenting lines you don't need in <filename>/etc/apt/sources." +"list</filename> or by increasing the cache size. The cache size can be " +"increased by setting <literal>APT::Cache-Limit</literal> in <filename>/etc/" +"apt/apt.conf</filename>. The following command will set it to a value that " +"should be sufficient for the upgrade:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:928 +#, no-wrap +msgid "" +"\n" +"# echo 'APT::Cache-Limit 12500000;' >> /etc/apt/apt.conf\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:932 +msgid "This assumes that you do not yet have this variable set in that file." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:935 +msgid "" +"Sometimes it's necessary to enable the <literal>APT::Force-LoopBreak</" +"literal> option in APT to be able to temporarily remove an essential package " +"due to a Conflicts/Pre-Depends loop. <command>aptitude</command> will alert " +"you of this and abort the upgrade. You can work around that by specifying " +"<literal>-o APT::Force-LoopBreak=1</literal> option on <command>aptitude</" +"command> command line." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:943 +msgid "" +"It is possible that a system's dependency structure can be so corrupt as to " +"require manual intervention. Usually this means using <command>aptitude</" +"command> or" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:947 +#, no-wrap +msgid "" +"\n" +"# dpkg --remove <replaceable>package_name</replaceable>\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:951 +msgid "to eliminate some of the offending packages, or" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:953 +#, no-wrap +msgid "" +"\n" +"# aptitude -f install\n" +"# dpkg --configure --pending\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:958 +msgid "" +"In extreme cases you might have to force re-installation with a command like" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:960 +#, no-wrap +msgid "" +"\n" +"# dpkg --install <replaceable>/path/to/package_name.deb</replaceable>\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:964 +msgid "" +"File conflicts should not occur if you upgrade from a pure &oldreleasename; " +"system, but can occur if you have unofficial backports installed. A file " +"conflict will result in an error like:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:968 +#, no-wrap +msgid "" +"\n" +"Unpacking <replaceable><package-foo></replaceable> (from <replaceable><package-foo-file></replaceable>) ...\n" +"dpkg: error processing <replaceable><package-foo></replaceable> (--install):\n" +" trying to overwrite `<replaceable><some-file-name></replaceable>',\n" +" which is also in package <replaceable><package-bar></replaceable>\n" +"dpkg-deb: subprocess paste killed by signal (Broken pipe)\n" +" Errors were encountered while processing:\n" +" <replaceable><package-foo></replaceable>\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:978 +msgid "" +"You can try to solve a file conflict by forcibly removing the package " +"mentioned on the <emphasis>last</emphasis> line of the error message:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:981 +#, no-wrap +msgid "" +"\n" +"# dpkg -r --force-depends <replaceable>package_name</replaceable>\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:985 +msgid "" +"After fixing things up, you should be able to resume the upgrade by " +"repeating the previously described <literal>aptitude</literal> commands." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:989 +msgid "" +"During the upgrade, you will be asked questions regarding the configuration " +"or re-configuration of several packages. When you are asked if any file in " +"the <filename>/etc/init.d</filename> or <filename>/etc/terminfo</filename> " +"directories, or the <filename>/etc/manpath.config</filename> file should be " +"replaced by the package maintainer's version, it's usually necessary to " +"answer `yes' to ensure system consistency. You can always revert to the old " +"versions, since they will be saved with a <literal>.dpkg-old</literal> " +"extension." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:998 +msgid "" +"If you're not sure what to do, write down the name of the package or file " +"and sort things out at a later time. You can search in the typescript file " +"to review the information that was on the screen during the upgrade." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/upgrading.dbk:1007 +msgid "Upgrading your kernel and related packages" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1009 +msgid "" +"This section explains how to upgrade your kernel and identifies potential " +"issues related to this upgrade. You can either install one of the " +"<systemitem role=\"package\">linux-image-*</systemitem> packages provided by " +"Debian, or compile a customized kernel from source." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1015 +msgid "" +"Note that a lot of information in this section is based on the assumption " +"that you will be using one of the modular Debian kernels, together with " +"<systemitem role=\"package\">initramfs-tools</systemitem> and <systemitem " +"role=\"package\">udev</systemitem>. If you choose to use a custom kernel " +"that does not require an initrd or if you use a different initrd generator, " +"some of the information may not be relevant for you." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1023 +msgid "" +"Note also that if <systemitem role=\"package\">udev</systemitem> is " +"<emphasis>not</emphasis> installed on your system, it is still possible to " +"use <systemitem role=\"package\">hotplug</systemitem> for hardware discovery." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1028 +msgid "" +"If you are currently using a 2.4 kernel, you should also read <xref linkend=" +"\"upgrade-to-2.6\"/> carefully." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:1032 +msgid "Installing the kernel metapackage" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1034 +msgid "" +"When you dist-upgrade from &oldreleasename; to &releasename;, it is strongly " +"recommended that you install a new linux-image-2.6-* metapackage. This " +"package may be installed automatically by the dist-upgrade process. You can " +"verify this by running:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:1038 +#, no-wrap +msgid "" +"\n" +"# dpkg -l linux-image* | grep ^ii\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1042 +msgid "" +"If you do not see any output, then you will need to install a new linux-" +"image package by hand. To see a list of available linux-image-2.6 " +"metapackages, run:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:1045 +#, no-wrap +msgid "" +"\n" +"# apt-cache search linux-image-2.6- | grep -v transition\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1049 +msgid "" +"If you are unsure about which package to select, run <literal>uname -r</" +"literal> and look for a package with a similar name. For example, if you " +"see '2.4.27-3-686', it is recommended that you install <systemitem role=" +"\"package\">linux-image-2.6-686</systemitem>. (Note that the 386 flavor no " +"longer exists; if you are currently using the 386 kernel flavor, you should " +"install the 486 flavor instead.) You may also use <command>apt-cache</" +"command> to see a long description of each package in order to help choose " +"the best one available. For example:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:1058 +#, no-wrap +msgid "" +"\n" +"# apt-cache show linux-image-2.6-686\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1062 +msgid "" +"You should then use <literal>aptitude install</literal> to install it. Once " +"this new kernel is installed you should reboot at the next available " +"opportunity to get the benefits provided by the new kernel version." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1067 +msgid "" +"For the more adventurous there is an easy way to compile your own custom " +"kernel on &debian;. Install the <systemitem role=\"package\">kernel-" +"package</systemitem> tool and read the documentation in <filename>/usr/share/" +"doc/kernel-package</filename>." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:1075 +msgid "Upgrading from a 2.6 kernel" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1077 +msgid "" +"If you are currently running a 2.6 series kernel from &oldreleasename; this " +"upgrade will take place automatically after you do a full upgrade of the " +"system packages (as described in <xref linkend=\"upgradingpackages\"/> )." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1082 +msgid "" +"If possible, it is to your advantage to upgrade the kernel package " +"separately from the main <literal>dist-upgrade</literal> to reduce the " +"chances of a temporarily non-bootable system. See <xref linkend=\"upgrading-" +"kernel\"/> for a description of this process. Note that this should only be " +"done after the minimal upgrade process described in <xref linkend=\"minimal-" +"upgrade\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1089 +msgid "" +"You can also take this step if you are using your own custom kernel and want " +"to use the kernel available in &releasename;. If your kernel version is not " +"supported by <systemitem role=\"package\">udev</systemitem> then it is " +"recommended that you upgrade after the minimal upgrade. If your version is " +"supported by <systemitem role=\"package\">udev</systemitem> you can safely " +"wait until after the full system upgrade." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:1099 +msgid "Upgrading from a 2.4 kernel" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1101 +msgid "" +"If you have a 2.4 kernel installed, and your system relies on <systemitem " +"role=\"package\">hotplug</systemitem> for its hardware detection you should " +"first upgrade to a 2.6 series kernel from &oldreleasename; before attempting " +"the upgrade. Make sure that the 2.6 series kernel boots your system and all " +"your hardware is properly detected before you perform the upgrade. The " +"<systemitem role=\"package\">hotplug</systemitem> package is removed from " +"the system (in favor of <systemitem role=\"package\">udev</systemitem>) when " +"you do a full system upgrade. If you do not do the kernel upgrade before " +"this your system might not boot up properly from this point on. Once you " +"have done an upgrade to a 2.6 series kernel in &oldreleasename; you can do a " +"kernel upgrade as described in <xref linkend=\"upgrade-from-2.6\"/> ." +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote> +#: en/upgrading.dbk:1114 +msgid "" +"If your system does not rely on <systemitem role=\"package\">hotplug</" +"systemitem><footnote>" +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote><para> +#: en/upgrading.dbk:1115 +msgid "" +"You can have the kernel modules needed by your system loaded statically " +"through proper configuration of <filename>/etc/modules</filename>" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1117 +msgid "" +"</footnote> you can delay the kernel upgrade to after you have done a full " +"system upgrade, as described in <xref linkend=\"upgrading-other\"/> . Once " +"your system has been upgraded you can then do the following (changing the " +"kernel package name to the one most suited to your system by substituting " +"<emphasis><flavor></emphasis>):" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:1123 +#, no-wrap +msgid "" +"\n" +"# aptitude install linux-image-2.6-<flavor>\n" +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:1129 +msgid "Device enumeration reordering" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1131 +msgid "" +"&releasename; features a more robust mechanism for hardware discovery than " +"previous releases. However, this may cause changes in the order devices are " +"discovered on your system, affecting the order in which device names are " +"assigned. For example, if you have two network adapters that are associated " +"with two different drivers, the devices eth0 and eth1 refer to may be " +"swapped. Please note that the new mechanism means that if you e.g. " +"exchange ethernet adapters in a running &releasename; system, the new " +"adapter will also get a new interface name." +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote> +#: en/upgrading.dbk:1140 +msgid "" +"For network devices, you can avoid this reordering by using <systemitem role=" +"\"package\">udev</systemitem> rules, more specifically, through the " +"definitions at <filename>/etc/udev/rules.d/z25_persistent-net.rules</" +"filename><footnote>" +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote><para> +#: en/upgrading.dbk:1144 +msgid "" +"The rules there are automatically generated by the script <filename>/etc/" +"udev/rules.d/z45_persistent-net-generator.rules</filename> to have " +"persistent names for network interfaces. Delete this symlink to disable " +"persistent device naming for NICs by <systemitem role=\"package\">udev</" +"systemitem>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1148 +msgid "" +"</footnote>. Alternatively you can use the <command>ifrename</command> " +"utility to bind physical devices to specific names at boot time. See " +"<citerefentry> <refentrytitle>ifrename</refentrytitle> <manvolnum>8</" +"manvolnum> </citerefentry> and <citerefentry> <refentrytitle>iftab</" +"refentrytitle> <manvolnum>5</manvolnum> </citerefentry> for more " +"information. The two alternatives (<systemitem role=\"package\">udev</" +"systemitem> and <command>ifrename</command>) should not be used at the same " +"time." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1158 +msgid "" +"For storage devices, you can avoid this reordering by using <systemitem role=" +"\"package\">initramfs-tools</systemitem> and configuring it to load storage " +"device driver modules in the same order they are currently loaded. To do " +"this, identify the order the storage modules on your system were loaded by " +"looking at the output of <command>lsmod</command>. <command>lsmod</command> " +"lists modules in the reverse order that they were loaded in, i.e., the first " +"module in the list was the last one loaded. Note that this will only work " +"for devices which the kernel enumerates in a stable order (like PCI devices)." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1168 +msgid "" +"However, removing and reloading modules after initial boot will affect this " +"order. Also, your kernel may have some drivers linked statically, and these " +"names will not appear in the output of <command>lsmod</command>. You may be " +"able to decipher these driver names and load order from looking at " +"<filename>/var/log/kern.log</filename>, or the output of <command>dmesg</" +"command>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1176 +msgid "" +"Add these module names to <filename>/etc/initramfs-tools/modules</filename> " +"in the order they should be loaded at boot time. Some module names may have " +"changed between &oldreleasename; and &releasename;. For example, " +"sym53c8xx_2 has become sym53c8xx." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1181 +msgid "" +"You will then need to regenerate your initramfs image(s) by executing " +"<literal>update-initramfs -u -k all</literal>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1185 +msgid "" +"Once you are running a &releasename; kernel and <systemitem role=\"package" +"\">udev</systemitem>, you may reconfigure your system to access disks by an " +"alias that is not dependent upon driver load order. These aliases reside in " +"the <filename>/dev/disk/</filename> hierarchy." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:1193 +msgid "Boot timing issues" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1195 +msgid "" +"If an initrd created with <systemitem role=\"package\">initramfs-tools</" +"systemitem> is used to boot the system, in some cases the creation of device " +"files by <systemitem role=\"package\">udev</systemitem> can happen too late " +"for the boot scripts to act on." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1202 +msgid "" +"The usual symptoms are that the boot will fail because the root file system " +"cannot be mounted and you are dropped into a debug shell, but that when you " +"check afterwards, all devices that are needed are present in <filename>/dev</" +"filename>. This has been observed in cases where the root file system is on " +"a USB disk or on RAID, especially if lilo is used." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1209 +msgid "" +"A workaround for this issue is to use the boot parameter " +"<literal>rootdelay=<replaceable>9</replaceable></literal>. The value for " +"the timeout (in seconds) may need to be adjusted." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/upgrading.dbk:1218 +msgid "Things to do before rebooting" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1220 +msgid "" +"When <literal>aptitude dist-upgrade</literal> has finished, the formal " +"upgrade is complete, but there are some other things that should be taken " +"care of <emphasis>before</emphasis> the next reboot." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:1225 +msgid "Converting from devfs" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1227 +msgid "" +"Debian kernels no longer include support for <literal>devfs</literal>, so " +"<literal>devfs</literal> users will need to convert their systems manually " +"before booting an &releasename; kernel." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1232 +msgid "" +"If you see the string 'devfs' in <filename>/proc/mounts</filename>, you are " +"most likely using <literal>devfs</literal>. Any configuration files that " +"reference <literal>devfs</literal>-style names will need to be adjusted to " +"use <systemitem role=\"package\">udev</systemitem>-style names. Files that " +"are likely to refer to <literal>devfs</literal>-style device names include " +"<filename>/etc/fstab</filename>, <filename>/etc/lilo.conf</filename>, " +"<filename>/boot/grub/menu.lst</filename>, and <filename>/etc/inittab</" +"filename>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1242 +msgid "" +"More information about potential issues is available in bug report <ulink " +"url=\"http://bugs.debian.org/341152\">#341152</ulink>." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:1248 +msgid "Rerun lilo" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1250 +msgid "" +"If you are using <systemitem role=\"package\">lilo</systemitem> as your " +"bootloader (it is the default bootloader for some installations of " +"&oldreleasename;) it is strongly recommended that you rerun <command>lilo</" +"command> after the upgrade:" +msgstr "" + +# type: Content of: <chapter><section><section><screen> +#: en/upgrading.dbk:1254 +#, no-wrap +msgid "" +"\n" +"# /sbin/lilo\n" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1258 +msgid "" +"Notice this is needed even if you did not upgrade your system's kernel, as " +"<command>lilo</command>'s second stage will change due to the package " +"upgrade." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1262 +msgid "" +"Also, review the contents of your <filename>/etc/kernel-img.conf</filename> " +"and make sure that you have <emphasis>do_bootloader = Yes</emphasis> in it. " +"That way the bootloader will always be rerun after a kernel upgrade." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1267 +msgid "" +"If you encounter any issues when running <command>lilo</command>, review the " +"symbolic links in <filename>/</filename> to <filename>vmlinuz</filename> and " +"<filename>initrd</filename> and the contents of your <filename>/etc/lilo." +"conf</filename> for discrepancies." +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote> +#: en/upgrading.dbk:1273 +msgid "" +"If you forgot to rerun <command>lilo</command> before the reboot or the " +"system is accidentally rebooted before you could do this manually, your " +"system might fail to boot. Instead of the lilo prompt, you will only see " +"<emphasis>LI</emphasis> when booting the system<footnote>" +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote><para> +#: en/upgrading.dbk:1276 +msgid "" +"For more information on <command>lilo</command>'s boot error codes please " +"see <ulink url=\"http://tldp.org/HOWTO/Bootdisk-HOWTO/a1483.html\">The Linux " +"Bootdisk HOWTO</ulink>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1279 +msgid "" +"</footnote>. See <xref linkend=\"recovery\"/> for information on how to " +"recover from this." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:1285 +msgid "Upgrading mdadm" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1287 +msgid "" +"mdadm now needs a configuration file to assemble MD arrays (RAID) from the " +"initial ramdisk and during the system initialisation sequence. Please make " +"sure to read and act upon the instructions in <filename>/usr/share/doc/mdadm/" +"README.upgrading-2.5.3.gz</filename> after the package has been upgraded " +"<emphasis role=\"strong\">and before you reboot</emphasis>. The latest " +"version of this file is available at <ulink url=\"http://svn.debian.org/wsvn/" +"pkg-mdadm/mdadm/trunk/debian/README.upgrading-2.5.3?op=file\"></ulink>; " +"please consult it in case of problems." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/upgrading.dbk:1301 +msgid "Preparing for the next release" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1303 +msgid "" +"After the upgrade there are several things you can do to prepare for the " +"next release." +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:1309 +msgid "" +"If using <command>grub</command>, edit <filename>/etc/kernel-img.conf</" +"filename> and adjust the location of the <command>update-grub</command> " +"program changing <filename>/sbin/update-grub</filename> to <filename>/usr/" +"sbin/update-grub</filename>." +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:1318 +msgid "" +"If the new kernel image metapackage was pulled in as a dependency of the old " +"one, it will be marked as automatically installed, which should be corrected:" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><screen> +#: en/upgrading.dbk:1321 +#, no-wrap +msgid "" +"\n" +"# aptitude unmarkauto $(dpkg-query -W 'linux-image-2.6-*' | cut -f1)\n" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:1327 +msgid "Remove &oldreleasename;'s kernel metapackages by running:" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><screen> +#: en/upgrading.dbk:1329 +#, no-wrap +msgid "" +"\n" +"# aptitude purge kernel-image-2.6-<flavor>\n" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:1335 +msgid "" +"Move any configuration options from <filename>/etc/network/options</" +"filename> to <filename>/etc/sysctl.conf</filename>. Please see <filename>/" +"usr/share/doc/netbase/README.Debian</filename> for details." +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:1342 +msgid "" +"Remove obsolete and unused packages as described in <xref linkend=\"obsolete" +"\"/> . You should review which configuration files they use and consider " +"purging the packages to remove their configuration files" +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/upgrading.dbk:1351 +msgid "Deprecated packages" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1353 +msgid "" +"With the release of <literal>Lenny</literal> a bigger number of server " +"packages will be deprecated, thus updating to newer versions of those now " +"will save you from trouble when updating to <literal>Lenny</literal>." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1358 +msgid "This includes the following packages:" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:1363 +msgid "apache (1.x), successor is apache2" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:1368 +msgid "bind8, successor is bind9" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:1373 +msgid "php4, successor is php5" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:1378 +msgid "postgresql-7.4, successor is postgresql-8.1" +msgstr "" + +# type: Content of: <chapter><section><itemizedlist><listitem><para> +#: en/upgrading.dbk:1383 +msgid "exim 3, successor is exim4" +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/upgrading.dbk:1390 +msgid "Obsolete packages" +msgstr "" + +# type: Content of: <chapter><section><para><footnote> +#: en/upgrading.dbk:1392 +msgid "" +"Introducing several thousand new packages, &releasename; also retires and " +"omits more than two thousand old packages that were in &oldreleasename;. It " +"provides no upgrade path for these obsolete packages. While nothing " +"prevents you from continuing to use an obsolete package where desired, the " +"Debian project will usually discontinue security support for it a year after " +"&releasename;'s release<footnote>" +msgstr "" + +# type: Content of: <chapter><section><para><footnote><para> +#: en/upgrading.dbk:1396 +msgid "" +"Or for as long as there is not another release in that time frame. " +"Typically only two stable releases are supported at any given time." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1398 +msgid "" +"</footnote>, and will not normally provide other support in the meantime. " +"Replacing them with available alternatives, if any, is recommended." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1403 +msgid "" +"There are many reasons why packages might have been removed from the " +"distribution: they are no longer maintained upstream; there is no longer a " +"Debian Developer interested in maintaining the packages; the functionality " +"they provide has been superseded by different software (or a new version); " +"or they are no longer considered suitable for &releasename; due to bugs in " +"them. In the latter case, packages might still be present in the unstable " +"distribution." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1411 +msgid "" +"Detecting which packages in an updated system are obsolete is easy since the " +"package management front-ends will mark them as such. If you are using " +"<command>aptitude</command>, you will see a listing of these packages in the " +"Obsolete and Locally Created Packages entry. <command>dselect</command> " +"provides a similar section but the listing it presents might differ. Also, " +"if you have used <command>aptitude</command> to manually install packages in " +"&oldreleasename; it will have kept track of those packages you manually " +"installed and will be able to mark as obsolete those packages pulled in by " +"dependencies alone which are no longer needed if a package has been " +"removed. Also, <command>aptitude</command>, unlike <command>deborphan</" +"command> will not mark as obsolete packages that you manually installed, as " +"opposed to those that were automatically installed through dependencies." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1425 +msgid "" +"There are additional tools you can use to find obsolete packages such as " +"<command>deborphan</command>, <command>debfoster</command> or " +"<command>cruft</command>. <command>deborphan</command> is highly " +"recommended, although it will (in default mode) only report obsolete " +"libraries: packages in the libs or oldlibs sections that are not used by any " +"other packages. Do not blindly remove the packages these tools present, " +"especially if you are using aggressive non-default options that are prone to " +"produce false positives. It is highly recommended that you manually review " +"the packages suggested for removal (i.e. their contents, size and " +"description) before you remove them." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/upgrading.dbk:1436 +msgid "" +"The <ulink url=\"http://bugs.debian.org/\">Debian Bug Tracking System</" +"ulink> often provides additional information on why the package was " +"removed. You should review both the archived bug reports for the package " +"itself and the archived bug reports for the <ulink url=\"http://bugs.debian." +"org/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&archive=yes\">ftp.debian." +"org pseudo-package</ulink>." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/upgrading.dbk:1444 +msgid "Dummy packages" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1446 +msgid "" +"Some packages from &oldreleasename; have been split into several packages in " +"&releasename;, often to improve system maintainability. To ease the upgrade " +"path in such cases, &releasename; often provides dummy packages: empty " +"packages that have the same name as the old package in &oldreleasename; with " +"dependencies that cause the new packages to be installed. These dummy " +"packages are considered obsolete packages after the upgrade and can be " +"safely removed." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/upgrading.dbk:1454 +msgid "" +"Most (but not all) dummy packages' descriptions indicate their purpose. " +"Package descriptions for dummy packages are not uniform, however, so you " +"might also find <command>deborphan</command> with the <literal>--guess</" +"literal> options useful to detect them in your system. Note that some dummy " +"packages are not intended to be removed after an upgrade but are, instead, " +"used to keep track of the current available version of a program over time." +msgstr "" diff --git a/blackboard/ml/whats-new.po b/blackboard/ml/whats-new.po index 6f57580..6ff2613 100644 --- a/blackboard/ml/whats-new.po +++ b/blackboard/ml/whats-new.po @@ -6,11 +6,864 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2008-10-27 03:39-0400\n" +"Project-Id-Version: release-notes 5.0\n" +"POT-Creation-Date: 2008-08-07 07:56+0300\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: ENCODING\n" +"Content-Transfer-Encoding: ENCODING" + +# type: Content of: <chapter><title> +#: en/whats-new.dbk:9 +msgid "What's new in &debian; &release;" +msgstr "" + +# type: Content of: <chapter><para> +#: en/whats-new.dbk:11 +msgid "" +"The <ulink url=\"&url-wiki-newinlenny;\">Wiki</ulink> has more information " +"about this topic." +msgstr "" + +# type: Content of: <chapter><para> +#: en/whats-new.dbk:15 +msgid "This release adds official support for the armel EABI." +msgstr "" + +# type: Content of: <chapter><para> +#: en/whats-new.dbk:18 +msgid "" +"The following are the officially supported architectures for &debian; " +"&releasename;:" +msgstr "" + +# type: Content of: <chapter><itemizedlist><listitem><para> +#: en/whats-new.dbk:24 +msgid "Intel x86 ('i386')" +msgstr "" + +# type: Content of: <chapter><itemizedlist><listitem><para> +#: en/whats-new.dbk:29 +msgid "Alpha ('alpha')" +msgstr "" + +# type: Content of: <chapter><itemizedlist><listitem><para> +#: en/whats-new.dbk:34 +msgid "SPARC ('sparc')" +msgstr "" + +# type: Content of: <chapter><itemizedlist><listitem><para> +#: en/whats-new.dbk:39 +msgid "PowerPC ('powerpc')" +msgstr "" + +# type: Content of: <chapter><itemizedlist><listitem><para> +#: en/whats-new.dbk:44 +msgid "ARM ('arm')" +msgstr "" + +# type: Content of: <chapter><itemizedlist><listitem><para> +#: en/whats-new.dbk:49 +msgid "MIPS ('mips' (big-endian) and 'mipsel' (little-endian))" +msgstr "" + +# type: Content of: <chapter><itemizedlist><listitem><para> +#: en/whats-new.dbk:54 +msgid "Intel Itanium ('ia64')" +msgstr "" + +# type: Content of: <chapter><itemizedlist><listitem><para> +#: en/whats-new.dbk:59 +msgid "HP PA-RISC ('hppa')" +msgstr "" + +# type: Content of: <chapter><itemizedlist><listitem><para> +#: en/whats-new.dbk:64 +msgid "S/390 ('s390')" +msgstr "" + +# type: Content of: <chapter><itemizedlist><listitem><para> +#: en/whats-new.dbk:69 +msgid "AMD64 ('amd64'" +msgstr "" + +# type: Content of: <chapter><para> +#: en/whats-new.dbk:74 +msgid "" +"You can read more about port status, and port-specific information for your " +"architecture at the <ulink url=\"http://www.debian.org/ports/i386/\">Debian " +"port web pages</ulink>." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/whats-new.dbk:79 +msgid "What's new in the distribution?" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:85 +msgid "" +"This new release of Debian again comes with a lot more software than its " +"predecessor &oldreleasename;; the distribution includes over &packages-new; " +"new packages, for a total of over &packages-total; packages. Most of the " +"software in the distribution has been updated: over 10700 software packages " +"(this is 68% of all packages in &oldreleasename;). Also, a significant " +"number of packages (over 3500, 23% of the packages in &oldreleasename;) have " +"for various reasons been removed from the distribution. You will not see " +"any updates for these packages and they will be marked as 'obsolete' in " +"package management front-ends." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:97 +msgid "With this release, &debian; updates from X.Org 7.1 to X.Org 7.3." +msgstr "" + +# type: Content of: <chapter><section><para><footnote> +#: en/whats-new.dbk:100 +msgid "" +"&debian; again ships with several desktop applications and environments. " +"Among others it now includes the desktop environments GNOME 2.22<footnote>" +msgstr "" + +# type: Content of: <chapter><section><para><footnote><para> +#: en/whats-new.dbk:103 +msgid "With some modules from GNOME 2.20." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:104 +msgid "" +"</footnote>, KDE 3.5.9, and Xfce 4.4.2. Productivity applications have also " +"been upgraded, including the office suites OpenOffice.org 2.4.1 and KOffice " +"1.6.3 as well as GNUcash 2.2.6, GNUmeric 1.8.3 and Abiword 2.6.4." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:110 +msgid "" +"Updates of other desktop applications include the upgrade to Evolution 2.6.3 " +"and Gaim 2.0. The Mozilla suite has also been updated: <command>iceweasel</" +"command> (version 3.0.1) is the unbranded <command>Firefox</command> web " +"browser and <command>icedove</command> (version 2.0.0.14) is the unbranded " +"<command>Thunderbird</command> mail client." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:116 +msgid "" +"Among many others, this release also includes the following software updates:" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><thead><row><entry> +#: en/whats-new.dbk:126 +msgid "Package" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><thead><row><entry> +#: en/whats-new.dbk:127 +msgid "Version in &oldreleasename;" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><thead><row><entry> +#: en/whats-new.dbk:128 +msgid "Version in &releasename;" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:133 +msgid "Apache" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:134 +msgid "2.2.3" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:135 +msgid "2.2.9" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:138 +msgid "BIND DNS Server" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:139 +msgid "9.3.4" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:140 +msgid "9.5.0" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:143 +msgid "Courier MTA" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:144 +msgid "0.53.3" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:145 +msgid "0.60.0" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:148 +msgid "Dia" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:149 +msgid "0.95.0" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:150 +msgid "0.96.1" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:153 +msgid "Ekiga VoIP Client" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:154 +msgid "2.0.3" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:155 +msgid "2.0.12" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:158 +msgid "Exim default email server" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:159 +msgid "4.63" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:160 +msgid "4.69" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:163 +msgid "GNU Compiler Collection as default compiler" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:164 +msgid "4.1.1" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:165 +msgid "4.3.1" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:168 +msgid "GIMP" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:169 +msgid "2.2.13" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:170 +msgid "2.4.6" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:173 +msgid "the GNU C library" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:174 +msgid "2.3.6" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:175 +msgid "2.7" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:178 +msgid "lighttpd" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:179 +msgid "1.4.13" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:180 +msgid "1.4.19" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:183 +msgid "maradns" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:184 +msgid "1.2.12.04" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:185 +msgid "1.3.07.08" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:188 +msgid "MySQL" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:189 +msgid "5.0.32" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:190 +msgid "5.0.51a" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:193 +msgid "OpenLDAP" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:194 +msgid "2.3.30" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:195 +msgid "2.4.10" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:198 +msgid "OpenSSH" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:199 +msgid "4.3" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:200 +msgid "4.7 (TODO: 5.1?)" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:203 +msgid "PHP" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:204 +msgid "5.2.0" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:205 +msgid "5.2.6" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:208 +msgid "Postfix MTA" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:209 +msgid "2.3.8" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:210 en/whats-new.dbk:220 +msgid "2.5.2" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:213 +msgid "PostgreSQL" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:214 +msgid "7.5.22" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:215 +msgid "8.3.3" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:218 +msgid "Python" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:219 +msgid "2.4.4" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:223 +msgid "Tomcat" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:224 +msgid "5.5.20" +msgstr "" + +# type: Content of: <chapter><section><informaltable><tgroup><tbody><row><entry> +#: en/whats-new.dbk:225 +msgid "5.5.26" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:234 +msgid "" +"The official &debian; distribution now ships on 19 to 23 binary CDs " +"(depending on the architecture) and a similar number of source CDs. A DVD " +"version of the distribution is also available." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:239 +msgid "Debian now supports Linux Standards Base (LSB), version 3.2." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/whats-new.dbk:242 +msgid "Package management" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:245 +msgid "" +"<command>aptitude</command> is the preferred program for package management " +"from console. <command>aptitude</command> supports most command line " +"operations of <command>apt-get</command> and has proven to be better at " +"dependency resolution than <command>apt-get</command>. If you are still " +"using <command>dselect</command>, you should switch to <systemitem role=" +"\"package\">aptitude</systemitem> as the official frontend for package " +"management." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:254 +msgid "" +"For &releasename; an advanced conflict resolving mechanism has been " +"implemented in <command>aptitude</command> that will try to find the best " +"solution if conflicts are detected because of changes in dependencies " +"between packages." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/whats-new.dbk:263 +msgid "backports.org/backports.debian.org" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:264 +msgid "TODO: write about probability backports.org becoming official" +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/whats-new.dbk:268 +msgid "debian-volatile now an official service" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:270 +msgid "" +"The <emphasis>debian-volatile</emphasis> service that was introduced as an " +"unofficial service with the release of &oldreleasename; has now become an " +"official Debian GNU/Linux service." +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote> +#: en/whats-new.dbk:275 +msgid "" +"This means that it now uses a <literal>.debian.org</literal> " +"address<footnote>" +msgstr "" + +# type: Content of: <chapter><section><section><para><footnote><para> +#: en/whats-new.dbk:276 +msgid "" +"The old <literal>volatile.debian.net</literal> address will also remain " +"valid for the time being." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:278 +msgid "" +"</footnote>. Please make sure to update your <filename>/etc/apt/sources." +"list</filename> accordingly if you were already using this service." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:283 +msgid "" +"<emphasis>debian-volatile</emphasis> allows users to easily update stable " +"packages that contain information that quickly goes out of date. Examples " +"are a virus scanner's signatures list or a spam filter's pattern set. For " +"more information and a list of mirrors, please see the archive's <ulink url=" +"\"http://volatile.debian.org/\">web page</ulink>." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/whats-new.dbk:295 +msgid "System improvements" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:297 +msgid "" +"There have been a number of changes in the distribution that will benefit " +"new installations of &releasename;, but may not be automatically applied on " +"upgrades from &oldreleasename;. This section gives an overview of the most " +"relevant changes." +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><term> +#: en/whats-new.dbk:303 +msgid "SELinux priority standard, but not enabled by default" +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:306 +msgid "" +"The packages needed for SELinux support have been promoted to priority " +"<emphasis>standard</emphasis>. This means that they will be installed by " +"default during new installations. For existing systems you can install " +"SELinux using:" +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><listitem><screen> +#: en/whats-new.dbk:311 +#, no-wrap +msgid "" +"\n" +"# aptitude install selinux-basics\n" +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:315 +msgid "" +"Note that SELinux support is <emphasis>not</emphasis> enabled by default. " +"Information on setting up and enabling SELinux can be found on the <ulink " +"url=\"http://wiki.debian.org/SELinux\">Debian Wiki</ulink>." +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><term> +#: en/whats-new.dbk:322 +msgid "New default inet superdaemon" +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:325 +msgid "" +"The default inet superdaemon for &releasename; is <systemitem role=\"package" +"\">openbsd-inetd</systemitem> instead of <systemitem role=\"package\">netkit-" +"inetd</systemitem>. It will not be started if no services are configured, " +"which is true by default. The new default daemon will be installed " +"automatically on upgrade." +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><term> +#: en/whats-new.dbk:334 +msgid "Default <command>vi</command> clone changed" +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:337 +msgid "" +"The <command>vi</command> clone installed by default is now a compact " +"version of <command>vim</command> (<systemitem role=\"package\">vim-tiny</" +"systemitem>) instead of <systemitem role=\"package\">nvi</systemitem>." +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><term> +#: en/whats-new.dbk:344 +msgid "" +"Changes in default features for <literal>ext2</literal>/<literal>ext3</" +"literal>" +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:347 +msgid "" +"New ext2 and ext3 file systems will be created with features " +"<emphasis>dir_index</emphasis> and <emphasis>resize_inode</emphasis> enabled " +"by default. The first feature speeds up operations on directories with many " +"files; the second makes it possible to resize a file system on-line (i.e. " +"while it is mounted)." +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><listitem><para><footnote> +#: en/whats-new.dbk:354 +msgid "" +"Users upgrading from &oldreleasename; could consider adding the " +"<emphasis>dir_index</emphasis> flag manually using <command>tune2fs</" +"command><footnote>" +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><listitem><para><footnote><para> +#: en/whats-new.dbk:356 +msgid "" +"The flag <emphasis>filetype</emphasis> should already be set on most file " +"systems, except possibly on systems installed before &oldreleasename;." +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:358 +msgid "" +"</footnote>; the <emphasis>resize_inode</emphasis> flag cannot be added to " +"an existing file system. It is possible to check which flags are set for a " +"file system using <literal>dumpe2fs -h</literal>." +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><term> +#: en/whats-new.dbk:366 +msgid "Better support for UTF-8" +msgstr "" + +# type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:369 +msgid "" +"A number of additional applications will be set up to use UTF-8 by default " +"or have better UTF-8 support than before." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:376 +msgid "" +"The <ulink url=\"http://wiki.debian.org/Etch2LennyUpgrade\">Debian Wiki</" +"ulink> has some additional information about changes between " +"&oldreleasename; and &releasename;." +msgstr "" + +# type: Content of: <chapter><section><title> +#: en/whats-new.dbk:382 +msgid "Major kernel-related changes" +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:384 +msgid "" +"&debian; &release; ships with kernel version &kernelversion; for all " +"architectures; the release is not compatible with 2.4 kernels." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:388 +msgid "" +"There have been major changes both in the kernel itself and in the packaging " +"of the kernel for Debian. Some of these changes complicate the upgrade " +"procedure and can potentially result in problems while rebooting the system " +"after the upgrade to &releasename;. This section gives an overview of the " +"most important changes; potential issues and information on how to work " +"around them is included in later chapters." +msgstr "" + +# type: Content of: <chapter><section><para> +#: en/whats-new.dbk:396 +msgid "" +"If you are currently using a 2.4 kernel, you should read <xref linkend=" +"\"upgrade-to-2.6\"/> carefully." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/whats-new.dbk:400 +msgid "Changes in kernel packaging" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/whats-new.dbk:403 +msgid "Kernel packages renamed" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:406 +msgid "" +"All Linux kernel packages have been renamed from <literal>kernel-*</literal> " +"to <literal>linux-*</literal> to clean up the namespace. This will make it " +"easier to include non-Linux kernels in Debian in the future." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/whats-new.dbk:414 +msgid "Flavor 386 replaced with 486" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:417 +msgid "" +"As support for 80386 processors was dropped with &oldreleasename;, the 386 " +"kernel flavor has now been dropped as well and replaced by a new 486 flavor." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><term> +#: en/whats-new.dbk:424 +msgid "Standard kernels have SMP abilities" +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:427 +msgid "No news here." +msgstr "" + +# type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> +#: en/whats-new.dbk:430 +msgid "" +"Multiprocessor systems no longer require an <literal>*-smp</literal> flavor " +"of the Linux kernel. For &arch-title;, <literal>linux-image</literal> " +"packages without the <literal>-smp</literal> suffix support both " +"uniprocessor and multiprocessor systems. (The one exception is the 486 " +"flavor, which only supports a single processor.)" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:441 +msgid "" +"Where possible, dummy transition packages that depend on the new packages " +"have been provided for the dropped packages." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/whats-new.dbk:447 +msgid "New utilities to generate initrds" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:449 +msgid "" +"The Debian kernel image packages for &arch-title; require an initrd for " +"booting the system. Because of changes in the kernel, the utility used to " +"generate initrds in &oldreleasename;, <systemitem role=\"package\">initrd-" +"tools</systemitem> can no longer be used and has been deprecated. Two new " +"utilities have been developed that replace it: <systemitem role=\"package" +"\">initramfs-tools</systemitem> and <systemitem role=\"package\">yaird</" +"systemitem>. The concepts behind the new utilities are very different; an " +"overview is available on the <ulink url=\"http://wiki.debian.org/" +"InitrdReplacementOptions\">Debian Wiki</ulink>. Both will generate an " +"initrd using the <emphasis>initramfs</emphasis> file system, which is a " +"compressed <command>cpio</command> archive. The default and recommended " +"utility is <systemitem role=\"package\">initramfs-tools</systemitem>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:464 +msgid "" +"Upgrading to an &releasename; kernel will cause <systemitem role=\"package" +"\">initramfs-tools</systemitem> to be installed by default. If you are " +"upgrading from a 2.4 kernel to a 2.6 Debian kernel, you must use <systemitem " +"role=\"package\">initramfs-tools</systemitem>. Using <systemitem role=" +"\"package\">yaird</systemitem> will cause linux-image-2.6 installations to " +"fail if you are running a 2.2 or 2.4 kernel." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:472 +msgid "" +"The package <systemitem role=\"package\">initrd-tools</systemitem> is still " +"included in &releasename; because it is needed for upgrades from " +"&oldreleasename;. It will be dropped for the next release." +msgstr "" + +# type: Content of: <chapter><section><section><title> +#: en/whats-new.dbk:479 +msgid "Dynamic <filename>/dev</filename> management and hardware discovery" +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:481 +msgid "" +"&releasename; kernels no longer provide support for <literal>devfs</literal>." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:484 +msgid "" +"The replacement for <literal>devfs</literal> is <systemitem role=\"package" +"\">udev</systemitem>, a userspace implementation of devfs." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:488 +msgid "" +"<systemitem role=\"package\">udev</systemitem> is mounted over the " +"<filename>/dev</filename> directory and will populate that directory with " +"devices supported by the kernel. It will also dynamically add and remove " +"devices as kernel modules are loaded or unloaded respectively, based on " +"events generated by the kernel. <command>udev</command> is a lot more " +"versatile than <literal>devfs</literal> and offers services that are used by " +"other packages like <systemitem role=\"package\">hal</systemitem> (hardware " +"abstraction layer)." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:497 +msgid "" +"In combination with the kernel, <systemitem role=\"package\">udev</" +"systemitem> also takes care of hardware discovery and module loading for " +"detected devices. Because of this it conflicts with <systemitem role=" +"\"package\">hotplug</systemitem>. In &oldreleasename;, <systemitem role=" +"\"package\">discover</systemitem> could also be used for loading modules " +"during the boot process, but its new version in &releasename; no longer " +"provides that function. <systemitem role=\"package\">discover</systemitem> " +"is still used by X.Org to detect what graphics controller is present in the " +"system." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:507 +msgid "" +"If you install a Debian kernel image, <systemitem role=\"package\">udev</" +"systemitem> will be installed by default as <systemitem role=\"package" +"\">initramfs-tools</systemitem> depends on it." +msgstr "" + +# type: Content of: <chapter><section><section><para> +#: en/whats-new.dbk:512 +msgid "" +"You can avoid installing <systemitem role=\"package\">udev</systemitem> by " +"compiling a custom non-modular kernel or by using an alternative initrd " +"generator, such as <systemitem role=\"package\">yaird</systemitem>. " +"However, <systemitem role=\"package\">initramfs-tools</systemitem> is the " +"recommended initrd generator." +msgstr "" |