On Tue, May 27, 2014 at 12:41 PM, Michael Biebl <mbi...@gmail.com> wrote: > 2014-05-27 4:38 GMT+02:00 Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl>: >> On Mon, May 26, 2014 at 09:39:46PM +0200, Tom Gundersen wrote: >>> When enabled in [Network] it will set up a dhcp server on the interface, >>> listening >>> on one of its statically configured IPv4 addresses and with a fixed size >>> pool of >>> leases determined from it. >> Hi Tom, >> before looking at the code, a couple of general questions: >> - does the DHCP server have to be part of networkd? Isn't the job >> of acquiring addresses and giving out addresses separate and shouldn't >> two different processes be responsible? > > I have to agree with Zbigniew here. This looks like feature creep.
As I already stated, if it turns out that things will be simpler with this separate, we could easily make that change later. I do agree with Marcel that that is unlikely though. > Also, IIRC, the scope of networkd was to establish network connections > in a minimal environment, like an initramfs. > I'm pretty sure we don't need a DHCP server in a initramfs... networkd should be usable in a minimal environment, like an initramfs. However, we also target other simple setups like virtualization/containers (inside and outside, which is what this feature is mainly meant for). Cheers, Tom _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel