If PAM isn't enabled then systemd-tmpfiles on boot will fail to start with the
following error message:
Failed to copy files to /etc/pam.d: No such file or directory
This is because systemd-tmpfiles is attempting to build a usable /etc from the
skeleton in /usr/share/factory but pam.d isn't present because PAM is disabled.
Fix this by not attempting to copy pam.d in non-PAM configurations.
(From OE-Core rev: 46a54e7991b939f12a729e4d263d19130e0aea78)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
d01cd53429