diff options
Diffstat (limited to 'po/zh_CN')
| -rw-r--r-- | po/zh_CN/boot-new.po | 84 | ||||
| -rw-r--r-- | po/zh_CN/hardware.po | 587 | ||||
| -rw-r--r-- | po/zh_CN/install-methods.po | 135 |
3 files changed, 157 insertions, 649 deletions
diff --git a/po/zh_CN/boot-new.po b/po/zh_CN/boot-new.po index d83942d9e..0a56fad74 100644 --- a/po/zh_CN/boot-new.po +++ b/po/zh_CN/boot-new.po @@ -4,7 +4,7 @@ msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2006-12-27 20:04+0000\n" -"PO-Revision-Date: 2006-10-25 20:41+0800\n" +"PO-Revision-Date: 2007-01-08 18:27+0800\n" "Last-Translator: Ji YongGang<jungle@soforge.com>\n" "Language-Team: debian-chinese-gb <debian-chinese-gb@lists.debian.org>\n" "MIME-Version: 1.0\n" @@ -43,7 +43,7 @@ msgid "" "will be for your new Debian system. If you had any other operating systems " "on your computer (like Windows) that were detected by the installation " "system, those will be listed lower down in the menu." -msgstr "" +msgstr "如果使用了默认安装，引导系统后您首先看到的是 <classname>grub</classname> 菜单或者是 <classname>lilo</classname> bootloader。菜单中的首选项将是您的新 Debian 系统。假如您的计算机上有其他的操作系统(如 Windows)，它们将被安装系统检测到，列入菜单的下方。" #. Tag: para #: boot-new.xml:23 @@ -55,7 +55,7 @@ msgid "" "such problems can be fixed without having to repeat the installation. One " "available option to fix boot problems is to use the installer's built-in " "rescue mode (see <xref linkend=\"rescue\"/>)." -msgstr "" +msgstr "如果系统无法正确启动，请勿惊慌。如果安装成功，还不错，只是出了一点儿小问题没法让系统引导 Debian。多数情况下不需重新安装就能修复。修复引导问题的一个方法是使用安装程序内置的 rescue 模式(参阅 <xref linkend=\"rescue\"/>)。" #. Tag: para #: boot-new.xml:32 @@ -72,7 +72,7 @@ msgid "" "linkend=\"submit-bug\"/>. Please make sure that you describe your problem " "clearly and include any messages that are displayed and may help others to " "diagnose the issue." -msgstr "" +msgstr "假如您刚接触 Debian 和 Linux，您可能需要从有经验的用户那里得到一些帮助。<phrase arch=\"x86\">直接的在线帮助，可以通过 OFTC network 上的 #debian 或 #debian-boot IRC 频道。另一种选择是 <ulink url=\"&url-list-subscribe;\">debian-user mailing list</ulink>。</phrase> <phrase arch=\"not-x86\">对于不常见的体系，比如 &arch-title;，最适合的方式是在 <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> 上请教。</phrase> 您也可以写下安装报告，说明见 <xref linkend=\"submit-bug\"/>。请确保问题描述清楚，并包括显示的任何信息，以助于分析问题。" #. Tag: para #: boot-new.xml:48 @@ -80,7 +80,7 @@ msgstr "" msgid "" "If you had any other operating systems on your computer that were not " "detected or not detected correctly, please file an installation report." -msgstr "" +msgstr "如果您计算机上的其他操作系统没有被侦测到，或者未被正确侦测，请撰写一份安装报告。" #. Tag: title #: boot-new.xml:55 @@ -589,7 +589,7 @@ msgstr "登录" #. Tag: para #: boot-new.xml:385 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Once your system boots, you'll be presented with the login prompt. Log in " "using the personal login and password you selected during the installation " @@ -622,11 +622,11 @@ msgid "" "example, documentation about the package management tool <command>apt</" "command> can be found in the packages <classname>apt-doc</classname> or " "<classname>apt-howto</classname>." -msgstr "" +msgstr "已安装程序相关的文档可以在 <filename>/usr/share/doc/</filename> 里找到，位于该程序名的子目录下(或者，更准确地说，包含该程序的软件包名)。但范围更广的文档会单独放在一个特殊的文档软件包内，默认并不安装。例如，关于软件包管理工具 <command>apt</command> 的文档放在 <classname>apt-doc</classname> 或 <classname>apt-howto</classname> 软件包内。" #. Tag: para #: boot-new.xml:410 -#, fuzzy, no-c-format +#, no-c-format msgid "" "In addition, there are some special folders within the <filename>/usr/share/" "doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</" @@ -634,12 +634,7 @@ msgid "" "filename>. After installing <classname>dhelp</classname>, you will find a " "browse-able index of documentation in <filename>/usr/share/doc/HTML/index." "html</filename>." -msgstr "" -"另外，还有一些特殊的目录位于 <filename>/usr/share/doc/</filename> 组织里。\n" -"Linux HOWTOs 以 <emphasis>.gz</emphasis> 格式安装，放在 <filename>/usr/share/" -"doc/HOWTO/en-txt/</filename>。\n" -"安装 <command>dhelp</command>之后，可以浏览 <filename>/usr/share/doc/HTML/" -"index.html</filename> 文档索引。" +msgstr "另外，还有一些特殊的目录位于 <filename>/usr/share/doc/</filename> 里。Linux HOWTOs 以 <emphasis>.gz</emphasis> (压缩)格式安装，放在 <filename>/usr/share/doc/HOWTO/en-txt/</filename>。安装 <command>dhelp</command>之后，可以浏览 <filename>/usr/share/doc/HTML/index.html</filename> 文档索引。" #. Tag: para #: boot-new.xml:419 @@ -652,6 +647,10 @@ msgid "" "</screen></informalexample> The dot after the <command>w3c</command> command " "tells it to show the contents of the current directory." msgstr "" +"使用基于文本的浏览器查看这些文档的简单方法是输入下面命令：<informalexample><screen>\n" +"$ cd /usr/share/doc/\n" +"$ w3c .\n" +"</screen></informalexample> <command>w3c</command> 命令后的点告知将显示当前目录下的内容。" #. Tag: para #: boot-new.xml:429 @@ -660,11 +659,11 @@ msgid "" "If you have a graphical desktop environment installed, you can also use its " "web browser. Start the web browser from the application menu and enter " "<userinput>/usr/share/doc/</userinput> in the address bar." -msgstr "" +msgstr "如果您安装了图形桌面环境，可以使用它的 web 浏览器。从应用程序菜单启动 web 浏览器，然后在地址栏内键入 <userinput>/usr/share/doc/</userinput>。" #. Tag: para #: boot-new.xml:435 -#, fuzzy, no-c-format +#, no-c-format msgid "" "You can also type <userinput>info <replaceable>command</replaceable></" "userinput> or <userinput>man <replaceable>command</replaceable></userinput> " @@ -676,55 +675,4 @@ msgid "" "after the command to cause the results to pause before scrolling past the " "top of the screen. To see a list of all commands available which begin with " "a certain letter, type the letter and then two tabs." -msgstr "" -"您也可以键入 <userinput>info <replaceable>command</replaceable></userinput> " -"或 <userinput>man <replaceable>command</replaceable></userinput> 在去查看大多" -"数的命令行下的命令。键入 <userinput>help</userinput> 将显示 shell 命令的帮" -"助。键入命令后面加上 <userinput>--help</userinput> 通常会显示命令用法的简短摘" -"要。如果命令的结果滚动超出屏幕顶端，键入 <userinput>| more</userinput> 于命令" -"之后，可以让输出暂停在滚出顶端屏幕。查看某子母开始的所有可用命令，键入该子" -"母，再是两个 tab。" - -#~ msgid "" -#~ "If you are booting directly into Debian, and the system doesn't start up, " -#~ "either use your original installation boot media, or insert the custom " -#~ "boot floppy if you have one, and reset your system. This way, you will " -#~ "probably need to add some boot arguments like " -#~ "<userinput>root=<replaceable>root</replaceable></userinput>, where " -#~ "<replaceable>root</replaceable> is your root partition, such as " -#~ "<filename>/dev/sda1</filename>. Alternatively, see <xref linkend=\"rescue" -#~ "\"/> for instructions on using the installer's built-in rescue mode." -#~ msgstr "" -#~ "如果直接启动 Debian，但系统没有起来，这时要么使用原来的安装启动媒介，要么" -#~ "使用您拥有的自定义启动软盘，然后重新启动系统。这种情况下，您也许需要添加一" -#~ "些启动参数，像 <userinput>root=<replaceable>root</replaceable></" -#~ "userinput>，其中 <replaceable>root</replaceable> 是您的根分区，例如 " -#~ "<filename>/dev/sda1</filename>。另外，参阅 <xref linkend=\"rescue\"/>，了" -#~ "解如何使用安装程序内嵌的 rescue 模式。" - -#~ msgid "" -#~ "Documentation accompanying programs you have installed is in <filename>/" -#~ "usr/share/doc/</filename>, under a subdirectory named after the program. " -#~ "For example, the APT User's Guide for using <command>apt</command> to " -#~ "install other programs on your system, is located in <filename>/usr/share/" -#~ "doc/apt/guide.html/index.html</filename>." -#~ msgstr "" -#~ "伴随程序的文档安装在 <filename>/usr/share/doc/</filename>，并在程序名命名" -#~ "的子目录下。例如，APT 用户指南是关于 <command>apt</command> 安装其他的程序" -#~ "到系统，位于 <filename>/usr/share/doc/apt/guide.html/index.html</" -#~ "filename>。" - -#~ msgid "" -#~ "One easy way to view these documents is to <userinput>cd /usr/share/doc/</" -#~ "userinput>, and type <userinput>lynx</userinput> followed by a space and " -#~ "a dot (the dot stands for the current directory)." -#~ msgstr "" -#~ "一种查看文档简易的方法是 <userinput>cd /usr/share/doc/</userinput>，然后键" -#~ "入 <userinput>lynx</userinput> 后面是空格加一个点(点是指当前目录)。" - -#~ msgid "" -#~ "For a more complete introduction to Debian and GNU/Linux, see <filename>/" -#~ "usr/share/doc/debian-guide/html/noframes/index.html</filename>." -#~ msgstr "" -#~ "了解更多的 Debian 和 GNU/Linux，请参阅 <filename>/usr/share/doc/debian-" -#~ "guide/html/noframes/index.html</filename>。" +msgstr "您也可以键入 <userinput>info <replaceable>command</replaceable></userinput> 或 <userinput>man <replaceable>command</replaceable></userinput> 去查看大多数的命令行下的命令。键入 <userinput>help</userinput> 将显示 shell 命令的帮助。键入命令后面加上 <userinput>--help</userinput> 通常会显示命令用法的简短摘要。如果命令的结果滚动超出屏幕顶端，命令后面加上 <userinput>| more</userinput>，可以让输出在滚出顶端屏幕前暂停。查看某字母开始的所有可用命令，键入该字母，然后两个 tab。" diff --git a/po/zh_CN/hardware.po b/po/zh_CN/hardware.po index 4c6a189de..64a53b6f4 100644 --- a/po/zh_CN/hardware.po +++ b/po/zh_CN/hardware.po @@ -4,7 +4,7 @@ msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2007-01-06 19:06+0000\n" -"PO-Revision-Date: 2006-10-31 21:18+0800\n" +"PO-Revision-Date: 2007-01-09 10:38+0800\n" "Last-Translator: Ji YongGang<jungle@soforge.com>\n" "Language-Team: debian-chinese-gb <debian-chinese-gb@lists.debian.org>\n" "MIME-Version: 1.0\n" @@ -115,9 +115,9 @@ msgstr "i386" #. Tag: entry #: hardware.xml:67 -#, fuzzy, no-c-format +#, no-c-format msgid "AMD64 & Intel EM64T" -msgstr "AMD64 & Intel EM64t" +msgstr "AMD64 & Intel EM64T" #. Tag: entry #: hardware.xml:68 @@ -165,25 +165,25 @@ msgstr "netwinder" #: hardware.xml:86 #, no-c-format msgid "Intel IOP32x" -msgstr "" +msgstr "Intel IOP32x" #. Tag: entry #: hardware.xml:87 #, no-c-format msgid "iop32x" -msgstr "" +msgstr "iop32x" #. Tag: entry #: hardware.xml:89 #, no-c-format msgid "Intel IXP4xx" -msgstr "" +msgstr "Intel IXP4xx" #. Tag: entry #: hardware.xml:90 #, no-c-format msgid "ixp4xx" -msgstr "" +msgstr "ixp4xx" #. Tag: entry #: hardware.xml:92 @@ -237,7 +237,7 @@ msgstr "<entry>64</entry>" #: hardware.xml:107 #, no-c-format msgid "Intel IA-64" -msgstr "" +msgstr "Intel IA-64" #. Tag: entry #: hardware.xml:108 @@ -488,33 +488,33 @@ msgstr "sparc" #. Tag: entry #: hardware.xml:183 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>sun4m</entry>" -msgstr "<entry>64</entry>" +msgstr "<entry>sun4m</entry>" #. Tag: entry #: hardware.xml:184 -#, fuzzy, no-c-format +#, no-c-format msgid "sparc32" -msgstr "sparc" +msgstr "sparc32" #. Tag: entry #: hardware.xml:186 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>sun4u</entry>" -msgstr "<entry>64</entry>" +msgstr "<entry>sun4u</entry>" #. Tag: entry #: hardware.xml:187 -#, fuzzy, no-c-format +#, no-c-format msgid "sparc64" -msgstr "sparc" +msgstr "sparc64" #. Tag: entry #: hardware.xml:189 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>sun4v</entry>" -msgstr "<entry>64</entry>" +msgstr "<entry>sun4v</entry>" #. Tag: entry #: hardware.xml:193 @@ -1789,22 +1789,19 @@ msgstr "<title>CPU</title>" #. Tag: para #: hardware.xml:703 -#, fuzzy, no-c-format +#, no-c-format msgid "Both AMD64 and Intel EM64T processors are supported." -msgstr "AMD64 和 Intel EM64t 处理器都获得支持。" +msgstr "AMD64 和 Intel EM64T 处理器都获得支持。" #. Tag: para #: hardware.xml:731 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Each distinct ARM architecture requires its own kernel. Because of this the " "standard Debian distribution only supports installation on a number of the " "most common platforms. The Debian userland however may be used by " "<emphasis>any</emphasis> ARM CPU." -msgstr "" -"每种 ARM 体系要求使用各自的内核，正因为如此，Debian 标准发布版只支持安装在一" -"些最常见的系统上。但 Debian userland 可以被包括 xscale 在内的 <emphasis>任何" -"</emphasis> ARM CPU 使用。" +msgstr "每种 ARM 体系要求使用各自的内核，正因为如此，Debian 标准发布版只支持安装到一些最常见的系统上。但 Debian userland 可以被 <emphasis>任何</emphasis> ARM CPU 使用。" #. Tag: para #: hardware.xml:740 @@ -1820,9 +1817,9 @@ msgstr "" #. Tag: para #: hardware.xml:748 -#, fuzzy, no-c-format +#, no-c-format msgid "The supported platforms are:" -msgstr "获得支持的系统有：" +msgstr "获得支持的平台有：" #. Tag: term #: hardware.xml:755 @@ -1848,7 +1845,7 @@ msgstr "" #: hardware.xml:769 #, no-c-format msgid "IOP32x" -msgstr "" +msgstr "IOP32x" #. Tag: para #: hardware.xml:770 @@ -1860,17 +1857,17 @@ msgid "" "Storage (NAS) devices. Debian explicitly supports two such devices: the " "<ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and " "the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>." -msgstr "" +msgstr "Intel I/O Processor (IOP) 产品线可以在一些数据存储和处理的产品中找到。Debian 当前支持 IOP32x 平台，IOP 80219 和 32x 芯片通常在 Network Attached Storage (NAS) 设备上找到。Debian 明确支持两个设备：IO-Data 的 <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> 和 <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>。" #. Tag: term #: hardware.xml:783 #, no-c-format msgid "IXP4xx" -msgstr "" +msgstr "IXP4xx" #. Tag: para #: hardware.xml:784 -#, fuzzy, no-c-format +#, no-c-format msgid "" "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one " "IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 " @@ -1879,10 +1876,7 @@ msgid "" "Ethernet connection and two USB ports to which hard drives can be connected. " "There is an external site with <ulink url=\"&url-arm-cyrius-nslu2;" "\">installation instructions</ulink>." -msgstr "" -"Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) 是一个小型的设" -"备，它让您可以通过网络很容易地提供存储。它带有一个以太网接口和两个 USB 口用于" -"硬盘连接。" +msgstr "IXP4xx 平台基于 Intel XScale ARM 核心。当前，只有一个基于 IXP4xx 的系统被支持，Linksys NSLU2。Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) 是一个通过网络提供易用存储的小型设备。它提供了一个以太网接口和两个 USB 端口来连接硬盘。这里有一个外部网站 <ulink url=\"&url-arm-cyrius-nslu2;\">installation instructions</ulink>。" #. Tag: term #: hardware.xml:798 @@ -1892,7 +1886,7 @@ msgstr "<term>RiscPC</term>" #. Tag: para #: hardware.xml:799 -#, fuzzy, no-c-format +#, no-c-format msgid "" "This machine is the oldest supported hardware but support for it in our new " "installer is incomplete. It has RISC OS in ROM, Linux can be booted from " @@ -1902,12 +1896,7 @@ msgid "" "and proprietary mouse port. The proprietary module expansion bus allows for " "up to eight expansion cards to be fitted depending on configuration, several " "of these modules have Linux drivers." -msgstr "" -"该机器发布于 1994 年，是最早支持的硬件。它在 ROM 里面包含 RISC OS，Linux 可以" -"使用 linloader 从该 OS 启动。RiscPC 有一种模块化的 CPU 卡，典型的安装有 " -"30MHz 610, 40MHz 710 或 233MHz Strongarm 110 CPU。主板集成了 IDE、SVGA 视频" -"卡、并口、单串口、PS/2 键盘和专有的鼠标口。依据不同的配置，专有的模块扩充总线" -"允许最多安装 8 块扩展卡，其中的一些模块有 Linux 驱动程序。" +msgstr "该机器是最早支持的硬件，但在我们新的安装程序里对它的支持还没有完成。它在 ROM 里面包含 RISC OS，Linux 可以使用 linloader 从该 OS 启动。RiscPC 有一种模块化的 CPU 卡，典型的安装有 30MHz 610、40MHz 710 或 233MHz Strongarm 110 CPU。主板集成了 IDE、SVGA 视频、并口、单串口、PS/2 键盘和专有的鼠标口。依据不同的配置，专有的模块扩充总线允许最多安装八块扩展卡，其中的一些模块有 Linux 驱动程序。" #. Tag: para #: hardware.xml:825 @@ -1927,31 +1916,26 @@ msgstr "" #. Tag: para #: hardware.xml:853 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Nearly all x86-based (IA-32) processors still in use in personal computers " "are supported, including all varieties of Intel's \"Pentium\" series. This " "also includes 32-bit AMD and VIA (former Cyrix) processors, and processors " "like the Athlon XP and Intel P4 Xeon." -msgstr "" -"几乎所有个人计算机中基于 x86 (IA-32) 的处理器都支持，包括所有的 Intel " -"\"Pentium\" 系列变种。还包括 32 位 AMD 和 VIA (前身是 Cyrix) 处理器，以及像 " -"Athlon XP 和 Intel P4 Xeon 这些较新的处理器。" +msgstr "几乎所有个人计算机中基于 x86 (IA-32) 的处理器都支持，包括所有的 Intel \"Pentium\" 系列变种。还包括 32 位 AMD 和 VIA (前身是 Cyrix) 处理器，以及像 Athlon XP 和 Intel P4 Xeon 这些处理器。" #. Tag: para #: hardware.xml:861 -#, fuzzy, no-c-format +#, no-c-format msgid "" "If your system has a 64-bit processor from the AMD64 or Intel EM64T " "families, you will probably want to use the installer for the amd64 " "architecture instead of the installer for the (32-bit) i386 architecture." -msgstr "" -"假如您的系统中有 64 位 AMD64、Intel EM64t 或者 Intel Core 2 Duo 处理器，要用 " -"amd64 架构的安装程序替代 (32位) i386 架构的安装程序。" +msgstr "假如您的系统中有 64 位 AMD64、Intel EM64T 家族的处理器，那么您该用 amd64 架构的安装程序替代 (32位) i386 架构的安装程序。" #. Tag: para #: hardware.xml:868 -#, fuzzy, no-c-format +#, no-c-format msgid "" "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on " "386 or earlier processors. Despite the architecture name \"i386\", support " @@ -1969,18 +1953,7 @@ msgid "" "introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the " "i386, introduced in 1986, did not have. Previously, these could not be " "easily used by most Debian packages; now they can. </para> </footnote>." -msgstr "" -"然而，Debian GNU/Linux &releasename; 将 <emphasis>不</emphasis> 运行在 386 或" -"更早的处理器上。尽管体系命名为 \"i386\"，Debian Sarge 已经 <emphasis>放弃</" -"emphasis> 对真正的 80386 处理器(以及它们的克隆)的支持，过去的版本曾经支持" -"<footnote> <para> 我们已经尽力避免，但由于编译器和内核的一系列因素，起因是 " -"GCC 提供的 C++ ABI 的 bug，最终只能如此。如果您自己动手从源码编译内核和所有的" -"软件包，仍然可以将 Debian GNU/Linux 运行在真正的 80386 处理器上，这部分内容超" -"出了本手册的范畴。</para> </footnote>。 (Linux 从来没有任何版本支持 286 或更" -"早的芯片。) i486 和后续的处理器仍然支持<footnote> <para> 许多 Debian 软件包在" -"新的计算机上可以运行地稍微快一点，但另一方面却舍弃了对就芯片的支持。1989 年发" -"布的 i486 有三个 opcodes (bswap, cmpxchg, and xadd)，然而 1986 年发布的 i386 " -"却没有。以前，Debain 软件包不能使用它们，现在可以了。</para> </footnote>." +msgstr "然而，Debian GNU/Linux &releasename; 将<emphasis>不能</emphasis>运行在 386 或更早的处理器上。尽管体系命名为 \"i386\"，Debian 的 Sarge (r3.1) 版已经<emphasis>放弃</emphasis>对真正的 80386 处理器(以及它们的克隆)的支持，过去的版本曾经支持<footnote> <para> 我们已经尽力避免，但由于编译器和内核的一系列因素，起因是 GCC 提供的 C++ ABI 的 bug，最终只能如此。如果您自己动手从源码编译内核和所有的软件包，仍然可以将 Debian GNU/Linux 运行在真正的 80386 处理器上，这部分内容超出了本手册的范畴。</para> </footnote>。(Linux 从来没有任何版本支持 286 或更早的芯片。) 所有的 i486 和后续的处理器仍然支持<footnote> <para> 许多 Debian 软件包在新的计算机上可以运行地稍微快一点，但另一方面却舍弃了对旧芯片的支持。1989 年发布的 i486 有三个 opcode (bswap、cmpxchg 和 xadd)，然而 1986 年发布的 i386 却没有。以前，Debain 软件包不能使用它们，现在可以了。</para> </footnote>。" #. Tag: title #: hardware.xml:905 @@ -2470,7 +2443,7 @@ msgstr "这种内核支持 PReP 子系统。" #: hardware.xml:1269 #, no-c-format msgid "apus" -msgstr "" +msgstr "apus" #. Tag: para #: hardware.xml:1270 @@ -3021,9 +2994,9 @@ msgstr "" # index.docbook:224, index.docbook:683, index.docbook:780, index.docbook:799, index.docbook:842, index.docbook:884, index.docbook:938, index.docbook:1085, index.docbook:1491 #. Tag: title #: hardware.xml:1644 -#, fuzzy, no-c-format +#, no-c-format msgid "CPU and Main Boards Support" -msgstr "CPU，主板和视频支持" +msgstr "CPU 和主板支持" #. Tag: para #: hardware.xml:1645 @@ -3033,13 +3006,13 @@ msgid "" "identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u " "or sun4v. The following list describes what machines they include and what " "level of support may be expected for each of them." -msgstr "" +msgstr "基于 sparc 的硬件分成不同的子体系，标识为下列名称：sun4、sun4c、sun4d、sun4m、sun4u 或 sun4v。下面说明包括哪些机器，以及每个获得支持的级别。" #. Tag: term #: hardware.xml:1656 #, no-c-format msgid "sun4, sun4c, sun4d" -msgstr "" +msgstr "sun4, sun4c, sun4d" #. Tag: para #: hardware.xml:1658 @@ -3048,13 +3021,13 @@ msgid "" "These subarchitectures include some very old 32-bit machines, which are no " "longer supported. For a complete list please consult the <ulink url=\"http://" "en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>." -msgstr "" +msgstr "这些子体系包含一些非常老的 32 位机器，它们不再获得支持。完整的列表，请查阅 <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>。" #. Tag: term #: hardware.xml:1669 -#, fuzzy, no-c-format +#, no-c-format msgid "<term>sun4m</term>" -msgstr "<term>apus</term>" +msgstr "<term>sun4m</term>" #. Tag: para #: hardware.xml:1671 @@ -3063,7 +3036,7 @@ msgid "" "sun4m is the only 32-bit subarchitecture (sparc32) that is currently " "supported. The most popular machines belonging to this class are " "Sparcstation 4, 5, 10 and 20." -msgstr "" +msgstr "sun4m 是当前惟一被支持的 32 位子体系(sparc32)。属于此类的流行机器有 Sparcstation 4、5、10 和 20。" #. Tag: para #: hardware.xml:1677 @@ -3074,13 +3047,13 @@ msgid "" "due to stability problems with such configurations. The available " "uniprocessor (UP) sparc32 kernel will boot fine on multiprocessor machines, " "although it will activate and use only the first CPU." -msgstr "" +msgstr "注意，symmetric multiprocessing (SMP) — 进程运行在多处理器上的能力 — 因为该配置下稳定性的问题，在此硬件上不被支持。现有的 uniprocessor (UP) sparc32 内核可以在多处理器机器上引导，但只激活和使用第一个 CPU。" #. Tag: term #: hardware.xml:1689 -#, fuzzy, no-c-format +#, no-c-format msgid "<term>sun4u</term>" -msgstr "<term>apus</term>" +msgstr "<term>sun4u</term>" #. Tag: para #: hardware.xml:1691 @@ -3092,13 +3065,13 @@ msgid "" "due to firmware or bootloader bugs (this problem may be worked around by " "using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP " "configurations respectively." -msgstr "" +msgstr "该子体系包括所有的基于 UltraSparc 处理器的 64 位机器(sparc64)及其克隆。大多数机器支持得很好，即使如此，您也可能会遇到因固件或 bootloader bug 引起的 CD 引导问题(该问题可通过使用网络引导避开)。分别地使用 sparc64 或 sparc64-smp 内核到 UP 和 SMP 配置中。" #. Tag: term #: hardware.xml:1704 -#, fuzzy, no-c-format +#, no-c-format msgid "<term>sun4v</term>" -msgstr "<term>apus</term>" +msgstr "<term>sun4v</term>" #. Tag: para #: hardware.xml:1706 @@ -3108,7 +3081,7 @@ msgid "" "based on the Niagara multi-core CPUs. At the moment such CPUs are only " "available in T1000 and T2000 servers by Sun, and are well supported. Use the " "sparc64-smp kernel." -msgstr "" +msgstr "这是 Sparc 家族中的最新成员，它们包括基于 Niagara 多核 CPU 的机器。当前该 CPU 只存在于 Sun 的 T1000 和 T2000 服务器上，并能很好地支持。使用 sparc64-smp 内核。" #. Tag: para #: hardware.xml:1717 @@ -3116,13 +3089,13 @@ msgstr "" msgid "" "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are " "not supported due to lack of support in the Linux kernel." -msgstr "" +msgstr "注意，使用富士通 SPARC64 CPU 的 PRIMEPOWER 家族服务器因为缺乏 Linux 内核的支持而得不到支持。" #. Tag: title #: hardware.xml:1726 -#, fuzzy, no-c-format +#, no-c-format msgid "Graphics Card Support" -msgstr "图形卡" +msgstr "图形卡支持" #. Tag: para #: hardware.xml:1727 @@ -3154,33 +3127,25 @@ msgstr "" #. Tag: para #: hardware.xml:1744 -#, fuzzy, no-c-format +#, no-c-format msgid "" "The X.Org X Window System is only supported on the SGI Indy and the O2. The " "Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI " "slots and support VGA emulation or Linux framebuffer on a selected range of " "graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility " "listing</ulink> for Broadcom evaluation boards is available." -msgstr "" -"X.Org 的 X11 窗口系统仅支持 SGI Indy 和 O2。Broadcom BCM91250A 和 BCM91480B " -"开发板具有标准的 3.3v PCI 插槽，并且可选配的显示卡支持 VGA 仿真或者 Linux " -"framebuffer。这里有一份 Broadcom 开发板的 <ulink url=\"&url-bcm91250a-" -"hardware;\">兼容列表</ulink>。" +msgstr "X.Org 的 X 窗口系统仅支持 SGI Indy 和 O2。Broadcom BCM91250A 和 BCM91480B 开发板具有标准的 3.3v PCI 插槽，并且可选配的显示卡支持 VGA 仿真或者 Linux framebuffer。这里有一份 Broadcom 开发板的 <ulink url=\"&url-bcm91250a-hardware;\">兼容列表</ulink>。" #. Tag: para #: hardware.xml:1753 -#, fuzzy, no-c-format +#, no-c-format msgid "" "The X.Org X Window System is supported on some DECstation models. The " "Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI " "slots and support VGA emulation or Linux framebuffer on a selected range of " "graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility " "listing</ulink> for Broadcom evaluation boards is available." -msgstr "" -"在某些 DEC 工作站机型上 X.Org 的 X11 窗口系统获得支持。Broadcom BCM91250A 和 " -"BCM91480B 开发板具有标准的 3.3v PCI 插槽，并且可选配的显示卡支持 VGA 仿真或" -"者 Linux framebuffer。有一份 Broadcom 开发板的 <ulink url=\"&url-bcm91250a-" -"hardware;\">兼容列表</ulink>。" +msgstr "在某些 DEC 工作站机型上 X.Org 的 X 窗口系统获得支持。Broadcom BCM91250A 和 BCM91480B 开发板具有标准的 3.3v PCI 插槽，并且可选配的显示卡支持 VGA 仿真或者 Linux framebuffer。有一份 Broadcom 开发板的 <ulink url=\"&url-bcm91250a-hardware;\">兼容列表</ulink>。" #. Tag: para #: hardware.xml:1761 @@ -3193,7 +3158,7 @@ msgid "" "(glint driver). To use an Elite3D card with X.org you additionally need to " "install the <classname>afbinit</classname> package, and read the " "documentation included with it on how to activate the card." -msgstr "" +msgstr "多数基于 Sparc 机器的图形选项都能支持。X.org 图形驱动程序可用于 sunbw2、suncg14、suncg3、suncg6、sunleo 和 suntcx framebuffers、Creator3D 和 Elite3D 卡(sunffb 驱动程序), PGX24/PGX64 基于 ATI 的视频卡 (ati 驱动程序)，和基于 PermediaII 的卡 (glint 驱动程序)。要在 X.org 中使用 Elite3D 卡，您需要额外安装 <classname>afbinit</classname> 软件包，并且阅读其中的文档了解如何激活该卡。" #. Tag: para #: hardware.xml:1771 @@ -3210,7 +3175,7 @@ msgid "" "used as an alternative. On some systems use of serial console can be " "activated automatically by disconnecting the keyboard before booting the " "system." -msgstr "" +msgstr "对 Sparc 机器来说，默认配置中有两块图形卡并非不常见。这种情况下，Linux 内核可能不将输出指向固件初始化的那块卡。缺少输出的图形控制端会由于这种错误而挂起(一般在控制台上最后显示的信息是 'Booting Linux...')。一种解决方法是物理地取下一块视频卡；另外一种方法是用内核引导参数禁止其中一块。同样，如果图形输出并不是必须或想要的，可以通过串口控制台替代。在某些系统上，引导系统前断开键盘连接将自动激活串口控制台。" #. Tag: title #: hardware.xml:1788 @@ -3239,18 +3204,14 @@ msgstr "多处理器" #. Tag: para #: hardware.xml:1801 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Multiprocessor support — also called <quote>symmetric multiprocessing</" "quote> or SMP — is available for this architecture. The standard " "Debian &release; kernel image was compiled with SMP support. This should not " "prevent installation, since the SMP kernel should boot on non-SMP systems; " "the kernel will simply cause a bit more overhead." -msgstr "" -"多处理器支持 — 又称<quote>symmetric multi-processing</quote>或 SMP " -"— 在本体系架构下可以使用。标准的 Debian &release; 内核在编译时已经加入" -"了 SMP 功能。因为 SMP 的内核也能在非 SMP 的系统下启动，只不过多些系统开销，所" -"以这并不会影响安装。" +msgstr "多处理器支持 — 又称 <quote>symmetric multiprocessing</quote> 或 SMP — 在本体系架构下可以使用。标准的 Debian &release; 内核映像在编译时已经加入了 SMP 功能。这并不会影响安装，因为 SMP 的内核也能在非 SMP 的系统下启动，只不过多些系统开销。" #. Tag: para #: hardware.xml:1809 @@ -3270,7 +3231,7 @@ msgstr "" #. Tag: para #: hardware.xml:1824 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Multiprocessor support — also called <quote>symmetric multiprocessing</" "quote> or SMP — is available for this architecture. The standard " @@ -3278,11 +3239,7 @@ msgid "" "firstterm> support. This means that the kernel will detect the number of " "processors (or processor cores) and will automatically deactivate SMP on " "uniprocessor systems." -msgstr "" -"多处理器支持 — 又称 <quote>symmetric multi-processing</quote> 或 SMP " -"— 在本体系架构下可以使用。标准的 Debian &release; 内核在编译时已经加入" -"了 <firstterm>SMP-alternatives</firstterm> 支持。也就是内核可以侦测处理器的数" -"量(或者处理器核心)，并在单内核系统上自动关闭 SMP 的功能。" +msgstr "多处理器支持 — 又称 <quote>symmetric multiprocessing</quote> 或 SMP — 在本体系架构下可以使用。标准的 Debian &release; 内核映像在编译时已经加入了 <firstterm>SMP-alternatives</firstterm> 支持。也就是内核可以侦测处理器的数量(或者处理器核心数)，并在单内核系统上自动关闭 SMP 的功能。" #. Tag: para #: hardware.xml:1833 @@ -3294,18 +3251,14 @@ msgstr "&arch-title; 的 486 Debian 内核映像软件包没有支持 SMP 。" #. Tag: para #: hardware.xml:1843 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Multiprocessor support — also called <quote>symmetric multiprocessing</" "quote> or SMP — is available for this architecture. However, the " "standard Debian &release; kernel image does not support SMP. This should not " "prevent installation, since the standard, non-SMP kernel should boot on SMP " "systems; the kernel will simply use the first CPU." -msgstr "" -"多处理器支持 — 又称<quote>symmetric multi-processing</quote>或 SMP " -"— 在本体系架构下可以使用。但是，标准的 Debian &release; 内核并不支持 " -"SMP。这不会影响安装，因为非 SMP 的内核也能在 SMP 的系统下启动，只不过内核只使" -"用第一个 CPU。" +msgstr "多处理器支持 — 又称 <quote>symmetric multiprocessing</quote> 或 SMP — 在本体系架构下可以使用。但是，标准的 Debian &release; 内核映像并不支持 SMP。这不会影响安装，因为非 SMP 的内核也能在 SMP 的系统下启动，只不过内核只使用第一个 CPU。" #. Tag: para #: hardware.xml:1852 @@ -3325,7 +3278,7 @@ msgstr "" #. Tag: para #: hardware.xml:1866 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Multiprocessor support — also called <quote>symmetric multiprocessing</" "quote> or SMP — is available for this architecture, and is supported " @@ -3333,11 +3286,7 @@ msgid "" "SMP-capable kernel may or may not be installed by default. This should not " "prevent installation, since the standard, non-SMP kernel should boot on SMP " "systems; the kernel will simply use the first CPU." -msgstr "" -"多处理器支持 — 又称<quote>symmetric multi-processing</quote>或 SMP " -"— 在本体系架构下可以使用，并且有一个预编译的 Debian 内核映象已经开启这" -"项功能。支持 SMP 的内核默认是否被安装，取决于您的安装介质。这并不会影响安装，" -"因为非 SMP 的内核也能在 SMP 的系统下启动，只不过内核只使用第一个 CPU。" +msgstr "多处理器支持 — 又称 <quote>symmetric multiprocessing</quote> 或 SMP — 在本体系架构下可以使用，并且有一个预编译的 Debian 内核映象已经开启这项功能。支持 SMP 的内核默认是否被安装，取决于您的安装介质。这并不会影响安装，因为非 SMP 的内核也能在 SMP 的系统下启动，只不过内核只使用第一个 CPU。" #. Tag: para #: hardware.xml:1876 @@ -3346,22 +3295,18 @@ msgid "" "In order to take advantage of multiple processors, you should check to see " "if a kernel package that supports SMP is installed, and if not, choose an " "appropriate kernel package." -msgstr "" +msgstr "为了利用多处理器，您应该确认支持 SMP 的内核软件包是否被安装，如果没有，请选择一个合适的内核软件包。" #. Tag: para #: hardware.xml:1882 -#, fuzzy, no-c-format +#, no-c-format msgid "" "You can also build your own customized kernel to support SMP. You can find a " "discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this " "time (kernel version &kernelversion;) the way you enable SMP is to select " "<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</" "quote> section of the kernel config." -msgstr "" -"为了使用多 CPU 的优势，您必须替换标准的 Debian 内核。您可以在<xref linkend=" -"\"kernel-baking\"/> 找到相关的讨论。当前(内核版本 &kernelversion;)启用 SMP 的" -"方法是在内核配置的 <quote>&smp-config-section;</quote> 中选中 <quote>&smp-" -"config-option;</quote>。" +msgstr "您可以自己定制内核来支持 SMP。可以在 <xref linkend=\"kernel-baking\"/> 找到相关的讨论。当前(内核版本 &kernelversion;)启用 SMP 的方法是在内核配置的 <quote>&smp-config-section;</quote> 中选中 <quote>&smp-config-option;</quote>。" #. Tag: title #: hardware.xml:1899 @@ -3653,18 +3598,16 @@ msgid "" "types of network connections (including PPPoE, but not ISDN or PPP), via " "either HTTP or FTP. After the installation is completed, you can also " "configure your system to use ISDN and PPP." -msgstr "" +msgstr "安装过程中可以使用网络来获取安装所需要的文件。是否使用网络取决于您选择的安装方法和安装过程中回答的特定问题。安装系统支持大多数类型的网络连接(包括 PPPoE，但不含 ISDN 或 PPP)，使用 HTTP 或 FTP。安装完成之后，您还可以配置您的系统使用 ISDN 和 PPP。" #. Tag: para #: hardware.xml:2075 -#, fuzzy, no-c-format +#, no-c-format msgid "" "You can also <emphasis>boot</emphasis> the installation system over the " "network. <phrase arch=\"mips\">This is the preferred installation technique " "for &arch-title;.</phrase>" -msgstr "" -"您还可以从网络 <emphasis>启动(boot)</emphasis> 系统。<phrase arch=\"mips\">这" -"是在 Mips 下推荐的安装技术</phrase>" +msgstr "您还可以从网络 <emphasis>启动(boot)</emphasis> 系统。<phrase arch=\"mips\">这是在 &arch-title; 下推荐的安装技术。</phrase>" #. Tag: para #: hardware.xml:2081 @@ -3684,17 +3627,14 @@ msgstr "Un*x 或 GNU 系统" #. Tag: para #: hardware.xml:2091 -#, fuzzy, no-c-format +#, no-c-format msgid "" "If you are running another Unix-like system, you could use it to install " "&debian; without using the &d-i; described in the rest of this manual. This " "kind of install may be useful for users with otherwise unsupported hardware " "or on hosts which can't afford downtime. If you are interested in this " "technique, skip to the <xref linkend=\"linux-upgrade\"/>." -msgstr "" -"如果您正在运行其它的类 Unix 系统，也可以用它来安装 &debian; 而无须本手册 剩余" -"部分讲述的 &d-i; 使用方法。这类安装方法可能对那些因为硬件不支持或机器停产的用" -"户有用。如果您对此技术感兴趣，请直接跳到 <xref linkend=\"linux-upgrade\"/>。" +msgstr "如果您正在运行其它的类 Unix 系统，也可以用它来安装 &debian; 而无须本手册剩余部分讲述的 &d-i; 使用方法。这类安装方法可能对那些因为硬件不支持或机器停产的用户有用。如果您对此技术感兴趣，请直接跳到 <xref linkend=\"linux-upgrade\"/>。" #. Tag: title #: hardware.xml:2103 @@ -3861,13 +3801,11 @@ msgstr "" #. Tag: para #: hardware.xml:2225 -#, fuzzy, no-c-format +#, no-c-format msgid "" "USB hardware generally works fine, only some USB keyboards may require " "additional configuration (see <xref linkend=\"hardware-issues\"/>)." -msgstr "" -"USB 硬件通常工作得很好，只有一些 USB 键盘需要额外的配置(请参考 <xref linkend=" -"\"usb-keyboard-config\"/>)。" +msgstr "USB 硬件通常工作得很好，只有一些 USB 键盘需要额外的配置(参阅 <xref linkend=\"hardware-issues\"/>)。" #. Tag: para #: hardware.xml:2231 @@ -4049,7 +3987,7 @@ msgstr "" #. Tag: para #: hardware.xml:2338 -#, fuzzy, no-c-format +#, no-c-format msgid "" "You should avoid Windows-specific hardware for two reasons. The first is " "that the manufacturers do not generally make the resources available to " @@ -4067,16 +4005,7 @@ msgid "" "any multi-processing operating system, even Windows 2000 or XP, suffers from " "degraded performance when peripheral manufacturers skimp on the embedded " "processing power of their hardware." -msgstr "" -"有两个原因让您应当避免使用 Windows 规格的硬件。首先，这些制造商一般不提供相应" -"资料用于编写 Linux 驱动程序。通常，这些设备的软硬件接口是专有的，即使相关资" -"料 存在，但不签署封闭的契约也无法得到它们。这就排除了被自由软件使用的可能，因" -"为自由软件的开发者不会将它们的软件源码封闭起来。其次，这些设备是没有内嵌处理" -"器的，操作系统必须承担本该由这些处理器完成的工作，并且经常是在 <emphasis>实时" -"</emphasis> 优先级下，因此 CPU 在驱动这些设备时就无法运行您的程序。因为典型" -"的 Windows 用户并不像 Linux 用户那样对多任务有强烈要求，这些制造商希望 " -"Windows 用户不会注意到 CPU 为他们硬件的开销。但是，任何多任务操作系统，甚至" -"是 Windows 2000 或 XP，都要忍受这些制造商克扣内嵌处理器造成的性能下降。" +msgstr "有两个原因让您应当避免使用 Windows 规格的硬件。首先，这些制造商一般不提供相应资料用于编写 Linux 驱动程序。通常，这些设备的软硬件接口是专有的，即使相关资料存在，但不签署封闭的契约也无法得到它们。这就排除了被自由软件使用的可能，因为自由软件的开发者不会将它们的软件源码封闭起来。其次，这些设备是没有内嵌处理器的，操作系统必须承担本该由这些处理器完成的工作，并且经常是在<emphasis>实时</emphasis>优先级下，因此 CPU 在驱动这些设备时就无法运行您的程序。因为典型的 Windows 用户并不像 Linux 用户那样对多任务有强烈要求，这些制造商希望 Windows 用户不会注意到 CPU 为他们硬件的开销。但是，任何多任务操作系统，甚至是 Windows 2000 或 XP，都要忍受这些制造商克扣内嵌处理器造成的性能下降。" #. Tag: para #: hardware.xml:2359 @@ -4105,7 +4034,7 @@ msgid "" "You must have at least &minimum-memory; of memory and &minimum-fs-size; of " "hard disk space. Note that these are really bare-minimum numbers. For more " "realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>." -msgstr "" +msgstr "您必须至少有 &minimum-memory; 的内存和 &minimum-fs-size; 的硬盘空间。注意这是最小的数字，要了解实际的情况，参阅 <xref linkend=\"minimum-hardware-reqts\"/>。" #. Tag: para #: hardware.xml:2384 @@ -4162,7 +4091,7 @@ msgstr "网络连接硬件" #. Tag: para #: hardware.xml:2423 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Almost any network interface card (NIC) supported by the Linux kernel should " "also be supported by the installation system; modular drivers should " @@ -4170,10 +4099,7 @@ msgid "" "PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards " "are supported as well.</phrase> <phrase arch=\"m68k\">Again, see <ulink url=" "\"&url-m68k-faq;\"></ulink> for complete details.</phrase>" -msgstr "" -"任何受 Linux 内核支持的网络接口卡(NIC)也全都被引导盘所支持。您可能需要将网络" -"驱动作为模块挂载。同样的，请参考 <ulink url=\"&url-m68k-faq;\"></ulink> 以了" -"解详细信息。" +msgstr "几乎所有被 Linux 内核支持的网络接口卡(NIC)也全都被安装系统所支持；驱动模块通常会自动加载。<phrase arch=\"x86\">这包含大多数 PCI 和 PCMCIA 卡。</phrase> <phrase arch=\"i386\">许多旧的 ISA 卡也能支持。</phrase> <phrase arch=\"m68k\">再次，参阅 <ulink url=\"&url-m68k-faq;\"></ulink> 获得完整的信息。</phrase>" #. Tag: para #: hardware.xml:2435 @@ -4181,7 +4107,7 @@ msgstr "" msgid "" "This includes a lot of generic PCI cards (for systems that have PCI) and the " "following NICs from Sun:" -msgstr "" +msgstr "这包括一些通用 PCI 卡(对于支持 PCI 的系统)和来自 Sun 的网卡：" #. Tag: para #: hardware.xml:2441 @@ -4219,15 +4145,13 @@ msgstr "MyriCOM Gigabit Ethernet" msgid "" "Due to kernel limitations only the onboard network interfaces on DECstations " "are supported, TurboChannel option network cards currently do not work." -msgstr "" -"因为内核的限制，DECstation 上只有板载网络接口获得支持，TurboChannel 网卡现在" -"还 不能工作。" +msgstr "因为内核的限制，DECstation 上只有板载网络接口获得支持，TurboChannel 网卡现在还不能工作。" #. Tag: para #: hardware.xml:2474 #, no-c-format msgid "The list of supported network devices is:" -msgstr "" +msgstr "支持的网络设备有：" #. Tag: para #: hardware.xml:2479 @@ -4258,24 +4182,22 @@ msgid "" "Unofficial images for Linksys NSLU2 with this proprietary microcode can be " "obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</" "ulink>." -msgstr "" +msgstr "在 &arch-title; 上，多数内建的以太网设备都支持，并提供额外的 PCI 和 USB 设备模块。主要的例外是 IXP4xx 平台(典型的设备是 Linksys NSLU2)，它需要专用的 microcode 来操作内建的以太网设备。包含该专有 microcode 的 Linksys NSLU2 非正式映像可以从 <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink> 地址获得。" #. Tag: para #: hardware.xml:2508 -#, fuzzy, no-c-format +#, no-c-format msgid "" "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not " "supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;. " "Using ISDN during the installation is not supported." -msgstr "" -"对于 ISDN，用于(老式)德国 1TR6 的 D-channel 协议不被支持，Spellcaster BRI " -"ISDN 板也不被 &d-i; 支持。" +msgstr "对于 ISDN，用于(老式)德国 1TR6 的 D-channel 协议不被支持，Spellcaster BRI ISDN 板也不被 &d-i; 支持。所以，安装过程中使用 ISDN 不被支持。" #. Tag: title #: hardware.xml:2517 #, no-c-format msgid "Drivers Requiring Firmware" -msgstr "" +msgstr "需要固件的驱动程序" #. Tag: para #: hardware.xml:2518 @@ -4284,7 +4206,7 @@ msgid "" "The installation system currently does not support retrieving firmware. This " "means that any network cards that use a driver that requires firmware to be " "loaded, is not supported by default." -msgstr "" +msgstr "安装系统当前不支持获取固件。也就是说，默认不支持那些需要驱动程序加载固件的网卡。" #. Tag: para #: hardware.xml:2524 @@ -4298,7 +4220,7 @@ msgid "" "your network manually. Note that the firmware may be packaged separately " "from the driver and may not be available in the <quote>main</quote> section " "of the &debian; archive." -msgstr "" +msgstr "如果您在安装时没有其他的网卡，使用完整的 CD-ROM 或 DVD 映像也可以安装 &debian;。选择不配置网络并且安装时只使用 CD/DVD 上有的软件包。完成安装之后，您再安装驱动程序和固件(重启之后)并且手动配置网络。注意，固件可能与驱动放在不同的软件包，并可能不在 &debian; archive 的 <quote>main</quote> 部分之中。" #. Tag: para #: hardware.xml:2535 @@ -4309,13 +4231,13 @@ msgid "" "to <filename>/usr/lib/hotplug/firmware</filename>. Don't forget to also copy " "the firmware to that location for the installed system before the reboot at " "the end of the installation." -msgstr "" +msgstr "如果驱动程序<emphasis>自己</emphasis>支持，您在安装过程中通过将固件复制到 <filename>/usr/lib/hotplug/firmware</filename> 也许可以使用网卡。完成安装之后别忘了将该固件复制到安装好的系统。" #. Tag: title #: hardware.xml:2547 #, no-c-format msgid "Wireless Network Cards" -msgstr "" +msgstr "无线网卡" #. Tag: para #: hardware.xml:2548 @@ -4325,7 +4247,7 @@ msgid "" "of wireless adapters require drivers that are either non-free or have not " "been accepted into the official Linux kernel. These NICs can generally be " "made to work under &debian;, but are not supported during the installation." -msgstr "" +msgstr "无线网卡通常也能支持得很好，但会附加限制性条款。很多无线网卡要求驱动程序是非自由的，或不能包含在正式的 Linux 内核之中。这些网卡一般可以在 &debian; 下工作，但不被安装系统支持。" #. Tag: para #: hardware.xml:2555 @@ -4334,7 +4256,7 @@ msgid "" "If there is no other NIC you can use during the installation, it is still " "possible to install &debian; using a full CD-ROM or DVD image. Use the same " "procedure as described above for NICs that require firmware." -msgstr "" +msgstr "如果安装时您没有其他的网卡可用，可以使用完整的 CD-ROM 或 DVD 映像来安装 &debian;。与要求固件的网卡步骤相同。" #. Tag: para #: hardware.xml:2561 @@ -4346,13 +4268,13 @@ msgid "" "manual. <phrase arch=\"x86\">If no Linux driver is available, your last " "resort is to use the <classname>ndiswrapper</classname> package, which " "allows you to use a Windows driver.</phrase>" -msgstr "" +msgstr "有些情况下，您需要的驱动程序不包含在 Debian 软件包里面。必须在互联网上寻找它们的源码，并自己动手编译驱动程序。该如何做已经超出了本手册的范围。<phrase arch=\"x86\">如果没有 Linux 驱动程序，您最后可以用 <classname>ndiswrapper</classname> 软件包，它让您使用 Windows 的驱动程序。" #. Tag: title #: hardware.xml:2575 #, no-c-format msgid "Known Issues for &arch-title;" -msgstr "" +msgstr "&arch-title; 的一些已知问题" #. Tag: para #: hardware.xml:2576 @@ -4360,13 +4282,13 @@ msgstr "" msgid "" "There are a couple of issues with specific network cards that are worth " "mentioning here." -msgstr "" +msgstr "有些特定的网卡事项需要在此提及。" #. Tag: title #: hardware.xml:2583 #, no-c-format msgid "Conflict between tulip and dfme drivers" -msgstr "" +msgstr "tulip 和 dfme 驱动程序之间的冲突" #. Tag: para #: hardware.xml:2585 @@ -4378,7 +4300,7 @@ msgid "" "driver. Because they have the same identification, the kernel cannot " "distinguish between them and it is not certain which driver will be loaded. " "If this happens to be the wrong one, the NIC may not work, or work badly." -msgstr "" +msgstr "有些 PCI 网卡具有相同的 PCI 标识，但却由不同的驱动程序支持。有些网卡在 <literal>tulip</literal> 驱动程序下工作，其他的在 <literal>dfme</literal> 驱动程序下工作。因为它们具有相同的标识，内核不能辨别而无法加载合适的驱动程序。如果使用不正确的驱动程序，网卡可能不工作，或者工作不正常。" #. Tag: para #: hardware.xml:2595 @@ -4391,13 +4313,13 @@ msgid "" "<replaceable>module</replaceable></userinput> (or both, if they are both " "loaded). After that you can load the correct module using " "<userinput>modprobe <replaceable>module</replaceable></userinput>." -msgstr "" +msgstr "常见的问题出现在使用 Davicom (DEC-Tulip 兼容的) NIC 网卡的 Netra 系统上。这种情况下，<literal>tulip</literal> 驱动程序可能是正确的。安装过程中的解决方法是切换到一个 shell 并使用 <userinput>modprobe -r <replaceable>module</replaceable></userinput> 卸载不正确的驱动程序模块 (如果都加载了，或者两个都卸载)。之后，您可以通过 <userinput>modprobe <replaceable>module</replaceable></userinput> 加载正确的模块。" #. Tag: title #: hardware.xml:2610 #, no-c-format msgid "Sun B100 blade" -msgstr "" +msgstr "Sun B100 blade" #. Tag: para #: hardware.xml:2612 @@ -4405,301 +4327,4 @@ msgstr "" msgid "" "The <literal>cassini</literal> network driver does not work with Sun B100 " "blade systems." -msgstr "" - -#~ msgid "" -#~ "After the operating system kernel is installed, you can install the rest " -#~ "of your system via any sort of network connection (including PPP after " -#~ "installation of the base system), via FTP or HTTP." -#~ msgstr "" -#~ "在安装了操作系统的内核以后，您可以使用任何一种网络连接方式(包括安装完基本" -#~ "系统以后使用 PPP) 通过 FTP 或 HTTP 完成剩余的系统安装任务。" - -#~ msgid "" -#~ "You must have at least &minimum-memory; of memory and &minimum-fs-size; " -#~ "of hard disk space. For a minimal console-based system (all standard " -#~ "packages), 250MB is required. If you want to install a reasonable amount " -#~ "of software, including the X Window System, and some development programs " -#~ "and libraries, you'll need at least 400MB. For a more or less complete " -#~ "desktop system, you'll need a few gigabytes." -#~ msgstr "" -#~ "您需要至少 &minimum-memory; 的内存和 &minimum-fs-size; 硬盘空间。对最小的" -#~ "基于控制台的系统(包括所有标准软件包)需要250MB。如果您要安装适当的软件，包" -#~ "括 X Window 系统，以及一些开发工具和库，需要至少400MB。对于一个基本的桌面" -#~ "系统，需要几个 G 的空间。" - -#, fuzzy -#~ msgid "" -#~ "The following network interface cards are supported directly by the " -#~ "installation images for Netwinder and CATS machines:" -#~ msgstr "以下网络接口卡在 Netwinder 和 CATS 机器上被安装盘直接支持：" - -#~ msgid "PCI-based NE2000" -#~ msgstr "PCI-based NE2000" - -#~ msgid "DECchip Tulip" -#~ msgstr "DECchip Tulip" - -#, fuzzy -#~ msgid "" -#~ "The following network interface cards are supported directly by the " -#~ "installation images for RiscPCs:" -#~ msgstr "下列网络接口卡在 RiscPC 上被安装盘直接支持：" - -#~ msgid "Ether1" -#~ msgstr "Ether1" - -#~ msgid "Ether3" -#~ msgstr "Ether3" - -#~ msgid "EtherH" -#~ msgstr "EtherH" - -#~ msgid "" -#~ "If your card is mentioned in the lists above, the complete installation " -#~ "can be carried out from the network with no need for CD-ROMs or floppy " -#~ "disks." -#~ msgstr "" -#~ "如果您的网卡出现在上述列表中，整个安装过程可以通过网络进行而不需要光盘或软" -#~ "盘。" - -#~ msgid "" -#~ "Any other network interface card (NIC) supported by the Linux kernel " -#~ "should also be supported by the boot disks. You may need to load your " -#~ "network driver as a module; this means that you will have to install the " -#~ "operating system kernel and modules using some other media." -#~ msgstr "" -#~ "任何受 Linux 内核支持的网络接口卡(NIC)也全都被引导盘所支持。您可能需要将网" -#~ "络驱动作为模块挂载。这意味着您不得不使用其他介质来安装操作系统内核。" - -#~ msgid "sun4cdm" -#~ msgstr "sun4cdm" - -#, fuzzy -#~ msgid "sun4m" -#~ msgstr "sun4cdm" - -#, fuzzy -#~ msgid "sun4v" -#~ msgstr "sun4u" - -#~ msgid "" -#~ "Most PCI and many older ISA network cards are supported. Some network " -#~ "interface cards are not supported by most Debian installation disks, such " -#~ "as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & " -#~ "Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel " -#~ "(MCA) network cards are not supported by the standard installation " -#~ "system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for " -#~ "some (old) instructions. FDDI networks are also not supported by the " -#~ "installation disks, both cards and protocols." -#~ msgstr "" -#~ "大多数的 PCI 和很多旧的 ISA 网卡都被支持。但一些网络接口卡不被多数 Debian " -#~ "安装盘支持，如 AX.25 卡与协议; NI16510 EtherBlaster 卡; Schneider & " -#~ "Koch G16 卡;以及 Zenith Z-Note 内置网卡。微通道(MCA)网卡不被标准的安装系统" -#~ "支持，但可以参考 <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> 可获" -#~ "得一些(旧的)指导。安装系统还不支持 FDDI 网络和协议。" - -#~ msgid "" -#~ "The following network interface cards (NICs) are supported from the " -#~ "bootable kernel directly:" -#~ msgstr "下列网络接口卡(NIC)被引导内核直接支持：" - -#~ msgid "" -#~ "The following network interface cards are supported as modules. They can " -#~ "be enabled once the drivers are installed during the setup. However, due " -#~ "to the magic of OpenPROM, you still should be able to boot from these " -#~ "devices:" -#~ msgstr "" -#~ "下列网卡作为模块支持。在安装过程中驱动被安装后，它们就可以启用了。然而，因" -#~ "为 OpenPROM 的魔力，您可以从这些设备启动：" - -# index.docbook:2337, index.docbook:2343, index.docbook:2349, index.docbook:2355, index.docbook:2361 -#~ msgid "" -#~ "Any network interface card (NIC) supported by the Linux kernel should " -#~ "also be supported by the boot disks. You may need to load your network " -#~ "driver as a module." -#~ msgstr "" -#~ "任何受 Linux 内核支持的网络接口卡(NIC)也全都被引导盘所支持。您可能需要将网" -#~ "络驱动作为模块挂载。" - -#~ msgid "" -#~ "Any network interface card (NIC) supported by the Linux kernel is also be " -#~ "supported by the boot disks. All network drivers are compiled as modules " -#~ "so you need to load one first during the initial network setup. The list " -#~ "of supported network devices is:" -#~ msgstr "" -#~ "任何受 Linux 内核支持的网卡(NIC)也全都被引导盘所支持。所有的网络驱动程序都" -#~ "被编译成了模块，因此您需要在最初的网络设置过程中加载其中一个。支持的网络设" -#~ "备列表为：" - -#~ msgid "" -#~ "Inter-User Communication Vehicle (IUCV) — available for VM guests " -#~ "only" -#~ msgstr "Inter-User Communication Vehicle (IUCV) — 仅对 VM guests 有效" - -#~ msgid "APUS" -#~ msgstr "APUS" - -#~ msgid "<entry>apus</entry>" -#~ msgstr "<entry>apus</entry>" - -#~ msgid "" -#~ "Currently the <emphasis>&architecture;</emphasis> port supports several " -#~ "types of Sparc systems. The most common identifiers for Sparc systems are " -#~ "sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old " -#~ "sun4 hardware. However, the other systems are supported. Sun4d has been " -#~ "tested the least of these, so expect possible problems with regard to the " -#~ "kernel stability. Sun4c and Sun4m, the most common of the older Sparc " -#~ "hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the " -#~ "SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class " -#~ "systems fall under the sun4u identifier, and are supported using the " -#~ "sun4u set of install images. Some systems that fall under these supported " -#~ "identifiers are known to not be supported. Known unsupported systems are " -#~ "the AP1000 multicomputer and the Tadpole Sparcbook 1. See the <ulink url=" -#~ "\"&url-sparc-linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for " -#~ "complete information." -#~ msgstr "" -#~ "当前 <emphasis>&architecture;</emphasis> 移植支持多种 Sparc 系统。最常见" -#~ "的 Sparc 系统标识是 sun4、sun4c、sun4m、sun4d 与 sun4u。当前我们不支持非常" -#~ "老的 sun4 硬件，但支持其它的系统。Sun4d 缺少这方面的测试，可能有潜在的内核" -#~ "稳定性问题。Sun4c 和 Sun4m，最常见的老 Sparc 硬件，包括 SparcStation 1, 1" -#~ "+, IPC, IPX 以及 SparcStation LX, 5, 10 和 20 这些 系统，也是如此。" -#~ "UltraSPARC 类系统也归于 sun4u，使用 sun4u 的安装内核。还有一些属于支持范围" -#~ "内的系统事实上还没有被支持。已知的有 AP1000 multicomputer 和 Tadpole " -#~ "Sparcbook 1。请参考 <ulink url=\"&url-sparc-linux-faq;\">Linux for " -#~ "SPARCProcessors FAQ</ulink> 以了解更多信息。" - -#~ msgid "Memory Configuration" -#~ msgstr "内存配置" - -#~ msgid "" -#~ "Some older Sun workstations, notably the Sun IPX and Sun IPC have memory " -#~ "banks located at fixed locations in physical memory. Thus if the banks " -#~ "are not filled gaps will exist in the physical memory space. The Linux " -#~ "installation requires a contiguous memory block into which to load the " -#~ "kernel and the initial RAMdisk. If this is not available a <quote>Data " -#~ "Access Exception</quote> will result." -#~ msgstr "" -#~ "一些老的 Sun 工作站，如著名的 Sun IPX 和 Sun IPC，内存插槽对应于固定位置的" -#~ "物理内存。因此，未插内存的插槽，将会在物理内存中留下空隙。Linux 安装要求连" -#~ "续的内存块用来加载内核与初始化 RAMdisk。如果不存在则会产生 <quote>Data " -#~ "Access Exception</quote>。" - -#~ msgid "" -#~ "Thus you must configure the memory so that the lowest memory block is " -#~ "contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks " -#~ "are mapped in at 16Mb boundaries. In effect this means that you must have " -#~ "a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In " -#~ "this case 4Mb is <emphasis>not</emphasis> sufficient." -#~ msgstr "" -#~ "所以，您必须配置内存使得低位内存至少有连续的 8Mb。在上面提到的 IPX 与 IPC " -#~ "中，内存插槽映射到 16Mb 边界。实施中这意味着您必须要有足够大的 SIMM 位于 " -#~ "0 插槽，用来储存内核与 RAMdisk。因此，4Mb 就<emphasis>不</emphasis>够用" -#~ "了。" - -#~ msgid "" -#~ "Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four " -#~ "SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS " -#~ "connectors]. You must therefore install the 16Mb SIMM in bank 0; it is " -#~ "then recommended to install the 4Mb SIMM in bank 2." -#~ msgstr "" -#~ "例如： 在 Sun IPX 机器上，您各有一条 16Mb SIMM 和 4Mb SIMM。有四个 SIMM 插" -#~ "槽(0, 1, 2, 3)。[插槽 0 位于 SBUS 连接器最远端]。您必须把 16Mb SIMM 插在插" -#~ "槽 0 上；然后按推荐方法 将 4Mb SIMM 插在插槽 2 上。" - -#~ msgid "Graphics Configuration" -#~ msgstr "图形配置" - -#~ msgid "" -#~ "Especially in the case of older Sun workstations, it is very common for " -#~ "there to be an onboard framebuffer which has been superseded (for example " -#~ "the bwtwo on a sun IPC), and an SBUS card containing a later probably " -#~ "accelerated buffer is then plugged in to an SBUS slot. Under Solaris/" -#~ "SunOS this causes no problems because both cards are initialized." -#~ msgstr "" -#~ "特别对于老的 Sun 工作站，常常会有板载的 framebuffer (比如 sun IPC 上的 " -#~ "bwtwo) 被插在 SBUS 槽上的带加速 buffer 的 SBUS 卡所取代。在 Solaris/SunOS " -#~ "上这不会造成任何问题，因为它们都会被初始化。" - -#~ msgid "" -#~ "However with Linux this can cause a problem, in that the boot PROM " -#~ "monitor may display its output on this additional card; however the linux " -#~ "kernel boot messages may then be directed to the original on board " -#~ "framebuffer, leaving <emphasis>no</emphasis> error messages on the " -#~ "screen, with the machine apparently stuck loading the RAMdisk." -#~ msgstr "" -#~ "然而，在 Linux 下却会造成问题，在启动时 PROM 监视器会显示输出到这个外加卡" -#~ "上； 但 Linux 内核启动信息却指向最初的板载 framebuffer，从而<emphasis>不会" -#~ "</emphasis>在屏幕上留下任何错误信息，表面上机器仍然加载 RAMdisk。" - -#~ msgid "" -#~ "To avoid this problem, connect the monitor (if required) to the video " -#~ "card in the lowest numbered SBUS slot (on motherboard card counts as " -#~ "below external slots). Alternatively it is possible to use a serial " -#~ "console." -#~ msgstr "" -#~ "为了避免这个问题，将监视器(如果需要)连接到最小编号的 SBUS 槽上的视频卡上" -#~ "(主板上计数低于外接槽)。另外一个方法是使用串行控制台。" - -#~ msgid "" -#~ "In order to take advantage of multiple processors, you should check to " -#~ "see if a kernel package that supports SMP is installed, and if not, " -#~ "choose an appropriate kernel package. You can also build your own " -#~ "customized kernel to support SMP. You can find a discussion of how to do " -#~ "this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version " -#~ "&kernelversion;) the way you enable SMP is to select <quote>&smp-config-" -#~ "option;</quote> in the <quote>&smp-config-section;</quote> section of the " -#~ "kernel config." -#~ msgstr "" -#~ "为了使用多 CPU 的优势，您应该检查支持 SMP 的内核包是否安装，如果没有，请选" -#~ "择一个合适的内核包。您也可以编译一个自定义的内核来支持 SMP。相关的讨论可以" -#~ "在 <xref linkend=\"kernel-baking\"/> 找到。当前(内核版本 &kernelversion;)" -#~ "启用 SMP 选项的方法是在内核配置的 <quote>&smp-config-section;</quote> 中选" -#~ "中 <quote>&smp-config-option;</quote>。" - -#~ msgid "Fake or <quote>Virtual</quote> Parity RAM" -#~ msgstr "假的或<quote>虚拟</quote>的奇偶校验内存" - -#~ msgid "" -#~ "If you ask for Parity RAM in a computer store, you'll probably get " -#~ "<emphasis>virtual parity</emphasis> memory modules instead of " -#~ "<emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often " -#~ "(but not always) be distinguished because they only have one more chip " -#~ "than an equivalent non-parity SIMM, and that one extra chip is smaller " -#~ "than all the others. Virtual-parity SIMMs work exactly like non-parity " -#~ "memory. They can't tell you when you have a single-bit RAM error the way " -#~ "true-parity SIMMs do in a motherboard that implements parity. Don't ever " -#~ "pay more for a virtual-parity SIMM than a non-parity one. Do expect to " -#~ "pay a little more for true-parity SIMMs, because you are actually buying " -#~ "one extra bit of memory for every 8 bits." -#~ msgstr "" -#~ "如果您到计算机商店购买奇偶校验内存(Parity RAM)，可能买到的是 <emphasis>虚" -#~ "拟奇偶校验</emphasis>内存，而不是 <emphasis>真奇偶校验</emphasis>的内存。" -#~ "虚拟奇偶校验 SIMM 经常(并不总是)与同等的非奇偶校验 SIMM 区别对待，因为它们" -#~ "多一个芯片，而且那片芯片比其他的都要小。虚拟奇偶校验 SIMM 与非奇偶校验内存" -#~ "工作方式相同。在它们并不能像主板上的真奇偶校验内存那样告诉您有一位 RAM 错" -#~ "误。不要为虚拟奇偶校验多付钱。而应该为真奇偶校验 SIMM 多付，因为您真正为每" -#~ "8位多买了一位。" - -#~ msgid "" -#~ "If you want complete information on &arch-title; RAM issues, and what is " -#~ "the best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware " -#~ "FAQ</ulink>." -#~ msgstr "" -#~ "如果您想得到关于 &arch-title; 内存的完整信息，以及什么才是最值得买的内存，" -#~ "请参考 <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</ulink>。" - -#~ msgid "Most, if not all, Alpha systems require true-parity RAM." -#~ msgstr "大多数的，但不是全部的，Alpha 系统都要求用真奇偶校验内存。" - -#~ msgid "Intel ia64-based" -#~ msgstr "Intel ia64-based" - -#~ msgid "Linksys NSLU2" -#~ msgstr "Linksys NSLU2" - -#~ msgid "nslu2" -#~ msgstr "nslu2" - -#~ msgid "NSLU2" -#~ msgstr "NSLU2" +msgstr "<literal>cassini</literal> 网络驱动程序不能工作在 Sun B100 刀片系统上。" diff --git a/po/zh_CN/install-methods.po b/po/zh_CN/install-methods.po index 26f68499c..16d5f4582 100644 --- a/po/zh_CN/install-methods.po +++ b/po/zh_CN/install-methods.po @@ -4,7 +4,7 @@ msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2007-01-07 13:24+0000\n" -"PO-Revision-Date: 2006-09-04 10:13+0800\n" +"PO-Revision-Date: 2007-01-09 11:16+0800\n" "Last-Translator: Ji YongGang<jungle@soforge.com>\n" "Language-Team: debian-chinese-gb <debian-chinese-gb@lists.debian.org>\n" "MIME-Version: 1.0\n" @@ -981,7 +981,7 @@ msgstr "" msgid "" "The <filename>syslinux.cfg</filename> configuration file should contain the " "following two lines:" -msgstr "" +msgstr "<filename>syslinux.cfg</filename> 配置文件应包含以下两行：" #. Tag: screen #: install-methods.xml:741 @@ -990,6 +990,8 @@ msgid "" "default vmlinuz\n" "append initrd=initrd.gz" msgstr "" +"default vmlinuz\n" +"append initrd=initrd.gz" #. Tag: para #: install-methods.xml:752 @@ -1494,19 +1496,16 @@ msgstr "" #. Tag: para #: install-methods.xml:1076 -#, fuzzy, no-c-format +#, no-c-format msgid "" "You need to setup a TFTP server, and for many machines a DHCP server<phrase " "condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=" "\"supports-bootp\">, or BOOTP server</phrase>." -msgstr "" -"您需要设置一台 TFTP 服务器，并且对于很多机器来说，还需要一台 BOOTP 服务器 " -"<phrase condition=\"supports-rarp\">，或 RARP 服务器</phrase> <phrase " -"condition=\"supports-dhcp\">，又或 DHCP 服务器</phrase>。" +msgstr "您需要设置一台 TFTP 服务器，并且对于很多机器来说，还需要一台 DHCP 服务器 <phrase condition=\"supports-rarp\">，或 RARP 服务器</phrase> <phrase condition=\"supports-bootp\">，又或 BOOTP 服务器</phrase>。" #. Tag: para #: install-methods.xml:1083 -#, fuzzy, no-c-format +#, no-c-format msgid "" "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol " "(RARP) is one way to tell your client what IP address to use for itself. " @@ -1517,15 +1516,7 @@ msgid "" "address can be manually configured in boot ROM.</phrase> The DHCP (Dynamic " "Host Configuration Protocol) is a more flexible, backwards-compatible " "extension of BOOTP. Some systems can only be configured via DHCP." -msgstr "" -"<phrase condition=\"supports-rarp\">反向地址解析协议( The Reverse Address " -"Resolution Protocol (RARP)) 是一种告诉您的客户它自己 IP 地址的方法。另外一种" -"方法是采用 BOOTP 协议。</phrase> <phrase condition=\"supports-bootp\">BOOTP " -"是一种 IP 协议，用来告诉一台计算机它自己 IP 地址以及从网络何处获得启动映像。" -"</phrase> <phrase arch=\"m68k\">在 VMEbus 系统上面的另外一种选择是：IP 地址可" -"以能够在引导 ROM 中手工配置。</phrase> <phrase condition=\"supports-dhcp" -"\">DHCP (动态主机配置协议 Dynamic Host Configuration Protocol) 是一个更灵活，" -"向后兼容的 BOOTP 拓展。有一些系统只能通过 DHCP 来配置。</phrase>" +msgstr "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) 是一种告诉您的客户机它自己 IP 地址的方法。另外一种方法是采用 BOOTP 协议。</phrase> <phrase condition=\"supports-bootp\">BOOTP 是一种 IP 协议，用来告诉一台计算机它自己 IP 地址以及从网络何处获得启动映像。</phrase> <phrase arch=\"m68k\">在 VMEbus 系统上面的另外一种选择是：IP 地址可以能够在引导 ROM 中手工配置。</phrase> DHCP (Dynamic Host Configuration Protocol) 是一个更灵活，向后兼容的 BOOTP 扩展。有些系统只能通过 DHCP 来配置。" #. Tag: para #: install-methods.xml:1100 @@ -1646,24 +1637,20 @@ msgstr "" #. Tag: title #: install-methods.xml:1189 -#, fuzzy, no-c-format +#, no-c-format msgid "Setting up a BOOTP server" -msgstr "设置 BOOTP 服务器" +msgstr "架设 BOOTP 服务器" #. Tag: para #: install-methods.xml:1190 -#, fuzzy, no-c-format +#, no-c-format msgid "" "There are two BOOTP servers available for GNU/Linux. The first is CMU " "<command>bootpd</command>. The other is actually a DHCP server: ISC " "<command>dhcpd</command>. In &debian; these are contained in the " "<classname>bootp</classname> and <classname>dhcp3-server</classname> " "packages respectively." -msgstr "" -"在 GNU/Linux 下面可以使用两种 BOOTP 服务器。首先是 CMU <command>bootpd</" -"command>，另外一种实际上是 DHCP 服务器：ISC <command>dhcpd</command>。" -"&debian; 下它们被包含在 <classname>bootp</classname> 和 <classname>dhcp</" -"classname> 软件包中。" +msgstr "在 GNU/Linux 下面可以使用两种 BOOTP 服务器。首先是 CMU <command>bootpd</command>，另外一种实际上是 DHCP 服务器：ISC <command>dhcpd</command>。&debian; 中它们分别被包含在 <classname>bootp</classname> 和 <classname>dhcp3-server</classname> 软件包。" #. Tag: para #: install-methods.xml:1198 @@ -1729,7 +1716,7 @@ msgstr "" #. Tag: para #: install-methods.xml:1231 -#, fuzzy, no-c-format +#, no-c-format msgid "" "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really " "easy, because it treats BOOTP clients as a moderately special case of DHCP " @@ -1739,13 +1726,7 @@ msgid "" "adding the <userinput>allow bootp</userinput> directive to the configuration " "block for the subnet containing the client, and restart <command>dhcpd</" "command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." -msgstr "" -"相反，通过 ISC <command>dhcpd</command> 设置 BOOTP 就非常容易。因为它把 " -"BOOTP 客户程序看成一个特殊的 DHCP 客户端。部分体系结构需要经过复杂的设置才能" -"从 BOOTP 启动客户端。如果您的机器属于这种情况，请阅读<xref linkend=\"dhcpd\"/" -">。否则，您大概只需要将 <userinput>allow bootp</userinput> 指令添加到包含客户" -"机的子网的配置部分，并重新启动 <command>dhcpd</command> 就可以了，重启的命令" -"是：<userinput>/etc/init.d/dhcpd restart</userinput>。" +msgstr "相反，通过 ISC <command>dhcpd</command> 设置 BOOTP 就非常容易。因为它把 BOOTP 客户程序看成一个特殊的 DHCP 客户端。部分体系结构需要经过复杂的设置才能从 BOOTP 启动客户端。如果您的机器属于这种情况，请阅读<xref linkend=\"dhcpd\"/>。否则，您大概只需要将 <userinput>allow bootp</userinput> 指令添加到包含客户机的子网的配置部分，并重新启动 <command>dhcpd</command> 就可以了，重启的命令是：<userinput>/etc/init.d/dhcpd3-server restart</userinput>。" #. Tag: title #: install-methods.xml:1252 @@ -1761,11 +1742,11 @@ msgid "" "the <classname>dhcp3-server</classname> package is recommended. Here is a " "sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</" "filename>):" -msgstr "" +msgstr "一个 DHCP 服务器自由软件是 ISC <command>dhcpd</command>。对于 &debian;，推荐使用 <classname>dhcp3-server</classname> 软件包。这里是它的一个简单的配置示例文件(参阅 <filename>/etc/dhcp3/dhcpd.conf</filename>)：" #. Tag: screen #: install-methods.xml:1260 -#, fuzzy, no-c-format +#, no-c-format msgid "" "option domain-name \"example.com\";\n" "option domain-name-servers ns1.example.com;\n" @@ -1787,9 +1768,6 @@ msgid "" " fixed-address 192.168.1.90;\n" "}" msgstr "" -"ISC <command>dhcpd</command> 是一种自由软件 DHCP 服务器。在 &debian; 里，它被" -"包含在 <classname>dhcp</classname> 软件包中。这里有它的一个配置文件的范例(通" -"常是 <filename>/etc/dhcpd.conf</filename>)： <informalexample><screen>\n" "option domain-name \"example.com\";\n" "option domain-name-servers ns1.example.com;\n" "option subnet-mask 255.255.255.0;\n" @@ -1806,12 +1784,9 @@ msgstr "" " filename \"/tftpboot/tftpboot.img\";\n" " server-name \"servername\";\n" " next-server servername;\n" -" hardware ethernet 01:23:45:67:89:AB; \n" +" hardware ethernet 01:23:45:67:89:AB;\n" " fixed-address 192.168.1.90;\n" -"}\n" -"</screen></informalexample> 注意：新的(并且是推荐的) <classname>dhcp3</" -"classname> 软件包使用 <filename>/etc/dhcp3/dhcpd.conf</filename>作为其配置文" -"件。" +"}" #. Tag: para #: install-methods.xml:1262 @@ -1831,13 +1806,11 @@ msgstr "" #. Tag: para #: install-methods.xml:1272 -#, fuzzy, no-c-format +#, no-c-format msgid "" "After you have edited the <command>dhcpd</command> configuration file, " "restart it with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." -msgstr "" -"在编辑了 <command>dhcpd</command> 配置文件后，您需要使用下面的命令重新启动" -"它：<userinput>/etc/init.d/dhcpd restart</userinput>作为其配置文件。" +msgstr "在编辑了 <command>dhcpd</command> 配置文件后，您需要使用下面的命令重新启动：<userinput>/etc/init.d/dhcpd3-server restart</userinput>。" #. Tag: title #: install-methods.xml:1280 @@ -1847,7 +1820,7 @@ msgstr "在 DHCP 配置中打开 PXE 引导功能" #. Tag: para #: install-methods.xml:1281 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Here is another example for a <filename>dhcp.conf</filename> using the Pre-" "boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" @@ -1882,9 +1855,7 @@ msgid "" "<filename>pxelinux.0</filename> is a boot loader, not a kernel image (see " "<xref linkend=\"tftp-images\"/> below)." msgstr "" -"这里是另外一个采用 TFTP 的 Pre-boot Execution Environment (PXE) 方法的 " -"<filename>dhcp.conf</filename> 配置例子。\n" -"<informalexample><screen>\n" +"这里是另外一个采用 TFTP 的 Pre-boot Execution Environment (PXE) 方法的 <filename>dhcp.conf</filename> 配置例子。<informalexample><screen>\n" "option domain-name \"example.com\";\n" "\n" "default-lease-time 600;\n" @@ -1896,9 +1867,8 @@ msgstr "" "# The next paragraph needs to be modified to fit your case\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" -" option subnet-mask 255.255.255.0;\n" " option broadcast-address 192.168.1.255;\n" -"# the gateway address which can be different \n" +"# the gateway address which can be different\n" "# (access to the internet for instance)\n" " option routers 192.168.1.1;\n" "# indicate the dns you want to use\n" @@ -1906,16 +1876,14 @@ msgstr "" "}\n" "\n" "group {\n" -" next-server 192.168.1.3;\n" -" host tftpclient {\n" +" next-server 192.168.1.3;\n" +" host tftpclient {\n" "# tftp client hardware address\n" " hardware ethernet 00:10:DC:27:6C:15;\n" -" filename \"/tftpboot/pxelinux.0\";\n" +" filename \"pxelinux.0\";\n" " }\n" "}\n" -"</screen></informalexample> 注意对于 PXE 引导来说，客户端文件名 " -"<filename>pxelinux.0</filename> 是一个启动引导器，而非一个内核映象(参见下面的" -"<xref linkend=\"tftp-images\"/> )。" +"</screen></informalexample> 注意对于 PXE 引导来说，客户端文件名 <filename>pxelinux.0</filename> 是一个启动引导器，而非一个内核映象(参见下面的 <xref linkend=\"tftp-images\"/>)。" #. Tag: title #: install-methods.xml:1297 @@ -1951,11 +1919,11 @@ msgid "" "Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default " "uses <filename>/var/lib/tftpboot</filename>. You may have to adjust the " "configuration examples in this section accordingly." -msgstr "" +msgstr "因为历史原因，TFTP 服务器使用 <filename>/tftpboot</filename> 作为映像文件目录。然而，&debian; 软件包遵守 <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> 使用其他的目录。例如，<classname>tftpd-hpa</classname> 默认使用 <filename>/var/lib/tftpboot</filename>。您或许要适当地调整一下配置文件示例。" #. Tag: para #: install-methods.xml:1320 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Look in <filename>/etc/inetd.conf</filename> and remember the directory " "which is used as the argument of <command>in.tftpd</command><footnote> " @@ -1968,15 +1936,7 @@ msgid "" "userinput>; on other machines, find out the process ID for <command>inetd</" "command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></" "userinput>." -msgstr "" -"检查那个文件并且记住被用作 <command>in.tftpd</command> 的参数的目录，您接下来" -"将会需要它。<userinput>-l</userinput> 参数能够让某些版本的 <command>in." -"tftpd</command> 将所有的请求记录到系统日志中。这将在检查错误的时候会很有用。" -"如果您必须修改 <filename>/etc/inetd.conf</filename>，您将必须提醒正在运行的 " -"<command>inetd</command>进程该文件已经被改变。在 Debian 系统中，您应该执行 " -"<userinput>/etc/init.d/inetd reload</userinput>；而在其它系统中，找到 " -"<command>inetd</command> 所对应的进程 ID，并且运行 <userinput>kill -HUP " -"<replaceable>inetd-pid</replaceable></userinput>。" +msgstr "检查 <filename>/etc/inetd.conf</filename> 文件记住被用作 <command>in.tftpd</command> 的参数的目录<footnote> <para> <userinput>-l</userinput> 参数能够让某些版本的 <command>in.tftpd</command> 将所有的请求记录到系统日志中。这将在检查错误的时候会很有用。</para> </footnote>，您接下来将会需要它。如果必须修改 <filename>/etc/inetd.conf</filename>，您必须提醒正在运行的 <command>inetd</command> 进程，该文件已经修改。在 Debian 系统中，应该执行 <userinput>/etc/init.d/inetd reload</userinput>；而在其它系统中，找到 <command>inetd</command> 所对应的进程 ID，并执行 <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>。" #. Tag: para #: install-methods.xml:1338 @@ -2014,19 +1974,14 @@ msgstr "将 TFTP 映像放到适当的位置" #. Tag: para #: install-methods.xml:1361 -#, fuzzy, no-c-format +#, no-c-format msgid "" "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-" "files\"/>, in the <command>tftpd</command> boot image directory. You may " "have to make a link from that file to the file which <command>tftpd</" "command> will use for booting a particular client. Unfortunately, the file " "name is determined by the TFTP client, and there are no strong standards." -msgstr "" -"接下来，将在 <xref linkend=\"where-files\"/>中找到的 TFTP 启动映像放置到" -"<command>tftpd</command>引导映像目录中。一般来说，这个目录将是 <filename>/" -"tftpboot</filename>。您必须将该文件链接到 <command>tftpd</command> 所使用的引" -"导特定客户端的文件名。不幸的是，这个文件名完全决定于 TFTP 客户程序，并且没有" -"一个强制的标准。" +msgstr "接下来，将 <xref linkend=\"where-files\"/> 中找到的 TFTP 启动映像放置到 <command>tftpd</command> 引导映像目录中。您可能需要将该文件链接到 <command>tftpd</command> 所使用的引导特定客户端的文件名。不幸的是，这个文件名完全决定于 TFTP 客户程序，并且没有一个强制的标准。" #. Tag: para #: install-methods.xml:1370 @@ -2047,18 +2002,14 @@ msgstr "" #. Tag: para #: install-methods.xml:1379 -#, fuzzy, no-c-format +#, no-c-format msgid "" "For PXE booting, everything you should need is set up in the " "<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this " "tarball into the <command>tftpd</command> boot image directory. Make sure " "your dhcp server is configured to pass <filename>pxelinux.0</filename> to " "<command>tftpd</command> as the filename to boot." -msgstr "" -"对于用 PXE 引导来说，您所需的只是设置 <filename>netboot/netboot.tar.gz</" -"filename> 压缩包。简单地将此包解压到 <command>tftpd</command> 引导映像目录" -"下。并确保您的 DHCP 服务器的配置将会把 <filename>/pxelinux.0</filename> 以启" -"动所需的文件名传递至<command>tftpd</command>。" +msgstr "对于用 PXE 引导来说，您所需的只是建立 <filename>netboot/netboot.tar.gz</filename> 压缩包。只须将此包解压到 <command>tftpd</command> 引导映像目录下。并确保您的 DHCP 服务器的配置将会把 <filename>/pxelinux.0</filename> 作为启动所需的文件名传递给 <command>tftpd</command>。" #. Tag: para #: install-methods.xml:1387 @@ -2224,7 +2175,7 @@ msgid "" "userinput> from the OpenPROM should load the image. If the image cannot be " "found, try checking the logs on your tftp server to see which image name is " "being requested." -msgstr "" +msgstr "如果都正确完成，从 OpenPROM 使用 <userinput>boot net</userinput> 命令应该加载映像。假如映像找不到，查看 tftp 服务器的日志所需要的映像文件名。" #. Tag: para #: install-methods.xml:1502 @@ -2353,19 +2304,3 @@ msgid "" msgstr "" "在 <xref linkend=\"appendix-preseed\"/> 是有关预置文件的完整文档，并有一些可" "以使用的例子供您修改。" - -#~ msgid "" -#~ "The <filename>syslinux.cfg</filename> configuration file should contain " -#~ "the following two lines: <informalexample><screen>\n" -#~ "default vmlinuz\n" -#~ "append initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw\n" -#~ "</screen></informalexample> Please note that the <userinput>ramdisk_size</" -#~ "userinput> parameter may need to be increased, depending on the image you " -#~ "are booting." -#~ msgstr "" -#~ "<filename>syslinux.cfg</filename> 配置文件应该含有下列两行： " -#~ "<informalexample><screen>\n" -#~ "default vmlinuz\n" -#~ "append initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw\n" -#~ "</screen></informalexample> 请注意，根据所启动的内存映像的大小，在必要的时" -#~ "候，您可能需要增大<userinput>ramdisk_size</userinput> 参数的数值。" |