[l10n-russian CVS] release-notes/sgml release-notes.en.sgml, 1.7,
1.8
Yuri Kozlov
yuray-guest at alioth.debian.org
Thu Mar 22 19:36:18 CET 2007
Update of /cvsroot/l10n-russian/release-notes/sgml
In directory alioth:/tmp/cvs-serv27329/sgml
Modified Files:
release-notes.en.sgml
Log Message:
up to 1.156
Index: release-notes.en.sgml
===================================================================
RCS file: /cvsroot/l10n-russian/release-notes/sgml/release-notes.en.sgml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- release-notes.en.sgml 18 Mar 2007 09:21:43 -0000 1.7
+++ release-notes.en.sgml 22 Mar 2007 18:36:16 -0000 1.8
@@ -116,14 +116,14 @@
<sect id="newdistro"><heading>What's new in the distribution?</heading>
-<!-- TODO: Numbers need to be updated -->
- <p>TODO: Update numbers</p>
+<!-- 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
- has been updated: almost 6500 software packages (this is 73% of
+ over 6200 new packages. Most of the software in the distribution
+ has been updated: over 10500 software packages (this is 67% of
all packages in &oldreleasename;). Also, a significant number
- of packages have for various reasons been removed from the distribution.
+ of packages (over 3400, 22% 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 front-ends.</p>
@@ -134,8 +134,52 @@
Window System, taking full advantage of hardware
OpenGL-acceleration for supported devices.</p>
- <p>&debian; again ships with current desktop applications. Amongst
- others it now includes GNOME 2.14, KDE 3.5 and OpenOffice.org 2.0.</p>
+ <p>&debian; again ships with several desktop applications and environments. Amongst
+ others it now includes the desktop environments GNOME 2.14<footnote>With some modules from
+ GNOME 2.16</footnote>, KDE 3.5.5a, and Xfce 4.4. Productivity applications
+ have also been upgraded, including the office suites OpenOffice.org 2.0.4a and
+ KOffice 1.6 as well as GNUcash 2.0.5, GNUmeric 1.6.3 and Abiword 2.4.6</p>
+
+ <p>Updates to other desktop applications include the upgrade of
+ Evolution 2.6.3 and Gaim 2.0. The Mozilla suite has also been updated
+ but the main programs have been renamed: <prgn>iceweasel</prgn>
+ (version 2.0.0.2) is the unbranded <prgn>Firefox</prgn> web browser
+ and <prgn/icedove/ (version 1.5) is the unbranded <prgn/Thunderbird/
+ mail client.</p>
+
+ <p>This release also includes, amongst others, the following software updates:</p>
+
+ <p><list>
+
+ <item>the GNU C library, version 2.3.6.</item>
+
+ <item>the GNU Compiler Collection 4.1 as default compiler.</item>
+
+ <item>Language interpreters: PHP 5.5, Python 2.4.</item>
+
+ <item>Server software:
+
+ <p><list>
+ <item>e-mail servers: Exim 4.63 (default email server
+ for new installations), Postfix 2.3, Courier 0.53, Cyrus 2.2.</item>
+
+<!-- TODO: Cherokee, lighttpd, and Tomcat 5 are NEW -->
+<!-- Note: No significant changes for Roxen4, Boa, and thttpd -->
+ <item>web servers: Apache 2.2, fnord 1.10</item>
+
+ <item>database servers: MySQL 5.0.32, PostgreSQL 8.1</item>
+
+ <item>the OpenSSH server, version 4.3.</item>
+
+ <item>name servers: Bind 9.3, maradns 1.2.</item>
+
+ <item>directory server: OpenLDAP 2.3</item>
+
+<!-- FIXME (JFS): List other server software? RADIUS? Streaming ? -->
+ </list></p>
+
+ </list></p>
+
<p><prgn/aptitude/ is the preferred program for package management
from console.
@@ -148,6 +192,34 @@
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
@@ -253,6 +325,12 @@
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
@@ -262,15 +340,48 @@
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 $FIXME$ languages.
+ now be installed in 47 languages using the text-based
+ installation user interface. This is six languages more
+ than in &oldreleasename;. Languages added in this release include
+ Belarusian, Esperanto, Estonian, Kurdish, Macedonian,
+ Tagalog, Vietnamese and Wolof.
+ Languages dropped in this relase due to lack of translation
+ updates include Persian and Welsh.
<![ %g-i [
- If the graphical user interface is used, an additional $FIXME$
- languages are supported.
+ If the graphical user interface is used, an additional 11
+ languages are supported. These languages can only be selected
+ using this installer as their fonts cannot be presented
+ in non-graphical environments.
]]>
+ Users that do not wish to use any local can now select
+ <em/C/ as their preferred local 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 needed be.</p></item>
]]> <!-- not-s390 -->
</taglist></p>
@@ -345,10 +456,40 @@
</sect>
]]>
+ <sect id="improves_in_etch"><heading>System improvements</heading>
+
+ <p>TODO: Document improvements which users installing etch will see but
+ not those upgrading from sarge. For more information see <url
+ id="http://wiki.debian.org/Sarge2EtchUpgrade" name="the wiki
+ pages">.</p>
+
+ <p><list>
+
+ <item>inetd: new default is OpenBSD's</item>
+
+ <item>portmap bound to loopback by default</item>
+
+ <item>mail server not listening to connections per default</item>
+
+ <item>development packages now priority optional, will not get installed (#301138)</item>
+
+ <item>new standard task in tasksel installs all standard and above</item>
+
+ <item>filesystem improvements</item>
+
+ <item>packages pulled in for laptops</item>
+
+ <item>localization-config NOT installed by d-i, needs to be run separately</item>
+
+ </list></p>
+
+ </sect>
+
<sect id="popcon"><heading>Popularity contest</heading>
- <p>Unlike for the previous release, the installation system will again offer
- to install the <package/popularity-contest/ package.</p>
+ <p>The installation system will again offer
+ 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
@@ -362,6 +503,9 @@
you will thereby help improve Debian.</p>
</sect>
+
+<!-- TODO: Mention localization config? -->
+
</chapt>
@@ -512,17 +656,13 @@
<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/,
- so preferably before starting the upgrade.
- It is recommended to upgrade to the 2.6-kernel series.
+ 2.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>
- <sect1 id="kernelorder"><heading>Upgrade your kernel or userland first?</heading>
-<!-- TODO: remove this section, it is just that one can see "needs to be done" on the normal output -->
- <p>[FIXME: Needs decision/documentation whether to upgrade userland or kernel first.]</p>
- </sect1>
-
</sect>
<sect id="system-status">
@@ -804,7 +944,7 @@
report. To start the recording, type:
<example>
-# script -a ~/upgrade-to-&releasename;.typescript
+# script -t -a ~/upgrade-to-&releasename;.typescript 2>~/upgrade-to-&releasename;.timing
</example>
or similar. Do not put the typescript file in a temporary
@@ -814,12 +954,24 @@
<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-to-&releasename;.typescript</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-to-&releasename;.timing 2>~/upgrade-to-&releasename;.typescript
+ </example>
+
+ </p>
+
<sect1 id="updating_lists"><heading>Updating the package list</heading>
<p>First the list of available packages for the new release needs to
@@ -835,6 +987,9 @@
<!-- 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
@@ -1005,12 +1160,38 @@
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: incoporate this part in this section -->
+ 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>
]]>
+ <sect1><heading>Upgrading from a 2.6 kernel</heading>
+
+<!-- JFS: Bug #413458, undeclared linux depency on coreutils' readlink's -m option -->
+ <p>If you are currently running a 2.6 series kernel from &oldreleasename;
+ you will have to upgrade to the latest version of <package/coreutils/ before
+ you upgrade to the 2.6 series kernel available in &releasename;.
+<!-- JFS: Bug #325568 -->
+ In order to do this you first have to do a minimal upgrade of the
+ system, a full upgrade of the system packages (as described in <ref
+ id="upgradingpackages">) is not an option since the <prgn/udev/
+ 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/.
@@ -1034,10 +1215,10 @@
manually before upgrading to an &releasename; kernel.</p>
<p>If you see the string 'devfs' in <file>/proc/mounts</file>,
- you are likely using <prgn>devfs</prgn>.
- Any config files that reference devfs style names will need to be
- adjusted to use udev style names. Files that are most likely to
- refer to devfs style device names include <file>/etc/fstab</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
@@ -1045,7 +1226,7 @@
</sect1>
<![ %i386-amd64-ia64 [
- <sect1><heading>Standard kernels contain SMP abilities</heading>
+ <sect1><heading>Standard kernels have SMP abilities</heading>
<p>Multiprocessor systems no longer require a *-smp flavour of the
Linux kernel. For &arch-title; linux-image packages without the -smp
suffix support both uniprocessor and multiprocessor systems.</p>
@@ -1077,7 +1258,14 @@
specific names at boot time.
<!-- TODO: add ifupdown-scripts-zg2 as well here? -->
See <manref name="ifrename" section="8"> and <manref name="iftab"
- section="5"> for more information.</p>
+ section="5"> for more information. You can also avoid this by
+ using <prgn>udev</prgn> rules, more specifically, through the
+ definitions at
+ <file>/etc/udev/rules.d/z25_persistent-net.rules</file><footnote>
+ The rules there are automatically generated to have persistent names for network
+ interfaces</footnote>. Both alternatives (<prgn>ifrename</prgn>
+ and <prgn>udev</prgn>) should not be used at the same time.
+ </p>
<!-- TODO:
*** maks: please review the initramfs stuff for accuracy - I'm going
@@ -1191,7 +1379,7 @@
<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
@@ -1207,6 +1395,43 @@
"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 &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>
+
<sect1 id="mdadm"><heading>Upgrading mdadm</heading>
<p>mdadm now needs a configuration file to assemble MD arrays (RAID)
@@ -1327,8 +1552,8 @@
<sect1 id="window-scaling"><heading>Certain networking site cannot be reached by TCP</heading>
<p>
- Since 2.6.17, Linux uses TCP window scaling which is specified in RFC 1323 in
- an aggressive way. Some servers have a broken behaviour, and announce wrong
+ 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">
@@ -1359,6 +1584,32 @@
<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>
@@ -1426,13 +1677,21 @@
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,
@@ -1461,8 +1720,8 @@
<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
- editing <file>/etc/X11/XF86Config-4</file> directly. Don't forget
+ either by running <tt>dpkg-reconfigure xserver-xorg</tt> or by
+ editing <file>/etc/X11/xorg.conf</file> directly. Don't forget
to read the documentation referred to in <ref id="nownownow">.</p>
<![ %i386 [
@@ -1527,7 +1786,9 @@
<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
@@ -1575,19 +1836,19 @@
<sect id="exim"> <heading>Upgrading from exim to exim4</heading>
<p>One of the packages that has been obsoleted by the &releasename;
- release is the Mail Transfer Agent (MTA) exim, which has been replaced
- by the completely new package exim4.</p>
+ release is the Mail Transfer Agent (MTA) <package/exim/, which has been replaced
+ by the completely new package <package/exim4/.</p>
- <p>exim (version 3.xx) has been unmaintained upstream for years, and
+ <p><prgn/exim/ (version 3.xx) has been unmaintained upstream for years, and
Debian has dropped support for that version as well. If you are still using
- exim 3.xx, please upgrade your exim installation to exim4 manually.
- Since exim4 is already part of &oldreleasename;, you can choose to do the
+ <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 exim package is not going to be upgraded and that it won't get
- security support after support for &oldreleasename; will be discontinued.</p>
+ 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 exim4 packages in Debian are extensively documented. The package's
+ <p>The <package/exim4/ packages in Debian are extensively documented. The package's
home page is <url id="http://wiki.debian.org/PkgExim4"> on the Debian Wiki, and
the README file can be found at
<url id="http://pkg-exim4.alioth.debian.org/README/README.Debian.html"> and
@@ -1595,7 +1856,7 @@
<p>The README file has a chapter about Packaging, which explains the
different package variations we offer, and it has a chapter about
- Updating from Exim 3, which will help you in doing the actual
+ Updating from <prgn/Exim/ 3, which will help you in doing the actual
transition.</p>
<!-- FIXME: update with decisions of (S)RMs might be needed -->
</sect>
@@ -1652,6 +1913,76 @@
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
+ 3.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
+ 2.14 Release Notes">.</p>
+ </sect>
+
+ <sect id="nano"> <heading>Default editor changed to nano</heading>
+ <p>The default editor for default installations in &releasename; is <package/nano/.
+ Previous Debian releases set the default editor for all users to
+ <package/vim/, in this release the default behaviour has changed and users
+ will get a more user-friendly editor.</p>
+
+ <p>Users wishing to retain the previous behaviour can either 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>
+
+ <p>Administrators that wish to change the behaviour for all users will have
+ to update the alternatives system using:
+
+ <example>
+# update-alternatives --config editor
+ </example>
+ </p>
+
+ </sect>
+
</chapt>
<chapt id="moreinfo">
@@ -1789,6 +2120,9 @@
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">
More information about the l10n-russian-cvs-commits
mailing list