bootmisc - I don't understand, why would you use pam_mount if you were going to mount the partition at boot time? pam_mount is intended for the case where mounts need to be made available at the moment a user logs in, possibly using user-provided credentials. If you're mounting at boot time, there are much better solutions available to you in any case.
I don't think that helps with this current problem, which to be sure is a serious regression that we'll want to get to the bottom of; but if you're having to move data around anyway to get access to it again in karmic, I would suggest using a more "standard" solution - cryptsetup (LUKS, /etc/crypttab) for boot-time mounts, or ecryptfs for per-user encrypted data. -- karmic's mount.crypt fails to mount Hardy's encrypted partition https://bugs.launchpad.net/bugs/476460 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
