]> code.ossystems Code Review - openembedded-core.git/commit
systemd: arrange for volatile /etc/resolv.conf
authorChristopher Larson <chris_larson@mentor.com>
Thu, 5 Nov 2015 03:19:19 +0000 (20:19 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Mon, 11 Jan 2016 23:23:16 +0000 (23:23 +0000)
commit7f087f161e8942bcd35f88999dfca418f01cd7fa
tree768365f59d50669a4abc9cb555b204c7e4e342b2
parent1fb3e1a4bbf36a5b46d126a478d42d0b94f43182
systemd: arrange for volatile /etc/resolv.conf

On sysvinit systems, volatiles is configured to make /etc/resolv.conf symlink
to a file in a volatile path, which lets us write to /etc/resolv.conf for
read-only-rootfs. For systemd, this isn't set up unless we enable
systemd-resolved, which we don't by default. When it's not enabled, create the
/etc/resolv.conf symlink and ensure the volatile path is created on boot with
tmpfiles.d.

Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
meta/recipes-core/systemd/systemd_228.bb