From 74e594185d4421e862806c29fc0519dd337f1229 Mon Sep 17 00:00:00 2001
From: Frans Pop <elendil@planet.nl>
Date: Sun, 19 Mar 2006 13:43:49 +0000
Subject: Update of original English docs

---
 fi/install-methods/install-tftp.xml | 10 +++++-----
 fi/install-methods/tftp/bootp.xml   |  4 ++--
 2 files changed, 7 insertions(+), 7 deletions(-)

(limited to 'fi/install-methods')

diff --git a/fi/install-methods/install-tftp.xml b/fi/install-methods/install-tftp.xml
index b3f577937..5f4291999 100644
--- a/fi/install-methods/install-tftp.xml
+++ b/fi/install-methods/install-tftp.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 31138 untranslated -->
+<!-- original version: 35613 untranslated -->
 
  <sect1 condition="supports-tftp" id="install-tftp">
  <title>Preparing Files for TFTP Net Booting</title>
@@ -125,7 +125,7 @@ server:
 # echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc
 </screen></informalexample>
 
-to turn off Path MTU discovery, otherwise the Indy's PROM can't
+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
@@ -308,10 +308,10 @@ for additional system-specific configuration information.
    </sect3>
 
    <sect3 arch="mips">
-   <title>SGI Indys TFTP Booting</title>
+   <title>SGI TFTP Booting</title>
 <para>
 
-On SGI Indys you can rely on the <command>bootpd</command> to supply
+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
@@ -321,7 +321,7 @@ the <userinput>filename=</userinput> option in
    </sect3>
 
    <sect3 arch="mips">
-   <title>Broadcom BCM91250A TFTP Booting</title>
+   <title>Broadcom BCM91250A and BCM91480B TFTP Booting</title>
 <para>
 
 You don't have to configure DHCP in a special way because you'll pass the
diff --git a/fi/install-methods/tftp/bootp.xml b/fi/install-methods/tftp/bootp.xml
index b6683f0ad..51c33ed7f 100644
--- a/fi/install-methods/tftp/bootp.xml
+++ b/fi/install-methods/tftp/bootp.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 28997 untranslated -->
+<!-- original version: 35613 untranslated -->
 
 
   <sect2 condition="supports-bootp" id="tftp-bootp">
@@ -50,7 +50,7 @@ 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
+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>
-- 
cgit v1.2.3