[l10n-russian CVS] release-notes/sgml release-notes.en.sgml, 1.16,
1.17
Yuri Kozlov
yuray-guest at alioth.debian.org
Sun Apr 1 18:24:52 UTC 2007
Update of /cvsroot/l10n-russian/release-notes/sgml
In directory alioth:/tmp/cvs-serv11858/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.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- release-notes.en.sgml 1 Apr 2007 13:35:40 -0000 1.16
+++ release-notes.en.sgml 1 Apr 2007 18:24:50 -0000 1.17
@@ -302,6 +302,101 @@
</sect1>
</sect>
+ <sect id="improves_in_etch"><heading>System improvements</heading>
+
+ <p>There have been a number of changes in the distribution that will
+ benefit new installations of &releasename;, but may not be automatically
+ applied on upgrades from &oldreleasename;. This section gives an
+ overview of the most relevant changes.
+ </p>
+
+ <p><taglist>
+
+<!-- Bug #301138, fixed in etch -->
+ <tag>Priority for basic development packages lowered</tag>
+ <item><p>A number of development packages that used to be priority
+ <em/standard/ are now priority <em/optional/, which means they will
+ no longer be installed by default.
+ This includes the standard C/C++-compiler, <package>gcc</package>,
+ as well as some other software (<package>dpkg-dev</package>,
+ <package>flex</package>, <package>make</package>) and development
+ headers (<package>libc6-dev</package>,
+ <package>linux-kernel-headers</package>).</p>
+<!-- TODO: Point to the bug report for the full list of packages in case
+ users want to remove them ? -->
+ <p>If you do wish to have these packages on your system, the easiest way
+ to install them is by installing <package/build-essential/, which will
+ pull in most of them.</p>
+ </item>
+
+<!-- FIXME: Bug Manoj for a link to documentation on enabling SELinux -->
+ <tag>SELinux priority standard, but not enabled by default</tag>
+ <item><p>The packages needed for SELinux support have been
+ promoted to priority <em/standard/. This means that they will be
+ installed by default during new installations. For existing systems
+ you can install SELinux using:
+ <example>
+# aptitude install selinux-basics
+ </example></p>
+
+ <p>Note that SELinux support is not enabled by default. If you want to
+ secure your system using SELinux, you will need to enable it by adding
+ the kernel boot parameter <tt/selinux=1/. Additional information
+ can be found on the <url id="&url-wiki-selinux" name="Debian Wiki">.
+ </p></item>
+
+ <tag>New default inet superdaemon</tag>
+ <item><p>The default inet superdaemon for &releasename; is
+ <package>openbsd-inetd</package> instead of <package>netkit-inetd</package>.
+ It will not be started if no services are configured, which is the
+ default. The new default will be installed automatically on upgrading.
+ </p></item>
+
+ <tag>Default <prgn/vi/ clone changed</tag>
+ <item><p>The <prgn/vi/ clone installed by default is now a compact version
+ 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
+ <em/dir_index/ and <em/resize_inode/ enabled by default. The first
+ the so 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
+ is mounted).</p>
+ <p>Users upgrading from &oldreleasename; could consider adding the
+ <em/dir_index/ flag manually using <prgn/tune2fs/<footnote>
+ The flag <em/filetype/ should already be set on most file systems, except
+ possibly on systems installed before &oldreleasename;.
+ </footnote>; the <em/reset_inode/ flag cannot be added to an existing
+ file system. It is possible to check which flags are set for a file
+ system using <tt/dumpe2fs -h/.</p></item>
+
+<!-- TODO: Add for lenny, link to utf8-migration-tool, which is right now not
+ available for etch -->
+ <tag>Default encoding for &releasename; is UTF-8</tag>
+ <item><p>The default encoding for new &debian installations is UTF-8. A
+ number of applications will also be set up to use UTF-8 by default.</p>
+ <p>Users upgrading to &releasename; that wish to switch to UTF-8 will
+ need to reconfiguring their environment and locale definitions. The
+ system-wide default can be changed using <tt/dpkg-reconfigure locales/;
+ first select a UTF-8 locale for your language and country and then
+ set that as default. Note that switching to UTF-8 means that you will
+ probably also need to convert existing files from your previous
+ (legacy) encoding to UTF-8.</p>
+ <p>The package <package/utf8-migration-tool/ contains a tool that may
+ help the migration, however that package is only available in unstable
+ as it was not ready in time for &releasename;. Making a backup of
+ your data and configuration before using the tool is strongly
+ recommended.</p>
+ <p>Note that not some applications may not yet work correctly in a UTF-8
+ environment (mostly display issues).</p></item>
+
+ </taglist></p>
+
+ <p>The <url id="http://wiki.debian.org/Sarge2EtchUpgrade"
+ name="Debian Wiki"> has some additional information about changes between
+ &oldreleasename; and &releasename;.</p>
+
+ </sect>
</chapt>
<chapt id="installing"><heading>Installation System</heading>
@@ -447,15 +542,6 @@
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
- promoted to priority "standard". This means that they will be
- installed by default if you select the Standard task during
- installation. However, SELinux support is not enabled by default.
- 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 sets up a basic configuration for
the system's mail server which will only provide for local e-mail
@@ -487,7 +573,7 @@
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
+ Languages dropped in this release due to lack of translation
updates include Persian and Welsh.</p>
<![ %g-i [
<p>If the graphical user interface is used, an additional eleven
@@ -503,7 +589,7 @@
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
@@ -519,9 +605,11 @@
included in the stock &debian; installer or in packages themselves. This
means that selection of a language will automatically install packages
necessary for that language (dictionaries, documentation, fonts...) both
- in standard and desktop enviroments. Configuration that is no longer
+ in standard and desktop environments. Configuration that is no longer
handled automatically include the papersize configuration and some
- advanced keyboard settings on Xorg for some languages.</p></item>
+ advanced X Windows keyboard settings for some languages.</p>
+ <p>Note that language specific packages will only be installed
+ automatically if they are available during the installation.</p></item>
]]> <!-- not-s390 -->
@@ -549,69 +637,6 @@
</sect1>
</sect>
- <sect id="improves_in_etch"><heading>System improvements</heading>
-
- <p>Users installing &releasename; will benefit from some improvements
- in the &debian; operating system. Most of these improvements
- will be carried over to upgrades from &oldreleasename; but there
- are some changes that will only affect new installs:
- </p>
-
- <p><list>
-
-<!-- Bug 301138, fixed in etch -->
- <item>Development packages are now of <em>Optional</em> priority.
- This includes the standard C/C++-compiler, <package>gcc</package>, as well
- as some other software (<package>dpkg-dev</package>,
- <package>flex</package>, or <package>make</package>) and development
- headers (<package>libc6-dev</package>,
- <package>linux-kernel-headers</package>).
-<!-- TODO: Point to the bug report for the full list of packages in case
- users want to remove them ? -->
- This reduces the disk space needed for a standard installation.
- </item>
-
-<!-- TODO: Recommend users to remove unused desktop environments ? -->
- <item>There are three different tasks for Desktop environments users can
- choose from: GNOME, KDE or Xfce. An installation of the Desktop task in
- &oldreleasename; would install both GNOME and KDE.</item>
-
- <item>The default inet superdaemon is <package>openbsd-inetd</package>
- instead of <package>netkit-inetd</package>. It will not be started if no
- services are configured, which is the default.</item>
-
- <item>The variant installed for <prgn/vi/ by default is a compact version of
- <prgn/vim/ (<package/vim-tiny/) instead of <package/nvi/.
-
- <item>The &releasename; installer sets up ext2 and ext3 filesystems so
- that they have "directory indexes", a feature which speeds operations on
- directories with many files. It does this by turning on the
- <em/dir_index/ and <em/filetype/ flags when the filesystem is created.
- Users upgrading from &oldreleasename; need to set these flags manually
- with <prgn/tune2fs/.</item>
-
-<!-- TODO: Add for lenny, link to utf8-migration-tool, which is right now not
- available for etch -->
- <item>The &debian; installer will setup all localized environments using
- UTF-8 as the default encoding instead of language-specific encoding.
- Users upgrading to &releasename; will have to switch to this encoding
- by configuring their environment and locale definitions.</item>
-
- </list></p>
-
-<!-- TODO: make it conditional based on arquitecture ? -->
- <p>Additional packages are pulled in based on the system being installed on or on the user
- configuration. Users running the installer in a laptop system will
- automatically get a set of packages specific for laptops, and so will
- users configuring a localized environment. Even though these packages are
- not pulled in when upgrading from &oldreleasename; to &releasename; they
- are still available for users through <em>tasks</em>. Users wishing to
- install these tasks just need to run <prgn/aptitude/ interactively and select the
- appropiate tasks from the <em>Tasks</em> item presented in the user interface.</p>
-
- <p>For more information please see the <url id="http://wiki.debian.org/Sarge2EtchUpgrade"
- name="wiki pages"> that describe the upgrade from &oldreleasename; to &releasename;.</p>
-
<sect id="popcon"><heading>Popularity contest</heading>
<p>The installation system will again offer
@@ -742,110 +767,6 @@
<!-- TODO: surely gdm/kdm are sane? -->
</sect1>
- <sect1><heading>Review actions pending in package manager</heading>
-
- <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>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>
-
- <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>
- 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
- 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
- recover from.</p>
-
-<!-- JFS: Apt will not always abort if you do not have enough disk space.
- For reference see: #247331, #214119, #192146, #185201, #40438 and #32919 -->
-
- <p>Both <prgn/aptitude/ and <prgn/apt/ will show you detailed information
- of the disk space needed for the installation. Before executing the
- upgrade, you can see this estimate by running:
- </p>
-
- <p><example>
-# aptitude -y -s -f --with-recommends dist-upgrade
-[ ... ]
-XXX upgraded, XXX newly installed, XXX to remove and XXX not upgraded.
-Need to get xx.xMB/yyyMB of archives. After unpacking AAAMB will be used.
-Would download/install/remove packages.
-</example></p>
-
-
- <p>If you do not have enough space for the upgrade, make sure you free up
- space beforehand. You can:
- </p>
-
-<!-- JFS There are more tips at
- http://lists.debian.org/debian-user/2005/11/msg02078.html
- or
- http://www.debian-administration.org/articles/143
- but maybe that should be in the Debian Reference best and pointed from here -->
- <p>
- <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>.
-
-<!-- JFS Point to http://www.enricozini.org/blog/eng/pkgsizestat.html ?
- Enrico's script shows files that occupy space in a given partition
- which might be good for systems that are heavily partitioned -->
-
- <item>Remove old packages you no longer use. If you have
- <prgn/popularity-contest/ installed, you can use
- <prgn/popcon-largest-unused/ to list the packages you do not use in the
- 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
- obsolete packages under "Obsolete and Locally Created Packages".
-
- <item>Remove packages taking up too much space, which are not currently
- needed (you can always reinstall them after the
- upgrade). You can list the packages that take up most of the disk space
- with <prgn/dpigs/ (available in the <package/debian-goodies/ package)
- or with <prgn/wajig/ (running <tt>wajig size</tt>).
-
-<!-- TODO: consider this for lenny
-You can list packages that take up most of the disk space with
- <prgn/aptitude/ . Start <prgn/aptitude/ into "visual mode", select
- "Views" and "New Flat Package List" (this menu entry is available only
- after etch version), press "l" and enter "~i", press "S" and enter
- "~installsize", then it will give you nice list to work with. Doing
- this after partial upgrade described in <ref id="upgrading_aptitude">
- should give you access to this new feature.
--->
-
- <item>Temporarily move to another system, or permanently remove, system
- logs residing under <file>/var/log/</file>.
-
- </list></p>
- </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
@@ -869,6 +790,28 @@
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>Review actions pending in package manager</heading>
+
+ <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>
+
+ <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
+ <file/sources.list/ still points to <em/&oldreleasename/; and not to
+ <em/stable/ or <em/&releasename;/; see <ref id="old-sources">.</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 suggested 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>
+
+ </sect1>
+
<sect1><heading>Disabling APT pinning</heading>
<p>If you have configured APT to install certain packages from a
@@ -987,7 +930,7 @@
# aptitude search 'i~M <package name>'
</example></p>
</sect>
-
+
<sect id="upgrade-process"><heading>Preparing sources for APT</heading>
<p>Before starting the upgrade you must set up <package/apt/'s
@@ -1212,6 +1155,96 @@
</sect1>
+ <sect1><heading>Make sure you have sufficient space for the upgrade</heading>
+
+ <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>
+ 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
+ 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
+ recover from.</p>
+
+<!-- JFS: Apt will not always abort if you do not have enough disk space.
+ For reference see: #247331, #214119, #192146, #185201, #40438 and #32919 -->
+
+ <p>Both <prgn/aptitude/ and <prgn/apt/ will show you detailed information
+ of the disk space needed for the installation. Before executing the
+ upgrade, you can see this estimate by running:
+ </p>
+
+ <p><example>
+# aptitude -y -s -f --with-recommends dist-upgrade
+[ ... ]
+XXX upgraded, XXX newly installed, XXX to remove and XXX not upgraded.
+Need to get xx.xMB/yyyMB of archives. After unpacking AAAMB will be used.
+Would download/install/remove packages.
+ </example></p>
+
+
+ <p>If you do not have enough space for the upgrade, make sure you free up
+ space beforehand. You can:
+ </p>
+
+<!-- JFS There are more tips at
+ http://lists.debian.org/debian-user/2005/11/msg02078.html or
+ http://www.debian-administration.org/articles/143
+ but maybe that should be in the Debian Reference best and pointed from here -->
+ <p>
+ <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>.
+
+<!-- JFS Point to http://www.enricozini.org/blog/eng/pkgsizestat.html ?
+ Enrico's script shows files that occupy space in a given partition
+ which might be good for systems that are heavily partitioned -->
+
+ <item>Remove old packages you no longer use. If you have
+ <prgn/popularity-contest/ installed, you can use
+ <prgn/popcon-largest-unused/ to list the packages you do not use in the
+ 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
+ obsolete packages under "Obsolete and Locally Created Packages".
+
+ <item>Remove packages taking up too much space, which are not currently
+ needed (you can always reinstall them after the
+ upgrade). You can list the packages that take up most of the disk space
+ with <prgn/dpigs/ (available in the <package/debian-goodies/ package)
+ or with <prgn/wajig/ (running <tt>wajig size</tt>).
+
+<!-- TODO: consider this for lenny
+You can list packages that take up most of the disk space with
+ <prgn/aptitude/ . Start <prgn/aptitude/ into "visual mode", select
+ "Views" and "New Flat Package List" (this menu entry is available only
+ after etch version), press "l" and enter "~i", press "S" and enter
+ "~installsize", then it will give you nice list to work with. Doing
+ this after partial upgrade described in <ref id="upgrading_aptitude">
+ should give you access to this new feature.
+-->
+
+ <item>Temporarily move to another system, or permanently remove, system
+ logs residing under <file>/var/log/</file>.
+
+ </list></p>
+
+ <p>Note that in order to safely remove packages, it is advisable to
+ switch your <file>sources.list</file> back to &oldreleasename; as
+ described in <ref id="old-sources">.</p>
+
+ </sect1>
+
<sect1 id="minimal_upgrade"><heading>Minimal system upgrade</heading>
<p>Before you start the full upgrade you have to make a minimal system upgrade
@@ -1222,7 +1255,7 @@
# aptitude upgrade
</example>
</p>
-
+
<p>This will upgrade a number of packages, include <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
@@ -1233,13 +1266,13 @@
<example>
# aptitude install initrd-tools
</example></p>
-
+
<p>This step will automatically upgrade <package/libc6/ and
<package/locales/ and will pull in SE linux 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>
-
+
<p>The following step depends on your system configuration:
<p><list>
@@ -1458,7 +1491,7 @@
This package may be installed automatically by the dist-upgrade
process. You can verify this by running:
<!-- NOTE (jfs): Users using apt/aptitude might not have their available file
- updated so '^ii' is really unnecesary, maybe dpkg -l 'linux-image*' would be
+ updated so '^ii' is really unnecessary, maybe dpkg -l 'linux-image*' would be
better here? -->
<example>
# dpkg -l "linux-image*" | grep ^ii
@@ -1521,7 +1554,7 @@
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 (changing the kernel package name to the one most
- suited to your system by substituing <em><flavor></em>):
+ suited to your system by substituting <em><flavor></em>):
<example>
# aptitude install linux-image-2.6-<flavor>
</example>
@@ -1550,13 +1583,13 @@
<p>If you have a 2.4 kernel installed, and your system relies on
<package/hotplug/ for its hardware detection you should first upgrade
- to a 2.6 series kernel from &releasename; before attempting the upgrade. Make
+ to a 2.6 series kernel from &oldreleasename; before attempting the upgrade. Make
sure that the 2.6 series kernel boots your system and all your hardware is
properly detected before you perform the upgrade. The <package/hotplug/ package
is removed from the system (in favor of <package/udev/) when you do a full system
upgrade. If you do not do the kernel upgrade before this your system might
not boot up properly from this point on. Once you have done an upgrade
- to a the 2.6 series kernel in &releasename; you can do a kernel upgrade
+ to a the 2.6 series kernel in &oldreleasename; you can do a kernel upgrade
as described in <ref id="upgrade-from-2.6">.</p>
<p>If your system does not rely on <package/hotplug/<footnote>You can
@@ -1565,7 +1598,7 @@
to after you have done a full system upgrade, as described in <ref
id="upgrading_other">. Once your system has been upgraded
you can then do the following (changing the kernel package name to the one most
- suited to your system by substituing <em><flavor></em>):
+ suited to your system by substituting <em><flavor></em>):
<example>
# aptitude install linux-image-2.6-<flavor>
</example>
@@ -1608,20 +1641,20 @@
<![ %i386-amd64-ia64 [
<sect1><heading>Standard kernels have SMP abilities</heading>
- <p>Multiprocessor systems no longer require a *-smp flavour of the
+ <p>Multiprocessor systems no longer require a *-smp flavor of the
Linux kernel. For &arch-title;, linux-image packages without the -smp
suffix support both uniprocessor and multiprocessor systems.</p>
</sect1>
]]>
<![ %i386 [
- <sect1><heading>386 kernel flavour deprecated</heading>
- <p>Support for the 80386 sub-archicture for &arch-title; has been dropped
+ <sect1><heading>386 kernel flavor deprecated</heading>
+ <p>Support for the 80386 sub-architecture for &arch-title; has been dropped
in &releasename;. The 386 kernel flavor is no longer supported and has been
- replaced by the new 486 flavour.</p>
+ replaced by the new 486 flavor.</p>
</sect1>
]]>
-
+
<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
@@ -1724,7 +1757,7 @@
select exactly one device for console output, input, and standard
error. Then do a cold reset so the changes take
effect.</p>
-
+
<p>For the MP console, be careful to select the device with
"Acpi(HWP0002,700)/Pci(...)/Uart" in the path.</p></item>
</list></p>
@@ -1744,6 +1777,36 @@
"formal" upgrade is complete, but there are some other things
that should be taken care of <em/before/ the next reboot.</p>
+<![ %sparc [
+ <sect1 id="missingdrivers"><heading>Possible missing drivers in initrd</heading>
+ <p>The &releasename; kernels do not yet have full sysfs support for
+ the native sparc sbus. <package/initramfs-tools/ relies on this to
+ 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
+ <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>
+]]>
+
+<![ %hppa [
+ <sect1 id="missingdrivers"><heading>Possible missing drivers in initrd</heading>
+ <p>The &releasename; kernels do not yet have full sysfs support for
+ the native HP bus. <package/initramfs-tools/ relies on this to
+ 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
+ <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>
+]]>
+
<![ %i386-amd64 [
<sect1 id="rerunlilo"><heading>Rerun lilo</heading>
@@ -1825,7 +1888,7 @@
<file>/etc/network/options</file> to <file>/etc/sysctl.conf</file>.</p>
<item><p>Remove obsolete and unused packages as described in <ref
- id="obsolete">. You should review which configuratin files they use
+ id="obsolete">. You should review which configuration files they use
and consider purging the packages to remove their configuration files</p>
</list></p>
@@ -1938,8 +2001,8 @@
<sect1 id="window-scaling"><heading>Certain networking site cannot be reached by TCP</heading>
<p>
- 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
+ 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
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">
@@ -2020,7 +2083,7 @@
<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
+ &debian;. This can mean that program behavior may change between
releases of &debian;. </p>
<p><em>No changes yet reported.</em></p>
@@ -2086,7 +2149,7 @@
<p>HP Itanium systems running older firmware are incompatible with the
2.6 kernel in &releasename;. That means you should upgrade your
system to the latest firmware before upgrading your kernel. It is
- recommeded you do this before the system upgrade, as if you are
+ recommended you do this before the system upgrade, as if you are
already running a 2.6 kernel you will automatically retrieve the
latest kernel when upgrading the rest of the system (see <ref
id="upgrading_other">). Failing to do this will result in an system
@@ -2098,7 +2161,7 @@
make sure you have a recovery method. First, make sure that the
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 cdrom to hand, in case misconfiguration of the bootloader
+ floppy or CD-ROM to hand, in case misconfiguration of the bootloader
prevents you booting the old kernel.</p>
<![ %not-s390 [
@@ -2428,12 +2491,12 @@
</sect1>
<!-- TODO: Changed to OFTC -->
<sect1 id="irc">
- <heading>Internet Relay Chat</heading>
+ <heading>Internet Relay Chat</heading>
<p>Debian has an IRC channel dedicated to the support and aid of
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
+ To access the channel, point your favorite IRC client at
&debian-irc-server; and join #debian.</p>
<p>Please follow the channel guidelines, respecting other users
@@ -2441,7 +2504,7 @@
id="&url-irc-host;" name="website">.</p>
</sect1>
- </sect>
+ </sect>
<sect id="bugs">
<heading>Reporting bugs</heading>
@@ -2462,7 +2525,7 @@
needed.</p>
<p>You can submit a bug report using the program
- <package>reportbug</package> or manually using email.
+ <package>reportbug</package> or manually using email.
You can read more about the Bug Tracking System and how to use it by
reading the reference cards (available at
<file>/usr/share/doc/debian</file> if you have
More information about the l10n-russian-cvs-commits
mailing list