|
<!--Maintainer: Hero_xbd!(heroxbd at 163 dot com)--> |
|
|
<!--Original Version 1.55--> |
|
|
|
|
| 1 |
<!DOCTYPE debiandoc PUBLIC "-//DebianDoc//DTD DebianDoc//EN" [ |
<!DOCTYPE debiandoc PUBLIC "-//DebianDoc//DTD DebianDoc//EN" [ |
|
<!entity % dynamicdata SYSTEM "../dynamic.ent" > %dynamicdata; |
|
|
<!entity % shareddata SYSTEM "../release-notes.ent" > %shareddata; |
|
|
<!entity docid "$Id: release-notes.zh_CN.sgml,v 1.9 2005-06-08 05:49:47 liling Exp $"> |
|
|
]> |
|
|
|
|
|
<!-- Be careful with automatic reformatting. Please note that the indentation |
|
|
in examples is used in the output (plus additional space) as well. --> |
|
| 2 |
|
|
| 3 |
|
<!ENTITY % dynamicdata SYSTEM "../en/../dynamic.ent"> %dynamicdata; |
| 4 |
|
<!ENTITY % shareddata SYSTEM "../en/../release-notes.ent"> %shareddata; |
| 5 |
|
<!ENTITY docid "$Id: release-notes.zh_CN.sgml,v 1.10 2006-12-05 20:32:38 jseidel Exp $"> |
| 6 |
|
]> |
| 7 |
<debiandoc> |
<debiandoc> |
| 8 |
<book> |
<book> |
| 9 |
<titlepag> |
<titlepag> |
| 10 |
<title>&debian; &release; ('&releasename'), &arch-title;发布说明</title> |
<title> |
| 11 |
<author> |
Release Notes for &debian; &release; ("&releasename"), &arch-title; |
| 12 |
<name>Josip Rodin, Bob Hilliard, Adam Di Carlo, Anne Bezemer, Rob |
</title> |
| 13 |
Bradford (current), Frans Pop (current)</name><email></email> |
<author> |
| 14 |
</author> |
<name>Josip Rodin, Bob Hilliard, Adam Di Carlo, Anne Bezemer, Rob |
| 15 |
<author> |
Bradford (current), Frans Pop (current), Andreas Barth |
| 16 |
<name></name><email>debian-doc@lists.debian.org</email> |
(current)</name><email></email> |
| 17 |
</author> |
</author> |
| 18 |
<version>&docid;</version> |
<author> |
| 19 |
</titlepag> |
<name></name><email>debian-doc@lists.debian.org</email> |
| 20 |
<toc detail="sect1"> |
</author> |
| 21 |
<chapt id="about"><heading>关于新的《发布说明》</heading> |
<version> |
| 22 |
<p>[如果您的版本已经有一个多月了，您可在<url id="&url-release-notes;">下载最新版。]</p> |
&docid; |
| 23 |
|
|
| 24 |
<p>请注意旧的《发布说明》讨论从&oldreleasename之前的发行版升级。可是这些信息往往使本说明复杂化，所以在新的《发布说明》中我们只讨论从&debian 3.0('woody')升级。如果您需要从更老的Debian发行版升级，请阅读旧的《发布说明》。</p> |
</version> |
| 25 |
|
</titlepag> |
| 26 |
</chapt> |
<toc detail="sect1"> |
| 27 |
<chapt id="whats-new"><heading>&debian; &release;的新特性</heading> |
|
| 28 |
|
<chapt id="about"> |
| 29 |
<p>&debian 3.1 ('sarge')与&debian; 3.0 ('woody')支持的系统架构保持一致。以下是本Debian发行版支持的系统架构的完整列表:</p> |
<heading> |
| 30 |
<p> |
Introduction |
| 31 |
<list> |
</heading> |
| 32 |
<item><p>Intel x86 ('i386')</p></item> |
<p> |
| 33 |
<item><p>Motorola 680x0 ('m68k')</p></item> |
The primary goals of these Release Notes are to inform users of major |
| 34 |
<item><p>Alpha ('alpha')</p></item> |
changes in this release of the Debian distribution, to provide |
| 35 |
<item><p>SPARC ('sparc')</p></item> |
information on how to upgrade safely from the previous to the this |
| 36 |
<item><p>PowerPC ('powerpc')</p></item> |
release and finally to inform users of known potential issues users |
| 37 |
<item><p>ARM ('arm')</p></item> |
could encounter when upgrading to or using the release. |
| 38 |
<item><p>MIPS ('mips' (Big endian) and 'mipsel' (Little endian))</p></item> |
</p> |
| 39 |
<item><p>Intel Itanium ('ia64')</p></item> |
<p> |
| 40 |
<item><p>HP PA-RISC ('hppa')</p></item> |
Note that it is impossible to list every known issue and that therefore |
| 41 |
<item><p>S/390 ('s390')</p></item> |
a selection has been made based on a combination of the expected |
| 42 |
</list> |
prevalence and impact of issues. |
| 43 |
</p> |
</p> |
| 44 |
|
<p> |
| 45 |
<p>您可以在<url id="&url-ports;" name="Debian系统移植页">阅读更多的系统移植信息。</p> |
The most recent version of this document is always available at <url |
| 46 |
|
id="&url-release-notes;">. If your version is more than a month old, you |
| 47 |
<![ %secondrelease [ |
might wish to download the latest version.] |
| 48 |
<p>这仅是 &debian;在&arch-title;系统架构上的第二次正式发行。我们觉得系统本身已经证明了它有公开发行的水准。然而，因为它从来没有像其他系统架构上的发行版那样知名(而且因之能被用户测试)，所以您可能会遭遇到一些问题。请利用我们的<url id="&url-bts;" name="Bug跟踪系统">来报告您所发现的任何问题；在报告中请不要忘了提及您是在&architecture;系统架构上发现这个错误的。</p> |
</p> |
| 49 |
]]> |
<p> |
| 50 |
|
请注意我们只支持和讨论从上一发行版（也就是&oldreleasename;）升级。如果您需要从更老的Debian发行版升级，请阅读从前的《发布说明》。 |
| 51 |
<![ %not-m68k [ |
</p> |
| 52 |
<p>&arch-title;上的&debian; &release; 使用&kernelversion;内核。</p> |
</chapt> |
| 53 |
<![ %available-2.6 [ |
<chapt id="whats-new"> |
| 54 |
|
<heading> |
| 55 |
<p>在&arch-title;上也可以使用&kernelversion-2.6;内核。注意Debian的2.6.8内核软件包含有2.6.8.1内核和一些补丁。]]> |
&debian; &release;的新特性 |
| 56 |
|
</heading> |
| 57 |
]]> <!-- %m68k --> |
<p> |
| 58 |
<![ %m68k [ |
这一发行版加入了对AMD64体系架构的支持，包括Intel(EM64T)和AMD(AMD64)的64位处理器。上发行版 |
| 59 |
<p>&arch-title上的&debian; &release;使用2.2.25和2.4.27版内核。对于某些子系统2.6.8内核也可用，但仍处于实验阶段。</p> |
&debian; 3.1 |
| 60 |
]]> |
('sarge')有非官方的AMD64移植可用。从这一非官方版本升级应该没有问题，但我们不准备在本发布说明中介绍。 |
| 61 |
|
</p> |
| 62 |
<sect id="newdistro"><heading>新的发行版</heading> |
<p> |
| 63 |
|
我们将停止对Motorola 680x0 |
| 64 |
<p>新版Debian比旧的&oldreleasename;拥有更多的软件；新版包含9000多个新软件包。大多数－－将近6500个软件包(占&oldreleasename;的73%)－－的软件被升级。另外，许多软件包由于某些原因被从发行版中移除，不会进行任何更新，它们在包管理程序中被注以'obsolete'。</p> |
('m68k')体系架构的官方支持，因为它不满足Debian发布管理的标准。关键问题出在它的性能和上游组织对基本工具的支持。然而，即使不再有官方发布版，m68k的移植工作仍然会很活跃，安装也不成问题。 |
| 65 |
|
</p> |
| 66 |
<p>本版的Debian GNU/Linux包括非常出色的XFree86 4.3，它提供对更广泛的硬件支持、更好的自动检测功能、更高级的技术如Xinerama和3D加速支持。</p> |
<p> |
| 67 |
|
下面是&debian;&releasename;中由官方支持的体系架构： |
| 68 |
<p>本版的&debian;比以前更加桌面化了，它现在提供GNOME 2.8和KDE 3.3。而且首次提供OpenOffice.org完整办公套件以及Evolution group software与GAIM即时消息客户端。</p> |
</p> |
| 69 |
|
<p> |
| 70 |
<p>&releasename;的<prgn/aptitude/是更优秀的字符界面包管理系统。它在包依赖问题解决上比<prgn/apt-get/更强大。<prgn/aptitude/支持大多数<prgn/apt-get/的命令行操作。如果您仍在使用<prgn/dselect/，就应试试<prgn/aptitude/来管理软件包。</p> |
<list> |
| 71 |
|
<item> |
| 72 |
<p>官方&debian;发行版包括13至15张(取决于系统架构)binary CD(含有编译后的软件包——译者)和十几张source CD(含有未编译的原代码——译者)，现在也可以使用单张DVD。</p> |
<p> |
| 73 |
|
Intel x86 ('i386') |
| 74 |
<sect1 id="volatile"><heading>debian-volatile新服务</heading> |
</p> |
| 75 |
|
</item> |
| 76 |
<p><em>debian-volatile</em>允许用户轻松升级经常更新的软件包。例如病毒扫描软件签名列表或spam滤镜样式集。管理员可以像"security.debian.org"一样方便地使用"volatile.debian.net"，接受最新信息，避免维护基于未更新软件系统的忧虑和风险。请查看<url id="&url-debian-volatile" name="volatile.debian.net">来获得更多信息及镜像列表。</p> |
<item> |
| 77 |
|
<p> |
| 78 |
<p>注意debian-volatile<em/不是/官方Debian服务。请自己辨别决定是否使用它。</p> |
Alpha ('alpha') |
| 79 |
|
</p> |
| 80 |
</sect1> |
</item> |
| 81 |
|
<item> |
| 82 |
<sect1 id="non-us"><heading>non-US被废弃</heading> |
<p> |
| 83 |
|
SPARC ('sparc') |
| 84 |
<p>从前在non-US部分的软件包在&releasename;中已被移进普通包列表。如果<file>/etc/apt/sources.list</file>中有指向"non-us"的行，您应移除它们。</p> |
</p> |
| 85 |
</sect1> |
</item> |
| 86 |
|
<item> |
| 87 |
</sect> |
<p> |
| 88 |
|
PowerPC ('powerpc') |
| 89 |
<sect id="newinst"><heading>新的安装系统</heading> |
</p> |
| 90 |
|
</item> |
| 91 |
<p>旧的&debian;安装系统已被全新的debian-installer取代。新的安装系统采用模块化设计，在扩展性理念下开发。它已经被完整翻译为近40种语言； |
<item> |
| 92 |
其它语言的翻译工作仍在继续，并将会被添加到&releasename;中。</p> |
<p> |
| 93 |
|
ARM ('arm') |
| 94 |
<p>安装系统的新功能包括更有效的硬件检测、可从U盘启动、最初可选用<prgn>aptitude</prgn>来安装软件包、<prgn>XFS</prgn>分区格式支持、<prgn>RAID</prgn>和<prgn>LVM</prgn>(一种卷管理工具)支持等等。</p> |
</p> |
| 95 |
|
</item> |
| 96 |
<p>建议用户阅读在第一张安装CD或<url id="&url-install-manual;" name="发布页">上的《安装手册》来深入了解新安装系统。《安装手册》已经被完整翻译为8种语言并且正在被翻译成更多种语言。其它语言版本将在完成后被放在网站上。</p> |
<item> |
| 97 |
|
<p> |
| 98 |
<![ %i386 [ |
MIPS ('mips' (Big endian) and 'mipsel' (Little endian)) |
| 99 |
|
</p> |
| 100 |
<p>在&arch-title;系统上，有一组特殊供盲人使用的安装软盘，"speakup"。它们含有一个支持braille(布莱叶文，一种盲文－－译者)显示的内核。可以在brltty(一种支持盲文显示的daemon程序——译者)文档中找到所有支持的设备型号。请查阅<url id="&url-installer;index#speakup" |
</item> |
| 101 |
name="debian-installer发布页">来获得"speakup"的深入信息。</p> |
<item> |
| 102 |
|
<p> |
| 103 |
]]> |
Intel Itanium ('ia64') |
| 104 |
|
</p> |
| 105 |
<!-- FJP: Maybe a short description of available installation methods could be |
</item> |
| 106 |
added here: floppy, CD (netinst/business-card/full ), netboot, |
<item> |
| 107 |
hd-media, USB-stick. --> |
<p> |
| 108 |
</sect> |
HP PA-RISC ('hppa') |
| 109 |
|
</p> |
| 110 |
</chapt> |
</item> |
| 111 |
|
<item> |
| 112 |
<chapt id="installing"><heading>全新安装</heading> |
<p> |
| 113 |
|
S/390 ('s390') |
| 114 |
<p>原有的<prgn>boot-floppies</prgn>安装系统已被全新更强大的模块化<prgn>debian-installer</prgn>取代。</p> |
</p> |
| 115 |
|
</item> |
| 116 |
<p>新的安装程序提供多种安装方式。具体可用的安装方式取决于您的系统架构。</p> |
<item> |
| 117 |
<p>如果要全新安装Debian，请阅读官方CD上的 |
<p> |
| 118 |
<example> |
AMD64 ('amd64') |
| 119 |
|
</p> |
| 120 |
|
</item> |
| 121 |
|
</list> |
| 122 |
|
</p> |
| 123 |
|
<p> |
| 124 |
|
您可以在<url id="&url-ports;" |
| 125 |
|
</p> |
| 126 |
|
<![ %secondrelease [ |
| 127 |
|
|
| 128 |
|
<p> |
| 129 |
|
这仅是 |
| 130 |
|
&debian;在&arch-title;系统架构上的第二次正式发行。我们觉得系统本身已经证明了它有公开发行的水准。然而，因为它从来没有像其他系统架构上的发行版那样知名(而且因之能被用户测试)，所以您可能会遭遇到一些问题。请利用我们的<url |
| 131 |
|
id="&url-bts;" |
| 132 |
|
</p> |
| 133 |
|
]]> |
| 134 |
|
|
| 135 |
|
<p> |
| 136 |
|
&arch-title;上的&debian; &release; 使用&kernelversion;内核。 |
| 137 |
|
</p> |
| 138 |
|
<sect id="newdistro"> |
| 139 |
|
<heading> |
| 140 |
|
新的发行版 |
| 141 |
|
</heading> |
| 142 |
|
<p> |
| 143 |
|
TODO: Update numbers |
| 144 |
|
</p> |
| 145 |
|
<p> |
| 146 |
|
This new release of Debian again comes with a lot more software than |
| 147 |
|
its predecessor &oldreleasename;; the distribution includes over 9000 |
| 148 |
|
new packages. Most of the software in the distribution has been |
| 149 |
|
updated: almost 6500 software packages (this is 73% of all packages in |
| 150 |
|
&oldreleasename;). Also, a significant number of packages have for |
| 151 |
|
various reasons been removed from the distribution. You will not see |
| 152 |
|
any updates for these packages and they will be marked as 'obsolete' in |
| 153 |
|
package management front-ends. |
| 154 |
|
</p> |
| 155 |
|
<p> |
| 156 |
|
With this release &debian; switches from XFree86 to the 7.1 release of |
| 157 |
|
X.Org, which includes support for a greater range of hardware and |
| 158 |
|
better autodetection. This allows the use of Compiz, which is one of |
| 159 |
|
the first compositing window managers for the X Window System, taking |
| 160 |
|
full advantage of hardware OpenGL-acceleration for supported devices. |
| 161 |
|
</p> |
| 162 |
|
<p> |
| 163 |
|
&debian;带有最新的桌面应用程序，比如GNOME 2.14, KDE 3.5 |
| 164 |
|
和OpenOffice.org 2.0。 |
| 165 |
|
</p> |
| 166 |
|
<p> |
| 167 |
|
<prgn>aptitude</prgn> is the preferred program for package management |
| 168 |
|
from console. <prgn>aptitude</prgn> supports most command line |
| 169 |
|
operations of <prgn>apt-get</prgn> and has proven to be better at |
| 170 |
|
dependency resolution than <prgn>apt-get</prgn>. If you are still using |
| 171 |
|
<prgn>dselect</prgn>, you should switch to <package>aptitude</package> |
| 172 |
|
as the official frontend for package management. |
| 173 |
|
</p> |
| 174 |
|
<p> |
| 175 |
|
官方&debian;发行版包括13至15张(取决于系统架构)binary |
| 176 |
|
CD(含有编译后的软件包——译者)和十几张source |
| 177 |
|
CD(含有未编译的原代码——译者)，现在也可以使用DVD。 |
| 178 |
|
</p> |
| 179 |
|
<sect1 id="volatile"> |
| 180 |
|
<heading> |
| 181 |
|
debian-volatile now an official service |
| 182 |
|
</heading> |
| 183 |
|
<p> |
| 184 |
|
The <em>debian-volatile</em> service that was introduced as an |
| 185 |
|
unofficial service with the release of &oldreleasename;, has now |
| 186 |
|
become an official &debian; service. |
| 187 |
|
</p> |
| 188 |
|
<p> |
| 189 |
|
This means that it no longer has a <tt>.debian.net</tt> address, but |
| 190 |
|
now uses a <tt>.debian.org</tt> address. Please make sure to update |
| 191 |
|
your <file>/etc/apt/sources.list</file> accordingly if you were |
| 192 |
|
already using this service. |
| 193 |
|
</p> |
| 194 |
|
<p> |
| 195 |
|
<em>debian-volatile</em> allows users to easily update stable packages |
| 196 |
|
that contain information that quickly goes out of date. Examples are a |
| 197 |
|
virus scanner's signatures list or a spam filter's pattern set. For |
| 198 |
|
more information and a list of mirrors, please see the archive's <url |
| 199 |
|
id="&url-debian-volatile" name="web page">. |
| 200 |
|
</p> |
| 201 |
|
</sect1> |
| 202 |
|
</sect> |
| 203 |
|
<sect id="inst-new"> |
| 204 |
|
<heading> |
| 205 |
|
新的安装系统 |
| 206 |
|
</heading> |
| 207 |
|
<p> |
| 208 |
|
There has been a lot of development on the Debian Installer since its |
| 209 |
|
first official release with &oldreleasename; resulting in both improved |
| 210 |
|
hardware support and some exciting new features. |
| 211 |
|
</p> |
| 212 |
|
<p> |
| 213 |
|
In these Release Notes we'll only list the major changes in the |
| 214 |
|
installer. If you are interested in an overview of the detailed changes |
| 215 |
|
since &oldreleasename;, please check the release announcements for the |
| 216 |
|
&releasename; beta and RC releases avaiable from the project's <url |
| 217 |
|
id="&url-installer-news" name="news history">. |
| 218 |
|
</p> |
| 219 |
|
<sect1 id="inst-changes"> |
| 220 |
|
<heading> |
| 221 |
|
Major changes |
| 222 |
|
</heading> |
| 223 |
|
<p> |
| 224 |
|
<taglist> |
| 225 |
|
<tag> |
| 226 |
|
No reboot during the installation |
| 227 |
|
</tag> |
| 228 |
|
<item> |
| 229 |
|
<p> |
| 230 |
|
The installation used to be split into two parts: setting up the |
| 231 |
|
base system and making it bootable, followed by a reboot and after |
| 232 |
|
that the execution of <prgn>base-config</prgn> which would take |
| 233 |
|
care of things like user setup, setup of the package management |
| 234 |
|
system and installation of additional packages (using tasksel). |
| 235 |
|
</p> |
| 236 |
|
<p> |
| 237 |
|
For &releasename; the second stage has been integrated into Debian |
| 238 |
|
Installer itself. This has a number of advantages, including |
| 239 |
|
increased security and the fact that after the reboot at the end of |
| 240 |
|
the installation the new system should already have the correct |
| 241 |
|
timezone and, if you installed the Desktop environment, will at |
| 242 |
|
once start the graphical user interface. |
| 243 |
|
</p> |
| 244 |
|
</item> |
| 245 |
|
<tag> |
| 246 |
|
UTF-8 encoding default for new systems |
| 247 |
|
</tag> |
| 248 |
|
<item> |
| 249 |
|
<p> |
| 250 |
|
The installer will set up systems to use UTF-8 encoding rather than |
| 251 |
|
the old language-specific encodings (like ISO-8859-1, EUC-JP or |
| 252 |
|
KIO-8). |
| 253 |
|
</p> |
| 254 |
|
</item> |
| 255 |
|
<tag> |
| 256 |
|
More flexible partitioning |
| 257 |
|
</tag> |
| 258 |
|
<item> |
| 259 |
|
<p> |
| 260 |
|
It is now possible to set up file systems on an LVM volume using |
| 261 |
|
guided partitioning. |
| 262 |
|
</p> |
| 263 |
|
<p> |
| 264 |
|
The installer is also able to set up encrypted filesystems. Using |
| 265 |
|
manual partitioning you have the choice between <tt>dm-crypt</tt> |
| 266 |
|
and <tt>loop-aes</tt>, using a passphrase or a random key, and you |
| 267 |
|
can tune various other options. Using guided partitioning, the |
| 268 |
|
installer will create an encrypted LVM partition that contains any |
| 269 |
|
other filesystems (except <file>/boot</file>) as logical volumes. |
| 270 |
|
</p> |
| 271 |
|
</item> |
| 272 |
|
<![ %i386-amd64 [ |
| 273 |
|
|
| 274 |
|
<tag> |
| 275 |
|
Graphical user interface |
| 276 |
|
</tag> |
| 277 |
|
<item> |
| 278 |
|
<p> |
| 279 |
|
If you prefer a graphical user interface, try booting the the |
| 280 |
|
installer with <tt>installgui</tt>. |
| 281 |
|
</p> |
| 282 |
|
<p> |
| 283 |
|
The functionality of the graphical installer is almost identical to |
| 284 |
|
the regular installer, only the presentation differs. There is one |
| 285 |
|
exception: the graphical frontend does not support setting up |
| 286 |
|
encrypted partitions using random keys. |
| 287 |
|
</p> |
| 288 |
|
<p> |
| 289 |
|
Note: the graphical user interface is not available for all |
| 290 |
|
architectures. |
| 291 |
|
</p> |
| 292 |
|
</item> |
| 293 |
|
]]><![ %powerpc [ |
| 294 |
|
|
| 295 |
|
<tag> |
| 296 |
|
Graphical user interface |
| 297 |
|
</tag> |
| 298 |
|
<item> |
| 299 |
|
<p> |
| 300 |
|
For &arch-title; a separate installation image using a graphical |
| 301 |
|
user interface is available on an experimental basis. It is known |
| 302 |
|
to work on most CHRP systems that have an ATI graphics card, but |
| 303 |
|
has been insufficiently tested on &arch-title; to include it on the |
| 304 |
|
normal installation CDs. |
| 305 |
|
</p> |
| 306 |
|
<p> |
| 307 |
|
If you'd like to try the graphical installer, look for the |
| 308 |
|
"gtk-miniiso" image. |
| 309 |
|
</p> |
| 310 |
|
</item> |
| 311 |
|
]]> |
| 312 |
|
|
| 313 |
|
<tag> |
| 314 |
|
Rescue mode |
| 315 |
|
</tag> |
| 316 |
|
<item> |
| 317 |
|
<p> |
| 318 |
|
You can use the installer to solve problems with your system, for |
| 319 |
|
example when it refuses to boot. The first steps will be just like |
| 320 |
|
a regular installation, but the installer will not start the |
| 321 |
|
partitioner. Instead it will offer you a menu of rescue options. |
| 322 |
|
</p> |
| 323 |
|
<p> |
| 324 |
|
Activate the rescue mode by booting the installer with |
| 325 |
|
<tt>rescue</tt>, or by adding a boot parameter |
| 326 |
|
<tt>rescue/enable=true</tt>. |
| 327 |
|
</p> |
| 328 |
|
</item> |
| 329 |
|
<tag> |
| 330 |
|
Using sudo instead of root account |
| 331 |
|
</tag> |
| 332 |
|
<item> |
| 333 |
|
<p> |
| 334 |
|
During expert installations you can choose to not set up the root |
| 335 |
|
account (it will be locked), but instead set up <prgn>sudo</prgn> |
| 336 |
|
so that the first user can use that for system administration. |
| 337 |
|
</p> |
| 338 |
|
</item> |
| 339 |
|
<tag> |
| 340 |
|
SELinux |
| 341 |
|
</tag> |
| 342 |
|
<item> |
| 343 |
|
<p> |
| 344 |
|
The packages needed for SELinux support have been promoted to |
| 345 |
|
priority "standard". This means that they will be installed by |
| 346 |
|
default if you select the Standard task during |
| 347 |
|
installation. However, SELinux support is not enabled by |
| 348 |
|
default. If you want to secure your system using SELinux, you will |
| 349 |
|
need to enable it manually after the installation. |
| 350 |
|
</p> |
| 351 |
|
</item> |
| 352 |
|
<![ %not-s390 [ |
| 353 |
|
|
| 354 |
|
<tag> |
| 355 |
|
New languages |
| 356 |
|
</tag> |
| 357 |
|
<item> |
| 358 |
|
<p> |
| 359 |
|
Thanks to the huge efforts of translators, Debian can now be |
| 360 |
|
installed in up to $FIXME$ languages. <![ %g-i [ If the graphical |
| 361 |
|
user interface is used, an additional $FIXME$ languages are |
| 362 |
|
supported. ]]> |
| 363 |
|
</p> |
| 364 |
|
</item> |
| 365 |
|
]]> |
| 366 |
|
|
| 367 |
|
</taglist> |
| 368 |
|
</p> |
| 369 |
|
</sect1> |
| 370 |
|
<sect1 id="inst-auto"> |
| 371 |
|
<heading> |
| 372 |
|
Automated installation |
| 373 |
|
</heading> |
| 374 |
|
<p> |
| 375 |
|
A lot of the changes mentioned in the previous section also imply |
| 376 |
|
changes in the support in the installer for automated installation |
| 377 |
|
using preconfiguration files. This means that if you have existing |
| 378 |
|
preconfiguration files that worked with the &oldreleasename; |
| 379 |
|
installer, you cannot expect these to work with the new installer |
| 380 |
|
without modification. |
| 381 |
|
</p> |
| 382 |
|
<p> |
| 383 |
|
The good news is that the <url id="&url-install-manual;" |
| 384 |
|
name="Installation Guide"> now has a separate appendix with extensive |
| 385 |
|
documentation on using preconfiguration. |
| 386 |
|
</p> |
| 387 |
|
<p> |
| 388 |
|
The &releasename; installer introduces some exciting new features that |
| 389 |
|
allow further and easier automation of installs. It also adds support |
| 390 |
|
for advanced partitioning using RAID, LVM and encrypted LVM. See the |
| 391 |
|
documentation for details. |
| 392 |
|
</p> |
| 393 |
|
</sect1> |
| 394 |
|
</sect> |
| 395 |
|
</chapt> |
| 396 |
|
<chapt id="installing"> |
| 397 |
|
<heading> |
| 398 |
|
全新安装 |
| 399 |
|
</heading> |
| 400 |
|
<p> |
| 401 |
|
The Debian Installer is the official installation system for Debian. It |
| 402 |
|
offers a variety of installation methods. Which methods are available to |
| 403 |
|
install your system depends on your architecture. |
| 404 |
|
</p> |
| 405 |
|
<p> |
| 406 |
|
Images of the installer for &releasename; and the Installation Guide can |
| 407 |
|
be found on the <url id="&url-installer;" name="Debian website">. |
| 408 |
|
</p> |
| 409 |
|
<p> |
| 410 |
|
The Installation Guide is also included on the first CD/DVD of the |
| 411 |
|
official Debian CD/DVD sets, at: |
| 412 |
|
<example> |
| 413 |
/doc/install/manual/<var>language</var>/index.html |
/doc/install/manual/<var>language</var>/index.html |
| 414 |
</example> |
</example> |
| 415 |
或Internet上的<url id="&url-install-manual;"name="&releasename; 安装手册">以及debian-installer的<url id="&url-installer;index#errata" name="errata">。</p> |
</p> |
| 416 |
|
<p> |
| 417 |
<![ %not-m68k [ |
You may also want to check the <url id="&url-installer;index#errata" |
| 418 |
<![ %d-i-avail-2.6 [ |
name="errata"> for debian-installer. |
| 419 |
|
</p> |
| 420 |
<p>缺省的情况下安装系统使用2.4系列内核。对于&arch-title;也可以使用基于2.6的内核。要了解更多信息，请参考《安装手册》。</p> |
<![ %alpha [ |
| 421 |
]]> |
|
| 422 |
<![ %d-i-default-2.6 [ |
<p> |
| 423 |
<p>安装系统在&arch-title;上缺省使用2.6系列的内核。</p> |
安装程序只能在那些支持SRM终端的alpha系统上使用。请在开始安 |
| 424 |
]]> |
装前将系统转换为SRM。如果您的机器只支持 AlphaBIOS/ARC终端，您 |
| 425 |
|
仍然可以通过安装(最小化)的 &oldreleasename; 随后将其升级来安装 |
| 426 |
]]> <!-- %not-m68k --> |
&releasename;。要了解关于不同终端的更多的信息，请阅读<url |
| 427 |
<![ %m68k [ |
id="http://www.debian.org/ports/alpha" name="Debian alpha port web |
| 428 |
<p>取决于子系统结构，安装时可以使用2.2.25内核或2.4.27内核或两者。对于Mac2.2.25内核更受偏爱，对于其它系统则是2.4.27内核。</p> |
pages"> |
| 429 |
|
</p> |
| 430 |
<p>目前<prgn/partman/不支持atari分区，<prgn/partman/是<package/debian-installer/中用来分区的工具。这意味着这一步仅能手动进行。请查阅Installation Guide来获取深入信息。</p> |
]]><![ %sparc [ |
| 431 |
]]> |
|
| 432 |
|
<sect id="sparc_fb"> |
| 433 |
<![ %alpha [ |
<heading> |
| 434 |
<p>安装程序只能在那些支持SRM终端的alpha系统上使用。请在开始安 |
&arch-title;上的帧缓冲器问题 |
| 435 |
装前将系统转换为SRM。如果您的机器只支持 AlphaBIOS/ARC终端，您 |
</heading> |
| 436 |
仍然可以通过安装(最小化)的 &oldreleasename; 随后将其升级来安装 |
<p> |
| 437 |
&releasename;。要了解关于不同终端的更多的信息，请阅读<url |
Because of display problems on some systems, framebuffer support is |
| 438 |
id="http://www.debian.org/ports/alpha" name="Debian alpha 移植页面">. |
disabled by default for &arch-title; for most graphics cards. This can |
| 439 |
</p> |
result in ugly display on systems that do properly support the |
| 440 |
]]> |
framebuffer. If you see display problems in the installer, you can try |
| 441 |
|
booting the installer with the parameter |
| 442 |
<![ %sparc [ |
<tt>framebuffer=true</tt>. Please let us know if the framebuffer is not |
| 443 |
<sect id="sparc_kbd"><heading>&arch-title;上的键盘问题</heading> |
used by default, but works for your hardware. |
| 444 |
|
</p> |
| 445 |
<p>在安装过程中会有一些键盘问题。</p> |
</sect> |
| 446 |
|
]]> |
| 447 |
<p>第一个问题是被Sun用在诸如SunBlade上的USB键盘。当采用默认的2.4内核安装时，这些键盘会被安装程序错误地识别为普通Sun键盘。一些解决方法可在《安装手册》中找到。</p> |
|
| 448 |
|
<sect id="popcon"> |
| 449 |
<p>第二个问题与内核有关。2.6系列的内核采用一个不同的输入层，它使所有键盘看起来都像“普通”PC键盘。这意味着如果您以2.4内核启动安装程序而且配置它为Sun或USB键盘，然后（在export模式）为新系统选择2.6内核，很可能在重启之后造成键盘不工作。</p> |
<heading> |
| 450 |
|
包受欢迎度排名 |
| 451 |
</sect> |
</heading> |
| 452 |
|
<p> |
| 453 |
<sect id="sparc_fb"><heading>&arch-title;上的帧缓冲器问题</heading> |
Unlike for the previous release, the installation system will again |
| 454 |
|
offer to install the <package>popularity-contest</package> package. |
| 455 |
<p>由于一些系统的显示问题，在&arch-title;上帧缓冲器默认被禁用。这会导致支持帧缓冲器系统显示得非常难看，就像ATI图形卡一样（ATI现在也很出色吧？－－译者）。如果您在安装系统中见到显示问题，可以"debian-installer/帧缓冲器=true"参数启动安装程序。</p> |
</p> |
| 456 |
|
<p> |
| 457 |
</sect> |
<package>popularity-contest</package>向Debian项目提供在发行版中被使用的软件包信息。这些信息主要用于决定软件包在安装CD-ROM上的顺序，也时常被开发人员用于决定是否继续使用缺少维护者的软件包。 |
| 458 |
]]> |
</p> |
| 459 |
|
<p> |
| 460 |
<sect id="popcon"><heading>包受欢迎度排名</heading> |
Information from <package>popularity-contest</package> is processed |
| 461 |
|
anonymously. We would appreciate it if you would participate in this |
| 462 |
<p>由于技术方面的原因，&releasename;中不再缺省安装<package/popularity-contest/。未来版本将会纠正这个问题。</p> |
official survey; you will thereby help improve Debian. |
| 463 |
|
</p> |
| 464 |
<p><package/popularity-contest/向Debian项目提供在发行版中被使用的软件包信息。这些信息主要用于决定软件包在安装CD-ROM上的顺序，也时常被开发人员用于决定是否继续使用缺少维护者的软件包。</p> |
</sect> |
| 465 |
|
</chapt> |
| 466 |
<p>从<package/popularity-contest/得到的信息是匿名的。感谢您安装<package/popularity-contest/并允许它参与官方调查;您就在帮助我们优化Debian。</p> |
<chapt id="upgrading"> |
| 467 |
|
<heading> |
| 468 |
</sect> |
从旧发行版升级 |
| 469 |
</chapt> |
</heading> |
| 470 |
|
<sect id="backup"> |
| 471 |
|
<heading> |
| 472 |
<chapt id="upgrading"><heading>从旧发行版升级 |
准备升级 |
| 473 |
|
</heading> |
| 474 |
<!-- For doc-writers' convenience: |
<p> |
| 475 |
Debian Supported |
We suggest that before upgrading you also read the information in <ref |
| 476 |
release: architectures: |
id="information">. That chapter covers potential issues not directly |
| 477 |
|
related to the upgrade process but which could still be relevant. |
| 478 |
1.3.1 or less i386 |
</p> |
| 479 |
2.0 i386,m68k |
<p> |
| 480 |
2.1 i386,m68k,alpha,sparc |
在升级之前，强烈建议您完整备份系统或至少备份重要数据和配置文件。升级工具和进程非常可靠，但是在安装过程中的硬件错误会导致系统严重损坏。 |
| 481 |
2.2 i386,m68k,alpha,sparc,powerpc,arm |
</p> |
| 482 |
3.0 + hppa s390 mips mipsel ia64 |
<p> |
| 483 |
--></heading> |
您需要备份的主要部份是/etc和/var/lib/dpkg中的内容以及dpkg |
| 484 |
|
--get-selections "*"（此处双引号不可忽略）的输出信息。 |
| 485 |
<sect id="backup"><heading>准备升级</heading> |
</p> |
| 486 |
|
<p> |
| 487 |
<p>在升级之前，强烈建议您完整备份系统或至少备份重要数据和配置文件。升级工具和进程非常可靠，但是在安装过程中的硬件错误会导致系统严重损坏。</p> |
升级过程并会修改<file>/home</file>目录中的文件。不过，一些应用程序（比如Mozilla，某些GNOME和KDE程序）会在第一次执行时用新的默认设置覆盖用户配置文件。作为预防措施，您可以把home目录中以句点开头的隐藏文件备份起来，以便恢复原来的设置。同时，通知其它用户这一问题。 |
| 488 |
|
</p> |
| 489 |
<p>您需要备份的主要部份是/etc和/var/lib/dpkg中的内容以及dpkg --get-selections "*"（此处双引号不可忽略）的输出信息。</p> |
<p> |
| 490 |
|
It's wise to inform all users in advance of any upgrades you're |
| 491 |
<p>升级过程并会修改<file>/home</file>目录中的文件。不过，一些应用程序（比如Mozilla，某些KDE程序）会在第一次执行时用新的默认设置覆盖用户配置文件。作为预防措施，您可以把home目录中以句点开头的隐藏文件备份起来，以便恢复原来的设置。同时，通知其它用户这一问题。</p> |
planning, although users accessing your system via an <prgn>ssh</prgn> |
| 492 |
|
connection should notice little during the upgrade, and should be able |
| 493 |
<p>虽然通过SSH访问您系统的用户不会在升级过程中注意到太多，他们也可能想继续工作，但是，在升级之前通知所有用户是明智的。如果要采取进一步预防措施，可以在升级之前备份或反挂载用户分区(/home)。重新启动并不是必须的，除非您要把内核一并升级。</p> |
to continue working. If you wish to take extra precautions, back up or |
| 494 |
|
unmount users' partitions (<file>/home</file>) before upgrading. A |
| 495 |
<p>全面的升级应在文本模式的虚拟控制台(或直连的串行终端)运行，或者远程地通过SSH运行。</p> |
reboot will not normally be necessary, unless you also plan to upgrade |
| 496 |
|
your kernel. |
| 497 |
<p><strong/重要提示!/不要使用telnet、rlogin、rsh或在要升级的计算机上由xdm、gdm、kdm管理的X会话进行升级。因为它们很可能在升级时被终止，那将造成一个因未完全升级而无法访问的系统。</p> |
</p> |
| 498 |
|
<p> |
| 499 |
<p>任何软件包安装操作都必须在超级用户权限下运行，所以要以root身份登录或用su/sudo来取得必需的访问权限。</p> |
全面的升级应在文本模式的虚拟控制台(或直连的串行终端)运行，或者远程地通过SSH运行。 |
| 500 |
</sect> |
</p> |
| 501 |
|
<p> |
| 502 |
<sect id="system-status"> |
<strong>重要提示!</strong>不要使用telnet、rlogin、rsh或在要升级的计算机上由xdm、gdm、kdm管理的X会话进行升级。因为它们很可能在升级时被终止，那将造成一个因未完全升级而无法访问的系统。 |
| 503 |
<heading>检查系统状态</heading> |
</p> |
| 504 |
|
<p> |
| 505 |
<p>在本章描述的升级过程是专门针对“纯”的&oldreleasename;系统。在此假定您的系统已经是最新版的&oldreleasename;。如果不是这样或您不清楚，请按<ref id="old-upgrade">操作。</p> |
任何软件包安装操作都必须在超级用户权限下运行，所以要以root身份登录或用su/sudo来取得必需的访问权限。 |
| 506 |
|
</p> |
| 507 |
<![ %has-woody-aptitude [ |
<p> |
| 508 |
<p>同时我们假定您装有&oldreleasename;的<prgn/aptitude/。您可以用 |
The upgrade has a few preconditions; you should check them before |
| 509 |
|
actually executing the upgrade. |
| 510 |
<example> |
</p> |
| 511 |
$ dpkg -l aptitude |
<sect1> |
| 512 |
</example> |
<heading> |
| 513 |
来检查。 |
Make sure you have sufficient space for the upgrade |
| 514 |
如果输出行<em/不/以"i"开头，您应在升级之前遵照<ref id="old-aptitude">来安装它。</p> |
</heading> |
| 515 |
]]> |
<p> |
| 516 |
<![ %mips [ |
You have to make sure before upgrading your system that you have |
| 517 |
<sect1><heading>SGI IP22:安装arcboot</heading> |
sufficient hard disk space when you start the full system upgrade |
| 518 |
|
described in <ref id="upgrading_other">. You will first need enough |
| 519 |
<p>如果拥有<em>SGI IP22</em>，现在您应当准备用<package>arcboot</package>启动，而不是直接用内核。<package>arcboot</package>可在&oldreleasename;中找到，按一般方法就可以安装。</p> |
hard disk on the filesystem partition that holds <file>/var/</file> to |
| 520 |
|
temporarily download the packages that will be installed in your |
| 521 |
<p>在安装<package>arcboot</package>之前，您应确认 <file>sources.list</file>仍然指向&oldreleasename;，正像在<ref id="old-sources">中解释的那样。</p> |
system. After the download, you will probably need more space in other |
| 522 |
|
filesystem partitions in order to both install upgraded packages |
| 523 |
</sect1> |
(which might contain bigger binaries or more data) and new packages |
| 524 |
]]> |
that will be pulled in for the upgrade. If your system does not have |
| 525 |
|
sufficient space you might end up with an incomplete upgrade that |
| 526 |
<sect1><heading>禁用APT pinning(APT的一种用于安装特定版本软件包的功能——译者)</heading> |
might be difficult to recover from. |
| 527 |
|
</p> |
| 528 |
<p>如果您配置了APT来安装非stable的特定软件包(例如从testing)，您应当改变APT pinning设置(在<file>/etc/apt/preferences</file>)。可在<manref name="apt_preferences" section="5">中找到APT pinning的详细信息。</p> |
<p> |
| 529 |
|
Both <prgn>aptitude</prgn> and <prgn>apt</prgn> will show you detailed |
| 530 |
</sect1> |
information of the disk space needed for the installation. You can see |
| 531 |
|
this estimate before executing the actual upgrade running: |
| 532 |
<sect1><heading>检查软件包状态</heading> |
</p> |
| 533 |
|
<p> |
| 534 |
<p>不管用什么方法升级，建议您先检查所有软件包的状态，确认所有软件包都处在可升级状态。以下命令会显示任何错误状态，特别是安装不全或配置失败的软件包。 |
<example> |
| 535 |
|
# aptitude -y -s -f --with-recommends dist-upgrade |
| 536 |
<example> |
[ ... ] |
| 537 |
|
XXX upgraded, XXX newly installed, XXX to remove and XXX not upgraded. |
| 538 |
|
Need to get xx.xMB/yyyMB of archives. After unpacking AAAMB will be used. |
| 539 |
|
Would download/install/remove packages. |
| 540 |
|
</example> |
| 541 |
|
</p> |
| 542 |
|
<p> |
| 543 |
|
If you do not have enough space for the upgrade, make sure you free up |
| 544 |
|
space beforehand. You can: |
| 545 |
|
</p> |
| 546 |
|
<p> |
| 547 |
|
<list> |
| 548 |
|
<item> |
| 549 |
|
<p> |
| 550 |
|
Remove packages that have been previously downloaded for |
| 551 |
|
installation (at <file>/var/cache/apt/archive</file>), cleaning up |
| 552 |
|
the package cache by running <prgn>apt-get clean</prgn>. |
| 553 |
|
</p> |
| 554 |
|
</item> |
| 555 |
|
<item> |
| 556 |
|
<p> |
| 557 |
|
Remove old packages you no longer use. If you have |
| 558 |
|
<prgn>popularity-contest</prgn> installed you can use |
| 559 |
|
<prgn>popcon-largest-unused</prgn> to list the packages you do not |
| 560 |
|
use in the system that occupy the most space. You can also use |
| 561 |
|
<prgn>deborphan</prgn> or <prgn>debfoster</prgn> to find obsolete |
| 562 |
|
packages (see <ref id="obsolete">) |
| 563 |
|
</p> |
| 564 |
|
</item> |
| 565 |
|
<item> |
| 566 |
|
<p> |
| 567 |
|
Remove packages that take up too much space and you do not have an |
| 568 |
|
immediate need for (you can always reinstall them after the |
| 569 |
|
upgrade). You can list packages that take up most of the disk space |
| 570 |
|
with <prgn>dpigs</prgn> (available in the |
| 571 |
|
<prgn>debian-goodies</prgn> package) or with <prgn>wajig</prgn> |
| 572 |
|
(running <prgn>wajig size</prgn>). |
| 573 |
|
</p> |
| 574 |
|
</item> |
| 575 |
|
<item> |
| 576 |
|
<p> |
| 577 |
|
Temporarily move to another system, or permanently remove, system |
| 578 |
|
logs residing under <file>/var/log/</file>. |
| 579 |
|
</p> |
| 580 |
|
</item> |
| 581 |
|
</list> |
| 582 |
|
</p> |
| 583 |
|
</sect1> |
| 584 |
|
<sect1 id="glibc-kernel"> |
| 585 |
|
<heading> |
| 586 |
|
Support for 2.2-kernels has been dropped |
| 587 |
|
</heading> |
| 588 |
|
<p> |
| 589 |
|
In case you run a kernel prior to 2.4.1, you need to upgrade to (at |
| 590 |
|
least) the 2.4-series before upgrading the <package>glibc</package>, |
| 591 |
|
which means: best before starting with the upgrade. It is recommended |
| 592 |
|
to upgrade to the 2.6-kernel series. |
| 593 |
|
</p> |
| 594 |
|
</sect1> |
| 595 |
|
<sect1 id="kernelorder"> |
| 596 |
|
<heading> |
| 597 |
|
Upgrade your kernel or userland first |
| 598 |
|
</heading> |
| 599 |
|
<p> |
| 600 |
|
[FIXME: Needs decision/documentation whether to upgrade userland or |
| 601 |
|
kernel first.] |
| 602 |
|
</p> |
| 603 |
|
</sect1> |
| 604 |
|
</sect> |
| 605 |
|
<sect id="system-status"> |
| 606 |
|
<heading> |
| 607 |
|
检查系统状态 |
| 608 |
|
</heading> |
| 609 |
|
<p> |
| 610 |
|
The upgrade process described in this chapter has been designed for |
| 611 |
|
upgrades from "pure" &oldreleasename; systems without 3rd party |
| 612 |
|
packages. It may be wise to remove these packages first. |
| 613 |
|
</p> |
| 614 |
|
<p> |
| 615 |
|
在此假定您的系统已经是最新版的&oldreleasename;。如果不是这样或您不清楚，请按<ref |
| 616 |
|
id="old-upgrade">操作。 |
| 617 |
|
</p> |
| 618 |
|
<sect1> |
| 619 |
|
<heading> |
| 620 |
|
禁用APT pinning(APT的一种用于安装特定版本软件包的功能——译者) |
| 621 |
|
</heading> |
| 622 |
|
<p> |
| 623 |
|
如果您配置了APT来安装非stable的特定软件包(例如从testing)，您应当改变APT |
| 624 |
|
pinning设置(在<file>/etc/apt/preferences</file>)。可在<manref |
| 625 |
|
section="5" name="apt_preferences">中找到APT pinning的详细信息。 |
| 626 |
|
</p> |
| 627 |
|
</sect1> |
| 628 |
|
<sect1> |
| 629 |
|
<heading> |
| 630 |
|
检查软件包状态 |
| 631 |
|
</heading> |
| 632 |
|
<p> |
| 633 |
|
不管用什么方法升级，建议您先检查所有软件包的状态，确认所有软件包都处在可升级状态。以下命令会显示任何错误状态，特别是安装不全或配置失败的软件包。 |
| 634 |
|
<example> |
| 635 |
# dpkg --audit |
# dpkg --audit |
| 636 |
</example></p> |
</example> |
| 637 |
|
</p> |
| 638 |
<p>您也可以使用<prgn/dselect/、<prgn/aptitude/或用命令 |
<p> |
| 639 |
<example> |
您也可以使用<prgn>dselect</prgn>、<prgn>aptitude</prgn>或用以下命令来检查您系统所有软件包的状态： |
| 640 |
|
<example> |
| 641 |
# dpkg -l | pager |
# dpkg -l | pager |
| 642 |
</example> |
</example> |
| 643 |
|
或 |
| 644 |
或 |
<example> |
|
|
|
|
<example> |
|
| 645 |
# dpkg --get-selections > ~/curr-pkgs.txt |
# dpkg --get-selections > ~/curr-pkgs.txt |
| 646 |
</example> |
</example> |
| 647 |
来检查您系统所有软件包的状态。</p> |
</p> |
| 648 |
|
<p> |
| 649 |
<p>在升级前移除任何hold(APT对软件的一种标记，它告诉APT不要自动替换这一软件包——译者)很必要。如果任何升级用的基本软件包处于hold状态，升级就会失败。您可以用 |
It is desirable to remove any holds before upgrading. If any package |
| 650 |
|
that is essential for the upgrade is on hold, the upgrade will fail. |
| 651 |
<example> |
</p> |
| 652 |
# dpkg --get-selections | grep hold |
<p> |
| 653 |
|
Note that <prgn>aptitude</prgn> uses a different method for |
| 654 |
|
registering packages that are on hold than <prgn>apt-get</prgn> and |
| 655 |
|
<prgn>dselect</prgn>. You can identify packages on hold for |
| 656 |
|
<prgn>aptitude</prgn> with |
| 657 |
|
<example> |
| 658 |
|
# aptitude search "~ahold" | grep "^.h" |
| 659 |
</example> |
</example> |
| 660 |
检查处于hold状态的软件包。</p> |
</p> |
| 661 |
|
<p> |
| 662 |
<p>如果您在本机修改并编译了一个软件包，且没有重命名或在版本号中加入epoch(软件包中自定义的版本号——译者)，您必须把它置为hold状态来防止它被更新。 |
如果您想查看用<prgn>apt-get</prgn>设定为保持的软件包，可以使用 |
| 663 |
|
<example> |
| 664 |
<![ %has-woody-aptitude [ |
# dpkg --get-selections | grep hold |
|
'hold'软件包状态可以用<prgn/aptitude/修改： |
|
|
|
|
|
<example> |
|
|
# aptitude hold | unhold <package name> |
|
|
</example> |
|
|
]]> |
|
|
|
|
|
<![ %no-woody-aptitude [ |
|
|
`hold'包状态可通用使用<prgn/dselect/改变(在Select菜单中用`H'和`G' 来标记'hold'和取消标记)，或编辑由 |
|
|
|
|
|
<example> |
|
|
# dpkg --get-selections > ~/curr-sels.txt |
|
| 665 |
</example> |
</example> |
| 666 |
|
</p> |
| 667 |
生成的文件，把"hold"改成"install"(反之亦然)，然后执行 |
<p> |
| 668 |
|
如果您在本机修改并编译了一个软件包，且没有重命名或在版本号中加入epoch(软件包中自定义的版本号——译者)，您必须把它置为hold状态来防止它被更新。 |
| 669 |
<example> |
</p> |
| 670 |
# dpkg --set-selections < ~/curr-sels.txt |
<p> |
| 671 |
|
<prgn>aptitude</prgn>中“hold"状态的包可以这样更改(将 <tt>hold</tt> |
| 672 |
|
替换为 <tt>unhold</tt>)： |
| 673 |
|
<example> |
| 674 |
|
# aptitude hold <var>package_name</var> |
| 675 |
</example> |
</example> |
| 676 |
]]> |
</p> |
| 677 |
</p> |
<p> |
| 678 |
|
如果需要修复，最好保证<file>sources.list</file>仍然指向 |
| 679 |
<p>如果需要修复，最好保证<file/sources.list/仍然指向 &oldreleasename;，正像在<ref id="old-sources">中解释的那样。</p> |
&oldreleasename;，正像在<ref id="old-sources">中解释的那样。 |
| 680 |
|
</p> |
| 681 |
</sect1> |
</sect1> |
| 682 |
|
<sect1 id="backports"> |
| 683 |
<sect1 id="backports"><heading>非官方源与backports（backports为Debian提供 不需要非Stable链接库就可在Stable版运行的新软件包，有效地弥补了Debian Stable版软件较旧的缺点－－译者）</heading> |
<heading> |
| 684 |
|
非官方源与backports（backports为Debian提供 |
| 685 |
<p>如果您在系统上使用非Debian软件包，请注意这些包可能在升级过程中由于包冲突而被删除。如果这些包是通过在<file>/etc/apt/sources.list</file>中加入非官方源安装的，您应检查这一非官方源是否提供为&releasename;编译的软件包，然后根据实际情况修改相应的行。</p> |
不需要非Stable链接库就可在Stable版运行的新软件包，有效地弥补了Debian |
| 686 |
|
Stable版软件较旧的缺点——译者） |
| 687 |
<p>一些用户在&oldreleasename;中使用非官方backport的较“新”软件包。这些包非常容易在升级中出错，因为它们很可能导致包冲突。<footnote>Debian的包管理系统一般不允许一个软件包中的文件替换另一包的文件；除非新的包被定义为那样做。</footnote><ref id="trouble">提供如何处理包冲突的办法。</p> |
</heading> |
| 688 |
|
<p> |
| 689 |
</sect1> |
如果您在系统上使用非Debian软件包，请注意这些包可能在升级过程中由于包冲突而被删除。如果这些包是通过在<file>/etc/apt/sources.list</file>中加入非官方源安装的，您应检查这一非官方源是否提供为&releasename;编译的软件包，然后根据实际情况修改相应的行。 |
| 690 |
</sect> |
</p> |
| 691 |
|
<p> |
| 692 |
<![ %glibcneedsnewkernel [ |
一些用户在&oldreleasename;中使用非官方backport的较“新”软件包。这些包非常容易在升级中出错，因为它们很可能导致包冲突。<footnote><p>Debian的包管理系统一般不允许一个软件包中的文件替换另一包的文件；除非新的包被定义为那样做。</p></footnote><ref |
| 693 |
<![ %not-mips-mipsel [ |
id="trouble">提供如何处理包冲突的办法。 |
| 694 |
|
</p> |
| 695 |
<sect id="new-kernel"> |
</sect1> |
| 696 |
<heading>检查内核支持</heading> |
</sect> |
| 697 |
|
<sect id="upgrade-process"> |
| 698 |
<![ %sparc [ |
<heading> |
| 699 |
<p>除去对内核支持的特殊考虑，所有64位的SPARC（sun4u）的计算机都是可升级的。</p> |
准备APT源 |
| 700 |
|
</heading> |
| 701 |
<p>sun4c处理器不再被&releasename;支持。对sun4d处理器的支持情况还不甚明了。很可很带有MMU的cun4d处理器可以正常工作。</p> |
<p> |
| 702 |
|
在升级之前，您必须在<file>/etc/apt/sources.list</file>中配置<package>apt</package>来生成软件包列表。 |
| 703 |
<p>sun4m处理器仍被支持，不过应当在升级之前先安装一个新一些的内核。这很必要，因为新版本的glibc使用一些机器不能识别的汇编指令，因此您应当更新内核来模拟机器内不存在的指令。</p> |
</p> |
| 704 |
|
<p> |
| 705 |
<p>技术上讲只有<em>一部分</em> sun4m芯片受影响，但是由于glibc不能可靠地检测出系统是否被影响，它会拒绝更新，除非安装一个新内核。</p> |
<package>apt</package>会以行先后顺序为优先级分析可通过"<tt>deb</tt>"行找到的所有软件包，然后安装具有最高版本号软件包。(这样，在具有许多镜像地址时，一般地，应先写入本地硬盘，然后CD-ROM，再然后HTTP/FTP镜像) |
| 706 |
|
</p> |
| 707 |
<p>一些确切消息：一些由Cypress/ROSS生产的sun4m芯片，不解释<tt>umul</tt>指令（RT601/CY7C601是同一芯片，仅名称不同）。它们被早期的SPARCserver 6xxMP型号使用。近期的型号使用TI生产的芯片。现在我们不知道这些芯片是否受影响。</p> |
<p> |
| 708 |
<!-- Add link to http://www.ultralinux.org/faq.html#q_2_1 ? --> |
一个发行版经常既可以由代号（如&oldreleasename;、&releasename;）也可由状态名（如oldstable、stable、testing、unstable）表示。用代号可使您不会对一个新发行版感到陌生，因此在本说明中我们使用代号。这当然意味着您自己必须关注新版的发行。如果使用状态名，您只会在新版发行时发现可升级的包。 |
| 709 |
]]><!--sparc--> |
</p> |
| 710 |
|
<sect1 id="network"> |
| 711 |
<![ %hppa [ |
<heading> |
| 712 |
<p>在64位HPPA机器上您应当在升级之前先安装一个新一些的内核。这很必要，因为新版本的glibc使用一些机器不能识别的汇编指令，因此您应当更新内核来模拟机器内不存在的指令。</p> |
添加Internet APT源 |
| 713 |
]]> |
</heading> |
| 714 |
<![ %i386 [ |
<p> |
| 715 |
<p>&releasename;不再支持80386处理器，但这不影响它对80486以上处理器的支持。</p> |
默认设置是从主Debian |
| 716 |
]]> |
Internet服务器安装，但是您也可以修改<file>/etc/apt/sources.list</file> |
| 717 |
|
来使用其它镜像，特别是网络上与您最近的镜像。 |
| 718 |
<![ %upgradekernel [ |
</p> |
| 719 |
<sect1 id="kernel-upgrade"><heading>升级内核</heading> |
<p> |
| 720 |
|
Debian HTTP或FTP镜像地址可在<url id="&url-debian-mirrors;"> |
| 721 |
<p>当且仅当前面章节提醒您需要在升级系统<em/之前/更新内核，您才应当这么做。</p> |
找到(查看"Full list of mirrors"部分)。HTTP服务器总体上比FTP服务器快。 |
| 722 |
|
</p> |
| 723 |
<p>Backports那里提供所有从&releasename;安装最新内核的工具。关于更新内核的详细说明可在<ref id="kernel-upgrade-howto">找到。</p> |
<p> |
| 724 |
|
例如，假设最近的镜像是<tt>&url-debian-mirror-eg;/</tt>当用浏览器或FTP工具访问它时，您会注意到主要目录是这样组织的： |
| 725 |
</sect1> |
<example> |
|
]]> |
|
|
</sect> |
|
|
]]><!-- not-mips-mipsel --> |
|
|
]]><!--glibcneedsnewkernel --> |
|
|
|
|
|
<sect id="upgrade-process"><heading>准备APT源</heading> |
|
|
|
|
|
<p>在升级之前，您必须在<file>/etc/apt/sources.list</file>中配置<package>apt</package>来生成软件包列表。</p> |
|
|
|
|
|
<p><package>apt</package>会以行先后顺序为优先级分析可通过"<tt>deb</tt>"行找到的所有软件包，然后安装具有最高版本号软件包。(这样，在具有许多镜像地址时，一般地，应先写入本地硬盘，然后CD-ROM，再然后HTTP/FTP镜像)</p> |
|
|
|
|
|
<p>一个发行版经常既可以由代号（如&oldreleasename;、&releasename;）也可由状态名（如oldstable、stable、testing、unstable）表示。用代号可使您不会对一个新发行版感到陌生，因此在本说明中我们使用代号。这当然意味着您自己必须关注新版的发行。如果使用状态名，您只会在新版发行时发现可升级的包。</p> |
|
|
|
|
|
<sect1 id="network"><heading>添加Internet APT源</heading> |
|
|
|
|
|
<p>默认设置是从主Debian Internet服务器安装，但是您也可以修改<file>/etc/apt/sources.list</file> 来使用其它镜像，特别是网络上与您最近的镜像。</p> |
|
|
|
|
|
<!-- FJP: Why is 'default configuration' relevant here? We are talking about |
|
|
upgrading existing installations; we really have no idea what |
|
|
apt-sources users will have set up here (maybe just a Woody CD-set). |
|
|
Note: D-I sets the default configuration to a mirror based on |
|
|
the selected country and not the 'main' servers. --> |
|
|
|
|
|
<p>Debian HTTP或FTP镜像地址可在<url id="&url-debian-mirrors;"> 找到(查看"Full list of mirrors"部分)。HTTP服务器总体上比FTP服务器快。</p> |
|
|
|
|
|
<p>例如，假设最近的镜像是<tt>&url-debian-mirror-eg;/</tt>当用浏览器或FTP工具访问它时，您会注意到主要目录是这样组织的： |
|
|
<example> |
|
| 726 |
&url-debian-mirror-eg;/dists/&releasename;/main/binary-&architecture;/... |
&url-debian-mirror-eg;/dists/&releasename;/main/binary-&architecture;/... |
| 727 |
&url-debian-mirror-eg;/dists/&releasename;/contrib/binary-&architecture;/... |
&url-debian-mirror-eg;/dists/&releasename;/contrib/binary-&architecture;/... |
| 728 |
</example></p> |
</example> |
| 729 |
|
</p> |
| 730 |
<p>为了让<prgn/apt/使用这一镜像，在<file/sources.list/中加入这一行： |
<p> |
| 731 |
|
为了让<prgn>apt</prgn>使用这一镜像，在<file>sources.list</file>中加入这一行： |
| 732 |
<example> |
<example> |
| 733 |
deb &url-debian-mirror-eg; &releasename; main contrib |
deb &url-debian-mirror-eg; &releasename; main contrib |
| 734 |
</example></p> |
</example> |
| 735 |
|
</p> |
| 736 |
<p>注意'<tt>dists</tt>'被自动隐含地添加了，且在发行版名称之后的参数被用来把安装路径扩展到不同目录中。</p> |
<p> |
| 737 |
|
#-#-#-#-# choice #-#-#-#-# |
| 738 |
<p>添加了新APT源之后，用井号(<tt>#</tt>)添在行前以把 <file>sources.list</file>中已有的"<tt>deb</tt>"行禁用。</p> |
注意'<tt>dists</tt>'被自动隐含地添加了，且在发行版名称之后的参数被用来把安装路径扩展到不同目录中。 |
| 739 |
|
#-#-#-#-# choice #-#-#-#-# |
| 740 |
<p>所有从网上下载的软件包都被储存在<file>/var/cache/apt/archives</file>(以及在下载进程中的<file>partial/</file>)，所以在开始安装之前您必须确保有足够的空间。对于一个适当扩展的Debian安装，至少要有300MB的下载数据。</p> |
注意`<tt>dists</tt>' |
| 741 |
|
被自动隐含地添加了，且在发行版名称之后的参数被用来把安装路径扩展到不同目录中。 |
| 742 |
</sect1> |
</p> |
| 743 |
|
<p> |
| 744 |
<sect1 id="localmirror"><heading>添加本地APT源</heading> |
#-#-#-#-# choice #-#-#-#-# |
| 745 |
|
添加了新APT源之后，用井号(<tt>#</tt>)添在行前以把 |
| 746 |
<p>您可以修改<file>/etc/apt/sources.list</file>来使用本地驱动器(可能是挂载的NFS分区)上的镜像。</p> |
<file>sources.list</file>中已有的"<tt>deb</tt>"行禁用。 |
| 747 |
|
#-#-#-#-# choice #-#-#-#-# |
| 748 |
<p>例如，您的镜像在<file>/var/ftp/debian/</file>，它有这样的主目录： |
添加了新APT源之后，用井号 (<tt>#</tt>)添在行前以把 |
| 749 |
|
<file>sources.list</file>中已有的"<tt>deb</tt>"行禁用。 |
| 750 |
<example> |
</p> |
| 751 |
|
<p> |
| 752 |
|
所有从网上下载的软件包都被储存在<file>/var/cache/apt/archives</file>(以及在下载进程中的<file>partial/</file>)，所以在开始安装之前您必须确保有足够的空间。对于一个适当扩展的Debian安装，至少要有300MB的下载数据。 |
| 753 |
|
</p> |
| 754 |
|
</sect1> |
| 755 |
|
<sect1 id="localmirror"> |
| 756 |
|
<heading> |
| 757 |
|
添加本地APT源 |
| 758 |
|
</heading> |
| 759 |
|
<p> |
| 760 |
|
您可以修改<file>/etc/apt/sources.list</file>来使用本地驱动器(可能是挂载的NFS分区)上的镜像。 |
| 761 |
|
</p> |
| 762 |
|
<p> |
| 763 |
|
例如，您的镜像在<file>/var/ftp/debian/</file>，它有这样的主目录： |
| 764 |
|
<example> |
| 765 |
/var/ftp/debian/dists/stable/main/binary-&architecture;/... |
/var/ftp/debian/dists/stable/main/binary-&architecture;/... |
| 766 |
/var/ftp/debian/dists/stable/contrib/binary-&architecture;/... |
/var/ftp/debian/dists/stable/contrib/binary-&architecture;/... |
| 767 |
</example></p> |
</example> |
| 768 |
|
</p> |
| 769 |
<p>要让<prgn>apt</prgn>使用它，在<file>sources.list</file>中加入这一行： |
<p> |
| 770 |
|
要让<prgn>apt</prgn>使用它，在<file>sources.list</file>中加入这一行： |
| 771 |
<example> |
<example> |
| 772 |
deb file:/var/ftp/debian &releasename; main contrib |
deb file:/var/ftp/debian &releasename; main contrib |
| 773 |
</example></p> |
</example> |
| 774 |
|
</p> |
| 775 |
<p>注意`<tt>dists</tt>' 被自动隐含地添加了，且在发行版名称之后的参数被用来把安装路径扩展到不同目录中。</p> |
<p> |
| 776 |
|
#-#-#-#-# choice #-#-#-#-# |
| 777 |
<p>添加了新APT源之后，用井号 (<tt>#</tt>)添在行前以把 <file>sources.list</file>中已有的"<tt>deb</tt>"行禁用。</p></sect1> |
注意'<tt>dists</tt>'被自动隐含地添加了，且在发行版名称之后的参数被用来把安装路径扩展到不同目录中。 |
| 778 |
|
#-#-#-#-# choice #-#-#-#-# |
| 779 |
<sect1 id="cdroms"><heading>添加CD-ROM或DVD APT源</heading> |
注意`<tt>dists</tt>' |
| 780 |
|
被自动隐含地添加了，且在发行版名称之后的参数被用来把安装路径扩展到不同目录中。 |
| 781 |
<p>如果只想使用CD-ROM，那就把<file/sources.list/中已有的<tt/deb/" 行用"<tt/#/"注释掉。</p> |
</p> |
| 782 |
|
<p> |
| 783 |
<!-- Default cdrom mount point is /cdrom, not /media/cdrom and fixed!, see #282344 |
#-#-#-#-# choice #-#-#-#-# |
| 784 |
(but the -d option of apt-cdrom allows scanning from somewhere else) --> |
添加了新APT源之后，用井号(<tt>#</tt>)添在行前以把 |
| 785 |
|
<file>sources.list</file>中已有的"<tt>deb</tt>"行禁用。 |
| 786 |
<p>确保<file>/etc/fstab</file>中有允许在<file>/cdrom</file>挂载CD-ROM的一行(<prgn>apt-cdrom</prgn>需要使用<file>/cdrom</file>挂载点)。例如，如果<file>/dev/hdc</file>是您的CD-ROM驱动器，<file>/etc/fstab</file>应包含这样一行： |
#-#-#-#-# choice #-#-#-#-# |
| 787 |
|
添加了新APT源之后，用井号 (<tt>#</tt>)添在行前以把 |
| 788 |
<example> |
<file>sources.list</file>中已有的"<tt>deb</tt>"行禁用。 |
| 789 |
|
</p> |
| 790 |
|
</sect1> |
| 791 |
|
<sect1 id="cdroms"> |
| 792 |
|
<heading> |
| 793 |
|
添加CD-ROM或DVD APT源 |
| 794 |
|
</heading> |
| 795 |
|
<p> |
| 796 |
|
如果只想使用CD-ROM，那就把<file>sources.list</file>中已有的<tt>deb</tt>" |
| 797 |
|
行用"<tt>#</tt>"注释掉。 |
| 798 |
|
</p> |
| 799 |
|
<p> |
| 800 |
|
确保<file>/etc/fstab</file>中有允许在<file>/cdrom</file>挂载CD-ROM的一行(<prgn>apt-cdrom</prgn>需要使用<file>/cdrom</file>挂载点)。例如，如果<file>/dev/hdc</file>是您的CD-ROM驱动器，<file>/etc/fstab</file>应包含这样一行： |
| 801 |
|
<example> |
| 802 |
/dev/hdc /cdrom auto defaults,noauto,ro 0 0 |
/dev/hdc /cdrom auto defaults,noauto,ro 0 0 |
| 803 |
</example></p> |
</example> |
| 804 |
|
</p> |
| 805 |
<p>注意在第四部分的”<tt>defaults,noauto,ro</tt>”中，词之间不能有任何空格。</p> |
<p> |
| 806 |
|
注意在第四部分的”<tt>defaults,noauto,ro</tt>”中，词之间不能有任何空格。 |
| 807 |
<p>要确认它有效，插入一张CD： |
</p> |
| 808 |
|
<p> |
| 809 |
<example> |
要确认它有效，插入一张CD： |
| 810 |
|
<example> |
| 811 |
# mount /cdrom # 挂载CD-ROM |
# mount /cdrom # 挂载CD-ROM |
| 812 |
# ls -alF /cdrom # 显示CD根目录 |
# ls -alF /cdrom # 显示CD根目录 |
| 813 |
# umount /cdrom # 卸载CD-ROM |
# umount /cdrom # 卸载CD-ROM |
| 814 |
</example></p> |
</example> |
| 815 |
|
</p> |
| 816 |
<p>下一步，对于您拥有的每一张Debian Binary CD-ROM运行 |
<p> |
| 817 |
|
下一步，对于您拥有的每一张Debian Binary CD-ROM运行 |
| 818 |
<example> |
<example> |
| 819 |
# apt-cdrom add |
# apt-cdrom add |
| 820 |
</example> |
</example> |
| 821 |
|
来向APT的数据库添加每一CD的信息。 |
| 822 |
来向APT的数据库添加每一CD的信息。</p> |
</p> |
| 823 |
</sect1> |
</sect1> |
| 824 |
</sect> |
</sect> |
| 825 |
|
<sect id="upgradingpackages"> |
| 826 |
<sect id="upgradingpackages"><heading>升级软件包</heading> |
<heading> |
| 827 |
|
升级软件包 |
| 828 |
<p>建议使用<prgn>aptitude</prgn>来全面升级系统。这一工具会做出比直接执行<prgn>apt-get</prgn>更安全的升级决定。</p> |
</heading> |
| 829 |
|
<p> |
| 830 |
<p>不要忘记以读写模式挂载所有分区(一般是root和<file>/usr</file>分区)： |
The recommended way to upgrade from previous &debian; releases is to |
| 831 |
|
use the package management tool <prgn>aptitude</prgn>. This program |
| 832 |
<example> |
makes safer decisions about package installations than running |
| 833 |
|
<prgn>apt-get</prgn> directly. |
| 834 |
|
</p> |
| 835 |
|
<p> |
| 836 |
|
不要忘记以读写模式挂载所有分区(一般是root和<file>/usr</file>分区)： |
| 837 |
|
<example> |
| 838 |
# mount -o remount,rw /<var>mountpoint</var> |
# mount -o remount,rw /<var>mountpoint</var> |
| 839 |
</example></p> |
</example> |
| 840 |
|
</p> |
| 841 |
<p>下一步确保APT源(<file>/etc/apt/sources.list</file>)指向"<tt/&releasename;/"或"<tt/stable/"。注意：CD-ROM经常被表示为"<tt/unstable/";虽然这令人迷惑，但<em/不要/修改它。</p> |
<p> |
| 842 |
|
下一步确保APT源(<file>/etc/apt/sources.list</file>)指向"<tt>&releasename;</tt>"或"<tt>stable</tt>"。注意：CD-ROM经常被表示为"<tt>unstable</tt>";虽然这令人迷惑，但<em>不要</em>修改它。 |
| 843 |
<p>强烈建议您使用<prgn>/usr/bin/script</prgn>程序来记录一个升级过程的信息副本。这样如果出现问题，您就有一个日志来验看发生了什么，而且如果需要的话，这可以提供bug报告的确切信息。输入： |
</p> |
| 844 |
<example> |
<p> |
| 845 |
|
强烈建议您使用<prgn>/usr/bin/script</prgn>程序来记录一个升级过程的信息副本。这样如果出现问题，您就有一个日志来验看发生了什么，而且如果需要的话，这可以提供bug报告的确切信息。输入： |
| 846 |
|
<example> |
| 847 |
# script -a ~/upgrade-to-&releasename;.typescript |
# script -a ~/upgrade-to-&releasename;.typescript |
| 848 |
</example> |
</example> |
| 849 |
或类似的命令来开始记录。不要把记录文件放在临时目录中，如<file>/tmp</file>或<file>/var/tmp</file>(在这些目录中的文件会在升级或重启动过程中被删除)。</p> |
或类似的命令来开始记录。不要把记录文件放在临时目录中，如<file>/tmp</file>或<file>/var/tmp</file>(在这些目录中的文件会在升级或重启动过程中被删除)。 |
| 850 |
|
</p> |
| 851 |
<p>typescript允许您浏览已经滚过屏幕的提示信息。只要转到VT2（Virtual Terminal 2－－译者）（使用<tt/alt-F2/），登录以后，用<tt>less ~/upgrade-to-&releasename;.typescript</tt>查看。</p> |
<p> |
| 852 |
|
typescript允许您浏览已经滚过屏幕的提示信息。只要转到VT2（Virtual |
| 853 |
<p>升级完成之后，您可以输入<tt/exit/命令来结束<prgn/script/。</p> |
Terminal 2——译者）（使用<tt>alt-F2</tt>），登录以后，用<tt>less |
| 854 |
|
~/upgrade-to-&releasename;.typescript</tt>查看。 |
| 855 |
<sect1 id="updating_lists"><heading>更新包列表</heading> |
</p> |
| 856 |
|
<p> |
| 857 |
<p>首先需要取得新发行版的软件包列表：<footnote>我们使用<prgn/apt-get/因为&oldreleasename;中的<prgn/aptitude/可能在新源加入<file/sources.list/时出错。</footnote></p> |
升级完成之后，您可以输入<tt>exit</tt>命令来结束<prgn>script</prgn>。 |
| 858 |
|
</p> |
| 859 |
<p><example> |
<sect1 id="updating_lists"> |
| 860 |
|
<heading> |
| 861 |
|
更新包列表 |
| 862 |
|
</heading> |
| 863 |
|
<p> |
| 864 |
|
首先需要取得新发行版的软件包列表：<footnote><p>我们使用<prgn>apt-get</prgn>因为&oldreleasename;中的<prgn>aptitude</prgn>可能在新源加入<file>sources.list</file>时出错。</p></footnote> |
| 865 |
|
</p> |
| 866 |
|
<p> |
| 867 |
|
<example> |
| 868 |
# apt-get update |
# apt-get update |
| 869 |
</example></p> |
</example> |
| 870 |
|
</p> |
| 871 |
</sect1> |
</sect1> |
| 872 |
|
<sect1 id="upgrading_aptitude"> |
| 873 |
<![ %mips-mipsel [ |
<heading> |
| 874 |
<sect1 id="upgrading_kernel_mipsen"><heading>升级内核</heading> |
升级aptitude |
| 875 |
|
</heading> |
| 876 |
<p>在&arch-title;机器上有必要在升级系统之前先升级内核。新libc库与内核有不一致的指令定义，所以需要新内核来提供正确的指令定义。</p> |
<p> |
| 877 |
|
升级测试表明&releasename;的<prgn>aptitude</prgn>在解决复杂依赖关系时比<prgn>apt-get</prgn>或&oldreleasename;的<prgn>aptitude</prgn>更出色。所以首先应升级它： |
| 878 |
<p>关于怎样安装新内核可参阅<ref id="kernel-upgrade-howto">。</p> |
<example> |
|
|
|
|
</sect1> |
|
|
]]> |
|
|
|
|
|
<!-- FJP: This next section can probably be dropped for etch --> |
|
|
<![ %has-woody-aptitude [ |
|
|
<sect1 id="upgrading_aptitude"><heading>升级aptitude</heading> |
|
|
]]> |
|
|
<![ %no-woody-aptitude [ |
|
|
<sect1 id="upgrading_aptitude"><heading>安装aptitude</heading> |
|
|
]]> |
|
|
|
|
|
<p>升级测试表明&releasename;的<prgn/aptitude/在解决复杂依赖关系时比<prgn/apt-get/或&oldreleasename;的<prgn/aptitude/更出色。 |
|
|
|
|
|
<![ %has-woody-aptitude [ |
|
|
所以首先应升级它： |
|
|
<example> |
|
| 879 |
# aptitude install aptitude |
# aptitude install aptitude |
| 880 |
</example></p> |
</example> |
| 881 |
]]><!--has-woody-aptitude--> |
</p> |
| 882 |
<![ %no-woody-aptitude [ |
<p> |
| 883 |
所以它应先升级： |
您会看到一些关于将要进行的修改的提示信息，并被问到是否确认。在确认之前，您应仔细查看要进行的更改，特别是在升级过程中即将被删除的包。 |
| 884 |
<example> |
</p> |
| 885 |
# apt-get install aptitude |
<p> |
| 886 |
</example></p> |
某些时候，如果很多软件包被列出来准备删除，您可用<package>aptitude</package>事先升级某些软件来缓解这种情况。举一个例子：当对装有KDE的系统进行检查时，我们会注意到这一过程会删除很多KDE和perl包。这时可以先把perl连同<package>aptitude</package>一起升级来解决。 |
| 887 |
]]> |
</p> |
| 888 |
|
</sect1> |
| 889 |
<p>您会看到一些关于将要进行的修改的提示信息，并被问到是否确认。在确认之前，您应仔细查看要进行的更改，特别是在升级过程中即将被删除的包。</p> |
<sect1 id="upgrading_other"> |
| 890 |
|
<heading> |
| 891 |
<p>某些时候，如果很多软件包被列出来准备删除，您可用<package/aptitude/事先升级某些软件来缓解这种情况。举一个例子：当对装有KDE的系统进行检查时，我们会注意到这一过程会删除很多KDE和perl包。这时可以先把perl连同<package/aptitude/一起升级来解决。</p> |
升级系统的其它部分 |
| 892 |
|
</heading> |
| 893 |
</sect1> |
<p> |
| 894 |
|
您现在已经一切就绪来进行升级的主要部分，运行 |
| 895 |
<sect1 id="upgrading_doc-base"><heading>升级doc-base</heading> |
</p> |
| 896 |
|
<p> |
| 897 |
<p><em>如果装有<package/doc-base/</em>，它也必须在系统升级之前被更新。原因是它会在<package/perl/升级时出错。您可以用</p> |
<example> |
|
|
|
|
<p><example> |
|
|
# dpkg -l doc-base |
|
|
</example></p> |
|
|
|
|
|
<p>检查它是否已安装。如果输出行以'i'开头表明它已安装，此时必须在进一步工作之前升级它：</p> |
|
|
|
|
|
<p><example> |
|
|
# aptitude install doc-base |
|
|
</example></p> |
|
|
|
|
|
</sect1> |
|
|
|
|
|
<sect1 id="upgrading_other"><heading>升级系统的其它部分</heading> |
|
|
|
|
|
<p>您现在已经一切就绪来进行升级的主要部分，运行</p> |
|
|
<p><example> |
|
| 898 |
# aptitude -f --with-recommends dist-upgrade |
# aptitude -f --with-recommends dist-upgrade |
| 899 |
</example></p> |
</example> |
| 900 |
|
</p> |
| 901 |
<p>将进行完整的系统升级，也就是说，安装所有最新版本的软件包并解决所有可能的包依赖关系变化问题。如果必要，它会安装一些新软件包(通常是新的链接库，或改名的软件包)，移除任何有冲突的旧包(如<package>console-tools-libs</package>)。</p> |
<p> |
| 902 |
|
将进行完整的系统升级，也就是说，安装所有最新版本的软件包并解决所有可能的包依赖关系变化问题。如果必要，它会安装一些新软件包(通常是新的链接库，或改名的软件包)，移除任何有冲突的旧包(如<package>console-tools-libs</package>)。 |
| 903 |
<p>当从一组CD-ROM升级时，您会被要求在特定时期插入特定CD。可能必须多次插入同一CD，这取决于分布于CD中的软件包内部关系。</p> |
</p> |
| 904 |
|
<p> |
| 905 |
<p>只有改变其它包状态才能被更新的软件包会被保留为当前版本(显示为'held back'状态)。这可以通过使用<prgn>aptitude</prgn>来选择这些包来安装或输入<tt>aptitude -f install |
当从一组CD-ROM升级时，您会被要求在特定时期插入特定CD。可能必须多次插入同一CD，这取决于分布于CD中的软件包内部关系。 |
| 906 |
<var>package</var></tt>来解决。</p> |
</p> |
| 907 |
|
<p> |
| 908 |
<p><tt>--fix-broken</tt> (或只是<tt>-f</tt>)设置项使 |
只有改变其它包状态才能被更新的软件包会被保留为当前版本(显示为'held |
| 909 |
<package>apt</package>尝试修复系统中的依赖性错误。<package>apt</package>不允许系统中存在未满足的包依赖关系。</p> |
back'状态)。这可以通过使用<prgn>aptitude</prgn>来选择这些包来安装或输入<tt>aptitude |
| 910 |
|
-f install <var>package</var></tt>来解决。 |
| 911 |
</sect1> |
</p> |
| 912 |
|
<p> |
| 913 |
<sect1 id="trouble"><heading>升级过程中可能出现的问题</heading> |
<tt>--fix-broken</tt> (或只是<tt>-f</tt>)设置项使 |
| 914 |
|
<package>apt</package>尝试修复系统中的依赖性错误。<package>apt</package>不允许系统中存在未满足的包依赖关系。 |
| 915 |
<p>如果在使用<prgn/aptitude/、<prgn/apt-get/或<prgn/dpkg/时出现如下错误 |
</p> |
| 916 |
<example> |
</sect1> |
| 917 |
|
<sect1 id="trouble"> |
| 918 |
|
<heading> |
| 919 |
|
升级过程中可能出现的问题 |
| 920 |
|
</heading> |
| 921 |
|
<p> |
| 922 |
|
如果在使用<prgn>aptitude</prgn>、<prgn>apt-get</prgn>或<prgn>dpkg</prgn>时出现如下错误 |
| 923 |
|
<example> |
| 924 |
E: Dynamic MMap ran out of room |
E: Dynamic MMap ran out of room |
| 925 |
</example> |
</example> |
| 926 |
那是因为默认的缓冲区太小。解决办法有二：移除<file>/etc/apt/sources.list</file>中的多余行，增大缓冲区。缓冲区大小可通过<file>/etc/apt/apt.conf</file>中的<tt/APT::Cache-Limit/设定。假设现有<file>/etc/apt/apt.conf</file>中未设定这一变量，可以这样做： |
那是因为默认的缓冲区太小。解决办法有二：移除<file>/etc/apt/sources.list</file>中的多余行，增大缓冲区。缓冲区大小可通过<file>/etc/apt/apt.conf</file>中的<tt>APT::Cache-Limit</tt>设定。假设现有<file>/etc/apt/apt.conf</file>中未设定这一变量，可以这样做： |
| 927 |
<example> |
<example> |
| 928 |
# echo 'APT::Cache-Limit "12500000";' >> /etc/apt/apt.conf |
# echo 'APT::Cache-Limit "12500000";' >> /etc/apt/apt.conf |
| 929 |
</example></p> |
</example> |
| 930 |
|
This assumes that you do not yet have this variable set in that file. |
| 931 |
<p>启用APT::Force-LoopBreak设置来临时移除在Conflicts/Pre-Depends(A Conflicts B表示A、B不能同时被安装，A Pre-Depends B表示安装A之前必须安装B——译者)循环中的一个基本软件包有时很必要。<prgn>aptitude</prgn>将警告您这种情况并终止升级。您可以通过在<prgn>aptitude</prgn>命令行中加入<tt>-o APT::Force-LoopBreak=1</tt>设置来实现。</p> |
</p> |
| 932 |
<!-- JFS: Shouldn't this mention also Apt's configuration file? --> |
<p> |
| 933 |
|
启用APT::Force-LoopBreak设置来临时移除在Conflicts/Pre-Depends(A |
| 934 |
<p>很有可能的是，系统依赖性结构会非常混乱而需要手动干预。通常这要使用<prgn>aptitude</prgn>或 |
Conflicts B表示A、B不能同时被安装，A Pre-Depends |
| 935 |
|
B表示安装A之前必须安装B——译者)循环中的一个基本软件包有时很必要。<prgn>aptitude</prgn>将警告您这种情况并终止升级。您可以通过在<prgn>aptitude</prgn>命令行中加入<tt>-o |
| 936 |
<example> |
APT::Force-LoopBreak=1</tt>设置来实现。 |
| 937 |
# dpkg --remove <var>packagename</var> |
</p> |
| 938 |
|
<p> |
| 939 |
|
很有可能的是，系统依赖性结构会非常混乱而需要手动干预。通常这要使用<prgn>aptitude</prgn>或 |
| 940 |
|
<example> |
| 941 |
|
# dpkg --remove <var>package_name</var> |
| 942 |
</example> |
</example> |
| 943 |
|
来去除这些不友好的软件包，或者 |
| 944 |
来去除这些不友好的软件包，或者 |
<example> |
|
|
|
|
<example> |
|
| 945 |
# aptitude --fix-broken install |
# aptitude --fix-broken install |
| 946 |
# dpkg --configure --pending |
# dpkg --configure --pending |
| 947 |
</example></p> |
</example> |
| 948 |
|
</p> |
| 949 |
<p>在极端情况下您可能要用 |
<p> |
| 950 |
|
在极端情况下您可能要使用以下命令强行重新安装： |
| 951 |
<example> |
<example> |
| 952 |
# dpkg --install <var>/path/to/packagename.deb</var> |
# dpkg --install <var>/path/to/package_name.deb</var> |
| 953 |
</example>强行重新安装。</p> |
</example> |
| 954 |
|
</p> |
| 955 |
<p>如果从"纯"&oldreleasename;升级，包冲突问题不会出现，但若使用非官方 backport包则会出现该问题。包冲突会造成如下错误： |
<p> |
| 956 |
|
如果从"纯"&oldreleasename;升级，包冲突问题不会出现，但若使用非官方 |
| 957 |
<example> |
backport包则会出现该问题。包冲突会造成如下错误： |
| 958 |
|
<example> |
| 959 |
Unpacking replacement <var><package-foo></var> ... |
Unpacking replacement <var><package-foo></var> ... |
| 960 |
dpkg: error processing <var><package-name-for-foo></var> (--unpack): |
dpkg: error processing <var><package-name-for-foo></var> (--unpack): |
| 961 |
trying to overwrite `<var><some-file-name></var>', |
trying to overwrite `<var><some-file-name></var>', |
| 962 |
which is also in package <var><package-bar></var> |
which is also in package <var><package-bar></var> |
|
</example></p> |
|
|
|
|
|
<p>您可以强行删除出错信息<em/最后/一行的软件包： |
|
|
|
|
|
<example> |
|
|
# dpkg -r --force-depends <var>packagename</var> |
|
|
</example></p> |
|
|
|
|
|
<p>修好之后，您应可以通过上面提到的<tt>aptitude</tt>命令方法恢复升级过程。</p> |
|
|
|
|
|
<p>在升级过程中，您会被问一些问题来配置或重新配置部分软件包。如果您被问到任何在<file>/etc/init.d</file>或<file>/etc/terminfo</file>目录中的文件，或<file>/etc/manpath.config</file>文件是否应被包维护者的文件替代时，通常回答'yes'很必要。您可以在任意时候转回旧的文件，因为它们会被标以 <tt>.dpkg-old</tt>扩展名储存。</p> |
|
|
|
|
|
<p>如果您不知道应该做什么，记下软件包或者文件的名字，再在升级后解决这些问题。您可以搜索日志文件来复查升级过程中显示的屏幕信息。</p> |
|
|
</sect1> |
|
|
</sect> |
|
|
|
|
|
<sect id="nownownow"><heading>重启前的任务</heading> |
|
|
|
|
|
<p>当<tt>aptitude dist-upgrade</tt>完成时，“前期”升级就已经结束了，但是在重启之前还有许多其它事情要做。</p> |
|
|
|
|
|
<p>阅读<file>/usr/share/doc/xfree86-common/README.Debian-upgrade.gz</file>来获取X视窗系统的详细系统升级信息。它与所有的先前Debian发行版用户相关。简短地讲，您需要阅读它!</p> |
|
|
|
|
|
<sect1 id="newkernel"><heading>升级内核</heading> |
|
|
|
|
|
<p>注意在这些步骤中Linux内核没有被更新。您应该自己去做，通过安装<package>kernel-image-*</package> 软件包或者通过从原代码编译自定的内核。</p> |
|
|
<!-- JFS: This is not strictly true, if the user was using a non-versioned |
|
|
kernel (kernel-image-2.4-686) he _will_ upgrade the kernel if using |
|
|
aptitude (post-sarge) --> |
|
|
|
|
|
<![ %available-2.6 [ |
|
|
|
|
|
<p>&debian;带有稳定的旧Linux 2.4系列中的&kernelversion;内核。为了实现更好的硬件支持或更高的性能，您可以使用2.6系列的内核。</p> |
|
|
|
|
|
<p>但是，<strong/不要/把升级到2.6内核看作从&oldreleasename;升级的一部分。关于升级到2.6内核的问题可在<ref id="upgrade-to-2.6">中找到。</p> |
|
|
|
|
|
]]> |
|
|
|
|
|
<p>为升级内核，您必须尽量选择适合您计算机的内核。可以用 |
|
|
|
|
|
<example> |
|
|
# apt-cache search ^kernel-image |
|
|
</example>来获取您可以使用的内核列表。</p> |
|
|
|
|
|
<p>然后您应该使用<tt>aptitude install</tt>来安装它。一旦新内核被安装，您应该重启来使用它，享受它的新功能。</p> |
|
|
|
|
|
<p>请注意&oldreleasename;(及以前的发行版)不以软件包的形式安装内核。在&releasename;中有所改变，您可以安装虚拟软件包来跟踪内核变化。这些软件包被命名为kernel-image-<tt>VERSION</tt>-<tt>ARCH</tt>，<tt>VERSION</tt>与内核版本（2.4或2.6）对应，<tt>ARCH</tt>与可用的系统架构对应。如果您想给包管理的内核使用安全支持（Debian针对系统安全提供的即时升级－－译者），请安装最适合您系统的内核软件包。</p> |
|
|
|
|
|
<p>如果要更刺激，有一种简单的方法来编译您自己定制的内核。安装<package>kernel-package</package>工具然后阅读<file>/usr/share/doc/kernel-package</file>中的文档。</p> |
|
|
|
|
|
</sect1> |
|
|
</sect> |
|
|
|
|
|
<sect id="obsolete"><heading>废弃的软件包</heading> |
|
|
|
|
|
<!-- JFS: Providing a full listing might be useful, especially if we can |
|
|
point to the Bug that was opened when the bug was removed. This list should |
|
|
be moved to an appendix, instead of adding it inline as we did in the |
|
|
potato to woody RN --> |
|
|
|
|
|
<p>&releasename;不但新引入了几千个新软件包，也废弃了200多个在&oldreleasename;中的旧软件包。它不为这些废弃软件包提供升级补丁。不过这不影响您在必要时继续使用废弃的软件包，Debian项目通常在&releasename;发布一年后停止对它们的安全支持<footnote>或者在&releasename;后新发行版发布时停止， 一般只能有两个stable发行版同时被支持。</footnote>，而且这期间不会提供其它支持。如果可以的话，就应把它们换为的替代软件。</p> |
|
|
|
|
|
<p>软件包被移去有很多原因：不再被上游开发者维护或没有Debian开发者（即DD－－译者）愿意维护；功能被其它软件或新版本更好地取代；错误太严重。在最后一个原因中，软件包很可能还属于unstable。</p> |
|
|
|
|
|
<p>包管理软件会标注出来哪些软件包被废弃，查看这方面信息十分容易。如果用<prgn>aptitude</prgn>，您会在"Obsolete and Locally Created Packages"部分见到这些软件包的列表。<prgn>dselect</prgn>提供一个类似的列表，不过可能有些差异。另外，如果您使用<prgn>aptitude</prgn>手动安装了&oldreleasename;中的软件包，它会记录您手动安装的包并且在包被删除时把由于依赖关系而被安装的包标记为废弃。而且，不像<prgn>deborphan</prgn>，<prgn>aptitude</prgn>不会把您手动安装的包标记为废弃，这不同于由于依赖关系而被自动安装的包。</p> |
|
|
|
|
|
<p>有许多寻找废弃软件包的附加工具，比如<prgn>deborphan</prgn>、 <prgn>debfoster</prgn>和<prgn>cruft</prgn>。 推荐使用<prgn>deborphan</prgn>，虽然它只报告"libs"和"oldlibs"中的废弃链接库。不要随意删除这些工具显示的软件包，特别是当您使用冒犯性的非默认设置时，它们很容易造成假象。推荐在删除之前仔细查看包的信息（内容，大小和描述）。</p> |
|
|
|
|
|
<!-- JFS: Should we recommend purging old packages? This might be |
|
|
dangerous since the maintainer scripts might try to remove stuff that |
|
|
didn't belong to them... --> |
|
|
|
|
|
<p><url id="&url-bts;" name="Debian错误跟踪系统">经常提供包被移除的原因。您应阅读软件本身的bug报告和<url id="&url-bts;cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&archive=yes" name="ftp.debian.org pseudo-package">的bug报告。</p> |
|
|
|
|
|
<sect1 id="dummy"><heading>Dummy包</heading> |
|
|
|
|
|
<!-- JFS: If the appendix is kept this section should point there and the packages described here should be moved to that section --> |
|
|
|
|
|
<p>一些&oldreleasename;中的软件包在&releasename;中被分成几部分，以提高系统的易维护性。为了简化升级，&releasename;经常提供通过依赖关系安装其它新包的"dummy"包－－与&oldreleasename;包有相同名称的空包。"dummy"包在升级后就没用了，可以安全地删除。 |
|
|
|
|
|
<p>大多数（不是所有）的dummy包的描述部分说明它们的目的。但是，包描述信息不是唯一的，所以您可能会发现<prgn>deborphan</prgn>加上<tt>--guess</tt>选项对寻找这些包有用。注意有些dummy包在升级后不会被删除，它们被用来记录一个程序的可用版本。</p> |
|
|
|
|
|
</chapt> |
|
|
|
|
|
<!-- FJP: Add more info here on dealing with obsolete packages? |
|
|
Also how to purge packages that were deleted but still have conffiles |
|
|
(use "limit" command in aptitude and search for ~c) --> |
|
|
|
|
|
<chapt id="information"> |
|
|
<heading>在&releasename;中应注意的问题</heading> |
|
|
|
|
|
<!-- 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@euro) |
|
|
unfortunately use an aesthetically unpleasing way of representing |
|
|
open quotation marks. We have retained it this way in order to |
|
|
preserve compatibility with other Linux distributions, and we hope |
|
|
that in the future it will be fixed. We suggest that you switch to a |
|
|
UTF-8 locale (e.g. de_DE@euro.UTF-8), which fully supports German with |
|
|
the correct quotation marks, and, using Unicode encoding, has better |
|
|
support for other languages as well.</p> |
|
|
|
|
|
<p>To change the system wide locale choice, use: |
|
|
<example>dpkg-reconfigure locales</example></p> |
|
|
</sect> |
|
|
--> |
|
|
<!-- 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 |
|
|
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> |
|
|
--> |
|
|
<sect id="pythonchanges"><heading>Python软件包的变化</heading> |
|
|
|
|
|
<p>任何&releasename;的python2.X软件包都不包含'profile'和'pstats'模块，因为它们注册在一个不与DFSG相容的许可协议下(详情查看bug#293932)。这两个模块可在Debian archive的non-free部分中以python-profiler和python 2.X-profiler软件包的形式找到。</p> |
|
|
</sect> |
|
|
|
|
|
<![ %available-2.6 [ |
|
|
<sect id="upgrade-to-2.6"> |
|
|
<heading>升级到2.6内核</heading> |
|
|
|
|
|
<p>2.6系列内核与2.4系列相比有重大改变。模块被改名，许多驱动程序被部分或全部改写。因此升级到2.6内核不那么容易。这一部分旨在让您了解一些需要注意的地方。</p> |
|
|
|
|
|
<p>强烈建议您不要把升级到2.6内核当作从&oldreleasename;升级到&releasename;的一部分。您应该确保系统在原有内核或&releasename;的2.4内核上正常工作，然后升级到2.6内核。要把升级内核当成一项独立任务！</p> |
|
|
|
|
|
<p>如果您编译新内核，应确保在重启之前安装了<package/module-init-tools/。这一软件包在2.6内核下取代<package/modutils/。如果您安装<package/kernel-image/之一，这一软件包会由于依赖关系被自动安装。</p> |
|
|
|
|
|
<p>如果您用<em/LVM/，就应当在重启前安装<package/lvm2/，因为2.6内核不直接支持LVM1。<package/lvm2/(dm-mod模块)被用来访问LVM1卷。您可以安装<package/lvm10/－－一个在启动时检查哪种内核被使用，然后执行相应模块的脚本。</p> |
|
|
|
|
|
<p>注意一些模块名称有所改变，请检查修改<file>/etc/modules</file>(在启动时自动执行的模块列表)，把旧名改为新名。</p> |
|
|
|
|
|
<![ %i386 [ |
|
|
<p>对于一些SATA磁盘控制器，驱动器的关联文件可能从<file>/dev/hdX</file>变为<file>/dev/sdX</file>。如果出现这种情况，就得修改 <file>/etc/fstab</file>与启动程序的配置。只有在正确地修改之后，系统才能正常启动。</p> |
|
|
]]> |
|
|
|
|
|
<p>注意在安装完2.6内核重启之前，要确保有一种恢复措施。首先，确保启动程序可以新内核和旧内核（2.4内核）启动。还需要确保手头有紧急修复软盘或光盘，以防万一启动程序的错误配置导致无法从旧内核启动。</p> |
|
|
|
|
|
<![ %not-s390 [ |
|
|
<sect1 id="2.6-keyboard"> |
|
|
<heading>键盘配置</heading> |
|
|
|
|
|
<p>2.6内核最扰人的改变是输入层的低级变化。这一变化使所有的键盘都变得像“正常”的PC键盘。这意味着如果您目前有一个不同种类的键盘(例如一个USB-MAC或Sun键盘)，它极有可能在重启后无法工作。</p> |
|
|
|
|
|
<p>如果可以从其它系统通过SSH访问，您可以运行<tt>'dpkg-reconfigure console-data'</tt>来解决问题，只要选择"Select keymap from full list"然后选择"pc"键盘。</p> |
|
|
|
|
|
<p>如果终端键盘也被影响了，您也许还得为X Windows System重新配置键盘。可以执行<tt>dpkg-reconfigure xserver-xfree86</tt>或直接修改<file>/etc/X11/XF86Config-4</file>。 |
|
|
不要忘记阅读相关文档<ref id="nownownow">。</P> |
|
|
|
|
|
<![ %i386 [ |
|
|
<p>这个问题不会影响&arch-title;，因为所有PS/2和大部分USB键盘将被配置为“正常”PC键盘。</p> |
|
|
]]> |
|
|
<![ %not-i386 [ |
|
|
<p>注意如果您在使用USB键盘，它可能配置为“正常”PC键盘或USB-MAC键盘。在前一种情况下，您不会被这一问题所影响。</p> |
|
|
]]> |
|
|
</sect1> |
|
|
|
|
|
<sect1 id="2.6-mouse"> |
|
|
<heading>鼠标配置</heading> |
|
|
|
|
|
<p>还是由于输入层的变化，如果您的鼠标在2.6内核下不工作，您可能得重新配置X Window System和<package/gpm/。最可能的原因是接收鼠标数据的设备变了。您可能还需要载入一些模块。</p> |
|
|
|
|
|
<![ %sparc [ |
|
|
<p>如果您配置X使用<file>/dev/sunmouse</file>，可能需要改为<file>/dev/psaux</file>。</p> |
|
|
]]> |
|
|
|
|
|
</sect1> |
|
|
|
|
|
<sect1 id="2.6-sound"> |
|
|
<heading>声音配置</heading> |
|
|
|
|
|
<p>对于2.6内核，ALSA声音驱动程序比OSS声音驱动程序更受偏爱。如果安装了<package/alsa-base/声卡的ALSA模块会被自动载入；这也会自动把OSS驱动加入<package/discover/和<package/hotplug/的黑名单来阻止它们被读取。 如果在<file>/etc/modules</file>中有OSS驱动，应移除。</p> |
|
|
|
|
|
</sect1> |
|
|
]]> <!-- %not-s390 --> |
|
|
|
|
|
<sect1 id="2.6-udev"> |
|
|
<heading>升级到2.6内核可能会启用udev</heading> |
|
|
|
|
|
<p><package/udev/是devfs在用户层的实现。它挂载在<file>/dev</file>目录并把它与内核支持的硬件相关联。它与<package/hotplug/一起来检测新设备，动态地针对模块的装载和卸载进行目录配置。<package/udev/仅能在2.6内核下运行。 |
|
|
|
|
|
<p>由于<package/udev/会因为依赖关系，如<package/gnome/，而被自动安装。升级至2.6内核时可能会启用<package/udev/。</p> |
|
|
|
|
|
<p>虽然<package/udev/已经过了广泛的测试，但您还是可能在某些设备上遇到一些必须修正小问题。最常见的问题是某个设备的权限变更。某些状况下，有些设备是不会被默认建立的。（如：<file>/dev/video</file> 和<file>/dev/radio</file>）。 |
|
|
|
|
|
<p><package/udev/提供处理这些问题的配置方案。请查看 <manref name="udev" section="8">和<file>/etc/udev</file> 来取得详细信息。</p> |
|
|
|
|
|
</sect1> |
|
|
</sect> |
|
|
]]> <!-- %available-2.6 --> |
|
|
|
|
|
<![ %i386 [ |
|
|
|
|
|
<sect id="x-mouse"> |
|
|
<heading>无法载入X Windows System</heading> |
|
|
|
|
|
<p>如果重启后无法载入X Window System，并且您在 <file>/var/log/XFree86.0.log</file>中看到了"missing core pointer"这个错误，很可能是因为<prgn/hotplug/未能及时载入鼠标的驱动程序。(bug <url id="http://bugs.debian.org/255744" name="#255744">)。解决方案是将您的鼠标驱动模块（例如：psmouse）加到<file>/etc/modules</file>中。</p> |
|
|
|
|
|
</sect> |
|
|
|
|
|
<sect id="x-transmeta"> |
|
|
<heading>Transmeta Crusoe系统上的X Window System</heading> |
|
|
|
|
|
<p>&releasename;上的X server包含了一些经过优化的代码，但很多Transmeta(TM)的Crusoe(TM)处理器却无法正确执行它们。这将导致某段时间内（当暂存的x86的指令转换至Crusoe的VLIW指令中，处理器处于一个不稳定的状态），与它连结的X用户端应用程程序会出错并显示如下信息： |
|
|
|
|
|
<example> |
|
|
X Error of failed request: BadLength(poly request too large or internal Xlib length error). |
|
|
Major opcode of failed request: 18 (X_ChangeProperty) |
|
|
Serial number of failed request: 15 |
|
|
Current serial number in output stream: 18 |
|
|
</example></p> |
|
|
|
|
|
<p>实际运行中，这意味着程序运行几小时后，会接二连三出错；如果有显示管理程序运行，也会反复地重新启动。这种状态会持续到老出错误的VLIW Transmeta的代码被从缓冲器中移去。</p> |
|
|
|
|
|
<p>由于这个问题出在Transmeta Code Morphing Software(CMS)中，而且笔记型电脑的BIOS只有在开机时才会由供应商的判别码来检查CMS，所以需要Transmeta和笔记本电脑生产商合作才能解决这个问题。有关这个问题的更多信息可以由<url id="http://www.cs.auc.dk/~fleury/bug_cms/">及Debian bug报告<url id="http://bugs.debian.org/216933" name="#216933">取得。</p> |
|
|
|
|
|
<p>解决办法是安装编译时没有加进优化的X server，比如<package/xserver-xfree86-dbg/。</p> |
|
|
|
|
|
</sect> |
|
|
]]><!--i386--> |
|
|
|
|
|
</chapt> |
|
|
|
|
|
<chapt id="moreinfo"> |
|
|
|
|
|
<heading>有关&debian;的更多信息</heading> |
|
|
|
|
|
<sect id="morereading"> <heading>进一步阅读</heading> |
|
|
<p>除了本《发布说明》和《安装手册》，更深入的Debian GNU/Linux Documentation(Linux世界中的重要组成部分，以文档形式存在，一般包含书籍、HOWTO、FAQ和样例配置文件等非常有用的说明性资料，通常由开发者和用户撰写——译者)可在Debian Documentation Project(DDP)中找到，它的宗旨是为Debian用户和开发者创建高质量的Documentation。Documentation如《Debian Guide》《Debian新维护人员手册》和《Debian FAQ》等等都可阅读。访问<url id="&url-ddp;" name="DDP站点">来详细查看所有可用资源。</p> |
|
|
|
|
|
<p>为特殊软件包准备的Documentation被安装在 |
|
|
<file>/usr/share/doc/<var>package</var></file>，这可能包含copyright信息，Debian专门信息，和一些上游Documentation。</p> |
|
|
|
|
|
</sect> |
|
|
|
|
|
<sect id="gethelp"> |
|
|
<heading>获得帮助</heading> |
|
|
|
|
|
<p>Debian用户可获得各种形式帮助、建议和支持，但是这些只在您细致研究了所有与问题相关的Documentation的情况下才被考虑。这一部分提供对Debian用户有益的简短指导。</p> |
|
|
|
|
|
<sect1 id="lists"> |
|
|
<heading>邮件列表</heading> |
|
|
<p>Debian用户最喜欢的邮件列表是debian-user列表(英语)和其它debian-user-<var>language</var>列表(别的语言)。查看<url id="&url-debian-list-archives;">以获取这些列表的信息和加入邮件列表的方法。请在发邮件之前检查您问题已有的解答并且要遵循标准邮件列表格式。</p> |
|
|
</sect1> |
|
|
|
|
|
<sect1 id="irc"><heading>IRC</heading> |
|
|
|
|
|
<p>Debian在Freenode网络中特为Debian用户开通了一个IRC频道，它专门提供开源社区的共享资源。用您最喜欢的IRC客户端访问&debian-irc-server;然后加入#debian频道就可以了。</p> |
|
|
|
|
|
<p>请遵守频道指南，尊敬其它用户。访问<url id="&url-irc-host;" name="freenode.net">来获取更多信息。</p> |
|
|
|
|
|
</sect1> |
|
|
</sect> |
|
|
|
|
|
<sect id="bugs"> |
|
|
<heading>报告bug</heading> |
|
|
|
|
|
<p>我们努力把Debian打造成高性能操作系统，但是那不意味着我们提供的软件包完全没有bug。作为为用户提供的服务和Debian开放性开发的实践，我们在<url id="&url-bts;" name="bugs.debian.org">的Bug跟踪系统(BTS)中提供所有已报告bug的信息。</p> |
|
|
<!-- FJP: I propose to replace the last sentence by: |
|
|
Consistent with Debian's 'open development' philosophy and as a |
|
|
service to our users, we provide all the information on reported bugs |
|
|
at our own Bug Tracking System (BTS). The BTS is browseable at |
|
|
<url id="&url-bts;" name="bugs.debian.org">. |
|
|
--> |
|
|
|
|
|
<p>如果您在发行版或它里面的打包软件中发现了一个bug，请报告这个bug以便它可以在下一发行版中得到修复。报告bug需要一个合法的Email地址，以使我们可以追踪bug，也使开发人员在需要更多信息的情况下与报告者取得联系。</p> |
|
|
|
|
|
<p>您可以使用<package>reportbug</package>或手动地使用Email提交一个bug报告。您可以在装有<package>doc-debian</package>的Debian系统中的<file>/usr/share/doc/debian</file>或在网上<url id="&url-bts;" name="Bug跟踪系统">阅读说明来获取更多BTS的信息以及学习如何使用它。</p> |
|
|
<!-- FJP: The 'bug' program and package are obsolete. --> |
|
|
<!-- JFS: The reference cards are only available if you have doc-debian installed, which might not always be the case --> |
|
|
|
|
|
</sect> |
|
|
|
|
|
<sect id="contributing"> |
|
|
<heading>为Debian做贡献</heading> |
|
|
|
|
|
<p>来为Debian做贡献，您不必是一名专家。在<url id="&url-debian-list-archives;" name="用户邮件列表">中帮助用户解决问题就是在为Debian社区做贡献。在<url id="&url-debian-list-archives;" name="开发邮件列表">中检查(并且解决)与发行版开发相关的问题对Debian也极其有帮助。可以<url id="&url-bts;" name="报告bug">并且帮助开发人员追踪和修复bug来保持Debian的高性能。如果您语言能力强，您可能会愿意通过写<url id="&url-ddp;" name="documentation">或用您自己的语言<url id="&url-debian-i18n;" name="翻译">已有的Documentation来做更活跃的贡献。</p> |
|
|
|
|
|
<p>如果您有更多时间，您可以在Debian中维护自由软件，<url id="&url-wnpp;" name="Work Needing |
|
|
and Prospective Packages数据库"> 会详细介绍这一信息。如果您在某一特殊领域感兴趣，那么您可能在Debian的一些子项目如系统平台移植、<url id="&url-debian-jr;" name="Debian |
|
|
Jr.">和<url id="&url-debian-med;" name="Debian Med">中获得乐趣。</p> |
|
|
|
|
|
<p>在任何情况下，如果您在以任何形式在自由软件社区内工作，不论是以用户、程序员还是写作者、翻译者身份，您已经在帮助自由软件。贡献是光荣而又有趣的，而且让您结识新朋友，这会给您一种来自内心深处的温暖!</p> |
|
|
</sect> |
|
|
|
|
|
</chapt> |
|
|
|
|
|
|
|
|
<![ %upgradekernel [ |
|
|
|
|
|
<appendix id="kernel-upgrade-howto"><heading>升级内核</heading> |
|
|
|
|
|
<![ %not-mips-mipsel [ |
|
|
<![ %sparc [ |
|
|
|
|
|
<p><strong>这个附录是特别给那些为了确保系统升级能够顺利进行，不得不在系统升级<em/之前/先升级内核的人们写的。请参考<ref id="new-kernel">来检查您的系统是否需要这样</strong>。</p> |
|
|
]]> |
|
|
<p>以下将逐步说明如何使用backports工具来安装新内核。</p> |
|
|
|
|
|
<p>由于软件包可能需要&oldreleasename;的，您应先检查<file>sources.list</file>仍指向&oldreleasename;，正如<ref id="old-sources">中解释的那样。</p> |
|
|
]]> <!-- %not-mips-mipsel --> |
|
|
|
|
|
<![ %mips-mipsel [ |
|
|
<p>以下将逐步说明如何安装新内核。</p> |
|
|
]]> |
|
|
|
|
|
<p><taglist> |
|
|
<tag>下载并安装必须的软件包</tag> |
|
|
|
|
|
<![ %mips-mipsel [ |
|
|
<item> |
|
|
<p><em>使用apt</em>;如果还没有的话，修改<file>sources.list</file>使之指向&releasename;，正如<ref id="upgrade-process">中解释的那样。更新软件包列表然后为您的机器安装内核包。您可以通过 |
|
|
|
|
|
<example> |
|
|
$ apt-cache search ^kernel-image |
|
|
</example>获得可用内核列表。</p> |
|
|
|
|
|
<p>在安装时apt可能警告模块不匹配并询问是否继续安装。请在回答<tt>yes</tt>因为这些不匹配会在您使用新内核重启后得到解决。</p> |
|
|
|
|
|
<p><em>使用dpkg</em>:从Debian镜像站取得最新的内核软件包。可用的有： |
|
|
|
|
|
<list> |
|
|
<![ %mips [ |
|
|
<item><p><url id="&mips-kernel-patch;/&mips-kernel-image-r4k;" name="&mips-kernel-image-r4k;">用于R4XX0处理器及SGI IP22子系统如Indy和Indigo2。</p></item> |
|
|
<item><p><url id="&mips-kernel-patch;/&mips-kernel-image-r5k;" name="&mips-kernel-image-r5k;">用于R5000处理器及SGI IP22子系统如Indy和Indigo2。</p></item> |
|
|
<item><p><url id="&mips-kernel-patch;/&mips-kernel-image-swarm;" name="&mips-kernel-image-swarm;">用于Broadcom BCM91250A(即SWARM)pass 2.2。</p></item> |
|
|
]]> |
|
|
<![ %mipsel [ |
|
|
<item><p><url id="&mips-kernel-patch;/&mipsel-kernel-image-r3k;" name="&mipsel-kernel-image-r3k;">用于配有KN02（或兼容）主机版、基于R3000的DEC工作站，如DECstation 5000/1xx(xx=20,25,33)及DECstation 5000/240。</p></item> |
|
|
<item><p><url id="&mips-kernel-patch;/&mipsel-kernel-image-r4k;" name="&mipsel-kernel-image-r4k;">用于配有KN04（或兼容）主机版、基于R4X00的DEC 工作站，如DECstation 5000/150、Personal DECstation 5000/50及DECstation 5000/260。</p></item> |
|
|
<item><p><url id="&mips-kernel-patch;/&mipsel-kernel-image-r5k-cobalt;" name="&mipsel-kernel-image-r5k-cobalt;">用于基于MIPS的Cobalt机器（如Qube、RaQ、Qube2 或 RaQ2）。</p></item> |
|
|
<item><p><url id="&mips-kernel-patch;/&mipsel-kernel-image-r5k-lasat;" name="&mipsel-kernel-image-r5k-lasat;">用于在Lasat Masquerade Pro上的R5000处理器。</p></item> |
|
|
<item><p><url id="&mips-kernel-patch;/&mipsel-kernel-image-swarm;" name="&mipsel-kernel-image-swarm;">用于Broadcom BCM91250A(即SWARM)pass 2.2。</p></item> |
|
|
<item><p><url id="&mips-kernel-patch;/&mipsel-kernel-image-xxs1500;" name="&mipsel-kernel-image-xxs1500;">用于基于Au1500的XXS1500主板。</p></item> |
|
|
]]> |
|
|
</list></p> |
|
|
|
|
|
<p>然后，使用<tt>dpkg -i</tt>来安装这些软件包。在安装时它可能警告模块不匹配（来自 <package>modutils</package>）并询问是否继续安装。请在回答<tt>yes</tt>因为这些不匹配会在您使用新内核重启后得到解决。</p> |
|
|
|
|
|
</item> |
|
|
]]> <!-- %mips-mipsel --> |
|
|
|
|
|
<![ %not-mips-mipsel [ |
|
|
<item> |
|
|
<p><em>使用apt</em>：若要使用<prgn>apt</prgn>或是一种前端来安装软件包，请将下行加入<file>/etc/apt/sources.list</file>中： |
|
|
|
|
|
<example> |
|
|
deb &url-kernel-upgrade; |
|
|
# sources are also available if you need them |
|
|
# deb-src &url-kernel-upgrade; |
|
|
</example></p> |
|
|
|
|
|
<![ %sparc [ |
|
|
<p>下一步，安装<package>modutils</package>及<package>initrd-tools</package>软件包。 |
|
|
]]> |
|
|
<![ %hppa [ |
|
|
<p>下一步，安装<package>module-init-tools</package>、<package>modutils</package>、<package>polo</package>及<package>initrd-tools</package>软件包。 |
|
|
<example> |
|
|
# apt-get install module-init-tools palo initrd-tools modutils |
|
|
</example> |
|
|
]]> |
|
|
|
|
|
（之后您就可以安全在恢复主要升级过程了。） |
|
|
|
|
|
<p>之后修改<file>sources.list</file>使之指向&releasename;，正如<ref id="upgrade-process">中解释的那样。更新软件包列表然后安装<package>&upgrade-kernel-image-name;</package>包。</p> |
|
|
|
|
|
<p><em>使用dpkg</em>：若要直接使用<prgn>dpkg</prgn>来安装软件包，您必须先去下载必要的文件。 |
|
|
<p><list> |
|
|
<item><url id="&upgrade-kernel-image;"></item> |
|
|
<item><url id="&upgrade-kernel-modutils;"></item> |
|
|
<![ %hppa [ <item><url id="&hppa-modutils;"></item> ]]> |
|
|
<item><url id="&all-initrd-tools;"></item> |
|
|
<item><url id="&upgrade-kernel-cramfsprogs;"></item> |
|
|
</list></p> |
|
|
|
|
|
<p>内核软件包依赖<package>&upgrade-kernel-modutils-name;</package><![ %hppa [ |
|
|
(与原有的 <package>modutils</package>冲突)]]>；<package>initrd-tools</package>依赖<package>cramfsprogs</package>。 |
|
|
&oldreleasename;中的软件包会满足其它任何依赖关系（<package>stat</package>、 <package>cpio</package>和<package>ash</package>）。</p> |
|
|
<![ %hppa [ |
|
|
<p>如果您用<em/LVM/，就应当在重启前安装<package/lvm2/，因为2.6内核不直接支持LVM1。<package/lvm2/(dm-mod模块)被用来访问LVM1卷。您可以安装<package/lvm10/ installed;，一个在启动时检查哪种内核被使用，然后执行相应模块的脚本。</p> |
|
|
]]> |
|
|
</item> |
|
|
]]> <!-- %not-mips-mipsel --> |
|
|
|
|
|
<tag>请别急于删除旧内核</tag> |
|
|
<item><p>您应该先去确认新内核能够正常开机，且所有在升级过程中必须用到的硬件（如网路装置）能够正常工作。</p></item> |
|
|
|
|
|
<![ %not-mips-mipsel [ |
|
|
<tag>让您的系统能够开机</tag> |
|
|
<item> |
|
|
<p>您应修改您的开机设置文件<file>&bootloader-conf;</file>。请注意，新内核会用使用initrd，而这在&oldreleasename;中的Debian内核不需要。</p> |
|
|
</item> |
|
|
]]> |
|
|
|
|
|
<tag>使用新内核重启</tag> |
|
|
<tag>检查您的系统</tag> |
|
|
<item><p>请小心确认，尤其是输入装置、显示设置、还有会用来存取 &releasename;软件包的设备（如网路装置、光驱等等）。有些驱动模块的名称可能已经有所改变，有些设备在以前是被编译进内核的，而现在则是被编译成模块... ...</p></item> |
|
|
|
|
|
</taglist></p> |
|
|
|
|
|
</appendix> |
|
|
]]><!--upgrade-kernel--> |
|
|
|
|
|
<appendix id="old-stuff"> |
|
|
<heading>管理&oldreleasename;系统</heading> |
|
|
|
|
|
<p>本附录包含在升级到&releasename;之前如何安装或升级&oldreleasename;软件包。这仅在某些特殊情况下有用。</p> |
|
|
|
|
|
<sect id="old-upgrade"> |
|
|
<heading>升级&oldreleasename;系统</heading> |
|
|
|
|
|
<p>基本上这与从前进行的&oldreleasename;升级没什么区别。仅有的区别在于首先您应确保软件包列表仍指向&oldreleasename;，正如<ref id="old-sources">中解释的。</p> |
|
|
|
|
|
</sect> |
|
|
|
|
|
<![ %has-woody-aptitude [ |
|
|
<sect id="old-aptitude"> |
|
|
<heading>安装&oldreleasename;的aptitude</heading> |
|
|
|
|
|
<p>首先必须确保安装&oldreleasename;的<package/aptitude/而不是&releasename;的，按照<ref id="old-sources">做。</p> |
|
|
|
|
|
<p>然后，执行 |
|
|
|
|
|
<example> |
|
|
# apt-get install aptitude |
|
| 963 |
</example> |
</example> |
| 964 |
|
</p> |
| 965 |
来安装<package/aptitude/。</p> |
<p> |
| 966 |
|
您可以强行删除出错信息<em>最后</em>一行的软件包： |
| 967 |
</sect> |
<example> |
| 968 |
]]><!--has-woody-aptitude--> |
# dpkg -r --force-depends <var>package_name</var> |
| 969 |
|
</example> |
| 970 |
<sect id="old-sources"> |
</p> |
| 971 |
<heading>检查源列表</heading> |
<p> |
| 972 |
|
修好之后，您应可以通过上面提到的<tt>aptitude</tt>命令方法恢复升级过程。 |
| 973 |
<p>如果<file>/etc/apt/sources.list</file>中的任何行指向'stable'，您正在“使用”&releasename;。如果您已经执行<tt>apt-get update</tt>，也可以遵循以下操作很轻松地回到&oldreleasename。</p> |
</p> |
| 974 |
|
<p> |
| 975 |
<p>如果您已经从&releasename;安装了软件包，安装&oldreleasename;的软件包就不太容易了。万一这样，您就要自己决定是否继续。可以进行软件包降级，但这非本说明所及。</p> |
在升级过程中，您会被问一些问题来配置或重新配置部分软件包。如果您被问到任何在<file>/etc/init.d</file>或<file>/etc/terminfo</file>目录中的文件，或<file>/etc/manpath.config</file>文件是否应被包维护者的文件替代时，通常回答'yes'很必要。您可以在任意时候转回旧的文件，因为它们会被标以 |
| 976 |
|
<tt>.dpkg-old</tt>扩展名储存。 |
| 977 |
<p>以root身份，打开<file>/etc/apt/sources.list</file>检查所有以<tt>deb http:</tt>或<tt>deb ftp:</tt>开头的行是否指向"<tt/stable/"。如果有，把<tt/stable/改为<tt/&oldreleasename;/。</p> |
</p> |
| 978 |
|
<p> |
| 979 |
<p>如果有以<tt>deb file:</tt>开头的行，那您将得自己检查它指向的地址是包含&oldreleasename;还是&releasename;软件。</p> |
如果您不知道应该做什么，记下软件包或者文件的名字，再在升级后解决这些问题。您可以搜索日志文件来复查升级过程中显示的屏幕信息。 |
| 980 |
|
</p> |
| 981 |
<p><strong/重要提示！/不要修改以<tt>deb cdrom:</tt>开头的行。否则会出错，以致不得不重新运行apt-cdrom 。不要因为'cdrom'行指向"<tt/unstable/"而感到惊讶。虽然令人困惑，但这是正常的。</p> |
</sect1> |
| 982 |
|
</sect> |
| 983 |
<p>如果您做了修改，保存文件然后执行 |
<sect id="newkernel"> |
| 984 |
|
<heading> |
| 985 |
<example> |
Upgrading your kernel and related packages |
| 986 |
|
</heading> |
| 987 |
|
<p> |
| 988 |
|
You should upgrade the Linux kernel separately from the rest of your |
| 989 |
|
packages. You may wish to do so yourself, either by installing one of |
| 990 |
|
the <package>linux-image-*</package> packages or by compiling a |
| 991 |
|
customized kernel from sources. Please read the information in this |
| 992 |
|
section about potential issues with kernel upgrades. |
| 993 |
|
</p> |
| 994 |
|
<p> |
| 995 |
|
All Linux kernel packages have been renamed from <tt>kernel-*</tt> to |
| 996 |
|
<tt>linux-*</tt> to clean up the namespace. |
| 997 |
|
</p> |
| 998 |
|
<![ %defaulted-2.4 [ |
| 999 |
|
|
| 1000 |
|
<p> |
| 1001 |
|
If you are currently using a kernel from the 2.4 series, the older |
| 1002 |
|
stable Linux kernel series, you should upgrade to a 2.6 series kernel, |
| 1003 |
|
as 2.4 is no longer supported in &releasename;. If you are currently |
| 1004 |
|
using a kernel from the 2.2 series, you must upgrade to (at least) the |
| 1005 |
|
2.4 series, better to a 2.6 series kernel prior to upgrading your |
| 1006 |
|
packages. Some general issues associated with an upgrade to 2.6 are |
| 1007 |
|
documented in <ref id="upgrade-to-2.6">. |
| 1008 |
|
</p> |
| 1009 |
|
]]> |
| 1010 |
|
|
| 1011 |
|
<sect1> |
| 1012 |
|
<heading> |
| 1013 |
|
initrd-tools deprecated |
| 1014 |
|
</heading> |
| 1015 |
|
<p> |
| 1016 |
|
<package>initrd-tools</package> is no longer supported and has been |
| 1017 |
|
superseded by <package>initramfs-tools</package> and |
| 1018 |
|
<package>yaird</package>. Upgrading to an &releasename; kernel will |
| 1019 |
|
cause <package>initramfs-tools</package> to be installed by |
| 1020 |
|
default. <![ %defaulted-2.4 [ If you are upgrading from a 2.4 kernel |
| 1021 |
|
to a 2.6 kernel for the first time, you must use |
| 1022 |
|
<package>initramfs-tools</package>. Using <package>yaird</package> |
| 1023 |
|
will cause linux-image-2.6 installations to fail if you are running a |
| 1024 |
|
2.2 or 2.4 kernel. ]]> |
| 1025 |
|
</p> |
| 1026 |
|
</sect1> |
| 1027 |
|
<sect1> |
| 1028 |
|
<heading> |
| 1029 |
|
devfs deprecated |
| 1030 |
|
</heading> |
| 1031 |
|
<p> |
| 1032 |
|
&releasename; no longer provides support for <prgn>devfs</prgn>. It is |
| 1033 |
|
recommended that users switch to udev for dynamic <file>/dev</file> |
| 1034 |
|
management. Debian kernels no longer include support for |
| 1035 |
|
<prgn>devfs</prgn>, so <prgn>devfs</prgn> users will need to manually |
| 1036 |
|
convert their systems before upgrading to an &releasename; kernel. |
| 1037 |
|
</p> |
| 1038 |
|
<p> |
| 1039 |
|
If you see the string 'devfs' in <file>/proc/mounts</file>, you are |
| 1040 |
|
likely using devfs. Any config files that reference devfs style names |
| 1041 |
|
will need to be adjusted to use udev style names. Files that are most |
| 1042 |
|
likely to refer to devfs style device names include |
| 1043 |
|
<file>/etc/fstab</file>, <file>/etc/lilo.conf</file>, |
| 1044 |
|
<file>/boot/grub/menu.lst</file>, etc. |
| 1045 |
|
</p> |
| 1046 |
|
<p> |
| 1047 |
|
More information about potential issues is available in bug report |
| 1048 |
|
<url id="http://bugs.debian.org/341152" name="#341152">. |
| 1049 |
|
</p> |
| 1050 |
|
</sect1> |
| 1051 |
|
<![ %i386-amd64-ia64 [ |
| 1052 |
|
|
| 1053 |
|
<sect1> |
| 1054 |
|
<heading> |
| 1055 |
|
Standard kernels contain SMP abilities |
| 1056 |
|
</heading> |
| 1057 |
|
<p> |
| 1058 |
|
Multiprocessor systems no longer require a *-smp flavour of the Linux |
| 1059 |
|
kernel. For &arch-title; linux-image packages without the -smp suffix |
| 1060 |
|
support both uniprocessor and multiprocessor systems. |
| 1061 |
|
</p> |
| 1062 |
|
</sect1> |
| 1063 |
|
]]><![ %i386 [ |
| 1064 |
|
|
| 1065 |
|
<sect1> |
| 1066 |
|
<heading> |
| 1067 |
|
386 kernel flavour deprecated |
| 1068 |
|
</heading> |
| 1069 |
|
<p> |
| 1070 |
|
Support for the 80386 sub-archicture for &arch-title; has been dropped |
| 1071 |
|
in &releasename;. The 386 kernel flavor is no longer supported and has |
| 1072 |
|
been replaced by the new 486 flavour. |
| 1073 |
|
</p> |
| 1074 |
|
</sect1> |
| 1075 |
|
]]> |
| 1076 |
|
|
| 1077 |
|
<sect1> |
| 1078 |
|
<heading> |
| 1079 |
|
Device enumeration reordering |
| 1080 |
|
</heading> |
| 1081 |
|
<p> |
| 1082 |
|
&releasename; features a more robust mechanism for hardware discovery |
| 1083 |
|
than previous releases. However, this may cause changes in the order |
| 1084 |
|
devices are discovered on your system affecting the order in which |
| 1085 |
|
device names are assigned. For example, if you have two network |
| 1086 |
|
adapters that are associated with two different drivers, the devices |
| 1087 |
|
eth0 and eth1 refer to may be swapped. Please note that the new |
| 1088 |
|
mechanism means that if you e.g. exchange ethernet adapters in a |
| 1089 |
|
running &releasename; system, the new adapter will also get a new |
| 1090 |
|
interface name. |
| 1091 |
|
</p> |
| 1092 |
|
<p> |
| 1093 |
|
For network devices, you can avoid this reordering by using the |
| 1094 |
|
<prgn>ifrename</prgn> utility to bind physical devices to specific |
| 1095 |
|
names at boot time. See <manref section="8" name="ifrename"> and |
| 1096 |
|
<manref section="5" name="iftab"> for more information. |
| 1097 |
|
</p> |
| 1098 |
|
<p> |
| 1099 |
|
For storage devices, you can avoid this reordering by using |
| 1100 |
|
<package>initramfs-tools</package> and configuring it to load storage |
| 1101 |
|
device driver modules in the same order they are currently loaded. To |
| 1102 |
|
do this, identify the order the storage modules on your system were |
| 1103 |
|
loaded by looking at the output of |
| 1104 |
|
<prgn>lsmod</prgn>. <prgn>lsmod</prgn> lists modules in the reverse |
| 1105 |
|
order that they were loaded in, i.e., the first module in the list was |
| 1106 |
|
the last one loaded. |
| 1107 |
|
</p> |
| 1108 |
|
<p> |
| 1109 |
|
However, removing and reloading modules after initial boot will affect |
| 1110 |
|
this order. Also, your kernel may have some drivers linked statically, |
| 1111 |
|
and these names will not appear in the output of |
| 1112 |
|
<prgn>lsmod</prgn>. You may be able to decipher these driver names and |
| 1113 |
|
load order from looking at <file>/var/log/kern.log</file>, or the |
| 1114 |
|
output of <prgn>dmesg</prgn>. |
| 1115 |
|
</p> |
| 1116 |
|
<p> |
| 1117 |
|
Add these module names to <file>/etc/initramfs-tools/modules</file> in |
| 1118 |
|
the order they should be loaded at boottime. Some module names may |
| 1119 |
|
have changed between &oldreleasename; and &releasename;. For example, |
| 1120 |
|
sym53c8xx_2 has become sym53c8xx. |
| 1121 |
|
</p> |
| 1122 |
|
<p> |
| 1123 |
|
You will then need to regenerate your initramfs image(s) by executing |
| 1124 |
|
<tt>update-initramfs -k all</tt>. |
| 1125 |
|
</p> |
| 1126 |
|
<p> |
| 1127 |
|
Once you are running an &releasename; kernel and <prgn>udev</prgn>, |
| 1128 |
|
you may reconfigure your system to access disks by an alias that is |
| 1129 |
|
not dependent upon driver load order. These aliases reside in the |
| 1130 |
|
<file>/dev/disk/</file> hierarchy. |
| 1131 |
|
</p> |
| 1132 |
|
</sect1> |
| 1133 |
|
<![ %ia64 [ |
| 1134 |
|
|
| 1135 |
|
<sect1> |
| 1136 |
|
<heading> |
| 1137 |
|
Serial device reordering |
| 1138 |
|
</heading> |
| 1139 |
|
<p> |
| 1140 |
|
If you have an HP machine and you're using the MP serial console port |
| 1141 |
|
(the connector labelled "console" on the 3-headed cable), this kernel |
| 1142 |
|
upgrade will break your console! |
| 1143 |
|
</p> |
| 1144 |
|
<p> |
| 1145 |
|
Please read the following information before upgrading. |
| 1146 |
|
</p> |
| 1147 |
|
<p> |
| 1148 |
|
<list> |
| 1149 |
|
<item> |
| 1150 |
|
<p> |
| 1151 |
|
The console device will change from <file>ttyS0</file> to |
| 1152 |
|
<file>ttyS1</file>, <file>ttyS2</file>, or <file>ttyS3</file> so |
| 1153 |
|
<list> |
| 1154 |
|
<item> |
| 1155 |
|
<p> |
| 1156 |
|
Edit <file>/etc/inittab</file> to add a getty entry for |
| 1157 |
|
<file>/dev/ttyS1</file> (rx4640, rx5670, rx7620, rx8620, |
| 1158 |
|
Superdome), <file>/dev/ttyS2</file> (rx1600), or |
| 1159 |
|
<file>/dev/ttyS3</file> (rx2600). |
| 1160 |
|
</p> |
| 1161 |
|
</item> |
| 1162 |
|
<item> |
| 1163 |
|
<p> |
| 1164 |
|
Edit <file>/etc/securetty</file> to add <file>ttyS1</file>, |
| 1165 |
|
<file>ttyS2</file>, or <file>ttyS3</file>. |
| 1166 |
|
</p> |
| 1167 |
|
</item> |
| 1168 |
|
<item> |
| 1169 |
|
<p> |
| 1170 |
|
Leave the existing <file>ttyS0</file> entries in |
| 1171 |
|
<file>/etc/inittab</file> and <file>/etc/securetty</file> so you |
| 1172 |
|
can still boot old kernels. |
| 1173 |
|
</p> |
| 1174 |
|
</item> |
| 1175 |
|
</list> |
| 1176 |
|
</p> |
| 1177 |
|
</item> |
| 1178 |
|
<item> |
| 1179 |
|
<p> |
| 1180 |
|
Edit <file>/etc/elilo.conf</file> to remove any "console=" |
| 1181 |
|
arguments. |
| 1182 |
|
</p> |
| 1183 |
|
</item> |
| 1184 |
|
<item> |
| 1185 |
|
<p> |
| 1186 |
|
Run <prgn>elilo</prgn> to install the bootloader with new |
| 1187 |
|
configuration. |
| 1188 |
|
</p> |
| 1189 |
|
</item> |
| 1190 |
|
<item> |
| 1191 |
|
<p> |
| 1192 |
|
Reboot and use the EFI boot option maintenance menu to select |
| 1193 |
|
exactly one device for console output, input, and standard |
| 1194 |
|
error. Then do a cold reset so the changes take effect. |
| 1195 |
|
</p> |
| 1196 |
|
<p> |
| 1197 |
|
For the MP console, be careful to select the device with |
| 1198 |
|
"Acpi(HWP0002,700)/Pci(...)/Uart" in the path. |
| 1199 |
|
</p> |
| 1200 |
|
</item> |
| 1201 |
|
</list> |
| 1202 |
|
</p> |
| 1203 |
|
<p> |
| 1204 |
|
More details about these changes and troubleshooting hints are |
| 1205 |
|
available at <url |
| 1206 |
|
id="http://lists.debian.org/debian-ia64/2005/01/msg00008.html">. |
| 1207 |
|
</p> |
| 1208 |
|
</sect1> |
| 1209 |
|
]]> |
| 1210 |
|
|
| 1211 |
|
<sect1> |
| 1212 |
|
<heading> |
| 1213 |
|
Upgrading the kernel |
| 1214 |
|
</heading> |
| 1215 |
|
<p> |
| 1216 |
|
When you dist-upgrade from &oldreleasename; to &releasename;, it is |
| 1217 |
|
strongly recommended that you install a new linux-image-2.6-* |
| 1218 |
|
metapackage. This package may be installed automatically by the |
| 1219 |
|
dist-upgrade process. You can verify this by running: |
| 1220 |
|
<example> |
| 1221 |
|
# dpkg -l | grep '^ii linux-image' |
| 1222 |
|
</example> |
| 1223 |
|
</p> |
| 1224 |
|
<p> |
| 1225 |
|
If you do not see any output, then you will need to install a new |
| 1226 |
|
linux-image package by hand. To see a list of available |
| 1227 |
|
linux-image-2.6 metapackages, run: |
| 1228 |
|
<example> |
| 1229 |
|
# apt-cache search linux-image-2.6- | grep -v transition |
| 1230 |
|
</example> |
| 1231 |
|
</p> |
| 1232 |
|
<p> |
| 1233 |
|
If you are unsure about which package to select, run <tt>uname -r</tt> |
| 1234 |
|
and look for a package with a similar name. For example, if you see |
| 1235 |
|
'2.4.27-3-686', it is recommended that you install |
| 1236 |
|
<package>linux-image-2.6-686</package>. You may also use apt-cache to |
| 1237 |
|
see a long description of each package in order to help choose the |
| 1238 |
|
best one available. For example: |
| 1239 |
|
<example> |
| 1240 |
|
# apt-cache show linux-image-2.6-686 |
| 1241 |
|
</example> |
| 1242 |
|
</p> |
| 1243 |
|
<p> |
| 1244 |
|
然后您应该使用<tt>aptitude |
| 1245 |
|
install</tt>来安装它。一旦新内核被安装，您应该重启来使用它，享受它的新功能。 |
| 1246 |
|
</p> |
| 1247 |
|
<p> |
| 1248 |
|
如果要更刺激，有一种简单的方法来编译您自己定制的内核。安装<package>kernel-package</package>工具然后阅读<file>/usr/share/doc/kernel-package</file>中的文档。 |
| 1249 |
|
</p> |
| 1250 |
|
</sect1> |
| 1251 |
|
</sect> |
| 1252 |
|
<sect id="nownownow"> |
| 1253 |
|
<heading> |
| 1254 |
|
重启前的任务 |
| 1255 |
|
</heading> |
| 1256 |
|
<p> |
| 1257 |
|
当<tt>aptitude |
| 1258 |
|
dist-upgrade</tt>完成时，“前期”升级就已经结束了，但是在重启之前还有许多其它事情要做。 |
| 1259 |
|
</p> |
| 1260 |
|
<sect1 id="mdadm"> |
| 1261 |
|
<heading> |
| 1262 |
|
Upgrading mdadm |
| 1263 |
|
</heading> |
| 1264 |
|
<p> |
| 1265 |
|
mdadm now needs a configuration file to assemble MD arrays (RAID) from |
| 1266 |
|
the initial ramdisk and during the system initialisation |
| 1267 |
|
sequence. Please make sure to read and act upon the instructions in |
| 1268 |
|
<file>/usr/share/doc/mdadm/README.upgrading-2.5.3.gz</file> after the |
| 1269 |
|
package has been upgraded <strong>and before you reboot</strong>. The |
| 1270 |
|
latest version of this file is available at <url |
| 1271 |
|
id="http://svn.debian.org/wsvn/pkg-mdadm/mdadm/trunk/debian/README.upgrading-2.5.3 op=file">; |
| 1272 |
|
please consult it in case of problems. |
| 1273 |
|
</p> |
| 1274 |
|
</sect1> |
| 1275 |
|
</sect> |
| 1276 |
|
<sect id="obsolete"> |
| 1277 |
|
<heading> |
| 1278 |
|
废弃的软件包 |
| 1279 |
|
</heading> |
| 1280 |
|
<p> |
| 1281 |
|
&releasename;不但新引入了几千个新软件包，也废弃了200多个在&oldreleasename;中的旧软件包。它不为这些废弃软件包提供升级补丁。不过这不影响您在必要时继续使用废弃的软件包，Debian项目通常在&releasename;发布一年后停止对它们的安全支持<footnote><p>或者在&releasename;后新发行版发布时停止， |
| 1282 |
|
一般只能有两个stable发行版同时被支持。</p></footnote>，而且这期间不会提供其它支持。如果可以的话，就应把它们换为的替代软件。 |
| 1283 |
|
</p> |
| 1284 |
|
<p> |
| 1285 |
|
软件包被移去有很多原因：不再被上游开发者维护或没有Debian开发者（即DD——译者）愿意维护；功能被其它软件或新版本更好地取代；错误太严重。在最后一个原因中，软件包很可能还属于unstable。 |
| 1286 |
|
</p> |
| 1287 |
|
<p> |
| 1288 |
|
包管理软件会标注出来哪些软件包被废弃，查看这方面信息十分容易。如果用<prgn>aptitude</prgn>，您会在"Obsolete |
| 1289 |
|
and Locally Created |
| 1290 |
|
Packages"部分见到这些软件包的列表。<prgn>dselect</prgn>提供一个类似的列表，不过可能有些差异。另外，如果您使用<prgn>aptitude</prgn>手动安装了&oldreleasename;中的软件包，它会记录您手动安装的包并且在包被删除时把由于依赖关系而被安装的包标记为废弃。而且，不像<prgn>deborphan</prgn>，<prgn>aptitude</prgn>不会把您手动安装的包标记为废弃，这不同于由于依赖关系而被自动安装的包。 |
| 1291 |
|
</p> |
| 1292 |
|
<p> |
| 1293 |
|
有许多寻找废弃软件包的附加工具，比如<prgn>deborphan</prgn>、 |
| 1294 |
|
<prgn>debfoster</prgn>和<prgn>cruft</prgn>。 |
| 1295 |
|
推荐使用<prgn>deborphan</prgn>，虽然它只报告"libs"和"oldlibs"中的废弃链接库。不要随意删除这些工具显示的软件包，特别是当您使用冒犯性的非默认设置时，它们很容易造成假象。推荐在删除之前仔细查看包的信息（内容，大小和描述）。 |
| 1296 |
|
</p> |
| 1297 |
|
<p> |
| 1298 |
|
<url id="&url-bts;" name="Debian Bug Tracking |
| 1299 |
|
System">经常有之所以软件包被除的更多信息。您可以查看软件包存档的bug报告和<url |
| 1300 |
|
id="&url-bts;cgi-bin/pkgreport.cgi pkg=ftp.debian.org&archive=yes" |
| 1301 |
|
name="ftp.debian.org pseudo-package">存档的bug报告。 |
| 1302 |
|
</p> |
| 1303 |
|
<sect1 id="dummy"> |
| 1304 |
|
<heading> |
| 1305 |
|
Dummy包 |
| 1306 |
|
</heading> |
| 1307 |
|
<p> |
| 1308 |
|
一些&oldreleasename;中的软件包在&releasename;中被分成几部分，以提高系统的易维护性。为了简化升级，&releasename;经常提供通过依赖关系安装其它新包的"dummy"包——与&oldreleasename;包有相同名称的空包。"dummy"包在升级后就没用了，可以安全地删除。 |
| 1309 |
|
</p> |
| 1310 |
|
<p> |
| 1311 |
|
大多数（不是所有）的dummy包的描述部分说明它们的目的。但是，包描述信息不是唯一的，所以您可能会发现<prgn>deborphan</prgn>加上<tt>--guess</tt>选项对寻找这些包有用。注意有些dummy包在升级后不会被删除，它们被用来记录一个程序的可用版本。 |
| 1312 |
|
</p> |
| 1313 |
|
</sect1> |
| 1314 |
|
</sect> |
| 1315 |
|
</chapt> |
| 1316 |
|
<chapt id="information"> |
| 1317 |
|
<heading> |
| 1318 |
|
在&releasename;中应注意的问题 |
| 1319 |
|
</heading> |
| 1320 |
|
<sect id="problems"> |
| 1321 |
|
<heading> |
| 1322 |
|
Potential problems |
| 1323 |
|
</heading> |
| 1324 |
|
<p> |
| 1325 |
|
Sometimes, changes have side-issues we cannot reasonably avoid, or we |
| 1326 |
|
expose bugs somewhere else. We document here the issues we are aware |
| 1327 |
|
of. Please also read the errata, the relevant packages' documentation, |
| 1328 |
|
bug reports and other information mentioned in <ref id="morereading">. |
| 1329 |
|
</p> |
| 1330 |
|
<sect1 id="window-scaling"> |
| 1331 |
|
<heading> |
| 1332 |
|
Certain networking site cannot be reached by TCP |
| 1333 |
|
</heading> |
| 1334 |
|
<p> |
| 1335 |
|
Since 2.6.17, Linux uses TCP window scaling which is specified in RFC |
| 1336 |
|
1323 in an aggressive way. Some servers have a broken behaviour, and |
| 1337 |
|
announce wrong window sizes for themselves. Please see the bugs <url |
| 1338 |
|
id="http://bugs.debian.org/381262" name="#381262"> and <url |
| 1339 |
|
id="http://bugs.debian.org/395066" name="#395066"> for more |
| 1340 |
|
information. |
| 1341 |
|
</p> |
| 1342 |
|
</sect1> |
| 1343 |
|
<sect1 id="poweroff"> |
| 1344 |
|
<heading> |
| 1345 |
|
Automatic poweroff stops working |
| 1346 |
|
</heading> |
| 1347 |
|
<p> |
| 1348 |
|
On some older systems, <prgn>shutdown -h</prgn> may not power off the |
| 1349 |
|
system anymore (but just stop it). This happens because apm needs to |
| 1350 |
|
be used there. Adding <tt>acpi=off apm=power_off</tt> to the kernel's |
| 1351 |
|
command line, e.g. in <package>grub</package> or |
| 1352 |
|
<package>lilo</package> configuration files should fix this |
| 1353 |
|
issue. Please see bug <url id="http://bugs.debian.org/390547" |
| 1354 |
|
name="#390547"> for additional information. |
| 1355 |
|
</p> |
| 1356 |
|
</sect1> |
| 1357 |
|
<sect1 id="apt-pdiff"> |
| 1358 |
|
<heading> |
| 1359 |
|
Apt downloads small files with update |
| 1360 |
|
</heading> |
| 1361 |
|
<p> |
| 1362 |
|
There has been support added to <prgn>apt</prgn> to download only the |
| 1363 |
|
difference between packages files. This is handy for people with bad |
| 1364 |
|
network connections, but people having a very nearby mirror may want |
| 1365 |
|
to disable this feature. One can disable it by adding |
| 1366 |
|
<tt>Acquire::Pdiffs "false";</tt> to <file>/etc/apt/apt.conf</file>. |
| 1367 |
|
</p> |
| 1368 |
|
</sect1> |
| 1369 |
|
</sect> |
| 1370 |
|
<![ %defaulted-2.4 [ |
| 1371 |
|
|
| 1372 |
|
<sect id="upgrade-to-2.6"> |
| 1373 |
|
<heading> |
| 1374 |
|
升级到2.6内核 |
| 1375 |
|
</heading> |
| 1376 |
|
<p> |
| 1377 |
|
2.6系列内核与2.4系列相比有重大改变。模块被改名，许多驱动程序被部分或全部改写。因此升级到2.6内核不那么容易。这一部分旨在让您了解一些需要注意的地方。 |
| 1378 |
|
</p> |
| 1379 |
|
<p> |
| 1380 |
|
强烈建议您不要把升级到2.6内核当作从&oldreleasename;升级到&releasename;的一部分。您应该确保系统在原有内核或&releasename;的2.4内核上正常工作，然后升级到2.6内核。要把升级内核当成一项独立任务！ |
| 1381 |
|
</p> |
| 1382 |
|
<p> |
| 1383 |
|
如果您编译新内核，应确保在重启之前安装了<package>module-init-tools</package>。这一软件包在2.6内核下取代<package>modutils</package>。如果您安装<package>linux-image</package>之一，这一软件包会由于依赖关系被自动安装。 |
| 1384 |
|
</p> |
| 1385 |
|
<p> |
| 1386 |
|
#-#-#-#-# choice #-#-#-#-# |
| 1387 |
|
如果您用<em>LVM</em>，就应当在重启前安装<package>lvm2</package>，因为2.6内核不直接支持LVM1。<package>lvm2</package>(dm-mod模块)被用来访问LVM1卷。您可以安装<package>lvm10</package>——一个在启动时检查哪种内核被使用，然后执行相应模块的脚本。 |
| 1388 |
|
#-#-#-#-# choice #-#-#-#-# |
| 1389 |
|
如果您用<em>LVM</em>，就应当在重启前安装<package>lvm2</package>，因为2.6内核不直接支持LVM1。<package>lvm2</package>(dm-mod模块)被用来访问LVM1卷。您可以安装<package>lvm10</package> |
| 1390 |
|
installed;，一个在启动时检查哪种内核被使用，然后执行相应模块的脚本。 |
| 1391 |
|
</p> |
| 1392 |
|
<p> |
| 1393 |
|
注意一些模块名称有所改变，请检查修改<file>/etc/modules</file>(在启动时自动执行的模块列表)，把旧名改为新名。 |
| 1394 |
|
</p> |
| 1395 |
|
<![ %i386-amd64 [ |
| 1396 |
|
|
| 1397 |
|
<p> |
| 1398 |
|
对于一些SATA磁盘控制器，驱动器的关联文件可能从<file>/dev/hdX</file>变为<file>/dev/sdX</file>。如果出现这种情况，就得修改 |
| 1399 |
|
<file>/etc/fstab</file>与启动程序的配置。只有在正确地修改之后，系统才能正常启动。 |
| 1400 |
|
</p> |
| 1401 |
|
]]> |
| 1402 |
|
|
| 1403 |
|
<p> |
| 1404 |
|
注意在安装完2.6内核重启之前，要确保有一种恢复措施。首先，确保启动程序可以新内核和旧内核（2.4内核）启动。还需要确保手头有紧急修复软盘或光盘，以防万一启动程序的错误配置导致无法从旧内核启动。 |
| 1405 |
|
</p> |
| 1406 |
|
<![ %not-s390 [<![ %not-amd64 [ |
| 1407 |
|
|
| 1408 |
|
<sect1 id="2.6-keyboard"> |
| 1409 |
|
<heading> |
| 1410 |
|
键盘配置 |
| 1411 |
|
</heading> |
| 1412 |
|
<p> |
| 1413 |
|
2.6内核最扰人的改变是输入层的低级变化。这一变化使所有的键盘都变得像“正常”的PC键盘。这意味着如果您目前有一个不同种类的键盘(例如一个USB-MAC或Sun键盘)，它极有可能在重启后无法工作。 |
| 1414 |
|
</p> |
| 1415 |
|
<p> |
| 1416 |
|
如果可以从其它系统通过SSH访问，您可以运行<tt>'dpkg-reconfigure |
| 1417 |
|
console-data'</tt>来解决问题，只要选择"Select keymap from full |
| 1418 |
|
list"然后选择"pc"键盘。 |
| 1419 |
|
</p> |
| 1420 |
|
<p> |
| 1421 |
|
如果终端键盘也被影响了，您也许还得为X Windows |
| 1422 |
|
System重新配置键盘。可以执行<tt>dpkg-reconfigure |
| 1423 |
|
xserver-xfree86</tt>或直接修改<file>/etc/X11/XF86Config-4</file>。 |
| 1424 |
|
不要忘记阅读相关文档<ref id="nownownow">。 |
| 1425 |
|
</p> |
| 1426 |
|
<![ %i386 [ |
| 1427 |
|
|
| 1428 |
|
<p> |
| 1429 |
|
这个问题不会影响&arch-title;，因为所有PS/2和大部分USB键盘将被配置为“正常”PC键盘。 |
| 1430 |
|
</p> |
| 1431 |
|
]]><![ %not-i386 [ |
| 1432 |
|
|
| 1433 |
|
<p> |
| 1434 |
|
注意如果您在使用USB键盘，它可能配置为“正常”PC键盘或USB-MAC键盘。在前一种情况下，您不会被这一问题所影响。 |
| 1435 |
|
</p> |
| 1436 |
|
]]> |
| 1437 |
|
|
| 1438 |
|
</sect1> |
| 1439 |
|
]]> |
| 1440 |
|
|
| 1441 |
|
<sect1 id="2.6-mouse"> |
| 1442 |
|
<heading> |
| 1443 |
|
鼠标配置 |
| 1444 |
|
</heading> |
| 1445 |
|
<p> |
| 1446 |
|
还是由于输入层的变化，如果您的鼠标在2.6内核下不工作，您可能得重新配置X |
| 1447 |
|
Window |
| 1448 |
|
System和<package>gpm</package>。最可能的原因是接收鼠标数据的设备变了。您可能还需要载入一些模块。 |
| 1449 |
|
</p> |
| 1450 |
|
<![ %sparc [ |
| 1451 |
|
|
| 1452 |
|
<p> |
| 1453 |
|
如果您配置X使用<file>/dev/sunmouse</file>，可能需要改为<file>/dev/psaux</file>。 |
| 1454 |
|
</p> |
| 1455 |
|
]]> |
| 1456 |
|
|
| 1457 |
|
</sect1> |
| 1458 |
|
<sect1 id="2.6-sound"> |
| 1459 |
|
<heading> |
| 1460 |
|
声音配置 |
| 1461 |
|
</heading> |
| 1462 |
|
<p> |
| 1463 |
|
对于2.6内核，ALSA声音驱动程序比OSS声音驱动程序更受偏爱。ALSA声音驱动默认以内核模块的形式提供。所以必须加载适当的模块，声音系统才会工作。如果您连同<package>alsa-base</package>安装了<package>hotplug</package>或<package>discover</package>，声卡的ALSA模块会被自动载入；这也会自动把OSS驱动加入<package>discover</package>和<package>hotplug</package>的黑名单来阻止它们被读取。如果在<file>/etc/modules</file>中有OSS驱动，应移除。 |
| 1464 |
|
</p> |
| 1465 |
|
</sect1> |
| 1466 |
|
]]> |
| 1467 |
|
|
| 1468 |
|
<sect1 id="2.6-udev"> |
| 1469 |
|
<heading> |
| 1470 |
|
升级到2.6内核可能会启用udev |
| 1471 |
|
</heading> |
| 1472 |
|
<p> |
| 1473 |
|
<package>udev</package>是devfs在用户层的实现。它挂载在<file>/dev</file>目录并把它与内核支持的硬件相关联。它与<package>hotplug</package>一起来检测新设备，动态地针对模块的装载和卸载进行目录配置。<package>udev</package>仅能在2.6内核下运行。 |
| 1474 |
|
</p> |
| 1475 |
|
<p> |
| 1476 |
|
由于<package>udev</package>会因为2.6内核initrd生成器（<package>initramfs-tools</package>）的依赖关系而被自动安装。升级至2.6内核时可能会启用<package>udev</package>。 |
| 1477 |
|
</p> |
| 1478 |
|
<p> |
| 1479 |
|
虽然<package>udev</package>已经过了广泛的测试，但您还是可能在某些设备上遇到一些必须修正小问题。最常见的问题是某个设备的权限变更。某些状况下，有些设备是不会被默认建立的。（如：<file>/dev/video</file> |
| 1480 |
|
和<file>/dev/radio</file>）。 |
| 1481 |
|
</p> |
| 1482 |
|
<p> |
| 1483 |
|
<package>udev</package>提供处理这些问题的配置方案。请查看 <manref |
| 1484 |
|
section="8" name="udev">和<file>/etc/udev</file> 来取得详细信息。 |
| 1485 |
|
</p> |
| 1486 |
|
</sect1> |
| 1487 |
|
</sect> |
| 1488 |
|
]]> |
| 1489 |
|
|
| 1490 |
|
<sect id="xorg"> |
| 1491 |
|
<heading> |
| 1492 |
|
XFree86 to X.Org transition |
| 1493 |
|
</heading> |
| 1494 |
|
<p> |
| 1495 |
|
The transition to X.Org involves some structural changes. In case all |
| 1496 |
|
installed packages are from Debian and also included in &releasename;, |
| 1497 |
|
the upgrade should work without problems. Experience has however shown |
| 1498 |
|
there are a few changes to be aware of as they can potentially cause |
| 1499 |
|
issues during the upgrade. |
| 1500 |
|
</p> |
| 1501 |
|
<p> |
| 1502 |
|
The most important change is that <file>/usr/X11R6/bin</file> has been |
| 1503 |
|
dropped and only remains as a symlink to <file>/usr/bin</file>. This |
| 1504 |
|
means this directory has to be empty at the time the new packages are |
| 1505 |
|
installed. The new packages conflict with most packages that used |
| 1506 |
|
<file>/usr/X11R6/bin</file>, but in some cases manual intervention may |
| 1507 |
|
be needed. Please remember to not run upgrades within an X session. |
| 1508 |
|
</p> |
| 1509 |
|
<p> |
| 1510 |
|
In case the upgrade aborts during X.Org installation, you should check |
| 1511 |
|
if any files are still left in <file>/usr/X11R6/bin</file>. You can |
| 1512 |
|
then use <tt>dpkg -S</tt> to find out which Debian package installed |
| 1513 |
|
that file (if any), and remove such packages with <tt>dpkg |
| 1514 |
|
--remove</tt>. Please make a note which packages you remove, so that |
| 1515 |
|
you can install substitute packages later on. Before continuing with |
| 1516 |
|
the upgrade, all files in <file>/usr/X11R6/bin</file> need to be |
| 1517 |
|
removed. |
| 1518 |
|
</p> |
| 1519 |
|
<p> |
| 1520 |
|
Please read <url id="http://wiki.debian.org/Xorg69To7"> for more |
| 1521 |
|
details and other issues. |
| 1522 |
|
</p> |
| 1523 |
|
</sect> |
| 1524 |
|
<sect id="exim"> |
| 1525 |
|
<heading> |
| 1526 |
|
Upgrading from exim to exim4 |
| 1527 |
|
</heading> |
| 1528 |
|
<p> |
| 1529 |
|
One of the packages that has been obsoleted by the &releasename; |
| 1530 |
|
release is the Mail Transfer Agent (MTA) exim, which has been replaced |
| 1531 |
|
by the completely new package exim4. |
| 1532 |
|
</p> |
| 1533 |
|
<p> |
| 1534 |
|
exim (version 3.xx) has been unmaintained upstream for years, and |
| 1535 |
|
Debian has dropped support for that version as well. If you are still |
| 1536 |
|
using exim 3.xx, please upgrade your exim installation to exim4 |
| 1537 |
|
manually. Since exim4 is already part of &oldreleasename, you can |
| 1538 |
|
choose to do the upgrade on your &oldreleasename; system before the |
| 1539 |
|
upgrade to &releasename;, or after the &releasename; upgrade at your |
| 1540 |
|
convenience. Just remember that your old exim package is not going to |
| 1541 |
|
be upgraded and that it won't get security support after support for |
| 1542 |
|
&oldreleasename; will be discontinued. |
| 1543 |
|
</p> |
| 1544 |
|
<p> |
| 1545 |
|
The exim4 packages in Debian are extensively documented. The package's |
| 1546 |
|
home page is <url id="http://wiki.debian.org/PkgExim4"> on the Debian |
| 1547 |
|
Wiki, and the README file can be found at <url |
| 1548 |
|
id="http://pkg-exim4.alioth.debian.org/README/etch/README.Debian.html"> |
| 1549 |
|
and inside the packages as well. |
| 1550 |
|
</p> |
| 1551 |
|
<p> |
| 1552 |
|
The README file has a chapter about Packaging, which explains the |
| 1553 |
|
different package variations we offer, and it has a chapter about |
| 1554 |
|
Updating from Exim 3, which will help you in doing the actual |
| 1555 |
|
transition. |
| 1556 |
|
</p> |
| 1557 |
|
</sect> |
| 1558 |
|
<sect id="apache2"> |
| 1559 |
|
<heading> |
| 1560 |
|
Upgrading apache2 |
| 1561 |
|
</heading> |
| 1562 |
|
<p> |
| 1563 |
|
Apache has been upgraded to the new version 2.2. Although this |
| 1564 |
|
shouldn't impact the average user, there are some potential issues to |
| 1565 |
|
be aware of. |
| 1566 |
|
</p> |
| 1567 |
|
<p> |
| 1568 |
|
<url id="http://httpd.apache.org/docs/2.2/upgrading.html"> contains the |
| 1569 |
|
upstream changes. Please read this page, and remember that especially: |
| 1570 |
|
<list> |
| 1571 |
|
<item> |
| 1572 |
|
<p> |
| 1573 |
|
all modules need to be recompiled |
| 1574 |
|
</p> |
| 1575 |
|
</item> |
| 1576 |
|
<item> |
| 1577 |
|
<p> |
| 1578 |
|
authorization modules have been resorted and renamed |
| 1579 |
|
</p> |
| 1580 |
|
</item> |
| 1581 |
|
<item> |
| 1582 |
|
<p> |
| 1583 |
|
some configuration options have been renamed |
| 1584 |
|
</p> |
| 1585 |
|
</item> |
| 1586 |
|
</list> |
| 1587 |
|
</p> |
| 1588 |
|
<p> |
| 1589 |
|
Debian-specific changes include that the string SSL is no longer |
| 1590 |
|
defined, as ssl is now supported by the default package. |
| 1591 |
|
</p> |
| 1592 |
|
</sect> |
| 1593 |
|
<sect id="php-globals"> |
| 1594 |
|
<heading> |
| 1595 |
|
Deprecated insecure php configurations |
| 1596 |
|
</heading> |
| 1597 |
|
<p> |
| 1598 |
|
For many years, turning on the <tt>register_globals</tt> settings in |
| 1599 |
|
PHP has been known to be insecure and dangerous, and this option has |
| 1600 |
|
defaulted to off for some time now. This configuration is now finally |
| 1601 |
|
deprecated on Debian systems as too dangerous. The same applies to |
| 1602 |
|
flaws in <tt>safe_mode</tt> and <tt>open_basedir</tt>, which have also |
| 1603 |
|
been unmaintained for some time. |
| 1604 |
|
</p> |
| 1605 |
|
<p> |
| 1606 |
|
Starting with this release, the Debian security team does not provide |
| 1607 |
|
security support for a number of PHP configurations which are known to |
| 1608 |
|
be insecure. Most importantly, issues resulting from |
| 1609 |
|
<tt>register_globals</tt> being turned on will no longer be addressed. |
| 1610 |
|
</p> |
| 1611 |
|
<p> |
| 1612 |
|
If you run legacy applications that require <tt>register_globals</tt>, |
| 1613 |
|
enable it for the respective paths only, e.g. through the Apache |
| 1614 |
|
configuration file. More information is available in the |
| 1615 |
|
<file>README.Debian.security</file> file in the PHP documentation |
| 1616 |
|
directory (<file>/usr/share/doc/php4</file>, |
| 1617 |
|
<file>/usr/share/doc/php5</file>). |
| 1618 |
|
</p> |
| 1619 |
|
</sect> |
| 1620 |
|
<sect id="mozilla-security"> |
| 1621 |
|
<heading> |
| 1622 |
|
Security status of mozilla products |
| 1623 |
|
</heading> |
| 1624 |
|
<p> |
| 1625 |
|
The Mozilla programs are important tools for many users. Unfortunately |
| 1626 |
|
the upstream security policy is to urge users to update to new upstream |
| 1627 |
|
versions, which conflicts with Debian's policy not to ship large |
| 1628 |
|
functional changes in security updates. We cannot predict it today, but |
| 1629 |
|
during lifetime of &releasename; the Debian Security Team may come to a |
| 1630 |
|
point where supporting Mozilla products is no longer feasible and |
| 1631 |
|
announce the end of security support for Mozilla products. You should |
| 1632 |
|
take this into account when deploying Mozilla and consider alternatives |
| 1633 |
|
available in Debian if the absence of security support would pose a |
| 1634 |
|
problem for you. |
| 1635 |
|
</p> |
| 1636 |
|
</sect> |
| 1637 |
|
</chapt> |
| 1638 |
|
<chapt id="moreinfo"> |
| 1639 |
|
<heading> |
| 1640 |
|
有关&debian;的更多信息 |
| 1641 |
|
</heading> |
| 1642 |
|
<sect id="morereading"> |
| 1643 |
|
<heading> |
| 1644 |
|
进一步阅读 |
| 1645 |
|
</heading> |
| 1646 |
|
<p> |
| 1647 |
|
Beyond these release notes and the installation guide, further |
| 1648 |
|
documentation on &debian; is available from the Debian Documentation |
| 1649 |
|
Project (DDP), whose goal is to create high quality documentation for |
| 1650 |
|
Debian users and developers. Documentation including the Debian |
| 1651 |
|
Reference, Debian New Maintainers Guide, and Debian FAQ are available, |
| 1652 |
|
and many more. For full details of the existing resources see the <url |
| 1653 |
|
id="&url-ddp;" name="DDP website">. |
| 1654 |
|
</p> |
| 1655 |
|
<p> |
| 1656 |
|
为特殊软件包准备的Documentation被安装在 |
| 1657 |
|
<file>/usr/share/doc/<var>package</var></file>，这可能包含copyright信息，Debian专门信息，和一些上游Documentation。 |
| 1658 |
|
</p> |
| 1659 |
|
</sect> |
| 1660 |
|
<sect id="gethelp"> |
| 1661 |
|
<heading> |
| 1662 |
|
获得帮助 |
| 1663 |
|
</heading> |
| 1664 |
|
<p> |
| 1665 |
|
Debian用户可获得各种形式帮助、建议和支持，但是这些只在您细致研究了所有与问题相关的Documentation的情况下才被考虑。这一部分提供对Debian用户有益的简短指导。 |
| 1666 |
|
</p> |
| 1667 |
|
<sect1 id="lists"> |
| 1668 |
|
<heading> |
| 1669 |
|
邮件列表 |
| 1670 |
|
</heading> |
| 1671 |
|
<p> |
| 1672 |
|
Debian用户最喜欢的邮件列表是debian-user列表(英语)和其它debian-user-<var>language</var>列表(别的语言)。查看<url |
| 1673 |
|
id="&url-debian-list-archives;">以获取这些列表的信息和加入邮件列表的方法。请在发邮件之前检查您问题已有的解答并且要遵循标准邮件列表格式。 |
| 1674 |
|
</p> |
| 1675 |
|
</sect1> |
| 1676 |
|
<sect1 id="irc"> |
| 1677 |
|
<heading> |
| 1678 |
|
IRC |
| 1679 |
|
</heading> |
| 1680 |
|
<p> |
| 1681 |
|
Debian has an IRC channel dedicated to the support and aid of Debian |
| 1682 |
|
users located on the OFTC IRC network which exists to provide |
| 1683 |
|
interactive services to peer-directed project communities. To access |
| 1684 |
|
the channel, point your favourite IRC client at &debian-irc-server; |
| 1685 |
|
and join #debian. |
| 1686 |
|
</p> |
| 1687 |
|
<p> |
| 1688 |
|
请遵守频道指南，尊敬其它用户。访问<url id="&url-irc-host;" |
| 1689 |
|
name="website">来获取OFTC的更多信息。 |
| 1690 |
|
</p> |
| 1691 |
|
</sect1> |
| 1692 |
|
</sect> |
| 1693 |
|
<sect id="bugs"> |
| 1694 |
|
<heading> |
| 1695 |
|
报告bug |
| 1696 |
|
</heading> |
| 1697 |
|
<p> |
| 1698 |
|
我们努力把Debian打造成高性能操作系统，但是那不意味着我们提供的软件包完全没有bug。作为为用户提供的服务和Debian开放性开发的实践，我们在<url |
| 1699 |
|
id="&url-bts;" |
| 1700 |
|
name="bugs.debian.org">的Bug跟踪系统(BTS)中提供所有已报告bug的信息。 |
| 1701 |
|
</p> |
| 1702 |
|
<p> |
| 1703 |
|
如果您在发行版或它里面的打包软件中发现了一个bug，请报告这个bug以便它可以在下一发行版中得到修复。报告bug需要一个合法的Email地址，以使我们可以追踪bug，也使开发人员在需要更多信息的情况下与报告者取得联系。 |
| 1704 |
|
</p> |
| 1705 |
|
<p> |
| 1706 |
|
您可以使用<package>reportbug</package>或手动地使用Email提交一个bug报告。您可以在装有<package>doc-debian</package>的Debian系统中的<file>/usr/share/doc/debian</file>或在网上<url |
| 1707 |
|
id="&url-bts;" |
| 1708 |
|
</p> |
| 1709 |
|
</sect> |
| 1710 |
|
<sect id="contributing"> |
| 1711 |
|
<heading> |
| 1712 |
|
为Debian做贡献 |
| 1713 |
|
</heading> |
| 1714 |
|
<p> |
| 1715 |
|
来为Debian做贡献，您不必是一名专家。在<url |
| 1716 |
|
id="&url-debian-list-archives;" |
| 1717 |
|
name="用户邮件列表">中帮助用户解决问题就是在为Debian社区做贡献。在<url |
| 1718 |
|
id="&url-debian-list-archives;" |
| 1719 |
|
name="开发邮件列表">中检查(并且解决)与发行版开发相关的问题对Debian也极其有帮助。可以<url |
| 1720 |
|
id="&url-bts;" |
| 1721 |
|
name="报告bug">并且帮助开发人员追踪和修复bug来保持Debian的高性能。如果您语言能力强，您可能会愿意通过写<url |
| 1722 |
|
id="&url-ddp;" name="documentation">或用您自己的语言<url |
| 1723 |
|
id="&url-debian-i18n;" |
| 1724 |
|
name="翻译">已有的Documentation来做更活跃的贡献。 |
| 1725 |
|
</p> |
| 1726 |
|
<p> |
| 1727 |
|
如果您有更多时间，您可以在Debian中维护自由软件，<url id="&url-wnpp;" |
| 1728 |
|
name="Work Needing and Prospective Packages数据库"> |
| 1729 |
|
会详细介绍这一信息。如果您在某一特殊领域感兴趣，那么您可能在Debian的一些子项目如系统平台移植、<url |
| 1730 |
|
id="&url-debian-jr;" name="Debian Jr.">和<url id="&url-debian-med;" |
| 1731 |
|
name="Debian Med">中获得乐趣。 |
| 1732 |
|
</p> |
| 1733 |
|
<p> |
| 1734 |
|
在任何情况下，如果您在以任何形式在自由软件社区内工作，不论是以用户、程序员还是写作者、翻译者身份，您已经在帮助自由软件。贡献是光荣而又有趣的，而且让您结识新朋友，这会给您一种来自内心深处的温暖! |
| 1735 |
|
</p> |
| 1736 |
|
</sect> |
| 1737 |
|
</chapt> |
| 1738 |
|
<appendix id="old-stuff"> |
| 1739 |
|
<heading> |
| 1740 |
|
管理&oldreleasename;系统 |
| 1741 |
|
</heading> |
| 1742 |
|
<p> |
| 1743 |
|
本附录包含在升级到&releasename;之前如何安装或升级&oldreleasename;软件包。这仅在某些特殊情况下有用。 |
| 1744 |
|
</p> |
| 1745 |
|
<sect id="old-upgrade"> |
| 1746 |
|
<heading> |
| 1747 |
|
升级&oldreleasename;系统 |
| 1748 |
|
</heading> |
| 1749 |
|
<p> |
| 1750 |
|
基本上这与从前进行的&oldreleasename;升级没什么区别。仅有的区别在于首先您应确保软件包列表仍指向&oldreleasename;，正如<ref |
| 1751 |
|
id="old-sources">中解释的。 |
| 1752 |
|
</p> |
| 1753 |
|
</sect> |
| 1754 |
|
<sect id="old-sources"> |
| 1755 |
|
<heading> |
| 1756 |
|
检查源列表 |
| 1757 |
|
</heading> |
| 1758 |
|
<p> |
| 1759 |
|
如果<file>/etc/apt/sources.list</file>中的任何行指向'stable'，您正在“使用”&releasename;。如果您已经执行<tt>apt-get |
| 1760 |
|
update</tt>，也可以遵循以下操作很轻松地回到&oldreleasename。 |
| 1761 |
|
</p> |
| 1762 |
|
<p> |
| 1763 |
|
如果您已经从&releasename;安装了软件包，安装&oldreleasename;的软件包就不太容易了。万一这样，您就要自己决定是否继续。可以进行软件包降级，但这非本说明所及。 |
| 1764 |
|
</p> |
| 1765 |
|
<p> |
| 1766 |
|
以root身份，打开<file>/etc/apt/sources.list</file>检查所有以<tt>deb |
| 1767 |
|
http:</tt>或<tt>deb |
| 1768 |
|
ftp:</tt>开头的行是否指向"<tt>stable</tt>"。如果有，把<tt>stable</tt>改为<tt>&oldreleasename;</tt>。 |
| 1769 |
|
</p> |
| 1770 |
|
<p> |
| 1771 |
|
如果有以<tt>deb |
| 1772 |
|
file:</tt>开头的行，那您将得自己检查它指向的地址是包含&oldreleasename;还是&releasename;软件。 |
| 1773 |
|
</p> |
| 1774 |
|
<p> |
| 1775 |
|
<strong>重要提示！</strong>不要修改以<tt>deb |
| 1776 |
|
cdrom:</tt>开头的行。否则会出错，以致不得不重新运行apt-cdrom |
| 1777 |
|
。不要因为'cdrom'行指向"<tt>unstable</tt>"而感到惊讶。虽然令人困惑，但这是正常的。 |
| 1778 |
|
</p> |
| 1779 |
|
<p> |
| 1780 |
|
如果您做了修改，保存文件然后执行 |
| 1781 |
|
<example> |
| 1782 |
# apt-get update |
# apt-get update |
| 1783 |
</example> |
</example> |
| 1784 |
|
来更新软件包列表。 |
| 1785 |
来更新软件包列表。</p> |
</p> |
| 1786 |
|
</sect> |
| 1787 |
</sect> |
</appendix> |
| 1788 |
|
</book> |
|
</appendix> |
|
|
</book> |
|
| 1789 |
</debiandoc> |
</debiandoc> |
|
|
|
|
<!-- Keep this comment at the end of the file |
|
|
Local Variables: |
|
|
mode: sgml |
|
|
sgml-omittag:t |
|
|
sgml-shorttag:t |
|
|
sgml-namecase-general:t |
|
|
sgml-general-insert-case:lower |
|
|
sgml-minimize-attributes:nil |
|
|
sgml-always-quote-attributes:t |
|
|
sgml-indent-step:2 |
|
|
sgml-indent-data:nil |
|
|
sgml-declaration:nil |
|
|
sgml-parent-document:nil |
|
|
sgml-exposed-tags:nil |
|
|
sgml-local-catalogs:nil |
|
|
sgml-local-ecat-files:nil |
|
|
fill-column: 75 |
|
|
End: |
|
|
--> |
|
Parent Directory
| 
Revision Log
| 
Patch