From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] datatype: rt_symbol_table_init() to search for iproute2 configs
Date: Fri, 22 Dec 2023 13:04:32 +0100 [thread overview]
Message-ID: <ZYV7UAC3jZyXFM4K@calendula> (raw)
In-Reply-To: <20231215211933.7371-1-phil@nwl.cc>
Hi Phil,
On Fri, Dec 15, 2023 at 10:19:33PM +0100, Phil Sutter wrote:
> There is an ongoing effort among various distributions to tidy up in
> /etc. The idea is to reduce contents to just what the admin manually
> inserted to customize the system, anything else shall move out to /usr
> (or so). The various files in /etc/iproute2 fall in that category as
> they are seldomly modified.
>
> The crux is though that iproute2 project seems not quite sure yet where
> the files should go. While v6.6.0 installs them into /usr/lib/iproute2,
> current mast^Wmain branch uses /usr/share/iproute2. Assume this is going
> to stay as /(usr/)lib does not seem right for such files.
>
> Note that rt_symbol_table_init() is not just used for
> iproute2-maintained configs but also for connlabel.conf - so retain the
> old behaviour when passed an absolute path.
Fine with me. This defines a fallback which is backward compatible.
next prev parent reply other threads:[~2023-12-22 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 21:19 [nft PATCH] datatype: rt_symbol_table_init() to search for iproute2 configs Phil Sutter
2023-12-22 12:04 ` Pablo Neira Ayuso [this message]
2023-12-22 12:09 ` Pablo Neira Ayuso
2023-12-22 16:17 ` [nft PATCH 1/2] datatype: Initialize rt_symbol_tables' base field Phil Sutter
2023-12-22 16:17 ` [nft PATCH 2/2] datatype: Describe rt symbol tables Phil Sutter
2024-01-02 21:46 ` [nft PATCH] datatype: rt_symbol_table_init() to search for iproute2 configs Phil Sutter
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=ZYV7UAC3jZyXFM4K@calendula \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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.