Re: ÇëУ¶Ôrelease-notes sgml 04.htm³õ¸å¡£
多谢，这是校对稿，请继续校对。
注意一下， &....; 中的';'是关键字的一部分，应该保持原样。
翻译文件时，可以把文件和原件的后缀都改成 .sgml ，这样当
打开 vim 的 syntax highlight 的时候，对翻译有一定的帮助。
在我的 .vimrc 里有:
" default fileencoding is prc, use taiwan for Big5 encoding
set fileencoding=prc
" turn on syntax highlight
if has("syntax")
syntax on
endif
%%%%%%%%%% 翻译
<sect id="information">系统的详细变化
<![ %not-sparc [
<![ %not-alpha [
<p>如下所述的升级步骤可用于将以前任意的Debian发行版本直接
升级至&release;你不必逐步升级至每一个中间发行版本。但是请注意，
从2.0或更早的版本升级到&release;还未被广泛地测试过，因此不予
支持。
]]>
]]>
<![ %sparc [
<p>这个基于&arch-title;的&debian发行版本;由于一些 GNU C 库函数的需要，
系统结构必需是一个2.2.x的内核(最好是2.2.7或更高版本的)。但是新的 GNU C 库
仍和老的程序兼容。如果你想从&debian; 2.1(另外唯一基于&arch-title;的版本)
升级到这个版本;而你又没有2.2.x的内核，那么<package/libc6/的包将无法安装。
不要试图在不是2.2.x内核的—进行* 制升级。如果你这么做的话，您将会
遇到严重的问题，以致你必须用急救盘起动修复。如果你需要升级你的内核，
要么安装这个发行版本中提供的某个内核(也就是说<package/kernel-image-*/
包)，或从源程序编译你自己的内核。然后你才可以进行升级。
]]>
<p>GNU C库源代码和二进制代码的向前兼容性意味着大多数来自以前发行版本的程序
可以在新版本中运行（但倒过来不行）。所有在&debian; &release;中的软件包都被创
建成在新环境中运行，当然，也可以在新版本中重新编译大多数程序而不需任何变化。
然而对以上规则也有一些例外，因此你的有些程序要在新的glibc下修改和/或重新编译
才能正常地运行。
<p>当在内核2.2和glibc2.1下运行的时候，系统会自动挂载一个额外的`devpts'
虚拟设备以支持Unix98 PTYs，此时，一些进程守护程序（Unix 服务器）会自动切换，
去使用那些新的设备(使用<file>/dev/pts/*</file> 来取代 <file>/dev/ttyp*</file>)
<p>在内核2.2.x下，PC打印机设备从lp0开始而不是2.0.x时的lp1，所以你要更新你的
printcap和其他一些配置文件来适应这一变化(<file>/dev/lp0</file> 取代
<file>/dev/lp1</file>， <file>/dev/lp1</file> 取代 <file>/dev/lp2</file> ，
以此类推)。
<p>注意（从slink）升级完后，必须先安装内核2.2.x才能让Samba再次正常工作。
<p>向使用新内核过度进行得很顺利，主要是因为我们早已为2.1版本运行2.2内核
作好了充分的准备。有些问题仍然存在，主要和网络有关：
<list>
<item>防火墙操作工具 <prgn/ipfwadm/ 已由 <prgn/ipchains/所取代。
<package/netbase/ 的升级过程中将会要求你和一个wrapper脚本建立符号连接，
这样你的防火墙才能继续起作用；你也可以参考 <file>/usr/share/doc/netbase/ipchains-HOWTO.txt.gz</file> ，将你的防火墙设置转换成正确的 <prgn/ipchains/ 设置。
<item>由老版本的Debian安装过程设立的 <file>/etc/init.d/network</file> 脚本
在用新的内核时会打印错误信息；这可以通过在该文件中使用<prgn/route/时加上恰当
的`netmask' 和 `dev'选项来解决。
<item>不幸的是，这次的内核升级也可能对那些机器内存很小的用户造成麻烦。
</list>
<p>你必须阅读内核的<file>Documentation/Changes</file>文档以取得更多的
关于如何升级软件，使之在新内核下工作的信息。
<p>对使用PAM的应用程序的升级过程我们尽量的做到顺畅和完整。在大多数情况下，
新的配置将仿照你旧的pre-PAM配置。但是，不是每种情况都能被照顾到的。如果有
需要作出修改，你可以安装<package/libpam-doc/包，里面的文档盖涵了PAM 函数库
的各个方面。
%%%%%%%%%%%% 原文
<sect id="information">Detailed changes to the system
<![ %not-sparc [
<![ %not-alpha [
<p>The upgrade procedures described below can be used to upgrade any
previous Debian release to &release; at once; you should not have to upgrade
separately to every intermediate release. Note however, that upgrades
from releases 2.0 and earlier to &release; have not been tested extensively,
and are therefore not supported.
]]>
]]>
<![ %sparc [
<p>This release of &debian; for the &arch-title; architecture requires
a 2.2.x kernel (preferably 2.2.7 or above), since some of the GNU C
library functions require it. The new GNU C library is, however, still
compatible with old programs. If you attempt to upgrade to this release
from &debian; 2.1 (the only other release for &arch-title;), and you do
not have a 2.2.x kernel, then the <package/libc6/ package install will
fail before proceeding. DO NOT attempt to force this upgrade on a
non-2.2.x kernel — if you do that, you will have severe problems
that will require booting a rescue disk to fix. If you need to upgrade
your kernel, either install one of the kernels provided in this release
(i.e. the <package/kernel-image-*/ packages), or compile your own from
source. Afterwhich, you may proceed with the upgrade.
]]>
<p>Backwards source and binary compatibility in GNU LibC 2.1 means most
programs from the previous release will run on the new release (but not
the other way around). All packages in &debian; &release; have been set
up to run in the new environment, of course, and it will be possible to
re-compile most programs on the new release without changes. However,
there are always a few exceptions to the rule, so some of your local
programs may need to be modified and/or recompiled on the new glibc to
run properly.
<p>When run under kernel 2.2 and glibc 2.1, system will automatically
mount an additional `devpts' virtual drive, to support Unix98 PTYs, and
some of our daemons (Unix servers) will automatically switch to using
those new devices (<file>/dev/pts/*</file> instead of
<file>/dev/ttyp*</file>).
<p>With kernel 2.2.x, the PC printer devices start from lp0 instead of lp1
as with kernels 2.0.x, so you will want to update your printcap and other
configuration files to use that (<file>/dev/lp0</file> instead of
<file>/dev/lp1</file>, <file>/dev/lp1</file> instead of
<file>/dev/lp2</file> and so on).
<p>Note that after upgrading (from slink), it is necessary to install a
2.2.x kernel before Samba will work again.
<p>The transition to using new kernel went quite smoothly, mainly because
we almost completely prepared the 2.1 release for running a 2.2 kernel.
Some issues still remain, mainly related to the network:
<list>
<item>Firewall manipulation utility <prgn/ipfwadm/ has been replaced with
<prgn/ipchains/. The upgrade of the <package/netbase/ will prompt you to
set up symlinks to a wrapper script so that your firewall remains
functioning; you can also read
<file>/usr/share/doc/netbase/ipchains-HOWTO.txt.gz</file> and properly
convert your firewall setup to <prgn/ipchains/.
<item>The <file>/etc/init.d/network</file> script, as set up by the old
Debian installation procedures, prints error messages with the new
kernel; this can be fixed by adding proper `netmask' and `dev' options
to <prgn/route/ invocations in that file.
<item>Unfortunately, this kernel upgrade could also mean problems for
those users whose machines have very small amounts of RAM.
</list>
<p>You should read the kernel's <file>Documentation/Changes</file> file for
more information on upgrading software to run with the new kernel.
<p>Upgrades to PAM enabled applications have been made as seamless and
integrated as possible. For most instances, the new configurations will
mimic that of your old pre-PAM configurations. However, not every case
can be accounted for. If changes need to be made, you can install the
<package/libpam-doc/ package, which contains documentation on every
--
Best regard
hashao
Reply to: