[systemd-devel] [PATCH] random-seed: break ordering cycle with encrypted tmp partitions
fcrozat at suse.com
Tue Nov 15 09:09:25 PST 2011
Le mardi 15 novembre 2011 à 19:20 +1100, Tom Gundersen a écrit :
> The cycle is caused by our ordering is to coarse. We order random-seed-load after
> all filesystems, but all we really care about is /var/lib being mounted rw.
> Waiting for all filesystems means that we would also have to wait for /tmp, which
> might depend on random-seed-load.
> Maybe the best way to solve this would have been to allow .path units to not only
> wait for a path, but also wait for it to have a specific permission.
> However, since we cannot do that at the moment, this should do the trick for now:
> We would like to wait for var.mount if /var is on a separate partition, and
> we'd like to wait for remount-rootfs.service otherwise. I couldn't figure out how
> to do this conditionally, so we unconditionally wait for both.
I did a different fix for openSUSE 12.1 (a bit dirty) where cryptsetup
creates a systemd-random-seed-load.service unit in /run (or in /etc I'm
not 100% sure), depending if tmp is encrypted or not. Patch is included
in another patch to fix lvm on top of cryptsetup (see
https://build.opensuse.org/package/view_file?file=storage-after-cryptsetup.patch&package=systemd&project=home%3Afcrozat%3Asystemd&rev=f050db3b3513798555eaca39d76e4a16 and yes, it is ugly ;)
I think your option of adding var.mount will cause systemd to complain
when /var is not a separate partition..
Frederic Crozat <fcrozat at suse.com>
More information about the systemd-devel