All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: RARP support disapeard in kernel 2.6.x ?
Date: Tue, 21 Sep 2004 14:13:31 -0400	[thread overview]
Message-ID: <cipqh4$g9d$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.60L.0409211511290.15099@rudy.mif.pg.gda.pl>

Tomasz Kłoczko wrote:
> On Tue, 21 Sep 2004, Tigran Aivazian wrote:
> 
>> also, the manpage rarpd(8) says:
>>
>> OBSOLETES
>>       This  rarpd obsoletes kernel rarp daemon present in Linux 
>> kernels up to
>>       2.2 which was controlled by the rarp(8) command.
>>
>> which means the kernel version was removed much earlier.
> 
> 
> # ps aux | grep rarpd
> root      4563  0.0  0.0  1456  332 ?        Ss   15:02   0:00 
> /usr/sbin/rarpd
> # rarp -a
> This kernel does not support RARP.
> 
> Maybe I'm wrong but IIRC rarpd as same as arpd was only neccessary for 
> large RARP table.

Is it possible that you are using an old version of the rarp command 
which is trying to use the kernel RARP rather than using the rarpd?


-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  parent reply	other threads:[~2004-09-21 18:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21 12:36 RARP support disapeard in kernel 2.6.x ? Tomasz Kłoczko
2004-09-21 12:44 ` Tigran Aivazian
2004-09-21 12:52   ` Tomasz Kłoczko
2004-09-21 12:54     ` Tigran Aivazian
2004-09-21 12:58       ` Tigran Aivazian
2004-09-21 13:00         ` Tigran Aivazian
2004-09-21 13:17           ` Tomasz Kłoczko
2004-09-21 17:08             ` Peter Buckingham
2004-09-21 18:13             ` Bill Davidsen [this message]
2004-09-21 18:28               ` Tomasz Kłoczko
2004-09-21 19:54                 ` David S. Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='cipqh4$g9d$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.