Showing diffs for about.dbk... (ver: 6370:)Index: about.dbk

--- about.dbk (revisión: 6370)
+++ about.dbk (copia de trabajo)
@@ -8,7 +8,7 @@

<title>Introduction</title>
<para>
This document informs users of the &debian; distribution about - major changes in version &release; (codenamed "&releasename;"). + major changes in version &release; (codenamed &releasename;).

</para>
<para>
The release notes provide information on how to upgrade safely @@ -49,8 +49,18 @@
in this documentation,
please file a bug in the <ulink url="&url-bts;">bug tracking system</ulink> against the <systemitem -role="package">release-notes</systemitem> package. +role="package">release-notes</systemitem> package. You +might want to review first the <ulink url="&url-bts-rn;">existing bug +reports</ulink> in case the issue you've found has already been reported. Feel +free to add additional information to existing bug reports if you can +contribute content for this document.
</para>
+<para>
+We appreciate, and encourage, reports providing patches to the +document's sources. You will find more information describing +how to obtain the sources of this document in <xref +linkend="sources"/>.
+</para>
</section>

<section id="upgrade-reports">
@@ -73,18 +83,18 @@
<para>

<programlisting condition="fixme">
-TODO: check status of #494028 about apt-get vs. aptitude TODO: any more things to add here?
</programlisting>

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>. +<systemitem role="package">apt</systemitem>'s package state information, +available at <filename>/var/lib/apt/extended_states</filename>. You +should have made a backup before the upgrade as described at +<xref linkend="data-backup"/>, but you can also find backups of +<filename>/var/lib/dpkg/status</filename> in +<filename>/var/backups</filename>.
</para>
</listitem>
<listitem>
. Added: 19 Removed: 9
../en/diff.ver: (No es un recurso versionado)

svn: Hubo un problema; vea otros informes de errores para más detalles ERROR: diff.ver has not a correct English version: ERROR: hyphenation.tex has not a correct English version: Showing diffs for installing.dbk... (ver: 6370:)Index: installing.dbk


--- installing.dbk      (revisión: 6370)
+++ installing.dbk      (copia de trabajo)

@@ -43,133 +43,267 @@
for the &releasename; beta and RC releases available from the Debian Installer's <ulink url="&url-installer-news;">news history</ulink>. </para>
+
<section id="inst-changes">
<title>Major changes</title>
+
+<!-- Sources:
+http://debian.org/devel/debian-installer/News/2010/20100221 (alpha1) +http://wiki.debian.org/DebianInstaller/ReleaseAnnounce (beta) --> +
+<!-- TODO: Add
+
+Tasks changes:
+Many changes have been made to package selection, plus: + * accessibility packages have been added to the GNOME task; + * the laptop task has been modernized; + * an SSH Server task has been added. +
+Behavioral changes in this release
+ Installer now uses udhcpc as DHCP client, except on kFreeBSD images. +
+Based on http://www.debian.org/devel/debian-installer/errata +there are currently no images for kFreeBSD in the alpha release +
+-->
+
<variablelist>
+
<varlistentry>
-<term>Support for loading firmware during installation</term> +<term>Dropped platforms</term>
<listitem>
<para>
-It is now possible to load firmware binary files from removable media -when they're provided externally to Debian installation media. +Support for the Alpha ('alpha'), ARM ('arm') and HP PA-RISC ('hppa') +architectures has been dropped from the installer. The 'arm' architecture is +obsoleted by the ARM EABI ('armel') port. </para>
</listitem>
</varlistentry>
-<varlistentry>
-<term>Support for installation from Microsoft Windows -<indexterm><primary>Microsoft Windows</primary></indexterm></term> +
+
+<varlistentry arch="i386;amd64">
+<term>Support for kFreeBSD</term>
<listitem>
<para>
-The installation media are now provided with an application -that allows preparing the system to install Debian from Microsoft -Windows environments.
+The installer can be used to install the kFreeBSD instead of the Linux +kernel and test the technology preview. To use this feature the appropriate +installation image (or CD/DVD set) has to be used. </para>
</listitem>
</varlistentry>
-<varlistentry>
-<term><acronym>SATA</acronym> <acronym>RAID</acronym> support</term> +
+<varlistentry arch="armel">
+<term>New supported platforms</term>
<listitem>
<para>
+The installation system now supports the following platforms: +
+<itemizedlist>
+<listitem>
+<para>
+Intel Storage System SS4000-E
</para>
</listitem>
+<listitem>
+<para>
+Marvell's Kirkwood platform:
+</para>
+
+<itemizedlist>
+<listitem>
+<para>
+QNAP TS-110, TS-119, TS-210, TS-219, TS-219P and TS-419P +</para>
+</listitem>
+<listitem>
+<para>
+Marvell SheevaPlug and GuruPlug
+</para>
+</listitem>
+<listitem>
+<para>
+Marvell OpenRD-Base, OpenRD-Client and OpenRD-Ultimate +</para>
+</listitem>
+</itemizedlist>
+</listitem>
+
+<listitem>
+<para>
+HP t5325 Thin Client (partial support) +</para>
+</listitem>
+</itemizedlist>
+
+</para>
+</listitem>
</varlistentry>
-<varlistentry>
-<term>Early upgrade of packages with security fixes</term> +
+<varlistentry arch="i386;amd64">
+<term>GRUB 2 is the default bootloader</term> <listitem>
<para>
-When used with functional network access, the installer will upgrade all packages that have been updated since -the initial release of &releasename;. This upgrade happens during -the installation step, before the installed system is booted. +The bootloader that will be installed by default is +<systemitem role="package">grub-pc</systemitem> (GRUB 2). </para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Help during the installation process</term> +<listitem>
<para>
-As a consequence, the installed system is less likely to be vulnerable -to security issues that were discovered and fixed between the release -time of &releasename; and the installation time. +The dialogs presented during the installation process now provide help +information. Although not currently used in all dialogs, this feature would be +increasingly used in future releases. This will improve the user experience +during the installation process, especially for new users. </para>
</listitem>
</varlistentry>
+
<varlistentry>
-<term>Support for <emphasis>volatile</emphasis></term> +<term>Installation of Recommended packages</term> <listitem>
<para>
-The installer can now optionally set up the installed system to use -updated packages from <literal>volatile.debian.org</literal>. This archive hosts packages -providing data that needs to be regularly updated over time, such -as timezones definitions, anti-virus signature files, etc. +The installation system will install all recommended packages by +default throughout the process except for some specific situations in +which the general setting gives undesired results. </para>
</listitem>
</varlistentry>
-<varlistentry arch="i386;amd64">
-<term>New boot menu for Intel x86 and AMD64</term> +
+<varlistentry>
+<term>Automatic installation of hardware-specific packages</term> <listitem>
<para>
-An interactive boot menu was added to make the choice of specific -options and boot methods more intuitive for users. +The system will automatically select for installation hardware-specific +packages when they are appropriate. This is achieved through the use of +<literal>discover-pkginstall</literal> from the <systemitem +role="package">discover</systemitem> package. </para>
</listitem>
</varlistentry>
+
<varlistentry>
-<term>New ports</term>
+<term>Support for installation of previous releases</term> <listitem>
<para>
-The armel architecture is now supported. Images for i386 Xen guests are also provided. +The installation system can be also used for the installation +of previous release, such as &oldreleasename;. </para>
</listitem>
</varlistentry>
+
<varlistentry>
-<term>Support for hardware speech synthesis devices</term> +<term>Improved mirror selection</term> <listitem>
<para>
-Several devices designed to provide hardware speech synthesis are now -supported by the installer, therefore improving its accessibility -for visually-impaired users.
-<indexterm><primary>visually-impaired users</primary></indexterm> +The installation system provides better support for installing +both &releasename; as well as &oldreleasename; and older releases +(through the use of archive.debian.org). In addition, it will also +check that the selected mirror is consistent and holds the selected +release.
</para>
</listitem>
</varlistentry>
+
<varlistentry>
-<term>Support for <literal>relatime</literal> mount options</term> +<term>Changes in partitioning features</term> <listitem>
<para>
-The installer can now set up partitions with the <literal>relatime</literal> mount option, -so that access time on files and directories is updated only if the previous access time was earlier than the current modify or change time. +This release of the installer supports the use of the ext4 file system and it +also simplifies the creation of RAID, LVM and crypto protected partitioning +systems. Support for the reiserfs file system is no longer included by default, +although it can be optionally loaded.
</para>
</listitem>
</varlistentry>
+
+<!-- Available in beta release of installer (jfs) --> <varlistentry>
-<term>NTP clock synchronization at installation time</term> +<term>Support for loading firmware debs during installation</term> <listitem>
<para>
-The computer clock is now synchronized with NTP servers over the network -during installation so that the installed system immediately has -an accurate clock.
+It is now possible to load firmware package files from the installation +media in addition to removable media, allowing the creation of PXE +images and CDs/DVDs with included firmware packages. </para>
+
+<para>
+Starting with Debian &release;, non-free firmware has been moved out of main. +To install Debian on hardware that needs non-free firmware, you can either +provide the firmware yourself during installation or use pre-made non-free +CDs/DVDs which include the firmware. See the <ulink +url="http://www.debian.org/distrib">Getting Debian section</ulink> on the +Debian website for more information.
+</para>
</listitem>
</varlistentry>
+
<varlistentry>
<term>New languages</term>
<listitem>
<para>
-Thanks to the huge efforts of translators, Debian can now be installed in 63 -languages (50 using the text-based installation user interface and 13 supported -only with the graphical user interface). This is five -languages more than in &oldreleasename;. Languages added in this release include -Amharic, Marathi, Irish, Northern Sami, and Serbian. Due to lack of translation updates, one language has been dropped in -this release: Estonian. Another language that was disabled in &oldreleasename; has been reactivated: Welsh. +Thanks to the huge efforts of translators, &debian; can now be installed in 67 +languages. This is three more languages than in &oldreleasename;. +Most languages are available in both the text-based installation +user interface and the graphical user interface, while some +are only available in the graphical user interface. </para>
+
<para>
+Languages added in this release include: +</para>
+
+<itemizedlist>
+<listitem>
+<para>
+Asturian, Estonian, Kazakh and Persian have been added to the graphical and +text-based installer.
+</para>
+</listitem>
+<listitem>
+<para>
+Kannada and Telugu have been added to the graphical installer. +</para>
+</listitem>
+<listitem>
+<para>
+Thai, previously available only in the graphical user interface, is now +available also in the text-based installation user interface too. +</para>
+</listitem>
+
+</itemizedlist>
+
+<para>
+Due to the lack of translation updates two languages were +dropped in this release: Wolof and Welsh. +</para>
+
+<para condition="fixme">
The languages that can only be selected using the graphical installer as their -character sets cannot be presented in a non-graphical environment are: Amharic, Bengali, Dzongkha, Gujarati, Hindi, Georgian, Khmer, Malayalam, -Marathi, Nepali, Punjabi, Tamil, and Thai. +character sets cannot be presented in a non-graphical environment are: Amharic, +Bengali, Dzongkha, Gujarati, Hindi, Georgian, Kannada, Khmer, Malayalam, +Marathi, Nepali, Punjabi, Tamil and Telugu. </para>
</listitem>
</varlistentry>
+
<varlistentry>
-<term>Simplified country choice</term> +<term>Improved localisation selection</term> <listitem>
<para>
-The country choice list is now grouped by continents, allowing an easier selection of country, when users don't want to pick the ones associated with the chosen language. +The selection of localisation-related values (language, location and locale +settings) is now less interdependent and more flexible. Users will be able to +customize the system to their localisation needs more easily while still make +it comfortable to use for users that want to select the locale most +common for the country they reside in. </para>
+<para>
+Additionally, the consequences of localisation choices (such as timezone, +keymap and mirror selection) are now more obvious to the user. +</para>
</listitem>
</varlistentry>
</variablelist>
@@ -192,114 +326,7 @@
</para>
</section>

-<section id="install-with-braille">
- <title>Install &debian; with a Braille display</title> -
- <para>
- You can install &debian; &release; (&releasename;) with a Braille - display. The Braille display must be connected to a - <acronym>USB</acronym> or a serial port. If your Braille display - is connected to a <acronym>USB</acronym> port and the American - Braille table is supposed to be used, you can press - <keycap>Enter</keycap> in the boot menu. The screen reader BrlTTY - is standardized to search for Braille displays at the - <acronym>USB</acronym> port and uses the American Braille - table. If the Braille display is connected to a serial port or if - you want to use a different Braille table, you have to press the - <keycap>Tab</keycap> key in the boot menu first. Then, you can - configure the screen reader BrlTTY with the kernel parameter - brltty.
- </para>
-
- <para>
- For the parameter, the following syntax is valid: - </para>
-
- <programlisting>brltty=<replaceable>driver</replaceable>,<replaceable>device</replaceable>,<replaceable>table</replaceable></programlisting> -
- <para>
- All operands are optional.
- </para>
-
- <variablelist>
- <varlistentry>

-      <term><varname>driver</varname></term>
-      <listitem>
-       <para>
-         The driver for the employed Braille display. Here, you must
-         enter either a code consisting of two letters or the word
-         <literal>auto</literal>. If this argument is not entered, the automated
-         recognition is activated by default.
-       </para>
-      </listitem>

- </varlistentry>
- <varlistentry>

-      <term><varname>device</varname></term>
-      <listitem>
-       <para>
-         The device can be entered as relative to /dev/ as well as an
-         absolute specification.
-       </para>
-      </listitem>

- </varlistentry>
- <varlistentry>

-      <term><varname>table</varname></term>
-      <listitem>
-       <para>
-         Defines the Braille table for the desired language. By
-         default, the US table is employed.
-       </para>
-      </listitem>

- </varlistentry>
- </variablelist>
-
- <section id="braille-examples">
- <title>Examples</title>
-
- <programlisting>brltty=ht,ttyS0,de</programlisting> -
- <para>

-      The Handy Tech Driver is used. The Braille display is connected
-      to Com1.  The German Braille table is used.

- </para>
-
- <programlisting>brltty=,,de</programlisting> -
- <para>

-      Here, only the German Braille table is specified. Therefore,
-      BrlTTY will try to find a Braille display at a
-      <acronym>USB</acronym> port.

- </para>
- </section>
</section>

-<section id="install-with-speech">
- <title>Install &debian; with a hardware speech synthesis</title> -
- <note>
- <para>

-      Support for hardware speech synthesis is only available in the
-      textual version of the installer. For size reasons, however, it
-      is enabled along with support for the graphical installer, which
-      needs more space anyway. You thus need to select the
-      <computeroutput>Graphical install</computeroutput> entry in the
-      boot menu.

- </para>
- </note>
-
- <para>
- Hardware speech synthesis can not be automatically detected. You thus need - to append the <userinput>speakup.synth=driver</userinput> boot parameter - to tell Speakup which driver it should use. <userinput>driver</userinput> - should be replaced by the driver code for your device, see <ulink - url="&url-speakup-driver-codes;"></ulink> for a list. The textual version - of the installer will then be automatically selected, and support for the - speech synthesis will be automatically installed on the target system. - </para>
-
-</section>
-
-</section>
-
</chapter>

. Added: 187 Removed: 160
Showing diffs for issues.dbk... (ver: 6592:)Index: issues.dbk


--- issues.dbk (revisión: 6592)
+++ issues.dbk (copia de trabajo)
@@ -12,13 +12,14 @@

<section id="problems">
<title>Potential problems</title>
-<para>
-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 +<para>
+Sometimes, changes introduced in a new release have side-effects +we cannot reasonably avoid, or they expose +bugs somewhere else. This section documents issues we are aware of. Please also read the errata, the relevant packages' documentation, bug reports and other information mentioned in <xref linkend="morereading"/>. </para>
-<section id="udev">
+<section id="udev" condition="fixme">
<title>Problems with devices related to udev</title> <para>
Although <systemitem role="package">udev</systemitem> has been tested @@ -35,20 +36,65 @@
</para>
</section>

-<section id="incompatible-2.4">
-<title>Some applications may no longer work with a 2.4 kernel</title> +<section id="ide-pata-transition">
+<title>Migration of disk drivers from IDE to PATA subsystem</title> <para>
-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. + The new Linux kernel version provides different drivers for some PATA (IDE) + controllers. The names of some hard disk, CD-ROM, and tape devices may + change.
</para>
<para>
-One example is the HTTP proxy <systemitem role="package">squid</systemitem>. + It is now recommended to identify disk devices in configuration files by + label or UUID (unique identifier) rather than by device name, which will + work with both old and new kernel versions. Upon upgrading to the + &releasename; version of the Debian kernel packages, the <systemitem + role="package">linux-base</systemitem> package will offer to do this + conversion for you in the config files for most of the filesystem-related + packages on the system, including the various bootloaders included in + Debian. If you choose not to update the system configuration + automatically, or if you are not using the Debian kernel packages, you must + update device IDs yourself before the next system reboot to ensure the + system remains bootable.
</para>
</section>

