/[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 3896 by fjp,
Wed Nov  1 03:59:52 2006 UTC
+revision 4226 by jfs,
Tue Mar 27 00:34:22 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.73 2006-11-01 03:59:52 fjp Exp $">
+   <!entity docid "$Id: release-notes.en.sgml,v 1.170 2007-03-27 00:34:22 jfs Exp $">
  ]>
  <!-- Be careful with automatic reformatting. Please note that the indentation
 Line 10
  <debiandoc>
    <book>
    <titlepag>
-     <title>Release Notes for &debian; &release; (`&releasename'), &arch-title;</title>
+     <title>Release Notes for &debian; &release; ("&releasename;"), &arch-title;</title>
        <author>
          <name>Josip Rodin, Bob Hilliard, Adam Di Carlo, Anne Bezemer, Rob
-         Bradford (current), Frans Pop (current)</name><email></email>
+         Bradford (current), Frans Pop (current), Andreas Barth (current)</name><email></email>
        </author>
        <author>
          <name></name><email>debian-doc@lists.debian.org</email>
 Line 21
        <version>&docid;</version>
      </titlepag>
      <toc detail="sect1">
-       <chapt id="about"><heading>What's new in the Release Notes</heading>
+       <chapt id="about"><heading>Introduction</heading>
-         <p>[The most recent version of this document is always available at
+         <p>The primary goals of these Release Notes are to inform users
-         <url id="&url-release-notes;">. If your version is more than a month
+         of major changes in this release of the &debian; distribution, to
-         old, you might wish to download the latest version.]</p>
+         provide information on how to upgrade safely from the previous
+         release to the current release and finally to inform users of known potential
+         issues users could encounter when upgrading to or using the
+         &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 <url
+         id="&url-release-notes;">. If the version you are reading is more than a
+         month old<footnote>On front page's 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 105
+Line 170
          <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
+      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
-            of 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 XOrg, which includes support for a greater range of
+            release of X.Org, which includes support for a greater range of
             hardware and better autodetection. This allows the use of Compiz,
             which is one of the first compositing window managers for the X
-            Window System allowing taking full advantage of hardware
+            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>
-            <p>The &releasename; version of <prgn/aptitude/ is the preferred
+            <item>name servers: Bind 9.3, maradns 1.2.</item>
-            program for package management from console. It has proven to be
-            better at dependency resolution than <prgn/apt-get/.
+            <item>directory server: OpenLDAP 2.3</item>
-            <prgn/aptitude/ supports most command line operations of
-            <prgn/apt-get/. If you are still using <prgn/dselect/, you should
+ <!-- FIXME (JFS): List other server software? RADIUS? Streaming ? -->
-            switch to <package/aptitude/ as the official frontend for package
+            </list></p>
-            management.</p>
+            </list></p>
+            <p><prgn/aptitude/ is the preferred program for package management
+            from console.
+            <prgn/aptitude/ supports most command line operations of <prgn/apt-get/
+            and has proven to be better at dependency resolution than <prgn/apt-get/.
+            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
             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. Unofficial apt sources administrators 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
-            unofficial service with the release of &oldreleasename, has now
+            unofficial service with the release of &oldreleasename;, has now
-            become an official Debian service.</p>
+            become an official &debian; service.</p>
             <p>This means that it no longer has a <tt/.debian.net/ address,
             but now uses a <tt/.debian.org/ address. Please make sure to update
-Line 158
+Line 299
          </sect1>
          </sect>
-         <sect id="newinst"><heading>What's new in the installation system?</heading>
+         <sect id="inst-new"><heading>What's new in the installation system?</heading>
- <!-- FJP: Maybe a short description of available installation methods could be
-           added here: floppy, CD (netinst/business-card/full set), netboot,
-           hd-media, USB-stick. -->
          <!-- 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>
+            <p>In these Release Notes we'll only list the major changes in the
+            installer. If you are interested in an overview of the detailed
+            changes since &oldreleasename;, please check the release announcements
+            for the &releasename; beta and RC releases available from the
+            Debian Installer's <url id="&url-installer-news" name="news history">.</p>
+          <sect1 id="inst-changes"><heading>Major changes</heading>
+            <p><taglist>
+              <tag>No reboot during the installation</tag>
+              <item><p>The installation used to be split into two parts:
+              setting up the base system and making it bootable, followed
+              by a reboot and after that the execution of <prgn/base-config/
+              which would take care of things like user setup, setup of the
+              package management system and installation of additional
+              packages (using tasksel).</p>
+              <p>For &releasename; the second stage has been integrated into
+              Debian Installer itself. This has a number of advantages,
+              including increased security and the fact that after the reboot
+              at the end of the installation the new system should already have
+              the correct timezone and, if you installed the Desktop environment,
+              will at once start the graphical user interface.</p></item>
+              <tag>UTF-8 encoding default for new systems</tag>
+              <item><p>The installer will set up systems to use UTF-8 encoding
+              rather than the old language-specific encodings (like ISO-8859-1,
+              EUC-JP or KOI-8).</p></item>
+              <tag>More flexible partitioning</tag>
+              <item><p>It is now possible to set up filesystems on an LVM volume
+              using guided partitioning.</p>
+              <p>The installer is also able to set up encrypted filesystems.
+              Using manual partitioning you have the choice between <tt/dm-crypt/
+              and <tt/loop-aes/, using a passphrase or a random key, and you can
+              tune various other options. Using guided partitioning, the installer
+              will create an encrypted LVM partition that contains any other
+              filesystems (except <file>/boot</file>) as logical volumes.</p></item>
+ <![ %i386-amd64 [
+              <tag>Graphical user interface</tag>
+              <item><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>
+              <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>
+ ]]>
+              <tag>Rescue mode</tag>
+              <item><p>You can use the installer to solve problems with your
+              system, for example when it refuses to boot. The first steps will
+              be just like a regular installation, but the installer will not
+              start the partitioner. Instead it will offer you a menu of rescue
+              options.</p>
+              <p>Activate the rescue mode by booting the installer with
+              <tt/rescue/, or by adding a boot parameter
+              <tt>rescue/enable=true</tt>.</p></item>
+              <tag>Using sudo instead of root account</tag>
+              <item><p>During expert installations you can choose to not
+              set up the root account (it will be locked), but instead set
+              up <prgn/sudo/ so that the first user can use that for
+              system administration.</p></item>
+              <tag>Cryptographic verification of downloaded packages</tag>
+              <item><p>Packages downloaded with the installer are
+              now cryptographically checked using <prgn/secure apt/
+              making it more difficult to compromise a system being
+              installed over the network.</p></item>
+ <!-- FIXME: Bug Manoj for a link to documentation on enabling SELinux -->
+              <tag>SELinux</tag>
+              <item><p>The packages needed for SELinux support have been
+              promoted to priority "standard". This means that they will be
+              installed by default if you select the Standard task during
+              installation. However, SELinux support is not enabled by default.
+              If you want to secure your system using SELinux, you will need
+              to enable it manually after the installation.</p></item>
+              <tag>Simplified mail configuration</tag>
+              <item><p>The installation system setups 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>
+ <![ %not-s390 [
+              <tag>New languages</tag>
+              <item><p>Thanks to the huge efforts of translators, Debian can
+              now be installed in 47 languages using the text-based
+              installation user interface. This is six languages more
+              than in &oldreleasename;. Languages added in this release include
+              Belarusian, Esperanto, Estonian, Kurdish, Macedonian,
+              Tagalog, Vietnamese and Wolof.
+              Languages dropped in this relase due to lack of translation
+              updates include Persian and Welsh.
+ <![ %g-i [
+              If the graphical user interface is used, an additional eleven
+              languages are supported. These languages can only be selected
+              using this installer as their character sets cannot be presented
+              in a non-graphical environment. The new languages are:
+              Bengali, Dzongkha, Gujarati, Hindi, Georgian, Khmer, Malayalam,
+              Nepali, Punjabi, Tamil and Thai.
+ ]]>
+              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
+       necessar for that language (dictionaries, documentation, fonts...) both
+       in standard and desktop enviroments. Configuration that is no longer
+       handled automatically include the papersize configuration and some
+       advanced keyboard settings on Xorg for some languages.</p></item>
+ ]]> <!-- not-s390 -->
+        </list></p>
+        </sect>
+            </taglist></p>
+          </sect1>
+          <sect1 id="inst-auto"><heading>Automated installation</heading>
+            <p>A lot of the changes mentioned in the previous section also
+            imply changes in the support in the installer for automated
+            installation using preconfiguration files. This means that if
+            you have existing preconfiguration files that worked with the
+            &oldreleasename; installer, you cannot expect these to work
+            with the new installer without modification.</p>
+            <p>The good news is that the <url id="&url-install-manual;"
+            name="Installation Guide"> now has a separate appendix with
+            extensive documentation on using preconfiguration.</p>
+            <p>The &releasename; installer introduces some exciting new
+            features that allow further and easier automation of installs.
+            It also adds support for advanced partitioning using RAID, LVM
+            and encrypted LVM. See the documentation for details.</p>
+          </sect1>
          </sect>
        </chapt>
- <!-- TODO: Mention default usage of UTF-8 for new installs -->
        <chapt id="installing"><heading>New installations</heading>
-         <p>The installer offers a variety of installation methods. Which methods
+         <p>The Debian Installer is the official installation system for Debian.
-         are available to install your system depends on your architecture.</p>
+         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>If you are making a new installation of Debian, you should read
+         <p>The Installation Guide is also included on the first CD/DVD of the
-         the Installation Guide, which is available on the Official CD at:
+         official Debian CD/DVD sets, at:
          <example>
  /doc/install/manual/<var>language</var>/index.html
-         </example>
+         </example></p>
-         or on the Internet from the <url id="&url-install-manual;"
+         <p>You may also want to check the <url id="&url-installer;index#errata"
-         name="&releasename; release pages">. You may also want to check the
+         name="errata"> for debian-installer for a list of knonw issues.</p>
-         <url id="&url-installer;index#errata" name="errata"> for
-         debian-installer.</p>
  <![ %alpha [
          <!-- TODO: Still true? -->
-Line 202
+Line 517
  <![ %sparc [
        <sect id="sparc_fb"><heading>Issues with framebuffer on &arch-title;</heading>
-         <!-- TODO: Still true -->
          <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 parameter <tt>debian-installer/framebuffer=true</tt>.
+         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="improves_in_etch"><heading>System improvements</heading>
+        <p>Users installing &releasename; will benefit from some improvements
+        in the &debian; operating system. Most of these improvements
+        will be carried over to upgrades from &oldreleasename; but there
+        are some changes that will only affect new installs:
+        </p>
+        <p><list>
+ <!-- Bug 301138, fixed in etch -->
+        <item>Development packages are now of <em>Optional</em> priority.
+        This includes the standard C/C++-compiler, <package>gcc</package>, as well
+        as some other software (<package>dpkg-dev</package>,
+        <package>flex</package>, or <package>make</package>) and development
+        headers (<package>libc6-dev</package>,
+        <package>linux-kernel-headers</package>).
+ <!-- TODO: Point to the bug report for the full list of packages in case
+      users want to remove them ? -->
+        This reduces the disk space needed for a standard installation.
+        </item>
+ <!-- TODO: Recommend users to remove unused desktop environments ? -->
+        <item>There are three different tasks for Desktop environments users can
+        choose from: GNOME, KDE or Xfce. An installation of the Desktop task in
+        &oldreleasename; would install both GNOME or KDE.</item>
+        <item>The default inet superdaemon 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.</item>
+        <item>The variant installed for <prgn/vi/ by default is a compact version of
+        <prgn/vim/ (<package/vim-tiny/) instead of <package/nvi/.
+        <item>The &releasename; installer sets up ext2 and ext3 filesystems so
+        that they have "directory indexes", a feature which speeds operations on
+        directories with many files. It does this by turning on the
+        <em/dir_index/ and <em/filetype/ flags when the filesystem is created.
+        Users upgrading from &oldreleasename; need to set this flags manually
+        with <prgn/tune2fs/.</item>
+ <!-- TODO: Add for lenny, link to utf8-migration-tool, which is right now not
+      available for etch -->
+        <item>The &debian; installer will setup all localized environments using
+        UTF-8 as the default encoding instead of language-specific encoding.
+        Users upgrading to &releasename; will have to switch to this encoding
+        by configuring their environment and locale definitions.</item>
+        </list></p>
+ <!-- TODO: make it conditional based on arquitecture ? -->
+       <p>Additional packages are pulled in based on the system being installed on or on the user
+       configuration. Users running the installer in a laptop system will
+       automatically get a set of packages specific for laptops, and so will
+       users configuring a localized environment. Even though these packages are
+       not pulled in when upgrading from &oldreleasename; to &releasename; they
+       are still available for users through <em>tasks</em>. Users wishing to
+       install these tasks just need to run <prgn/aptitude/ interactively and select the
+       appropiate tasks from the <em>Tasks</em> item presented in the user interface.</p>
+       <p>For more information please see the <url id="http://wiki.debian.org/Sarge2EtchUpgrade"
+       name="wiki pages"> that describe the upgrade from &oldreleasename; to &releasename;.</p>
        <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 231
+Line 609
          you will thereby help improve Debian.</p>
        </sect>
        </chapt>
-Line 252 
 release: architectures:
+Line 631 
 release: architectures:
          <sect id="backup"><heading>Preparing for the upgrade</heading>
+           <p>We suggest that before upgrading you also read the information in
+           <ref id="information">. That chapter covers potential issues not
+           directly related to the upgrade process but which could still be
+           relevant.</p>
            <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 274 
 release: architectures:
+Line 658 
 release: architectures:
            also want to inform users about this.</p>
            <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/
+           planning, although users accessing your system via an <prgn/ssh/
-           connection should notice little during the upgrade, and shold be
+           connection should notice little during the upgrade, and should be
            able to continue working. If you wish to take extra precautions, back up or
-           unmount users' partitions (<file>/home</file>) before upgrading. A
+           unmount users' partitions (<file>/home</file>) before upgrading.</p>
-           reboot will not normally be necessary, unless you plan to also
-           upgrade your kernel.</p>
+ <!-- JFS: Not true in etch
+           <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 ? -->
            <p>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>
+ <!-- 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 300 
 release: architectures:
+Line 701 
 release: architectures:
            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/.
+           This should preferable be done before starting the upgrade.
+           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>
          </sect>
          <sect id="system-status">
-Line 307 
 release: architectures:
+Line 791 
 release: architectures:
          <p>The upgrade process described in this chapter has been designed for
          upgrades from "pure" &oldreleasename; systems without 3rd party
-         packages. It may be wise  remove these packages first.</p>
+         packages. It may be wise to remove these packages first.</p>
          <p>This procedure also assumes your system has been updated to the
          latest point release of &oldreleasename;.  If you have not done this
-Line 351 
 release: architectures:
+Line 835 
 release: architectures:
            <p>It is desirable to remove any holds before upgrading. If any
            package that is essential for the upgrade is on hold, the upgrade
-           will fail.
+           will fail.</p>
-           Note that <prgn/aptitude/ uses a different method for registering
+           <p>Note that <prgn/aptitude/ uses a different method for registering
            packages that are on hold than <prgn/apt-get/ and <prgn/dselect/.
            You can identify packages on hold for <prgn/aptitude/ with
-Line 372 
 release: architectures:
+Line 856 
 release: architectures:
            it from being upgraded.</p>
            <p>The "hold" package state for <prgn/aptitude/ can be changed using
-           (replace <tt/hold/ with <tt/unhold/ to unset the "hold" state):</p>
+           (replace <tt/hold/ with <tt/unhold/ to unset the "hold" state):
-           <p>
            <example>
  # aptitude hold <var>package_name</var>
            </example>
-Line 407 
 release: architectures:
+Line 889 
 release: architectures:
          </sect1>
          </sect>
          <sect id="upgrade-process"><heading>Preparing sources for APT</heading>
            <p>Before starting the upgrade you must set up <package/apt/'s
-Line 558 
 deb file:/var/ftp/debian &releasename; m
+Line 1039 
 deb file:/var/ftp/debian &releasename; m
          <sect id="upgradingpackages"><heading>Upgrading packages</heading>
-           <p>The recommended tool for upgrading between &debian; releases is
+           <p>The recommended way to upgrade from previous &debian; releases is
-           to use the package management tool <prgn>aptitude</prgn>. This tool
+           to use the package management tool <prgn>aptitude</prgn>. This program
            makes safer decisions about package installations than running
            <prgn>apt-get</prgn> directly.</p>
-Line 577 
 deb file:/var/ftp/debian &releasename; m
+Line 1058 
 deb file:/var/ftp/debian &releasename; m
            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 584 
 deb file:/var/ftp/debian &releasename; m
+Line 1067 
 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 594 
 deb file:/var/ftp/debian &releasename; m
+Line 1077 
 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
-Line 615 
 deb file:/var/ftp/debian &releasename; m
+Line 1111 
 deb file:/var/ftp/debian &releasename; m
  <!-- FJP: This next section can probably be dropped for etch -->
+ <!-- JFS: Actually, this caused issues if done, as documented in 396331, such as
+      removing the current *running* kernel does this still apply with the
+      latest aptitude 0.4.4-1  -->
          <sect1 id="upgrading_aptitude"><heading>Upgrading aptitude</heading>
            <p>Upgrade tests have shown that &releasename;'s version of
-Line 642 
 deb file:/var/ftp/debian &releasename; m
+Line 1141 
 deb file:/var/ftp/debian &releasename; m
          </sect1>
- <!-- FJP: This next section can probably be dropped for etch -->
-         <sect1 id="upgrading_doc-base"><heading>Upgrading doc-base</heading>
-           <p><em>If you have <package/doc-base/ installed</em>, it must be
-           upgraded before the rest of the system too. Reason is that it may fail
-           if <package/perl/ is upgraded at the same time. You can find out if it
-           is installed using:</p>
-           <p><example>
- # dpkg -l doc-base
-           </example></p>
-           <p>If the line of output begins with "i" then it is installed and
-           must be upgraded before continuing.</p>
-           <p><example>
- # aptitude install doc-base
-           </example></p>
-         </sect1>
          <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
-Line 785 
 dpkg: error processing <var>&lt;package-
+Line 1263 
 dpkg: error processing <var>&lt;package-
          </sect1>
          </sect>
-         <sect id="nownownow"><heading>Things to do before rebooting</heading>
+         <sect id="newkernel"><heading>Upgrading your kernel and related
+         packages</heading>
-           <p>When <tt>aptitude dist-upgrade</tt> has finished, the
+           <p>You should upgrade the Linux kernel separately from the rest of
-           "formal" upgrade is complete, but there are some other things
+           your packages.
-           that should be taken care of <em/before/ the next reboot.</p>
+ <!-- TODO: add something in "before you upgrade", and get the order right -->
+           You may wish to do so yourself, either by installing one
+           of the <package/linux-image-*/ packages or by compiling a customized
+           kernel from sources.
+           Please read the information in this section about potential issues
+           with kernel upgrades.</p>
- <!-- TODO: Needs update; we probably need a section about upgrading to XOrg -->
+           <p>All Linux kernel packages have been renamed from <package/kernel-*/ to
-           <p>Read
+           <package/linux-*/ to clean up the namespace.</p>
-           <file>/usr/share/doc/xfree86-common/README.Debian-upgrade.gz</file> for
-           more info on the upgrade of the X window system packages. This is
-           relevant for users of all previous Debian releases. In short, you
-           need to read it.</p>
-         <sect1 id="newkernel"><heading>Upgrading your kernel</heading>
+ <![ %defaulted-2.4 [
+           <p>If you are currently using a kernel from the 2.4 series,
+           the older stable Linux kernel series, you should upgrade to a 2.6
+           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.
+ <!-- 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>
+ ]]>
-           <p>Note that the Linux kernel was <em/not/ upgraded by these
+         <sect1><heading>Upgrading from a 2.6 kernel</heading>
-           procedures. You may wish to do so yourself, either by installing one
-           of the <package/linux-image-*/ packages or by compiling a customized
+ <!-- JFS: Bug #413458, undeclared linux depency on coreutils' readlink's -m option -->
-           kernel from sources.</p>
+          <p>If you are currently running a 2.6 series kernel from &oldreleasename;
- <!-- JFS: This is not strictly true, if the user was using a non-versioned
+          you will have to upgrade to the latest version of <package/coreutils/ before
-   kernel (kernel-image-2.6-686) he _will_ upgrade the kernel if using
+          you upgrade to the 2.6 series kernel available in &releasename;.
-   aptitude (post-sarge) -->
+ <!-- JFS: Bug #325568 -->
+          In order to do this you first have to do a minimal upgrade of the
- <!-- TODO: Needs to be updated
+          system, a full upgrade of the system packages (as described in <ref
-            Mention 2.4 no longer supported; mention rename to linux-*
+          id="upgradingpackages">) is not an option since the <prgn/udev/
-            Upgrade from 2.6.8 may cause problems -->
+          version in &releasename; does not support 2.6.8 kernels, conversely
+          the <prgn/udev/ version in &oldreleasename; will not work properly with the
+          latest kernels.</p>
+          <p><em>TODO</em>: Describe the steps for this minimal upgrade, should take care
+          of glibc, initrd-tools and udev + linux-image 2.6.</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><heading>initrd-tools deprecated</heading>
+           <p><package/initrd-tools/ is no longer supported and has been
+           superseded by <package/initramfs-tools/ and <package/yaird/.
+           Upgrading to an &releasename; kernel will cause
+           <package/initramfs-tools/ to be installed by default.
  <![ %defaulted-2.4 [
+           If you are upgrading from a 2.4 kernel to a 2.6 kernel for the
+           first time, you must use <package/initramfs-tools/. Using
+           <package/yaird/ will cause linux-image-2.6 installations to
+           fail if you are running a 2.2 or 2.4 kernel.
+ ]]>
+           </p>
+         </sect1>
+         <sect1><heading>devfs deprecated</heading>
+           <p>&releasename; no longer provides support for <prgn>devfs</prgn>.
+           It is recommended that users switch to <package>udev</package> for dynamic
+           <file>/dev</file> management.
+           Debian kernels no longer include support for <prgn>devfs</prgn>,
+           so <prgn>devfs</prgn> users will need to convert their systems
+           manually before upgrading to an &releasename; kernel.</p>
+           <p>If you see the string 'devfs' in <file>/proc/mounts</file>,
+           you are most likely using <prgn>devfs</prgn>.
+           Any config files that reference <prgn>devfs</prgn> style names will need to be
+           adjusted to use <prgn>udev</prgn> style names. Files that are most likely to
+           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
+           <url id="http://bugs.debian.org/341152" name="#341152">.</p>
+         </sect1>
+ <![ %i386-amd64-ia64 [
+         <sect1><heading>Standard kernels have SMP abilities</heading>
+           <p>Multiprocessor systems no longer require a *-smp flavour of the
+           Linux kernel. For &arch-title; linux-image packages without the -smp
+           suffix support both uniprocessor and multiprocessor systems.</p>
+         </sect1>
+ ]]>
-          <p>If you are currently using a kernel from the 2.4 series,
+ <![ %i386 [
-          the older stable Linux kernel series, you may wish to upgrade to a 2.6
+         <sect1><heading>386 kernel flavour deprecated</heading>
-          series kernel for better hardware support or improved performance.</p>
+           <p>Support for the 80386 sub-archicture for &arch-title; has been dropped
+           in &releasename;.  The 386 kernel flavor is no longer supported and has been
-          <p>However, you are strongly advised <strong/not/ to upgrade to a 2.6
+           replaced by the new 486 flavour.</p>
-          kernel as part of the upgrade from &oldreleasename; to &releasename;.
+         </sect1>
-          Some issues associated with an upgrade to 2.6 are documented in
-          <ref id="upgrade-to-2.6">.</p>
  ]]>
+         <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
+           in which device names are assigned.
+           For example, if you have two network adapters that are associated
+           with two different drivers, the devices eth0 and eth1 refer to
+           may be swapped.
+           Please note that the new mechanism means that if you e.g. exchange
+           ethernet adapters in a running &releasename; system, the new adapter
+           will also get a new interface name.</p>
+           <p>For network devices, you can avoid this reordering by using the
+           <prgn>ifrename</prgn> utility to bind physical devices to
+           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. 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
+           ***       by what I remember, and haven't tested this recently
+           -->
+           <p>For storage devices, you can avoid this reordering by using
+           <package/initramfs-tools/ and configuring it to load storage device
+           driver modules in the same order they are currently loaded.
+           To do this, identify the order the storage modules on your system
+           were loaded by looking at the output of <prgn/lsmod/.
+           <prgn/lsmod/ lists modules in the reverse order that they were loaded
+           in, i.e., the first module in the list was the last one
+           loaded.</p>
+           <p>However, removing and reloading modules after initial boot
+           will affect this order. Also, your kernel may have some drivers
+           linked statically, and these names will not appear in the output
+           of <prgn>lsmod</prgn>. You may be able to decipher these driver
+           names and load order from looking at
+           <file>/var/log/kern.log</file>, or the output of
+           <prgn>dmesg</prgn>.</p>
+           <p>Add these module names to <file>/etc/initramfs-tools/modules</file>
+           in the order they should be loaded at boot time. Some module names may
+           have changed between &oldreleasename; and &releasename;. For
+           example, sym53c8xx_2 has become sym53c8xx.</p>
+           <p>You will then need to regenerate your initramfs image(s) by
+           executing <tt>update-initramfs -k all</tt>.</p>
+           <p>Once you are running an &releasename; kernel and <prgn/udev/, you may
+           reconfigure your system to access disks by an alias that is not
+           dependent upon driver load order. These aliases reside in the
+           <file>/dev/disk/</file> hierarchy.</p>
+         </sect1>
+ <![ %ia64 [
+         <sect1><heading>Serial device reordering</heading>
+           <p>If you have an HP machine and you're using the MP serial
+           console port (the connector labelled "console" on the 3-headed
+           cable), this kernel upgrade will break your console!</p>
-          <p>To upgrade your kernel you must first choose the kernel most
+           <p>Please read the following information before upgrading.</p>
-          appropriate for your subarchitecture. A list of kernels available for
-          you to install can be found with:
+           <p><list>
+           <item><p>The console device will change from <file>ttyS0</file> to
-          <example>
+            <file>ttyS1</file>, <file>ttyS2</file>, or <file>ttyS3</file> so
- # apt-cache search ^linux-image
+             <list>
-          </example></p>
+             <item><p>Edit <file>/etc/inittab</file> to add a getty entry for
+              <file>/dev/ttyS1</file> (rx4640, rx5670, rx7620, rx8620, Superdome),
+              <file>/dev/ttyS2</file> (rx1600), or
+              <file>/dev/ttyS3</file> (rx2600).</p></item>
+             <item><p>Edit <file>/etc/securetty</file> to add
+              <file>ttyS1</file>, <file>ttyS2</file>, or
+              <file>ttyS3</file>.</p></item>
+             <item><p>Leave the existing <file>ttyS0</file> entries in
+              <file>/etc/inittab</file> and <file>/etc/securetty</file> so
+              you can still boot old kernels.</p></item>
+             </list>
+           </p></item>
+           <item><p>Edit <file>/etc/elilo.conf</file> to remove any "console="
+            arguments.</p></item>
+           <item><p>Run <prgn/elilo/ to install the bootloader with new
+            configuration.</p></item>
+           <item><p>Reboot and use the EFI boot option maintenance menu to
+            select exactly one device for console output, input, and standard
+            error.  Then do a cold reset so the changes take
+            effect.</p>
+            <p>For the MP console, be careful to select the device with
+            "Acpi(HWP0002,700)/Pci(...)/Uart" in the path.</p></item>
+           </list></p>
+           <p>More details about these changes and troubleshooting hints are
+           available at
+           <url id="http://lists.debian.org/debian-ia64/2005/01/msg00008.html">.</p>
+         </sect1>
+ ]]>
+         <sect1><heading>Upgrading the kernel</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 unnecesary, maybe dpkg -l 'linux-image*' would be
+      better here? -->
+           <example>
+ # dpkg -l | grep '^ii  linux-image'
+           </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 benefit.</p>
+          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
-Line 841 
 dpkg: error processing <var>&lt;package-
+Line 1514 
 dpkg: error processing <var>&lt;package-
           in <file>/usr/share/doc/kernel-package</file>.</p>
          </sect1>
+         </sect>
+         <sect id="nownownow"><heading>Things to do before rebooting</heading>
+           <p>When <tt>aptitude dist-upgrade</tt> has finished, the
+           "formal" upgrade is complete, but there are some other things
+           that should be taken care of <em/before/ the next reboot.</p>
+         <sect1 id="rerunlilo"><heading>Rerun lilo</heading>
+           <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>
+ # /sbin/lilo
+           </example></p>
+           <p>Notice this is needed even if you did not upgrade your system's kernel, as
+           lilo's second stage will change due to the package upgrade.</p>
+           <p>Also, review the contents of your <file>/etc/kernel-img.conf</file> and
+           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>
+           <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>
+         </sect1>
- <!-- TODO: Replace with #389099 -->
+         <sect1 id="mdadm"><heading>Upgrading mdadm</heading>
-         <sect1 id="mdadm"><heading>Upgrading from raidtools2 to mdadm</heading>
-          <p><package/raidtools2/ is no longer maintained by its upstream
+          <p>mdadm now needs a configuration file to assemble MD arrays (RAID)
-          developers and has been replaced by the <package/mdadm/ package.
+          from the initial ramdisk and during the system initialisation
-          <prgn/mdadm/ is a single program that can perform almost any RAID
+          sequence. Please make sure to read and act upon the instructions in
-          management task without a configuration file; by default it does
+          <file>/usr/share/doc/mdadm/README.upgrading-2.5.3.gz</file> after
-          not use one.</p>
+          the package has been upgraded <strong>and before you reboot</strong>.
+          The latest version of this file is available at
-          <p>The remainder of this section gives some upgrade hints for users of
+          <url id="http://svn.debian.org/wsvn/pkg-mdadm/mdadm/trunk/debian/README.upgrading-2.5.3?op=file">;
-          <package/raidtools2/.</p>
+          please consult it in case of problems.</p>
-          <p>As mentioned above, in many cases <prgn/mdadm/ can work without
-          configuration file. If you use a kernel that automatically configures
-          the RAID array for you, can skip this paragraph &mdash; you merely have to
-          install the package <package/mdadm/ and the RAID will be detected during
-          the boot process. The standard kernels in Debian have support for the
-          configuration of RAID arrays on boot. You also need to make sure that
-          the partitions are set to type "Linux raid autodetect" (id <tt/fd/). The
-          following command will list the current type of partitions:
-          <example>
- # fdisk -l <var>disk_device</var>
-          </example></p>
-          <p>If you have a mixed setup with some RAID arrays that are auto-configured
-          and some that are not, you have to create a configuration file.</p>
-          <p>To migrate from the configuration file <file>/etc/raidtab</file>
-          (<package/raidtools2/) to <file>/etc/mdadm/mdadm.conf</file>
-          (<package/mdadm/), please execute:
-          <example>
- # echo 'DEVICE /dev/hd*[0-9] /dev/sd*[0-9]' &gt; /etc/mdadm/mdadm.conf
- # mdadm --examine --scan &gt;&gt; /etc/mdadm/mdadm.conf
-          </example></p>
-          <p>These commands will generate a configuration file with the existing
-          arrays on the system.</p>
-          <p>You should also make sure that the RAID arrays are started automatically
-          on boot. Check the file <file>/etc/default/mdadm</file> to see if the variable
-          AUTOSTART is set to <tt/true/.</p>
          </sect1>
          </sect>
-Line 984 
 didn't belong to them... -->
+Line 1668 
 didn't belong to them... -->
          <chapt id="information">
          <heading>Issues to be aware of for &releasename;</heading>
+         <sect id="problems"><heading>Potential problems</heading>
+           <p>Sometimes, changes have side-issues we cannot reasonably avoid,
+           or we expose bugs somewhere else.
+           We document here the issues we are aware of.
+           Please also read the errata, the relevant packages' documentation,
+           bug reports and other information mentioned in <ref id="morereading">.
+           </p>
+           <sect1 id="window-scaling"><heading>Certain networking site cannot be reached by TCP</heading>
+           <p>
+           Since 2.6.17, Linux aggresively uses TCP window scaling which is specified in RFC 1323.
+           Some servers have a broken behaviour, 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">
+           for more information.
+           </p>
+           </sect1>
+ <![ %i386 [
+           <sect1 id="poweroff"><heading>Automatic poweroff stops working</heading>
+           <p>
+           On some older systems, <tt>shutdown -h</tt> may not power off the system
+           anymore (but just stop it). This happens because apm needs to be used there.
+           Adding <tt>acpi=off apm=power_off</tt> to the kernel's command line, e.g.
+           in <package/grub/ or <package/lilo/ configuration files should fix this issue.
+           Please see bug
+           <url id="http://bugs.debian.org/390547" name="#390547">
+           for additional information.
+           </p>
+           </sect1>
+ ]]>
+           <sect1 id="apt-pdiff"><heading>Apt downloads small files with update</heading>
+           <p>
+           Support has been added to <prgn>apt</prgn> to download only the difference
+           between packages files. This is handy for people with bad network connections,
+           but people having a very nearby mirror may want to disable this feature.
+           One can disable it by adding <tt>Acquire::Pdiffs "false";</tt> to
+           <file>/etc/apt/apt.conf</file>.
+           </p>
+           </sect1>
+ <![ %i386 [
+           <sect1 id="hp-acpi"><heading>ACPI support disabled for some HP laptop models in &releasename; kernel</heading>
+           <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. Also, fans might not work after
+           the system is suspedend. The kernel therefore disables ACPI support
+           internally when it detects certain ACPI BIOS versions.  Models known
+           to be affected by this change include the HP nx6125, nx6120, nx6325,
+           nc6120 and nc6000 models.
+           </p>
+           <p>
+           Users who require ACPI support on these systems may install a Linux 2.6.19 or
+           later kernel.  Please see Debian bug
+           <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>
+ ]]>
+         </sect>
  <!-- Controversial, disabled for now, please translate though
          <sect id="german-quotes"><heading>Problems with German Quotes</heading>
-Line 1049 
 didn't belong to them... -->
+Line 1804 
 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>
  ]]>
            <p>Once you have installed your 2.6 kernel, but before you reboot,
-Line 1084 
 didn't belong to them... -->
+Line 1847 
 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 1134 
 didn't belong to them... -->
+Line 1897 
 didn't belong to them... -->
          </sect1>
  ]]> <!-- %not-s390 -->
- ]]> <!-- %defaulted-2.4 -->
  <!-- FJP: May already be covered by kernel team text
            Etch Debian kernels depend on udev via initramfs-tools -->
-Line 1151 
 didn't belong to them... -->
+Line 1913 
 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 1164 
 didn't belong to them... -->
+Line 1928 
 didn't belong to them... -->
          for further information.</p>
          </sect1>
-         </sect>
+       </sect>
+ ]]> <!-- %defaulted-2.4 -->
+       <sect id="xorg"> <heading>XFree86 to X.Org transition</heading>
+         <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
+         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
+         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>
+         <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>.
+         You can then use <tt>dpkg -S</tt> to find out which Debian package
+         installed that file (if any), and remove such packages with
+         <tt>dpkg --remove</tt>. Please make a note which packages you
+         remove, so that you can install substitute packages later on.
+         Before continuing with the upgrade, all files in
+         <file>/usr/X11R6/bin</file> need to be removed.</p>
+         <p>Please read <url id="http://wiki.debian.org/Xorg69To7">
+         for more details and other issues.</p>
+       </sect>
+       <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) <package/exim/, which has been replaced
+       by the completely new package <package/exim4/.</p>
+       <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
+       <prgn/exim/ 3.xx, please upgrade your <package/exim/ installation to <package/exim4/ manually.
+       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 <package/exim/ package is not going to be upgraded and that it won't get
+       security support after support for &oldreleasename; has been discontinued.</p>
+       <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
+       inside the packages as well.</p>
+       <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 <prgn/Exim/ 3, which will help you in doing the actual
+       transition.</p>
+ <!-- FIXME: update with decisions of (S)RMs might be needed -->
+       </sect>
+       <sect id="apache2"> <heading>Upgrading apache2</heading>
+         <p>Apache has been upgraded to the new version 2.2.
+         Although this shouldn't impact the average user,
+         there are some potential issues to be aware of.</p>
+         <p><url id="http://httpd.apache.org/docs/2.2/upgrading.html"> contains
+         the upstream changes. Please read this page, and remember that especially:
+         <list>
+         <item><p>all modules need to be recompiled</p></item>
+         <item><p>authorization modules have been resorted and renamed</p></item>
+         <item><p>some configuration options have been renamed</p></item>
+         </list></p>
+         <p>Debian-specific changes include that the string SSL is no longer defined,
+         as ssl is now supported by the default package.</p>
+       </sect>
+       <sect id="php-globals"> <heading>Deprecated insecure php configurations</heading>
+         <p>For many years, turning on the <tt/register_globals/ settings in PHP
+         has been known to be insecure and dangerous, and this option has defaulted to
+         off for some time now. This configuration is
+         now finally deprecated on Debian systems as too dangerous.
+         The same applies to flaws in <tt/safe_mode/ and <tt/open_basedir/, which
+         have also been unmaintained for some time.</p>
+         <p>Starting with this release, the Debian security team does not provide
+         security support for a number of PHP configurations which are known to
+         be insecure. Most importantly, issues resulting from
+         <tt/register_globals/ being turned on will no longer be addressed.</p>
+         <p>If you run legacy applications that require <tt/register_globals/,
+         enable it for the respective paths only, e.g. through the Apache
+         configuration file. More information is available in the
+         <file>README.Debian.security</file> file in the PHP
+         documentation directory (<file>/usr/share/doc/php4</file>,
+         <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 <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
+         large functional changes in security updates.
+         We cannot predict it today, but during lifetime of &releasename; the
+         Debian Security Team may come to a point where supporting
+         Mozilla products is no longer feasible and announce
+         the end of security support for Mozilla products.
+         You should take this into account when deploying Mozilla and consider
+         alternatives available in Debian if the absence of security support would
+         pose a problem for you.</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 that 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 1172 
 didn't belong to them... -->
+Line 2119 
 didn't belong to them... -->
          <heading>More information on &debian;</heading>
          <sect id="morereading"> <heading>Further reading</heading>
-         <p>Beyond these release notes and the installation guide further
+         <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
-         including the Debian Guide, Debian New Maintainers Guide, and Debian
+         including the Debian Reference, Debian New Maintainers Guide, and Debian
-         FAQ are available, and many more. For full details of the resources
+         FAQ are available, and many more. For full details of the existing resources
-         available see the <url id="&url-ddp;" name="DDP website">.</p>
+         see the <url id="&url-ddp;" name="DDP website">.</p>
          <p>Documentation for individual packages is installed into
          <file>/usr/share/doc/<var>package</var></file>, this may include
-Line 1212 
 didn't belong to them... -->
+Line 2159 
 didn't belong to them... -->
          <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 favourite IRC client at
          &debian-irc-server; and join #debian.</p>
          <p>Please follow the channel guidelines, respecting other users
-Line 1302 
 didn't belong to them... -->
+Line 2249 
 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.3896
 


changed lines


 
Added in v.4226
 Legend:



Removed from v.3896
 


changed lines


 
Added in v.4226
-Removed from v.3896
+Added in v.4226

	ViewVC Help
Powered by ViewVC 1.1.5