diff options
Diffstat (limited to 'po/pot/install-methods.pot')
| -rw-r--r-- | po/pot/install-methods.pot | 84 |
1 files changed, 42 insertions, 42 deletions
diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 072d95889..a67e08450 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-05-03 00:14+0000\n" +"POT-Creation-Date: 2009-07-10 00:13+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -806,25 +806,25 @@ msgid "<emphasis>Copy</emphasis> (not move) the following four files which you d msgstr "" #. Tag: filename -#: install-methods.xml:1103 install-methods.xml:1460 +#: install-methods.xml:1103 install-methods.xml:1461 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1108 install-methods.xml:1465 +#: install-methods.xml:1108 install-methods.xml:1466 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1113 install-methods.xml:1470 +#: install-methods.xml:1113 install-methods.xml:1471 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1118 install-methods.xml:1475 +#: install-methods.xml:1118 install-methods.xml:1476 #, no-c-format msgid "yaboot.conf" msgstr "" @@ -945,23 +945,23 @@ msgstr "" #. Tag: para #: install-methods.xml:1308 #, no-c-format -msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. In that case, you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." +msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1329 +#: install-methods.xml:1330 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1330 +#: install-methods.xml:1331 #, no-c-format msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):" msgstr "" #. Tag: screen -#: install-methods.xml:1337 +#: install-methods.xml:1338 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -986,25 +986,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1339 +#: install-methods.xml:1340 #, no-c-format msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP." msgstr "" #. Tag: para -#: install-methods.xml:1349 +#: install-methods.xml:1350 #, no-c-format msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1357 +#: install-methods.xml:1358 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1358 +#: install-methods.xml:1359 #, no-c-format msgid "" "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" @@ -1039,13 +1039,13 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1374 +#: install-methods.xml:1375 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1375 +#: install-methods.xml:1376 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled. This is usually enabled by having something like the following line in <filename>/etc/inetd.conf</filename>: <informalexample><screen>\n" @@ -1054,19 +1054,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1387 +#: install-methods.xml:1388 #, no-c-format msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/var/lib/tftpboot</filename>. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1397 +#: install-methods.xml:1398 #, no-c-format msgid "Look in <filename>/etc/inetd.conf</filename> and remember the directory which is used as the argument of <command>in.tftpd</command><footnote> <para> All <command>in.tftpd</command> alternatives available in Debian should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors. </para> </footnote>; you'll need that below. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1417 +#: install-methods.xml:1418 #, no-c-format msgid "" "If you intend to install Debian on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n" @@ -1077,61 +1077,61 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1439 +#: install-methods.xml:1440 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1440 +#: install-methods.xml:1441 #, no-c-format msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." msgstr "" #. Tag: para -#: install-methods.xml:1449 +#: install-methods.xml:1450 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:" msgstr "" #. Tag: filename -#: install-methods.xml:1480 +#: install-methods.xml:1481 #, no-c-format msgid "boot.msg" msgstr "" #. Tag: para -#: install-methods.xml:1485 +#: install-methods.xml:1486 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: para -#: install-methods.xml:1493 +#: install-methods.xml:1494 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: title -#: install-methods.xml:1505 +#: install-methods.xml:1506 #, no-c-format msgid "Alpha TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1506 +#: install-methods.xml:1507 #, no-c-format 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 "" #. Tag: title -#: install-methods.xml:1521 +#: install-methods.xml:1522 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1522 +#: install-methods.xml:1523 #, no-c-format msgid "" "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n" @@ -1140,85 +1140,85 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1538 +#: install-methods.xml:1539 #, no-c-format msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested." msgstr "" #. Tag: para -#: install-methods.xml:1545 +#: install-methods.xml:1546 #, no-c-format msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in." msgstr "" #. Tag: title -#: install-methods.xml:1556 +#: install-methods.xml:1557 #, no-c-format msgid "BVM/Motorola TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1557 +#: install-methods.xml:1558 #, no-c-format msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:1562 +#: install-methods.xml:1563 #, no-c-format 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 "" #. Tag: title -#: install-methods.xml:1574 +#: install-methods.xml:1575 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1575 +#: install-methods.xml:1576 #, no-c-format msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>." msgstr "" #. Tag: title -#: install-methods.xml:1587 +#: install-methods.xml:1588 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1588 +#: install-methods.xml:1589 #, no-c-format msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to be loaded to CFE." msgstr "" #. Tag: title -#: install-methods.xml:1693 +#: install-methods.xml:1694 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1694 +#: install-methods.xml:1695 #, no-c-format msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself." msgstr "" #. Tag: title -#: install-methods.xml:1707 +#: install-methods.xml:1708 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1708 +#: install-methods.xml:1709 #, no-c-format msgid "The Debian Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." msgstr "" #. Tag: para -#: install-methods.xml:1715 +#: install-methods.xml:1716 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" |