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

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

On Fri, 21.02.14 17:14, Jason A. Donenfeld (Jason at zx2c4.com) wrote:

> On Fri, Feb 21, 2014 at 5:11 PM, Tom Gundersen <teg at jklm.no> wrote:
> >
> > In the not-too-distant future we'll start shipping some configuration
> > files (as Lennart mentioned to do with nspawn). These are files that
> > in most cases will not apply, and shouldn't interfere with your
> > existing networking solutions, but we want them to apply in the very
> > special circumstances that we know are safe (in a nspawn container, on
> > a device we create ourselves with a specific purpose).
> But in the case of nspawn using it, then nspawn should start it.
> Otherwise if nobody is going to use nspawn, why start it?

That'd be all backwards...

nspawn is not going to reach into the container and start specific
services there as it pleases. The code inside the container should
figure out what it wants to run.


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list