https://bugzilla.novell.com/show_bug.cgi?id=875373
https://bugzilla.novell.com/show_bug.cgi?id=875373#c5
--- Comment #5 from Thomas Blume 2014-04-28 13:33:16 UTC ---
I still see a problem with ordering here.
/home is a directory not required in the init process, but /var (resp. /run)
is.
Making /var depending on the availability of /home is IMHO not quite correct.
In order to fullfill this, you will need to make /home available as early as
the mounts required for the init process.
In order to do so, you could use the rd.luks parameters to enable the crypsetup
of /home from within the initrd. (see details at:
http://www.freedesktop.org/software/systemd/man/systemd-cryptsetup-generator...)
This should be early enough to not conflict with the
systemd-tmpfiles-setup.service.
However, if you really want to make sure that the crypt setup is done before
the tmpfiles get created, you need to add a dependency in in
/usr/lib/systemd/system/systemd-tmpfiles-setup.service, e.g. change:
After=systemd-readahead-collect.service systemd-readahead-replay.service
local-fs.target
into:
After=systemd-readahead-collect.service systemd-readahead-replay.service
local-fs.target cryptsetup.target
Still, this can only be a custom setup, because if a user is not using crypted
devices, cryptsetup.target wouldn't be active and this dependency should fail.
Can you try wheter either of these suggestions work?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.