[l10n-russian CVS] release-notes/sgml release-notes.en.sgml, 1.19,
1.20
Yuri Kozlov
yuray-guest at alioth.debian.org
Wed Apr 4 17:58:32 UTC 2007
Update of /cvsroot/l10n-russian/release-notes/sgml
In directory alioth:/tmp/cvs-serv21556/sgml
Modified Files:
release-notes.en.sgml
Log Message:
Index: release-notes.en.sgml
===================================================================
RCS file: /cvsroot/l10n-russian/release-notes/sgml/release-notes.en.sgml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -r1.19 -r1.20
--- release-notes.en.sgml 3 Apr 2007 18:00:59 -0000 1.19
+++ release-notes.en.sgml 4 Apr 2007 17:58:30 -0000 1.20
@@ -13,7 +13,9 @@
<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), Andreas Barth (current)</name><email></email>
+ Bradford, Frans Pop (current), Andreas Barth (current), Javier
+ Fernández-Sanguino Peña (current), Steve Langasek
+ (current)</name><email></email>
</author>
<author>
<name></name><email>debian-doc at lists.debian.org</email>
@@ -70,13 +72,18 @@
<list>
<!-- TODO: any more things to add here? -->
+ <item><p>The status of your package database before and after the
+ upgrade: <prgn/dpkg/'s status database available at
+ <file>/var/lib/dpkg/status</file> and <prgn/aptitudes/'s package
+ state information, available at
+ <file>/var/lib/aptitude/pkgstates</file>. You should have made a
+ backup before the upgrade as described at <ref id="data-backup">,
+ but you can also find backups of this information in
+ <file>/var/backups</file>.</p></item>
+
<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">.</p></item>
-
<item><p>Your aptitude logs, available at <file>/var/log/aptitude</file>.</p></item>
</list></p>
@@ -88,8 +95,9 @@
</sect>
<sect id="sources"><heading>Sources for this document</heading>
- <p>This document uses <package>debiandocsgml</package>. Its sources
- are available in the CVS of the <em>Debian Documentation Project</em>.
+ <p>This document is generated using <package>debiandoc-sgml</package>.
+ Sources for the Release Notes
+ are available in the CVS repository of the <em>Debian Documentation Project</em>.
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
@@ -167,12 +175,67 @@
&architecture; platform.</p>
]]>
+<![ %arm [
+ <sect id="new-arch"><heading>What's new for &arch-title;?</heading>
+ <p>RiscPC (RPC) support is incomplete and will be removed after etch.
+ While a kernel for RiscPC is still provided in etch, the installer
+ doesn't support this system.</p>
+
+ <p>Support for Intel's IXP4xx platform has been added. The installer
+ includes support for the Linksys NSLU2, a small and inexpensive device
+ which allows the usage of attached storage through USB. More
+ information about Debian on the NSLU2 can be found at
+ <url id="http://www.cyrius.com/debian/nslu2/">.</p>
+
+ <p>Support has also been added for Intel's I/O Processor (IOP) platform.
+ Specifically, &debian; &release; supports IOP 32x based devices. Two Network
+ Attached Storage (NAS) devices based on an IOP chip are supported in
+ the installer: the GLAN Tank from IO-Data and the Thecus N2100. See
+ <url id="http://www.cyrius.com/debian/iop/">.</p>
+ </sect>
+]]>
+
+<![ %mips-mipsel [
+ <sect id="new-arch"><heading>What's new for &arch-title;?</heading>
+<![ %mipsel [
+ <p>DECstation support is incomplete and untested in etch and will be
+ removed completely after this release. This includes both DECstation
+ variants previously supported in Debian, r3k-kn02 and r4k-kn04.</p>
+
+ <p>Installations on MIPS based Cobalt machines (Qube 2700, RaQ1, Qube2,
+ RaQ2) are now possible without the use of a serial console. By
+ default, installations on Cobalt are now done via SSH. See
+ <url id="http://www.cyrius.com/debian/cobalt/"> for more information.</p>
+]]>
+<![ %mips [
+ <p>Support for SGI's IP32 platform has been added. The IP32 platform
+ consists of SGI O2 machines with R5000, R5200 or RM7000 processors.
+ Installation is possible via frame buffer or the serial console.</p>
+]]>
+ <p>Support for Broadcom's SB1A evaluation board BCM91480B ("BigSur"),
+ which is based on the BCM1480 quad-core chip, has been added, both to
+ the kernel and the installer. This board is supported both in little
+ and big endian mode.</p>
+
+ <p>Support for a Qemu machine has been added. The Qemu/MIPS machine
+ emulates a classic ISA PC style machine with a MIPS 4Kc CPU.</p>
+ </sect>
+]]>
+
+<![ %powerpc [
+ <sect id="new-arch"><heading>What's new for &arch-title;?</heading>
+ <p>This release adds support for 64bit PowerPC architectures (IBM
+ pSeries, Apple G5 powermacs). Support for the Apple Apus subarchitecture
+ has been dropped; the Apple Nubus subarchitecture is also not supported.</p>
+ </sect>
+]]>
+
<!--
<p>&debian; &release; for the &arch-title; architecture ships with
kernel version &kernelversion;.</p>
-->
- <sect id="newdistro"><heading>What's new in the distribution?</heading>
+ <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 -->
@@ -180,10 +243,10 @@
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 6,200 new packages, for a total of over 18,000 packages. Most
- of the software in the distribution has been updated: over 10,500
- software packages (this is 67% of all packages in &oldreleasename;).
- Also, a significant number of packages (over 3400, 22% of the
+ over &packages-new; new packages, for a total of over &packages-total; packages. Most
+ of the software in the distribution has been updated: over &packages-updated;
+ software packages (this is &packages-update-percent;% of all packages in &oldreleasename;).
+ Also, a significant number of packages (over &packages-removed;, &packages-removed-percent;% of the
packages in &oldreleasename;) have for various reasons been removed
from the distribution. You will not see any updates for these
packages and they will be marked as 'obsolete' in package management
@@ -245,6 +308,14 @@
</list></p>
+ <p>The official &debian; distribution now ships on 19 to 23
+ binary CDs (depending on the architecture) and a similar number of
+ source CDs. A DVD version of the distribution is also available.</p>
+
+<!-- FIXME: Note on LSB support? (3.1?) -->
+
+ <sect1 id="pkgmgmt"><heading>Package management</heading>
+
<!-- FIXME (vorlon): is aptitude news for etch, does it belong here? -->
<p><prgn/aptitude/ is the preferred program for package management
from console.
@@ -252,14 +323,10 @@
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 19 to 23
- binary CDs (depending on the architecture) and a similar number of
- source CDs. A DVD version of the distribution is also available.</p>
-
-<!-- FIXME: Note on LSB support? (3.1?) -->
-
- <sect1 id="secureapt"><heading>Secure APT</heading>
+ <p>For &releasename; an advanced conflict resolving mechanism has been
+ implemented in <prgn/aptitude/ that will try to find the best solution
+ if conflicts are detected because of changes in dependencies between
+ packages.</p>
<!-- FIXME: More content needed here? -->
<p><em/Secure APT/ is now available in &releasename;. This feature adds
@@ -277,13 +344,17 @@
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</prgn>'s manual page, the
+ <p>For more information please read <manref name="apt" section="8">, 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="Debian Wiki">.</p>
+ <p>Another feature that was added in <prgn/apt/ is the ability to
+ download only the changes in <file/Packages/ files since your last
+ update. More about this feature in <ref id="apt-pdiff">.</p>
+
</sect1>
<sect1 id="volatile"><heading>debian-volatile now an official service</heading>
@@ -361,7 +432,7 @@
of <prgn/vim/ (<package/vim-tiny/) instead of <package/nvi/.</p></item>
<tag>Changes in default features for <tt>ext2</tt>/<tt>ext3</tt></tag>
- <item><p>New ext2 and ext3 filesystems will be created with features
+ <item><p>New ext2 and ext3 file systems will be created with features
<em/dir_index/ and <em/resize_inode/ enabled by default. The first
feature speeds up operations on directories with many files; the
second makes it possible to resize a file system on-line (i.e. while it
@@ -405,9 +476,12 @@
<sect id="kernel-changes"><heading>Major kernel-related changes</heading>
<p>&debian; &release; ships with kernel version &kernelversion; for all
- architectures; 2.4 kernels are no longer officially supported.</p>
+ architectures; the release is still mostly<footnote>Some individual
+ packages may no longer work correctly with a 2.4 kernel; see
+ <ref id="incompatible-2.4">.</footnote> compatible with 2.4 kernels, but
+ Debian no longer provides or supports 2.4 kernel packages.</p>
- <p>There have been major changes, both in the kernel itself and in the
+ <p>There have been major changes both in the kernel itself and in the
packaging of the kernel for Debian. Some of these changes complicate
the upgrade procedure and can potentially result in problems while
rebooting the system after the upgrade to &releasename;. This section
@@ -424,7 +498,7 @@
<p><taglist>
<tag>Kernel packages renamed</tag>
<item><p>All Linux kernel packages have been renamed from <tt/kernel-*/
- to <tt/linux-*/ to clean up the namespace: it will make it easier to
+ to <tt/linux-*/ to clean up the namespace. This will make it easier to
include non-Linux kernels in Debian in the future.</p></item>
<![ %i386 [
@@ -435,22 +509,31 @@
]]>
<![ %amd64 [
<tag>Single generic kernel for &arch-title;</tag>
- <item><p>In &oldreleasename; had separate kernel flavors for different
- processor families. Because of changes in the kernel which will
+ <item><p>In &oldreleasename; there were separate kernel flavors for
+ different processor families of this architecture. Because of changes
+ in the kernel which will
automatically optimize the kernel for the processor(s) in the system,
there is no longer any real need for seperate kernel flavors.</p></item>
]]>
<![ %i386-amd64-ia64 [
<tag>Standard kernels have SMP abilities</tag>
- <item><p>Multiprocessor systems no longer require a <tt/*-smp/ flavor of the
+ <item><p>Multiprocessor systems no longer require an <tt/*-smp/ flavor of the
Linux kernel. For &arch-title;, <tt/linux-image/ packages without the <tt/-smp/
suffix support both uniprocessor and multiprocessor systems.
<![ %i386 [
- There is one exception: the 486 flavor only supports a single processor.
+ (The one exception is the 486 flavor, which only supports a single
+ processor.)
]]>
</p></item>
]]>
+
+<![ %mips [
+ <tag>r5k-ip22 kernel flavor dropped</tag>
+ <item><p>The kernel image for IP22 machines with an R5000 CPU has been
+ dropped because the r4k-ip22 image now supports IP22 machines with either
+ an R4x000 or an R5000 CPU.</p></item>
+]]>
</taglist></p>
<p>Where possible, dummy transition packages that depend on the new packages
@@ -463,7 +546,7 @@
<![ %no-initrd [
<p>The Debian kernel image packages for &arch-title; do not require an
initrd for booting the system. This means that the information in this
- section may not really be relevant for you, but is still included for
+ section may not be relevant for you, but is still included for
reference.</p>
]]>
<p>
@@ -494,7 +577,7 @@
</p>
<p>The package <package/initrd-tools/ is still included in &releasename;
- because it is needed for upgrades from &oldreleasename;. The package will
+ because it is needed for upgrades from &oldreleasename;. It will
be dropped for the next release.</p>
]]>
@@ -502,16 +585,16 @@
<sect1 id="kernel-devfs"><heading>Dynamic <file>/dev</file> management</heading>
- <p>&releasename; kernels no longer provide support for <prgn/devfs/.</p>
+ <p>&releasename; kernels no longer provide support for <tt>devfs</tt>.</p>
- <p>The replacement for <prgn/devfs/ is <prgn/udev/.
+ <p>The replacement for <tt>devfs</tt> is <package/udev/.
<p><package/udev/ is a userspace implementation of devfs. It is mounted
over the <file>/dev</file> directory and will populate that directory
with devices supported by the kernel. It will also dynamically add and
remove devices as kernel modules are loaded or unloaded respectively,
based on events generated by the kernel. <prgn/udev/ is a lot more
- versatile than <prgn/devfs/ and offers services that are used by other
- programs like <prgn/hal/ (hardware abstraction layer).</p>
+ versatile than <tt/devfs/ and offers services that are used by other
+ packages like <package/hal/ (hardware abstraction layer).</p>
<![ %uses-initrd [
<p>If you install a Debian kernel image, <package/udev/ will be installed
@@ -625,14 +708,14 @@
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
+ <item><p>It is now possible to set up file systems on an LVM volume
using guided partitioning.</p>
- <p>The installer is also able to set up encrypted filesystems.
+ <p>The installer is also able to set up encrypted file systems.
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>
+ file systems (except <file>/boot</file>) as logical volumes.</p></item>
<![ %g-i [
<tag>Graphical user interface</tag>
@@ -825,12 +908,12 @@
<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>
+ important to know about before you begin.</p>
- <sect1><heading>Backup any data or configuration information</heading>
+ <sect1 id="data-backup"><heading>Back up any data or configuration information</heading>
<p>Before upgrading your system, it is strongly recommended that
- you make a full backup, or at least backup any data or
+ you make a full backup, or at least back up any data or
configuration information you can't afford to lose. The upgrade
tools and process are quite reliable, but a hardware failure in
the middle of an upgrade could result in a severely damaged
@@ -840,7 +923,7 @@
<file>/etc</file>, <file>/var/lib/dpkg</file> and the output of
<tt>dpkg --get-selections "*"</tt> (the quotes are important).</p>
- <p>The upgrade process in itself does not modify anything in the
+ <p>The upgrade process itself does not modify anything in the
<file>/home</file> directory. However, some applications (e.g.
parts of the Mozilla suite, and the GNOME and KDE desktop
environments) are known to overwrite existing user settings with new
@@ -879,17 +962,17 @@
</sect1>
- <sect1><heading>Prepare a safe environment for the upgrade</heading>
+ <sect1 id="upgrade_preparations"><heading>Prepare a safe environment for the upgrade</heading>
<p>The distribution upgrade should be done either locally from a
textmode virtual console (or a directly connected serial
terminal), or remotely via an <prgn/ssh/ link.</p>
- <p>In order to gain extra safety margin, we suggest you to run
- upgrade processes in the virtual console provided by the
- <prgn/screen/ program which enables the safe reconnection and ensures
- the uninterrupted upgrade processes even if the remote connection
- process fails by chance.</p>
+ <p>In order to gain extra safety margin when upgrading remotely, we
+ suggest that you run upgrade processes in the virtual console provided by
+ the <prgn/screen/ program, which enables safe reconnection and ensures
+ the upgrade process is not interrupted even if the remote connection
+ process fails.</p>
<!-- JFS: probably can be removed for lenny -->
<p>If you are upgrading remotely via an <prgn/ssh/ link it is highly
@@ -910,15 +993,17 @@
half-upgraded.</p>
<!-- TODO: surely gdm/kdm are sane? -->
+ <!-- (vorlon) haha, no, gdm is not; I had that thought, and tested a gdm
+ restart on my live session ;) -->
</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
2.4-series before upgrading <package/glibc/.
- This should preferably 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.
+ This should be done before starting the upgrade.
+ It is recommended that you directly upgrade to the 2.6.8 kernel available
+ in &oldreleasename;, instead of upgrading to a 2.4 kernel.
</p>
</sect1>
@@ -928,8 +1013,15 @@
<heading>Checking system status</heading>
<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 to remove these packages first.</p>
+ upgrades from "pure" &oldreleasename; systems without third-party
+ packages.
+<!-- vorlon: remove for lenny -->
+ In particular, there are known problems with third-party packages
+ which install programs under <file>/usr/X11R6/bin/</file> causing problems
+ with upgrades due to the X.org transition (<ref id="xorg">).
+<!-- -->
+ For greatest reliability of the upgrade process, you may wish to remove
+ third-party packages from your system before you begin upgrading.</p>
<p>This procedure also assumes your system has been updated to the
latest point release of &oldreleasename;. If you have not done this
@@ -939,13 +1031,14 @@
<p>In some cases, the use of <prgn/apt-get/ for installing packages instead
of <prgn/aptitude/ might make <prgn/aptitude/ consider a package as
- "unused" and schedule it for removal. In general, the system should be
- fully up-to-date and "clean".</p>
+ "unused" and schedule it for removal. In general, you should make sure
+ the system is fully up-to-date and "clean" before proceeding with
+ the upgrade.</p>
<p>Because of this you should review if there are any pending actions
in the package manager <prgn/aptitude/. If a package is scheduled
- for removal or update in the package manager, it might impact negatively
- on the upgrade procedure. Note that this is only possible if your
+ for removal or update in the package manager, it might negatively impact
+ the upgrade procedure. Note that correcting this is only possible if your
<file/sources.list/ still points to <em/&oldreleasename/; and not to
<em/stable/ or <em/&releasename;/; see <ref id="old-sources">.</p>
@@ -1015,11 +1108,11 @@
it or put an epoch in the version, you must put it on hold to prevent
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>The "hold" package state for <prgn/aptitude/ can be changed using:
<example>
# aptitude hold <var>package_name</var>
</example>
+ Replace <tt/hold/ with <tt/unhold/ to unset the "hold" state.
</p>
<p>If there is anything you need to fix, it is best to make sure your
@@ -1042,7 +1135,7 @@
system. Such packages are most likely to cause problems during an
upgrade as they may result in file conflicts<footnote>Debian's
package management system normally does not allow a package to remove
- or replace a file owned by another package; not unless it has been
+ or replace a file owned by another package unless it has been
defined to replace that package.</footnote>. Section <ref id="trouble">
has some information on how to deal with file conflicts if they should
occur.</p>
@@ -1066,7 +1159,7 @@
<p>And 2.6 kernel images if you have installed them using a kernel metapackage:
<example>
-# aptitude unmarkauto $(dpkg-query -W 'kernel-image-2.6*' | cut -f1)
+# aptitude unmarkauto $(dpkg-query -W 'kernel-image-2.6.*' | cut -f1)
</example></p>
<p>Note: You can review which packages are marked as <em/auto/ in aptitude by running:
@@ -1139,17 +1232,9 @@
multiple directories.</p>
<p>After adding your new sources, disable the previously existing
- "<tt/deb/" lines in <file/sources.list/, by placing a hash sign
+ "<tt/deb/" lines in <file/sources.list/ by placing a hash sign
(<tt/#/) in front of them.</p>
- <p>Any package needed for installation that is fetched from the
- network is stored in <file>/var/cache/apt/archives</file>
- (and the <file>partial/</file> subdirectory, during download), so
- you must make sure you have enough space before attempting to
- start the installation. With a reasonably extended Debian
- installation, you can expect at least 300 MB of downloaded
- data.</p>
-
</sect1>
<sect1 id="localmirror"><heading>Adding APT sources for a local mirror</heading>
@@ -1179,7 +1264,7 @@
multiple directories.</p>
<p>After adding your new sources, disable the previously
- existing "<tt/deb/" lines in <file/sources.list/, by placing a
+ existing "<tt/deb/" lines in <file/sources.list/ by placing a
hash sign (<tt/#/) in front of them.</p></sect1>
<sect1 id="cdroms"><heading>Adding APT source from CD-ROM or DVD</heading>
@@ -1238,7 +1323,7 @@
# mount -o remount,rw /<var>mountpoint</var>
</example></p>
- <p>Next you should double check that the APT source entries (in
+ <p>Next you should double-check that the APT source entries (in
<file>/etc/apt/sources.list</file>) refer either to
"<tt/&releasename;/" or to "<tt>stable</tt>". There should not be
any sources entries pointing to &oldreleasename;.
@@ -1304,11 +1389,14 @@
<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>
+ described in <ref id="upgrading_other">. First, any package needed for
+ installation that is fetched from the network is stored in
+ <file>/var/cache/apt/archives</file> (and the <file>partial/</file>
+ subdirectory, during download), so you must make sure you have enough space
+ on the file system 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
+ file system partitions in order to both install upgraded packages (which
might contain bigger binaries or more data) and new packages that will be pulled
in for the upgrade. If your system does not have sufficient space you
might end up with an incomplete upgrade that might be difficult to
@@ -1343,12 +1431,9 @@
<list>
<!-- JFS: Does aptitude to 'apt-get autoclean' by itself? -->
<item>Remove packages that have been previously downloaded for
- installation (at <file>/var/cache/apt/archive</file>), cleaning up the
- package cache by running <prgn>apt-get autoclean</prgn> or
- <prgn>aptitude autoclean</prgn> will remove unused package files. If
- that does not give you enough space, you can clean up the package cache
- further by running <prgn>apt-get clean</prgn> or <prgn>aptitude
- clean</prgn>.
+ installation (at <file>/var/cache/apt/archive</file>). Cleaning up the
+ package cache by running <prgn>apt-get clean</prgn> or <prgn>aptitude
+ clean</prgn> will remove all previously downloaded package files.
<!-- JFS Point to http://www.enricozini.org/blog/eng/pkgsizestat.html ?
Enrico's script shows files that occupy space in a given partition
@@ -1360,7 +1445,7 @@
system that occupy the most space. You can also use <prgn/deborphan/
or <prgn/debfoster/ to find obsolete packages (see
<ref id="obsolete">).
- Alternatively you can start <prgn/aptitude/ into "visual mode" and find
+ Alternatively you can start <prgn/aptitude/ in "visual mode" and find
obsolete packages under "Obsolete and Locally Created Packages".
<item>Remove packages taking up too much space, which are not currently
@@ -1392,22 +1477,23 @@
<sect1 id="minimal_upgrade"><heading>Minimal system upgrade</heading>
- <p>Before you start the full upgrade you have to make a minimal system upgrade
- to ensure you have the basic system libraries upgraded.</p>
+ <p>Because of certain necessary package conflicts between &oldreleasename;
+ and &releasename;, running <tt>aptitude dist-upgrade</tt> directly will
+ often remove large numbers of packages that you will want to keep. We
+ therefore recommend a two-part upgrade process, first a minimal upgrade to
+ overcome these conflicts, then a full <tt>dist-upgrade</tt>.
+ </p>
- <p>First run:
+ <p>First, run:
<example>
# aptitude upgrade
</example>
</p>
- <p>This will upgrade a number of packages, including <package/base-files/,
- <package/console-common/, and <package/debconf/. You will be asked information
- about your console keymap as well as the default level and frontend for
- package configuration questions.</p>
-
- <p>You have to follow the minimal upgrade with:
+ <p>This has the effect of upgrading those packages which can be upgraded
+ without requiring any other packages to be removed or installed.</p>
+ <p>Follow the minimal upgrade with:
<example>
# aptitude install initrd-tools
</example></p>
@@ -1415,67 +1501,134 @@
<p>This step will automatically upgrade <package/libc6/ and
<package/locales/ and will pull in SELinux support libraries
(<package/libselinux1/). At this point, some running services will be
- restarted, including <prgn/xdm/, <prgn/gdm/ and <prgn/kdm/, as a
- consequence local X11 sessions will be disconnected.</p>
+ restarted, including <prgn/xdm/, <prgn/gdm/ and <prgn/kdm/. As a
+ consequence, local X11 sessions will be disconnected.</p>
- <p>The following step depends on your system configuration:
+ <p>The next step will vary depending on the set of packages that you have
+ installed. These release notes give general advice about which method
+ should be used, but if in doubt, it is recommended that you examine the
+ package removals proposed by each method before proceeding.</p>
+ <p>Some common packages that are expected to be removed include
+ <package/base-config/, <package/hotplug/, <package/xlibs/,
+ <package/netkit-inetd/, <package/python2.3/, <package/xfree86-common/,
+ and <package/xserver-common/. For a more complete list of packages
+ obsoleted in &releasename;, see <ref id="obsolete">.
+ </p>
- <p><list>
- <item><p>If you are running a system with a Desktop environment, you first
- have to verify if you have <package/libfam0c102/ and <package/xlibmesa-glu/
- installed. You have them installed if you have selected &oldreleasename;'s
- Desktop task but if you have a custom-made environment you have to manually
- verify it:
+ <sect2 id="minimal_upgrade_desktop"><heading>Upgrading a desktop system</heading>
+ <p>This upgrade path has been verified to work on systems with the sarge
+ <tt>desktop</tt> task installed. It is probably the method that will give
+ the best results on systems with the <tt>desktop</tt> task installed, or
+ with the <tt>gnome</tt> or <tt>kde</tt> packages installed.
+
+ <p>It is probably <em>not</em> the correct method to use if you do not
+ already have the <package/libfam0c102/ and <package/xlibmesa-glu/ packages
+ installed:
<example>
-# dpkg -l "libfam*" | grep ^ii
-# dpkg -l "xlibmesa-glu*" | grep ^ii
+# dpkg -l libfam0c102 | grep ^ii
+# dpkg -l xlibmesa-glu | grep ^ii
</example>
+ </p>
- If you have them installed then you have to install the latest
- versions from &releasename;. The following command will install both,
- if you have only one of them you should remove the other:
+ <p>If you do have a full desktop system installed, run:
+ <example>
+# aptitude install libfam0 xlibmesa-glu
+ </example></p>
+
+ </sect2>
+
+ <sect2 id="minimal_upgrade_x_server"><heading>Upgrading a system with some X packages installed</heading>
+ <p>Systems with some X packages installed, but not the full
+ <tt>desktop</tt> task, require a different method. This method applies in
+ general to systems with <package/xfree86-common/ installed, including some
+ server systems which have <package/tasksel/ server tasks installed as some
+ of these tasks include graphical management tools. It is likely the
+ correct method to use on systems which run X, but do not have the full
+ <tt>desktop</tt> task installed.
+ <example>
+# dpkg -l xfree86-common | grep ^ii
+ </example>
+ </p>
+ <p>First, check whether you have the <package/libfam0c102/ and
+ <package/xlibmesa-glu/ packages installed.
<example>
-# aptitude install libfam0 xlibmesa-glu
- </example></p>
+# dpkg -l libfam0c102 | grep ^ii
+# dpkg -l xlibmesa-glu | grep ^ii
+ </example>
+ </p>
- <p>Note that doing this will also install the File Alteration Monitor
+ <p>If you do not have <package/libfam0c102/ installed, do not include
+ <package/libfam0/ in the following commandline. If you do not have
+ <package/xlibmesa-glu/ installed, do not include it in the following
+ commandline.
+ <footnote>This command will determine whether you need libfam0 and
+ xlibmesa-glu installed, and auto-select them for you:
+ <example>
+# aptitude install x11-common \
+ $(dpkg-query --showformat '${Package} ${Status}\n' -W libfam0c102 xlibmesa-glu \
+ | grep 'ok installed$' | sed -e's/ .*//; s/c102//')
+ </example>
+ </footnote>
+
+ <example>
+# aptitude install x11-common <var>libfam0</var> <var>xlibmesa-glu</var>
+ </example>
+ </p>
+
+ <p>Note that installing <package/libfam0/ will also install the File Alteration Monitor
(<package/fam/) as well as the RPC portmapper (<package/portmap/) if
not already available in your system. Both packages will enable a new
network service in the system although they can both be configured to
be bound to the (internal) loopback network device.</p>
+ </sect2>
- <item><p>For all other systems, verify if you have any
- X Window System packages installed by running the following command:
- <example>
-# dpkg -l "xfree86-common*" | grep ^ii
- </example>
+ <sect2 id="minimal_upgrade_server"><heading>Upgrading a system with no X support installed</heading>
+ <p>On a system with no X, no additional aptitude install command should be
+ required, and you can move on to the next step.
+ </p>
- Notice that if you selected some server tasks in &oldreleasename; you
- might have parts of it installed. If you have the X Window System
- installed you will need to upgrade to the latest version in
- &releasename;:
+ </sect2>
+
+ </sect1>
+ <sect1 id="upgrading_kernel"><heading>Upgrading the kernel</heading>
+
+ <p>The <package/udev/ version in &releasename; does not support kernel
+ versions earlier than 2.6.15 (which includes &oldreleasename; 2.6.8
+ kernels), and the <package/udev/ version in &oldreleasename; will not work
+ properly with the latest kernels. In addition, installing the
+ &releasename; version of <package/udev/ will force the removal of
+ <package/hotplug/, used by Linux 2.4 kernels.</p>
+
+ <p>As a consequence, the previous kernel package will probably not boot
+ properly after this upgrade. Similarly, there is a time window during
+ the upgrade in which <package/udev/ has been upgraded but the latest kernel
+ has not been installed. If the system were to be rebooted at this point,
+ in the middle of the upgrade, it might not be bootable because of
+ drivers not being properly detected and loaded. (See <ref
+ id="upgrade_preparations"> for recommendations on preparing for this
+ possibility if you are upgrading remotely.)</p>
+
+ <p>Unless your system has the <tt>desktop</tt> task installed, or
+ other packages that would cause an unacceptable number of package
+ removals, it is therefore recommended that you upgrade the kernel on its
+ own at this point.</p>
+
+ <p>To proceed with this kernel upgrade, run:
<example>
-# aptitude install x11-common
+# aptitude install linux-image-2.6-<var>flavor</var>
</example>
- <p>If you are running a server system, with no X packages
- installed, you do not need to do any additional installation steps.
- </p>
-
- </list></p>
+ See <ref id="kernel-metapackage"> for help in determining which flavor of
+ kernel package you should install.</p>
- <p>Note: After this minimal upgrade has finished you might want to
- consider upgrading the kernel before upgrading the full system,
- as described in <ref id="newkernel">.
- Doing so reduces the timeframe in which the system will not
- properly boot if rebooted accidentally.
- This is because the full upgrade described in the next section will
- install a new version of <prgn/udev/ and will remove <prgn/hotplug/.
- This might not be an option for systems with a Desktop environment,
- as large parts of the system will be removed if you do the kernel
- upgrade here.</p>
+ <p>In the desktop case, it is unfortunately not possible to ensure the
+ new kernel package is installed immediately after the new <package/udev/
+ is installed, so there is a window of unknown length when your system
+ will have no kernel installed with full hotplug support. See <ref
+ id="newkernel"> for information on configuring your system to not depend
+ on hotplug for booting.</p>
</sect1>
@@ -1511,9 +1664,35 @@
</sect1>
+<!-- JFS: Bug #403496 -->
+ <sect1 id="get_signatures"><heading>Getting package signatures</heading>
+
+ <p>After the upgrade, with the new version of <prgn/apt/ you can now
+ update your package information, which will include the new package
+ signature checking mechanism:</p>
+ <p><example>
+# aptitude update
+ </example></p>
+
+ <p>The upgrade will have already retrieved and enabled the signing
+ keys for Debian's package archives. If you add other (unofficial)
+ package sources, <prgn/apt/ will print warnings related to its
+ inability to confirm that packages downloaded from them are
+ legitimate and have not been tampered with. For more information
+ please see <ref id="pkgmgmt">.
+ </p>
+
+<!-- JFS: Bug #376158 -->
+ <p>You will notice that, since you are using the new version of
+ <prgn/apt/, it will download package differences files (<tt/pdiff/)
+ instead of the full package index list. For more information on this
+ feature please read <ref id="apt-pdiff">.</p>
+
+ </sect1>
+
<sect1 id="trouble"><heading>Possible issues during upgrade</heading>
- <p>If an operation using <prgn/aptitude/, <prgn/apt-get/ or
+ <p>If an operation using <prgn/aptitude/, <prgn/apt-get/, or
<prgn/dpkg/ fails with the error
<example>
E: Dynamic MMap ran out of room
@@ -1529,7 +1708,10 @@
</example>
This assumes that you do not yet have this variable set in that file.</p>
- <p>Sometimes it's necessary to enable APT::Force-LoopBreak option
+<!-- (vorlon) FIXME: I recommend dropping this paragraph, it doesn't seem relevant
+ for sarge->etch?
+-->
+ <p>Sometimes it's necessary to enable the <tt/APT::Force-LoopBreak/ option
in APT to be able to temporarily remove an essential package due
to a Conflicts/Pre-Depends loop. <prgn/aptitude/ will alert you of
this and abort the upgrade. You can work around that by specifying
@@ -1564,8 +1746,8 @@
backports installed. A file conflict will result in an error like:
<example>
-Unpacking <var><package-name></var> (from <var><package-foo></var>) ...
-dpkg: error processing <var><package-name-for-foo></var> (--install):
+Unpacking <var><package-foo></var> (from <var><package-foo-file></var>) ...
+dpkg: error processing <var><package-foo></var> (--install):
trying to overwrite `<var><some-file-name></var>',
which is also in package <var><package-bar></var>
dpkg-deb: subprocess paste killed by signal (Broken pipe)
@@ -1595,7 +1777,7 @@
extension.</p>
<p>If you're not sure what to do, write down the name of the
- package or file, and sort things out at a later time. You can
+ package or file and sort things out at a later time. You can
search in the typescript file to review the information that
was on the screen during the upgrade.</p>
@@ -1619,7 +1801,7 @@
<ref id="upgrade-to-2.6"> carefully.</p>
]]>
- <sect1><heading>Installing the kernel metapackage</heading>
+ <sect1 id="kernel-metapackage"><heading>Installing the kernel metapackage</heading>
<p>When you dist-upgrade from &oldreleasename; to &releasename;,
it is strongly recommended that you install a new
linux-image-2.6-* metapackage.
@@ -1672,41 +1854,18 @@
of the system packages (as described in <ref id="upgradingpackages">).
</p>
- <p>Take into account that the <prgn/udev/ version in &releasename; does
- not support kernel versions earlier than 2.6.15 (which includes
- &oldreleasename; 2.6.8 kernels). Conversely the <prgn/udev/ version in
- &oldreleasename; will not work properly with the latest kernels.
- As a consequence, the previous kernel package will probably not boot
- properly after this upgrade. Similarly, there is a time window through
- the upgrade in which <prgn/udev/ has been upgraded but not the
- latest kernel. If the system were to be rebooted at this point,
- in the middle of the upgrade, it might not be bootable.</p>
-
-<!-- JFS: Bug #413458, #413311, aka coreutils dependency
- not mentioned - fixed in 2.6.18.dfsg.1-12, entered testing already -->
- <p>Consequently, you might want to upgrade to the latest kernel
- before doing the full upgrade. Before you can upgrade to the 2.6
- series kernel available in &releasename; you will have to
- upgrade to the latest version of <package/initrd-tools/.
- To upgrade the kernel before the upgrade, take
- all the steps up to and including the steps related to the a minimal
- upgrade of the system, as described in <ref id="minimal_upgrade">.
- Once the package <package/initrd-tools/ has been upgraded after those steps,
- you can do the following (changing the kernel package name to the one most
- suited to your system by substituting <em><flavor></em>):
- <example>
-# aptitude install linux-image-2.6-<flavor>
- </example>
+ <p>If possible, it is to your advantage to upgrade the kernel package
+ separately from the main <tt/dist-upgrade/ to reduce the chances of a
+ temporarily non-bootable system. See <ref id="upgrading_kernel"> for a
+ description of this process. Note that this should only be done after the
+ minimal upgrade process described in <ref id="minimal_upgrade">.
</p>
- <p>This step will also update <package/libc6/, install <prgn/udev/, and
- remove <package/base-config/ and <package/hotplug/.</p>
-
<p>You can also take this step if you are using your own custom
kernel and want to use the kernel available in &releasename;.
- If your kernel version is not supported by <prgn/udev/ then
- it is recommended you upgrade after the minimal upgrade.
- If your version is supported by <prgn/udev/ you can safely wait
+ If your kernel version is not supported by <package/udev/ then
+ it is recommended that you upgrade after the minimal upgrade.
+ If your version is supported by <package/udev/ you can safely wait
until after the full system upgrade.</p>
<!--
@@ -1760,18 +1919,18 @@
will also get a new interface name.</p>
<p>For network devices, you can avoid this reordering by using
- <prgn>udev</prgn> rules, more specifically, through the definitions at
+ <package>udev</package> rules, more specifically, through the definitions at
<file>/etc/udev/rules.d/z25_persistent-net.rules</file><footnote>
The rules there are automatically generated by the script
<file>/etc/udev/rules.d/z45_persistent-net-generator.rules</file> to
have persistent names for network interfaces. Delete this symlink to
- disable persistent device naming for NICs by <prgn/udev/.</footnote>.
+ disable persistent device naming for NICs by <package/udev/.</footnote>.
Alternatively you can use 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.
- The two alternatives (<prgn>udev</prgn> and <prgn>ifrename</prgn>)
+ The two alternatives (<package>udev</package> and <prgn>ifrename</prgn>)
should not be used at the same time.
</p>
@@ -1805,7 +1964,7 @@
<p>You will then need to regenerate your initramfs image(s) by
executing <tt>update-initramfs -u -k all</tt>.</p>
- <p>Once you are running a &releasename; kernel and <prgn/udev/, you may
+ <p>Once you are running a &releasename; kernel and <package/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>
@@ -1873,16 +2032,16 @@
that should be taken care of <em/before/ the next reboot.</p>
<sect1 id="convert-devfs"><heading>Converting from devfs</heading>
- <p>Debian kernels no longer include support for <prgn>devfs</prgn>,
- so <prgn>devfs</prgn> users will need to convert their systems
+ <p>Debian kernels no longer include support for <tt>devfs</tt>,
+ so <tt>devfs</tt> users will need to convert their systems
manually before booting 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>
+ you are most likely using <tt>devfs</tt>.
+ Any config files that reference <tt>devfs</tt>-style names will need to be
+ adjusted to use <package>udev</package>-style names. Files that are likely to
+ refer to <tt>devfs</tt>-style device names include <file>/etc/fstab</file>,
+ <file>/etc/lilo.conf</file>, <file>/boot/grub/menu.lst</file>, and <file>/etc/inittab</file>.</p>
<p>More information about potential issues is available in bug report
<url id="http://bugs.debian.org/341152" name="#341152">.</p>
@@ -1895,7 +2054,7 @@
include drivers for disk controllers in the initrd. If a driver is
not included in the initrd, your system may fail to boot.
<p>If your system uses the <tt/esp/ or <tt/qlogicpti/ module to
- access your hard disks, you will need that module in
+ access your hard disks, you will need to include that module in
<file>/etc/initramfs-tools/modules</file> and regenerate the initrd
before you reboot your system. The initrd can be regenerated using:
<example>
@@ -1910,12 +2069,13 @@
include drivers for disk controllers in the initrd. If a driver is
not included in the initrd, your system may fail to boot.
<p>If your system uses the <tt/lasi700/ or <tt/zalon7xx/ module to
- access your hard disks, you will need that module in
+ access your hard disks, you will need to include that module in
<file>/etc/initramfs-tools/modules</file> and regenerate the initrd
before you reboot your system. The initrd can be regenerated using:
<example>
# update-initramfs -u -k all
</example></p>
+ </sect1>
]]>
<![ %i386-amd64 [
@@ -1936,9 +2096,9 @@
bootloader will always be rerun after a kernel upgrade.
</p>
- <p>If you encounter any issues when running <prgn/lilo/ review the
+ <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>initrd</file> and 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
@@ -1950,8 +2110,12 @@
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
+ more information on how to do this please review the Debian Installer's
+ Manual chapter <url
+ id="http://www.debian.org/releases/etch/i386/ch08s07.html"
+ name="Recovering a Broken System"> and the
+ <url
+ id="http://wiki.debian.org/DebianInstaller/FAQ" name="Debian Installer
FAQ">.</p>
</sect1>
@@ -2055,7 +2219,7 @@
and for qeth: <tt/QETH_PORTNAME/, <tt/QETH_PORTNO/ and <tt/QETH_OPTIONS/.
</p>
<p>As network devices on S/390 do not have a stable MAC address, it is
- not possible to use <prgn/udev/ persistent device naming. Instead you
+ not possible to use <package/udev/ persistent device naming. Instead you
can add an option <tt/INTERFACE_NAME/ in the configuration file to
rename an interface.</p>
@@ -2139,6 +2303,9 @@
suitable for &releasename; due to bugs in them. In the latter case,
packages might still be present in the "unstable" distribution.</p>
+<!-- (vorlon) FIXME: not true in etch because 'Obsolete and Locally Created
+ Packages' is not the default view AFAICS?
+-->
<p>Detecting which packages in an updated system are "obsolete" is
easy since the package management front-ends will mark them as
such. If you are using <prgn>aptitude</prgn>, you will see a
@@ -2154,6 +2321,7 @@
that you manually installed, as opposed to those that were
automatically installed through dependencies.</p>
+<!-- (vorlon) FIXME: AIUI, cruft is not useful for this? -->
<p>There are additional tools you can use to find obsolete packages
such as <prgn>deborphan</prgn>, <prgn>debfoster</prgn> or
<prgn>cruft</prgn>. <prgn>deborphan</prgn> is highly recommended,
@@ -2207,9 +2375,9 @@
<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,
+ <p>Sometimes, changes have side-effects we cannot reasonably avoid,
or we expose bugs somewhere else.
We document here the issues we are aware of.
Please also read the errata, the relevant packages' documentation,
@@ -2228,7 +2396,19 @@
for further information.</p>
</sect1>
- <sect1 id="window-scaling"><heading>Certain networking site cannot be reached by TCP</heading>
+<![ %defaulted-2.4 [
+ <sect1 id="incompatible-2.4">
+ <heading>Some applications may no longer work with a 2.4 kernel</heading>
+ <p>Some applications in &releasename; may no longer work with a 2.4
+ kernel, for example because they require <tt/epoll()/ support, which
+ is not available in 2.4 kernels. Such applications may either not
+ work at all or not work correctly until the system has been rebooted
+ with a 2.6 kernel.</p>
+ <p>One example is the HTTP proxy <package/squid/.</p>
+ </sect1>
+]]>
+
+ <sect1 id="window-scaling"><heading>Certain network sites cannot be reached by TCP</heading>
<p>
Since 2.6.17, Linux aggressively uses TCP window scaling which is specified in RFC 1323.
Some servers have a broken behavior, and announce wrong
@@ -2253,14 +2433,27 @@
</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>
+<!-- JFS: Bug #376158 -->
+ <sect1 id="apt-pdiff"><heading>Slower updates of APT package index files</heading>
+ <p>By default, the &releasename version of <prgn>apt</prgn> uses a
+ new way to update APT package
+ index files (when you run <tt/aptitude update/) which downloads differences
+ files (instead of the full package index file) called <tt/pdiff/. This new
+ feature should use less bandwidth and be faster for most systems.
+ Unfortunately, it can also have the opposite effect of making the updates
+ slower on systems with fast network connections (or a very nearby
+ mirror) which are infrequently updated, as it might take more time
+ for the system to merge the differences files than to download a
+ full package index. It is possible to disable this feature by adding
+ <tt>Acquire::Pdiffs "false";</tt> to the
+ <file>/etc/apt/apt.conf</file> configuration file.</p>
+<!-- For more info, see thread "These new diffs are great, but...", d-devel, july 2006 -->
+
+ <p>This change mostly affects users of the <em/unstable/ and
+ <em/testing/ branch of &debian;, due to the changing nature of these
+ archives. Users of &releasename; will notice this
+ feature mainly when updating their package status for the security
+ archive.</p>
</sect1>
<![ %i386 [
@@ -2288,8 +2481,41 @@
</sect1>
]]>
- </sect>
+ <sect1 id="asynchronous-network-start"><heading>Asynchronous network initialization may cause unpredictable behavior</heading>
+ <p>On systems which use <package/udev/ to load drivers for network
+ interfaces, it is possible due to the asynchronous nature of
+ <package/udev/ that the network driver will not be loaded before
+ <prgn>/etc/init.d/networking</prgn> runs on system boot. Although
+ including <tt/allow-hotplug/ to <file>/etc/network/interfaces</file> (in
+ addition to <tt/auto/) will ensure that the network interface is enabled
+ once it becomes available, there is no guarantee that this will finish
+ before the boot sequence begins to start network services, some of which
+ may not behave correctly in the absence of the network interface.</p>
+
+ </sect1>
+
+<![ %not-s390 [
+ <sect1 id="wpa"><heading>Trouble when using WPA secured wireless networks</heading>
+ <p>In &oldreleasename;, the <package/wpasupplicant/ package was
+ set up as a system service, configured via
+ <file>/etc/default/wpasupplicant</file> and a user-provided
+ <file>/etc/wpasupplicant.conf</file>.</p>
+ <p>In &releasename;, <file>/etc/init.d/wpasupplicant</file> has been
+ dropped and the Debian package now integrates with
+ <file>/etc/network/interfaces</file>, similar to other packages such as
+ <package/wireless-tools/. This means <package/wpasupplicant/ no longer
+ provides a system service directly.</p>
+
+ <p>For information on configuring wpasupplicant please refer to
+ <file>/usr/share/doc/wpasupplicant/README.modes.gz</file>, which gives
+ examples for <file>/etc/network/interfaces</file> files. Updated
+ information about the usage of the <package/wpasupplicant/ package
+ in Debian can be found in the <url id="http://wiki.debian.org/WPA"
+ name="Debian Wiki">.</p>
+ </sect1>
+ </sect>
+]]>
<!-- Controversial, disabled for now, please translate though
<sect id="german-quotes"><heading>Problems with German Quotes</heading>
@@ -2359,11 +2585,11 @@
<file>/etc/fstab</file> and bootloader configuration accordingly.
Unless these changes are made correctly, your system may not boot
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>
+ to mount the root file system and will abort with an error <em>waiting for root file system</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>
+ identify the newly assigned device names in the kernel boot messages or by reviewing
+ the contents of <file>/dev/disk/</file>.</footnote>.</p>
]]>
<!-- Bug: #416720 -->
@@ -2384,7 +2610,7 @@
bootloader configuration has entries for both the new kernel and
the old, working 2.4 kernel. You should also ensure you have a "rescue"
floppy or CD-ROM to hand, in case misconfiguration of the bootloader
- prevents you booting the old kernel.</p>
+ prevents you from booting the old kernel.</p>
<![ %not-s390 [
<sect1 id="2.6-keyboard">
@@ -2436,6 +2662,7 @@
</sect1>
+<!-- FIXME: should be udev now? (vorlon) -->
<sect1 id="2.6-sound">
<heading>Sound configuration</heading>
@@ -2471,7 +2698,7 @@
but in some cases manual intervention may be needed.
Please remember to not run the distribution upgrade from within an
X session.</p>
-
+
<p>In case the upgrade aborts during X.Org installation, you should
check if any files are still left in <file>/usr/X11R6/bin</file>.
You can then use <tt>dpkg -S</tt> to find out which Debian package
@@ -2486,6 +2713,36 @@
</sect>
+<!-- JFS: Bug #406300 -->
+ <sect id="xorg-8bit"><heading>No support for 8-bit displays in many applications</heading>
+
+ <p>After the upgrade to the Xorg and the latest libraries, X terminals
+ which can only represent colors 8 bits depth will not work. This is
+ because the Cairo 2D vector graphics library (<package/libcairo2/)
+ doesn't have 8-bit pseudocolor support. This library is used by the GNOME
+ and Xfce desktops as well as by many desktop applications compiled
+ with the Gtk2+ toolikt, such as <package/abiword/.</p>
+
+<!-- TODO: make this arch-specific ? This applies to remote terminals, so
+ it might not make sense to make it arch-specific ... -->
+<!-- Specific models mentioned in freedeskop's BTS, might not be complete:
+ - Tektronix XP117C X terminal,
+ - NCD: 19r X11, 256 color X terminal
+ - IBM: Netstation
+ - SUN: Ultra 10, Ultra 5, Ultra 60 (Solaris 8 with Xsun)
+ - SGI: Octane
+-->
+ <p>Known systems that are affected by this include some Sun machines and
+ X terminals from Tektronix, NCD, IBM and SGI, as well as some other
+ remote X windowing systems. You should configure these terminals to use
+ 16-bit colour, if possible.</p>
+
+ <p>More information is available
+ in Freedesktop's <url id="https://bugs.freedesktop.org/show_bug.cgi?id=4945"
+ name="bug #4945">.</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
@@ -2500,6 +2757,11 @@
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>Note that, depending on your configuration of <package/debconf/, you may not
+ be asked any configuration question during installation of <package/exim4/.
+ If no questions are asked, the system will default to a 'local delivery' setup.
+ Configuration is possible using the command <tt/dpkg-reconfigure exim4-config/.</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
@@ -2512,7 +2774,7 @@
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,
@@ -2529,6 +2791,17 @@
<p>Debian-specific changes include that the string SSL is no longer defined,
as ssl is now supported by the default package.</p>
+ <p>If you are using the experimental ITK MPM (from the
+ <package/apache2-mpm-itk/ package), the cgi module will not be correctly
+ enabled by default. To properly enable it, you will need to manually
+ disable <tt/mod_cgid/ and enable <tt/mod_cgi/:
+ <example>
+# cd /etc/apache2/mods-enabled
+# rm cgid.conf cgid.load
+# ln -s ../mods-available/cgi.load .
+# /etc/init.d/apache2 force-reload
+ </example></p>
+
</sect>
<sect id="zope"> <heading>Upgrading Zope and Plone</heading>
@@ -2549,12 +2822,40 @@
run the &oldreleasename; version in parallel to the &releasename;
version.</p>
- <p>For Zope, you may also be able to keep the old packages installed on
- your &releasename; system. For most packages this is possible as they
- use a different name space. To keep the old versions, you will need to
- package holding as documented in <ref id="package_status">. This method
- is not possible for Plone because the <package/zope-cmfplone/ package
- is not versioned.</p>
+ <p>It is not possible to have the old and new versions of Zope/Plone
+ installed together on an &releasename; system, partly because the old
+ packages depend on <package/python2.3/ which cannot be installed
+ together with <package/python2.4/.</p>
+ </sect>
+
+ <sect id="tar"> <heading>Wildcard expansion (globbing) with GNU tar</heading>
+ <p>Previous versions of GNU <prgn/tar/ assumed shell-style globbing
+ when extracting files from or listing an archive. For example:
+ <example>
+tar xf foo.tar '*.c'
+ </example>
+ would extract all files whose names end in '.c'. This behavior was not
+ documented and was incompatible with traditional <prgn/tar/
+ implementations. Therefore, starting from version 1.15.91, GNU
+ <prgn/tar/ no longer uses globbing by default. For example, the above
+ invocation is now interpreted as a request to extract from the archive
+ the file named '*.c'.</p>
+ <p>See <file>/usr/share/doc/tar/NEWS.gz</file> for further information.</p>
+ </sect>
+
+ <sect id="nis"><heading>NIS and Network Manager</heading>
+ <p>The version of <prgn/ypbind/ included with <package/nis/ for
+ &releasename; contains support for Network Manager. This support causes
+ <prgn/ypbind/ to disable NIS client functionality when Network Manager
+ reports that the computer is disconnected from the network. Since Network
+ Manager will usually report that the computer is disconnected when it is
+ not in use, NIS users with NIS client systems should ensure that Network
+ Manager support is disabled on those systems.</p>
+ <p>This can be done by either uninstalling the <package/network-manager/
+ package, or editing <file>/etc/default/nis</file> to add <tt/-no-dbus/ to
+ <tt/YPBINDARGS/.</p>
+ <p>The use of <tt/-no-dbus/ is the default for new installs of Debian, but
+ was not the default in previous releases.</p>
</sect>
<sect id="php-globals"> <heading>Deprecated insecure php configurations</heading>
@@ -2569,7 +2870,7 @@
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
@@ -2615,7 +2916,7 @@
<!-- 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
+ from some of the changes introduced in the default configuration in
Debian for &releasename;. In some extreme cases the GNOME desktop might
not properly handle your old configuration and might not behave properly.</p>
@@ -2626,7 +2927,7 @@
&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
+ 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>
@@ -2672,14 +2973,14 @@
<sect id="morereading"> <heading>Further reading</heading>
<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 Project (DDP), whose goal is to create high-quality
documentation for Debian users and developers. Documentation,
including the Debian Reference, Debian New Maintainers Guide, and Debian
FAQ are available, and many more. For full details of the existing resources
see the <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
+ <file>/usr/share/doc/<var>package</var></file>. This may include
copyright information, Debian specific details and any upstream
documentation.</p>
@@ -2769,7 +3070,7 @@
<p>If you can dedicate more time, you could manage a piece of the
Free Software collection within Debian. Especially helpful is if
people adopt or maintain items that people have requested for
- inclusion within Debian, the <url id="&url-wnpp;" name="Work Needing
+ inclusion within Debian. The <url id="&url-wnpp;" name="Work Needing
and Prospective Packages database"> details this information. If you
have an interest in specific groups then you may find enjoyment in
contributing to some of Debian's subprojects which include ports to
@@ -2827,7 +3128,7 @@
<p>If you have any lines starting with <tt>deb file:</tt>, you will
have to check for yourself if the location they refer to contains
- a &oldreleasename; or a &releasename; archive.</p>
+ a &oldreleasename; or an &releasename; archive.</p>
<p><strong/Important!/ Do not change any lines that begin with
<tt>deb cdrom:</tt>. Doing so would invalidate the line and you would
More information about the l10n-russian-cvs-commits
mailing list