[l10n-russian CVS] release-notes/sgml release-notes.en.sgml, 1.12,
1.13
Yuri Kozlov
yuray-guest at alioth.debian.org
Sat Mar 31 14:43:04 UTC 2007
Update of /cvsroot/l10n-russian/release-notes/sgml
In directory alioth:/tmp/cvs-serv3280/sgml
Modified Files:
release-notes.en.sgml
Log Message:
done 1.200
Index: release-notes.en.sgml
===================================================================
RCS file: /cvsroot/l10n-russian/release-notes/sgml/release-notes.en.sgml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- release-notes.en.sgml 29 Mar 2007 17:59:16 -0000 1.12
+++ release-notes.en.sgml 31 Mar 2007 14:43:02 -0000 1.13
@@ -36,7 +36,7 @@
<p>The most recent version of this document is always available at <url
id="&url-release-notes;">. If the version you are reading is more than a
- month old<footnote>On front page's of the PDF version and in the footer
+ month old<footnote>On front page of the PDF version and in the footer
of the online, HTML, version</footnote>, you might wish to obtain the
latest version.</p>
@@ -302,9 +302,55 @@
</sect1>
</sect>
- <sect id="inst-new"><heading>What's new in the installation system?</heading>
+ </chapt>
+
+ <chapt id="installing"><heading>Installation System</heading>
+
+ <p>The Debian Installer is the official installation system for Debian.
+ It offers a variety of installation methods. Which methods
+ are available to install your system depends on your architecture.</p>
+
+ <p>Images of the installer for &releasename; and the Installation Guide
+ can be found on the <url id="&url-installer;" name="Debian website">.</p>
+
+ <p>The Installation Guide is also included on the first CD/DVD of the
+ official Debian CD/DVD sets, at:
+
+ <example>
+/doc/install/manual/<var>language</var>/index.html
+ </example></p>
+
+ <p>You may also want to check the <url id="&url-installer;index#errata"
+ name="errata"> for debian-installer for a list of known issues.</p>
+
+<![ %alpha [
+ <!-- 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;
+ installation and a subsequent upgrade. For more information about the
+ different consoles please read the references on the
+ <url id="http://www.debian.org/ports/alpha" name="Debian alpha port web pages">.
+ </p>
+]]>
+
+<![ %sparc [
+ <sect id="sparc_fb"><heading>Issues with framebuffer on &arch-title;</heading>
+
+ <p>Because of display problems on some systems, framebuffer support is
+ disabled by default for &arch-title; for most graphics cards. This can
+ result in ugly display on systems that do properly support the framebuffer.
+ If you see display problems in the installer, you can try booting the installer
+ with the parameter <tt>framebuffer=true</tt>.
+ Please let us know if the framebuffer is not used by default, but works for
+ your hardware.</p>
+
+ </sect>
+]]>
+
+ <sect id="inst-new"><heading>What's new in the installation system?</heading>
- <!-- TODO: Hhhm. Whats new in the installer ? -->
<p>There has been a lot of development on the Debian Installer
since its first official release with &oldreleasename; resulting
in both improved hardware support and some exciting new features.</p>
@@ -347,27 +393,34 @@
will create an encrypted LVM partition that contains any other
filesystems (except <file>/boot</file>) as logical volumes.</p></item>
-<![ %i386-amd64 [
+<![ %g-i [
<tag>Graphical user interface</tag>
+<![ %i386-amd64 [
<item><p>If you prefer a graphical user interface, try booting
the installer with <tt/installgui/.</p>
- <p>The functionality of the graphical installer is almost identical
- to the regular installer, only the presentation differs. There is one
- exception: the graphical frontend does not support setting up
- encrypted partitions using random keys.</p>
- <p>Note: the graphical user interface is not available for all
- architectures.</p></item>
]]>
<![ %powerpc [
- <tag>Graphical user interface</tag>
<item><p>For &arch-title; a separate installation image using a
graphical user interface is available on an experimental basis.
It is known to work on most CHRP systems that have an ATI graphics
card, but has been insufficiently tested on &arch-title; to include
it on the normal installation CDs.</p>
<p>If you'd like to try the graphical installer, look for the
- "gtk-miniiso" image.</p></item>
+ "gtk-miniiso" image.</p>
+]]>
+
+ <p>The functionality of the graphical installer is almost identical
+ to the regular installer, only the presentation differs. There is one
+ exception: the graphical frontend does not support setting up
+ encrypted partitions using random keys.</p>
+ <p>The major advantage of the graphical user interface is that it
+ supports more languages than the regular user interface (newt).
+ Information about the graphical installer and the most important
+ differences between the graphical and regular installer are documented
+ in an appendix in the installation guide.</p>
+ <p>Note: the graphical user interface is not available for all
+ architectures.</p></item>
]]>
<tag>Rescue mode</tag>
@@ -402,7 +455,7 @@
to enable it manually after the installation.</p></item>
<tag>Simplified mail configuration</tag>
- <item><p>The installation system setups a basic configuration for
+ <item><p>The installation system sets up 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
@@ -413,12 +466,16 @@
<tag>Desktop selection</tag>
<item><p>The installation system will install
- a GNOME desktop as the default desktop if the user asks for one.
- However, users wishing to install alternate desktop environments
- can easily do so by adding boot parameters:
- <tt>tasks="standard, kde-desktop"</tt> for KDE and
- <tt>tasks="standard, xfce-desktop"</tt> for Xfce. ISO images for
- alternate desktop environments will also be available.</p></item>
+ a GNOME desktop as the default desktop if the user asks for one.</p>
+ <p>However, users wishing to install alternate desktop environments
+ can easily do so by adding boot parameters:
+ <tt>tasks="standard, kde-desktop"</tt> for KDE and
+ <tt>tasks="standard, xfce-desktop"</tt> for Xfce. Note that this
+ will not work when installing from a full CD image without using
+ a network mirror as an additional package source; it will work
+ when using a DVD image or any other installation method.</p>
+ <p>There are also separate CD images available that install the
+ KDE or Xfce desktop environment by default.</p></item>
<![ %not-s390 [
<tag>New languages</tag>
@@ -429,16 +486,16 @@
Belarusian, Esperanto, Estonian, Kurdish, Macedonian,
Tagalog, Vietnamese and Wolof.
Languages dropped in this relase due to lack of translation
- updates include Persian and Welsh.
+ updates include Persian and Welsh.</p>
<![ %g-i [
- If the graphical user interface is used, an additional eleven
+ <p>If the graphical user interface is used, an additional eleven
languages are supported. These languages can only be selected
using this installer as their character sets cannot be presented
in a non-graphical environment. The new languages are:
Bengali, Dzongkha, Gujarati, Hindi, Georgian, Khmer, Malayalam,
- Nepali, Punjabi, Tamil and Thai.
+ Nepali, Punjabi, Tamil and Thai.</p>
]]>
- Users that do not wish to use any locale can now select
+ <p>Users that do not wish to use any locale can now select
<em/C/ as their preferred locale in the installer's language
selection.
More information on language coverage is available at the
@@ -459,7 +516,7 @@
were previously handled by the <package>localization-config</package> tool are now
included in the stock &debian; installer or in packages themselves. This
means that selection of a language will automatically install packages
- necessar for that language (dictionaries, documentation, fonts...) both
+ necessary for that language (dictionaries, documentation, fonts...) both
in standard and desktop enviroments. Configuration that is no longer
handled automatically include the papersize configuration and some
advanced keyboard settings on Xorg for some languages.</p></item>
@@ -488,54 +545,7 @@
and encrypted LVM. See the documentation for details.</p>
</sect1>
- </sect>
-
- </chapt>
-
- <chapt id="installing"><heading>New installations</heading>
-
- <p>The Debian Installer is the official installation system for Debian.
- It offers a variety of installation methods. Which methods
- are available to install your system depends on your architecture.</p>
-
- <p>Images of the installer for &releasename; and the Installation Guide
- can be found on the <url id="&url-installer;" name="Debian website">.</p>
-
- <p>The Installation Guide is also included on the first CD/DVD of the
- official Debian CD/DVD sets, at:
-
- <example>
-/doc/install/manual/<var>language</var>/index.html
- </example></p>
-
- <p>You may also want to check the <url id="&url-installer;index#errata"
- name="errata"> for debian-installer for a list of known issues.</p>
-
-<![ %alpha [
- <!-- 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;
- installation and a subsequent upgrade. For more information about the
- different consoles please read the references on the
- <url id="http://www.debian.org/ports/alpha" name="Debian alpha port web pages">.
- </p>
-]]>
-
-<![ %sparc [
- <sect id="sparc_fb"><heading>Issues with framebuffer on &arch-title;</heading>
-
- <p>Because of display problems on some systems, framebuffer support is
- disabled by default for &arch-title; for most graphics cards. This can
- result in ugly display on systems that do properly support the framebuffer.
- If you see display problems in the installer, you can try booting the installer
- with the parameter <tt>framebuffer=true</tt>.
- Please let us know if the framebuffer is not used by default, but works for
- your hardware.</p>
-
</sect>
-]]>
<sect id="improves_in_etch"><heading>System improvements</heading>
@@ -575,7 +585,7 @@
that they have "directory indexes", a feature which speeds operations on
directories with many files. It does this by turning on the
<em/dir_index/ and <em/filetype/ flags when the filesystem is created.
- Users upgrading from &oldreleasename; need to set this flags manually
+ Users upgrading from &oldreleasename; need to set these flags manually
with <prgn/tune2fs/.</item>
<!-- TODO: Add for lenny, link to utf8-migration-tool, which is right now not
@@ -699,7 +709,7 @@
<sect1><heading>Prepair a safe environment for the upgrade</heading>
- <p>Distribution upgrade should be done either locally from a
+ <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>
@@ -732,12 +742,21 @@
<sect1><heading>Review actions pending in package manager</heading>
- <P>TODO</p>
+ <P>First of all, you have to review if there any actions pending 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.</p>
- <p>Run aptitude interactively and check that there are no packages
- scheduled for removal or update (if a packages was installed with
- apt-get, aptitude may sometimes not know about it and list it for
- removal; in general, the system should be up-to-date and "clean").</p>
+ <p>To do this, you have to run <prgn/aptitude/'s user interface and
+ press 'g' ("Go"). If it shows any actions, you should review them and
+ either fix them or implement the suggeted actions. If no actions are
+ suggested you will be presented with a message saying "No packages are
+ scheduled to be installed, removed, or upgraded".</p>
+
+ <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" an schedule it for removal. In general, the system should be
+ fully up-to-date and "clean".</p>
<sect1><heading>Make sure you have sufficient space for the upgrade</heading>
@@ -829,7 +848,7 @@
<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 preferable be done before starting the upgrade.
+ 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.
</p>
@@ -1425,13 +1444,13 @@
<!-- 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; this upgrade will take place after do a full upgrade
+ &oldreleasename; this upgrade will take place after you do a full upgrade
of the system packages (as described in <ref id="upgradingpackages">).
</p>
- <p>Take in account that the <prgn/udev/ version in &releasename; does
- not support kernel earlier than 2.6.15 (which includes
- &oldreleasename; 2.6.8 kernels), conversely the <prgn/udev/ version in
+ <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
@@ -1439,21 +1458,24 @@
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 #325568 -->
+<!-- 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/coreutils/ and
- <package/initrd-tools/. To upgrade the kernel before the upgrade, take
+ 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">,
- and then do the following:
+ upgrade of the system, as described in <ref id="minimal_upgrade">.
+ Once <package/initrd-tools/ have been upgraded after those steps
+ you can then do the following (substituting an appropriate kernel package
+ for your system):
<example>
-# aptitude install initrd-tools coreutils linux-image-2.6-686
+# aptitude install linux-image-2.6-686
</example>
</p>
- <p>This step will also update libc6, install <prgn/udev/ and
+ <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
@@ -1513,7 +1535,7 @@
<![ %i386-amd64-ia64 [
<sect1><heading>Standard kernels have SMP abilities</heading>
<p>Multiprocessor systems no longer require a *-smp flavour of the
- Linux kernel. For &arch-title; linux-image packages without the -smp
+ Linux kernel. For &arch-title;, linux-image packages without the -smp
suffix support both uniprocessor and multiprocessor systems.</p>
</sect1>
]]>
@@ -1529,7 +1551,7 @@
<sect1 id="device-reorder"><heading>Device enumeration reordering</heading>
<p>&releasename; features a more robust mechanism for hardware discovery
than previous releases. However, this may cause changes in the
- order devices are discovered on your system affecting the order
+ order devices are discovered on your system, affecting the order
in which device names are assigned.
For example, if you have two network adapters that are associated
with two different drivers, the devices eth0 and eth1 refer to
@@ -1642,6 +1664,7 @@
"formal" upgrade is complete, but there are some other things
that should be taken care of <em/before/ the next reboot.</p>
+<![ %i386-amd64 [
<sect1 id="rerunlilo"><heading>Rerun lilo</heading>
<p>If you are using <package/lilo/ as your bootloader (it is the
@@ -1678,6 +1701,7 @@
FAQ">.</p>
</sect1>
+]]>
<sect1 id="mdadm"><heading>Upgrading mdadm</heading>
@@ -1717,7 +1741,7 @@
no longer a Debian Developer interested in maintaining the packages;
the functionality they provide has been superseded by different
software (or a new version); or they are no longer considered
- suitable for &releasename; due to bugs in them. In the later case,
+ suitable for &releasename; due to bugs in them. In the latter case,
packages might still be present in the "unstable" distribution.</p>
<p>Detecting which packages in an updated system are "obsolete" is
@@ -2056,16 +2080,17 @@
<p>The transition to X.Org involves some structural changes. In case
all installed packages are from Debian and also included in &releasename;,
the upgrade should work without problems.
- Experience has however shown there are a few changes to be aware of as
- they can potentially cause issues during the upgrade.</p>
+ However, experience has shown that there are a few changes to be aware
+ of, as they can potentially cause issues during the upgrade.</p>
<p>The most important change is that <file>/usr/X11R6/bin</file> has
been dropped and only remains as a symlink to <file>/usr/bin</file>.
- This means this directory has to be empty at the time the new packages
+ This means the directory has to be empty at the time the new packages
are installed. The new packages conflict with most packages that used
<file>/usr/X11R6/bin</file>,
but in some cases manual intervention may be needed.
- Please remember to not run upgrades within an X session.</p>
+ 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>.
@@ -2153,9 +2178,9 @@
(rebranded in Debian to <package>iceweasel</package> and <package>icedove</package>, respectively),
are important tools for many users.
Unfortunately the upstream security policy is to urge users to update to
- new upstream versions, which conflicts with Debian's policy not to ship
+ new upstream versions, which conflicts with Debian's policy of not shipping
large functional changes in security updates.
- We cannot predict it today, but during lifetime of &releasename; the
+ We cannot predict it today, but during the lifetime of &releasename; the
Debian Security Team may come to a point where supporting
Mozilla products is no longer feasible and announce
the end of security support for Mozilla products.
@@ -2211,7 +2236,7 @@
<p>If you were using <prgn/vim/ as your default editor, this may
be changed to <prgn/nano/ during the upgrade.</p>
- <p>Administrators that wish to change the default editor for all users
+ <p>Administrators who wish to change the default editor for all users
will have to update the alternatives system using:
<example>
@@ -2242,7 +2267,7 @@
<p>Beyond these release notes and the installation guide, further
documentation on &debian; is available from the Debian
Documentation Project (DDP), whose goal is to create high quality
- documentation for Debian users and developers. Documentation
+ 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>
@@ -2302,10 +2327,10 @@
<p>If you find a bug in the distribution or in packaged software
that is part of it, please report it so that it can be properly
- fixed for next releases. Reporting bugs requires a valid email
- address, we ask for this so that we can trace bugs and developers
- can get in contact with submitters should they need more
- information.</p>
+ fixed for future releases. Reporting bugs requires a valid email
+ address. We ask for this so that we can trace bugs and developers
+ can get in contact with submitters should additional information be
+ needed.</p>
<p>You can submit a bug report using the program
<package>reportbug</package> or manually using email.
@@ -2323,11 +2348,11 @@
<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
- the community. Identifying (and importantly solving) problems
+ the community. Identifying (and also solving) problems
related to the development of the distribution by participating on
the development <url id="&url-debian-list-archives;" name="lists"> is
also extremely helpful. To maintain Debian's high quality
- distribution <url id="&url-bts;" name="submit bugs">
+ distribution, <url id="&url-bts;" name="submit bugs">
and help developers track them down and fix them. If you have a way
with words then you may want to contribute more actively by helping
to write <url id="&url-ddp;"
More information about the l10n-russian-cvs-commits
mailing list