So many revealings in one reply! Thank you very much for explaining it
in basic terms to me.
Mantas Mikulėnas píše v Ne 04. 11. 2018 v 18:18 +0200:
> You should just put an entry in /etc/crypttab instead, and let
> systemd-cryptsetup handle it via the existing dependencies mechanism.
>
>
On Sun, Nov 4, 2018 at 5:47 PM Marek Howard wrote:
> Hello.
>
> I'm trying to unlock my LUKS (type luks2) encrypted backup drive via
> udev rule /etc/udev/rules.d/99-unlock-backupdrive.rules:
>
> ACTION=="add", SUBSYSTEM=="block", ENV{DEVTYPE}=="partition", \
> ENV{ID_SERIAL}=="FZ133888",
Hello.
I'm trying to unlock my LUKS (type luks2) encrypted backup drive via
udev rule /etc/udev/rules.d/99-unlock-backupdrive.rules:
ACTION=="add", SUBSYSTEM=="block", ENV{DEVTYPE}=="partition", \
ENV{ID_SERIAL}=="FZ133888", ENV{ID_PART_ENTRY_UUID}=="8c347a-02", \