-<section id="window-scaling">
+<section id="mdadm-metadata">
+<title>mdadm metadata format change requires recent Grub</title> +<para>
+The following only applies to users who want to let the <systemitem +role="package">grub-pc</systemitem> bootloader load the kernel directly off +a <acronym>RAID</acronym> device created with <systemitem +role="package">mdadm</systemitem> 3.x and default values, or when the metadata +version is explicitly set using <literal>-e</literal>. Specifically, this +includes all arrays created during or after the installation of Debian +&releasename;. Arrays created with older mdadm versions, and +<acronym>RAID</acronym>s created with the command-line option <literal>-e +0.9</literal> are not affected.
+</para>
+<para>
+Versions of <systemitem role="package">grub-pc</systemitem> older than +1.98+20100720-1 will not be able to boot directly off +a <acronym>RAID</acronym> with the 1.x metadata formats (the new default is +1.2). To ensure a bootable system, please make sure to use <systemitem +role="package">grub-pc</systemitem>
+1.98+20100720-1 or later, which is provided by Debian &releasename;. An +unbootable system may be rescued with <ulink +url="http://www.supergrubdisk.org/super-grub2-disk/">Super Grub2 Disk</ulink> +or <ulink url="http://grml.org">grml</ulink>. +</para>
+</section>
+
+<section id="pam_userdb">
+<title>pam_userdb.so breakage with newer libdb</title> +<para>
+Some Berkeley Database version 7 files created with libdb3 cannot be read by +newer libdb versions (see bug <ulink url="&url-bts;521860">#521860</ulink>). +As a workaround, the files can be recreated with <command>db4.8_load</command>, +from the <systemitem role="package">db4.8-util</systemitem> package. +</para>
+</section>
+
+<section id="window-scaling" condition="fixme"> <title>Certain network sites cannot be reached by TCP</title> <para>
Since 2.6.17, Linux aggressively uses TCP window scaling which is @@ -66,7 +112,7 @@
</para>
</section>

-<section id="poweroff">
+<section id="poweroff" condition="fixme"> <title>Automatic poweroff stops working</title> <para>
On some older systems, <literal>shutdown -h</literal> may not power off the @@ -104,7 +150,7 @@
</para>
</section>

-<section id="asynchronous-network-start"> +<section id="asynchronous-network-start" condition="fixme"> <title>Asynchronous network initialization may cause unpredictable behavior</title> <para>
On systems which use <systemitem role="package">udev</systemitem> to load @@ -120,7 +166,7 @@
</para>
</section>

-<section id="wpa">
+<section id="wpa" condition="fixme">
<title>Trouble when using <acronym>WPA</acronym> secured wireless networks</title> <indexterm><primary>WPA</primary></indexterm> <para>
@@ -147,7 +193,7 @@
</para>
</section>

-<section id="partitionenc">
+<section id="partitionenc" condition="fixme"> <title>Problems with non-ASCII characters in filenames</title> <para>
Mounting vfat, ntfs or iso9660 file systems with files that include non-ASCII @@ -164,7 +210,7 @@
</para>
</section>

-<section id="no-sound">
+<section id="no-sound" condition="fixme"> <title>Sound stops working</title>
<para>
In rare cases, sound might stop working after the upgrade. If this happens, @@ -204,7 +250,8 @@
<listitem>
<para>
check whether the command
-<programlisting>cat /dev/urandom &gt; /dev/dsp</programlisting> +<programlisting>cat /dev/urandom &gt; /dev/audio</programlisting> +or the command <programlisting>speaker-test</programlisting> works for <literal>root</literal>.
</para>
</listitem>
@@ -212,7 +259,7 @@
</para>
</section>

-<section arch="s390">
+<section arch="s390" condition="fixme">

<title>Potential Filesystem Corruption on upgrade</title> <para>
Starting with Kernel 2.6.25, Linux on the s390 architecture @@ -233,167 +280,50 @@

</para>
</section>

-</section>
-
-<section id="upgrade-to-2.6" condition="fixme"> -<title>Upgrading to a 2.6 kernel</title> -<programlisting condition="fixme">TODO: This section can be removed for lenny!</programlisting> -<para>
-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. -</para>
-<para>
-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. -</para>
-<para>
-If you use <emphasis><acronym>LVM</acronym></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. -</para>
-<para>
-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.
-</para>
-<para>
-For some <acronym>SATA</acronym> 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><para> 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 <literal>initramfs</literal> 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>. </para> </footnote>. -</para>
-<para>
-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 <quote>rescue</quote> floppy or CD-ROM to hand, in case -misconfiguration of the bootloader prevents you from booting the old kernel. -</para>
-<section id="l2.6-keyboard">
-<title>Keyboard configuration</title>
-<para>
-The most invasive change in the 2.6 kernels is a fundamental change of the -input layer. This change makes all keyboards look like <quote>normal</quote> 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. -</para>
-<para>
-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 -<quote>Select keymap from full list</quote> and selecting a <quote>pc</quote> keyboard. -</para>
-<para>
-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"/>. -</para>
-<para arch="i386">
-This issue is unlikely to affect the &arch-title; architecture as all -PS/2 and most <acronym>USB</acronym> keyboards will already be configured as a <quote>normal</quote> PC -keyboard.
-</para>
-<para arch="not-i386">Note that if you are using a <acronym>USB</acronym> keyboard, this -may be configured as either a <quote>normal</quote> PC keyboard or as a USB-MAC -keyboard. In the first case you will not be affected by this -issue.</para>
-</section>
-
-<section id="l2.6-mouse">
-<title>Mouse configuration</title>
-<para>
-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.
-</para>
-</section>
-
-<section id="l2.6-sound">
-<title>Sound configuration</title>
-<programlisting condition="fixme">TODO: Do we still need this for lenny?</programlisting> -<para>
-For the 2.6 kernel series the <acronym>ALSA</acronym> sound drivers are recommended over the older -<acronym>OSS</acronym> sound drivers. <acronym>ALSA</acronym> sound drivers are provided as modules by default. In -order for sound to work, the <acronym>ALSA</acronym> 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, -the <systemitem role="package">discover</systemitem> package installed. The -<systemitem role="package">alsa-base</systemitem> package also <quote>blacklists</quote> <acronym>OSS</acronym> -modules to prevent <command>discover</command> -from loading them. If you have <acronym>OSS</acronym> modules listed in -<filename>/etc/modules</filename>, you should remove them. -</para>
-</section>
-
-</section>
-
-<section id="nfs-common">
- <title><acronym>NFS</acronym> mounts now handled by nfs-common</title> -
+<section id="shell-diversions">
+ <title>Potential issues with diversions of /bin/sh</title>

<para>
- Since <systemitem role="package">util-linux</systemitem> 2.13 - <acronym>NFS</acronym> mounts are no longer handled by <systemitem - role="package">util-linux</systemitem> itself, but by <systemitem - role="package">nfs-common</systemitem>. Since not all systems - mount <acronym>NFS</acronym> shares and to avoid a standard - portmapper installation <systemitem - role="package">util-linux</systemitem> only suggests <systemitem - role="package">nfs-common</systemitem>. If you need to mount - <acronym>NFS</acronym> shares, make sure <systemitem - role="package">nfs-common</systemitem> is installed on your - system. The preinstallation script of the <systemitem - role="package">mount</systemitem> package checks whether - <acronym>NFS</acronym> mounts exist and aborts if - <filename>/usr/sbin/mount.nfs</filename> from <systemitem - role="package">nfs-common</systemitem> is not present or if - <systemitem role="package">nfs-common</systemitem> is - out-of-date. Either upgrade <systemitem - role="package">nfs-common</systemitem> or unmount any - <acronym>NFS</acronym> mounts prior to upgrading <systemitem - role="package">mount</systemitem>. + If you have previously added a local diversion for <literal>/bin/sh</literal>, + or modified the <literal>/bin/sh</literal> symlink to point to somewhere + other than <literal>/bin/bash</literal>, then you may encounter problems + when upgrading the <systemitem role="package">dash</systemitem> or + <systemitem role="package">bash</systemitem> packages. + Note that this includes changes made by allowing other packages (for example + <systemitem role="package">mksh</systemitem>) to become the default system + shell by taking over <literal>/bin/sh</literal>.

</para>
+ <para>
+ If you encounter any such issues, please remove the local diversion and + ensure that the symlinks for both <literal>/bin/sh</literal> and its + manual page point to the files provided by the <systemitem + role="package">bash</systemitem> package and then + <command>dpkg-reconfigure --force dash</command>. + </para>
+ <programlisting>
+ dpkg-divert --remove /bin/sh
+ dpkg-divert --remove /usr/share/man/man1/sh.1.gz +
+ ln -sf bash /bin/sh
+ ln -sf bash.1.gz /usr/share/man/man1/sh.1.gz + </programlisting>
</section>

-<section id="romanian-keyboard">
- <title>Change of Romanian (ro) keyboard layout</title> +<section>
+ <!-- bug#568126 -->
+ <title>Change in kernel policy regarding resource conflicts</title>

<para>
- Because of the upgrade to <systemitem - role="package">xkb-data</systemitem> version 1.3 in &releasename; - the default variant for Romanian (ro) layout is now producing the - correct ÈTMÈ characters (comma below) instead of ÅÅ£ (cedilla - below). Also some of the variants have been renamed. The old - variant names still work, but users are encouraged to update their - <filename>/etc/X11/xorg.conf</filename>. More info as well as - possible side effects due to this change are available in the - <ulink url="http://wiki.debian.org/L10N/Romanian/Lenny/Notes"> - wiki (Romanian language only)</ulink>. + The default setting for the acpi_enforce_resources parameter in the Linux + kernel has changed to be <quote><literal>strict</literal></quote> by + default. This can lead some legacy sensor drivers to be denied access to + the sensors' hardware. One workaround is to append + <quote><literal>acpi_enforce_resources=lax</literal></quote> to the kernel + command line.

</para>
</section>

-<section id="apache2">
+</section>
+
+<section id="apache2" condition="fixme">

<title>Upgrading apache2</title>
<para>
The apache2 default configuration has changed in some ways that @@ -440,7 +370,7 @@

</para>
</section>

-<section id="nis">
+<section id="nis" condition="fixme">
<title><acronym>NIS</acronym> and Network Manager</title> <indexterm><primary>NIS</primary></indexterm> <indexterm><primary>Network Manager</primary></indexterm> @@ -465,150 +395,376 @@
</para>
</section>

-<section id="mozilla-security">
-<title>Security status of Mozilla products</title> +<section id="ldap-gnutls">
+ <title><acronym>LDAP</acronym> support</title> + <indexterm><primary>LDAP</primary></indexterm> + <para>
+ A feature in the cryptography libraries used in the + <acronym>LDAP</acronym> libraries causes programs that use + <acronym>LDAP</acronym> and attempt to change their effective + privileges to fail when connecting to an <acronym>LDAP</acronym> + server using <acronym>TLS</acronym> or <acronym>SSL</acronym>. + This can cause problems for suid programs on systems using + <systemitem role="package">libnss-ldap</systemitem> like + <command>sudo</command>, <command>su</command> or + <command>schroot</command> and for suid programs that perform LDAP + searches like <systemitem role ="package">sudo-ldap</systemitem>. + </para>
+ <para>
+ It is recommended to replace the
+ <systemitem role="package">libnss-ldap</systemitem> package with + <systemitem role="package">libnss-ldapd</systemitem>, a newer library + which uses separate daemon (<command>nslcd</command>) for all + <acronym>LDAP</acronym> lookups. The replacement for + <systemitem role="package">libpam-ldap</systemitem> is + <systemitem role="package">libpam-ldapd</systemitem>. + </para>
+ <para>
+ Note that <systemitem role="package">libnss-ldapd</systemitem> recommends + the NSS caching daemon (<systemitem role="package">nscd</systemitem>) + which you should evaluate for suitability in your environment before + installing.
+ As an alternative to <systemitem role="package">nscd</systemitem> you + can consider <systemitem role="package">unscd</systemitem>. + </para>
+ <para>
+ Further information is available in bugs + <ulink url="&url-bts;566351">#566351</ulink> and + <ulink url="&url-bts;545414">#545414</ulink>. + </para>
+</section>
+
+
+<section id="sieve-port-number">
+<title><literal>sieve</literal> service moving to its IANA-allocated port</title> <para>
-<indexterm><primary>Mozilla</primary></indexterm> -The Mozilla programs <systemitem role="package">firefox</systemitem>, -<systemitem role="package">thunderbird</systemitem>, and -<systemitem role="package">sunbird</systemitem> (rebranded in Debian to -<systemitem role="package">iceweasel</systemitem>, <systemitem -role="package">icedove</systemitem>, and <systemitem -role="package">iceowl</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. +The IANA port allocated for ManageSieve is 4190/tcp, and the old port used +by <command>timsieved</command> and other managesieve software in many +distributions (2000/tcp) is allocated for Cisco SCCP usage, according to <ulink +url="http://www.iana.org/assignments/port-numbers">the IANA registry</ulink>. </para>
<para>
-<systemitem role="package">iceape</systemitem>, the unbranded version -of the <systemitem role="package">seamonkey</systemitem> internet -suite has been removed from &releasename; (with the exception of a few -internal library packages).
+Starting with the version 4.38 of the Debian <systemitem +role="package">netbase</systemitem> package, the <literal>sieve</literal> +service will be moved from port 2000 to port 4190 in the +<filename>/etc/services</filename> file. </para>
+<para>
+Any installs which used the <literal>sieve</literal> service name instead of a +numeric port number will switch to the new port number as soon as the services +are restarted or reloaded, and in some cases, immediately after +<filename>/etc/services</filename> is updated. +</para>
+<para>
+This will affect Cyrus IMAP. This may also affect other sieve-enabled +software such as DoveCot.
+</para>
+<para>
+In order to avoid downtime problems, mail cluster administrators using +Debian are urged to verify their Cyrus (and probably also DoveCot) installs, +and take measures to avoid services moving from port 2000/tcp to port +4190/tcp by surprise in either servers or clients. +</para>
+<para>
+It is worth noting that:
+<itemizedlist>
+<listitem>
+<para>
+<filename>/etc/services</filename> will only be automatically updated if you +never made any modifications to it. Otherwise, you will be presented with a +prompt by dpkg asking you about the changes. +</para>
+</listitem>
+<listitem>
+<para>
+You can edit <filename>/etc/services</filename> and change the +<literal>sieve</literal> port back to 2000 if you want (this is not +recommended, though).
+</para>
+</listitem>
+<listitem>
+<para>
+You can edit <filename>/etc/cyrus.conf</filename> and any other relevant +configuration files for your mail/webmail cluster (e.g. on the sieve web +frontends) ahead of time to force them all to a static port number. +</para>
+</listitem>
+<listitem>
+<para>
+You can configure cyrus master to listen on both ports (2000 and 4190) +at the same time, and thus avoid the problem entirely. This also allows for +a much more smooth migration from port 2000 to port 4190. +</para>
+</listitem>
+</itemizedlist>
+</para>
</section>

+
<section id="kde-desktop-changes">
<title>KDE desktop</title>
<para>
-There are no huge changes in the KDE Desktop Enviroment from the version -shipped in etch. Lenny ships an updated translation and service release of KDE -3.5 that is a mixture of 3.5.9 and 3.5.10. Some modules are labeled as version -3.5.9, but have been updated and include most of the same changes found in 3.5.10. -Overall, lenny ships 3.5.10 without the kicker improvements shipped in kdebase -and some bug fixes in kdepim.
+&Releasename; is the first Debian release to ship with the full support +for the next generation KDE that is based on Qt 4. +Most official KDE applications are at version 4.4.5 with the exception +of <systemitem role="package">kdepim</systemitem> that is at version 4.4.7. You +can read the <ulink url="http://www.kde.org/announcements/">announcements from +the KDE Project</ulink> to learn more about the changes. </para>
+
+<section id="kde-upgrading-from-kde3"> +<title>Upgrading from KDE 3</title>
+
<para>
-Lenny will be the last stable release including a KDE 3 series environment. +KDE 3 Desktop Environment is no longer supported in Debian &release;. +It will be automatically replaced by the new 4.4 series on upgrade. +As this is a major change, users should take some precautions in order +to ensure as smooth of an upgrade process as possible. </para>
+
+<important>
+<para>
+It is discouraged to upgrade while there is an active KDE 3 session +on the system. Otherwise, the process might render the running session +dysfunctional with the possibility of data loss. +</para>
+</important>
+
+<para>
+Upon the first login on the upgraded system, existing users will +be prompted with the Debian-KDE guided migration procedure called +<systemitem role="package">kaboom</systemitem> +which will assist in the process of migrating the user's personal data +and optionally backing up old KDE configuration. +For more information, visit
+<ulink url="http://pkg-kde.alioth.debian.org/kaboom.html">the Kaboom homepage</ulink>. +</para>
+
+<para>
+While KDE 3 based desktop environment is no longer supported, +users can still install and use some individual KDE 3 applications +since the core libraries and binaries of KDE 3 +(<systemitem role="package">kdelibs</systemitem>) and Qt 3 are +still available in Debian &release;. However, please note that these +applications might not be well integrated with the new environment. +What's more, neither KDE 3 nor Qt 3 will be supported in any form in the next +Debian release so if you are using them, you are strongly advised to port your +software to the new platform.
+</para>
</section>

-<section id="gnome-desktop-changes">
-<title>GNOME desktop changes and support</title> -<programlisting condition="fixme">TODO: Remove the next three paragraphs for lenny?</programlisting> -<para condition="fixme">
-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. +<section id="kde-metapackages">
+<title>New KDE metapackages</title>
+<para>
+As noted earlier, Debian &release; introduces a new set +of KDE related metapackages:
+
+<!-- Note to translators, do not translate '(KDE) Plasma Desktop' or 'KDE Plasma Netbook' --> +<itemizedlist>
+<listitem>
+<para>
+You are strongly advised to install the +<systemitem role="package">kde-standard</systemitem> +package for normal desktop usage.
+<systemitem role="package">kde-standard</systemitem> +will pull in the
+<ulink url="http://www.kde.org/workspaces/plasmadesktop/">KDE Plasma Desktop</ulink> +by default, and a selected set of commonly used applications. </para>
-<para condition="fixme">
-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.
+</listitem>
+<listitem>
+<para>
+If you want a minimal desktop you can install the +<systemitem role="package">kde-plasma-desktop</systemitem> +package and manually pick the applications you need. This is a rough +equivalent of the <systemitem role="package">kde-minimal</systemitem> +package as shipped in Debian &oldrelease;. </para>
-<para condition="fixme">
-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. +</listitem>
+<listitem>
+<para>
+For small form factor devices, there is an alternative environment +called
+<ulink url="http://www.kde.org/workspaces/plasmanetbook/">KDE Plasma Netbook</ulink> +that can be installed with the
+<systemitem role="package">kde-plasma-netbook</systemitem> package. +Plasma Netbook and Plasma Desktop can live in the same system +and the default can be configured in System Settings (replacement of the +former KControl).
</para>
+</listitem>
+<listitem>
<para>
+If you want a full set of official KDE applications, you have the possibility +to install the <systemitem role="package">kde-full</systemitem> package. +It will install KDE Plasma Desktop by default. +</para>
+</listitem>
+</itemizedlist>
+</para>
+</section>
+
+</section>
+
+<section id="gnome-desktop-changes">
+<title>GNOME desktop changes and support</title> +<para>
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://library.gnome.org/misc/release-notes/2.22/">GNOME 2.22 Release -Notes</ulink>.
+<ulink url="http://library.gnome.org/misc/release-notes/2.30/">GNOME 2.30 Release +Notes</ulink>. Specific issues are listed below. </para>
+
+<section>
+<title>GDM 2.20 and 2.30</title>
+<para>
+The GNOME Display Manager (GDM), is kept at version 2.20 for systems upgraded +from &oldreleasename;. This version will still be maintained for the squeeze +cycle but it is the last release to do so. Newly installed systems will get +GDM 2.30 instead, provided by the <systemitem role="package">gdm3</systemitem> +package. Because of incompatibilities between both versions, this upgrade is +not automatic, but it is recommended to install <systemitem +role="package">gdm3</systemitem> after the upgrade to &releasename;. This +should be done from the console, or with only one open GNOME session. Note +that settings from GDM 2.20 will <emphasis role="strong">not</emphasis> be +migrated. For a standard desktop system, however, simply installing +<systemitem role="package">gdm3</systemitem> should be enough. +</para>
</section>

-<section id="no-unicode">
-<title>No default support for Unicode in emacs21
</title> -<indexterm><primary>Unicode</primary></indexterm> +<section>
+<title>Device and other administrative permissions</title> <para>
-Emacs21 and emacs21-nox are not configured to use Unicode by default. For more -information and a workaround please see <ulink -url="&url-bts;419490">Bug #419490</ulink>. -Consider switching to <systemitem role="package">emacs22</systemitem>, -<systemitem role="package">emacs22-gtk</systemitem>, or <systemitem -role="package">emacs22-nox</systemitem>. +Specific permissions on devices are
+granted automatically to the user currently logged on physically to the +system: video and audio devices, network roaming, power management, +device mounting. The cdrom, floppy, audio, video, plugdev and powerdev +groups are no longer useful. See the <systemitem +role="package">consolekit</systemitem> documentation for more information. </para>
+<para>
+Most graphical programs requiring root permissions now rely on <ulink +url="http://www.freedesktop.org/wiki/Software/PolicyKit">PolicyKit</ulink> to +do so, instead of <systemitem role="package">gksu</systemitem>. The recommended +way to give a user administrative rights is to add it to the +<literal>sudo</literal> group.
+</para>
</section>

-<section id="openldapreplica">
- <title>slurpd/replica will no longer work</title> +<section>
+ <title>network-manager and ifupdown interaction</title>

<para>
- OpenLDAP has dropped support for <acronym>LDAP</acronym> - replication via the slurpd service in release 2.4.7. Existing - configurations need to be reconfigured for the - <acronym>LDAP</acronym> Sync Replication engine (syncrepl). More - verbose documentation can be found at <ulink - url="http://www.openldap.org/doc/admin24/replication.html">http://www.openldap.org/doc/admin24/replication.html</ulink>;. + Upon upgrading the <systemitem role="package">network-manager</systemitem> + package, interfaces configured in
+ <filename>/etc/network/interfaces</filename> to use + <acronym>DHCP</acronym> with no other options will be disabled in that + file, and handled by NetworkManager instead. Therefore the + <command>ifup</command> and <command>ifdown</command> commands will not + work. These interfaces can be managed using the NetworkManager frontends + instead, see <ulink
+ url="http://live.gnome.org/NetworkManager/SystemSettings">the + NetworkManager documentation</ulink>.

</para>
-</section>
-
-<section id="vga-output-bug">
- <title>Desktop not using full screen</title>

<para>
- The driver for Intel Mobile GM965 may wrongly detect a - <acronym>VGA</acronym> output and set the size of the screen to a - lower value to accomodate it. The symptom of this bug is that the - desktop manager will only use a fraction of the screen. Correct - behaviour can be forced by adding the following lines to the - <filename>/etc/X11/xorg.conf</filename> configuration file. - <programlisting>Section "Monitor"
- Identifier "VGA"
- Option "Ignore" "true"
-EndSection</programlisting>
- Please refer to the bug <ulink
- url="&url-bts;/496169">#496169</ulink> for more informations. + Conversely, any interfaces configured in + <filename>/etc/network/interfaces</filename> with more options will be + ignored by NetworkManager. This applies in particular to wireless + interfaces used during the installation of Debian (see bug <ulink + url="&url-bts;606268">#606268</ulink>).

</para>
</section>

-<section arch="sparc">
- <title>&releasename; kernel fails to boot on Sparc workstations with PCI-Express</title> +</section>

+<section id="graphics">
+ <title>Graphics stack changes</title>

<para>
- Due to an unfortunate interaction of a kernel fix with PCI Express - subsystem, Lenny default kernel will fail to boot on Sparc - workstations with PCI Express slots, like Ultra 25 and Ultra - 45. As this problem has been discovered very late in the release - cycle, we were unable to include a fix in the original Lenny - release, but we'll do our best to eliminate the problem for the - first point release.
- <indexterm><primary>Sun Ultra 25</primary></indexterm> - <indexterm><primary>Sun Ultra 45</primary></indexterm> - <indexterm><primary>PCI Express</primary></indexterm> + There have been a number of changes to the X stack in Debian &release;. + This section lists the most important and user-visible.

</para>
-</section>

-<section>
- <title><acronym>DHCP</acronym> failover issue</title> + <section>
+ <title>Obsolete Xorg drivers</title> + <para>

+      The <literal>cyrix</literal>, <literal>imstt</literal>,
+      <literal>sunbw2</literal> and <literal>vga</literal> Xorg video drivers
+      are no longer provided.  Users should switch to a generic such as
+      <literal>vesa</literal> or <literal>fbdev</literal> instead.

+ </para>
+ <para>

+      The old <literal>via</literal> driver was no longer maintained, and has
+      been replaced by the <literal>openchrome</literal> driver, which will be
+      used automatically after the upgrade.

+ </para>
+ <para>

+      The <literal>nv</literal> and <literal>radeonhd</literal> drivers are
+      still present in this release, but are deprecated.  Users should
+      consider the <literal>nouveau</literal> and <literal>radeon</literal>
+      drivers instead, respectively.

+ </para>
+ <para>

+      The <literal>calcomp</literal>, <literal>citron</literal>,
+      <literal>digitaledge</literal>, <literal>dmc</literal>,
+      <literal>dynapro</literal>, <literal>elo2300</literal>,
+      <literal>fpit</literal>, <literal>hyperpen</literal>,
+      <literal>jamstudio</literal>, <literal>magellan</literal>,
+      <literal>microtouch</literal>, <literal>mutouch</literal>,
+      <literal>palmax</literal>, <literal>spaceorb</literal>,
+      <literal>summa</literal>, <literal>tek4957</literal> and
+      <literal>ur98</literal> X input drivers have been discontinued and are
+      not included in this release.  Users of these devices might want to
+      switch to a suitable kernel driver and the evdev X driver.  For many
+      serial devices, the <command>inputattach</command> utility allows
+      attaching them to a Linux input device which can be recognized by the
+      <literal>evdev</literal> X driver.

+ </para>
+ </section>

<appendix id="ap-old-stuff" lang="en"> -<title>Managing your &oldreleasename; system</title> +<title>Managing your &oldreleasename; system before the upgrade</title> <para>
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 @@ -29,27 +29,29 @@
<title>Checking your sources list</title> <para>
If any of the lines in your <filename>/etc/apt/sources.list</filename> refer to -'stable', you are effectively already <quote>using</quote> &releasename;. If you have already run +'stable', you are effectively already <quote>using</quote> &releasename;. This +might not be what you want if you are not ready yet for the upgrade. If +you have already run
<literal>apt-get update</literal>, you can still get back without problems following the procedure below.
</para>
<para>
-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. +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. </para>
<para>
Open the file <filename>/etc/apt/sources.list</filename> with your favorite -editor (as <literal>root</literal>) and check all lines beginning with <literal>deb -http:</literal>; or <literal>deb ftp:</literal> for a reference to -<quote><literal>stable</literal></quote>. If you find any, change <literal>stable</literal> -to <literal>&oldreleasename;</literal>. +editor (as <literal>root</literal>) and check all lines beginning with +<literal>deb http:</literal>; or <literal>deb ftp:</literal> for a reference to +<quote><literal>stable</literal></quote>. If you find any, change +<literal>stable</literal> to <literal>&oldreleasename;</literal>. </para>
<para>
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 an &oldreleasename; or a &releasename; -archive.
+to check for yourself if the location they refer to contains an +&oldreleasename; or a &releasename; archive. </para>
<important>
<para>
@@ -71,5 +73,27 @@
</para>
</section>

+<section id="switch-utf8">
+
+<title>Upgrade legacy locales to UTF-8</title> +<para>
+If your system is localised and is using a locale that is not based on UTF-8 +you should strongly consider switching your system over to using UTF-8 locales. +In the past, there have been bugs identified that manifest itself only when +using a non-UTF-8 locale. On the desktop, such legacy locales are supported +through ugly hacks in the libraries internals, and we cannot decently provide +support for users who still use them.
+</para>
+<para>
+To configure your system's locale you can run <command>dpkg-reconfigure +locales</command>. Ensure you select an UTF-8 locale when you are presented +with the question asking which locale to use as a default in the system. In +addition, you should review the locale settings of your users and ensure that +they do not have legacy locales definitions in their configuration +environment.
+</para>
+
+</section>
+
</appendix>

. Added: 37 Removed: 13
Showing diffs for release-notes.dbk... (ver: 6592:)Index: release-notes.dbk


--- release-notes.dbk (revisión: 6592) +++ release-notes.dbk (copia de trabajo) @@ -1,6 +1,7 @@
<?xml version='1.0' encoding='utf-8'?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ + <!ENTITY % languagedata SYSTEM "language.ent" > %languagedata;

<!ENTITY % shareddata SYSTEM "../release-notes.ent" > %shareddata; ]>

@@ -13,16 +14,31 @@

<bookinfo>
<editor>
+ <firstname>Steve</firstname>
+ <surname>Langasek</surname>
+ <email>vorlon@debian.org</email>
+ </editor>
+ <editor>

     <firstname>W. Martin</firstname>
     <surname>Borgert</surname>
     <email>debacle@debian.org</email>

</editor>
+ <editor>
+ <firstname>Javier</firstname>
+ <surname>Fernandez-Sanguino</surname> + <email>jfs@debian.org</email>
+ </editor>
+ <editor>
+ <firstname>Julien</firstname>
+ <surname>Cristau</surname>
+ <email>jcristau@debian.org</email> + </editor>

<editor condition="fixme">

     <firstname></firstname>
     <surname></surname>
     <contrib>There were more people!</contrib>

</editor>
- <pubdate>2009-02-14</pubdate>
+ <pubdate>2010-11-12</pubdate>

<legalnotice>

     <para>
     This document is free software; you can redistribute it and/or modify
@@ -44,7 +60,7 @@
     </para>
 
     <para>The license text can also be found at <ulink

- url="http://www.gnu.org/copyleft/gpl.html"/> + url="http://www.gnu.org/licenses/gpl-2.0.html"/>

     and <filename>/usr/share/common-licenses/GPL-2</filename> on
     &debian;.</para>

</legalnotice>
@@ -76,7 +92,7 @@

     <author>
       <firstname>Adam</firstname>
       <surname>Di Carlo</surname>
-      <contrib>previous release</contrib>
+      <contrib>previous releases</contrib>
     </author>,
     <author>
       <firstname>Andreas</firstname>
@@ -127,11 +143,11 @@
       <firstname>Esko</firstname>
       <surname>Arajärvi</surname>
       <contrib>rework X11 upgrade</contrib>

- </author>
+ </author>,

     <author>
       <firstname>Frans</firstname>
       <surname>Pop</surname>
-      <contrib>previous release</contrib>
+      <contrib>previous release (Etch)</contrib>
     </author>,
     <author>
       <firstname>Giovanni</firstname>
@@ -146,7 +162,7 @@
     <author>
       <firstname>Javier</firstname>
       <surname>Fernández-Sanguino Peña</surname>
-      <contrib>previous release</contrib>
+      <contrib>previous release (Etch), Squeeze release</contrib>
     </author>,
     <author>
       <firstname>Jens</firstname>
@@ -161,7 +177,7 @@
     <author>
       <firstname>Josip</firstname>
       <surname>Rodin</surname>
-      <contrib>previous release</contrib>
+      <contrib>previous releases</contrib>
     </author>,
     <author>
       <firstname>Justin B</firstname>
@@ -216,7 +232,7 @@
     <author>
       <firstname>Rob</firstname>
       <surname>Bradford</surname>
-      <contrib>previous release</contrib>
+      <contrib>previous release (Etch)</contrib>
     </author>,
     <author>
       <firstname>Samuel</firstname>
@@ -241,7 +257,7 @@
     <author>
       <firstname>Steve</firstname>
       <surname>Langasek</surname>
-      <contrib>previous release</contrib>
+      <contrib>previous release (Etch)</contrib>
     </author>,
     <author>
       <firstname>Tobias</firstname>

@@ -279,32 +295,7 @@

</para>
</appendix>

-<appendix>
- <title>Lenny dedicated to Thiemo Seufer</title>

<glossary id="relnotes-glossary">
@@ -366,7 +357,7 @@

</glossentry>
<glossentry>
<glossterm>LSB</glossterm>
- <glossdef><para>Linux Standards Base</para></glossdef> + <glossdef><para>Linux Standard Base</para></glossdef>

</glossentry>
<glossentry>
<glossterm>LVM</glossterm>
@@ -405,6 +396,14 @@

<glossdef><para>Serial Advanced Technology Attachment</para></glossdef> </glossentry>
<glossentry>
+ <glossterm>SSL</glossterm>
+ <glossdef><para>Secure Sockets Layer</para></glossdef> + </glossentry>
+ <glossentry>
+ <glossterm>TLS</glossterm>
+ <glossdef><para>Transport Layer Security</para></glossdef> + </glossentry>
+ <glossentry>

     <glossterm>USB</glossterm>
     <glossdef><para>Universal Serial Bus</para></glossdef>

</glossentry>
. Added: 35 Removed: 36
../en/showdiffs.sh: (No es un recurso versionado)

svn: Hubo un problema; vea otros informes de errores para más detalles ERROR: showdiffs.sh has not a correct English version: ENG_SVN_VER=$(sed -n 's/\(.\)/\1/p' $i) Showing diffs for upgrading.dbk... (ver: 6668:)Index: upgrading.dbk


--- upgrading.dbk       (revisión: 6668)
+++ upgrading.dbk       (copia de trabajo)

@@ -5,7 +5,7 @@
]>

