systemd-resolved and systemd-oomd fail in the live ISO

These services fail, apparently due to missing /var/tmp

The eos-live-boot-overlayfs-setup.service sets up an overlayfs at /var/tmp and the services do eventually start successfully, so this maybe a systemd unit ordering issue.

[dsd]

Sounds familiar! oomd should be disabled though, as we have our own low memory handling solution (may need to be put back in place if not done already) and aren't going to migrate to another solution at this time.

What I could find about OOM handling was https://github.com/endlessm/eos-boot-helper/blob/master/10-eos-oom-policy.conf. I notice eos6 doesn't have systemd-oomd, but are you sure that enabling in EOS7 will cause problems?

Can do a patch to disable it anyway

[dsd]

Not sure if it will cause problems or not, last time we tested it in low memory conditions we didn't like the behaviour.

Not that we're entirely happy with our own solution either (psi-monitor from eos-boot-helper). But we were thinking to stick with that for now as the immediate simple/consistent path forward.

Should be fixed by #194