Just rebuilt my F17 live USB with F18. It seems fine, except that something weird is happening with mounting persistent /home. It asks for the password, but then seems to carry on more or less immediately without waiting for me to type it in. The consequence is that /home doesn't get unencrypted and mounted.
The problem seems to be in /etc/rc.d/init.d/livesys. That's where the password prompting happens, and nothing after that line gets executed. I'd added a line to the end of that file to create a 'james' user, and in F17, it got executed fine; but it's now never reaching that point.
I can Ctrl-Alt-F2, log in as root, manually mount /home, and manually create the 'james' user, but that's not much fun. I'd have to do the mounting bit every time.
Any clues?
James
It appears that /etc/rc.d/init.d/livesys gets executed, but the boot process isn't waiting for it to complete. So it runs for ever in the background, waiting for the password.
When the machine has booted up, if I Ctrl-Alt-F2 and log in as root, I can see that livesys is still running, as is plymouth, still waiting for the password.
I can't work out why this would be happening on a live USB stick, but not on a HDD installation. My other machines have seemingly the same setup, but they run fine.
Please help... even if it's just to say that you are(n't) having this problem. It would be nice to know if it's just me.
James
On Sun, 2013-02-03 at 23:11 +0000, James Heather wrote:
Just rebuilt my F17 live USB with F18. It seems fine, except that something weird is happening with mounting persistent /home. It asks for the password, but then seems to carry on more or less immediately without waiting for me to type it in. The consequence is that /home doesn't get unencrypted and mounted.
The problem seems to be in /etc/rc.d/init.d/livesys. That's where the password prompting happens, and nothing after that line gets executed. I'd added a line to the end of that file to create a 'james' user, and in F17, it got executed fine; but it's now never reaching that point.
I can Ctrl-Alt-F2, log in as root, manually mount /home, and manually create the 'james' user, but that's not much fun. I'd have to do the mounting bit every time.
Any clues?
James
-- livecd mailing list livecd@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/livecd
On Mon, Feb 4, 2013 at 6:18 AM, James Heather j.heather@surrey.ac.ukwrote:
It appears that /etc/rc.d/init.d/livesys gets executed, but the boot process isn't waiting for it to complete. So it runs for ever in the background, waiting for the password.
When the machine has booted up, if I Ctrl-Alt-F2 and log in as root, I can see that livesys is still running, as is plymouth, still waiting for the password.
I can't work out why this would be happening on a live USB stick, but not on a HDD installation. My other machines have seemingly the same setup, but they run fine.
Please help... even if it's just to say that you are(n't) having this problem. It would be nice to know if it's just me.
I'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.
I noticed it also with updated Fedora 17 Live images. I suspect that the systemd interaction with the crypto_LUKS players needs attention.
--Fred
I'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.
I noticed it also with updated Fedora 17 Live images. I suspect that the systemd interaction with the crypto_LUKS players needs attention.
Ah--glad it's not just me.
I also wondered whether it was the change to systemd: presumably there was some way previously of running a startup script interactively and in the foreground, but now everything's getting forced into the background.
James
Now reported as
https://bugzilla.redhat.com/show_bug.cgi?id=907622
James
On Mon, 2013-02-04 at 16:06 +0000, James Heather wrote:
I'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.
I noticed it also with updated Fedora 17 Live images. I suspect that the systemd interaction with the crypto_LUKS players needs attention.
Ah--glad it's not just me.
I also wondered whether it was the change to systemd: presumably there was some way previously of running a startup script interactively and in the foreground, but now everything's getting forced into the background.
James
-- livecd mailing list livecd@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/livecd
livecd@lists.fedoraproject.org
-
Frederick Grose -
James Heather