Comment 92 for bug 96084

OK. Just found this in a random FAQ searching for Busybox and the above error:

> Why do I keep getting "sh: can't access tty; job control turned off" errors? Why doesn't Control-C work
> within my shell?
>
> Job control will be turned off since your shell can not obtain a controlling terminal. This typically happens
> when you run your shell on /dev/console. The kernel will not provide a controlling terminal on the
> /dev/console device. Your should run your shell on a normal tty such as tty1 or ttyS0 and everything will
> work perfectly. If you REALLY want your shell to run on /dev/console, then you can hack your kernel (if
> you are into that sortof thing) by changing drivers/char/tty_io.c to change the lines where it sets
> "noctty = 1;" to instead set it to "0". I recommend you instead run your shell on a real console...

What this suggests to me is that the Busybox error is irrelevant. The bug/problem/whatever is arising before Busybox is invoked and that "bug" then results in Busybox being started. Busybox cannot give a controlling terminal on the /dev/console device so hence the error.

The problem with a clean install, though, is that you can't see the error which causes the Busybox shell to be invoked. You just get the Ubuntu logo and the progress bar.