From: David Ahern <dsahern@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next v2] arpd: remove
Date: Wed, 18 Nov 2026 15:59:57 -0700 [thread overview]
Message-ID: <ce450062-7a21-4b4e-b96d-06c12cc629cb@kernel.org> (raw)
In-Reply-To: <20261108203417.1207407-1-stephen@networkplumber.org>
On 11/8/26 2:33 PM, Stephen Hemminger wrote:
> arpd, the userspace ARP daemon, passed away quietly in misc/.
> Born last century to Alexey Kuznetsov, it spent its youth answering kernel
> neighbour solicitations for networks too large for the in-kernel table,
> keeping its memories in a Berkeley DB file. In its final years its only
> visitors were tree-wide cleanups, who stopped by to add an SPDX tag and
> fix its whitespace. It outlived the problem it was built to solve, as
> neighbour tables grew up and learned to take care of themselves.
>
> arpd was predeceased by its lifelong companion libdb, which Fedora has
> already laid to rest; Debian is making arrangements. Unable to build
> without it, arpd chose to go with dignity rather than be kept alive on
> a bundled copy. It is survived by ip neigh, which does the job without
> a database. In lieu of flowers, please drop libdb from your build
> dependencies.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> v2 - claude review found some more dead bits to remove
>
> Makefile | 5 -
> README | 11 +-
> configure | 23 --
> man/man8/arpd.8 | 69 ----
> misc/.gitignore | 1 -
> misc/Makefile | 7 -
> misc/arpd.c | 841 ------------------------------------------------
> 7 files changed, 2 insertions(+), 955 deletions(-)
> delete mode 100644 man/man8/arpd.8
> delete mode 100644 misc/arpd.c
>
applied to iproute2-next
prev parent reply other threads:[~2026-11-18 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 20:33 [PATCH iproute2-next v2] arpd: remove Stephen Hemminger
2026-11-18 22:59 ` David Ahern [this message]
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=ce450062-7a21-4b4e-b96d-06c12cc629cb@kernel.org \
--to=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox