I did some more testing. My conclusion is once I inhibit the system from
trying (I do not mount crypted disks at boottime I mount crypted disks
upon GDM/shell login) to mount crypted disk at boot time everything
works out.
/etc/default/cryptdisks:
# Run cryptdisks at startup ?
CRYPTDISKS_ENABLE=No
I did not have to disable anything in cryptsetup before mountall package
was installed, so I'm not sure if this is a mountall bug, a cryptsetup
bug or is a bug for both of em.
# apt-cache policy mountall cryptsetup
mountall:
Installed: 0.1.6
Candidate: 0.1.6
Version table:
*** 0.1.6 0
500 http://ch.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status
cryptsetup:
Installed: 2:1.0.6+20090405.svn49-1ubuntu4
Candidate: 2:1.0.6+20090405.svn49-1ubuntu4
Version table:
*** 2:1.0.6+20090405.svn49-1ubuntu4 0
500 http://ch.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status
--
stuck on standard fstab
https://bugs.launchpad.net/bugs/430684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
