Hi Ward,
On Sat, Mar 29, 2008 at 06:09:27PM -0400, Ward Vandewege wrote:
Hi Andi,
On Sat, Mar 29, 2008 at 07:15:35PM +0100, Andreas B. Mundt wrote:
thanks for your hint, but a search for CONFIG_ASH_READ_TIMEOUT gives:
...buildrom-devel$ egrep -r CONFIG_ASH_READ_TIMEOUT * deploy/config/busybox/.config:CONFIG_ASH_READ_TIMEOUT=y
...........
support. (CONFIG_ASH_READ_TIMEOUT) [Y/n/?] y ....
so this seems not to be the reason.
Hmm, ok. Can you debug the lab environment? You could try to chroot into it on your build system, or else just comment out the kexec line and start a busybox shell instead on your target. You should then see what error 'read' is throwing.
I stopped in LAB and got just:
# read -t 5 ash: read: arg count
the same as if I just type:
# read ash: read: arg count
The weird thing is, that even the debian lenny busybox gives the same on my box (2.6.24-1-amd64):
andi@flashgordon:~$ busybox ash
BusyBox v1.1.3 (Debian 1:1.1.3-5) Built-in shell (ash) Enter 'help' for a list of built-in commands.
~ $ read -t 5 ash: read: arg count ~ $ read ash: read: arg count ~ $ exit
from the source of busybox in debian I checked that CONFIG_ASH_READ_TIMEOUT=y is enabled there as well.
Only bash works fine:
andi@flashgordon:~$ read -t 5 hello andi@flashgordon:~$ echo $REPLY hello
So for the time being I'm stuck, and I guess the weather is to good to explore that further now...
Thanks,
Andi