Update of POT and PO files for the manual

1 files changed, 6 insertions, 6 deletions

diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot
index a59ab8a27..878d47e98 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"
-"POT-Creation-Date: 2006-03-12 23:40+0000\n"
+"POT-Creation-Date: 2006-03-19 13:45+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"
@@ -920,7 +920,7 @@ msgid ""
       "  sm=255.255.255.0:\\\n"
       "  sa=192.168.1.1:\\\n"
       "  ha=0123456789AB:\n"
-      "</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI Indys you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>"
+      "</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI machines you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>"
 msgstr ""
 
 #: install-methods.xml:1251
@@ -1042,7 +1042,7 @@ msgstr ""
 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"
       "# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
-      "</screen></informalexample> to turn off Path MTU discovery, otherwise the Indy's PROM can't download the kernel. Furthermore, make sure TFTP packets are sent from a source port no greater than 32767, or the download will stall after the first packet. Again, it's Linux 2.4.X tripping this bug in the PROM, and you can avoid it by setting <informalexample><screen>\n"
+      "</screen></informalexample> to turn off Path MTU discovery, otherwise the SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets are sent from a source port no greater than 32767, or the download will stall after the first packet. Again, it's Linux 2.4.X tripping this bug in the PROM, and you can avoid it by setting <informalexample><screen>\n"
       "# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
       "</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses."
 msgstr ""
@@ -1161,19 +1161,19 @@ msgstr ""
 #: install-methods.xml:1533
 #, no-c-format
 #. Tag: title
-msgid "SGI Indys TFTP Booting"
+msgid "SGI TFTP Booting"
 msgstr ""
 
 #: install-methods.xml:1534
 #, no-c-format
 #. Tag: para
-msgid "On SGI Indys 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>."
+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 ""
 
 #: install-methods.xml:1546
 #, no-c-format
 #. Tag: title
-msgid "Broadcom BCM91250A TFTP Booting"
+msgid "Broadcom BCM91250A and BCM91480B TFTP Booting"
 msgstr ""
 
 #: install-methods.xml:1547