[systemd-devel] [WIP][RFC][PATCH] networkd: generate resolv.conf

[Kay Sievers]

On Mon, Jan 6, 2014 at 6:49 AM, Tom Gundersen <teg at jklm.no> wrote:
> This adds support to generate a basic resolv.conf in /run/systemd/network.
> This file will not take any effect unless the admin makes a symlink from
> /etc/resolv.conf.
>
> The precedence of nameservers is:
>
>  1) nameservers receieved over DHCP
>  2) nameservers statically configured in a currently active .network file
>  3) nameservers statically configured in the global networkd configuration file
>
> Note: /etc/resolv.conf is severely limited, so in the future we will likely
> rather provide a much more powerfull nss plugin (or something to that effect),
> but this should allow current users to function without any loss of
> functionality.
> ---
>
> Hi guys,
>
> This patch is not finished yet (currently only hooked up to DHCP, not to statically
> configured addresses), but I thought I'd ask for some input early on.
>
> It seems pretty clear that resolv.conf sucks, and we want somethig better (and
> that pretty soon). However, it seems simple to provide the legacy resolv.conf
> functionality at least until we have something better in place. Without it, I
> guess it will be a bit of a hassle to test networkd.
>
> So first question: do you agree with adding this functionality?

Sounds fine as long as we make sure it's a private file in the systemd
directory. PPP does something similar.

We should make sure that people understand resolv.conf a rescue for
rather broken tools that rely on it, not something we will carry
forward as a primary interface like fstab.

So, writing one out in a private directory sounds fine, but it should
have a few magic as it can have.

Kay