On Fri, Feb 21, 2014 at 4:44 PM, Michael Biebl <mbi...@gmail.com> wrote: > 2014-02-21 16:31 GMT+01:00 Jason A. Donenfeld <ja...@zx2c4.com>: >> On Fri, Feb 21, 2014 at 4:19 PM, Lennart Poettering >> <lenn...@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. > > What about Zbigniews idea of using something like: > ConditionDirectoryNotEmpty=/etc/systemd/network/ > > Would that work?
We'd have to look in all the possible folders, and there may (and due to 99-deafult.link, always will) be files there, so we don't really have a reasonable test. When we start shipping some default .network files it becomes even harder (e.g. the thing Lennart mentioned which will only apply for given interfaces that we create ourselves inside systemd-nspawn). We'll then always have config files, but they may not necessarily apply (and we can't know whether or not they ever will). Cheers, Tom _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
