ha-HA! The problem seems to be that underscore is no longer a valid
character for the device name. I changed "sda2_crypt" to "root" and
everything works beautifully!

Now for the bad part. What the heck happened here?! WHY did "sda2_crypt"
stop being a valid target name? That name was picked for my by default
by the Hardy installer. If people upgrading to Jaunty with encrypted
filesystems are going to experience this kind of breakage then there
needs to be a guide somewhere or an automatic migration as part of the
package upgrade!

Can anyone identify exactly when this was broken?

Which package / script / binary is responsible for parsing the crypttab
file?

WHY would _ make the entire line invalid in crypttab?

Does anyone reading this actually care about this problem?

-- 
initrd no longer activating encrypted filesystems
https://bugs.launchpad.net/bugs/318892
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

Reply via email to