/[ddp]/manuals/branches/release-notes/lenny/en/release-notes.dbk

Diff of /manuals/branches/release-notes/lenny/en/release-notes.dbk

Parent Directory | Revision Log | View Patch Patch

-revision 4162 by jfs,
Sun Mar 18 18:30:36 2007 UTC
+revision 4284 by fjp,
Sun Apr  1 12:20:29 2007 UTC
 Line 1
  <!DOCTYPE debiandoc PUBLIC "-//DebianDoc//DTD DebianDoc//EN" [
    <!entity % dynamicdata  SYSTEM "../dynamic.ent"       > %dynamicdata;
    <!entity % shareddata   SYSTEM "../release-notes.ent" > %shareddata;
-   <!entity docid "$Id: release-notes.en.sgml,v 1.122 2007-03-18 18:30:36 jfs Exp $">
+   <!entity docid "$Id: release-notes.en.sgml,v 1.214 2007-04-01 12:20:29 fjp Exp $">
  ]>
  <!-- Be careful with automatic reformatting. Please note that the indentation
 Line 24
        <chapt id="about"><heading>Introduction</heading>
          <p>The primary goals of these Release Notes are to inform users
-         of major changes in this release of the Debian distribution, to
+         of major changes in this release of the &debian; distribution, to
          provide information on how to upgrade safely from the previous
-         to the this release and finally to inform users of known potential
+         release to the current release and finally to inform users of known potential
          issues users could encounter when upgrading to or using the
-         release.</p>
+         &releasename; release.</p>
          <p>Note that it is impossible to list every known issue and that
          therefore a selection has been made based on a combination of the
          expected prevalence and impact of issues.</p>
-         <p>The most recent version of this document is always available at
+         <p>The most recent version of this document is always available at <url
-         <url id="&url-release-notes;">. If your version is more than a month
+         id="&url-release-notes;">. If the version you are reading is more than a
-         old, you might wish to download the latest version.</p>
+         month old<footnote>On front page of the PDF version and in the footer
+         of the online, HTML, version</footnote>, you might wish to obtain the
+         latest version.</p>
          <p>Please note that we only support
          and document upgrading from the previous release of Debian (in this case,
          the upgrade from &oldreleasename;). If you need to upgrade from older
-         releases, we suggest you read previous editions of the release notes.</p>
+         releases, we suggest you read previous editions of the release notes and
+         upgrade to &oldreleasename; first.</p>
+         <sect id="bug_reports"><heading>Reporting bugs on this document</heading>
+           <p>We have attempted to test all the different upgrade steps
+           described in this document and we have also tried to anticipate all
+           the possible issues our users might encounter.</p>
+           <p>Nevertheless, If you think you have found any bug in this
+           documentation (incorrect information or information that is missing),
+           please file a bug in the <url id="&url-bts;" name="bug tracking
+           system"> against the <package>release-notes</package> package.</p>
+        </sect>
+         <sect id="upgrade_reports"><heading>Contributing upgrade reports</heading>
+         <p>We welcome any information from users related to upgrades from
+         &oldreleasename; to &releasename;. If you are willing to share information
+         please file a bug in the <url id="&url-bts;" name="bug tracking system">
+         against the <package>upgrade-reports</package> package with your results.</p>
+         <p>Please provide the following information when submitting your upgrade report:
+         <list>
+ <!-- TODO: any more things to add here? -->
+             <item><p>Session logs using <package>script</package>, as described in
+             <ref id="record_session">.</p></item>
+             <item><p>The status of your package database before and after the
+             upgrade, using the backup procedure described at <ref
+             id="backup">.
+             <item><p>Your aptitude logs, available at <file>/var/log/aptitude</file>.</p></item>
+         </list></p>
+         <p>Note: you should take some time to review and remove any sensitive and/or confidential
+         information from the logs before including them in a bug report as the information
+         will be published in a public database.
+         </sect>
+         <sect id="sources"><heading>Sources for this document</heading>
+           <p>This document uses <package>debiandocsgml</package>. Its sources
+           are available in the <em>Debian Documentation Project</em>'s CVS.
+           You can use the <url id="&url-cvs-release-notes;" name="web
+           interface"> to access its files individually through the web and see
+           their changes. For more information on how to access the CVS please
+           consult the <url id="&url-ddp-cvs-info;" name="Debian Documentation Project CVS pages">.
+           </p>
+         </sect>
  <!--
          <sect id="changes"><heading>Changes in the Release Notes</heading>
-Line 66
+Line 120
          <p>This release adds official support for the AMD64 architecture which
          supports 64-bit processors from both Intel (EM64T) and AMD (AMD64).
          During the previous release, &debian; 3.1 ('sarge'), an unofficial
-         version of this port was available. Upgrading from this unofficial
+         version of this port was available.
-         version should be possible using these Release Notes, but is not
+ <![ %amd64 [
-         supported.</p>
+         Upgrading from this unofficial version should be possible using these
+         Release Notes, but is not supported.
+ ]]>
+         </p>
          <p>Official support for the Motorola 680x0 ('m68k') architecture has been
          dropped because it did not meet the criteria set by the Debian Release
-Line 116
+Line 173
          <sect id="newdistro"><heading>What's new in the distribution?</heading>
- <!-- TODO: Numbers need to be updated -->
+ <!-- TODO (jfs): numbers could be entities so that updating them was easier, like
-            <p>TODO: Update numbers</p>
+      in the FAQ -->
+ <!-- TODO: Numbers need to be reviewed, these values have been obtained
+      using the changes-release script -->
             <p>This new release of Debian again comes with a lot more software
             than its predecessor &oldreleasename;; the distribution includes
-            over 9000 new packages. Most of the software in the distribution
+            over 6,200 new packages, for a total of over 18,000 packages. Most
-            has been updated: almost 6500 software packages (this is 73% of
+            of the software in the distribution has been updated: over 10,500
-            all packages in &oldreleasename;). Also, a significant number
+            software packages (this is 67% of all packages in &oldreleasename;).
-            of packages have for various reasons been removed from the distribution.
+            Also, a significant number of packages (over 3400, 22% of the
-            You will not see any updates for these packages and they will be
+            packages in &oldreleasename;) have for various reasons been removed
-            marked as 'obsolete' in package management front-ends.</p>
+            from the distribution.  You will not see any updates for these
+            packages and they will be marked as 'obsolete' in package management
+            front-ends.</p>
             <p>With this release &debian; switches from XFree86 to the 7.1
             release of X.Org, which includes support for a greater range of
-Line 134
+Line 195
             Window System, taking full advantage of hardware
             OpenGL-acceleration for supported devices.</p>
-            <p>&debian; again ships with current desktop applications. Amongst
+            <p>&debian; again ships with several desktop applications and environments. Amongst
-            others it now includes GNOME 2.14, KDE 3.5 and OpenOffice.org 2.0.</p>
+            others it now includes the desktop environments GNOME 2.14<footnote>With some modules from
+            GNOME 2.16.</footnote>, KDE 3.5.5a, and Xfce 4.4. Productivity applications
+            have also been upgraded, including the office suites OpenOffice.org 2.0.4a and
+            KOffice 1.6 as well as GNUcash 2.0.5, GNUmeric 1.6.3 and Abiword 2.4.6</p>
+            <p>Updates to other desktop applications include the upgrade of
+            Evolution 2.6.3 and Gaim 2.0.  The Mozilla suite has also been updated,
+            but the main programs have been renamed: <prgn>iceweasel</prgn>
+            (version 2.0.0.2) is the unbranded <prgn>Firefox</prgn> web browser
+            and <prgn/icedove/ (version 1.5) is the unbranded <prgn/Thunderbird/
+            mail client.</p>
+            <p>This release also includes, amongst others, the following software updates:</p>
+            <p><list>
+            <item>the GNU C library, version 2.3.6.</item>
+            <item>the GNU Compiler Collection 4.1 as default compiler.</item>
+            <item>language interpreters: PHP 5.5, Python 2.4.</item>
+            <item>server software:
+            <p><list>
+            <item>e-mail servers: Exim 4.63 (default email server
+            for new installations), Postfix 2.3, Courier 0.53, Cyrus 2.2.</item>
+ <!-- TODO: Cherokee, lighttpd, and Tomcat 5 are NEW -->
+ <!-- Note: No significant changes for Roxen4, Boa, and thttpd  -->
+            <item>web servers: Apache 2.2, fnord 1.10</item>
+            <item>database servers: MySQL 5.0.32, PostgreSQL 8.1</item>
+            <item>the OpenSSH server, version 4.3.</item>
+            <item>name servers: Bind 9.3, maradns 1.2.</item>
+            <item>directory server: OpenLDAP 2.3</item>
+ <!-- FIXME (JFS): List other server software? RADIUS? Streaming ? -->
+            </list></p>
+            </list></p>
             <p><prgn/aptitude/ is the preferred program for package management
             from console.
-Line 144
+Line 249
             If you are still using <prgn/dselect/, you should switch to
             <package/aptitude/ as the official frontend for package management.</p>
-            <p>The official &debian; distribution now ships on thirteen to fifteen
+            <p>The official &debian; distribution now ships on 19 to 23
             binary CDs (depending on the architecture) and a similar number of
             source CDs. A DVD version of the distribution is also available.</p>
+ <!-- FIXME: Note on LSB support? (3.1?) -->
+         <sect1 id="secureapt"><heading>Secure APT</heading>
+ <!-- FIXME: More content needed here? -->
+            <p><prgn/apt-secure/ (also known as <em/Secure APT/) is now available
+            in &releasename;. This feature adds extra security to &debian;
+            systems by easily supporting strong cryptography and digital
+            signatures to validate downloaded packages. This release includes
+            the <prgn/apt-key/ tool for adding new keys to apt's keyring, which by
+            default includes only the current Debian archive signing key, provided
+            in the <package>debian-archive-keyring</package>.</p>
+            <p>In its default configuration, <prgn>apt-secure</prgn> will
+            warn if packages are downloaded from sources that are not authenticated.
+            Future releases might force all packages to be verified before downloading
+            them. Administrators of unofficial apt repositories are encouraged to
+            generate a cryptographic key and sign their Release files, as well
+            as providing a secure way to distribute their public keys.</p>
+            <p>For more information please read <prgn>apt-secure</prgn>'s manual
+            page, the <url
+            id="http://www.debian.org/doc/manuals/securing-debian-howto/ch7#s-deb-pack-sign"
+            name="Package signing in Debian"> chapter of the <em/Securing Debian
+            Manual/ and the <url id="http://wiki.debian.org/SecureApt"
+            name="wiki documentation">.</p>
+         </sect1>
          <sect1 id="volatile"><heading>debian-volatile now an official service</heading>
             <p>The <em/debian-volatile/ service that was introduced as an
