[l10n-russian CVS] release-notes/sgml release-notes.en.sgml, 1.17,
1.18
Yuri Kozlov
yuray-guest at alioth.debian.org
Mon Apr 2 17:52:33 UTC 2007
Update of /cvsroot/l10n-russian/release-notes/sgml
In directory alioth:/tmp/cvs-serv29068/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.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- release-notes.en.sgml 1 Apr 2007 18:24:50 -0000 1.17
+++ release-notes.en.sgml 2 Apr 2007 17:52:30 -0000 1.18
@@ -27,7 +27,7 @@
of major changes in this release of the &debian; distribution, to
provide information on how to upgrade safely from the previous
release to the current release and finally to inform users of known potential
- issues users could encounter when upgrading to or using the
+ issues they could encounter when upgrading to or using the
&releasename; release.</p>
<p>Note that it is impossible to list every known issue and that
@@ -36,15 +36,15 @@
<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 of the PDF version and in the footer
- of the online, HTML, version</footnote>, you might wish to obtain the
- latest version.</p>
+ month old<footnote>as listed on the 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>
- <p>Please note that we only support
- and document upgrading from the previous release of Debian (in this case,
- the upgrade from &oldreleasename;). If you need to upgrade from older
- releases, we suggest you read previous editions of the release notes and
- upgrade to &oldreleasename; first.</p>
+ <p>Please note that we only support and document upgrading from the
+ previous release of Debian (in this case, the upgrade from
+ &oldreleasename;). If you need to upgrade from older releases, we suggest
+ you read previous editions of the release notes and upgrade to
+ &oldreleasename; first.</p>
<sect id="bug_reports"><heading>Reporting bugs on this document</heading>
@@ -52,7 +52,7 @@
described in this document and we have also tried to anticipate all
the possible issues our users might encounter.</p>
- <p>Nevertheless, If you think you have found any bug in this
+ <p>Nevertheless, if you think you have found any bug in this
documentation (incorrect information or information that is missing),
please file a bug in the <url id="&url-bts;" name="bug tracking
system"> against the <package>release-notes</package> package.</p>
@@ -89,7 +89,7 @@
<sect id="sources"><heading>Sources for this document</heading>
<p>This document uses <package>debiandocsgml</package>. Its sources
- are available in the <em>Debian Documentation Project</em>'s CVS.
+ are available in the CVS of the <em>Debian Documentation Project</em>.
You can use the <url id="&url-cvs-release-notes;" name="web
interface"> to access its files individually through the web and see
their changes. For more information on how to access the CVS please
@@ -123,7 +123,7 @@
version of this port was available.
<![ %amd64 [
Upgrading from this unofficial version should be possible using these
- Release Notes, but is not supported.
+ Release Notes, but is not officially supported by Debian.
]]>
</p>
@@ -144,7 +144,7 @@
<item><p>SPARC ('sparc')</p></item>
<item><p>PowerPC ('powerpc')</p></item>
<item><p>ARM ('arm')</p></item>
- <item><p>MIPS ('mips' (Big endian) and 'mipsel' (Little endian))</p></item>
+ <item><p>MIPS ('mips' (big-endian) and 'mipsel' (little-endian))</p></item>
<item><p>Intel Itanium ('ia64')</p></item>
<item><p>HP PA-RISC ('hppa')</p></item>
<item><p>S/390 ('s390')</p></item>
@@ -188,35 +188,39 @@
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
+ <p>With this release, &debian; switches from XFree86 to the 7.1
release of X.Org, 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>
+ OpenGL acceleration for supported devices.</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>&debian; again ships with several desktop applications and environments.
+ Among 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
+ <p>Updates of other desktop applications include the upgrade to
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>
+ with a rename of the main programs: <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>Among many others, this release also includes the following software
+ updates:</p>
<p><list>
- <item>the GNU C library, version 2.3.6.</item>
+ <item>the GNU C library, version 2.3.6</item>
- <item>the GNU Compiler Collection 4.1 as default compiler.</item>
+ <item>the GNU Compiler Collection 4.1 as default compiler</item>
- <item>language interpreters: PHP 5.5, Python 2.4.</item>
+ <item>PHP 5.5</item>
+
+ <item>language interpreters: PHP 5.2, Python 2.4</item>
<item>server software:
@@ -230,9 +234,9 @@
<item>database servers: MySQL 5.0.32, PostgreSQL 8.1</item>
- <item>the OpenSSH server, version 4.3.</item>
+ <item>the OpenSSH server, version 4.3</item>
- <item>name servers: Bind 9.3, maradns 1.2.</item>
+ <item>name servers: Bind 9.3, maradns 1.2</item>
<item>directory server: OpenLDAP 2.3</item>
@@ -242,6 +246,7 @@
</list></p>
+<!-- FIXME (vorlon): is aptitude news for etch, does it belong here? -->
<p><prgn/aptitude/ is the preferred program for package management
from console.
<prgn/aptitude/ supports most command line operations of <prgn/apt-get/
@@ -258,23 +263,23 @@
<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><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>
+ 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. Administrators of unofficial apt repositories are encouraged to
+ <p>In its default configuration, <prgn/apt/ will now warn if packages
+ are downloaded from sources that are not authenticated. Future releases
+ might force all packages to be verified before downloading them.
+ Administrators of unofficial apt repositories 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
+ <p>For more information please read <prgn>apt</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"
@@ -284,7 +289,7 @@
<sect1 id="volatile"><heading>debian-volatile now an official service</heading>
<p>The <em/debian-volatile/ service that was introduced as an
- unofficial service with the release of &oldreleasename;, has now
+ 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,
@@ -329,7 +334,6 @@
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
@@ -339,17 +343,17 @@
# 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>Note that SELinux support is <em/not/ enabled by default. Information
+ on setting up and enabling SELinux 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.
+ It will not be started if no services are configured, which is true by
+ default. The new default daemon will be installed automatically on
+ upgrade.
</p></item>
<tag>Default <prgn/vi/ clone changed</tag>
@@ -359,24 +363,24 @@
<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
+ 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
+ </footnote>; the <em/resize_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
+ <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
+ need to reconfigure 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
@@ -387,8 +391,8 @@
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>
+ <p>Note that some applications may not yet work correctly in a UTF-8
+ environment, mostly due to display issues.</p></item>
</taglist></p>
@@ -405,8 +409,9 @@
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>Images of the installer for &releasename; can be found together with the
+ Installation Guide 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:
@@ -419,14 +424,14 @@
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">.
+ console, the recommended way to install &releasename; is to first install
+ a (minimal) woody system, the upgrade to &oldreleasename; and finally to
+ &releasename;. 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>
]]>
@@ -442,6 +447,24 @@
your hardware.</p>
</sect>
+
+ <sect id="sparc_illegal_instruction"><heading>Issues with booting on &arch-title;</heading>
+
+ <p>It has been reported by several users that the installation CD
+ fails to boot successfully upon the '<tt>boot cdrom</tt>' PROM
+ command, displaying the error '<tt>Illegal Instruction</tt>'.</p>
+
+ <p>The apparent explanation for this problem is that it doesn't work
+ because the machine had previously been rebooted from Solaris.
+ The workaround is to power the machine off fully, and then boot it
+ directly into the installation CD.</p>
+
+ <p>The problem was reported by users of various systems (namely,
+ Enterprise 450, Blade 2000, Fire V240, Enterprise 250 and Blade 100
+ at the time of writing), so it is believed to be generic. Please
+ let us know if you observe similar issues with your hardware.</p>
+
+ </sect>
]]>
<sect id="inst-new"><heading>What's new in the installation system?</heading>
@@ -460,7 +483,7 @@
<p><taglist>
<tag>No reboot during the installation</tag>
- <item><p>The installation used to be split into two parts:
+ <item><p>Previously, the installation was split into two parts:
setting up the base system and making it bootable, followed
by a reboot and after that the execution of <prgn/base-config/
which would take care of things like user setup, setup of the
@@ -473,6 +496,7 @@
the correct timezone and, if you installed the Desktop environment,
will at once start the graphical user interface.</p></item>
+<!-- FIXME (vorlon): is this true for /all/ languages? -->
<tag>UTF-8 encoding default for new systems</tag>
<item><p>The installer will set up systems to use UTF-8 encoding
rather than the old language-specific encodings (like ISO-8859-1,
@@ -538,19 +562,18 @@
<tag>Cryptographic verification of downloaded packages</tag>
<item><p>Packages downloaded with the installer are
- now cryptographically checked using <prgn/secure apt/
+ now cryptographically checked using <prgn/apt/,
making it more difficult to compromise a system being
installed over the network.</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
- 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>
+ <item><p>If the "standard system" is installed, the installer sets up
+ a basic configuration for the system's mail server which will only
+ provide for local e-mail delivery. 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>
<tag>Desktop selection</tag>
<item><p>The installation system will install
@@ -573,8 +596,8 @@
than in &oldreleasename;. Languages added in this release include
Belarusian, Esperanto, Estonian, Kurdish, Macedonian,
Tagalog, Vietnamese and Wolof.
- Languages dropped in this release due to lack of translation
- updates include Persian and Welsh.</p>
+ Due to lack of translation updates, two languages have been dropped
+ in this release: Persian and Welsh.</p>
<![ %g-i [
<p>If the graphical user interface is used, an additional eleven
languages are supported. These languages can only be selected
@@ -592,7 +615,7 @@
<tag>Simplified localization and timezone selection</tag>
<item><p>Configuration of language, countries and timezones
- have been simplified to reduce the amount of information
+ has 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
@@ -604,11 +627,11 @@
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
- necessary for that language (dictionaries, documentation, fonts...) both
- in standard and desktop environments. Configuration that is no longer
- handled automatically include the papersize configuration and some
+ necessary for that language (dictionaries, documentation, fonts...) in both
+ standard and desktop environments. Configuration that is no longer
+ handled automatically includes the papersize configuration and some
advanced X Windows keyboard settings for some languages.</p>
- <p>Note that language specific packages will only be installed
+ <p>Note that language-specific packages will only be installed
automatically if they are available during the installation.</p></item>
]]> <!-- not-s390 -->
@@ -651,8 +674,8 @@
maintainer.</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>
+ We would appreciate it if you would participate in this official survey,
+ helping to improve Debian.</p>
</sect>
@@ -734,7 +757,7 @@
</sect1>
- <sect1><heading>Prepair a safe environment for the upgrade</heading>
+ <sect1><heading>Prepare a safe environment for the upgrade</heading>
<p>The distribution upgrade should be done either locally from a
textmode virtual console (or a directly connected serial
@@ -772,7 +795,7 @@
you need to upgrade to (at least) the
2.4-series before upgrading <package/glibc/.
This should preferably be done before starting the upgrade.
- It is recommended you directly upgrade to the 2.6-kernel (available
+ 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>
@@ -924,7 +947,7 @@
# aptitude unmarkauto $(dpkg-query -W 'kernel-image-2.6*' | cut -f1)
</example></p>
- <p>Note: You can review which packages are marked as <em/auto/ in aptitude running:
+ <p>Note: You can review which packages are marked as <em/auto/ in aptitude by running:
<example>
# aptitude search 'i~M <package name>'
@@ -1109,7 +1132,7 @@
report. To start the recording, type:
<example>
-# script -t -a ~/upgrade-&releasename;.script 2>~/upgrade-&releasename;.time
+# script -t 2>~/upgrade-&releasename;.time -a ~/upgrade-&releasename;.script
</example>
or similar. Do not put the typescript file in a temporary
@@ -1256,7 +1279,7 @@
</example>
</p>
- <p>This will upgrade a number of packages, include <package/base-files/,
+ <p>This will upgrade a number of packages, including <package/base-files/,
<package/console-common/, and <package/debconf/. You will be asked information
about your console keymap as well as the default level and frontend for
package configuration questions.</p>
@@ -1667,18 +1690,20 @@
ethernet adapters in a running &releasename; system, the new adapter
will also get a new interface name.</p>
- <p>For network devices, you can avoid this reordering by using the
- <prgn>ifrename</prgn> utility to bind physical devices to
- specific names at boot time.
+ <p>For network devices, you can avoid this reordering 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 by the script
+ <file>/etc/udev/rules.d/z45_persistent-net-generator.rules</file> to
+ have persistent names for network interfaces. Delete this symlink to
+ disable persistent device naming for NICs by <prgn/udev/.</footnote>.
+ Alternatively you can use the <prgn>ifrename</prgn> utility to bind
+ physical devices to specific names at boot time.
<!-- TODO: add ifupdown-scripts-zg2 as well here? -->
See <manref name="ifrename" section="8"> and <manref name="iftab"
- section="5"> for more information. 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.
+ section="5"> for more information.
+ The two alternatives (<prgn>udev</prgn> and <prgn>ifrename</prgn>)
+ should not be used at the same time.
</p>
<!-- TODO:
@@ -1692,7 +1717,8 @@
were loaded by looking at the output of <prgn/lsmod/.
<prgn/lsmod/ lists modules in the reverse order that they were loaded
in, i.e., the first module in the list was the last one
- loaded.</p>
+ loaded. Note that this will only work for devices which the kernel
+ enumerates in a stable order (like PCI devices).</p>
<p>However, removing and reloading modules after initial boot
will affect this order. Also, your kernel may have some drivers
@@ -1708,9 +1734,9 @@
example, sym53c8xx_2 has become sym53c8xx.</p>
<p>You will then need to regenerate your initramfs image(s) by
- executing <tt>update-initramfs -k all</tt>.</p>
+ executing <tt>update-initramfs -u -k all</tt>.</p>
- <p>Once you are running an &releasename; kernel and <prgn/udev/, you may
+ <p>Once you are running a &releasename; kernel and <prgn/udev/, you may
reconfigure your system to access disks by an alias that is not
dependent upon driver load order. These aliases reside in the
<file>/dev/disk/</file> hierarchy.</p>
@@ -1846,6 +1872,112 @@
</sect1>
]]>
+<![ %s390 [
+ <sect1 id="s390-config"><heading>S/390 hardware configuration</heading>
+
+ <p>Not all S/390 hardware can be configured automatically. For the
+ &releasename; kernels a new utility <package/sysconfig-hardware/ is
+ used to correctly set up devices. Unfortunately documentation for
+ this utility and its configuration files is not yet available. The
+ configuration files for <package/sysconfig-hardware/ can be found
+ under <file>/etc/sysconfig/</file>.</p>
+
+ <p>Especially if your system is currently running a 2.4 kernel,
+ getting the configuration right can be a challenge. If you need any
+ help, feel free to contact the
+ <url id="http://lists.debian.org/debian-s390"
+ name="Debian S/390 mailing list">.</p>
+
+ <p>First install the utility and regenerate the initramfs initrd as
+ the utility provides some scripts that need to be included in the
+ initrd:
+ <example>
+# aptitude install sysconfig-hardware
+# update-initramfs -u -k all
+ </example></p>
+
+ <sect2 id="s390-dasd"><heading>Configuration for disks</heading>
+
+ <p>This is done by modifying <file>/etc/zipl.conf</file>. The
+ sysconfig utility can use the device path to the root device to
+ enable it, which means that this path needs to be passed in the kernel
+ boot parameters. For a regular dasd, the path is composed as follows:
+ <example>
+<bus>-<device>
+ </example>
+
+ For the <tt/root/ parameter the partition needs to be appended to
+ the path. So if your dasda is <tt/0.0.0122/, instead of
+ <file>root=/dev/dasda1</file> you would include the following in
+ the <tt/parameters/ line in <tt>/etc/zipl.conf</tt>:
+ <example>
+root=/dev/disks/by-path/ccw-0.0.0122-part1
+ </example>
+
+ Or, alternatively you can use the <tt/enable/ parameter to specify
+ the device to be enabled; in that case the partition:
+ <example>
+root=/dev/dasda1 enable=ccw-0.0.0122
+ </example>
+
+ The paths to be used can vary for different devices. For example, for
+ disks on a zFCP fiberchannel host adapter, the path consists of bus,
+ device, driver, wwpn and lun. The parameters for a RAID1 would look
+ like (on a single line):
+ <example>
+root=/dev/md0 enable=ccw-0.0.2900-zfcp-0x21000020371c93a5:0
+enable=ccw-0.0.2900-zfcp-0x21000020371d8f94:0
+ </example></p>
+
+ <p>Other dasd devices (dasds not needed to bring up the root file
+ system are enabled through configuration files in
+ <file>/etc/sysconfig/hardware/</file>. For a regular dasd, you just
+ need to touch a file with the device path in its name:
+ <example>
+# cd /etc/sysconfig/hardware
+# touch config-ccw-0.0.0122
+ </example>
+
+ For disks on a zFCP fiberchannel host adapter the individual devices
+ are listed inside the file. Using the same example as above,
+ create a file <file/config-ccw-0.0.2900/ containing (second device
+ truncated for readability):
+ <example>
+ZFCP_DEVICES=(0x21000020371c93a5:0x0000000000000000 0x2100...:0x...)
+ </example></p>
+
+ </sect2>
+ <sect2 id="s390-other"><heading>Configuration for network devices</heading>
+
+ <p>Network devices are enabled through configuration files in
+ <file>/etc/sysconfig/hardware/</file>. For a ctc network device with
+ read channel <tt/0.0.0a00/ and write channel <tt/0.0.0a01/ and using
+ the S/390 protocol, you would create a file <file/config-ccw-0.0.0a00/
+ containing:
+ <example>
+CCWGROUP_CHANS=(0.0.0a00 0.0.0a01)
+CTC_PROTOCOL=0
+ </example>
+
+ For a qeth network device with layer2 mode enabled, this could be a
+ file <file/config-ccw-0.0.0600/:
+ <example>
+CCWGROUP_CHANS=(0.0.0600 0.0.0601 0.0.0602)
+QETH_OPTIONS=(layer2)
+ </example></p>
+
+ <p>Supported options for ctc are: <tt/CTC_PROTOCOL/ and <tt/CTC_BUFFER/;
+ and for qeth: <tt/QETH_PORTNAME/, <tt/QETH_PORTNO/ and <tt/QETH_OPTIONS/.
+ </p>
+ <p>As network devices on S/390 do not have a stable MAC address, it is
+ not possible to use <prgn/udev/ persistent device naming. Instead you
+ can add an option <tt/INTERFACE_NAME/ in the configuration file to
+ rename an interface.</p>
+
+ </sect2>
+ </sect1>
+]]>
+
<sect1 id="mdadm"><heading>Upgrading mdadm</heading>
<p>mdadm now needs a configuration file to assemble MD arrays (RAID)
@@ -1871,11 +2003,11 @@
and adjust the location of the <prgn/update-grub/ program changing
<file>/sbin/update-grub</file> to <file>/usr/sbin/update-grub</file>.</p>
-<!-- TODO: (jfs) Is this needed? aptitude-0.4.4-1 "fixed" this, see #386307 -->
- <item><p>Unmark the 2.6 kernel image installed as not an automatic
- package, so that <prgn/aptitude/ never considers it unused:
+ <item><p>If the new kernel image metapackage was pulled in as a
+ dependency of the old one, it will be marked as automatically installed,
+ which should be corrected:
<example>
-# aptitude unmarkauto linux-image-2.6-<flavor>
+# aptitude unmarkauto $(dpkg-query -W 'linux-image-2.6-*' | cut -f1)
</example>
</p>
<item><p>Remove &oldreleasename;'s kernel metapackages by running:
@@ -2586,8 +2718,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>
+ <p>If you upgrade your system using a Debian mirror, it will
+ automatically be upgraded to the latest &oldreleasename; point
+ release.</p>
</sect>
More information about the l10n-russian-cvs-commits
mailing list