> Op 3 nov. 2014, om 08:37 heeft Hongxu Jia <hongxu....@windriver.com> het > volgende geschreven: > > While networkd supported, we add network config which starts > dhcp by default. > > And the customers could edit it according their own requirements. > (dhcp or static ip...) > > It refers: > https://wiki.archlinux.org/index.php/systemd-networkd > > Signed-off-by: Hongxu Jia <hongxu....@windriver.com> > --- > meta/recipes-core/systemd/systemd/oe-core.network | 8 ++++++++ > meta/recipes-core/systemd/systemd_216.bb | 6 ++++++ > 2 files changed, 14 insertions(+) > create mode 100644 meta/recipes-core/systemd/systemd/oe-core.network > > diff --git a/meta/recipes-core/systemd/systemd/oe-core.network > b/meta/recipes-core/systemd/systemd/oe-core.network > new file mode 100644 > index 0000000..fcaefc2 > --- /dev/null > +++ b/meta/recipes-core/systemd/systemd/oe-core.network
First: config files on the target shouldn't be named after the buildsystem, a better name would be 'ethernet.network' or something similar > @@ -0,0 +1,8 @@ > +[Match] > +Name=eth* Add 'en*' as well for pci devices that get renamed by udev > +[Network] > +DHCP=v4 DHCP=both or DHCP=yes would be better since that would include dhcpv6 as well > +[DHCPv4] > +UseHostname=false Why? Using the hostname makes DHCP logs a lot easier to debug. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
