Bug#141102: Not release notes
On Wed, Apr 10, 2002 at 07:24:39PM -0700, Chris Tillman wrote:
> Does this address the issue?
>
> Index: inst-methods.sgml
> ===================================================================
> RCS file: /cvs/debian-boot/boot-floppies/documentation/en/inst-methods.sgml,v
> retrieving revision 1.117
> diff -u -r1.117 inst-methods.sgml
> --- inst-methods.sgml 2002/04/08 14:49:07 1.117
> +++ inst-methods.sgml 2002/04/11 02:23:01
> @@ -993,6 +993,7 @@
> If you get <tt>SIOCSRARP: Invalid argument</tt> you probably need to
> load the rarp kernel module or else recompile the kernel to support
> RARP. Try <tt>modprobe rarp</tt> and then try the rarp command again.
> +Newer kernels use an rarpd user program rather than a module.
This should be in a separate paragraph, like the part about SunOS, because
the method is completely different. The 'rarp' command is not used, and
none of the preceding text applies. How about something like this:
--
- mdz
--- inst-methods.sgml.old Wed Apr 10 22:57:41 2002
+++ inst-methods.sgml Wed Apr 10 22:58:20 2002
@@ -1020,19 +1020,25 @@
OpenBoot <tt>.enet-addr</tt> command, or ]]> boot into ``Rescue'' mode
(e.g., from the rescue floppy) and use the command
<tt>/sbin/ifconfig eth0</tt>.
- <p>
-In GNU/Linux you need to populate the kernel's RARP table. To do this
-execute
+<p>
+On systems using a Linux 2.2.x kernel, you need to populate the kernel's
+RARP table. To do this execute
<example>
/sbin/rarp -s <var>client-hostname</var> <var>client-enet-addr</var>
/usr/sbin/arp -s <var>client-ip</var> <var>client-enet-addr</var>
</example>
- <p>
+<p>
If you get <tt>SIOCSRARP: Invalid argument</tt> you probably need to
load the rarp kernel module or else recompile the kernel to support
RARP. Try <tt>modprobe rarp</tt> and then try the rarp command again.
+
+<p>
+On systems using a Linux 2.4.x kernel, there is no rarp module, and you
+should instead use the rarpd program. The procedure is similar to that used
+under SunOS below.
+
<p>
Under SunOS, you need to ensure that the Ethernet hardware address for
the client is listed in the ``ethers'' database (either in the
Reply to: