On Fri, 15.08.14 15:35, Ivan Shapovalov (intelfx...@gmail.com) wrote: > > That should be enough. (You don't need to individually order the > > systemd-fsck@.service instances for the other devices after your > > service, since they are already ordered after systemd-fsck-root.service, > > and you order yourself before that, so all is good). > > One more question. What about setups with no initrd and read-write rootfs? > In such cases, the resume unit must silently skip itself. > > ConditionPathIsReadWrite=!/ doesn't seem to be useful here: with initramfs > this check will yield a false-negative.
I am pretty sure the hibernation stuff should only be supported when an initrd is used. And in that case we should simply not pull in the hibernation service into the non-initrd initial transaction (or in other words, only pull it in by initrd.target, but not otherwise). Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
