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

Jason A. Donenfeld Jason at zx2c4.com
Fri Feb 21 07:31:28 PST 2014

On Fri, Feb 21, 2014 at 4:19 PM, Lennart Poettering
<lennart at poettering.net> wrote:
> Well, ultimately it's up the distributions to decide what they want to
> enable and what not.

True, but this requires manual patching and fixing up of `make
install`, which is a bummer.

> I think networkd is a good choice, especially
> since it doesn't break anything without configs around.

But it shouldn't even run when it doesn't have configs. It seems
totally superfluous and wasteful to do so.

> Moreover, we will probably start shipping some .network files by default
> to auto configure the veth tunnels of nspawn automatically.

Couldn't nspawn then run it, as needed? Seems wasteful to have this
running all the time, especially because most people never even touch

> 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
> containers.

Having it not enabled by default doesn't destroy the out-of-box
functionality, since configuration files need to be written anyway. An
administrator will write this configs, and then type "systemctl enable
systemd-networkd". Otherwise, it doesn't need to be running.

> but ultimately it's
> the distro's choice what they want to do.

"complain downstream" isn't a very nice thing to hear.

More information about the systemd-devel mailing list