netdev - Re: [iproute2 00/22] Support for stateless configuration (read from /etc and /usr)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 19 Jul 2023 14:36:28 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Gioele Barabucci <gioele@...rio.it>
Cc: netdev@...r.kernel.org
Subject: Re: [iproute2 00/22] Support for stateless configuration (read from
 /etc and /usr)

On Wed, 19 Jul 2023 20:50:44 +0200
Gioele Barabucci <gioele@...rio.it> wrote:

> Dear iproute2 maintainers,
> 
> this patch series adds support for the so called "stateless" configuration
> pattern, i.e. reading the default configuration from /usr while allowing
> overriding it in /etc, giving system administrators a way to define local
> configuration without changing any distro-provided files.
> 
> In practice this means that each configuration file FOO is loaded
> from /usr/lib/iproute2/FOO unless /etc/iproute2/FOO exists.

I don't understand the motivation for the change.
Is /etc going away in some future version of systemd?

Perhaps just using an an environment variable instead of hard coding
/etc/iproute2 directory.

I do like the conslidation of the initialize_dir code though.