<chapter id="ch-upgrading" lang="en">
-<title>Upgrades from previous releases</title> +<title>Upgrades from Debian &oldrelease; (&oldreleasename;)</title> <section id="backup">
<title>Preparing for the upgrade</title> <para>
@@ -26,8 +26,10 @@
<para>
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). +<filename>/var/lib/apt/extended_states</filename> and the output of +<literal>dpkg --get-selections ""</literal> (the quotes are important). If +you use <command>aptitude</command> to manage packages on your system, you +will also want to back up <filename>/var/lib/aptitude/pkgstates</filename>. </para>
<para>
The upgrade process itself does not modify anything in the @@ -49,55 +51,86 @@
executing the upgrade.
</para>

-<section id="upgrading-kernel">
- <title>Make sure you are on a suitable kernel</title> - <para>
- &releasename;'s version of <systemitem - role="package">glibc</systemitem> will not work with kernels older - than <literal>2.6.8</literal> on any architecture and some - architectures have higher requirements. We strongly recommend that - you upgrade to and test an &oldreleasename; - <literal>2.6.18</literal> or <literal>2.6.24</literal> kernel or a - custom kernel of at least version <literal>2.6.18</literal> before - beginning the upgrade process.
- </para>
</section>

-</section>
-
<section id="inform-users">
<title>Inform users in advance</title> <para>
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.
+working.
</para>
<para>
If you wish to take extra precautions, back up or unmount the <filename>/home</filename> partition before upgrading. </para>
<para>
-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.
+You will have to do a kernel upgrade when upgrading to &releasename;, so a +reboot will be necessary.
+<!-- Not for Squeeze:
+Typically, this will be done after the upgrade is finished. --> </para>
</section>

+<!-- Based on information/complains from upgrade-reports, such as #602797 --> +<section id="services-downtime">
+<title>Prepare for downtime on services</title> +
+<para>
+During the upgrade process, there might be services associated with packages +that will be include in the upgrade. If this is the case, these services might +be stopped while the packages that are going to be upgraded are being replaced +and configured. During this time, these services will not be available. +</para>
+
+<para>
+The precise downtime for these service will vary depending on the number of +packages being upgraded in the system, and it also includes the time the system +administrator answers the configuration questions from different package +upgrades (if any). Notice that if the upgrade process is left unattended and +the system requests input throughout the upgrade there is a high +possibility of services being unavailable<footnote><para>If the debconf +priority is set to a very high level you might prevent configuration prompts, +but services that rely on default answers that are not applicable to your +system will fail to start.</para></footnote> for a significant period of time. +</para>
+
+<para>
+If the system being upgraded provides critical services for your users or +network<footnote><para>For example: DNS or DHCP services, specially when +there is no redundancy or failover. In the DHCP case end-users might be disconnected +from the network if the lease time is lower than the time it takes for the +upgrade process to complete.</para></footnote>, you can reduce the downtime if +you do a minimal system upgrade, as described in <xref +linkend="minimal-upgrade"/>, followed by a kernel upgrade and reboot (see <xref +linkend="upgrading-udev"/>), and then upgrade the packages associated with your +critical services. Upgrade these packages prior to doing the full upgrade +described in <xref linkend="upgrading-full"/>. This way you can ensure that +these critical services are running and available through the full upgrade +process, and their downtime is reduced. +</para>
+
+</section>
+
<section id="recovery">
<title>Prepare for recovery</title>
<para>
-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.
+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. </para>
<para>
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.
</para>
+
+<!-- FIXME: Is there a risk in Lenny for this to happen? --> +<!-- Another option would be an automatic reboot to a previous kernel using +Davor Ocelic's testnet script or similar --> <para>
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 @@ -108,6 +141,7 @@
accidentally in the middle of an upgrade there is a chance you will need to recover using a local console.
</para>
+<!-- FIXME: The next paragraph might not be true for Lenn? --> <para>
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 @@ -120,6 +154,9 @@
system and <literal>chroot</literal> into it to investigate and fix the problem.
</para>
+
+<!-- FIXME: Consider putting this option first, as it should be the +recommended rescue method -->
<para>
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 @@ -164,8 +201,16 @@
<para>
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.
+<command>ssh</command> link.
</para>
+<important>
+ <para>
+ If you are using some VPN services (such as <systemitem + role="package">tinc</systemitem>) they might not be available + throughout the upgrade process. Please see + <xref linkend="services-downtime"/>. + </para>
+</important>
<para>
In order to gain extra safety margin when upgrading remotely, we suggest that you run upgrade processes in the virtual console provided by the @@ -193,29 +238,16 @@

</section>

-<section arch="i386;amd64" id="prepare-initramfs"> - <title>Prepare initramfs for <acronym>LILO</acronym><indexterm><primary>LILO</primary></indexterm></title> - <para>
- Users using the <acronym>LILO</acronym> bootloader should note that the default - settings for <systemitem
- role="package">initramfs-tools</systemitem> now generate an - initramfs that is too large for <acronym>LILO</acronym> to load. Such users should - either switch to <systemitem role="package">grub</systemitem>, or - edit the file
- <filename>/etc/initramfs-tools/initramfs.conf</filename>, changing - the line <programlisting>MODULES=most</programlisting> to read - <programlisting>MODULES=dep</programlisting></para> -
- <para>
- Note, however, that doing this will cause <systemitem - role="package">initramfs-tools</systemitem> to install onto the - initramfs only those modules that are required for the particular - hardware that it is being run on. If you want to generate boot - media that will work on more hardware than just the machine you're - generating it on, you should leave the line as - <programlisting>MODULES=most</programlisting> and make sure you do - not use <acronym>LILO</acronym>.
- </para>
+<section id="purge-splashy">
+<title>Remove conflicting packages</title> +<para>
+Due to bug <ulink url="&url-bts;512951">#512951</ulink>, the <systemitem +role="package">splashy</systemitem> package needs to be purged prior to the +upgrade.
+<screen>
+ # apt-get purge splashy
+</screen>
+</para>
</section>

</section>
@@ -230,10 +262,18 @@
before you begin upgrading.
</para>
<para>
+Direct upgrades from Debian releases older than &oldrelease; (&oldreleasename;) +are not supported.
+Please follow the instructions in the <ulink +url="http://www.debian.org/releases/&oldreleasename;/releasenotes">Release +Notes for &debian; &oldrelease;</ulink> to upgrade to &oldrelease; first. +</para>
+<para>
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"/>. </para>
+
<section id="review-actions">
<title>Review actions pending in package manager</title> <para>
@@ -325,13 +365,13 @@
upgraded.
</para>
<para>
-The <quote>hold</quote> package state for <command>aptitude</command> can be changed using: +The <quote>hold</quote> package state for <command>apt-get</command> can be changed using: </para>
<screen>
- aptitude hold <replaceable>package_name</replaceable> + echo <replaceable>package_name</replaceable> hold | dpkg --set-selections </screen>
<para>
-Replace <literal>hold</literal> with <literal>unhold</literal> to unset the +Replace <literal>hold</literal> with <literal>install</literal> to unset the <quote>hold</quote> state.
</para>
<para>
@@ -352,6 +392,7 @@

</para>
</section>

+<!-- FIXME: REVIEW for Squeeze this was written for Lenny - drop? (jfs) --> <section id="userbackports">
<title>Unofficial sources and backports</title> <para>
@@ -372,61 +413,9 @@
<xref linkend="trouble"/> has some information on how to deal with file conflicts if they should occur.
</para>
-<section>
- <title>Using <literal>backports.org</literal> packages</title> - <para>
- <literal>backports.org</literal> is a semi-official repository - provided by &debian; developers, which provides newer packages for - the stable release, based on a rebuild from the packages from the - <quote>testing</quote> archive.
- </para>
- <para>
- The <literal>backports.org</literal> repository mainly contains packages - from <quote>testing</quote>, with reduced version numbers - so that the upgrade path from &oldreleasename; backports to - &releasename; still works. However, there are a few backports - which are made from unstable: security updates, plus the following - exceptions: Firefox, the Linux kernel, OpenOffice.org, and X.Org. - </para>
- <para>
- If you do not use one of these exceptions, you can safely upgrade - to &releasename;. If you use one of these exceptions, set the - <literal>Pin-Priority</literal> (see <citerefentry> <refentrytitle>apt_preferences</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>) - temporarily to <literal>1001</literal> for all packages from &releasename;, - and you should be able to do a safe dist-upgrade too. See the - <ulink
- url="http://backports.org/dokuwiki/doku.php?id=faq">backports - FAQ</ulink>.
- </para>
-</section>
-</section>

</section>

-<section id="handle-conflict">
-<title>Manually unmarking packages</title> -<para>
-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:
-</para>
-<screen>
- aptitude unmarkauto openoffice.org vim -</screen>
-<para>
-And 2.6 kernel images if you have installed them using a kernel metapackage: -</para>
-<screen>
-
aptitude unmarkauto $(dpkg-query -W 'kernel-image-2.6.
' | cut -f1) -</screen>
-<note>
- <para>
- You can review which packages are marked as <emphasis>auto</emphasis> in - aptitude by running:
- </para>
- <screen># aptitude search 'i~M'</screen> -</note>
</section>

<section id="upgrade-process">
@@ -444,22 +433,6 @@
hard disk, then <acronym>CD-ROM</acronym>s, and then HTTP/FTP mirrors). </para>

-<tip>
- <para>
- You might need to add an <acronym>GPG</acronym> checking exception - for <acronym>DVD</acronym>s and <acronym>CD-ROM</acronym>s. Add - the following line to <filename>/etc/apt/apt.conf</filename>, if - it's not already in
- <filename>/etc/apt/apt.conf.d/00trustcdrom</filename>: -
- <programlisting>APT::Authentication::TrustCDROM "true";</programlisting> -
- This does not work with
- <acronym>DVD</acronym>/<acronym>CD-ROM</acronym> image files, - however.
- </para>
-</tip>
-
<para>
A release can often be referred to both by its codename (e.g. <literal>&oldreleasename;</literal>, <literal>&releasename;</literal>) and by @@ -471,6 +444,7 @@
If you use the status name instead, you will just see loads of updates for packages available as soon as a release has happened. </para>
+
<section id="network">
<title>Adding APT Internet sources</title> <para>
@@ -588,9 +562,11 @@
<title>Upgrading packages</title>
<para>
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.
+use the package management tool <command>apt-get</command>. In previous +releases, <command>aptitude</command> was recommended for this purpose, but +recent versions of <command>apt-get</command> provide equivalent +functionality and also have shown to more consistently give the desired +upgrade results.
</para>
<para>
Don't forget to mount all needed partitions (notably the root and @@ -606,12 +582,13 @@
any sources entries pointing to &oldreleasename;. <note>
<para>
- Source lines for a CD-ROM will often refer to + Source lines for a CD-ROM might sometimes refer to

     <quote><literal>unstable</literal></quote>; although this may be confusing, you
     should <emphasis>not</emphasis> change it.

</para>
</note>
</para>
+
<section id="record-session">
<title>Recording the session</title>
<para>
@@ -630,7 +607,7 @@
</para>
<para>
The typescript will also allow you to review information that has scrolled -off-screen. Just switch to VT2 (using +off-screen. If you are at the system's console, just switch to VT2 (using <keycombo action='simul'><keycap>Alt</keycap><keycap>F2</keycap></keycombo>) and, after logging in, use
<literal>less -R ~root/upgrade-&releasename;.script</literal> to view @@ -642,8 +619,8 @@
</para>

<programlisting condition="fixme">
-TODO: Could mention the script I provided in 400725 which is useful if you -have not dumped the timing file
+TODO: (jfs) Could mention the script I provided in #400725 which is useful if +you have not dumped the timing file
</programlisting>

<para>
@@ -663,13 +640,8 @@
This is done by executing:
</para>
<screen>
- aptitude update
+
apt-get update
</screen>
-<para>
-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. -</para>
</section>

<section id="sufficient-space">
@@ -677,7 +649,7 @@
<para>
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 +linkend="upgrading-full"/>. 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 @@ -691,16 +663,16 @@
difficult to recover from.
</para>
<para>
-Both <command>aptitude</command> and <systemitem role="package">apt</systemitem> will show you -detailed information of the disk space needed for the installation. Before -executing the upgrade, you can see this estimate by running: +<command>apt-get</command> can show you detailed information of the disk +space needed for the installation. Before executing the upgrade, you can see +this estimate by running:
</para>
<screen>
- aptitude -y -s -f --with-recommends dist-upgrade + apt-get -o APT::Get::Trivial-Only=true dist-upgrade [ ... ]
XXX upgraded, XXX newly installed, XXX to remove and XXX not upgraded. -Need to get xx.xMB/yyyMB of archives. After unpacking AAAMB will be used. -Would download/install/remove packages. +Need to get xx.xMB of archives.
+After this operation, AAAMB of additional disk space will be used. </screen>
<note>
<para>
@@ -712,8 +684,16 @@
space.
</para>
</note>
+
<para>
-If you do not have enough space for the upgrade, make sure you free up space +If you do not have enough space for the upgrade, <command>apt-get</command> +will warn you with a message like this: +</para>
+<screen>
+E: You don't have enough free space in /var/cache/apt/archives/. +</screen>
+
+<para>In this situation, make sure you free up space beforehand. You can:
</para>
<itemizedlist>
@@ -721,8 +701,8 @@
<para>
Remove packages that have been previously downloaded for installation (at <filename>/var/cache/apt/archives</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. +running <command>apt-get clean</command> will remove all previously downloaded +package files.
</para>
</listitem>
<listitem>
@@ -749,14 +729,12 @@
<para>
You can list packages that take up most of the disk space with <systemitem role="package">aptitude</systemitem>. Start -<command>aptitude</command> into <emphasis>visual mode</emphasis>, +<command>aptitude</command> in <quote>visual mode</quote>, select <menuchoice><guimenu>Views</guimenu><guimenuitem>New Flat Package -List</guimenuitem></menuchoice> (this menu entry is available only after etch -version), press <keycap>l</keycap> and enter <literal>~i</literal>, press -<keycap>S</keycap> and enter <literal>~installsize</literal>, then it -will give you nice list to work with. Doing this after upgrading -<systemitem role="package">aptitude</systemitem> should give you -access to this new feature.
+List</guimenuitem></menuchoice>, press <keycap>l</keycap> and enter +<literal>~i</literal>, press <keycap>S</keycap> and enter +<literal>~installsize</literal>, then it will give you nice list to work +with.
</para>
</listitem>
<listitem>
@@ -771,10 +749,11 @@
</listitem>
<listitem>
<para>
-Temporarily move to another system, or permanently remove, system logs residing -under <filename>/var/log/</filename>.
+ Temporarily move to another system, or permanently remove, system logs + residing under <filename>/var/log/</filename>. </para>
</listitem>
+
<listitem>
<para>
Use a temporary <filename>/var/cache/apt/archives</filename>: You @@ -833,7 +812,19 @@

is mounted on your system.
</para>
</listitem>
+
+<listitem>
+ <para>
+ Do a minimal upgrade of the system (see <xref linkend="minimal-upgrade"/>) + or partial upgrades of the system followed by a full upgrade. + This will make it possible to upgrade the system partially, and + allow you to clean the package cache before the full upgrade. + </para>
+</listitem>
+
</itemizedlist>
+
+
<para>
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 @@ -841,151 +832,125 @@
</para>
</section>

-<section id="aptupgrade1st">
- <title>Upgrade apt and/or aptitude first</title> - <para>
- Several bug reports have shown that the versions of the <systemitem - role="package">aptitude</systemitem> and <systemitem - role="package">apt</systemitem> packages in etch are often unable to - handle the upgrade to &releasename;. In &releasename;, <systemitem - role="package">apt</systemitem> is better at dealing with complex chains - of packages requiring immediate configuration and <systemitem - role="package">aptitude</systemitem> is smarter at searching for - solutions to satisfy the dependencies. These two features - are heavily involved during the dist-upgrade to &releasename;, so it - is necessary to upgrade these two packages before upgrading - anything else. For <systemitem role="package">apt</systemitem>, run: - <screen> apt-get install apt</screen> - and for <systemitem role="package">aptitude</systemitem> (if you have - it installed) run:
- <screen>
aptitude install aptitude</screen> - </para>
- <para>
- 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 might be disconnected.
- <indexterm><primary>SELinux</primary></indexterm> - </para>
-</section>
-<section id="aptconvert">
- <title>Using aptitude's list of automatically-installed packages with apt</title> - <para>
- <systemitem role="package">aptitude</systemitem> maintains a list - of packages that were installed automatically (for instance, as - dependencies of another package). In &releasename;, <systemitem - role="package">apt</systemitem> now has this feature as well. - </para>
- <para>
- The first time the &releasename; version of <systemitem - role="package">aptitude</systemitem> is run, it will read in its - list of automatically installed packages and convert it for use - with the &releasename; version of <systemitem - role="package">apt</systemitem>. If you have <systemitem - role="package">aptitude</systemitem> installed, you should at - least issue one <command>aptitude</command> - command to do the conversion. One way to do this is by searching for - a non-existent package:
- <screen># aptitude search "?false"</screen> -</para>
-</section>

<section id="minimal-upgrade">
<title>Minimal system upgrade</title>
<para>
-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>. +In some cases, doing the full upgrade (as described below) directly might +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 upgrade as described in <xref +linkend="upgrading-full"/>.
</para>
<para>
-First, run:
+To do this first, run:
</para>
<screen>
- aptitude upgrade
+
apt-get upgrade
</screen>
<para>
This has the effect of upgrading those packages which can be upgraded without requiring any other packages to be removed or installed. </para>
+
<para>
-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. +The minimal system upgrade can also be useful when the system is tight on space +and a full upgrade cannot be run due to space constrains. </para>
-<para>
-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 more information about -packages obsoleted in &releasename;, see <xref linkend="obsolete"/>. -</para>
+
</section>

-<section id="upgrading-kernel-obsolete" condition="fixme"> -<title>Upgrading the kernel</title>
-<programlisting condition="fixme">TODO: This is outdated for lenny, right?</programlisting> +<!-- For more information See BTS #571255 and #602397 --> +<!-- NOTE (jfs-2010-11-06) Upgrade tests for Squeeze have shown +that this is not absolutely required, users could do a dist-upgrade +and then reboot. This is, however, the recommended path to be on the +safe side -->
+<section id="upgrading-udev">
+<title>Upgrading the kernel and udev</title> <para>
-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.
+The <systemitem role="package">udev</systemitem> version in &releasename; +requires a kernel of version 2.6.26 or newer with the +<literal>CONFIG_SYSFS_DEPRECATED</literal> option disabled and the +<literal>CONFIG_INOTIFY_USER</literal> and +<literal>CONFIG_SIGNALFD</literal> options enabled. Because the standard +Debian kernels in &oldreleasename; (version 2.6.26) have +<literal>CONFIG_SYSFS_DEPRECATED</literal> enabled, and the <systemitem +role="package">udev</systemitem> version in &oldreleasename; will not +provide all the functionality expected by the latest kernels, special care +must be taken when upgrading to avoid putting your system in an unbootable +state.
</para>
<para>
-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.) +Booting the 2.6.26 kernel from &oldreleasename; with the <systemitem +role="package">udev</systemitem> from &releasename; may result in a failure +to correctly assign names to network devices, and will also fail to apply +certain additional permissions to block devices (such as access by the +<literal>disk</literal> group).
+The software itself will appear to be working, but some rules +(for example, network-based rules) will not be loaded properly. +It is therefore strongly recommended that +you upgrade the kernel on its own at this point, to ensure a compatible +kernel is available before upgrading <systemitem +role="package">udev</systemitem>.
</para>
+<!-- FIXME: Review if we have to upgrade the kernel and udev +at the same time here -->
<para>
-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. -</para>
-<para>
To proceed with this kernel upgrade, run: </para>
<screen>
- aptitude install linux-image-2.6-<replaceable>flavor</replaceable> + apt-get install linux-image-2.6-<replaceable>flavor</replaceable> </screen>
<para>
See <xref linkend="kernel-metapackage"/> for help in determining which flavor of kernel package you should install.
</para>
+<para arch="i386;amd64">
+Users of the <systemitem role="package">grub</systemitem> bootloader should +make sure that <command>update-grub</command> is run as part of the kernel +upgrade, or run it manually.
+</para>
<para>
-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. +Immediately after upgrading the kernel, you should also install +the new <systemitem role="package">udev</systemitem> to minimize the risk of +other incompatibilities caused by using the old udev with a new kernel +<footnote><para>There are also known incompatibilities between the old kernel +and the new <systemitem role="package">udev</systemitem>. If you find +issues after the reboot with the new kernel you will have to downgrade the +<systemitem role="package">udev</systemitem> in order +to use the old one.</para></footnote>. +You can do this by running:
</para>
+<!-- TODO (2010-11-6): Needs to be tested, maybe the ugprade to udev might not +work due to the preinst checks introduced by the maintainer --> +<screen>
+# apt-get install udev
+</screen>
+
+<para>
+Once you have upgraded both the kernel and <systemitem role="package">udev</systemitem> the system should be rebooted. +</para>
+
</section>

-<section id="upgrading-other">
-<title>Upgrading the rest of the system</title> +
+<section id="upgrading-full">
+<title>Upgrading the system</title>
<para>
-You are now ready to continue with the main part of the upgrade. Execute: +Once you have taken the previous steps, you are now ready to continue +with the main part of the upgrade. Execute: </para>
<screen>
- aptitude dist-upgrade
+
apt-get dist-upgrade
</screen>
+ <note>
+ <para>

+      The upgrade process for other releases recommended the
+      use of <command>aptitude</command> for the upgrade. This
+      tool is not recommended for upgrades from &oldreleasename; to
+      &releasename;.

+ </para>
+ </note>
<para>
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 @@ -1004,34 +969,63 @@
changing the install status of another package will be left at their current version (displayed as <quote>held back</quote>). This can be resolved by either using <command>aptitude</command> to choose these packages for installation or by -trying <literal>aptitude -f install
+trying <literal>apt-get -f install
<replaceable>package</replaceable></literal>. </para>
</section>

-<section id="get-signatures" condition="fixme"> -<title>Getting package signatures</title> -<programlisting condition="fixme">TODO: Can be removed for lenny, right?</programlisting> +</section>
+
+<section id="trouble">
+<title>Possible issues during upgrade</title> +
<para>
-After the upgrade, with the new version of <systemitem role="package">apt</systemitem> you can now -update your package information, which will include the new package signature -checking mechanism:
+The following sections describe known issues that might appear +during an upgrade to &releasename;.
</para>
-<screen>
-# aptitude update
-</screen>
+
+<section id="cryptoloop">
+<title>cryptoloop support not included in the &releasename; Linux kernel</title> <para>
-The upgrade will have already retrieved and enabled the signing keys for -Debian's package archives. If you add other (unofficial) package sources, -<systemitem role="package">apt</systemitem> 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"/>. +Support for cryptoloop has been dropped from the Linux kernel packages +included in Debian &release;. Existing installations using cryptoloop need to +be transitioned to dm-crypt before the upgrade. </para>
</section>

-<section id="trouble">
-<title>Possible issues during upgrade</title> +<section id="expected-removals">
+<title>Expected removals</title>
<para>
+The upgrade process to &releasename; might ask for removal of +packages in the system. The precise list of packages will vary depending on the +set of packages that you have installed. These release notes give general +advice on these removals, but if in doubt, it is recommended that you examine +the package removals proposed by each method before proceeding. +</para>
+
+<!-- FIXME: This needs to be reviewed based on real upgrade logs (jfs) --> +<!-- Alternative, another source of information is the UDD +'not-in-testing' page: http://udd.debian.org/bapase.cgi?t=testing --> +<para>
+Some common packages that are expected to be removed include: +<systemitem role="package">autofs</systemitem> (replaced by +<systemitem role="package">autofs5</systemitem>), +<systemitem role="package">dhcp3</systemitem> (replaced by +<systemitem role="package">isc-dhcp</systemitem>), +<systemitem role="package">madwifi-source</systemitem>, +<systemitem role="package">python-setuptools</systemitem> and +<systemitem role="package">python2.4</systemitem> (replaced by +<systemitem role="package">python2.6</systemitem>). +
+For more information about packages obsoleted in &releasename;, see <xref +linkend="obsolete"/>.
+</para>
+
+</section>
+
+<section id="apt-error-operation">
+<title>Errors running aptitude or apt-get</title> +<para>
If an operation using <command>aptitude</command>, <command>apt-get</command>, or <command>dpkg</command> fails with the error </para>
@@ -1052,18 +1046,24 @@
<para>
This assumes that you do not yet have this variable set in that file. </para>
+
+</section>
+
+<section id="conflicts-loops">
+<title>Conflicts or Pre-Depends loops</title> +
<para>
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 +Conflicts/Pre-Depends loop. <command>apt-get</command> will alert you of this and abort the upgrade. You can work around this by specifying the option <literal>-o -APT::Force-LoopBreak=1</literal> on the <command>aptitude</command> command +APT::Force-LoopBreak=1</literal> on the <command>apt-get</command> command line.
</para>
<para>
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
+<command>apt-get</command> or
</para>
<screen>
dpkg --remove <replaceable>package_name</replaceable> @@ -1072,7 +1072,7 @@
to eliminate some of the offending packages, or </para>
<screen>
-
aptitude -f install
+# apt-get -f install
# dpkg --configure --pending
</screen>
<para>
@@ -1081,6 +1081,12 @@
<screen>
# dpkg --install <replaceable>/path/to/package_name.deb</replaceable> </screen>
+
+</section>
+
+<section id="file-conflicts">
+<title>File conflicts</title>
+
<para>
File conflicts should not occur if you upgrade from a <quote>pure</quote> &oldreleasename; system, but can occur if you have unofficial backports installed. A file conflict will @@ -1104,16 +1110,22 @@
</screen>
<para>
After fixing things up, you should be able to resume the upgrade by repeating -the previously described <command>aptitude</command> commands. +the previously described <command>apt-get</command> commands. </para>
+
+</section>
+
+<section id="configuration-changes">
+<title>Configuration changes</title>
+
<para>
-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. +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> directory, 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. </para>
<para>
If you're not sure what to do, write down the name of the package or file and @@ -1122,8 +1134,64 @@
</para>
</section>

+<section id="console-change">
+<title>Change of session to console</title> +<para>
+If you are running the upgrade using the system's local console you +might find that at some points during the upgrade the console is shifted over +to a different view and you lose visibility of the upgrade +process. For example, this will happen in desktop systems when +<command>gdm</command> is restarted.
+</para>
+<para>
+To recover the console where the upgrade was running you will have to use +<keycombo action='simul'><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo> +to switch back to the virtual terminal 1 if in the graphical startup screen or +use <keycombo action='simul'><keycap>Alt</keycap><keycap>F1</keycap></keycombo> +if in the local text-mode console. Replace F1 with the function key with the +same number of the virtual terminal the upgrade was running in. You can also +use <keycombo action='simul'><keycap>Alt</keycap><keycap>Left Arrow</keycap></keycombo> or +<keycombo action='simul'><keycap>Alt</keycap><keycap>Right +Arrow</keycap></keycombo> to switch between the different text-mode terminals. +</para>
</section>

+<section id="package-specific-issues"> +<title>Special care for specific packages</title> +<para>
+In most cases, packages should upgrade smoothly between &oldreleasename; +and &releasename;. There are a small number of cases where some intervention +may be required, either before or during the upgrade; these are detailed +below on a per-package basis.
+</para>
+<section id="issues-evolution">
+<title>Evolution</title>
+<para>
+Evolution (the GNOME Desktop mail client) has been updated from version +<literal>2.22</literal> to <literal>2.30</literal>. This changes the +storage format used by the package for local data and there is a +possibility of data loss if the upgrade is performed whilst <systemitem +role="package">evolution</systemitem> is running. Exiting the +application itself may not be sufficient, as various related components +will continue to run in the background. To avoid any potential issues, +it is recommended that you completely exit your desktop environment +before beginning the upgrade to &releasename;. +</para>
+<para>
+As part of the upgrade process, <systemitem +role="package">evolution</systemitem> will check whether any related +processes are running and will recommend that they be closed. A +secondary check for processes will then be performed; if necessary, a +choice will be offered between allowing the remaining processes to be +killed or aborting the upgrade in order to resolve the situation by +hand.
+</para>
+</section>
+</section>
+<!-- End of 'trouble' section -->
+</section>
+
+<!-- TODO: need to be reviewed with information from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571255 --> <section id="newkernel">
<title>Upgrading your kernel and related packages</title> <para>
@@ -1157,29 +1225,34 @@
<screen>
# apt-cache search linux-image-2.6- | grep -v transition </screen>
+
+<!-- FIXME: Review the Example for Squeeze --> <para>
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 '<literal>2.6.18-6-686</literal>', it is recommended that you install <systemitem -role="package">linux-image-2.6-686</systemitem>. (Note that the <literal>k7</literal> flavor no -longer exists; if you are currently using the <literal>k7</literal> kernel flavor, you should -install the <literal>686</literal> 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:
+see '<literal>2.6.26-2-686</literal>', it is recommended that you install +<systemitem role="package">linux-image-2.6-686</systemitem>. 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: </para>
<screen>
# apt-cache show linux-image-2.6-686
</screen>
<para>
-You should then use <literal>aptitude install</literal> to install it. Once +You should then use <literal>apt-get 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. </para>
<para>
-For the more adventurous there is an easy way to compile your own custom kernel -on &debian;. Install the <systemitem
+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>. +<filename>/usr/share/doc/kernel-package</filename>. Alternatively, +you can also use the kernel sources, provided in the <systemitem +role="package">linux-source-2.6</systemitem> package. You can make use of the +<literal>deb-pkg</literal> target available in the sources' makefile for +building a binary package. There are some differences in these two approaches, +please consult the respective package's documentation. </para>
<para>
If possible, it is to your advantage to upgrade the kernel package separately @@ -1190,70 +1263,47 @@
</para>
</section>

+<!-- FIXME: REVIEW for Squeeze this was written for Lenny - drop? (jfs) --> <section id="device-reorder">
<title>Device enumeration reordering</title> <para>
-&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. +In &oldreleasename; and later, a new kernel mechanism for hardware discovery +may change the order in which devices are discovered on your system on each +boot, affecting the device names assigned to them. 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. </para>
<para>
-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/70-persistent-net.rules</filename><footnote><para> -The rules there are automatically generated by the script -<filename>/etc/udev/rules.d/75-persistent-net-generator.rules</filename> to -have persistent names for network interfaces. Delete this symlink to disable -persistent device naming for <acronym>NIC</acronym>s by <systemitem -role="package">udev</systemitem>. </para> </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. +For network devices, this reordering is normally avoided by the definitions +at <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> for +<systemitem role="package">udev</systemitem>. Since these rules were +already in place in &oldreleasename;, no additional action should be +required when upgrading to &releasename; to get the benefit of stable +network device names. Please note, however, that this udev mechanism means +that a given network device name is tied to a particular piece of hardware; +if you, for instance, exchange ethernet adapters in a deployed &releasename; +system, the new adapter will get a new interface name instead of using the +existing one. To reuse an existing device name for new hardware, you will +need to delete the associated entry from +<filename>/etc/udev/rules.d/70-persistent-net.rules</filename>. </para>
<para>
-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). +For storage devices, you may be able to 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. However, in light of other changes to the storage subsystem of the +Linux kernel as described at <xref linkend="ide-pata-transition"/>, this is +usually not worth the effort and it is recommended instead to use device +names that are guaranteed to be stable over time, such as the UUID aliases +<footnote><para>Some devices, such as those used by crypt, RAID +or LVM have stable non-UUID identifiers. In these cases you should use the +name of the devices, which are already unambiguous and stable.</para></footnote> +in the <filename>/dev/disk/by-uuid/</filename> directory or LVM device names +in <filename>/dev/mapper/</filename>.
</para>
-<para>
-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>.
-</para>
-<para>
-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, <literal>sym53c8xx_2</literal> has become <literal>sym53c8xx</literal>. -</para>
-<para>
-You will then need to regenerate your initramfs image(s) by executing -<literal>update-initramfs -u -k all</literal>. -</para>
-<para>
-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. -</para>
</section>

+<!-- FIXME: REVIEW for Squeeze this was written for Lenny - drop? (jfs) --> <section id="boot-timing">
<title>Boot timing issues</title>
<para>
@@ -1279,20 +1329,35 @@

</section>

-<section id="nownownow">
+<!--
+No tasks left in this section, so comment the whole thing out. +-->
+<section id="nownownow" condition="fixme"> <title>Things to do before rebooting</title> <para>
-When <literal>aptitude dist-upgrade</literal> has finished, the <quote>formal</quote> upgrade +When <literal>apt-get dist-upgrade</literal> has finished, the <quote>formal</quote> upgrade is complete, but there are some other things that should be taken care of <emphasis>before</emphasis> the next reboot. </para>

-<section id="rerunlilo">
+<!-- FIXME: Probably dropable since lilo is no longer setup in Lenny --> +<programlisting condition="fixme">
+There is probably no need at all to run lilo manually on upgrade anymore, +/etc/kernel/postinst.d/zz-lilo runs lilo unconditionally on kernel upgrade; +but don't throw this all away until the lilo maintainers confirm this +isn't required on upgrade for the second-stage bootloader. +</programlisting>
+
+<!-- FIXME: REVIEW for Squeeze this was written for Lenny - drop? (jfs) --> +<section arch="i386;amd64" id="rerunlilo" condition="fixme"> <title>Rerun lilo</title>
<para>
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: +strongly recommended that you rerun <command>lilo</command> after the +upgrade. The <systemitem role="package">lilo</systemitem> package will +offer to do this for you as part of the upgrade, but if you decline or don't +see the prompt, you should run lilo by hand: </para>
<screen>
# /sbin/lilo
@@ -1308,9 +1373,9 @@
</para>
<para>
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. +symbolic links in <filename>/</filename> or <filename>/boot</filename> to +<filename>vmlinuz</filename> and <filename>initrd</filename> and the +contents of your <filename>/etc/lilo.conf</filename> for discrepancies. </para>
<para>
If you forgot to rerun <command>lilo</command> before the reboot or the system @@ -1324,6 +1389,7 @@
</para>
</section>

+<!-- FIXME: REVIEW for Squeeze this was written for Lenny - drop? (jfs) --> <section id="mdadm" condition="fixme"> <title>Upgrading mdadm</title>
<programlisting condition="fixme">TODO: Remove for lenny?</programlisting> @@ -1366,11 +1432,17 @@

     <literal>hdc</literal>, <literal>hdd</literal>. The new drivers
     will name the same disks respectively <literal>sda</literal>,
     <literal>sdb</literal>, <literal>sdc</literal>,

- <literal>sdd</literal>. The problem appears when the upgrade does + <literal>sdd</literal>.
+ </para>
+ <para>
+ The problem appears when the upgrade does

     not generate a new <filename>/boot/grub/menu.lst</filename> file
     to take the new naming convention into account. During the boot,
     Grub will pass a system root partition to the kernel that the

- kernel doesn't find.
+ kernel doesn't find. It can also appear when mounting filesystems + if the <filename>/etc/fstab</filename> has not been updated accordingly. + Although the upgrade process to &releasename; should cover both situations + automatically.

</para>

<para>
@@ -1388,7 +1460,7 @@

       next. There are two possible methods for doing this - labeling
       the filesystem, or using the filesystem's universally unique
       identifier (<acronym>UUID</acronym>). These methods are
-      supported in Debian since the 'etch' release.
+      supported in Debian since the etch release.
     </para>
 
     <para>
@@ -1460,12 +1532,22 @@
        <listitem>
          <para>
            Find out the universally unique identifier of your filesystem by issuing:
-           <command>ls -l /dev/disk/by-uuid | grep hda6</command>
+           <command>ls -l /dev/disk/by-uuid | grep hda6</command>. You can also use <command>blkid /dev/hda6</command>.
+
          </para>
+        
          <para>
-           You should get a line similar to this one:
+            If you list the contents in <filename>/dev/disk/by-uuid</filename>,
+            you should get a line similar to this one:
            <screen>lrwxrwxrwx 1 root root 24 2008-09-25 08:16 d0dfcc8a-417a-41e3-ad2e-9736317f2d8a -> ../../hda6</screen>
+          </para>
+          <!-- TODO: Put the output of vol_id instead, since this is before the upgrade -->
+          <para>
+          If you use <command>blkid</command>, you should get an output similar to this one:
+          <screen>/dev/hda6: UUID="d0dfcc8a-417a-41e3-ad2e-9736317f2d8a" TYPE="ext3"</screen>
+          </para>
 
+          <para>
            The <acronym>UUID</acronym> is the name of the symbolic
            link pointing to <filename>/dev/hda6</filename> i.e.:
            <literal>d0dfcc8a-417a-41e3-ad2e-9736317f2d8a</literal>.
@@ -1481,7 +1563,7 @@
          <para>
            Edit <filename>/boot/grub/menu.lst</filename> and change the line:
            <programlisting> kopt=root=/dev/hda6 ro</programlisting>
-           to
+           to use UUID instead:
            <programlisting> kopt=root=UUID=d0dfcc8a-417a-41e3-ad2e-9736317f2d8 ro</programlisting>
            <note>
              <para>
@@ -1516,6 +1598,9 @@
     </para>

</section>

+<!-- FIXME: This section might not be relevant anymore for Squeeze + but could be turned into a generic section on how to recover from + issues -->

<section id="how-to-recover">
<title>How to recover from the problem after the upgrade</title>

@@ -1530,6 +1615,7 @@

        linkend="solution3"/>.
       </para>

+<!-- FIXME: If kept for Squeeze adjust the kernel version to that of Lenny -->

       <orderedlist>
        <listitem>
          <para>
@@ -1538,15 +1624,15 @@
            related to this entry. You will see something like:
 
            <screen>root (hd0,0)

-kernel /vmlinuz-2.6.26-1-686 root=/dev/hda6 ro -initrd /initrd.img-2.6.26-1-686</screen> +kernel /vmlinuz-2.6.32-5-686 root=/dev/hda6 ro +initrd /initrd.img-2.6.32-5-686</screen>

          </para>
        </listitem>
        <listitem>
          <para>
            Highlight the line
 
-           <screen>kernel /vmlinuz-2.6.26-1-686 root=/dev/hda6 ro</screen>
+           <screen>kernel /vmlinuz-2.6.32-5-686 root=/dev/hda6 ro</screen>
 
            press the <keycap>e</keycap> key and replace
            <literal>hd<replaceable>X</replaceable></literal> with
@@ -1556,7 +1642,7 @@
            <literal>c</literal> or <literal>d</literal> depending of
            your system). In my example the line becomes:
 
