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

Lennart Poettering lennart at poettering.net
Fri Feb 21 08:15:50 PST 2014

On Fri, 21.02.14 16:31, Jason A. Donenfeld (Jason at zx2c4.com) wrote:

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

Well, packaging is hard, let's go shopping.

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

Well, it will have these configs as soon as we do the veth thing for

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

The idea is that we run the same image inside and outside of a
container, unmodified.

If people build systemd from scratch then they should just pass
--disable-networkd. If they get it from distributions then the
distributions should make a choice whether they either split it out into
its own package, or whether they disable it by default but leave it in
the default package, or whether they leave it enabled and ship it by
default, or whether they do that but also add more default configuration
to it.

I fail to see who you are trying to make happy here: people who build
from source with everything compile-time enabled but then want that
stuff to be runtime-disabled by default?  That sounds like a very weird
combination to support out-of-the-box. If you compile it yourself turn
it off completely, or turn it on completely, but the middle thing is
really not for those people: it's for the distributions.


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list