On Mon, 27.06.11 17:04, yoshi watanabe ([email protected]) wrote: > > my guess is that systemd populates /var before mounting it, and then > mounts it over and some files are possibly lost. or maybe because the > /var is empty before mount and that causes problems.
systemd is very careful in not using data from /usr or /var before it is mounted. (After all we introduced /run just to be able to deal with this kind of problems properly). So, I doubt that systemd is really doing something wrong here, more likely some other code involved in early boot is responsible. For example, the device mapper libs might be trying to access /var/lock or so. But that's just a guess. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
