summaryrefslogtreecommitdiff
path: root/en/install-methods
diff options
context:
space:
mode:
authorFrans Pop <elendil@planet.nl>2006-08-16 20:36:24 +0000
committerFrans Pop <elendil@planet.nl>2006-08-16 20:36:24 +0000
commit7b25bd0caf707ef6dfa239e2d69d0e2817b3a1a9 (patch)
tree9b1515a9645228c4e07d22dd0ea39f69e39e8b0b /en/install-methods
parent8584cea9ea16f10fc7d8f13ec2ca043ae7bd491c (diff)
downloadinstallation-guide-7b25bd0caf707ef6dfa239e2d69d0e2817b3a1a9.zip
- Update info on setting up RARP; thanks Nathanael Nerode
- Remove info for servers running 2.2 kernels, these should no longer be allowed to exist
Diffstat (limited to 'en/install-methods')
-rw-r--r--en/install-methods/tftp/rarp.xml51
1 files changed, 10 insertions, 41 deletions
diff --git a/en/install-methods/tftp/rarp.xml b/en/install-methods/tftp/rarp.xml
index e59b94587..89ad3fb7e 100644
--- a/en/install-methods/tftp/rarp.xml
+++ b/en/install-methods/tftp/rarp.xml
@@ -3,10 +3,10 @@
<sect2 condition="supports-rarp" id="tftp-rarp">
- <title>Setting up RARP server</title>
+ <title>Setting up RARP server</title>
<para>
-To setup RARP, you need to know the Ethernet address (a.k.a. the MAC address)
+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
@@ -18,47 +18,16 @@ 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
+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.
-In SunOS 4, issue the command (as root):
-<userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use
-<userinput>/usr/sbin/rarpd -a</userinput>.
+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).
</para>
</sect2>