-Line 169
+Line 302
          </sect1>
          </sect>
-         <sect id="inst-new"><heading>What's new in the installation system?</heading>
+       <sect id="improves_in_etch"><heading>System improvements</heading>
+        <p>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.
+        </p>
+        <p><taglist>
+ <!-- Bug #301138, fixed in etch -->
+        <tag>Priority for basic development packages lowered</tag>
+        <item><p>A number of development packages that used to be priority
+        <em/standard/ are now priority <em/optional/, which means they will
+        no longer be installed by default.
+        This includes the standard C/C++-compiler, <package>gcc</package>,
+        as well as some other software (<package>dpkg-dev</package>,
+        <package>flex</package>, <package>make</package>) and development
+        headers (<package>libc6-dev</package>,
+        <package>linux-kernel-headers</package>).</p>
+ <!-- TODO: Point to the bug report for the full list of packages in case
+      users want to remove them ? -->
+        <p>If you do wish to have these packages on your system, the easiest way
+        to install them is by installing <package/build-essential/, which will
+        pull in most of them.</p>
+        </item>
+ <!-- FIXME: Bug Manoj for a link to documentation on enabling SELinux -->
+        <tag>SELinux priority standard, but not enabled by default</tag>
+        <item><p>The packages needed for SELinux support have been
+        promoted to priority <em/standard/. This means that they will be
+        installed by default during new installations. For existing systems
+        you can install SELinux using:
+        <example>
+ # aptitude install selinux-basics
+ </example></p>
+        <p>Note that SELinux support is not enabled by default. If you want to
+        secure your system using SELinux, you will need to enable it by adding
+        the kernel boot parameter <tt/selinux=1/. Additional information
+        can be found on the <url id="&url-wiki-selinux" name="Debian Wiki">.
+        </p></item>
+        <tag>New default inet superdaemon</tag>
+        <item><p>The default inet superdaemon for &releasename; is
+        <package>openbsd-inetd</package> instead of <package>netkit-inetd</package>.
+        It will not be started if no services are configured, which is the
+        default. The new default will be installed automatically on upgrading.
+        </p></item>
+        <tag>Default <prgn/vi/ clone changed</tag>
+        <item><p>The <prgn/vi/ clone installed by default is now a compact version
+        of <prgn/vim/ (<package/vim-tiny/) instead of <package/nvi/.</p></item>
+        <tag>Changes in default features for <tt>ext2</tt>/<tt>ext3</tt></tag>
+        <item><p>New ext2 and ext3 filesystems will be created with features
+        <em/dir_index/ and <em/resize_inode/ enabled by default. The first
+        the so 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).</p>
+        <p>Users upgrading from &oldreleasename; could consider adding the
+        <em/dir_index/ flag manually using <prgn/tune2fs/<footnote>
+        The flag <em/filetype/ should already be set on most file systems, except
+        possibly on systems installed before &oldreleasename;.
+        </footnote>; the <em/reset_inode/ flag cannot be added to an existing
+        file system. It is possible to check which flags are set for a file
+        system using <tt/dumpe2fs -h/.</p></item>
+ <!-- TODO: Add for lenny, link to utf8-migration-tool, which is right now not
+      available for etch -->
+        <tag>Default encoding for &releasename; is UTF-8</tag>
+        <item><p>The default encoding for new &debian installations is UTF-8. A
+        number of applications will also be set up to use UTF-8 by default.</p>
+        <p>Users upgrading to &releasename; that wish to switch to UTF-8 will
+        need to reconfiguring their environment and locale definitions. The
+        system-wide default can be changed using <tt/dpkg-reconfigure locales/;
+        first select a UTF-8 locale for your language and country and then
+        set that as default. Note that switching to UTF-8 means that you will
+        probably also need to convert existing files from your previous
+        (legacy) encoding to UTF-8.</p>
+        <p>The package <package/utf8-migration-tool/ contains a tool that may
+        help the migration, however that package is only available in unstable
+        as it was not ready in time for &releasename;. Making a backup of
+        your data and configuration before using the tool is strongly
+        recommended.</p>
+        <p>Note that not some applications may not yet work correctly in a UTF-8
+        environment (mostly display issues).</p></item>
+        </taglist></p>
+       <p>The <url id="http://wiki.debian.org/Sarge2EtchUpgrade"
+       name="Debian Wiki"> has some additional information about changes between
+       &oldreleasename; and &releasename;.</p>
+       </sect>
+       </chapt>
+       <chapt id="installing"><heading>Installation System</heading>
+         <p>The Debian Installer is the official installation system for Debian.
+         It offers a variety of installation methods. Which methods
+         are available to install your system depends on your architecture.</p>
+         <p>Images of the installer for &releasename; and the Installation Guide
+         can be found on the <url id="&url-installer;" name="Debian website">.</p>
+         <p>The Installation Guide is also included on the first CD/DVD of the
+         official Debian CD/DVD sets, at:
+         <example>
+ /doc/install/manual/<var>language</var>/index.html
+         </example></p>
+         <p>You may also want to check the <url id="&url-installer;index#errata"
+         name="errata"> for debian-installer for a list of known issues.</p>
+ <![ %alpha [
+         <!-- TODO: Still true? -->
+         <p>The installer can only be used to install on alpha systems which
+         support the SRM console. Be sure to switch your system to SRM before
+         starting the installation. If your machine supports only the AlphaBIOS/ARC
+         console, you can still install &releasename; using a (minimal) &oldreleasename;
+         installation and a subsequent upgrade. For more information about the
+         different consoles please read the references on the
+         <url id="http://www.debian.org/ports/alpha" name="Debian alpha port web pages">.
+         </p>
+ ]]>
+ <![ %sparc [
+       <sect id="sparc_fb"><heading>Issues with framebuffer on &arch-title;</heading>
+         <p>Because of display problems on some systems, framebuffer support is
+         disabled by default for &arch-title; for most graphics cards. This can
+         result in ugly display on systems that do properly support the framebuffer.
+         If you see display problems in the installer, you can try booting the installer
+         with the parameter <tt>framebuffer=true</tt>.
+         Please let us know if the framebuffer is not used by default, but works for
+         your hardware.</p>
+       </sect>
+ ]]>
+       <sect id="inst-new"><heading>What's new in the installation system?</heading>
-         <!-- TODO: Hhhm. Whats new in the installer ? -->
             <p>There has been a lot of development on the Debian Installer
             since its first official release with &oldreleasename; resulting
             in both improved hardware support and some exciting new features.</p>
-Line 214
+Line 488
               will create an encrypted LVM partition that contains any other
               filesystems (except <file>/boot</file>) as logical volumes.</p></item>
