/[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 4198 by jfs,
Tue Mar 20 08:27:26 2007 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.149 2007-03-20 08:27:26 jfs 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 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'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 116
+Line 170
          <sect id="newdistro"><heading>What's new in the distribution?</heading>
+ <!-- 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 6200 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: over 10500 software packages (this is 67% 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 (over 3400, 22% of the packages in &oldreleasename;) 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 192
             Window System, taking full advantage of hardware
             OpenGL-acceleration for supported devices.</p>
-            <p>&debian; again ships with several desktop applications. Amongst
+            <p>&debian; again ships with several desktop applications and environments. Amongst
-            others it now includes GNOME 2.14, KDE 3.5, OpenOffice.org 2.0 and
+            others it now includes the desktop environments GNOME 2.14<footnote>With some modules from
-            KOffice 1.6.</p>
+            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 149
+Line 250
             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
-Line 290
+Line 419
               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 11
+              If the graphical user interface is used, an additional eleven
               languages are supported. These languages can only be selected
-              using this installer as their fonts cannot be presented
+              using this installer as their character sets cannot be presented
-              in non-graphical environments.
+              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 local can now select
+              Users that do not wish to use any locale can now select
-              <em/C/ as their preferred local in the installer's language
+              <em/C/ as their preferred locale in the installer's language
               selection.
-              More information on
+              More information on language coverage is available at the
-              language coverage is available at the
               <url id="&url-d-i-i18n;" name="d-i languages list">.
               </p></item>
-Line 310
+Line 440
               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 needed be.</p></item>
+              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>
-Line 339
+Line 483
        </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.
-Line 357
+Line 500
          </example></p>
          <p>You may also want to check the <url id="&url-installer;index#errata"
-         name="errata"> for debian-installer.</p>
+         name="errata"> for debian-installer for a list of knonw issues.</p>
  <![ %alpha [
          <!-- TODO: Still true? -->
-Line 385
+Line 528
        </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>The installation system will again offer
-Line 404
+Line 610
        </sect>
- <!-- TODO: Mention localization config? -->
        </chapt>
-Line 457 
 release: architectures:
+Line 661 
 release: architectures:
            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
-           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 also plan to
-           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 837 
 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 844 
 deb file:/var/ftp/debian &releasename; m
+Line 1067 
 deb file:/var/ftp/debian &releasename; m
            report. To start the recording, type:
            <example>
- # script -t -a ~/upgrade-to-&releasename;.typescript 2>~/upgrade-to-&releasename;.timing
+ # script -t -a ~/upgrade-&releasename;.script 2>~/upgrade-&releasename;.time
            </example>
            or similar. Do not put the typescript file in a temporary
-Line 854 
 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 -R ~root/upgrade-to-&releasename;.typescript</tt>
+           logging in, use <tt>less -R ~root/upgrade-&releasename;.script</tt>
            to view the file.</p>
-Line 867 
 deb file:/var/ftp/debian &releasename; m
+Line 1090 
 deb file:/var/ftp/debian &releasename; m
            you can use the <prgn/scriptreplay/ program to replay the whole session:
            <example>
- # scriptreplay ~/upgrade-to-&releasename;.timing 2>~/upgrade-to-&releasename;.typescript
+ # scriptreplay ~/upgrade-&releasename;.time ~/upgrade-&releasename;.script
            </example>
            </p>
+         </sect1>
          <sect1 id="updating_lists"><heading>Updating the package list</heading>
-Line 1141 
 dpkg: error processing <var>&lt;package-
+Line 1365 
 dpkg: error processing <var>&lt;package-
          </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
-Line 1255 
 dpkg: error processing <var>&lt;package-
+Line 1479 
 dpkg: error processing <var>&lt;package-
            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>
-Line 1298 
 dpkg: error processing <var>&lt;package-
+Line 1525 
 dpkg: error processing <var>&lt;package-
          <sect1 id="rerunlilo"><heading>Rerun lilo</heading>
            <p>If you are using <package/lilo/ as your bootloader (it is the
-           default bootloader for &oldreleasename;) it is strongly recommended
+           default bootloader for some installations of &oldreleasename;) it is strongly recommended
            that you rerun lilo after the upgrade:
            <example>
  # /sbin/lilo
-Line 1800 
 didn't belong to them... -->
+Line 2027 
 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
          large functional changes in security updates.
-Line 1856 
 didn't belong to them... -->
+Line 2086 
 didn't belong to them... -->
 .14 Release Notes">.</p>
        </sect>
-       <sect id="nano"> <heading>Default editor changed to nano</heading>
+ <!-- FJP: Bug #398887 -->
-         <p>The default editor for default installations in &releasename; is <package/nano/.
+       <sect id="default-editor"> <heading>Default editor</heading>
-         Previous Debian releases set the default editor for all users to
+         <p>If you were using <prgn/vim/ as your default editor, this may
-         <package/vim/, in this release the default behaviour has changed and users
+         be changed to <prgn/nano/ during the upgrade.</p>
-         will get a more user-friendly editor.</p>
+         <p>Administrators that wish to change the default editor for all users
-         <p>Users wishing to retain the previous behaviour can either define the
+         will have to update the alternatives system using:
-         environment variable <em>EDITOR</em> by introducing the following lines
-         in their own profiles:
            <example>
- EDITOR=vi
+ # update-alternatives --config editor
- export EDITOR
- alias editor=$EDITOR
            </example>
          </p>
-         <p>Administrators that wish to change the behaviour for all users will have
+         <p>Users wishing to change the default editor can define the
-         to update the alternatives system using:
+         environment variable <em>EDITOR</em> by introducing the following lines
+         in their own profiles:
            <example>
- # update-alternatives --config editor
+ EDITOR=vi
+ export EDITOR
+ alias editor=$EDITOR
            </example>
          </p>
-Line 2020 
 alias editor=$EDITOR
+Line 2249 
 alias editor=$EDITOR
            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.4198
 


changed lines


 
Added in v.4226
 Legend:



Removed from v.4198
 


changed lines


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

	ViewVC Help
Powered by ViewVC 1.1.5