В Thu, 8 May 2014 17:54:12 +0400
Alexander Tsoy <[email protected]> пишет:
> Here is a possible fix that works fine on my system (hostonly +
> hostonly-cmdline + empty /etc/crypttab + no rd.luks* in kernel
> cmdline).
>
> diff --git a/modules.d/90crypt/parse-crypt.sh
> b/modules.d/90crypt/parse-crypt.sh
> index a6b5252..8bb1328 100755
> --- a/modules.d/90crypt/parse-crypt.sh
> +++ b/modules.d/90crypt/parse-crypt.sh
> @@ -35,8 +35,8 @@ else
> printf -- 'ENV{ID_FS_TYPE}=="crypto_LUKS", '
> printf -- 'ENV{ID_FS_UUID}=="*%s*", ' $luksid
> printf -- 'RUN+="%s --settled --unique --onetime '
> $(command -v initqueue)
> - printf -- '--name systemd-cryptsetup-%%k %s start '
> $(command -v systemctl)
> - printf -- 'systemd-cryptsetup@luks$$(dev_unit_name
> -$env{ID_FS_UUID}).service"\n'
> + printf -- '--name crypt-run-generator-%%k %s '
> $(command -v crypt-run-generator)
> + printf -- '$env{DEVNAME} luks-$env{ID_FS_UUID}"\n'
> } >> /etc/udev/rules.d/70-luks.rules.new
> fi
> fi
>
Hmm.. I just walked through commit history and it turned out that my
patch almost reverts your following commits (with minor difference in
initqueue args):
ab9b04f55bb9917749e9ddb52ce8f5f1ef56af99
5ac8420abcfd5665f712f18f8678f3977e039969
What was the reason to replace crypt-run-generator with "systemctl
start systemd-cryptsetup@..." in udev rules?
--
Alexander Tsoy
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
