diff options
Diffstat (limited to 'po')
| -rw-r--r-- | po/zh_CN/bookinfo.po | 26 | ||||
| -rw-r--r-- | po/zh_CN/boot-installer.po | 941 | ||||
| -rw-r--r-- | po/zh_CN/boot-new.po | 86 | ||||
| -rw-r--r-- | po/zh_CN/hardware.po | 808 | ||||
| -rw-r--r-- | po/zh_CN/install-methods.po | 211 | ||||
| -rw-r--r-- | po/zh_CN/partitioning.po | 102 | ||||
| -rw-r--r-- | po/zh_CN/preparing.po | 338 | ||||
| -rw-r--r-- | po/zh_CN/preseed.po | 60 | ||||
| -rw-r--r-- | po/zh_CN/random-bits.po | 4 | ||||
| -rw-r--r-- | po/zh_CN/using-d-i.po | 38 | ||||
| -rw-r--r-- | po/zh_CN/welcome.po | 11 |
11 files changed, 76 insertions, 2549 deletions
diff --git a/po/zh_CN/bookinfo.po b/po/zh_CN/bookinfo.po index dd2c1a8d9..8ed4aab0a 100644 --- a/po/zh_CN/bookinfo.po +++ b/po/zh_CN/bookinfo.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: 2009-11-02 22:05+0000\n" -"PO-Revision-Date: 2007-01-08 09:30+0800\n" +"PO-Revision-Date: 2009-11-21 10:56+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" @@ -98,27 +98,3 @@ msgid "" msgstr "" "本手册属于自由软件，您可以在 GNU 通用公共授权(GPL)下重新发布和(或)修改它。请" "在 <xref linkend=\"appendix-gpl\"/> 阅读该许可证的内容。" - -#~ msgid "" -#~ "Because the &arch-title; port is not a release architecture for " -#~ "&releasename;, there is no official version of this manual for &arch-" -#~ "title; for &releasename;. However, because the port is still active and " -#~ "there is hope that &arch-title; may be included again in future official " -#~ "releases, this development version of the Installation Guide is still " -#~ "available." -#~ msgstr "" -#~ "对于 &releasename;，&arch-title; 的移植不是发布的体系，&releasename; 还没" -#~ "有正式的 &arch-title; 手册。然而，该平台的移植工作还在进行中，将来也许会包" -#~ "含在正式的发布版中，所以安装手册的开发版仍然保留着。" - -#~ msgid "" -#~ "Because &arch-title; is not an official architecture, some of the " -#~ "information, and especially some links, in this manual may be incorrect. " -#~ "For additional information, please check the <ulink url=\"&url-ports;" -#~ "\">webpages</ulink> of the port or contact the <ulink url=\"&url-list-" -#~ "subscribe;\">debian-&arch-listname; mailing list</ulink>." -#~ msgstr "" -#~ "因为 &arch-title; 并非正式的体系，本手册中的信息，特别是一些链接，可能不正" -#~ "确。详细的信息，请检查该移植的 <ulink url=\"&url-ports;\">webpages</" -#~ "ulink>，或者查阅 <ulink url=\"&url-list-subscribe;\">debian-&arch-" -#~ "listname; mailing list</ulink>。" diff --git a/po/zh_CN/boot-installer.po b/po/zh_CN/boot-installer.po index 9a5dcd744..283a1245b 100644 --- a/po/zh_CN/boot-installer.po +++ b/po/zh_CN/boot-installer.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: 2009-11-18 01:11+0000\n" -"PO-Revision-Date: 2009-08-01 14:15+0800\n" +"PO-Revision-Date: 2009-11-21 11:46+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" @@ -1838,7 +1838,7 @@ msgstr "" # index.docbook:1597, index.docbook:2103 #. Tag: para #: boot-installer.xml:1538 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "To boot the installer from hard disk, you will have already completed " #| "downloading and placing the needed files in <xref linkend=\"boot-drive-" @@ -1847,9 +1847,7 @@ msgid "" "To boot the installer from hard disk, you will have already completed " "downloading and placing the needed files as described in <xref linkend=" "\"boot-drive-files\"/>." -msgstr "" -"如果要从硬盘上引导安装程序，您也许已经在 <xref linkend=\"boot-drive-files\"/" -"> 处下载并且在 <xref linkend=\"boot-drive-files\"/> 安置了所需文件。" +msgstr "如果要从硬盘上引导安装程序，您需要参考 <xref linkend=\"boot-drive-files\"/> 下载并且安置所需文件。" #. Tag: title #: boot-installer.xml:1558 @@ -2956,10 +2954,10 @@ msgstr "" #. Tag: term #: boot-installer.xml:2392 -#, fuzzy, no-c-format +#, no-c-format #| msgid "debian-installer/theme (theme)" msgid "base-installer/install-recommends (recommends)" -msgstr "debian-installer/theme (theme)" +msgstr "base-installer/install-recommends (recommends)" #. Tag: para #: boot-installer.xml:2393 @@ -2971,7 +2969,7 @@ msgid "" "the selected software, but they do enhance that software and should, in the " "view of the package maintainers, normally be installed together with that " "software." -msgstr "" +msgstr "在使用包管理系统安装软件包时，将默认安装该软件包推荐的软件包。这些推荐的软件包并不影响要安装软件包的核心功能，但可以增强其功能。从软件包维护人员的角度看，正常情况下应该安装这些软件。" #. Tag: para #: boot-installer.xml:2402 @@ -2981,7 +2979,7 @@ msgid "" "management system will be configured to not automatically install such " "<quote>Recommends</quote>, both during the installation and for the " "installed system." -msgstr "" +msgstr "通过设置 <userinput>false</userinput> 选项，在安装过程和以后的系统中，包管理系统将配置为不自动安装这些<quote>推荐的软件包(Recommends)</quote>。" #. Tag: para #: boot-installer.xml:2409 @@ -2992,7 +2990,7 @@ msgid "" "may have to manually install some of the recommended packages to obtain the " "full functionality you want. This option should therefore only be used by " "very experienced users." -msgstr "" +msgstr "注意，虽然使用该选项可以得到一个瘦小的系统，但将会失去一些通常认为应有的特性。您不得不使用手动方式安装这些推荐软件包以获得完整的功能。因此，该选项应由非常有经验的用户来使用。" #. Tag: term #: boot-installer.xml:2421 @@ -3148,17 +3146,17 @@ msgstr "" #. Tag: term #: boot-installer.xml:2525 -#, fuzzy, no-c-format +#, no-c-format #| msgid "debian-installer/locale (locale)" msgid "debian-installer/language (language)" -msgstr "debian-installer/locale (locale)" +msgstr "debian-installer/language (language)" #. Tag: term #: boot-installer.xml:2526 -#, fuzzy, no-c-format +#, no-c-format #| msgid "debian-installer/theme (theme)" msgid "debian-installer/country (country)" -msgstr "debian-installer/theme (theme)" +msgstr "debian-installer/country (country)" #. Tag: term #: boot-installer.xml:2527 @@ -3172,7 +3170,7 @@ msgstr "debian-installer/locale (locale)" msgid "" "There are two ways to specify the language, country and locale to use for " "the installation and the installed system." -msgstr "" +msgstr "有两种方法可以指定安装过程和安装后系统中所使用的语言(language)、国家(country)和地方(locale)。" #. Tag: para #: boot-installer.xml:2533 @@ -3185,7 +3183,7 @@ msgid "" "set as default locale for the installed system). Limitation is that not all " "possible combinations of language, country and locale can be achieved this " "way." -msgstr "" +msgstr "第一种和最简单的方法为只设置 <literal>locale</literal> 参数。语言和国家将依据该值产生。例如，您可以使用 <userinput>locale=de_CH</userinput> 选择语言为德语，瑞士为国家(安装后的系统中默认的 locale 将设置为 <literal>de_CH.UTF-8</literal> )。该方法有一个缺陷，因为并不是所有的语言、国家和地方可以采用这种方式组合。" #. Tag: para #: boot-installer.xml:2542 @@ -3196,7 +3194,7 @@ msgid "" "literal> can optionally be added to specify a specific default locale for " "the installed system. Example: <userinput>language=en country=DE " "locale=en_GB.UTF-8</userinput>." -msgstr "" +msgstr "第二种更具弹性的方法，是分开指定 <literal>language</literal> 和 <literal>country</literal>。这种方式下 <literal>locale</literal> 可以作为选项来指定安装后系统中默认的 locale 值。例如： <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>。" #. Tag: term #: boot-installer.xml:2554 @@ -4245,912 +4243,3 @@ msgstr "" " and ideas you had during the initial install.>\n" "</screen></informalexample> 在 bug 报告中，请说明问题所在，包括内核挂起时最后" "见到的内核消息。描述进入问题状态所进行的步骤。" - -#~ msgid "" -#~ "Can be used to set both the language and country for the installation. " -#~ "This will only work if the locale is supported in Debian. For example, " -#~ "use <userinput>locale=de_CH</userinput> to select German as language and " -#~ "Switzerland as country." -#~ msgstr "" -#~ "可用来设置安装的语言和国家。它只在该 locale 被 Debian 支持时工作。例如，使" -#~ "用 <userinput>locale=de_CH</userinput> 选择德语作为语言，并且瑞士作为国" -#~ "家。" - -#~ msgid "Alpha Console Firmware" -#~ msgstr "Alpha 控制台固件" - -#~ msgid "" -#~ "Console firmware is stored in a flash ROM and started when an Alpha " -#~ "system is powered up or reset. There are two different console " -#~ "specifications used on Alpha systems, and hence two classes of console " -#~ "firmware available:" -#~ msgstr "" -#~ "控制台固件是保存在一个闪存 ROM 中并且每次在 Alpha 系统加电或者重启的时候启" -#~ "动。在 Alpha 系统上有两种规格的控制台，并且因此有两类控制台固件供使用。" - -#~ msgid "" -#~ "<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem " -#~ "specification, which provides an operating environment for OpenVMS, Tru64 " -#~ "UNIX, and Linux operating systems." -#~ msgstr "" -#~ "<emphasis>SRM console</emphasis> 基于 Alpha 控制台子系统规范。它为 " -#~ "OpenVMS，Tru64 Unix，以及 Linux 操作系统提供了一个操作环境。" - -#~ msgid "" -#~ "<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the " -#~ "Advanced RISC Computing (ARC) specification, which provides an operating " -#~ "environment for Windows NT." -#~ msgstr "" -#~ "<emphasis>ARC, AlphaBIOS 或 ARCSBIOS console</emphasis> 基于 Advanced " -#~ "RISC Computing (ARC) 规范。它为 Windows NT 提供了一个操作环境。" - -#~ msgid "" -#~ "From the user's perspective, the most important difference between SRM " -#~ "and ARC is that the choice of console constrains the possible disk-" -#~ "partitioning scheme for the hard disk which you wish to boot off of." -#~ msgstr "" -#~ "按照用户的角度看，SRM 和 ARC 最重要的区别，是控制台的选择，可能会影响到您" -#~ "需要引导的磁盘分区方法。" - -#~ msgid "" -#~ "ARC requires that you use an MS-DOS partition table (as created by " -#~ "<command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition " -#~ "tables are the <quote>native</quote> partition format when booting from " -#~ "ARC. In fact, since AlphaBIOS contains a disk partitioning utility, you " -#~ "may prefer to partition your disks from the firmware menus before " -#~ "installing Linux." -#~ msgstr "" -#~ "ARC 需要您为引导磁盘使用一个 MS-DOS 分区表(用 <command>cfdisk</command> 创" -#~ "建)。因此从 ARC 引导则 MS-DOS 分区表是作为<quote>原始的</quote>分区格式 " -#~ "ARC。事实上，由于 AlphaBIOS 包含了一个磁盘分区工具，您也许可以在安装 " -#~ "Linux 时，通过固件菜单对磁盘进行分区。" - -#~ msgid "" -#~ "Conversely, SRM is <emphasis>incompatible</emphasis><footnote> <para> " -#~ "Specifically, the bootsector format required by the Console Subsystem " -#~ "Specification conflicts with the placement of the DOS partition table. </" -#~ "para> </footnote> with MS-DOS partition tables. Since Tru64 Unix uses the " -#~ "BSD disklabel format, this is the <quote>native</quote> partition format " -#~ "for SRM installations." -#~ msgstr "" -#~ "保守地说，SRM 是 <emphasis>不兼容</emphasis> MS-DOS 分区表。" -#~ "<footnote><para> 具体来说，控制台子系统规范与需要的引导扇区格式和 DOS 分区" -#~ "表有冲突。</para></footnote>由于 Tru64 Unix 使用的是 BSD 磁盘标记格式，对" -#~ "于SRM 安装来说，这是一个<quote>原始的</quote>分区格式。" - -#~ msgid "" -#~ "GNU/Linux is the only operating system on Alpha that can be booted from " -#~ "both console types, but &debian; &release; only supports booting on SRM-" -#~ "based systems. If you have an Alpha for which no version of SRM is " -#~ "available, if you will be dual-booting the system with Windows NT, or if " -#~ "your boot device requires ARC console support for BIOS initialization, " -#~ "you will not be able to use the &debian; &release; installer. You can " -#~ "still run &debian; &release; on such systems by using other install " -#~ "media; for instance, you can install Debian woody with MILO and upgrade." -#~ msgstr "" -#~ "由于 GNU/Linux 是唯一能够通过两种控制台格式引导的系统，这个问题就取决于您" -#~ "想在机器上面运行什么样的其他操作系统。所有的其他 Unix 型的操作系统 (Tru64 " -#~ "Unix，FreeBSD，OpenBSD，以及 NetBSD) 和 OpenVMS 只能从 SRM 上面引导，而 " -#~ "Windows NT 只能从 ARC 上面引导。" - -#~ msgid "" -#~ "Because <command>MILO</command> is not available for any of the Alpha " -#~ "systems currently in production (as of February 2000), and because it is " -#~ "no longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM " -#~ "firmware on your older Alpha, it is recommended that you use SRM when " -#~ "possible." -#~ msgstr "" -#~ "由于 <command>MILO</command> 在当前生产型 Alpha 系统上并没有实现(从 2000 " -#~ "年二月份开始)。并且也不需要购买一个 OpenVMS 和 Tru64 Unix 授权，来在老 " -#~ "Alpha 上装上 SRM 固件。我们推荐在新的机器上使用 SRM。" - -#~ msgid "" -#~ "The following table summarizes available and supported system type/" -#~ "console combinations (see <xref linkend=\"alpha-cpus\"/> for the system " -#~ "type names). The word <quote>ARC</quote> below denotes any of the ARC-" -#~ "compliant consoles." -#~ msgstr "" -#~ "下面表格总结了可用以及支持的系统类型/控制台组合(系统类型名称参见 <xref " -#~ "linkend=\"alpha-cpus\"/>)。单词 <quote>ARC</quote> 注明任何和 ARC 兼容的控" -#~ "制台。" - -#~ msgid "System Type" -#~ msgstr "系统类型" - -#~ msgid "Console Type Supported" -#~ msgstr "支持的控制台类型" - -#~ msgid "alcor" -#~ msgstr "alcor" - -# index.docbook:110, index.docbook:113, index.docbook:119, index.docbook:125, index.docbook:128, index.docbook:131, index.docbook:134, index.docbook:140, index.docbook:143, index.docbook:146, index.docbook:155, index.docbook:164, index.docbook:179, index.docbook:182, index.docbook:188 -#~ msgid "ARC or SRM" -#~ msgstr "ARC or SRM" - -#~ msgid "avanti" -#~ msgstr "avanti" - -#~ msgid "book1" -#~ msgstr "book1" - -# index.docbook:116, index.docbook:122, index.docbook:137, index.docbook:149, index.docbook:158, index.docbook:161, index.docbook:167, index.docbook:173, index.docbook:176 -#~ msgid "SRM only" -#~ msgstr "SRM only" - -#~ msgid "cabriolet" -#~ msgstr "cabriolet" - -#~ msgid "dp264" -#~ msgstr "dp264" - -#~ msgid "eb164" -#~ msgstr "eb164" - -#~ msgid "eb64p" -#~ msgstr "eb64p" - -#~ msgid "eb66" -#~ msgstr "eb66" - -#~ msgid "eb66p" -#~ msgstr "eb66p" - -#~ msgid "jensen" -#~ msgstr "jensen" - -#~ msgid "lx164" -#~ msgstr "lx164" - -#~ msgid "miata" -#~ msgstr "miata" - -#~ msgid "mikasa" -#~ msgstr "mikasa" - -#~ msgid "mikasa-p" -#~ msgstr "mikasa-p" - -#~ msgid "nautilus" -#~ msgstr "nautilus" - -#~ msgid "ARC (see motherboard manual) or SRM" -#~ msgstr "ARC (see motherboard manual) or SRM" - -#~ msgid "noname" -#~ msgstr "noname" - -#~ msgid "noritake" -#~ msgstr "noritake" - -#~ msgid "noritake-p" -#~ msgstr "noritake-p" - -#~ msgid "pc164" -#~ msgstr "pc164" - -#~ msgid "rawhide" -#~ msgstr "rawhide" - -#~ msgid "ruffian" -#~ msgstr "ruffian" - -# index.docbook:170, index.docbook:185 -#~ msgid "ARC only" -#~ msgstr "ARC only" - -#~ msgid "sable" -#~ msgstr "sable" - -#~ msgid "sable-g" -#~ msgstr "sable-g" - -#~ msgid "sx164" -#~ msgstr "sx164" - -#~ msgid "takara" -#~ msgstr "takara" - -#~ msgid "<entry>xl</entry>" -#~ msgstr "<entry>xl</entry>" - -#~ msgid "<entry>xlt</entry>" -#~ msgstr "<entry>xlt</entry>" - -#~ msgid "" -#~ "Generally, none of these consoles can boot Linux directly, so the " -#~ "assistance of an intermediary bootloader is required. For the SRM " -#~ "console, <command>aboot</command>, a small, platform-independent " -#~ "bootloader, is used. See the (unfortunately outdated) <ulink url=\"&url-" -#~ "srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</" -#~ "command>." -#~ msgstr "" -#~ "一般来说，这些控制台都不能直接引导 Linux ，因此需要一个中间引导装载程序。" -#~ "对于 SRM 控制台，<command>aboot</command>，小型的，平台独立的引导装载器。" -#~ "参见(抱歉的是它也有点过时了)<ulink url=\"&url-srm-howto;\">SRM HOWTO</" -#~ "ulink> 来获得更多有关信息 <command>aboot</command>。" - -#~ msgid "" -#~ "The following paragraphs are from the woody install manual, and are " -#~ "included here for reference; they may be useful to someone at a later " -#~ "date when Debian supports MILO-based installs again." -#~ msgstr "" -#~ "以下章节来自 woody 安装手册，放在这里作为参考；如果以后 Debian 再支持基于 " -#~ "MILO 的安装，它们对某些人或许有用。" - -#~ msgid "" -#~ "Generally, none of these consoles can boot Linux directly, so the " -#~ "assistance of an intermediary bootloader is required. There are two " -#~ "mainstream Linux loaders: <command>MILO</command> and <command>aboot</" -#~ "command>." -#~ msgstr "" -#~ "一般来说，这些控制台都不能直接引导 Linux，因此需要一个中间引导装载程序。这" -#~ "里有两个主要的 Linux 装载程序： <command>MILO</command> 和 " -#~ "<command>aboot</command>。" - -#~ msgid "" -#~ "<command>MILO</command> is itself a console, which replaces ARC or SRM in " -#~ "memory. <command>MILO</command> can be booted from both ARC and SRM and " -#~ "is the only way to bootstrap Linux from the ARC console. <command>MILO</" -#~ "command> is platform-specific (a different <command>MILO</command> is " -#~ "needed for each system type) and exist only for those systems, for which " -#~ "ARC support is shown in the table above. See also the (unfortunately " -#~ "outdated) <ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>." -#~ msgstr "" -#~ "<command>MILO</command> 自己本身是一个用来替换载入内存中的 ARC 和 SRM 的控" -#~ "制台。<command>MILO</command> 能够同时从 ARC 和 SRM 引导并且是唯一一种方法" -#~ "从 ARC 控制台引导 Linux。<command>MILO</command> 取决与具体的平台。(对于每" -#~ "种不同的系统类型需要不同的 <command>MILO</command> 并且只适合这些系统。参" -#~ "见(很遗憾有点过时)<ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>。" - -#~ msgid "" -#~ "<command>aboot</command> is a small, platform-independent bootloader, " -#~ "which runs from SRM only. See the (also unfortunately outdated) <ulink " -#~ "url=\"&url-srm-howto;\">SRM HOWTO</ulink> for more information on " -#~ "<command>aboot</command>." -#~ msgstr "" -#~ "<command>aboot</command> 是一个小型的，平台独立的引导装载器，不过只运行与 " -#~ "SRM 上。参见 (抱歉的是它也有点过时了 ) <ulink url=\"&url-srm-howto;\">SRM " -#~ "HOWTO</ulink>来获得更多有关信息 <command>aboot</command>。" - -#~ msgid "" -#~ "Thus, three scenarios are generally possible, depending on the system's " -#~ "console firmware and whether or not <command>MILO</command> is available: " -#~ "<informalexample><screen>\n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ "</screen></informalexample> Because <command>MILO</command> is not " -#~ "available for any of the Alpha systems currently in production (as of " -#~ "February 2000), and because it is no longer necessary to buy an OpenVMS " -#~ "or Tru64 Unix license to have SRM firmware on your older Alpha, it is " -#~ "recommended that you use SRM and <command>aboot</command> on new " -#~ "installations of GNU/Linux, unless you wish to dual-boot with Windows NT." -#~ msgstr "" -#~ "因此，三种方案都是可行的，取决与系统控制台固件以及是否有相应的 " -#~ "<command>MILO</command> ： <informalexample><screen>\n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ "</screen></informalexample> 由于 <command>MILO</command> 在当前生产型 " -#~ "Alpha 系统上并没有实现(从 2000 年二月份开始)。并且也不需要购买一个 " -#~ "OpenVMS 和 Tru64 Unix 授权，来在老 Alpha 上装上 SRM 固件。除非您想采用 " -#~ "Windows NT 并且进行双引导，我们推荐在新的机器上使用 SRM 和 " -#~ "<command>aboot</command> 安装 Linux。" - -#~ msgid "" -#~ "The majority of AlphaServers and all current server and workstation " -#~ "products contain both SRM and AlphaBIOS in their firmware. For " -#~ "<quote>half-flash</quote> machines such as the various evaluation boards, " -#~ "it is possible to switch from one version to another by reflashing the " -#~ "firmware. Also, once SRM is installed, it is possible to run ARC/" -#~ "AlphaBIOS from a floppy disk (using the <command>arc</command> command). " -#~ "For the reasons mentioned above, we recommend switching to SRM before " -#~ "installing &debian;." -#~ msgstr "" -#~ "大部分 AlphaServers 以及目前所有的服务器以及工作站产品固件中都同时含有 " -#~ "SRM 和 AlphaBIOS。对于具有不同开发板的 <quote>half-flash</quote> 机器来" -#~ "说。可以通过重刷固件 来从一个版本切换到另外一个版本。并且一旦 SRM 安装完" -#~ "毕，从软盘上运行 ARC/AlphaBIOS 也是可能的(使用 <command>arc</command>)。基" -#~ "于上述的理由，我们推荐在安装 &debian; 之前切换至 SRM。" - -#~ msgid "" -#~ "As on other architectures, you should install the newest available " -#~ "revision of the firmware<footnote> <para> Except on Jensen, where Linux " -#~ "is not supported on firmware versions newer than 1.7 — see <ulink " -#~ "url=\"&url-jensen-howto;\"></ulink> for more information. </para> </" -#~ "footnote> before installing &debian;. For Alpha, firmware updates can be " -#~ "obtained from <ulink url=\"&url-alpha-firmware;\">Alpha Firmware Updates</" -#~ "ulink>." -#~ msgstr "" -#~ "和另外的体系结构一样，您也应该在安装 &debian; 之前安装最新版本的固件" -#~ "<footnote><para>不包括 Jensen，1.7 以上版本的固件不支持 Linux — 查" -#~ "看 <ulink url=\"&url-jensen-howto;\"></ulink> 以获得更多的信息。</para></" -#~ "footnote>。对于 Alpha 来说，固件升级可以通过 <ulink url=\"&url-alpha-" -#~ "firmware;\">Alpha Firmware Updates</ulink>取得。" - -#~ msgid "" -#~ "In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> " -#~ "prefix, and will be listed in the output of the <userinput>show dev</" -#~ "userinput> command, like this (edited slightly): " -#~ "<informalexample><screen>\n" -#~ ">>> show dev\n" -#~ "ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" -#~ "ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" -#~ "ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" -#~ "</screen></informalexample> You first need to set the boot protocol: " -#~ "<informalexample><screen>\n" -#~ ">>> set ewa0_protocols bootp\n" -#~ "</screen></informalexample> Then check the medium type is correct: " -#~ "<informalexample><screen>\n" -#~ ">>> set ewa0_mode <replaceable>mode</replaceable>\n" -#~ "</screen></informalexample> You can get a listing of valid modes with " -#~ "<userinput>>>>set ewa0_mode</userinput>." -#~ msgstr "" -#~ "在 SRM 上，以太网界面名字带有 <userinput>ewa</userinput> 前缀，并可以用 " -#~ "<userinput>show dev</userinput> 命令列出，类似如下显示(可能有一点不同)： " -#~ "<informalexample><screen>\n" -#~ ">>> show dev\n" -#~ "ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" -#~ "ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" -#~ "ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" -#~ "</screen></informalexample> 您首先需要设置引导协议： " -#~ "<informalexample><screen>\n" -#~ ">>> set ewa0_protocol bootp\n" -#~ "</screen></informalexample> 然后检查媒介类型是否正确： " -#~ "<informalexample><screen>\n" -#~ ">>> set ewa0_mode <replaceable>mode</replaceable>\n" -#~ "</screen></informalexample> 获得一个有效模式的列表 <userinput>>>>" -#~ "set ewa0_mode</userinput>。" - -#~ msgid "" -#~ "Then, to boot from the first Ethernet interface, you would type: " -#~ "<informalexample><screen>\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ "</screen></informalexample> This will boot using the default kernel " -#~ "parameters as included in the netboot image." -#~ msgstr "" -#~ "接下来，如果从第一个以太网界面引导，您需要输入： " -#~ "<informalexample><screen>\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ "</screen></informalexample> 这将 netboot 映象启动，并使用默认的内核参数。" - -#~ msgid "" -#~ "If you wish to use a serial console, you <emphasis>must</emphasis> pass " -#~ "the <userinput>console=</userinput> parameter to the kernel. This can be " -#~ "done using the <userinput>-flags</userinput> argument to the SRM " -#~ "<userinput>boot</userinput> command. The serial ports are named the same " -#~ "as their corresponding files in <userinput>/dev</userinput>. Also, when " -#~ "specifying additional kernel parameters, you must repeat certain default " -#~ "options that are needed by the &d-i; images. For example, to boot from " -#~ "<userinput>ewa0</userinput> and use a console on the first serial port, " -#~ "you would type:" -#~ msgstr "" -#~ "如果希望使用一个串行控制台，您 <emphasis>必须</emphasis> 给内核传递 " -#~ "<userinput>console=</userinput> 参数。这个工作可以使用附带 <userinput>-" -#~ "flags</userinput> 参数的 SRM <userinput>boot</userinput> 命令来完成。串口" -#~ "号的命名和它们在目录 <userinput>/dev</userinput> 中相同。另外，如有指定额" -#~ "外的内核参数，也必须给 &d-i; 映象重复指定。比如，如果需要从 " -#~ "<userinput>ewa0</userinput> 引导，并且在第一个串口使用控制台，您需要输入：" - -#~ msgid "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" -#~ msgstr "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" - -#~ msgid "Booting from CD-ROM with the SRM Console" -#~ msgstr "采用 SRM 控制台来从 CD 光盘上引导" - -#~ msgid "" -#~ "The &debian; install CDs include several preconfigured boot options for " -#~ "VGA and serial consoles. Type <informalexample><screen>\n" -#~ ">>> boot xxxx -flags 0\n" -#~ "</screen></informalexample> to boot using VGA console, where " -#~ "<replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation. To " -#~ "use serial console on the first serial device, type " -#~ "<informalexample><screen>\n" -#~ ">>> boot xxxx -flags 1\n" -#~ "</screen></informalexample> and for console on the second serial port, " -#~ "type" -#~ msgstr "" -#~ "&debian; 安装光盘为 VGA 和串口控制台包含了一些预置的引导选项。键入 " -#~ "<informalexample><screen>\n" -#~ ">>> boot xxxx -flags 0\n" -#~ "</screen></informalexample> 使用 VGA 控制台引导，其中 <replaceable>xxxx</" -#~ "replaceable> 是您的 CD-ROM 驱动器的 SRM 记号。要使用第一个串口设备上的串行" -#~ "控制台，键入 <informalexample><screen>\n" -#~ ">>> boot xxxx -flags 1\n" -#~ "</screen></informalexample> 而对第二个串口上的控制台，键入" - -#~ msgid ">>> boot xxxx -flags 2" -#~ msgstr ">>> boot xxxx -flags 2" - -#~ msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" -#~ msgstr "通过 ARC 或者 AlphaBIOS 控制台来从 CD 光盘上启动" - -#~ msgid "" -#~ "To boot a CD-ROM from the ARC console, find your sub-architecture code " -#~ "name (see <xref linkend=\"alpha-cpus\"/>), then enter <filename>\\milo" -#~ "\\linload.exe</filename> as the boot loader and <filename>\\milo" -#~ "\\<replaceable>subarch</replaceable></filename> (where " -#~ "<replaceable>subarch</replaceable> is the proper subarchitecture name) as " -#~ "the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: " -#~ "You need to use <filename>\\milo\\ldmilo.exe</filename> as boot loader." -#~ msgstr "" -#~ "为了从 ARC 控制台引导 CD 光盘，找出您的子体系结构代码名称(参见 <xref " -#~ "linkend=\"alpha-cpus\"/>)，然后输入 <filename>\\milo\\linload.exe</" -#~ "filename> 作为引导装载器并且在 `OS Selection Setup' 菜单下选择 <filename>" -#~ "\\milo\\<replaceable>subarch</replaceable></filename> (这里 " -#~ "<replaceable>subarch</replaceable> 是相应的子体系结构名称)作为操作系统路" -#~ "径。Ruffians 则是一个例外：您需要使用 <filename>\\milo\\ldmilo.exe</" -#~ "filename> 作为引导装载器。" - -#~ msgid "Booting from Floppies with the SRM Console" -#~ msgstr "通过 SRM 控制台从软盘引导" - -#~ msgid "" -#~ "At the SRM prompt (<prompt>>>></prompt>), issue the following " -#~ "command: <informalexample><screen>\n" -#~ ">>> boot dva0 -flags 0\n" -#~ "</screen></informalexample> possibly replacing <filename>dva0</filename> " -#~ "with the actual device name. Usually, <filename>dva0</filename> is the " -#~ "floppy; type <informalexample><screen>\n" -#~ ">>> show dev\n" -#~ "</screen></informalexample> to see the list of devices (e.g., if you want " -#~ "to boot from a CD). Note that if you are booting via MILO, <command>-" -#~ "flags</command> argument is ignored, so you can just type <command>boot " -#~ "dva0</command>. If everything works OK, you will eventually see the Linux " -#~ "kernel boot." -#~ msgstr "" -#~ "在 SRM 提示符下 (<prompt>>>></prompt>)，使用如下命令： " -#~ "<informalexample><screen>\n" -#~ ">>> boot dva0 -flags 0\n" -#~ "</screen></informalexample> 可以用实际的设备名称来替换 <filename>dva0</" -#~ "filename>。通常情况下，<filename>dva0</filename> 是软盘；输入 " -#~ "<informalexample><screen>\n" -#~ ">>> show dev\n" -#~ "</screen></informalexample> 来查看设备列表(比如，如果您想从一张 CD 上面引" -#~ "导)。注意如果您想通过 MILO 引导 <command>-flags</command> 参数将被忽略，因" -#~ "此您可以只需输入 <command>boot dva0</command>。如果上面步骤工作正常，您将" -#~ "最终看到 Linux 内核引导。" - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via <command>aboot</" -#~ "command>, use the following command: <informalexample><screen>\n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ "</screen></informalexample> (typed on one line), substituting, if " -#~ "necessary, the actual SRM boot device name for <filename>dva0</filename>, " -#~ "the Linux boot device name for <filename>fd0</filename>, and the desired " -#~ "kernel parameters for <filename>arguments</filename>." -#~ msgstr "" -#~ "如果您想在通过 <command>aboot</command> 引导的时候指定特定的内核参数，请使" -#~ "用如下命令： <informalexample><screen>\n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ "</screen></informalexample> (输入到一行)，如果需要，替换 <filename>dva0</" -#~ "filename> 的真实 SRM 引导设备名 <filename>dva0</filename>，<filename>fd0</" -#~ "filename> 的 Linux 引导设备名，<filename>arguments</filename> 需要的内核参" -#~ "数。" - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via <command>MILO</" -#~ "command>, you will have to interrupt bootstrap once you get into MILO. " -#~ "See <xref linkend=\"booting-from-milo\"/>." -#~ msgstr "" -#~ "如果您想在通过 <command>MILO</command> 启动时指定内核参数，您必须在进入 " -#~ "MILO 时中断引导。参阅 <xref linkend=\"booting-from-milo\"/>。" - -#~ msgid "Booting from Floppies with the ARC or AlphaBIOS Console" -#~ msgstr "在 ARC 或者 AlphaBISO 控制台下从软盘引导" - -#~ msgid "" -#~ "In the OS Selection menu, set <command>linload.exe</command> as the boot " -#~ "loader, and <command>milo</command> as the OS Path. Bootstrap using the " -#~ "newly created entry." -#~ msgstr "" -#~ "在操作系统选择菜单内，设置 <command>linload.exe</command> 作为引导装载器，" -#~ "并且 <command>milo</command> 作为操作系统参数。然后使用这个最近建立的选项" -#~ "启动。" - -#~ msgid "Booting with MILO" -#~ msgstr "采用 MILO 引导" - -#~ msgid "" -#~ "MILO contained on the bootstrap media is configured to proceed straight " -#~ "to Linux automatically. Should you wish to intervene, all you need is to " -#~ "press space during MILO countdown." -#~ msgstr "" -#~ "自我启动介质上的 MILO 会自动直接进入 Linux 引导过程。如果您要对此有所控" -#~ "制，只需要在 MILO 倒计时时按下空格键。" - -#~ msgid "" -#~ "If you want to specify all the bits explicitly (for example, to supply " -#~ "additional parameters), you can use a command like this: " -#~ "<informalexample><screen>\n" -#~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments --" -#~ ">\n" -#~ "</screen></informalexample> If you are booting from something other than " -#~ "a floppy, substitute <filename>fd0</filename> in the above example with " -#~ "the appropriate device name in Linux notation. The <command>help</" -#~ "command> command would give you a brief MILO command reference." -#~ msgstr "" -#~ "如果您想显式指定所有的位(比如，支持附加的参数)，您可以使用像下面形式的命" -#~ "令： <informalexample><screen>\n" -#~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments --" -#~ ">\n" -#~ "</screen></informalexample> 如果通过软盘之外别的方法引导，在 Linux 标记下" -#~ "把上面例子中的 <filename>fd0</filename> 替换成合适的设备名称。" -#~ "<command>help</command> 命令将给出一个简单的 MILO 命令参考。" - -#~ msgid "Choosing an Installation Method" -#~ msgstr "选择安装方法" - -#~ msgid "" -#~ "Some &arch-title; subarchs have the option of booting using either a 2.4." -#~ "x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux " -#~ "kernel. The installer should also require less memory when using a 2.4.x " -#~ "linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x " -#~ "uses tmpfs." -#~ msgstr "" -#~ "一些 &arch-title; 子体系可以选择使用从 2.4.x 或 2.2.x linux 内核启动。如果" -#~ "可以这样选取，请使用 2.4.x linux 内核。使用 2.4.x linux 内核的安装程序要求" -#~ "较少的内存，因为 2.2.x 支持需要固定尺寸的 ramdisk 而 2.4.x 使用 tmpfs。" - -#~ msgid "" -#~ "If you are using a 2.2.x linux kernel, then you need to use the " -#~ "&ramdisksize; kernel parameter." -#~ msgstr "如果您在使用 2.2.x 内核，那么需要设置 &ramdisksize; 内核参数。" - -#~ msgid "" -#~ "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel " -#~ "parameters." -#~ msgstr "确保 <userinput>root=/dev/ram</userinput> 在内核参数中。" - -#~ msgid "" -#~ "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's " -#~ "&arch-title; debian-installer FAQ</ulink>." -#~ msgstr "" -#~ "如果碰到麻烦，检查 <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; " -#~ "debian-installer FAQ</ulink>。" - -#~ msgid "Amiga" -#~ msgstr "Amiga" - -#~ msgid "" -#~ "The only method of installation available to amiga is the hard drive (see " -#~ "<xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is " -#~ "not bootable.</emphasis>" -#~ msgstr "" -#~ "amiga 仅支持从硬盘安装方式(参阅 <xref linkend=\"m68k-boot-hd\"/>)。" -#~ "<emphasis>也就是说 cdrom 无法启动。</emphasis>" - -#~ msgid "" -#~ "Amiga does not currently work with bogl, so if you are seeing bogl " -#~ "errors, you need to include the boot parameter <userinput>fb=false</" -#~ "userinput>." -#~ msgstr "" -#~ "当前 Amiga 不能与 bogl 一起工作，如果您看到 bogl 错误，您应该包含下面内核" -#~ "参数 <userinput>fb=false</userinput>。" - -#~ msgid "Atari" -#~ msgstr "Atari" - -#~ msgid "" -#~ "The installer for atari may be started from either the hard drive (see " -#~ "<xref linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=" -#~ "\"boot-from-floppies\"/>). <emphasis>In other words the cdrom is not " -#~ "bootable.</emphasis>" -#~ msgstr "" -#~ "atari 安装程序可以从硬盘(参阅 <xref linkend=\"m68k-boot-hd\"/>) 或软盘 (参" -#~ "阅 <xref linkend=\"boot-from-floppies\"/>)。<emphasis>也就是说 cdrom 无法" -#~ "启动。</emphasis>" - -#~ msgid "" -#~ "Atari does not currently work with bogl, so if you are seeing bogl " -#~ "errors, you need to include the boot parameter <userinput>fb=false</" -#~ "userinput>." -#~ msgstr "" -#~ "当前 Atari 不能与 bogl 一起工作，如果您看到 bogl 错误，应该包含下面内核参" -#~ "数 <userinput>fb=false</userinput>。" - -#~ msgid "BVME6000" -#~ msgstr "BVME6000" - -#~ msgid "" -#~ "The installer for BVME6000 may be started from a cdrom (see <xref linkend=" -#~ "\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies" -#~ "\"/>), or the net (see <xref linkend=\"boot-tftp\"/>)." -#~ msgstr "" -#~ "BVME6000 上安装程序可以从 cdrom (参阅 <xref linkend=\"m68k-boot-cdrom\"/" -#~ ">), 软盘(参阅 <xref linkend=\"boot-from-floppies\"/>)，或网络(参阅 <xref " -#~ "linkend=\"boot-tftp\"/>)。" - -#~ msgid "Macintosh" -#~ msgstr "Macintosh" - -#~ msgid "" -#~ "The only method of installation available to mac is from the hard drive " -#~ "(see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the " -#~ "cdrom is not bootable.</emphasis> Macs do not have a working 2.4.x kernel." -#~ msgstr "" -#~ "mac 上启动的唯一方法是硬盘(参阅 <xref linkend=\"m68k-boot-hd\"/>)。" -#~ "<emphasis>也就是说 cdrom 无法启动。</emphasis> Macs 不能工作在 2.4 内核" -#~ "上。" - -#~ msgid "" -#~ "If your hardware uses a 53c9x-based scsi bus, then you may need to " -#~ "include the kernel parameter <userinput>mac53c9x=1,0</userinput>. " -#~ "Hardware with two such scsi buses, such as the Quadra 950, will need " -#~ "<userinput>mac53c9x=2,0</userinput> instead. Alternatively, the parameter " -#~ "can be specified as <userinput>mac53c9x=-1,0</userinput> which will leave " -#~ "autodetection on, but which will disable SCSI disconnects. Note that " -#~ "specifying this parameter is only necessary if you have more than one " -#~ "hard disk; otherwise, the system will run faster if you do not specify it." -#~ msgstr "" -#~ "如果您的硬件中包括基于 53c9x 的 scsi 总线，那么您需要包括下面的内核参数 " -#~ "<userinput>mac53c9x=1,0</userinput>。带有两个这种 scsi 总线的硬件，如 " -#~ "Quadra 950，您需要 <userinput>mac53c9x=2,0</userinput> 参数。另外，参数指" -#~ "定为 <userinput>mac53c9x=-1,0</userinput> 可打开自动侦测，但却禁止了 SCSI " -#~ "断开。注意，使用这种参数仅用于不止一个硬盘的情况下; 如果不指定，您的系统将" -#~ "运行得更快。" - -#~ msgid "MVME147 and MVME16x" -#~ msgstr "MVME147 and MVME16x" - -#~ msgid "" -#~ "The installer for MVME147 and MVME16x may be started from either floppies " -#~ "(see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref " -#~ "linkend=\"boot-tftp\"/>). <emphasis>In other words the cdrom is not " -#~ "bootable.</emphasis>" -#~ msgstr "" -#~ "MVEM147 和 MVEM16x 可以从软盘(参阅 <xref linkend=\"boot-from-floppies\"/>)" -#~ "或网络(参阅 <xref linkend=\"boot-tftp\"/>)。<emphasis>也就是说 cdrom 无法" -#~ "启动。</emphasis>" - -#~ msgid "Q40/Q60" -#~ msgstr "Q40/Q60" - -#~ msgid "" -#~ "The only method of installation available to Q40/Q60 is from the hard " -#~ "drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words " -#~ "the cdrom is not bootable.</emphasis>" -#~ msgstr "" -#~ "Q40/Q60 只支持从硬盘安装(参阅 <xref linkend=\"m68k-boot-hd\"/>)。" -#~ "<emphasis>也就是说 cdrom 无法启动。</emphasis>" - -#~ msgid "Booting from a Hard Disk" -#~ msgstr "从硬盘引导" - -#~ msgid "" -#~ "At least six different ramdisks may be used to boot from the hard drive, " -#~ "three different types each with and without support for a 2.2.x linux " -#~ "kernel (see <ulink url=\"&disturl;/main/installer-&architecture;/current/" -#~ "images/MANIFEST\">MANIFEST</ulink> for details)." -#~ msgstr "" -#~ "至少有六中不同的 ramdisk 可以从硬盘启动，三个不同的类型分别用于支持或不支" -#~ "持 2.2.x linux 内核(参阅 <ulink url=\"&disturl;/main/installer-" -#~ "&architecture;/current/images/MANIFEST\">MANIFEST</ulink> 了解更多细节)。" - -#~ msgid "" -#~ "The three different types of ramdisks are <filename>cdrom</filename>, " -#~ "<filename>hd-media</filename>, and <filename>nativehd</filename>. These " -#~ "ramdisks differ only in their source for installation packages. The " -#~ "<filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer " -#~ "packages. The <filename>hd-media</filename> ramdisk uses an iso image " -#~ "file of a cdrom currently residing on a hard disk. Finally, the " -#~ "<filename>nativehd</filename> ramdisk uses the net to install packages." -#~ msgstr "" -#~ "这三种 ramdisk 类型为 <filename>cdrom</filename>, <filename>hd-media</" -#~ "filename>，和 <filename>nativehd</filename>。它们的区别仅在于安装软件包的" -#~ "源不同。<filename>cdrom</filename> ramdisk 使用 cdrom 获取 debian-" -#~ "installer 软件包。<filename>hd-media</filename> ramdisk 使用硬盘上的 iso " -#~ "映象文件。最后，<filename>nativehd</filename> ramdisk 使用网络安装软件包。" - -#~ msgid "Booting from AmigaOS" -#~ msgstr "从 AmigaOS 上引导" - -#~ msgid "" -#~ "In the <command>Workbench</command>, start the Linux installation process " -#~ "by double-clicking on the <guiicon>StartInstall</guiicon> icon in the " -#~ "<filename>debian</filename> directory." -#~ msgstr "" -#~ "在 <command>Workbench</command> 下，双击 <guiicon>StartInstall</guiicon> " -#~ "图标来启动 Linux 安装过程，它位于 <filename>debian</filename> 目录中。" - -#~ msgid "" -#~ "You may have to press the &enterkey; key twice after the Amiga installer " -#~ "program has output some debugging information into a window. After this, " -#~ "the screen will go grey, there will be a few seconds' delay. Next, a " -#~ "black screen with white text should come up, displaying all kinds of " -#~ "kernel debugging information. These messages may scroll by too fast for " -#~ "you to read, but that's OK. After a couple of seconds, the installation " -#~ "program should start automatically, so you can continue down at <xref " -#~ "linkend=\"d-i-intro\"/>." -#~ msgstr "" -#~ "在 Amiga 安装程序在一个窗口已经输出一些调试信息，您也可以按下 &enterkey; " -#~ "两次。之后屏幕将变灰，这里有一些很短的延迟。接下来，一个黑屏白字将显示更多" -#~ "的调试信息。这些 信息可能上翻的非常快无法看到，但这没有问题。在一些时间过" -#~ "后，安装程序应该自动安装，因此您可以继续参阅 <xref linkend=\"d-i-intro\"/" -#~ ">。" - -#~ msgid "Booting from Atari TOS" -#~ msgstr "从 Atari TOS 引导" - -#~ msgid "" -#~ "At the GEM desktop, start the Linux installation process by double-" -#~ "clicking on the <guiicon>bootstra.prg</guiicon> icon in the " -#~ "<filename>debian</filename> directory and clicking <guibutton>Ok</" -#~ "guibutton> at the program options dialog box." -#~ msgstr "" -#~ "在 GEM 桌面上，可以通过双击 <guiicon>bootstra.prg</guiicon> 图标，它位于 " -#~ "<filename>debian</filename> 目录下，并且在程序选项对话框内点击 " -#~ "<guibutton>Ok</guibutton> 来开始启动安装过程。" - -#~ msgid "" -#~ "You may have to press the &enterkey; key after the Atari bootstrap " -#~ "program has output some debugging information into a window. After this, " -#~ "the screen will go grey, there will be a few seconds' delay. Next, a " -#~ "black screen with white text should come up, displaying all kinds of " -#~ "kernel debugging information. These messages may scroll by too fast for " -#~ "you to read, but that's OK. After a couple of seconds, the installation " -#~ "program should start automatically, so you can continue below at <xref " -#~ "linkend=\"d-i-intro\"/>." -#~ msgstr "" -#~ "当 Atari 安装程序在一个窗口输出一些调试信息以后，您可能必须按下 " -#~ "&enterkey;。之后屏幕将变灰，这里有一些很短的延迟。接下来，一个黑屏白字将显" -#~ "示更多的调试信息。这些信息可能上翻的非常快没法看，但这没有问题。在一些时间" -#~ "过后，安装程序应该自动安装，因此您可以继续参阅 <xref linkend=\"d-i-intro" -#~ "\"/>。" - -#~ msgid "Booting from MacOS" -#~ msgstr "从 MacOS 引导" - -#~ msgid "" -#~ "You must retain the original Mac system and boot from it. It is " -#~ "<emphasis>essential</emphasis> that, when booting MacOS in preparation " -#~ "for booting the Penguin linux loader, you hold the <keycap>shift</keycap> " -#~ "key down to prevent extensions from loading. If you don't use MacOS " -#~ "except for loading linux, you can accomplish the same thing by removing " -#~ "all extensions and control panels from the Mac's System Folder. Otherwise " -#~ "extensions may be left running and cause random problems with the running " -#~ "linux kernel." -#~ msgstr "" -#~ "您必须有原来的 Mac 系统，并从它启动。它是 <emphasis>必要的</emphasis>，当" -#~ "启动 MacOS 准备启动 Penguin linux 加载器时，按住 <keycap>shift</keycap> 键" -#~ "阻止加载扩展。如果除了加载 linux 不使用 MacOS，您可以从 Mac 的系统文件夹下" -#~ "清除所有的扩展和控制面板达到同样的目的。否则扩展会运行使运行的 linux 内核" -#~ "参数随机错误。" - -#~ msgid "" -#~ "Macs require the <command>Penguin</command> bootloader, which can be " -#~ "downloaded from <ulink url=\"&url-m68k-mac;\">the Linux/mac68k " -#~ "sourceforge.net project</ulink>. If you do not have the tools to handle a " -#~ "<command>Stuffit</command> archive, you can put it on a MacOS-formatted " -#~ "floppy using a second GNU/Linux machine of any architecture and the " -#~ "<command>hmount</command>, <command>hcopy</command>, and " -#~ "<command>humount</command> tools from the <classname>hfsutils</classname> " -#~ "suite." -#~ msgstr "" -#~ "Mac 需要用 <command>Penguin</command> bootloader，它可以从 <ulink url=" -#~ "\"&url-m68k-mac;\">the Linux/mac68k sourceforge.net project</ulink> 下载。" -#~ "如果您没有处理 <command>Stuffit</command> 档案的工具，可以将它放到一张 " -#~ "MacOS 格式化的软盘，再用一台任意体系的 GNU/Linux 机器，使用 " -#~ "<classname>hfsutils</classname> 套件里面的 <command>hmount</command>、" -#~ "<command>hcopy</command> 和 <command>humount</command> 工具。" - -#~ msgid "" -#~ "At the MacOS desktop, start the Linux installation process by double-" -#~ "clicking on the <guiicon>Penguin Prefs</guiicon> icon in the " -#~ "<filename>Penguin</filename> directory. The <command>Penguin</command> " -#~ "booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item " -#~ "in the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</" -#~ "guilabel> tab. Select the kernel (<filename>vmlinuz</filename>) and " -#~ "ramdisk (<filename>initrd.gz</filename>) images in the <filename>install</" -#~ "filename> directory by clicking on the corresponding buttons in the upper " -#~ "right corner, and navigating the file select dialogs to locate the files." -#~ msgstr "" -#~ "在 MacOS 桌面，启动 Linux 安装进行需要双击 <guiicon>Penguin Prefs</" -#~ "guiicon> 图标，它位于 <filename>Penguin</filename> 目录。" -#~ "<command>Penguin</command> 引导将开始。进入到 <guimenuitem>Settings</" -#~ "guimenuitem> 项，它位于 <guimenu>File</guimenu>菜单，点击 " -#~ "<guilabel>Kernel</guilabel> 选项卡。选择内核(<filename>vmlinuz</filename>)" -#~ "和 ramdisk (<filename>initrd.gz</filename>) 映象，它位于 " -#~ "<filename>install</filename> 目录，点击右上角对应的按钮，引导文件选择对话" -#~ "框至文件。" - -#~ msgid "" -#~ "To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -" -#~ "> <guimenuitem>Settings...</guimenuitem>, then switch to the " -#~ "<guilabel>Options</guilabel> tab. Boot parameters may be typed in to the " -#~ "text entry area. If you will always want to use these settings, select " -#~ "<guimenu>File</guimenu> -> <guimenuitem>Save Settings as Default</" -#~ "guimenuitem>." -#~ msgstr "" -#~ "为 Penguin 设置启动参数，选择 <guimenu>File</guimenu> -> " -#~ "<guimenuitem>Settings...</guimenuitem>，然后切换到 <guilabel>Options</" -#~ "guilabel> 选项卡。启动参数可以写到文本区域。如果您要一直采用这些设置，选" -#~ "择 <guimenu>File</guimenu> -> <guimenuitem>保存设置为默认</" -#~ "guimenuitem>。" - -#~ msgid "" -#~ "Close the <guilabel>Settings</guilabel> dialog, save the settings and " -#~ "start the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in " -#~ "the <guimenu>File</guimenu> menu." -#~ msgstr "" -#~ "关闭 <guilabel>Settings</guilabel> 对话框，保存设置然后开始引导用 " -#~ "<guimenuitem>Boot Now</guimenuitem> 项，它位于 <guimenu>File</guimenu> 菜" -#~ "单。" - -#~ msgid "" -#~ "The <command>Penguin</command> booter will output some debugging " -#~ "information into a window. After this, the screen will go grey, there " -#~ "will be a few seconds' delay. Next, a black screen with white text should " -#~ "come up, displaying all kinds of kernel debugging information. These " -#~ "messages may scroll by too fast for you to read, but that's OK. After a " -#~ "couple of seconds, the installation program should start automatically, " -#~ "so you can continue below at <xref linkend=\"d-i-intro\"/>." -#~ msgstr "" -#~ "<command>Penguin</command> 启动将输出一些调试信息到窗口。然后，屏幕变灰，" -#~ "会有数秒延迟。接着，带有文本的黑屏出现，显示各种内核调试信息。这些信息可能" -#~ "滚动很快无法阅读，这是正常的。再过一段时间，安装程序就会自动运行，您可以按" -#~ "下面步骤继续 <xref linkend=\"d-i-intro\"/>。" - -#~ msgid "Booting from Q40/Q60" -#~ msgstr "从 Q40/Q60 启动" - -#~ msgid "FIXME" -#~ msgstr "FIXME" - -#~ msgid "" -#~ "The installation program should start automatically, so you can continue " -#~ "below at <xref linkend=\"d-i-intro\"/>." -#~ msgstr "" -#~ "安装程序就会自动运行，您可以按下面步骤继续 <xref linkend=\"d-i-intro\"/>。" - -#~ msgid "" -#~ "Currently, the only &arch-title; subarchitecture that supports CD-ROM " -#~ "booting is the BVME6000." -#~ msgstr "目前唯一 &arch-title; 子体系结构支持 CD 光盘引导的是 BVME6000。" - -#~ msgid "" -#~ "After booting the VMEbus systems you will be presented with the LILO " -#~ "<prompt>Boot:</prompt> prompt. At that prompt enter one of the following " -#~ "to boot Linux and begin installation proper of the Debian software using " -#~ "vt102 terminal emulation:" -#~ msgstr "" -#~ "在引导 VMEbus 系统后您应该看到 LILO <prompt>Boot:</prompt> 提示符。在提示" -#~ "符下输入以下一种方法来引导 Linux，并开始在一个 vt102 仿真终端下面安装普通" -#~ "的 Debian 软件。" - -#~ msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000" -#~ msgstr "输入 <screen>i6000 &enterkey;</screen> 来安装 BVME4000/6000" - -#~ msgid "type <screen>i162 &enterkey;</screen> to install an MVME162" -#~ msgstr "输入 <screen>i162 &enterkey;</screen> 来安装 MVME162" - -#~ msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167" -#~ msgstr "输入 <screen>i167 &enterkey;</screen> 来安装 MVME166/167" - -#~ msgid "" -#~ "You may additionally append the string <screen>TERM=vt100</screen> to use " -#~ "vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</" -#~ "screen>." -#~ msgstr "" -#~ "您也可以附加一个字符串 <screen>TERM=vt100</screen> 来使用 vt100 终端模拟。" -#~ "比如,<screen>i6000 TERM=vt100 &enterkey;</screen>。" - -#~ msgid "" -#~ "For most &arch-title; architectures, booting from a local filesystem is " -#~ "the recommended method." -#~ msgstr "" -#~ "对于大多数 m68k 体系来说，推荐方法是从一个本地文件系统引导安装程序。" - -#~ msgid "" -#~ "Booting from the boot floppy is supported only for Atari and VME (with a " -#~ "SCSI floppy drive on VME) at this time." -#~ msgstr "从软盘引导的方法目前只支持 Atari 以及 VME (VME 有一个 SCSI 软驱)。" - -#~ msgid "Such problems have been reported on the Amiga 1200 and SE/30." -#~ msgstr "在 Amiga 1200 and SE/30 上面报告过具有有这些方面的问题。" diff --git a/po/zh_CN/boot-new.po b/po/zh_CN/boot-new.po index f3ef80079..57ac4c517 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: 2009-11-02 22:05+0000\n" -"PO-Revision-Date: 2007-03-13 16:55+0800\n" +"PO-Revision-Date: 2009-11-21 11:46+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" @@ -598,87 +598,3 @@ msgstr "" "如果命令的结果滚动超出屏幕顶端，命令后面加上 <userinput>| more</" "userinput>，可以让输出在滚出顶端屏幕前暂停。查看某字母开始的所有可用命令，键" "入该字母，然后按两个 tab。" - -#~ msgid "BVME 6000 Booting" -#~ msgstr "BVME 6000 启动" - -#~ msgid "" -#~ "If you have just performed a diskless install on a BVM or Motorola VMEbus " -#~ "machine: once the system has loaded the <command>tftplilo</command> " -#~ "program from the TFTP server, from the <prompt>LILO Boot:</prompt> prompt " -#~ "enter one of:" -#~ msgstr "" -#~ "如果您是采用无盘方式安装到 BVM 或 Motorola VMEbus 机器上： 一旦系统从 " -#~ "TFTP 服务器加载 <command>tftplilo</command> 程序，在 <prompt>LILO Boot:</" -#~ "prompt> 提示符下输入：" - -#~ msgid "" -#~ "<userinput>b6000</userinput> followed by &enterkey; to boot a BVME " -#~ "4000/6000" -#~ msgstr "<userinput>b6000</userinput> 然后按 &enterkey; 启动 BVME 4000/6000" - -#~ msgid "" -#~ "<userinput>b162</userinput> followed by &enterkey; to boot an MVME162" -#~ msgstr "<userinput>b162</userinput> 然后按 &enterkey; 启动 MVME162" - -#~ msgid "" -#~ "<userinput>b167</userinput> followed by &enterkey; to boot an MVME166/167" -#~ msgstr "<userinput>b167</userinput> 然后按 &enterkey; 启动 MVME166/167" - -#~ msgid "Macintosh Booting" -#~ msgstr "Macintosh 启动" - -#~ msgid "" -#~ "Go to the directory containing the installation files and start up the " -#~ "<command>Penguin</command> booter, holding down the <keycap>command</" -#~ "keycap> key. Go to the <userinput>Settings</userinput> dialogue " -#~ "(<keycombo> <keycap>command</keycap> <keycap>T</keycap> </keycombo>), and " -#~ "locate the kernel options line which should look like <userinput>root=/" -#~ "dev/ram ramdisk_size=15000</userinput> or similar." -#~ msgstr "" -#~ "进入包含安装文件的目录，然后启动 <command>Penguin</command> 引导器，按住 " -#~ "<keycap>command</keycap> 键。进入 <userinput>Settings</userinput> 对话框" -#~ "(<keycombo> <keycap>command</keycap> <keycap>T</keycap> </keycombo>)，然后" -#~ "定位到内核选项那行，它看起来应该像 <userinput>root=/dev/ram " -#~ "ramdisk_size=15000</userinput> 这样。" - -#~ msgid "" -#~ "You need to change the entry to <userinput>root=/dev/<replaceable>yyyy</" -#~ "replaceable></userinput>. Replace the <replaceable>yyyy</replaceable> " -#~ "with the Linux name of the partition onto which you installed the system " -#~ "(e.g. <filename>/dev/sda1</filename>); you wrote this down earlier. For " -#~ "users with tiny screens, adding <userinput>fbcon=font:VGA8x8</userinput> " -#~ "(or <userinput>video=font:VGA8x8</userinput> on pre-2.6 kernels) may help " -#~ "readability. You can change this at any time." -#~ msgstr "" -#~ "您需要将条目修改为 <userinput>root=/dev/<replaceable>yyyy</replaceable></" -#~ "userinput>。将其中的 <replaceable>yyyy</replaceable> 替换为您安装的 Linux " -#~ "分区名称(例如，<filename>/dev/sda1</filename>); 即早先记下的内容。小屏幕的" -#~ "用户，使用 <userinput>fbcon=font:VGA8x8</userinput> (2.6 以前的内核或者使" -#~ "用 <userinput>video=font:VGA8x8</userinput>) 有易于阅读。您可以随时修改" -#~ "它。" - -#~ msgid "" -#~ "If you don't want to start GNU/Linux immediately each time you start, " -#~ "uncheck the <userinput>Auto Boot</userinput> option. Save your settings " -#~ "in the <filename>Prefs</filename> file using the <userinput>Save Settings " -#~ "As Default</userinput> option." -#~ msgstr "" -#~ "如果您不想每次启动时立即启动 GNU/Linux，去除 <userinput>Auto Boot</" -#~ "userinput> 选项。保存设置到 <filename>Prefs</filename> 文件，使用 " -#~ "<userinput>Save Settings As Default</userinput> 选项。" - -#~ msgid "" -#~ "Now select <userinput>Boot Now</userinput> (<keycombo> <keycap>command</" -#~ "keycap> <keycap>B</keycap> </keycombo>) to start your freshly installed " -#~ "GNU/Linux instead of the RAMdisk installer system." -#~ msgstr "" -#~ "现在选择 <userinput>Boot Now</userinput> (<keycombo> <keycap>command</" -#~ "keycap> <keycap>B</keycap> </keycombo>) 启动新安装的 GNU/Linux，而不是 " -#~ "RAMdisk 安装系统。" - -#~ msgid "" -#~ "Debian should boot, and you should see the same messages as when you " -#~ "first booted the installation system, followed by some new messages." -#~ msgstr "" -#~ "Debian 应该启动，然后您将看到与安装系统同样的讯息，跟着是一些新讯息。" diff --git a/po/zh_CN/hardware.po b/po/zh_CN/hardware.po index 16bc169e2..229681e0a 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: 2009-11-18 01:11+0000\n" -"PO-Revision-Date: 2009-08-01 14:25+0800\n" +"PO-Revision-Date: 2009-11-21 12:04+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" @@ -453,7 +453,7 @@ msgid "" "the Pentium D and the Core2 Duo). Those systems are supported by " "the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit " "userland, the <emphasis>i386</emphasis> architecture." -msgstr "" +msgstr "&arch-title; 体系只支持 Intel Itanium 处理器，而不是常见的属于 EM64T 家族的 64 位处理器(包括像 Pentium D 和 Core2 Duo)。它们是被 <emphasis>amd64</emphasis> 体系支持。如果您希望使用 32 位系统，可以选择 <emphasis>i386</emphasis> 体系。" #. Tag: para #: hardware.xml:188 @@ -593,7 +593,7 @@ msgstr "Kirkwood" #. Tag: para #: hardware.xml:302 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM " #| "CPU, Ethernet, SATA, USB, and other functionality in one chip. We " @@ -608,12 +608,7 @@ msgid "" "<ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (TS-" "110, TS-119, TS-210, TS-219 and TS-219P; the TS-410 and TS-419P are not yet " "supported)." -msgstr "" -"Kirkwood 是 Marvell 的 SoC (system on a chip) 产品，芯片上集成了 ARM CPU、以" -"太网、SATA、USB，以及一些其他的功能。当前我们能支持以下几种基于 Kirkwood 的设" -"备: <ulink url=\"&url-arm-cyrius-sheevaplug;\">SheevaPlug</ulink> 和 <ulink " -"url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (TS-119 " -"and TS-219)。" +msgstr "Kirkwood 是 Marvell 的 SoC (system on a chip) 产品，该芯片上集成了 ARM CPU、Ethernet、SATA、USB，以及一些其他的功能。当前我们能支持以下几种基于 Kirkwood 的设备： OpenRD (OpenRD-Base 和 OpenRD-Client)、<ulink url=\"&url-arm-cyrius-sheevaplug;\">SheevaPlug</ulink> 和 <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (TS-110, TS-119, TS-210, TS-219 和 TS-219P; TS-410 和 TS-419P 仍然不被支持)。" #. Tag: term #: hardware.xml:317 @@ -2754,798 +2749,3 @@ msgstr "" "本界面需要更多的内存，并且内存不应少于 &minimum-memory; 。如果可以在普通和图" "形界面两种方式之间选择，应选择普通方式。</para> </footnote>或磁盘空间上安装系" "统或许可行，但只针对有经验的用户。" - -#~ msgid "DEC Alpha" -#~ msgstr "DEC Alpha" - -#~ msgid "alpha" -#~ msgstr "alpha" - -#~ msgid "" -#~ "Complete information regarding supported DEC Alphas can be found at " -#~ "<ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose " -#~ "of this section is to describe the systems supported by the boot disks." -#~ msgstr "" -#~ "完整的 DEC Alphas 支持情况信息可以在 <ulink url=\"&url-alpha-howto;" -#~ "\">Linux Alpha HOWTO</ulink> 中找到。本节是描述启动盘对系统支持的概况。" - -#~ msgid "" -#~ "Alpha machines are subdivided into different system types because there " -#~ "are a number of generations of motherboard and supporting chipsets. " -#~ "Different systems (<quote>sub-architectures</quote>) often have radically " -#~ "different engineering and capabilities. Therefore, the process of " -#~ "installing and, more to the point, booting, can vary from system to " -#~ "system." -#~ msgstr "" -#~ "由于有很多世代的主板和支持芯片，Alpha 机器可以细分成不同的系统。不同的系统" -#~ "(<quote>子体系(sub-architectures)</quote>)通常具有完全不同的工程设计与运行" -#~ "效能。因此，安装过程，更准确地说是启动过程，会因系统不同而不同。" - -#~ msgid "" -#~ "The following table lists the system types supported by the Debian " -#~ "installation system. The table also indicates the <emphasis>code name</" -#~ "emphasis> for these system types. You'll need to know this code name when " -#~ "you actually begin the installation process:" -#~ msgstr "" -#~ "以下表格中列出 Debian 安装系统所支持的系统类型。表格中还指出这些系统类型" -#~ "的 <emphasis>代号(code name)</emphasis>。当开始安装时，您需要知道这些代" -#~ "号。" - -#~ msgid "Hardware Type" -#~ msgstr "硬件类型" - -#~ msgid "Aliases" -#~ msgstr "别名" - -#~ msgid "MILO image" -#~ msgstr "MILO image" - -#~ msgid "ALCOR" -#~ msgstr "ALCOR" - -#~ msgid "AlphaStation 500 5/266.300" -#~ msgstr "AlphaStation 500 5/266.300" - -#~ msgid "Maverick" -#~ msgstr "Maverick" - -# index.docbook:267, index.docbook:271, index.docbook:275 -#~ msgid "alcor" -#~ msgstr "alcor" - -#~ msgid "AlphaStation 500 5/333...500" -#~ msgstr "AlphaStation 500 5/333...500" - -#~ msgid "Bret" -#~ msgstr "Bret" - -#~ msgid "AlphaStation 600/266...300" -#~ msgstr "AlphaStation 600/266...300" - -#~ msgid "Alcor" -#~ msgstr "Alcor" - -#~ msgid "AlphaStation 600/300...433" -#~ msgstr "AlphaStation 600/300...433" - -#~ msgid "<entry>XLT</entry>" -#~ msgstr "<entry>XLT</entry>" - -#~ msgid "<entry>xlt</entry>" -#~ msgstr "<entry>xlt</entry>" - -#~ msgid "BOOK1" -#~ msgstr "BOOK1" - -#~ msgid "AlphaBook1 (laptop)" -#~ msgstr "AlphaBook1 (laptop)" - -#~ msgid "Alphabook1/Burns" -#~ msgstr "Alphabook1/Burns" - -#~ msgid "book1" -#~ msgstr "book1" - -#~ msgid "AVANTI" -#~ msgstr "AVANTI" - -#~ msgid "AlphaStation 200 4/100...166" -#~ msgstr "AlphaStation 200 4/100...166" - -#~ msgid "Mustang" -#~ msgstr "Mustang" - -# index.docbook:293, index.docbook:297, index.docbook:301, index.docbook:305, index.docbook:309, index.docbook:313, index.docbook:317, index.docbook:321 -#~ msgid "avanti" -#~ msgstr "avanti" - -#~ msgid "AlphaStation 200 4/233" -#~ msgstr "AlphaStation 200 4/233" - -#~ msgid "Mustang+" -#~ msgstr "Mustang+" - -#~ msgid "AlphaStation 205 4/133...333" -#~ msgstr "AlphaStation 205 4/133...333" - -#~ msgid "<entry>LX3</entry>" -#~ msgstr "<entry>LX3</entry>" - -#~ msgid "AlphaStation 250 4/300" -#~ msgstr "AlphaStation 250 4/300" - -#~ msgid "<entry>M3+</entry>" -#~ msgstr "<entry>M3+</entry>" - -#~ msgid "AlphaStation 255 4/133...333" -#~ msgstr "AlphaStation 255 4/133...333" - -#~ msgid "LX3+" -#~ msgstr "LX3+" - -#~ msgid "AlphaStation 300 4/266" -#~ msgstr "AlphaStation 300 4/266" - -#~ msgid "Melmac" -#~ msgstr "Melmac" - -#~ msgid "AlphaStation 400 4/166" -#~ msgstr "AlphaStation 400 4/166" - -#~ msgid "Chinet" -#~ msgstr "Chinet" - -#~ msgid "AlphaStation 400 4/233...300" -#~ msgstr "AlphaStation 400 4/233...300" - -#~ msgid "Avanti" -#~ msgstr "Avanti" - -# index.docbook:325, index.docbook:338, index.docbook:339 -#~ msgid "EB164" -#~ msgstr "EB164" - -#~ msgid "AlphaPC164" -#~ msgstr "AlphaPC164" - -#~ msgid "PC164" -#~ msgstr "PC164" - -#~ msgid "pc164" -#~ msgstr "pc164" - -#~ msgid "AlphaPC164-LX" -#~ msgstr "AlphaPC164-LX" - -#~ msgid "LX164" -#~ msgstr "LX164" - -#~ msgid "lx164" -#~ msgstr "lx164" - -#~ msgid "AlphaPC164-SX" -#~ msgstr "AlphaPC164-SX" - -#~ msgid "SX164" -#~ msgstr "SX164" - -#~ msgid "sx164" -#~ msgstr "sx164" - -#~ msgid "eb164" -#~ msgstr "eb164" - -# index.docbook:344, index.docbook:353, index.docbook:354 -#~ msgid "EB64+" -#~ msgstr "EB64+" - -#~ msgid "AlphaPC64" -#~ msgstr "AlphaPC64" - -# index.docbook:346, index.docbook:350 -#~ msgid "Cabriolet" -#~ msgstr "Cabriolet" - -# index.docbook:347, index.docbook:351 -#~ msgid "cabriolet" -#~ msgstr "cabriolet" - -#~ msgid "AlphaPCI64" -#~ msgstr "AlphaPCI64" - -#~ msgid "eb64p" -#~ msgstr "eb64p" - -# index.docbook:359, index.docbook:360, index.docbook:361 -#~ msgid "EB66" -#~ msgstr "EB66" - -#~ msgid "eb66" -#~ msgstr "eb66" - -# index.docbook:364, index.docbook:365 -#~ msgid "EB66+" -#~ msgstr "EB66+" - -#~ msgid "eb66p" -#~ msgstr "eb66p" - -#~ msgid "JENSEN" -#~ msgstr "JENSEN" - -#~ msgid "DEC 2000 Model 300(S)" -#~ msgstr "DEC 2000 Model 300(S)" - -# index.docbook:372, index.docbook:380 -#~ msgid "Jensen" -#~ msgstr "Jensen" - -# index.docbook:373, index.docbook:377, index.docbook:381, index.docbook:442, index.docbook:446, index.docbook:464, index.docbook:468, index.docbook:472, index.docbook:476, index.docbook:480, index.docbook:484, index.docbook:488, index.docbook:502, index.docbook:506, index.docbook:510, index.docbook:514, index.docbook:518, index.docbook:552, index.docbook:556, index.docbook:560, index.docbook:564, index.docbook:578, index.docbook:582, index.docbook:586, index.docbook:590, index.docbook:597, index.docbook:601, index.docbook:605, index.docbook:609, index.docbook:613, index.docbook:617, index.docbook:621, index.docbook:625, index.docbook:629, index.docbook:633, index.docbook:637, index.docbook:641, index.docbook:645, index.docbook:652, index.docbook:656 -#~ msgid "<entry>N/A</entry>" -#~ msgstr "<entry>N/A</entry>" - -#~ msgid "DEC 2000 Model 500" -#~ msgstr "DEC 2000 Model 500" - -#~ msgid "Culzen" -#~ msgstr "Culzen" - -#~ msgid "DECpc 150" -#~ msgstr "DECpc 150" - -#~ msgid "MIATA" -#~ msgstr "MIATA" - -#~ msgid "Personal WorkStation 433a" -#~ msgstr "Personal WorkStation 433a" - -# index.docbook:387, index.docbook:391, index.docbook:395, index.docbook:399, index.docbook:403, index.docbook:407, index.docbook:411, index.docbook:415 -#~ msgid "Miata" -#~ msgstr "Miata" - -# index.docbook:388, index.docbook:392, index.docbook:396, index.docbook:400, index.docbook:404, index.docbook:408, index.docbook:412, index.docbook:416 -#~ msgid "miata" -#~ msgstr "miata" - -#~ msgid "Personal WorkStation 433au" -#~ msgstr "Personal WorkStation 433au" - -#~ msgid "Personal WorkStation 466au" -#~ msgstr "Personal WorkStation 466au" - -#~ msgid "Personal WorkStation 500a" -#~ msgstr "Personal WorkStation 500a" - -#~ msgid "Personal WorkStation 500au" -#~ msgstr "Personal WorkStation 500au" - -#~ msgid "Personal WorkStation 550au" -#~ msgstr "Personal WorkStation 550au" - -#~ msgid "Personal WorkStation 600a" -#~ msgstr "Personal WorkStation 600a" - -#~ msgid "Personal WorkStation 600au" -#~ msgstr "Personal WorkStation 600au" - -#~ msgid "MIKASA" -#~ msgstr "MIKASA" - -#~ msgid "AlphaServer 1000 4/200" -#~ msgstr "AlphaServer 1000 4/200" - -#~ msgid "Mikasa" -#~ msgstr "Mikasa" - -# index.docbook:423, index.docbook:427, index.docbook:431, index.docbook:435 -#~ msgid "mikasa" -#~ msgstr "mikasa" - -#~ msgid "AlphaServer 1000 4/233..266" -#~ msgstr "AlphaServer 1000 4/233..266" - -#~ msgid "Mikasa+" -#~ msgstr "Mikasa+" - -# index.docbook:429, index.docbook:433 -#~ msgid "AlphaServer 1000 5/300" -#~ msgstr "AlphaServer 1000 5/300" - -#~ msgid "Mikasa-Pinnacle" -#~ msgstr "Mikasa-Pinnacle" - -#~ msgid "Mikasa-Primo" -#~ msgstr "Mikasa-Primo" - -#~ msgid "NAUTILUS" -#~ msgstr "NAUTILUS" - -#~ msgid "UP1000" -#~ msgstr "UP1000" - -#~ msgid "Nautilus" -#~ msgstr "Nautilus" - -#~ msgid "UP1100" -#~ msgstr "UP1100" - -#~ msgid "Galaxy-Train/Nautilus Jr." -#~ msgstr "Galaxy-Train/Nautilus Jr." - -#~ msgid "NONAME" -#~ msgstr "NONAME" - -#~ msgid "AXPpci33" -#~ msgstr "AXPpci33" - -#~ msgid "Noname" -#~ msgstr "Noname" - -# index.docbook:453, index.docbook:457 -#~ msgid "noname" -#~ msgstr "noname" - -#~ msgid "<entry>UDB</entry>" -#~ msgstr "<entry>UDB</entry>" - -#~ msgid "Multia" -#~ msgstr "Multia" - -#~ msgid "NORITAKE" -#~ msgstr "NORITAKE" - -#~ msgid "AlphaServer 1000A 4/233...266" -#~ msgstr "AlphaServer 1000A 4/233...266" - -#~ msgid "Noritake" -#~ msgstr "Noritake" - -#~ msgid "AlphaServer 1000A 5/300" -#~ msgstr "AlphaServer 1000A 5/300" - -#~ msgid "Noritake-Pinnacle" -#~ msgstr "Noritake-Pinnacle" - -#~ msgid "AlphaServer 1000A 5/333...500" -#~ msgstr "AlphaServer 1000A 5/333...500" - -#~ msgid "Noritake-Primo" -#~ msgstr "Noritake-Primo" - -#~ msgid "AlphaServer 800 5/333...500" -#~ msgstr "AlphaServer 800 5/333...500" - -# index.docbook:475, index.docbook:483, index.docbook:487 -#~ msgid "Corelle" -#~ msgstr "Corelle" - -#~ msgid "AlphaStation 600 A" -#~ msgstr "AlphaStation 600 A" - -#~ msgid "Alcor-Primo" -#~ msgstr "Alcor-Primo" - -#~ msgid "Digital Server 3300" -#~ msgstr "Digital Server 3300" - -#~ msgid "Digital Server 3300R" -#~ msgstr "Digital Server 3300R" - -#~ msgid "PLATFORM 2000" -#~ msgstr "PLATFORM 2000" - -# index.docbook:493, index.docbook:494 -#~ msgid "<entry>P2K</entry>" -#~ msgstr "<entry>P2K</entry>" - -#~ msgid "<entry>p2k</entry>" -#~ msgstr "<entry>p2k</entry>" - -#~ msgid "RAWHIDE" -#~ msgstr "RAWHIDE" - -#~ msgid "AlphaServer 1200 5/xxx" -#~ msgstr "AlphaServer 1200 5/xxx" - -# index.docbook:501, index.docbook:513 -#~ msgid "Tincup/DaVinci" -#~ msgstr "Tincup/DaVinci" - -#~ msgid "AlphaServer 4000 5/xxx" -#~ msgstr "AlphaServer 4000 5/xxx" - -#~ msgid "Wrangler/Durango" -#~ msgstr "Wrangler/Durango" - -#~ msgid "AlphaServer 4100 5/xxx" -#~ msgstr "AlphaServer 4100 5/xxx" - -# index.docbook:509, index.docbook:517 -#~ msgid "Dodge" -#~ msgstr "Dodge" - -#~ msgid "Digital Server 5300" -#~ msgstr "Digital Server 5300" - -#~ msgid "Digital Server 7300" -#~ msgstr "Digital Server 7300" - -#~ msgid "RUFFIAN" -#~ msgstr "RUFFIAN" - -#~ msgid "DeskStation AlphaPC164-UX" -#~ msgstr "DeskStation AlphaPC164-UX" - -# index.docbook:524, index.docbook:528, index.docbook:532, index.docbook:536, index.docbook:540, index.docbook:544 -#~ msgid "Ruffian" -#~ msgstr "Ruffian" - -# index.docbook:525, index.docbook:529, index.docbook:533, index.docbook:537, index.docbook:541, index.docbook:545 -#~ msgid "ruffian" -#~ msgstr "ruffian" - -#~ msgid "DeskStation RPL164-2" -#~ msgstr "DeskStation RPL164-2" - -#~ msgid "DeskStation RPL164-4" -#~ msgstr "DeskStation RPL164-4" - -#~ msgid "DeskStation RPX164-2" -#~ msgstr "DeskStation RPX164-2" - -#~ msgid "DeskStation RPX164-4" -#~ msgstr "DeskStation RPX164-4" - -#~ msgid "Samsung AlphaPC164-BX" -#~ msgstr "Samsung AlphaPC164-BX" - -#~ msgid "SABLE" -#~ msgstr "SABLE" - -#~ msgid "AlphaServer 2000 4/xxx" -#~ msgstr "AlphaServer 2000 4/xxx" - -#~ msgid "Demi-Sable" -#~ msgstr "Demi-Sable" - -#~ msgid "AlphaServer 2000 5/xxx" -#~ msgstr "AlphaServer 2000 5/xxx" - -#~ msgid "Demi-Gamma-Sable" -#~ msgstr "Demi-Gamma-Sable" - -#~ msgid "AlphaServer 2100 4/xxx" -#~ msgstr "AlphaServer 2100 4/xxx" - -#~ msgid "Sable" -#~ msgstr "Sable" - -#~ msgid "AlphaServer 2100 5/xxx" -#~ msgstr "AlphaServer 2100 5/xxx" - -#~ msgid "Gamma-Sable" -#~ msgstr "Gamma-Sable" - -#~ msgid "TAKARA" -#~ msgstr "TAKARA" - -#~ msgid "21164 PICMG SBC" -#~ msgstr "21164 PICMG SBC" - -#~ msgid "Takara" -#~ msgstr "Takara" - -#~ msgid "takara" -#~ msgstr "takara" - -#~ msgid "TITAN" -#~ msgstr "TITAN" - -#~ msgid "AlphaServer DS15" -#~ msgstr "AlphaServer DS15" - -#~ msgid "HyperBrick2" -#~ msgstr "HyperBrick2" - -#~ msgid "AlphaServer DS25" -#~ msgstr "AlphaServer DS25" - -#~ msgid "Granite" -#~ msgstr "Granite" - -#~ msgid "AlphaServer ES45" -#~ msgstr "AlphaServer ES45" - -#~ msgid "Privateer" -#~ msgstr "Privateer" - -# index.docbook:588, index.docbook:627, index.docbook:631 -#~ msgid "UNKNOWN" -#~ msgstr "UNKNOWN" - -#~ msgid "Yukon" -#~ msgstr "Yukon" - -#~ msgid "TSUNAMI" -#~ msgstr "TSUNAMI" - -#~ msgid "AlphaServer DS10" -#~ msgstr "AlphaServer DS10" - -# index.docbook:596, index.docbook:644 -#~ msgid "Webbrick" -#~ msgstr "Webbrick" - -#~ msgid "AlphaServer DS10L" -#~ msgstr "AlphaServer DS10L" - -#~ msgid "Slate" -#~ msgstr "Slate" - -#~ msgid "AlphaServer DS20" -#~ msgstr "AlphaServer DS20" - -#~ msgid "Catamaran/Goldrush" -#~ msgstr "Catamaran/Goldrush" - -#~ msgid "AlphaServer DS20E" -#~ msgstr "AlphaServer DS20E" - -#~ msgid "Goldrack" -#~ msgstr "Goldrack" - -#~ msgid "AlphaServer DS20L" -#~ msgstr "AlphaServer DS20L" - -#~ msgid "Shark" -#~ msgstr "Shark" - -#~ msgid "AlphaServer ES40" -#~ msgstr "AlphaServer ES40" - -#~ msgid "Clipper" -#~ msgstr "Clipper" - -# index.docbook:619, index.docbook:620 -#~ msgid "DP264" -#~ msgstr "DP264" - -#~ msgid "SMARTengine 21264 PCI/ISA SBC" -#~ msgstr "SMARTengine 21264 PCI/ISA SBC" - -#~ msgid "Eiger" -#~ msgstr "Eiger" - -#~ msgid "Warhol" -#~ msgstr "Warhol" - -#~ msgid "Windjammer" -#~ msgstr "Windjammer" - -#~ msgid "UP2000" -#~ msgstr "UP2000" - -#~ msgid "Swordfish" -#~ msgstr "Swordfish" - -#~ msgid "XP1000" -#~ msgstr "XP1000" - -#~ msgid "Monet/Brisbane" -#~ msgstr "Monet/Brisbane" - -#~ msgid "XP900" -#~ msgstr "XP900" - -#~ msgid "WILDFIRE" -#~ msgstr "WILDFIRE" - -#~ msgid "AlphaServer GS160" -#~ msgstr "AlphaServer GS160" - -# index.docbook:651, index.docbook:655 -#~ msgid "Wildfire" -#~ msgstr "Wildfire" - -#~ msgid "AlphaServer GS320" -#~ msgstr "AlphaServer GS320" - -# index.docbook:660, index.docbook:662 -#~ msgid "<entry>XL</entry>" -#~ msgstr "<entry>XL</entry>" - -#~ msgid "XL-233...266" -#~ msgstr "XL-233...266" - -#~ msgid "<entry>xl</entry>" -#~ msgstr "<entry>xl</entry>" - -#~ msgid "" -#~ "It is believed that Debian &releasename; supports installing on all alpha " -#~ "sub-architectures with the exception of the ARC-only Ruffian and XL sub-" -#~ "architectures and the Titan subarchitecture, which requires a change to " -#~ "the kernel compile options." -#~ msgstr "" -#~ "除了需要修改内核编译选项的 ARC-only Ruffian、XL sub-architectures，以及 " -#~ "Titan 子体系之外，Debian &releasename; 支持安装到所有的 alpha 子体系上。" - -#~ msgid "" -#~ "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as " -#~ "the controller is supported by the SRM console. This rules out many add-" -#~ "on controller cards, but most integrated IDE and SCSI chips and " -#~ "controller cards that were provided by the manufacturer can be expected " -#~ "to work. To find out whether your device is supported from the SRM " -#~ "console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." -#~ msgstr "" -#~ "只要 SRM 控制台能支持相应的控制器，&arch-title; 上的 SCSI 和 IDE/ATAPI CD-" -#~ "ROM 就能获得支持。这将会把许多附加的控制卡排除在外，但是大多数由制造商提供" -#~ "的集成 IDE 和 SCSI 芯片以及控制卡都应该能够工作。要想知道您的设备是否被 " -#~ "SRM 控制台支持，请参阅 <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>。" - -#~ msgid "" -#~ "Any storage system supported by the Linux kernel is also supported by the " -#~ "boot system. This includes both SCSI and IDE disks. Note, however, that " -#~ "on many systems, the SRM console is unable to boot from IDE drives, and " -#~ "the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-" -#~ "howto;\"></ulink> for more information on booting the Jensen)" -#~ msgstr "" -#~ "所有 Linux 内核支持的存储系统也都被启动系统所支持。这包括 SCSI 和 IDE 磁" -#~ "盘。注意，在许多系统上，SRM 控制台不能从 IDE 驱动器上启动，并且 Jensen 不" -#~ "能从软盘上启动。(请参考 <ulink url=\"&url-jensen-howto;\"></ulink> 以了解" -#~ "更多关于从 Jensen 启动的信息)" - -#~ msgid "Motorola 680x0" -#~ msgstr "Motorola 680x0" - -#~ msgid "m68k" -#~ msgstr "m68k" - -#~ msgid "Atari" -#~ msgstr "Atari" - -#~ msgid "atari" -#~ msgstr "atari" - -#~ msgid "Amiga" -#~ msgstr "Amiga" - -#~ msgid "amiga" -#~ msgstr "amiga" - -#~ msgid "68k Macintosh" -#~ msgstr "68k Macintosh" - -#~ msgid "<entry>mac</entry>" -#~ msgstr "<entry>mac</entry>" - -#~ msgid "<entry>VME</entry>" -#~ msgstr "<entry>VME</entry>" - -#~ msgid "bvme6000" -#~ msgstr "bvme6000" - -#~ msgid "mvme147" -#~ msgstr "mvme147" - -#~ msgid "mvme16x" -#~ msgstr "mvme16x" - -#~ msgid "" -#~ "Complete information concerning supported M68000 based " -#~ "(<emphasis>&architecture;</emphasis>) systems can be found at the <ulink " -#~ "url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely " -#~ "outlines the basics." -#~ msgstr "" -#~ "有关支持基于 M68000 (<emphasis>&architecture;</emphasis>完整的信息见 " -#~ "<ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>。本节只是基本概况。" - -#~ msgid "" -#~ "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged " -#~ "Memory Management Unit) and a FPU (floating-point unit). This includes " -#~ "the 68020 with an external 68851 PMMU, the 68030, and better, and " -#~ "excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink " -#~ "url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details." -#~ msgstr "" -#~ "&architecture; 移植的 Linux 可以运行在具有 PMMU (Paged Memory Management " -#~ "Unit) 和 FPU (floating-point unit) 的任何 680x0 上面。这包括带有外部 " -#~ "68851 PMMU 的 68020、68030，以及其它更好的处理器，不包括 <quote>EC</" -#~ "quote> 系列的 680x0 处理器。请参考 <ulink url=\"&url-m68k-faq;\">Linux/" -#~ "m68k FAQ</ulink> 以了解更多信息。" - -#~ msgid "" -#~ "There are four major supported <emphasis>&architecture;</emphasis> " -#~ "flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were " -#~ "the first two systems to which Linux was ported; in keeping, they are " -#~ "also the two most well-supported Debian ports. The Macintosh line is " -#~ "supported incompletely, both by Debian and by the Linux kernel; see " -#~ "<ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for " -#~ "project status and supported hardware. The BVM and Motorola single board " -#~ "VMEbus computers are the most recent addition to the list of machines " -#~ "supported by Debian. Ports to other &architecture; architectures, such as " -#~ "the Sun3 architecture and NeXT black box, are underway but not yet " -#~ "supported by Debian." -#~ msgstr "" -#~ "一共有四个主要的 <emphasis>&architecture;</emphasis> 变种获得支持：Amiga、" -#~ "Atari、Macintosh 和 VME 机器。Amiga 与 Atari 是首批移植 Linux 的两个系统；" -#~ "并且，它们也是被 Debian 移植得最好的两个。Debian 与 Linux 内核对 " -#~ "Macintosh 系列的支持都是不完整的，请参考 <ulink url=\"&url-m68k-mac;" -#~ "\">Linux m68k for Macintosh</ulink> 以了解项目的状态和支持的硬件。BVM 和 " -#~ "Motorola VMEbus 单板电脑最近才加入 Debian 支持行列。移植到其它的 " -#~ "&architecture; 体系的工作，比如 Sun3 体系与 NeXT black box，还在进行中，且" -#~ "没有被 Debian 支持。" - -#~ msgid "" -#~ "Unfortunately, it's quite rare to find any vendor shipping new &arch-" -#~ "title; machines at all." -#~ msgstr "不幸的是，很少会有厂商出售新 &arch-title; 机器。" - -#~ msgid "" -#~ "Another example is the proprietary hardware in the older Macintosh line. " -#~ "In fact, no specifications or documentation have ever been released for " -#~ "any Macintosh hardware, most notably the ADB controller (used by the " -#~ "mouse and keyboard), the floppy controller, and all acceleration and CLUT " -#~ "manipulation of the video hardware (though we do now support CLUT " -#~ "manipulation on nearly all internal video chips). In a nutshell, this " -#~ "explains why the Macintosh Linux port lags behind other Linux ports." -#~ msgstr "" -#~ "另一个例子是老式 Macintosh 产品系列的专有硬件。事实上，Macintosh 硬件没有" -#~ "公布任何规格书与文档，特别是 ADB 控制器(用于鼠标和键盘)、软盘控制器、所有" -#~ "的视频硬件加速和 CLUT 处理器(虽然我们不支持绝大多数内置显示芯片的 CLUT 处" -#~ "理器)。总之，这就是为什么向 Macintosh 移植 Linux 的进度总是滞后于其他移植" -#~ "版的原因。" - -#~ msgid "" -#~ "In fact, installation from your local disk is the preferred installation " -#~ "technique for most &architecture; machines." -#~ msgstr "事实上，从本地磁盘安装，对大多数 &architecture; 机器是推荐的做法。" - -#~ msgid "" -#~ "Pretty much all storage systems supported by the Linux kernel are " -#~ "supported by the Debian installation system. Note that the current Linux " -#~ "kernel does not support floppies on the Macintosh at all, and the Debian " -#~ "installation system doesn't support floppies for Amigas. Also supported " -#~ "on the Atari is the Macintosh HFS system, and AFFS as a module. Macs " -#~ "support the Atari (FAT) file system. Amigas support the FAT file system, " -#~ "and HFS as a module." -#~ msgstr "" -#~ "基本上所有 Linux 内核支持的存储系统都被 Debian 安装系统所支持。注意，当前" -#~ "的 Linux 内核仍不支持 Macintosh 上的软盘，并且 Debian 安装系统也不支持 " -#~ "Amigas 上 的软盘。支持 Atari 上的 Macintosh HFS 系统，并以模块形式支持 " -#~ "AFFS。Mac 机支持 Atari(FAT) 文件系统。Amigas 支持 FAT 文件系统，HFS 则是受" -#~ "模块支持。" - -#~ msgid "" -#~ "On the Amiga the size of FastRAM is relevant towards the total memory " -#~ "requirements. Also, using Zorro cards with 16-bit RAM is not supported; " -#~ "you'll need 32-bit RAM. The <command>amiboot</command> program can be " -#~ "used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/" -#~ "m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically." -#~ msgstr "" -#~ "在 Amiga 上，FastRAM 的大小与总的内存需求相关联。而且，使用 16 位的 Zorro " -#~ "RAM 卡不 被支持，您要用32位的。<command>amiboot</command> 程序可以被用来禁" -#~ "止 16 位 RAM，请参考 <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</" -#~ "ulink>。最近的内核可以自动禁止 16 位的 RAM。" - -#~ msgid "" -#~ "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many " -#~ "users have reported problems running the kernel itself in Fast RAM, so " -#~ "the Atari bootstrap will place the kernel in ST-RAM. The minimum " -#~ "requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more " -#~ "of TT-RAM." -#~ msgstr "" -#~ "在 Atari 上，ST-RAM 和 Fast RAM (TT-RAM) 都可以被 Linux 所使用。许多用户报" -#~ "告在 Fast RAM 上运行内核有问题，因此 Atari 启动将内核放在 ST-RAM。最小需" -#~ "要 2 MB 的 ST-RAM。您需要额外的 12 MB 或更多的 TT-RAM。" - -#~ msgid "" -#~ "On the Macintosh, care should be taken on machines with RAM-based video " -#~ "(RBV). The RAM segment at physical address 0 is used as screen memory, " -#~ "making the default load position for the kernel unavailable. The " -#~ "alternate RAM segment used for kernel and RAMdisk must be at least 4 MB." -#~ msgstr "" -#~ "在 Macintosh 上，需要注意 RAM-based video (RBV)。物理地址 0 的 RAM 段用于" -#~ "显示内存，使得默认的内核引导位置无效。替代的用于内核的 RAM 段与 RAMdisk 至" -#~ "少 需要 4 MB。" - -#~ msgid "FIXME: is this still true?" -#~ msgstr "FIXME: is this still true?" diff --git a/po/zh_CN/install-methods.po b/po/zh_CN/install-methods.po index 783f7972a..457495272 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: 2009-11-18 01:11+0000\n" -"PO-Revision-Date: 2009-08-01 14:31+0800\n" +"PO-Revision-Date: 2009-11-21 12:42+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" @@ -255,14 +255,14 @@ msgid "" "the installation files for QNAP TS-109 and TS-209 from &qnap-orion-firmware-" "img; and for QNAP TS-110, TS-119, TS-210, TS-219, TS-219P from &qnap-" "kirkwood-firmware-img;." -msgstr "" +msgstr "QNAP Turbo Station 安装文件包括内核和 ramdisk 以及将这些映象写入 flash 的脚本。您可以从 &qnap-orion-firmware-img; 获得 QNAP TS-109 和 TS-209 的安装文件。从 &qnap-kirkwood-firmware-img; 获得 QNAP TS-110, TS-119, TS-210, TS-219, TS-219P 的。" #. Tag: title #: install-methods.xml:186 -#, fuzzy, no-c-format +#, no-c-format #| msgid "Alpha Installation Files" msgid "SheevaPlug and OpenRD Installation Files" -msgstr "Alpha 的安装文件" +msgstr "SheevaPlug 和 OpenRD 安装文件" #. Tag: para #: install-methods.xml:187 @@ -271,7 +271,7 @@ msgid "" "The installation files for the Marvell SheevaPlug and OpenRD devices consist " "of a kernel and initrd for U-Boot. You can obtain these files from &kirkwood-" "marvell-firmware-img;." -msgstr "" +msgstr "Marvell SheevaPlug 和 OpenRD 设备的安装文件包括内核和 initrd 用于 U-Boot。您可以从 &kirkwood-marvell-firmware-img; 获得这些文件。" #. Tag: title #: install-methods.xml:237 @@ -904,7 +904,7 @@ msgstr "我们将展示如何使用 U 盘的第一个分区，而不是整个设 #. Tag: para #: install-methods.xml:670 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "Since most USB sticks come pre-configured with a single FAT16 partition, " #| "you probably won't have to repartition or reformat the stick. If you have " @@ -927,13 +927,9 @@ msgid "" "for your USB stick. The <command>mkdosfs</command> command is contained in " "the <classname>dosfstools</classname> Debian package." msgstr "" -"由于大多数 U 盘预先设置了一个单独的 FAT16 分区，您可能不需要重新分区或者格式" -"化 U 盘。如果必须要做，请使用 <command>cfdisk</command> 或者其他的分区工具来" -"创建一个 FAT16 分区，然后建立文件系统：<informalexample><screen>\n" +"由于大多数 U 盘预先设置了一个单独的 FAT16 分区，您可能不需要重新分区或者格式化 U 盘。如果必须要做，请使用 <command>cfdisk</command> 或者其他的分区工具来创建一个 FAT16 分区<footnote> <para> 别忘记设置 <quote>bootable</quote> 引导标记。</para> </footnote>，然后建立文件系统：<informalexample><screen>\n" "# mkdosfs /dev/<replaceable>sdX1</replaceable>\n" -"</screen></informalexample> 注意，请使用正确的 U 盘设备名称。" -"<command>mkdosfs</command> 命令包含在 Debian 的 <classname>dosfstools</" -"classname> 软件包中。" +"</screen></informalexample> 注意，请使用 U 盘正确的设备名称。<command>mkdosfs</command> 命令包含在 Debian 的 <classname>dosfstools</classname> 软件包中。" #. Tag: para #: install-methods.xml:689 @@ -983,7 +979,7 @@ msgstr "添加安装程序映像" #. Tag: para #: install-methods.xml:717 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</" #| "replaceable> /mnt</userinput>) and copy the following installer image " @@ -1006,18 +1002,11 @@ msgid "" "in the <filename>gtk</filename> subdirectory. If you want to rename the " "files, please note that <classname>syslinux</classname> can only process DOS " "(8.3) file names." -msgstr "" -"挂载分区 (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</" -"userinput>) 并复制下面的安装程序映象文件到 U 盘：<itemizedlist> " -"<listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></" -"listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk " -"image) </para></listitem> </itemizedlist> 您可以选择使用文本界面或者图形安装" -"界面安装程序。后者可以从 <filename>gtk</filename> 子目录获得。假如您需要改文" -"件名，请注意 <classname>syslinux</classname> 只遵循 DOS (8.3) 命名方式。" +msgstr "挂载分区(<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>)并复制下列安装程序映象文件到 U 盘：<itemizedlist> <listitem><para> <filename>vmlinuz</filename> 或 <filename>linux</filename> (内核二进制文件) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (初始化 ramdisk 映象) </para></listitem> </itemizedlist> 你可以选择使用安装程序的文本或者图形界面。后者放在 <filename>gtk</filename> 子目录下面。如果需要改文件名，请注意 <classname>syslinux</classname> 只能处理 DOS (8.3) 文件名。" #. Tag: para #: install-methods.xml:741 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "Next you should create a <filename>syslinux.cfg</filename> configuration " #| "file, which at a bare minimum should contain the following two lines: " @@ -1037,16 +1026,14 @@ msgid "" "</screen></informalexample> For the graphical installer you should add " "<userinput>video=vesa:ywrap,mtrr vga=788</userinput> to the second line." msgstr "" -"接下来，您需要创建一个 <filename>syslinux.cfg</filename> 配置文件，里面最少要" -"包含下面两行： <informalexample><screen>\n" +"接下来，您需要创建一个 <filename>syslinux.cfg</filename> 配置文件，里面最少要包含下面两行(如果您使用 <filename>netboot</filename> 映象，修改内核文件名为 <quote><filename>linux</filename></quote> )：<informalexample><screen>\n" "default vmlinuz\n" "append initrd=initrd.gz\n" -"</screen></informalexample> 对于图形安装程序，您需要添加 " -"<userinput>video=vesa:ywrap,mtrr vga=788</userinput> 到第二行尾部。" +"</screen></informalexample> 对于图形安装程序，您需要添加 <userinput>video=vesa:ywrap,mtrr vga=788</userinput> 到第二行尾部。" #. Tag: para #: install-methods.xml:753 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "If you used an <filename>hd-media</filename> image, you should now copy a " #| "Debian ISO image (businesscard, netinst or full CD image; be sure to " @@ -1060,10 +1047,7 @@ msgid "" "filename></quote> image is not usable for this purpose. </para> </footnote> " "onto the stick. When you are done, unmount the USB memory stick " "(<userinput>umount /mnt</userinput>)." -msgstr "" -"如果您使用 <filename>hd-media</filename> 映象，现在应该复制 Debian ISO 映象" -"(businesscard、netinst 或者完整的 CD 映象；确认适合的一种)到 U 盘上。然后，卸" -"载 U 盘 (<userinput>umount /mnt</userinput>)。" +msgstr "如果您使用 <filename>hd-media</filename> 映象，现在应该复制 Debian ISO 映象<footnote> <para> 您可以使用 businesscard、netinst 或完整的 CD 映象 (参阅 <xref linkend=\"official-cdrom\"/>)。确认选择合适的映象。注意 <quote>netboot <filename>mini.iso</filename></quote> 映象并不用在这里。</para> </footnote> 到 U 盘上。然后卸载 U 盘(<userinput>umount /mnt</userinput>)。" #. Tag: para #: install-methods.xml:777 @@ -2225,168 +2209,3 @@ msgid "" msgstr "" "在 <xref linkend=\"appendix-preseed\"/> 是有关预置文件的完整文档，并有一些可" "以使用的例子供您修改。" - -#~ msgid "" -#~ "The QNAP Turbo Station (TS-109, TS-209 and TS-409) requires a kernel and " -#~ "ramdisk which can be obtained from &qnap-orion-firmware-img;. A script is " -#~ "provided to write these images to flash." -#~ msgstr "" -#~ "QNAP Turbo Station (TS-109, TS-209 和 TS-409) 需要内核和 ramdisk，这些可" -#~ "从 &qnap-orion-firmware-img; 获得。有一个脚本用于将这些映象写到 flash 里" -#~ "面。" - -#~ msgid "" -#~ "If you choose to boot from ARC console firmware using <command>MILO</" -#~ "command>, you will also need to prepare a disk containing <command>MILO</" -#~ "command> and <command>LINLOAD.EXE</command> from the provided disk " -#~ "images. See <xref linkend=\"alpha-firmware\"/> for more information on " -#~ "Alpha firmware and boot loaders. The floppy images can be found in the " -#~ "<filename>MILO</filename> directory as " -#~ "<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>." -#~ msgstr "" -#~ "如果您选择通过 <command>MILO</command> 来从 ARC 控制台固件引导，就需要从所" -#~ "提供的磁盘映像中准备一张载有 <command>MILO</command> 和 <command>LINLOAD." -#~ "EXE</command> 的磁盘。有关 Alpha 固件和启动引导器的更多信息请参见 <xref " -#~ "linkend=\"alpha-firmware\"/> 。软盘映像可以在 <filename>MILO</filename> 目" -#~ "录下找到。其形式为： <filename>milo_<replaceable>subarchitecture</" -#~ "replaceable>.bin</filename>。" - -#~ msgid "" -#~ "Unfortunately, these <command>MILO</command> images could not be tested " -#~ "and might not work for all subarchitectures. If you find it doesn't work " -#~ "for you, try copying the appropriate <command>MILO</command> binary onto " -#~ "the floppy (<ulink url=\"&disturlftp;main/disks-alpha/current/MILO/\"></" -#~ "ulink>). Note that those <command>MILO</command>s don't support ext2 " -#~ "<quote>sparse superblocks</quote>, so you can't use them to load kernels " -#~ "from newly generated ext2 file systems. As a workaround, you can put your " -#~ "kernel onto the FAT partition next to the <command>MILO</command>." -#~ msgstr "" -#~ "抱歉的是，这些 <command>MILO</command> 映像文件未经过足够的测试，也许并不" -#~ "是在所有的子体系下都能正常运行。如果您发现它不能运行，请尝试将合适的 " -#~ "<command>MILO</command> 二进制文件拷贝到软盘中(<ulink url=\"&disturlftp;" -#~ "main/disks-alpha/current/MILO/\"></ulink>)。注意，这些 <command>MILO</" -#~ "command> 不支持 ext2 的<quote>sparse superblocks</quote>，因此您不能从新生" -#~ "成的 ext2 文件系统中装载内核。作为一个变通方法，您可以把内核放到 FAT 分区" -#~ "中，紧跟着 <command>MILO</command>。" - -#~ msgid "" -#~ "<command>MILO</command> binaries are platform-specific. See <xref linkend=" -#~ "\"alpha-cpus\"/> to determine the appropriate <command>MILO</command> " -#~ "image for your Alpha platform." -#~ msgstr "" -#~ "<command>MILO</command> 的二进制文件是依赖于具体平台的，请参见 <xref " -#~ "linkend=\"alpha-cpus\"/> 来确认哪一个 <command>MILO</command> 映象适用于您" -#~ "的 Alpha 平台。" - -#~ msgid "" -#~ "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM " -#~ "console will <emphasis>not</emphasis> use RARP to obtain its IP address, " -#~ "and therefore you must use BOOTP for net booting your Alpha<footnote> " -#~ "<para> Alpha systems can also be net-booted using the DECNet MOP " -#~ "(Maintenance Operations Protocol), but this is not covered here. " -#~ "Presumably, your local OpenVMS operator will be happy to assist you " -#~ "should you have some burning need to use MOP to boot Linux on your Alpha. " -#~ "</para> </footnote>. You can also enter the IP configuration for network " -#~ "interfaces directly in the SRM console." -#~ msgstr "" -#~ "不像 Sparc 和 PowerPC 机器上的 Open Firmware, SRM 控制台将 <emphasis>不</" -#~ "emphasis> 使用 RARP 来获得它的 IP 地址。因此您必须使用 BOOTP 来从网络启动" -#~ "您的 Alpha 机器<footnote> <para> Alpha 系统也可以通过 DECNet MOP " -#~ "(Maintenance Operations Protocol) 从网络启动，但在此不作阐述。在您急切需要" -#~ "使用 MOP 来启动 Alpha 系统上的 Linux 时，估计 OpenVMS 操作员很乐意帮您完" -#~ "成。 </para> </footnote>。您也可以直接在 SRM 控制台中直接输入网络接口的 " -#~ "IP 配置。" - -#~ msgid "Alpha TFTP Booting" -#~ msgstr "Alpha TFTP 引导" - -#~ msgid "" -#~ "On Alpha, you must specify the filename (as a relative path to the boot " -#~ "image directory) using the <userinput>-file</userinput> argument to the " -#~ "SRM <userinput>boot</userinput> command, or by setting the " -#~ "<userinput>BOOT_FILE</userinput> environment variable. Alternatively, the " -#~ "filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the " -#~ "<userinput>filename</userinput> directive). Unlike Open Firmware, there " -#~ "is <emphasis>no default filename</emphasis> on SRM, so you " -#~ "<emphasis>must</emphasis> specify a filename by either one of these " -#~ "methods." -#~ msgstr "" -#~ "在 Alpha 上，您必须通过 <userinput>-file</userinput> 参数将文件名(与启动引" -#~ "导映像目录的相对路径形式)指定给 SRM 的<userinput>boot</userinput> 命令，或" -#~ "者设置 <userinput>BOOT_FILE</userinput> 环境变量。或者，也可以通过 BOOTP " -#~ "给出文件名(在 ISC 的 <command>dhcpd</command> 中，使用 " -#~ "<userinput>filename</userinput> 指令)。与 Open Firmware 不同的是，这里的 " -#~ "SRM 中<emphasis>没有缺省文件名</emphasis>，因此您 <emphasis>必须</" -#~ "emphasis> 通过以上方法之一来指定一个文件名。" - -#~ msgid "Choosing a Kernel" -#~ msgstr "选择一个内核" - -#~ msgid "" -#~ "Some m68k subarchs have a choice of kernels to install. In general we " -#~ "recommend trying the most recent version first. If your subarch or " -#~ "machine needs to use a 2.2.x kernel, make sure you choose one of the " -#~ "images that supports 2.2.x kernels (see the <ulink url=\"&disturl;/main/" -#~ "installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>)." -#~ msgstr "" -#~ "一些 m68k 子体系可以选择要安装的内核。一般来说我们推荐您首先尝试最新的版" -#~ "本。如果您的子体系系统或机器需要使用 2.2.x 版的内核，请确认您选择的是一个" -#~ "支持对应内核的映像。(请参见 <ulink url=\"&disturl;/main/installer-" -#~ "&architecture;/current/images/MANIFEST\">MANIFEST</ulink>)。" - -#~ msgid "" -#~ "All of the m68k images for use with 2.2.x kernels, require the kernel " -#~ "parameter &ramdisksize;." -#~ msgstr "" -#~ "所有使用 2.2.x 内核的 m68k 的映像都要求使用 &ramdisksize; 内核参数。" - -#~ msgid "" -#~ "Booting the installer from floppy disk is not supported on Amigas or 68k " -#~ "Macs." -#~ msgstr "Amigas 或者 68k Macs 的安装程序软盘引导也不被支持。" - -#~ msgid "Writing Disk Images on Atari Systems" -#~ msgstr "在 Atari 系统上写磁盘映像" - -#~ msgid "" -#~ "You'll find the &rawwrite.ttp; program in the same directory as the " -#~ "floppy disk images. Start the program by double clicking on the program " -#~ "icon, and type in the name of the floppy image file you want written to " -#~ "the floppy at the TOS program command line dialog box." -#~ msgstr "" -#~ "您可以在与软盘映像相同的目录下找到 &rawwrite.ttp;。双击程序图标，在 TOS 程" -#~ "序 命令行输入框内键入您想写入软盘的软盘映像文件名。" - -#~ msgid "Writing Disk Images on Macintosh Systems" -#~ msgstr "在 Macintosh 系统上写磁盘映像" - -#~ msgid "" -#~ "Since the current release does not yet support booting from floppies to " -#~ "start the installation, there would be no point in doing this on " -#~ "Macintosh Systems. However, these files are needed for the installation " -#~ "of the operating system and modules, later in the process." -#~ msgstr "" -#~ "由于当前发布版不支持从软盘启动安装系统，因此在 Macintosh 系统上也没有相关" -#~ "内容。但是，这些文件被用在后面的安装过程中，用来安装操作系统和模块。" - -#~ msgid "BVM/Motorola TFTP Booting" -#~ msgstr "BVM/Motorola TFTP 引导" - -#~ msgid "" -#~ "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; " -#~ "to <filename>/tftpboot/</filename>." -#~ msgstr "" -#~ "对于 BVM 以及 Motorola VMEbus 系统来说，请先将 &bvme6000-tftp-files; 文件" -#~ "拷贝到 <filename>/tftpboot/</filename>。" - -#~ msgid "" -#~ "Next, configure your boot ROMs or BOOTP server to initially load the " -#~ "<filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> " -#~ "files from the TFTP server. Refer to the <filename>tftplilo.txt</" -#~ "filename> file for your subarchitecture for additional system-specific " -#~ "configuration information." -#~ msgstr "" -#~ "接下来，配置您的启动引导 ROM 或 BOOTP 服务器，使其从 TFTP 服务器中初始装" -#~ "入 <filename>tftplilo.bvme</filename> 或者 <filename>tftplilo.mvme</" -#~ "filename> 文件。请阅读 <filename>tftplilo.txt</filename> 文件来获得更多的" -#~ "关于您所使用的子体系的系统特殊配置信息。" diff --git a/po/zh_CN/partitioning.po b/po/zh_CN/partitioning.po index ed0a9bb90..edd6b33d5 100644 --- a/po/zh_CN/partitioning.po +++ b/po/zh_CN/partitioning.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: 2009-11-02 22:19+0000\n" -"PO-Revision-Date: 2008-10-23 10:41+0800\n" +"PO-Revision-Date: 2009-11-21 13:12+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" @@ -1453,103 +1453,3 @@ msgstr "" "这里建议第三个分区应该是 <quote>Whole disk</quote>(type 5)，并且包含整个磁盘 " "(从第一个柱面至最后一个)，这是 Sun 磁盘格式的惯例，并且确保 <command>SILO</" "command> 启动引导器工作良好。" - -#~ msgid "" -#~ "Booting Debian from the SRM console (the only disk boot method supported " -#~ "by &releasename;) requires you to have a BSD disk label, not a DOS " -#~ "partition table, on your boot disk. (Remember, the SRM boot block is " -#~ "incompatible with MS-DOS partition tables — see <xref linkend=" -#~ "\"alpha-firmware\"/>.) As a result, <command>partman</command> creates " -#~ "BSD disk labels when running on &architecture;, but if your disk has an " -#~ "existing DOS partition table the existing partitions will need to be " -#~ "deleted before <command>partman</command> can convert it to use a disk " -#~ "label." -#~ msgstr "" -#~ "从 SRM 控制台引导 Debian (惟一能被 &releasename; 支持的启动方法)要求您的启" -#~ "动盘上有 BSD disk label，而不是 DOS 分区。(注意，SRM 引导块不和 MS-DOS 分" -#~ "区兼容 — 参阅 <xref linkend=\"alpha-firmware\"/>。)因此，" -#~ "<command>partman</command> 在 &architecture; 上运行时会创建 BSD disk " -#~ "label，如果您的磁盘上已经存在一个 DOS 分区表，在 partman 转换到 disk " -#~ "label 前需要将它删除。" - -#~ msgid "" -#~ "If you have chosen to use <command>fdisk</command> to partition your " -#~ "disk, and the disk that you have selected for partitioning does not " -#~ "already contain a BSD disk label, you must use the <quote>b</quote> " -#~ "command to enter disk label mode." -#~ msgstr "" -#~ "如果您选择使用 <command>fdisk</command> 为您的磁盘分区，并且该磁盘上没有 " -#~ "BSD 磁盘卷标，您必须使用<quote>b</quote>命令进入磁盘卷标模式。" - -#~ msgid "" -#~ "Unless you wish to use the disk you are partitioning from Tru64 Unix or " -#~ "one of the free 4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, " -#~ "or NetBSD), you should <emphasis>not</emphasis> create the third " -#~ "partition as a <quote>whole disk</quote> partition (i.e. with start and " -#~ "end sectors to span the whole disk), as this renders the disk " -#~ "incompatible with the tools used to make it bootable with aboot. This " -#~ "means that the disk configured by the installer for use as the Debian " -#~ "boot disk will be inaccessible to the operating systems mentioned earlier." -#~ msgstr "" -#~ "除非您想在 Tru64 Unix 或者一个 free 4.4BSD-Lite 后续的系统下(FreeBSD, " -#~ "OpenBSD 或 NetBSD)使用这个磁盘，请 <emphasis>不要</emphasis> 建立包含" -#~ "<quote>整个磁盘</quote>的第三分区(如，起始和终止扇区扩展到整个磁盘)，这与" -#~ "让磁盘启动的工具 aboot 不兼容。意味着安装程序配置的 Debian 引导盘将无法被" -#~ "前面提到的操作系统访问。" - -#~ msgid "" -#~ "Also, because <command>aboot</command> is written to the first few " -#~ "sectors of the disk (currently it occupies about 70 kilobytes, or 150 " -#~ "sectors), you <emphasis>must</emphasis> leave enough empty space at the " -#~ "beginning of the disk for it. In the past, it was suggested that you make " -#~ "a small partition at the beginning of the disk, to be left unformatted. " -#~ "For the same reason mentioned above, we now suggest that you do not do " -#~ "this on disks that will only be used by GNU/Linux. When using " -#~ "<command>partman</command>, a small partition will still be created for " -#~ "<command>aboot</command> for convenience reasons." -#~ msgstr "" -#~ "同时，由于 <command>aboot</command> 将被写到磁盘的前面的几个扇区(目前它占" -#~ "用大约 70 KB 空间，或者 150 个扇区)。您 <emphasis>必须</emphasis> 在磁盘的" -#~ "开始处留下足够的空间。以前的方法建议您在磁盘的开始处分出一个较小并且不格式" -#~ "化的分区。基于上面的理由，我们现在建议您这块磁盘专门用于 GNU/Linux。当使" -#~ "用 <command>partman</command>，仍会建立一个小的分区给 <command>aboot</" -#~ "command>，这是习惯所致。" - -#~ msgid "" -#~ "For ARC installations, you should make a small FAT partition at the " -#~ "beginning of the disk to contain <command>MILO</command> and " -#~ "<command>linload.exe</command> — 5 megabytes should be sufficient, " -#~ "see <xref linkend=\"non-debian-partitioning\"/>. Unfortunately, making " -#~ "FAT file systems from the menu is not yet supported, so you'll have to do " -#~ "it manually from the shell using <command>mkdosfs</command> before " -#~ "attempting to install the boot loader." -#~ msgstr "" -#~ "对于 ARC 的安装来说，您应该在磁盘开始处建立一个小的 FAT 分区以便装入 " -#~ "<command>MILO</command> 以及 <command>linload.exe</command> — 至少需" -#~ "要 5 MB 空间，请参见 <xref linkend=\"non-debian-partitioning\"/>。不幸地" -#~ "是，从菜单建立 FAT 文件系统的方法是不被支持的，因此您必须在 Shell 下面使" -#~ "用 <command>mkdosfs</command> 然后再尝试安装启动引导器。" - -#~ msgid "" -#~ "On the other hand, Atari Falcons and Macs feel pain when swapping, so " -#~ "instead of making a large swap partition, get as much RAM as possible." -#~ msgstr "" -#~ "在另外一个方面，Atari Falcons 以及 Macs 会对交换感到很痛苦，因此建立一个大" -#~ "的交换分区不如获得尽可能多的 RAM 。" - -#~ msgid "" -#~ "The first ACSI device is named <filename>/dev/ada</filename>, the second " -#~ "is named <filename>/dev/adb</filename>." -#~ msgstr "" -#~ "第一个 ACSI 设备被命名为 <filename>/dev/ada</filename> ，第二个则是 " -#~ "<filename>/dev/adb</filename>。" - -#~ msgid "" -#~ "VMEbus systems using the TEAC FC-1 SCSI floppy drive will see it as " -#~ "normal SCSI disk. To make identification of the drive simpler the " -#~ "installation software will create a symbolic link to the appropriate " -#~ "device and name it <filename>/dev/sfd0</filename>." -#~ msgstr "" -#~ "VMEbus 系统使用的 TEAC FC-1 SCSI 软盘驱动器将被看成正常的 SCSI 磁盘。为了" -#~ "让驱动器辨认更强容易安装软件将创建一个符号链接至合适的设备并且称为 " -#~ "<filename>/dev/sfd0</filename>。" diff --git a/po/zh_CN/preparing.po b/po/zh_CN/preparing.po index 015aa9c7d..79cc5932b 100644 --- a/po/zh_CN/preparing.po +++ b/po/zh_CN/preparing.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: 2009-11-02 22:19+0000\n" -"PO-Revision-Date: 2008-10-23 10:42+0800\n" +"PO-Revision-Date: 2009-11-21 13:12+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" @@ -2640,339 +2640,3 @@ msgstr "" "碰到这种问题(有时可以看到显示器上的数据，有时却什么都没有)，或者引导安装程序" "以后黑屏，而不是显示用户界面，请试着在 MacOS 下修改显示设置为 256 色，替代 " "<quote>thousands</quote> 或 <quote>millions</quote>。" - -#~ msgid "Linux/Alpha FAQ" -#~ msgstr "Linux/Alpha FAQ" - -#~ msgid "Partitioning in Tru64 UNIX" -#~ msgstr "Tru64 UNIX 下分区" - -#~ msgid "" -#~ "Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly " -#~ "known as OSF/1, uses the partitioning scheme similar to the BSD " -#~ "<quote>disk label</quote>, which allows for up to eight partitions per " -#~ "disk drive. The partitions are numbered <quote>1</quote> through to " -#~ "<quote>8</quote> in Linux and <quote>lettered</quote> <quote>a</quote> " -#~ "through to <quote>h</quote> in UNIX. Linux kernels 2.2 and higher always " -#~ "correspond <quote>1</quote> to <quote>a</quote>, <quote>2</quote> to " -#~ "<quote>b</quote> and so on. For example, <filename>rz0e</filename> in " -#~ "Tru64 UNIX would most likely be called <filename>sda5</filename> in Linux." -#~ msgstr "" -#~ "Tru64 UNIX，前身是 Digital UNIX，更早是 OSF/1，采用的分区方式类似于 BSD 的" -#~ "<quote>disk label</quote>，它允许每个磁盘上最多八个分区。分区命名在 Linux " -#~ "下从<quote>1</quote>到<quote>8</quote>，在 UNIX 下是按<quote>字母次序</" -#~ "quote>从<quote>a</quote>到<quote>h</quote>。Linux 内核 2.2 或更高的版本是" -#~ "<quote>1</quote>对应<quote>a</quote>，<quote>2</quote>对应<quote>b</" -#~ "quote>，依此类推。例如，<filename>rz0e</filename> 是在 Tru64 UNIX 中的命" -#~ "名，而 <filename>sda5</filename> 是在 Linux 里的名称。" - -#~ msgid "" -#~ "Partitions in a Tru64 disk label may overlap. Moreover, if this disk will " -#~ "be used from Tru64, the <quote>c</quote> partition is required to span " -#~ "the entire disk (thus overlapping all other non-empty partitions). Under " -#~ "Linux this makes <filename>sda3</filename> identical to <filename>sda</" -#~ "filename> (<filename>sdb3</filename> to <filename>sdb</filename>, if " -#~ "present, and so on). However, the partman partitioning tool used by &d-i; " -#~ "cannot handle overlapping partitions at present. As a result, it is " -#~ "currently not recommended to share disks between Tru64 and Debian. " -#~ "Partitions on Tru64 disks can be mounted under Debian after installation " -#~ "has been completed." -#~ msgstr "" -#~ "Tru64 磁盘标签下的分区可以重叠。此外，如果以前磁盘在 Tru64 下使用，" -#~ "<quote>c</quote>分区要求扩展到整个磁盘(因此会覆盖其他所有的非空分区)。在 " -#~ "Linux 下这是 <filename>sda3</filename> 源于 <filename>sda</filename> " -#~ "(<filename>sdb3</filename> 对应于 <filename>sdb</filename>，等等)。然而，" -#~ "&d-i; 使用的 partman 分区工具当前尚不能处理重叠的分区。因此，目前不推荐在 " -#~ "Tru64 和 Debian 之间共享磁盘。完成安装之后，Tru64 的磁盘分区可以挂载到 " -#~ "Debian 之下。" - -#~ msgid "" -#~ "Another conventional requirement is for the <quote>a</quote> partition to " -#~ "start from the beginning of the disk, so that it always includes the boot " -#~ "block with the disk label. If you intend to boot Debian from that disk, " -#~ "you need to size it at least 2MB to fit aboot and perhaps a kernel. Note " -#~ "that this partition is only required for compatibility; you must not put " -#~ "a file system onto it, or you'll destroy data." -#~ msgstr "" -#~ "另外一个约定俗成的要求是分区<quote>a</quote>起始于磁盘开始处，因此它总包含" -#~ "具有磁盘标签的引导块。如果您从该磁盘启动 Debian，您至少需要给它 2MB 空间以" -#~ "在存储 aboot 和内核。注意，此分区仅为兼容考虑；您千万不要将文件系统置于其" -#~ "上，否则会破坏数据。" - -#~ msgid "" -#~ "It is possible, and indeed quite reasonable, to share a swap partition " -#~ "between UNIX and Linux. In this case it will be needed to do a " -#~ "<command>mkswap</command> on that partition every time the system is " -#~ "rebooted from UNIX into Linux, as UNIX will damage the swap signature. " -#~ "You may want to run <command>mkswap</command> from the Linux start-up " -#~ "scripts before adding swap space with <command>swapon -a</command>." -#~ msgstr "" -#~ "我们可以，也有理由，让 UNIX 和 Linux 共享交换分区。这时就需要在该分区上使" -#~ "用 <command>mkswap</command>。因为 UNIX 将破坏 swap 标志，所以每次从 UNIX " -#~ "到 Linux 重启后都要重新执行一次。您可以让 <command>mkswap</command> 从 " -#~ "Linux 的启动脚本里面运行，时间是在用 <command>swapon -a</command> 添加交换" -#~ "分区之前。" - -#~ msgid "" -#~ "If you want to mount UNIX partitions under Linux, note that Digital UNIX " -#~ "can use two different file system types, UFS and AdvFS, of which Linux " -#~ "only understands the former." -#~ msgstr "" -#~ "如果您想在 Linux 中挂载 UNIX 分区，注意 Digital UNIX 可以使用两种不同的文" -#~ "件系统类型，UFS 和 AdvFS，而 Linux 只能识别前者。" - -#~ msgid "Partitioning in Windows NT" -#~ msgstr "Windows NT 下分区" - -#~ msgid "" -#~ "Windows NT uses the PC-style partition table. If you are manipulating " -#~ "existing FAT or NTFS partitions, it is recommended that you use the " -#~ "native Windows NT tools (or, more conveniently, you can also repartition " -#~ "your disk from the AlphaBIOS setup menu). Otherwise, it is not really " -#~ "necessary to partition from Windows; the Linux partitioning tools will " -#~ "generally do a better job. Note that when you run NT, the Disk " -#~ "Administrator may offer to write a <quote>harmless signature</quote> on " -#~ "non-Windows disks if you have any. <emphasis>Never</emphasis> let it do " -#~ "that, as this signature will destroy the partition information." -#~ msgstr "" -#~ "Windows NT 使用 PC 风格的分区表。如果您要处理已存在的 FAT 或 NTFS 分区，推" -#~ "荐使用 Windows NT 本身的工具(或者，照惯例，您可以用 AlphaBIOS 配置菜单里面" -#~ "的工具重新分区)。否则，真没有必要从 Windows 来分区，Linux 的分区工具可以做" -#~ "得更好。注意，如果您运行 NT，Disk Administrator 也许会建议您写一个" -#~ "<quote>harmless signature</quote> 到您的非 Windows 的磁盘上。<emphasis>千" -#~ "万别</emphasis>让它那样做，这个标志会破坏该分区上的信息。" - -#~ msgid "" -#~ "If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you " -#~ "will need a (small) FAT partition for MILO. 5 MB is quite sufficient. If " -#~ "Windows NT is installed, its 6 MB bootstrap partition can be employed for " -#~ "this purpose. Debian &releasename; does not support installing MILO. If " -#~ "you already have MILO installed on your system, or install MILO from " -#~ "other media, Debian can still be booted from ARC." -#~ msgstr "" -#~ "如果您计划从 ARC/AlphaBIOS/ARCSBIOS 控制台引导 Linux，您也许需要给 MILO 一" -#~ "个(小的) FAT 分区。5 Mb 就足够了。如果已经安装了 Windows NT，它的 6 Mb 启" -#~ "动分区可以用来满足此要求。Debian &releasename; 不支持安装 MILO。如果您的系" -#~ "统上已经有 MILO，或者从其他介质安装，Debian 仍然可以从 ARC 启动。" - -#~ msgid "" -#~ "With the exception of the BVM and Motorola VMEbus computers, the only " -#~ "supported installation method for m68k systems is booting from a local " -#~ "disk or floppy using an AmigaOS/TOS/MacOS-based bootstrap, for these " -#~ "machines you will need the original operating system in order to boot " -#~ "Linux. In order to boot Linux on the BVM and Motorola VMEbus machines you " -#~ "will need the <quote>BVMBug</quote> or <quote>16xBug</quote> boot ROMs." -#~ msgstr "" -#~ "除了 BVM 和摩托罗拉 VMEbus 系列的计算机外，m68k 系统的计算机唯一支持的安装" -#~ "方式就是用 AmigaOS、TOS 或 MacOS 的引导程序从本地的硬盘或软盘上启动。所" -#~ "以，对于这种类型的计算机，您必须要有原来的操作系统用来启动 Linux。而为了" -#~ "在 BVM 和摩托罗拉 VMEbus 系列的计算机上启动 Linux，<quote>BVMBug</quote>或" -#~ "<quote>16xBug</quote>引导存储器是必须的。" - -#~ msgid "Linux/m68k FAQ" -#~ msgstr "Linux/m68k FAQ" - -#~ msgid "Whether IDE or SCSI (most m68k computers are SCSI)." -#~ msgstr "是 IDE 还是 SCSI(大多数 m68k 计算机上是 SCSI)。" - -#~ msgid "" -#~ "A 68030 or better processor is recommended for m68k installs. You may get " -#~ "by with a little less drive space than shown." -#~ msgstr "" -#~ "在 m68k 机器上安装，推荐使用 68030 或更快的处理器。您可能用比推荐稍小的硬" -#~ "盘空间就能完成安装。" - -#~ msgid "Partitioning in AmigaOS" -#~ msgstr "在 AmigaOS 下分区" - -#~ msgid "" -#~ "If you are running AmigaOS, you can use the <command>HDToolBox</command> " -#~ "program to adjust your native partitions prior to installation." -#~ msgstr "" -#~ "如果您运行 AmigaOS，您可以使用 <command>HDToolBox</command> 程序在安装之前" -#~ "调整您的分区。" - -#~ msgid "Partitioning in Atari TOS" -#~ msgstr "在 Atari TOS 下分区" - -#~ msgid "" -#~ "Atari partition IDs are three ASCII characters, use <quote>LNX</quote> " -#~ "for data and <quote>SWP</quote> for swap partitions. If using the low " -#~ "memory installation method, a small Minix partition is also needed (about " -#~ "2 MB), for which the partition ID is <quote>MNX</quote>. Failure to set " -#~ "the appropriate partition IDs not only prevents the Debian installation " -#~ "process from recognizing the partitions, but also results in TOS " -#~ "attempting to use the Linux partitions, which confuses the hard disk " -#~ "driver and renders the whole disk inaccessible." -#~ msgstr "" -#~ "Atari 的分区 ID 是三个 ASCII 字符，<quote>LNX</quote>用于数据，" -#~ "<quote>SWP</quote>用于交换分区。如果使用小内存安装方式，还需要一个小的 " -#~ "Minix 分区(大约 2MB)，它的 ID 是<quote>MNX</quote>。错误的设置分区 ID 不仅" -#~ "会因为 Debian 无法识别分区而中断安装进程，还会造成 TOS 使用 Linux 分区，让" -#~ "硬盘驱动程序混乱，使得整个磁盘无法访问。" - -#~ msgid "" -#~ "There are a multitude of third party partitioning tools available (the " -#~ "Atari <command>harddisk</command> utility doesn't permit changing the " -#~ "partition ID); this manual cannot give detailed descriptions for all of " -#~ "them. The following description covers <command>SCSITool</command> (from " -#~ "Hard+Soft GmBH)." -#~ msgstr "" -#~ "有很多第三方的分区工具(Atari <command>harddisk</command> 工具不允许修改分" -#~ "区 ID)，本手册无法对它们都进行详细说明。下面的说明涵盖了 " -#~ "<command>SCSITool</command> (来自 Hard+Soft GmBH)。" - -#~ msgid "" -#~ "Start <command>SCSITool</command> and select the disk you want to " -#~ "partition (<guimenu>Disk</guimenu> menu, item <guimenuitem>select</" -#~ "guimenuitem>)." -#~ msgstr "" -#~ "启动 <command>SCSITool</command> 然后选择您要分区的磁盘(<guimenu>Disk</" -#~ "guimenu> 菜单中的 <guimenuitem>select</guimenuitem>)。" - -#~ msgid "" -#~ "From the <guimenu>Partition</guimenu> menu, select either " -#~ "<guimenuitem>New</guimenuitem> to add new partitions or change the " -#~ "existing partition sizes, or <guimenuitem>Change</guimenuitem> to change " -#~ "one specific partition. Unless you have already created partitions with " -#~ "the right sizes and only want to change the partition ID, " -#~ "<guimenuitem>New</guimenuitem> is probably the best choice." -#~ msgstr "" -#~ "从 <guimenu>Partition</guimenu> 菜单，选择 <guimenuitem>New</guimenuitem> " -#~ "来添加新分区或者修改现有分区的大小，或选择 <guimenuitem>Change</" -#~ "guimenuitem> 来修改指定的分区。除非您已经创建了合适大小的分区并只想修改分" -#~ "区 ID，否则 <guimenuitem>New</guimenuitem> 大概是最佳选择。" - -#~ msgid "" -#~ "For the <guimenuitem>New</guimenuitem> choice, select <guilabel>existing</" -#~ "guilabel> in the dialog box prompting the initial settings. The next " -#~ "window shows a list of existing partitions which you can adjust using the " -#~ "scroll buttons, or by clicking in the bar graphs. The first column in the " -#~ "partition list is the partition type; just click on the text field to " -#~ "edit it. When you are finished changing partition settings, save the " -#~ "changes by leaving the window with the <guibutton>OK</guibutton> button." -#~ msgstr "" -#~ "在 <guimenuitem>New</guimenuitem> 选项中，从提示初始设置的对话框里选择 " -#~ "<guilabel>existing</guilabel>。接下来的窗口显示的是现有分区的列表，您可以" -#~ "通过滚动按钮进行调节，或者直接点击条图。分区列表的第一列是分区类型，点击文" -#~ "本框就可以编辑它。当您完成分区设置，用 <guibutton>OK</guibutton> 按钮保存" -#~ "并离开窗口。" - -#~ msgid "" -#~ "For the <guimenuitem>Change</guimenuitem> option, select the partition to " -#~ "change in the selection list, and select <guilabel>other systems</" -#~ "guilabel> in the dialog box. The next window lists detailed information " -#~ "about the location of this partition, and lets you change the partition " -#~ "ID. Save changes by leaving the window with the <guibutton>OK</guibutton> " -#~ "button." -#~ msgstr "" -#~ "在 <guimenuitem>Change</guimenuitem> 选项中，从列表里面选择要修改的分区，" -#~ "然后在对话框中选择 <guilabel>other systems</guilabel>。接下来的窗口会列出" -#~ "该分区位置的详细信息，并让您修改分区 ID。用 <guibutton>OK</guibutton> 按钮" -#~ "保存并离开窗口。" - -#~ msgid "" -#~ "Write down the Linux names for each of the partitions you created or " -#~ "changed for use with Linux — see <xref linkend=\"device-names\"/>." -#~ msgstr "" -#~ "记下您为了使用 Linux 而创建或修改的每个分区的 Linux 名称 — 参考 " -#~ "<xref linkend=\"device-names\"/>。" - -#~ msgid "" -#~ "Quit <command>SCSITool</command> using the <guimenuitem>Quit</" -#~ "guimenuitem> item from the <guimenu>File</guimenu> menu. The computer " -#~ "will reboot to make sure the changed partition table is used by TOS. If " -#~ "you changed any TOS/GEM partitions, they will be invalidated and have to " -#~ "be reinitialized (we told you to back up everything on the disk, didn't " -#~ "we?)." -#~ msgstr "" -#~ "退出 <command>SCSITool</command> 使用 <guimenuitem>Quit</guimenuitem> 选" -#~ "项，位于 <guimenu>File</guimenu> 菜单下。计算机将重新启动以确保 TOS 会使用" -#~ "修改过的分区表。如果您修改了任何 TOS/GEM 分区，它们将会失效并要重新初始化" -#~ "(我们已经告诉过您需要备份磁盘上的所有数据，不是吗？)。" - -#~ msgid "" -#~ "There is a partitioning tool for Linux/m68k called <command>atari-fdisk</" -#~ "command> in the installation system, but for now we recommend you " -#~ "partition your disk using a TOS partition editor or some disk tool. If " -#~ "your partition editor doesn't have an option to edit the partition type, " -#~ "you can do this crucial step at a later stage (from the booted temporary " -#~ "install RAMdisk). <command>SCSITool</command> is only one of the " -#~ "partition editors we know of which supports selection of arbitrary " -#~ "partition types. There may be others; select the tool that suits your " -#~ "needs." -#~ msgstr "" -#~ "在 Linux/m68k 中有一个分区工具，在安装系统中被称为 <command>atari-fdisk</" -#~ "command>，但是我们现在建议您使用 TOS 分区编辑器或其他的磁盘工具来对硬盘分" -#~ "区。如果您的分区编辑器没有编辑分区类型的选项，您可以在后续阶段做这项重要任" -#~ "务 (从启动临时安装 RAMdisk)。<command>SCSITool</command> 是我们所知的唯一" -#~ "支持选择任意分区类型的分区编辑器。也许还有其他的，请选择一个符合您要求的工" -#~ "具。" - -#~ msgid "Partitioning in MacOS" -#~ msgstr "在 MacOS 下分区" - -#~ msgid "" -#~ "Partitioning tools for Macintosh tested include <command>pdisk</command>, " -#~ "<command>HD SC Setup</command> 7.3.5 (Apple), <command>HDT</command> 1.8 " -#~ "(FWB), <command>SilverLining</command> (LaCie), and <command>DiskTool</" -#~ "command> (Tim Endres, GPL). Full versions are required for <command>HDT</" -#~ "command> and <command>SilverLining</command>. The Apple tool requires a " -#~ "patch in order to recognize third-party disks (a description on how to " -#~ "patch <command>HD SC Setup</command> using <command>ResEdit</command> can " -#~ "be found at <ulink url=\"http://www.euronet.nl/users/ernstoud/patch.html" -#~ "\"></ulink>)." -#~ msgstr "" -#~ "Macintosh 下经过测试的分区工具包括 <command>pdisk</command>、<command>HD " -#~ "SC Setup</command> 7.3.5 (Apple)、<command>HDT</command> 1.8 (FWB)、" -#~ "<command>SilverLining</command> (LaCie) 和 <command>DiskTool</command> " -#~ "(Tim Endres, GPL)。对 <command>HDT</command> 和 <command>SilverLining</" -#~ "command> 要完整版。Apple 工具需要打补丁才能识别第三方的磁盘 (如何给 " -#~ "<command>HD SC Setup</command> 打补丁(使用 <command>ResEdit</command>)的说" -#~ "明位于 <ulink url=\"http://www.euronet.nl/users/ernstoud/patch.html\"></" -#~ "ulink>)。" - -#~ msgid "" -#~ "For IDE based Macs, you need to use <command>Apple Drive Setup</command> " -#~ "to create empty space for the Linux partitions, and complete the " -#~ "partitioning under Linux, or use the MacOS version of pdisk available for " -#~ "download from <ulink url=\"http://homepage.mac.com/alk/downloads/pdisk." -#~ "sit.hqx\">Alsoft</ulink>." -#~ msgstr "" -#~ "对基于 IDE 的 Mac，您需要使用 <command>Apple Drive Setup</command> 为 " -#~ "Linux 分区创建空闲空间，然后在 Linux 下完成分区，或者使用 MacOS 版的 " -#~ "pdisk，它可以从 <ulink url=\"http://homepage.mac.com/alk/downloads/pdisk." -#~ "sit.hqx\">Alsoft</ulink> 下载。" - -#~ msgid "Firmware Revisions and Existing OS Setup" -#~ msgstr "固件修订版和已有的 OS 配置" - -#~ msgid "" -#~ "&arch-title; machines are generally self-configuring and do not require " -#~ "firmware configuration. However, you should make sure that you have the " -#~ "appropriate ROM and system patches. On the Macintosh, MacOS version >= " -#~ "7.1 is recommended because version 7.0.1 contains a bug in the video " -#~ "drivers preventing the boot loader from deactivating the video " -#~ "interrupts, resulting in a boot hang. On the BVM VMEbus systems you " -#~ "should make sure you are using BVMBug revision G or higher boot ROMs. The " -#~ "BVMBug boot ROMs do not come as standard on the BVM systems but are " -#~ "available from BVM on request free of charge." -#~ msgstr "" -#~ "&arch-title; 机器通常自行配置，不需要设置固件。但是，您应该确定您用了适宜" -#~ "的 ROM 和系统补丁。在 Macintosh 上，推荐使用 MacOS >= 7.1 的版本，这是由于" -#~ "版本 7.0.1 在视频驱动方面包含 bug，它会阻挡 boot loader 禁止视频中断，造" -#~ "成 boot 挂起。在 BVM VMEbus 系统上，您应该确定使用 BVMBug 修订版 G 或更新" -#~ "的 boot ROM。BVMBug boot ROM 不属于 BVM 系统的标准配置，但可用从 BVM 免费" -#~ "获取。" - -#~ msgid "" -#~ "Atari TT RAM boards are notorious for RAM problems under Linux; if you " -#~ "encounter any strange problems, try running at least the kernel in ST-" -#~ "RAM. Amiga users may need to exclude RAM using a booter memfile. <phrase " -#~ "condition=\"FIXME\"><emphasis> FIXME: more description of this needed. </" -#~ "emphasis></phrase>" -#~ msgstr "" -#~ "Atari TT 内存条因其在 Linux 下的内存故障而获臭名。无论您 碰到了何种怪异的" -#~ "问题，请至少试试换用 ST-RAM 来运行内核。Amiga 的用户可能需要用 booter " -#~ "menfile 来排除部分内存。<phrase condition=\"FIXME\"><emphasis> FIXME: " -#~ "more description of this needed. </emphasis></phrase>" diff --git a/po/zh_CN/preseed.po b/po/zh_CN/preseed.po index 89af9fd43..afaffd400 100644 --- a/po/zh_CN/preseed.po +++ b/po/zh_CN/preseed.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: 2009-11-18 01:11+0000\n" -"PO-Revision-Date: 2009-09-12 09:50+0800\n" +"PO-Revision-Date: 2009-11-21 13:31+0800\n" "Last-Translator: Ji YongGang <jungle@soforge.com>\n" "Language-Team: debian-chinese-gb <debian-chinese-gb@debian.org>\n" "MIME-Version: 1.0\n" @@ -770,27 +770,27 @@ msgstr "debian-installer/framebuffer" #: preseed.xml:512 #, no-c-format msgid "language" -msgstr "" +msgstr "language" #. Tag: entry #: preseed.xml:512 -#, fuzzy, no-c-format +#, no-c-format #| msgid "debian-installer/locale" msgid "debian-installer/language" -msgstr "debian-installer/locale" +msgstr "debian-installer/language" #. Tag: entry #: preseed.xml:513 #, no-c-format msgid "country" -msgstr "" +msgstr "country" #. Tag: entry #: preseed.xml:513 -#, fuzzy, no-c-format +#, no-c-format #| msgid "debian-installer/locale" msgid "debian-installer/country" -msgstr "debian-installer/locale" +msgstr "debian-installer/country" #. Tag: entry #: preseed.xml:514 @@ -1204,7 +1204,7 @@ msgid "" "instead, the values will need to be preseeded individually. </para> </" "footnote>. So alternatively the values can be preseeded individually. " "Language and country can also be specified as boot parameters." -msgstr "" +msgstr "虽然这个方法很容易使用，但它无法预置所有的语言、国家和地方组合<footnote> <para> 比如预置 <literal>locale</literal> 为 <userinput>en_NL</userinput> 在安装后的系统中默认的 locale 将是 <literal>en_US.UTF-8</literal>。如果想使用 <literal>en_GB.UTF-8</literal>，该值应该分别进行预置。</para> </footnote>。 因此另一种方法是单独预置各值。语言和国家可以在引导参数里面指定。" #. Tag: screen #: preseed.xml:716 @@ -1220,6 +1220,15 @@ msgid "" "# Optionally specify additional locales to be generated.\n" "#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8" msgstr "" +"# Preseeding only locale sets language, country and locale.\n" +"d-i debian-installer/locale string en_US\n" +"\n" +"# The values can also be preseeded individually for greater flexibility.\n" +"#d-i debian-installer/language string en\n" +"#d-i debian-installer/country string NL\n" +"#d-i debian-installer/locale string en_GB.UTF-8\n" +"# Optionally specify additional locales to be generated.\n" +"#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8" #. Tag: para #: preseed.xml:718 @@ -1503,7 +1512,7 @@ msgstr "" #. Tag: para #: preseed.xml:817 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "The parameter <classname>mirror/udeb/suite</classname> determines the " #| "suite for additional components for the installer. It is only useful to " @@ -1519,11 +1528,7 @@ msgid "" "suite that was used to build the initrd for the installation method used for " "the installation. Normally the installer will automatically use the correct " "value and there should be no need to set this." -msgstr "" -"参数 <classname>mirror/udeb/suite</classname> 决定安装程序使用的额外组件的套" -"件。它只在组件通过网络下载并与安装时使用的 initrd 建立套件相匹配时才有效。默" -"认情况下，<classname>mirror/udeb/suite</classname> 与 <classname>mirror/" -"suite</classname> 的值相同。" +msgstr "参数 <classname>mirror/udeb/suite</classname> 决定安装程序使用的额外组件的套件。它只在组件通过网络下载并与安装时使用的 initrd 建立套件相匹配时才有效。通常安装程序会自动安装并使用正确的值而毋需手动设置。" #. Tag: screen #: preseed.xml:828 @@ -1961,7 +1966,7 @@ msgstr "本阶段的安装并没有多少东西需要预置。仅有一个与内 #. Tag: screen #: preseed.xml:931 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "# Select the initramfs generator used to generate the initrd for 2.6 " #| "kernels.\n" @@ -1986,12 +1991,15 @@ msgid "" "# kernel is to be installed.\n" "#d-i base-installer/kernel/image string linux-image-2.6-486" msgstr "" -"# Select the initramfs generator used to generate the initrd for 2.6 " -"kernels.\n" +"# Configure APT to not install recommended packages by default. Use of this\n" +"# option can result in an incomplete system and should only be used by very\n" +"# experienced users.\n" +"#d-i base-installer/install-recommends boolean false\n" +"\n" +"# Select the initramfs generator used to generate the initrd for 2.6 kernels.\n" "#d-i base-installer/kernel/linux/initramfs-generators string yaird\n" "\n" -"# The kernel image (meta) package to be installed; \"none\" can be used if " -"no\n" +"# The kernel image (meta) package to be installed; \"none\" can be used if no\n" "# kernel is to be installed.\n" "#d-i base-installer/kernel/image string linux-image-2.6-486" @@ -2297,7 +2305,7 @@ msgstr "" #. Tag: screen #: preseed.xml:1050 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "#tasksel tasksel/first multiselect standard, web-server\n" #| "# If the desktop task is selected, install the kde and xfce desktops\n" @@ -2351,11 +2359,8 @@ msgstr "" "\n" "# Individual additional packages to install\n" "#d-i pkgsel/include string openssh-server build-essential\n" -"# By default, packages that are only Recommended by packages installed " -"using\n" +"# By default, packages that are only Recommended by packages installed using\n" "# pkgsel/include (as opposed to their dependencies) will not be installed.\n" -"# Uncomment this line to install Recommends as well.\n" -"#d-i pkgsel/include/install-recommends boolean true\n" "# Whether to upgrade packages after debootstrap.\n" "# Allowed values: none, safe-upgrade, full-upgrade\n" "#d-i pkgsel/upgrade select none\n" @@ -2750,10 +2755,3 @@ msgstr "" "也可以通过在前面设置 preseed/url 从 initrd 或者文件预置链载进入网络预置。这将" "使网络预置在网络连通时执行。您应该小心使用，因为这是两种预置，意味着您有机会" "执行 preseed/early 命令，第二个可以在网络连通后使用。" - -#~ msgid "" -#~ "# Locale sets language and country.\n" -#~ "d-i debian-installer/locale string en_US" -#~ msgstr "" -#~ "# Locale sets language and country.\n" -#~ "d-i debian-installer/locale string en_US" diff --git a/po/zh_CN/random-bits.po b/po/zh_CN/random-bits.po index c59cf28ed..3bc775c57 100644 --- a/po/zh_CN/random-bits.po +++ b/po/zh_CN/random-bits.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: 2009-11-08 01:11+0000\n" -"PO-Revision-Date: 2009-04-13 17:21+0800\n" +"PO-Revision-Date: 2009-11-21 13:34+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" @@ -2400,7 +2400,7 @@ msgid "" "If a dialog offers additional help information, a <guibutton>Help</" "guibutton> button will be displayed. The help information can be accessed " "either by activating the button or by pressing the <keycap>F1</keycap> key." -msgstr "" +msgstr "如果对话框提供了额外的帮助信息，会显示一个 <guibutton>Help</guibutton> 按钮。帮助信息可以通过该按钮或者按下 <keycap>F1</keycap> 键。" #. Tag: para #: random-bits.xml:1263 diff --git a/po/zh_CN/using-d-i.po b/po/zh_CN/using-d-i.po index 3c0395ed4..1f8de8158 100644 --- a/po/zh_CN/using-d-i.po +++ b/po/zh_CN/using-d-i.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: 2009-11-11 01:11+0000\n" -"PO-Revision-Date: 2009-09-12 09:51+0800\n" +"PO-Revision-Date: 2009-11-21 13:42+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" @@ -166,7 +166,7 @@ msgid "" "Some dialogs may offer additional help information. If help is available " "this will be indicated on the bottom line of the screen by displaying that " "help information can be accessed by pressing the <keycap>F1</keycap> key." -msgstr "" +msgstr "一些对话框会提供额外的帮助信息。有帮助信息的时候，它们会显示在屏幕的最下面一行，帮助信息可以通过 <keycap>F1</keycap> 键访问。" #. Tag: para #: using-d-i.xml:95 @@ -897,7 +897,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:575 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "A default locale will be selected based on the selected language and " #| "country. If you are installing at medium or low priority, you will have " @@ -909,9 +909,7 @@ msgid "" "option of selecting additional locales to be generated for the installed " "system; if you do, you will be asked which locale should be the default for " "the installed system." -msgstr "" -"默认 locale 的选择是基于先前所选的语言和国家。如果您以 medium 或 low 优先级安" -"装，可以选择不同的默认 locale 以及为安装好的系统生成额外的 locale。" +msgstr "默认 locale 的选择是基于先前所选的语言和国家。如果您以 medium 或 low 优先级安装，可以有机会为安装后的系统选择生成额外的 locale；这时，您将会被要求选择默认的 local。" #. Tag: title #: using-d-i.xml:591 @@ -4791,31 +4789,3 @@ msgid "" msgstr "" "如果固件从不严格的固件文件加载，复制到安装好的系统的固件将<emphasis>不会</" "emphasis>自动更新，除非对应的固件软件包(如果有的话)在系统安装之后安装。" - -#~ msgid "" -#~ "If you choose guided partitioning for your Alpha system, an additional, " -#~ "unformatted partition will be allocated at the beginning of your disk to " -#~ "reserve this space for the aboot boot loader." -#~ msgstr "" -#~ "如果您为 Alpha 系统选择导引式分区，一个额外的、未格式化的分区将分配在磁盘" -#~ "的开始处，为 aboot boot loader 的保留空间。" - -#~ msgid "Install <command>aboot</command> on a Hard Disk" -#~ msgstr "安装 <command>aboot</command> 到硬盘上" - -#~ msgid "" -#~ "If you have booted from SRM and you select this option, the installer " -#~ "will write <command>aboot</command> to the first sector of the disk on " -#~ "which you installed Debian. Be <emphasis>very</emphasis> careful — " -#~ "it is <emphasis>not</emphasis> possible to boot multiple operating " -#~ "systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k." -#~ "a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a " -#~ "different operating system installed on the disk where you have installed " -#~ "Debian, you will have to boot GNU/Linux from a floppy instead." -#~ msgstr "" -#~ "如果您从 SRM 启动，并选择该项，安装程序将写入 <command>aboot</command> 到" -#~ "安装 Debian 磁盘的第一个扇区。要<emphasis>特别</emphasis>小心 — 它也" -#~ "许<emphasis>不能</emphasis>从同一个磁盘上启动多个操作系统(如，GNU/Linux、" -#~ "Free/Open/NetBSD、OSF/1 又名 Digital Unix 又名 Tru64 Unix 或 OpenVMS)。如" -#~ "果您在安装 Debian 的磁盘上装有不同的操作系统，将不得不从一个软盘启动 GNU/" -#~ "Linux。" diff --git a/po/zh_CN/welcome.po b/po/zh_CN/welcome.po index a652f46c5..c1a286f48 100644 --- a/po/zh_CN/welcome.po +++ b/po/zh_CN/welcome.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: 2009-11-08 01:11+0000\n" -"PO-Revision-Date: 2008-10-23 10:13+0800\n" +"PO-Revision-Date: 2009-11-21 13:46+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" @@ -295,7 +295,7 @@ msgstr "" #. Tag: para #: welcome.xml:194 -#, fuzzy, no-c-format +#, no-c-format #| msgid "" #| "Linus Torvalds continues to coordinate the work of several hundred " #| "developers with the help of a few trusty deputies. An excellent weekly " @@ -311,12 +311,7 @@ msgid "" "kernel. More information about the <userinput>linux-kernel</userinput> " "mailing list can be found on the <ulink url=\"&url-linux-kernel-list-faq;" "\">linux-kernel mailing list FAQ</ulink>." -msgstr "" -"在几个可信赖代理人的帮助下，Linus Torvalds 一直协调着数百位开发人员的工作。有" -"关 <userinput>linux-kernel</userinput> 邮件列表上讨论内容的每周纪要在 <ulink " -"url=\"&url-kernel-traffic;\">Kernel Traffic</ulink>上可以看到。更多有关 " -"<userinput>linux-kernel</userinput> 邮件列表的信息请参考 <ulink url=\"&url-" -"linux-kernel-list-faq;\">linux-kernel 邮件列表问答</ulink>。" +msgstr "在一些子系统维护人员的帮助下，Linus Torvalds 一直协调着数百位开发人员的工作。Linux 内核有一个 <ulink url=\"&url-kernel-org;\">official website</ulink>。有关 <userinput>linux-kernel</userinput> 邮件列表更多的信息可以在 <ulink url=\"&url-linux-kernel-list-faq;\">linux-kernel mailing list FAQ</ulink> 上找到。" #. Tag: para #: welcome.xml:204 |