- <![ %i386-amd64 [
+ <![ %g-i [
               <tag>Graphical user interface</tag>
-              <item><p>If you prefer a graphical user interface, try booting
+              <item>
+ <![ %i386-amd64 [
+              <p>If you prefer a graphical user interface, try booting
               the installer with <tt/installgui/.</p>
-              <p>The functionality of the graphical installer is almost identical
-              to the regular installer, only the presentation differs. There is one
-              exception: the graphical frontend does not support setting up
-              encrypted partitions using random keys.</p>
-              <p>Note: the graphical user interface is not available for all
-              architectures.</p></item>
  ]]>
  <![ %powerpc [
-              <tag>Graphical user interface</tag>
+              <p>For &arch-title; a separate installation image using a
-              <item><p>For &arch-title; a separate installation image using a
               graphical user interface is available on an experimental basis.
               It is known to work on most CHRP systems that have an ATI graphics
               card, but has been insufficiently tested on &arch-title; to include
               it on the normal installation CDs.</p>
               <p>If you'd like to try the graphical installer, look for the
-              "gtk-miniiso" image.</p></item>
+              "gtk-miniiso" image.</p>
+ ]]>
+              <p>The functionality of the graphical installer is almost identical
+              to the regular installer, only the presentation differs. There is one
+              exception: the graphical frontend does not support setting up
+              encrypted partitions using random keys.</p>
+              <p>The major advantage of the graphical user interface is that it
+              supports more languages than the regular user interface (newt).
+              Information about the graphical installer and the most important
+              differences between the graphical and regular installer are documented
+              in an appendix in the installation guide.</p>
+              <p>Note: the graphical user interface is not available for all
+              architectures.</p>
+              </item>
  ]]>
               <tag>Rescue mode</tag>
-Line 253
+Line 536
               up <prgn/sudo/ so that the first user can use that for
               system administration.</p></item>
- <!-- FIXME: Bug Manoj for a link to documentation on enabling SELinux -->
+              <tag>Cryptographic verification of downloaded packages</tag>
-              <tag>SELinux</tag>
+              <item><p>Packages downloaded with the installer are
-              <item><p>The packages needed for SELinux support have been
+              now cryptographically checked using <prgn/secure apt/
-              promoted to priority "standard". This means that they will be
+              making it more difficult to compromise a system being
-              installed by default if you select the Standard task during
+              installed over the network.</p></item>
-              installation. However, SELinux support is not enabled by default.
-              If you want to secure your system using SELinux, you will need
+              <tag>Simplified mail configuration</tag>
-              to enable it manually after the installation.</p></item>
+              <item><p>The installation system sets up a basic configuration for
+              the system's mail server which will only provide for local e-mail
+              delivery, if the "standard system" is installed. The mail
+              server will be unavailable to other systems connected to the same
+              network. If you want to configure your system to handle e-mail not
+              local to the system (either to send e-mail or to receive it) you
+              will have to reconfigure the mail system after
+              installation.</p></item>
+              <tag>Desktop selection</tag>
+              <item><p>The installation system will install
+              a GNOME desktop as the default desktop if the user asks for one.</p>
+              <p>However, users wishing to install alternate desktop environments
+              can easily do so by adding boot parameters:
+              <tt>tasks="standard, kde-desktop"</tt> for KDE and
+              <tt>tasks="standard, xfce-desktop"</tt> for Xfce. Note that this
+              will not work when installing from a full CD image without using
+              a network mirror as an additional package source; it will work
+              when using a DVD image or any other installation method.</p>
+              <p>There are also separate CD images available that install the
+              KDE or Xfce desktop environment by default.</p></item>
  <![ %not-s390 [
               <tag>New languages</tag>
               <item><p>Thanks to the huge efforts of translators, Debian can
-              now be installed in $FIXME$ languages.
+              now be installed in 47 languages using the text-based
+              installation user interface. This is six languages more
+              than in &oldreleasename;. Languages added in this release include
+              Belarusian, Esperanto, Estonian, Kurdish, Macedonian,
+              Tagalog, Vietnamese and Wolof.
+              Languages dropped in this release due to lack of translation
+              updates include Persian and Welsh.</p>
  <![ %g-i [
-              If the graphical user interface is used, an additional $FIXME$
+              <p>If the graphical user interface is used, an additional eleven
-              languages are supported.
+              languages are supported. These languages can only be selected
+              using this installer as their character sets cannot be presented
+              in a non-graphical environment. The new languages are:
+              Bengali, Dzongkha, Gujarati, Hindi, Georgian, Khmer, Malayalam,
+              Nepali, Punjabi, Tamil and Thai.</p>
  ]]>
+              <p>Users that do not wish to use any locale can now select
+              <em/C/ as their preferred locale in the installer's language
+              selection.
+              More information on language coverage is available at the
+              <url id="&url-d-i-i18n;" name="d-i languages list">.
               </p></item>
+              <tag>Simplified localization and timezone selection</tag>
+              <item><p>Configuration of language, countries and timezones
+              have been simplified to reduce the amount of information
+              needed from the user. The installer will now guess
+              what the system's country and timezone is based on the
+              language selected, or will provide a limited selection
+              if it cannot. Users can still introduce obscure
+              combinations if need be.</p></item>
+       <tag>Improved system-wide localization</tag>
+       <item><p>Most of the internationalization and localization tasks that
+       were previously handled by the <package>localization-config</package> tool are now
+       included in the stock &debian; installer or in packages themselves. This
+       means that selection of a language will automatically install packages
+       necessary for that language (dictionaries, documentation, fonts...) both
+       in standard and desktop environments. Configuration that is no longer
+       handled automatically include the papersize configuration and some
+       advanced X Windows keyboard settings for some languages.</p>
+       <p>Note that language specific packages will only be installed
+       automatically if they are available during the installation.</p></item>
  ]]> <!-- not-s390 -->
             </taglist></p>
-Line 295
+Line 635
             and encrypted LVM. See the documentation for details.</p>
           </sect1>
-         </sect>
-       </chapt>
- <!-- TODO: Mention default usage of UTF-8 for new installs -->
-       <chapt id="installing"><heading>New installations</heading>
-         <p>The Debian Installer is the official installation system for Debian.
-         It offers a variety of installation methods. Which methods
-         are available to install your system depends on your architecture.</p>
-         <p>Images of the installer for &releasename; and the Installation Guide
-         can be found on the <url id="&url-installer;" name="Debian website">.</p>
-         <p>The Installation Guide is also included on the first CD/DVD of the
-         official Debian CD/DVD sets, at:
-         <example>
- /doc/install/manual/<var>language</var>/index.html
-         </example></p>
-         <p>You may also want to check the <url id="&url-installer;index#errata"
-         name="errata"> for debian-installer.</p>
- <![ %alpha [
-         <!-- TODO: Still true? -->
-         <p>The installer can only be used to install on alpha systems which
-         support the SRM console. Be sure to switch your system to SRM before
-         starting the installation. If your machine supports only the AlphaBIOS/ARC
-         console, you can still install &releasename; using a (minimal) &oldreleasename;
-         installation and a subsequent upgrade. For more information about the
-         different consoles please read the references on the
-         <url id="http://www.debian.org/ports/alpha" name="Debian alpha port web pages">.
-         </p>
- ]]>
- <![ %sparc [
-       <sect id="sparc_fb"><heading>Issues with framebuffer on &arch-title;</heading>
-         <p>Because of display problems on some systems, framebuffer support is
-         disabled by default for &arch-title; for most graphics cards. This can
-         result in ugly display on systems that do properly support the framebuffer.
-         If you see display problems in the installer, you can try booting the installer
-         with the parameter <tt>framebuffer=true</tt>.
-         Please let us know if the framebuffer is not used by default, but works for
-         your hardware.</p>
        </sect>
- ]]>
        <sect id="popcon"><heading>Popularity contest</heading>
-         <p>Unlike for the previous release, the installation system will again offer
+         <p>The installation system will again offer
-         to install the <package/popularity-contest/ package.</p>
+         to install the <package/popularity-contest/ package. This package was not
+         installed by default in &oldreleasename; but it was installed in older releases.</p>
          <p><package/popularity-contest/ provides the Debian project with valuable information
          on which packages in the distribution are actually used. This information
-Line 362
+Line 655
          you will thereby help improve Debian.</p>
        </sect>
        </chapt>
-Line 388 
 release: architectures:
+Line 682 
 release: architectures:
            directly related to the upgrade process but which could still be
            relevant.</p>
+        <sect1><heading>Backup any data or configuration information</heading>
            <p>Before upgrading your system, it is strongly recommended that
            you make a full backup, or at least backup any data or
            configuration information you can't afford to lose. The upgrade
-Line 409 
 release: architectures:
+Line 705 
 release: architectures:
            backup may help to restore or recreate the old settings. You may
            also want to inform users about this.</p>
+           <p>Any package installation operation must be run with superuser
+           privileges, so either login as root or use <prgn/su/ or
+           <prgn/sudo/ to gain the necessary access rights.</p>
+           <p>The upgrade has a few preconditions; you should check them
+           before actually executing the upgrade.</p>
+        </sect1>
+        <sect1><heading>Inform users in advance</heading>
            <p>It's wise to inform all users in advance of any upgrades you're
            planning, although users accessing your system via an <prgn/ssh/
            connection should notice little during the upgrade, and should be
-           able to continue working. If you wish to take extra precautions, back up or
+           able to continue working. </p>
-           unmount users' partitions (<file>/home</file>) before upgrading. A
-           reboot will not normally be necessary, unless you also plan to
+           <p>If you wish to take extra precautions, back up or
+           unmount users' partitions (<file>/home</file>) before upgrading.</p>
+ <!-- JFS: Not true in etch, maybe for lenny?
+           <p>A reboot will not normally be necessary, unless you also plan to
            upgrade your kernel.</p>
+ -->
+           <p>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.</p>
-           <!-- TODO: Is not necessary to change the kernel? e.g. udev ? -->
+        </sect1>
-           <p>Distribution upgrade should be done either locally from a
+        <sect1><heading>Prepair a safe environment for the upgrade</heading>
+           <p>The distribution upgrade should be done either locally from a
            textmode virtual console (or a directly connected serial
            terminal), or remotely via an <prgn/ssh/ link.</p>
+           <p>In order to gain extra safety margin, we suggest you to run
+           upgrade processes in the virtual console provided by the
+           <prgn/screen/ program which enables the safe reconnection and ensures
+           the uninterrupted upgrade processes even if the remote connection
+           process fails by chance.</p>
+ <!-- JFS: probably can be removed for lenny -->
+           <p>If you are upgrading remotely via an <prgn/ssh/ link it is highly
+           recommended that you take the necessary precautions to be able to
+           access the server through a remote serial terminal. There are chances
+           that, after upgrading the kernel and rebooting, some devices will
+           be renamed (as described in <ref id="device-reorder">) and you will
+           have to fix the system configuration through a local console. Also,
+           if the system is rebooted accidentally in the middle of an upgrade
+           there are chances you will need to recover using a local console.</p>
+ <!-- END - remove for lenny -->
            <p><strong/Important!/ You should <em/not/ upgrade using <prgn/telnet/,
            <prgn/rlogin/, <prgn/rsh/, or from an X session managed by <prgn/xdm/,
            <prgn/gdm/ or <prgn/kdm/ etc on the machine you are upgrading. That is
-Line 431 
 release: architectures:
+Line 765 
 release: architectures:
            half-upgraded.</p>
            <!-- TODO: surely gdm/kdm are sane? -->
+        </sect1>
-           <p>Any package installation operation must be run with superuser
-           privileges, so either login as root or use <prgn/su/ or
-           <prgn/sudo/ to gain the necessary access rights.</p>
-           <p>The upgrade has a few preconditions; you should check them
-           before actually executing the upgrade.</p>
-        <sect1><heading>Make sure you have sufficient space for the upgrade</heading>
-        <p>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 <ref id="upgrading_other">. You will first need
-        enough hard disk on the filesystem partition that holds <file>/var/</file>
-        to temporarily download the packages that will be installed in your system.
-        After the download, you will probably need more space in other
-        filesystem partitions in order to both install upgraded packages (which
-        might contain bigger binaries or more data) and new packages that will be pulled
-        in for the upgrade. If your system does not have sufficient space you
-        might end up with an incomplete upgrade that might be difficult to
-        recover from.</p>
- <!-- JFS: Apt will not always abort if you do not have enough disk space.
-        For reference see: #247331, #214119, #192146, #185201, #40438 and #32919 -->
-        <p>Both <prgn/aptitude/ and <prgn/apt/ will show you detailed information
-        of the disk space needed for the installation. Before executing the
-        upgrade, you can see this estimate by running:
-        </p>
-          <p><example>
- # aptitude -y -s -f --with-recommends 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.
- </example></p>
-        <p>If you do not have enough space for the upgrade, make sure you free up
-        space beforehand. You can:
-        </p>
- <!-- JFS There are more tips at
-        http://lists.debian.org/debian-user/2005/11/msg02078.html
-        or
-        http://www.debian-administration.org/articles/143
-        but maybe that should be in the Debian Reference best and pointed from here -->
-        <p>
-        <list>
- <!-- JFS: Does aptitude to 'apt-get autoclean' by itself? -->
-        <item>Remove packages that have been previously downloaded for
-        installation (at <file>/var/cache/apt/archive</file>), cleaning up the
-        package cache by running <prgn>apt-get clean</prgn>.
- <!-- JFS Point to http://www.enricozini.org/blog/eng/pkgsizestat.html ?
-      Enrico's script shows files that occupy space in a given partition
-      which might be good for systems that are heavily partitioned -->
-        <item>Remove old packages you no longer use. If you have
-        <prgn/popularity-contest/ installed, you can use
-        <prgn/popcon-largest-unused/ to list the packages you do not use in the
-        system that occupy the most space. You can also use <prgn/deborphan/
-        or <prgn/debfoster/ to find obsolete packages (see
-        <ref id="obsolete">).
-        <item>Remove packages taking up too much space, which are not currently
-        needed (you can always reinstall them after the
-        upgrade). You can list the packages that take up most of the disk space
-        with <prgn/dpigs/ (available in the <package/debian-goodies/ package)
-        or with <prgn/wajig/ (running <tt>wajig size</tt>).
-        <item>Temporarily move to another system, or permanently remove, system
-        logs residing under <file>/var/log/</file>.
-        </list></p>
-         </sect1>
          <sect1 id="glibc-kernel"><heading>Support for 2.2-kernels has been dropped</heading>
            <p>In case you run a kernel prior to 2.4.1,
            you need to upgrade to (at least) the
-.4-series before upgrading <package/glibc/,
+.4-series before upgrading <package/glibc/.
-           so preferably before starting the upgrade.
+           This should preferably be done before starting the upgrade.
-           It is recommended to upgrade to the 2.6-kernel series.
+           It is recommended you directly upgrade to the 2.6-kernel (available
+           in &oldreleasename;, instead of upgrading to a 2.4-kernel series.
            </p>
          </sect1>
-         <sect1 id="kernelorder"><heading>Upgrade your kernel or userland first?</heading>
- <!-- TODO: remove this section, it is just that one can see "needs to be done" on the normal output -->
-           <p>[FIXME: Needs decision/documentation whether to upgrade userland or kernel first.]</p>
-         </sect1>
          </sect>
          <sect id="system-status">
-Line 536 
 Would download/install/remove packages.
+Line 790 
 Would download/install/remove packages.
          latest point release of &oldreleasename;.  If you have not done this
          or are unsure, follow the instructions in <ref id="old-upgrade">.</p>
+        <sect1><heading>Review actions pending in package manager</heading>
+           <p>In some cases, the use of <prgn/apt-get/ for installing packages instead
+           of <prgn/aptitude/ might make <prgn/aptitude/ consider a package as
+           "unused" and schedule it for removal. In general, the system should be
+           fully up-to-date and "clean".</p>
+           <p>Because of this you should review if there are any pending actions
+           in the package manager <prgn/aptitude/. If a package is scheduled
+           for removal or update in the package manager, it might impact negatively
+           on the upgrade procedure. Note that this is only possible if your
+           <file/sources.list/ still points to <em/&oldreleasename/; and not to
+           <em/stable/ or <em/&releasename;/; see <ref id="old-sources">.</p>
+           <p>To do this, you have to run <prgn/aptitude/'s user interface and
+           press 'g' ("Go"). If it shows any actions, you should review them and
+           either fix them or implement the suggested actions. If no actions are
+           suggested you will be presented with a message saying "No packages are
+           scheduled to be installed, removed, or upgraded".</p>
+         </sect1>
          <sect1><heading>Disabling APT pinning</heading>
            <p>If you have configured APT to install certain packages from a
-Line 569 
 Would download/install/remove packages.
+Line 845 
 Would download/install/remove packages.
            or
            <example>
- # dpkg --get-selections &gt; ~/curr-pkgs.txt
+ # dpkg --get-selections "*" &gt; ~/curr-pkgs.txt
            </example></p>
            <p>It is desirable to remove any holds before upgrading. If any
-Line 628 
 Would download/install/remove packages.
+Line 904 
 Would download/install/remove packages.
          </sect1>
          </sect>
+ <!-- JFS: This section should be probably removed for lenny -->
+         <sect id="handle-conflict"><heading>Manually unmarking packages</heading>
+         <p>To prevent <prgn/aptitude/ from removing some packages that were pulled
+         in through dependencies, you need to manually unmark them as <em/auto/
+         packages. This includes OpenOffice and Vim for desktop installs:
+ <!-- This is a no-op if none of them are installed -->
+ <example>
+ # aptitude unmarkauto openoffice.org vim
+ </example></p>
+ <!-- JFS: This cannot be in the same line as above since it produces an ugly output if
+      you just have 2.4 kernels installed -->
+         <p>And 2.6 kernel images if you have installed them using a kernel metapackage:
+ <example>
+ # aptitude unmarkauto $(dpkg-query -W 'kernel-image-2.6*' | cut -f1)
+ </example></p>
+         <p>Note: You can review which packages are marked as <em/auto/ in aptitude running:
+ <example>
+ # aptitude search 'i~M &lt;package name&gt;'
+ </example></p>
+         </sect>
          <sect id="upgrade-process"><heading>Preparing sources for APT</heading>
-Line 793 
 deb file:/var/ftp/debian &releasename; m
+Line 1095 
 deb file:/var/ftp/debian &releasename; m
            <p>Next you should double check that the APT source entries (in
            <file>/etc/apt/sources.list</file>) refer either to
-           "<tt/&releasename;/" or to "<tt>stable</tt>". Note: source
+           "<tt/&releasename;/" or to "<tt>stable</tt>". There should not be
-           lines for a CD-ROM will often refer to "<tt/unstable/";
+           any sources entries pointing to &oldreleasename;.
+           Note: source lines for a CD-ROM will often refer to "<tt/unstable/";
            although this may be confusing, you should <em/not/ change it.</p>
+         <sect1 id="record_session"><heading>Recording the session</heading>
            <p>It is strongly recommended that you use the
            <prgn>/usr/bin/script</prgn> program to record a transcript of the
            upgrade session. Then if a problem occurs, you will have a log of
-Line 804 
 deb file:/var/ftp/debian &releasename; m
+Line 1109 
 deb file:/var/ftp/debian &releasename; m
            report. To start the recording, type:
            <example>
- # script -a ~/upgrade-to-&releasename;.typescript
+ # script -t -a ~/upgrade-&releasename;.script 2>~/upgrade-&releasename;.time
            </example>
            or similar. Do not put the typescript file in a temporary
-Line 814 
 deb file:/var/ftp/debian &releasename; m
+Line 1119 
 deb file:/var/ftp/debian &releasename; m
            <p>The typescript will also allow you to review information that has
            scrolled off-screen. Just switch to VT2 (using <tt/Alt-F2/) and, after
-           logging in, use <tt>less ~root/upgrade-to-&releasename;.typescript</tt>
+           logging in, use <tt>less -R ~root/upgrade-&releasename;.script</tt>
            to view the file.</p>
            <p>After you have completed the upgrade, you can stop <prgn/script/
            by typing <tt/exit/ at the prompt.</p>
+ <!-- TODO: Could mention the script I provided in 400725 which is useful if you
+      have not dumped the timing file -->
+           <p>If you have used the <em>-t</em> switch for <prgn/script/
+           you can use the <prgn/scriptreplay/ program to replay the whole session:
+           <example>
+ # scriptreplay ~/upgrade-&releasename;.time ~/upgrade-&releasename;.script
+           </example>
+           </p>
+         </sect1>
          <sect1 id="updating_lists"><heading>Updating the package list</heading>
            <p>First the list of available packages for the new release needs to
-           be fetched. This is done by executing<footnote>We use <prgn/apt-get/
+           be fetched. This is done by executing:</p>
-           for this because the &oldreleasename; version <prgn/aptitude/ may fail
-           when new sources have been added to <file/sources.list/.</footnote>:</p>
            <p><example>
- # apt-get update
+ # aptitude update
            </example></p>
+ <!-- JFS: Hopefully this will be fixed in lenny -->
+           <p>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.
+           </p>
+         </sect1>
+        <sect1><heading>Make sure you have sufficient space for the upgrade</heading>
+        <p>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 <ref id="upgrading_other">. You will first need
+        enough hard disk on the filesystem partition that holds <file>/var/</file>
+        to temporarily download the packages that will be installed in your system.
+        After the download, you will probably need more space in other
+        filesystem partitions in order to both install upgraded packages (which
+        might contain bigger binaries or more data) and new packages that will be pulled
+        in for the upgrade. If your system does not have sufficient space you
+        might end up with an incomplete upgrade that might be difficult to
+        recover from.</p>
+ <!-- JFS: Apt will not always abort if you do not have enough disk space.
+        For reference see: #247331, #214119, #192146, #185201, #40438 and #32919 -->
+        <p>Both <prgn/aptitude/ and <prgn/apt/ will show you detailed information
+        of the disk space needed for the installation. Before executing the
+        upgrade, you can see this estimate by running:
+        </p>
+          <p><example>
+ # aptitude -y -s -f --with-recommends 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.
+        </example></p>
+        <p>If you do not have enough space for the upgrade, make sure you free up
+        space beforehand. You can:
+        </p>
+ <!-- JFS There are more tips at
+        http://lists.debian.org/debian-user/2005/11/msg02078.html or
+        http://www.debian-administration.org/articles/143
+        but maybe that should be in the Debian Reference best and pointed from here -->
+        <p>
+        <list>
+ <!-- JFS: Does aptitude to 'apt-get autoclean' by itself? -->
+        <item>Remove packages that have been previously downloaded for
+        installation (at <file>/var/cache/apt/archive</file>), cleaning up the
+        package cache by running <prgn>apt-get autoclean</prgn> or
+        <prgn>aptitude autoclean</prgn> will remove unused package files.  If
+        that does not give you enough space, you can clean up the package cache
+        further by running <prgn>apt-get clean</prgn> or <prgn>aptitude
+        clean</prgn>.
+ <!-- JFS Point to http://www.enricozini.org/blog/eng/pkgsizestat.html ?
+      Enrico's script shows files that occupy space in a given partition
+      which might be good for systems that are heavily partitioned -->
+        <item>Remove old packages you no longer use. If you have
+        <prgn/popularity-contest/ installed, you can use
+        <prgn/popcon-largest-unused/ to list the packages you do not use in the
+        system that occupy the most space. You can also use <prgn/deborphan/
+        or <prgn/debfoster/ to find obsolete packages (see
+        <ref id="obsolete">).
+        Alternatively you can start <prgn/aptitude/ into "visual mode" and find
+        obsolete packages under "Obsolete and Locally Created Packages".
+        <item>Remove packages taking up too much space, which are not currently
+        needed (you can always reinstall them after the
+        upgrade). You can list the packages that take up most of the disk space
+        with <prgn/dpigs/ (available in the <package/debian-goodies/ package)
+        or with <prgn/wajig/ (running <tt>wajig size</tt>).
+ <!-- TODO: consider this for lenny
+ You can list packages that take up most of the disk space with
+        <prgn/aptitude/ .  Start <prgn/aptitude/ into "visual mode", select
+        "Views" and "New Flat Package List" (this menu entry is available only
+        after etch version), press "l" and enter "~i", press "S" and enter
+        "~installsize", then it will give you nice list to work with.  Doing
+        this after partial upgrade described in <ref id="upgrading_aptitude">
+        should give you access to this new feature.
+ -->
+        <item>Temporarily move to another system, or permanently remove, system
+        logs residing under <file>/var/log/</file>.
+        </list></p>
+        <p>Note that in order to safely remove packages, it is advisable to
+        switch your <file>sources.list</file> back to &oldreleasename; as
+        described in <ref id="old-sources">.</p>
          </sect1>
+         <sect1 id="minimal_upgrade"><heading>Minimal system upgrade</heading>
+         <p>Before you start the full upgrade you have to make a minimal system upgrade
+         to ensure you have the basic system libraries upgraded.</p>
+         <p>First run:
+           <example>
+ # aptitude upgrade
+           </example>
+         </p>
+         <p>This will upgrade a number of packages, include <package/base-files/,
+         <package/console-common/, and <package/debconf/. You will be asked information
+         about your console keymap as well as the default level and frontend for
+         package configuration questions.</p>
+         <p>You have to follow the minimal upgrade with:
+           <example>
+ # aptitude install initrd-tools
+           </example></p>
+         <p>This step will automatically upgrade <package/libc6/ and
+         <package/locales/ and will pull in SE linux support libraries
+         (<package/libselinux1/). At this point, some running services will be
+         restarted, including <prgn/xdm/, <prgn/gdm/ and <prgn/kdm/, as a
+         consequence local X11 sessions will be disconnected.</p>
+         <p>The following step depends on your system configuration:
- <!-- FJP: This next section can probably be dropped for etch -->
+           <p><list>
-         <sect1 id="upgrading_aptitude"><heading>Upgrading aptitude</heading>
+           <item><p>If you are running a system with a Desktop environment, you first
+           have to verify if you have <package/libfam0c102/ and <package/xlibmesa-glu/
+           installed. You have them installed if you have selected &oldreleasename;'s
+           Desktop task but if you have a custom-made environment you have to manually
+           verify it:
+           <example>
+ # dpkg -l "libfam*" | grep ^ii
+ # dpkg -l "xlibmesa-glu*" | grep ^ii
+           </example>
-           <p>Upgrade tests have shown that &releasename;'s version of
+           if you have them installed then you have to install the latest
-           <prgn/aptitude/ is better at solving the complex dependencies during
+           versions from &releasename;. The following command will install both,
-           an upgrade than either <prgn/apt-get/ or &oldreleasename;'s
+           if you have only one of them you should remove the other:
-           <prgn/aptitude/.
-           It should therefore be upgraded first using:
            <example>
- # aptitude install aptitude
+ # aptitude install libfam0 xlibmesa-glu
            </example></p>
-           <p>You will be shown a list of the changes that will be
+           <p>Note that doing this will also install the File Alteration Monitor
-           made and asked you to confirm them. You should take a careful look at
+           (<package/fam/) as well as the RPC portmapper (<package/portmap/) if
-           the proposed changes, especially packages that will be removed by the
+           not already available in your system. Both packages will enable a new
-           upgrade, before you confirm.</p>
+           network service in the system although they can both be configured to
+           be bound to the (internal) loopback network device.</p>
-           <p>In some cases if a large number of packages is listed for removal,
-           you may be able to reduce this list by "pre-upgrading" selected other
+           <item><p>For all other systems, verify if you have any
-           packages alongside <package/aptitude/. An example may clarify this.
+           X Window System packages installed by running the following command:
-           During upgrade tests for systems having KDE installed, we have seen
+           <example>
-           that this step would cause removal of a large number of KDE packages
+ # dpkg -l "xfree86-common*" | grep ^ii
-           and/or perl. The solution proved to be to <tt>install aptitude perl</tt>
+           </example>
-           instead of <tt>install aptitude</tt>.</p>
+           Notice that if you selected some server tasks in &oldreleasename; you
+           might have parts of it installed. If you have the X Window System
+           installed you will need to upgrade to the latest version in
+           &releasename;:
+           <example>
+ # aptitude install x11-common
+           </example>
+           <p>If you are running a server system, with no X packages
+           installed, you do not need to do any additional installation steps.
+           </p>
+           </list></p>
+         <p>Note: After this minimal upgrade has finished you might want to
+         consider upgrading the kernel before upgrading the full system,
+         as described in <ref id="newkernel">.
+         Doing so reduces the timeframe in which the system will not
+         properly boot if rebooted accidentally.
+         This is because the full upgrade described in the next section will
+         install a new version of <prgn/udev/ and will remove <prgn/hotplug/.
+         This might not be an option for systems with a Desktop environment,
+         as large parts of the system will be removed if you do the kernel
+         upgrade here.</p>
          </sect1>
+ <!-- TODO: For lenny, consider restoring the section 'Upgrade aptitude' -->
          <sect1 id="upgrading_other"><heading>Upgrading the rest of the system</heading>
            <p>You are now ready to continue with the main part of the
            upgrade. Execute:</p>
+ <!-- NOTE (jfs): we have not tested with the -f and with-recommends option -->
            <p><example>
- # aptitude -f --with-recommends dist-upgrade
+ # aptitude dist-upgrade
            </example></p>
            <p>This will perform a complete upgrade of the system, i.e. install
-Line 875 
 deb file:/var/ftp/debian &releasename; m
+Line 1350 
 deb file:/var/ftp/debian &releasename; m
            possible dependency changes between packages in different releases.
            If necessary, it will install some new packages (usually new library
            versions, or renamed packages), and remove any conflicting obsoleted
-           packages (such as <package>console-tools-libs</package>).</p>
+           packages.</p>
            <p>When upgrading from a set of CD-ROMs, you will be asked to
            insert specific CDs at several points during the upgrade. You
-Line 889 
 deb file:/var/ftp/debian &releasename; m
+Line 1364 
 deb file:/var/ftp/debian &releasename; m
            packages for installation or by trying <tt>aptitude -f install
            <var>package</var></tt>.</p>
-           <p>The <tt/--fix-broken/ (or just <tt/-f/) option causes
-           <package/apt/ to attempt to correct a system with broken
-           dependencies in place. <package/apt/ does not allow broken package
-           dependencies to exist on a system.</p>
          </sect1>
          <sect1 id="trouble"><heading>Possible issues during upgrade</heading>
-Line 949 
 E: Dynamic MMap ran out of room
+Line 1419 
 E: Dynamic MMap ran out of room
            backports installed. A file conflict will result in an error like:
            <example>
- Unpacking replacement <var>&lt;package-foo&gt;</var> ...
+ Unpacking <var>&lt;package-name&gt;</var> (from <var>&lt;package-foo&gt;</var>) ...
- dpkg: error processing <var>&lt;package-name-for-foo&gt;</var> (--unpack):
+ dpkg: error processing <var>&lt;package-name-for-foo&gt;</var> (--install):
   trying to overwrite `<var>&lt;some-file-name&gt;</var>',
   which is also in package <var>&lt;package-bar&gt;</var>
+ dpkg-deb: subprocess paste killed by signal (Broken pipe)
+  Errors were encountered while processing:
+  <var>&lt;package-foo&gt;</var>
            </example></p>
            <p>You can try to solve a file conflict by forcibly removing the
-Line 1005 
 dpkg: error processing <var>&lt;package-
+Line 1478 
 dpkg: error processing <var>&lt;package-
            series kernel, as 2.4 is no longer supported in &releasename;.
            If you are currently using a kernel from the 2.2 series, you
            must upgrade to (at least) the 2.4 series, preferably to a 2.6 series
-           kernel prior to upgrading your packages.
+           kernel, prior to upgrading your packages.
- <!-- TODO: incoporate this part in this section -->
+ <!-- TODO: incorporate this part in this section -->
            Some general issues associated with an upgrade to 2.6 are documented
            in <ref id="upgrade-to-2.6">.</p>
  ]]>
+         <sect1><heading>Installing the kernel metapackage</heading>
+           <p>When you dist-upgrade from &oldreleasename; to &releasename;,
+           it is strongly recommended that you install a new
+           linux-image-2.6-* metapackage.
+           This package may be installed automatically by the dist-upgrade
+           process. You can verify this by running:
+ <!-- NOTE (jfs): Users using apt/aptitude might not have their available file
+      updated so '^ii' is really unnecessary, maybe dpkg -l 'linux-image*' would be
+      better here? -->
+           <example>
+ # dpkg -l "linux-image*" | grep ^ii
+           </example></p>
+           <p>If you do not see any output, then you will need to install a
+           new linux-image package by hand. To see a list of available
+           linux-image-2.6 metapackages, run:
+           <example>
+ # apt-cache search linux-image-2.6- | grep -v transition
+           </example></p>
+           <p>If you are unsure about which package to select, run
+           <tt>uname -r</tt> and look for a package with a similar name.
+           For example, if you see '2.4.27-3-686', it is recommended that you
+           install <package/linux-image-2.6-686/.
+           You may also use <prgn>apt-cache</prgn> to see a long description of each
+           package in order to help choose the best one available.
+           For example:
+           <example>
+ # apt-cache show linux-image-2.6-686
+           </example></p>
+          <p>You should then use <tt/aptitude install/ 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.</p>
+          <p>For the more adventurous there is an easy way to compile your
+          own custom kernel on &debian;. Install the
+          <package>kernel-package</package> tool and read the documentation
+          in <file>/usr/share/doc/kernel-package</file>.</p>
+         </sect1>
+         <sect1 id="upgrade-from-2.6"><heading>Upgrading from a 2.6 kernel</heading>
+         <p>If you are currently running a 2.6 series kernel from
+         &oldreleasename; this upgrade will take place automatically after you do a full upgrade
+         of the system packages (as described in <ref id="upgradingpackages">).
+         </p>
+         <p>Take into account that the <prgn/udev/ version in &releasename; does
+         not support kernel versions earlier than 2.6.15 (which includes
+         &oldreleasename; 2.6.8 kernels). Conversely the <prgn/udev/ version in
+         &oldreleasename; will not work properly with the latest kernels.
+         As a consequence, the previous kernel package will probably not boot
+         properly after this upgrade. Similarly, there is a time window through
+         the upgrade in which <prgn/udev/ has been upgraded but not the
+         latest kernel. If the system were to be rebooted at this point,
+         in the middle of the upgrade, it might not be bootable.</p>
+ <!-- JFS: Bug #413458, #413311, aka coreutils dependency
+      not mentioned - fixed in 2.6.18.dfsg.1-12, entered testing already -->
+         <p>Consequently, you might want to upgrade to the latest kernel
+         before doing the full upgrade. Before you can upgrade to the 2.6
+         series kernel available in &releasename; you will have to
+         upgrade to the latest version of <package/initrd-tools/.
+         To upgrade the kernel before the upgrade, take
+         all the steps up to and including the steps related to the a minimal
+         upgrade of the system, as described in <ref id="minimal_upgrade">.
+         Once <package/initrd-tools/ have been upgraded after those steps
+         you can then do the following (changing the kernel package name to the one most
+         suited to your system by substituting <em>&lt;flavor&gt;</em>):
+         <example>
+ # aptitude install linux-image-2.6-&lt;flavor&gt;
+         </example>
+         </p>
+         <p>This step will also update <package/libc6/, install <prgn/udev/, and
+         remove <package/base-config/ and <package/hotplug/.</p>
+         <p>You can also take this step if you are using your own custom
+         kernel and want to use the kernel available in &releasename;.
+         If your kernel version is not supported by <prgn/udev/ then
+         it is recommended you upgrade after the minimal upgrade.
+         If your version is supported by <prgn/udev/ you can safely wait
+         until after the full system upgrade.</p>
+ <!--
+          <p><em>TRY</em>: In aptitude, upgrade only 'required' 'important'
+          'standard' packages limit by pressing 'l' and input
+          !~v(~pextra|~poptional) keep with : for hold this time upgrade by
+          pressing 'U" and 'g'  (untested but ...) (You can do this in much
+          finer steps.)
+ -->
+         </sect1>
+         <sect1 id="upgrade-from-2.4"><heading>Upgrading from a 2.4 kernel</heading>
+         <p>If you have a 2.4 kernel installed, and your system relies on
+         <package/hotplug/ for its hardware detection you should first upgrade
+         to a 2.6 series kernel from &releasename; before attempting the upgrade. Make
+         sure that the 2.6 series kernel boots your system and all your hardware is
+         properly detected before you perform the upgrade. The <package/hotplug/ package
+         is removed from the system (in favor of <package/udev/) when you do a full system
+         upgrade. If you do not do the kernel upgrade before this your system might
+         not boot up properly from this point on. Once you have done an upgrade
+         to a the 2.6 series kernel in &releasename; you can do a kernel upgrade
+         as described in <ref id="upgrade-from-2.6">.</p>
+         <p>If your system does not rely on <package/hotplug/<footnote>You can
+         have the kernel modules needed by your system loaded statically through proper configuration
+         of <file>/etc/modules</file></footnote> you can delay the kernel upgrade
+         to after you have done a full system upgrade, as described in <ref
+         id="upgrading_other">. Once your system has been upgraded
+         you can then do the following (changing the kernel package name to the one most
+         suited to your system by substituting <em>&lt;flavor&gt;</em>):
+         <example>
+ # aptitude install linux-image-2.6-&lt;flavor&gt;
+         </example>
+         </p>
+         </sect1>
          <sect1><heading>initrd-tools deprecated</heading>
            <p><package/initrd-tools/ is no longer supported and has been
            superseded by <package/initramfs-tools/ and <package/yaird/.
-Line 1034 
 dpkg: error processing <var>&lt;package-
+Line 1629 
 dpkg: error processing <var>&lt;package-
            manually before upgrading to an &releasename; kernel.</p>
            <p>If you see the string 'devfs' in <file>/proc/mounts</file>,
-           you are likely using <prgn>devfs</prgn>.
+           you are most likely using <prgn>devfs</prgn>.
-           Any config files that reference devfs style names will need to be
+           Any config files that reference <prgn>devfs</prgn> style names will need to be
-           adjusted to use udev style names. Files that are most likely to
+           adjusted to use <prgn>udev</prgn> style names. Files that are most likely to
-           refer to devfs style device names include <file>/etc/fstab</file>,
+           refer to <prgn>devfs</prgn> style device names are <file>/etc/fstab</file>,
            <file>/etc/lilo.conf</file>, <file>/boot/grub/menu.lst</file>, etc.</p>
            <p>More information about potential issues is available in bug report
-Line 1045 
 dpkg: error processing <var>&lt;package-
+Line 1640 
 dpkg: error processing <var>&lt;package-
          </sect1>
  <![ %i386-amd64-ia64 [
-         <sect1><heading>Standard kernels contain SMP abilities</heading>
+         <sect1><heading>Standard kernels have SMP abilities</heading>
-           <p>Multiprocessor systems no longer require a *-smp flavour of the
+           <p>Multiprocessor systems no longer require a *-smp flavor of the
-           Linux kernel. For &arch-title; linux-image packages without the -smp
+           Linux kernel. For &arch-title;, linux-image packages without the -smp
            suffix support both uniprocessor and multiprocessor systems.</p>
          </sect1>
  ]]>
  <![ %i386 [
-         <sect1><heading>386 kernel flavour deprecated</heading>
+         <sect1><heading>386 kernel flavor deprecated</heading>
-           <p>Support for the 80386 sub-archicture for &arch-title; has been dropped
+           <p>Support for the 80386 sub-architecture for &arch-title; has been dropped
            in &releasename;.  The 386 kernel flavor is no longer supported and has been
-           replaced by the new 486 flavour.</p>
+           replaced by the new 486 flavor.</p>
          </sect1>
  ]]>
-         <sect1><heading>Device enumeration reordering</heading>
+         <sect1 id="device-reorder"><heading>Device enumeration reordering</heading>
            <p>&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
+           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
-Line 1077 
 dpkg: error processing <var>&lt;package-
+Line 1672 
 dpkg: error processing <var>&lt;package-
            specific names at boot time.
  <!-- TODO: add ifupdown-scripts-zg2 as well here? -->
            See <manref name="ifrename" section="8"> and <manref name="iftab"
-           section="5"> for more information.</p>
+           section="5"> for more information. You can also avoid this by
+           using <prgn>udev</prgn> rules, more specifically, through the
+           definitions at
+           <file>/etc/udev/rules.d/z25_persistent-net.rules</file><footnote>
+           The rules there are automatically generated to have persistent names for network
+           interfaces.</footnote>. Both alternatives (<prgn>ifrename</prgn>
+           and <prgn>udev</prgn>) should not be used at the same time.
+           </p>
  <!-- TODO:
            *** maks: please review the initramfs stuff for accuracy - I'm going
-Line 1120 
 dpkg: error processing <var>&lt;package-
+Line 1722 
 dpkg: error processing <var>&lt;package-
            console port (the connector labelled "console" on the 3-headed
            cable), this kernel upgrade will break your console!</p>
+           <p>Upon reboot, the system will show up the message "Loading
+           initrd...." but it will stop there. Notice that systems with
+           outdated firmware will show similar symptoms, although the issue is
+           related to kernel incompatibilities (see <ref
+           id="upgrade-to-2.6">).</p>
            <p>Please read the following information before upgrading.</p>
            <p><list>
-Line 1161 
 dpkg: error processing <var>&lt;package-
+Line 1769 
 dpkg: error processing <var>&lt;package-
          </sect1>
  ]]>
-         <sect1><heading>Upgrading the kernel</heading>
+         </sect>
-           <p>When you dist-upgrade from &oldreleasename; to &releasename;,
-           it is strongly recommended that you install a new
-           linux-image-2.6-* metapackage.
-           This package may be installed automatically by the dist-upgrade
-           process. You can verify this by running:
-           <example>
- # dpkg -l | grep '^ii  linux-image'
-           </example></p>
-           <p>If you do not see any output, then you will need to install a
+         <sect id="nownownow"><heading>Things to do before rebooting</heading>
-           new linux-image package by hand. To see a list of available
-           linux-image-2.6 metapackages, run:
-           <example>
- # apt-cache search linux-image-2.6- | grep -v transition
-           </example></p>
-           <p>If you are unsure about which package to select, run
+           <p>When <tt>aptitude dist-upgrade</tt> has finished, the
-           <tt>uname -r</tt> and look for a package with a similar name.
+           "formal" upgrade is complete, but there are some other things
-           For example, if you see '2.4.27-3-686', it is recommended that you
+           that should be taken care of <em/before/ the next reboot.</p>
-           install <package/linux-image-2.6-686/.
-           You may also use <prgn>apt-cache</prgn> to see a long description of each
+ <![ %i386-amd64 [
-           package in order to help choose the best one available.
+         <sect1 id="rerunlilo"><heading>Rerun lilo</heading>
-           For example:
+           <p>If you are using <package/lilo/ as your bootloader (it is the
+           default bootloader for some installations of &oldreleasename;) it is strongly recommended
+           that you rerun lilo after the upgrade:
            <example>
- # apt-cache show linux-image-2.6-686
+ # /sbin/lilo
            </example></p>
-          <p>You should then use <tt/aptitude install/ to install it. Once
+           <p>Notice this is needed even if you did not upgrade your system's kernel, as
-          this new kernel is installed you should reboot at the next available
+           lilo's second stage will change due to the package upgrade.</p>
-          opportunity to get the benefit.</p>
-          <p>For the more adventurous there is an easy way to compile your
-          own custom kernel on &debian;. Install the
-          <package>kernel-package</package> tool and read the documentation
-          in <file>/usr/share/doc/kernel-package</file>.</p>
-         </sect1>
+           <p>Also, review the contents of your <file>/etc/kernel-img.conf</file> and
-         </sect>
+           make sure that you have <em>do_bootloader = Yes</em> in it. That way the
+           bootloader will always be rerun after a kernel upgrade.
+           </p>
-         <sect id="nownownow"><heading>Things to do before rebooting</heading>
+           <p>If you encounter any issues when running <prgn/lilo/ review the
+           symbolic links in <file>/</file> to <file>vmlinuz</file> and
+           <file>initrd</file>, as well as the contents of your
+           <file>/etc/lilo.conf</file> for discrepancies.</p>
+           <p>If you forgot to rerun <prgn/lilo/ before the reboot or the system
+           is accidentally rebooted before you could do this manually, your
+           system might fail to boot. Instead of the lilo prompt, you will only
+           see <em/LI/ when booting the system<footnote>For more information on
+           <prgn/lilo/'s boot error codes please see <url
+           id="http://tldp.org/HOWTO/Bootdisk-HOWTO/a1483.html" name="The Linux
+           Bootdisk HOWTO">.</footnote>. In order to
+           recover from this you will have to start up a media installation disk
+           in <em/rescue/ mode. For
+           more information on how to do this please review the <url
+           id="http://wiki.debian.org/DebianInstaller/FAQ" name="DebianInstaller
+           FAQ">.</p>
-           <p>When <tt>aptitude dist-upgrade</tt> has finished, the
+         </sect1>
-           "formal" upgrade is complete, but there are some other things
+ ]]>
-           that should be taken care of <em/before/ the next reboot.</p>
          <sect1 id="mdadm"><heading>Upgrading mdadm</heading>
-Line 1221 
 dpkg: error processing <var>&lt;package-
+Line 1830 
 dpkg: error processing <var>&lt;package-
          </sect1>
          </sect>
+         <sect id="for_next"><heading>Preparing for the next release</heading>
+           <p>After the upgrade there are several things you can do
+           to prepare for the next release.</p>
+           <p><list>
+           <item><p>If using <prgn/grub/, edit <file>/etc/kernel-img.conf</file>
+           and adjust the location of the <prgn/update-grub/ program changing
+           <file>/sbin/update-grub</file> to <file>/usr/sbin/update-grub</file>.</p>
+ <!-- TODO: (jfs) Is this needed? aptitude-0.4.4-1 "fixed" this, see #386307 -->
+           <item><p>Unmark the 2.6 kernel image installed as not an automatic
+           package, so that <prgn/aptitude/ never considers it unused:
+ <example>
+ # aptitude unmarkauto linux-image-2.6-&lt;flavor&gt;
+ </example>
+ </p>
+         <item><p>Remove &oldreleasename;'s kernel metapackages by running:
+ <example>
+ # aptitude purge kernel-image-2.6-&lt;flavor&gt;
+ </example>
+ </p>
+         <item><p>Move any kernel configuration values at
+         <file>/etc/network/options</file> to <file>/etc/sysctl.conf</file>.</p>
+         <item><p>Remove obsolete and unused packages as described in <ref
+         id="obsolete">.  You should review which configuration files they use
+         and consider purging the packages to remove their configuration files</p>
+         </list></p>
+         </sect>
          <sect id="obsolete"><heading>Obsolete packages</heading>
  <!-- JFS: Providing a full listing might be useful, especially if we can
-Line 1245 
 potato to woody RN -->
+Line 1889 
 potato to woody RN -->
           no longer a Debian Developer interested in maintaining the packages;
           the functionality they provide has been superseded by different
           software (or a new version); or they are no longer considered
-          suitable for &releasename; due to bugs in them. In the later case,
+          suitable for &releasename; due to bugs in them. In the latter case,
           packages might still be present in the "unstable" distribution.</p>
           <p>Detecting which packages in an updated system are "obsolete" is
-Line 1327 
 didn't belong to them... -->
+Line 1971 
 didn't belong to them... -->
            <sect1 id="window-scaling"><heading>Certain networking site cannot be reached by TCP</heading>
            <p>
-           Since 2.6.17, Linux uses TCP window scaling which is specified in RFC 1323 in
+           Since 2.6.17, Linux aggressively uses TCP window scaling which is specified in RFC 1323.
-           an aggressive way. Some servers have a broken behaviour, and announce wrong
+           Some servers have a broken behavior, and announce wrong
            window sizes for themselves. Please see the bugs
            <url id="http://bugs.debian.org/381262" name="#381262"> and
            <url id="http://bugs.debian.org/395066" name="#395066">
-Line 1365 
 didn't belong to them... -->
+Line 2009 
 didn't belong to them... -->
            <p>
            Certain models of HP laptops have an ACPI BIOS that is incompatible with the
            Linux 2.6.18 kernel shipped in &releasename;, which would prevent the fans from
-           spinning up leading to unnecessary heat stress.  The kernel therefore disables
+           spinning up leading to unnecessary heat stress. Also, fans might not work after
-           ACPI support internally when it detects certain ACPI BIOS versions.  Models
+           the system is suspended. The kernel therefore disables ACPI support
-           known to be affected by this change include the HP nx6125, nx6325, and nc6120
+           internally when it detects certain ACPI BIOS versions.  Models known
-           models.
+           to be affected by this change include the HP nx6125, nx6120, nx6325,
+           nc6120 and nc6000 models.
            </p>
            <p>
            Users who require ACPI support on these systems may install a Linux 2.6.19 or
-           later kernel.  Please see bug
+           later kernel.  Please see Debian bug
-           <url id="http://bugs.debian.org/404143" name="#404143">
+           <url id="http://bugs.debian.org/404143" name="#404143"> and
+           <url id="http://bugs.debian.org/400488" name="#400488">,
+           and Linux Kernel's bugs
+           <url id="http://bugzilla.kernel.org/show_bug.cgi?id=5534" name="#5534">
+           and
+           <url id="http://bugzilla.kernel.org/show_bug.cgi?id=7122" name="#7122">
            for additional information.
            </p>
            </sect1>
-Line 1403 
 didn't belong to them... -->
+Line 2053 
 didn't belong to them... -->
            <p>Debian attempts to avoid changing upstream packages, therefore
            any changes in the upstream package will be present in the version in
-           &debian;. This can mean that program behaviour may change between
+           &debian;. This can mean that program behavior may change between
            releases of &debian;. </p>
            <p><em>No changes yet reported.</em></p>
-Line 1422 
 didn't belong to them... -->
+Line 2072 
 didn't belong to them... -->
            lightly. This section aims to make you aware of some of the issues
            you may face.</p>
+ <!-- TODO - needs to be changed for etch, not TRUE -->
            <p>You are therefore strongly advised not to upgrade to a 2.6 kernel
            as part of the upgrade from &oldreleasename; to &releasename;.
            Instead, you should first make sure your system works correctly
-Line 1446 
 didn't belong to them... -->
+Line 2097 
 didn't belong to them... -->
            module names may have changed. If this happens you will have to update
            this file with the new module names.</p>
+ <!-- JFS: Can't this device name change even for some other disk controllers? I've found
+      references in debian-user posts talking about some strange chipsets and BIOS
+      which are seen in sarge' 2.4 as hda and in etch's 2.6 as hdf... -->
  <![ %i386-amd64 [
            <p>For some SATA disk controllers, the device assigned to a drive and
            its partitions may change from <file>/dev/hdX</file> to
            <file>/dev/sdX</file>. If this happens, you will have to modify your
            <file>/etc/fstab</file> and bootloader configuration accordingly.
            Unless these changes are made correctly, your system may not boot
-           correctly.</p>
+           correctly<footnote>It will boot the kernel but will fail when trying
+           to mount the root filesystem and will abort with an error <em>waiting for root filesystem</em>
+           followed by <em>unable to mount /dev/hdX ..not found</em>.
+           You can use the <prgn/initramfs/ shell to fix this issue, after you
+           identify the names newly assigned devices in the kernel boot messages or by reviewing
+           the contents of <file>/dev/disk</file>.</footnote>.</p>
+ ]]>
+ <!-- Bug: #416720 -->
+ <![ %ia64 [
+          <p>HP Itanium systems running older firmware are incompatible with the
+.6 kernel in &releasename;. That means you should upgrade your
+             system to the latest firmware before upgrading your kernel. It is
+             recommended you do this before the system upgrade, as if you are
+             already running a 2.6 kernel you will automatically retrieve the
+             latest kernel when upgrading the rest of the system (see <ref
+             id="upgrading_other">). Failing to do this will result in an system
+             that does not boot,
+          </p>
  ]]>
            <p>Once you have installed your 2.6 kernel, but before you reboot,
            make sure you have a recovery method. First, make sure that the
            bootloader configuration has entries for both the new kernel and
            the old, working 2.4 kernel. You should also ensure you have a "rescue"
-           floppy or cdrom to hand, in case misconfiguration of the bootloader
+           floppy or CD-ROM to hand, in case misconfiguration of the bootloader
            prevents you booting the old kernel.</p>
  <![ %not-s390 [
-Line 1481 
 didn't belong to them... -->
+Line 2153 
 didn't belong to them... -->
            <p>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 <tt>dpkg-reconfigure xserver-xfree86</tt> or by
+           either by running <tt>dpkg-reconfigure xserver-xorg</tt> or by
-           editing <file>/etc/X11/XF86Config-4</file> directly. Don't forget
+           editing <file>/etc/X11/xorg.conf</file> directly. Don't forget
            to read the documentation referred to in <ref id="nownownow">.</p>
  <![ %i386 [
-Line 1547 
 didn't belong to them... -->
+Line 2219 
 didn't belong to them... -->
          <p>As <package/udev/ is automatically installed as a dependency of the new
          default initrd generator used with the 2.6 kernels
          (<package/initramfs-tools/), upgrading to a 2.6 kernel will normally result
-         in <package/udev/ being activated.</p>
+         in <package/udev/ being activated. You can avoid installing <package/udev/
+         if you install an alternate initrd generator, such as <package/yaird/.
+         <package/initramfs-tools/ is the recommended initrd generator.</p>
          <p>Although <package/udev/ has been tested extensively, you may experience
          minor problems with some devices that will need to be fixed. The most
-Line 1568 
 didn't belong to them... -->
+Line 2242 
 didn't belong to them... -->
          <p>The transition to X.Org involves some structural changes. In case
          all installed packages are from Debian and also included in &releasename;,
          the upgrade should work without problems.
-         Experience has however shown there are a few changes to be aware of as
+         However, experience has shown that there are a few changes to be aware
-         they can potentially cause issues during the upgrade.</p>
+         of, as they can potentially cause issues during the upgrade.</p>
          <p>The most important change is that <file>/usr/X11R6/bin</file> has
          been dropped and only remains as a symlink to <file>/usr/bin</file>.
-         This means this directory has to be empty at the time the new packages
+         This means the directory has to be empty at the time the new packages
          are installed. The new packages conflict with most packages that used
          <file>/usr/X11R6/bin</file>,
          but in some cases manual intervention may be needed.
-         Please remember to not run upgrades within an X session.</p>
+         Please remember to not run the distribution upgrade from within an
+         X session.</p>
          <p>In case the upgrade aborts during X.Org installation, you should
          check if any files are still left in <file>/usr/X11R6/bin</file>.
-Line 1595 
 didn't belong to them... -->
+Line 2270 
 didn't belong to them... -->
        <sect id="exim"> <heading>Upgrading from exim to exim4</heading>
        <p>One of the packages that has been obsoleted by the &releasename;
-       release is the Mail Transfer Agent (MTA) exim, which has been replaced
+       release is the Mail Transfer Agent (MTA) <package/exim/, which has been replaced
-       by the completely new package exim4.</p>
+       by the completely new package <package/exim4/.</p>
-       <p>exim (version 3.xx) has been unmaintained upstream for years, and
+       <p><prgn/exim/ (version 3.xx) has been unmaintained upstream for years, and
        Debian has dropped support for that version as well. If you are still using
-       exim 3.xx, please upgrade your exim installation to exim4 manually.
+       <prgn/exim/ 3.xx, please upgrade your <package/exim/ installation to <package/exim4/ manually.
-       Since exim4 is already part of &oldreleasename;, you can choose to do the
+       Since <package/exim4/ is already part of &oldreleasename;, you can choose to do the
        upgrade on your &oldreleasename; system before the upgrade to &releasename;,
        or after the &releasename; upgrade at your convenience. Just remember that
-       your old exim package is not going to be upgraded and that it won't get
+       your old <package/exim/ package is not going to be upgraded and that it won't get
-       security support after support for &oldreleasename; will be discontinued.</p>
+       security support after support for &oldreleasename; has been discontinued.</p>
-       <p>The exim4 packages in Debian are extensively documented. The package's
+       <p>The <package/exim4/ packages in Debian are extensively documented. The package's
        home page is <url id="http://wiki.debian.org/PkgExim4"> on the Debian Wiki, and
        the README file can be found at
        <url id="http://pkg-exim4.alioth.debian.org/README/README.Debian.html"> and
-Line 1615 
 didn't belong to them... -->
+Line 2290 
 didn't belong to them... -->
        <p>The README file has a chapter about Packaging, which explains the
        different package variations we offer, and it has a chapter about
-       Updating from Exim 3, which will help you in doing the actual
+       Updating from <prgn/Exim/ 3, which will help you in doing the actual
        transition.</p>
  <!-- FIXME: update with decisions of (S)RMs might be needed -->
        </sect>
-Line 1659 
 didn't belong to them... -->
+Line 2334 
 didn't belong to them... -->
          <file>/usr/share/doc/php5</file>).</p>
        </sect>
+ <!-- JFS: Bug #400311 -->
        <sect id="mozilla-security"> <heading>Security status of Mozilla products</heading>
-         <p>The Mozilla programs are important tools for many users.
+         <p>The Mozilla programs <package>firefox</package> and <package>thunderbird</package>
+         (rebranded in Debian to <package>iceweasel</package> and <package>icedove</package>, 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 not to ship
+         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 lifetime of &releasename; the
+         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.
-Line 1672 
 didn't belong to them... -->
+Line 2350 
 didn't belong to them... -->
          alternatives available in Debian if the absence of security support would
          pose a problem for you.</p>
        </sect>
+ <!-- JFS: Bug #400838 -->
+       <sect id="kde-desktop-changes"> <heading>KDE desktop</heading>
+         <p>KDE media handling has changed in the version available in
+         &releasename; from using <file>device:/</file> to <file>media:/</file>.
+         Some user configuration files might have stored <file>device:/</file>
+         links in them which should be adapted. Notably,
+         <file>~/.kde/share/apps/konqsidebartng/virtual_folders/services</file>
+         contains this reference and can be safely deleted as it will not be
+         created when setting up new users.
+         <p>There have been many changes in the KDE desktop environment from
+         the version shipped in &oldreleasename; to the version in
+         &releasename;, you can find more information in the <url
+         id="http://www.kde.org/announcements/announce-3.5.php" name="KDE
+.5 Release Notes">.</p>
+       </sect>
+ <!-- JFS: Bug #387921 -->
+       <sect id="gnome-desktop-changes"> <heading>GNOME desktop changes and support</heading>
+         <p>If you used the GNOME desktop in &oldreleasename; you will not benefit
+         of 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.</p>
+         <p>If you have not heavily invested in configuring your GNOME desktop
+         you might want to move the the <file>.gconf</file> directory in user's
+         home directories to a different name (such as <file>.gconf.old</file>)
+         so that it gets recreated, with the default configuration for
+         &releasename;, upon starting a new session.</p>
+         <p>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.</p>
+         <p>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 <url
+         id="http://www.gnome.org/start/2.14/notes/en/" name="GNOME
+.14 Release Notes">.</p>
+       </sect>
+ <!-- FJP: Bug #398887 -->
+       <sect id="default-editor"> <heading>Default editor</heading>
+         <p>If you were using <prgn/vim/ as your default editor, this may
+         be changed to <prgn/nano/ during the upgrade.</p>
+         <p>Administrators who wish to change the default editor for all users
+         will have to update the alternatives system using:
+           <example>
+ # update-alternatives --config editor
+           </example>
+         </p>
+         <p>Users wishing to change the default editor can define the
+         environment variable <em>EDITOR</em> by introducing the following lines
+         in their own profiles:
+           <example>
+ EDITOR=vi
+ export EDITOR
+ alias editor=$EDITOR
+           </example>
+         </p>
+       </sect>
        </chapt>
        <chapt id="moreinfo">
-Line 1682 
 didn't belong to them... -->
+Line 2429 
 didn't belong to them... -->
          <p>Beyond these release notes and the installation guide, further
          documentation on &debian; is available from the Debian
          Documentation Project (DDP), whose goal is to create high quality
-         documentation for Debian users and developers. Documentation
+         documentation for Debian users and developers. Documentation,
          including the Debian Reference, Debian New Maintainers Guide, and Debian
          FAQ are available, and many more. For full details of the existing resources
          see the <url id="&url-ddp;" name="DDP website">.</p>
-Line 1714 
 didn't belong to them... -->
+Line 2461 
 didn't belong to them... -->
        </sect1>
  <!-- TODO: Changed to OFTC -->
        <sect1 id="irc">
          <heading>Internet Relay Chat</heading>
          <p>Debian has an IRC channel dedicated to the support and aid of
          Debian users located on the OFTC IRC network which exists to
          provide interactive services to peer-directed project communities.
-         To access the channel, point your favourite IRC client at
+         To access the channel, point your favorite IRC client at
          &debian-irc-server; and join #debian.</p>
          <p>Please follow the channel guidelines, respecting other users
-Line 1727 
 didn't belong to them... -->
+Line 2474 
 didn't belong to them... -->
          id="&url-irc-host;" name="website">.</p>
        </sect1>
        </sect>
        <sect id="bugs">
          <heading>Reporting bugs</heading>
-Line 1742 
 didn't belong to them... -->
+Line 2489 
 didn't belong to them... -->
          <p>If you find a bug in the distribution or in packaged software
          that is part of it, please report it so that it can be properly
-         fixed for next releases. Reporting bugs requires a valid email
+         fixed for future releases. Reporting bugs requires a valid email
-         address, we ask for this so that we can trace bugs and developers
+         address. We ask for this so that we can trace bugs and developers
-         can get in contact with submitters should they need more
+         can get in contact with submitters should additional information be
-         information.</p>
+         needed.</p>
          <p>You can submit a bug report using the program
          <package>reportbug</package> or manually using email.
          You can read more about the Bug Tracking System and how to use it by
          reading the reference cards (available at
          <file>/usr/share/doc/debian</file> if you have
-Line 1763 
 didn't belong to them... -->
+Line 2510 
 didn't belong to them... -->
          <p>You do not need to be an expert to contribute to Debian. By
          assisting users with problems on the various user support <url
          id="&url-debian-list-archives;" name="lists"> you are contributing to
-         the community. Identifying (and importantly solving) problems
+         the community. Identifying (and also solving) problems
          related to the development of the distribution by participating on
          the development <url id="&url-debian-list-archives;" name="lists"> is
          also extremely helpful. To maintain Debian's high quality
-         distribution <url id="&url-bts;" name="submit bugs">
+         distribution, <url id="&url-bts;" name="submit bugs">
          and help developers track them down and fix them. If you have a way
          with words then you may want to contribute more actively by helping
          to write <url id="&url-ddp;"
-Line 1809 
 didn't belong to them... -->
+Line 2556 
 didn't belong to them... -->
            first need to make sure your package list still contains
            &oldreleasename; packages as explained in <ref id="old-sources">.</p>
+           <p>You should upgrade to the latest &oldreleasename; point release:
+           r5, published February 2007.</p>
         </sect>
         <sect id="old-sources">

 Legend:



Removed from v.4162
 


changed lines


 
Added in v.4284
 Legend:



Removed from v.4162
 


changed lines


 
Added in v.4284
-Removed from v.4162
+Added in v.4284

	ViewVC Help
Powered by ViewVC 1.1.5