Comment 3 for bug 476161

Can anyone confirm that if cryptsetup is not installed, the recovery shell works? If this is so and Cryptsetup does not get fixed, I will have to write a script to detect "single" in /proc/cmdline and open a shell prior to mountall, for recovery on a subsequent boot. This will be needed on all my systems, as I always use encrypted /home , swap , and tmp directories.

I've seen esc on root(NOT encrypted) filesystem fsck lead to a hung mountall, esc
on the dependent mounts (encrypted partition not ready) do the same. if this is Cryptsetup, a patch will be needed if cryptsetup doesn't get fixed upstream(bugs from Jaunty are still unfixed there).

> Date: Mon, 9 Nov 2009 16:25:51 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 476161] Re: Recovery shell does not spawn if mountall stopped by esc (mountall 1.0)
>
> Sounds like cryptsetup is taking the escape key instead
>
> ** Package changed: mountall (Ubuntu) => cryptsetup (Ubuntu)
>
> --
> Recovery shell does not spawn if mountall stopped by esc (mountall 1.0)
> https://bugs.launchpad.net/bugs/476161
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Find the right PC with Windows 7 and Windows Live.
http://www.microsoft.com/Windows/pc-scout/laptop-set-criteria.aspx?cbid=wl&filt=200,2400,10,19,1,3,1,7,50,650,2,12,0,1000&cat=1,2,3,4,5,6&brands=5,6,7,8,9,10,11,12,13,14,15,16&addf=4,5,9&ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen2:112009