summaryrefslogtreecommitdiff
path: root/po/pot/install-methods.pot
diff options
context:
space:
mode:
Diffstat (limited to 'po/pot/install-methods.pot')
-rw-r--r--po/pot/install-methods.pot86
1 files changed, 43 insertions, 43 deletions
diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot
index 41d3a8320..7ad4deae5 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: 2010-02-24 01:12+0000\n"
+"POT-Creation-Date: 2010-02-26 01:12+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"
@@ -752,25 +752,25 @@ msgid "<emphasis>Copy</emphasis> (not move) the following four files which you d
msgstr ""
#. Tag: filename
-#: install-methods.xml:1034 install-methods.xml:1361
+#: install-methods.xml:1034 install-methods.xml:1360
#, no-c-format
msgid "vmlinux"
msgstr ""
#. Tag: filename
-#: install-methods.xml:1039 install-methods.xml:1366
+#: install-methods.xml:1039 install-methods.xml:1365
#, no-c-format
msgid "initrd.gz"
msgstr ""
#. Tag: filename
-#: install-methods.xml:1044 install-methods.xml:1371
+#: install-methods.xml:1044 install-methods.xml:1370
#, no-c-format
msgid "yaboot"
msgstr ""
#. Tag: filename
-#: install-methods.xml:1049 install-methods.xml:1376
+#: install-methods.xml:1049 install-methods.xml:1375
#, no-c-format
msgid "yaboot.conf"
msgstr ""
@@ -832,41 +832,41 @@ msgstr ""
#. Tag: para
#: install-methods.xml:1124
#, no-c-format
-msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>."
+msgid "For a &debian; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>."
msgstr ""
#. Tag: title
-#: install-methods.xml:1141
+#: install-methods.xml:1140
#, no-c-format
msgid "Setting up RARP server"
msgstr ""
#. Tag: para
-#: install-methods.xml:1142
+#: install-methods.xml:1141
#, no-c-format
msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>ip addr show dev eth0</userinput>."
msgstr ""
#. Tag: para
-#: install-methods.xml:1154
+#: install-methods.xml:1153
#, no-c-format
msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
msgstr ""
#. Tag: title
-#: install-methods.xml:1175
+#: install-methods.xml:1174
#, no-c-format
msgid "Setting up a DHCP server"
msgstr ""
#. Tag: para
-#: install-methods.xml:1176
+#: install-methods.xml:1175
#, 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:1183
+#: install-methods.xml:1182
#, no-c-format
msgid ""
"option domain-name \"example.com\";\n"
@@ -891,25 +891,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: install-methods.xml:1185
+#: install-methods.xml:1184
#, 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:1195
+#: install-methods.xml:1194
#, 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:1203
+#: install-methods.xml:1202
#, no-c-format
msgid "Enabling PXE Booting in the DHCP configuration"
msgstr ""
#. Tag: para
-#: install-methods.xml:1204
+#: install-methods.xml:1203
#, 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"
@@ -944,19 +944,19 @@ msgid ""
msgstr ""
#. Tag: title
-#: install-methods.xml:1224
+#: install-methods.xml:1223
#, no-c-format
msgid "Setting up a BOOTP server"
msgstr ""
#. Tag: para
-#: install-methods.xml:1225
+#: install-methods.xml:1224
#, no-c-format
msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively."
msgstr ""
#. Tag: para
-#: install-methods.xml:1233
+#: install-methods.xml:1232
#, no-c-format
msgid ""
"To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run Debian, the line in question should look like: <informalexample><screen>\n"
@@ -973,43 +973,43 @@ msgid ""
msgstr ""
#. Tag: para
-#: install-methods.xml:1266
+#: install-methods.xml:1265
#, 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\"/>. 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:1285
+#: install-methods.xml:1284
#, no-c-format
msgid "Enabling the TFTP Server"
msgstr ""
#. Tag: para
-#: install-methods.xml:1286
+#: install-methods.xml:1285
#, no-c-format
msgid "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled."
msgstr ""
#. Tag: para
-#: install-methods.xml:1291
+#: install-methods.xml:1290
#, no-c-format
msgid "In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package."
msgstr ""
#. Tag: para
-#: install-methods.xml:1300
+#: install-methods.xml:1299
#, 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:1310
+#: install-methods.xml:1309
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
#, 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"
@@ -1020,49 +1020,49 @@ msgid ""
msgstr ""
#. Tag: title
-#: install-methods.xml:1340
+#: install-methods.xml:1339
#, no-c-format
msgid "Move TFTP Images Into Place"
msgstr ""
#. Tag: para
-#: install-methods.xml:1341
+#: install-methods.xml:1340
#, 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:1350
+#: install-methods.xml:1349
#, 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:1381
+#: install-methods.xml:1380
#, no-c-format
msgid "boot.msg"
msgstr ""
#. Tag: para
-#: install-methods.xml:1386
+#: install-methods.xml:1385
#, 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:1394
+#: install-methods.xml:1393
#, 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:1406
+#: install-methods.xml:1405
#, no-c-format
msgid "SPARC TFTP Booting"
msgstr ""
#. Tag: para
-#: install-methods.xml:1407
+#: install-methods.xml:1406
#, 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"
@@ -1071,55 +1071,55 @@ msgid ""
msgstr ""
#. Tag: para
-#: install-methods.xml:1423
+#: install-methods.xml:1422
#, 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:1430
+#: install-methods.xml:1429
#, 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:1441
+#: install-methods.xml:1440
#, no-c-format
msgid "SGI TFTP Booting"
msgstr ""
#. Tag: para
-#: install-methods.xml:1442
+#: install-methods.xml:1441
#, 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:1550
+#: install-methods.xml:1549
#, no-c-format
msgid "Automatic Installation"
msgstr ""
#. Tag: para
-#: install-methods.xml:1551
+#: install-methods.xml:1550
#, 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:1564
+#: install-methods.xml:1563
#, no-c-format
msgid "Automatic Installation Using the Debian Installer"
msgstr ""
#. Tag: para
-#: install-methods.xml:1565
+#: install-methods.xml:1564
#, 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:1572
+#: install-methods.xml:1571
#, no-c-format
msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
msgstr ""