diff options
Diffstat (limited to 'po/zh_CN/install-methods.po')
| -rw-r--r-- | po/zh_CN/install-methods.po | 211 |
1 files changed, 15 insertions, 196 deletions
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> 文件来获得更多的" -#~ "关于您所使用的子体系的系统特殊配置信息。" |