Hey Jochen, On 03/12/2008 Jochen Schulz wrote: > Hi, > > I am trying to use an encrypted /home filesystem on a system whose boot > process is managed by insserv. > > Unfortunately, the prompt from /etc/init.d/cryptdisks isn't visible on > screen at the time I am supposed to enter the passphrase. The system > just sits idle waiting for me to enter it. Above the cursor are kernel > messages about detected devices and information about a boot log being > created.
Do you use any kind of bootsplash implementation, like splashy or usplash? how does your exact setup look like? is /home directly on top of the dm-crypt device, or do you use LVM? What exactly do you see on the boot screen? Are you asked for a passphrase input at all? If yes, how exactly does it look like? Please provide more information so that we're able to track down the actual bug. > What makes things worse (and this report Severity: important, at least > in my opinion) is that, more often than not, my keypresses are echoed to > the screen and don't get read by cryptseup at all. Since cryptsetup is > the only software needing user interaction at boot time (and both > situations look exactly equally on screen), I strongly suspect it to be > the culprit. It looks like it closes stdin even before I have the chance > to enter my passphrase. I prepared a new upload of cryptsetup which fixes several bugs. Could you give that a try and report whether it fixes your bug as well? You can find the new packages at http://people.debian.org/~mejo/cryptsetup/ greetings, jonas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org