From 1ea73eea5ecc6a8ed901316049259aee737ee554 Mon Sep 17 00:00:00 2001
From: Joey Hess <joeyh@debian.org>
Date: Fri, 7 Oct 2005 19:51:38 +0000
Subject: move manual to top-level directory, split out of debian-installer
 package

---
 fi/install-methods/tftp/rarp.xml | 64 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 64 insertions(+)
 create mode 100644 fi/install-methods/tftp/rarp.xml

(limited to 'fi/install-methods/tftp/rarp.xml')

diff --git a/fi/install-methods/tftp/rarp.xml b/fi/install-methods/tftp/rarp.xml
new file mode 100644
index 000000000..c6fd184d4
--- /dev/null
+++ b/fi/install-methods/tftp/rarp.xml
@@ -0,0 +1,64 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+
+  <sect2 condition="supports-rarp" id="tftp-rarp">
+   <title>Setting up RARP server</title>
+<para>
+
+To setup 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>/sbin/ifconfig eth0</userinput>.
+
+</para><para>
+
+On a RARP server system using a Linux 2.2.x kernel,
+you need to populate the kernel's RARP table.
+To do this, run the following commands:
+
+<informalexample><screen>
+# <userinput>/sbin/rarp -s
+<replaceable>client-hostname</replaceable>
+<replaceable>client-enet-addr</replaceable></userinput>
+
+# <userinput>/usr/sbin/arp -s
+<replaceable>client-ip</replaceable>
+<replaceable>client-enet-addr</replaceable></userinput>
+</screen></informalexample>
+
+If you get
+
+<informalexample><screen>
+SIOCSRARP: Invalid argument
+</screen></informalexample>
+
+you probably need to load the RARP kernel module or else recompile the
+kernel to support RARP.  Try <userinput>modprobe rarp</userinput> and
+then try the <command>rarp</command> command again.
+
+</para><para>
+
+On a RARP server system using a Linux 2.4.x kernel,
+there is no RARP module, and
+you should instead use the <command>rarpd</command> program.  The
+procedure is similar to that used under SunOS in the following
+paragraph.
+
+</para><para>
+
+Under SunOS, 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.
+In SunOS 4, issue the command (as root):
+<userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use
+<userinput>/usr/sbin/rarpd -a</userinput>.
+
+</para>
+  </sect2>
-- 
cgit v1.2.3