Sascha Wildner <[email protected]> added the comment: The problem was caused by a bogus /etc/crypttab which was created by a (now fixed) bug in the installer that caused it to always add swap to /etc/crypttab, regardless of whether the user configured encrypted swap or not.
I have clarified the message the script prints when /etc/crypttab is found but dm(4) is not configured. See commit 667a7e9f9e095785ff8cb7c2e1fc0a8492542ae0 ---------- status: unread -> resolved _____________________________________________________ DragonFly issue tracker <[email protected]> <http://bugs.dragonflybsd.org/issue1965> _____________________________________________________
