When using raspi-config to configure raspbian to boot directly to Scratch, a problem occurs if the pi user has been renamed or removed.
/etc/inittab is modified to auto login the pi user without checking if the pi user exists - if the user has been renamed this causes the process to respawn 'too quickly' and the user is unable to login to the console.
I suggest that raspi-config should check that the pi user exists before proceeding to modify /etc/inittab.
When using raspi-config to configure raspbian to boot directly to Scratch, a problem occurs if the pi user has been renamed or removed.
/etc/inittab is modified to auto login the pi user without checking if the pi user exists - if the user has been renamed this causes the process to respawn 'too quickly' and the user is unable to login to the console.
I suggest that raspi-config should check that the pi user exists before proceeding to modify /etc/inittab.