-           <screen>kernel /vmlinuz-2.6.26-1-686 root=/dev/sda6 ro</screen>
+           <screen>kernel /vmlinuz-2.6.32-5-686 root=/dev/sda6 ro</screen>
 
            Then press <keycap>Enter</keycap> to save the
            modification. If other lines show
@@ -1591,10 +1677,10 @@
        to use as root file system. The proposed choices will look
        something like:
 
-       <screen>/dev/ide/host0/bus0/target0/lun0/part1

-/dev/ide/host0/bus0/target0/lun0/part2 -/dev/ide/host0/bus0/target0/lun0/part5 -/dev/ide/host0/bus0/target0/lun0/part6</screen> + <screen>/dev/sda1
+/dev/sda2
+/dev/sda5
+/dev/sda6</screen>

</para>

<para>
@@ -1678,15 +1764,15 @@

            Find the section similar to:
            <programlisting>## ## End Default Options ##
 
-title           Debian GNU/Linux, kernel 2.6.26-1-686
+title           Debian GNU/Linux, kernel 2.6.32-5-686
 root            (hd0,0)
-kernel          /vmlinuz-2.6.26-1-686 root=/dev/hda6 ro
-initrd          /initrd.img-2.6.26-1-686
+kernel          /vmlinuz-2.6.32-5-686 root=/dev/hda6 ro
+initrd          /initrd.img-2.6.32-5-686
 
-title           Debian GNU/Linux, kernel 2.6.26-1-686 (single-user mode)
+title           Debian GNU/Linux, kernel 2.6.32-5-686 (single-user mode)
 root            (hd0,0)
-kernel          /vmlinuz-2.6.26-1-686 root=/dev/hda6 ro single
-initrd          /initrd.img-2.6.26-1-686
+kernel          /vmlinuz-2.6.32-5-686 root=/dev/hda6 ro single
+initrd          /initrd.img-2.6.32-5-686

### END DEBIAN AUTOMAGIC KERNELS LIST</programlisting>

@@ -1728,54 +1814,85 @@
<itemizedlist>
<listitem>
<para>
-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: -</para>
-<screen>
- aptitude unmarkauto $(dpkg-query -W 'linux-image-2.6-' | cut -f1) -</screen>
-</listitem>
-<listitem>
-<para>
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. </para>
</listitem>
</itemizedlist>
+
+<section id="update-grub" arch="amd64;i386"> +<title>Upgrade to GRUB 2</title>
+<para>
+During the upgrade, you will normally have been offered the option to +"chainload" GRUB 2: that is, to keep GRUB Legacy as the primary boot loader +but to add an option to it to load GRUB 2 and then start your &debian; +system from that. This allows you to verify that GRUB 2 works on your +system before committing to use it permanently. +</para>
+<para>
+Once you have confirmed that GRUB 2 works, you should switch to using it +properly: the chainloading setup is only intended to be used temporarily. +You can do this by running <command>upgrade-from-grub-legacy</command>. +</para>
+<para>
+The GRUB Manual has <ulink
+url="http://www.gnu.org/software/grub/manual/grub.html#Changes-from-GRUB-Legacy">more +information</ulink> on the changes between GRUB Legacy and GRUB 2, some of +which may require changes to complex configurations. If you have not modified +your boot loader configuration, you should not need to do anything further. +</para>
+
</section>

-<section id="deprecated" condition="fixme"> -<title>Deprecated packages</title>
-<programlisting condition="fixme">
-TODO: the only packages listed here at lenny release time were all packages -that are already gone in lenny; if there are other deprecations we want to -list here, someone will need to populate that list. -</programlisting>
+</section>
+
+<section id="deprecated">
+<title>Deprecated components</title>
<para>
With the next release of &debian; &nextrelease; (codenamed -&nextreleasename;) 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 &nextrelease;. +&nextreleasename;) some features will be deprecated. Users +will need to migrate to other alternatives to prevent +trouble when updating to &nextrelease;. </para>
+
<para>
-This includes the following packages:
+This includes the following features:
</para>
+
<itemizedlist>
+
<listitem>
+<!-- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574529 + http://lists.debian.org/debian-devel-announce/2009/10/msg00003.html --> <para>
-<systemitem role="package">apache</systemitem> (1.x), successor is -<systemitem role="package">apache2</systemitem> +OpenVZ and Linux-Vserver: &debian; &release; will be +the last release to include Linux kernel virtualization featuresets outside of +mainline. This means that the OpenVZ and Linux-Vserver featuresets should be +considered deprecated, and users should migrate to linux-2.6 upstream merged +virtualization solutions like KVM, Linux Containers or Xen. </para>
</listitem>
+
+<listitem>
+ <para>
+ The <systemitem role="package">gdm</systemitem> package (GNOME Display + Manager version 2.20) will be obsoleted by <systemitem + role="package">gdm3</systemitem>, a rewritten version. See <xref + linkend="gnome-desktop-changes" /> for more information. + </para>
+</listitem>
+
</itemizedlist>
+
+
</section>

<section id="obsolete">
<title>Obsolete packages</title>
<para>
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 +than four 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><para> Or for as @@ -1800,15 +1917,20 @@
provides a similar section but the listing it presents might differ. </para>
<para>
-Also, if
-you have used <command>aptitude</command> to manually install packages in &oldreleasename; +Also, if you have used <command>aptitude</command> or +<command>apt-get</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. +are no longer needed if a package has been removed. +<command>aptitude</command> and <systemitem role="package">apt</systemitem>, +unlike <command>deborphan</command>, will not mark for removal packages that +you manually installed, as opposed to those that were automatically +installed through dependencies. To remove automatically installed packages +that are no longer used, run:
</para>
+<screen>
+# apt-get autoremove
+</screen>
<para>
There are additional tools you can use to find obsolete packages such as <command>deborphan</command>, <command>debfoster</command> or @@ -1828,6 +1950,108 @@
url="&url-bts;cgi-bin/pkgreport.cgi?pkg=ftp ftp.debian.org&amp;archive=yes">ftp ftp.debian.org pseudo-package</ulink>.
</para>
+<!-- FIXME: Review for Squeeze - more obsolete packages probably need to be listed here --> +<!-- TODO:
+Use the following reources for more information: +
+ - http://alioth.debian.org/~spaillard/udd-release-notes-src-with-RM +
+ - http://www.klabs.be/~fpiat/linux/comp-dist2/squeeze/ +(alternatively)
+ - Use the change-release information and sort by popcon +-->
+<para>
+ The list of obsolete packages includes: + <itemizedlist>
+ <listitem>

+      <para>
+      The <systemitem role="package">plone</systemitem> content
+      management suite. This has been done on request by the developers
+      to use the Unified Installer for Linux, which  they consider their only
+      supported deployment platform. The recommended tool for installing Plone
+      on a &debian; system is the Unified Installer, available
+      for download from <ulink url="http://plone.org/" />
+      </para>

+ </listitem>
+ <listitem>

+      <para>
+        <systemitem role="package">nessus</systemitem>, the vulnerability
+        scanning server and its associated libraries and other software.
+        It has been deprecated in favor of the software provided by OpenVAS 
+        which includes
+        <systemitem role="package">openvas-server</systemitem> and
+        <systemitem role="package">openvas-client</systemitem>. As
+        there is no automatic upgrade path you will have to install
+        OpenVAS and manually move over your Nessus service configuration 
+        (users, certificates, etc.) to OpenVAS.
+      </para>

+ </listitem>
+ <listitem>

+      <para>
+        <systemitem role="package">postgresql-8.3</systemitem>, successor
+        is <systemitem role="package">postgresql-8.4</systemitem>.
+      </para>

+ </listitem>
+ <listitem>

+      <para>
+        <systemitem role="package">mysql-server-5.0</systemitem>, successor
+        is <systemitem role="package">mysql-server-5.1</systemitem>.
+      </para>

+ </listitem>
+ <listitem>

+      <para>
+        <systemitem role="package">python2.4</systemitem>, successor
+        is <systemitem role="package">python2.6</systemitem>.
+      </para>

+ </listitem>
+ <listitem>

+      <para>
+        Java 5 software including the packages <systemitem
+        role="package">sun-java5-jre</systemitem> and <systemitem
+        role="package">sun-java5-bin</systemitem>, successor is Java 6:
+        <systemitem role="package">sun-java6-jre</systemitem> and
+        associated packages.
+      </para>

+ </listitem>
+ <!-- apt-proxy RM: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576821 --> + <listitem>

+      <para>
+      <systemitem role="package">apt-proxy</systemitem> is no longer
+      provided, alternatives to this tool include
+      <systemitem role="package">apt-cacher-ng</systemitem>,
+      <systemitem role="package">apt-cacher</systemitem> and
+      <systemitem role="package">approx</systemitem>. Although no
+      automatic upgrade path exists, user of <systemitem
+      role="package">apt-proxy</systemitem> can switch to these alternatives
+      by manually installing any of these packages. 
+      </para>

+ </listitem>
+ <listitem>

+      <para>
+      Some of Xorg's video drivers are no longer available in 
+      &releasename; and are obsolete. This includes 
+      <systemitem role="package">xserver-xorg-video-cyrix</systemitem>,
+      <systemitem role="package">xserver-xorg-video-i810</systemitem>,
+      <systemitem role="package">xserver-xorg-video-imstt</systemitem>,
+      <systemitem role="package">xserver-xorg-video-nsc</systemitem>,
+      <systemitem role="package">xserver-xorg-video-sunbw2</systemitem>, and
+      <systemitem role="package">xserver-xorg-video-vga</systemitem>.
+      They might be removed through the upgrade. Users should install
+      <systemitem role="package">xserver-xorg-video-all</systemitem>
+      instead.
+      </para>

+ </listitem>
+ <listitem>

+      <para>
+      The utility used in &oldreleasename; to display a splash image at boot
+      time, <systemitem role="package">usplash</systemitem>, is no longer
+      available. It has been replaced by 
+      <systemitem role="package">plymouth</systemitem>.
+      </para>

+ </listitem>
+ </itemizedlist>
+</para>
+
<section id="dummy">
<title>Dummy packages</title>
<para>
@@ -1841,45 +2065,15 @@
<para>
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. +also find <command>deborphan</command> with the +<literal>--guess-<replaceable>
</replaceable></literal> options (e.g. +<literal>--guess-dummy</literal>) 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.
</para>
</section>

</section>

-<!-- Please remove 'arch="arm;armel"' when this section gets subsections -related to some other architectures. --> -<section id="plans-for-nigel" arch="arm;armel"> - <title>Plans for the next Debian release</title> -
- <section arch="arm;armel">
- <title>Drop of the ARM ABI port, in favor of the ARM EABI port</title> -
- <para>

-      Debian lenny has two different and incompatible ARM ports: the
-      old ABI port (arm) and the new EABI port (armel).  Debian lenny
-      is the last release with support for the ARM ABI port and future
-      releases will only support the ARM EABI or armel port.  It's
-      therefore recommended to use armel for new installations of
-      lenny.

- </para>
-
- <para>

-      With the exception of Netwinder, installer images for supported
-      ARM machines are available for both arm and armel in lenny.
-      Netwinder support is only available for arm and it will be
-      dropped after lenny along with the arm port.
-      <indexterm><primary>Netwinder</primary></indexterm>

- </para>
-
- <para>

-      Please visit <ulink
-      url="http://wiki.debian.org/ArmEabiPort">this page</ulink> to
-      learn more about the ARM EABI (armel) port.

- </para>
- </section>
-</section>
</chapter>
. Added: 640 Removed: 446
Showing diffs for whats-new.dbk... (ver: 6592:)Index: whats-new.dbk


--- whats-new.dbk       (revisión: 6592)
+++ whats-new.dbk       (copia de trabajo)

@@ -7,11 +7,19 @@
<chapter id="ch-whats-new" lang="en">
<title>What's new in &debian; &release;</title> <para>
-The <ulink url="&url-wiki-newinlenny;">Wiki</ulink> has more information +The <ulink url="&url-wiki-newinsqueeze;">Wiki</ulink> has more information about this topic.
</para>
+
+<!--
+Sources for architecture status:
+ http://release.debian.org/squeeze/arch_qualify.html +-->
+
<para>
-This release adds official support for the ARM EABI (armel). +This release drops official support for the <ulink +url="http://lists.debian.org/debian-devel-announce/2010/09/msg00008.html">HP +PA-RISC ('hppa')</ulink>, Alpha ('alpha') and ARM ('arm') architectures. </para>
<para>
The following are the officially supported architectures for &debian; @@ -20,16 +28,11 @@
<itemizedlist>
<listitem>
<para>
-Intel x86 ('i386')
+32-bit PC ('i386')
</para>
</listitem>
<listitem>
<para>
-Alpha ('alpha')
-</para>
-</listitem>
-<listitem>
-<para>
SPARC ('sparc')
</para>
</listitem>
@@ -40,11 +43,6 @@
</listitem>
<listitem>
<para>
-ARM ('arm')
-</para>
-</listitem>
-<listitem>
-<para>
MIPS ('mips' (big-endian) and 'mipsel' (little-endian)) </para>
</listitem>
@@ -55,17 +53,12 @@
</listitem>
<listitem>
<para>
-HP PA-RISC ('hppa')
-</para>
-</listitem>
-<listitem>
-<para>
S/390 ('s390')
</para>
</listitem>
<listitem>
<para>
-AMD64 ('amd64')
+64-bit PC ('amd64')
</para>
</listitem>
<listitem>
@@ -74,16 +67,28 @@
</para>
</listitem>
</itemizedlist>
+
+<!-- Based on http://www.debian.org/News/2010/20100806 --> +<para>In addition to the officially supported architectures, &debian; squeeze +introduces the GNU/kFreeBSD ports ('kfreebsd-amd64' and 'kfreebsd-i386') as a +technology preview. These ports are the first ones included in a Debian +release which aren't based on the Linux kernel, but instead use the FreeBSD +kernel with a GNU userland. Users of these versions however should be warned +that the quality of these ports is still catching up with the outstanding high +quality of our Linux ports, and that some advanced desktop features are not +supported yet. However, the support of common server software is strong and +extends the features of Linux-based Debian versions by the unique features +known from the BSD world. This is the first time a Linux distribution has been +extended to also allow use of a non-Linux kernel. +</para>
+
<para>
You can read more about port status, and port-specific information for your architecture at the <ulink url="&url-ports;">Debian port web pages</ulink>.
</para>

-<programlisting condition="fixme">
-TODO: freeBSD port not ready for lenny, but in very good shape -</programlisting>
-
+<!-- FIXME: REVIEW for Squeeze - this happened in Lenny --> <section id="newforarm" arch="arm;armel"> <title>What's new for ARM?</title>

@@ -117,17 +122,26 @@

     role="package">ixp4xx-microcode</systemitem> in non-free.
     Installer images for Debian which include this microcode will
     continue to be made available from <ulink

- url="slug-firmware.net">slug-firmware.net</ulink>. + url="http://slug-firmware.net">slug-firmware.net</ulink>.

</para>
</section>

+<section id="newfors390" arch="s390">
+<title>What's new for S390?</title>
+<para>

+       The 32-bit <literal>s390</literal> kernel flavour is no longer
+       provided.  As a consequence, only hardware with z/Architecture support
+       will be supported in Debian &release;, using the
+       <literal>s390x</literal> kernel flavour.

+</para>
+</section>
+
<section id="newdistro">
<title>What's new in the distribution?</title>

<programlisting condition="fixme">
- TODO: Numbers need to be reviewed, these values have been obtained + TODO: Make sure you update the numbers in the .ent file

      using the changes-release.pl script found under ../
-     DONE for lenny release

</programlisting>

<para>
@@ -143,41 +157,50 @@
see any updates for these packages and they will be marked as 'obsolete' in package management front-ends. </para>
+
+<!-- INFO: For Squeeze this might be useful +http://www.klabs.be/~fpiat/linux/comp-dist2/squeeze/ --> +
<para>
-With this release, &debian; updates from X.Org 7.1 to X.Org 7.3. +With this release, &debian; updates from X.Org 7.3 to X.Org 7.5. </para>
<para>
&debian; again ships with several desktop applications and environments. Among others it now includes the desktop environments GNOME<indexterm><primary>GNOME</primary></indexterm> - 2.22<footnote><para> With some modules from GNOME 2.20. + 2.30<footnote><para> With some modules from GNOME 2.32.

</para></footnote>, KDE<indexterm><primary>KDE</primary></indexterm> - 3.5.10, Xfce<indexterm><primary>Xfce</primary></indexterm> 4.4.2, and - LXDE<indexterm><primary>LXDE</primary></indexterm> 0.3.2.1+svn20080509. + 4.4.5, Xfce<indexterm><primary>Xfce</primary></indexterm> 4.6.2, and + LXDE<indexterm><primary>LXDE</primary></indexterm> 0.5.0.

Productivity applications have also been upgraded, including the office suites
OpenOffice.org<indexterm><primary>OpenOffice.org</primary></indexterm> - 2.4.1 and KOffice<indexterm><primary>KOffice</primary></indexterm> - 1.6.3 as well as
- GNUcash<indexterm><primary>GNUcash</primary></indexterm> 2.2.6, - GNUmeric<indexterm><primary>GNUmeric</primary></indexterm> 1.8.3 and - Abiword<indexterm><primary>Abiword</primary></indexterm> 2.6.4. + 3.2.1 and KOffice<indexterm><primary>KOffice</primary></indexterm> + 2.2.1 as well as
+ GNUcash<indexterm><primary>GNUcash</primary></indexterm> 2.2.9, + GNUmeric<indexterm><primary>GNUmeric</primary></indexterm> 1.10.8 and + Abiword<indexterm><primary>Abiword</primary></indexterm> 2.8.2. </para>
<para>
Updates of other desktop applications include the upgrade to - Evolution<indexterm><primary>Evolution</primary></indexterm> 2.22.3 - and Pidgin<indexterm><primary>Pidgin</primary></indexterm> 2.4.3 (formerly known as Gaim<indexterm><primary>Gaim</primary></indexterm>). The - Mozilla<indexterm><primary>Mozilla</primary></indexterm> suite has + Evolution<indexterm><primary>Evolution</primary></indexterm> 2.30.3 + and Pidgin<indexterm><primary>Pidgin</primary></indexterm> 2.7.3. + The Mozilla<indexterm><primary>Mozilla</primary></indexterm> suite has

also been updated:
<systemitem role="package">iceweasel</systemitem> - (version 3.0.6) is the unbranded
+ (version 3.5.13) is the unbranded

<application>Firefox<indexterm><primary>Firefox</primary></indexterm></application> web browser and
<systemitem role="package">icedove</systemitem> - (version 2.0.0.19) is the unbranded
+ (version 3.0.7) is the unbranded

<application>Thunderbird<indexterm><primary>Thunderbird</primary></indexterm></application> mail client.
</para>
+
+<!-- JFS:
+Might it be useful point to http://distrowatch.com/table.php?distribution=debian ? +This provides a more comprehensive comparison among different releases --> +
<para>
Among many others, this release also includes the following software updates: </para>
@@ -197,113 +220,118 @@

     <tbody>
       <row id="new-apache2">
        <entry>Apache<indexterm><primary>Apache</primary></indexterm></entry>
-       <entry>2.2.3</entry>
        <entry>2.2.9</entry>
+       <entry>2.2.16</entry>
       </row>
       <row id="new-bind9">
        <entry>BIND<indexterm><primary>BIND</primary></indexterm> <acronym>DNS</acronym> Server</entry>
-       <entry>9.3.4</entry>
-       <entry>9.5.0</entry>
+       <entry>9.6.0</entry>
+       <entry>9.7.1</entry>
       </row>
       <row id="new-cherokee">
        <entry>Cherokee<indexterm><primary>Cherokee</primary></indexterm> web server</entry>
-       <entry>0.5.5</entry>
        <entry>0.7.2</entry>
+       <entry>1.0.8</entry>
       </row>
       <row id="new-courier">
        <entry>Courier<indexterm><primary>Courier</primary></indexterm> <acronym>MTA</acronym></entry>
-       <entry>0.53.3</entry>
        <entry>0.60.0</entry>
+       <entry>0.63.0</entry>
       </row>
       <row id="new-dia">
        <entry>Dia<indexterm><primary>Dia</primary></indexterm></entry>
-       <entry>0.95.0</entry>
        <entry>0.96.1</entry>
+       <entry>0.97.1</entry>
       </row>
       <row id="new-ekiga">
        <entry>Ekiga<indexterm><primary>Ekiga</primary></indexterm> VoIP Client</entry>
-       <entry>2.0.3</entry>
        <entry>2.0.12</entry>
+       <entry>3.2.7</entry>
       </row>
       <row id="new-exim4">
        <entry>Exim<indexterm><primary>Exim</primary></indexterm> default email server</entry>
-       <entry>4.63</entry>
        <entry>4.69</entry>
+       <entry>4.72</entry>
       </row>
       <row id="new-gcc">
        <entry><acronym>GNU</acronym> Compiler Collection as default compiler<indexterm><primary>GCC</primary></indexterm></entry>
-       <entry>4.1.1</entry>
        <entry>4.3.2</entry>
+       <entry>4.4.5</entry>
       </row>
       <row id="new-gimp">
        <entry><acronym>GIMP</acronym><indexterm><primary>GIMP</primary></indexterm></entry>
-       <entry>2.2.13</entry>
        <entry>2.4.7</entry>
+       <entry>2.6.10</entry>
       </row>
       <row id="new-libc6">
        <entry>the <acronym>GNU</acronym> C library</entry>
-       <entry>2.3.6</entry>
        <entry>2.7</entry>
+       <entry>2.11.2</entry>
       </row>
       <row id="new-lighttpd">
        <entry>lighttpd</entry>
-       <entry>1.4.13</entry>
        <entry>1.4.19</entry>
+       <entry>1.4.28</entry>
       </row>
       <row id="new-maradns">
        <entry>maradns</entry>
-       <entry>1.2.12.04</entry>
        <entry>1.3.07.09</entry>
+       <entry>1.4.03</entry>
       </row>
       <row id="new-mysql">
        <entry>MySQL<indexterm><primary>MySQL</primary></indexterm></entry>
-       <entry>5.0.32</entry>
        <entry>5.0.51a</entry>
+       <entry>5.1.49</entry>
       </row>
       <row id="new-openldap">
        <entry>OpenLDAP</entry>
-       <entry>2.3.30</entry>
        <entry>2.4.11</entry>
+       <entry>2.4.23</entry>
       </row>
       <row id="new-openssh">
        <entry>OpenSSH<indexterm><primary>OpenSSH</primary></indexterm></entry>
-       <entry>4.3</entry>
        <entry>5.1p1</entry>
+       <entry>5.5p1</entry>
       </row>
       <row id="new-php">
        <entry>PHP<indexterm><primary>PHP</primary></indexterm></entry>
-       <entry>5.2.0</entry>
        <entry>5.2.6</entry>
+       <entry>5.3.2</entry>
       </row>
       <row id="new-postfix">
        <entry>Postfix<indexterm><primary>Postfix</primary></indexterm> <acronym>MTA</acronym></entry>
-       <entry>2.3.8</entry>
        <entry>2.5.5</entry>
+       <entry>2.7.1</entry>
       </row>
       <row id="new-postgresql">
        <entry>PostgreSQL<indexterm><primary>PostgreSQL</primary></indexterm></entry>
-       <entry>8.1.15</entry>
        <entry>8.3.5</entry>
+       <entry>8.4.5</entry>
       </row>
       <row id="new-python">
        <entry>Python</entry>
-       <entry>2.4.4</entry>
        <entry>2.5.2</entry>
+       <entry>2.6.6</entry>
       </row>
+      <row id="new-samba">
+       <entry>Samba</entry>
+       <entry>3.2.5</entry>
+       <entry>3.5.5</entry>
+      </row>
       <row id="new-tomcat">
        <entry>Tomcat<indexterm><primary>Tomcat</primary></indexterm></entry>
-       <entry>5.5.20</entry>
        <entry>5.5.26</entry>
+       <entry>6.0.28</entry>
       </row>
     </tbody>

</tgroup>
</informaltable>

<programlisting condition="fixme">
- Note: No significant changes for Roxen4, Boa, and thttpd TODO: (JFS) List other server software? RADIUS? Streaming ? </programlisting>

+<!-- TODO: REVIEW for Squeeze -->
<para>
The official &debian; distribution now ships on 4 to 5 binary <acronym>DVD</acronym>s <indexterm><primary>DVD</primary></indexterm> @@ -313,46 +341,170 @@
<acronym>CD</acronym>s. Additionally, there is a <emphasis>multi-arch</emphasis> <acronym>DVD</acronym>, with a subset of the release for the <literal>amd64</literal> and -<literal>i386</literal> architectures, along with the source code. For -the first time, &debian; is also released as Blu-ray +<literal>i386</literal> architectures, along with the source code. +&debian; is also released as Blu-ray
<indexterm><primary>Blu-ray</primary></indexterm> images, also for the <literal>amd64</literal> and <literal>i386</literal> architectures, along with the source code. </para>
<para>
-Debian now supports Linux Standards Base (<acronym>LSB</acronym>) version 3.2. -Debian &oldrelease; did support version 3.1. -<indexterm><primary>Linux Standards Base</primary></indexterm> +Debian still supports Linux Standard Base (<acronym>LSB</acronym>) version 3.2. +<indexterm><primary>Linux Standard Base</primary></indexterm> </para>
+
+<section id="nonfree-firmware">
+<title>Firmware moved to the non-free section</title> +<para>
+Some drivers included in the Linux kernel used to contain non-free firmware +blobs. Starting from &releasename; this firmware has been moved to separate +packages in the non-free section of the archive, such as <systemitem +role="package">firmware-linux</systemitem>. If such packages are installed, +the firmware will be loaded automatically when required. +</para>
+</section>
+
+<!-- FIXME: REVIEW for Squeeze -->
<section id="pkgmgmt">
<title>Package management</title>
+<para>
+The preferred program for interactive package management from a terminal is +<command>aptitude</command>. For a non-interactive command line interface +for package management, it is recommended to use <command>apt-get</command>. +<command>apt-get</command> is also the preferred tool for upgrades +between major releases.
+If you are still using <command>dselect</command>, you should switch to +<systemitem role="package">aptitude</systemitem> as the official front-end +for package management.
+</para>

+<para>
+For &releasename; APT automatically installs recommended packages by default<footnote><para>This change implies that disk requirements for tasks selected through the debian installer have increased too. For more information please +see the <quote>Disk Space Needed for Tasks</quote> chapter in the +<ulink url="&url-install-manual;">Installation Guide</ulink>.</para></footnote>. +This can be changed by adding the following line in +<filename>/etc/apt/apt.conf</filename>: +<programlisting>APT::Install-Recommends "false";</programlisting> +</para>
+
<programlisting condition="fixme">
-TODO: is aptitude always prefered over apt-get? +TODO: Do we have to mention dpkg triggers here or elsewhere? </programlisting>

+</section>
+
+<section id="dependency-boot">
+<title>Dependency booting</title>
+
<para>
-The preferred program for package management from the command line is -<command>aptitude</command>, which can perform the same package -management functions as <command>apt-get</command> and has proven to be -better at dependency resolution. If you are still using -<command>dselect</command>, you should switch to <systemitem -role="package">aptitude</systemitem> as the official front-end for package -management.
+An important improvement in the &debian; boot system is the introduction +of dependency-based boot sequencing and parallel boot. This feature is enabled +by default in new installs and it will be enabled for upgrades from +&oldreleasename;, if possible.
</para>
+
<para>
-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.
+This feature is enabled through the use of <systemitem role="package">insserv</systemitem> +by sysv-rc to order init.d scripts based on their declared +dependencies<footnote><para>These dependences are declared through the use of +the header format specified in the Linux Standard Base (LSB)</para></footnote>. +It has been possible after a sustained effort to adapt all the boot scripts +of packages provided in the distribution as well as the boot system itself. </para>

-<programlisting condition="fixme">
-TODO: Do we have to mention dpkg triggers here or elsewhere? -</programlisting>
+<para>
+With dependency-based boot sequencing it is also now possible to run the boot +system scripts in parallel which can, under most circumstances, improve the +speed of the boot process. This feature is enabled by default, in new +systems and upgrades, whenever possible. +To disable it specify <programlisting>CONCURRENCY=none</programlisting> +in <filename>/etc/default/rcS</filename>. +For more information on this feature refer to the information available in +<filename>/usr/share/doc/insserv/README.Debian</filename>. +</para>

</section>

+<section id="unity-keyboard-settings"> +<title>Unified keyboard settings</title> +
+<para>
+In this new release, the settings for the keyboard have been unified so that +both the console and the Xorg server use the same settings. The keyboard +settings are now defined in the <filename>/etc/default/keyboard</filename> +configuration file which overrides the keyboard defined in Xorg's +configuration file.
+</para>
+
+<para>
+The <systemitem role="package">console-setup</systemitem> package now +handles the keyboard for both environments as well as the font +configuration for the console. You can reconfigure the keyboard layout and +related settings by executing
+<command>dpkg-reconfigure keyboard-configuration</command> +or by manually editing the <filename>/etc/default/keyboard</filename> +configuration file.
+</para>
+
+</section>
+
+<section id="kms">
+ <title>Kernel mode setting</title>
+ <para>
+ Graphics mode setting code for the most common desktop chipsets (from + Intel, ATI/AMD and NVIDIA) has moved from the respective Xorg drivers to + the Linux kernel. This provides a number of advantages, such as: + <itemizedlist>

+      <listitem><para>More reliable suspend and resume</para></listitem>
+      <listitem>
+        <para>Ability to use graphics devices without X</para>
+      </listitem>
+      <listitem><para>Faster VT switch</para></listitem>
+      <listitem><para>Native mode text console</para></listitem>

+ </itemizedlist>
+ </para>
+
+ <para>
+ More details are in <xref linkend="graphics"/> and in <ulink + url="&url-wiki;KernelModesetting">the Debian wiki</ulink>. + </para>
+</section>
+
+<section id="new-ldap">
+ <title><acronym>LDAP</acronym> support</title> + <indexterm><primary>LDAP</primary></indexterm> + <para>
+ This Debian release comes with several options for implementing + client-side authentication using LDAP. + Users of the <systemitem role="package">libnss-ldap</systemitem> and + <systemitem role="package">libpam-ldap</systemitem> packages should + consider upgrading to
+ <systemitem role="package">libnss-ldapd</systemitem> and + <systemitem role="package">libpam-ldapd</systemitem>. + </para>
+ <para>
+ These newer packages delegate the <acronym>LDAP</acronym> queries to a central unprivileged + daemon (<command>nslcd</command>) that provides separation between the process using the <acronym>LDAP</acronym> + information and the daemon performing <acronym>LDAP</acronym> queries. This simplifies + handling of secured <acronym>LDAP</acronym> connections, + <acronym>LDAP</acronym> authentication credentials, provides a simpler + mechanism to perform connection fail-over and debugging and avoids + loading <acronym>LDAP</acronym> and related libraries into most + applications.
+ </para>
+ <para>
+ Upgrading to <systemitem role="package">libnss-ldapd</systemitem> and + <systemitem role="package">libpam-ldapd</systemitem> should be easy + as existing configuration information will be mostly reused. + Only for advanced configuration should any manual reconfiguration be + necessary.
+ </para>
+ <para>
+ These packages however currently lack support for nested groups and only + support password change using the <acronym>LDAP</acronym> password modify + EXOP operation.
+ </para>
+</section>
+
<section id="proposed-updates-intro">
<title>The proposed-updates section</title> <para>
@@ -364,12 +516,12 @@

</para>
<para>
Packages can enter <literal>proposed-updates</literal> in two - ways. Firstly, security-patched packages added to - security.debian.org are automatically added to - <literal>proposed-updates</literal> as well. Secondly, &debian; - developers may upload new packages directly to - <literal>proposed-updates</literal>. The current list of packages - can be seen at <ulink
+ ways. Firstly, security-patched packages added to security.debian.org are + automatically added to <literal>proposed-updates</literal> as well. + Secondly, &debian; developers may upload new packages to + <literal>proposed-updates</literal>, where they get added after review by + the Stable Release Managers. The current list of packages can be seen at + <ulink

url="&url-ftpmaster;/proposed-updates.html">&url-ftpmaster;/proposed-updates.html</ulink>. </para>
<para>
@@ -381,7 +533,7 @@

<programlisting>deb &url-debian-mirror-eg;/debian &releasename;-proposed-updates main contrib deb-src &url-debian-mirror-eg;/debian &releasename;-proposed-updates main contrib</programlisting> <para>
- The next time you run <command>aptitude update</command>, the + The next time you run <command>apt-get update</command>, the

     system will become aware of the packages in the
     <literal>proposed-updates</literal> section and will consider them
     when looking for packages to upgrade.

@@ -392,118 +544,60 @@

</para>
</section>

-<section id="backports.org" condition="fixme"> -<title>backports.org/backports.debian.org</title> -<para >TODO: write about probability backports.org becoming official</para> +<section id="stable-updates">
+ <title>The stable-updates section</title> + <para>
+ Some packages from <literal>proposed-updates</literal> may also be made + available via the <literal>&releasename;-updates</literal> mechanism. + This path will be used for updates which many users may wish to install + on their systems before the next point release is made, such as updates + to virus scanners and timezone data. All packages from + <literal>&releasename;-updates</literal> will be included in point + releases.
+ </para>
+ <para>
+ Note that this replaces the functionality previously provided by the + <ulink url="http://volatile.debian.org/">volatile.debian.org archive</ulink>. + </para>
+ <para>
+ In order to use packages from <literal>&releasename;-updates</literal>, + you can add an entry to your <filename>sources.list</filename>: + </para>
+ <programlisting>deb &url-debian-mirror-eg;/debian &releasename;-updates main contrib +deb-src &url-debian-mirror-eg;/debian &releasename;-updates main contrib</programlisting> + <para>
+ The next time you run <command>apt-get update</command>, the + system will become aware of the packages in the + <literal>&releasename;-updates</literal> section and will consider them + when looking for packages to upgrade. + </para>
+ <para>
+ When a new package is made available via <literal>&releasename;-updates</literal>, + this will be announced on the <ulink + url="http://lists.debian.org/debian-stable-announce/">debian-stable-announce</ulink> mailing list. + </para>
</section>

-</section>
+<section id="backports.debian.org">
+<title>backports.org/backports.debian.org</title>

-<section id="system-changes">
-<title>System improvements</title>
-<para>
-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. +<para >
+The service provided by the backports.org repositories has been integrated in +Debian infrastructure and <ulink
+url="http://www.debian.org/News/2010/20100905">is now an official Debian +service</ulink>, hosted at <ulink
+url="&url-debian-backports;">backports.debian.org</ulink>. </para>
-<variablelist>
-<varlistentry>
-<term>SELinux priority standard, but not enabled by default</term> -<listitem>
-<indexterm><primary>SELinux</primary></indexterm> -<para>
-The packages needed for SELinux (Security-Enhanced Linux) 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:
-</para>
-<screen>
-# aptitude install selinux-basics
-</screen>
-<para>
-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="&url-wiki-selinux;">Debian Wiki</ulink>. -</para>
-</listitem>
-</varlistentry>
-<varlistentry condition="fixme">
-<term>New default inet superdaemon</term> -<listitem>
-<programlisting condition="fixme">TODO: Remove for lenny?</programlisting> -<para>
-The default inet superdaemon for &releasename; is <systemitem -role="package">openbsd-inetd</systemitem> instead of <systemitem -role="package">inetutils-inetd</systemitem>. It will not be started if no -services are configured, as is the case by default. The new default daemon will -be installed automatically on upgrade. -</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>New default syslog daemon</term> -<listitem>
-<para>
-The package <systemitem role="package">rsyslog</systemitem> takes -over as default system and kernel logging daemon for Debian &release;, -replacing <command>syslogd</command> and <command>klogd</command>. -With stock logging rules, it can be used as a drop-in replacement; if -you have custom rules, you should migrate them to the new configuration -file, <filename>/etc/rsyslog.conf</filename>. -</para>
-<para>
-Users upgrading from &oldreleasename; need to install <systemitem -role="package">rsyslog</systemitem> and remove <systemitem -role="package">sysklogd</systemitem> manually. The default syslog daemon is -not replaced automatically at the upgrade to &releasename;. -</para>
-</listitem>
-</varlistentry>
-<varlistentry condition="fixme">
-<term>Changes in default features for <literal>ext2</literal>/<literal>ext3</literal></term> -<listitem>
-<programlisting condition="fixme">TODO: Remove for lenny?</programlisting> -<para>
-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).
-</para>
-<para>
-Users upgrading from &oldreleasename; could consider adding the -<emphasis>dir_index</emphasis> flag manually using -<command>tune2fs</command><footnote><para> The flag -<emphasis>filetype</emphasis> should already be set on most file systems, -except possibly on systems installed before &oldreleasename;. </para> </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>.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>Better support for UTF-8</term>
-<listitem>
-<para>
-A number of additional applications will be set up to use UTF-8 by -default or have better UTF-8 support than before. See at <ulink -url="&url-wiki;UTF8BrokenApps">&url-wiki;UTF8BrokenApps</ulink> about -applications that still have difficulties in handling UTF-8. -</para>
-</listitem>
-</varlistentry>
-</variablelist>
-<para>
-The <ulink url="&url-wiki;Etch2LennyUpgrade">Debian Wiki</ulink> -has some additional information about changes between &oldreleasename; and &releasename;. -</para>
+
</section>

+</section>
+
+<!-- FIXME: REVIEW for Squeeze - keep highlighting? --> <section id="live" arch="amd64;i386">
<title>Debian Live</title>
<para>
-With &releasename; Debian presents official Live systems for the amd64 +With &releasename; Debian provides official Live systems for the amd64 and i386 architectures.
<indexterm><primary>Live system</primary></indexterm> <indexterm><primary>Debian Live</primary></indexterm> @@ -515,138 +609,39 @@
produced by a tool named <systemitem
role="package">live-helper</systemitem>, which can easily be used to create custom live images. More information about the Debian Live project -can be found at <ulink url="http://debian-live.alioth.debian.org/" />. +can be found at <ulink url="http://live.debian.net/" />. </para>
</section>

-<section id="kernel-changes">
-<title>Major kernel-related changes</title> +<section>
+<title>Comprehensive support for neuroimaging research</title> <para>
-&debian; &release; ships with kernel version &kernelversion; for all -architectures.
+&debian; &release; is the first GNU/Linux distribution release ever to offer +comprehensive support for magnetic resonance imaging (MRI) based neuroimaging +research. It comes with up-to-date software for structural image analysis +(e.g. <systemitem role="package">ants</systemitem>), diffusion imaging and +tractography (e.g. <systemitem role="package">mrtrix</systemitem>), stimulus +delivery (e.g. <systemitem role="package">psychopy</systemitem>), MRI +sequence development (e.g. <systemitem role="package">odin</systemitem>), as +well as a number of versatile data processing and analysis suites (e.g. +<systemitem role="package">nipype</systemitem>). Moreover, this release has +built-in support for all major neuroimaging data formats. See the <ulink +url="http://blends.alioth.debian.org/science/tasks/neuroscience-cognitive">Debian +Science</ulink> and <ulink
+url="http://debian-med.alioth.debian.org/tasks/imaging">Debian Med</ulink> +task pages for a comprehensive list of included software and the <ulink +url="http://neuro.debian.net">NeuroDebian webpage</ulink> for further +information.
+<indexterm><primary>neuroimaging research</primary></indexterm> +<indexterm><primary>Debian Med</primary></indexterm> +<indexterm><primary>Debian Science</primary></indexterm> +<indexterm><primary>NeuroDebian</primary></indexterm> +<indexterm><primary>packages</primary><secondary>ants</secondary></indexterm> +<indexterm><primary>packages</primary><secondary>mrtrix</secondary></indexterm> +<indexterm><primary>packages</primary><secondary>psychopy</secondary></indexterm> +<indexterm><primary>packages</primary><secondary>odin</secondary></indexterm> +<indexterm><primary>packages</primary><secondary>nipype</secondary></indexterm> </para>
-<para>
-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; information on how -to work around potential issues is included in later chapters. -</para>
-<section id="kernel-packaging">
-<title>Changes in kernel packaging</title> -<variablelist>
-<varlistentry>
-<term>New OpenVZ<indexterm><primary>OpenVZ</primary></indexterm> kernel flavor</term> -<listitem>
-<para>
-&debian; &release; provides pre-built kernel images for OpenVZ, a -second virtualization solution to go alongside the Linux-VServer -support included in &oldreleasename;. Advantages of OpenVZ include -support for live migration, at the expense of a slightly higher -overhead.
-<indexterm><primary>virtualization</primary></indexterm> -<indexterm><primary>VServer</primary></indexterm> -</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>Kernel x86 packages unified</term> -<listitem>
-<para>
-In previous releases there was a special <literal>-k7</literal> kernel -flavor for 32-bit AMD Athlon/Duron/Sempron processors. This variant -has been dropped; the single single flavor <literal>-686</literal> -now handles all AMD/Intel/VIA 686 class processors. -</para>
-</listitem>
-</varlistentry>
-</variablelist>
-<para>
-Where possible, dummy transition packages that depend on the new packages have -been provided for the dropped packages. -</para>
</section>

-<section id="kernel-initrd" condition="fixme"> -<title>New utilities to generate initrds</title> -<programlisting condition="fixme">TODO: Remove for lenny?</programlisting> -<para>
-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> is not included anymore. -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="&url-wiki;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>. -<systemitem role="package">yaird</systemitem> is not included in &releasename;. -</para>
-<para condition="fixme">
-Upgrading to a &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>. -<programlisting condition="fixme">TODO: Remove? yaird is not in lenny! -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.</programlisting> -</para>
-</section>
-
-</section>
- <section id="emdebian">
- <!-- text taken by Neil Williams #494366 --> - <title>Emdebian 1.0 (based on &debian; &releasename; &release;)</title> - <indexterm><primary>Emdebian</primary></indexterm> -
- <para>

-      Lenny now contains the build tools for Emdebian which allow Debian 
-      source packages to be cross-built and shrunk to suit embedded ARM
-      systems.

- </para>
-
- <para>

-      The Emdebian 1.0 distribution itself contains prebuilt ARM packages 
-      sufficient to create root filesystems that can be customised for
-      specific machines and machine variants. Kernels and kernel modules
-      need to be provided separately. Support for armel and i386 is under
-      development.
-
-      See the <ulink url="http://www.emdebian.org/">Emdebian
-      webpage</ulink> for further information.

- </para>
- </section>
-
- <section>
- <title>Netbook support</title>
-
- <para>

-      Netbooks, such as the Eee PC by Asus, are now supported by
-      Debian. For the Eee PC, have a look at the <systemitem
-      role="package">eeepc-acpi-scripts</systemitem>. Also, Debian
-      features a new Lightweight X11 Desktop Environment, <systemitem
-      role="package">lxde</systemitem>, which is beneficial for
-      netbooks or other computers with relatively low performance.

- </para>
- </section>
-
- <section>
- <title>Java now in Debian</title>
- <para>

-      The OpenJDK Java Runtime Environment <systemitem
-      role="packgage">openjdk-6-jre</systemitem> and Development Kit
-      <systemitem role="packgage">openjdk-6-jdk</systemitem>, needed
-      for executing Java GUI and Webstart programs or building such
-      programs, are now in Debian.  The packages are built using the
-      IcedTea build support and patches from the IcedTea project.
-      <indexterm><primary>Java</primary></indexterm>
-      <indexterm><primary>IcedTea</primary></indexterm>
-      <indexterm><primary>OpenJDK</primary></indexterm>

- </para>
- </section>
</chapter>
. Added: 315 Removed: 320