On Fri, Jul 11, 2014, at 03:04 PM, Dave Reisner wrote: > No way. This precludes tmpfiles from creating directories in /run.
Yeah that suggestion would break other stuff too, ignore it. This does get into the ostree commit I linked to though; we could just have systemd mount /var as a tmpfs if the filesystem is readonly. I'm guessing Michael is doing something like generating a disk image that's composed using traditional rpm/dpkg type tooling which lays out skeleton directories in /var, and then booting it as readonly. That sort of situation is why we changed OSTree to auto-mount a /var tmpfs, and it's worth thinking about at least if systemd should do the same. The main concern I had is that if you're booting the system readonly to try to say recover the journald logs, it'd be kind of annoying to have them vanish... Another option is to have systemd-tmpfiles silently ignore EROFS. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
