[systemd-devel] [PATCH] install: Do not enable systemd-networkd by default

Lennart Poettering lennart at poettering.net
Fri Feb 21 07:19:22 PST 2014

On Fri, 21.02.14 15:03, Jason A. Donenfeld (Jason at zx2c4.com) wrote:

> On Fri, Feb 21, 2014 at 2:08 PM, Tom Gundersen <teg at jklm.no> wrote:
> > I'll just apply this patch and
> > add the /etc symlink in a follow-up.
> I appreciate merging my patch, so now administrators can disable it in
> a sane way (without having to use mask). But still, why enable it by
> default? I thought the idea of networkd was that it was an opt-in
> thing. For folks that want to use it, it's there. For folks who are
> already using something else that works, they don't need it. Enabling
> it by default seems a bit heavy handed: "you shall now use system
> resources using our network manager, my default". Seems like until
> it's got a little more wide-spread adoption, a default symlink in etc
> is inappropriate.

Well, ultimately it's up the distributions to decide what they want to
enable and what not. What we enabled like this from upstream "make
install" is simply what we thinkmakes a good choice if you build your
own system. And yupp, I think networkd is a good choice, especially
since it doesn't break anything without configs around.

Moreover, we will probably start shipping some .network files by default
to auto configure the veth tunnels of nspawn automatically. This is the
kind of functionality that should just work and that is not available
out-of-the-box with other managers, since they tend not to run in

Consider this a gentle push to leave the thing on, but ultimately it's
the distro's choice what they want to do.


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list