On Mon, May 18, 2015 at 6:55 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Fri, 15.05.15 22:49, Tom Gundersen (t...@jklm.no) wrote: > >> On Fri, May 15, 2015 at 10:02 PM, Lennart Poettering >> <lenn...@poettering.net> wrote: >> > On Fri, 15.05.15 12:56, Michael Marineau (michael.marin...@coreos.com) >> > wrote: >> > >> >> (build time option to ./configure that is) >> > >> > I guess I'd be OK with that... >> >> It would be a shame if we started diverging on the defaults I think. >> Would be nice if we could come up with some scheme that would work for >> everyone. Would an option be to use a script to append >> IPForward='kernel' to your network files on upgrades? Pretty dirty, >> but I don't know how you usually deal with config changes... > > Well, I think it is fine if downstream departs from our defaults...
Ok, I guess. As there appears to be no better way. > Another idea would be to add DefaultIPForward= to > /etc/systemd/networkd.conf that alters defaults for networks, the same > way as we have DefaultXYZ= in /etc/systemd/system.conf that affects > unit defaults? In principle it sounds like a feature we could add, but I think we should have a better usecase than just backwards compatibility, then I'd rather go with the compile-time switch I guess. -t _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel