[l10n-russian CVS] release-notes/sgml release-notes.en.sgml, 1.3,
1.4
Yuri Kozlov
yuray-guest at alioth.debian.org
Mon Nov 6 20:19:26 CET 2006
Update of /cvsroot/l10n-russian/release-notes/sgml
In directory alioth:/tmp/cvs-serv18312/sgml
Modified Files:
release-notes.en.sgml
Log Message:
sync with upstream
Index: release-notes.en.sgml
===================================================================
RCS file: /cvsroot/l10n-russian/release-notes/sgml/release-notes.en.sgml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- release-notes.en.sgml 22 Oct 2006 10:21:13 -0000 1.3
+++ release-notes.en.sgml 6 Nov 2006 19:19:24 -0000 1.4
@@ -22,7 +22,7 @@
</titlepag>
<toc detail="sect1">
<chapt id="about"><heading>What's new in the Release Notes</heading>
-
+
<p>[The most recent version of this document is always available at
<url id="&url-release-notes;">. If your version is more than a month
old, you might wish to download the latest version.]</p>
@@ -38,7 +38,7 @@
<p>This section lists changes in the Release Notes since the original
version that was published with &debian; &release;r0. Minor textual
corrections are omitted.</p>
-
+
<p><list>
<item><p>Description of change.</p></item>
@@ -66,8 +66,8 @@
is expected to remain active and available for installation even if not a
part of this official stable release.</p>
- <p>This results in the following list of officially supported architectures
- for &debian; &releasename;:</p>
+ <p>The following are the officially supported architectures for
+ &debian; &releasename;:</p>
<p>
<list>
@@ -109,90 +109,61 @@
<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 (that is 73% of
- the number of packages in &oldreleasename;). Also, a significant number
- of packages has for various reasons been removed from the distribution.
+ has been updated: almost 6500 software packages (this is 73% of
+ of packages in &oldreleasename;). Also, a significant number
+ of packages 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>
- <p>With this release &debian; switches from XFree86 to the 7.1 release
- of XOrg, which includes support for a greater range of hardware and
- better autodetection support. It also supports Compiz, which is one
- of the first compositing window managers for the X Window System that
- is able to take advantage of OpenGL-acceleration.</p>
-
+ <p>With this release &debian; switches from XFree86 to the 7.1
+ release of XOrg, which includes support for a greater range of
+ hardware and better autodetection. This allows the use of Compiz,
+ which is one of the first compositing window managers for the X
+ Window System, 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>The &releasename; version of <prgn/aptitude/ is the preferred
- program for package management from console. It has proven to be
- better at dependency resolution than <prgn/apt-get/. <prgn/aptitude/
- supports most command line operations of <prgn/apt-get/. If you are
- still using <prgn/dselect/, you should also give <package/aptitude/
- a try as frontend for package management.</p>
-
+
+ <p><prgn/aptitude/ is the preferred program for package management
+ from console.
+ It has proven to be better at dependency resolution than <prgn/apt-get/
+ <prgn/aptitude/ supports most command line operations of <prgn/apt-get/.
+ If you are still using <prgn/dselect/, you should switch to
+ <package/aptitude/ as the official frontend for package management.</p>
+
<p>The official &debian; distribution now ships on thirteen to fifteen
binary CDs (depending on the architecture) and a similar number of
- source CDs. A DVD version of the distribution is now also available.</p>
+ source CDs. A DVD version of the distribution is also available.</p>
- <sect1 id="volatile"><heading>New service debian-volatile</heading>
+ <sect1 id="volatile"><heading>debian-volatile now an official service</heading>
- <p>There is a new service <em/debian-volatile/ allowing users to easily
+ <p>The <em/debian-volatile/ service that was introduced as an
+ unofficial service with the release of &oldreleasename, has now
+ become an official &debian; service.</p>
+
+ <p>This means that it no longer has a <tt/.debian.net/ address,
+ but now uses a <tt/.debian.org/ address. Please make sure to update
+ your <file>/etc/apt/sources.list</file> accordingly if you were
+ already using this service.</p>
+
+ <p><em/debian-volatile/ allows users to easily
update stable packages that contain information that quickly goes out
of date. Examples are a virus scanner's signatures list or a spam
- filter's pattern set. An administrator can use the "volatile.debian.net"
- archive with similar ease to the "security.debian.org" archive, and
- enjoy the use of packages with up-to-date information without the
- hassle and risks of maintaining an entire (or partial) system based
- on bleeding-edge packages. For more information and a list of mirrors,
+ filter's pattern set. For more information and a list of mirrors,
please see the archive's <url id="&url-debian-volatile"
name="web page">.</p>
-
- <p>Note that debian-volatile is <em/not/ an official Debian service.
- Use it at your own discretion.</p>
</sect1>
-
</sect>
<sect id="newinst"><heading>What's new in the installation system?</heading>
- <p>The old &debian; installation system has been replaced by a
- completely new installation system called
- <prgn>debian-installer</prgn>. The new installation system is
- modular in design and so has been developed with extensibility in
- mind. It has been fully translated into almost forty languages;
- additional translations are in progress and may be added in
- point releases for &releasename;.</p>
-
- <p>Some of the new features in the installation system include
- improved hardware detection, support for booting off USB flash devices,
- the use of <prgn>aptitude</prgn> to install packages during configuration
- of the base system, and support for the <prgn>XFS</prgn> file system,
- <prgn>RAID</prgn> and <prgn>LVM</prgn> (logical volume management).</p>
-
- <p>For full details on the new Debian installation system, users
- are advised to read the Debian Installation Guide included on the
- first CD or available from <url id="&url-install-manual;"
- name="the release pages">. The Installation Guide has been fully
- translated into eight languages and more are being worked on.
- Additional translations will be made available from the website
- when completed.</p>
-
-<![ %i386 [
- <p>For the &arch-title; architecture, a special set of installation
- floppy disk images, "speakup", is available for the blind.
- These images have a special kernel that supports braille displays.
- A complete list of supported models may be found in the brltty
- documentation. See the <url id="&url-installer;index#speakup"
- name="debian-installer release page"> for further information
- on these images.</p>
-]]>
-
<!-- FJP: Maybe a short description of available installation methods could be
added here: floppy, CD (netinst/business-card/full set), netboot,
hd-media, USB-stick. -->
+ <!-- TODO: Hhhm. Whats new in the installer ? -->
</sect>
</chapt>
@@ -200,13 +171,9 @@
<!-- TODO: Mention default usage of UTF-8 for new installs -->
<chapt id="installing"><heading>New installations</heading>
- <p>The old &debian; installation system called
- <prgn>boot-floppies</prgn> has been replaced by a new componentized and
- more powerful installation system called <prgn>debian-installer</prgn>.</p>
-
<p>The installer offers a variety of installation methods. Which methods
are available to install your system depends on your architecture.</p>
-
+
<p>If you are making a new installation of Debian, you should read
the Installation Guide, which is available on the Official CD at:
@@ -220,7 +187,8 @@
debian-installer.</p>
<![ %alpha [
- <p>The new installer can only be used to install on alpha systems which
+ <!-- TODO: Still true? -->
+ <p>The installer can only be used to install on alpha systems which
support the SRM console. Be sure to switch your system to SRM before
starting the installation. If your machine supports only the AlphaBIOS/ARC
console, you can still install &releasename; using a (minimal) &oldreleasename;
@@ -256,9 +224,9 @@
in deciding whether or not to adopt a package that no longer has a
maintainer.</p>
- <p>Information from <package/popularity-contest/ is processed anonymously. We would
- appreciate it if you install the package and allow it to participate
- in the official survey; you will thereby help improve Debian.</p>
+ <p>Information from <package/popularity-contest/ is processed anonymously.
+ We would appreciate it if you would participate in this official survey;
+ you will thereby help improve Debian.</p>
</sect>
</chapt>
@@ -295,20 +263,23 @@
<p>The upgrade process in itself does not modify anything in the
<file>/home</file> directory. However, some applications (e.g.
- Mozilla, some KDE applications) are known to overwrite existing
- user settings with new defaults when a new version of the application
- is first started by a user. As a precaution, you may want to make a
- backup of the hidden files and directories ("dotfiles") in users'
- home directories. This backup may help to restore or recreate the
- old settings. You may also want to inform users about this issue.</p>
+ parts of the Mozilla suite, and the GNOME and KDE desktop
+ environments) are known to overwrite existing user settings with new
+ defaults when a new version of the application is first started by a
+ user. As a precaution, you may want to make a backup of the hidden
+ files and directories ("dotfiles") in users' home directories. This
+ backup may help to restore or recreate the old settings. You may
+ also want to inform users about this.</p>
<p>It's wise to inform all users in advance of any upgrades you're
- planning, although users accessing your system via SSH (at least)
- shouldn't notice much during the upgrade, and may want to continue
- working. If you wish to take extra precautions, back up or unmount
- user's partitions (<file>/home</file>) before upgrading. A reboot
- will not normally be necessary, unless you plan to also upgrade
- your kernel.</p>
+ 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
+ reboot will not normally be necessary, unless you plan to also
+ upgrade your kernel.</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
@@ -321,6 +292,8 @@
upgrade, which can result in an <em/inaccessible/ system that is only
half-upgraded.</p>
+ <!-- TODO: surely gdm/kdm are sane? -->
+
<p>Any package installation operation must be run with superuser
privileges, so either login as root or use <prgn/su/ or
<prgn/sudo/ to gain the necessary access rights.</p>
@@ -331,10 +304,12 @@
<heading>Checking system status</heading>
<p>The upgrade process described in this chapter has been designed for
- upgrades from "pure" &oldreleasename; systems. It assumes your system
- has been updated to the latest point release of &oldreleasename;.
- If you have not or are unsure, follow the instructions in
- <ref id="old-upgrade">.</p>
+ upgrades from "pure" &oldreleasename; systems without 3rd party
+ packages. It may be wise to remove these packages first.</p>
+
+ <p>This procedure also assumes your system has been updated to the
+ latest point release of &oldreleasename;. If you have not done this
+ or are unsure, follow the instructions in <ref id="old-upgrade">.</p>
<sect1><heading>Disabling APT pinning</heading>
@@ -374,16 +349,16 @@
<p>It is desirable to remove any holds before upgrading. If any
package that is essential for the upgrade is on hold, the upgrade
- will fail.
-
- Note that <prgn/aptitude/ uses a different method for registering
+ will fail.</p>
+
+ <p>Note that <prgn/aptitude/ uses a different method for registering
packages that are on hold than <prgn/apt-get/ and <prgn/dselect/.
You can identify packages on hold for <prgn/aptitude/ with
-
+
<example>
# aptitude search "~ahold" | grep "^.h"
</example></p>
-
+
<p>If you want to check which packages you had on hold for
<prgn/apt-get/, you should use
<example>
@@ -392,11 +367,10 @@
<p>If you changed and recompiled a package locally, and didn't rename
it or put an epoch in the version, you must put it on hold to prevent
- it from being upgraded.
+ it from being upgraded.</p>
- The "hold" package state for <prgn/aptitude/ can be changed using
+ <p>The "hold" package state for <prgn/aptitude/ can be changed using
(replace <tt/hold/ with <tt/unhold/ to unset the "hold" state):
-
<example>
# aptitude hold <var>package_name</var>
</example>
@@ -436,7 +410,7 @@
<p>Before starting the upgrade you must set up <package/apt/'s
configuration file for package lists,
<file>/etc/apt/sources.list</file>.</p>
-
+
<p><package/apt/ will consider all packages that can be found via
any "<tt>deb</tt>" line, and install the package with the highest
version number, giving priority to the first mentioned lines (that
@@ -504,7 +478,7 @@
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>
@@ -671,7 +645,7 @@
upgraded before the rest of the system too. Reason is that it may fail
if <package/perl/ is upgraded at the same time. You can find out if it
is installed using:</p>
-
+
<p><example>
# dpkg -l doc-base
</example></p>
@@ -704,14 +678,14 @@
insert specific CDs at several points during the upgrade. You
might have to insert the same CD multiple times; this is due to
inter-related packages that have been spread out over the CDs.</p>
-
+
<p>New versions of currently installed packages that cannot be
upgraded without changing the install status of another package will
be left at their current version (displayed as "held back"). This can
be resolved by either using <prgn>aptitude</prgn> to choose these
packages for installation or by trying <tt>aptitude -f install
<var>package</var></tt>.</p>
-
+
<p>The <tt/--fix-broken/ (or just <tt/-f/) option causes
<package/apt/ to attempt to correct a system with broken
dependencies in place. <package/apt/ does not allow broken package
@@ -754,7 +728,7 @@
</example>
to eliminate some of the offending packages, or
-
+
<example>
# aptitude --fix-broken install
# dpkg --configure --pending
@@ -821,7 +795,7 @@
need to read it.</p>
<sect1 id="newkernel"><heading>Upgrading your kernel</heading>
-
+
<p>Note that the Linux kernel was <em/not/ upgraded by these
procedures. You may wish to do so yourself, either by installing one
of the <package/linux-image-*/ packages or by compiling a customized
@@ -844,7 +818,7 @@
Some issues associated with an upgrade to 2.6 are documented in
<ref id="upgrade-to-2.6">.</p>
]]>
-
+
<p>To upgrade your kernel you must first choose the kernel most
appropriate for your subarchitecture. A list of kernels available for
you to install can be found with:
@@ -852,7 +826,7 @@
<example>
# apt-cache search ^linux-image
</example></p>
-
+
<p>You should then use <tt/aptitude install/ to install it. Once
this new kernel is installed you should reboot at the next available
opportunity to get the benefit.</p>
@@ -861,7 +835,7 @@
own custom kernel on &debian;. Install the
<package>kernel-package</package> tool and read the documentation
in <file>/usr/share/doc/kernel-package</file>.</p>
-
+
</sect1>
<!-- TODO: Replace with #389099 -->
@@ -1009,7 +983,7 @@
<!-- Controversial, disabled for now, please translate though
<sect id="german-quotes"><heading>Problems with German Quotes</heading>
-
+
<p>The locales for German style languages (e.g. de_DE at euro)
unfortunately use an aesthetically unpleasing way of representing
open quotation marks. We have retained it this way in order to
@@ -1026,13 +1000,13 @@
<!-- Will be added if relevant information is written here
<sect id="syntax"><heading>Important program syntax changes</heading>
- <p>Debian attempts to avoid changing upstream packages, therefore
+ <p>Debian attempts to avoid changing upstream packages, therefore
any changes in the upstream package will be present in the version in
&debian;. This can mean that program behaviour may change between
releases of &debian;. </p>
<p><em>No changes yet reported.</em></p>
-
+
</sect>
-->
@@ -1098,12 +1072,12 @@
a different type of keyboard selected (e.g. a USB-MAC or Sun
keyboard), you will very likely end up with a non-working keyboard
after rebooting with the new 2.6 kernel.</p>
-
+
<p>If you can SSH into the box from another system, you can resolve
this issue by running <tt>dpkg-reconfigure console-data</tt>, choosing
the option "Select keymap from full list" and selecting a "pc"
keyboard.</p>
-
+
<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
@@ -1156,7 +1130,6 @@
</sect1>
]]> <!-- %not-s390 -->
-]]> <!-- %defaulted-2.4 -->
<!-- FJP: May already be covered by kernel team text
Etch Debian kernels depend on udev via initramfs-tools -->
@@ -1187,6 +1160,7 @@
</sect1>
</sect>
+]]> <!-- %defaulted-2.4 -->
</chapt>
<chapt id="moreinfo">
@@ -1201,23 +1175,23 @@
including the Debian Guide, Debian New Maintainers Guide, and Debian
FAQ are available, and many more. For full details of the resources
available 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
copyright information, Debian specific details and any upstream
documentation.</p>
-
+
</sect>
-
+
<sect id="gethelp">
<heading>Getting help</heading>
-
+
<p>There are many sources of help, advice and support for Debian
users, but these should only be considered if research into
documentation of the issue has exhausted all sources. This section
provides a short introduction into these which may be helpful for
new Debian users.</p>
-
+
<sect1 id="lists">
<heading>Mailing lists</heading>
<p>The mailing lists of most interest to Debian users are the
@@ -1230,15 +1204,15 @@
<!-- TODO: Changed to OFTC -->
<sect1 id="irc">
<heading>Internet Relay Chat</heading>
-
+
<p>Debian has an IRC channel dedicated to the support and aid of
- Debian users located on the Freenode IRC network which exists to
+ Debian users located on the OFTC IRC network which exists to
provide interactive services to peer-directed project communities.
To access the channel point your favourite IRC client at
&debian-irc-server; and join #debian.</p>
-
+
<p>Please follow the channel guidelines, respecting other users
- fully. For more information on Freenode please visit the <url
+ fully. For more information on OFTC please visit the <url
id="&url-irc-host;" name="website">.</p>
</sect1>
@@ -1246,7 +1220,7 @@
<sect id="bugs">
<heading>Reporting bugs</heading>
-
+
<p>We strive to make Debian GNU/Linux a high quality operating
system, however that does not mean that the packages we provide are
totally free of bugs.
@@ -1274,7 +1248,7 @@
<sect id="contributing">
<heading>Contributing to Debian</heading>
-
+
<p>You do not need to be an expert to contribute to Debian. By
assisting users with problems on the various user support <url
id="&url-debian-list-archives;" name="lists"> you are contributing to
@@ -1333,18 +1307,18 @@
refer to 'stable', you are effectively already "using" &releasename;.
If you have already run <tt>apt-get update</tt>, you can still get
back without problems following the procedure below.</p>
-
+
<p>If you have also already installed packages from &releasename;,
there probably is not much point in installing packages from
&oldreleasename; anymore. In that case you will have to decide for
yourself whether you want to continue or not. It is possible to
downgrade packages, but that is not covered here.</p>
-
+
<p>Open the file <file>/etc/apt/sources.list</file> with your favorite
editor (as root) and check all lines beginning with <tt>deb http:</tt>
or <tt>deb ftp:</tt> for a reference to "<tt/stable/". If you find any,
change <tt/stable/ to <tt/&oldreleasename;/.</p>
-
+
<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>
@@ -1353,7 +1327,7 @@
<tt>deb cdrom:</tt>. Doing so would invalidate the line and you would
have to run <prgn/apt-cdrom/ again. Do not be alarmed if a 'cdrom' source
line refers to "<tt/unstable/". Although confusing, this is normal.</p>
-
+
<p>If you've made any changes, save the file and execute
<example>
More information about the l10n-russian-cvs-commits
mailing list