All my Details appear in Reproducibility, Steps to Reproduce, and Actual Results below, except that: 1) The way I fell into pressing Ctrl-D once inadvertently was that I wanted to close the typescript file of a `script` session I was using to accurately log results to share at bugs.gentoo.org. 2) For me this was the "out of the box experience" that introduced Gentoo to me. Reproducible: Always Steps to Reproduce: 1. Boot Gentoo 2004.2 PPC live CD. 2. mkdir /mnt/hda ; mount -w /dev/hda /mnt/hda 3. Press Ctrl-D inadvertently. Actual Results: The boot shell exited, and prompted me to login with a password. I failed to guess the unknowable scrambled root password, and eventually resorted to powering off with my HDD still mounted, ouch. Expected Results: Don't exit the boot shell. Or print the root password before exit. Or log root into all the vt (virtual consoles) like the Knoppix live CD does. I chose "Severity" = "Critical: The software crashes, hangs, or causes you to lose data", because I lost the writability of my HDD this way. I first told my story at "Bug 61152" "Livecd: force mount hfsplus partition rw" last month, and by now people there have posted hopes of teaching 2004.3 to recover my HDD without erasing it.
At bug 61152 I see: ------ Additional Comment #9 From Pieter Van den Abeele 2004-09-22 16:44 PST ------- Livecd team: has the CTRL-D issue been fixed in catalyst? ... ------- Additional Comment #10 From Chris Gianelloni 2004-09-23 06:36 PST ------- livecd@ is not responsible for catalyst and do not have write access to the sources, just the actual release media that we create with catalyst. If you need something fixed in catalyst, you should file a bug and assign it to zhen@gentoo.org instead.
OK... I managed to get write access to catalyst, so now I can fix this... ;] Anyway, if you use baselayout 1.9.4-r6, then it starts bashlogin rather than using mingetty. It does this on all the consoles. While we are not trapping a control+d to stop someone from hitting it, the inittab will simply spawn another bash shell, so they should never get "logged out" at all.
