On 8 July 2013 14:31, Jonathan Liu <net...@gmail.com> wrote: > Check if running systemd in postinst by testing for existence of > /sys/fs/cgroup/systemd instead of checking if systemd-tmpfiles > exists in PATH. This is so populate-volatile.sh update is called > instead of systemd-tmpfiles --create if the system has > systemd-tmpfiles installed but was booted using sysvinit.
So this says to me that having two ways of creating files in volatile locations is stupid. Should we just split out populate-volatiles from initscripts into it's own package so it can be used by pure systemd images, and split out systemd-tmpfiles so it isn't enabled by default? This patch solves the issue for resolvconf but there are plenty of other recipes that don't install files/postinst for both populate-volatile and systemd-tmpfiles. Ross _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
