From: Stephen Hemminger <stephen@networkplumber.org>
To: Max Gautier <mg@max.gautier.name>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] Makefile: use systemd-tmpfiles to create /var/lib/arpd
Date: Mon, 11 Mar 2024 18:30:07 -0700 [thread overview]
Message-ID: <20240311183007.4a119eeb@hermes.local> (raw)
In-Reply-To: <Ze-Fj2RwYnM0WgWi@framework>
On Mon, 11 Mar 2024 23:28:31 +0100
Max Gautier <mg@max.gautier.name> wrote:
> On Mon, Mar 11, 2024 at 12:40:03PM -0700, Stephen Hemminger wrote:
> > On Mon, 11 Mar 2024 17:57:27 +0100
> > Max Gautier <mg@max.gautier.name> wrote:
> >
> > > Only apply on systemd systems (detected in the configure script).
> > > The motivation is to build distributions packages without /var to go
> > > towards stateless systems, see link below (TL;DR: provisionning anything
> > > outside of /usr on boot).
> > >
> > > The feature flag can be overridden on make invocation:
> > > `make USE_TMPFILES_D=n DESTDIR=<install_loc> install`
> > >
> > > Links: https://0pointer.net/blog/projects/stateless.html
> >
> > Why does arpd need such hand holding, it is rarely used, maybe should just not be built.
>
> The commit introducing the install of that directory is quite old
The problem is that build environment != runtime environment for embedded systems.
But arpd really is legacy/dead/rotting code at this point.
next prev parent reply other threads:[~2024-03-12 1:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 16:57 [PATCH iproute2-next] Makefile: use systemd-tmpfiles to create /var/lib/arpd Max Gautier
2024-03-11 19:40 ` Stephen Hemminger
2024-03-11 22:28 ` Max Gautier
2024-03-12 1:30 ` Stephen Hemminger [this message]
2024-03-12 8:22 ` Max Gautier
2024-03-12 21:24 ` Stephen Hemminger
2024-03-12 21:34 ` Max Gautier
2024-03-12 22:19 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2024-03-13 9:16 Max Gautier
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=20240311183007.4a119eeb@hermes.local \
--to=stephen@networkplumber.org \
--cc=mg@max.gautier.name \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).