On Mon, Feb 4, 2013 at 6:18 AM, James Heather <span dir="ltr">&lt;<a href="mailto:j.heather@surrey.ac.uk" target="_blank">j.heather@surrey.ac.uk</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

It appears that /etc/rc.d/init.d/livesys gets executed, but the boot<br>
process isn&#39;t waiting for it to complete. So it runs for ever in the<br>
background, waiting for the password.<br>
<br>
When the machine has booted up, if I Ctrl-Alt-F2 and log in as root, I<br>
can see that livesys is still running, as is plymouth, still waiting for<br>
the password.<br>
<br>
I can&#39;t work out why this would be happening on a live USB stick, but<br>
not on a HDD installation. My other machines have seemingly the same<br>
setup, but they run fine.<br>
<br>
Please help... even if it&#39;s just to say that you are(n&#39;t) having this<br>
problem. It would be nice to know if it&#39;s just me.<br></blockquote><div><br></div><div>I&#39;ve experienced the same unanswerable wait for a password with a crypto_LUKS partition on home.img but not with an --unencrypted-home setup of a Live USB.</div>

<div><br></div><div>I noticed it also with updated Fedora 17 Live images.  I suspect that the systemd interaction with the crypto_LUKS players needs attention.</div><div><br></div><div>        --Fred</div></div>