Removing the "swap" keyword from /etc/crypttab makes things work.

Technically speaking, this keyword should not be there because I am
using the swap partition for hibernation (so mkswap should not be run).

It seems that sysvinit silently skipped the mkswap call, while systemd
now errors out.

I think systemd's behavior is preferable, but it's unfortunate that
things break during the upgrade. Would it be possible to scan
/etc/crypttab for such problems (like it's planned for /etc/inittab)?

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to